Related
Hi All,
Been having issues with my HTC One X for the past week now and haven't been able to solve it via google or searching this forum, so was hoping one of you kind people can assist a bit.
I do apologise if this issue has already been posted and I missed it, if you can link me I'll be eternally grateful.
Basically, had a few issues annoying me with my HTC so wanted to stick a custom ROM on it. Did some searching about, eventually got a plan together to unlock and root it. All went fine, unlocked it (S-On still) got TWRP recovery on it (Chose this as the ROM I was looking at claimed to be not compatible with CWR) and was booted back into my stock droid.
First thing I did after a successful boot was to go back into recovery and make a full backup (I may have not ticked the Cache and _android.secure)
Played about with the phone again a bit, getting some of the apps back on as it had been wiped, then made a second backup (This one I know I ticked all the boxes for)
Next I tried putting CleanROM on, but could get past the white HTC screen boot loop, after various reflashing the Boot.IMG and clearing cache, so fired up TWRP and restored back to my second backup. All back to normal.
Used the phone as normal for a day or so then I tried flashing another ROM (ViperX) same thing as CleanROM (White HTC screen boot loop) and then went on to try Team Baked's ROM. Managed to get this working successfully, however the ROM was not to my liking and decided to go back to my stock backup. Here's where the issue started.
Now, when restoring the backup the phone boots as far as displaying my background and the status bar at the top, however I cannot pull the status bar down and the ring to unlock the phone with doesn't appear. It sits here for a few second and then reboots. Boot loop.
I've tried clearing cache, restoring various different ways and restoring the boot.img (though I'm not sure I have the right one) but nothing works.
The last variation I tried for restoring involved:
1. Clearing the phone via TWRP (System Restore/Clear Cache/Clear Davik/Clear System/Clear SD Card (heard this can cause issues)/Clearing Android.Secure in that order)
2. Reboot into recovery
3. Repeat step 1 (in case of locked files)
4. Reboot into Recovery
5. full restore (With MD5 check enable)
6. Clear Cache and Dalvik (Tried with just cache, also done Fastboot clear cache in another attempt)
7. Attempt to boot into OS.
As I mentioned earlier, I'm not sure if I have the right boot.IMG for my phone Model/kernal/other, to be honest I'm not entirely sure of the requirements. The details of my phone I've collected so far are:
Getvar version-main (Not sure if this is kernal or what) = 2.17.771.3
hBoot = 1.12.0000
radio = 2.1204.135.20H
CID = H3G_001
Basically, as far as I can tell from the masses of reading I've been doing, I won't be able to update to custom JB for a while so want to get back to my stock ICS and then OTA to JB when my carrier releases their version, then maybe sometime in the future when the ROM specific to my phone has been cracked consider switching to a custom.
on a final note, I've tried flashing both my backups, same result. I've also tried restoring the stock recovery and doing a system recovery with that. It appears to go through the motions (phone with green arrows? Also had the red exclamation mark, but only once of the 3 attempts) then reboots and it's still the same issue.
Thanks for reading through, any advice would be much appreciated. Used to love my phone but now can barely stand to look at it.
Cheers,
Sean
Ok, so I've now downloaded a different boot.img which should be for stock ics and after flashing that, then flashing stock recovery and doing a system restore via bootloader I will 50% of the time get the lock screen and when I unlock it I see the white HTC screen of the initial setup, then it sticks there a while and reboots. It also reboots after left at the lock screen.
To me this seems like it's doing a check or looking for a certain piece of software/file that's missing but is required to finish the start-up process. Anyone any ideas?
Even if someone can point me in the right direction for an RRU for my phone as football's RRU's seem to be the only one that has the one I need but as of 5 days before all this happened the site they're hosted on doesn't allow 500+MB downloads for free members
Cheers,
Sean
**EDIT** Just done a full device wipe then restored only the SYSTEM partition and manually flashed the boot, then when I restarted it sat on the white HTC on the device setup but eventually loaded up, allowed me to complete the device setup and then loaded into the OS. All seemed fine aside from the phone being stuck in turning off airplane mode. Rebooted it to see if that would clear it up and now I'm back to bootloops before the lock screen appears (I just get my background and status bar)
So you have a nandroid backup ! Then do this
Wipe all in recovery and i mean ALL except the sdcard obvious ! system,data,caches,dalvik cache...
Then boot back into fastboot usb mode and flash the boot.img from the nandroid. Taken with TWRP the boot.img is called something like
Emmc.boot.win (or at least similar to this)
You can flash this file with fastboot command
Fastboot flash boot name of the boot.img (.win in this case)
Then enter the recovery and full wipe if you didn't o that already !
Restore the nandroid and boot it up :thumbup:
Should work
Perfect! Thanks so much man, I never even thought to flash the .wim, thought it had to be .img. Just successfully booted fully back into my old system. Hopefully will stay stable the next hour or so but looking good!
Thanks again,
Sean
Need help!!!
I'm facing the same problem with my device, i have ulocked bootloader from HTCdev and flash TWRP recovery, was trying to flash Maximus but unfortunately after flashing Maximus in TWRP my device stuck on boot logo.
Hboot: 1.12.0000
CID: HTC__J15
version-main: 2.17.415.2
Please help.
Did you flash boot.img through fastboot?
Sent from my HTC One X
TToivanen said:
Did you flash boot.img through fastboot?
Sent from my HTC One X
Click to expand...
Click to collapse
Yes, the one came with Android_Fastboot_KIT_V12.x
And make sure you flash a 2.17 based ICS rom. You can not run the maximus JB rom on that 1.12 hboot !
Mr Hofs said:
And make sure you flash a 2.17 based ICS rom. You can not run the maximus JB rom on that 1.12 hboot !
Click to expand...
Click to collapse
Then, i have done the mistake there. Now, please guide me what i need to do to get out of this problem.
I have forget to mention my device still S-ON
Please guide, sorry for troubling.
Download a 2.17 ics Rom and copy it to the phone (mount the sdcard within the recovery as a usb disk)
Take the boot.img file from that rom and copy it to the tool you used to flash it
Then enter the recovery and wipe EVERYTHING except sdcard ofcourse !!! (Cache,dalvik cache, system and data)
Then install the Rom.zip
Mr Hofs said:
Download a 2.17 ics Rom and copy it to the phone (mount the sdcard within the recovery as a usb disk)
Take the boot.img file from that rom and copy it to the tool you used to flash it
Then enter the recovery and wipe EVERYTHING except sdcard ofcourse !!! (Cache,dalvik cache, system and data)
Then install the Rom.zip
Click to expand...
Click to collapse
Thank you so much.
No problem mate ! :thumbup:
If you're looking for a Rom, I've got hboot 1.12 as well and tried a few ROMs and only ones I got working were:
Team Baked, based on jellybean though still works with 1.12. No Sense though, and a few things weren't to my liking (to name a couple,backlights on buttons didn't work and multitask button was switched back to menu button like in older devices)
SkyDragon, ics ROM with sense. Only had this a short while but appeared to be an exact stock ROM, everything working the way it should, and with a few added extra improvements.
Good luck
Slaverty said:
If you're looking for a Rom, I've got hboot 1.12 as well and tried a few ROMs and only ones I got working were:
Team Baked, based on jellybean though still works with 1.12. No Sense though, and a few things weren't to my liking (to name a couple,backlights on buttons didn't work and multitask button was switched back to menu button like in older devices)
SkyDragon, ics ROM with sense. Only had this a short while but appeared to be an exact stock ROM, everything working the way it should, and with a few added extra improvements.
Good luck
Click to expand...
Click to collapse
Is there anyway to restore it to the backup i have made with TWRP which is still in the sdcard???
sfawad81 said:
Is there anyway to restore it to the backup i have made with TWRP which is still in the sdcard???
Click to expand...
Click to collapse
Yes.
Copy the boot.img from the backup to your PC (you can mount SD card as USB from TWRP), flash it:
fastboot flash boot boot.img
And restore backup from TWRP.
Yeah, if you follow Mr hofs 1st post on the 1st page he describes all the steps required to restore. Worked perfectly for me
Slaverty said:
Yeah, if you follow Mr hofs 1st post on the 1st page he describes all the steps required to restore. Worked perfectly for me
Click to expand...
Click to collapse
Thanks alot, got it back as it was before.
Need to clear a doubt; will I be able to update my device with the OTA, as my device is unlocked, S-ON & TWRP installed?
I hope so, I'm in the same boat as you. From what I've been reading, it should still be possible as long as you put back the stock recovery and relock the bootloader.
This website offers links to download the stock recovery
http://www.androidauthority.com/one-x-revert-stock-recovery-76854/
As for relocking the bootloader, I think the process is to run this command whilst in Fast Boot USB mode
fastboot oem lock
After it's run there should be a purple "RELOCKED" at the top of your bootloader menu.
Remember to flash the recovery BEFORE you relock the bootloader
You do not have to lock the bootloader, just the stock recovery is needed ....
Stock rom (out of the box stock)
Stock boot.img
Stock recovery
Here is the 2.17 based stock recovery for those who needs it
http://db.tt/U5CK4noo
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
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:
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.
*FIXED*
The problem turned out to be the wrong TWRP version for verizon phones, the correct version is here http://crackflasher.com/openrecovery-twrp-2-7-0-1-m7wlv-img-htc-one-verizon-openrecovery/
Hello, I will not pretend to be an expert in this area but I feel I have most of my bases covered in this case and would appreciate some help.
First, the phone,
Unlocked
M7_WLV PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OS-3.11.605.1
The Problem:
Whenever I flash the rom via TWRP everything seems to work fine and the install claims it is successful however this is clearly not the case as when i try to boot the phone it bootloops getting only as far as the HTC screen (with the red development only text underneath)
Next, Pre-reqs:
Phone obviously is unlocked S-off and supercid
TWRP 2.7.0.0 is flashed to the phone (when i try 2.6.3.3 the phone only boot loops even recovery loops)
SuperSU installed
Weaksauce installed
Usb-debugging enabled
all htc drivers installed on Pc
adb installed on pc + working
fastboot installed on pc +working
Steps Taken:
I have tried both pushing the Rom.zip and copying the rom.zip to the sdcard on the phone, this has made no difference
I do the factory reset (wipe) before installing
I do the factory reset (wipe) after installing
I have unchecked all the options and made the most basic install I can
I have tried to flash the TWRP version that came on the ROM, this also causes recovery bootloop
I have tried downloading the rom directly to the phone
I have made sure the MD5 codes match
I have tried flashing the boot.img separately via fastboot
My most recent attempts Aroma Log is attached
Any help would be greatly appreciated!!!!!
PblicEnemy said:
Hello, I will not pretend to be an expert in this area but I feel I have most of my bases covered in this case and would appreciate some help.
First, the phone,
Unlocked
M7_WLV PVT SHIP S-OFF RH
CID-11111111
HBOOT-1.56.0000
RADIO-1.13.41.0109_2
OS-3.11.605.1
The Problem:
Whenever I flash the rom via TWRP everything seems to work fine and the install claims it is successful however this is clearly not the case as when i try to boot the phone it bootloops getting only as far as the HTC screen (with the red development only text underneath)
Next, Pre-reqs:
Phone obviously is unlocked S-off and supercid
TWRP 2.7.0.0 is flashed to the phone (when i try 2.6.3.3 the phone only boot loops even recovery loops)
SuperSU installed
Weaksauce installed
Usb-debugging enabled
all htc drivers installed on Pc
adb installed on pc + working
fastboot installed on pc +working
Steps Taken:
I have tried both pushing the Rom.zip and copying the rom.zip to the sdcard on the phone, this has made no difference
I do the factory reset (wipe) before installing
I do the factory reset (wipe) after installing
I have unchecked all the options and made the most basic install I can
I have tried to flash the TWRP version that came on the ROM, this also causes recovery bootloop
I have tried downloading the rom directly to the phone
I have made sure the MD5 codes match
I have tried flashing the boot.img separately via fastboot
My most recent attempts Aroma Log is attached
Any help would be greatly appreciated!!!!!
Click to expand...
Click to collapse
I noticed you said you do the factory reset after you flash Viper? You'll only want to wipe before you flash the rom. I'm guessing that's you're issue if I understood correctly.
Sent from my HTC6500LVW using Tapatalk
brholt6 said:
I noticed you said you do the factory reset after you flash Viper? You'll only want to wipe before you flash the rom. I'm guessing that's you're issue if I understood correctly.
Sent from my HTC6500LVW using Tapatalk
Click to expand...
Click to collapse
I see now I might not have been as clear as I meant to be. When I said that i wiped before and after I meant that I performed both wipes seprately from each other and a third time together. I only tried the wipe after flash because it was a suggestion from another developer website. It would seem that this is not the solution, as the bootloop happens regardles of wipe before, wipe after, or wipe before and after or even no wipe at all. Thanks for the reply!
Try this. Download this recovery http://www.androidfilehost.com/?fid=23329332407584851.
Use fastboot to flash the recovery.
Code:
fastboot erase cache
Code:
fastboot erase recovery
Code:
fastboot flash recovery nameofrecovery.img
Code:
fastboot reboot-bootloader
Go to recovery.
In recovery go to wipe - advanced - check boot, system, data, and cache. Proceed with the wipe.
Flash your rom
Boot up.
cmlusco said:
Try this
Use fastboot to flash the recovery.
Code:
fastboot erase cache
Code:
fastboot erase recovery
Code:
fastboot flash recovery nameofrecovery.img
Code:
fastboot reboot-bootloader
Go to recovery.
In recovery go to wipe - advanced - check boot, system, data, and cache. Proceed with the wipe.
Flash your rom
Boot up.
Click to expand...
Click to collapse
Everything went very well except 2 things. 1: when issuing the "fastboot erase recovery" command in fastboot it failed and came back as "not allowed". 2: the rom installation failed and came back as , error: 7. I tried to boot to system regardless of the error message but the boot loop continues
The new error log is attached again. Thanks for the reply! (and the TWRP update!)
Seems to be an issue with the rom. The log shows everything going fine until the very last step where it tries to change the permissions of an apk and fails, therfore aborting the whole install.
Code:
Setting permissions
ApplyParsedPerms: removexattr of /system/app/BasicDreams.apk to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
I would post that in the roms thread.
cmlusco said:
Seems to be an issue with the rom. The log shows everything going fine until the very last step where it tries to change the permissions of an apk and fails, therfore aborting the whole install.
Code:
Setting permissions
ApplyParsedPerms: removexattr of /system/app/BasicDreams.apk to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
I would post that in the roms thread.
Click to expand...
Click to collapse
I would love to but unfortunately I am not allowed to post there until I have 10 posts and have been cleared by a mod. Do you think it could have anything to do with the temproot i installed (weaksauce) because it works by installing a root every time the phone boots up, or would that be deleted when the wipe is performed?
When you wiped before the rom install it should wipe out everything including weaksauce. The reason it wont boot is because you have no or an incomplete rom. I would just flash another rom in the mean time till you can figure out whats up with viper. Or you could do an ruu if you wanted to be stock.
cmlusco said:
When you wiped before the rom install it should wipe out everything including weaksauce. The reason it wont boot is because you have no or an incomplete rom. I would just flash another rom in the mean time till you can figure out whats up with viper. Or you could do an ruu if you wanted to be stock.
Click to expand...
Click to collapse
I really want viper because of the customization, do you know of any other sources that I could acquire viper from? or would it be possible to install an older version and update it?
*UPDATE* I tried to install Android Revolution HD just now to see if it would work and I end up with the exact same error, seems like a phone problem to me. is there anyway to put my phone completely back to the way i got it out of the box and start over?
Yes you can do an ruu to get back to stock. But you need fastboot to do it. You probably dont have the correct drivers installed on your pc. What version of windows you runing?
cmlusco said:
Yes you can do an ruu to get back to stock. But you need fastboot to do it. You probably dont have the correct drivers installed on your pc. What version of windows you runing?
Click to expand...
Click to collapse
Windows 7 64bit. I use fastboot all the time with this phone so I should be able to use it.
Nevermind, i was thinking this was a different thread. Anyways you will need to change your cid back to vzw__001. Then download the ruu from the second post of santods stock rom thread in development section.
fastboot oem rebootRUU
fastboot flash zip ruufilename.zip
(may fail with flush error, do command again)
fastboot reboot
PblicEnemy said:
I really want viper because of the customization, do you know of any other sources that I could acquire viper from? or would it be possible to install an older version and update it?
*UPDATE* I tried to install Android Revolution HD just now to see if it would work and I end up with the exact same error, seems like a phone problem to me. is there anyway to put my phone completely back to the way i got it out of the box and start over?
Click to expand...
Click to collapse
The big problem with Android Revolution is that it isn't made for the Verizon HTC One. Make sure you you're only flashing roms from the Verizon HTC One thread or you've talked to the Dev. Flashing roms meant for other carriers can really screw you up.
Sent from my HTC6500LVW using Tapatalk
Thanks to both of you, good information and helpful, I'm still hoping I can figure out the set_metadata_recursive error, I have another thread going specifically for it!