Database Users

Want to root my legend 2.2 ota... wwe_3.15.405.3-2

I read many thread but didn't find clear answer for this question.
I have a vodafone htc legend with froyo updated trought ota
I would, root it and install HTC rooted rom.
any body can help with the steps and tools need it?
thanks a lot

follow this http://android.modaco.com/content/htc-legend-legend-modaco-com/323201/downgrading-from-froyo-ota/

it is not rooting, it is downgrade, what's not same

rolks said:
it is not rooting, it is downgrade, what's not same
Click to expand...
Click to collapse
he have official froyo... then he must downgrade first or what??
FIRST HAVE TO DOWNGRADE
follow this http://android.modaco.com/content/htc-legend-legend-modaco-com/323201/downgrading-from-froyo-ota/
Click to expand...
Click to collapse
THEN U CAN ROOT
http://theunlockr.com/2010/06/07/how-to-root-the-htc-legend/

Great!
If I undertood right...
First downgrade (this is something we could not avoid) then root.
Let me try!
Ill back!
Thanks

MontseCat said:
Great!
If I undertood right...
First downgrade (this is something we could not avoid) then root.
Let me try!
Ill back!
Thanks
Click to expand...
Click to collapse
i followed these steps and now i have rooted legend with BlaYo ROM B 0.2...
GOOD LUCK

I tried yesterday and having some troubles with Android sdk, doesn't work I don't know if any trouble with its installation.
Need to read carefully the instalation process and try again.
The only issue is find time for ths... its chrismas so, some familiar meetings
I'll back!

Oh!
I tried once again with not succes.
when running "crackin"...
starts with...
"Copying tools"
"adb" is not recogniced as command internal or external
program or file executable...
And remainds with same message for serveral lines till finish!!
Nothing happens.
I installed the android sdk package and added the hack4legend-v5.zip contenst on android-sdk-windows\tootls folder
Obviously I am doing something wrong but I am not able to locate where the problem or mistake is!!
any idea?
thanks

I downgraded my Legend from the OTA 2.2.
Now the ROM version is 1.31 which should be correct, but the HBOOT version still is 1.00, which is according to this guide (http://forum.xda-developers.com/showthread.php?t=746454 ) the wrong one, it should be 0.43.... any ideas on this one?
Edit: @MontseCat: have you installed your USB drivers? The come with HTC Sync from the HTC homepage. Otherwise you can check adb functionality by opening a console window, running 'cd C:\Absolute\Path\containing\adb.exe\' (for Windows users, I guess Linux users know how to use cd) and then 'adb devices'. This should show a number refering to your device, opposed to simply nothing if it is not working.

nae64 said:
Edit: @MontseCat: have you installed your USB drivers? The come with HTC Sync from the HTC homepage. Otherwise you can check adb functionality by opening a console window, running 'cd C:\Absolute\Path\containing\adb.exe\' (for Windows users, I guess Linux users know how to use cd) and then 'adb devices'. This should show a number refering to your device, opposed to simply nothing if it is not working.
Click to expand...
Click to collapse
Sorry I don't follow you at all.
I currently have my legend working with HTC Sync, witout problems, so don't undesrtand, shall I remove an reinstal it after installed android sdk to?? or..
thanks

No, that was just my problem at first when I had to move to a Windows PC for the downgrade, adb requires HTC Sync. So you should be fine.
But now that I read your problem again, my solution would not even fit I guess your tools directory does not contain the adb.exe. But the directory platform-tools in the android-sdk folder does. I just copied over the contents of the hack zip to platform-tools and did it from there... what ever, now I am having the problem i described above...

nae64 said:
I downgraded my Legend from the OTA 2.2.
Now the ROM version is 1.31 which should be correct, but the HBOOT version still is 1.00, which is according to this guide (http://forum.xda-developers.com/showthread.php?t=746454 ) the wrong one, it should be 0.43.... any ideas on this one?
Edit: @MontseCat: have you installed your USB drivers? The come with HTC Sync from the HTC homepage. Otherwise you can check adb functionality by opening a console window, running 'cd C:\Absolute\Path\containing\adb.exe\' (for Windows users, I guess Linux users know how to use cd) and then 'adb devices'. This should show a number refering to your device, opposed to simply nothing if it is not working.
Click to expand...
Click to collapse
Hmm my HBOOT version is 1.01
Sent from my HTC Legend using XDA App

Okay, thank you very much, root completed successfully even with HBOOT v1.00

nae64 said:
... But the directory platform-tools in the android-sdk folder does. I just copied over the contents of the hack zip to platform-tools and did it from there... what ever, now I am having the problem i described above...
Click to expand...
Click to collapse
I done as you said and succed,
Now the problem is
CR--rw----
So fails
the message at the end is xxxx permision denied.
I don't konw how to put an image of the scren. sorry
what whall I do now?

MontseCat said:
I done as you said and succed,
Now the problem is
CR--rw----
So fails
the message at the end is xxxx permision denied.
I don't konw how to put an image of the scren. sorry
what whall I do now?
Click to expand...
Click to collapse
- Temproot with VISIONary r13 (install the downloaded file as per a normal APK)
- Once you are temprooted, connect via 'adb' and do 'su' (to get root) then '/data/local/flash_image misc /data/local/misc1-2.img'
You should then be able to downgrade in the normal way.

janarp said:
- Temproot with VISIONary r13 (install the downloaded file as per a normal APK)
- Once you are temprooted, connect via 'adb' and do 'su' (to get root) then '/data/local/flash_image misc /data/local/misc1-2.img'
You should then be able to downgrade in the normal way.
Click to expand...
Click to collapse
Ok I Istalled the Visionary and temorary root,
I don't know how to connect via 'adb' and do su...
so, just stoped here and waiting next instruction. Sorry work as neel!!

[HOW-TO] ADB for Dummies(How-To Learner's Guide)

janarp said:
[HOW-TO] ADB for Dummies(How-To Learner's Guide)
Click to expand...
Click to collapse
even with this guide I didn't succed!!!
What I done is just temporary root with visionary then run again the adb but remains the same,
sorry I don't see where lost!!

In the following I will assume a Windows-PC:
1. Restart your phone to start from scratch, make sure 'TempRoot on boot' (or sth along this line...) is NOT checked
2. Run the crackin.bat, which you put (along with all other files in that download) into the directory containing the adb.exe (which is, at least for me, the platform-tools directory)
3. when it fails (it will), TempRoot using VISIONary, leaving everything unchecked (no System Read Write, even if that seems like a good idea)
4. on your PC, go to a Terminal (Windowsbutton + R, enter 'cmd' without quotes, press enter) , navigate to the folder crackin.whatever is in using the cd command like in my following example, but with the correct, full path
Example: 'cd "C:\\Programm Files\Android\andorid-sdk\platform-tools"' (again, without the single quotes (preserve doublequotes))
5. in that same Terminal Window, enter 'adb shell' (again, without quotes). The prompt should change to a dollar sign. Then enter 'su' (you know, without quotes...), and when the prompt changes to a '#', the TempRoot was successful and we can resume. Make sure to leave that Terminal open, you can use it again when rooting.
6. On a Windos System (32bit preferred) run the RUU.something.exe and follow these steps.
7. follow the main rooting guide, in which you will have to open a Terminal Window in the directory you unzipped. This is done with the same method I described above (opening cmd, 'cd' command)
I hope this makes it more clear =)
Edit: btw, this is a full guide, feel free to pick out the stuff you need, because I really did not understand what your problem was =) as a rooting guide I used this: http://forum.xda-developers.com/showthread.php?t=746454

MontseCat said:
even with this guide I didn't succed!!!
What I done is just temporary root with visionary then run again the adb but remains the same,
sorry I don't see where lost!!
Click to expand...
Click to collapse
i belive u have same folder names like me...
first i connect my phone with pc then i open command (start and type cmd)
Code:
cd C:\android-sdk-windows-1.1_r1\tools
then
Code:
adb shell
and then
Code:
su
and then follow nae64 post
point 6 and 7

Root - MT4G

Is there any way to root the MT4G without using a computer?
Sent from my HTC Glacier using XDA App

Yes. I was able to using visionary r14 & terminal emulator.
Find Grankins thread on rooting for step by step.
Sent from my HTC Glacier using XDA App

pvchip3 said:
Is there any way to root the MT4G without using a computer?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Fast easy and fairly safe way, Visionary Plus r14. One click root for temp and perma-root. Usually I do not recommend the 'easy way' method because I think everyone should learn how to actually root the 'hard way' just in case.. but I have to admit Visionary Plus works perfectly on the MT4G and is fast and simple as well as fairly safe. I suggest you use the temp root option first, this way if there is any issues with your device a simple reboot will fix it.

Thanks guys I now have S=OFF and this a new replacement from TMO
Sent from my HTC Glacier using XDA App

What all did you do?

PostaHTC said:
What all did you do?
Click to expand...
Click to collapse
i cannot speak of the person @ hand
The three needed items
you download VISIONary.apk
download the Root.sh file .zip and sore the folder with the script file inside the folder on the root of the SD card
download Terminal Emulator from the Android Market
How to do it
Run VISIONary and temp root w/ visionary.sh and set system to r/w after root checked
go into the Term Emul and type "SU". The $ sign should change to a #
if it does
cd /sdcard/root
sh root.sh
Click to expand...
Click to collapse
reboot into bootloader and make sure s=off.

Ok do I every hit Perm-Root?

PostaHTC said:
Ok do I every hit Perm-Root?
Click to expand...
Click to collapse
i never did. Once you turn s=off it will not check for that. after you reboot you will need to hit temp root one more time.

I'm trying it as we speak....
I temp-root?
Then I run the commands?
Then I temp-root one last time
Then Turn Off and S should be off....RIGHT?

I did a recent root though perm one. It was through a youtube video and a guide from this forum! look for perm root and s=off thread. its posted by the person who did ultimate true root and s=off.
and use visionary r11, if you dont like the manual way. thats really quick and good as well. but i dont take any responsibility though for any bricking to your phone from this suggestion xD.

PostaHTC said:
I'm trying it as we speak....
I temp-root?
Then I run the commands?
Then I temp-root one last time
Then Turn Off and S should be off....RIGHT?
Click to expand...
Click to collapse
I need to know what you have done so far
steps are:
Download files, temp root, run sh root.sh, reboot, no need to perm root from visonary
edit:
Go here:
http://forum.xda-developers.com/showthread.php?t=858996
And get the eng boot (optional steps at thhe end of the guide), its a must if you wanna start playin around with ur phone
Sent from my rooted glacier running CM7 and grankin's oc kernel

I'm doing the first steps to get S-Off but it's still S-On

I'm uploading a video to show you wat I'm doing

PostaHTC said:
I'm uploading a video to show you wat I'm doing
Click to expand...
Click to collapse
So, still no progress?
I need details though, like, what files have you downloaded, what steps, and everything.
Details bro, details.

http://www.youtube.com/watch?v=M6DrLUau8mE

PostaHTC said:
http://www.youtube.com/watch?v=M6DrLUau8mE
Click to expand...
Click to collapse
k, I saw the vid, the problem is you are still running bootloader version 0.86 and we want to be on eng bootloader, 0.85.
Ok, try this:
First off: we need the SDK, get it from google here: http://developer.android.com/sdk/index.html
Download the version that works for you, once it downloads (it is a .zip), extract it on your C:/ directory and for working purposes we will rename it to: "androidsdk". you have to launch the SDK manager, let it update and then read what follows:
Alternative Root Process
First, uninstall visionary and superuser and restart your device to wipe out temp root.
Second, download MT4G Modperm.zip and unzip its contents to your sdk platform - tools directory. (will be at C:/androidsdk/platform-tools
MT4G Modperm.zip: http://www.mediafire.com/?eaw0q0zjc7rrrwh
MD5Sum: 3ea4a7a6ddee711d12f7350ce60fae33
Then:
Windows Users:
1a. Using Explorer navigate to the root of your sdk. Hold shift and right mouse click on the platform-tools folder. Select "Open command window here". Or, open a command prompt, type:
cd /androidsdk/
cd platform-tools/
2a. Type "adbbat" + enter. Wait till the batch file finishes. (this will only work if the file we downloaded (MT4G mod perm) is extracted at C:/androidsdk/platform-tools (make sure that you do not create an extra folder within the platform-tools directory)
2. Disconnect your phone from the PC.
3. Open terminal emulator on the phone and type "/data/local/rage" + enter. Wait for "Forked XXXXXXXX children" to appear and then close the terminal.
4. Start terminal back up. It should force close.
5. Start terminal back up, again. This time it should stay open and you should have a "#" prompt instead of a "$" prompt. Then type "/data/local/temp.sh"
6. When the script finishes run /data/local/rage again and sit tight. The phone should start acting weird and do a soft reboot. Then right after everything loads it should do a hard reboot. (the phone might not reboot twice, if it does not, then you can reboot manually into bootloader and S=Off and Hboot 0.85 should be there)
7. Enjoy root!

PostaHTC said:
http://www.youtube.com/watch?v=M6DrLUau8mE
Click to expand...
Click to collapse
you didn't read what i said.
Run Visionary.sh after root should be checked
as well as
set system r/w after root.
Both of those HAVE to be checked.
As far as why you still have s=on, i have no clue.
I followed the method posted @ the unlockr (the first time i rooted my phone) link to the unlcokr. The second time i rooted my phone i followed the Wiki posted via Cyanogen Link to their Wiki page, and both of them worked perfectly.
If you want me to make a YouTube video for you showing you how to get s=off i will be more than glad to.

everest.deth said:
k, I saw the vid, the problem is you are still running bootloader version 0.86 and we want to be on eng bootloader, 0.85.
Click to expand...
Click to collapse
the first time i rooted my phone i didn't flash the Engineering Bootloader. The only current reason you need that is to flash slash images.

neidlinger said:
i cannot speak of the person @ hand
The three needed items
you download VISIONary.apk
download the Root.sh file .zip and sore the folder with the script file inside the folder on the root of the SD card
download Terminal Emulator from the Android Market
How to do it
Run VISIONary and temp root w/ visionary.sh and set system to r/w after root checked
go into the Term Emul and type "SU". The $ sign should change to a #
if it does
reboot into bootloader and make sure s=off.
Click to expand...
Click to collapse
that didnt work for me. infact, anything that involves visionary doesnt work for me

sheek360 said:
that didnt work for me. infact, anything that involves visionary doesnt work for me
Click to expand...
Click to collapse
You could try Cyanogen's method.

Having trouble rooting on Windows 7 64bit

I am having a bit of difficulty rooting my g2. I am not sure if its related to my os or not but i can not get it to work.
I have followed this and tried it all kinds of different ways.
addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/[/url]
I can get to my run command after doing all of that and it shows my serial number after typing adb devices but after that i can't enter any info in the sdk run command promt.
I have not been able to gain temp root yet because it won't let me enter the commands. I went to try to re-install java/sdk manager yet again and now it says java is not in the right path.
Any help?

If you're having troubles with ADB, why use it? You don't need ADB anymore to root the G2. It can all be done by placing the files on the SD card and running Terminal Emulator on the phone. You can run any of the prompts from ADB in the phone instead. I rooted my first G2 this way. It took some getting used to coming from a phone with a 1-click root, but it wasn't hard.
Check the Wiki, pretty sure it outlines this method as well.

martonikaj said:
If you're having troubles with ADB, why use it? You don't need ADB anymore to root the G2. It can all be done by placing the files on the SD card and running Terminal Emulator on the phone. You can run any of the prompts from ADB in the phone instead. I rooted my first G2 this way. It took some getting used to coming from a phone with a 1-click root, but it wasn't hard.
Check the Wiki, pretty sure it outlines this method as well.
Click to expand...
Click to collapse
Do you have a link for that method i would be glad to try it but i am not sure what to search for, cant find it under rooting g2 with sd card
Also i am trying to gain permanent root if possible

901-Memphis said:
Do you have a link for that method i would be glad to try it but i am not sure what to search for, cant find it under rooting g2 with sd card
Also i am trying to gain permanent root if possible
Click to expand...
Click to collapse
Yep let me grab a link for you (theres actually a video tutorial I wanna try and find). But basically instead of using ADB to push the files to the correct location, you just have to manually put the files in the right locations on the SDcard, which is where ADB pushes them anyways.
K so I followed this method: http://www.youtube.com/watch?v=tU9zn_BEth4
The files he refers to are in this thread: http://forum.xda-developers.com/showthread.php?t=833965
Now different people have had different issues with this. I personally had some issues where it tells you to run #sync, because my perm root wouldn't stick properly after reboot. If this doesn't work properly, I'm sure someone can help you with your drivers to get ADB working.
I should also say that you don't necessarily have to do this method with the initial temp root via visionary, you can simply do the one outlined in the Wiki for rooting (aka http://forum.xda-developers.com/showthread.php?t=834228 ), but just place the files manually and run the commands in terminal emulator.

If you got the adb devices command to work you are actually in good shape. You are supposed to enter all of the commands from what you are calling the "run command" prompt anyway (the one you used for adb devices).

martonikaj said:
I should also say that you don't necessarily have to do this method with the initial temp root via visionary, you can simply do the one outlined in the Wiki for rooting (aka http://forum.xda-developers.com/showthread.php?t=834228 ), but just place the files manually and run the commands in terminal emulator.
Click to expand...
Click to collapse
Unfortunately this won't work (if you don't want to use ADB, Visionary must be used to get temp root). ADB is needed in order to push the files directly to the phone. If you try copying the files to the SD card first, you won't have the correct permissions to copy the files to the phone in Terminal. You are also not allowed to execute programs directly from the SD card (mounted as noexec), so you can't try to obtain temp root from there. If you want to use the gfree method of rooting without using ADB, I made a guide using Visionary for the temp root here: http://forum.xda-developers.com/showthread.php?t=928160.
But the OP actually has ADB working, so he should be able to use any of the guides.

This is the error i get now if i try to enter anything in the sdk manager run prompt box. Is there some place else i should be entering the commands?
Uploaded with ImageShack.us

901-Memphis said:
This is the error i get now if i try to enter anything in the sdk manager run prompt box. Is there some place else i should be entering the commands?
Click to expand...
Click to collapse
You are supposed to be using the regular command prompt (I think you referred to it as the "run command prompt" earlier). It is the prompt in which you successfully ran the "adb devices" command. That is the only prompt you need to use.

Do i enter commands 1 at a time or all at once?

901-Memphis said:
Do i enter commands 1 at a time or all at once?
Click to expand...
Click to collapse
First off, Yes you enter each line as you see it.
Second just to make sure you are in the right area to enter these commands, to get to command prompt you can either search for it from the start menu or hold the "windows button + R".
That opens your run command from there type in "cmd" and that opens command prompt.
Next make sure your current directory is the one you installed adb into. To get to that you can type "cd C:/...... whatever folder you installed it to."
To make sure my adb is working I usually type "adb devices" and see if my phone shows up.
Good luck

Glad to see someone else from the good ole 901 around here =)
Sent from my HTC Vision using XDA App

Okay does anyone have a better guide to rooting?
I got all the way to pushing all the files on the sd card and running the terminal emulator where it shows forked children, reboots the terminal emulator and then i can not enter /data/local/gfree -f
sync
It wont find that file

901-Memphis said:
Okay does anyone have a better guide to rooting?
I got all the way to pushing all the files on the sd card and running the terminal emulator where it shows forked children, reboots the terminal emulator and then i can not enter /data/local/gfree -f
sync
It wont find that file
Click to expand...
Click to collapse
try pushing the file to that folder again

Re-Tried everything at least 3 times, including pushing the files that didn't go.
I give up Ive spent so much time on this only to have it fail at the most unlikely times.
Will wait for another method to root come available

You could try downloading and installing Droid Explorer. It installs adb and fastboot files in its install folder.

Are you sure you actually pushed all of the needed files to your phone correctly (i.e., no errors appeared when doing so)? Which guide are you following and what were the specific errors you are getting? Once you have temp root, running gfree and obtaining permanent root only takes a few more minutes...
Also, did you try any other guides (like the one I linked to earlier)? If you are waiting for a new method of rooting, you might be waiting for a while (since the existing methods work, I don't know how actively people are working on new methods).

ianmcquinn said:
Are you sure you actually pushed all of the needed files to your phone correctly (i.e., no errors appeared when doing so)? Which guide are you following and what were the specific errors you are getting? Once you have temp root, running gfree and obtaining permanent root only takes a few more minutes...
Also, did you try any other guides (like the one I linked to earlier)? If you are waiting for a new method of rooting, you might be waiting for a while (since the existing methods work, I don't know how actively people are working on new methods).
Click to expand...
Click to collapse
Using this guide
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
I get an error when i attempt to enter this into the emulator on my phone
adb shell chmod 777 /data/local/gfree
and it doesn't do anything

901-Memphis said:
Using this guide
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
I get an error when i attempt to enter this into the emulator on my phone
adb shell chmod 777 /data/local/gfree
and it doesn't do anything
Click to expand...
Click to collapse
You are supposed to do that command from your computer. (The instructions state "On the computer, open terminal and type the following commands".) Here, terminal means the command prompt that you've been running all of you other ADB commands from.
If you wanted to run the command from terminal on your phone, you would just type "chmod 777 /data/local/gfree".

You don't need ADB for G2s.

trance2315 said:
You don't need ADB for G2s.
Click to expand...
Click to collapse
Can someone link me a better guide for my G2 so that i can try this 1 more time ?
Maybe a link to the top choices for versions of android to run once i get it rooted?

[Q] Unable to ADB Remount XOOM...!!

Hi..!! Everyone I tried everything, I was going to unlock and root my xoom but I got stuck at this step:
7. fastboot flash boot rootboot.img
I get this error: "can't load rootboot.img"
I run fastboot reboot command and works, after reboots I try adb devices and my xoom shows but if I run adb remount I get this error:
"remount failed: Operation no permitted"
I tried everything search everywhere, update everything and NADA, I'm on a Windows 7 64bit.
Thanks and I hope somebody can direct me to the right path..

You will want to grant root access again using the adb commands. This happened to me once. You don't have permission to do this because it needs to have root access to carry on this operation. Try the root commands again to grant root access and then see what it does when trying to flash the rootboot files.
If that's not it come let us know. XDA will have your answer for sure.
Sent from my Droid using XDA Premium App

diablo2224 said:
You will want to grant root access again using the adb commands. This happened to me once. You don't have permission to do this because it needs to have root access to carry on this operation. Try the root commands again to grant root access and then see what it does when trying to flash the rootboot files.
If that's not it come let us know. XDA will have your answer for sure.
Sent from my Droid using XDA Premium App
Click to expand...
Click to collapse
I get stuck on step 7 of this guide below, so I think I never get to the point of getting root, but if I'm doing something wrong and I have to run some other commands please let me know.
1. Download the Motorola Xoom Root Zip file and unzip it. Download
2. Place the files in the SDK Tools folder.
3. adb reboot bootloader (You can skip the next 3 steps if you’ve unlocked with fastboot previously)
5. fastboot oem unlock (wait for reboot)
6. adb reboot bootloader
7. fastboot flash boot rootboot.img
7. fastboot reboot (wait for reboot)
8. adb remount
9. adb shell push su /system/bin
10. adb shell ln –s /system/bin/su /system/xbin/su
11. adb shell chmod 4755 /system/bin/su
12. adb push Superuser.apk /system/app
And thanks for making some time to reply, I try to get some help on other threads with no response.

dumb question: is rootboot.img in the same directory as everything else?
It sounds to me like your flashboot can't find it.

That's a good point from the poster above. I had trouble at the start with this and the SDK tools folder because I never messed with the adb shell too often because there never really has been a need for me to do so up until I got the Xoom.
OP... like this reply says above me, I am agreeing to as well. It looks like it might not be finding your rootboot. Make sure all root files are located in the very root of the SDK tools folder, and make sure all root files are not inside a folder. If they are please drag them into the tools folder and slap them all in there. It looks like a mess but it works. Do the same type of thing if you plan on flashing an overclock kernel. Always make sure that all files are NOT in folders when flashing something like this, and that they are always placed in the very root of the tools folder located within the SDK folder. Hope this helps.
About my above post... woops. I wasn't paying attention totally. It was late. I was thinking about when you are trying to install an overclock kernel and run into this problem that says that you cannot remount in adb. It does have to do with root access though.

Thank you very much guys I found what was my problem, I was running ADB straight from CMD window without navigating to my tool folder and always worked so I thought running step 7 will work, but NO I had to cd c:.....bla bla navigate to tool folder and do step 7.
Now I'm happily Rooted thanks again for your time guys, now to set up again my beautiful screens.

I'm having that problem where i'm trying to flash Tiamat Kernel on my Xoom and when i get to the remount i'm getting - remount failed: Operation not permitted . When you say grant root access again you talking about pointing it to the platform folder ?.

It sounds like those having problems are not very familiar with adb. Don't worry, we have all been there at one point. I would suggest that you use the one click method. No its not really a one click, more like a one click at a time method. But, it goes slow and you can see what it is doing as it goes along and has a nice tutorial from the op.
Sent from my HTC HD2 using XDA Premium App

jase33 said:
It sounds like those having problems are not very familiar with adb. Don't worry, we have all been there at one point. I would suggest that you use the one click method. No its not really a one click, more like a one click at a time method. But, it goes slow and you can see what it is doing as it goes along and has a nice tutorial from the op.
Sent from my HTC HD2 using XDA Premium App
Click to expand...
Click to collapse
No i'm not so good at it but i'm willing to or i want to learn . I used it for the first time when my Xoom was soft brick from installing a theme , i restored it with ADB and then use ADB to root ,so that's twice , the first time i rooted my Xoom i used the one click method because i was so afraid of ADB . Today the third time i was using it to flash a Kernel and at the remount i got into the problem above .

jawonder said:
No i'm not so good at it but i'm willing to or i want to learn . I used it for the first time when my Xoom was soft brick from installing a theme , i restored it with ADB and then use ADB to root ,so that's twice , the first time i rooted my Xoom i used the one click method because i was so afraid of ADB . Today the third time i was using it to flash a Kernel and at the remount i got into the problem above .
Click to expand...
Click to collapse
Are you trying to push something thru a ADB...???
Sent from my Xoom using XDA Premium App

lokko21 said:
Are you trying to push something thru a ADB...???
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Yes i'm trying to flash a kernel but at the remount step it's telling that : remount failed : operation is not permitted .

[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