Related
The main question is the title - Should you S-off before or after the OTA?
I have seen people around the forums (via a few searches) say that it is likely a good idea to perform S-off before OTA because we didn't know for sure if the OTA would close the S-off exploit. Now that the OTA is a known quantity, is that still the best route?
My device is:
Stock rom and firmware (2.01.605.11)
Unlocked
AmonRA 3.15 recovery
Rooted
I'm a little nervous about doing S-off, but I figure it will be really handy to have it once its done, and I understand it really is no big deal. My end goal is to run the Venom rom and then move to AOKP/CM9 once they have most of the bugs worked out. Would my best course of action be to S-Off, run the firmware updater, reinstall recovery (probably TWRP, seems like that is the most popular one at the moment), then flash my rom of choice? Will I need to re-root if I switch to a different recovery?
UPDATE:
S-off is done and was no big deal, I got it on my third try. I selected to not install the jb_hboot during the process, since I'm doing RUU next.
The 3.14.605.12 RUU (from android police) was as simple as could be, I renamed the file to PH98IMG.zip and dumped it into my sd card, once I rebooted into the bootloader it was automatic from there
I got stuck on the "flash juopunut Bear hboot" part, I am using Hasoon2000's HTC Rezound ALL-In-One Kit and S-Off Toolkit. I thought I could just flash the hboot from this and be done... I learned that unless you have the jb_hboot (the latest vigor hboot from unlimited.io) installed you can't use ADB commands (which the toolkits use). The solution was very simple. I just renamed the jb_hboot to PH98IMG.zip, rebooted into the bootloader and it was installed.
TWRP v. 2.20 flashed, for some reason my phone doesn't charge while plugged in and booted into this recovery. I guess I need to make sure I have a nice charge if I want to do anything major.
Installed ViperRez rom 1.03, now I'm toying around with it
Originally Posted by AshtonTS
Originally Posted by YTHero
My device is:
Stock rom and firmware (2.01.605.11)
Unlocked
AmonRA 3.15 recovery
Rooted
I want to run a custom (like ViperRez or CM9) ICS rom with the OTA (3.14.605.12) updated firmware.
So my process will be:
S-Off -> flash Hboot/radio/firmware files from 3.14.605.12 -> flash juopunut Bear hboot -> flash TWRP -> Flash ICS rom
Is my plan correct in that I should flash juopunutBear hboot after I flash the Hboot/radio/firmware files from 3.14.605.12? If so why?
Is there anything else that I should do in between these steps that I haven't identified? Am I taking any unnecessary risks by doing it this way?
Click to expand...
Click to collapse
Yeah, flash the RUU, then the JBear hboot, then TWRP/Amon Ra, then a Rom
Click to expand...
Click to collapse
I would do it beforehand. Once you are s-off, you can flash the latest firmware without installing the whole RUU also.
But it limits from getting the actual ota which I love to see
Sent from my ADR6425LVW using xda app-developers app
I would do it before and then after you S-Off run through this PH98IMG RUU. From talks, this is the OTA.
http://forum.xda-developers.com/showthread.php?t=1810931
Then flash the patched 2.25.2525 JB hboot from http://unlimited.io/hboot-downloads/
EDIT:
Alternatively you could S-Off, flash latest radios and patched hboot, then flash a rom of your choosing based on 605.10 or 605.12.
I'm still going to wait to see if we can get s-off on ics before updating today as I don't have the wire to currently do the exploit.
Sent from my ADR6425LVW using xda app-developers app
All I am saying is this. Why wait for the OTA when their are already roms based off 605.10, barely anything changed from it to 605.12. Also, S-Off will stick as long as you make it stick.
why wait for the ota when the ota was leaked?
YTHero said:
The main question is the title - Should you S-off before or after the OTA?
I have seen people around the forums (via a few searches) say that it is likely a good idea to perform S-off before OTA because we didn't know for sure if the OTA would close the S-off exploit. Now that the OTA is a known quantity, is that still the best route?
My device is:
Stock rom and firmware (2.01.605.11)
Unlocked
AmonRA 3.15 recovery
Rooted
I'm a little nervous about doing S-off, but I figure it will be really handy to have it once its done, and I understand it really is no big deal. My end goal is to run the Venom rom and then move to AOKP/CM9 once they have most of the bugs worked out. Would my best course of action be to S-Off, run the firmware updater, reinstall recovery (probably TWRP, seems like that is the most popular one at the moment), then flash my rom of choice? Will I need to re-root if I switch to a different recovery?
Click to expand...
Click to collapse
You are on Gingerbread firmware, that's the first thing to recognize. There's lots of development tools that were designed AFTER the Gingerbread firmware (2.xx is GB; 3.xx is ICS). In fact Amon Ra 3.15 was the version done after the ICS leak (because mount points were changed).
So you can (and probably should) do the S-OFF using the GB version over at Juopunut's site and then either wait for the ICS OTA to come to your phone or flash it in bootloader as a PH98IMG.ZIP (the RUU is available via Android Police, 3.14.605.12 is the "official" ICS, and I'm pretty sure its here on XDA but I don't remember the thread.)
If you don't want to wait for the OTA, it doesn't matter whether you are S-ON or S-OFF, you'll still have to flash the RUU in hboot. Both will completely wipe your phone, and the S-OFF process will wipe your CARD so use a different card before you do it!
Finally, to reiterate what's all over by now: the "official" update, 3.14.605.12 is only marginally different than the unofficial leak that's been out since May, 3.14.605.10, and the radios, kernel and hboot are all the same.
hgoldner said:
So you can (and probably should) do the S-OFF using the GB version over at Juopunut's site and then either wait for the ICS OTA to come to your phone or flash it in bootloader as a PH98IMG.ZIP (the RUU is available via Android Police, 3.14.605.12 is the "official" ICS, and I'm pretty sure its here on XDA but I don't remember the thread.)
If you don't want to wait for the OTA, it doesn't matter whether you are S-ON or S-OFF, you'll still have to flash the RUU in hboot. Both will completely wipe your phone, and the S-OFF process will wipe your CARD so use a different card before you do it!
Click to expand...
Click to collapse
I recieved the OTA today from Verizon, but deferred to take until I figured out what I want to do. If I understand what you are saying:
S-Off -> OTA -> install TWRP -> then Flash ViperRez or whatever rom
Taking the OTA seems like the easiest and most straight forward way of upgrading to ICS radios/hboot. Will I need to do anything else before or following the OTA? I feel like somewhere I read that I will need to patch the hboot because I will be S-off.
YTHero said:
I recieved the OTA today from Verizon, but deferred to take until I figured out what I want to do. If I understand what you are saying:
S-Off -> OTA -> install TWRP -> then Flash ViperRez or whatever rom
Taking the OTA seems like the easiest and most straight forward way of upgrading to ICS radios/hboot. Will I need to do anything else before or following the OTA? I feel like somewhere I read that I will need to patch the hboot because I will be S-off.
Click to expand...
Click to collapse
After you s off, flash juopunutBears hboot it should be on his website
Sent from my ADR6425LVW using xda app-developers app
Squirrel1620 said:
After you s off, flash juopunutBears hboot it should be on his website
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
I'm trying to understand this post
http://forum.xda-developers.com/showpost.php?p=29715514&postcount=51
and this thread
http://forum.xda-developers.com/showthread.php?t=1614366
superchilpil said:
New firmware patch huh?
This is simply for those upgrading to ICS firmware on a GB rom Or and ICS rom that had the gingerbread patch flashed over it
Whats the difference between the stock Hboots and the JB/ENG Hboots?
Simply, These Hboots have fastboot commands enabled WITHOUT unlocking the bootloader
I suggest if you use fastboot alot to use these hboots
Click to expand...
Click to collapse
I'm just trying to figure out if I will have to reflash the juopunutBears hboot after I flash the Hboot/radio/firmware files from 3.14.605.12
So will it be:
S-Off -> Hboot/radio/firmware files from 3.14.605.12 -> juopunut Bear hboot ->install TWRP -> then Flash ViperRez or whatever ICS rom
YTHero said:
So will it be:
S-Off -> Hboot/radio/firmware files from 3.14.605.12 -> juopunut Bear hboot ->install TWRP -> then Flash ViperRez or whatever ICS rom
Click to expand...
Click to collapse
You got it right on.
Sent from my ADR6425LVW using xda app-developers app
i've been wondering if anyone else has been having any issues with mean rom ics, i've flashed it twice, and even done a full wipe and everything. but it seems every time i restart (or the phone powers down) i go through about 6 - 10 crashes before it can run stable enough for me to use it at all. has anyone else had this issue or have this issue and can shed any light on what could be causing it?
Strange. Are you s-on or s-off?
Read, Search, Read again, ... Then Ask with Tapatalk 2
Im s-off via Juopunutbear. My phone came with bootloader 1.50 but I updated for ics using what was posted Here, so I could retain s-off
I was having some odd things happen when I first moved to MeanROM 2.6 as well so I flashed the 2.89 RUU when it became available to make sure that the software and firmware were completely in sync. That's pretty easy to do if you are S-OFF since all you have to do is connect your phone to a Windows PC and run the RUU.exe, then flash a custom recovery and optionally a different bootloader.
Things seem to be a little smoother for me after flashing the 2.89 RUU as a base.
ramjet73
ramjet73 said:
I was having some odd things happen when I first moved to MeanROM 2.6 as well so I flashed the 2.89 RUU when it became available to make sure that the software and firmware were completely in sync. That's pretty easy to do if you are S-OFF since all you have to do is connect your phone to a Windows PC and run the RUU.exe, then flash a custom recovery and optionally a different bootloader.
Things seem to be a little smoother for me after flashing the 2.89 RUU as a base.
ramjet73
Click to expand...
Click to collapse
but isn't flashing via bootloader the firmware bits doing (the long-ish way) the same thing as what the RUU would do? I'm still on the stock HTC bootloader for 1.58 because i was updated to it from the firmware bits, but if the RUU does something extra then maybe i would benefit from flashing with it. but i mean i also have MIUI 2.8.17 and i installed it (after i was able to use my phone) through boot manager a few weeks after installing MeanROM and booting to it yields me no issues of crashing or anything. do note its based off (supposedly) the GSM port for the E3D as well as files from the sprint/htc ICS release
AlexxSeven said:
but isn't flashing via bootloader the firmware bits doing (the long-ish way) the same thing as what the RUU would do? I'm still on the stock HTC bootloader for 1.58 because i was updated to it from the firmware bits, but if the RUU does something extra then maybe i would benefit from flashing with it. but i mean i also have MIUI 2.8.17 and i installed it (after i was able to use my phone) through boot manager a few weeks after installing MeanROM and booting to it yields me no issues of crashing or anything. do note its based off (supposedly) the GSM port for the E3D as well as files from the sprint/htc ICS release
Click to expand...
Click to collapse
There's no guaranty that flashing the RUU will fix anything but it did seem to help on my phone. The RUU flashes both the stock ROM and all the firmware, including the bootloader, so it makes your phone 100% stock except for the S-ON/S-OFF radio security and bootloader locked/unlocked status. It won't change either of those, but you must have your bootloader locked (or relocked) to run the RUU if S-ON.
After running the RUU.exe you can flash a custom recovery and bootloader if you want. It should be the same as returning to stock and taking the OTA update, but flashing the RUU.exe is faster and easier.
ramjet73
Hboot 1.5 s-on and I'm running meanrom ICS 2.6 .
I did the HTC unlock. Then installed Su zip from this site. Then I installed 4ext and rebooted into recovery...flashed the meanrom zip (it flashed the kernel that comes w the Rom ) and that was it. Now I'm on sw 2.89 build w the 3.0.16 kernel and like I said still s off and hboot 1.5
If anyone knows any where to get a kernel to overclock please let me know
Sent from my PG86100 using xda app-developers app
ramjet73 said:
There's no guaranty that flashing the RUU will fix anything but it did seem to help on my phone. The RUU flashes both the stock ROM and all the firmware, including the bootloader, so it makes your phone 100% stock except for the S-ON/S-OFF radio security and bootloader locked/unlocked status. It won't change either of those, but you must have your bootloader locked (or relocked) to run the RUU if S-ON.
After running the RUU.exe you can flash a custom recovery and bootloader if you want. It should be the same as returning to stock and taking the OTA update, but flashing the RUU.exe is faster and easier.
ramjet73
Click to expand...
Click to collapse
i actually decided to give it a try after making a nand backup ofc, and still had the same issues :s after re-flashing from my backup though it seems to boot fairly stable now. even between switching roms im not sure exactly why but could it have been an issue with anything that is permanent between any rom?
I recently re-locked my bootloader (never had s-off) and flashed the appropriate RUU to restore my device back to complete stock, however now it won't pull the ICS update and I'm having a hard time figuring out what issue is. Is there any chance that someone can help me get this working? When I check the status of the upgrade server it's completely blank except for the source: Verizon Wireless and code: 0 any idea?
Flash the GB RUU and it will update to ICS after the install. If you flashed the ICS leaks then you need to S off so that you can get back to GB. Getting S off is very easy. I would recommend it so you can flash all the new roms.
Sent from my ADR6425LVW using Tapatalk 2
DownRiver_Droid said:
Flash the GB RUU and it will update to ICS after the install. If you flashed the ICS leaks then you need to S off so that you can get back to GB. Getting S off is very easy. I would recommend it so you can flash all the new roms.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Hello, I have a stock Rooted Rezound runniong 2.3.4 android. I got prompted to install ICS, and i delayed it, and it installed anyway and my phone would not get past the HTC screen. I have cwm installed, and i reverted back to the day i rooted.
How do i get the phone back to "stock" so i can get the OTA properly. is there a thread i can follow? i am s-on i think. (how do i tell, i thought i was s-off, see below for the bootloader screen)
when o go to the boot loader it says
*** UNLOCKED *** (in pink)
VIGOR PVT SHIPS S-ON RL
HBOOT-2.11.0000
eMMC-boot
You are S-On.
Download the GB RUU.
Relock the bootloader.
Run the GB RUU.
Let the OTA install.
EmerikL said:
You are S-On.
Download the GB RUU.
Relock the bootloader.
Run the GB RUU.
Let the OTA install.
Click to expand...
Click to collapse
thanks, where do i find the GB RUU? Theres so much stuff on these forums sometimes its hard to find it. I found this unroot thread. but the links to download seem to be down
http://forum.xda-developers.com/showthread.php?t=1472606
DownRiver_Droid said:
Flash the GB RUU and it will update to ICS after the install. If you flashed the ICS leaks then you need to S off so that you can get back to GB. Getting S off is very easy. I would recommend it so you can flash all the new roms.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
That's what I did, it won't pull any update.
john10101 said:
thanks, where do i find the GB RUU? Theres so much stuff on these forums sometimes its hard to find it. I found this unroot thread. but the links to download seem to be down
http://forum.xda-developers.com/showthread.php?t=1472606
Click to expand...
Click to collapse
Check Shipped-roms.com.
Sent from my ADR6425LVW using xda app-developers app
I dont see the rezound listed on that site.
[RUU] HTC Rezound RUU RoundUp
Includes most RUU's release for the Rezound, except the latest 4.3.605.2 version. Their server is a little slow, but it always seems to work.
acejavelin said:
[RUU] HTC Rezound RUU RoundUp
Includes most RUU's release for the Rezound, except the latest 4.3.605.2 version. Their server is a little slow, but it always seems to work.
Click to expand...
Click to collapse
So i think i figured out the shipped roms site. the Rezound is under vigor.
so which one do i flash theres 3 different roms.
how do i figure out which one i am on
1.00.605.3
1.02.605.6
2.01.605.11
also is there another link for the fastboot tool? so i can lock it again? Will these replace cwm on my device?
You have boot 2.11 so you need to get the 2.01 ruu. And yes it will return it too 100 percent stock including the recovery. You want to keep kt that way until after you update with the ota.
Sent from my GT-N8013 using xda premium
DigitalDementia said:
I recently re-locked my bootloader (never had s-off) and flashed the appropriate RUU to restore my device back to complete stock, however now it won't pull the ICS update and I'm having a hard time figuring out what issue is. Is there any chance that someone can help me get this working? When I check the status of the upgrade server it's completely blank except for the source: Verizon Wireless and code: 0 any idea?
Click to expand...
Click to collapse
What happens when you check for a new update? Does it sit there for a couple seconds and then just disappear and not say anything? Or does it at least tell you that "there is no update available"? I had this same issue on the GB update: http://forum.xda-developers.com/showthread.php?t=1469246
basically what I had to do what activate my SIM on another rezound and then put it back into my original and it started pulling the updates.
http://forum.xda-developers.com/showpost.php?p=22502775&postcount=22
murhaava1 said:
What happens when you check for a new update? Does it sit there for a couple seconds and then just disappear and not say anything? Or does it at least tell you that "there is no update available"? I had this same issue on the GB update: http://forum.xda-developers.com/showthread.php?t=1469246
basically what I had to do what activate my SIM on another rezound and then put it back into my original and it started pulling the updates.
http://forum.xda-developers.com/showpost.php?p=22502775&postcount=22
Click to expand...
Click to collapse
Great. so the thread i found has the fast boot tool listed on it for relocking the boot loader (which from what i understand i have to do first) the link to download the tool is down. does anyone have an alternate download location for this tool?
I found the tool in another thread. http://forum.xda-developers.com/showpost.php?p=20780879&postcount=1
I was able to lock the device. Push the RUU 2.01 (like recommended) I then pulled down two OTA updates. One "prepared for ICS" the second installed ICS
thanks for your help.
OK so I've tried googling and all that but this problem doesn't seem to be as common as the mainver is older issue.
Background:
Just sold the phone on swappa but I need to return to stock before I send it, hopefully tomorrow. I was s on running neo 1.7 before I got into this mess.
Issue:
I booted into recovery and did a factory reset. I then booted into hboot and did a factory reset there also. I think I then selected the wipe internal storage option. I then proceeded to relock the bootloader which I believe was successful since it says relocked now.
I have downloaded and tried flashing 3 different ICS RUUs by renaming them to the appropriate phxxx name and flashing them in hboot. It goes thru the process a little ways and then all of a sudden I get the "hboot is older" error and "update failed" message. My Hboot version is showing 2.27 which i believe is the newest one. I can't do anything and can't find a solution. I really need to figure out how to fix this asap so I can get the buyer his phone. All help is greatly appreciated!
It is impossible to downgrade HBoot without S-Off, so you will only be able to run an RUU with HBoot version 2.27 or higher (I believe that's either the ICS OTA or the Global leak - correct me if I'm wrong).
To get completely stock, i.e., stock firmware and Locked (as opposed to Relocked), you will need to get S-Off, then flash whatever RUU you want, then get S-On again.
However, just flashing any RUU - either the ICS OTA or the Global leak, and staying Relocked should be fine - many people receive used phones with custom ROMs and all, so an RUU would be a big step up from that (in terms of being as stock as possible).
EDIT: as LOBBS said (below), you will need to run the Global Leak RUU. That will get you on the latest leaked firmware / radios, which is probably the best anyway if you are selling the phone to the 'average', uninformed user (or to the informed user, for that matter). You will have Relocked bootloader.
Alternatively, you could get S-Off and then get on stock firmware / radios, Locked bootloader, and back to S-On, but I assume you won't want to bother to do all that just to sell the phone.
Hboot 2.27 is the global leak RUU 4.03.605.
Sent from my ADR6425LVW using xda app-developers app
Thanks fellas. I will try that one. I thought I had already but maybe I haven't. Let ya know what happens!
I flashed the global leak and all went well. Thanks for the quick help!
I tried searching for this answer before I posted this but I was not successful at finding it. So.....
Is there anything that cannot be updated by the ROMs? Are there items that can only be updated by taking the latest OTA update? I am trying to figure out if I need to take this latest update to get the latest firmware, kernel, etc.
I am OK with waiting for the ROM updates to come out if they will update everything, too. If they can't, I might as well get these OTA updates to see if they fix some of my problems.
Thanks for the help.
badtlc said:
I tried searching for this answer before I posted this but I was not successful at finding it. So.....
Is there anything that cannot be updated by the ROMs? Are there items that can only be updated by taking the latest OTA update? I am trying to figure out if I need to take this latest update to get the latest firmware, kernel, etc.
I am OK with waiting for the ROM updates to come out if they will update everything, too. If they can't, I might as well get these OTA updates to see if they fix some of my problems.
Thanks for the help.
Click to expand...
Click to collapse
Yes there are a lot of files that cant be updated with roms. The only way to get all of the new firmware is to run the ruu. Turge has figured out how to flash radios now without flashing the ruu so thats good. But thats not everything. I'd wait to run the ruu until the devs change their rom base to the new update. Otherwise no custom rom yet. You can root the stock update after installing, just not many goodies atm.
Thank you very much for your help.
When you say the only way to get the new firmware is to run the new RUU, does that mean running the RUU from at&t or one of the modified RUUs posted on here?
If it is the At&t one, the only way to get it to fully update is by going back to the stock 1.15 ROM, correct?
Yep I ran ruu and got it running stock but my 2nd x+ still running old one wit elegancia till roms get updated I don't mind unrooting updating and rooting takes 30 min tops just patiently waiting for a update hell if viper gets updated first ill rock that
Sent from my HTC One X+ using XDA Premium HD app
badtlc said:
Thank you very much for your help.
When you say the only way to get the new firmware is to run the new RUU, does that mean running the RUU from at&t or one of the modified RUUs posted on here?
If it is the At&t one, the only way to get it to fully update is by going back to the stock 1.15 ROM, correct?
Click to expand...
Click to collapse
The latest ruu for ATT to get the newest firmware is 1.19.502.1 http://dl3.htc.com/application/RUU_E...178_signed.exe
nugzo said:
The latest ruu for ATT to get the newest firmware is 1.19.502.1 http://dl3.htc.com/application/RUU_E...178_signed.exe
Click to expand...
Click to collapse
Correct, but I wasn't sure if you could update directly to that RUU from a custom ROM and get all the updates like hboot, firmware and radio. I was wondering if I needed to go from a custom ROM back to stock 1.15 and THEN do this 1.19 update to get everything updated properly.
If you update your phone to the latest RUU, you won't be able to installed a custom ROM until the devs update their ROM. You update, you stay stock for a moment. You still can ROOT the stock ROM.
badtlc said:
If it is the At&t one, the only way to get it to fully update is by going back to the stock 1.15 ROM, correct?
Click to expand...
Click to collapse
Not exactly. You can upgrade with a RUU if your actual version is equal or lower. You can't downgrade your version unless your phone is S-OFF.
To flash the RUU
Reboot in fastboot mode
type at the prompt >fastboot oem lock
Rebooting
Keep your phone in FASTBOOT USB mode
Run the RUU installer on your computer.
This will FULLY WIPE the phone.
[QUOTE"badtlc"]If it is the At&t one, the only way to get it to fully update is by going back to the stock 1.15 ROM, correct?[/QUOTE]
Not exactly. You can upgrade with a RUU if your actual version is equal or lower. You can't downgrade your version unless your phone is S-OFF.
To flash the RUU
Reboot in fastboot mode
type at the prompt >fastboot oem lock
Rebooting
Keep your phone in FASTBOOT USB mode
Run the RUU installer on your computer.
This will FULLY WIPE the phone.[/QUOTE]
Doing this method, one could use the latest 1.19 directly from HTC and get everything updated? No need to do this method, install the older 1.15, and then do the 1.19 RUU update?
badtlc said:
If it is the At&t one, the only way to get it to fully update is by going back to the stock 1.15 ROM, correct?
Not exactly. You can upgrade with a RUU if your actual version is equal or lower. You can't downgrade your version unless your phone is S-OFF.
To flash the RUU
Reboot in fastboot mode
type at the prompt >fastboot oem lock
Rebooting
Keep your phone in FASTBOOT USB mode
Run the RUU installer on your computer.
This will FULLY WIPE the phone.
Doing this method, one could use the latest 1.19 directly from HTC and get everything updated? No need to do this method, install the older 1.15, and then do the 1.19 RUU update?
Click to expand...
Click to collapse
You can do one of two things to get the full update. One is to go back to a 1.15 stock ROM, flash the stock recovery and run the OTA. The other is to run the latest RUU from HTC (the one from the link posted above) after you've flashed the stock recovery and re-locked the bootloader (otherwise the RUU might not proceed). Bare in mind that running the RUU will wipe your phone to factory settings.
I started a thread here http://forum.xda-developers.com/showthread.php?t=2245955 about people's experiences updating and post-update. Once you decide to update feel free to share your experience there!
I have already updated. I went from elegancia. I locked the bootloader, rebooted to fastboot, and then ran the 1.15 stock RUU. After that, I ran the 1.19 update I downloaded from HTC. I was just trying to figure out if I would have went straight from elegancia to 1.19 if everything including radio, kernel, etc. would have updated properly since elegancia was on the phone and not stock version 1.15. I don't know what these RUUs look at before applying their updates.