Database Users

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.

do I need s=off for cyanogenmod 7?

I have ROM manager premium, and I just downloaded CM7 through it, and was about to flash it, but remembered I dont have s=off.
Also, I cannot get past this screen no matter what. htt p://img145.imageshack.us/i/20110222142411.jpg/
Any help will be appreaciated I really want to be able to run CM7

You need to be rooted, use the ultimate gfree method that's stickie in the development section after you root make sure to back up your stock OS.
Sent from my HTC Glacier using XDA App

epsix said:
You need to be rooted, use the ultimate gfree method that's stickie in the development section after you root make sure to back up your stock OS.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Thanks for answering, but I am rooted, I used the visionary perm-root method. I have terminal emulator and typed "su" and it prompted for super user access. I also have a few apps that use root, which work.

Root access alone is not enough. You need S-Off as well.

jggimi said:
Root access alone is not enough. You need S-Off as well.
Click to expand...
Click to collapse
Is that why I always get this screen when I try to make a back up or boot into recovery.

jggimi said:
Root access alone is not enough. You need S-Off as well.
Click to expand...
Click to collapse
This Statement is correct.
jessek17 said:
Thanks for answering, but I am rooted, I used the visionary perm-root method. I have terminal emulator and typed "su" and it prompted for super user access. I also have a few apps that use root, which work.
Click to expand...
Click to collapse
for short terms "s" Means security protocol. If your S=ON that means the phone will do a search each time you boot the phone on to see if anything as been tampered with. and if it has it will revert back to a factory status. Just like you first bought the phone. Which includes rooting, recovery images, boot images, engineering screens. What ever you do to your phone that isn't factory will be undone.
It is impossible to do. Because you need to flash the ROM from the recovery image. And since one you boot your phone it will replace Clockwork ROM manager with the factory style recovery image, you cannot not even get to the place you need to flash it from.

jessek17 said:
Is that why I always get this screen when I try to make a back up or boot into recovery.
Click to expand...
Click to collapse
Correct because you flashing the Clockwork Recovery image will not STICK unless you have s=off.
They system will replace the aftermarket image with the original EVERYTIME you turn off the phone.

That is the Stock Recovery. You need S-Off and ClockworkMod Recovery. And the right release of CWM Recovery, also. Use CWM Recovery 2.x to back up, restore, and install Android 2.2 (Froyo) based ROMs, including stock, and CWM Recovery 3.x to back up, restore, and install Android 2.3 (Gingerbread) based ROMs, such as CM7.
There is a special version of CWM Recovery that can manage both Froyo and Gingerbread ROMs: 3.0.0.6. Search for it in the Development subforum.

Thanks for all the information, I am slowly learning, and trying to understand all of this.
I am currently trying to get s=off. I found this link via google : ht tp://forum.xda-developers.com/showthread.php?t=858996
I am already "rooted" I believe, because I have superuser access. Should I unroot first?
Also, in order to back up my current(stock) rom, do I need to use clockwork recovery 2.x?

jessek17 said:
Thanks for all the information, I am slowly learning, and trying to understand all of this.
I am currently trying to get s=off. I found this link via google : ht tp://forum.xda-developers.com/showthread.php?t=858996
I am already "rooted" I believe, because I have superuser access. Should I unroot first?
Also, in order to back up my current(stock) rom, do I need to use clockwork recovery 2.x?
Click to expand...
Click to collapse
Yes that method will work.
no do not unroot prior to starting that method
yes you need to use 2.x to back up froyo (2.2) ROMs.

neidlinger said:
Yes that method will work.
no do not unroot prior to starting that method
yes you need to use 2.x to back up froyo (2.2) ROMs.
Click to expand...
Click to collapse
Okay, is there a simpler way to get s=off? That looks a little complex for my first time doing this, and it seems as if one typo will brick my phone.

jessek17 said:
Okay, is there a simpler way to get s=off? That looks a little complex for my first time doing this, and it seems as if one typo will brick my phone.
Click to expand...
Click to collapse
http://theunlockr.com/2010/12/10/how-to-temporarily-root-the-t-mobile-mytouch-4g-htc-glacier/
you can use the link i posted ^^^ there.
I will state this though. That link that you posted is the simplest way of truly rooting your phone. If that seem complex i would advice against you doing it at this point in time.
Rooting your phone basically turns your phone into a computer that can make and receive phone calls. And doing the wrong thing at the wrong time will seriously FUBAR your phone.
If you take a look in the Q&A section and the General Section you will see TONS of post with people in your shoes that didn't know what they were getting into and didn't take the warning laid out there.
READ READ READ about the android ADB before you decide to root your phone. And learn what everything is and what it does.
not trying to sound like a "Richard" but i don't want to see you mess up your phone either.

neidlinger said:
http://theunlockr.com/2010/12/10/how-to-temporarily-root-the-t-mobile-mytouch-4g-htc-glacier/
you can use the link i posted ^^^ there.
I will state this though. That link that you posted is the simplest way of truly rooting your phone. If that seem complex i would advice against you doing it at this point in time.
Rooting your phone basically turns your phone into a computer that can make and receive phone calls. And doing the wrong thing at the wrong time will seriously FUBAR your phone.
If you take a look in the Q&A section and the General Section you will see TONS of post with people in your shoes that didn't know what they were getting into and didn't take the warning laid out there.
READ READ READ about the android ADB before you decide to root your phone. And learn what everything is and what it does.
not trying to sound like a "Richard" but i don't want to see you mess up your phone either.
Click to expand...
Click to collapse
Isnt that just a video of temprooting and then confirming the root with terminal emulator?
I have seen many people with problems and they think they bricked their phone. I dont want to be one of them, and I've had a few close calls, and I'll tell you it wasnt fun.
From what I see ADB is just a remote terminal?
I appreciate that, and have taken the warnings very seriously.

jessek17 said:
Isnt that just a video of temprooting and then confirming the root with terminal emulator?
I have seen many people with problems and they think they bricked their phone. I dont want to be one of them, and I've had a few close calls, and I'll tell you it wasnt fun.
From what I see ADB is just a remote terminal?
I appreciate that, and have taken the warnings very seriously.
Click to expand...
Click to collapse
That's kind of my point. People don't read.
If you take your time and read and do the entire process you won't have a problem. but you need to read all the way through something prior to jumping in the ring. There is a very strict set a rules that need to be followed.

To root or not to root?

So over the past few days I have been doing alot of research on rooting my phone. I have watched videos and read almost every thread concerning it. I understand the advantages and disadvantages of it. I have never done this before, but I am more than competent enough to follow the directions. I have taken it as far as using visionary and temp rooting my phone. I have a file manager downloaded, and a terminal emulator downloaded. If I go through with it I plan on following the directions in the thread using the gfree method. Ok, with that being said, my only real question is..if I follow the directions, obviously making sure my phone is charged as well, what are the chances of me bricking my phone? Is it incompetence that will create a brick? Or is it something that following the directions correctly will easily avoid?

just do it. -nike
follow directions and youll be fine. thats what i did

Yeah, it's pretty hard to brick your phone. One word of caution though: if you decide to flash the engineering bootloader, screwing up that command WILL brick your phone. Check it, re-check it, and do it over again just to be sure you've typed it properly.

Yea, not trying to get that in depth into it, just want to run some STABLE custom ROM's. I have spent the past 2 hours setting up adb and getting my phone to accept commands. Starting to get comfortable with that. I am really new to all of this, so I am trying to learn as much as I can before I jump into it.

UPDATE: Just need a couple more people to chime in on this. Like I said, I have ADB setup, my phone is accepting commands (rebooted over adb to test) I have visionary, I can temp root with no problem. I have read over the instructions, and understand them fully. I am not going to flash the engineering bootloader, just want to permroot to flash custom rom's and delete bloatware and such. So just doing permroot, is there a chance I can brick my phone?

as long flash a revovery image. And dont mess with the radio file you should be okay.
Cyanogen Powered; Android designed

Alright, thanks for the help, I am obviously a noob...Flashing the recovery is done right on the ROM Manager App right? And there is no way to accidentally mess with the radio?

lowandbehold said:
Alright, thanks for the help, I am obviously a noob...Flashing the recovery is done right on the ROM Manager App right? And there is no way to accidentally mess with the radio?
Click to expand...
Click to collapse
yes it can be done with clockwork ROM manager.
And no the radio has to be done on purpose.
Cyanogen Powered; Android designed

Thanks for the help, It took me 2 days but I grew a pair and did it. Followed the directions on the guide and worked perfectly. Deleted Visionary, rebooted into hboot and have S off, went into my terminal emulator and still have superuser access. Thanks again!

lowandbehold said:
Thanks for the help, It took me 2 days but I grew a pair and did it. Followed the directions on the guide and worked perfectly. Deleted Visionary, rebooted into hboot and have S off, went into my terminal emulator and still have superuser access. Thanks again!
Click to expand...
Click to collapse
You really should flash the Engineering bootloader. It makes it harder to brick your device in the future.

It took a bunch of reading, but I rooted my phone and my wife's phone using the gfree method, and installed the engineering bootloader.
Then, a month or so later, I upgraded to CM7. CM7, while still beta, is tons better than the stock firmware. I was going to do Ice Glacier, but developement stopped on it, and ultimately I wanted to be on CM anyway.
Better battery life, tons more features, no reason to complain.
Just do it. TMO should make CM stock on these phones.

I downgraded from the Official AT&T 2.2 update back to 2.1

I used the info on this page: *android.modaco.com/content/htc-desire-desire-modaco-com/310873/possible-hboot-downgrade/* it didn't downgrade the hboot, but that might be something to work on.
CHANGE STEP 3.4. "change it to 1.15.405.1" don't do that, change the "2.20.502.1" in the misc.img from your aria to 1.25.502.2
Oh and you'll need either a Temp root, or a Shell root for adb

I have done this and can confirm that this works
Thanks mate!

I just noticed the Aria got 2.2 finally, albiet through this silly sync method.... It's my wifes phone, I'm sure she's not going to be happy to have to hard reset it.. wth.
Anyway, so why are you guys going back to 2.1? I am surprised not to see more discussion on 2.2 in this forum, but I don't frequent it much since I don't own the Aria myself.

khaytsus said:
I just noticed the Aria got 2.2 finally, albiet through this silly sync method.... It's my wifes phone, I'm sure she's not going to be happy to have to hard reset it.. wth.
Anyway, so why are you guys going back to 2.1? I am surprised not to see more discussion on 2.2 in this forum, but I don't frequent it much since I don't own the Aria myself.
Click to expand...
Click to collapse
I went back to 2.1 because the 2.2.2 version that AT&T released was extremely slow, and my touchscreen would become unresponsive.

andrewishcool95 said:
I used the info on this page: *android.modaco.com/content/htc-desire-desire-modaco-com/310873/possible-hboot-downgrade/* it didn't downgrade the hboot, but that might be something to work on.
CHANGE STEP 3.4. "change it to 1.15.405.1" don't do that, change the "2.20.502.1" in the misc.img from your aria to 1.25.502.2
Oh and you'll need either a Temp root, or a Shell root for adb
Click to expand...
Click to collapse
How do you get a temp root or shell root with the new HBoot still in-place? If temp root is possible, then can't you install clockworkmod and get permaroot?

Gene Poole said:
How do you get a temp root or shell root with the new HBoot still in-place? If temp root is possible, then can't you install clockworkmod and get permaroot?
Click to expand...
Click to collapse
I got a shell root from super one click root (forum.xda-developers.com/showthread.php?t=803682)
after I downgraded to 2.1 I got z4root to get a temp root.

andrewishcool95 said:
I got a shell root from super one click root (forum.xda-developers.com/showthread.php?t=803682)
after I downgraded to 2.1 I got z4root to get a temp root.
Click to expand...
Click to collapse
I'm also very curious about this.

Sounds like the first steps to rooting and downgrading. I'm curious to see if any developers catch this
Sent from my SAMSUNG-SGH-I897 using XDA Premium App

I've been reading up on this and the skinny is that the HBOOT image controls the S-ON and S-OFF flags of the NAND RAM in the device. Even with a temp root shell, you can't write to a partition with its S-ON flag set. This normally includes all the partitions on the phone except the data partition, so trying to root the device requires some sort of interaction with the HBOOT image to turn off the S-ON flag for the recovery and system partitions to properly root a phone.
In short, if and until someone hacks hboot_liberty_7227_1.02.0000_101104, your phone is unrootable.

Gene Poole said:
I've been reading up on this and the skinny is that the HBOOT image controls the S-ON and S-OFF flags of the NAND RAM in the device. Even with a temp root shell, you can't write to a partition with its S-ON flag set. This normally includes all the partitions on the phone except the data partition, so trying to root the device requires some sort of interaction with the HBOOT image to turn off the S-ON flag for the recovery and system partitions to properly root a phone.
In short, if and until someone hacks hboot_liberty_7227_1.02.0000_101104, your phone is unrootable.
Click to expand...
Click to collapse
Help me out, I may be thinking in the wrong direction, but I've been dealing with my nook which is why I thought of this.
Is there not a way to write an hboot to an sd-card or connect via usb at start to make the aria think that the sd-card or the usb connection is the corrected hboot, thus being able to modify?

FroztIkon said:
Help me out, I may be thinking in the wrong direction, but I've been dealing with my nook which is why I thought of this.
Is there not a way to write an hboot to an sd-card or connect via usb at start to make the aria think that the sd-card or the usb connection is the corrected hboot, thus being able to modify?
Click to expand...
Click to collapse
There may be. When I first got my Aria, the rooting procedure involved an HTC signed update that you fooled the hboot into partially loading, then swapped the sdcard with the root package. It involved some complex timing issues where you had to run adb in a loop and plug/unplug the usb cable at appropriate times.
I've been searching the net for that procedure and I can't seem to find the right search terms, or I'm just not looking in the right places or something, but I know that's how I did my Aria before there was an unrevoked plug-n-root.

I have the procedure u are looking for i think...let me know if this is what u were after because i have an archive of saved documents I have copied from forums in the past...GOOD LUCK!
well apparently i haven't posted enough to put the links up in the post

PM me if you want the process...

xerotix said:
PM me if you want the process...
Click to expand...
Click to collapse
May I have a copy of said process? Currently the only way is to buy a very expensive hardware called XClip. I have managed to get the updated 2.2.2 Stock ROM rooted but not deodex or EXT3 FOR ap2sd trying to play with some files from another source to get hboot s off.

econcep said:
May I have a copy of said process? Currently the only way is to buy a very expensive hardware called XClip. I have managed to get the updated 2.2.2 Stock ROM rooted but not deodex or EXT3 FOR ap2sd trying to play with some files from another source to get hboot s off.
Click to expand...
Click to collapse
That process does not work with the new HBOOT. That's why unrevoked doesn't work. Having root access does not unlock NAND.
Currently, the only way known is via hardware tools.

It works. I managed a work around for 2.2.2 update
Hey everyone I am in the second phase of testing my work around with the new HTC Aria update from ATT. I managed to load the update and keep my phone rooted. I am now in the setup mode with no bootloop.
Running into a couple of issues with the new radio but I believe I know how to fix that as well. Keep you all posted and once all bugs worked out I will post my findings and HOPEFULLY MY ROOTED ROM.ZIP with instructions.
IF AT FIRST YOU DON'T SUCCEED.....TRY TRY TRY and TRY I did and I am 99% there.

econcep said:
Hey everyone I am in the second phase of testing my work around with the new HTC Aria update from ATT. I managed to load the update and keep my phone rooted. I am now in the setup mode with no bootloop.
Running into a couple of issues with the new radio but I believe I know how to fix that as well. Keep you all posted and once all bugs worked out I will post my findings and HOPEFULLY MY ROOTED ROM.ZIP with instructions.
IF AT FIRST YOU DON'T SUCCEED.....TRY TRY TRY and TRY I did and I am 99% there.
Click to expand...
Click to collapse
This might be the wrong thread. Did you manage to get around the HBOOT issue with the 2.2 update? If not, then you've just done the same thing I did the day after this release was out:
http://forum.xda-developers.com/showthread.php?t=970272

Gene Poole said:
This might be the wrong thread. Did you manage to get around the HBOOT issue with the 2.2 update? If not, then you've just done the same thing I did the day after this release was out:
http://forum.xda-developers.com/showthread.php?t=970272
Click to expand...
Click to collapse
You are right this might be the wrong thread. But I managed a work around with the new update 2.2.2 and the HBOOT 1.0X. As soon as I can confirm without a doubt that it works and will be able to repeat the process successfully with my husband's ARIA (unfortunately we love hacking things and tend to buy multiple devices) I will be more than happy to share the results.
Again, my apologies if it's the wrong thread.

econcep said:
You are right this might be the wrong thread. But I managed a work around with the new update 2.2.2 and the HBOOT 1.0X. As soon as I can confirm without a doubt that it works and will be able to repeat the process successfully with my husband's ARIA (unfortunately we love hacking things and tend to buy multiple devices) I will be more than happy to share the results.
Again, my apologies if it's the wrong thread.
Click to expand...
Click to collapse
Perhaps I misread (or we're talking past each other). You do have, in fact, HBOOT 1.02.0000 on your Aria, and managed to write to the system partition?

Yes & No. I'm stuck on couple of things. First the will temporary give me root access but then it locks up saying I don't have busybox. I'm rooted but no s-off. I also noticed when I reboot into recovery I go into CWM 2.5.0.1 but other times it boots into CWM 2.5.0.7. When that happens I loose my unknown source in settings>application. Again, if this is the wrong thread, I really am sorry.
I googled alpharev and some others who have worked on rooting. Found some cached pages from Jan when they were testing to root/s-off the Aria. Basing my work on that and couple of other devices that are similar to the Aria.

Can someone confirm?

so... i have been doing a lot of research over the past couple days and have come to the conclusion that these are the steps to getting my phone completely rooted and flashed to a gingerbread ROM... let me know if i'm off or what steps may need to be added to get to the prize...
1.temp root
2.perm root
3.flash recovery image
4.flash gingerbread ROM
i am a noob trying to get by so be easy on me...
~Thanks

It's a really easy and relatively safe process, use the g-free method to root, this way http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD when your done just flash the gingerbread rom through clockwork. Remember to do nandroid backups so if something goes wrong you can revert back.

DarkPyroGuy 09 said:
It's a really easy and relatively safe process, use the g-free method to root, this way.
Click to expand...
Click to collapse
I agree. That's the best and safest process to use. Just don't try to use Visionary for perm root...although some have had success, there are just about as many that have messed up their phones with it.

so i wouldn't be safe using this guide? http://forum.xda-developers.com/showthread.php?t=928160

i've seen many people have problem using that guide
but if you don't mind using ADB (very simply) i would suggest you take the gfree/rage way also it took me 15 mins to root my g2 when i did it
Good Luck~