Related
I tried to flash a new splash using android flasher 1.6.1 and it didn't worked out.
I tried to do it using ADB and it's write to me :
sending 'splash1' (750KB)...
OKAY [0.118s]
writing 'splash1'...
FAILED (remote:not allowed)
finished.total time 0.119s
I am using Cyanogen7 ROM and I have S-OFF :
BRAVO PV4 SHIP S-OFF
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-5.09.05.30_2
Can please someone help me ?
fastboot flash?
ghalalb said:
fastboot flash?
Click to expand...
Click to collapse
yes
Im trying to change the splash picture.
sorry, I should have explained myself, have you flashed from fastboot or adb only? I'm sure you have to do it from fastboot not adb, there is a tut on here somewhere, but i can't find the link for it
could try this method though i've not
http://forum.xda-developers.com/showthread.php?t=794638
AmonRa 2.0.1 | PVT4 40000 S-Off Alpharev 1.8| HBoot 0.93.1000 | Radio 5.17.05.08 | LeeDroid 3.0.2 (A2SD) | HTC Desire A8181 | UOT Kitchen Mods
found the method I used
http://forum.xda-developers.com/showthread.php?t=795132&highlight=fastboot+flash+splash1
AmonRa 2.0.1 | PVT4 40000 S-Off Alpharev 1.8| HBoot 0.93.1000 | Radio 5.17.05.08 | LeeDroid 3.0.2 (A2SD) | HTC Desire A8181 | UOT Kitchen Mods
That method worked for me too, nice
I tried to do it with fastboot ,still don't work for me.
it says it's all done but nothing happends.
I also tried to do the S-OFF again and it give me the next error:
waiting for your device... FOUND!
Identifying your phone:
Device model: PB992
CID: 11111111
MID: PB992
HBOOT version: 0.93.0001
Screen type:
Your phone was not recognized or is unsupported at this time.
If you are 100% sure your phone type should be supported in this version,please note the Model ID displayed.
Powering off in 60 seconds.
I dont understand what's wrong ?
I use android flasher. Its damn easy for noobs. I'm not a noob, but I'm lazy enough to use it.
I have also tried with Android Flasher but still doesn't work...
kleinyair said:
I tried to do it with fastboot ,still don't work for me.
it says it's all done but nothing happends.
I also tried to do the S-OFF again and it give me the next error:
waiting for your device... FOUND!
Identifying your phone:
Device model: PB992
CID: 11111111
MID: PB992
HBOOT version: 0.93.0001
Screen type:
Your phone was not recognized or is unsupported at this time.
If you are 100% sure your phone type should be supported in this version,please note the Model ID displayed.
Powering off in 60 seconds.
I dont understand what's wrong ?
Click to expand...
Click to collapse
I think, you should write this problem on irc.freenode.net, channel #alpharev
Don't know what's the problem, but think the guys from alpharev-team could help here...
Sent from my HTC Desire using XDA App
anderl78 said:
I think, you should write this problem on irc.freenode.net, channel #alpharev
Don't know what's the problem, but think the guys from alpharev-team could help here...
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
How do I use the IRC ?
I tried to write it in my exlorer,didn't go nowhere.
I'm sorry I'm quite new here.
And your fastboot/hboot does say something like aplpharev on the top? If that is the case it will also work if you do it right when booted into fastboot. I might be able to guide you through it.
If that is not the case, something is wrong, and you will need to run alpharev again.
I also dont get how your cid can be 11111111, as that definitely does not look right. Try booting to fastboot and run "fastboot oem boot" and write the cid it throws out it should be something like HTC_Y13
mortenmhp said:
And your fastboot/hboot does say something like aplpharev on the top? If that is the case it will also work if you do it right when booted into fastboot. I might be able to guide you through it.
If that is not the case, something is wrong, and you will need to run alpharev again.
I also dont get how your cid can be 11111111, as that definitely does not look right. Try booting to fastboot and run "fastboot oem boot" and write the cid it throws out it should be something like HTC_Y13
Click to expand...
Click to collapse
My hboot doesn't say nothing about alpharev i got it allready s-off from the store,thats what it write on my hboot:
BRAVO PV4 SHIP S-OFF
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-5.11.05.14
I run fastboot oem boot and this is the reasult:
I will very appreciate if you could please help me.
Try the alpha rev s-off method (bootcd) then try again with the gui tool
isit-LoVe said:
Try the alpha rev s-off method (bootcd) then try again with the gui tool
Click to expand...
Click to collapse
I have allready tried with alpharev bootcd and it gave me:
waiting for your device... FOUND!
Identifying your phone:
Device model: PB992
CID: 11111111
MID: PB992
HBOOT version: 0.93.0001
Screen type:
Your phone was not recognized or is unsupported at this time.
If you are 100% sure your phone type should be supported in this version,please note the Model ID displayed.
Powering off in 60 seconds.
what do you mean gui tool ?
seems like your phone uses an alternative s-off method or its just faking S-OFF (only displaying it on screen)
i googled for about 15 mins and found this: http://4pda.ru/forum/index.php?showtopic=180832&st=12640#entry6668455
use google language translator for other language
When you try to get the S-OFF:
identifying your phone:
Device model: PB992
CID: 11111111
MID: PB992
HBOOT VERSION: 0.93.0001
SCREEN TYPE:
Your phone was not recognized or is unsuported at this time.
Have:
BRAVO PVT4 SHIP S-OFF
HBOOT-0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.14.05.17
Aug 10, 2010 17:52:18
Telephone gray, root mean.
Beat 3 months, finally found the solution:
when alpharev gives Your phone was not recognized or is unsuported at this time.
disable the phone from the wire
Hit Ctrl + C
see $
write vi alpharev.sh Hit Enter
cursor down to 117 lines, where it is written PB9920000 remove zeros that would get PB992
Hit Shift colon and write wq
see $
write. / alpharev.sh
process will start again on the instructions of obtaining s-off
ps. sewed with flash
Click to expand...
Click to collapse
gui tool i mean android flasher but after you successfully flashed with alpha rev :/
I tried the process,I changed the PB9920000 to PB992 but I dont understand what is that mean :"Hit Shift colon and write wq"
what is shift colon ?
Edit :O.K I figured it out !!!!
after I changed the num to PB992 I pushed Shift+Z
and I wrote :" ./ alpharev.sh "and Enter
It start all over from the begining and its all working good now.
Thank you very much...
His phone is s-off alright, but it has somehow been delivered that way, so you have got a phone, which were meant for development or a store demo device(have seen the same issue on store demo devices).
The problem is, that this is real s-off, which means it's set by a flag on a low level of the nand, so he still has the original bootloader, which doesn't support fastboot commands. And because it's a development device it's got cid 11111111, which is wrong and makes alpharev recognize it as a different/non existing device. You should be able to flash it in another way because as you are s-off, you can make the recovery ask the bootloader to flash low level stuff like splash, and the bootloader is s-off, so it shouldn't check for anything. You might need some specialist aka the ones from alpharev though if they are interested in helping you.
edit: As it is s-off it might very well be able to flash one of the pb99img.zip files containing the alpharev hboot found on the alpharev site because it will accept them as if they were from HTC, so just put them on the sd-card with the right name and reboot to the bootloader. This way you might be able to activate fastboot commands, and start flashing the same way we do. This requires that those images will work normally on your phone, so i would still ask the alpharev guys so you don't risk a brick.
i agree with mortenmhp asking alpharev is probably the best idea
shift colon is probably :
in the editor vi you use ":wq" to tell the programm to save stuff and exit the editor
How can I make contact with alpharev ?
I didn't understant how to use the IRC...
C:\Users\Gil\Desktop\Radio flash>c:\windows\system32\cmd.exe
Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Gil\Desktop\Radio flash>fastboot flash radio radio.img
sending 'radio' (24960 KB)... OKAY [ 4.110s]
writing 'radio'... FAILED (remote: not allowed)
finished. total time: 4.111s
C:\Users\Gil\Desktop\Radio flash>
it says REMOTE NOT ALOUD..can any one help me and i'm doing for CoreDriod 2.3.3 v5 on a desire HD
Hi there, Do you have S-OFF? If not you can view jkoljo's thread here for details on how to do this http://forum.xda-developers.com/showthread.php?t=857537
you need S-OFF to flash radio
hello
i have the same problem, but @ my htc if run Leedroid 3.0.3 and i what the flash a new radio.
i already done the process with goldcard and s-off, but i can't flash radio right now.
plz help
question: if i have normaly a branding device, i knew the i need a goldcard but i need it the whole time or only one time? Because i changed my sd card XD
Read post numbers 2 & 3. Then follow the link in post 2. Use the tool in that thread.
andyharney said:
Read post numbers 2 & 3. Then follow the link in post 2. Use the tool in that thread.
Click to expand...
Click to collapse
???
I have done the process with S-off, but i got the same problem link post 1.
on my device is fastboot and in my bootloader are stand:
ACE PVT ENG S-OFF and in systeminfo the CID is 11111111
now my question was if i need the whole time a goldcard => because my new sd card isn't a goldcard
and if i run the radio s-off tool in the link of post 2 => i got an error message "Unknown error, probably connection" => and wifi on doesn't fix the problem
if your gettign an eror in connection i had the same issue and hasd to upgrade my framework on my pc.... all now works sweet
writing 'radio'... FAILED (remote: not allowed)
Click to expand...
Click to collapse
That indicates the remote part of the process, i.e your handset, is not allowing the radio to be written.
So to confirm you have ENG S-OFF and Radio S-OFF? If you have I would recommend using jkoljo's tool again. Put Radio S-OFF back to ON, reboot, then turn is OFF again.
check the MD5 of the image you have dl form the server, it can be bad...
andyharney said:
That indicates the remote part of the process, i.e your handset, is not allowing the radio to be written.
So to confirm you have ENG S-OFF and Radio S-OFF? If you have I would recommend using jkoljo's tool again. Put Radio S-OFF back to ON, reboot, then turn is OFF again.
Click to expand...
Click to collapse
I think i have both of this (Radio S-Off and Eng S-Off) because i did the process to debranding my smartphone after buy, i always change micro sd card => my new micro sd card isn't a goldcard.
when i comes from work, i've trying to set Radio S-on + restart and after this i set it agian to Radio S-Off
Edit:
so now it's working => i've tested it on an other system, i use only EasyS-off again and now i can flash radio versions, maybe it's a driverproblem on my nootbook
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??
PHONE INFO:
-------------------------------------------------------------
HTC Wildfire S A510b
Android version
2.3.5
HTC Sense ver.
2.1
Build No
2.26.841.4
Kernel
2.6.35.10-ga9ceb63
Baseband
47.10.35.3029H_7.46.35.08
Marvel PVT SHIP S-ON RL
HBOOT-0.90.0000
MICROP-0451
RADIO-7.46.35.08
APR 8 2011M 17:45:10
-------------------------------------------------------------
Symptoms: Wi-fi stopped working (can't be turned on - error ) and all the icons and UI elements are filckering at times.
"Factory Reset" didn't work...
Had the idea to re-install the stock rom but didn't know how and couldn't find the right one on androidruu.com
Now considering a CM mod or something better if you can recommend for htc WFS if a stock can't be found.
While trying the "HTC Easy Unlock Bootloader Tool" (tried to install CM 10.1 for htc WFS) another problem occurred. When I came to the part when it puts the phone in HBOOT and I press any key ... in the cmd like "HTC Easy Unlock Bootloader Tool" it says:
Obtaining Unlock Token
... INFO[ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.008s
Now copy the identifier token as shown here (use the right button of the mouse to choose mark and then press right button again to select) then paste the token at the botton of the page and submit. Opening HTVDEV site
Press any key to continue . . .
What to do people ? Help if you can. :crying:
Doesn't anyone know anything about this???
By googling, have found out that hboot 0.90 may not support "fastboot oem get_identifier_token" command
which is only logical after receiving "command error" in return.
So does anyone know how to update HBOOT from 0.90 to 1.09 ???? I tried from RUUs and PGs with no success.
Tried these (Phone is Next G, Telestra):
From Win7
1. RUU_Marvel_HTC_Europe_1.33.401.2_Radio_47.10.35.3029H_7.46.35.08_release_185724_signed
2. PG7612000_Marvel_hboot_1.09.0099_1.52.841.1_1.52.841.2_0214 (i.imgur.com/7NqUW2f.jpg)
nothing worked....
Extracted rom.zip and tried from sdcard:
1. This one has the same HBOOT version so nothing happened
2. This one couldn't do it because of image version difference
(It has 2 rom.zip files, rom_01.zip and rom_02.zip. Tried with renaming rom_02.zip to PG76IMG.zip because it contains newer ver. of HBOOT.)
still... nothing happened...
HELP, getting desperate here
My HTC wildfire touch don't work after downgrade from 2.34.186.1 to from 2.34.186.1.
The branding ist 1und1. After this i try to find the original OTA 2.34.186.1 to upgrade
to the old one that was on the phone before. - no way - i don't found
After this i unlocked the bootloader and i think that there is a way to upgrade any firmware
but its not possible.
My bootscreen:
*** UNLOCKED ***
BUZZ PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0622
RADIO-3.35.15.31
Dec 13 2011,12:08:54
The HTC boot normaly to the lock screen but the touch don't work.
Anyone an idea to solve my problem an install another rom?
Here is another thread that discusses a similar issue.
Hope it'll help.
http://forum.xda-developers.com/showthread.php?t=1056767
Sent from my G9 using Tapatalk
Pretendde said:
My HTC wildfire touch don't work after downgrade from 2.34.186.1 to from 2.34.186.1.
The branding ist 1und1. After this i try to find the original OTA 2.34.186.1 to upgrade
to the old one that was on the phone before. - no way - i don't found
After this i unlocked the bootloader and i think that there is a way to upgrade any firmware
but its not possible.
My bootscreen:
*** UNLOCKED ***
BUZZ PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0622
RADIO-3.35.15.31
Dec 13 2011,12:08:54
The HTC boot normaly to the lock screen but the touch don't work.
Anyone an idea to solve my problem an install another rom?
Click to expand...
Click to collapse
Hmmm. This is going to be hard to get out of as you upgraded your Hboot. Does the phone still register fastboot commands? Also what downgrade thread did you follow?
Sent from my HTC Sensation using Tapatalk
It dont work at update with ruu shows the version 2.46.0.0 of the divece rom....
The update prozess stops and there is " FEHLER [155] : ABBILD-UPDATE-FEHLER " (IMAGE UPDATE ERROR)
The same with the PC49IMG.zip on microsd card:
RUU
Security fail!
Update Fail!
Pretendde said:
It dont work at update with ruu shows the version 2.46.0.0 of the divece rom....
The update prozess stops and there is " FEHLER [155] : ABBILD-UPDATE-FEHLER " (IMAGE UPDATE ERROR)
The same with the PC49IMG.zip on microsd card:
RUU
Security fail!
Update Fail!
Click to expand...
Click to collapse
That's not what I mean, to unlock your bootloader you would have had to issue the command fastboot OEM unlock, or fastboot flash OEM unlock unlock_token.bin or something similar. These types of commands are the ones I'm interested in I want to see if you can flash clockworkmod recovery pal.
Sent from my HTC Sensation using Tapatalk
I downgraded with the standard buzzdowngrade.zip package, step1 but the goldcard-step fail.....i flashed after hboot downgrade RUU_Buzz_Vodafone_DE_1und1_1.19.186.3_Radio_13.45.55.24_3.35.15.31_release_133745_signed.exe
Than was the problem with the touch ... it dont work.
After this i tryed many ruu's ....no way.
Than i downloaded from htcdev - PC4910000_Buzz_Froyo_hboot_1.02.0000_R3.exe and flashed and unlocked with Unlock_code.bin
I was thinking i would be able to unlock and update every rom
Pretendde said:
I downgraded with the standard buzzdowngrade.zip package, step1 but the goldcard-step fail.....i flashed after hboot downgrade RUU_Buzz_Vodafone_DE_1und1_1.19.186.3_Radio_13.45.55.24_3.35.15.31_release_133745_signed.exe
Than was the problem with the touch ... it dont work.
After this i tryed many ruu's ....no way.
Than i downloaded from htcdev - PC4910000_Buzz_Froyo_hboot_1.02.0000_R3.exe and flashed and unlocked with Unlock_code.bin
I was thinking i would be able to unlock and update every rom
Click to expand...
Click to collapse
Ok so fastboot works, good good. Do you have clockworkmod recovery installed? If not follow my thread for rooting hboot 1.02.0000 and install clockworkmod but go no further.
Also just for your information the ruu will not install because of
1. Your honor is higher than the ones in the RUU,
2 your bootloader is unlocked.
We need to downgrade you to the WWE rom with hboot 1.01.0001 and hopefully that will restore your touch panel to working order
Sent from my HTC Sensation using Tapatalk
Clockworkmod recovery is installed, rooting hboot 1.02.0000 o.k.
and now?
Pretendde said:
Clockworkmod recovery is installed, rooting hboot 1.02.0000 o.k.
and now?
Click to expand...
Click to collapse
ok so what we want to do know is downgrade your hboot to 1.01.0001 so to do that we need your misc partition to be edited. as such i would like you to boot the phone into clockworkmod recovery and connect it to the pc with a usb cable. windows should install the drivers if it has not done so already.
next you will need to set up your command prompt for using adb/fastboot commands.
then we will pull a copy of your misc partition to your sdcard and then copy it into your windows adb folder.
then you will upload that image to me, i will make the necessary changes and then re-upload for you.
then you will flash it to the phone all going well, re-lock your bootloader and then downgrade your hboot and rom and hopefully regain touch input
then as an extra if you want to use a rooted version of that german ruu you were trying to flash i can make you a "safe to flash" version
ok, so....
step 1. Connect your wildfire up to your pc In clockworkmod recovery mode.
step 2. open a command prompt within your adb/fastboot folder. (the same one you used to flash clockworkmod recovery)
step 3. enter the following commands one at a time. copy paste is recommended.
Code:
adb shell
su
cat /dev/mtd/mtd0 > /sdcard/misc.img
exit
exit
adb pull /sdcard/misc.img misc.img
step 4. Upload this file to somewhere like dropbox or media fire and then send me a link to it.
in command prompt
su
/sbin/sh: su: not found
what i do wrong?
Pretendde said:
in command prompt
su
/sbin/sh: su: not found
what i do wrong?
Click to expand...
Click to collapse
OK just skip that and move onto the next bit.
Sent from my Nexus 7 using Tapatalk
I attached this file here, i hope it is o.k.
It takes a while until i found out to mount the SD card before
Pretendde said:
I attached this file here, i hope it is o.k.
It takes a while until i found out to mount the SD card before
Click to expand...
Click to collapse
okey dokey, here is your new misc image. extract it into your adb folder.
i have edited this so it will re-lock your bootloader automatically once you have flashed it. one problem solved
also download this package, it has some tools you will need and the WWE rom you need to flash
lastly we need to make a goldcard. this will be hard given that your touch screen is non-functional. as such you will need a different, working android phone and YOUR sdcard. this trick is sdcard specific so dont swap them about
ok once you are ready with the right stuff, do these steps.
step 5. now we need to make a gold card. if you already have one, you can skip this part. first using your working android phone, download and install Goldcard helper from the android market. Run the app and copy down your SD cards reverse cid. double check it
step 6. now go to this website here and enter in your reverse cid. it will then let you download a goldcard.img.
step 7. now go back to the package you downloaded earlier with the WWE rom (named 1.01.zip) in it and run the goldcardtool.exe, this will flash the goldcard to your sd card. Warning! this will format your card!! in order to achieve this you will have to mount the sdcard from clockworkmod recovery to the computer, use mount usb storage and not mount sdcard.
step 8. once that is done we are now ready for the final push
Now the gold card is ready, i leave al the data on the goldcard, its not been formatted. Goldcard tool says, G: Goldcard is now ready.
The new misc image, must be copy to the phone ?
Pretendde said:
Now the gold card is ready, i leave al the data on the goldcard, its not been formatted. Goldcard tool says, G: Goldcard is now ready.
The new misc image, must be copy to the phone ?
Click to expand...
Click to collapse
ok from here copy the Nmisc.img to your sdcard and do not rename it, leave it on the sd card within no folders.
then connect up the phone in clockworkmod recovery again, and mount the sdcard with mount sdcard and not usb mass storage.
lastly make sure that the 1.01.zip is in your adb folder.
issue the following commands.
Code:
adb shell
(your shell symbol should be a #)
flash_image misc /sdcard/Nmisc.img
exit
(now it should not be a #)
adb reboot bootloader
The phone should not reboot into bootloader and should say at the top locked OOW.
This is ok, if it does not say this then your misc image was not flashed.
if all is well issue these commands.
Code:
fastboot oem rebootRUU
fastboot flash zip 1.01.zip
This will state an error, and that it needs to be reflushed. this is what we want, if any other issue your goldcard may have failed.
repeat the last command to reflush.
Code:
fastboot flash zip 1.01.zip
(this will take a while.)
fastboot reboot
the phone should reboot into the WWE stock rom and hopefully your touch screen will be working again. if it is proceed to s-off with revolutionary here ignore all but revolutionary and then if you want the german ruu as a safe flash rom send me a link to the ruu and I will make it. but it make take a few days.
im at work atm so my replys will be delayed pal, good luck
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 63.656s
i flashed 3 times....
Pretendde said:
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
FAILED (remote: 42 custom id check fail)
finished. total time: 63.656s
i flashed 3 times....
Click to expand...
Click to collapse
Your gold card has failed. Format the sdcard and then reissue the fastboot commands.
Sent from my HTC Sensation using Tapatalk
Yes the goldcard was bad, now its okay but n ow a new error :
INFOsignature checking...
FAILED (remote: not allowed)
finished. total time: 56.078s
flashed 5 times ...same error
Pretendde said:
Yes the goldcard was bad, now its okay but n ow a new error :
INFOsignature checking...
FAILED (remote: not allowed)
finished. total time: 56.078s
flashed 5 times ...same error
Click to expand...
Click to collapse
Does your bootloader still say locked?
Sent from my HTC Sensation using Tapatalk
heavy_metal_man said:
does your bootloader still say locked?
Sent from my htc sensation using tapatalk
Click to expand...
Click to collapse
yes
*** locked (00w) ***