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
Related
Hello guys, I wanted to share something I've discovered so that others will not repeat my same mistake. And yes I'm a noob
A little backstory
I have an Asian XT1033 Moto G, bootloader unlocked, rooted and using Faux's kernel. So, after reading some feedback about 5.1.1 for XT1033, I've been tempted to flash 5.1.1 over my 4.4.4.
The problem
I've downloaded the stock 5.0.2 Asia XT1033 firmware in img format, and proceeded to flash them via fastboot using Minimal ADB and Fastboot. (I tried to fastboot flash 5.0.2 stock firmware directly from 4.4.4 stock). Everything was fine, after flashing each part, Okay messages were shown. After rebooting, my Moto G booted and showed the usual "Warning Bootloader Unlocked" screen. EXCEPT, the "Warning Bootloader Unlocked" screen stayed for more than 10minutes......., I've spent the whole midnight trying to reflash back using 4.4.4 stock Asia firmwares (same stucked at warning screen), baffled, googling for similar problems encountered in hopes of a solution, but found nothing. The next day something came to my mind and I googled "the difference between fastboot and mfastboot" which led me to Mark_Venture's website, and after some reading, I first facepalmed myself hard and then screamed Eureka with my mind
What's causing this
To rephrase Mark_Venture, "fastboot is compatible with almost all Android devices, but is limited on how big the size of files it can actually flash, while Motorola have their own version called mfastboot which surpassed the file size limits of the usual fastboot", so basically when I tried to flash via fastboot, the command I've typed was "fastboot.exe flash partition gpt.bin" which is wrong and should be "mfastboot.exe flash partition gpt.bin", so basically I've used the usual fastboot.exe instead of Motorola's own mfastboot.exe. This probably explains why all the other files from the stock firmware are successfully flashed, EXCEPT the system.img_sparsechunk.0123 files due to their average sizes easily exceeding 256MB (my own take here, correct me if I'm wrong). This probably explains why rebooting after flashing via fastboot doesn't work because the system imgs are not flashed, and hence the phone get stucked at "Warning Bootloader Unlocked" screen because there is no ROM to boot to.
Alternatively, actually much more easier
You can also flash using fastboot a custom recovery, then boot into the custom recovery and either adb push or using USB OTG to install ROM zips. Personally I've used USB OTG with PhilZ Touch Recovery to install custom ROM and my phone finally boots.
TL;DR
Use mfastboot.exe instead of fastboot.exe when flashing via fastboot
Big credits to Mark_Venture and his website
Source: http://mark.cdmaforums.com/MotoX-mFastboot.htm
Great find. TIL for me too
Hi everybody
My Zenfone Selfie after a normal update (never modified) is in bootloop.
So I installed adb and fastboot and I flashed the twrp.
Then I tried in every way to flash a rom. I've tried both with official firmware and with various versions of cyanogenmod. Through fastboot and via adb sideload.
Even if seems to work, when I reboot I get the bootloop problem again.
As far as I can understand the problem it’s that I have the bootloader still locked. The official apk solution I guees it’s not applicable in my case. By fastboot oem unlock i get an error message (probably why i can not enable usb debug).
Do you know of other ways to unlock the bootloader or in general to flick my phone?
Thanks to everyone for the help
Here is a link for selfie's boot, recovery and system images for fastboot flashing
https://mega.nz/#F!Ao1RjT7D!hQ5x60r02WveB9-Hl32B4g!810z0DoQ
You can't unlocked bootloader on fastboot. I hope you can restore your device.
24imelqui said:
Here is a link for selfie's boot, recovery and system images for fastboot flashing
https://mega.nz/#F!Ao1RjT7D!hQ5x60r02WveB9-Hl32B4g!810z0DoQ
You can't unlocked bootloader on fastboot. I hope you can restore your device.
Click to expand...
Click to collapse
i tried evrything from flashing stock image , recovery partition , boot image . but nothing works. same i dont have unlocked bootloader. i am stuck at just rebooting phone. please help
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.
Hi I flashed the ATHENE_RETAIL_8.1.0_OPJ28.111-22_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml in my Moto G4 Amazon variant phone.
Now the phone is stocked at logo.
Has anyone root this model with bootloader locked ?
meolivares06 said:
Hi I flashed the ATHENE_RETAIL_8.1.0_OPJ28.111-22_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml in my Moto G4 Amazon variant phone.
Now the phone is stocked at logo.
Has anyone root this model with bootloader locked ?
Click to expand...
Click to collapse
You cannot root with a locked bootloader.
i have the same issue, wondering if any solution out yet ?
henser said:
i have the same issue, wondering if any solution out yet ?
Click to expand...
Click to collapse
Could try LMSA Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ali using XDA Labs
sd_shadow said:
Could try LMSA Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
i've just tried, tried rescue but i got an error when trying to install flashboot flash error. Says Flash failed, try again. stuck at 68 Percent
Currently looking in to flashing this.
Did you all try to flash the rom as a single file in twrp or similar or did you try to flash individual files to individual partitions?
With fastboot like:
DO NOT USE FOR THIS PHONE, SHOWN AS EXAMPLE!
sudo fastboot flash bluetooth BTFM.bin
sudo fastboot flash dsp dspso.bin
sudo fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash system system.img_sparsechunk.0
I used this kind of code for flashing new software to my G7
(Sudo is for using these commands in linux)
Restore
Just follow those steps, doesn't matter if you have the bootloader locked.
Important:
Next time, unlock the bootloader and install a custom recovery, twrp is the most common. After that flash the 8.1, it will reboot several times like if it has a problem but thats just the android config. Don't panic if you see it reach the homescreen and reboot, 3 or 4 times. It will do that untill you see the finishing progress bar prompt when it boots to homescreen
will give a try with this to see if it works.
edit tried, with 7.0 and the second command says preflash validation failed, with 8.1.0 the phone says okay all the commands but when i reboot the phone gets stuck on the blue m logo
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.