Everything will get wiped. It's back to factory. There is a way to filter your contacts to see whether they are on Gmail or phone. I forget how you get there. The Gmail contacts will magically reappear on your phone.
I've run this, and it's downgraded to 2.3.3. All steps seemed to work. But I can't run programs that require root. What have I missed?
Did you revolutionary?
If so,did you install recovery and flash superuser as described in the revolutionary info/faq?
__________________
The Delivery Guy
If someone has helped you,please click the THANKS button on that post.
Please post questions so others can benefit from the answers. donate to my device fund
I decided to repeat the entire process because I think I missed something somewhere.
Now, when I type in: adb shell /data/local/tacoroot.sh --setup
I get: ...rm failed for /data/data/recovery/log, no such file or directory
link failed No such file or directory
Are you s-off? You.should be if you ran revolutionary.
If you're s off you're making things unneccessarily hard on yourself.
Yes.
I have rooted Eris's and Droid X's and felt like I knew what I was doing. I am lost here. The first trip through all went as it should but I never saw anything about flashing SU.
I just HAD to make an account here to tell you how much I appreciate this! I'm very new to Android and I spent all day looking at different how-to's and yours was by far the easiest to understand. The first method worked perfectly for me and I can't thank you enough!
I just HAD to make an account here to tell you how much I appreciate this! I'm very new to Android and I spent all day looking at different how-to's and yours was by far the easiest to understand. The first method worked perfectly for me and I can't thank you enough!
So i was trying to root my phone or whatever so i can install a custom rom and i was following this guide because i had 6.01.605.05 and another guide on here said i had to downgrade before rooting
I got all the way to the end and was about to use revolutionary to install a recovery or whatever it was supposed to do, but then my phone started to bootloop and i followed the instructions to "flash the 0312 radio" but i get
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
HBOOT USB
IMAGE CRC
i havent done an HTCdev unlock, and someone told me to go ahead and try revolutionary but when i try it, it gives me "waiting for devices" i run it as an admin and ive ran it about 3 times, my tray icons say that my device is not recognized even though i know i have the drivers installed
i can follow the guide again but when i get to "adb devices" i cant continue because my device is not recognized even though i've reinstalled the drivers, does my phone need to be fully booted? because it wont fully boot since its stuck in a bootloop.
EDIT: my pc seems to pick up my phone when its in FASTBOOT USB but "adb devices" still wont find my device
Last edited by Blizzard158; October 6th, 2012 at 09:59 AM.
Thank you so much, revolutionary worked and i flashed the 0312 radio, but now, i wanted to do a nandroid backup so i downloaded ROM manager and i selected reboot into recovery and it said "An error occurred while attempting to run privileged commands" does this mean im not rooted? on my hboot screen, it said revolutionary at the top and s-Off
The Following User Says Thank You to Blizzard158 For This Useful Post:
We wouldn't be here if we didn't get a kick out of helping people. Congrats on your new phone! Now you get to choose a ROM. ICS or GB. Sense 3, Sense 4 or non-Sense. I'm running EclipticSense. Check the sticky for a huge list.
The Following User Says Thank You to bberryhill0 For This Useful Post:
Scotty,
Not sure where I have gone wrong.
I have redone the whole process 3x trying both versions listed (first and 2nd post).
No matter which i get stock here.
c:\miniadb_inc2>adb shell /data/local/tmp/misc_version -s 2.18.605.3
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up misc partition...
Error opening input file.
I did the unlock with htcdev first and that worked fine. I am using the CWM-SuperSU-v0.96.zip if that means anything.
Just cant get pass this.
So i installed MIUI v.1.12.30 and i absolutely love it, but it doesnt really answer calls right... so im going to hop around and try some different roms, are there any you guys would recommend that has as much customization as miui?
Scotty,
Not sure where I have gone wrong.
I have redone the whole process 3x trying both versions listed (first and 2nd post).
No matter which i get stock here.
c:\miniadb_inc2>adb shell /data/local/tmp/misc_version -s 2.18.605.3
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up misc partition...
Error opening input file.
I did the unlock with htcdev first and that worked fine. I am using the CWM-SuperSU-v0.96.zip if that means anything.
Just cant get pass this.
You have to undo (relock) the hTCdev unlock before you can get s-off.
Not sure if I did this correctly, but here is what I got.
c:\miniadb_inc2>adb shell Su
Su: permission denied
looks like you are not rooted. did you flash the superuser files in recovery?
you also do not want to enter adb shell and su in one command.
you want to: adb shell
if the prompt changes to a $>
then,enter: su
prompt should chage to a #>
and you may have to grant permissions on the phone screen,so have it awake and unlocked
your failure to open input file in the post above,could be from not haveing root access,or could be from an inaccessible sd card(mounted as a disk drive instead of charge only,sd not in the phone,or possibley bad)
you didnt say wich method you were following,but i assume youre following htcdev directions in post 2.
youll need to have a # before you the misc version will work.
no trouble at all! like bberry said,thats why were here sorry for the short replys,i was at work
glad you got it firgured out.
did misc_version push successfully to data/local/tmp?
are you in the "root" stage of taco root(i.e. does adb shell give you a # ?)
reboot the phone,start the process over,and then copy/paste the entire cmd window here and well see what we can see
Here's what i got. tried the adb shell, and it gave me a $ even after running the tacoroot command and it going into it's bootloop cycle.
Code:
C:\android>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\android>adb devices
List of devices attached
HT14DMA06456 device
C:\android>adb push tacoroot.sh /data/local/
346 KB/s (2129 bytes in 0.006s)
C:\android>adb shell chmod 755 /data/local/tacoroot.sh
C:\android>adb shell /data/locla/tacoroot.sh --setup
/data/locla/tacoroot.sh: not found
C:\android>adb shell /data/local/tacoroot.sh --setup
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the same tim
e, and reboot the system.
rm failed for /data/data/recovery/log, No such file or directory
C:\android>adb shell /data/local/tacoroot.sh --root
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
C:\android>adb push misc_version /data/local/tmp/misc_version
1109 KB/s (367096 bytes in 0.323s)
C:\android>adb shell chmod 777 /data/local/tmp/misc_version
error: closed
C:\android>adb shell /data/local/tacoroot.sh --undo
error: protocol fault (status 54 61 63 6f?!)
C:\android>adb kill-server
C:\android>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\android>adb devices
List of devices attached
C:\android>adb devices
List of devices attached
C:\android>adb devices
List of devices attached
HT14DMA06456 device
C:\android>adb shell chmod 777 /data/local/tmp/misc_version
Unable to chmod /data/local/tmp/misc_version: Operation not permitted
C:\android>adb shell
$ quit
quit
quit: permission denied
$ exit
dir
^C
C:\android>adb shell /data/local/tacoroot.sh --undo
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
rm failed for /data/data/recovery/log, No such file or directory
rm failed for /data/local.prop, No such file or directory
Root removed, rebooting
C:\android>
Here's what i got. tried the adb shell, and it gave me a $ even after running the tacoroot command and it going into it's bootloop cycle.
Code:
C:\android>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\android>adb devices
List of devices attached
HT14DMA06456 device
C:\android>adb push tacoroot.sh /data/local/
346 KB/s (2129 bytes in 0.006s)
C:\android>adb shell chmod 755 /data/local/tacoroot.sh
C:\android>adb shell /data/locla/tacoroot.sh --setup
/data/locla/tacoroot.sh: not found
C:\android>adb shell /data/local/tacoroot.sh --setup
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the same tim
e, and reboot the system.
rm failed for /data/data/recovery/log, No such file or directory
C:\android>adb shell /data/local/tacoroot.sh --root
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
C:\android>adb push misc_version /data/local/tmp/misc_version
1109 KB/s (367096 bytes in 0.323s)
C:\android>adb shell chmod 777 /data/local/tmp/misc_version
error: closed
C:\android>adb shell /data/local/tacoroot.sh --undo
error: protocol fault (status 54 61 63 6f?!)
C:\android>adb kill-server
C:\android>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\android>adb devices
List of devices attached
C:\android>adb devices
List of devices attached
C:\android>adb devices
List of devices attached
HT14DMA06456 device
C:\android>adb shell chmod 777 /data/local/tmp/misc_version
Unable to chmod /data/local/tmp/misc_version: Operation not permitted
C:\android>adb shell
$ quit
quit
quit: permission denied
$ exit
dir
^C
C:\android>adb shell /data/local/tacoroot.sh --undo
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
rm failed for /data/data/recovery/log, No such file or directory
rm failed for /data/local.prop, No such file or directory
Root removed, rebooting
C:\android>
was the phone still bootlooping when you enterd the adb shell command? i notice prior that you tried to undo the root. despite getting an error,if the phone rebooted, the root may have been allrerady undone.
also,looks like you did not try su at the $ prompt,so we dont know for sure if you had root access here or not,if the phone was still inthe bootloop root cycle.
as far as your closed error,could be from no root,did you reboot from the stock recovery as described?
make sure sd is mounted(charge only),and is present. make sure that no phone programs are running-htc sync,easy tether,pda net,etc.
was the phone still bootlooping when you enterd the adb shell command? i notice prior that you tried to undo the root. despite getting an error,if the phone rebooted, the root may have been allrerady undone.
also,looks like you did not try su at the $ prompt,so we dont know for sure if you had root access here or not,if the phone was still inthe bootloop root cycle.
as far as your closed error,could be from no root,did you reboot from the stock recovery as described?
make sure sd is mounted(charge only),and is present. make sure that no phone programs are running-htc sync,easy tether,pda net,etc.
ok so i went through and also made sure i didn't have htc sync on my computer or phone running (even made sure it was uninstalled)
it helped as i got a little farther.
but now i'm stuck at
Code:
C:\android>adb push misc_version /data/local/tmp/misc_version
2938 KB/s (367096 bytes in 0.122s)
C:\android>adb shell
^C
C:\android>adb shell
# su
su
su: not found
# ^C
C:\android>adb shell chmod 777 /data/local/tmp/misc_version
C:\android>adb shell /data/local/tmp/misc_version -s 2.18.605.3
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up misc partition...
it just sort of hangs there while the phone keeps rebooting
looks like you are not rooted. did you flash the superuser files in recovery?
you also do not want to enter adb shell and su in one command.
you want to: adb shell
if the prompt changes to a $>
then,enter: su
prompt should chage to a #>
and you may have to grant permissions on the phone screen,so have it awake and unlocked
your failure to open input file in the post above,could be from not haveing root access,or could be from an inaccessible sd card(mounted as a disk drive instead of charge only,sd not in the phone,or possibley bad)
you didnt say wich method you were following,but i assume youre following htcdev directions in post 2.
youll need to have a # before you the misc version will work.
Thanks Scotty and BB.
I have now joined the revolution thanks to you 2.
Now I guess it is time to pick a Rom, what do recommend?
i believe he thot you were further along in the process
Quote:
Originally Posted by skippybingo
Thanks Scotty and BB.
I have now joined the revolution thanks to you 2.
Now I guess it is time to pick a Rom, what do recommend?
awsome glad you got it figured out i personally would pick an AOSP ICS or JB rom even if its missing some minor functionality,but thats just me my inc 2 hasnt been my DD for a long time,so im pretty out of touch with available roms. bberry will be able to direct you there!
Quote:
Originally Posted by skarrd
got it to work past that point!
unmounted the sd card, formatted it through android and tried it again, worked beautifully c:
Does EclipticSense have themes? I use GO Launcher and Android Pro Widgets among other things.
Perhaps they are not themes, when you first boot into EclipticSense (setup) there are 4-5 choices you can choose from. I have tried 3, I cant tell the difference, but then again Im a noob......
I would like to know what they are all about, what the real diff are.
17Likes
Error opening input file?
