[Q] Stuck on booting screen - HTC One X+

So I'm rather new to installing custom roms and things of this nature so bear with me. I followed the guide corrisponding with my phone to install cyanogen mod on my phone and followed all the steps exactly at first, when I got to the end I noticed that it was not booting into cyanogen mod so I made sure to search the page again when I noticed the bottom note "This device, if unlocked with HTC Dev Unlock, MUST have its kernel flashed via fastboot! Extract the boot.img from the rom zip and flash using fastboot flash boot boot.img" So I figured that must be the fix so I did exactly as it said and tried to install the rom.zip again and reboot. Now whenever I try to reboot I get stuck at the "HTC ONE" screen. Any help ?
evitare_ul pvt ship s-on rl
hboot-1.40.0000

Related

Flashing Roms W/ HTC unlock Install works but wont boot

Hi Everyone. '
I have been trying everything to get a custom rom on my HTC View. I tried the multi tool, which was unsuccesful at downgrading. I also tried no sense roms both would go to a black screen after flashing.
This Time i tried flashing dexters JB rom. The aroma installer worked fine but it says succesfulley installed, however the last line on the aroma installer says
-> Flashing Kernel
assert failedackage_extract_file("boot.img", "/dev/block/mmcblk0p22")
It then gives me the option to select next or save logs.
I select next and go and flash the 1.6 patch.
next i flash google apps.
then power off.
Next power on,
White HTC screen, then a black screen. nothing.
This happened to every rom i Installed. I am using Clockwork mod recovery to flash these. Is there something else I have to do?
here is my bootloader screen
***Unlocked***
express PVT SHIP S-ON RL
HBOOT- 1.140005
MICROP- 0656
RADIO-1.05.01.1006_3
eMMC-BOOT
OCT 25 2011, 16:35:13
From there I would select recovery and the revolutionary CWM would come up, I will then wip everything, install zip from sd card.
If you're HTCDev unlocked you cannot flash a different boot.img in recovery. Extract the boot.img from the ROM you are trying to flash and place it in your android-sdk/platform-tools folder then use the following commands in a terminal.
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot erase cache
fastboot reboot

[Q] Another Flyer stuck in reboot loop after flashing DextersJB18

Hello,
I have a US 3G Flyer that my friend messed up while trying to root and reflash it. He asked me to revive it.
The device was stuck at the HTC logo during boot.
It must have had HC since the HBOOT is 1.11.0011. It was unlocked through HTCDev since it says UNLOCKED in the bootloader. However, it still has S-ON. The device has Revolutionary CWM 4.0.1.4 flashed as a recovery.
I tried to follow the instructions by globatron in http://forum.xda-developers.com/showthread.php?p=18508210 to downgrade to GB in order to run Revolutionary and get S-OFF.
fastboot getvar cid gives HTC__102
However, I do not have permission to read the thread that has the download links to the RRU: http://forum.xda-developers.com/showthread.php?t=1062184
So I went ahead and tried to flash DextersJB18 because it seemed from the thread http://forum.xda-developers.com/showthread.php?t=1795342 that some people flashed it sucessfully with HTCDev unlocked S-ON devices.
I downloaded the ROM zip file and gapps-jb-20121212-signed.zip, put that on the SD card, booted into CWM v4 and flashed this way:
1. Wipe factory data/reset
2. Wipe cache
3. Go into mounts and storage
4. Format /system
5. Format /data
6. Format /cache
7. Enter advanced
8. Wipe dalvik
9. Flash ROM (including wipe all) then flashed gapps
10. Booted to fastboot then "fastboot flash boot boot.img" (taken from DextersJB18.zip)
After I reboot, it never goes past the HTC logo. If I hold the power key, it shutdowns but reboots immediately. I know I go to the bootloader and say power off to prevent draining the battery.
Can someone please provide some insight into how I can get the device up and running again? Thanks. I really appreciate it.
Resolved
Well after another day of trying various things I finally got the device back up and running.
I figured out that for the HTC__102 model device I could use RUU_Flyer_HTC_WWE_2.00.405.3_R_Radio_20.3501.30.089BU_3809.05.04.10_M_release_194964_signed.exe to downgrade to Gingerbread. I googled that and found it on a random site.
After I found the correct RUU, I was able to follow globatron's instructions in http://forum.xda-developers.com/showthread.php?p=18508210 to downgrade to stock Gingerbread. The device booted OK into Gingerbread.
I then got S-OFF with Revolutionary and upgraded to Honeycomb by running ARUWizard.exe in RUU_3G_B09.zip. The device then booted OK into Honeycomb.
I then flashed DextersJB18 and gapps-jb-20120726-signed.zip from CWM recovery. Initially I had weird issues like the keyboard crashing because I used gapps-jb-20121011-signed.zip, which is ONLY for Android Jelly Bean 4.1.2, not 4.1.1. After flashing the correct gapps, things were OK.
The device now boots into Jelly Bean! Yea!
help, cant get boot or recovery
Hi hope you can help.
I have been running my flyer rooted on stock honeycomb with no trouble. I wanted to install Dexters JB18 rom, something went wrong after the install and now i can only access hboot screens, flyer wont boot, and recovery (was cwm with no issues) just brings up htc screen with nothing else.
I have tried flashing several recovery/boot images via fastboot, without any noticable effect. I get the messages saying image is written okay from command prompt but rebooting device or attempting to enter recovery just brings me white htc screen.
I have run getvar cid and got the result htc001, but attempting to reboot using adb gives the result device not found.
this is the info on the hboot screen
****unlocked****
flyer pvt ship s-on
hboot-1.11.0011
microp-0950
radio-3822.10.08.07_m
emmc-boot
A few threads here look promising, but i cant access them to be sure or find the right links, such as finding RUU type etc altho I dont think Im that far along until i can flash and get in to a workable recovery?
---------- Post added at 12:32 PM ---------- Previous post was at 12:14 PM ----------
Hi hope you can help.
I have been running my flyer rooted on stock honeycomb with no trouble. I wanted to install Dexters JB18 rom, something went wrong after the install and now i can only access hboot screens, flyer wont boot, and recovery (was cwm with no issues) just brings up htc screen with nothing else.
I have tried flashing several recovery/boot images via fastboot, without any noticable effect. I get the messages saying image is written okay from command prompt but rebooting device or attempting to enter recovery just brings me white htc screen.
I have run getvar cid and got the result htc001, but attempting to reboot using adb gives the result device not found.
this is the info on the hboot screen
****unlocked****
flyer pvt ship s-on
hboot-1.11.0011
microp-0950
radio-3822.10.08.07_m
emmc-boot
A few threads here look promising, but i cant access them to be sure or find the right links, such as finding RUU type etc altho I dont think Im that far along until i can flash and get in to a workable recovery?
adb driver?
ok, i think my issue is with adb.
with flyer in hboot so options are
fastboot
recovery
factory reset
clear storage
simlock
image crc
when i check device manager, it is listed as ADB interface, expand that and you get 'bootloader interface'
put flyer in fastboot mode, i see
bootloader
reboot reboot bootloader
power down
and the device is gone from device manager completely.
in either mode, when in adb running command 'adb devices' i get nothing, although running commands such as 'fastboot flash boot boot.img/recovery.img i get a success message after writing. 'fastboot reboot' will successfully reboot the device but it still does not boot up or enter recovery when attempted.
am i missing an adb driver or something?
Jelly Bean 1.8 No Wifi
I did the Same like you.
The device now boots into Jelly Bean! But i dont have wirless connection. It searches for wifi but dont find nothing.What should i do?
Where to download DextersJB18?
Hi, right now it's impossible to download DextersJB18 from dev-host, do you know any mirror link? Or kindly upload your saved ROM to other cloud storage? Thanks!
Better late than never...
I have been looking for dexterjb for a while now, thought I would search for it tonight and voila! There it is at
hmm, can't post external links. I could have sworn I was able to before...
?fid=746163614322263502 after androidfilehost.com/

[Q] HTC stuck on boot loader and can't restore rom

Hi,
I have been looking for a solution to my problem but I couldn't find any, anywhere, here included; hopefully someone can help me out.
I have an HTC One X+ 64GB International version which I unlocked via the HTC website, rooted and flashed Android Revolution HD.
Today, after a long while, I decided to try a different rom but somehow I totally screwed up (and I can't remember the exact steps) and now my HTC is stuck on the bootloader. I tried to flash different kernel for different roms (Sense and aosp) and flashed those roms.
No luck. I am successful in flashing a kernel and a recovery but every time I try to flash a rom (IceColdJelly, Android Revolution) it fails miserably.
So, now my HTC is stuck on the bootloader and I can't seem to be able to do anything to get it to work again.
Anyone can help with a step-by-step solution? I can provide more info if needed.
Here's what the bootloader screen presents:
***UNLOCKED***
ENRC2B_U PVT SHIP S-ON RL
HBOOT-1.35.0000
CPLD-None
RADIO-3.1204.168.32
Thank you in advance for any help.
Tell me, are you erasing cache after flashing the boot.img?
>fastboot flash boot boot.img
>fastboot erase cache
Which Recovery are you using?
Lets start with this.
HOX+ Stuck on logo
Could anyone help me
I did unlock the Hox+, after that I do the recovery
after that i want to change rom and other
looks like I made ​​a mistake and when I want to do recovery, the file recovery LOST
In other words my Hox+ currently can only go in the HTC LOGO, HBOOT and Recovery mode.
Anybody please help me what should i do: (
Hi wisd0ms,
If you want some help, please describe the more precisely what you have done and give us the maximum detail on your phone and also which carrier you are using.
HOX+ Stuck on logo
Okay then, I'll try to give the details of the case:
with the help of All-In-One_Kit_v2.3 and fastboot
while doing wipe, clear cache, factory reset and flash the kernel through recovery mode
the point is, I made ​​a mistake while in recovery mode and I can not find the data that exist
I use a carrier Hutchisen from hongkong
thanks for the reply & salute :fingers-crossed:
So I guess your phone is an International/Global version.
If so, then follow the instructions in this thread.
SOLVED thank you :good::victory:

[Q] HTC Desire 601 stuck in recovery

hi, i have a HTC Desire 601 with Virgin Mobile (in canada) and i tried to flash a custom rom, and it didnt work, i got an error 7, i tried several rom and all i got is a error 7.
now i want to go back to a stock rom , but every time i think i have a good stock rom, i get an error 7.
this is what appears in the bootloader
***TAMPERED***
***UNLOCKED***
ZARA_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.26.40e.00.14
OPENDSP-v.18.2.0268.0925
OS-2.14.666.3
EMMC-BOOT 1024MB
i flashed PhilZ Recovery (philz_touch_6.19.3-zara.zip is the exact filename), but i think i've done something wrong because everytime i try to flash anything, i get an error 7, even doing a nandroid backup gave me an error..
so, what should i do to get the phone to a working state?
thanks
skfunnyboy said:
hi, i have a HTC Desire 601 with Virgin Mobile (in canada) and i tried to flash a custom rom, and it didnt work, i got an error 7, i tried several rom and all i got is a error 7.
now i want to go back to a stock rom , but every time i think i have a good stock rom, i get an error 7.
this is what appears in the bootloader
***TAMPERED***
***UNLOCKED***
ZARA_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.26.40e.00.14
OPENDSP-v.18.2.0268.0925
OS-2.14.666.3
EMMC-BOOT 1024MB
i flashed PhilZ Recovery (philz_touch_6.19.3-zara.zip is the exact filename), but i think i've done something wrong because everytime i try to flash anything, i get an error 7, even doing a nandroid backup gave me an error..
so, what should i do to get the phone to a working state?
thanks
Click to expand...
Click to collapse
You either don't have the right recovery, correct roms. or you wiped the /system. Typically status 7 is from the updater-script checking the build.prop located in /system to see if you are trying to install it on the right device. I'm wondering about the recovery since not even your backup would restore. What was the error message when that happened?
But for me, I would try the version of Philz here:
http://androidforums.com/desire-601...stall-recovery-guide-htc-desire-601-zara.html
And still having the same trouble, and you know that the roms are the correct ones, you can try removing the asserts in the updater script like this:
http://www.androidgadgematic.com/2012/12/fix-custom-rom-installation-status-7.html
If you have wiped the /system, it might be easier to re-lock the bootloader and run the official RUU, if available.
If you do any of this and then manage to install the wrong rom, I claim no responsibility. Any mods are done at your own risk.
A friend of mine is in Zara Desire 601 too and we have a problem when we want to flash a .zip file. We have unblocked the bootloader on the HTC site and we would like now to achieve the root flashing a .zip file but when we copy the .zip file in the innternal memory we don't see it when we reboot in recovery (philz touch) the folder structure is not the same and we can't find our .zip file...Where we are wrong? thx!!!

Stuck "Entering Recovery..." After Flashing RUU, Unlocking, flashing TWRP

Hello,
I am having trouble returning my M8 back to stock. I am following this guide: http://www.droidviews.com/restore-att-htc-one-m8-stock-firmware/
I was able to flash RUU_M8_UL_K44_SENSE60_ATT_SECURITY_Cingular_US_1.58.502.1_Radio_1.16.21331931.LA11G_20.31A.4145.02L_release_368350_signed_2.exe without any issues, and then proceeded to unlock the bootloader successfully as well.
My issue is getting into TWRP after flashing. I issue the commands:
Code:
adb fastboot reboot
fastboot erase cache
fastboot flash recovery twrp-3.0.0-1-m8.img
And it says that the write is successful, but when I go back to HBOOT to boot into recovery, It gets stuck with the "htc" logo and a pink text "Entering Recovery..." at the top of the screen. If I do an
Code:
adb devices
, it shows my phone and status "recovery".
I'm thinking that the recovery flash isn't sticking or maybe I have the wrong version (I believe I flashed the latest). Or maybe its entirely something else but I'm starting to run out of options. I've also tried rebooting into the bootloader after flashing recovery and just doing "fastboot reboot" and then trying to go back into recovery from a powered-off state but I still get stuck.
Here is my current fastboot Info:
Code:
***UNLOCKED***
M8_UL_CA PVT SHIP S-OFF
CID-CWS__001 ;;I recently flashed this from Super CID
HBOOT-3.16.0.0000
RADIO-1.16.21331931.LA11G
OpenDSP-v38.2.2-00542-M8974.0311
OS-1.58.502.1
eMMC-boot 2048MB
Apr 18, 2014,16:06:33.24624
Thank you in advance for your help.
- Kristian
The RUU you used is far too old to work with the TWRP version 3.0.0.0. Mixing old/new hboot, OS versions with new recovery versions is usually a bad idea.
The fact the guide you are using is from 2014 (!) is doing you no favors. That RUU is 3 Android versions obsolete. Relock the bootloader, than run the (current latest) 4.28.502 RUU as linked in my Index thread: http://forum.xda-developers.com/showthread.php?t=2751432
What is your intent in returning to stock? That guide is far too complicated for most purposes, aside from returning to HTC for warranty (for which, most M8 devices no longer have valid warranty).
For most purposes, relocking the bootloader and RUU is good enough.
@redpoint73
Thanks for replying. I was able to successfully go back to stock for the most part. I wanted to do a factory reset to see if it would fix my camera issue (auto-focus was broken and constantly re-focusing). Anyway, it didn't immediately help, but somewhere along the lines the camera fixed itself. Thanks again!

Categories

Resources