Develop Bugs

[SOLVED] Won't boot and random fastboot errors after upgrade attempt

Hi,
Short story:
My One X won't boot to Android anymore. I can only enter boot / fastboot modes.
And when trying to apply modifications (fastboot flash or fastboot unlock), it shows various errors, not always the same.
Long story:
I bought this phone second hand quite a while ago, soon after its market launch. It was already unlocked and rooted, but I don't know what method had been used.
RUU says it runs release 1.28.
Boot says:
- S-On
- HBoot-0.94.0000
- Radio 1.1204.103.14
- Apr 11 2012,02:27:11
Given that it was unlocked / rooted it never received an OTA.
I recently decided to perform a full wipe, and by the way a full upgrade.
So:
- I did a CWM Recovery backup
- I flashed a «semi-stock» image, the stock de-odexed 4.18.401.3 from android-revolution (URL forbidden here, I'm a newbie!) .
- I performed a full wipe / factory reset / cache cleaning / Dalvik cache cleaning.
It didn't boot, and I learnt about the ICS / JB hboot incompatibility.
I tried to flash the boot from the android-revolution page, with no improvements.
So, I decided to revert to my Nandroid backup, from the recovery.
Didn't boot either.
Then I found a Windows computer, relocked the bootloader, and tried RUUs (3.14 and 1.26) with no success.
CID is HTC__203, so I used .401 RUU or OTA files.
RUU application stops each time at a different moment, either for usb connexion error, wrong RUU for my phone, not enough battery, or unknown error.
I read about a battery charge issue, and tried this method to charge it:
Code:
while : ; do fastboot getvar battery-voltage; fastboot reboot-bootloader; sleep 6; done
(as you may see, my main workstation is running Linux)
After a 9 hours long night:
Code:
< waiting for device >
battery-voltage: 3610mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.177s]
finished. total time: 0.177s
< waiting for device >
battery-voltage: 3610mV
finished. total time: 0.100s
rebooting into bootloader...
OKAY [ 0.177s]
finished. total time: 0.177s
It seems that it couldn't go farther than 3.6V.
But if I tried to unlock my phone after that:
Code:
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
FAILED (remote: battery low)
finished. total time: 0.353s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 1.140s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (remote: unknown command)
finished. total time: 1.140s
[[email protected] htc_one_x]# fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] htc_one_x]#
You can see error message is not always the same.
Same for my firmware.zip flash attempts:
Code:
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot oem rebootRUU
...
FAILED (remote: unknown command)
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot oem rebootRUU
...
FAILED (command write failed (Cannot send after transport endpoint shutdown))
finished. total time: 5.928s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
OKAY [ 1.419s]
writing 'zip'...
FAILED (remote: 13 battery low)
finished. total time: 1.629s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (remote: unknown command)
finished. total time: 1.005s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (remote: unknown command)
finished. total time: 1.005s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]# fastboot flash zip firmware.zip
sending 'zip' (10967 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
[[email protected] OTA_ENDEAVOR_U_ICS_40_S_HTC_Europe_2.17.401.2-1.29.401.11_release_2749568xzb2t6wu96omqzo]#
What is the real issue? Why can't it give me a consistent error ?
What else could I try?
Thanks for reading this long post and trying to help me!

hervenicol said:
Hi,
What is the real issue? Why can't it give me a consistent error ?
What else could I try?
Thanks for reading this long post and trying to help me!
Click to expand...
Click to collapse
Give me result from command fastboot getvar version-main
Download this fastboot.zip and extract it to a folder fastboot rename the file fastboot-linux to fastboot. The file fastboot only is for windows and if you want to keep it rename fastboot to fastboot-windows

Thant said:
Give me result from command fastboot getvar version-main
Click to expand...
Click to collapse
Here it is, with both versions of fastboot:
1 - my one, from the Android SDK
2 - yours
Code:
[[email protected] fastboot]# fastboot getvar version-main
version-main: 1.28.401.9
finished. total time: 0.006s
[[email protected] fastboot]# ./fastboot getvar version-main
version-main: 1.28.401.9
[[email protected] fastboot]#

hervenicol said:
Here it is, with both versions of fastboot:
1 - my one, from the Android SDK
2 - yours
Code:
[[email protected] fastboot]# fastboot getvar version-main
version-main: 1.28.401.9
finished. total time: 0.006s
[[email protected] fastboot]# ./fastboot getvar version-main
version-main: 1.28.401.9
[[email protected] fastboot]#
Click to expand...
Click to collapse
1. Charge your phone
2. Download this RUU 1.28.401.9
3. Lock your bootloader with command fastboot oem lock
4. Run the RUU as administrator
5. Aplly all update to latest JB from Settings/Software update

Thant said:
1. Charge your phone
2. Download RUU 1.28.401.9 (link removed from quote)
3. Lock your bootloader with command fastboot oem lock
4. Run the RUU as administrator
5. Aplly all update to latest JB from Settings/Software update
Click to expand...
Click to collapse
That's exactly what I was trying to do.
I finally succeeded, few minutes ago, after charging to 3920mv.
It looks like the USB cable quality has a big impact on the charging capabilities:
- with a cheap cable I couldn't go farther than 3.6xx V.
- When I changed my cable, it was charging much faster, up to 3.9xx V.
…then at this level of charge the RUU*worked.
Thanks anyway for your help! :good:
Now it's doing OTA*updates…

hervenicol said:
That's exactly what I was trying to do.
I finally succeeded, few minutes ago, after charging to 3920mv.
It looks like the USB cable quality has a big impact on the charging capabilities:
- with a cheap cable I couldn't go farther than 3.6xx V.
- When I changed my cable, it was charging much faster, up to 3.9xx V.
…then at this level of charge the RUU*worked.
Thanks anyway for your help! :good:
Now it's doing OTA*updates…
Click to expand...
Click to collapse
Good to hear that:good:

All upgrades applied, works like a charm
I set the title for this answer with [SOLVED], I hope it applies to the thread as well.
Now let's look for a way to root this rom!

[Q] LG g3 stay in fastboot and can't flash anything

hi guys
i have lg g3 D855 after update its dead and now its only stay on lg logo i tried to flash new rom but when i try to go the download mode its going to fastboot mood then i try to flash laf.img its give me this error
C:\New folder\Minimal ADB and Fastboot>fastboot flash boot boot.img
target reported max download size of 2147483648 bytes
sending 'boot' (12800 KB)...
OKAY [ 0.406s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 10.470s
C:\New folder\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 2147483648 bytes
sending 'laf' (17408 KB)...
OKAY [ 0.552s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 10.617s
C:\New folder\Minimal ADB and Fastboot>fastboot erase laf
erasing 'laf'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.036s
also i get the same error with flashing the recovery file
so whats wrong and what should i do to fix this?

Run fastboot boot laf.img
Plug G3 into LGFlashTool and flash KDZ using CSM flash

itsbighead said:
Run fastboot boot laf.img
Plug G3 into LGFlashTool and flash KDZ using CSM flash
Click to expand...
Click to collapse
thx for replay me
i did that (fastboot boot laf.img) its say done with showing some words on the phone monitor but nothing happen also still cant go the flash mode

Try this
Boot into TWRP
Enable MTP and copy laf.img to sdcard
Go to Terminal Command in Advanced
Run the commands below using TWRP
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
dd if=/sdcard/laf.img of=/dev/block/platform/msm_sdcc.1/by-name/laf

[DEV][N][DP2][CRACKLING]Android N Developer Preview

Hi all.
Here Android N for Swift
Needed files here -> https://secure.wlfx.tech
Latest = DP2
Manual:
Unlock bootloader
Install TWRP
Install OEM
Download OEM oem.img
Enter commands into fastboot
Code:
fastboot -i 0x2970 erase oem
Code:
fastboot -i 0x2970 flash oem oem.img
Download files from here (Only System and Boot)
Flash files
Code:
fastboot flash boot boot.img
Code:
fastboot flash system system.img
Reboot into TWRP
Make wipe data & wipe cache
Reboot phone
All works fine.
Sorry for my bad english and russian site server.

FindYanot said:
Hi all.
Here Android N for Swift
Needed files here -> https://secure.wlfx.tech/ANDROIDN
Manual:
Wipe data
Bot into fastboot
Use this commands:
fastboot flash boot boot.img
fastboot flash oem oem.img
fastboot flash system system.img
All works fine.
Sorry for my bad english and russian site server.
Click to expand...
Click to collapse
IFlashed. Works fine so far. Gapps are included in preview. Many thanks

FindYanot said:
Hi all.
Here Android N for Swift
Needed files here -> https://secure.wlfx.tech
Manual:
Wipe data
Bot into fastboot
Use this commands:
fastboot flash boot boot.img
fastboot flash oem oem.img
fastboot flash system system.img
All works fine.
Sorry for my bad english and russian site server.
Click to expand...
Click to collapse
Just curious. Does it have root? I am going to flash if in an hour or 2
---------- Post added at 05:55 AM ---------- Previous post was at 05:33 AM ----------
yasteellutch said:
Just curious. Does it have root? I am going to flash if in an hour or 2
Click to expand...
Click to collapse
Does it have OTA?
---------- Post added at 06:32 AM ---------- Previous post was at 05:55 AM ----------
yasteellutch said:
Just curious. Does it have root? I am going to flash if in an hour or 2
---------- Post added at 05:55 AM ---------- Previous post was at 05:33 AM ----------
Does it have OTA?
Click to expand...
Click to collapse
I am having an issue flashing. I flash using TWRP and when I reboot it says "No OS Installed". Also when I tried via fastboot. Is there any thing I am missing?

No root and OTA.
Before flashing via fastboot wipe data through twrp.

mermigas said:
No root and OTA.
Before flashing via fastboot wipe data through twrp.
Click to expand...
Click to collapse
Could you upload a screenshot?

mermigas said:
No root and OTA.
Before flashing via fastboot wipe data through twrp.
Click to expand...
Click to collapse
I did exactly that and still stuck in boot

http://4pda.ru/forum/index.php?showtopic=730213&st=120#entry47858392
Use Google translate to see instructions

Phew! some development on the Crackling!
:good:
Very impressed... TWRP method didn't wrk, fastboot worked fine! thankyou for bringing it here too, my Russian is non existent
My 1st impressions:
Very good, I haven't encountered any major issues..... I'll keep testing

Well, I just installed on my trusty Wileyfox Swift.
Overall I'm impressed, however the sensors are not working- gyro/ accelerometer/ proximity. There is some conflict with libraries when starting a game.
With a few more updates (fingers crossed) I can see myself using it as a daily driver
Everything else works and works really well. The phone seems a lot faster, the SDcard was formatted (haven't tested using an app from it but games are out of the question anyway), dual-window will be neat and is fine at the moment.
There is a lot to like here with few issues.
PS: After reading a bit from the older threads on XDA and from 4pda.ru , it seems the sensor issue is connected to the bridge to enable Android One roms with FindYanot's oem image on our crackling. Really impressive thus far. I wonder if we can flash General Mobile 4G firmware with QFIL?

I've tried this firmware on my phone and I'd like to share both experience and expressions.
Main laptop is MacBook Air, so it was quite hard to find working fastboot, adb ot GUI utilities.
Finally, I've installed them with command:
Code:
bash <(curl -s https://raw.githubusercontent.com/corbindavenport/nexus-tools/master/install.sh)
Then I tried to unlock the bootloader and flash images:
Code:
Sergeys-MacBook-Air:tools cleversokol$ adb devices
List of devices attached
adb server is out of date. killing...
adb I 4550 408520 usb_osx.cpp:259] Found vid=2970 pid=2282 serial=bf2ecad9
adb I 4550 408520 usb_osx.cpp:259]
* daemon started successfully *
bf2ecad9 unauthorized
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
As you can see, I had failed unlocking the bootloader and I did not install TWRP. Also, without TWRP I had not done wipe.
Code:
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.002s
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (18457 KB)...
OKAY [ 0.667s]
writing 'boot'...
OKAY [ 1.835s]
finished. total time: 2.502s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash oem oem.img
target reported max download size of 268435456 bytes
sending 'oem' (6128 KB)...
OKAY [ 0.224s]
writing 'oem'...
OKAY [ 0.734s]
finished. total time: 0.958s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 1.131s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.011s]
writing 'system'...
OKAY [ 21.393s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.789s]
writing 'system'...
OKAY [ 20.547s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.854s]
writing 'system'...
OKAY [ 20.591s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.522s]
writing 'system'...
OKAY [ 20.518s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.106s]
writing 'system'...
OKAY [ 21.263s]
sending sparse 'system' (23028 KB)...
OKAY [ 0.978s]
writing 'system'...
OKAY [ 1.729s]
finished. total time: 165.433s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.001s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
< waiting for any device >
After flashing this three images I got a brick. Phone showed Wileyfox logo once and turned off. After ejecting/inserting battery, it responsed (once) to Power button, but showed only logo and turned off again.
Eject/insert battery again and pressing Power + VolDown took me to some menu. From it I've reached fastboot menu.
With windows-laptop and WileyFox Tool utility I pressed Check bootloader status button. Phone restarted and I got Android N boot animation. Then restarted again and finally I'm in Android N First Setup Utility.
Working:
— screen, touchscreen, brightness ajustment (manual)
— mic, speaker
— charging
— GPS
— 4G
— Wi-Fi
— camera (video does not work)
— night mode
— multi-window mode
Not working:
— sensors
— some apps show library mismatch
Also, Power + VolDown button now does not take me to recovery menu. It shows android with red exclamation point. I think it's not right.

cleversokol said:
I've tried this firmware on my phone and I'd like to share both experience and expressions.
Main laptop is MacBook Air, so it was quite hard to find working fastboot, adb ot GUI utilities.
Finally, I've installed them with command:
Code:
bash <(curl -s https://raw.githubusercontent.com/corbindavenport/nexus-tools/master/install.sh)
Then I tried to unlock the bootloader and flash images:
Code:
Sergeys-MacBook-Air:tools cleversokol$ adb devices
List of devices attached
adb server is out of date. killing...
adb I 4550 408520 usb_osx.cpp:259] Found vid=2970 pid=2282 serial=bf2ecad9
adb I 4550 408520 usb_osx.cpp:259]
* daemon started successfully *
bf2ecad9 unauthorized
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
As you can see, I had failed unlocking the bootloader and I did not install TWRP. Also, without TWRP I had not done wipe.
Code:
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.002s
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
Sergeys-MacBook-Air:tools cleversokol$ adb reboot bootloader
Sergeys-MacBook-Air:tools cleversokol$ fastboot devices
bf2ecad9 fastboot
Sergeys-MacBook-Air:tools cleversokol$ fastboot -i 0x2970 oem unlock-go
< waiting for any device >
^C
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash boot boot.img
target reported max download size of 268435456 bytes
sending 'boot' (18457 KB)...
OKAY [ 0.667s]
writing 'boot'...
OKAY [ 1.835s]
finished. total time: 2.502s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash oem oem.img
target reported max download size of 268435456 bytes
sending 'oem' (6128 KB)...
OKAY [ 0.224s]
writing 'oem'...
OKAY [ 0.734s]
finished. total time: 0.958s
Sergeys-MacBook-Air:tools cleversokol$ fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 1.131s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.011s]
writing 'system'...
OKAY [ 21.393s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.789s]
writing 'system'...
OKAY [ 20.547s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.854s]
writing 'system'...
OKAY [ 20.591s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.522s]
writing 'system'...
OKAY [ 20.518s]
sending sparse 'system' (262140 KB)...
OKAY [ 11.106s]
writing 'system'...
OKAY [ 21.263s]
sending sparse 'system' (23028 KB)...
OKAY [ 0.978s]
writing 'system'...
OKAY [ 1.729s]
finished. total time: 165.433s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
rebooting...
finished. total time: 0.001s
Sergeys-MacBook-Air:tools cleversokol$ fastboot reboot
< waiting for any device >
After flashing this three images I got a brick. Phone showed Wileyfox logo once and turned off. After ejecting/inserting battery, it responsed (once) to Power button, but showed only logo and turned off again.
Eject/insert battery again and pressing Power + VolDown took me to some menu. From it I've reached fastboot menu.
With windows-laptop and WileyFox Tool utility I pressed Check bootloader status button. Phone restarted and I got Android N boot animation. Then restarted again and finally I'm in Android N First Setup Utility.
Working:
— screen, touchscreen, brightness ajustment (manual)
— mic, speaker
— charging
— GPS
— 4G
— Wi-Fi
— camera (video does not work)
— night mode
— multi-window mode
Not working:
— sensors
— some apps show library mismatch
Also, Power + VolDown button now does not take me to recovery menu. It shows android with red exclamation point. I think it's not right.
Click to expand...
Click to collapse
I've had the opposite experience. Fastboot works without fail on Mac and Linux. Windows- not so much with the Swift.
Flash TWRP manually - fastboot flash recovery your_recovery_image.img (replace with the file name for TWRP)
You've just installed the patched oem.img (to allow code name "seed" images) along with boot and system. Can't boot to recovery if you don't have one
Steer away from flashing other files from the Android One stock image (it will be even messier hardbrick and you would have to follow the instructions from the other thread).
If you want to return to stock COS, follow the instructions from these awesome people : http://forum.cyanogenmod.org/topic/118287-manual-flashing-of-stock-cyanogenos/
PS: For some reason, unlocking the bootloader for me worked with: fastboot oem unlock-go
but not with:
fastboot -i 0x2970 oem unlock-go
Locking with: fastboot oem lock-go , worked as expected

Can I use this TWRP? I did not found Wileyfox Swift among supported devices.

cleversokol said:
Can I use this TWRP? I did not found Wileyfox Swift among supported devices.
Click to expand...
Click to collapse
I believe this is the one I've used.
In case the Windows tool for Wileyfox works for you (I'm missing some C# utilities on mine and can't deal with it atm), you can add TWRP from there as well.
PS: I used it only to install initially this preview. I haven't used it after.

Sucessfully installed TWRP3.0 (CM13-nightly-recovery did not work for me. Keep getting image of Android with red exclamation mark), wiped cache, data and installed CM13-nightly + GAPPS Mini. Booted into CM, did basic setup. After that I wanted to re-lock the bootloader.
With
Code:
fastboot oem lock-go
it worked, but after this command I got brick-phone again.
Only replacing the battery + re-unlocking the device helped to restore it.
Is there a way to keep device working with locked bootloader?

Lock the bootloader only if you'll be using stock signed images of CyanogenOS. That is in case you will have to return the device due to hardware fault- dead pixels, non functioning microphones/ speakers, etc. Another reason as of why you might want to relock, is to ensure that you'll be using CyanogenOS recovery and no problems with future OTAs (no guarantee there as encrypted devices had problems with first official update but things are looking nice for future official OTAs).
If you want to use custom recovery- TWRP/CMRecovery by itself or along with CyanogenMod13 or any other custom ROM- do not lock the bootloader.
These are your options Keep the bootloader unlocked unless you have the need/ desire to return it to true stock.

I tried to install it again and it doesn't work. I flashed stock and unlocked my bootloader. I managed to flash OEM and BOOT but it doesn't want to flash the system partition at all. I tried everything. I tried 4pda method too. Am I missing something?

yasteellutch said:
I tried to install it again and it doesn't work. I flashed stock and unlocked my bootloader. I managed to flash OEM and BOOT but it doesn't want to flash the system partition at all. I tried everything. I tried 4pda method too. Am I missing something?
Click to expand...
Click to collapse
System img is big and post propably your fastboot installer cannot handle it.
Try this fastboot installer
http://forum.xda-developers.com/showthread.php?t=2588979

This is the one I'm using. Mininimal adb and and fastboot . it won't work. Even tried with android studio
---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------
yasteellutch said:
This is the one I'm using. Mininimal adb and and fastboot . it won't work. Even tried with android studio
Click to expand...
Click to collapse
It keeps on saying sending sparse system img(0kb)

yasteellutch said:
This is the one I'm using. Mininimal adb and and fastboot . it won't work. Even tried with android studio
---------- Post added at 12:26 PM ---------- Previous post was at 12:25 PM ----------
It keeps on saying sending sparse system img(0kb)
Click to expand...
Click to collapse
Just try this
http://androidhost.org/P2XKs
unzip to your root directory - copy Android N images to this directory and give it a try.

mermigas said:
Just try this
http://androidhost.org/P2XKs
unzip to your root directory - copy Android N images to this directory and give it a try.
Click to expand...
Click to collapse
This is what I get

How to unlock bootloader when OEM unlocking option is disabled

Hello,
I am asking here is there a way to unlock bootloader?
The situation is:
- the phone is in boot loop.
- the phone boots to download mode every time.
- cannot access to recovery mode from fastmode.
- cannot apply LG tot to refurbish in download mode. It now deads at 4% of the process.
- and the last, I didn't enable OEM unlocking when the phone was still functioning.
Adb, fastboot, I tried all the commands that I know so far, but no help.
I know that I have to enable OEM unlocking to be able to unlock bootloader. But again, I cannot boot in to do it.
So just hope that some experts might know a way.

You don't have a possibility to unlock it!
The only way is by settings from working phone.
S C:\Android\platform-tools> .\fastboot.exe devices
0171046759b8474f fastboot
PS C:\Android\platform-tools> fastboot flashing get_unlock_ability
...
(bootloader) get_unlock_ability: 1
OKAY [ 0.020s]
finished. total time: 0.021s
PS C:\Android\platform-tools> fastboot.exe flashing unlock
...
OKAY [ 9.244s]
finished. total time: 9.247s
PS C:\Android\platform-tools> fastboot.exe flashing unlock
...
FAILED (remote: Already unlocked)
finished. total time: 0.008s
PS C:\Android\platform-tools> fastboot flash boot boot-fixed.img
target reported max download size of 536870912 bytes
sending 'boot' (11797 KB)...
OKAY [ 0.321s]
writing 'boot'...
OKAY [ 0.137s]
finished. total time: 0.461s
PS C:\Android\platform-tools> fastboot flash recovery recovery-fixed.img
target reported max download size of 536870912 bytes
sending 'recovery' (17437 KB)...
OKAY [ 0.459s]
writing 'recovery'...
OKAY [ 0.209s]
finished. total time: 0.671s
PS C:\Android\platform-tools>

Sigh,
So no more hope.
Thank you ^_^

Try the battery discharge trick described by sd_cb on the page Fix-a-Brick: Fighting the Nexus 5X Bootloop:
"One trick I learned for my bootlooped 5X is that first you let the phone completely drain of battery (boot into recovery and let it sit). Then, plug in the phone and boot up. I would get ~1 minute in the phone before it would reset. What did this do for me? It allowed me to recover my 2 factor codes that I was stupid enough not to print or save to begin with. Lesson learned"

Stucked In BootLoop, tried a lot of things

Hi, Have an MOTO G 5 XT 1672 In inifinity loop, he has oem_locked,
in fastboot mode i select recovery mode and shows logo and loop again, don't give me the option "no command" for wipe data. Tried the Lenovo Rescue and Smart Assistant, she find the smartphone, flash the system and give me success, but the phone shows nothing different. He continues loop in boot logo.
Tried manually with ADB with the actual firmware and comands lines but no success too. i dont know what to do.
If someone give me an light i will apreciate.

welitonxdd said:
Hi, Have an MOTO G 5 XT 1672 In inifinity loop, he has oem_locked,
in fastboot mode i select recovery mode and shows logo and loop again, don't give me the option "no command" for wipe data. Tried the Lenovo Rescue and Smart Assistant, she find the smartphone, flash the system and give me success, but the phone shows nothing different. He continues loop in boot logo.
Tried manually with ADB with the actual firmware and comands lines but no success too. i dont know what to do.
If someone give me an light i will apreciate.
Click to expand...
Click to collapse
Does it give any error, when flashing the stock Oreo. Like permission denied for erase user data or any other?

welitonxdd said:
Hi, Have an MOTO G 5 XT 1672 In inifinity loop, he has oem_locked,
in fastboot mode i select recovery mode and shows logo and loop again, don't give me the option "no command" for wipe data. Tried the Lenovo Rescue and Smart Assistant, she find the smartphone, flash the system and give me success, but the phone shows nothing different. He continues loop in boot logo.
Tried manually with ADB with the actual firmware and comands lines but no success too. i dont know what to do.
If someone give me an light i will apreciate.
Click to expand...
Click to collapse
In fastboot mode type the following
fastboot erase userdata
This is the equivalent of doing a factory reset - all data will be erased including anything on internal storage
Without a full hardware/software diagnosis of your phone there really isn't anything else to suggest

riyan65 said:
Does it give any error, when flashing the stock Oreo. Like permission denied for erase user data or any other?
Click to expand...
Click to collapse
No error, give me success, but nothing happens
TheFixItMan said:
In fastboot mode type the following
fastboot erase userdata
This is the equivalent of doing a factory reset - all data will be erased including anything on internal storage
Without a full hardware/software diagnosis of your phone there really isn't anything else to suggest
Click to expand...
Click to collapse
i made this but nothing happens, i have no idea what to do now see video
youtube
watch?v=4apyEzljmjA

welitonxdd said:
No error, give me success, but nothing happens
i made this but nothing happens, i have no idea what to do now see video
youtube
watch?v=4apyEzljmjA
Click to expand...
Click to collapse
It looks like you have no rom installed either due to flashing wrong firmware or incomplete flashing or you have a hardware fault
Download firmware from below - make sure it's the same android version as you currently have eg android 7 or 8
https://mirrors.lolinet.com/firmware/moto/cedric/official/
Commands to use
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot
Post output - note if you get security downgrade error flashing gpt or bootloader the firmware is too old
If you get permission denied try a different firmware as your device does not have an unlocked bootloader you can't flash unsigned firmware parts

TheFixItMan said:
Post output - note if you get security downgrade error flashing gpt or bootloader the firmware is too old
If you get permission denied try a different firmware as your device does not have an unlocked bootloader you can't flash unsigned firmware parts
Click to expand...
Click to collapse
before I had done it this way, without success too, now that I tried again this option of "is logical not found" appears, but even with this option it seems that the command has tried several firmwares but the one that does not give the mentioned error is last one
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
D:\adbmoto>fastboot flash partition gpt.bin
(bootloader) is-logicalartition: not found
Sending 'partition' (45 KB) OKAY [ 0.171s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.091s]
Finished. Total time: 0.286s
D:\adbmoto>fastboot flash bootloader bootloader.img
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5179 KB) OKAY [ 0.499s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.555s]
Finished. Total time: 1.075s
D:\adbmoto>fastboot flash logo logo.bin
(bootloader) is-logical:logo: not found
Sending 'logo' (2242 KB) OKAY [ 0.478s]
Writing 'logo' OKAY [ 0.100s]
Finished. Total time: 0.608s
D:\adbmoto>fastboot flash boot boot.img
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 1.710s]
Writing 'boot' OKAY [ 0.430s]
Finished. Total time: 2.177s
D:\adbmoto>fastboot flash recovery recovery.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 1.316s]
Writing 'recovery' OKAY [ 0.441s]
Finished. Total time: 1.779s
D:\adbmoto>fastboot flash dsp adspso.bin
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 1.477s]
Writing 'dsp' OKAY [ 0.282s]
Finished. Total time: 1.803s
D:\adbmoto>fastboot flash oem oem.img
(bootloader) is-logicalem: not found
Sending 'oem' (148900 KB) OKAY [ 4.891s]
Writing 'oem' OKAY [ 7.660s]
Finished. Total time: 21.190s
D:\adbmoto>fastboot flash system system.img_sparsechunk.0
(bootloader) is-logical:system: not found
Sending 'system' (258344 KB) OKAY [ 8.377s]
Writing 'system' OKAY [ 5.902s]
Finished. Total time: 17.582s
D:\adbmoto>fastboot flash system system.img_sparsechunk.1
(bootloader) is-logical:system: not found
Sending 'system' (256570 KB) OKAY [ 8.307s]
Writing 'system' OKAY [ 5.519s]
Finished. Total time: 17.536s
D:\adbmoto>fastboot flash system system.img_sparsechunk.2
(bootloader) is-logical:system: not found
Sending 'system' (246510 KB) OKAY [ 8.012s]
Writing 'system' OKAY [ 6.545s]
Finished. Total time: 19.623s
D:\adbmoto>fastboot flash system system.img_sparsechunk.3
(bootloader) is-logical:system: not found
Sending 'system' (262141 KB) OKAY [ 8.472s]
Writing 'system' OKAY [ 7.533s]
Finished. Total time: 19.463s
D:\adbmoto>fastboot flash system system.img_sparsechunk.4
(bootloader) is-logical:system: not found
Sending 'system' (261322 KB) OKAY [ 8.451s]
Writing 'system' OKAY [ 11.216s]
Finished. Total time: 24.197s
D:\adbmoto>fastboot flash system system.img_sparsechunk.5
(bootloader) is-logical:system: not found
Sending 'system' (262141 KB) OKAY [ 8.481s]
Writing 'system' OKAY [ 5.513s]
Finished. Total time: 17.029s
D:\adbmoto>fastboot flash system system.img_sparsechunk.6
(bootloader) is-logical:system: not found
Sending 'system' (262143 KB) OKAY [ 8.489s]
Writing 'system' OKAY [ 6.678s]
Finished. Total time: 19.322s
D:\adbmoto>fastboot flash system system.img_sparsechunk.7
(bootloader) is-logical:system: not found
Sending 'system' (256817 KB) OKAY [ 8.302s]
Writing 'system' OKAY [ 6.812s]
Finished. Total time: 20.305s
D:\adbmoto>fastboot flash system system.img_sparsechunk.8
(bootloader) is-logical:system: not found
Sending 'system' (237909 KB) OKAY [ 7.713s]
Writing 'system' OKAY [ 7.424s]
Finished. Total time: 18.200s
D:\adbmoto>fastboot flash modem NON-HLOS.bin
(bootloader) is-logical:modem: not found
Sending 'modem' (66358 KB) OKAY [ 2.278s]
Writing 'modem' OKAY [ 1.050s]
Finished. Total time: 5.473s
D:\adbmoto>fastboot erase modemst1
Erasing 'modemst1' OKAY [ 0.035s]
Finished. Total time: 0.041s
D:\adbmoto>fastboot erase modemst2
Erasing 'modemst2' OKAY [ 0.036s]
Finished. Total time: 0.041s
D:\adbmoto>fastboot flash fsg fsg.mbn
(bootloader) is-logical:fsg: not found
Sending 'fsg' (2956 KB) OKAY [ 0.440s]
Writing 'fsg' OKAY [ 0.119s]
Finished. Total time: 0.589s
D:\adbmoto>fastboot erase cache
Erasing 'cache' OKAY [ 0.009s]
Finished. Total time: 0.014s
D:\adbmoto>fastboot erase userdata
Erasing 'userdata' OKAY [ 0.176s]
Finished. Total time: 0.183s
D:\adbmoto>fastboot oem fb_mode_clear
OKAY [ 0.002s]
Finished. Total time: 0.004s
D:\adbmoto>fastboot reboot
Rebooting OKAY [ 0.002s]
Finished. Total time: 0.004s
D:\adbmoto>
Click to expand...
Click to collapse

welitonxdd said:
before I had done it this way, without success too, now that I tried again this option of "is logical not found" appears, but even with this option it seems that the command has tried several firmwares but the one that does not give the mentioned error is last one
Click to expand...
Click to collapse
There's no errors in the output and everything is normal
Although unlikely to be causing an issue remove any sdcard and sim card from the device & try to boot
If it's still not booting after you have left it trying to boot for a while you may have a hardware fault
There's not really anything I can suggest - you can try using a different fastboot
Try using the mfastboot in the attachment below
Copy firmware to same directory as mfastboot
The commands are the same as above but instead of typing fastboot before each command type mfastboot

TheFixItMan said:
There's no errors in the output and everything is normal
Although unlikely to be causing an issue remove any sdcard and sim card from the device & try to boot
If it's still not booting after you have left it trying to boot for a while you may have a hardware fault
There's not really anything I can suggest - you can try using a different fastboot - I'll upload it in a min
Click to expand...
Click to collapse
the procediments was made without SIM and SD cards. i think the only answers now is the hardware fault.
thanks for your attention. and response in my topic.

welitonxdd said:
the procediments was made without SIM and SD cards. i think the only answers now is the hardware fault.
thanks for your attention. and response in my topic.
Click to expand...
Click to collapse
Try with the mfastboot I just posted in post above just incase the version you're using has issues - just substitute fastboot for mfastboot in the commands

TheFixItMan said:
Try with the mfastboot I just posted in post above just incase the version you're using has issues - just substitute fastboot for mfastboot in the commands
Click to expand...
Click to collapse
I finished now, the last hope was this, I did the procedure and it was the same way, after resetting it stays in the loop

welitonxdd said:
I finished now, the last hope was this, I did the procedure and it was the same way, after resetting it stays in the loop
Click to expand...
Click to collapse
Assuming you have tried the generic retail firmware there's not really anything else I can suggest
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

TheFixItMan said:
Assuming you have tried the generic retail firmware there's not really anything else I can suggest
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Yeah, already made with this firmware, the only accepted.
Strange is dont pass into recovery mode after fastboot screen. hardware fault sucks...
Another information is in Lenovo Smart Assistant continues showing RETBR, ive flashed only retail original