Related
Hi guys,
In front of me, I have my friend's very stubborn LG Nexus 4. It's about 7 months old and a month ago, he dropped it and cracked the screen's glass (and the case's glass back as well). The phone still worked fine for a few weeks after that after that, but the touchscreen was not always responding correctly. He decided to give it to a service center for repair, but they returned it in a few days claiming there's a bootloop and they won't repair it (even if he paid) since the phone wasn't purchased in the same country. (Such BS, isn't it?)
An easy thing to fix, I thought, after fixing all sorts of bootloops on my SGT, SGS1 and my other friend's SGS2. Turns out, it's anything but.
Regardless of whether I flash stock following this guide or CM11 following the CM wiki, the phone is stuck on boot animation. 4 swirling colored balls for stock or an arrow rotating aroud Cid in case of CM11.
I have tried both stock recovery and CWM. I have tried wiping cache, data, Dalvik cache, any combination of only one or two or all three, tried waiting for an hour on first boot (someone suggested the first boot can take up to 15 minutes... find that hard to believe since even my sluggish SGS1 will manage in 3 minutes tops after a flash, but still tried) - all in vain. All I get is the screen's backlight level suddenly jumping up about 5 minutes into the boot process, as if the "Welcome to Android!" menu is about to appear - but it's still bootlooping until the battery runs out. (It gets quite warm too.)
TL;DR Nexus 4 flashes successfully with both stock 4.4.2 and CM11 but bootloops no matter what.
What can I do at this point to troubleshoot it? I'm out of ideas.
Its possible that this is a hardware issue but for now what I would try is download latest stock, Google search
android factory images
And choose the latest for your device, KOT49H
Now boot to fastboot
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now
fastboot flash bootloader nameofbootloader.img
fastboot flash radio nameofradio.img
Now either double click the flashall.bat or I prefer just extracting the rest an manual flash
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
Now
fastboot reboot
If this doesn't work than a good chance of hardware issue from all the falls, if it does work then my guess is you want to root it so go back to fastboot and flash the latest twrp or cwm recovery
Then either boot to recovery and flash su or wipe all and flash a custom ROM
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Its possible that this is a hardware issue but for now what I would try is download latest stock, Google search
android factory images
And choose the latest for your device, KOT49H
Now boot to fastboot
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now
fastboot flash bootloader nameofbootloader.img
fastboot flash radio nameofradio.img
Now either double click the flashall.bat or I prefer just extracting the rest an manual flash
fastboot flash system system.img
fastboot flash data userdata.img
fastboot flash cache cache.img
fastboot flash boot boot.img
Now
fastboot reboot
If this doesn't work than a good chance of hardware issue from all the falls, if it does work then my guess is you want to root it so go back to fastboot and flash the latest twrp or cwm recovery
Then either boot to recovery and flash su or wipe all and flash a custom ROM
Best of luck!
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
As I said, I've already tried CWM, custom ROM (CM 11 - which required rooting, which I did) and followed the guide I linked for flashing the latest stock ROM I got from Google. The only thing I haven't tried is the fastboot erase commands - thanks for suggesting that, I will try them ASAP before trying to flash stock again though I don't have much hope left
Give it a shot, if you do everything in this order you will be good if its a software issue, if it doesn't work than possibly hardware
Sent from my Nexus 4 using XDA Premium 4 mobile app
My story is strange.
I was trying to install AudioFX of CM12.1, because stock equalizer of Moto haven't got Bluetooth options. It's very pitty with the devices, which support APT-X. The quality in my Creative is perfect.
So, i unlock Bootloader, at first, than flash TWRP recovery and flash ZIP file with audioFX from CM for any stock roms.
The sound in bluetooth improved, but the speakers won't work.
I re-flash phone after some trying to troubleshoot and got another problem. If the phone is off- i just turn it power on and it loading in fastboot by default. I try to re-flash another time with Lock bootloader with instructions from here : http://forum.xda-developers.com/moto-x-style/help/how-relock-bootloader-t3207771
But the phone still loading in fastboot by default.
BTW i tried to flash logo to remove the Warning or UNLOCKER BOOTLOADER, but it doesn't work for me.
My phone is X Pure Edition , XT1575.
I found the solution of fastboot problem, i tried to read bootloader logs and found - UTAG "bootmode" configured as fastboot
So i just try this command and it's help!
fastboot oem fb_mode_clear
Now i only have a problem with Warning Logo.
By doesn't work does it fail to flash or just doesn't apply?
joshbean39 said:
By doesn't work does it fail to flash or just doesn't apply?
Click to expand...
Click to collapse
Flash status is OKAY. No errors of fails.
My problem on XT1572 fixed already
many thanks
Hello Team
i am stuck on Boot Loop after flashing V12A Rom using LGUP(with Patched DLL)
Last working rom was VS995-17A (non-rooted)
I successfully flashed V13A and V17A rom but no profit
tried UPDATE & PARTION DL modes
I tried US996 10F rom with LGUP - rom boots up but force closes in 10 seconds with errors com.android FC
My bootloader is locked - (checkd with fastboot getvar command)
I still have a working download mode
uccfar said:
Hello Team
i am stuck on Boot Loop after flashing V12A Rom using LGUP(with Patched DLL)
Last working rom was VS995-17A (non-rooted)
I successfully flashed V13A and V17A rom but no profit
tried UPDATE & PARTION DL modes
I tried US996 10F rom with LGUP - rom boots up but force closes in 10 seconds with errors com.android FC
My bootloader is locked - (checkd with fastboot getvar command)
I still have a working download mode
Click to expand...
Click to collapse
so your bootloader was looked when you tried to "update" rom?
if so thats your issue. you can try to connect to pc and put phone in fastboot mode and unlock bootloader.
cbissa18 said:
so your bootloader was looked when you tried to "update" rom?
if so thats your issue. you can try to connect to pc and put phone in fastboot mode and unlock bootloader.
Click to expand...
Click to collapse
No they cant. Fastboot oem unlock only works with the T-mobile variant (unlock works without a key but is missing flash commands) and the us unlocked us996 can unlock by flashing a key from lg but can actually flash roms.
@uccfar is using the term rom when meaning stock firmware, and if this didnt happen when rooted or trying to root it could easily be a hardware issue.
Phoenix591 said:
No they cant. Fastboot oem unlock only works with the T-mobile variant (unlock works without a key but is missing flash commands) and the us unlocked us996 can unlock by flashing a key from lg but can actually flash roms.
@uccfar is using the term rom when meaning stock firmware, and if this didnt happen when rooted or trying to root it could easily be a hardware issue.
Click to expand...
Click to collapse
I fixed my problems and my V20 VS995 is up and running .
Thanks goes to all the members who have posted their problems and a subsequent solution for each and every issue
uccfar said:
I fixed my problems and my V20 VS995 is up and running .
Thanks goes to all the members who have posted their problems and a subsequent solution for each and every issue
Click to expand...
Click to collapse
Just wondering, how did you fix your issue?
Thank you.
Since I bought the Moto G5 I always used platform tools (ADB + Fastboot) version r27.
Two weeks ago I updated to the latest version (r28) and had no problems using ADB, but when I first used Fastboot I was unfortunate to get the following error before every flash operation:
Code:
(bootloader)is-logical:not found
And the flash process apparently went on normally, but it did not, it just bricked my phone.
I googled for the error and found out several Motorola users were having the same issue with other devices too (Moto X2, Moto G5 Plus and I found one other Cedric user with the same problem).
After trying several firmwares with no success I realized the problem was with Fastboot, so I tried both Fastboot r26 and r27 and both flashed my phone normally, but again on r28 I had the issue above, so I warn you all to stay away from Fastboot r28.
Of course it only soft bricked my phone, but if I were relocking my bootloader or flashing a newer firmware using Fastboot r28, I'd hard brick my phone for sure, since that's what to be expected from a failed attempt to flash gpt.bin or bootloader.img
I've been using fastboot v28 with no issues. I used it flash my G5 from Nougat to Oreo a month or so ago, used it to unlock my bootloader, flash TWRP, and flash a custom bootlogo. I do get those "(bootloader)is-logical:not found" messages, but I think it has to do with fastboot looking for the partition structure used on native-Oreo devices for Treble, but I'm not sure. Hasn't been an issue for me though. (FWIW, I'm on Linux)
xtermmin said:
I've been using fastboot v28 with no issues. I used it flash my G5 from Nougat to Oreo a month or so ago, used it to unlock my bootloader, flash TWRP, and flash a custom bootlogo. I do get those "(bootloader)is-logical:not found" messages, but I think it has to do with fastboot looking for the partition structure used on native-Oreo devices for Treble, but I'm not sure. Hasn't been an issue for me though. (FWIW, I'm on Linux)
Click to expand...
Click to collapse
interesting. I haven't tried this on linux though.
xtermmin said:
I've been using fastboot v28 with no issues. I used it flash my G5 from Nougat to Oreo a month or so ago, used it to unlock my bootloader, flash TWRP, and flash a custom bootlogo. I do get those "(bootloader)is-logical:not found" messages, but I think it has to do with fastboot looking for the partition structure used on native-Oreo devices for Treble, but I'm not sure. Hasn't been an issue for me though. (FWIW, I'm on Linux)
Click to expand...
Click to collapse
Same for me here using Linux. Still able to flash without issues at all.
Hi,
I am having a problem trying to relock my bootloader.
i am selling my g4, so needed to remove my custom rom, flash stock and relock my bootloader.
I downloaded and flashed via twrp the stock 8.1 ROM on the g4 plus page. ( stock rom in twrp format)
That went fine.
Then I booted into fastboot , and entered fastboot lock command fastboot oem lock
It said the android image was not valid?
So I then entered fastboot flashing lock
it rebooted fine to the stock android , but now the bootloader warning says ''your device has loaded a different operating system'', and thens boots 8.1.
DO you think I should go back anf flash stock rom ( not a twrp flashable version), using fastboot commands, ending with 'fastboot oem lock' ?
Just dont want to brick it, as it is now sold!
Many Thanks for any help
pootler
P.S. the TWRP I am using is a custom one ( i think )
pootler said:
Hi,
I am having a problem trying to relock my bootloader.
i am selling my g4, so needed to remove my custom rom, flash stock and relock my bootloader.
I downloaded and flashed via twrp the stock 8.1 ROM on the g4 plus page. ( stock rom in twrp format)
That went fine.
Then I booted into fastboot , and entered fastboot lock command fastboot oem lock
It said the android image was not valid?
So I then entered fastboot flashing lock
it rebooted fine to the stock android , but now the bootloader warning says ''your device has loaded a different operating system'', and thens boots 8.1.
DO you think I should go back anf flash stock rom ( not a twrp flashable version), using fastboot commands, ending with 'fastboot oem lock' ?
Just dont want to brick it, as it is now sold!
Many Thanks for any help
pootler
P.S. the TWRP I am using is a custom one ( i think )
Click to expand...
Click to collapse
Use LMSA flash rescue option if you have a Windows machine
(Lenovo) MOTO Smart Assistant (PC)
then see
Relocking the bootloader
sd_shadow said:
Use LMSA flash rescue option if you have a Windows machine
(Lenovo) MOTO Smart Assistant (PC)
then see
Relocking the bootloader
Click to expand...
Click to collapse
THanks for the reply.
Strange, thought I had already updated this
I went back to stock firmware and decided to flash with fastboot all individual files.
At some point, I got the same ''verification failed' but the command line suggested flashing system, boot, and ( something else, cant remember) again.
i did this this, and this time, no errors occured, and I had a complete install, with a locked bootloader, and no bootloader warning screen.!
Yay - result
Thanks again for your advice - I will remember it for the future.