Related
my phone info
hboot 1.18.0000
radio 10.14.9035.01_M
image 1.45.401.2
its not getting even stock rom with same image version
ruu says
trying to reboot in bootloader .............
but no luck
ever tried with htcdev bootunlock method to S-Off
gots this
fastboot oem get_identifier_token
C:\sdk>fastboot oem get_identifier_token
Program too big to fit in memory
Try to go fast-boot and run ruu should work.
If not take out the battery and hold volume down and swith on,run recovery or fast-boot and then run ruu.
yes i have done that too
in fastboot ruu runs and read info of my set (which show that its conected with pc)
but when ruu tried to reboot in bootloader
it takes almost 30 minutes then error comes of usb conectivity
problem is that bootloader are locked
it shows when pluged in fastboot mode
"Locked"
It will do, that's completely normal
i think still a driver problem with your laptop.
download the official one from HTC, just following the installation and STOP the installation when it wants you in install HTC SYNC!!
EddyOS said:
It will do, that's completely normal
Click to expand...
Click to collapse
what will do what ???
i could'nt get that
Rawahi said:
i think still a driver problem with your laptop.
download the official one from HTC, just following the installation and STOP the installation when it wants you in install HTC SYNC!!
Click to expand...
Click to collapse
tried on three different systems with three differernt os and checked all drivers
it does'nt make sense that its a conectivity problem
cuz ruu shows all info of my set. so its conected in fastboot with pc
guys i need to run ruu to go back s on but when i run the ruu after everything going ok it says rebooting bootloader which doesnt than gives me error 155 when i try to do bootloader it doesnt c gives error 170 im supercid on 1.17 fw
Reboot to manually to fastboot (guides are on XDA everywhere) - then run the RUU
Error 170 happens when the RUU can not recognize your phone. Do you have the recommended drivers installed (e.g. from HTC Sync)?
Easier to boot into fastboot, connect the phone to the PC and then try and run it - should then work fine (so long as you have the drivers installed)
done it thanks install htc sync done it thanks
I'm searching for the original RUU for my branded HTC One S 1.53.169.3 with CID VODAP120. I semi-bricked it while trying to flash the vanilla modaco rom. I had a nandroid backup of my stock rom and reverted to stock. when the restore process was done i got a bootloop and couldn't mount /sdcard/ from cwm anymore. so i restored stock recovery over fastboot and relocked the bootloader and tryed to restore my device with the 1.53.401.2 unbranded RUU by editing the android_info.txt and adding my cid in the rom.zip but i am still getting error 132 (signature error) because there still isn't a possibility to s-off the one s. My only hope is to find the original branded One S RUU 1.53.169.3. I would be pleased if someone could upload the RUU. Thanks
its not possible to mount the sdcard in cwm. boot your phone in to recovery and
adb push yourrom.zip /sdcard
Try this rom: http://files.virtuousrom.com/ville/roms/Virtuous_Ville_v.1.4.0_PROPER.zip
maybe this will fix your bootloop. if not try this:
Start the RUU
- in windows type %TEMP%
- search for rom.zip
- extract it
- cmd to this folder
- fastboot flash boot boot_signed.img
restart your phone. Maybe this helps!
i'm always getting device not found in adb shell. the boot_signed.img is already on the device. still stuck in boot
install the usb driver from android sdk
my htc drivers are installed and i've tried now a coupe of times to install the android usb drivers and i am always getting drivers not match message
also having red triangle in recovery. should i try to unlock bootloader and install cwm recovery and try adb again?
I have, in the past had fastboot working on my Desire S in Windows 7 so perhaps this is a Windows 8.1 driver compatibility issue?
Firstly, I tried to downgrade from a very slow Jelly Bean to the Ice Cream Sandwich RUU, but the device got stuck in a bootloop showing the HTC logo and the RUU USB connection times out. So I figured that I might need to re-lock my device for the RUU to work. So I tried, but fastboot devices, and fastboot oem lock dont work. Windows 8.1 says Device unrecognized and I have tried reinstalling different versions of the drivers.
adb devices works when the phone is in Jelly Bean. It's just fastboot that doesn't work.
Please help?
i have the same problem,only i have ice cream sandwich perfecto linaro edition,and my phone is not recognised on 5 different pc,and 3 macs.
fastboot does not work,neither adb debugging.
i don-t have a notification when i plug in the cable,and also i can-t use mass storage.i tried flashing a new kernel,but it wont-t flash.
recovery works,i can flash other roms,but i get a boot loop and cannot start the phone.
any help would be greatly appreciated.
thanks.
htc desire s
try this
http://downloads.unrevoked.com/HTCDriver3.0.0.007.exe
i will try this tonight.
i copied PG88IMG.ZIP to sd card,and i booted in bootloader,and it finds the file,it says loading then just parsing for 1 sec and nothing happens.
will post results tomorrow.
saga pvt ship s-on rl
hboot 2.02.0002
radio 3831.19.00.110
eMMC-boot
unfortunately it didn't work.
the driver provided didn't detect my phone.
if i format the sd card will it work?
is there any method to relock the bootloader from hboot or fastboot?i can enter recovery but every time i flash a new rom,i get a bootloop .
alllexander said:
i will try this tonight.
i copied PG88IMG.ZIP to sd card,and i booted in bootloader,and it finds the file,it says loading then just parsing for 1 sec and nothing happens.
will post results tomorrow.
saga pvt ship s-on rl
hboot 2.02.0002
radio 3831.19.00.110
eMMC-boot
Click to expand...
Click to collapse
Sorry for the newbish question, but have you both tried using different cables? I had this problem once, and it was the cable that was faulty. Charged fine, sdcard mounted fine - but neither adb nor fastboot worked.
allexander: I dont think PG88img.zip will run with s-on unless its an official, signed update thing. I think thats correct, anyway.
hello.
the pg88img.zip file is in fact the rom.zip renamed after a stock RUU installation.
I tried usint 3 different cables for the phone.
i can however connect through wifi adb.
can i do something to flash a different boot.img and then flash a ROM i know it works with usb connection and adb debugging?
alllexander said:
hello.
the pg88img.zip file is in fact the rom.zip renamed after a stock RUU installation.
I tried usint 3 different cables for the phone.
i can however connect through wifi adb.
can i do something to flash a different boot.img and then flash a ROM i know it works with usb connection and adb debugging?
Click to expand...
Click to collapse
Hmm interesting problem. Generally when the hboot says 'parsing PG88img.zip' but then that flashes for a second and goes away again, its because its trying to find a valid PG88IMG.zip but cant find one it thinks is valid enough to use. So I still think this relates to you being S-ON. For example maybe the hboot file is too old for your current version, in which case there may be fixes available using misc_version hack. That's just my instinct though. My radio has always been s-off via a cheap hardware clip, but I still struggled at first to flash PG88IMG.zip because I didnt understand the file format.
There is alot you could do if you could get PG88IMG.zip working.
Regarding your strange bootloop: are you certainly using 4EXTRecovery to wipe all partitions except the SD card before flashing a new rom?
nothing worked for me in windows 8.1 , cannot recognise the device in fastboot. only recognised in adb.
so just installed windows 7 in another partition. then fastboot recognised the phone. and i could flash the 4ext recovery. :good:
I am using twrp 2.4 and i can't flash another recovery.every time i try,it says recovery flashed then i get the same recovery when i reboot
rimpy said:
I have, in the past had fastboot working on my Desire S in Windows 7 so perhaps this is a Windows 8.1 driver compatibility issue?
Firstly, I tried to downgrade from a very slow Jelly Bean to the Ice Cream Sandwich RUU, but the device got stuck in a bootloop showing the HTC logo and the RUU USB connection times out. So I figured that I might need to re-lock my device for the RUU to work. So I tried, but fastboot devices, and fastboot oem lock dont work. Windows 8.1 says Device unrecognized and I have tried reinstalling different versions of the drivers.
adb devices works when the phone is in Jelly Bean. It's just fastboot that doesn't work.
Please help?
Click to expand...
Click to collapse
Hi your biggest issue is with windows 8 and Fastboot. They don't play nice. You will need a windows 7 PC to proceed. Once you have that. Reunlock your bootloader and flash a stock ROM from the dev section.
alllexander said:
i have the same problem,only i have ice cream sandwich perfecto linaro edition,and my phone is not recognised on 5 different pc,and 3 macs.
fastboot does not work,neither adb debugging.
i don-t have a notification when i plug in the cable,and also i can-t use mass storage.i tried flashing a new kernel,but it wont-t flash.
recovery works,i can flash other roms,but i get a boot loop and cannot start the phone.
any help would be greatly appreciated.
thanks.
htc desire s
Click to expand...
Click to collapse
It sounds like your micro USB port may be damaged. Is it loose feeling at all?
radical.entropy said:
Hmm interesting problem. Generally when the hboot says 'parsing PG88img.zip' but then that flashes for a second and goes away again, its because its trying to find a valid PG88IMG.zip but cant find one it thinks is valid enough to use. So I still think this relates to you being S-ON. For example maybe the hboot file is too old for your current version, in which case there may be fixes available using misc_version hack. That's just my instinct though. My radio has always been s-off via a cheap hardware clip, but I still struggled at first to flash PG88IMG.zip because I didnt understand the file format.
There is alot you could do if you could get PG88IMG.zip working.
Regarding your strange bootloop: are you certainly using 4EXTRecovery to wipe all partitions except the SD card before flashing a new rom?
Click to expand...
Click to collapse
You are correct good sir, s-on is the issue here. If the IMG.zip passed to the hboot is a lower version that the img installed to the device the hboot will skip it anyway. A misc hboot downgrade would work but you would need a unlocked hboot+ working recovery and to make a gold card to bypass the cid check of the ruu.
Its not that hard to do once you have done it before, but it can be daunting at first
Sent from my HTC Desire S using Tapatalk
i flashed just now flinny cm,and i got passed the htc logo,and the boot animation started but it was in a very low resolution and not centered on the screen.
i get to the point where my charging led is on,then nothing.it remains the same,through the boot process.
i am usint twrp 2.4 and i cannot flash another recovery ,not via terminal or apps in the phone.i will try to flash in recovery.can i do that?
ContactFront said:
try this
HTCDriver3.0.0.007.exe
Click to expand...
Click to collapse
Tried this and it didn't work.
DroidArmy said:
nothing worked for me in windows 8.1 , cannot recognise the device in fastboot. only recognised in adb.
so just installed windows 7 in another partition. then fastboot recognised the phone. and i could flash the 4ext recovery. :good:
Click to expand...
Click to collapse
Sounds like I need to do this. It worked for me last time I checked in Windows 7.
heavy_metal_man said:
Hi your biggest issue is with windows 8 and Fastboot. They don't play nice. You will need a windows 7 PC to proceed. Once you have that. Reunlock your bootloader and flash a stock ROM from the dev section.
Click to expand...
Click to collapse
Makes sense. I'm surprised there isn't a fix for it in Windows 8. My phone is already unlocked and I am wanting to install the RUU. Are you suggesting that I can't downgrade with RUU and need to install a stock ROM instead?
rimpy said:
Makes sense. I'm surprised there isn't a fix for it in Windows 8. My phone is already unlocked and I am wanting to install the RUU. Are you suggesting that I can't downgrade with RUU and need to install a stock ROM instead?
Click to expand...
Click to collapse
correct. while you could do it, its alot of hassle you would need to edit your misc partition so it states that your mainversion is lower than it really is. then the ruu is considered an "upgrade" and gets flashed. you would also need to make a goldcard using your sdcard and the goldcard tool in order to bypass the hboots cid check on your ruu. then it would run.
but much easier to flash a rooted stock rom go for one of these
alllexander said:
i have the same problem,only i have ice cream sandwich perfecto linaro edition,and my phone is not recognised on 5 different pc,and 3 macs.
fastboot does not work,neither adb debugging.
i don-t have a notification when i plug in the cable,and also i can-t use mass storage.i tried flashing a new kernel,but it wont-t flash.
recovery works,i can flash other roms,but i get a boot loop and cannot start the phone.
any help would be greatly appreciated.
thanks.
htc desire s
Click to expand...
Click to collapse
It is the incompatible of the driver with either Windows 8 & 8.1. I have to PCs, one with Windows 7 and the other with Windows 8.1; under either bootloader or recovery mode plugged in works with Win 7. On the other hand on win 8.1, recovery mode plugged in works fine but bootloader mode win 8.1 does not recognize the phone. I have tested them with the same phone and the same rom C11 by Devin Kin. No matter which HTC drivers installed, I got the same result.
i have now windows 7 64 bit,and it doesn't recognise my phone.
if i install usb mass storage app on the phone,if i connect the usb cable the phone notifies me about mass storage toggle,but not the usual from the ROM,the one from the app.
if i enable the usb mass storage the device isn't recognised,if i disable it it is also not recognised.
i can connect through adb wifi,i will post the logcat here,maybe someone can help.
also,can i use a command in adb shell to relock the bootloader?
if i can do that i cand try to flash PG88IMG through hboot .
i noticed i can push files through adb,can i flash boot.img from a different rom then flash the rom vie recovery immediately after?like fastboot flash after flashing a rom in recovery.
hello all.
i found the problem
it was the umt connector on the phone.
alllexander said:
hello all.
i found the problem
it was the umt connector on the phone.
Click to expand...
Click to collapse
Please tell us how to solve the problem.
Hello,
My phone was updating and crashed. The phone turns on but only the HTC logo appears and then goes to a black screen. I can't fastboot into the device as it is not recognised. I can't access TWRP recovery any more and goes to a downloading screen and then restarts again. While in the bootloader the phone shows the following:
***TAMPERED***
*** RELOCKED***
M4_UL PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.19.0000
RADIO-1.22.40e.00.07
OpenDSP-v19.2.0268.0927
OS-1.31.401.1
eMMC-boot 1024MB
Aug 7 2013, 17:37:54.0
Please help me, any help greatly appreciated!
Update:
The phone is working and has an update but it can not update on the device, is there a way i can get the downloaded OTA file on to my PC?
CoolAndroid1 said:
Hello,
My phone was updating and crashed. The phone turns on but only the HTC logo appears and then goes to a black screen. I can't fastboot into the device as it is not recognised. I can't access TWRP recovery any more and goes to a downloading screen and then restarts again. While in the bootloader the phone shows the following:
***TAMPERED***
*** RELOCKED***
M4_UL PVT SHIP S-OFF RL
CID-11111111
HBOOT-2.19.0000
RADIO-1.22.40e.00.07
OpenDSP-v19.2.0268.0927
OS-1.31.401.1
eMMC-boot 1024MB
Aug 7 2013, 17:37:54.0
Please help me, any help greatly appreciated!
Click to expand...
Click to collapse
Hi,
What do you want to flash stock sense 6...??
greets
shivasrage said:
Hi,
What do you want to flash stock sense 6...??
greets
Click to expand...
Click to collapse
Hello,
Yes I would like to go back to Sense 6 or any stock firmware preferably 4.4.2
Thanks
CoolAndroid1 said:
Hello,
Yes I would like to go back to Sense 6 or any stock firmware preferably 4.4.2
Thanks
Click to expand...
Click to collapse
Ok
First I recommend you to unlock your bootloader.
So if you are in bootloader and your device is not recognised I think it´s a driver issue.
If you allready checked it check it once more or update your tools (ADB, fastboot)
If nothing helps you could go to recovery and format your device (not only wipe format) should be clear that all data on device is lost.
Try different recoverys some people report that philz also works fine on M_4. (try install new rom option on philz).
DONT flash stock sense 6 ROM (wrong partition layout for this hboot) with this hboot rather take 5.5.
I´m sorry but without get connectet via ADB or fastboot I think there is no chance to get it working again.
greets
shivasrage said:
Ok
So if you are in bootloader and your device is not recognised I think it´s a driver issue.
If you allready checked it check it once more or update your tools (ADB, fastboot)
If nothing helps you could go to recovery and format your device (not only wipe format) should be clear that all data on device is lost.
Try different recoverys some people report that philz also works fine on M_4. (try install new rom option on philz).
DONT flash stock sense 6 ROM (wrong partition layout for this hboot) with this hboot rather take 5.5.
With out get connectet via ADB or fastboot I think there is no chance to get it working again.
greets
Click to expand...
Click to collapse
I can not access recovery to wipe anything out, on bootloader if i choose to wipe it attempts to load recovery which goes into download mode. The device comes up as "Device failed emulation" on Windows 8
CoolAndroid1 said:
I can not access recovery to wipe anything out, on bootloader if i choose to wipe it attempts to load recovery which goes into download mode. The device comes up as "Device failed emulation" on Windows 8
Click to expand...
Click to collapse
Ok
I tell you in short terms:
If you can´t get a fastboot connection to your device it looks very bad to bring your device back.
For wiping something you need recovery for flashing new recovery you need fastboot.
For flashing a new firmware to fix messed up partitions you need fastboot.
And first of all to unlock your bootloader you need fastboot.
You see all ends up with fastboot.
As what the device is shown in the manager of windows?
Better to use Windows 7 there are much driver problems people reporting on win 8
greets
Ok, I will use a win 7 pc and let you know
shivasrage said:
Ok
I tell you in short terms:
If you can´t get a fastboot connection to your device it looks very bad to bring your device back.
For wiping something you need recovery for flashing new recovery you need fastboot.
For flashing a new firmware to fix messed up partitions you need fastboot.
And first of all to unlock your bootloader you need fastboot.
You see all ends up with fastboot.
As what the device is shown in the manager of windows?
Better to use Windows 7 there are much driver problems people reporting on win 8
greets
Click to expand...
Click to collapse
After i fix my drivers issue what can i do afterwards?
shivasrage said:
Ok
I tell you in short terms:
If you can´t get a fastboot connection to your device it looks very bad to bring your device back.
For wiping something you need recovery for flashing new recovery you need fastboot.
For flashing a new firmware to fix messed up partitions you need fastboot.
And first of all to unlock your bootloader you need fastboot.
You see all ends up with fastboot.
As what the device is shown in the manager of windows?
Better to use Windows 7 there are much driver problems people reporting on win 8
greets
Click to expand...
Click to collapse
I can now do the fastboot command from CMD
CoolAndroid1 said:
After i fix my drivers issue what can i do afterwards?
Click to expand...
Click to collapse
If you have a connection via fastboot you first have to decide what ROM you want, search for the matching firmware.
for example flash the latest firmware for M_4... 4.09.401.3 from here (new partition layout for e.g. sense 6):
https://docs.google.com/file/d/0BzCFBBNdXagdcEMybkdBME5iUE0/edit
After that flash TWRP 2.7.1.1 or philz and format all you have to try one of this recoverys should work.
Next push or sideload a ROM via adb I recommend you one them:
http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921
You can decide what you want rooted or not it doesn´t matter.
After installing with succsess try to reboot that´s it.
greets
I encountered a similar issue when playing around with returning my device to stock. I flashed stock recovery, then re-locked my bootloader. What is the downloading screen you're seeing? Is it the stock recovery screen?
To fix, i had to change CID back to stock (for me that was, CWS__001)
Unlock bootloader again, using HTC unlock.bin (unlock.bin wouldn't work when i was on super cid)
Flash custom recovery TWRP 2.6.3.0 (I'm not sure if 2.7.1.1 works with the old partition layout, so i used this version until i had upgraded to hboot 2.22, then I flashed 2.7.1.1. This may be an unnecessary step, but it always worked for me)
Once twrp was working again...
Flash stock hboot 2.22 found in the dev section
Flash TWRP 2.7.1.1 (again, might be an unnecessary step)
Boot to recovery
From TWRP, adb push the sense 6 rom i wanted to flash (IC 3.07 in my case)
After the push completed, flash ROM and reboot and all was good
As you can see, the steps i took require that fastboot and adb drivers work flawlessly, especially when pushing ROM to the device using abd.
If any of this seems unfamiliar, then don't do these steps. Again, this is just what i did when i flashed stock recovery and re-locked bootloader with a ROM that wouldn't boot.
jollywhitefoot said:
I encountered a similar issue when playing around with returning my device to stock. I flashed stock recovery, then re-locked my bootloader. What is the downloading screen you're seeing? Is it the stock recovery screen?
To fix, i had to change CID back to stock (for me that was, CWS__001)
Unlock bootloader again, using HTC unlock.bin (unlock.bin wouldn't work when i was on super cid)
Flash custom recovery TWRP 2.6.3.0 (I'm not sure if 2.7.1.1 works with the old partition layout, so i used this version until i had upgraded to hboot 2.22, then I flashed 2.7.1.1. This may be an unnecessary step, but it always worked for me)
Once twrp was working again...
Flash stock hboot 2.22 found in the dev section
Flash TWRP 2.7.1.1 (again, might be an unnecessary step)
Boot to recovery
From TWRP, adb push the sense 6 rom i wanted to flash (IC 3.07 in my case)
After the push completed, flash ROM and reboot and all was good
As you can see, the steps i took require that fastboot and adb drivers work flawlessly, especially when pushing ROM to the device using abd.
If any of this seems unfamiliar, then don't do these steps. Again, this is just what i did when i flashed stock recovery and re-locked bootloader with a ROM that wouldn't boot.
Click to expand...
Click to collapse
I cant unlock my bootloader as its relocked and fails, I cant install TWRP either
CoolAndroid1 said:
I cant unlock my bootloader as its relocked and fails, I cant install TWRP either
Click to expand...
Click to collapse
Did you get fastboot working yet? Does "fastboot devices" show your device? You can't do anything until fastboot works...but I imagine it worked at some point, since you unlocked and re-locked your device.
You can't install recovery because your bootloader is locked. And you can't unlock your bootloader until you change your CID back to whatever it was when you created the unlock.bin file on the HTC website.
Are you getting this error when you attempt to unlock?
FAILED (remote: unlock token check failed)
jollywhitefoot said:
Did you get fastboot working yet? Does "fastboot devices" show your device? You can't do anything until fastboot works...but I imagine it worked at some point, since you unlocked and re-locked your device.
You can't install recovery because your bootloader is locked. And you can't unlock your bootloader until you change your CID back to whatever it was when you created the unlock.bin file on the HTC website.
Are you getting this error when you attempt to unlock?
FAILED (remote: unlock token check failed)
Click to expand...
Click to collapse
Hello,
I did have the error code above but i used FUU to flash back to stock and all is fine now!!
CoolAndroid1 said:
Hello,
I did have the error code above but i used FUU to flash back to stock and all is fine now!!
Click to expand...
Click to collapse
Cool. Did you use fuu from here?
http://forum.xda-developers.com/showthread.php?t=2659109
jollywhitefoot said:
Cool. Did you use fuu from here?
http://forum.xda-developers.com/showthread.php?t=2659109
Click to expand...
Click to collapse
Yep! Windows 8 sucks with drivers and didn't work so had to switch to a different laptop!
CoolAndroid1 said:
Yep! Windows 8 sucks with drivers and didn't work so had to switch to a different laptop!
Click to expand...
Click to collapse
That's what i had to do when i first tried to root my phone. I was on Windows 7, but it was an old install and had all kinds of software on it that might have been preventing usb from working (iTunes, HTC Sync, some other random software, etc.) Sometimes, I would even have trouble connecting an external HD!
I ended up installing a clean copy of XP on an old computer that i now use strictly for flashing stuff to my phone.
New problem
I have 4.3 on my HTC now and have received an update for 4.4.2, however when I try this it goes a quarter of the way then comes up with a red triangle and exclamation point. The device is still rooted somehow. Can you help me update?
CoolAndroid1 said:
New problem
I have 4.3 on my HTC now and have received an update for 4.4.2, however when I try this it goes a quarter of the way then comes up with a red triangle and exclamation point. The device is still rooted somehow. Can you help me update?
Click to expand...
Click to collapse
I don't think OTA will work on unlocked/tampered device with custom recovery.I think you need to run ruu.exe if one is available for you to get 100% stock before OTA will work again.
jollywhitefoot said:
I don't think OTA will work on unlocked/tampered device with custom recovery.I think you need to run ruu.exe if one is available for you to get 100% stock before OTA will work again.
Click to expand...
Click to collapse
Hello,
I found an FUU for 4.4 Kitkat on the link you posted earlier, It does all the necessary actions with no failures and completes with a Congrats screen but the firmware is the same?