Hi,
This is the first time i'm installing a custom rom on my One X and every rom I tried takes too long (15min) to boot up and then i actually give up and try something else
I've tried:
CM10
ICJ 1.6
and some others but they keep getting stuck at htc logo screen
Can somebody help me out and tell me what i'm doing wrong?
This is what I do:
I've rooted and unlocked bootloader
1) go into fastboot
2) flash boot.img
3) go to recovery
4) wipe cache and dalvik cache
5) install rom with recovery
6) wipe cache and dalvik cache
7) install gapps
8) wipe cache and dalvik cache
9) reboot
That is the procedure i saw on many threads and sites.
Problems?:
One thing i noticed was that when going to HBOOT I get the following: failed to open usb master mode
Roms that did work
Android Revolution HD 18.1 and 9.8, I think that's because of the aroma installer and I don't have to do anything
But Android Revolution HD worked very slow and laggy for some reason...
Any help is greatly appreciated. Have been searching everywhere for 2 days know and can't figure it out
Boot.img needs to be flashed after you install the ROM.
Otherwise the ROM will flash over the Boot.img (atleast I think thats how it works)
By the way, no ROM would take 15 minutes to boot, if it does you're in a bootloop.
Bellerophr0n said:
This is what I do:
I've rooted and unlocked bootloader
1) go into fastboot
2) flash boot.img
3) go to recovery
4) wipe cache and dalvik cache
5) install rom with recovery
6) wipe cache and dalvik cache
7) install gapps
8) wipe cache and dalvik cache
9) reboot
That is the procedure i saw on many threads and sites.
Click to expand...
Click to collapse
I don't know where you got the instructions from, but they're horribly wrong and overly redundant.
This is what you should do when flashing a new rom:
1. Boot to recovery
2. Wipe data/factory reset
3. Flash rom and gapps (if necessary)
4. Reboot into fastboot (adb reboot bootloader)
5. Flash boot.img
6. fastboot erase cache (if you're having problems, usually unnecessary)
That's all. For upgrading the same rom (say, to a newer version), you can skip step 2.
Wilks3y said:
Boot.img needs to be flashed after you install the ROM.
Otherwise the ROM will flash over the Boot.img (atleast I think thats how it works)
Click to expand...
Click to collapse
That only applies to non-HTC phones or HTC phones with s-off. Phones with s-on like the HOX will not flash boot.img via recovery, only fastboot. Other phones have their boot.img flashed via recovery directly, skipping the fastboot bit as it is redundant.
1st: wrong forum, you have to post that in Q/A
2nd: you dont have to flash the boot.img after ROM, the ROM cant overflash it because we dont have s-off yet
3rd: are you sure you are using the right kernel (boot.img) for the ROMs you are trying to flash. After the hboot updates (JB) we got some changes on what you can flash and what not.
Sent from my EndeavorU using xda premium
First of all Sorry for posting in the wrong forum and thankyou for the replies.
I have tried the things you guys said and it still didn't work
the boot.img i use are the ones included in the zip.
EDIT:
Got it working with ICJ:
http://www.youtube.com/watch?v=O0j_sESAIds&feature=youtu.be
And you are sure that you can use that specific ROM with your curent firmware ? Is your hboot 1.31 and above (did you perform the JB OTA) ?
Sent from my EndeavorU using xda premium
sometimes you also need to fastboot erase cache because at sense roms it can help...try that if it won't work did you flashed any mods after that?
muamers said:
And you are sure that you can use that specific ROM with your curent firmware ? Is your hboot 1.31 and above (did you perform the JB OTA) ?
Sent from my EndeavorU using xda premium
Click to expand...
Click to collapse
No i'm not sure (will search how I can find out), yes I have hboot 1.31, yes I have performed JB OTA.
I have also done fastboot clear cache
If you want to use CM10 on a JB hboot you need a modified boot.img file
http://db.tt/uDdWaAtH
With this one and a full wipe it will boot fine
The failed to open usb master error is due to the cable that is connected to the pc, plug it off and try it again. The error will be gone
Sent from my GT-P5110 using xda app-developers app
Mr Hofs said:
If you want to use CM10 on a JB hboot you need a modified boot.img file
http://db.tt/uDdWaAtH
With this one and a full wipe it will boot fine
The failed to open usb master error is due to the cable that is connected to the pc, plug it off and try it again. The error will be gone
Sent from my GT-P5110 using xda app-developers app
Click to expand...
Click to collapse
Thank you very much! I will try it.
Bellerophr0n said:
Hi,
This is the first time i'm installing a custom rom on my One X and every rom I tried takes too long (15min) to boot up and then i actually give up and try something else
I've tried:
CM10
ICJ 1.6
and some others but they keep getting stuck at htc logo screen
Can somebody help me out and tell me what i'm doing wrong?
This is what I do:
I've rooted and unlocked bootloader
1) go into fastboot
2) flash boot.img
3) go to recovery
4) wipe cache and dalvik cache
5) install rom with recovery
6) wipe cache and dalvik cache
7) install gapps
8) wipe cache and dalvik cache
9) reboot
That is the procedure i saw on many threads and sites.
Problems?:
One thing i noticed was that when going to HBOOT I get the following: failed to open usb master mode
Roms that did work
Android Revolution HD 18.1 and 9.8, I think that's because of the aroma installer and I don't have to do anything
But Android Revolution HD worked very slow and laggy for some reason...
Any help is greatly appreciated. Have been searching everywhere for 2 days know and can't figure it out
Click to expand...
Click to collapse
From what i've noticed on my HTC One X the steps to install ROMS on it is the same but in a pattern!
1)Boot recovery and install the rom THEN the gapps
2)Factory Data Reset (If coming from a sense rom to a AOKP/AOSP(cyanogenmod for example)
3)reboot in fastboot then flash the boot image.
That should be all.
If it's a sense rom your flashing then the rom is corrupted.
i4GS said:
From what i've noticed on my HTC One X the steps to install ROMS on it is the same but in a pattern!
1)Boot recovery and install the rom THEN the gapps
2)Factory Data Reset (If coming from a sense rom to a AOKP/AOSP(cyanogenmod for example)
3)reboot in fastboot then flash the boot image.
That should be all.
If it's a sense rom your flashing then the rom is corrupted.
Click to expand...
Click to collapse
First of all ....he had his instructions ....secondly
2 : factory reset after installing the custom Rom.....lol then it won't boot up anymore. You can't factory reset a custom rom hahaha
Sent from my HTC One X using xda premium
Related
Appreciated any help I can get here.
I'm attempting to flash my first custom ROM by following the instructions here (http://drippler.com/updates/share/how-unlock-root-install-custom-rom-your-htc-one-x).I've got to point 5 and instead of copying the zip file and boot.img to my phone I stupidly went and carried out the 'fastboot flash boot boot.img' command first. The result is the phone just hangs on the boot screen.
I can get back into recovery OK, but after a couple of hours searching I'm struggling to see how I can resolve this. I have tried a full restore from recovery but it didn't work.
I assume I have to put the boot.img and ROM zip file back on the phone and repeat the process. I cannot find a way to enable me to do this as I cant seem to mount the phone on the PC.
Thanks in advance.
You can mount the sdcard as a usb mass storage device inside the recovery. What recovery do you have ?
You flashed the new boot.img already ? All you have to do is enter the recovery and perform a full wipe before you install the new rom. Of the rom is not on the phone sd you mount it first and copy the rom over. Then continue to install it
Mr Hofs said:
You can mount the sdcard as a usb mass storage device inside the recovery. What recovery do you have ?
You flashed the new boot.img already ? All you have to do is enter the recovery and perform a full wipe before you install the new rom. Of the rom is not on the phone sd you mount it first and copy the rom over. Then continue to install it
Click to expand...
Click to collapse
I have Clockmod v5.8.1.8
No I didn't transfer the boot.img file from the new ROM to the phone. I just typed 'fastboot flash boot boot.img' into the command prompt. The new boot.img file was in the fastboot folder.
http://db.tt/Krlm4dPs
Flash the above recovery, you have an old one that does not support usb mass storage !
Ow and the boot.img does not have to be on the phone, only the rom.zip to install it. The boot.img file is only flashed in fastboot as you did. No need to do anything else.
When you enter the new recovery you go to
MOUNTS & STORAGE - mount as mass storage device (most bottom option)
Mr Hofs said:
http://db.tt/Krlm4dPs
Flash the above recovery, you have an old one that does not support usb mass storage !
Ow and the boot.img does not have to be on the phone, only the rom.zip to install it. The boot.img file is only flashed in fastboot as you did. No need to do anything else.
When you enter the new recovery you go to
MOUNTS & STORAGE - mount as mass storage device (most bottom option)
Click to expand...
Click to collapse
OK, thank you. New recovery installed, zip file transferred. Wipe cache partition & Wipe Dalvik Cache completed. Install from zip file completed. Re-boot and it still hangs.
I'm using the CM10 nightly from 17/2/2013 if this presents a problem at all?
I've also tried 'fastboot erase cache', which has no effect either.
Flash this boot.img
http://db.tt/uDdWaAtH
Also wipe everything ! Also data factory reset and under mounts and storage - format cache,data,system
Otherwise it will not boot again
Mr Hofs said:
Flash this boot.img
http://db.tt/uDdWaAtH
Also wipe everything ! Also data factory reset and under mounts and storage - format cache,data,system
Otherwise it will not boot again
Click to expand...
Click to collapse
Appreciate you taking time to help me out. Thank you. Were still not there though, it's still hanging on the first boot screen.
The CM10 zip file is only 171MB which seems awfully small to me. I'm currently downloading the Viper Rom 3.3.7 which is 625MB. Could this be part of the issue? Am I trying to flash just an update and not full ROM?
Nope, AOSP ROMs are small in size. The zip you have is legitimate full ROM.
TToivanen said:
Nope, AOSP ROMs are small in size. The zip you have is legitimate full ROM.
Click to expand...
Click to collapse
Thank you, that's that theory out of the window, I think this bloody phone may follow it !
Try this.....
First in recovery do
Wipe data factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts and storage - format cache, data, system
Then install the rom.zip, dont reboot and install directly the gapps.zip
Then you type
Adb reboot bootloader
Flash the boot.img again (for cm10 the modded one)
Fastboot flash boot boot.img
Fastboot erase cache
Fastboot reboot
*fingers crossed*
Mr Hofs said:
Try this.....
First in recovery do
Wipe data factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts and storage - format cache, data, system
Then install the rom.zip, dont reboot and install directly the gapps.zip
Then you type
Adb reboot bootloader
Flash the boot.img again (for cm10 the modded one)
Fastboot flash boot boot.img
Fastboot erase cache
Fastboot reboot
*fingers crossed*
Click to expand...
Click to collapse
Boom! Sorted, I think it was the fingers crossed bit that finally did it!
Many thanks for your help this afternoon, it is much appreciated. I'll buy you a pint if your ever in Sheffield.
Thanks ! I will add that to my todo list !!! Checked : trip to Sheffield !!!
Nice you tot it sorted ! :thumbup:
CASE CLOSED !
Also you probably want to flash a new recovery as well. Clockwork recovery has a habit of failing on one x phones. TWRP is currently the most stable recovery for One X.
Sent from my One X using xda premium
Greygollum said:
Also you probably want to flash a new recovery as well. Clockwork recovery has a habit of failing on one x phones. TWRP is currently the most stable recovery for One X.
Sent from my One X using xda premium
Click to expand...
Click to collapse
Can you explain that a bit more.....im using cwm sinds i had my good old desire. Never had a single issue with it. Never one failed flash or backup restore....
Sent from my GT-P5110 using xda app-developers app
CWM sucks on One X. The evita one x that is.
Yeah he's not so quick with an answer so i guess he's on a slow dual-core evita phone
Greygollum said:
Also you probably want to flash a new recovery as well. Clockwork recovery has a habit of failing on one x phones. TWRP is currently the most stable recovery for One X.
Sent from my One X using xda premium
Click to expand...
Click to collapse
It was the second thing I did! I'm now wondering why it's took me this long to finally root and install a Custom ROM on my android phone. Thanks for your help. :beer:
Sent from my HTC One X using xda app-developers app
No problem. I had issues with CWM failing to flash correctly on the One x. I have had no problems with TWRP. I have heard dozens of complaints about CWM in a few different phones especially the One x.
BTW I respond slow because I work for a living.
Sent from my One X using xda premium
Greygollum said:
No problem. I had issues with CWM failing to flash correctly on the One x. I have had no problems with TWRP. I have heard dozens of complaints about CWM in a few different phones especially the One x.
BTW I respond slow because I work for a living.
Sent from my One X using xda premium
Click to expand...
Click to collapse
Keep your pants on mate, it was just a joke....
I've tried lots and lots of things for hours now and I've still been stuck in the boot screen of htc for the past 4 hours. And yes, I've googled so much and tried all solutions that people have had, and it's still not working.
I have tried wiping, installing ROM, go into recovery, fastboot flash boot boot.img, reboot and it hasn't worked for me.
I've tried both TWRP and CWM to install my ROM. I have a backup in TWRP that I did before it derped, but it doesn't turn my phone into working state again.
The ROM I'm trying to activate is the Cyanogen Mod 10.1 from the weekly link.
Only once I managed to get the Cyanogen boot screen (it got stuck there too), but after flashing my boot.img it disappeared. I tried updating my hboot with something I downloaded.
What have I done wrong? After reading all those threads, I'm totally clueless.
What is your hboot number ?
Mr Hofs said:
What is your hboot number ?
Click to expand...
Click to collapse
HBOOT-1.39.0000
Also its S-ON, but after googling I think everyone's One X is S-ON.
Oke do this
If you have cwm 5.8.4.0 (otherwise flash it to follow these steps)
Enter the recovery and perform a full wipe
Data/factory reset
Wipe cache partition
Mounts and storage-format cache,data,system
Advanced-wipe dalvik cache
install the CM10.1.zip (do not reboot after)
install gapps (do not reboot after)
Then type in the fastboot window :
Adb reboot bootloader
Flash the boot.img file from the rom
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Fastboot reboot !
Fingers crossed
Mr Hofs said:
Oke do this
If you have cwm 5.8.4.0 (otherwise flash it to follow these steps)
Enter the recovery and perform a full wipe
Data/factory reset
Wipe cache partition
Mounts and storage-format cache,data,system
Advanced-wipe dalvik cache
install the CM10.1.zip (do not reboot after)
install gapps (do not reboot after)
Then type in the fastboot window :
Adb reboot bootloader
Flash the boot.img file from the rom
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Fastboot reboot !
Fingers crossed
Click to expand...
Click to collapse
I followed your steps so precisely... but it didn't work Also I think I've done something close to this process before and had no success.
What you did differently though, I never installed gapps, and I didn't know that you can wipe dalvik cache in CWM.
What I had to do during your method though was go into mount SD storage and insert a fresh copy of both the gapps and CM10.1.
If you need any more information I'd gladly provide them as quick as possible, I'll be refreshing this thread constantly
Try my steps again but this time use a completely different rom. Try a standard sense base rom. Just to check if its booting ! Ow and you can leave the step for gapps away. And you can choose to do the boot.img thing first and then the recovery part.
This one maybe
http://forum.xda-developers.com/showthread.php?t=2063556
If it does not boot up we are missing something somewhere ... You are actually flashing the boot.img from the rom correctly ....also flash the boot.img from the rom .... Its inside the rom.zip
Mr Hofs said:
Try my steps again but this time use a completely different rom. Try a standard sense base rom. Just to check if its booting ! Ow and you can leave the step for gapps away. And you can choose to do the boot.img thing first and then the recovery part.
This one maybe
http://forum.xda-developers.com/showthread.php?t=2063556
If it does not boot up we are missing something somewhere ... You are actually flashing the boot.img from the rom correctly ....also flash the boot.img from the rom .... Its inside the rom.zip
Click to expand...
Click to collapse
I downloaded ViperX_2.6.0 instead (http://forum.xda-developers.com/showthread.php?t=1745176), since it was pretty much done right before you added the suggestion. The guide there tells me to flash the boot first then install the rom, but I did the rom first. IT WORKED! Thought it was stuck in the bootscreen again haha. I got to the unlock screen, but after unlocking all I saw was the HTC symbol. I then held the power button and pressed restart. Same thing after restart. After unlocking, all I see is a white screen with the HTC symbol in the middle. Can only lock the phone :/ Is it me or the ROM?
Or the phone ! Strange ..... But you must flash a JB rom to check if your bootloader supports it. The viper x 2.6 is an old ics one and runs on any hboot.
Actually is doesn't matter what you do first ..... It works both ways.
Test the bugX Rom. Flash the boot.img that is inside the bugX.zip copy it out to the fastboot folder and flash it directly from there. Make sure to full wipe again and install the rom .....I don't know what else....doing it like this for months and never failed.
Mr Hofs said:
Or the phone ! Strange ..... But you must flash a JB rom to check if your bootloader supports it. The viper x 2.6 is an old ics one and runs on any hboot.
Click to expand...
Click to collapse
Nevermind it worked after waiting a long time! The ROM works! Thanks!
But now, how do I go and fix CM10.1? I'm thinking I might have downloaded the wrong CM10.1 file since it was only 171MB and this ROM is around the 600MB range.
YOke now test a true JB rom. Read my post above to check the hboot !
And CM10.1 is that small. I don't know why it does not work ! Installed it this week on somebody else's phone just like i described here .....
CM10.1 ROM
http://d-h.st/Sgu
GAPPS
http://goo.im/gapps/gapps-jb-20121212-signed.zip
BOOT.IMG
http://d-h.st/Q2Y
Mr Hofs said:
YOke now test a true JB rom. Read my post above to check the hboot !
And CM10.1 is that small. I don't know why it does not work ! Installed it this week on somebody else's phone just like i described here .....
CM10.1 ROM
http://d-h.st/Sgu
GAPPS
http://goo.im/gapps/gapps-jb-20121212-signed.zip
BOOT.IMG
http://d-h.st/Q2Y
Click to expand...
Click to collapse
Alright I was gonna try the bugX ROM to test out if JB Roms worked, but I'll try CM10.1 once again using only the links you posted above. Will report back!
EDIT: IT WORKED! IT TOOK 6 HOURS BUT IT WORKED! Oh my god thank you SO MUCH! I have no idea what I did wrong though!
It might be the choice of CM10.1 type, or something. I just used your first method with your files and it just worked instantly!
Once again, thank you so much for bearing with me for so long haha.
I have a proble...
I tried to instal viper 3.3.7 rom and I failed it stuck on htc screen. Than I tried to do my nandroid backup cm 10.1 b6 and the phone can not reed sd card. It behaves like it is not there. When I go to recovery there is that folder 0 and than i cut and paste all from that folder back to rot of the phone but even when I tried clean install of cm 10.1 b6 it did not stick. What Do I have to do to have everything working again.
Please help.
I have an extraordinary patience mate
Have fun with CM10.1 :thumbup:
After a few unsuccessful attempts to flash my HTC One X up to CM10.1, I found out my hboot version was too low, so after much reading, trying and failing etc. I managed to get my hboot up to 1.36 (even after having my phone stuck at the white HTC boot logo for about 2 hours), but I still cant install the version of CM10.1 that I spent hour trying to do at the weekend (cm-10.1-20130312-NIGHTLY-endeavoru.zip) it still fails at the hboot checking point.
My main question is what would be the process that I would need to get the lastest version of CM10.1 to work?
Details from my phone
hboot - 1.36
CID - ORANG001
RUU - 2.17.61.3
I know there is a new boot.img that needs to be flashed after CM10.1 has gone in and was reading earlier about the stable releases, which is fine I have no problem with that, but I just cant figure out why I still cant flash 10.1 even after hboot upgrade which was a pain having to go back to a stock rom after re-locking my bootloader etc.
I know this stuff gets asked so many times, this is probably a repost but I just dont want to have to troll through hundreds of posts if the process is just, flash this, now this... done...
Thanks for reading.
Check for something called "vendor" it needs to be installed after the rom. Dont shoot me for this info....i haven't checked it myself ! But read something about it from the sideline
Go to CM thread in original dev section, in first post you can find a vendor installer zip that you must flash in recovery after flashing the ROM.
This is due to vendor files being taken down (DMCA),that's why latest zips have them missing and can't boot.
Sent from my One X using xda premium
LOL TT the sideline posting ninja !!!
TToivanen said:
Go to CM thread in original dev section, in first post you can find a vendor installer zip that you must flash in recovery after flashing the ROM.
This is due to vendor files being taken down (DMCA),that's why latest zips have them missing and can't boot.
Sent from my One X using xda premium
Click to expand...
Click to collapse
Yeh but thats my problem, how can I flash the vendor installer after the rom when I cant actually get the rom to flash in the first place?
If I grab the lastest nightly from clockworkmod app on my phone, tell it to wipe cache and then install rom, it reboots the phone like normal, I get the ruu replacement screen it does some of it, then flat out fails at the hboot check, I then have to use recovery to reboot the phone and it back on the original rom but I have to setup everything again (install apps and such, connect to my google account for contacts etc)
Bump
The steps are
Make a FULL wipe in the recovery
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & Storage - format cache,data,system
Then install cm10.1, gapps,vendors - DO NOT REBOOT IN BETWEEN AND ALSO NOT AFTER THE INSTALL !
now head back to the bootloader
Adb reboot bootloader
And flash the boot.img from the cm10.1.zip file
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Fastboot reboot
Should be it !
So I've bought my phone secondhand a few months before, rooted and with ARHD 9.X.
Then I decided I want a JB custom ROM and tried to upgrade to ARHD 19.2 (JB), and also Viper X 3.4.0 (JB). - NO LUCK.
I,ve upgraded HBOOT to 1.39 and followed all the steps required for Jelly Bean upgrade (or so I think).
ISSUE
After flashing, my HOX managed to boot the system, even start the start up process, but after a minute or two everything froze up and restarted, again boot, restart... Some kind of a bootloop.
Then I just went to the older version of Viper X 2.7.0.
I really want a new JB custom ROM, but can't have it because I'm obviously missing something.
Please assist...
Here are some screenshoots with software information. cidnum: HTC__032
http://forum.xda-developers.com/attachment.php?attachmentid=1830866&stc=1&d=1364160760
http://forum.xda-developers.com/attachment.php?attachmentid=1830867&stc=1&d=1364160760
Did you flash the boot.img from the new viper rom ? And did you perform a FULL wipe in the recovery before you installed the new rom ?
And for additional info, can you do a fastboot command for me
Fastboot getvar version-main
AW: Can't flash any JB custom ROM
If you didn't flash the the boot img then download it from the ARHD thread. There is a bat. Which do it for you. Very easy
Sent from my HTC One X using xda premium
I did flash boot.img that was on the viperx's thread, also tried with the .bat file when I was trying to flash new ARHD ROM.
Before flashing every ROM I did factory reset/wipe, wiped cache partition and wiped dalvik cache.
Mr Hofs, I did the following command:http://forum.xda-developers.com/attachment.php?attachmentid=1832227&stc=1&d=1364214488
May i suggest you turn to stock first to check its all fine
http://bugsylawson.com/index.php/fi...-r-radio-5120416229-release-302015-signedexe/
Download the ruu, put the phone in the bootloader/fastboot usb mode ....lock the bootloader
Fastboot oem lock
Then right click the ruu and select " run as administrator"
ok, so I just installed the stock rom with your instructions and my HOX froze again... really frustrating.
do U have any more ideas what can I do?
vander4 said:
ok, so I just installed the stock rom with your instructions and my HOX froze again... really frustrating.
do U have any more ideas what can I do?
Click to expand...
Click to collapse
Hey , I have that same problem , HOX branded from Orange , unlocked bootloader , flashed recovery CWM 6.0.9.7 , full wipe , flashed rom :
[ROM] HTC One X *STOCK* ROM | 3.18.401.1 | Jelly Bean | HTC Sense 4+
Flashed boot.img from rom and phone freeze at startup logo ...
I read 61 pages in rom development and see few ppl have that same problem but no one answer nothing usefull ...
please help ...
but I actually manage to get past the startup logo and I am able to enjoy JB for a minute or two..... then freeze.
freemaind, I've read a lot of posts with the same problem as yours, but i didn't find any that actually had the "freeze" within the newly installed ROM.
vander4 said:
but I actually manage to get past the startup logo and I am able to enjoy JB for a minute or two..... then freeze.
freemaind, I've read a lot of posts with the same problem as yours, but i didn't find any that actually had the "freeze" within the newly installed ROM.
Click to expand...
Click to collapse
So you installed the ruu with succes ? If so and it still happends there is something wrong with the phone !
But on a ICS (viper x 2.7) rom you do not have this problem ?
Mr Hofs said:
So you installed the ruu with succes ? If so and it still happends there is something wrong with the phone !
Click to expand...
Click to collapse
Yes, I did.
But if something is wrong with my phone, how can I have ICS ROMs with no problem but not JB?
relock it and run ruu, get update to stock jb and flash the other rom. enjoy
Sent from my HTC One X with ARHD 19.2/XM-Kernel 273/Lyapota ModPack 5.3 with resManager 2.4 using xda premium
pisc3s1203 said:
relock it and run ruu, get update to stock jb and flash the other rom. enjoy
Sent from my HTC One X with ARHD 19.2/XM-Kernel 273/Lyapota ModPack 5.3 with resManager 2.4 using xda premium
Click to expand...
Click to collapse
What are you talking about it IS the jellybean ruu !
And if you would have read the thread you could see he already updated the hboot to be able to run JB roms, and he also did.....he has trouble starting the roms. But ICS roms work fine !
pisc3s1203 said:
relock it and run ruu, get update to stock jb and flash the other rom. enjoy
Sent from my HTC One X with ARHD 19.2/XM-Kernel 273/Lyapota ModPack 5.3 with resManager 2.4 using xda premium
Click to expand...
Click to collapse
Tried that, no go... still freezes.
Vander....
Could please write down ALL the exact steps you take with installing the new rom ?
From boot.img , recovery actions .... all used commands ... Etc etc etc
a few months ago I installed JB RUU and actualy managed to update it via software update.
That just reminded me that I was able to keep stock rom active without freezing when it was on charger. how weird is that?
anyway, this is how I did the software update. but as soon as I jacked the charger out, it froze again.
i don't know what else I can do, except stay with my current ROM. but I'm not happy with that.
any constructive suggestion or ideas would be great. thanks
Mr Hofs said:
Vander....
Could please write down ALL the exact steps you take with installing the new rom ?
From boot.img , recovery actions .... all used commands ... Etc etc etc
Click to expand...
Click to collapse
1.downloaded RUU from your link
2. fastboot mode -> cmd -> command: fastboot oem lock ->phone relocked
3. run RUU as administrator, followed steps as instructed on the installer
4. after a few minutes phone rebooted and loaded stock rom, took me to setup
5. went through setup process, then check software version, browsed through the phone a little and freeze
Sorry ..... I ment when you install a custom rom !
But now it goes well when you keep it on the charger but it goes wrong when you unplug it ?
Mr Hofs said:
Sorry ..... I ment when you install a custom rom !
But now it goes well when you keep it on the charger but it goes wrong when you unplug it ?
Click to expand...
Click to collapse
yes. but that happened only with stock rom. i tried that with ViperX JB and it didn't work.
did you ever hear of such case?
Yesterday i tried Viper X 3.4.0:
1. downloaded ROM and boot.img from http://forum.xda-developers.com/showthread.php?t=2087443
2. put ROM to SD card
3. reboot to fastboot usb mode
4. open CMD in fastboot folder - > entered: fastboot flash boot boot.img -> OKAY
5. unpluged USB from phone, went to recovery in fastboot mode
6. CWM recovery -> wipe data/factory reset -> wipe cache partition -> wipe dalvik cache
7. install zip from SD card, browsed to ViperX 3.4.0 and selected it
8. went through setup process, chosen wipe data in installation (just in case)
9. finished installation
10. HOX loaded ROM successfully, started setup, after few moments FREEZE
Oke try this :
Flash the viper x 3.4.0 boot.img
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Unplug the cable and enter the recovery.....
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then install the viper x 3.4.0, choose a full wipe in the aroma installer and choose kernel - viper delivered.....
Reboot after install
Mr Hofs said:
Oke try this :
Flash the viper x 3.4.0 boot.img
Fastboot erase cache
Fastboot flash boot boot.img
Fastboot erase cache
Unplug the cable and enter the recovery.....
Factory reset
Wipe cache partition
Advanced - wipe dalvik cache
Mounts & storage - format cache, data, system
Then install the viper x 3.4.0, choose a full wipe in the aroma installer and choose kernel - viper delivered.....
Reboot after install
Click to expand...
Click to collapse
Tried exactly as instructed, no luck. Same problem.
Hi, (not sure if I'm in the right section of the forum, sorry if I'm not)I'm new to this forum and rooting. I have currently installed CM 10.1.2 on my HTC One X.
Everytime I try to install a new ROM it gets stuck on the boot animation after installation is done.
I follow the steps like flash boot.img, wipe caches, flash rom.zip...
Am I doing something wrong?
Thanks in advance
Salim1995 said:
Hi, (not sure if I'm in the right section of the forum, sorry if I'm not)I'm new to this forum and rooting. I have currently installed CM 10.1.2 on my HTC One X.
Everytime I try to install a new ROM it gets stuck on the boot animation after installation is done.
I follow the steps like flash boot.img, wipe caches, flash rom.zip...
Am I doing something wrong?
Thanks in advance
Click to expand...
Click to collapse
after you flash the rom in recovery you have to get into fastboot mode, and using you'r PC flash the boot.img that you extract from the rom zip file
fastboot flash boot boot.img
If you are using the correct roms for your device (should be endeavorU) than that should do it, since we are S-ON thats the only way to flash a rom.
After you flash boot.omg and Rom in cwm, wipe cache, and dalvic cache.
Sent from my HTC One X using xda premium
convict_moody said:
After you flash boot.omg and Rom in cwm, wipe cache, and dalvic cache.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks so much for your feedback. It was the wiping that was the problem.