Related
Hi Everyone,
Apologies for this post, I've spent the last week and a half trawling through forum posts for my problem with limited success.
My Desire S had been experiencing random freezes, which would require a battery pull to reboot. I had tried a factory reset from HBOOT, but the phone would still freeze after that.
After the 5th or 6th battery pull, my phone would no longer boot successfully - It would get stuck on the white screen with green 'HTC' Text.
I can still successfully boot into HBOOT. If i select RECOVERY, it shows a black screen with a green triangle, then the screen goes black and the phone vibrates seven times.
If i select FACTORY RESET, the phone freezes and is not responsive.
My Phone details from HBOOT are as follows:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 30 2011, 17:29:31
I've tried connecting the phone to the PC and running some of the RUUs from here: http://forum.xda-developers.com/showthread.php?t=1002506
specifically: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
If I connect in HBOOT and run the RUU, I get a less than 30% battery power error, but if i connect through FASTBOOT, the RUU will run but gets stuck on a 'rebooting to bootloader' message.
The phone cannot be seen in a devices search in ADB either. Also, In an effort to remove S-ON to load PG88IMG.zip from my SD CARD, i tried the revolutionary and HTC provided methods, both were unsuccessful.
with Revolutionary, it would show "Waiting on device" and then nothing, and with the HTC method, the fastboot command to get the device token wouldn't work due to a command error. I know that the HTC method doesnt officially support the Desire S, but another XDA poster said that worked for his (or hers).
So, I'm asking for help. There are a lot of posts that relate to my issue, but none match 100%. I wanted to figure this out myself, but I defer to your greater knowledge.
Thanks very much, any help would be great.
sorry, as an addendum, I've also successfully created a gold card, if that helps.
Blindshot888 said:
Hi Everyone,
Apologies for this post, I've spent the last week and a half trawling through forum posts for my problem with limited success.
My Desire S had been experiencing random freezes, which would require a battery pull to reboot. I had tried a factory reset from HBOOT, but the phone would still freeze after that.
After the 5th or 6th battery pull, my phone would no longer boot successfully - It would get stuck on the white screen with green 'HTC' Text.
I can still successfully boot into HBOOT. If i select RECOVERY, it shows a black screen with a green triangle, then the screen goes black and the phone vibrates seven times.
If i select FACTORY RESET, the phone freezes and is not responsive.
My Phone details from HBOOT are as follows:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 30 2011, 17:29:31
I've tried connecting the phone to the PC and running some of the RUUs from here: http://forum.xda-developers.com/showthread.php?t=1002506
specifically: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
If I connect in HBOOT and run the RUU, I get a less than 30% battery power error, but if i connect through FASTBOOT, the RUU will run but gets stuck on a 'rebooting to bootloader' message.
The phone cannot be seen in a devices search in ADB either. Also, In an effort to remove S-ON to load PG88IMG.zip from my SD CARD, i tried the revolutionary and HTC provided methods, both were unsuccessful.
with Revolutionary, it would show "Waiting on device" and then nothing, and with the HTC method, the fastboot command to get the device token wouldn't work due to a command error. I know that the HTC method doesnt officially support the Desire S, but another XDA poster said that worked for his (or hers).
So, I'm asking for help. There are a lot of posts that relate to my issue, but none match 100%. I wanted to figure this out myself, but I defer to your greater knowledge.
Thanks very much, any help would be great.
Click to expand...
Click to collapse
A very rare problem, and since you've done a lot on your phone that were'nt successful, hope for the best that you haven't fried your eMMC. (Check forum for reference)
I would strongly suggest to remove the battery out for atleast 30secs to 1min. Then place it back in.
don't turn on the phone and charge it until full.
Once full, disconnect from power.
Go to bootloader, post your hboot version.
If hboot is still the same, go to fastboot and RUU with the one that your phone came with when you bought it.
It's great that you have a GoldCard, if the step above don't work, try RUU to the latest one.
Now regarding the freezes, I haven't received any freezes from my phone when it was still on stock. It might be a software problem and RUU might fix it. But if its a hardware, you might need to send for repair or maybe replacement.
Thanks very much for the reply Skanob,
Unfortunately, I didn't receive a RUU with my phone when it bought it. I checked through the SC card that was in the phone, but there's nothing that resembles an RUU. If you could please direct me to the latest version you mention, I would appreciate it.
when you say to post my HBOOT version, do you mean for me to post it here on the forums?
Apologies for the questions, I'm still getting used to the lingo.
Blindshot888 said:
Thanks very much for the reply Skanob,
Unfortunately, I didn't receive a RUU with my phone when it bought it. I checked through the SC card that was in the phone, but there's nothing that resembles an RUU. If you could please direct me to the latest version you mention, I would appreciate it.
when you say to post my HBOOT version, do you mean for me to post it here on the forums?
Apologies for the questions, I'm still getting used to the lingo.
Click to expand...
Click to collapse
The phone really didn't came with an RUU file. What I meant is that try to remember the Software Version of the phone when it came when you bought it. That means that software version is the RUU that was installed with it. Also the region.
My phone was installed with the one prior to RUU_Saga_hTC_Asia_WWE_1.48.707.1......
Try to get the RUU of your phone.
Post your HBOOT means post here or atleast tell me what is the version of your bootloader.
Example:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0000
RADIO-38.03.02.15_M
eMMC-boot
Mar 10 2011, 14:58:38
the latest as of now is RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30.0822U_3822.10.08.04_M_release_219480_signed.
Thanks again Skanob,
I'll try what you said to do and post the results.
from my initial post, I stated my HBOOT version as 0.98.0002. From what you've told me, should I expect my HBOOT version to change?
Also, I've checked the Europe RUU I attempted to use initially, i can confirm that it was the same version number as my phone. However, it got stuck on the status of "Rebooting to Bootloader" for hours.
Hi Skabob,
Just an update, after performing the steps you told me, my Desire S is still the same, with HBOOT version as 0.98.0002.
The rest of the details are the same as my original post.
Blindshot888 said:
Hi Skabob,
Just an update, after performing the steps you told me, my Desire S is still the same, with HBOOT version as 0.98.0002.
The rest of the details are the same as my original post.
Click to expand...
Click to collapse
I was expecting that your HBOOT would've been changed to the new one, it was an honest error on my end. I thought you've RUUed on the latest one. Sorry about that.
Seeing that you already have a GoldCard, I strongly suggest to RUU to the latest Europe version first.
If it still doesn't work, prepare for a long instruction, read on:
If you cannot use any RUU, the only thing you can do is update your HBOOT to the latest official S-ON.
Seeing that you are still currently S-ON. you wont be able to flash anything on your phone properly.
I myself don't have a proper guide on how you can update it as stock as possible, but maybe you can try what I've done before.
Skanob said:
amidabuddha said:
Ok taking my words back And how do you did this? You flashed the Stock 2.10.401.4 ROM over you bricked phone and it worked? (overwritted the revolutionary hboot or which version was it before?).
Click to expand...
Click to collapse
To make the long story short:
I stupidly get the firmware.zip file inside the ota file. That file had the latest hboot, recovery, and others. I renamed it to the correct pgxxximg.zip (cant remember the correct filename, currently drinking ) to flash it from bootloader.
Everything went well. Everything inside the file updated the corresponding file/partition/image to my phone. Hence letting me be stuck to the "locked" hboot 2.xx.xx s-on. ROM wouldn't boot as I said.
Being on the "locked" state wouldn't allow me to flash anything on the phone as far as i can remember. While writing, it will say has its unsuccessful.
But "unlocking" the hboot let me flash the recovery.
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
The OTA file that I've mentioned here is the recently released OTA file for Sense 3.0. Use search on where to get the download link.
Once you have the OTA file, just extract it and gather the firmware.zip file. copy it to your phones SD Card and rename it to PG88IMG.zip (.zip should be the extension of the file, not included in the name of the file).
Boot your phone into bootloader and agree to the phone if it asks you to update. AFAIK it should automatically do its thing.
Also, I remembered that it should be stuck in the middle of its update, just past the HBOOT and RADIO procedure. Once you are on that stuck state, maybe wait for about 10-15mins and see if it doesn't move. That is when I've removed the battery and waited for 30secs to 1min then re-plug it in. So you should pay close attention to what it is doing. Then check your HBOOT and see if it is updated.
If it is successful on updating your HBOOT, you would now need to UNLOCK your bootloader. The HTC unlock method supports the new HBOOT, seeing that you are still on the OLD one, thats one reason it wasn't successful.
What we're trying to do here is to get your phone to a state where you should be able to flash a custom recovery (check partitions if they are corrupted, most especially cache), full wipe partitions, flash a custom rom (pre-rooted stock recommended), then RUU back if you still want stock roms.
Goodluck!
P.S.
These instructions that I've given you are the methods that I would've used and thought of if I was in your situation. I am no expert in ADB nor on how to fix the phone properly. I assume that you already know the world-wide disclaimer: "not held responsible, know what you are doing" blah blah blah...
Also, full charge your phone first prior to doing it.
---------- Post added at 02:51 AM ---------- Previous post was at 02:32 AM ----------
And it's Skanob...
oh! my apologies Skanob! the B and N keys are right next to each other..but still I should have double checked.
Okay, I've tried running the RUU exe file for the RUU you referred me to. unfortunately it didnt move past "rebooting to bootloader".
I also grabbed the OTA file from this link. http://forum.xda-developers.com/showthread.php?t=1282019&page=65
Post number 643 had the link
I renamed the file to PG88IMG, put it on my sd card and loaded the Bootloader on the phone. It scanned the file, but did not give me am option to update.
Blindshot888 said:
oh! my apologies Skanob! the B and N keys are right next to each other..but still I should have double checked.
Okay, I've tried running the RUU exe file for the RUU you referred me to. unfortunately it didnt move past "rebooting to bootloader".
I also grabbed the OTA file from this link. http://forum.xda-developers.com/showthread.php?t=1282019&page=65
Post number 643 had the link
I renamed the file to PG88IMG, put it on my sd card and loaded the Bootloader on the phone. It scanned the file, but did not give me am option to update.
Click to expand...
Click to collapse
it should be PG88IMG.zip (.zip is the file extension). But have you double checked if the HBOOT was updated?
I can confirm that the file I used was indeed a .zip file.
From looking at the HBOOT version, its still sitting at 0.98.0002.
Blindshot888 said:
I can confirm that the file I used was indeed a .zip file.
From looking at the HBOOT version, its still sitting at 0.98.0002.
Click to expand...
Click to collapse
you might want to try to re-create your GoldCard. You might have a bad one.
Does the phone detects the file? There should be a check of .zip files once you boot on bootloader. The screen will take you there within 3-5 seconds after boot and will stay on checking the files for 1-2 seconds.
Blindshot888 said:
My Phone details from HBOOT are as follows:
SAGA PVT SHIP S-ON RL
HBOOT-0.98.0002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 30 2011, 17:29:31
Click to expand...
Click to collapse
Hey man this says it all. You do not need to change hboots, flash RUU or other stuff. Just go to the service center and they will repair it for free. Like this guy did. If you have warranty of course
amidabuddha said:
Hey man this says it all. You do not need to change hboots, flash RUU or other stuff. Just go to the service center and they will repair it for free. Like this guy did. If you have warranty of course
Click to expand...
Click to collapse
or that ^^^^
Hello folks!
First off I hope this problem hasn't been posted previously since I searched and couldn't find it.
I have on my HTC sensation the Android Revolution _HD-Sensation_3.6.11 or 3.6.2 I for some reason have two on my computer and can't remember which one I put in. The phone's HBOOT is 1.17.1111 and I can't remember when I put that update in either. My concern is that I want to update the software as I'm noticing some issues with the phone again and so downloaded the Android Revolution HD 6.5.1 for HTC Sensation from here: http://forum.xda-developers.com/showthread.php?t=1098849
Upon putting said zipped file in SD card and going into bootloader it t says the message above: "Loading...[PG58DIAG.zip] No img" and below that: "Loading...[PG58DIAG.nbh] No img or Wrong img" It repeats like that on the screen. I remember having this issue before as well when I updated the phone last, so I downloaded, as I was instructed to, "PG58IMG" and mounted it on the SD card. It fixed the problem then, so doing it again this time it didn't fix the problem for me. First off, I hope I have the correct ROM as trying to search for the updated version of the ROM I have I was unsuccessful in. So then I decided let's do this since it has ICS. I appreciate any and all help. Thanks in advance.
Are you running the latest firmware ? 3.32 is needed for ARHD 6.5.1
Also, you said you where using [PG58DIAG.zip] It should be PG58IMG i think you maybe using the wrong file,
Im still a noob, i only had this sensation 2 days so i maybe wrong.
sano1 said:
Hello folks!
First off I hope this problem hasn't been posted previously since I searched and couldn't find it.
I have on my HTC sensation the Android Revolution _HD-Sensation_3.6.11 or 3.6.2 I for some reason have two on my computer and can't remember which one I put in. The phone's HBOOT is 1.17.1111 and I can't remember when I put that update in either. My concern is that I want to update the software as I'm noticing some issues with the phone again and so downloaded the Android Revolution HD 6.5.1 for HTC Sensation from here: http://forum.xda-developers.com/showthread.php?t=1098849
Upon putting said zipped file in SD card and going into bootloader it t says the message above: "Loading...[PG58DIAG.zip] No img" and below that: "Loading...[PG58DIAG.nbh] No img or Wrong img" It repeats like that on the screen. I remember having this issue before as well when I updated the phone last, so I downloaded, as I was instructed to, "PG58IMG" and mounted it on the SD card. It fixed the problem then, so doing it again this time it didn't fix the problem for me. First off, I hope I have the correct ROM as trying to search for the updated version of the ROM I have I was unsuccessful in. So then I decided let's do this since it has ICS. I appreciate any and all help. Thanks in advance.
Click to expand...
Click to collapse
HBOOT 1.17.1111 will work with GB ROMs but not ICS ROMs.
You need to flash the appropriate firmware and as stated PG58IMG.zip is the correct filename on the SDcard. After flashing pop out the card while it boots up reinsert the SDcard and delete/rename the PG58IMG.zip file.
Look in http://forum.xda-developers.com/showthread.php?t=1459767 for the firmware. I've seen folks posting problems with the most recent firmware but haven't followed them.
I guess Mike's ARHD thread should have firmware in it with some guidance.
azzledazzle said:
Are you running the latest firmware ? 3.32 is needed for ARHD 6.5.1
Also, you said you where using [PG58DIAG.zip] It should be PG58IMG i think you maybe using the wrong file,
Im still a noob, i only had this sensation 2 days so i maybe wrong.
Click to expand...
Click to collapse
+1
Here is an excellent noob friendly guide from joaquinf. It's made for ARHD 6.5.1. It has all the steps to upgrade Your firmware to 3.32 and flashing ARHD 6.5.1 / 6.5.1 xe.
http://forum.xda-developers.com/showthread.php?p=21989107
gol_n_dal said:
HBOOT 1.17.1111 will work with GB ROMs but not ICS ROMs.
You need to flash the appropriate firmware and as stated PG58IMG.zip is the correct filename on the SDcard. After flashing pop out the card while it boots up reinsert the SDcard and delete/rename the PG58IMG.zip file.
Look in http://forum.xda-developers.com/showthread.php?t=1459767 for the firmware. I've seen folks posting problems with the most recent firmware but haven't followed them.
I guess Mike's ARHD thread should have firmware in it with some guidance.
+1
Click to expand...
Click to collapse
Good sir or madame?, thank you quite very much. I have visited the link and it all seems quite easy. I also understand the mistake I have made. I will be working on the flash possibly tomorrow when I have more time at hand to do it all. I also appreciate your feedback along with the link.
sano1 said:
Good sir or madame?, thank you quite very much. I have visited the link and it all seems quite easy. I also understand the mistake I have made. I will be working on the flash possibly tomorrow when I have more time at hand to do it all. I also appreciate your feedback along with the link.
Click to expand...
Click to collapse
GL
blah blah (10 chars)
One last question if I may, I noticed on the threads that there were apps and even built in features which would back up my phone, including my sms text messages. Now I'll follow the advice on the thread and remove sim card for the just in case (but since all contacts are synced to Google account it won't matter), what I really wanna back are all my text message conversations, not even so much the apps themselves as I can always re-download them later on. I want to back up my music playlist as well if it's possible at all. I know I'll have it all on my SD card, but the playlists are all on the phone itself and that is what I really want to back up. I thank you all once again for all the feedback as well as the help provided, wish me luck for I'll be at it tomorrow.
sano1 said:
One last question if I may, I noticed on the threads that there were apps and even built in features which would back up my phone, including my sms text messages. Now I'll follow the advice on the thread and remove sim card for the just in case (but since all contacts are synced to Google account it won't matter), what I really wanna back are all my text message conversations, not even so much the apps themselves as I can always re-download them later on. I want to back up my music playlist as well if it's possible at all. I know I'll have it all on my SD card, but the playlists are all on the phone itself and that is what I really want to back up. I thank you all once again for all the feedback as well as the help provided, wish me luck for I'll be at it tomorrow.
Click to expand...
Click to collapse
There are two main backup methods:
1 Nandroid Backup/Recovery. You do this via your recovery, e.g. CWM. This is a whole phone backup.
2 An app like Titanium, with this you can backup and recover apps and their data individually. If you go down this route DO NOT restore any system apps if you change ROMs as it'll cause problems. Restoring your downloaded apps and data is fine. You can "probably" restore some system data, like SMS. Before you recover any system data DO A NANDROID BACKUP first so if it screws up anything you can just restore the phone to its previous state.
Use SMS Backup & Restore or SMS Backup+ for backup Your SMS.
I think titanium backup is suitable for music playlists.
Sensation stuck on boot
Hey guys, So I initiated flash today and have come across a slight problem;
I followed the guides on here: http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
and here: http://forum.xda-developers.com/showthread.php?p=21989107
I saw that the first thing to have done was install 4ext recovery. I followed the read me and tried the "adb reboot bootloader" but it kept saying device not found. Then I noticed I had it already in my phone, so I ran the backup and it said back up complete. So then I turned off the phone, rebooted into bootloader and waited for the update. However, it said "error invalid CID and can't update. Press power to reboot" It was the only option given. So then, I followed the guide on Kohr-Ah's page and took out the SD card, rebooted into bootloader, went to Recovery, ran superwipe and installed ARHD 6.5.1 with Beats Audio. After everything went done and well, it rebooted and turns on but once the beats logo completes its circle, it gets stuck on the beats page. I ran the wipe again, and reinstalled ARHD and still gives the same result. Any body know how I can solve it?
I also forgot to say that when I try to install the PG581IMG (the firmware) it says:
Finding update package...
Opening update package...
Installing update package...
Installation aborted.
Very much a noob when it comes to Android phones and I have been working through the process to get a custom Rom on my HTC Sensation. I started following the instructions in this thread [Guide] to Installing S-off, Unlocking, ClockWork, Root, SuperCID & S-on and successfully completed step one, achieving s-off on the phone.
In step two things went badly wrong. Following the instructions I downloaded clockwork recovery and copied the PG58IMG onto my sd card, at least I thought I did. What I now realize is that since I had been doing a lot of reading and research on this topic before attempting it for the first time I had downloaded several relevant files in advance, one of which is the PG58IMG file from this thread [DEV] HTC Sensation & HTC Sensation XE firmware | Partitions Info | [01.03.2012 and it was this file that I put on the sd card. Obviously not what I should have flashed at all. Especially since it seems that the tool which would help me out of this mess is the one I just failed to install properly.
So the situation is that the phone loops constantly on startup when booting normally. When I boot into HBOOT with the SD card in it tries to update again and when that fails, gives no option but to reboot. If I remove the SD card then I get access to the following screen -
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-10.14.9035.01_M
eMMC-boot
and below the options -
HBOOT
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
I have tried connecting the phone to my computer at this stage but I cant get FASTBOOT USB and adb cant find any devices either. Am I completely stuffed at this point? If not, if anyone can help me out with some instructions on what to do here I would be extremely grateful.
Thanks,
Webba
So have you tried to go into recovery once your in bootloader ? what happens then ?
If you get the correct files onto your sd card via a card reader, then put it in the phone, bootloader should attempt to update the new correct files.
I have tried going into recovery, it comes up with a pic of a phone with a green circle, followed by a phone with a red triangle, followed by going into the boot cycle. This is with the sd card removed. Am I right in thinking that if I get the right files onto the card and then run recovery with the sd card in it will work?
If you run BOOTLOADER then it should do... Make sure you remove the old PG58IMG before putting the new one on.
Thanks so much, I will try it as soon as I can. I assume I will find the right stock rom somewhere on these forums?
webster84 said:
Thanks so much, I will try it as soon as I can. I assume I will find the right stock rom somewhere on these forums?
Click to expand...
Click to collapse
you will find anything and everything you will ever need on these forums
My Sensation was purchased in Hong Kong, after looking at the lists at shipped-roms this one - RUU_Pyramid_hTC_Asia_WWE_1.35.707.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198358_signed.exe
seems to be most likely correct. Can anyone more knowledgeable confirm this? I would hate to flash the wrong thing again.
did you successfully get superCID ? if so i do believe that you can flash any RUU / ROM
Im not 100% on this as im still new to the sensation myself, But im sure thats the whole point in having SuperCID
Unfortunately I dont have superCID. I was following the instructions pretty slavishly and the superCID setup is one step after clockwork
Is there a way to get superCID in my phones current state? From what I am reading I need it to at least hook up to adb which it is not doing at the moment so I assume I just have to get the right onto the sdcard to have any chance of it working, right?
Yes, You need clockwork mod before SuperCID. Have you tried to re download CWM and put it on sd card ? It could have just been a bad download, it happens to us all.
Download it again, Remove the previous PG58IMG from SD Card via a card reader (if you have one) Put the new PG58IMG on SD card. Pull battery out, Put SD Card back into the phone, put battery back in and boot into bootloader (volume down + Power)
Bootloader should automatically find the PG58IMG and ask if you want to update it, Select yes and theoretically you should be fine..
EDIT: Use this one http://forum.xda-developers.com/attachment.php?attachmentid=706572&d=1314848127
Yeah, I have re-downloaded CWM and made sure it is the right one I have to wait until the shops open here so I can pick up a micro sdcard reader but I will try the new CWM first, and if that fails then I will try the stock rom. Am I right in thinking that neither of this is likely to make the situation worse, even if they dont work?
No providing bootloader still works everything is fix-able..
We aint messing with bootloader so u will be ok.
Cant believe you dont have a card reader lol....
lol, up until today the only thing I needed to be able to read micro sd cards was the phone. Well, I will be better prepared next time anyway.
The thing that had me worried is that since I originally didn't realize PG58IMG was not a unique file name I am almost certain that the one on my sd card at the moment is not even CWM at all but one of the updated firmware ones I mentioned in the OP that I very stupidly mistook for it. It feels like a really serious mistake to make, but happy to know that if the boot loader is working then it should be fixable. I wasn't sure even about that.
I think the PG58IMG is a unique code that the phone reads and recognises as something to be flashed / updated.
Ive seen various things CWM / Firmwares / Updates with the same PG58IMG title. so maybe youre right and the original file you downloaded wasnt the correct one.
Dont panic, Keep calm, Ask questions, Get answers...... This is the only way to avoid a bricked phone
Yeah, you've saved me a lot of stress already. Ill be back in a few hours with the results of the next attempt. Thanks again!
Ok, the news is not great. I got hold of a micro sd adaptor so I could plug it into my computer and removed the old PG58IMG. I put the correct one (downloaded from this thread) on the sd card and rebooted the phone into HBOOT. It recognizes the file on the sd card but gets a cid fail and there is no option but to reboot which goes into the boot cycle.
Whats worse is that doing this apparently fries the sdcard. I tried it twice, because I am sucker for punishment and in both cases the sdcard is unreadable afterwards.
Maybe I should try and explain more clearly that I am now sure the PG58IMG that I first put on the card and flashed I am sure is the Firmware from 3.32.401.x & 3.32.401.10x RUU from this thread. It appeared to successfully update before rebooting the phone into its current state, causing me to realize I had the wrong file. I dont understand enough to know exactly whats going on but it seems pretty bad. Do you think I should try a 3rd sdcard with the Shipped ROM on it or is there something else I should do at this point?
Edit - The second sd card wasn't fried after all, but I am still searching for a shipped rom that isnt in .exe format, since the phone isnt connecting to the computer by usb at all right now. Anyone know where I can find one?
Edit - Ok, now I have fastboot usb which means I can use .exe shipped roms. adb devices cant find the phone though which means I cant superCID it which means I still have to find the right ROM. Since I brought the phone from HK I am trying all the asian ones first. Anyone know specifically which file at shipped-roms.com is the right one?
You flashed firmware for ics rom, so the stock rom won't boot and you have bootloop. If you flash the 3.12 firmware ( works for both ics and gb) that will resolve the loop and you will be able to continue with the guide and flash cwm.
Sent from my HTC Pyramid using xda premium
Hey Stringer7, do you mean this Firmware from 3.12.401.2/102 RUU available in the same thread? I will download it and give it a try.
edit - Gave it a try, I get CID incorrect from it too. Seems like CID incorrect for everything I try to flash atm.
What is your CID ??
Unfortunately I dont know. I didn't know I needed it before I started and now since the phone isn't talking to adb I cant use it to find out. All I know is that I bought the phone from Hong Kong about 6 months ago. Is there a way to check the CID with the phone the way it is now?
I examined most if not all Boot Loop related items in XDA-Developers, as well as other sources. Although there are lots of suggestions, I cannot find one that relates to my specific situation. The last thing I want to do is make it worse. So, here's my story. I'll keep it brief, but concise.
I've had my Sensation 4G for a little over two years. Soon after purchase, I rooted it via the Revolutionary mechanism. Unfortunately (I think), I also opted for the Clockwork Mod. Unfortunately, I have not been able to do OTA updates, and find I'm still running 2.3.4.
I recently desired to purchase the HTC One for T-Mobile, and did so. I wanted to pass on my Sensation 4G to my sister. Therefore I needed to unroot it. I did weeks of reading about all the ways to do this. Early last week I attempted doing so by following the directions found here (http://kgs1992.com/ruu-guide/). I used the PG58IMG file found here (http://forum.xda-developers.com/showthread.php?t=1459767#2). The file selected was Firmware 3.33 Universal: (http://d-h.st/SuC). I followed the directions precisely. All appeared to run properly, and appeared to end with successful messages. At the end of the instructions it states "If you experience a boot loop, repeat 4.4.2 again." I did that several times. I still have the boot loop.
I started the process with this...
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.17.1111
RADIO-10.14.9035.01_M
eMCC-boot
Jun 2 2011.22:31:39
HBOOT
(VOL UP) to previous item
(VOL DOWN to next item
(POWER) to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Following afore-mentioned process it says...
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24a. 3504.31-M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
That brings me to my big question. What do I do now? I had hoped to retain my contacts and applications. I'd like to first attempt ways to fix it and still salvage what's on the phone, but ultimately I just need the phone to work. I should also mention that I've downloaded the following two files. My next attempt was going to execute the top one, but I don't know the status of the phone after doing so. Can anyone help me? Are there other things I should try first?
RUU_PYRAMID_ICS_TMOUS_3.32.531.14_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_256085_signed.exe
RUU_Pyramid_TMOUS_1.50.531.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223976_signed.exe
Micalee said:
I examined most if not all Boot Loop related items in XDA-Developers, as well as other sources. Although there are lots of suggestions, I cannot find one that relates to my specific situation. The last thing I want to do is make it worse. So, here's my story. I'll keep it brief, but concise.
I've had my Sensation 4G for a little over two years. Soon after purchase, I rooted it via the Revolutionary mechanism. Unfortunately (I think), I also opted for the Clockwork Mod. Unfortunately, I have not been able to do OTA updates, and find I'm still running 2.3.4.
I recently desired to purchase the HTC One for T-Mobile, and did so. I wanted to pass on my Sensation 4G to my sister. Therefore I needed to unroot it. I did weeks of reading about all the ways to do this. Early last week I attempted doing so by following the directions found here (http://kgs1992.com/ruu-guide/). I used the PG58IMG file found here (http://forum.xda-developers.com/showthread.php?t=1459767#2). The file selected was Firmware 3.33 Universal: (http://d-h.st/SuC). I followed the directions precisely. All appeared to run properly, and appeared to end with successful messages. At the end of the instructions it states "If you experience a boot loop, repeat 4.4.2 again." I did that several times. I still have the boot loop.
I started the process with this...
-Revolutionary-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.17.1111
RADIO-10.14.9035.01_M
eMCC-boot
Jun 2 2011.22:31:39
HBOOT
(VOL UP) to previous item
(VOL DOWN to next item
(POWER) to select item
FASTBOOT
RECOVERY
FACTORY RESET
SIMLOCK
IMAGE CRC
Following afore-mentioned process it says...
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24a. 3504.31-M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
That brings me to my big question. What do I do now? I had hoped to retain my contacts and applications. I'd like to first attempt ways to fix it and still salvage what's on the phone, but ultimately I just need the phone to work. I should also mention that I've downloaded the following two files. My next attempt was going to execute the top one, but I don't know the status of the phone after doing so. Can anyone help me? Are there other things I should try first?
RUU_PYRAMID_ICS_TMOUS_3.32.531.14_Radio_11.69A.3504.00U_11.23.3504.07_M2_release_256085_signed.exe
RUU_Pyramid_TMOUS_1.50.531.1_Radio_10.56.9035.00U_10.14.9035.01_M_release_223976_signed.exe
Click to expand...
Click to collapse
You will probably have to wipe the data partition, and therefore delete your contacts and apps (but if your contacts are saved on your google account they will be restored).
:
Do you have access to the recovery? from there you can flash a ROM and do a fresh install. I got that problem when I upgraded to the newer firmware, and I just flashed the ROM, and then everything worked fine.
astar26 said:
You will probably have to wipe the data partition, and therefore delete your contacts and apps (but if your contacts are saved on your google account they will be restored).
:
Do you have access to the recovery? from there you can flash a ROM and do a fresh install. I got that problem when I upgraded to the newer firmware, and I just flashed the ROM, and then everything worked fine.
Click to expand...
Click to collapse
I'm not sure I know what the data partition is. I can get to all my apps via play.google.com. I took full Titanium Backups, so maybe that'll be an option. Those backups were copied to my laptop.
As to Recovery, I can access it, but cannot put anything on the sd card as I do not have access to it. Apparently I can only do things via ADB.
I was just reading "A must read for those noobs who want to enjoy ICS". Perhaps there is a solution. There are apparently conflicts with Hboot versions and ICS or something. I just found that, so I'm still looking into that. I don't know how to deal with only Hboot.
Micalee said:
I'm not sure I know what the data partition is. I can get to all my apps via play.google.com. I took full Titanium Backups, so maybe that'll be an option. Those backups were copied to my laptop.
As to Recovery, I can access it, but cannot put anything on the sd card as I do not have access to it. Apparently I can only do things via ADB.
I was just reading "A must read for those noobs who want to enjoy ICS". Perhaps there is a solution. There are apparently conflicts with Hboot versions and ICS or something. I just found that, so I'm still looking into that. I don't know how to deal with only Hboot.
Click to expand...
Click to collapse
You can connect your MicroSD card via another phone to the PC, and also use the "adb push" command to push the ROM files to the root of the microSD card. Also, some recoveries allow mounting the SD card to the PC like doing it when the phone is booted, as an external drive, check for it in the recovery.
To move the ROM files to the SD card:
put the files in the folder where ADB is located
On command line type: "adb push rom.zip /sdcard/rom.zip"
Where rom.zip is the name of the rom file you are going to flash. this should work, here is a full guide to help you pushing the file via ADB: http://forum.xda-developers.com/showthread.php?t=1667929
Good luck
astar26 said:
You can connect your MicroSD card via another phone to the PC, and also use the "adb push" command to push the ROM files to the root of the microSD card. Also, some recoveries allow mounting the SD card to the PC like doing it when the phone is booted, as an external drive, check for it in the recovery.
To move the ROM files to the SD card:
put the files in the folder where ADB is located
On command line type: "adb push rom.zip /sdcard/rom.zip"
Where rom.zip is the name of the rom file you are going to flash. this should work, here is a full guide to help you pushing the file via ADB: http://forum.xda-developers.com/showthread.php?t=1667929
Good luck
Click to expand...
Click to collapse
That certainly sounds doable. I went to the link you provided. I'm not sure how pushing the rom.zip to the sdcard and doing the recovery via the phone's recovery is different than via the adb command as done earlier. The adb command process seemed to work correctly, except for the resulting boot loop. Apparently I still need to determine which rom.zip will leave me with a function phone. The only other difference in what I read at the link you provided was to do the various ["Factory Reset", "Wipe Cache Partition", and "Wipe Dalvik Cache]" commands, which I have not done. I need to determine whether those commands are necessary in my case. Thank you for your contribution.
What's happens here is that you have placed ice cream sandwich firmware with a gingerbread Rom. Gingerbread doesn't support it and as such won't boot. If you want to regain access to everything again the reflash 1.17 firmware from the thread. Then your Rom should boot up. Then jump to recovery and make a full nandroid back up. Then re-flash the ics 3.33 universal firmware and then run one of the ics ruu's you downloaded. That will make the phone have a fresh install of ics and stock HTC sense unrooted
don't try to s-on again as their is no real point to it. It's not going back for warrenty so what's the concern eh?
Good luck pal
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Micalee said:
That certainly sounds doable. I went to the link you provided. I'm not sure how pushing the rom.zip to the sdcard and doing the recovery via the phone's recovery is different than via the adb command as done earlier. The adb command process seemed to work correctly, except for the resulting boot loop. Apparently I still need to determine which rom.zip will leave me with a function phone. The only other difference in what I read at the link you provided was to do the various ["Factory Reset", "Wipe Cache Partition", and "Wipe Dalvik Cache]" commands, which I have not done. I need to determine whether those commands are necessary in my case. Thank you for your contribution.
Click to expand...
Click to collapse
If you want you should backup via recovery, but wiping the phone after is necessary. if you managed to push the ROM to the SD-card, you can normally flash. but use a ICS (or newer) ROM, that supports the firmware.
In contrast to what heavy_metal_man said, you can do a nandroid backup as it is, as the files are still there. but you don't have much to do with it.
Edit - If you need any help doing it step by step - I'm here to help, just say where you are stuck on the guide (or just explain)
heavy_metal_man said:
What's happens here is that you have placed ice cream sandwich firmware with a gingerbread Rom. Gingerbread doesn't support it and as such won't boot. If you want to regain access to everything again the reflash 1.17 firmware from the thread. Then your Rom should boot up. Then jump to recovery and make a full nandroid back up. Then re-flash the ics 3.33 universal firmware and then run one of the ics ruu's you downloaded. That will make the phone have a fresh install of ics and stock HTC sense unrooted
don't try to s-on again as their is no real point to it. It's not going back for warrenty so what's the concern eh?
Good luck pal
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Click to expand...
Click to collapse
Thanks heavy_metal_man for that information. In the mean time, while waiting for another suggestion, I decided to try a different rom. That was due to the comments I'd seen about conflicts between Hboot and ICS. So, just for the heck of it I went through whole routine, using ROM V3.12. After doing so (twice), the phone booted! Amazingly, other than thinking it's 1970, it appears to be identical to what it was before I ever did anything. It's still running V2.3.4 of Android, and Sense V3.0. I don't recall which version of Sense was there before. After it booted, I shut it down again and put it in Recovery mode. There have been a number of changes there. Now it says...
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.23.0000
RADIO-11.19.3504.29.2
OpenADSP-v01.6.0.2226.00.1227
eMMC-boot
Dec 26 2011.12:14:25
Does any of this information affect or change your suggestion in any way? I'd still like to get ICS on this thing so the latest is available for when I give it to my sister. I wonder what will happen if I attempt OTA? By the way, it still has Revolutionary CWM V4.0.1.4 on it.
Micalee said:
Thanks heavy_metal_man for that information. In the mean time, while waiting for another suggestion, I decided to try a different rom. That was due to the comments I'd seen about conflicts between Hboot and ICS. So, just for the heck of it I went through whole routine, using ROM V3.12. After doing so (twice), the phone booted! Amazingly, other than thinking it's 1970, it appears to be identical to what it was before I ever did anything. It's still running V2.3.4 of Android, and Sense V3.0. I don't recall which version of Sense was there before. After it booted, I shut it down again and put it in Recovery mode. There have been a number of changes there. Now it says...
*** LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.23.0000
RADIO-11.19.3504.29.2
OpenADSP-v01.6.0.2226.00.1227
eMMC-boot
Dec 26 2011.12:14:25
Does any of this information affect or change your suggestion in any way? I'd still like to get ICS on this thing so the latest is available for when I give it to my sister. I wonder what will happen if I attempt OTA? By the way, it still has Revolutionary CWM V4.0.1.4 on it.
Click to expand...
Click to collapse
you just used a ruu.exe from pc and restored everything to stock condition
but how you were able to keep custom recovery(cwm V4.0.1.4)
when you flashed the 3.33 firmware you could just install a custom ics rom
because with 3.33 firmware the gb rom you had it would never booted
about OTA i assume nothing will happen as long as you have cwm recovery installed
you must have the stock recovery
Well, since you flashed a new rom you can disregard my first suggestion and go straight for running the ics ruu you have. Ota updates will not work if you dont have the stock recovery. But the ruu will give you it so ota will work, but the updates will be for the cid of the rom you flashed. So flash a WWE rom to make sure you get any updates, but at this point their will be few if any.
Aside from that you will be all sorted pal
Sent from my Nexus 7 using Tapatalk 4
Thanks again heavy_metal_man. It wasn't that I ignored your suggestion, I tried the second (V3.12) Rom before I had seen it. As for your last entry, I was following it until you hit me with the WWE reference. As for the V3.12 Rom I used, there was a direct MIB match, and the CID used was cid******, so a direct match was not necessary as far as I can determine. I could have edited the txt file and inserted my actual CID however. Also, was your comment about "the ics ruu I have", in reference to the two RUU_PYRAMID_ICS_TMOUS...etc. files I mentioned that I had already downloaded? Running one of those will be a new experience. I'll run the latest. If that works, I'll be a happy camper. I've learned a lot, but I have a long way to go.
Micalee said:
Thanks again heavy_metal_man. It wasn't that I ignored your suggestion, I tried the second (V3.12) Rom before I had seen it. As for your last entry, I was following it until you hit me with the WWE reference. As for the V3.12 Rom I used, there was a direct MIB match, and the CID used was cid******, so a direct match was not necessary as far as I can determine. I could have edited the txt file and inserted my actual CID however. Also, was your comment about "the ics ruu I have", in reference to the two RUU_PYRAMID_ICS_TMOUS...etc. files I mentioned that I had already downloaded? Running one of those will be a new experience. I'll run the latest. If that works, I'll be a happy camper. I've learned a lot, but I have a long way to go.
Click to expand...
Click to collapse
ah sorry, getting ahead of myself with terminology here WWE stand for world wide English. most unbranded phones run on world wide English roms, and if people are downgrading/upgrading they tend to want unbranded as they will get official htc updates faster
as far as cid`s are concerned they dont really matter as you are s-off and the phone will accept any ruu (rom update utility) you give it. one note of caution though is you have select a t-mobileus ruu and they are ment to be for the tmobile sensation 4g. if you dont have the tmobus 4g it may give you some issues with the radio, meaning you may lose phone signal. ( im not 100% sure but caution is advised )
if you dont have a sensation 4g then download and run this one here. im pretty confident that its a stock ice cream sandwich unbranded rom
Running the RUU is simple enough, just boot the phone into your stock 2.3.4 rom and turn on usb debugging from settings for good measure. Then connect the phone to the pc via the usb cable and then run the RUU. it will connnect to the phone and confirm the phone is the correct model i believe, then it will confirm this is what you want to do. select yes and let it work its magic. its pretty straight forward they phone may reboot several times, this is normal. just dont disconnect the battery or the usb cable and you will be fine. should be done in ten minutes tops
good luck pal
I made it through the RUU process, but not without some difficulty. When I ran the RUU_PYRAMID_ICS_TMOUS_3.32.531.14 version, it died with an Error 155. Fortunately it left everything intact. Then I ran the older RUU_Pyramid_TMOUS_1.50.531.1 non-ICS version. It got the same error. I think these errors must somehow be due to the peculiar results from flashing the PG58IMG file earlier. Once again, it left everything intact. I tried the RUU ICS 3.32 version one more time, except this time I put the phone in flashboot mode first. Curiously, the RUU screen that came up thought it was updating a later version than what was actually on the phone, but IT RAN... all the way through to a successful finish. I was stunned. Now the phone reports...
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24a. 3504.31-M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
The entire process left my SD card intact as well. Amazing. It still says S-OFF as you expected. I may or may not attempt turning S-On again.
One comment I'd like to make about xda-developers. There is an amazing amount of information here. The biggest problem I've encountered is trying to figure out if I'm looking at, or have found, the latest information. Some times I'll find something that looks pertinent, only to find that I'm on page 2 of a 114 page thread, and the information I'm looking at is completely obsolete. It's tough for a noob to decipher it all. Anyway, thanks again for everyone's assistance. I think this is a proper place to terminate this particular thread. Now I'll start looking for the latest information on rooting my new HTC ONE. At least I have a fall back phone in my newly restored Sensation 4G. I'm not sure I'm in love the ONE yet, so perhaps I'll take it back. I'm within my 14 day return window.
I'm glad your sorted pal the threads can be a bit out of date, maintenance of information is not really regulated but as always if people are unsure just ask, quoting the info you have and what you think is the case
Sent from my HTC Sensation XE with Beats Audio Z715e using Tapatalk 2
Micalee said:
I made it through the RUU process, but not without some difficulty. When I ran the RUU_PYRAMID_ICS_TMOUS_3.32.531.14 version, it died with an Error 155. Fortunately it left everything intact. Then I ran the older RUU_Pyramid_TMOUS_1.50.531.1 non-ICS version. It got the same error. I think these errors must somehow be due to the peculiar results from flashing the PG58IMG file earlier. Once again, it left everything intact. I tried the RUU ICS 3.32 version one more time, except this time I put the phone in flashboot mode first. Curiously, the RUU screen that came up thought it was updating a later version than what was actually on the phone, but IT RAN... all the way through to a successful finish. I was stunned. Now the phone reports...
-Firmware-3.33-
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24a. 3504.31-M
OpenADSP-v05.6.0.2226.00.0418
eMMC-boot
Jan 13 2012,17:33:34
The entire process left my SD card intact as well. Amazing. It still says S-OFF as you expected. I may or may not attempt turning S-On again.
One comment I'd like to make about xda-developers. There is an amazing amount of information here. The biggest problem I've encountered is trying to figure out if I'm looking at, or have found, the latest information. Some times I'll find something that looks pertinent, only to find that I'm on page 2 of a 114 page thread, and the information I'm looking at is completely obsolete. It's tough for a noob to decipher it all. Anyway, thanks again for everyone's assistance. I think this is a proper place to terminate this particular thread. Now I'll start looking for the latest information on rooting my new HTC ONE. At least I have a fall back phone in my newly restored Sensation 4G. I'm not sure I'm in love the ONE yet, so perhaps I'll take it back. I'm within my 14 day return window.
Click to expand...
Click to collapse
actually are you sure that you flashed the ruu.exe correctly?
you still have the patched hboot and on top of the screen it still says firmware 3.33 which is the patched one
don't attempt to S-ON.probably you will brick the device
after ruu installation your bootloader should say relocked or locked on top of the screen
edit:if i remember well error 155 means a connection issue
rzr86 said:
actually are you sure that you flashed the ruu.exe correctly?
you still have the patched hboot and on top of the screen it still says firmware 3.33 which is the patched one
don't attempt to S-ON.probably you will brick the device
after ruu installation your bootloader should say relocked or locked on top of the screen
edit:if i remember well error 155 means a connection issue
Click to expand...
Click to collapse
Flashed? All I did was run the program. It did whatever it did. I think the 3.33 was somehow left over from flashing a PG58IMG I'd gotten from here>http://forum.xda-developers.com/showthread.php?t=1459767#2. That failed as explained earlier in this thread. I figured that running the RUU would overwrite that failure, and I'm surprised it didn't. All I care is that I'm now getting OTA updates correctly. Yeah, I won't be trying to S-ON. I've thought about rerunning the RUU (3.32) again, but for now I'm going to just leave well enough alone.
I forgot to mention. This information was in the documentation for the RUU
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
One last note. I returned the HTC ONE, and have reactivated the Sensation 4g which this thread is about. The HTC ONE hardware is wonderful, but I didn't like all the HTC ONE software "features" you can't turn off. Maybe I'll jump ship and go with the Samsung Galaxy S4. In the mean time, this Sensation 4G is okay.
Micalee said:
Flashed? All I did was run the program. It did whatever it did. I think the 3.33 was somehow left over from flashing a PG58IMG I'd gotten from here>http://forum.xda-developers.com/showthread.php?t=1459767#2. That failed as explained earlier in this thread. I figured that running the RUU would overwrite that failure, and I'm surprised it didn't. All I care is that I'm now getting OTA updates correctly. Yeah, I won't be trying to S-ON. I've thought about rerunning the RUU (3.32) again, but for now I'm going to just leave well enough alone.
I forgot to mention. This information was in the documentation for the RUU
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
One last note. I returned the HTC ONE, and have reactivated the Sensation 4g which this thread is about. The HTC ONE hardware is wonderful, but I didn't like all the HTC ONE software "features" you can't turn off. Maybe I'll jump ship and go with the Samsung Galaxy S4. In the mean time, this Sensation 4G is okay.
Click to expand...
Click to collapse
exactly the firmware 3.33 and the 1.27.1100 hboot version are from 3.33 universal firmware zip(from the thread you mentioned)
but as long as you are on S-OFF you can use any ruu.exe if you are also supercid
When the PG58IMG flash failed, I assumed at that time that it failed completely, and that no part of it actually worked. I'm too much of a noob to understand the pieces, or elements of the phone's software vs. firmware. I know the difference of course, but not as they relate to this phone, and certainly not as they relate to all the various flashes or other 'fixes' or other such mechanisms I see here on xda-developers.
If I get the nerve to attempt it, is there a way to get everything to a fully legitimate 'stock' situation? That is, just in case I upgrade to another phone again and want to sell this Sensation 4G? For example, I wonder what would be the result of a factory reset at this point? I realize it'll wipe everything out of course, but I wouldn't care.
Micalee said:
When the PG58IMG flash failed, I assumed at that time that it failed completely, and that no part of it actually worked. I'm too much of a noob to understand the pieces, or elements of the phone's software vs. firmware. I know the difference of course, but not as they relate to this phone, and certainly not as they relate to all the various flashes or other 'fixes' or other such mechanisms I see here on xda-developers.
If I get the nerve to attempt it, is there a way to get everything to a fully legitimate 'stock' situation? That is, just in case I upgrade to another phone again and want to sell this Sensation 4G? For example, I wonder what would be the result of a factory reset at this point? I realize it'll wipe everything out of course, but I wouldn't care.
Click to expand...
Click to collapse
A factory reset only deletes the data partition and cache, not any other partition. There are ROMs that are based on stock (and even stock). By fully legitimate 'stock' situation I believe you mean S-On and every thing stock. There are guies for that in the general and development forums.
I just got S-Off with Sun Shine, but can't seem to get SuperuserSU working (I was going to install TWRP from TWRP Manager after getting SuperuserSU.) Anyone know what I need to do? I looked for a thread that explained the process, but have not found anything. Many thanks!
Flash twrp from fastboot. Flash SuperSU from twrp.
Sent from my XT1254 using Tapatalk
I am trying to flash TWRP with Minimal ADB and Fastboot from here..... http://androidmtk.com/download-minimal-adb-and-fastboot-tool
I keep getting this for messages when I type the command flash twrp.img "cannot load 'twrp.img'
I know that the device is connected since it goes into fastboot when I type "adb reboot bootloader".
Any ideas?
Solved......I am a complete fool. I renamed the recovery image "twrp.img" so the actual file was "twrp.img.img". How embarrassing.....LOL! Time to just go and hit the bar and have a beer! I must have cabin fever after this winter and my mind is not functioning properly. ARGH!
therreid said:
Solved......I am a complete fool. I renamed the recovery image "twrp.img" so the actual file was "twrp.img.img". How embarrassing.....LOL! Time to just go and hit the bar and have a beer! I must have cabin fever after this winter and my mind is not functioning properly. ARGH!
Click to expand...
Click to collapse
It happens a lot[emoji14]
Sent from my XT1254 using Tapatalk
I posted this in the general questions thread, but I wanted to post here as well...
beaups said:
It happens a lot[emoji14]
Sent from my XT1254 using Tapatalk
Click to expand...
Click to collapse
I apologize in advance as I'm sure this has been asked toomany times to count, but I have searched and searched thread after thread to see if I can find a solution for about 23 hrs straight, I'm pretty much out of time & panicking now that I messed up beyond fixing. Any advice, help, or a point in the right direction to the right post would be very much appreciated!!!
So, the problem is, I'm not 100% sure but I think I have "soft bricked" my phone... I gained s-off through Sunshine about a week ago, I have been reading & researching how to root my phone for updating to a custom ROM running 6.0 MM for months now trying to prevent any issues & be as well educated as possible...
Last night I finally gained root access using Kingroot, then switching over superSU BUT of course, I had the problem with the binaries. I installed TWRP app to perform the recovery flash to ext SD because I do have a PC, but it's a work computer so I don't have administrator rights to install any programs/apps on the PC such as ADB, Flashify, etc.
Before I decided to restart my phone I had SuperSU running the # sign in the notifications center (re: the binaries), I also had the TWRP manager I chose my device model, but I did not install any files (at least I don't think I did). I was most concerned on my current backup & flashing that to my extSD. Which is what I thought I had done, or maybe I didn't do anything at all? BTW- I have removed the SD card & inserted into my PC to see what files were on it, and nothing!! Nothing at all to do with SuperSU nor TWRP (I have since installed the latest update SuperSU zip file on that card). All I know is I cannot get my phone on past the Verizon screen, I can perform a hard boot & get back into hboot /fastboot, I have all options on the menu, and have tried every one of them minus the 'factory data reset', 'apply from phone storage' or 'ramdump'. I would have typed in the information that the screen says in HBOOT but my phone literally just died from the screen being on so long :-/ I will add that info if needed once I can boot it back up without use of the charging cable.
Any help on what to do would be so greatly appreciated as apparently I'm freaking out & I'm thinking I'm way in over my head not knowing what exactly happened to cause this!!! Please Help:crying:
M-FayeHTC said:
I apologize in advance as I'm sure this has been asked toomany times to count, but I have searched and searched thread after thread to see if I can find a solution for about 23 hrs straight, I'm pretty much out of time & panicking now that I messed up beyond fixing. Any advice, help, or a point in the right direction to the right post would be very much appreciated!!!
So, the problem is, I'm not 100% sure but I think I have "soft bricked" my phone... I gained s-off through Sunshine about a week ago, I have been reading & researching how to root my phone for updating to a custom ROM running 6.0 MM for months now trying to prevent any issues & be as well educated as possible...
Last night I finally gained root access using Kingroot, then switching over superSU BUT of course, I had the problem with the binaries. I installed TWRP app to perform the recovery flash to ext SD because I do have a PC, but it's a work computer so I don't have administrator rights to install any programs/apps on the PC such as ADB, Flashify, etc.
Before I decided to restart my phone I had SuperSU running the # sign in the notifications center (re: the binaries), I also had the TWRP manager I chose my device model, but I did not install any files (at least I don't think I did). I was most concerned on my current backup & flashing that to my extSD. Which is what I thought I had done, or maybe I didn't do anything at all? BTW- I have removed the SD card & inserted into my PC to see what files were on it, and nothing!! Nothing at all to do with SuperSU nor TWRP (I have since installed the latest update SuperSU zip file on that card). All I know is I cannot get my phone on past the Verizon screen, I can perform a hard boot & get back into hboot /fastboot, I have all options on the menu, and have tried every one of them minus the 'factory data reset', 'apply from phone storage' or 'ramdump'. I would have typed in the information that the screen says in HBOOT but my phone literally just died from the screen being on so long :-/ I will add that info if needed once I can boot it back up without use of the charging cable.
Any help on what to do would be so greatly appreciated as apparently I'm freaking out & I'm thinking I'm way in over my head not knowing what exactly happened to cause this!!! Please Help:crying:
Click to expand...
Click to collapse
You are fine. Start fixing it by flashing the latest s-on ruu I have posted. This will NOT affect your s-off or unlocked boot loader status. Then when done flash twrp via fastboot. (Never use that stinking app). Then flash supersu zip in twrp to root your stock rom. If you have fast internet I can always you using team viewer (free app)
I'm still having trouble...
dottat said:
You are fine. Start fixing it by flashing the latest s-on ruu I have posted. This will NOT affect your s-off or unlocked boot loader status. Then when done flash twrp via fastboot. (Never use that stinking app). Then flash supersu zip in twrp to root your stock rom. If you have fast internet I can always you using team viewer (free app)
Click to expand...
Click to collapse
First,I appreciate you getting back tome so soon. I downloaded the latest RUU onto my SD card, then reloaded it into my phone in bootloader, nothing happened
Right now, I still cannot get past the red Verizon screen, my phone won't turn on fully... The options I have are my "Administrator PW protected work PC" that I cannot run fastboot on, or my Nextbook tablet. Would Team View work on either of these since my phone is out of the question?
Rightnow this is what my HBOOT screen is saying....
**UNLOCKED**
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT- 3.19.0.0000
RADIO- 1.12.20.1211
OpenDSP- v47.2.2-00564-M8975-FO.1024
OS-4.17.605.9
eMMC-boot 2048MB
Aug 11 2015, 22:31:04.0
Thanks in Advance!!!
M-FayeHTC said:
First,I appreciate you getting back tome so soon. I downloaded the latest RUU onto my SD card, then reloaded it into my phone in bootloader, nothing happened
Right now, I still cannot get past the red Verizon screen, my phone won't turn on fully... The options I have are my "Administrator PW protected work PC" that I cannot run fastboot on, or my Nextbook tablet. Would Team View work on either of these since my phone is out of the question?
Rightnow this is what my HBOOT screen is saying....
**UNLOCKED**
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT- 3.19.0.0000
RADIO- 1.12.20.1211
OpenDSP- v47.2.2-00564-M8975-FO.1024
OS-4.17.605.9
eMMC-boot 2048MB
Aug 11 2015, 22:31:04.0
Thanks in Advance!!!
Click to expand...
Click to collapse
If nothing ran you have the file either named wrong or have an extra .zip on the end of the name. Make sure you view file extensions to be sure. It's case sensitive and 0P6BIMG.zip
Leading character is a zero.
First part COMPLETE!
dottat said:
If nothing ran you have the file either named wrong or have an extra .zip on the end of the name. Make sure you view file extensions to be sure. It's case sensitive and 0P6BIMG.zip
Leading character is a zero.
Click to expand...
Click to collapse
Okay, I have hope. Thank You SO MUCH!!! Phone is on (upgrading currently), but IT'S ON:highfive: I think I accidentally used the s-off file instead of the s-on, and I did add the .zip onto that file (since it wasn't showing it w/ it, DUHHH). I will follow the rest of your instruction's very carefully later on, this will take a while, on app 80 out of 279 (bloatware, ugh!!) Hopefully, it goes more smoothly & I won't have to bother you again :fingers-crossed:
Thanks Again!
P.S. Will be contributing ASAP once I get this mess cleaned up. I really do appreciate all of your hard work & the magic that you make happen!!
M-FayeHTC said:
Okay, I have hope. Thank You SO MUCH!!! Phone is on (upgrading currently), but IT'S ON:highfive: I think I accidentally used the s-off file instead of the s-on, and I did add the .zip onto that file (since it wasn't showing it w/ it, DUHHH). I will follow the rest of your instruction's very carefully later on, this will take a while, on app 80 out of 279 (bloatware, ugh!!) Hopefully, it goes more smoothly & I won't have to bother you again :fingers-crossed:
Thanks Again!
P.S. Will be contributing ASAP once I get this mess cleaned up. I really do appreciate all of your hard work & the magic that you make happen!!
Click to expand...
Click to collapse
Well if you used the s-off one that's fine too. You will be rooted already. Just need to flash the latest twrp image and you will be fine.