Related
After booting my tablet for the first time, I connected to the internet. The unit then told me that I needed a system update (4.something). I clicked ok. The system connected and downloaded the update. It seemed to install it. It then attempted to shutdown and it hung up at the final moment and the little activity circle just continued to go round and round.
I forced a shut down and rebooted. Next the "ACER" and the "android" came on the screen in that order. Next the tablet said that it was shutting down and the same thing happened -- it hung up again with little circle. Every time I attempt to reboot it repeats the same cycle. I have tried resetting the unit and holding the power and the volume+ down on reboot, but nothing seems to help.
I tried phone tech support and they sent me to a third party repair that charges even when the unit is under warranty. Acer support was not even accepting emails! This is a strange customer support.
Can anyone help?
Thanks
How long did it hang at the spinning circle? Probably what it was doing was updating you to HC 3.2. Sometimes it can take up to 20 minutes before if finishes.
I suspect maybe you force booted it before it could finish.
The easiest thing, would've been to take it back to the store for a replacement.
However, you might try the factory reset option. I've never used it, but, you'll see a small pinhole near the power button. With power off, press and hold the pinhole (with whatever you can find to fit, mabe a small paperclip) and power on I believe (check your instructions). Hopefully, the failed update didn't mess that up also. But probably did. Or did you already try this method according to your original post?
EDIT: Also, I would check your SD card, and remove what is on there. You can format it in your pc to FAT32. Then install it. This will ensure any garbage is removed from it.
Next, check this link;
http://forum.xda-developers.com/showthread.php?t=1276227
Pay attention to method 2. That might get you up and running, although with an unstable version. But, it will be running and allow you time to get another stable OS on it.
Check back with your progress.
Moscow Desire said:
How long did it hang at the spinning circle? Probably what it was doing was updating you to HC 3.2. Sometimes it can take up to 20 minutes before if finishes.
I suspect maybe you force booted it before it could finish.
The easiest thing, would've been to take it back to the store for a replacement.
However, you might try the factory reset option. I've never used it, but, you'll see a small pinhole near the power button. With power off, press and hold the pinhole (with whatever you can find to fit, mabe a small paperclip) and power on I believe (check your instructions). Hopefully, the failed update didn't mess that up also. But probably did. Or did you already try this method according to your original post?
EDIT: Also, I would check your SD card, and remove what is on there. You can format it in your pc to FAT32. Then install it. This will ensure any garbage is removed from it.
Next, check this link;
http://forum.xda-developers.com/showthread.php?t=1276227
Pay attention to method 2. That might get you up and running, although with an unstable version. But, it will be running and allow you time to get another stable OS on it.
Check back with your progress.
Click to expand...
Click to collapse
I can confirm this will work, the 3.2 update bootlooped my tablet too when i first got it but I just reverted back and even through the force closes was able to root and load CWM then go from there
sent from my Acer Iconia A500 beast of a tablet via XDA app
Thanks for the help. I am returning the unit.
I discovered that the unit was not charging the battery. I initially had pluged in the the unit to charge for 3 hours. After that I tried turning it on. During the numerous restart /shut down attempts, I noticed that the battery icon showed that the battery had not charged at all.
I next charged the unit for straight 10 hours. It still behaved the same way starting and then shutting down. The battery had not charged at all from the 10 hours of being plug in. I checked the charger and it was outputting a full 12 volts.
I called the vendor and will return the unit tomorrow.
Thanks for your attempts to help me.
JW
Symptoms: The Kindle Fire starts booting normally, but then shuts off prematurely or reboots spontaneously before the device completes the startup process. In extreme cases, the bootlogo may not even appear on the display and only the power switch LED lights up before the device shuts off again.
Cause: The battery has been depleted to the point that not enough power gets delivered to the CPU. The CPU detects the low power condition and its safety features power off the device.
Solution: Use the stock 1.8 amp AC charger to recharge the battery. In most cases, this seems to be enough to get power to the CPU and battery that it will begin to charge again.
In some rare instances, not even the AC charger will be enough to charge the battery. Why? The Kindle Fire's hardware does not have the ability to charge its battery offline. The device needs to be up and running so the ramdisk can handle the battery charging operation and that requires the CPU to be powered up. If the battery cannot provide enough power to the CPU, it shuts off automatically and the boot process stops or restarts... a classic catch-22.
Devices without FireFireFire 1.4 (or later) will need to upgrade to that version. This bootloader stops the boot process for a low battery condition (less than 3%) and charges the battery to its specified minimum before continuing to boot.
If the device has an earlier version of FFF, use the temporary fastboot mode feature to fastboot flash the new version using fastboot. If the device is using the stock bootloader (white/orange "kindle fire" bootlogo), a factory cable is probably necessary to put the device into fastboot mode.
Although the preferred method of installing this bootloader is through TWRP, it is dangerous in this situation because TWRP could shut down without warning. Because of this potential for a premature TWRP shutdown and a bad flash as a result, fastboot must be used under these circumstances. The device can be powered entirely from the USB port while running the bootloader, so it's much safer in this regard. Be sure to check the MD5 sum of the distribution, extract the contents of the zip archive and find the binary inside the cache directory. Flash this file using fastboot.
Using an older version of FFF...
Code:
fastboot flash bootloader /path/to/u-boot.bin
fastboot reboot
With the stock bootloader...
Code:
fastboot -i 0x1949 flash bootloader /path/to/u-boot.bin
fastboot -i 0x1949 reboot
Note: In both cases above, the "/path/to/u-boot.bin" must be replaced with the actual path to the file's location.
After a reboot, the bootloader will automatically stop the boot process and begin charging. The backlight is normally off in battery charging mode to conserve power, but press and hold the power button for a few seconds and a battery charging notification will appear on the display.
Note: Currently, neither FFF 1.4 nor 1.4a will display a bootlogo before entering battery charging mode, so the device may appear to be bricked. Press and hold the power button for a few seconds to display the battery charging notice. In addition, these versions will only enter battery charging mode when hooked up to USB power and not the AC wall charger. The developer is aware of both situations and has indicated that he intends to implement fixes for these issues.
Credits
pokey9000 - For providing information about the Kindle Fire hardware
SBlood86 - For sharing his experiences and initial ideas for a fix
Hashcode - For fixing/implementing battery charging on the bootloader
+1
Sent from my Amazon Kindle Fire using xda premium
My kindle fire is running Firefirefire 1.4a and when it boots normal mode it loads the Kindle Fire screen then restarts it's self. Trying to boot it in any other mode never boots it. The thing is charged but i cannot get it booting at all.
What if I do not have the stock charger?
I charge it using my PC?
Please help, I am lost without my kindle.
Kindle Fire Restarts on its own
A long while back, I rooted the kindle fire using the kindle fire utility .95. It worked fine for months. Then today, the device suddenly restarted and went into the "press power button to for recovery" page with the yellow triangle.
I can get it to go into the system for about 10 seconds but then it just restarts. To get in, I use the kindle fire utility and put it into normal boot mode. It goes in fine but then it restarts. I do have access to fastboot and i can get in. Battery power is near full so that wasn't the problem.
Anyways, after trying everything I found in the internet, i found the best solution was to use this thread:
[GUIDE] Kindle Fire For Beginners
Assuming you're already in fastboot mode, go down to post number 3 and start at step number 6. I got the u-boot.bin from this page Amazon Update
(you have to extract it). The twrp file I got from the kindle fire utility page.
The last step I did was step number 7 which was to reboot. Once I rebooted, it went into twrp recovery but said it couldn't access the memory or something of the sort. Then it did some sort of update and sort of took a long time to update. Then it restarted, paused for around 30+ seconds on the flashing kindle fire logo,and now its perfect.
Tip: To get into fastboot mode, the exact steps I took were:
1. Shut down Kindle completely.
2. From the kindle fire utility, select 1 and then select 1 again. It should come as waiting for device. After that plug in the kindle and let it do its things. Once the kindle fire logo pops up, keep on spamming 2 in the kindle fire utility to select fastboot mode till it lets you get in. You have to do it before it starts to shut down again.
After that, the fastboot things should be working and you can do the rest of the stuff starting from number 6.
I hope this helps some one.
JoshuaLintag said:
What if I do not have the stock charger?
I charge it using my PC?
Please help, I am lost without my kindle.
Click to expand...
Click to collapse
You need something with a higher charging output than a pc. The stock of charger puts out 1.8 amps, so you need a charger that is close to that. I know that some aftermarket iPad chargers are 2.1 amps so that may work if you can get one of those.
Sent from my Kindle Fire using xda premium
I am new to the Kindle Fire, as in I don't have one yet. But, this seems like kind of a big deal or does it only happen on rooted, customized Kindle Fires in which case Amazon probably doesn't care quite so much?
If this happens on a fully stock Fire when it goes dead I would imaging a ton of these being returned if something like this happened to gramps or someone less tech savvy...which I have a feeling is a huge number of Kindle Fire owners.
Evo_Shift said:
I am new to the Kindle Fire, as in I don't have one yet. But, this seems like kind of a big deal or does it only happen on rooted, customized Kindle Fires in which case Amazon probably doesn't care quite so much?
If this happens on a fully stock Fire when it goes dead I would imaging a ton of these being returned if something like this happened to gramps or someone less tech savvy...which I have a feeling is a huge number of Kindle Fire owners.
Click to expand...
Click to collapse
A new Kindle Fire purchased from Amazon comes with a stock wall charger. It does not come with a USB cable.
Evo_Shift said:
I am new to the Kindle Fire, as in I don't have one yet. But, this seems like kind of a big deal or does it only happen on rooted, customized Kindle Fires in which case Amazon probably doesn't care quite so much?
If this happens on a fully stock Fire when it goes dead I would imaging a ton of these being returned if something like this happened to gramps or someone less tech savvy...which I have a feeling is a huge number of Kindle Fire owners.
Click to expand...
Click to collapse
I think a more appropriate answer to your question can be found in the OP...
A couple of users have reported flashing back to the stock boot image to get out of this situation. The idea is that some ramdisks on custom ROMs may not be as efficient as stock when it comes to the battery charging software.
Click to expand...
Click to collapse
My Kindle starts up and turns off 2 seconds from turning it on.
ADB won't detect it also the KFU. help
JoshuaLintag said:
My Kindle starts up and turns off 2 seconds from turning it on.
ADB won't detect it also the KFU. help
Click to expand...
Click to collapse
This is a joke right? You're just toying with me, right? I mean, if you were serious then you wouldn't be very bright considering the answer to your problem is in the OP.
Oh, and also in this thread, WHERE I ALREADY TOLD YOU THE ANSWER!
soupmagnet said:
This is a joke right? You're just toying with me, right? I mean, if you were serious then you wouldn't be very bright considering the answer to your problem is in the OP.
Oh, and also in this thread, WHERE I ALREADY TOLD YOU THE ANSWER!
Click to expand...
Click to collapse
Maybe it's because you talked about your military background, but I get flashes of Full Metal Jacket during some of your "motivational teaching" posts...
You little scumbag!
I got your name!
I got your ass!
You will not laugh!
You will not cry!
You will learn by the numbers!
I will teach you!
Anybody else?
kinfauns said:
Maybe it's because you talked about your military background, but I get flashes of Full Metal Jacket during some of your "motivational teaching" posts...
You little scumbag!
I got your name!
I got your ass!
You will not laugh!
You will not cry!
You will learn by the numbers!
I will teach you!
Anybody else?
Click to expand...
Click to collapse
"Tough love" is better than no love at all.
Sent from my DROID BIONIC using Tapatalk
JoshuaLintag said:
My Kindle starts up and turns off 2 seconds from turning it on.
ADB won't detect it also the KFU. help
Click to expand...
Click to collapse
There will be times when I tell myself "Maybe you're being too hard on people".
Then I see stuff like this and snap out of it.
fzdolfan said:
"Tough love" is better than no love at all.
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
I'll go with that. Maybe he didn't appreciate my tongue in cheek effort at humor... or I'm dating myself by quoting a 25 year old movie.
kinfauns said:
I'll go with that. Maybe he didn't appreciate my tongue in cheek effort at humor... or I'm dating myself by quoting a 25 year old movie.
Click to expand...
Click to collapse
That's a great movie BTW. Although, my love/hate relation with it is due to my drill sergeants watching it before every cycle to get themselves "motivated"
Ah, good times
Help, after a day or so of use, I rooted my kindle and installed google apps cause I couldn't install apps from the amazon apps store, i live abroad.
So, I was done modding my kindle, and after a day of regular use, my kindle began to shut down by itself and then it turns itself on and gets stuck in boot logo, I can manage to reboot it again using the normal boot command in kindle fire utility, but after 1 or 2 seconds of being on normally, its shuts itself down again and gets back to boot logo, any idea?
I would like to restore it to the original software (6.2.2) and try all over again if its possible, I can't send it back to amazon for warranty, I live outside the US so its not an option,
Please help!
Here is a video of what happens
http://www.youtube.com/watch?v=5zYtNZkpy7Y
luishawk said:
Help, after a day or so of use, I rooted my kindle and installed google apps cause I couldn't install apps from the amazon apps store, i live abroad.
So, I was done modding my kindle, and after a day of regular use, my kindle began to shut down by itself and then it turns itself on and gets stuck in boot logo, I can manage to reboot it again using the normal boot command in kindle fire utility, but after 1 or 2 seconds of being on normally, its shuts itself down again and gets back to boot logo, any idea?
I would like to restore it to the original software (6.2.2) and try all over again if its possible, I can't send it back to amazon for warranty, I live outside the US so its not an option,
Please help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=25400963
That link will take you to a thread that will explain what your problem is and how to fix it.
luishawk said:
Help, after a day or so of use, I rooted my kindle and installed google apps cause I couldn't install apps from the amazon apps store, i live abroad.
So, I was done modding my kindle, and after a day of regular use, my kindle began to shut down by itself and then it turns itself on and gets stuck in boot logo, I can manage to reboot it again using the normal boot command in kindle fire utility, but after 1 or 2 seconds of being on normally, its shuts itself down again and gets back to boot logo, any idea?
I would like to restore it to the original software (6.2.2) and try all over again if its possible, I can't send it back to amazon for warranty, I live outside the US so its not an option,
Please help!
Here is a video of what happens
http://www.youtube.com/watch?v=5zYtNZkpy7Y
Click to expand...
Click to collapse
Well, I think we've reached a new low today. You post a question...
http://forum.xda-developers.com/showthread.php?t=1648813
... and I answer it by providing a link to a thread that not only tells you what the problem is, but also suggests possible fixes. Instead of actually trying the fix... one of which is as simple as plugging in your charger! You copy/paste the same post into a thread that already gives you the answer in the OP!
I don't like going negative in my posts, but stuff like this really makes me wonder why I take the time...
After 5s bootloop, now my kindle fire total battery die, can't use stock 1.8 amp AC charger or usb - pc, usb - iphone charger. It not show 5s bootloop now .
Any solution ?
I wish to read this topic earlier
TL;DR: Any way to fix/flash a Nexus 7 that reports it's in APX mode to Windows yet, that won't do anything else?
Backstory: I've had a 2012 Nexus 7 32gb since the day it came out (Oct 2012 or so?). Worked great for a year, loved it! Had AOKP on it, unlocked/rooted, used tons of apps, never a single problem. And then one day while I was using it to play music while charging it, out of the blue, it hard shut off while it was running, rebooted and shut off during boot and... never turned on again. Wouldn't indicate a charge, wouldn't turn on, couldn't get it to respond to any power or volume key presses, nothing.
I called Asus, and they agreed it needed to be repaired. I sent it to them, they sent me back the same unit, repaired, and said they swapped the mainboard out in the repair notes. Worked great, except the device was completely wiped, relocked, unrooted, and they removed my nice Stenheil screen protector.
I was without it long enough that I got used to not having it. Since it was completly back to stock, I decided instead that I would sell it when I found a good buyer (friend, etc), and buy the new 2013 Nexus 7 instead. I found a friend who wanted it a few days ago.
Today's Issue: I charged it over night last night so it was on a full charge this AM. I saw that I was still running 4.3 on it (hadn't really used it since I got it back in November), so I did the factory/official "OTA" update to 4.4.2 this AM. Went flawless, no issues, booted up fine. I updated all the apps on it, also worked fine.
I then decided to do a Factory Reset on it, (Thru Backup/Reset IN android, NOT Recovery). I went thru the confirmations/warnings, and then it said "Shutting Down..." and, it shut down. I let it sit for a few minutes, expecting it to boot back up (it never did). I tried to turn it on, nothing. I tried ALL combinations of power + volume, + charging cable in/out, etc. Everything possible, trust me, I scoured the web for new combinations and timing ,etc. No matter what, I never got ANYTHING on the display, no charging indicator, no recovery or bootloader, nothing. It's like the display is dead. The battery was fully charged this AM after being charged overnight so I know the battery wasn't even close to low. It's like it's completely dead no matter what I do.
I then tried to hook it up to my PC, which is setup for ADB etc, couldn't see it in ADB. In Device Manager though, it's showing as being in APX mode? So I tried holding power down for 10 seconds with it connected, and it DOES disconnect from windows, and a few seconds later, it shows up again, again in APX mode. Nothing ever appears on the display. Holding VOL down or all three buttons while plugging into PC never changes anything, no matter what, it ALWAYS shows in APX mode.
From what I'm reading online, this is a sign that the bootloader is missing or corrupt, and, that there isn't a fix for that unless you first backed up your crypto "blob" using Flatline (which I didn't even know about till today). I'm hoping that maybe what I've read is out of date? Is there perhaps a way to fix or flash this yet?
The whole thing makes little sense. All I did is update it, then reset it, all officially supported/normal things, on a bone stock tablet. It seems more like they didn't ACTUALLY fix it the first time it went back to them....
Help? AFAIK the tablet is now out of warranty. I just want to sell it and get the 2013 model! The tablet is in perfect shape, it's been used with a screen protector and case since day 1 - not a single scratch on the screen or case. :crying:
i'll take the silence to mean I'm screwed, right? :crying:
I don't know how, but it seems your bootloader is gone. (corrupted sector on the nand,maybe)
You can't do much without the proper blobs.
If I were you, would try to send it back to Asus. They are the only ones who can repair it.
Wow I can't believe it's been two months, but, I still have this tablet, still not working, Asus won't fix it for a reasonable price... anything changed on this in the last two months?
It seems like it should be possible to do something... maybe I'm just optimistic.
I want a 2013 Nexus 7 but it's hard to pull the trigger knowing my very lightly used gen1 model failed twice now.
There is no way to produce an universal blob and device specific blob creation is working so there is little to no reasons for further development.
You could fit a new motherboard 32gb ones are expensive but the 16gb are a lot cheaper
Programming is a race between engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning.
They're readily available on eBay - $35 for a used 16GB motherboard, and $50 for a 32GB board. That's how I fixed my APX bricked N7...
Whoever stumbles across my late entry, if the N7 won't boot after empty battery, no button combinations work and PC shows only APX mode - take off the back housing (it's pretty easy to do) and disconnect and reconnect the battery cable, this let me boot it up immediately...
(my N7 however was plugged over night to charge before I attempted this unplug but actually didn't show up the charging indicator and wasn't bootable, surprisingly it was charged already half when I finally could boot it up)
Sent from my OnePlus5T using XDA Labs
Apparently it is possible without having done the backup first, at least for some people.
https://forum.xda-developers.com/nexus-7/general/tutorial-how-to-unbrick-nexus-7-blob-bin-t4083879
I got my phone yesterday, and it was working for about 18 hours. All of a sudden I picked it up at work and it is no longer turning on. I tried plugging it into the charger, holding volume up + power, holding volume down plus power, but nothing worked. Has anyone else had this issue? I called Google support and they are going to send a new phone, but this doesn't give me a lot of confidence in this phone.
someone on reddit posted something similar. ended up RMA'ing the device as well. not sure what's up with this scenario - loose battery maybe?
Google is sending a replacement unit. It really sucks because I cut my sim to be nano from the nexus 5, so I can't go back to my old phone at all.
shaklee3 said:
Google is sending a replacement unit. It really sucks because I cut my sim to be nano from the nexus 5, so I can't go back to my old phone at all.
Click to expand...
Click to collapse
Use a sim adapter
shaklee3 said:
Google is sending a replacement unit. It really sucks because I cut my sim to be nano from the nexus 5, so I can't go back to my old phone at all.
Click to expand...
Click to collapse
Google sends a replacement unit overnight. Should arrive the next day, so you won't have a phone for at least 1-2 days.
jaidev.s said:
Use a sim adaptor
Click to expand...
Click to collapse
Thanks. I ordered an adapter in the meantime just in case something happens on the next phone.
zephiK said:
Google sends a replacement unit overnight. Should arrive the next day, so you won't have a phone for at least 1-2 days.
Click to expand...
Click to collapse
I'm having this issue as well. Phone worked well since Oct 29, then all of a sudden it shut down and will do nothing. I've requested a new device and Google support is telling me the phone won't ship until the 12th, when the rest of the Google Play Store orders ship. I stole my daughters phone in the mean time, but I can't wait a full week to receive the replacement as one of us will do without till it arrives. I may request a refund and buy a phone locally. Sad-- I waited a month for this phone, ordered on launch day. I shouldn't wind up in the regular queue to get the phone replaced. Poor support if you ask me.
Same thing for my N6p, picked it up and it was off. It's a brick now.
I called and was told they would ship me another, I just saw that its going to be a few days until it gets shipped out.
I transferred my Straight talk to the new nano sim, now I cant go back to my N5.
No phone for a few days.
Dang
Same exact problem. Phone was over 80% charged. Picked it up off of my desk at work to check the time and nothing. Just a brick.
Update*** I hooked the thing to power and nothing. So I just sat here at my desk for several minutes holding down the power button and the damn thing finally came back on. But I had to hold it for a very very long time, not the normal 10-30 seconds like it should take to do a hard power off. I'm talking minutes.
deanb1234 said:
Same exact problem. Phone was over 80% charged. Picked it up off of my desk at work to check the time and nothing. Just a brick.
Update*** I hooked the thing to power and nothing. So I just sat here at my desk for several minutes holding down the power button and the damn thing finally came back on. But I had to hold it for a very very long time, not the normal 10-30 seconds like it should take to do a hard power off. I'm talking minutes.
Click to expand...
Click to collapse
I had the same problem, put the phone down on my desk and picked up a brick. Tried deanb's method out of boredom and desperation, basically, and it actually worked for me as well. I think I held my power button for about a minute and a half before it booted back up. Very weird.
same
Same thing just happened to me, thank you so much for the tip!
Lets hope it will not be a recurrent problem.
Hold Power button+volume down until it turns on....it might take a min. or more.....it happened to me
IF your guys phones turns on, I would still suggest RMA'ing it back to google. There's obviously something wrong with it, don't be lazy. You'll thank me later
My sons just did the same thing. He had 15% and put it in power save and cut the screen off and it would not come back on. Charged it for a while and then read this post. Held the power button down for around a minute and Bam. Working fine now, powering on and off as normal. Thanks alot for the info deanb1234. Still gonna get rma, bad thing he got it from Huawei not the google store and their cs is the worst i have ever seen.
Had the same thing happened. Thankfully it was within 14 days so I returned and got a new one immediately. (Got it from a carrier)
I am having the problem right now. The phone was fully charged and I used it for 10 minutes this morning. The screen went black after 1 minute as normal. I used the finger print reader about 15 minutes later and it would not turn on. It is essentially dead as a brick. I will try to hold the power button + Vol down for over a minute to see it it works. The phone was working flawlessly beforehand. I did not have any problems whatsoever.
My question. Will I have a problem getting Google to RMA the phone if I get it revived? Can they tell if it is currently working? I would like to RMA the phone regardless just in case it is faulty. I purchased the phone in late Oct 2015 and I did not buy the insurance.
Edit: I got it to work again after holding down the power and volume down. Anyone find a cause for this problem? I was systemless rooted for several weeks but everything else was stock.
Wanna ask all you folks who are just sending phones back willy nilly. Are you wiping the phone of your personal data such as Google account etc? All you really have to do is just hold the power button for a while and the phone will turn on. It's not really a defect (well technically perhaps), but why not turn the phone back on and factory reset it before sending it back? Some dude in a warehouse is probably gonna turn your phone back on and he now has access to your Gmail account and God knows what else (if you don't have a screen lock). What am I missing here.
Sent from my Nexus 7 using XDA Free mobile app
I was planning to use android device manager to wipe device if I could not get it to respond. Factory wipe reset along with flashing system image is best option if possible.
systemless root may be cause in my situation . I was using older 2.62 apk. I will give it another few weeks and try new root when Jan security update is released before RMA.
biggolfer said:
I am having the problem right now. The phone was fully charged and I used it for 10 minutes this morning. The screen went black after 1 minute as normal. I used the finger print reader about 15 minutes later and it would not turn on. It is essentially dead as a brick. I will try to hold the power button + Vol down for over a minute to see it it works. The phone was working flawlessly beforehand. I did not have any problems whatsoever.
My question. Will I have a problem getting Google to RMA the phone if I get it revived? Can they tell if it is currently working? I would like to RMA the phone regardless just in case it is faulty. I purchased the phone in late Oct 2015 and I did not buy the insurance.
Edit: I got it to work again after holding down the power and volume down. Anyone find a cause for this problem? I was systemless rooted for several weeks but everything else was stock.
Click to expand...
Click to collapse
Do you send your phone to google anyways? or just cancel the replacement?
GMScreech said:
Do you send your phone to google anyways? or just cancel the replacement?
Click to expand...
Click to collapse
No, I did not return the phone and no issues have occurred since. I suspect it was a problem due to rooting the phone. I was using a beta version of SuperSU.
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 ?