Related
Hi,
I succeeded at installing the recovery image using flashrec and making the nandroid backup. Now I'm trying to go to the next step of the rooting tutorial for noobs: MODIFYING THE CODE TO GET ROOT ACCESSS
This is my cmd (administrator rights) in Fastboot USB Mode:
Code:
c:\sdk\tools>fastboot devices
HT**KL****** fastboot
c:\sdk\tools>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
This is my cmd (administrator rights) in "normal mode":
Code:
c:\sdk\tools>adb devices
List of devices attached
HT**KL****** device
c:\sdk\tools>adb shell mount /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
c:\sdk\tools>adb push su /system/bin/
failed to copy 'su' to '/system/bin//su': Read-only file system
c:\sdk\tools>adb push su /system/bin
failed to copy 'su' to '/system/bin/su': Read-only file system
c:\sdk\tools>adb shell rm /system/app/Superuser.apk
rm failed for /system/app/Superuser.apk, Read-only file system
c:\sdk\tools>adb push su /system/bin/
failed to copy 'su' to '/system/bin//su': Read-only file system
c:\sdk\tools>adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /syste
m
mount: Operation not permitted
c:\sdk\tools>adb shell chmod 777 /system
Unable to chmod /system: Read-only file system
I am running Windows 7 (x64), I downloaded the latest adb tools and usb drivers using SDK Setup.exe. I installed the ADB drivers properly (using the manual wizard to browse to the usb_driver folder and restarting my computer) for the fastboot USB and for "normal mode" with the option debugging usb active.
Information of my current Rom ("Orange Belgium")
HBOOT-1.76.0007 (HERO10000)
RADIO-6.35.06.18
Aug 4 2009,19:43:30
I couldn't find anything by google that solved the problem... I hope you guys can help me out..
First and foremost, please post questions like this in the Q&A, or GENERAL section next time. This part will be moved for you though.
Ok,... I think your making this more difficult than need be. I haven't looked at the link you provided as my phone is playing up..
Take a look at BTDAGs guide linked in my signature... If you have already successfully installed the custom recovery, all you need to do now is pick a custom ROM to download and flash using the recovery.
Sent from my HTC Hero using XDA App
That is quite an old guide you're following. Try mine, or the one here http://villainrom.co.uk/viewtopic.php?f=107&t=2028 or there is universal androot - which will just give you root access on any rom.
you should use this to mount system in read/write-mode:
Code:
# mount -o rw -t yaffs2 /dev/block/mtdblock3 /system
alternatively put adb shell in front of:
Code:
>adb shell mount -o rw -t yaffs2 /dev/block/mtdblock3 /system
And by the way, you should do this from recovery mode (which is accessed by keeping home-button pressed down while turning on. I assume that you have a custom recovery)
Moved to Q&A as not development
Managed to put the recovery rom on it, thanks!
sorry to post it this late. can you pls explain how you resolve? if its available in some other thread, can someone guide me there. have been doing search on the forum for a while now. thanks!
Found a one root script. Just need to see if it'll work on the Amaze. If it does, I'll add it in my tool and give proper credits as always. If not, I'll look into it myself.
Prerequisites?
_________________________
Am I on Candid Camera?
Same as usual. S-off or unlock boot loader.
I will be able to help after work in few hours if still needed. Unless I don't need a computer, in which if that's the case, I'll help ya out now
_________________________
Am I on Candid Camera?
You need a computer, I just need a few testers. Thanks GG!
hasoon2000 said:
You need a computer, I just need a few testers. Thanks GG!
Click to expand...
Click to collapse
I'm home I'm an hour and half... I'll ccheck in then. No prob
_________________________
Am I on Candid Camera?
replacement is due in an hour or two so I will test it then.
zPacKRat said:
replacement is due in an hour or two so I will test it then.
Click to expand...
Click to collapse
Before you s-off/unlock your boot loader, run the script. Tell me if it works. If it does, reboot the phone twice and see if it is a perm root or temp root.
Wife says I'm busy :banghead:
Sorry 4 now
_________________________
Am I on Candid Camera?
hasoon2000 said:
Before you s-off/unlock your boot loader, run the script. Tell me if it works. If it does, reboot the phone twice and see if it is a perm root or temp root.
Click to expand...
Click to collapse
first attempt it hangs:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
749 KB/s (2005736 bytes in 2.613s)
640 KB/s (91980 bytes in 0.140s)
713 KB/s (570342 bytes in 0.781s)
REBOOT
cannot create /data/local.prop: permission denied
AGAIN REBOOT
After rebooting from power button it provided the following:
AGAIN!?
mount: Operation not permitted
mount: Operation not permitted
cannot create /system/xbin/busybox: read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
busybox: permission denied
busybox: permission denied
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
Unlock your boot loader and try it.
hasoon2000 said:
Unlock your boot loader and try it.
Click to expand...
Click to collapse
same!
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
4544 KB/s (2005736 bytes in 0.431s)
3592 KB/s (91980 bytes in 0.025s)
2978 KB/s (570342 bytes in 0.187s)
REBOOT
cannot create /data/local.prop: permission denied
AGAIN REBOOT
AGAIN!?
mount: Operation not permitted
mount: Operation not permitted
cannot create /system/xbin/busybox: read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/xbin/busybox: not found
busybox: permission denied
busybox: permission denied
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
Flash a recovery. Boot into recovery, run the command. Sorry for all this lol
from 4ext nothing, just hangs.
Hold on, adb is giving me issues.
Alright. Try CWM
no go from cwm
it seems that in recovery it hangs a "@adb wait-for-device"
below is what happened when I removed the wait for device command and changed reboot to reboot recovery.
I had dropped the last part of the script in manually to finish the process.
* server not running *
DON'T TOUCH THE DEVICE OR UNPLUG WHILE ROOTING!
PUSH FILES
788 KB/s (2005736 bytes in 2.483s)
747 KB/s (91980 bytes in 0.120s)
704 KB/s (570342 bytes in 0.791s)
mv: can't rename '/data/local/tmp': No such file or directory
REBOOT
error: device offline
AGAIN REBOOT
error: device offline
AGAIN!?
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "echo ro.kernel.qemu=1 > /data/local.prop"
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>ECHO
AGAIN REBOOT
AGAIN REBOOT
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
reboot recovery
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "mount -wo remount rootfs /"
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "mount -o remount,rw -t ext4
/dev/block/mmcblk0p30 on /cache type ext4 (rw,nodev,noatime,nodiratime,barrier=1
,data=ordered)
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>/dev
/block/mmcblk0p33 /system"
The system cannot find the path specified.
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "cat /data/local/busybox >
/sbin/sh: syntax error: unexpected end of file
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>/sys
tem/xbin/busybox"
The system cannot find the path specified.
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "chmod 777 /system/xbin/busybox"
chmod: /system/xbin/busybox: No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "/system/xbin/busybox --install -s
/sbin/sh: /system/xbin/busybox: not found
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>/sys
tem/xbin"
The system cannot find the path specified.
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "busybox cp /data/local/Superuser.apk
BusyBox v1.19.3-cm9 static (2011-11-20 14:44 +0100) multi-call binary.
Usage: cp [OPTIONS] SOURCE DEST
Copy SOURCE to DEST, or multiple SOURCE(s) to DIRECTORY
-a Same as -dpR
-R,-r Recurse
-d,-P Preserve symlinks (default if -R)
-L Follow all symlinks
-H Follow symlinks on command line
-p Preserve file attributes if possible
-f Overwrite
-i Prompt before overwrite
-l,-s Create (sym)links
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>/sys
tem/app/Superuser.apk"
The system cannot find the path specified.
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "busybox cp /data/local/su /system/xbin/su"
cp: can't stat '/data/local/su': No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "chown 0.0 /system/xbin/su"
chown: /system/xbin/su: No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "chmod 06755 /system/xbin/su"
chmod: /system/xbin/su: No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "chmod 644 /system/app/Superuser.apk"
chmod: /system/app/Superuser.apk: No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "rm /data/local.prop"
rm: can't remove '/data/local.prop': No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "rm /data/local/tmp"
rm: can't remove '/data/local/tmp': No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>@adb
shell "mv /data/local/tmp.bak /data/local/tmp"
mv: can't rename '/data/local/tmp.bak': No such file or directory
C:\Documents and Settings\user.account\My Documents\Downloads\Oneclickroot>
try this. It will reboot you in recovery
Just a heads up, I've s-offed and am upgrading to ICS because I have to get it ready for work tomorrow. let me know if there is any other way I can help.
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
Wait til you are in recovery, then press a button
Press any key to continue . . .
6359 KB/s (2005736 bytes in 0.308s)
6416 KB/s (91980 bytes in 0.014s)
5460 KB/s (570342 bytes in 0.102s)
mv: can't rename '/data/local/tmp': No such file or directory
mount: mounting /dev/block/mmcblk0p33 on /system failed: Invalid argument
/sbin/sh: can't create /system/xbin/busybox: nonexistent directory
chmod: /system/xbin/busybox: No such file or directory
/sbin/sh: /system/xbin/busybox: not found
cp: can't create '/system/app/Superuser.apk': No such file or directory
cp: can't create '/system/xbin/su': No such file or directory
chown: /system/xbin/su: No such file or directory
chmod: /system/xbin/su: No such file or directory
chmod: /system/app/Superuser.apk: No such file or directory
mv: can't rename '/data/local/tmp.bak': No such file or directory
C:\Users\user.account\Desktop\Oneclickroot>
I wouldn't recommend running this batch script on Amaze.
It doesn't even know where our system partition is mounted.
And if my memory is correct, we won't have root previledge to do much with adb shell right after unlocking the bootloader; we need to flash su binary using updater-script to begin with. As for the busybox, just install the 'busybox installer' so that users can run it in Android.
BTW, your all-in-one tool is very handy. Why no 4EXT recovery, though...
ringochan said:
I wouldn't recommend running this batch script on Amaze.
It doesn't even know where our system partition is mounted.
And if my memory is correct, we won't have root previledge to do much with adb shell right after unlocking the bootloader; we need to flash su binary using updater-script to begin with. As for the busybox, just install the 'busybox installer' so that users can run it in Android.
BTW, your all-in-one tool is very handy. Why no 4EXT recovery, though...
Click to expand...
Click to collapse
His tool does have ext4... You just have to get the full version from android-dev
Sent from my HTC_Amaze_4G using Tapatalk 2
I want to root my Android 4.0.4 virtual device for developing.......... How to root it?
Here you go ... ;-)
Paresh Kalinani said:
I want to root my Android 4.0.4 virtual device for developing.......... How to root it?
Click to expand...
Click to collapse
The following method is actually for 2.2 virtual machine ... but should work fine for 4.0 too ... i'll confirm after i have tested it ... meanwhile you can try it ..
You'll require
'su' binary
and
'busybox binary'
SU BINARY : See post's end
BUSY BOX BINARY : see posts end
Then, we need to start the emulator by providing extra partition size to /system. This can be done only through command-line
Code:
emulator -avd MyAndroid -partition-size 128 -no-snapshot-load
Make sure the AVD “MyAndroid” is already created. The “-no-snapshot-load” option is used if we enabled the snapshot. As a result, we will start the emulator with extra disk space for /system. By this, we can adding extra files to /system later.
Then, we need to use “adb shell” to remount the /system so that we have write access to the /system.
Code:
adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
Then, we can push the su and busybox to the /system/xbin.
Code:
adb push su /system/xbin/
adb push busybox /system/xbin/
Now, to actually make the su work properly, we need to chmod it,
Code:
adb shell chmod 06755 /system/xbin/su
adb shell chmod 06755 /system/xbin/busybox
Now, we need to install Superuser.apk (which you can get together with “su”). We can install it with “adb install” command. It is required when the other apps request for “su”.
We can try our “su” with Root Checker Basic or Stericson Busy-box.
Now, that is rooting. You might feel happy with it. However, if we restart the emulator, without snapshot, all the “su” does not work any more. So, we are going to customise the ROM image.
Failures
Now, if we restart the emulator, everything will return to default. No more “su” and Android Market. Why? The reason is because whatever we done to the /system, it will not save to the ROM image.
The /system is actually from the system.img, installed with android-2.2 in my case. This file is mounted in emulator as yaffs2 file system format. In order to customise this ROM image, I have tried several ways.
Using unyaffs, it can only extract the image, but I cannot continue. I can simply pull the /system using adb command without it.
Using yaffs2utils, unyaffs2 produced nothing. And the image built by mkyaffs2 does not allow the emulator to boot.
Using mkyaffsimage, also not work as above.
Some resources mentioned that, we can get the mkyaffs2image utility when building the Android source. But the problem is, to get the source, it requires a lot of disk space and need a long time to download.
So, what is the best way to modify the system.img? I even tried the low level way using dd to extract the /dev/block/mtdblock0, but failed.
Solution
Finally, I tried to solve it with userdata-qemu.img. This is the /data folder that will always modified when we install apps in the emulator. Restarting the emulator does not reset /data. Therefore, we can simply create the ROM image from /data. We can done it simply clean all the /data.
Code:
adb shell busybox rm -R /data/*
This will remove everything is /data, except “lost+found” folder.
Code:
adb shell busybox ls /data
Check with ls command, make sure only “lost+found” left.
Now, since the /system contains the “su”, “busybox”, Market and Google Services Framework we have done earlier, we need to copy the whole /system to the /data.
Code:
adb shell busybox cp -a /system/* /data/
adb shell busybox ls /data
As a result, the /data is identical to the /system.
Now, we have the userdata-qemu.img file in the AVD folder, which is modified. Close the emulator. Then, we can use the userdata-qemu.img file as the system image. We can rename it to system.img, or calling it as the system with “-system” option from the emulator command-line.
Start the emulator with this customised system.img, now, we have busybox by default, and also Android Market. :good::highfive:
Tip
If you are doing this on windows make sure you CD to here for issuing the commands:
%profilename%\AppData\Local\Android\android-sdk\tools
Don't use the stuff in C:\Program Files\Android. That is the wrong location.
The below gets your GAPPS too. You can download Cyanogens GAPPS to get what you need. Just edit the necessary lines below.
cd %profilename%\AppData\Local\Android\android-sdk\
.\tools\emulator -avd MyAndroid -partition-size 2047 -no-snapshot-load -verbose
echo wait for boot
pause
.\platform-tools\adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
.\platform-tools\adb push %~dp0platform-tools\su /system/xbin/
.\platform-tools\adb push %~dp0platform-tools\busybox /system/xbin/
.\platform-tools\adb shell chmod 06755 /system/xbin/su
.\platform-tools\adb shell chmod 06755 /system/xbin/busybox
.\platform-tools\adb shell busybox rm -R /data/*
.\platform-tools\adb shell busybox ls /data
.\platform-tools\adb shell busybox ls /data
.\platform-tools\adb push %profilename%\Downloads\gapps-ics-20120317-signed\system /system
.\platform-tools\adb shell busybox cp -a /system/* /data/
Which busybox binary?
You don't say which of the various busybox files in the .7z archive is to be used on the AVD?
I try to push the su, I got this message:
C:\adb>adb push sources\root\su /system/xbin
failed to copy 'sources\root\su' to '/system/xbin/su': Directory not empty
Then try push the Superuser.apk
C:\adb>adb push sources\root\system\app\Superuser.apk /system/app/Superuser.apk
failed to copy 'sources\root\system\app\Superuser.apk' to '/system/app/Superuser
.apk': Out of memory
I think that's because of this:
View attachment 1617834
How to make the System ROM space more freely???
----------------------------------------------------------------------------
Sorry for my noob question. Now, I see.
I have done untill rename userdata-qemu.img to system.img
But while I run from AVD Manager, my AVD got bootloop.
That's because you haven't started your emulator with additional space. Use the -partition-size option as per niranjan94's post above.
I found an even better way to make a /system image, and adapted it for use on Windows hosts and using the x86 emulator images now available.
References:
http://blog.thecobraden.com/2012/06/making-persistent-changes-to-android.html
http://code.google.com/p/android-group-korea/downloads/detail?name=mkfs.yaffs2.x86
Place this batch file in the same folder as the mkfs.yaffs2.x86 binary and you'll get an emulator image updated to your liking and ready to run.
Code:
@echo off
adb -e remount
echo Pushing mkfs.yaffs2.x86 to device...
adb -e push mkfs.yaffs2.x86 /data/local/
echo Executing chmod 770 /data/local/mkfs.yaffs2.x86
adb -e shell chmod 770 /data/local/mkfs.yaffs2.x86
echo Setting /system partition to read-only (Just to be safe!)
adb -e shell mount -o ro,remount /dev/block/mtdblock0 /system
echo Creating YAFFS2 image of /system
adb -e shell /data/local/mkfs.yaffs2.x86 /system/ /mnt/sdcard/_system.img
echo Pulling image to local directory...
adb -e pull /mnt/sdcard/_system.img
echo Cleaning....
adb -e shell rm /data/local/mkfs.yaffs2.x86
adb -e shell rm /mnt/sdcard/_system.img
echo OK
pause
Don't work on 4.2.2 emulator
Ι mean I push it, give permissions, install su.apk ... still nothing...
On 4.2.2 emulator
Hi,
I got the same error on 4.2.2 emulator.
So I tried with size 256:
emulator -avd Andy2 -partition-size 256 -no-snapshot-load
and it worked fine.
Also, I'm using CPU ARM (armeabi-v7a). So for busybox I used the binary from this thread:
http://forum.xda-developers.com/showthread.php?t=1380278
Error while trying to permanent patch rooted android
Hi,
While trying to root my android emulator where I delete all the files in the /data/ folder and copy files from /system/ to /data/, I am getting the following error,
Code:
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
Could anyone help me how to overcome this issue?
Hi,
i've followed your instructions step by step and didn't encounter any problems while executing the commands, but the emulator is not getting rooted according to the Root Checker app (see also the screenshot attached). Could you help me please to solve this issue?
Here is an enumeration of the commands I've entered into the console:
emulator -avd Huawei -partition-size 256 -no-snapshot-load
adb shell mount -o rw,remount -t yaffs2 /dev/block/mtdblock0 /system
adb push "C:\Users\Admin\Desktop\Superuser-3.0.7-efghi-signed\system\bin\su" /system/xbin/
adb push "C:\Users\Admin\Desktop\busybox binary\busybox" /system/xbin/
adb shell chmod 06755 /system/xbin/su
adb shell chmod 06755 /system/xbin/busybox
adb install "C:\Users\Admin\Desktop\Superuser-3.0.7-efghi-signed\system\app\Superuser.apk"
adb install "C:\Users\Admin\Desktop\Root Checker App.apk"
Hi,
I have the device created in AVD, started, but for the life of me I cannot open ADB:
Code:
[email protected]:~$ sudo adb devices
[sudo] password for joel:
List of devices attached
[email protected]:~$
What to I have to do to trick the virtual device in advertising ADB? Developer is on, USB debugging is on. Using a virtual device as closely matching the LG Optimus F3Q as I can recall (so API 16 / Android 4.1.2 loaded).
Many thanks.
EDIT: Figured it out. Need to use the adb provided in the Android SDK (in the platform-tools directory), not any other version (I was using the Debian-provided one).
Unable to root nexus 4 avd
I tried to root Nexus_4_API_21.avd (lollipop) following commands from the post exactly.
I used latest versions of superuser, and busybox.
But at the end emulator is not rooted.
Could someone help with with this, if you have rooted avd please share it so that I can download.
Thank you.
Regards
I tried to root with Lollipop, Kitkat, and even Gingerbread, but it doesn't work.
Under Lollipop and Kitkat, it's not rooted, but under Gingerbread, I can't install any application afterwards.
When I try to, the emulator looks like it reboots, but it never goes to the end, and keeps showing the Android logo glowing.
For android 4, 5 and 6 I write manual in russian. Read it here: http://4pda.ru/forum/index.php?showtopic=318487&view=findpost&p=45421931
Worked for me with AVD Lollipop and Marshmallow.
I am trying to make a simple shell script and I am getting constant errors.
So i made a test.sh file and saved it in /data because /sdcard is excuetable protected.
The shell file contains:
#!/system/bin/sh
cd /sdcard
mkdir test
su -c "rm /data/test.sh"
echo Done!
So then I typed the command chmod 777 /data/test.sh
I also tried chown root:shell /data/test.sh
And then /data/test.sh and it returned: tmp-mksh: /data/test.sh: No such file or directory
So then I tried running: sh /data/test.sh and it returned:
No such file or directoryrd
Done
I even tried executing the script from a root shell interface but still no luck same result as above.
Forgot to mention I am running 4.4.4 on a moto g that is rooted and has busybox installed.
I am trying to put a binary in ramdisk and execute that binary towards the end of kernel init to launch it from a seperate thread. But I am not able to launch the binary as the binary doesnt have execution permissions..So do you know how I can give execution permissions to a binary in ramdisk..like first stage android init in ramdisk..
What do you mean with ramdisk? My understanding of RAMDisk is that it's a segment or portion of system memory on your Android phone that is used as a disk drive. In essence, it is a virtual storage, created by software, from your device’s RAM chip.
Anyway here I show you how a binary is made executable, assumed device's Android is rooted and you can access it via ADB then
Code:
adb devices
adb shell "su -c 'cd / && mount -t auto -o rw,remount <MOUNT_POINT>'"
adb push <BINARY_FILE> <MOUNT_POINT>/
adb shell "su -c 'chmod 0755 <MOUNT_POINT>/<BINARY_FILE>'"
adb shell "su -c 'chown <USER>:<GROUP> <MOUNT_POINT>/<BINARY_FILE>'"
where <MOUNT_POINT> is the partition / dir that will house the <BINARY_FILE>, where <USER> and/or <GROUP> can be specified by name or by number.