Related
NOTE: THIS MIGHT NOT WORK IF YOU INSTALLED THE HTC RUU USING A GOLD CARD IN THE FIRST PLACE... I'M LOOKING FOR TESTERS TO CONFIRM THIS.
I tried this when I first ended up with 1.76.0007, and it worked, but I didn't want to take a chance trying it again. I thought it was just a coincidence or my eyes were playing tricks on me. I was scared that I would brick my phone...
I finally got the guts to try it again and it worked!
Here's how...
You'll need:
- HTC 2.53.707.2 Test Build SAPPIMG.zip (Thanks Amon_RA!!)
http://rapidshare.com/files/267446145/2.53.707.2_-_sappimg.zip
- 1.76.2007 'Engineering' SPL
http://rapidshare.com/files/313034025/update-hboot-1.76.2007-signed.zip
- 6.35.07.29 32A Radio Image
http://rapidshare.com/files/313035429/radio-6.35.07.29-32A.zip
- Amon_RA Hero Recovery
http://forum.xda-developers.com/showthread.php?t=561124
- Gold Card
http://forum.xda-developers.com/showthread.php?t=572683
Caveats!!!
- Your splash screen will be changed to the HTC MAGIC screen and not your wireless provider's screen. I know of no way to change this.
- This might brick your phone... I was sweating bullets when I was running this on my phone because I wasn't sure it would work, and I'm still not 100% sure this will work for everyone. YMMV
Steps:
- Create your Gold Card! This is not just a suggestion. You need a proper gold card before starting. I used the card that came with my phone and it worked fine.
- Back up whatever you can from your existing setup. You can't go back and can't recovery anything here. Google sync should backup most of your stuff though.
- Shut off your phone and put the 2.53.707.2-sappimg.zip file on your gold card. Make sure it's named 'sappimg.zip'. Put the gold card in your phone.
- Turn on your phone using VolDown and Power. It will boot into HBOOT mode and within 10 seconds will scan your SD card. Do not press anything at this point! It will find SAPPIMG.zip only if it is named SAPPIMG.zip and not SAPPIMG.zip.zip... Get it? As it's loading SAPPIMG.zip it will show a blue progress bar on the right hand side of the screen.
- It will then check that SAPPIMG.zip is not corrupt.
- When prompted 'Do you want to start update?', press in on the trackwheel (Action key).
- The process will update the SYSTEM, USERDATA, BOOT, BOOTLOADER (SPL), RADIO_V2, RECOVERY and SPLASH.
At this point, you now have 3.22.20.17 32A Radio image and 1.33.2010 Engineering SPL. You can now flash any 32A Recovery and ROM and carry on like nothing happened and you didn't make a big mistake by flashing the HTC RUU. Next time don't be so impatient!
If you decide to stick with this Radio and SPL then I suggest flashing the Amon_RA 32A Recovery and picking a 32A ROM to run.
If you want to flash new HTC 3.03 ROMs using the 1.76.2007 Eng SPL and the new radio, then continue on. There are advantages to this, but at this point it's not for rookies.
Steps
- Download the recovery image, radio image and SPL (hboot) update into a folder of their own.
- Put the update-hboot-1.76.2007-signed.zip onto your SD card.
- Open a command prompt, navigate to the folder you saved all of the files in. This assumes that your Android SDK Tools folder is in your PATH environment variable)
- Boot your phone it fastboot by holding Back and Power.
- Once in FASTBOOT USB, type in these commands, hitting enter after each one.
Code:
fastboot flash radio radio.img
fastboot flash recovery recovery-RA-hero-v1.3.2.img
- Once it's finished, turn off your phone by pressing MENU.
- Start up your phone into recovery mode by holding Home and pressing Power.
- Apply the update-hboot-1.76.2007-signed.zip update.
- NOTE THAT THE RECOVERY REQUIRES YOU TO PRESS THE HOME KEY TO SELECT AN OPTION.
- Reboot your phone using the recovery option. Your phone will reboot back into recovery, and will format the CACHE. Don't worry about this, it's supposed to happen. If it doesn't boot back into recovery after a few minutes, pull the battery and power it on while holding the HOME key.
- Once it's booted into recovery mode, shut off your phone by pulling the battery.
- Start it back up into FASTBOOT mode by holding Back and pressing Power.
- You should now see the following on the screen:
Code:
SAPPHIRE PVT 32A ENG S-OFF H
HBOOT-1.76.2007
CPLD-12
RADIO-6.35.07.29
Aug 21 2009,18:19:15
If your phone doesn't display exactly this information, then you might have made a mistake along the way and should consider yourself lucky that your phone boots at all. Try again from the beginning.
At this point, you can enter the recovery menu and run the CursorSense update.zip from:
http://forum.xda-developers.com/showthread.php?t=592856
This was probably the closest I came to bricking my phone, but I'm sure it works now.
Good luck and happy rooting!
That won't work because if you Flashed via RUU it'll say that your version is older.
If you only flashed SPL/radio and not rest of the ROM i guess it could work.
it can break the Perfected SPL?
When i was flashed the sense-ui by htc?
mkrle said:
That won't work because if you Flashed via RUU it'll say that your version is older.
If you only flashed SPL/radio and not rest of the ROM i guess it could work.
Click to expand...
Click to collapse
You might have a point here... I thinks that maybe I didn't think this through entirely...
Would anybody be willing to test? Just to see...
Thanks,
Quite tempting to try, as I did flash via the RUU. Will look into it.
cursordroid said:
You might have a point here... I thinks that maybe I didn't think this through entirely...
Would anybody be willing to test? Just to see...
Thanks,
Click to expand...
Click to collapse
Main Version is older....
I've tried it, didn't work, but again who knows it might work for someone. There was a guy who said he got s-off SPL from a regular RUU so you never know.
Main version is older...
Main Version is older
I tried it on HBOOT-1.76.0007 (SAPP10000)
Hong Kong Sense Update from 17/11/09
Same problem NOTHING NEW:
Main Version is older
main version is older, flashed with RUU
i know 2.53.707 sappimg.zip file saved a few people, they also flashed official ruu, but get spl info like this: 1.76.0007(SAPP*****), and s-off.
but for most of us, we get this: 1.76.0007(SAPP10000), and s-on. therefore, we trying to use 2.53.707 sappimg.zip file and get "main version is older, update failed". and, if we use fastboot, it says "remote: not allow".
the only difference is the SAPP model text following 1.76.0007. if it's *****(all "*" symbols, not means any key), security is off, no version check, and it work! if it's 10000(maybe 50000 is also the same but i'm not sure), we stucked at version check.
so, what can we do...
tigerdigi said:
i know 2.53.707 sappimg.zip file saved a few people, they also flashed official ruu, but get spl info like this: 1.76.0007(SAPP*****), and s-off.
but for most of us, we get this: 1.76.0007(SAPP10000), and s-on. therefore, we trying to use 2.53.707 sappimg.zip file and get "main version is older, update failed". and, if we use fastboot, it says "remote: not allow".
the only difference is the SAPP model text following 1.76.0007. if it's *****(all "*" symbols, not means any key), security is off, no version check, and it work! if it's 10000(maybe 50000 is also the same but i'm not sure), we stucked at version check.
so, what can we do...
Click to expand...
Click to collapse
yes, i also found some person get this: spl info like this: 1.76.0007(SAPP*****), and s-off, if in this state, they can flash any rom/spl/radio.
can anybody find how to go to this state? if we can, we can do anything.
I dont know any thing further other than I got 0007 and s-on
so, all I can do is bump...
I have SAP***** for some time, even before i flashed 1.76 SPL but it's s-on, so i think it's not directly related.
P.S. I think i got SAP**** by playing around with different radios and all i can say is *don't* change (especially downgrade) radio unless you're sure what you're doing and/or have a matching SPL.
still no luck searching for a root cure for 1.76.0007
I accidentaly posted this to another thread (http://forum.xda-developers.com/showpost.php?p=5196720&postcount=7) although it was meant to be posted here:
I was missing the Android Market wich didnt come with the Singapore RUU so just downloaded the the HK RUU, ran it with a gold card (dont know if thats really neccesary) and got Market.
The point being - if people are on the Singapore official update, would it be somehow possible to "patch" the HK RUU files from the temporary folders where it stores the files for the update? To say, replace the original HBOOT with an ENG HBOOT (possibly *.2007?)?
Since Singapore rom version is lower than the HK one..:
Singapore: ROM Version: 3.03.728.4(For Indonesia, Malaysia& Vietnam only)
HK-E: ROM Version: 3.03.990.6
..possibly it would skip the "wrong main version" or whatever it says during the update..?
Am I onto something here?
No because the (zip) files are signed and perfect SPL won't accept flashing them if they are modified.
so is there a newer spl yet?
jamesyb0i said:
so is there a newer spl yet?
Click to expand...
Click to collapse
nobody, help we. amon_ra, and all the developers.. because don't help us??? we need help!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
We need either kernel exploit to get root, or HTC signed RUU with 3.x ROM and s-off SPL. period.
Hello,
I try to unlock my bootloader with htcdev but i get this error :
C:\Users\Administrator>cd C:\Android
C:\android>fastboot oem get_identifier_token
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.009s]
finished. total time: 0.009s
How to fix this ? :$
I'm looking too, but for the [Doubleshot].
Trying the same thing myself on the HTC Doubleshot (MyTouch 4G Slide) and no joy, same exact error.
ericosman, did you by chance follow all the advice on HTC's site -- including specifically installing HTC Sync? I didn't install Sync because it looks like stuff I won't use and don't need, except that Sync has some dependencies (like a USB BMP Driver, whatever that is) that might make the difference. I haven't tried yet but I plan to.
I've tried two different versions of Fastboot, one I downloaded from masterjason.com and another I downloaded from Google's Android SDK manager. Both behave identically, despite one being nearly a megabyte where the other was 70 kilobytes.
I've tried reinstalling USB drivers, no joy.
I can get fastboot devices to work, as well as adb anything when the phone is booted, so I don't think drivers are really the issue.
I think it's HTC making a blanket promise that all the phones in that list can do this and indeed not all can.
[EDIT 2012-01-07: Add more info I found]
Gotta love it. Edited the post, and when saving, was told to refresh and log in. Then I wasn't given a chance to copy-paste what I typed. Annoying.
Anyway, see if I can remember what all I typed...
uhm...
I found through Google, and directed to Yet Another Android Forum somewhere on the 'net, that fastboot oem h will provide you a list of commands that are supported, and get_identifier_token was not among them. I suspect it's the phone's bootloader which contains supported commands, not Fastboot executable itself, so it may require downgrading/upgrading to a different HBOOT that has the necessary command support.
I did find readsecureflag which returns the integer "3" on my S-ON device. I assume then that the command I found called writesecureflag similarly takes an integer value, but what value to feed it, I don't know, and I don't want to risk my phone. Seems benign enough, but I know from computer programming that anything looking benign is not always.
Anyway, if you run fastboot oem h and get_identifier_token isn't there, I'd recommend giving up on this particular method of rooting.
Hope this helps.
[Edit 2012-04-15: Strikeout above no longer applicable info]
Turns out, see Aisho's post below, which sums up what eventually worked for me.
I actually had to wait for an OTA to be available long enough for a dev to package it up to a bootloader-flashable package, which included the get_identifier_token. Once I had that version on my phone, I was able to get the token to HTCDEV and get my bootloader unlocked. Not full access, but not bad: The only downside is if I need to flash a kernel I have to do it separately from the ROM through fastboot, and I don't think I can update my radio (not that I should need to). But hey, I can flash a custom ROM and get rid of this nasty crap T-Mobile thinks everyone should have (I will never play bejeweled, so I don't even want that adware/nagware on my phone).
[/edit]
I actually had this same problem with my HTC Wildfire S, and found this thread in searching for answers -- since I figured it out, I figured I'd put the solution out there.
My HBOOT was precisely the version HTC was advertising on their site as necessary for the unlock, which made it all the more perplexing when I repeatedly got this error. But then it occurred to me that while my version might be the same, HTC had stuck a neat little asterisk* next to the Wildfire S initially, saying that it required a new HBOOT anyway. I'd thought I was smarter than they were, but really what's different in the new download is the incorporation of just the command you're missing here. Since the ability to unlock is fairly new (through HTC officially, I mean) they're providing new HBOOTs with that command line included. I flashed the new HBOOT (even though it was exactly the same version) and lo and behold when I tried it again, it accepted the fastboot oem get_indentifier_token command.
I'd check to make sure that the HTC Legend doesn't have an asterisk as well, and maybe redownload the HBOOT anyway just in case. It can't hurt.
Aisho said:
I flashed the new HBOOT (even though it was exactly the same version)
Click to expand...
Click to collapse
I'm having the same problem on htc salsa, I have the version it says i should have, but have no get_indentifier_token, how is HBOOT updated?
My phone is S-ON and Hboot is 1.07.0000
HBOOT is updated via bootloader mode (on my phone, assumably the same for most HTC phones). You will need the correct HBOOT for your phone, and it will probably have to be contained within a full update package (for my phone, it's PG59IMG.ZIP, for the Dream it was DREAIMG.ZIP, your phone model will have its own filename). That file goes on the SD card, you boot into bootloader (usually, remove battery to ensure phone is full off, replace battery, and power up while holding the "VOLUME DOWN" button in). It then checks the file and asks you if you want to update.
However, if your phone is the same or newer version as the file you are trying to use, there's a good chance it will not work (the phone will not downgrade (usually (I think (I could be wrong) ) ) ).
You might also be amongst the lucky few who have a phone with what's called an RUU available. That's an .EXE file you run in Windows, connect your phone, and it writes what's in the file directly to the phone regardless of version.
HIH.
I have the upgraded HBOOT version as Im following a thread for how to do it, which incidentally isnt working, when I go to the bootloader menu it finds the file but does not up date it. It has been updated to the current version stated on htcdev with a FOTA update which may be why the HBOOT upgrade doesnt work.
I have the HTC salsa and it does reference RUU a few times. I dont use windows but HTC sync doesnt seem to find the phone, I have tried many things to get it working
Am I meant to run the EXE provided by htcdev and dont run HTC SYNC? Should I be in the bootloader menu/recovery first before running it?
@ericosman
did you follow every single steps ?
I just did it on my Legend (24 hours ago), in the end I followed the post of BlaY0 (http://forum.xda-developers.com/showpost.php?p=22613990&postcount=62) and it worked great.
And yes, the RUU file is the one of a few MiB that you find at the very beginning at HTCdev.
The only trick is that I had to restore my data backup but also my boot backup, otherwise I was stuck in the hboot.
I did it by flashing the recovery image, as I deleted my old update.zip of ClockWorkMod, following the steps of http://forum.xda-developers.com/showthread.php?t=1290841 (see the end of the post: 'New recovery'). Then I went to 'Advanced restore' and restored both my boot image and my data back.
Always backup your system before playing around !
i must be reading it wrong
where is says install htc sync and use the file below
I took it as use the file from htc sync
no
execute the file below
chris... said:
i must be reading it wrong
where is says install htc sync and use the file below
I took it as use the file from htc sync
no
execute the file below
Click to expand...
Click to collapse
Alright, let's try again.
Before the step 1 of HTCdev, it asks you to upgrade your phone to the latest RUU. You don't have to. (see BlaY0's post [1])
Just download the RUU file, thus you will be able to retrieve the very hboot's zip (just run the EXE, don't go through the installer but instead locate its temporary extraction folder with the task manager and get that rom.zip).
They only want you to install HTC Sync so that your phone is recognized by Windows and the RUU can located it.
[1] BlaY0 explains that you don't have to upgrade to the latest HTC ROM or even RUU.
got it, and dump that zip file with the correct file name onto the root of the sdcard and start the bootloader
YAY it works, time to proceed to unlock
The version I got from a different post must not have been the correct one
im sure im bumping an old thread, but im trying to unlock an old espresso, but its having the same issue as the OP, i cant find the RUU with the new hboot, it currently has the 1.02 hboot, any clues?
Have you tried following the steps I referred to ?
Look at my two posts.
In fastboot, What is displayed besides the hboot version ? Something like "unlocked" ?
If note you have to re-flash your hboot with HTC dev method, once again read the post I linked to.
Sent from my Legend using XDA
just to add that on my MyTouch 4G slide I had hboot-1.44.0007 and gave me the same error as the first post when trying to unlock through htcdev.com. I did an OTA update to HBOOT-1.45.0013 (Software version 1.63.531.2 710RD) then went back to htcdev.com and it worked without problems
Getting this while trying to re-unlock evo 3d ics. hboot 1.58.
It's an old thread but maybe it's helping someone...
If you receive the error described in the topic title/first post you need to simply register to htcdev dot com and follow each step(including the 1st step because that's actually what you need to do )
i got same problem w my Z3 plus hbot will work on my z3 plus????????
Hi all, here's a long story cut short:
1. Flashed the stock 2.23.707.2 de-odexed rom on my One XL (the S4 version of One X), was running 4.0.4 fine
2. Didn't like the new radio that came with 2.23, tried flashing back to the 1.88 Asia radio which worked best for me, took much longer than usual then appeared to be successfully flashed only to find in bootloader the radio version hasn't changed and once rebooted the baseband info becomes "unknown" and the phone sees no signal at all, probably a messed up radio...
3. (the stupidest of my moves) Relocked my phone using the HTCdev way in an attempt to RUU back to stock and start from scratch, failed with an error code140 (not surprisingly due to the higher hboot version), then noticed the HTCdev unlock code doesn't work anymore. Tried obtaining the unlock_code.bin again in case something changed, but new code is no good either.
Therefore I now have a phone that is Relocke and can't use TWRP recovery, can't boot up as it hits a block at the initial setup (explained below), and one that for some strange reason cannot be unlocked again. I can boot to bootloader, go to fastboot and push the unlock_code.bin file via usb, it will go through and i see the normal unlock confirmation screen on the phone, but choosing yes each time the phone will reboot and when checking in bootloader it still shows the phone is "Relocked". What's worse, after "unlcoking bootloader" the phone now goes into the setup wizard each time it boots up, but perhaps due to the messed up radio thing it can't read the carriers available and thus only shows the white screen with the HTC logo on it, no way forwar. This is where I get completely stuck now.
I can't post in the Development page due to my freshness in xda, but I am not a complete newbie and have owned a Desire, a Sensation and now the One X, each time going through the root/supercid/custom recovery/custom rom/flashing radios processes without major problems so I will say I do have basic knowledge with all these things.
Anyway if someone can shed some light on how I can get out of this mess without having to send the phone back to HTC for some pricey repair, it would be extremely appreciated.
Thanks for your attention,
Sunster
sunster00 said:
Hi all, here's a long story cut short:
1. Flashed the stock 2.23.707.2 de-odexed rom on my One XL (the S4 version of One X), was running 4.0.4 fine
2. Didn't like the new radio that came with 2.23, tried flashing back to the 1.88 Asia radio which worked best for me, took much longer than usual then appeared to be successfully flashed only to find in bootloader the radio version hasn't changed and once rebooted the baseband info becomes "unknown" and the phone sees no signal at all, probably a messed up radio...
3. (the stupidest of my moves) Relocked my phone using the HTCdev way in an attempt to RUU back to stock and start from scratch, failed with an error code140 (not surprisingly due to the higher hboot version), then noticed the HTCdev unlock code doesn't work anymore. Tried obtaining the unlock_code.bin again in case something changed, but new code is no good either.
Therefore I now have a phone that is Relocke and can't use TWRP recovery, can't boot up as it hits a block at the initial setup (explained below), and one that for some strange reason cannot be unlocked again. I can boot to bootloader, go to fastboot and push the unlock_code.bin file via usb, it will go through and i see the normal unlock confirmation screen on the phone, but choosing yes each time the phone will reboot and when checking in bootloader it still shows the phone is "Relocked". What's worse, after "unlcoking bootloader" the phone now goes into the setup wizard each time it boots up, but perhaps due to the messed up radio thing it can't read the carriers available and thus only shows the white screen with the HTC logo on it, no way forwar. This is where I get completely stuck now.
I can't post in the Development page due to my freshness in xda, but I am not a complete newbie and have owned a Desire, a Sensation and now the One X, each time going through the root/supercid/custom recovery/custom rom/flashing radios processes without major problems so I will say I do have basic knowledge with all these things.
Anyway if someone can shed some light on how I can get out of this mess without having to send the phone back to HTC for some pricey repair, it would be extremely appreciated.
Thanks for your attention,
Sunster
Click to expand...
Click to collapse
Try this
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
so this method allows u to downgrade no matter whats your version.. should workout
jags_the1 said:
Try this
First, make sure you're in fastboot mode, then type 'fastboot oem rebootRUU'
Next, make sure you have the .zip RUU file in the same folder and type 'fastboot flash zip XXX.zip' (replace XXX with whatever it's called, of course)
Now, you can see what is actually happening when you are flashing the RUU. In my case, there was 2 points where it told me to "re-flush image immediately" or something like that. When I ran the last command again (fastboot flash zip XXX.zip) it went a bit further each try, but it took until the 3rd try before it was successful.
thanks to kilo89 for method
so this method allows u to downgrade no matter whats your version.. should workout
Click to expand...
Click to collapse
Hi mate thanks for offering advice and help. I have not had to use your method as I decided to give the HTC bootloader unlock code one final try before proceeding to your rescue plan and all of a sudden it was successful again. I got into recovery and did a nandroid restore so am back online again, but have nevertheless made note of your method in case I become stuck again in the future. Thanks anyway for your reply! :good:
I am new to all of this, and dumb as a rock. That being said, I have soft-bricked this phone. I loaded PACman v15.3 primoc inyourface09.zip first
Went to boot loop. In trying to fix that, I did a bunch of other stuff that didn't work and I don't really remember what all I did-been a week of this chaos. Last thing I did was load Cyanogen Mod 9, which boot looped. Still shows this when I go to fastboot:
*** UNLOCKED ***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0928
eMMC-boot
May 14 2012.20:27:30
Here is other possibly useful info.
MWID: Hex:A10000023E805EE
SN: FA2AJX40824
MB: 31B15AD04215
MEID Dec: 270113181115205870
SD Checking
LOADING
wRONG OR NO ZIPPED IMAGE [PK76IMG.ZIP]
lOADING
NO IMAGE [PK76IMG.NBH]
same for .TAR, .AES, .ENC
I then loaded gapps-jb-20120726-signed.zip, JmzStockDeodex-VirginMobile.zip and JmzStockodex-VirginMobile.zip
I still get the HTC white screen with red disclaimer. Then goes to buzz, lightning, Red Virgin Mobile splash screen with sound, and reboots to HTC white screen-boot loop.
When I got a PK76IMG.ZIP and tried to flash it, it says it can't open the zip file.
But I can still get to the Hboot, Fastboot screen and recovery. Backup was empty :s
Tried to load a different recovery, but just like pacman, twrp won't go away.
And just so you know, I did factory reset a gazillion times.
Help! What have I done, and what can I do to fix it? I am comfortable with command lines, poking around in code, etc., but not with a totally new device like this...obviously, too much to mess up.
.
..
Still need serious help! found a possible reason for problem
Seems my HBoot 1.53.00.00 is for GSM; my phone is CDMA. Do how do I install/where do I download the correct hboot for vmt120 (the model number for this One V)?
I have been researching the phone and the problem, not just posting for help ad nauseum. I really need some help, please.
Thanks in advance, folks.
goofed again said:
Seems my HBoot 1.53.00.00 is for GSM; my phone is CDMA. Do how do I install/where do I download the correct hboot for vmt120 (the model number for this One V)?
I have been researching the phone and the problem, not just posting for help ad nauseum. I really need some help, please.
Thanks in advance, folks.
Click to expand...
Click to collapse
Were you able to get a backup of the original config, (before you first rooted it?)
(I have the same phone, same radio, (hboot 1.57), for NTelos, and am able to boot, but just no wifi/mobile data).. So, if you have a good backup, I might be able to trade a stock kernel that works for my phone.
I'm desperate also, so I know how it feels to have a machine that doesn't work,...
goofed again said:
I am new to all of this, and dumb as a rock. That being said, I have soft-bricked this phone. I loaded PACman v15.3 primoc inyourface09.zip first
Went to boot loop. In trying to fix that, I did a bunch of other stuff that didn't work and I don't really remember what all I did-been a week of this chaos. Last thing I did was load Cyanogen Mod 9, which boot looped. Still shows this when I go to fastboot:
*** UNLOCKED ***
PRIMOC PVT SHIP S-ON RL
HBOOT-1.53.0000
RADIO-1.00.00.0928
eMMC-boot
May 14 2012.20:27:30
Here is other possibly useful info.
MWID: Hex:A10000023E805EE
SN: FA2AJX40824
MB: 31B15AD04215
MEID Dec: 270113181115205870
SD Checking
LOADING
wRONG OR NO ZIPPED IMAGE [PK76IMG.ZIP]
lOADING
NO IMAGE [PK76IMG.NBH]
same for .TAR, .AES, .ENC
I then loaded gapps-jb-20120726-signed.zip, JmzStockDeodex-VirginMobile.zip and JmzStockodex-VirginMobile.zip
I still get the HTC white screen with red disclaimer. Then goes to buzz, lightning, Red Virgin Mobile splash screen with sound, and reboots to HTC white screen-boot loop.
When I got a PK76IMG.ZIP and tried to flash it, it says it can't open the zip file.
But I can still get to the Hboot, Fastboot screen and recovery. Backup was empty :s
Tried to load a different recovery, but just like pacman, twrp won't go away.
And just so you know, I did factory reset a gazillion times.
Help! What have I done, and what can I do to fix it? I am comfortable with command lines, poking around in code, etc., but not with a totally new device like this...obviously, too much to mess up.
Click to expand...
Click to collapse
Hey! Just restore your Radio back to stock. Google "RUU Stock for HTC ONE V VM" and there are some articles that could help you. Basically, you just run the RUU and extract some files in it.
---------- Post added at 11:23 PM ---------- Previous post was at 11:17 PM ----------
plebevt said:
Were you able to get a backup of the original config, (before you first rooted it?)
(I have the same phone, same radio, (hboot 1.57), for NTelos, and am able to boot, but just no wifi/mobile data).. So, if you have a good backup, I might be able to trade a stock kernel that works for my phone.
I'm desperate also, so I know how it feels to have a machine that doesn't work,...
Click to expand...
Click to collapse
So guys, if you still have this problem here' what you'll need to do.
Originally Posted by CafeKampuchia
Before you start, you will need to set up your computer to properly recognize the phone. You probably did this when rooting originally, but just in case... Install SDK tools for Android, Java runtime, and HTC Sync.
About HTC Sync: The only reason you need HTC Sync installed is for the USB drivers that come with it. But the program itself has been known to cause conflicts. Make sure that HTC Sync is not running in the background by opening Task Manager in Windows and killing it if you find it lurking in there.
Here we go:
First of all, google "RUU of HTC ONE V CDMA" or sumthing. then you'll find alot of things. Choose the SPRINT/VM Then:
1. Download the correct RUU for your device from Football's Primo Shipped ROM Collection.
2. Charge the battery above 50% or for at least one hour. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up. While the RUU wizard is open,(LET IT OPEN UP, DONT DO ANYTHING!) find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC Recovery and it is needed to run the RUU.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT/B] using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools. Flash the stock recovery extracted in step 3 above using the following command:
Code:
fastboot flash recovery recovery.img
or
Code:
fastboot flash recovery recovery_signed.img
6. Relock the bootloader using the following command:
Code:
fastboot oem lock
7. Re-run the RUU. It will restore the device to it's original condition, locked (though *** RELOCKED ***) and unrooted.
Once the install is done you'll have unlock the bootloader again using the token you already have from the first time, reflash CWM Recovery and re-root. All this will be 10x easier than the first time.
If you do re-root your phone, be 100% you backup the stock ROM in ClockworkMod Recovery before making changes!
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.