Database Develop

noob guide for noob like me....

anyone kind enough to make a complete step by step noob guide on rooting, installing the SU and custom boot.img..... cause im lost in installing the SU and the custom boot img....thanks in advance for the guide.....

see here
http://www.androidworld.it/wiki/Root_HTC_Tattoo

can it be in english???

shazarul said:
can it be in english???
Click to expand...
Click to collapse
Hi,
see #237 post of the page 24 of this thread for what you want:
http://forum.xda-developers.com/showthread.php?t=635961
You need to collect the files: m7 at page 1, tattoo-hack.ko at page 23, and su at page 23. Just follow the sequence of #237.
Note that if you haven't pushed "su" to /data/local/bin, you can only execute the
Code:
while do /data/local/bin/m7 ; done
for first rooting, otherwise
Code:
/data/local/bin/su
At the first time to root it, you need to push the files to /data/local/bin, like:
Code:
----------- Your machine ----------------------------
adb push m7 /data/local/bin
adb push tattoo-hack.ko /data/local/bin
----------- Android Shell ----------------------------
adb shell
chmod 755 /data/local/bin/m7
while do /data/local/bin/m7 ; done
(find your first character of shell changing from $ to #, got root already.)
----------- Your machine ----------------------------
adb push su /data/local/bin/su
adb push su /sdcard
----------- Android Shell ----------------------------
export LD_LIBRARY_PATH=/system/lib
export PATH=/system/bin
mount -o rw,remount /dev/block/mtdblock3 /data
chown root.root /data/local/bin/su
chmod 4755 /data/local/bin/su
(and run the #237 procedure from step 7, insmod tattoo-hack.ko ......)
After the first time rooting, you can just type "su" to enter root again. If not, you need to do the #237 procedure from step 1 to last.

thanks guys for the help.....finally root my fone.....

[GUIDE] Steps to root stocked Nexus One android without flashing(unlocked bootloader)

Disclaimer 1 : I tried to look for something like this but I did not found it. Then I tried to achieve it. Sorry if they are well known steps
This guide allows to root a Nexus One with unlocked bootloader with NO need to flash recovery
USE THAT INFORMATION AT YOUR RISK!!
Updated: Added a line to work with Gingerbread
That steps are for Ubuntu. If you are any interested windows user, please let me know.
Prerequisites:
Unlocked bootloader
adb working properly
1. Download fastboot
Code:
wget --referer=http://developer.htc.com/adp.html http://dl4.htc.com/RomCode/ADP/fastboot.zip
unzip fastboot.zip
chmod u+x fastboot
rm fastboot.zip
2. Obtain busybox (anyone have any direct link?) - NOT GOING TO FLASH CM, JUST GETTING busybox from a trusted place
Code:
wget http://download.cyanogenmod.com/get/update-cm-7.0.0-N1-signed.zip
unzip update-cm-7.0.0-N1-signed.zip system/xbin/busybox
rm update-cm-7.0.0-N1-signed.zip
3. Download su
-- UPDATE: that link broken, you have to donwload it from Google Play
Code:
wget http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
unzip su-2.3.6.1-ef-signed.zip system/app/Superuser.apk system/bin/su
rm su-2.3.6.1-ef-signed.zip
4. Download recovery-RA - NOT GOING TO FLASH IT, DON'T WORRY!!!
Code:
wget -O recovery-RA-passion-v2.2.1.img http://files.androidspin.com/files/amon_ra/RECOVERY/recovery-RA-passion-v2.2.1.img
md5sum recovery-RA-passion-v2.2.1.img
echo ... Validate md5sum is 3def709ab1c9e051a92a1c8b1504a36a
5. Reboot to bootloader - JUST BOOTING WITH, NO FLASHING
Code:
adb devices
adb wait-for-device
adb reboot-bootloader
fastboot boot recovery-RA-passion-v2.2.1.img
echo ... Waiting for recovery image load
while [ -z `adb shell pwd 2> /dev/null` ]
do
sleep 1
done
6. Root it!
Code:
adb shell mount /system
adb push system/xbin/busybox /system/bin/busybox
adb shell chmod 4755 /system/bin/busybox
adb push system/bin/su /system/bin/su
adb shell chmod 4755 /system/bin/su
adb push system/app/Superuser.apk /system/app/Superuser.apk
adb shell chmod 4755 /system/app/Superuser.apk
7. Reboot and enjoy rooting
Code:
adb shell reboot

Will this work on stock Gingerbread?

If you are running Nexus One with Gingerbread, as I understand, it can work. I've not tried, you can try.... at your risk ;-)

Helleqn said:
Will this work on stock Gingerbread?
Click to expand...
Click to collapse
If you have an unlocked bootloader, yes, it will work. If you have an unlocked bootloader, you can install pretty much anything you want, whenever you want...
Sent from my Nexus One using XDA Premium App

Helleqn said:
Will this work on stock Gingerbread?
Click to expand...
Click to collapse
I've added a adb command (mount /system) to work with Gingerbread. It works on mine.

It also works on 2.3.4

Yep. Worked great for me. But with all due respect, it seemed a little fishy to me that your directions have users pull busybox from Cyanogenmod but then have them pull su and Superuser.apk from a random file on a Dropbox account especially since both files are available in the already trusted Cyanogenmod download that was used for busybox. And even more so because the Superuser.apk file using your instructions is a larger file than the one included with Cyanogenmod. So I only used the files from CM and it worked like a charm.
Not accusing you or anything. I'm just pointing that out.

The easier way is to do step 5, then flash the su zip from step 3, and you're pretty much done. You can install busybox through the Market app...

Don't worry for the link, I toke it from the original post for that su release:
http://forum.xda-developers.com/showthread.php?t=682828
I agree it's enough with CM but I intend to get the last version... may be it's not the best option...
Thanks for your comments.

[ROOT] Linux command lines if SuperOneClick fails

Hi.
I've tried many times to root my LG2X with Z4root, UniversalAndRoot, Visionary and SuperOneClick since I've bought it but it failed each time.
I've seen the [Root] topic in the developpement thread but I can't post there (less than 10 posts...) but I want to help someone to root his/her mobile.
I've searched a long time a good way to do so without SuperOneClick (which doesn't respond with Windows Seven or Ubuntu 11.04) but there is none.
There we go...
Disclaimer : I can't be responsible if you break your phone, cancel your warranty or launch your LG2X on the wall in rage.
If you want, there is already SuperOneClick which run smoothly for many geeks : LG2X SuperOneClick Forum and SuperOneClick Forum
My HTC Magic had been rooted with the command line and I've tried myself to do so with every bit of informations and tips I could find on Internet.
I recommand to test the SuperOneClick method and if it fails, come test this with a Linux terminal (psneuter, su-v2, busybox and the SuperUser.apk can be found in the SuperOneClick archive) :
Code:
adb push psneuter /data/local/tmp
adb push su-v2 /data/local/tmp
adb push busybox /data/local/tmp
adb shell
$ busybox chmod +x /data/local/tmp/psneuter
$ /data/local/tmp/psneuter
adb remount
adb shell
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
# busybox chmod 6755 /system/xbin/su
# busybox chown 0.0 /system/xbin/su
# busybox cp /system/xbin/su /system/bin/su
# busybox chown 0.2000 /system/bin/su
# busybox cp /data/local/tmp/busybox /system/xbin
# busybox chmod 0755 /system/xbin/busybox
# busybox chown 0.2000 /system/xbin/busybox
# exit
adb install Superuser.apk
adb reboot
And... Normally you have permanent root on your LG2X.
You can check the files permissions with
Code:
ls -l /system/xbin/su /system/bin/su
-rwsr-sr-x root root 26264 2011-04-23 20:07 su
-rwsr-sr-x root shell 26264 2011-04-23 23:20 su
It seems that /system/xbin/su isn't necessary at all. The su command which gave you the root is the one in /system/bin/. And I had some problems with /system/xbin, I've deleted the folder (with rm /system/xbin or mv /system/xbin /dev/null, I can't recall) and applied mkdir on it again.
If this can be of help, I'll update this later.

thanks for the detailed instructions, but super one click definitely works with win7 (64bit too) as long as you have the right drivers installed

Thanks but with Windows Seven 64 bits, Linux ou Windows Seven 32 bits with Virtualbox I end up with "SuperOneClick doesn't respond" or stuck on with "chmod psneuter" (with the drivers properly installed).
It's only an alternative solution if SuperOneClick doesn't run properly for another guy.

Thanks a lot for that tips.
The problem I have now is that su isn't persistant.
When I use
$ su
It hangs up few seconds... and says "Permission denied"
I've used su-v2
Here are the su permission :
-rwsr-sr-x root shell 26324 2011-02-13 14:43 su
Is there a more up-to-date su, that will maybe fix the problem ?
Thanks.
EDIT :
Ok.
The wait time seems to come from SuperUser, I've removed it.
Now I have directly the "permission denied", and "stat failed with 2: No such file or directory" in the logcat.
Maybe that can help.

Hannes The Hun said:
thanks for the detailed instructions, but super one click definitely works with win7 (64bit too) as long as you have the right drivers installed
Click to expand...
Click to collapse
It didn't for me (after installing nightly 51)
With the step-by-step instructions I get "Failed to set prot mask (inappropriate ioctl for device)" when trying to execute psneuter.

Hi.
Sorry for the wait.
Have you resolved your problem with your rooting?

Rooting/unlocking Nexus One with broken power button using Linux terminal tools

I am attempting to get Cyanogenmod onto my Nexus One, but am running into far more problems than expected. The information on rooting Android devices seems heavily fragmented across the web and the tools unreliable. At least in my case, SuperOneClick has proven a complete misnomer. So I'd like to go back to basics - executing as many of the commands as possible from a Linux terminal to get the phone rooted/unlocked/whatever else has to happen to get Cyanogenmod installed. The two constraints I'm working with here are as follows:
1. The device is running Android 2.2.1 (I downgraded from 2.3.x using the PASSIMG method).
2. The power button on the device is broken, so any method which requires pressing/holding it is ruled out.
The problem I am having is that even after following Linux-centric guides, I get to the point of installing the SuperUser app followed by the ROM Manager app, but I'm never prompted to give ROM Manager superuser permissions and so can't flash the ClockworkMod recovery.
Below I describe the steps I've been taking so far, based on the "How To Root Nexus One Running Android 2.2.1 From Ubuntu Linux" guide (Google it, I can't post hyperlinks).
- Download/extract/move Nexus One Softroot files to same directory as adb
- From adb directory, execute the following commands:
sudo ./adb push psneuter /data/local/tmp/psneuter
sudo ./adb push busybox /data/local/tmp/busybox
sudo ./adb push su /data/local/tmp/su
sudo ./adb shell chmod 755 /data/local/tmp/psneuter
sudo ./adb shell chmod 755 /data/local/tmp/busybox
sudo ./adb shell chmod 755 /data/local/tmp/su
sudo ./adb shell cd /data/local/tmp ./psneuter
sudo ./adb shell
After executing sudo ./adb shell as above, I get the # prompt, which is purported to indicate that rooting was successful.
- Still following the guide, I then execute the commands which purportedly make root permanent:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /data/local/tmp
./busybox cp busybox /system/bin
chmod 4755 /system/bin/busybox
busybox cp su /system/bin
chmod 4755 /system/bin/su
exit
exit
- Again, still following the guide, I execute the commands which purportedly set the /system partition back to read-only:
sudo ./adb shell
su
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
exit
exit
- Now, I download the SuperUser app from the Android Market and open it to make sure it's running.
- Next, I download the ROM Manager app from Google Play (looks like it pulled a sneaky and upgraded from Android Market to Google Play here).
- I run ROM Manager and choose Flash ClockworkMod Recovery. I'm prompted to confirm the phone is a Google Nexus One and then ROM Manager runs for about 30 seconds (yellow program bar goes all the way) before spitting out An error occurred while attempting to run privileged commands!. And this is the point I am stuck at.
I should note that at no point am I prompted by the SuperUser app to give the ROM Manager app super user permissions. I don't restart the phone or do anything else throughout all of the steps I've described above, so I can't see any reason for root to have been lost at any point. In fact, if I execute the command sudo ./adb shell after all this, I still get the # prompt indicating root. And when I execute id afterwards, I get uid=0(root) gid=0(root) -- further confirmation of root. I really am stuck on this one. I've spent a lot of time digging through forum posts and online articles, but the signal to noise ratio is poor and I haven't been able to find anything that actually works. Can someone suggest where I am going wrong?

Programs might expect su to be in /system/xbin rather than /system/bin, which is probably your case.
Also, use SuperSU instead of Superuser.
Also, make sure the su you're using is matching the relevant control program - which means, downloading Superuser from the Play Store won't help, if it can't work with the binary you have. So download a complete ZIP from XDA with SuperSU.apk and su binary, and use those. The last version I used was 0.89 and it was on XDA just like I described above.

interesting problem with ez fix, get new phone. n1's are $100 on ebay, thats how i got mine.

[Q] Help unlocking bootloader w or w/o HTCdev

I've got a dilemma where my HTC One's volume rocker doesn't work properly (the volume down button seems to work when it's convenient while the volume up never works). So when I get to the screen where it asks me to confirm the unlocked bootloader, I can't confirm it at all. I've looked into other methods and revone seems to be the most promising. I tried it yesterday and got the error "segmentation fault". Is there another method to unlocking the bootloader aside from HTCDev or a workaround to the volume button problem?

Gigaman92 said:
I've got a dilemma where my HTC One's volume rocker doesn't work properly (the volume down button seems to work when it's convenient while the volume up never works). So when I get to the screen where it asks me to confirm the unlocked bootloader, I can't confirm it at all. I've looked into other methods and revone seems to be the most promising. I tried it yesterday and got the error "segmentation fault", which I found a solution to. Before I try this solution, however, I want to know, is there an easier method?
Click to expand...
Click to collapse
1st method to unlock bootloader is from htcdev.com which will require your volume button to works.
2nd method require s-off either by using the guru bootloader tool or using dd commands

alray said:
1st method to unlock bootloader is from htcdev.com which will require your volume button to works.
2nd method require s-off either by using the guru bootloader tool or using dd commands
Click to expand...
Click to collapse
I'll look into Guru a bit more. I might be able to use it but I'm not sure yet.

Sorry for the bump. I looked into the Guru bootloader tool and it says I need S-Off as a prerequisite. Revone should be capable of giving me S-off as my HTC One's HBOOT version is 1.44. and its software version is 1.26.502.15. However, I get the Segmentation fault error when I try to run revone. I've read that HBOOT should be dated for May 2013 but mine is dated for July 2013 so that might be why revone doesn't work.
Are there any other solutions to my problem?

Gigaman92 said:
Sorry for the bump. I looked into the Guru bootloader tool and it says I need S-Off as a prerequisite. Revone should be capable of giving me S-off as my HTC One's HBOOT version is 1.44. and its software version is 1.26.502.15. However, I get the Segmentation fault error when I try to run revone. I've read that HBOOT should be dated for May 2013 but mine is dated for July 2013 so that might be why revone doesn't work.
Are there any other solutions to my problem?
Click to expand...
Click to collapse
You can try to revone using a terminal emulator on your phone. Download a terminal emulator from the Play Store, then follow these steps:
 Download the Revone file and transfer it to your phone (or download on your phone)
 Use a root file explorer and paste the file inside the /data/local/tmp folder
 Open a terminal emulator and type of the following:
 su (enter)
cd /data/local/tmp (enter)
chmod 755 revone (enter) (IF revone doesn’t work, type revone.bin)
./revone -P (enter)
 Reboot
 Open terminal again and type:
 su (enter)
cd /data/local/tmp (enter)
./revone -s 0 -u (That would be a ZERO) (enter)
 Reboot
 That’s it!

majmoz said:
You can try to revone using a terminal emulator on your phone. Download a terminal emulator from the Play Store, then follow these steps:
 Download the Revone file and transfer it to your phone (or download on your phone)
 Use a root file explorer and paste the file inside the /data/local/tmp folder
 Open a terminal emulator and type of the following:
 su (enter)
cd /data/local/tmp (enter)
chmod 755 revone (enter) (IF revone doesn’t work, type revone.bin)
./revone -P (enter)
 Reboot
 Open terminal again and type:
 su (enter)
cd /data/local/tmp (enter)
./revone -s 0 -u (That would be a ZERO) (enter)
 Reboot
 That’s it!
Click to expand...
Click to collapse
Thanks for the help. However, revone will not work with my phone. Using weaksauce, I was able to root the phone. I tried revone with the phone rooted and got Error 6, so apparently my HBOOT 1.44 is patched. I'm going to try using firewater a bit later today. Wish me luck.