Related
After a Update failure my Desire isn’t feeling to good...
I was running oxygen-2.1.6 on my Desire but decided to go back to stock. BAD choice!
Now when power on I get the black htc screen with the triangles in the corners. When I try volume down + power on I get the same black screen.
If I start the RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe again to do the same update I get ERROR [152]:IMAGE UPDATE ERROR with the option to Recover which gives me a black screen until I pull the USB connection. Then I get a fastboot lock a like screen.
AlphaRev CM7 r2
BRAVO PVT3 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNW0101
RADIO-4.06.00.002_2
Aug 10 2010, 17:52:18
RUU
[1] BOOT - OK
[2] BOOTLOADER - Bypassed
[3] RADIO_v2 - OK
[4] RADIO_CUST -OK
[5] RECOVERY - OK
[6] SPLASH1 - OK
[7] SYSTEM - Fail-PU
[8] USERDATA - OK
Partition update fail!
Update Fail!
I’ve tried many of the other RUU but they all results in ERROR [110]: FILE OPEN ERROR […] Click ‘Exit’ to quit
How do I get past this?
Have no goldcard...
All I want is my phone up and running again…
Any solution out there?
//Tommy
Everything is fine except you can't RUU over the hboot you have as /system is too small for the Rom.
You need bravo stock. You need to either fastboot flash the downgrader from alpharev and run the RUUagain or fast boot flash a recovery img and restore a nandroid backup
Sent from my HTC Desire using XDA App
Yep downgrade the hboot first from AlphaRev website then continue.
Swyped...
Ok no!! Do not flash the downgrader just yet!! Flash the stock alpharev hboot but not the downgrader, otherwise that will put you s-on when you flash the RUU and if something goes wrong you wont have s-off to help. So as I said just flash the stock hboot, restart and then try the RUU again. Sorry it feels like I'm hanging my ass over the ragged edge when I'm S-ON
bortak said:
Ok no!! Do not flash the downgrader just yet!! Flash the stock alpharev hboot but not the downgrader, otherwise that will put you s-on when you flash the RUU and if something goes wrong you wont have s-off to help. So as I said just flash the stock hboot, restart and then try the RUU again. Sorry it feels like I'm hanging my ass over the ragged edge when I'm S-ON
Click to expand...
Click to collapse
Sounds great but how do I do that?
My phone is as I said not responding to vol. down + power for the bootloader or the back + power for fastboot. Black htc screen with the triangles in the corners on both cases. I can’t flash anything from my phone (that I know off) since I can’t get to the fastboot or the bootloader. How do I use the .img file from alpharev.nl? I don’t know how to run the PB99IMG from my phone as it is now.
I’ve tried to run the alpharev cd again but with no luck.
“Waiting for your device… hub 2-0:1.0: unable to enumerate USB device on port [number of the USB port]”
My computer recons the phone, or at least that it’s an Android 1.0 device, when I’m in windows (both win 7 and XP) so can I do anything from there?
try download Android flasher 1.8 in dev.section
after that try to flash CWM recovery 3.0.0.5 and alsom try to flash stock Hboot
all these steps via android flasher can be done
edit - you can run alpharev but only with stock rom and hboot
in other way rooted phone with custom rom wont work with alpharev, there is also recommendation on the site about stock rom in case to use alpharev boot cd
I had the same problem today and I flashed the stock hboot with android flasher 1.8 and it worked. Thanks AssassinSvK.
This did the trick! Thank you =)
I have a problem with fastboot, I can`t acces it when I hold down the volume button and the power button nothing happens rom starts normally and everything works fine except the fastboot. What caused this problem? I flashed new rom and new radio, maybe something went wrong
adobric said:
I have a problem with fastboot, I can`t acces it when I hold down the volume button and the power button nothing happens rom starts normally and everything works fine except the fastboot. What caused this problem? I flashed new rom and new radio, maybe something went wrong
Click to expand...
Click to collapse
Settings/Application/untick fast boot
Alternative reboot phone and hold volume down at beginning of reboot process.
SwiftKeyed from Oxygen with Transparent XDA App
andQlimax said:
Settings/Application/untick fast boot
Click to expand...
Click to collapse
Thank you! This solved the problem
AssassinSvK said:
try download Android flasher 1.8 in dev.section
after that try to flash CWM recovery 3.0.0.5 and alsom try to flash stock Hboot
all these steps via android flasher can be done
edit - you can run alpharev but only with stock rom and hboot
in other way rooted phone with custom rom wont work with alpharev, there is also recommendation on the site about stock rom in case to use alpharev boot cd
Click to expand...
Click to collapse
So I am having the same issue here but I have tried what you suggested. I get the following error when flashing CWM recovery 3.0.0.5 (under recovery tab)
The system cannot find the path specified.
The system cannot find the path specified.
cd data\
taskkill /F /IM adb.exe
taskkill /F /IM fastboot.exe
taskkill /F /IM fastboot.exe
ERROR: The process "fastboot.exe" not found.
adb.exe reboot bootloader
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
I then tried to flash back the HBoot (HBOOT) but get the following error
The system cannot find the path specified.
The system cannot find the path specified.
cd data\
taskkill /F /IM adb.exe
ERROR: The process "adb.exe" not found.
taskkill /F /IM fastboot.exe
ERROR: The process "fastboot.exe" not found.
adb.exe reboot bootloader
'adb.exe' is not recognized as an internal or external command,
operable program or batch file.
Just an update what I have tried
Have tried to push the following to the phone via windows “RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed”. Loads and at about 55%, says that there is an issue. Try to restore but no success. When I unplug the USB, I get the following screen
AlphaRev CM7 r2
BRAVO PVT3 SHIP S-OFF
HBOOT-6.93.1002
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
Aug 10 2010, 17:52:18
RUU (highlighted orange)
[1] BOOTLOADER- Bypassed
[2] RADIO_V2- OK
[3] RADIO_CUST- OK
[4] BOOT- OK
[5] RECOVERY- OK
[6] SYSTEM- Fail-PU
[7] USERDATA- OK
[8] SPLASH1- OK
[9] SPLASH2- OK
Partition update fail!
Update Fail
When I try to load boot loader (-ve + power), it just starts up with the screen with HTC in the middle and 4 x triangles with “!” in all 4 corners..
So in short, am I screwed and should I be looking for another phone?
You cannot run ruu because the hboot version you use is protected against overwriting by ruu or ota. You have to flash bravo downgrader first.
SwiftKeyed from Oxygen with Transparent XDA App
MatDrOiD said:
You cannot run ruu because the hboot version you use is protected against overwriting by ruu or ota. You have to flash bravo downgrader first.
SwiftKeyed from Oxygen with Transparent XDA App
Click to expand...
Click to collapse
Hey
So I have run bravo downgrade and the screen has the following
BRAVO PVT3 SHIP-ON
HBOOT-0.83.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO 5.11.05.14
Jun 10 2010, 12:12:05
When I try and and hit "Recovery" on "recovery-clockwork-3.0.0.5-bravo" i get the following error
ERROR: The process "fastboot.exe" not found.
ERROR: The process "fastboot.exe" not found.
cd data\
taskkill /F /IM adb.exe
taskkill /F /IM fastboot.exe
adb.exe reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* daemon started successfully *
fastboot.exe flash recovery recovery.img
sending 'recovery' (3398 KB)...
OKAY [ 0.475s]
writing 'recovery'...
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.957s
downloading 'boot.img'...
OKAY [ 0.475s]
booting...
booting...
FAILED (remote: not allowed)
finished. total time: 0.475s
When going to load HBOOT, I get the following
C:\Users\Philip\Desktop\Stock Phone>@echo off
cd data\
taskkill /F /IM adb.exe
SUCCESS: The process "adb.exe" with PID 5456 has been terminated.
taskkill /F /IM fastboot.exe
adb.exe reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
* daemon started successfully *
fastboot.exe flash hboot hboot.img
sending 'hboot' (512 KB)...
OKAY [ 0.084s]
OKAY [ 0.084s]
writing 'hboot'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.157s
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.023s
finished. total time: 0.023s
erasing 'cache'...
FAILED (command write failed (No such file or directory))
FAILED (command write failed (No such file or directory))
finished. total time: -0.000s
finished. total time: -0.000s
rebooting...
finished. total time: -0.000s
Please let me know what I can do please to get my phone working again??
u are s-on now...u can't use fatboot
what u need to do? U can run the ruu if u want go back to stock and having the phone working
andQlimax said:
u are s-on now...u can't use fatboot
what u need to do? U can run the ruu if u want go back to stock and having the phone working
Click to expand...
Click to collapse
Hey
So I have tried to run the Ruu to go back to stock (from windows). However, I am getting errors that saying it can not varify signature and other error messages that I googled which say that I am actually downgrading the software..
I took the phone to a store and they tried the "goldSD" or something, before it was downgraded... I wonder if I should take it back and get them to try again? Other than that, what are the options if ruu wont load??
Freaking out that I may need to buy a new phone..
Now i have got this problem on my legend any suggestions?
nevermind...
doolz23 said:
Hey
So I have tried to run the Ruu to go back to stock (from windows). However, I am getting errors that saying it can not varify signature and other error messages that I googled which say that I am actually downgrading the software..
I took the phone to a store and they tried the "goldSD" or something, before it was downgraded... I wonder if I should take it back and get them to try again? Other than that, what are the options if ruu wont load??
Freaking out that I may need to buy a new phone..
Click to expand...
Click to collapse
If you're still interested, from what I've read you need to make a GoldCard and then run the RUU: http://forum.xda-developers.com/showthread.php?t=1275632
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??
Hi guys,
I need some help with my phone. Few days back I charge my phone after it died as it ran out of battery. I turned it on as I was connecting it to the charger and the white HTC loading screen came on. Left it there to do my own work and came back few hours later to notice that it's still stuck at the same loading screen. Pulled out the battery and tried turning it on again with the same result.
I tried all the methods I could find online to fix it.
The HBoot/Recovery selection only cause it to reboot and get stuck at the same loading screen. Clear Storage is successful but it get stuck again at the same screen after rebooting.
I tried to flash the latest official RUU through the pc at first but error 170 came out and my phone was not detected by the pc.
Then I tried it again with the PB99IMG.zip method with both my current microsd card and my goldcard.
The PB99IMG wasn't detected on my goldcard showing no image found, however it was detected when I place it in my current microsd but the CID incorrect error came up.
I tried the same thing again with few other different RUU.
Examples of the RUU that I had tried:
RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4. 05.00.11_release_122704.exe
RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4. 06.00.02_2_release_126984_signed.exe
RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00. 32U_5.11.05.27_release
I even reformatted my goldcard to try again but the PB99IMG still wasn't detected.
Details of my phone is as below:
BRAVO PVT3 SHIP S-ON
HBOOT- 0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-5.11.05.27
It is unbranded Asia WWE SLCD phone. I rooted it a year ago and flashed it to official WWE europe version to catch up with the froyo hype. And I did use back the same goldcard back then to try the PB99IMG method.
Can anybody please help me out?
try boot into fastboot power+back button
Then run in cmd:
Fastboot OEM enableqxdm0
Sent from my HTC Desire using XDA Premium App
kotag82, thanks for your reply.
I did what you told me to but after I entered the command, all I got was this
C:\android-sdk\platform-tools> Fastboot OEM enableqxdm0
. . .
<bootloader> [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s
Also when I entered "adb devices" on the cmd prompt, the list of devices attached is empty. Any advice?
try
fastboot devices
as adb doesnt work in fastboot mode
fastboot oem enableqxdm 0
fastboot oem eraseconfig
i sorry mistyped
I did as you advised me to and the following was the result:
C:\android-sdk\platform-tools> fastboot oem enableqxdm 0
. . .
OKAY [ 0.098s]
finished. total time: 0.099s
C:\android-sdk\platform-tools> fastboot oem eraseconfiq
. . .
<bootloader> [ERR] Command error !!!
OKAY [ 0.007s]
finished. total time: 0.007s
the eraseconfiq command failed so what should I do now?
config is spelled with a g, not q
sorry for the misspellings on my last post.. I did enter eraseconfig (with the correct spelling) but the same result came out..
C:\android-sdk\platform-tools> fastboot oem eraseconfig
. . .
<bootloader> [ERR] Command error !!!
OKAY [ 0.006s]
finished. total time: 0.006s
anything else that I missed?
How many partitions do you have on your gold card? Has it ever worked before?
only 1 partition
yes it's working..i used it to root my phone 2 years ago to flash the european froyo as mentioned in my initial post
Are you able to get another goldcard or create another goldcard with another phone?
Sent from dGB using Transparent XDA App
i have no access to another android-based phones and the current goldcard i am using is the only card that i managed to create a goldcard from
are there any other solutions?
edit: sorry for the double post
anybody else have any ideas? my phone is still stuck at the htc logo
i neded to flash stock 3uk romy (any) and lock bootloader
i have customn rom and custom recovery
INFODEBUG: cid: H3G__001
version-main: 1.28.771.9
i found solution but maybe its wrong
1.fastboot oem lock
then i have message in bootloader:
https://www.dropbox.com/s/oq8e5ko9p3zexbl/20130213_032052.jpg
and then i downloaded:
RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.28.771.9_Radio_1.1204.103.14H_release_256494_signed
im in fastboot but i have error 170 problem with connection.
can someone please help me...
lukers said:
i neded to flash stock 3uk romy (any) and lock bootloader
i have customn rom and custom recovery
INFODEBUG: cid: H3G__001
version-main: 1.28.771.9
i found solution but maybe its wrong
1.fastboot oem lock
then i have message in bootloader:
https://www.dropbox.com/s/oq8e5ko9p3zexbl/20130213_032052.jpg
and then i downloaded:
RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.28.771.9_Radio_1.1204.103.14H_release_256494_signed
im in fastboot but i have error 170 problem with connection.
can someone please help me...
Click to expand...
Click to collapse
so you have fastboot up and running, if you give the fastboot command
fastboot devices
it gives a serial back in the command window ? (your bootloader says fastboot usb, so i guess it should be fine)
how did you execute the RUU, did you execute the RUU with admin rights (right click the ruu.exe and select run with admin rights)
Mr Hofs said:
so you have fastboot up and running, if you give the fastboot command
fastboot devices
it gives a serial back in the command window ? (your bootloader says fastboot usb, so i guess it should be fine)
how did you execute the RUU, did you execute the RUU with admin rights (right click the ruu.exe and select run with admin rights)
Click to expand...
Click to collapse
fastboot devices - back
SH24XW111133 fastboot
ruu as amin
after if have this message relocked security warning if i want use phone i have to:
fastboot getvar battery-voltage
fastboot reboot-bootloader
ping /n 6 localhost >nul
and unlock bootloader ant then my old rom is working but because i want unlock my phone i have from network unlock pin but not working i someone said that i have to back to stock with lock bootloader.
and i cant find answer
why i have this error 170 in fastboot?
this ruu is ok: RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.28.771.9_Radio_1.12 04.103.14H_release_256494_signed?
the only thing i noticed that radio its diffident in ruu then in bootloader. and im using Windows 7 and when im in fastboot windows see phone as fastboot.
The main version matches so that should be fine. What you can try is this :
Flash the stock recovery 1.28 and the stock boot.img back first. Then relock the bootloader and run the ruu again.
Mr Hofs said:
The main version matches so that should be fine. What you can try is this :
Flash the stock recovery 1.28 and the stock boot.img back first. Then relock the bootloader and run the ruu again.
Click to expand...
Click to collapse
i reinstalled drivers and connect to diffrent usb and ruu start but now during process error 155??? The flash fails at checking mid/cid and before that there is image version 1.28.771.0 to image version 1.28.771.0
so i will try
Flash the stock recovery 1.28 and the stock boot.img back first???
i did unpack ruu and from rom.zip recovery and boot from (RUU_ENDEAVOR_U_ICS_40_H3G_UK_1.28.771.9_Radio_1.12 04.103.14H_release_256494_signed)
i did:\
C:\fastboot>fastboot flash boot boot.img
sending 'boot' (4282 KB)... OKAY
writing 'boot'... INFOFormat partition LNX done
OKAY
C:\fastboot>fastboot erase cache
erasing 'cache'... OKAY
C:\fastboot>fastboot flash recovery recovery.img
sending 'recovery' (5790 KB)... OKAY
writing 'recovery'... INFOFormat partition SOS done
OKAY
then
C:\fastboot>fastboot oem lock
... INFOLock successfully...
FAILED (status read failed (Too many links))
C:\fastboot>fastboot erase cache
erasing 'cache'... OKAY
this time no security warning
ant then in fastboot ruu again and error 155 again
thanks for your help
Download this one
http://androidfiles.org/ruu/securek...adio_1.1204.105.14H_release_260888_signed.exe
Try again
Mr Hofs said:
Download this one
http://androidfiles.org/ruu/securek...adio_1.1204.105.14H_release_260888_signed.exe
Try again
Click to expand...
Click to collapse
now its look good
i flashed recovery and boot from this fresh downloaded rom
its stock 3 android 4.0.3
wowwwwwwwwww
can now upgrade to jelly bean?
i checked ota update but is not available from phone,
lukers said:
now its look good
i flashed recovery and boot from this fresh downloaded rom
its stock 3 android 4.0.3
wowwwwwwwwww
can now upgrade to jelly bean?
i checked ota update but is not available from phone,
Click to expand...
Click to collapse
Yeah you should be able to update the phone, try to check a couple of times manually for ota's.
Hello XDA Programmers and Developers,
I have a big issue with my HTC Desire. Long story short I think I have bricked it
To begin with, I acquired the phone locked to Vodafone UK. After trying to unlock it using HTC Unlock Sim Tool, the software crashed and the phone was restarting at random times. You can watch the video here.
So, following some advice from XDA, I tried to re-install RUU 2.3 Gingerbread Update through the SD Card. For some reason I got a worse problem which was Radio Fail
In order to fix the issue, I tried many different RUUs available in order to get the radio fixed. One of the RUU I used resulted to what is known SLCD brick. As you can understand now, I have now visual feedback now.
In order to fix this, I followed this thread along with this tutorial.
I have created a goldcard and tried all day long to get a WWE RUU run and fix the issue. However I got no results.
Then, I decided to try fastboot and see if the phone is working.
When I run Command I get the follwing results:
1) The device is connected properly:
Code:
C:\android-sdk-windows\tools>fastboot devices
HT091PL00003 fastboot
2) I cannot flash RUU from fastboot:
Code:
C:\android-sdk-windows\tools>fastboot update C:\rom.zip
Whoops: didn't find expected signature
read_central_directory_entry failed
æÙf¸ıÝ´Ñ♫#È╩Á¹Ù■WÎPo±*Uì¬▒á·[▒¡←#òc¼ÿ¢@mUaóQ├«+═^IÕ(F^.↕ƒF,C╗_îü䬲kÿ░Û░û£↨▼♫¤ó♀
bH╗ÓòH+·qÚøµvÞ¾↨ò▲?<´ª█í8úb0<Í╔ÚÈ═║¿µ»gÑvØ╠Ð7tù¿┬Z
ÙÖíÌ´─┐uüL;^Ý3Ö<N²®♦ö"┤uè+║ö┬öµgO¥Å)XX┌u↕▒#Ì iÜøJÅ×R5ıÜ<▓=5ï▲WÂ☺B─┤0º▲Ó©^÷┴JÂn0q
BÓü▓ý☼¯cª°£]'oÿ¥ùO4£g←╔o☼!⌂_LSä¯Ê☻(½j♣&O}bõ,∟♥┘Ä°bT↨╚↔ÒıÌì╬+ð▀»L▀»‗ûjéC▒D#▒¼.)ª♀
*┘♀ƒI*y§À,y²À²©┘±▲|>}À5Z2♦÷^E´ù♀Á╩å3ÆÓÖãÅÌV┬⌂+■5nÕAÔ0~┴½Âq▲←»nl»ÍaîéÝÜW♀█üç+*Ñ*Ö
l/ý§┼x>£i5ız▬♠↑╠ëI∟0½♂±☻·/A╗│T▓ÖÖ±ÜعØÊë│R█zKÁTé■3þ┼▓♫ã▒Ã╔↔η↑ïS2←3Ì^jNÌ^r╦╝$e;k
Ik$├S=I█ì█_Ƶû┐$═ü¤=ãv~rìÛ]&bµÿ╚0C¢d6▼»C*©ziÿ▒░âÕßõÀ╝
vШ¬─©Q_2â│Cg¢À¼©C3ï▒╠ÛHÂü|┐½«♦§§{'
3) This is a bit weird: The list never ends
Code:
C:\android-sdk-windows\tools>fastboot oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8E
07D944
INFOTAG:Ramdisk OK
4) I can however restart it into bootloader (apparently since I don't have any feedback from the phone or the computer)
Code:
C:\android-sdk-windows\tools>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.016s]
finished. total time: 0.016s
-----
Lastly, I can't update using any RUU since I get ERROR 170 and ERROR 171.
Any help is appreciated.
Did you try the 2.3 GB RUU?
abaaaabbbb63 said:
Did you try the 2.3 GB RUU?
Click to expand...
Click to collapse
Yes, I did try it. However, when I try and run the .exe file through my computer I get error 171.
The exe file guides me up to the point where the installation begins, and it stops working at this point:
"Restarting Bootloader"
"Watining for Bootloader......................"
"Error 171:USB Connection fail"
Click to expand...
Click to collapse