Database Users

[Q] Boot loop after OTA update.

Hi,
I have been given this mobile to try and fix and despite two days of solid reading I cannot find an answer.
The phone was originally on T-Mobile and had stock rom, the phone HAD been rooted and unlocked.The phone boots up then after a few seconds will say "powering Off" then in boot mode I get the dreaded "Failed to boot 2" then it says "Starting RSD mode" and stays on that.
I have tried to boot into recovery and get the "Failed to boot 2" error.
I need to somehow clear the update from the internal memory but cannot see if that is possible.One the phone boots up I dont get long enough to get into the settings before it powers down.
I have tried every option including "fastboot" on the phone with no luck.
Cheers
Nick

Note that using the steps I did to get your phone booting again will cause you to lose all the data that you saved on your phone. Proceed only if you know what you're doing.
1)Download fastboot here
2)Connect your phone to your PC.
3)Run a command prompt in administrator's mode
4)Remove the battery and plug it back in
5)Phone should start, if not, power it on (if necessary press the vol down button while powering on)
6)Once phone is on, type fastboot -w
Your command prompt window should say
erasing 'userdata'.... OKAY
erasing 'cache' .... OKAY
finished. total time: x.xxs
7)Type fastboot reboot
Phone should boot normally.
With thanks to eval- (for the fastbook package) and thekooliest over here for the steps to clear the userdata. Credit goes to both of them
Happened to me a couple of hours ago after i tried to run a update OTA, my phone is rooted, unlocked too.

look here also: http://forum.xda-developers.com/showthread.php?t=1391940
This guy had the same problem as you and is able to recover.

Stuck at Google Screen won't do anything HELP

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

Nexus 7 won't boot past "Google" screen

So, for a long time, my Nexus 7 never worked, because the charging port was too loose. So I decided to order one. It came in the mail today. Installation was easy. It started charging, but no charging icon appeared. The only thing that happend was the screen back light turning on slightly. So I let it charge more. The Nexus turned on!... But got stuck on the Google screen. So I try and use fastboot and starting it from there. "Boot failed". So, maybe no OS? Try using ADB to flash stock android onto the device. "Failed (Bootloader locked)". Ok, ill just unlock the bootloader. "Unlock failed (unknown error)" . Maybe flashing a new recovery will work? Nope, has to be unlocked. So far, nothing has worked. Spent 2 hours trying to flash, unlock and factory reset, and nothing but "failed" has come up. The device can't even go into recovery mode. When connected to adb, The list of adb devices is blank. It knows the device is connected, but it doesn't show the name or model.
Anyone know what to do?? (I have never tried to flash anything previous from today on this tablet.)

[Q] 2 Years later the Brick returns

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?

LeEco Le 3 Pro - Phone in constant reboot loop

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?