Database Users

[Q] S-OFF after using Visionary r14

Could someone explain to me or point me to a thread that explains how to get S-OFF after permarooting with the r14 visionary + build?

I just used the s-off guide in the android development section and it worked perfect.
Go on youtube and search for "visionary g2", there is a guy on their called blackprice that has a step by step video on how to perm root and s-off the phone.
Good Luck.

Thanks, but I need someone to explain to me how to use adb with a mac. Every guide out seems to be for windows

pak256 said:
Thanks, but I need someone to explain to me how to use adb with a mac. Every guide out seems to be for windows
Click to expand...
Click to collapse
In the video, black prince actually shows how to do it on the phone itself with terminal emulator.

Awesome, thanks

So I have followed the instructions from blackprice and they seemed to work, I was able to do the S-OFF. However, when using SetCPU I get this message:
Root Access Not Detected
SetCPU could not obtain root
access. Did you allow SetCPU
through Superuser
Permissions? (the answer is yes) If you checked
Superuser Permissions and SetCPU still cannot get root,
there may be a permissions
issue with your ROM.
Please advise...
Thanks

Use visionary and attempt perm root. I had the same problem but this fixed it. Wait for someone else to confirm this though.
Sent from my T-Mobile G2 using XDA App

Also get rom manager from the market and falsh clockwork recovery.
Perm root and the reboot, and visionary should stick.

Thanks! Both of you.

pak256 said:
Thanks, but I need someone to explain to me how to use adb with a mac. Every guide out seems to be for windows
Click to expand...
Click to collapse
If you google then you will come across some good guides to use ADB on mac

So to confirm with what you are stating, S-OFF but still not accessing root permissions. Re-apply perm root in Visionary, let it reboot, and it should stick. Correct?

[Q] permroot with visionary, s-on, which part of filesys. persist on reboot?

Hi. I was trying to modify build.prop file after permroot (no soff), but on hard reboot (not fast boot) it keeps being rewritten with original. Can someone clear up, which parts of the fs persist with permroot and s-on?
-- sent from htc z using xda app

There is no permanent root with S-ON, is there ? Just a temp root that can keep being re-applied.

Is visionary permroot s-off then? I thought it isnt. Can someone explain this?
-- sent from htc z using xda app

tbalden said:
Is visionary permroot s-off then? I thought it isnt. Can someone explain this?
Click to expand...
Click to collapse
I would like to know too. But what does your HBOOT say if you go into it, S-ON or S-OFF ?

Reading Paul's thread on Visionary on his website, there's this bit that I noticed :
Permroot on the other hand is inherently more risky. Permroot does make changes to the /system partition of your device. Technically speaking the only change that is made is the installation of a small file to /system/xbin
Click to expand...
Click to collapse
And then in the changelog later :
•After permroot, required kernel module is placed in /data/local for your convenience
•Added option to unroot
•Note: this does NOT rewrite your hboot - you will need to do this manually to get S-OFF.
Click to expand...
Click to collapse
So it looks like it doesn't do S-OFF.
Personally I don't really see this as "perm root", if you want to be pedantic (and pedantic is my middle name ). It's a temp root that it keeps doing when you boot up. But I guess to the user it does effectively look like a permanent root.
I know this doesn't answer your original question though, sorry.

Back to your original question, you could just try creating a small dummy file (e.g. "touch abc123") in each file system, and then see which ones are still there after a reboot.

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] S =-off, no Visionary won't let me root

I used visionary to temp root/root. followed all the instructions in visionary and terminal emulator. when I restarted the phone it showed S off, I went to visionary to perm root and it say's I have to temp root my phone?? I rooted my other mytouch 4g the same way and it worked so I don't know what's wrong Im pretty sure i'm not doing anything wrong

Once you get s off and boot up you don't have su permissions so you need to temproot and then permroot immediately after to complete the root process
Sent from my HTC Glacier using XDA App

I got S off, rebooted in the mode, did everything in terminal emulator and when i went to visionary to perm root it said i had to temp root my device first, when i try to temp root with visionary the program keeps flashing for a few minutes, then nothing... anything I can do with the S being off already? The "super user" program is in my programs already also... can't figure it out

King350z said:
I got S off, rebooted in the mode, did everything in terminal emulator and when i went to visionary to perm root it said i had to temp root my device first, when i try to temp root with visionary the program keeps flashing for a few minutes, then nothing... anything I can do with the S being off already? The "super user" program is in my programs already also... can't figure it out
Click to expand...
Click to collapse
When you try to use root access is it not allowing it? Open up something like root explorer that asks for root access and see if it works. If it does then it sounds like it worked.

No it's not even though I have S off and did all the commands in terminal, I tried using Rom Manager, Titanium etc.. other root programs it says I need to root my phone first...

King350z said:
No it's not even though I have S off and did all the commands in terminal, I tried using Rom Manager, Titanium etc.. other root programs it says I need to root my phone first...
Click to expand...
Click to collapse
Do you have the SuperUser icon?

bootloader? Here's the root guide
What bootloader do you have?
0.86.0000 seems to make some rooting methods difficult if not completely ineffective.
Follow these instructions:
http://forum.xda-developers.com/archive/index.php/t-995549.html
It was seamless for me.
**I am not responsible for any consequences of you playing with your phone.**

thepza said:
What bootloader do you have?
0.86.0000 seems to make some rooting methods difficult if not completely ineffective.
Follow these instructions:
http://forum.xda-developers.com/archive/index.php/t-995549.html
It was seamless for me.
**I am not responsible for any consequences of you playing with your phone.**
Click to expand...
Click to collapse
All phones come with the .86.xxxx bootloader, you cannot load the .85.xxxx bootloader to the phone till after one has rooted and s-off'd the phone.
as quoted from here
http://forum.xda-developers.com/showpost.php?p=14573409&postcount=15
there are two ways to root our phones.
1) root.sh, regardless of what VISIONary or root.sh package you use. This will only root phones with good eMMCs. If your phone doesn't root via this method, then you have a bad eMMC and shouldn't root your phone.
2) ./gfree, regardless of what VISIONary or ./gfree package you use. This will root your phone regardless if you have a good or bad chip. you are setting yourself up to be royally screwed down the road, if you use root.sh it fails multiple times. Then use ./gfree to root it.
you are correct in the assumption that ./gfree will root your phone no matter what. But it will brick you phone if you have a bad eMMC. It might not happen right away, it might not happen in a week, or a month. But it's coming. There are thousands of threads all over the webs of people with bricked phone who use ./gfree to root their devices with a bad eMMC. there are significantly less threads of people who use root.sh and have bricked their phones.
advising someone to use ./gfree after they've admitted that root.sh didn't work, multiple times, w/o a fair warning is ignorant and not really helping anyone. a rooted phone is nice, a bricked device is totally different....

Yes I do and s off, but no root access and visionary wont root it after I successfully temp rooted, then booted did terminal emulator, wen I went to perm root it said I had to temp root first
neidlinger said:
Do you have the SuperUser icon?
Click to expand...
Click to collapse
Sent from my HTC Vision using XDA App

King350z said:
Yes I do and s off, but no root access and visionary wont root it after I successfully temp rooted, then booted did terminal emulator, wen I went to perm root it said I had to temp root first
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
settings > applications > all > search for super user > delete the icon > reboot the phone > try visionary again.
Try that, it should help.

neidlinger said:
1) root.sh, regardless of what VISIONary or root.sh package you use. This will only root phones with good eMMCs. If your phone doesn't root via this method, then you have a bad eMMC and shouldn't root your phone.
[/SIZE]
Click to expand...
Click to collapse
Not true. Visionary doesn't permaroot for all of the good eMMCs. Verify which eMMC you have. If you don't have ADB set up, then temp root (although you're having problems with that currently) and then in Terminal Emulator:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
That will report out the name of the chip you have. SEM=good.

delete the icon or uninstall the program, then try to temp root again with visionary and go through the steps?

King350z said:
delete the icon or uninstall the program, then try to temp root again with visionary and go through the steps?
Click to expand...
Click to collapse
delete Super User from the Application menu, via the settings. Then try to temp root / perma root again.

thepza said:
Not true. Visionary doesn't permaroot for all of the good eMMCs. Verify which eMMC you have. If you don't have ADB set up, then temp root (although you're having problems with that currently) and then in Terminal Emulator:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
That will report out the name of the chip you have. SEM=good.
Click to expand...
Click to collapse
you have no clue what i'm saying.
VISIONary will not perma root a phone at all. You must manually turn s-off. You need to do that one of two ways. Either with the root.sh or the ./gfree method. both of which use VISIONary in their independent process. root.sh will not root bad eMMC phones. ./gfree will root either or without a problem.

will try it thanks, I don't know if it makes a diff but wheni open visionary now while temp rooting it just flashes for a few minutes?
neidlinger said:
delete Super User from the Application menu, via the settings. Then try to temp root / perma root again.
Click to expand...
Click to collapse

King350z said:
will try it thanks, I don't know if it makes a diff but wheni open visionary now while temp rooting it just flashes for a few minutes?
Click to expand...
Click to collapse
That's why i said earlier to reboot after you delete the superuser.apk. It will clean all of the current cache out.

Thank you for the help, will try it out when i get a chance later tonight or tomorrow, hope it works

failed root need help

So on my girlfreindd my touch 4g I installed and ran invisonary r14 at first I checked temp root on startup and mount system and clicked temproot now.....the su Popped up but phone restarted before I can click allow. After rebooting it was very slow and then I went back into it and click permanentroot but says to do temproot .....so I did it agian an after rebooted clicked permanentboot and restarted but my phone is not rooted....su is installed and I have Apps that say its not rooted so when I try again visionary just flashes and goes back to the apparently so now it wont even temproot to permanentroot and su is installdd and it says its not root so I can't un root so is there anyway of doing this or am I stucl

First off all : VISIONary.apk is a one click root tool but the security flags on our phones turn off the SU ability and remove root commands upon rebooting.
Second of all : you really didn't search this because every "root method" i've seen mentions using one of two different method to root our phones. Either ./gfree or root.sh. The search button works wonders
Third and final : I'm assuming since you gained SU access via VISIONary.apk you are still rocking 2.2.x. You can use the links in my signature for both methods. However i highly suggest you read the newcomers thread first.

Did you search, read before posting? If you are on gingerbread 2.3(which I'm pretty sure you are) you can't root with visionary.
If you're still on froyo 2.2, there's a lot of how to's here and on google.
EDIT:^^^^exactly what he said.
Sent from my HTC Glacier using xda premium

Quoted myself. Ignore.

Well currently It is 2.2.1 (Froyo) but thank you neidlinger, I will try both of those, but can you guys tell me how safe this is? When I rooted my other phones it was easy and painless (samsung GS phones) But I never rooted an HTC phone so is there anyway these guides can break the phone permanently?

tanner2007 said:
Well currently It is 2.2.1 (Froyo) but thank you neidlinger, I will try both of those, but can you guys tell me how safe this is? When I rooted my other phones it was easy and painless (samsung GS phones) But I never rooted an HTC phone so is there anyway these guides can break the phone permanently?
Click to expand...
Click to collapse
Its very easy and very safe if you follow the directions to the T. It takes me 5 minutes tops to root and gain s-off with the visionary, root.sh method. I have never messed up.
Sent from my HTC Glacier using xda premium

HTC phones are very easy to root, you just need to follow directions and obtain S-off. once Security is off, rooting and flashing is painless.