Hey guys,
Been looking around on the forum but couldn't find any info about this.
I recently purchased a Le 3 Pro and was actually working well. I had a few random reboots (I read this was something normal - happened in Snapchat, but after clearing the app cache all was well again).
Anyway, so today at work I noticed the phone just rebooted for no reason, but then it just kept rebooting and rebooting.
I have the stock Chinese rom (it's the X720 vesion by the way) so I have not done any rooting. Was planning to, but thought I'd give stock a run for its money.
So, not I'm stuck with a phone that's stuck in reboot mode.
I can get into fastboot and I tried flashing TWRP into Recovery, and that "seemed" to work (the command came back successful) however when going into recovery mode, it's just the LeEco Recovery and it doesn't do anything. So, I have to power cycle again and then gets stuck in the reboot cycle.
I don't think OEM unlocking was enabled, but seeing I can't get into the OS I can't check. The bootloader was unlocked upon arrival.
I turned the phone off (volume up and down + power button)
Now, I also tried putting the phone into the charger, (it was still at 85%-ish as far as I can remember) however it doesn't seem to be charging. So I'm thinking there may be a hardware issue.
However, maybe a software solution... never know, so if anybody DOES know - highly appreciated
Thx
EDIT: so I've been fiddling around using some guides on this forum... nothing...
C:\Users\Ryan\Desktop\LEMAX2>fastboot devices
403077b2 fastboot
C:\Users\Ryan\Desktop\LEMAX2>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (787 KB)...
OKAY [ 0.048s]
writing 'aboot'...
OKAY [ 0.023s]
finished. total time: 0.079s
C:\Users\Ryan\Desktop\LEMAX2>fastboot oem unlock-go
...
OKAY [ 0.009s]
finished. total time: 0.010s
C:\Users\Ryan\Desktop\LEMAX2>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.092s]
finished. total time: 0.094s
** NOTE --> this was always showing unlocked (even if not doing any of these steps).
C:\Users\Ryan\Desktop\LEMAX2>fastboot flash recovery twrp-3.1.0-0-x2.img
target reported max download size of 536870912 bytes
sending 'recovery' (59348 KB)...
OKAY [ 1.284s]
writing 'recovery'...
OKAY [ 0.407s]
finished. total time: 1.697s
Click to expand...
Click to collapse
This would normally allow me to boot into TWRP recovery. however it just takes me to the Stock Recovery (and does nothing - ie: there is no option to do anything).
Have you tried booting into TWRP instead of flashing it? Try "fastboot boot recovery twrp-3.1.0-0-x2.img"
EDIT: What recovery you are using?
Presterin said:
Have you tried booting into TWRP instead of flashing it? Try "fastboot boot recovery twrp-3.1.0-0-x2.img"
Click to expand...
Click to collapse
Yes, tried that as well. Afterwards I tried:
Fastboot reboot
And also just manually booting into Recovery straight from the Fastboot screen (volume up + power).
Both times it just takes me to the "standard" LeEco Recovery Screen (it just says LeEco, some Chinese text and "Recovery") and doesn't allow me to do anything.
Also, I tried multiple chargers, no sign of the phone being charged at all (no sounds, no on screen display, no LED).
So, basically all I can do is turn it on and watch it reboot over and over again, or go into Fastboot, do some commands (which all seem to do nothing - although I get an "OK" status) or go into the standard LeEco Recovery (even after flashing TWRP into Recovery).
I'm seriously starting to think this is just a Hardware malfunction. However, I've scoured the net and haven't really found a case like mine.
Are you trying to flash Le Max 2 recovery on Le Pro 3? I don't know if it should work, but I would try one from this forum meant for this phone. For example this: https://drive.google.com/file/d/0B7uXK7jfW17nZGRCWmFmZU9NVWs/view (link copied from official LineageOS13 thread)
Presterin said:
Are you trying to flash Le Max 2 recovery on Le Pro 3? I don't know if it should work, but I would try one from this forum meant for this phone. For example this: (link removed) (link copied from official LineageOS13 thread)
Click to expand...
Click to collapse
No. Actually my dad and girlfriend have the Le Max 2 and had to install a new ROM on one of them, hence the LEMAX2 directory (where I'm just centralizing the flash files).
Basically I just want the stock (China) rom for the X720 -as that seemed to be working perfectly for me... for now (well, not now.. but you know what I mean).
I would try clearing all the data from recovery. See if that gets it to "reset".
If that doesn't work you could see about getting a hold of an "update.zip", pushing it to the device and flashing it from the stock recovery to see if it gets it out of the loop.
slgooding said:
I would try clearing all the data from recovery. See if that gets it to "reset".
If that doesn't work you could see about getting a hold of an "update.zip", pushing it to the device and flashing it from the stock recovery to see if it gets it out of the loop.
Click to expand...
Click to collapse
thanks for the answer, would you mind pointing me in the direction of how to "clear the data from recovery"?
Also, I'm not sure if I tried, by ADB doesn't work in Fastboot (to push the zip). At the moment, even in stock recovery I can't do anything.
EDIT: so, home from work. I've had the phone OFF for about 12 hours now. Plugged it in to charger and now I get an LED. Boots up normally, but battery was at 0%. I have no idea what's going on or why it now works, or even why the battery is at 0% (it was at 85% or so when it "crashed" yesterday I believe). Is this a known issue by chance? Or does this seem like a one off type of thing?
Ryanx0r said:
No. Actually my dad and girlfriend have the Le Max 2 and had to install a new ROM on one of them, hence the LEMAX2 directory (where I'm just centralizing the flash files).
Basically I just want the stock (China) rom for the X720 -as that seemed to be working perfectly for me... for now (well, not now.. but you know what I mean).
Click to expand...
Click to collapse
Can't get over "x2" in recovery image file, it points to Le Max 2 recovery.
Ryanx0r said:
thanks for the answer, would you mind pointing me in the direction of how to "clear the data from recovery"?
Also, I'm not sure if I tried, by ADB doesn't work in Fastboot (to push the zip). At the moment, even in stock recovery I can't do anything.
EDIT: so, home from work. I've had the phone OFF for about 12 hours now. Plugged it in to charger and now I get an LED. Boots up normally, but battery was at 0%. I have no idea what's going on or why it now works, or even why the battery is at 0% (it was at 85% or so when it "crashed" yesterday I believe). Is this a known issue by chance? Or does this seem like a one off type of thing?
Click to expand...
Click to collapse
There are some odd issues with this phone and charging. I'm not sure why it would bootloop and then die, only to charge and boot up again finally. Consider yourself fortunate that it works now! I ordered an Anker charger off of amazon and now use that for quick charging instead of the stock charger just in case...
What is the solution for this?
Ryanx0r said:
Yes, tried that as well. Afterwards I tried:
Fastboot reboot
And also just manually booting into Recovery straight from the Fastboot screen (volume up + power).
Both times it just takes me to the "standard" LeEco Recovery Screen (it just says LeEco, some Chinese text and "Recovery") and doesn't allow me to do anything.
Also, I tried multiple chargers, no sign of the phone being charged at all (no sounds, no on screen display, no LED).
So, basically all I can do is turn it on and watch it reboot over and over again, or go into Fastboot, do some commands (which all seem to do nothing - although I get an "OK" status) or go into the standard LeEco Recovery (even after flashing TWRP into Recovery).
I'm seriously starting to think this is just a Hardware malfunction. However, I've scoured the net and haven't really found a case like mine.
Click to expand...
Click to collapse
Can you reply me as soon as possible the solution for the constant reboots.
shivaraju07 said:
Can you reply me as soon as possible the solution for the constant reboots.
Click to expand...
Click to collapse
No solution. It "died" again (and to think I only used it for about 2 days).
I got into contact with the seller on Ali Express, I was told to send it back so they could look into it.
But Ali Express paid me back (while the seller was still looking into the problem). I didn't 'really' want my money back, just wanted the phone and an explanation - however, once I was paid back, the RMA was stopped and I was told to place a new order. Trying to do so, resulted in the seller letting me know that they no longer make the LeEco Pro 3.
So... I just went for OnePlus 5 instead - great phone
Ryanx0r said:
however, once I was paid back, the RMA was stopped and I was told to place a new order. Trying to do so, resulted in the seller letting me know that they no longer make the LeEco Pro 3.
Click to expand...
Click to collapse
I've read that LeEco stopped making phones. What they sell are the remaining stock, that it.
ZeblodS said:
I've read that LeEco stopped making phones. What they sell are the remaining stock, that it.
Click to expand...
Click to collapse
It's a real shame, because they're actually really good phones. My girlfriend has one and is really happy with it. It's the LeMax 2, but still a nice piece of (cheap, but great quality) hardware.
I have leeco le s3. After update Google Play Services, my phone always restarted continuosly when using GPS. Is that same with your issue?
InitialDS said:
I have leeco le s3. After update Google Play Services, my phone always restarted continuosly when using GPS. Is that same with your issue?
Click to expand...
Click to collapse
Have you solved the problem?
Related
My Nexus 4 is in a sorry state and I'm looking for some advice before I RMA, just in case it can be saved. It's very odd.
My N4 was on charge overnight and my alarm went off this morning as normal, Cancelling it crashed the clock app, and when I unlocked the device I was greeted with a cascade of crashing services. So I turned the device off but it will not start and hangs on the Google logo with a padlock icon displayed at the bottom of the screen, The device is not encrupted and the battery is fully charged.
I am running stock 4.2.2 with an unlocked bootloaded and the device _will_ boot to fastboot mode. Selecting the Recovery option displays the Android red warning triangle icon.
So I fired up the Nexus 4 Toolkit and this will let me flash a temporary recovery image. But neither CWM and TWRP can mount /cache, /system, /data or /sd-card, so a factory reset/Dalvik wipe etc will not work. Very odd.
As a last resort I downloaded the official 4.2.2 image but the toolkit cannot flash it and it displays:
Starting Flash Process..
Flashing Bootloader Image..
sending 'bootloader' (2188 KB)...
OKAY [ 0.140s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.156s
An Error Occured
I am out of ideas so any suggestions are welcome.
rec71 said:
My Nexus 4 is in a sorry state and I'm looking for some advice before I RMA, just in case it can be saved. It's very odd.
My N4 was on charge overnight and my alarm went off this morning as normal, Cancelling it crashed the clock app, and when I unlocked the device I was greeted with a cascade of crashing services. So I turned the device off but it will not start and hangs on the Google logo with a padlock icon displayed at the bottom of the screen, The device is not encrupted and the battery is fully charged.
I am running stock 4.2.2 with an unlocked bootloaded and the device _will_ boot to fastboot mode. Selecting the Recovery option displays the Android red warning triangle icon.
So I fired up the Nexus 4 Toolkit and this will let me flash a temporary recovery image. But neither CWM and TWRP can mount /cache, /system, /data or /sd-card, so a factory reset/Dalvik wipe etc will not work. Very odd.
As a last resort I downloaded the official 4.2.2 image but the toolkit cannot flash it and it displays:
Starting Flash Process..
Flashing Bootloader Image..
sending 'bootloader' (2188 KB)...
OKAY [ 0.140s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.156s
An Error Occured
I am out of ideas so any suggestions are welcome.
Click to expand...
Click to collapse
I suggest you leave it as is and OEM lock it before you send it in. If they see its OEM locked they shouldn't give you a problem with it
brandonc0526 said:
I suggest you leave it as is and OEM lock it before you send it in. If they see its OEM locked they shouldn't give you a problem with it
Click to expand...
Click to collapse
It won't relock.
It's like it's read-only.
rec71 said:
It won't relock.
It's like it's read-only.
Click to expand...
Click to collapse
Hmmm. Try booting into TWRP from the toolkit and flashing a rom. If that doesn't work just try wiping everything and toggling/untoggling all the mounts. I had this issue on my old galaxy S and wiping did the trick, although I had to flash my ROM again
Strange. TWRP asks for a password - is this normal? The device has never had encryption enabled. But if I skip this I still cannot mount or access any part of the storage.
Same error. Have you find any solution?
Hello, did you find any solution? I just had the same exact problem. I wiped it through fastboot but when I try to flash the image, I get the same error
rec71 said:
My Nexus 4 is in a sorry state and I'm looking for some advice before I RMA, just in case it can be saved. It's very odd.
My N4 was on charge overnight and my alarm went off this morning as normal, Cancelling it crashed the clock app, and when I unlocked the device I was greeted with a cascade of crashing services. So I turned the device off but it will not start and hangs on the Google logo with a padlock icon displayed at the bottom of the screen, The device is not encrupted and the battery is fully charged.
I am running stock 4.2.2 with an unlocked bootloaded and the device _will_ boot to fastboot mode. Selecting the Recovery option displays the Android red warning triangle icon.
So I fired up the Nexus 4 Toolkit and this will let me flash a temporary recovery image. But neither CWM and TWRP can mount /cache, /system, /data or /sd-card, so a factory reset/Dalvik wipe etc will not work. Very odd.
As a last resort I downloaded the official 4.2.2 image but the toolkit cannot flash it and it displays:
Starting Flash Process..
Flashing Bootloader Image..
sending 'bootloader' (2188 KB)...
OKAY [ 0.140s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.156s
An Error Occured
I am out of ideas so any suggestions are welcome.
Click to expand...
Click to collapse
Don't use a toolkit, use the guide posted in the general section, toolkits are often very faulty as they only tend to work on working devices
Sent from my Nexus 4 using xda app-developers app
Same problem here, tried flashing everything through fastboot,
"fastboot flash recovery recovery-twrp-2.5.0.0-mako.img
sending 'recovery' (7510 KB)...
OKAY [ 0.473s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.479s"
Anything I flash I get the same response.
Any help would be appreciated
This is likely an emmc hardware failure
I've seen something very similar happen a couple of times with people on the one x.
Bootloader magically relocked itself. All partitions only read only. Unable to flash anything or issue lock/unlock commands
Sent from my Nexus 4 using xda app-developers app
highessupremacy said:
Same problem here, tried flashing everything through fastboot,
"fastboot flash recovery recovery-twrp-2.5.0.0-mako.img
sending 'recovery' (7510 KB)...
OKAY [ 0.473s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.479s"
Anything I flash I get the same response.
Any help would be appreciated
Click to expand...
Click to collapse
I'm having the exact same issue. Going to try to warranty it but since it the bootloader can't be relocked I have the feeling I'm screwed.
remote flash write failure
Same issue here.
My phone was unlocked and rooted, with stock firmware. I haven't made any changes to my phone for months since I re-rooted after 4.2.2 was released.
Had some apps crashing yesterday afternoon, not a big deal I thought, I'll just reboot. When I rebooted, the phone got stuck on the nexus boot screen - left it for hours and nothing.
Tried clearing the cache and doing a factory reset, no effect at all. Today, I tried reflashing, erased all the partitions first, but couldn't flash anything. Tried stock firmware first, but also custom recovery partitions and custom boot roms. Nothing.
Same issue here. Can't flash anything, I always get "FAILED (remote: flash write failure)" I also cannot re-lock the bootloader. I guess I will have to send it back for warranty repair to Google/LG?
This is the only thread I could find on this issue, I wonder if some recent app update broke my N4?
nothing to add besides same issue here. I got a google services failed message that I couldn't clear so I turned off my phone and then stuck on X. Haven't even installed a new app or anything in a couple of weeks. I have tried command prompt method and toolkit and both give flash write failure. I have cleared everything via command prompt and same result. Always told you cannot brick a Nexus...
Did you try to connect via adb after fastbooting to CWM (or even on X logo)?
We could compare our kernel logs then, hope it might clarify something...
Had any luck this far? I've got my nexus bootloader unlocked but not rooted, and I fear it will happen to me too.
Same problem here.
I believe I was able to fastboot erase /userdata but every 'flash' command fails. I am able to relock it though so I will try to send it in.
Good thing I kept my Galaxy Nexus and I was able to fit my micro SIM into it
Am I screwed?
Hey guys, another affected Nexus 4 user checking in. Same exact symptoms: was charging, checked something on it, saw a cascade of force closes. Shut it down, then it wouldn't boot past the Google screen. At one point I got it past that to the X screen, but it was stuck there indefinitely (for hours).
I'm running stock 4.2.2 with an unlocked bootloader. Same issues when trying to do anything over fastboot. Had the same idea to flash back to stock with no luck.
So... am I just screwed out of a phone? Or has anyone had luck getting it replaced?
This sounds like an simular issues my LG optimus G had. I would have to flash the misc.img in fastboot to get it to work again due to the misc partition getting corrupt Has anyone tried that yet?
Sent from my HTC One using Tapatalk 4 Beta
Just got off the phone with Google Play support. They had me run through a few tests (boot to fastboot, go into recovery, try booting from there; boot to fastboot, go into recovery, factory reset, reboot). Same thing: stuck on the "x" screen. I mentioned I wasn't rooted, but they didn't ask about the bootloader being unlocked. They went ahead and treated it as a normal in-warranty RMA. They're sending a new Nexus 4, and then I send the defective one back once it arrives.
If you have this issue with a Nexus 4 bought from Google Play, I suggest you call Google Play hardware support at (855) 836-3987. They were super friendly and helpful. While I'm bummed something went wrong with my phone, I'm glad I don't have to buy a new one.
---------- Post added at 09:17 PM ---------- Previous post was at 09:14 PM ----------
XsMagical said:
This sounds like an simular issues my LG optimus G had. I would have to flash the misc.img in fastboot to get it to work again due to the misc partition getting corrupt Has anyone tried that yet?
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
I don't see a misc.img in the stock image from Google for the Nexus 4. But anything else I tried to do via fastboot failed, which I've never had before.
I had the same exact issue experienced with the original poster. The apps were crashing on me like crazy. I was at the dog park. I remember the only app that was being updated at that time was AirDroidv2 just literally like 2 minutes ago before the google apps started to go crazy. I started to shut it down and boot it back up. I got stuck on the "X" screen. after an hour, i went home and tried the toolkit. then i went manual with cmd. all i get is "FAILED (remote: flash write failure)" whenever i attempt to flash it.
after a while, the OS wasn't even booting up. No "google" logo or "X" logo. Only i got was the bootup into fastboot. Now it doesn't even power up unless i connect the usb.
curious, is anyone hearing any rattling sounds in their device and/or red led dot when connecting to usb? I fear it's a bad connection to the battery.
Count me in as one of the unlucky folks as well. I noticed my N4 was auto-updating some apps last night, then later when I went to pick it up I couldn't get the screen to turn on. Held down power until it rebooted, then was stuck at the Google logo and never got any farther. Bootloader mode works, trying to boot into recovery gives a black screen. Tried to re-flash recovery.img from stock but got the same error as others: "FAILED (remote: flash write failure)"
I called Play Support and they were helpful in getting the RMA process started. Unfortunately I expressed some concern about my cracked glass back affecting the return and the CSR mentioned that he'd have to escalate. (As a point of reference, my glass cracked a few months ago). We discussed how common cracked glass backs are with the N4 and how I hoped it wouldn't affect my RMA as the device has been working fine for months. He's waiting to hear back from the specialist before we can move forward.
Really hoping that everything works out.
UPDATE: Warranty claim denied due to the broken glass. Not sure what my next step is. :/
Ok I'm pretty good with Windows but I know nothing at all about Android. So I got this tablet off a site the guy said it needed a new motherboard which I never heard of. He said he didn't do anything to it it just stopped loading one day.
So I go all over and find all the little tricks to try and make it work. I did the power and volume button thing. I tried to reset it with the Rootkit program. I even tried to get SDK but that won't run on my PC for some reason.
Anyway what is happening is the tablet gets stuck on the Google word. I see nothing before that and it stays on that forever. I waited 15 minutes and nothing. When I try the rootkit program it gets stuck when it tries to reboot. The tablet just never turns back on. I can get it to boot into the bootloader screen. But nothing after that is functional. So what are my options here? If any. I'm hoping I can fix it. I am pretty quick at picking stuff up but this one is really stumping me.
Any help or advice or direction would be GREATLY appreciated. Thanks
Ok so when I do the Soft Brick Flash Stock + Unroot everything works up until the command prompt attempts to reboot. It turns off and never turns back on The last paragraph of the cmd prompt reads as follows and is what may be the issue. It reads
sending 'bootloader' <2100kb>
FAILED <remote: Bootloader is locked.>
finished. total time:0.145s
rebooting into bootloader...
OKAY [ 0.020s]
So I'm thinking it has something to do with this FAILED section as everything else works with no issues. Also after this I'm stuck at the < waiting for device > and my tablet doesn't power back on. I have a 100% charge and did all the driver stuff first.
Any ideas?????
Nexus 7 2012
Cr8zyJay said:
Ok I'm pretty good with Windows but I know nothing at all about Android. So I got this tablet off a site the guy said it needed a new motherboard which I never heard of. He said he didn't do anything to it it just stopped loading one day.
So I go all over and find all the little tricks to try and make it work. I did the power and volume button thing. I tried to reset it with the Rootkit program. I even tried to get SDK but that won't run on my PC for some reason.
Anyway what is happening is the tablet gets stuck on the Google word. I see nothing before that and it stays on that forever. I waited 15 minutes and nothing. When I try the rootkit program it gets stuck when it tries to reboot. The tablet just never turns back on. I can get it to boot into the bootloader screen. But nothing after that is functional. So what are my options here? If any. I'm hoping I can fix it. I am pretty quick at picking stuff up but this one is really stumping me.
Any help or advice or direction would be GREATLY appreciated. Thanks
Ok so when I do the Soft Brick Flash Stock + Unroot everything works up until the command prompt attempts to reboot. It turns off and never turns back on The last paragraph of the cmd prompt reads as follows and is what may be the issue. It reads
sending 'bootloader' <2100kb>
FAILED <remote: Bootloader is locked.>
finished. total time:0.145s
rebooting into bootloader...
OKAY [ 0.020s]
So I'm thinking it has something to do with this FAILED section as everything else works with no issues. Also after this I'm stuck at the < waiting for device > and my tablet doesn't power back on. I have a 100% charge and did all the driver stuff first.
Any ideas?????
Nexus 7 2012
Click to expand...
Click to collapse
Try unlocking the bootloader. It says your bootloader is still locked.
riggerman0421 said:
Try unlocking the bootloader. It says your bootloader is still locked.
Click to expand...
Click to collapse
I did and it doesn't boot back up after it completes the unlock. The tablet just stays powered down. I am going to try and do it manually instead of the Root toolkit
Hi, You guys may remember me from around 2 years ago when I was scrambling for answers about my nexus 7 2012 edition being hard bricked from "Fastboot Erase Bootloader". Well shortly after that I got the motherboard replaced everything worked fine after that. In fact the tablet worked flawlessly (whilst un-rooted) for over 2 whole years.
But then...
in the last 3 days something very unusual started happening. After downloading an audio recorder app the tab started crashing and freezing while it was in a locked state (screen off and supposed to be on stand by mode). The only way I could get out was a long power button press. Then this issue began to get progressively worse. The tablet started freezing/crashing whilst I was doing normal stuff on it and sometimes the device would automatically shut off while frozen(and it was doing this repetitively). I did some basic diagnostics on it including taking off the back cover for inspection (didn't see anything unusual however I am not an expert on motherboards) so I then booted in safe mode which didn't change anything. After that I tried clearing the system cache. That didn't change anything either. Then suddenly out of the blue the tab started getting stuck on the google logo. It does feel like my tab is going through a slow and painful death. I have not rooted this tab or updated the android version or anything of that sort since the motherboard replacement and I am absolutely clueless as to what could have happened here. And this time It literally doesn't make any sense to me. Does this really mean two motherboards F***ed in a row?
I would be very grateful if anyone could enlighten me on this new problem and "safe" steps to take in resolving it (if it is reversible).
PS: I have ADB (sideload mode only) and Fastboot up and running.
Update
I think I have made a break through. I finally decided to clear the data so I went in recovery mode and pressed the option to wipe data and factory reset however it got stuck on "Formatting data" so eventually I pressed the power button to force restart it and this time it actually got passed the google screen but then I was stuck with an endless 4 circles animation playing so I pressed the power button again and this time it booted to the google screen and then went black and showed the google screen again and black again over and over again. Now I am even more confused however I am not sure if this is still a hardware problem.
Any ideas guys????
I've had lots of issues with my first nexus 7, though never as bad as yours. Factory reset always solved it at least temporarily.
That being said, recently got tired of staying stock and jumped to the unofficial PureNexus (Android M) + pico Gapps + parrotmod + DC kernel and the N7 has been running smoother/faster than ever. Since you can't even get into the normal OS at this point, and you can clearly access the bootloader and recovery, why don't you try out a custom ROM setup?
Well thanks but unfortunately that is not much use
Now I can't even get the boot loader unlocked, I type "fastboot oem unlock" and I get this
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: (Unknown error code))
finished. total time: 6.733s
Also the factory reset option in recovery appears not to work (still hangs at the 4 colored circles animation), clearing cache option gets stuck, I don't know which sideload would work.
Any clue what the hell is going on here?
last night i got the notification to say that i was able to update to 7.0 and i was so excited that i kinda forgot about xposed and stuff and now
the phone is completely useless it wont turn on it just does nothing, when its charging the white light flashes but still nothing Please help
Can you connect your phone to a computer and see if adb/fastboot still senses your device, or whether your device still shows up (or reports as a Qualcomm HS-USB)?
echo92 said:
Can you connect your phone to a computer and see if adb/fastboot still senses your device, or whether your device still shows up (or reports as a Qualcomm HS-USB)?
Click to expand...
Click to collapse
nope not seeing it
Hmm, so you're not getting anything showing up in Device Manager (like in this thread https://forum.xda-developers.com/moto-g4-plus/help/help-xt1642-hard-bricked-help-t3498943 )?
I am not familiar with the procedure of how to unbrick a device like this, vache has uploaded a blank flash file (https://forum.xda-developers.com/showpost.php?p=70701015&postcount=1975), I hope someone else can guide you on the procedure to unbrick your phone if you need such a file.
Sounds crazy, but push the power button for 2-3 minutes.... Dont know why, but worked for me in the past.
bullfinch110 said:
Sounds crazy, but push the power button for 2-3 minutes.... Dont know why, but worked for me in the past.
Click to expand...
Click to collapse
thankyou it worked perfectly
The same here after update!
I have a Moto G4 Plus, Product: athene_16mp XT1644 64GB P2A
Since last update (Nouga) my phone doesn't pass the bootloader screen. Connected to my PC, only fastboot commands works as adb don't see it. The recovery mode is dead, every time I try to enter it says:
Failed to validate recovery image. Error: Failed to pass validation, backup to fastboot. Boot up failed.
I searched the forum to find the original rom image but as I didn't Check 'Allow OEM Unlock' in Android Settings > Developer, I can't install any image from there.
Any help?
alemangioni said:
I have a Moto G4 Plus, Product: athene_16mp XT1644 64GB P2A
Since last update (Nouga) my phone doesn't pass the bootloader screen. Connected to my PC, only fastboot commands works as adb don't see it. The recovery mode is dead, every time I try to enter it says:
Failed to validate recovery image. Error: Failed to pass validation, backup to fastboot. Boot up failed.
I searched the forum to find the original rom image but as I didn't Check 'Allow OEM Unlock' in Android Settings > Developer, I can't install any image from there.
Any help?
Click to expand...
Click to collapse
If fastboot still works, perhaps try this fastboot Nougat image, see if that'll flash? https://forum.xda-developers.com/moto-g4-plus/how-to/android-7-0-install-nougat-official-t3531612
It requires you booting into bootloader (so power down your device, wait 5 seconds then hold the volume down and power button, should then boot into bootloader), so it might flash a working recovery and system onto your device.
bullfinch110 said:
Sounds crazy, but push the power button for 2-3 minutes.... Dont know why, but worked for me in the past.
Click to expand...
Click to collapse
I believe there are two possible reasons...
Either 2-3 minutes forces a fully hard reset.
Or
If you have a really really flat battery sometimes as it charges and then boots up it gets stuck in repeated reboot since effort to boot drains more than it can charge in that time, so holding power button holds boot sequence long enough for battery to gain enough charge to allow boot to work..
Both are just my opinions so might be completely wrong
I think it's Option no1, because in my case the battery was nearly full charged.
Nevertheless... One guy happy to have helped, the other guy happy to have reanimated his phone:laugh:
Hi, many thank in advance for people making this forum alive and developer who working on it.
I received a P9 lite from a friend of mine and I dont realy know what he tried to do but. The phone show me warning about the unlock but can't boot on system and when i tried to flash TWRP on it, the phone show me multiples errors in terminal (when i tried to flash boot with a stock room)
Bref, I don't know the actual state of any partition and i have to back from scratch about everything on it. What could you suggest to do about ? Some verifications and others things ?
The only mode i can boot on is recovery fast boot (the white page) and showing me everything is unlocked. And when i let it boot for a while i finally boot on eRecovery.
I am all your to test and give you information about.
Many thanks in advance for any help.
(I'm not so bad in terminal things by the way)
Buy dc phoenix and force the update.app to it. Cost about 15~ $ saved my phone last day also
What error did you had when you tried to install TWRP?
Also, have you tried to put in the micro SD the stock UPDATE.APP in the dload folder and installing it pressing all the 3 buttons?
@Kcetin20 Using a paid service it's the last resource, before that I think it's better to try everything possible to restore the phone
quickly, cause it's late here in france,
Thanks for your reply.
@Potato997 : I get no error when i flash, simply no boot when volume up and down simultaneous
terminal :
Code:
F:\PROJETS\huawei p9 lite\__OK>fastboot flash recovery "F:\PROJETS\huawei p9 lite\__OK\TWRP.img"
target reported max download size of 471859200 bytes
sending 'recovery' (27434 KB)...
OKAY [ 0.937s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.948s
what is this procedure ?
Also, have you tried to put in the micro SD the stock UPDATE.APP in the dload folder and installing it pressing all the 3 buttons?
Click to expand...
Click to collapse
@Kcetin20 : thanks, i'll try any free option before. But it's good to know there are software or solutions to force in last resort
@bumpshoveit try to see if you can force him in 2 buttons menu, shutdown phone > press volume + and volume - > press power key > if this leads you to a update menu you can flash the phone thought a SD card.
bumpshoveit said:
quickly, cause it's late here in france,
Thanks for your reply.
@Potato997 : I get no error when i flash, simply no boot when volume up and down simultaneous
terminal :
what is this procedure ?
@Kcetin20 : thanks, i'll try any free option before. But it's good to know there are software or solutions to force in last resort
Click to expand...
Click to collapse
Command not allowed when flashing in fastboot usually means the bootloader is locked.
So unlock your bootloader and try to flash TWRP again.
bumpshoveit said:
quickly, cause it's late here in france,
Thanks for your reply.
@Potato997 : I get no error when i flash, simply no boot when volume up and down simultaneous
terminal :
Code:
F:\PROJETS\huawei p9 lite\__OK>fastboot flash recovery "F:\PROJETS\huawei p9 lite\__OK\TWRP.img"
target reported max download size of 471859200 bytes
sending 'recovery' (27434 KB)...
OKAY [ 0.937s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.948s
what is this procedure ?
@Kcetin20 : thanks, i'll try any free option before. But it's good to know there are software or solutions to force in last resort
Click to expand...
Click to collapse
that procedure is you download a stock rom, extract update.app from it, put that file in a folder called "dload" on your sdcard (create the folder if it doesn't exist) and then reboot by holding volume up and down and power.
however, you need to know what localization it is (cXXX)
@Cetin20 @mjz2cool Thanks for procedure. I just took a quick look before go to work (yes i don't care, i got a nexus 5X working like a charm ME, hahaha). So I pulled out the SD card and i already found on it a fodler named dload and update.app inside. I don't remember any purpose of installation. The only I have is Huawei eRecovery trying to connect to Wifi and download but as you can imagine; nothing append
error : Getting package info failed (i got image but can't post now)
@zgomot : I think command are was allowed, cause I can upload and when I uploaded certains version of TWRP it boot up but but with multiples errors when trying to update. Now nothing work exepted eRecovery
bumpshoveit said:
@Cetin20 @mjz2cool Thanks for procedure. I just took a quick look before go to work (yes i don't care, i got a nexus 5X working like a charm ME, hahaha). So I pulled out the SD card and i already found on it a fodler named dload and update.app inside. I don't remember any purpose of installation. The only I have is Huawei eRecovery trying to connect to Wifi and download but as you can imagine; nothing append
error : Getting package info failed (i got image but can't post now)
@zgomot : I think command are was allowed, cause I can upload and when I uploaded certains version of TWRP it boot up but but with multiples errors when trying to update. Now nothing work exepted eRecovery
Click to expand...
Click to collapse
if erecovery boots up you didn't use the 3 buttons or the phone was connected to usb.
press and hold the 3 buttons until it says something about installing firmware, it should flash the update.app. if it doesn't work it will say it wasn't able to install the update. you have to do this while disconnected from usb
zgomot said:
Command not allowed when flashing in fastboot usually means the bootloader is locked.
So unlock your bootloader and try to flash TWRP again.
Click to expand...
Click to collapse
bootloader or that oem in develop settings fixed it whit dc phoenix ..
mjz2cool said:
if erecovery boots up you didn't use the 3 buttons.
press and hold the 3 buttons until it says something about installing firmware, it should flash the update.app. if it doesn't work it will say it wasn't able to install the update. you have to do this while disconnected from usb
Click to expand...
Click to collapse
i think if you do 3 button with USB connected it maybe goes to erecovery?
JimmyEatFood said:
i think if you do 3 button with USB connected it maybe goes to erecovery?
Click to expand...
Click to collapse
yeah, that's what i replied, i forgot to mention that as another option what could have caused that
Hello everyone,
First thing, thanks for your advices ! You were right, I had to press 3 button (vol up, down and power) at the same time while USB is disconnected. I finally found update.app and are actually installing it. What do suggest to me to do after ?
I would like to install TWRP, and android os nearest of google release as possible ! My friend said to me, i found tutorial and tried to follow it but nothing append like expected (don't play me guy ! Were do f**k up ?)
Any advise ?
By the way thank you again for your help ! I'll force my friend to make a donation tro XDA
Haha ! speaking to fast ! Installation seem to be ok, goes to 100% but now screen is black and nothing append ! This phone is damn
You have to unlock the bootloader first, then install Meticulus TWRP and then I suggest you CyanogenMod 13.
You can find the tutorial in the Guide section to unlock bootloader.
Lol, opened the back cover, disconnected battery. Nothing more. Screen stay black, no vibration. Nothing... is it that a bricked phone ?
bumpshoveit said:
Lol, opened the back cover, disconnected battery. Nothing more. Screen stay black, no vibration. Nothing... is it that a bricked phone ?
Click to expand...
Click to collapse
Does your pc detects the phone when you plugin ? if not dc phoenix is your last option...
Shutdown phone > volume - and put cable in see if he goes in fastboot..
My computer dit not detect the phone. Just after installation (via 3 button boot) screen goes black. And now just nothing. I pressed multiples times every possibility of button for a while and screen stay black with no backlight and nothing appear in device manager of windows. No vibration too !
It's like if battery disappear or something ! Obviously fastboot and adb does not detect anything !
So... I'll have to tell to my friend to buy a new phone ! I'll suggest to buy a Nexus... a bit less exotic phone
When I launched update from 3 buttons boot update.app were put there by my friend and i didn't know were it came from... I should have to check it before ! Damn !
bumpshoveit said:
My computer dit not detect the phone. Just after installation (via 3 button boot) screen goes black. And now just nothing. I pressed multiples times every possibility of button for a while and screen stay black with no backlight and nothing appear in device manager of windows. No vibration too !
It's like if battery disappear or something ! Obviously fastboot and adb does not detect anything !
So... I'll have to tell to my friend to buy a new phone ! I'll suggest to buy a Nexus... a bit less exotic phone
When I launched update from 3 buttons boot update.app were put there by my friend and i didn't know were it came from... I should have to check it before ! Damn !
Click to expand...
Click to collapse
have you tried holding the powerbutton for about 10 seconds?
haha, you kidding ? I pressed each for a minute at least !