So I've inherited a milestone that has gone through the washing machine.
It partially boots, as in it kills itself before any human interaction, and I can start up and stay in recovery as well as flash whatever I want.
I think that when starting into android the cellular signal kills the entire phone and I've already tried to insert a script to disable the radio to no avail. (still tries to talk with GSM.)
So I guess my questions are; is there a ROM of some sort out there that the milestone radio does not work, will I have to do some software backflips and, will I have to chuck it?
Thanks
Have you tried first to open it up and use a hair dryer to dry it up, using cold air? If not, try that. Otherwise, try untagging the antenna cable from inside the phone or use a "Cell Phone Signal Blocker Pouch" to see if the phone boots in it while blocking the signal. I don't think this will work tho, because the phone will still be trying to find signal. I don't know what else to say. Good luck.
Related
So I recently got back from a trip to Maryland (I live in Michigan) and now I am experiencing frustrating behavior from my Tilt. In places where I use to have acceptable signal (typically 2 bars, sometimes one if I angle just wrong behind a wall) I now get "no signal", however, when I reset the phone or when I turned the radio off and then back on again it would connect to the network just fine. I tried to use the "Airplane Mode" in the communications manager to simulate switching the phone off, and almost every time I do this it immediately says that my SIM card is missing. I have to take out the card, wait a few minutes, and then reinsert it for the phone to work normally again. I don't believe this to be an issue with a loose card, as it only happens as soon as I attempt to use Airplane Mode. Jostling the phone, opening and closing it, nothing else seems to trigger this. Can someone explain to me what's wrong, and how I can fix it?
Have you ever flashed a rom on the phone or anything?
No, I use the stock 6.1 AT&T rom. I do use Manilla 2D, but I've been using that for awhile.
Sync up the contacts or use PIM backup, save all of your files and do a hard reset.
that's what I was afraid of, oh well, It'll give me an excuse to clean out my phone of apps I don't use.
thanks, I'll update if that works.
Yeah it's pretty painless to redo your phone. Good luck
asrrin29 said:
that's what I was afraid of, oh well, It'll give me an excuse to clean out my phone of apps I don't use.
thanks, I'll update if that works.
Click to expand...
Click to collapse
What happened. I have this SIM CARD MISSING problem as well
I am using the latest version of Touch Tools: pr1.4, and have my settings to "AUTO DISCONNECT DATA CONN', which works very well EXCEPT: every morning when I take the phone out of "sleep" I see that the data connection is ON.
I have traced the issue to ms MYPHONE, which is scheduled to run at 0517am every morning. I changed the run time to 0700am and after MYPHONE is complete, the data connection remains ON. It was OFF prior to MYPHONE running.
Every other application that requires or uses DATA, the connection shuts down within seconds after the app is closed.
Any thoughts or suggestions?
Hey Bro,
Check out G-Profile, you can set your data based on time or cell location.
'sup Bruce! Not a bad idea, but it is only that one app, all the others shut off after done, just like Touch Tools is set to do.
I guess I want to know if anyone else has this issue with myPhone, and have you figured how to stop it. It isn't a big deal, just one of those darn quirks that has me puzzled. Kinda like the last time I had to take a primary cover off my bike and ONE darn screw needed an impact driver to remove, the rest came out easy...why? Murphy's Law?
jdwilson said:
'sup Bruce! Not a bad idea, but it is only that one app, all the others shut off after done, just like Touch Tools is set to do.
I guess I want to know if anyone else has this issue with myPhone, and have you figured how to stop it. It isn't a big deal, just one of those darn quirks that has me puzzled. Kinda like the last time I had to take a primary cover off my bike and ONE darn screw needed an impact driver to remove, the rest came out easy...why? Murphy's Law?
Click to expand...
Click to collapse
Yeah, definitely Murphy's law!
Whoa! My droid 3 just did something weird! I started getting screen artifacts that looked like a black terminal and it said something about a BP failure and BP bypass. This a pop up showed up asking if I want to switch to global mode since no cdma tower was available ( I switched to cdma only and it save crazy amounts of battery now). Then my phone rebooted without me making a selection! This has never happened before. I got to see this stuff, but I'm wondering if its cause I installed Log This that I was able to notice anything. What is (a) BP ?
If this is all software related, could the bypass get us escalated priviledges?
Darksurf said:
Whoa! My droid 3 just did something weird! I started getting screen artifacts that looked like a black terminal and it said something about a BP failure and BP bypass. This a pop up showed up asking if I want to switch to global mode since no cdma tower was available ( I switched to cdma only and it save crazy amounts of battery now). Then my phone rebooted without me making a selection! This has never happened before. I got to see this stuff, but I'm wondering if its cause I installed Log This that I was able to notice anything. What is (a) BP ?
If this is all software related, could the bypass get us escalated priviledges?
Click to expand...
Click to collapse
That's a bootloader protection (BP) Bypass. That may be the way in! Any way to replicate that? We need *FULL* disclosure on what was going on. A logcat output would be great!
Open ADB and type:
Code:
adb shell logcat > /sdcard/logcat.txt
adb pull /sdcard/logcat.txt C:\
Then upload that file (C:\logcat.txt) to a sharing site and let us rip it apart.
Some people over at phandroid had similar BP issues. There was no bypass message though. Maybe they are somehow related?
http://androidforums.com/motorola-droid-3/387878-my-d3-crashed-bp-panicked-error.html
forum.xda-developers.com/showthread.php?t=1188279
Yes, but we need the output of dmesg from before the panic. logcat will provide that.
BP=Baseband Processor=Radio
Something caused the radio to go into panic mode and it rebooted the phone.
This is not a way to get root unfortunately. The radio is setup such that in order to access it you need to bypass the AP (Applications Processor) layer where the OS and kernel etc. reside. That is what BP Bypass or Passthrough mode is for.
When you flash an SBF file the last stage of the flash re initializes the device for BP Passthrough to flash the radio partition.
The radio is literally a separate chipset on the board from the OMAP SoC and there are various access modes and device interfaces for all of those components.
Well bummer, I was hoping for something useful. At least we know that this has already been covered instead of wasting our time on it. Thanx for the info, knowledge is the key to everything.
either way, it'd still be nice to know what caused it.
Mine did the same thing shortly before it went to complete ****. After that happened it started rebooting itself all the time, rebooting itself coming back up with the welcome to android screen, even though there was no factory reset, it would reboot during calls, it would tell me i had missed calls from tomorrow. Browser barely functioned, apps would constantly force close. I brought it in to verizon after 3 days of it. Got a new one and traded my wife for her X. And now root comes. Ohh well i guess ill have to get by with a bionic.
pplude said:
either way, it'd still be nice to know what caused it.
Click to expand...
Click to collapse
I think it has something to do with not having CDMA signal. Just a guess. I have my phone set to CDMA only to save lots of battery, and sometimes all signal drops and then I get signal again (it happens when bouncing between 2 towers where I live) and then I guess the radio freaks.
I've only had it happen once, but I have notice that I had pretty good signal then bounced over to another tower and when I bounced back (all in a short time frame) is when it happened.
Just a guess.
I am hoping someone has dealt with either of the following problems, and come up with a way to effectively diagnose and fix either.
The phone - 1101 build; running AT&T Stock KK4; rooted via kernel swap method (using stock KK4 kernel after swap, i.e., do not have clockwork recovery); some AT&T bloatware frozen with TiBu, otherwise stock with root
Problem #1 - roughly once a day, the phone will freeze when in sleep mode; I have had this happen with both the slide to unlock and Exchange PIN lock screen up; when I hit power to wake the phone, the screen wakes up but is unresponsive and then the screen won't shot off again; live wallpaper is frozen in place, but if the phone was plugged in, the battery icon continues with the animation loop. And if the phone is not plugged in, battery power drops rapidly in this state.
The phone isn't completely dead, because if I connect/disconnect it via USB (set to debug mode) to my laptop, the computer recognizes the phone is connected, but it is dead enough that if I call the phone, it does not recognize the missed call. The only way I can restore the phone is a battery pull. Usually it takes several minutes for the phone to come back after this, acting like it would if I had flushed the dalvik cache or installed an update.zip from recovery.
Problem #2 -also roughly once a day, at random times the screen will wake up momentarily, then clear, and I will hear the AT&T boot up sound, after a short while, the phone will run through the media scanner and any other startup launches, acting as though it had been turned on, but the battery stats show continuous uptime throughout. I have had this happen when using the phone, including when on a phone call (and the call did not drop).
I have seen problem #2 on virtually all of the AT&T GB leaks, and it seems to get more frequent the more apps that are installed. I had not seen problem #1 until recently.
The phone is out of warranty, and owned by my employer. I am not due for a new phone from them until July. I've done more master clear/reflash stock cycles than I care to admit, tried replacing/testing for disk errors the external SD card, etc..., and am afraid of doing that and having the problems come up again.
Any thoughts on how to diagnose either of these problems?
Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.
I have the exact same problems. Hope someone comes up with a fix. The only help I can give you is that when the phone freezes, instead of pulling the battery, you can hold the vol up & power buttons for 10 seconds and the phone will restart. Easier than pulling your phone apart, especially if you have it in a case, like I do.
Sent from my SAMSUNG-SGH-I897 using Tapatalk
korockinout13 said:
Hmm... I don't really think there is an exact diagnosis for any of these issues. Some phones are just problematic like that. The only thing I can suggest is trying a different ROM or kernel, and that might help your stability.
Click to expand...
Click to collapse
So, the way I see it, unfortunately these problems could be a function of:
Bad hardware
Misbehaving app
ROM issue
Kernel issue
I tried pretty much every leaked AT&T GB ROM and had random reboots with all of them. Seems to track with the number of apps installed, but can't prove that. I have not tried any custom ROMs or kernels.
Since this is technically not my phone, I am trying to avoid doing anything that can't really be undone if I need to turn the phone back in at some point. And I need something that can be a daily driver for work calls and Exchange email, and rely heavily on tethering when I am on the road.
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.
Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much
studacris said:
Nothing you do can't be undone, it's just a simple Odin flash away.
Be sure to back up your efs folder before flashing too much
Click to expand...
Click to collapse
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)
stoobie-doo said:
I've used Odin with the various GB leaks; if I go further afield (heck, performance is dicey already, how many more problems could I have with one of the ICS alphas), is it still a straight shot back to stock KK4, or are there other steps to do first?
And before I go down that road, any suggestions on diagnostics (other than yet again pulling apps off of the Captivate to see if one of them is the culprit...?)
Click to expand...
Click to collapse
You actually might have less problems on ICS. But it all depends. You can always get back to stock with one, bootloader-free, safe flash. Diagnostics wise, there isn't really much you can do besides removing apps. I would only worry about the ones that are constantly running in the background, as they could possibly be screwing with the phone while in sleep. I think it's unlikely that this sort of testing would actually help though. I still say try something different.
stoobie-doo said:
Anyone with ideas on what to test, or how to capture enough log information to figure out where the problem is, would be a big help. Otherwise, I am stuck riding this out until July when I can get a new phone from my employer.
Click to expand...
Click to collapse
I am having the same issues except in my case I have tried to recreate the conditions and check memory and I am close to maxing it out. Part of my problem is that I come from a Palm background and I have found that Android, or at least the Cappy, is not as responsive (I was really spoiled by Cards on my Pre) I was thinking that my Android noobness is causing me to push the phone too hard and locking it up. FWIW, you might want to check memory issues
Recently my N7000 got a weird and pita wifi problem.
So wifi is working fine, connected to the AP etc. I leave the phone be, charging or not doesn't matter, wifi sleep policy doesn't matter.
When i get to it, wifi MIGHT be gone. It's on, but doesn't find networks. Cannot disable. To fix it, i either reboot, or enable Wifi HotSpot and disable.
The moment i do it, the moment wifi start seeing APs again.
logcat bellow, a few of the last lines. It was to big to post it all.
http://logcat.scheffsblend.com/view?id=1849002
Currently i'm running CM11, but i've been able to replicate it in all current AOSP roms, and Stock 4.1 roms.
Anyone care to advise?
Ok, so this doesn't end like this, i'll provide a update.
I tried EVERYTHING. Stock 2.3, stock 4.1, JB bootloader, custom wifi drivers and nothing fixed it. Simptoms remained the same.
Then i went to the hardware side.I opened the device multiple times... lost a screw in the process. I noticed that with the device opened and on, if i pressed the general position of the wifi chips and metal covers, wifi would die instantly. This probably could be fixed with a reflow, but i had no heat gun (and the hairdryer doesn't cut it). So. i cut a few small peaces of paper, folded them a few times into small pads, put them over the wifi chip. and a few other positions, slammed the cover in, screws on it and wifi has been stable ever since. Not sure this will be a permanent solution, but it's working now