how to enable init.d support? - Motorola Atrix HD

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

Related

[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.

[Q] REvolution oneclick root help

I was unsuccessful in my search so I am posting my question in this QA forum.
The original thread was in the Revolution Android Development subforum but I am unable to post on that thread as I am a useless noob.
I have a LG Revolution Android version 2.3.4
I followed the directions as posted:
How Do I Root and Install CWM?:
1) Download zip and extract
2) Install drivers if not already installed
3) Click root.bat and watch the magic!!!
I unzipped and was able to update drivers
I was sure to have the USB debugging on (before connecting).
I also set the the USB connection to Internet connection
I clicked root.bat and the following line is repeated almost every other line
'adb' is not recoginized as an internal or external command
At the very end it says:
[*] root complete, enjoy!
[*] Press any key to continue..
When I try to open Titanium backup or Barnacle it says I do not have root
A few other things I'm noticing is that I keep getting usb device not recognized when connecting the phone via usb.
I also noticed a LG software upgrade assistant in my PC tray that I cannot remove.
Any help would be greatly appreciated.
With adb not recognized it sounds like you just ran the root.bat without extracting the zip extract the zip to a folder the click on root.bat
Sent from my VS910 4G using xda premium
Yes, I believe I just unzipped the file and clicked the root.bat. Where do I extract the file to?
Thanks for your response.
Doesn't really matter you just need to extract it you can make a new folder and extract to that
Sent from my VS910 4G using xda premium
Beamer, that certainly did the trick.
Confirmed rooted with access to Barnacle and Titanium.
Now I need to figure out the Gingervolt process. Only about 75 more pages to read through.
Lol if you have clockwork mod recovery just download gingervolt put it on your sd card boot into recovery hold power button down and volume down at the same time until you get to the black screen asking to wipe data or something like that hit the power button to confirm this will not wipe your data but will boot into recovery once in recovery use the volume keys to navigate and power button to select then follow all of the directions in the 1st post every step is important.
Sent from my VS910 4G using xda premium
atlsud said:
Beamer, that certainly did the trick.
Confirmed rooted with access to Barnacle and Titanium.
Now I need to figure out the Gingervolt process. Only about 75 more pages to read through.
Click to expand...
Click to collapse
I appreciate you actually reading instead of instantly asking to be spoon fed!
atlsud said:
I was unsuccessful in my search so I am posting my question in this QA forum.
The original thread was in the Revolution Android Development subforum but I am unable to post on that thread as I am a useless noob.
I have a LG Revolution Android version 2.3.4
I followed the directions as posted:
How Do I Root and Install CWM?:
1) Download zip and extract
2) Install drivers if not already installed
3) Click root.bat and watch the magic!!!
I unzipped and was able to update drivers
I was sure to have the USB debugging on (before connecting).
I also set the the USB connection to Internet connection
I clicked root.bat and the following line is repeated almost every other line
'adb' is not recoginized as an internal or external command
At the very end it says:
[*] root complete, enjoy!
[*] Press any key to continue..
When I try to open Titanium backup or Barnacle it says I do not have root
A few other things I'm noticing is that I keep getting usb device not recognized when connecting the phone via usb.
I also noticed a LG software upgrade assistant in my PC tray that I cannot remove.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
how would one go about downloading
1) Download zip and extract
2) Install drivers if not already installed
3) Click root.bat and watch the magic!!![/I][/B]
AssumedDarkness said:
how would one go about downloading
1) Download zip and extract
2) Install drivers if not already installed
3) Click root.bat and watch the magic!!![/I][/B]
Click to expand...
Click to collapse
Here:
http://forum.xda-developers.com/showthread.php?t=1348557
Follow this post, it's as simple as that.
http://forum.xda-developers.com/showthread.php?t=1326542&page=54
It's the easiest to understand for me & worked flawlessly.
Ed
please help
AssumedDarkness said:
how would one go about downloading
1) Download zip and extract
2) Install drivers if not already installed
3) Click root.bat and watch the magic!!![/I][/B]
Click to expand...
Click to collapse
no im coming up with this and im stuck
Removing Trash and Installing Root Files
rm failed for /system/tmp/su, No such file or directory
rm failed for /system/tmp/busybox, No such file or directory
rm failed for /system/tmp/Superuser.apk, No such file or directory
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
rmdir failed for /system/tmp, No such file or directory
AssumedDarkness said:
no im coming up with this and im stuck
Removing Trash and Installing Root Files
rm failed for /system/tmp/su, No such file or directory
rm failed for /system/tmp/busybox, No such file or directory
rm failed for /system/tmp/Superuser.apk, No such file or directory
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
rmdir failed for /system/tmp, No such file or directory
Click to expand...
Click to collapse
Copy and paste the whole thing to pastebin and drop a link in here and I will look at it. That small portion could be normal, I would just have to look at the rest to know for sure.
Sent from my VS910 4G using xda premium
I am trying to root my Revolution 2.3.4 ( I am a complete newb)
How will I know it is rooted?
This is what showed up when it was finished:
Rooting the LG Revolution
Tool Built by mtmichaelson
Exploit Built by the Revolutionary Team
Rooting
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Pushing Zergrush
1279 KB/s (22281 bytes in 0.017s)
Running Zergrush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x40121cd4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd255f1 0xafd39067
[*] Poping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
Removing Trash and Installing Root Files
rm failed for /system/tmp/su, No such file or directory
rm failed for /system/tmp/busybox, No such file or directory
rm failed for /system/tmp/Superuser.apk, No such file or directory
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
rmdir failed for /system/tmp, No such file or directory
3639 KB/s (22364 bytes in 0.006s)
3778 KB/s (828156 bytes in 0.214s)
2550 KB/s (843503 bytes in 0.323s)
Removing Trash
Finished Rooting!!!
Press any key to continue . . .
Is that normal?
Is there anything else I need to download on the phone to get rid of bloatware? I am not sure really how to do this.
Thanks!
AprilRevo said:
I am trying to root my Revolution 2.3.4 ( I am a complete newb)
How will I know it is rooted?
This is what showed up when it was finished:
Rooting the LG Revolution
Tool Built by mtmichaelson
Exploit Built by the Revolutionary Team
Rooting
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Pushing Zergrush
1279 KB/s (22281 bytes in 0.017s)
Running Zergrush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.
[+] Found a GingerBread ! 0x00017118
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[*] Trying a new path ...
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x40121cd4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd255f1 0xafd39067
[*] Poping 24 more zerglings
[*] Sending 173 zerglings ...
[+] Rush did it ! It's a GG, man !
Removing Trash and Installing Root Files
rm failed for /system/tmp/su, No such file or directory
rm failed for /system/tmp/busybox, No such file or directory
rm failed for /system/tmp/Superuser.apk, No such file or directory
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
rmdir failed for /system/tmp, No such file or directory
3639 KB/s (22364 bytes in 0.006s)
3778 KB/s (828156 bytes in 0.214s)
2550 KB/s (843503 bytes in 0.323s)
Removing Trash
Finished Rooting!!!
Press any key to continue . . .
Is that normal?
Is there anything else I need to download on the phone to get rid of bloatware? I am not sure really how to do this.
Thanks!
Click to expand...
Click to collapse
You are now rooted, I would install CWM and do a back up before doing anything else though.
Sent from my VS910 4G using xda premium
Do I get CWM from the same file as the root?
If so, I did run the "CWM Recovery" from that file. Is that what you mean?
I also see that I am rooted, I downloaded the titinium backup and was able to uninstall a lot of Verizons app that I never use.
Anything else good to do with a rooted Revo?
Gingervolt it !!!! 2.0 is real good & removes all of the bloat. If you find yourself missing anything from the stock that youo want, get the "Stock app installer" & reload what you want...
\Ed

V8 rooted but no CWM

I was on v8 non-rooted.
I followed the instructions here to the letter:
http://forum.xda-developers.com/showthread.php?t=1566729&page=4
didn't have any issues at all, no errors.
I'm confirmed on V8 and do have root but can't access CWM. Attempting to run the new AIO again gives the following:
Root and Recovery for ZV8
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found
Mounting Device
remount failed: Operation not permitted
Pushing Root Permissions
Unable to chmod /system/bin/su: Read-only file system
7781 KB/s (5345280 bytes in 0.670s)
Unable to chmod /system/xbin/busybox: Read-only file system
Installing CWM Recovery
/dev/block/mmcblk0p14: cannot open for write: Permission denied
Remove Trash
rm failed for /system/etc/install-recovery.sh, Read-only file system
rm failed for /system/recovery-from-boot.p, Read-only file system
rm failed for /data/local.prop, No such file or directory
CWM Recovery!!!
Press any key to continue . . .
Any ideas how to get to CWM?
Looks like you need to root again after your upgrade. Run MT's Root&RecoveryAIO.bat again and select the "Root ZV8" option.
[EDIT]
My bad. That's what you are trying to do! I've been up all night and am tired. Did you get any errors when you ran the "Prepare for Update" option before you upgraded? That option actually pushes the superuser files back to your phone and the "Root ZV8" option just goes back and set's the permissions. You can try manually running these commands with adb first.
Files\adb push Files\zergrush /data/local/tmp/zergrush
Files\adb shell "chmod 755 /data/local/tmp/zergrush"

Z1 boots but cant boot into recovery or bootloader

Hey guys,
i have rooted many phones before, however i am having a problem with a previously rooted Sony Z1.
The previous happenings:
I rooted the device by unlocking the bootloader on the sony site. I then loaded on clockwork recovery and slapped cyanogen mod on it.
The phone was fine and working nicely, but recently stopped updating Cyanogen mod. I attempted to boot into recovery to install the latest version but all combinations of button pushing lead to nothing for a good few seconds before it starts to boot back into cyanogenmod again.
I tried using apps and various other methods to boot into fastboot, recovery and bootloader but it all goes right back into the OS.
I now have no way of updating the OS and tried using ADB to load on recovery again. ADB can see the device, and pushes successfully but when trying to boot into it, again, it does nothing but go back to the OS.
Can anyone give me a hand in popping on a recovery and somehow installing the latest Cyanogen back on? This is by far the biggest pain in the butt phone to root to begin with, but any help is much appreciated.
Tex0gen said:
Hey guys,
i have rooted many phones before, however i am having a problem with a previously rooted Sony Z1.
The previous happenings:
I rooted the device by unlocking the bootloader on the sony site. I then loaded on clockwork recovery and slapped cyanogen mod on it.
The phone was fine and working nicely, but recently stopped updating Cyanogen mod. I attempted to boot into recovery to install the latest version but all combinations of button pushing lead to nothing for a good few seconds before it starts to boot back into cyanogenmod again.
I tried using apps and various other methods to boot into fastboot, recovery and bootloader but it all goes right back into the OS.
I now have no way of updating the OS and tried using ADB to load on recovery again. ADB can see the device, and pushes successfully but when trying to boot into it, again, it does nothing but go back to the OS.
Can anyone give me a hand in popping on a recovery and somehow installing the latest Cyanogen back on? This is by far the biggest pain in the butt phone to root to begin with, but any help is much appreciated.
Click to expand...
Click to collapse
I've ran into almost exactly the same issue. Only difference is that I'm yet to install a custom ROM.
If anyone has a solution it would be greatly appreciated.
spiritonline said:
I've ran into almost exactly the same issue. Only difference is that I'm yet to install a custom ROM.
If anyone has a solution it would be greatly appreciated.
Click to expand...
Click to collapse
Just reflash dual recovery. I had the same issue before just flash dual recovery from the install batch or shell file and should work
JustPlayingHard said:
Just reflash dual recovery. I had the same issue before just flash dual recovery from the install batch or shell file and should work
Click to expand...
Click to collapse
I've tried this to no avail unfortunately.
if your cm rom 's zip got boot.img flash it
Sent from my C6903 Xperia Z1 using Tapatalk
---------- Post added at 09:02 AM ---------- Previous post was at 09:00 AM ----------
using fastboot flash it
i think the boot .img include kernel with recovery
==============================================
fastboot flash boot boot.img
Sent from my C6903 Xperia Z1 using Tapatalk
JustPlayingHard said:
Just reflash dual recovery. I had the same issue before just flash dual recovery from the install batch or shell file and should work
Click to expand...
Click to collapse
Dual recovery is for stock roms, it won't work on CM.
Sent from my C6903 using XDA Premium 4 mobile app
gregbradley said:
Dual recovery is for stock roms, it won't work on CM.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Whoops I'm so sorry didn't read it was CM. Try flash a kernel with Recovery in it?
gregbradley said:
Dual recovery is for stock roms, it won't work on CM.
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm on the stock Vodafone rom.
I've tried running the dual recovery again it says it succeeds but I still can't boot into flash mode.
The weird thing is that I previously could.
I've also tried flashing boot.img but still no luck
Any other suggestions?
Thanks in advance!
spiritonline said:
I'm on the stock Vodafone rom.
Click to expand...
Click to collapse
have you rooted it?
I've tried running the dual recovery again it says it succeeds but I still can't boot into flash mode.
Click to expand...
Click to collapse
You do not need recovery or root to enter flashmode. Flashmode is a boot mode that completely stock phones can boot into in order to perform updates via PCCompanion
The weird thing is that I previously could.
I've also tried flashing boot.img but still no luck
Click to expand...
Click to collapse
Have you unlocked the bootloader?
Any other suggestions?
Click to expand...
Click to collapse
Yes, please post the output of the command window when you try to install dual recovery
Thanks in advance!
Click to expand...
Click to collapse
gregbradley said:
have you rooted it?You do not need recovery or root to enter flashmode. Flashmode is a boot mode that completely stock phones can boot into in order to perform updates via PCCompanionHave you unlocked the bootloader?Yes, please post the output of the command window when you try to install dual recovery
Click to expand...
Click to collapse
I'm not sure how to quote inline as you just did but:
- Yes I've rooted the phone
- You're right I'm mixing things up. I can't enter recovery I can go to flash mode. (blue led)
- No I haven't unlocked the boot loader
- Dual fails on my Mac, I will boot into my windows install and come back with the output.
Thanks for your time.
spiritonline said:
I'm not sure how to quote inline as you just did but:
- Yes I've rooted the phone
- You're right I'm mixing things up. I can't enter recovery I can go to flash mode. (blue led)
Click to expand...
Click to collapse
Wrong, Blue LED is fastboot, green LED is flashmode. This may be your issue.
- No I haven't unlocked the boot loader
Click to expand...
Click to collapse
then you wont be able to flash the boot.img
- Dual fails on my Mac, I will boot into my windows install and come back with the output.
Click to expand...
Click to collapse
It is a windows based installer, so that may help
Thanks for your time.
Click to expand...
Click to collapse
gregbradley said:
Wrong, Blue LED is fastboot, green LED is flashmode. This may be your issue.then you wont be able to flash the boot.imgIt is a windows based installer, so that may help
Click to expand...
Click to collapse
You're quick!
Here's the output:
Code:
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices! =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit
Please choose install action.
[1,2,3,4,5]?1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
=============================================
Getting ro.build.product
=============================================
Device model is C6903
Firmware is 14.4.A.0.133
=============================================
Step2 : Sending the recovery files.
=============================================
mkdir failed for /data/local/tmp/recovery, File exists
13 KB/s (29 bytes in 0.002s)
3710 KB/s (15757 bytes in 0.004s)
297 KB/s (501 bytes in 0.001s)
3952 KB/s (11842 bytes in 0.002s)
5157 KB/s (56834 bytes in 0.010s)
1914 KB/s (3082 bytes in 0.001s)
187 KB/s (385 bytes in 0.002s)
5708 KB/s (657704 bytes in 0.112s)
5432 KB/s (2965179 bytes in 0.533s)
5374 KB/s (2598631 bytes in 0.472s)
5795 KB/s (1875928 bytes in 0.316s)
3093 KB/s (8759 bytes in 0.002s)
=============================================
Step3 : Setup of dual recovery.
=============================================
Look at your device and grant supersu access!
Press any key to continue AFTER granting root access.
-rwxr-xr-x 1 shell shell 657704 Jul 31 17:09 /data/local/tmp/recover
y/busybox
Press any key to continue . . .
##########################################################
#
# Installing XZDR version 2.7.154 BETA
#
#####
Temporarily disabling the RIC service, remount rootfs and /system writable to al
low installation.
mount: permission denied (are you root?)
mount: permission denied (are you root?)
Copy recovery files to system.
cp: can't create '/system/bin/recovery.twrp.cpio.lzma': File exists
cp: can't create '/system/bin/recovery.cwm.cpio.lzma': File exists
cp: can't create '/system/bin/recovery.philz.cpio.lzma': File exists
chmod: /system/bin/recovery.twrp.cpio.lzma: Read-only file system
chmod: /system/bin/recovery.cwm.cpio.lzma: Read-only file system
chmod: /system/bin/recovery.philz.cpio.lzma: Read-only file system
Copy chargemon script to system.
cp: can't create '/system/bin/chargemon': File exists
chmod: /system/bin/chargemon: Read-only file system
Copy dualrecovery.sh to system.
cp: can't create '/system/bin/dualrecovery.sh': File exists
chmod: /system/bin/dualrecovery.sh: Read-only file system
Copy rickiller.sh to system.
cp: can't create '/system/bin/rickiller.sh': File exists
chmod: /system/bin/rickiller.sh: Read-only file system
Installing NDRUtils to system.
cp: can't create '/system/app/NDRUtils.apk': File exists
chmod: /system/app/NDRUtils.apk: Read-only file system
Copy disableric to system.
cp: can't create '/system/xbin/disableric': File exists
chmod: /system/xbin/disableric: Read-only file system
Copy busybox to system.
cp: can't create '/system/xbin/busybox': Read-only file system
cp: can't create '/system/.XZDualRecovery/busybox': File exists
chmod: /system/xbin/busybox: No such file or directory
Trying to find and update the gpio-keys event node.
Found and will be using /dev/input/event4!
Trying to find and update the power key event node.
Found and will be monitoring /dev/input/event3!
Speeding up backups.
Make sure firstboot goes to recovery.
=============================================
DEVICE WILL NOW TRY A DATA SAFE REBOOT!
=============================================
=============================================
Your installation has already cleaned up after
itself if you see the install.bat/install.sh exit.
=============================================
/system/bin/sh: /system/xbin/busybox: not found
=============================================
Installation finished. Enjoy the recoveries!
=============================================
Press any key to continue . . .
There is an issue with your root. Can you remount the system partition into read/write?
Please goto
sys/kernel/security/sony_ric
and look in the file that is there (If there is one). Please tell me if it says 1 or 0.
Can you let me know how you rooted?
gregbradley said:
There is an issue with your root. Can you remount the system partition into read/write?
Please goto
sys/kernel/security/sony_ric
and look in the file that is there (If there is one). Please tell me if it says 1 or 0.
Can you let me know how you rooted?
Click to expand...
Click to collapse
I'm not sure how to remount the system partition into read/write.
The folder you suggested is indeed empty.
I've rooted trough this guide: http://forum.xda-developers.com/xperia-z1/development/c6903-14-4-0-133-deodex-patch-root-t2848466
I can imagine something being wrong but it worked to some extend since I have superSU working.
Thanks again.
spiritonline said:
I'm not sure how to remount the system partition into read/write.
Click to expand...
Click to collapse
Use any root explorer and goto system and try to create a file or folder. If you are not mounted as RW it will prompt you to do so. Let me know if you can create a file or folder in the system partition
The folder you suggested is indeed empty.
I've rooted trough this guide: http://forum.xda-developers.com/xperia-z1/development/c6903-14-4-0-133-deodex-patch-root-t2848466
Click to expand...
Click to collapse
That should be ok and install dual recovery. The issue is getting the system to be RW. Try running it again and use option 3.
I can imagine something being wrong but it worked to some extend since I have superSU working.
Thanks again.
Click to expand...
Click to collapse
If it still does not work, then you can try flashing the stock 133 FTF again and going through the process of rooting again using option 3
gregbradley said:
Use any root explorer and goto system and try to create a file or folder. If you are not mounted as RW it will prompt you to do so. Let me know if you can create a file or folder in the system partition That should be ok and install dual recovery. The issue is getting the system to be RW. Try running it again and use option 3.
If it still does not work, then you can try flashing the stock 133 FTF again and going through the process of rooting again using option 3
Click to expand...
Click to collapse
Thanks for your continues support on this.
I'm unable to create a new folder in the system directory as you predicted.
I just tried to do recovery option 3 but it hangs on "libdvm opend <lol javasucks>
I've posted everything bellow. (I will now try to flash 133 again.)
Code:
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices! =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit
Please choose install action.
[1,2,3,4,5]?3
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
=============================================
Getting ro.build.product
=============================================
Device model is C6903
Firmware is 14.4.A.0.133
=============================================
Step2 : Sending the recovery files.
=============================================
mkdir failed for /data/local/tmp/recovery, File exists
4 KB/s (29 bytes in 0.006s)
1837 KB/s (15757 bytes in 0.008s)
132 KB/s (501 bytes in 0.003s)
1667 KB/s (11842 bytes in 0.006s)
2784 KB/s (56834 bytes in 0.019s)
625 KB/s (3082 bytes in 0.004s)
123 KB/s (385 bytes in 0.003s)
2788 KB/s (657704 bytes in 0.230s)
3484 KB/s (2965179 bytes in 0.830s)
4140 KB/s (2598631 bytes in 0.612s)
3605 KB/s (1875928 bytes in 0.508s)
1487 KB/s (8759 bytes in 0.005s)
=============================================
Step3 : Setup of dual recovery.
=============================================
=============================================
Attempting to get root access for installation using TowelRoot now.
NOTE: this only works on certain ROM/Kernel versions!
If it fails, please check the development thread (Post #2) on XDA for more detai
ls.
REMEMBER THIS:
XZDualRecovery does NOT install any superuser app!!
You can use one of the recoveries to root your device.
=============================================
=============================================
Sending files
=============================================
505 KB/s (1572 bytes in 0.003s)
3929 KB/s (13592 bytes in 0.003s)
5716 KB/s (197320 bytes in 0.033s)
2356 KB/s (9496 bytes in 0.003s)
2973 KB/s (13672 bytes in 0.004s)
Copying kernel module...
3693 KB/s (34473 bytes in 0.009s)
342 KB/s (765 bytes in 0.002s)
2778 KB/s (13592 bytes in 0.004s)
Kernel version is 3.4.0-perf-gf96f13d-00901-g5169043
Version does not match 3.4.0-perf-ge4322cd, needs patching...
1+0 records in
0+1 records out
34 bytes transferred in 0.001 secs (34000 bytes/sec)
Kernel module patched.
modulecrcpatch (by zxz0O0)
module_layout: match
__aeabi_unwind_cpp_pr1: match
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: match
successfully patched
=============================================
Installing using zxz0O0's towelzxperia
(using geohot's towelroot library)
=============================================
towelzxperia (by zxz0O0)
thanks to geohot for libexploit
creating libzxploit.so
libzxploit.so created
doing the magic
creating vm (loljavasucks)
libdvm opened (loljavasucks)
spiritonline said:
Thanks for your continues support on this.
I'm unable to create a new folder in the system directory as you predicted.
I just tried to do recovery option 3 but it hangs on "libdvm opend <lol javasucks>
I've posted everything bellow. (I will now try to flash 133 again.)
Code:
==============================================
= =
= PhilZ Touch, CWM and TWRP Dual Recovery =
= Maintained by [NUT] =
= =
= For Many Sony Xperia Devices! =
= =
==============================================
1. Installation on ROM rooted with SuperSU
2. Installation on ROM rooted with SuperUser
3. Installation on unrooted ROM using the TowelRoot method
4. Install ADB drivers to windows
5. Exit
Please choose install action.
[1,2,3,4,5]?3
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
=============================================
Waiting for Device, connect USB cable now...
=============================================
Device found!
=============================================
Getting ro.build.product
=============================================
Device model is C6903
Firmware is 14.4.A.0.133
=============================================
Step2 : Sending the recovery files.
=============================================
mkdir failed for /data/local/tmp/recovery, File exists
4 KB/s (29 bytes in 0.006s)
1837 KB/s (15757 bytes in 0.008s)
132 KB/s (501 bytes in 0.003s)
1667 KB/s (11842 bytes in 0.006s)
2784 KB/s (56834 bytes in 0.019s)
625 KB/s (3082 bytes in 0.004s)
123 KB/s (385 bytes in 0.003s)
2788 KB/s (657704 bytes in 0.230s)
3484 KB/s (2965179 bytes in 0.830s)
4140 KB/s (2598631 bytes in 0.612s)
3605 KB/s (1875928 bytes in 0.508s)
1487 KB/s (8759 bytes in 0.005s)
=============================================
Step3 : Setup of dual recovery.
=============================================
=============================================
Attempting to get root access for installation using TowelRoot now.
NOTE: this only works on certain ROM/Kernel versions!
If it fails, please check the development thread (Post #2) on XDA for more detai
ls.
REMEMBER THIS:
XZDualRecovery does NOT install any superuser app!!
You can use one of the recoveries to root your device.
=============================================
=============================================
Sending files
=============================================
505 KB/s (1572 bytes in 0.003s)
3929 KB/s (13592 bytes in 0.003s)
5716 KB/s (197320 bytes in 0.033s)
2356 KB/s (9496 bytes in 0.003s)
2973 KB/s (13672 bytes in 0.004s)
Copying kernel module...
3693 KB/s (34473 bytes in 0.009s)
342 KB/s (765 bytes in 0.002s)
2778 KB/s (13592 bytes in 0.004s)
Kernel version is 3.4.0-perf-gf96f13d-00901-g5169043
Version does not match 3.4.0-perf-ge4322cd, needs patching...
1+0 records in
0+1 records out
34 bytes transferred in 0.001 secs (34000 bytes/sec)
Kernel module patched.
modulecrcpatch (by zxz0O0)
module_layout: match
__aeabi_unwind_cpp_pr1: match
kallsyms_lookup_name: not found
printk: not found
mem_text_write_kernel_word: not found
__aeabi_unwind_cpp_pr0: match
successfully patched
=============================================
Installing using zxz0O0's towelzxperia
(using geohot's towelroot library)
=============================================
towelzxperia (by zxz0O0)
thanks to geohot for libexploit
creating libzxploit.so
libzxploit.so created
doing the magic
creating vm (loljavasucks)
libdvm opened (loljavasucks)
Click to expand...
Click to collapse
Ok don't forget to flash the .108 kernel. It hangs there if you are on the .133 kernel.
gregbradley said:
Ok don't forget to flash the .108 kernel. It hangs there if you are on the .133 kernel.
Click to expand...
Click to collapse
Ok, so I flash the .108 first, then root, then flash 133?
Yes, but kernel only
Sent from my C6903 using XDA Premium 4 mobile app
gregbradley said:
Yes, but kernel only
Sent from my C6903 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok, so I
1. flashed .108
2. rooted user dualrecovery
3. verified permissions by creating a new file in system and recovery was working fine.
I then tried to install darkCM per instructions but after flashing in recovery the phone wont boot.
It will just show a a blinking red LED when it's on a charger.
The only way I could find to fix it was to install stock vodafone firmware.
I retried the above twice with the same result, I hope I'm not to much a nuisance but if you could help me any further i'd appreciate it.:good:

Categories

Resources