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!

HTC Desire 816G cyanogenmod fastboot oem unlock issue

When i issue
sudo fastboot oem unlock
I am getting this error message
...
FAILED (remote: unknown command)
finished. total time: 0.002s
How to solve this issue?

Return to S-on?

I bought a WWE HTC 10 to use in the states... I used sunshine and have s-off locked status, I changed the cid and mid to the unlocked us numbers and did a conversion using the htc ruu.exe, I have a red warning every time i start the phone about development purposes only etc... I figure this must have to do with the s-off so i want to set it back to on as though i just bought a usa unlocked model!
im in download mode
I tried the good old
Code:
fastboot oem writesecureflag 3
and i got this output
Code:
...
(bootloader) HTC KEY CARD VERSION: 7
(bootloader) VERIFY_BY_PROJECT_SIGN_KEY_FAIL hosd (-9)
FAILED (remote: Partition verify fail -9)
finished. total time: 1.024s
what am i doing wrong?

THC Butterz said:
I bought a WWE HTC 10 to use in the states... I used sunshine and have s-off locked status, I changed the cid and mid to the unlocked us numbers and did a conversion using the htc ruu.exe, I have a red warning every time i start the phone about development purposes only etc... I figure this must have to do with the s-off so i want to set it back to on as though i just bought a usa unlocked model!
im in download mode
I tried the good old
Code:
fastboot oem writesecureflag 3
and i got this output
Code:
...
(bootloader) HTC KEY CARD VERSION: 7
(bootloader) VERIFY_BY_PROJECT_SIGN_KEY_FAIL hosd (-9)
FAILED (remote: Partition verify fail -9)
finished. total time: 1.024s
what am i doing wrong?
Click to expand...
Click to collapse
Go to bootloader mode?
Sent from my SM-G935T using Tapatalk

didnt work in bootloader mode at all
Code:
...
FAILED (remote: unknown command)
finished. total time: 0.052s
didnt work in uru mode either
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
OKAY [ 0.001s]
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem writesecureflag 3
...
(bootloader) HTC KEY CARD VERSION: 7
(bootloader) VERIFY_BY_PROJECT_SIGN_KEY_FAIL hosd (-9)
FAILED (remote: Partition verify fail -9)
finished. total time: 1.042s

THC Butterz said:
didnt work in bootloader mode at all
Code:
...
FAILED (remote: unknown command)
finished. total time: 0.052s
didnt work in uru mode either
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem rebootRUU
...
OKAY [ 0.001s]
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem writesecureflag 3
...
(bootloader) HTC KEY CARD VERSION: 7
(bootloader) VERIFY_BY_PROJECT_SIGN_KEY_FAIL hosd (-9)
FAILED (remote: Partition verify fail -9)
finished. total time: 1.042s
Click to expand...
Click to collapse
Actually if you still have the red warning then the Ruu likely didn't fully flash. You shouldn't have that message if it successfully flashes.
Sent from my SM-G935T using Tapatalk

dottat said:
Actually if you still have the red warning then the Ruu likely didn't fully flash. You shouldn't have that message if it successfully flashes.
Sent from my SM-G935T using Tapatalk
Click to expand...
Click to collapse
after speaking with jcase figgured out that because the ruu didnt mach the one the phone shipped with im sol for turning s-off back to s-on

THC Butterz said:
after speaking with jcase figgured out that because the ruu didnt mach the one the phone shipped with im sol for turning s-off back to s-on
Click to expand...
Click to collapse
Yeah I still believe that a fully flashed matching Ruu will clear that flag. Can you try flashing again and see if the dev flag clears?
Sent from my SM-G935T using Tapatalk

Help unbrick honor 7x frp locked, bootloader loked. rescue mode only save me or..?

Hi all,
I seen this community and some peoples very expert of honor 7x in many post pls help me to up to life my phone....... i continusly testing honor 7x because i love this model but something went wrong this time........... i forget to install twrprecovery and unfortunatly lock bootloader because in my mind i think when lock or relock the phone do hard reset and all partition go in right place.......but........ i think the phone erase all data and now i have bootloader loked frp loked and twrp screen bootloop when try to open phone with all conbination of key + pc don't recognized fastboot metod.... so i unmonted honor 7x and unmounted battery press volume down+power+usb cable and only in this way i can put file in phone with rescue mode fastboot and adb recognized the device "fastboot devices" with serial but frp and bootloader still locked.....
P.s.
-IF SOME ONE CAN HELP ME I WANT ONLY PUT STOCK RECOVERY OR TWRP then i can unbrick myself.. thank's hope in a responze me i'm so mad for this unluky brick because i do many attention when mod android device -_- but this time evil come to brick.....
-OR REMOUNT ALL IMAGES FILE BUT WITH DEVICE IN THIS STATE IS VERY difficult.....
-OR UNLOCK BOOTLOADER WITHOUT ENTER IN DEVELOPPERS OPTION I MEAN IN FAST BOOT BECAUSE I ONLY CAN USE RESCUE MODE..
here the results of fast boot mode hlep me and i can support you:
PS C:\adb> fastboot oem get-product-model
...
(bootloader) BND-L21
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.016s
PS C:\adb> fastboot oem get-build-number
...
(bootloader) :BND-L21 8.0.0.302(C432log)
OKAY [ 0.016s]
finished. total time: 0.016s
PS C:\adb> fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.016s
PS C:\adb> fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :BND-L21C432B121CUSTC432D001
OKAY [ 0.016s]
finished. total time: 0.016s
FAILED dload folder with oreo update.app single file or with other files in the zip..........
FAILED TO flash in fastboot rescue mode system (fastboot flash system system.img or other files .img).......
FAILED ALL TENTATIVES TO FLASH RECOVERY MANY TYPE ... because bootloader is closed.........
PS C:\adb> fastboot boot C:\adb\twrpimgmount_ramdisk.img
downloading 'boot.img'...
OKAY [ 0.501s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.517s
PS C:\adb> fastboot boot C:\adb\BND-RECOVERY-NoCheck.img
downloading 'boot.img'...
OKAY [ 1.222s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 1.238s
PS C:\adb> fastboot boot C:\adb\twrp_openkirin_sudeep.img
downloading 'boot.img'...
OKAY [ 0.851s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.853s
PS C:\adb> fastboot boot C:\adb\twrp_ramdisk_oreo_19-4-18.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
PLEASE TELL ME YOUR OPINION or if i paied FUNKY HUAWEI SOFTWARE for unbrick ..... or buy new mainboard.............
BEST REGARDS TO ALL COMUNITY....

JKmamba$ said:
Hi all,
I seen this community and some peoples very expert of honor 7x in many post pls help me to up to life my phone....... i continusly testing honor 7x because i love this model but something went wrong this time........... i forget to install twrprecovery and unfortunatly lock bootloader because in my mind i think when lock or relock the phone do hard reset and all partition go in right place.......but........ i think the phone erase all data and now i have bootloader loked frp loked and twrp screen bootloop when try to open phone with all conbination of key + pc don't recognized fastboot metod.... so i unmonted honor 7x and unmounted battery press volume down+power+usb cable and only in this way i can put file in phone with rescue mode fastboot and adb recognized the device "fastboot devices" with serial but frp and bootloader still locked.....
P.s.
-IF SOME ONE CAN HELP ME I WANT ONLY PUT STOCK RECOVERY OR TWRP then i can unbrick myself.. thank's hope in a responze me i'm so mad for this unluky brick because i do many attention when mod android device -_- but this time evil come to brick.....
-OR REMOUNT ALL IMAGES FILE BUT WITH DEVICE IN THIS STATE IS VERY difficult.....
-OR UNLOCK BOOTLOADER WITHOUT ENTER IN DEVELOPPERS OPTION I MEAN IN FAST BOOT BECAUSE I ONLY CAN USE RESCUE MODE..
here the results of fast boot mode hlep me and i can support you:
PS C:\adb> fastboot oem get-product-model
...
(bootloader) BND-L21
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.016s
PS C:\adb> fastboot oem get-build-number
...
(bootloader) :BND-L21 8.0.0.302(C432log)
OKAY [ 0.016s]
finished. total time: 0.016s
PS C:\adb> fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.016s
PS C:\adb> fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :BND-L21C432B121CUSTC432D001
OKAY [ 0.016s]
finished. total time: 0.016s
FAILED dload folder with oreo update.app single file or with other files in the zip..........
FAILED TO flash in fastboot rescue mode system (fastboot flash system system.img or other files .img).......
FAILED ALL TENTATIVES TO FLASH RECOVERY MANY TYPE ... because bootloader is closed.........
PS C:\adb> fastboot boot C:\adb\twrpimgmount_ramdisk.img
downloading 'boot.img'...
OKAY [ 0.501s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.517s
PS C:\adb> fastboot boot C:\adb\BND-RECOVERY-NoCheck.img
downloading 'boot.img'...
OKAY [ 1.222s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 1.238s
PS C:\adb> fastboot boot C:\adb\twrp_openkirin_sudeep.img
downloading 'boot.img'...
OKAY [ 0.851s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.853s
PS C:\adb> fastboot boot C:\adb\twrp_ramdisk_oreo_19-4-18.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
PLEASE TELL ME YOUR OPINION or if i paied FUNKY HUAWEI SOFTWARE for unbrick ..... or buy new mainboard.............
BEST REGARDS TO ALL COMUNITY....
Click to expand...
Click to collapse
this needs to come here n the open, not in my PM.
PS C:\adb> fastboot flash rescue_recovery_ramdisk C:\adb\twrp_openkirin_sudeep.img
target reported max download size of 471859200 bytes
sending 'rescue_recovery_ramdisk' (25164 KB)...
OKAY [ 0.854s]
writing 'rescue_recovery_ramdisk'...
OKAY [ 0.031s]
finished. total time: 0.885s
PS C:\adb> fastboot reboot
rebooting...
Click to expand...
Click to collapse
recovery flashed while frp and bootloader locked.
!!!!!!!!!!!!!
---------- Post added at 06:55 PM ---------- Previous post was at 06:16 PM ----------
What happens after reboot, try to boot to recovery with volume button, when you use
Code:
fastboot flash rescue_recovery_ramdisk RECOVERY_RAMDIS.img
recovery_ramdisk
does phone still have your broken twrp or the stock recovery?

JKmamba$ said:
https://ibb.co/nKOuRT
https://ibb.co/ccECD8
https://ibb.co/m1qxfo
for new users prevented post external link sorry .... you can for me?
Click to expand...
Click to collapse
so the fastboot command shows ok flashed, but its not changing the loaded recovery image.
don't know what to suggest next.

JKmamba$ said:
Hi all,
I seen this community and some peoples very expert of honor 7x in many post pls help me to up to life my phone....... i continusly testing honor 7x because i love this model but something went wrong this time........... i forget to install twrprecovery and unfortunatly lock bootloader because in my mind i think when lock or relock the phone do hard reset and all partition go in right place.......but........ i think the phone erase all data and now i have bootloader loked frp loked and twrp screen bootloop when try to open phone with all conbination of key + pc don't recognized fastboot metod.... so i unmonted honor 7x and unmounted battery press volume down+power+usb cable and only in this way i can put file in phone with rescue mode fastboot and adb recognized the device "fastboot devices" with serial but frp and bootloader still locked.....
P.s.
-IF SOME ONE CAN HELP ME I WANT ONLY PUT STOCK RECOVERY OR TWRP then i can unbrick myself.. thank's hope in a responze me i'm so mad for this unluky brick because i do many attention when mod android device -_- but this time evil come to brick.....
-OR REMOUNT ALL IMAGES FILE BUT WITH DEVICE IN THIS STATE IS VERY difficult.....
-OR UNLOCK BOOTLOADER WITHOUT ENTER IN DEVELOPPERS OPTION I MEAN IN FAST BOOT BECAUSE I ONLY CAN USE RESCUE MODE..
here the results of fast boot mode hlep me and i can support you:
PS C:\adb> fastboot oem get-product-model
...
(bootloader) BND-L21
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\adb> fastboot getvar vendorcountry
vendorcountry: hw/eu
finished. total time: 0.016s
PS C:\adb> fastboot oem get-build-number
...
(bootloader) :BND-L21 8.0.0.302(C432log)
OKAY [ 0.016s]
finished. total time: 0.016s
PS C:\adb> fastboot getvar rescue_enter_recovery
getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
finished. total time: 0.016s
PS C:\adb> fastboot oem oeminforead-SYSTEM_VERSION
...
(bootloader) :BND-L21C432B121CUSTC432D001
OKAY [ 0.016s]
finished. total time: 0.016s
FAILED dload folder with oreo update.app single file or with other files in the zip..........
FAILED TO flash in fastboot rescue mode system (fastboot flash system system.img or other files .img).......
FAILED ALL TENTATIVES TO FLASH RECOVERY MANY TYPE ... because bootloader is closed.........
PS C:\adb> fastboot boot C:\adb\twrpimgmount_ramdisk.img
downloading 'boot.img'...
OKAY [ 0.501s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.517s
PS C:\adb> fastboot boot C:\adb\BND-RECOVERY-NoCheck.img
downloading 'boot.img'...
OKAY [ 1.222s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 1.238s
PS C:\adb> fastboot boot C:\adb\twrp_openkirin_sudeep.img
downloading 'boot.img'...
OKAY [ 0.851s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.853s
PS C:\adb> fastboot boot C:\adb\twrp_ramdisk_oreo_19-4-18.img
downloading 'boot.img'...
OKAY [ 0.801s]
booting...
FAILED (remote: Command not allowed)
finished. total time: 0.801s
PLEASE TELL ME YOUR OPINION or if i paied FUNKY HUAWEI SOFTWARE for unbrick ..... or buy new mainboard.............
BEST REGARDS TO ALL COMUNITY....
Click to expand...
Click to collapse
HI, You said if you could put stock recovery then you can unbrick yourself. Can you elaborate on this please? Also, you tried the load method with the update.app so can you tell me where did you get that file? I'm in the same situation. I locked myself out completely trusting that the dload update.app method so that I could go back to complete stock as I was stuck in the emui 8 beta earlier with twrp installed with twrp backups. I have stock recovery "RECOVERY_RAMDIS.IMG" installed on my phone. I flashed it to get rid of TWRP so I could be on stock recovery.
I flashed stock recovery, relocked bootloader and tried the dload method and every time it fails at 5%. I'm using BND AL10C675 (INDIAN) so now I can't unlock bootloader because I need to enable "OEM unlock" in settings and I can't do that cos I can't boot into system as the system is formatted (NO OS) and so I can't install twrp or any system images nothing. I just locked myself out and I can't believe it. **** does happen

Thetpcguy said:
HI, You said if you could put stock recovery then you can unbrick yourself. Can you elaborate on this please? Also, you tried the load method with the update.app so can you tell me where did you get that file? I'm in the same situation. I locked myself out completely trusting that the dload update.app method so that I could go back to complete stock as I was stuck in the emui 8 beta earlier with twrp installed with twrp backups. I have stock recovery "RECOVERY_RAMDIS.IMG" installed on my phone. I flashed it to get rid of TWRP so I could be on stock recovery.
I flashed stock recovery, relocked bootloader and tried the dload method and every time it fails at 5%. I'm using BND AL10C675 (INDIAN) so now I can't unlock bootloader because I need to enable "OEM unlock" in settings and I can't do that cos I can't boot into system as the system is formatted (NO OS) and so I can't install twrp or any system images nothing. I just locked myself out and I can't believe it. **** does happen
Click to expand...
Click to collapse
let me chek man take a pictures of all single screen you'll see... RECOVERY, AFTER RECOVERY (bootloop logo, black screen ecc), and FAST BOOT MODE.. maybe i help you ... i won't to roll back my device because oreo is very perfomance but so buggy for exemple bluethoot don't worck multy shut on photograf bugged or many root application work and after 5 min close with (root with magisk -_-")... in nougat don't have ever this problem root with only super su and all unlocked....

i cant flash or erase any partition in fastboot mode

when ever i try to flash or erase a file in fastboot mode on my lg g4 i keep getting the error
FAILED (remote: cannot erase this partition in unlocked state)
finished. total time: 0.024s
and when i lock the bootloader in fastboot mode and try again i still get an error
erasing 'laf'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.023s
please what do i do? i really need your help

Mortal Killer said:
when ever i try to flash or erase a file in fastboot mode on my lg g4 i keep getting the error
FAILED (remote: cannot erase this partition in unlocked state)
finished. total time: 0.024s
and when i lock the bootloader in fastboot mode and try again i still get an error
erasing 'laf'...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.023s
please what do i do? i really need your help
Click to expand...
Click to collapse
Double post and Member requested to close the thread
THREAD CLOSED