Database Users

Frak! Fat fingered permaroot - root is now an unknown user

Need some help from the geniuses. And though it'll be clear I am not one of these geniuses, I wanted to mention this is my 5th Android phone and I've perma-rooted all of the others and flashed ROMs hundreds of times. I've also searched for a resolution to this with no luck. Lastly, I know some will argue this fits in General or Q&A, but this problem has been reported by a number of folks across phone lines without resolution and I think it is going to require real dev collaboration to solve and possibly help prevent this in the future, so I'm posting it in Dev.
Now, on to the problem....
Bought a MT4G yesterday and came home to root. Followed some of the great guides here to use Visionary R14 to get temproot and then "permaroot". I was getting S-OFF, but my root didn't seem to be lasting beyond reboot, maybe this was because I was showing 2.2 and not the 2.2.1 OTA update. So, I continued with the permaroot guide here: http://forum.xda-developers.com/showthread.php?t=834225 and all seemed to be going well. My root was surviving reboot and I had S-OFF, but the LAST STEP is to reboot again and check S-flag in HBOOT and that's where I went wrong. I'd left the PD15IMG file on the SD root and when it rebooted I guess I was holding the volume rocker up unintentionally, so it flashed this file without me being able to stop it. I rebooted and still showed S-OFF and 2.2.1, but now when I entered terminal emulator and type "su" I get an error about the user being unknown (doing a "ls su" in /system/bin shows su to be there, btw). Obviously the file screwed up root, and reverted my recovery from Clockworkmod to stock. From there I thought I'd reflash the OTA update.zip but I get an "invalid operation" error.
So I probably should have asked for help then, but I've been trying to follow downgrade guides and redo the root procedures but no joy, usually because they require root to initiate the downgrade (to flash a recovery and do a nandroid restore or to execute some steps of the script). I can get a # prompt when I run the rage scripts, but it appears to be losing root when I reboot. One attempt turned S-ON back on as well. My searching turned up a number of other users who have obviously had this problem with various android phones, and the only one to report successfully fixing flashed a non-root update.zip and did some sort of fixes to busybox.
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.

vettejock99 said:
Need some help from the geniuses. And though it'll be clear I am not one of these geniuses, I wanted to mention this is my 5th Android phone and I've perma-rooted all of the others and flashed ROMs hundreds of times. I've also searched for a resolution to this with no luck. Lastly, I know some will argue this fits in General or Q&A, but this problem has been reported by a number of folks across phone lines without resolution and I think it is going to require real dev collaboration to solve and possibly help prevent this in the future, so I'm posting it in Dev.
Now, on to the problem....
Bought a MT4G yesterday and came home to root. Followed some of the great guides here to use Visionary R14 to get temproot and then "permaroot". I was getting S-OFF, but my root didn't seem to be lasting beyond reboot, maybe this was because I was showing 2.2 and not the 2.2.1 OTA update. So, I continued with the permaroot guide here: http://forum.xda-developers.com/showthread.php?t=834225 and all seemed to be going well. My root was surviving reboot and I had S-OFF, but the LAST STEP is to reboot again and check S-flag in HBOOT and that's where I went wrong. I'd left the PD15IMG file on the SD root and when it rebooted I guess I was holding the volume rocker up unintentionally, so it flashed this file without me being able to stop it. I rebooted and still showed S-OFF and 2.2.1, but now when I entered terminal emulator and type "su" I get an error about the user being unknown (doing a "ls su" in /system/bin shows su to be there, btw). Obviously the file screwed up root, and reverted my recovery from Clockworkmod to stock. From there I thought I'd reflash the OTA update.zip but I get an "invalid operation" error.
So I probably should have asked for help then, but I've been trying to follow downgrade guides and redo the root procedures but no joy, usually because they require root to initiate the downgrade (to flash a recovery and do a nandroid restore or to execute some steps of the script). I can get a # prompt when I run the rage scripts, but it appears to be losing root when I reboot. One attempt turned S-ON back on as well. My searching turned up a number of other users who have obviously had this problem with various android phones, and the only one to report successfully fixing flashed a non-root update.zip and did some sort of fixes to busybox.
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
Click to expand...
Click to collapse
Try the alternative method in my guide with rage instead of visionary and see if that helps. One thing is does is reinstall su and busybox. Also, make sure that you have deleted the PD15IMG.zip from your sdcard so that this doesn't happen again.

Hey! i had the same problem and all i had to do was re-flash the ROM and ive been fine ever since!

just either use the stock rom in the downgrading post, or flash one of the new ones i.e. icedglacier or Gorillas's. iceglaciers seems to be pretty functional right now gorillas is awesome just has a few kinks he's working on

vettejock99 said:
In summary, I can't return the phone to T-mo because I bought it from an associate at work, and I appear to be stuck between root and non-root without any options that are clear to me to resolve the situation. I am somewhat familiar with adb, fastboot flashing, etc., so if someone can just help me fix su/busybox or somehow flash this back to stock so I can start over or something I would be HUGELY appreciative.
Click to expand...
Click to collapse
try this (you should be s-off) and assuming you have busybox already installed.
run rage to get su in your terminal then run the following command in the terminal
busybox mount -o remount,rw /system
busybox chown 0 /system/bin/su
busybox chmod 4755 /system/su
install the superuser.apk if it's not already installed
make sure everything is working by opening a adb shell and typing "su" to verify.
use your phone normally and try rebooting after a few hours. hopefully the fs cache flushed and root is fixed permanently.

mrpanic7 said:
Hey! i had the same problem and all i had to do was re-flash the ROM and ive been fine ever since!
Click to expand...
Click to collapse
Okay, first things first - guess I have to try to see if I can even get S-OFF again or if I've completely screwed myself.
Going to try the alt root method, but I think I have been and it wasn't working. So unless me being tired at 1am was the cause, I may need some more help. Thanks.

Okay, followed the s-off guide, and ran the busybox commands posted above, and I am back to S-OFF and now I get "permission denied" instead of "unknown user root". I think this is progress, but still can't flash because I don't have root. I noticed opening Superuser keeps FC'ing...

Please post questions in Q&A section.

just follow this guide here, which you are already familiar with. it's for temp root using rage. but since your phone has the eng hboot with s-off it should become permanent once the FS flushes out to disk (flash)
http://forum.xda-developers.com/showthread.php?t=797042
follow the guide for root and mainly to get the su files installed just in case your's didn't instal properly prior. when you are done just type "sync" multiple times in your terminal
wait a while an hour or so. then reboot to verify that it's permanent.

Same thing happened to me with the unknown root user. What finally fixed it for me, was redoing the adb commands that put those files on your device so you could use rage. Once it re put the files on my phone, I did the rage commands again and it worked
Sent from my HTC Glacier using XDA App

Thanks, everyone! I am working again, and I cannot tell you how much I appreciate the help. I was THIS CLOSE to giving up on this phone.
Thanks again.
Mark

i turned on S now it wont let me turn it back on please help

hi guys i turned on s because iam sending this back to tmo. but i forgot to flash the stock recovery img and now i am attempting to root again with visionary. it says already rooted. but it wont give me permission. and the s is on. what do i do please help...

anyone...?

This is probably going to get moved to the Q & A forum before I can finish posting this.
I have yet to find an easier root process or an easier set of instructions to follow, than the following post...
http://forum.xda-developers.com/showthread.php?t=834225
Please read that in its entirety. This is such an easy process that anyone who gets lost or messes it up, might not want to try it in the first place. I'm being as honest as possible, not trying to be insulting.
Ultimately, S=On is part of the un-root process, soooo, you're back at scratch. This means you would need to start back at the top of that post above and follow the instructions on how to root your phone/get S=Off.
Good luck!

shlongwoodian said:
This is probably going to get moved to the Q & A forum before I can finish posting this.
I have yet to find an easier root process or an easier set of instructions to follow, than the following post...
http://forum.xda-developers.com/showthread.php?t=834225
Please read that in its entirety. This is such an easy process that anyone who gets lost or messes it up, might not want to try it in the first place. I'm being as honest as possible, not trying to be insulting.
Ultimately, S=On is part of the un-root process, soooo, you're back at scratch. This means you would need to start back at the top of that post above and follow the instructions on how to root your phone/get S=Off.
Good luck!
Click to expand...
Click to collapse
i understand BUT when i run visionary it tells me already rooted.... but when i type in su it says permission denied....

We're going to need some additional details. You on 2.2.1? Have you restarted your phone since and tried again?
I'll spell it out for you - it really is dead-simple...
(***paraphrasing the OFFICIAL instructions in the thread I linked to above***)
- Enable USB Debugging
- Extract the root.rar in the original post - MAKE SURE YOU PAID ATTENTION AND NOTICED THERE IS A ROOT FOLDER WITHIN A ROOT FOLDER - a nested folder. You do NOT WANT THIS. You want just one /root folder on your sdcard, within it at the .sh scripts.
- Install VISIONary
- Attempt Temp Root
- Run Terminal emulator, type su and follow the instructions in the original post to execute the script - reboot.
- When your phone comes back up, run VISIONary again
- Attempt Temp Root
- Attempt Perm Root
There is really no way to mess this up. I have done this on 6 MT4G's, so if it's not working, you didn't follow the instructions - no doubt, no question. You don't need ADB - you can do this all from your phone with a file explorer (I use EStrongs) and a terminal emulator (I use Android Terminal Emulator).
I'm surprised this hasn't been moderated yet...

2012iawait said:
i understand BUT when i run visionary it tells me already rooted...
Click to expand...
Click to collapse
What do you mean it "tells you already rooted"? I am rooted and just running VISIONary - that is, launching VISIONary - it doesn't tell you anything. If you click Temproot now, is that when it shows that?
You know you have to first do Temproot and then do Permroot, right? From what I've seen, you can't "over root," so honestly, I highly recommend starting over again. If possible, I would literally type out each and every step you're taking. Maybe it will show us where you're messing up.

Try a different version of visionary... r11 is my preference
Sent from my HTC Glacier using XDA App

ESKIMOn00b said:
Try a different version of visionary... r11 is my preference
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Good call. I thought about that as soon as I finished my last reply - i.e. check the VISIONary version.
I've been using r14 since my first MT4G and haven't had a single issue on any of the MT4G's I've used it on.

guys loook.... i am using r11 when i click root now.... it says already rooted i can access the clock work recover and everything but s is on and i dont have super user permission.... i turned the s on but now i cant turn it of. i dont have super user permission in terminal

2012iawait said:
i turned the s
Click to expand...
Click to collapse
So that means you used the unroot.rar file and the process outlined in the first post? That's how you got S back =On again?

ok finally i got it. but now it wont let me flash the stock reocovery image i tried in adb and terminal in terminal it says file not found. and in adb sending reovery<3948kb> falled< status malformed help..... i have to send this back tomorrow

2012iawait said:
ok finally i got it.
Click to expand...
Click to collapse
So what was it? It would help if you posted your mistake, so maybe it can help someone else that runs into problems.

shlongwoodian said:
So what was it? It would help if you posted your mistake, so maybe it can help someone else that runs into problems.
Click to expand...
Click to collapse
i had to unroot it restart the temp root again then permroot.
done ... i flashed stock recovery....

Please post questions in Q&A section.

I Want Permroot, but no go?

Nothing happens when I click "attempt perm root"...absolutely nothing. What the F is going on?

bballcat03 said:
Nothing happens when I click "attempt perm root"...absolutely nothing. What the F is going on?
Click to expand...
Click to collapse
You have to follow steps to unlock the bootloader (achieving S-off) before perm root will stick. Read the thread on achieving S-off. Don't do anything you don't fully understand, so read a lot. Afaik visionary does not perm root with one click without first having an unlocked bootloader.
EDIT: Read the resource bible. It's a sticky in the dev forum.
Swyped on my rooted MyTouch4G

I have s-off with 0.85.2007...everything works like a charm until I get to the permroot part...nothing happens when I hit it.

bballcat03 said:
I have s-off with 0.85.2007...everything works like a charm until I get to the permroot part...nothing happens when I hit it.
Click to expand...
Click to collapse
If you have s-off and you have the eng 2007 bootloader, you're rooted. Make sure you have the superuser app installed to your phone. If not, you can get it from the market. You need it to gain root privileges in apps. If you have superuser you can test root by opening terminal emulator. Type su and hit enter. If you get a root request confirm it. The $ symbol should change to #.
You shouldn't need visionary anymore. Once you confirm root, uninstall it.
Swyped on my rooted MyTouch4G

But without doing "permroot" in visionary, it's not permanent, correct? Cause I want it permanent, not temp.
Yes I have superuser installed.

bballcat03 said:
But without doing "permroot" in visionary, it's not permanent, correct? Cause I want it permanent, not temp.
Yes I have superuser installed.
Click to expand...
Click to collapse
Try what I said with terminal. If you type su and hit enter, you should see a #. If you do, congrats. Reboot and test terminal su command to see if your root sticks. Visionary won't tell you if you're rooted.
Swyped on my rooted MyTouch4G

Ok I redid everything again (without doing "attempt permroot") and did what you said and the $ changed to #...however, when I first did the temp root, and then went into terminal to do the:
- su
- "cd /data/local" etc....it changed from a $ to a # as well then...before I got to the end and rebooted.
So I am permrooted then and can change roms? Why didn't I have to do "attempt permroot" in visionary?

The unlocked.com
Precise...simple..quick...easy...works...
Hope it helps!
Sent from my HTC Glacier using XDA App

h0wlings0nnets said:
The unlocked.com
Precise...simple..quick...easy...works...
Hope it helps!
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Uh, that's not a website!

Like I said, you were already rooted. When you attempt perm root with Visionary, I don't think it tells you anything. Just make sure your root sticks by rebooting and then typing su in terminal. If you get the #, you can uninstall Visionary.
As for flashing ROMs: You need to flash a new recovery in order to make Nandroid backups and flash ROMs. Clockwork ROM Manager from the market will allow you to flash Clockwork Recovery on your phone. I don't know how much experience you have with flashing ROMs in general, but if you're a novice in any way I wouldn't start changing your system just yet. Read the resource bible, lurk the developer threads, and get a firm grasp on what you are doing. Get familiar with ADB and Fastboot. Be totally confident in your knowledge. You can still brick your phone or at the very least give yourself an unneeded heart attack and hours of troubleshooting sh!t.
Resource Bible
Good luck and congrats on root!

Yeah I am looking at the "how to flash a rom for noobs" thread out of the resource bible...it says "In the hboot menu select recovery and then the phone will restart. You will get a phone with yellow triangle error."
I select recovery and another screen came up regarding the clockwork with a bunch of options, it didn't restart. And when I selected the option that said "reboot" it did, but I didn't get a yellow triangle error
Any ideas there?

Sounds to me you already have Clockwork Recovery installed. You must have done that without knowing it. Beats me. I you go into HBOOT and select Recovery the phone will shut off and boot into recovery mode. If you got Clockwork Recovery version 2.x.x.x (with green typeface), that just means you have Clockwork recovery installed and can flash Froyo based ROMs (like Iced Glacier), make Nandroid backups, and a bunch of other stuff you probably shouldn't mess with.
Just know that you CANNOT flash Gingerbread based ROMs (like CyanogenMod 7) with CW v. 2.x.x.x
You need CW v. 3.x.x.x to use gingy ROMs.
Keep reading.

I PM'd ya, but no when I hboot and hit recovery, it doesn't reboot, it goes to "clockwork mod recovery v2.5.1.2

XfooYen said:
You have to follow steps to unlock the bootloader (achieving S-off) before perm root will stick. Read the thread on achieving S-off. Don't do anything you don't fully understand, so read a lot. Afaik visionary does not perm root with one click without first having an unlocked bootloader.
EDIT: Read the resource bible. It's a sticky in the dev forum.
Swyped on my rooted MyTouch4G
Click to expand...
Click to collapse
I'm having the same issue as the OP. I'm quoting because I had a permroot stick with s-on on my previous MT4G. (I just had it replaced, damn power button)
Explain please? Why would it work on one but not the other?

I would have posted this in the development forum in the thread that had this technique, but I don't have enough posts yet or something?
Anyway, I have S=off, and visionary temp root works fine. But permroot in visionary r14 doesn't work, it just flashes like the button is pushed then does nothing, like I didn't even hit it. So I need to run the temp root everytime my phone starts up.
I didn't setup the engineer bootloader yet, should I do that?
Does r11 work better?
What is the next step to get permroot to work?

[Q] Unrooting Without Bricking

In order to troubleshoot an issue with my phone, I need to unroot. I originally rooted using this guide. I have been reading all of the unrooting posts I can find here on XDA and honestly, I'm not sure which one to use. I really don't want to brick my phone.
This was my first time rooting and will be my first time unrooting. If someone could point me towards the correct steps/link/guide that will allow me to unroot properly, I would be very appreciative. Please let me know if you need to know more about my setup.
Thanks.

Its easy. Just place the PD15IMG.zip on your SD card then go into bootloader and let it do its thing. You can pick between 2.2.1 and 2.3.4. They're somewhere in the development or general sections. Good luck.
Sent from my HTC Glacier using xda premium

SJMarty said:
In order to troubleshoot an issue with my phone, I need to unroot. I originally rooted using this guide. I have been reading all of the unrooting posts I can find here on XDA and honestly, I'm not sure which one to use. I really don't want to brick my phone.
This was my first time rooting and will be my first time unrooting. If someone could point me towards the correct steps/link/guide that will allow me to unroot properly, I would be very appreciative. Please let me know if you need to know more about my setup.
Thanks.
Click to expand...
Click to collapse
Seems you rooted gfree method.Try this ways
forum.xda-developers.com/showthread.php?t=924923

invasion2 said:
Its easy. Just place the PD15IMG.zip on your SD card then go into bootloader and let it do its thing. You can pick between 2.2.1 and 2.3.4. They're somewhere in the development or general sections. Good luck.
Click to expand...
Click to collapse
Thanks. I restored stock v2.3.4 and everything appears to have gone OK but I still have S-OFF. It restored the non-engineering bootloader but it's still S-OFF. Do you know what I need to do to get S-ON?

You used gfree right? Here are the procedures...they are taken from here.
Procedure to revert
1. Rename the part7backup file that you already have to something just so you know that it is the original backup.
2. Open up terminal emulator or adb shell and type "su" + enter to get root privileges.
3. Type "cd /data/local" and hit enter.
4. Now type "./gfree -f" + enter to run gfree again. It will disable wp on the emmc and remove the brq filter in the kernel. (as well as make another backup, which you can delete if you wish)
5. Now run the "dd if=/where/your/part7backup-numbers.bin of=/dev/block/mmcblk0p7" and it should show the output:
xxxx bytes in
xxxxbytes out
xxxxxxxxxx copied in blah blah blah
6. Run "sync" and then reboot. (I didn't do this and it worked fine but it won't hurt either. )

Yes, I did use gfree. I found that thread before posting but when I originally rooted, I did not use the method in that thread. I used the method in the CyanogenMod Wiki so I don't have the part7backup file. The thread you linked too specifically says (in big red text) that "Gfree writes a backup of the file that it patches named Part7backup-numbers.bin on your sdcard. I suggest putting this file in a safe place as it is the only way to revert if you need to." After seeing that, I didn't think that was the way to go.
Are you saying that I only need to do the second set of steps (where it starts with "If you have the engineering hboot 0.85.2007 installed...")?

Not sure...sorry

You could try the part of the engineering bootloader. Wortha shot.
Sent from my HTC Glacier using xda premium

[Q] HTC dev unlocked/Perm root/ NO S=OFF

I unlocked the Boot loader 2 weeks ago via Htcdev
Following this thread about acheiving S=OFF after HTCdev Unlocked.
GUIDE] How to get root/flash custom roms with HTCDEV unlock by Nipqer posted January 19,2012 adb push su /data/local/tmp/
GAING PERM ROOT.
> adb push busybox /data/local/tmp/
> adb push fixsu.sh /data/local/tmp/
> adb install SuperUser.apk
> adb shell chmod 755 /data/local/tmp/fixsu.sh
> adb shell chmod 755 /data/local/tmp/busybox
> adb shell /data/local/tmp/fixsu.sh
PERM ROOT WAS ACHEIVED, But I can not get S=OFF
I then followed the guide on the post.
EASY PERM/S-OFF FOR MYTOUCH 4G: G2/Desire Z PermRoot/S-OFF
http://forum.xda-developers.com/showthread.php?p=21563546
All commands seem to go flawlessly until
After following the directions on
Step Two:
Open term. emu. and type.
(DO NOT TYPE */# just commands.)
$) su
#) cp /sdcard/root_files/perm_root /data/local/perm_root
#) chmod 777 /data/local/*
#) /data/local/perm_root
http://forum.xda-developers.com/showthread.php?t=1035278
I get this error
chmod 777 /data/local/tmp/fre3vo is not working it show No such file or directory
I have all the proper files in the Platform tools folder in Adk
tried several times but no joy on S=off
Am I just going to have to stay with PERM ROOT, or will I have to downgrade to FROYO TO acheive S=OFF.
I have Android 2.3.4
SOFTWARE 2.32.531.1
HBOOT 0.89.0007
Any advice

I have the exact same problem, except I flashed a 2.2.1 stock Rom that had root permissions, and everything appeared to go well, but s-on remained. I'm interested in seeing how this turns out, because mostly I am being told that I am doing something wrong or not following the guides properly. However, I think its the HTC update that is complicating things...
Sent from my HTC Glacier using Tapatalk

HTC dev unlocked/Perm root/ NO S=OFF
I agree. I thought it might be that I unlocked a stock gingerbread rom and that was what was preventing me from S=OFF.
Although I have perm root and followed instructions. tried several times. still no joy.
I am wondering if someone typing the instructions left something out by mistake.
It is frustrating to get that far the get that chmod error.
Have you flashed a custom rom?
I have not tried yet. I have the stock Rom and the CM7 Rom saved. just cant bite the bullit.

You guys should take a look here
http://forum.xda-developers.com/showthread.php?p=21563546
Re lock and follow downgrade guides....easy cheesy...

4GBurn said:
I agree. I thought it might be that I unlocked a stock gingerbread rom and that was what was preventing me from S=OFF.
Although I have perm root and followed instructions. tried several times. still no joy.
I am wondering if someone typing the instructions left something out by mistake.
It is frustrating to get that far the get that chmod error.
Have you flashed a custom rom?
I have not tried yet. I have the stock Rom and the CM7 Rom saved. just cant bite the bullit.
Click to expand...
Click to collapse
Yes if you use adb/fastboot on your pc, to flash Clockwork recovery or 4ext recovery, you can then flash custom roms, all you want. But make sure you have adb/fastboot working because once you flash a custom Rom, you will have to then have to extract the boot.img from the Rom and flash it through fastboot. What I do is this:
1- download the Rom of your choice. Unzip it, and copy the boot.img into your adb directory on your pc.
2. Place the zipped Rom on your sdcard ( make it easy to find)
3. Boot your phone into recovery mode.
4. At this point, I do a Nandroid backup.
5. Wipe data/ factory reset
6. Wipe cache + davlik
7. Install .zip from sdcard - choose your Rom that you placed on sdcard ( be patient and be sure its finished)
8. Reboot your phone to hboot/FASTBOOT and plug in USB cable.
** on your pc click start--> run -> cmd --then in the command prompt type -->cd\ then type --> cd adb you should then be able to proceed to step 9.
9 type- fastboot flash boot boot.img
10 type- fastboot-windows reboot
At this point unplug your phone and wait for it to load your new Rom.
Again, this is what I do, and I have loaded 10 or more roms this way. But make sure you have either Clockwork or 4ext recovery on your device, and also that FASTBOOT is working on your pc. If you are not 100% comfortable, please don't try this...
Sent from my HTC Glacier using Tapatalk

out of sheer curiousity why would you unlock via htcdev?
--sent from my glacier.

rockstarar said:
out of sheer curiousity why would you unlock via htcdev?
--sent from my glacier.
Click to expand...
Click to collapse
In my case it was ignorance... Thinking it was the same as rooting. I wouldn't have if I had read here 1st, but a respected site that I read a lot, made it appear like a wonderful thing. And truthfully, if all you wanna do is load roms.. its not that bad. Just an extra step in flashing the boot.img from whatever Rom u choose. I do wish I hadn't though.
Sent from my HTC Glacier using Tapatalk

....people.. Never ever ever ever ever ever EVER use htcdev for unlock
Sent from my HTC Glacier using xda premium

nicgraner said:
....people.. Never ever ever ever ever ever ever use htcdev for unlock
sent from my htc glacier using xda premium
Click to expand...
Click to collapse
+ 1,000,000,000,000,000,000,000,000

1) You didn't extract the RAR properly, and/or you're trying to execute a script that is calling fre3vo while your SD card is mounted to your computer.
2) You didn't see that the guide you're using is LONG OUTDATED, and you need to downgrade the phone for it to proceed.
3) Read the previous threads on the subject.
4) Read the stickies BEFORE you start messing with something.
5) Relock your phone and proceed with downgrade.
6) Google it next time. You're yet another case of someone that comes around, doesn't read the stickies, and creates a thread "I did I-don't-know-exactly-what, now I'm doing something else that I shouldn't be doing but I don't know it, and it doesn't work out well".
I wish HTC released their unlock tool with basic Linux quiz that wouldn't allow using it unless you're at least likely to know what you're doing.

And I wish xda had a reading/googling comprehension test before allowing people to post...

I wish people that are seasoned and very knowledgable would stop assuming that you can learn EVERYTHING by reading. Sometimes when you read, people are speaking or typing in terms that are very confusing for someone that is brand new. Even better than that, if it is bothersome or aggravating to see someone ask questions, choose not to answer them rather than insult everyone that comes along to ask a question. I used to be a forum moderator, but it was for programming DirecTV satellite cards, and I know how frustrating noobs can be, but in this case, with phones there are so many different ways to achieve the same results, and it is confusing to know what to type where. I for one am very appreciative for any and all help that I receive, but have read until my eyes hurt, and some of the methods are not working on the HTC unlocked devices. I tried downgrading for 2 weeks and I never saw a section in the wiki that told me to relock my bootloader to downgrade. Anyway, thanks to all that have helped without making me feel like a total idiot when asking a question. Even more thanks to those that have chosen not to reply at all rather than post to insult me.
Sent from my HTC Glacier using Tapatalk

This forum is called "XDA-Developers" and not "XDA-Users" for a good reason. When you'll think about this reason, you'll probably understand the reason why new users should start by reading, reading and reading, rather than writing, and why not answering their questions will very quickly hurt them much more than being bashed in response to something stupid/lazy.

Jack_R1 said:
This forum is called "XDA-Developers" and not "XDA-Users" for a good reason. When you'll think about this reason, you'll probably understand the reason why new users should start by reading, reading and reading, rather than writing, and why not answering their questions will very quickly hurt them much more than being bashed in response to something stupid/lazy.
Click to expand...
Click to collapse
I agree to a certain degree, and I have learned a lot from you in the past 2 weeks, and I don't want u to think that I am ungrateful, because I am very appreciative for what you helped me with. In fact, I have continued to read for days. I'm trying to learn, but its not easy. A lot of the guides are not working for me because of my HTC update. I am trying methods on 2 different devices, one w/o the update is being more coopertive...
Sent from my HTC Glacier using Tapatalk