Database Info

[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..

No fastboot, No recovery, No adb and LG Flash Tool also doesn't work!

Ok I've been spending my Saturday on this for 9 hours straight now. Damn!
It started with trying to clean install resurrection remix rom (I had lollipop RR but I wanted to clean install a new version). I went full retard and deleted everything then I had nothing to flash and I couldn't connect to device with adb from windows 10.
I went to linux and I could use adb there. I booted into recovery (TWRP 2.7) and sideloaded new RR rom. It started to work!
Then I went beyond full retarded and tried to upgrade the TWRP itself to 2.8.6 and I tried different things that didn't work except one that was an app that took care of it but then it could not boot normally.
I did some more idiotic things til I ended up with a brick that the only way I could feel some communication with it (!) was with Download mode (press vol +) in DemiGod Crash Handler and LG flash tools!
Nothing else works (no adb, no fastboot, no recovery). It gives secure booting error (boot certificate verify) when it tries to boot (or into recovery) and gives Critical Error that I can either reboot or go to Dload mode!
By the way from the beginning I couldn't use fastboot!
also LG flash tools give model information check fail error!
I remember some weird stuff like using dd to copy some image partitions (I didn't have fastboot). I also remember doing rm -rf * somewhere =)) and a lot of playing around with TWRP!
I would really appreciate some help getting out of this mess!

_Rooz_ said:
Ok I've been spending my Saturday on this for 9 hours straight now. Damn!
It started with trying to clean install resurrection remix rom (I had lollipop RR but I wanted to clean install a new version). I went full retard and deleted everything then I had nothing to flash and I couldn't connect to device with adb from windows 10.
I went to linux and I could use adb there. I booted into recovery (TWRP 2.7) and sideloaded new RR rom. It started to work!
Then I went beyond full retarded and tried to upgrade the TWRP itself to 2.8.6 and I tried different things that didn't work except one that was an app that took care of it but then it could not boot normally.
I did some more idiotic things til I ended up with a brick that the only way I could feel some communication with it (!) was with Download mode (press vol +) in DemiGod Crash Handler and LG flash tools!
Nothing else works (no adb, no fastboot, no recovery). It gives secure booting error (boot certificate verify) when it tries to boot (or into recovery) and gives Critical Error that I can either reboot or go to Dload mode!
By the way from the beginning I couldn't use fastboot!
also LG flash tools give model information check fail error!
I remember some weird stuff like using dd to copy some image partitions (I didn't have fastboot). I also remember doing rm -rf * somewhere =)) and a lot of playing around with TWRP!
I would really appreciate some help getting out of this mess!
Click to expand...
Click to collapse
This will help with flash tool
http://forum.xda-developers.com/showthread.php?p=56961336
Sent from my LGLS991 using Tapatalk

Swetnes said:
This will help with flash tool
http://forum.xda-developers.com/showthread.php?p=56961336
Sent from my LGLS991 using Tapatalk
Click to expand...
Click to collapse
Thanks I think I made some progress but it is not working yet!
Instead of changing to D800, I zeroed out the bytes corresponding to number (because I was getting error CrossDL [] to [D800]) and it moved one step forward!
Now it stops at "Change to DL mode" (can't change to download mode - 00000064).
It may be related that it can't read PID and IMEI off my phone!
Also that refurbish term might need some attention (I got it from ebay but I don't recall anything saying it is refurbished and it was an att seller emptying their stock of g2s).
Again, I don't (can't) go to Dload mode by pressing volume up and plugging in. A critical error page comes up when I turn on the phone that has 2 options: vol+ for Dload and vol- for reboot.
That's all I can think of as of now!
Froms the log file:
[ 1:23:21] SubProcess Name : DiagDload
[ 1:23:21] [T000003] 00 00 7E ...
[ 1:23:21] [T000004] 3A A1 6E 7E :.n.
[ 1:23:26] Response packet time out 5000 milisec
[ 1:23:26] CBasicCom::SendRecvPacket, PACKET_ERROR code = 1460 Msg => This operation returned because the timeout period expired.
[ 1:23:26] Error! CCmdProcess::ExecuteCommand() �� SendRecvPacket()
[ 1:23:26] Can't change to download mode
[ 1:23:26] RefurbishProcess() Error.
[ 1:23:26] �ڡ� ERROR REASON : LAF_ERROR_CHANGE_DLOAD_F
[ 1:23:26] CComPort::ClosePort, Closed Port Successfully for COM 41
[ 1:23:26] CBasicComControl::Close, the port(COM41) is closed successfully
[ 1:23:26] RunProcess() is fail.
[ 1:23:26] CBasicComControl::IsConnected, the port(COM41) connection is not detected
[ 1:23:26] [ 1:23:26] Can't change to download mode
[ 1:23:26] DoDownload() Exception
Click to expand...
Click to collapse

Fastboot no Recovery Flash

655/5000
Hello everybody,
I have a small or big problem.
I wanted to flash a new ROM. Unfortunately, I can not flash the TWRP.
Each time:
PHP:
C: \ Users \ Marcel \ Downloads \ adb 1.0.36 and fastboot> fastboot flash recovery twrp-3.1.1-0-frd.img
Target reported max download size of 471859200 bytes
Sending 'recovery' (25184 KB) ...
OK [0.544s]
Writing 'recovery' ...
FAILED (remote: Command not allowed)
finished. Total time: 0.557s
In Fastboot mode, PHONE is unlocked (in red) and FRP lock (in green). Does the FRP have anything to do with it?
Since then I can not use the Honor Recovery. He wants to download something, but that does not work.
Also with the "dload" upgrade he makes a rebootart and the Screen " YOur devices is booting now..."
Can anyone give me a hint?

It's the FRP lock. Delete all the Google accounts on your phone, that should free up the FRP lock and let you flash recovery.

Hello,
Thank you very much. About settings I could disable the FRP.
FRP and Phone ist UNLOCK.
TWRP I can copy. About the one Huawei multitool I came 1 time in the recovery mode. There I made a wipe. The installation of the new Custom Rome did not work (Error Code 7).
Now I'm only in the fastboot mode. In the TWRP I come no more pure.
The mobile phone is constantly running again.
It is not recognized in the Huawei Multitool. From the console (cmd) I can use fastboot mode.
How can I save it?

I've never used the multitool, so I can't help you there. I always flash directly from ADB.

Via the cmd I can copy the recovery (twrp). But if I want to restart the devices, the twrp does not start. Therefore, I try the tool.
It is very annoying that you can not just start the twrp.
Also delete or copy system, boot, etc is not (FAILED (remote: Command not allowed))

Use the button combo to get into TWRP. Power the device off, then hold down Power + Vol Up. When you feel the short vibrate, let go of power, keep holding Vol Up. It should boot you into TWRP.

many thanks for the help. Apparently I must be too stupid for it.
I have only 2 options.
1. Volume down (-) with power to fastboot mode.
2. Volume high (+) (the topmost pressure point (head)) with power. Here I get into the overview:
Your devices has been unlocked and can't be trusted.
(1) Presspower key to continue
(2) Press VOlumen Up key to 2 Secondary to restore your device.
(3) Your devices will continue to boot 5 seconds later if there is no operation
No matter how, it always stands YOur devices is booting now ...
After a few minutes he makes a reboot
EDIT: After I have done the Unbrick with the tool, the mobile phone starts again. But if I install TWRP or get to use, then it is only version 3.0.2.0

Nexus 5 won't boot after flashing the device

Hello,
I formerly posted my question on Google forum (productforums.google.com/forum/#!topic/nexus/nIG4E-uAbMc) .
However, they forwarded me to this forum for this kind of question.
I tried to flash my Nexus5 (hammerhead) device from a Linux system. The battery was full when I started the operation.
I followed the official described procedure: developers.google.com/android/images
1) I enabled developper options
2) I rebooted on the bootloader
3) I unlocked the flashing option with #fastboot flashing unlock
4) I unlocked oem with #fastboot oem unlock
5) I downloaded 6.0.1 (MMB29K) image from the same above link
6) I unzipped the downloaded file. From this unzipped folder I ran the "flash-all.sh" script.
6.1) Sending 'bootloader' went OKAY
6.2) Writing 'bootloader' went OKAY
6.3) Rebooting into bootloader went OKAY (FINISHED output)
Then the phone shutdown and did not booted after this operation.
I waited for long time for the phone to boot, however it never happened.
I tried the usual tricks to force the phone to boot, but it did not worked so far
1) Power push for 30s
2) Volume up + Power push for 30s
3) Volume up + Volume down + Power push for 30s
I have 2 questions:
1) Do you know what happened during the flashing procedure (the fastboot command seemed to run well given the outputs) and why it does not boot anymore ?
2) How can I fix the phone ? What procedure should I follow ?
Thank you in advance for your help

Pixel 2 = brick? FASTBOOT + ADB not helping. How do I clear files so can get repair?

I have a Pixel 2 which overnight stopped working - my guess is that it rebooted due to an automated software update.
I now only get the page with the robot on it's back.
Options in green on this page are Barcodes, Power Off, and Start.
After reading a lot online I've tried all the usual key press combinations to no avail.
I've also downloaded ADB and FASTBOOT to my Mac.
ADB doesn't see the phone when plugged in via USB (ie. ADB DEVICES doesn't return anything)
FASTBOOT DEVICES does, however, show the serial number as listed on the page with the robot on it's back (and the -l option adds "usb:" plus an 8 digit number and the letter "X"
FASTBOOT REBOOT restarts the phone and brings me back to the robot on it's back page.
Other information on the Robot on it's back page include -
Product Revision: walleye MP1
Boot-slot: b
Console: DISABLED
Secure Boot: yes (PRODUCTION)
Device State: locked
Advice online suggests I need to unlock the phone, so I've tried FASTBOOT FLASHING UNLOCK, and FASTBOOT OEM UNLOCK but neither work.
When I try these I get "FAILED (remote: Flashing Unlock is not allowed)"
An article on Android Police suggests this may have been a bug on the Pixel 2 originally and that it's now resolved?
Unfortunately, my cat 22 situation seems to be that I need to do a factory reset, but the steps I've found as to how to do a factory reset all lead back to the Robot on it's back page, so I can't see how to move forward to with recovering my phone?
Can anyone help please?
Really frustrated that my new phone can put itself into this state without me having done anything and that it's seemingly impossible to recover from this state now that it's in it.
At very least I'd like to wipe all data from the phone so I can send it off for repair.
Thanks in advance.

Unfortunately, I can't describe a situation to get around this because the bootloader is still locked -- you'll probably want to unlock the bootloader and then leave it unlocked permanently if flashing the images using this method on a regular basis... I have personal notes that I've written for two scenarios. (1) is to gain root from stock and directions (2) is to flash the latest Android image and retain the data... Perhaps try the bottom block of steps (re-installing the factory image) --- but also unlock the bootloader from the top block of steps:
=======================
Code:
ROOT FROM STOCK
0.5 - Download the following
Magisk-v16.7-1674.zip -- https://transfer.sh/YVFdi/Magisk-v16.7-1674-.zip
twrp-pixel2-installer-walleye-3.2.3-0.zip -- https://dl.twrp.me/walleye/
twrp-3.2.3-0-walleye.img -- https://dl.twrp.me/walleye/
1.0 - On phone: Settings > System > About Phone > tap on the 'build number' seven times.
2.0 - The Developer Options will now be visible in the main settings page. Enter it and turn on USB debugging and OEM unlocking
3.0 - Reboot into 'bootloader' and unlock bootloader (this will factory reset phone)
# adb reboot bootloader
# fastboot oem unlock
4.0 - Download 'twrp-3.2.3-0-walleye.img' to Desktop. Rename the File to 'pixeltwrp.img' (Not necessary to rename -- just did; https://dl.twrp.me/walleye/)
5.0 - Now boot your phone in bootloader mode. Turn off phone and Hold the Volume Down + Power, then release Power button or...
# adb reboot bootloader
6.0 - Run the following command
# fastboot boot ~/Desktop/pixeltwrp.img
7.0 - Phone will boot in the TWRP mode. Push 'twrp-pixel2-installer-walleye-3.2.3-0.zip' and 'Magisk-v16.7-1674.zip' to the phone's /data/ directory
# adb push ~/Downloads/twrp-pixel2-installer-walleye-3.2.3-0.zip /data/
# adb push ~/Downloads/Magisk-v16.7-1674.zip /data/
8.0 - Tap on 'Install' and flash 'twrp-pixel2-installer-walleye-3.2.3-0.zip' and 'Magisk-v16.7-1674.zip' files
9.0 - Reboot Phone
10.0 - Install busybox on /system/bin
UPDATE IMAGE TO LATEST WITHOUT WIPING PHONE
0.5 - Download the following
Magisk-v16.7-1674.zip -- https://transfer.sh/YVFdi/Magisk-v16.7-1674-.zip
twrp-pixel2-installer-walleye-3.2.3-0.zip -- https://dl.twrp.me/walleye/
twrp-3.2.3-0-walleye.img -- https://dl.twrp.me/walleye/
1.0 - Remove "PIN UNLOCK" for security reasons
2.0 - Download the latest factory image from https://developers.google.com/android/images#walleye
3.0 - Unzip the factory image's ZIP and remove '-w' from "flash-all.sh"
4.0 - Reboot to bootloader
# adb reboot bootloader
5.0 - Flash image
# ./flash-all.sh
6.0 - Re-install magisk (https://dl.twrp.me/walleye/)
# adb reboot bootloader
# fastboot boot ~/Desktop/pixeltwrp.img
7.0 - Tap on 'Install' and flash 'twrp-pixel2-installer-walleye-3.2.3-0.zip' and 'Magisk-v16.7-1674.zip' files (located on /data/) - If installing a new magisk version, run the magisk uninstaller first '/data/Magisk-uninstaller-20180719.zip'
7.1 - Wipe Dalvik/Cache and reboot
7.2 - Install MagiskManager and TWRP Manager if not installed
7.3 - Go to bootloader and flash kernel 'flashkernel-wahoo-v3.01.zip'
8.0 - Reboot phone
9.0 - Install busybox on /system/bin
10.0 - Re-add security unlock
=======================
...If these options don't work then the last thing I can think is to attempt to boot into the 'pixeltwrp.img' and switch the the primary slot (from Slot B to Slot A) and try to reboot.

Thanks @armordillo for your reply. I'm not planning on doing anything like this regularly - just trying to get my phone to boot or get the files off it so I can send it for repair.
Sadly I can't execute step 1 in either of your proposed processes - I literally can't get past the screen with the upturned robot
I can't turn on USB debugging, and I can't run OEM UNLOCK.
I'm completely stuck.

Can you get into the stock recovery?
On the screen with Andy in his back use the volume keys to scroll till you see Recovery Mode (or something similar) then hit the power button. At this point you should get another dead Andy. Press and hold Power button and then press the Volume UP button once. That should take you to the stock recovery. There will be a bunch of text with options for clearing cache adb sideload and other things.
Sent from my Pixel 2 using Tapatalk

Sadly not.
That option (Recovery mode) is in red and so are 'restart bootloader' and 'download mode' - when I choose any of these by pressing the power button to select, the phone screen goes black for 2 seconds and then the robot on his back image comes back on.
The power button and up volume combination takes me back to the same screen also.

I'm not sure it works on the pixel 2 but you can try changing to boot with slot a using the command:
fastboot --set-active=a
domonicwhite said:
Sadly not.
That option (Recovery mode) is in red and so are 'restart bootloader' and 'download mode' - when I choose any of these by pressing the power button to select, the phone screen goes black for 2 seconds and then the robot on his back image comes back on.
The power button and up volume combination takes me back to the same screen also.
Click to expand...
Click to collapse
Sent from my Pixel 2 using Tapatalk

It says I can't do that because it's locked.
PiousInquisitor said:
I'm not sure it works on the pixel 2 but you can try changing to boot with slot a using the command:
fastboot --set-active=a
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse

You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk

Thanks!
I don't mind not accessing my files - I'd be happy if I could just delete them.
I'm non technical and not familiar with TWRP but I'll do some searching and see what I can learn.
Based on an earlier post I'm guessing I need to download TWRP first? Or is that a part of FASTBOOT?
When you say version.img - I'm assuming that's also something I need to download?
Sorry for the newb questions (I literally just want my phone back)
Thanks again.
PiousInquisitor said:
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse

domonicwhite said:
Thanks!
Based on an earlier post I'm guessing I need to download TWRP first? Or is that a part of FASTBOOT?
When you say version.img - I'm assuming that's also something I need to download?
Click to expand...
Click to collapse
Yes, you'll need to download TWRP from https://dl.twrp.me/walleye/twrp-pixel2-installer-walleye-3.2.3-0.zip.html
To help clarify what PiousInquisitor was saying about the version.img is that you'd have to type in the version of TWRP, that I've linked to, in that particular command.

Thank you! Does it matter that I'm using a Mac / OSX?
SargeStryker said:
Yes, you'll need to download TWRP from https://dl.twrp.me/walleye/twrp-pixel2-installer-walleye-3.2.3-0.zip.html
To help clarify what PiousInquisitor was saying about the version.img is that you'd have to type in the version of TWRP, that I've linked to, in that particular command.
Click to expand...
Click to collapse

domonicwhite said:
Thank you! Does it matter that I'm using a Mac / OSX?
Click to expand...
Click to collapse
I'm pretty sure that it doesn't matter.

What they're describing, @domonicwhite , is my steps 4-6 in the first block. Skip to that and see if you can perform it. You will need to have adb/fastboot installed on your MacBook.

Sadly it won't let me do this in the locked state (assuming I did everything correctly).
Any further suggestions?
--
Last login: Tue Aug 21 09:45:09 on ttys001
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot
Rebooting
Finished. Total time: 0.001s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot boot /Users/domonicwhite/Desktop/pixeltwrp.img.img
Downloading 'boot.img' OKAY [ 0.814s]
booting FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 0.832s
--
PiousInquisitor said:
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse

Sadly it won't let me do this in the locked state (assuming I did everything correctly).
Any further suggestions?
--
Last login: Tue Aug 21 09:45:09 on ttys001
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot bootloader
* daemon not running; starting now at tcp:5037
* daemon started successfully
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ adb reboot
error: no devices/emulators found
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot
Rebooting
Finished. Total time: 0.001s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot reboot bootloader
rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Domonics-MacBook-Pro:~ domonicwhite$ fastboot boot /Users/domonicwhite/Desktop/pixeltwrp.img.img
Downloading 'boot.img' OKAY [ 0.814s]
booting FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 0.832s
--
PiousInquisitor said:
You can try booting twrp. But if you had some form of security (pin/password) you probably won't be able to decrypt and access your files.
You probably won't even be able to boot twrp. It's worth a shot though.
fastboot boot twrp<version>.img
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
armordillo said:
What they're describing, @domonicwhite , is my steps 4-6 in the first block. Skip to that and see if you can perform it. You will need to have adb/fastboot installed on your MacBook.
Click to expand...
Click to collapse

Computer says no
It won't let me do this in the locked state -
Domonics-MacBook-Pro:~ domonicwhite$ fastboot boot /Users/domonicwhite/Desktop/pixeltwrp.img.img
Downloading 'boot.img' OKAY [ 0.814s]
booting FAILED (remote: Operation is not allowed in Lock State)
Finished. Total time: 0.832s
armordillo said:
What they're describing, @domonicwhite , is my steps 4-6 in the first block. Skip to that and see if you can perform it. You will need to have adb/fastboot installed on your MacBook.
Click to expand...
Click to collapse

And doing one or both of these don't work from the bootloader either?
# fastboot oem unlock
# fastboot flashing unlock

In red? The color doesn't matter you can still choose recovery. Then hold power for a second and press up. You can the ADB sideload an OTA zip.
I'm pretty sure mine is red too, but it still let's me choose it

Did you accidently reset the bootloader lock after tinkering with your phone? that can cause this, my kid did it to my other phone after i had it messed with. so it was erroring out. nothing you can do but call your company see if you can exchange it for *faulty udate*
since your phone is *locked* just say you tried updating the software, and it reset the phoen to this. phones still locked so you have a shot at exchange..
they exchanged my *faulty update* for a new one. actually recieved it 5 days after making the request. before i had even sent the non working one back.

Sorry I didn't read where you said that it leads back to fastboot. I had to do an RMA due to this because I didn't unlock the bootloader. I then received a phone that cannot be bootloader unlocked (apparently all refurb phones can't). Horrible situation really and probably going to result in me never buying another pixel.