Hi guys! I want to know how to have root permission on my Htc Hd Mini with NAND ROM CM9 RC2...
Thanks!
Repack boot.img, repack initrd and edit default.prop (change ro.secure=1 to ro.secure=0), pack initrd than pack boot.img again...done
munjeni said:
Repack boot.img, repack initrd and edit default.prop (change ro.secure=1 to ro.secure=0), pack initrd than pack boot.img again...done
Click to expand...
Click to collapse
Ok...so after I must to reinstall the rom?
fra18061988 said:
Ok...so after I must to reinstall the rom?
Click to expand...
Click to collapse
No! Just install only boot.img
Can you edit boot.img for me? I haven't software to unpack .img...is impossible for me...
My boot.img is attached in this post...
Thank you so much!!!!
You can do it using your recovery!
Procedure:
reboot to recovery
installing tools:
adb push unpackbootimg /
adb push mkbootimg /
adb push mkbootfs /
adb shell chmod 6755 /unpackbootimg
adb shell chmod 6755 /mkbootimg
adb shell chmod 6755 /mkbootfs
unpacking boot.img:
adb push boot.img /tmp/
adb shell
cd /tmp
/unpackbootimg -i boot.img
mkdir initr
cd initr
ls ../
gunzip < ../boot.img-ramdisk.gz | cpio -i --make-directories
cd ..
edit default.prop that is located in /tmp/initr (you can do it by adb push and adb pull... just for idea)!
/mkbootfs ./initr | gzip > initrd.gz
/mkbootimg --kernel boot.img-zImage --ramdisk initrd.gz --cmdline 'no_console_suspend=1 console=null' --base 0x12c00000 -o new_boot.img
and you are done, press ctrl+c to exit from adb, than:
adb pull /tmp/new_boot.img
Or if you want to install new boot.img:
adb push new_boot.img /
adb shell
erase_image boot
flash_image boot /new_boot.img
To repack boot.img I used Cygwin...but in default.prop, "ro.secure" is already set to ro.secure=0 ...see below
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=adb
So...root permission are on CM9 RC2
My big problem was to move applications like Facebook, Google Play etc...on SD Card. I solved the problem with Titanium Backup and Link2SD...
Related
So I posted a question yesterday to see if anyone could instruct me on how to root my phone using a MAC, no PC AT ALL. And then install CWM w/o having to use ODIN, b/c I do not have a PC. Well after some researching on my own I found out how and here is how I did it.
To root: Follow this thread (it requires using adb commands)
http://forum.androidcentral.com/ver...s/34188-rooting-using-mac-video-tutorial.html
To install CWM reference this thread, but here are the steps. You must download and install ROM Manager from market and also download zimage file. This also requires adb commands.
http://forum.xda-developers.com/showthread.php?t=804248
Copy zImage to the root folder of your SD Card
Open Terminal
$ cd (path to android sdk)/tools
$ ./adb push (path to redbend_ua)/redbend_ua /data/local
$ ./adb shell
$ cd /data/local/tmp
$ chmod 0755 rage.bin
$ ./rage.bin
(username)$ ./adb shell
# mount -t rfs -o remount,rw /dev/block/stl9 /system
# cd /data/local
# chmod 755 redbend_ua
# ./redbend_ua restore /sdcard/zImage /dev/block/bml7
--Phone Reboots--
$ ./adb shell
$ su
# cd /data/local
# ./redbend_ua restore /sdcard/zImage /dev/block/bml8
I know this is vague, but if you know what you are doing and reference the threads you should have no problem. Let me know if you have any questions.
This tutorial will show you how to root and install Overcome on Ubuntu:
Before we begin I'd like to give alterbridge86 a big thanks for creating the rom:
http://forum.xda-developers.com/showthread.php?t=932082
The author is not responsible for bla bla bla bla and damaging your tablet.
This tutorial is split into 4 sections:
Preparation
Rooting the Device
Flashing the Overcome Kernel with OC and UV support
Installing the rom
Before you begin:
sudo make coffee
======================
Preparation:
1.
Turn on usb debugging on the tablet before you connect the usb to the computer.
2.
Download the latest Overcome Rom which should be called Overcome vX.X.X Full Install:
http://forum.xda-developers.com/showthread.php?t=932082
3.
Mount your phone and place the file above in the root directory.
4.
Download the compressed file:
http://www.2shared.com/file/dILCeJ0W/Rootflashpkg.html
md5: 0beecbdee775ce08e03a829fc44759e1
sha1: 313151e027dd4e10214aca8660118c40d29c03d1
5.
Extract the compressed file, open up a terminal and cd to the folder.
(Thanks to CLShortFuse for providing the root files: http://forum.xda-developers.com/showthread.php?t=803682
======================
Rooting the device:
(Thanks to blacklevel: http://forum.xda-developers.com/showthread.php?t=859712
1.
Type these commands:
chmod +x adblinux
sudo ./adblinux push rageagainstthecage /data/local/tmp
sudo ./adblinux shell
cd /data/local/tmp
chmod 777 rageagainstthecage
./rageagainstthecage
sudo ./adblinux kill-server
sudo ./adblinux shell
mount -o remount,rw -t rfs /dev/block/stl9 /system
exit
sudo ./adblinux push busybox /system/bin
sudo ./adblinux push su /system/bin
sudo ./adblinux install Superuser.apk
sudo ./adblinux shell
chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/su
mount -o remount,ro -t rfs /dev/block/stl9 /system
exit
sudo ./adblinux reboot
======================
Flashing the Overcome Kernel with OC and UV support:
(Thanks to Koush: http://forum.xda-developers.com/showthread.php?t=870690)
1.
Download Overcome_Kernel_vX.X.X_OCUV_ODIN.tar from
http://forum.xda-developers.com/showthread.php?t=932082
2.
Extract the zImage file and place it in the Rootflashpkg directory.
3.
Type these commands:
chmod +x adblinux
sudo ./adblinux push flash_image /data/local/bin/flash_image
sudo ./adblinux push zImage /sdcard/
sudo ./adblinux shell
su
chmod 755 /data/local/bin/flash_image
/data/local/bin/flash_image boot /zImage
sync
exit
sudo ./adblinux reboot recovery
======================
Installing the Rom:
(Thanks to Mwa)
1.
You should already be in the recovery, but if not, press and hold the power and volume up button to get into recovery mode.
2.
Choose the "Install zip from sd card" option
3.
Choose "Choose zip from internal sd card" option
4.
Navigate and select the Overcome vX.X.X Full Install zip file.
Interesting... I just installed Overcome yesterday using Odin though... Here you are not suggesting Wipe & Restock... Any Camera issues after doing this?
I did not wipe but the option is available through Overcome's recovery mode that is flashed in this tutorial.
As for the camera issues, sounds like a hardware problem.
Hmm but it was working fine before .. Will try restocking and then see...thx for your response..
ravindrank said:
Hmm but it was working fine before .. Will try restocking and then see...thx for your response..
Click to expand...
Click to collapse
joohock from:
forums.whirlpool.net.au/forum-replies.cfm?t=1675443&p=7
Says:
"There have been reports of camera malfunctioning on that ocuv kernel. Try the no ocuv kernel."
OS Ubuntu 10.04 LTS x64
I downloaded photonic sources from schlund github place, ARM EABI Toolchain, get config from device(with schlund FW) and try to make, but have a error in makefile in "expr $(VERSION) \* 65536 + $(PATCHLEVEL) \* 256 + $(SUBLEVEL)); \". If i calculate version and write number to expr make done. I have zImage. Now i try to write new kernel to device. Get file boot.img from clockworkmod backup, "unpackbootimg -i boot.img", "mkbootimg --kernel zImage --ramdisk boot.img-ramdisk.gz --cmdline "no_console_suspend=1 console=null" --base 00200000 --pagesize 2048 -o ./tmp/boot.img" => have new boot.img. Through ADB push boot.img to sdcard then:
# cat /dev/zero > /dev/mtd/mtd2
write: No space left on device [this is ok, you can ignore]
# flash_image boot /sdcard/boot.img
Reboot device, but it write error in console(then i restore recovery and restore)
How to correctly build kernel and put it to the device?
Sorry for my bad english...
You not need bloksize argument for mkbootimg. And you have wrong argument for base (00200000 instead of 0x00200000)! Try:
- mkbootimg --kernel zImage --ramdisk boot.img-ramdisk.gz --cmdline 'no_console_suspend=1 console=null' --base 0x00200000 -o ./tmp/boot.img"
First, mount your sd card in recovery, then:
- adb push boot.img /sdcard/
than:
- adb shell erase_image boot
than:
- adb shell flash_image boot /sdcard/boot.img
It working also without mounting sdcard becouse boot.img is small and you are able to put it in memory, for example push it to /
- adb push boot.img /
- adb shell erase_image boot
- adb shell flash_image boot /boot.img
Can i "flash_image" In the booted android or just recovery?
will try to evening....
Just want to play with kernel...
YES!!!!!!!!!!!
It's work!!!!!!!!!!!!!!!!!!!!!!!!!
Thanx munjeni!!!!!!!!!!
Out of the 4 or so times I've successfully rooted the damn thing, I still am not 100% what I am doing right. Since each time I end up with a headache I've written myself a guide which seems to be almost always wrong along somewhere. I'm curious how wrong my latest discovery is. It seems when I use the 2.2.2 Android sbf I can't follow the usual directions listed on the wiki page. I need to run psneuter from another phone's root hack to give me "busybox, psneuter and su. Then I go back to install the bootmenu. Am I missing anything? Cheers:
II.C. Rooting
[EDIT:: It seems for Froyo 2.2.2 ("CEE sbf") you will probably need to follow the psneuter instructions:
http://wiki.cyanogenmod.org/wiki/LG_G2x:_Full_Update_Guide
Then go back and install bootmenu:
http://wiki.cyanogenmod.org/wiki/Motorola_Defy:_Full_Update_Guide ]
Is there anything else?
II.C.1. Connect Defy via USB and set it to "None." Open up terminal and begin pushing the files over:
Code:
$ adb push $PATH/TO/busybox /data/local/
i.e.
Code:
$ adb push /Users/kg/Android/android-sdk-macosx/platform-tools/busybox /data/local/
Push psneuter:
Code:
$ adb push $PATH/TO/psneuter /data/local/
… and su:
Code:
$ dab push $PATH/TO/su /data/local/
Now to change some permissions
Code:
$ adb shell chmod 777 /data/local/busybox
Code:
$ adb shell chmod 777 /data/local/psneuter
Enter into Defy and run psneuter by typing:
Code:
$ adb shell
Code:
$ /data/local/psneuter
Once the command finishes enter:
Code:
$ adb shell
"$" should now be "#."
Code:
# mount -o remount,rw -t ext3 /dev/block/mmcblk0p25 /system
Code:
# mkdir /system/xbin
Should the last command say, "mkdir failed for /system/xbin, File exists" let it be. It tried to create a directory but one with that name already exists. Just move along:
Code:
# /data/local/busybox cp /data/local/su /system/xbin/su
Code:
# chown 0:0 /system/xbin/su
Code:
# chmod 6755 /system/xbin/su
Code:
# ln -s /system/xbin/su /system/bin/su
Code:
# exit
One last push:
Code:
$ adb push $PATH/TO/Superuser.apk /system/app/Superuser.apk
Code:
$ adb reboot
Fin.
II.C.2.To Install the Bootmenu by connecting the Defy via USB, allow memory card access.
Drag and drop the bootmenu folder into the SD card
Rename it "bootmenu"
Eject the SD card and on the Defy set the USB mode to "None."
In Terminal start up adb:
Code:
$ adb shell
Now give it SuperUser permissions, enter the following then unlock the screen on the defy and select "allow":
Code:
$ su
The prompt "$" should now be "#."
Code:
# cp -R /sdcard/bootmenu /data/bootmenu
Code:
# cd /data/bootmenu
Code:
# chmod 755 *
Just let this command run the script to the end (when the user prompt, # is given)
Code:
# ./install.sh
Once finished, don't reboot yet:
Code:
# rm -R /data/bootmenu
Now do so:
Code:
# reboot
If you want to see if it worked, upon the first boot animation/logo watch for the LED to flash blue after a good few seconds. Press Volume-Down upon seeing the light. You should be in the bootmenu!
This method is similar to Chainfire's adbd Insecure, I tried Chainfire method, adb wireless didn't work for me, so I made my own, I needed to use adb wireless on some devices.
I made this adbd for my BLU Studio 5.0 C Cell phone, but I am sure it will work for other arm devices.
Anyway long story short, you need a rooted device, you push a script and an adbd file to /system/xbin then you add a line to /etc/install-recovery.sh to load the script each boot.
To install download replace_adbd.zip
extract zip place all three files on sdcard, and use rooted file manager to copy them to to their correct places, or use adb.
adb shell
mount -o rw,remount /system
adb push adbd /system/xbin/adbd
adb push adbd-Insecure /system/xbin/adbd-Insecure
adb push install-recovery.sh /system/etc/install-recovery.sh
adb shell
chmod 755 /system/xbin/adbd
chmod 755 /system/xbin/adbd-Insecure
chmod 755 /system/etc/install-recovery.sh
reboot
Or use file manager like ES File Explorer File Manager to copy files from sdcard to correct place and set permission then reboot.
https://www.androidfilehost.com/?fid=24052804347763661
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=1
ro.allow.mock.location=0
persist.mtk.aee.aed=on
ro.debuggable=0
ro.adb.secure=1
persist.sys.usb.config=mtp,adb
persist.service.acm.enable=0
ro.mount.fs=EXT4
ro.persist.partition.support=no
[email protected] STUDIO 5.0 C:/ #
credits
@carliv for CarlivScreenshot
http://forum.xda-developers.com/android/development/tool-carlivscreenshot-screenshots-t3075992
@Chainfire for the ideal of making adbd insecure
http://forum.xda-developers.com/showthread.php?t=1687590
Download link didn't sync correctly, file was corrupt first link, I have now changed the link, this one should now work correctly.
Thanks, I will test on my device and report back. I've always wanted some manual way instead of using the app.
@vampirefo
Is it possible to integrate in your batch the latest version of adbd demon get from adb insecuere 2.0.apk?
Is it possible to check the adbd version? How to?
Is it possible to create a dos batch with all need commands via adb commands? Like
adb shell mount -o rw,remount /system
adb push adbd /system/xbin/adbd
adb push adbd-Insecure /system/xbin/adbd-Insecure
adb shell cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
adb push install-recovery.sh /system/etc/install-recovery.sh
adb shell chmod 755 /system/xbin/adbd
adb shell chmod 755 /system/xbin/adbd-Insecure
adb shell chmod 755 /system/etc/install-recovery.sh
adb reboot
Thanks.
bovirus said:
@vampirefo
Is it possible to integrate in your batch the latest version of adbd demon get from adb insecuere 2.0.apk?
Is it possible to check the adbd version? How to?
Is it possible to create a dos batch with all need commands via adb commands? Like
adb shell mount -o rw,remount /system
adb push adbd /system/xbin/adbd
adb push adbd-Insecure /system/xbin/adbd-Insecure
adb shell cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.old
adb push install-recovery.sh /system/etc/install-recovery.sh
adb shell chmod 755 /system/xbin/adbd
adb shell chmod 755 /system/xbin/adbd-Insecure
adb shell chmod 755 /system/etc/install-recovery.sh
adb reboot
Thanks.
Click to expand...
Click to collapse
Yes, one can use the adbd binary from adb insecure 2.0.apk.
There isn't any version number to check, we both just build the adbd binary from source, mine was built from CM 12.1 source, not sure about chainfire's.
Chainfire's may have used AOSP source.
Yes one can create a Windows batch file, to execute the adb commands, or create a flashable zip, provided the devices has a custom recovery.
Sent from my Venue 8 3830 using Tapatalk