Develop Bugs

Trying to use ADB to flash_image on Desire Z

Hey, I've been following Cyanogen mods guide about flash_image to flash PSFmod onto my phone. I can use ADB to push files to my SD card and stuff, but when I follow this:
Code:
Temporarily allow app to run from the sdcard (use mount to find the correct device for your sdcard, ie: the /dev/block/BLAH part)
mount -o remount,exec /dev/block//vold/179:1 /sdcard
cd /sdcard
./flash_image recovery /sdcard/recovery.img
But I get this error:
Code:
error scanning partitions
Does anyone know how to fix it?

You get that error from which of those commands ?

From flash_image.
Whenever I run flash_image from my phone now, I get that partition error.
Is it because I'm on a Desire Z?

Beegee7730 said:
From flash_image.
Whenever I run flash_image from my phone now, I get that partition error.
Is it because I'm on a Desire Z?
Click to expand...
Click to collapse
Where did you get the flash_image utility from ? Was it from somewhere that has verified it to work on DZ ?

Dude u might brick ur phone lol ...try using Rom manager .....its safer
Sent from my HTC Vision using XDA App

I would use fastboot to flash a new recovery. You're sure what you're flashing is ok for the Vision, right ?

steviewevie said:
Where did you get the flash_image utility from ? Was it from somewhere that has verified it to work on DZ ?
Click to expand...
Click to collapse
I got it from the Cyanogen Mod Wiki, should I look for a different version?
theXeffect said:
Dude u might brick ur phone lol ...try using Rom manager .....its safer
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I would but the recovery I'm flashing isn't supported by Rom Manager.
steviewevie said:
I would use fastboot to flash a new recovery. You're sure what you're flashing is ok for the Vision, right ?
Click to expand...
Click to collapse
How do I use Fastboot? It should be okay for it, as it's the G2 version of Psfmod.

Beegee7730 said:
How do I use Fastboot? It should be okay for it, as it's the G2 version of Psfmod.
Click to expand...
Click to collapse
If you've got adb all setup via installing the SDK etc, then fastboot should work fine too. I think you need the engineering bootloader though.
Boot the phone into fastboot by holding down the trackpad button and holding the Power button, with the phone off. Or you can put it into hboot with Volume Down and Power and then select "Fastboot" from the menu.
It should then say "Fastboot" on the phone. With the USB cable plugged in that should say "Fastboot USB", and if you run "fastboot devices" on your PC it should show up your phone in the same way that "adb devices" normally would.
If that's all working you can run "fastboot flash recovery filename.img" to flash "filename.img" to recovery.

steviewevie said:
If you've got adb all setup via installing the SDK etc, then fastboot should work fine too. I think you need the engineering bootloader though.
Boot the phone into fastboot by holding down the trackpad button and holding the Power button, with the phone off. Or you can put it into hboot with Volume Down and Power and then select "Fastboot" from the menu.
It should then say "Fastboot" on the phone. With the USB cable plugged in that should say "Fastboot USB", and if you run "fastboot devices" on your PC it should show up your phone in the same way that "adb devices" normally would.
If that's all working you can run "fastboot flash recovery filename.img" to flash "filename.img" to recovery.
Click to expand...
Click to collapse
Wait a sec.

steviewevie said:
If you've got adb all setup via installing the SDK etc, then fastboot should work fine too. I think you need the engineering bootloader though.
Boot the phone into fastboot by holding down the trackpad button and holding the Power button, with the phone off. Or you can put it into hboot with Volume Down and Power and then select "Fastboot" from the menu.
It should then say "Fastboot" on the phone. With the USB cable plugged in that should say "Fastboot USB", and if you run "fastboot devices" on your PC it should show up your phone in the same way that "adb devices" normally would.
If that's all working you can run "fastboot flash recovery filename.img" to flash "filename.img" to recovery.
Click to expand...
Click to collapse
Tried few days ago with a kernel,but don`t works too.
You mean I need the eng hboot,then it should work,right?
Otherwise fastboot don`t work.

C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (4214 KB)... OKAY [ 0.891s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.891s
C:\android-sdk-windows\tools>

Beegee7730 said:
C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (4214 KB)... OKAY [ 0.891s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.891s
C:\android-sdk-windows\tools>
Click to expand...
Click to collapse
You haven't got S-OFF. You need S-OFF to flash a custom recovery.

I do have S-Off, I followed this and when I boot into fastboot it says "S-OFF" in green text at the top.

Beegee7730 said:
I do have S-Off, I followed this and when I boot into fastboot it says "S-OFF" in green text at the top.
Click to expand...
Click to collapse
ok, do you have the engineering bootloader ? Does it say "SHIP" or "ENG" at the top.

steviewevie said:
ok, do you have the engineering bootloader ? Does it say "SHIP" or "ENG" at the top.
Click to expand...
Click to collapse
SHIP.
I assume I need to reflash it with the engineering one?

Beegee7730 said:
SHIP.
I assume I need to reflash it with the engineering one?
Click to expand...
Click to collapse
Yeah I think you need the engineering bootloader for fastboot to work fully. I didn't think you'd get that sort of error for no eng bootloader though.

steviewevie said:
Yeah I think you need the engineering bootloader for fastboot to work fully. I didn't think you'd get that sort of error for no eng bootloader though.
Click to expand...
Click to collapse
Code:
C:\android-sdk-windows\tools>adb push hboot-eng.img /data/local
1598 KB/s (0 bytes in 1048576.000s)
Is that supposed to happen?

Beegee7730 said:
Code:
C:\android-sdk-windows\tools>adb push hboot-eng.img /data/local
1598 KB/s (0 bytes in 1048576.000s)
Is that supposed to happen?
Click to expand...
Click to collapse
Did it work and is the file there in /data/local now ?
Do a checksum on the eng hboot before you flash it, as per the guides, to make sure it's not corrupted.

steviewevie said:
Did it work and is the file there in /data/local now ?
Do a checksum on the eng hboot before you flash it, as per the guides, to make sure it's not corrupted.
Click to expand...
Click to collapse
Ah, managed to flash it.
Will test and report back when done.
EDIT:
It works!
Thanks alot!

steviewevie said:
Yeah I think you need the engineering bootloader for fastboot to work fully. I didn't think you'd get that sort of error for no eng bootloader though.
Click to expand...
Click to collapse
I think too,the same with my HTC Hero.
Fastboot wont work without engineering bootloader/hboot!
So the same at Desire Z.

[Q] Bricked or is there still hope?

I'm messing around since 3 days with a non working Desire.
I was trying to root that Vodafone UK Branded Phone with a goldcard, but it somehow did't really work stable.
So I managed it to install a RUU in order to revert it and begin the Process from the beginning on:
1.This was the RUU, and everything went fine: RUU_Bravo_Froyo_Vodafone_UK_2.33.161.2_Radio_32.49.00.32U_5.11.05.27_release_157522_signed
2.Then I tried to downgrade my HBOOT from 0.93.0001 to 0.80 using the method in this thread (with goldcard!)
3. During the installation of the PB99IMG.zip something went wrong and (maybe a mismatch with goldcard or the mtd0.img, i still don't know / understand) HBOOT could not be updated and RADIO-V2 also
4. now I cant boot the Phone at all or issue adb commands (I think the phone needs to be fully booted and USB-debbug-enabled for this) so I cant follow any of the solutions wich I found in the last two days. A PB99IMG.zip is also not flashable in HBOOT since it just cancels after "Checking..[PB99IMG.zip]" and returns back to the HBOOT screen.
Here's my phones specs:
CID: VODAP102
PVT4
S-ON
HBOOT 0.93.0001
MICROP-051d
SLCD
RADIO 5.11.05.27
If someone has an idea where to start, any help would be greatly apreciated. If someone is even willing to assist via instant messaging or skype I would be happy to compensate his time with a donation via paypal! Thank you in advance!
EDIT: SOLVED!!!
cosine83 from the unrevoked IRC channel solved it for me!!
I was able to enter RUU mode and flash the PB99IMG.zip in 2 quick steps!
In fastboot mode:
1.fastboot oem rebootRUU
2.fastboot flash zip PB99IMG.zip
huge thanks!!!

Hello sorry for that
but the good news is your phone is not dead, do you red this
http://forum.xda-developers.com/showthread.php?t=750888
I think your fix is here : http://forum.xda-developers.com/showthread.php?p=7602850#post7602850
hope it can help you

what happens if you hold vol down + power when the phone is off?

Good idea. I forgot to ask
Sent from my HTC Desire using XDA Premium App

Droidxda said:
Hello sorry for that
but the good news is your phone is not dead, do you red this
http://forum.xda-developers.com/showthread.php?t=750888
I think your fix is here : http://forum.xda-developers.com/showthread.php?p=7602850#post7602850
hope it can help you
Click to expand...
Click to collapse
Trying this right now, almost gave up on this...
vol down + power brings me to the regular hboot manu and i can also enter fastboot...

Regular 0.93 ?
Do you try unrevoked?
Sent from my HTC Desire using XDA Premium App

Droidxda said:
Regular 0.93 ?
Do you try unrevoked?
Sent from my HTC Desire using XDA Premium App
Click to expand...
Click to collapse
for unrevoked I need my phone booted up and have debugging enabled as far as i know, but I cant boot it...
EDIT: I followed your guide from HERE but the result is still the same. I am not able to flash the PB99IMG.zip HBOOT reads it (the blue bar on the right top goes all the way up but then comes "Checking..[PB99IMG.zip]" and the procedure just aborts.
I think it must have something to do with a wrong mtd0.img which was flashed during my first attempt to downgrade (mybe not matching the PB99IMG???) or there is a problem with the goldcard (i am very certain that I did everythin correct with the gc, did it manually and also tith the gc-maker)

On the fastboot menu, could you access a recovery?
Sent from Desire Bravo with xda App. Leedroid ROM HD port inside.

Droidxda said:
On the fastboot menu, could you access a recovery?
Sent from Desire Bravo with xda App. Leedroid ROM HD port inside.
Click to expand...
Click to collapse
well I can select the "recovery" from the Hboot menu and also try flashing an update.zip, but every time I do this I get:
E:failed to verify whole-file signature
E:signature verifivation failed
Installation aborted

The best way should find a correct hboot P99IMG.zip and put it on the SD
Should ask to unrevoked team by the irc channel.
Sent from Desire Bravo with xda App. Leedroid ROM HD port inside.

cgorki said:
well I can select the "recovery" from the Hboot menu and also try flashing an update.zip, but every time I do this I get:
E:failed to verify whole-file signature
E:signature verifivation failed
Installation aborted
Click to expand...
Click to collapse
**** I know this message, but I can't remember.
EDIT - hboot 0.93 ?
Sent from Desire Bravo with xda App. Leedroid ROM HD port inside.

I thought it wasn't possible to change hboot until you s-off? or does a goldcard make it possible when s-on?
if you can access the bootloader menu (vol down + power) then you should be able to fix your phone.

Do you try to install an ruu Rom?
Sent from Desire Bravo with xda App. Leedroid ROM HD port inside.

Boot the phone into bootloader menu.
connect usb cable.
in command prompt load the SDK folder, instead of typing adb.exe type fastboot.exe.
place the hboot you want into the "platform-tools" folder in the SDK directory - if its in the pb99img.zip then extract the .img file from there and place just that file into the folder.
type "fastboot flash hboot *name-of-file.img*"
if this works then type
type "fastboot reboot-bootloader"
type "fastboot erase cache"
Not sure it will work though as you are S-ON.
However you should be able to flash a recovery through the same way, type "fastboot flash recovery *name.img*". Not sure if this will help fix it, but if you can access recovery then its a start! Obviously you'll need to download a recovery first and place it into the platform-tools folder.

himeshladva said:
Boot the phone into bootloader menu.
connect usb cable.
in command prompt load the SDK folder, instead of typing adb.exe type fastboot.exe.
place the hboot you want into the "platform-tools" folder in the SDK directory - if its in the pb99img.zip then extract the .img file from there and place just that file into the folder.
type "fastboot flash hboot *name-of-file.img*"
if this works then type
type "fastboot reboot-bootloader"
type "fastboot erase cache"
Not sure it will work though as you are S-ON.
However you should be able to flash a recovery through the same way, type "fastboot flash recovery *name.img*". Not sure if this will help fix it, but if you can access recovery then its a start! Obviously you'll need to download a recovery first and place it into the platform-tools folder.
Click to expand...
Click to collapse
doubt that this will work with s-on, but trying anyways!!
thank you!

cgorki said:
doubt that this will work with s-on, but trying anyways!!
thank you!
Click to expand...
Click to collapse
would probably give the recovery option a go first..

himeshladva said:
would probably give the recovery option a go first..
Click to expand...
Click to collapse
C:\1>fastboot flash recovery cwm.img
sending 'recovery' (3366 KB)... OKAY [ 0.488s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.958s
EDIT: Is there a way to issue ADB commands to the phone without having it booted up?

cgorki said:
C:\1>fastboot flash recovery cwm.img
sending 'recovery' (3366 KB)... OKAY [ 0.488s]
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.958s
EDIT: Is there a way to issue ADB commands to the phone without having it booted up?
Click to expand...
Click to collapse
You can if you are able to access recovery.. or try to just turn the phone on and see.
Also, take a read through this.. maybe it will help.
http://www.askabouthugo.com/general...n-fastboot-with-remote-signature-verify-fail/

Not sure what else can be done if that doesn't help.
Would be best to join unrevoked IRC channel as they would know a lot more about it..

himeshladva said:
Not sure what else can be done if that doesn't help.
Would be best to join unrevoked IRC channel as they would know a lot more about it..
Click to expand...
Click to collapse
I'm talking to some of the guys from the IRC, so far no solution in sight. Maybe tomorrow there are some ppl online who are familiar with the HTC Bravo GSM...

S-ON after Revolutionary S-OFF possible? [SOLVED]

I'm looking for a way to remove Revolutionary S-OFF...
I tried flashing several RUUs with different HBOOT versions but Revolutionary HBOOT is very persistant
I'd would love to return to HBOOT 0.93 since I have to return my device due to a possible hardware error.
anyone have a suggestion? tnx

Only to use RUU

name.vic said:
Only to use RUU
Click to expand...
Click to collapse
not sure what you mean exactly, but just flashing a stock RUU with NOT remove revolutionary HBOOT. I'll explain in next post.

SOLVED: just got THE answer from someone at #revolutionary
1. what: downgrade HBOOT using AlphaRev
how: go to http://alpharev.nl/, download (and always MD5-) check "bravo_downgrade.img", flash using fastboot
2. what: flash stock RUU
how:go to http://shipped-roms.com/index.php?category=android&model=Bravo and download RUU for your device and run the executable
(I chose "RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe " since it turned out to contain HBOOT 0.93 which I wanted)
3. done

Thank you thank you thank you thank you thank you !
Puff, i got a good scare after upgrading to GB.
I found out that after upgrading I cannot simply RRU my way back, installed revolutionary then I wanted to bring my Desire to service [reboots] and wanted to get rid of s-off and revolutionary hboot to make it "stock".
Once again, thanks to this great community !

hi.
Hope someone still watching these posts.
I tried your solution.
Flashed the hboot and it switched from Revolutionary to alpharev.
Then i flashed the phone with stock ruu RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe
But still no luck.
The methods iv tried is:
All through command in windows, :
adb devices
adb reboot bootloader
fastboot devices
fastboot flash hboot bravo.img <-- i renamed the file i took from the ruu im using.
flash hboot - reboot to android os - stock ruu flash = no stock hboot
flash hboot 4 times - reboot to android os - stock ruu flash = no stock hboot
flashed hboot - still in hboot i ran stock ruu = no stock hboot.
am i missing any step?
My phone/hboot is:
Swedish unlocked HTC Desire.
Bravo pvt4 ship s-off
hboot 6.93.1002
radio 5.11.05.27

Why are you using adb? You must be on the fastboot screen not hboot screen
Sent from my HTC Desire using XDA App

rootSU said:
Why are you using adb? You must be on the fastboot screen not hboot screen
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Hi and ty for your reply.
I think i have tried it in fastboot to.
Or on my phone it says fastboot usb marked in red collor.
Is that right or wrong?
could you give me a step by step?
I have the revolutionary drivers and uninstalled htc sync alredy.
The things iv tried so far is this list of commands in order:
cd c:\desire <--- where i have the files
adb devices
adb reboot bootloader
fastboot devices
fastboot flash hboot bravo.img

rootSU said:
Why are you using adb? You must be on the fastboot screen not hboot screen
Click to expand...
Click to collapse
how do you flash files in fastboot,if not with adb to my knowledge he was in the fastboot screen(when you adb reboot bootloader thats where it takes you)
we need more detail in step #2. after getting an "ok" flashing the downgrader image in step one,do you reboot to the OS,then run the executable from there? or do you run it while still in fastboot?
ive been helping him on another forum,and from what he describes,it looks like hes followed DXsl's steps,but it still hasnt worked.
thanks for any info

After flashing the downgrader, you cannot boot any rom, because the downgrader deletes all internal partitions. So after flashing the hboot downgrader successfully, just enter this
Code:
fastboot reboot-bootloader
When done, flash ruu. At the end you are on stock rom with stock hboot (s-on).
A little note at the end: If your phone is in fastmode mode, you cannot use adb (commands). If your phone is in hboot mode, you cannot use fastboot (commands). And fastboot can only be used if one is s-off. I know you are in this state, but this information is for the future.

MatDrOiD said:
After flashing the downgrader, you cannot boot any rom, because the downgrader deletes all internal partitions. So after flashing the hboot downgrader successfully, just enter this
Code:
fastboot reboot-bootloader
When done, flash ruu. At the end you are on stock rom with stock hboot (s-on).
A little note at the end: If your phone is in fastmode mode, you cannot use adb (commands). If your phone is in hboot mode, you cannot use fastboot (commands). And fastboot can only be used if one is s-off. I know you are in this state, but this information is for the future.
Click to expand...
Click to collapse
i see what you are getting at now. while you are in fastboot mode,you technically are using fastboot commands,not adb commands. kind of splitting hairs,but correct. when folks are in the CMD window and entering commands to the phone they broadly describe the experience as "using ADB".
while an engineering or patched hboot provides alot more functionality,there are limited commands for s-on in fastboot mode.
thanks for the info

This isn't working. RUU managed to flash HBOOT, Radio, Signature, but after that it gives error 140 and ends.
---------- Post added at 01:50 PM ---------- Previous post was at 01:29 PM ----------
So I tried to install it manually and the only component that failed to flash was system. Here is log:
Code:
********************************
###Calling fastboot with: flash system D:\Programy\Android\system\PB99IMG_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed\system.img###
sending 'system' (254219 KB)... FAILED (remote: data length is too large)
finished. total time: 0.004s
********************************

Is that with the downgrader flashed?
Sent from my HTC Desire using XDA App

Yes.
10char

How much total space do you have on system? (try a df -f on a terminal emulator)

Dunno, but I wiped entire phone and GB RUU runs fine.

Terepin said:
Dunno, but I wiped entire phone and GB RUU runs fine.
Click to expand...
Click to collapse
I think your partition size is somehow smaller than it should be. Did you flash the stock HBOOT after flashing downgrade HBOOT?
PS: also use command "fastboot erase cache" after flashing HBOOT and "fastboot reboot bootloader" too. Just to be sure

theGanymedes said:
I Did you flash the stock HBOOT after flashing downgrade HBOOT?
Click to expand...
Click to collapse
Nooo..If after the downgrader u flash the stock one, u are locked s-off again (downgrade protection)
the downgrader is already stock, and because this one has no protection, the ruu overwrite it before to flash the system partition

andQlimax said:
Nooo..If after the downgrader u flash the stock one, u are locked s-off again (downgrade protection)
the downgrader is already stock, and because this one has no protection, the ruu overwrite it before to flash the system partition
Click to expand...
Click to collapse
With custom MTD, we had to format system, cache and data so maybe it would be best practice to do that after flashing the downgrader if you still have recovery (i.e havent tried to run an RUU over CM7 hboot)

yes, u can't flash an ruu over the cm7 hboot, but u can over the downgrader
this damn downgrader is the stock hboot (with stock partitions size)with no protection..all the other hboots on alpharev have the downgrade protection (so an ruu can't overwrite it)
so for example, if u have the cm7 hboot, u dont need to flash the stock hboot and then the downgrader hboot (or viceversa)..only the downgrader is enough..the downgrader is an hboot with stock partition size
in addition, the first thing that the ruu does is to flash the hboot with stock size (only after the ruu flash the system)..but of course, it will successfully write the hboot only if u have the downgrader one

[Q] How to flash an hboot with fastboot/adb

Clockworkmod recovery doesn't work(only get a blank screen after I make my selection), and my phone wont boot. I'm trying to flash a rom via fastboot or adb.
I installed fastboot and adb using this guide:
fastboot adb guide
I downloaded htc sync to install the drivers.
I'm trying to follow this guide for flashing a new rom
xda flashing guide
when i try "fastboot -w" the command prompt returns "erasing 'userdata'... FAILED <remote: not allowed>"
it seems the sollution for this is posted here. but i don't know how to flash an hboot. Can anyone point me in the right direction? I've been searching and all i could find was fastboot commander, but when I try to flash a new Hboot or my recovery image it returns "flash FAILURE"

sombomb said:
Clockworkmod recovery doesn't work(only get a blank screen after I make my selection), and my phone wont boot. I'm trying to flash a rom via fastboot or adb.
I installed fastboot and adb using this guide:
fastboot adb guide
I downloaded htc sync to install the drivers.
I'm trying to follow this guide for flashing a new rom
xda flashing guide
when i try "fastboot -w" the command prompt returns "erasing 'userdata'... FAILED <remote: not allowed>"
it seems the sollution for this is posted here. but i don't know how to flash an hboot. Can anyone point me in the right direction? I've been searching and all i could find was fastboot commander, but when I try to flash a new Hboot or my recovery image it returns "flash FAILURE"
Click to expand...
Click to collapse
In clockwork use the trackball to select items, not the power button.
To use most fastboot commands you need an unlocked bootloader, or the engineering bootloader. To chanhe your bootloader you need to be s-off, or do an entire ruu.

cmlusco said:
In clockwork use the trackball to select items, not the power button.
To use most fastboot commands you need an unlocked bootloader, or the engineering bootloader. To chanhe your bootloader you need to be s-off, or do an entire ruu.
Click to expand...
Click to collapse
Wasn't using the trackball. This is embarrassing. Thanks for all the helpful info, you're awesome.

=X
wow this is funny, but sadly it helped me also

In case you'd still like to know how to do it via fastboot, here are some steps:
Place the .zip in the same directory as the adb and fastboot executables
Double check the md5 of the .zip before proceeding to prevent bricking the device
Run the following commands in command prompt:
fastboot devices //Verify that the device is detected
fastboot erase cache //Not sure if this is completely necessary, but the guide I followed included it as a step
fastboot oem rebootRUU //Boot into RUU, which lets you flash HBOOT, radio, etc.
fastboot flash zip [zipname.zip] //Replace zipname.zip with the actual name of the file you are flashing
fastboot reboot-bootloader //The guide I pulled this info from didn't specifically say that you should reboot to bootloader rather than to Android, but I have seen others mention that you should always reboot to the bootloader first after flashing an HBOOT or radio. I would do this just in case

thehiggins you saved the day

Thanks You
Didn't know I had to be in RUU. When do I need to be in RUU, when flashing the boot or any boot related img/zip ?

[Q] HTC Desire Z NOT BOOTING at all and cannot make S-OFF

My Desire Z was previously running official updated Android 2.3.3 Gingerbread. I did the following.
1. unlocked bootloader from official HTCDEV.
2. installed CWM 6.0.4.5 with fastboot from this link http://forum.xda-developers.com/showthread.php?t=2561226
3. According to instructions from this link http://www.teamandroid.com/2013/03/13/update-htc-desire-z-android-422-aosp-jelly-bean-custom-rom/2/, in CWM recovery, I wiped data.
4. Then I installed Custom ROM AOSP 4.2.2 zip and Gapp received from this link http://forum.xda-developers.com/showthread.php?t=2163579
After that, and Now, no matter how I try, my Desire Z cannot boot anymore and hanging only at HTC logo white screen.
-I can only go to fastboot mode and go to CWM recovery 6.0.45.
-I tried wipe data, cache, dalvick cache from recovery, but still cannot boot.
-This is the detail of the bootloader and system:
VISION PVT SHIP S-ON
HBOOT-0.85.0015
MICROP-0425
RADIO-26.10.04.03_M
eMMC-boot
DEC 20 2010,16:21:13
Carrier: htc Asia WWE
Model: PC1011000
-I saw s-on when I power on at bootloader mode. I don't know how to root and make s-off.
-I cannot use ADB because I cannot boot and my adb cannot find the device in bootloader/fastboot mode.
-In CWM mode, my adb saw it as "SH118RT01215 recovery" with adb devices command.
-So with CWM mode, When I run "adb shell cat /dev/msm_rotator" command, I received "cat: read error: Invalid argument"
-When I run "chmod 777 /data/local/tmp/fre3vo" after "adb push", it shows "no such file or directory"
-I tried to do instructions given as on http://forum.xda-developers.com/showthread.php?t=1178912 but received errors.
-I also tried instructions from http://wiki.cyanogenmod.org/w/HTC_Desire_Z:_Firmware_Downgrade_(Gingerbread) but no luck.
I would like to install custom ROM and use Android 4.x on my Desire Z.
What should I do now? Please help. :crying: :crying: :crying:

Being you are s-on, after flashing a custom ROM in recovery you need to boot into bootloader and flash the kernel via fastboot
Unzip the ROM, extract the boot.img
fastboot flash boot boot.img
fastboot reboot
After this when up and running I highly suggest relocking your phone and following the steps to downgrade and root via gfree

demkantor said:
Being you are s-on, after flashing a custom ROM in recovery you need to boot into bootloader and flash the kernel via fastboot
Unzip the ROM, extract the boot.img
fastboot flash boot boot.img
fastboot reboot
After this when up and running I highly suggest relocking your phone and following the steps to downgrade and root via gfree
Click to expand...
Click to collapse
Thanks demkantor. With your instructions and the help from Nipqer at g2root chat. The problem is solved. Successfully S-OFF and now running Custom ROM android 4.2.2.
Thanks again a lot for everybody. :good::good::laugh: