Hi All,
I tried searching for this but couldn't find anything on it. I flashed my One V CDMA with Parnoid Android's latest rom. What I noticed is that when the phone is charging the LED flashes amber. Is there a way that I can change this in the settings so that it will stay solid instead?
Any help would be appreciated.
nope i dont think so
no way to do that from the within the rom. the source needs to be modified.
BUT
I think you have a bad flash, because the led-lights are fixed for both GSM and CDMA by simonsimons34.
1ceb0x said:
no way to do that from the within the rom. the source needs to be modified.
BUT
I think you have a bad flash, because the led-lights are fixed for both GSM and CDMA by simonsimons34.
Click to expand...
Click to collapse
Everything else is working fine, so should I just re-install everything again on top of what I have or wipe and install? In TWRP I had the Dalvik cache wipe and factory reset fail with some error about the e:\sd-ext but everything else was fine.
And just to confirm, the LED when it is fully charged stays on as a solid green. It is just when in charge state (orange) that the LED blinks.
Do you have an unanswered voicemail or message? My light is set to blink amber of I have an unanswered message/ VM .
Sent from my HTC One V+ (because the X+ isnt as awesome as my V+ )
Tehwafflez said:
Do you have an unanswered voicemail or message? My light is set to blink amber of I have an unanswered message/ VM .
Sent from my HTC One V+ (because the X+ isnt as awesome as my V+ )
Click to expand...
Click to collapse
I don't have any messages nor anything missed in the notification window. It also doesn't flash when it's unplugged so I don't think that's it.
1ceb0x said:
I think you have a bad flash, because the led-lights are fixed for both GSM and CDMA by simonsimons34.
Click to expand...
Click to collapse
By bad flash, are you referring to the kernel/bootloader or the ROM?
Thanks
by bad flash i'm reffering that in TWRP recovery you didn't wiped the system partition.
Ok so I went into TWRP and tried this again.
Wiped Cache - Ok
Dalvik Cache - Ok
Factory Reset - Failed
using rm -rf on .android_secure
E:\Unable to mount 'sd-ext'
Updating Partition details
Wipe System - Ok
Installing the rom and gapps went successfully with not errors. Everything booted ok but I still have the blinking amber light when it charges. Does anyone know if the problem is with the sd card? Is this because I was using link2sd before?
OK I think I found how to fix the issue. I haven't confirmed it for this particular rom (since I have an issue with Bluetooth and am trying different ROMs to get it working) but this is what I did to get it fixed.
1) Wiped Cache
2) Dalvik Cache
3) Factory Reset
4) Wipe System
5) Install ROM and Gapps
6) Wiped Cache
7) Dalvik Cache
8) Factory Reset
9) Apply Bootloader
10) Reboot
Related
I bought a T-Mobile Samsung Galaxy S III yesterday. It was working like a champ. I tapped the Software update button, it installed, rebooted, poof phone + contacts icons are now turned into little android icons, the apps are gone. Every app on the phone is crashing, Factory Reset doesn't remedy this.
So I decide, oh okay, I'll restore the stock rom that came with it. Did this after much trial and error but now everything on the phone is crashing constantly. The UI won't even stay running for more than 1 minute.
So far I have tried: Reinstalling the original stock rom, and the updated stock rom.
( T999UVALEM_T999TMBALEM_T999UVALEM_HOME.tar.md5 and T999UVALH2_T999TMBALH2_T999UVALH2_HOME.tar.md5 )
I was using a tool I found here called Samsung Galaxy S3 QCom ToolKit.
I have tried everything and I am at wits end.
Reflash one of them. Wipe all including /data /cache /dalvik-cache /system before you flash. As soon as its finished reboot straight to recovery and wipe data/factory reset
billard412 said:
Reflash one of them. Wipe all including /data /cache /dalvik-cache /system before you flash. As soon as its finished reboot straight to recovery and wipe data/factory reset
Click to expand...
Click to collapse
It suddenly works again after rebooting several times (Nothing has crashed at all so far)
I wish I could offer an explanation as to why it suddenly works now. I used to be really big into android but we are talking back when the HTC Hero on Sprint was new.
hiimcody1 said:
It suddenly works again after rebooting several times (Nothing has crashed at all so far)
I wish I could offer an explanation as to why it suddenly works now. I used to be really big into android but we are talking back when the HTC Hero on Sprint was new.
Click to expand...
Click to collapse
I would go into recovery and wipe system, data, cache and dalvik cache then use ODIN and flash T999UVALH2_T999TMBALH2_T999UVALH2_HOME.tar.md5 just to make sure you dont have any problems like this again in the future, especially if it crashed and after several reboots and it is finally working. Start FRESH.
Hello,
i just installed the Jedi Mind Trick 9 on 989 and going thru the configs.
The keys on the bottom of the phone are dying after some time and i can't perform any actions. I already rebooted 3 times and it's a consistent behavior.... What is a possible issue here?
IT seems that they become unresponsive after some time of inactivity - 3-5 minutes (?)
dbabo said:
Hello,
i just installed the Jedi Mind Trick 9 on 989 and going thru the configs.
The keys on the bottom of the phone are dying after some time and i can't perform any actions. I already rebooted 3 times and it's a consistent behavior.... What is a possible issue here?
IT seems that they become unresponsive after some time of inactivity - 3-5 minutes (?)
Click to expand...
Click to collapse
Could be a bad flash or download. Do the md5's match up? And did you full wipe vefore and wipe cache an dalvik afterwards?
Sezier said:
Could be a bad flash or download. Do the md5's match up? And did you full wipe vefore and wipe cache an dalvik afterwards?
Click to expand...
Click to collapse
md5 matches.
full wipe performed as :
Wipe Data/factory reset
Wipe Cache
Wipe Dalvik-Cache
Wipe Battery Stats
Format /system
still the same....
I switched to TWRP2 ( 2.3.0.0). and proceeded with the steps in the installation - the last " fix permissions" fails with message :
"Can't check permissions after factory reset.
Please boot rom and try again after reboot into recovery"
Attempts to boot give me boot loop....
after 3 reboots it somehow managed to boot... wow %) let's see what will fail this time...
Looks like life is improving rapidly - keys are staying lit, reboot is working....
I switched to TWRP and tried flashing some roms and it caused a bunch of weird issues....i would suggest you go back to CWM and use darkside scripts and reflash. I am using JMT9 and everything is working great!!!!
toreone said:
I switched to TWRP and tried flashing some roms and it caused a bunch of weird issues....i would suggest you go back to CWM and use darkside scripts and reflash. I am using JMT9 and everything is working great!!!!
Click to expand...
Click to collapse
interesting. For me it seems to be the TWRP2 that allowed me to get the phone to work. I'm not touching this phone for at least a few months Or maybe if Jediv10 will have an awesome battery life. current one (9) is seemed to be draining it on the screen... I can almost see the indicator going down if i don't use the "energy safe" option...
Greetings,
I would have liked to post this questions, where it belongs to, but I'm new to this forum, so I put it here.
Last September I've updated my DHD following the instructions given in the thread mentioned in the headline and everything was fine. Yesterday in the evening, I got the notification to restart using the recovery mode, because something in the context of the superuser should be updated or modified. Because it was not the first time, I just did it. But this time, after rebooting, the device stopped with the HTC bootscreen (green HTC on white background).
After 10 minutes I took out the battery and restarted again. Again I was able to choose recovery mode, but while starting the DHD got stuck with the bootscreen. I decided to wait and just put it aside showing the boot screen, but the result this morning was that the battery is empty and nothing changed.
Does someone know about that issue and what do I need to do to get the device to work again? Why was this update needed in the first place?
Thanks a lot in advance...
im not sure why
but have you tried re-flashing the ROM?
PHOENIX-9 said:
im not sure why
but have you tried re-flashing the ROM?
Click to expand...
Click to collapse
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.
If you don't wipe your data partition (dirty flash) and you flash the exact same ROM, you shouldn't lose data.
KKrittel said:
Not yet. I was afraid to loose all data and maybe exchaning a file would also do the job. I mean, the update of the superuser component has changed something and this could be corrected again.
Click to expand...
Click to collapse
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up
PHOENIX-9 said:
try to back up your ROM
do a clean install..then restore only the data (advanced restore)..wipe dalvik and cashe
if it didnt boot..you can restore your data using titanium backup pro from the CWM back up
Click to expand...
Click to collapse
Tried to make a backup, but it recovering did not work. Doesn't matter. I just flashed the same image again, downloaded 'my' apps and restored the status from before the crash.
Nevertheless the same notification showed up, saying that the superuser kernel needs to be updated and I should use 'recovery mode' again. With a bad feeling, I did it again, but this time it works.
So to sum it up: device was useless for some days, restored it with some effort and now it works again. But I need to get prepared for the next time and to think of an app to backup all apps including app-data.
...but as always, this is a task for laaaaater
Thx,
Karl
Hi, I'm a noob at messing with rooting or ROMs, I have a T-Mobile HTC One M8 that I rooted, it worked fine until 2 weeks later it started rebooting every few seconds, I went into TWRP Recovery and wiped the Dalvik Cache and the regular Cache, it worked fine for a few days then started rebooting every minute or so so I attempted to wipe both the Dalvick Cache and the regular Cache again thinking it would solve the problem once more. I went into Advanced Wipe and wiped Dalvik Cache, Cache, Data, Internal Storage and System...it was a noob mistake thinking that I just did a Factory Wipe. I'm not sure why I did that, but afterwards, I lost the OS to my phone because of it.
These are the Problems:
I have S-On
I didn't do a Backup of anything
I don't know how to find the CID (if needed to fix it)
I don't know how to fix the phone
I've attached a picture of what my bootloader shows for its information. Please can someone help me fix my mistake...I really want to learn how to fix this. Can someone please instruct me how to get my OS back? I want to be able to use this phone again.
mauricioreynoso123 said:
Hi, I'm a noob at messing with rooting or ROMs, I have a T-Mobile HTC One M8 that I rooted, it worked fine until 2 weeks later it started rebooting every few seconds, I went into TWRP Recovery and wiped the Dalvik Cache and the regular Cache, it worked fine for a few days then started rebooting every minute or so so I attempted to wipe both the Dalvick Cache and the regular Cache again thinking it would solve the problem once more. I went into Advanced Wipe and wiped Dalvik Cache, Cache, Data, Internal Storage and System...it was a noob mistake thinking that I just did a Factory Wipe. I'm not sure why I did that, but afterwards, I lost the OS to my phone because of it.
These are the Problems:
I have S-On
I didn't do a Backup of anything
I don't know how to find the CID (if needed to fix it)
I don't know how to fix the phone
I've attached a picture of what my bootloader shows for its information. Please can someone help me fix my mistake...I really want to learn how to fix this. Can someone please instruct me how to get my OS back? I want to be able to use this phone again.
Click to expand...
Click to collapse
Download a custom rom and adb push it to your internal storage and then flash it from recovery.
Same problem
mauricioreynoso123 said:
Hi, I'm a noob at messing with rooting or ROMs, I have a T-Mobile HTC One M8 that I rooted, it worked fine until 2 weeks later it started rebooting every few seconds, I went into TWRP Recovery and wiped the Dalvik Cache and the regular Cache, it worked fine for a few days then started rebooting every minute or so so I attempted to wipe both the Dalvick Cache and the regular Cache again thinking it would solve the problem once more. I went into Advanced Wipe and wiped Dalvik Cache, Cache, Data, Internal Storage and System...it was a noob mistake thinking that I just did a Factory Wipe. I'm not sure why I did that, but afterwards, I lost the OS to my phone because of it.
These are the Problems:
I have S-On
I didn't do a Backup of anything
I don't know how to find the CID (if needed to fix it)
I don't know how to fix the phone
I've attached a picture of what my bootloader shows for its information. Please can someone help me fix my mistake...I really want to learn how to fix this. Can someone please instruct me how to get my OS back? I want to be able to use this phone again.
Click to expand...
Click to collapse
In addition to the same problem, when I connect my phone to the PC, it does not show up.
Did you get a fix on the problem ???
ED
riversinc said:
In addition to the same problem, when I connect my phone to the PC, it does not show up.
Did you get a fix on the problem ???
ED
Click to expand...
Click to collapse
Honestly there's a lot of people with no os on bootloader screen.
My os dissapears after unlock recovery s-off and custom Rom.
If your phone is tripping I would just relock and flash ruu in bootloader mode.
First I would verify its not a driver issue and make sure usb debugging is on. If u are on a custom Rom go to there superuser settings and make sure it's set to apps and adb. Then try again.
twinnfamous said:
Honestly there's a lot of people with no os on bootloader screen.
My os dissapears after unlock recovery s-off and custom Rom.
If your phone is tripping I would just relock and flash ruu in bootloader mode.
First I would verify its not a driver issue and make sure usb debugging is on. If u are on a custom Rom go to there superuser settings and make sure it's set to apps and adb. Then try again.
Click to expand...
Click to collapse
i have the same issue on my phone my pc isnt recognizing the phone at all and when i can get into my recovery screen to try to turn phone off it says i need to flash super user and when i do it goes to a white htc android developers screen but thank god i can get back to bootloader screen any help to my problem i really would appreciate an answer
STANC1 said:
i have the same issue on my phone my pc isnt recognizing the phone at all and when i can get into my recovery screen to try to turn phone off it says i need to flash super user and when i do it goes to a white htc android developers screen but thank god i can get back to bootloader screen any help to my problem i really would appreciate an answer
Click to expand...
Click to collapse
boot to recovery, sideload a rom. if use adb is to hard for you then download the toolkit and use that to sideload a rom.
I'm no genius on this stuff, but if I were you I'd throw a ROM on the external SD and wipe everything and flash it.
I'm curious why you were having problems in the first place...your phone shouldn't have been having problems like that. It sort of sounds like a kernel problem. Regardless, I wouldn't necessarily flash whatever ROM you were having problems with. If I were you, I'd grab one that tons of other people who are on your carrier are using. Definitely don't flash one that is newer--get something from a well established dev/group.
As long as you can get to TWRP or whatever custom recovery you have, you should be able to wipe & flash without having to use ADB. Not that using ADB is bad, but if you're new, it can be confusing. Let us know how it works out.
can you help?
i dont even have recovery on mine anymore.So, how can i even flash a new rom?
zerozed99 said:
I'm no genius on this stuff, but if I were you I'd throw a ROM on the external SD and wipe everything and flash it.
I'm curious why you were having problems in the first place...your phone shouldn't have been having problems like that. It sort of sounds like a kernel problem. Regardless, I wouldn't necessarily flash whatever ROM you were having problems with. If I were you, I'd grab one that tons of other people who are on your carrier are using. Definitely don't flash one that is newer--get something from a well established dev/group.
As long as you can get to TWRP or whatever custom recovery you have, you should be able to wipe & flash without having to use ADB. Not that using ADB is bad, but if you're new, it can be confusing. Let us know how it works out.
Click to expand...
Click to collapse
stlsports said:
i dont even have recovery on mine anymore.So, how can i even flash a new rom?
Click to expand...
Click to collapse
you might be able to get the phone in the boot-loader (power and volume key down key) and then via fastboot flash the twrp recovery and then push a backup to the phone and restore.
-brad
Use the toolkit available in the general? section and flash the 4.4.4 RUU. Should return you to complete stock.
Did you get it fixed
mauricioreynoso123 said:
Hi, I'm a noob at messing with rooting or ROMs, I have a T-Mobile HTC One M8 that I rooted, it worked fine until 2 weeks later it started rebooting every few seconds, I went into TWRP Recovery and wiped the Dalvik Cache and the regular Cache, it worked fine for a few days then started rebooting every minute or so so I attempted to wipe both the Dalvick Cache and the regular Cache again thinking it would solve the problem once more. I went into Advanced Wipe and wiped Dalvik Cache, Cache, Data, Internal Storage and System...it was a noob mistake thinking that I just did a Factory Wipe. I'm not sure why I did that, but afterwards, I lost the OS to my phone because of it.
These are the Problems:
I have S-On
I didn't do a Backup of anything
I don't know how to find the CID (if needed to fix it)
I don't know how to fix the phone
I've attached a picture of what my bootloader shows for its information. Please can someone help me fix my mistake...I really want to learn how to fix this. Can someone please instruct me how to get my OS back? I want to be able to use this phone again.
Click to expand...
Click to collapse
I have the same problem no os but I have everything but no os
Well I fixed my phone
Sent from my HTC One_M8 using XDA Premium 4 mobile app
I have this problem with my Note 7, with TWRP installed and SuperSU but everything else stock. People can ring me and I can hear them but they can't hear me talking back.
Any help appreciated please.
I have tried factory resetting like mentioned below I can't Factory Reset or wipe caches or system or data, I get the Failed to mount error on everything i try
Try:
- Clearing Cache/Dalvik
- Clear data from Phone
- Factory reset
- Confirm whether pre-root calls work and then come back.
imatts said:
Try:
- Clearing Cache/Dalvik
- Clear data from Phone
- Factory reset
- Confirm whether pre-root calls work and then come back.
Click to expand...
Click to collapse
Thanks, I'll download the firmware and try again
Okay, probably nobody has done something this dumb except me, but this happened to me once, and the problem was that I had a Pressy button in the headphone jack and hadn't yet installed the Pressy app, so the phone was treating it as headphones. Good luck.
Sent from my SM-N930T using Tapatalk
Waiting for the firmware to download I remembered last night I tried to install the sound mods but they didn't work, the normal unable to mount errors
Oops I can't Factory Reset or wipe caches or system or data, I get the Failed to mount error on everything i try