Hey guys, so since the latest OTA, we haven't been able to downgrade nor root the shift, if we were on the latest OTA. I've been hunting through methods for downgrading and rooting, but nothing came about that actually worked. Finally having a free mind after my AP Physics exam, I got a train of though going, and tried Indirect's downgrade method, which yes, failed. What happened is when tacoroot tried to reboot the phone, it didn't have the permissions to reboot the phone, and so when the "error" on the CMD wrote that I have no permission to reboot the phone, I whipped out quick root, and did the reboots through it. Using quick root and Indirect's method of downgrading, I managed to downgrade to Android 2.2, and got to root my phone, then flash some ROMs.
Solution:
When you are in the step in Indirect's tutorial where you use the
Code:
[COLOR="Red"]adb shell sh /data/local/tmp/taco --setup[/COLOR]
command, you'll notice that tacroot doesn't have the permissions to reboot, at that time, you have to open lyriquidperfection's "HTC Quick Root v1.1.13" application and execute the reboot to recovery command through it by clicking on the drop down in reboot options, and choosing to reboot to recovery.
When you are at the step in the tutorial when you boot to hboot in order to downgrade, you can use the Quick Root application to reboot to bootloader where you flash your downgraded PG06IMG.zip.
Links:
Indirect's - Root and downgrade for Android 2.3.4
lyriquidperfection's - HTC Quick Root v1.1.13
If any clarification is needed, please post below, this is simply a quick guide to allow people to downgrade and if they choose, root it or flash a ROM. I take NO responsibility in what you do with your device nor when you void your warranty. I take NO credit for neither Indirect's method of downgrading, nor lriquidperfection's application, though I would appreciate a thanks for my compiling this "quick guide" to help you downgrade your device. If you're looking for credits on the method and application, they should be found at those posts.
Good luck,
John
*If you want to flash a rooted version of this update, go to this thread
Just keep in mind you can't flash a new ROM to your phone until you downgrade.
local.prop: permission denied resolution by CNexus: his post
For anyone else who has problems, here's what I did. if you get the message
Code:
local.prop: permission denied
After running
Code:
adb shell sh /data/local/tmp/taco --root
Then simply run the following command again (step 2 of Indirect's method)
Code:
adb shell chmod 755 /data/local/tmp/taco
The problem is that your phone resets the permissions of that directory, so it doesn't let tacoroot execute and do its thing.
Nice
Sent from my HTC Evo Shift using xda app-developers app
BigSplit said:
Nice
Sent from my HTC Evo Shift using xda app-developers app
Click to expand...
Click to collapse
Thanks, glad to see people appreciating this
Very nice, and much appreciated . Hellua nice find.
Very nice find, I would triple thanks if I could
ICS rom, here I come.
Sent from my PG06100 using xda premium
Might want to add the Software Number to the OP
indirects method for 2.3.4 wouldnt work for me on the latest ota but lyriquidperfection's - HTC Quick Root v1.1.13 method rooted like a charm. i was running completely stock 2.3.4 latest with the newest hboot and with some force and annoyance managed to somehow trick the new hboot into doing the downgrade to 2.2 and i was able to get s-off/full root again.
if i can figure out what exactly i did ill post it up for everyone but im not entirely sure. it mightve been a fluke.
all i know for sure is after i got root with lyriquidperfection's - HTC Quick Root v1.1.13
i dd the misc.img a ****load of times and then dd the eng hboot a ****load of times until it <------like 30 times in a row each lol, one after another the other.
it forced the hboot to relock the htcdev unlock and accidentally took the 2.2 downgrade (PG06IMG.zip) so i could switch hboots again.
its a helluva gamble but if anyone else has unlocked through htcdev and is willing to gamble on it have fun, if you brick it isnt my fault and i hold no responsibility over it. i think i pissed the phone off and it gave up but it worked for me. it was really a combination of using the lyriquidperfection's - HTC Quick Root v1.1.13, indirects root method, and vicodans method.
OP: so you tried my method and it failed too?
VICODAN said:
OP: so you tried my method and it failed too?
Click to expand...
Click to collapse
I believe I may have come across it. This weekend I may go back to 2.3.4 to test out some other solutions, mix and match, just to see what over all works.
JohnnyCakeXM said:
I believe I may have come across it. This weekend I may go back to 2.3.4 to test out some other solutions, mix and match, just to see what over all works.
Click to expand...
Click to collapse
yeah, i had to do a complete mashup to get my hboot to take the 2.2 downgrade, im still trying to remember how i did it and debating on taking the gamble again myself
Lol, i'm just fine with this method. Worked for me, therefore I am satisfied,
JohnnyCakeXM just a suggestion, but you may want to give a little more detail in the OP. Maybe a Step by Step .
prboy1969 said:
JohnnyCakeXM just a suggestion, but you may want to give a little more detail in the OP. Maybe a Step by Step .
Click to expand...
Click to collapse
Basically he just used a reboot app to do the needed reboots since taco couldn't and everything else is done by script
Sent from my miTouch-4G-Slide using Tapatalk 2
strapped365 said:
Basically he just used a reboot app to do the needed reboots since taco couldn't and everything else is done by script
Sent from my miTouch-4G-Slide using Tapatalk 2
Click to expand...
Click to collapse
I understand what he did . It's just I've received a few PM's asking what his steps are. So rather then explain it every time, I figured I'd give him a heads up to give a more detailed OP for the newbs.
TEAM MiK
MikROMs Since 3/13/11
Moved from THIS thread.
---
prboy1969 said:
Well I think you would've be better off posting in JohnnyCakeXM's thread. Might want to think about moving this discussion over there. But anyway. It sounds like you did not actually complete the first part of the process.
A factory Reset isn't going to do it.
Click to expand...
Click to collapse
Well thats the problem, to complete the first part, I need to get that menu to show up again, but it won't and just gives me the recovery icon
But any ideas? I was thinking of running the 2.3.4 RUU, but it may not take because of the OTA, so idk
Sent from my PG06100 using xda premium
CNexus said:
Ok, so today I got around to rooting my phone, running the latest OTA with JohnnyCakeXM's process
I ran the command that was denied "adb shell sh /data/local/tmp/taco --setup"
Gives error (expected)
Rebooted through HTC Quickroot, pressed the 3 buttons and got the "cache files" error
It gave me the "Android System Recovery <3e>" menu...but then I kinda just pulled the battery instead of selecting "Reboot system now"
Now whenever I try to go through this again to get to the "3e" menu, it just stays stuck in recovery (with the ! sign) after I press VolUp + VolDown + Power
Any help as to how to get to that menu again?
Click to expand...
Click to collapse
CNexus said:
Moved from THIS thread.
Well thats the problem, to complete the first part, I need to get that menu to show up again, but it won't and just gives me the recovery icon
But any ideas? I was thinking of running the 2.3.4 RUU, but it may not take because of the OTA, so idk
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
I do not think the 2.3.4 RUU is going to work for you. The issue I believe is that you didn't actually complete Indirects part of the method.
The command " adb shell sh /data/local/tmp/taco --setup " should have gone through before you went any further. I would try starting the whole process over again.
I'll take care of it some time tonight, or tomorrow. Just will have to re-flash stock 2.3.4 to ensure everything is in order and I'll even make a video for it. Text tutorial will come first, when it does.
prboy1969 said:
I do not think the 2.3.4 RUU is going to work for you. The issue I believe is that you didn't actually complete Indirects part of the method.
The command " adb shell sh /data/local/tmp/taco --setup " should have gone through before you went any further. I would try starting the whole process over again.
Click to expand...
Click to collapse
Thats the reason why JohnnyCakeXM posted this thread in the first place...? Because the command DOESN'T go through completely so you need to use some third party program to do the reboots for you
EDIT: Yes, I have gone through it multiple times and even checked my cables and everything to make sure that none of that was the problem before I even posted here
Sent from my PG06100 using xda premium
CNexus said:
Thats the reason why JohnnyCakeXM posted this thread in the first place...? Because the command DOESN'T go through completely so you need to use some third party program to do the reboots for you
EDIT: Yes, I have gone through it multiple times and even checked my cables and everything to make sure that none of that was the problem before I even posted here
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
What he said in the OP was :
" when tacoroot tried to reboot the phone, it didn't have the permissions to reboot the phone, and so when the "error" on the CMD wrote that I have no permission to reboot the phone, I whipped out quick root, and did the reboots through it. "
So unless I'm not reading his OP incorrectly ( which is a possibility ) , the command has to go through. But it will fail to reboot, then you use Quick Root to do the Reboots. Again this is why I suggested a Clearer Step by Step OP. So that the process can be more easily followed, and diagnosed if there is an issue . It leaves a lot less to interpretation.
prboy1969 said:
What he said in the OP was :
" when tacoroot tried to reboot the phone, it didn't have the permissions to reboot the phone, and so when the "error" on the CMD wrote that I have no permission to reboot the phone, I whipped out quick root, and did the reboots through it. "
So unless I'm not reading his OP incorrectly ( which is a possibility ) , the command has to go through. But it will fail to reboot, then you use Quick Root to do the Reboots. Again this is why I suggested a Clearer Step by Step OP. So that the process can be more easily followed, and diagnosed if there is an issue . It leaves a lot less to interpretation.
Click to expand...
Click to collapse
Yes, I ran tacoroot --setup, waited for the error, and then rebooted through Quickroot
I think I said this in my original post in the other thread..?
Sent from my PG06100 using xda premium
Related
Hi,
Thanks in advance for anyone who tries to help me.
A few weeks ago I tried to gain root access to HTC Eris. I followed the prereq and part one of the guide but stopped there. Rebooted my phone, checked the version (2.1) and went about reinstalling apps and such.
Now I want to install a different ROM so I went back and tried to start from the beginning and put PB00IMG.zip on my phone, went to hboot, let run but then I get the message "Main Version is older! Update Fail! Do you want to reboot device?"
So when I move onto III in the walk through, I get an error on the command
adb push flash_image /system/bin
It would seem like I've lost root right? Is there anyway I can check to see if I accidentally installed the leak w/o root?
Thanks,
Nate
Easy way is to do
adb shell
if the prompt is
$
your likely on leak
if the prompt is
#
your on root.
Once your on root, flash recovery.
I am anticipating the next question, so here is your answer. If you did indeed root your phone, you should have loaded a recovery image as jcase mentioned.
First, load the new ROM onto the root of your sd card. Next, power off your phone. Then, hold down the vol up button and turn on your phone. It should boot into the recovery console. From here to load another ROM, you need to perform a wipe and then load your new ROM by flashing. You should see a Wipe and Flash from Zip menu option in recovery.
In the Wipe menu, choose the first two options in order (factory reset and cache). Wait for each to complete. Next, pressing vol down should get you back to the main menu. From here choose Flash from Zip and then select the ROM zip file you loaded onto your sd card and wait for the update to complete. Last, reboot your phone from the menu.
jcase said:
Easy way is to do
adb shell
if the prompt is
$
your likely on leak
if the prompt is
#
your on root.
Once your on root, flash recovery.
Click to expand...
Click to collapse
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
xnatex21 said:
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
Click to expand...
Click to collapse
You have 2.1 from the OTA, or on phone at purchase or from an image you flashed?
try su
xnatex21 said:
$
When you say "likely" you pretty much mean "sorry but you're non-rooted and I don't want to be the one to tell you" ?
Click to expand...
Click to collapse
adb shell
$ su
If you still have a $ then you most "likely" loaded a leak rather then root. If you get a # then you are in luck.
I don't remember if the the leak that included su had adb set to root by default.
good luck.
jcase said:
You have 2.1 from the OTA, or on phone at purchase or from an image you flashed?
Click to expand...
Click to collapse
I followed a guide a few weeks ago that must have been for the leaked version of 2.1.
thisismyanonymousaccount said:
adb shell
$ su
If you still have a $ then you most "likely" loaded a leak rather then root. If you get a # then you are in luck.
I don't remember if the the leak that included su had adb set to root by default.
good luck.
Click to expand...
Click to collapse
I get
su: permission denied
Click to expand...
Click to collapse
I guess that means my phone I'm stuck with it...FML!
xnatex21 said:
I guess that means my phone I'm stuck with it...FML!
Click to expand...
Click to collapse
Yes, sadly you are now stuck with the Leak.
Stay tuned as the devs are still working on it.
g00gl3 said:
Yes, sadly you are now stuck with the Leak.
Stay tuned as the devs are still working on it.
Click to expand...
Click to collapse
Does anyone know what HTC says about all of this? Can I send the phone back to them and have them "restore" the phone to factory settings?
xnatex21 said:
Does anyone know what HTC says about all of this? Can I send the phone back to them and have them "restore" the phone to factory settings?
Click to expand...
Click to collapse
Technically, modifying your device would void warranties. Even if they could "restore" the device, it would still have the newer bootloader that is causing the rooting issue. Some people have "lost" or "broken" the device bad enough that they could get a replacement from Verizon. However, there is mixed results as to what bootloader the refurbished devices come back with.
I posted before about the safety of re-rooting my eris from 1.5 to a rooted 2.2 rom, and due to lack of responses on any forums over the web, I jumped the gun today. First off my Eris after un-rooting it, wouldn't take the OTA update for 2.1, it downloaded and verified that, but after it rebooted, it was still at 1.5 saying no new updates are available. I cannot download the eris 1 click root app as it's only for 2.1 I'm assuming because it says it's not compatible with 1.5 firmware when I download it. I tried to follow this guide [Walkthrough] From stock (1.5) to rooted 2.1 (update - new link) - xda-developers and when I installed the PB00IMG.zip it downloaded but failed to flash and the screen read "Main version is older". I tried this guide All-In-One Auto-Root Script - Page 4 - xda-developers and when it says it's flashing the root image, it goes straight to a screen with only two options "recovery" something and "fastboot". None of which are listed as options in the guides. I am just trying to root my 1.5 eris and flash the KaosFroyo V3 eris rom with Amon Ra's recovery image. Thanks if anyone can help my problem, or shed light on the situation! Sorry if there's been a fix to this problem already stated, I've desperately been browsing many forums and hundreds of replies to no avail. Thanks again.
It looks to me like you got a pretty reasonable answer to the same question over on Android Forums
bftb0
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.
After selecting "recovery" from HBOOT, all I get is a black screen with a red warning triangle. 20mins pass, and nothing changes.
I got the phone 2 days ago, and have been unsuccessful in rooting it. Every guide has failed at one point or another. Temp root works, via Visionary and rage, but it will not stick. Rom Manager was able to flash Clockwork, but it didn't work either.
Is something wrong with my phone, or am I just doing it wrong?
It is common for the recovery flash to fail. The red triangle is from the stock recovery software, which doesn't do anything.
Flash the recovery again.
HTC Glacier running CM7 #15
You have to reflash recovery
Sent from my HTC Glacier using XDA App
jggimi said:
It is common for the recovery flash to fail. The red triangle is from the stock recovery software, which doesn't do anything.
Flash the recovery again.
HTC Glacier running CM7 #15
Click to expand...
Click to collapse
So, the stock recovery doesn't do anything, and this is normal? That's a relief.
I still can't flash CW because its not rooted. Every proceedure fails. Ill update with the actual output when I get home tonight.
Sent from my HTC Glacier using XDA App
pagnaet said:
So, the stock recovery doesn't do anything, and this is normal? That's a relief.
I still can't flash CW because its not rooted. Every proceedure fails. Ill update with the actual output when I get home tonight.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
i know this isnt the right thread, but i noticed in your signature that your s-on wont turn off...did you try taking a break and doing it again? i have had times when i tried to root my devices and i would sit there for 2 hours redoing the process over and over then take a hour break, and then get it right away.
Have you tried gfree for S-OFF? I have not heard of that failing. Older methods, yes. My phone rooted with an older method 100% first try -- so easy! My wife's phone, however, was a different story. It absolutely would NOT go S-OFF even after it let me flash the eng hboot file! Which is by itself S-OFF!
Grankin suggested the phone may have a bad eMMC controller and to swap it. I did, and her replacement rooted as easily as my phone (this was a few months back, before gfree).
So if things *truly* are not working and you are certain you've tried every permutation of rooting and just don't have success on one phone even when others work -- swap it.
Genocaust said:
Have you tried gfree for S-OFF? I have not heard of that failing. Older methods, yes. My phone rooted with an older method 100% first try -- so easy! My wife's phone, however, was a different story. It absolutely would NOT go S-OFF even after it let me flash the eng hboot file! Which is by itself S-OFF!
Grankin suggested the phone may have a bad eMMC controller and to swap it. I did, and her replacement rooted as easily as my phone (this was a few months back, before gfree).
So if things *truly* are not working and you are certain you've tried every permutation of rooting and just don't have success on one phone even when others work -- swap it.
Click to expand...
Click to collapse
It's starting to look that way. I tried gfree again tonight.
Code:
Attempting to power cycle eMMC... Failed (not fatal)
Module tried to power cycle eMMC, but could not verify write-protect status.
And then it fails:
Code:
Error reading input file.
And then it freezes.
What do I tell Tmob? Other than the root-resistance thing, the phone is solid.
Sorry I didn't see this sooner! I got your PM though, hope it goes well! You may consider posting this over in the gfree thread and see if you can pull some debug info if one of the devs there would like it, as I've never seen gfree fail like that before.
Gfree 0.2 saves the day!
On a last ditch effort to determine if it was my phone at fault, I tried gfree-0.2(as opposed to 0.4) after reading this post: http://forum.xda-developers.com/showthread.php?p=10560636&highlight=eMMC+fails#post10560636
To do it right, I followed Cyanogen's method and files on his wiki, but with the older gfree. Well, eMMC power cycled just fine and everything worked perfectly, S-OFF, and I'm so glad I don't have swap this flawless device for a possible defect.
Thank all of you for your help, and what you do here. XDA is great community.
pagnaet said:
It's starting to look that way. I tried gfree again tonight.
Code:
Attempting to power cycle eMMC... Failed (not fatal)
Module tried to power cycle eMMC, but could not verify write-protect status.
And then it fails:
Code:
Error reading input file.
And then it freezes.
What do I tell Tmob? Other than the root-resistance thing, the phone is solid.
Click to expand...
Click to collapse
You get that error because your not running gfree as root
you need to temp root, then open terminal
type su
the /data/local/gfree -f
then you should be all set.
option94 said:
You get that error because your not running gfree as root
you need to temp root, then open terminal
type su
the /data/local/gfree -f
then you should be all set.
Click to expand...
Click to collapse
I can assure you that I'm not that stupid. Temp root was never a problem. Gfree 0.4 just didn't like my phone.
ok so i recently picked up a used mytouch 4g. i rooted it and have superuser ability along with rom manager. have tried and think i have installed 3.0.2.4 clockwork recovery. i flashed that multiple times.
however when i try and boot into recovery i merely get to the phone with the red !. am i missing something?
thanks for your time!
kdm212 said:
ok so i recently picked up a used mytouch 4g. i rooted it and have superuser ability along with rom manager. have tried and think i have installed 3.0.2.4 clockwork recovery. i flashed that multiple times.
however when i try and boot into recovery i merely get to the phone with the red !. am i missing something?
thanks for your time!
Click to expand...
Click to collapse
does you phone say s-off at the top when you boot into hBoot?
neidlinger said:
does you phone say s-off at the top when you boot into hBoot?
Click to expand...
Click to collapse
s-on. however i thought you could still root and flash roms with it on. looks like im wrong?
kdm212 said:
s-on. however i thought you could still root and flash roms with it on. looks like im wrong?
Click to expand...
Click to collapse
you are correct in your assumption.
The HTC Glacier and Vision have a security protocol in place that will revert the phone back to a 100% stock fashion every-time you turn off the phone. If you wish to do custom ROMs, recovery images, and radio files you must turn the "s-on" to "s-off".
neidlinger said:
you are correct in your assumption.
The HTC Glacier and Vision have a security protocol in place that will revert the phone back to a 100% stock fashion every-time you turn off the phone. If you wish to do custom ROMs, recovery images, and radio files you must turn the "s-on" to "s-off".
Click to expand...
Click to collapse
ok so i did see the thread for s-off yet it seems very intensive. im also assuming theres no other way to get s-off.
kdm212 said:
ok so i did see the thread for s-off yet it seems very intensive. im also assuming theres no other way to get s-off.
Click to expand...
Click to collapse
You can try the sh root.sh method.
1a ) download and install VISIONary.apk. Download from here
-Looks like you've done that since you have come this far.
1b) when you run VISIONary make sure both set system to R/W and Run Visionary.sh are both checked.
2) Download the script to the root of your SDcard
This is the file
3) Extract the folder from the .zip and store the folder with it's contents onto the root of the SDcard.
4) Download Terminal emulator from the market
-Link to the market for this app.
5) open the Terminal Emulator and type
Code:
$ su
#
The Dollar Sign " $ " should change to a pound sign " # ". If the Super user program ask for your permission, you'll want to grant it. You're screen should look like the box just above this line.
6 ) Change the directory to the root folder
Code:
# cd /sdcard/root
7) run the script
Code:
# sh root.sh
make sure you do not get any errors.
If you havent you can reboot into hBoot and look for s-off.
i personally used this method to root my phone before i left the t-mobile store when i bought the phone.
I CANNOT AND WILL NOT BE HELD ACCOUNTABLE IF YOU MESS UP YOUR PHONE. ROOTING ONES PHONE IS SERIOUS BUSINESS AND SHOULDN'T BE TAKEN LIGHTLY. IF YOU SHOULD BLAME ME I WILL LAUGH AND POINT.
neidlinger said:
You can try the sh root.sh method.
1a ) download and install VISIONary.apk.
-Looks like you've done that since you have come this far.
1b) when you run VISIONary make sure both set system to R/W and Run Visionary.sh are both checked.
2) Download the script to the root of your SDcard
This is the file
3) Extract the folder from the .zip and store the folder with it's contents onto the root of the SDcard.
4) Download Terminal emulator from the market
-Link to the market for this app.
5) open the Terminal Emulator and type
Code:
$ su
#
The Dollar Sign " $ " should change to a pound sign " # ". If the Super user program ask for your permission, you'll want to grant it. You're screen should look like the box just above this line.
6 ) Change the directory to the root folder
Code:
# cd /sdcard/root
7) run the script
Code:
# sh root.sh
make sure you do not get any errors.
If you havent you can reboot into hBoot and look for s-off.
i personally used this method to root my phone before i left the t-mobile store when i bought the phone.
I CANNOT AND WILL NOT BE HELD ACCOUNTABLE IF YOU MESS UP YOUR PHONE. ROOTING ONES PHONE IS SERIOUS BUSINESS AND SHOULDN'T BE TAKEN LIGHTLY. IF YOU SHOULD BLAME ME I WILL LAUGH AND POINT.
Click to expand...
Click to collapse
tried that and it does have s-off. thanks! however when i try to boot into recovery im still stuck with the phone and !...
EDIT: /sdcard/root/wpx.ko failed (function not implemented)
kdm212 said:
tried that and it does have s-off. thanks! however when i try to boot into recovery im still stuck with the phone and !...
Click to expand...
Click to collapse
After doing the above method you're gonna have to reinstall the recovery from Rom Manager. Watch it carefully do not let the phone sleep (I recommend going to delopment check never sleep while charging and plug it into a charger while it downloads.) You have to pay attention because it will ask for SU permissions when it finishes downloading, and it for some reason only gives you like 3 or 4 seconds instead of the usual ten. If you have already tried installing the recovery you may wanna go to the SU App and make sure that Rom Manager didn't get denied premission which is the default if you do not select Allow fast enough.
got it! thank you very much! cant wait to play with a new rom. any recommendations?
Virtuous Fusion 1.0.6 with sense 3.0/3D is fantastic!. Give it a go.
kdm212 said:
got it! thank you very much! cant wait to play with a new rom. any recommendations?
Click to expand...
Click to collapse
Try out a sense rom and non sense to decide which you like best. virtuous fusion 1.0.6 is pretty nice sense rom and cm7 or royalginger are awesome non sense roms.
im going to try both!
kdm212 said:
im going to try both!
Click to expand...
Click to collapse
Make sure to do Nandroid Backups prior to flashing new ROMs. And just a fair warning you might want to install the .85 (engineering) hBoot.
what is that hboot all about?
neidlinger said:
Make sure to do Nandroid Backups prior to flashing new ROMs. And just a fair warning you might want to install the .85 (engineering) hBoot.
Click to expand...
Click to collapse
Absolutely a great idea, little nerve wracking to make changes to hboot and radio but very worth it. The directions how to do engineering boot loader are in the ultimate s-off sticky. Confusing at first, but after you do it once it gets easier.
Sent from my HTC Glacier using XDA App
kdm212 said:
what is that hboot all about?
Click to expand...
Click to collapse
It's a option that helps prevent bricking the device. Allows you to flash section of to phone's workings
[sent via Cyanogen powered Android]
Shivansh said:
Virtuous Fusion 1.0.6 with sense 3.0/3D is fantastic!. Give it a go.
Click to expand...
Click to collapse
+++++100000000000000000000000000000000000000000000 BEST ROM I HAVE EVER USED!!!!!
*so far
so first i must thank you all for the help. now the bad, i decided to buy another mytouch 4g. my fiance liked the old one so much that she took it. so now im here with a new one and have nothing but problems.
im running 2.2.1 and seem to be able to root the phone. su icon is on and everything. BUT if i reboot the phone its like i have to start over. im not just temp rooting either. second, i cant get ANY terminal emulator to let me have su access.
visionary, z4root, adb. you name it and i seem to think ive tried it. lol this is unfair, my chicks phone is way better than mine.
any help would be so awesome.
kdm212 said:
so first i must thank you all for the help. now the bad, i decided to buy another mytouch 4g. my fiance liked the old one so much that she took it. so now im here with a new one and have nothing but problems.
im running 2.2.1 and seem to be able to root the phone. su icon is on and everything. BUT if i reboot the phone its like i have to start over. im not just temp rooting either. second, i cant get ANY terminal emulator to let me have su access.
visionary, z4root, adb. you name it and i seem to think ive tried it. lol this is unfair, my chicks phone is way better than mine.
any help would be so awesome.
Click to expand...
Click to collapse
Trade phones back so she gets the new one. Problem solved!
Seriously though, some of these phones won't root with visionary root.sh method. Bad news is if it's not working you will need to try gfree method to root which is indicative of a phone with the emmc chip that is considered to be faulty. For more info search for the thread about emmc chips.
Sent from my demonSPEED Glacier using XDA Premium App
so this is not a rootable phone?
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