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

[Q] Desire Z with 2.42.405.2 Able to downgrade? ( i'm able to temproot )

Hi all
I have a European HTC Desire Z with this info:
Android 2.3.3
Sense 2.1
Build 2.42.495.2
Vision PVT Ship S-ON
Hboot-0.85.0013
MicroP-0425
Radio 26.10.04.03_M
eMMC-boot
Apr 11 2011,23:36:27
I am able to temproot this phone with the method provided here:
http://forum.xda-developers.com/showpost.php?p=15851661&postcount=1
using the code:
Code:
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
However the downgrading part fails on me.
After entering the bootloader menu is scans the SDCARD and finds the PC10IMG.zip
telling me: loading...[PC10IMG.zip], after that it's saying: Checking..[PC10IMG.zip].
After checking it just goes back to the Menu without asking me to update etc.
I did however changed the misc_version and followed the guide precisely.
I searched and found some Threads saying this version isn't rootable yet. though they were couple months old, and I am able to get temp root. it should be do-able right?
Can someone please confirm this and tell me how to, or what i'm doing wrong and let this baby free.

I followed the guide to the letter, without changing misc_version or anything, and I managed to downgrade and root without problems on first try. Same version as you, Desire Z bought in Poland.
Just be sure to grab the file for Desire Z and not for T-Mobile G2 and it should work

costipl said:
Just be sure to grab the file for Desire Z and not for T-Mobile G2 and it should work
Click to expand...
Click to collapse
What file are you referring to here?
Also, how is it possible to downgrade without changing the misc_version, i thought it was all about changing that in order to make it work haha.

Sorry, I think I misunderstood your post...
I did this to change misc_version:
Code:
$ adb push misc_version /data/local/tmp/misc_version
$ adb shell chmod 777 /data/local/tmp/misc_version
$ adb shell
# /data/local/tmp/misc_version -s 1.00.000.0
I assumed you changed the "1.00.000.0" to something else (while browsing the forum I found in some threads that people used a different value on DZ).
As for the file I was referring to, I meant the stock rom image - 1.34.405.5_PC10IMG.zip
Maybe you grabbed the file "PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09 b_26.02.01.15_M2_release_149459_signed.zip", which is for G2?
Other than that, I'm not familiar enough with the bootloader to be of any help.

costipl said:
Sorry, I think I misunderstood your post...
I did this to change misc_version:
Code:
$ adb push misc_version /data/local/tmp/misc_version
$ adb shell chmod 777 /data/local/tmp/misc_version
$ adb shell
# /data/local/tmp/misc_version -s 1.00.000.0
I assumed you changed the "1.00.000.0" to something else (while browsing the forum I found in some threads that people used a different value on DZ).
As for the file I was referring to, I meant the stock rom image - 1.34.405.5_PC10IMG.zip
Maybe you grabbed the file "PC10IMG_Vision_TMOUS_1.19.531.1_Radio_12.21.60.09 b_26.02.01.15_M2_release_149459_signed.zip", which is for G2?
Other than that, I'm not familiar enough with the bootloader to be of any help.
Click to expand...
Click to collapse
I redownloaded the zip file and you just made my day i had a other zip from another thread. but with the exact same name.. maybe corrupted ? THANKS!

Radio's get flashed AFTER you flash your ROM, not before ;P
Remember to rename your PC10IMG.zip to something else after you're done rooting/installing a new ROM, cos if anything happens and your phone crashes and you need to enter recovery, having PC10IMG.zip on the root of your SD will ensure that you never get into recovery
Power + Vol Down boots into bootloader, and it automatically scans for updates, PC10IMG.zip being one of them. Only when there are no update files on SD root will it give you a choice of booting into Recovery to well, recover your phone

[Q] Problems downgrading/rooting Desire Z Gingerbread.

Hello everyone!
Not my phone, just helping a friend
We got problems downgrading from Gingerbread to earlier version of Android.
So, wanted to root, flash custom recovery, then MIUI.
Started with this tut, then understood, that Gingerbread isn't rootable and it needs to be downgraded.
So, tried [GUIDE] Downgrade G2 (2.3.X) & DZ (2.3.X) & mT4g (2.3.4) & DHD w/ S-ON to Stock Froyo and HTC Desire Z: Firmware Downgrade (Gingerbread).
So, installed JRE, JDK, SDK (ADB), drivers.
With phone plugged to PC (USB Debuggind ON), ADB & Device manager sees it.
So, moved files to C:\android-sdk\platform-tools and ran cmd (administrator privileges). Till "adb shell it's good". But, after that, when ran chmod, it says, that permissions denied.
Question:
What we're doing wrong and how to fix it?
We've read so many guides, but unsuccessfully so far..
Device HTC Desire Z
Android 2.3.3
Kernel version 2.6.35.10-g7b95729
Baseband 12.56.60.25U_26.10.04.03_M
Build 2.42.405.2 CL84109
Thanks about helping!

Is it permission denied when u try to change the version? If permission denied during change the version, run this command:
cd /data/local/tmp/misc_version
chmod 777 misc_version
./misc_version -s 1.00.000.0
sync
Sent from my HTC Vision using XDA App

Are you sure your temp root is working?

aDeQ666, no, it wont chmod when typing chmod 777 /data/local/tmp/fre3vo, so - no temp root for us. Tried visionary, z4root, SuperOneClick - nothing works
It was updated from Froyo to Gingerbread via OTA, i think that's the issue? What else we can do? Thanks!

Could you post a copy/pastebin of your cmd when running it? It'll be much easier to spot the error if we can see exactly what you did/are doing.
-Nipqer

I have one problem when i tried to root htc desire. i already done the downgrade and now i am want to root... i folllowed the instructions on the link you gave untill this
[chmod 755 /data/local/tmp/*
/data/local/tmp/psneuter
NOTE: You will drop out of the shell after this command. Restart the shell using:
adb shell
cd /data/local/tmp
./busybox md5sum /dev/block/mmcblk0p18]
well after command:
chmod 755 /data/local/tmp/*
/data/local/tmp/psneuter
i`m not dropping out of the shell and the next instruction results with a "cd: bad substitution" msg. what should i do?
sorry for my bad english

When do u received the error? Is it when u downgrading or try to root? Are u using the wiki guide?

What I've down a few times now (and this does work) is use the fre3vo guide (the one you linked) to downgrade then continue with the guide below from step 14 or 15 to gain perm root.
http://forum.xda-developers.com/showthread.php?t=905261
Hope that helps.
Edit: You're better off flashing 1.34.405.5 as the one on the CM wiki may not be working. Its worth a shot IMO.

aDeQ666 said:
Is it permission denied when u try to change the version? If permission denied during change the version, run this command:
cd /data/local/tmp/misc_version
chmod 777 misc_version
./misc_version -s 1.00.000.0
sync
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
Hi, i have been trying to change my misc version but it gives me permission denied and i have # (root) already. So i tried chmod after cd which didn't have a problem but now when i try harder./misc_version it says the file not found.
Please help

I used this guide. it worked fine for me =)
http://forum.xda-developers.com/showthread.php?t=905261
*faceslapps self* sorry. I was a tad too fast. I didn't see that someone allready posted that guide here.

This is the command that i use before this:
adb push misc_version /data/local/tmp/misc_version
cd /data/local/tmp/misc_version
chmod 777 misc_version
./misc_version -s 1.00.000.0
sync
Sent from my HTC Desire Z using XDA App

I used this guide when I had to go through the pain of downgrading my desire z http://forum.xda-developers.com/showthread.php?p=15851843 . It worked very easily, just follow the instructions nice and carefully, the problem is that you need ADB set up for you to use that guide though.
Once you downgrade though, I would use the guide here for rooting your phone http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2 .
I hope that helps, that's what I used for my phone.
To be more precise in regards to the problem though, i just realised that i had the same problem as you when i was trying to run the chmod command where i had temproot but i kept getting "permission denied". As it turned out, i had accidentally written "adb push fre3vo /data/local/tmp/" instead of "adb push fre3vo /data/local/tmp" when i was following that downgrading guide. Basically what my mistake did was, it pushed fre3vo into a new folder within /tmp instead of just placing fre3vo in /tmp. So what you can do to figure out where fre3vo is, navigate to the /tmp folder using CD (in adb shell) and once you get to /tmp, type "ls". This will then display all the contents of /tmp and then you will be able to see if you accidentally created a folder like i did. Then once you check that, when you go to run the chmod command, you have to run it like "chmod 777 /data/local/tmp/**possible accidental folder name**/fre3vo", see if that works now .

Use this guide should do the job for you www.desirez.strawmetal.com

aDeQ666 said:
This is the command that i use before this:
adb push misc_version /data/local/tmp/misc_version
cd /data/local/tmp/misc_version
chmod 777 misc_version
./misc_version -s 1.00.000.0
sync
Sent from my HTC Desire Z using XDA App
Click to expand...
Click to collapse
were you able to fix this problem?

I had the same problem with my Desire Z with OTA 2.3.3.
Finally I've unlocked bootloader as show at htcdev.com.
Then I used this guide http://forum.xda-developers.com/showthread.php?t=1453066 (great thx for it), and CM 7.1 works like a charm.
All best.

allendon said:
were you able to fix this problem?
Click to expand...
Click to collapse
For my case, yes.
Sent from my HTC Vision using XDA App

[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?

Problems downgrading/rooting - fre3vo not being found?

I'm trying to root my Bell HTC Desire Z and I'm getting stuck pretty early just trying to downgrade to Froyo.
No matter what guide I've followed this is far as I'll get typing in the terminal:
adb push fre3vo /data/local/tmp
adb push misc_version /data/local/tmp
adb shell
chmod 777 /data/local/tmp/fre3vo
I'll then get a response saying unable to chmod /data/local/tmp/fre3vo: no such file or directory.
I've placed the fre3vo file in the same folder as adb so I'm super confused.
Any help would be super appreciated!

edit you first post and change the title of the post... it will change the title of the thread's name too

Now, I'm making even less progress.
adb push fre3vo /data/local/tmp
turns back with:
cannot stat 'fre3vo': No such file or directory

That error means fre3vo is not in the directory cmd/terminal is pointed at.
You need to either use the 'cd' command (change dir) or, if you're on windows, you can hold shift and right click in the dir fre3vo is, and select 'open cmd here'
-Nipqer

Alright, so I'm having slightly more luck following this guide http://forum.xda-developers.com/showthread.php?t=1178912&highlight=root+bell+desire+z
I've got to the portion about "Changing Version Number to Allow Downgrade and Gaining SuperCID with a Goldcard" but when I type:
# cd /data/local/tmp
I get cd /data/local/tmp: not found
I thought I was making progress...
EDIT: Never mind - I just decided to re-type the command in and it worked...moving on to downgrading

Success! Rooted my phone and flashed CM 7.2. Big thanks to Nipqer on #G2Root!!!!
Mods this thread could probably be deleted.

I am stuck on the same spot the OP was. I have done as nipqer suggested and opened a cmd window directly in the platform-tools folder and now the response coming back is
Code:
C:\platform-tools>adb shell
$ chmod 777/data/local/tmp/fre3vo
chmod 777/data/local/tmp/fre3vo
Usage: chmod <MODE> <FILE>
$ /data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
/data/local/tmp/fre3vo: permission denied
suggestions ?
I have read a lot of threads and tutorials on this and honestly there's so many it has become confusing. Help a fella out! :good:

follow this guide first
http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Firmware_Downgrade_(Gingerbread)
now go to this guide when complete
http://wiki.cyanogenmod.com/wiki/TMobile_G2:_Rooting
dont skip steps and if you need more help log onto freenode

You ran the chmod command wrong, didn't put a space between the 777 and the /data/local/tmp/fre3vo
-Nipqer

righto, thanks guys, will take a look at the threads you linked and try again. will post back one way or the other as soon as I have something.

ok I have run into a real problem. it looks as if I have semi bricked. I skipped nothing, followed the guide to a T.
Code:
NOTE: Take note of this number, we will need it later. For the remainder of this guide, we will refer to this number md5 #3.
If md5 #1 & md5 #3 match, then gfree 0.7 failed to powercycle the eMMC chip on the device. Either the software version is too high and the device was not downgraded per the previous section, or you did something wrong. Try again or join #G2Root on Freenode for further help..
If md5 #2 & md5 #3 match, then everything should be fine and you continue on.
Code:
md5 #1 - b532ca54a073f0c4043bd7be69ebce8d
md5#2 - 2ce1bdd5e4c1119ccfcecb938710d742
md5#3 - 2ce1bdd5e4c1119ccfcecb938710d742
as you can see they match so reboot command should have been fine but all O get now is hanging at the HTC screen, unless I reboot holding the volume down button then that takes me to hboot screen. What do I do?
UPDATE - As I worked out how to use clockwork I realized I had s-off so I downloaded CM7 and followed the instructions on wiping cache and what not then installed. All seems to be working now.
Thank you.

for future reference these is very common when switching hboots (part of the rooting process) you will not be able to boot into your previous rom as partition checks will have changed. when you have completed rooting you should either boot into fastboot or recovery to flash rom of choice
Sent from my HTC Vision using xda premium