Develop Bugs

Huge problem

Hey,
I am running the exodus rom on my oneplus 3 and after todays update I got a huge problem. My screen fails to wake up, the phone works normal I think but the screen is just black..
How do I solve a problem like this?
I have tried turning it on and off again, it did not work

Fast And Pro said:
Hey,
I am running the exodus rom on my oneplus 3 and after todays update I got a huge problem. My screen fails to wake up, the phone works normal I think but the screen is just black..
How do I solve a problem like this?
I have tried turning it on and off again, it did not work
Click to expand...
Click to collapse
dirty flash?
may be clean flash will help

JumboMan said:
dirty flash?
may be clean flash will help
Click to expand...
Click to collapse
Idk what happend
but the screen works again but my phone is now bricked and the usual guides to unbrick do not work.
This is the status of my 1+3
Bootloader: unlocked and I can boot in the bootloader
my device is recognized by my pc
I cannot enter TWRP and I cant flash TWRP.
When I try to flash it CMD says that its flashed but I still cant boot in twrp, I get a random screen with md5 checksum and some fails.
Can someone help me?

Fast And Pro said:
Idk what happend
but the screen works again but my phone is now bricked and the usual guides to unbrick do not work.
This is the status of my 1+3
Bootloader: unlocked and I can boot in the bootloader
my device is recognized by my pc
I cannot enter TWRP and I cant flash TWRP.
When I try to flash it CMD says that its flashed but I still cant boot in twrp, I get a random screen with md5 checksum and some fails.
Can someone help me?
Click to expand...
Click to collapse
I don't have answer for question.
it looks like you have some serious problem with your phone.
may be some experienced user will help you.
I think you should approach Naman bhalla as he made guide to unbrick so he may know in detail

JumboMan said:
I don't have answer for question.
it looks like you have some serious problem with your phone.
may be some experienced user will help you.
I think you should approach Naman bhalla as he made guide to unbrick so he may know in detail
Click to expand...
Click to collapse
I found a fix on the forum and this explained what my problem was
On the screen when the phone failed to md5 checksum, you've got several partition failed right? in red text.
- download this : https://www.androidfilehost.com/?fid=24591000424942573
and then extract.
- download platform tools attached below. extract in the same folder with first file you've downloaded.
- Boot your phone to fastboot mode, plug your usb, make sure adb and fastboot driver are installed.
- on the folder, hold shift and right click, click open command here
- type fastboot devices
- make sure your serial number appear.
- now flash the img of the missing file according to the partition in red text on your ms5 checksum failed one by one.
- e.g. "fastboot flash boot_aging boot_aging.img.
- make sure you flash all the missing partition.
- type fastboot reboot.
this will boot you to oos 3.1.2.
unfortunately I couldn't extract the newest oos dat. data. but you could always take the OTA
goodluck mate. sorry for my english

Fast And Pro said:
I found a fix on the forum and this explained what my problem was
On the screen when the phone failed to md5 checksum, you've got several partition failed right? in red text.
- download this : https://www.androidfilehost.com/?fid=24591000424942573
and then extract.
- download platform tools attached below. extract in the same folder with first file you've downloaded.
- Boot your phone to fastboot mode, plug your usb, make sure adb and fastboot driver are installed.
- on the folder, hold shift and right click, click open command here
- type fastboot devices
- make sure your serial number appear.
- now flash the img of the missing file according to the partition in red text on your ms5 checksum failed one by one.
- e.g. "fastboot flash boot_aging boot_aging.img.
- make sure you flash all the missing partition.
- type fastboot reboot.
this will boot you to oos 3.1.2.
unfortunately I couldn't extract the newest oos dat. data. but you could always take the OTA
goodluck mate. sorry for my english
Click to expand...
Click to collapse
Its good.
Self help is best help

Lenovo K8 Note Red State Bootloop After Flashing Custom Recovery

Hello Guys,
The issue is that i wanted to root my lenovo k8 note so follow this link "https://forum.xda-developers.com/android/development/tutorials-how-to-root-lenovo-k8-note-t3685502", Everything works file but in last rooting step no. 9
9. If you see internal storage 0mb Then GoTo Wipe and FORMAT DATA once & reboot to recovery
but in my device there has memory 59999mb so i ignored and reboot using twrp but it says no OS installed
and shows orange state, then i format phone using twrp but nothing happens again orange state and no os installed.
then i found another article with same issue "https://forum.xda-developers.com/android/help/lenovo-k8-note-stuck-boot-logo-flashing-t3751324/post75974342#post75974342" and found this
The bootlogo issue.
Hey! I read your post regarding your k8 note being stuck at the bootlogo.
Consider that you can still use TWRP, boot into it.
Then go ahead and download the SuperSU zip on your PC/laptop and connect your phone with a USB. You might be able to see the SD card folders on your PC, then you can just copy and paste it to the internal sd and flash it. You'll be good to go. If that doesn't work, in the TWRP Mode, go to advanced and select ADB sideload. You can now flash using ADB sideload.
Search for tutorials on ADB sideload. It's easy and that should work.
Click to expand...
Click to collapse
solution over there and flash supersu but nothing happens.
After so many try i locked oem bootloader in fastboot using command "fastboot oem lock", after this my lenovo k8 note show Red State.
Now i am not able to do anythig please help me out.
Basically my device is stuck at the bootloop with the
Red State
=> "Your Device has fail to pass verification and may not work properly
your device will boot in 10 sec trusted
Your device will boot in 5 seconds"
definitely I must have screwed up something.
Please help me to boot my Lenovo K8 note in normal mode.
Thanks

beingfhd said:
Hello Guys,
The issue is that i wanted to root my lenovo k8 note so follow this link "https://forum.xda-developers.com/android/development/tutorials-how-to-root-lenovo-k8-note-t3685502", Everything works file but in last rooting step no. 9
9. If you see internal storage 0mb Then GoTo Wipe and FORMAT DATA once & reboot to recovery
but in my device there has memory 59999mb so i ignored and reboot using twrp but it says no OS installed
and shows orange state, then i format phone using twrp but nothing happens again orange state and no os installed.
then i found another article with same issue "https://forum.xda-developers.com/an...-flashing-t3751324/post75974342#post75974342" and found this solution over there and flash supersu but nothing happens.
After so many try i locked oem bootloader in fastboot using command "fastboot oem lock", after this my lenovo k8 note show Red State.
Now i am not able to do anythig please help me out.
Basically my device is stuck at the bootloop with the
Red State
=> "Your Device has fail to pass verification and may not work properly
your device will boot in 10 sec trusted
Your device will boot in 5 seconds"
definitely I must have screwed up something.
Please help me to boot my Lenovo K8 note in normal mode.
Thanks
Click to expand...
Click to collapse
Are you okay with losing your data on your phone? If yes then go ahead and flash stock ROM with sp flash tool. And about your problem, I guess you wiped the /system partition as well that's why it was showing no os installed.
Another thing is that if you install twrp Do not boot up your phone, boot up into twrp by pressing volume up and power button at the same time you'll need to flash magisk or supersu so that twrp can modify partition correctly.

Thanks
Anas Rahman said:
Are you okay with losing your data on your phone? If yes then go ahead and flash stock ROM with sp flash tool. And about your problem, I guess you wiped the /system partition as well that's why it was showing no os installed.
Another thing is that if you install twrp Do not boot up your phone, boot up into twrp by pressing volume up and power button at the same time you'll need to flash magisk or supersu so that twrp can modify partition correctly.
Click to expand...
Click to collapse
Thanks for the reply but i recovered it using flash stock rom.
But i have another ques that can i flash twrp without oem unlock?

beingfhd said:
Thanks for the reply but i recovered it using flash stock rom.
But i have another ques that can i flash twrp without oem unlock?
Click to expand...
Click to collapse
No you can't

k8 note stuck on bootloop...??
need help.....my k8 note was running oreo....thn i downgraded to nougat...duo to bugs on oreo... thn i was facing more problems... so i decided to flash oreo again. ... i was trying to flash...but i was getting some brom error...so i thought it might be due to unlocked bootloader... so i tried to lock it.. and then try... and the system got deleted.... i cant even access fastboot... but device is detecting on sp flash tool... but getting the same error... help buddy... its urgent.. my device is not turning on... but the led is working....

DeepRBasak said:
need help.....my k8 note was running oreo....thn i downgraded to nougat...duo to bugs on oreo... thn i was facing more problems... so i decided to flash oreo again. ... i was trying to flash...but i was getting some brom error...so i thought it might be due to unlocked bootloader... so i tried to lock it.. and then try... and the system got deleted.... i cant even access fastboot... but device is detecting on sp flash tool... but getting the same error... help buddy... its urgent.. my device is not turning on... but the led is working....
Click to expand...
Click to collapse
This might be helpful https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839

thank u somuch am also mobile sevice man it help full for me
Anas Rahman said:
Are you okay with losing your data on your phone? If yes then go ahead and flash stock ROM with sp flash tool. And about your problem, I guess you wiped the /system partition as well that's why it was showing no os installed.
Another thing is that if you install twrp Do not boot up your phone, boot up into twrp by pressing volume up and power button at the same time you'll need to flash magisk or supersu so that twrp can modify partition correctly.
Click to expand...
Click to collapse

I have the same problem. please help us!

HARDROCK2614 said:
I have the same problem. please help us!
Click to expand...
Click to collapse
What problem do you have, please describe

I have lost all my mind and need serious help.
Recently, the march update came. i forgot that rooted phone should not be updated by the OTA update. And i did. As a result i got stuck in a bootloop. Then I had to use the oreo ROM from this forum and flashed it using SP Flash tool. It was a successfull flash. Then I used Maui META to write the IMEI for both sim. That was successfull too(Wifi and bluetooth addresses were working by themselves and i didnt write the serial number of the phone).
After working nicely for three days, i was using Whatsapp and a friend of mine sent me a .pptx file (powerpoint presentation). I opened it using WPS office app. I opened it multiple times in morning with no problems. But in the afternoon at about 2.53 PM while i was in my car, i was unable to open the file. The phone hanged. It heated up. To get out of the hang, i restarted the phone using the power button. IT DID NOT START. All it showed was the lenovo logo screen. And after doing more restarts, the phone went completely blank.
Now i cannot start it, or charge it. So i thought of flashing it again. But when i connect it to my PC, it keeps CONNECTING and DISCONNECTING. what i saw in the device manager was that the driver keeps changing very fast betwee MTK USB PORT and PRELOADER.
I found the solution to be updating the drivers manually. I did. Now the driver shows only DA USB VCOM and when it changes, it goes invisible in the PC and then appears back. Now when i start flashing, the first red progress bar appears as: Download DA 100%. and the flash hangs. After some time, this error will popup: ERROR: STATUS_UNKNOWN_STORAGE_TYPE (0xC0040009)
Please someone help me.

custom619 said:
Recently, the march update came. i forgot that rooted phone should not be updated by the OTA update. And i did. As a result i got stuck in a bootloop. Then I had to use the oreo ROM from this forum and flashed it using SP Flash tool. It was a successfull flash. Then I used Maui META to write the IMEI for both sim. That was successfull too(Wifi and bluetooth addresses were working by themselves and i didnt write the serial number of the phone).
After working nicely for three days, i was using Whatsapp and a friend of mine sent me a .pptx file (powerpoint presentation). I opened it using WPS office app. I opened it multiple times in morning with no problems. But in the afternoon at about 2.53 PM while i was in my car, i was unable to open the file. The phone hanged. It heated up. To get out of the hang, i restarted the phone using the power button. IT DID NOT START. All it showed was the lenovo logo screen. And after doing more restarts, the phone went completely blank.
Now i cannot start it, or charge it. So i thought of flashing it again. But when i connect it to my PC, it keeps CONNECTING and DISCONNECTING. what i saw in the device manager was that the driver keeps changing very fast betwee MTK USB PORT and PRELOADER.
I found the solution to be updating the drivers manually. I did. Now the driver shows only DA USB VCOM and when it changes, it goes invisible in the PC and then appears back. Now when i start flashing, the first red progress bar appears as: Download DA 100%. and the flash hangs. After some time, this error will popup: ERROR: STATUS_UNKNOWN_STORAGE_TYPE (0xC0040009)
Please someone help me.
Click to expand...
Click to collapse
I couldn't find more about the problem online, can you please upload a screenshot of the error. Try using the latest version of SP Flash Tool and see if the problem persists

I have lost all my mind and need serious help.
here are the screenshots. Note that the battery is in the phone always because i am unable to open the back cover. During the flashing process, i did not press the vol - button.
https://ibb.co/sq8knnj
https://ibb.co/VjqKQm3
https://ibb.co/4VkVPjs
https://ibb.co/cw2BzLC
https://ibb.co/kcjjJ74
Now in the following screenshots, i kept the vol - button pressed down. Note that the driver is stuck at preloader and not DA. Also the first bar is yellow color in both these cases. However, in the above situation, multiple files were flashed. But in this below situation, only this so called "flash" was done; that too unsucessful in the end.
https://ibb.co/1QKtsCb
https://ibb.co/Ssj58Zd

custom619 said:
here are the screenshots. Note that the battery is in the phone always because i am unable to open the back cover. During the flashing process, i did not press the vol - button.
https://ibb.co/sq8knnj
https://ibb.co/VjqKQm3
https://ibb.co/4VkVPjs
https://ibb.co/cw2BzLC
https://ibb.co/kcjjJ74
Now in the following screenshots, i kept the vol - button pressed down. Note that the driver is stuck at preloader and not DA. Also the first bar is yellow color in both these cases. However, in the above situation, multiple files were flashed. But in this below situation, only this so called "flash" was done; that too unsucessful in the end.
https://ibb.co/1QKtsCb
https://ibb.co/Ssj58Zd
Click to expand...
Click to collapse
The problem may be with your drivers, i see you have Preloader drivers only.
Follow this guide for installing drivers - https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033

Anas Rahman said:
The problem may be with your drivers, i see you have Preloader drivers only.
Follow this guide for installing drivers - https://forum.xda-developers.com/elephone-m2/help/windows-10-mtk-vcom-usb-drivers-32-64-t3267033
Click to expand...
Click to collapse
So i did as you said brother. I don' t know how but something happened. The phone, after a long time actually displayed up. It showed the LENOVO logo and down in the corner two things came in written :
>device unlocked
>Tool DL image Fail
I googled it up and found that it requires to flash the phone with the DA DL option ticked. I did that but it does not flash. The error is same as follows:
https://ibb.co/Ssj58Zd
Can you please guide me in the flashing process? I think the mistake is very small but i don't know where i am missing.

I have lost all my mind and need serious help.
custom619 said:
So i did as you said brother. I don' t know how but something happened. The phone, after a long time actually displayed up. It showed the LENOVO logo and down in the corner two things came in written :
>device unlocked
>Tool DL image Fail
I googled it up and found that it requires to flash the phone with the DA DL option ticked. I did that but it does not flash. The error is same as follows:
https://ibb.co/Ssj58Zd
Can you please guide me in the flashing process? I think the mistake is very small but i don't know where i am missing.
Click to expand...
Click to collapse
Okay so what i figured out is that in this state: (battery plugged in, no notification LED response, no response on power or volume buttons) the driver you require is MTK USB PORT.
I updated to this driver manually, and guess what? the phone actually flashed. But three files remained and the process hanged. (system, cache and userdata)
Now i get the errors:
>device unlocked
>Tool DL image Fail
and sometimes: >device otp failed
I am trying to flash the rest three files individually. Lets see what happens.

custom619 said:
Okay so what i figured out is that in this state: (battery plugged in, no notification LED response, no response on power or volume buttons) the driver you require is MTK USB PORT.
I updated to this driver manually, and guess what? the phone actually flashed. But three files remained and the process hanged. (system, cache and userdata)
Now i get the errors:
>device unlocked
>Tool DL image Fail
and sometimes: >device otp failed
I am trying to flash the rest three files individually. Lets see what happens.
Click to expand...
Click to collapse
Try flashing wihtout these three files, then boot to fastboot mode by pressing POWER+VOL UP and choose fastboot mode then flash these three files with fastboot commamds

Anas Rahman said:
Try flashing wihtout these three files, then boot to fastboot mode by pressing POWER+VOL UP and choose fastboot mode then flash these three files with fastboot commamds
Click to expand...
Click to collapse
I.AM.DUMBFOUNDED.
During flashing this error occurred:
(yellow bar in SPFlash tool)
[recovery] Download Flash 100%
ERROR: STATUS_MMC_ERR (0xC0040030)
[HINT]:

custom619 said:
I.AM.DUMBFOUNDED.
During flashing this error occurred:
(yellow bar in SPFlash tool)
[recovery] Download Flash 100%
ERROR: STATUS_MMC_ERR (0xC0040030)
[HINT]:
Click to expand...
Click to collapse
Couldn't find much about the error, give this a try
https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839
ALSO, in the last few screenshots you're using firmware upgrade option please choose downlaod only.
Join the Telegram group more people can help there - -
Join «Lenovo XT1902-1/2/3 (K8 Series) Official Chat Group» on Telegram: https://t.me/K8Official

Anas Rahman said:
Couldn't find much about the error, give this a try
https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839
ALSO, in the last few screenshots you're using firmware upgrade option please choose downlaod only.
Join the Telegram group more people can help there - -
Join «Lenovo XT1902-1/2/3 (K8 Series) Official Chat Group» on Telegram: https://t.me/K8Official
Click to expand...
Click to collapse
I Already tried this thread you suggested. No outcome.

Anas Rahman said:
Couldn't find much about the error, give this a try
https://forum.xda-developers.com/k8-note/how-to/lenovo-k8-note-xt1902-3-fix-dead-hard-t3791839
ALSO, in the last few screenshots you're using firmware upgrade option please choose downlaod only.
Join the Telegram group more people can help there - -
Join «Lenovo XT1902-1/2/3 (K8 Series) Official Chat Group» on Telegram: https://t.me/K8Official
Click to expand...
Click to collapse
This group is possibly dead. No one has responded till today...

Could somebody help me?downgrade emui5

:crying:Last night, I installed the Android 8 update package on the forum.
Halfway through, an error is displayed and then exit.
I tried eRecovery and Hisuite, but all failed.
I tried it and found that the original recovery partition became recovery_ramdisk. It looks like the partition has changed.
What can I do to be able to return to emui5?
I have imagined "fastboot flashall", but I do not know how? Forgive my lame English

zzkeier said:
:crying:Last night, I installed the Android 8 update package on the forum.
Halfway through, an error is displayed and then exit.
I tried eRecovery and Hisuite, but all failed.
I tried it and found that the original recovery partition became recovery_ramdisk. It looks like the partition has changed.
What can I do to be able to return to emui5?
I have imagined "fastboot flashall", but I do not know how? Forgive my lame English
Click to expand...
Click to collapse
recovery_ramdisk. is the new name of recovery partition. EMUI8/Oreo flashing has started means the partitions etc have changed already so right now you can't go back to EMUI 5 as rollback images are not available yet. You can try to flash again properly with proper download for your specific model. I guess you are missing some echo commands.

thank you very much
SVR said:
recovery_ramdisk. is the new name of recovery partition. EMUI8/Oreo flashing has started means the partitions etc have changed already so right now you can't go back to EMUI 5 as rollback images are not available yet. You can try to flash again properly with proper download for your specific model. I guess you are missing some echo commands.
Click to expand...
Click to collapse
I extract the update.app(oreo) file and then i flash the system.img. Now it works..Thank you

hey how did you did that?
zzkeier said:
I extract the update.app(oreo) file and then i flash the system.img. Now it works..Thank you
Click to expand...
Click to collapse
I also have similar problem I installed different model rom using firmware finder and now I can only use my phone when I unlock bootloader when I lock it it will not open directly go into the erecovery and nothing is working I tried everything twrp,erecovery,force updating nothing worked all failed.please help

shrey2204 said:
I also have similar problem I installed different model rom using firmware finder and now I can only use my phone when I unlock bootloader when I lock it it will not open directly go into the erecovery and nothing is working I tried everything twrp,erecovery,force updating nothing worked all failed.please help
Click to expand...
Click to collapse
well,I flash the system.img by fastboot,and then make a factory reset.Bootloader unlock needed.

i have the same problem
I tried to upgrade phone to Oreo after unlock, in update progress it got error and restart phone! Now it shows:
Code:
Error Mode
Attention!
Please update system again
Error!
Func No : 11 (recovery image)
Error No : 2 ( load failed )
I just have access to fastboot
i did flash system.img and tried install twrp on ramdisk recovery. but always same
:crying::crying::crying::crying:

ERROR MODE Attention! Please update system again.

Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!

Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system

mrmazak said:
Doing the update second time is fine, and best way to restore full stock. But you needed to use Oreo version of no-check recovery and the Oreo partition to flash it to.
So if still able to get into twrp, can try with correct no-check recovery and correct partition it's flashed to.
Also
With multi tool , make sure you put check mark on emui 8. Up in upper right corner. That way it uses Oreo partition names and file not nougat.
The partition length over message usually means nougat file or partition name used on Oreo system
Click to expand...
Click to collapse
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore

Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
I give my phone to a friend to work on it. If he can't fix it I try new multi tools version to flash phone.

Mohammadreza76646 said:
Thank you for your answer.
But I try to extract update.app (oreo version) but its failed! huawei update extractor cant open it and 7zip cant extract it with (unexpected error...)!
And unfortunately my TWRP dos not work anymore
Click to expand...
Click to collapse
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk

Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!!
Click to expand...
Click to collapse
I ever have similiar problem with you dude, but it's solved now, if you always stuck on " its OK but when my phone want to start its stuck on google page "just a sec...", its call google accont verification, i'll by bypass with this script, save as to .bat and put on adb folder
adb devices
adb shell content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1
adb shell am start -n com.google.android.gsf.login/
adb shell am start -n com.google.android.gsf.login.LoginActivity
pause
in fastboot type:
fastboot -w
after all it's works to me to bypass google account verification
and if now your problem is
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
i solve with re-flash system from this
https://androidfilehost.com/?fid=673956719939830152
fastboot flash system system.img
and doing TWRP Flashing
https://forum.xda-developers.com/devdb/project/?id=25826#downloads
fastboot flash recovery_ramdisk complete_twrp_ramdisk.img
and voila my problem solved..

mrmazak said:
On the extractor app. On options tab uncheck the verify header option, it should extract then.
Then perhaps first do these three partitions.
Kernel.img
Ramdisk.img
Then
twrp_ramdisk or for stock use recovery_ramdisk
Click to expand...
Click to collapse
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (

Mohammadreza76646 said:
Hello again dude.
Finally I flashed my phone and I got the system installed.
But now my phones IMEI is lost. and I cant put sim on it!!!
what should I do now???
FRP is locked! (
Click to expand...
Click to collapse
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595

mrmazak said:
So now is locked frp. Does phone have twrp or stock now.?
I think when you tried to install the oreo update for second time, you followed same tutorial as the first time. And that made you problem worse. The tutorial has you flash no-check recovery to 2 partition by block number. 22 & 29. On nougat that is "recovery" and "recovery2". On Oreo partion table it is "reserved2" & "erecovery_vendor"
I don't know how to fix imei. Have hope that if to ucan have a full ota install , maybe can be fixed.
There is available a "service rom" (used to fix most all problem) for Europe region with l21.
I can share link to site with service rom if you want , but I have not used it myself so not gonna be much help with it.
Link is to rusian language page. Google should translate for you.
https://4pda.ru/forum/index.php?showtopic=879524&view=findpost&p=73818595
Click to expand...
Click to collapse
It have stock recovery.

Mohammadreza76646 said:
It have stock recovery.
Click to expand...
Click to collapse
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)

mrmazak said:
in summery. because i have been going back and forth in multiple different groups, multiple problem, i cant remember it all.
you have broken system, from failed root attempt, followed by failed update.
device condition is as follows.
--system not booting
--stock recovery loads
--fastboot/bootloader loads, but is in frp lock status
options are limited, at best.
I think "dload" method with service rom is best.
other option is maybe paid service like dc-unlock. But I can recall some note on there service about frp-unlock, that can only be used on device with working system. (of course if was working system, wouldn't need dc-unlock)
Click to expand...
Click to collapse
No. System boot successfully!
I will send you screenshot:

Mohammadreza76646 said:
No. System boot successfully!
I will send you screenshot:
Click to expand...
Click to collapse
here you are

Mohammadreza76646 said:
here you are
Click to expand...
Click to collapse
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.

mrmazak said:
what about the "about phone" screen
what does it show for version?
If is all stock you should be able to go into deveolper options and enable "oem unlock". If it is greyed out and cannot switch it. Try First to remove google account (all accounts ). and reboot. See if can change then. If not, try Second to do "fastboot oem relock [enter your bootloader code here]
after relock and rebooted oem switch should be enabled again.
****RELOCK IS ONLY ADVISED IF 100% STOCK ROM****
otherwise relock could make more trouble.
Still not sure how to get IMEI back even if unlocked frp though.
**And please stop posting in other threads , the same problem , because you are getting help here.
your post in recovery thread is off topic to that thread and just makes the forum harder to maintain.
Click to expand...
Click to collapse
Thanks )
I'm so sorry for my posts, it's because I don't have a stable connection and I can't see notification of my thread.
I gave my phone to friend an he fix IMEI (I don't know how)
But OEM is steel lock.
I think he did it with using special box.

Mohammadreza76646 said:
Hi
I have a problem with my Honor 7X L21.
Because online update dose not work for this model I decided to updated my smartphone offline.
I downloaded Oreo update file
Unlock my phone
install twrp
update phone
every thing is going well until here
then I decided to root my phone but I saw there is no twrp on my phone
I search and I found a thread here that show how install twrp with adb use recovery ramdisk.
I install twrp on recovery ramdisk and try to root my phone. its OK but when my phone want to start its stuck on google page "just a sec..."
I boot my device on twrp and I did factory reset but the problem was still exist.
then I decided to flash update again.
I copy update file on SD card and wright code on twrp
but at the end when I reboot the recovery, twrp except stock recovery came up and my stock recovery was gone.
I reboot the system but Its loop on this page that says:
ERROR MODE
Attention!
Please update system again.
Error!
Func NO : 11 (recovery image)
Error NO : 2 (load failed!)
Please help me!!!
I try to install stock recovery and twrp with adb and huawei multi tools but it didn't work.
it shows:
"FAILED (remote: partition length get error)"
I try to unbrick my phone too but it shows same message that "FAILED (remote: partition length get error)"
Helllllp lpeaeaeaeaeaseeee!!![/QUOTE
Are u able.to boot into twrp ?
Click to expand...
Click to collapse

Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?

IonDEfeso said:
Hello I have a Huawei Mate-SE (with bootloader unlocked and rooted with magisk v16). I have been using the android custom rom RRO v6 (RR-O-v6.0.0-20180401-bnd-OpenKirin) for around a month now. I got this exact same problem about the White Screen saying "ERROR MODE Attention...." since I updated the Magisk to latest version (from the installed application) and rebooted my phone. SInce I rebooted I am getting that same error which makes the phone loops into it for a few times and then it loads the Huawei eRecovery that offers me some options that I am not sure what would do to my phone.
I have been trying to connect to adb tools/fastboot but it doesn't detect the phone and im pretty sure I have the device drivers installed on my computer since nothing have changed in my pc for a month now since I flashed RRO on it.
Is there any other mode besides recovery that would allow me to connect adb/fastboot to it? Or does anyone knows how should I proceed?
Click to expand...
Click to collapse
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)

mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.

mrmazak said:
I have seen where the magisk update screwed up and patches the kernel intead of the ramdisk.
Power off , long press power button.
Hold volume down and plug in USB from PC.
This should cause it to boot into fastboot mode.
Then flash the stock kernel. And the stock or first patched ramdisk. (From earlier root)
Click to expand...
Click to collapse
Do you know what the boot.img files name is after extraction?
I have extracted all 3 update zips and cannot find anything called boot.img
By the way, thank you.. After updating magisk I have been dealing with failed recovery and failed boot for over a week and this is the first reply anywhere that looks promising

IonDEfeso said:
Hi thank you I was able to finally detect the device now. I am unsure about the kernel is that the recovery.img or system.img files I downloaded (i saved every file i used when I installed the rom) or do I need to look for the kernel somewhere else? I do have the complete_twrp_ramdisk.img file though.
Edit, I did more research and found the stock kernel is withing the boot.img file which I dont have so I looked up for the official BND-L34 oreo update and im currently downloading to extract the stock boot.img from the update.zip and flash it. Since that download was going to take me a while anyway i tried flashing the twrp recovery file without success (didn't changed anything) so i guess I should follow the instructions you gave me by flashing the kernel first then the twrp recovery.
Click to expand...
Click to collapse
if you were on oreo. then there is not a boot.img, instaed there is seperate ramdisk.img and kernel.img.
i have all the files already extracted for oreo and a backup from nougat as well.
https://androidfilehost.com/?w=files&flid=265998
make sure you know what you are doing before flashing.
for example. on oreo the boot and recovery share one kernel image. SO if kernel is messed up you will not be able to boot "boot" or "recovery"

Bricked .. Help me !

Hello, i have bricked my phone after an hurupdate, i dont know why but the phone have suddenly turn off during twrp hurupdater process and now i can't turn on the phone, i can plug in my pc & he recognize him as "fastboot devices" but when i try to flash something or unbrick via multi tool nothing happen (FAILED (remote: Command not allowed))
I can't do anything now.. Please help me !

Albanheraibi said:
Hello, i have bricked my phone after an hurupdate, i dont know why but the phone have suddenly turn off during twrp hurupdater process and now i can't turn on the phone, i can plug in my pc & he recognize him as "fastboot devices" but when i try to flash something or unbrick via multi tool nothing happen (FAILED (remote: Command not allowed))
I can't do anything now.. Please help me !
Click to expand...
Click to collapse
Erecovery has started working for some people. you can try that

mrmazak said:
Erecovery has started working for some people. you can try that
Click to expand...
Click to collapse
Nope .. nothing work ..
Anyone know how to unbrick ? ..

I think i have flashed the wrong update, i have bndl21 & i have flashed the bndl22 or bndal10, my phone is dead ?

Albanheraibi said:
I think i have flashed the wrong update, i have bndl21 & i have flashed the bndl22 or bndal10, my phone is dead ?
Click to expand...
Click to collapse
Shouldn't be, at least not from that, not completely.
Was this the first condition, or an added problem?
I think best thing to try is the service ROM.
This one is BND-L21C432..
Service rom BND-L21C432
https://www.androidfilehost.com/?fid=11050483647474828964
1. Unzip download
2. copy the dload folder to root of sdcard
3. power on phone holding all three buttons
4. After phone finishes and reboots, unlock frp and bootloader, if needed
5. Use Huru or HWOTA to flash correct firmware for your model/ region.. If this is not the correct version for your honor 7x

Now with dc phoenix i have restore the fastboot and the erecovery, i can flash all i want but nothing happens, just boot loop at "your phone is not trusted" screen.
I was on catuva's rom before brick and now i have the catuva splashboot screen even after full firmware retore by dc phoenix.
When i try to flash in twrp i see lot of errors related to partition table (invalid argument cust, odm, sytsem etc) it seems the partition table have a problem..
The DLOAD can restore this ?

When i try to restore via dload it stuck at 5% and it says "software install failed!" ..
Someone Help me ?..

Albanheraibi said:
When i try to restore via dload it stuck at 5% and it says "software install failed!" ..
Someone Help me ?..
Click to expand...
Click to collapse
You got failed using the "service-rom" dload?
This one is Oreo I believe. There is a nougat one also.

mrmazak said:
You got failed using the "service-rom" dload?
This one is Oreo I believe. There is a nougat one also.
Click to expand...
Click to collapse
Yes stuck at 5%..
i have try to flash the Honor 7X-Elemental V1(8.X-GPU) and i get an error at the end of process >
mount: failed to mount
/dev/block/platform/hi_mci.0/by-name/system at /system: invalid argument
What i am supposed to do with this error ?

Albanheraibi said:
Yes stuck at 5%..
i have try to flash the Honor 7X-Elemental V1(8.X-GPU) and i get an error at the end of process >
mount: failed to mount
/dev/block/platform/hi_mci.0/by-name/system at /system: invalid argument
What i am supposed to do with this error ?
Click to expand...
Click to collapse
Says in the install guide for it, you must be running at newest security patch in order to install elemental.
Please focus on one thing. Getting phone to boot full stock first before trying other rom. You are going to hard brck your phon if you keep doing flashes when the stock fails to install

mrmazak said:
Says in the install guide for it, you must be running at newest security patch in order to install elemental.
Please focus on one thing. Getting phone to boot full stock first before trying other rom. You are going to hard brck your phon if you keep doing flashes when the stock fails to install
Click to expand...
Click to collapse
When i try to rollback emui5 via twrp with your guide i have this error :
write radio image...
check_write_data_to_partition,write data error update_huawei_pkg_from_ota_zip: update pakage from zip failed
E : unknown command [errno]
Updater process ended with ERROR : 9
Error installing zip file '/external_sd/HWOTA8/update.zip'
i remember that the phone has started to bootloop just after twrp flashed the wrong radio file..
This is the end ?

Albanheraibi said:
When i try to rollback emui5 via twrp with your guide i have this error :
write radio image...
check_write_data_to_partition,write data error update_huawei_pkg_from_ota_zip: update pakage from zip failed
E : unknown command [errno]
Updater process ended with ERROR : 9
Error installing zip file '/external_sd/HWOTA8/update.zip'
i remember that the phone has started to bootloop just after twrp flashed the wrong radio file..
This is the end ?
Click to expand...
Click to collapse
I am not understanding how you say you follow my guide, then post the error.
This error shows you are trying to install ota update with TWRP.
My guide sets you to install ota update file with a modified stock recovery (no-check).
If you are having trouble because of bad translation, please do not assume what you need to do and wait for proper help and translation

mrmazak said:
I am not understanding how you say you follow my guide, then post the error.
This error shows you are trying to install ota update with TWRP.
My guide sets you to install ota update file with a modified stock recovery (no-check).
If you are having trouble because of bad translation, please do not assume what you need to do and wait for proper help and translation
Click to expand...
Click to collapse
Ok after update with hurupdater via twrp (he flashed the correct radio.img file) the phone have income from death !
Thank you for trying to help me !