Database Info

[Q] Moto G error 'Boot up failed'

Hi so I have a Moto G 4G (XT1039) and I recently tried flashing an Android Lollipop rom onto the phone. The process in TWRP went fine but afterwards my phone started turning on and it showed the boot up screen for a quarter of a second and after I was redirected to the fastboot menu with the error message 'Fastboot Reason: Fall-through from normal boot mode' I tried going on 'Normal Powerup' after that but that resulted in 'Boot up failed' and it does this for every option except 'Recovery' this took me to the stock recovery screen. (not TWRP because when I tried flashing TWRP recovery earlier this came up with 'Boot up failed' for when I went on Recovery so instead I put TWRP in the normal boot mode). Anyway, after this I went to wipe all the data from Recovery and it did this process just fine however when I rebooted the device it still came up with 'Fastboot Reason: Fall-through from normal boot mode' and 'Boot up failed' when I went on 'Normal powerup'. My computer does not let me access the phone either. (it is detected because it made a noise when I plugged it in but its not accessible and doesn't appear in my drivers screen). I think the phone still may be trying to boot from the corrupted/faulty boot image as I put it in the phones internal memory but I cannot delete it from there because as I said I can't access the phones internal memory. If there is a fix for this (I assume there isn't as I am so limited to doing anything on the phone or on the computer now) I would appreciate it a lot. I would also like to ask: when the phone boots does it boot up from the internal memory and files from the hard-drive in the phone or from somewhere else? If so I will probably just take it to a shop and pay for the hard-drive to be replaced. Thanks. And also if there are any developers that skim this post and a similar one that sounds the same don't as there is no one else with this problem and I have a different problem thane the others. And yes I have posted two other posts one is similar but still different and the other has been closed by mistake because of somebody skimming that one and my other one thinking they were the same

Your thread will be moved to the appropriate forum.

[Q] Stuck at Google logo when powering on, can't enter recovery mode

Hey guys,
Few days ago, I woke up and saw my Nexus 5 was out of battery, charged it and when I turned it on it started to update and it was going through with optimising apps ## of ### and when I checked it again, it was stuck on the four circles animation. It got stuck on this screen for quite a while so I powered off, powered on again and now it just stays stuck on the Google logo, what should I do?
I've tried entering Fastboot Mode and selecting Recovery Mode but then nothing happens; screen stays on but stays black. I tried connecting it to my computer so I could backup my files but I can't get it to appear as a Nexus 5 drive and access the folders. Also LOCK STATE - locked [preetty sure I unlocked it back when I first got the phone in 2013 but then I haven't really done anything custom with it]
So I've tried following the steps here: androidforums.com/threads/nexus-5-stuck-in-the-start-up-screen.887612/page-3#post-6817816, but I can't get my device to appear as an adb device, even though i ran the 'fastboot oem unlock' command and it unlocked the Nexus? i.imgur.com/VHHjaVe.png (Android device is showing but 'adb list devices' command doesn't detect anything?)
Ideally I would like to access the Nexus 5 internal storage and just copy paste the folder to my computer to serve as a backup and save files, then flash a new image/factory reset it. I went over to my cousin's place last night to see if he could help as he is more technical than I am but he couldn't flash a new image onto it. I've also unlocked the phone a few times with the 'fastboot oem unlock' command, which changes to LOCK STATE - unlocked, but then if I power off the phone and enter Fastboot Mode again it will show as LOCK STATE - locked.
Also, I'm not sure at this point if the unlocking has wiped whatever data might have been on the phone anyway? [does the internal sdcard get wiped if you run oem unlock? e.g. I had about 6/32GB left on my phone but now it'll just be 31/32 GB because it wiped?]
Thanks, I hope my description of the problem is clear. I have tried googling extensively to see if anyone has experienced similar problems but they're not quite the same (eg. stuck on Google screen bootloop is a power button issue but my phone doesn't constantly reboot and the power button seems fine) [clearing cache or running Recovery mode, but my phone can't run Recovery mode] {Flashing new image but that didn't seem to work either}
Sorry my links don't work, I'm a new user so don't have enough posts here!

OnePlus One CM12S is stuck on booting, shows only CYANOGEN logo

Hi,
I bought my OnePlus One (64 GB Sandstone Black) in September 2014. Since I got the phone, everything was running very quickly & smoothly. I did not have any problems with it, so I was very pleased with my brand new phone.
I did not tamper at all with my OnePlus One phone and every time there was a new OTA update, I updated it with the latest version. Currently my OPO has the latest Cyanogen OS 12 OTA updates (CM12S).
Last Friday I used my phone and everything was running very good, as usual. I shut down my phone and went to bed. The next day, on Saturday morning when I turned on the phone, it started showing the OnePlus One logo (with the text "powered by android"). Then CYANOGEN logo appeared on the screen and nothing happened. I waited near my phone for half an hour and nothing happened, it kept showing the CYANOGEN logo. It's like a cycle that never ends. So now I am facing a huge problem with my OPO: every time I press the power button, my OnePlus One gets stuck while booting, showing only the CYANOGEN logo. :crying:
Please see picture "OPO stuck on booting - shows only CYANOGEN logo.JPG".
As I said before, I did not tampered with my OPO, I did not flash it, I did not installed any ROM, I did not installed a custom recovery. Also, I did not drop my phone, so it is in good hardware condition. Every time there were new updates, I updated it with the latest OTA updates. I did not have any issues after the updates, so I don't understand why now it gets stuck on booting (especially since before this problem appeared, everything was working great, as usual).
I read through the forums, the internet and tried to find several solutions, without wiping my data. Any solution that I found did not work and I could not fix this problem (OPO stuck on booting, while showing the CYANOGEN logo). After two days in which I could not use my phone, I removed my SIM from the OPO and now I am using a normal phone (only for calls and SMS).
After my OPO gets stuck while booting, showing only the CYANOGEN logo, I connect it to my laptop using the USB cable (the same one used for charging), but I cannot access my files. Before this huge problem appeared, I could easily connect my OPO to my laptop. Please see pictures: "Connecting my OPO via USB - Installing device driver software - Step 1.JPG" and "Connecting my OPO via USB - Installing device driver software - Step 2 - Failed.JPG". I updated the drivers, but it did not work.
Ever since I got my phone, I have never unlocked the bootloader or rooted or anything of that sort.
I have never even touched any fastboot/adb commands since I got the OPO, until now, when I have this major problem with it.
After reading the forums, I started my OPO in Fastboot Mode and used 2 commands with fastboot.exe (Please see picture named "OPO Fastboot Mode.JPG")
Results below:
******************************
F:\OnePlus One tools>fastboot.exe devices
b01c5f88 fastboot
F:\OnePlus One tools>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.006s]
finished. total time: 0.006s
******************************
I do not understand why "Device tampered: true", since I have never unlocked the bootloader or rooted or flashed or anything of that sort ever since I got my OPO. I did not tamper my OPO, so "Device tampered" should have been false.
I also tried to use ADB, but it does not work. Please see below:
******************************
F:\OnePlus One tools>adb devices
List of devices attached <--- THIS LIST IS EMPTY, IT DOES NOT SHOW MY DEVICE, SO ADB DOES NOT WORK AT ALL
******************************
I want to save my media files (pictures, recordings, clips, audio files), my documents and messages.
For other suggestions found on the forums, I did not use at all, because I do not want to erase all data of the phone.
My OPO can boot into recovery mode (Please see picture named "OPO Cyanogen Recovery.JPG"), so I can see the Cyanogen Recovery menu, but I do not want to wipe all my data and do a factory reset. I want to first save my data and afterwards I can erase all data and reset my OPO.
Problem: my OPO gets stuck while booting, showing only the CYANOGEN logo. I wait and wait and nothing happens (today I waited for two hours, the logo is still there and the phone does not start).
I want to:
1) Save to my computer my files (media files, documents) and messages (SMS and chat messages, like viber and so on)
2) Solve this boot logo issue (OPO stuck on booting, while showing only the CYANOGEN logo)
Any help regarding this problem is enormously appreciated.
Thanks in advance,
Bogdan

[Completed] Nexus 7(2012) 3G bootloop without an option to fastboot

Hi, people. I hope you can help me.
My problem is that my rooted Nexus 7 (2012) with 3G and kitkat Stock Android suddenly turned into so called brick state. Only Google logo was appearing during the boot, and that will last forever. Then, just for interest, I tried to enter into the recovery mode (Clockwork Recovery v6.0.4.3 for tilapia), but the device did not go into it. The logo of CWM appeared in the middle of the screen and then the device reboots automatically showing the Google logo screen for several seconds and then going into recovery mode with the CWM logo appearing on the centre of the screen, and then reboot again. This recovery bootloop lasts forever or till the battery runs out. I tried to use
Code:
adb devices
and
Code:
fastboot devices
on my nexus 4, everythings works fine (meaning drivers are installed correclty). But
Code:
fastboot devices
for the nexus 7 outputs into
Code:
- waiting for device -
I tried to force the battery to run out and then tried to go into fastboot, but that did not help, the recovery bootloop appeared on its own again. Please, help me, I don't know what to do.
EDIT. I tried to pull out the battery for a half day (disconnect battery connectors) in hope that this will somehow reset the boot options, but this did not help.
Any thoughts?
Also, if the thread is not in the appropriate branch of the forum, please, let me know, probably at correct location I will find more help. Thanks.
EDIT2. I solved the problem by trying to enter the bootloader mode via adb. But to enter bootloader required a liitle bit of humoristic approach. I was pressing UP then ENTER to enter fastboot mode via termianl (#adb reboot-bootloader) for 5 to 10 minutes. When I managed to enter the fastboot, I flashed TWRP recovery for tilapia and the latest 5.1 Lopllipop But it seems there is a bug in the stock recovery because it does not work with NEXUS 7, the last two updates of Kitkat and Lollipop required to flash custom recovery, because the stock one did the bootloop on either Google logo or the animation of "beautiful" circles.
Thanks for reading, hope this might help someone.
from danik

Hi,
Glad to hear it solved
Good Luck!
Thread Closed.

Stuck on "Your device is corrupt. It can't be trusted and will not boot" start screen

Stuck on "Your device is corrupt. It can't be trusted and will not boot" start screen
Hi,
(I already posted this as a comment on the thread - GUIDE: How to unbrick your Zenfone 6 (ZS630KL) - but am looking for anyone who can help with this issue)
I did a series of steps over the past 48 hours that have ended with my phone now displaying the message, "Your device is corrupt. It can't be trusted and will not boot." It stays like that for about twenty seconds, and then reboots. At the time it is rebooting, I'm able to press the volume up + power keys together and get it into the Fastboot Mode - and then it shows up in the Fastboot menu of an attached computer, but that's it - from there, I'm unable to reboot into Recovery / System, as both attempts end with the above stated message. I AM able to power off the device from the Fastboot Mode, but the device powers on automatically (and displays that message onscreen).
I downloaded the Qualcomm drivers as suggested in this article, and was able to convert the phone from an "unknown android" to a "Asus android" device in Windows Device Manager - but no further progress; after running the .bat and the script, this message still appears onscreen, when attempting to login to the Recovery from the Fastboot Mode.
Any guidance would be appreciated. I am briefly outlining the glorious-many (mis-)steps that led to this current situation:
- Installed LineageOS 17.1
- Realised that Google Pay (Indian version) and a banking app don't work
- Tried multiple options to resolve that issue, such as installing (and uninstalling) TWRP, Magisk, Xposed framework, etc.
- finally gave up and was looking to get back everything to stock - ROM, Recovery and boot loader. Stumbled on the "fastboot oem asus-back" command, which now in retrospect, I shouldn't have used with custom recovery + ROM on the device, but yeah, that's what led to this issue.

cutesocks7583 said:
Hi,
(I already posted this as a comment on the thread - GUIDE: How to unbrick your Zenfone 6 (ZS630KL) - but am looking for anyone who can help with this issue)
I did a series of steps over the past 48 hours that have ended with my phone now displaying the message, "Your device is corrupt. It can't be trusted and will not boot." It stays like that for about twenty seconds, and then reboots. At the time it is rebooting, I'm able to press the volume up + power keys together and get it into the Fastboot Mode - and then it shows up in the Fastboot menu of an attached computer, but that's it - from there, I'm unable to reboot into Recovery / System, as both attempts end with the above stated message. I AM able to power off the device from the Fastboot Mode, but the device powers on automatically (and displays that message onscreen).
I downloaded the Qualcomm drivers as suggested in this article, and was able to convert the phone from an "unknown android" to a "Asus android" device in Windows Device Manager - but no further progress; after running the .bat and the script, this message still appears onscreen, when attempting to login to the Recovery from the Fastboot Mode.
Any guidance would be appreciated. I am briefly outlining the glorious-many (mis-)steps that led to this current situation:
- Installed LineageOS 17.1
- Realised that Google Pay (Indian version) and a banking app don't work
- Tried multiple options to resolve that issue, such as installing (and uninstalling) TWRP, Magisk, Xposed framework, etc.
- finally gave up and was looking to get back everything to stock - ROM, Recovery and boot loader. Stumbled on the "fastboot oem asus-back" command, which now in retrospect, I shouldn't have used with custom recovery + ROM on the device, but yeah, that's what led to this issue.
Click to expand...
Click to collapse
This issue is kinda resolved now - it took more than 24 hours of looking through various solutions on the internet.
In the interests of anyone who happens on my comment/post and would like to know how I resolved it, I can't give you exact steps - sorry, but there was just way too much fiddling. But these two posts were invaluable in helping me understand the issue:
a) XDA post: [Guide]Remove "your device is corrupted and can not be trusted" issue
b) XDA post (and the first few replies): Phone keeps booting into csc fastboot mode
and this post was invaluable in actually finally resolving the issue (it resolved only after I ran through the steps a second time, after trying the steps from the above two links a few times, and trying other steps from other forums on the internet)
c) [GUIDE] QDLoader 9008 fix | EDL Mode fix
I didn't complete ALL steps in that last post, since my ROM had already been flashed in my previous steps; I just had to get past that locked/unlocked Bootloader, and things are fine now.
I'm trying to update to firmware version UL-ASUS_I01WD-ASUS-17.1810.2008.171-1.1.1-user now, after which I'm going to attempt flashing the stock ROM from the ASUS website. Hopefully, it all works out fine - but right now, I'm just glad that the phone isn't bricked, and that I don't need to visit an Asus service centre.