Related
I rooted my sensation using the revolutionary method to get S=OFF and decided to put the phone back to S=ON so I could sell it and buy the new Galaxy S2 when it comes out this month.
I went through the process on the development forum to get S=ON and I used the correct RU file for TMOUS.
I made sure the CID was properly set using fastboot and it was set to TMOB010 so I could not flash to wrong RU file.
I flashed the RU file and it flashed fine and said the process completed with no errors.
I used the proper fastboot command to write the secureflag to 3 and the HBoot screen showed S=OFF and so far so good.
I rebooted the phone and the TMobile Sens ROM booted up fine to the home screen.
I shut the phone off figuring the process had been completed fine and when I turned the phone on an hour later, it booted to the HBoot screen with a "security warning" message.
Now all the phone will do is boot to the HBoot screen, I tried to re-flash the RU file like the forum stated but I keep getting a battery low error even with a fully charged battery.
Now all I have is a phone that only boots to the HBoot screen with a "security warning message"
The HBoot version is showing the following:
PYRAMID PVT SHIP S-ON RL
HBOOT-1.17.0008
RADIO-10.11.9007.15.M
eMMC-boot
I hope I do not have a 300 dollar paper weight, any help would be appricetd please.
My email is:
[email protected]
It's not bricked if you can turn it on... I can't help you much though... Seeing you got S-ON, maybe you could try to get S-OFF again and then start over?
Sent from my HTC Sensation Z710e
bakron1 said:
I rooted my sensation using the revolutionary method to get S=OFF and decided to put the phone back to S=ON so I could sell it and buy the new Galaxy S2 when it comes out this month.
I went through the process on the development forum to get S=ON and I used the correct RU file for TMOUS.
I made sure the CID was properly set using fastboot and it was set to TMOB010 so I could not flash to wrong RU file.
I flashed the RU file and it flashed fine and said the process completed with no errors.
I used the proper fastboot command to write the secureflag to 3 and the HBoot screen showed S=OFF and so far so good.
I rebooted the phone and the TMobile Sens ROM booted up fine to the home screen.
I shut the phone off figuring the process had been completed fine and when I turned the phone on an hour later, it booted to the HBoot screen with a "security warning" message.
Now all the phone will do is boot to the HBoot screen, I tried to re-flash the RU file like the forum stated but I keep getting a battery low error even with a fully charged battery.
Now all I have is a phone that only boots to the HBoot screen with a "security warning message"
The HBoot version is showing the following:
PYRAMID PVT SHIP S-ON RL
HBOOT-1.17.0008
RADIO-10.11.9007.15.M
eMMC-boot
I hope I do not have a 300 dollar paper weight, any help would be appricetd please.
My email is:
[email protected]
Click to expand...
Click to collapse
this needs to be addressed.
try sending a PM to the following people
- MikeChannon
- ClydeB1
- xl VipeR xl
jigners said:
this needs to be addressed.
try sending a PM to the following people
- MikeChannon
- ClydeB1
- xl VipeR xl
Click to expand...
Click to collapse
I may sound like a noob, but I never used the PM function on this site. I am so frustrated I want to throw the dam thing through the wall.
I can't understand why I keep getting the battery is below 30% error every time I try and run the RU file to re-flash the ROM. I have tried two different fully charged batteries with no luck.
Thank god I have my G2x and my Nexus S as backups, at least they be rooted and un-rooted very easily, unlike this POS.
If your H-Boot now reads S=On, technically there is no evidence to suggest that you have done anything, unless they can find a problem some other way, as you have said you used the correct ROM and CID. So you could try and return the handset under warranty. Someone correct me if im wrong
I also tried copying the RU programs rom.zip file and renaming it to PG581MG.zip and putting in on the SD card and tried flashing it through the Hboot screen but it scrolls thru the file and never ask me if I want to apply the update.
The fastboot function is probably enabled in the stock ROM i flashed and I am stuck in the HBoot screen. I am totally stumped.
Anyone out there willing to try and get this thing operational. I will pay you for your trouble as long as you are trustworthy.
My email is [email protected]
bakron1 said:
I also tried copying the RU programs rom.zip file and renaming it to PG581MG.zip and putting in on the SD card and tried flashing it through the Hboot screen but it scrolls thru the file and never ask me if I want to apply the update.
Click to expand...
Click to collapse
That's because the zip should be PG58IMG.zip and not PG581MG.zip
1.try different battery
2. Can you go into recovery? If yes try wiping from there. Also I believe in hboot there is factory reset option
3. Discharge battery and charge it up.again
Sent from my HTC Sensation Z710e using XDA App
tinky1 said:
1.try different battery
2. Can you go into recovery? If yes try wiping from there. Also I believe in hboot there is factory reset option
3. Discharge battery and charge it up.again
Sent from my HTC Sensation Z710e using XDA App
Click to expand...
Click to collapse
I appreciate the info, I have tried everything I know and I am stuck on the HBoot screen. I am going to try a different battery and try letting the original completely discharge and re-charge it and go from there. This is last sensation I am going to buy, I have never in all my years of rooting phones had a product that is a pain in the ass like this one has been.
Shame on HTC, what is the point of having an android product if not to root it and flash a custom ROM. I paid full retail for the thing with my hard earned money so I should be able to do with it what I want too.
I came over from the Nexus S and never had this many problems and complicated procedures going back to the stock ROM.
I am back to my G2x, at least I can easily root and un-root it and it runs the CM7 just fine. Not like the HTC POS.
bakron1 said:
I appreciate the info, I have tried everything I know and I am stuck on the HBoot screen. I am going to try a different battery and try letting the original completely discharge and re-charge it and go from there. This is last sensation I am going to buy, I have never in all my years of rooting phones had a product that is a pain in the ass like this one has been.
Shame on HTC, what is the point of having an android product if not to root it and flash a custom ROM. I paid full retail for the thing with my hard earned money so I should be able to do with it what I want too.
I came over from the Nexus S and never had this many problems and complicated procedures going back to the stock ROM.
I am back to my G2x, at least I can easily root and un-root it and it runs the CM7 just fine. Not like the HTC POS.
Click to expand...
Click to collapse
I think to fix it, you gotta clam down first lmao. I've NEVER had all these issues you're having. I don't mean to be rude, but I think it's the user... so relax! and fix it up!
as for the last sensation you're ever going to buy.. I think this will probably be the only sensation out there haha
Did you also try what this guy suggested?
M-M-C said:
That's because the zip should be PG58IMG.zip and not PG581MG.zip
Click to expand...
Click to collapse
Question was this the thread you used to unroot ?
http://forum.xda-developers.com/showthread.php?t=1192300
KAwAtA said:
I think to fix it, you gotta clam down first lmao. I've NEVER had all these issues you're having. I don't mean to be rude, but I think it's the user... so relax! and fix it up!
as for the last sensation you're ever going to buy.. I think this will probably be the only sensation out there haha
Did you also try what this guy suggested?
Click to expand...
Click to collapse
I finally fixed it!!!
I did have the right file name PG58IMG, but I kept getting an error when I tried to flash it through HBoot when the zip file was loading i.e. invalid image, no image found etc.
I tried the other RU file for TMOUS and extracted the rom.zip, renamed it and flashed it and it finally took and I am up and running.
I apologize for being upset but this was the longest time I ever spent trying to recover a phone, but I have learned allot from this experience and have taken some great notes and will put them in a thread when I get some free time.
Thanks to everyone out there who helped me through this.
bakron1 said:
I have learned allot from this experience and have taken some great notes and will put them in a thread when I get some free time.
Click to expand...
Click to collapse
Please do so since it would help others a LOT!
Glad you succeeded
bakron1 said:
I finally fixed it!!!
I did have the right file name PG58IMG, but I kept getting an error when I tried to flash it through HBoot when the zip file was loading i.e. invalid image, no image found etc.
I tried the other RU file for TMOUS and extracted the rom.zip, renamed it and flashed it and it finally took and I am up and running.
I apologize for being upset but this was the longest time I ever spent trying to recover a phone, but I have learned allot from this experience and have taken some great notes and will put them in a thread when I get some free time.
Thanks to everyone out there who helped me through this.
Click to expand...
Click to collapse
I am having the exact same problem from doing the EXACT same thing you did. My HBOOT, radio and everything else is exactly the same as yours as well. So my question is, was the RUU that worked properly for the older T-Mobile one? RUU_Pyramid_TMOUS_1.29.531.2_Radio_10.42.9007.00P_10.11.9007.15_M_release_193714 <-- This one??
Hi. I have similiar problem, but I can't extract zip file from RUU. With HD2 RUU I could unpack it with WINRAR, but with Sensation RUU there is no such option.
How did you extract rom.zip file from RUU... .exe file?
I am stuck at the same place can you please tell me how to extract the zip file from ruu and what is called I would really appreciate it
karankukkar said:
... can you please tell me ...
Click to expand...
Click to collapse
Sometimes I doubt if anyone else read this thread...
Tachion81 said:
How did you extract rom.zip file from RUU... .exe file?
Click to expand...
Click to collapse
Run the executable up to the initial screen and leave it open. Then open My Computer and browse to C:\Users\<username>\AppData\Local\Temp and you will see a folder with a long random looking name like {17ad63h46f09a0c883058}. Open this folder and you will see a heap of files - images for branding, scripts and the like, as well as a file called rom.zip. Open this file and in it will be radio.img, which you can extract and rename as PG58IMG.zip.
This is how I extracted the stock radio from my Telstra RUU anyway.
wmoore said:
Run the executable up to the initial screen and leave it open. Then open My Computer and browse to C:\Users\<username>\AppData\Local\Temp and you will see a folder with a long random looking name like {17ad63h46f09a0c883058}. Open this folder and you will see a heap of files - images for branding, scripts and the like, as well as a file called rom.zip. Open this file and in it will be radio.img, which you can extract and rename as PG58IMG.zip.
This is how I extracted the stock radio from my Telstra RUU anyway.
Click to expand...
Click to collapse
THX a LOT!
Hi guys
I have really strange problem, could you please help me out.
I am was using insert coin rom 4.4.1 and every thing was good so far,
Then i have realized that i have s- off and rooted my phone but i didn't super cid it
So i want to do that, i have supercid it by following the steps listed in this thread:
http://forum.xda-developers.com/showthread.php?t=1192300.
After i reboot the phone, it stayed in the flash screen (HTC screen)
I have reinstalled the rom and even other roms, but nothing was done.
I have tried to reflash it using firmwire 3.24 but samething.
FYI: i have already supercid it i have checked it by adb and it is 11111111
There is small problem, i didn't remember my proper cid, all i know it is a europe version of sensation.
i have this written in recovery session:
REVOLUTIONARY
pyramid PUT ship s off RL
boot 1.27.1110
Radio 11.21.3504.13.2
Open ADSP V02-6-0.2226.00.0104
EMMC-boot
Jan 13-2012, 17:33:34
Please help me i am lost here, DONT TELL ME THAT I HAVE DAMAGED THE PHONE!!
Thanks
Not sure if this will help
Hey I am not sure about your problem not heard of this. Maybe you need to super cid before flashing new firmware. Maybe if you can remember what your cid was before, you can change back and see if it makes any difference. maybe once returned to the stock cid you can revert firmware and then super cid. I am not sure though! I am just taking a stab at it since no one else has answered. here is a link with some firmware and it also tells stock cid's for different carriers/countries. Also maybe try flashing different firmware.
http://forum.xda-developers.com/showthread.php?t=1459767
maybe that will refresh your memory to what yours was.
Good Luck
P.S. I think that since you still have access to recovery you will be able to resolve the issue (not hard bricked yet), just need to figure out what the problem is exactly.
Given that you still have access to your SDcard, trying flashing a new rom and firmware (go for Virtuous Inquisition).
ungraph:
I have already tried other roms:
Android rev-hd 3-16-13: negative result
RCMix_ICS_v311_STbase: negative result
The problem is all roms stuck in the splash screen, i have looked in some threads that some people have 30 min for the first boot, for me i kept it for 1 hour or more but it seems that it is stuck, i have checked the temp it isn't hot so may be when i have supercid it , did i make something wrong to supercid it after installing the rom??
Noobzter said:
ungraph:
I have already tried other roms:
Android rev-hd 3-16-13: negative result
RCMix_ICS_v311_STbase: negative result
The problem is all roms stuck in the splash screen, i have looked in some threads that some people have 30 min for the first boot, for me i kept it for 1 hour or more but it seems that it is stuck, i have checked the temp it isn't hot so may be when i have supercid it , did i make something wrong to supercid it after installing the rom??
Click to expand...
Click to collapse
If you wanna use ARHD 3.6.13 you need to downgrade your firmware to 3.12 or 1.17 it won't run on 3.24
I would downgrade your firmware, go to a GB rom, get it so your phone boots, then go through the process of going back to ICS.
Noobzter said:
ungraph:
I have already tried other roms:
Android rev-hd 3-16-13: negative result
RCMix_ICS_v311_STbase: negative result
The problem is all roms stuck in the splash screen, i have looked in some threads that some people have 30 min for the first boot, for me i kept it for 1 hour or more but it seems that it is stuck, i have checked the temp it isn't hot so may be when i have supercid it , did i make something wrong to supercid it after installing the rom??
Click to expand...
Click to collapse
Last time when I had major issue with my phone, I flashed couple different firmwares and different ICS and GB ROM. And somehow it worked for me. I'm just saying there's always hope. Dont give up! And good luck!
flash the latest official eu RUU, if nothing works.
You can always s-off/root then afterwards.
Where has InsertCoin Rom gone?? It appears to have disappeared!
Sent from my HTC Sensation Z710e using xda premium
Guys now there is something changed
When i`m trying to install another firmwire i have noticed that in hboot "revolutionary" (in purple) was changed to "locked"
What does it means??
roose21 said:
Where has InsertCoin Rom gone?? It appears to have disappeared!
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Thread was deleted at his request, as was his XDA account.
Noobzter said:
Guys now there is something changed
When i`m trying to install another firmwire i have noticed that in hboot "revolutionary" (in purple) was changed to "locked"
What does it means??
Click to expand...
Click to collapse
Nothing, most do not use fastboot commands, so don't worry about it. You are still s-off and able to flash any rom you desire.
Noobzter said:
Guys now there is something changed
When i`m trying to install another firmwire i have noticed that in hboot "revolutionary" (in purple) was changed to "locked"
What does it means??
Click to expand...
Click to collapse
you need to STOP flashing random firmware...if you don't know what it is and what the outcome is going to be, do not flash it
follow these instructions:
Kohr-Ah said:
I would downgrade your firmware, go to a GB rom, get it so your phone boots, then go through the process of going back to ICS.
Click to expand...
Click to collapse
I have downgraded my firmwire to 3.12 and i have used hd 3.16.13 GB rom.
The bad news is that nothing done yet, stucking in HTC splash screen.
But there is something i want to add, may be is the clue to this problem .
I have realized that when i remove my SD card from the phone and i want to read it in my PC, it appears protected each time and this is strange (virus effect).
may be my SD card was damaged and it is the only problem of stucking???
What do you think guys??
Noobzter said:
I have downgraded my firmwire to 3.12 and i have used hd 3.16.13 GB rom.
The bad news is that nothing done yet, stucking in HTC splash screen.
But there is something i want to add, may be is the clue to this problem .
I have realized that when i remove my SD card from the phone and i want to read it in my PC, it appears protected each time and this is strange (virus effect).
may be my SD card was damaged and it is the only problem of stucking???
What do you think guys??
Click to expand...
Click to collapse
Perhaps you accidentally set some sort of sharing protection on the SD card, which doesn't let the phone access the adequate files? If so, try reformatting your card on fat32. And then copy back the firmware/rom and attempt flashing again.
i have already formatted the SD card, coping Rom and firmwire PG58IMG reflash the rom .
Still stuck in HTC S screen.
What about RUU?
Any suggestion ?
Hi guys
i have used the cmd to see my cid
i entred by bootloader menu then go to recovery menu
I have written in cmd "adb devices" then it is written
list of devices attached shxxxxxxxx my number, then i wrote "fastboot getvar cid" then it stayed in <waiting for device> normally it gave me my proper cid 11111111
Am i making something wrong??
I am exausted guys!! please help me out!
Noobzter said:
Hi guys
i have used the cmd to see my cid
i entred by bootloader menu then go to recovery menu
I have written in cmd "adb devices" then it is written
list of devices attached shxxxxxxxx my number, then i wrote "fastboot getvar cid" then it stayed in normally it gave me my proper cid 11111111
Am i making something wrong??
I am exausted guys!! please help me out!
Click to expand...
Click to collapse
If your bootloader says LOCKED like you previously indicated then you can not use fastboot commands as kpjimmy already said. Because you never supercid your phone you probably have some partial firmware update.
If I were you I would flash an older RUU to get to a known stable config and then start over.
No i have changed the firmwire and it is written revolutionary in purple.
Noobzter said:
i have already formatted the SD card, coping Rom and firmwire PG58IMG reflash the rom .
Still stuck in HTC S screen.
What about RUU?
Any suggestion ?
Click to expand...
Click to collapse
You have to remove the firmware from the card after flashing it. But to bypass it, does your phone boot once you flash the rom and then remove the sd card?
kpjimmy
when i updated the firmware hboot then the phone wrote push the power button to reboot, the problem is the phone will try to run the rom already installed in the phone, so i am forced to remove the battery and then remove the firmware from my PC.
in order to install the new rom.
I got a bricked T-mobile Sensation today at the shop and after checking it out I thought it would be easy to fix but unfortunately its proving to be much more difficult than I expected. Here's what I'm working with:
Locked s-on
Hboot 1.18.0000
radio 10.14.9035.01_m
First, I tried all kinds of PG58 zips. None worked. I figure I need to be unlocked to do it. Did the HTC unlock and got to the warning screen and where it asks to choose yes or no. I can navigate to yes or no but when I choose yes it just freezes and doesn't do anything. I tried it 3 different times, same thing. I can't even choose factory reset in Hboot, it just freezes. I don't know what the eff is going on. I've been downloading RUUs but have yet to find the correct one. I don't know what firmware it has because it does not boot up.
I thought, well shoot, I have fastboot, maybe I could just s-off and root from fastboot, but I can't find any thread explaining how to do it.
Any help would be great.
Thanks!
Edit:
Found the correct RUU, 1.50.xxxx whatever. WHen I run the utility It says its rebooting into bootloader but stays in the same screen and doesn't do anything. I don't know if this helps, but when I go into the bootloader I cannot go back into hboot. It just, freezes.
Have you tried this guide?
http://forum.xda-developers.com/showthread.php?t=1192300
And you need to be s-off to flash those pg58 zips, thats why they failed.
As you're on HBOOT 1.18.0000 use the revolutionary method to get S-OFF. http://revolutionary.io
The HTC unlock is a bit redundant as it doesn't give S-OFF which you need.
There are many guides here on XDA to help you. Such as:
http://forum.xda-developers.com/showthread.php?t=1192300
EDIT: Oops didn't notice that "Kazireh" has already posted the link.
You'll need the HTC drivers (download HTC Sync install it then delete HTC Sync leaving the drivers installed).
You should also get the ADB tools installed as at some stage they'll be useful.
As far as the RUU is concerned you need to make sure it's the right one for the current CID on the phone.
Kazireh said:
Have you tried this guide?
http://forum.xda-developers.com/showthread.php?t=1192300
And you need to be s-off to flash those pg58 zips, thats why they failed.
Click to expand...
Click to collapse
gol_n_dal said:
As you're on HBOOT 1.18.0000 use the revolutionary method to get S-OFF. http://revolutionary.io
The HTC unlock is a bit redundant as it doesn't give S-OFF which you need.
There are many guides here on XDA to help you. Such as:
http://forum.xda-developers.com/showthread.php?t=1192300
EDIT: Oops didn't notice that "Kazireh" has already posted the link.
You'll need the HTC drivers (download HTC Sync install it then delete HTC Sync leaving the drivers installed).
You should also get the ADB tools installed as at some stage they'll be useful.
As far as the RUU is concerned you need to make sure it's the right one for the current CID on the phone.
Click to expand...
Click to collapse
Thanks for the help guys, but heres the deal:
I cannot s-off due to it not being able to boot.
I could try Junopbears s-off but I cannot unlock, as it just freezes when I try.
I found the correct ruu but again it freezes and does not boot into the bootloader.
My CID is T-mob010
I have all drivers installed, adb, fastboot, etc
If your on hboot 1.18 you have a gingerbread fw, look for that
Sent from my HTC Sensation 4G
its completely possible that the motherboard is failing. I see this in my shop all the time, though usually with the MyTouch 4G (faulty eMMC chip) but the sensation and a few other HTC's also see this. we havent come up with a solution between my two stores employees, so hopefully someone here can?
q said you did not understand, is how I explain more thoroughly I am new to the subject
and my device does not enter the system and when using the mode prop vo comand says device not found what to do? sensation with my ta hboot 1.27.0000 s-s on rl unloked help me
2strokenut said:
Thanks for the help guys, but heres the deal:
I cannot s-off due to it not being able to boot.
Click to expand...
Click to collapse
Can you get into "Fastboot USB" ?
I could try Junopbears s-off but I cannot unlock, as it just freezes when I try.
Click to expand...
Click to collapse
Junopbear is wrong as it's for 1.2x.xxxx HBOOT, try Revolutionary.
I found the correct ruu but again it freezes and does not boot into the bootloader.
My CID is T-mob010
Click to expand...
Click to collapse
Eek.
T-MOB010 == RUU x.xx.531.xxxxxxxxx according to my list.
I have all drivers installed, adb, fastboot, etc
Click to expand...
Click to collapse
Good.
There are a few "unbrick" guides, never tried to use them so can't help on that front.
nickL0V3 said:
its completely possible that the motherboard is failing. I see this in my shop all the time, though usually with the MyTouch 4G (faulty eMMC chip) but the sensation and a few other HTC's also see this. we havent come up with a solution between my two stores employees, so hopefully someone here can?
Click to expand...
Click to collapse
Yeah that's what I'm leaning toward right now, there is nothing else I can do. I have 4 or 5 Mytouchs on the shelf with bad eMMc chips so I guess this one is joining them.
gol_n_dal said:
Can you get into "Fastboot USB" ?
Junopbear is wrong as it's for 1.2x.xxxx HBOOT, try Revolutionary.
Eek.
T-MOB010 == RUU x.xx.531.xxxxxxxxx according to my list.
Good.
There are a few "unbrick" guides, never tried to use them so can't help on that front.
Click to expand...
Click to collapse
Yes the RUU was 1.50.531.xxxxxx
Yes, I can get into Fastboot usb, I can do fastboot commands, it just freezes when the RUU tries to do its thing.
Jbear would still work if the bootloader were locked, but I couldn't unlock the bootloader. Revolutionary will not work either because its run while the phone is on, which I can't do.
I think I've exhausted every option, it seems to all point to a failed eMMc chip, shame though, I really like these phones.
Thanks for the help fellas
GL
///////////////
hello
having (what i am now convinced is) a hardware issue with my phone, where it periodically shuts itself down, typically when its idle, although it has happened when i have been using it. Have to do a long press on the thing (around 15-20 seconds), to bring it back to life
Its a Telstra HTC One XL.
phone doesnt seem to be overheating etc.
i have rooted, s-off'd, superCIDd, the thing, so when its booting, i am met with tampered/unlocked in hboot, with the initial HTC splashscreen saying that this build is for dev purposes.
have tried numerous ROMs etc, and am now back on a stock/rooted telstra rom.
Interestingly, the phone never locks up/shuts down when in recovery or fastboot (have left for a good 30 minutes/1 hr)
i am looking for a simple way to revert everything back to its original state, i know that if i simply re-lock the bootloader, it comes up with 'relocked', have looked at some other posts which say that you can use a hex editor to change the hboot text.
i am curious, if i wipe out all the relocked/tampered stuff, and then reflash the stock RUU, will that reset the hboot etc? i think i need to relock to reflash the stock RUU.
i am tempted to just hex edit the hboot stuff, uninstall SuperSU from the phone, and hopefully the repair guys arent that smart and dont look beyond some basic stuff..
the 'this build is for htc dev purposes' might be more difficult to remove...
Telstra wont do a warranty repair on a rooted phone!
if anyone has any ideas to the cause of the shutdowns, troubleshooting suggests, that would be great... there are no weird or wonderful apps installed
First thing is definitely try to RUU. If that doesn't work, I (or someone else) will help you after that.
You can remove the red text on the splash screen pretty easily, here's a link:
http://forum.xda-developers.com/showthread.php?t=2156368
Sent from my Evita
yeah, thats the red text (tampered), will that get overwritten if i relock and then RUU? (i am pretty sure i will need to relock before RUU)
also, whats the standard text on the hboot screen? (if you havent super CIDd)
If you are s-off you don't need to relock to run the RUU.
Sent from my Evita
ok, so try the RUU, see if that fixes the shutdowns? if it doesnt, use that util to change all the hboot text, and take it back to the shop, and see if they are to dumb to notice?
Yep I think that's the best plan. RUU it and keep running that for a couple of days to see if you have an improvement. If not, it's likely a hardware issue.
Sent from my Evita
ok, cool, and do you know if i need to re-unlock the bootlader after the RUU? or if i am s-off i can change the hboot text etc?
gjw00 said:
ok, cool, and do you know if i need to re-unlock the bootlader after the RUU? or if i am s-off i can change the hboot text etc?
Click to expand...
Click to collapse
There's no need to relock the boot loader if you're s-off. You can change the hboot and some bootloader text using the tool in the Android Development forum for this phone.
Pretty sure its hardware, same after ruu installed. At least now it restarts, usually after shutting off screen or taking off charger. Gonna use that util to change text back to s-on etc, doesn't say tampered, which is cool (must be ruu). What do I need to set to get rod of the cid-1111111 entry in hboot? What is default Telstra text? Hopefully they won't dig too deep.in the repaier shop!!
gjw00 said:
Pretty sure its hardware, same after ruu installed. At least now it restarts, usually after shutting off screen or taking off charger. Gonna use that util to change text back to s-on etc, doesn't say tampered, which is cool (must be ruu). What do I need to set to get rod of the cid-1111111 entry in hboot? What is default Telstra text? Hopefully they won't dig too deep.in the repaier shop!!
Click to expand...
Click to collapse
Ok so you'll need to RUU, relock the bootloader, change the text, change the CID, and the last thing you'll want to do is make it s-on.
The fastboot command to change the cid is:
fastboot oem writecid TELST001
I can't remember the command to make it s-on again, Google that, but it s-off be the very last thing you do after all other steps.
Sent from my Evita
cant i just change all the text, to make it 'look like' its s-off etc?
sorry for all the questions, do i just need s-off to write the hboot text etc?
I don't think you can change the s-off text. I think you can only change the tampered/unlocked/relocked text.
And yes you need s-off to write change that text and to change the CID back.
Sent from my Evita
thanks for the tips, i think that util changes text to s-off, although it might be better, to set everything back as normal (RUUd/relocked/s-off), at one point i thought that reverting all that stuff was not possible...
cannot get rid of the **RELOCKED** text.. that little util doesnt seem to remove that
Hmm you might be SOL then. Telstra are pretty strict when it comes to this stuff I think. I know Optus are, I used to work for a place did that took care of Optus repairs and warranties.
Sent from my Evita
managed to do it, now says ***LOCKED***, had to reunlock bootloader for that text to change
Good outcome, got all bootloader text back to standard, put the ruu on. Telstra repaired I within a few days by essentially giving me a brand new phone. All the battery issues (very fast standby drain) are also gone.
2 days in and resisting the temptation to root!
Hi, new to the forums and completely perplexed by this rom root flashing stuff. I have tried following some guides but I'm just not sure that they are applicable in my circumstance:
Situation:
1. Complete technophobe sister came back from holiday complaining she needed a new battery for her Sensation as it just kept rebooting over and over.
2. This phone has NEVER been modded or flashed or god knows what. It was unlocked from its carrier (Vodafone) though by the previous owner. Bought in the UK.
3. I had another spare battery and used that. Same situation.
4. I started googling. Lots of people with similar situations but not identical. Key difference is that all of them have meddled with their devices FIRST and THEN got into this bootloop.
5. All the advice is therefore a few steps ahead of where I am and is leaving me confused and puzzles.
What the device can/can't do:
I can get to the Boot menu and navigate it
I cannot boot into Android proper as it were.
"Recovery" and "Factory Reset" both send the phone into its boot loop cycle.
Defining what I call a bootloop:
Goes to the blank white screen with HTC logo then off then rinse and repeat over and over.
What I have done:
I tired following some links from some of these threads and did a SuperCID??? (the thing where you go to cmd and do fastboot-reboot 11111111 or something similar) as all the threads kept complaining that the OP hadn't done this yet. This seemed to be successful but the instructions following then didn't seem to apply.
Other info you might need?
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.29A350418_M
OpenADSP-v)".6/0/2266.00.0131
eMMC-boot
Jan 13 2012,17:33:34
I hope I have written all you need. Apologies if I have not.
theonetruewill said:
Hi, new to the forums and completely perplexed by this rom root flashing stuff. I have tried following some guides but I'm just not sure that they are applicable in my circumstance:
Situation:
1. Complete technophobe sister came back from holiday complaining she needed a new battery for her Sensation as it just kept rebooting over and over.
2. This phone has NEVER been modded or flashed or god knows what. It was unlocked from its carrier (Vodafone) though by the previous owner. Bought in the UK.
3. I had another spare battery and used that. Same situation.
4. I started googling. Lots of people with similar situations but not identical. Key difference is that all of them have meddled with their devices FIRST and THEN got into this bootloop.
5. All the advice is therefore a few steps ahead of where I am and is leaving me confused and puzzles.
What the device can/can't do:
I can get to the Boot menu and navigate it
I cannot boot into Android proper as it were.
"Recovery" and "Factory Reset" both send the phone into its boot loop cycle.
Defining what I call a bootloop:
Goes to the blank white screen with HTC logo then off then rinse and repeat over and over.
What I have done:
I tired following some links from some of these threads and did a SuperCID??? (the thing where you go to cmd and do fastboot-reboot 11111111 or something similar) as all the threads kept complaining that the OP hadn't done this yet. This seemed to be successful but the instructions following then didn't seem to apply.
Other info you might need?
PYRAMID PVT SHIP S-ON RL
HBOOT-1.27.0000
RADIO-11.29A350418_M
OpenADSP-v)".6/0/2266.00.0131
eMMC-boot
Jan 13 2012,17:33:34
I hope I have written all you need. Apologies if I have not.
Click to expand...
Click to collapse
You could try putting paper or cardboard between the battery and the back cover to keep snug and fit.
If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya
AndroidSupporter318 said:
You could try putting paper or cardboard between the battery and the back cover to keep snug and fit.
If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya
Click to expand...
Click to collapse
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).
astar26 said:
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).
Click to expand...
Click to collapse
Some phones do have superCID with s-on. Iv seen it with the htc desire / s
jmcclue said:
Some phones do have superCID with s-on. Iv seen it with the htc desire / s
Click to expand...
Click to collapse
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.
astar26 said:
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.
Click to expand...
Click to collapse
I have put card in-between this to keep it secure before on a trial and error when it was having connection issues. It is not this that is the problem. Thank you for your input though.
astar26 said:
Anyway, checking the CID before doing anything should be good, just to be safe. And at least as far as I know, it's only possible to achieve SuperCID while S-OFF (possible to S-ON later, but to achieve you must have S-OFF at the time). But this doesn't matter to the problem at hand.
Click to expand...
Click to collapse
How do I do this. Please bear in mind I have not rooted etc before. I performed Step 4 of this guide before and that is why I believed I had done this. http://forum.xda-developers.com/showthread.php?t=1192300
I'd like to add just because you do not seem to be S-OFF, which means you don't have SuperCID, pick an RUU based on your device's CID, else it will not work. check what your CID is and pick the RUU compatible with it. It should be what the phone came with (same region and carrier).
I believe RUU should fix this issue, so you should definitely try that. SuperCID cannot be achieved while S-ON, but it doesn't really matter in your situation (unless you can't find the appropriate RUU).
Click to expand...
Click to collapse
This is where I got confused and started to seek assistance. I have no idea what my CID is or really how to use an RUU or what one to pick. It was a UK Vodafone handset but I don't know how this corresponds to anything or what to do about it.
AndroidSupporter318 said:
...If that doesn't work, then I would try to run a ruu.exe to restore the phone to stock. Look here for ruu.exe: http://forum.xda-developers.com/showthread.php?p=26541170
Sent from my Ouya
Click to expand...
Click to collapse
When I do (and did before) step 3 I just get a list of commands and no current software version showing. This was exactly when I came here. I thus went no further as what I had did not correspond.
If you got your device from UK vodaphone then this should be your RUU (got it from RUU thread in Sensation Development).
if you want to check CID (you need adb and fastboot with device drivers on your computers, I'll explain in short (and assume you have the tools)):
connect phone to computer with USB debugging enabled
-adb reboot bootloader
when bootloader starts, run this:
-"fastboot getvar cid"
this will give you the CID your device has.
astar26 said:
If you got your device from UK vodaphone then this should be your RUU (got it from RUU thread in Sensation Development).
if you want to check CID (you need adb and fastboot with device drivers on your computers, I'll explain in short (and assume you have the tools)):
connect phone to computer with USB debugging enabled
-adb reboot bootloader
when bootloader starts, run this:
-"fastboot getvar cid"
this will give you the CID your device has.
Click to expand...
Click to collapse
I just get a series of commands and what they do. I don't get anything else. I can also not check if USB debugging is enabled as the phone wont turn on to turn it on.
jmcclue said:
Some phones do have superCID with s-on. Iv seen it with the htc desire / s
Click to expand...
Click to collapse
in the sensation forums no one reported that he had supercid while on S-ON
theonetruewill said:
I just get a series of commands and what they do. I don't get anything else. I can also not check if USB debugging is enabled as the phone wont turn on to turn it on.
Click to expand...
Click to collapse
open the cmd window in the folder where you have adb and fastboot files and perform there the command
also make sure that in hboot screen it shows fastboot usb
rzr86 said:
in the sensation forums no one reported that he had supercid while on S-ON
Click to expand...
Click to collapse
Hi. Maybe no one has reported it but u can have supercid with s-on, and i dont mean by going s-off first. It is very rare tho, like if u work for lets say vodafone then u can get a stock s-on phone with supercid. For development r something i think. But like i said, its very rare that us general public get our hands on them. But it is possible
Got it to show my cid. Error when flashing the rom using the executable file. Will try again when back from work
Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.
theonetruewill said:
Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.
Click to expand...
Click to collapse
maybe you used an RUU of SE when you are not (or otherwise, regular for XE). beside CID, there is MID. the procedure of adding your MID and checking the MID is similiar to the CID.
MID indicates your model - in this case mainly three are possible: one for regular sensation, one for XE, and one for 4G.
theonetruewill said:
Getting stuck at step 4.2/4.3 of this guide (http://forum.xda-developers.com/showthread.php?p=26541170). The archive is always corrupt and thus changes cannot be made to the text file. I can't do 4.3 because it says error not correct id (ERROR [130]: MODEL ID ERROR)and it directs back to 4.2. Any suggestions?
I have also tried HTCs own flash update (https://support.htc.com/en-us/HTC_S..._Updates/Software_Update_for_HTC_Sensation_4G) this also fails to work for exactly the same reasons.
Click to expand...
Click to collapse
when you are trying to add your cid to the text file don't extract it
just open it as it is,add your cid and then save it
rzr86 said:
when you are trying to add your cid to the text file don't extract it
just open it as it is,add your cid and then save it
Click to expand...
Click to collapse
I am doing this. The zipped folder is unable to be opened in windows explorer (opened not extracted) as it says it is not valid. I then tried to use winrar to open it (not extract it) This worked. However when I attempt to save the modifications it says archive corrupt and unable to save.
I can't even do the S-OFF then Super CID thing because my HBOOT (1.27.0000) isn't listed here..... http://revolutionary.io
Managed to get a RUUto flash to it - http://freakshare.com/files/gt7345y....23.3504.07_M2_release_251541_signed.exe.html
Unfortunately this has not fixed the problem. I suspect this may be terminal. Any suggestions?
HI there guys, I have the phone in my hands now.
Will is one of my close friends and I plan to get it back alive.
I'll try and look around and post questions here, as I'm not familiar with HTC devices.
I've flashed god knows how many Samsung's and helped quite a few hundred thousand people with flashing via ODIN.
To me: The phone seems locked, and stuck in a bootloop.
Wiping doesn't resolve the issue, nor does trying to flash another firmware as it comes with errors.
theonetruewill said:
I can't even do the S-OFF then Super CID thing because my HBOOT (1.27.0000) isn't listed here..... http://revolutionary.io
Click to expand...
Click to collapse
with that hboot version you can only use juopunutbear method to S-OFF the device
try to unlock the bootloader via htcdev site
flash a custom recovery(i suggest 4ext)
flash a custom rom from recovery(before flashing enable smartflash from 4ext)
---------- Post added at 02:55 AM ---------- Previous post was at 02:54 AM ----------
TotallydubbedHD said:
HI there guys, I have the phone in my hands now.
Will is one of my close friends and I plan to get it back alive.
I'll try and look around and post questions here, as I'm not familiar with HTC devices.
I've flashed god knows how many Samsung's and helped quite a few hundred thousand people with flashing via ODIN.
To me: The phone seems locked, and stuck in a bootloop.
Wiping doesn't resolve the issue, nor does trying to flash another firmware as it comes with errors.
Click to expand...
Click to collapse
post your bootloader details and what exactly did you do ?
---------- Post added at 02:58 AM ---------- Previous post was at 02:55 AM ----------
theonetruewill said:
I am doing this. The zipped folder is unable to be opened in windows explorer (opened not extracted) as it says it is not valid. I then tried to use winrar to open it (not extract it) This worked. However when I attempt to save the modifications it says archive corrupt and unable to save.
Click to expand...
Click to collapse
do it with notepad++