Guest Sami Beck Posted August 27, 2011 Report Posted August 27, 2011 Im Just wondering what you have to do to give root acess to a ROM that hasnt already got it, I dont mean just for the blade but for all android devices in general?
Guest plegdroid Posted August 27, 2011 Report Posted August 27, 2011 (edited) universal androot will work, you need to chk which one to use though, there's one version that will work upto android 2.2(1.6.2 beta 5) and another for above that. beta 6. Edited August 27, 2011 by plegdroid
Guest Sami Beck Posted August 27, 2011 Report Posted August 27, 2011 universal androot will work, you need to chk which one to use though, there's one version that will work upto android 2.2(1.6.2 beta 5) and another for above that. beta 6. no i mean so when you actaully flash the rom its prerooted.
Guest plegdroid Posted August 27, 2011 Report Posted August 27, 2011 misunderstood, sorry mate, all the custom roms for the racer their all hard rooted, was under the impression that all others would be too.
Guest KonstaT Posted August 27, 2011 Report Posted August 27, 2011 You need to do three things: -add/replace /system/bin/su (make sure that permissions are correct) -add /system/app/Superuser.apk -set ro.secure=0 in default.prop You need to unpack boot.img to edit default.prop. There might also be lines in init.rc that give wrong permissions to /system/bin/su.
Guest Sami Beck Posted August 27, 2011 Report Posted August 27, 2011 You need to do three things: -add/replace /system/bin/su (make sure that permissions are correct) -add /system/app/Superuser.apk -set ro.secure=0 in default.prop You need to unpack boot.img to edit default.prop. There might also be lines in init.rc that give wrong permissions to /system/bin/su. How do you unpack it? I can get it to be the zimage and the ramdisk if thats what you mean?
Guest t0mm13b Posted August 27, 2011 Report Posted August 27, 2011 How do you unpack it? I can get it to be the zimage and the ramdisk if thats what you mean? Konstat is referring to the ramdisk where it needs to be ungzipped and cpio'd gzip -dc boot.img-ramdisk.gz | cpio -i There you can get at the default.prop. Make the changes necessary, then, to repack it - mkbootfs ramdisk | gzip > new_ramdisk.gz B)
Guest KonstaT Posted August 27, 2011 Report Posted August 27, 2011 Yes, and here is good tutorial: http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack%2C_Edit%2C_and_Re-Pack_Boot_Images There is also a link to split_bootimg.pl that you need when you split boot.img to zImage and ramdisk.
Guest unrandomsam Posted August 27, 2011 Report Posted August 27, 2011 You need to do three things: -add/replace /system/bin/su (make sure that permissions are correct) -add /system/app/Superuser.apk -set ro.secure=0 in default.prop You need to unpack boot.img to edit default.prop. There might also be lines in init.rc that give wrong permissions to /system/bin/su. Permissions on su being 6755
Guest Sami Beck Posted August 27, 2011 Report Posted August 27, 2011 Permissions on su being 6755 what?
Guest t0mm13b Posted August 27, 2011 Report Posted August 27, 2011 what? He meant this chmod 6755 /system/bin/su That's from the adb shell command line.... B)
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now