Firstly i did not do this guide. it took it from this forum and just compile so that newbie like me can easily root their tattoo.....
ROOTING TATTOO
Download the ZIP file attached to this post. Extract the files to a safe location - perhaps C:\Tattoo ?
Now, you'll need adb for windows. You can get it from COBURN website's server here: ADB for windows.
Make sure your device is in USB Debug Mode (Settings > Applications > Development).
Extract all the files in the adb4win zip file to your C:\Tattoo folder.
Now, go to Command Prompt. In XP, it's under System Tools in Accessories. In Vista/7, it'll be under accessories.
Do the following at the command line:
C:\Users\Coburn> cd C:\Tattoo
Then you will get this C:\Tattoo
Next type in this:
C:\Tattoo> adb-windows shell "mkdir /data/local/bin" (with the quotes!).
If you get a error (like mkdir failed, file/folder exists), this is fine!
just means that the folder already exists in your phone
Now, run this command:
C:\Tattoo> adb-windows push m7 /data/local/bin/m7
this will just take a few seconds
Run this:
C:\Tattoo> adb-windows shell "cd /data/local/bin && chmod 755 ./m7" (with the quotes!)
This allows you to run the sucker. Looks like something nothing happen but it did something.
C:\Tattoo> adb-windows shell
This will dump you at a "$" shell. do the following:
C:\Tattoo> adb-windows shell
$ cd /data/local/bin
$ while ./m7 ; do : ; done
...lotsa text will flow down your screen. This is normal.
Soon, you'll be greeted with this:
#
This is the root prompt! If you get stuff like this:
# usage: reboot ...
usage: reboot ....
usage: reboot ...
Just keep your cool, press enter and the # will pop again. This is due the exploit spawning reboots to gain the shell.
Next type in this:
export LD_LIBRARY_PATH=/system/lib
export PATH=/system/bin
Check if u have root, type:
id
you will get
# id
uid=0(root) gid=1000(shell) groups=1003(graphics),1004(input),1007(log),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
The uid=0(root) is important, so call your phone is root.
REMOUNT PARTITION (SU)
Now you need to install su. Exit your root shell (via CTRL+C) and download this su.zip and extract it to C:\Tattoo.
DO NOT EXIT THE COMMAND PROMPT WINDOW.
in your command prompt window, do this:
C:\Tattoo> adb-windows push su /data/local/bin/su
Then break out a shell...
C:\Tattoo> adb-windows shell
at the $ prompt, enter:
$ chmod 755 /data/local/bin/su
$ cd /data/local/bin/
$ while 'true' ; do ./m7 ; done
It will change from $ to #
Type in this:
export LD_LIBRARY_PATH=/system/lib
export PATH=/system/bin
Next type in this:
# chown root.root /data/local/bin/su
# chmod 4755 /data/local/bin/su
# mount -o rw,remount /dev/block/mtdblock5 /data
# mount -o rw,remount /dev/block/mtdblock3 /system
After that, you can exit out of the root shell, and try a normal shell and this:
$ /data/local/bin/su
...which should make you get a nice # prompt.
Custom Boot.img:
Boot img v2:http://forum.xda-developers.com/show...0&postcount=38
Tattoo-hack.ko:http://forum.xda-developers.com/atta...2&d=1266670581
Download this flash_image:http://forum.xda-developers.com/attachment.php?attachmentid=287463&d=1267386499
adb push flash_image ./data/local/bin/flash_image
adb push Mainfram3.boot.02.img /sdcard/Mainfram3.boot.02.img
adb push tattoo-hack.ko ./data/local/bin/tattoo-hack.ko
c:\tattoo>adb shell
$ su
su
su: access granted, courtesy of www.magicandroidapps.com
# insmod /data/local/bin/tattoo-hack.ko
#mount -o rw,remount /dev/block/mtdblock5 /data
#mount -o rw,remount /dev/block/mtdblock3 /system
#chmod 755 /data/local/bin/flash_image
#/data/local/bin/flash_image boot /sdcard/Mainfram3.boot.02.img
Cutom Recovery Img:
After custom boot.img
adb push TCRI.alpha.img /sdcard/TCRI.alpha.img
c:\tattoo>adb shell
#/data/local/bin/flash_image recovery /sdcard/TCRI.alpha.img
once again i did not make the guide...i only compile it from different thread and put them as 1....tats all....thanks to all the devs that came up with the guide.....
hi!
will be possible flash official ROM made HTC after rooting proces?
I'm totaly new to this android applications
correct me if im wrong...you can always flash official rom frm htc for that paticular phone model....whether root or not....
the flash image no longer exists...
@Bikers
Download here:http://forum.xda-developers.com/attachment.php?attachmentid=287463&d=1267386499
@shazarul
Correct the link in the post.
c:\tattoo>adb shell
$ su
su
su: access granted, courtesy of www.magicandroidapps.com
i get permision denied! I know there is somewhere else a thread like this but i jus t can't find it...
try it with root 1 click by maverixx
have change the flash_image link..... biker i think u have to root it again???/ i think should b the easy way out....
just flashed custom boot img using this tutorial, thanks !
Thanks a lot, but I have a problem.
When I get to:
Code:
adb push Mainfram3.boot.02.img /sdcard/Mainfram3.boot.02.img
I get this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I had the same problem with http://forum.xda-developers.com/showthread.php?t=644279&page=6 1 click root script when pushing to /sdcard...
have you tried to put it directly in your sd card? Did you putted your phone in MSSync at the usb options?
try to unmount sdcard from the phone, with the command in the notification bar of the tattoo
i am having this error while flashing custom recovery image ...
# /data/local/bin/flash_image boot /sdcard/Mainfram3.boot.02.img
/data/local/bin/flash_image boot /sdcard/Mainfram3.boot.02.img
error opening /sdcard/Mainfram3.boot.02.img: No such file or directory
#
Click to expand...
Click to collapse
where am i getting it wrong ??? till that i have no issues in following tutorial...
please help me...
chtamina said:
try to unmount sdcard from the phone, with the command in the notification bar of the tattoo
Click to expand...
Click to collapse
this suggestion solved my problem.... thanks chtamina..... you made my day...
Related
I'm running one-click root, unleash the beast, circle battery and ext2 lag fix. Unleash the beast updated my hosts file to block ads but unfortunately also blocks the Audiogalaxy servers which I'd like to use for their new streaming app.
Trying to edit the hosts file I did an adp pull to my PC, edited the file and saved. But I can't push it back to /system/etc/hosts as I get a "permission denied" error.
After some reading it seems this means my root directory doesn't mounted with write permissions. I tried "adb root" but it gives me error "cannot run as root in production builds" and tried "adb remount" but that gives me error "remount failed: No such file or directory". I'm stuck at this point.
Any ideas? Could this be because I'm running the ext2 lag fix?
phishie said:
I'm running one-click root, unleash the beast, circle battery and ext2 lag fix. Unleash the beast updated my hosts file to block ads but unfortunately also blocks the Audiogalaxy servers which I'd like to use for their new streaming app.
Trying to edit the hosts file I did an adp pull to my PC, edited the file and saved. But I can't push it back to /system/etc/hosts as I get a "permission denied" error.
After some reading it seems this means my root directory doesn't mounted with write permissions. I tried "adb root" but it gives me error "cannot run as root in production builds" and tried "adb remount" but that gives me error "remount failed: No such file or directory". I'm stuck at this point.
Any ideas? Could this be because I'm running the ext2 lag fix?
Click to expand...
Click to collapse
did you type in su before using pushing the file?
Edit: it would be like this
su (press enter)
adb push blah*
tytdfn said:
did you type in su before using pushing the file?
Edit: it would be like this
su (press enter)
adb push blah*
Click to expand...
Click to collapse
Yea I had tried that. "su" by itself is not a recognized command. "adb su" just prints the adb help text (lists commands).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Ok maybe I need to simplify my question:
Does anyone know how to get the root directory to mount to USB with write permissions?
This is what I use to put things in and out of /system/. Haven't a clue what most of the commands mean, but it works for me all the time.
(You have to be root'd)
Code:
First, put the file on your desktop.
adb push %userprofile%\desktop\<filename> /sdcard
adb shell
su
mount -o rw,remount /system
rm /system/.../<filename>
busybox mv /sdcard/<filename> /system/...
Hope that helps.
MikeyMike01 said:
This is what I use to put things in and out of /system/. Haven't a clue what most of the commands mean, but it works for me all the time.
(You have to be root'd)
Code:
First, put the file on your desktop.
adb push %userprofile%\desktop\<filename> /sdcard
adb shell
su
mount -o rw,remount /system
rm /system/media/<filename>
busybox mv /sdcard/<filename> /system/media
Hope that helps.
Click to expand...
Click to collapse
Cool I'll try that, are you running any lag fixes by chance?
phishie said:
Cool I'll try that, are you running any lag fixes by chance?
Click to expand...
Click to collapse
Yeah, the one that come in the old SuperRooter.
MikeyMike01 said:
This is what I use to put things in and out of /system/. Haven't a clue what most of the commands mean, but it works for me all the time.
(You have to be root'd)
Code:
First, put the file on your desktop.
adb push %userprofile%\desktop\<filename> /sdcard
adb shell
su
mount -o rw,remount /system
rm /system/.../<filename>
busybox mv /sdcard/<filename> /system/...
Hope that helps.
Click to expand...
Click to collapse
Permission denied when trying to push to /sdcard.
MikeyMike01 said:
This is what I use to put things in and out of /system/. Haven't a clue what most of the commands mean, but it works for me all the time.
(You have to be root'd)
Code:
First, put the file on your desktop.
adb push %userprofile%\desktop\<filename> /sdcard
adb shell
su
mount -o rw,remount /system
rm /system/.../<filename>
busybox mv /sdcard/<filename> /system/...
Hope that helps.
Click to expand...
Click to collapse
By the way this worked perfectly once I realized I needed to physically approve the "su" request on the phone. Thanks again.
Stupid me go back to the stock rom and upgraded to 2.2.1 and lost the root. Ive been trying all day today by following the instruction from this tutorial(http://forum.xda-developers.com/showthread.php?t=736271) but im stuck at the rootshell command. its says permission denied. Can some one please help me..please.. is there any way to root this FRG83, please??
This method does not work anymore.. you have to go a different method..
you can try this method
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp/
adb shell
$chmod 700 /data/tmp rageagainstthecage
exit
go to sdk/tools
/tools>freenexus.bat
adb shell
$cd data/local/tmp
ls
check if all files are in
rage
su
Superuser.apk
busybox
$./rageagainstthecage
743C[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3084, 3084}[*] Searching for adb ...
[+] Found adb as PID 64[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] 7-4-3-C[at]web.de so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.
DONT TYPE ANYTHING TILL YOU HERE THE ADB ON PHONE RESTARTS.
C:/adb kill-server
C:/adb start-server
adb shell
#
should get pound sign if not run ragecage again and dont do anything to you here the last ding on computer
#cd /data/local/tmp
#./busybox cp busybox /system/bin/
(if get read-only error do this
mount -o remount,rw /dev/block/mtdblock3 /system)
#chmod 4755 /system/bin/busybox
#./busybox cp Superuser.apk /system/app
#./busybox cp su /system/bin/
#chmod 4755 /system/bin/su
#exit
if $ type exit again
then go into terminal on phone, and type su
if you get the # you have root once again! yay!
now to install busybox command
adb shell
$su
#cd /sdcard
#sh ./installbusybox.sh
thats it
i dont have files i will upload in a bit before i have to go
ok for busybox installing on phone..
put installer.sh
and busybox on root of sdcard
then follow rest of instructions..pretty simple
put su,busybox,and all the freenexus stuff in sdktools
http://www.mediafire.com/file/nm7k71ofdgltk5g/root.rar
ilostchild said:
This method does not work anymore.. you have to go a different method..
you can try this method
Code:
adb push rageagainstthecage-arm5.bin /data/local/tmp/
adb shell
$chmod 700 /data/tmp rageagainstthecage
exit
go to sdk/tools
/tools>freenexus.bat
adb shell
$cd data/local/tmp
ls
check if all files are in
rage
su
Superuser.apk
busybox
$./rageagainstthecage
743C[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3084, 3084}[*] Searching for adb ...
[+] Found adb as PID 64[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] 7-4-3-C[at]web.de so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.
DONT TYPE ANYTHING TILL YOU HERE THE ADB ON PHONE RESTARTS.
C:/adb kill-server
C:/adb start-server
adb shell
#
should get pound sign if not run ragecage again and dont do anything to you here the last ding on computer
#cd /data/local/tmp
#./busybox cp busybox /system/bin/
(if get read-only error do this
mount -o remount,rw /dev/block/mtdblock3 /system)
#chmod 4755 /system/bin/busybox
#./busybox cp Superuser.apk /system/app
#./busybox cp su /system/bin/
#chmod 4755 /system/bin/su
#exit
if $ type exit again
then go into terminal on phone, and type su
if you get the # you have root once again! yay!
now to install busybox command
adb shell
$su
#cd /sdcard
#sh ./installbusybox.sh
thats it
i dont have files i will upload in a bit before i have to go
ok for busybox installing on phone..
put installer.sh
and busybox on root of sdcard
then follow rest of instructions..pretty simple
put su,busybox,and all the freenexus stuff in sdktools
http://www.mediafire.com/file/nm7k71ofdgltk5g/root.rar
Click to expand...
Click to collapse
man thanks alot for your help, but im really a noob.
wud u mind telling me step by step, i know it sounds pretty stupid but pls just guide in the right direction. Much appreciated.
Ouch. I hope you can laugh about this one day. I'm sure you'll have root again.
Have you ever heard the term "curiosity kills the cat".
You knew enough to get root, revert to stock so that you could apply 2.2.1, to discover the hard way that the .1 was mainly, if nothing more than a security patch locking out root. And now need coles notes for above. Sorry, that'll be funny after you have root again.
In the meantime, I hope you find solace in paving the road for future noobs starting new from 2.2.1.
Anyway, the majority of the guide above are sequences while in ADB. You had to use some adb to get
root the first time. Google and do a little research on the subject. You need to polish up as I think the warnings above about "don't do anything until", are warnings to avoid bricking. If this procedure is that risky then your ounce of comprehension is worth a ton of hand holding.
Sent from my Nexus One using XDA App
read this thread first
my instructions are the same just more detailed..
and yes gotto do this thru adb
so you get the ragecage arm5
and go to android sdk/tools> and from there do adb push.. and im sure you can do the rest
ilostchild said:
my instructions are the same just more detailed..
and yes gotto do this thru adb
so you get the ragecage arm5
and go to android sdk/tools> and from there do adb push.. and im sure you can do the rest
Click to expand...
Click to collapse
ijust wanted to know which files to download and where to extract themm.. just lik ehow it was mentioned in the freenexus thread, it was defined so clear which fuiles to download and where,,.
Can anyone please help. thanks.
Loveact's post links you to a thread with multiple victims of the patch, links and details to get back root.
Sent from my Nexus One using XDA App
Detailed step-by-step instructions
nexusdue said:
Detailed step-by-step instructions
Click to expand...
Click to collapse
ok so i tried last nite several time but im stuck at the part after
$./rageagainstthecage
its says not found
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what am i suppose to do now, I am stuck. All my files are in the tools folder
I need your help, please help me out.
If you are running windows, did you run freenexus.bat? I think that step was not mentioned unless u looked at the readme file in the freenexus.zip files.
kpjimmy said:
If you are running windows, did you run freenexus.bat? I think that step was not mentioned unless u looked at the readme file in the freenexus.zip files.
Click to expand...
Click to collapse
Do I have to double click it and run iton windows before i start the process??
is that what you mean??
junooni.1980 said:
ok so i tried last nite several time but im stuck at the part after
$./rageagainstthecage
its says not found
what am i suppose to do now, I am stuck. All my files are in the tools folder
I need your help, please help me out.
Click to expand...
Click to collapse
Congrats for not following the instructions.
nexusdue said:
Congrats for not following the instructions.
Click to expand...
Click to collapse
i did man.. can some one help me then dunno what am i m issing.. here pls.
Looks like you don't have the rageagainstthecage binary on your phone.
Doing 'adb shell ls -l /data/local/tmp' on your computer should get you something like this:
Code:
-rwxrwxrwx shell shell 5392 2010-08-25 01:42 rageagainstthecage-arm5.bin
-rwxr-xr-x shell shell 1926944 2010-03-22 20:29 busybox
-rwxrwxrwx shell shell 26248 2010-07-22 10:20 su
-rwxrwxrwx shell shell 27688 2010-07-22 10:19 Superuser.apk
There might be some other files in there; it's these that matter. If you don't see them then do all the 'adb push' and 'adb shell chmod' stuff in the previously linked instructions.
Egypt Urnash said:
Looks like you don't have the rageagainstthecage binary on your phone.
Doing 'adb shell ls -l /data/local/tmp' on your computer should get you something like this:
Code:
-rwxrwxrwx shell shell 5392 2010-08-25 01:42 rageagainstthecage-arm5.bin
-rwxr-xr-x shell shell 1926944 2010-03-22 20:29 busybox
-rwxrwxrwx shell shell 26248 2010-07-22 10:20 su
-rwxrwxrwx shell shell 27688 2010-07-22 10:19 Superuser.apk
There might be some other files in there; it's these that matter. If you don't see them then do all the 'adb push' and 'adb shell chmod' stuff in the previously linked instructions.
Click to expand...
Click to collapse
what is Doing 'adb shell ls ((-l /data/local/tmp' ))on your computer should get you something like this: i meant what is -I??
If you can't follow these instrucstions, you should NOT be rooting anyhow, since you obviously have NO IDEA what you are doing.
1) Get rageagainstthecage-arm5.bin
http://stealth.openwall.net/xSports/RageAgainstTheCage.tgz
2) Get Superuser.apk, busybox,su
http://dl.dropbox.com/u/1327667/freenexus.zip
3) Get the Android SDK (ADB)
http://dl.google.com/android/android-sdk_r07-windows.zip
4a) Unzip android SDK (e.g. so that the tools folder is F:\ADB\)
4b) connect Nexus One with with "applications=>development=>USB debug enabled" (and install USB driver if necessary)
5) Unzip/unrar files within RageAgainstTheCage.tgz to F:\ADB\
6) Unzip/unrar files within freenexus.zip to F:\ADB\
7) Open command prompt go to F:\ADB
[7b) Verify that your nexus one is connected and responding - type "adb devices" it should list your N1
8) Now within the command prompt do the following (commands in bold - the rest gives you an indication of the results)
(Note: if you get $ instead of #, just go back and repeat the instructions from where it says $ ./rageagainstthecage. Worked like a charm on the second try for me.)
F:\ADB>adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
263 KB/s (5392 bytes in 0.020s)
F:\ADB>adb push Superuser.apk /data/local/tmp/Superuser.apk
263 KB/s (5392 bytes in 0.020s)
F:\ADB>adb push su /data/local/tmp/su
263 KB/s (5392 bytes in 0.020s)
F:\ADB>adb push busybox /data/local/tmp/busybox
263 KB/s (5392 bytes in 0.020s)
F:\ADB>adb shell chmod 700 /data/local/tmp/rageagainstthecage
F:\ADB>adb shell
$
$ cd /data/local/tmp
cd /data/local/tmp
$ ./rageagainstthecage
./rageagainstthecage[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C[*] checking NPROC limit ...
[+] RLIMIT_NPROC={3084, 3084}[*] Searching for adb ...
[+] Found adb as PID 64[*] Spawning children. Dont type anything and wait for reset![*][*] If you like what we are doing you can send us PayPal money to[*] 7-4-3-C[at]web.de so we can compensate time, effort and HW costs.[*] If you are a company and feel like you profit from our work,[*] we also accept donations > 1000 USD![*][*] adb connection will be reset. restart adb server on desktop and re-login.
$
F:\ADB>adb kill-server
F:\ADB>adb start-server
* daemon not running. starting it now *
* daemon started successfully *
F:\ADB>adb shell chmod 755 /data/local/tmp/busybox
F:\ADB>adb shell
#mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cd /data/local/tmp
cd /data/local/tmp
# ./busybox cp busybox /system/bin
./busybox cp busybox /system/bin
# chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/busybox
# busybox cp Superuser.apk /system/app
busybox cp Superuser.apk /system/app
# busybox cp su /system/bin
busybox cp su /system/bin
# chmod 4755 /system/bin/su
chmod 4755 /system/bin/su
# exit
F:\ADB>adb shell
# su
su
#mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
# exit
F:\ADB>exit
Click to expand...
Click to collapse
nexusdue said:
If you can't follow these instrucstions, you should NOT be rooting anyhow, since you obviously have NO IDEA what you are doing.
1) Get rageagainstthecage-arm5.bin
http://stealth.openwall.net/xSports/RageAgainstTheCage.tgz
2) Get Superuser.apk, busybox,su
http://dl.dropbox.com/u/1327667/freenexus.zip
3) Get the Android SDK (ADB)
http://dl.google.com/android/android-sdk_r07-windows.zip
4a) Unzip android SDK (e.g. so that the tools folder is F:\ADB\)
4b) connect Nexus One with with "applications=>development=>USB debug enabled" (and install USB driver if necessary)
5) Unzip/unrar files within RageAgainstTheCage.tgz to F:\ADB\
6) Unzip/unrar files within freenexus.zip to F:\ADB\
7) Open command prompt go to F:\ADB
[7b) Verify that your nexus one is connected and responding - type "adb devices" it should list your N1
8) Now within the command prompt do the following (commands in bold - the rest gives you an indication of the results)
(Note: if you get $ instead of #, just go back and repeat the instructions from where it says $ ./rageagainstthecage. Worked like a charm on the second try for me.)
Click to expand...
Click to collapse
Ok perhaps that what i am doing wrong...
so i download android-sdk_r07-windows.zip & unzip it..to a folder F:\ADB.
So i have to create a new folder named ADB and thne unzip all teh stuff in it??
because before i was unzipping the android-sdk_r07-windows.zip & then the folder named android-sdk_r07-windows & i was upzipping freenexus.zip & RageAgainstTheCage.tgz in the tools folder in the android-sdk_r07-windows folder.
So correct me if im wrong instead of android-sdk_r07-windows folder I have to make a new folder named F:\ADB and then unzinp android-sdk_r07-windows.zip & freenexus.zip & RageAgainstTheCage.tgz in teh F;\ADB folder not in the android-sdk_r07-windows tools folder??
Please advise?>?
junooni.1980 said:
Ok perhaps that what i am doing wrong...
so i download android-sdk_r07-windows.zip & unzip it..to a folder F:\ADB.
So i have to create a new folder named ADB and thne unzip all teh stuff in it??
because before i was unzipping the android-sdk_r07-windows.zip & then the folder named android-sdk_r07-windows & i was upzipping freenexus.zip & RageAgainstTheCage.tgz in the tools folder in the android-sdk_r07-windows folder.
So correct me if im wrong instead of android-sdk_r07-windows folder I have to make a new folder named F:\ADB and then unzinp android-sdk_r07-windows.zip & freenexus.zip & RageAgainstTheCage.tgz in teh F;\ADB folder not in the android-sdk_r07-windows tools folder??
Please advise?>?
Click to expand...
Click to collapse
Sorry this is so basic ... if you don't understand folder structures, you really SHOULD NOT ROOT!
Do NOT do it! Maybe after using computers for a couple of years you can "upgrade" to rooting your phone.
nexusdue said:
Sorry this is so basic ... if you don't understand folder structures, you really SHOULD NOT ROOT!
Do NOT do it! Maybe after using computers for a couple of years you can "upgrade" to rooting your phone.
Click to expand...
Click to collapse
I can admire how you're so annoyed but I guess i gotta suck it up cus It I who is in need.
LOL! i've been using computers for a while now & I do undrestand the folder structure pretty well why would i think that? Cus I was able to root the phone the first time.
It's just that i find the description so confusing, I use windows, dunno what OS are you on? But when you extract a zip file it creates a default folder of the same name so...
But i really don't think that my question was that hard, which shot you over the moon & piss you off and made you tell me to learn basic computing first.
All i asked was If I am suppose to make a separate folder named ADB & if I sould extract every thing in it rather than the default unzipped folder that windows makes. But I guess If you're so annoyed then i'l leave it for some one else, I am quite sure one of the purpose of this forum is to get and give help. And im pretty sure that there will be someone who can help me or perhaps i'll find a way myself. But anyways thanks alot for your time, you've been nothing but great help. LOL! And I mean it...
This guide is for people who want root but want to keep their stock rom, not breaking the warranty, unlocking bootloader etc.
A proud ubuntu user, I am writing this in a new thread purely because the manual rageagainstthecage method and SuperOneClick method did not not work for me, see link to my conclusion below if you care
http://forum.xda-developers.com/showpost.php?p=11305312&postcount=2526
What did work however was via adb shell using psneuter and its fairly simple if you follow the following commands.
This guide assumes you know how to get access to the shell via adb, if you dont then search elsewhere for a useful guide
OK lets get to business!
1. Download the attached nexus_one_softroot.tar from the bottom of this post and extract contents to the same folder as adb
2. Open up your terminal, cd to the same folder as adb and the extracted files
3. Enter the following commands:
Code:
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
After this you should see only a $ which tells us that we at the android command line with user privileges only, lets continue
Code:
$ cd /data/local/tmp
$ ls
busybox
su
psneuter
$ ./psneuter
property service neutered.
killing adbd. (should restart in a second or two)
You will now be kicked out of android shell, lets go back in
Code:
sudo ./adb shell
After this you should see only a # which tells us that we root baby! If you want to double check issue this command
Code:
# id
uid=0(root) gid=0(root)
Lets continue on. From this point we will install busybox and su which will make root permanent
Code:
# 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
For some reason I sometimes have to enter exit twice to leave the android shell. Again, re-access the android shell
Code:
sudo ./adb shell
Now in the android shell we can finish up
Code:
# su
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
# exit
# exit
Lastly we must install Superuser, and I did this from the android market so I knew its the latest version, its simple to get, less command input etc.
Now you have root! I hope this was simple enough to follow, I have not really written a guide before but from lots of searching I just could not find a solution for my Nexus One 2.2.1 FRG83D, especially any guide that uses psneuter.
Anyway, glad to contribute
EDIT - also, being new to starting threads, this may not quite be in the right section of the forum, sorry if thats the case mods
Added link to the thread from Wiki.
upgraded to gingerbread 2.3.3. after copying and setting permissions, got this:
PHP:
$ cd /data/local/tmp
$ ls -l
-rwxr-xr-x shell shell 26248 2010-07-22 10:20 su
-rwxr-xr-x shell shell 1062992 2010-10-16 22:29 busybox
-rwxr-xr-x shell shell 585731 2011-01-08 18:02 psneuter
su
busybox
psneuter
$ ./psneuter
Failed to set prot mask (Inappropriate ioctl for device)
second time threw me out of shell. again adb shell gives this:
PHP:
$ id
uid=2000(shell) gid=2000(shell) groups=1003(graphics),1004(input),1007(log),1009(mount),1011(adb),1015(sdcard_rw),3001(net_bt_admin),3002(net_bt),3003(inet)
mfkr said:
upgraded to gingerbread 2.3.3. after copying and setting permissions, got this:
Code:
$ ./psneuter
Failed to set prot mask (Inappropriate ioctl for device)
Click to expand...
Click to collapse
I believe this is due to a change in the kernel as it is upgraded into gingerbread, the input/output controls have changed, leaving psneuter out of date with the current kernel.
However if an exploit is found with the kernel used in 2.3.3, you can use it in place of psneuter with the above method.
Hey Samsung Galaxy tab users and devs.
So im' having a bit of a problem here trying to remount my galaxy tab so i can read/write to it. My cache size is the famous and well hated 25 MB file size limit so i wanted to change it by using this method:
http://forum.xda-developers.com/showpost.php?p=18840882&postcount=227
Im currently running gingerbread 2.3 with root priviliges, and Clockworkmod 3.0.5
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/URL] [/IMG]
Whenever i've try to use the remount command it get this error:
http://imageshack.us/photo/my-images/600/androidadb.jpg/
So what am im doing wrong? running WIn 7 64 bit and my tablet is set to usb debugging mode.
Been searching Google and XDA the couple of days but haven't found any solution.
In advance thanks, jakk212
Jakk212 said:
Hey Samsung Galaxy tab users and devs.
So im' having a bit of a problem here trying to remount my galaxy tab so i can read/write to it. My cache size is the famous and well hated 25 MB file size limit so i wanted to change it by using this method:
http://forum.xda-developers.com/showpost.php?p=18840882&postcount=227
Im currently running gingerbread 2.3 with root priviliges, and Clockworkmod 3.0.5
[/URL] [/IMG]
Whenever i've try to use the remount command it get this error:
http://imageshack.us/photo/my-images/600/androidadb.jpg/
So what am im doing wrong? running WIn 7 64 bit and my tablet is set to usb debugging mode.
Been searching Google and XDA the couple of days but haven't found any solution.
In advance thanks, jakk212
Click to expand...
Click to collapse
Hi Jakk,
I'm not a developer, but, the error seems indicate that adb can't remount as RW the /system, so:
1) adb shell work? (you must see a "#" if you are root)
2) have you installed busybox?
3) the 01newcache script in init.d directory work if you have a rom/kernel that suppor init.d
I use the script and i can confirm that work very fine
Bye
Idk
1) How am i able to see that? Should i see a # at the ADB CMD box? Root checker veryfies that my device is rooted.
2) Yes it's installed using V1.16.2androidminimal - updating now.
3) How can i check if my ROM supports that? My rom is the Stock safe Rom provided when flashing to Overcome.
Using the "adb shell" command in ADB gives me a $
using the adb shell command gives me the $ as i said.
When using the command su it gives me the # you're where talking about.
Jakk212 said:
using the adb shell command gives me the $ as i said.
When using the command su it gives me the # you're where talking about.
Click to expand...
Click to collapse
Though im still not capable of remounting my galaxy tab
Jakk212 said:
using the adb shell command gives me the $ as i said.
When using the command su it gives me the # you're where talking about.
Click to expand...
Click to collapse
Hi Jakk,
Yes, so you have a working superuser thats ok, but if you have stock kernel (i think) there isn't any init.d support so the only way is to try manually.
Another way is installing a custom rom (boca, overcome, etc..) or custom kernel that have init.d support.
Bye
Idk
---------- Post added at 02:01 PM ---------- Previous post was at 01:55 PM ----------
Jakk212 said:
Though im still not capable of remounting my galaxy tab
Click to expand...
Click to collapse
There is some errore message when you try to remount via adb? Try to remount filsystem directly in a root shell, here :
http://forum.xda-developers.com/showthread.php?t=859712
there is, at the end of first post, the instruction to mount r/o the /system
Bye
Idk
Hmm actually not sure that there is a custom kernel installed (i don't suppose since it's a stock firmware, then the kernel should be stock - dosen't allow me to overglock however xD )
I've get this message:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
30336CA087D400EC device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ su
# adb remount
adb remount
adb: not found
# remount
remount
remount: not found
#
Gonna try with to remount it directly in a root shell as you've said - see if that works.
I'll suppose that this is what im gonna write in adb?
Code:
> adb shell
# mount -o remount,rw -t rfs /dev/block/stl9 /system
# exit
Tried to flash the overcome kernel v3.3.1
Also i've connected the tab while in recovery mode now i get a ~$ when entering adb shell.
Jakk212 said:
Hmm actually not sure that there is a custom kernel installed (i don't suppose since it's a stock firmware, then the kernel should be stock - dosen't allow me to overglock however xD )
I've get this message:
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
30336CA087D400EC device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Operation not permitted
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
$ su
# adb remount
adb remount
adb: not found
# remount
remount
remount: not found
#
Gonna try with to remount it directly in a root shell as you've said - see if that works.
I'll suppose that this is what im gonna write in adb?
Code:
> adb shell
# mount -o remount,rw -t rfs /dev/block/stl9 /system
# exit
Click to expand...
Click to collapse
Hi Jakk,
1) adb is use only from PC (windows or linux), there isn't any adb command into android OS...
2) My mistake: read this links: http://android-tricks.blogspot.com/2009/01/mount-filesystem-read-write.html and http://forum.xda-developers.com/showthread.php?t=685146; the above command is about rfs (Samsung Robust File System); if you have converted the filesystem into ext4, i'm not sure that above command work....
sorry
Bye
Idk
Im am able to mount using the
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Command you told me about but when i try to push the newcache file
Code:
adb push 01newcache /system/etc/init.d/
it simply says:
adb: Not found
When trying to copy it outside the shell it says:
failed to copy "01newcache" to "system/etc/init.d/": Is a directory.
Jakk212 said:
Im am able to mount using the
Code:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Command you told me about but when i try to push the newcache file
Code:
adb push 01newcache /system/etc/init.d/
it simply says:
adb: Not found
When trying to copy it outside the shell it says:
failed to copy "01newcache" to "system/etc/init.d/": Is a directory.
Click to expand...
Click to collapse
Hi,
if you try the adb into android phone shell, simply don't work because adb is a windows command (adb = android debug bridge).
The good is seems you have the init.d directory, so try this:
go to android phone shell and remount /system
in a windows cmd shell do this:
adb push 01newcache /system/etc/init.d/
return into android phone shell:
adb shell
cd /system/etc/init.d
chmod 777 01newcache
ls -l /system/etc/init.d (to show the contend of init.d)
exit
Bye
So you mean that i'll just simply open a cmd box without refering to adb and then use the adb push 01newcache /system/etc/init.d/ command? How's that gonna work?
If you've got the time could you please assist me over teamwiever or something similair?
Jakk212 said:
So you mean that i'll just simply open a cmd box without refering to adb and then use the adb push 01newcache /system/etc/init.d/ command? How's that gonna work?
If you've got the time could you please assist me over teamwiever or something similair?
Click to expand...
Click to collapse
Hi Jakk,
Rollback, read this:
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
The operation is in 2 steps, pc and android terminal: adb is pc side the rest in android terminal.
I'm sorry, i prefer forum support, i've no time at this moment.....
If i'm not clear enough please tell me, i don't know your skill level...
Bye
Idk
pretty skilled, gonna start my IT-technician education after christmas, and i've know a bit bat programming from working with windows server and also a bit html and php.
capable of flashing ROMS, unbricking etc but haven't used ADB before. I've configured adb the exact same way as the tut you've sent me.
However i still just get's error codes like adb not found, remount not found, Is a directory, or are you sure you are rooted?
Jakk212 said:
pretty skilled, gonna start my IT-technician education after christmas, and i've know a bit bat programming from working with windows server and also a bit html and php.
capable of flashing ROMS, unbricking etc but haven't used ADB before. I've configured adb the exact same way as the tut you've sent me.
However i still just get's error codes like adb not found, remount not found, Is a directory, or are you sure you are rooted?
Click to expand...
Click to collapse
Is working ?:
Code:
adb shell
If yes then:
Code:
su
mount -o remount rw /system
then - if you are not able to use "push" - copy the file in your SDcard then, while in adb shell:
Code:
cp /sdcard/yourfile /your-destination/
Seem easy
then which one am i going to choose? The overwrite?
and am i just supposed to write it like this:
cp /mnt/sdcard/01newcache /system/etc/init.d/
Because then i've get a cp can't create /system/etc/init.d/: Is a directory
Jakk212 said:
then which one am i going to choose? The overwrite?
and am i just supposed to write it like this:
cp /mnt/sdcard/01newcache /system/etc/init.d/
Because then i've get a cp can't create /system/etc/init.d/: Is a directory
Click to expand...
Click to collapse
Try this:
cp /mnt/sdcard/01newcache /system/etc/init.d/01newcache
Bye
If you have the init.d folder then just manul copy "01newcache" to your sd card and from your tab, with a root explorer (i use esfile explorer with root option enabled from option menu) copy it to system/etc/init.d.
...to solve the original problem...
I fixed this on my device from a windows command prompt by typing "adb root" , which restarts the daemon on the device with root permissions.
Okay I've done enough research before deciding to make this post but couldn't find any solution.
Situation is I tried to install CF3D using CWM and now I'm stuck at the black boot screen that says GT N7000.
I tried to log into ADB shell and execute /system/lib/cf3d_uninstall.sh since that is the general solution but it seems I do not have the file there. Can someone give me the sh file if they have or tell me how to remove the drivers manualls through the ADB shell so that I can boot back normally. I did not backup before doing this..and I guess today isn't my day! Please help me remove the drivers! It's a little urgent.
I am new to the ADB shell concept and these are the commands I executed after connecting:
adb devices
adb shell
su
ls -d */
cd system
cd lib
sudo cf3d_uninstall.sh
Here it says that the file isn't found.
Edit: Nevermind.. Restoring back to CM9 for tonight...
Click to expand...
Click to collapse
tried these ?
sh system/lib
sh /cf3d_uninstall.sh
Should I just execute the contents of this shellscript via ADB? I found these on Google Code
Code:
#!/system/bin/sh
mount -o rw -o remount /dev/block/mtdblock4 /system
stop
cat /system/lib/libGLESv1_CM_ORG_CF3D.so > /system/lib/libGLESv1_CM.so
chown 1000.1000 /system/lib/libGLESv1_CM.so
chown 1000:1000 /system/lib/libGLESv1_CM.so
chown system.system /system/lib/libGLESv1_CM.so
chown system:system /system/lib/libGLESv1_CM.so
chmod 644 /system/lib/libGLESv1_CM.so
cat /system/lib/libGLESv2_ORG_CF3D.so > /system/lib/libGLESv2.so
chown 1000.1000 /system/lib/libGLESv2.so
chown 1000:1000 /system/lib/libGLESv2.so
chown system.system /system/lib/libGLESv2.so
chown system:system /system/lib/libGLESv2.so
chmod 644 /system/lib/libGLESv2.so
#rm /system/lib/libGLESv1_CM_ORG_CF3D.so
#rm /system/lib/libGLESv2_ORG_CF3D.so
rm /system/lib/cf3d_uninstall.sh
rm /system/lib/cf3d_sh
reboot -f
reboot
reboot normal
toolbox reboot
busybox reboot -f
busybox reboot
busybox reboot normal
nokiamodeln91 said:
tried these ?
sh system/lib
sh /cf3d_uninstall.sh
Click to expand...
Click to collapse
Heya it says "Can't open 'cf3d_uninstall.sh' "
What Rom are you on?
nokiamodeln91 said:
What Rom are you on?
Click to expand...
Click to collapse
Ultimate N7000 XXLSC JellyBean 4.1.2 v5.1 ... And I really don't wanna reflash :/
Pl first try to locate where the cf3d files are and then run the command with right paths
[RESOLVED] CF3D Uninstall after boot loop
agvulcan said:
Okay I've done enough research before deciding to make this post but couldn't find any solution.
Situation is I tried to install CF3D using CWM and now I'm stuck at the black boot screen that says GT N7000.
I tried to log into ADB shell and execute /system/lib/cf3d_uninstall.sh since that is the general solution but it seems I do not have the file there. Can someone give me the sh file if they have or tell me how to remove the drivers manualls through the ADB shell so that I can boot back normally. I did not backup before doing this..and I guess today isn't my day! Please help me remove the drivers! It's a little urgent.
I am new to the ADB shell concept and these are the commands I executed after connecting:
adb devices
adb shell
su
ls -d */
cd system
cd lib
sudo cf3d_uninstall.sh
Here it says that the file isn't found.
Click to expand...
Click to collapse
Resolved (for me) :
I actually had the same error using the same command you did. You made a mistake though : when using an "sh" script, you have to invoke it's command, simply using "sh" before the name of the script you attempt to launch.
This is the way you have to go :
you should have typed : "sudo sh cf3d_uninstall.sh"
I actually managed to get it to work this way, and to stop boot loop / freeze (call it whatever you want), as it actually DID uninstall CF3D faulty drivers.
DO NOT USE CF3D with Jelly Bean, at the moment at least. Though Chainfire wrote he wouldn't develop anymore his drivers for JB, as it would need too much coding, again. Stick to GB or even ICS (it used to work for me)
--------
Full technique :
Prerequisites :
-CWM
-Aroma File Manager : Download it here :
Way to go :
-Take out your SD card from your device
-Copy Aroma FM to your Ext. SD Card using a microSD adapter (you can find one at any classical SD card retailer for a few bucks)
-Stick it back in your device
-Launch ClockWorkRecoveryMod
-"Install zip file"
-"Install from SD Card'
-Choose Aroma FM zip file, and install it.
-Tap on option key to get option menu, and launch the shell
-Then type :
su
cd system
cd lib
sh cf3d_uninstall.sh
Your device will automatically reboot, and boot your system normally.
See Ya
Chain Fire 3d boot loop .. not booting help plz ASAP
hello.. i am facing the same problem
i am using Panasonic T11, i had rooted it but it does not have any CWM,etc
when i installed Chain Fire 3d. it prompt me to reboot, bt it was boot looped, and i tried the ways u suggested
the problem its shows this errors in pic . plz suggest me something i can do about my phone
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
when i tried to go in recovery mode it shows ENTRY QPST DOWNLOAD
plz help me