Hi,
I had made my Desire S , S-off and rooted. I have cyanogenmod 7.1 running on my device. There was a slight problem with GPS to thought of making it to HTC rom. So used RUU to update it. But device crashed, when I try to start it gets stuck in white screen of htc. I came across this situation before, but I used RUU again then everything went fine, this time device is not at all detecting by RUU or adb. I tried most of the methods mentioned in XDA, but nothing help. Please guide me regarding this.
Here is the output of fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) version-baseband: 38.03.02.11_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.1
(bootloader) serialno: <<>>
(bootloader) imei: <<>>
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4210mV
(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.018s
My Hboot details:
-----AlphaRev-----
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-38.03.02.11_M
eMMC-boot
Mar 10 2011, 14:58:38
This is the thing which I able to get by any commands. Please help me regarding this issue.
Thanks,
Bhaswanth Gattineni.
II suggest that you edit your last post and remove both your imei code and the serial number
Swyped firm ym Desire S unsig XAD Permuim
Thanks ben_pyett ! I edited it.
I had the same issue. I think the problem lies within the version of hboot set to 6.xxxx. You should have installed the eng hboot right after the s-off, as they recommend here on xda.
I had the chance that a friend of mine works in a cell phone repair company, where they put my DS back to default.
You can still fastboot, so try to flash CM again, or locate the rom.zip file of the RUU. You can find it somewhere on your hard drive when running the RUU.
In the zip you will see boot.img, system.img and some other img files, flash them all.
fastboot flash system system.img, flashboot boot boot.img, and so on.
Good luck
@bhaswanth88
You sir need a goldcard I think (that cid isn't in the Europe RUU's) not sure about WWE ones.
If you have recovery.img back up, just find the Android Flasher program some where in xda, and flash your recovery by Flasher.
I've same problem before, I want to install a RUU files, but I don't check CID between my phone & ruu files.
Sent from my HTC Desire S using XDA
foX2delta said:
@bhaswanth88
You sir need a goldcard I think (that cid isn't in the Europe RUU's) not sure about WWE ones.
Click to expand...
Click to collapse
Too late for a gold card.
- flash a suitable HBOOT
- look for a suitable Stock recovery (there's one in the RUU)
- zip it along with the android-info.txt (using normal compression)
- rename it to PG88IMG.zip
- put it in the root of your card & boot into fastboot mode
- flash the file when the phone makes the request
- try the RUU again
- if it fails, create a PG88IMG.zip from either CWM or EXT4
- flash it the same way
- then flash a custom ROM
- from the custom ROM, you can create a gold card, use ADB commands, etc.
I think I should mention for future reference, the answer to all your problems is not a RUU. There is already a GPS fix in the development section
Sent from my Desire S using Tapatalk 2 Beta-4
Related
Hi, I was trying to unroot my desire S, I have been following the desire fanatics guide on youtube (Can't post the link - sorry)
And I got up to the point where I was running the RUU utility. It started and then It got to about 50% in and then said Error, please use the correct RUU utility. (I'm guessing I've downloaded the incorrect RUU file.
So now, when I turn the phone on it goes right into the white menu with all the stuff on HBOOT etc.. fastboot I think it is, and it says security warning.
I'm guessing Its wiped the data but no longer has an OS to boot into. I honestly don't think it is bricked but I have no clue what to do from now!
I got my phone from mobiles.co.uk (A carphone warehouse subsidiary) and it is on contract with T-mobile. The phone had no branding on it from T-mobile so I guess its unlocked.
However I downloaded the T-mobile UK RUU and ran that..
Any advice on what to do from here? I'm currently in the process of downloading The Saga_HTC _Europe_1.28.401.1_Radio20.28b.30.0805U_38.03.02.11_M_release_177977_signed.exe
I don't even know if this will work because I can't get into any OS. I also read a lifehacker article and it said I can put a file onto the SD card and it will automatically run fixing the phone, making it better.
Please help me!
So far, I've tryed:
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed
and
RUU_Saga_TMO_UK_1.30.110.2_R_Radio_20.28b.30.0805U_38.03.02.11_M_release_180106_signed
But neither of these have worked, it gives me an error 140 saying I'm using the wrong version!
Can anybody tell me the correct version for an unlocked desire S bought in the UK from mobiles.co.uk?
Something that may of made this slightly more difficult for myself Is that While following the guide I followed, I used android flasher and flashed the bootloader included in the Revert to stock bundle kit thing, It was called engHBOOToverARX
I honestly have no Idea how I can fix this but Hopefully somebody else can!
can you tell me your current hboot version?
is your device detected by ADB?
if you have not set up ADB before read this below link
His device won't be detected by adb, only fastboot.
Run fastboot command "fastboot getvar all" and post the response.
Ok, this is what I get after fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.11_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.401.4
(bootloader) serialno: SH15NTJ00762
(bootloader) imei: 356708049175530
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4040mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.023s
And I have the ability to run adb commands but I don't know what command to use to check if its detecting my device, I type adb into cmd and loads of commands come up..
@imattacus
Okay you have a UK unbranded phone, I say this cause your CID is HTC__001 and your main version is 1.47.401.4.
So to fix you can either;
1) You can download this RUU (v1.47.401.4, hboot 0.98.0002) and run it from the PC.
Or
2) Change your main version (by getting shell root) then trying again with the 1.28.401.1 RUU. (but may be impossible since you can't get adb)
Option 1 is the easiest.
Same issue with Virgin Mobile RUU
Anyone got the correct RUU for me as I've got the same issue with a Virgin Mobile RUU. I followed the instructions for unrooting here. I was using the Virgin Mobile RUU listed on the link provided which was this list but I keep on getting error 140 when I run the RUU, telling me to use the correct one.
My bootloader is as follows:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.15_M
eMMC-boot
I just need to find the right RUU version.
Any help would be greatly appreciated and as soon as possible.
Thanks
Just use Goldcard and try 1.47.401.4 again.
I also have a few problems with my Desire-S:
-my android email app keeps crashing when i try to open any email;
-official update aborts instalation (system 7) (even after hard reset).
So i decided to try fixing this via RUU. My phone is unbranded (bought in Slovenia's Vodafone), unrooted:
-android 2.3.3
-Sense 2.1
-Build 1.47.401.4
-Boot says: Saga PVT Ship S-on RL, Hbroot 0.98.0002, radio 3805.06.02.03_M
I tried to install:
-RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_234765_signed.exe
Every time i get an error 131- customer id error and message, that the ruu is wrong...
So i tried with the older one:
-RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085 AU_3805.06.02.03_M_release_199410_signed.exe
And i keep getting error 140.
And i'm stuck here. Any help? I'd like to put on 2.3.5 with sense 3 without that email bug.... and i'm considering taking it to the repair service...
Thank You
i had in a way similar problem with imattacus...
only i can't run adb commands (adb devices returns no value)
i tried folowing ruu-s:
RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed
RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed
RUU's installed, but after boot phone was stuck in white screen with green htc.
after i installed this RUU my phone booted:
RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
update>>
I checked for updates and there were some... After installing phone stuck on white screen...
I just whish to restore my phone to it's factory outofthebox state..
My getvar all result is::
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 13.10.401.8
(bootloader) serialno: HT13HTJ16283
(bootloader) imei: 355067040509788
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4020mV
(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
Any sugestions?
Goldcard
Sent from my HTC Desire S
I have installed ruu with the gold card, but I did removed it before update... Will try again and post back. Thank you very much for quick response!
>>>>>update...
Unfortunately, with gold card everything went same as before...
When i download and run update, phone reboots into update screen with progress bar, then reboots to update screen with same bar, then reboots to update screen without progress bar, then reboots and stays stuck on white screen...
i guess i have to find a way to unroot and s-on my device to the stock values before i try to update again...
my fastboot screen reads:
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3822.10.08.04_M
eMMC-boot
Mar 10 2011, 14:58:38
One more curious thing..
When i install RUU ver 1.47.401.4 (only i'm able to boot so far) image version that i overwrite (visible from RUU install screen) is 13.10.401.8... A bit large number, isn't it?
>>> FINAL UPDATE
SUCCESS!!!
as i suspected earlier, when i folowed first post on this topic i locked the phone, and then update worked.
have a nice day, everyone!
I soft bricked a friend's (yikes, I know) Telus HTC One S trying to install CM10.0.
I have abandoned the installation now and would be happy to be able to just reflash stock.
Here's my status:
I can get to fastboot.
I have the following fastboot screen:
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-0.17.31501S.10_2
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 20 2012,15:14:18
I attempted to follow a procedure to flash a stock RUU, and it demanded relocking the bootloader so now it's relocked.
I can no longer boot it into recovery since relocking.
Now, when I attempt to install the RUU that I downloaded (RUU_Ville_U_TELUS_WWE_1.84.661.9_Radio_0.17.31501S.10_2_10.27.31501S.10L_release_265367_signed.exe) while in fastboot USB mode, the RUU software executes but fails at the first step with Error 170: USB Connection Error.
I am now at a loss. Any help much appreciated.
You need to recheck correct drivers , usb cable, and usb 2.0 ports only.
Sent from my HTC One S using Tapatalk 4 Beta
Extracting the update on windows, copying it to a mac and using openruu there worked.
I don't know how people put up with Windows 8 on a Surface. It gave me a lot of trouble today.
You have to use a real computer/laptop. Surface is not real computer - it is piss poor imitation. I got Gateway laptop with win8 and have no problems.
i had this too how i fixed it i unlocked the bootloader and the security warning tag went away and i flashed recovery and flashed a romi havent found a way to go back to stock after getting the security warning.
HTC One S 1.5Ghz Soft Bricked to!
I have the same issue. Mine is also ''Tampered'' and ''Relocked''. And nothing I do works
What I done so far!
Before tampering with the cellphone I took backup .img files of my ROM. I even took a manual ''Copy everything on the cellphone to my PC'' in case this would happen. So....
I have installed Universal ADB Drivers, JDK for Java, Android Studio bundle, The HTC One Toolkit - Squabbi - 3.1.2 version. Not that it done any good so far.
The BIG problem is that the cellphone can't mount it's memory card. So I can't put any ROMS, FLASH FILES, .zips or anything on it. I failed at forcing data into the ''data'' folder to.
And when I try to flash a file directly using ''Fastboot'' the device hangs at ''Sending'' request. Other problems when working with the ''ADB commands'' gives me the ''Device not found'' response.
I downloaded the RUU for my device as a .zip as there's no existing .exe version to be found. With no luck flashing it I might say. Due to the constant hanging when the file is ''Sending''.
( This is the RUU I downloaded: OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50. 05.28_10.27.50.08L_release_301852xf01hejl416oev96. zip )
And for 2 days with applying fix after fix and trial and error I'm coming nowhere! I'm thinking on formatting the whole cellphone and copy my ''manual copy of my cellphone'' into the formatted cellphone drive.
In the bootloader this information can be seen:
*** TAMPERED ***
*** RELOCKED *** (Along the lines of guides this happen. No idea how though
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.11.50.05.28
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012,17:10:57:-1
My cellphone has: Philz touch 5 CWM Base version 6.0,3,2 on it.
NOW! This is what actually works on my cellphone:
1. I can get into BootLoader on my HTC One S!
2. I can get into Fastboot on my HTC One S!
3. The Fastboot on my HTC One S recognizes as ''Fastboot USB'' on when I plug it into my computer.
4. My computer recognizes the cellphone as a ''removable disk''. And using the command ''Fastboot Devices'' in CMD lets me see the ''SH32HW401164'' number. Using the command ''Fastboot getvar all'' gives me this information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4150mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
----
My plan was to flash this ROM into my phone if the stock one still showed issues: http://forum.xda-developers.com/show....php?t=2531065
This being said and again: My HTC One S is NOT flashed with a custom ROM! It has the same ROM it came with, all though, it has been unlocked -> Rooted -> Relocked. And never been S-off. it is still S-On.
Any help with this issues would be appreciated and thanks for this great forum
HTC-One-User said:
I have the same issue. Mine is also ''Tampered'' and ''Relocked''. And nothing I do works
What I done so far!
Before tampering with the cellphone I took backup .img files of my ROM. I even took a manual ''Copy everything on the cellphone to my PC'' in case this would happen. So....
I have installed Universal ADB Drivers, JDK for Java, Android Studio bundle, The HTC One Toolkit - Squabbi - 3.1.2 version. Not that it done any good so far.
The BIG problem is that the cellphone can't mount it's memory card. So I can't put any ROMS, FLASH FILES, .zips or anything on it. I failed at forcing data into the ''data'' folder to.
And when I try to flash a file directly using ''Fastboot'' the device hangs at ''Sending'' request. Other problems when working with the ''ADB commands'' gives me the ''Device not found'' response.
I downloaded the RUU for my device as a .zip as there's no existing .exe version to be found. With no luck flashing it I might say. Due to the constant hanging when the file is ''Sending''.
( This is the RUU I downloaded: OTA_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_1.11.50. 05.28_10.27.50.08L_release_301852xf01hejl416oev96. zip )
And for 2 days with applying fix after fix and trial and error I'm coming nowhere! I'm thinking on formatting the whole cellphone and copy my ''manual copy of my cellphone'' into the formatted cellphone drive.
In the bootloader this information can be seen:
*** TAMPERED ***
*** RELOCKED *** (Along the lines of guides this happen. No idea how though
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO-1.11.50.05.28
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012,17:10:57:-1
My cellphone has: Philz touch 5 CWM Base version 6.0,3,2 on it.
NOW! This is what actually works on my cellphone:
1. I can get into BootLoader on my HTC One S!
2. I can get into Fastboot on my HTC One S!
3. The Fastboot on my HTC One S recognizes as ''Fastboot USB'' on when I plug it into my computer.
4. My computer recognizes the cellphone as a ''removable disk''. And using the command ''Fastboot Devices'' in CMD lets me see the ''SH32HW401164'' number. Using the command ''Fastboot getvar all'' gives me this information:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4150mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.063s
----
My plan was to flash this ROM into my phone if the stock one still showed issues: http://forum.xda-developers.com/show....php?t=2531065
This being said and again: My HTC One S is NOT flashed with a custom ROM! It has the same ROM it came with, all though, it has been unlocked -> Rooted -> Relocked. And never been S-off. it is still S-On.
Any help with this issues would be appreciated and thanks for this great forum
Click to expand...
Click to collapse
I managed to UNLOCK it again. Then used this guide to fix the SD card error: http://forum.xda-developers.com/showthread.php?t=2086156 Afterwards I downloaded the VIperROM 3.2.0.zip and put it on my SD card. Then flashed like normal and now the phone has ROM and works Thanks for the fantastic support to this forum!
I'm trying to get my father's phone ruu'ed to 3.14 tmo.
I rooted his phone and unlocked through htc dev a long time ago.
He is currently running cm10 w/ hboot 1.09 and radio 0.16.31501s.
S-on w/ tmo CID.
I used faceplam S-off on my phone and lost 3g/4g. I do not want this to happen to his phone.
So what I'am asking is what do i have to do to get his tmo HTC ONE S safely onto the JB 3.14 from htc/tmo?
When i try to ruu using the 3.14 i get ERROR [159]: IMAGE ERROR. It says i have the wrong image and to download the correct one. Its the same one i used on my phone repeatably.
Any help would be great. Really afraid of borking his phone.
after some googling. I found that the ruu has to match the hboot and be re-locked. Some one also suggested flashing a stock zip and stock recovery. However i cant find a stock rom zip for 1.53. So i just tried re-locking and ruu'ing, but now i get ERROR 155.
Any help would be great. Again i can't s-off for fear of being stuck on edge like my phone
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.16.31501S.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4132mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
billydroid said:
after some googling. I found that the ruu has to match the hboot and be re-locked. Some one also suggested flashing a stock zip and stock recovery. However i cant find a stock rom zip for 1.53. So i just tried re-locking and ruu'ing, but now i get ERROR 155.
Any help would be great. Again i can't s-off for fear of being stuck on edge like my phone
Click to expand...
Click to collapse
tmobile U.S.
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe
http://www.androidruu.com/getdownlo..._10.30.50.08L_release_309489_signed_ICS_2.exe
to relock
while phone is in bootloader >fastboot USB
fastboot folder, shift right click open command window
from command window type
fastboot oem lock
(also heard but haven't tried because I'm S-Off that you can run RUU.exe from fastboot USB without relocking bootloader)
Edit: to answer the bootloader question. Yes you can ruu a different hboot as long as it is a higher hboot. (s-off no matter)
I got it. I had to re-lock and run ruu 1.84 rc2 first. Then it let me ruu 3.14.
Sent from my HTC VLE_U using Tapatalk
Hi. It was long time ago I played with Sensation. A friend of mine brought his phone asking for help. That's the story:
He had problems with ARHD installed, wanted to clean flash. He wiped and started to install ROM. Android_Revolution_HD_Super_Wipe_Sensation.zip was used.
Firmware was 3.33 universal, hboot original 1.29 was downgraded and unlocked previously via controlbear method.
Phone had problems with entering into CWM, so he flashed CWM. No go.
He flashed firmware again and on bootscreen we have now:
LOCKED
s-off
hboot 1.29.0000
Mar 2 2012
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.24.401.1
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3780mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Looks like radio is missing ( he said about some problems when he tried RUU for first time.
Now:
Unable to install RUU - no phone connected (phone states fastbootUSB)
Unable to install firmware fron sdcard, unable to change CID.
How to bring it to life?
Thanks, Mike
sp5it said:
Hi. It was long time ago I played with Sensation. A friend of mine brought his phone asking for help. That's the story:
He had problems with ARHD installed, wanted to clean flash. He wiped and started to install ROM. Android_Revolution_HD_Super_Wipe_Sensation.zip was used.
Firmware was 3.33 universal, hboot original 1.29 was downgraded and unlocked previously via controlbear method.
Phone had problems with entering into CWM, so he flashed CWM. No go.
He flashed firmware again and on bootscreen we have now:
LOCKED
s-off
hboot 1.29.0000
Mar 2 2012
Looks like radio is missing ( he said about some problems when he tried RUU for first time.
Now:
Unable to install RUU - no phone connected (phone states fastbootUSB)
Unable to install firmware fron sdcard, unable to change CID.
How to bring it to life?
Thanks, Mike
Click to expand...
Click to collapse
the device still has gb firmware
that's why you can't boot the rom(if i understand well)
try this
http://forum.xda-developers.com/showthread.php?t=1459767
flash 3.33 universal
follow the indtructions to the letter
and before flashing check md5 sums(important)
I tried 3.33 FW.
I have message: [7]Bootloader - Fail-PU
Update fail.
M
sp5it said:
I tried 3.33 FW.
I have message: [7]Bootloader - Fail-PU
Update fail.
M
Click to expand...
Click to collapse
that is not good
ok then since you are on S-OFF change your cid to supercid
then use again any ruu.exe
best wishes
HI Guys
So my mate's phone won't boot up and I'd really appreciate some assistance. The last thing I did was unlock the phone via htcdev. But that's all I could do. Now I can't flash a recovery (I've tried a few) because I get an IMAGE UPDATE ERROR. I've also received a "SIGNATURE VERIFY FAIL" error.
Also, adb won't recognise my device but fastboot does.
What I'm trying to do is install a custom rom because my mate was complaining that his phone was slow and a bit laggy. I sold the phone to him in the first place so I've taken it upon myself to fix it.
Thanks guys, let me know if you need any further info.
CJ
First of all, we need some information about your phone.
I need : what kind(k2u, k2ul and so on)
Then what you have already done.
Then the other things (best of all you copy all information from your boot loader)
Edit: okay skript point 2 xD
Kreumadragon
Thanks for getting back to me.
Here's the information you've requested.
UNLOCKED
K2_ul PVT SHIP S-ON RL
HBOOT-2.21.0000
Radio-1.18.40a.00.05
openDSP-v13.2.0268.0620
OS-3.12.980.10
eMMC-boot 1024MB
Jul 2014
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.21.0000
(bootloader) version-baseband: 1.18.40a.00.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.12.980.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT2BWTP01724
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) meid:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8015000
(bootloader) cidnum: OPTUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4330mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2bb255c2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.100s
Let me know if you need any further information.
With regards to what I have already done, I tried to flash TWRP recovery but I got an image update error.
Mhh do you flash the right TWRP?
And use fastboot flash recovery *recovery name*?
Do you have any data's to loose?
Kreumadragon
yeah I flashed a few different TWRPs and none of them worked.. if there is a specific one and if you have a link, I could try again?
nope i don't need any data to lose. I have removed the sd card. Thanks again.
Anyone? Still having no luck with this phone.
Please test (if you want) the cwm recovery. Link:
http://forum.xda-developers.com/showthread.php?p=37075457
If this doesn't work flash a ruu and try again
Kreumadragon
There is no RUU out which will work and also the cwm is outdated.
How did you flash recovery?
Use the one i recommended in my index thread. This should work on your hboot.
An other option is to get s off and flash it via pl**img.zip isn't it?
Kreumadragon
You need a working OS for S-off. Not sure if that is working here.
@Old
You have s off, haven't you?
And I get s off with hboot 2.21
Kreumadragon
I don't have One SV anymore.
Rumrunner works on hboot 2.21.
He says that he didn't have data's to loose
theoretically you can create an ........IMG.zip file with all files a ruu use, only the recovery is changed? Think I can make one but first want to read what you think(old)
Kreumadragon
As long as he is S-on you don't need to make anything.
Right now he can only flash signed firmware by HTC this way.
Okay, thx I don't know
Actually no ruu for any kind of k2ul?
Kreumadragon
Only one. And you must be S-off or on ICS to use that.
@CJ_
Do you have test old.s method?
If this doesn't work, you probably need SOff.
Kreumadragon
Hi old.splatterhand, to answer your question, I flashed the latest TWRP recovery (2.8. something) but I got the following IMAGE UPDATE ERROR. Will try the ones in your index and report back.
Thanks for your help guys.
Will try it now... If that doesn't work, how do I get S-Off when I can't do anything with the phone?