Database Info

[Q] fastboot flash recovery problem? "variable not supported"

Not sure if this belongs over here in Q/A as a new thread, or if I should append this to shabbypenguin's root thread. I am attempting to root my Photon Q following shabbypenguin's method. I downloaded the latest SDK bundle, installed latest Motorola drivers, successfully unlocked the bootloader.
I can't seem to get any recovery images to flash correctly at this point, though. When I run "fastboot flash recovery cwmrecovery.img" I get the following output:
Code:
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6632 KB)...
OKAY [ 0.519s]
writing 'recovery'...
OKAY [ 2.363s]
finished. total time: 2.885s
Not sure if "Variable not supported" is a normal message or not, but otherwise it appears to have completed successfully? But when I reboot into recovery mode, I always get the android with a red triangle screen, like this. I have tried flashing shabbypenguin's CWM recovery image, the latest TWRP recovery image, and the stock recovery image linked to in this thread. Same result every time; red triangle screen.
My phone is running the updated OTA build (77.8.10). Is that what is hindering my ability to flash and root successfully? Not sure where else I could have gone wrong. The only other thing I can think of is that before starting with all this, I did have encryption enabled on the phone. But before unlocking the bootloader and attempting to flash CWM recovery, I performed a factory reset to remove the encryption.
UPDATE: it doesn't actually seem like the recovery images are getting flashed at all. At first I thought something was being corrupted (given the red triangle).
But if I press the Up/Down Vol buttons on that screen, I get the Android system recovery utility menu. So if a recovery flash had occurred, this would have been overwritten, right?
I'd be grateful for any suggestions of what to try at this point.

i've never seen that bootloader message before, but it seems like your recovery might be getting flashed back to stock when you reboot. another guy had this issue, you might hopefully be able to solve it by reading this short thread here:
http://forum.xda-developers.com/showthread.php?t=2017748
edit; in short, you could try rooting with Motofail2go: http://forum.xda-developers.com/showthread.php?t=1940594, then use your SU priviledge to rename recovery-from-boot.p to recovery-from-boot.bak,(in /system), then reflash recovery of choice and it should stick.

Thanks yogi! That was indeed my problem as well. I hadn't come across that thread in my initial searching, so I really appreciate your ultra fast response and the sage solution you figured out in the earlier thread. You rock!

Ah, glad that worked for you also! I'm not sure why some people have had to do that, while I don't think I ever did(I have a file named recovery-from-boot.bak, but I don't think I actively renamed it). I am also not sure why we have have an unlockable bootloader, yet without a 3rd-party exploit, some people are getting stuck

In shabbys supersu zip the script had it rename that boot on recovery file. Maybe people are skipping that step after flashing recovery or moto changed the file location and it doesnt match shabbys original script now.
Sent from my XT897 using Tapatalk 2

Rangerbry said:
In shabbys supersu zip the script had it rename that boot on recovery file. Maybe people are skipping that step after flashing recovery or moto changed the file location and it doesnt match shabbys original script now.
Sent from my XT897 using Tapatalk 2
Click to expand...
Click to collapse
Ah ok, i figured something was renaming that file. The thing is, is there a way to boot straight into recovery from the bootloader? I've always had to boot into the system and then adb reboot recovery.

just hold up like normal after
fastboot reboot

ah yes ok, i guess people should do that after flashing recovery so they can get SU flashed before losing their recovery. and we'll see if Shabby's SU zip still disables that recovery file. i guess that's sort of standard procedure on phones in general, but i don't think i ever did that on this device.

Nice, thanks! Yeah, I was booting back in to system and doing adb reboot recovery as well. The couple blog write-ups I was following weren't clear on that aspect, but then, using the hardware buttons to force it directly to recovery makes perfect since; wondering why I didn't think about that at the time.

Guys!
I have the same problem!
My phone version XT925:
4.1.2
unlocked bootloader
no ROOT
Phone not loading to recovery! so I can't install SU.zip, to get ROOT and rename recovery-from-boot.p.
And because my version 4.1.2 I can't use exploit to get root.
I am realy need your help!

Alex42rus said:
Guys!
I have the same problem!
My phone version XT925:
4.1.2
unlocked bootloader
no ROOT
Phone not loading to recovery! so I can't install SU.zip, to get ROOT and rename recovery-from-boot.p.
And because my version 4.1.2 I can't use exploit to get root.
I am realy need your help!
Click to expand...
Click to collapse
Have you done the hardware key method?
Power + down till phone resets than power + up will you are in recovery?
Otherwise use this command in fastboot(meaning you have SDK tools and you open a command window in platform tools folder):
adb reboot recovery
than the phone should reboot itself into recovery
let us know if you need anything else

Hinyo said:
Have you done the hardware key method?
Power + down till phone resets than power + up will you are in recovery?
Otherwise use this command in fastboot(meaning you have SDK tools and you open a command window in platform tools folder):
adb reboot recovery
than the phone should reboot itself into recovery
let us know if you need anything else
Click to expand...
Click to collapse
>Power + down till phone resets than power + up will you are in recovery?
Phone goes to boot menu.
if I select recovery, phone try to load it (green horizontal anroid logo), but after some time it start the system.
>adb reboot recovery
the same.

Alex42rus said:
>Power + down till phone resets than power + up will you are in recovery?
Phone goes to boot menu.
if I select recovery, phone try to load it (green horizontal anroid logo), but after some time it start the system.
>adb reboot recovery
the same.
Click to expand...
Click to collapse
This means you have stock recovery.
Flash a custom recovery - TWRP, CWM, OpenRecovery.
If you are having issues with recovery not sticking, there is a thread right below yours which addresses this.
Especially see this post from kabaldan.

arrrghhh said:
This means you have stock recovery.
Flash a custom recovery - TWRP, CWM, OpenRecovery.
Click to expand...
Click to collapse
Yes, I am tring, but when I do it, I have "variable not supported" message.
Console:
C:\adt-bundle-windows-x86_64\sdk\platform-tools>fastboot flash recovery twrp-hdr
ecovery.img
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (6678 KB)...
OKAY [ 0.502s]
writing 'recovery'...
OKAY [ 1.960s]
finished. total time: 2.465s
C:\adt-bundle-windows-x86_64\sdk\platform-tools>

Alex42rus said:
Yes, I am tring, but when I do it, I have "variable not supported" message.
Click to expand...
Click to collapse
Please read the link I provided above, and see if it helps you. Or the second post in this thread...

arrrghhh said:
Please read the link I provided above, and see if it helps you. Or the second post in this thread...
Click to expand...
Click to collapse
>Stock OTA update contains /system/etc/install-recovery.sh that will re-flash the recovery to stock any time you boot the android system.
>Boot to custom recovery first before starting the android system after the update
This path realy help me! I go to recovery by presing power + up after recovery.
> and remove this script by using the console or adb shell:
adb shell not connected, and I not find console in recovery, but before reboot recovery ask me to remove "re-install recovery"
great thanks !

Had the same problem trying to flash TWRP to my XT926. Flashing multiple versions of CWM or TWRP gave the same results. (bootloader) variable not supported, but flashing would still appear to proceed ok. However the recovery was always jacked somehow. The only thing that would flash correctly (even with the error) was the stock recovery.
I was using minimal adb & fastboot. Clued in off of a thread off of droid rzr forums (cannot post url due to my new user status) I FINALLY realized I needed to replace the included AOSP binaries with the motorola ones.
Upon replacing the binaries flashing proceeded without error & TWRP was installed & running correctly.
So as this thread came up most of the time when searching for solution to my error, I hope this reply helps.
So, in short double check your version of adb fastboot (or its binaries), your usb drivers, & your recovery is appropriate/ latest update for your phone/ firmware.
Sent from my XT926 using XDA Free mobile app

4ndr01dpilot said:
So, in short double check your version of adb fastboot (or its binaries), your usb drivers, & your recovery is appropriate/ latest update for your phone/ firmware.
Click to expand...
Click to collapse
Thanks for this tip. I used the fastboot version from Motopocalypse instead of my standard ADB installation version, and the variable message stopped appearing. :highfive:

I was puzzled for days being stuck in endless "Flashing recovery ..."
In the end I decided, after saying 1 hour waiting a hypothetical "success/congrats message", NOT QUITTING the current fastboot screen, to select the recovery option in this very fastboot menu (on a Razr i : Vol- to highlight recovery item, then Vol+ to select) and bang I was in TWRP menu. What to do next once in, it is another story.

[ROOTING] Ulefone Be Touch 2 with TWRP recovery

Hi Folks,
Disclosure: No responsibility taken or accepted in any form if the following process failed.
As forum rules prevented me from posting links try to understand how to find referred files.
1. Prepare a PC with Windows 7 installed and the automatic Windows driver update lookup function possibly disabled.
2. Download BETA-SuperSU-v2.49.zip (appr. 4 MB, from chainfire eu and copy it to the phone's SD card or to an external micro SD card.
3. Download the latest stock ROM and flash tool packed together (e.g. 'Be-Touch-2_150702_s7yler.zip') from needrom com . Search for ulefone-be-touch-2.
4. Download TWRP recovery image file from needrom com . Search for be-touch-2-twrp-2-8-7-0.
Extract the rar archive and rename recoverye.img to recovery.img
5. Extract 'Be-Touch-2_150702_s7yler.zip' and replace the recovery.img file in the "Be-Touch-2_150702_s7yler\One Key Flashing(Be Touch 2_150702)\software" folder with the one from the TWRP archive (see point 2).
6. Install the MTK chipset driver (it works on Win7 only at the present time):
- Navigate to the "Be-Touch-2_150702_s7yler\One Key Flashing(Be Touch 2_150702)\Driver Auto Installer" folder.
- Open a Command Window to see what happens on the command line.
- Run Install.bat with real Administrator priviledges (in most cases Run as Administrator may not be enough - refer to UAC).
- Wait until the driver installation is finished. You will see on the screen if the drivers were installed successfully (e.g. "Driver install done").
7. Flashing ROM
Notes:
- Flashing ROM will wipe all your data. If you have not done a backup before you will permanently lose your data!
- The doc file containing pictures included in the zip file can also be followed.
- Do NOT format your phone with the flashing tool, that can result in lost IMEI.
- For anvanced users: the flash_tool.exe in the Smart Phone Flash Tool package can also be used only to flash recovery.img using an enclosed scatter.txt file.
a/ Open the Be-Touch-2_150702_s7yler\One Key Flashing folder and run SP_Facility_DL_Tool.exe
b/ Turn off the phone, take out the battery, press the Scan button in the SP_DownLoad window then connect your phone to the PC via USB.
c/ After the text "N/A+COM(x)" appears on the left hand side of the window disconnect your phone, reinsert the battery, press the Start button and reconnect your phone via the USB cable.
d/ Wait until the flashing utility finishes updating the phone (e.g. the process bar shows 100 % on yellow background and "DL OK" can be read to the left of the process bar).
8. After flashing, enter the TWRP custom recovery: press vol up + power to boot for a few seconds then install BETA-SuperSU-v2.49.zip from your (external) SD card.
9. You are done with rooting.

Fastboot
litokraz said:
- Flashing ROM will wipe all your data if you have not done a backup before!
- The doc file containing pictures included in the zip file can also be followed.
- Do NOT format your phone with the flashing tool, that can result in lost IMEI.
- For anvanced users: the flash_tool.exe in the Smart Phone Flash Tool package can also be used only to flash recovery.img using an enclosed scatter.txt file.
Click to expand...
Click to collapse
Again, for advanced users: You can also use fastboot (get it elsewhere) to flash just the TWRP recovery without wiping the rest of the phone: (e.g. "fastboot.exe flash recovery recovery-betouch2.img"), then use it to install supersu. You can also then flash the stock recovery back over it if you wish. Works like a charm.

marblemunkey said:
Again, for advanced users: You can also use fastboot (get it elsewhere) to flash just the TWRP recovery without wiping the rest of the phone: (e.g. "fastboot.exe flash recovery recovery-betouch2.img"), then use it to install supersu. You can also then flash the stock recovery back over it if you wish. Works like a charm.
Click to expand...
Click to collapse
Yes you are right. The method I described above also updates to the latest(?) Ulefone ROM as of 02-07-2015.
Even you can flash a Carlive recovery (tried and works) based on the downloadable from the "Ulefone Be Touch 2, 5.5 Inch Full HD, Metal Frame, MT6752 64-bit, 3050mAh Battery" thread Post #76. Carlive (originated from CWM) lacks the annoying splash screen which is included in TWRP.

UPDATE: Never mind, I got it. WooHoo
Guys, how do I get to Fastboot mode on my BE Touch 2? I tried power + volume down, yet it takes me to chinese menu I do not understand.
Odesláno z mého Be Touch 2 pomocí Tapatalk

Thank you Litakraz .... Good job done ... works like charm ..well explained

marblemunkey said:
Again, for advanced users: You can also use fastboot (get it elsewhere) to flash just the TWRP recovery without wiping the rest of the phone: (e.g. "fastboot.exe flash recovery recovery-betouch2.img"), then use it to install supersu. You can also then flash the stock recovery back over it if you wish. Works like a charm.
Click to expand...
Click to collapse
Hi, i have one Be Touch 2 and i can't find the fastboot mode in my recovery mode ( chinese recovery )
here is a screenshot of a similar recovery mode i got
youtu.be/RwpUyc7ig5w
Can you explain how to enter in Fastboot mode please ?
Thanks
Sorry for my bad english
UPDATE : I finally tried the command "adb reboot bootloader"
and after this I was able to flash recovery.img with fastboot (fastboot flash recovery recovery.img)
but i still can't boot on TWRP (still chinese bootloader)
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (13540 KB)...
OKAY [ 0.458s]
writing 'recovery'...
OKAY [ 0.207s]
finished. total time: 0.665s
UPDATE 2 :
My bad, to enter in TWRP mode reboot the phone using POWER+VOL UP
worked like a charm with the recovery img from needrom , thanks !
PS : /!\ AVOID TO UPDATE YOUR DEVICE OR YOU WILL BE BLOCKED ON THE ULEFONE LOGO !!! /!\

dkpiit said:
Hi, i have one Be Touch 2 and i can't find the fastboot mode in my recovery mode ( chinese recovery )
here is a screenshot of a similar recovery mode i got
youtu.be/RwpUyc7ig5w
Can you explain how to enter in Fastboot mode please ?
Thanks
Sorry for my bad english
UPDATE : I finally tried the command "adb reboot bootloader"
and after this I was able to flash recovery.img with fastboot (fastboot flash recovery recovery.img)
but i still can't boot on TWRP (still chinese bootloader)
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (13540 KB)...
OKAY [ 0.458s]
writing 'recovery'...
OKAY [ 0.207s]
finished. total time: 0.665s
UPDATE 2 :
My bad, to enter in TWRP mode reboot the phone using POWER+VOL UP
worked like a charm with the recovery img from needrom , thanks !
Click to expand...
Click to collapse
Tried that method, always get stuck in <waiting for device> !!!
Any advice ???

Heshamvido said:
Tried that method, always get stuck in <waiting for device> !!!
Any advice ???
Click to expand...
Click to collapse
Yes, just download and install adbdriver[DOT]com/downloads/

Thanks to the OP for the guide. I am now rooted & the phone is working perfectly.
Now just waiting for cyanogenmod to be released for it & I'll be a happy man.

Is there a way to root the Ulefone be touch one which is compatible with the last firmware ? (15/08/11)
The solution given by @Pasi_K don't work with the update

Darkstar2r1 said:
Is there a way to root the Ulefone be touch one which is compatible with the last firmware ? (15/08/11)
The solution given by @Pasi_K don't work with the update
Click to expand...
Click to collapse
I am curious on that too! Did you get it running?
I will try a different recovery.... hope that works.

hi guys..
anyone has NVRAM for this device..? it is black screen now but it is working..

Installing a Recovery on Xperia M2

Hello all,
Before all, yes I have read many thread about installing a Recovery on this Phone (LB & UB).
So, what I have done :
- Unlock the boot loader following the Sony's guide → OK
- Installing fastboot on my debian →OK
- Flashing boot following this guide : http://forum.xda-developers.com/xpe...2303-cwm-based-recovery-6-0-4-6-root-t2884503 → OK
- Now I have a "Cyanogen recovery"
- I want to change this Recovery to TWRP and I have following this topic : http://forum.xda-developers.com/xperia-m2/general/unlocked-bl-root-sony-xperia-m2-android-t3214498
I write this command :
Code:
fastboot flash recovery RECOVERY-TWRP-2.8.7.0-D230X_D240X-UPDATED-THEME.img
Sending 'recovery'
OKAY
writing 'recovery'
OKAY
finished
But nothing happens I'm still stuck in 'cyanogen recovery'
Any idea what i have done wrong ?
Thank you !
Auze

Auze-Absy said:
Hello all,
Before all, yes I have read many thread about installing a Recovery on this Phone (LB & UB).
So, what I have done :
- Unlock the boot loader following the Sony's guide → OK
- Installing fastboot on my debian →OK
- Flashing boot following this guide : http://forum.xda-developers.com/xpe...2303-cwm-based-recovery-6-0-4-6-root-t2884503 → OK
- Now I have a "Cyanogen recovery"
- I want to change this Recovery to TWRP and I have following this topic : http://forum.xda-developers.com/xperia-m2/general/unlocked-bl-root-sony-xperia-m2-android-t3214498
I write this command :
Code:
fastboot flash recovery RECOVERY-TWRP-2.8.7.0-D230X_D240X-UPDATED-THEME.img
Sending 'recovery'
OKAY
writing 'recovery'
OKAY
finished
But nothing happens I'm still stuck in 'cyanogen recovery'
Any idea what i have done wrong ?
Thank you !
Auze
Click to expand...
Click to collapse
Easy: that Cyanogen Recovery (which is an old version, btw) is stored in the boot image as a separate ramdisk, with a script that pops-up an LED to tell you to decide to open it or not. The TWRP recovery however is in a separate /recovery partition, and it can only be triggered via Vol- + Power until the BIG Sony logo pops-up. That's it. You can have both at the same time if you wish so

linuxct said:
Easy: that Cyanogen Recovery (which is an old version, btw) is stored in the boot image as a separate ramdisk, with a script that pops-up an LED to tell you to decide to open it or not. The TWRP recovery however is in a separate /recovery partition, and it can only be triggered via Vol- + Power until the BIG Sony logo pops-up. That's it. You can have both at the same time if you wish so
Click to expand...
Click to collapse
Hello !
Thx for the reply !
After several try, I never show the TWRP booting. Always stuck on the cynaogen recovery.
I has flashed again the phone with flashboot and the last stock system to reset completly all partitions → OK
I will retest this Week-end without the boot.img (Just TWRP) and let you now.
Thx again !

did you give root access to fastboot command? did you upgrade your bootloader?

dark90 said:
did you give root access to fastboot command? did you upgrade your bootloader?
Click to expand...
Click to collapse
Can't do that, because i am stuck with the cyanogen recovery and unable to start a ROM.
I have used the Flastools to restore an Official Stock Rom due to this.
I will change this phone on fews days, so I will retry later when giving the phone to my nephew.
Thank you for the time spend !
Auze

How can I root project spectrum?

Are there any tools around for rooting Spectrum on the R7Plusf?

W1F1 said:
How am I able to root project spectrum on the Oppo R7 Plus?
Thanks in advance!
Click to expand...
Click to collapse
Hello, W1F1. There is no way at this point in time to root Project Spectrum on Oppo R7Plus as TWRP isnt compatible. They changed a lot when they made Project Spectrum. For now there is no TWRP. So there is no way to root. It's Fastboot is also set to non-root access making is hard to use the command (fastboot flash recovery _TWRP-HERE_) but not impossible to flash the stock recovery and then ColorOS to get back to safety (by safety I mean CyanogenMod 14.1 [OFFICIAL] or AICP [UNOFFICIAL]). All you need to do is ask and I'll give you the links.

EximusCode said:
Hello, W1F1. There is no way at this point in time to root Project Spectrum on Oppo R7Plus as TWRP isnt compatible. They changed a lot when they made Project Spectrum. For now there is no TWRP. So there is no way to root. It's Fastboot is also set to non-root access making is hard to use the command (fastboot flash recovery _TWRP-HERE_) but not impossible to flash the stock recovery and then ColorOS to get back to safety (by safety I mean CyanogenMod 14.1 [OFFICIAL] or AICP [UNOFFICIAL]). All you need to do is ask and I'll give you the links.
Click to expand...
Click to collapse
Thanks for the reply! So I could use stock recovery to get back to a version of color os that has fastboot enabled, and then get TWRP and then cyanogen mod from there?

W1F1 said:
Thanks for the reply! So I could use stock recovery to get back to a version of color os that has fastboot enabled, and then get TWRP and then cyanogen mod from there?
Click to expand...
Click to collapse
Bingo my friend. If you want the links you need only ask. :good:

EximusCode said:
Bingo my friend. If you want the links you need only ask. :good:
Click to expand...
Click to collapse
The links would be fantastic, thanks so much!

W1F1 said:
The links would be fantastic, thanks so much!
Click to expand...
Click to collapse
Will post them ASAP

Thanks!

W1F1 said:
Thanks!
Click to expand...
Click to collapse
Recovery:http://goo.gl/1AdXkD
ROM:https://s3.amazonaws.com/public.opp...olorOS/Specified_ColorOS_R7plusf_full_014.zip
0. Move all files to external MicroSD card *rename the ROM to update.zip*
1. Flash the recovery.img to recovery partition. With (fastboot flash recovery "recovery.img) *remember to put the recovery.img file in the ADB and Fastboot file for easier transfer*
2. Reboot into the system recovery and select Update, then go to where you put your ROM and select it
3. Wait for it to flash and then reboot
4. Your reboot will hang. Leave it do that for about 5 minutes, then reboot into fastboot mode again.
5. Seeing as you are now on a ROM with an unlocked bootloader you will be able to now flash TWRP recovery with the command (fastboot flash recovery "TWRPRECOVERYNAME") *I used TWRPRECOVERYNAME as an example as to where the recovery file needs to go. You should also have this in the ADB and Fastboot folder*

EximusCode said:
Will post them ASAP
Click to expand...
Click to collapse
I'm sorry but I can't seem to download from app.box, even after creating an account. Could you please upload the recovery to somewhere else like google drive?
EDIT: Whoops disregard that I managed to download it.

W1F1 said:
I'm so so sorry but I can't seem to download from app.box, even after creating an account. Could you please upload the recovery to somewhere else like google drive?
Sorry again.
EDIT: Sorry disregard that I managed to download it.
Click to expand...
Click to collapse
Hope it works for you like it did for me :good:

EximusCode said:
Recovery:http://goo.gl/1AdXkD
ROM:https://s3.amazonaws.com/public.opp...olorOS/Specified_ColorOS_R7plusf_full_014.zip
0. Move all files to external MicroSD card *rename the ROM to update.zip*
1. Flash the recovery.img to recovery partition. With (fastboot flash recovery "recovery.img) *remember to put the recovery.img file in the ADB and Fastboot file for easier transfer*
2. Reboot into the system recovery and select Update, then go to where you put your ROM and select it
3. Wait for it to flash and then reboot
4. Your reboot will hang. Leave it do that for about 5 minutes, then reboot into fastboot mode again.
5. Seeing as you are now on a ROM with an unlocked bootloader you will be able to now flash TWRP recovery with the command (fastboot flash recovery "TWRPRECOVERYNAME") *I used TWRPRECOVERYNAME as an example as to where the recovery file needs to go. You should also have this in the ADB and Fastboot folder*
Click to expand...
Click to collapse
Ok I'm still having an issue. The flashing of the recovery goes through successfully but when I try to enter recovery mode it simply shows the Oppo logo and the screen goes black. Like it's been doing with all the recovery's that I've tried. If I try the "fastboot boot recovery.img" it has this error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.485s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.553s

W1F1 said:
Ok I'm still having an issue. The flashing of the recovery goes through successfully but when I try to enter recovery mode it simply shows the Oppo logo and the screen goes black. Like it's been doing with all the recovery's that I've tried. If I try the "fastboot boot recovery.img" it has this error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.485s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.553s
Click to expand...
Click to collapse
After flashing recovery, type (fastboot reboot) Before you press enter, hold down the Volume - button (on the phone) and simultaneously press enter. You should then be able to boot to stock recovery
JUST REMEMBER TO NOT BOOT BACK INTO SPECTRUMOS. This will reset the recovery partition as it locks it on boot

EximusCode said:
After flashing recovery, type (fastboot reboot) Before you press enter, hold down the Volume - button (on the phone) and simultaneously press enter. You should then be able to boot to stock recovery
JUST REMEMBER TO NOT BOOT BACK INTO SPECTRUMOS. This will reset the recovery partition as it locks it on boot
Click to expand...
Click to collapse
Sadly no all it does is show the Oppo logo, and then when it should show the recovery screen it just goes black. I think it's something to do with the DTB error before.

W1F1 said:
Sadly no all it does is show the Oppo logo, and then when it should show the recovery screen it just goes black. I think it's something to do with the DTB error before.
Click to expand...
Click to collapse
Please give me some more time. I will find some more info. I will be back to you as soon as I have found some more.

EximusCode said:
Please give me some more time. I will find some more info. I will be back to you as soon as I have found some more.
Click to expand...
Click to collapse
Thank you. I have looked around a lot and I believe creating a new recovery img using the dt from here might work: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/716
Please let me know if you find something.

W1F1 said:
Thank you. I have looked around a lot and I believe creating a new recovery img using the dt from here might work: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/716
Please let me know if you find something.
Click to expand...
Click to collapse
You could very well try that and it work. I have limited knowledge when it comes to development of ROMs and Recoveries so I'm not too sure how you will fair, it may take a bit of trial and error. Tell me how you go with it

EximusCode said:
You could very well try that and it work. I have limited knowledge when it comes to development of ROMs and Recoveries so I'm not too sure how you will fair, it may take a bit of trial and error. Tell me how you go with it
Click to expand...
Click to collapse
Update:
Bad news: Unfortunately my phone is now stuck in a boot loop.
Good news: Using a recovery provider by the user "Ricky" on the first page of this thread: http://community.oppo.com/en/forum.php?mod=viewthread&tid=46395&extra=&page=1 I have been able to flash the stock recovery and it is now working. Because of the boot loop problem I am reinstalling Spectrum through recovery to try and get out of that, then hopefully I will be able to flash back to Color OS if the boot loop stops.

W1F1 said:
Update:
Bad news: Unfortunately my phone is now stuck in a boot loop.
Good news: Using a recovery provider by the user "Ricky" on the first page of this thread: http://community.oppo.com/en/forum.php?mod=viewthread&tid=46395&extra=&page=1 I have been able to flash the stock recovery and it is now working. Because of the boot loop problem I am reinstalling Spectrum through recovery to try and get out of that, then hopefully I will be able to flash back to Color OS if the boot loop stops.
Click to expand...
Click to collapse
Is it just the boot animation continuously playing? If so, this is when you need to turn off your phone and right as the screen goes off press and hold the volume + button. This will put you back in fastboot. Once you are there flash the TWRP recovery. After that hold the volume - and type fastboot reboot. This will boot you to TWRP recovery

EximusCode said:
Is it just the boot animation continuously playing? If so, this is when you need to turn off your phone and right as the screen goes off press and hold the volume + button. This will put you back in fastboot. Once you are there flash the TWRP recovery. After that hold the volume - and type fastboot reboot. This will boot you to TWRP recovery
Click to expand...
Click to collapse
All good, I erased data in recovery and now it's working. Now to flash back to Color OS in recovery.

W1F1 said:
All good, I erased data in recovery and now it's working. Now to flash back to Color OS in recovery.
Click to expand...
Click to collapse
Okay, good luck

strange... brick? (SOLVED)

Hello friends
I have a problem, to see if you can help me
I was installing a custom rom, and when I tried to install the twrp, I did not get it
ADB apparently performs the process well, but when trying to enter twrp, it enters the recovery stock
the problem is that I do not have an operating system or access to twrp, so I do not know how to recover the phone
by not having access to twrp, it does not help me HWOta or Huru Updater ...
I have access to bootloader and to the recoveries of huawei
before the disaster was in oreo
The bootloader is unlocked
any ideas?

You want to flash TWRP correct? Well first I want you to confirm me following things.
What recovery are you using. You need an Oreo Compatible TWRP. Try the one in Elemental ROM thread in Honor 6X Roms.
What command are you using. This is the most common mistake people make. Just a reminder the command to flash TWRP recovery on EMUI 8 is :-
fastboot flash recovery_ramdisk RECOVERY-V2.img
RECOVERY-V2.img is the name of TWRP you will download from above-mentioned thread.
Now if you are doing all of the above, and still no success, tell me what the Command Prompt says when you try to flash. After you flash try to manually boot into TWRP by holding Volume Up and Power. Luck.

Mannan Qamar said:
You want to flash TWRP correct? Well first I want you to confirm me following things.
What recovery are you using. You need an Oreo Compatible TWRP. Try the one in Elemental ROM thread in Honor 6X Roms.
What command are you using. This is the most common mistake people make. Just a reminder the command to flash TWRP recovery on EMUI 8 is :-
fastboot flash recovery_ramdisk RECOVERY-V2.img
RECOVERY-V2.img is the name of TWRP you will download from above-mentioned thread.
Now if you are doing all of the above, and still no success, tell me what the Command Prompt says when you try to flash. After you flash try to manually boot into TWRP by holding Volume Up and Power. Luck.
Click to expand...
Click to collapse
thanks for your reply
Yes, I know the commands, and it's even the same recovery, from KingOfMezi
as I comment, he performs the process well:
PS C: \ adb>. \ Fastboot flash recovery_ramdisk RECOVERY-V2.img
Sending 'recovery_ramdisk' (9100 KB)............................................. OKAY [0.328s]
Writing 'recovery_ramdisk'........................................................................ OKAY [0.125s]
Finished. Total time: 0.516s
PS C: \ adb>
but when starting the phone with power + vol+ (releasing power when vibrating and without releasing it, I tried both ways) starts the recovery stock
the most curious thing is that I had done it more times, and I never had any problem with that, in fact, the last thing I did was in the twrp

That's odd. Try to reboot after flashing TWRP. Once you flash it instead of manually booting into TWRP type
fastboot reboot
Now when the device shows device has been unlocked message press Volume up to enter erecovery. From there turn off phone and then boot into TWRP by holding Power and Volume Up. Keep holding it until you see your device is booting now... Screen.
Alternatively try to use dload to restore the system.

about dload I have a doubt.
Being debranded as l22 and having installed oreo, where do I get update.zip? of a ROM l22 oreo, or of the l21 that corresponds to my device?

Download L22 Oreo from Firmware Finder website or Windows App

solved use the bat of kingofmezi, Elementary Kernel + ramdisk.zip.
this made the recovery disappear (if you tried to access, a screen appeared similar to when we accessed fastboot, saying there is no recovery) and then flashed twrp correctly. thanks for your help

You are in Elemental v2. Do you mind if I ask for a review. Was it a complete flash or in complete. i.ewas the wallpaper when you first booted Blue&Black or Pink one.

Mannan Qamar said:
You are in Elemental v2. Do you mind if I ask for a review. Was it a complete flash or in complete. i.ewas the wallpaper when you first booted Blue&Black or Pink one.
Click to expand...
Click to collapse
unfortunately I could not prove it. when flashing the bat, I only managed to recover twrp, and then I was able to return to stock, I did not dare to try it again out of fear (I feel the delay, I could not enter before due to personal problems)

vicent76 said:
solved use the bat of kingofmezi, Elementary Kernel + ramdisk.zip.
this made the recovery disappear (if you tried to access, a screen appeared similar to when we accessed fastboot, saying there is no recovery) and then flashed twrp correctly. thanks for your help
Click to expand...
Click to collapse
Where can i find the elemental kerrnel+recovery.zip....I am not able to find it in official thread