Hi everyone,
I had problems with my Moto X Force (UK) and bough second hand one to replace the board (was said was in bootloop), I tried to flash and it gives no errors but continued in bootloop, notice it has the bootloader locked and since I can't boot into the OS it doesn't let me to unlock using Motorola unique code.
Any suggestion?
P.S. replaced the board since I couldn't fix or get anyone able to fix the micro USB charging port.
Related
Hi guys,
this is a nexus 7 that i saw on sale online, owner says it can't boot and stuck here
http://center.jeddahbikers.com/uploads/images/jb13928760421.jpg
Is this something that can be saved or not, since all the resources i found are for a different error, it's the first time i saw this one.
Can anybody pitch in before i buy the device ?
It's impossible to tell. The device on the photo is stuck during booting into Android, so technically it can be booted into bootloader mode and flashed with a proper factory image, BUT the cause of the error can be hardware related (damaged emmc).
Hello,
I am writing this thread for a friend of mine. He owns a Z1 - stock ROM, locked bootloader.
Today it started looping and I tried to fix it (telling him over a chat what to do). It goes through the bootanimation and then dies or while optimizing apps, or while starting them.
What we tried:
1) Wipe cache
2) Factory reset
3) adb sideload the current official CM onto it
Nothing helped, the error stays the same. We also tried this http://forum.xda-developers.com/showpost.php?p=64458076&postcount=4 but it never really recognised the phone (despite using the correct drivers and following the procedure) - it did not appear under ports (Windows 10?).
Is there any other way to unlock this goddamn phone? My Androids so far had an easily unlockable bootloader via fastboot. This would have, too, but in order to unlock the bootloader via fastboot you first have to allow this in the developer settings - which we can not reach due to the loop.
If you know some way to get a working ROM onto it, we would be very happy. In the end we will end up unlocking the bootloader and flashing another Recovery and ROM anyway. We only need some way to achieve this. I expect the way to do this will be the QPST thingy. Any ideas why it did not recognise the phone? He does not own a PC with another OS than Win10...
Thanks in advance for your help,
Moritz
EDIT: Looks like the sideload did work - after tens of reboots it finally succeeded and bootet straight into the ROM.
Took a lot of attempts, strangely.
Proceeding to unlock it
Mine does the same boot loop on CM13. After tons of different tries to fix it, i think it could have something to do with my fingerprint sensor which is not working anymore.
Maybe there is some kind of hardware malfunction and android crashes while initializing that piece of hardware.
Hello and good day,
I have my Moto X Play XT1563, I bought it in Mexico and I wanted to Downgrade from Nougath to Lollipop (was trying to test a sensor) unfortunately I always have problem to identify my firmware image so I guess I flash one that is not for my phone (hate motorola has tons of variants), now the phone is always in the unlocked bootloader warning screen and then reboots to the same screen.
This is the file I flash:
XT1563_LUX_RETLA_DS_5.1.1_LPD23.118-32_CFC_v2.xml
My phone is XT1563 Dual SIM
Im able to enter download mode, recovery mode etc but seems debug mode is disabled as my phone is not detected by my PC so I cannot flash again,
Has anybody any idea how to fix this as I try to figure out but have no clue.
Thanks.
Just re-flash with fastboot, will update if succeed.
Have to Flash again Nougat with this one LUX_RETLA_DS_7.1.1_NPD26.48-24-1_cid12_subsidy-DEFAULT_CFC.xml.
Please some admin close this thread.
Thanks!
Does anyone know where a G950U1UES5DSF3 combination file is? I haven't had any luck finding one, and my phone got FRP locked. In order to use my phone (since I got water in my digitizer ) I need to use USB debugging. Well, the problem is, my phone is stuck on the setup screen and I cannot get passed it without enabling ADB somehow, because I flashed the new stock rom. Please, send help!
So, basically I will make this short as possible
Due to some problems I had to sell my G6 Plus (Brazilian -8 model) but it was on a custom rom, and did the most dumb thing that I could do: Reflashing pure stock and locking it, I've used the LMSA tool then relocked in Fastboot, the thing is some files were corrupt and when locked, it doesn't boot up anymore, as i still had hope for it, I tried to LSMA again, but it doesnt recognize anymore, as the lock flag is now "Flashing_Locked", flashing manually via Fastboot gives a error related to the lock flag (also LSMA resets the device, so using my unlock key asks to enable OEM Unlock at settings, a impossible thing when OS is broken) , then searched for some solutions, first it was booting a Boot.img file from the last stock, which was the flashed one, it bootloops, then tried something on the recovery that works, but is the stock one and pretty limited, so the logical thing to do is flashing a OTA file, but only works for old versions that requires one version before the target one, so its a no go. The last thing i tried to do is booting TWRP, but it gets stuck on a red warning that indicates that system is corrupt. Then the last hope was EDL Mode, and thats the point where i want to go, i've bought a EDL Cable that's basically a green and black wire thing used on most Qualcomm based Redmi/Xiaomi devices, but it automatically boots to fastboot, so I need help to get EDL Test Points for this device, im with access to the board, i just need the right Pads to short-circuit it and blankflash it, so i can finally get it to work like normal again.
Schematics (for people who understands): https://androidfilehost.com/?fid=4349826312261726244
Any help is important, I'm sorry for some typos, english isnt my main language considering i didnt use translate
and please don't come with instructions like "have you tried LSMA?, try booting up the device and select oem unlock" because its clear that it doesnt work.