Database Info

Flashing ROMs on MT4GS with TWRP

Sorry for the noob question, but this isn't my phone. I'm trying to flash ROMs on my buddy's Doubleshot using TWRP. I use this recovery on my Hercules every day, so I'm very familiar with it. I try to flash using the standard procedure (wipe, install zip, reboot) and when I reboot, it just hangs. I tried wiping cache and it still hangs. Is there something else I could have missed? I've tried several different ROMs.

Is he S-On? If so you will need to fastboot flash the boot.img!
::Respect::

CoNsPiRiSiZe said:
Is he S-On? If so you will need to fastboot flash the boot.img!
::Respect::
Click to expand...
Click to collapse
So even if I already have a custom recovery installed, I still have to install via fastboot if it's S-ON? Actually, I think I may have seen that somewhere...I may have more reading to do.
EDIT: Yes, I found it. No more replies needed (for now!)

Pls can anyone help me with link for superwipe script for mt4gs

4th post under wipes
http://forum.xda-developers.com/showthread.php?p=31338925
Be sure to thanks blue for creating them and weekends for hosting his lost projects
Sent from my Nexus 7 using XDA Premium 4 mobile app

Problems After S-Off

I have an AT&T One XL and have had problems recently. I unlocked my bootloader last year on the 2.20 firmware, which is how the phone came. I was able to flash ROMs no problem. About 3 weeks ago I decided to go S-Off with the whole thing. The S-Off was successful, I immediately flashed a new splashscreen and it is confirmed in bootloader that I am S-off. Last week I tried to flash the stable CM10 build, but it was unsuccessful. I found that the only ROMs I am able to flash are Sense ROMs 4.1.1 and above, or AOSP ROMs that are 4.2.x or above. I am on hboot 1.14 and I am very confused as to why I cannot flash properly. I am on TWRP 2.4.1.0, but have used various recoveries trying to solve the problem. I have also RUU'd trying to fix the problem, but to no avail. Any help would be much appreciated!

Twrp 2.4 has issues with wiping properly. Have you tried a different version or wiping with adb in fastboot?
Sent from my HTC One X using xda premium

From what I understand twrp 2.4.1 should be working but I would flash 2.3.x just in case, then do fastboot erase cache. Then wipe cache, dalvik, system, factory reset.
If you RUUd and are s-off why are you still on 1.14? You may as well go up to 2.14 then downgrade touchscreen to use AOSP. Super easy.
Since S-OFF is just a security flag, I am 100% sure it's not the cause of your issue.
Sent from my One X using xda app-developers app

exad said:
From what I understand twrp 2.4.1 should be working but I would flash 2.3.x just in case, then do fastboot erase cache. Then wipe cache, dalvik, system, factory reset.
If you RUUd and are s-off why are you still on 1.14? You may as well go up to 2.14 then downgrade touchscreen to use AOSP. Super easy.
Since S-OFF is just a security flag, I am 100% sure it's not the cause of your issue.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I haven't wiped in fastboot because I thought that's what wiping in recovery was for, I really appreciate all of the input and I will be trying both of these things as soon as I'm done with dinner. Man's gotta eat, ya know :laugh:

Lol. Yep.
Sent from my HTC One X using xda premium

Only fastboot erase cache! The rest of the wiping is done in recovery!
Sent from my One X using xda app-developers app

exad said:
Only fastboot erase cache! The rest of the wiping is done in recovery!
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
As a question, what is the difference between wiping cache in recovery and the fastboot command?

Downgrade twrp to 2.3.3.1
Sent from the HOXL dimension of S-OFF

The fastboot command wipes a cache related to the recovery. Wiping cache in recovery wipes a cache relating to the rom.
Sent from my One X using xda app-developers app

exad said:
The fastboot command wipes a cache related to the recovery. Wiping cache in recovery wipes a cache relating to the rom.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
So I wiped cache via fastboot, and flashed the ROM like i normally would (wipe everything in recovery), but nothing has changed. I still get hung up on the splashscreen when trying to boot the new ROM. ViperXL boots fine when I restore my NANDroid backup, though.

Did you try flashing the boot.img after? You're still on hboot 1.14 afterall. I haven't seen first hand if you can skip flashing the boot.img with s-off, in your case, it seems not.
Sent from my One X using xda app-developers app

exad said:
Did you try flashing the boot.img after? You're still on hboot 1.14 afterall. I haven't seen first hand if you can skip flashing the boot.img with s-off, in your case, it seems not.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Even without flashing the boot.img, it should go past the splashscreen to the boot animation, am I wrong?

You are wrong. It may depending on the kernel previously installed
Sent from my One X using xda app-developers app

exad said:
You are wrong. It may depending on the kernel previously installed
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Sorry to sound like a complete noob, I've been rooting ect for 2.5 years and never seen this problem. Could you please explain a bit more what you mean by the previous post. Are you saying it's the kernel or the boot.img not being installed correctly?

WeiblezWobble said:
Sorry to sound like a complete noob, I've been rooting ect for 2.5 years and never seen this problem. Could you please explain a bit more what you mean by the previous post. Are you saying it's the kernel or the boot.img not being installed correctly?
Click to expand...
Click to collapse
flashing the boot.img is flashing the kernel. you don't sound like a complete noob so don't worry.

I'm going to try again right now to flash the boot.img and then the ROM like normal, reporting back in 15 mins

WeiblezWobble said:
I'm going to try again right now to flash the boot.img and then the ROM like normal, reporting back in 15 mins
Click to expand...
Click to collapse
wipe everything first of course. cache dalvik system and factory reset. i dont mean to treat you like a noob but its better to be extra specific than not specific enough

exad said:
wipe everything first of course. cache dalvik system and factory reset. i dont mean to treat you like a noob but its better to be extra specific than not specific enough
Click to expand...
Click to collapse
Alright, tried it all exactly how you said and it had the same response, got stuck on splashscreen. I am completely puzzled

WeiblezWobble said:
Alright, tried it all exactly how you said and it had the same response, got stuck on splashscreen. I am completely puzzled
Click to expand...
Click to collapse
alright so just to be sure. first off youre on twrp 2.3.x right?
you wipe cache, dalvik, system and factory reset right?
then you flash the rom and the boot.img right? (doesnt matter what order these are flashed)
and still bootlooping?

exad said:
alright so just to be sure. first off youre on twrp 2.3.x right?
you wipe cache, dalvik, system and factory reset right?
then you flash the rom and the boot.img right? (doesnt matter what order these are flashed)
and still bootlooping?
Click to expand...
Click to collapse
Exactly, but just to be 100% clear, I am getting stuck at the splashscreen, and it just sits there infinitely.

[Q] Fresh Start

Hi all, I just wanted to start by saying that xda is the shizz and has helped me through thick n thin. Anywho, I have a custom Rom and am trying to go to a different Rom. ViperX to be specific. I've tried before, but with little success. Extracted boot.img, fastboot flash boot boot.img in the command, put the Rom on my sd and installed via TWRP. Problem is, is that it never boots, only the HTC boot screen with the red writing. Anyone have any suggestions on what I need to do? I'm still S-on, but from what I understand, that doesn't matter if you fastboot the boot.img via command prompt. I also have Hboot 1.14.
Thanks.

Chuckles850 said:
Hi all, I just wanted to start by saying that xda is the shizz and has helped me through thick n thin. Anywho, I have a custom Rom and am trying to go to a different Rom. ViperX to be specific. I've tried before, but with little success. Extracted boot.img, fastboot flash boot boot.img in the command, put the Rom on my sd and installed via TWRP. Problem is, is that it never boots, only the HTC boot screen with the red writing. Anyone have any suggestions on what I need to do? I'm still S-on, but from what I understand, that doesn't matter if you fastboot the boot.img via command prompt. I also have Hboot 1.14.
Thanks.
Click to expand...
Click to collapse
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
That being said, Sounds like you are on TWRP 2.4.x please confirm.
If so, fastboot flash twrp 2.3.x.x
then fastboot erase cache
then wipe cache, dalvik, system, factory reset
Install rom and fastboot flash boot boot.img
Keep me posted.

exad said:
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
That being said, Sounds like you are on TWRP 2.4.x please confirm.
If so, fastboot flash twrp 2.3.x.x
then fastboot erase cache
then wipe cache, dalvik, system, factory reset
Install rom and fastboot flash boot boot.img
Keep me posted.
Click to expand...
Click to collapse
Will do thank you
Sent from my HTC One XL using xda app-developers app

exad said:
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
That being said, Sounds like you are on TWRP 2.4.x please confirm.
If so, fastboot flash twrp 2.3.x.x
then fastboot erase cache
then wipe cache, dalvik, system, factory reset
Install rom and fastboot flash boot boot.img
Keep me posted.
Click to expand...
Click to collapse
Apparently there's a TWRP 2.4.4 out, would it hurt me to flash the latest version?
Sent from my HTC One XL using xda app-developers app

Yes. It would hurt anyone with a one xl as 2.4 does not wipe our device properly. I tested 2.4.4 myself.
Sent from my HTC One X using xda app-developers app

ok, well I found another problem you might be able to help me with, but I'll shoot it to you anyway. I just found out my phone was originally a One X when I got it from the ATT store. Now apparently after I flashed the Rom I got (odex-JB-Sense4+.zip), It's saying my phone is an XL. Seems to me I have a whole new set of issues. Did I flash the wrong Rom? I though I did enough research to find a compatible Rom. How do I find out for sure what's going on with my phone and how to fix it properly?

Chuckles850 said:
ok, well I found another problem you might be able to help me with, but I'll shoot it to you anyway. I just found out my phone was originally a One X when I got it from the ATT store. Now apparently after I flashed the Rom I got (odex-JB-Sense4+.zip), It's saying my phone is an XL. Seems to me I have a whole new set of issues. Did I flash the wrong Rom? I though I did enough research to find a compatible Rom. How do I find out for sure what's going on with my phone and how to fix it properly?
Click to expand...
Click to collapse
No problem you have the correct ROM, if you had flashed wrong one it would have not worked correctly. Depending on the ROM sometimes it will show XL instead of X.

One xl is the proper model name, code named Evita, not to be confused with the real HTC One X international quad core version.
So in other words, nothing is wrong. This is normal. If you flashed the wrong rom you would know as you would now have a paperweight
Sent from my HTC One X using xda app-developers app

ok cool, I was kinda confused there for a sec lol. Ok, now for the TWRP. I'm assuming you were referring to 2.3.0.0? just because there is a 2.3.0.0, 2.3.1.0, 2.3.3.0, and a 2.3.3.1. I just want to make sure I have the correct one for Hboot 1.14

Doesn't matter which one. I use 2.3.3.1 myself.
Sent from my HTC One X using xda app-developers app

You have an xl so be sure to download and flash ViperXL and not ViperX. Luckily Viper does a model check before it installs.
Sent from my HTC One X using xda premium

ok, downloading it now. I'll keep you updated.

bkmo said:
You have an xl so be sure to download and flash ViperXL and not ViperX. Luckily Viper does a model check before it installs.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Ah I didn't catch that in the first post! Good eye.

bkmo said:
You have an xl so be sure to download and flash ViperXL and not ViperX. Luckily Viper does a model check before it installs.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
ok, I'll keep that in mind. Thank you!!

exad said:
Ah I didn't catch that in the first post! Good eye.
Click to expand...
Click to collapse
it's ok bud, just downloaded and installed TWRP 2.3.3.1 successfully, now i'm downloading ViperXL and hope everything comes out ok

exad said:
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
That being said, Sounds like you are on TWRP 2.4.x please confirm.
If so, fastboot flash twrp 2.3.x.x
then fastboot erase cache
then wipe cache, dalvik, system, factory reset
Install rom and fastboot flash boot boot.img
Keep me posted.
Click to expand...
Click to collapse
Should I need to be thinking about Kernels of any sort?

Chuckles850 said:
Should I need to be thinking about Kernels of any sort?
Click to expand...
Click to collapse
Yeah.......give bulletproof 1.1 a shot. Gonna give you better performance and battery, plus a no brainer install and its stable.
Sent from my Transformer TF101 using xda premium

bkmo said:
Yeah.......give bulletproof 1.1 a shot. Gonna give you better performance and battery, plus a no brainer install and its stable.
Sent from my Transformer TF101 using xda premium
Click to expand...
Click to collapse
Ok cool. Any links?
Sent from my HTC One X using xda app-developers app

It's in Android development page. if not the first page then the second.

exad said:
Because you are S-ON with hboot 1.14 you ALWAYS ALWAYS ALWAYS need to fastboot flash boot boot.img from the rom you are flashing.
Click to expand...
Click to collapse
Except for ViperXL (and old builds of CleanROM, which may also happen with future builds if/when scrosler gets AROMA back in there) which is intended to flash the boot.img in AROMA.
Although, it doesn't always work for some folks, so they have had to flash boot.img manually. So yes, if at all in doubt (and you have a boot loop) flash boot.img manually.

Trouble getting Miui to boot....again

Okay so Im trying to install miui v5 but im having isuues getting it to boot...again. ok so when v4 3.2.22 first came out I couldnt get it to boot. I would install the rom, then gapps and could not get it to boot past the optimizing apps screen. it would just stay at starting apps. I was told by another user to flash rohans kernel version b5 as that has worked for him on a different rom, and it worked for me. Now trying to install V5 its been a nightmare. when just installing the rom, then gapps I could not get it to boot past the splash screen. it would load it for a second then just go to a black screen. I then tried installing rohans kernel version b5 but now I get stuck at the starting apps screen I tried wiping cache and dalvik and that did nothing. tried installing different kernels and most I tried wouldnt let me get past the boot animaion Im using twrp 2.3.1.0, Im s-off and I even tried lowering my hboot from 1.14 to 1.09 just incase that might be it but nope. im no sure what else to do and help would be greatly appreciated

avery.0 said:
Okay so Im trying to install miui v5 but im having isuues getting it to boot...again. ok so when v4 3.2.22 first came out I couldnt get it to boot. I would install the rom, then gapps and could not get it to boot past the optimizing apps screen. it would just stay at starting apps. I was told by another user to flash rohans kernel version b5 as that has worked for him on a different rom, and it worked for me. Now trying to install V5 its been a nightmare. when just installing the rom, then gapps I could not get it to boot past the splash screen. it would load it for a second then just go to a black screen. I then tried installing rohans kernel version b5 but now I get stuck at the starting apps screen I tried wiping cache and dalvik and that did nothing. tried installing different kernels and most I tried wouldnt let me get past the boot animaion Im using twrp 2.3.1.0, Im s-off and I even tried lowering my hboot from 1.14 to 1.09 just incase that might be it but nope. im no sure what else to do and help would be greatly appreciated
Click to expand...
Click to collapse
Wipe everything. Install your rom only. Does it boot?

exad said:
Wipe everything. Install your rom only. Does it boot?
Click to expand...
Click to collapse
no. It loads the splash screen for a second then goes to a black screen.

You've verified the md5 right?
Boot to bootloader/fastboot and do fastboot erase cache in command prompt then wipe everything cache, dalvik, system, factory reset, then flash rom.
Does it boot?
Sent from my HTC One X using xda app-developers app

exad said:
You've verified the md5 right?
Boot to bootloader/fastboot and do fastboot erase cache in command prompt then wipe everything cache, dalvik, system, factory reset, then flash rom.
Does it boot?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
redownloaded 3 times. erased cache. wiped everything and same problem as before loads splash screen then back screen

Redownloading != checking md5 you could Redownload 500 times and all 500 downloads could have corruption of some sort.
You did fastboot erase cache?
If you're positive your download is good and after fastboot erase cache and wiping everything isn't working. Your last step is to s-off if you're not already and ruu to the latest version then flash twrp then wipe everything then flash the rom.
Sent from my HTC One X using xda app-developers app

exad said:
Redownloading != checking md5 you could Redownload 500 times and all 500 downloads could have corruption of some sort.
You did fastboot erase cache?
If you're positive your download is good and after fastboot erase cache and wiping everything isn't working. Your last step is to s-off if you're not already and ruu to the latest version then flash twrp then wipe everything then flash the rom.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Just making sure since I have only researched slightly, since im s-off If i run the latest unrootable RUU Id still be able to unlock bootloader and regain root?

What other roms have you tried to flash? Is Mui the only ones giving you problems? Try other ones to see if it is not a bad twrp. It may not be wiping correctly.
Sent from my HTC One X using xda premium

Venomtester said:
What other roms have you tried to flash? Is Mui the only ones giving you problems? Try other ones to see if it is not a bad twrp. It may not be wiping correctly.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
every other rom ive flashed boots fine its only miui that gives me problems. It boots for other people fine so I dont think its the rom and I tried to install on CWM and still have issues

I had the same problem with Chameleon. Took four different downloads to get it. Avatar took a few too lol. Take above advice. Check sum. Might even try wiping cache in adb.
Sent from my HTC One X using xda premium

Venomtester said:
I had the same problem with Chameleon. Took four different downloads to get it. Avatar took a few too lol. Take above advice. Check sum. Might even try wiping cache in adb.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
noob question but how do I find the md5?

avery.0 said:
noob question but how do I find the md5?
Click to expand...
Click to collapse
Search MD5 Sum Checker. It's a program that is pretty self explanatory and will check it for you. The MD5 is attached to the download. You copy it from the site and past it in the checker.

And after you s-off you don't need to re lock to ruu so you won't lose bootloader unlock
Sent from my HTC One X using xda app-developers app

Running the 3.18 RUU fixed my problems. Thank you both for the help
Sent from my HTC One X using xda premium

Question about Cyanogenmod 11

Hello guys,
I've been looking around for CM11 for my HTC One X+.
Now I've found the original CM11 on their website for HOX+, but there is one little question I got about this.
http://download.cyanogenmod.org/?device=enrc2b
That's the link where I've found it by the way.
There is no boot.img download, how safe is it to just install the ROM? In my opinion it isn't.
So let me know what you guys think.
Sent from my HOX+

NiZii. said:
Hello guys,
I've been looking around for CM11 for my HTC One X+.
Now I've found the original CM11 on their website for HOX+, but there is one little question I got about this.
http://download.cyanogenmod.org/?device=enrc2b
That's the link where I've found it by the way.
There is no boot.img download, how safe is it to just install the ROM? In my opinion it isn't.
So let me know what you guys think.
Sent from my HOX+
Click to expand...
Click to collapse
Its on the official website, and It should work. Make a backup though.
The boot.img download isn't there because the boot.img is probably inside the .zip.
So open the zip and you'll have your boot.img.
Sent from my Nexus 5 using Tapatalk

krishneelg3 said:
Its on the official website, and It should work. Make a backup though.
The boot.img download isn't there because the boot.img is probably inside the .zip.
So open the zip and you'll have your boot.img.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yeah, already found it.
Thanks though.
One small question, if I'm going to put the .zip file on my SD card I can just leave the boot.img in the .zip right?
Sent from my HOX+

NiZii. said:
Yeah, already found it.
Thanks though.
One small question, if I'm going to put the .zip file on my SD card I can just leave the boot.img in the .zip right?
Sent from my HOX+
Click to expand...
Click to collapse
Well is your device s-off or s-on?
Sent from my Nexus 5 using Tapatalk

krishneelg3 said:
Well is your device s-off or s-on?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
S-On, after hours of searching how to put S-Off I gave that up. Since I can't find it for my HTC One X+.
Sent from my HOX+

NiZii. said:
S-On, after hours of searching how to put S-Off I gave that up. Since I can't find it for my HTC One X+.
Sent from my HOX+
Click to expand...
Click to collapse
Oh okay, you will need to flash the boot.img alone then as flashing the ROM zip won't just work. So boot into bootloader, and flash the new boot.img you had extracted from the .zip
Once yo uhave flashed the .img boot into recovery mode and perform a gull wipe, including cache. Once done simply flash the zip and reboot.
First reboot takes a bit so be patient. I also recommend you getting a band backup in case.
Sent from my Nexus 5 using Tapatalk

krishneelg3 said:
Oh okay, you will need to flash the boot.img alone then as flashing the ROM zip won't just work. So boot into bootloader, and flash the new boot.img you had extracted from the .zip
Once yo uhave flashed the .img boot into recovery mode and perform a gull wipe, including cache. Once done simply flash the zip and reboot.
First reboot takes a bit so be patient. I also recommend you getting a band backup in case.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Ye I know it takes a lot of time since I've been flashing a ROM once before, but I can just leave the file in the .zip when flashing it in recovery?
Sent from my HOX+

NiZii. said:
Ye I know it takes a lot of time since I've been flashing a ROM once before, but I can just leave the file in the .zip when flashing it in recovery?
Sent from my HOX+
Click to expand...
Click to collapse
Yeah I suppose you can. Nothing will happen.
Sent from my Nexus 5 using Tapatalk

krishneelg3 said:
Yeah I suppose you can. Nothing will happen.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Okay thanks.
Sent from my HOX+

NiZii. said:
Okay thanks.
Sent from my HOX+
Click to expand...
Click to collapse
No worries.
All the best.
Sent from my Nexus 5 using Tapatalk

If you're coming from a Sense ROM you can't just flash the zip without flashing the boot.img. It wouldn't even boot. And sometimes it boots but without mobile signal or WiFi signal.
So just place the zip on your sdcard, take the boot.img out of the zip on your computer.. Then boot into bootloader and connect it to the computer using USB then type
"fastboot flash boot boot.img"
Then "fastboot erase cache"
(you must have fastboot installed and configured on your computer)
Then boot into recovery and flash the zip file and gapps. Oh don't forget a wipe is mandatory if you're coming from sense ROM. But if you're coming from an AOSP ROM it's recommended but you can go without wiping. I flashed cyanogen over paranoid android without wiping data and had no issues at all. But I wiped the system partition.
And you cannot S-OFF an HTC One X+.. If it's S-ON then it stays that way. Only a few amount of people have S-OFF on their HOX+.
Oh and I don't think TWRP recovery is compatible with CM11 on HOX+.. So I recommend you flash philz recovery. Flash it by using the fastboot command "fastboot flash recovery recovery.img"
(recovery.img should be replaced with the name of the recovery you downloaded)
It doesn't take a lot of time. I change ROMs almost every week.
Please press the thanks button if I helped!
Sent from my One X+ using XDA Premium 4 mobile app

backb0ne5p1d0r said:
If you're coming from a Sense ROM you can't just flash the zip without flashing the boot.img. It wouldn't even boot. And sometimes it boots but without mobile signal or WiFi signal.
So just place the zip on your sdcard, take the boot.img out of the zip on your computer.. Then boot into bootloader and connect it to the computer using USB then type
"fastboot flash boot boot.img"
Then "fastboot erase cache"
(you must have fastboot installed and configured on your computer)
Then boot into recovery and flash the zip file and gapps. Oh don't forget a wipe is mandatory if you're coming from sense ROM. But if you're coming from an AOSP ROM it's recommended but you can go without wiping. I flashed cyanogen over paranoid android without wiping data and had no issues at all. But I wiped the system partition.
And you cannot S-OFF an HTC One X+.. If it's S-ON then it stays that way. Only a few amount of people have S-OFF on their HOX+.
Oh and I don't think TWRP recovery is compatible with CM11 on HOX+.. So I recommend you flash philz recovery. Flash it by using the fastboot command "fastboot flash recovery recovery.img"
(recovery.img should be replaced with the name of the recovery you downloaded)
It doesn't take a lot of time. I change ROMs almost every week.
Please press the thanks button if I helped!
Sent from my One X+ using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey i have htc one m7_ul and when ever i tried to flash cyanogenmod i ended up with so error like some binary problem do you know the fix for it???

Aisfkhan said:
Hey i have htc one m7_ul and when ever i tried to flash cyanogenmod i ended up with so error like some binary problem do you know the fix for it???
Click to expand...
Click to collapse
Whats the error exactly ? and where did you get the error ?

backb0ne5p1d0r said:
Whats the error exactly ? and where did you get the error ?
Click to expand...
Click to collapse
Its in twrp 2.6.3.3 and about some extracting binary failed error but now solved i flashed the boot.img file from cm11.zip file then flashed from philz recovery and everything goes fine