I was running a stock ROM, rooted, with the original radios. All was operating properly.
Flashed the leaked radio update. Everything still okay.
Flashed Das BAMF 1.6. It boots up fine (and looks gorgeous, btw), but my SIM card is not recognized at all. Symptoms:
When making a call, I see text in the upper-right corner saying: "SIM Card not found. Please \n the phone."
Settings > Call > Voicemail Service... tapping on this dropdown results in "Voicemail number change unsuccessful. Please contact your carrier if this..."
I tried turning the phone off, booting it once without the SIM card, then rebooting with it back in place. That didn't help.
Out of frustration, I restored my tbolt to the backup I made before attempting das BAMF. Magically, my SIM card is recognized and everything back to normal. ...I tried das bamf one more time, only to have the same crappy results... FYI, I was sure to wipe data/cache/dalvik before flashing the rom in recovery.
HELP!
EDIT: I've also just noticed that despite this being das bamf 1.6 remix, I don't see the 4-in-1 restart menu, nor a 6-bar signal indicator. I'm absolutely positive that I downloaded 1.6 remix... Am I in the twilight zone?
did you wipe data before installing the ROM?
nevermind i missed it. i dont know then sorry.
try redownloading and check md5
I verified the md5 before flashing.
i actually received the same errors but it did not impede functions of the phone. My data has been dropping, but that is not because of the ROM, it has been doing it since the 4G outage.
EDIT: Actuallly my voicemail says:
"We have a problem
Your voicemail settings could not be loaded. Please try again."
Never seen that before.
The more I look into it, I'm missing things that are pictured in the 1.6 Remix screenshots... all of this has me very confused. I'm going back to the stock ROM until someone else finds and resolves the SIM card issue.
I am experiencing the same issues here. I see 'no Sim Card Detected' at the top, I have none of the Reboot Options, no 6 bar signal, etc.
Seems to be kind of a big issue and yet noone has really offered solutions. I have done the full wipe aswell.
Thank you for everyone's time involved with making such a Great ROM....Plus this Community of Users is awesome...Take that IPhone!
Did you happen to download 1.6.1 or 1.6.2 and install just those first? Those two are just patches that required 1.6 as a base.
So, you would have to flash 1.6, then 1.6.1 or 1.6.2 over it as a patch - you can't just flash 1.6.1 or 1.6.2 by themselves. With 1.6.3, I think they went back to a full rom release.
Install via cwr, not Rom manager.
Sent from my ADR6400L using XDA App
I had the same problem with the SD card running Bamf Remix. What solved it for me was formatting the SD card. Obviously backup the SD card on your computer first.
Download 1.6.3 and do a flash. It's a complete download too, id give that a go. I didn't run into any of those problems. Are you flashing through rom manager or cwm?
Sent from my ADR6400L using XDA App
Dont manually mount data. For some reason when i did that the same exact this happened to me. No 6 bar signal and no 4 in 1 reboot menu.
Sent from my ADR6400L using XDA App
Thanks for all the suggestions, everyone. I solved the problem by using recovery rather than ROM Manager, and wiping data/dalvik/cache twice each (doing them only once wasn't sufficient, although idk how to explain it). I've been running 1.6.2 without issues for a day now. I'll move on to 1.6.3 after I see how well it's holding up for everyone else.
I ended up wiping everything and installing 1.6.3 and that fixed everything. Thank You all Gentlemen for helping!
You guys are genius!
Well I thought the issues was over after the install, But now Every time i receive a call ...Call Recorder Crashes. Also I am experiencing random reboots.
I was in the middle of a call and it rebooted on me.
Any Ideas?
Kodiax said:
Well I thought the issues was over after the install, But now Every time i receive a call ...Call Recorder Crashes. Also I am experiencing random reboots.
I was in the middle of a call and it rebooted on me.
Any Ideas?
Click to expand...
Click to collapse
For the Call Recorder, it sounds like you're running a custom kernel. Most kernels don't support the things that Call Recorder needs. For the reboots, well, can't help you there.
mcore09 said:
Thanks for all the suggestions, everyone. I solved the problem by using recovery rather than ROM Manager, and wiping data/dalvik/cache twice each (doing them only once wasn't sufficient, although idk how to explain it). I've been running 1.6.2 without issues for a day now. I'll move on to 1.6.3 after I see how well it's holding up for everyone else.
Click to expand...
Click to collapse
Other than wiping twice (???), what you said you did should be standard procedure. Flashing via ROM Manager and Kernel Manager are no-no's unless you get lucky. In an ideal world, they work. And in many cases, they do work. However, in many cases, they cause nasty issues. For example, if you flash some kernels via Kernel Manager, the device drivers don't get flashed properly and you have some pretty nasty problems. And when you flash via ROM Manager, well, you learned what happens. From now on, only flash via CWM and CWM only.
Thank you for your responses. I am only using the 4.4.7 kernel. Which come s with dad band 1.6.3. I think that it is this new kernel (4.4.7). I never had these issues with 1.6.2.
Sent from my ADR6400L using XDA Premium App
Try down grading your kernel to a slightly older version.
Sent from my ADR6400L using XDA App
I reflashed my kernel to the same 4.4.7 but downloaded the kernel from his standalone post regarding kernels. My call rcorder is working now. Hasn't restarted since then either. Crossing my fingers ...
Sent from my ADR6400L using XDA Premium App
Well it restarted randomly while I had it connected to my Laptop and set to charge. I was in the middle of a Call with someone.
Very interesting why its Randomly rebooting. Could be the new radio. May be that why verizon held out on releasing it yet.
Related
I found the solution to the problem described below. It was ROM Manager that was sabotaging me, for whatever reason. I went into CWM manually, wiped everything obsessively 3 times like I've seen other people describe, installed 1.6, and it worked perfectly. Too early to say how it actually runs for me but I least I've got it fully installed!
PROBLEM:
I started from stock rooted S-off ROM and installed Das BAMF 1.5, wiping everything as recommended. Under Settings/About Phone/Software information, the baseband, kernel, build number etc were all correct. Things ran OK, although battery life was pretty bad. But there were a number of anomalies. The Verizon bloatware still seems to be present. The location reticule is still present in the notification area. Etc.
Today I installed 1.6 over 1.5, again wiping everything even though it is said not to be essential. I did the install through ROM Manager. Everything proceeded as expected, the boot animation screen shows BAMF 1.6, all the About Phone information is correct for 1.6. But again, the location reticule is still present; signal strength indicator is 4 bars instead of 6, Verizon bloatware still present.
I know the real action is in the development thread but I still need a few more posts before reaching that exalted status. Anybody else seen/solved an issue like this? Any help is appreciated and if some kind moderator feels led to move this to the other thread, all the better!
[EDIT] A couple other anomalies are the extended Power Options and Reboot menu options shown in the 3rd and 4th screenshots at the beginning of the Das BAMF 1.6.1 development thread-- I don't have those. On the other hand, I do have BAMF Toolbox, Call Recorder, and other expected apps included with the ROM.
Thanks very much.
I'm having the exact same results. Frustrating!
Are you installing with ROM Manager, or directly from CWM?
Having the exact same issue and I installed with ROM manager. Should I reinstall 1.6 manually in CWR? I JUST rooted my phone a week ago and I think I may have flashed it 20X already, lol! I also have weird caller ID issues, it says CDMA call waiting when I miss a call, and Call waiting when I have a voicmail. If flashing it manually will fix these issues, I'll do it again!
Here's the thing I don't get. What's the fricking point of wiping 3 times?
If wiping == formatting a partition, then what good does it do to do it 3 times? None that I can imagine.
If wiping == deleting everything in a directory tree, then again, what point is it to wipe 3 times? What is accomplished on the second and third time that isn't on the first?
Just my opinion. I've never had a problem with wiping just once.
johnkc1975 said:
Having the exact same issue and I installed with ROM manager. Should I reinstall 1.6 manually in CWR? I JUST rooted my phone a week ago and I think I may have flashed it 20X already, lol! I also have weird caller ID issues, it says CDMA call waiting when I miss a call, and Call waiting when I have a voicmail. If flashing it manually will fix these issues, I'll do it again!
Click to expand...
Click to collapse
I would try hbooting the unsigned stock RUU. Then try flashing the rom of your choice through Cwm not rom manager. This should start you back at scratch with s off along with clearing up any bugs you can't seem to get rid of.
I had the same problem. Don't use Rom Manager for this Rom. Do it manually and everything will be like it should.
Ditto to that. All my unfruitful efforts were due to initiating the process via ROM Manager. Doing it all via CWR did the trick.
I came from Das BAMF Remix 1.6.3; performed factory wipe/data reset, wipe dalvik and wiped cache. I flashed the GB Radio via Hboot (update=yes; then updates by doing 2 things, then hit power to restart). I then flashed the ROM.
The first two (2) times I flashed 2.0-4.0 and could NOT get Wi-Fi to work, but I had 3G working no probs as well as GPS. Went out for a couple hours and had no issues. Got Back, and I still could not get Wi-Fi to connect. I reflashed radio..no dice...re-downloaded the ROM, did a complete wipe and reflashed both the ROM and radio. Still would not connect, even after I downloaded Test7 kernel (kernel shouldn't mess with my mobile connection?).
I then went and downloaded 2.0-4.01, and now I can connect to Wi-Fi. Now the problem is that I am stuck on 1x Mobile Data and cannot get 3G. I've re-wiped, reflashed and downloaded Imeseyons new kernel..still stuck on 1x. I have even tried toggling Airplane mode, but cannot get it to 3G connection.
Any ideas?
Dunno if it will make any difference but flash the rom 1st then either battery pull or adb into hboot to flash the radio. Maybe others can confirm if this might help or not.
Not sure if this is the root of your problem, but the directions given by the developers of these gingerbread roms indicate that you should put the rom and radios on the root of sd card, flash the rom first in recovery, don't reboot, get into hboot via adb, then let the radios flash, and reboot. It sounds like you flashed the radios first, and then the rom. Maybe this is causing your problems?
lanceman5000 said:
Not sure if this is the root of your problem, but the directions given by the developers of these gingerbread roms indicate that you should put the rom and radios on the root of sd card, flash the rom first in recovery, don't reboot, get into hboot via adb, then let the radios flash, and reboot. It sounds like you flashed the radios first, and then the rom. Maybe this is causing your problems?
Click to expand...
Click to collapse
Don't think so, cause I have tried both ways. Also, in Ad's posts he recommended both ways.
Either way, if I botched it the first time, it doesn't make sense that with the same radio I was getting 3g but no Wi-Fi, but now I'm getting Wi-Fi and no 3g.
I reflashed back to Remix 1.6.3 and have 3g+Wi-Fi right away.
And 3g returns..On 1.6.3.
Sent from my ADR6400L using XDA App
Someone will correct me if im wrong, however it could ne a kernal issue, had the same problem, flashed imo's 2.4 test 7 kernal, and now i get get service on bamf 2.4, just a thought
Sent from my ADR6400L using XDA Premium App
Thunder Droid said:
Someone will correct me if im wrong, however it could ne a kernal issue, had the same problem, flashed imo's 2.4 test 7 kernal, and now i get get service on bamf 2.4, just a thought
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
When I wiped and reverted back to 1.6.3 I lost a Superuser file. I decided to re-root and start from scratch.
Re-rooted, then flashed 2.0-4.1 and let it startup. Then shutdown and went into Hboot and flashed GB ROM. Went through a normal startup and I had 1x which after a couple of minutes turned into 3G, but very laggy. I then flashed Imo's 2.5.4 kernel and re-started. 3G came up and speeds were just fine.
A lot of work to get BAMF to work, but I'm happy. Now working on adding Launcher Pro, Fancy Widget and a few other personalizations.
I have checked the forums for this problem, I mean looked! Can't find anything.
My rezound keeps rebooting every 10 seconds. It turns on, then ill be using it, then BOOM reboot. Repeat...repeat....
What should I do? I wiped EVERYTHING.
I also wiped my SD Card as well, Everything like I mentioned above.
http://forum.xda-developers.com/showthread.php?t=1394659
Its a sticky in the General Forum.
Thanks! I'm gonna try this out!
This didn't work at all.
I followed everything, like 5 times. I removed the SIM card and the SD card, and cover. Everytime I go to type in the code to swith the network, my phone reboots, but only when I press a number to dial.
Are you rooted? If so what ROM and recovery are you running?
Well I am assuming I am rooted, I am on Clean ROM 4.1 SENSE ICS on Amon Ra
I have a weak signal, I checked to see if the network was the problem, and it was not.
Anytime I go to call anyone, or to dial, even if the back antenna case is on OR off, it reboots... I have no idea what to do. I will do anything to fix this.
EDIT: correction, now when I'm doing anything, when 30-45 of when im operating the phone, it will reboot
please help, My phone is TOTALLY UNSTABLE. :/
Try to clear cache and dalvik in recovery. If that doesn't work try wiping data.
Sent from my ADR6425LVW using xda premium
I just did, along with that; I flashed the latest version of rez rom to see if that changes anything. I will keep you updated, thanks.
Nothing Changed! I went to go dial A number, and right when I dial the first number, it freezes and reboots. Even If I flash a new rom and everything. What do you suggest.
It would help to know what you did before this started (was it installing CleanROM ICS 4.X?)
Did you do follow Scott's RUU instructions prior to installing his ROM? If no, there is a possibility that the new kernel has confused your old firmware. If yes, do it again and see if the new stock ROM is working for you.
If you don't know what I'm talking about, look right under the pictures in post one of Scott's 4.1, there is a link regarding preparing for the ROM. Go there and follow it closely.
Best of luck.
You had the same problem that I just fixed,
like me you probably used a trash guide to upgrade to RUU.
Use this one:
http://www.teambamf.net/topic/3528-guide-to-install-ics-ruu-and-firmware-windows/
kernal
You need a kernel patch for GB firmware or these reboots will happen. To fix update firmware......instructions on xda
The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
vash265 said:
The gist of my problem: Earlier today I successfully installed the latest CM9 from Joker (.0.7.0.0). Unfortunately, all wireless services other than WIFI were down (including SMS and telephone), and on start the phone produced an error about the com.android.phone force closing (or some such). I figured I had screwed something up, so I reflashed the clean stock firmware.
Since then (roughly 12 hours ago), I've been getting the stuck on the boot screen whenever I try flashing CM9. Relevant details follow:
Logcat doesn't help -- it tosses an error about the shell directory or file not being found (the exact error message escapes me, but I can reproduce it if need be).
I've tried formatting cache, data, and system, followed by a wipe (or two) on several occasions.
I've also tried flashing various versions of CM9 -- specifically .0.7.0.0 and .3.1. Both give the same result. I've also tried whatever version is in the KitchenSink v2.11 installer. Same result.
My CMW version is the 5.0.2.8. I installed it through RomManager (as opposed to the command prompt on Windows, which I did the first time when it quasi-worked). I've read that using v2 fixes this issue, but I can't find a live copy anywhere, so I haven't been able to try it.
Rather than going for a completely new install every time I bork something, I made a backup just after I finished unlocking and rooting the phone. I just restore that backup after each attempt, and it goes back to working fine on the stock Android firmware (3.whatever).
Any ideas? I think I'll try starting completely from scratch again and not using RomManager tomorrow, but if anyone can point out my error before then and save me a lot of -- hopefully not wasted -- effort, it would be fantastic.
Cheers,
Vash
Click to expand...
Click to collapse
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Well, I got .3.1 working. Then tried to install .7 and it crapped itself again. Should I have cleared all the data/caches/etc. between the two?
Edit - I tried it again but this time cleared all the data between installs. It booted, but I got the same 'android.phone failed to start' message.
Edit 2 - Alright, I think I got it. I didn't clear anything between the two installs, but I installed each firmware twice without exiting recovery mode either time. It seems to be working (phone works, at least), although I'm not sure my 3G is working...
na7q said:
Use this recovery. http://forum.xda-developers.com/showthread.php?t=1218417
Or jokers at http://forum.jokersax.com/discussion/25/joker-recovery-for-the-photon-v3
I use the first link. Works perfect. Once you install the recovery. Wipe everything. Install 0.3.1. Boot into the system. Go back and flash the newest 0.7.0 update with gapps.
Should fix all the issues.
Sent from my SGH-I777 using XDA
Click to expand...
Click to collapse
Joker's recovery is a zip file you can flash from 5.0.2.8 if you don't feel like hooking up to the computer and using fastboot. But 5.0.2.8 doesn't work right to flash roms.
Sent from my MB855 using xda app-developers app
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
vash265 said:
Aside from not being able to connect to any 3G networks (which is a problem...), it looks like it's working. Any ideas why 3G doesn't work now?
Thanks for the help thus far =)
Click to expand...
Click to collapse
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Acvice said:
Install 3.1, boot, reboot to recovery, wipe cache and dalvik, install 7.0, install gapps, boot.
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
vash265 said:
Yep...already did that and got it to boot just fine. Now I'm struggling with poor reception. I've seen other users (different phones) mention radio upgrades, but I was extremely unfamiliar with the terminology. The phone seems to work okay, but I only get 1x reception for data.
Or were you actually suggesting to repeat the entire process?
Edit - Tried again, still no luck with 3G.
Click to expand...
Click to collapse
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Acvice said:
Before doing what i stated did you wipe everything (system, data, cache, dalvik)? Also, you still getting a forceclose upon boot or just crap signal? And are you on sprint or electrify?
Click to expand...
Click to collapse
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
vash265 said:
I wiped everything. I can boot into the OS and my phone works fine, but my data rate is stuck on 1x (so crap signal). I'm on sprint.
Click to expand...
Click to collapse
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
na7q said:
well did you have 3g on stock? there's no reason it would go to 1x unless 3g is unavailable. the rom shouldn't cause it to go into 1x.
Click to expand...
Click to collapse
Yep. Despite popular belief, I'm not a moron =) I'm in the dead center of 3G availability for Sprint in my area, and with stock android I get perfect 3G reception. I've read reports of the same things happening to other people, but haven't found a solution yet. I restored to stock after making a backup to try updating the PRL. I'll update again when I find out if it worked or not.
Edit - Sprint just sucks, apparently. http://www.sprintusers.com/forum/showthread.php?t=225908
When I rebooted to stock I checked the radio status and sure enough, 1xRTT. Evidently I am a moron =p
There was something wrong with the phone afterall. To fix it, I did the following:
Dial *#*#4636#*#*
You'll be presented with a menu. Go to Phone Information.
About halfway down the page, there will be a menu with a dropdown. Mine was set to CDMA. To fix the issue, I changed it to CDMA auto (PRL). I'm now receiving excellent 3G reception.
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
I had the same issue today between 2 and 3, but it wasn't letting me send texts even though I could receive them. Maybe a network hiccup?
I am on stock radios, didn't know new ones came out. It is working for me now.
in the same boat
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
cappiez said:
Have a VZW DNA, currently on Hatka 3.0.3. S-Off, latest radio, stock 2.04 kernel. Twrp
Shortly before I flashed the new radios, I had a problem that whenever I tried to connect a call, whether incoming or outgoing, com.android.phone or.. process.acore?? would force close. I can't remember what the exact name of the acore force close was. Anyway.
I was pretty sure I fixed the problem before I flashed the new radios, but either way, I have the problem again. And, I have noticed that after the force close, the SIM seems to reset. Get a toast message for preparing the SIM card.
It makes no difference whether its the stock dialer, or a third party like Go Contacts. Third party apps don't force close, just go back to whatever I was doing before I tried to connect the call.
I tried flashing the viper with both dsb's stock and cubed kernel with viper to no avail. I haven't tried RUU, or old radios simply because I haven't had time to back up.
Any ideas before I do RUU?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
sjhanson Today, 12:20 AM #1035
Junior Member
Thanks Meter 1
Posts: 11
Join Date: Jan 2011
I am running 3.0.3 now. I was running Viper until the big man published 3.0.3, then i switched back. But even on Viper I was getting the same COM.PHONE.ANDROID has stopped error.
Cheers!
http://forum.xda-developers.com/showthread.php?t=2126386&page=2
borkborkbork! said:
looks like we're in the same situation. I looked through the threads and this is another case of call errors. I found this thread and one other, not sure if it was droid dna related.
Click to expand...
Click to collapse
Link to any of the other threads?
http://forum.xda-developers.com/showthread.php?t=2157855
xDexter said:
Link to any of the other threads?
Click to expand...
Click to collapse
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
You went back to S-ON or just a different kernel?
TheJ0hnman said:
I had the same issue, actually was getting soft reboots upon receipt of an incoming call, happened to me after s-off. It took a bit of fiddling, but I finally got back up and running 100% by flashing stock kernel and a clean ROM install.
Click to expand...
Click to collapse
I also tried going back to stock ruu , nothing worked for me
borkborkbork! said:
I also tried going back to stock ruu , nothing worked for me
Click to expand...
Click to collapse
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
xDexter said:
I am having 0 issues anymore with S-OFF and .torrented's rom and suggested R/W kernel: http://forum.xda-developers.com/showthread.php?t=2150262
Click to expand...
Click to collapse
com.android.phone .. but I still get my txt messages, go figure. I think my partitions may be in rare shape from rom's, kernals, and all the other numerous changes. Never been the same after I got error 7 on schatka 3.0.2, I switched back and forth from viper/hatka and twrp/cwmr
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
xDexter said:
You went back to S-ON or just a different kernel?
Click to expand...
Click to collapse
Forgot about this post, sorry. Did not go back to s-on, just flashed stock kernel from here: http://d-h.st/Ma1, boot.img via fastboot and then the modules zip contained within in recovery, and everything was good.
This didnt work for me . Any other suggestions?
cappiez said:
I took my phone into Verizon yesterday, explained the situation. Told them it started after ota, and I had done a factory reset already. They tried a new SIM card to no avail, overnighting a new phone.
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
Basically I hd the same situation happen to myself, no calls or data but wifi was good. Mine started to fail slowly , firs \t it was showing a 1X connection but dl were about 3G speeds. Next I lost signals in areas I never had signal issues with. Then total loss. New sim card and spent hours on the support line and a replacement unit.
Got a PM request for assistance, and thought I don't have a lot of tips to offer other than what I provided before, I'm going to post a more detailed overview (as I remember it, it's been awhile...) in case it's helpful for any other who may come across it later. The bottom line for me was that once things broke, it didn't work again until I flashed stock kernel via fastboot +modules in recovery and did a clean install of Hatka 3.03 w/ Sense launcher. That said, because of my flashing compulsion and failure to fully test things once installed, I can't pinpoint the exact step at which things broke.
Initially, I: Bought phone and factory reset, did not take Verizon OTA. Fiddled around, hated Sense, unlocked, flashed recovery, flashed Viper 1.1.0 (?, whatever the base was), booted and setup, fiddled around, hated Sense, wiped data, flashed 3 subsequent Viper updates (1.1.1,2,3 maybe?), booted and setup, fiddled around, hated Sense. Wiped and reinstalled de-Sensed Viper a few times in an attempt to get rid of Sense as much as possible.
Then things get murky. I did s-off, and at some point flashed (recovery) a kernel, Cubed I think. Wifi or something was borked (as I understand is the case with Cubed/Viper), and I flashed stock kernel back via recovery (no modules, I didn't catch that part at the time) and restored my backup for good measure, leaving me on fully functional Viper 1.1.3. Everything worked for a few days, but I continued to hate Sense, and began searching for something more sensible. At some point I flashed Hatka 3.03 w/ de-Sensed options, went to 320 DPI, and thought everything was fine for about 18 hours until I realized my phone was warm, and figured out it was rebooting every time I received (or placed) an incoming call (boss was pissed and kept trying to call me, already gives me a hard time about being an Android fanboy so I'm never going to hear the end of that). After a few hours of fiddling and various recovery attempts including restores and full wipe/clean installs of Viper, I finally managed to get things up and running with A. flashing stock kernel via fastboot + modules in recovery and a full wipe/clean install of Hatka 3.03 w/ Sense + Xperia launchers and eventually a 380 DPI.
One of or some combination of the s-off/custom kernel/failure to reinstall stock kernel modules/de-Sensed/low DPI/pin lock/Widget Locker/Viper combo I had going fouled something up, which I know is not entirely helpful. If I found myself in this situation again, I would flash stock boot.img via fastboot + modules in recovery, and probably flash a stock ROM to rule out anything else, then wipe and flash things from there until I got where I wanted or it broke.
For the record, I'm now back on my Galaxy Nexus until stable-ish CM 10.1 is within sight or I get tired of waiting and sell the thing, I just can't tolerate Sense.
same issue
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
jimmydee62 said:
I've been reading wherever I see this topic and haven't found the answer that I'm looking for. Have tried everything said but nothing has fixed my problem can't make or receive calls. This problem happened after I turned s-off have relocked boot loader, flashed RUU, reset factory, re-unlocked bootloader, re-flashed different roms, and flashed radios still not working. No doubt it is a software issue. Does anyone know how to format internal storage on this phone. My thinking is if that can be done problem should go away and then can re-flash to stock. Any help would be most appreciated.
Click to expand...
Click to collapse
Have you tried fixing permissions? In some other post I read phone process force closing was just a matter of wrong permissions.
In other hand I think if you format system, data and cache the phone storage would just keep hboot and recovery; at that point you could only run RUU to stock or adb sideload from recovery if your CWM version has the feature.
Sent from my HTC6435LVW using xda app-developers app
still problem
Yes have fixed permissions. Also have formatted everything I could in CWM still have problem. Is there a way to format with ADB commands?