Database Info

[RUU]RUU_SuperSonic_GB_Sprint_WWE_4.54.651.1_Radio_2.15 .00.0808_NV_2.15

Here the latest shipped RUU for SuperSonic
http://www.filefactory.com/file/cfe....15.00.0808_NV_2.15_release_220182_signed.exe
Enjoy!

As always, thanks
Sent from my PC36100 using xda premium

Nice! But just curious. How do you use this? Of all the things I know about rooting and whatnot this is the only thing I'm stumped on...
Sent from my PC36100 using XDA App

You run it on your pc. It returns your phone to stock
We're comin from a pure power source.

Football said:
Here the latest shipped RUU for SuperSonic
http://www.filefactory.com/file/cfe....15.00.0808_NV_2.15_release_220182_signed.exe
Enjoy!
Click to expand...
Click to collapse
Thank you Sir!

as always, thank you!!

exactly what I needed for my newly purchased evo 4G, big thanks!

I keep getting Error 170 when trying to run this... Running Win7 x64. Is there anything special I need to do to get this to work?

Drakhar said:
I keep getting Error 170 when trying to run this... Running Win7 x64. Is there anything special I need to do to get this to work?
Click to expand...
Click to collapse
That's what I am wondering. Every other RUU he uploaded were zip files that you just flashed through HBoot & this one is a exe file. How do you use this? This is a non-Rooted Rom right?

Drakhar said:
I keep getting Error 170 when trying to run this... Running Win7 x64. Is there anything special I need to do to get this to work?
Click to expand...
Click to collapse
Don't know exactly where you coming from and going to, 4.53 to 4.54? But something and that has been working and continued for me.
This ruu.exe is ran from the PC through usb debugging enabled, and having the correct drivers installed, I am on xp so I ran latest drivers maually, for higher o/s ver. its going to regonized the android and try to install autmatically....press stop/cancel you will need to configure it manually to have it install the correct drivers.
assuming you done this already, then enable settings>applic>develop>usb-deb and device powered on to home screen, from pc just double click the .exe and go through simple menu's and continue to process.
good luck and hope it helps..
latest Drivers
RUU4.54

Thank football!!!!

Anybody checked if stagefright libs were updated by HTC?

I have a custom slash screen on my EVO, will this put back on the oem Sprint one back on it? I just bought a E3D and am selling my EVO.

doeboy1984 said:
I have a custom slash screen on my EVO, will this put back on the oem Sprint one back on it? I just bought a E3D and am selling my EVO.
Click to expand...
Click to collapse
it should!!!

brad
my dilemma is that I have a rooted evo running a synergy rom on Hboot .79 and Radio 1.39
thing is that the s status is S-ON on this particular phone and unrevoked forever does not work on that radio version.
I've tried to upgrade the radio through clockwork recovery with the prepackaged zip yet when I reboot the phone still shows the old radio version.
I've tried installing an RUU from the PC but they all error out.
I'm looking for an RUU packaged in an install-able .zip that includes updated Radios Kernels Hboot and ROM in one. Is that even possible so i can fix this phone and get it some updated radios?!

brad560 said:
it should!!!
Click to expand...
Click to collapse
So I know you say it "should" but I don't want to RUU and then still have my batman logo as my splash screen, that would suck. I would ave to re-root it to try and find a splash .img, but I guess I will try it out and see if it works.

skunkd said:
brad
my dilemma is that I have a rooted evo running a synergy rom on Hboot .79 and Radio 1.39
thing is that the s status is S-ON on this particular phone and unrevoked forever does not work on that radio version.
I've tried to upgrade the radio through clockwork recovery with the prepackaged zip yet when I reboot the phone still shows the old radio version.
I've tried installing an RUU from the PC but they all error out.
I'm looking for an RUU packaged in an install-able .zip that includes updated Radios Kernels Hboot and ROM in one. Is that even possible so i can fix this phone and get it some updated radios?!
Click to expand...
Click to collapse
just saw you replied to me, sorry for the lateness. first of all, i would try aman ra for recovery, as many users have had problems with clockwork. as far as the ruu, how can you be s-on and still be rooted?

brad560 said:
just saw you replied to me, sorry for the lateness. first of all, i would try aman ra for recovery, as many users have had problems with clockwork. as far as the ruu, how can you be s-on and still be rooted?
Click to expand...
Click to collapse
I have the opposite issue. I have S-OFF (Revolutionary) but on stock unrooted (brought the phone to Sprint for a broken power button, and they ended up not fixing it, but flashed 4.53 stock rooted).
How the hell do I get this ROM rooted since Revolutionary doesn't want to root it because the bootloader is unlocked and I can't go to recovery because once I'm on the HTC white background fastboot screen, the volume button are locked and my power button is dead anyway...
I'm trying this Ruu .exe hoping it will give me S-ON but I'm doubtful it will happen...
EDIT: Just as I thought, I'm now on stock rooted 4.54 with S-OFF. And no power button

doeboy1984 said:
So I know you say it "should" but I don't want to RUU and then still have my batman logo as my splash screen, that would suck. I would ave to re-root it to try and find a splash .img, but I guess I will try it out and see if it works.
Click to expand...
Click to collapse
They will always update the splash screen, it helps to identify the firmware and rom versions at a glance. During install the setup program will create a temp folder with PC36IMG.zip or update.zip look in this zip file and you should see a splash.img file or something like that (sorry haven't looked HTC updates since my Hero Days).
Sent from my PC36100 using xda premium

Any way to get this to be able to install through the bootloader because my usb port is broken on my phone and it won't stay connected to the computer and I need to get Unrooted, s-off, return to stock, stock hboot because I need to take my phone to Sprint to get phone replaced/fixed. Thanks.
Sent from my PC36100 using xda premium

[Q] Sensation died whilst in use, won't charge, won't switch on.

As the title states, I have a possible brick on my hands, the phone isn't mine and the person who uses it doesn't really mess with overclocking and such, it was running Miks rom GSM, and not overclocked (running at 1.18ghz) No overvolt either, it is an s-off device, before this it was a fully functional sensation.
Basically what i'm told is that the phone was in use and it just switched off.
No lights, no power, have tried three batteries, about 10 chargers, different usb cables, can't get to bootloader or recovery, adb won't recognise it, it appears to be just a dead phone, personally i'm guessing it's the mainboard but i thought i'd ask anyway, there are no signs of water damage or major droppage.
Popped over to dexters unbricking project but as i said the phone won't come on so it won't work.
As i said before it's not my phone, but i'd like to do a friend a favour if i could.
Any ideas?
Before anyone asks, I cannot get to the bootloader or recovery.
Many thanks.

Hope you get it working..but it's becoming quite common and no one seems to have any ideas. Mine did the same thing...and I just had the motherboard repaired!

Yeah, here is the other thread.
http://forum.xda-developers.com/showthread.php?t=1624293
On such a popular Rom it is a bit unsettling.
Is it firmware, radio, kernel, or rom?
I hadn't seen this many Sensations die like this back on Gingerbread.

I am not sure...seems to have happened on a few different ROMs...so maybe it's not a specific ROM? I just got mine back and rooted and S-off as I needed the root to unlock the simlock...but I am scared of installing any custom ROMs or radio etc....I am thinking maybe I'll just wait for the official t-mobile ICS update...

gustav30 said:
Yeah, here is the other thread.
http://forum.xda-developers.com/showthread.php?t=1624293
On such a popular Rom it is a bit unsettling.
Is it firmware, radio, kernel, or rom?
I hadn't seen this many Sensations die like this back on Gingerbread.
Click to expand...
Click to collapse
I'll be starting a thread to determine just that... I have my suspicions, but I'd like to know in one place what everyone was running.

I was running ARHD 6.6.2 Just flashed the ROM.. and seem to flash fine, able to boot up. Even reinstalled all the apps...then while calling...had this long tone from the phone...and phone was unresponsive...I pressed power button.. and it turned off.
The first time..it actually turned back on....so I thought maybe it's an issue with reinstalling the apps. Then when I called again...after 30sec-1 min...same tone again...then phone turned off and never turned on again...Battery was 100% charged.
I updated the correct firmware since I was already using insertcoin ICS ROM for a while before changing to ARHD 6.6.2
I am scared of installing a custom ROM now....I have rooted the phone again, S-off, Clockwork, superCID....but I am thinking maybe I should just wait for teh official update for ICS and leave it as that.
Can I just to OTA update when it comes out?

newr said:
Can I just to OTA update when it comes out?
Click to expand...
Click to collapse
Change your CID back to T-MOB010 and you can...
FWIW, what kernel were you running when it took a dump?

I didn't install any custom kernel...I just installed the firmware as suggested.. and also the radio file that ARHD page says we should flash for T-mobile phones....
then flash the ROM as usual. Everything worked...the phone died while running the ROM.
So I need to change CID again to do OTA update? It's ok to leave it rooted, Clockwork, and S-off? Maybe I shouldn't have changed to super CID then?

newr said:
I didn't install any custom kernel...I just installed the firmware as suggested.. and also the radio file that ARHD page says we should flash for T-mobile phones....
then flash the ROM as usual. Everything worked...the phone died while running the ROM.
So I need to change CID again to do OTA update? It's ok to leave it rooted, Clockwork, and S-off? Maybe I shouldn't have changed to super CID then?
Click to expand...
Click to collapse
You can leave it rooted and s-off (in fact you WANT to keep s-off), make sure your stock rom is un-modified, and you need to go back to stock recovery. If you leave superCID then it will not detect the update. It needs to refer to CID to find the correct update package for your device...

I haven't modify the Rom that's on here now. So stock recovery means removing clockwork ? And changing CID...is there a tutorial to do that?..

newr said:
I was running ARHD 6.6.2 Just flashed the ROM.. and seem to flash fine, able to boot up. Even reinstalled all the apps...then while calling...had this long tone from the phone...and phone was unresponsive...I pressed power button.. and it turned off.
The first time..it actually turned back on....so I thought maybe it's an issue with reinstalling the apps. Then when I called again...after 30sec-1 min...same tone again...then phone turned off and never turned on again...Battery was 100% charged.
I updated the correct firmware since I was already using insertcoin ICS ROM for a while before changing to ARHD 6.6.2
I am scared of installing a custom ROM now....I have rooted the phone again, S-off, Clockwork, superCID....but I am thinking maybe I should just wait for teh official update for ICS and leave it as that.
Can I just to OTA update when it comes out?
Click to expand...
Click to collapse
Did you try flashing the new 6.6.4 ARID? Came out on May 6th
Sent w/ HTC Sensation 4G (Z710a) XDA Premium

another one with the same problem :S

namila007 said:
another one with the same problem :S
Click to expand...
Click to collapse
But is it a HTC problem or a flashing custom stuff problem?
I don't know what I should do now...if I should just wait for ICS update...but now I'll have to remove superCID and somehow flash stock recovery or something

[Q] After Flashing JB Rom, Won't Boot

First: Thanks to this great forum of developers and users, I have learned a lot in a short period of time. The HTC One S is my first Android handset, and I love it. All the wonderful tutorials and threads you guys created made learning the basics of rooting/flashing easy.
This is my second HTC One S handset, the previous one died from hardware failure. The previous handset had HBoot 1.06, and so I was able to flash the TWRP recovery and use the Trickdroid 9.1.0 flawlessly. The problem comes with this new handset, and I am not sure exactly what it is to troubleshoot. The current HBoot on the phone is 1.14 (which means I can't flash radios, etc.). After unlocking the bootloader, I flashed the latest TWRP recovery (2.4.1.0). After factory resetting the phone and installing the Trickdroid 9.1.0, the phone won't boot. If I hold the power for 5-10 seconds, the keys flash, that's it. I am able to get into the bootloader using the power + volume down method, and then I have to recover my phone back to factory settings using the RUU avaliable online. I have tried redoing this process 2-3 times now, and everytime I flash the JB rom, the phone won't boot. I am not sure if having a HBoot 1.14 prevents me from upgrading from ICS --> JB, recovery, or anything else. As I said, my knowledge of Android is very limited as I am a new user. I really would like to use the JB rom that is cleaned and optimized. If anyone has any suggestions on what I can do, I would greatly appreciate it. Right now, I just did the perm root to be able to get rid of some of the bloat (T-Mobile comes with so much garbage!). Thank you so much, once again, and any troubleshooting help will be returned with big kiss! :angel:

bombina said:
First: Thanks to this great forum of developers and users, I have learned a lot in a short period of time. The HTC One S is my first Android handset, and I love it. All the wonderful tutorials and threads you guys created made learning the basics of rooting/flashing easy.
This is my second HTC One S handset, the previous one died from hardware failure. The previous handset had HBoot 1.06, and so I was able to flash the TWRP recovery and use the Trickdroid 9.1.0 flawlessly. The problem comes with this new handset, and I am not sure exactly what it is to troubleshoot. The current HBoot on the phone is 1.14 (which means I can't flash radios, etc.). After unlocking the bootloader, I flashed the latest TWRP recovery (2.4.1.0). After factory resetting the phone and installing the Trickdroid 9.1.0, the phone won't boot. If I hold the power for 5-10 seconds, the keys flash, that's it. I am able to get into the bootloader using the power + volume down method, and then I have to recover my phone back to factory settings using the RUU avaliable online. I have tried redoing this process 2-3 times now, and everytime I flash the JB rom, the phone won't boot. I am not sure if having a HBoot 1.14 prevents me from upgrading from ICS --> JB, recovery, or anything else. As I said, my knowledge of Android is very limited as I am a new user. I really would like to use the JB rom that is cleaned and optimized. If anyone has any suggestions on what I can do, I would greatly appreciate it. Right now, I just did the perm root to be able to get rid of some of the bloat (T-Mobile comes with so much garbage!). Thank you so much, once again, and any troubleshooting help will be returned with big kiss! :angel:
Click to expand...
Click to collapse
Did you flash the boot.img via fastboot after flashing the rom?

rustykwak said:
Did you flash the boot.img via fastboot after flashing the rom?
Click to expand...
Click to collapse
That seemed to be the problem this whole time! Argh! Thanks! In the previous phone, I always flashed it after rebooting via FlashGUI. I guess the only looming problem now is that the Wifi doesn't work on this Trickdroid ROM for my HBoot (1.14). Blah.

bombina said:
That seemed to be the problem this whole time! Argh! Thanks! In the previous phone, I always flashed it after rebooting via FlashGUI. I guess the only looming problem now is that the Wifi doesn't work on this Trickdroid ROM for my HBoot (1.14). Blah.
Click to expand...
Click to collapse
theres a thread in dev section wifi partions perhaps that will help you out!

rustykwak said:
theres a thread in dev section wifi partions perhaps that will help you out!
Click to expand...
Click to collapse
Unfortunatly on that hboot I dnt think we can
Sent from my HTC One S using xda app-developers app

siqbudz said:
Unfortunatly on that hboot I dnt think we can
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Yes, that is right. I think any HBoot higher than 1.09 (I am 1.14) will not be able to flash WiFi partitions. Any way we can make WiFi work on JB? Would upgrading the HBoot to 2.x fix this Wifi problem? I still don't know why it doesn't work though and not having Wifi is kind of a big deal.

Sensation WiFi and Bluetooth issue

Alright here's the issue...
Ok so my brother had my rooted HTC SENSATION S-ON with CM9, and he was longboarding and txting (bad combination...). As it results, obviously, he fell and desintegrated the screen, but the phone was fully functional before. Couple of months after the incident, before fixing it, i took it out of the drawer i had it put away and turned it on, and earlier that day i had found a very stable cm10.1 rom for it so i went ahead and installed it because wifi and bluetooth was functional on it. After i do so, i try to turn my wifi on in the innitial Google log on and on the screen it said "Turning WiFi on." and i waited about half an hour and nothing, so i skipped it. When i went into the settings app i tried turning bluetooth on and the switch went back to off instantly. And i went online and did research and saw a guy that just pulled the bluetooth and wifi connectors for the antenna up so they would actually work, and i tried it, but no luck... I also tried flashing the boot.img for the current rom, but also didnt work. So i thought it might have been the rom since it wasnt fully stable yet, so i did a full wipe and re-flashed the currnet rom and re-flashed the boot.img but no luck. So i downloaded a stable release of cm9 and did full wipe and installed the boot.img for that version of cm9, but yet again no luck... So i re-installed the cm10.1 Albinoman build and lived on 4G so far... i need help on re-enabling bluetooth and wifi....plz help im desperate
P.S. I think this might have to do with the incident of the screen, but i dont think its hardware related...anyways im going to have the screen replaced this monday, so wish me luck

Try formatting all the partitions except for SD card and then reflash the ROM.
Look here for general solutions: http://forum.xda-developers.com/showthread.php?t=2085025
Sent from my HTC Sensation

AndroidSupporter318 said:
Try formatting all the partitions except for SD card and then reflash the ROM.
Look here for general solutions: http://forum.xda-developers.com/showthread.php?t=2085025
Sent from my HTC Sensation
Click to expand...
Click to collapse
tried that already

Which recovery do you have? If you don't have 4EXT, you need to get flash it, otherwise, you need to s-off your phone
Sent from my HTC Sensation

AndroidSupporter318 said:
Which recovery do you have? If you don't have 4EXT, you need to get flash it, otherwise, you need to s-off your phone
Sent from my HTC Sensation
Click to expand...
Click to collapse
Yea i got 4EXT and i always use smartflash when flashing anything at all

Hmmm... what is your radio version and hboot version number? Try to obtain s-off, and then flash firmware 3.33(i think it has a different radio that might fix your problem)
Also, make sure that you s-off before flashing 3.33 from bootloader.
Here's s-off guide: http://forum.xda-developers.com/showthread.php?p=25202517
Here's firmware 3.33: http://forum.xda-developers.com/showthread.php?t=1459767
Sent from my HTC Sensation

AndroidSupporter318 said:
Hmmm... what is your radio version and hboot version number? Try to obtain s-off, and then flash firmware 3.33(i think it has a different radio that might fix your problem)
Also, make sure that you s-off before flashing 3.33 from bootloader.
Here's s-off guide: http://forum.xda-developers.com/showthread.php?p=25202517
Here's firmware 3.33: http://forum.xda-developers.com/showthread.php?t=1459767
Sent from my HTC Sensation
Click to expand...
Click to collapse
I cant read the version due to the dead chunks on the screen but i should have it fixed in a couple of days. I preffer not trying to s-off since i find that too complicated, but in case i had to do so, would i have to do a full wipe?

No, a full wipe is not required for s-off.
You can go to "about phone" in the settings to find out about your radio version. It should be the baseband numbers/letters.
Also, which kernel do you have? Flashing another kernel might solve the problem.
Try flashing this kernel: http://forum.xda-developers.com/showthread.php?p=36216263
Or this one: http://forum.xda-developers.com/showthread.php?p=16608447
Sent from my HTC Sensation

i took it to get fixed and they fixed the screen and tried to fix this issue but couldnt and told me
it was a motherboard issue and that it was broken, but i highly doubt it because everything else works
perfectly fine, although i tried the kernel (Sultan) and it didnt work...still got that same issue

Well, did you get s-off on your phone? I think the only way is to fix your radio (flash 3.33) but you need s-off for that... Other than that, I have no idea.
BTW, did you try stock ICS before? If yes, how did it go?
Here's some quick fixes to WiFi: http://forum.xda-developers.com/showthread.php?t=1469428
Sent from my HTC Sensation

dosnoventa said:
i took it to get fixed and they fixed the screen and tried to fix this issue but couldnt and told me
it was a motherboard issue and that it was broken, but i highly doubt it because everything else works
perfectly fine, although i tried the kernel (Sultan) and it didnt work...still got that same issue
Click to expand...
Click to collapse
hi, didn't see anywhere that you mention your android version, if it is 4.2.X, don't try to turn the WiFi on, rather go to advanced WiFi settings and select a region code in there, whatever you liked. but in case it is 4.1.X then Install WiFix Manager while WiFi is off, and reboot your phone.
good luck. :good:

AndroidSupporter318 said:
Well, did you get s-off on your phone? I think the only way is to fix your radio (flash 3.33) but you need s-off for that... Other than that, I have no idea.
BTW, did you try stock ICS before? If yes, how did it go?
Here's some quick fixes to WiFi: http://forum.xda-developers.com/showthread.php?t=1469428
Sent from my HTC Sensation
Click to expand...
Click to collapse
as a matter of fact i did try the stock ics and it had the same issue, unafortunately i havent s-off yet, but im not quite sure i want to do that

A friend of mine haf the same problem about a year back. Tried softwarefix but no luck. Restocked it and got the board replaced by htc.
Sent from my GT-N7105 using xda app-developers app

AndroidSupporter318 said:
Well, did you get s-off on your phone? I think the only way is to fix your radio (flash 3.33) but you need s-off for that... Other than that, I have no idea.
BTW, did you try stock ICS before? If yes, how did it go?
Here's some quick fixes to WiFi: http://forum.xda-developers.com/showthread.php?t=1469428
Sent from my HTC Sensation
Click to expand...
Click to collapse
I did try stock ics, even resetting the phone to stock but no luck. Though i might not want to s-off, finding
that the process is pretty complicated, i yet do not have the knowledge to understand.

help
Hey guys I need help with my galaxy note 2 t0ltetmo, if anyone is interested and is willing to help me with this one I'd appreciate it, cause no one seems to help me. Please help if you can, I'm in desperate need here. Anyways here's the link to the forum: http:// http://forum.xda-developers.com/showthread.php?p=48442689&nocache=1

[Q] No OS Installed - 3.18 Unlocked S=On

Followed the steps in Hassoon's toolkit, installed recovery, sideloaded CM, and now I have no OS. I can still access fastboot and recovery, see attached image for more info. Any more information needed, please let me know. This is pretty frustrating, no wonder I like Nexus devices.
(sorry for double posting, I also put this in Hassoon's thread, but felt it'd be more appropriate to post here)

first man... you'll only be able to use sense roms most likely, as the newer aosp roms dont mix with the upgraded touchscreen on the 3.18 firmware. so you can head to the original dev section to find the "downgrade touchscreen" thread to use aosp...
second, you have to fastboot flash the boot.img of every rom because the newer hboots dont allow it. easy solution to that is to go to original dev section and follow the s-off thread. if you can s-off you can say bye bye to fastboot for the most part

Also, you need to S-OFF to downgrade touchscreen firmware.
But yeah, if you can get into recovery just wipe everything and flash a rom.. (has to be sense until you s-off and downgrade touchscreen firmware)

exad said:
Also, you need to S-OFF to downgrade touchscreen firmware.
But yeah, if you can get into recovery just wipe everything and flash a rom.. (has to be sense until you s-off and downgrade touchscreen firmware)
Click to expand...
Click to collapse
Never thought I had to pull the boot image out, flash that through fastboot, THEN install the OS. Thanks for the help guys, I tested it out with the copy of CM I had (unofficial port on the threads) and sure enough, it booted up fine. Of course, as stated previously, I can't click anything b/c of the upgraded touchscreen, so I'm omw to flashing a sense rom and getting s-off and a downgraded touch screen. Thanks for the help guys!

Dolfan058 said:
Never thought I had to pull the boot image out, flash that through fastboot, THEN install the OS. Thanks for the help guys, I tested it out with the copy of CM I had (unofficial port on the threads) and sure enough, it booted up fine. Of course, as stated previously, I can't click anything b/c of the upgraded touchscreen, so I'm omw to flashing a sense rom and getting s-off and a downgraded touch screen. Thanks for the help guys!
Click to expand...
Click to collapse
Yea man its a pain to get everything going. But once you s-off, downgrade etc this phone really flies on aosp. There's also an (optional) thread in development section to rid the splash screen of the red text. Its a simple 3 step process that should only take 20 seconds. After that you're golden
Sent from my One X using Tapatalk 2

InflatedTitan said:
Yea man its a pain to get everything going. But once you s-off, downgrade etc this phone really flies on aosp. There's also an (optional) thread in development section to rid the splash screen of the red text. Its a simple 3 step process that should only take 20 seconds. After that you're golden
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...

Dolfan058 said:
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Click to expand...
Click to collapse
are you using a sense rom or aosp?
you need to be on a sense rom since your hboot is 2.14 because aosp requires you change a setting to allow you to soff which you cant since the touchscreen doesnt work.
if you are already on a sense rom. simulate a battery pull by pressing and holding power on your phone till the capacative buttons blink a bunch of times and then it shuts off. then try again.

Dolfan058 said:
I'll bet. Getting S-off to work is killing me though. Keep running into the 99 unknown error while flashing the RUU file. I've done complete wipes, made sure i have superCID, and still no luck. So close and yet so far...
Click to expand...
Click to collapse
I feel bad, I see all these people having trouble getting s-off to work, and I did it today without any hassles at all.
Sent from my Evita using XDA Premium

exad said:
are you using a sense rom or aosp?
you need to be on a sense rom since your hboot is 2.14 because aosp requires you change a setting to allow you to soff which you cant since the touchscreen doesnt work.
if you are already on a sense rom. simulate a battery pull by pressing and holding power on your phone till the capacative buttons blink a bunch of times and then it shuts off. then try again.
Click to expand...
Click to collapse
Definitely a sense rom (http://forum.xda-developers.com/showthread.php?t=1868236), still trying to work through it. It's so annoying, I'm dying to get the unofficial CM build on here already.

Dolfan058 said:
Definitely a sense rom (http://forum.xda-developers.com/showthread.php?t=1868236), still trying to work through it. It's so annoying, I'm dying to get the unofficial CM build on here already.
Click to expand...
Click to collapse
if a simulated battery pull isnt working for you, you can paste your cmd prompt window in here and i can check if anything weird is going on.
usually it should work by the third try or so if not after the first simulated battery pull.