[Q] touch screen issues after update - Asus ZenWatch

Hi all,
My Zenwatch had issues with a recent update basically it failed mid-update, the watch rebooted & seems to have partially loaded the OS.
The screen is not responding to touch but works on tilt, notifications etc all were working ok too.
Unfortunately i didn't turn ADB debugging on so i can't access it via PC/ADB either, now its lost my phone pairing too and as mentioned i cant access the swipe to do anything helpful on the watch.
As i bought the watch on holiday Asus UK aren't entertaining any help under warranty & can't suggest a repair shop either (though as i cant turn on ADB im not sure what they can do anyway!).
Have i now got a paperweight or is there a way of reflashing the Zenwatch without ADB turned on on the watch?
James

I got the same problem with touchscreen so i send it back to asus

Would love to but got the watch on holiday in the usa and now back in the UK..
Asus are saying return it to where you bought it.
Not much of a warranty if that's the case :-S
Sent from my D6603 using XDA mobile app

call Asus us

If you can get into recovery mode, you might be able to re-flash the update zip. It shouldn't matter that you don't have debugging turned on to do that, I think. There's some information on how to get to recovery mode here:
http://www.tomsguide.com/faq/id-2411652/reset-android-wear-watch-factory-settings.html

darn - got exited reading that until i saw that was for the LG!
I think im going to have to send it to a friend of mine in the US & get them to return it for me.
Thanks all
James

Jamesb4uk said:
darn - got exited reading that until i saw that was for the LG!
Click to expand...
Click to collapse
I don't think that matters. It should work the same on the Asus. I've used recovery mode to sideload updates on mine in the past.

Don't send your watch across the pond!
Jamesb4uk said:
darn - got exited reading that until i saw that was for the LG!
I think im going to have to send it to a friend of mine in the US & get them to return it for me.
Thanks all
James
Click to expand...
Click to collapse
You can get to fastboot by turning the watch on and swiping from the top left to the bottom right as soon as you see the Asus logo. I don't know if there is a similar method to boot directly to recovery, but fastboot should be all you need.
Edit: To boot to recovery swipe from the top right to the bottom left when you see the Asus logo.
-Andy
Sent from my Speak & Spell.

Doc Ames said:
You can get to fastboot by turning the watch on and swiping from the top left to the bottom right as soon as you see the Asus logo. I don't know if there is a similar method to boot directly to recovery, but fastboot should be all you need.
Edit: To boot to recovery swipe from the top right to the bottom left when you see the Asus logo.
-Andy
Sent from my Speak & Spell.
Click to expand...
Click to collapse
Tried to get to Fastboot, sadly didn't notice any difference in bootup - might indicate more of a hardware issue than software.
is it like phone based fastboot where you plug the USB lead in before fastboot? If so that could be difficult with the Zenwatch cradle!
James

Jamesb4uk said:
is it like phone based fastboot where you plug the USB lead in before fastboot? If so that could be difficult with the Zenwatch cradle!
James
Click to expand...
Click to collapse
No need to mess with a cable. The timing isn't picky either. I think you just have to do it between the time that the logo displays and the watch vibrates. You probably have some misnatched firmware due to the failed update. Maybe thats why the touch screen is borked. I wonder if there is a way to enter fastboot by jumping two of the pogo pins together. If not you're SOL.
-Andy
Sent from my Blendtec Total Blender.

Doc Ames said:
No need to mess with a cable. The timing isn't picky either. I think you just have to do it between the time that the logo displays and the watch vibrates. You probably have some misnatched firmware due to the failed update. Maybe thats why the touch screen is borked. I wonder if there is a way to enter fastboot by jumping two of the pogo pins together. If not you're SOL.
-Andy
Sent from my Blendtec Total Blender.
Click to expand...
Click to collapse
Yep firmware mismatch sounds about right. Sadly no luck with the fastboot at all.
Might give the jumping a go - got nothing else to loose, then i'll ask a friend of mine to return it.
Thanks for your help here Andy.
James

When you get the new one I bet I know the first thing that you're going to do

again, why not call Asus us? I had an issue with mine and they quickly sent me an rma label

Related

How I (accidentally) got into download mode on my Bell i9000m

This is not the kind of recipe you'd want to follow to get download mode on a phone with 3 button recovery disabled, but this might clue someone in as to how to make it accessible under simpler circumstances.
This worked for me, dont assume anything:
- Got brand new Bell Samsung Galaxy S from store this morning.
- Tested general funcs, installed nothing.
- Tested every possible way of getting into Recovery or Download mode. None worked.
- Loaded up Kies
- Plugged in phone
- Clicked upgrade firmware
- Started the firwmare update process
- At around 20% progress, unplugged the phone (dont ask)
- Phone was now Purple screen bricked.
- Popped and re-inserted battery.
- Came back with "disconnted" graphic (phone-warning-pc)
- Held HOME, then VOLUME-DOWN, then power (with usb plugged in)
- Held till it came back in download mode.
- Voila!
I then used Odin to flash JH2 onto my phone. Phone works fine now. Impossible to get into recovery or download mode again.
Conclusions:
- If you are completely mad, you could try this technique to get into download mode.
- The blocking of the mechanism is clearly software, not hardware.
- Erasing or damaging the firmware erases the block.
- You may not be able to get into download mode voluntarily, but when you need it most (ie phone bricked) it's there for you.
I hope this somehow ever so slightly advances us toward a hack or fix for this problem. Good luck all.
davidke said:
- At around 20% progress, unplugged the phone (dont ask)
- Phone was now Purple screen bricked.
Click to expand...
Click to collapse
Glad you got it working. I'm able to boot into recovery/download mode when my phone is warmish. Try explaining that!
risky stuff good job
mInes saying device cannot be updated
taurean376 said:
mInes saying device cannot be updated
Click to expand...
Click to collapse
Because you already have the latest....
Smart to test that method when brand new. In an emergency that isn't a bad thing to try. But they need to fix that, we bought the phone in good faith that it was complete and it might kill warranty but we should be able to get into download mode as designed. If we do then there isn't an issue with people wanting to exchange them cause we can fix our mistakes. Isn't that the better less evil way?...
taurean376 said:
mInes saying device cannot be updated
Click to expand...
Click to collapse
God I hate that angry face emoticon. It's like QQ more red face dude!
Anyway, mine says that too. Who cares. Just use odin.
my phone will only go into download mode if the back is warm. i flashed it 4 or 5 times yesterday and each time it would not go into download mode until i left it plugged in long enough for the back to become a little warm, then i could enter download mode at will
I have to sacrifice the lives of 1000 virgins to get mine into recovery/download mode Pain in the ass...
[/sarcasm]
Actually mine works fine. Mind you, I've had a locked out one. It Bricked
it's not true, i got mine into the ultimate bricked mode
and no matter what trick you tried
it will not go into download mode holding the 3 combo keys
on the NEW phone i got after that, it will easily go into download mode at my will, EVEN WHEN THE PHONE IS ON
so, it really just comes down to, if it works, it will work regardless
if it doesn't work... better return it before it is too late, and when you really really need it and it's not there for you
AllGamer said:
it's not true, i got mine into the ultimate bricked mode
and no matter what trick you tried
it will not go into download mode holding the 3 combo keys
on the NEW phone i got after that, it will easily go into download mode at my will, EVEN WHEN THE PHONE IS ON
so, it really just comes down to, if it works, it will work regardless
if it doesn't work... better return it before it is too late, and when you really really need it and it's not there for you
Click to expand...
Click to collapse
I had that picture on my screen yesterday and I almost swallowed my tongue! I was able to get it into download mode and flash with odin. Pretty scary as I mentioned earlier that my phone needs to be warm for it to have any chance of entering download mode.
from what i can gather, people that are able to to get into download mode, it was because it was working fine to begin with, just not hittings the buttons in the correct time or sequence
because if the heat mode worked, or the usb plugged mode worked, then it should have worked as well on the one i sent back for repair, but it didn't work because i tried those methods already
I definately cannot get back into download mode. I tried 100 times. Yet, yesterday, when I had the black screen of death, I could do it at will easily.
So there are circumstances that will let you in and others that wont.
For some it's "warmth", for me it's when it's bricked. Or maybe I killed a virgin that day... not sure.
i like the new term "Black Screen of Death"
lets keep using it more often, so it becomes the norm
it's much easier than say i got bricked at the phone -- ! -- pc screen as most people have been trying to describe
I can't get mine into d/l mode for the life of me.
question: I've had my phone for about a month now. Is it too late? I'm not even sure if I have the receipt (although my buddy is a manager at the bell store)
Should I replace mine? and if so, how do I go about doing it ?
Is it really necessary?
Can't you get into download mode via ADB ?????????????
i'll say wait for froyo to be out
then see if Samsung includes a fix for the 3 button issue.
if they don't or if the froyo upgrade dies half way
then you can comment it all here
http://www.facebook.com/samsungmobilecanada
AllGamer said:
i like the new term "Black Screen of Death
lets keep using it more often, so it becomes the norm
it's much easier than say i got bricked at the phone -- ! -- pc screen as most people have been trying to describe
Click to expand...
Click to collapse
plz help to bass this problem
I dont think you can "brick" an android device. I've had customers come in with all sorts of failed atemps of rooting and hacking and have fixed them all.
Device list:
Samsung Galaxy s
Samsung Galaxy
Samsung Apollo
HTC Wildfire
HTC Desire
Sony X10
Sony X10 Mini Pro
LG Intouch Max
T-Mobile G2
T-Mobile G1
There are a few things like when people dont make back ups of there efs folder etc but that is just user "school boy" errors by people who would play Russian roulette with a fully loaded gun and go first.
Why do people jump into things without thinking and expect others to fix it when they f**k it up. My advice is that if you cant afford to buy a new one when you brake it then leave it alone.
Flashing the software shouldn't "brake" it. It shouldn't break it either. Point is, the phones have a method of recovering from a bad flash, and that isn't working for some of us. We shouldn't have to be ready to buy a whole new phone, just to try different software.
Sent from my GT-I9000M using XDA App

Seeking Assistance Q.Q!

Hi guys! I'm new to the board. I've done some searching and still haven't been able to resolve my issue so hopefully, with your expertise, I can get this fixed.
Here's the story: I bought a Galaxy Nexus (GSM) second hand from a guy on Craigslist. He showed me the phone, works and looks like new. Yippee!! Well, when I got home I see that there's a lock code on it.. Tried calling the seller a few times and left a VM - now it says the number is disconnected... Emailed, no response. So I looked on here and learned how to get into the Bootloader menu...except when I hit Power and VOL+/-, it just boots straight back into the lock screen..
I've installed the appropriate Samsung drivers on my PC and tried to get it to be recognized that way. However, it seems to be in mass storage mode because when plugged in it just mounts it like a drive. I've tried the "Toolkits" but since my PC isn't seeing the phone properly it never makes a data connection for ADB. So, what're my options? Am I completely SOL?
The phone is beautiful and would love to use it =(
Not sure what exactly you mean by "lock code". But could be a stolen and locked phone.
How does the prompt look like?
You can't get to the bootloader? Really? That's the weirdest thing I've heard actually ...
Are you SURE you pressed both volume up and down then pressed power? Sometimes, you might boot into the ROM first, then press the volume buttons.
Also, I believe that you gotta unlock to install drivers and use ADB commands at first. My phone didn't let me install driver on my computer when it was locked (screen turned off)
If you can't get to the bootloader, you ARE pretty much screwed.. since you can't use fastboot and adb commands either
abnah said:
Not sure what exactly you mean by "lock code". But could be a stolen and locked phone.
How does the prompt look like?
Click to expand...
Click to collapse
It's just the standard lock screen. Keypad, Date/Time.
kyokeun1234> Yes, I am certain I'm holding the buttons in - there is a "click" on both VOL+ and VOL- as well as the Power button.
I've tried holding them all in. Holding just the VOL- button (for ODIN) - same result. OS just boots normally and goes back to the keypad requesting the code.
HerroKitty said:
It's just the standard lock screen. Keypad, Date/Time.
Click to expand...
Click to collapse
Okay, that looks like the phone just wasn't reset (resetted? Help, please, English isn't my native =D) properly. If you somehow manage to get into the bootloader, no worst case. But how you can do that when the button-combo isn't workling is above my knowlegde. Sorry. :/
There is a "special" micro USB cord called a Jig that can be used to coax the device into download (Odin) mode simply by plugging it into the device.
Hopefully someone will come along and give information as to where you can obtain one.
Once the device is in download mode you should be able to use Odin to return the device to a factory state.
Edit: I read an article that claimed this jig is compatible with the Galaxy Nexus:
http://www.amazon.com/gp/aw/d/B0053H73JQ/ref=redir_mdp_mobile?redirect=true&ref_=ox_ya_os_product
Sent from my Galaxy Nexus using Tapatalk 2

Random now permanent black screen issue

Bought this phone off the electronic bay, arrived totally fine, no signs of any damage, worked just fine. Upgraded it with the sony OTA updates to 4.1 and then the screen started acting a little funny. Sometimes when hitting the unlock button it would just light up the backlight. Then a few days later it stopped ever doing anything besides lighting up the backlight. Then it progressed to doing what I show in the video.
It still plays alert tones when i get messages or calls, but obviously the phone is totally unusable, but charges up fine.
any ideas what is going on here? Called Sony for a repair, but I was unaware they just charge a flat $185 irregardless of what the problem is...ridiculous.
foofiebeast said:
Bought this phone off the electronic bay, arrived totally fine, no signs of any damage, worked just fine. Upgraded it with the sony OTA updates to 4.1 and then the screen started acting a little funny. Sometimes when hitting the unlock button it would just light up the backlight. Then a few days later it stopped ever doing anything besides lighting up the backlight. Then it progressed to doing what I show in the video.
It still plays alert tones when i get messages or calls, but obviously the phone is totally unusable, but charges up fine.
any ideas what is going on here? Called Sony for a repair, but I was unaware they just charge a flat $185 irregardless of what the problem is...ridiculous.
Click to expand...
Click to collapse
Hi,
The best way to rule out any software problems would be to flash the latest 6.2.B.1.96 ftf using Flashtool. So, first make sure that the phone has enough charge, then press and hold the volume up+power combination until you get three vibrations. Then press and hold the volume down key and simultaneously connect the USB cable when Flashtool prompts you to. Once the flashing is complete, disconnect your phone and turn it on normally.
Regards,
abcdjdj
Sent from my LT26i using xda app-developers app
I already flashed back to stock just using the sony bridge app. It seemed to work fine (nothing showed up on the screen the entire time). After the phone boots up I can hear notification sounds as it gets all my texts and voicemails/whatever else. But otherwise it still does what is shown in the video below:
here is the video again, not sure if it worked last time:
http://www.youtube.com/watch?v=jbrpsWburMw
foofiebeast said:
I already flashed back to stock just using the sony bridge app. It seemed to work fine (nothing showed up on the screen the entire time). After the phone boots up I can hear notification sounds as it gets all my texts and voicemails/whatever else. But otherwise it still does what is shown in the video below:
here is the video again, not sure if it worked last time:
http://www.youtube.com/watch?v=jbrpsWburMw
Click to expand...
Click to collapse
What bug u reported is the bug of .200 and .211 official bug.. Its fixed in .96fw.. Wipe everything when u flash .96fw... So there won't be any problems..
sudhindrakv said:
What bug u reported is the bug of .200 and .211 official bug.. Its fixed in .96fw.. Wipe everything when u flash .96fw... So there won't be any problems..
Click to expand...
Click to collapse
Well there is a slight problem.
The phone does not have an unlocked bootloader yet, so I can't use flashtool. It has been flashed back to stock using the method I mentioned above. I have just finished installing ADB because (bear with me please) there is no way to turn the phone into fastboot mode without turning it off (I cannot currently turn it off because I can't see what is happening on the screen and don't remember how this phone works when you hold down the lock key to turn it off). I can perform a hard reset, but no way to just get it to turn off entirely.
So I thought I could use adb to shut it down, but adb won't work unless I have debugging enabled, which again I can't do unless I could basically just blindly navigate the menu to those buttons.
Although if I wait until the phone is fully dead then I can hopefully get it into fastboot mode, but that only gives me one chance. Plus it has a full charge right now, so that's going to be awhile.
Any suggestions?
I can get it in to fast boot if I'm quick, but I still can't enable debugging beforehand so its semi worthless.
I've been trying to watch videos to see where the button placement is to navigate through the menu to blindly enable debugging, but I can't seem to figure it out. It also doesn't help that I have no idea what version of android is now on the phone. I used the mac sony bridge app to restore the phone, but i'm not sure if that set it back to stock stock, or what version of android it set it to.
I am also now even more confused because I connected the phone to the computer and when I browsed it, all the pictures I took were still there...which should have been wiped when I restored it with sony bridge...
figured out it was 4.1 and watched review videos until i found one that showed the menu layout (although now I realize google images would have been more helpful).
Now going to see if I can get the bootloader unlocked.
I still feel like flashing 6.2.B.1.96 isn't going to do anything, because I assume that is what the sony bridge app flashed to it. Also I don't see where you are talking about that the issue I am having was a known issue, if you could point me in that direction that would be very helpful.
EDIT: Actually I'm not sure I enabled debugging after all, as when I do adb devices, no device is listed as running, just a blank space. Though I'm still not convinced doing the above would do anything, as it is basically what I have already done, just with flash tool as opposed to the official sony route.
Anyone have any ideas? I got a torx 6 and opened the phone, checked the connection between the motherboard and phone and it is fine. Screen is still having same issue.
I would be happy to just buy a replacement part for it, but i have no idea what part is messing up. Is it the display (the touch works fine) or is it the motherboard (it seems weird that it would be this because the phone functions completely normally, I even accidentally answered a call yesterday).
If i was to try and replace the LCD (or whatever it is) would I have to replace the digitizer as well? At which point it would make more sense to just sell the phone for parts I suppose.
You can use the flash tool by bin4ry with a locked bootloader. Not sure if you're past that stage though.
Sent from my LT26i using xda app-developers app
dkconor said:
You can use the flash tool by bin4ry with a locked bootloader. Not sure if you're past that stage though.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
I'll go ahead and try that out, but is there really much of a point do you think? Considering I've technically flashed the phone back to stock using the official software, why would it be any different doing it this way?
I am asking honestly btw, not trying to sound rude. I'm thinking it is more of a hardware failure, i just have no idea what part exactly is failing.
The phone itself works totally 100% fine, the touch works totally 100% fine, the only thing that is not happening is the data getting to the screen and displaying. The screen just flashes white for a second and then fades out (as you can see in the youtube link). Or it flashes a solid block of white at the top in the middle and faded white the rest of the way down and then it slowly all fades out (or disappears immedaitely if i press the lock button. The buttons all work fine (physical and touch) and i can navigate around the phone, albeit totally blindly.
This is really frustrating, and I'm pretty disappointed to see how sony had no interest at all in helping me resolve this situation.
Flashtool works with lock and unlocked bootloader
XDAプレミアムを使用 して私のLT28hから送ら れてきた
UchihaDareNial said:
Flashtool works with lock and unlocked bootloader
XDAプレミアムを使用 して私のLT28hから送ら れてきた
Click to expand...
Click to collapse
....right i know, but why does that matter. Why would reflashing my phone help at all at this point. Did you even read my post?
Listen to us
Alright so you came to this thread for...help
We have told you numerous times to flash using this tool (dev host link):
http://d-h.st/Kb8
install the flashtool created by Binary (sorry for username spelling error)
Download the ftf
https://docs.google.com/file/d/0B18FXPCopQhkeXNoWGVWbzlRaG8/edit?pli=1
now USING FLASHTOOL (link 1)
FLASH the FTF (link 2)
A clean flash. This flash is different from the flash that Sony will provide you for obvious reasons.
Using this method will COMPLETELY remove any doubt whether the issue is regarding software or hardware. Then you dont have to "think" whether the issue is hardware related or software related.
Sorry if i sounded rude but i had a hard time comprehending why you would not use the advice given by i believe 2 different indiviuals on a questions and answers thread.
424aca said:
Alright so you came to this thread for...help
We have told you numerous times to flash using this tool (dev host link):
http://d-h.st/Kb8
install the flashtool created by Binary (sorry for username spelling error)
Download the ftf
https://docs.google.com/file/d/0B18FXPCopQhkeXNoWGVWbzlRaG8/edit?pli=1
now USING FLASHTOOL (link 1)
FLASH the FTF (link 2)
A clean flash. This flash is different from the flash that Sony will provide you for obvious reasons.
Using this method will COMPLETELY remove any doubt whether the issue is regarding software or hardware. Then you dont have to "think" whether the issue is hardware related or software related.
Sorry if i sounded rude but i had a hard time comprehending why you would not use the advice given by i believe 2 different indiviuals on a questions and answers thread.
Click to expand...
Click to collapse
Hi,
because I could not follow the advice from the first user because the bootloader is locked. The second person gave me the advice, but honestly it seemed like pretty pointless advice. I don't understand how it is "obviously different" if it is literally flashing the same firmware (at least the first advice was that). I don't think it's that strange to ask why it would be any different.
To me it sounds like I had a broken window in my house and I asked someone how to fix it. I bought the replacement glass from store A and it didn't fit. I asked for help and someone pointed me to the exact same item at store B and said that surely it would work. Do you understand why this could be confusing? I feel like about half the time people give help on XDA it is very general and people are just looking for "thanks"...
I'll definitely try this though if you think there's a chance that it might work out differently. I'll try and get it set up tonight, thanks for the encouragement, I understand I probably sound stupid, just trying to figure out what to do.
Also, I assume this flash tool won't work if USB debugging isn't enabled. As I've said in previous posts, I can click things just fine, but because I can't see what I am doing, I don't have way of knowing where to click on the menu.
Does anyone have their phone set up with this version of android still. If you could take screen shots of each click to make to get to the dubugging box (and if there is a confirmation box) i would greatly appreciate it. I only had the phone for a week before this randomly happened, so I hadn't thought to enable debugging yet, as I hadn't even thought about custom firmware yet.
EDIT: Or even just a picture of what the screen that comes up when you long press to shut the phone down. I have no way of turning off this phone right now without just waiting for it to run out of battery.
Holding down the power button for a long time does nothing, holding vol up and power restarts it, but I need a way to turn it off. If i hold the power button for like a second so instead of locking it, the menu comes up, I just can't seem to find the freakin button for power off.
(please remember I can see nothing on the screen, it is just blank).
flashtool does not need debugging when you doing the actual flashing
to turn off the phone
SIMULTANEOUSLY hold down
Power+ Vol up + Vol Down (AT THE SAME TIME)
wait for about maybe less than 25 seconds and you will experience THREE short consecutive vibrations
at this time...the phone is off
then you can begin the flashtool method

Is my 1+3 dead!?

Hi everyone,
I'm experiencing pretty silly situation with my phone.
So the story begins here:
I was surfing the web while listening to music in the bus when suddenly my oneplus3 randomly turned off and I couldn't turn it back on. (I was on something around 15% on battery so it's not a low battery problem) I tried to turn it on several times and after holding the power button for like 10secs it turned on, and after pressing the power button again (because I needed to get past unlocked bootloader screen and dm-verity) I saw a boot screen. The capacitive button leds turned on and after 3 secs it turned off again, so I started worrying... After a while I tried to access the recovery, but no luck at all. It powers it self off after bootscreen. So I started to research. Tried to flash the entire OS, partritions with msmdownload tool. After several unsuccessful flashes (firehosewritedata failed sometimes while writing userimg or system.img or boot.img) I did get the download complete green text message, and after successful flash, the white LED turned on, even the phone was not plugged in USB or charger and turned off. The screen is completely black and the white led just flashes constantly without blinking or anything. I could only turn the led off by pressing the power button for another 10 secs. And after turning the phone off, problem still remains. After oneplus logo phone shuts down...
I can access bootloader.
And after flashing everything should be on stock, because now I only got screen only about bootloader, no dm-verity..
And of course - I still cannot access the recovery.
p.s. I tried to do the power cycle (as the tech support told me) but still no luck at all.
did u tried the full msmdownload tool (1gb) or the 55mb version ?
Mukthar. said:
did u tried the full msmdownload tool (1gb) or the 55mb version ?
Click to expand...
Click to collapse
1GB version
djemm1996 said:
1GB version
Click to expand...
Click to collapse
Are you sure that you did it right? Did your phone show up as mentioned in the instructions?
Puddi_Puddin said:
Are you sure that you did it right? Did your phone show up as mentioned in the instructions?
Click to expand...
Click to collapse
Of course. Everything is done right. I also get that green "download complete" message.
p.s I also opened the phone. water indicators are fine and no major defects what can i see by eye... All connectors are good as well.
Puddi_Puddin said:
Are you sure that you did it right? Did your phone show up as mentioned in the instructions?
Click to expand...
Click to collapse
And yes, phone was connected right. :good: installed drivers with test mode on Win10 and got Snapdragon device in COM devices. As well the MsmDownload tool shows up my device in port #20
Any ideas?
djemm1996 said:
Any ideas?
Click to expand...
Click to collapse
Follow method 2 from the Hard Brick guide by Naman Bhalla and try two or three times.
Sometimes it takes more than once for restoration.
Since you opened the phone, i think your warranty is gone now.
If the msmdownloadtool didnt help you, there is nothing you can do i think.
try to flash again, and if it still maybe something short inside.
if you have disassembly your phone, try disconnecting various flex cable like camera, sim slot etc that connect to the mainboard, that doesn't prevent device from powered on, then try to turning it on.
if it still, check your mainboard, if you don't know how, send it back.
AcidNoteZ said:
Since you opened the phone, i think your warranty is gone now.
If the msmdownloadtool didnt help you, there is nothing you can do i think.
Click to expand...
Click to collapse
Is ir really gone? There is a still warranty void sticker on the screw there, but of course it's possible to see by eye that the phone has been opened.
I have an appointment with Level2 tech support @oneplus, they are going to remotely flash the entire OS, but do you think they are using pretty similar technique as the msmdownloadtool?
djemm1996 said:
Is ir really gone? There is a still warranty void sticker on the screw there, but of course it's possible to see by eye that the phone has been opened.
I have an appointment with Level2 tech support @oneplus, they are going to remotely flash the entire OS, but do you think they are using pretty similar technique as the msmdownloadtool?
Click to expand...
Click to collapse
They are doing the same thing like you did.
I already had a session since i thought they are going to do something "special"
You can try the remote session but im afraid that wont help you if you already did it multiple times.
What about battery? Charged?
drmuruga said:
What about battery? Charged?
Click to expand...
Click to collapse
Yes battery is charged of course. It's just doint the same thing. Turns on, after a while when bootscreen comes it just turns off and white notification led appears, after that nothing.
I tried to flash it with tool using method 2 for like 15 times with "download complete" messages, but still no luck at all. Tried to erase partritions with fastboot, flashing just only recovery, modded recovery etc. but I still cannot access the recovery nor system. I just don't get it why the phone does not boot into recovery if I flash it or boot it straight away, It just only turns off and that's it. nothing more. Only black screen and white led lighting all the time (after a while the phone turns warm).
I have read all the MsmDownloadTool thread in "Mega Unbrick thread" and saw that few people have experienced the very same situation as me, so I was wondering if there is any fix for this? It's so strange that I was just surfing the Web and it just turned off by it self with like static image for miliseconds and after that just black screen.
There should be any fix. I guess that it's just a partition error...
Ok, not good news. I had a little remote session before a while. They says it's already a hardware problem.
AcidNoteZ said:
Since you opened the phone, i think your warranty is gone now.
If the msmdownloadtool didnt help you, there is nothing you can do i think.
Click to expand...
Click to collapse
Pfffft you think manufacturers notice when you take apart phones? Hell I took apart my Xperia Z2 because it was having problems and then glued it back together with cyanoacrylate hahahaha (worst thing to do but wtv) and no one noticed though it was seemless and everything looked perfect
Guys, I've got something for you! Not really the same thing as Naman.
p.s. not saying its original hehehehe keep safe
man i got a very similiar problem but my op3 has a black screen i was also on low battery around 5-15% when my phone went off after i was in twrp
Actually I was on twrp too! Also I have recently noticed that recovery loading speed was far too long than normal one. I'm talking for something about 5-7 minutes after reboot into twrp. So, who knows what did happen. Just made an RMA request. Will see how it goes.
Anyway, I was on stock 7.1.1 and it's just rooted with custom recovery and that's it! Nothing more! Is that just a factory failure or maybe it's caused by drops i have had? Nothing serious for a 4-5 times for a half year. Of course I have used it even in winter when the snowflakes are coming down from the sky and little rain. Btw, these liquid indicators are white, so all safe. ::laugh:
A
makadama said:
man i got a very similiar problem but my op3 has a black screen i was also on low battery around 5-15% when my phone went off after i was in twrp
Click to expand...
Click to collapse

Screen won't stay on

I've recently purchased a used Moto G5 (3gb ram version) from eBay. It's been working fine for a couple of weeks but has suddenly developed a fault, the screen will not stay on. It just constantly goes black / blank. When it boots the Moto logo is shown for about a second and then it goes off and will not come back on until I pull and replace the battery.
I know the phone is still functioning as i can hear it sat waiting at the encryption "enter PIN" prompt on boot up, it makes a click sound when briefly pressing the power button.
The only time I can get the screen to stay on is by booting to fastboot. However as soon as I try to boot system or recovery the screen goes off.
Has anyone else had this issue and is there any way to fix it?
Attached photo showing fastboot screen which is all I can get to without the screen going off...
audinswfc said:
Attached photo showing fastboot screen which is all I can get to without the screen going off...
Click to expand...
Click to collapse
Why don't you try a flash,as if any corrupted partition is there for screen it can get fixed, you can use Lenovo Moto smart assistant app to flash.
riyan65 said:
Why don't you try a flash,as if any corrupted partition is there for screen it can get fixed, you can use Lenovo Moto smart assistant app to flash.
Click to expand...
Click to collapse
It's this an Android app? If so I've no way of using it as the screen doesn't work when the OS boots...
audinswfc said:
It's this an Android app? If so I've no way of using it as the screen doesn't work when the OS boots...
Click to expand...
Click to collapse
It is a pc application which is use to flash the firmware on your device, it will guide you how to flash the firmware.
riyan65 said:
It is a pc application which is use to flash the firmware on your device, it will guide you how to flash the firmware.
Click to expand...
Click to collapse
OK thank you. Strangely enough after a full night on charge the phone is working perfectly fine this morning! However I think i'll do that firmware flash anyway just in case. Also wonder if I've got a faulty battery...
audinswfc said:
OK thank you. Strangely enough after a full night on charge the phone is working perfectly fine this morning! However I think i'll do that firmware flash anyway just in case. Also wonder if I've got a faulty battery...
Click to expand...
Click to collapse
You can try a flash, but I don't think there is a battery fault, if there any, bootloader also didn't show up, so there are possible changes of corrupt firmware in you device. And did you replace the original screen with other 3rd party screen. As that is also a reason, someone was having similar issue like you but, he has got the problem after screen replacement.so if you have done a screen replacement then that can be a problem.
riyan65 said:
You can try a flash, but I don't think there is a battery fault, if there any, bootloader also didn't show up, so there are possible changes of corrupt firmware in you device. And did you replace the original screen with other 3rd party screen. As that is also a reason, someone was having similar issue like you but, he has got the problem after screen replacement.so if you have done a screen replacement then that can be a problem.
Click to expand...
Click to collapse
No it has the original screen. Bought the phone second hand though so it's fairly scratched (but not cracked).
audinswfc said:
No it has the original screen. Bought the phone second hand though so it's fairly scratched (but not cracked).
Click to expand...
Click to collapse
Then flash can fix the problem.
riyan65 said:
Then flash can fix the problem.
Click to expand...
Click to collapse
Thank you, i'll give it a shot tonight.

Categories

Resources