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!
Related
I had a few problems with my HTC Desire he won't start after I did an update of Insertcoin (I did this update, like every other update).
So I thought that I had to re-root my phone.. Bad idea I think.
Now my sd-card is formatted so I don't have my gold-card anymore
and I can't boot my phone.
When I boot it, in the top right and left corner and bottem left and right corner there is the debugging logo (so the triangle with the '!') and in the middle of the screen HTC logo.
EDIT: I also cannot go to the bootloader or fastboot I can only see the screen above nothing else.
EDIT2: I tried and original RUU but I don't know which one I had to use..
I don't know what to do, so please help me!
Sounds like you've flashed the wrong RUU. This happened to me, I've got a Vodafone Desire, flashing the newest HTC Europe RUU restored my HBOOT but still didn't boot (so you could try that I guess), so I used fastboot to flash recovery and then a new ROM. Good luck to you.
Oh yeah also, if you've installed a custom HBOOT and then tried to use a RUU it may be the cause of the problem since it wouldn't have been able to flash the system partition. Although it doesn't appear as to be working, I tried to flash the stock HBOOT through fastboot when my phone was like that, and after the RUU finished installing I did have the stock alpharev one and not my cm7 one.. Just something that might come in useful.
I've tried this solution here but it doesn't work for me.
Yes, it's working again.
This is the solution.
I downloaded this RUU and install it and now it works
I'm new at this sort of. I've got this HTC wildfire s(A510c, CDMA), I recently rooted it(successful), I wanted to get a custom rom so i decided to download ROM manager and install clockwordmod as you had too in order to get they're roms. I downloaded a rom that was based on Sense 3.5, I left the package and everything as is, i tried "installing from the SD" i backed up, and rebooted into clockworkmod booting screen, i installed it from sd cleared the cache and so on but still no changes but it froze several times and eventually completely rest, i tried it one more time, it froze and now its stuck on the white HTC screen and won't go any further but i can still access HBOOT and Clockworkmod Bootloader but bootloader likes to freeze on me a lot, can you help me? that would be greatly appreciated
dreammaster252 said:
I'm new at this sort of. I've got this HTC wildfire s(A510c, CDMA), I recently rooted it(successful), I wanted to get a custom rom so i decided to download ROM manager and install clockwordmod as you had too in order to get they're roms. I downloaded a rom that was based on Sense 3.5, I left the package and everything as is, i tried "installing from the SD" i backed up, and rebooted into clockworkmod booting screen, i installed it from sd cleared the cache and so on but still no changes but it froze several times and eventually completely rest, i tried it one more time, it froze and now its stuck on the white HTC screen and won't go any further but i can still access HBOOT and Clockworkmod Bootloader but bootloader likes to freeze on me a lot, can you help me? that would be greatly appreciated
Click to expand...
Click to collapse
Look for the ruu that goes with your phone. You can probably find it in football's thread. Run the ruu and that should get you back to original state. When you go install a rom, make sure it's for your phone, otherwise you can brick it.
Edit : Here's a link to the US Carriers RUU's. Make sure you use the right one: http://forum.xda-developers.com/showthread.php?t=1432425
stuck at htc logo
dreammaster252 said:
I'm new at this sort of. I've got this HTC wildfire s(A510c, CDMA), I recently rooted it(successful), I wanted to get a custom rom so i decided to download ROM manager and install clockwordmod as you had too in order to get they're roms. I downloaded a rom that was based on Sense 3.5, I left the package and everything as is, i tried "installing from the SD" i backed up, and rebooted into clockworkmod booting screen, i installed it from sd cleared the cache and so on but still no changes but it froze several times and eventually completely rest, i tried it one more time, it froze and now its stuck on the white HTC screen and won't go any further but i can still access HBOOT and Clockworkmod Bootloader but bootloader likes to freeze on me a lot, can you help me? that would be greatly appreciated
Click to expand...
Click to collapse
search syed zain ahmed on utube and watch his video , ur problem will be solved as it helped me a lot thanks.
i am new and cant post the link here.. after 10 post i can post a link so it might take a while for me.
So... I am gone try and put my question in this post as detailed as I can... And I really hope that someone can help...
I have an HTC Wildfire S (Marvel, bought in Denmark) that had 2.2.1, I wanted to use ICS on it and so I started researching for a good ICS ROM. My phone had the below,
Marvel S HTC Europe
HBoot 1.09.0099
2.26.401.3 Radio 47.23e.35.3038H 7.57.39.10M
I decided to flash the below ROM,
Paranoid Android pa_marvel-1.6a-beta1-24AUG2012-142650
My steps were the following,
1. Went on HTCDEV.com and unlocked the bootloader
2. I downloaded the necessary SDK files on a folder on C drive (adb.exe, AdbWinApi.dll, AdbWinUsbApi.dll & fastboot.exe) I then used the following command to flash a recovery “fastboot flash recovery recovery-clockwork-5.0.2.8-marvel.img”, this was a ClockWorkMod official recovery.
3. When I tried to access the recovery it seems that it was ok but I had a black screen with the tactile buttons switched on for about a minute and then it booted... I research in XDA and I found a solution... the following.... http://forum.xda-developers.com/showthread.php?t=1781105 it is a small jave software that enables you PC screen to display your htc screen when it is black to actually see what is happening... this saved me!!!!!! Thanks to “rajanand”....
4. After I managed to see my recovery on my PC screen I flashed Paranoid Android... doing always the norm of Wiping Data, Cache and Dalvik first.
5. When I tried booting I only got the HTC White Screen logo and nothing else... (PANIC!!!) I assumed there was something wrong with the ROM.
6. I then flashed CM9 from Alquez... doing always the norm of Wiping Data, Cache and Dalvik first.
7. When I tried booting I only got the HTC White Screen logo and nothing else... (PANIC AGAIN!!!)
8. I then decided to put it back to its original state by running the official RUU of the phone by downloading it from here http://forum.xda-developers.com/showthread.php?t=1074445
9. When I run the RUU, but first I relocked the bootloader with the following command in the bootloader “fastboot OEM Lock”, (RUU_Marvel_S_HTC_Europe_2.26.401.3_Radio_47.23e.35.3038H_7.57.39.10M_release_261695_signed), the phone got an error 140, meaning that my bootloader was a higher version... and the is not other RUU which is higher than this... so I was a bit stuck and confused as to how this happened.
10. I WAS REALLY NERVOUS...
11. I then read a post from someone, I can’t remember saying that only EQDKP ROMs worked for him.
12. I unlocked the bootloader again using the same key when I unlocked it the first time. Keep it.
13. And I flashed the following, [Drk_mod]EQDKPv4.9_multi_deodexed_mhr.zip, and finally my phone booted in the ROM and it is currently working...
See below a screen shot from the Java program and my cwd... it seems that this ROM things a bit different when flashing things or is this a misunderstanding...
Can anyone explain why NO OTHER ROM is working?
Had a working CDMA VM HTC ONE V running on slim bean. Wanted to update to newest version of Slim Bean so also decided to downgrade the HTC V to stock VM RUU ROM first to get rid of OTA update issues with custom ROMS. Anyway that wouldn't work cause the RUU wizard said the HBOOT was lower or something. Anyway, decided to forget stock VM firmware and just wanted to reflash Slim Bean but now I can't get into recovery nor will Slim Bean fully boot. I can get into fastboot and tried flashing recovery several times. I still can't enter it -- it just sticks at white HTC screen. If I just try to regular boot into the current ROM, it just sticks at boot screen. What should I try to do now? STUCK big time.
Thanks.
Finally got recovery to boot. Not sure how but I just kept trying to install and enter and it finally worked. With that could reinstall Slim Bean. All this started with the inability to downgrade from 928 (I think that's the number) radio and 1.57 HBoot. Is there anyway to do this now? I found older threads that said you're unable to downgrade from that but I don't know if that's still the case (?)
dawg1 said:
Finally got recovery to boot. Not sure how but I just kept trying to install and enter and it finally worked. With that could reinstall Slim Bean. All this started with the inability to downgrade from 928 (I think that's the number) radio and 1.57 HBoot. Is there anyway to do this now? I found older threads that said you're unable to downgrade from that but I don't know if that's still the case (?)
Click to expand...
Click to collapse
I have no idea on the CDMA one V, but for future reference if it doesn't flash, just boot the recovery straight up:
fastboot boot nameofrecoveryimghere.img
There is no known way that I am aware of to downgrade the device from the updated hboot. but there is a kernel available in the slim bean thread at the very top of the downloads area that allows the newer hboot owners to use slim bean cdma with only minor bluetooth audio issues.
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