Related
I have my HTC Sensation XE which has originally the 2.3.4 Gingerbread.
I would like to have an assistance on how to do it?
Do I need to flash specific firmwares? Where could I get it? and is it safe to use the backup I made before with that Gingerbread Rom?
Thank you.
I used SUPERCID method.. Therefore I'm not exactly sure whats my CID number and RUU but im pretty sure its either HTC__038 or HTC__044 asia or wwe_asia.
If it helps , I had some Starhub apps, Singtel or whatever, so I assume its more of an HTC__044 CID number?
Thank you.
If you did superCID you don't need to worry about which ruu you use. There is a stock GB ruu link in the s-on section of the sticky guide to everything in the dev forum.
Sent from my HTC Pyramid using xda premium
stringer7 said:
If you did superCID you don't need to worry about which ruu you use. There is a stock GB ruu link in the s-on section of the sticky guide to everything in the dev forum.
Sent from my HTC Pyramid using xda premium
Click to expand...
Click to collapse
Thank you for the response. But im trying to get the OTA also.
That's why I want to be sure about my RUU. and CID ^^, Thank you.
ardom said:
Thank you for the response. But im trying to get the OTA also.
That's why I want to be sure about my RUU. and CID ^^, Thank you.
Click to expand...
Click to collapse
OK, you can find your original cid by entering "getprop ro.cid" in terminal emulator.
Sent from my HTC Pyramid using xda premium
stringer7 said:
OK, you can find your original cid by entering "getprop ro.cid" in terminal emulator.
Sent from my HTC Pyramid using xda premium
Click to expand...
Click to collapse
I had changed my CID when i rooted mine i used supercid method and changed it to 11111111 i forgot my original ru. Im nt sure exactly too if its wwe_asia or asia but im sure its either of the two. I had Starhub app too so i have a premonition that it could be htc__044 or asiawwe singapore version.
Im confused lol. I Want to go back to my stock ruu and cid. Or least the cid so i could restore my backup if possible. Then if ever i ota update. Less prblems could be encountered.
Sent from my HTC Sensation XE with Beats Audio
What are the steps I need to do?
Which to flash? any firmware?
THank you.
This is a prime example of making sure you check for the RUU BEFORE you flash anything new
Do what is said above and it will tell you your original CID. We can then see if we can find the RUU
Good luck. I just updated my xe to ics by simply reading a lot of posts on this site. And simply following all instructions.
At first tho, I mistakenly flashed sensation and not sensation xe. But again, found the correct files here on this site. All sorted and now have beats audio back, now with sense and ics latest.
So many helpful people here, so I hope you too get your fine sorted to the way you want yours. Although curious as to why you wanna go back to gb.
Surely ics is better?
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA
hi
hi guys, do you have any link for official Gingerbread RUU 1.73 with beats audio for sensation XE? i just turn my sensation XE to s-on and flash the RUU but i flashed a wrong ruu.thanks guys.i want to update my sensation XE to ics through system update
Are you S-ON again now? If so, you'll need to S-OFF before you can flash the XE RUU (which you can find here):
https://www.yousendit.com/download/M3BtWmd2YWJ6NE5qQTlVag
Its already 1111111 for my CID. Im planning to go back to stock gb so i can get the ota ics and try it out.
Sent from my HTC Sensation XE with Beats Audio
Yes my phone is s-on again, so how do I flash the ruu?and just s-off? No need to do rooting?thanks
Help ~ Loop boot
I was gonna revert to my stock Gingerbread 2.3.4, I was trying to achieve ICS 4.x and Cyanogen mod 9, but I n00bed it up and wound up in a boot loop. I've read several different tutorials and I gathered I need to flash back to Stock GB. Do I just need a link to a Stock GB that fits my CID?
CID = T-MOB010
No Super CID
No RUU
Thanks much
soldierforus said:
I was gonna revert to my stock Gingerbread 2.3.4, I was trying to achieve ICS 4.x and Cyanogen mod 9, but I n00bed it up and wound up in a boot loop. I've read several different tutorials and I gathered I need to flash back to Stock GB. Do I just need a link to a Stock GB that fits my CID?
CID = T-MOB010
No Super CID
No RUU
Thanks much
Click to expand...
Click to collapse
yes yes stock GB would do ..also ..you have stock ICS for that cid too want that ?
GB RUU for TMOB USA
ICS RUU for TMOB USA (post #1 section #3 has the link to RUU's)
but
care to explain more what happened ?..it probably might be a small solution
small details would do ..
complete details present in the bootscreen (a screenshot would do too)
also
a complete output of the following command (except IMEI and serail number)
fastboot getvar all
then i can give you a perfect solution
ganeshp said:
yes yes stock GB would do ..also ..you have stock ICS for that cid too want that ?
GB RUU for TMOB USA
ICS RUU for TMOB USA (post #1 section #3 has the link to RUU's)
but
care to explain more what happened ?..it probably might be a small solution
small details would do ..
complete details present in the bootscreen (a screenshot would do too)
also
a complete output of the following command (except IMEI and serail number)
fastboot getvar all
then i can give you a perfect solution
Click to expand...
Click to collapse
Sorry to double post, I thought this may be a dead thread since the previous post had a question and no reply in 4 months.
_____________________________________________
The Details:
Boot loop began after I flashed to firmware 3.32 using:
Universal Firmware 3.32 Universal (Non-TMOUS): Since I am on TMO, I gather I should have used the TMOUS flash?
DOWNLOAD: http://d-h.st/afS
MD5: 8f50e9f4f3fab7edcd4013015703f81c
From this tutorial: http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
I later I found a cynaogen tutorial to help with boot loop and followed these steps:
1) Set to factory reset
2)Cleared Delvick (sp?) Cache
____________________________________________
Current Boot Screen:
Revolutionary
Pyramid PVT SHIP S-OFF RL
HBOOT 1.27.1100
RADIO-11.22.3504.07_M
OpenADSP-v02. 6. 0. 226.00.0131
eMMC-boot
_____________________________________________
Getvar all Results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.1100
(bootloader) version-baseband: 11.22.3504.07_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.401.3
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5810000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3816mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.490s
So how do the RUU's function exactly? I read the glossary term in wiki, but I don't fully understand the concept. They will update my ROM through window? I guess I need to be able to kill this boot loop first though.
Thanks again
soldierforus said:
Sorry to double post, I though this may be a dead thread since the previous post had a question and no reply in 4 months.
_____________________________________________
The Details:
Boot loop began after I flashed to firmware 3.32 using:
Universal Firmware 3.32 Universal (Non-TMOUS): Since I am on TMO, I gather I should have used the TMOUS flash?
DOWNLOAD: http://d-h.st/afS
MD5: 8f50e9f4f3fab7edcd4013015703f81c
From this tutorial: http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
I later found a cynaogen turoial to help with bootloop and followed these steps:
1) Set to factory reset
2)Cleared Delvick (sp?) Cache
____________________________________________
Current Boot Screen:
Revolutionary
Pyramid PVT SHIP S-OFF RL
HBOOT 1.27.1100
RADIO-11.22.3504.07_M
OpenADSP-v02. 6. 0. 226.00.0131
eMMC-boot
_____________________________________________
Getvar all Results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.1100
(bootloader) version-baseband: 11.22.3504.07_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.401.3
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5810000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3816mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.490s
So How the RUU's function exactly. They will update my ROM through window? I guess I need to be able to kill this boot loop first though.
Thanks again
Click to expand...
Click to collapse
for RUU ..you need to connect the phone in bootloader to pc ..and then just double click on it ...that will do
one last try for flashing custom rom ..still not worked then go for RUU
btw what recovery you are using ?
if using cwm ...can you switch to 4EXT recovery ?
get the recovery image from the below db link (recovery.img inside the zip)
4EXT DB link
and flash it via fastboot
fastboot flash recovery recovery.img
got to the recovery
4EXT->wipe|format->format all partitions except sdcard
then back to main menu ...and flash the rom (what ever custom rom you want)
then reboot and see..if it still stuck at boot logo
then extract the boot.img from the rom zip file
and flash it manually
fastboot flash boot boot.img
then reboot
still stuck ?
then reflash the firmware (be sure to check the md5 of the firmware you have downloaded)
still stuck?
then RUU
No-Go
ganeshp said:
for RUU ..you need to connect the phone in bootloader to pc ..and then just double click on it ...that will do
one last try for flashing custom rom ..still not worked then go for RUU
btw what recovery you are using ?
if using cwm ...can you switch to 4EXT recovery ?
get the recovery image from the below db link (recovery.img inside the zip)
4EXT DB link
and flash it via fastboot
fastboot flash recovery recovery.img
got to the recovery
4EXT->wipe|format->format all partitions except sdcard
then back to main menu ...and flash the rom (what ever custom rom you want)
then reboot and see..if it still stuck at boot logo
then extract the boot.img from the rom zip file
and flash it manually
fastboot flash boot boot.img
then reboot
still stuck ?
then reflash the firmware (be sure to check the md5 of the firmware you have downloaded)
still stuck?
then RUU
Click to expand...
Click to collapse
So it wouldn't let me flash 4ext, it says: "cannot load 'recovery.img'" I didn't unzip it or even leave the zip in the root, I took only the recovery.img and left it in to sd root.
You said to flash the custom ROM, but this is my first attempt, and although I have downloaded CM9, the instructions I have read from other tutorials tell me I have to upgrade first to firmware 3.32, then to firmware 3.33, then I can install CM9, which will give me ICS/4.x Am I correct so far?
I don't even know if the 3.32 flash was a success (Do you?) since now I am in a boot loop. Could it be because I should have used the TMOUS instead of the non-TMOUS universal for 3.32? I picked the non-TMOUS because I didn't realize what TOUS stood for at the time, and the other link said universal (and the android-info had my cid/mid)
Also thanks for the RUU links, but I don't know what good the ICS will do if I don't have it yet. Those RUU's will do what exactly? Update to the latest ROM ? Also, is that for all roms or just 3rd party? Looking at the getvar log I sent you, I gather the 3.32 did work, So I should download the ICS 3.32 RUU link you sent me. That's what I am going to try now
EDIT
________________________________
I re-installed cm9, AND EUREKA!!!!!! My first custom ROM. Many thanks to all who helped! Now which RUU do I use, and how often should I run it?
soldierforus said:
So it wouldn't let me flash 4ext, it says: "cannot load 'recovery.img'" I didn't unzip it or even leave the zip in the root, I took only the recovery.img and left it in to sd root.
You said to flash the custom ROM, but this is my first attempt, and although I have downloaded CM9, the instructions I have read from other tutorials tell me I have to upgrade first to firmware 3.32, then to firmware 3.33, then I can install CM9, which will give me ICS/4.x Am I correct so far?
I don't even know if the 3.32 flash was a success (Do you?) since now I am in a boot loop. Could it be because I should have used the TMOUS instead of the non-TMOUS universal for 3.32? I picked the non-TMOUS because I didn't realize what TOUS stood for at the time, and the other link said universal (and the android-info had my cid/mid)
Also thanks for the RUU links, but I don't know what good the ICS will do if I don't have it yet. Those RUU's will do what exactly? Update to the latest ROM ? Also, is that for all roms or just 3rd party? Looking at the getvar log I sent you, I gather the 3.32 did work, So I should download the ICS 3.32 RUU link you sent me. That's what I am going to try now
EDIT
________________________________
I re-installed cm9, AND EUREKA!!!!!! My first custom ROM. Many thanks to all who helped! Now which RUU do I use, and how often should I run it?
Click to expand...
Click to collapse
RUU is rom update utility.. It's official htc file
Ruu is complete software for your phone
It wipes everything.. Rom, recovery firmware.. Everything and flashes the corresponding stock One...
So when you run ics ruu.. You will have complete ics stock rom of tmobile US
And the recovery flash you did earlier was wrong..
You need to keep that recovery file in the adb folder (it should be in pc) Then the command will fetch the file.. As you have kept it on top of sdcard.. It can't find it..
Sent from my pyramid.. Through blazing fast sonic waves
I have a HTC sensation which I am trying to fix.
It was working fine and then did an OTA update and it would not boot again and would lock up on the HTC logo with a white background.
I did manage to unlock the phone, but it is still S-ON because I am unable to get into the phone normally to get revolutionary to detect the phone correctly because it cant find the phone in recovery mode.
I managed to get EXT4 recovery image installed which helped me flash the rom to cyanogenmod 10.1 but it will reboot every 5 seconds after it loads into the menu.
I did a super wipe and installed ARHD but it only gets to the beats audio logo before restarting.
I was unable to find the correct stock rom or the RUU because the CID is TELNZ which doesn't seem to have many stock rom files around.
I believe that if I can find the RUU_PYRAMID_TELNZ then it will help me fix the device, but I can't find it on the net.
I tried to write a super CID so I could flash any rom to it but it doesn't work:
C:\AndroidSDK\sdk\tools>fastboot oem writecid 11111111
...
(bootloader) vreg_set: request is duplicated id 14
(bootloader) pyramid_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
I tried to manually update the phone with (I had to edit the file and add TELNZ*** to it):
C:\AndroidSDK\sdk\tools>fastboot flash zip PG58IMG.zip
sending 'zip' (14242 KB)...
OKAY [ 3.087s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
I also tried to put PG58IMG.zip on the SD card but the phone fails to update from the image with no error after it finishes "checking" the file.
Here is the info that I have gathered from the device:
Model: HTC sensation z710a
version: 0.5
version-bootloader: 1.18.0000
version-baseband: 10.14.9035.02_2
version-cpld: None
version-microp: None
version-main: 1.50.781.1
product: pyramid
platform: HBOOT-8260
modelid: PG5811000
cidnum: TELNZ001
battery-status: good
battery-voltage: 3912mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: 9d24123f
hbootpreupdate: 11
gencheckpt: 0
What I am hoping to do is to get the device S-OFF and install ARHD Sensation 7.3 or a working install of cyanogenmod 10.1.
If anyone could offer me any help, that would be greatly appreciated.
**update 1**
I have found the reason that the roms are restarting constantly.
Basically the 1.18 HBOOT version I have is too low and causing issues.
I need to update to 3.33 but the revolution tool cant get root, so I am trying to use the Tacoroot method to try and get revolution to work.
The issue I am now facing is that I cant get past the first step because of this error: "failed to copy 'tacoroot.bin' to '/data/local/tacoroot.bin': Permission denied"
delete.....
ahsan64 said:
use this guide to update firmware ( http://forum.xda-developers.com/showthread.php?t=1472298 )... If you already have 4ext recovery installed than move to flashing 3.33 firmware section..
Click to expand...
Click to collapse
I am unable to follow this guide because I am still S-ON, I'm trying to get S-OFF but revolutionary is not working and neither will the tacoroot method.
McBOeric said:
I am unable to follow this guide because I am still S-ON, I'm trying to get S-OFF but revolutionary is not working and neither will the tacoroot method.
Click to expand...
Click to collapse
Yeah i forgot that device you mention your device is still S-ON and that's why i removed my abov post but you can still flash GB RUU.. let me find..
You're s-on... Then you must flash boot.img of the ROM you're trying to flash, using fastboot commands:
fastboot flash boot boot.img
Then immediately reboot.
Revelation™ ushered in a revolution... Right on, SebastianFM!
ashkan-khatar said:
You're s-on... Then you must flash boot.img of the ROM you're trying to flash, using fastboot commands:
fastboot flash boot boot.img
Then immediately reboot.
Click to expand...
Click to collapse
Thanks.
To go into greater detail, does this mean that I need to download hTC-Stock-FirmWare-3.33.401.6 (HBOOT-1.29.0000+boot.img+Radio+Recovery+etc.) and manually flash the boot.img via CMD?
What I have managed to do so far is run superwipe and install SENSEaY_XE35_v2.1.0 which is a modified GB rom.
I tried to then run the revolutionary method to get S-OFF but it always just corrupted the rom.
I also tried the tacoroot method but that corrupted the rom as well.
So for now I'm just leaving it with SENSEaY_XE35_v2.1.0 installed since that is the only thing that works and seems to be stable on the phone.
Hi all!
Im in a big pickle here and I cant get myself out at the moment.
First hand.. The info
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.13.0000
(bootloader) version-baseband: 0.17.31501S.10_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4011000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3917mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d92cc658
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.093s
Now i've been running cyanogenmod 10 stable since I started rooting etc...
And it's been amazing, but now since there has been a release candidate for 10.1, I was looking into updating it.
I ran into an issue where my boot-loader was not accepted , therefor i would run into an error on Clockwork mod stopping me from flashing 10.1
The bad thing was that I erased my previous installation without backing up the stock and CM10.
So now i'm left with no system. Though I can get into Fastboot and ADB via recovery.I
For some reason if I try to flash CM10 (The rom and the boot file) the cyanogenmod logo will continue spinning.
I tried to fiddle around with my RUU afterwards because I currently have S-On. But i later learned that i need superCID.
^(Which i learned that you need your phone on to alter it to the 8 "1"s) Which i cant do because i have no system.
I might have already altered some files guessing that my boot-loader is named "dirty-d92cc658" and im afraid that I messed up something internally.
So anyways. Im here with my Ville S4 plugged in on fastboot not knowing what to do.
Any Help would be amazing , thank you
Did you try a RUU for Rogers? Not sure if there is one but try to find a RUU that matches your cid
c19932 said:
Did you try a RUU for Rogers? Not sure if there is one but try to find a RUU that matches your cid
Click to expand...
Click to collapse
Do I need to have superCID to flash RUU's ?
Mozziliac said:
Do I need to have superCID to flash RUU's ?
Click to expand...
Click to collapse
If you have a RUU for your specific phone, no, you just need to lock the bootloader.
Have USB debugging turned on (unless running ruu when your phone is in fastboot usb mode)
If you can't find one for Rogers, then yes you have to be super cid to run another RUU.exe (after that change your cid back so an OTA update doesn't brick your phone)
If your phone is on Jellybean, you need to run a JB ruu, if it's Ice Cream Sandwich it won't run. Unless you are supercid I guess.
Khan.orak has a guide for OTA zips to return to stock that you might want.
http://forum.xda-developers.com/showthread.php?p=44365370
Ville / VilleC2 RUU, OTA and Stock Nandroid Collection
http://forum.xda-developers.com/showthread.php?t=2200930
tivofool said:
If you have a RUU for your specific phone, no, you just need to lock the bootloader.
Have USB debugging turned on (unless running ruu when your phone is in fastboot usb mode)
If you can't find one for Rogers, then yes you have to be super cid to run another RUU.exe (after that change your cid back so an OTA update doesn't brick your phone)
If your phone is on Jellybean, you need to run a JB ruu, if it's Ice Cream Sandwich it won't run. Unless you are supercid I guess.
Khan.orak has a guide for OTA zips to return to stock that you might want.
http://forum.xda-developers.com/showthread.php?p=44365370
Ville / VilleC2 RUU, OTA and Stock Nandroid Collection
http://forum.xda-developers.com/showthread.php?t=2200930
Click to expand...
Click to collapse
How can I superCID my phone if I cant boot into the rom?
I've never superCid, can't help you there.
Good news is you can get into bootloader still.
You could fastboot flash a boot.img and flash a rom in recovery.
Just need to mount usb storage in recovery to put the rom.zip on your phone.
Edit: reread that you tried that but rom didn't boot. Hopefully you waited 5-10 min for first load.
try wipedata/factory reset from CWM like 3 times then flashing?
Good luck to ya.
Edit 2: kind of wondering if you can run the Rogers RUU with that low of a bootloader (version-bootloader: 1.13.0000)
Maybe someone can chime in, because that would be nice not having to SuperCid.
Alright so I seemed to get it running on CM 10 by switching recoveries and flashing it's boot.
Then I was able to superCID the phone, which then lead my into S-off'ing it.
Then I was able to update the hboot firmware to 2.15
Cleared the cache and installed the new kernel and flashed cyanogenmod 10.1 rc
Everything went well after that. I did run into a laggy issue, which I then fixed by switching the CPU governor to ondemand instead of interactive.
Thanks for the post guys
Heyy, so i was wondering if yous could help me. I have a stock HTC Sensation EU, t-mobile version, which I had updated to the latest version (4.0.3 I think). During the upgrade-process something went wrong and now it doesn't go past the HTC logo. S-ON. When in Hboot it shows no found something.img. What is the way to fix this?
If possible I'd like to root it as well and use the Cyanogenmod.
HI, is it possible to you to go In Recovery Mod or Fastboot???
If it's yes,
Go here :
[GUIDE][N00b] Flash a ROM from 100% Stock!
This is a guide that give u all the way to unlock ur bootloader, change your stock recovery with a custom one (4ext).
Then u'll be able to install a ROM custom.
Here u can found a lot of ROM Developped for HTC SENSATION.
Sensation Android Development
blogodoblogodo said:
HI, is it possible to you to go In Recovery Mod or Fastboot???
If it's yes,
Go here :
[GUIDE][N00b] Flash a ROM from 100% Stock!
This is a guide that give u all the way to unlock ur bootloader, change your stock recovery with a custom one (4ext).
Then u'll be able to install a ROM custom.
Here u can found a lot of ROM Developped for HTC SENSATION.
Sensation Android Development
Click to expand...
Click to collapse
Seems good, i´ll try it out
blogodoblogodo said:
HI, is it possible to you to go In Recovery Mod or Fastboot???
If it's yes,
Go here :
[GUIDE][N00b] Flash a ROM from 100% Stock!
This is a guide that give u all the way to unlock ur bootloader, change your stock recovery with a custom one (4ext).
Then u'll be able to install a ROM custom.
Here u can found a lot of ROM Developped for HTC SENSATION.
Sensation Android Development
Click to expand...
Click to collapse
So it worked, but it didn't. I managed to install a custom rom, but after 10 seconds (if it even was that much), the system crashes and reboots, only to do the same thing again.
I used a RUU as well but I got a signing error (132) when using the RUU. I then tried installing the RUU through fastboot and I got further. I did however got the error saying the CID wasn't matching. In the .txt file from the zip I had added my CID, So I thought it had to work.
There is no official rom for my cid (T-MOB003) unfortunately.
This is starting to give me a headache
Search for this HERE
blogodoblogodo said:
Search for this HERE
Click to expand...
Click to collapse
Well DEFINITELY not there.
Those are Sensation XL.
Here's for our Sensation http://forum.xda-developers.com/showthread.php?t=1672425
Hoooooooo, Nooo,
Sorry ,really sorry
I googled "T-MOB003 for SENSATION"
Sorry DrNickjen
Thank You Nicx59
Nicx59 said:
Well DEFINITELY not there.
Those are Sensation XL.
Here's for our Sensation http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
I have read that once, but I'll do it again; this time more thorougly.
The RUU I'm trying to install is RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed
fastboot getvar all returns
Code:
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.18.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.50.114.2
(bootloader) serialno: xxx
(bootloader) imei: xxx
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5813000
(bootloader) cidnum: T-MOB003
(bootloader) battery-status: good
(bootloader) battery-voltage: 4104mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 9d24123f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Since my cidnum is not in the RUU, (and there isn't a RUU for my cid) I'll have to add it according to the guide. I'll get to that later. hboot version to install and version-main are both higher than currently installed, so that shouldn't be an issue.
My phone is S-ON, but unlocked so I'll have to relock it again. Followed instructions and device is *** RELOCKED ***. Displays, however, a security warning. I'll now proceed with the installation by executing the exe. If I'm right I should see an error.
Error: Customer ID incorrect, as expected. I'll now try to install manually.
Since my CID is different I'll change it in the .zip. 7z didn't allow me to change it in the archive itself so I've extracted the archive, changed android-info.txt to:
Code:
modelid: PG5813000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__N34
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__032
cidnum: HTC__016
cidnum: T-MOB003
mainver: 3.32.401.5
hbootpreupdate:12
DelCache:1
Note: When pasting this my CID was placed on the same line as mainver. Inserted an enter and repasted in android-info.txt.
What I did as well was unlock the bootloader again, changed recovery to the file inside the rom.zip, and relocked the bootloader. I read this was a fix for the problem.
THIS POST IS IN PROGRESS
HI its not necessary to show ure imei, plz, edit your post and Erase it.
blogodoblogodo said:
HI its not necessary to show ure imei, plz, edit your post and Erase it.
Click to expand...
Click to collapse
Thanks.
Just Hit ThAnks Button
So For you, is it good???
blogodoblogodo said:
Just Hit ThAnks Button
So For you, is it good???
Click to expand...
Click to collapse
Nope. I gave up fot the day because I couldn't het the PG58IMG flashed. It didn't have an effect in hboot so I tried using fastboot but i got an unknown error. The tries installing ViperS 2.0, which succeeded. On boot, however, the system crashed and rebooted automatically, just like the other rom's i've tried.
If only I could get a rom working...
DrNickjen said:
Nope. I gave up fot the day because I couldn't het the PG58IMG flashed. It didn't have an effect in hboot so I tried using fastboot but i got an unknown error. The tries installing ViperS 2.0, which succeeded. On boot, however, the system crashed and rebooted automatically, just like the other rom's i've tried.
If only I could get a rom working...
Click to expand...
Click to collapse
actually if you are still on gingerbread firmware you can't boot any ics or jb rom
flash this rom from recovery
http://d-h.st/bqL
if you still want to upgrade to ics then S-OFF the device from here
http://revolutionary.io/
after that flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
follow the instructions to the letter
and before flashing check md5 sums(important)
then flash any ics or jb rom from recovery
rzr86 said:
actually if you are still on gingerbread firmware you can't boot any ics or jb rom
flash this rom from recovery
http://d-h.st/bqL
if you still want to upgrade to ics then S-OFF the device from here
http://revolutionary.io/
after that flash 3.33 universal from here
http://forum.xda-developers.com/showthread.php?t=1459767
follow the instructions to the letter
and before flashing check md5 sums(important)
then flash any ics or jb rom from recovery
Click to expand...
Click to collapse
Flashed it using Cwm, first did a full wipe and it installed fine. It then booted en got to a black screen and rebooted. Wiping Dalvik cache + /cache didn't work as a solution.
Same thing as any other .zip I've installed through recovery.
DrNickjen said:
Flashed it using Cwm, first did a full wipe and it installed fine. It then booted en got to a black screen and rebooted. Wiping Dalvik cache + /cache didn't work as a solution.
Same thing as any other .zip I've installed through recovery.
Click to expand...
Click to collapse
can you post your bootloader details again and what rom did you try to flash now?
also did you try to follow the steps i gave you?
rzr86 said:
can you post your bootloader details again and what rom did you try to flash now?
also did you try to follow the steps i gave you?
Click to expand...
Click to collapse
UNLOCKED
Pyramid PVT SHIP S-ON RL
HBOOT-1.18.000
eMMC-boot
August 2nd 2011
Tried to flash the rom you linked to and yes I have.
DrNickjen said:
UNLOCKED
Pyramid PVT SHIP S-ON RL
HBOOT-1.18.000
eMMC-boot
August 2nd 2011
Tried to flash the rom you linked to and yes I have.
Click to expand...
Click to collapse
change the recovery to 4ext
before flash the rom enable smartflash from 4ext
rzr86 said:
change the recovery to 4ext
before flash the rom enable smartflash from 4ext
Click to expand...
Click to collapse
I love you omg it worked <3 <3
So, what do I have to do in order to get e.g. Cyanogenmod running?
DrNickjen said:
I love you omg it worked <3 <3
So, what do I have to do in order to get e.g. Cyanogenmod running?
Click to expand...
Click to collapse
First make a full backup of your device through 4ext.
Then just flash the zips from one of the following releases:
android1234567's release (here you have to flash rom and kernel seperately)
albinoman887's releease
And last flash gapps from here
DrNickjen said:
I love you omg it worked <3 <3
So, what do I have to do in order to get e.g. Cyanogenmod running?
Click to expand...
Click to collapse
see my previous post of what to do now
S-OFF
flash 3.33 universal(check md5 sums before flashing)
flash cyanogenmod rom
done
note:when you achieve S-OFF you won't need anymore the smartflash feature
My HTC One SV (LTE europe version ) stuck while booting, it displays white logo screen only,
now i unlocked bootloader and tried to flash rom, but failed,
How i can flash a custom rom or original oerating systedm in my phone,
please help me.
anpayy said:
My HTC One SV (LTE europe version ) stuck while booting, it displays white logo screen only,
now i unlocked bootloader and tried to flash rom, but failed,
How i can flash a custom rom or original oerating systedm in my phone,
please help me.
Click to expand...
Click to collapse
Can you get into the bootloader? If you can, you can flash TWRP recovery via fastboot and flash a custom Rom with the recovery.
Yes
thearif said:
Can you get into the bootloader? If you can, you can flash TWRP recovery via fastboot and flash a custom Rom with the recovery.
Click to expand...
Click to collapse
i can get into bootloder, but where can i get TWRP recovery and custom rom file ?
anpayy said:
i can get into bootloder, but where can i get TWRP recovery and custom rom file ?
Click to expand...
Click to collapse
Go to http://forum.xda-developers.com/showthread.php?t=2292432 . Read through and find the recovery there. It is pretty well explained there. I am on my mobile so I am not sure of the link will take you to the first page. It is on the first page. Make sure you get the correct recovery for your phone model.
Original rom
Where i can get original ROM for HTC ONE SV LTE k2ul_4.2.2_3.11.401.1 ???
anpayy said:
Where i can get original ROM for HTC ONE SV LTE k2ul_4.2.2_3.11.401.1 ???
Click to expand...
Click to collapse
That I do not know, but if my memory serves me right, there was a thread either in android development or general sections with the latest OTAs. You might wanna search for that...
anpayy said:
Where i can get original ROM for HTC ONE SV LTE k2ul_4.2.2_3.11.401.1 ???
Click to expand...
Click to collapse
You've already got the link to my index thread, but it seems you are to lazy to have a look at it. You even only need to watch for the software number and you will easily find what you are searching for.
Os intallation failed
i tried to install OTA update through TWRP recovery , but it failed
You can't flash this in recovery. Use TWRP recovery and flash the rom (not the Ota). Links are in my index thread.
Installed rom
Sucessfully instaled Viper SV rom,
but still phone did not booting,
Did you also flash boot.img of the rom in fastboot?
no
I missed to boot boot.img,
Now phone is working perfectly...........
Thanks all........specially old.splatterhand & thearif
Nice
anpayy said:
I missed to boot boot.img,
Now phone is working perfectly...........
Thanks all........specially old.splatterhand & thearif
Click to expand...
Click to collapse
Good to hear that...
Hi all,
I'm new in this forum so I post there.
My problems starts after try to updete htc one sv k2_ul. After update I get red triangle and then my phone freezed on white screen with logo.
Try to do factory reset from bootloader, but nothing happen. After few days looking information I unlock bootloader and try flash new boot, but after that I get Tampered. I found if I must s-off, but how I can get it? My pc found phone only on fastboot mode. Any ideas?
miegas said:
Hi all,
I'm new in this forum so I post there.
My problems starts after try to updete htc one sv k2_ul. After update I get red triangle and then my phone freezed on white screen with logo.
Try to do factory reset from bootloader, but nothing happen. After few days looking information I unlock bootloader and try flash new boot, but after that I get Tampered. I found if I must s-off, but how I can get it? My pc found phone only on fastboot mode. Any ideas?
Click to expand...
Click to collapse
You can't get S-off, without working OS.
You don't have an OS anymore on your phone?
Are you running a custom recovery like TWRP?
Run this fastboot cmd and copy the output here (remove your imei & serial number):
Code:
fastboot getvar all
old.splatterhand said:
You can't get S-off, without working OS.
You don't have an OS anymore on your phone?
Are you running a custom recovery like TWRP?
Run this fastboot cmd and copy the output here (remove your imei & serial number):
Code:
fastboot getvar all
Click to expand...
Click to collapse
My os just stop working.
I don't try TWRP, today will look more about that.
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 1.15.40a.00.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.401.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4143mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.075s
edit
I flashed TWRP and I make restore, but phone won't start anyway. Maybe need to flash new os?
Flash the stock rom in TWRP, and don't forget to flash boot.img of the rom in fastboot.
Links are in my index thread.
Make a backup in recovery (just in case) and a wipe (advanced -> everything except int & ext sdcard) before.
old.splatterhand said:
Flash the stock rom in TWRP, and don't forget to flash boot.img of the rom in fastboot.
Links are in my index thread.
Make a backup in recovery (just in case) and a wipe (advanced -> everything except int & ext sdcard) before.
Click to expand...
Click to collapse
Something I make wrong. I flashed TWRP, then installed ViperSV, phone restarted and booted TWRP. Then I found boot.img in yours index thead.
Then in fastboot flashed new boot, but phone still booting in TWRP. What I make wrong?
You need to flash the boot.img thats inside the ViperSV.zip, not any from my index thread.