EP121 users, I did a fresh install of the RP tonight. I actually stepped away for a while and when I came back I got a message "Auto Rotate Locked". So yes, rotation is working, volume, Windows button, all of it. Thought I would share
Related
my mistake, please delete! moved here
TF101
Stock Android 3.2.1
Im getting this wierd screen thing going on. Anyone seen this or possibly have a solution?
When I tap the screen it comes back on... If I keep taping it, it eventually stays on, untill I put it in the dock or remove it from the dock, or tap the screen again.
i was trying to update my acer with the V4 program from here: http://forum.xda-developers.com/showthread.php?t=1307539 to try to root it and i left my computer and the tablet on while i went and did something for 30 min because it was updating and when i came back my computer was off and my tablet was on the acer screen. i ended up turning it off and now when i turn it on the power light comes but it doesn't vibrate and the screen doesnt come on.
Can anyone help me?
mdillard1992 said:
i was trying to update my acer with the V4 program from here: http://forum.xda-developers.com/showthread.php?t=1307539 to try to root it and i left my computer and the tablet on while i went and did something for 30 min because it was updating and when i came back my computer was off and my tablet was on the acer screen. i ended up turning it off and now when i turn it on the power light comes but it doesn't vibrate and the screen doesnt come on.
Can anyone help me?
Click to expand...
Click to collapse
Looking at TimmyDeans thread, and in the instructions, it says, if it doesn't succeed the first time around, to repeat the process.
I hope you wrote that UID number down, just in case.
I have never used it, but, from what I have read in the thread, it is better to use a Win7 PC, rather than XP. Also, when you start the app, as with most Linux and Java, it is better to "right" mouse click the application file, and select "run as administrator".
Additionally, you may want to post this also, in TimmyDeans's thread as well.
Anyhow, I believe he says to restart both the PC and Tab, and start the process again. From what some users said, it may take several times.
I'll preface by saying I am an IT professional for work so this is no noob request.
So, this all started with my capacitive buttons acting up. I have CWM (tripped knox), SlimROM. What was happening was when my capactive buttons were lit and then would dim... whenever I'd press ANYWHERE on the screen (with the capactive buttons dimmed), it would press the back button for me. Made no sense to me, sounds weird I know. Never got around to trying to flash a new rom or anything, just ended up permanently having the buttons dimmed.
Fast forward a few days... in my car in the cupholder, spilled energy drink where my phone was sitting in cup holding. Probably only an inch high or so with my phone upside down (home button to the sky), so the charging port side was safe. That day is when it went south. I'd hit the power button on, screen would come on. Power button off and on again, screen would not go on (but capactive buttons WILL light up, and digitizer works and you can hear the audio). Off and on again, maybe came on. Intermittent. Put in rice for 36 hours. Same thing. Note that when the screen IS on it is perfectly fine and usable (the capacitive button problem is gone now too....). I set the display to turn off after 30 minutes of inactivity. It's been on for like 10 right now and hasn't flickered or nothing. It's just if I turn the phone off, and back on, chances are it will not come back on (but capacitive buttons always light and touch screen and audio still works). It seems to only come on when it's been left for a while. Like if I turned it off now, and went off/on/off/on/off/on it would probably stay black until i left for 10 minutes and then might fire on.
My Note 3 model is SM-N900W8 (Canadian TELUS). Behind the battery there is a speck of a circle that is pink looking. Unsure if this is a Liquid Damage Indicator. Another CLEAR liquid indicator on the top left when case is off is clearly white, the LDI on the battery is white. Had a hard time finding image that shows the LDI's. Anyway, KNOX is tripped. As far as I've researched I cannot change this. I do have a CWM image of the stock Samsung firmware. But, there is no point in going through warranty at this point (phone IS under warranty though) unless I can revert KNOX, and confirm the LDI's are all white......
I am thinking this would be a relatively easy hardware fix though. Everything seems to work perfectly fine if the screen IS on. It's just the screen getting on being finicky.....
Any suggestions?
Currently getting all data off, and then will try flashing another firmware etc. but this really seems like a hardware issue.....
Thanks for any advice!
brockmo said:
I'll preface by saying I am an IT professional for work so this is no noob request.
So, this all started with my capacitive buttons acting up. I have CWM (tripped knox), SlimROM. What was happening was when my capactive buttons were lit and then would dim... whenever I'd press ANYWHERE on the screen (with the capactive buttons dimmed), it would press the back button for me. Made no sense to me, sounds weird I know. Never got around to trying to flash a new rom or anything, just ended up permanently having the buttons dimmed.
Fast forward a few days... in my car in the cupholder, spilled energy drink where my phone was sitting in cup holding. Probably only an inch high or so with my phone upside down (home button to the sky), so the charging port side was safe. That day is when it went south. I'd hit the power button on, screen would come on. Power button off and on again, screen would not go on (but capactive buttons WILL light up, and digitizer works and you can hear the audio). Off and on again, maybe came on. Intermittent. Put in rice for 36 hours. Same thing. Note that when the screen IS on it is perfectly fine and usable (the capacitive button problem is gone now too....). I set the display to turn off after 30 minutes of inactivity. It's been on for like 10 right now and hasn't flickered or nothing. It's just if I turn the phone off, and back on, chances are it will not come back on (but capacitive buttons always light and touch screen and audio still works). It seems to only come on when it's been left for a while. Like if I turned it off now, and went off/on/off/on/off/on it would probably stay black until i left for 10 minutes and then might fire on.
My Note 3 model is SM-N900W8 (Canadian TELUS). Behind the battery there is a speck of a circle that is pink looking. Unsure if this is a Liquid Damage Indicator. Another CLEAR liquid indicator on the top left when case is off is clearly white, the LDI on the battery is white. Had a hard time finding image that shows the LDI's. Anyway, KNOX is tripped. As far as I've researched I cannot change this. I do have a CWM image of the stock Samsung firmware. But, there is no point in going through warranty at this point (phone IS under warranty though) unless I can revert KNOX, and confirm the LDI's are all white......
I am thinking this would be a relatively easy hardware fix though. Everything seems to work perfectly fine if the screen IS on. It's just the screen getting on being finicky.....
Any suggestions?
Currently getting all data off, and then will try flashing another firmware etc. but this really seems like a hardware issue.....
Thanks for any advice!
Click to expand...
Click to collapse
So how did it go?
I would just bring it to repair, it's better to lose a hundred canadian (send to repair or fix yourself) than to bear with a broken phone that doesn't sleep properly.
Test the proximity sensor and ambient light sensor.... If you have any "pocket mode" or active display features active in your rom try disabling those... Sounds like your warranty is definitely void but you could take it to a local independent shop if samsung wants too much to fix it.
Good luck!
Sent from my SM-T320 using Tapatalk
nicholaschum said:
So how did it go?
I would just bring it to repair, it's better to lose a hundred canadian (send to repair or fix yourself) than to bear with a broken phone that doesn't sleep properly.
Click to expand...
Click to collapse
Since I cannot stand when I research an issue, finally find someone with the same question and turns out there was never a resolution response, I am going to say that much to my shock, reflashing to my stock Samsung TouchWiz nandroid fixed the issue. I then clean flashed the latest SlimROM and all is well. I had dirty flashed to the latest (stable) SlimROM 4.4.4 and it worked fine for weeks which is why I had little to no faith a reflash would fix. Especially since the screen would be blacked out during the boot screens. That is baffling to me. A custom ROM/kernel should have no effect prior to the ROM booting should it? I guess I am wrong on that? Regardless, happy I did not have to work around the KNOX being triipped....
brockmo said:
Since I cannot stand when I research an issue, finally find someone with the same question and turns out there was never a resolution response, I am going to say that much to my shock, reflashing to my stock Samsung TouchWiz nandroid fixed the issue. I then clean flashed the latest SlimROM and all is well. I had dirty flashed to the latest (stable) SlimROM 4.4.4 and it worked fine for weeks which is why I had little to no faith a reflash would fix. Especially since the screen would be blacked out during the boot screens. That is baffling to me. A custom ROM/kernel should have no effect prior to the ROM booting should it? I guess I am wrong on that? Regardless, happy I did not have to work around the KNOX being triipped....
Click to expand...
Click to collapse
That's so strange, but congratulations on fixing it.
You should have a boot animation with any ROM you flash, just remember to check your MD5's to the developer's MD5's after you download.
Please pardon if this is a duplicate thread. I looked all the way back to July '15, but didn't find anything similar... Apologize in advance for the long intro, but want to give as much background as possible to see if anyone can help find a solution. I have several Galaxy Tab4 8.0 tablets (model SM-T337V). When purchased, they were running Android 4.4.4. I enrolled them in an MDM environment (SOTI MobiControl) and everything was working fine. Through the MDM software, I was using a custom lock screen, which I believe Samsung calls kiosk mode, and had selected the option to NOT allow factory resets. When Android 5.1.1 (pretty sure) came out, it prompted tablet users to upgrade, which several did before I was able to intervene. When those tablets were upgraded to the new OS, it became incompatible with the version of MDM that was installed (v11.02). Now, the tablets will boot, but after swiping the home screen, I just get a black screen, and a dialog box that reads "Unfortunately, MobiControl has stopped" repeatedly comes up. I can't get to the settings or anything, due to the settings of the MDM software. I can get into the "recovery booting" screen by holding the home/volume up/power buttons to turn on. Get the full menu, but cannot do a factory reset due to the settings held by the MDM software. If I connect to a PC via USB cable, I can see the device, but cannot get to any of the system files to remove the MDM software. I'm hoping that someone will know of a way to get into the device and bypass the old MDM settings so that I can reset and use the tablets again. Please let me know if there is any other information you may need to assist.
Thanks for the help!!
JeffG
Booting into safemode disables 3rd party apps,
for your device, it should be the following;
power off device
poweron device, as soon as you see the samsung bootsplash press and hold down the volume down button,
you will know if you did it correctly when you see safe mode at the bottom left of the screen and a notification in drawer,
if that does the trick, after you remove the offending software, pull down and click on the safemode notification.
m
Thanks for the quick reply!! Well, the first one, I must have held the volume-down button too soon. It stopped booting at the red Verizon screen and won't do anything else. The second two, I held the volume-down at the colorful Samsung splash. Am getting a dialog box that says "Android is starting..." with moving circle and "Starting apps.", but, again, no further bootup.
JeffG
Ok, so I bought a third hand T580 2016 and seller explained that screen can blink and screenshot sound could be heard.
I got it cheap, so I figured I could try this disconnecting the battery and screen flat cables... but even after 3-4 attempts this doesn't work.
It's really annoying because somehow I managed to activate voice assistant and screen responds to tapping.
Assistant said that it was in Samsung Setup, but also something about an unauthorized installation attempt.
Finally I managed to turn it off and enter download mode, so I flashed the latest stock firmware + pit with repartition and according to Odin all went well.
I haven't tried anything after that because the battery was down on 14% so I'm charging it at the moment.
Anyone here with this kind of fault?
The screen does flash rapidly as to turn on, but then goes black...
Edit:
I forgot... my pc sees the tab, but shows empty of course since it's not "opened" or MTP isn't activated only charging or something like that
After further testing and googling I've decided to order a new LCD...
I will try to reuse the outer touchscreen as it's in a reasonable shape.
Someone must have tried the cable tricks before me because all securing tape was removed.
Edit:
Seems like Voice assistant is activated by pressing both Vol + and - together with Power.
This time she talks about exploring the icons... double tap on Home was the Accessability shortcut.
Funny... nothing about Unauthorized installation and nothing about Setup.
Apparently no lockscreen(?)