Related
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.
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?
Hi
I'm new to this and am wondering if I rooted my touch 4g how would I unroot it.
Sent from my HTC Glacier using XDA App
Concorde380 said:
Hi
I'm new to this and am wondering if I rooted my touch 4g how would I unroot it.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
depends on the method you used to root it.
If you used ./gfree you would need to replace the file they told you to save, then flash the PD15IMG from the hBoot.
From this thread http://forum.xda-developers.com/showpost.php?p=9551846&postcount=1
1. Rename the part7backup file that you already have to something just so you know that it is the original backup.
2. Open up terminal emulator or adb shell and type "su" + enter to get root privileges.
3. Type "cd /data/local" and hit enter.
4. Now type "./gfree -f" + enter to run gfree again. It will disable wp on the emmc and remove the brq filter in the kernel. (as well as make another backup, which you can delete if you wish)
5. Now run the "dd if=/where/your/part7backup-numbers.bin of=/dev/block/mmcblk0p7" and it should show the output:
xxxx bytes in
xxxxbytes out
xxxxxxxxxx copied in blah blah blah
6. Run "sync" and then reboot. (I didn't do this and it worked fine but it won't hurt either. )
If you have the engineering hboot 0.85.2007 installed you will still be showing s=off when you do the above revert steps. Follow these steps to reflash the stock hboot and turn s=on:
Download this file and unzip it to /sdcard on your device.
unroot.rar
http://www.mediafire.com/?12oi5elu7v2y8og
md5sum: aad4e64126cf8d92d7e8b5abb48fdadd
a. Type "su" + enter to gain root privileges.
b. Type "cd /sdcard/unroot" + enter.
c. Type "sh unroot.sh" + enter.
d. Follow the onscreen prompts.
Click to expand...
Click to collapse
If you used the root.sh to root it...just flash the PD15IMG from the hBoot.
Concorde380 said:
Hi
I'm new to this and am wondering if I rooted my touch 4g how would I unroot it.
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Depends on how you rooted it. If you rooted it with the root.sh method all you need to do is put an unrooted stock PD15IMG.zip (the image of the carrier ROM) on the root of your sdcard and reboot into bootloader and follow the menu.
If you did the whole radio S-OFF thing (the sticky thread that talks about TRUE permaroot) you will need the backup file from when you used gfree to unlock your radio and use gfree to turn your radio's security back to stock and then do the above step.
If you are already wanting to know how to unroot your phone before you have done it, you may want to forego even rooting in the first place.
eqjunkie829 said:
If you are already wanting to know how to unroot your phone before you have done it, you may want to forego even rooting in the first place.
Click to expand...
Click to collapse
Or he's just trying to be prepared and informed? Better to do that than not know what you are doing and have a panic attack when you need to exchange your phone.
Exactly
Sent from my HTC Glacier using XDA App
The best way to be prepared and informed would be reading the relevant guides in Development section, not asking a general question.
Links please
Sent from my HTC Glacier using XDA App
http://forum.xda-developers.com/forumdisplay.php?f=796
Press "Search this forum", type "unroot" or "unrooting", Enter, enjoy.
Rooting guide is sticky, and it also explains how to unroot.
Jack_R1 said:
The best way to be prepared and informed would be reading the relevant guides in Development section, not asking a general question.
Click to expand...
Click to collapse
This is true also. At least he DID post it in the general section and not development.
Concorde380: Jack is right though, learning to search will save you a ton of headache, keep you from getting flamed (well mostly), and improve your overall rep here on the forums.
What would be the easiest method to root.also if I were to sell my phone would the person know if I rooted.couldn't you just factory restore to un root
Sent from my HTC Glacier using XDA App
Concorde380 said:
What would be the easiest method to root.also if I were to sell my phone would the person know if I rooted.couldn't you just factory restore to un root
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
the easiest method is the root.sh method (see my signature) and yes they could. And no, doing a factory reset will not turn s-on.
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
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