Develop Bugs

Honor 8 pro DUK-L09C636B187 keep restarting after flashing Custom ROM

Hi all,
I have flashed dotOS custom ROM on my Honor 8 Pro. but i cant boot up after the installation, my phone keep restarting and cant boot up to dotOS..
Here is some of the details:
1)Firmware: Honor 8 pro DUK-L09C636B187
2) Bootloader: Unlocked
3) FRP Unlock
4) ADB terminal able to detect fastboot devices but not ADB devices
5) Able to go:
a)Fastboot mode
b) TWRP and eRecovery mode
c) EMUI mode
I have tried all these but failed:
1) Tried flashing DUK-L09C636B189, DUK-L09C636B186 and DUK-L09C636B360 update files on TWRP and gives me error code 9 "the target reported max"...
(all updates files i saved on internal memory and tried on SDCard)
2) Tried forcing update on sdcard/dload/update.app with the 3 button pressed also FAILED.
3) Extracted files from the update.app(BOOT.img, SYSTEM.img, RECOVERY.img) and use fastboot command to flash these files, Only SYSTEM.img gave me an error..
Please assist me in unbricking my Honor 8 pro..
Thank you!

Since you are able to boot into twrp, please try downloading all the 3 files of the latest firmware for your version and try using this to install stock oreo..
https://forum.xda-developers.com/honor-8-pro/how-to/restoring-dukfullotaromflasher-t3741223
Once done you can retry installing dotos
Kojooouuu said:
Hi all,
I have flashed dotOS custom ROM on my Honor 8 Pro. but i cant boot up after the installation, my phone keep restarting and cant boot up to dotOS..
Here is some of the details:
1)Firmware: Honor 8 pro DUK-L09C636B187
2) Bootloader: Unlocked
3) FRP Unlock
4) ADB terminal able to detect fastboot devices but not ADB devices
5) Able to go:
a)Fastboot mode
b) TWRP and eRecovery mode
c) EMUI mode
I have tried all these but failed:
1) Tried flashing DUK-L09C636B189, DUK-L09C636B186 and DUK-L09C636B360 update files on TWRP and gives me error code 9 "the target reported max"...
(all updates files i saved on internal memory and tried on SDCard)
2) Tried forcing update on sdcard/dload/update.app with the 3 button pressed also FAILED.
3) Extracted files from the update.app(BOOT.img, SYSTEM.img, RECOVERY.img) and use fastboot command to flash these files, Only SYSTEM.img gave me an error..
Please assist me in unbricking my Honor 8 pro..
Thank you!
Click to expand...
Click to collapse

Finally i am able to boot up to oreo!! Thank you
Now i have problem flashing to TWRP... i cant boot up to TWRP now.. i uses adb terminal to flash the TWRP 3.1.1.zip.
The error is remote partition length get error.

How unlock bootloader when the phone no start ??

Hi guys,
My phone has shut down and remains stuck in recovery mode or don't stop restarting
Of course I tried everything (wipe, erase, reboot ect ...)
My status :
usb no debugging
no internal storage acces
I tried adb sideload but it don't work...
PS C:\Android-ADB\tools> adb sideload OnePlus5TOxygen_43_OTA_034_all_1804201221_6d7a5834eb364dc6.zip
error: protocol fault (no status)
I tried TOOL ALL IN ONE (https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711)
but my bootloader is lock...
Someone has idea ??:crying::crying:

No idea ?

Have you tried to format data in recovery. " Not wipe, FORMAT." I had this happen a few times and a format fixed it.

https://youtu.be/PpLvmID1wdI
Try this

Device on Stock Recovery right?

Format already done...
Unbrick d'ont work : connect failed...
Device on recovery mode

Can't flash global rom

So, I have a Redmi Note 8 Pro with a Chinese ROM and I'm trying to flash a global ROM, obviously.
I unlocked the device - it worked fine. I used Miflash to flash the global ROM in fastboot. The process was successful - at least that's what the utility reported.
Now the device only boots into recovery - I can't even boot it into fastboot, let alone the system. In recoery, Mi PC Suit does not see it...
What can I do?
Update:
Redmi Recovery says "This MIUI version can't be installed on this device"
Update 2:
No matter what I do I can't get it into fastboot....

moshepupkin said:
"l.....
Update 2:
No matter what I do I can't get it into fastboot....
Click to expand...
Click to collapse
While in recovery, connect to your PC and run "adb reboot bootloader"
Or just get the proper ROM for your phone and flash through recovery via adb sideload or pushing it to your sdcard and flashing it through recovery

I tried tons of ROMs via adb recovery, but nothing works - I get either of the two following error messages:
ERROR: This rom cannot be installed, server code -> 2001, server message -> It's not allowed to upgrade to unofficial ROM package.
ERROR: This rom cannot be installed, server code -> 2009, server message -> Couldn't verify. Looks like current ROM's network carrier type is different from that in the Recovery package. Please download the correct ROM from MIUI forum.

adb reboot booloader got me into fastboot, but now it says "not allowed in locked state"...I did unlocked it...what the heck!?

OK, I figured out what went wrong - I accidentally flashed EE ROM, and now:
1. The phone doesn't boot with that ROM
2. I can't flash any other ROM, other than EE
Anything I can do?

In recovery I get the following error message" This MIUI version can't be installed on this device"

It appears that I accidently locked it back (that's the default in MiFlash). Anything I can do ow?

OK. I figured it out. Sorry for spamming. For the record:
1. I used adb to reboot into bootloader, as suggested
2. I used Mi unlock to unlock it again - strangely enough, this time I got it unlocked immediately, without waiting
3. I flashed the ROM with adb
Now everything works.

Xiaomi A2 lite : unable to flash a recovery

Hi, I want to move to a custom ROM on my A2 Lite. But before anything else, I need to backup my phone.
1st step : TWRP recovery.
On the PC, ADB driver is installed. Phone powered and connected, I have no problem to send ADB command to phone. "adb reboot bootloader" for example.
But once the phone is in fastboot (logo on screen), it is not recognized by PC (no driver) and I can"t send Fastboot command.
Any hint ?
Thanks.

Ok, I found a solution.
Downloading Google USB Driver but installation procedure is wrong, I should FORCE it and manually assigne the driver "Android Device / Bootloader" to be able to connect in Fastboot mode.
fastboot oem unlock
-> Reboot with the warning message but wipe all data. It's the only I found to unlock the bootloader :/
fastboot oem edl
-> Not the solution to flash the new ROM
fastboot boot twrp*.img
-> Way better to get the recovery flashed

Question [Solved] Help can boot in fastboot only

Hello i've got a Poco F3 with unlocked bootloader custom rom and recovery
yesterday i decided to install latest twrp on my poco f3 and after proceeding with zip installation trough twrp udate,phone cannot boot except fastboot,
after that
when launching twrp trough fastboot and trying to install any rom or update.zip i keep getting errors like
"failed to mount system_root" (no such file or directory)
"failed to mount product" (no such file or directory)
"failed to mount vendor" (no such file or directory)
triyed miflash tool but keep getting timeout error
even when connecting power charger phone boots in fastboot and not in battery logo

How to remove unlock mi account in Redmond 9A mobile please help me

lorezz said:
Hello i've got a Poco F3 with unlocked bootloader custom rom and recovery
yesterday i decided to install latest twrp on my poco f3 and after proceeding with zip installation trough twrp udate,phone cannot boot except fastboot,
after that
when launching twrp trough fastboot and trying to install any rom or update.zip i keep getting errors like
"failed to mount system_root" (no such file or directory)
"failed to mount product" (no such file or directory)
"failed to mount vendor" (no such file or directory)
triyed miflash tool but keep getting timeout error
even when connecting power charger phone boots in fastboot and not in battery logo
Click to expand...
Click to collapse
it seem your partition is encrypted.
try re flash the stock firmware first.
then, you could try flash the custom recovery again.
or u could study the stpe here, though it done on redmi 6A:
Fix HardBrick Redmi 6A (no recovery and no fastboot, only black screen)Fix without need Authotization stuff
----------------------------------------------------------------------- Finally I could fix my redmi 6A after suffering hardbrick. I couldnot enter to recovery neither to fastboot mode. My redmi 6A just give me a black screen with vibration on...
forum.xda-developers.com

Gamari said:
How to remove unlock mi account in Redmond 9A mobile please help me
Click to expand...
Click to collapse
try these:
Download Mi Account Unlock Tool | How to Use Unlock Tool
Download Mi Account Tool for free. You will get here the latest version to Bypass Mi Account. Get Easy way to Remove Mi Cloud Verification using this Tool.
xiaomibuzz.com
or
https://forum.unlocktool.net/threads/xiaomi-redmi-note-10-micloud-frp-bypass-done-by-unlock-tool.5324/

had the same problem yesterday, i downloaded the stock rom than i used fastboot boot twrp.img (didn't work for the first time) thn i tried fastboot boot orangefox.img (didn't even work for the first time) but after a few reboots and un/on pluging suddenly it wokred and booted twrp than i wiped everything and flased the stock now everything is fine.

made some progress and was able to flash a custom xiaomi eu rom trough fastboot commands and so phone boots to miui perfectly.....
a problem that remains is when i boot twrp from fastboot whit "fastboot boot recovery.img" command,is that twrp shows 0mb internal memory

do you habe a/b virtual partition? or perhaps you should mount that partition

lorezz said:
made some progress and was able to flash a custom xiaomi eu rom trough fastboot commands and so phone boots to miui perfectly.....
a problem that remains is when i boot twrp from fastboot whit "fastboot boot recovery.img" command,is that twrp shows 0mb internal memory
Click to expand...
Click to collapse
try to mount the target partition
if u couldnot mount it, then it might be encrypted
in my case to this issue:
-go into twrp
-wipe the user data partition
-wipe dalvic, cache, system, internal
-then, flash the custom rom
-reboot
hope that work for u too.