Hello.
I have only been able to install ViperX+ 1.08 ROM successfully. I wanted to experience other ROMs in comparison and have found ROMs specifically for this model, HTC One X Plus International, only to have them fail to fully install successfully. I have read up here on how to go about it and followed the steps dutifully but to no avail.
Does it make a difference on which Recovery you have installed for it to be successful or not? I currently have the latest TWRP 2.5.0.0 for my model. I have tried installing CyanogenMod and AOKP. CyanogenMod never makes it pass the installation because it fails right after attempting to install. AOKP installs but hang at the opening picture, and yes, I tried flashing the boot.img in Fastboot thinking that would solve it but it continued hanging anyway. Anyone have any help they can offer me? Thanks.
Jussi31 said:
Hello.
I have only been able to install ViperX+ 1.08 ROM successfully. I wanted to experience other ROMs in comparison and have found ROMs specifically for this model, HTC One X Plus International, only to have them fail to fully install successfully. I have read up here on how to go about it and followed the steps dutifully but to no avail.
Does it make a difference on which Recovery you have installed for it to be successful or not? I currently have the latest TWRP 2.5.0.0 for my model. I have tried installing CyanogenMod and AOKP. CyanogenMod never makes it pass the installation because it fails right after attempting to install. AOKP installs but hang at the opening picture, and yes, I tried flashing the boot.img in Fastboot thinking that would solve it but it continued hanging anyway. Anyone have any help they can offer me? Thanks.
Click to expand...
Click to collapse
The aokp uses the 4.2 kernal so you will have to instal that. But I'm not sure on the recovery .. maybe it might be worth trying clockwork as if the twrp you are useing is especially for the viper Rom? Have a go at installing the different recovery maybe that will help and double check what you have to do to install on the thread hope this helps
Ilike the viper Rom... But if I get time tomorrow I will try for myself ... If no one else helps you out by the time I do it I will update you on how I done it and any problems I faced maybe I will end up in the same situation.
Sent from my HTC One X+ using xda premium
Appreciate it. Insofar as the Recovery is concerned, the initial Recovery that I installed from the All-In-One kit when installing ViperX+ is different from the one I have now. Unless it is just a newer version, I now have Venom TWRP 2.5.0.0., just FTR. Thanks again, I will be interested to hear what happens for you.
Jussi31 said:
Appreciate it. Insofar as the Recovery is concerned, the initial Recovery that I installed from the All-In-One kit when installing ViperX+ is different from the one I have now. Unless it is just a newer version, I now have Venom TWRP 2.5.0.0., just FTR. Thanks again, I will be interested to hear what happens for you.
Click to expand...
Click to collapse
TWRP is the ideal solution for our HOX+ - at least as of now.
I hope you are doing the following:
1. Wiping Data & System.
2. Installing boot.img.
The Venom customized TWRP does not have any issues because I also used it for some time (as of now I am back on the official TWRP).
You can download the lastes verison from here:
http://techerrata.com/browse/twrp2/enrc2b
And install it using Hox+ All in one toolkit by hasoon.
Make sure you wipe data & system before you install the ROM.
I also changed from ViperX 1.08 to ARHD, InsertCoin & Elegancia.. no issues
Hmmm. I'll have to putz around with it some more and see what happens. Thanks.
Here's a brief summary of what I attempted to do.
I wiped Delvik Cache; I wiped Cache; I did Factory Reset; I wiped System.
Next I tried installing CyanogenMod and received the following error messages:
assert failed: getprop
E: error executing updater binary in zip
Error flashing zip
So I wiped everything again and tried installing AOKP. It successfully installs. I try rebooting prior to flashing boot.img. It hangs on horse picture opening screen. So I flash the boot.img in Fastboot and reboot after erasing cache. When rebooting it hangs on opening white screen.
I'm baffled. What am I doing wrong?
Jussi31 said:
Here's a brief summary of what I attempted to do.
I wiped Delvik Cache; I wiped Cache; I did Factory Reset; I wiped System.
Next I tried installing CyanogenMod and received the following error messages:
assert failed: getprop
E: error executing updater binary in zip
Error flashing zip
So I wiped everything again and tried installing AOKP. It successfully installs. I try rebooting prior to flashing boot.img. It hangs on horse picture opening screen. So I flash the boot.img in Fastboot and reboot after erasing cache. When rebooting it hangs on opening white screen.
I'm baffled. What am I doing wrong?
Click to expand...
Click to collapse
I guess your recovery is not able to detect that your phone is one x+.. that's why assert failed error.. try changing the recovery( maybe CWM) and try again
Through trial-and-error, and reading hard, I figured out I had to install a compatible Kernel. I then was able to install, successfully, AOKP and it seems to work very smoothly. I'm just learning the ins-and-outs of everything. Thanks for your help.
Jussi31 said:
Through trial-and-error, and reading hard, I figured out I had to install a compatible Kernel. I then was able to install, successfully, AOKP and it seems to work very smoothly. I'm just learning the ins-and-outs of everything. Thanks for your help.
Click to expand...
Click to collapse
:good::good::good:
that is cool!
Related
I've been shuffling through threads for the past 2 days trying to find a fix a no luck yet so i'm making my own noob post.
yesterday after flashing CM7 to my atrix, I was trying to install the Gapps package and after that install my phone wont boot past the logo screen.
Im still able to access fastboot and get into android recovery. I've tried to wipe everything and reinstall cm7 but still nothing.
i read that some people were able to get this issue resolved using command prompt and fastboot commands, but im totally lost when it comes to command prompt and couldn't get working correctly.
any suggestions or fixes would be greatly appreciated
DThimself said:
I've been shuffling through threads for the past 2 days trying to find a fix a no luck yet so i'm making my own noob post.
yesterday after flashing CM7 to my atrix, I was trying to install the Gapps package and after that install my phone wont boot past the logo screen.
Im still able to access fastboot and get into android recovery. I've tried to wipe everything and reinstall cm7 but still nothing.
i read that some people were able to get this issue resolved using command prompt and fastboot commands, but im totally lost when it comes to command prompt and couldn't get working correctly.
any suggestions or fixes would be greatly appreciated
Click to expand...
Click to collapse
Just to be clear:
1. You successfully booted into CM7 after installing it? Then you went to install gapps and couldn't get past the boot logo?
2. Or were you trying to install gapps right after flashing CM7 (i.e. stayed in recovery and did not boot into OS)?
i Successfully booted into cm7 then went back into recovery to install the gapps package and after that install it wouldnt boot past the logo
DThimself said:
i Successfully booted into cm7 then went back into recovery to install the gapps package and after that install it wouldnt boot past the logo
Click to expand...
Click to collapse
Hmm, well that definitely rules out an outdated recovery, which is what usually causes people to get stuck at the bootlogo. If you can't even re-install after wiping, then I would just restore a backup and start over.
Maybe try getting a fresh download of the gapps package. You may have possibly had a corrupted download?
Are you running CWM recovery or Rom Racer's? I had a problem where I was stuck at the boot logo while using CWM (latest one) but when I switched to Rom Racer's recovery and flashed everything worked.
I ended up having to use an older CWM recovery and wiping the phone and SD card with a lot of help from a friend of mine whos knows more about this than i do
DThimself said:
i Successfully booted into cm7 then went back into recovery to install the gapps package and after that install it wouldnt boot past the logo
Click to expand...
Click to collapse
How did you prep for the CM7 and GAPPS flash? If you did not wipe correctly, there was a first indication you might have problems.
How long did you wait after the phone first booted into CM7? If you rebooted as soon as the OS was up, that's more than likely your issue. You need to wait 10 minutes to let the phone build system files after flashing.
Also, an older CWM would have, if anything, caused more problems. If you had the latest ROM Manager or Romracer CWM then that was definitely not your problem, so your friend using an "older" CWM wasn't helping any.
DThimself said:
I've been shuffling through threads for the past 2 days trying to find a fix a no luck yet so i'm making my own noob post.
yesterday after flashing CM7 to my atrix, I was trying to install the Gapps package and after that install my phone wont boot past the logo screen.
Im still able to access fastboot and get into android recovery. I've tried to wipe everything and reinstall cm7 but still nothing.
i read that some people were able to get this issue resolved using command prompt and fastboot commands, but im totally lost when it comes to command prompt and couldn't get working correctly.
any suggestions or fixes would be greatly appreciated
Click to expand...
Click to collapse
I have run into this issue before when flashing any apps that update an app that is already there. I have found that a Dalvik wipe is needed before the flash. It is good practice to wipe Dalvik at least when flashing anything that changes the System Files. I also wipe the cache Partition before any flashes just to help mitigate issues like this.
I got my S3 a while ago and only recently decided to install a custom rom. I installed the CM10.1 nightly build and I've been happy with it and all, but upon seeing MIUI on my friend's phone I decided to flash MIUI. Now, when I tried flashing through recovery it hung for a min or so at "opening update package" and then gave me an error saying "E: Can't open /external_sd/miuiandroid_m0_jb-3.1.25.zip (bad) Installation aborted". I have tried re-downloading the rom and all, I've tried wiping cache/dalvik cache and even a factory reset and nothing's worked so far.
This happens no matter what rom I try to flash over CM. Has anyone had this happen and does anyone know how to fix it?
b0sanac said:
I got my S3 a while ago and only recently decided to install a custom rom. I installed the CM10.1 nightly build and I've been happy with it and all, but upon seeing MIUI on my friend's phone I decided to flash MIUI. Now, when I tried flashing through recovery it hung for a min or so at "opening update package" and then gave me an error saying "E: Can't open /external_sd/miuiandroid_m0_jb-3.1.25.zip (bad) Installation aborted". I have tried re-downloading the rom and all, I've tried wiping cache/dalvik cache and even a factory reset and nothing's worked so far.
This happens no matter what rom I try to flash over CM. Has anyone had this happen and does anyone know how to fix it?
Click to expand...
Click to collapse
Never happened to me. I can suggest a method that's not been tested, although theoretically there should be no problem implementing.
Although, have you tried flashing some AOSP mods? I'm getting a feeling something might be wrong with your recovery. If that is the case, try flashing siyah and hijack the recovery using stweaks. Then try installing roms again.
Are you installing from the internal or external sd? try the internal, and check the md5
Glebun said:
Are you installing from the internal or external sd? try the internal, and check the md5
Click to expand...
Click to collapse
Tried both internal and external, I get the same thing. I'm pretty sure that it's not corrupted since this is the same file that my friend used to flash his s3 to miui.
xcly said:
Never happened to me. I can suggest a method that's not been tested, although theoretically there should be no problem implementing.
Although, have you tried flashing some AOSP mods? I'm getting a feeling something might be wrong with your recovery. If that is the case, try flashing siyah and hijack the recovery using stweaks. Then try installing roms again.
Click to expand...
Click to collapse
I have not, will try it.
Edit: Flashed an AOSP rom and it worked fine, then MIUI, the install worked but now MIUI is just hanging on the boot screen.
Edit 2: Okay I got it working, I had to do a factory reset and it just started working.
Thanks for your help guys
Hi there!
I've recently flashed xpirt's unofficial port of MIUI v5. However, I'm not seeing any MIUI elements in my phone except 2 apps (which do not work). They are MiCloud and MiCredits. Other than those apps, my phone is pretty much a sensed based phone after flashing the phone.
Each time the phone boots up, a pop up will appear saying : Unfortunately, Xiaomi service framework has stopped. Same thing happens when i try to start the two related apps.
My order of flashing
Format /data
Format /cache
Format /system
Format /delvikcache
flash xpirt miui v5 #1
(at this point I repeated steps 1,2 & 4 after multiple failed attempts to get my miui working)
flash xpirt miui v5 #2
reboot
Did i flash it wrongly?
I have a working CWM recovery already.
Any help is appreciated!! My phone is in working condition even without the miui theme, but meh, wouldn't i just return to the stock rom?
Did a lot of work just to get my JB version on DX too! :crying:
Android 4.1.1
Hboot 1.25
fulmix.Kernel #2
Tried searching for any similar issues faced but seems like I'm the only one facing the issue.
Not even sure if it's supposed to be how it is... not enough screenshots around from other users to show what I should see upon starting up.
You have a wrong CWM recovery for JB hboot.
Use TWRP recovery for JB
Thanks!
ckpv5 said:
You have a wrong CWM recovery for JB hboot.
Use TWRP recovery for JB
Click to expand...
Click to collapse
Wow, that works for me! Thanks! :good::good:
I have the exact same problem
Hboot 1.25
unlocked with WinDroid HTC Desire X Toolkit v3.0
tried flashing the rom with the included TWRP and CWM.
phone boots, i get the error "xiaomi framework stopped" and the two mentioned apps.
flash order like aarontanws
do i need superuser before i flash the rom?
any other suggestions?
cheers
I'm not sure if the Windroid Tool checks your hboot and matches the right TWRP version. I for myself use TWRP 2.6.3.0 on JB hboot, works perfectly for me. You can also use PhilZ Touch if you want, but be sure to choose the JB version. Given that, flash the recoveries manually via fastboot, perform a full wipe, install the first package along with the second one.
TWRP 2.6.3.0 here.
I get an Error when I try wiping the dalvik cache.
flashed TWRP 2.5.0.0 via command line
no Error wiping dalvik + flashes MIUI successfully
fleischverpackung said:
TWRP 2.6.3.0 here.
I get an Error when I try wiping the dalvik cache.
flashed TWRP 2.5.0.0 via command line
no Error wiping dalvik + flashes MIUI successfully
Click to expand...
Click to collapse
Best tip I can give you, don't use a toolkit. Do everything manually
I recently changed from pauls recovery to twrp and tried to wipe and flash new rom however now im stuck. twrp seems to have wiped some stuff but not all and the rom just boot loops. any help is welcome asap.
I get this message. E:error opening '/data/data/com.google.android.g and E:error: I/O error
patrickliebl said:
I recently changed from pauls recovery to twrp and tried to wipe and flash new rom however now im stuck. twrp seems to have wiped some stuff but not all and the rom just boot loops. any help is welcome asap.
I get this message. E:error opening '/data/data/com.google.android.g and E:error: I/O error
Click to expand...
Click to collapse
I was having problems with TWRP recently (and periodically in the past). It would give errors and not flash/wipe/etc. I switched to the latest CWM and it's been working great so far. Just a thought it you cannot find a solution. I couldn't.
Good luck.
I got this from trying to use TB, and it corrupted a file. I switched recoveries a couple of time wiping internal, and data, switched back to twrp, and been solid ever since. It is the way TB messes up. I don't blame twrp for my mistake. Even posted in nebula about it.
Sent from my SCH-I605 using Tapatalk
Hello!!
Im new to all of this rooting etc... I have been trying for several weeks to get rooted and a rom installed. After much reading I realized my phone need the ph44img.zip to get recovery installed. I have my phone unlocked through htcdev, installed cwm 5.0.8.2, installed supersu. I have tried several roms and can never get past the htc white screen. I have tried installing the reloaded rom which i heard was very good with this phone. I've tried mazwoz got the error status 7 message so i did the assert delete fix. installed it and same white screen. cyanogen same thing. I have been doing the factoryreset data wipe, cahe wipe, dalvik wipe etc. then installing the rom. Am I missing something or a step??? I thought i've read it all and followed all procedures.
htc evo 4g NOT lte kingdom
hboot 1.32.0000
radio 1.11.00.1116
Thanks in advance for any help!!
Steven A.K.A. Dotcomdz
DOTCOMDZ said:
Hello!!
Im new to all of this rooting etc... I have been trying for several weeks to get rooted and a rom installed. After much reading I realized my phone need the ph44img.zip to get recovery installed. I have my phone unlocked through htcdev, installed cwm 5.0.8.2, installed supersu. I have tried several roms and can never get past the htc white screen. I have tried installing the reloaded rom which i heard was very good with this phone. I've tried mazwoz got the error status 7 message so i did the assert delete fix. installed it and same white screen. cyanogen same thing. I have been doing the factoryreset data wipe, cahe wipe, dalvik wipe etc. then installing the rom. Am I missing something or a step??? I thought i've read it all and followed all procedures.
htc evo 4g NOT lte kingdom
hboot 1.32.0000
radio 1.11.00.1116
Thanks in advance for any help!!
Steven A.K.A. Dotcomdz
Click to expand...
Click to collapse
After you download a rom. Right click it and choose open, don't extract the zip file. Then look for the boot.img
Copy the boot.img to the folder where you have the adb and fastboot files. Then flash the rom in cwm.
Then type adb reboot bootloader, then fastboot flash boot boot.img Then reboot.
It should boot the rom then, instead of the white screen.