Got in contact with HTC because of the Prox. Sensor bug they had me download this file and reflash the ROM, but it didn't fix the problem. I thought I would post this here in case anyone wanted it. I know the RUU is already on here.
https://www.dropbox.com/s/k8llst3qjb0pn73/PJ75IMG.zip
jdawg0024 said:
Got in contact with HTC because of the Prox. Sensor bug they had me download this file and reflash the ROM, but it didn't fix the problem. I thought I would post this here in case anyone wanted it. I know the RUU is already on here.
https://www.dropbox.com/s/k8llst3qjb0pn73/PJ75IMG.zip
Click to expand...
Click to collapse
this is basicly an RUU rite? i wish there was a fix for the prox sensor.. im sensor is all f ed up since jelly bean dropped
Weird, is this widespread? I didn't have any issues with stock or custom (Pacman) ROM I am using now.
Sent from my EVO using xda app-developers app
happens to me, when i call some one the screen goes black, and i can turn it on with the power button but when i put it up to my ear it goes black again and doesnt come on when i move it away as its supposed to
evo401 said:
this is basicly an RUU rite? i wish there was a fix for the prox sensor.. im sensor is all f ed up since jelly bean dropped
Click to expand...
Click to collapse
Yes this is like the RUU except you put this file on the ROOT of your SD card and boot into HBOOT and it will reflash the ROM.. This is for STOCK UNROOTED phones.
waterbound said:
Weird, is this widespread? I didn't have any issues with stock or custom (Pacman) ROM I am using now.
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
pacman rom is aosp
not sense
lol
jdawg0024 said:
Got in contact with HTC because of the Prox. Sensor bug they had me download this file and reflash the ROM, but it didn't fix the problem. I thought I would post this here in case anyone wanted it. I know the RUU is already on here.
https://www.dropbox.com/s/k8llst3qjb0pn73/PJ75IMG.zip
Click to expand...
Click to collapse
Great post man. I am not having luck with ruu. It will be great if you post MD5 to confirm the download.
djisia87 said:
Great post man. I am not having luck with ruu. It will be great if you post MD5 to confirm the download.
Click to expand...
Click to collapse
Not sure how to make one of those as I didn't get one from HTC
Sent from my EVO using xda app-developers app
I'm gonna try this. I've been having a serious bug with my phone where it essentially will stop responding to touch. If I do a simpull it starts working again but it'll stop soon after. Done factory resets, cache wipes, etc. Now I'll have to try this just in case. (I already have a new phone ordered on its way but I might as well cover all my bases)
So this is just the totally stock software from HTC and I don't need a root or an unlocked bootloader or anything? Cuz I haven't done any of that.
MrSteez said:
I'm gonna try this. I've been having a serious bug with my phone where it essentially will stop responding to touch. If I do a simpull it starts working again but it'll stop soon after. Done factory resets, cache wipes, etc. Now I'll have to try this just in case. (I already have a new phone ordered on its way but I might as well cover all my bases)
So this is just the totally stock software from HTC and I don't need a root or an unlocked bootloader or anything? Cuz I haven't done any of that.
Click to expand...
Click to collapse
This is the stock Factory image
Sent from my EVO using xda app-developers app
jdawg0024 said:
This is the stock Factory image
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Alright well I tried it and it didn't fix my problem anyways. Replacement's on its way!
MrSteez said:
Alright well I tried it and it didn't fix my problem anyways. Replacement's on its way!
Click to expand...
Click to collapse
mine said signiture failed. Can anyone advise
nextlevel_44 said:
mine said signiture failed. Can anyone advise
Click to expand...
Click to collapse
Try redownloading it..
jdawg0024 said:
Try redownloading it..
Click to expand...
Click to collapse
I did. I am on hboot 2.09.0000 radio 1.05.11.0606 stock recovery and relocked if that helps at all. I have tried running the JB ruu and it takes about 3 min but my phone is still tampered and wont reboot
nextlevel_44 said:
I did. I am on hboot 2.09.0000 radio 1.05.11.0606 stock recovery and relocked if that helps at all. I have tried running the JB ruu and it takes about 3 min but my phone is still tampered and wont reboot
Click to expand...
Click to collapse
The JB RUU is screwed up. I've downloaded it a few times and it doesn't actually make any changes
Rxpert said:
The JB RUU is screwed up. I've downloaded it a few times and it doesn't actually make any changes
Click to expand...
Click to collapse
Is There any ruu i can run other than that one seeing that i am on hboot 2.09.0000 i tried this file again and it goes through the whole process then does nothing
nextlevel_44 said:
mine said signiture failed. Can anyone advise
Click to expand...
Click to collapse
That means the file is either corrupted or has been modified. Can you check what the md5 for the copy you have is?
edit: If you have a mac it'll automatically break the signature when you download it.
xHausx said:
That means the file is either corrupted or has been modified. Can you check what the md5 for the copy you have is?
edit: If you have a mac it'll automatically break the signature when you download it.
Click to expand...
Click to collapse
Mac......yuck
Sent from my EVO using Tapatalk 2
Ok I finally got lucky. When I 1st flashed this file it had no affect on the P. Sensor. (Still didn't work). All of a sudden today its working perfectly, including VVM. (No longer getting a black screen while listening to messages). I don't know what would have caused it to start working but it is now. My phone is still 100% Stock
Edit: Upon further review the P. Sensor is still messed up. It will work flawlessly when outside during the day (bright light) but still turns the screen off under low light situations
Sent from my EVO using xda app-developers app
xHausx said:
That means the file is either corrupted or has been modified. Can you check what the md5 for the copy you have is?
edit: If you have a mac it'll automatically break the signature when you download it.
Click to expand...
Click to collapse
Thank you for your help, I redownloaded the file and it appears to load and go through the motions but in the end it ends up back at the bootloader screen still saying tampered. I am trying to get this phone back to stock and nothing I try from the ruu to this img doesnt work. Any help will be greatly appreciated.
Related
K I'm using boot manager to install a cm9 Rom and it keeps failing at creating boot.img. I don't know what I'm doing wrong since I've herd of others installing cm9 roms sucessfully using boot manager. Maybe it's something in my settings? Tried making a thread at init2winit forums but have not gotten any response over there. Anyone here willing to help me out? I would greatly appreciate it.
Sent from my ADR6425LVW using Tapatalk 2
that usually means you dont have enough space
Thanks for the advice. I did check my SD storage and it said that I only had 1.16GBs left. So I thought that this could be true I suppose. So I switched to int. Storage as the install location(which I have 9.67GBs available on) and its causing my phone to lock up and freeze. Happened right at the part "extracting Rom please wait..." Weird...
Sent from my ADR6425LVW using Tapatalk 2
boot manager doesnt surport rexound officially，maybe thats the final answer. i encounterred the same issue too，but when i reinstall the app，it works just fine.
Sent from my ADR6425LVW using xda premium
anubis2k3 said:
Thanks for the advice. I did check my SD storage and it said that I only had 1.16GBs left. So I thought that this could be true I suppose. So I switched to int. Storage as the install location(which I have 9.67GBs available on) and its causing my phone to lock up and freeze. Happened right at the part "extracting Rom please wait..." Weird...
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Remember to disable logging in Superuser. That also causes some major issues. Just open superuser hit settings icon, and where it says logging set it to off. You should have much better luck that way
Cool, I will try that. I've uninstalled and reinstalled multiple times, with no luck. I'm interested though. What do you guys have setup in settings?
Sent from my ADR6425LVW using Tapatalk 2
live2die said:
boot manager doesnt surport rexound officially，maybe thats the final answer. i encounterred the same issue too，but when i reinstall the app，it works just fine.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
The Rezound is supported by bootmanager.
I've never been able to get boot manager to work correctly since I've started using it back on my dinc2. Had issues installing some roms on that phone too. Which is why I think my problem may be the settings I am using. Is there specific settings I need to use for the rezound?
EDIT: After I changed the settings SU I tried again at work and it froze still and even rebooted during the install.
Sent from my ADR6425LVW using Tapatalk 2
Ok, so I finally got cm9 roms to install correctly and now when I try to boot to them it just shows the splash screen for a couple seconds and my display turns off and it never boots. I've tried with kang and paranoid with the same results. I've tried going into recovery and manually flashing the update zip for rom 1, didnt work. Can't think of what could be the problem....
Sent from a galaxy far..far..away....
anubis2k3 said:
Ok, so I finally got cm9 roms to install correctly and now when I try to boot to them it just shows the splash screen for a couple seconds and my display turns off and it never boots. I've tried with kang and paranoid with the same results. I've tried going into recovery and manually flashing the update zip for rom 1, didnt work. Can't think of what could be the problem....
Sent from a galaxy far..far..away....
Click to expand...
Click to collapse
Doesnt look like anyone has asked you this, but are you S-Off?? You need to be S-off for this to work. Also make sure when installing you wipe system/data/cache. You should be able to use the ext.4/2 either one will work. I use the ext.4 since it installs faster....alot faster.
dalvear88 said:
Doesnt look like anyone has asked you this, but are you S-Off?? You need to be S-off for this to work. Also make sure when installing you wipe system/data/cache. You should be able to use the ext.4/2 either one will work. I use the ext.4 since it installs faster....alot faster.
Click to expand...
Click to collapse
He can be HTC unlocked and s-on it will still work bootmanager still hasn't updated since the rezound got s-off... His problem sound like the boot.img does not have the right kernel installed or something
Sent from my Dinc... I mean Rezound
yojoe600 said:
He can be HTC unlocked and s-on it will still work bootmanager still hasn't updated since the rezound got s-off... His problem sound like the boot.img does not have the right kernel installed or something
Sent from my Dinc... I mean Rezound
Click to expand...
Click to collapse
only mentioning that because in the instructions for the app. If he doesnt have to be S-Off then thats strange. Only thing i could suggest after that would be redownload ROM and check MD5
dalvear88 said:
only mentioning that because in the instructions for the app. If he doesnt have to be S-Off then thats strange. Only thing i could suggest after that would be redownload ROM and check MD5
Click to expand...
Click to collapse
i understand... he could probably do a dirty install of the same rom over top and make sure it has a boot.img in the zip that is not in any of the folders
ok,
So like an idiot, i began the S-OFF process without reverting my SuperCID. I cannot get past step 8, and i am having errors flashing my RUU.
Right now i cannot get past the bootloader. If i try to fastboot reboot, it takes me back to the bootloader. If i try a reboot, it takes me back to the bootloader.
Is there something that i can flash to get me back and running? I have tried numerous things, and i really need my phone back tonight. Grandfather is in the hospital, and i have no way to contact anyone except through facebook / email.
does anyone have some ideas, or know what i need to do? I honestly dont care about root or s-off, i can do that later. Right now i just need a bootable phone.
help!
squeezyb said:
ok,
So like an idiot, i began the S-OFF process without reverting my SuperCID. I cannot get past step 8, and i am having errors flashing my RUU.
Right now i cannot get past the bootloader. If i try to fastboot reboot, it takes me back to the bootloader. If i try a reboot, it takes me back to the bootloader.
Is there something that i can flash to get me back and running? I have tried numerous things, and i really need my phone back tonight. Grandfather is in the hospital, and i have no way to contact anyone except through facebook / email.
does anyone have some ideas, or know what i need to do? I honestly dont care about root or s-off, i can do that later. Right now i just need a bootable phone.
help!
Click to expand...
Click to collapse
Did you relock the boot loader?
Sent from my DROID RAZR using Tapatalk 2
yes i did
squeezyb said:
yes i did
Click to expand...
Click to collapse
More info would help like what errors you are getting
Sent from my DROID RAZR using Tapatalk 2
adb wont even find my device, so i am not getting any errors. is there a working RUU i can rename to PJ53IMG, and flash that through the bootloader?
http://forum.xda-developers.com/showthread.php?p=28723878
Sent from my DROID RAZR using Tapatalk 2
right, i tried this and had no success. the bootloader went through the process, and began to load the file, but did not finish the process. Could i possibly have tried flashing the wrong one?
i know this is something simple that i can flash, but it is not working
squeezyb said:
right, i tried this and had no success. the bootloader went through the process, and began to load the file, but did not finish the process. Could i possibly have tried flashing the wrong one?
Click to expand...
Click to collapse
Either should work but try the other
Sent from my DROID RAZR using Tapatalk 2
i tried using the one from unlimited.io, renaming it to PJ53IMG, but it would not flash... in theory that would do the trick right?
i am trying to download the file again, we'll see if that works. possibly corrupted on my end
squeezyb said:
i tried using the one from unlimited.io, renaming it to PJ53IMG, but it would not flash... in theory that would do the trick right?
i am trying to download the file again, we'll see if that works. possibly corrupt
Click to expand...
Click to collapse
Probably not. Use the one provided in Andy's thread. ADB is probably not working because debugging has been turned off.
Have you tried the recovery? Check to see if that works. If not try to fastboot a recovery. The command is "Fastboot flash recovery". Try with TWRP. If that takes then try to flash a ROM with that.
blazingwolf said:
Probably not. Use the one provided in Andy's thread. ADB is probably not working because debugging has been turned off.
Click to expand...
Click to collapse
the link in andy's thread is busted, or i would. unless i am wrong.. have you tried it?
On my side ill say do what the ther said, if you still have supercid you can unlock device and flash recovery and flash a working rom if you want it booteable
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
squeezyb said:
the link in andy's thread is busted, or i would. unless i am wrong.. have you tried it?
Click to expand...
Click to collapse
Yep. Working just fine for me.
Anyways, try the recovery route. I think it is your best bet.
blazingwolf said:
Yep. Working just fine for me.
Anyways, try the recovery route. I think it is your best bet.
Click to expand...
Click to collapse
OK FALSE ALARM!
I am back in business.
the first time tried flashing the RUU it did not work. i redownloaded, tried again, and it works fine.
Thank you everyone for dealing with my noob behavior.
<3 you all
squeezyb said:
OK FALSE ALARM!
I am back in business.
the first time tried flashing the RUU it did not work. i redownloaded, tried again, and it works fine.
Thank you everyone for dealing with my noob behavior.
<3 you all
Click to expand...
Click to collapse
Great to hear.
squeezyb said:
OK FALSE ALARM!
I am back in business.
the first time tried flashing the RUU it did not work. i redownloaded, tried again, and it works fine.
Thank you everyone for dealing with my noob behavior.
<3 you all
Click to expand...
Click to collapse
Everyone panics a little bit when the screen goes black
Sent from my DROID RAZR using Tapatalk 2
jamminjon82 said:
Everyone panics a little bit when the screen goes black
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
No truer words are spoken
jamminjon82 said:
Everyone panics a little bit when the screen goes black
Sent from my DROID RAZR using Tapatalk 2
Click to expand...
Click to collapse
Yep. And somehow time stands still for an eternity until something happens to let you know its alive.
I'll ask here first I achieved s off bit it destroyed my sd well to cut it short I flashed the ruu.zip I'm now s off with a locked bootloader no superuser or root and no recovery how do I install a recovery?
Sent from my ADR6410LVW using xda app-developers app
prairiedogn said:
I'll ask here first I achieved s off bit it destroyed my sd well to cut it short I flashed the ruu.zip I'm now s off with a locked bootloader no superuser or root and no recovery how do I install a recovery?
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
look here: http://forum.xda-developers.com/showthread.php?t=1435228
I really need help, recently my twrp won't back up the boot.img so I can't restore any of my nandroids, has this ever happened to anyone else and do you know how to fix it. Yea I make sure there is a check in front of boot also, I even unchecked it and rechecked it... please help me
your boot.img isnt modified from a rom so just grab it from the .zip file and put it in the backups folder for your respective backup with the proper file name and it'll restore just fine
ticklemepinks said:
I really need help, recently my twrp won't back up the boot.img so I can't restore any of my nandroids, has this ever happened to anyone else and do you know how to fix it. Yea I make sure there is a check in front of boot also, I even unchecked it and rechecked it... please help me
Click to expand...
Click to collapse
Are you s on?
Sent from my Nexus 7 using xda app-developers app
Indirect said:
your boot.img isnt modified from a rom so just grab it from the .zip file and put it in the backups folder for your respective backup with the proper file name and it'll restore just fine
Click to expand...
Click to collapse
thanks i wil from now on, i just wish it worked like normal
jesuscash said:
Are you s on?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
nope, im s off
Have you tried reflashing twrp??
#Root-Hack_Mod*Always=LTE
laie1472 said:
Have you tried reflashing twrp??
#Root-Hack_Mod*Always=LTE
Click to expand...
Click to collapse
yep i'm strating to think its my sd card, i formatted it and now its sticking... idk how long it will work tho
What firmware are you using, and what version of TWRP? I had some issues yesterday with 2.4+, and I would've been stuck if not for my S-Off status. I took the new OTA to experiment and quickly realized that it doesn't behave nicely with the older versions of TWRP. 2.3.1 was the most stable for this device for me.
______________________________
HTC Evo 4G LTE
ticklemepinks said:
yep i'm strating to think its my sd card, i formatted it and now its sticking... idk how long it will work tho
Click to expand...
Click to collapse
Well chances are that your good to go. However if you suspect that its your sd then I'd recommend getting a new one as soon as you can just to avoid the risk of this issue happening again. Amazon always has good deals "imo". Nevertheless Glad you got it solved.
#Root-Hack_Mod*Always=LTE
aarsyl said:
What firmware are you using, and what version of TWRP? I had some issues yesterday with 2.4+, and I would've been stuck if not for my S-Off status. I took the new OTA to experiment and quickly realized that it doesn't behave nicely with the older versions of TWRP. 2.3.1 was the most stable for this device for me.
______________________________
HTC Evo 4G LTE
Click to expand...
Click to collapse
im on the newest, and I actually haven't upgrade my firmware yet, at least i don't believe i have lol
laie1472 said:
Well chances are that your good to go. However if you suspect that its your sd then I'd recommend getting a new one as soon as you can just to avoid the risk of this issue happening again. Amazon always has good deals "imo". Nevertheless Glad you got it solved.
#Root-Hack_Mod*Always=LTE
Click to expand...
Click to collapse
yeah i have a 32gb class 10 which i got for 30 on sell, if i can find that price again i'll replace it
this which looks like a winner http://www.amazon.com/SanDisk-Micro...&qid=1360022045&sr=8-2&keywords=32gb+micro+sd
ticklemepinks said:
this which looks like a winner http://www.amazon.com/SanDisk-Micro...&qid=1360022045&sr=8-2&keywords=32gb+micro+sd
Click to expand...
Click to collapse
you will love that SD card. We both just got that one and love it.
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
saabguy93 said:
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Try reflashing a kernel. Might try stock first, then maybe Elkay's or dsb's writeable.
In case you're doing it a different way, try flashing it this way: flash the boot.img using the Flash Image GUI app. Then flash the corresponding modules for that specific boot.img kernel (can't mix and match) in Recovery.
If that doesn't help the situation, you may need to flash a different radio.
HTH!
saabguy93 said:
Everytime I go to make a call or receive a call the phone force closes and then signal drops off. I have flashed new kernals and have done a clean Rom install and problem continues. Any help would be greatly appreciated.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
have you tried a completly different rom?
.torrented said:
have you tried a completly different rom?
Click to expand...
Click to collapse
I have relocked my bootloader. Loaded the stock RUU and then Unlocked again, rerooted and installed Viper Rom and still same Issue.
saabguy93 said:
I have relocked my bootloader. Loaded the stock RUU and then Unlocked again, rerooted and installed Viper Rom and still same Issue.
Click to expand...
Click to collapse
Have you tried a different SIM.
Sent from my HTC6435LVW using xda app-developers app
Perhaps you accidentally flashed your radio partition? Reflash your radio and you'll probably be good to go. Either that or like someone else said try a different sim card.
Bigandrewgold said:
Have you tried a different SIM.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I put the SIM in my Nexus and I dont have any problems at all.
saabguy93 said:
I put the SIM in my Nexus and I dont have any problems at all.
Click to expand...
Click to collapse
Like the other guy said, try flashing a radio.
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Like the other guy said, try flashing a radio.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Flashed the new radio and still a no go. I keep getting "com.android.phone" force close when i go to dial a number.
Run the RUU again but this time try and just booting into android from the RUU and trying to use your phone
saabguy93 said:
Flashed the new radio and still a no go. I keep getting "com.android.phone" force close when i go to dial a number.
Click to expand...
Click to collapse
If you are getting com.android.phone fcs. then reflash ruu, DL' a rom of choice on your computer and transfer using ADB push (will take a second) . reboot to bootloader. flash boot.img, boot to recovery, flash modules, then flash custom rom. when phone reboots, wait about 45 seconds before running setup. If this process still does not work, please report back. Or PM me or another RC so we can figure it out for you in a quick manner.
Well this morning I switched to CWM recovery and loaded Digital Dream 1.5 and I'm back working. Thanks for everyone's help.
Sent from my HTC6435LVW using xda app-developers app
saabguy93 said:
Well this morning I switched to CWM recovery and loaded Digital Dream 1.5 and I'm back working. Thanks for everyone's help.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Yeah so it was a rom issue then
Sent from my HTC6435LVW using XDA Premium HD app
Not a Rom issue, I've had the problem on viper and hatka, both before and after soff and new radio. New kernel, old kernel.
I'm getting ready to try stock 1.15 before I ruu.. will report back.
Edit: Fresh off RUU, with the old radios flashed before the RUU. Still no change. Tried turning phone off, remove sim card, phone on, try to use cell connection (obvious failure), phone off, insert sim card and boot. Still no good. About to try above method using CWM and Digital Dream, as soon as it downloads.
Edit 2: Still no such luck. After digging through system logs, there's quite a few errors pertaining to the radio, IccCard, and RIL. One that particularly caught my eye was an error that there stated Ril_get_icc_status returned an error, and it should never return an error. Unfortunately, I didn't get a capture on the time I saw that, the radio reset which Su to reset which caused catlog to reset. Still have quite a few errors pertaining to SIM problems as well. I am way over my head after this point. I can interpret java, and linux.. but not so much understand when they're mixed together in Android.
http://www.pastebin.ca/2317800 This is logcat capture I got of the radio log. Unknown technology doesn't sound good to me....
http://db.tt/nbYfqEkb A full system log as soon as I could save after the force close. Couple things here and there.
I suppose if I can't get it fixed in a day or two.. off Verizon for a replacement. What's the purpose of a phone if I can't make phone calls on it?
Sent from my HTC6435LVW using xda premium
Unless an error loops continually, its okay.
Have you tried to manually select a different network? I'm not quite sure how to do it on a sense rom, but I do know that when I was messing around within my CM10 build and changed to the wrong network type, I lost 4G data in sense. I reflashed CM10, selected a different network and then flashed back and it was working.
Have no fear...
THE MAN IS HERE!!!
OK guys honestly if it's up to me, we should all be scared ****less if we were relying on me. I bought a DNA with this problem to see if I could fix it and so far I've relocked, run the RUU twice (executable 1.15) unlocked and flashed recovery and done clean rom installs, kernels, switched to every network mode imaginable. I took my sim out of my DNA working perfectly so I know the sim is good in a different DNA.
I just flashed the 2.04 radios and I'm going to see what that does. I promise I'm going to give this issue my everything though because I gave a lot for this phone that's otherwise NIB condition and MINT. OK and the radios didn't help
CharliesTheMan said:
Have no fear...
THE MAN IS HERE!!!
OK guys honestly if it's up to me, we should all be scared ****less if we were relying on me. I bought a DNA with this problem to see if I could fix it and so far I've relocked, run the RUU twice (executable 1.15) unlocked and flashed recovery and done clean rom installs, kernels, switched to every network mode imaginable. I took my sim out of my DNA working perfectly so I know the sim is good in a different DNA.
I just flashed the 2.04 radios and I'm going to see what that does. I promise I'm going to give this issue my everything though because I gave a lot for this phone that's otherwise NIB condition and MINT. OK and the radios didn't help
Click to expand...
Click to collapse
Any luck figuring this out? I have the same issue and have tried radios, kernels, ROMs, RUU, and am still getting the same error message.
jc332986 said:
I was having "com.android.phone" issues. I relocked then ran the RUU. It didn't fix the error. I unlocked, tried to go Into recovery and there was no recovery. I flashed cwm recovery, flashed busy box/superuser, and rebooted. I flashed cubed kernel. The fix for the phone was to fix permissions with system write capabilities. I'm not sure why the RUU didn't put the phone all the way back to stock.
Click to expand...
Click to collapse
spjoneser said:
I had this problem with my first DNA, warrantied it out after trying all the same things, flashing different roms, RUUing. After replacement I came across a thread somewhere and found that someone had fixed the same problem by simply fixing permissions before doing anything else, sounds like once you flash something else you're screwed.
Anyone try that first?
Click to expand...
Click to collapse
Anyone have an idea about the permissions described here?
same issue
dragonstalker said:
If you are getting com.android.phone fcs. then reflash ruu, DL' a rom of choice on your computer and transfer using ADB push (will take a second) . reboot to bootloader. flash boot.img, boot to recovery, flash modules, then flash custom rom. when phone reboots, wait about 45 seconds before running setup. If this process still does not work, please report back. Or PM me or another RC so we can figure it out for you in a quick manner.
Click to expand...
Click to collapse
This is driving me crazy I have same issue mine won't make or receive calls after I did s-off get same message com.androd.phone fcs. I re-locked phone then flashed original rom. Turned on phone still have same problem. So at that point I flashed kernalls h-boot and radios booted still same problem. Then I decided to re-flash RUU rom still same problem. Please help don't know what to do next.:crying:
jimmydee62 said:
This is driving me crazy I have same issue mine won't make or receive calls after I did s-off get same message com.androd.phone fcs. I re-locked phone then flashed original rom. Turned on phone still have same problem. So at that point I flashed kernalls h-boot and radios booted still same problem. Then I decided to re-flash RUU rom still same problem. Please help don't know what to do next.:crying:
Click to expand...
Click to collapse
I'm in the same boat with you my friend :crying:...Can someone please help us. PLEASE!!!
So currently I am pre-OTA 2.04.605.2 710RD, and I heard that this update fixes the SIM card issues. My phone has been plagued with this shortly after I got it. Currently it is rooted with S-Off, however I don't really use the feature much, my phone is pretty bone stock minus ClockworkMod and the menu button mod. I'm sick of the SIM card error and would like to update, however the install always fails in ClockworkMod (that's where it goes after rebooting) so my question is how can I update now, and just wait for S-off or root to become available later?
Put the stock recovery on and install the ota. Then reinstall cwm
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Put the stock recovery on and install the ota. Then reinstall cwm
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Flashed back to stock recovery, when trying to do the OTA I get an error 'assert failed: apply_patch_check("system/apps/Settings.apk)'
NeroMorg said:
Flashed back to stock recovery, when trying to do the OTA I get an error 'assert failed: apply_patch_check("system/apps/Settings.apk)'
Click to expand...
Click to collapse
if you like stock I will trade you mine
ocman40 said:
if you like stock I will trade you mine
Click to expand...
Click to collapse
I would gladly take you up on that offer, but I have my phone setup the way I need it, and I use it as a GPS a lot. It's hard to use it when the SIM error comes up 2-3 times a week.
NeroMorg said:
I would gladly take you up on that offer, but I have my phone setup the way I need it, and I use it as a GPS a lot. It's hard to use it when the SIM error comes up 2-3 times a week.
Click to expand...
Click to collapse
My wife's got the sim error once. I took it out, cleaned it with an eraser then put it back in pressing down pretty hard. Never an issue again.
ocman40 said:
My wife's got the sim error once. I took it out, cleaned it with an eraser then put it back in pressing down pretty hard. Never an issue again.
Click to expand...
Click to collapse
Unfortunately that has not worked for me, and I have had the SIM card replaced. I've heard the update fixes SIM card detection issues. Is this true? I still can't get it to install.
Just install the new radio's
ocman40 said:
Just install the new radio's
Click to expand...
Click to collapse
I don't know how to do that. Care to give a guide, or a link?
There is a thread in the dev section. Search it and then install. I think the sim stuff is in the new radio's.
NeroMorg said:
I don't know how to do that. Care to give a guide, or a link?
Click to expand...
Click to collapse
Are you s off?
Sent from my HTC6435LVW using xda app-developers app
Bigandrewgold said:
Are you s off?
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
First post he stated he was.