Booting stuck on HTC logo - Desire HD General

Hello,
I want to install custom ROM on my Desire HD. I had some problems, which thanks to forum member, I have solved ( this thread ). I found that I can unlock my device to install custom ROM's using htcdev.com site. I have done everything, what I had to do. On HBOOT now I have *** UNLOCKED *** on the top, but still I have S-ON. I installed root-test application, where was the message, that phone has root. Then I have installed EXT4 recovery and Blackout ICS v 3.0. After that, booting stuck on HTC logo and nothing happens. I tried with other ROM's and theres the same issue. I can't use RUU files also - it throws an error when it's checking signatures.
What I supposed to do ?

Cause the flashing method is different if you were to have s-off. You need to extract the boot image and do it that way. That's about all I know.
Sent from a dream.

Thanks a lot!!!
I have flashed boot.img from extracted zip file by fastboot and now everything works fine.

Related

Flashing problem on Magic_Rogers 3.54.631 rom

hi everybody!
some days ago i flashed my magic (TIM Italy, so 32A) whit the Magic_Rogers3.54.631.3 rom, that was a ruu exe file.
It flashed my spl and radio, that now are hboot-1.76.0010 (SAPP10000) and 6.35.16.19.
Now i wanted to change rom because of the language (i'm not able to put an italian dictionary when i write), but i don't succeed.. i tried to reflash the recovery, but i can't because fastboot says that is not possible to send data to the phone, so i can't also boot some recovery image.. same problem via adb or via terminal on the phone.
i rooted the phone with the last universal androot, but it's the same..
i succeeded to change recovery only with rom manager, but the phone doesn't go in recovery mode (it's still on the "rogers" splash screen), or if it goes, it reboot alone after a few seconds.
oh, at last, i'm not able to flash other rom, like the RUU_Sapphire_HTC_Europe_3.05.401.1_test_signed_NoDriver or my original TIM rom.
I'll be really grateful to who will help me!!
thanks for reading!
download this application FlashRec
install it to your device
then download any of Amon_RA recovery imgs (HERE) (Choose the correct one for your device)
then push it to your sdcard
then open the FlashRec and press backup,
then write in the blank box "sdcard/xxxxx.img"
where xxxxx is the name of the img you pushed to your SD
then press flash .. if it is successful, connect your phone to adb
and write "adb shell reboot recovery"
I tried this on 32A 1.33.0010 and Radio 3.22,
I'm NOT 100% sure it will work with you,
try it at your own risk.
it says "phone type is EBI1/32A"
i press backup with or without the name in the box,and the result is
"backup failed: could not run command."
first: this is the false place for this thread. this is for general!
second:
follow this thread http://forum.xda-developers.com/showthread.php?t=756918
it is not possible to flash or backup with flashrec. the new roms are bugfixed.
renedlog said:
first: this is the false place for this thread. this is for general!
second:
follow this thread http://forum.xda-developers.com/showthread.php?t=756918
it is not possible to flash or backup with flashrec. the new roms are bugfixed.
Click to expand...
Click to collapse
I think you are right, because i was on stock 1.5 when i used this method.
OmarAta said:
I think you are right, because i was on stock 1.5 when i used this method.
Click to expand...
Click to collapse
me too... but the htc magic 32a with the actual stock rom, android 1.5 with sense form january, is already bugfixed.
Moving to General
sorry for the mistake, i thought it was the right section..
anyway i followed the guide in the post linked by renedlog and.. it worked!!! i didn't know where to put the flash_image file.. but it was written there.. so i did all, and now my rom is the RCMagic 5.0!
do you think it's good to try something different?
i use RCMagic 4.2
the version 5 is still a little buggy with the wake up from standby.
i will upgrade to an android 2.2 rom, if there is an update today for the 32B and hopefully it will be patched to my 32A.
yeah, i saw that bug.. it's really a pity, the rom was a little faster than the 4.2..
i suppose it would not be a big bug, so i hope somebody that is able will fix it!!
are there so big changes beetwen the 2.1 and 2.2?

Is there a chance for my (new) Magic ?

Hi all,
Well, that's the way, it sometimes goes....
On Tuesday i received in exchange my new Vodafone Magic. After only two days i'm stuck with a "deadlock" situation. Following happened:
The Magic was delivered with the standard 1.6 Donut on it. I then manually flashed the OTA update to 2.1.1 and the apps that I use regularly. Yesterday I used the "Gingerbread.apk from the XDA forum to gain root. Armed with root, i downloaded Rom-Manager from the Market and installed ist. Next, i installed the Clockwork Recovery via Rom-Manager. Then reboot into the recovery and Voila .... Clockwork recovery.
Ok, first thing i did was to make a backup of my current ROM and then came the big mistake ...
I wanted to have a black Notficationbar in OTA. So i flashed "blackbar.zip" from "http://www50.zippyshare.com/d/43974308/12150/blackbar.zip". But after reboot it didn't work (Bootloop).
Well, I thought I reboot back into the recovery and restore my backup.
And then came the shock ...
What I saw then was not the Clockwork recovery but the original HTC Magic recovery.
Ok, tried to flash the 2nd part of the OTA Update again.... Nope. The HTC Recovery reports "Assert Failure". Obviously checksum tests are done and after flasing the blackbar, "framework-res" no longer matches the checksum.
OK, so back to 1.6 with the NBH Image .... Nope, The Magic reads the image, but refuses to install with the comment "main version is older"
Since the OTA update, installs an "S-ON" Spl, no more fastboot...
Searched in Google and found a lot of Posts saying "try using this image", "try using that image", but nothing worked.
So the Situation now is as follows:
- Magic can not start anymore. Bootloop in the "android" Bootscreen
- Fast boot is not possible because of the SPL
- New import of the OTA update, part 2 not possible due to checksum error
- Back to 1.6 not possible due to "Main version older"
- I only have the the original Magic Recovery. (and of course can boot into HBOOT / FASTBOOT mode)
What I would need would be a flash-ready image of Enginnering SPL or an update, however, in the format, which is accepted by the original recovery of the Magic. I also dealt with the idea of creating a Goldcard. Could this be a way to save my Magic?
Has anyone else an idea, or anyone knows how to create a flash-ready image, which is accepted by the original recovery?
Thanks and greetings. lagloose
Is this a 32B or 32A? I've been in that situation before. If you can get into fastboot you can save it. Get a RUU (for 32A I used 3.5.401 from Rogers) and install it. In the process, it'll try to get the phone into fastboot mode, but it's already there, so you'll factory-reset it. After that, you can apply an Engineering SPL through update.zip (using the recovery from the RUU itself, not AmonRa or others's) and then you can do anything else you want on your device.
Good luck! ^^.
I think you're going to have to make a goldcard, which is a problem since you can't boot. If you can somehow make (find?) a goldcard then you should be able to flash a RUU. Can you post you're device specs? Vodafone Magics are supposed to be 32A's right?
I don 't know your phone information,but i think you need a goldcard and flash ruu

[Q] Cannot boot into any custom ROM!

A friend of mine wanted to change the stock rom on his old tmobile MyTouch 4G to CM7.2
It is currently running the latest 2.3.4 (hboot_0.89.0007, radio 12.62.60.27_26.13.04.19), I unlocked the phone following the steps from HTC Dev website. And they explained that unlocking is enough to flash custom rom since it enabled write access to recovery, system and boot http://www.htcdev.com/bootloader/about_unlock_process.
I was able to flash and run both TWRP and CWM (twrp2.2.2.1-glacier-recovery & recovery-clockwork-touch-5.8.1.0-glacier) adn used them to flash CM7.2 stable and the latest nightly and some other custom ROMs i found on the developers forum at XDA, however, not of them do boot. The phone will get stock at the first screen showing Tmobile and myTouch 4g logo.
I followed many threads/steps that recommended downgrading to stock froyo first to turn security off (S-OFF) but it won't let me since it is older version, then some says to downgrade the radio first, but that is also not possible with S-ON and i get signature error. i tried doing it from the sd-card using the file name "PD15IMG.zip" for the stock rom but didn't work neither from the fastboot rebootRUU thingy.
From the recovery i wiped every thing even system, then checked it to make sure it is empty, flashed CM7.2 and mounted system and there are the files as they should be but it won't boot, and "adb devices" won't show anything so i cannot see the log. which means it didn't even start.
Am I missing something trivial?
* BTW, i had to lock the bootloader again to flash the stock 2.3.4 back, but I have the unlock token "Unlock_code.bin" and I can unlock it again if someone knows the answer to this problem

HTC One M9e -- HIMAR Bootloop after custom rom install...

Hi Guys...
I have no idea how you guys deal with these problems, and I take my hat off to you. Asking for help is never my first option, and this is what probably leads to more problems than a resolution. I have no choice. I have to send my pride to his room right now...sigh...
I was trying to install ViperOneM9_4.3.0.
The phone details are here...
--
bootloader kernel: lk
bootloader kroduct: htc_himaruhl
bootloader version: 1.0
bootloader version-main: 1.03.709.13
bootloader boot-mode: download
bootloader version-bootloader: 1.01.0000
bootloader cid: 11111111
HTC Download Mode Details...
--
***unlocked***
htc_himaruhl PVT S-OFF
CID-11111111
Device is rooted and TWRP 3.0.0.1 HIMAR installed.
---
Under the impression that once the phone is in current state, I can install Custom ROM.
I loaded ViperOne unto Phone Storage and used TWRP Recovery to install zip. Install reported success and phone was rebooted.
Phone now stuck in reboot loop.
I may have made matters worse by erasing cache and deleting system folder, etc...
I did make a TWRP recovery backup. I have those files.
I've also downloaded numerous files, including 2PRGIMG_HIMAR_UHL_L50_SENSE70_hTC_Asia_TW_1.03.709.13_Radio_1.1506V24P52.2508.0910_HT[W.T]_release_454911_signed_2_4.
I get "invalid sparse file format at header magi" error when using..
fastboot oem rebootRUU
fastboot flash zip rom.zip
Much thanks for any assistance offered...
You're trying to run 6.0 twrp and roms on top of 5.0 firmware. That's the problem. You need to update your firmware to MM.
iElvis said:
You're trying to run 6.0 twrp and roms on top of 5.0 firmware. That's the problem. You need to update your firmware to MM.
Click to expand...
Click to collapse
Ok, so you're saying TWRP currently installed is the wrong one? ...but it's working. I can finally boot into recovery mode.
What would be my solution? As of now, if I unplug the phone from the USB cable, it does not reboot, it's just there with a blank screen and a flashing orange light.
cnsops said:
Ok, so you're saying TWRP currently installed is the wrong one? ...but it's working. I can finally boot into recovery mode.
What would be my solution? As of now, if I unplug the phone from the USB cable, it does not reboot, it's just there with a blank screen and a flashing orange light.
Click to expand...
Click to collapse
What he meant was your base firmware is on Lollipop and you are trying to flash a marshmallow rom over the top. They are not compatible.
You need to either flash a Lollipop based rom or update your "FIRMWARE" to marshmallow and then flash a marshmallow based rom (viper 4.3.0) over the top and it'll work.
You're s-off. You can flash unsigned zips to update to marshmallow. Simple and fast. (cid might cause issues and need changing temporarily).
Beamed in by telepathy.
Is the M9e (codename: HIMAR) even compatible with roms made for the M9 (codename: HIMA)? Since it already needs a different TWRP than the M9 I highly doubt that you can use the Viper rom on your phone.
Edit: I just googled the specs of the M9e. It's a mediatek device which means you definitely cannot use M9 roms.
Sent from my HTC One M9 using XDA Labs
Hi Guys..
Sorry for no reply... It's a leap year and leap years, mean pure problems.
I have backup files via TWRP on the PC. In TWRP recovery option, I do not see any Backups to restore, probably because I wiped everything.
Can I use the backup files on my PC to restore the phone?
Thanks...
https://super-firmware.com/index.php?a=browse&b=category&id=4854
3$ 1 day
Tapatalk kullanarak iPhone aracılığıyla gönderildi
maybe this it's already solved, but i had the same problem. i wanted to flash at least android 6 but i can't found a way.
any way i solved de reboot whit this (i'm not allowed to post links):
- search for himar_uhl in androidfilehost.com
- this is the filename: 2PRGIMG_HIMAR_UHL_L50_SENSE70_hTC_Asia_TW_1.10.709.2_Radio_1.1506V24P59.2508.1112_HT[W.T]_release_464157_signed_HBoot.zip
PD: i don't know if my english it's correct.
igoh said:
maybe this it's already solved, but i had the same problem. i wanted to flash at least android 6 but i can't found a way.
any way i solved de reboot whit this (i'm not allowed to post links):
- search for himar_uhl in androidfilehost.com
- this is the filename: 2PRGIMG_HIMAR_UHL_L50_SENSE70_hTC_Asia_TW_1.10.709.2_Radio_1.1506V24P59.2508.1112_HT[W.T]_release_464157_signed_HBoot.zip
PD: i don't know if my english it's correct.
Click to expand...
Click to collapse
got bootloop on my htc one m9e (HIMAR) need Original Stock ROM anybody knows where i can get them?
Snaki99 said:
got bootloop on my htc one m9e (HIMAR) need Original Stock ROM anybody knows where i can get them?
Click to expand...
Click to collapse
Does anybody have the RUU Firmware.zip for M9e?
2PRGIMG_HIMAR_UHL_L50_SENSE70_hTC_Asia_TW_1.10.709 .2_Radio_1.1506V24P59.2508.1112_HT[W.T]_release_464157_signed_2_4
http://forum.gsmdevelopers.com/htc-...g-_himar2_ml_uhl-mtk-official-stock-roms.html
http://forum.gsmdevelopers.com/downloads.php?do=file&id=19
twrp here
https://www.mediafire.com/folder/2wd1oprpj5ija/HTC_M9_PCE
command in fastboot console
htc_fastboot flash recovery twrp-3.0.2-1-himar2.img

COS13 rooting failed, stuck in boot loop

Hi all,
I got a brand new Wileyfox Storm which I liked to have rooted. When I booted the phone I got several updates which I installed first.
After updating I followed this guide: http://forum.xda-developers.com/wileyfox-storm/general/root-wileyfox-storm-t3250992
And also with a little bit help from the Cyanogen wiki: https://wiki.cyanogenmod.org/w/Install_CM_for_kipper
Reason I chose for this method is because I tried the recommended WinDroid Toolkit before but the server doesn't has the required files anymore so that program is useless for the Wileyfox Storm.
I'm running Cyanogen Os version 13.1.2-ZNH2KAS3NA-kipper btw (offical FOTA).
When I followed Bobslesbricoleurs tutorial to unlock the bootloader I got a message but not one I expected. It said:
<bootloader> Device already : unlocked !
OKAY [ 0.000s]
finished. total time : 0.000s
Does this mean I got my Wileyfox Storm with bootloader already unlocked? That how I read it...
I continued to start rooting it, but not before testing if I could still boot but everything was fine.
I tried to flash the attached custom recovery I got OK and a 'remote: size too large' error. It didn't successful flashed the recovery.
I checked if everything still was ok and it was. I could boot and everything.
So I tried something different. I'm not new to flashing (I've had a Galaxy S2 for 5 years which was running on CM13) so I went to the Cyanogen site and downloaded the latest stable (snapshot) recovery for kipper which was cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J4-kipper-recovery.img.
I tried to flash that recovery and it succeeded. I could still boot recovery and system... except that after booting system the ROM would replace the recovery back to stock.
I did some research on this but I couldn't find any helpful information about it for the Storm device. So I Googled it in general and read somewhere that COS had a developers toggle to disable 'updating recovery'.
This is probably where I made my mistake because I unchecked that update recovery toggle and reflashed the snapshot recovery that worked before.
I'm not very sure, I should have written this down, but if I remember correctly the system could still boot.
I didn't know how to flash the SuperSu-v2.46_signed.zip with fastboot, the tutorial didn't specify this and I'm used to flashing from recovery (fastboot is kinda new to me, although I have worked with adb commands before).
So I booted the rom, installed AirDroid to push the zip to my internal storage and I went back to the recovery.
I flashed the SuperSu-v2.46_signed.zip with the update option in the recovery.
And now the rom is in a boot loop.
I already tried a full factory reset but it's still boot looping.
I know that in the tutorial topic FluffyTwit has had a similar problem, not sure if it's the same but it looks like it.
The given solution is "Flash stock boot.img from stock rom zip, reboot" to which he replied " flashed the whole .zip file because I saw a tutorial on some website...".
But at this stage I'm a bit afraid that I'll do it wrong again, as the instructions are either out-dated or they're just not 100% correct. Could someone help me out and/or confirm the exact steps I should do to get my device back up and running?
I'd rather keep the device stock without root than rooting it with risks of bricking. I have a feeling this device isn't as safe to rooting as I'm used to..
Thank you in advance.
Edit: I've found my solution and had to change something.
You can read it here starting from Edit 2.
http://forum.xda-developers.com/showpost.php?p=68632922&postcount=84

Categories

Resources