Database Users

s-off but not super user acces!? help please :)

hey well i got to this point :
# # /data/local/tmp/root
Click to expand...
Click to collapse
anyhow when i run this it says:
cp: can't stat '/sdcard/superuser.apk': no such file or directory
then is the same but with su
Click to expand...
Click to collapse
i went ahead and put sync anyhow and when i restart and run 'su' but is says: unknown user root
any ideas what i did wrong? :/
oh and btw somehow i have S-off...
i followed each step, but i just notices this... for some reason it wont let me push superuser.apk or su, all of the other files can be pushed... any ideas?

no one?

http://www.youtube.com/watch?v=tU9zn_BEth4 i did that way and it works for me.

but i have s-off i supposed to be rooted already but i do not have super user powers... what do i do

Did you copy the Superuser.apk file to the root of your SDcard?

yes i did, and su too and now when i put su on my phone it says unknown user root :/
i can get temporal rooting tough.

Use visionary r13 ... had same issue... worked for me
Get it from pauls visionary thread on Modaco.
Sent from my HTC Vision using XDA App

i had the same situation with u few days ago. just follow http://forum.xda-developers.com/showthread.php?t=834228 and u only need do the temp root part.
Delete visionary and superuser first, install terminal emulator from market.
on you pc:
$ 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 chmod 0755 /data/local/tmp/*
Then on you G2, open a terminal emulator
Launch Terminal Emulator---/data/local/tmp/rage----Wait for the message: "Forked #### childs."------Menu > Reset Term - Terminal Emulator will exit.-----Launch Terminal Emulator, it Force Closes. Launch a second time, and you'll have a root shell----- run the /data/local/tmp/root script here.---sync.
In the last step, u can find the origin thread dose not let u do this. but, if you've got s-off, trust me, just do the last step "/data/local/tmp/root", and when u see a feedback "****files exist",then "sync",

I got s-off, flashed clockwork recovery and baconbits
setcpu is also working
but when I try typed su then reboot in terminal
it says not permitted
and when I want to get rid of the bloatware ie Finance
root explorer refuses to switch to r/w in data folder
any suggestions

u can also do what i suggested in the 8th floor.

o>c said:
I got s-off, flashed clockwork recovery and baconbits
setcpu is also working
but when I try typed su then reboot in terminal
it says not permitted
and when I want to get rid of the bloatware ie Finance
root explorer refuses to switch to r/w in data folder
any suggestions
Click to expand...
Click to collapse
r u rspt in Gfan? since u can read chinese, just look at here. http://www.hiapk.com/thread-631413-1-3.html
I made this thread to help solve such problem.

After I got S-off, I didn't have root either. I just jumped on visionary (made sure run on boot wasn't checked), clicked root now. And boom, that was it. Then I deleted visionary and I've had root ever since...

Last ditch root Attempt.

Hey All.
I have a new Aria with a stock 2.2 build, and the associated Bootloader but I want to get root access to see if I can address my Bluetooth issues
All evidence points to me needing to edit /system/etc/bluetooth/audio.conf but without getting root access I can’t even read the file let alone edit it, so this is still a guess.
Any way we have lots of dodgy little phone shops around Melbourne, and odds on at least one will have an XTC clip. So what is it I actually want them to do?
I know I need to end up with a copy of su in system/bin, Is that what I am asking for? Or am is that not what is required?

FALCON-LORD said:
Hey All.
I have a new Aria with a stock 2.2 build, and the associated Bootloader but I want to get root access to see if I can address my Bluetooth issues
All evidence points to me needing to edit /system/etc/bluetooth/audio.conf but without getting root access I can’t even read the file let alone edit it, so this is still a guess.
Any way we have lots of dodgy little phone shops around Melbourne, and odds on at least one will have an XTC clip. So what is it I actually want them to do?
I know I need to end up with a copy of su in system/bin, Is that what I am asking for? Or am is that not what is required?
Click to expand...
Click to collapse
You would like them to turn security off on the phone and put it in a S-OFF state. With S-OFF, you would be able to flash a custom recovery and gain root access.

So does this mean I can't just insert the binaries i require into the existing OS?
There appear to be some one touch solutions for some ROMs (Universal Androot) wouldn't this indicate that you can just apply the binaries?

FALCON-LORD said:
So does this mean I can't just insert the binaries i require into the existing OS?
There appear to be some one touch solutions for some ROMs (Universal Androot) wouldn't this indicate that you can just apply the binaries?
Click to expand...
Click to collapse
The problem with temporary root on the Aria is the Security Flag (S-ON). As long as that is enabled, you cannot mount the /system partition in Read/Write mode so that you can push new binaries. With the Aria you need to mount the /system partition from ClockworkMod in order to push new binaries to it.

tpbklake said:
The problem with temporary root on the Aria is the Security Flag (S-ON). As long as that is enabled, you cannot mount the /system partition in Read/Write mode so that you can push new binaries. With the Aria you need to mount the /system partition from ClockworkMod in order to push new binaries to it.
Click to expand...
Click to collapse
O.K. So from that statement am I right to assume that you set S-Off, apply your ROM (Or push your binaries) then set S-On so that you can mount it and boot.
How does Universal Androot work then? It would have to push the binaries on without setting S-Off?

FALCON-LORD said:
O.K. So from that statement am I right to assume that you set S-Off, apply your ROM (Or push your binaries) then set S-On so that you can mount it and boot.
How does Universal Androot work then? It would have to push the binaries on without setting S-Off?
Click to expand...
Click to collapse
Once you s-off your phone you would leave it s-off, no need to put it back to s-on and why would you want too?
My phone is s-off, I can flash the official 2.2.2 rom and then turn around and easily get back to a different rooted rom any time I want by flashing a custom recovery followed by the rom of choice.

FALCON-LORD said:
O.K. So from that statement am I right to assume that you set S-Off, apply your ROM (Or push your binaries) then set S-On so that you can mount it and boot.
How does Universal Androot work then? It would have to push the binaries on without setting S-Off?
Click to expand...
Click to collapse
You cannot set the security flag on the Aria with HBOOT 1.02 via any software method. That is the reason why you cannot gain permanent root using Unrevoked anymore. On HBOOT 1.02 you can only turn S-OFF by using the XTC Clip hardware. As A$$h5t pointed out, once you get S-OFF, you do not want to turn security back on.
What I was trying to say was even if Universal Androot could get you temporary root on the Aria HBOOT 1.02, it would not be able to turn security off so and mount the /system partition in Read/Write mode.

tpbklake said:
You cannot set the security flag on the Aria with HBOOT 1.02 via any software method. That is the reason why you cannot gain permanent root using Unrevoked anymore. On HBOOT 1.02 you can only turn S-OFF by using the XTC Clip hardware. As A$$h5t pointed out, once you get S-OFF, you do not want to turn security back on.
What I was trying to say was even if Universal Androot could get you temporary root on the Aria HBOOT 1.02, it would not be able to turn security off so and mount the /system partition in Read/Write mode.
Click to expand...
Click to collapse
O.K. I think I have it now.
So you used to be able to mount the system partition on the phone with S-OFF, the change they made in HBOOT 1.02.000 is what stops it. Thus Universal doesn’t work, and you can’t play on the system partition in the same way. So not only do you now need the XTC Clip, but the options open to you even with that are still more limited than they were…
Is that about right?
[EDIT]
O.K. After re-reading I see that assessment is wrong.
It is that The Clip sets S-Off, which mounts system as rw, then anding su is a separate issue…
Wouldn’t this mean that Universal could theroeticaly work on a system where s-off has been set?
[/EDIT]

FALCON-LORD said:
O.K. I think I have it now.
So you used to be able to mount the system partition on the phone with S-OFF, the change they made in HBOOT 1.02.000 is what stops it. Thus Universal doesn’t work, and you can’t play on the system partition in the same way. So not only do you now need the XTC Clip, but the options open to you even with that are still more limited than they were…
Is that about right?
Click to expand...
Click to collapse
Almost.
Prior to HBOOT 1.02, with ClockworkMod recovery installed, it was able to temporary turn security off and on to mount the /system partition. On the Aria we were never able to get permanent S-OFF via a software solution like some of the other HTC models.
With the XTC Clip, you can now get permanent S-OFF on the Aria which will give you more options, not less options than before. With S-OFF, you are able to mount both the /system and the /recovery partition in Read/Write mode, so you can not only install new ROMs, but also different custom recovery.

FALCON-LORD said:
O.K. I think I have it now.
[EDIT]
O.K. After re-reading I see that assessment is wrong.
It is that The Clip sets S-Off, which mounts system as rw, then anding su is a separate issue…
Wouldn’t this mean that Universal could theroeticaly work on a system where s-off has been set?
[/EDIT]
Click to expand...
Click to collapse
Yes and yes.

O.K. So with that in mind, I go an get the Droid Clipped, it will now be S-Off, which means /system will be set to rw.
Now I need to get su into system/bin, which I won’t have permissions for, that is the next challenge right?
So is there a way to do that without using an entirely custom ROM?

FALCON-LORD said:
O.K. So with that in mind, I go an get the Droid Clipped, it will now be S-Off, which means /system will be set to rw.
Now I need to get su into system/bin, which I won’t have permissions for, that is the next challenge right?
So is there a way to do that without using an entirely custom ROM?
Click to expand...
Click to collapse
I believe once you are s-off you can just adb push it to /system/bin.
Also, there are 2.2.2 roms out there which are basically the stock rom already rooted and ATT crap removed if you want to stay close to stock.

A$$h4t said:
I believe once you are s-off you can just adb push it to /system/bin.
Also, there are 2.2.2 roms out there which are basically the stock rom already rooted and ATT crap removed if you want to stay close to stock.
Click to expand...
Click to collapse
The copy I have doesn’t have all the AT&T Crap, it is a generic unlocked build.
That then means the next question is where do I get a adb to push in su?
[EDIT]
O.K. Further research shows that my question makes no sense…
How do I get a copy of su to push onto the phone using adb
Any quick link to a guide to set up a dev environment and adb?
[/EDIT]
[RE-EDIT]
O.K. I now have ADB Sorted and am punting around on the phones system.
Now what?
Obviously get the phone clipped to make the system volume RW.
But that still doesn't give me the rights to push a file onto the phone, so then what? (And where do i get the file to push?)
I note that originally a version of su was on the phones that only worked from adb. for my current purposes this would suffice
[/RE-EDIT]

FALCON-LORD said:
The copy I have doesn’t have all the AT&T Crap, it is a generic unlocked build.
That then means the next question is where do I get a adb to push in su?
[EDIT]
O.K. Further research shows that my question makes no sense…
How do I get a copy of su to push onto the phone using adb
Any quick link to a guide to set up a dev environment and adb?
[/EDIT]
[RE-EDIT]
O.K. I now have ADB Sorted and am punting around on the phones system.
Now what?
Obviosly get the phone clipped to make the system volume RW.
But that still doesn't give me the rights to push a file onto the phone, so then what? (And where do i get the file to push?
[/RE-EDIT]
Click to expand...
Click to collapse
With the system in an S-OFF state, you can use HBOOT to flash a custom rooted ROM or custom recovery (ClockworkMod) by copying the associated ZIP file to the root of your microSD card and name it LIBEIMG.zip. Next time you boot into HBOOT, it will find the zip file and attempt to install it.
Once you get the Aria clipped, I would pay a visit to the Aria IRC chat room for more specifics and questions. These guys will be able to assist you on the best steps to take.
http://webchat.freenode.net/?channels=#liberatedAria

Follow the directions in this post: http://forum.xda-developers.com/showpost.php?p=13650005&postcount=67
(Not the quoted part, the part that attn1 says to do.) This should install Clockwork on your phone.
Oh, and adb is in the platform-tools folder of the Android SDK and fastboot is in tools folder.

FALCON-LORD said:
O.K. So with that in mind, I go an get the Droid Clipped, it will now be S-Off, which means /system will be set to rw.
Now I need to get su into system/bin, which I won’t have permissions for, that is the next challenge right?
So is there a way to do that without using an entirely custom ROM?
Click to expand...
Click to collapse
S-OFF alone does not make system r/w. You will still have a secure boot image.
The next step will be installing custom recovery, which is a snap once you have S-OFF. From there, you can install whatever you want on system, or flash rooted stock ROMs, or just root routines.
FYI, most people are not happy with just root access; they eventually will want basic busybox services and the ability to customize on the fly.
Come into the IRC channel in my sig if you have questions.
With Radio S-OFF fastboot flash image won't work directly, but this will work to install clockworkmod simply and easily:
Prerequisites:
HTC android usb device driver (if you use windows)
adb and fastboot utilities for your platform
Code:
adb reboot bootloader
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip clockwork2501.zip
fastboot reboot
Download:
MD5: 5d01f06af3ce99f27d23cf8a2df47926 clockwork2501.zip

Thanks tpbklake, drumist & attn1, I think I am getting close to feeling ready to do this.
So as I see it have to do the following.
Prerequisite items
Install HTC Sync (USB Driver)
Install Oracle JDK (Prerequisite for SDK)( http://www.oracle.com/technetwork/java/javase/downloads/jdk-6u25-download-346242.html )
Install SDK (for ADB) (http://developer.android.com/sdk/index.html )
Get copy of clockwork.zip ( http://forum.xda-developers.com/attachment.php?attachmentid=591945&d=1305031790 )
So Once I have all of the ingredients perform the following actions
Find somewhere with an XTC clip to set S-Off
Go home and plug the phone into the PC
Copy clockwork.zip to the root of SD Card
Open a cmd prompt at adb directory (C:\Program Files\Android\android-sdk\platform-tools and enter the following commands
Code:
adb reboot bootloader
cd C:\Program Files\Android\android-sdk\tools
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip clockwork2501.zip
fastboot reboot
So from my reading it appears doing this means I can now load things onto the system partition, by copying them as a zip package onto the SD and then booting into CWM and selecting “install zip from sdcard” and this will allow me to install su.
Is that about the length of it?
So I still need a zip with su in it and then I am able to raise my privileges?

A few corrections:
1) You don't have to install the Oracle JDK for what you are doing, you can skip that step completely.
2) Don't place the clockwork.zip on the SD card. You need to have it on your computer, and it will copy the file over to your phone when you issue the fastboot command. You will want to place it in the tools folder.
3) Before you run the adb/fastboot commands, type the following at the command prompt:
Code:
path %PATH%;C:\Program Files\Android\android-sdk\platform-tools
After doing this you can run all commands from the \tools folder, including adb, until you close that command line box.
4) I believe you need the HBOOT drivers installed on your system (this is in addition to the HTC Sync drivers). Follow the installation directions here: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install

drumist said:
A few corrections:
1) You don't have to install the Oracle JDK for what you are doing, you can skip that step completely.
2) Don't place the clockwork.zip on the SD card. You need to have it on your computer, and it will copy the file over to your phone when you issue the fastboot command. You will want to place it in the tools folder.
3) Before you run the adb/fastboot commands, type the following at the command prompt:
Code:
path %PATH%;C:\Program Files\Android\android-sdk\platform-tools
After doing this you can run all commands from the \tools folder, including adb, until you close that command line box.
4) I believe you need the HBOOT drivers installed on your system (this is in addition to the HTC Sync drivers). Follow the installation directions here: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
Thanks Drumist.
The SDK package wouldn’t install without the JDK installed, so that is why I have added that in, I have changed my steps for where to put clockwork, thanks for the line on path (I should have done that initially…)
Once I have done all of this then I take it I follow some instructions like these?
http://geeknizer.com/how-to-root-motorola-droid/
can I use the su package they have linked there? It looks like these instructions were written for a much earlier droid release.
I take it if that is correct it will look more like this..
Code:
cd C:\Program Files\Android\android-sdk\platform-tools
adb push su /data/local
adb shell su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin mv su osu
cat /data/local/su > su
chmod 6755 su

I'm not sure what the best method is to root an unrooted ROM. My personal recommendation is to just install one of the ROMs from this site that already have root. You can always make a Nandroid backup first in case you don't like the subtle differences between those ROMs and the one you're using now.

[Q] ADB push permission denied while trying to temp root on HTC Glacier via Windows

Hello all,
I'll preface this by saying that I'm completely new to android phones and rooting them so I apologize for being noob in advance.
I have been following this guide (wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide) to a tee and have ended up stuck at #6 with failed to copy/permission denied errors when I attempt to push busybox, superuser, or temp root over to my phone. I believe I have everything in order, such as: having the latest java sdk, installing the latest android sdk at c:\, downloading and installing the latest platform-tools (rev 4) and google usb driver, and changing the variable value section of path to "%SystemRoot%;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools", but i just cannot seem to execute the commands and I'm not sure what I'm doing wrong. I will also add that my phones settings are enabled for usb debugging and disk drive connection to PC.
This is exactly the command I'm trying:
C:\Users\thepaperescape>cd c:\android-sdk-windows\platform-tools
c:\android-sdk-windows\platform-tools>adb push su /sdcard/su
failed to copy 'su' to '/sdcard/su': Permission denied
Any help would be awesome. And sorry to make a new post... I've tried searching for 3 hours but cannot find the exact same incident.
Thanks

thepaperescape said:
Hello all,
I'll preface this by saying that I'm completely new to android phones and rooting them so I apologize for being noob in advance.
I have been following this guide (wiki.cyanogenmod.com/index.php?title=TMobile_myTouch_4G:_Full_Update_Guide) to a tee and have ended up stuck at #6 with failed to copy/permission denied errors when I attempt to push busybox, superuser, or temp root over to my phone. I believe I have everything in order, such as: having the latest java sdk, installing the latest android sdk at c:\, downloading and installing the latest platform-tools (rev 4) and google usb driver, and changing the variable value section of path to "%SystemRoot%;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools", but i just cannot seem to execute the commands and I'm not sure what I'm doing wrong. I will also add that my phones settings are enabled for usb debugging and disk drive connection to PC.
This is exactly the command I'm trying:
C:\Users\thepaperescape>cd c:\android-sdk-windows\platform-tools
c:\android-sdk-windows\platform-tools>adb push su /sdcard/su
failed to copy 'su' to '/sdcard/su': Permission denied
Any help would be awesome. And sorry to make a new post... I've tried searching for 3 hours but cannot find the exact same incident.
Thanks
Click to expand...
Click to collapse
You need to have VISIONary.apk downloaded and installed on your phone. and make sure to run it with Visionary.sh and Set system to r/w both checked. And try it again.
How ever their are much easier methods. This being one of them. Makes sure to go to page two.

neidlinger said:
You need to have VISIONary.apk downloaded and installed on your phone. and make sure to run it with Visionary.sh and Set system to r/w both checked. And try it again.
Click to expand...
Click to collapse
The guide I am using gives instructions on how to root specifically without visionary so I'd like to stick to it's outline but just find guidance on how to make it work.

thepaperescape said:
The guide I am using gives instructions on how to root specifically without visionary so I'd like to stick to it's outline but just find guidance on how to make it work.
Click to expand...
Click to collapse
okay.
I've seen alot of people try this method and very little come out okay.
you need SU access to push objects to the phone. The phone is seeing it as a foreign object and is wanting to prevent it from being pushed. The only other option you'd have is to turn on mass media storage and drop/drag the objects to the root of the SDcard.

Agreed with neidlinger, if I'm not mistaken you must have atleast temproot to be able to use the command 'SU' as it stands for superuser and as ridiculous as it sounds you are not the superuser of your phone, Google is
Sent from my HTC Glacier using XDA Premium App

Nicgraner said:
Agreed with neidlinger, if I'm not mistaken you must have atleast temproot to be able to use the command 'SU' as it stands for superuser and as ridiculous as it sounds you are not the superuser of your phone, Google is
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
SU was actually Switch User but Super User is used ATM due to the confusion it created to the newbies a decade ago who didn't understand how permission base structure on *nix worked. Which always required chmod and whole rwx thing even made it more confusing so they preallocated it with [email protected] with UiD:0 as default permission.
Now what I like to know is why are you using that howto? As neidlinger stated just run VISIONary+ to get TempROOT and then do root.sh to obtain PermROOT. If you need to unlock the CiD just call TMo and get the code free as no need to risk it. But if you still want Radio S=OFF then just do the simple gfree step and you will have it.

You shouldn't need temproot to push a file to your sd card. Have you made sure the file is in the same folder as adb directory?

UsrBkp said:
Now what I like to know is why are you using that howto?
Click to expand...
Click to collapse
Well for one, I chose that guide because my goal is to install cyanogen and that is found directly off their site regarding my phone. My expectation is that a group of developers so renowned for their contributions should be able to correctly explain how to get to the point of install. Still I know it's a wiki, and things are constantly changing (generally faster than the wiki). For instance, I did notice that the wiki was incorrect about the location of the google usb drivers post download. I assume that is due to the newer version of the sdk i installed. And the jdk r25 is pretty new and I believe that to be one of the other things causing me problems, but I don't know for sure.
neidlinger said:
The only other option you'd have is to turn on mass media storage and drop/drag the objects to the root of the SDcard.
Click to expand...
Click to collapse
I tried doing this for those two files (su and superuser) that are supposed to be pushed onto the sd root and i thought it worked. cmd allowed me to push the other three files into /data/... no problem. chmod to 0755 even seemed to work (it neither explicitly approved or denied). but then when I got to step 8, terminal on the phone said i did not have access to run that command.
shuka325 said:
You shouldn't need temproot to push a file to your sd card. Have you made sure the file is in the same folder as adb directory?
Click to expand...
Click to collapse
That's what I figured based off of the guide (since it's a guide on GETTING TO temproot, but what do I know... i'm supernoob. I've attached an image to see if you can see ANYTHING wrong with what I'm trying to do.
Thanks for everything guys!

I would give up that guide and use VISIONary to gain Temp Root & Root.sh to obtain perm Root. Then install the latest rom manager and make sure CWM sticks. Then you can flash CM7, or any other ROM for that matter.

Is there any guide you all think stands above the rest?!?!

thepaperescape said:
Is there any guide you all think stands above the rest?!?!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=13989736&postcount=6

[Q] Cant root using anything and got 1.34.405.5

I dont know whats wrong but suddenly i cant root my device after i downgraded to 1.34 .. I need to turn S-ON because my device needs to go for repairs.. I follow this guide:
http://forum.xda-developers.com/showthread.php?t=928671
but for some reason when i try to launch psneuter i get some wierd permission denied error..
Code:
adb push psneuter /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
1841 KB/s (265118 bytes in 0.140s)
adb shell chmod 777 /data/local/tmp/psneuter
adb push adb shell /data/local/tmp/psneuter
PK♥8+: permission denied
∩♣ÿ☼: permission denied
☼: permission denied
/data/local/tmp/psneuter: 6: Syntax error: "|" unexpected
so im stuck ! Any suggestions ?

Da9L said:
I dont know whats wrong but suddenly i cant root my device after i downgraded to 1.34 .. I need to turn S-ON because my device needs to go for repairs.. I follow this guide:
http://forum.xda-developers.com/showthread.php?t=928671
but for some reason when i try to launch psneuter i get some wierd permission denied error..
Code:
adb push psneuter /data/local/tmp
adb server is out of date. killing...
* daemon started successfully *
1841 KB/s (265118 bytes in 0.140s)
adb shell chmod 777 /data/local/tmp/psneuter
adb push adb shell /data/local/tmp/psneuter
PK♥8+: permission denied
∩♣ÿ☼: permission denied
☼: permission denied
/data/local/tmp/psneuter: 6: Syntax error: "|" unexpected
so im stuck ! Any suggestions ?
Click to expand...
Click to collapse
I guess as you've already achieved root / S-OFF etc, you find the command to S-ON there will probably be a command switch to S-OFF. Failing that, when I S-OFF'd, it produced a backup.

craiglay said:
I guess as you've already achieved root / S-OFF etc, you find the command to S-ON there will probably be a command switch to S-OFF. Failing that, when I S-OFF'd, it produced a backup.
Click to expand...
Click to collapse
Yes i do currently have S-OFF but need S-ON again because the phone is beeing returned for repairs..

Might be able to use rage, for temp root.
Sent from my HTC Vision using XDA Premium App

Re reading your post, i'm not sure psneuter is root for 1.34 i used it to get temp root on 1.72 downgraded and used rage for root on 1.34. Look in android development for the guide to downgrade and root (no links on app) start at after the 1.34 flash bit. gfree is the app that s-off so its likely gfree can also s-on. Running gfree with no switches should give a manual page, or just search gfree switches. (I'm not responsible for bricks etc!!)
Edit, rage gives temp root on 1.34
Sent from my HTC Vision using XDA App

Okay so i've managed to get root on the device ! Finally..
However i still have trouble running gfree.. i've tried a few methods but it gives me the same output
Code:
# /data/local/gfree -r /sdcard/part7backup-1298979588.bin
/data/local/gfree -r /sdcard/part7backup-1298979588.bin
/data/local/gfree: 1: Syntax error: ")" unexpected
# /data/local/gfree -s on -c HTC__Y13
/data/local/gfree -s on -c HTC__Y13
/data/local/gfree: 1: Syntax error: ")" unexpected
I "think" i managed to get root.. when i write 'adb shell' i dont go directly to a root shell, but only '$'. Writing 'su' phone ask me if i want to let permission to give a root shell which i accept whereafter i get the '#'
EDIT: Just tried it again using a newer version of gfree.. (The one i used above was 0.4) Same problems with gfree 0.7. But i have an idea that it can be because of this:
When i download the file 'gfree_07.zip' am i supposed to just rename this file to only 'gfree' without any extension and then with push it to phone with 'adb push gfree /data/local/' ? OR am i supposed to open the zip file and extract the gfree file within it and then push that file to the phone ?

Yes, you must unzip gfree_0x.zip file and move the extracted gfree binary file to your phone as instructions (and this thread) states. Good luck!!!
How I wish we wouldn't need to do this kind of trickery just to use our own phones as we wish...

Let us know if it eork. Ive been having the same trouble
Sent from my GT-P1000T using XDA Premium App

[Q] problem downgrading gingerbread htc panache (2.3.3)

I hope somebody can help me with this little anomaly.
Been trying to downgrade htc panache with gingerbread 2.3.3.
I was able to successfully execute the cmds listed on the guide http://forum.xda-developers.com/showthread.php?t=1178912; however, when i try to downgrade the misc_version, I get the following error:
> adb push misc_version /data/local/tmp/misc_version
> adb push flashgc /data/local/tmp/flashgc
> adb shell chmod 777 /data/local/tmp/*
> adb shell
> cd /data/local/tmp
# ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0: PERMISSION DENIED
According to the guide I should have seen something like this (--set_version set. VERSION will be changed to: 1.00.000.0
Patching and backing up partition 17...)
I was also not sure as to when the cmd "adb push PD15IMG.zip /sdcard/PD15IMG.zip" be executed, before or after downgrading? And when doing this should I have my regular SD card or gold card inserted in the phone?
I wasn't able to find the solution to the problem. Hope you can be of help

The correct tutorial to root the Panache is here :
http://forum.xda-developers.com/showpost.php?p=16858971&postcount=98
Be sure your sdcard is not mounted and usb debugging is enable.
The misc command must be execute with your regular sdcard.
The PD15IMG. zip must be pushed on your goldcard and is only used in the next step (dowgrading to froyo)
Regards
Sent from my HTC Panache / CM7 using xda premium.

thanks...i'll give it a try

SprigganMaster said:
The correct tutorial to root the Panache is here :
http://forum.xda-developers.com/showpost.php?p=16858971&postcount=98
Be sure your sdcard is not mounted and usb debugging is enable.
The misc command must be execute with your regular sdcard.
The PD15IMG. zip must be pushed on your goldcard and is only used in the next step (dowgrading to froyo)
Regards
Sent from my HTC Panache / CM7 using xda premium.
Click to expand...
Click to collapse
I gave it a try...I followed the guide precisely. Everything goes smoothly until I reach the "Change Version" section. When i try to downgrade the misc version i keep getting PERMISSION DENIED.
The error is generated after executing this command: "# ./misc_version -s 1.00.000.0"
I have been at this days, but with no luck.

Check your bootloader version if its 86.000 then u can use gingerbreak to root
Sent from my HTC Glacier using xda premium

allendon said:
I hope somebody can help me with this little anomaly.
Been trying to downgrade htc panache with gingerbread 2.3.3.
I was able to successfully execute the cmds listed on the guide http://forum.xda-developers.com/showthread.php?t=1178912; however, when i try to downgrade the misc_version, I get the following error:
> adb push misc_version /data/local/tmp/misc_version
> adb push flashgc /data/local/tmp/flashgc
> adb shell chmod 777 /data/local/tmp/*
> adb shell
> cd /data/local/tmp
# ./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0
./misc_version -s 1.00.000.0: PERMISSION DENIED
According to the guide I should have seen something like this (--set_version set. VERSION will be changed to: 1.00.000.0
Patching and backing up partition 17...)
I was also not sure as to when the cmd "adb push PD15IMG.zip /sdcard/PD15IMG.zip" be executed, before or after downgrading? And when doing this should I have my regular SD card or gold card inserted in the phone?
I wasn't able to find the solution to the problem. Hope you can be of help
Click to expand...
Click to collapse
You are doing something wrong in step 6 of the temp root guide.... Step 6 is successful if your device is kicked out of adb shell...... If you have the 86.0000 bootloader just install gingerbreak and root your phone no nees to follow all these steps
Sent from my HTC Glacier using xda premium

mansisingh said:
You are doing something wrong in step 6 of the temp root guide.... Step 6 is successful if your device is kicked out of adb shell...... If you have the 86.0000 bootloader just install gingerbreak and root your phone no nees to follow all these steps
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
GingerBreak worked great on my Panache. My bootloader was 86.0000

mansisingh said:
You are doing something wrong in step 6 of the temp root guide.... Step 6 is successful if your device is kicked out of adb shell...... If you have the 86.0000 bootloader just install gingerbreak and root your phone no nees to follow all these steps
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Ok, I managed to get through. Step 6 was successful. It was able to find an exploit at the end, then it kicks the device out of adb shell.
I skipped the temp rooting backup guide as i have nothing to backup.
Next I pushed the PD15IMG.zip file in to the sd card and rebooted. It scanned it but nothing happened. The guide said it was expected so I rebooted inserted the gold card and tried again. Nothing happened. It scanned the .zip file and remained at the bootloader screen. No t-mobile splash or anything like the guide says. This is what I see:
GLACIER PVT SHIP S-ON
HBOOT-0.89.0005
MICROP-0429
RADIO-26.09.04.26_M
eMMc-boot
What am I doing wrong? Could it be the .zip file is defective? I couldn't access the link for that file on the guide. megaupload is blocked, so i had to download it from elsewhere. It is 10.2 MB and has one radio.img file and another android-info .txt file.
Please help

mansisingh said:
You are doing something wrong in step 6 of the temp root guide.... Step 6 is successful if your device is kicked out of adb shell...... If you have the 86.0000 bootloader just install gingerbreak and root your phone no nees to follow all these steps
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Please don't spread misinformation. Gingerbreak only works if you are already S-OFF. It is not going to work on the Panache which comes with the 0.89 HBOOT. If your Panache mysteriously came with 0.86 then it's an anomaly and you got lucky.
Also from my experience, you can do everything using one gold card - you don't need a separate non-gold SD to make any particular things happen.
---------- Post added at 12:17 PM ---------- Previous post was at 12:13 PM ----------
The 10 MB files are just radio files. That's not what you need.
For the correct downgrade file, the MD5 checksum is 49D07F0EE7DE1765A6A84CB12FA53110. There is another copy available at the following links:
http://www.multiupload.com/QZS83O5L1U
http://cmw.22aaf3.com/glacier/stock/1.17.531.2/PD15IMG.zip
http://goo-inside.me/ruu/glacier/fu....140e_26.03.02.26_M_release_155771_signed.zip

It worked! the problem was i didn't have the right PD15IMG file.
I'm now rooted with s-off and froyo.
Thanks very much
I noticed that my bootloader was downgraded to 0.85 and not 0.86. Is that OK?

I think you should be ok
congrats on the rooting

allendon said:
It worked! the problem was i didn't have the right PD15IMG file.
I'm now rooted with s-off and froyo.
Thanks very much
I noticed that my bootloader was downgraded to 0.85 and not 0.86. Is that OK?
Click to expand...
Click to collapse
Yay! Once you have Radio S-OFF your bootloader version doesn't really matter anymore, because no matter what you flash you're still S-OFF.

cmstlist said:
Yay! Once you have Radio S-OFF your bootloader version doesn't really matter anymore, because no matter what you flash you're still S-OFF.
Click to expand...
Click to collapse
Ehhh...Not really. Your bootloader is really important because you will either stay with the .86 one or your root method will flash the engineering H-boot which is .85.2007, The engineering H-boot is essential for things like reviving bricks (brick is not when your eMMC fails) and flashing things like recovery.img's and custom splash screens.

Nicgraner said:
Ehhh...Not really. Your bootloader is really important because you will either stay with the .86 one or your root method will flash the engineering H-boot which is .85.2007, The engineering H-boot is essential for things like reviving bricks (brick is not when your eMMC fails) and flashing things like recovery.img's and custom splash screens.
Click to expand...
Click to collapse
Even without ENG HBOOT, once you have Radio S-OFF, any version bootloader will accept an unsigned PD15IMG.zip. You can recover from bricks, flash recovery and splash screens from there too.
Sent from my Nook Color!

REply
cmstlist said:
Please don't spread misinformation. Gingerbreak only works if you are already S-OFF. It is not going to work on the Panache which comes with the 0.89 HBOOT. If your Panache mysteriously came with 0.86 then it's an anomaly and you got lucky.
Also from my experience, you can do everything using one gold card - you don't need a separate non-gold SD to make any particular things happen.
---------- Post added at 12:17 PM ---------- Previous post was at 12:13 PM ----------
The 10 MB files are just radio files. That's not what you need.
For the correct downgrade file, the MD5 checksum is 49D07F0EE7DE1765A6A84CB12FA53110. There is another copy available at the following links:
Click to expand...
Click to collapse
These links don't seem to be dead... Are there any other links you can post??

Sorry, I don't own the Panache anymore.
Sent from my Nexus 7 using Tapatalk HD