Develop Bugs

[DEPRECATED][GUIDE] Temporary root your Desire Z

HTC Vision // Desire Z Temporary Rooting
1. Download this package: MegaUpload
2. Copy the content of the package in a folder called "temproot" in your SDCard root.
3. Execute this script:
Code:
#!/system/bin/sh
cp -R /mnt/sdcard/temproot/* /data/local/tmp/
cd /data/local/tmp/
chmod 755 *
./rageagainstthecage-arm5.bin
ps
4. Restart Terminal Emulator
5. Execute this script:
Code:
#!/system/bin/sh
/data/local/tmp/busybox killall rageagainstthecage-arm5.bin
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
/data/local/tmp/busybox cp /sdcard/temproot/Superuser.apk /system/app/Superuser.apk
/data/local/tmp/busybox cp /sdcard/temproot/su /system/bin/su
/data/local/tmp/busybox cp /sdcard/temproot/busybox /system/bin/busybox
chmod 4755 /system/bin/su
chmod 4755 /system/bin/busybox
mount -o ro,remount -t ext3 /dev/block/mmcblk0p25 /system
Now your phone is temporairily rooted and you can even get root on adb.
Thanks to:
*- C-Skills for the exploit
*- Guys in G2 section for testing it.

Sweet
but what do we do to get full root access?

There is no full root yet for either this device or g2. You will see that later

M9x3mos said:
There is no full root yet for either this device or g2. You will see that later
Click to expand...
Click to collapse
excited
wonder if the "z" and G2 can use the same Recovery image and Roms..or wil it be like htc magic and My touch ?

G2 and Z are the same device.... HTC Vision.
Radio ROMs and BootLoaders should be compatible, we only need someone that can verify, but AFAIK a G2 owner flashed a full Desire Z ROM and worked without problems.

kholk said:
G2 and Z are the same device.... HTC Vision.
Radio ROMs and BootLoaders should be compatible, we only need someone that can verify, but AFAIK a G2 owner flashed a full Desire Z ROM and worked without problems.
Click to expand...
Click to collapse
any idea if the G2 is a test unit or retail unit? i want senseui (sad i know, but im a sucker for nice graphic)

Correction. The Desire Z rom currently be flashed to G2 but the PC10IMG.zip original G2 rom does work on the Desire Z

I try using this but My G2 didn't work, I got stock here at this step:
"#!/system/bin/sh
cp -R /mnt/sdcard/temproot/* /data/local/tmp/"

Anyone try overclocking it yet?

waiting89 said:
I try using this but My G2 didn't work, I got stock here at this step:
"#!/system/bin/sh
cp -R /mnt/sdcard/temproot/* /data/local/tmp/"
Click to expand...
Click to collapse
Are there any errors?
Please provide more details, it's only a file copy...

kholk said:
Are there any errors?
Please provide more details, it's only a file copy...
Click to expand...
Click to collapse
Link is down kind sir. I found this one Droid2Root.rar from another forum.

waiting89 said:
I try using this but My G2 didn't work, I got stock here at this step:
"#!/system/bin/sh
cp -R /mnt/sdcard/temproot/* /data/local/tmp/"
Click to expand...
Click to collapse
It gives you an axxs denied when you try that. says "cp: permission denied." I can't ls inside of /data either.

do changes persist?
If I do this temp root and install busybox or tether, will the changes be wiped out on restart?

"cp: permission denied." Yes this is the error code I get.
"export PATH=/data/local/bin:$PATH
$ $ #! /system/bin/sh
$ cp -R /mnt/sdcard/temproot/* /data/local/tmp/
cp: permission denied
$"
That's exactly what it appears on the terminal.

I read this on androidspin :
If you root your new G2 phone, HTC has embedded a chip that will detect this and return the phone back to its original factory settings. So much for open source!
They can do this?

The file is no longer available. Can someone repost it?
Thanks

Hmm, yep same problem, cp gives me a permission denied, and the folder /data is a system file seems like we don't have any access to it. on the example, seems like there's # instead of $ which means it has admin access, how did you get to that state? sorry android noob here :-\

stian230 said:
I read this on androidspin :
If you root your new G2 phone, HTC has embedded a chip that will detect this and return the phone back to its original factory settings. So much for open source!
They can do this?
Click to expand...
Click to collapse
Actually no, and its covered in many threads, and I'm sure the op doesn't want the discussion started again.

There isn't any chip that will magically transform your HTC Vision in an airplane / automobile / house / cigarette industry.

script?
Could somebody help with packaging this as a script so we could re-root simply?

[HOWTO] manual rooting of Galaxy Tab (EURO)

This howto is for those people who are unable to root their Galaxy Tab using any of the automated procedures and do not suffer from CLPS (command-line-phobia-syndrome).
My story: After upgrading my EURO (GSM) Galaxy Tab to JM6 my persistent efforts to root the device using either the z4root or SuperOnClick methods have all been unsuccessful. z4root (v1.3.0) kept crashing at different stages, apparently depending on which and how many background apps were running. With SuperOneClick I never managed to get beyond the "changing permissions" stage.
Since both methods are basically wrappers of the rageagainstthecage application, I tried to perform the rooting procedure manually. Guess what, that worked without any problem and it is pretty easy to do.
The basic steps of the rooting process are:
1) use rageagainstthecage to get a temporary root shell
2) use the temporary root shell to copy three files to the read-only system partition the device
While I find the outlined procedure straightforward, you may not. Anyhow, try this at your own risk.
==== Prerequisites ====
I used Ubuntu 10.10 for this, but it should work on any other distro and on Windows just as well. Whatever OS you use, you need a working adb connection to your Galaxy Tab. Odin or Kies are of no use here.
You need the following binaries
* su
* busybox
* Superuser.apk
* rageagainstthecage
To get the all required files, simply download "SuperOneClickv1.5.5-ShortFuse.zip". That's what I used.
Get it here: http://forum.xda-developers.com/showthread.php?t=803682
Extract the contents of the ZIP, open a command-prompt on your computer and change to the directory where the extracted files are located.
Some advice if shell commands are not your regular cup of tea.
The following instructions show the shell commands. Some are executed on the host computer. Others are executed on the Galaxy Tab. You can differentiate between the two easily: All commands which start with "> " need to be executed in a shell on the host computer. Commands which are prefixed with "$ " are executed on the Galaxy Tab. In both case the ">" and the "$" must not be typed. If you copy+paste from this howto, make sure only to copy the commands and leave out the prompt.
==== Step 1: getting a temporary root shell ====
Copy the rageagainstthecage exploit to a temporary directory.
Code:
> adb push rageagainstthecage /data/local/tmp
263 KB/s (5392 bytes in 0.020s)
Change the file permissions and execute the exploit.
Code:
> adb shell
$ cd /data/local/tmp
$ chmod 777 rageagainstthecage
$ ./rageagainstthecage
[*] CVE-2010-EASY Android local root exploit (C) 2010 by 743C
(other output truncated)
Your shell session will be terminated which will throw you back to the regular command prompt of your host computer.
==== Step 2: restart adb server ====
Now stop and restart the adb server process.
Code:
> adb kill-server
> adb start-server
* daemon not running. starting it now *
* daemon started successfully *
Now reconnect to the Galaxy Tab again. Notice the '#' prompt. This means you have a temporary root shell now. We use this to execute some privileged commands which make the rooting permanent.
==== Step 3: making it permanent ====
First, make the system partition writeable. We need this to be able to copy su, busybox and Superuser.apk to the required locations. Then exit the android shell again.
Code:
> adb shell
# mount -o remount,rw -t rfs /dev/block/stl9 /system
# exit
Now we push busybox and su via adb. Then we install Superuser.apk.
Code:
> adb push busybox /system/bin
> adb push su /system/bin
> adb install Superuser.apk
The final steps are to change the file permissions for su and busybox and then remount the system partition as read-only again.
Code:
> adb shell
# chmod 4755 /system/bin/busybox
# chmod 4755 /system/bin/su
# mount -o remount,ro -t rfs /dev/block/stl9 /system
# exit
That should be all. Try a reboot and some apps which require root, like Titanium Backup. The Superuser.apk should popup a dialog requesting permission.
Hope this helps. Happy rooting.
[update]
This process worked for JMA and JMD as well.
"adb install" Superuser.apk instead of "adb push"
[/update]

It will help me !
Merci ;-)

Fantastic! This is just what I was looking for, thank you! I feel dumb now, because I started a thread of my own right as you posted this. You must just type faster than me
I ran a quick test, and it all looks good. One quick question actually. Why do you mount like this:
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
When most instructions for the Galaxy Tab have you doing something like this:
Code:
# mount -o remount,rw -t rfs /dev/block/stl9 /system
I'm not saying it is wrong, in fact, it actually worked for me. I'm just curious as to why it works like that? My understanding of mounting partitions and such in Linux is a little bit weak, so I like to indulge my curiousity by bugging fine people like yourself
Anyway, thanks again, this did exactly what I needed it to. Well done, I appreciate it.

DavidThompson256 said:
One quick question actually. Why do you mount like this:
Code:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
When most instructions for the Galaxy Tab have you doing something like this:
Code:
# mount -o remount,rw -t rfs /dev/block/stl9 /system
I'm not saying it is wrong, in fact, it actually worked for me. I'm just curious as to why it works like that? My understanding of mounting partitions and such in Linux is a little bit weak, so I like to indulge my curiousity by bugging fine people like yourself
Click to expand...
Click to collapse
Thanks for pointing that out! Actually both the filesystem type and blockdevice name were totally wrong. Apparently the mount command ignores both parameters - at least when they are wrong.
I just verified this as self-punishment for not paying attention:
Code:
# mount
(...)
/dev/block/stl9 /system rfs ro,relatime,vfat,log_off,check=no,gid/uid/rwx,iocharset=utf8 0 0
(...)
/system is mounted read-only to /dev/block/stl9. This is the normal state of things.
Now I remount this without the fstype parameter and using a wrong blockdevice name:
Code:
# mount -o remount,rw /dev/block/xyz /system
# mount
(...)
/dev/block/stl9 /system rfs rw,relatime,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
(...)
Surprise, this actually remounts /system in read-write mode. This is why my original howto worked despite using the wrong parameters.
Thanks again. I corrected the HOWTO.

It works for me, but i get now error message: The application calendar save (proces com.android.providers.calendar) is unexpecly stopt. Try again. Forced closing
I had this also with SuperOneClick.
When i want to start the calender in the applications i get it also.
The application wil not run anymore.
How can i resolved this.
Thnx

leonreijnders said:
It works for me, but i get now error message: The application calendar save (proces com.android.providers.calendar) is unexpecly stopt. Try again. Forced closing
I had this also with SuperOneClick.
When i want to start the calender in the applications i get it also.
The application wil not run anymore.
How can i resolved this.
Thnx
Click to expand...
Click to collapse
That is strange. The result of the rooting process is just adding three files to the system partition. I find it hard to believe that this could lead to the problem you describe. However, while experimenting with z4root I had the the effect that there were many rageagainstthecage processes running in the background and the Galaxy Tab slowed down considerably. Perhaps there is something similar going on.
Have you tried rebooting after completing the rooting process?
Try shutting down the Tab completely.After rebooting get a shell on the Tab with "adb shell" and execute "ps". That shows the process list. If that looks normal, I would try a factory reset of the device. Which ROM version are you running?

BlackLevel: Thank you soooooooooo much... I don't get how to hit the Thanks Meter thing, but here is the old fashioned way. I used a MacBook to accomplish your perfect, step by step rooting of an AT&T Galaxy Tab i987. It helps that I'm more comfortable at the command line than with most GUI systems.
I could put this into a bash script, but that could be dangerous. People really need to look at whats happening with 'adb' and have some idea of what adb is for. I did renamed your 'adbmac' to 'adb', then I could cut and paste from your instructions except for adding ./ before the adb... ie. ./adb shell
Again, wonderful work at pulling this all together in one place.
Jeff

This guide worked perfectly! I love a nice quiet clean root and it doesn't get any better than this. You my friend deserve a cookie!

Hi Guys,
I flashed to JMA, rooted it with One Click Root, and everxthing seemdet to be okay, but activating OCLF failed....is there anybody with the same problem?
Jan

Thanks a lot !. It's clean and doesn't need a kies ...
Just a question : after reboot I have to use "su" after "adb shell" to become root.
Is there any way to be root directly after adb shell ?
And thanks again ...
Mike

mbaroukh said:
Just a question : after reboot I have to use "su" after "adb shell" to become root.
Is there any way to be root directly after adb shell ?
Click to expand...
Click to collapse
The reason is that "/sbin/adbd" (the adb daemon) is running as the shell user. It would need to run as root user instead. This requires changes to the initial ram disk where adbd the relevant settings are stored.

Dealing with "insufficient permissions for device"
Thanks, this worked for me.
One small thing: running from a Linux sustem (Ubuntu 9.04), to overcome a "insufficient permissions for device" problem, I had to put my Ubuntu terminal session into su mode and restart the ADB server -- cf. groups.google.com /group/android-discuss/browse_thread/thread/f85a795644e65b59?pli=1 :
[[
adb kill-server
sudo adb start-server
adb devices
]]

gklyne said:
One small thing: running from a Linux sustem (Ubuntu 9.04), to overcome a "insufficient permissions for device" problem, I had to put my Ubuntu terminal session into su mode and restart the ADB server -- cf. groups.google.com /group/android-discuss/browse_thread/thread/f85a795644e65b59?pli=1 :
[[
adb kill-server
sudo adb start-server
adb devices
]]
Click to expand...
Click to collapse
Thanks for the feedback. On my Ubuntu 10.10 adb runs under my regular user-id (1000) and I do not have to use sudo or run the local adb server as root. That might be due to the way the udev rules are set up. Mine are rather unrestrictive and look like this:
Code:
$ cat /etc/udev/rules.d/51-android.rules
SUBSYSTEMS=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEMS=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
How do yours look like?

Which is the more simple method for root of galaxy tab euro ?are there ?

the incredible said:
Which is the more simple method for root of galaxy tab euro ?are there ?
Click to expand...
Click to collapse
Try z4root or SuperOneClick. Both methods are wrappers of the rageagainstthecage exploit and try to automate the manual process outlined here.

This thread should be a sticky. Worked like a charm.

z4root is very simple method..thanks.

thanks to Germany...
I agree, this thread should be sticky. Finaly some sense in android devel section...

Thank you very much for your guide!
I followed all the instructions in your guide, everything seems fine until I try to push the busybox and su to my Galaxy Tab.
blacklevel said:
Now we push busybox and su via adb. Then we install Superuser.apk.
Code:
> adb push busybox /system/bin
> adb push su /system/bin
> adb install Superuser.apk
[/update]
Click to expand...
Click to collapse
I received an error: "failed to copy 'busybox' to '/system/bin/busybox' : No space left on device\"
the same error for the 'su' too
(No space left on device) is impossible, my tab is brand new sealed when i got it.
I have been trying the z4root and SuperOneClick procedure to root this tab but are all unsuccessful.
I am not sure if it is because of my tab needed a "NAND unlock" (I cannot find any guide about the NAND unlock) because I received this message when I tried to install busybox from the market.
Please help! My tab is carrier locked to Bell Canada, I really wanna to unlock it and root it~
Thanks!

gummo6869 said:
I received an error: "failed to copy 'busybox' to '/system/bin/busybox' : No space left on device\"
the same error for the 'su' too,
Click to expand...
Click to collapse
The `no space left on device` message indicates that the /system partition is still read-only. That means the mount command in step 3 was unsuccessful. Did you get any error message when you executed it?

Cant get root! Help plz!

Hi all, first of all: i am from germany, so sorry for my bad english
So i tried to root my phone the "manual" way and used a german tutorial.
i'll explain what i did step by step:
- first i go the needed files, superuser.apk, SU, rage, root, busybox, wpx.ko (for my handset, here from the forum "2.6.32.21-gbe90714")
- adb push su /sdcard/su
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push rage /data/local/tmp/rage
- adb push busybox /data/local/tmp/busybox
- adb push root /data/local/tmp/root
- adb shell cd /data/local/tmp; chmod 0755 rage busybox root;
usb disconnected and in terminal:
- /data/local/tmp/rage
after forking all the innocent children, in the tut it says:
"reset terminal. it should shut down. start it again and click away the FC, start it again and u should see a # in the terminal command line"
all that happend like he said!
- than connect usb
- adb push wpx.ko /data/local
- usb off
- in terminal "insmod /data/local/wpx.ko"
than he says, if everything goes right, it should appear "init_module 'wpthis-OTA.ko' failed (Function not implemented)" and you have temp root.
this all worked too, but now the bad part.
in the tut he says, in terminal do "/data/local/tmp/root"
when i did that, for me it said "mkdir failed. folder already exists"
so i opened the root file and did all my self by hand.
what i did was:
Code:
#!/system/bin/sh
#clean up after rage
/data/local/tmp/busybox killall rage
#remount system as read/write
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
#set up busybox
mkdir /system/xbin [COLOR="Red"]<- this i skipped! Folder existed allready[/COLOR]
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chmod 4755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/bin
#set up su and Superuser.apk
cp /sdcard/Superuser.apk /system/app/Superuser.apk
cp /sdcard/su /system/bin/su
chmod 4755 /system/bin/su
#remount system as read-only
mount -o ro,remount -t ext3 /dev/block/mmcblk0p25 /system
ok, so far so good. it worked!
THAN the tut says, type "sync" in terminal, wait about one or two minutes and reboot. now u should see superuser and so on in the appdrawer list.
i did but there is NOTHING! no superuser rights at all!
than i was dissapointed and tried visionary+r14. did the temp root, it took really long (bout 1-2 min) and in the middle, the screen went black for some seconds. i only saw the statusbar. it ends and i click "permroot", nothing happens. i wait and wait. after about 5 mins, i restarted visionary, klicked permroot again and this time , after about 20 seconds the phone reboots. BUT, adw.launcher was gone FC, newsrob FC, browser FC'ses, gapps FC. And it didn't stop FC'ing. after about 2 minutes the phone restarted itself and booted normally.
Now my phone works almost, but adw.launcher, browser, newsrob and so on are still FC'ing when i try to launch them. 3 or 4 games too.
In german forum they say, first i have to reflash a RUU to restore my system and than i should try visionary directly and it should work.
my questions now:
1. What did i do wrong?
2. What went wrong?
3. Which RUU do i need?
4. How should i root my phone? Which TuT may i use?
My system build is: 1.32.405.3 CL275498 release-keys
Baseband: 12.28b.60.140eU_26.03.02.15_M3
Im thankfull for every help i can get!

tranceonline said:
Hi all, first of all: i am from germany, so sorry for my bad english
So i tried to root my phone the "manual" way and used a german tutorial.
i'll explain what i did step by step:
- first i go the needed files, superuser.apk, SU, rage, root, busybox, wpx.ko (for my handset, here from the forum "2.6.32.21-gbe90714")
- adb push su /sdcard/su
- adb push Superuser.apk /sdcard/Superuser.apk
- adb push rage /data/local/tmp/rage
- adb push busybox /data/local/tmp/busybox
- adb push root /data/local/tmp/root
- adb shell cd /data/local/tmp; chmod 0755 rage busybox root;
usb disconnected and in terminal:
- /data/local/tmp/rage
after forking all the innocent children, in the tut it says:
"reset terminal. it should shut down. start it again and click away the FC, start it again and u should see a # in the terminal command line"
all that happend like he said!
- than connect usb
- adb push wpx.ko /data/local
- usb off
- in terminal "insmod /data/local/wpx.ko"
than he says, if everything goes right, it should appear "init_module 'wpthis-OTA.ko' failed (Function not implemented)" and you have temp root.
this all worked too, but now the bad part.
in the tut he says, in terminal do "/data/local/tmp/root"
when i did that, for me it said "mkdir failed. folder already exists"
so i opened the root file and did all my self by hand.
what i did was:
Code:
#!/system/bin/sh
#clean up after rage
/data/local/tmp/busybox killall rage
#remount system as read/write
mount -o rw,remount -t ext3 /dev/block/mmcblk0p25 /system
#set up busybox
mkdir /system/xbin [COLOR="Red"]<- this i skipped! Folder existed allready[/COLOR]
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chmod 4755 /system/xbin/busybox
/system/xbin/busybox --install -s /system/bin
#set up su and Superuser.apk
cp /sdcard/Superuser.apk /system/app/Superuser.apk
cp /sdcard/su /system/bin/su
chmod 4755 /system/bin/su
#remount system as read-only
mount -o ro,remount -t ext3 /dev/block/mmcblk0p25 /system
ok, so far so good. it worked!
THAN the tut says, type "sync" in terminal, wait about one or two minutes and reboot. now u should see superuser and so on in the appdrawer list.
i did but there is NOTHING! no superuser rights at all!
than i was dissapointed and tried visionary+r14. did the temp root, it took really long (bout 1-2 min) and in the middle, the screen went black for some seconds. i only saw the statusbar. it ends and i click "permroot", nothing happens. i wait and wait. after about 5 mins, i restarted visionary, klicked permroot again and this time , after about 20 seconds the phone reboots. BUT, adw.launcher was gone FC, newsrob FC, browser FC'ses, gapps FC. And it didn't stop FC'ing. after about 2 minutes the phone restarted itself and booted normally.
Now my phone works almost, but adw.launcher, browser, newsrob and so on are still FC'ing when i try to launch them. 3 or 4 games too.
In german forum they say, first i have to reflash a RUU to restore my system and than i should try visionary directly and it should work.
my questions now:
1. What did i do wrong?
2. What went wrong?
3. Which RUU do i need?
4. How should i root my phone? Which TuT may i use?
My system build is: 1.32.405.3 CL275498 release-keys
Baseband: 12.28b.60.140eU_26.03.02.15_M3
Im thankfull for every help i can get!
Click to expand...
Click to collapse
1 & 2 ...
Who can say? You could spend some time examining logcat and dmesg outputs but why? May as well just accept it went wrong and start again.
3.
You want this RUU file.
The most reliable method to flash it would be here. Make it into a pd98img.zip.
4.
After using the visionary r14 tool to temproot I then used this excellent tool to get permanent root. The tool can be used to get eng hboot s-off if you want it as well.
You should also get radio s-off using another excellent tool. Radio s-off is the single best thing you can do to protect yourself from rogue OTA updates which kill root.
5. If your phone explodes its not my fault.
I'm not sure why I'm helping a guy like you though. Fancy forking innocent children
EDIT: Just corrected my post slightly.

i'll try what u said.
I dont know why the rage command forked all the children
I am only thankfull, i did not have had to see that!!
so i am in the bootloader, first it says "no blablaimg.nbh" and so on, than it starts checking the pd98img.zip and after that, its back in the main menu of the bootloader and nothing happens

If you get stuck I'll try my best to help if I'm still around.

it doesn't ask me if i want to flash. first it loads when its says "Checking pd98img.zip" and a blue bar at the right upper corner starts loading. after that, it says "checking pd98img.zip"
when thats finished, nothing happens.
than i reboot my phone and everything is like before
it says "System UID Inconsistent" and i can press "I'm feeling lucky"
Edit: Just saw, that the browser is fully gone! no app in the list anymore!
Edit1: In the zip is an exe file? is this correckt? or is this file only for flashing through pc?
Edit3 LOL: i did a factory reset in the bootloader.
everything is back to stock and working fine now!

OMFG THATS A FU***ING JOKE!!
I did a factory reset to stock, configurated everything and what do my eyes see?
the superuser.apk! i tried SU in erminal and got SU rights! WTF???
how did THAT happen??
i dont know, but i have root now.
Tried to reboot and root stays permanent. This is ok for now i think.
Becaus i read that a Custom ROM don't gives u sooo much advantage, ill stay at stock with root for now. it runs fine and until it starts lagging to much or something else, i'll stay at stock ROM i think
Thank you very much for your help mox !

Ok, now there is another problem.
I have root, setcpu and terminal work fine. Titanium backup les too and says busybox is working too. Solo I wanted to use root explorer and delete some Stuff out of the /system/app folder. Things like amazon mp3 and so on. But I can't get read write rights in that folder. Why that? Can anyone help plz?
Sent from my Desire HD using XDA App

How to root manually/without Windows

There is already an excellent write-up on how to use SuperOneClick to root your Optimus V.
Unfortunately, you may not have a Windows machine available to run the util, or your PC hates the LG drivers, or you may wish to control how you go about rooting your device.
Hence this short write-up which, obviously, relies on pieces I got from that other write-up.
I. Rooting your device
1. You still need ADB!
2. Download the LG Optimus V Tools package from http://nexus.zteo.com/projects/tools/
3. Unzip it
4. Command-line:
Code:
adb push psneuter /data/local/tmp/
adb push su /data/local/tmp/
adb shell
cd /data/local/tmp
chmod 777 psneuter
chmod 777 su
./psneuter
5. You should be kicked out of the shell
6. Command-line:
Code:
adb shell
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
cat /data/local/tmp/su > /system/bin/su
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
(Oh look you are root!)
That's it. You now have permanent root access.
After rebooting your phone, adb should be back to logging you in as a regular user but typing "su" will do the trick.
Note: I realize that the version of SuperUser.apk that comes with SuperOneClick might be re-usable here. I haven't had any success with it but you may.
II. Flashing a new ROM
1. After rooting your device, obviously...
2. Get an image for the ROM you wish to flash...
Currently, my favourite one is a fairly recent version of Zefie's CM7.
You can find it by googling "update-cm-7-04282011-NIGHTLY-thunderc-Xionia-signed.zip" -- I will refer to it, below, as <your_rom_zip_file>
3. Get a minimum Google Apps package for flashing as well.
Here, I would google "gapps-gb-20110325-signed.zip" -- I will refer to it, below, as <your_gapps_zip_file>
3. Command-line:
Code:
adb push flash_recovery /data/local/tmp/
adb push recovery.img /sdcard/
adb push Debug-FormatSYSTEM.zip /sdcard/
adb push <your_rom_zip_file> /sdcard/
adb push <your_gapps_zip_file> /sdcard/
adb shell
su
chmod 777 /data/local/tmp/flash_recovery
/data/local/tmp/flash_recovery /sdcard/recovery.img
reboot recovery
4. In recovery: Flash Debug-FormatSYSTEM.zip
5. In recovery: Wipe cache and dalvik-cache
6. In recovery: Flash <your_rom_zip_file> -- this will take a while
7. Do not reboot!
8. In recovery: Flash <your_gapps_zip_file>
9. Now, reboot.
10. Let your phone think about life for a few minutes
11. Select "Skip" when your phone asks you to create/enter your account info
12. Launch the market; now, enter your main account information

Hey first of all let me tell you that I appreciate this guide. Now my problem is that I am such a noob that I may be doing this wrong.I download the file to my optimus.Then in an explorer I extract it, correct? After that once I put in the first line of command on terminal emulator I get an error that says "adb: permission denied". Please help this guide is my last resort.Whatever I do I can not root through windows.It would be nice if you could explain in more detail every step. Thanks!

help
can u please add a little more detail thank u very much appreciated.

SouthParkFan15:
adb is a tool that you run on your computer; it is available for Windows, Mac OS X and Linux. It is part of the Google SDK.
thizizjohnny:
Could you give me a little more detail regarding what detail you are interested in?

How do I unzip?.. is extract the same thing? I'm running Linux mint 10. How do I get adb? Excuse my noobness.
Sent from my VM670 using XDA App

Oh and one last thing.. does this work on android version 2.2.1?
Sent from my VM670 using XDA App

Yes this works with 2.2.1.
On Linux Mint, you can use the package manager or the unzip command in a terminal window.
apk:
Download the SDK at http://developer.android.com/sdk/index.html
Install it, then run "android" and select "Install platform tools"

I finally got adb on my system, but when I type in "adb devices" nothing comes up and when I do any command that involves the phone i get "error:device not found".Yes I have usb debugging on and yes I have all the right drivers installed and yes I have tried rebooting a million times, and no my computer has never recognized my phone the way it should.Let me also point out that though pdanet or droid explorer they can't find my device. Help please I'm desperate!

Oh, my. Sorry to read that.
Problem is, in 2.2.x, the exploits that give you root access rely on ADB itself so you couldn't be more out of luck.
On second thought...this may seem a bit weird but there may be a way. I have to think about it. It would involve using a file manager that agrees to "see" /data/local/tmp, running psneuter from there and keeping our fingers crossed. I'll keep you updated.

Alright thanks cyansmoke! Keep me informed.

I ran all of the steps for rooting and I didn't get one error. It didn't seem to work though. When I launch adb again after rebooting my phone I get permission denied when I try to run su.
Here is the cap from my command line. I have no idea why it didn't take.
C:\phone\LGOptimusVTools>adb shell
$ cd /data/local/tmp
cd /data/local/tmp
$ chmod 777 psneuter
chmod 777 psneuter
$ chmod 777 su
chmod 777 su
$ ./psneuter
./psneuter
property service neutered.
killing adbd. (should restart in a second or two)
C:\phone\LGOptimusVTools>adb shell
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /data/local/tmp/su > /system/bin/su
cat /data/local/tmp/su > /system/bin/su
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
# exit
exit
C:\phone\LGOptimusVTools>adb shell
$ su
su
su: permission denied
$

It's possible that you have another su in your path that takes precedence.
Please try typing:
/system/bin/su

Hey, do you know if there is a way to upgrade my device to froyo 2.2.2? It's currently 2.2.1 and whenever I go to update system it says something like "Your system is up to date".Incase you have forgotten I have the optimus v that can't establish connections with the computer.So what I could do?I'm thinking that If I do that then maybe it could fix all of my problems (or some of them).Thanks

I don't think that it will help you no.
OK it's taking longer than I thought because my wife's LGV, after I restored it to stock, decided that it would not allow psneuter anymore.
Thus, I will need you to run these commands for me and let me know how that went:
1. First, copy psneuter to the root of your SD Card.
2. Then, download Terminal Emulator from the market
3. Run Terminal Emulator, type:
Code:
cp /sdcard/psneuter /data/local/tmp/
chmod 777 /data/local/tmp/psneuter
/data/local/tmp/psneuter
Now, if we are lucky, you should get kicked out of the terminal app (I know it's weird but there is a claim that it goes through adb(!))
Restart the terminal emulator. If we are double-lucky, your prompt should have changed from '$' to '#'
Fingers crossed. Still surprised to hear that terminal emulator would go through adb. No, let me rephrase that: I am moderately surprised, in fact, considering the limitations put on non-rooted apps.

After I put psneuter on the root of my sdcard.I go to terminal emulator and put in the first code and it says "cp: permission denied".Any suggestions?

SouthParkFan15 said:
After I put psneuter on the root of my sdcard.I go to terminal emulator and put in the first code and it says "cp: permission denied".Any suggestions?
Click to expand...
Click to collapse
Ah, my bad, no "cp" by default.
New instructions:
Code:
cat /sdcard/psneuter > /data/local/tmp/
chmod 777 /data/local/tmp/psneuter
/data/local/tmp/psneuter

After I put in the first code I get an error message saying "cannot create /data/local/tmp/: is a directory".

*facepalm*
Of course I should have written:
Code:
cat /sdcard/psneuter > /data/local/tmp/psneuter

I put in "cat /sdcard/psneuter > /data/local/tmp/psneuter" and I get an error message saying "cannot create /data/local/tmp/psneuter: directory nonexistent".

Any suggestions?

[GUIDE] How to Unroot Bell Desire Z

Hello,
I've had a few requests for help unrooting the Bell Desire Z for warranty purposes.
If you've noticed, there isn't a specific guide for us Bell users, while T-Mobile customers have like a dozen guides scattered around. I figured this out and I should share it.
The really tricky part was figuring out how to get rid of superuser.apk and also get s-on and Bell's CID in the right order, but it turns out it's simple haha. Unfortunately there was not guide for me, so I had to figure this out trial and error and piecing it together from other random posts. I'm not a dev/hacker (well, maybe now I am a novice hacker), so it was a big deal for me (lol) and I can relate to the frustration that comes from not having a good resource.
The exact build my phone shipped with was 1.34.666.5 and other phones may have shipped with other builds, but I've determined that the way Bell operates is that they send their phones to a 3rd party repair facility, and they don't check this (or don't care). However, they may still check whether or not the phone is rooted. So let's unroot it.
DISCLAIMER: Do your own research. I am not responsible for anything bad that happens to your phone after this point (but I will take credit for your success!! ). I used this method successfully and everything worked great. But proceed with caution. If you are unsure, do some looking around. CHECK YOUR MD5 SUMS! Easy MD5 is in the market, and is great.
0. If you have flashed a new radio, flash the old radio back. This one:
http://www.mediafire.com/?9cb8a7jwxob8o6r
NOTE: I'm leaving specific details out of this because if you don't know how to do this, that means you haven't done it before, and you don't need to do this step, and should probably avoid flashing new radios anyway.
1. Download this file:
https://rcpt.yousendit.com/1317004046/ea1de40db3968b867573327c903231bf
-unzip it, and place the folders in /sdcard/clockworkmod/backup/
(recovery will check the md5 sums for you)
2. Reboot into recovery (assuming you have the clockworkmod recovery).
-Do a factory reset (yes, you will lose all your apps etc if you didn't back up)
-Choose Backup/Restore, Advanced Restore, Stock DZ System, System.img
-Choose Backup/Restore, Advanced Restore, Stock DZ Boot, Boot.img
-Reboot
3. Download
http://dl.dropbox.com/u/15272013/Flash Recovery Files.zip
Unzip those files to the root of your sdcard.
PLEASE CHECK THE MD5 of recovery.img AFTER you have unzipped it and placed it on your sdcard!! Sometimes if you check an md5 on your pc and then copy it over, you could still have an error, and then you'll be in a bit of trouble!
md5 of recovery.img: id5d280af717f9afd7ce1c3285c129bc
4. Download the following file:
http://cmw.22aaf3.com/common/gfree_07.zip
md5 (of entire folder): 6916cf05b0805aeac9effdc1725aaa12
unzip and place the file gfree on the root of your sdcard
3. Install Terminal Emulator from the Market. This all needs to be done in the same Terminal Session. Type
$su
#mount -o remount, rw /system
#cp /sdcard/flash_image /system/bin/
#chmod 777 /system/bin/flash_image
#/system/bin/flash_image recovery /sdcard/recovery.img
#cp /sdcard/gfree /data/local/tmp/
#chmod 777 /data/local/tmp/gfree
#rm /system/app/superuser.apk
#/data/local/tmp/gfree -s on -c BM___001
Now when you reboot your phone, you will have an unrooted phone, stock. For clarity, you have:
-Stock, Unrooted Bell ROM 1.34.666.5
-Stock, Matching Radio
-S-Off HBoot
-Proper Bell CID
-Superuser.apk nowhere to be found
The only loose ends are that flash_image will still be in your /system/bin and if you flashed the eng hboot, your hboot number may not match. I'm 99.9% certain nobody at the repair facility will look or care about it. Also, I'd prefer you avoid flashing your hboot, since that is singly the most risky thing you can do with your phone.
If anybody knows whether the flash_image binary works in /data/local/tmp, let me know and I'll edit the post.
Note: when you get your phone back, it will have the latest GB RUU on it. This will give you a bit of trouble re-rooting it. There is no way around having them flash the latest firmware on it, since it's the very first thing they do before they diagnose your phone.
Thanks to Football for information on shipped builds and mxpxboi for his rooted 1.34.666.5 nandroid files.
Cheers!
JT

jontornblom said:
3. Install Terminal Emulator from the Market. This all needs to be done in the same Terminal Session. Type
$su
#mount -o remount, rw /system
#cp /sdcard/flash_image /system/bin/
#chmod 777 /system/bin/flash_image
#/system/bin/flash_image recovery /sdcard/recovery.img
#cp /sdcard/gfree /data/local/tmp/
#chmod777 /system/bin/gfree
#rm /system/app/superuser.apk
#/data/local/tmp/gfree -s on -c BM___001
Click to expand...
Click to collapse
Thanks for the help jontornblom. Quick question:
I am receiving the error message saying /system/bin/gfree no such directory.
Any Tips?

Merzennary said:
Thanks for the help jontornblom. Quick question:
I am receiving the error message saying /system/bin/gfree no such directory.
Any Tips?
Click to expand...
Click to collapse
Did you accidentally type a "/" after gfree?
Sent from my Nexus 6 like tears in rain.

good job - thx for this guide

jontornblom said:
$su
#mount -o remount, rw /system
#cp /sdcard/flash_image /system/bin/
#chmod 777 /system/bin/flash_image
#/system/bin/flash_image recovery /sdcard/recovery.img
#cp /sdcard/gfree /data/local/tmp/
#chmod777 /system/bin/gfree
#rm /system/app/superuser.apk
#/data/local/tmp/gfree -s on -c BM___001
Click to expand...
Click to collapse
There are a couple of small typos in this code. In the second chmod there should be a space between "chmod" and "777". More importantly though, that second chmod should be on "/data/local/tmp/gfree" since that's where it's been copied
Sent from my Desire Z running CM7.

steviewevie said:
There are a couple of small typos in this code. In the second chmod there should be a space between "chmod" and "777". More importantly though, that second chmod should be on "/data/local/tmp/gfree" since that's where it's been copied
Sent from my Desire Z running CM7.
Click to expand...
Click to collapse
Thanks! Sorry about that =( I will edit the OP
Edit: okay, typos fixed. My apologies to anyone who ran into trouble because of this.
Sent from my Nexus 6 like tears in rain.

jontornblom said:
Hello,
1. Download this file:
...yousendit.com/1317004046/....3968b867573327c903231bf
-unzip it, and place the folders in /sdcard/clockworkmod/backup/
(recovery will check the md5 sums for you)
Click to expand...
Click to collapse
Could someone re-upload file from step 1?

Hi,
I too could use the file from Step 1. And there is a little urgency as I need to get my DZ back to stock as soon as possible.
Your help is appreciated...greatly!
Thanks.