Database Users

Boot from SD card. EMMC memory is dead

I have the wt86047(HM2014813,HM2XTDPro) and I have dead emmc on my phone. The internal /data /system and /cache partitions are unmountable. So I decided that I try to boot from sdcard.
I have used this tutorial Dual boot to partition my sdcard and modify the recovery and the rom(Lineage 14.1) to look for the system, data and cache partitions on sdcard.
But when I try to boot up the phone is stuck at the MI logo and I see my device in fastboot. To be able to boot to my device I need in fastboot to execute fastboot boot modifiedboot.img. This is not too much convenient as I need pc to turn my phone on. I also can only boot recovery and not to get to the recovery mode. I can however flash the image to the /recovery partition. I suspect that my /boot partition is also corrupted. I tried to manualy flash boot also with no succes. Any ideas how to boot the phone without need to use fastboot?

I have the exact same issue with the same phone.
You have modified only the fstab file ?

nings008 said:
I have the exact same issue with the same phone.
You have modified only the fstab file ?
Click to expand...
Click to collapse
In boot.img yes(fstab.qcom), in TWRP the etc/recovery.fstab and in the updater script any mention of /system and /data.
The phone boots with the fastboot boot, but it is quite slow as I have quite cheap sd card in it. I would buy a better one If I would be able to boot the phone without computer.
EDIT: Camera is also not working for some reason

Try folding the fastboot ROM.
Same thing happened to me. I tried and flashed the fastboot image. It worked. This happened to me a long time ago. Don't worry about bootloader if you can see the fastboot screen with the mi man on your phone .
http://bigota.d.miui.com/V8.0.1.0.K...DG_20160805.0000.29_4.4_global_daca6227c0.tgz
This is the link for the fastboot file for Redmi 2 aka wt88047 or any other version of the Redmi 2.
Just use the following method to flash using ADB and should be successful.
Steps to Flash MIUI Fasboot ROM Without Using Mi Flash Tool {Using Command Prompt}
We would like to suggest that Please use the Official Flashing method through Mi Flash Tool if that method didn’t work for you then try this method.
Below is the overall method to Flash MIUI 8/9 Using Command Prompt. The commands use in this method are pretty common. For most of the users are familiar with this Commands.
Quick Requirments:
Download Fastboot ROM of your device.
Xiaomi USB Driver & ADB Driver of your device.
Try Mi PC Suite if above USB Driver doesn’t work for you.
Flash MIUI Fastboot ROM Using Command Prompt
1. Download the Fastboot ROM you want to flash from the above download link. Extract the Downloaded Fastboot ROM in your Windows PC.
2. Enter into Download Folder. You will see some Files & Folder out there. Again go to Images Folder.
3. Boot your device into Fastboot Mode. To do this Switch off your phone. Now, Press Power Button + Volume Down button to boot your device into Fastboot Mode.
4.In that folder “Open Command Window” by Holding Shift Button + Right Click button of the mouse. You will see Command Prompt will open there.
5.Type following Command to check whether your device is connected or not.
fastboot devices
6. Below the command, If it shows the device then you are ready to flash. Now, Execute following commands one by one to flash the whole ROM.
fastboot flash system system.img
Press Enter to Continue
fastboot flash boot boot.img
Press Enter to Continue
fastboot flash recovery recovery.img
Press Enter to Continue
fastboot flash cache cache.img
Press Enter to Continue
Want Complete erase of data? All Data will be deleted it will be like new device. Then type this following commands.
fastboot erase userdata
Press Enter to Continue
fastboot flash userdata userdata.img
Press Enter to Continue
All Flashing process in complete. Now, Type the following code & hit enter button to Reboot your device normally.
fastboot reboot
That’s it! Congratulation! You have successfully Installed Latest MIUI Fastboot ROM. Your device bootloader is locked now & You device is unrooted. Please let me know if it helped.

d2211basu said:
Same thing happened to me. I tried and flashed the fastboot image. It worked. This happened to me a long time ago. Don't worry about bootloader if you can see the fastboot screen with the mi man on your phone .
Click to expand...
Click to collapse
This won't help. This is the hardware issue. The storage chip on the motherboard is dead. You can not write anything to it. It is possible to replace that chip but it is a quite difficult operation.

tulen_kobi said:
Any ideas how to boot the phone without need to use fastboot?
Click to expand...
Click to collapse
Looking for the same.
https://forum.xda-developers.com/android/help/how-to-boot-sd-card-qmobile-z8-bricked-t3712171

Redmi 2 Hard Bricked or Boot Dead Repair
tulen_kobi said:
I have the wt86047(HM2014813,HM2XTDPro) and I have dead emmc on my phone. The internal /data /system and /cache partitions are unmountable. So I decided that I try to boot from sdcard.
I have used this tutorial Dual boot to partition my sdcard and modify the recovery and the rom(Lineage 14.1) to look for the system, data and cache partitions on sdcard.
But when I try to boot up the phone is stuck at the MI logo and I see my device in fastboot. To be able to boot to my device I need in fastboot to execute fastboot boot modifiedboot.img. This is not too much convenient as I need pc to turn my phone on. I also can only boot recovery and not to get to the recovery mode. I can however flash the image to the /recovery partition. I suspect that my /boot partition is also corrupted. I tried to manualy flash boot also with no succes. Any ideas how to boot the phone without need to use fastboot?
Click to expand...
Click to collapse
Follow This Link
https://globaltech2u.com/how-to-bring-a-boot-dead-or-hard-bricked-redmi-2-back-to-life

Nvidia Shield 2019 Pro Developer images 8.1.0

It's seems like Nvidia released the developers image for the shield 2019 pro. There is no description at links only some dots see images.
Shield Android TV SW Version: 8.1.0 (32.7.301.32)
Android Paches: 5 oct 2019
https://developer.nvidia.com/search/site/Shield 2019
NVIDIA SHIELD ANDROID TV 2019 Pro Developer Only OS Image
https://developer.nvidia.com/nvidia-shield-android-tv-pro-developer-only-os-image
Filename: nv-recovery-image-shield-atv-pro-2019-8.1.0-dev-rooted.zip
NVIDIA SHIELD ANDROID TV 2019 Pro Recovery OS Image
https://developer.nvidia.com/nvidia-shield-android-tv-pro-recovery-os-image
Filename: nv-recovery-image-shield-atv-pro-2019-8.1.0.zip
I have downloaded them let see what happens, i'm not responsible if you brick your device.
Both recovery images are working on the Shield 2019 PRO and I was able to fully flash my shield and got things running again.
Image files contains a flash-all file and all the images to recover you device
fastboot oem unlock
:: Confirm the prompt on the screen
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash dtb mdarcy.dtb.img
fastboot flash vbmeta vbmeta.img
fastboot oem lock
:: Confirm the prompt on the screen
The developer version contains 1 extra file called vbmeta_skipped.img.
NOTE: After unlocking your bootloader you will lose Dolby Vision, after locking you bootloader you will get back Dolby Vision

See also https://forum.xda-developers.com/showpost.php?p=81200005&postcount=380
Below are the steps we used to root our Nvidia Shield 2019 PRO, if you are new to rooting devices you better can wait until their are less steps.
For some reason this post doesn't show correctly in the XDA app.
UPDATE: it's possible to use the official release of Magisk.
PreRequisites:
Download: Experimental TWRP is from https://forum.xda-developers.com/showpost.php?p=80769929&postcount=312
Download: Magisk official release https://github.com/topjohnwu/Magisk/releases/tag/v20.4
Download: Filename: nv-recovery-image-shield-atv-pro-2019-8.1.0-dev-rooted.zip (see above post)
Download: Filename: nv-recovery-image-shield-atv-pro-2019-8.1.0.zip (see above post)
Working ADB/Fastboot.
Coffee and a bit of luck.
Enable Developers options/Enable USB Debugging/Authorize device.
Step 1
Reboot to bootloader to start fresh...(you will need a keyboard)
Use files from filename: nv-recovery-image-shield-atv-pro-2019-8.1.0.zip
Use vbmeta_skipped.img from filename:
nv-recovery-image-shield-atv-pro-2019-8.1.0-dev-rooted.zip
a) fastboot oem unlock and confirm by pressing A
b) fastboot flash staging blob
c) fastboot flash boot boot.img
d) fastboot flash recovery recovery.img
e) fastboot flash system system.img
f) fastboot flash vendor vendor.img
g) fastboot flash dtb mdarcy.dtb.img
h) fastboot flash vbmeta vbmeta_skip.img
I) fastboot -w
j) fastboot reboot bootloader
Step 2
Now we will boot to twrp and install magisk...
a) fastboot boot twrp.img (you will need a mouse for this)
b) select mount and mount everything it lets you (usually data, system_root, vendor, cache)
c) adb remount all
d) adb shell
e) rm /system (removes symlinked folder)
f) mkdir /system
g) mount -o bind /system_root/system /system
h) exit
i) adb push Magisk-v20.4.zip /data/media
j) In twrp press install and navigate to magisk zip and flash it
k) adb reboot bootloader
l) fastboot -w
m) fastboot reboot bootloader
n) fastboot flash dtb mdarcy.dtb.img
o) fastboot flash vbmeta vbmeta_skip.img
p) fastboot reboot
q) let it reboot a couple of times, after Nvidia blinks and then reboots).
Optional
r) If Shield doesn't go passed the Nvidia logo.
s) start shield with A+B pressed to get in fastboot
t) in fastboot menu select reset factory default.
u) fastboot flash dtb mdarcy.dtb.img
v) fastboot flash vbmeta vbmeta_skip.img
w) fastboot reboot
x) let it reboot a couple of time
Step 3
Device eventually loads.. when it does follow these steps
a) Enable usb debugging
b) make sure its authorized and connected
c) adb install -g magisk.apk
d) adb shell
e) su (grant root to shell when it pops up)
f) mount -o rw,remount /
g) Go to apps (trough settings), show all apps, start/open magisk manager
h) When it pops up telling you it needs to install stuff select ok and install it.. device will reboot in 5 seconds...
Step 4
When device tries to boot you should now be stuck at the android boot ani (NOT the nvidia logo).. then follow these steps..
a) adb shell
b) su
c) resetprop ro.boot.verifiedbootstate orange
d) after device boots run: resetprop ro.boot.verifiedbootstate green
Step 5
If you have registerd for the hotfix (32.7.301.43) then you can start the upgrade now. The device will reboot and starts the upgrade, after that you lost root again.
a) adb reboot bootloader
b) fastboot boot twrp.img (you will need a mouse for this)
c) select mount and mount everything it lets you (usually data, system_root, vendor, cache)
d) adb remount all
e) adb shell
f) rm /system (removes symlinked folder)
g) mkdir /system
h) mount -o bind /system_root/system /system
i) exit
j) adb push Magisk-v20.4.zip /data/media
k) In twrp press install and navigate to magisk zip and flash it
l) adb reboot bootloader
m) fastboot flash dtb mdarcy.dtb.img
n) fastboot flash vbmeta vbmeta_skip.img
o) fastboot reboot
p) When device tries to boot you should now be stuck at the android boot ani (NOT the nvidia logo).. then follow these steps..
q) adb shell
r) su
s) resetprop ro.boot.verifiedbootstate orange
t) after device boots run: resetprop ro.boot.verifiedbootstate green
After every reboot
When device tries to boot you should now be stuck at the android boot ani (NOT the nvidia logo).. then follow these steps..
a) adb shell
b) su
c) resetprop ro.boot.verifiedbootstate orange
d) after device boots run: resetprop ro.boot.verifiedbootstate green
Stuck at Nvidia Logo
a) Power off Shield, remove power cable
b) Press & Hold A+B on keyboard or controller.
c) Plugin power cable will holding keys.
d) You will see the fastboot menu.
Restore Stock
Use files from Filename: nv-recovery-image-shield-atv-pro-2019-8.1.0.zip
a) Power off Shield, remove power cable
b) Press & Hold A+B on keyboard or controller.
c) Plugin power cable will holding keys.
d) You will see the fastboot menu.
e) fastboot flash staging blob
f) fastboot flash boot boot.img
g) fastboot flash recovery recovery.img
h) fastboot flash system system.img
i) fastboot flash vendor vendor.img
j) fastboot flash dtb mdarcy.dtb.img
k) fastboot flash vbmeta vbmeta.img
l) fastboot -w
m) fastboot reboot bootloader
n) fastboot oem lock and confirm by pressing A
Like I mentioned before, only use this when you know what your are doing. I'm not responsible for any brick devices.
All the credits are for @elliwigy and @rootfan

reserved

Hello and thank you for sharing this.
I'm looking for the fastboot drivers (the 2017 don't works with the pro 2019), I have contacted Nvidia by chat and he doesn't found too.
Can you please tell me where I can download them ?
And sorry for my poor english I'm french.
EDIT :
Ok I have resolved the problem, I have manually installed the .inf.
Regards.

After every reboot
When device tries to boot you should now be stuck at the android boot ani (NOT the nvidia logo).. then follow these steps..
a) adb shell
b) su
c) resetprop ro.boot.verifiedbootstate orange
d) after device boots run: resetprop ro.boot.verifiedbootstate green
Click to expand...
Click to collapse
I don't understand, does this mean we have to do these steps every time the shield reboot ?

lycaos said:
Hello and thank you for sharing this.
I'm looking for the fastboot drivers (the 2017 don't works with the pro 2019), I have contacted Nvidia by chat and he doesn't found too.
Can you please tell me where I can download them ?
And sorry for my poor english I'm french.
EDIT :
Ok I have resolved the problem, I have manually installed the .inf.
Regards.
Click to expand...
Click to collapse
Hi,lycaoslease tell me how to edit the .inf,thanks a lot!

marokino95 said:
I don't understand, does this mean we have to do these steps every time the shield reboot ?
Click to expand...
Click to collapse
Yes every time you reboot you will have to do this. I have connected a Raspberry to the shield which makes it easier.

song4 said:
Hi,lycaoslease tell me how to edit the .inf,thanks a lot!
Click to expand...
Click to collapse
Hello.
It's not easy for me to explain in english, I have Windows in french. But simply go to "device manager" or something like that, select update fastboot, select choose manually, and select again the option to choose manually the driver. Select the .inf and choose boooader driver (it is really simple but like I've said It's not easy for me to explain in english, just don't select the option to search automatically the driver in folder/sub folders, select the other option).
Ok so, I have a big problem when I boot twrp.img : My mouses are not recognized (I have tried 4 wired mouses and bought one very basic old mouse. All the mouses are detected in normal or fastboot mode but 0 device are detected except the computer (I can send adb commands in twrp mode, it's all I can do).
I have also tried a lot of wired controller...
If someone have a solution to use twrp...
(All that things just for modify the Vendor_045e_Product_028e.kl to change A to B and Y to X to use my switch controller pro connected to the 8bitdo recognized as xbox 360 controller >< because natively the switch have pads issues and button mapper have a big latence and don't works in nvidia gamestream !!).
Have a good week-end guys, french kisses :silly:

lycaos said:
Hello.
It's not easy for me to explain in english, I have Windows in french. But simply go to "device manager" or something like that, select update fastboot, select choose manually, and select again the option to choose manually the driver. Select the .inf and choose boooader driver (it is really simple but like I've said It's not easy for me to explain in english, just don't select the option to search automatically the driver in folder/sub folders, select the other option).
Ok so, I have a big problem when I boot twrp.img : My mouses are not recognized (I have tried 4 wired mouses and bought one very basic old mouse. All the mouses are detected in normal or fastboot mode but 0 device are detected except the computer (I can send adb commands in twrp mode, it's all I can do).
I have also tried a lot of wired controller...
If someone have a solution to use twrp...
(All that things just for modify the Vendor_045e_Product_028e.kl to change A to B and Y to X to use my switch controller pro connected to the 8bitdo recognized as xbox 360 controller >< because natively the switch have pads issues and button mapper have a big latence and don't works in nvidia gamestream !!).
Have a good week-end guys, french kisses :silly:
Click to expand...
Click to collapse
Dear lycaos,Thank you for your kindness to help me.Wish you have a good weekend.

Thanks

hi, I am trying to root my Shield 2019 Pro. However I am stuck at installing Fastboot drivers for Windows 10. I only found the Windows drivers for older Shield models. And they don't work. How can I make these work? Thanks a lot!

Well, some of you know this because you have successfully rooted the Shield Pro 2019.
How do I install Fastboot drivers on Windows 10?

thanks for absolutely no help.

Rey3000 said:
thanks for absolutely no help.
Click to expand...
Click to collapse
That's a interesting reply, I also have a busy job and a family. And the same goes for other people on xda.
I'm using Linux and I don't have a problem with the drivers. But you can use the drivers on the Nvidia site.
https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB
If that doesn't work you could maybe try
https://xdaflash.com/download-universal-adb-driver-installer-windows

Rey3000 said:
thanks for absolutely no help.
Click to expand...
Click to collapse
Maybe read all post next time ? Lycaos had the same problem you have and he explained how he resolved it on the first page, i had it too and resolved it by following what he said.

powercommy said:
Below are the steps we used to root our Nvidia Shield 2019 PRO, if you are new to rooting devices you better can wait until their are less steps.
Click to expand...
Click to collapse
While I'm generally familiar with Android, I'm new to rooting devices. Where is the best place to keep tabs on progress? Also, out of curiosity, how long does it usually take "until there are fewer steps"?

Exosq said:
Maybe read all post next time ? Lycaos had the same problem you have and he explained how he resolved it on the first page, i had it too and resolved it by following what he said.
Click to expand...
Click to collapse
Of course I tried. Doesn't work. Windows 10. Tried all USB ports. Hence my plea. - how dare I ask for help??
---------- Post added at 08:12 PM ---------- Previous post was at 08:10 PM ----------
besides ... he didn't mention what drivers he used. I OBVIOUSLY tried the latest ones from Nvidia - 2018. They do NOT work ffs.

Rey3000 said:
Of course I tried. Doesn't work. Windows 10. Tried all USB ports. Hence my plea. - how dare I ask for help??
---------- Post added at 08:12 PM ---------- Previous post was at 08:10 PM ----------
besides ... he didn't mention what drivers he used. I OBVIOUSLY tried the latest ones from Nvidia - 2018. They do NOT work ffs.
Click to expand...
Click to collapse
Maybe you should try a different approach with users of XDA and tone down your attitude a little bit. I have no interest in helping you out this way. Maybe other xda-ers will.

powercommy said:
Maybe you should try a different approach with users of XDA and tone down your attitude a little bit. I have no interest in helping you out this way. Maybe other xda-ers will.
Click to expand...
Click to collapse
In case you haven't noticed ... you DIDN'T help me.

mgmcd said:
While I'm generally familiar with Android, I'm new to rooting devices. Where is the best place to keep tabs on progress? Also, out of curiosity, how long does it usually take "until there are fewer steps"?
Click to expand...
Click to collapse
It really depends on how many users are using their Nvidia 2019 Pro before things gets easier. Their is not much differents between rooting your phone/tablet. As long as you follow the the steps you should be okay. It's very difficult to brick your device.
You could also monitor this thread @elliwigy is a user to watch.
https://forum.xda-developers.com/sh...-twrp-shield-android-tv-t3510456/post81811131

HTC U Ultra stuck in bootloop..Can you experts validate the STEPS to solve the issue?

So, my HTC U Ultra got stuck in bootloop just 3 days after warranty ended(tough luck level : 100).
My phone runs on everything stock and no root.
I press all the buttons when powered off and it goes into bootloader mode. It displays options to boot into recovery mode, boot into download mode and power down, all of which(except power down) gets device into bootloop again.
THE PRIORITY OF GOALS IS : DATA RECOVERY > PHONE BOOTING AND WORKING PROPERLY AGAIN
I did a little research and figured out some sort of procedure by putting bits and pieces together :
1. Download ADB/Fastboot toolkit || universal driver from koush github // I have HTC Sync manager installed as well || twrp custom recovery image for htc u ultra || new ruu from htc support for rom update.
2. Now I put my phone into fastboot mode (since it doesn't show up on adb devices), connect to pc using usb.
3. I type in cmd : "fastboot devices" --> My device shows up there --> Again in cmd : "fastboot boot recovery mytwrp.img" --> the twrp boots into my phone
I was able to put this many steps together and after the last step, i have an abstract idea of what to do :
Enable USB Debugging using twrp recovery --> Use ADB Pull Command to get my all my data from phone to pc --> Use adb wipe the old Firmware (Not sure which command) --> Use adb again to flash new RUU (again not sure how, I've got an .exe file as RUU || should I get it in zip or img or any other format ? || Please help on this too) --> Finally Boot and hopefully everything turns out smooth and secure.
CAN YOU EXPERTS HELP ME TO PUT TOGETHER REMAINING STEPS (AND MODIFY ERRORS, IF ANY, OF EXISTING STEPS ) OF THIS PROCEDURE...???

Only to clarify: ADB and Fastboot are 2 completely different things.
ADB
is a protocol that allows you to communicate with an Android device that got booted, means its main Android OS is running
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb <ANY_SUPPORTED_ADB_SUBCOMMAND>
FASTBOOT
is a program used to manipulate (list, install, erase) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode with the fastboot protocol enabled.
IMPORTANT: Fastboot will only work if the OEM/Carrier has included support for the Fastboot protocol.
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot <ANY_SUPPORTED_FASTBOOT_SUBCOMMAND>

jwoegerbauer said:
Only to clarify: ADB and Fastboot are 2 completely different things.
ADB
is a protocol that allows you to communicate with an Android device that got booted, means its main Android OS is running
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb <ANY_SUPPORTED_ADB_SUBCOMMAND>
FASTBOOT
is a program used to manipulate (list, install, erase) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode with the fastboot protocol enabled.
IMPORTANT: Fastboot will only work if the OEM/Carrier has included support for the Fastboot protocol.
At Windows command prompt you enter commands - one by one -
Code:
adb devices
adb reboot bootloader
fastboot devices
fastboot <ANY_SUPPORTED_FASTBOOT_SUBCOMMAND>
Click to expand...
Click to collapse
@jwoegerbauer Yes, thank you for the description, I understood the difference later on. Do you think the fastboot and adb steps I've mentioned will work properly ?

noobie12112 said:
@jwoegerbauer Yes, thank you for the description, I understood the difference later on. Do you think the fastboot and adb steps I've mentioned will work properly in my case?
Click to expand...
Click to collapse
Android boot loop error does not come out of thin air. There are several cases that may cause the Android is starting loop. If phone didn't get physically damaged then an action of the user is the main reason .
To answer your question: NO.
As already said:
ADB is integral part of Android OS hence if Android OS isn't started you can't make use of ADB, Fastboot is integral part of phone's bootloader ( comparable to a Windows PC's UEFI/BIOS ) means you can't access Android OS - will say its folders and files.

jwoegerbauer said:
Android boot loop error does not come out of thin air. There are several cases that may cause the Android is starting loop. If phone didn't get physically damaged then an action of the user is the main reason .
To answer your question: NO.
As already said:
ADB is integral part of Android OS hence if Android OS isn't started you can't make use of ADB, Fastboot is integral part of phone's bootloader ( comparable to a Windows PC's UEFI/BIOS ) means you can't access Android OS - will say its folders and files.
Click to expand...
Click to collapse
@jwoegerbauer Thank you for the insight. In my case, the phone wasn't physically damaged, the bootloop occurred out of the blue one day. Now, what I presumed I should do, is to flash a custom recovery (twrp) using "fastboot boot recovery.img" command, and using twrp (Can I enable USB Debugging using twrp ?) to access files, backup and then flash a new RUU. But I found that I need to unlock bootloader, is there any way to use command "fastboot oem unlock" and not lose data, or any other method to unlock bootloader, where i don't lose data?
Thank you for your help.

Unlocking phone's bootloader always causes complete loss of data.
Forget the TWRP thing, it's not helpful at all in your case.
Try to flash phone's Stock ROM by means of ADB - what requires ADB got installed on Windows computer and USB debugging got ( manually !!! ) enabled on phone.

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?

return from lineage os to oxygen. problem with twrp installation

hello everyone. I haven't modded a smartphone for a long time and I need some help.
after installing lineage os a few years ago now i would like to go back with oxygen but i have problems with the installation of twrp.
I installed the platform tools and drivers and placed the twrp image in the (platform tools) folder.
debugging enabled
launching the command in the windows prompt: adb reboot bootloader the smartphone restarts correctly and shows me the screen with the choice START RESTART RECOVERY POWER OFF
the fastboot devices command, however, does not return any results
inserting the adb rebbot fastboot command instead the phone starts correctly in lineage os fastboot mode and now the fastboot devices command gives the result
now I enter the folder where I copied the twrp image cd c:\platform-tools and I give the command fastboot boot twrp.img (the file is renamed TWRP)
but this is the result
c:\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (33116 KB) OKAY [ 0.995s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
Can someone be kind enough to help me. I have made many different attempts to no avail.
Thank you!

sun-k said:
hello everyone. I haven't modded a smartphone for a long time and I need some help.
after installing lineage os a few years ago now i would like to go back with oxygen but i have problems with the installation of twrp.
I installed the platform tools and drivers and placed the twrp image in the (platform tools) folder.
debugging enabled
launching the command in the windows prompt: adb reboot bootloader the smartphone restarts correctly and shows me the screen with the choice START RESTART RECOVERY POWER OFF
the fastboot devices command, however, does not return any results
inserting the adb rebbot fastboot command instead the phone starts correctly in lineage os fastboot mode and now the fastboot devices command gives the result
now I enter the folder where I copied the twrp image cd c:\platform-tools and I give the command fastboot boot twrp.img (the file is renamed TWRP)
but this is the result
c:\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (33116 KB) OKAY [ 0.995s]
Booting FAILED (remote: 'Unrecognized command boot')
fastboot: error: Command failed
Can someone be kind enough to help me. I have made many different attempts to no avail.
Thank you!
Click to expand...
Click to collapse
Hello,
let me see if i can help,
but i need some info....
Which the LineageOS version
your device currently running ?
Is your 6T a global or T-Mobile version ?

hi, thanks for the reply. it is a secondary phone and has an old lineage version. yesterday with a different PC than usual I managed to install the latest version of twrp from cmd after solving a partition problem. i installed twrp only theoretically since after reboot the lineage prompt doesn't start and the boot stops at the screen with fastboot written... by forcibly turning it off I can access the bootloader. this is the current situation. 6t golobal...

developments ... from what I wrote above I could not get any progress. the device goes into bootloader mode manually but from the windows prompt it is not detected by the adb device command or by fastboot device .. so I can't advance ...

Going back to stock version does not necessarily
imply the use of a custom recovery,
you just need to use the MSM/rollback tool.
You can download it from THIS thread.
Use the earlier version of the tool as
you don't know wich exactly the
version of android installed in your device,
9.0.16 suggested.
When you will have a running device,
manually download and install OOS 9.0.17 firmware,
which will let your device to upgrade to android 10 and so on...
READ carefully @iaTa THREAD to follow exact MSM procedure.
Use a Windows pc and be sure
you have installed Oneplus driver.
Feel free to ask.