[Q] major problem - Galaxy Tab 4 Q&A, Help & Troubleshooting

Hi all,
I have a major problem with my Samsung galaxy tab 4. When I power on the tab sometimes it will hang on the splashscreen.
Then if and when I get through the frozen splashscreen the screen will flicker extremely badly, almost like interference and will freeze.
I done a factory reset, disconnected the battery, still the same issue.
Any ideas what the issues are?
Thanks in advance

skalicioustimes said:
Hi all,
I have a major problem with my Samsung galaxy tab 4. When I power on the tab sometimes it will hang on the splashscreen.
Then if and when I get through the frozen splashscreen the screen will flicker extremely badly, almost like interference and will freeze.
I done a factory reset, disconnected the battery, still the same issue.
Any ideas what the issues are?
Thanks in advance
Click to expand...
Click to collapse
I would find the correct firmware for your tab (from the Samsung site) and reflash the full Odin tar. If that doesn't help I'd contact Samsung about the issue.

Is there any point in getting in touch with Samsung after opening the tablet up?
There is horizontal and vertical lines approximately 5mm apart, coloured.
I can see the logo behind these lines but and the whole system has frozen.
This still happens after a factory reset which makes me think it may be a hardware issue.
Would it be a digitizer issue?

skalicioustimes said:
Is there any point in getting in touch with Samsung after opening the tablet up?
There is horizontal and vertical lines approximately 5mm apart, coloured.
I can see the logo behind these lines but and the whole system has frozen.
This still happens after a factory reset which makes me think it may be a hardware issue.
Would it be a digitizer issue?
Click to expand...
Click to collapse
That would be your display, not your digitizer. since you're thinking of opening the tab, check the connector
to the board from the display screen, just be patient, steady handed, and keep a light touch.
use a magnifying glass of you can't see the layout clearly, the connector may be seated wrong/crooked
there should/may be clips on either side that need to be slid out before disconnecting the ribbon.
I would get a replacement if you haven't opened the tab already.
questions belong in q&a. :good:
m
just a thought, check for moisture/corrosion anywhere, at the point you open the device, you're pretty
much S.O.L. but hey.

Yes unfortunately the Tab 4 has been opened.
By disconnecting and reseating the battery sockets i believe the warranty is void. The back has been opened.
I find if i get the device running momentarily then by gently plexing "twisiting" the unit in my hands can cause the screen to switch back to normal.
But soon after the dreaded horizontal and vertical lines appear then the device becomes frozen again, the intermitent lines jump around the screen with whatever is in the background leaving the display frozen.
Only solution is to gently open up the device and disconnect the battery and then reconnect again.
This is only a temporary solution as the problem reappears very soon after.

moonbutt74 said:
That would be your display, not your digitizer. since you're thinking of opening the tab, check the connector
to the board from the display screen, just be patient, steady handed, and keep a light touch.
use a magnifying glass of you can't see the layout clearly, the connector may be seated wrong/crooked
there should/may be clips on either side that need to be slid out before disconnecting the ribbon.
I would get a replacement if you haven't opened the tab already.
questions belong in q&a. :good:
m
just a thought, check for moisture/corrosion anywhere, at the point you open the device, you're pretty
much S.O.L. but hey.
Click to expand...
Click to collapse
So you reckon it is not the digitizer that has failed? I was thinking of replacing that.
Hmmm..

skalicioustimes said:
So you reckon it is not the digitizer that has failed? I was thinking of replacing that.
Hmmm..
Click to expand...
Click to collapse
I'm not so sure after what you said about twisting the tab, can you get into the system through adb ?
After the tab "freezes" hook up to your comp and get adb shell running, run any/all of the following
logcat -d
mount
ps
dmesg
and do some directory hopping to see what you can access, reason being we narrow it down to display/digitizer/something loose on board.
just to refresh my memory, the same behavior occurs in recovery ?
also tap your power button to screen-off/lock.
and at the end after adb test, force reboot to recovery with button combo.
m

moonbutt74 said:
I'm not so sure after what you said about twisting the tab, can you get into the system through adb ?
After the tab "freezes" hook up to your comp and get adb shell running, run any/all of the following
logcat -d
mount
ps
dmesg
and do some directory hopping to see what you can access, reason being we narrow it down to display/digitizer/something loose on board.
just to refresh my memory, the same behavior occurs in recovery ?
also tap your power button to screen-off/lock.
and at the end after adb test, force reboot to recovery with button combo.
m
Click to expand...
Click to collapse
I'm unsure about your suggestions, as i don't know were to locate those commands.
I have done a factory reset, so i am just waiting for the device to charge before attempting to load new firmware through Samsung Kies which i downloaded through this link... http://www.samsung.com/uk/support/usefulsoftware/KIES/#versionInfo
are the commands you suggested within the Samsung Kies software?

ahh, no. You need to run adb on windows [ewww]
or adb on linux [yay!]
can't help you with windows.
but what about in recovery ? did you encounter the same issue or no ?
m

moonbutt74 said:
ahh, no. You need to run adb on windows [ewww]
or adb on linux [yay!]
can't help you with windows.
but what about in recovery ? did you encounter the same issue or no ?
m
Click to expand...
Click to collapse
When i was having the problems initially, i could not for the life of me get into recovery mode using the button combo's. Eventually i did get into recovery, so as a last resort i cleared cache, and done a factory reset. Now it is booting up as normal but i was going to use Kies on windows to see if it is a software issue.
So were do i go about getting
adb
logcat -d
mount
ps
dmesg.
And what would you suggest as a step by step guide from were i am at now?
Note: i haven't physically messed with the device to see if the Horizontal and Vertical screen issue is still there.
Thanks

XDA search bar
adb install

moonbutt74 said:
XDA search bar
adb install
Click to expand...
Click to collapse
i tried running adb but i'm getting unaturiosed, clicked on the revoke debugging and then adb just ran through all the commands.
then the device screen problem has arisen again and i can't get it to boot.

skalicioustimes said:
i tried running adb but i'm getting unaturiosed, clicked on the revoke debugging and then adb just ran through all the commands.
then the device screen problem has arisen again and i can't get it to boot.
Click to expand...
Click to collapse
You're not supposed to revoke adb debugging.
Look, i'm at a loss, the thing is, do you blow more cash on a quess, or cut your losses.
As to learning how to use adb, XDA searxh box, using adb.
m

not a bother.
thanks for your help :good:

skalicioustimes said:
not a bother.
thanks for your help :good:
Click to expand...
Click to collapse
Hi,
you're not bothering me, i'm just saying you have to jump in all the way. :good:
m

moonbutt74 said:
Hi,
you're not bothering me, i'm just saying you have to jump in all the way. :good:
m
Click to expand...
Click to collapse
ah i understand, it's just it's driving me crazy. a bit like a crossword puzzle that i can't finish and i'm looking for someone to give me the answer without me having ta look up the answer in a dictionary....hahaha.
i suppose i am looking for someone who had a similar problem, a few clicks here and there

skalicioustimes said:
ah i understand, it's just it's driving me crazy. a bit like a crossword puzzle that i can't finish and i'm looking for someone to give me the answer without me having ta look up the answer in a dictionary....hahaha.
i suppose i am looking for someone who had a similar problem, a few clicks here and there
Click to expand...
Click to collapse
dude are you on hangouts ? if so pm me.

moonbutt74 said:
dude are you on hangouts ? if so pm me.
Click to expand...
Click to collapse
sent you a message on hangouts. thanks

Flashed the stock kernel using Odin, i hope that gets rid of the screen issue :fingers-crossed:

Well 3 hours later and the Tab is going good
My daughter is delighted that it's sorted and she hopes it stays that way
Many thanks to Moonbutt74 for your time and effort, it's very much appreciated.
Would you say that it's good to go? And is there anything else i need to do to the device before handing it over to her?
Cheers

Related

Something strange has heppened with my Nook touch

Hi everybody! so there is serious problem with my NST...
My nook doesn't boot - I get only screen with floating points(it can longs for hours)...
I haven't root my device, only installed last update(it worked great for a month after this)
So the story how I get this:
I put my nook in my backpack(nook was in sleeping mode) and take it with me... it was in my backpack whole day and in the evening when i took it i saw floating points...
Already tried to restore factory image, procedure goes well but it doesn't help...
So any ideas what i have to do next?
Thank's everbody for answers!
P.S. Sorry for my poor English
Are the points moving (I assume because you say floating)? Sounds like a screen problem but without ADB can't say for sure, because that way could take screenshot and see what is going on in the software.
tazzix said:
Are the points moving (I assume because you say floating)? Sounds like a screen problem but without ADB can't say for sure, because that way could take screenshot and see what is going on in the software.
Click to expand...
Click to collapse
yeah, points are moving, and from time to time screen is refreshing... don't know how to take screenshots, device is not rooted so ADB is not awailable, shoud i root it?
Thank's everybody for reading this topic, I already have solved my problem...
I simply erase settings and user data by pressing lower scrolling buttons and power button, when device was turned all... now everything fine
CAn you take a picture of it?
3-finger-press and hold: n, power, and one or two of the front buttons. This made mine reboot and got me out of a similar situation.
Good luck. A reboot will allow you to boot from SD.

Black Shroud of Death

FML! I went ahead and did it! I mentioned that I hadn't had an SOD or reboot since ICS and now enraged the gods of karma and pulled down on myself a wrath unlike any other!
Yes, I have a problem that I call the Black Shroud of Death. Using transformer and the backlight goes out. I click the power on and I see the backlight go on but I don't see anything on the screen. Hmm, figure that I must have gotten my first SOD or maybe a misbehaving app is FC'ing. So I reboot, the ASUS logo flashes a bunch of times and then it goes to a black screen...backlight is still on though. It never "seems" to boot. I reboot a couple of times and it repeats the same process.
Then something odd happens, when playing with the power and volume keys I notice the lock screen for a second appears. Playing around more and suddenly I see the lock screen BUT only if I hold the volume keys. So, it IS booting but for some reason, the display is unable to show graphics. The backlight is on too so it's not a backlight issue.
I am able to unlock and I start disabling settings(I'm on Megatron) in hopes to hit on the cause of this issue. I release the keys and I'm back to the Black Shroud again! If I'm lucky, I can make it reboot into recovery where I don't need to hold keys to see options.
I tried downgrading to a different GAPPS version as I had previously upgraded and wanted to see if that's the problem. While it boot, the typical gapps upgrade screens were flashing like crazy.
I tried reflashing my ROM but that didn't seem to do anything.
My guess is that I need to completely power down and clear out some bad crap in the video memory. I opened the back of the unit but couldn't figure out how to pull the battery cable. I did manage to ruin some plastic clips on the bottom or something, so yeah the less than perfect bottom fit is now fun. So, my next step is to let it power down, charge it up and see what happens.
Any advice...other than don't enrage the Gods?
Skyeclad said:
FML! I went ahead and did it! I mentioned that I hadn't had an SOD or reboot since ICS and now enraged the gods of karma and pulled down on myself a wrath unlike any other!
Yes, I have a problem that I call the Black Shroud of Death. Using transformer and the backlight goes out. I click the power on and I see the backlight go on but I don't see anything on the screen. Hmm, figure that I must have gotten my first SOD or maybe a misbehaving app is FC'ing. So I reboot, the ASUS logo flashes a bunch of times and then black screen...backlight is still on though. It never "seems" to boot. I reboot a couple of times and it repeats the same process.
Then something odd happens, when playing with the power and volume keys I notice the lock screen for a second appears. laying around more and suddenly I see the lock screen BUT only if I hold the volume keys. So, it IS booting but for some reason, the display is unable to show graphics. The backlight is on too so it's not a backlight issue.
I am able to unlock and I start disabling settings(I'm on Megatron) in hopes to hit on the cause of this issue. I release the keys and I'm back to the Black Shroud again! If I'm lucky, I can make it reboot into recovery where I don't need to hold keys to see options.
I tried going down to a different GAPPS version as I had previously upgraded and wanted to see if that's the problem. While it boot, the typical gapps upgrade screens were flashing like crazy.
I tried reflashing my ROM but that didn't seem to do anything.
My guess is that I need to completely power down and clear out some bad crap in the video memory. I opened the back of the unit but couldn't figure out how to pull the battery cable. I did manage to ruin some plastic clips on the bottom or something, so yeah the less than perfect bottom fit is now fun. So, my next step is to let it power down, charge it up and see what happens.
Any advice...other than don't enrage the Gods?
Click to expand...
Click to collapse
Sorry, this post isn't going to help, but I literally laughed out loud when I saw
Skyeclad said:
FML! I went ahead and did it! I mentioned that I hadn't had an SOD or reboot since ICS and now enraged the gods of karma and pulled down on myself a wrath unlike any other!
Click to expand...
Click to collapse
in the preview of the post. Lol
Maybe I should delete my original Karma-Killing post as a start.
Well, it certainly doesn't sound like a software issue to me. I would exchange it for another.
a.mcdear said:
Well, it certainly doesn't sound like a software issue to me. I would exchange it for another.
Click to expand...
Click to collapse
It might not be software but I can see the recovery screen so I have some reasons to believe it could still be software. Unfortunately, if I try to RMA, they're going to say that I voided the warranty....because I probably did by opening the case AND running a cooked ROM. So, they'll fix it but as a service. I'm not sure it would be worth the cost.
Wait for the next update. I tried sending it in for repair. No change what so ever. If it is software you got me beat on the weirdest ICS bug.
yanbo2012 said:
Wait for the next update. I tried sending it in for repair. No change what so ever. If it is software you got me beat on the weirdest ICS bug.
Click to expand...
Click to collapse
Yeah, I think it's some corrupted memory that sticks around after reboot. At least I hope so. When I get home tonight I'm going to charge it up and see if the power draining helped.
If not...well, it might be time to think about my next tablet. I'm interested in seeing how the "Google Play Tablet" turns out as their might be integration with home theater stuff. Then there's the updated Transformers or maybe the iPad. Yeah, I know iOS is boring as hell but it has lots of tablet apps and gets new one's first. I'm kind of getting tired of seeing...."Coming for Android".
Skyeclad said:
Yeah, I think it's some corrupted memory that sticks around after reboot. At least I hope so. When I get home tonight I'm going to charge it up and see if the power draining helped.
If not...well, it might be time to think about my next tablet. I'm interested in seeing how the "Google Play Tablet" turns out as their might be integration with home theater stuff. Then there's the updated Transformers or maybe the iPad. Yeah, I know iOS is boring as hell but it has lots of tablet apps and gets new one's first. I'm kind of getting tired of seeing...."Coming for Android".
Click to expand...
Click to collapse
Yea, you screwed up by opening it. You might as well upgrade if all else fails. I'd hold off on another transformer for as long as I can though if I were you...already hearing about minor defects in tf300s such as light bleeding.
Then there's always the...iPad...but make sure you update if you get one! Jailbreak that MF first and then you'd be good to go. My dad wants me to jailbreak his iPad 2, but it doesn't help that he's "update happy"
Skyeclad said:
I opened the back of the unit but couldn't figure out how to pull the battery cable. I did manage to ruin some plastic clips on the bottom or something, so yeah the less than perfect bottom fit is now fun. So, my next step is to let it power down, charge it up and see what happens.
Any advice...other than don't enrage the Gods?
Click to expand...
Click to collapse
So, with some plastic clips damaged. Does it close properly now?
The battery cable should be either soldered onto the board or it uses zip cconnector. Nowadays cable/ribbon cable uses zip connector on motherboard.
And not all TF101/G would have 100% perfectly & exactly the same and this might giving you a little not so perfect in term of tiny capacitances on the board. This little components sometimes don't hold voltages that good as they should. Thus giving some trapped voltages and having your battery connected makes this trapped voltages remain in it. The best option now is to drained your TF101 completely and stay drained for another day(this is to let the capacitances drain its trapped voltages). The next time you boot and it might just solved your problem..
farsight73 said:
So, with some plastic clips damaged. Does it close properly now?
The battery cable should be either soldered onto the board or it uses zip cconnector. Nowadays cable/ribbon cable uses zip connector on motherboard.
And not all TF101/G would have 100% perfectly & exactly the same and this might giving you a little not so perfect in term of tiny capacitances on the board. This little components sometimes don't hold voltages that good as they should. Thus giving some trapped voltages and having your battery connected makes this trapped voltages remain in it. The best option now is to drained your TF101 completely and stay drained for another day(this is to let the capacitances drain its trapped voltages). The next time you boot and it might just solved your problem..
Click to expand...
Click to collapse
Almost, there's a slight bulge in the bottom but it fits on the dock.
Unfortunately, I think it's a hardware problem. I tried unbricking the device using NVFlash to load stock ICS but the entire time the screen never displayed anything. It didn't look like the entire Flash job completed and I can't get the back light to turn on now. I can't even tell if it's charging.
Anything more I can try before I chalk this up to a brick?
Skyeclad said:
Almost, there's a slight bulge in the bottom but it fits on the dock.
Unfortunately, I think it's a hardware problem. I tried unbricking the device using NVFlash to load stock ICS but the entire time the screen never displayed anything. It didn't look like the entire Flash job completed and I can't get the back light to turn on now. I can't even tell if it's charging.
Anything more I can try before I chalk this up to a brick?
Click to expand...
Click to collapse
Have you tried leaving it for a day or two in total battery drained??
List you could do/perform.
1) NVflash works on B60 and below.. check yours
2) Put it in a freezer for a night
3) Dissemble again and see if anything disconnected or loose since the last time you open it.
4) Smell it and see if anything like burn smell around the motherboard(this could be over voltage from a weak components).
.
.
.
.
.
If all above still yielled the same result..
5) Check and see if your TF101 could survive 2 storey height drop..
Good Luck..
farsight73 said:
Have you tried leaving it for a day or two in total battery drained??
List you could do/perform.
...
2) Put it in a freezer for a night
...
Good Luck..
Click to expand...
Click to collapse
A lot of LCD screens can be damaged by freezing, unless you know that the TF is safe I would not freeze it.
OK, I managed to unbrick the device but I still can't see any video. Backlight is working fine and I can output to HDMI. Digitizer is also working fine as I can manipulate the screen and see the result on the TV.
So, now that I'm at stock ICS and can output video. Does this narrow it down to an LCD problem? If so, is there a loose wire I can check? Am I likely going to have to send it to ASUS for repair?
Skyeclad said:
OK, I managed to unbrick the device but I still can't see any video. Backlight is working fine and I can output to HDMI. Digitizer is also working fine as I can manipulate the screen and see the result on the TV.
So, now that I'm at stock ICS and can output video. Does this narrow it down to an LCD problem? If so, is there a loose wire I can check? Am I likely going to have to send it to ASUS for repair?
Click to expand...
Click to collapse
Lol, didn't you already take it apart before?
I2IEAILiiTY said:
Lol, didn't you already take it apart before?
Click to expand...
Click to collapse
Yes, but at the time I was looking for a cable that I could loosen, now I'm looking for a cable to tighten. Fml, yes it sounds stupid but I'm at the point where I need to decide if a repair or replacement is the next step. I'm not thrilled with anything out there.
Almost exactly the same problem here...
I have a very similar problem to yours right now; the screen on my TF101 is entirely black but the backlight is on and i can output through HDMI fine. I'm still under warranty but i can't RMA it at the moment as it is running Android Revolution HD and i need to restore it to stock Asus TW firmware before they would fix it. Problem is Rogue XM Recovery is not able to output through HDMI ;p, so now i have to wait for someone to post screenshots/pictures on a thread that i started showing the menu for the recovery and the other screens involving wiping the dalvik cache and installing from zip file. Any closer to solving the problem?
I had the same problem of the backlight being on but no video. It worked over the hdmi but that was it. I had to send in my unit via a RMA to get it fixed.
Thankfully it was under warranty so they fixed it. Did you drop your unit?
MeLikes said:
I have a very similar problem to yours right now; the screen on my TF101 is entirely black but the backlight is on and i can output through HDMI fine. I'm still under warranty but i can't RMA it at the moment as it is running Android Revolution HD and i need to restore it to stock Asus TW firmware before they would fix it. Problem is Rogue XM Recovery is not able to output through HDMI ;p, so now i have to wait for someone to post screenshots/pictures on a thread that i started showing the menu for the recovery and the other screens involving wiping the dalvik cache and installing from zip file. Any closer to solving the problem?
Click to expand...
Click to collapse
Just out of curiosity, why not nvflash your way back to stock? I did because I couldn't find my HDMI mini cable. I haven't opened my tablet again. I'm going to try to RMA it.
try to nvflash stock rom and start over? that would your best chance....
Sent from my Transformer TF101 using xda premium
Well first of all i don't know how to use NVflash, and secondly i have a B70 transformer so i don't know if it will work. Also i need to flash the stock Taiwan firmware because that's the original firmware that came with it and i can't find instructions for that. Just wondering though does flashing the stock rom using NVflash also install the stock recovery?

[Q] Is it possible to retrieve files from N7 whilst dead/bricked?

Hi all
Apologies at coming on here and immediately asking for help, but....
I've had my Nexus 7 since July and have been very happy until NOW!
I seem to have been cursed with the dreaded flat battery resulting in n7 being stuck in the boot up.
I get as far as the Google and X icon but then stalls.
I've tried all the methods of long push of buttons/multiple buttons/etc but to no avail.
I can bring up the factory restore option so I know I can get it working again, but....
I have an exam in a week which foolishly had work stored for on my n7 without back up (yes fool) so....
Please is there anyway to retrieve my files via PC etc before factory resetting
All help genuinely appreciated
Mark
rooted vs unrooted (or unlocked bootloader even if not rooted) makes a huge difference in the answer.
Please state which.
Sorry about that
Not rooted.
It is absolute stock, nothing changed or added from purchase other than jellybean updates
Thanks Mark
pleading said:
Sorry about that
It is absolute stock, nothing changed or added from purchase other than jellybean updates
Thanks Mark
Click to expand...
Click to collapse
I believe you are SOL in that case. Sorry.
Find someone with a Nexus 7, pop the back cover off and use their battery to boot up and retrieve your files. The back cover just pops off.
Sent from my Nexus 7 using xda app-developers app
bigbop said:
Find someone with a Nexus 7, pop the back cover off and use their battery to boot up and retrieve your files. The back cover just pops off.
Click to expand...
Click to collapse
pleading mentions the battery, but then says "stalls" - not "shuts down", which is what you might expect if the battery was drained:
pleading said:
I seem to have been cursed with the dreaded flat battery resulting in n7 being stuck in the boot up.
I get as far as the Google and X icon but then stalls.
Click to expand...
Click to collapse
But, bigbop could be correct if pleading meant "low battery shutdown"
One other very long shot - assuming that that the device is hung - is to see if either adb or MTP are available. Normally that happens very late in the boot & I have to imagine that he has already tried that though.
Hi again guys
Firstly thanks for not giving up on my situation!
Bad explanation by me I guess....
The battery went flat/dead (my bad)
Plugged in to charge and screen lit up again but showing the 'powering off' script
Left over night on charge, wouldn't switch on again next morning
Left on charge all day still no joy but if I try switching on whilst plugged in I first get the Google name, then the Google X but then gets 'hung' (probably a better description than freezes etc as it still pulsates the colours)
Only way to get out of this is to keep power button pressed which switches n7 off and starts the cycle again
If during the recycle I keep the volume down pressed then it accesses the option screen to recover/reboot etc
Hope this helps, and again thanks (desperate to recover course work)
Mark
Hi again
Update...
Battery is showing full now
But still same 'hung' situation
Regarding the 'ADB'
I can get to the 'apply update from ADB' option
And if I choose it states.... 'now send the package you want to apply to the device with "adb sideload <filename>"'
As always thanks for any help or suggestions
Mark
Mark,
It sounds to me like what you are describing is ADB in the stock recovery, not a ADB when the regular operating system is running. (Is that right?)
Unfortunately, the stock recovery is only good for 2 things: applying an OTA update, and doing a factory reset. Even if your tablet needed an OTA update (and it probably doesn't if it is up to date), it probably wouldn't fix the looping/wedged phenomenon: usually that is caused by stuff in the userdata partition.
Doing the stock recovery factory reset might cure the wedged/looping problem - but only if it wipes all the data from your tablet. (Including the /sdcard area too).
The only hope I held out was if your tablet was reachable via a ADB or MTP with the wedged operating system sitting there looping. Usually those facilities start up quite late in the boot sequence, however so probably you don't have that.
Sorry. I think you are still SOL when it come to retrieving files.
Thanks for the help anyway
I'm guessing that with no further responses that really is the end for my work.
Unfortunately for me personally it will mean the end off my relationship with the N7, as much as I've loved it I really can't justify the obviously common occurrence of this happening.
Thanks again all
pleading said:
Thanks for the help anyway
I'm guessing that with no further responses that really is the end for my work.
Unfortunately for me personally it will mean the end off my relationship with the N7, as much as I've loved it I really can't justify the obviously common occurrence of this happening.
Thanks again all
Click to expand...
Click to collapse
I had same sort of problem N7 went flat tried to charge but would not power on
Took back panel off and disconnected battery for 10 mins reconnected battery and put back on charge
it then booted up as normal
pleading said:
Thanks for the help anyway
I'm guessing that with no further responses that really is the end for my work.
Unfortunately for me personally it will mean the end off my relationship with the N7, as much as I've loved it I really can't justify the obviously common occurrence of this happening.
Thanks again all
Click to expand...
Click to collapse
Uhhh ... what?
The OP was about a tablet that you couldn't get into because
[a] it had a correctable soft-fault
you didn't want to exercise an available soft-fault recovery method because of a desire to reclaim user files not backed up
... and so far as we know the soft-fault recovery mechanism still is available to you.
How did that morph into "this is the end"?
You need to re-do your homework, perform a factory reset, and move on with your life.
You have used either software or hardware in the past haven't you? That thing isn't a toaster or a waffle-iron! No backups of important stuff? Come on!
OK, well then. Pack it up and send it to me with the charger and I'll pay for the shipping - UPS ground.
Doesn't the Nexus have a safe-boot mode?
Sent from my Nexus 7 using xda app-developers app
bigbop said:
Doesn't the Nexus have a safe-boot mode?
Click to expand...
Click to collapse
Just tried right now - held the Vol-down button down continuously from about 2 secs after the Google B&W splash screen appeared until the lock screen appeared. That worked. (Stock 4.2.2)
"Safe mode" appears in the lower left corner. I had access to all the market apps (that I tried), but did not see a toast notification from StickMount after the boot - suggesting that safe mode only inhibits apps from starting on boot.
I suppose this could work (although the OP's deadline has probably come and gone) for bypassing a hung boot - but only if the hang is due to a market app that normally starts on boot.

Phantasm Touch and finger slider

Hi all,
I'm new here, a friend refered me this page to ask for some troubles I'm having with my Nexus 4.
I bought it from ebay about 4 months ago. For all this time, it worked perfectly, no problems at all, running fine.
The thing is that this last week the telephone is doing strange things. While using it, at a few minutes of use, "phantasmal touches" occurs, getting hit the buttons from back, back to desktop and last applications.
Also, after some minutes, or just touching the screen for scroll, the slide malfunction, getting harder to slide, even sometimes this doesn't works, but touching stills operative (sometimes not).
The only way that temporarily works, is locking and unlocking the screen, but problem still appear again and again.
Tried also to restore it (like as it was new). But nothing.
Hope you can help me with this. Thanks.
the-cheshire-cat said:
Hi all,
I'm new here, a friend refered me this page to ask for some troubles I'm having with my Nexus 4.
I bought it from ebay about 4 months ago. For all this time, it worked perfectly, no problems at all, running fine.
The thing is that this last week the telephone is doing strange things. While using it, at a few minutes of use, "phantasmal touches" occurs, getting hit the buttons from back, back to desktop and last applications.
Also, after some minutes, or just touching the screen for scroll, the slide malfunction, getting harder to slide, even sometimes this doesn't works, but touching stills operative (sometimes not).
The only way that temporarily works, is locking and unlocking the screen, but problem still appear again and again.
Tried also to restore it (like as it was new). But nothing.
Hope you can help me with this. Thanks.
Click to expand...
Click to collapse
Have you noticed if it stops or starts doing it if you plug it into a charger (preferably the stock or a decent quality one)
sp99 said:
Have you noticed if it stops or starts doing it if you plug it into a charger (preferably the stock or a decent quality one)
Click to expand...
Click to collapse
The charger is wich it came with the original mobil, and does it also when charging
Is it stock?
sp99 said:
Is it stock?
Click to expand...
Click to collapse
I'm sorry, what you mean with stock.
Have you rooted it or put a custom ROM on it?
sp99 said:
Have you rooted it or put a custom ROM on it?
Click to expand...
Click to collapse
No, it's not.
the-cheshire-cat said:
No, it's not.
Click to expand...
Click to collapse
Is the os up to date? (Settings-> about phone->Software updates->check for updates) Also try wiping the cache partition (I will post instructions of you need them).
sp99 said:
Is the os up to date? (Settings-> about phone->Software updates->check for updates) Also try wiping the cache partition (I will post instructions of you need them).
Click to expand...
Click to collapse
It's updated, and thanks for spending your time with this, I apreciate it, sincerely. Will wait for that instruction!
the-cheshire-cat said:
It's updated, and thanks for spending your time with this, I apreciate it, sincerely. Will wait for that instruction!
Click to expand...
Click to collapse
No problem.
This is from an email from Google regarding my nexus 7, it should be the same:
Hold the*Power Button*until the device powers down completely.Press and hold*Power Button*and*Volume Downsimultaneously.Once at the Android bootloader screen, pressVolume down*until you see the option*Recovery mode.Press*Power*button to restart into*Recovery mode. You should see an image of an Android with a red exclamation point.While holding down the*Power button, pressVolume Up.Use the Volume keys to scroll down to*wipe cache partition*and press*Power*Button*to select it. The device should clear the cache instantly.*Select and press the*Power Button*on*Reboot System Now, then see if the issue is resolved.
sp99 said:
No problem.
This is from an email from Google regarding my nexus 7, it should be the same:
Hold the*Power Button*until the device powers down completely.Press and hold*Power Button*and*Volume Downsimultaneously.Once at the Android bootloader screen, pressVolume down*until you see the option*Recovery mode.Press*Power*button to restart into*Recovery mode. You should see an image of an Android with a red exclamation point.While holding down the*Power button, pressVolume Up.Use the Volume keys to scroll down to*wipe cache partition*and press*Power*Button*to select it. The device should clear the cache instantly.*Select and press the*Power Button*on*Reboot System Now, then see if the issue is resolved.
Click to expand...
Click to collapse
Ok, it's done, I gonna test it for a while and see if it's solved
Nothing, less than a minute to the slider started to fail when moving up and down
the-cheshire-cat said:
Nothing, less than a minute to the slider started to fail when moving up and down
Click to expand...
Click to collapse
Don't quite understand, does that mean it has worked or it still has a problem?
sp99 said:
Don't quite understand, does that mean it has worked or it still has a problem?
Click to expand...
Click to collapse
The problem stills, for example, im in facebook or whatsapp, i slide up and down for reading, and from the nothing it's harder to slide/scroll... it's not that sensitive as before. I mean, with just a slide of the finger at early is scrolls fast, as it must be, but for some reason, after a few slides, with the same finger slide, it just scrolls a bit.
the-cheshire-cat said:
The problem stills, for example, im in facebook or whatsapp, i slide up and down for reading, and from the nothing it's harder to slide/scroll... it's not that sensitive as before. I mean, with just a slide of the finger at early is scrolls fast, as it must be, but for some reason, after a few slides, with the same finger slide, it just scrolls a bit.
Click to expand...
Click to collapse
Have you tried cleaning the screen with (alcohol free) screen wash? Otherwise it sounds like a hardware issue or something wrong with the touch drivers.
Sent from my Nexus 4 using Tapatalk
sp99 said:
Have you tried cleaning the screen with (alcohol free) screen wash? Otherwise it sounds like a hardware issue or something wrong with the touch drivers.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Even with the screen protector? Can try it. If it's the touch drivers, how can they be "reparired"?
the-cheshire-cat said:
Even with the screen protector? Can try it. If it's the touch drivers, how can they be "reparired"?
Click to expand...
Click to collapse
It's probably the screen protector causing the problem, take it off and then try using the phone again and see what happens.
Sent from my Nexus 4 using Tapatalk
the-cheshire-cat said:
Even with the screen protector? Can try it. If it's the touch drivers, how can they be "reparired"?
Click to expand...
Click to collapse
Well, for the moment I've done a wipe from all data, the other option from the "recovery menu", and it's been a while using it, and the problem doesn't shows, non of both i mention.
Let's see if this continue like this. Tomorrow I'll let you know.
thanks for all!
after this post, it came again T-T
the-cheshire-cat said:
Well, for the moment I've done a wipe from all data, the other option from the "recovery menu", and it's been a while using it, and the problem doesn't shows, non of both i mention.
Let's see if this continue like this. Tomorrow I'll let you know.
thanks for all!
Click to expand...
Click to collapse
You're welcome Remember to press the thanks/thumbs up button!
Sent from my Nexus 4 using Tapatalk
Nothing, the problem still persist.
I'll see if I must clean the screen (it has a screen-protector althought). If not, I don't know what to do, unless I send it to someone if can repair it or something... :crying:

Touch input broken- alternative input methods?

I was given two Nexus 4 units with fractured glass to tinker with- I'd like to use them to just run a data processing app as a lower powered server. The problem is that the touch input appears to be completely dead on one unit, and only 30% of the screen responds to touch on the other!
I can't even get past the welcome screen, which is problematic. Can someone help me come up with a way to get an alternative input? I just want to get in far enough to install the app and run it, I'm thinking either via remote desktop or keyboard/mouse via OTG cable.
Both units have stock roms, which means USB debugging is off and apparently OTG support doesn't exist either. I'm feeling like I hit a brick wall here. Is there anything I can do, or are these units useless? Can a custom rom with OTG support be installed perhaps through recovery? Any ideas or suggestions would be helpful, thanks!
Try the phone which works 30% screen by rotating in 90 degrees or 180 degree and then try to select the menu options. If it works then you can try for something.
Sent from my SM-G7102 using Tapatalk
pm_dsp_ra said:
Try the phone which works 30% screen by rotating in 90 degrees or 180 degree and then try to select the menu options. If it works then you can try for something.
Sent from my SM-G7102 using Tapatalk
Click to expand...
Click to collapse
Problem is that the homescreen doesn't rotate. I needed to click "next" in the bottom right corner to advance past the welcome screen, and I couldn't!
But I was able to pull down the top bar and get into settings from there, and turn on USB debugging. Once I did that, I downloaded and ran a remote control app that I could sideload with ADB and set up what I wanted to run there. So at least I got ONE working. But the other one which has no touch input working at all, I'm just hitting a brick wall with that one.
Is there no way to install a custom rom with a non-functional screen?
Similar problem
Hi Dishe, did you find any solution to this problem. I'm in a similar situation but worse since my phone was encrypted and some points does not work on screen. If you've find any alternative please let me know.
Dishe said:
Problem is that the homescreen doesn't rotate. I needed to click "next" in the bottom right corner to advance past the welcome screen, and I couldn't!
But I was able to pull down the top bar and get into settings from there, and turn on USB debugging. Once I did that, I downloaded and ran a remote control app that I could sideload with ADB and set up what I wanted to run there. So at least I got ONE working. But the other one which has no touch input working at all, I'm just hitting a brick wall with that one.
Is there no way to install a custom rom with a non-functional screen?
Click to expand...
Click to collapse
ridwanoz said:
Hi Dishe, did you find any solution to this problem. I'm in a similar situation but worse since my phone was encrypted and some points does not work on screen. If you've find any alternative please let me know.
Click to expand...
Click to collapse
Have you tried BT mouse?
Unfortunately the device cannot boot up since it is encrypted, so cannot make any connections.
ze7zez said:
Have you tried BT mouse?
Click to expand...
Click to collapse
ridwanoz said:
Unfortunately the device cannot boot up since it is encrypted, so cannot make any connections.
Click to expand...
Click to collapse
Can you format the partitions through TWRP and upload the new ROM?
Or try the following:
fastboot format userdata
Thanks for your concern. Meanwhile, I've installed the stock rom via fastboot cli and phone works now. I've lost all my data and touch panel is nonresponsive on the right side of the screen but at least I can make calls now.
Anyway I need to replace either screen or the phone itself.
ze7zez said:
Can you format the partitions through TWRP and upload the new ROM?
Or try the following:
fastboot format userdata
Click to expand...
Click to collapse
ridwanoz said:
Thanks for your concern. Meanwhile, I've installed the stock rom via fastboot cli and phone works now. I've lost all my data and touch panel is nonresponsive on the right side of the screen but at least I can make calls now.
Anyway I need to replace either screen or the phone itself.
Click to expand...
Click to collapse
Replacing the screen may be unprofitable. It is better to buy BT mouse and use the N4 for special tasks. Anyway, you yourself decide.

Categories

Resources