yashsingh1/xdaforums huggingface dataset:
[G2 and Desire Z General] acritec:
I was able to get permroot on 1.72 with the wiki-package.

Pushed the packages through adb, ran psneuter and the root script without any problem.

Permanant root access confirmed (terminal, titanium backup, setCPU)

But when opening the superuser application, I got FC, so I flashed the rmk-updated version.

No issues since.
[G2 and Desire Z General] djfoo000:
is there anyway to rollback to the stock 1.72 ROM (assuming it wasn't done thru OTA but from from a fresh device that 1.72 came with)? Previously on the 1.34 ROM a backup of it was made in the form of a nandroid backup. The procedure for the 1.72 ROM involves downgrading to 1.34 then permarooting (correct me if I'm wrong), which makes a nandroid backup only possible after downgrading to 1.34.

I'm looking for a rollback instead of an RUU method. Are there any?
[G2 and Desire Z General] ludow:
Back to SGS for awhile. They have clear guides. Not just guessing 6 months. :p
[G2 and Desire Z General] steviewevie:
You only have to downgrade to 1.34 to get S-OFF via gfree, because gfree won't work at 1.72. If you already have S-OFF then you can just permaroot at 1.72.

To go back to the 1.72 ROM then unless you were S-OFF already (and could do a nandroid backup) then you will either have to run the RUU or flash the rom.zip.

Sent from my HTC Desire Z
[G2 and Desire Z General] djfoo000:
Meaning:

rooted 1.34 -> OTA 1.72 = reroot with rage

Shipped 1.72 = downgrade to 1.32

I'm just assuming the existence of a shipped 1.72 because I returned my DZ S-ON-ed and factory resetted to repair for the power-down-pull-battery issue. So they might return it to me with 1.72 already on.

The 1.34 RUU posted in the link in the first post, is it considered stock enough and applicable for ALL Desire Zs? If I happen to need to return to the dealer for a 2nd time I want to know if I can get away with the 1.34 ROM this RUU will be flashing (because the nandroid backup will be of this 1.34 ROM, am I right?).
[G2 and Desire Z General] YOSEFE:
Yes, S-OFF does not and did not go away. I have done OTA several times.
[G2 and Desire Z General] YOSEFE:
Oh, by the way, it is not just six months of guessing. When you are charting new territory, as you know very well, knowledge is cumulative.
[G2 and Desire Z General] Zaim2:
I've been meaning to ask, but is there a flashable stock Vodafone UK 1.34 ROM somewhere? I have a Nandroid, but I'd feel more comfortable having a .zip around as well.
[G2 and Desire Z General] ludow:
I have perm root and S-OFF. OTA 1.72 + rage. That's it? :D
[G2 and Desire Z General] steviewevie:
I don't recall seeing one on this forum. We also are missing quite a few other stock ROMs unfortunately.

Sent from my HTC Desire Z
[G2 and Desire Z General] steviewevie:
Sorry but I don't think I am following what you are asking totally.

Yes the 1.34 RUU mentioned is a stock European one, so that will look stock on some DZs. But don't forget there is a large variety of markets, e.g. it won't look stock on a NAM Bell DZ or an Asian DZ.

Can't you just flash the stock 1.72 ROM or RUU if you want to return the phone ? This is where I don't think I understand your scenario.

Sent from my HTC Desire Z
[G2 and Desire Z General] ludow:
Summa summarum: I have 1.34 with perm root and S-OFF.

I can accept 1.72 OTA and get perm root via rage method. Is that correct?
[G2 and Desire Z General] tbalden:
You will need psneuter and than use the permaroot part of the rage method,yeah. But not the rage binary itself, it won't work.its psneuter u should use.
[G2 and Desire Z General] ludow:
Thanks for the tip. I'll go for psneuter.

EDIT: I need help with psneuter. Looks like pretty messy. Anybody?
[G2 and Desire Z General] premist:
This is how I got psneuter to work:

adb push psneuter /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell /data/local/tmp/psneuter

Run adb shell with the command below:

adb shell

and if you get a # then you have a temp root!

Hope this helps
[G2 and Desire Z General] ludow:
Thanks premist. And after that rage?
[G2 and Desire Z General] steviewevie:
After that, the permaroot part of the rage method, i.e. running the "root" script. Not rage itself, that's only for temp root and doesn't work anyway at 1.72.

Sent from my HTC Desire Z
[G2 and Desire Z General] ludow:
This is like a riddle. What is permaroot part of the rage method?
[G2 and Desire Z General] premist:
Run:

adb push su /sdcard/su
adb push Superuser.apk /sdcard/Superuser.apk
adb push busybox /data/local/tmp/busybox
adb push root /data/local/tmp/root
adb shell chmod 0755 /data/local/tmp/*

In the command prompt you need bring up an ADB shell, type in:

adb shell

This should give you a #, then you would type in '/data/local/tmp/root'

It should look something like this:

adb shell
# /data/local/tmp/root

/data/local/tmp/root
killall: rage: no process killed
mkdir failed for /system/xbin, File exists

Open a terminal prompt on your phone and type in 'su' you should get a prompt from the superuser permissions to allow the terminal to gain super user status, once you allow that you should get a # at the terminal prompt.
[G2 and Desire Z General] ludow:
Thank guys. :)

He heh, OTA doesn't install. I get small white triangle and small green android. :D
[G2 and Desire Z General] Tyomkeen:
Can't get root on terminal :(

Previously I've rooted my DZ (while it was 1.34) with rage method, I already have S-OFF. After that got update to 1.72.

Now I can get temp root in adb shell using psneuter, but can't get root at all in terminal. I've check su and Superuser.apk both from ChainsDD and rmk40. But nevertheless I can't get root :(

$ su

[terminal holds for a 10+ seconds]

permission denied...

May be somebody knows solution?
[G2 and Desire Z General] steviewevie:
Is that from an adb shell ? Check the phone isn't trying to pop up a window from Superuser on the phone, asking for permission. Because that's what it sounds like the delay is, trying to talk to Superuser to get permission for the "su".
[G2 and Desire Z General] acritec:
Could also be an issue with the Superuser application.

Have you tried opening Superuser with its application icon in the apps drawer ?

If you launch it and it force closes, then you will have to exchange su and Superuser with the special 1.72 versions supplied by rmk.

If it opens OK, you could check the log and also make it 'forget' your previous answers to the Superuser prompt.

Then try again to su from terminal or adb shell. You should get the prompt to allow root permissions.
[G2 and Desire Z General] acritec:
The OTA doesn't seem to work if you have a customized system (clockwork recovery/eng hboot/custem kernel).

If you want stock 1.72, you'll have to use the RUU posted by Football.

This RUU will erase everything, including your data and these customizations.

But you will keep S-OFF, so you're OK to root your device afterwards.
[G2 and Desire Z General] Tyomkeen:
@steviewevie & @acritec

Thank you for the answers! There was a dalvik-cache for Superuser.apk and com.noshufou.android.su.apk.

@all

If you have similar problem - just look through /data/dalvik-cache and rm files:

*Superuser*.apk

*com.noshufou.android.su*.apk

* - wildcard
[G2 and Desire Z General] valve90210:
Do we think there will be a simple one click way of rooting on the 1.72 sense anytime?

I'd like to update but want root just for SetCPU for underclocking for better battery life, and being a total android newbie, don't really understand the process people have been using, with psneuter etc.
[G2 and Desire Z General] djfoo000:
^ 1.72 need to be rooted first for this to be done. The problem now is that root can only be achieved via a downgrade to 1.34 and attempting root (which is what this guide is doing). When the 1.72 radio (or ROM, or thing they exploit for root) gets rooted itself then a one-click to directly root 1.72 should be up in no time.
[G2 and Desire Z General] Hunkelmunkel:
ADB Push

I have the same problem with the adb push command.

If i try to push the "psneuter" file to the sd card it says "failed to copy ... Read-only file system" ... I tried it several times, but it wont work.

Attached is a screenshot with the error.

Can anyone describe me how to mount my sd card as read-write ?

My device is a HTC Desire Z, with Android 2.2, Software 1.72.-405.2, no root or such things. I want to root it, and for the downgrade i need to push psneuter like its described in the downgrade guide in the cyanogen.wiki. I am not allowd to post the link here since i am a new member, but i hope someone knows the way with ADB and "psneuter"

Please help me :)
[G2 and Desire Z General] reid_only:
Getting ready to root G2

Hey all!

First let me say I've read every word of this post, the wiki and several other threads prior to these questions. I feel like I should know the answer on a few of these, but alas, I don't. Thanks in advance for the help and patience.

1) I have a brand new USA G2 - this thing has been powered up once, never made or rec'd a call.

Model number: T-Mobile G2

Android Version: 2.2

Baseband Version: 12.28b.60.140eU_26.03.02.26_M

Kernel Version: 2.6.32.17-g9ab3677

htc-kernel@and18-2 #1

Build number: 1.22.531.8 CL277427 release-keys

Everything I've read here - with posts as recent as this week - states that in the US 1.72 hasn't been rolled out, thus I should be able to root pretty simply without the whole temp root / downgrade / perm root / upgrade / perm root sequence.

However, I'm also reading that if one has Android 2.2, which I do, then you are at 1.72. Maybe that doesn't apply to the U.S.? I don't see anything (ROM version? Software version?) that states 1.34 OR 1.72. So which do I have? Pretty basic question, but one I think I'd better resolve before diving in.

2) Backup: It seems prudent to back things up so I have an escape if things go bad, however from what I can tell Nandroid isn't an option in 1.72, only 1.34. If indeed I'm at 1.72, how to back things up prior to beginning? If I'm at 1.34, is the Nandriod backup integral to the Psneuter procedure (admittedly, I have not completely scoured the Psneuter process yet.) If not, may I request a pointer toward the directions?

I guess that's all for now. I'm off to read about ADB while I wait for a reply here. Thanks in advance!

Reid

G1 (yesterday) -> G2 (today)
[G2 and Desire Z General] guhl99:
Hi !

If adb push fails to write to /sdcard/ then the sd-card is mounted to the PC and not not to the phones /sdcard/ mount point.

Pull down the status bar on the phone, select "USB connected" and make sure that the android is green (if it is yellow click on "Turn off USB storage")

but just 2 principle comments:

- if the sdcard is mounted to your pc then you could also just copy psneuter (or any other file) on the PC to the removable drive

- psneuter is supposed to be copied to /data/local in the end (because the /sdcard/ is a mount point that that can not contain executable files. The psneuter procedure is supposed to be:

adb push psneuter /data/local/
adb shell chmod 777 /data/local/psneuter
adb shell /data/local/psneuter
adb shell

have fun - Guhl
[G2 and Desire Z General] guhl99:
Hi !

You have a normal G2 that is rootable without any downgrade.

Just follow the guide at http://xdaforums.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 or the a little bit simplified guide here http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting

All G2/DZ/DHD are running Android 2.2 as there original Android version. What you have been reading is just wrong.
[G2 and Desire Z General] Hunkelmunkel:
Thank you for your quick help Guhl!

But if im trying to push this, he says something like this:

C:\android-sdk-windows\platform-tools>adb push psneuter \data\local\
failed to copy 'psneuter' to '\data\local\': Read-only file system

C:\android-sdk-windows\platform-tools>adb shell chmod 777 psneuter
Unable to chmod psneuter: No such file or directory

C:\android-sdk-windows\platform-tools>adb push psneuter \data\local\tmp
failed to copy 'psneuter' to '\data\local\tmp': Read-only file system

C:\android-sdk-windows\platform-tools>adb push psneuter F:\data\local\tmp
failed to copy 'psneuter' to 'F:\data\local\tmp': Read-only file system

C:\android-sdk-windows\platform-tools>adb push psneuter \data\local\tmp
failed to copy 'psneuter' to '\data\local\tmp': Read-only file system

I tried it with my normal 16 gb card and a 8 gb goldcard, i made this only for this problem... it seems like there is either no directory named \data\local\tmp on my sd card or it is protected with read-only. I can´t even see the directory from my computer.

Or am i misunderstanding something ? I´m not so experienced with rooting but

I´m drowning in bookmarks with guides for rooting and downgrading... but since visionary wont work with 1.72 i have to downgrade somehow.

And please excuse my long text, but it drives me to despair since 1 week.
[G2 and Desire Z General] guhl99:
Come on, .... ;-)

This is a linux operating system. It is using / (the forward slash) as the path separator and not \ (back slash)

Just copy the commands as i posted them.
[G2 and Desire Z General] Hunkelmunkel:
OMG...

I am so dumb... thank you Guhl ! xD
[G2 and Desire Z General] reid_only:
Thanks guhl99

Thanks. I think I figured it out just after I posted (of course). I was looking for 1.34 or 1.72 but what I have appears to be 1.22. Thanks again. Sorry you guys have to go through so much B.S. for the same result.

Reid
[G2 and Desire Z General] MostStupidUser:
Why not temp root through rootfs?

This may sound like a silly question, but to me it is not clear at all why we have to root the device through the NAND protected file system.

I made the following experiment (Desire Z, 1.72, s-ON):

- temproot via psneuter

- write different tools (including su) to the /system partition:

This works (after remounting rw), and allows me to get a working su if I use the built-in busybox-su and create a corresponding /etc/passwd.

The NAND protection self-cleans the file system on the bit level: After a while the content of the copied files gets corrupted, the inodes are cleared up and at the end (after some hours) one is left with a virginal /system partition

- write tools to /sbin:

This is on the rootfs partition where quite some space is left:

After remounting this rw, I can also copy su or other suid programs there. This

does not get cleaned up (except of course with a reboot) and I can use those programs. Unfortunately, the su from the Superuser.apk does not seem to interact well with the frontend when installed in /sbin, so that it still does not work at the moment, but to me it is not clear why this is no reasonable way to get temproot on the phone within the normal Superuser.apk framework.

Hope anybody can explain why /system is needed instead of /.
[G2 and Desire Z General] tbalden:
Psneuter kills some property service iirc (that's what ps in psneuter stands for I think). New processes will suffer probably, at least that's what scotty2 author of it wrote.
[G2 and Desire Z General] jammesraven:
WOW cool thx a lot :)
[G2 and Desire Z General] steviewevie:
I am probably missing something. But isn't the answer that we usually want permanent root, and as you said without defeating the NAND write protection then changes are lost on a reboot ? Without doing this the changes are in cache, so persist until reboot. Since the changes weren't written to permanent storage (NAND) then the original data is visible again.

Sent from my HTC Desire Z
[G2 and Desire Z General] rmclardy:
Hi. just a quick question. i downgraded my DZ, rooted, S-off etc with gfree and rage, than did a OTA update, back to 1.72. (Still with S-off) then ive done the below, and all went fine. but now my superuser FC's everytime its asked for a root permission. its the latest off the market. typing SU in terminal sits for 10 seconds (i presume window from superuser isnt showing. i have adfree installed, but as soon as you click accept, superuser FC's

any ideas what im doing wrong?

i dont have CWM recovery btw.

Cheers Ross.

Run:

Code:

adb push su /sdcard/su

adb push Superuser.apk /sdcard/Superuser.apk

adb push busybox /data/local/tmp/busybox

adb push root /data/local/tmp/root

adb shell chmod 0755 /data/local/tmp/*In the command prompt you need bring up an ADB shell, type in:

Code:

adb shellThis should give you a #, then you would type in '/data/local/tmp/root'

It should look something like this:

Code:

adb shell

# /data/local/tmp/root

/data/local/tmp/root

killall: rage: no process killed

mkdir failed for /system/xbin, File existsOpen a terminal prompt on your phone and type in 'su' you should get a prompt from the superuser permissions to allow the terminal to gain super user status, once you allow that you should get a # at the terminal prompt.
[G2 and Desire Z General] acritec:
@rmclardy :

rmk40 popsted a working Superuser for 1.72 here:

http://xdaforums.com/showthread.php?t=886999

But you need CWM to install it.

You could try to flash CMW, but I doubt it will work.

You might try cleaning the cache/data for Superuser

through Setting/Applications/Manage applications

Choose the "All" tab and look for Superuser.

Then clear data and cache.

Or you could try the direct hard way as described in post

http://xdaforums.com/showpost.php?p=10887236&postcount=432
[G2 and Desire Z General] rmclardy:
Thanks for the reply, got me thinking tho, as i had CWM installed before.

looked in rom manager, and it says i have 2.5.1.3 installed.

but, alas, i cant boot into recovery as SU (process com.noshufou.android.com) keeps FC'ing. are there button presses i can attempt to get into CWM with on power up?

i know down and power is bootloader, tried up and power but started vibrating and light flashing.

i dont know what im doing enough to go removing stuff from dalvik cache (i cleared data in app manager, cache button was blank anyway)
[G2 and Desire Z General] rmclardy:
OK scrub that, realised i can hit into recovery thru bootloader, but my CWM is borked, comes up with red exclamation mark.

not sure on the way forwards now...
[G2 and Desire Z General] joem1n:
CM7 topic how to use?
[G2 and Desire Z General] steviewevie:
That is the stock recovery, CWM hasn't flashed. For some reason you usually have to flash it twice to make it "stick".

Sent from my HTC Desire Z
[G2 and Desire Z General] Janaboy:
.

Help me please! I tried to find my answer, but i'm not sure.

Can be possible use the update.zip without any modification? Or i need change the hboot?

Thank you!

Janaboy
[G2 and Desire Z General] rmclardy:
Ah right. i know it was on there at one point, as i had CM7 running. rom manager wont flash it at all now, says it cant get privilidges or something.

nothing seems to happen at all now. im not getting the superuser prompts at all. ive s-off still. but no root. :(
[G2 and Desire Z General] acritec:
You're stuck untill you get Superuser working.

Did you try to clear it's data like I suggested before.

Or did you try this :

http://xdaforums.com/showpost.php?p=10887236&postcount=432
[G2 and Desire Z General] rmclardy:
Something odds happened... i was, let us say, buggering about, with psneuter, root, gfree, su and superuser app.

I then uninstalled superuser and rom manager and tried a reboot. When it fired back up, it wont let me install superuser from the market. Says package not signed correctly!! What??

Anyway, i then notice its trying to upgrade it. I have a look and there is an old version installed on there, v2.0 with the little ninja icon. It will not let me uninstall this at all. Icon is grayed out. Im assuming the version i pushed when i initially rooted.

Anyway, i try opening adfree, and low and behold i have a prompt for permissions come up! No FC!

Install rom manager, and flash CWM v2.5.1.3 and try reboot to recovery. Works fine!!

So i now have root, with CWM, but an old version of superuser that wont update or uninstall. How odd!

Thoughts?
[G2 and Desire Z General] acritec:
I am using this version of Superuser without any issues on 1.72 :

http://xdaforums.com/showthread.php?t=886999

It installs with CWM
[G2 and Desire Z General] pmcqueen:
odd happenings (my fault) during root, but appears to be fine?

here's my story:

-pre 1.72 G2

-rooting using wiki method (gfree)

first time I went to do this, I forgot to copy the root file from the temproot part of the process over... so I went thru this whole process and when I got to the part where I was going to execute the final "lock in" command, the phone was naturally confused. upon trying to fix this, I was greeted with plentiful "permission denied" errors when trying to copy the root file I'd forgotten. then the phone proceeded to reboot itself randomly and give me system force close errors, etc. lovely.

so I scrapped everything I had done (everything but locking in the root), wiped the phone, formatted the SD card, and started again from scratch.. this time VERY CAREFULLY so I didn't forget to copy any files.

root went thru fine this time... when I go into fastboot menu, I see "s-off" so I'm assuming that's a big thumbs up. the weird thing is when I went to verify using gfree verify, I got a permissions denied error.

rooted apps are dling and running fine. I'm going to try and install CM6 (7? should I? will dig around and see what people are saying).

I guess my question is this: should I assume, even with the permissions denied error that I received and my initial blunders, that I have successfully permarooted my device? any way to verify besides the "s-off" note in fastboot?
[G2 and Desire Z General] navkaranchadha:
this might seem to be a very basic ques, i want to root my phone but its software no is 1.34.720.6.

is it considered the new 1.72 rom?
[G2 and Desire Z General] acritec:
You're still on the older version.

Rooting that is pretty straightforward.

All you need is in the wiki :

http://xdaforums.com/wiki/index.php?title=HTC_Vision#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
[G2 and Desire Z General] trillistic:
My g2 states My Build number is 1.22.531.8 i just recieved this from tmobile 2 weeks ago. Can i Root this somehow.. im seeing that Alot of g2s cannot be rooted.. and if so Which method should i use??
[G2 and Desire Z General] steviewevie:
Yes, that is the version for the T-Mo OTA update, which came out shortly after the phone was released. Check out the Wiki (link above) and use the method there.

Sent from my HTC Desire Z
[G2 and Desire Z General] projectkennedy:
Ok so , I tried the rooting method in the wiki: Wiki and it didn't work, I'm assuming it is because of the stupid 1.72 ROM, I figured I needed to go through most of the steps in the wiki anyways because the thread that has the 'revert to an older rom' doesn't give those steps and assumes you know what you're doing ( I don't!)

SO, I really really don't want to revert to an older rom to do the s-off thing.. is there a way around it, I do realise that there's probably some thread in some really obvious place, BUT I have been going around in circles all day trying to figure out where to start and where to end up, so please be kind and just help?

In other news: the referencing to threads could use a little tweaking, it's really hard to figure out where to start and where to go from there. Maybe the wiki should say, if you have version 1.72, go all the way to step (whatever) and then see this thread, and the thread should say, make sure you follow the procedure from the wiki up till step (whatever) and then you can start here.

I know you're all smart and it makes sense to you, but for us new people who aren't stupid but are just unfamiliar, it takes a lot of time to get our heads around it!

Thanks
[G2 and Desire Z General] steviewevie:
You're right that the existing threads are a mess. The Wiki also doesn't detail the 1.72 method.

Look for the thread in the dev forum about how to downgrade from 1.72. You will have to downgrade if you don't have radio S-OFF already, because currently there is no way to get that at 1.72. But if you get S-OFF back at 1.34 then you can go back to 1.72 and then permaroot, and you will keep the S-OFF.

Sent from my HTC Desire Z