i just bought a phone one month ago, a BLU Studio 5.5....
well this phone does not have any custom roms for it like so many other of these mtk phones that have flooded the market, so i started my quest of finding a compatible rom for it.
i tried a rom from a Gionee G2 (specifically WBW5883GI_0301_T5425) as these phones are pretty much identical....the short version is it wasnt compatible and it failed to load, so i immediately reflashed my original backup.
but when it loaded my touch is no longer calibrated properly. for instance to press the home button i must press the screen about one inch higher and slightly to the left. as you can imagine the phone is pretty much unusable now, its a pain just making a call let alone doing anything else on it.
since then ive reflashed it many times. ive factory reset many times. ive tried multiple recalibration apks. ive tried the calibration.ini trick. ive even went as far as making a full 4gb raw backup from an identical phone...nothing has remedied this problem.
this is a mt6589 phone, ive tried flashing with both sp flash tool and cwm, as well as nvram restore from MtkDroidTools.
is the calibration data stored in some inaccessible location?
was this just a coincidence that my digitizer went wacky during a flash?
anyone else ever hear of a similar problem?
any and all comments are welcome...any more info needed just ask
-D
[edit0]
some more info
the calibration is the same in cwm also.
the calibration seems to be good at the top left of the screen, and get worse the farther you get from that position
[/edit0]
[edit1]
dang think i posted in the wrong section...feel free to move it
[\edit1]
Yes, I have the same problem but I can't find the solution. If you can fix the problem, please tell me.
Related
I've been having a reoccurring freeze issue with my HD2 no matter what build I am using. On the initial first time startup everything works fine until the display goes to sleep. Once it does, the touch pad freezes. Hard buttons still work although don't do anything since it's stuck on the lock screen, and even if I soft reset or reflash anything, the problem persists.
Not even disabling the lock screen helps. Even if I install lock screen disabling apps (I've tried them all), the touch screen is still non-responsive when I wake the display.
Whether I use stock winmo, custom winmo or android (NexusHD2 gingerbread 2.3.4 as of late, but I've also used the old Desire Android 2.1) makes no difference; neither does reflashing HSPL, radio, ROM, Recovery CWM, reformatting SD card, fixing file permissions or even performing Task29. I've even restored everything all the way back to stock winmo which didn't work, so I performed every step along the road to getting back to Android. No success. I'm at a loss because I've tried every solution I have found online in just about every order imaginable.
There has to be some solution to this issue and I'm hoping that SOMEONE out there will rescue me. It's been a problem since I first got the phone and although even once in a while it will work for no apparent reason, it has been in this status for some time.
PLEASE help. I'm tired of paying a bill for a phone I can't use.
It's most likely a hardware problem. Your digitizer has most likely went out, I'm not a pro but it happened to me before.
little13193 said:
It's most likely a hardware problem. Your digitizer has most likely went out, I'm not a pro but it happened to me before.
Click to expand...
Click to collapse
Is the digitizer easily fixable or would I need to replace it? Or would it just be overall cheaper to replace?
Hi,
I realize many of you will state this has been asked before but I really can't find a fix for the phone so I thought maybe it's best to ask my own question and describe the issue.
So I work in a small company dealing with recycled mobile phones. I've been there about a year and a half, I had no training as it was just me and another guy, so it was just google and a lot of help from this site, so thanks guys for all the great help as I've got most of my answers from previously asked questions. I'm not a complete noob, but still have lots to learn.
This question I will keep related to the Moto G. So in my company we managed to pick up around 20 Moto G XT-1032. However around 6 of them seem to have software issues, after a factory reset (after testing) 6 got stuck on a boot loop. So I searched around and found 'http://forum.xda-developers.com/showthread.php?t=2542219' which I followed and managed to flash the software back to 4.3, I had issues on an XP computer but after trying with a windows 7 it seemed to work and the phone booted up. The 6 which got stuck in a boot loop had previously been factory reset as I could see it was at the factory set-up when I turned them on. So I was quite confused why 6 would get stuck.
So today I actually finally figured out to move to a windows 7 laptop which allowed me to actually flash the phones. After flashing the phone back to 4.3 I tested the phone and all seemed fine, so as these are to be sold I had to factory reset them again (resetting through the standard settings, no special code). So once again they all seemed to get stuck in a bootloop, but instead of an actual bootloop it shows the Motorola logo and then the screen goes black but I can see the backlight is still on, then it just sits there as long as I leave it, over 4 hours so far.
I have attempted a second flash on one of the phones and it's done the same. I'm downloading UK firmware for the xt1032 not the dual sim version. I've held the power button for 120 seconds as someone mentioned that on some random thread. Managed to get to restart and got into the android bios thingy (not sure what it's actually called, hopefully you'll understand what I mean) and attempted a factory reset but it just gets stuck on the black screen (still can see the backlight is on).
I'm now out of ideas, I really don't know what else to try. I'd really appreciate if someone could shine some light on this and what could possibly be causing the issues. The phones look brand new and are known as '14 day returns' meaning someone has returned it from new after 14 days, they are then fully tested by the manufacturer before being sold to companies like ourselves. If it was one phone I'd suspect maybe a hardware issue but because it's 6 I'm just thinking this would be a strange coincidence.
I'd be interested to hear from anyone who could give me advice on, unlocking, flashing and anything else which could help me at my place of work. I work with Sony's, HTC's, Lumia's, Samsung's and Motorola's, and also every now and again ZTE and Huawei's. So feel free to contact me if you think you could offer me any advice, all is welcome.
Thanks for reading, and thanks in advance to any advice.
Chris
kimber015 said:
Hi,
I realize many of you will state this has been asked before but I really can't find a fix for the phone so I thought maybe it's best to ask my own question and describe the issue.
So I work in a small company dealing with recycled mobile phones. I've been there about a year and a half, I had no training as it was just me and another guy, so it was just google and a lot of help from this site, so thanks guys for all the great help as I've got most of my answers from previously asked questions. I'm not a complete noob, but still have lots to learn.
This question I will keep related to the Moto G. So in my company we managed to pick up around 20 Moto G XT-1032. However around 6 of them seem to have software issues, after a factory reset (after testing) 6 got stuck on a boot loop. So I searched around and found 'http://forum.xda-developers.com/showthread.php?t=2542219' which I followed and managed to flash the software back to 4.3, I had issues on an XP computer but after trying with a windows 7 it seemed to work and the phone booted up. The 6 which got stuck in a boot loop had previously been factory reset as I could see it was at the factory set-up when I turned them on. So I was quite confused why 6 would get stuck.
So today I actually finally figured out to move to a windows 7 laptop which allowed me to actually flash the phones. After flashing the phone back to 4.3 I tested the phone and all seemed fine, so as these are to be sold I had to factory reset them again (resetting through the standard settings, no special code). So once again they all seemed to get stuck in a bootloop, but instead of an actual bootloop it shows the Motorola logo and then the screen goes black but I can see the backlight is still on, then it just sits there as long as I leave it, over 4 hours so far.
I have attempted a second flash on one of the phones and it's done the same. I'm downloading UK firmware for the xt1032 not the dual sim version. I've held the power button for 120 seconds as someone mentioned that on some random thread. Managed to get to restart and got into the android bios thingy (not sure what it's actually called, hopefully you'll understand what I mean) and attempted a factory reset but it just gets stuck on the black screen (still can see the backlight is on).
I'm now out of ideas, I really don't know what else to try. I'd really appreciate if someone could shine some light on this and what could possibly be causing the issues. The phones look brand new and are known as '14 day returns' meaning someone has returned it from new after 14 days, they are then fully tested by the manufacturer before being sold to companies like ourselves. If it was one phone I'd suspect maybe a hardware issue but because it's 6 I'm just thinking this would be a strange coincidence.
I'd be interested to hear from anyone who could give me advice on, unlocking, flashing and anything else which could help me at my place of work. I work with Sony's, HTC's, Lumia's, Samsung's and Motorola's, and also every now and again ZTE and Huawei's. So feel free to contact me if you think you could offer me any advice, all is welcome.
Thanks for reading, and thanks in advance to any advice.
Chris
Click to expand...
Click to collapse
Before I start: DISCLAIMER: I DO NOT TAKE ANY RESPONSIBILITY FOR YOUR ACTIONS BY FOLLOWING MY INSTRUCTIONS. YOU ARE FULLY RESPONSIBLE FOR YOUR ACTIONS.
Now we got that out of the way...
Try upgrading to 4.4.2: http://sbf.droid-developers.org/phone.php?device=14 (Get the firmware here)
Use the thread you mentioned: http://forum.xda-developers.com/showthread.php?t=2542219
Hello All,
In my attempt to root the device which I was successful in doing somehow things went south when i tried to flash TWRP on my device. I performed the .img to tar.md5 conversion with the CWM Tool on another thread then i flashed the file to my device, afterwards the devices were rebooted and now I am unable to touch the screen with my fingers and only my S-Pen works, which tells me hardware wise the screen is ok but something software wise is causing this issue. Can someone please help me in troubleshooting this issue. I seen another user have this same exact issue but it ended with him sending it to the service center. I have performed a full dat/factory reset.... I have performed a full reflashing of the stock rom i have re-rooted. I am all out of options.
See video i made regarding this issue.
https://www.youtube.com/watch?v=orLEnWhlATo
Thanks in advance!
Can anyone help with this
Capacitive touch and spen use 2 totally different chips inside the tablet. The spen uses a Wacom digitizer, while touch interaction is processed using standard methods.
In fact, each one has their own ribbon cable from the screen to different points on the motherboard.
I have no idea how rooting broke your touch ability, but the spen working is not an indication that the touch interaction is not damaged in some way.
I can tell you that on mine (especially when using papyrus) it has a tendency to lose touch until I shut the screen off and turn it back on. Maybe something screwy is going on with the touch driver. Flash back to stock and see if it's still broken
Did the reset work?
I ask because we just got a used tablet off ebay and it is doing the same thing to me. My wife emailed Samsung who said blah-blah-blah so we are stuck with it. I know enough to brick a phone really fast, but I have been running custom Roms a long time and have replaced screens so I may check the cables on my day off.
But it was doing it before I rooted it, recovery, and Hyper-drive Rom.
though the knox had been tripped before I got it, so I don't know what has been done to it before this. So please let me know what you think even if you try it and it does or doesn't work and I will gladly do the same for you.
Thanks--Rick
Hi there,
I hope someone can help me. This is my last chance
Last week I broke my screen and replaced it with a screen I bought from Ebay. I did this more then once for friends, so everything went perfect
The screen works, touch works, colors are fine, but the aligment is wrong.
If I touch in the top region, then it takes the higher part of my finger
If I touch in the middle region, then Everything is fine
If I touch in the bottom region, then the lower port of my finger is used
This is not possible to get used to. So...I think I need to recalibrate my screen some way..
I looked and found a tool from 2012 or so, but that did not work because it cannot install. (TouchRecalibrate.apk , calibrate.apk, ..).
I looked for other apps in the store. Nothing that helps
I tried looking for settings but I can only find old threads that refer to calibration, so I assume that this function no longer exist.
I used the servicemenu but cannot find any calibration there.
I reinstalled the phone as well (factory default) + safe mode and I googled for hours.
The tool I am looking for is a tool that ask to put your finger on dots all over the screen and that it then generates some setting file that the operating system uses. No idea if such a program exists?
If someone has an idea, please let me know
The phone is not rooted but if needed I want to do this.
ps. feeling sad about this happening again. The phone is not even a year old.
My old Z2 broke as well... I wish that they go back to plastic..like the good old Xperia Arc S. I dropped that phone hundreds of times
greetings,
Demesmaeker
Hello, First time poster long time user of XDA, I some what experienced with flashing roms, recovery, kernels and modems but I ran into my first major issue.
I will start with how I obtained the phone and go from there, I think the more you know the more you could help.
I got the phone on ebay relatively cheap, its apparently google locked as he forgot his password, no biggie for me ill get around that.
He claimed he was replacing the screen and cracked the new glass while trying but not the lcd.
Anyway once I received it I turned it on and tried to see how far I could get in the initial set up.
I only got to the wifi selection screen, It would not turn on and when the button moved to the on position it would indefinitely load.
I assumed faulty rom flash.
I downloaded the latest rom from sammob and flashed to oreo, same Issue, I should point out at this point I had no data left on my sim to proceed on the phone without internet.
My friend who very experienced with the flashing seen suggested the modem.
I flashed one he suggested then no sim reception def no wifi.
ok damn.
I went to flash the oreo once again and for some messed up reason I wiped the nand only.
Well I wasnt to happy with myself to say the least.
To further ad to the pain, I can no longer access recovery or download mode to salvage this.
No button input seems to work.
It gets to the pulsing samsung logo and that its.
I even resorted to making a usb jig, It has no response to that but my spare note 2 boots to download no worries with it.
It does charge via usb, The buttons were working correctly when I was first in android at the beginning.
Does anybody have any suggestions or ideas?
Many thanks in advance, I will be following this post regularly and reply with feedback and report progress.
Cheers. r3al77