Good night everybody, I'm dipping my toes into phone/tablet repairs and I have a strange case with a Nexus 7 32GB model, first it was stuck at the Google screen that has a open padlock, after flashing it with Android 4.2.2(JDQ39) and updated the bootloader from 3.12 to 4.18 it finally started working, but if I turn it off after 5 seconds the tablet boots up by itself, the power button is working fine, and I can lock and unlock the screen just fine using the power button, any ideas of what it can be?
My first idea was to do all the updates up to Android 5.0.2 hoping that it might solve the problem.
Best regards and thanks in advance.
It reboots and then works normal?
Really weird
Yes, I reboots and is working perfectly, except for the touch-screen, already tried 3 new digitizers and no sign of life out of them, works with no problem with a mouse.
I friend of mine told me that it is supposed to reboot when the power button is pressed for a long time, but I can't find evidence of that information googling around.
Related
I just got my A7+ this weekend and I love it. The only problem is it will not resume from standby. If the screen goes off, either by hitting the power button or timeout the green led starts to flash and the lcd turns off. When I press the power button to wake the tablet the led turns on solid green, the screen flickers and nothing. The only way I can get the tablet to work again is to turn it off completly by holding the power button for 10 seconds and reboot it. I did a factory reset and installed the latest firmware. Any ideas on what could be causing this problem ?
Thanks for the help.
i have the same problem.
Hey guys, I bought a refurb A7+ last week and have not had this issue. Which (factory) firmware version do you have ? Mine is build QAJ3000.3.0018 .
Have either of you sideloaded anything unusual ?
Cheers !
I also got mine refurbished, for $120 can't beat that ! I have the same build number. I did not side load any apps, it was dowing it right out of the box. Anyways I got tierd of playing with it so I brought it back to the store and they exchanged it for me. The new one works perfectly ! Just waiting for a rom now
digidog_A7+ said:
Hey guys, I bought a refurb A7+ last week and have not had this issue. Which (factory) firmware version do you have ? Mine is build QAJ3000.3.0018 .
Have either of you sideloaded anything unusual ?
Cheers !
Click to expand...
Click to collapse
This problem was fixed with the 3.0021 firmware release on the eLocity website. As of today, there is a newer update to the rom 3.0022 which fixes wiping user data from the device.
I have the same issue and it is with the 3.0021 FW.
I have had the same problem with mine since new, I am using the newest firmware and the issue is still there. I can get it to wake up some times if I just rapidly push the power button until the screen flashes on. I don't know what to do with this thing, it would be great with ICS but between the wake issue, Froyo, choppy video, and poor support I am about to throw in the towel on this one.
I have the 3.0022 firmware installed and if I decide to force sleep (soft press of power button) I can duplicate the sleep issue, almost get myself into a panic mode, but then after a few tries it will wake up. They say that 3.0022 fixes it, but it does not. I have display set to not time-out. It's an annoying issue.
What happens is, my Nexus 7 will sometimes not awaken from a sleep state. Pressing and/or holding the Power/Lock button does nothing when this happens. The button otherwise works fine.
Faced with this dilemma, I tried to boot into recovery by holding Power/Lock+Volume Up+Volume Down. This needs to be held for about ten seconds to get a response out of the device. I haven't flashed or rooted, but I did update to 4.1.1. On successfully "booting into recovery", the Nexus 7 skips recovery and boots straight into the Google splash screen, after which it functions normally.
I thought this might have been a one-off issue, but it just happened again.
Is this just a software bug in 4.1.1, or is it faulty hardware? The unit is otherwise fine, no lifting bezel, speaker problems, dead pixels, etc. The next shipment of Nexus 7's isn't meant to get here until midway through August, but rather than hanging onto mine I'd prefer to have the security of a refund or guaranteed replacement if I can get one.
Bought locally in New Zealand.
Bump.
I'm going to take it back to the retailer to talk to them about it - I haven't done anything to the device other than updating to 4.1.1, so it can't be a firmware thing? I suppose it could be a buggy app, but I can't think of a reason why a buggy app would basically crash the Nexus 7 to the point where it won't turn on without using the recovery key combination.
If anyone has any input I'd love to hear it, I'm totally lost.
I've had my Nexus 7 since launch.... so i guess first build.
Anyway for the past month or so when i charge the unit from complete shutdown... it restarts. This results in a further shutdown to get the battery graphics up indicating the charging cycle.
Although i can live with this problem, i'm also then having trouble starting there after, but only the first restart after charching, the first restart usually means holding down the start button for 30 secs or more.
This problem existed before the latest upgrade 4.1.2, which i,ve had for some time.
The N7 was purchased from google, and is the 8gb version.
Will i need to return this unit for repair or swop out or is there a fix i haven't read about, i should also add the unit is completely stock.
Thanks if you can help.
That usually happens that you have to hold the power button down for a long time. That doesn't happen for me anymore for some reason because of the update though.
Ryan35310 said:
That usually happens that you have to hold the power button down for a long time. That doesn't happen for me anymore for some reason because of the update though.
Click to expand...
Click to collapse
Thanks Ryan 35310,
But i was looking for a fix.... or even a send it back, its defo not working correctly.
Hello friends,
My LeEco Le Pro3 (727) bricked two days ago and I haven't had any luck turning it back on. It was running LineageOS 8.1 latest official build with an unlocked bootloader, Magisk 16.0, TWRP 3.2.1, and OpenGapps ARM64 8.1 nano. Immediately prior to bricking I was setting it up for bluetooth with my car and was trying to run Google Maps through voice command. As I directed Google Maps to take me to a location, the phone froze, the screen got all "fuzzy" and I got the dreaded blue screen of death.
From that point on I have not been able to turn the phone back on. When I press the power button it will vibrate every 5-10 seconds as though it will turn on but it never does. Ive tried everything I can think of to get to work again including:
- Pressing power button for 2 min, 5 mins, 10 mins
- Pressing power button + vol up (recovery) for 2 min, 5 mins, 10 mins
- Pressing power button + vol down (fastboot) for 2 min, 5 mins, 10 mins
- Pressing power button + vol up + vol down (QFIL MODE) -> Installing Qualcomm driver, downloading "FlashOne2.0", flashing all versions of "qfil files" that I could find but still unable to boot up
- Pressing all different button combinations while plugged in to computer/charger
- Using different cords/chargers/usb ports
- Leaving it to charge overnight/full day then trying to boot up
- Leaving it sitting not charging for a full day then trying to boot up
At this point I'm starting to think it might be a hardware issue but who knows..
Any advice/suggestions would be greatly appreciated.
Thank you.
Where did you buy it from.
I don't have much to add here it seems like you have done everything that you could
Let's clear this up no fashboot right.
Only one thing to try hold power down then plug in USB.
Sent from my LEX727 using xda premium
My one did the same, the issue was motherboard. You should send it back to repair.
mchlbenner said:
Where did you buy it from.
I don't have much to add here it seems like you have done everything that you could
Let's clear this up no fashboot right.
Only one thing to try hold power down then plug in USB.
Sent from my LEX727 using xda premium
Click to expand...
Click to collapse
Thank you for the reply.
It was purchased from a local retailer here in the United States through Google Express. Fortunately I should still be able to return it for a full refund but I would rather have a working phone than my money back.
No flashboot either. It's like the phone just decided to quit working one day. Tried holding power while plugging in USB as well and no change.
marik1 said:
My one did the same, the issue was motherboard. You should send it back to repair.
Click to expand...
Click to collapse
The conclusion I'm reaching at this point too. I'll see what the return policy.
Well if it will not turn on it is hardware issue you should be able to return it.
Sent from my LEX727 using xda premium
That is so strange. The screen going fuzzy like that is indicative of a hardware issue, IMO. I saw that on my laptop once, but that was because I hit the screen too hard. Never seen a BSOD on an Android device before. TIL.
I assume you've already tried an adb logcat. Were you using the original LeEco cable? I heard it has issues since it's not up to spec. 99% hardware failure, but I can't help but think it has something to do with driver communication confusing the device and causing hardware failure (?) if that's even possible.
Just a final update for those curious.
After leaving the phone alone for two days I plugged it into the charger and low and behold it started vibrating and booted up by itself. It was running a Chinese developers editions 720 rom due to the QFIL File I had flashed in my earlier in my attempt to fix it. Battery was drained so I let it charge for a while and everything was fine until I attempted to restart the phone. As the boot animation was loading, I got the blue screen of death for a second time.
I took a quick picture, the phone shut off itself off, and same as before it wouldn't boot again. As other users have suggested it appears to be a hardware issue, likely with the motherboard. Fortunately I was still able to return the phone (purchased through Google Express via a local retailer) and received a full refund. I've since bought another Le Pro3 (727) and hopefully when that one comes in, it won't have any issues.
Thanks to all the users who left suggestions/tips.
shyboi122 said:
Just a final update for those curious.
I've since bought another Le Pro3 (727) and hopefully when that one comes in, it won't have any issues.
Thanks to all the users who left suggestions/tips.
Click to expand...
Click to collapse
You bought the same phone again? :good: You're courageous, lol.
i been experiencing the exact problem like your on my x720, as i boot up the system or enterting the recovery mode the screen go fuzzy on loading screen and shut itself off completly, i can still able access fastboot. As i left it for a while the phone will be able to almost finish the boot then ending it all with a blue screen.
Have anyone found a way to fix this DIY since my phone has past the guarantee plan ?
Hi
recently I bought a Xiaomi Mi A1 for my girlfriend, unfortunately she travels a lot so I just powered the device once, applied a couple of actualizations and shutted it down. I didn't tested the phone until she arrived (two weeks later) and we found that the device shuts it self down as soon the screen goes off.
I've been doing some tests and found that:
1 the phone doesn't shuts down immediately as the screen goes off, it takes something like 4 sec to do it
2 the phone shuts down, it is not that the screen freezes or the phone freezes. I can power it up normally,
3 if there is some "action" running in the background (a download, music), the cell phone doesn't shut down,
4 if I press the power button in order to shutdown just the screen, the phone does not shuts down immediately, but after a minute or so it shuts itself down,
I 'm not sure, but I believe that this problems came after the upgrades, the phone came with Android 7.1, and I upgraded to Android 8.1, so I ventured and flash the rom tissot_images_7.12.19_20171219.0000.00_7.1_d39fa89aaf but the problem persisted.
Do you think is a hardware issue?, does anybody has a clue about this behavior?
Should I return the phone?, Btw I bought it on gearbest, so rma might be problematic.
I will appreciate any help you can give me!
You can try flashing 8.0 fastboot image with Mi Flash Tool
Suraj Dutta said:
You can try flashing 8.0 fastboot image with Mi Flash Tool
Click to expand...
Click to collapse
Thanks, I will try, however this strange behavior makes me wonder if there is a hardwere problem