Hey guys, i updated my CM7 from RC2 to final some days ago and i started to notice some strange behaivour.
I started getting the black screen during calls problem so i went back to RC2 but still happening.
So i installed Sensor Test from market and i can see that the light and proximity sensors are not working for some reason. The rest of the sensors have numbers changing but not the light or proximity.
This is not my first time flashing a rom and i did all the proper steps and wipes, now no matter to which rom i go cant see the sensors working.
Any idea??
I'm having the exact same issue. I flashed CM7 Final nearly the same time I replaced my digitizer so I thought it I messed up my install somehow but maybe it's actually software related.
my workaround for the moment so i dont get the black screen of death is hexedit /system/lib/hw/sensors.mahimahi.so and change /dev/cm3602 to something else.
That way the sensor is disabled and i can talk normally and then return to homescreen without having to remove the battery.
i found quite a few ppl with this problem, there isnt any official statement about this issue from cyanogen right?
i have the same problem
What can i do?
I'm with nightly 51
I have done the hex edit hack on /system/lib/hw/sensors.mahimahi.so, and that did turn off the proximity sensor. However changing the line /dev/cm3602 to /eev/cm3602 to turn off the proximity sensor, but this also turns off the accelerometer. No landscape view switch on 90 degree turns. (I'm guessing losing this functionality would also affect Navigation if i tried it).
I also went back to stock 2.2, and did the OTA to 2.3.4 from an old nandroid backup. The problem of the screen going off during a call (as others have described above), still occurs. Starting to think its a hardware problem.
I have tried the following apps to turn the proximity sensor off, or, lock the screen on in phone calls - to no avail:
- Screen Suite
- Todds Droid Tools
- Screebl
- Flip it!
I made 2 folders on my SD Card for sensors.mahimahi.so.
/Sensors switch/sensors.mahimahi.so (contains the hex edited on that turns off Prox)
/Sensors original/sensors.mahimahi.so
My thinking was I could copy/paste the files into system/lib/hw depending on the day and my needs. Eg.: If I need to do a lot of phone calls that day requiring dialpad on, or even check my voicemail. However reverting back to the original file still keeps the phone's proximity sensor and accelerometer off'd, even after rebooting. A Nandroid backup is all that will restore this functionality. Hence that approach will not work.
NEways, at this point I'm thinking of doing an HTC repair. I want to know if they will still be able to provide me an N1 (credit card hold on charge...how much?...do they even have N1s?), while sending this one in for repair.
Incidentally, I don't think I will qualify for warranty as this phone has previous water damage. I replaced the screen because of it with an ebay one, but the prox sensor worked for a long time after that.
In general, I'm not sure if a $$ repair is worth it, but on the other hand I just bought a $500 phone in the N1 less than 6 months ago.
What to do...
bump.
What would you guys do? in this situation?
its too good a phone to just sell, even if it just does web/tethering/low profile/android apps awesome.
(i can always switch /sensors.mahimahi.so filez on the fly, worst case scenario. with nandroid restores in between(saving refurb monies)).
nm,
ghetto Romguest 2005 fix:
(hope this helps someone googling same said problem. which i've heard appears on faulty proximity sensors on Droid_1s, and Nexus'ses)
2 Nandroid backups:
1. With the original sensor file of system/lib/hw (in an SD card folder)
2. with the hex edited sensor lib/hw (in an SD card folder number 2)
Copy both respectively into your current rom, and nandroid both respectively into two nandroid versions.
On the days you need touchpad/dialpad, restore 2.
On the days you need landscape/gps/accelerometer, restore 1.
Problem solved, if no hardware warranty options available like me.
$190 saved.
Priceless..
PROGRESS ON THIS THING! )
Ok, so the last time I left this thread i was at the point of sending the phone in for an RMA. The reason I'm writing on this thread is in case someone on an android phone comes up with the Proximity sensor issue ( and it seems a lot of droid devices have this bug, whether its a hw failure like mine on the sensor, or not) ... then at least this thread will be here for the body of knowledge.
So just to summarize:
- hacking the sensor file mentioned above will disable the proximity sensor from working.
- having two nandroids of the proximity file (hacked and normal), will allow you to switch between normal phone (where the screen blanks), and proximity hacked phone (where the screen stays on in call, but never landscapes).
Is there an APK app to manually switch from Landscape to Portrait? Nope... there is code for it that devs can use to force their programs to run in a certain way, but not an on the fly solution.
'Screen Lock' , a program that comes closest simply locks the phone into Portrait.
What if you want to view a web page sideways then? Do you have to nandroid restore the original OS before the hack?
I just found out you don't. I ran Asphalt to see if it would run in portrait or landscape, and it ran in landscape surprisingly. So the portrait locked fone can be tricked in to landscape. woot
On exiting Asphalt, it keeps the phone in landscape
Goto web browser...browse all u want.
Want it back to portrait?
Go to Phone dialer, and it forces portrait. On exit, of fone, your home screen goes back to portrait.
Does proximity sensor off affect the GPS positioning? I'm not sure, it might - have to test.
Does the proximity sensor disabled, mean the accelerometer still works? No, the accelerometer doesnt work in this mode. ;P cant play Asphalt.
Why don't i just warranty my phone? ...I might. Its just that HTC doesnt send out replacement N1s anymore for the warranty period (with a Credit card debit), AND, my ASDF provider, doesn't give out loaners.
Hope this helps out anyone in the meantime!
Hope my GPS still works
UPDATE: Moving to a new phone.....
UPDATE:
So I decided to fold on my software fixes, and went for the Warranty route. Unfortunately HTC couldnt do the warranty themselves, and forwarded me to my Carriers reseller (not the private store I bought the phone from, but the Corporation who bought N1s in bulk from HTC, and sold them to my Carrier), which turned to be a one room office with a personal voicemail machine....
So I went to my Carriers corporate store, as they said they'd do the warranty. The CSR said that he's had people waiting >1 month for Nexus One replacements, with no idea what they'd replace it with. I would have to buy a phone too to use in the interim because they had not loaners.
His guess was that if the warranty might be accepted (mine may have not been a warranty cover because I changed the LCD once and stuff), I might get a Nexus S, or the next HTC phone they offered. All guesses, and all with a month long wait time with no smartphone, and $100 out for a secondary phone...in the interim.
So last night I tried a fix that worked for some Droid owners failed proximity sensor. It involves a rubber grommet set in place between the screen and the sensor, to let it "see" properly again.
No go. As well, my Camera and LED no longer work. (from before the fix attempt btw). Go figure.
So I folded, and bought the next best option for my Carrier, and AWS HTC Mytouch 4g. I decided to forgo Ebay, and buy off newegg, b/c there is some ambiguity into the quality of SLCD and Eeprom (?) chip you may get, so at least Newegg has great service.
I tossed around the idea of selling my N1 last night, but I won't. First too much hassle explaining to a buyer all these issues, and getting a worthy price. They could just Paypal revoke their payment when they get as pissed off with my particular fones lack of function as well.
I'm really going to miss the form factor of the N1 the most, and already am. I think I may wifi tether it to the Mytouch, and use it with Google voice or something.
Anyways, that is the end of my story. Wished I could keep the N1. Even tossed up buying a used N1 off ebay, for the form factor and hacking alone.
Related
I don't know what caused this.
I got my G1 today. It worked for probably 2-3 hours perfectly fine.
I had an app freeze (either Barcode Scanner or Lock 2.0) and had to do a full hard reset.
Now, whenever the phones screen darkens or I put it to sleep manually, it WILL NOT come back up.
I have factory reset three times now to try and get this to work.
When the screen is black, all buttons on the phone still light up and so does the LED indicator up top. I had my phone set to use a locking pattern screen at one point during one reset to test out and when the screen went black, I was still able to try and log in by doing my pattern. It unlocked, but still showed nothing on the screen.
Please help!
I've tried:
Turning Wi-Fi off
Turning 3g Off
Disclaimer: Yes, I've searched. I can find other users with the same problem but none of them seem to have a solution.
Phone is NOT ROOTED and has the factory ROM.
Update 1: Update: It only freezes/blacks out when I try to wake the phone from one of the front key buttons.
If I'm sliding to unlock, it seems to be fine.... (but if I've already tried to open from the front it doesnt)
Update 2: If I mash all the buttons in random orders for about a minute or two it seems to come back. Anyone have any idea?
Update 3: I'm thinking this has to be an issue with none of the buttons waking the phone up when closed. If I lock the phone with the "END" key, and then click the front "END" Key again, nothing happens. If I slide the phone open, and click it twice - the phone wakes up.
Update 4: Confirmed update 3. Phone will not unlock via front keys unless it's slid open (or open enough to trigger).
I would really, really appreciate help with this.
Hate to bump this, but I've added some detail on the top and bottom. Have to leave for work, hopefully someone might have an idea by the time I get back.
Well you can try to reload the factory rom or root it and try a custom rom and see if the problem still exist. If it is still happening then it would be a hardware problem and need to be sent in. And yes you will still be covered under warranty with HTC since the phone is still less than a year old.
I had a problem with exactly the same symptoms. It turned out that the SD card was cocked-up so home, core, and some other process would hang trying to read it and the phone would not wake-up the screen any more.
Did you try removing the SD card and seeing if that helps?
Karolis said:
I had a problem with exactly the same symptoms. It turned out that the SD card was cocked-up so home, core, and some other process would hang trying to read it and the phone would not wake-up the screen any more.
Did you try removing the SD card and seeing if that helps?
Click to expand...
Click to collapse
Removed the SD card and rebooted the phone.
No change ( still acts the same way ).
Did you factory reset after or was it an instant change?
I don't mind losing data to fix this.
supremeteam256 said:
Well you can try to reload the factory rom or root it and try a custom rom and see if the problem still exist. If it is still happening then it would be a hardware problem and need to be sent in. And yes you will still be covered under warranty with HTC since the phone is still less than a year old.
Click to expand...
Click to collapse
Wouldn't I have to root to reload the factory rom? Is there a rooting tutorial based just on that?
zeabrid said:
Wouldn't I have to root to reload the factory rom? Is there a rooting tutorial based just on that?
Click to expand...
Click to collapse
If you use the official update you don't have to have root. There are some links on here. I'll see if I can find it for you.
https://android.clients.google.com/updates/signed-gfh-CRB43-from-CRB21.c88b03d2.zip
That should be it, but can't confirm since I'm on my work computer.
Some thoughts--may be useful, or not:
Mine was doing that too, but it was caused because I dunked mine underwater during an urban exploring mission. I dried it out, replaced the LCD screen, and everything worked until it would go to sleep. Then I had to do a variety of button mashes and opening the keyboard to get it to come back to life. Sometimes it just wouldn't come back. The problem grew worse over time.
If wiping and reflashing (no need to use a stock ROM) gets you nowhere, then I would suspect a deeper hardware issue. I see you bought it used, can you contact the seller?
If you want to check for water damage, take out the battery and look at the tiny circular sticker in the battery chamber--if it is not white, it has been water damaged. (And the warranty will not be honored.)
Other Lesson: No urban exploring with G1s.
The link didn't work, btw.
derfolo said:
Some thoughts--may be useful, or not:
Mine was doing that too, but it was caused because I dunked mine underwater during an urban exploring mission. I dried it out, replaced the LCD screen, and everything worked until it would go to sleep. Then I had to do a variety of button mashes and opening the keyboard to get it to come back to life. Sometimes it just wouldn't come back. The problem grew worse over time.
If wiping and reflashing (no need to use a stock ROM) gets you nowhere, then I would suspect a deeper hardware issue. I see you bought it used, can you contact the seller?
If you want to check for water damage, take out the battery and look at the tiny circular sticker in the battery chamber--if it is not white, it has been water damaged. (And the warranty will not be honored.)
Other Lesson: No urban exploring with G1s.
Click to expand...
Click to collapse
Zero water damage.
That's great news zeabrid! In that case, I agree with an earlier poster--you should be covered by warranty. Wipe and flash a good rooted rom, and if that doesn't work, revert to stock and demand a new phone.
derfolo said:
That's great news zeabrid! In that case, I agree with an earlier poster--you should be covered by warranty. Wipe and flash a good rooted rom, and if that doesn't work, revert to stock and demand a new phone.
Click to expand...
Click to collapse
Do you have a link to a guide that teaches how to do this (with the stock rom)? I can only see a few that're spread out.
I'm not entirely sure my phone can boot into safe mode/disk mode, so we'll see about that.
Another update: When I boot into safe mode, the same problem exists.
Edit: Just emailed HTC.
This can officially no longer be considered a software issue.
I just rooted and installed a standard ROM. Same issue.
It happens all the way at boot now, just realized this.
HTC emailed me back and told me to call them directly. Will do that tomorrow.
if I find a solution I'll post it immediately.
Alright, my phone is officially ****ed.
Restored back to the original rom.
New problem now: When I close the screen, the backlight goes out and doesn't come back on. (I can still barely see everything, but there's no light).
Calling HTC today.
Edit: Called T-Mo support. They suggested deleting programs to free up space (I only have 2 downloaded and to reset (already done)
=(
Edit2: Called and placed a RMA with HTC after talking to two of their customer support reps. Thankfully, they forwarded me up the support tier after only about a minute with each person when they realized I had already tried all other steps.
The RMA process was surprisingly easy. I have everything set up, and when I get paid (tomorrow) I'm going to ship the phone out. I was given an estimation of 7-10 business days for full repair and return shipping (which sounds great in my opinion - I've never sent anything in for warranty work before).
I'll update you guys once I hear from their repair team on whether or not I'm going to be covered under warranty (I told them that the phone was a gift to me), and if not what the cost is going to be. Like I said earlier in the thread, all water damage indicators are clear and I have unrooted my phone, so I should be covered hopefully.
Thanks to anyone who posted in this thread.
zeabrid said:
Alright, my phone is officially ****ed.
Restored back to the original rom.
New problem now: When I close the screen, the backlight goes out and doesn't come back on. (I can still barely see everything, but there's no light).
Calling HTC today.
Edit: Called T-Mo support. They suggested deleting programs to free up space (I only have 2 downloaded and to reset (already done)
=(
Edit2: Called and placed a RMA with HTC after talking to two of their customer support reps. Thankfully, they forwarded me up the support tier after only about a minute with each person when they realized I had already tried all other steps.
The RMA process was surprisingly easy. I have everything set up, and when I get paid (tomorrow) I'm going to ship the phone out. I was given an estimation of 7-10 business days for full repair and return shipping (which sounds great in my opinion - I've never sent anything in for warranty work before).
I'll update you guys once I hear from their repair team on whether or not I'm going to be covered under warranty (I told them that the phone was a gift to me), and if not what the cost is going to be. Like I said earlier in the thread, all water damage indicators are clear and I have unrooted my phone, so I should be covered hopefully.
Thanks to anyone who posted in this thread.
Click to expand...
Click to collapse
Yea it defitenly sounds like a hardware issue and needs to be fixed. Glad your getting it fixed and you'll be covered no problem.
Do you know if they charge return shipping if it's covered under warranty? I have to pay my own shipping there, and they had me put a credit card down on file in case I either bail when its already there or they need to charge for repair.
zeabrid said:
Do you know if they charge return shipping if it's covered under warranty? I have to pay my own shipping there, and they had me put a credit card down on file in case I either bail when its already there or they need to charge for repair.
Click to expand...
Click to collapse
To be honest I don't know the answer but would like to say they would pay for it. But they would have to let you know of the charge before they apply a charge to a credit card.
wow its weird cause im just having a similiar issue now.. in landscape mode.. phone and back light work perfectly. but one i close the screen everything goes virtually blank, everything is running perfectly just the screen light wont turn on..
will try some of your previous methods.. hopefully it works on mine..=/
thanks, for the info zeabrid
Like many users my N1 isn't exactly perfect but I have putting up with it since day one (release day) since I like what the phone does when it does properly.
I have touch screen accuracy issues, mitigated somewhat by having a silicone case around the phone and using Swype and occasionally pressing the power button off and on to get it working again. My camera has a pinkish hue which HTC said I should try to remove by doing a factory reset. My wifi isn't exactly great with it taking often 30s or more to download a page on my home wifi and with the latest firmware, my GPS seems to be erratic.
The phone hardly ever can get a lock on the satellites when it's in the car on the dash which makes it pretty useless as a car GPS device but outside it seems to lock on okay. Occasionally if I an outside and get a lock, then take the phone in the car, it maintains a lock.
This was never great but got worse it seems with the latest firmware. The phone itself isn't rooted.
Reading the horror stories about refurbs and having to go through more than one I just wonder if getting a refurb is going to help me. I would go the send refurb to me first route so I wouldn't be without a phone during the swap and possibly send the refurb back if it wasn't working properly.
I presume it's highly unlikely that HTC has new units to send out now for warranty replacements?
What do folks think?
Since the last few days I've been getting some strange issues with my touchscreen. Sometimes parts of the screen (or the full screen) do not respond, and even the softbuttons are affected. When I take the phone out of my pocket, it either responds normally (I use pattern lock) or tries to use the emergency dialer or emergency contacts, and sometimes even tries to call a number from the emergency dialer (number 2 and luckily not 112..)
When in the launcher, it sometimes opens an app (like my calendar) and slowly scrolls either sideways or vertically. Turning the screen off and on again once or twice usually solves it for a (short) while.
I've already read some threads about it and ruled out the following causes:
The phone is not connected to any charger when this happens.
It still happens after cleaning the screen (just with a cloth, no liquids)
It still happens after disabling CPU Tuner. I didn't overlock the system, but used some custom power settings and different governors which apparently can also affect this behaviour.
The battery is still original since nowadays I prefer to use external chargers instead of buying a big battery for every new phone
The only things that changed recently are:
I installed the OwnCloud app, but that doesn't seem related.
We moved to another office building, in which the carpet generates more static electricity.
I gained some weight which may put a bit more pressure in my pant pockets than before
It started happening a few days ago, after using the .215 ICS leak for a few weeks without issue. I seem to get the problem less at home than I do at work, which makes me think it's either the static electricity or CPU governor (since battery percentage is lower by the time I get home again, so it might use a different governor). However, I've been using CPU Tuner for quite some time before this issue started, and the issue persists after disabling it.
So I am guessing it's any of the following causes:
Static electricity
Keeping the phone in my pant pockets which may put some pressure on the screen
A problem with the battery or screen somehow (moisture?)
Some other hardware issue
Some software issue
Does anybody have any tips or other ideas about this? Thanks in advance.
Edit: I enabled some development options to show touch pointer location (white dot) and trails. Screenshot added. Phantom touches seem to be focused in the bottom center part of the phone, which is probably around where I grap it when I take it out of my pocket. Trails usually disappear the next time you touch the screen, but in this case the trails kept growing / adding. I made some real swipes (upper half of the screen) and they 'stuck' without the phone responding to them (the application did not scroll) due to the parallel phantom touches in the bottom. In this case the phantom touches blocked my real input, in other cases they cause some behaviour (scrolling etc.). However, sometimes when the screen is not responding, there are no phantom touches visible in this display mode.
Edit 2:The no-touch input problem seems to be 'triggered' most of the time I open the keyboard. Sometimes this is followed by the phantom touches, but usually they start occuring in the portrait mode lock screen.
Sjaakbanaan said:
Since the last few days I've been getting some strange issues with my touchscreen. Sometimes parts of the screen (or the full screen) do not respond, and even the softbuttons are affected. When I take the phone out of my pocket, it either responds normally (I use pattern lock) or tries to use the emergency dialer or emergency contacts, and sometimes even tries to call a number from the emergency dialer (number 2 and luckily not 112..)
When in the launcher, it sometimes opens an app (like my calendar) and slowly scrolls either sideways or vertically. Turning the screen off and on again once or twice usually solves it for a (short) while.
I've already read some threads about it and ruled out the following causes:
The phone is not connected to any charger when this happens.
It still happens after cleaning the screen (just with a cloth, no liquids)
It still happens after disabling CPU Tuner. I didn't overlock the system, but used some custom power settings and different governors which apparently can also affect this behaviour.
The battery is still original since nowadays I prefer to use external chargers instead of buying a big battery for every new phone
The only things that changed recently are:
I installed the OwnCloud app, but that doesn't seem related.
We moved to another office building, in which the carpet generates more static electricity.
I gained some weight which may put a bit more pressure in my pant pockets than before
It started happening a few days ago, after using the .215 ICS leak for a few weeks without issue. I seem to get the problem less at home than I do at work, which makes me think it's either the static electricity or CPU governor (since battery percentage is lower by the time I get home again, so it might use a different governor). However, I've been using CPU Tuner for quite some time before this issue started, and the issue persists after disabling it.
So I am guessing it's any of the following causes:
Static electricity
Keeping the phone in my pant pockets which may put some pressure on the screen
A problem with the battery or screen somehow (moisture?)
Some other hardware issue
Some software issue
Does anybody have any tips or other ideas about this? Thanks in advance.
Edit: I enabled some development options to show touch pointer location (white dot) and trails. Screenshot added. Phantom touches seem to be focused in the bottom center part of the phone, which is probably around where I grap it when I take it out of my pocket. Trails usually disappear the next time you touch the screen, but in this case the trails kept growing / adding. I made some real swipes (upper half of the screen) and they 'stuck' without the phone responding to them (the application did not scroll) due to the parallel phantom touches in the bottom. In this case the phantom touches blocked my real input, in other cases they cause some behaviour (scrolling etc.). However, sometimes when the screen is not responding, there are no phantom touches visible in this display mode.
Edit 2:The no-touch input problem seems to be 'triggered' most of the time I open the keyboard. Sometimes this is followed by the phantom touches, but usually they start occuring in the portrait mode lock screen.
Click to expand...
Click to collapse
clean you phone with an air duster than a alcohol swab make sure you dry it quickly and use 72% not 90%. make sure you get the corners... get a screen protector and apply that as well. then sbf to 217... and wipe data,,,, that should work.
if not it could be the ribbon cable,,, it may be frayed...
how to fix
http://forum.xda-developers.com/showthread.php?t=1584260
where to get the part
http://cellphone-repair-shop.com/motorola-droid-4-lcd-screen/
myfishbear said:
clean you phone with an air duster than a alcohol swab make sure you dry it quickly and use 72% not 90%. make sure you get the corners... get a screen protector and apply that as well. then sbf to 217... and wipe data,,,, that should work.
if not it could be the ribbon cable,,, it may be frayed...
how to fix
http://forum.xda-developers.com/showthread.php?t=1584260
where to get the part
http://cellphone-repair-shop.com/motorola-droid-4-lcd-screen/
Click to expand...
Click to collapse
Thank you, let me try that. Couldn't find the right alcohol pct. so I'd have to use some generic screen cleaning liquid, would that be okay as well?
My screen was having issues too. So I turned the dot thing on from the dev part as well. The dot seems to freeze as I'm opening my keyboard. And the dot stays frozen in place until I close the scree again. Any ideas on how to fix it? Also if the screen is open and I touch a spot nothing happens, but then when I close the screen it will sense correctly where I touched while it was open.
Sounds like the same problem, so I'm getting the feeling it might be due to the connectors rather than the screen digitizer itself. After cleaning it, I didn't have any issues for a while, but they started occurring again now.
The replacement part is not available right now, a bit expensive, and excludes the price for the required tools which I don't have yet. Warranty may be tricky as I didn't get my phone from Verizon directly. So if it turns out to be a connector issue I will say goodbye to the Droid family and just get another non-QWERTY phone.. at least until Motorola starts selling them (as 'Milestone' since 'Droid' is a Verizon brand) in Europe again. The Droid 4 is the best phone I ever had, this is potentially making it unusable for me though. Glad I didn't order a Lapdock yet!
Motorola will repair your phone for 168... out of warranty and all... I found this cheaper and easier then fixing it myself and guaranteed done right in 5-7 days..
Sent from my DROID4 using xda app-developers app
Mine is still within the one year warranty. So I want to send it in. But I'm afraid they will check for the root stuff and they will consider voiding my warranty because I was rooted. I unrooted and did a factory reset to see if it would fix the issue. So this is my only chance left. I heard clearing the data wouldn't remove the qe process they use to know that I'm rooted. So I'm not sure if its worth the chance.
Flash SBF restores everything to my knowledge. No way to see what happened before the SBF flash.
I read in the original post for the DROID 4 ICS root tool that a sbf will not remove the part that says you were rooted at one point. I checked that first. An sbf flash is really easy. I was really hoping that it would work.
they dont take the time to check that stuff... if you sbf they wont know a thing...
bty found what u need on the cheap
Motorola DROID 4 XT894 Flex Cable Ribbon 27$
http://www.ebay.com/itm/Motorola-DROID-4-XT894-Flex-Cable-Ribbon-/150849219594
If they don't check it then why should I even bother? Does an sbf change something a factory reset doesn't? I've already reset it. I'll look into the fix though. It will depend on if I have the tools to do it or not.
SBF/fastboot will revert rom changes.
About that ribbon cable how would that work as the lcd is fused to the cable?
The Old One said:
SBF/fastboot will revert rom changes.
About that ribbon cable how would that work as the lcd is fused to the cable?
Click to expand...
Click to collapse
Cant be... it is glued in place and has connectors... how else could he sell you the cable by itself... http://www.ifixit.com/Teardown/Motorola-Droid-4-Teardown/7759/1
Just to weigh in on the whole root checking thing, SBFing or fastbooting back to stock DOES NOT remove evidence of root. qe still picks it up somehow in stock recovery.
That being said, they cannot void your hardware warranty for software modifications, it's the law (in the U.S.)
Of course, if you somehow softbrick your phone, they have no obligation to help you.
Edit: Just to clarify, I tried this myself just this morning. Full SBF back to stock + a factory reset, and qe shows 0/1, which indicates currently unrooted but previously rooted. No idea how their security works, but it does.
podspi said:
Just to weigh in on the whole root checking thing, SBFing or fastbooting back to stock DOES NOT remove evidence of root. qe still picks it up somehow in stock recovery.
That being said, they cannot void your hardware warranty for software modifications, it's the law (in the U.S.)
Of course, if you somehow softbrick your phone, they have no obligation to help you.
Edit: Just to clarify, I tried this myself just this morning. Full SBF back to stock + a factory reset, and qe shows 0/1, which indicates currently unrooted but previously rooted. No idea how their security works, but it does.
Click to expand...
Click to collapse
your right but most ppl dont inspect the phone that hardcore... it takes time, and time is money
Yes
Sent from my DROID4 using xda premium
myfishbear said:
your right but most ppl dont inspect the phone that hardcore... it takes time, and time is money
Click to expand...
Click to collapse
I agree it's probably not anything most people need to worry about... I still plan on sending my D4 in before the warranty is up, I've been having terrible wifi + 4G drops, even on stock (that's why I fastbooted in the first place)
I am a bit nervous though, because I've heard horror stories about Moto replacements. That being said, if Ops phone is under warranty, I'd send it in rather than trying to repair it. If it isn't under warranty, then I'd go for the flex cable, the Moto phones are built well and reasonably easy to work on.
Sent from my Galaxy Nexus using xda app-developers app
I probably have some kind of warranty with the seller, not with Moto directly as I have no way of obtaining a QWERTY phone from them (they don't sell those in Europe for some reason). But I really can't miss my phone for an extended period of time, so I'd either need to switch to an old one while I'm waiting, or get a new one.
Since I don't have the tools available to open the phone properly and I don't want to spend any more money on this thing, I'll probably sit it out until it breaks. For now, switching the screen on and off one or two times seems to 'solve' it.
Sjaakbanaan said:
I probably have some kind of warranty with the seller, not with Moto directly as I have no way of obtaining a QWERTY phone from them (they don't sell those in Europe for some reason). But I really can't miss my phone for an extended period of time, so I'd either need to switch to an old one while I'm waiting, or get a new one.
Since I don't have the tools available to open the phone properly and I don't want to spend any more money on this thing, I'll probably sit it out until it breaks. For now, switching the screen on and off one or two times seems to 'solve' it.
Click to expand...
Click to collapse
all u need is a $0.60 guitar pic and a t5 screwdriver(can find at home improvement store). none of those silly tools they try to sell you help that much
myfishbear said:
all u need is a $0.60 guitar pic and a t5 screwdriver(can find at home improvement store). none of those silly tools they try to sell you help that much
Click to expand...
Click to collapse
I still have tons of guitar picks so I just ordered a Torx set for this and future problems.. hope that pushing the connector around a bit can solve it already.
My M9 won't auto rotate the screen any more. Tried reboot. Toggling the setting, tried calibrating the g-sensor in display settings. When calibrating, the vertical level moves, but the horizontal does not budge. If I open G maps, right away it asks me if I meant to shake my device, and therefore initiate "feedback". I didn't even move the phone at ALL.
I am stock and havent had the phone past 30 days. Any ideas before I head back to T-Mobile?
Pretty much same thing happening to me, I work as a tech for Sprint and I noticed none of my motion launch gestures working. Co worker told me to run the hardware diagnostics, G-sensor failed. No motion gestures work, screen orientation doesn't change, nada. About to order a replacement device, but facing the dilemma of having a brand new phone <30 days owned, and having to order a refurb device. Kinda bummed.
Same issue, Have had my VZ M9 for 6 weeks. While i was using it, no less, G sensor failed, no rotate. Tried everything i can find to fix including resets of G-Sensor, recalibrate on board diagnostics, Boot to bootloader and reset to factory( complete wipe). etc...
Called HTS tech support. they took my info and said a supervisor would call back, never did. called back and online tech "could not contact supervisor" said my only warranty options were replace with refurb in 10-20 days after they receive my bad one, or have $500 hold on credit card for advanced replacement MINUS CHARGES FOR REPAIR or REPLACE, AT THEIR DISCRETION, WITH NO CHALLENGE BY ME.
So basically tough luck too bad so sad..Refurb with 90 day warranty or nothing.
UH OH policy only counts for "damaged" phone, not warranty issues...
caveat emptor..
Hey all,
I have had my Z3 Compact since its release back in 2014 and it has seen some horrors. I once dropped it from the third floor of a building to the ground floor (luckily survived with screen in tact but with the back glass shattered), the USB port has long been dysfunctional as well as my earphone jack as I trusted Sony waterproof claim and took it along one of my swimming routine, some parts of my screen's adhesive came off so I can lift my screen a bit and (probably) because of this my proximity sensor is broken (it always thinks there is something close to the sensor).
I took my phone to an after service centre recently and was told that fixing all of its problems will cost more than the original price of the phone and so I am left with no choice but to use it as it is; I don't mind it because I am rather fond of this little phone. And I'm lucky that there is the magnetic port from where I can charge my phone with Sony's dock.
There is, however, one thing that I want to fix - the proximity sensor. I would like to turn it off completely as whenever I am in a call, I have to wait for the other person to hang up as the screen is black no matter what physical keys I press as the proximity sensor thinks there is something close to the phone whenever it is turned on.
Sony's stock call app does not have an option to disable it and I have tried various 3rd party apps with no luck. So my current plan is to root it and use Xposed mod to turn the sensor off. But I am obviously stuck because my USB jack is faulty.
So my question is, is it possible to root using only the phone itself? (From my basic knowledge of rooting, I am assuming that the answer is no, but I still want to try my luck)
ghlrobin said:
Hey all,
I have had my Z3 Compact since its release back in 2014 and it has seen some horrors. I once dropped it from the third floor of a building to the ground floor (luckily survived with screen in tact but with the back glass shattered), the USB port has long been dysfunctional as well as my earphone jack as I trusted Sony waterproof claim and took it along one of my swimming routine, some parts of my screen's adhesive came off so I can lift my screen a bit and (probably) because of this my proximity sensor is broken (it always thinks there is something close to the sensor).
I took my phone to an after service centre recently and was told that fixing all of its problems will cost more than the original price of the phone and so I am left with no choice but to use it as it is; I don't mind it because I am rather fond of this little phone. And I'm lucky that there is the magnetic port from where I can charge my phone with Sony's dock.
There is, however, one thing that I want to fix - the proximity sensor. I would like to turn it off completely as whenever I am in a call, I have to wait for the other person to hang up as the screen is black no matter what physical keys I press as the proximity sensor thinks there is something close to the phone whenever it is turned on.
Sony's stock call app does not have an option to disable it and I have tried various 3rd party apps with no luck. So my current plan is to root it and use Xposed mod to turn the sensor off. But I am obviously stuck because my USB jack is faulty.
So my question is, is it possible to root using only the phone itself? (From my basic knowledge of rooting, I am assuming that the answer is no, but I still want to try my luck)
Click to expand...
Click to collapse
If someone reply's to your question quoting Kingingroot, then ignore them, that's not really helpful.
Not unless you want all your phone information (including IMEI number) sent to an unknown server in China and probably cloned. Then be left with a phone that struggles to have normal SuperSU installed and has some unknown apks running on it, in the background...
Edit: There's a heap of 'how to' videos out there, why not replace the screen yourself ? $80 for genuine screen on ebay or $40 for a copy.
There is a workaround for proximity sensor on lollipop, but it's not working on marshmallow caller. Check my post
http://forum.xda-developers.com/z3-compact/help/d5833-6-0-1-23-5-0-570-call-proximity-t3371803
ghlrobin said:
So my question is, is it possible to root using only the phone itself? (From my basic knowledge of rooting, I am assuming that the answer is no, but I still want to try my luck)
Click to expand...
Click to collapse
Yes, I had this exact issue and wrote a guide for getting root and recovery which will then let you flash a pre-rooted rom
http://forum.xda-developers.com/crossdevice-dev/sony/guide-how-to-root-custom-recovery-t3325775