Database Info

(Q) "Huawei cust fail" error and the solution?

My device's rom is MT7-L09V100R001C00B133SP11, I tried to install B127 MT7-L09 West Europe rom but have error while installing the rom. The error is "huawei cust fail". I tried many roms (B120, B121, B126, B127) but no success and everytime the same error. But I can flash only its original rom MT7-L09V100R001C00B133SP11 without any problem. How to solve this problem? Help please.

Tried to flash after FLASHE of Rom, the Cust.img in flash mode?
fastboot flash cust cust.img
The Cust you can find here.
https://mega.co.nz/#!uQ4mFTjB!vcz0m0Ea4mUjkIQdQEgCtdnn3RkpxKK1sFDHbPSvWSA

Fooox1 said:
Tried to flash after FLASHE of Rom, the Cust.img in flash mode?
fastboot flash cust cust.img
The Cust you can find here.
https://mega.co.nz/#!uQ4mFTjB!vcz0m0Ea4mUjkIQdQEgCtdnn3RkpxKK1sFDHbPSvWSA
Click to expand...
Click to collapse
No problem flashing cust. When I put the rom dload and to install full rom it gives error. I could not flash any rom from dload except b133.

Then extract the desired Rome and boot.img, recovery.img, system.img and cust.img manual flash.
command:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
Then it should start and you can do that Rome again completely FLASHE.

Fooox1 said:
Then extract the desired Rome and boot.img, recovery.img, system.img and cust.img manual flash.
command:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
Then it should start and you can do that Rome again completely FLASHE.
Click to expand...
Click to collapse
I did everything you write. Everytime no success. I think there was a regional lock on our phones. I think I must flash more img files to unlock regional lock.

Of course, the boot loader mechanism to be open. More imgs can not flash itself. All other get error messages.
Open bootloader, flash Custom Rom would be an alternative.

Fooox1 said:
Of course, the boot loader mechanism to be open. More imgs can not flash itself. All other get error messages.
Open bootloader, flash Custom Rom would be an alternative.
Click to expand...
Click to collapse
My bootloader is unlocked. Which custom rom can I flash.

Try it so that is close to stock and deodexd.
http://forum.xda-developers.com/mate-7/orig-development/custom-rom-kangvip-rom-b122sp06v1-1-t3022436

Fooox1 said:
Try it so that is close to stock and deodexd.
http://forum.xda-developers.com/mate-7/orig-development/custom-rom-kangvip-rom-b122sp06v1-1-t3022436
Click to expand...
Click to collapse
But it says "In addition, you should the B127 MT7-L09 Western Europe or the B122SP06 installed, otherwise it will get to the bootloop." and my rom is not b127 or b126. My rom is b133. Will it bootloop.

b127 is the minimum requirement, you lie already higher. If so beware.

Fooox1 said:
b127 is the minimum requirement, you lie already higher. If so beware.
Click to expand...
Click to collapse
Can you explain step by step what will I do.

I'm in cust fail error drama like you, i have TL 10 international stuck in b119 original firmware but i got root with alternative method whitout unlock boot loader.
Cust fail appears even if i simply Hard reset my phone the root remains
No ROM upgrade via ota non ROM can be flashed via SD card method.
My questions:
Can i try to flash original firmware via fast boot without unlock boot loader first?
I unpacked update.app with extractor and got many file : cust boot recovery modem etc
Which One should i flash and in which order?
Thnks in advance forma help

Without unlocked bootloader you can not flash imgs. If you have unpack the zip you a dload folder that is on the SD and you can flash.
---------- Post added at 01:21 PM ---------- Previous post was at 01:17 PM ----------
isaekrem said:
Can you explain step by step what will I do.
Click to expand...
Click to collapse
You can read it in the manual.
- Flash KangVIP recovery
- Zip to the SD
- Factory reset in recovery
- Flash zip
Done.

Fooox1 said:
Without unlocked bootloader you can not flash imgs. If you have unpack the zip you a dload folder that is on the SD and you can flash.
---------- Post added at 01:21 PM ---------- Previous post was at 01:17 PM ----------
You can read it in the manual.
- Flash KangVIP recovery
- Zip to the SD
- Factory reset in recovery
- Flash zip
Done.
Click to expand...
Click to collapse
Thanks. Now I am on kangvip rom.

can someone upload they cust folder for me?

Install b112 using adb

Good Day
No one seems able to cure my restarting X2 problem
I have mininal ADB and fastboot installed
I need to try and install B112 using adb
How do I use adb to flash B112 to my x2 ? (step by step please)
Please please there must be someone out there can help
Regards
Mark
[founder of xda Huawei MediaPad X2 forum]

elio321 said:
Good Day
No one seems able to cure my restarting X2 problem
I have mininal ADB and fastboot installed
I need to try and install B112 using adb
How do I use adb to flash B112 to my x2 ? (step by step please)
Please please there must be someone out there can help
Regards
Mark
[founder of xda Huawei MediaPad X2 forum]
Click to expand...
Click to collapse
Flash via ADB all the img files fromB112 without Stock Recovery
Flash the Universal Cust B112 in TWRP
Flash Stock Recovery from B112
Factory Reset with Internal Memory
pasta

letschky said:
Flash via ADB all the img files fromB112 without Stock Recovery
Flash the Universal Cust B112 in TWRP
Flash Stock Recovery from B112
Factory Reset with Internal Memory
pasta
Click to expand...
Click to collapse
how do i flash using adb ?
I can flash using fastboot
fastboot flash boot boot.img etc
what is the command syntax for flashing using the adb command ?

elio321 said:
how do i flash using adb ?
I can flash using fastboot
fastboot flash boot boot.img etc
what is the command syntax for flashing using the adb command ?
Click to expand...
Click to collapse
fastboot is good
and this is good(fastboot flash boot boot.img etc )

letschky said:
fastboot is good
and this is good(fastboot flash boot boot.img etc )
Click to expand...
Click to collapse
stilll not working for me I am still getting the constant restart with the grinding noise

elio321 said:
stilll not working for me I am still getting the constant restart with the grinding noise
Click to expand...
Click to collapse
Your Bootloader is unlocked?

letschky said:
Your Bootloader is unlocked?
Click to expand...
Click to collapse
yes i believe so...how can i verify it is ?

elio321 said:
yes i believe so...how can i verify it is ?
Click to expand...
Click to collapse
Boot into Bootloader and the Red font says unlocked or green Font says Locked

when i go into bootloader mode it says PHONE Unlocked so I am presuming the bootloader is unlocked

elio321 said:
when i go into bootloader mode it says PHONE Unlocked so I am presuming the bootloader is unlocked
Click to expand...
Click to collapse
is TWRP installed?

elio321 said:
when i go into bootloader mode it says PHONE Unlocked so I am presuming the bootloader is unlocked
Click to expand...
Click to collapse
got red font unlocked

letschky said:
is TWRP installed?
Click to expand...
Click to collapse
it was...but now I am back to stock recovery....and i cant get twrp (5.1.1) to install using fastboot now

if you flash the img files says fastboot ok or?
---------- Post added at 05:02 PM ---------- Previous post was at 04:59 PM ----------
elio321 said:
it was...but now I am back to stock recovery....and i cant get twrp (5.1.1) to install using fastboot now
Click to expand...
Click to collapse
yes you can Flash Twrp via fastboot.
fastboot flash recovery TWRP_eng.img
have you a Backup of the B112 from twrp?

letschky said:
if you flash the img files says fastboot ok or?
---------- Post added at 05:02 PM ---------- Previous post was at 04:59 PM ----------
yes you can Flash Twrp via fastboot.
fastboot flash recovery TWRP_eng.img
have you a Backup of the B112 from twrp?
Click to expand...
Click to collapse
yes flashing the image files fastboot says ok
I have a number of B112 TWRP created backups

you can try to restore the backup and flash the Universal Cust B112,this helps me
---------- Post added at 05:26 PM ---------- Previous post was at 05:20 PM ----------
ok,step by step
Boot into Bootloader and flash all the img,Boot,Cache,Cust,System,Userdata.img via fastboot
Flash Twrp and Boot into TWRP
Restore your B112 Backup
Flash the Universal Cust for B112
Boot from TWRP into Bootloader and flash the Stock Recovery via fastboot.
Reboot and make a Factory Reset
This Procedur helps me go back from B205 or B209 to B112
---------- Post added at 05:29 PM ---------- Previous post was at 05:26 PM ----------
Here is the Universal Cust for B112
http://forum.xda-developers.com/mediapad-x2/development/mod-sim-card-switching-fix-t3254534
and here a Tool to flash TWRP 6.0 ENG
https://www.androidfilehost.com/?fid=24499762636008564

letschky said:
you can try to restore the backup and flash the Universal Cust B112,this helps me
---------- Post added at 05:26 PM ---------- Previous post was at 05:20 PM ----------
ok,step by step
Boot into Bootloader and flash all the img,Boot,Cache,Cust,System,Userdata.img via fastboot
Flash Twrp and Boot into TWRP
Restore your B112 Backup
Flash the Universal Cust for B112
Boot from TWRP into Bootloader and flash the Stock Recovery via fastboot.
Reboot and make a Factory Reset
This Procedur helps me go back from B205 or B209 to B112
---------- Post added at 05:29 PM ---------- Previous post was at 05:26 PM ----------
Here is the Universal Cust for B112
http://forum.xda-developers.com/mediapad-x2/development/mod-sim-card-switching-fix-t3254534
and here a Tool to flash TWRP 6.0 ENG
https://www.androidfilehost.com/?fid=24499762636008564
Click to expand...
Click to collapse
i don't have userdata.img
when u say reboot and make a factory reset...you mean from within Android/settings ? If not, from where do I factory reset
does it matter what version of twrp i use ?
you have provided a link to twrp 6......does this indicate it is for use with Android 6 or is it just the version number of the program ?

elio321 said:
i don't have userdata.img
when u say reboot and make a factory reset...you mean from within Android/settings ? If not, from where do I factory reset
does it matter what version of twrp i use ?
you have provided a link to twrp 6......does this indicate it is for use with Android 6 or is it just the version number of the program ?
Click to expand...
Click to collapse
Userdata.img is in the B112 UPDATE.APP extract this file and flash
fastboot flash userdata USERDATA.img
TWRP 6 work on Android 5 and 6,i am on B112 and use TWRP 6 and works
Yes you can make the Factory Reset from Settings or Power off and Press and hold Volume+ and Power Button at same Time for ca 10 sec. and boot in Stock Recovery.
In stock Recovery you can use Factory Reset and Wipe Cache

not boot ing past honor animation after doing those steps but cant factory reset from stock recovery and when i try and put twrp back it says failed write error

Which Version of X2 do you have,703L?

letschky said:
Which Version of X2 do you have,703L?
Click to expand...
Click to collapse
Yes GEM-703L

screwed up when flashing twrp

Alright so I screwed Up. I got in a rush and followed some guys advice in a thread for a different phone and not sure how to get back on track. Can someone help?
Heres what I did.....
G:\Downloads\oneplus 6 root\android p>fastboot flash recovery twrp-3.2.3-0-enchilada.img
target reported max download size of 536870912 bytes
sending 'recovery' (26744 KB)...
OKAY [ 0.569s]
writing 'recovery'...
FAILED (remote: (recovery_b) No such partition)
finished. total time: 0.577s
Click to expand...
Click to collapse
Nothing..... SO I googled and then typed this:
>>fastboot flash boot_b twrp-3.2.3-0-enchilada.img
Phone rebooted and showed twrp, cool. I restarted from there then, sh1t! Now I can't get back to twrp nor the os to follow the correct guide.
I tried holding power for 7 seconds - reboots and shows the red dot with white dots circling eternally
I tried holding volume down + power for 7 seconds - reboots and does the same thing
I tried holding volume up + power for 7 seconds - it goes into this all black recovery mode or something
no recovery mode is seen again yet since my mistake

As far as I know the only TWRP that works for Android p on the OnePlus 6 is bluspark. Try this unbrick thread or try fastboot bluspark.img
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
---------- Post added at 04:45 AM ---------- Previous post was at 04:36 AM ----------
Bluspark
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965
Fastboot commands
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965/page44

dgunn said:
As far as I know the only TWRP that works for Android p on the OnePlus 6 is bluspark. Try this unbrick thread or try fastboot bluspark.img
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
---------- Post added at 04:45 AM ---------- Previous post was at 04:36 AM ----------
Bluspark
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965
Fastboot commands
https://forum.xda-developers.com/oneplus-6/development/kernel-t3800965/page44
Click to expand...
Click to collapse
Hey thanks for trying to help me. I somehow just got it into fastboot mode....... Not really sure how, but I tried to follow the guide here to get in to it.
Anyway. I was running android oreo not android p before I tried to flash twrp.. does that make a difference?

So just to be clear you were trying to update TWRP on Oreo and not Android p?
Reason I ask is it says Android p in your original post

dgunn said:
So just to be clear you were trying to update TWRP on Oreo and not Android p?
Reason I ask is it says Android p in your original post
Click to expand...
Click to collapse
Hey! sorry, I made the folder called "Android P" because i will be upgrading to android p lineage os 16. Before I made this mistake, I was running the latest version of android oreo.
GOOD NEWS THOUGH. I somehow got into twrp through fastboot (using bootloader? option). now it keeps booting into twrp. How can I restore stock recovery from here and have a do-over? Thank you!

If you want to restore stock recovery you have to flash the stock image that you are currently on. If you are on the latest Oreo it would be 5.1.11
And I believe you will have to delete the TWRP folder. Not exactly sure when you do that but I read about it somewhere

dgunn said:
If you want to restore stock recovery you have to flash the stock image that you are currently on. If you are on the latest Oreo it would be 5.1.11
And I believe you will have to delete the TWRP folder. Not exactly sure when you do that but I read about it somewhere
Click to expand...
Click to collapse
Ok this is weird..........
I boot into twrp, then I choose; reboot, slot a (instead of default slot b), then the phone boots and it's running android P. what the heck!?
Not sure what happened....... here's the history
1- Android 8
2- Installed Android P dev preview
3- Rolled back to Android 8
4- Installed TWRP, screwed it up
5- Got back to TWRP, chose slot B, now it's booted
6- How is it running Android P

I really just want to get it back to full stock and start over since i screwed up. or even better... just want to fix my screw up the way it's meant to be done right......

Once it screwed up the TWRP it automatically switch slots.
Installed Android p (slot a)
Rolled back (slot b)
TWRP screw up (switched to slot a)
Every time you update it Flags the current slot
---------- Post added at 05:16 AM ---------- Previous post was at 05:15 AM ----------
Boot into recovery and Flash a full stock ROM Oreo

dgunn said:
Once it screwed up the TWRP it automatically switch slots.
Installed Android p (slot a)
Rolled back (slot b)
TWRP screw up (switched to slot a)
Every time you update it Flags the current slot
---------- Post added at 05:16 AM ---------- Previous post was at 05:15 AM ----------
Boot into recovery and Flash a full stock ROM Oreo
Click to expand...
Click to collapse
So is slot A and B only for ROMS and not for recovery?
When I downgraded to 8 from 9, technically 9 was still installed:silly:?

R0ttenB4ndit said:
hey @ajsmsg78. when i do adb devices through usb, it doesn't find it. it will keep booting to the red dot and spinning white dots around it. no recovery option appears on the phone. what mode do I have to be in for the pc to see it at this point?
Click to expand...
Click to collapse
1. Shut off device
2. Unplug any cables or otg connectwd to it.
3. Hold volup while holding power, you should be greeted with fastboot mode and a oneplus logo
4. When you get into the menu do
Code:
fastboot flash boot_x boot.img
Replace _x with _a then _b, to flash it to both slots.
5. By now you should be up and running, to flash twrp you have to
Code:
fastboot boot twrp.img
6. Flash the twrp zip to make it stay.
Reason being that twrp has to be patched to your current boot image, new phones with ab partition tables doesnt have a recovery partition. Thats why we have to boot the twrp img from our pc initially, then use the zip to patch it in permanently.
If you dont have a boot for your oos there is a thread with stock and prepatched twrp boot img's in discussion subforum
I posted this in the other thread before i saw any replies here, if you want to reset to full stock just use the fastboot unbrick bat

I can't boot back into TWRP lol. I also tried changing the slots while in fastboot with PC using
a) fastboot --set-active=a
b) fastboot set_active [a,b]
c) fastboot set_active other
none of them worked. how do you recommend I get back to how twrp and the rom is supposed to be installed? Thank again for the help, big help.
UPDATE: OK I see your previous response, I'll try and report back.

R0ttenB4ndit said:
I can't boot back into TWRP lol. I also tried changing the slots while in fastboot with PC using
a) fastboot --set-active=a
b) fastboot set_active [a,b]
c) fastboot set_active other
none of them worked. how do you recommend I get back to how twrp and the rom is supposed to be installed? Thank again for the help, big help.
Click to expand...
Click to collapse
Well, easiest way is the last mentioned one, its a real simple procedure. Hook up to fastboot, then click the corresponding bat and wait, heres the thread. Then to get twrp running follow my previous posted steps
forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665/page57

After installing the zip... should I wipe the cache/dalvik?
Update: the answer is yes, I'm reading. will update soon.

efinityy said:
1. Shut off device
2. Unplug any cables or otg connectwd to it.
3. Hold volup while holding power, you should be greeted with fastboot mode and a oneplus logo
4. When you get into the menu do
Code:
fastboot flash boot_x boot.img
Replace _x with _a then _b, to flash it to both slots.
5. By now you should be up and running, to flash twrp you have to
Code:
fastboot boot twrp.img
6. Flash the twrp zip to make it stay.
Reason being that twrp has to be patched to your current boot image, new phones with ab partition tables doesnt have a recovery partition. Thats why we have to boot the twrp img from our pc initially, then use the zip to patch it in permanently.
If you dont have a boot for your oos there is a thread with stock and prepatched twrp boot img's in discussion subforum
I posted this in the other thread before i saw any replies here, if you want to reset to full stock just use the fastboot unbrick bat
Click to expand...
Click to collapse
Alright, thought I had it............ but no, now it just keeps rebooting into fast mode. Maybe I'm getting ahead of myself here. Sorry....
Here's what I did:
cmd
>>fastboot flash boot_a twrp-3.2.3-0-enchilada.img
>>fastboot flash boot_b twrp-3.2.3-0-enchilada.img
all ok
>>fastboot boot twrp-3.2.3-0-enchilada.img
the phone boots into twrp, cool
cmd again
>>adb push twrp-installer-enchilada-3.2.3-0.zip /sdcard/
then installed twrp-installer-enchilada-3.2.3-0.zip to make it stay
wiped dalvik/cache and it rebooted to twrp again
think I am now in the clear yay (not).
>>adb push lineage-16.0-20180916_111137-UNOFFICIAL-enchilada.zip /sdcard/
then installed lineage-16.0-20180916_111137-UNOFFICIAL-enchilada.zip
success
I reboot but it still goes to twrp
i change slot to b (it was set to A) hoping maybe it'd boot to lineage
phone reboots and now I can't make it go back to twrp. It keep rebooting into fastboot no matter what I do (hard keys reset/options to choose)
stuck again.

When try to mount the twrp image just to boot into it, I get this now:
>>fastboot boot twrp-3.2.3-0-enchilada.img
downloading 'boot.img'...
OKAY [ 0.568s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.584s

so @efinityy what's this fastboot unbrick bat you speak of? Is it this one I need: flash-all-partitions-fastboot.bat ?
Thanks again.
Which zip is it that I need?

R0ttenB4ndit said:
so @efinityy what's this fastboot unbrick bat you speak of? Is it this one I need: flash-all-partitions-fastboot.bat ?
Thanks again.
Which zip is it that I need?
Click to expand...
Click to collapse
Exactly, but i dont think its the all partitions one, it says in the thread which one almost always is the necessary one, using the wrong one can make it worse... and the twrp zip you need can be gotten from blu_spark kernel threads download section, you want the twrp v2 for pie, v1 for Oreo.. Scratch that, v2 works for all.
Dont flash the twrp img in boot partition yo ? you want the stock boot image/ kernel there... Twrp will later be merged with your current boot, flashing twrp to boot a or b will make you have no kernel, having no kernel equals having no instructions to get android running, and instead of calling the kernel to boot android it will just call twrp over and over
Why we are installing the zip is because previously we had recovery partition, a dedicated partition made for the recovery, now we don't, the recovery is part of the kernel, and we don't ever wanna lose our kernel because that means the phone doesn't know how to boot itself to a usable state, so that's why we only fastboot BOOT twrpimghere... Then install the twrp zip to to patch out the old recovery, like removing a tumor from a body, then patch that empty place with a bandaid that is twrp, so you have your old kernel, the one that can boot the system, and a fresh bandaid on top of it that is twrp... Sorry for the weird metaphoring, I trying to put a/b partitions and it's functions in condensed text is a challenge, but as soon as you grasp the concept you will understand how to do it flawlessly every time

efinityy said:
Exactly, but i dont think its the all partitions one, it says in the thread which one almost always is the necessary one, using the wrong one can make it worse... and the twrp zip you need can be gotten from blu_spark kernel threads download section, you want the twrp v2 for pie, v1 for oreo
Click to expand...
Click to collapse
In the OP it says:
Now usually the one needed is only the first "flash-all-partitions-fastboot.bat" but if you are badly bricked i recommend to use flash-all-partitions.bat .
Click to expand...
Click to collapse
When you say I want the twrp..... is this something else I need before I run the Stock Fastboot ROM bat file?

which step did I go wrong?
I did Replace _x with _a then _b, to flash it to both slots
I thought it was meaning to flash it to both A and B? What did that mean? Thank you!

Qualcomm Crashdump Screen when I try to boot TWRP

recently I update to Android PIe but since then I couldnt get TWRP back again. everytime I'm botting to TWRP I get Qualcomm Crashdump Screen.
I'm using twrp-3.2.3-0-enchilada
does anyone have any idea ?

W4LUIZ said:
recently I update to Android PIe but since then I couldnt get TWRP back again. everytime I'm botting to TWRP I get Qualcomm Crashdump Screen.
I'm using twrp-3.2.3-0-enchilada
does anyone have any idea ?
Click to expand...
Click to collapse
Use blu_spark twrp recovery pls.
https://forum.xda-developers.com/devdb/project/?id=27466#downloads
Flash img via adb and the zip in blu TWRP itself.

Pundy said:
Use blu_spark twrp recovery pls.
https://forum.xda-developers.com/devdb/project/?id=27466#downloads
Flash img via adb and the zip in blu TWRP itself.
Click to expand...
Click to collapse
sorry to hijack a post, but im having same problem!
how would I get the zip file onto my phone?

gary_auto said:
sorry to hijack a post, but im having same problem!
how would I get the zip file onto my phone?
Click to expand...
Click to collapse
Hey. Just boot your phone into fastboot mode. flash the blu_spark recovery.IMG.
Now the phone reboots into twrp blu_spark recovery. Now you can transfer the zip to your phone storage (mount option in twrp) or use usb otg .
And now you can flash the zip and you are good to go

Pundy said:
Hey. Just boot your phone into fastboot mode. flash the blu_spark recovery.IMG.
Now the phone reboots into twrp blu_spark recovery. Now you can transfer the zip to your phone storage (mount option in twrp) or use usb otg .
And now you can flash the zip and you are good to go
Click to expand...
Click to collapse
DO NOT flash the img. You need to Fastboot boot twrp. Img
---------- Post added at 03:51 AM ---------- Previous post was at 03:49 AM ----------
gary_auto said:
sorry to hijack a post, but im having same problem!
how would I get the zip file onto my phone?
Click to expand...
Click to collapse
Boot to Fastboot
Fastboot boot bluespark twrp. Img
Flash bluespark twrp. Zip
Reboot recovery
Flash magisk.

yldlj said:
DO NOT flash the img. You need to Fastboot boot twrp. Img
---------- Post added at 03:51 AM ---------- Previous post was at 03:49 AM ----------
Boot to Fastboot
Fastboot boot bluespark twrp. Img
Flash bluespark twrp. Zip
Reboot recovery
Flash magisk.
Click to expand...
Click to collapse
after I fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
the phone restarts with a blackscreen white/blue led???

gary_auto said:
after I fastboot boot twrp-3.2.3-x_blu_spark_v9.86_op6.img
the phone restarts with a blackscreen white/blue led???
Click to expand...
Click to collapse
Not sure what you have done to get to this point. I would start over with the MSN tool or you could try fastboot rom.

I have pretty much the same issue:
- "standard" TWRP wouln't boot (stuck at crashdump)
- blu spark TWRP boots and installs but afterwards phone doesn't boot anymore ("boots" into crashdump)
I have solved the phone-not-booting part by reflashing everything (meaning that I am now on a phone that is just stock with unlocked bootloader).
The MSM Download Tool could be the solution to our issue but I'm now off to work.

erecovery honor 6x android o no flash

hi
i'm want to flash stock recovery and erecovery
but erecovery whit commond fastboot flash recovery_ramdisk_b no flash
Flash correctly
But again, twrp will boot
twrp in the erecovery
sorry for my english

That's because your command is wrong. The command is same as the one you used for flashing TWRP. i.e fastboot flash recovery_ramdisk nameofrecovery.img

Mannan Qamar said:
That's because your command is wrong. The command is same as the one you used for flashing TWRP. i.e fastboot flash recovery_ramdisk nameofrecovery.img
Click to expand...
Click to collapse
I use this command
But twrp is still in erecovery

Boot into twrp by powering off the phone and then holding down volume up and power button simultaneously

Mannan Qamar said:
Boot into twrp by powering off the phone and then holding down volume up and power button simultaneously
Click to expand...
Click to collapse
My problem is that erecovery does not replace twrp

Try to flash correct eRecovery using "Huawei MultiTool" by TeamMT!

MadDog.76 said:
Try to flash correct eRecovery using "Huawei MultiTool" by TeamMT!
Click to expand...
Click to collapse
When I select emui8, the erecovery flash button turns off

Are you sure img flashed is a stock erecovery image and not a twrp image???

MadDog.76 said:
Are you sure img flashed is a stock erecovery image and not a twrp image???
Click to expand...
Click to collapse
yes i'm extracted from official rom

What command are you using? That's all the difference
---------- Post added at 05:21 PM ---------- Previous post was at 05:20 PM ----------
Why so you need those recoveries again?

Correct Command
If you want to flash the "E"Recovery, your command has to be "fastboot flash erecovery_ramdisk nameofyourimg.img"

Mannan Qamar said:
What command are you using? That's all the difference
---------- Post added at 05:21 PM ---------- Previous post was at 05:20 PM ----------
Why so you need those recoveries again?
Click to expand...
Click to collapse
I use the fastboot flash recovery_ramdisk_b xxx.img and fastboot flash erecovery_ramdisk xxx.img command
My mobile should go to erecovery for the initial boot

Lakoia said:
If you want to flash the "E"Recovery, your command has to be "fastboot flash erecovery_ramdisk nameofyourimg.img"
Click to expand...
Click to collapse
I used this command but did not work

I'v flashed TWRP on my 6x. But IMHO Nougat and Oreo have different boot methods:
Nougat:
Power on > Unlocked screen warning > now press and keep pressed Vol.+ = TWRP (if flashed as eRecovery)
Oreo:
Power on > Unlocked screen warning > now press and keep pressed Vol.+ = stock eRecovery
Power and Vol. + keep pressed at the same time= TWRP
Please try and let me know if is your same condition!