HTC One x stuck - HTC One X

Hi.
So after flashing new recovery to CWM 6.0.4.8 to get kitkat and lollipop roms for my HOX any rom i flash gets stuck at the loading screen for the rom and wont go any further, yet when i go back to android revolution it works fine with new recovery flashed.
Any ideas?

km6061 said:
Hi.
So after flashing new recovery to CWM 6.0.4.8 to get kitkat and lollipop roms for my HOX any rom i flash gets stuck at the loading screen for the rom and wont go any further, yet when i go back to android revolution it works fine with new recovery flashed.
Any ideas?
Click to expand...
Click to collapse
are you flash the boot.img? are you make Full wipe?

Do as @Thant said. And please don't make multiple threads about the same subject, it gets confusing. You can just bump the original thread if you are getting no response.

Related

[Q] Epic stuck at Teamwin splash screen[CM11]

I just tried to preform an OTA update to the latest CM11 nightly and so it installed it through Teamwin recovery and now it is just stuck at the Teamwin splash screen. I cannot boot into recovery but I can access the yellow downloading screen. Any Idea on what to do? Am I going to have to use Odin to revert the phone back to stock rom?
Flash back to Stock
joejames542 said:
I just tried to preform an OTA update to the latest CM11 nightly and so it installed it through Teamwin recovery and now it is just stuck at the Teamwin splash screen. I cannot boot into recovery but I can access the yellow downloading screen. Any Idea on what to do? Am I going to have to use Odin to revert the phone back to stock rom?
Click to expand...
Click to collapse
I am pretty sure that happens if your Teamwin recovery is not new enough (I don't recall the required version). This happened to me as well.
My solution was to ODIN back to stock and install CWM (v5.0.2.7), CM11 will update it to v6.0.4.7. If I recall correctly I had to install the CM11 update twice (once for the CWM update and once to flash ROM)
Hope that helps
Chris
From what I know, the latest official TWRP (2.6.0.0) CAN NOT flash 4.4.x ROMs. Use CWM as included in CM nightlies, or try @unjust's 2.6.3.0 test build.
Sent from Google Nexus 4 @ CM11

Issue with flashing roms with s-on

I've HTC dev bootloader unlocked desire hd with custom recovery. I've tried flashing boot.img (from rom.zip) in fastboot before and after flashing rom in recovery mode. The phone gets past htc logo screen and then goes blank with back light on and stays there forever. I've tried 4 different roms. The only rom I was able to flash was CM7.
The phone is currently at h-boot 2.00.0029, is this why I can't flash new roms?
Any help is really appreciated
tt33333 said:
I've HTC dev bootloader unlocked desire hd with custom recovery. I've tried flashing boot.img (from rom.zip) in fastboot before and after flashing rom in recovery mode. The phone gets past htc logo screen and then goes blank with back light on and stays there forever. I've tried 4 different roms. The only rom I was able to flash was CM7.
The phone is currently at h-boot 2.00.0029, is this why I can't flash new roms?
Any help is really appreciated
Click to expand...
Click to collapse
Update your recovery.img to either of following;either one is good. But make backup of any rom you're on so that you may revert it back in future.
-TWRP 2.7.1.0
-Philz touch CWM
-4EXT Recovery Touch 1.0.0.6 RC 3
By the way which four roms you've tried? if recovery is up-to-date then phone should boot normally.
I have already tried philz touch and twrp. One thing I noticed was when i did a backup in recovery and tried restoring it and always get a md5 error. The same issue with different recoveries and on multiple tries. So I just flashed system.img and boot.img to get my phone back to stock rom.
Thanks
tt33333 said:
I have already tried philz touch and twrp. One thing I noticed was when i did a backup in recovery and tried restoring it and always get a md5 error. The same issue with different recoveries and on multiple tries. So I just flashed system.img and boot.img to get my phone back to stock rom.
Thanks
Click to expand...
Click to collapse
Strange....
Well unmark md5 check on restore. And clear cache/dalvic before rebooting it,Let's see how it goes.Also want to know which perticular rom you've tried so far where you were facing this issue. Also did you format devlog partition before installing CM11 nigthlies 20140618 onwards? If not then try doing so and let me know where you gets stuck?
I'm also S-ON where most other already made S-OFF so feel free to ask me. I'll help as much as i know :good:
Still no luck, it basically does the same thing for all roms. HTC logo shows up and then the screen goes blank with black light on. I've tried these roms:
cm-11-20140710-UNOFFICIAL-M8.1-ace.zip
ICESenseV1.1.zip
cm-7-20130301-NIGHTLY-ace.zip
MK44.4-ace-140719-RELEASE.zip
AoCP6_UW1_Port_for_Ace
I don't get any errors during the flashing process for all except the last one (AoCP6).
Also, the cm7 works sometimes and on other occasions it does the same thing as well. Could it be the sequence? I do a wipe, flash rom and then boot.img? Also, I've a broken volume button, so I flash the rom in recovery and then I do "adb reboot bootloader" and then flash boot.img, could this be causing this issue?
If it's not too much trouble could you upload system.img and boot.img backup from your phone of any custom rom? I would like to flash those from fastboot.
Thanks
tt33333 said:
Still no luck, it basically does the same thing for all roms. HTC logo shows up and then the screen goes blank with black light on. I've tried these roms:
cm-11-20140710-UNOFFICIAL-M8.1-ace.zip
ICESenseV1.1.zip
cm-7-20130301-NIGHTLY-ace.zip
MK44.4-ace-140719-RELEASE.zip
AoCP6_UW1_Port_for_Ace
I don't get any errors during the flashing process for all except the last one (AoCP6).
Also, the cm7 works sometimes and on other occasions it does the same thing as well. Could it be the sequence? I do a wipe, flash rom and then boot.img? Also, I've a broken volume button, so I flash the rom in recovery and then I do "adb reboot bootloader" and then flash boot.img, could this be causing this issue?
If it's not too much trouble could you upload system.img and boot.img backup from your phone of any custom rom? I would like to flash those from fastboot.
Thanks
Click to expand...
Click to collapse
Except Mokee 4.4.4 Release and CM11 M8.1 i used Philz but before that i was on CWM 5.8.1.5 and i had no issues with it. Also i've tried TWRP 2.7.1.0 too. Works perfect but i'm used to reboot into recovery by default option,which only available in CWM. Other recoveries boots into blank screen,If you powered off the device and put on charge.
Nope there isn't any sequence.... either you flash boot.img first or last it only helps in device to boot and have proper connectivity. Even if you don't flash boot.img then only your device should hang on bootloop or boots but no wifi reception. So these is something different.
Sure i can provide system.img and boot.img of M8.1 which i'm currently on. But how sure you're that it will work? I mean do you have a backup of it? Or fresh install. Also wanted to know have you ever tried format devlog partition and FULL WIPE your device?
Try using following attachments. FULL WIPE it's just an alternative of manual wipes,works with every recovery out there. And devlog partition will be formatted if any means of corrupted or remnant leftover using format_devlog zip. Meanwhile provide me details whether you got backup of M8.1 CM11 or going to flash fresh install. So that i can provide boot and system.img of it.
It's working now. Installed 4ext recovery and ran you'r script.
Thanks for all the help

Stuck on HTC logo(help)

Hello guys,
Just got my m9 a few hours ago, decided to root,s-off etc
Anyway, I did something stupid and Im stuck on the android logo.
Here is what I did.
-I updated the device through the stock recovery, there was another update but I didnt install i.
- unlocked the bootloader, phone rebooted and was working fine
-installed costume recovery(TWRP), I didnt boot into it because there wasnt and option like in the m8 to boot in recovery from bootloader.
-I reset the device and installed the update(stupid move I knew the stock recovery is not there)
- I got into TWRP and the updated failed so I had the SUbinary.zip so I plashed it and decided to reboot
-Here I got a note that theres no OS installed so I installed android Revolution, I placed it in the sdcard prior
- after flashing it I pressed on reboot yet I get no OS installed and now im stuck on the HTC logo.
BTW I can boot into boot loader but it says sd card not mounted (64GB)
Edit:
I entered into recovery, flashed AR again,its installs everything normally but I realized on the installation log last line : set_metadata_recursive: some changes failed
still I get no OS installed
I got it working now. Anyone whos having this problem just use the beta recovery because the official one is broken
here's a like https://basketbuild.com/devs/Captain_Throwback/One (M9)/Recovery
just flash it normally and install the rom again.
now i will have to go back to stock recovery and download the OTA the flash TWRP again -.-
will the OTA work on the ARHD and stock recovery or thats not possible?
mr.dj26 said:
Hello guys,
I got it working now. Anyone whos having this problem just use the beta recovery because the official one is broken
here's a like https://basketbuild.com/devs/Captain_Throwback/One (M9)/Recovery
just flash it normally and install the rom again.
now i will have to go back to stock recovery and download the OTA the flash TWRP again -.-
will the OTA work on the ARHD and stock recovery or thats not possible?
Click to expand...
Click to collapse
I dont think the OTA will work.
either find the latest full RUU and flash it, or an older RUU, flash it, then do all the available OTAs.
Then redo TWRP and ARHD.
x51 said:
I dont think the OTA will work.
either find the latest full RUU and flash it, or an older RUU, flash it, then do all the available OTAs.
Then redo TWRP and ARHD.
Click to expand...
Click to collapse
hey there, thanks for the reply.
I think ill do the s-off first then ill download the RUU like this guy http://forum.xda-developers.com/one-m9/help/tut-ota-successfully-1-32-401-15-to-1-t3091911
i wish i updated before
I did the same thing twrp no OS installed and restarted now I am stuck at the htc logo and I can't get it to restart. Please help?
I tried power and volume down and it's not responding.
edit:
pressed all the buttons and got into recovery. went into download mode and updated twrp and reflashed android hd. working now.
thunderwolf333 said:
I did the same thing twrp no OS installed and restarted now I am stuck at the htc logo and I can't get it to restart. Please help?
I tried power and volume down and it's not responding.
edit:
pressed all the buttons and got into recovery. went into download mode and updated twrp and reflashed android hd. working now.
Click to expand...
Click to collapse
Thats good to hear, sometimes TWRP will say that there isn't any OS installed but actually there is just reboot the device.
After updating through the OTA I installed ARHD and I got the same error again with the latest recovery. I think its because when I did wipe the data there root directory is changing make the phone unable to boot or there is a problem with the rom although it flashed before the update.
Here is a fix http://forum.xda-developers.com/one...h-recovery-t3066720/post59934542#post59934542
If it didn't work try to format data in the recovery and reboot. Make sure you have a ROM or back up on an SD card.
Since your phone is running I would suggest you to S-off because from what I understand is RUU (for Europe) will only work with S-off
http://forum.xda-developers.com/one-m9/general/htc-one-m9-dump-t3060545
hope this helps others

Cant enter recovery to flash ROM ..idk if bricked?

hi guys ..im new to this forum stuff so if im in wrong section im sorry lol.. ok.. so im not sure how to explain this, but i was flashing over my HTC ONE M9 and for some reason it bootlooped back to the bootloader after completion and i was flashing Android Revolution HD 20 .. and then i went to upgrade the TWRP to 3.0 and idk what happened but it failed and now i cant load into recovery mode or download mode.. it says 0PJAIMG missing.. it just says failed to boot into recovery and back to the bootloader and im not sure how to load back a stock ROM or any ROM for that matter..
You updated twrp. That is a no-no. There is only one working twrp and one working supersu.
Twrp 2.9.0.1 and supersu 2.65 is the only working combo.
Get the phone into download mode then Fastboot flash twrp 2.9.0.1. Reboot and it should at least fire up.
Sent from my HTC One M9 using Tapatalk
I am running ARHD 20 and twrp 3.0 without a problem, as are many people. But some have had issues.
How did you flash the new twrp? It sounds like you might have done something wrong.

Recovery hangs at splash screen after flashing 7.0 ROM...

Hello all,
Having a weird issue. I flashed a stock-based Nougat ROM today and everything went fine, flashed new bootloader/radio first and new vendor img after ROM. Set up the ROM without issues, everything running smooth. I just went to flash a custom kernel and found out that I can't seem to get into TWRP. When I reboot to bootloader and then select "Recovery mode" it brings up the TWRP splash screen but the recovery never loads, it just hangs there for several minutes. I've tried rebooting several times.
Anyone else having this issue? Afraid I might need to reflash the recovery but I'd like to avoid that if possible.
Thanks.
The_mamba said:
Hello all,
Having a weird issue. I flashed a stock-based Nougat ROM today and everything went fine, flashed new bootloader/radio first and new vendor img after ROM. Set up the ROM without issues, everything running smooth. I just went to flash a custom kernel and found out that I can't seem to get into TWRP. When I reboot to bootloader and then select "Recovery mode" it brings up the TWRP splash screen but the recovery never loads, it just hangs there for several minutes. I've tried rebooting several times.
Anyone else having this issue? Afraid I might need to reflash the recovery but I'd like to avoid that if possible.
Thanks.
Click to expand...
Click to collapse
You need to reflash recovery because you are on 3.0.2.0 and you need at least 2.1 or 2.2. Just fastboot that img and it'll boot
Stevica Smederevac said:
You need to reflash recovery because you are on 3.0.2.0 and you need at least 2.1 or 2.2. Just fastboot that img and it'll boot
Click to expand...
Click to collapse
Okay, thanks. Any idea if I will need to revert recoveries if I go back to 6.0 or are they backwards compatible?
The_mamba said:
Okay, thanks. Any idea if I will need to revert recoveries if I go back to 6.0 or are they backwards compatible?
Click to expand...
Click to collapse
No need, newest will work with MM

Categories

Resources