Database Info

[Q] I need help please, completly lost....

Hi,
i've got a htc desire S and surprise, surprise i've run into another problem (most probably caused by me right now phone is in a state of "zombification" (freezes at boot screen, boots to hboot screen but loops back to hboot screen when choosing recovery or factory wipe)
I was running edymion v3.5 base release, with pdroid. but i noticed apps kept crashing/ force closing (facebook, default mail, youtube etc) bypassed most of these by reinstalling them or finding alternatives. few weeks later loads of the app started crashing, especially the camera (cashing limited to default and background apps). I decided that a reinstallation of endymion MIGHT fix this so i factory wiped using clockworkmod recovery and reflashed endymion + pdroid.
Alas, it froze on the HTC boot screen. this had happened before when i tried rooting and all..... so i did what i did before...http://forum.xda-developers.com/showthread.php?t=1728513
which failed cause the update kept stopping midway, so i pulled battery, and repeated a few times, tried using a RUU and a OTA
RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
and
OTA_Saga_S_HTC_Europe_2.10.401.8-2.10.401.5_release_225212pe4gpljm46wwfk8i
these failed as well, either stopped halfway or completed then freeze on HTC boot screen.
Phone is s-off from revolutionary, no clockworkmod now (thanks to multiple wipes) and i dont think it is rooted anymore....
here is data that may help
fastboot screen
-revolutionary-
SAGA PUT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) version-baseband: 3805.06.02.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 13.10.401.8
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: T-MOB005
(bootloader) battery-status: good
(bootloader) battery-voltage: 4057mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.017s
Mar 10 2011, 14:58:38
please advice....
P.S. sry this was so lengthy, thought more details would help fix it quicker

is your device still recognized by adb? if YES then this should enable you flash a recovery through fastboot.
exert from 4ext touch thread which is what I'd recommend that you use.
Code:
There's a [URL="http://www.4ext.net/ddl/saga/recovery.zip"]direct download[/URL] for a version you can flash via fastboot.
Download this file
Unzip it
check md5sum of the included image file
attach device through USB to PC
flash through fastboot
Code:
fastboot flash recovery recovery.img
I'd then suggest a full wipe and attempt to include a custom ROM

ben_pyett said:
is your device still recognized by adb? if YES then this should enable you flash a recovery through fastboot.
exert from 4ext touch thread which is what I'd recommend that you use.
Code:
There's a [URL="http://www.4ext.net/ddl/saga/recovery.zip"]direct download[/URL] for a version you can flash via fastboot.
Download this file
Unzip it
check md5sum of the included image file
attach device through USB to PC
flash through fastboot
Code:
fastboot flash recovery recovery.img
I'd then suggest a full wipe and attempt to include a custom ROM
Click to expand...
Click to collapse
Thanks for replying, i was begining to lose hope
unfortunately it does not register with adb since it won't switch on. But it DOES register with fastboot, so i'm trying it right not. So far it has stopped moving at
c:\Users\ME\Desktop\adroid>fastboot flash recovery recovery.img
sending 'recovery' (6038 KB)...
OKAY [ 1.021s]
writing 'recovery'...
But i'll give it some time before trying again, will report back soon
update:
Soo, waited a while, then tried flashing again. stopped at the exact same spot (writing 'recovery')

If you manage to flash a recovery, search for guide to change your misc version. Then search for a guide to change your bootloader. There is one in my signature. Finally download a T-Mobile RUU since your phone is branded. Do not flash any other versions
Sent from my HTC Desire S using xda app-developers app

amidabuddha said:
If you manage to flash a recovery, search for guide to change your misc version. Then search for a guide to change your bootloader. There is one in my signature. Finally download a T-Mobile RUU since your phone is branded. Do not flash any other versions
Sent from my HTC Desire S using xda app-developers app
Click to expand...
Click to collapse
thanks, can't seem to flash recovery though, stops and just stays at "writing recovery"

Getting stuck when trying to write one of the partitions is bad news.

Jack_R1 said:
Getting stuck when trying to write one of the partitions is bad news.
Click to expand...
Click to collapse
lol yea, i've pretty much given up. trying to find some one who can fix it, buti guess i'll have to wait to get a new phone

In which case, you surely have nothing to loose sending the dead device in for warranty fix, best leave the battery out.
Sywepd form my DsereiS

[Q] HTC One S bricked (noob level)

Hello guys,
yesterday my brother bricked his HTC One S (he is very peachy in breacking new phones ) and I was not able to restore the stock rom.
I tried some restore methods:
- If I try to enter in recovery mode on the screen appears the phone with red triangle
- If I try to run ruu exe in fastboot it doesn't work (error 155 or error 130 after various try)
- If I try to install stock zip from fastboot (after the restoring of genuine boot.img and recovery.img) the terminal said:"FAILED <remote: not allowed>"
I have no idea how to fix the issue so I hope you can help me
I noted a strange think: if I try to get all global variables, some of them are unknown, here my getvar all:
version: 0.5
version-bootloader: 1.14.0002
version-baseband: 1.08es.50.02.16
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: MB231W404549
imei: xxx (I hide it)
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: ORANG309
battery-status: good
battery-voltage: 4057mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 1a7fdca3
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
What could I do? Thanks all!

PierDesk said:
Hello guys,
yesterday my brother bricked his HTC One S (he is very peachy in breacking new phones ) and I was not able to restore the stock rom.
I tried some restore methods:
- If I try to enter in recovery mode on the screen appears the phone with red triangle
- If I try to run ruu exe in fastboot it doesn't work (error 155 or error 130 after various try)
- If I try to install stock zip from fastboot (after the restoring of genuine boot.img and recovery.img) the terminal said:"FAILED <remote: not allowed>"
I have no idea how to fix the issue so I hope you can help me
I noted a strange think: if I try to get all global variables, some of them are unknown, here my getvar all:
What could I do? Thanks all!
Click to expand...
Click to collapse
you should flash TWRP recovery to install a custom rom than you can try different sense roms which are very close to stock

Could you say what the RUU says for error 155 or 130? Also, to enter the menu for recovery hold down power, and while holding it down, press volume up.
Edit: You are using the wrong RUU. What CID are you and what phone do you have, Ville C2?
Also you might want to hide your Serial #

[Q] Black screen and reboot to recovery after HTC logo

Hello,
I am trying to help a friend with his Desire S and we have managed to Developer unlock the phone and install TWRP on it. However no matter which ROM we try after flashing and rebooting it just goes black (though with backlight on) after a short while the phone reboots and goes back into Recovery.
The phone is as said Unlocked, though with S-ON. Running HBOOT 2.00.002:
Code:
version: 0.5
version-bootloader: 2.00.0002
version-baseband: 3822.10.08.04_M
version-cpld: None
version-microp: None
version-main: 13.10.401.8
serialno: xxxx
imei: xxxx
product: saga
platform: HBOOT-7230
modelid: PG8810000
cidnum: HTC__Y13
battery-status: good
battery-voltage: 4122mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: ebd3df7d
hbootpreupdate: 12
gencheckpt: 0
Is there any way to get this device up and running again somehow?

Ah I found out. Unlike most other devices I have tried, the kernel needs to be flash manually each time and is resided in the root of the ROM usually, and can be flashed by:
First flash the ROM
Reboot into Bootloader (fastboot usb)
Extract the boot.img from the ROM zip
Issue the command: fastboot flash boot boot.img
Some ROMs require addons such as gapps being applied at this step
I think this should be more explicitly outlined in every ROM install details as it is not very clear for someone used to having the kernel flashed automagically through the recovery.

Cheesebaron said:
Ah I found out. Unlike most other devices I have tried, the kernel needs to be flash manually each time and is resided in the root of the ROM usually, and can be flashed by:
First flash the ROM
Reboot into Bootloader (fastboot usb)
Extract the boot.img from the ROM zip
Issue the command: fastboot flash boot boot.img
Some ROMs require addons such as gapps being applied at this step
I think this should be more explicitly outlined in every ROM install details as it is not very clear for someone used to having the kernel flashed automagically through the recovery.
Click to expand...
Click to collapse
Lol yh, i agree. Before i downgraded n went s-off, i flashed 2 roms and they didnt boot and the OP said nothing bout flashing boot.img after the rom. So u might look into going s-ff, u dont need to flash boot.img after flashing the rom.

Cyanogenmod11 ruu

I made install cm11 a bit easier for yall.
https://drive.google.com/file/d/0B0x...it?usp=sharing
download this file.
extract rom.zip and put into same folder as fastboot
reboot phone into fastboot
then run command fastboot oem rebootRUU
when in ruu mode run command- fastboot flash zip rom.zip
note you must be s-off and using supercid.
it might say flush immediately blah blah just run fastboot flash zip rom.zip again and wait til it finishes
next fastboot reboot-bootloader
and then boot into recovery
press the wipe button and choose "format data" enter "yes" when prompted
then reboot recovery and choose "wipe" this time press "advanced wipe" only check "cache" when its done go back and now only check "dalvik-cache"
once thats complete reboot system and wallaa cm11
these are just the bootloader variables hboot is also modded for red text, and will also not show "tampered" or "security warning" etc.. also when you do fastboot oem lock it will say locked not relocked.
I tested it on my mini so it does work.
version: 0.5
version-bootloader: 2.21.0000
version-baseband: 1.24.40e.00.26
version-cpld: None
version-microp: None
version-main: Cyanogenmod11
version-misc: PVT SHIP S-OFF
serialno:
imei:
meid:
product: m4_ul
platform: HBOOT-8930
modelid: PO5822000
cidnum: 11111111
battery-status: good
battery-voltage: 4319mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4dab9d12
hbootpreupdate: 11
gencheckpt: 0
thanks to h8rift for the hard work on cm11
and to jmz for an official twrp recovery
also attached is stocksplash.zip..to apply use fastboot oem rebootRUU then fastboot flash zip stocksplash.zip then fastboot reboot..done.

Thx for the ROM, I can confirm it works.
Is it possible to post the original boot splash screen(in splash.img form) for stock restore? I can't find it anywhere.
Thx in advance.

Sorry, but what is this exactly?

Its basically just custom recovery hboot and ROM all in a flashable zip.
Sent from my One Mini using Tapatalk

Work with Hboot 2.22.0000!?
cmvienneau said:
Its basically just custom recovery hboot and ROM all in a flashable zip.
Sent from my One Mini using Tapatalk
Click to expand...
Click to collapse
Execute me. i'm new in HTC One mini and i'm poor in English.
this RUU worked with Hboot 2.22?
i have one is Hboot 2.22 S-ON if i apply this ROM it worked?
and another one is Hboot 2.19 S-OFF 4.2.2 rooted if i Update OAT can i keep ROOT after Updated?
Thanks.

[Q] lot's of problems

Hi, not sure this is the correct place to ask but i have a sensation that is stuck in a boot loop( brought from EBay) and i wish to return it to stock, hboot is 1.27.0000 image is 3.32.161.11, radio 11.23.3504.07_m2, bootloader unlocked via HTCDev but S-ON and i cannot find a ruu or image to return to stock, (unable to boot into recovery phone just loop's) all the ruu's I've found i receive signature fail error, I've also tried several post's in the fourm that tell me how to flash a custom rom while being s-on but nothing seem's to work, again signature fail error I've also flashed several recovery images via fastboot all completed ok but ether bootloop or freeze my phone, being newish to flashing rom's ect am I doing something wrong?
Any help would be appreciated.

theconverter said:
Hi, not sure this is the correct place to ask but i have a sensation that is stuck in a boot loop( brought from EBay) and i wish to return it to stock, hboot is 1.27.0000 image is 3.32.161.11, radio 11.23.3504.07_m2, bootloader unlocked via HTCDev but S-ON and i cannot find a ruu or image to return to stock, (unable to boot into recovery phone just loop's) all the ruu's I've found i receive signature fail error, I've also tried several post's in the fourm that tell me how to flash a custom rom while being s-on but nothing seem's to work, again signature fail error I've also flashed several recovery images via fastboot all completed ok but ether bootloop or freeze my phone, being newish to flashing rom's ect am I doing something wrong?
Any help would be appreciated.
Click to expand...
Click to collapse
did you try this ruu?
RUU_Pyramid_ICS_Vodafone_UK_3.32.161.11_R_Radio_11.69A.3504.00U_11.23.3504.07
i can't find a working link right now

rzr86 said:
did you try this ruu?
RUU_Pyramid_ICS_Vodafone_UK_3.32.161.11_R_Radio_11.69A.3504.00U_11.23.3504.07
i can't find a working link right now
Click to expand...
Click to collapse
Hi,Yep tried that one still getting signed error.
Thanks for looking

You have to get an RUU according to your CID.Get into your bootloader (by pressing power + vol-) and when you see fastboot usb give the command fastboot getvar all.Then copy-paste everything here except your imei and serialno so we will be able to help you further. If you cannot find an RUU for your CID you have to S-OFF your device so you be able to change your cid. After that you can flash any RUU.
You probably have bootloop issues with custom roms because you are S-ON user and you have to flash mannually the kernel.Just extract the boot.img from the rom zip you flash from your recovery in the folder you have fastboot and then flash it from your bootloader by using the command fastboot flash boot boot.img.Then your custom Rom should be working. After that you can S-OFF your bootloader with runrummer or with juopunutbear as long as you have already unlocked your phone with HTC_dev.
** Also after S-OFF it would be nice to upgrade your radio to the latest. **

lot's of problems
Gatosbil said:
You have to get an RUU according to your CID.Get into your bootloader (by pressing power + vol-) and when you see fastboot usb give the command fastboot getvar all.Then copy-paste everything here except your imei and serialno so we will be able to help you further. If you cannot find an RUU for your CID you have to S-OFF your device so you be able to change your cid. After that you can flash any RUU.
You probably have bootloop issues with custom roms because you are S-ON user and you have to flash mannually the kernel.Just extract the boot.img from the rom zip you flash from your recovery in the folder you have fastboot and then flash it from your bootloader by using the command fastboot flash boot boot.img.Then your custom Rom should be working. After that you can S-OFF your bootloader with runrummer or with juopunutbear as long as you have already unlocked your phone with HTC_dev.
** Also after S-OFF it would be nice to upgrade your radio to the latest. **
Click to expand...
Click to collapse
Hi Gatosbil, info below many thanks for you help
rm-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.23.3504.07_M2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.161.11
(bootloader) serialno: ****************
(bootloader) imei: ****************
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3929mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.568s

theconverter said:
Hi Gatosbil, info below many thanks for you help
rm-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.0000
(bootloader) version-baseband: 11.23.3504.07_M2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.161.11
(bootloader) serialno: ****************
(bootloader) imei: ****************
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3929mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.568s
Click to expand...
Click to collapse
the only ruu you can use since you are on S-ON is the one i told you in my previous post
otherwise install 4ext recovery
enbale smartflash from 4ext
flash a custom rom
here is the latest version of 4ext
http://www.4shared.com/zip/WnSyLWMaba/4EXT_Recovery_Touch_v1006_RC3_.html
extract the recovery.img and flash it via fastboot command

rzr86 said:
the only ruu you can use since you are on S-ON is the one i told you in my previous post
otherwise install 4ext recovery
enbale smartflash from 4ext
flash a custom rom
here is the latest version of 4ext
extract the recovery.img and flash it via fastboot command
Click to expand...
Click to collapse
Thank you for your reply, I have run the ruu that you suggested in your first post but i'm still in a boot loop and being a ruu I do not know how to extract the boot image to flash it ( as this has stopped the boot loop problems in my previous phone). is there a boot.img available?
When i click on the link for 4ext you posted I cannot find the download link also can i flash 4ext being s-on
Looking forward to your reply.
Had to remove the outside link being a new member cant post outside link with less than 10 posts

theconverter said:
Thank you for your reply, I have run the ruu that you suggested in your first post but i'm still in a boot loop and being a ruu I do not know how to extract the boot image to flash it ( as this has stopped the boot loop problems in my previous phone). is there a boot.img available?
When i click on the link for 4ext you posted I cannot find the download link also can i flash 4ext being s-on
Looking forward to your reply.
Had to remove the outside link being a new member cant post outside link with less than 10 posts
Click to expand...
Click to collapse
in the ruu thread there is somewhere how to flash ruu manually
maybe from there you can locate the boot.img
about the recovery link i think you have to sign in in 4shared site
and yes you can flash 4ext while on S-ON as long as the bootloader is unlocked

rzr86 said:
in the ruu thread there is somewhere how to flash ruu manually
maybe from there you can locate the boot.img
about the recovery link i think you have to sign in in 4shared site
and yes you can flash 4ext while on S-ON as long as the bootloader is unlocked
Click to expand...
Click to collapse
I think ill give up with this phone, i have flashed 4ext via fastboot and still wont boot into recovery ( just loops)
also installed from sd card update ect ect still loops, could this be a hardware fault with the phone?

theconverter said:
I think ill give up with this phone, i have flashed 4ext via fastboot and still wont boot into recovery ( just loops)
also installed from sd card update ect ect still loops, could this be a hardware fault with the phone?
Click to expand...
Click to collapse
i really don't know mate

rzr86 said:
i really don't know mate
Click to expand...
Click to collapse
Hi, just a update ive fixed my phone, :laugh: done so by making a gold card following the tut's on this fourm installed 4ext via the card booted into recovery cleared dalvik cache ect and now boot's without any loop's.
Looking forward to flashing cyanogenmod and maybe going s-off
Many thanks for all your help and suggestions ill hit the thanks button for you.
Just need to mark as " solved " not sure how ( mod's ? )