Related
Alright...so here goes. I have been out of the smartphone market for some time now and am getting this awesome phone tomorrow. I am friggin excited! Feels like Christmas in the summer! Verizon tells me that it will already come with the 6.1 update installed. Anyone gotten one recently to verify this, and how do I tell when I get it...also how can I tell the radio that it has? I also already wanna mod this machine, and although I am selfproclaimed computer savvy, I am a little nervous about bricking the phone. I think I def want either an iCRAP setup to piss off everyone at work, or nfsfans 6.5....although I would like to have someone walk me through it. I have to say, everyone on this forum has done an excellent job with their machines and I am impressed. Also, I don't know that this will even be an issue, but it will still need to function as a phone and pda...as I have read in a few different places that some cant use their phone function anymore, etc. And I definitely wanna get the GPS running ASAP, due to travel on the job. Any help will be greatly appreciated, and I will def help out anyone on here if I can. I also am not sure about when and when not to let customizations run...any help with that would be awesome too
i am also getting this phone from vzw thursday, they told me it comes standard with wm6.0 idk or care. as soon as i get it im gonna flash a custom rom.
Hey there, I'm a fellow Verizon user. It was kind of nerve-wracking flashing the ROM for the first time, but its really NBD once you get into it (be sure and try android too!).
Do your reading first, there are tutorials all over the place. Something to remember about customizations - Don't let them run on any official Verizon updates you see floating around the internet, as they will cripple your GPS. Don't let them run on any ROM designed for another carrier. If you're flashing a generic or Verizon-specific CUSTOM ROM, let them run.
And you can check in settings to see your radio and OS version and all that (under "about" I think, correct me if I'm wrong)
Have fun!
so if i run mr1 from verizon to get to wm6.1, then I SHOULD NOT not run customizations. What buttons do I press to do a hard reset before that comes up? But, if I were to do NFSFAN's 6.5 rom, then I SHOULD let customizations run. Also, could someone point me to a set of CLEAR directions on doing the flashes? I have read a bunch of them, and it seems they are all missing little parts.....probably something so familiar to the editor, they just forget to include in the steps.
Yes, the lack of CLEAR instructions as a stickey is a real problem on a lot of boards. I've read threads over 300 posts in order to get solid info. I don't mind searching for info, but jeesh, guys it is unbearable. Granted some of this stuff is not for the faint of heart, but there can be so much info, and sometimes it is often confusing and contradictory. The SR. members and the Admins need to get their heads together and take a month to provide the community some solid resources, and weed out some of the erroneous info here. We want to make having this phone FUN and Practical. A Case in point is trying to get GPS working. Have you guys looked at all the info on here about this. Granted there is variety of carriers, but it shouldn't be brain surgery.
Also chevyspd,you want to do a SOFT reset before the customizations. Use your stylus to depress the small hole in the bottom of the phone before they run. Should be golden. A HARD reset will restart the flashing process from scratch.
10-4....so only do a soft reset by only pressing the button in the hole on the bottom before customizations runs. That is very contradictory from about 50 other posts I've read so far. A whole bunch of them say to do a HARD reset, but I will remember not to. But, when I do a custom rom like NFSFANS, I don't have to do a reset at all....correct?
You wouldn't believe how many times I got flamed for that same kinda comment on other forums.....interestingly though....Also...if I flash to NFSFANs 6.5, are the cubes still active, or is that something from HTC that gets written over with a new rom?
So, my new phone already has 6.1 right outta the box. Interestingly enough, it went to the customizations screen as soon as I powered the phone up, so I immediately hit the soft reset. How can I tell if what I did worked, and if it didn't, how can I fix it so I can use 3rd party gps programs?
Wow; a lot of questions. I'm not sure about NFSFAN's rom. To see if the gps works, make sure you have the Settings>phone>services>location is set to on. Then make sure the external gps setting is set to Comm4, then hardware NONE, baud 4800, and allow Windows to manage gps. Do a Google search for HTC QuickGPS if it's not already on your phone (varies from carrier to carrier) and Install it; Run it, outside and allow it 10 minutes to get a lock. If gps is working, then you should be golden. You will probably need to turn the radio on after every re-boot; and be aware that leaving the radio going WILL drain you battery faster than usual. All this assumes you are using the stock rom, and not one of the custom ones; each to those varies, some work out of the box so to speak, some of them require tweaking.
Funny i just got the phone yesterday to, but i actually already had it for about a year lol, just replaced the one i broke on saturday. But honestly the first thing i did with the phone is put in my SD card and boot up Android....
I really want my GPS back again but i dont really want to go through the hassle of unlocking, flashing, unlocking, and flashing, but if you deem it neccessary. and maybe i will to one day soon. lol heres the link
http://wiki.ppchaven.com/index.php?title=Pocket_PC_WIki:FIX_VERIZON_GPS
chevyspd said:
You wouldn't believe how many times I got flamed for that same kinda comment on other forums.....interestingly though....Also...if I flash to NFSFANs 6.5, are the cubes still active, or is that something from HTC that gets written over with a new rom?
Click to expand...
Click to collapse
The cube is way back when man, sorry but those things are old school already. lol so when you flash to the 6.5 NFSFAN rom it will not have the cube, but it will have titanium and manilla 2d, which in my opinion are awesome replacements
chevyspd said:
But, if I were to do NFSFAN's 6.5 rom, then I SHOULD let customizations run?
Click to expand...
Click to collapse
Yes, and remember to install the Verizon cab in his post :thumbsup:
Well, the phone didn't come with the cube anyways...lol...so anywho...I think the GPS is working anyways...just gotta find a free GPS like vznavi or something.
Does anybody experience problem with the g-sensor?
I had my Magic changed (after brick for a wrong spl) and I realized lately why auto orientation change is not working,
the g-sensor is giving crazy values (20g), auto-calibration does not work, it stops since it sense strange values.
My guess is a hardware problem. But since I have a Q-Technology Hero-port firmware I would like to know if anybody ecperience this with this firmware.
I don't remember if it was working immediately after taking it from Vodafone shop since I flashed the new firmware straight away.
Question: where can I get the original Vodafone firmware?
Thanks
Byron
It occurs to me that I might be having a similar problem. I reported it against the Cyanogen ROM I'm using, thinking it was a Donut + 32A problem. I did, as it happens, get mine "serviced" after I bricked it earlier and I can't remember the orientation stuff working since then.
Here's what I reported, I assume you are getting very similar results:
http://forum.xda-developers.com/showpost.php?p=4536450&postcount=923
After some further searching I came across this thread:
http://forum.xda-developers.com/showthread.php?t=545345&highlight=sensor
I assume that deleting these files causes the automatic calibration to occur, which is probably what you've referred to as trying without success. I deleted those files myself and it has not fixed my problem.
Using the Sensor Debug application on the Market, I'm noticing that with my phone sitting idle on my very stationary desk I get the following values:
azimuth ~= 303
pitch ~=123
roll = 32
force on x-axis = 17.95...
force on y-axis = 28.19...
force on z-axis ~= 1
magnetic field ~= (-21, -12, -23)
where I'm using the "~=" notation to indicate constantly fluctuating approximations. Are those measures forces normal?
Also, I can't help you with a Vodafone ROM, but if you go to the HTC website there are a few factory ROMs in the support section for the Magic. Check them out, but obviously choose very carefully.
I've sent a help request to the folks at HTC about this issue.
After Googling the subject, I've discovered that the HTC Hero comes with a user-accessible sensor calibration tool. HTC will likely not release for their other handsets, but the fact they've released it into the wild means they somewhat acknowledge that there is actually a problem with the sensors.
Well, the folks at HTC are a strange bunch. They seem to have completely misunderstood the reason I contacted them.
I contacted someone with a perfectly functioning rooted 32A and was able to procure their akmd_set.txt file. Thanks bcrook.
My original akmd_set.txt file causes the handset to have only left-to-right roll detection in portrait, or up-and-down roll detection in landscape.
Plugging bcrook's akmd_set.txt file straight in reverses the situation. I now have left-to-right roll detection in landscape, and up-and-down roll detection in portrait.
I have no idea exactly where to begin, but I suppose it's possible that merging the files will bring me to the desired resolution. Now I just need to figure out what the good settings from my file are, and identify the similarly good settings from bcrook. /sigh
I just flashed the MyHero ROM to my phone in order to get access to the G-Sensor Calibration tool found in the Sound & Display settings. This looked very promising but I kept getting the "Calibration aborted" message. Why me?
not able to load rom
while flashing rom..m getting error...No signature(731 files). plz help
ultimaterakesh said:
while flashing rom..m getting error...No signature(731 files). plz help
Click to expand...
Click to collapse
Really off-topic, you'll probably find answers elsewhere. This thread is specifically about G-Sensor Calibration difficulties.
In the meantime, I'd suggest getting your files directly from the source, and reading all the instructions carefully. If the files are distributed here on these forums, then make sure you definitely read the entire first page of posts, since they'll usually have lots of important information.
Every few weeks I try out a new Hero-based ROM and see if the Calibration Tool works. I checked out Evil Hero yesterday. Still no dice. The Calibration Tool does not abort prematurely, however, and the /system/bin/ssd_bma15_usr file is definitely there.
I can confirm, however, that if the /data/misc/akmd_set.txt is missing, then it is generated using fixed tags somewhere. And running the Calibration Tool does not appear to even alter the calibration, it just doesn't visibly fail anymore. I had "adb logcat" running during a calibration run, and I noticed the sensors being opened and closed but no errors reported.
I don't know the specifics, but it's possible that the ssd_bma150_usr is just a stub. So my options to get my phone 100% functional are still:
A - wait for official HTC Sense UI release for Sapphire
B - send phone back to HTC's support team
I tried out MyHero 2.0.2 today. No dice. This ROM is apparently based off the official HTC SenseUI for Magic, and there does not appear to be any G-Sensor Calibration available anywhere.
It's still a little too early to tell, but I have a feeling that the official HTC SenseUI for Magic simply lacks the tool. I'll wait for the release for my region before giving up. /sigh I suppose only the Hero has a calibration driver HTC can be bothered with supporting.
This likely means, though, that my list of available options shrinks to a single option: send my phone back for repairs. And since this hardware fault only presented itself when I last did that, I'm just not entirely confident.
any solution found?
kirkusss said:
any solution found?
Click to expand...
Click to collapse
Not yet, I'm afraid.
If you'd like to help, you can search the internet for a leak of the Diagnostic SD Card image. If you boot your phone while holding the Volume Down key, you will quickly see it try to load one the SAPPDIAG.* files. That's the file we need. I was on the trail for a little while, but I hit a dead-end when I got to an unlisted HTC website that required a password.
Another way you can help is by doing a nandroid backup of your phone. Then go and try out one of the Sense UI ROM releases found on these forums and see if there is an option anywhere to calibrate the sensors. Once you've checked out the ROM, post your results here and then you can restore your nandroid backup so your phone is back to normal (or keep the new ROM if you like it better). I've already checked MyHero 2.0.2 and an older version of Evil Hero, but there are a few more to check.
A word of warning to everyone, it is very important that you do a nandroid backup of your phone fresh out of the box and BEFORE you do anything else. If only I had done this, I would still have my original akmd_set.txt file and my phone's sensors would not be misbehaving.
Today's adventures with official HTC update 2.17.861.3
Okay, so I decided to take the plunge and try out the official ROM update for my Sapphire 32A. I found it here at HTC's support page, version 2.17.861.3. I figured there was a chance an official ROM would have drivers that the cooked ones floating around here don't, and it was worth checking to see if I could fix my G-Sensors once and for all.
I struggled for a while to get the ROM update to even work. Eventually I learned to enable USB debugging, delete the ADB device and drivers from Windows 7's device manager, grab a copy of the Vista64 drivers and install them. So the ROM update finally worked, yay!
I'm going to put this in large bold letters as a warning to others right now:
HTC Magic ROM update 2.17.861.3 installs a perfect SPL!
That is to say that if you install this ROM, you won't be able to fastboot a new recovery or system ROM.
I can also confirm that the official ROM does not fix my problem, it is just as clueless about true calibration as any of the 3rd party cooked ROMs. The closest I ever got to this sort of solution was a Hero-based ROM and it never worked either. /sigh
So I figured I was completely stuck at this point, unable to install AmonRA's recovery and therefore unable to restore my nandroid backup to this morning's snapshot.
However, it dawned on me after a few hours of struggling to create a goldcard, the old bluetooth vulnerability exploited by flashrec might be present in this official ROM. As it turns out:
HTC Magic ROM update 2.17.861.3 is vulnerable to flashrec!
So here I am back with CyanogenMod 4.2.3.1 and RA-v1.2.3, but with a perfect SPL. A significant step backwards, in that it'll now be difficult or impossible to update my recovery,seeing as CM is immune to the bluetooth bug and you need a non-perfect SPL in order to fastboot a new recovery. Oh well. Lessons learnt.
[duplicate post]
Okay, so on Monday my phone was shipped back to the technicians for repair regarding sensor calibration. As you can tell by reading this thread, trying to fix this myself was impossible without somehow getting access to the Diagnostic SD card image for Sapphire, which as far as I know as not been leaked and only resides on HTC's (password-protected) technicians' website.
I got it back today, and the issue was still there. So I sent it back immediately with quotes from the leaked service manual detailing exactly what they need to do. And I also mentioned factory-installed applications they can use to determine if the problem persists, namely HTC's Teeter and simply trying to get the phone to notice a transition from portrait to landscape. /sigh
Anyhow, I don't know what I'm expecting or even hoping for. Is it better to have technicians who were previously incompetent but can fix my phone with my instructions? Or is there a chance my phone really is broken and the technicians are indeed competent and trying everything they can to no avail? /shrug
Mine is also at the local htc repair center. As far as I know they are waiting for the calibration image.
Do you have a link to the leaked service manual?
I'll keep you posted
http://phandroid.com/htc-magic-manual.pdf
I pretty much just Googled it.
Okay, my phone got back from the service centre today and it is all fixed!
I noticed that they installed a newer version of the basic Android 1.5 HTC ROM without SenseUI: 2.17.861.5 (only .3 is available for download) and the SPL was a non-perfect version, which is very nice. The technicians apparently had to replace the motherboard.
Judging by how few people seem to have this persistently broken sensor issue, I would say it is a very rare manufacturing defect. I am guessing that when the phone is built, the sensors are calibrated and this data is stored on a flash ROM somewhere on the motherboard. When there is no /data/misc/akmd_set.txt file, the kernel goes and fetches the data from this sensor flash.
Because this data is not part of the usual wipe-and-flash area where user and system data is stored, it is not able to be fixed with any consumer-accessible software.
The Diagnostic SD card that was my Holy Grail for so long was also probably unable to fix this problem, although it certainly narrowed it down enough for the technicians to know that only a new motherboard would solve it.
Can you please upload the SD card image somewhere?
Thanks
I never at any time had access to the Diagnostic SD card. It can only be retrieved from HTC's website, and only if you have been given a password-protected technician / service account.
My HTC Hero was a dream to mod. I plugged it in, ran some ADB, and it worked like a charm. I flashed whatever I wanted whenever I wanted, and it worked fine with my computer which is running 64bit Win7.
Now the Samsung Epic... this is disappointing. ADB doesn't work any more. It says there are no devices attached and I can't mount my SD Card through the phone to my computer. I can't get the drivers to work properly. I've tried reinstalling the "proper" ones from the clockwork mod thread and also reinstalling the ones that windows update wants to install.
Nothing works. Modding this phone is a nightmare and now it doesn't work with my computer at all. ADB used to work, kind of. Now it doesn't even detect the phone.
Samsung did a bad job. I love the screen and the blazing fast hardware, but the difficulty with modding is ridiculous.
If anyone has any suggestions, I'm game. But if I can't get full control over my phone via command prompt like I could with my Hero, I'm going back to HTC before next week.
Leon H said:
My HTC Hero was a dream to mod. I plugged it in, ran some ADB, and it worked like a charm. I flashed whatever I wanted whenever I wanted, and it worked fine with my computer which is running 64bit Win7.
Now the Samsung Epic... this is disappointing. ADB doesn't work any more. It says there are no devices attached and I can't mount my SD Card through the phone to my computer. I can't get the drivers to work properly. I've tried reinstalling the "proper" ones from the clockwork mod thread and also reinstalling the ones that windows update wants to install.
Nothing works. Modding this phone is a nightmare and now it doesn't work with my computer at all. ADB used to work, kind of. Now it doesn't even detect the phone.
Samsung did a bad job. I love the screen and the blazing fast hardware, but the difficulty with modding is ridiculous.
If anyone has any suggestions, I'm game. But if I can't get full control over my phone via command prompt like I could with my Hero, I'm going back to HTC before next week.
Click to expand...
Click to collapse
Every time someone on here says that ADB doesn't work it has ended up being their computer that is the problem. Either they didn't install the drivers correctly or there is something else wrong. I suggest you try it on a different computer. The majority of us have never had a problem with ADB and as an ex-Hero user I think the epic works just as well over command line.
richse said:
Every time someone on here says that ADB doesn't work it has ended up being their computer that is the problem. Either they didn't install the drivers correctly or there is something else wrong. I suggest you try it on a different computer. The majority of us have never had a problem with ADB and as an ex-Hero user I think the epic works just as well over command line.
Click to expand...
Click to collapse
I'm working on getting a fresh install of 32bit WinXP, but I don't see why it doesn't just work on my Win7 install. I've tried it on XP before with similar (non-working) results, but I'll give it a foolproof trial and try to troubleshoot if it's the computer end or the phone end.
Leon H said:
I'm working on getting a fresh install of 32bit WinXP, but I don't see why it doesn't just work on my Win7 install. I've tried it on XP before with similar (non-working) results, but I'll give it a foolproof trial and try to troubleshoot if it's the computer end or the phone end.
Click to expand...
Click to collapse
ADB worked on my Win 7 64bit laptop when I was rooting my Epic. Had 0 problems.
PEBKAC imo.
Leon H said:
My HTC Hero was a dream to mod. I plugged it in, ran some ADB, and it worked like a charm. I flashed whatever I wanted whenever I wanted, and it worked fine with my computer which is running 64bit Win7.
Now the Samsung Epic... this is disappointing. ADB doesn't work any more. It says there are no devices attached and I can't mount my SD Card through the phone to my computer. I can't get the drivers to work properly. I've tried reinstalling the "proper" ones from the clockwork mod thread and also reinstalling the ones that windows update wants to install.
Nothing works. Modding this phone is a nightmare and now it doesn't work with my computer at all. ADB used to work, kind of. Now it doesn't even detect the phone.
Samsung did a bad job. I love the screen and the blazing fast hardware, but the difficulty with modding is ridiculous.
If anyone has any suggestions, I'm game. But if I can't get full control over my phone via command prompt like I could with my Hero, I'm going back to HTC before next week.
Click to expand...
Click to collapse
Ahh.. Why blame Samsung for having a phone that that is "difficult to mod". They never wanted you mod it, funny how you mentioned the awesome screen and "blazing fast hardware" in the same paragraph though, but still call it a bad phone.
ADB works just fine if you install the correct drivers.
Not insulting your decision to choose the Evo, they are both awesome, but the Evo won't save you from not knowing what you're doing.
PEBCAK.
First google search of the day = pebkac; good one!
TheDub said:
Not insulting your decision to choose the Evo, they are both awesome, but the Evo won't save you from not knowing what you're doing.
Click to expand...
Click to collapse
But maybe the Evo will save me from this driver fiasco. I've tested the phone on WinXP and Ubuntu now, and ADB works on both. But for whatever reason, the drivers on Windows 7 are not working. I've uninstalled them and reinstalled drivers from three or four different venues now.
Leon H said:
My HTC Hero was a dream to mod. I plugged it in, ran some ADB, and it worked like a charm. I flashed whatever I wanted whenever I wanted, and it worked fine with my computer which is running 64bit Win7.
Now the Samsung Epic... this is disappointing. ADB doesn't work any more. It says there are no devices attached and I can't mount my SD Card through the phone to my computer. I can't get the drivers to work properly. I've tried reinstalling the "proper" ones from the clockwork mod thread and also reinstalling the ones that windows update wants to install.
Nothing works. Modding this phone is a nightmare and now it doesn't work with my computer at all. ADB used to work, kind of. Now it doesn't even detect the phone.
Samsung did a bad job. I love the screen and the blazing fast hardware, but the difficulty with modding is ridiculous.
If anyone has any suggestions, I'm game. But if I can't get full control over my phone via command prompt like I could with my Hero, I'm going back to HTC before next week.
Click to expand...
Click to collapse
I had a similar problem but instead, I blamed Windows 7
Install PDAnet.. pick the appropriate device, then you can have full control over your "blazing fast hardware" P.O.S.
PEBKAC .. LMFAO...
Leon H said:
But maybe the Evo will save me from this driver fiasco.
Click to expand...
Click to collapse
yeeeeeaaaahh... that'll happen...
I've tested the phone on WinXP and Ubuntu now, and ADB works on both.
Click to expand...
Click to collapse
But for whatever reason, the drivers on Windows 7 are not working. I've uninstalled them and reinstalled drivers from three or four different venues now.
Click to expand...
Click to collapse
To kinda go along with my previous post, it appears as though ITS NOT THE DAMN PHONE...
Did you read what you posted ??? seriously... honestly ???.. it's not ur phone.
daddymikey1975 said:
yeeeeeaaaahh... that'll happen...
Click to expand...
Click to collapse
It did with the Hero. My experience with HTC drivers has been much better than Sammy drivers so far.
daddymikey1975 said:
To kinda go along with my previous post, it appears as though ITS NOT THE DAMN PHONE...
Did you read what you posted ??? seriously... honestly ???.. it's not ur phone.
Click to expand...
Click to collapse
I get that now, I was in the process of installing a new OS to test this. I blamed the phone at first, before I got around to testing it properly, but now I know where the problem lies.
I'm not blaming the phone anymore. It seems to work fine (besides the sd card mount, that will only work on linux). I'm blaming Samsung for their Windows 7 drivers. You can throw acronyms around all you want, but I think the problem is actually somewhere in how Samsung develops for 64 bit.
Also, I can praise the phone's hardware and curse the software. That's perfectly logical, by the way.
algorhythm said:
ADB worked on my Win 7 64bit laptop when I was rooting my Epic. Had 0 problems.
PEBKAC imo.
Click to expand...
Click to collapse
Thanks for your anecdote. Unfortunately, my setup is not working the same as yours. If you'd like to be helpful and tell me how you installed the working drivers, I'd appreciate it.
to OP, what you should know is, that even without any modding, and running on 2.1 , my epic will always be WAY faster than any evo.
now imagine how fast it is for me now, with my Quantum froyo...
I had the same problem with my phone not showing up on the computer, i know this may sound stupid but it works. I have 2 usb ports in the front of my computer and thats what i tired using for the phone it wouldn't work, so i plugged it in the back of the computer and now it works fine shows up everytime on my computer.. So i just bought a extra usb cord off ebay and have it constantly plugged in the back of the computer.
ericizzy1 said:
to OP, what you should know is, that even without any modding, and running on 2.1 , my epic will always be WAY faster than any evo.
now imagine how fast it is for me now, with my Quantum froyo...
Click to expand...
Click to collapse
I agree, that's why I bought the Epic in the first place. I just wish I could ADB into it with my Windows 7 machine that I'm using 99% of the time. The posters in this thread don't seem to understand that I like the phone, I just don't like the way it interacts with my computer.
Maybe their installation of 64 bit windows 7 can ADB fine, but that doesn't help me any. I wish I could get some help instead of being called an idiot. From my experiences, these Samsung drivers are worthless.
Phone good, drivers bad.
my intention was not to insult, just to convince you to keep it, and try to find the solution, which is what youre doing. wish i could help
ericizzy1 said:
my intention was not to insult, just to convince you to keep it, and try to find the solution, which is what youre doing. wish i could help
Click to expand...
Click to collapse
Haha, not to worry, you've been one of the most helpful in this thread. It's nice to be reaffirmed that my choice to go with a Samsung phone for the first time wasn't a mistake.
I'm just put off by all of the suggestions in this thread that the problem lies between the chair and keyboard instead of anything helpful about how to get these absurd drivers ironed out. Never had problems with HTC drivers, just sayin'.
You can get drivers to install better with one of 2 ways:
1) Use device manager to go to manually load the drivers in the 16_Shrewberry folder
2) Install Kies..even if it doesnt work it seems to install the drivers better
-------------
also if your using a desktop..back ports are more efficient.
gTen said:
You can get drivers to install better with one of 2 ways:
1) Use device manager to go to manually load the drivers in the 16_Shrewberry folder
2) Install Kies..even if it doesnt work it seems to install the drivers better
-------------
also if your using a desktop..back ports are more efficient.
Click to expand...
Click to collapse
That's what I'm talking about. Awesome information, I'll do some driver wiping and see how these methods work out from a clean slate. Thanks a lot.
SamsungEpic86 said:
I had the same problem with my phone not showing up on the computer, i know this may sound stupid but it works. I have 2 usb ports in the front of my computer and thats what i tired using for the phone it wouldn't work, so i plugged it in the back of the computer and now it works fine shows up everytime on my computer.. So i just bought a extra usb cord off ebay and have it constantly plugged in the back of the computer.
Click to expand...
Click to collapse
Good point! My 2 front USB ports are useless for connecting my Epic as well.
I installed the Samsung drivers for win 7 x64 from Sammys site and no driver issues here. Maybe try uninstalling the drivers you already installed and start from scratch?
bullet2300 said:
I installed the Samsung drivers for win 7 x64 from Sammys site and no driver issues here. Maybe try uninstalling the drivers you already installed and start from scratch?
Click to expand...
Click to collapse
I just got that step done through the driver program that Samsung installed, next I'm going to delete every trace in the Device Manager and try again with gTen's new methods.
Hello!,
After trying a numerous NAND roms for my HD2, on every of them the accelerometer is not working. But flashing back to winmo everything is OK and accelerometer works.
Problems having : No screen rotation, no games work which need accelerometer, no bubble meters and so on.
I saw lots of threads here, but none of them were answered. Also some fixes out there from january, but its is said that new kernels include that fix.. Being really desperate about the accelerometer to start working tryed everything , all those fixes - none of them worked.
I really would appreciate if somebody would say a 100% answer if they had same problem and is it for EVERYONE that you are chilling around without accelerometer with NAND roms?
Or, a nicely explained , or some new fixes around there, to fix that..?
I have European HD2, Bought in Estonia. 2.15 radio, and RAFDroid build atm 4.02
Before teyed all cyagenmod build from MDJ, imilka builds, Coredroid, etc.
Waiting for a adequate anwer!, and Thank you in advance!
Daniil.
No pb for me with each Nand i tested. (prj Clean Desire, typhoon, Hyperdroid)
i had this to on my sd build i used to have but when i went to NAND everything was fixed
maybe you can try to recalibrate it in android?
Auralol said:
Hello!,
After trying a numerous NAND roms for my HD2, on every of them the accelerometer is not working. But flashing back to winmo everything is OK and accelerometer works.
Problems having : No screen rotation, no games work which need accelerometer, no bubble meters and so on.
I saw lots of threads here, but none of them were answered. Also some fixes out there from january, but its is said that new kernels include that fix.. Being really desperate about the accelerometer to start working tryed everything , all those fixes - none of them worked.
I really would appreciate if somebody would say a 100% answer if they had same problem and is it for EVERYONE that you are chilling around without accelerometer with NAND roms?
Or, a nicely explained , or some new fixes around there, to fix that..?
I have European HD2, Bought in Estonia. 2.15 radio, and RAFDroid build atm 4.02
Before teyed all cyagenmod build from MDJ, imilka builds, Coredroid, etc.
Waiting for a adequate anwer!, and Thank you in advance!
Daniil.
Click to expand...
Click to collapse
Usually d G-Sensor/Accelerometer has been pre-calibrated while cooking d android build...I've never had such a problem on SD, NAND or RAM builds....Perform a Task 29 on ur device and try flashing the build contained in my signature....CMY's work has always been great...
Done task29, done recalibration in android, everything... same. There is numerous people having the same prob , as i have seen from questions subforum.
Auralol said:
Done task29, done recalibration in android, everything... same. There is numerous people having the same prob , as i have seen from questions subforum.
Click to expand...
Click to collapse
Hmmm...Since it works on WinMo, try recalibrating it there and then run an android sd build (i just tried "Desire_DL" series and all was ok....on d other hand, have u tried d NAND build in my sig?
I have tryed everything, including your builds in the signature.... Nothing helps
Help!
Try the post that is in my sig, there is alot of info in there that might be of use to you. What definitely controls the G-Sensor is the bma150_usr file. If nothing in my post helps you at all, then I am unable to help you further since I dont have a Eu HD2. But I still believe that there might have been a revision which might explain your troubles as well as some other people.
Tryed that also, no help at all.
Auralol said:
Tryed that also, no help at all.
Click to expand...
Click to collapse
Hmm, dats quite a dilemma....I tk it u can't return n request for another device seeing as u got it 4rom Estonia...or can u?
Android is not supposed to run on HD2 anyways, so why should i have an opportunity to return my device for another one?
Auralol said:
Android is not supposed to run on HD2 anyways, so why should i have an opportunity to return my device for another one?
Click to expand...
Click to collapse
True it wasn't but IT IS...I and several others are proof it works beautifully on the HD2, even better than some native android devices...I offered a suggestion n its ur call 2 tk it or leave it...I on d other hand, love my current android build on my HD2.
Have u tried this workaround?
P.S. Oh yeah, and my accelerometer/g-sensor works perfectly in apps n games.
I mean, yeah it is working, but... not working for my device. And the point was that i can't take it to my local shop for a return, as the g-sensor works for the WinMo, and they will say that its your fault that it isn't working in android. Yeah i know that accelerometer works on androids on the Tmobile HD2-s
And yeah, i have tryed
Different type of g-sensor
I understand that some newer builds of the HD2 have a different type of g-sensor. I have x4 HD2's. 3 are working perfectly with HyperDroid CM7 cheerful cheetah. The forth is used by my company co-director which I recently tried to move over to the HyperDroid CM7 cheerful cheetah from WM6.5. This is when I came across the problem. Very annoying. The fact is that this device went back to HTC to repair/replace a cracked screen (I dropped the device last June). I suspect they gave me a reconditioned or replacement unit with the "updated" sensor.
Please advise me if there are any new developments. I can confirm that the HD2 (with the working g-sensor) has incredible battery life and is only my no.2 device because of the 8mp camera on the DesireHD.
Regards,
Jay
[email protected] said:
I understand that some newer builds of the HD2 have a different type of g-sensor. I have x4 HD2's. 3 are working perfectly with HyperDroid CM7 cheerful cheetah. The forth is used by my company co-director which I recently tried to move over to the HyperDroid CM7 cheerful cheetah from WM6.5. This is when I came across the problem. Very annoying. The fact is that this device went back to HTC to repair/replace a cracked screen (I dropped the device last June). I suspect they gave me a reconditioned or replacement unit with the "updated" sensor.
Please advise me if there are any new developments. I can confirm that the HD2 (with the working g-sensor) has incredible battery life and is only my no.2 device because of the 8mp camera on the DesireHD.
Regards,
Jay
Click to expand...
Click to collapse
Hi Jay, I've got a similar problem.
Actually, I've got (or had) an EU model, and my screen cracked, so it has been out for repair. So both descriptions in this post (yours and Auralol's) fit my problem. I have been looking for a fix for a while now, did you find anything?
I would love it to work, it really is the only thing that doesn't. If this is fixed, my HD2 would be perfect and irreplaceable.
If you find anything that helps, keep me posted?
Kind regards,
Bas
Hey Bas,
I contacted vfuk & simply said that there was a problem with the g-sensor on my HD2... The helpful telephone attendant asked me to remove the battery, memory and sim cards and a replacement device would be with me the next day. The following day the courier took the troubled HD2 and handed me a new Desire HD albeit without the antenna and battery covers. I have a spare battery and ordered the covers from expansys.
I did explain to vfuk what happened - they said I wasn't to worry.
At the time of writing I now have x4 dhd's and a working HD2 with HyperDroid which I am going to give to a pal to lure him away from Nokia...
I now have no way of helping you further. Sorry bout that.
Best,
Jay
[email protected] said:
Hey Bas,
I contacted vfuk & simply said that there was a problem with the g-sensor on my HD2... The helpful telephone attendant asked me to remove the battery, memory and sim cards and a replacement device would be with me the next day. The following day the courier took the troubled HD2 and handed me a new Desire HD albeit without the antenna and battery covers. I have a spare battery and ordered the covers from expansys.
I did explain to vfuk what happened - they said I wasn't to worry.
At the time of writing I now have x4 dhd's and a working HD2 with HyperDroid which I am going to give to a pal to lure him away from Nokia...
I now have no way of helping you further. Sorry bout that.
Best,
Jay
Click to expand...
Click to collapse
Heyy Jay,
Thanks for the reply. So, you kind of worked around the issue Sounds like great customer service. Too bad my provider does not work like that.
Just being curious if you had the same problem as I am facing now, did you try to retrieve / read data from the sensor (i.e. with "sensor debug")? I tried yesterday, didn't get any data at all. Probably means Android doesn't see the sensor, or it is indeed a different sensor and therefore needs other drivers.
I just downloaded some e-books about android and java, just to see how it works with hardware. Maybe it is possible to implement my 'own' drivers in a ROM to make sure the sensor can be detected at least. I guess it is going to be my pet project to find a solution, and when I do, I'll probably try to get it posted on xda. But then again, my programming skills are minimal at this point (just some Basic, html and Step 7), so it might take me a while...
Anyway, thanks for the reply. Too bad your solution does not work for me (I would not mind that either).
Kind regards,
Bas
Bas2ct said:
Heyy Jay,
Thanks for the reply. So, you kind of worked around the issue Sounds like great customer service. Too bad my provider does not work like that.
Just being curious if you had the same problem as I am facing now, did you try to retrieve / read data from the sensor (i.e. with "sensor debug")? I tried yesterday, didn't get any data at all. Probably means Android doesn't see the sensor, or it is indeed a different sensor and therefore needs other drivers.
I just downloaded some e-books about android and java, just to see how it works with hardware. Maybe it is possible to implement my 'own' drivers in a ROM to make sure the sensor can be detected at least. I guess it is going to be my pet project to find a solution, and when I do, I'll probably try to get it posted on xda. But then again, my programming skills are minimal at this point (just some Basic, html and Step 7), so it might take me a while...
Anyway, thanks for the reply. Too bad your solution does not work for me (I would not mind that either).
Kind regards,
Bas
Click to expand...
Click to collapse
Hi,
I'm having the same issue as you and was wondering if you had made any progress or if there is anything I could help you with although my programming knowledge is probably more limited than yours. Anyway this issue seriously needs to be looked at! :'(
Still no fix?
Hello, I know it is old thread, but I see there are more people than only me having this issue. Same thing happens to me. Accelerometer isnt working on Android, but it works great on WinMo. I tried a lot of ROMs, "fixes", but nothing helped at all. I used apps like Sensor debug, and sensor list, seems that they dont see my g sensor at all, like someone said before. As I know, g sensor is connected with bma150_usr file, but I used my Root Explorer to search for that file and there is no such a file at all. Shouldnt it come to my device with other ROM files? Yes, I tried to put it where it should be, but the same s**t again... Is there anyone who solved this thing? Because I dont see any solutions mentioned in the whole xda forum.
Looking forward for answers which REALLY helps.
Hi,
I have this same problem, My g-sensor didin't work on AMeriCan Android.
I was reading a topic http://forum.xda-developers.com/showthread.php?t=902129, and my question for this: How I can delete files
Before installing the file above, go to System/Bin and delete the bma150_usr, then navigate to Data/Misc, and delete the following files:
AK8973Prms.txt
AK8973.Prms.txt.tmp (If there)
bma150_usr.txt (If there)
After navigate to the above file and add it to System/BIN and then your calibrating will function correctly and adjust the values properly.
Click to expand...
Click to collapse
Hey xda, i just got this used Mytouch 4G and rooted and flashed, etc... but know i notice that my wifi does not turn on at all, it just says turning on..... but it never does, when i was on 2.3.4 it would turn on but would say cannot scan. is there any fix for this? is the wifi just dead? throw the phone away?
symbiiote said:
Hey xda, i just got this used Mytouch 4G and rooted and flashed, etc... but know i notice that my wifi does not turn on at all, it just says turning on..... but it never does, when i was on 2.3.4 it would turn on but would say cannot scan. is there any fix for this? is the wifi just dead? throw the phone away?
Click to expand...
Click to collapse
What ROM are you using. Sometimes its just a kernel problem, I've been testing different kernels with different ROMS, and some of them wont let you turn on wifi. Try a different ROM then.
Hey thanks for the replie, ive used pac rom 4.2.2 and cfx rom 4.2.2
symbiiote said:
Hey thanks for the replie, ive used pac rom 4.2.2 and cfx rom 4.2.2
Click to expand...
Click to collapse
Try a stable-ish rom. Like Dark Unicorn Resurrected --->http://forum.xda-developers.com/showthread.php?t=1716558 (Second Post). Or Synthetic.Nightmare's AOSPX -----> http://forum.xda-developers.com/showthread.php?t=1684835
If that doesn't work try going to a stable GB rom (Like CyanogenMod 7.2.0) If that doesn't work then just donate your phone to someone that could use the parts
I tried cm7 and no go, click on turn wifi on and it reboots... x(
Sent from my A500 using Tapatalk HD
Awwwww man. That sucks. If it won't work on cm7. Then try a GB sense rom. If it doesn't work there. Revert to stock all over again. If it won't work there. Then your screwed man. Hope it works though.
Sent from my myTouch 4g using xda app-developers app
N_otori0us_ said:
What ROM are you using. Sometimes its just a kernel problem, I've been testing different kernels with different ROMS, and some of them wont let you turn on wifi. Try a different ROM then.
Click to expand...
Click to collapse
symbiiote said:
Hey xda, i just got this used Mytouch 4G and rooted and flashed, etc... but know i notice that my wifi does not turn on at all, it just says turning on..... but it never does, when i was on 2.3.4 it would turn on but would say cannot scan. is there any fix for this? is the wifi just dead? throw the phone away?
Click to expand...
Click to collapse
N_otori0us_ said:
Awwwww man. That sucks. If it won't work on cm7. Then try a GB sense rom. If it doesn't work there. Revert to stock all over again. If it won't work there. Then your screwed man. Hope it works though.
Sent from my myTouch 4g using xda app-developers app
Click to expand...
Click to collapse
It's not an issue with the ROM, it's an issue stemming from the kernel modules. You'll see this most commonly when a kernel and the subsequent modules weren't compiled together or the modules were compiled against a different kernel version or configuration. If it's always done this out of the box, however, you may have a problem on your hands but that doesn't necessarily mean it isn't still software related; it just makes that likelihood far less.. likely. You said it was used, so it's possible the previous owner screwed up the kernel modules and the kernel. It's not a hard issue to test for, you just need a known working kernel with known working modules. If you'd like, I'll build you a kernel that's mostly stock just so you can eliminate a majority of the suspects but I am only prepared to build kernels for Jellybean based ROMs, which isn't a big deal because most of the ROMs are already 4.2.2. LiquidSmooth is also a good ROM to try, it worked very well off the jump for me. In the event that you find that you still have an issue, certainly don't throw it in the trash. I happen to need a MT4G because my camera button, volume rocker, and the connector on the side with the three contacts that I assume is some sort of dock connector err.. fell off.. I'd advise against disassembling it unless you pay very close attention to the instructions because those three items are attached to the outer casing and if you aren't careful when you remove it then I'll have to make space in the boat because you'll be in the same one I am, haha. If you have any other questions, by all means ask and if I'm incorrect in any of my statements then someone please correct me so that I don't go around giving out bad information out of ignorance, but I'm fairly confident in my statements. You'll find the modules in /system/lib/modules if you care to look but just because it's empty doesn't mean that they aren't simply compiled directly into the kernel as there isn't much reason not to unless it's something that not everyone would use or someone might see fit to change. The firmware for the WLAN, however, will be in /system/firmware/ no matter what and will be something along the lines of bcmdhd.bin or bcm4329.bin
zygh0st said:
It's not an issue with the ROM, it's an issue stemming from the kernel modules. You'll see this most commonly when a kernel and the subsequent modules weren't compiled together or the modules were compiled against a different kernel version or configuration. If it's always done this out of the box, however, you may have a problem on your hands but that doesn't necessarily mean it isn't still software related; it just makes that likelihood far less.. likely. You said it was used, so it's possible the previous owner screwed up the kernel modules and the kernel. It's not a hard issue to test for, you just need a known working kernel with known working modules. If you'd like, I'll build you a kernel that's mostly stock just so you can eliminate a majority of the suspects but I am only prepared to build kernels for Jellybean based ROMs, which isn't a big deal because most of the ROMs are already 4.2.2. LiquidSmooth is also a good ROM to try, it worked very well off the jump for me. In the event that you find that you still have an issue, certainly don't throw it in the trash. I happen to need a MT4G because my camera button, volume rocker, and the connector on the side with the three contacts that I assume is some sort of dock connector err.. fell off.. I'd advise against disassembling it unless you pay very close attention to the instructions because those three items are attached to the outer casing and if you aren't careful when you remove it then I'll have to make space in the boat because you'll be in the same one I am, haha. If you have any other questions, by all means ask and if I'm incorrect in any of my statements then someone please correct me so that I don't go around giving out bad information out of ignorance, but I'm fairly confident in my statements. You'll find the modules in /system/lib/modules if you care to look but just because it's empty doesn't mean that they aren't simply compiled directly into the kernel as there isn't much reason not to unless it's something that not everyone would use or someone might see fit to change. The firmware for the WLAN, however, will be in /system/firmware/ no matter what and will be something along the lines of bcmdhd.bin or bcm4329.bin
Click to expand...
Click to collapse
Wow, thanks for the detailed reply. ill defiantly try this out, ill get back to you. [Update] ive checked and theres no firmware folder in system, and in system/lib/modules there is a bcm4329.ko file. (im on CM7)
Are you interested in a trade? I cant use phone with no Wi-Fi
Sent from my A500 using Tapatalk HD
Fixed my wifi!
symbiiote said:
Are you interested in a trade? I cant use phone with no Wi-Fi
Sent from my A500 using Tapatalk HD
Click to expand...
Click to collapse
Just FYI, I was in the same boat. I bought a used and heavily abused Mytouch 4g just to pull the motherboard and use it to fix my wife's hard bricked (no power whatsover) mytouch. It worked fine for a day or so, then started having random reboots and wifi failure (i.e. on the stock ROM it would cycle on & off repeatedly, then reboot, and on CM7 it would just not turn on, or occasionally show 'error' if I forced the driver to load.
I tried everything: rooting and installing multiple ROMs, multiple kernels, flashing to stock unrooted, flashing to stock Froyo unrooted, and it never resolved. In the dmesg I would get an error "dhsdsio_probe_attach: si_attach failed!" every time I tried to enable wifi. I even tried different radios, not really expecting much, but just to cover my bases. I took the phone apart multiple times looking for loose cables, damaged ribbons, etc, but never found anything, although occasionally wifi would return for a few hours, then disappear again. Often it came back right after flashing a new rom or factory reset, but even without installing any apps, it would eventually fail, so it wasn't an app issue.
Then... I discovered another thread where people with the Motorola Atrix discovered that a well placed piece of plastic would resolve their failing wifi by applying pressure in just the right spot - most likely due to a loose or failing solder connection. I dug around online and found a photo showing exactly where the Broadcom 4329 chip is in our phones (it is right behind the microphone on the underside of the motherboard), and discovered that by squeezing hard with one finger just to the left of the trackpad, and the other directly behind on the back of the phone, I could get wifi to enable and scan. Letting go would drop the scan. Give that a shot and see if it makes a difference. If so, read on...
I found that people with iPhones with a failed Broadcom 4329 module (same chip) had had some success in reflowing the motherboard. Not having any expertise in that area, I was surprised to find that a common solution was to use an oven to heat the motherboard up in order to soften the solder and do a poor-man's "reflow". I can't post links yet, but if you google "iphone WiFi Repair: Oven Fix" you'll find a great video describing how to to it and why it works.
So I went for it. I took it apart one last time (plenty of take apart videos online to show how this is done), pulled out just the motherboard, stripped everything off that wasn't permanently attached (including removing/unlatching the metal covers on front & back & all ribbons), got a cookie sheet and some aluminum foil, put the foil loosely around the rest of the motherboard (shiny side out) and ripped an opening just around the chip. Then raised the mother board off of the cookie sheet with little foil balls (per instructions online for laptop reflowing) and baked at 360 for 8 minutes, shutting off the heat and cracking the oven door slightly for 20 minutes to cool it slowly, then open all the way for another 20 minutes, out, reassembled, and now I have a working wifi chip.
Crazy, yes, but if you are about to toss the phone, it might be worth a shot as a last resort. Not a 100% success rate when you search online for people trying this, some people have destroyed their phones, but it worked for me!
Keep in mind, I just did this about 2 hours ago, so there's still the possibility it was a short-lived solution. I will try to check back in here in a week or two to confirm that it 'took'.
UPDATE 1: One day later, and zero reboots, 100% reliable wifi. It has never been so stable.
zygh0st said:
It's not an issue with the ROM, it's an issue stemming from the kernel modules. You'll see this most commonly when a kernel and the subsequent modules weren't compiled together or the modules were compiled against a different kernel version or configuration. If it's always done this out of the box, however, you may have a problem on your hands but that doesn't necessarily mean it isn't still software related; it just makes that likelihood far less.. likely. You said it was used, so it's possible the previous owner screwed up the kernel modules and the kernel. It's not a hard issue to test for, you just need a known working kernel with known working modules. If you'd like, I'll build you a kernel that's mostly stock just so you can eliminate a majority of the suspects but I am only prepared to build kernels for Jellybean based ROMs, which isn't a big deal because most of the ROMs are already 4.2.2. LiquidSmooth is also a good ROM to try, it worked very well off the jump for me. In the event that you find that you still have an issue, certainly don't throw it in the trash. I happen to need a MT4G because my camera button, volume rocker, and the connector on the side with the three contacts that I assume is some sort of dock connector err.. fell off.. I'd advise against disassembling it unless you pay very close attention to the instructions because those three items are attached to the outer casing and if you aren't careful when you remove it then I'll have to make space in the boat because you'll be in the same one I am, haha. If you have any other questions, by all means ask and if I'm incorrect in any of my statements then someone please correct me so that I don't go around giving out bad information out of ignorance, but I'm fairly confident in my statements. You'll find the modules in /system/lib/modules if you care to look but just because it's empty doesn't mean that they aren't simply compiled directly into the kernel as there isn't much reason not to unless it's something that not everyone would use or someone might see fit to change. The firmware for the WLAN, however, will be in /system/firmware/ no matter what and will be something along the lines of bcmdhd.bin or bcm4329.bin
Click to expand...
Click to collapse
I think WiFi should have worked on cyanogen7 or a sense Rom....
That's why I figured it was a hardware problems.
Also can you compile kernels for me? I don't know How to properly. :'(
Sent from my HTC Glacier
A little more info in case it helps anyone diagnose a different issue, below were some handy-dandy commands I used to check the driver situation:
Try to turn on wifi (obviously it will fail)
Then in terminal emulator (download one from the play store if not installed), type
$ lsmod
if nothing is returned, the driver isn't loaded. If you get "bcm4329" listed as 'live', then your driver is loaded. Its probably not a driver compatibility problem (not 100% on that, since I'm new to all of this).
If your driver isn't loading, it still might not be a bad driver. It might just have been because the chip wasn't detected. Type the following to give permissions and manually load the bcm4329 driver:
$ su
# mount -o remount,rw /dev/block/mtdblock3 /system
# insmod /system/lib/modules/bcm4329.ko
if it returns an error/fail, you've got the wrong bcm4329.ko file/driver installed or maybe a corrupted file. Try reflashing the ROM, or replacing the bcm4329.ko file with one that is compatible with the ROM/kernel you are using.
If not, then
# exit
then check again with
$ lsmod
If the driver shows up now, then at least you know it can load. Then try connecting again. If it still doesn't connect, this might help the process of elimination.
go back to terminal emulator immediately after trying to connect
type in dmesg
scroll up a little ways and look for the a series of phrases 'wifi_set_power: 1', etc. If you see it trying to connect, then a few lines down, see the error "dhdsdio_probe_attach: si_attach failed!" shortly after it loads the Dongle Host Driver, then it isn't finding the chip. You probably have the same loose connection problem I had (above), and may have to do something physically to your phone if you want wifi back. I'd try the 'squeeze test' first to confirm before taking it apart.
I hope that is helpful. I spent way too much time figuring this out, and would have loved to have found this info somewhere in one spot online.
its def a kernel problem because i rely on wifi everyday since i tether to my pc and once i tried a kernel that should fix headphone heat up. didnt know if it did but it broke the wifi. would not switch on so i switch back to a next kernel n wifi works. roms like carbon, cm10.2 everlov gives kernel with wifi working. hope this help if someone end up in this boat again
http://forum.xda-developers.com/showpost.php?p=41652708&postcount=3
Just a quick link to N_otori0us_'s posts on kernels if you wanted to try other ones.
tonyMEGAphone said:
http://forum.xda-developers.com/showpost.php?p=41652708&postcount=3
Just a quick link to N_otori0us_'s posts on kernels if you wanted to try other ones.
Click to expand...
Click to collapse
There's more kernels for Gingerbread in the second post too. The one's in the 3rd post were just common things I've seen people asking for,
my friend just gave me a new motherboard, works fine now.
followup on the oven solution
After a week - wifi still working, but not without some intervention. It crapped out again after 2 days, and I re-baked it (the first time I chickened out and didn't keep it at 385 for the full 8 minutes). It has stayed fairly consistent, but started acting up again over the weekend, so I grabbed a tiny square of some sort of soft compressable insulation material from a tablet I was fixing, and placed it right over the broadcom chip to keep it compressed and applying a little pressure. So far that has held and worked well.
I have a feeling its a matter of time before this eventually fails again, too. I don't think there is anything that can be done to permanently fix lead-free solder paste that has started to develop micro 'whiskers', according to what I've dug up online. Reflowing and pressure seem to work temporarily to re-establish a connection. If I knew how to remove the solder and re-apply a solder paste with some lead content, I'd do it. That would probably be a permanent fix. That or a new motherboard ala simbiiote.
[UPDATE 2] Killed it. Apparently re-baking every few days at slightly hotter temperatures eventually will fry your motherboard. Don't go past 400 degrees, and use an oven thermometer to get an accurate idea of what the real temp is. Now back hunting for broken ebay phones to replace the motherboard. Oh well, it was good while it lasted.