Related
My ChaCha is stuck at HTC boot screen. i have done factory reset, battery pulls and installing ROMS to no avail. I keep getting errors while trying to install the stock ROMS. Am I going about it the right way, trying to find ROMs or Is there something else I can do to solve this problem.
dagbula said:
My ChaCha is stuck at HTC boot screen. i have done factory reset, battery pulls and installing ROMS to no avail. I keep getting errors while trying to install the stock ROMS. Am I going about it the right way, trying to find ROMs or Is there something else I can do to solve this problem.
Click to expand...
Click to collapse
do you have root? and have recovery? if yes then go there and delete dalvik, delete cache and try factory reset
petulikt said:
do you have root? and have recovery? if yes then go there and delete dalvik, delete cache and try factory reset
Click to expand...
Click to collapse
Yes, I have root and can boot to recovery. I already tried clearing the dalvik cache and factory reset. i also restored from a Nandroid backup, all this to no avail. The boot loop problem still persist.
i also tried flashing ROM but all the ROMs i got gives one error or the other. I really need help.
dagbula said:
i also tried flashing ROM but all the ROMs i got gives one error or the other. I really need help.
Click to expand...
Click to collapse
Have you tried flashing an official RUU 1.33 with a goldcard?
Did you find a solution ?
i am having the same problem
ZaSa 4 chacha ROM saved me from the trouble check here http://forum.xda-developers.com/showthread.php?t=1343636
Please help. When i first received my HTC One X, i had it rooted and the boot loader unlocked. TWRP recovery is also installed. The first thing i did was flash Clean Rom 3 LE and it booted up and was working perfectly. A few days later, i attempted to flash Cm9 alpha4 and after telling TWRP to reboot, it would just sit at the HTC screen for over twenty minutes. I tried restoring my backup and re downloading the file but it still failed. At this point i had just thought that it must be an issue with the rom on my phone, so i downloaded aokp rom from rootzwiki. I did a factory reset and cleared my caches, but it would then get stuck at the HTC screen, and then proceed to the recovery as if i had never flashed the rom. Any help is really appreciated. Thank you
If nothing else work, you can run one of the RUUs. But it will wipe data, and you will need to root, unlock bootloader (?) and install recovery again.
Thanks, but I am able to plug my phone into my mac and get to the recovery via terminal. I can then flash Clean rom and it will boot up and work fine. I'm wondering if this is an issue flashing any non-Sense based roms.
I've Flashed miui and cm9 and aokp with no problems. Did you flash the ones found in our development section? The ones in the International section won't work.
Try redownloading the zips. Make sure you wipe everything a couple times.
In the TWRP recovery wipe menu select cache, factory reset, and system then install CM9. This should fix your problem.
I flashed the ones found in our development section. Is there any extra step that I have to take. I did a factory reset, cleared my cache and dalvik cache, and then flashed the rom. I then cleared my cache and dalvik cache and then rebooted.
AMDERS17 said:
I flashed the ones found in our development section. Is there any extra step that I have to take. I did a factory reset, cleared my cache and dalvik cache, and then flashed the rom. I then cleared my cache and dalvik cache and then rebooted.
Click to expand...
Click to collapse
I don't think it's casuing the problem but the 2nd cache and dalvik clearning aren't necessary.
P_Dub_S said:
In the TWRP recovery wipe menu select cache, factory reset, and system then install CM9. This should fix your problem.
Click to expand...
Click to collapse
Still not working, but thank you for the advice. If it helps any, its stuck at the first HTC screen where it tells you in red that the software is for development purposes only.
AMDERS17 said:
Still not working, but thank you for the advice. If it helps any, its stuck at the first HTC screen where it tells you in red that the software is for development purposes only.
Click to expand...
Click to collapse
it just sits there?
that's odd.
if you connect it to your computer can you get a logcat?
type adb logcat from command prompt.
gunnyman said:
it just sits there?
that's odd.
if you connect it to your computer can you get a logcat?
type adb logcat from command prompt.
Click to expand...
Click to collapse
When i enter the command, this is what i get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
Ive never taken a logcat before, so Im sure i must have done something wrong
AMDERS17 said:
When i enter the command, this is what i get:
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
is adb in your path?
gunnyman said:
is adb in your path?
Click to expand...
Click to collapse
It is, but does my phone need to be on, because it is stuck at the HTC screen
Ok. Flash a rom you know works. Get the phone running then do a fresh download of cm9 alpha 4. Before you install it do a backup in recovery in case it's borked again.
gunnyman said:
Ok. Flash a rom you know works. Get the phone running then do a fresh download of cm9 alpha 4. Before you install it do a backup in recovery in case it's borked again.
Click to expand...
Click to collapse
Doing that now
Re downloaded the file and flashed it but it is still stuck at the HTC booting screen
AMDERS17 said:
Re downloaded the file and flashed it but it is still stuck at the HTC booting screen
Click to expand...
Click to collapse
stupid question is your bootloader locked?
gunnyman said:
stupid question is your bootloader locked?
Click to expand...
Click to collapse
It is. I was a able to flash Clean Rom. Im pretty stumped as to what the problem is.
AMDERS17 said:
It is. I was a able to flash Clean Rom. Im pretty stumped as to what the problem is.
Click to expand...
Click to collapse
if it's LOCKED that's probably your problem. Unlock it. There's no reason to re-lock it anyway.
gunnyman said:
if it's LOCKED that's probably your problem. Unlock it. There's no reason to re-lock it anyway.
Click to expand...
Click to collapse
Sorry. I read your other post wrong. It is unlocked. lol
I was running the ruu 1.7x with PA because I had a soft brick a few weeks ago, just last night I tried flashing King Cobra in TWRP. Upon rebooting it gave me trouble but I eventually got the phone to boot up all the way. Everything worked except and I couldn't call or text but I can receive them. I thought maybe installing the latest update would solve the problem but I'm still having the same issue. EVERYTHING got wiped no backs up no nothing, am I screwed?
Sent from my HTC One X using xda app-developers app
Check your apn settings and make sure your using the correct settings for your carrier.
Grnfinger said:
Check your apn settings and make sure your using the correct settings for your carrier.
Click to expand...
Click to collapse
I did that when I was running KC and now on the stock software, I thought it was because I was on 1.7x and flashed KC cause I didn't have this problem with PA, so I did the update ruu tool to 2.20 and the problem still persist :/
WOOOWWW.
I am the biggest herp that ever derped. I did not flash the FC.zip fix provided in the King Cobra thread instead I updated with the RUU tool and the problem still persists. So I suppose I have to wait for the amazing minds of XDA to figure out a way to root the HOX on 2.20 before I can root/unlock to flash this silly zip. Ohhhh woe is me.
droidnamedjakke said:
I am the biggest herp that ever derped. I did not flash the FC.zip fix provided in the King Cobra thread instead I updated with the RUU tool and the problem still persists. So I suppose I have to wait for the amazing minds of XDA to figure out a way to root the HOX on 2.20 before I can root/unlock to flash this silly zip. Ohhhh woe is me.
Click to expand...
Click to collapse
Since you already unlocked the phone with HTC dev unless you changed your cid before the ruu you can unlock again with the same token and install twrp and flash a rooted rom.
You will just need to flash the boot.img from fastboot before the rom
Sent from my HTC One XL using Forum Runner
droidnamedjakke said:
I am the biggest herp that ever derped. I did not flash the FC.zip fix provided in the King Cobra thread instead I updated with the RUU tool and the problem still persists. So I suppose I have to wait for the amazing minds of XDA to figure out a way to root the HOX on 2.20 before I can root/unlock to flash this silly zip. Ohhhh woe is me.
Click to expand...
Click to collapse
As long as you left your phone SuperCID, then you can reunlock and re-root.
I unlocked it once again and flashed KC back, but the .zip fix he provided isn't working. Any ideas fellas?
droidnamedjakke said:
I unlocked it once again and flashed KC back, but the .zip fix he provided isn't working. Any ideas fellas?
Click to expand...
Click to collapse
Try going in to recovery and clearing everything (cache, dalvik, factory reset, system) and reflash. Keep in mind if you are on 2.20, you have to flash the boot.img manually.
Butters619 said:
Try going in to recovery and clearing everything (cache, dalvik, factory reset, system) and reflash. Keep in mind if you are on 2.20, you have to flash the boot.img manually.
Click to expand...
Click to collapse
It didn't solve the problem I still can't flash the .zip fix nor is the issue gone. Should I try flashing a different Rom and see if that takes care of it?
flash newest twrp 2.2.2.0 in fastboot. also do a "fastboot erase cache" then "fastboot flash boot boot.img" using the boot.img from CleanROM 4.5. then wipe cache,dalvik,data,system,etc. even flash external after backing up everything. then mount usb copy CleanROM 4.5 to storage. then install selecting full wipe in aroma. then install cleanmods in the created storage folder. that will be the safest method to make sure your starting clean.
DvineLord said:
flash newest twrp 2.2.2.0 in fastboot. also do a "fastboot erase cache" then "fastboot flash boot boot.img" using the boot.img from CleanROM 4.5. then wipe cache,dalvik,data,system,etc. even flash external after backing up everything. then mount usb copy CleanROM 4.5 to storage. then install selecting full wipe in aroma. then install cleanmods in the created storage folder. that will be the safest method to make sure your starting clean.
Click to expand...
Click to collapse
I'll try this when I get home from work at 2:30, thanks for giving the advice. But what do you mean "even flash external"?
DvineLord said:
flash newest twrp 2.2.2.0 in fastboot. also do a "fastboot erase cache" then "fastboot flash boot boot.img" using the boot.img from CleanROM 4.5. then wipe cache,dalvik,data,system,etc. even flash external after backing up everything. then mount usb copy CleanROM 4.5 to storage. then install selecting full wipe in aroma. then install cleanmods in the created storage folder. that will be the safest method to make sure your starting clean.
Click to expand...
Click to collapse
I did a full wipe of everything and installed CleanROM but to no avail I'm still getting the error as listed before. I don't understand everything was wiped for my HOX why is it still doing this?
I've been having a problem with phone calls putting them on speaker. The volume of the external speaker is comparable to the volume of the ear piece. This is only in calls, music and notifications seem to be fine. It was fine before I rooted, but seems to be goofed up on JB roms. I rooted with the brand new 2.20 root method. I tried things like Volume+ and nothing seems to make a difference. I've tried all the basic things like wiping cache/dalvick. What are the chances it's a bad device?
you already posted this in the roms thread. someone probably saw it so why make a thread? wipe and reflash. you also can't blame root because you flashed another rom. on first root, unlock, recovery flashing i always "fastboot erase cache", then wipe literally everything in twrp, then flash my rom. you could first try "fastboot erase cache" in bootloader then wipe cache/dalvik then fix permissions before doing the above and see if that fixes it.
DvineLord said:
you already posted this in the roms thread. someone probably saw it so why make a thread? wipe and reflash. you also can't blame root because you flashed another rom. on first root, unlock, recovery flashing i always "fastboot erase cache", then wipe literally everything in twrp, then flash my rom. you could first try "fastboot erase cache" in bootloader then wipe cache/dalvik then fix permissions before doing the above and see if that fixes it.
Click to expand...
Click to collapse
yes, i posted it there because at the time i thought the problem was specific to that rom (i think it started with the codename rom). but after being on more than one rom (i'm now on the jb build 4) i don't think it is. or it may be specific to jb roms. i'm not sure. i thought i would ask before i just go flashing away... i'm also wondering if anybody else is having this problem.
i followed you all the way till "fix permissions", is this another tab in twrp?
with all the changes right now with CM10 which is base for alot of jb roms its hard to determine the cause. unless you are using a jb aosp build before the kernel changes which is basically anything after 10/01 then you might have some unique issues.
fix permissions is under advanced
Speaking of kernels, I haven't gotten any kernels to successfully flash with either ROM. For instance rohans kernel to oc. Flashed it with his ROM. Won't take.
So basically what you're saying is wipe caches with fastboot, go into twrp, erase everything, reflash, then fix permissions?
Sent from my One X using xda app-developers app
ck4794 said:
Speaking of kernels, I haven't gotten any kernels to successfully flash with either ROM. For instance rohans kernel to oc. Flashed it with his ROM. Won't take.
So basically what you're saying is wipe caches with fastboot, go into twrp, erase everything, reflash, then fix permissions?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
use the stock kernel that comes with your rom for now. reboot in to bootloader and "fastboot flash boot boot.img" the kernel(ie boot.img) from ur current rom. then run "fastboot erase cache" then boot into recovery. wipe cache/dalvik then go into advanced and fix permissions.
if that doesnt work then wipe everything and reflash your rom and gapps if its aosp rom, then rewipe cache/dalvik and reboot.
Didn't work, but sandy just knocked out the power so I think this can wait a while haha
Sent from my One X using xda app-developers app
ck4794 said:
Speaking of kernels, I haven't gotten any kernels to successfully flash with either ROM. For instance rohans kernel to oc. Flashed it with his ROM. Won't take.
So basically what you're saying is wipe caches with fastboot, go into twrp, erase everything, reflash, then fix permissions?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I respectfully suggest you stay away from custom kernel for now until you are a little more familiar with your device, especially if you're playing with jb/cm10 based roms stay with the kernel that came with. The devs will not support any issues that arise from flashing a custom kernel on top of a their roms.
Crappyvate said:
I respectfully suggest you stay away from custom kernel for now until you are a little more familiar with your device, especially if you're playing with jb/cm10 based roms stay with the kernel that came with. The devs will not support any issues that arise from flashing a custom kernel on top of a their roms.
Click to expand...
Click to collapse
i will definitely take this under consideration
DvineLord said:
use the stock kernel that comes with your rom for now. reboot in to bootloader and "fastboot flash boot boot.img" the kernel(ie boot.img) from ur current rom. then run "fastboot erase cache" then boot into recovery. wipe cache/dalvik then go into advanced and fix permissions.
if that doesnt work then wipe everything and reflash your rom and gapps if its aosp rom, then rewipe cache/dalvik and reboot.
Click to expand...
Click to collapse
did this and still a no go... no volume on speaker phone during a call. wiped everything and reflashed rom with stock kernel, wiped again, fixed permissions. all other volumes seem to be appropriate.
ck4794 said:
did this and still a no go... no volume on speaker phone during a call. wiped everything and reflashed rom with stock kernel, wiped again, fixed permissions. all other volumes seem to be appropriate.
Click to expand...
Click to collapse
relock bootloader and ruu...if that does not do it you have a hardware issue.
i'm not questioning your logic, but for my own knowledge can you explain this a little better for me? not the process but the reasoning? to my understanding an ruu basically strips the phone back to some previous state, depending on the ruu you chose, and reverts it back to stock. what purpose does re locking the bootloader serve here? would i need a new unlock code or would the unlock code i got from the first time i unlocked it still work?
also let me make sure i have this process down, relock, ruu, unlock, flash? am i missing any steps in there? like will i need to reflash my recovery?
ck4794 said:
i'm not questioning your logic, but for my own knowledge can you explain this a little better for me? not the process but the reasoning? to my understanding an ruu basically strips the phone back to some previous state, depending on the ruu you chose, and reverts it back to stock. what purpose does re locking the bootloader serve here? would i need a new unlock code or would the unlock code i got from the first time i unlocked it still work?
also let me make sure i have this process down, relock, ruu, unlock, flash? am i missing any steps in there? like will i need to reflash my recovery?
Click to expand...
Click to collapse
here is the logic.
1. you need to relock bootloader to run ruu
2. ruu bring you back to vanilla stock everything, allowing you to evaluate your hardware/software issue. If your speaker works it was some kind of corruption if doesn't it you know you have a hardware problem.
Unlock code stays the same.
That's also why you should always do a clean install/full wipe/factory reset when you experiment with different roms (aosp/sense)
Crappyvate said:
here is the logic.
1. you need to relock bootloader to run ruu
2. ruu bring you back to vanilla stock everything, allowing you to evaluate your hardware/software issue. If your speaker works it was some kind of corruption if doesn't it you know you have a hardware problem.
Unlock code stays the same.
Click to expand...
Click to collapse
thanks for being patient with me man, i appreciate it. i'll give this a go a little later this evening and post back results.
ck4794 said:
thanks for being patient with me man, i appreciate it. i'll give this a go a little later this evening and post back results.
Click to expand...
Click to collapse
good luck. :highfive:
[STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502
am i ok to run this ruu even though i came from 2.20 when i rooted?
ck4794 said:
[STOCK] AT&T RUU_Evita_UL_Cingular_US-1.85.502
am i ok to run this ruu even though i came from 2.20 when i rooted?
Click to expand...
Click to collapse
http://dl3.htc.com/application/htc_o...s_08022012.exe
Crappyvate said:
http://dl3.htc.com/application/htc_o...s_08022012.exe
Click to expand...
Click to collapse
bad link
ck4794 said:
bad link
Click to expand...
Click to collapse
what...i just tested it ?? hold on
http://forum.xda-developers.com/showpost.php?p=29766409&postcount=3
Crappyvate said:
what...i just tested it ?? hold on
http://forum.xda-developers.com/showpost.php?p=29766409&postcount=3
Click to expand...
Click to collapse
i saw some where i think that this ruu would get me back to square one, unrooted. is there anything like that i should know about before i run this ruu? also i've never run an ruu, is it one of those i put it on my c: drive run it and it will do the work?
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
xfranchize said:
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
Click to expand...
Click to collapse
Try re-flashing another rom, as PA is a beta ROM, and thats where you may be having your crashed apps
xfranchize said:
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
Click to expand...
Click to collapse
You can always flash the factory images here: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
You can flash any ROM and that should fix your issue
You will not lose your unlocked bootloader unless you flash the stock one which is in the factory images
Your bootloader will not relock unless you lock it yourself using fastboot. Flashing roms or factory images won't lock it by themselves.
And even if it somehow did, one fastboot command and you're unlocked again.
And as far as root goes....it takes 5 minutes to reroot.
So just flash whatever factory image you need and then custom recovery, and you're done. Maybe need to download superSU from play store after.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
justinisloco said:
Try re-flashing another rom, as PA is a beta ROM, and thats where you may be having your crashed apps
Click to expand...
Click to collapse
So i just flashed purity rom, and im still having the same issues, but the crashes and reboots are less yet their still there. Maybe reverting back to stock rom will do the trick?
xfranchize said:
So i just flashed purity rom, and im still having the same issues, but the crashes and reboots are less yet their still there. Maybe reverting back to stock rom will do the trick?
Click to expand...
Click to collapse
The crashes and reboots are because you didn't wipe data/factory reset and also didn't wipe dalvic/cache...
If you're keen on using a custom rom follow these steps:
1. Head over to recovery and wipe data/factory reset and wipe dalvic/cache
2. Flash rom.zip and gapps.zip
3. Reboot!
Initial boot can take upto 10 minutes sometimes so be patient...
If you want to go fully stock then follow this thread:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
vin4yak said:
The crashes and reboots are because you didn't wipe data/factory reset and also didn't wipe dalvic/cache...
If you're keen on using a custom rom follow these steps:
1. Head over to recovery and wipe data/factory reset and wipe dalvic/cache
2. Flash rom.zip and gapps.zip
3. Reboot!
Initial boot can take upto 10 minutes sometimes so be patient...
If you want to go fully stock then follow this thread:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
Sorry if i did not include this on the op, but everytime i were to flash a rom or gapps i would wipe data/factory and dalvic/cache, since i had those issues i even wipe internal memory just to see if the problems were there.
xfranchize said:
Sorry if i did not include this on the op, but everytime i were to flash a rom or gapps i would wipe data/factory and dalvic/cache, since i had those issues i even wipe internal memory just to see if the problems were there.
Click to expand...
Click to collapse
Maybe your flashing a bad version of GApps since the force closes are on google Calander?
Are you using a 4.4.2 GApps?
Im on cataclysm now, and i believe no gapps needed since their included in the zip. Have had about 3 reboots, i believe their because of playstore downloading an update or something, and one caused by either bluetooth or hello messaging app. But who knows. Just one more thing, by me accidentally wiping the system shouldnt be the cause of my random crashes and reboots?
Sent from my Nexus 5 using Tapatalk
xfranchize said:
Im on cataclysm now, and i believe no gapps needed since their included in the zip. Have had about 3 reboots, i believe their because of playstore downloading an update or something, and one caused by either bluetooth or hello messaging app. But who knows. Just one more thing, by me accidentally wiping the system shouldnt be the cause of my random crashes and reboots?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Why don`t you backup your user apps and data with TB and start fresh by flashing the stock image, reroot and reflash a custom rom in recovery. This will eliminate all errors and reboots.
gee2012 said:
Why don`t you backup your user apps and data with TB and start fresh by flashing the stock image, reroot and reflash a custom rom in recovery. This will eliminate all errors and reboots.
Click to expand...
Click to collapse
Sorry but how do i do that? Im really new to this, i had someone else root and unlock my bootloader for me. How do i flash the stock image then root?
xfranchize said:
Sorry but how do i do that? Im really new to this, i had someone else root and unlock my bootloader for me. How do i flash the stock image then root?
Click to expand...
Click to collapse
Read this thread http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905 well and all should be pretty easy.
gee2012 said:
Read this thread http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905 well and all should be pretty easy.
Click to expand...
Click to collapse
Okay cool, do i just skip the bootloader part right?
Sent from my Nexus 5 using Tapatalk
xfranchize said:
Okay cool, do i just skip the bootloader part right?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, just flash the factory image (flash-all.batt) in fastboot, reboot and setup the phone. Flash a custom recovery and flash the superSU.zip (1.94 is the latest).
gee2012 said:
Yes, just flash the factory image (flash-all.batt) in fastboot, reboot and setup the phone. Flash a custom recovery and flash the superSU.zip (1.94 is the latest).
Click to expand...
Click to collapse
Okay ill give it a shot, thanks alot. Ill update here if im successful.
Sent from my Nexus 5 using Tapatalk