****jb ruu 3.15.651.16 warning****

[rollerpig]

It has come to a lot of peoples furious attention that there is an issue with the latest RUU from HTC. I firsthand had to deal with it an it is documented in this thread http://forum.xda-developers.com/showthread.php?t=2074643 in which i attempted to restore my htcdev unlocked phone back to stock.

THE ISSUE
The problem is the ruu is updating hboot and seemingly nothing else. Radios, recovery, rom, etc all have remained the same after running the ruu. Attempts at re running the ruu do nothing and various ways of flashing/applying the ruu are ineffective. This creates a stable but malfunctioning phone with mismatched hboot, radios, rom, and seems unable to take you back to fully stock.

Pre-RUU:
s-on
hboot: 1.19
radio: 1.05.11.0606
rom: stock rooted jb with superuser

Post-RUU: (after multiple flashings/applications)
hboot: 2.09
radio: 1.05.11.0606
rom: stock rooted jb with superuser (i'm assuming that this should have been completely stock instead its the same rom i had previous to ruu application)

In the mean time, I've been running the latest stock jb rom and its stable enough for a functioning phone but things like cellular data (streaming music from google music doesn't work or sending sexy pics to the ladies on snap chat) and lte is completely absent. If you experience the same issue post in here with what happened, solutions, fixes, etc.

GOING BACK TO STOCK
If you need to get back to stock or semi bricked your phone use the ruu for your current software not the latest (for example if your hboot is 1.19 use the ruu with hboot 1.19 not the jb ruu with 2.09 hboot)

For now it seems the best thing to do is aware htc of the problem, wait for a new ota update/ruu fix, and/or wait for new s-off method for 2.09,
tankerevo has been working on various attempts/fixes and i've forwarded this thread along with some other information to htc.

RESPONSE FROM HTC

Dear rollerpig,

Thank you for contacting the HTC Technical Support Center in regards to your issue suggestion.

We are glad to know there are customers like you committed with our brand to improve our service and customer satisfaction. We understand there could be a lot of users and fans waiting for a fix on this RUU. We think it is amazing to have a good support in our users to enhance our products and releases. Right now we will share this concern with the Develop Team to look forward on a solution. We expect this issue will be fixed as soon as possible.

Rollerpig, we want to thank you once again for working with us, and for caring about our brand.

If you require further assistance in the near future please contact us through http://www.htc.com/us/support/email-support or call us at +1-866-449-8358 from 6AM to 1AM EST, 7 days a week.

Have a nice day,

Let me know if I have successfully answered your question, please click here to complete this.

To send a reply to this message, please click here.

Sincerely,

Julian

HTC

Want to see what others are saying? Have a question to ask other HTC fans?

Become a fan of HTC facebook.com/htc
Follow us on Twitter twitter.com/htc
Subscribe to our YouTube Channel youtube.com/htc

Explore our development resources developer.htc.com

Please visit us at htc.com if you have any questions or need further assistance.

THE FIX
Here's a possible fix complements of user Fuses. I have not tried this yet because i'm on vacation but it looks very promising and most likely works. http://forum.xda-developers.com/showthread.php?t=2097150

Fix
- Download JB OTA firmware from http://unlimited.io/jewel.htm
- Download fastboot executable (google)
- Put all files in one directory
- Reboot phone into fastboot mode
- Make sure that bootloader is Locked or Relocked. If bootloader is Unlocked, relock it with command fastboot oem lock
- Enter commands

Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip jewel_jb_ota_firmware.zip
NOTE:
If you see FAILED (remote: 90 hboot pre-update! please flush image again immediately) text after running fastboot flash zip command you have to run fastboot flash zip command again.

After this flash stock RUU again.

Permanent fix
- S-OFF your phone. With S-OFF phone you can always flash decrypted, unsigned and/or older RUU and get phone working again easily.

 

[tankerkevo]

Obviously, depending on the firmware version you are frozen at there will likely be variance in stability and function between ROMs and other users with the issue stuck at a different firmware version.

For me the last ICS stock ROM is working the best including LTE. But WiFi, Cell, and Data do restart rather incessantly.

MeanBean 2.0 works alright considering... But LTE doesn't work at all and the radios get very weak signals to the point that I start to enter roaming often.

 

[IAmSixNine]

It might help to post before and after info of the radio versions, hboot, pri, all that stuff so if someone were to have used the RUU and it worked they can compare what the old stuff is to the new stuff.

 

[rollerpig]

does gps work well on the ics stock?

 

[Papa Smurf151]

sickied for a little while until issue is resolved

 

[Evolutionmods]

sickied for a little while until issue is resolved

good deal... And also , Thanks OP for the heads up

 

[emtchrisbishop]

I've got my lte back, but had to nandroid back to superlte. I went to ##3282# and set profile to 1, and changed scan timer to 2 and max timer 30. It has been the longest I've had constant lte in a month.

Sent from my EVO using Tapatalk 2

 

[buggsbuny]

Mine was hosed too. If I ran the 2.13 RUU, it said you have a 2.13 image, would you like to update it to 2.13. If I ran the 3.15 RUU, it would say you have a 3.15 image on your phone, would you like to update it to 3.15?

Needless to say, none of that worked. I even tried the P75 image of JB direct from Sprint through recovery. No workie. I gave up and took it to Sprint. Explained that after RUU just aint going to work and this phone is stuck in ICS/JB hybrid limbo.

Sprint replaced the phone and I am now good to go. If you want to wait for a hack fix, then wait. Otherwise, you can try getting Sprint to replace it with a new one.

 

[IAmSixNine]

So back to my original question, can someone post what the 3.15.651.16 official numbers should be.
PRI, Radio, All those magical numbers were talking about..
Id like to check mine and see. I do remember downloading the RUU and installing it..

 

[Sloth]

So back to my original question, can someone post what the 3.15.651.16 official numbers should be.
PRI, Radio, All those magical numbers were talking about..
Id like to check mine and see. I do remember downloading the RUU and installing it..

PRI - 2.87_003
Baseband - 1.12.11.1119

 

[IAmSixNine]

PRI - 2.87_003
Baseband - 1.12.11.1119

OK those numbers match my device so i guess im OK..

 

[IAmSixNine]

The file i used to upgrade was downloaded 12/24/2012
RUU_JEWEL_CL_BJ_45_S_SPRINT_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed.exe
This is the RUU i used on mine because i was impatient and didnt want to wait for the OTA to hit my phone.
From what i can tell it did the upgrade just fine.

 

[cloves]

The file i used to upgrade was downloaded 12/24/2012
RUU_JEWEL_CL_BJ_45_S_SPRINT_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed.exe
This is the RUU i used on mine because i was impatient and didnt want to wait for the OTA to hit my phone.
From what i can tell it did the upgrade just fine.

IAmSixNine, could you give us a bit more detail on your setup. OS (windows etc), where you downloaded the RUU, and what software version were you running before you upgraded.

 

[IAmSixNine]

Windows 7 home, i was on the latest stock, unlocked device prior to that update coming out.
Where did i DL it at, http://www.htcruu.com/?dir=Jewel

 

[Fuses]

Try this one, please report on that thread if fix works for you also
http://forum.xda-developers.com/showthread.php?t=2097150

 

[MerkoPCS]

I installed the 3.15 RUU from CM10 to try to bring my phone back to stock.

The RUU took, but now my phone is incredibly slow, freezes, screen goes unresponsive, camera wont work...All kinds of issues]

I even reapplied the same RUU from the stock 3.15 ROM.

Are my issues symptoms of this problem outlined in this thread?

 

[tankerkevo]

Possibly. What's you baseband version?

If its less than 1.12 then yes.

---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------

Also if it is less then fllow fuses thread link above.

 

[frey482]

update baseband

is there a way to update the baseband version mine is less then 1.12, I am s-off and am running the latest meanrom because meanbean was super unstable for me.

do I need to download the latest ruu to update it, then flash it with the latest meanbean?

 

[Sloth]

is there a way to update the baseband version mine is less then 1.12, I am s-off and am running the latest meanrom because meanbean was super unstable for me.

do I need to download the latest ruu to update it, then flash it with the latest meanbean?

Here is the full firmware minus hboot-recovery-kernel
http://d-h.st/4Y0
MD5 2a9b2c8f6a969fe0163df5738e8f4b5

Rename it PJ75IMG and place it on your ext sdcard/boot into bootloader/ it should ask you if you want to update follow the on screen instructions once you are rebooted remove the file from your sdcard if you don't you will be asked to update every time you enter bootloader

 

[beamer1341]

I rooted my phone this morning, and attempted to install cm10. the screen became inop. so I tried a recovery and it put it into boot loop. I have relocked the phone and tried some RUUs but all come back with bootloader, or signature errors, I have tried this method as well to no avail all i end up getting is this:
C:\Users\Downloads>fastboot flash zip RUU.zip
sending 'zip' (659905 KB)...
OKAY [ 27.926s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 106.089s
Boot Screen:
*tampered
*relocked
s on
hboot 2.09
radio 1.12.11.1210
opendsp-v31.1.45.0815
eMMC-boot


Any help would be appreciated