Related
Does anybody have AT&T stock 2.20 nandroid backup? I'm trying to make my phone complete stock for a reason. I cannot flash RUU, because previously I flashed Asian 2.42 RUU, and that's why its not letting me to downgrade even with super cid. Backup would be appreciated if anybody can provide it.
Thanks in advance.
Sent from my HTC One XL using xda premium
Nandroid is not going to return you to stock like an RUU would. You would still be rooted and have custom recovery.
What you are asking for would not really have any different result than flashing a stock rooted ROM, so you can do that, if you just want to get the ROM back to stock.
redpoint73 said:
Nandroid is not going to return you to stock like an RUU would. You would still be rooted and have custom recovery.
What you are asking for would not really have any different result than flashing a stock rooted ROM, so you can do that, if you just want to get the ROM back to stock.
Click to expand...
Click to collapse
To be more specific, I want complete stock, non rooted, odexed and with AT&T bloatware backup, that some people my have as a backup.
Sent from my HTC One XL using xda premium
kaiser347 said:
To be more specific, I want complete stock, non rooted, odexed and with AT&T bloatware backup, that some people my have as a backup.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
No one is going to give you their nandroid, since that would have all their personal settings and Google password.
The 2.20 AT&T RUU should work. Are you sure you've got HTC sync installed?
iElvis said:
No one is going to give you their nandroid, since that would have all their personal settings and Google password.
The 2.20 AT&T RUU should work. Are you sure you've got HTC sync installed?
Click to expand...
Click to collapse
I'm not noob, and I pretty sure know how to run RUU. I have all the drivers installed. And currently running JB custom ROM on 2.42 ICS firmware with 1.14 bootloader. I can not run AT&T 2.20 RUU, because I will getting bootloader error. You will have same problem if you run different region RUUs with newer firmware. I don't want personal information. Some people may have clean stock nandroid without any personal stuff.
I had the same problem with my ONE S and there were people who had such nandroids, and they did help me with it.
That's why we call it community. We try to help each other as much as we can.
Sent from my HTC One XL using xda premium
kaiser347 said:
I'm not noob, and I pretty sure know how to run RUU. I have all the drivers installed.
Click to expand...
Click to collapse
Relax man. He's asking for the easy stuff first, since the best solution is very often the easiest one. Better to ask the seemingly 'obvious' question right off the bat, rather than go down some complicated road needlessly.
Re-installing HTC Sync fixes up the issue for the huge majority of people with RUU errors. Not in your case, as you are correct that trying to run the RUU with a lower hboot version number that what is already installed, will cause it to fail. But he is just trying to be helpful.
redpoint73 said:
Relax man. He's asking for the easy stuff first, since the best solution is very often the easiest one. Better to ask the seemingly 'obvious' question right off the bat, rather than go down some complicated road needlessly.
Re-installing HTC Sync fixes up the issue for the huge majority of people with RUU errors. Not in your case, as you are correct that trying to run the RUU with a lower hboot version number that what is already installed, will cause it to fail. But he is just trying to be helpful.
Click to expand...
Click to collapse
I'm relaxed, thank you for understanding me. The reason for this request is that there might be, and its might be an update from At&t in a future eventually. I'm just trying to be prepared for this, because I can not run 2.20 RUU and the only way to get this future update would be from a system setting. I like clean stock, rooted Rom with all the unneeded apps uninstalled. Once I got the update I can just unlock the bootloader and root it and install insecure kernel along.
Sent from my HTC One XL using xda premium
Here is a ruu link, hope it helps
http://forum.xda-developers.com/showthread.php?t=1671237
Sent from my HTC One XL using xda premium
I didnt't realize 2.42 contained an updated hboot. That would obviously prevent running an earlier ruu. Sorry for the confusion.
iElvis said:
I didnt't realize 2.42 contained an updated hboot. That would obviously prevent running an earlier ruu. Sorry for the confusion.
Click to expand...
Click to collapse
It seems hboot is the same 1.14 in both 2.20 and 2.42 RUUs. I think with the latter some other partitions were updated as well, which prevent downgrading.
Sent from my HTC One XL using xda premium
DESERT.TECH said:
Here is a ruu link, hope it helps
http://forum.xda-developers.com/showthread.php?t=1671237
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Thank you for the link. I do have a RUU. But can not install.
Sent from my HTC One XL using xda premium
RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.5 0.05.31_10.30.50.08L_release_309489
http://dl3.htc.com/application/RUU_..._10.30.50.08L_release_309489_signed_ICS_2.exe
ricky176bx said:
http://dl3.htc.com/application/RUU_..._10.30.50.08L_release_309489_signed_ICS_2.exe
Click to expand...
Click to collapse
Any news about sense 5
is this a full stock rom or do you need the ICS 2.35 RUU first before running this if you want to go back to stock? The DL is about 700 MB so I surely hope it's the whole thing otherwise, that's a bit bloated for an update...lol
epsiblivion said:
is this a full stock rom or do you need the ICS 2.35 RUU first before running this if you want to go back to stock? The DL is about 700 MB so I surely hope it's the whole thing otherwise, that's a bit bloated for an update...lol
Click to expand...
Click to collapse
Hi I have a quick question. Was there something about flashing this RUU that would break the S-off exploit? Meaning if we used this RUU, we would no longer be able to S-off?
joemanbui said:
Hi I have a quick question. Was there something about flashing this RUU that would break the S-off exploit? Meaning if we used this RUU, we would no longer be able to S-off?
Click to expand...
Click to collapse
I haven't heard of anything about that but I haven't really read much about it either. For me S-off isn't a big deal. it makes things more convenient but isn't necessary. Really only affects updating radios and blackbox partitions. As long as I got access to recovery and system, I'm fine.
joemanbui said:
Hi I have a quick question. Was there something about flashing this RUU that would break the S-off exploit? Meaning if we used this RUU, we would no longer be able to S-off?
Click to expand...
Click to collapse
The OTA broke soff exploit so I would assume the same here.
Sent from my HTC One S using xda app-developers app
OCedHrt said:
The OTA broke soff exploit so I would assume the same here.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
If you are SOFF prior to running the RUU, you will stay SOFF.
Sent from my HTC VLE_U using xda app-developers app
troby86 said:
If you are SOFF prior to running the RUU, you will stay SOFF.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
thanks this is what i was looking for!
I am s-off, rooted, super CID, etc... for running custom roms. Do i need to do anything before i run the RUU? I want to go back to stock ROM.
sumasage said:
I am s-off, rooted, super CID, etc... for running custom roms. Do i need to do anything before i run the RUU? I want to go back to stock ROM.
Click to expand...
Click to collapse
make sure your CID is US t-mobile.
sumasage said:
I am s-off, rooted, super CID, etc... for running custom roms. Do i need to do anything before i run the RUU? I want to go back to stock ROM.
Click to expand...
Click to collapse
I did not have to change my CID, I just relocked my boot loader first, after the RUU, I was still SOFF and SuperCID.
Sent from my One S using xda app-developers app
troby86 said:
I did not have to change my CID, I just relocked my boot loader first, after the RUU, I was still SOFF and SuperCID.
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
For me, I don't need to re-lock my BL since my CID is T-Mobile.. I just ran RUU and everything successfully plus i'm still S-off and my BL is still unlock After that I just fastboot flash recovery TWRPv2.3.3.0.img
I have superCID, s-off and unlocked boot loader and was able to run the RUU without any issues.
Is this a full Official ROM? What does this update provide? I cannot find any information on Tmobile.com for this update.
jgentry151 said:
Is this a full Official ROM? What does this update provide? I cannot find any information on Tmobile.com for this update.
Click to expand...
Click to collapse
Its the full official RUU for T-Mobile to update you to JB.
Sent from my HTC One S using xda app-developers app
troby86 said:
Its the full official RUU for T-Mobile to update you to JB.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
So is this the same rom that the new JB stock roms in this board are based on? or is this a newer base?
jgentry151 said:
So is this the same rom that the new JB stock roms in this board are based on? or is this a newer base?
Click to expand...
Click to collapse
Mkinney88s ROM and my ROM have the same base as this RUU. This RUU is a bit older than the WWE ROMs that are out though...like ViperOneS...its based on 3.16, and the T-Mobile version is 3.14...but they are both JB...I suggest using the 3.16 bases unless you are T-Mobile US.
Sent from my HTC One S using xda app-developers app
troby86 said:
Mkinney88s ROM and my ROM have the same base as this RUU. This RUU is a bit older than the WWE ROMs that are out though...like ViperOneS...its based on 3.16, and the T-Mobile version is 3.14...but they are both JB...I suggest using the 3.16 bases unless you are T-Mobile US.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Im with TMO USA. The WWE roms caused some 3G issues all the time, I do my best to stay away from the WWE roms at this point. Thanks for the info!
Hey all, I've just switched to this ATT One X and I'm looking for a little guidance. I've rooted, unlocked bootloader, and flashed TWRP. I've also downloaded PAC and GAPPs. That being said, I've read a little about flashing a Rom and a boot.img seperately which would be new to me. I didn't see anything mentioning that process on the PAC thread so I'm assuming that I just wipe data, flash Rom, wipe cache and dalvik, flash gapps and reboot? If there is something I'm missing, could anybody help? Thanks in advance!
Sent from my HTC One X using xda app-developers app
If you are s-off you do not have to flash the boot.img seperately. If you are s-on you have to flash the boot.img with fastboot from a computer.
Sent from my HTC One X using xda app-developers app
mmmatt312 said:
If you are s-off you do not have to flash the boot.img seperately. If you are s-on you have to flash the boot.img with fastboot from a computer.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks! Im s-on at the moment so I'll look into getting s-off when I get some free time. Hopefully adb will cooperate with me, we have a love/hate relationship....
Sent from my HTC One X using xda app-developers app
Quick question, flash the whole rom zip, then the boot.img, then gaaps?
Sent from my HTC One X using xda app-developers app
I'm pretty sure you can flash the boot.img with fastboot before or after the rom. But flash gapps after you flash the rom. The way I used to do it(when I was s-on) was flash rom, flash gapps, then flash the boot.img from the terminal using fastboot.
Sent from my HTC One X using xda app-developers app
[APP] Flash Image GUI - Flash Kernels and Recoveries from normal Android mode! is your friend
flash boot.img first then rom and gapps, but definately do s-off you don't wanna end up forgetting that flashing 3.17/3.18 with s-on + supercid will brick your phone.
Nice! I'm looking into s-off as of now, but what did you mean by flashing 3.17/3.18? I'm on 3.18 and I believe I have superCID. Does that mean I should hold off on flashing until I'm s-off?
Sent from my HTC One X using xda app-developers app
No you can flash now. We weren't aware that you're already on the 3.18 firmware. If you weren't on that firmware you would have needed to RUU up to it in order to flash the ROM, and the warning was to get s-off before running the RUU because s-on + SuperCID + RUU = brick. So, go ahead and flash the ROM.
PS. In future, make sure you provide all relevant information (current firmware/current recovery/s-off or s-on status). This information is needed to help, and it also stops this kind of confusion.
Sent from my Evita
timmaaa said:
No you can flash now. We weren't aware that you're already on the 3.18 firmware. If you weren't on that firmware you would have needed to RUU up to it in order to flash the ROM, and the warning was to get s-off before running the RUU because s-on + SuperCID + RUU = brick. So, go ahead and flash the ROM.
PS. In future, make sure you provide all relevant information (current firmware/current recovery/s-off or s-on status). This information is needed to help, and it also stops this kind of confusion.
Sent from my Evita
Click to expand...
Click to collapse
Sorry for the confusion. Trying to gather as much knowledge on this as possible and didn't think to mention that I did the ota update to 3.18. I appreciate the help guys and hopefully soon I'll have a custom Rom running on this thing :thumbup:
Sent from my HTC One X using xda app-developers app
Successfully flashed PAC and ended up using the app posted here. Worked like a charm! Thanks for all the help guys!
Sent from my One X using xda app-developers app
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
Somebody knows why
This happend or what is the problem
Thanks in advance
Sent from my HTC One XL using xda app-developers app
Do you really expect anyone to be able to help if that's the only information you're giving? Seriously, you haven't given any information whatsoever.
Sent from my Evita
Im on hboot 2.15
Unlocked
S off
Twrp 2.6.3.0
Android 4.2.2
Sense 5
Kickdroid rom halloween edition
Beastmode kernel 3.5 reloaded
Sent from my HTC One XL using xda app-developers app
It looks like it's probably a hardware problem, but to test the theory you could run an RUU and see if the problem persists on the stock ROM. If so you have a faulty digitizer.
Sent from my Evita
I have the same problem on hboot 2.15 no matter what rom I use. Is it possible to downgrade?
Sent from my HTC One X using xda app-developers app
Yaakov. M said:
I have the same problem on hboot 2.15 no matter what rom I use. Is it possible to downgrade?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Please provide exact details on your situation, saying you have the same problem doesn't tell me anything. I also need your bootloader details, ROM details, kernel details, recovery details.
Sent from my Evita
Ok,
hboot 2.15 (latest AT&T ruu)
S-off supercid ect...
Currently running cleanrom 7.0r2 but the problem persists on every rom I've tried since I took the ruu.
I didn't play with custom kernel.
I also tried cm but phone's touchscreen would randomly stop responding all together after sleep.
Tried both twrp and cwm
Thanks
Sent from my HTC One X using xda app-developers app
I need your bootloader details, the first five or six lines, from the very top. The latest at&t RUU comes with the 2.18 hboot, not the 2.15 hboot. I also need to know exactly which recovery versions you've been using. And you haven't described the problem you're having.
Sent from my Evita
*** unlocked **
Evita put ship s off rl
Cid 11111111
Hboot 2.18.0000
Radio 1.35a 32.45.27
Open dsp v33.1.0.45.1128
Emmc boot
December 3 2013 17:10:01:1768
I've tried twrp 2.6.3.0, twrp 2.7, and the latest cwm.
The problem on every rom is a line to which the touch screen is not responding (just below the middle of the display)
Specifically on cm m4 the screen would stop responding all together after waking
Thanks
Edit : the problem started after I took the ruu
Sent from my HTC One X using xda app-developers app
Ok, so you have the 2.18 hboot, that's why I asked for your bootloader details the first time around. You should run an RUU, maybe the 3.18, to see if it resolves your problem.
Sent from my Evita
Can I run the 3.18 ruu after running the 5.something one? And yes I remembered the hboot wrong.
Sent from my HTC One X using xda app-developers app
You can run any Evita RUU when you have s-off, whether it's a higher or lower version.
Sent from my Evita