I just installed the VenomXL 3.2.6 on my HTC One X using TWRP 2.5.0.0. I am not 100% sure that I have S-Off, I rooted my phone right when the exploit for the "impossible" firmware was figured out a number of months ago. HBoot is showing 1.14.
I did factory wipe 3x before starting the installer. Then chose "wipe" in the installer. Everything installed quickly/correctly. After installing, I rebooted into fastboot and flashed the boot.img over with no issues.
Now when I try to boot, it'll boot loop at the initial white HTC-with-red-warning screen and then automatically boot into TWRP.
What can I do to make this ROM work?
Thanks
You can download twrp 2.3.3.1, check md5
flash twrp 2.3.3.1
fastboot erase cache
reboot to recovery, wipe cache, dalvik, system, factory reset.
flash rom, flash boot.img
Working.
Good Luck. By the way, if you were S-OFF, you would know.
exad said:
You can download twrp 2.3.3.1, check md5
flash twrp 2.3.3.1
fastboot erase cache
reboot to recovery, wipe cache, dalvik, system, factory reset.
flash rom, flash boot.img
Working.
Good Luck. By the way, if you were S-OFF, you would know.
Click to expand...
Click to collapse
Thank you for your advice! I've followed it as you listed and, unfortunately, my problem persists. After flashing fastboot flashing the boot.img at the end and restarting, it will hang at the white HTC-with-red-warning-text screen and then reboot into recovery.
Do you have any other suggestions?
I'm still searching that particular ROM thread looking for people with similar issues.
My next step is to try the next most popular ROM, whichever that is.
sappro said:
Thank you for your advice! I've followed it as you listed and, unfortunately, my problem persists. After flashing fastboot flashing the boot.img at the end and restarting, it will hang at the white HTC-with-red-warning-text screen and then reboot into recovery.
Do you have any other suggestions?
I'm still searching that particular ROM thread looking for people with similar issues.
My next step is to try the next most popular ROM, whichever that is.
Click to expand...
Click to collapse
the boot.img you are flashing is extracted from viperxl rom? viper xl should have the option to flash the boot.img for you so you don't even have to.
Otherwise i'd check MD5 of the Rom, either the file is bad or you're doing something wrong.
exad said:
the boot.img you are flashing is extracted from viperxl rom? viper xl should have the option to flash the boot.img for you so you don't even have to.
Otherwise i'd check MD5 of the Rom, either the file is bad or you're doing something wrong.
Click to expand...
Click to collapse
The MD5 on my flash drive of the downloaded ROM is incorrect, even though it was correct before moving to my flash drive. I will redownload and see if that solves the issue.
Thank you!
exad said:
the boot.img you are flashing is extracted from viperxl rom? viper xl should have the option to flash the boot.img for you so you don't even have to.
Otherwise i'd check MD5 of the Rom, either the file is bad or you're doing something wrong.
Click to expand...
Click to collapse
Wow, I've never had an MD5 problem before, but that appeared to have fixed it. Thanks very much for the suggestion!
SOLVED: The ZIP files were somehow subtly corrupted during transfer from computer to flash drive to phone. After checking the MD5 using http://forum.xda-developers.com/showthread.php?t=1939007 I was verify this. Using a different computer/browser, I downloaded the ROMs again and now the MD5 hashes correctly!
Cool glad you are up and going. Personally I like to download roms to phone then install with twrp . Also you probably know this but a nandriod backup is a must .
Sent from my HTC One X using xda premium
Related
I was running the ruu 1.7x with PA because I had a soft brick a few weeks ago, just last night I tried flashing King Cobra in TWRP. Upon rebooting it gave me trouble but I eventually got the phone to boot up all the way. Everything worked except and I couldn't call or text but I can receive them. I thought maybe installing the latest update would solve the problem but I'm still having the same issue. EVERYTHING got wiped no backs up no nothing, am I screwed?
Sent from my HTC One X using xda app-developers app
Check your apn settings and make sure your using the correct settings for your carrier.
Grnfinger said:
Check your apn settings and make sure your using the correct settings for your carrier.
Click to expand...
Click to collapse
I did that when I was running KC and now on the stock software, I thought it was because I was on 1.7x and flashed KC cause I didn't have this problem with PA, so I did the update ruu tool to 2.20 and the problem still persist :/
WOOOWWW.
I am the biggest herp that ever derped. I did not flash the FC.zip fix provided in the King Cobra thread instead I updated with the RUU tool and the problem still persists. So I suppose I have to wait for the amazing minds of XDA to figure out a way to root the HOX on 2.20 before I can root/unlock to flash this silly zip. Ohhhh woe is me.
droidnamedjakke said:
I am the biggest herp that ever derped. I did not flash the FC.zip fix provided in the King Cobra thread instead I updated with the RUU tool and the problem still persists. So I suppose I have to wait for the amazing minds of XDA to figure out a way to root the HOX on 2.20 before I can root/unlock to flash this silly zip. Ohhhh woe is me.
Click to expand...
Click to collapse
Since you already unlocked the phone with HTC dev unless you changed your cid before the ruu you can unlock again with the same token and install twrp and flash a rooted rom.
You will just need to flash the boot.img from fastboot before the rom
Sent from my HTC One XL using Forum Runner
droidnamedjakke said:
I am the biggest herp that ever derped. I did not flash the FC.zip fix provided in the King Cobra thread instead I updated with the RUU tool and the problem still persists. So I suppose I have to wait for the amazing minds of XDA to figure out a way to root the HOX on 2.20 before I can root/unlock to flash this silly zip. Ohhhh woe is me.
Click to expand...
Click to collapse
As long as you left your phone SuperCID, then you can reunlock and re-root.
I unlocked it once again and flashed KC back, but the .zip fix he provided isn't working. Any ideas fellas?
droidnamedjakke said:
I unlocked it once again and flashed KC back, but the .zip fix he provided isn't working. Any ideas fellas?
Click to expand...
Click to collapse
Try going in to recovery and clearing everything (cache, dalvik, factory reset, system) and reflash. Keep in mind if you are on 2.20, you have to flash the boot.img manually.
Butters619 said:
Try going in to recovery and clearing everything (cache, dalvik, factory reset, system) and reflash. Keep in mind if you are on 2.20, you have to flash the boot.img manually.
Click to expand...
Click to collapse
It didn't solve the problem I still can't flash the .zip fix nor is the issue gone. Should I try flashing a different Rom and see if that takes care of it?
flash newest twrp 2.2.2.0 in fastboot. also do a "fastboot erase cache" then "fastboot flash boot boot.img" using the boot.img from CleanROM 4.5. then wipe cache,dalvik,data,system,etc. even flash external after backing up everything. then mount usb copy CleanROM 4.5 to storage. then install selecting full wipe in aroma. then install cleanmods in the created storage folder. that will be the safest method to make sure your starting clean.
DvineLord said:
flash newest twrp 2.2.2.0 in fastboot. also do a "fastboot erase cache" then "fastboot flash boot boot.img" using the boot.img from CleanROM 4.5. then wipe cache,dalvik,data,system,etc. even flash external after backing up everything. then mount usb copy CleanROM 4.5 to storage. then install selecting full wipe in aroma. then install cleanmods in the created storage folder. that will be the safest method to make sure your starting clean.
Click to expand...
Click to collapse
I'll try this when I get home from work at 2:30, thanks for giving the advice. But what do you mean "even flash external"?
DvineLord said:
flash newest twrp 2.2.2.0 in fastboot. also do a "fastboot erase cache" then "fastboot flash boot boot.img" using the boot.img from CleanROM 4.5. then wipe cache,dalvik,data,system,etc. even flash external after backing up everything. then mount usb copy CleanROM 4.5 to storage. then install selecting full wipe in aroma. then install cleanmods in the created storage folder. that will be the safest method to make sure your starting clean.
Click to expand...
Click to collapse
I did a full wipe of everything and installed CleanROM but to no avail I'm still getting the error as listed before. I don't understand everything was wiped for my HOX why is it still doing this?
First, I have H-BOOT 1.09, and I am rooted, I have TWRP v3
Now, I had ViperROM 1.2.0 installed, and decided to install Trickdroid v7, and it failed. I thought it was weird, so I restarted the phone. It was just on the boot screen, and after rebooting into Recovery, I noticed that when I tried rebooting, it would say that no OS was installed.
I downloaded ViperROM 1.2.0 and checked the MD5 and it checked out. Thinking they might of fixed the Aroma full wipe, I ran it with a full wipe, and of course it didn't work. So, I rebooted into recovery, wiped Cache, Dalvik, Factory and System. Tried installing ViperROM again, this time with out the full wipe, it gets to 7% and then ask me to reboot. If I try rebooting, it tells me no OS is installed. Right now I am running CM10 but I don't want it. I want ViperROM.
I had this same issue before, but I was exactly sure what I did in order to get it to install. So now I am stumped, and I don't know how to use ADB.
If you use latest TWRP 2.3.x, it will not work. You need to go back to TWRP 2.2.2.0
cat2115 said:
If you use latest TWRP 2.3.x, it will not work. You need to go back to TWRP 2.2.2.0
Click to expand...
Click to collapse
I feel really stupid because I didn't check the last 30 pages of that topic, although it seems its because System is mounted, which I had absolutely no idea WTF that meant.
Does that mean that the latest TWRP is the reason why Trickdroid didn't install?
I could never get either to install using any version of TWRP and i'm on hboot 1.06. I always had to fastboot flash the boot.img first, clear caches. It's weird and no one involved could explain it...been flashing other ROMs fine via TWRP 2.3
Hgaara said:
I feel really stupid because I didn't check the last 30 pages of that topic, although it seems its because System is mounted, which I had absolutely no idea WTF that meant.
Does that mean that the latest TWRP is the reason why Trickdroid didn't install?
Click to expand...
Click to collapse
If you download gooManager from Play. it will install the latest TWRP. If you need TWRP 2.2.2.0, you can find it in ToolKit Rooting. Inside the folder there' s a TWRP 2.2.2.0
Use that img and do a fastboot
fastboot flash recovery TWRP.img
Click to expand...
Click to collapse
Hope this help you.
Or you can try
older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
Click to expand...
Click to collapse
at http://forum.xda-developers.com/showthread.php?t=1677670&highlight=twrp+recovery
below "CHANGELOG for 2.3.0.0:" you find a download link to "update-binary"
I upgraded to CM10 from the original OS and I am using the latest version to root my phone, I am using TWRP. Anyway, Everything worked fine, I rooted the phone, I upgraded to CM10. I want to go back to the original OS. I downloaded [ROM][8/3] - Stock Rooted AT&T 2.20.502.7 - Android 4.0.4 - Odex or De-Odex, I got the ODEX version, I flashed it to my phone but its just hangs at the HTC One X Splash screen with the red lettering. What am I missing here? I can get back into recovery and I backed up my old ROM just in case.
How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.
mgutierrez87 said:
How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.
Click to expand...
Click to collapse
It just shuts off and turns back on again, it basically loops. Did I download the wrong file maybe? Is there a specific ROM I need other than the one I mentioned earlier?
Boot into recovery and wipe your cache and dalvik cache again
mgutierrez87 said:
Boot into recovery and wipe your cache and dalvik cache again
Click to expand...
Click to collapse
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app
This was the ROM that worked when i did it.
http://forum.xda-developers.com/showthread.php?t=1872842
---------- Post added at 04:53 AM ---------- Previous post was at 04:46 AM ----------
Myrder said:
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
He mentioned in another thread that he did those steps. The only other thing I would try is to flash the boot.IMG from the ROM you want to use
I still want to keep my phone rooted. This wont kill the root right?
No the ROM posted above is stock rooted
But if you made a backup as you said in the first post why are you not just restoring the backup?
Sent from my Nocturnalized One XL using Forum Runner
Basically where I am right now. I downloaded the original OS, by following instructions, I have managed to delete my backed up rom of CM10 that i backed up earlier. I was able to FLASH the OS I wanted, I flashed the boot.img file using fastboot. I restarted the phone and now its just stuck on the HTC Quietly Brilliant screen with the red lettering at the bottom. It doesn't restart or anything, it just hangs there. What am I missing here guys? ):
I'm going to install cm10 right now them go back to stock rooted and see what's up with this
There's no issues going back and forth. You probably flashed a bad ROM
yea, your most likely just doing it wrong. you need to do a full wipe and flash boot.img
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.
What hboot are you on? If you separately flashed boot.img from CM10 via fastboot, you might need to again separately flash the boot.img from the stock ROM. Also remember that the procedure employed to root 2.20 is substantially different from the root procedure to root the previous build of stock. Not sure what software you rooted, or whether this would pose a problem, but it's a consideration.
Another option is to just restore to stock via RUU and re-unlock, re-root, if nothing else works. Getting stuck on HTC splash screen sounds like a boot.img issue. Good luck.
DvineLord said:
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.
Click to expand...
Click to collapse
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!
Did you fastboot flash boot boot.img?
Sent from my HOX running Cyanogenmod 10
redpoint73 said:
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!
Click to expand...
Click to collapse
im assuming the age of the stock rooted would have conflicts with the new twrp. i have had problems with roms not flashing with newest twrp. it is also a known problem since twrp 2.3.1.0 release.
I know the CM 10.1 nightly was experimental.
I flashed it, and it worked decently well enough.
What I failed to realize was that 10.1 flashes a new kernel on the phone, one that is incompatible with CM 10.0. I'm guessing the 4.2 base requires a new kernel.
So Fine, I've tried flashing the stock kernel on my phone, and then installing CM10, but no fish.
Any attempts I've made to change my kernel and then install CM 10 have resulted in my phone being stuck on the CM boot screen (the cyan circle animation)
Flashing CM10.1 nightly from twrp lets my phone boot up, because (i suppose) that rom installation just installs the compatible kernel again.
Can someone please help me figure out what I'm doing wrong with my kernel flashing?
taurius1 said:
I know the CM 10.1 nightly was experimental.
I flashed it, and it worked decently well enough.
What I failed to realize was that 10.1 flashes a new kernel on the phone, one that is incompatible with CM 10.0. I'm guessing the 4.2 base requires a new kernel.
So Fine, I've tried flashing the stock kernel on my phone, and then installing CM10, but no fish.
Any attempts I've made to change my kernel and then install CM 10 have resulted in my phone being stuck on the CM boot screen (the cyan circle animation)
Flashing CM10.1 nightly from twrp ets my phone boot up, because (i suppose) that rom installation just installs the compatible kernel again.
Can someone please help me figure out what I'm doing wrong with my kernel flashing?
Click to expand...
Click to collapse
What hboot r u on? You're full wiping right? And if you're on hboot 1.14 grab the boot.img our of the Rom zip you desire to flash and Fastboot flash it
a box of kittens said:
What hboot r u on? You're full wiping right? And if you're on hboot 1.14 grab the boot.img our of the Rom zip you desire to flash and Fastboot flash it
Click to expand...
Click to collapse
I'm on the 1.09 hboot. I haven't messed with my hboot ever. Should I be upgrading? I'll have to look it up.
I did try what you suggested.
I extracted the boot.img from CM10 stable for evita, flashed it via fastboot.
Then i rebooted into recovery, wiped my system, my cache, my dalvik cache, and did a factory reset.
Then I flashed CM 10.
After all this, still stuck on the cm boot animation. :3 I give it about 10 minutes before I decide its stuck. That is enough time, I think.
taurius1 said:
I'm on the 1.09 hboot. I haven't messed with my hboot ever. Should I be upgrading? I'll have to look it up.
I did try what you suggested.
I extracted the boot.img from CM10 stable for evita, flashed it via fastboot.
Then i rebooted into recovery, wiped my system, my cache, my dalvik cache, and did a factory reset.
Then I flashed CM 10.
After all this, still stuck on the cm boot animation. :3 I give it about 10 minutes before I decide its stuck. That is enough time, I think.
Click to expand...
Click to collapse
Ok no you want to stay on hboot 1.09 and redownload the latest cm10..and do these exact instructions
Wipe factory reset
System
Caches
Install Rom
Install gapps
I'm thinking you just had a bad download
a box of kittens said:
Ok no you want to stay on hboot 1.09 and redownload the latest cm10..and do these exact instructions
Wipe factory reset
System
Caches
Install Rom
Install gapps
I'm thinking you just had a bad download
Click to expand...
Click to collapse
I've done that. But just to be sure, I'm gonna try a fresh download once more. ^_^ Brb 10 minutes.
Curious what happened, as I think I may be having this same issue.
a box of kittens said:
Ok no you want to stay on hboot 1.09 and redownload the latest cm10..and do these exact instructions
Wipe factory reset
System
Caches
Install Rom
Install gapps
I'm thinking you just had a bad download
Click to expand...
Click to collapse
OOh that worked. Thanks a ton! ^_^
Probably was a bad download all three times I tried to download it before. :/ (I should probably buy a lottery ticket now :/ )
Now, Let me try installing my rooted stock rom. :3
Almost Same Problem
I have HTC One XL
-rooted
-unlocked
-bootloader unlocked
-hboot 1.14
-twrp recovery
I was also running the 10.1 expiremental (the first one). It was very buggy, so I tried out the newer experimental to see if the problems were fixed. The newer one was worse, so I decided to switch back to 10.0 nightly. I used fastboot to change the kernel to the one extracted from the 10.0 rom zip. I went to recovery and installed the 10.0 rom, but I DID NOT WIPE ANYTHING THE FIRST TIME. Either it slipped my mind, or I was thinking it wasn't necessary because I was still using a CM rom. The device would not boot, but instead of hanging on the cm animation screen, I'm stuck on the HTC logo screen. I went back to fastboot and did the kernel again and the phone automatically rebooted up correctly, however after a reboot i'm still stuck at the htc logo screen. It reminds me of tethered jailbreaks on iOS, lol. I may have to reflash the kernel every time I reboot. I tried stable, nightly, 10.1 nightly. no dice. any ideas?
lucasjohnsond said:
I have HTC One XL
-rooted
-unlocked
-bootloader unlocked
-hboot 1.14
-twrp recovery
I was also running the 10.1 expiremental (the first one). It was very buggy, so I tried out the newer experimental to see if the problems were fixed. The newer one was worse, so I decided to switch back to 10.0 nightly. I used fastboot to change the kernel to the one extracted from the 10.0 rom zip. I went to recovery and installed the 10.0 rom, but I DID NOT WIPE ANYTHING THE FIRST TIME. Either it slipped my mind, or I was thinking it wasn't necessary because I was still using a CM rom. The device would not boot, but instead of hanging on the cm animation screen, I'm stuck on the HTC logo screen. I went back to fastboot and did the kernel again and the phone automatically rebooted up correctly, however after a reboot i'm still stuck at the htc logo screen. It reminds me of tethered jailbreaks on iOS, lol. I may have to reflash the kernel every time I reboot. I tried stable, nightly, 10.1 nightly. no dice. any ideas?
Click to expand...
Click to collapse
Sounds like the best solution would be what I did, thanks to box of kittens.
Full wipe. (factory reset, system, cache)
Flash a download of CM to make sure you don't have a damaged copy.
taurius1 said:
Sounds like the best solution would be what I did, thanks to box of kittens.
Full wipe. (factory reset, system, cache)
Flash a download of CM to make sure you don't have a damaged copy.
Click to expand...
Click to collapse
Actually, I just remembered. If you're on the new hboot, you should be flashing the boot img through fastboot, and then installing the zip. Since you've been doing all that anyway, perhaps its time to just wipe everything and start over, step by step.
> download cm 10.0
> check md5 to make sure it's proper
> extract boot.img and flash it via fastboot
> reboot into recovery.
> wipe system, cache, dalvik cache, and factory reset
> transfer the rom and flash it via recovery
:/ I'm no expert here, but that's what I'd be doing now.
Hi guys
I got my one S two days ago, and in thursday ive read everything (as usual), did every single faq/tutorial and always got in the same end.. A dead device.
I don't know if I miss something or some "basic" knowing about it, i have a t-mobile one S and nothing wotks except runing the stock t-mobile update.
I'm coming from a long range nexus family (and i love sense, for sure), and i don't know what im doing wrong now.
And yeah, just in case, im runing a t-mobile stock, deodexed, rooted, init.d and optimized stock rom.
Thanks in advance.
can you list the steps?
I flash say CM10.1 like this:
1. download cm10.1 nightly zipfile from get.cm. Check md5sum
2. extract boot.img from above zip file.
3. copy zipfile to my sdcard
5.. boot into recovery ( I use TWRP )
6. install cm10.1 zip file
7. wipe cache and wipe dalvik cache
8. boot into bootloader
9. fastboot flash boot boot.img ( from you PC )
10. reboot and enjoy
My guess is you aren't doing 9). Indeed if you have S-OFF this step can be superfluous.
Three - that's how many posts I predict will remind you to post questions in the other forum
bluebenno said:
can you list the steps?
I flash say CM10.1 like this:
1. download cm10.1 nightly zipfile from get.cm. Check md5sum
2. extract boot.img from above zip file.
3. copy zipfile to my sdcard
5.. boot into recovery ( I use TWRP )
6. install cm10.1 zip file
7. wipe cache and wipe dalvik cache
8. boot into bootloader
9. fastboot flash boot boot.img ( from you PC )
10. reboot and enjoy
My guess is you aren't doing 9). Indeed if you have S-OFF this step can be superfluous.
Three - that's how many posts I predict will remind you to post questions in the other forum
Click to expand...
Click to collapse
Yes, all your steps listed, I've tried all this steps and got a bootloop, with any rom. That's why I make this thread, im starting to feel retarded.
Menelkir said:
Yes, all your steps listed, I've tried all this steps and got a bootloop, with any rom. That's why I make this thread, im starting to feel retarded.
Click to expand...
Click to collapse
Edit the title and remove Nooob!?!? for sure anyone jump in anyone if we missing something! And both my guesses where wrong
Firmware would be the next thing I'd look at - although CM10.1 is pretty tolerant. Please can you post all the text on your boot loader screen?
=> It is a S4 variant, right?
Do you get a success message when flashing the boot.img?
Was going to say..... We are talking S4?
Can't think what else can be wrong
Sent from my Liquid Smooth One S
CyanogenMod has NEVER worked on my HTC One S (S4), didn't matter how many times i wiped the system / cache / dalvik, didn't matter if i booted boot.img (S-ON), it just stayed on the splash screen.
Other ROMs worked though, an I am currently enjoying the hell out of my liquidsmooth ROM and OC kernel (bubba 3.6b). Maybe i just never let CM10 sit long enough...
But if you say that no ROMs work, are you sure you're not using an S3 device?
WCCobra said:
Do you get a success message when flashing the boot.img?
Click to expand...
Click to collapse
Yep
ATSPerson said:
Was going to say..... We are talking S4?
Can't think what else can be wrong
Sent from my Liquid Smooth One S
Click to expand...
Click to collapse
Yes.
Are you wiping system and data in addition to cache and dalvik?
Sent from my HTC One S using xda app
You say you end up with a bootloop, but are you giving the rom enough time to settle? The first boot can take a minutes to complete. I found this with CM when I first started flashing roms
Sent from my Liquid Smooth One S
i usually reboot one more time after initial boot
did you try reformatting sdcard, use a good formatter like sdformatter and do full format
Have you wiped system, cache and done a factory reset before flashing the ROM zip?
Sent from my HTC One S using xda app-developers app
Well I fixed. After a few tries I just format every single partition (even boot), and then flash the zip.