[Rom]Att leak * Hboot upgrade 1.55 * Deodexed - One (M7) Android Development

Hi to all.
Well, i ve made a Rom based on Ruu zip from user of Rootzwiki Birdman
All Credits and thanks to him
Due to severals pm i made this thread
This rom will upgrade your hboot to 1.55. Just flash rom as a regular one.
Rom is deodexed, stock kernel. Debloated. No root. Wont lose Soff or supercid. Anyway, always backup what you think its important like sdcard and more.
Base 3.10 Leak ATT
IMPORTANT
Before downloading and flashing, read this
http://forum.xda-developers.com/showthread.php?p=45650775
Gdrive link
https://drive.google.com/uc?id=0BzFnR6weqD7pZElXTjk3RUdRX28&export=download
Cheers

Is this the 3.17 base?
Sent from my HTC One using Tapatalk 4

mobb315 said:
Is this the 3.17 base?
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Hi
Noup, its Att leak base 3.10
The thing is that several users ask me for it, as they are scared to update manually their hboot, well, this is the easiest method for them i think.
Just you flash it as normal rom. Got upgrade your hboot to 1.55, then you can flash whatever you want.
For custom rom base 3.17 check you have others devs options, or can try my SD v 5.0 ULTIMATE
Cheers

Ok thanks for the quick reply. Any real benefits to upgrading hboot?
Sent from my HTC One using Tapatalk 4

mobb315 said:
Ok thanks for the quick reply. Any real benefits to upgrading hboot?
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
Allows you to flash firmwares /roms that requires specific hboot number mainly, i guess it s better to have the latest update, in this case, the hboot

In case, it's best to have lowest. Lower HBOOT allows to upgrade, higher won't let you downgrade.
If S-OFF comes out for 1.55 then people with 1.54 can upgrade to 1.55, however if S-OFF is released for 1.54 then people with 1.55 will be out of luck.
Rule is: keep as low HBOOT as possible. If old HBOOT works with new FW, great, if not think twice before upgrading.

lollylost100 said:
In case, it's best to have lowest. Lower HBOOT allows to upgrade, higher won't let you downgrade.
If S-OFF comes out for 1.55 then people with 1.54 can upgrade to 1.55, however if S-OFF is released for 1.54 then people with 1.55 will be out of luck.
Rule is: keep as low HBOOT as possible. If old HBOOT works with new FW, great, if not think twice before upgrading.
Click to expand...
Click to collapse
1+
Added to Op
Great tip

Is HBOOT needed to run 3.10 FW? If it's not, then why does your package update HBOOT?

lollylost100 said:
Is HBOOT needed to run 3.10 FW? If it's not, then why does your package update HBOOT?
Click to expand...
Click to collapse
Well, i ve just make a rom of ruu zip with hboot because i could, once i realized my Hboot was updated, i just stopped working on the rom, also because i could not flash a custom kernel. Then i stated in thread that the rom updates hboot, some sent me pms about rom link cause they didn't want to update manually, and instead of getting pm about rom link, i made this post.
I think rom in itself its not important here, but an easy way to upgrade hboot makes the trick for those who never flashed an update firmware or ruu.
Instead of doing manually using cmd, u just flash this rom, but i did it with Soff and Supercid.

lollylost100 said:
In case, it's best to have lowest. Lower HBOOT allows to upgrade, higher won't let you downgrade.
If S-OFF comes out for 1.55 then people with 1.54 can upgrade to 1.55, however if S-OFF is released for 1.54 then people with 1.55 will be out of luck.
Rule is: keep as low HBOOT as possible. If old HBOOT works with new FW, great, if not think twice before upgrading.
Click to expand...
Click to collapse
But this apply for everybody because I updated from hboot 1.54 to 1.55 and i still s off

Could you please share just the fw package 3.17.502.2?

How does this Rom update hboot exactly? Just curious really....
Sent from my HTC One using Tapatalk 4

vomer said:
Could you please share just the fw package 3.17.502.2?
Click to expand...
Click to collapse
Here is fw package 3.10.502.2 with latest radio and hboot no red warning latest radio is 4A.19.3263.13_10.38j.1157.04 which i have and works perfect
Code:
https://mega.co.nz/#!50wVRKoT!ertraVdAaIJuvLJoBFODVFFgYZAN5PD3aQtugBCqPI4
Remember S Off needed I dont know why some people say to no update hboot because im on 1.55 still SOFF and i was on 1.54 SOFF already uploading file it has hboot 1.55 with no red warning
typo this is 3.10.502.2
Now I confused
there is 3.10.502.2 which is att
3.17.401.2 wich is Europe there is also a 3.17.401.1 ROM
and 3.17.502.2 WTF is this also att?
**** im really confused

maxrdlf95 said:
Remember S Off needed I dont know why some people say to no update hboot because im on 1.55 still SOFF and i was on 1.54 SOFF already
Click to expand...
Click to collapse
Once you have soff it does not matter what hboot you are on.

THanks @vomer
Links for FW is up

maxrdlf95 said:
THanks @vomer
Links for FW is up
Click to expand...
Click to collapse
thanks! :good: but whay is it 3.10 not 3.17??

vomer said:
Could you please share just the fw package 3.17.502.2?
Click to expand...
Click to collapse
vomer said:
thanks! :good: but whay is it 3.10 not 3.17??
Click to expand...
Click to collapse
Because thats the only leaked version? lol

maxrdlf95 said:
Because thats the only leaked version? lol
Click to expand...
Click to collapse
Well, it was the one i found

dragonesdenano said:
Hi to all.
Well, i ve made a Rom based on Ruu zip from user of Rootzwiki Birdman
All Credits and thanks to him
Due to severals pm i made this thread
This rom will upgrade your hboot to 1.55. Just flash rom as a regular one.
Rom is deodexed, stock kernel. Debloated. No root. Wont lose Soff or supercid. Anyway, always backup what you think its important like sdcard and more.
Base 3.10 Leak ATT
IMPORTANT
Before downloading and flashing, read this
http://forum.xda-developers.com/showthread.php?p=45650775
Gdrive link
https://drive.google.com/uc?id=0BzFnR6weqD7pZElXTjk3RUdRX28&export=download
Cheers
Click to expand...
Click to collapse
I have S-ON. This didn't upgrade my hboot to 1.55. I'm still on 1.54. Accidentally flashed an ATT RUU onto my TMO phone.

But you know, that all previously bases leaked here are AT&T leaks as well?
3.09 and 3.17 are NOT WWE 401 bases...all are AT&T bases...so I see no point on releasing an old AT&T base here when there is already a 3.17 AT&T base out? =o

Related

Update hboot on htc one s

HI I will like to know how can I update the hboot on the htc one s my current hboot is 1.06.0000
thank you..
sparda1 said:
HI I will like to know how can I update the hboot on the htc one s my current hboot is 1.06.0000
thank you..
Click to expand...
Click to collapse
Run the latest RUU.
invasion2 said:
Run the latest RUU.
Click to expand...
Click to collapse
Where can I find this lates RUU?
sparda1 said:
HI I will like to know how can I update the hboot on the htc one s my current hboot is 1.06.0000
thank you..
Click to expand...
Click to collapse
Why would you want to update your hboot. I'm on the latest one and would love to go back to 1.06
dc211 said:
Why would you want to update your hboot. I'm on the latest one and would love to go back to 1.06
Click to expand...
Click to collapse
really? I have 2 htc one s one with 1.06 and the other 1.09 the one with the old hboot have a battery drain problem the battery will drain really quick even in standby the 2 phones are running the same rom trick droid 7.1.0 and I thought that may be the problem..
sparda1 said:
really? I have 2 htc one s one with 1.06 and the other 1.09 the one with the old hboot have a battery drain problem the battery will drain really quick even in standby the 2 phones are running the same rom trick droid 7.1.0 and I thought that may be the problem..
Click to expand...
Click to collapse
You should compare the basebands not the hboot. Check under settings -> about. You can update your baseband to the latest by flashing the newer radio. But keep your hboots where they are for now, DON'T use a OTA update or RUU.
dc211 said:
You should compare the basebands not the hboot. Check under settings -> about. You can update your baseband to the latest by flashing the newer radio. But keep your hboots where they are for now, DON'T use a OTA update or RUU.
Click to expand...
Click to collapse
Why is older hboot better than the new ones? I know you can flash radio, but anything else? Surely there is some benefit to running the full ruu and getting updated system files in addition to updated hboot?
Sent from my Nexus 7 using xda app-developers app
chrikenn said:
Why is older hboot better than the new ones? I know you can flash radio, but anything else? Surely there is some benefit to running the full ruu and getting updated system files in addition to updated hboot?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Hboot is nothing but problems in the root world...if you update and decide to root, you'll run into trouble.
invasion2 said:
Hboot is nothing but problems in the root world...if you update and decide to root, you'll run into trouble.
Click to expand...
Click to collapse
So rather than running ruu to get latest firmware and baseband, you recommend just flashing them individually?
Sent from my Nexus 7 using xda app-developers app
chrikenn said:
So rather than running ruu to get latest firmware and baseband, you recommend just flashing them individually?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Well it's a big decision. If you plan to NOT root, then yes, run the RUU and update everything. If you think about rooting, I would wait to update. Sorry.
sparda1 said:
HI I will like to know how can I update the hboot on the htc one s my current hboot is 1.06.0000
thank you..
Click to expand...
Click to collapse
Do not update the hboot unless you want to jump through hoops to flash roms. I have seen many complain of issues with hboot higher than 1.09. Highly recommend leaving it alone. I am on 1.06 and never have problems like the updated ones.
Sent from my HTC VLE_U using Xparent SkyBlue Tapatalk 2
invasion2 said:
Well it's a big decision. If you plan to NOT root, then yes, run the RUU and update everything. If you think about rooting, I would wait to update. Sorry.
Click to expand...
Click to collapse
thanks everyone for your help can some one tell me whats the best radio to be flashed on the one s?
sparda1 said:
thanks everyone for your help can some one tell me whats the best radio to be flashed on the one s?
Click to expand...
Click to collapse
In which country are you living?
If it's somewhere in Europe (sparda?! - maybe Germany ) the latest radio is 1.06s.50.02.27_2_10.08.50.04L.
Anyway you should keep your current hboot so. Just flash the radio. If you want, send me a PM and I'll give you a link to a cwm backup I made right after my RUU Update. It's untouched (no personal settings etc.), only with Super SU in \system, so you will have everything like as you'd run the RUU update and rooted your device.
Please learn more about the 4.04 update here.
LikeaG2root said:
Do not update the hboot unless you want to jump through hoops to flash roms. I have seen many complain of issues with hboot higher than 1.09. Highly recommend leaving it alone. I am on 1.06 and never have problems like the updated ones.
Sent from my HTC VLE_U using Xparent SkyBlue Tapatalk 2
Click to expand...
Click to collapse
I appreciate your advise. I discovered that I am also on 1.06 HBoot and was thinking that I had to do an OTA update to get the latest radio. So now I should be able to find a radio update and flash it in CWM.
-------------
Half an hour of searching later, I've come to conclude that the only way to update the radio is via the RUU update process. I haven't found any newer radio that is flashable. So I don't really think there is any way to keep my 1.06 hboot AND update the radio.
if you are using cwm you need to fastboot it if using twrp recovery you can flash thru recovery
http://ville.giev.de/?page_id=42
https://www.dropbox.com/s/zvi1a70n41yy2ri/radio_OTA_19072012.zip
NOTE: the "recovery.img" is the exact name of that img file
dhigby said:
I appreciate your advise. I discovered that I am also on 1.06 HBoot and was thinking that I had to do an OTA update to get the latest radio. So now I should be able to find a radio update and flash it in CWM.
-------------
Half an hour of searching later, I've come to conclude that the only way to update the radio is via the RUU update process. I haven't found any newer radio that is flashable. So I don't really think there is any way to keep my 1.06 hboot AND update the radio.
Click to expand...
Click to collapse
You didn't search hard enough. On hboot 1.06 you can flash radios using twrp, no ruu necessary. I know because I did it, and so did many others.
-Sent from my HTC One S.-
did no one read my post 15
rugmankc said:
if you are using cwm you need to fastboot it if using twrp recovery you can flash thru recovery
http://ville.giev.de/?page_id=42
https://www.dropbox.com/s/zvi1a70n41yy2ri/radio_OTA_19072012.zip
NOTE: the "recovery.img" is the exact name of that img file
Click to expand...
Click to collapse
The radios on the Cyanogenmod site (first link) are from the 1.78 base. I am using TweakDroid 7.1 which is from the 2.21 base and so I want the most recent radio that goes with that base. Your second link to the dropbox gives me hope... What is it? Dated July 19, would this be the one from the newer base?
Thanks!
Yes that is the newest
The other link is to how to fastboot radio. Fastboot into recovery per instructions. Be careful.
rugmankc said:
Yes that is the newest
The other link is to how to fastboot radio. Fastboot into recovery per instructions. Be careful.
Click to expand...
Click to collapse
do i need to update my h.boot so my wifi works again on viper 2.0.0?
how do we flash radios? i see no stickies about that

How to downgrade hboot after s-off???

currently on hboot 1.14 how do i downgrade to 1.01?
EDIT: Got it done, thanks though!
AngioNicholai said:
currently on hboot 1.14 how do i downgrade to 1.01?
EDIT: Got it done, thanks though!
Click to expand...
Click to collapse
Share?
you don't need to downgrade with s-off
But on a related issue ... with security now removed ... is it worth upgrading to the latest hboot?
i found 2.20 to bring improvements from 1.85.
edit: pretty sure that had nothing to do with hboot though.
how did you do it?
Flashing hboots(newer or older)
Put desired hboot into adb/fastboot folder
fastboot flash hboot NameOfHbootFile
Sent from my SPH-L710 using Tapatalk 2
any major improvements in the latest JB hboot and radio?
greganka said:
any major improvements in the latest JB hboot and radio?
Click to expand...
Click to collapse
Ok, really? Come on bro read. This has been stated for weeks/months. The new jb ota only works with sense ROMs and are incompatable with anything but sense 4+ due to some change in the firmware. So I'd advise not to update until we get a fix. But since I'm nice I told you :thumbup:
Sent from my One X using Tapatalk 2
Kole_Ackerson said:
Ok, really? Come on bro read. This has been stated for weeks/months. The new jb ota only works with sense ROMs and are incompatable with anything but sense 4+ due to some change in the firmware. So I'd advise not to update until we get a fix. But since I'm nice I told you :thumbup:
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
alot of people got all hboot upgrade happy for some reason

[Q] (Cyanogenmod 10.1) HBoot requirement???

Hello, I am fairly new to XDA so, I do not know much. But I am fairly knowledged on technology so just say what you may to help out.
I rooted my HTC One X (Evita) And I installed Cyanogenmod 10 . Now I wanna install cm10.1 nightly, now I installed the
M-2 Release and went back to cm10 now I hear there is a HBOOT requirement.
Now, what would happen if. I tried the nightly (boot loop)?? Because I wanna try it and I don't really trust any other dev except AOKP. Thanks!
There is no requirement. But if your on hboot 2.14 from either a ruu or your hox came with 2.14 then you need to downgrade your touchscreen firmware. The thread is sticked in original dev section. You should be fine flashing the nightly
Sent from my Elemental Venomized S-off HTC One XL
majortaylor said:
There is no requirement. But if your on hboot 2.14 from either a ruu or your hox came with 2.14 then you need to downgrade your touchscreen firmware. The thread is sticked in original dev section. You should be fine flashing the nightly
Sent from my Elemental Venomized S-off HTC One XL
Click to expand...
Click to collapse
Well, i rooted my phone when it was HBOOT 2.20 running Sense 4.0.4, is this fine? and if i'm wrong will i get a hard bricked phone??(which is what i don't wan't)
i4GS said:
Well, i rooted my phone when it was HBOOT 2.20 running Sense 4.0.4, is this fine? and if i'm wrong will i get a hard bricked phone??(which is what i don't wan't)
Click to expand...
Click to collapse
No you wont get bricked but if your not soff you will need to flash the boot.img of the ROM in question in fast boot because your on 2.20. All the instructions for flashing will be in the roms thread in the first post.
Sent from my Elemental Venomized S-off HTC One XL
majortaylor said:
No you wont get bricked but if your not soff you will need to flash the boot.img of the ROM in question in fast boot because your on 2.20. All the instructions for flashing will be in the roms thread in the first post.
Sent from my Elemental Venomized S-off HTC One XL
Click to expand...
Click to collapse
Sorry! I meant hboot 1.14.0002 , evita S-on.
It's still safe to install?? sorry but i'm just making sure because i can't afford a repair. Though i think i have warranty...
i4GS said:
Sorry! I meant hboot 1.14.0002 , evita S-on.
It's still safe to install?? sorry but i'm just making sure because i can't afford a repair. Though i think i have warranty...
Click to expand...
Click to collapse
You won't brick. Just make sure you flash the boot.img if the ROM requires it. Just check the 1st post in the ROMs thread and there should be instructions for flashing if your worried still
Sent from my Elemental Venomized S-off HTC One XL
majortaylor said:
You won't brick. Just make sure you flash the boot.img if the ROM requires it. Just check the 1st post in the ROMs thread and there should be instructions for flashing if your worried still
Sent from my Elemental Venomized S-off HTC One XL
Click to expand...
Click to collapse
This is true. I am on 1.14. I flashed about four roms. If you are stuck in bootloop, then just reformat /system and /data, and reflash, and then use fastboot the boot.img. Most of the CM roms requires it. But, I seriously suggest you get S-OFF, while you can. It is worth it, and makes life really simple. The link is in my sig
Herc08 said:
This is true. I am on 1.14. I flashed about four roms. If you are stuck in bootloop, then just reformat /system and /data, and reflash, and then use fastboot the boot.img. Most of the CM roms requires it. But, I seriously suggest you get S-OFF, while you can. It is worth it, and makes life really simple. The link is in my sig
Click to expand...
Click to collapse
Actually have you guys tried the King Kong ROM for Evita? I wanna try that. Any insights? [About to flash]
i4GS said:
Actually have you guys tried the King Kong ROM for Evita? I wanna try that. Any insights? [About to flash]
Click to expand...
Click to collapse
Try it out yourself. Its cm, AOKP and pa.
Sent from my Nexus 4
i4GS said:
Actually have you guys tried the King Kong ROM for Evita? I wanna try that. Any insights? [About to flash]
Click to expand...
Click to collapse
No. I am content with what i have. But let me know.
Sent from my Liquid-fied Evita using xda-developers app
hboot 1.09 with s-ff
Ive had 1.09 all along and its flashed anything ive thrown at it
Ooooooooooooo..... Wrong thread) :
-Sugardaddy Duncan
hi plz help me
i have htc one xl with hboot 2.10 and radio 3.20...
i wanna to flash cyanogenmod 10.1 or newer...when i flash this rom it says ma hboot does not supported...
i look every where to update my hboot...but every one say i cant update... plz help me...i want cyanogenmod 10.1
sepehrppp said:
i have htc one xl with hboot 2.10 and radio 3.20...
i wanna to flash cyanogenmod 10.1 or newer...when i flash this rom it says ma hboot does not supported...
i look every where to update my hboot...but every one say i cant update... plz help me...i want cyanogenmod 10.1
Click to expand...
Click to collapse
You have the middle eastern variant of this phone, none of the firmware/hboots/radios etc from the normal version are compatible and will most likely brick your phone if you try to install them. Basically, you can't run any aosp ROM because you can't flash the necessary upgrades. It's unfortunate but you're stuck with Sense ROMs.
The problem is that there simply aren't enough of the middle eastern variant around so there is no development specifically for it, so all you users with that variant are kinda stuck coming into this forum where not everything is compatible.
Sent from my Evita
thanks man...
timmaaa said:
You have the middle eastern variant of this phone, none of the firmware/hboots/radios etc from the normal version are compatible and will most likely brick your phone if you try to install them. Basically, you can't run any aosp ROM because you can't flash the necessary upgrades. It's unfortunate but you're stuck with Sense ROMs.
The problem is that there simply aren't enough of the middle eastern variant around so there is no development specifically for it, so all you users with that variant are kinda stuck coming into this forum where not everything is compatible.
Sent from my Evita
Click to expand...
Click to collapse
thanks for helping me...
how about to get supercid then flash ruu 3.18??
You could try, but there's a really good chance you'll brick. Personally I wouldn't risk it.
Sent from my Evita
I believe I am running hboot 2.20.502.7 and I want to install cyanogenmod 10.2
I keep getting errors when attempting to flash. it says something like:
assert failed getprop( ro.bootloader )
^this is followed by some numbers including 2.14.0000 and 2.15.0000
do I need to downgrade my hboot firmware to install this rom?
thanks
erikxj said:
I believe I am running hboot 2.20.502.7 and I want to install cyanogenmod 10.2
I keep getting errors when attempting to flash. it says something like:
assert failed getprop( ro.bootloader )
^this is followed by some numbers including 2.14.0000 and 2.15.0000
do I need to downgrade my hboot firmware to install this rom?
thanks
Click to expand...
Click to collapse
There's no such thing as hboot 2.20, that's your software version. You need to upgrade your firmware by running the 3.18 RUU. It does state that very clearly in the CM thread. You must have s-off to do this or you'll brick.
Sent from my Evita
timmaaa said:
There's no such thing as hboot 2.20, that's your software version. You need to upgrade your firmware by running the 3.18 RUU. It does state that very clearly in the CM thread. You must have s-off to do this or you'll brick.
Sent from my Evita
Click to expand...
Click to collapse
I tried getting s-off with the facepalm method and had no luck. I had no erros other than the ones expected in the instructions. I'm beginning to wonder if maybe my firmware is too old. I now know that my kernal version is 3.0.51.
Why not update your ROM and try again?
Sent from my Evita

Do I need to update my RUU if I'm installing a CM10.1 based rom?

I was running ViperRom XL, and it messed up my phone. I was thinking about going back to stock but wanted to give another rom a try before doing that. I was considering installing Avatar Rom which says to follow the Cyanogenmod directions for installation. The first line when looking at Cyanogenmod's installation instructions is:
The CM 10.1 builds require you to be updated to the newest 3.17/3.18 RUU (for the updated firmware and the 2.14 hboot). You also must downgrade your touchscreen firmware, see here: http://forum.xda-developers.com/showpost.php?p=38304611&postcount=1
That line seemed a little ambiguous to me, and I wanted to make sure I absolutely understood before continuing.
I'm only running hboot ver 1.14.0002 with S-OFF and SuperCID. Since I never updated to 2.14, does that mean I don't need to update my RUU to 3.17/3.18? Do I need to downgrade my touchscreen firmware?
Or can I get right into flashing the new rom?
Thanks in advance for your help.
Yes, if it has the 3.4 kernel you will need to RUU up to 3.18.
Sent from my Evita
timmaaa said:
Yes, if it has the 3.4 kernel you will need to RUU up to 3.18.
Sent from my Evita
Click to expand...
Click to collapse
Great, thanks!
I need to edit this because I have a choice overload with all of these RUUs. I went to http://forum.xda-developers.com/showthread.php?t=2191477. I'm running on AT&T, but the latest RUU (RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe) doesn't mention AT&T. In fact, the only AT&T RUU is the 1.44 version (RUU_Evita_UL_ATT_US_1.44.502.1_Radio_0.15.3201.09_ release_249105.exe).
Would I use the Cingular 3.18 version? Which is the correct RUU to update to?
The Cingular 3.18 one is the correct att one.
Sent from my Evita
If you look at the first post in the Dev thread, you will also see that it is no longer necessary for you to downgrade your touchpanel firmware. H8 had that removed quite a while ago.
Sluff said:
If you look at the first post in the Dev thread, you will also see that it is no longer necessary for you to downgrade your touchpanel firmware. H8 had that removed quite a while ago.
Click to expand...
Click to collapse
hi
does that mean i can flash cm10?
i am on viper xl and hboot 2.14 without downgrading the firmware?
Yep you should be good to go.
Sent from my Evita
timmaaa said:
Yep you should be good to go.
Sent from my Evita
Click to expand...
Click to collapse
does that also mean that i can try any asop 4.2.2 rom now ?
Yep. But you might need to downgrade your touchscreen firmware for the older ROMs using the 3.0 kernel.
Sent from my Evita

I can install RUU with my S-off Cid 11111?

Hello geniuses
I have a doubt, my HOXL phone is new and comes with software
RUU_Evita_UL_Cingular_US_1.85.502.3_R2_Radio_0.17. 32.09. 12_10. 86.32 08L_release_262092_signed. exe
EVITA PVT SHIP S-OFF
CID-11111111
H.boot 1.09.0000
I want to install the latest version
RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24 p. 32.09 06_10. 130.32 34_release_signed. exe
But I am afraid of making it brick but the S-OFF CID 11111
I can? or not?
Or I have to return it to S-ON
Is which the correct way??
You'll be fine, it only bricks when you have SuperCID + s-on. Your current configuration (SuperCID + s-off) is fine.
Sent from my Evita
timmaaa said:
You'll be fine, it only bricks when you have SuperCID + s-on. Your current configuration (SuperCID + s-off) is fine.
Sent from my Evita
Click to expand...
Click to collapse
Thank you, I am more reassured
You or someone I could confirm if the version
is 3.18 best for my phone? or they have any better?
The 3.18 RUU is the latest at&t RUU that has been released. It will update your hboot to 2.14, which is good because if you plan on running any recent aosp ROM you need that hboot. If you plan on staying stock though you'll have JB 4.1 running.
Sent from my Evita
timmaaa said:
The 3.18 RUU is the latest at&t RUU that has been released. It will update your hboot to 2.14, which is good because if you plan on running any recent aosp ROM you need that hboot. If you plan on staying stock though you'll have JB 4.1 running.
Sent from my Evita
Click to expand...
Click to collapse
Timmaaa,
If I've upgraded the firmware and flashed Turge's 4.2.2 sense ROM, do you think it's safe to RUU back to stock?
The combination of the new ROM, the new firmware, and Beastmode kernel seem to produce bad behaviors like going to airplane mode during calls and random shutdowns.
Thanks,
Dan
Sent from my HTC One XL using xda app-developers app
DanGeorges said:
Timmaaa,
If I've upgraded the firmware and flashed Turge's 4.2.2 sense ROM, do you think it's safe to RUU back to stock?
The combination of the new ROM, the new firmware, and Beastmode kernel seem to produce bad behaviors like going to airplane mode during calls and random shutdowns.
Thanks,
Dan
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I haven't seen anyone report running an RUU while on the latest firmware, but if you're s-off you should be safe to do so. Please note I'm saying you SHOULD be safe, this is not a guarantee as I haven't tested it, but I'd assume that the theory is sound.
Sent from my Evita
timmaaa said:
I haven't seen anyone report running an RUU while on the latest firmware, but if you're s-off you should be safe to do so. Please note I'm saying you SHOULD be safe, this is not a guarantee as I haven't tested it, but I'd assume that the theory is sound.
Sent from my Evita
Click to expand...
Click to collapse
Thanks for the advice and warning. The firmware downgrade is the one thing that makes me hesitate.
Any ideas on the issues I'm experiencing? I really like the ROM. It's buttery smooth.
Sent from my HTC One XL using xda app-developers app
If you've upgraded your firmware you might not necessarily need to use the Beastmode kernel, you could try dirty flashing the ROM. This will in effect just replace Beastmode with the stock kernel.
Sent from my Evita
I've been looking all over this forum and would appreciate some related help! I'm also trying to run ViperXL 4.1 but have constant reboots which many posts suggest can be remedied by upgrading ones firmware. I'm SuperCID + s-off, hboot 1.14, and I don't know where to go from here! What should I upgrade and how? ...any links/help would be appreciated!
Greatday1 said:
I've been looking all over this forum and would appreciate some related help! I'm also trying to run ViperXL 4.1 but have constant reboots which many posts suggest can be remedied by upgrading ones firmware. I'm SuperCID + s-off, hboot 1.14, and I don't know where to go from here! What should I upgrade and how? ...any links/help would be appreciated!
Click to expand...
Click to collapse
After all this time searching I only had to ask and I got lucky and found it!
http://forum.xda-developers.com/showthread.php?t=2423735
timmaaa said:
If you've upgraded your firmware you might not necessarily need to use the Beastmode kernel, you could try dirty flashing the ROM. This will in effect just replace Beastmode with the stock kernel.
Sent from my Evita
Click to expand...
Click to collapse
Can I just flash the boot.img from the ROM instead of dirty flashing the entire thing?
Yep.
Sent from my Evita

Categories

Resources