Hi guys, I bought a used 5a and am seeing a snapdragon logo (red/white circle) flash briefly at boot up right before the normal Google G splash screen and was wondering if this was normal for the 5a.
I have already tried flashing the lastest OTA (zip via ADB) and kernel (boot img) via fastboot after unlocking the bootloader just in case. I am worried about any potential malware and want the phone as factory stock as possible.
Related
Hi, sorry for creating a new thread but I posted in two different related threads i didn't get any answers.
I was given thus moto g 2nd gen xt1064 us version, with unlocked bootloader, status code:3, the phone powers on and go through the boot animation then turns blank with a faint backlight and stays there until battery drain.
What i did so far.
I booted into recovery and made cache and data wipe. Didn't work.
I flashed a stock firmware (5.02 btw) through fastboot with bootloader lock, everything went well according to log, but same result won't go past bootanimation.
I noticed the bootloader is still unlocked even though the relock command was successful, also phone is not detected by my pc except in fastboot mode.
Any suggestions?
Hey guys,
I have a Moto G 2014 here that is stuck in a boot loop. It's on stock recovery, not rooted and the bootloader is locked. It was running 5.x and had an update available (I'm pretty sure it was the stagefright update). After installing it it restarted and got stuck on the Motorola boot logo. Twice it's gotten past the boot logo (I think after letting the battery run out and wiping cache it does this) and shows a popup "Android is upgrading - Starting apps" with a spinning circle but it doesn't go past that. I can get into fastboot and stock recovery.
My question is, with a locked bootloader, is there any way to get it to boot again without losing user data?
gamma_6 said:
Hey guys,
I have a Moto G 2014 here that is stuck in a boot loop. It's on stock recovery, not rooted and the bootloader is locked. It was running 5.x and had an update available (I'm pretty sure it was the stagefright update). After installing it it restarted and got stuck on the Motorola boot logo. Twice it's gotten past the boot logo (I think after letting the battery run out and wiping cache it does this) and shows a popup "Android is upgrading - Starting apps" with a spinning circle but it doesn't go past that. I can get into fastboot and stock recovery.
My question is, with a locked bootloader, is there any way to get it to boot again without losing user data?
Click to expand...
Click to collapse
At these stage you need to flash Stock firmware again via Fastboot , i guess there is no other way to boot up !
Hitesh2626 said:
At these stage you need to flash Stock firmware again via Fastboot , i guess there is no other way to boot up !
Click to expand...
Click to collapse
Is there a way to do it without losing user data?
gamma_6 said:
Is there a way to do it without losing user data?
Click to expand...
Click to collapse
I guess no other way left or else try once wiping cache from stock recovery and check whether it boots if not then you have to flash the whole firmware with loosing your data.
So I successfully rooted my lg k8 2018 (lg aristo 2). I decided to install gravitybox and turned on some things. I rebooted my phone and now it's stuck on the boot logo. I can't boot into recovery because I get the bootloader is unlocked message. (Not possible to re-lock it w/o putting my phone into a boot loop). I can get into fastboot by holding down and plugging in my phone. What should I do?
Update: I need to be able to get into recovery to flash xposed uninstaller. However, because I get the bootloader is unlocked message, I cant. I tried at least a thousand times. I also tried the button combination to disable xposed on startup. That didn't work. It was running android 7.X (I think 7.1 or 7.2)
TLDR: Dropped phone. Broke screen. Battery ran out (while waiting for replacement screen). Replaced screen. Phone bootloops at Mi logo. Able to boot to fastboot. Able to unlock bootloader and flash stock rom, but bootloops continue.
...
I recently dropped and shattered the screen of my Mi 8 Global (128Gb, purchased from GearBest), and was not able to see anything at all.
While waiting for a replacement screen I ordered online, I tried to turn off the phone, but it didn't seem very successful - sometimes, when handing the phone, I could feel it vibrate a little when I touched the fingerprint sensor with another finger. After some time, I guess the battery ran out.
New screen arrived, and I was able to replace it - however, while testing the screen (motherboard, battery, new screen only), the phone would bootloop at the mi logo. Not much else I could do, except reassemble it with the new screen and try figure out what's wrong.
Plugging in a charger, the same thing happens: mi logo bootloop; charging led does not light (I seem to recall that it did not light too when I plugged in a charger with the broken screen, before I disassembled the phone)
Holding down up+power button; or up+down+power has no effect, and same thing happens: mi logo bootloop
Holding down+power button brings me to fastboot mode.
In fastboot, I am able to unlock the bootloader with miflash-unlock; I had requested for permission and linked my phone with my account when I first got it. Mi logo bootloops continue (With 'unlocked' displayed)
In fastboot, I am able to flash dipper_global_images_V10.1.2.0.PEAMIFI_20181211.00 00.00_9.0_global_0099f5af5f.tgz with xiaomiflash successfully. With 'clean all' Mi logo bootloops continue; even after flashing twice. Same with 'clean all and lock'. Mi logo bootloop (but 'unlocked' is no longer displayed). I am able to unlock the phone again with miflash-unlock.
Any suggestions on what I can try to do from here? Pretty much at a loss now.
Bump for help.
Any suggestions on what I can try to do to recover the phone?
If anyone is wondering, my phone booted correctly after flashing with the current ROM (dipper_global_images_V10.2.1.0.PEAMIXM_20190110.0000.00_9.0_global_4d02fd6c97.tgz), downloaded from here, via fastboot. Earlier version would result in a bootloop.
Just a quick update.
The latest Miui Global Rom (V10.3.3.0.PEAMIXM) can't boot on my phone, and I have to stick with the previous (V10.3.2.0 PEAMIXM) for now. It doesn't loop, just gets stuck at the initial Mi screen; this also happens if the bootloader is locked and updated via OTA.
Official TWRP versions also can't boot, but TWRP by LR Team (from here) works.
Lineage OS 16 bootloops.
I'm not exactly sure why replacing the broken display causes this, or what I can do to try figure out what the problem is; but I thought someone else might find this information useful.
Hello all,
I have been using my Pixel 4 XL for years, and all of a sudden it shut down, and now it keeps being stuck in a booting loop.
I get to Google's logo and the loading animation ... and then it turns black, and starts all over, in a loop.
I am able to access the bootloader and recovery mode.
I tried a complete wipe through recovery mode, didn't change anything.
I wanted to flash original images, but the bootloader is locked and I haven't found any way to unlock it without going through the phone settings (which doesn't boot anymore).
All fastboot flashing related commands fail stating my device is locked.
Would you have any suggestion ?
Anything I should try before considering my device is completely dead ?
Thanks in advance
utundu said:
Hello all,
I have been using my Pixel 4 XL for years, and all of a sudden it shut down, and now it keeps being stuck in a booting loop.
I get to Google's logo and the loading animation ... and then it turns black, and starts all over, in a loop.
I am able to access the bootloader and recovery mode.
I tried a complete wipe through recovery mode, didn't change anything.
I wanted to flash original images, but the bootloader is locked and I haven't found any way to unlock it without going through the phone settings (which doesn't boot anymore).
All fastboot flashing related commands fail stating my device is locked.
Would you have any suggestion ?
Anything I should try before considering my device is completely dead ?
Thanks in advance
Click to expand...
Click to collapse
Try sideloading an OTA image. You can do that with a locked bootloader.
Thanks Lughnasadh
I've tried multiple times, and the process fails randomly, at different percentages ...
The phone suddenly reboots and the laptop displays " adb: failed to read command: No error"
The weird thing is it doesn't reboot and can stay up for super long while on the bootloader.
With a locked bootloader the rescue OTA (full OTA image flashed via adb) is all you have. I would try a different data cable (A-to-C) first and then move to a different computer. Make sure the new PC is running the latest adb/fastboot binaries. This is why I unlock the bootloader on every Pixel in my family. Even though they will never root the phone, if the fit hits the shan you have many more options. BTW, I just traded in my son's P4XL and got $285 trade-in on a 6a. Net cost was less than $150. The deal just ended but will likely come back again. Same deal was offered earlier but included a pair of first-gen earbuds. Wish you luck on getting your old phone working. The P4XL is still my primary phone and is still working well.