I have been reading and trying to return to stock for over a week, and nothing will work. I used HTCdev to unlock and I installed Jellytime, but now I want to go back to stock to sell it, and I can't get anything to work. It is S-On now, and I think thats why nothing works. I have Clockwork recovery, and the only rom I can get to flash is jellytime, nothing else works. I tried HTC RUU, and that gives me an unknown error. I've tried flashing several PD98IMG's, and they all fail also. I have also tried flashing the att stock rom via RUU and Clockwork recovery, that doesn't work either. Someone please help! Thanks!
tjmortenson said:
I have been reading and trying to return to stock for over a week, and nothing will work. I used HTCdev to unlock and I installed Jellytime, but now I want to go back to stock to sell it, and I can't get anything to work. It is S-On now, and I think thats why nothing works. I have Clockwork recovery, and the only rom I can get to flash is jellytime, nothing else works. I tried HTC RUU, and that gives me an unknown error. I've tried flashing several PD98IMG's, and they all fail also. I have also tried flashing the att stock rom via RUU and Clockwork recovery, that doesn't work either. Someone please help! Thanks!
Click to expand...
Click to collapse
Re lock bootloader. Place phone into fastboot and plug into PC. Run ruu from PC. May need HTC sync installed to avoid errors when running ruu. Also if your hboot is the newest version you will only be able to run the newest ruu from HTC.
Sent from my Motorola Droid RAZR MAXX HD using xda premium.
Gizmoe said:
Re lock bootloader. Place phone into fastboot and plug into PC. Run ruu from PC. May need HTC sync installed to avoid errors when running ruu. Also if your hboot is the newest version you will only be able to run the newest ruu from HTC.
Sent from my Motorola Droid RAZR MAXX HD using xda premium.
Click to expand...
Click to collapse
tjmortenson said:
I have been reading and trying to return to stock for over a week, and nothing will work. I used HTCdev to unlock and I installed Jellytime, but now I want to go back to stock to sell it, and I can't get anything to work. It is S-On now, and I think thats why nothing works. I have Clockwork recovery, and the only rom I can get to flash is jellytime, nothing else works. I tried HTC RUU, and that gives me an unknown error. I've tried flashing several PD98IMG's, and they all fail also. I have also tried flashing the att stock rom via RUU and Clockwork recovery, that doesn't work either. Someone please help! Thanks!
Click to expand...
Click to collapse
In addition to what Gizmoe says, you need To flash an Inspire RUU as you are S-ON. Other RUU's will fail due to cid signature
Thanks, I finally got the RUU to flash, I didn't realize that I had to relock the bootloader, thats why it wasn't working.
Related
followed steps correctly usb debugging on..check, tried in fastboot....check, tried both t-mobile U.S. RUUs and even tried downloading each from different sources...check, restored stock recovery and relocked bootloader I also made sure htc drivers are properly installed. WTF I dont know whats going on im on stock rom just rooted, my hboot is 1.009, can anyone give me a hand? I have to return my phone for a warranty exchange the older ruu gives me the error 155(tried fasboot usb method) and the 1.84 ruu acts as if it's working hell it even reboots my phone and says rom update successfully installed in ruu prompt but when I boot into bootloader it still has tampered? also I can tell its not working properly because under the white HTC logo/w black screen the little green installation bar is not displayed.....sorry for the run on sentencing....just trying to remember everything. (video) http://youtu.be/Y8qIt-tYiwQ
can anyone provide a link for stock recovery.img; got one from modaco, but not sure if it's the correct one ? PLZNTHNX
kirkcody said:
followed steps correctly usb debugging on..check, tried in fastboot....check, tried both t-mobile U.S. RUUs and even tried downloading each from different sources...check, restored stock recovery and relocked bootloader I also made sure htc drivers are properly installed. WTF I dont know whats going on im on stock rom just rooted, my hboot is 1.009, can anyone give me a hand? I have to return my phone for a warranty exchange the older ruu gives me the error 155(tried fasboot usb method) and the 1.84 ruu acts as if it's working hell it even reboots my phone and says rom update successfully installed in ruu prompt but when I boot into bootloader it still has tampered? also I can tell its not working properly because under the white HTC logo/w black screen the little green installation bar is not displayed.....sorry for the run on sentencing....just trying to remember everything. (video) http://youtu.be/Y8qIt-tYiwQ
Click to expand...
Click to collapse
That's a tough one to nail down. Below is the stock recovery from the 1.84 t-mobile OTA. Maybe flash that and try the clear storage option.
Also, you might try doing the the Mainver Fix in the all in one tool kit. It's an option in the box in the lower right hand corner.
https://dl.dropbox.com/s/g4r0ryvjy6oce9k/recovery.img?dl=1
Thankyou my friend ill give it a go
unfortunately that didn't work either...i don't know why this wont work for me
kirkcody said:
unfortunately that didn't work either...i don't know why this wont work for me
Click to expand...
Click to collapse
This same thing happened to me at some point. I would suggest just starting over and redoing all the steps.
0. Flash original radio
1. Flash stock recovery
2. Use stock recovery "clear storage" option
3. Factory reset.
4. Enable usb debugging
5. Uninstall usb drivers from your computer
6. Reinstall HTC USB driver
7. Lock bootloader
8. Switch usb cable
9. Run RUU.
If that doesn't work use a hammer and smash the thing =)
Actually instead of using a hammer I would change to super cid and use a different RUU that had the same hboot as the one your on.
Extract the Rom.zip from the RUU, rename to PJ40IMG.zip, place on root of SD card.
Sent from my locked, tampered ville
@usaf22 really? Did that method work for you?(thought it may not work because we don't have s-off) Did it also remove the tampered and relocked banners? Thanks for both of you guys help will give it a go.
(Edit Hboot wont detect the PJ40IMG.zip )
usaff22 said:
Extract the Rom.zip from the RUU, rename to PJ40IMG.zip, place on root of SD card.
Sent from my locked, tampered ville
Click to expand...
Click to collapse
No that won't work. Has it ever worked on the One S?
Didn't work Hboot didn't detect PJIMG.zip :crying:
kirkcody said:
Didn't work Hboot didn't detect PJIMG.zip :crying:
Click to expand...
Click to collapse
Did you try all this?
0. Flash original radio
1. Flash stock recovery
2. Use stock recovery "clear storage" option
3. Factory reset.
4. Enable usb debugging
5. Uninstall usb drivers from your computer
6. Reinstall HTC USB driver
7. Lock bootloader
8. Switch usb cable
9. Run RUU.
kirkcody said:
can anyone provide a link for stock recovery.img; got one from modaco, but not sure if it's the correct one ? PLZNTHNX
Click to expand...
Click to collapse
link no good-deleted
I have this exact same problem. The recovery cannot be flashed. I get a signature failed. I managed to download the the recovery just fine though. I need to flash the stock recovery so that I can do that latest update, but now I can't even enter the recovery. I get a security warning message next to Relocked everytime I try to get in... Awesome.
PS: The phone I already tried the RUU and I got a 155. Because you can only downgrade if you are S-OFF. So... What are we supposed to do now..?
Fixter said:
I have this exact same problem. The recovery cannot be flashed. I get a signature failed. I managed to download the the recovery just fine though. I need to flash the stock recovery so that I can do that latest update, but now I can't even enter the recovery. I get a security warning message next to Relocked everytime I try to get in... Awesome.
PS: The phone I already tried the RUU and I got a 155. Because you can only downgrade if you are S-OFF. So... What are we supposed to do now..?
Click to expand...
Click to collapse
I'm going to assume that by now you have taken off the phone everything you wanted to back up. You flashed the stock recovery onto the phone right? And now your bootloader is relocked?
If so do this:
enter fastboot
then select the bootloader option.
clear storage
factory reset
select fastboot again.
Run the RUU
dc211 said:
I'm going to assume that by now you have taken off the phone everything you wanted to back up. You flashed the stock recovery onto the phone right? And now your bootloader is relocked?
If so do this:
enter fastboot
then select the bootloader option.
clear storage
factory reset
select fastboot again.
Run the RUU
Click to expand...
Click to collapse
I got it working guys, but I know why. I was using the incorrect RUU. The link said it was the one for 1.83 but it was for the 1.5 version. I download it again and sure enough it's the 1.83 one. I guess I'm back to work now.
One question and this may save a big headache lol... did you LOCK your bootloader back? I had a couple RUU's that didn't work for me either, but I didn't follow the step of locking the bootloader I was just trying to flash over. Once I relocked I was good to go.
Thanks everyone yes I relocked the bootloader, hey @ dc211 can you provide a link for a successful RUU that you have used...plznthnx
kirkcody said:
Thanks everyone yes I relocked the bootloader, hey @ dc211 can you provide a link for a successful RUU that you have used...plznthnx
Click to expand...
Click to collapse
Your problem is that there is only 1 RUU you can use. Only 2 exist for T-mobile US and one you can't use because the hboot is lower then yours. But you're kinda lucky that a new OTA came out today. So a newer T-mobile US RUU should be out in a few days, that's normally how long it takes football to get them.
Here's a link to eh 1.83 RUU that should be fast. https://dl.dropbox.com/u/76257867/RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe
Our you can try to get the OTA. You should be able to see it now if you check for software updates but it should fail to install. I saw you're using the 1.06es radio. You'd have to go back to the original radio, recovery, lock the booloader and factory reset. For it to work.
I know you should be able to get it working I was stuck where you're at but my Hboot also said "Security Warning" and RUU's & OTA's wouldn't run which I really haven't seen anyone else get.
OK.. here is the deal: HTC One S, T-MO, flashed recovery (TWRP), NO ROM would work in the WiFi dept. I tried flashing the radio and no matter what I couldnt get it to flash the 1.5 or 1.84 radio. TWRP would take forever and say it was complete, but the radio version still said 1.04 (or something) in hboot.
Also, I tried going back to a Stock Tmo RUU and it would ALWAYS fail at the signature part of the install EVEN THOUGH I relocked my bootloader.
SO- I unlocked my bootloader, I flashed CWM. Works like a charm.. or so it seems. I flashed the radio and it will only boot into CWM. I can flash a ROM but it still only boots into CWM. I cant even get into fastboot. This sucks.
Ideas anyone?
What happens if you do adb reboot bootloader from your computer while the phone is in CWM?
It reboots, the screen flickers for a millisecond or so (I am sure its probably trying to load hboot and gives some type of error so fast that I can't see) and then it goes to CWM. I am thinking about flashing it back to team win recovery...
mbolden said:
OK.. here is the deal: HTC One S, T-MO, flashed recovery (TWRP), NO ROM would work in the WiFi dept. I tried flashing the radio and no matter what I couldnt get it to flash the 1.5 or 1.84 radio. TWRP would take forever and say it was complete, but the radio version still said 1.04 (or something) in hboot.
Also, I tried going back to a Stock Tmo RUU and it would ALWAYS fail at the signature part of the install EVEN THOUGH I relocked my bootloader.
SO- I unlocked my bootloader, I flashed CWM. Works like a charm.. or so it seems. I flashed the radio and it will only boot into CWM. I can flash a ROM but it still only boots into CWM. I cant even get into fastboot. This sucks.
Ideas anyone?
Click to expand...
Click to collapse
mbolden said:
It reboots, the screen flickers for a millisecond or so (I am sure its probably trying to load hboot and gives some type of error so fast that I can't see) and then it goes to CWM. I am thinking about flashing it back to team win recovery...
Click to expand...
Click to collapse
Try flashing the boot.img thats compatible with your ROM. As for going back to stock try this http://forum.xda-developers.com/showthread.php?t=1927939 If you're on Hboot 1.14 then the T-Mo RUU's wont work for you. I had that problem.
antny said:
Try flashing the boot.img thats compatible with your ROM. As for going back to stock try this http://forum.xda-developers.com/showthread.php?t=1927939 If you're on Hboot 1.14 then the T-Mo RUU's wont work for you. I had that problem.
Click to expand...
Click to collapse
OK.. I thought about that.. but my question is: How can I flash a boot.img if I cant get into fastboot? I installed the trickdroid ROM and I have the boot.img from the zip. I DID try to go back to stock (when I could still access everything pretty easily), but It got stuck on the signature part of the RUU. I went back to trickdroid and all was well sans the WiFi not working.
Can I flash a boot.img via ADB since that is the only thing really working right now?
Thanks
-M
If you still need help...
I'm sure you guys have figured this out by now, but I Solved a problem very similar to this one in my Thread. I was able to return to Stock while still being Rooted.
I decided to downgrade to 1.85 for a fresh start after downgrading hboot to 1.09.000. 1.85, 1.73 RUUs failed and im trying 2.20 as we speak :// if this fails what are mmy options?
thanks
Did you relock the bootloader?
Sent from my HTC One XL using xda app-developers app
RUU's still fail after Jet to 1.09 due to version reported on mmcblk0p23.
Fix here:
http://forum.xda-developers.com/showthread.php?t=1671135
Note one user reported that going from 3.17 back to 1.81 ended in a bricked phone.
After Jet to 1.09 and altering mmcblk0p23 version, RUU accepted flashing, but bricked phone.
area51avenger said:
Did you relock the bootloader?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
yes
twistedddx said:
RUU's still fail after Jet to 1.09 due to version reported on mmcblk0p23.
Fix here:
http://forum.xda-developers.com/showthread.php?t=1671135
Note one user reported that going from 3.17 back to 1.81 ended in a bricked phone.
After Jet to 1.09 and altering mmcblk0p23 version, RUU accepted flashing, but bricked phone.
Click to expand...
Click to collapse
I did this and I keep getting error 140- per this I am stuck in bl and I cant get adb
anyone? im in need of desperate help..
You don't need to run an ruu.... you downgraded your boot loader so just go on to flashing ROMs
You can flash the old radios and you should be set
No reason to put yourself through all this trouble
Sent from my One X using Tapatalk 2
superchilpil said:
You don't need to run an ruu.... you downgraded your boot loader so just go on to flashing ROMs
You can flash the old radios and you should be set
No reason to put yourself through all this trouble
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
that's the problem, I relocked the BL, so now m stuck in fastboot with a locked boot loader any way I could get to adb so I can re unlock it?
Kole_Ackerson said:
that's the problem, I relocked the BL, so now m stuck in fastboot with a locked boot loader any way I could get to adb so I can re unlock it?
Click to expand...
Click to collapse
If you still have your unlock token
Fastboot flash unlocktoken unlocktoken.bin
Replace unlocktoken.bin with the location of your old unlock token
If you don't have it go through the steps on HTC dev to get a new one. You don't need to boot up the phone, just need fastboot
Sent from my One X using Tapatalk 2
superchilpil said:
If you still have your unlock token
Fastboot flash unlocktoken unlocktoken.bin
Replace unlocktoken.bin with the location of your old unlock token
If you don't have it go through the steps on HTC dev to get a new one. You don't need to boot up the phone, just need fastboot
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
ok, I got the unlock token but its hanging on sending (0kb)
Kole_Ackerson said:
ok, I got the unlock token but its hanging on sending (0kb)
Click to expand...
Click to collapse
Make sure you're in fastboot not hboot
If that doesn't work reset your computer to make sure not programs are interfering with it
Sent from my One X using Tapatalk 2
it is in fastboot usb so ill reset my comp.
If it fails again, try running
Fastboot devices
To see if your device is showing up
Sent from my One X using Tapatalk 2
superchilpil said:
If it fails again, try running
Fastboot devices
To see if your device is showing up
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
wow,i got it. it was my usb port... and ive been in 1.14 for so long I forgot that I can just unlock with 1.09... ill be buuying you a beer when I get paid.
Kole_Ackerson said:
wow,i got it. it was my usb port... and ive been in 1.14 for so long I forgot that I can just unlock with 1.09... ill be buuying you a beer when I get paid.
Click to expand...
Click to collapse
Nah don't worry about it!
Just helping out where I can
Sent from my One X using Tapatalk 2
Can only boot to bootloader and all RUU failed
I am in a bit of trouble at the moment. I will try to describe what I have done to end up where I am now.
I have a Telstra HTC One XL. Recently upgraded an already unlocked, rooted HOXL to JB using the OTA update (big mistake I know now). This upgraded the hboot to 2.14 and software to 3.17.8xxx.
Spent a lot of time trying to re-root. TWRP didn't work (no touch response). So I eventually found the Interim CWM Recovery (no touch) by Modaco. This seemed to work well and I managed to root the phone.
Then i followed the instructions to flash to KingBeatZ 1.2.0 ROM. Booted fine but had no touch response too.
So I wiped KingBeatZ 1.2.0 and went for the nightly CM10. Again, booted fine but no touch response.
OK, so I figured I should just go back to my restored data. Tried that but apparently no restore data (didn't realise a wipe wiped the restore data as well, what is the point of that?)
So I decided to wipe CM10 to try flashing the Stock Rooted Telstra ROM by pablo11. This wipe however seems to have wiped incorrectly and this is where my real problem begins. I can now only boot to BL and Recovery. I cannot mount the sdcard so I have no way of pushing ROMS to my phone. I have tried a Telstra RUU and the latest Asia one. About to try the 1.89 Telstra RUU but I don't think that will make any difference. The setups do not detect an existing version on my phone, and all fail with Error 155. I have read that this error generally occurs due to unlocked bootloader so I have already relocked it.
I do not know what I should do now to restore any functionality to my HOXL. Any help would be greatly appreciated.
o0okiato0o said:
So I decided to wipe CM10 to try flashing the Stock Rooted Telstra ROM by pablo11. This wipe however seems to have wiped incorrectly and this is where my real problem begins. I can now only boot to BL and Recovery. I cannot mount the sdcard so I have no way of pushing ROMS to my phone. I have tried a Telstra RUU and the latest Asia one. About to try the 1.89 Telstra RUU but I don't think that will make any difference. The setups do not detect an existing version on my phone, and all fail with Error 155. I have read that this error generally occurs due to unlocked bootloader so I have already relocked it.
Click to expand...
Click to collapse
You can't run the RUU for a different carrier (CID), and you can't run an RUU for an older version. So neither 1.89 Telstra or an Asia RUU will work. You may be stuck waiting for the 3.17 RUU (don't think its been posted yet?).
You might also be able to make your own RUU by sticking the ROM in the Development forum in an RUU package. I don't know the specifics, and haven't done it myself. But I think it was done for Rogers, which never had a proper RUU package. So others might be able to advise you better on this.
redpoint73 said:
You can't run the RUU for a different carrier (CID), and you can't run an RUU for an older version. So neither 1.89 Telstra or an Asia RUU will work. You may be stuck waiting for the 3.17 RUU (don't think its been posted yet?).
You might also be able to make your own RUU by sticking the ROM in the Development forum in an RUU package. I don't know the specifics, and haven't done it myself. But I think it was done for Rogers, which never had a proper RUU package. So others might be able to advise you better on this.
Click to expand...
Click to collapse
You would need the .img files EX: system.img boot.img
Since our ROMs aren't packaged that way it won't work.
There's a way to create the system.img but its beyond me, and I do believe if it isn't signed it will fail
The only thing you can flash in hboot by ruu without s-off without being signed would be a boot.img
I would suggest trying to flash a stock ROM and a different kernel, or waiting for the ruu
Sent from my One X using Tapatalk 2
superchilpil said:
You would need the .img files EX: system.img boot.img
Since our ROMs aren't packaged that way it won't work.
There's a way to create the system.img but its beyond me, and I do believe if it isn't signed it will fail
The only thing you can flash in hboot by ruu without s-off without being signed would be a boot.img
I would suggest trying to flash a stock ROM and a different kernel, or waiting for the ruu
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Could you elaborate on the different kernel bit? I have just tried flashing a stock rom via the fastboot flash zip rom.zip method, but it fails the hboot check. Cheers
o0okiato0o said:
Could you elaborate on the different kernel bit? I have just tried flashing a stock rom via the fastboot flash zip rom.zip method, but it fails the hboot check. Cheers
Click to expand...
Click to collapse
Take a stock ROM and pull out the boot.img
And fastboot flash boot boot.img just to make sure it flashes
Then flash the ROM in recovery
Sent from my One X using Tapatalk 2
Hi everyone,
This is my very first post and I'll admit I am a NOOB.
As I've searched XDA and Google for my questions, I am really at a loss and thought I would pose my question(s) to the community.
I have a Rogers HTC One X(Evita) running CM 10.0, I am currently S-ON, with TWERP 2.3.1
I would like to install the latest CM but it would seem my HBOOT (1.11) needs to be upgraded.
My first question is if my CID is Roger001 is this similar to being SuperCID?
If so, which firmware is recommended? Which is the latest HBOOT I should upgrade to?
I guess this brings me to my next question, what exactly do I need to be able to upgrade my HBOOT?
I've seen a few walkthroughs but none mention Roger001 as CID and I'd rather not risk bricking my phone.
If you need any other information, please let me know.
Any assistance is greatly appreciated.
You definitely need to update your phone in order to flash the latest cm ROM. But, with your phone in its current state you'll brick it. You don't have SuperCID (11111111), you'll definitely need to get that first, then get s-off, then you can RUU up to the latest. Links to everything you need are in this thread.
Sent from my Evita
Thanks Tim.
I'll give that a whirl and let you know how it turns out.
Another silly question, what exactly is RUU?
Sent from my One X using xda app-developers app
RUU stands for ROM Update Utility. It basically takes your phone back to being completely stock, including recovery. The beauty of being s-off when you run an RUU is the s-off status survives the process, and so will your unlocked bootloader. So all you need to do when it's finished is flash TWRP again via fastboot, then flash your ROM via TWRP.
Sent from my Evita
Ahh
That makes perfect sense!
If I wanted to stay stock, I could?
Sent from my One X using xda app-developers app
Yeah there's nothing stopping you. Then if you change your mind it's as simple as following the steps I mentioned before.
Sent from my Evita
I haven't had a chance to try anything as of yet but I've been doing some reading, could I use the One X Att all-in-one kit 3.0.1 to obtain SuperCID as well S-Off?
I tried another apparently popular program yesterday but it didn't work, as my CID is still Roger001.
Thanks!
Sent from my One X using xda app-developers app
Yeah you might as well try anything you can to get it done.
Sent from my Evita
Yes!
timmaaa said:
Yeah you might as well try anything you can to get it done.
Sent from my Evita
Click to expand...
Click to collapse
Hey timmaa,
Just wanted to say thanks for the help!
I managed to get CID 11111111, as well as S-OFF.
I've just relocked and I am currently downloading the Rogers stock RUU, with that comes HBoot 2.14 and the latest CM!
Thanks again:good::laugh:
Spoke too soon.. :S
asarrecchia said:
Hey timmaa,
Just wanted to say thanks for the help!
I managed to get CID 11111111, as well as S-OFF.
I've just relocked and I am currently downloading the Rogers stock RUU, with that comes HBoot 2.14 and the latest CM!
Thanks again:good::laugh:
Click to expand...
Click to collapse
So, I flashed that latest Rogers RUU using ARUWizard, everything looked to be okay, as now I am now on H-Boot 2.14.
However, I cant boot into anything..
For some reason, when it tries to boot up it shows the CyanogenMod logo when loading but nothing.
Windows recognizes my phone and tries to install new drivers but fails.
I can boot into the bootloader but when I hit recover, the screen goes black and then after awhile a red ! with a phone beneath it shows up.
Any ideas anyone?
asarrecchia said:
So, I flashed that latest Rogers RUU using ARUWizard, everything looked to be okay, as now I am now on H-Boot 2.14.
However, I cant boot into anything..
For some reason, when it tries to boot up it shows the CyanogenMod logo when loading but nothing.
Windows recognizes my phone and tries to install new drivers but fails.
I can boot into the bootloader but when I hit recover, the screen goes black and then after awhile a red ! with a phone beneath it shows up.
Any ideas anyone?
Click to expand...
Click to collapse
Ok, firstly you didn't need to relock your bootloader to run the RUU because you have s-off. And what exactly is aruwizard? And how did you flash CM after you ran the RUU?
Sent from my Evita
timmaaa said:
Ok, firstly you didn't need to relock your bootloader to run the RUU because you have s-off. And what exactly is aruwizard? And how did you flash CM after you ran the RUU?
Sent from my Evita
Click to expand...
Click to collapse
I followed the steps from the link you gave me, under the RUU section, as there was a guide on how to install an RUU for Rogers HTC One X.
It said to relock the phone, so, I did.
ARWizard was part of the guide.
The weird thing is, I didn't flash CM, I flashed the Rogers RUU, so, I'm not even sure how CM10 is even on my phone.
I can get to the Bootloader but I can't launch TWERP and my windows PC now doesn't recognize my phone, it says installing drivers but never does. I had HTC Sync installed in hopes that it would help, it didn't.
Is my only option to do a Factory Reset in Hboot? I've read ill lose all my info on the SD card.
Thanks
Which RUU did you run? Something has gone wrong.
Sent from my Evita
timmaaa said:
Which RUU did you run? Something has gone wrong.
Sent from my Evita
Click to expand...
Click to collapse
I followed the steps in the below thread to help me flash the RUU
http://forum.xda-developers.com/showthread.php?t=1658929&nocache=1
I went to this site to get the Stock image:
http://forum.xda-developers.com/showthread.php?p=37227608
It's 3.17.631.2
OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.3 2.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl 6j.zip
I really do appreciate the help, by the way.
I'm not familiar with that method, but it seems to me that it doesn't do a full RUU. And evidently it hasn't because you still have cm on your phone. What hboot version does your phone list in bootloader now? You could just run the at&t 3.18 RUU which will do the whole job. You're s-off so it should be fine.
Sent from my Evita
timmaaa said:
I'm not familiar with that method, but it seems to me that it doesn't do a full RUU. And evidently it hasn't because you still have cm on your phone. What hboot version does your phone list in bootloader now? You could just run the at&t 3.18 RUU which will do the whole job. You're s-off so it should be fine.
Sent from my Evita
Click to expand...
Click to collapse
I am 2.14 HBOOT and S-off.
The problem is that while my Windows PC recognizes my phone, it doesnt load the drivers and therefore, I cant send any ADB commands.
I am not even able to go into TWERP.
How will I be able to run the AT&T if I cant push any ADB commands from my PC?
You don't need any adb commands to run an RUU, but you do need the pc to recognize the phone. I'd try uninstalling all drivers, then installing them again to see if it helps.
Sent from my Evita
Ota is not the same as aruwizard zip. Aru zip is exactly the same as Rom.zip you find inside ruu files, evita ones get the name pj83img.
Not sure why everyone thinks ota is ruu, nowhere is it refered to as being the same thing.
Maybe the firmware.zip in the ota managed to flash though hence your hboot and other firmware was upgraded.
If you follow the "or" method for flashing the zip it actually should work. The better correct answer is once s-off to download/install the latest ruu available that you want and ota up from there.
twistedddx said:
Ota is not the same as aruwizard zip. Aru zip is exactly the same as Rom.zip you find inside ruu files.
Not sure why everyone thinks ota is ruu, nowhere is it refered to as being the same thing.
Maybe the firmware.zip in the ota managed to flash though hence your hboot and other firmware was upgraded.
Click to expand...
Click to collapse
That's what I thought, but if he has used this aru zip, it's had the opposite effect. He now has the upgraded hboot but the previous ROM is still intact.
Sent from my Evita
timmaaa said:
That's what I thought, but if he has used this aru zip, it's had the opposite effect. He now has the upgraded hboot but the previous ROM is still intact.
Sent from my Evita
Click to expand...
Click to collapse
Thanks guys.
I'll try uninstalling the phone drivers and reinstall them, hopefully, it'll allow my PC to see my phone.
Worse case scenario, if my computer doesn't load the drivers for my phone, what are my options?
What if I select factory reset from HBOOT?
I decided to update my Dev unlocked Sensation to ICS, but had forgotten it was probably still on a Gingerbread radio. Now I have no working rom, and for some reason I am unable to flash the original rom (RUU) via the SD card method (PG58IMG).
My CID is HTC__E11 and therefor european roms from RUU should work, but I get the following error message when trying the sd card flash: wrong zipped image. In other cases it wont go further than parsing.
When i try to flash the RUU in ruu mode on the phone I get the following error: 99 unknown fail.
Unfortunately I cannot go back to the rom I was on before, since I dont have it anymore.
So the only thing I have now is TWRP recovery 2.6.3 and unlocked HBOOT 1.27.
Furthermore I am unable to see what my current radio firmware is. I want to flash a jellybean rom.
Does anyone know what to do?
MAsterokki said:
I decided to update my Dev unlocked Sensation to ICS, but had forgotten it was probably still on a Gingerbread radio. Now I have no working rom, and for some reason I am unable to flash the original rom (RUU) via the SD card method (PG58IMG).
My CID is HTC__E11 and therefor european roms from RUU should work, but I get the following error message when trying the sd card flash: wrong zipped image. In other cases it wont go further than parsing.
When i try to flash the RUU in ruu mode on the phone I get the following error: 99 unknown fail.
Unfortunately I cannot go back to the rom I was on before, since I dont have it anymore.
So the only thing I have now is TWRP recovery 2.6.3 and unlocked HBOOT 1.27.
Furthermore I am unable to see what my current radio firmware is. I want to flash a jellybean rom.
Does anyone know what to do?
Click to expand...
Click to collapse
ok would i be correct in thinking that you are s-on? how exactly did you upgrade from gingerbread to ics and have you tried formatting all partitions from twrp?
heavy_metal_man said:
ok would i be correct in thinking that you are s-on? how exactly did you upgrade from gingerbread to ics and have you tried formatting all partitions from twrp?
Click to expand...
Click to collapse
Yes I am S-ON. I did try formatting all partitions from twrp, that didnt help. I also tried cwm, but that didnt help either.
My radio was finally displayed by HBOOT, it is: 11.29A.3504.18_M. I believe this is a ICS radio, so there should be no problem here. Unfortunately i cannot find the RUU that corresponds to that radio and trying to flash another ruu wont work.
To go to ICS I just installed the latest CM11 from Sultan, which works on my other sensation (which is S-OFF). I have also tried other roms, but they all wont boot for some weird reason. For every rom I do a full wipe.
MAsterokki said:
Yes I am S-ON. I did try formatting all partitions from twrp, that didnt help. I also tried cwm, but that didnt help either.
My radio was finally displayed by HBOOT, it is: 11.29A.3504.18_M. I believe this is a ICS radio, so there should be no problem here. Unfortunately i cannot find the RUU that corresponds to that radio and trying to flash another ruu wont work.
To go to ICS I just installed the latest CM11 from Sultan, which works on my other sensation (which is S-OFF). I have also tried other roms, but they all wont boot for some weird reason. For every rom I do a full wipe.
Click to expand...
Click to collapse
If your s-on you need to flash the boot.IMG of your rom from fastboot straight after flashing your rom from recovery pal. But I recommend installing 4ext recovery and enabling its "smart flash" feature and this will do it for you try this and check back pal.
Sent from my Nexus 7 using Tapatalk
heavy_metal_man said:
If your s-on you need to flash the boot.IMG of your rom from fastboot straight after flashing your rom from recovery pal. But I recommend installing 4ext recovery and enabling its "smart flash" feature and this will do it for you try this and check back pal.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Lol I have been doing this for so long with a S-OFF device that I totally forgot about that! Thank you so much, sorry for my stupidity haha. Still weird that I cannot flash RUU though...
MAsterokki said:
Lol I have been doing this for so long with a S-OFF device that I totally forgot about that! Thank you so much, sorry for my stupidity haha. Still weird that I cannot flash RUU though...
Click to expand...
Click to collapse
Its cool pal it is, but then again ruus won't flash unless your bootloader is relocked
Sent from my Nexus 7 using Tapatalk