Will someone post the correct 1.85 RUU for this phone, or send a link to it? Having a little trouble trying to find it. Or maybe I did?
RUU_Evita_Cingular_US_1.85.502.3_R2_Radio_0.71.32.09.12_10.86.32.08L_release_262092_signed
I'm trying to downgrade via this guide: http://forum.xda-developers.com/showpost.php?p=33914948&postcount=65
Edited the mmcblk0p23 just fine, placed it back on my phone and tried to run the RUU but it says that it wasn't able to run, which leads me to the conclusion it's the wrong RUU.
Any input would be fantastic.
Edit: just tried again and this is the error that I am getting.
Here: http://forums.team-nocturnal.com/showthread.php/1005-RUU-One-X-XL-LTE-RUU-s
Here: http://forum.xda-developers.com/showthread.php?t=1670238
Or also here: http://forum.xda-developers.com/showthread.php?t=1671237
I believe that since you are editing the version number on your phone, it shouldn't matter what RUU version, as long as the CID is correct (which SuperCID should also render a moot point).
redpoint73 said:
Here: http://forums.team-nocturnal.com/showthread.php/1005-RUU-One-X-XL-LTE-RUU-s
Here: http://forum.xda-developers.com/showthread.php?t=1670238
Or also here: http://forum.xda-developers.com/showthread.php?t=1671237
I believe that since you are editing the version number on your phone, it shouldn't matter what RUU version, as long as the CID is correct (which SuperCID should also render a moot point).
Click to expand...
Click to collapse
Well, quick on the draw with 3 links... I have the correct one. Now it's just a matter of finding out why it's not working. I'll look at my CID and see what's going on.
Did you reboot into fast boot and relock the boot loader after applying the edit?
Im trying this right now but my hex file is all zeros? Why is this and what should I do to resolve this?
absolutelygrim said:
Did you reboot into fast boot and relock the boot loader after applying the edit?
Click to expand...
Click to collapse
Yeah. Ran the 2.20 RUU just fine
mlaws90 said:
Im trying this right now but my hex file is all zeros? Why is this and what should I do to resolve this?
Click to expand...
Click to collapse
The place you have to edit will be on the right side, You'll find the line 0x0a0 on the left.
Myrder said:
The place you have to edit will be on the right side, You'll find the line 0x0a0 on the left.
Click to expand...
Click to collapse
Screenshot:
Is this all I do?:
mlaws90 said:
Is this all I do?
Click to expand...
Click to collapse
Yeah
Wait, that's your mmcblk0p23? That's wrong, that should have your CID and Clearimage what not above the 0x0a0 line...
Grim, what do?
Myrder said:
Yeah
Wait, that's your mmcblk0p23? That's wrong, that should have your CID and Clearimage what not above the 0x0a0 line...
Grim, what do?
Click to expand...
Click to collapse
Yeah, I only have the unlocked bootloader, not SuperCID, I THINK, I did it a long time ago, I got the phone on release day. Could this be why? I am getting an RUU Error 154 or 155 I think why I do try it it will go about 2 min then fail.
mlaws90 said:
I only have the unlocked bootloader, not SuperCID, I did it a long time ago, I got the phone on release day. Could this be why? I am getting an RUU Error 154 or 155 I think why I do try it it will go about 2 min then fail.
Click to expand...
Click to collapse
Oh, that makes sense.. I got the phone two weeks after release, and finally decided to root about 3 weeks ago-ish? so me being dumb I didn't even think to look here before I did the OTA update from AT&T. So I had to do the x factor exploit to get rooted. That might be why yours isn't like mine...? I'm not 100% sure on that one.
mlaws90 said:
Yeah, I only have the unlocked bootloader, not SuperCID, I THINK, I did it a long time ago, I got the phone on release day. Could this be why? I am getting an RUU Error 154 or 155 I think why I do try it it will go about 2 min then fail.
Click to expand...
Click to collapse
That was the same way mine was. I got the 155 error. Going to run some errands after I get my phone back working again.. and give it another go later.
mlaws90 said:
Yeah, I only have the unlocked bootloader, not SuperCID, I THINK, I did it a long time ago, I got the phone on release day.
Click to expand...
Click to collapse
You can't have an unlocked bootloader without SuperCID on the AT&T branded version. Or possibly another CID besides the AT&T CID, since AT&T's CID is not allowed on HTCDev.com.
Should look like this
absolutelygrim said:
Should look like this
Click to expand...
Click to collapse
But why doesnt mine look like that , can someone upload a mmcblk0p23 for me to use, if that is possible. Mine is all Zeros and I get the 154 or 155 error on RUU.
mlaws90 said:
But why doesnt mine look like that , can someone upload a mmcblk0p23 for me to use, if that is possible. Mine is all Zeros and I get the 154 or 155 error on RUU.
Click to expand...
Click to collapse
Try extracting p23 with your phone plugged into a computer and USB debugging on
I'll give this another go later tonight, If it doesn't work I'll just downgrade my hboot and leave it alone. lol.
Myrder said:
I'll give this another go later tonight, If it doesn't work I'll just downgrade my hboot and leave it alone. lol.
Click to expand...
Click to collapse
I drowngraded hboot, changed main version and then ran the RUU just now with no problems. Weird that it isn't working for you.
mbh87 said:
I drowngraded hboot, changed main version and then ran the RUU just now with no problems. Weird that it isn't working for you.
Click to expand...
Click to collapse
First time I got ahead of myself and didn't save the mmcblk0p23... The next time, idk wtf happened. I'll downgrade hboot in a bit and then try again to see what that will do.
Myrder said:
First time I got ahead of myself and didn't save the mmcblk0p23... The next time, idk wtf happened. I'll downgrade hboot in a bit and then try again to see what that will do.
Click to expand...
Click to collapse
If you tried running it over the top of 2.20 without downgrading hboot then that would be a problem too.
Related
http://alpharev.nl/x/beta/
If you have another hboot, you are SOL without upgrading to hboot 1.02.0000
attn1 said:
http://alpharev.nl/x/beta/
If you have another 1.x hboot, you are SOL without upgrading to the ATT 2.2.2 RUU.
Click to expand...
Click to collapse
sweetness.
worked for me
Sooooo tempted to flash OTA 2.2 just to use this to s-off. Somebody try it on the .57 bootloader to see if it works for s-off!
unsivil_audio said:
Sooooo tempted to flash OTA 2.2 just to use this to s-off. Somebody try it on the .57 bootloader to see if it works for s-off!
Click to expand...
Click to collapse
says only supports 1.02
Strange, you would think an exploit in 1.02 would also exist in anything earlier and could be utilized.
unsivil_audio said:
Sooooo tempted to flash OTA 2.2 just to use this to s-off. Somebody try it on the .57 bootloader to see if it works for s-off!
Click to expand...
Click to collapse
I got .057 on mine ... was holding off on pushing the upgrade ... but I guess its time to get the hboot up to specs
katz said:
I got .057 on mine ... was holding off on pushing the upgrade ... but I guess its time to get the hboot up to specs
Click to expand...
Click to collapse
i would hold off until official but who knows
i updated just for this, i was told it only supports 1.02
So, in theory...you could nandroid back up your CM7, update to 2.2.2 and then S-OFF and then nandroid restore your CM7 back up?
zervic said:
So, in theory...you could nandroid back up your CM7, update to 2.2.2 and then S-OFF and then nandroid restore your CM7 back up?
Click to expand...
Click to collapse
what i did
I pulled the trigger and upgraded with RUU to get HBOOT 1.02.0000, but alas, now I'm stuck. It hangs at "Acquiring root (method 1)..."
Oh Well. Hope they get a newer beta soon. Can't mess with my Aria now.
Gene Poole said:
I pulled the trigger and upgraded with RUU to get HBOOT 1.02.0000, but alas, now I'm stuck. It hangs at "Acquiring root (method 1)..."
Oh Well. Hope they get a newer beta soon. Can't mess with my Aria now.
Click to expand...
Click to collapse
was done for me in about 5 seconds?
sorry
drowningchild said:
what i did
Click to expand...
Click to collapse
Roger...looks like i'll have to get a Live CD made and get this tonight...need to find directions for updating to 2.2.2 :s
I did a RUU update and when I got back to the channel window BETA WAS CLOSED ...
told you to hold off
OK, reran from my gentoo box instead of my ubuntu VM and it worked. I'm a little annoyed that it says ---AlphaRev--- at the top of HBOOT. Won't make it easy to slip by the att warranty desk.
Well this sucks, I missed it. Now lets wait another month for the actual release lol...
Gene Poole said:
OK, reran from my gentoo box instead of my ubuntu VM and it worked. I'm a little annoyed that it says ---AlphaRev--- at the top of HBOOT. Won't make it easy to slip by the att warranty desk.
Click to expand...
Click to collapse
So what's to stop you from flashing the stock 2.2.2 RUU to return it - erasing the aplharev hboot?
attn1 said:
So what's to stop you from flashing the stock >>>>2.2.2<<<< RUU to return it - erasing the aplharev hboot?
Click to expand...
Click to collapse
Oh - two two twain - Truman Capote.
Get it?
attn1 said:
So what's to stop you from flashing the stock 2.2.2 RUU to return it - erasing the aplharev hboot?
Click to expand...
Click to collapse
Tried that. Shows all the images then shows "Bypassed" next to hboot and some message scrolls by like "cannot roll back hboot image" or something like that.
i rooted my device not too long ago with revolutionary.. Everything was successful..
When i got the phone i had the hboot 1.1800
well i went to try a rom.. ICS..
Told me i had to get the latest firmware, well i places the file on my sd card and went into hboot..
it was doing the update but said incorrect CID and now when i reboot, i get the boot loop on the htc screen..
i have a sd card reader, so i can put it in my computer.. so i tried to put back the original img.zip back because i did the win recovery..
so when my device reads that, it says incorrect model..
Help please!
oh my hboot says 1.27 now... how do i get back to my original 1.18?? i have to unroot it now but dunno how
Enter bootloader.
Perform superCID.
Reflash firmware, should be good to go with ics.
Sent from my Pyramid-T
thank you.. can you give me a link to the SuperCID
http://forum.xda-developers.com/showthread.php?t=1192300
Only takes a minute.
Sent from my Pyramid-T
stringer7 said:
http://forum.xda-developers.com/showthread.php?t=1192300
Only takes a minute.
Sent from my Pyramid-T
Click to expand...
Click to collapse
thanks again lol.. but im not seeing where to download it.. im skimming thru it because i have to be somewhere in 15 minutes!
Ha ha, you don't download superCID. it's a fastboot command! The thread has a guide, its a simple operation.
Sent from my Pyramid-T
matholomus said:
thanks again lol.. but im not seeing where to download it.. im skimming thru it because i have to be somewhere in 15 minutes!
Click to expand...
Click to collapse
Take your time man, this will take longer than 15 minutes. You always have to read the information more than once so that you don't mess up your phone like you did.
Step 4 tells you how to SuperCID
Hgaara said:
Take your time man
Click to expand...
Click to collapse
Sound advice...
Sent from my Pyramid-T
Hgaara said:
Take your time man, this will take longer than 15 minutes. You always have to read the information more than once so that you don't mess up your phone like you did.
Step 4 tells you how to SuperCID
Click to expand...
Click to collapse
ok im doing what it says.. but when i type adb devices.. it doesnt give me my phone s/n
Easier way - download the firmware that has your CID, kohr-ah has a thread covering all of them I believe
Edit:
http://forum.xda-developers.com/showthread.php?t=1459767
1. Find out your CID
2. Download firmware for your CID
3. Put firmware on your sd card
4. Flash
5. ???
6. Profit.
matholomus said:
ok im doing what it says.. but when i type adb devices.. it doesnt give me my phone s/n
Click to expand...
Click to collapse
Do you have the drivers installed?
cdstewart said:
Easier way - download the firmware that has your CID, kohr-ah has a thread covering all of them I believe
Click to expand...
Click to collapse
he has 1.17, not 1.18
V1k70r said:
Do you have the drivers installed?
Click to expand...
Click to collapse
yes..
10 char
... guess im screwed. damn!!
matholomus said:
... guess im screwed. damn!!
Click to expand...
Click to collapse
my dumbass used the wrong firmware file... wow.. i used htc instead of tmobile.. up and running!
HELP!!!
its my birthday today and i just got my tmobile htc sensation i tryed to install a new rom so i did the revolutionary successfully and now i have the bootloader Hboot 1.27.1100 and i believe i never got my CID number before i decided to try to flash the HD 5.2 rom so when i tryed it didnt work so now i dont know how to get my CID number because i can get to my original rom and even tho i backed up my rom it still wont let me is there anyone who can help me i also have the 4ext recovery and ive been trying different roms all day but they all do the same thing which takes me through a bootloop and its getting sicking can someone please help me i got a date 2day for my bday dont wanna be without my gift
bigb1324 said:
its my birthday today and i just got my tmobile htc sensation i tryed to install a new rom so i did the revolutionary successfully and now i have the bootloader Hboot 1.27.1100 and i believe i never got my CID number before i decided to try to flash the HD 5.2 rom so when i tryed it didnt work so now i dont know how to get my CID number because i can get to my original rom and even tho i backed up my rom it still wont let me is there anyone who can help me i also have the 4ext recovery and ive been trying different roms all day but they all do the same thing which takes me through a bootloop and its getting sicking can someone please help me i got a date 2day for my bday dont wanna be without my gift
Click to expand...
Click to collapse
ARHD 5.2 doesnt work with the 1.27 hboot - try 6.X (at your own risk) http://forum.xda-developers.com/showthread.php?t=1098849
bigb1324 said:
its my birthday today and i just got my tmobile htc sensation i tryed to install a new rom so i did the revolutionary successfully and now i have the bootloader Hboot 1.27.1100 and i believe i never got my CID number before i decided to try to flash the HD 5.2 rom so when i tryed it didnt work so now i dont know how to get my CID number because i can get to my original rom and even tho i backed up my rom it still wont let me is there anyone who can help me i also have the 4ext recovery and ive been trying different roms all day but they all do the same thing which takes me through a bootloop and its getting sicking can someone please help me i got a date 2day for my bday dont wanna be without my gift
Click to expand...
Click to collapse
Punctuation omg.
I have superCID.
I've relocked the bootloader
I get error 140 when trying to go back to 1.73 from 1.85. What am I missing?
bootloader screen says
Tampered
relocked
security warning
What if you RUU to 1.85, which should get rid of tampered message and then try 1.73?
I've tried that before I'll try it again though
Why do you want stock? Returning this one too? I had a hell of a time with USB drivers. 1.73 and 1.82 worked flawless but 1.85 kept getting errors. Uninstalled drivers and installed htc sync and it worked. If these are the drivers you have installed then search for the naked adb drivers. One of the 2 might fix you up.
nugzo said:
Why do you want stock? Returning this one too? I had a hell of a time with USB drivers. 1.73 and 1.82 worked flawless but 1.85 kept getting errors. Uninstalled drivers and installed htc sync and it worked. If these are the drivers you have installed then search for the naked adb drivers. One of the 2 might fix you up.
Click to expand...
Click to collapse
Sorry, but I just wanted to say I love your avatar. Where did you get it?
Samsung infuse is an animal!!
nugzo said:
Why do you want stock? Returning this one too? I had a hell of a time with USB drivers. 1.73 and 1.82 worked flawless but 1.85 kept getting errors. Uninstalled drivers and installed htc sync and it worked. If these are the drivers you have installed then search for the naked adb drivers. One of the 2 might fix you up.
Click to expand...
Click to collapse
No not returning it. I just want to play with the 1.73 look at the partitions etc.
I installed HTC sync.
looks like going from 1.85 ruu to 1.73 might be working this time. I disabled HTC sync. Something I keep forgetting to do
Have you read the downgrade thread? It does require you to hex edit the mmcblk0p23 file.
nunyabiziz said:
Have you read the downgrade thread? It does require you to hex edit the mmcblk0p23 file.
Click to expand...
Click to collapse
not if you have superCID which I do have.
gunnyman said:
looks like going from 1.85 ruu to 1.73 might be working this time. I disabled HTC sync. Something I keep forgetting to do
Click to expand...
Click to collapse
spoke too soon error 140 again.
look here
http://forum.xda-developers.com/showthread.php?p=26509600.
from my HTC One X using xda premium
I just reread the thread again and I dont see where it said having super cid will excludes you from the hex editing the misc file. I may be not, if so sorry for the misdirection.
nunyabiziz said:
I just reread the thread again and I dont see where it said having super cid will excludes you from the hex editing the misc file. I may be not, if so sorry for the misdirection.
Click to expand...
Click to collapse
superCID is supposed to allow you to install any RUU isn't it?
gunnyman said:
superCID is supposed to allow you to install any RUU isn't it?
Click to expand...
Click to collapse
But there is another check that will fail without the hex edit.
nunyabiziz said:
But there is another check that will fail without the hex edit.
Click to expand...
Click to collapse
ok thanks. I'll try it tomorrow. Getting tired.
gunnyman said:
ok thanks. I'll try it tomorrow. Getting tired.
Click to expand...
Click to collapse
Any luck going to 1.82? I was able to get to that, but I haven't tried to go to 1.73.
Sent from my HTC One X using Tapatalk 2
droidiac13 said:
Any luck going to 1.82? I was able to get to that, but I haven't tried to go to 1.73.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Hadn't tried.
droidiac13 said:
Any luck going to 1.82? I was able to get to that, but I haven't tried to go to 1.73.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Same here. Just relocked and flashed from 1.85 to 1.82 without any problems. No hex edit just super CID. Haven't tried 1.73 though.
Sent from my HTC One X using xda premium
You doing this from fastboot or while the phone was booted into the OS?
Somehow R2 was appended to my software version number. I had previously initiated the RUU while booted up but this was blocking me from restoring as it thought I had a software version newer than the RUU. While in fastboot, no software version is detected and I'd imagine any RUU should work.
nunyabiziz said:
I just reread the thread again and I dont see where it said having super cid will excludes you from the hex editing the misc file. I may be not, if so sorry for the misdirection.
Click to expand...
Click to collapse
I have downgraded to 1.73 without hexedit. Supercid takes care of having to do that. Thats why its calld SUPER cid I think its a driver error. Have you tried the drivers from this thread? http://forum.xda-developers.com/showthread.php?t=1379875
I'm giving my phone to my dad and I need to return it back to stock, but I can't seem to find a tutorial/guide to get me back to stock?
Can anyone with experience point me in the right direction?
This is easy to do on Samsung phones lol, this is just my first time doing so on HTC phones. Thanks! :good:
relock the bootloader via command fastboot oem lock in fb. Then run ruu according to the firmware of your phone.
WhatTheAndroid? said:
relock the bootloader via command fastboot oem lock in fb. Then run ruu according to the firmware of your phone.
Click to expand...
Click to collapse
what is ruu? is this something i have to download?
sorry i'm such a noob
EDIT: Found out that ruu seems to be the firmware version or stock"rom" sorta. it's the executable correct?
afrojoc said:
what is ruu? is this something i have to download?
sorry i'm such a noob
EDIT: Found out that ruu seems to be the firmware version or stock"rom" sorta. it's the executable correct?
Click to expand...
Click to collapse
What software were you on before you rooted, 2.20. Because i think i have the 2.20 ruu version.
WhatTheAndroid? said:
What software were you on before you rooted, 2.20. Because i think i have the 2.20 ruu version.
Click to expand...
Click to collapse
2.20 I also used the newest root method if that matters.
htc_one_x_RUU_2.20.502.7_att_us_08022012
This should be the name of it. and this is the link i downloaded it from when i needed to ruu back to stock. If you have the all in one v 1.1 one x toolkit you should be able to lock bootloader from the command there and THEN run ruu:
this is if you are on att htc one x(evita)
Edit: link not working just go to my old thread and install ruu from the link there on post 19. http://forum.xda-developers.com/showthread.php?t=1956258&page=2
WhatTheAndroid? said:
htc_one_x_RUU_2.20.502.7_att_us_08022012
This should be the name of it. and this is the link i downloaded it from when i needed to ruu back to stock. If you have the all in one v 1.1 one x toolkit you should be able to lock bootloader from the command there and THEN run ruu:
this is if you are on att htc one x(evita)
Edit: link not working just go to my old thread and install ruu from the link there on post 19. http://forum.xda-developers.com/showthread.php?t=1956258&page=2
Click to expand...
Click to collapse
Ahh okay I see you actually do have experience xD thanks i found a link!
thank you very much man!:good:
As usual, my index thread has most anything you will ever need: http://forum.xda-developers.com/showthread.php?t=1671237
Specifically, link in Xs Magicals RUU collection under "Stock RUUs and Related" seems to be working fine.
redpoint73 said:
As usual, my index thread has most anything you will ever need: http://forum.xda-developers.com/showthread.php?t=1671237
Specifically, link in Xs Magicals RUU collection under "Stock RUUs and Related" seems to be working fine.
Click to expand...
Click to collapse
Okay last question I hope.. how exactly do i relock my bootloader using the toolkit? I can't seem to find the option. And i've searched for this too... :crying:
EDIT: FOUND A WAY!!
afrojoc said:
Okay last question I hope.. how exactly do i relock my bootloader using the toolkit? I can't seem to find the option. And i've searched for this too... :crying:
EDIT: FOUND A WAY!!
Click to expand...
Click to collapse
Did you get your phone back to stock ok?
WhatTheAndroid? said:
Did you get your phone back to stock ok?
Click to expand...
Click to collapse
Well i gotta charge it first.. doing all this exploring made my battery drop lol.
WhatTheAndroid? said:
Did you get your phone back to stock ok?
Click to expand...
Click to collapse
Worked perfectly. Thank you very much man!!
So after having Jellybean updated on my Telstra One XL I decided to much around with recoveries and custom ROMs to see if I could get them running. I realised that this was going to cause issues, but I was fine with mucking around with it.
I unlocked the phone and got a recovery installed and of course the touchscreen didn't work in recovery. So I mucked around with it and managed to get ROMs installed via manual boot.img flashing and manual ROM flashing via:
Code:
adb shell recovery --update_package=/sdcard/rom.zip
My test was with CM10 and it got up and running. The only issue is that touchscreen doesn't work. Which made any progression through the setup phase impossible
If anyone has any clues as to how to get this up and going again I'm all ears.
I tried to use JET to roll back the HBOOT and try to roll back the firmware, but the RUUs wanted none of it.
Thanks in advance,
Anthony
Did you also fix the version number on mmcblk0p23 before attempting an older RUU?
eg:
http://forum.xda-developers.com/showthread.php?t=1671135
twistedddx said:
Did you also fix the version number on mmcblk0p23 before attempting an older RUU?
eg:
http://forum.xda-developers.com/showthread.php?t=1671135
Click to expand...
Click to collapse
No I didn't, must've missed that. Thanks, I will try that.
Didn't work with any RUU either.
EDIT: Got the RUU installed, thank you very much. I was an idiot and forgot to relock my bootloader again
I would use twrp on the hoxl for recovery. Its not failed me yet
Sent from my HTC One XL using xda premium
Hooray first success story of a downgrade.
Was this 3.17 and down to what ruu?
DESERT.TECH said:
I would use twrp on the hoxl for recovery. Its not failed me yet
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Not really relevant.
twistedddx said:
Hooray first success story of a downgrade.
Was this 3.17 and down to what ruu?
Click to expand...
Click to collapse
RUU_Evita_UL_Telstra_WWE_1.81.841.1_R_Radio_0.17a.32.09.03_2_10.85.32.16L_release_259804_signed.exe
Not really a success though. Once it pushed through the RUU, it bricked the phone. No power LED, won't start etc.
Tried the unbricking process, but it won't work. Going to get it replaced now.
Antonioffaxii said:
Not really a success though. Once it pushed through the RUU, it bricked the phone. No power LED, won't start etc.
Click to expand...
Click to collapse
Dam!
Did you try Jet again to get back to hboot 1.09 a second time?
Does it allow you to RUU again or just nothing?
I would have tried a newer RUU also, like 2.42.
twistedddx said:
Dam!
Did you try Jet again to get back to hboot 1.09 a second time?
Does it allow you to RUU again or just nothing?
I would have tried a newer RUU also, like 2.42.
Click to expand...
Click to collapse
I couldn't restore it in anyway, I had work so I took it with me and had it replaced.
Now I have one that works again!