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.
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.
So I wanted CM 10 on my phone, I used Flash GUI app, and flashed and tried flashing it through twrp. It reset, somethings didnt install properly couldn't catch what it didnt install. I read some misinformation online (or misinterpretation on my part) and wiped cache + davlik data. So now when I restart it goes to HTC screen then a black screen. I can still access bootloader, but I don't have a recovery file now to go off from or have no idea where to go from
I have HBOOT 1.15 with S-ON, 1.22.651.3, any ideas, or suggestions?
The kernel install didnt take. I'd highly suggest doing it via fastboot and not the app.
http://androidforums.com/evo-4g-lte-all-things-root/606748-how-install-kernels-h-boot-1-15-wip.html
Dude thank you so much! I did exactly what you said! You are awesome awesome awesome!
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!
Today I decided to root my phone, and after successfully doing that, decided I wanted to try out installing a custom ROM. Obviously by the title that didn't work out too well.
I'm using ClockworkMod as recovery, and I attempted to flash CyanogenMod using ROMManager. I created backups before I tried flashing, but that didn't help. Once I hit Install ROM from SD Card I made sure to back up again, but I did not check clear the cache which I probably should have done. My phone then rebooted into ClockworkMod and I then went to install zip from sdcard and chose the .zip that contained the latest CyanogenMod, it ran through the process alright then rebooted.
At that point I got stuck in a boot loop, I think it might've been either that I didn't clear the cache before or if it was that I had the .zip on an external SD card or not. I then looked up ways to fix the loop such as clearing the Dalvik cache, wiping the cache partition, then eventually I tried to wipe the data/factory reset on the recovery option but that all did nothing. During all this I also tried my backup hoping that would end my problem, but I got an error with the MD5 mismatching so I can't use that backup, I do have other backups on my computer, but I can't get them onto the SD card, and ADB isn't detecting my phone so I can't try a way to fix the backup that way either.
Anyone have any idea how to fix this? I can provide more information if needed. Any help would be great.
If you're S-on you have to flash the kernel separately from the ROM. Hit the top link in my sig for more info. Also, TWRP recovery is recommended on the EVO LTE, not CWM, which is no longer supported, at least on this device.
Sent from my HTC EVO 4G LTE
FinZ28 said:
If you're S-on you have to flash the kernel separately from the ROM. Hit the top link in my sig for more info. Also, TWRP recovery is recommended on the EVO LTE, not CWM, which is no longer supported, at least on this device.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Ok, thank you so much for your response this actually got me back on track after switching to TWRP and flashing the kernel first with CWM being the big issue for me. Now I'm just waiting for CyanogenMod to load, which I assume just takes a few minutes at the loading screen.
Got it fully working, thanks again
Not a problem.
Sent from my HTC EVO 4G LTE
Hello, I need help. I tried to update my phone to a new ROM and now it is only booting in bootloader and says there is no OS. I have downloaded a RUU that matched, renamed it and put it on my microsd and tried to flash it but it reboots in TWRP. I have a backup and when I try to restore it says Restore Complete Failed---E: Cannot restore System -- mounted read only. I really love the M9 and want it back up and running can anyone please help me get it back functioning? It does not have fastboot option and adb server out of date. Pretty much a noob here. I have flashed other Roms before, but this M9 is proving to be a pain. I have been researching thread after thread and still no luck. Any help would greatly be appreciated.
Here is info on device:
htc_himawh1 PVT S-On
[email protected]
OS-1.32.651.30
OpenDSP-v22.2.6-00452-M8994_0318
**Software status: Modified**
***Unlocked***
***S-ON***
Ruu aint flashing cuz u have unlocked firmware. Search up how to relock bootloader. Btw, why not just install a rom? . One thing is u wont be able to root ur phone after relock.
EvoGuy2010 said:
Ruu aint flashing cuz u have unlocked firmware. Search up how to relock bootloader. Btw, why not just install a rom? . One thing is u wont be able to root ur phone after relock.
Click to expand...
Click to collapse
Thanks I figured I will look at how to relock the bootloader without fastboot. I honestly didn't think I could install a rom because I figured most needed MM7 and I dont have that installed which is what happened when I tried to install Viper Rom
Got it working again. I had to restore only the boot and system image. After it rebooted I then restored data and it's back to normal.
SirDeuce said:
Got it working again. I had to restore only the boot and system image. After it rebooted I then restored data and it's back to normal.
Click to expand...
Click to collapse
Can you please help me?
i woke up today and my phone died of charge. I plugged in the charger and tried to power up my phone. It was stuck in a bootloop. So, I went into recovery, wiped cache and dalvik cache, rebooted, and still didnt work.
I then went to wipe and did the thing where twrp asks to do a factory reset by wiping cache, dalvik cache, and data. Still didnt worl, so i took out the sd card and did it again. Still bootloops. So, i then wiped dalvik cahce, cache, system, and data. Now, my phone is stuck in the white HTC logo with red text. and twrp tells me there is no os installed, are you sure you want to continue? CAN SOMEONE PLEASE HELP ME WITH THIS! PLEASE PLEASE REPLY AS SOON AS POSSIBLE!
KingAirman said:
Can you please... Now, my phone is stuck in the white HTC logo with red text. and twrp tells me there is no os installed, are you sure you want to continue? CAN SOMEONE PLEASE HELP ME WITH THIS! PLEASE PLEASE REPLY AS SOON AS POSSIBLE!
Click to expand...
Click to collapse
Hey did you get it to work? Just seeing this post. If you backed up your system and boot images boot into twrp and flash those copies you made before the wipes. See where that gets ya. Hopefully you got it fixed by now.