Strange problem - HTC Desire Eye

Firstly 1 month ago my phone started rebooting itself randomly and I was using s-team desire eye and I tried to upgrade to S5.2 X10.0.8u and it didn't worked phone goes into endless bootlop after that I tried to flash every rom and no one worked. And finally I tried stock rom in this thread firstly I think it worked firstly "android is upgrading" screen comes and after that first install language screen comes and it freezes for 1-2 second and bootloop again. Any help?
EYE_UL
UNLOCKED
S-ON
TWRP 3.0.0-0

I'm not sure, but your phone is s-on, and switching from MM back to LP is not good idea... maybe you should try to install stock MM rom?

Download the Lollipop RUU from the HTC's website and try it. Maybe that works...

Related

[Q]Phone does not boot, can only go to bootloader

Hi guys,
So i researched a few days before trying to root, install a custom rom (LeeDroid) and flash a custom rom
I managed to do it yesterday and everything was working fine. It is a really great rom.
But today I powered down my DHD and I can't boot anymore. The phone keeps rebooting (it vibrates one time, i see the HTC green logo, then a black screen, vibrates and so on...). The only way to stop this process is to hold the vol- key wich takes me to bootloader (so it appears the phone is continuosly powering off and on)
I already tried and bootloader is working fine, but when a I try any option that requires a reboot, the phone starts this process of power up and down.
Does anyone have any idea of whats happening?
Thanks guys!
Did you perm root your phone?
You could try reinstalling the stock rom too.
Go to bootloader, select recovery, do a full wipe and reflash your ROM. If you get a bootloop when you enter recovery, get stock RUU from XDA and use that.
Yeah I permrooted it.
But, how can I install a new rom without recovery?
I thought that you already flashed LeeDroid, and if you did, you have ClockworkMod recovery. But if that is not the case, use a RUU.
jkoljo said:
Go to bootloader, select recovery, do a full wipe and reflash your ROM. If you get a bootloop when you enter recovery, get stock RUU from XDA and use that.
Click to expand...
Click to collapse
Sorry man... I overlooked this post...
To better describe what I did:
-Radio s-off
Eng S-off
Instaled Leedroid (followed every recomendation he did in the post)
Flashed the radio he suggested
Got the phone working, tested a little bit, charged and then I powered off
When powered on again I got this bootloop
______________________________________
So, do you still recomend RUU?
Can I find any guide here on XDA?
Thanks!
edit:Forgot to mention that I get the bootloop even if I choose recovery on bootloader
edit2:
So after I came home I found de RUU post.
So here are some questions:
Mosts of the RUUs are in .exe extension, so I think that's the ones I should be looking for.
Can I download any version?
I'm currently downloading de WWE Asia version since my phone came from India. Only English (india) was available from stock, but I will not try to do anything before I'm sure of what to do.
When I plug the usb cable the bootloader changes to USB bootloader (or something like that). From the little that I found aboutt RUU I should run with the phone on that condition. Is that correct?
Thanks again, and sorry for the constant editing
Really sorry for double posting, but I need to update.
I managed to install the RUU. The program worked fine and I got the confirmation of installed rom, but when the phone rebooted it got stucked on the bootloop again.
Can this be a hardware problem? Is there anything else that I can do having access only to bootloader?
Okay, it is a hardware problem. The RUU wipes everything clean and installs a new system, and as it does not seem to help, the problem is definitely in hardware side.
After I was almost giving up I tried a different version of the RUU and the phone booted!
I already rebooted it a few times and it seems ok.
Thanks for the help jkoljo!
Nice job, which RUU did you use?
I think that there was a bad block in your phone's internal memory, which got fixed when the RUU wrote on it a few times.
jkoljo said:
Nice job, which RUU did you use?
I think that there was a bad block in your phone's internal memory, which got fixed when the RUU wrote on it a few times.
Click to expand...
Click to collapse
I used the Asia_WWE_1.32.707.1
I was trying to use a 1.72 version and still got the bootloop, but the asia version worked just fine.
I´m really glad the phone is working now, the only downside is that I´m back to the stock rom.

HTC One x (protoype) bootloop after jellybean update

HTC One x (protoype) bootloop after jellybean update
Hey guys, This is my first post ever on XDA so please forgive me if I sound like an idiot
I got hold of a HTC One x which was already had an unlocked bootloader, rooted and had CWM recovery installed. I was told that I have a prototype version of the one x. Anyway that is not issue. when I got the phone it was running android version 4.0.4 HTC Sense version 4.1 and I checked software update. The 3.14.401.27 OTA update was available so I proceeded with the update and after the reboot I found my phone stuck in a bootloop and the only way for me to sort it out was by restoring my nand back up from CWM. I really wanted the new Sense 5 UI and android jelly bean so I downloaded:
RUU_ENDEAVOR_U_JB_45_S_hTC_Asia_TW_3.14.709.20_Radio_5.1204.162.29_release_292865_signed.exe
My CID was HTC__621 thats why I downloaded that ruu but after flashing it not was I only stuck in a bootloop but also when I entered recovery mode it was just a blank black screen with the back lights on. I even flashed different versions of CWM recovery and TWRP which gave me the same black screen so I flashed the stock recovery.img which also gave me the same black screen. I thought me maybe a different Ruu would resolve this issue so I used 'JBFWTOOL21' to change my CID to '11111111' this allowed me to flash:
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.27_Radio_5.1204.162.29_release_298897_signed.exe
&
RUU_ENDEAVOR_U_JB_45_S_HTC_Europe_3.14.401.31_R_Radio_5.1204.162.29_release_302015_signed.exe
After trying both these ruu's I still found my device stuck in a bootloop. Next I downloaded 'Endeavoru_CustomRUU' this contained a 'rom.zip' which I belive was a jelly bean rom and said it would update my image version to '3.14.401.31' after flashing this ruu, my phone booted up past the 'HTC Quietly Brilliant' screen but into a black screen but I could hear the boot sound and knew it booted up but it still gave me a black screen. barre in mind this was the only rom that booted up and didn't get stuck in a bootloop but the downside was I had no picture on the screen it was literally pitch black with the backlight on when it went past the 'HTC Quietly Brilliant' boot screen. I didn't even see the one x boot animation. I could only hear the boot up sound and once it was booted up the notification LED would flash I was receiving network settings from my operator. That was about it. I booted into recovery to see wether that worked but unfortunatelly it was also still giving me a black screen. The only thing I could boot into without a problem was 'power button + volume down' which booted into bootloader in which I chose 'fastboot' to flash all these roms.
At this point I thought my device was soft bricked so I gave it to my friends father who happened to really good with his IT skills. He managed to change my device's CID from 'HTC__621' to 'HTC__001' after doing so he downloaded this ruu and flashed it:
RUU_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2_Radio_2.1204.135.20_release_274900_signed.exe
This ruu turned out to work perfectly fine with my device. Everything functioned once again, the device was able to boot into recovery and boot normally without a hassle. I also discovered that this was the rom that I received my phone with which put me back to the start on android 4.0.4
I was really annoyed with the fact that I was stuck on ICS so I flashed the MaximusHD 21.1.0 rom and its boot.img which put me into a bootloop again. I also tried other custom roms such as Revolution and SD secxces which all put my phone in a bootloop even though I flashed their boot.img kernels. I knew that I required a hboot 1.33.0000 or above in order to flash jb roms so I used 'JBFWTOOL21' once again before flashing these custom roms to update my hboot from 1.12.0000 to 1.33.0000. so all these bootloops still occourd after doing all this and I just had to return back to ICS. barre in mind I only tried flashing JB roms as I want sense 5 so I don't know if a custom ics rom would work on my device as I havent tried it yet but I know for a full fact that none of the jb roms work on my device.
For those who are wondering here, I uploaded some pictures of my device just go to the top of the page where it says "Reason:" I put a link in it just copy and paste the link in your browser, sorry but this is the only way I can share links as I don't have 10 posts. The pictures show all the information you may want to know about my device (HTC One X PROTOTYPE).
I really hope someone can help me update to jelly bean and get sense 5 as I am frustrated from failing and being stuck in bootloops
If you read all of this I honestly appreciate it and Thank you for it, I hope you can help me!

Unable to flash new rom

hi friends.. basically i am unable to install any new rom on my Redmi 1s, I searched almost everything but couldn't find the solution.. so i am posting it here... i will try to describe my problem below..
Back a few months i was using CM 12.1-20150603-UNOFFICIAL-armani.. then a OTA update came i installed it joyfully.. but my joys didn't last longer as a noticed that after booting my Wifi always shows "Turning WiFi On" but never got really opened. So i flashed back to old version... Then i installed Xtreme Music Mod and and the Earpeice Speaker went off... So i thought of flashing again, This time I flashed Flex OS.. was sucessful and then days later i installed xposed and got struck in bootloop due to an improper mod... due to my noobness i staraight away tried to flash flex OS again and then the install was successful but after the initial boot phone worked for like 30 seconds then freezes and reboot.. this happened again and again untill i flashed the CM 12.1-20150603-UNOFFICIAL-armani again... in middle of all this i tried using Multirom but was unsucessful....
And NOW MY PHONE WON"T ACCEPT ANY ROM OTHER THAN CM 12.1-20150603-UNOFFICIAL-armani
I tried changing recovery, gone through the Fastboot flashing and doing things a fresh
but every time i install a rom My phone either freezes on "ANDROID IS UPGRADING" or it boots completely and then freezes and reboot...
I hope someone has a solution for this.. coz m dying to use MM ..
Thanks
niimtz said:
hi friends.. basically i am unable to install any new rom on my Redmi 1s, I searched almost everything but couldn't find the solution.. so i am posting it here... i will try to describe my problem below..
Back a few months i was using CM 12.1-20150603-UNOFFICIAL-armani.. then a OTA update came i installed it joyfully.. but my joys didn't last longer as a noticed that after booting my Wifi always shows "Turning WiFi On" but never got really opened. So i flashed back to old version... Then i installed Xtreme Music Mod and and the Earpeice Speaker went off... So i thought of flashing again, This time I flashed Flex OS.. was sucessful and then days later i installed xposed and got struck in bootloop due to an improper mod... due to my noobness i staraight away tried to flash flex OS again and then the install was successful but after the initial boot phone worked for like 30 seconds then freezes and reboot.. this happened again and again untill i flashed the CM 12.1-20150603-UNOFFICIAL-armani again... in middle of all this i tried using Multirom but was unsucessful....
And NOW MY PHONE WON"T ACCEPT ANY ROM OTHER THAN CM 12.1-20150603-UNOFFICIAL-armani
I tried changing recovery, gone through the Fastboot flashing and doing things a fresh
but every time i install a rom My phone either freezes on "ANDROID IS UPGRADING" or it boots completely and then freezes and reboot...
I hope someone has a solution for this.. coz m dying to use MM ..
Thanks
Click to expand...
Click to collapse
*go to cm12.1 thread
*download and flash firmware.zip from post #3 and flash it
*wipe all in twrp(leave internal,external,usb otg)incase you want to wipe internal too,don't forget to make a backup before on pc.
*flash R31+5.1.1 gapps(i will prefer open gapps)
*wipe cache and dalvik
*reboot

HTC one m9 firnware upgrade issues

I was trying to upgrade my firmware according to the main thread
everything looked ok but i noticed that it was very fast
after it completed i flashed the new recovery
tried to install the new viper rom but got into bootloader every time i rebooted the phone
i managed to restore previous rom from backup but i cant install new roms
anybody know how can i fix this?
thanks in advance
Try flashing firmware again. It probably failed with error 90, which just means you have to immediately flash again. If that doesn't work, post your terminal output from when you flash so we can see what error you're getting. Booting straight to bootloader screen indicates you're trying to use a marshmallow rom on lollipop firmware

M9 in bootloop, TWRP stopped working

Hello all, my M9 has been crazy since some days. I have a lot of different problems and haven't been able to see what the common issue is, so I will list everything I know:
1. European M9 unlocked, baseband 01.01_U11440792_97.00.51203G_F, OS-3.35.401.32
2. Had official Android 6.0 and couldn't update OTA to Nougat (update crashing after 25%) so I tried rooting and flashing a custom ROM (RR-N-v5.8.0-20170106-himaul-Unofficial). Worked without problems for 3 months and 2 days ago my phone restarted and didn't boot to the rom anymore (I see the HTC logo with white background and red letters, after 10 seconds or so I see the logo of my rom but it freezes and restarts again, over and over again).
3. Tried flashing the same version stock rom with RUU method (renaming it to 0PJAIMG.zip and place it in sd card) and this failed because of a problem with the zip signature.
4. Tried another custom rom (ViperOneM9_6.1.0) and the same situation (I see the rom logo but freezes and restarts again)
5. After flashing the 2nd rom, my TWRP stopped working (I see the logo of TWRP and freezes, restart)
6. I tried using fastboot commands to boot to recovery and nothing happens, tried flashing different TWRP versions and still freezes.
So at the moment the working modes are only download and bootloader.
Any ideas of where the problem is?
I'm pretty used to flashing custom roms but never had such problems before, so my knowledge doesn't go that far. Also if you need logs, please give me some instructions on how to get them. Thanks

Categories

Resources