Develop Bugs

[Q] Another unroot/s-off problem

Im hoping someone can point me in the right direction here.
Clearly I did something wrong. I could use a little direction here to get back
to factory state phone. I have a "factory phone" without root and stock apps but
S-OFF and I need to get back to S-ON
1) Rooted using Rage/Gfree method for temp root/s-off/perma root
2) Wanted to roll back(please don't ask why)
3) Tried to follow step 1a) on http://forum.xda-developers.com/showthread.php?t=835971
4) Receive following message
-- Installing: SDCARD:/stock_root.zip
E:Board does not support mtd utils.E:Failure at line 344:
write_raw_image PACKAGE:boot.img BOOT:
Installation aborted.
5) Recovered from clockwork backup
5) Went to step 1b successfully
6) Followed step 2 successfully
7) Phone patched itself OTA(step 3)
8) checked bootloader to find S -off
Steps I have taken
1) Regain temp root using rage
2) copied gfree back to phone
3) from terminal "# ./gfree -s on"
4) "#sync"
5) Reboot into bootloader to find S-OFF *sigh*
Bootloader items
VISION PVT SHIP S-OFF
HBOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
**Amendment* I don't have the gfree partition backup that gets created the first time you root

brandonmcgrew said:
Steps I have taken
1) Regain temp root using rage
2) copied gfree back to phone
3) from terminal "# ./gfree -s on"
4) "#sync"
5) Reboot into bootloader to find S-OFF *sigh*
Bootloader items
VISION PVT SHIP S-OFF
HBOOT-0.82.0000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
**Amendment* I don't have the gfree partition backup that gets created the first time you root
Click to expand...
Click to collapse
You have the regular bootloader (not the eng one), so the fact you have S-OFF still means your "gfree -s on" didn't work. You need to try that again, and look for what error messages were produced at the time.

You have the regular bootloader (not the eng one), so the fact you have S-OFF still means your "gfree -s on" didn't work. You need to try that again, and look for what error messages were produced at the time.
Can you give me the steps for that. I got temp root with rage and ran the s-on and sync commands. do you want the output from that???

brandonmcgrew said:
Can you give me the steps for that. I got temp root with rage and ran the s-on and sync commands. do you want the output from that???
Click to expand...
Click to collapse
Yes, please post up the output from when you run "./gfree -s on", that's the bit that sounds like it's failing.

# export PATH=/data/local/bin:$PATH
# cd data
# cd local
# ./gfree -s on
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.17-g9ab3677
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Searching for mmc_blk_issue_rq symbol...
- Address: c029c72c, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc029c000
Kernel memory mapped to 0x40001000
Searching for brq filter...
- Address: 0xc029c72c + 0x34c
- 0x2a000012 -> 0xea000012
Patching and backing up partition 7...
Done.
#

Well that's odd, that looks liked it worked ok.
What about if you try the stuff at http://forum.xda-developers.com/wik...ion#3._.28OPTIONAL.29_Verify_you_did_it_right to verify that S-ON has been set ?

Ok at this point I decided to get back to a spot where I felt comfortable. So I permarooted using rage/Gfree. I have also installed Clockwork and done a nandriod. So at this point here is my status. Perhaps you can help me get back to factory
1) Factory Stock w/OTA
2) Root
3) gfree verify
gfree verify_cid returned:
@CID: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
At this point I can't do anymore today but if you could/would give me a little help getting back to factory stock no root s-on simlock on I would REALLY appreciate it.

I'll do my best not to derail, but I cannot even install the stock ROMs anymore, and I think it is because of the version of CWR I am running. Since I wanted CM7, I had to install CWR 3.x. Is it safe to assume that any Android 2.3 ROM needs CWR 3.x, and any Android 2.2 or previous required CWR 2.x?

OK I finally got back to working on this and got a FIX!
See previous post(s) to get caught up......done ok GOOD
**THIS REQUIRED ADB TO BE WORKING**
**IF YOU TAKE THESE STEPS BELOW I TAKE NO RESPONSIBILTY IF SOMETHING GOES CRAZY AND YOU BRICK YOU PHONE. IM A NEWB TO THIS SO THIS IS JUST WHAT I DID**
Where I left off is I was Stock OTA rooted using the gfree/rage method. I had Clockwork installed and a nice nandroid backup(Such a good feeling). Copied backup to computer
1) Followed steps to a tee downgrade from OTA -->http://forum.xda-developers.com/showthread.php?t=831398
2) With a fresh preOTA phone I unmounted my sdcard
3) Formatted SDCard(no idea if this helped but made me happy)
4) Copied Visionary R14 to root of sdcard-->http://android.modaco.com/content/h...m/320722/19-nov-r14-visionary-one-click-root/
5) Enabled Unknown Sources install from Manage application
6) Installed File Manager from Market
7) Used File Manager to install Visionary
8) TempRoot using Visionary
9) Downloaded latest gFree from -->http://www.thinkthinkdo.com/trac/project1/raw-attachment/wiki/gfree/gfree_02.zip
10) unzip gfree_02.zip
11) open command prompt
12) enter following commands to confirm you have root
adb shell
$ su
**on phone should see superuser prompt...press allow**
if you see a "#" you got temp root
# exit
$ exit
13) Push gfree to phone
c:\adb push gfree_02 /data/local
c:\adb shell
$ su
# cd /data/local
# chmod 777 gfree
14) Set S-On
# ./gfree -s on
15) Set CID
# ./gfree -c TMO010
# exit
$ exit
16) Power off
17) Boot phone to bootloader (Hold Power +Vol Down) and confirm
VISION PVT SHIP S-ON
HBOOT-0.82.0000
MICROP-0425
RADIO -26.02.01.15.M2
eMMC-boot
18) Reboot Device. ALL DONE!!!
**If you want you could temproot again and remove all files copied for gfree to /data/local or you could do a factory reset from the bootloader**

[Q] How to test if your phone has Root using Terminal and other Rooting question

Ok. I want to know how can you test that your phone is rooted. When I'm doing the XDA method of rooting my G2, I push all the needed files to my phone, and do the thing where Terminal Force closes and you open again after you had ran rage. Now I have the root shell in Terminal.
When I run command:
$ su
not found
($) is my command line, and (blanks) is what came back. ^^
Is it suppose to say "not found"? or is it suppose to say something else? I did exactly what I was suppose to do. It wasn't all that hard. Before I did the rage command, it was
$ su
Permission Denied
That seems normal. But after I supposedly temporarily root my phone, if I open ROM manager, it tells me that I need to root my phone. What tha truck? Am I missing something?
I run:
$ /data/local/gfree -f
{export PATH=/data/local/bin:$PATH
# # /data/local/gfree -f
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x00015398 (86936)
Section index for section name string table: 41
String table offset: 0x000151df (86495)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x000011cc (4556)
-- size: 0x000000c4 (196)
Kernel release: 2.6.32.17-g9ab3677
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c029c72c, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc029c000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc029c72c + 0x34c
- 0x2a000012 -> 0xea000012
Backing up current partition 7 and patching it...
patching secu_flag: 0
Done.}
I run command:
$sync
# {sync}
I run command:
$ /data/local/tmp/root
# {/data/local/tmp/root
mkdir failed for /system/xbin, File exists
cp: can't stat '/system/xbin/busybox': Not a directory
Unable to chmod /system/xbin/busybox: Not a directory
/data/local/tmp/root: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
#}
(mkdir failed for /system/xbin, File exists) This is where I think I'm messing up. The directions say it should state:
( mkdir: /system/xbin already exists)
See the difference? The directions doesn't say "Failed" while mines does.
In Hboot mode:
VISION PVT SHIP S-OFF
HBOOT-0.82.000
MICROP-0425
RADIO-26.03.02.26_M
eMMC-boot
Sep 2 2010, 17:59:38
HBOOT
(How to navigate)
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
So what's going on? Is my phone rooted or not? Why when I go to recovery, there's this triangle thing there? LoL!! It's the picture of the phone with a red triangle.
Thanks for any help. And sorry. I completely changed the question.

I think for some reason you are missing the su binary do you have the superuser
app installed? when you type su, superuser should ask you if you want to allow terminal to access root and after accepting it $ will change to # which means you can run a command as root .
and for the red triangle, it is the stock recovery if you want to install clockworkmod ,you can flash it true Rom manager

bahmanxda said:
I think for some reason you are missing the su binary do you have the superuser
app installed? when you type su, superuser should ask you if you want to allow terminal to access root and after accepting it $ will change to # which means you can run a command as root .
and for the red triangle, it is the stock recovery if you want to install clockworkmod ,you can flash it true Rom manager
Click to expand...
Click to collapse
I have the SuperUser app installed on my phone. But once I get the root shell (#) symbol in Terminal Emulator, if i type (su) I get the response " not found ". I don't know what it's saying. It sounds like you're right when you say the file (su) isn't moving to my phone.
Dugh!!

When you're in terminal and you get the root # symbol there's nothing more to do. Just open terminal, type 'su' and hit enter. The $ should change to a # and that means you are root. If you get anything but that then like the other guy said, your su binaries are probably messed up.
In that case you the search function on here and look for something like 'reinstall su binaries'. That should set you straight. Btw, make sure to use the binaries from the gfree method, their the most current as far as I know.
Sent from my HTC Vision using XDA App

Ok. Now I really don't know what's going on. When I reboot while holding Power, and Vol+Down, I can see that I have S-Off, but when I open ROM Manager or any other root app, it tells me I need to Root my phone. Am I missing something?
And yes, I did check the forums about when people had this same problem. They aren't helping. Somehow, people are getting their root after they find something out, but I don't know what's going on.
It seems that my phone isn't TempRooting.
I did notice that when I go to Super User app, it tells me that there is an update to the SU Binary, and it fails to update, so there is a zip file on my SD Card, and that I should start the phone in recovery mode and flash it.
Right now, it says Superuser v2.3.6.1 Is that the most current, or no?
The zip file name is su-2.3.1-bin-signed.zip
Thanks for any help. I don't know how I got S-Off, a Root Shell, and still don't have Temp Root to go to PermaRoot.

What instructions did you use to root? Sounds like you might have skipped a step. Also how did you temporarily root?

What do you have in /system/xbin ?
HTC Vision 1.8 OC, CM7 RC1==HAPPY!!

[Q] Is my phone "really" rooted?

Ok. Let me tell you all what I have.
I have:
S-Off
Root Shell (#)
Super User App
Yet when I open ROM manager, it tells me I need to root my phone. Excuse me!? Is my phone not rooted? Am I missing something?
I tried rooting using this method (http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2) and when I did the gfree_verify, everything came out ok. But when I reboot, I lose my root shell and when I type "su" it tells me permission denied. I have to do the temp root method every time to get the root shell (#).
And here's the thing. Even though I have the root shell (#), root apps, like ROM manager tell me my phone isn't rooted. I thought your phone was tempRooted or Rooted if you had the Root shell, S-Off and Super User app.
Am I missing something? The gfree_verify and what I think the problem is, is below.
()()()C:\Users\Izaya\Downloads\Phone ROMS\G2 Root_2011\Newest Root Method>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# stop ril-daemon
stop ril-daemon
# ./gfree_verify
./gfree_verify
gfree verify_cid returned:
OK
gfree verify_secu_flag returned:
@CID: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
# start ril-daemon
start ril-daemon()()()
# cd /data/local/tmp
cd /data/local/tmp
# ./gfree -f
./gfree -f
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x00015384 (86916)
Section index for section name string table: 41
String table offset: 0x000151cb (86475)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x000011cc (4556)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.17-g9ab3677
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c029c72c, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc029c000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc029c72c + 0x34c
- 0x2a000012 -> 0xea000012
Backing up current partition 7 and patching it...
patching secu_flag: 0
Done.
(Right Here, it looks like this is a problem. I made sure that I pushed all my files to my phone, so making sure that I pushed them to the phone is not why. Please have a different response from that. Thanks *smiley face*
()()()# ./root_psn
./root_psn
cp: can't stat '/system/xbin/busybox': Not a directory
Unable to chmod /system/xbin/busybox: Not a directory
./root_psn: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
#()()()
It looks like this busybox thing is what's messing up or something. Is there someway I can format the /data/local/tmp folder so I can just redo everything, or when I push the same file, does it over right? Because I've been pushing multiple times only to come up with this same error multiple times.

No_Nickname90 said:
Ok. Let me tell you all what I have.
I have:
S-Off
Root Shell (#)
Super User App
Yet when I open ROM manager, it tells me I need to root my phone. Excuse me!? Is my phone not rooted? Am I missing something?
I tried rooting using this method (http://forum.xda-developers.com/wiki/index.php?title=HTC_Vision#Rooting_the_G2) and when I did the gfree_verify, everything came out ok. But when I reboot, I lose my root shell and when I type "su" it tells me permission denied. I have to do the temp root method every time to get the root shell (#).
And here's the thing. Even though I have the root shell (#), root apps, like ROM manager tell me my phone isn't rooted. I thought your phone was tempRooted or Rooted if you had the Root shell, S-Off and Super User app.
Am I missing something? The gfree_verify and what I think the problem is, is below.
()()()C:\Users\Izaya\Downloads\Phone ROMS\G2 Root_2011\Newest Root Method>adb shell
# cd /data/local/tmp
cd /data/local/tmp
# stop ril-daemon
stop ril-daemon
# ./gfree_verify
./gfree_verify
gfree verify_cid returned:
OK
gfree verify_secu_flag returned:
@CID: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
# start ril-daemon
start ril-daemon()()()
# cd /data/local/tmp
cd /data/local/tmp
# ./gfree -f
./gfree -f
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x00015384 (86916)
Section index for section name string table: 41
String table offset: 0x000151cb (86475)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x000011cc (4556)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.17-g9ab3677
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c029c72c, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc029c000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc029c72c + 0x34c
- 0x2a000012 -> 0xea000012
Backing up current partition 7 and patching it...
patching secu_flag: 0
Done.
(Right Here, it looks like this is a problem. I made sure that I pushed all my files to my phone, so making sure that I pushed them to the phone is not why. Please have a different response from that. Thanks *smiley face*
()()()# ./root_psn
./root_psn
cp: can't stat '/system/xbin/busybox': Not a directory
Unable to chmod /system/xbin/busybox: Not a directory
./root_psn: /system/xbin/busybox: not found
cp: not found
cp: not found
Unable to chmod /system/bin/su: No such file or directory
#()()()
It looks like this busybox thing is what's messing up or something. Is there someway I can format the /data/local/tmp folder so I can just redo everything, or when I push the same file, does it over right? Because I've been pushing multiple times only to come up with this same error multiple times.
Click to expand...
Click to collapse
Strange; try downloading Titanium Backup from the Market, select "Problems" and download BusyBox and SuperUser from there.
Sent from my HTC Vision using XDA App

OriginalGabriel said:
Strange; try downloading Titanium Backup from the Market, select "Problems" and download BusyBox and SuperUser from there.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I don't think I made myself clear. (I'm not being sarcastic. LoL!!) What I'm saying is, although I did the tempRoot method and have the Root shell, even after the TempRoot method, ROM manager still says "I need to Root my phone" even though I have the root shell. I don't think my phone is even tempRooting, and it looks like for some weird reason, busybox isn't getting pushed to the right places.
IDK what's going on. I have yet to see this problem else where. *sad face* I want the joys of a custom ROM.
Remember, I can't even PermaRoot, if I can't even TempRoot. Visionary didn't even TempRoot my phone. I would do the Visionary method, open Terminal Emulator, type "su" and get "permission denied" *sad face*
If someone ever tells me "permission denied" Ima hurt them. LoL!!

Unable to ROOT Desire Z from 2.2.1?

I want to load a custom ROM on my Desire Z. (finally!)
And I eventually got adb to work.
Now following the guide: Rooting the Vision (G2/DZ) and DHD; I got as far as this step:
4 S-OFF, root and its friends Super-CID, SIM-unlock, engineering hboot, clockwork recovery and root
In the following section we are trying to gain write access to the emmc by power cycling it.
We recommend to install the engineering hboot as part of the gfree procedure.
In the root shell (indicated by the #) that you got in the Temporary root section execute the following commands:
Code:
# cd /data/local/tmp
# ./gfree -f -b hboot-eng.img -y recovery.img
# ./root_psn
# sync
Wait a few seconds for the changes to "take".
Click to expand...
Click to collapse
Before receiving this error:
Code:
# ./gfree -f -b hboot-eng.img -y recovery.img
./gfree -f -b hboot-eng.img -y recovery.img
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
--hboot set. hboot image hboot-eng.img will be installed in partition 18
--recovery set. recovery image recovery.img will be installed in partition 21
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.21-g132894e
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c02adc44, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02ad000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc02adc44 + 0x34c
- 0x2a000012 -> 0xea000012
Backing up current partition 18 and installing specified hboot image...
md5sum #1 = 62c0aac0a85f3a0a0cbe364b64c552e6
md5sum #2 = 2ce1bdd5e4c1119ccfcecb938710d742
Backing up partition /dev/block/mmcblk0p18 to /sdcard/part18backup-1363017105.bin ...
Writing image hboot-eng.img to partition /dev/block/mmcblk0p18 ...
md5sum #3 = 62c0aac0a85f3a0a0cbe364b64c552e6
md5sum #3 == md5sum #1 - the hboot image was not installed!
Probably the power cycle of the eMMC failed. Check the messages above.
You might join the IRC channel #G2Root on Freenode for further help!
What should be my next course of action?
Thanks for all suggestions,
Alec Taylor

Double check you have the right hboot downloaded and that the md5sum matches, then run the command again. If you still have issues copy and paste your input/output from cmd here
Sent from my Nexus 7 using xda premium

I have included the input/output from my CMD in the initial post.

Sorry I thought you were just copying and pasting from the guide you were folowing. I guess I was reffuring to the entire root procedure but its no big deal
Its telling you exactly what is happening, phone didn't take the flash of the new engineeging bootloader, probably the emmc didn't cycle, try running command again, if its the same outcome double check your radio version as that can cause this or can you post all info from your hboot screen here
Sent from my SGH-T839 using Tapatalk 2

Also I couldn't get it to work with Gingerbreak or DooMLoRD's Easy Rooting Toolkit either.

*bump*

Right down all info on boot loader, you seem to know what to do but you're missing something, possibly need to change radio as gfree will not work with newer ones
Sent from my Nexus 7 using xda premium

FYI: Was able to root it finally by upgrading my stock to gingerbread from froyo; then back down to non-stock froyo followed by upgrade to modded Jelly Bean.

[Q] Desire Z - Upgrade to Android 4

Hi Everybody,
I know, that there are a lot of threats about this fact in the forum. But nothing will work for me, aspessially important links will not work anymore. Could anybody help me?
If I go to the bootloader (noise - and Power-On) there are the following informations written:
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_MeMMC-boot
Apr 11 2ß11,23:36:27
HBOOT
OK, on my cell is working a Android 2.3.3, so I have to root my cell and downgrade.
I tryed to do this with the following threat: http://forum.xda-developers.com/showthread.php?t=905261
1. I Tryed to create a GOLDCARD. I read this threat, got the CID of my cell with the the code
Code:
adb shell cat /sys/class/mmc_host/mmc2/mmc2:*/cid
. Now I should type this CID in a webformular at this link to reverse it. This formular is still working, but there is also a Excel-Tool on this page for downloading, which should do the same. So my CID like "035344534d49202010000073b900d494" was reversed to "00d400b9730000102020494d53445303".
This code I should input to this formular for creating a GOLDCARD, but it doesn't work anymore.
So I looked around and found this threat, where a goldcardcreator is downloadable.
In this zip-file is included a program named "SimpleGoldCard", which read a reversed CID from the cell. On a command-Line I typed in
Code:
gcard -c 00d400b9730000102020494d53445303 -r -o "GoldCard.img"
Than I putted in the sd-Card into the Card-Reader of my Desktop, formatted it, used the tool "HeX Editor", copyed (line) 00000000 to offset (line) 00000170 (including the 00000170 line) and pasted it to the SD-Card.
After that I hope to created a correct GoldCard.
2. After that I downloaded the files psneuter, PC10IMG.zip and root. But in this threat is written, that I have to extract "misc_version_01.zip". Where is this file? I searched in this forum and downloaded a file named like this. Are there Differences or is a special version needed? I copyed the PC10IMG.zip to the SD-Card and put this to the cell.
3. then I booted the cell again, connected it to the desktop and used the following commands to put the downloaded files to the cell
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
After that I should get the # - symbol instead of the $ - symbol which means, that I rooted the phone. But here is my first problem, I didn't get the # - symbol, so I don't have the permission to start the next programms.
4. Normally I would do next the following commands and then to reboot and flash the older Firmware.
Code:
/data/local/tmp/misc_version -s 1.33.405.5
exit
adb reboot bootloader
But when I reboot, the bootloader is looking for the PC10IMG.zip, is loading and checking this ... and gives me the information
CID incorrect!
Update Fail!
Press <POWER> to reboot.
Well, this is the next big problem.
Cold anybody tell me, where my mistakes are? I read 2 days in the forum, tryed a lot to get the final result, but now I don't have the time anymore to continue in this way.
THanks a lot. with best regards, Speedy8

Mods please move to q&a
Always check the stickies
http://forum.xda-developers.com/showthread.php?p=43195539
Follow the threads linked here, don't use any other to root your phone, they will either be outdated or cause you trouble.
After following these threads if you still have issues post back and I'll try to help ya
Best of luck!
Sent from my Nexus 4 using xda premium

well ... I searched again today ... and found the following threat, which was working on my cell-phone.
And also at the cyanogenmod-page you can find the relevant things to root the Desire Z. You can find it here.
Now I will first install the latest cyanogenmod, which is for the Desire Z not the Android 4, but at the moment newer than 2.3.3.
Thanks for answering, my Questions are answered.
With best regards.