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.
Related
Hi All
Was using SD versions of Android in my HD2 which worked quite well .....decided to make the jump to NAND recently but I'm having a problem with phone calls.
When I make a call out, everything works fine, but when I hang up on the call, the hard buttons on the bottom of the phone all light up but the screen doesn't turn back on.... Only way to get the screen back on is to plug in the USB cable or power adapter or pull the battery and do a reboot!
Have tried a couple of different builds from different chefs and a couple of Radios just in case.
At the moment I've got the following on it:
Radio is 2.12.50.02_2
Android version is 2.2.1
Build is DL DesireZ v3.4 Final (but this problem also happens with CleanDROID V1.31)
Also tried an MTTY Task 29, reload of MAGLDR then re-flash of the NAND in case traces of my previous ROM were still around but that hasn't helped either.
Any ideas?
I seen many threads about same situation. Actually i itself use daily gpc hd2 gingerbread v1.5 with same problem. Sometime help back button (when call ended not at me). Sometime just more light to proximity (or it light) sensor (when inside and put phone with face to some light). Outside i just must turn phone with face to sun or good light then screen wakes up.
I tested many many nand roms. All have same problem.
Tested win 6.5, win 7 and sd version, they works well. That gives confirmation that my proximity (or it light) sensor works well. And finally that something wrong with nand.
Here was discussion that MAGLDR does that. NO.
I started run over net and find solution. Here seems no help for this right now. Maybe just problem ignored because cookers itself dont have this and cant do anything. If you dont have problem then how you can fix it.
On web i found some discussion about kernel problem or smth about this proximity sensor. I cant find it right now again. There was talking about this problem, but no solution.
I thinked about open new thread and invite kernel chiefs to discussion to solve this problem. But today i find your ask. I opened for any test and help that i can give. I dont be afraid to lose my phone if something must go wrong. Phone is just piece of electronic and you can replace parts. But knowledge and experience you cant buy.
Any ideas how to resolve this little bad thing?
Thanks for the reply.
Yes it's a real problem but mine won't wake up no matter how much light.
The only way I can get it to wake up is to plug it in to power, then the screen wakes up.
Is that the same as yours?
I i remember it right i was suprised once too if this happened. I just put my "again dead" phone to charging and its waked up.
If screen is dead and same time connected to pc (i use for managing inside phone androidcommander) then moving over dirs wake screen back too.
But lets look how long my nerves will be good. Today i thinked to move back win 6.5 and sell this bastard.
No don't sell we need to resolve! I'm hoping someone will look at this thread and help us figure out why this is happening. I can't believe we are the only 2 people who have this issue.
Anyone else have any ideas as to why this is happening?
This issue was also on sd versions. So I see nand has not fixxed it. I am running MDJ HD 4.6 and have this issue. Sometimes the light sensor works properly and other times it goes to black screen and gets stuck.
I read somewhere that it might be the hardware itself. Saw a video on youtube also. Seems the european T8585 and telstra T9193 might have poor light sensors. The T-mobile light sensor supposedly does not have this problem.
So I am guessing anyone with this problem does not have the T-mobile USA version??
It could just be drivers too. It is a pain and sometimes I wish I could just disable the light sensor.
Also NAND roms are no better than sd versions as far as bugs. If the sd version has the bugs then so will the NAND version. The build is just installed at a different location.
Yes good point.... the bug will be replicated as it's just where the OS is stored that's different.
I'm thinking it's the hardware as I have this problem on WinMo6.5 too and I have tried various WinMo roms but had the same problem.
Mine is a UK HD2 supplied by O2. Wish there was a fix for it :-( It's a real problem.
PS I ran PhireMOD's Skinny EVO SD Android for a while and didn't have as much as a problem as I have had with the 2 NAND roms I've tried..... if that's any clue? At least with that rom I was able to make calls and hang up and still get the screen back after I hung up (except for the screen going white and washed out which could only be resolved by a reboot). There was still the problem with the screen being on all the time during a call or the screen being black and not coming back on during a call though.
I have these sort of problems too. It's really annoying when you're in a phonecall and you take the phone away from your ear and it takes a few secs to turn on. Also when I'm unlocking it.
Sent from my HTC HD2 using XDA App
At least yours comes back on lol mine stays off for ages and ages and sometimes doesn't come back on at all!
Noticed that if I shine a torch into the proximity sensor that's the only way I can get the thing to turn back on :-( Also noticed the 2 little holes where the prox sensor sits appear dirty/cloudy... not sure how that happened.
I wonder if the prox sensor is busted or if it's just dirty or something? Going to get a T5 Torx and take my phone apart to find out if it's something I can resolve.
Well i had this with rafpignas kernel...i changed to markinuX today and tested it with over 10 calls and it works flawlessly right now
Hmm, are you sure g9650? Seems my guess about kernel was then true. I use gpc pure gingerbread 1.6 with gpc itself made kernel. I go right now replace kernel and test. Results tomorrow.
Took the phone apart yesterday night and uncovered the proximity sensor. Even out of the case it needs a torch/flashlight to shine on it to bring the screen back on :-( I honestly think the proximity sensor hardware isn't working anymore.
I'll try the kernal you suggested though just in case that's what's causing the problem.
Datas0ft let me know if it works for you?
Latz, actually i taked to test markinus extra clean 1.7.1 (right now on it itype this). Had one call before and no changes.
Also i stuck on taking out kernel at this version. Low knowledge. Dont find any help yet on xda. I work on it. If you have hints dont hestitate say.
Sent from my HTC HD2 using XDA App
:-( I was hoping we found a miracle cure! Ok let me flash mine tonight and try it to see if mine behaves any different. Will post back with results... let me know fi anything changes with your phone datas0ft.
q9650 said:
Well i had this with rafpignas kernel...i changed to markinuX today and tested it with over 10 calls and it works flawlessly right now
Click to expand...
Click to collapse
Can anyone upload MarkinuX Kernel please? Thanks
Ok. Searched forum. Finded way how to get kernel at some nand. Got MarkinuX kernel and now test. Test will be during whole day tomorrow on different conditions.
For kernel extract and install is this thread very good. Helped and teached me.
marcosxd i taked needed files for you and attached.
datas0ft said:
Ok. Searched forum. Finded way how to get kernel at some nand. Got MarkinuX kernel and now test. Test will be during whole day tomorrow on different conditions.
For kernel extract and install is this thread very good. Helped and teached me.
marcosxd i taked needed files for you and attached.
Click to expand...
Click to collapse
Thanks, I just finished downloading the whole Markinus rom to extract kernel haha but you saved me... will test and report, thanks
datas0ft said:
Ok. Searched forum. Finded way how to get kernel at some nand. Got MarkinuX kernel and now test. Test will be during whole day tomorrow on different conditions.
For kernel extract and install is this thread very good. Helped and teached me.
marcosxd i taked needed files for you and attached.
Click to expand...
Click to collapse
Quick question, the zip file you gave me only has two .ko files and zImage while the original rafdroid kernel has like 5 .ko files... what should I do? copy raf's kernel .ko files missing into markinux ones?
Or just pack the zip file using two .ko files? Thanks
I cant ansver. Dont have much knowledge on this. I followed instructions. This taked to me these three files. I installed these.
I finded some problems right now (wifi and gps dont work and my 3g too). This may not happen at kernel side. I have made some changes on rom side. I go replace whole rom and then again kernel. Then i go make final decisions.
I'm having the same problems, you two are not the only ones. This has been really frustrating me lately, and I thought it might have been a problem for only me because I just had the screen replaced. It worked fine in winmo 6.5, now in NAND I'm having some issues. I text a lot more than I actually call, however so it's not that big of a problem for me right now
So basically i Started Installing roms for like 4 months now, i started the rooting process using this guy's "Mackster248" method, witch was the gfree shown here: youtube.com/watch?v=c4B4y0CQUDo[/url]. I never tried anything more complicated than this aside from installing the genius button with required the need to use button shortcut app.
I've tried a few roms like VU 1.29. and a Vdoubleshoot one witch i hated. I loved vu 1.29.0 but i felt something was missing, so i tried the DARKSIDE Runny v2.1.0 first but found out that the voice recognition in the genius did not work, so i updated to 2.2.0. witch did work with the easy genius fix....Sooo I Loved it & decided to stay with it for good regardless of the ffc issue. So after reinstalling all my apps again i noticed that my power button would not lock and turn off the screen, I thought it was the button cause i had a problem with it being hard and sticking, so on the lock screen i "pulled the battery" yes after now reading in some forums I'm seeing that's a Big NO NO!
After trying to power on i get a Black screen of death where the black light turns on when pressing on the home screen only when the charger is plugged in so yes i am aware that I'm bricked but my question is why? This also happened to my friends "UNROOTED" mytouch 4g, when he was downloading something from the market the froze on him so i pulled the battery out and upon rebooting it was stuck on a line of androids. When sent to HTC they said it was the emmc chip.
So a some questions i have are, 1: Do these phone brick regardless of rooted or not? 2nd: Is pulling the battery out really so dangerous? if so what to do in my 2 scenarios? After i realized my phone was bricked i was thinking i should of used clockward mod before turning it off, but would that had made a difference? Ohh well i already know that HTC repairs rooted phones based on whats been posted in these forums so I'm not worried and i have already my shipped my phone...hopefully it wont take too long to replace that eMMc. Thanks for reading me out!
Maybe change the title of your thread... Your phone was bricked because you installed the Rom...
How r people getting the FFC to work with stock camera
wanabdev said:
So basically i Started Installing roms for like 4 months now, i started the rooting process using this guy's "Mackster248" method, witch was the gfree shown here: youtube.com/watch?v=c4B4y0CQUDo[/url]. I never tried anything more complicated than this aside from installing the genius button with required the need to use button shortcut app.
I've tried a few roms like VU 1.29. and a Vdoubleshoot one witch i hated. I loved vu 1.29.0 but i felt something was missing, so i tried the DARKSIDE Runny v2.1.0 first but found out that the voice recognition in the genius did not work, so i updated to 2.2.0. witch did work with the easy genius fix....Sooo I Loved it & decided to stay with it for good regardless of the ffc issue. So after reinstalling all my apps again i noticed that my power button would not lock and turn off the screen, I thought it was the button cause i had a problem with it being hard and sticking, so on the lock screen i "pulled the battery" yes after now reading in some forums I'm seeing that's a Big NO NO!
After trying to power on i get a Black screen of death where the black light turns on when pressing on the home screen only when the charger is plugged in so yes i am aware that I'm bricked but my question is why? This also happened to my friends "UNROOTED" mytouch 4g, when he was downloading something from the market the froze on him so i pulled the battery out and upon rebooting it was stuck on a line of androids. When sent to HTC they said it was the emmc chip.
So a some questions i have are, 1: Do these phone brick regardless of rooted or not? 2nd: Is pulling the battery out really so dangerous? if so what to do in my 2 scenarios? After i realized my phone was bricked i was thinking i should of used clockward mod before turning it off, but would that had made a difference? Ohh well i already know that HTC repairs rooted phones based on whats been posted in these forums so I'm not worried and i have already my shipped my phone...hopefully it wont take too long to replace that eMMc. Thanks for reading me out!
Click to expand...
Click to collapse
1. I have yet to hear of a non-rooted phone bricking because of the bad eMMc chip, only after you root it does the chip start acting funny. could have been a possibility that you had the bad eMMc, did you check to see before taking the plunge and rooting your phone?(guessing not lol )
2. pulling the battery isnt as dangerous as everyone says it is. its only dangerous if you pull it while trying to flash the stock PD15IMG to return to stock, or during the phones booting process where its loading everything up. Ive pulled my battery plenty of times, but never in those situations.
Maybe hope
Out of curiosity are you able to get into the bootloader to run fastboot at all by holding down the power and the down volume on your phone? If so you could probably flash clockworkmod onto your phone again through fastboot and reflash a new rom.
If you're able to do this you could save your phone
macblaxter said:
Out of curiosity are you able to get into the bootloader to run fastboot at all by holding down the power and the down volume on your phone? If so you could probably flash clockworkmod onto your phone again through fastboot and reflash a new rom.
If you're able to do this you could save your phone
Click to expand...
Click to collapse
DING DING DING we have ourselves a winner.
[OP] are you able to get into the bootloader or recovery?
I remember when I first started rooting my phone it would be titles like this that would scare me away form certain roms. Which is a good and bad thing. Although I would generalize the title a little. Like " dam i messed up installing a sense rom" this way it's a little more inviting to open minded people that want to help and less offending to people that put in time for tutorials and development
Sent using XDA App
aznprodgy said:
1. I have yet to hear of a non-rooted phone bricking because of the bad eMMc chip, only after you root it does the chip start acting funny. could have been a possibility that you had the bad eMMc, did you check to see before taking the plunge and rooting your phone?(guessing not lol )
Click to expand...
Click to collapse
Wrong. To hear this (or actually, to see this), you only need to go to the eMMC thread in General section, and look at the poll. You'll see enough failed non-rooted "bad" eMMCs, and you'll also see some "good" eMMC chips fail, even non-rooted. If you were reading the forum for the last 1/2 year, you'd hear more than enough of stock phones dying with failed eMMC. You can just try searching and reading the threads.
Moreover, you're wrong about the dangers of battery pull too. The danger isn't only when you're writing to sensitive partitions. It's a bit complicated, but I'll try to explain:
When the power is turned off, it doesn't go out at once - it takes a bit of time, several microseconds, maybe less, maybe more, depends on the capacitance of the supply path. During that time the electronic circuits still act, but with gradually diminishing voltage.
Circuits are built to function reliably in certain voltage range. The thing is that under that range, they don't stop functioning immediately - there is a range where they still function, but unreliably. Signals can receive erroneous values that aren't determined by the logic.
During that unreliable functionality period, a sequence of signals might happen that will cause overwriting one of the system partitions in the eMMC - since the logic doesn't function reliably, it can happen. If the phone is currently writing to eMMC (which might easily happen - programs read and write data when they run), you only need a couple of bits to fail in the bus address and write protection mechanism. The probability is very low and there are protections against that, but still, they aren't 100%.
If it happens, the phone is dead.
To add to that, there could be physical effects on eMMC chip from uncontrolled voltage drop.
So, this is why there's a recommendation to avoid pulling the battery, and using it only when really necessary.
Jack_R1 said:
Wrong. To hear this (or actually, to see this), you only need to go to the eMMC thread in General section, and look at the poll. You'll see enough failed non-rooted "bad" eMMCs, and you'll also see some "good" eMMC chips fail, even non-rooted. If you were reading the forum for the last 1/2 year, you'd hear more than enough of stock phones dying with failed eMMC. You can just try searching and reading the threads.
Moreover, you're wrong about the dangers of battery pull too. The danger isn't only when you're writing to sensitive partitions. It's a bit complicated, but I'll try to explain:
When the power is turned off, it doesn't go out at once - it takes a bit of time, several microseconds, maybe less, maybe more, depends on the capacitance of the supply path. During that time the electronic circuits still act, but with gradually diminishing voltage.
Circuits are built to function reliably in certain voltage range. The thing is that under that range, they don't stop functioning immediately - there is a range where they still function, but unreliably. Signals can receive erroneous values that aren't determined by the logic.
During that unreliable functionality period, a sequence of signals might happen that will cause overwriting one of the system partitions in the eMMC - since the logic doesn't function reliably, it can happen. If the phone is currently writing to eMMC (which might easily happen - programs read and write data when they run), you only need a couple of bits to fail in the bus address and write protection mechanism. The probability is very low and there are protections against that, but still, they aren't 100%.
If it happens, the phone is dead.
To add to that, there could be physical effects on eMMC chip from uncontrolled voltage drop.
So, this is why there's a recommendation to avoid pulling the battery, and using it only when really necessary.
Click to expand...
Click to collapse
well damn bro, didnt think it was that serious...
Hey Jack_R1 thanks for the input. I always enjoy getting a snapshot of information to clarify how things work.
wanabdev do you know if you're able to get into the boot loader to get access to fastboot? You really may be able to save your phone if you're still able to do this.
Wi-Fi Calling using Darkside Runny 2.2
Does anyone know how I can resolved my wifi calling issue using this ROM? I've tried about 10 ROMS on my MT4G, and found this to be the nicest. But when I'm on wifi, any calls I make or receive, the person on the other end says they can barely hear me. I can hear them just fine, but they can't. This is also true at multiple hotspots, ie. Starbucks, friends home, etc.
When I flash different ROM, this feature works just fine.
Help!
Chicago T said:
Does anyone know how I can resolved my wifi calling issue using this ROM? I've tried about 10 ROMS on my MT4G, and found this to be the nicest. But when I'm on wifi, any calls I make or receive, the person on the other end says they can barely hear me. I can hear them just fine, but they can't. This is also true at multiple hotspots, ie. Starbucks, friends home, etc.
When I flash different ROM, this feature works just fine.
Help!
Click to expand...
Click to collapse
same here, not rooted. any calls I make or receive, the person on the other end says they can barely hear me. I can hear them just fine, but they can't.
Wi-Fi Calling using Darkside Runny 2.2
glacier1122 said:
same here, not rooted. any calls I make or receive, the person on the other end says they can barely hear me. I can hear them just fine, but they can't.
Click to expand...
Click to collapse
Right, soooooo annoying. There's gotta be a fix out there? I like this ROM the best, it has all the little tweaks that make me happy!
Anyone have any ideas?
Flash the newest version.
http://forum.xda-developers.com/showthread.php?t=1283682
Hi all, I normally don't like to post questions because i feel like the answer is somewhere online, and i almost always find it. Apparently this is one of those times i can't. Bear with me as i wanna make sure i dont leave anything out.
My problem is simply that my HD2 will not find any access points when i turn on my wifi. This started happening to me with a previous HD2 i had about a month ago for no aparent reason. I had not changed or flashed anything on my phone around the time the problem happened. I figured i would ignore the problem because i had 3g anyways but then that HD2s touch screen failed so thats why i ended up sending it in for a warranty replacement.
Now i hoped that since i had a new HD2 that the problem would be gone, i mean how could it be possible that the problem would appear on a brand new phone. So i went about doing my usual. Installed 2.08.HSPL, followed by MAGLDR, followed by MIUIAndroid.com rom, same setup i had before the problem began. I made sure the first thing i did was turn on WiFi on first boot of the phone. To my suprise, No access points found. I know it is not my router as i have connected every other device im my house to my router, including other androids and windows phones. I thought maybe its a MAGLDR/Android issue. Flashed back to WinMobile 6.5 and still no acess points. Tried every radio available and still no access points.
Bottom line is im really confused how this can be with a brand new phone. Im pretty sure its a software issue but im out of ideas.
SO please if anyone can help. Please :'-(.
Just found out this morning that it can find my access point, but only if i literally lay it on top of my router. if i go more than maybe a foot away from it then nothing.
It sounds like a hardware issue. I read about these things having issues with a connection to the antennae that can be solved by taking apart the phone and cleaning some leads.
joshnchen said:
It sounds like a hardware issue. I read about these things having issues with a connection to the antennae that can be solved by taking apart the phone and cleaning some leads.
Click to expand...
Click to collapse
Sounds strange that such a new phone would have a hardware issue already. at this point though, im willing to try anything. how/where exactly would i clean/find these leads?
Check this: forum.xda-developers.com/showthread.php?t=834199 and this: forum.xda-developers.com/showthread.php?t=1190180, but be aware that opening your phone might void your waranty. Good luck
is that the only rom you have flashed? and was it nand, or sd etc...??
make sure because it could be a simple error in software as well..
something you can try and report back before opening up the phone
b12rtc said:
Check this: forum.xda-developers.com/showthread.php?t=834199 and this: forum.xda-developers.com/showthread.php?t=1190180, but be aware that opening your phone might void your waranty. Good luck
Click to expand...
Click to collapse
thanks. will take a look at those.
tecle2595 said:
is that the only rom you have flashed? and was it nand, or sd etc...??
make sure because it could be a simple error in software as well..
something you can try and report back before opening up the phone
Click to expand...
Click to collapse
I first got the problem while it was still stock. then i flashed miuiandroid.com's rom with MAGLDR and still. then i went to tytungs ICS Beta4 roms and still. now im back to the miuiandroid rom. so it doesnt seem to be a rom issue.
also all the roms were nand
gotenksnath said:
Just found out this morning that it can find my access point, but only if i literally lay it on top of my router. if i go more than maybe a foot away from it then nothing.
Click to expand...
Click to collapse
Hi my Friend,
your black Wifi Coaxial-Cable inside your HD2 is unpluged and not correct Connected. I had this three times at three different EU-HD2 Devices, too ( the Distance for a working WIFI Signal was 1 Feet. Normal, without Antenna ;-)). Regular the Connector at the PCM at the upper Corner fall of...
If you Still have Warrenty you have to bring this Phone to a Service. If not, you have to fix this little Problem by yourself ( you need 2 Minutes to do that ). Be Carefully when you Bring the whole HD2 inside your Backcover. You have to Tape the Vol-Rocker with a little Sticky-Tape. So this Plastic can´t fall off during the reassembling and is not to Deep to kill the Vol. Buttons...
The Opening is easy. You need only a Guitar-Plectron and t Torx-Screwdriver. Here you find Pictures:
http://mperlitsch.hintergrundbild.com/htc_hd2.htm
Here a Picture from you Sick-Zone:
http://mperlitsch.hintergrundbild.com/htc_hd2/hd2_23.jpg
Where the RED ARROW is, you see One Wifi-Connector and i bet a Sex-Pack good German Beer, this one is your Problem. Put this Connector Back and everything works fine...
Best Regards,
Micha
P.S. Sorry for my poor english !
Perlitschke said:
Hi my Friend,
your black Wifi Coaxial-Cable inside your HD2 is unpluged and not correct Connected. I had this three times at three different EU-HD2 Devices, too ( the Distance for a working WIFI Signal was 1 Feet. Normal, without Antenna ;-)). Regular the Connector at the PCM at the upper Corner fall of...
If you Still have Warrenty you have to bring this Phone to a Service. If not, you have to fix this little Problem by yourself ( you need 2 Minutes to do that ). Be Carefully when you Bring the whole HD2 inside your Backcover. You have to Tape the Vol-Rocker with a little Sticky-Tape. So this Plastic can´t fall off during the reassembling and is not to Deep to kill the Vol. Buttons...
The Opening is easy. You need only a Guitar-Plectron and t Torx-Screwdriver. Here you find Pictures:
http://mperlitsch.hintergrundbild.com/htc_hd2.htm
Here a Picture from you Sick-Zone:
http://mperlitsch.hintergrundbild.com/htc_hd2/hd2_23.jpg
Where the RED ARROW is, you see One Wifi-Connector and i bet a Sex-Pack good German Beer, this one is your Problem. Put this Connector Back and everything works fine...
Best Regards,
Micha
P.S. Sorry for my poor english !
Click to expand...
Click to collapse
Thanks so much to you and everyone who helped me out. Im going to see how much longer my warranty is because the only reason i would really send it back is if the touch screen fails AGAIN (happened twice already) but that wont happen for at least a year. So if warranty is gonna expire before then ill fix myself. again thank you to everyone.
By now folks realize there are different hardware variances for the touchscreen which is one reason why some people have issues and others do not.
Don't you hate it when you have a workable system, then an update comes along which fixes something, let's say GPS, but then your touchscreen goes down the tubes? Suddenly you have dead spots, dead bands, ghost/phantom touches, stuck touches, broken drags, etc. Touchscreen works ok when held or plugged in, but is unusable on a table?
Never fear, I've put together packages to handle 3 different variances of the touchscreen.
I was able to make the touchscreen usable again on 3 of 4 test units. The 4th was always bad even out of the box so it might be hopeless for that one.
I do NOT claim this will fix everyones' touchscreen and that isn't even the goal as it might be an impossible task.
The goal is to make 70-80% of the problem units usable (again), but even if only 50% become usable this is an improvement over the current situation.
On to the packages:
In the attached boot-ts.7z file you'll find 4 files:
boot-ts10-lock.img
boot-ts20-lock.img
boot-ts30-lock.img
boot-ts-unlock.img
the ts10, ts20, and ts30 packages handle 3 variances on the touchscreen
You basically try each one to see which works best for your particular touchscreen.
Once you find one (and hopefully you do) then it is locked in place so future updates won't mess up your touchscreen again. No more OTA performance anxiety.
Now let's say there is an update in the future which has touchscreen fixes you want to use, that is where the 4th package comes into play. Once you use the ts-unlock image, you will once again be using touchscreen updates from the manufacturer. If that update doesn't work out, you can go back and use the ts10/20/30 package that was working for you.
Ok, so how does all this work?
I tried to make the process as simple as possible (has been tested on JWR66N, JSS15J, and JSS15Q, will work on LTE and custom ROMs also):
Your bootloader must be UNLOCKED to use these packages. Unlocking your bootloader is covered in this post.
unpack the boot-ts.7z package using 7-zip
you'll be left with a boot-ts directory with the aforementioned files
connect your tablet by USB
make sure USB debugging is enabled
Settings->About tablet [tap "Build number" 7 times]
Settings->Developer options [check "USB debugging"]
you can find adb/fastboot drivers HERE
in a command prompt in the boot-ts directory type (commands in italics)
adb reboot bootloader
wait for the bootloader screen to come up
alternatively use Power+VolDown to get to the bootloader/fastboot screen
fastboot boot boot-ts10-lock.img
this is how you try out package ts10
the screen will hang for 18-24 seconds, this is NORMAL, do not touch
this does NOT flash over your existing kernel
wait until Android is COMPLETELY booted
Note: if you are on Android 4.4 the stock 4.3 kernel will not get past the BouncingBalls
wait 120 seconds for the boot to settle down
press/hold the Power button 10-15 seconds until the tablet reboots
proceed to next step
adb reboot
after booting to Android you MUST reboot at least once
IGNORE any instability up to this point, it is expected
if adb reboot does not work for some reason, use the power button to shutdown/reboot
once you are booted into Android the 2nd time, try out the touchscreen and see if it feels usable
if there is instability, give it one more reboot back into Android before judging
if things are not working acceptably
repeat step #3, with ts20, and ts30 if needed
hopefully between ts10, ts20, and ts30, you will have found a package that works for you
there is nothing else for you to do
you can reboot and use your normal ROMs, custom ROMs, stock kernels, custom kernels, etc.
your touchscreen package is locked in place and won't change unless you want it to
if you want to go back to the way it was before and/or you want a future touchscreen update from the manufacturer
repeat step #3 using boot-ts-unlock.img
upon first reboot you will have the touchscreen software from the installed ROM/kernel
Please post feedback with:
the version of software you are running
what was/is broken
whether any of the packages helped
Remember to click thanks if you find this useful.
That's it folks, hope this helps somebody.
very interesting! lots of FC after loading the file, cant really "Power off using power button" because of FC-windows, using adb reboot instead.
current ROM: [ROM][CM10.2][4.3][CyanogenMod FLO Kangs][DJL10.2][LINARO][Build 10-TEST][2013/08/27]
ts-10: no more jumping in google maps while zooming/panning, but still jumping in other apps. after second reboot, starts jumping in maps again. after third reboot, no jumping on rightside of screen.
screenshot using two fingers
ts-20: lots of jumping on right side of the screen, zooming/panning in gmaps is still jumpy. after third reboot, still jumpy in gmaps.
ts-30: still jumps of right side of the screen, just a few mm from the right bezel,zooming/panning in gmaps is still jumpy. after second reboot, same effect. after third reboot, still jumpy on right side of screen.
so what exactly are in those files?
neonlite said:
very interesting! lots of FC after loading the file, cant really "Power off using power button", using adb reboot instead.
tried ts-10. no more jumping in google maps while zooming/panning, but still jumping in other apps, will try others.
so what exactly are in those files?
Click to expand...
Click to collapse
When you say lots of FCs, can you tell me what ROM/version you are running?
You should IGNORE any instability in that first boot. While you can boot into android using the files I'm providing (and in some cases run fine), there could be mismatches in versions depending on what you have currently installed, which is why I say in RED you must reboot at least once before the system will become stable.
Once you do that reboot, you are back on your original software with just the touchscreen controller updated.
neonlite said:
ts-30: still jumps of right side of the screen, just a few mm from the right bezel,zooming/panning in gmaps is still jumpy. after second reboot, seems most stable.
Click to expand...
Click to collapse
You must IGNORE any results from that first boot for all the packages, especially since you are running CM because (on that first boot) you are essentially running CM with a stock kernel without any kernel mods CM may need.
On CM I would actually not pass judgment until perhaps a second reboot.
One shouldn't have as much instability in that first boot if they are running a stock ROM.
Can you compare the behavior to what you had before trying them out?
I presume you had some issues before, hence trying these out.
sfhub said:
You must IGNORE any results from that first boot for all the packages, especially since you are running CM because (on that first boot) you are essentially running CM with a stock kernel without any kernel mods CM may need.
On CM I would actually not pass judgment until perhaps a second reboot.
One shouldn't have as much instability in that first boot if they are running a stock ROM.
Can you compare the behavior to what you had before trying them out?
I presume you had some issues before, hence trying these out.
Click to expand...
Click to collapse
yes, ignored all FC's. no problem.
ts-10 is running perfectly, no more jumpy stuff. maps/right side of screen, hold and drag working great too.
I really appreciate how much effort you've put into helping others with troubled devices here.
Could we get some clarification on what exactly the 3 packages are? Are these touchscreen settings customized by you or simply the settings from each of the 3 versions of 4.3 we have had available to us?
You sent me here from the other thread and i must thank you, the ts10 one worked fine and now no screen problems, cancelled my replacement. Just a question though, if you tap hard on the camera corner of the tablet whilst holding it in the air, do you hear a small rattle?
It is the touchscreen controller software.
pashinator said:
Just a question though, if you tap hard on the camera corner of the tablet whilst holding it in the air, do you hear a small rattle?
Click to expand...
Click to collapse
Every unit has the rattle. Some louder than others. It is normal. Possibly the lens or focusing mechanism.
sfhub said:
Every unit has the rattle. Some louder than others. It is normal. Possibly the lens or focusing mechanism.
Click to expand...
Click to collapse
cool i thought i broke it by bashing it to get the screen to work again
i've been a long time lurker at the xda forums and your multitouch fix made me register and become a member just to say thanks. ts10 fixed my multitouch issues, going to observer for a few more days and update you if there are bugs. thanks a lot!
My tablet was working perfectly on the JSS15J then JSS15Q came along and I found letters "sticking" while typing and the screen was unresponsive to touch while laying flat on a table. I flashed the ts-10-lock image and so far, so good. I have been typing for awhile now with no "sticking" letters, and while laying flat on a table. I have not encountered the unresponsive screen at all flat on its back or otherwise. I will continue running through scenarios that used to give me problems and report back if I encounter anything. Also, running Bulletproof kernel and no impact with kernel functions.
Thank you sfhub!
Can anyone verify if placing the N7 on a Macbook Pro keyboard still triggers the multitouch craziness with the patch?
This is the video of my N7 placed on my MBPs' keyboard.
http://www.youtube.com/watch?v=H05N1P0dpTo
Can this really be only a software problem?
I am not really experiencing other touchscreen issues with my N7 except for some very rare stuck touches. This one I triggered by accident.
bandit_knight said:
Can anyone verify if placing the N7 on a Macbook Pro keyboard still triggers the multitouch craziness with the patch?
Click to expand...
Click to collapse
So this guy goes to the doctor's office and says my head hurts everytime I hit the wall. The doctor says, then stop hitting the wall.
Couldn't you just slide it over and don't use the tablet on top of the keyboard?
Have you considered the MacBook Pro might be emitting interference? Stray currents and voltages? It doesn't take much to throw these capacitative touchscreens off.
On this thread, most people have it much worse than you making the tablet very hard to use. We are trying to get these units back into a state that is at least usable.
Your case, while an interesting science project really isn't something someone would feel any sense of urgency to help address.
Excellent.
I'll try these now and put them through there paces.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Great work
Incredible!! tried the ts10 and OMG everything is fixed!! Great work, sfhub!!
you should work in Google, seriously! shouldnt he, everybody?
My device is:
1) 4.3 JSS15Q
2) two finger touching registered as one finger, and muiti-touches ghosted. hold on the Left side of screen and the touch is registered repeatedly
1) TS10
Yea I booted 10 first and it is great. I can't reproduce any of the bugs I've seen before using YAMMT.
Google Maps Pinch/Zoom is working flawlessly. I couldn't even zoom in before.
The OP says to "fastboot boot boot-ts10-lock.img". Should we eventually "fastboot flash boot-ts10-lock.img" to make it permanent?
My N7 is:
HW rev_e
Bootloader....... FLO-03.14
15Q - CM 10.2 Kanged Build 9
Sitting the N7 on my Logitech Keyboard doesn't make it go crazy either! LOGITECH FTW
sfhub said:
It is the touchscreen controller software.
Click to expand...
Click to collapse
How do you "lock" it in so that it won't get updated? Is it just a file in the filesystem, if so how do you prevent "fastboot erase" from getting rid of it? I've looked at ektf3k.c and know where I need to make a change so that it will replace any non-matching version, but I don't really know where the actual firmware is stored. It doesn't seem to be in the vendor part of the kernel tree or in the actual ektf3k.c or ektf3k.h files. Where is it kept? kept in fw_data.b
I'm new to Android, but I'm not new to Linux or reverse engineering so please be patient with me. Just looking for a technical description of how you did what you did. What exactly is in the .img files?
EDIT: I haven't booted any of them yet, but I'm guessing these are Linux kernel images with a modified version of the elan driver. Sorry for being stupid, I'm just trying to put this all together in my head and I can't cope with anything that seems like magic. Thanks for your time.
EDIT: Ok, I figured out where the firmware is stored. I also successfully built a ROM with my compiled kernel and flashed them to the tablet. No brick, it booted the second try and seems to work. Of course there's no apps on it hardly.
I'm kinda thinking out loud here, please correct anything that I get wrong:
I started off with the assumption that there was a closed source driver, but that seems to have been incorrect on my part. After looking at the code a little more, I see that ektf3k.c appears to be the lowest level driver, outside the embedded firmware. The driver does only update the firmware in the case that the flash is empty (FFFF.....) or the firmware presented is a higher version (just as you said of course). It appears that a simple change will make it flash any version presented that is different than the one currently flashed in. I plan to try this on my tablet and see if there are any unexpected repercussions from doing so.
I wish I had a datasheet for the controller (hint hint anyone).
DISCLAIMER: I know that you have already solved this problem in an arguably better way, I just want to tinker around a little. Thanks again. :good::good::good:
sfhub said:
By now folks realize there are different hardware variances for the touchscreen which is one reason why some people have issues and others do not.
Don't you hate it when you have a workable system, then an update comes along which fixes something, let's say GPS, but then your touchscreen goes down the tubes?
Never fear, I've put together packages to handle 3 different variances of the touchscreen.
I was able to make the touchscreen usable again on 3 of 4 test units. The 4th was always bad even out of the box so it might be hopeless for that one.
I do NOT claim this will fix everyones' touchscreen and that isn't even the goal as it might be an impossible task.
The goal is to make 70-80% of the problem units usable (again), but even if only 50% become usable this is an improvement over the current situation.
On to the packages:
In the attached boot-ts.7z file you'll find 4 files:
boot-ts10-lock.img
boot-ts20-lock.img
boot-ts30-lock.img
boot-ts-unlock.img
the ts10, ts20, and ts30 packages handle 3 variances on the touchscreen
You basically try each one to see which works best for your particular touchscreen.
Once you find one (and hopefully you do) then it is locked in place so future updates won't mess up your touchscreen again. No more OTA performance anxiety.
Now let's say there is an update in the future which has touchscreen fixes you want to use, that is where the 4th package comes into play. Once you use the ts-unlock image, you will once again be able to get touchscreen updates from the manufacturer. If that update doesn't work out, you can go back and use the ts10/20/30 package that was working for you.
Ok, so how does all this work?
I tried to make the process as simple as possible (has been tested on JWR66N, JSS15J, and JSS15Q):
Your bootloader must be UNLOCKED to use these packages. Unlocking your bootloader is covered in the stickies.
unpack the boot-ts.7z package using 7-zip
you'll be left with a boot-ts directory with the aforementioned files
connect your tablet by USB
make sure USB debugging is enabled
you can find adb/fastboot drivers HERE
in a command prompt in the boot-ts directory type (commands in italics)
adb reboot bootloader
wait for the bootloader screen to come up
alternatively use Power+VolDown to get to the bootloader/fastboot screen
fastboot boot boot-ts10-lock.img
this is how you try out package ts10
the screen will hang for 18-24 seconds, this is NORMAL, do not touch
this does NOT flash over your existing kernel
adb reboot
after booting to Android you MUST reboot at least once
IGNORE any instability up to this point, it is expected
once you are booted into Android the 2nd time, try out the touchscreen and see if it feels usable
if there is instability, give it one more reboot back into Android before judging
if things are not working acceptably
repeat step #3, with ts20, and ts30 if needed
hopefully between ts10, ts20, and ts30, you will have found a package that works for you
there is nothing else for you to do
you can reboot and use your normal ROMs, custom ROMs, stock kernels, custom kernels, etc.
your touchscreen package is locked in place and won't change unless you want it to
if you want to go back to the way it was before and/or you want a future touchscreen update from the manufacturer
repeat step #3 using boot-ts-unlock.img
Please post feedback with:
the version of software you are running
what was/is broken
whether any of the packages helped
Remember to click thanks if you find this useful.
That's it folks, hope this helps somebody.
Click to expand...
Click to collapse
So if we do this can we lock the boot loader backup. If for some reason it doesn't work will I be able to take it back for exchange. After unlocking the boot loader. Do people leave the boot loader unlocked . Is the software staying the same meaning will I be ok downloading future updates.
Is there a way to find out what variance is installed right now on the device? I got JSS15Q and my tablet is useable but sometimes there are ghost touches or the touch is stuck or gets interrupted and the likes.
Hey!
While I was calibrating my fingerprint, phone suddenly turned off and went to recovery with screen off.
I managed to reflash stock rom through fastboot and it boots to system fine, but the screen stays off and the front camera keeps trying to open while playing the MIUI camera sound (sometimes, while booting, the camera does manage to open once, kinda like it's calibrating). Some playing around with ADB and it seems that the SIM isn't recognized either.. antenna maybe?
I opened the phone up and checked everything, there's no visible issues with the electronics, however it could just be the inside of a cable that died?
Does anyone know what this could be? I noticed the screen, fingerprint reader and antenna are all connected to the same removable PCB, but the camera isn't so that's odd.
Aren't we moving way too fast here? Like wtf is happening rn?
First: Explain in detail from the beginning please if you want help.
Second: Please state exactly what is your issue, and the ROM version of your device.
I don't think what you just did is the cause of whatever problem you're facing, do you mind telling me the source from which you got this phone? Otherwise you might want to send it to a service center.
XDHx86 said:
Aren't we moving way too fast here? Like wtf is happening rn?
First: Explain in detail from the beginning please if you want help.
Second: Please state exactly what is your issue, and the ROM version of your device.
I don't think what you just did is the cause of whatever problem you're facing, do you mind telling me the source from which you got this phone? Otherwise you might want to send it to a service center.
Click to expand...
Click to collapse
It's a bit of a long one, so I didn't want to bother too much with the details if anyone knew what those specific issues could be caused by, here goes though:
I am on a Mi 9T bought on Amazon Italy in July 2019. I cannot comfortably send it to a repair center due to every authorized shop around here is just a drop-off point for Xiaomi RMA. I talked to them and, due to (>6 months old) glass damage to the screen and back of the phone, they intended to charge me way more than I can afford, as "solving issues covered by the warranty would require us to replace the accidentally damaged components"
As for what happened:
I was running LOS 17.1 with no issues for a few months. I went to unlock the phone and I heard the reboot vibration, which sent me to recovery (softbricked) but with no screen signal. I assumed it was just a software problem, so I flashed MIUI 12 (global, V12.0.7.0.QFJMIXM) to see what would happen.
As it completed, the phone rebooted itself, the MIUI logo popped up and it went to system (seemingly) without any issues.
I went through the initial wizard and played around with it. everything seemed fine and I even made sure the screen did work in recovery and fastboot. Later, when I went to setup the fingerprint reader, the screen went blank for half a second when I first touched it, and then the same screen death -> reboot to recovery.
The phone was softbricked again, though, this time, reinstalling MIUI didn't yield the same success. Now:
MIUI boots "normally" again
The screen isn't working at all
The front camera opens, as if it's calibrating, when system boots up
The front camera randomly tries to open again every now and then, failing to do so as if the motor is stuck, while MIUI plays the camera closing sound.
Meddling through ADB, the antenna doesn't seem to be working, but I can't be 100% sure due to the methods used
The power and volume buttons, speakers, and the charging light all work.
I have opened the phone up myself, thoroughly checked every cable, connection and PCB, but there is no sign of damage. I put it back together and the same issue continued.
My best guess is that something inside the fingerprint reader went bad and shorted something else.
What that something else is, I couldn't find out. Given the antenna, screen and FOD are all connected to the same little PCB which then runs a couple cables to the motherboard, I am now in the process of finding a couple replacement cables to see if that fixes anything.
As I mentioned before, repair centers are not an option due to the lack of anyone who's willing to help me for less than a good chunk of the price of the phone.
Interesting. So basically what happened is due to the initial soft brick and accordingly you flashed a global MIUI 12 ROM, which in return brought you to the second soft brick which caused some issues within the hardware of the device.
Now you're stuck with a faulty screen, a faulty camera and a faulty antenna.
I don't have the skills to play around with the motherboard and the phone circuit. And I don't care which youtube tutorial you saw, you should have NEVER done that - Of course unless you're actually experienced in that manner, then I apologize for speaking with such prejudice -
I can't help you if you messed up your phone circuit since I have no knowledge about android hardware, however I can safely assume that what caused your issue isn't related to hardware.
I think the issue is caused by an incomplete flashing of a ROM (In this case MIUI 12 global) OR flashing a different variation from your device.
e.g. you flashed only the ROM, but didn't flash the other components of the ROM.
Needless to say, flashing a variation of the ROM that isn't meant for you device can be a disaster recipe.
I recommend flashing LOS again, since you can't go back on Xiaomi devices due to rollback protection.
XDHx86 said:
I don't have the skills to play around with the motherboard and the phone circuit. And I don't care which youtube tutorial you saw, you should have NEVER done that - Of course unless you're actually experienced in that manner, then I apologize for speaking with such prejudice -
Click to expand...
Click to collapse
I understand why you'd think that and have seen people do similar stupid things, however I didn't watch any youtube video and know what I'm doing quite well.
I made sure I flashed the correct rom through fastboot to restore everything to stock. I did try to reflash LOS and whatever else (though it's kind of a pain with adb shell), but it doesn't fix the problem, sadly.
That's why I'm betting on a HW issue.
The fingerprint reader and everything else worked flawlessly in LOS for months, but it made the screen go blank and bricked the device in both LOS and fully functional, stock MIUI.
Currently, I'm battling with this damn thing to get USB debugging working while booted to system, so I can do a few things like cast the screen to my PC and see what works from there.
I have access to fastboot and recovery, but everything I know (editing build.prop or patching the boot image) didn't work so far. Do you have any idea what I could do to get that done?
angometry said:
Currently, I'm battling with this damn thing to get USB debugging working while booted to system, so I can do a few things like cast the screen to my PC and see what works from there.
Click to expand...
Click to collapse
If the touch screen is dead then you can use mouse and OTG cable.
If it is completely black then you can get usb c to HDMI cable (Also usb c hub might work, like this one). Or you can use playstore on pc to download and install apps like (Screen stream over HTTP) on your device, just make sure your device is connected to the internet and you're signed in on your phone as well, you might have to type in the screen password if you have one.
angometry said:
I have access to fastboot and recovery, but everything I know (editing build.prop or patching the boot image) didn't work so far. Do you have any idea what I could do to get that done?
Click to expand...
Click to collapse
I don't know why bother with build.prop unless you have the wrong fingerprint prop. Then you can get the correct one from your device's stock ROM, though I think this is irrelevant to your issue.
All I can think of is:
Wiping dalvik cache, though you might have already done that.
Trying other custom ROMs from here.
You may try to get your device rollback index and installing a MIUI ROM that has index higher than it, and see if that works.
That is as far as I can help, unfortunately.
I have zero knowledge when it comes to hardware, so I can only help with software issues. If none of my solutions worked then sorry for wasting your time :/
XDHx86 said:
If it is completely black then you can get usb c to HDMI cable (Also usb c hub might work, like this one).
Click to expand...
Click to collapse
Wait, does it actually just automatically use it as a 2nd screen if I connect it via HDMI?
XDHx86 said:
I don't know why bother with build.prop unless you have the wrong fingerprint prop. Then you can get the correct one from your device's stock ROM, though I think this is irrelevant to your issue.
Click to expand...
Click to collapse
Sorry, I didn't explain myself, I'm looking for a way to enable USB Debugging without a screen. Thinking that using adb in twrp is the best way, but I can't manage to do it. Do you have any ideas?
If I can get it on, I can then use things like scrcpy to get screen signal through USB.
Main problem with everything else is that the screen is 100% dead. Even with usb otg I don't know how I could possibly get through the setup wizard haha
angometry said:
Wait, does it actually just automatically use it as a 2nd screen if I connect it via HDMI?
Click to expand...
Click to collapse
I haven't tried it myself, however it should detect it as a second monitor. Give it a try the cable isn't costly at all anyway.
angometry said:
I'm looking for a way to enable USB Debugging without a screen. Thinking that using adb in twrp is the best way, but I can't manage to do it. Do you have any ideas?
Click to expand...
Click to collapse
TWRP has debugging mode on by default, however that strictly applies to recovery and fastboot modes only as debugging mode is pretty powerful and can cause security issues. So you better forget about it.
I saw one of my friends who owns an authorized service center use some cable connections to get the screen to display on another touch screen. If you have the capabilities and resources I recommed trying it, though don't mess too much with the motherboard.
Just a question though, can you confirm if the touch is working? If not then there's a chance - Although slight - that this is just a UI problem (Which is pretty common in MIUI ROMs for some reason). In that case deleting dalvik cache or completely reflashing the ROM might solve the issue.
I may not do much help but certainly someone there can help so it's better if you include "usb debugging" in the title and/or the tags. Like changing the title to "Enabling usb debugging without screen" or "Screen is dead, need help to flash ROM"
Using proper title and proper tags can get the right person to help.