Database Users

Locked Boot loader, Encrypted Device, BootLoop, No Recovery/ Factor. HELP

So the title pretty much says it all..
I have a Nexus 6P
Last night It got stuck in a bootloop. The only access I have to the device is it will launch into the boot loader. But no options work, factory, recovery do not work. USB Debugging was turned off, OEM unlock is turned off, developer options are on. But I have zero access to the android only the boot loader screen. Fastboot does work but it gives me "DEVICE IS LOCKED" on most commands. Oh and the icing on top is I'm on Android N 7.0 beta.
I've ordered a replacement, but I have all my personal data on the phone. I'd like to either fix it and get it working so I can get all my stuff off it. Or at very least try to wipe the device.
Also Fastboot Format, erase, do not work. It says Locked Device. HELP PLEASE. I can answer any more questions.

can you adb pull and push files?
If so, on your Windows machine, type this:
Code:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys

It won't connect via ADB only Fastboot.
adb devices
List of devices attached
Wiltron said:
can you adb pull and push files?
If so, on your Windows machine, type this:
Code:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
Click to expand...
Click to collapse

Not sure if this will work, but try downloading the latest TWRP img file from their website, then running this command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
If you get it into recovery, then pull the files you need for a backup, and then use adb push to push a new ROM to the device.
Make sure you format all partitions/data.
Note: adb push should work better in recovery, vs. the command line that didn't work earlier.

What do you mean by "recovery doesn't work"? Please explain what happens when you boot into it.
Sent from my Nexus 5X using Tapatalk

an276123 said:
It won't connect via ADB only Fastboot.
adb devices
List of devices attached
Click to expand...
Click to collapse
Why not download stock Marshmallow and attempt to flash?
https://developers.google.com/android/nexus/images#angler
A locked bootloader should still allow you to flash a signed ROM.
An unlocked bootloader means you can boot and install anything.
Rule #1 If you are running *ANYTHING* other than an OTA, unlock the bootloader!
Unlocking the bootloader DOES NOT void the warranty.
Final note, it's encrypted. If you can't get into it, nobody interested in your data can.
Even if they can, it's block level encrypted. Who cares, no need to wipe.

SlimSnoopOS said:
What do you mean by "recovery doesn't work"? Please explain what happens when you boot into it.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
When I click down and then power on recovery it should go into the recovery. But instead it just gets back into an endless loop of starting.

tech_head said:
Why not download stock Marshmallow and attempt to flash?
https://developers.google.com/android/nexus/images#angler
A locked bootloader should still allow you to flash a signed ROM.
An unlocked bootloader means you can boot and install anything.
Rule #1 If you are running *ANYTHING* other than an OTA, unlock the bootloader!
Unlocking the bootloader DOES NOT void the warranty.
Final note, it's encrypted. If you can't get into it, nobody interested in your data can.
Even if they can, it's block level encrypted. Who cares, no need to wipe.
Click to expand...
Click to collapse
On a side note. I am running stock android N 7.0 and it was OTA. I just didn't think to unlock it since it was all done OTA.
Thats what I'm thinking too on the data.

Wiltron said:
Not sure if this will work, but try downloading the latest TWRP img file from their website, then running this command:
Code:
fastboot -c "lge.kcal=0|0|0|x" boot customrecovery.img
If you get it into recovery, then pull the files you need for a backup, and then use adb push to push a new ROM to the device.
Make sure you format all partitions/data.
Note: adb push should work better in recovery, vs. the command line that didn't work earlier.
Click to expand...
Click to collapse
When I try to run this I get this.
downloading 'boot.img'...
OKAY [ 0.397s]
booting...
FAILED (remote: unlock device to use this command)
finished. total time 0.421s

That means you need to unlock your bootloader, which should already be done, or if it's not, it will erase your internal storage.
You can unlock your bootloader, or try too, with
Code:
fastboot flashing unlock

Wiltron said:
That means you need to unlock your bootloader, which should already be done, or if it's not, it will erase your internal storage.
You can unlock your bootloader, or try too, with
Code:
fastboot flashing unlock
Click to expand...
Click to collapse
He said OEM unlock is turned off so that won't work.

So any luck to boot this sucker ? Don't even have stock recovery ..

have you tried "fastboot boot boot.img" from the correct factory image ?

Boot loop plus no recovery equals BLOD. Sorry but likely you are done.

Wiley Fox Swift2+ Bootloader Unlock

It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is no longer available - seek out the LineageOS rom instead

I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.

Swift 2 Plus and SuperSU
FelixPiers said:
I unlocked my bootloader the other day and those are the same steps I did so I can confirm this works.
I then proceeded to root the phone with SuperSU 2.78. Worked a treat.
Click to expand...
Click to collapse
Yes initially the only version of SuperSU I could find was v2.46, which kept failing.

Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.

thejackle123 said:
Any help? My reboot menu doesn't have a fastboot option. Yes I have advanced reboot and oem unlocking enabled.
Edit: Sorted it. Turns out you have to reboot into the bootloader.
Click to expand...
Click to collapse
Is it too hard to google your question?
Works on most devices:
1) Turn off device
2) Hold VOLUME UP button
3) Connect device to PC via usb-cable

I installed SuperSU, before that I installed TWRP. Now I am unable to install the latest update "cm-marmite-a1478a0ee9-to-7aa1c797975e-signed"
When I download this update and perform the actual install, it gives an error. Restarting the phone via TWRP recovery gives the same error. I am getting "Error 7"
So no I want to revert back, to get rid off SuperSU and TWRP to install all updates and then later root the device with TWRP and SuperSU. How do I get the original state of the phone back?
Or do you have any advice how to get the latest update installed?
Thx.

SMessy said:
It seems that unlocking the BootLoader on the WileyFox Swift2+ is even easier.
To unlock the boot loader (WARNING!!! This wipes your user data!!!)
Go To 'Settings - About Phone' Tap 'Build Number' seven times to enable 'Developer Options'.
Go To 'Developer Options' Enable 'Advanced Reboot', Enable 'OEM Unlocking'
...## not sure if these next few steps are even needed!!
Connect to computer running "Minimal ADB and Fastboot"
Open command window as administrator (To prevent Win10 messing around).
Enter command "fastboot oem unlock"
...##
Press the phone 'Power Off - Reboot - FastBoot'
PC detects device and states "Follow instructions on device screen"
Phone screen issues dire warnings about unlocking Bootloader.
Proceed and job done Bootloader is Unlocked (device at this point not rooted).
The stock Swift2+ Cyanogen Rom is here
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip
Click to expand...
Click to collapse
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll

Rom location
RayfG said:
Hi, mate
unfortunately teh link to the stock rom is not working.
Can u provide me with another working link?
I deleted my rom and i can't find the stock to reanimate my phone.....
EDIT!!!!
All done, device is restored
THy @ll
Click to expand...
Click to collapse
Just to confirm the stock room is still at this location as at 2nd march 2017
http://builds.cyngn.com/factory/marmite/cm-13.1.4-ZNH2KAS5RM-marmite-signed-fastboot-c64f8f5d87.zip

"Just to confirm the stock ROM is still at this location as at 2nd march 2017 :"
Link above does not work now, however below one does.
https://androidfilehost.com/?w=files&flid=126553

Hmmm. I'm going to try again. Before I got fastboot in red and Dvice Status: Locked. But I'll try again, see where I get.
Image of issue: https://ibb.co/jfLPye
edit: Updating to the latest Oreo update (8.1 I think)
---------- Post added at 08:34 AM ---------- Previous post was at 08:14 AM ----------
ohhhhhhh, I had to turn the phone off while connected, already running "adb & fastboot" (not just adb) then (phone connected in USB debugging mode) turn off the phone and hold volume up (no need to hole the power key as connected and I got the option to unlock with a warning that I may void the warranty. Then my phone encrypted/re-encrypted itself (I think it was already encrypted).
Now to flash TWRP (3.2 I think) and flash a custom ROM (Lineage 15.1 / 8.1 Oreo) Not sure if I should root or not. And if I do, should I root before installing 8.1?

got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)

Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?

bl91 said:
Hi, trying to unlock my S2+ bootloader with Ubuntu MATE. Have completed all the steps listed, entered fastboot oem unlock into the terminal which now just sits there displaying < waiting for any device >
Any idea where I go from here?
Click to expand...
Click to collapse
your device isn't picked up by fastboot ...first of all install the very latest version of adb ...using the usual Ubuntu story
sudo apt-get install adb
sudo apt-get upgrade
sudo apt-get update
sudo reboot
then switch on your device
go to /settings/about/buildnumber
click until developer settings are enabled
go to developer settings
toggle oem unlock to on
toggle adb to on
WITHOUT SWITCHING OFF
connect device to pc/laptop with original orange wileyfox cable
now your Ubuntu machine
must install drivers and Mount the phone so it should appear as a mounted volume on desktop
now open a terminal
now run the following :
sudo adb
sudo adb devices
now look on your phone and pull down the notification shadse ..make sure you have adb connected and file transfer mode ..if not change from charge to file transfer ...
there should be a pop up window on phone screen asking for permission for adb ..select allways allow and give pernission / authorization ..
now in terminal run adb devices and it should return some value as connected device
run:
adb reboot bootloader
phone will reboot to bootloader
run:
fastboot oem unlock
*use volume up to select yes
**beware will erase DATA ...
***if it doesn't work and adb and fastboot doesn't detect your device it is a driver problem but i haven't used Ubuntu in ages so can't remember steps to update your drivers other than updating the whole adb package
****some ubuntu instructions might be a little off as I've explained previously it's been a while
*****your waiting for device means
-adb service didn't start
+try "sudo adb"
-adb drivers out of date
+try sudo apt-get update
-adb on device not toggled to on
+toggle adb in dev settings
*adb authorization not given **should still see unauthorized device
-bad usb cable
+try another usb cable
-bad usb port
+try a different usb port
_____for clarity double check Ubuntu adb instructions and commands but this should put you on the right track____
---------- Post added at 08:30 AM ---------- Previous post was at 08:19 AM ----------
reggiexp said:
got damit i never understand how to flash twrp i followed what google said.
fastboot flash recovery XXX.img it does its thing i reboot still no recovery im on stock cm12 ? i think or cm13 android 6.0)
Click to expand...
Click to collapse
don't reboot immediately ..stock recovery will be flashed back over twrp
*i assume you know how to get to fastboot
adb reboot bootloader
fastboot oem unlock
*volume up for yes
fastboot flash recovery recovery.img
*make sure you have a copy of twrp called recovery.img in adb folder
when it says sending...
then is says writing ...
then it says done
DON'T REBOOT
UNPLUG USB
***MANUALLY BOOT TO BOOTLOADER USING VOLUME UP AND POWER
**** IN BOOTLOADER SELECT "RECOVERY"
you should then just wait on wileyfox first time it takes a minute or two don't know why then
it should boot to twrp
***you can take stock boot.img and patch it with magisk
-use: fastboot flash boot boot.img
-then you will have magisk and rooted
-using twrp apk or something like root rasher or flasher ..give apk root permission
-download twrp ..flash with apk from inside system ..after flashing select yes to reboot directly to recovery

Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now

bl91 said:
Thanks very much, I've unlocked my bootloader now! Onto the TWRP, Magisk and LineageOS business now
Click to expand...
Click to collapse
okay no problem
*i know everybody likes lineage and its usually more stable and the base for many custom roms
however just my 2cents worth ...i tried all the roms for our device ..but the by far the best for me was following the tutorial on how to make our device treble compatible ..
Then ...after 3-4 months of trying different treble GSI's i have stopped on Viper Official Pie 64bit A-only treble system.img ... at least give it a try after trying out lineageOs ..
you might thank me .

I can't get my device to show up usb debugging is on, Advanced Reboot', 'OEM Unlocking' etc. I've been trying for hours and hours. It shows up to transfer files if I want that mode so my PC is recognising it, but it doesn't seem to have drivers for adb. I've tried installing google usb drivers and also this: https://afterthoughtsoftware.com/posts/using-adb-with-wileyfox-swift
sorry if I haven't explained clearly, I'm just so sleepy from going around in circles. :|
I've rooted phones before and never had this issue. please can anybody help?
edit: have fixed I think! did two things at once so not sure which. I revoked usb devices so that my computer would have to ask permission again to connect (or something like this) and also clicked a thing on my PC to allow it to update what I think said driver icons automatically, which I wouldn't have thought would help, but it seemed to find the adb driver this time. I'd probably make more sense if it weren't 1am. :|

When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.

My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
RavZ75 said:
When i got my Swift 2 X, it came updated with 8.1 Oreo out of the box and the issue I had was unlocking the bootloader.
Sure fastboot oem unlock unlocked so I could flash recovery and roms but whenever I tried flashing a bootloader via fastboot, it gave me "FAILED (remote: Critical partition flashing is not allowed)". So that part was still locked.
This I fixed way back after searching around on my own about it but since the solution to this aint mentioned around here and I can't be the only one who have encountered this I think, I am just gonna add it in here.
There are now other commands to unlock your device, fastboot flashing unlock that does the exact same thing that fastboot oem unlock does and fastboot flashing unlock_critical is the command that unlocks the bootloader.
Both commands prompts you with the usual to confirm unlock and wipes your data.
It doesn't matter if you already unlocked the device with the oem command or flashing command, fastboot flashing unlock_critical should be able to unlock the bootloader either way.
Click to expand...
Click to collapse

bubba_66 said:
My swift was also at 8.1 I had no problem unlocking the bootloader.
DH
Click to expand...
Click to collapse
Doesn't seem that many who have this lock on their bootloaders, the only ones I could find here who had locked bootloaders the same way as I had are in the LineageOS 14.1 thread.
So at least I am not alone with that but sure makes me wonder how it is so for some while others not.

After unlock bootloader Everytime reboot always like this https://ibb.co/NSZR818

Downgrade Orea beta to Nougat

Orea beta is great but battery drain so much.
for 30 min of screen use it used 11%, is it normal ?
and I am looking to go back to Nougat, could any one please tell me how can I go back.
Thank you.

are this instructions for downgrading ?
Set up your computer for flashing
Download the fastboot tool from the Android SDK Platform-Tools package
Add it to your path so the flash scripts can find it
Connect your Essential phone to your computer with a USB cable
Enable unlocking
Before you can flash a new image, ensure Developer options are enabled and OEM unlocking is turned on. To do this:
Tap Settings, then tap System > About phone
Scroll to the bottom of the page, then tap Build number multiple times until you see the pop-up message “You are now a developer” (It usually takes seven taps)
Go back one screen to System, then tap Developer options
Find the option: OEM Unlocking and turn it on
Fastboot mode
Put your Essential Phone into fastboot mode by doing either of the following:
Use the ADB tool packaged above to run the command: adb reboot bootloader
Reboot your phone while holding the Volume-down button
Unlock your bootloader
NOTE: Installing the factory image will erase all information from your device. So remember to backup your phone before continuing.
Run the command: fastboot flashing unlock
Press the Volume-down button to navigate to the YES option, then press the Power button to confirm
Flash your factory image
Download the factory image to your computer
Unzip the downloaded file
Go to where you unzipped the images
For Linux / Mac OS X - Run the command: flashall.sh
For Windows - Run the command: flashall.bat
https://forum.xda-developers.com/essential-phone/help

Yup those are them, I just did it yesterday.
Just an FYI, I found that putting Oreo on the phone resulted in ADB not working 100% anymore, such as attempting to reboot into recovery/etc. It would just reboot back into the O.S..
Here is what I did.
- download the current release you want to flash. (e.g. NMJ32F), then unzip it into a new folder.
- on your phone, verify that USB debugging and OEM unlocking are turned on in the developers menu.
- reboot your phone into the fastboot mode (power and volume down buttons)
- from your adb command line: type: fastboot flashing unlock
- This will make your phone show a new screen asking if you want to unlock the bootloader. Use the volume down to select YES, and hit the power button. It will now reboot and erase the phone. It will eventually end up booting up too request you setup the phone. (that is what it did for me.)
- reboot the phone back into the fastboot mode (power and volume down buttons)
- you should now see the bootloader listed as unlocked (vs locked)
- from your adb command line: type: fastboot devices (which should show your phones serial number and fastboot next too it.
- on your computer, using the command line, go to the unzipped folder of the NMJ32F build you downloaded
- in the folder there is a batch file you will run called flashall.bat. run it
- your phone will start flashing the NMJ32F build
- when it completes it will reboot a couple of times, erase the phone, and end up at the "lets get started" screen.
- reboot the phone back to the fastboot mode
- from your adb command line: type: fastboot flashing lock
- select the option to lock your bootloader. The phone will reboot/erase I believe, and then end up back to the "lets get started" screen.
- after you setup your phone, you can go back into the developers menu to turn off the oem unlocking
The above steps pretty much follow essentials instructions. (the essential instructions don't give some specifics.)
You are all done. (I recommend you review my instructions and the essential instructions carefully, don't copy paste commands as I may have spelled something wrong, etc.. Just wanted to give you a flow of the process.)
vjyrdy said:
are this instructions for downgrading ?
Set up your computer for flashing
Download the fastboot tool from the Android SDK Platform-Tools package
Add it to your path so the flash scripts can find it
Connect your Essential phone to your computer with a USB cable
Enable unlocking
Before you can flash a new image, ensure Developer options are enabled and OEM unlocking is turned on. To do this:
Tap Settings, then tap System > About phone
Scroll to the bottom of the page, then tap Build number multiple times until you see the pop-up message “You are now a developer” (It usually takes seven taps)
Go back one screen to System, then tap Developer options
Find the option: OEM Unlocking and turn it on
Fastboot mode
Put your Essential Phone into fastboot mode by doing either of the following:
Use the ADB tool packaged above to run the command: adb reboot bootloader
Reboot your phone while holding the Volume-down button
Unlock your bootloader
NOTE: Installing the factory image will erase all information from your device. So remember to backup your phone before continuing.
Run the command: fastboot flashing unlock
Press the Volume-down button to navigate to the YES option, then press the Power button to confirm
Flash your factory image
Download the factory image to your computer
Unzip the downloaded file
Go to where you unzipped the images
For Linux / Mac OS X - Run the command: flashall.sh
For Windows - Run the command: flashall.bat
https://forum.xda-developers.com/essential-phone/help
Click to expand...
Click to collapse

I cannot get past the flashall.sh command, says permission denied everytime. I am able to execute every command to that point with out any issues. I have downloaded the latest android platform tools, and my mac is on the latest version of macOS . I have also tried to flash every single image that is available on the essential dev webpage. Any ideas would be awesome, is in possible to side load using the adb commands from the recovery menu and avoid the fastboot mode all together.

swagglepuff said:
I cannot get past the flashall.sh command, says permission denied everytime. I am able to execute every command to that point with out any issues. I have downloaded the latest android platform tools, and my mac is on the latest version of macOS . I have also tried to flash every single image that is available on the essential dev webpage. Any ideas would be awesome, is in possible to side load using the adb commands from the recovery menu and avoid the fastboot mode all together.
Click to expand...
Click to collapse
unlock_critical.
You can't flash all the partitions is you have not performed and unlock AND and unlock_critical.

tech_head said:
unlock_critical.
You can't flash all the partitions is you have not performed and unlock AND and unlock_critical.
Click to expand...
Click to collapse
I have ran both unlock commands successfully and still get permission denied

swagglepuff said:
I have ran both unlock commands successfully and still get permission denied
Click to expand...
Click to collapse
And you checked the OEM unlock in developer options?
Hmmmm

tech_head said:
And you checked the OEM unlock in developer options?
Hmmmm
Click to expand...
Click to collapse
The issue has something to do with Mac and the platform tools. I was able to downgrade with no problem using a friend's Windows PC.

Sorry for the silly question, but what does this statements means?
"Add it to your path so the flash scripts can find it"
Is there any better instructions for first time user which dont include instructions like above? Thanks.

trizon2016 said:
Sorry for the silly question, but what does this statements means?
"Add it to your path so the flash scripts can find it"
Is there any better instructions for first time user which dont include instructions like above? Thanks.
Click to expand...
Click to collapse
Nothing confusing about that statement for Windows, MacOS or Linux.
A command path needs to exist so that when you type the command it can be found.

Trying to unlock bootloader for oneplus6t getting error in adb

When I go into the bootloader to run the fastboot oem unlock command it gets stuck at waiting for device. I tried turning on USB debugging and it reads the phone while its booted into the OS but when going to bootloader "Waiting for device" could someone plz help me out thks. I have minimal adb and fastboot on my computer and it has worked before

Have you turned OEM unlocking on in developer options? Test for connectivity with "fastboot devices" fastboot drivers are also not installed by default on PC, might have to go searching for some more up to date drivers

Did you install all your drivers , ie.. the one for OnePlus...

Hello. I am having the same issue. When I read the general XDA rules and the guide to OnePlus Device Forums, I believe I should post here instead of creating a new topic.
I am running adb and fastboot on Fedora 33. My 6T is a T-mobile variant. I was running /e/ for a couple months. I used the MSM tool to restore to Oxygen 9. Then I upgraded to Oxygen 10 OTA. No issues there.
I enabled developer tools, and toggled OEM Unlock to ON. I am able to start in fastboot, no issues. The phone is obviously locked. I have the unlock token from when I originally unlocked to install /e/.
When I run
Bash:
sudo fastboot devices
, it returns the same number as on the phone's fastboot menue. So I believe it sees the phone.
If I run
Bash:
[sudo] adb reboot bootloader
, I get the message
Code:
error: insufficient permissions for this device. See [http://developer.android.com/tools/device.html] for more information
. (Going to that website gives a white page with bold letters Service Unavailable.
I run
Bash:
fastboot flash cust-unlock unlock_code.bin
, and it hangs with the message
Bash:
< waiting for any device >
. I'm able to Ctrl-C back to the command prompt.
If I run
Bash:
sudo fastboot flash cust-unlock unlock_code.bin
, it gives me the message
Bash:
fastboot: error: cannot load unlock_code.bin: permission denied
After searching on the web, I've seen a couple of others with this same problem. But I haven't seen anybody found a solution yet. I'm going to keep on plugging away at this. If I figure something out, I'll bring it back here.
Dan.

OK. Turns out I'm a complete dodo bird. The permission denied is from bash. chmod 755 on the token file fixed the problem. Lineage is now running nicely.

OnePlus 8 TMO Magisk boot image IN2017_11_C.43

It took a bit of work to root OnePlus 8 T-Mobile version on the latest Android 12 update. I am a long time lurker and simply I wished someone else had posted the boot image to save me time. Can be simply flashed using fastboot commands.
Please check to make sure you are on the latest update from T-Mobile and that software version is: IN2017_11_C.43 Android 12 Security update November 5, 2022.
Installation instructions:
*You must have your phone unlocked for any carrier otherwise OEM unlocking will be unable to set.*
#1 go to settings, about device. TAP software version five times to enable developer options under system settings. Go to developer options and tick the following options:
a OEM Unlocking
b Enable USB debugging
#2 Download the OnePlus 8 Windows drivers and ADB fastboot drivers if your using a PC or Termux from F-Droid if using another rooted phone.
PC instructions:
Go to the directory you installed ADB and Fastboot. Open the command prompt by either right click on an empty space in that folder and finding command prompt or going to the directory tree and typing cmd and hit enter. Inside the Windows command prompt the root directory should be the same folder as your ADB and fastboot executables. Move the attached boot image to the same folder as your ADB and fastboot executables and rename it boot.img. Attach your phone to your PC and run the following commands:
adb devices
This command is so you can check to see if your PC is correctly configured and it should send you a notification on your phone to allow debugging from your PC, make sure you will allow it always.
adb reboot fastboot
This command will reboot your phone into fastboot mode. Do not select any you on your phone and only type in the following commands on your PC.
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
This command will flash the magisk modified boot image which will grant you root access to your phone.
fastboot reboot
This command will reboot your phone. Congrats, your now rooted on the latest Android 12 update for your T-Mobile Oneplus 8!

what attached boot img?

zeromonarch said:
what attached boot img?
Click to expand...
Click to collapse
I must've somehow missed it too. I cant find any boot image to download

If only there were the elusive boot image...
It could have saved my ass from the current double-slotted brick I sit upon!

Does anyone have the boot image for the latest T-Mobile update?
IN2017_11_C.45
in fact this isn't even the latest as there is a new update waiting for me with the new security release or security update but I haven't updated yet also does this wipe data?