Develop Bugs

[GUIDE] Downgrade your Desire-Z from 1.72 to 1.34 (and get root and S-OFF)

First thanks to everybody who made it possible to root our great devices.
THIS WILL WIPE YOUR DEVICE, BACKUP EVERYTHING BEFORE DOING THIS!
Polish translation by trzype
If you don't know how to use adb/fastboot don't do this. Use the search function and google and learn how to use them. If you know everything about them come back. I made a pretty nice tutorial, many people used it already with success. But I won't add anything like "go to startmenu and type..."
If your INFOCID is NOT one of these you need to make a goldcard to downgrade!
HTC__001
HTC__032
HTC__E11
HTC__203
HTC__Y13
HTC__102
HTC__405
HTC__304
HTC__A07
HTC__N34
HTC__J15
check with:
Code:
adb reboot bootloader
fastboot oem boot
Here is a great guide how to make a goldcard, follow the first part and come back here then.
Get theses 3 files:
https://github.com/tmzt/g2root-kmod/raw/scotty2/scotty2/psneuter/psneuter (right click > save as...)
https://rapidshare.com/files/1884723844/PC10IMG.zip
https://rapidshare.com/files/948281832/root.zip
Since this uses some security holes to gain root privileges on your phone some antivirus programs on your pc might warn you that this contains a virus. Thats not the case!
MikeChannon said:
It might be worth saying in the thread that android/Exploit.ragecage.A is the exploit being used to gain root and Users should not worry about the warning some software will give.
Click to expand...
Click to collapse
Extract misc_version_01.zip (only misc_version is needed)
Get the PC10IMG.zip from here or download the full RUU from here.
If you already downloaded the 1.34 RUU somewhere else you can skip this step.
Code:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
Check if you have the '#' sign instead of the '$'
If you see the '#' sign you got root!
Code:
/data/local/tmp/misc_version -s 1.33.405.5
exit
If you have downloaded the 1.34.405.5_PC10IMG.zip copy it to you SD-Card and rename it to PC10IMG.zip.
If you downloaded the full RUU or had it already execute the exe file (mine is called RUU_Vision_HTC_WWE_1.34.405.5_Radio_12.28b.60.140e_26.03.02.26_M_release_155556_signed.exe), start explorer and type %temp% in the adress bar.
Look in all the folders starting with a { sign and also in the sub directories if it also starts with a { sign, in one of the subdirectories there should be a rom.zip file with 298.442.206 bytes and the MD5 sum 2ff42897cd27e0db425a2cf36c8bd078.
Copy this rom.zip to your SD-Card on the phone and rename it to PC10IMG.zip
Code:
adb reboot bootloader
(or turn your phone of and on again while holding the trackbad).
Wait till the phone is in bootloader mode (white screen should look like this but with other infos http://www.brutzelstube.de/wp-content/uploads/2010/09/hboot.jpg)
Select bootloader (vol +/- buttons for navigation and power button for select).
Wait for the phone to scan the sdcard, once it's done it will ask you if you want to start the update. Confirm it and wait till it's done. Reboot with powerbutton when asked.
After the reboot check for version informations, it should show this:
Enable USB-Debugging on your phone
Extract root.zip
Code:
adb install AndroidTerm.apk
adb push busybox /data/local/tmp/
adb push gfree /data/local/tmp/
adb push rage /data/local/tmp
adb push root /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/*
adb push su /sdcard/
adb push Superuser.apk /sdcard/
Start the Terminal app on your phone and type:
Code:
/data/local/tmp/rage
Wait until you see the message "Forked #### childs.", reset Terminal (menu > Reset Term). The Terminal app will close, launch it again. It will force close, launch it again.
You should see the magic '#' sign again.
Next type in the terminal
Code:
/data/local/tmp/gfree -f
, this will turn Security off (S-OFF), remove SIM Lock and set CID to 11111111.
Last step in terminal app on your phone is to execute these commands.
Code:
/data/local/tmp/root
sync
This will root your phone. It's possible that you get an error message "mkdir: /system/xbin already exists", don't worry everything should be ok.
After that restart your phone.
Now get ROM Manager and install the recovery image from there. If you are happy with the 1.34 software everything is done here, if not you can flash anything you want now.

Nice work! We allways need more people using the magic of root
Sent from my HTC Vision using XDA App

Thanks a lot for your effort!
Just bought a Desire Z and accidentally upgraded OTA.
Will try it now and report back.

I get the following Error when trying to run misc version
Code:
# /data/local/tmp/misc_version -s 1.33.405.5
/data/local/tmp/misc_version -s 1.33.405.5
--set_version set. VERSION will be changed to: 1.33.405.5
Patching and backing up partition 17...
Error opening backup file.
#
Any ideas mate?
Edit: Sorry, forgot to unmount phone from windows when i copied the img over.

VERY IMPORTANT
The OP made a small mistake in the instructions:
Code:
/data/local/tmp/misc[COLOR="Red"][B]-[/B][/COLOR]version -s 1.33.405.5
exit
the dash (-) should be an underline (_)
Code:
/data/local/tmp/misc[COLOR="Red"][B]_[/B][/COLOR]version -s 1.33.405.5
exit
Please update the first post

Darkyy said:
VERY IMPORTANT
The OP made a small mistake in the instructions:
Code:
/data/local/tmp/misc[COLOR="Red"][B]-[/B][/COLOR]version -s 1.33.405.5
exit
the dash (-) should be an underline (_)
Code:
/data/local/tmp/misc[COLOR="Red"][B]_[/B][/COLOR]version -s 1.33.405.5
exit
Please update the first post
Click to expand...
Click to collapse
Thanks, fixed it.

Question:
Should the psneuter -file be without a suffix?
Or should it be like psneuter.txt?

Gnurf said:
Question:
Should the psneuter -file be without a suffix?
Or should it be like psneuter.txt?
Click to expand...
Click to collapse
Without the extension... .txt is added by your browser presumably so you'll have to rename it

Another error:
When I reboot into the bootloader, the phone scans PC10IMG.ZIP and then says "CID incorrect! Update Fail! Press <POWER> to reboot."

paw3lk said:
Without the extension... .txt is added by your browser presumably so you'll have to rename it
Click to expand...
Click to collapse
Thats what I thought aswell, but seeing there has been a post about it previously... (in the other tread)
Thanks.

worked as described, big thx

waqypaqy said:
Another error:
When I reboot into the bootloader, the phone scans PC10IMG.ZIP and then says "CID incorrect! Update Fail! Press <POWER> to reboot."
Click to expand...
Click to collapse
What phone and software version do you have?
It seems like you use a wrong PC10IMG.zip for your phone. Did you download the zip from here or got it yourself from the full ruu?

Another error:
Step 15: Extract root.zip
and then do the commands:
Code:
adb chmod 0755 /data/local/tmp/*
should be
Code:
adb [B][COLOR="Red"]shell [/COLOR][/B]chmod 0755 /data/local/tmp/*

g4rb4g3 said:
What phone and software version do you have?
It seems like you use a wrong PC10IMG.zip for your phone. Did you download the zip from here or got it yourself from the full ruu?
Click to expand...
Click to collapse
I've got the Desire Z running 1.72. I first tried downloading the PC10IMG.zip from the 1st link in part 3 which didnt work. I then tried the RUU file, found the rom.zip in Temp, renamed it and copied it to SD card, which didnt work either
What am I doing wrong?
Software number: 1.72.161.1

Darkyy said:
Another error:
Step 15: Extract root.zip
and then do the commands:
Code:
adb chmod 0755 /data/local/tmp/*
should be
Code:
adb [B][COLOR="Red"]shell [/COLOR][/B]chmod 0755 /data/local/tmp/*
Click to expand...
Click to collapse
Thanks, fixed it.
Sent from my HTC Vision using XDA App

waqypaqy said:
I've got the Desire Z running 1.72. I first tried downloading the PC10IMG.zip from the 1st link in part 3 which didnt work. I then tried the RUU file, found the rom.zip in Temp, renamed it and copied it to SD card, which didnt work either
What am I doing wrong?
Software number: 1.72.161.1
Click to expand...
Click to collapse
Did you root your phone before the ota update?
Sent from my HTC Vision using XDA App

g4rb4g3 said:
Did you root your phone before the ota update?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Yes I had rooted it with Visionary before I updated it. Please tell me I still have some hope for getting root back

waqypaqy said:
Yes I had rooted it with Visionary before I updated it. Please tell me I still have some hope for getting root back
Click to expand...
Click to collapse
Did you set s-off too while rooting?
Sent from my HTC Vision using XDA App

g4rb4g3 said:
Did you set s-off too while rooting?
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Nope Im screwed arent I?

waqypaqy said:
Nope Im screwed arent I?
Click to expand...
Click to collapse
adb reboot bootloader
fastboot oem boot
Post the result of the 2nd command (dont know if it works... but it wont harm anything)
Sent from my HTC Vision using XDA App

[Solved] Got problem when type adb command to root Desire Z

I used this two guides when trying to root my Desire Z
first installed Android_SDK
http://wiki.cyanogenmod.com/index.php?title=Howto:_Install_the_Android_SDK
and it works perfect, I can run command adb devices and my device is shown there.
the problem appear when I followed the second guide to downgrade the ROM
http://wiki.cyanogenmod.com/index.php?title=HTC_Desire_Z:_Rooting#Downgrade_to_1.34.707.3
under that guide, there is some command must be done:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
Click to expand...
Click to collapse
and when I tried to run "adb push psneuter /data/local/tmp" the command prompt replay "cannot stat 'psneuter': No such file directory"
I already put the "psneuter" in same folder (platform-tools) with adb.exe on directory C: android-sdk-windows.
Anyone has the experience or familiar with this problem? please help
I already search the same problem on google, and find some user has the problem too, but still there is no solution or I already did and useless

Try to cd into the directory that contains adb.exe

Make sure you are in that directory of adb.exe
Example how mine is
cd C:
C: cd android-sdk-windows
C:/android-sdk-windows/> cd platform-tools
C:/android-sdk-windows/platform-toold/>
Then from there do adb comman
C:/android-sdk-windows/platform-tools/>adb push psneutor /data/local/tmp
And so forth and it should go through fine
If you setup sdk in enirovemnt where can run adb anywhere then there less and simple way
All you would have to do is adb push (drag the file into cmd window) /data/local/tmp

theSpam said:
Try to cd into the directory that contains adb.exe
Click to expand...
Click to collapse
ilostchild said:
Make sure you are in that directory of adb.exe
Example how mine is
cd C:
C: cd android-sdk-windows
C:/android-sdk-windows/> cd platform-tools
C:/android-sdk-windows/platform-toold/>
Then from there do adb comman
C:/android-sdk-windows/platform-tools/>adb push psneutor /data/local/tmp
And so forth and it should go through fine
If you setup sdk in enirovemnt where can run adb anywhere then there less and simple way
All you would have to do is adb push (drag the file into cmd window) /data/local/tmp
Click to expand...
Click to collapse
thanks bro, work when I drag the file to cmd
but stuck again when I follow step 7 & 8
7. On the computer, open terminal and run the following command:
adb reboot bootloader
8. Follow the on screen directions, on the HTC Desire Z, on flashing the 1.34.707.3 firmware.
Click to expand...
Click to collapse
can I also ask this question in this thread? or is there anybody have a free time to guide me

after you do those steps in command type adb reboot bootloader once again make sure your in the adb.exe directory
from there phone should reboot int bootloader (white screen) and it will do a check for the PCIMG after it will ask if you want to install update Vol for yes and VOl for no

ilostchild said:
after you do those steps in command type adb reboot bootloader once again make sure your in the adb.exe directory
from there phone should reboot int bootloader (white screen) and it will do a check for the PCIMG after it will ask if you want to install update Vol for yes and VOl for no
Click to expand...
Click to collapse
step 7 work fine, but phone only show bootloader and didn't ask to install update..
maybe stupid question but should i need to run RUU on my computer first after type adb reboot bootloader?

measn you dont have the PCIMG on sdcard
On the computer, open terminal and run the following commands:
adb push psneuter /data/local/tmp
adb push misc_version /data/local/tmp
adb shell chmod 777 /data/local/tmp/psneuter
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/psneuter
adb shell
NOTE: You should have the "#" sign instead of the "$". If you do, you have temporary root, and can continue on.
/data/local/tmp/misc_version -s 1.33.405.5
exit
Copy the 1.34.707.3 firmware to the root of the SD card (NOT in any folders).
On the computer, open terminal and run the following command:
adb reboot bootloader
Follow the on screen directions, on the HTC Desire Z, on flashing the 1.34.707.3 firmware.
Once finished you can can continue to the next section.
Click to expand...
Click to collapse

Ok I got it, it because I copy the RUU on the sd card instead PCIMG.zip, my bad.
another question bro, how to backup my current build (1.82.707.1)? if i downgrade to 1.34.707.3, is not the current build will be replaced?

Vader™ said:
Ok I got it, it because I copy the RUU on the sd card instead PCIMG.zip, my bad.
another question bro, how to backup my current build (1.82.707.1)? if i downgrade to 1.34.707.3, is not the current build will be replaced?
Click to expand...
Click to collapse
need custom recovery to back up current rom sorry

ilostchild said:
need custom recovery to back up current rom sorry
Click to expand...
Click to collapse
is there anyway to do custom recovery without downgrade?
anyway thanks very much for helping me bro, really appreciate it.

umm not that i know of really if you can gain temp root you can back up your apps and all with titanium, but you want a full nandroid your gonna need a custom recovery, and the way your going allows you to downgrade to achive root and custom recovery

ilostchild said:
umm not that i know of really if you can gain temp root you can back up your apps and all with titanium, but you want a full nandroid your gonna need a custom recovery, and the way your going allows you to downgrade to achive root and custom recovery
Click to expand...
Click to collapse
I see, thanks again bro.

[GUIDE] Mac users guide to the Automated Root

I couldn't reply to the [ROOT][EG30/31] Automated root of your existing stock ROM (w/o ODIN or ROM Flash)
post in the dev forums because I'm a noob, so I figured I'd post it here.
The OP's Mac instructions were a bit vague for noobs like me, but I figured it out, hope it helps others.
1. Download the eg30auto.zip listed in step 1 of the original post. Unzip it.
2. Follow step 2 in the original post for hooking up your phone
3. Download the platform tools here and unzip
4. Copy the adb file from the platform tools folder, to your eg30auto folder
5. Open a Terminal, cd to the eg30auto folder
6. Use these commands to open an adb shell, copy the needed files:
./adb shell
./adb push copy2tmp /data/local/tmp/
./adb push copy2sd /sdcard/
Click to expand...
Click to collapse
7. Run the exploit (do not type the $ symbols)
$ cd /data/local/tmp
$ /system/bin/sh install-zerg.sh
Click to expand...
Click to collapse
8. The previous step will take a few minutes. Assuming it is successful, it will kick you out of "adb shell". Restart "adb shell"
./adb shell
Click to expand...
Click to collapse
9. Your adb shell should now have the # prompt indicating temporary root. Proceed to install persistent root and cleanup the temp rooting files, followed by rebooting the phone (do not type the # symbols)
# cd /sdcard/000root
# /system/bin/sh install-root.sh
# /system/bin/sh install-cleanup.sh
# reboot
Click to expand...
Click to collapse
If you get an error during the install, consult the original post. Otherwise, you should be rooted now! Mad props to the hardworking devs that blessed us with this early christmas gift!

[Acer _AV041_A100_1.037.00_ww_gen1] root？

[Acer _AV041_A100_1.037.00_ww_gen1]
root
Can be successfully？？？

alexsec said:
[Acer _AV041_A100_1.037.00_ww_gen1]
root
Can be successfully？？？
Click to expand...
Click to collapse
ZN's method still works just fine.
http://forum.xda-developers.com/showthread.php?t=1531646

i can't root!
i can't root!

Verify the device is showing under the device manager, usb debugging is turned on, and that it is being run as administrator.
What OS are you using?

i have the same problem. Can't root after the recent update. using W7, executing it with and without administrator rights. Executing with administrator rights it says something of ADB.

alexsec said:
i can't root!
Click to expand...
Click to collapse
Updating script. Try once again.

rooted!! thanks!!

How to Updating script. Try once again.

@ ZeroNull, can you confirm whether ICS_rooting_A10x_A5xx works for the latest build?
Build number
Acer_A100_2.001.01_COM_GEN2
I have been unsuccessful so far:
==========================================
Preparation is finished.
-
Executing of the main script.
remote object '/system/bin/su' does not exist
The file "su" isn't created!
-
Not getting root!
-
Error!

I can confirm that I successfully rooted my A100 using ZeroNull's simple method (http://forum.xda-developers.com/showthread.php?t=1531646)
Build number: Acer_AV041_A100_1.037.00_WW_GEN1
I didn't even use the new script, I'm still using the old one (ICS_rooting.zip)
Unfortunately I can also confirm problems with recent updates of the SuperUser APK (It did not assign the correct Group ID), but apparently they were fixed in the latest update (v3.1.3)
Good Luck.
---------- Post added at 10:30 AM ---------- Previous post was at 10:05 AM ----------
alexsec said:
i can't root!
Click to expand...
Click to collapse
alexsec said:
How to Updating script. Try once again.
Click to expand...
Click to collapse
Hi alexsec, did you try with the new script, it creates a different directory than the old script did, and it uses the mkdir -p option so it creates any parent directories it needs:
Code:
adb shell "mkdir -p /data/local/tmp"
adb push tools /data/local/tmp
adb shell "chmod 0755 /data/local/tmp/mempodroid"
And it does a better job by waiting longer for the tablet to reboot:
Code:
rem Wait reboot tablet
for /L %%i in (1,1,7000000) do @rem
I even modify the getroot.sh script just to change back to the old su command and modify its permissions:
Code:
cd /data/local/tmp
echo >/data/local.prop
toolbox mount -o remount, rw /system/
cat su >/system/bin/su
ln -s /system/bin/su /system/xbin/su
chmod 06755 /system/bin/su
sync ; sync ; sync
reboot
Good Luck...

[UPDATED] Get s-off and root for 6.01.605.05 software

Update: Found better instructions here and updated this post with them: http://rootzwiki.com/topic/27003-root-dinc2-on-any-firmware-may-want-to-sticky-later/
Be warned that this has been reported to cause bootloops on Sense ROMs, proceed at your own risk.
A few disclaimers before I begin:
1) I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. ANYTHING YOU ATTEMPT TO DO YOU DO AT YOUR OWN RISK
2) This method requires use of adb and is not for thr faint of heart. your phone WILL be bootlooping along the way; this is exactly what we want (at a specific point)
Now to begin in earnest
First find what we need!
We need the patched misc version, tacoroot, and the earlier GB RUU
Modified htc drivers or linux, both with working adb installation
disable fastboot on your device
A few disclaimers before I begin:
1) I AM NOT RESPONSIBLE FOR ANYTHING YOU DO TO YOUR PHONE. ANYTHING YOU ATTEMPT TO DO YOU DO AT YOUR OWN RISK
2) This method requires use of adb and is not for thr faint of heart. your phone WILL be bootlooping along the way; this is exactly what we want (at a specific point)
Now to begin in earnest
First find what we need!
We need the patched misc version, tacoroot, and the earlier GB RUU
Modified htc drivers or linux, both with working adb installation
disable fastboot on your device
Now we push, make executable, and execute the tacoroot method
adb push tacoroot.sh /data/local/
adb shell chmod 755 /data/local/tacoroot.sh
adb shell /data/local/tacoroot.sh
At this point we will run tacoroot with the --recovery, (push volume up and power at the triangle) (reboot after this) --setup and --root (run one, wait for the device to settle then run the next)
AT THIS POINT YOUR DEVICEWILL BE BOOTLOOPING; THAT IS PERFECTLY NORMAL
Now we downgrade the misc_version
adb push misc_version /data/local
adb shell chmod 777 /data/local/misc_version
adb shell /data/local/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
If everything so far has succeeded, youre almost there!
adb reboot bootloader
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip <your RUU>
fastboot reboot
If everything so far has succeeded, youre almost there!
adb reboot bootloader
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip <your RUU>
fastboot reboot
Click to expand...
Click to collapse
Tacoroot: https://github.com/CunningLogic/TacoRoot
misc_version: https://github.com/downloads/hyuh/misc_version_universal/misc_version_universal.zip
2.3.3 RUU: http://jellybellys.minus.com/mvivow/2

prototype7 said:
All credit goes to jcase on the RootzWiki forums, I can't try this out myself but I thought I'd share it for those who could use it:
Here are my instructions to preform this. If you do pack this in a script/program , please follow the license that comes with Tacoroot and misc_version
Download https://github.com/d...n_universal.zip
and unzip it
Preform manual tacoroot exploit
adb reboot recovery
(Reboot normally once in recovery, this creates the directory for the log. Continue once booted)
adb shell
rm /data/data/recovery/*
ln -s /data/local.prop /data/data/recovery/log
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
exit
adb reboot
(Device will appear to bootloop, but ADB will work, continue once adb is working)
adb push misc_version /data/local/
adb shell
chmod 755 /data/local/misc_version
/data/local/misc_version --set_version 1.11.605.11
rm /data/data/recovery/log
echo 'ro.kernel.qemu=0' > /data/local.prop
adb reboot
Now you can flash the proper ruu to s-off with
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
I'm going to try this when I get home hopefully I can FINALLY get downgraded...
Sent from my ADR6350 using XDA

Jayydude_SGP said:
I'm going to try this when I get home hopefully I can FINALLY get downgraded...
Sent from my ADR6350 using XDA
Click to expand...
Click to collapse
Let me know how it works .
Sent from my Incredible 2 using Tapatalk 2 Beta-5

I'm just a little unclear about what comes before and after this...
Can we get a post that has ALL the code/instructions spelled out? For instance, the "Preform manual tacoroot exploit"... is that the tacoroot code from before in its entirety, or just a certain part of it?
And then when the instructions in this post are done, are we to then follow the downgrade instructions from beginning to end?
Sorry to be pesty, but really want this to work and I'm just unsure of what all to do. Many many super thanks.

tcwota said:
I'm just a little unclear about what comes before and after this...
Can we get a post that has ALL the code/instructions spelled out? For instance, the "Preform manual tacoroot exploit"... is that the tacoroot code from before in its entirety, or just a certain part of it?
And then when the instructions in this post are done, are we to then follow the downgrade instructions from beginning to end?
Sorry to be pesty, but really want this to work and I'm just unsure of what all to do. Many many super thanks.
Click to expand...
Click to collapse
After you do this, use an RUU to downgrade and then use revolutionary to obtain s-off. I'll look into the tacoroot in a minute, like I said these aren't my instructions.
Edit: Nothing like a quick google search to make you feel like an idiot lol. The adb commands are the manual tacoroot exploit. I'll update the OP to make it more clear.
Sent from my Incredible 2 using Tapatalk 2 Beta-5

OP updated. Make sure to post and tell me if this works.

Thanks, but still unclear about one thing. To flash the RUU, do we follow all the instructions in the downgrade vivow .98 thread?

You have to combine all the instructions.
If you go to the rootzwiki page I spelled it out. Just can't link to external sites because I'm new to xda.

Perfect. Thanks and can't wait to give this a try in the morning.
Do you (or anyone) think it will matter that I have already (successfully) used the HTCDev boot unlocker?
aaronc222 said:
You have to combine all the instructions.
If you go to the rootzwiki page I spelled it out. Just can't link to external sites because I'm new to xda.
Click to expand...
Click to collapse

It took some tinkering (and a bit of sweating), but I was able to get this to work successfully.
I had previously used the HTCdev tool to unlock and was running clockwork recovery. I had to flash the stock recovery and do a factory restore, but still got a "99 unknown fail" when trying to flash the RUU at the end of this process.
A quick google search told me to relock the bootloader with "fastboot oem lock." After the relock, I had to do ANOTHER factory restore and then everything worked fine.
One difference for me: the bootloop started earlier, ie after "adb shell /data/local/tacoroot.sh --root". But I just continued to use adb when I could and got through it.
About to run Revolutionary. Thanks to everyone up to this point! Such a fantastic community!

not to rain on your parade but this makes no sense. after the adb reboot recovery..... i do the adb shell and then it cant find the file/directory

dets34 said:
not to rain on your parade but this makes no sense. after the adb reboot recovery..... i do the adb shell and then it cant find the file/directory
Click to expand...
Click to collapse
Are you rebooting out of the recovery? You do "adb reboot recovery," and then when you get to the red triangle, hold down volume up AND volume down and then the power button, reboot, let the phone reboot back into normal, and then continue the instructions.

unstuck! ... then stuck again
Trying this on a warranty replacement Dinc2 that's got Android 2.3.4, Software number 6.01.605.05 710RD ... the above post got me past the red triangle "!" thing, so I proceeded to:
Code:
adb shell
rm /data/data/recovery/*
ln -s /data/local.prop /data/data/recovery/log
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
and got:
Code:
$ echo 'ro.kernel.qemu=1' > /data/local.prop
cannot create /data/local.prop: permission denied
Is it significant that I'm seeing a "$" prompt instead of a "#"? or is that later in the process? Is it significant that, after the sym-linking of /data/local.prop to the log file and then rebooting, my phone had no signal and seemed pretty inoperable, but then after the write to /data/local.prop failed (and I sat googling around for a bit) the phone rebooted itself (no adb commands, and I didn't even breath in its direction) and came back to having signal and my settings, etc. and full operability?
Any help appreciated - I'll come back to this tomorrow ...

jehosephat said:
Trying this on a warranty replacement Dinc2 that's got Android 2.3.4, Software number 6.01.605.05 710RD ... the above post got me past the red triangle "!" thing, so I proceeded to:
Code:
adb shell
rm /data/data/recovery/*
ln -s /data/local.prop /data/data/recovery/log
exit
adb reboot
adb shell
echo 'ro.kernel.qemu=1' > /data/local.prop
and got:
Code:
$ echo 'ro.kernel.qemu=1' > /data/local.prop
cannot create /data/local.prop: permission denied
Is it significant that I'm seeing a "$" prompt instead of a "#"? or is that later in the process? Is it significant that, after the sym-linking of /data/local.prop to the log file and then rebooting, my phone had no signal and seemed pretty inoperable, but then after the write to /data/local.prop failed (and I sat googling around for a bit) the phone rebooted itself (no adb commands, and I didn't even breath in its direction) and came back to having signal and my settings, etc. and full operability?
Any help appreciated - I'll come back to this tomorrow ...
Click to expand...
Click to collapse
I'm in the same situation, any idea's yet? I wonder if I should htcdev unlock just to have root privilages

Here's a better guide for it, I'll update the OP in a minute: http://rootzwiki.com/topic/27003-root-dinc2-on-any-firmware-may-want-to-sticky-later/
Edit: OP updated.

prototype7 said:
Here's a better guide for it, I'll update the OP in a minute: http://rootzwiki.com/topic/27003-root-dinc2-on-any-firmware-may-want-to-sticky-later/
Edit: OP updated.
Click to expand...
Click to collapse
Thanks a lot, quick question though, will this send my phone into a continuous bootloop if I don't run aosp?
Sent from my ADR6425LVW using Tapatalk 2

prototype7 said:
Here's a better guide for it, I'll update the OP in a minute: http://rootzwiki.com/topic/27003-root-dinc2-on-any-firmware-may-want-to-sticky-later/
Edit: OP updated.
Click to expand...
Click to collapse
Trying this now. Hopefully it fixes the
Code:
cannot create /data/local.prop: permission denied
errors other people and myself are seeing.
---------- Post added at 02:46 PM ---------- Previous post was at 02:03 PM ----------
worked until i ran the tacoroot.sh --root command. Didn't root my phone and left me hanging at
Code:
adb shell chmod 777 /data/local/misc_version
adb shell /data/local/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
after --root this is what i received.
Code:
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:\Program Files (x86)\Android\android-sdk\platforms>abd shell chmod 777 /data/l
ocal/misc_version
'abd' is not recognized as an internal or external command,
operable program or batch file.
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell chmod 777 /data/l
ocal/misc_version
Unable to chmod /data/local/misc_version: No such file or directory
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell /data/local/sh -c
'/data/local/tmp/misc_version -s 2.18.605.3'
/data/local/sh: not found
C:\Program Files (x86)\Android\android-sdk\platforms>

dets34 said:
Trying this now. Hopefully it fixes the
Code:
cannot create /data/local.prop: permission denied
errors other people and myself are seeing.
---------- Post added at 02:46 PM ---------- Previous post was at 02:03 PM ----------
worked until i ran the tacoroot.sh --root command. Didn't root my phone and left me hanging at
Code:
adb shell chmod 777 /data/local/misc_version
adb shell /data/local/sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
after --root this is what i received.
Code:
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:\Program Files (x86)\Android\android-sdk\platforms>abd shell chmod 777 /data/l
ocal/misc_version
'abd' is not recognized as an internal or external command,
operable program or batch file.
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell chmod 777 /data/l
ocal/misc_version
Unable to chmod /data/local/misc_version: No such file or directory
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell /data/local/sh -c
'/data/local/tmp/misc_version -s 2.18.605.3'
/data/local/sh: not found
C:\Program Files (x86)\Android\android-sdk\platforms>
Click to expand...
Click to collapse
Interesting. Looking over the code and tacoroot.sh, nothing actually puts the misc_version where it needs to be lol. Updated the instructions and added "adb push misc_version /data/local" before "adb shell chmod...", try that.

yeah i was just going to say looks like a the push misc_version was missing which solved everything for me.
as for others with this problem if the push misc_version doesn't seem to help i'd take a loot at this post here http://forum.xda-developers.com/showthread.php?t=1526316 for manually changing the version.
s-offffffed

dets34 said:
yeah i was just going to say looks like a the push misc_version was missing which solved everything for me.
as for others with this problem if the push misc_version doesn't seem to help i'd take a loot at this post here http://forum.xda-developers.com/showthread.php?t=1526316 for manually changing the version.
s-offffffed
Click to expand...
Click to collapse
So it worked?