Develop Bugs

Confusing problem..

Hey guys,
I've currently got a HTC One X that is stuck in the bootloader. I have got Clockworks Flash Recovery 5.8.4.0 installed but haven't got any rom working. I was using Cyanogenmod until my screen started flickering and eventually it was unbearable so I tried to upgrade it. The newer version didn't support the older hboot (1.12) and therefore the update failed. I tried installing other roms from the forum but had no luck with any of them.
The steps i've been taking are basically flash the boot.img, wipe data/factory reset, install the zip, wipe the data/factory reset and dalvik cache and then reboot the phone but after all of these steps I end up stuck with a bootscreen of the rom i'm trying to install. I have followed tutorials word by word and I am still stuck on the bootloader. I'm really in a dead end here as I'm not that knowledgeable when it comes to HTC, any help would be appreciated as all I want is my phone to be working!
Not sure if it's useful but..
S-ON
HBOOT-1.12.0000
RADIO-1.1204.90.13H
and the CID is H3G_001
Thanks,
Luke

If you make a factory reset after installing the custom rom in the recovery you actually wiped it again. Only perform a full wipe before the rom. Don't wipe anything after ......
Ow and you can't install any sense based JB roms. You need to update the hboot first

..
Thanks for the fast reply,
I've looked all over the forum and they all seem to be JB with Sense of some sort? Hate to be lazy but i've tried searching and can't find anything that would be compatible, would you be able to link me a rom that should work as i've got no clue.
Thanks,
Luke

Why don't you update the hboot and flash anything you like
This is a very useful thread for you
http://forum.xda-developers.com/showthread.php?t=1927048
It has everything you need to update the hboot :thumbup:

...
Will take a look and let you know how I get off, Thank you!

..
Problem is fixed after a whole day of trying. Got there in the end with a little assistance.
Thanks for your help
Luke195

Good !
CASE CLOSED !

Strange issues with latest TWRP for device and restoring / installing?

Hello all,
I'm running the latest TWRP for this device (that fixes most of the restore/backup issues). I had wicked v2 installed and running successfully for awhile. now I'm having a strange issue.
I made a nandroid backup of my stock as well as of my wicked install and played with some other roms. (aosp ones). Went back to wicked as they are all "not there yet" and the initial restore works.
Unfortunately if I shut down or rebootI basically find myself unable to boot. It hangs on "Samsung Galaxy S4". screen and doesn't finish.
If I reboot into recovery from here and try to say, clear the dalvik or something it asks me for a password like it's encrypted, and wiping dalvik for example fails.
My nandroid did not have an encrypted FS. On top of that, I tried reflashing wicked completely from scratch and I have the same issue.
Essentially I cannot reboot my phone now once flashed.
I can get into recovery no issue but I'm stuck in a cycle here.
Thanks for any help.

bezerker said:
Hello all,
I'm running the latest TWRP for this device (that fixes most of the restore/backup issues). I had wicked v2 installed and running successfully for awhile. now I'm having a strange issue.
I made a nandroid backup of my stock as well as of my wicked install and played with some other roms. (aosp ones). Went back to wicked as they are all "not there yet" and the initial restore works.
Unfortunately if I shut down or rebootI basically find myself unable to boot. It hangs on "Samsung Galaxy S4". screen and doesn't finish.
If I reboot into recovery from here and try to say, clear the dalvik or something it asks me for a password like it's encrypted, and wiping dalvik for example fails.
My nandroid did not have an encrypted FS. On top of that, I tried reflashing wicked completely from scratch and I have the same issue.
Essentially I cannot reboot my phone now once flashed.
I can get into recovery no issue but I'm stuck in a cycle here.
Thanks for any help.
Click to expand...
Click to collapse
it wasn't just latest update, people were taking about this issue for weeks now... not sure what the fix will be I think Odin back to stock... supposedly is a TWRP problem and it doesn't happen in CWM but I heard CWM has its own share of problems...
Sent from my SGH-M919

aLdaRiS said:
it wasn't just latest update, people were taking about this issue for weeks now... not sure what the fix will be I think Odin back to stock... supposedly is a TWRP problem and it doesn't happen in CWM but I heard CWM has its own share of problems...
Sent from my SGH-M919
Click to expand...
Click to collapse
Interesting.
I was about to try odin'ing back to stock and reflashing twrp.
The only thing I wonder if may be related is when you restore a backup with TWRP it gives options of all sorts of partitions besides system/data/cache etc... preload etc. It's possible it doesn't like mucking with those.

Interesting to note: If I install a CM nightly, it will allow me to reboot. Wickedv2 or my backup of wickedv2 no go.
Testing further.

Maybe when you flashed CM it messed with a partition or something. I would suggest to ODIN back to stock and then re-root and try again.

saldebot said:
Maybe when you flashed CM it messed with a partition or something. I would suggest to ODIN back to stock and then re-root and try again.
Click to expand...
Click to collapse
Righto. Sounds like a valid idea.
Unfortunately, the download links in konane's thread are timing out for me mid download. Tragic.

Managed to snag it from another location. Flashed back to stock firmware/recovery via odin.
Letting it boot to see what it does.
EDIT:
That did it.
Restored my backup and most everything is working correctly (restoring my titanium backup of all apps now.)
Few things were messed up (swiftkey was missing a language pack etc?)
But looks like AOSP/AOKP roms do something to the partition table as you said that requires flashing back the original.
Good to know and thanks for the help!

Don't wipe system in twrp.

makomek said:
Don't wipe system in twrp.
Click to expand...
Click to collapse
Does this cause issues? Didn't know.
I found that only CM nightlies would reboot fine. restoring via odin stock official then going back and putting on wicked again seemed to work to fix it and I can now reboot in a touchwhiz based rom.

re: stuck
bezerker said:
Hello all,
I'm running the latest TWRP for this device (that fixes most of the restore/backup issues). I had wicked v2 installed and running successfully for awhile. now I'm having a strange issue.
I made a nandroid backup of my stock as well as of my wicked install and played with some other roms. (aosp ones). Went back to wicked as they are all "not there yet" and the initial restore works.
Unfortunately if I shut down or rebootI basically find myself unable to boot. It hangs on "Samsung Galaxy S4". screen and doesn't finish.
If I reboot into recovery from here and try to say, clear the dalvik or something it asks me for a password like it's encrypted, and wiping dalvik for example fails.
My nandroid did not have an encrypted FS. On top of that, I tried reflashing wicked completely from scratch and I have the same issue.
Essentially I cannot reboot my phone now once flashed.
I can get into recovery no issue but I'm stuck in a cycle here.
Thanks for any help.
Click to expand...
Click to collapse
If you want a 95% sure way of fixing it so it boots completly,
then try this, it usually always works.
Get the phone into recovery mode twrp/cwm does not matter.
Then simply do a "factory reset" and I am fairly certain that it
will boot completly, I have seen this issue so many times
already not just here in the S4 thread but also in the S3.
The factory reset will not delete any of your music, videos and pictures.
Good luck!

[Q] GAPPS stops responding after CWM restore

O.K. People, I kinda dropped off the map for a while and hadn't kept up with all the latest info but it appears I need some help. I'll try and drop the cliff notes version with as much data as I can here and see if anyone has some input for me:
I took the 4.3. O.T.A. and knox did just that..knocked me into the dirt. I was able to root and install custom recovery using CFAuto root and afterwards, disabled knox and reconfigured the stock ROM the way I wanted to. I reinstalled CWM and proceeded to create a backup of my 4.3 stock rooted rom. After the backup completed I proceeded to restore my backed up ROM as a sanity check to make sure all was well and it certainly wasn't.
When CWM restored my backup I rebooted, got back into the ROM w/out problems but as soon as I swiped to access the home screen I get the com process GAPPS has stopped responding....I get this over and over and over....I have to wipe caches and reset to factory default from CWM in order to get into the ROM w/out this message. Does anyone have any insight into what I might be doing wrong, i've never experienced this before and have had plenty of experience doing these backups and restores. I'm at a loss and I don't want to have to factory reset every time I want to restore the rom as I like to make changes, and customize the stock rooted rom. Please help. If you want version specifics and such let me know and I'll post them as they're needed, and thanks in advance!
P.S. Sig file needs to be updated....that's the version info from which I updated to 4.3
~Fred

gapps stops after cwm restore
Phederico said:
O.K. People, I kinda dropped off the map for a while and hadn't kept up with all the latest info but it appears I need some help. I'll try and drop the cliff notes version with as much data as I can here and see if anyone has some input for me:
I took the 4.3. O.T.A. and knox did just that..knocked me into the dirt. I was able to root and install custom recovery using CFAuto root and afterwards, disabled knox and reconfigured the stock ROM the way I wanted to. I reinstalled CWM and proceeded to create a backup of my 4.3 stock rooted rom. After the backup completed I proceeded to restore my backed up ROM as a sanity check to make sure all was well and it certainly wasn't.
When CWM restored my backup I rebooted, got back into the ROM w/out problems but as soon as I swiped to access the home screen I get the com process GAPPS has stopped responding....I get this over and over and over....I have to wipe caches and reset to factory default from CWM in order to get into the ROM w/out this message. Does anyone have any insight into what I might be doing wrong, i've never experienced this before and have had plenty of experience doing these backups and restores. I'm at a loss and I don't want to have to factory reset every time I want to restore the rom as I like to make changes, and customize the stock rooted rom. Please help. If you want version specifics and such let me know and I'll post them as they're needed, and thanks in advance!
P.S. Sig file needs to be updated....that's the version info from which I updated to 4.3
~Fred
Click to expand...
Click to collapse
I have the same issue. Did you find an answer?

psawood said:
I have the same issue. Did you find an answer?
Click to expand...
Click to collapse
NOPE...no one's said a word and I've just been rolling back to my last stock rooted ROM and then taking the O.T.A. then re-rooting whenever I do something stupid. LOL If you have an answer for me..or anyone does for that matter, I'd sure like to hear it!
P.S. sorry, gave up on this thread, so hadn't kept up on it...just now saw your post.
~Fred

I ran into this issue.
What I did is :
DL Rom Manager
Open Rom Manager
Fix Permissions
Boot into Recovery
Wipe Cache
Wipe Dalvik
Reboot
Haven't had the issue since.

[Q] Will OTA return to S-ON and relock bootloader?

My M7 had quite the meltdown yesterday, highlighted by what seems to be a corruption of my cache partition. Long, long story short, I was able to use the ruu to 2.10.605, where everything seemed fine. Funny enough, I kept s-off and an unlocked bootloader through the process.
I was content to keep the phone as is, since my f'ing with it surely caused the cache issue. But, to be safe, I rerooted, installed CWM (TWRP will not install for me, despite a dozen efforts), and backed up. Then, to see if the problem had been solved, I tried to wipe cache, but no dice. I won't be installing original ROMs anymore, it seeems. Not a huge deal since I at least have a functional phone, but now it has downloaded 4.4 and wants to update. A couple of questions:
Should I assume that the update will likely run into cache-related issues?
Will the update relock the bootloader and/or return the phone to S-on?
If either of these is a yes, I'm thinking about using the 2.10 ruu again, returning everything as was, and then installing santod's OTA killer. I can live with 4.3 on this phone for another year - not ideal, but considering the alternatives...
Thanks in advance to anyone who might have an idea about all this.

dmdubois said:
My M7 had quite the meltdown yesterday, highlighted by what seems to be a corruption of my cache partition. Long, long story short, I was able to use the ruu to 2.10.605, where everything seemed fine. Funny enough, I kept s-off and an unlocked bootloader through the process.
I was content to keep the phone as is, since my f'ing with it surely caused the cache issue. But, to be safe, I rerooted, installed CWM (TWRP will not install for me, despite a dozen efforts), and backed up. Then, to see if the problem had been solved, I tried to wipe cache, but no dice. I won't be installing original ROMs anymore, it seeems. Not a huge deal since I at least have a functional phone, but now it has downloaded 4.4 and wants to update. A couple of questions:
Should I assume that the update will likely run into cache-related issues?
Will the update relock the bootloader and/or return the phone to S-on?
If either of these is a yes, I'm thinking about using the 2.10 ruu again, returning everything as was, and then installing santod's OTA killer. I can live with 4.3 on this phone for another year - not ideal, but considering the alternatives...
Thanks in advance to anyone who might have an idea about all this.
Click to expand...
Click to collapse
Question for you...
Where did you get your Recoveries from that you installed or tried to install?
Did you grab the versions for the m7vzw in our Verizon HTC One Original Development section?
Or did you install one intended for the International m7?

santod040 said:
Question for you...
Where did you get your Recoveries from that you installed or tried to install?
Did you grab the versions for the m7vzw in our Verizon HTC One Original Development section?
Or did you install one intended for the International m7?
Click to expand...
Click to collapse
Yes, I got them from this site, under that section. I just installed Phil's CWM, which booted, and allowed me to clear the cache (!), but now I can't install a rom. I tried your NuSense Max and your odexed 4.42....in both cases I got a status 7 error. (Before I tried either one, I updated the firmware, fyi.)
Fortunately Phil's CWM backup process is simpler and faster. Unless there are other suggestions, I think I'll tried flashing your OTA killer and live with 4.3
Thanks again.

dmdubois said:
Yes, I got them from this site, under that section. I just installed Phil's CWM, which booted, and allowed me to clear the cache (!), but now I can't install a rom. I tried your NuSense Max and your odexed 4.42....in both cases I got a status 7 error. (Before I tried either one, I updated the firmware, fyi.)
Fortunately Phil's CWM backup process is simpler and faster. Unless there are other suggestions, I think I'll tried flashing your OTA killer and live with 4.3
Thanks again.
Click to expand...
Click to collapse
Twrp 2.6.3.3 or 2.6.3.4 will install those Roms.
You can always do fastboot erase cache
That will clear the cache.
Until a newly installed recovery has booted into the OS once, it usually won't clear cache.
Sent from my HTC6435LVW using Tapatalk

santod040 said:
Twrp 2.6.3.3 or 2.6.3.4 will install those Roms.
You can always do fastboot erase cache
That will clear the cache.
Until a newly installed recovery has booted into the OS once, it usually won't clear cache.
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
It worked.
I don't know what in the hell I've been doing (I swear that's the same TWRP file I've been using) but, just like that, it booted, and successfully installed your NuSense Max Rom. No more 4.3, no cache issues, no more worry about OTAs. You're the man!
Thanks a million.

Custom Rom Problem

Everytime I install a 4.4.2 ROM it works fine until I power-off completely. When I turn it back on the microphone and speakers stop working.
I can restart the phone and reboot to recovery and everything is fine.
Of course my phone is a d2att. I only seem to get it working again is when I restore a Nandroid backup of the stock ROM then reinstall the custom ROM.
Can someone tell me a permanent way to solve this problem so I can power off with my custom ROM?

diando said:
Everytime I install a 4.4.2 ROM it works fine until I power-off completely. When I turn it back on the microphone and speakers stop working.
I can restart the phone and reboot to recovery and everything is fine.
Of course my phone is a d2att. I only seem to get it working again is when I restore a Nandroid backup of the stock ROM then reinstall the custom ROM.
Can someone tell me a permanent way to solve this problem so I can power off with my custom ROM?
Click to expand...
Click to collapse
You really haven't given any information that would help to diagnose your issues. Without information it's pretty much impossible to help you.
1.) What ROM?
2.) Fully wipe?
3.) Have you made any modifications that could conflict?
4.) Ect...

task650 said:
You really haven't given any information that would help to diagnose your issues. Without information it's pretty much impossible to help you.
1.) What ROM?
2.) Fully wipe?
3.) Have you made any modifications that could conflict?
4.) Ect...
Click to expand...
Click to collapse
I've installed Validus, C-ROM, CM11, AOKP.
None of them seem to have sound working on restart. I've tried re-flashing 4.1.1 stock via Odin then reinstall those ROMs but it never seem to work. Still have that problem after it is turned off.
I've fully wiped the phone clean every time.
Sound on the stock ROM works fine.

Not really sure what to tell you as you seem to be one of the only users posting this type of issue as far as I can see. Maybe someone that has the same issue will chime in here.

task650 said:
Not really sure what to tell you as you seem to be one of the only users posting this type of issue as far as I can see. Maybe someone that has the same issue will chime in here.
Click to expand...
Click to collapse
Also other notes
Using the Google Experience Launcher when I use the hotword "OK Google" the beep sound is scratchy.

Made another discovery, @task650, I flashed the stock recovery while running C-ROM and wiped the cache and it restored sound every time - though wiping the cache in CWM did nothing. I'm going to try TWRP now.
EDIT
--
TWRP wipe doesn't work but it does seems like there's a problem with how the cache works on my phone. Hopefully 4.4.3 based roms won't have the same issues but I will stick to stock recovery for now.
Is there any way to get a CWM flashable zip of the stock recovery or nandroid file?