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
Related
I'm facing problems when updating the radio on my DHD.
Details that appear in the bootloader:
ACE PVT SHIP S-OFF
HBOOT-0.85.0007
Microp-0438
RADIO-26.03.02.15_M3
eMMc-boot
oct 11 2010,12:47:02
When I do a adb devices in command prompt(with phone in normal state and not in boot loader) I do get my device listed in the List of devices attached. However when I boot the device and get into the bootloader then Fastboot(in order to update the radio), here i try adb devices in command prompt and my devices does not appear in the list.
C:\Program Files\Android\android-sdk-windows\tools>adb devices
List of devices attached
I still tried updating the radio
C:\Program Files\Android\android-sdk-windows\tools>fastboot flash radio radio.img
sending 'radio' (24832 KB)... OKAY [ 4.056s]
writing 'radio'... FAILED (remote: not allowed)
finished. total time: 4.056s
Currently I am using CM7-RC0-DHD-PNK20.. could that be the issue. Previously I was able to update the radio successfully when using LeeDrOiD_HD 1.3 but then due some reasons I had to format my PC and reinstalled android SDK..
The radio I'm try to update to is radio_12.28e.60.140fu_26.04.02.17_M2 which I got at LeeDrOiD_HD 1.3 page...
Any help will be greatly appreciated as I understand that the upgraded radio increases the battery life..
Please read this carefully:
http://forum.xda-developers.com/showthread.php?t=896597
You also need ENG S-OFF to flash a radio (you already have Radio S-OFF), and to get that, you need to go back to HTC 1.32 based ROM with preferably stock kernel.
jkoljo said:
Please read this carefully:
http://forum.xda-developers.com/showthread.php?t=896597
You also need ENG S-OFF to flash a radio (you already have Radio S-OFF), and to get that, you need to go back to HTC 1.32 based ROM with preferably stock kernel.
Click to expand...
Click to collapse
jkoljo thanks for the reply.. I kinda had the feeling that I'd have to go back to HTC 1.32 based roms.
Will try this out.
jkoljo said:
Please read this carefully:
http://forum.xda-developers.com/showthread.php?t=896597
You also need ENG S-OFF to flash a radio (you already have Radio S-OFF), and to get that, you need to go back to HTC 1.32 based ROM with preferably stock kernel.
Click to expand...
Click to collapse
if i have radio s-off and using a custom rom, can i just use the tool to get eng s-off? or do i have to do anything special first?
getbacker said:
jkoljo thanks for the reply.. I kinda had the feeling that I'd have to go back to HTC 1.32 based roms.
Will try this out.
Click to expand...
Click to collapse
jkoljo.. i am now using a stock rom and i have done the same as specified in the link u gave me... the details are:
ACE PVT ENG S-OFF
HBOOT-0.85.2007(PD9810000)
Microp-0438
RADIO-26.03.02.15_M3
eMMc-boot
oct 11 2010,12:44:14
I am in the bootloader and still unable to get my devices in the List of devices attached when doing adb devices and in the bootloader it says FASTBOOT USB... any idea what did i do wrong??
How do I flash the radio..?
getbacker said:
jkoljo.. i am now using a stock rom and i have done the same as specified in the link u gave me... the details are:
ACE PVT ENG S-OFF
HBOOT-0.85.2007(PD9810000)
Microp-0438
RADIO-26.03.02.15_M3
eMMc-boot
oct 11 2010,12:44:14
I am in the bootloader and still unable to get my devices in the List of devices attached when doing adb devices and in the bootloader it says FASTBOOT USB... any idea what did i do wrong??
How do I flash the radio..?
Click to expand...
Click to collapse
did you follow exactly the instructions?
1. Download attached Radio flash.zip
2. Extract the folder to anywhere of your choice (MINE IS ON THE DESKTOP)
3. Open the flash folder
4.Download the radio you want to use from the links above .Then Drag and drop radio.img you have downloaded in to radio flash folder
5.In the folder press SHIFT + left click and choose 'Open command prompt window'
6. Type: adb reboot bootloader
The adb reboot bootloader will take the device directly to fastboot
7. Once your phone has rebooted in to bootloader screen type fastboot flash radio radio.img
8. Once it done type fastboot reboot
All done
Because everything is done through your pc
It should not show anything in adb devices while your phone is in the bootloader.
jkoljo said:
It should not show anything in adb devices while your phone is in the bootloader.
Click to expand...
Click to collapse
Just flashed the radio through fastboot.. worked fine. thanks ..
My desire is stuck on fastboot mode,
it is S-OFF
bravo pvt1 ship s-off
riff: 0.93.0001
microp-051d
radio-4.06.00.02_2
Made goldcard, but all the PB99IMG.zip I put on the sdcard are reported as INVALID.
try via fastboot, but I allways get the same error as it wasnt connected.
when I type: fastboot devices I get the device sn but not the $ to keep sending commands so every command I send reports the same error.
try the android flasher, nothing.
used the search button, read a lot but still cannot get the fastboot flash recovery recovery.img to work
run out of ideas, need some help please.
Please specify exactly which error is given when you execute "fastboot flash recovery recovery.img"(recovery.img being your recovery image).
Because if you've got fastboot commands working you should be able to flash.
Do your hboot say alpharev anywhere?
C:\Documents and Settings\Usuario>fastboot devices
HT05PPL02709 fastboot
C:\Documents and Settings\Usuario>cd\sdk
C:\sdk>cd android-sdk-windows
C:\sdk\android-sdk-windows>cd tools
C:\sdk\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (4216 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s
I read this means no proper comunication in fastboot.
it is the clockworkmod recovery and the RA recovery...
both give me the same error... I cannot use any fastboot commmands.
they all end as previously shown.
tryed android flasher 1.8.0, selected recovery.img.... got "could not find part of the path data\recovery.img"
everytime, with every recovery.img I use.
this is all the lines on the hboot screen:
BRAVO PVT1 SHIP S-OFF
RIFF: 0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-4.06.00.02_2
Aug 10 2010,17:52;10
You can flash a recovery with the following command over adb or terminal emulator if your s-off. I know cm7, amonra recovery and rmd recovery support this, others...probably.
su
flash_image recovery /sdcard/recovery.img
I use it all the time.
Sent from my HTC Desire using XDA App
it doesnt work because I am stuck on fastboot.
adb shell do not work for me.
is there anything I should do after "fastboot devices" command?
I am using a xtc clip created goldcard.
should I flash a new hboot or a new radio?
hugmax said:
it doesnt work because I am stuck on fastboot.
adb shell do not work for me.
is there anything I should do after "fastboot devices" command?
I am using a xtc clip created goldcard.
should I flash a new hboot or a new radio?
Click to expand...
Click to collapse
[enter]
fastboot flash radio radio.img [enter] {wait the ok message}
fastboot reboot-bootloader [enter] {wait the reboot}
fastboot flash recovery recovery.img [enter] {wait the ok message}
fastboot reboot-bootloader [enter] {unplug the cable and wait the reboot}
from the bootloader menu go into recovery and flash the rom u want
ensure the img file are in the same directory of fastboot.exe
how u got s-off? with alpharev or an xtc clip? the xtc clip doesn't give u fastboot flash commands i think, then u should try run revolutionary.io i think, after u can flash recovery etc
s-off via xtc-clip.
will try the commands... should I pick any radio.img?
hugmax said:
s-off via xtc-clip.
will try the commands... should I pick any radio.img?
Click to expand...
Click to collapse
first run revolutionary, it will give u a patched s-offed hboot..this hboot will allow commands like "fastboot flash..."
about the radio, u can use the latest in this thread (extract the img from the zip) be careful flashing it..wait it to finish..don't remove battery or something like that
if I run revolutionary all I get is "waiting for device"
D:\Docs\Celulares\htc\desire\revolutionary-0.4pre4>revolutionary
=============================================
| Revolutionary S-OFF & Recovery Tool 0.4pre4 |
=============================================
Brought to you by AlphaRev & unrEVOked.
Waiting for device...
Click to expand...
Click to collapse
if I am stuck on fastboot and xtc clip doesnt allow any fastboot command... and unrevoke/revolutionary dont recognize my fastboot device...
what am I suppose to do now?
I get FAILED(status malformed.... ) with every single fastboot command.
hugmax said:
if I run revolutionary all I get is "waiting for device"
Click to expand...
Click to collapse
uninstall htc synch at all, and other programs that can interferr
install this fastboot drivers
run revolutionary, plug the phone in fastboot mode
Have you try to unroot with a PB99IMG?
Sent from my rooted and s-offed HTC Desire.
andQlimax said:
uninstall htc synch at all, and other programs that can interferr
install this fastboot drivers
run revolutionary, plug the phone in fastboot mode
Click to expand...
Click to collapse
I installed the drivers, it says
Android Composite ADB Device
version 2.0.10.12
date: 11/08/2009
Shouldnt it says 3.0?
anyway... it didnt work... I will try to delete/uninstall everysingle htc driver in my pc or try on another fresh laptop with no htc drivers.
Again here,
new pc, Windows XP SP3 with no HTC/Android software.
Intalled the HTC 3.0 and the phone was not recognized
should I try on win7?
that is going to be my next test
follow up: tryed on win7, htc 3.0.0 drivers didnt work. phone is not recognized.
I know it was working fine... tryed to flash it and it died... resurrected with RIFF Box but cannot flashed with any firmware.
i tried to flash a new hboot with android flasher, but it just reboot and nothing happened.
did you check md5 sum btw? just with the error saying invalid and 1 byte...
So you can still access fastboot but cant flash? hmmm...
I would personally delete all your android sdk and redownload it all and set up adb fastboot again, it does sound like a driver problem
timothio said:
i tried to flash a new hboot with android flasher, but it just reboot and nothing happened.
Click to expand...
Click to collapse
What did you expect? Its requires few seconds to flash it..If u saw the success message and u see the new hboot on the bootloader screen, thats all
ok,
now I went to find a PB99IMG.zip with the same radio.
copied it to the sd
power on the phone
and I got this:
Uploaded with ImageShack.us
but it is just sitting there, waiting for something to happen?
I tryed to select something but it doesnt respond to anything... can it be that the touch screen is faulty? because it was working at the beginning.
I did redownload everything again.
java sdk and everything
it doesnt work with the htc 3.0 driver, only with 2.0
Hi guys,
A good friend of mine recently requested me to help with rooting her Wildfire S A510e (purchased from SingTel, CID HTC__044). I managed to change her Wildfire S from S-ON to S-OFF via HTCdev. As far as I know, HTCdev isn't supposed to give you S-OFF but only to remove the NAND write locks on certain partitions.
Users: This is NOT for you. This is NOT a tutorial.I will not be responsible for any bricked WFS.
Here's what happened, pretty long so I'm gonna break it down into multiple sections. Important points in red.
Replacing SingTel ROM with HTC EU ROM
The phone was originally running Android 2.3.3, ROM version 1.35.707.1, HBOOT 0.90.0000. This ROM version is not supported by HTCdev unlock yet.
Reboot to HBOOT on WFS. Choose FASTBOOT.
Connect WFS to computer via USB.
Downloaded the HBOOT RUU for "hTC Asia India" from HTCdev. Attempted to install the RUU but got a CID error.
Disconnected WFS from computer.
Rebooted normally on WFS.
Connect WFS to computer via USB (Disk Drive).
Created a goldcard by using SimpleGoldCard while WFS is mounted as Disk Drive. (this wipes your SD card)
Disconnect WFS from computer and reboot.
Connect WFS to computer via USB (Disk Drive).
Downloaded RUU_Marvel_S_HTC_Europe_2.13.401.2
Ran the RUU. Went into %temp%, found the relevant directory and copied rom.zip to the goldcard as PG76IMG.zip.
Disconnect WFS from computer.
Turn off WFS and rebooted into HBOOT.
Went into HBOOT -> Fastboot. RUU_Marvel_S_HTC_Europe_2.13.401.2 was installed successfully (Android 2.3.5, ROM version 2.13.401.2, HBOOT 0.90.0000).
Installing HTCdev Unlock
Rebooted WFS into HBOOT.
Connect WFS to computer via USB.
Downloaded the HBOOT RUU from HTCdev for "HTC EU".
Ran the HBOOT RUU. RUU installation gets stuck at 50% ("Flushing radio...") for about 20 minutes.
Decided that the RUU has hung so disconnected WFS from USB and did a battery pull
RUU offered to do a recovery but I clicked "Exit".
Turn on WFS in HBOOT mode.
S-OFF obtained!
I was pretty much at "dafuq?" at this stage. I didn't even need to upload the device identifier to HTCdev to get an unlock key. The device was already S-OFF (HBOOT shows it)!
HBOOT remained at 0.90.0000.
I verified the S-OFF by flashing ClockWorkMod which went without issues.
Possible theory of operation: (just my thoughts)
The HTCdev HBOOT RUU provides a temporary S-OFF in order to unlock the NAND
When the RUU is done, it is supposed to restore S-ON to the device.
However, since the process was hung, the RUU had no chance of restoring the device to S-ON.
Hence the WFS was left at S-OFF.
If there are any adventurous devs around who are willing to try to dissect the RUU, please do so, but standard disclaimer applies. Attempting to interrupt the HBOOT RUU flashing is pretty dangerous and WILL possibly brick your device! I will not be held responsible if you brick your WFS!
This seems to be a case of pure luck.
Addendum:
The HBOOT RUU contains 2 ZIP files: rom_01.zip, rom_02.zip
They are presumably flashed in-order.
rom_01.zip contains Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.08M_Signed_20111208.img
rom_02.zip contains hboot_1.08.0099_6e20b6fac09.nb0 and radio_47.23a.35.3035H_7.53.39.03M_MR.img
My friend has radio version 47.23b.35.3035_7.54.39.08M. From here, we can tell that rom_01.zip was successfully flashed but rom_02.zip wasn't. Also notice the "special" file name of the first radio image.
Addendum 2:
It appears that both radio ROMs have the same size but different md5sum. Can someone with S-ON try to flash Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.08M_Signed_20111208.img? (Again, standard disclaimer applies)
i like the very last sentence that you used ...
good job anyway mate !
how do you go about flashing a radio??
---------- Post added at 04:12 AM ---------- Previous post was at 04:09 AM ----------
rom1.zip is 10.370.252
rom2.zip is 10.586.425
ie not the same size
stevie67 said:
rom1.zip is 10.370.252
rom2.zip is 10.586.425
ie not the same size
Click to expand...
Click to collapse
If you look into the ZIP files, Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.08M_Signed_20111208.img and radio_47.23a.35.3035H_7.53.39.03M_MR.img are both the same size.
Reboot to HBOOT, choose FASTBOOT, connect WFS to computer. Use "fastboot flash radio Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.08M_Signed_20111208.img".
ok i tried to flash this radio i put the .img file on my sdcard went to fastboot then recovery,install from sdcard and there was nothing there so i put the rom1.zip folder on my sdcard went to fastboot,install from sdcard,rom1.zip and got this
CWM-based Recovery v5.0.2.6
-- Installing: /sdcard/rom_01.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/rom_01.zip
(bad)
Installation aborted
did i do something wrong??
You must flash the radio with fastboot command. But this wont work, bc the hboot will check if the file is signed. And that isn't.
But try, maybe i'm not right.
Sent from my HTC Wildfire S A510e using XDA App
and the fastboot command is??
and the file says its signed
Reboot to HBOOT, choose FASTBOOT, connect WFS to computer. Use "fastboot flash radio Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.08M_Signed_20111208.img".
Click to expand...
Click to collapse
He said it
Sent from my HTC Wildfire S A510e using XDA App
My phone wouldn't update using the HTC method so I extracted the two ROMs from the RUU and flashed them seperately. After the first one (radio) I noticed that the phone was S-OFF but when I'd flashed the second it was S-ON again and I couldn't go back.
WOW, you have S-OFF after flashing radio via
fastboot flash radio radio.img
???
And now you can't go back?
I extracted the htcdev ruu and tried to flash the radio image. but it is not possible, signature check fails. so if the bootloader is already unlocked, it is not possible to obtain s-off this way
Have u test it with
fastboot oem lock
first and then to flash the radio.img?
Or to try to downfrade hnoot with the tutorial here in forum and then flash the new radio.
not yet. Will try that and report again
did relock phone using oem lock.
*** RELOCKED ***
Tried flashing 1st radio from htcdev ruu
flashing successful, but still S-ON
Hmm, and can u try to downgrade to Hboot 0.9 or Hboot 1.08?
I'm a noob so it's possible I made a mistake but I'm pretty sure I was S-OFF after the first flash. I was on Hboot 0.09.0000. Unfortunately I didn't realise the significance at the time so proceeded anyway.
I will try
I will try too, but earliest tomorrow, then i have my windows pc
this is what i get with or without bootloader locked
C:\Android>fastboot flash radio Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.0
8M_Signed_20111208.img
sending 'radio' (23936 KB)...
OKAY [ 5.375s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 13.063s
stevie67 said:
this is what i get with or without bootloader locked
C:\Android>fastboot flash radio Radio_special_MARVEL_MR_47.23b.35.3035_7.54.39.0
8M_Signed_20111208.img
sending 'radio' (23936 KB)...
OKAY [ 5.375s]
writing 'radio'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 13.063s
Click to expand...
Click to collapse
I extracted the rom1.zip and renamed it PG76IMG.zip and flashed via hboot. this worked when the phone was re-locked
theq86 said:
I extracted the rom1.zip and renamed it PG76IMG.zip and flashed via hboot. this worked when the phone was re-locked
Click to expand...
Click to collapse
so are you now s-off??
Sorry for my pour English!
I am a Chinese , and in China there are some htc phones were locked in hboot by some speculators. They use xtc-clip unlock the official hboot so we can see it shows s-off and cid is 11111111 , then they flash a modified hboot designed by themselves so that we can not flash any RUU and PG76IMG.zip with this modified hboot. We call this phone is Trojan phone or virus phone.
I have two ideas to solve this problem. One is flash CWM recovery so I can flash rom in recovery mode , but it's not a perfact method. The other is to flash back to official hboot so I can flash RUU and PG76IMG.zip.But it is impossible to flash stock hboot in modified hboot mode, it doesn't work.
Maybe some of you guys know, if we have root permission when we load system use ADB SHELL, then we can use dd command to recover hboot just like
Desire HD("dd if=/data/local/tmp/hboot_7230_Ace_0.85.0024_110411.nb0 of=/dev/block/mmcblk0p18"), "/dev/block/mmcblk0p18" is the hboot partition mount point in Desire HD.
Now the problem is I can't find the hboot partition mount point in G13. Could anyone tell me the mount point or how to get the hboot partition address in nand flash ?
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: