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!
i was wondering if there is a way to do this. ??
im tired of my MTS4G, i want to install a good rom!
Amen to that
Sent from my myTouch_4G_Slide using Tapatalk
As of right now no, were all basically stuck. Htc say they'll release a update at the end of the month to allow unlocking but that will void your warranty. Im just waiting for a crack for this version. Shouldn't Be too long i hope.
Sent from my myTouch_4G_Slide using Tapatalk
I did not realize that this phone still had an unlocked bootloader when I purchased it a few days ago. It's unfortunate how the HTC Unlocker was glitchy with the MT4GS; it might be why there's such a lack of development right now, haha.
ac3theone said:
As of right now no, were all basically stuck. Htc say they'll release a update at the end of the month to allow unlocking but that will void your warranty. Im just waiting for a crack for this version. Shouldn't Be too long i hope.
Sent from my myTouch_4G_Slide using Tapatalk
Click to expand...
Click to collapse
i hope!! i dont care about the warranty, i hate the stock the sence , is so slow and i hate the interface, im comming from a vibrant runing ics passion v12, you can only imagine my frustration .
Limewirelord said:
I did not realize that this phone still had an unlocked bootloader when I purchased it a few days ago. It's unfortunate how the HTC Unlocker was glitchy with the MT4GS; it might be why there's such a lack of development right now, haha.
Click to expand...
Click to collapse
I think we can start shelving the idea that there's a lack of dev for the device - some definite strides being made in that direction now.
We could always use more people helping make stuff, though.
----
I need a copy of an S-ON bootloader that has not been unlocked.
I need both S-ON 1.44.0007 and S-ON 1.45.0013 - if anyone can get either to me that would be great.
They are only 1MB in size and can be attached to a post in the forum.
If you can get it - attach it as a reply to this post:
http://forum.xda-developers.com/showthread.php?t=1254518
The terminal command to back up a copy of it is:
Code:
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
That will place a copy of your hboot on your sdcard, called hboot.img, if run from a terminal.
Nlarge got his unlocked S-ON bootloader added to that thread, now we need some regular S-ON ones to compare them to. If anyone can figure out how to get one to us it would be helpful.
We are trying to work the S-ON issue, but it's not exactly an easy nut to crack and we've mostly just started.
Thanks for any help that can be provided. This may not be all we need, but it's a start.
Hasn't anyone been able to flash the original PG59IMG.zip via the OTAbootloader patch?
Delivered via candygram for Mr. Mongo.
Blue6IX said:
I need a copy of an S-ON bootloader that has not been unlocked.
I need both S-ON 1.44.0007 and S-ON 1.45.0013 - if anyone can get either to me that would be great.
They are only 1MB in size and can be attached to a post in the forum.
If you can get it - attach it as a reply to this post:
http://forum.xda-developers.com/showthread.php?t=1254518
The terminal command to back up a copy of it is:
Code:
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
That will place a copy of your hboot on your sdcard, called hboot.img, if run from a terminal.
Click to expand...
Click to collapse
I'll see if I can figure out how to get that to you. If I can't code, at least I can help with other things.
Cool, we'll look it over and see what we come up with. No promises, just gonna look and see what we see and hope it leads to something.
The hboot may or (more likely) may not be the whole problem for s-off/s-on, but the more we have to play with the more we are learning.
Blue6IX said:
Cool, we'll look it over and see what we come up with. No promises, just gonna look and see what we see and hope it leads to something.
The hboot may or (more likely) may not be the whole problem for s-off/s-on, but the more we have to play with the more we are learning.
Click to expand...
Click to collapse
I tried to copy it with (adb shell <command>) but it says I have permission denied.
Limewirelord said:
I tried to copy it with (adb shell ) but it says I have permission denied.
Click to expand...
Click to collapse
Okay, we are working on that, etn4off is leading the charge on adb through stock recovery, so hold that thought.
Meantime, i've whipped up a new version of the stock restore .zip file, that should work on the new OTA.
( Make sure you have a full battery first!)
Edit - didn't work
What you have to do is rename the file to:
PG59IMG.zip
...then place on the main directory of your sdcard.
Make sure fastboot is turned off in settings on the phone, and then power off.
Hold Volume Down and press Power to turn it on, booting into hboot. The installer will take over from there and guide you through it.
It will load itself, then ask you to press Volume UP to install - then does it's thing and will tell you to press power to reboot when it is done.
This is basically the same restore file you get from here: Thread Link updated for the new OTA.
This should solve the version mismatch problem people were having, but won't know until someone tries to install it.
Afterwards you can run Revolutionary to S-OFF your 1.44.0007 hboot.
You will no longer be on the newest OTA, but then you can apply it if you want and go back - as long as you run the Revolutionary process on the 1.44.0007 hboot before you do.
I'm going to try this asap
Sent from my myTouch_4G_Slide using Tapatalk
Blue6IX said:
Okay, we are working on that, etn4off is leading the charge on adb through stock recovery, so hold that thought.
Meantime, i've whipped up a new version of the stock restore .zip file, that should work on the new OTA.
( Make sure you have a full battery first!)
Stock_Retail_OTA_1-55-531-3_downgrade_PG59IMG.zip
Download link
MD5: c7ea224be738b14824a003fd9c9b4b19
What you have to do is rename the file to:
PG59IMG.zip
...then place on the main directory of your sdcard.
Make sure fastboot is turned off in settings on the phone, and then power off.
Hold Volume Down and press Power to turn it on, booting into hboot. The installer will take over from there and guide you through it.
It will load itself, then ask you to press Volume UP to install - then does it's thing and will tell you to press power to reboot when it is done.
This is basically the same restore file you get from here: Thread Link updated for the new OTA.
This should solve the version mismatch problem people were having, but won't know until someone tries to install it.
Afterwards you can run Revolutionary to S-OFF your 1.44.0007 hboot.
You will no longer be on the newest OTA, but then you can apply it if you want and go back - as long as you run the Revolutionary process on the 1.44.0007 hboot before you do.
Click to expand...
Click to collapse
Has anyone tried this? Not that im saying its bad i just dont want to mess up my newest toy...lol
Sent from my myTouch_4G_Slide using Tapatalk
izzy001 said:
Has anyone tried this? Not that im saying its bad i just dont want to mess up my newest toy...lol
Sent from my myTouch_4G_Slide using Tapatalk
Click to expand...
Click to collapse
No. That's why I said we won't know until someone tries.
I've run the package on both of my devices, so can attest to it working - but they are both s-off.
I've run it from the device in the newest OTA form, and it brought me back, but the old package did too - seems no version check on my devices (probably any s-off devices)
I've run from all versions of the hboot - 1.44.0006, 1.44.0007, 1.44.1107, and 1.45.0013, but they were all s-off.
As for what happens with an s-on device... ...? I updated the version because in another thread that was pinpointed as the problem for it not installing on the newest OTA.
Blue6IX said:
No. That's why I said we won't know until someone tries.
I've run the package on both of my devices, so can attest to it working - but they are both s-off.
I've run it from the device in the newest OTA form, and it brought me back, but the old package did too - seems no version check on my devices (probably any s-off devices)
I've run from all versions of the hboot - 1.44.0006, 1.44.0007, 1.44.1107, and 1.45.0013, but they were all s-off.
As for what happens with an s-on device... ...? I updated the version because in another thread that was pinpointed as the problem for it not installing on the newest OTA.
Click to expand...
Click to collapse
Well i tried it... But it didnt even see it as an update... It just checked it and went straight to the hboot menu
Sent from my myTouch_4G_Slide using Tapatalk
izzy001 said:
Well i tried it... But it didnt even see it as an update... It just checked it and went straight to the hboot menu
Sent from my myTouch_4G_Slide using Tapatalk
Click to expand...
Click to collapse
Okay thanks, it was pretty much an 'it will do it or it won't' situation, so we'll have to try something else.
I wish I could get an s-on device in my hands that I could try stuff on - for now it's test and test and test on the s-off, then try on the s-on ...
Sorry it didn't work, we'll have to try another way.
I'll give this a try as well, even though it supposedly doesn't work. Better try than not.
Is what you're trying to do make the older ROM (with the 1.44.0007 HBOOT) appear as an update to the newer update so we can, in a way, downflash to the older HBOOT that's compatible with the Revolutionary tool?
I'm kind of new to the whole Android scene and am just curious as to how things work.
Limewirelord said:
I'll give this a try as well, even though it supposedly doesn't work. Better try than not.
Is what you're trying to do make the older ROM (with the 1.44.0007 HBOOT) appear as an update to the newer update so we can, in a way, downflash to the older HBOOT that's compatible with the Revolutionary tool?
I'm kind of new to the whole Android scene and am just curious as to how things work.
Click to expand...
Click to collapse
If this flashes it should revert the phone back to retail launch - but it's probably not going to. Finding a way to force it could have a less then desirable outcome.
If it doesn't take, don't try to force the issue with it unless you know what you're doing and why.
Well I tried it as well and it got a check, but it didn't install anything. I wish I had the know-how to mess around with this stuff.
Limewirelord said:
Well I tried it as well and it got a check, but it didn't install anything. I wish I had the know-how to mess around with this stuff.
Click to expand...
Click to collapse
When it checks and oks it go to recovery in hboot menu
Sent from my myTouch_4G_Slide using Tapatalk
ok like the title says ive been messing with this thing for a week now and im getting to the point im about to smash it with a hammer
its stuck in a boot loop and i have no backup to load apparently. it was rooted when i got it and my roomate messed it up while i was at work im not sure how or what was done but no matter what i try to do i cant get it out of this loop. im not familiar with android at all ive been reading and searching but i cant find anything helpful ive tried to ruu a few times not really knowing which files to use i finally found out that the radio needed to be the same found a matching file but still no luck i know im gonna get flamed for being so uneducated in this matter but i have indeed searched and i feel im left with no other option then to ask for assistance here
i can get to the boot loader and im just going to type down exactly what i see on it although i dont really know what any of it means
***tampered***
***unlocked***
evita pvt ship s-on rl
hboot-1.14.0002
radio-0.19as.32.09.11_2
opendsp-v29.1..0.45.0622
emmc-boot
jun 11 2012,14:36:28
fastboot usb
vol up
vol down
power
fastboot
recovery
factory reset
clear storage
simlock
image crc
power down
im in need of a thourough stepo by step instruction on how to fix this thing i dont care if its by means of a custom rom stock rom whatevers easiest. i know how to utilize fastboot with instruction and ive changed back and forth between cwm and twrp but no matter how many tuts i follow i always end up in a loop and im not sure why again i apologize for being such a noob but ive come to realize that this forum is the best at fixing stupid problems like mine fairly quickly
thanks in advance for your help....
Alright, is there a custom recovery installed on it? Go to recovery from bootloader menu and it it says TWRP or CWM then there is.
Edit: Also, I'm assuming you have no knowledge of adb and fastboot commands? Because you might need to learn. And did you try this ruu? It's for your firmware version. http://forum.xda-developers.com/showthread.php?t=1814217
RollTribe said:
Alright, is there a custom recovery installed on it? Go to recovery from bootloader menu and it it says TWRP or CWM then there is.
Click to expand...
Click to collapse
yes i can get to the custom recovery but it seemes like everytime i try to go into it it falls back into a loop unless i flash it and then imiediatly go into it but right now i have twrp on here
im downloading that one now and ill give it a try i really hope this helps. im not to familiar with fastboot but i with instruction from someone who is im sure i can figure it out ya know
frankthebunny said:
yes i can get to the custom recovery but it seemes like everytime i try to go into it it falls back into a loop unless i flash it and then imiediatly go into it but right now i have twrp on here
Click to expand...
Click to collapse
frankthebunny said:
im downloading that one now and ill give it a try i really hope this helps. im not to familiar with fastboot but i with instruction from someone who is im sure i can figure it out ya know
Click to expand...
Click to collapse
Alright, so I'm assuming the problem is there is no ROM on the phone or someone did factory reset in bootloader. So if the ruu helps, great (it should). If not, then I'm sure we'll figure it out.
thats what ive been assuming as well im really hoping this works out and i do appreciate the help ive been trying to figure out for hours how to find the correct ruu that i need.
now just to be clear there isnt any kind of preperation or anything for this right? im just going to go into the bootloader and make sure the usb is connected and recognized and the open the file on my pc and let it do its thing...
i got about 20 minutes left on this download (my internet connection is poop out here) and ill let you know how it works out
thanks again :good:
frankthebunny said:
thats what ive been assuming as well im really hoping this works out and i do appreciate the help ive been trying to figure out for hours how to find the correct ruu that i need.
now just to be clear there isnt any kind of preperation or anything for this right? im just going to go into the bootloader and make sure the usb is connected and recognized and the open the file on my pc and let it do its thing...
i got about 20 minutes left on this download (my internet connection is poop out here) and ill let you know how it works out
thanks again :good:
Click to expand...
Click to collapse
Yup. Since you're on an older hboot there's no preparation needed. I'm assuming you don't really want to get into all this rooting stuff and just want a working phone? If you want help with rooting, come back here when the ruu is done, but if you like it stock, then you should be good to go :beer:
Ps take care not to flash 3.18 ruu or ota without advise. You are likely supercid and are s-on, a bad combination.
Once 2.20 is installed come back here before installing 3.18 even if the phone offers it to you.
Sent from my HTC One XL using xda app-developers app
actually i would like to root it after i get it all fixed and put a custom rom on it and what not. like i said earlier i can follow instructions this was just a difficult spot to start from ya know.
twistedddx said:
Ps take care not to flash 3.18 ruu or ota without advise. You are likely supercid and are s-on, a bad combination.
Once 2.20 is installed come back here before installing 3.18 even if the phone offers it to you.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Hopefully he see's this post. If his phone isn't from AT&T Shouldn't be Scid
right on ill do that. is there anything else i should be downloding now to prepare for what ever it is i need to do to protect my phone from messing up again?
exad said:
Hopefully he see's this post. If his phone isn't from AT&T Shouldn't be Scid
Click to expand...
Click to collapse
yeah it is an at&t phone. at least it says on the top of it however im using straight talk t-mobile i believe.
will i need to root it again in order to utilize the t-mobile carrier?
No need to root for your carrier.
But you will need to root again to install other roms.
So is this phone back up and running again yet?
Sent from my HTC One XL using xda app-developers app
damn it didnt work.
error [155]: unkown error
the rom update utility cannot update your android phone
please get the correct rom update utility and try again
this is what ive run into every time ive tried this
frankthebunny said:
damn it didnt work.
error [155]: unkown error
the rom update utility cannot update your android phone
please get the correct rom update utility and try again
this is what ive run into every time ive tried this
Click to expand...
Click to collapse
What ruu?
Did you relock the bootloader?
no i didnt relock the bootloader i didnt realize i needed to. i asked if i needed to prep in anyway before i ran it and i used the ruu that was recommended to me in the beggining of the thread...
if relocking the bootloader will solve my problem how do i go about doing that...
heres the name of the file
htc_one_x_RUU_2.20.502.7_att_us_08022012
frankthebunny said:
no i didnt relock the bootloader i didnt realize i needed to. i asked if i needed to prep in anyway before i ran it and i used the ruu that was recommended to me in the beggining of the thread...
if relocking the bootloader will solve my problem how do i go about doing that...
Click to expand...
Click to collapse
First do :
fastboot oem readcid and tell me what it says
if it's CWS__001 then do:
fastboot oem lock
And chill, your phone will work when I'm done with you.
it say
cid: 11111111
frankthebunny said:
it say
cid: 11111111
Click to expand...
Click to collapse
ok hopefully since it didn't say CWS__001 you didn't use the lock command.
do:
fastboot oem writecid CWS__001 (be sure to note there are two "_")
then do
fastboot oem readcid
It should now say CWS__001
please confirm
nice ok ive changed it now to CWS__001
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++
hi guys, im not new to this, and i have a good understanding of adb and fastboot. i have just purchased a htc one xl (telstra) im running Hboot 2.15 and have unlocked bootloader via htc dev, installed TWRP ver; 2.6.0.0, rooted via flashing superSU and am currently running stock android ver 4.2.2 htc sense 5.0. i sim unlocked it so i could run my vodafone sim, and radio is working fine but i think the telstra RUU isnt allowing the sims internet conectis-on, therefore i am deciding to flash another rom. i first tried flashing pacman rom unsuccessfully but have yet to flash the boot.img as i havent got S-OFF and figure it wont allow writing to that partition yet, i have had alot of problems rewriting the CID for superCID, have tried many methods including xfactor and manually via fastboot and have been unsucessfull thus far, i understand that its not possible to downgrade Hboot unless S-off is achieved, alas facepalm is not possible unless superCID is achieved, and i cannot rewrite the CID manually or using any scripts i have found, is my Hboot version the problem or is there something im missing here?
help would be much appreciated
Have you tried the hex edit method?
Sent from my Evita
Yeah it returns with an error in adb, system mounted read only, and its deffinatly rooted so I'm not sure how to make system readwrite
Sent from my Wildfire S A510e using xda app-developers app
It would seem there s no sure fire way around this. Unless someone can help me figure out the read only issue in adb using the hex edit method
Sent from my Wildfire S A510e using xda app-developers app
hex edit progress
ok so i fixed the problem by uninstalling htcsync and re installing adb and fastboot via sdk tools, i got the file pulled from my phone and hex edited it, from cid; TELST001 to cid; 11111111 and pushed the file back onto my phone as per instructions, yet when i reboot into bootloader and do fastboot oem readcid it still comes back TELST001. somehow the phone knows what is happening and is changing the hex back to original form..??
ok scratch that, it actually never pulled the file from my phone, that was a file leftover from some script that didnt work, it had a cid of telus001 and my cid reads telst001 so i know that wasnt my file, the adb shell is able to read my phone but not ble to take the mmcblk0p4 file, so when i enter the command dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4 i get 2.0 records in 2.0 records out 1024 bytes transferred at <40960> bytes. so im guessing it was successful, yet when i check my sd root the file is nowhere to be seen!? where am i going wrong here
I just remembered someone had posted a different method, try this one:
http://forum.xda-developers.com/showthread.php?t=2460148
Sent from my Evita
argh
O..K so i rebooted the one xl ad the file was there, i copied to desktop, hex edited, and did dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4 to push the file back. read as successful in adb, so i did reboot fastboot and fastboot oem readcid, CID READS TELST001 STILL i must be retarded or something
timmaaa said:
I just remembered someone had posted a different method, try this one:
http://forum.xda-developers.com/showthread.php?t=2460148
Sent from my Evita
Click to expand...
Click to collapse
ok thanks man, ill give it a go now
st3wy said:
ok thanks man, ill give it a go now
Click to expand...
Click to collapse
yeah i tried it both ways and still gets cid TELST001 :l it seems im so close, the file was the same size the names were right, all commands i entered were spot on. just cant figure this one out
st3wy said:
yeah i tried it both ways and still gets cid TELST001 :l it seems im so close, the file was the same size the names were right, all commands i entered were spot on. just cant figure this one out
Click to expand...
Click to collapse
i even tried doing echo -ne "22222222" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
and still get INFOcid: TELST001
is it possible that my cid is stored somewhere other than mmcblk0p4 or mmcblk0p5??
You might be stuck in the same situation that at&t users were in after taking the 3.18 update. Basically the system partition is read only, so temp root was needed to get SuperCID in order to unlock their bootloader. The only difference being that you can unlock your bootloader just fine but can't get SuperCID in order to get s-off. I'm not sure on this, just spitballing ideas.
Sent from my Evita
timmaaa said:
You might be stuck in the same situation that at&t users were in after taking the 3.18 update. Basically the system partition is read only, so temp root was needed to get SuperCID in order to unlock their bootloader. The only difference being that you can unlock your bootloader just fine but can't get SuperCID in order to get s-off. I'm not sure on this, just spitballing ideas.
Sent from my Evita
Click to expand...
Click to collapse
sounds about right, i did read about this. so im guessing because i used temp root to spoof cid and unlock bootloader using the unlock code from that process, that there is no way to 'officially' relock the bootloader, and start the whole process again using a different method, say for instance using adb.. and thus getting bootlocker unlocked without spoofed cid and temp root possibly resulting in the ability to obtain supercid and full root? i have got supersu flashed through recovery.. but yeah obviously having serious issues with supercid atm.. thanks so much for your help this far man came a long way this arvo, just cant see the light at the ed of the tunnel... its like if i was able to flash Hboot i may be able to get around, but that requires s-off, which reuires super cid, which requires different Hboot lol
you wouldnt happen to know anyone else that might be able to brainstorm on this would you? although from looking at the threads youve made, it seems your possibly THE most educated person on this matter... idk might just have to wait for a dev to look into this and find a loophole. im not that good unfortunately. again, thanks for your help man. if you do get any ideas dont hesitate to post em up on this thread. cheers.
I'm definitely not the most educated person in this kinda stuff, I just read a lot on here and remember the ins and outs of this device. Finding a loophole around this is something that the HTC experts would have to work on, people like beaups, jcase, those kinda guys. Like I said though I'm not even sure if what I said is what's stopping you, I could be completely wrong.
Sent from my Evita
well, ive had one thaught that might be a stupid one but possibly one of the only things i am yet to try.. if i go through with the s-off and see if it works, although my phone is reading cid it may actually have supercid because like i say, its been successful in adb just hasnt returned a supercid through the fastboot commands, i guess the only question is will i brick my device if i follow through with s-off when i dont have supercid or will it just fail and all will be gravy
is there anyway to get them in on this thread so they know where im up to, or would i have to PM them exclusively and explain all over again
btw i think your right, system is read only. thats why the pushes arent working, even though they say they are in adb, either that or the phones cid and the RUU's cid are different and fastboot oem readcid is reading softwares cid and not the phones cid?
either way im going to drink a beer and go outside for a while, thanks again timmaaa, i didnt expect anyone to reply to this thread for a good while. like i said if u happen to have contact with the devs or anyone else that might be able to help, id be stoked. cheers bro and peace out!
You can try SuperCID but it just won't work. You can try contacting them and pointing them to this thread, but I think they're pretty busy guys so I don't know if they'll be able to help. The CID that shows up when using the fastboot command is definitely the phone CID and not the software CID.
Sent from my Evita