Related
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?
This is second myTouch 4G that refuses to get S-OFF via root.sh method. I have a good chip and I followed all the steps entirely several times.
Some said that it is impossible with a good chip. What am I missing?
PS: I'm using the Unlockr guide
Which guide are you following and what exactly happens when you get through all the steps?
I was having the same problem for a long time with mine despite following every step word for word. Whenever I ran root.sh it would only run for like 4 or 5 seconds and then stop itself, rather than the 20-30 seconds that most people seem to say is the usual. After like 20 failed attempts I decided to get rid of my soft root, redownload every file(including visionary) and try again and that seemed to work out for me.
Just saw your edit lol, try using this guide instead:
http://forum.xda-developers.com/showthread.php?t=858021
I feel like it gives pretty good directions. I'd also recommend redownloading your root.sh files from there as well. Perhaps a bad download left you with a dysfunctional script that won't root you properly.
AlanB412 said:
Which guide are you following and what exactly happens when you get through all the steps?
I was having the same problem for a long time with mine despite following every step word for word. Whenever I ran root.sh it would only run for like 4 or 5 seconds and then stop itself, rather than the 20-30 seconds that most people seem to say is the usual. After like 20 failed attempts I decided to get rid of my soft root, redownload every file(including visionary) and try again and that seemed to work out for me.
Click to expand...
Click to collapse
I use this one:
http://theunlockr.com/2010/12/10/how-to-temporarily-root-the-t-mobile-mytouch-4g-htc-glacier/
And then Permroot steps.
It does it quick, and seem to finish without errors.
I just realized, I should've asked you this first because it makes a really big difference. Is your phone on Android 2.3.4 already? If you got the Gingerbread update from t-mobile there's currently no known way to get root.
The thread I linked you to will only work if your phone is still on Froyo
AlanB412 said:
I just realized, I should've asked you this first because it makes a really big difference. Is your phone on Android 2.3.4 already? If you got the Gingerbread update from t-mobile there's currently no known way to get root.
The thread I linked you to will only work if your phone is still on Froyo
Click to expand...
Click to collapse
Nah, Im on latest froyo. Terminal Emulator keeps giving exactly same error: insmod: init_module '/sdcard/root/wpx.ko' failed (function not implemented)
PS: Search seem getting into a dead end. I will probably use gfree again
If I remember correctly, that function not implemented message is supposed to show up when you do it properly. After you get that message you're supposed turn phone off, reboot into hboot and it should say S= Off. Then after that you just have to reboot your phone again, head into Visionary, temproot one more time, and then click attempt PermRoot. Once your phone reboots you should have root.
After you get that "function not implemented" message does hboot still say S= On?
AlanB412 said:
If I remember correctly, that function not implemented message is supposed to show up when you do it properly.
After you get that message does hboot still say S= On?
Click to expand...
Click to collapse
yeap. I just went and did it with gfree. Is it true that gfree causing eMMC to fail? I saw it somewhere in the forum
AntonJart said:
yeap. I just went and did it with gfree. Is it true that gfree causing eMMC to fail? I saw it somewhere in the forum
Click to expand...
Click to collapse
Well I guess that works out for you then. As long as you have the good emmc chip you don't need to worry about the chip failure. Gfree can cause the chip failure for people with the bad chip though.
To revert back to stock after using the gfree method is a bit more annoying than usual though, regardless of what chip you have, because it does something to your radio in order to give you the permaroot. So if you ever do decide to unroot you'll have to take some extra steps to undo the gfree changes.
But that's only a problem if you want to unroot though lol
AlanB412 said:
Well I guess that works out for you then. As long as you have the good emmc chip you don't need to worry about the chip failure. Gfree can cause the chip failure for people with the bad chip though.
To revert back to stock after using the gfree method is a bit more annoying than usual though, regardless of what chip you have, because it does something to your radio in order to give you the permaroot. So if you ever do decide to unroot you'll have to take some extra steps to undo the gfree changes.
But that's only a problem if you want to unroot though lol
Click to expand...
Click to collapse
On the first mytouch unrooting was quite easy. I recovered the back up (s-off still stayed) and then applied stock image. Thanks for your replies
Okay, here is the deal. I was trying to change around some stuff on my phone, the IMEI number to match the one on my prepaid tracphone. So far, before I changed the IMEI, i had it rooted and everything was slamming. But it would disconnect me after about a half hour. I am changing the IMEI to see if it fixes this, but after all this I had to revert back to a total stock flash of 2.2.1 HTC rom, it updated everything, one of those PBxx.img ones you do during the bootloader.
So now I've rooted it with visionary, and it hardly works, won't permaroot, but I get regular root. So I did another method on a wiki and have permaroot now. Updated SU, clockwork mod, ETC and everything works (well it installs and prompts me to give super user access then doesnt complain.)
HERE IS THE PROBLEM: I CANT CHANGE RECOVERY OR BOOTLOADER TO S-OFF
I have used gfree (multiple versions) to turn s off, and turn off all locks and to change the bootloader the nb0 one. BUT NOTHING gives.
>Clockworkmod from the rooted main screen, when i open the app, it won't install the clockwork mod recovery.
>When booting to recovery, the phone goes to stock recovery with the red triangle and phone. Upon where you have to push VOL UP + PWR button to see any options, and they are just the stock ones, (reboot, apply update:sdcard, etc)
I was wondering if someone had a signed image that they could link to me or send or whatever that has the s-off in a format that I can use with the BOOTLOADER; i.e.: Just put it on SD-CARD, hold "VOL UP+PWR" then it will do the update. U know, like radios are flashed.
If you can help me please, help me. I was so excited with this phone and moving along and now this.... ARG! lol. Thanks guys any and all input is appreciated no matter how irrelevant!
peace
GLACIER PVT SHIP S-ON
HBOOT-0.86.0000
MICROP-0429
RADIO-26.03.02.26_M
eMMC-boot
Sep 27 2010,11:12:59
You don't have perm-root.
Gfree can't work without root. Since you don't have perm-root without Gfree, you need temp-root.
While not S-OFF, you can't have perm-root. Period. End of story. Temp-root and execute Gfree.
Execute the rooting guide in Wiki properly, and you'll have S-OFF.
Of course, having no perm-root makes it impossible to flash recovery, or flash anything at all.
help.. tried root explorer, astro, es file..and have had no luck flashing to better roms...help
Sent from my HTC Glacier using XDA Premium App
If you are using Visionary R14, try R11. And f*ck wiki.
Jack_R1 said:
You don't have perm-root.
Gfree can't work without perm-root.
While not S-OFF, you can't have perm-root. Period. End of story.
Execute the rooting guide in Wiki properly, and you'll have S-OFF.
Of course, having no perm-root makes it impossible to flash recovery, or flash anything at all.
Click to expand...
Click to collapse
G-free turns s-off. If he has a bad eMMc chip, G-free is the only method he can use. And some phones have issues with the newer version of visionary.
lowandbehold said:
G-free turns s-off. If he has a bad eMMc chip, G-free is the only method he can use. And some phones have issues with the newer version of visionary.
Click to expand...
Click to collapse
I guess I wasn't clear enough in my response above, and wrote "perm-root" where just "root" was in order. Edited.
In any case, when was the last time you've read the Wiki? I suggest you look at it again.
I don't know if I am explaining correctly.
I applied the root method using visionary r14 because thats the latest from the site, it temp roots, but does not perma root.
I did a su, and got root, but I have to SU before i get root, it asks for SU permissions and I allow and I have root. (all this is done in a shell). So I know I have root, i can open up the system to read write and even delete some stock .apk and other files that aren't supposed to be deleted. So its all good. I can chmod 777, i know whats up there.
I did all this madness, SU updates to the most current binary, clockwordmod both an older and the newest version open, ask for and allow SU permission, and all that appears to work fine. EVEN with the friggen flash clockworkmod recovery, it says current recovery: clockworkmod x.x.x.x (meaning whatever the version is, tried a bunch).
BUT WHEN I BOOT TO RECOVERY OR BOOTLOADER, S-ON and friggen stock recovery for me. WHAT THE heck. its like its ignoring what I do to flash the bootloader.
Does anyone have a PBxx.IMG they can send, hopefully signed, that I can just use to update? or link to one? also, and update.zip for the stock recovery would work too.
HERE's the thing, its a T-mobile phone, and my TRACPHONE Prepaid sim works on it, but that *MIGHT* just be because TRACFONE = AT&T also T-Mobile=AT&T now also.
But I think the sim is unlocked, I'm waiting on other sim to come in the mail before I can verify for sure.
MAIN thing i need is a signed (or I'll even play with an unsigned) PBXX.img file for either the bootloader or recovery, or an update.zip one. At this point, if you have a lower version of 2.2.1 that has the whole entire shebang, (the radio, bootloader, os, recovery, etc) then I'll appreciate that too.
I just can't find it on here after days of searching and I am needing a push in the right direction. And google's overloaded with the SAME article just in different spam blog formats. Thx guyz
You CAN'T.
Everything you do when you're temp-rooted, DOESN'T GO TO THE eMMC! It stays in memory (eMMC cache), and the next time you reboot - everything is GONE. All your file deletions, chmods, etc - they're NOT REALLY EXECUTED. Reboot and see for yourself.
The only thing that will make it stay - is running gfree and gaining S-OFF.
The link, as everything else you're looking for, is in Wiki. Look in the Downgrade guide, there's a link for 2.2.1 RUU for MT4G. But it won't help you - you're just being stubborn and unwilling to read. YOU DIDN'T EXECUTE PERMAROOT PROPERLY, AND UNTIL YOU DO - YOU WON'T BE ABLE TO FLASH A DAMN THING.
The Wiki links to a Gfree method guide. Read it and execute it STEP BY STEP.
Okay, i did it
Here is what I did. I went in manually and copied the .nb0 to the file several times in a row.
Visionary does not work, the only way I can root this thing, without some type of temproot visionary app that messes up, is this way:
http://wiki.rootzwiki.com/index.php/HTC_myTouch_4G
Also, I am hoping I am correct, but this is how its laid out in the /dev block...
mmcblk0p18: HBOOT DATA (bits) And....
mmcblk0p21: RECOVERY DATA (bits) data or bits, whatever you want to call it. (its not a file)
Okay. So with that being said;
/dev/block/mmcblk0p18 = hboot 'file' and this is what i did.
Using 'dd' which is a unix command that just does low level convert and copy, will take the input file if=hboot_hacked_file.nb0 and then put it to the output device converting it and whatnot, the output file of=/dev/block/device
so it looks like this in example:
Code:
# dd if=/directory/filename.xxx of=/dev/block/output_device_or_file
Oh, and another thing that might just be paranoia... The wifi was on and it wasn't doing what it was supposed to do, I noticed it also being active unusually, I should have put wireshark on and checked it out, but didn't think about it at the time. Now that wifi off, it feels as if its fine now. It was almost like another user was in it. But thats probably just paranoia..... or the t-mob trying to mess me around!!!
This IS the gfree method, and you ARE running an app to gain temp-root there.
Copying the bootloader didn't help you at all, it was only a later step. It wouldn't stick if not for gfree.
Running gfree did.
Oh well, I guess that it's useless to explain. Glad it worked.
naw bro, its good that you explain what you mean, its not useless to explain anything. Here is what I'm saying... gfree -f is supposed to do the S-OFF right? well, it didn't. it also said failed or error or something at the end. Once I did the 'dd' command not just once, but several times and VERIFIED that it was working and different, while having # then I ran gfree again and it said SUCCESS at the bottom and THAT did it bro. SO that, in the end, turned my s-off and gfree unlocked my sim super unlock and cid unlock too.
I've cloned my IMEI because its legal, its my own phone and I'm not doing anything extra other than using it to make calls which I pay for at outrageous prepaid prices.
Does anyone know where that information is located by the way, just for information purposes... I've already done it using a hex editor and a part7.bin file... but I just am not quite sure on EXACTLY what I've done. like, the locations of what file or data that i've flashed. With CDMA, I usually enter QPST programming and all that and just just play till my heart's content... but now I'm trying to learn GSM and I want to know if there is a way to enter that kind of programming also. Or are us fellas forced to dump .bin files, hex edit, then reflash or reflex em...
Just lookin for some pushes in the right direction for programming in the GSM area.
Also if you have links to radios, all of them, previous and what not, I would appreciate it too
Flashing hboot, superuser or not, several times or not, didn't do a thing for unlocking.
For what reason gfree failed initially - I don't know, but when you ran it again and it didn't fail - that did it all. Otherwise you'd still be with S-ON, and the bootloader would still be the same.
You can't really argue against HW. That's how it works.
Radios are here:
http://forum.xda-developers.com/forumdisplay.php?f=796
Look for "Glacier Radios" sticky.
Like I said before as well. There are alot of issues with R14...find and use visionary R11. You are not the first person to have issues with visionary, and with the majority of them, the downgrade solved the problem.
Not true
I have try everything and nothing work. R11, r14 from visionary and it dosent work. Please devs try to get another method for the people that nothing work. I have hboot 0.86.0000
ahernandez646 said:
I have try everything and nothing work. R11, r14 from visionary and it dosent work. Please devs try to get another method for the people that nothing work. I have hboot 0.86.0000
Click to expand...
Click to collapse
Do you have Android version 2.3.4?
If so, Visionary won't work. You have to downgrade to 2.2.1 first. There is no way around this. But it's easy to do.
Skipjacks said:
Do you have Android version 2.3.4?
If so, Visionary won't work. You have to downgrade to 2.2.1 first. There is no way around this. But it's easy to do.
Click to expand...
Click to collapse
No, that's the froyo bootloader.
What happened when you ran visionary? Did you have usb debugging checked? Sometimes the temp root works on the first try, sometimes on the tenth. If it doesn't work, reboot and try again. If it still doesn't work after several attempts do a factory reset and try again. Sometimes a clean slate helps.
Sent from my HTC Glacier using XDA App
i do have 2.2.1 but i had a mytouch 3g slide and i root it. but for some reason i can't get the mytouch 4g to do it. i will re-try everything again.
Thanks to all that have reply.
OK.... I said f*ck it to the replacement phone.... DOn't want it... Can't root it... (besides I found out it had the ****ty screen that is manufactured in Taiwan, not China). Further, I want to root it now and I cannot do it with stock gingerbread. Sending back replacement phone today...
BUT....Unfortunately, I restored Froyo to my old phone. So now I have an unrooted phone, with Android 2.2.1.
But.... I STILL DO NOT HAVE THE ABILITY TO CONNECT VIA USB TO USE ADB
I cannot use any wifi adb methods as they all require root.
I cannot use Visionary for temp root as the cyanogen root page wiki says it should be uninstalled.
Nonetheless, I copied all of the needed files to my sdcard, so I am ready....
BUT I NEED TEMP ROOT FROM THE EMULATOR.
Does anyone know how to get temp root for FROYO through the emulator only??.....OR, another Visionary type apk which will give me temp root???
Sorry can"t help on your problem, but how did you restore stock froyo? Had the same replacement prob, sent it back to T-mobile, called CS told them about issues, they're sending a MT4GSlide, call CS you might get lucky like I did
use the "how to root.sh root your phone".
i used that in the T-Mobile store to root my before i left the store when i bought the device.
Marquis63 said:
Sorry can"t help on your problem, but how did you restore stock froyo?
Click to expand...
Click to collapse
The phone I restored to stock Froyo was my old phone... It was rooted already. I just wanted to restore it to a factory condition so I wouldn't have any problems returning my old, and rooted/heavily modded phone to TMO.
So I just took the .img that you can download from this thread LINK
Then you just make sure it is on the root of your sdcard, then boot into hboot by holding the volume down while pressing the power button. It will boot and think it is an "update", but it will just restore it to the stock.
Obviously this cannot be done from 2.3.4 because it realizes it is an old version... If you have a phone with stock 2.3.4 you have to trick it into letting you downgrade from gingerbread to froyo using this thread: LINK
---------- Post added at 01:07 PM ---------- Previous post was at 12:37 PM ----------
Marquis63 said:
Sorry can"t help on your problem, but how did you restore stock froyo? Had the same replacement prob, sent it back to T-mobile, called CS told them about issues, they're sending a MT4GSlide, call CS you might get lucky like I did
Click to expand...
Click to collapse
That's great! But I told them about the fact I solved my wifi problem.... Besides, I already tried to shake them down for a Sensation... no go.
The Slide version looks great... Better camera and faster.... But for now, I will stick with the 4G regular unless I get another issue....
My solution (in another thread) to my wifi problem requires you select "wifi only" under the wifi calling app. If this becomes really problematic and inconvenient, I will call them back... Will try to get a Sensation again or a 4G Slide then.
syntropic said:
OK.... I said f*ck it to the replacement phone.... DOn't want it... Can't root it... (besides I found out it had the ****ty screen that is manufactured in Taiwan, not China). Further, I want to root it now and I cannot do it with stock gingerbread. Sending back replacement phone today...
BUT....Unfortunately, I restored Froyo to my old phone. So now I have an unrooted phone, with Android 2.2.1.
But.... I STILL DO NOT HAVE THE ABILITY TO CONNECT VIA USB TO USE ADB
I cannot use any wifi adb methods as they all require root.
I cannot use Visionary for temp root as the cyanogen root page wiki says it should be uninstalled.
Nonetheless, I copied all of the needed files to my sdcard, so I am ready....
BUT I NEED TEMP ROOT FROM THE EMULATOR.
Does anyone know how to get temp root for FROYO through the emulator only??.....OR, another Visionary type apk which will give me temp root???
Click to expand...
Click to collapse
Go to youtube type gfree mytouch 4g look for author Mackster248 video I would link but I'm a noob
Sent from my HTC Glacier using XDA App
Z4Root is another app that might work on Froyo.
You can manually execute psneuter or rageagainstthecage from Terminal Emulator. Search Google, it'll guide you for both.
Or you could just not listen to CM Wiki, and use Visionary.
I think Visionary screws things up pretty badly.... I found this out the hard way.
I think I have done a hard reset (removed battery + factory reset) about 8 times so far.
I have been using a combination of Visionary, followed by a root.sh script from this link. Then I do get root.... but it is tremendously precarious.
I then uninstall Visionary, use ADBwireless as I have root now and proceed to follow the Cyanogen instructions.....
But then... whenever I have to run psneuter, it boots me out of the adb shell and I have to start everything all over again.... I have to do a factory reset to get Visionary to work that one f*cking precious time.
I just tried it again just now (I have been modifying steps and things to get it to work)... And now... every time I do a factory reset and run visionary, I don't get a Superuser Root... I get "UNKNOWN USER ROOT" in the emulator.... I have know idea what that means, but it is not root....
I have been at this for days and losing my mind. I cannot believe I can't root this phone.... especially now in Froyo... Without a god**mn USB CABLE!!!
Jack_R1 said:
Z4Root is another app that might work on Froyo.
You can manually execute psneuter or rageagainstthecage from Terminal Emulator. Search Google, it'll guide you for both.
Or you could just not listen to CM Wiki, and use Visionary.
Click to expand...
Click to collapse
z4 root doesn't work with the MT4G...
Hey... I had a thought..
Since I have nandroid backups... If I get a Visionary root (if I can....), can I just restore my phone with one of them... I mean those backups are all simunlock, eng hboot, radio =111111111, etc. full root.
But... I thought I would ask so I do not have to do another 15 hard resets to figure out that it doesn't work.
syntropic said:
Hey... I had a thought..
Since I have nandroid backups... If I get a Visionary root (if I can....), can I just restore my phone with one of them... I mean those backups are all simunlock, eng hboot, radio =111111111, etc. full root.
But... I thought I would ask so I do not have to do another 15 hard resets to figure out that it doesn't work.
Click to expand...
Click to collapse
no, because VISIONary.apk only gives root access, not S-off. S-off is needed to flash Clockworkmod Recovery, which is needed to flash the backups.
saranhai said:
no, because VISIONary.apk only gives root access, not S-off. S-off is needed to flash Clockworkmod Recovery, which is needed to flash the backups.
Click to expand...
Click to collapse
Thanks... and for whatever reason... even though I think I rooted my phone successfully, I cannot restore any of my nandroid backups... I get an error in Rom Manager.... and while in recovery, I get an error of "files missing".
Now I cannot even boot the phone. It is stuck at the myTouch Splash.
I am so f*cking tired of doing this... Nothing has worked--
I cannot believe I reset this phone to Froyo in anticipation of sending it back....
I ended up keeping it because it had the better screen and because I thought I had solved my wifi problem...
I am without a phone at all at this point.
removed post
syntropic said:
OK.... I said f*ck it to the replacement phone.... DOn't want it... Can't root it... (besides I found out it had the ****ty screen that is manufactured in Taiwan, not China). Further, I want to root it now and I cannot do it with stock gingerbread. Sending back replacement phone today...
BUT....Unfortunately, I restored Froyo to my old phone. So now I have an unrooted phone, with Android 2.2.1.
But.... I STILL DO NOT HAVE THE ABILITY TO CONNECT VIA USB TO USE ADB
I cannot use any wifi adb methods as they all require root.
I cannot use Visionary for temp root as the cyanogen root page wiki says it should be uninstalled.
Nonetheless, I copied all of the needed files to my sdcard, so I am ready....
BUT I NEED TEMP ROOT FROM THE EMULATOR.
Does anyone know how to get temp root for FROYO through the emulator only??.....OR, another Visionary type apk which will give me temp root???
Click to expand...
Click to collapse
Have you tried gfree?
+1 it might be your only option.
Sent from my LG-P999 using XDA Premium App
And to add to that, gfree doesn't exactly require ADB.
You can use that paid root app to manually push the necessary files into system>data>local.
mackster248 said:
And to add to that, gfree doesn't exactly require ADB.
You can use that paid root app to manually push the necessary files into system>data>local.
Click to expand...
Click to collapse
I finally managed to do it. But it took a lot of trial and error.
I learned:
You can only be rely on exactly 1 temp root from visionary after a factory reset. Any more and you are getting lucky.
Visionary definitely should be uninstalled before following that guide.
I may make a guide after belabouring 17 hours to accomplish this.
I guess I am lucky... If TMO had sent me a phone with a good screen, I would have been tempted to keep that one. If I did, it would have been stock 2.3.4, and I would probably not have root yet.
Sent from my HTC Glacier using xda premium
syntropic said:
I finally managed to do it. But it took a lot of trial and error.
I learned:
You can only be rely on exactly 1 temp root from visionary after a factory reset. Any more and you are getting lucky.
Visionary definitely should be uninstalled before following that guide.
I may make a guide after belabouring 17 hours to accomplish this.
I guess I am lucky... If TMO had sent me a phone with a good screen, I would have been tempted to keep that one. If I did, it would have been stock 2.3.4, and I would probably not have root yet.
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Thanks for the link, yes you should write a guide, it will help others in your situation. I didn't even ask, the CSR offered the MTS4G. Glad you finally got it figured out, it can make you crazy LOL
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