Root [HOW TO] an easier way to flash PH98IMG files

[chucktr]

However, your last statement:
left me a little uncomfortable. IF the ROM.img is flashable via the SD card, say the CM10.1 image, then it should be flashable with the fastboot... right?? I mean, they should have the 'same' requirements. Especially, IF you are S-Off.

no. they do not have the same requirements at all. thats what i was getting at with this explanation above(wich i apparently didnt do very well ):

on your first question,zips intended to flash in recovery,i.e.,roms, are put together differently than zip files intended to be installed by the bootloader.

as such,cm10.1 will have to be installed via recovery,and the PH98IMG type files will have to be installed using hboot and the sd card,or fastboot and ruu mode(as described here)

extract a PH98IMG file,such as an ruu. then extract your cm10 rom. youll find that while the rom does contain a boot image that is suitable to pack into a PH98IMG file,that it does NOT contain a system image,it contains install scripts and system files. nor will it have an android info text document,so the cm10 rom zip is not flashable via the bootloader.

Yes, after sending the reply last evening, I UN-zipped an RUU from HTC and a ROM from CM10. They are different

 

[scotty85]

By the way, is there a site you can recommend that will describe adb and fastboot commands. Not just a bunch of examples that are performed by rote -but- someplace that tells a little more about the details of their operation and why. Thanks for your help.

google will find alot of places that list commands and their basic format. unfortunately,ive never see one that lists commands,and gives a noob friendly explanation of exactly what each one does,and give a less confusing example of its usage.

ive basically just been figuring stuff out as i go... theres defiantely alot i do not know about adb and fastboot... so if you come across such a sight,id be interested to see it!

 

[debo19832003]

this seems to be the closest link to the problem i have. i have been reading for over 5hr and i can't seem to get help anywhere. i was in the process of relocking my phone using hasoon2000 all in one toolkit. now my phone says

tampered
relocked
security warning
im currently on S-on RL
hboot 2.25
radio 1.22.10.0421

i was able to lock my phone but its stuck on the white screen and now im not able to use the ph98 file also my computer doesn't recognizing my phone. in the cmd prompt it says device not recognized. can someone plz give me some help..

 

[scotty85]

this seems to be the closest link to the problem i have. i have been reading for over 5hr and i can't seem to get help anywhere. i was in the process of relocking my phone using hasoon2000 all in one toolkit. now my phone says

tampered
relocked
security warning
im currently on S-on RL
hboot 2.25
radio 1.22.10.0421

i was able to lock my phone but its stuck on the white screen and now im not able to use the ph98 file also my computer doesn't recognizing my phone. in the cmd prompt it says device not recognized. can someone plz give me some help..

this is why i dont like toolkits. they dont usually offer much support when things go wrong,and teach you little about what your actually doing if you need to do things manually.

you have 2 options:
1)re-unlock your bootloader. you can use your original token if you still have it. otherwise,you can get a new token.

from here you can restore a backup,or flash a new rom. rference this thread for rom flashing info: http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html

2)run an ruu. on hboot 2.25, you need the this ruu: 3.14.605.12

it can be flashed from a FAT32 firmatted sd card by renaming PH98IMG,place on the root of the sd,and boot to hboot from powered off.

it can also be flashed from fastboot/ruu mode by using the directions in the OP. the following should help you sort your connectivity issues:

troubleshooting connectivity issues:
*make sure you have changed to your adb/fastboot directory!
-try a reboot of the PC
-try different usb cables and ports
-dont use a usb hub
-dont use usb 3.0
-make sure nothing capable of comunicating with the phone is enabled and running. htc sync,pdanet,easy tether,and even itunes have all been known to cause issues.
-windows 8 has been known to have issues. try a windows 7 or older machine

failing the above,
-i use these drivers for fastboot and adb(donwload and run as admin): http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe (mirror)

failing that,try manually updating the drivers in the following manner:
-put the phone in fastboot mode(select fastboot from the hboot menu)
-open device manager on the PC
-plug in phone,watch for it to pop up in device manager.
-update drivers with device manager,pointing the wizard to the extracted
driver download folder from above

note that you can check the connectivity of the phone,and make sure drivers are working by in the following manner:
-open cmd window. change to directory containing adb/fastboot utilities

-adb with the phone in the booted OS,usb debug enabled,enter:
adb devices in a cmd window

-fastboot with phone in fastboot(not hboot!),enter:
fastboot devices in cmd window

in either case,a properly connected phone with working drivers installed should report back the phones serial number.

holler if you have further questions

 

[debo19832003]

im here. thanks for all the info. im still very new to this so im learning all this on the fly. just a few questions. what is a fat32? im currently running a windows 7 64 bit and at all cost if possible i don't want to unlock this bootloader . i came across a file i was told can put me on complete stock.

ota-global-stock- 4.05.605.605.14 710rd-rooted.zip

and otapkg.zip
and does " op" mean other post?? i think the second option may be more helpful. let me try it and see what happens.

make sure you have changed to your adb/fastboot directory!
does this mean go into the cmd prompt and type in "adb fastboot recovery"

m here. thanks for all the info. im still very new to this so im learning all this on the fly. just a few questions. what is a fat32? im currently running a windows 7 64 bit and at all cost if possible i don't want to unlock this bootloader . i came across a file i was told can put me on complete stock.

ota-global-stock- 4.05.605.605.14 710rd-rooted.zip

and otapkg.zip
and does " op" other post?? i think the second option may be more helpful. let me try it and see what happens.

make sure you have changed to your adb/fastboot directory!
does this mean go into the cmd prompt and type in "adb fastboot recovery"
i checked my drivers in device manager and it says to be working properly. also when i went to click on the link a webpage popped up stating that the download is now being blocked....

i ran the cmd prompt and when i tryped in adb devices in the window i received this message. daemon not running. starting it now on port 5037
daemon started successfully
list of devices attached
then i typed in your next heading fastboot devices. this heading came up
c:\users\sony. with a lot of commands here we go..

Ht1a1s224547 fastboot
c:users\sony>fastboot device
usage:fastboot[ <option> ] <command>
commands:
update <filename>
flashall
flash<partition>[ <filename>]
erase <partition>
format <partition>
gervar <variable>
boot <kernel> [<ramdisk>]
flash:raw boot <kernel> [ <ramdisk>]
devices
continue
reboot
reboot-bootloader
help
options:
-w
-u
-s <specific device> -l
-p<product>
-c< cmdline>
-i<vendor id>
-b <base_addr>
-n <page size>
2048
-s <size> [k;m;g]

then i have directions
reflash device from update.zip flashboot + recovery+ system write a file to a flash partition earse a flash partition format a flash partition display a bootloader variable download and boot kernel create bootimage and glash it list all connected devices continue with autoboot rebot device normally reboot device into bootloader show this help message erase userdata and cache < and format if supported by partition type do not first erase partition before formatting specify device serial number or path to device port with "devices lists device paths specify product name override kernel commandline specify a custom usb vendor id specify a custom kernel base address specify the name page size. defaults automatically sparse files greater than size.0 to disable.


that was it. now how does this help me get out of purgatory?

 

[scotty85]

what are your reservations about unlocking the bootloader? unfortunately,an RUU for your build does not exist,so re-unlocking may be your only option.

OP=original post

"make sure you have changed to your adb/fastboot directory!" means that to run commands,you need to be in the directory that contains those utilities. if you have used any of my guides,you use a file called "miniadb" and the directions tell you how to change to it with a command: cd c:\foldername assuming you put the folder onthe root of C

since youve not used any of my guides,and youy used a toolkit to unlock,you may not have such a folder set up use these directions to download and set up the miniadb folder:

first download and install these drivers: revolutionary drivers (mirror)

then,download this small file:
mini-adb.zip

-unzip it,and place the unzipped folder onto the root of your C drive(not inside a folder)

-open a cmd window(with win 7,click start bubble,type "command" or "cmd" in hte search box)

-now change to your mini-adb directory(assuming you didnt chagne the name). type in the black cmd window that opened on your PC:
cd c:\mini-adb

-pull the battery in your phone for a few seconds. hold volume down,then power. hold them both until you see the white/colored writing hboot screen

-select "fastboot" from the hboot menu with the vol rocker/power button

-in your cmd window type:
fastboot devices

it should output your phones serial number. if so youre good to go. if not,youre apparently having a driver issue. i usually recomend these drivers from Revolutionary: modified htc drivers download and install the drivers(you should just have to run that file). afterwards,unplug your phone,plug it back in. make sure its in fastboot. as soon as you get a result from "fastboot devices" your ready to procede to the next step.

-in your cmd window,type(or copy/paste,is much easier):
fastboot getvar all

-copy the info that outputs here. right click in your cmd window,click mark,highlight it all in white. hit enter. paste the info here. it will help us know which ruu for you to run.

onward with your prollem,you cant install the zip youre trying to install.
ota-global-stock- 4.05.605.605.14 710rd-rooted.zip is a rom thats flashed with a custom recovery(twrp,amon,cw)
otapkg.zip is the actual ota that needs the stock recovery to apply. it will only work if youre on a working,official release build older than what you have.

********************************************************

how did your phone come to be in the state that its in?

if it were working and functional,just unlock the bootloader.

from there you can re-install the stock rom and reflash the firmware,wich in the end will leave you stock and relocked

links for the rom and official firmware are found in this thread:http://androidforums.com/rezound-all-things-root/716364-newest-global-rom.html

along with s-on directions to install(post 5) just dont re-unlock at the end,of you wish to stay stock and relocked.

gotta get to work,ill check on you later this evening if you have more questions

 

[scotty85]

any luck?