Search the thread, been asked a dozen times.
The information you have shown is of no relevance to the problem... If you are flashing the same version of firmware, factory reset in stock recovery, then flash it in fastboot, if it fails include the terminal log.Hello guys,
I have one issue
How to get through this thing "Allow OEM Unlocking" from the developer option.
Since my Phone is in Bootloop so there is no chance of checking this option from settings
I tried flashing the same version of firmware with Fastboot and ADB
Need help please
(bootloader) date: 12-23-2015
(bootloader) sku: XT1550
(bootloader) battid: SNN5965A
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Thu Apr 6 15:21:11 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/osprey_retasia_ds_2gb/osp
(bootloader) ro.build.fingerprint[1]: rey_ud2:6.0.1/MPIS24.107-55-2-17/1
(bootloader) ro.build.fingerprint[2]: 9:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.226.17.osprey_ret
(bootloader) ro.build.version.full[1]: asia_ds_2gb.retasia.en.03
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LA.BR.1.1.3_RB1.
(bootloader) ro.build.version.qcom[1]: 05.01.00.032.015
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.10.49-g8299559 (hudsoncm
(bootloader) kernel.version[1]: @ilclbld53) (gcc version 4.8 (GCC) ) #1
(bootloader) kernel.version[2]: SMP PREEMPT Mon Jan 16 23:09:59 CST 2017
Sure, but you probably have it already...don't confuse the boot logo with the boot animation. The boot logo is the Moto logo that appears before the ROMs startup animation.
Sure, but you probably have it already...don't confuse the boot logo with the boot animation. The boot logo is the Moto logo that appears before the ROMs startup animation.
What phone do you haveWith success, no problems faced bro. To be clear, i was on 6.0.1 stock --> rooted and unlocked -- > 7.1 Custom ROM -> Clean Install of Stock ROM of 5.1.1 ( by clean install i mean i even formatted internal storage and everything , dont know if thats necessary )
Then , 5.1.1 still had ghost touch problems so reverted back to Lineage OS now without any problems.
Got a link? A comment like this means nothing unless you back it up... Others may find it useful.Edit: Found it after hours of search on and off. Tested and is real MPIS24.107-55-2-17 19.
There is some good costom ROMs out there I'm on 0ne 6.0 there is even 8.0 and 7.0 costum ROMs that work good with out bloat just saying have good dayHi
Based on the guide at https://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750 , I'm trying to flash my xt1543.
It has a 6.0_MPI24.65-33.1-2-16 version. The newer version that I founded in the forum is is 6.0.1_MPI24.107-55-2_cid12
Then I sent the first command:
fastboot oem fb_mode_set (returned okay, finished)
the next command was
fastboot flash partition gpt.bin
returned:
(bootloader) Preflash validation failed
FAILED (remote failure)
According to te guide, I downloaded a newer rom. In this case, what can I do?
Thanks
adb reboot-bootloader
adb reboot-bootloader
With Moto G (3rd Gen) in particular - not doing a 'factory data reset' has prevented Android booting for many people. It's also my experience with Moto G generally that not erasing userdata can introduce a wide range of issues, from very minor to very serious. I am now of the opinion that if you have not done a 'Factory data reset' in Android and erased userdata during fastboot flashing - you have not flashed Android properly. For best performance / experience, do what I say.Yes and no.
I mean reflashing same firmware.
If I reflash same firmware, but only system partition (or all files), I think it could work (to unroot) without erasing anything.
In nexus 7, reflashing same firmware without erasing user data is the right way to unroot.
Three days ago I upgraded from 5.1 to 6.0 without performing 'Factory data reset' and Android boots ok
The last thing you should ever do is touch the Bootloader on a device. It's completely unnecessary and stupidly dangerous.@lost101, do you think the downgrade could result if we flash only gtp.bin and bootloader (it will flash the old bootloader), reboot to bootloader (the old one now) and then flash the other partitions?
Sorry if this is a stupid question.