Database Info

In2017 to global guide?

I've searched and soft bricked and restored via msm and even got twrp on one time. Is there a straight forward guide anywhere that shows the process of going from stock TMobile android 10 or 11 to the global device software? Im either misunderstanding it or just can't find it. The one guide that i thought was correct was good all the way until it got to the part where it said not for branded devices but there's not actually a link that leads to a section to do branded devices. Please help as this thing is almost unusable on mint mobile with the current stock rom.

I mean I know there is the wip guide in the other forum. But I can't seem to get out of crash dump or fastboot loop so I figured maybe that's the wip part of it?

I can't stress enough to read, read, read. There are not that many threads here so it should be pretty easy to do. I'm posting the link to convert to global for you. Used it many times. In fact I used it this weekend. Happy modding!
[ROM][STOCK][FASTBOOT][OP8] Stock Fastboot ROMs for OnePlus 8
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are...
forum.xda-developers.com

.

i dont know if you have been succesful yet or not but the WIP guide is the way to go. Like you i kept getting flash dump error then flash back to t-mobile and very frustrated.
but if you read through the forum with the wip guide, somewhere it mentions that you have to first flash an earlier t-mobile version of OOS then you can flash the same version Global OOS and just like that it worked for me. After you can upgrade to the latest.
i hope that helps.

MSM Tool doesn't work

Hello guys i have KB2003 8T, and i now i'am using hydrogen os (i was using oxygen).
I cannot turn back to oxygenos with msm tool, when download finish it says qualcom crashdump.
All i can do is, installing oxygen beta 5 with local upgrade. please help me

.

MSM tool works great and has bailed me out twice already from some good bricking.
Run through your process start to finish with each step and the result from those steps please.
Is there any potential reason that the hardware might have failed?

parakleet said:
MSM tool works great and has bailed me out twice already from some good bricking.
Run through your process start to finish with each step and the result from those steps please.
Is there any potential reason that the hardware might have failed?
Click to expand...
Click to collapse
i dont think so its Hardware problem. Please anyone help me.

in the giant XDA forum, no one has any idea?

[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com

[BOOTLOADER] Error: Unable to boot from 2nd slot! [QUALCOMM CrashDump 0x00007f00]

Hi all,
trying to boot form second slot ends up in QUALCOMM CrashDump 0x00007f00 and I have no idea how to fix it.
Edit: Booting from slot A & recovery works fine. Only trying to boot from B ends up in this error.
I own a new 8T, currently with stock OxygenOS 11.0.11.11, TWRP installed and wanted to prepare it to install a custom rom.
So according to https://lineageosroms.com/kebab/ I used copy-partitions-20210323_1922.zip, to sync slots.
After syncing, trying to change to 2. slot (used TWRP to change slot) ended up in error above.
On 2. slot I was not even able to mount /data...
Tnx to @BillGoss I could fix an issue - partitions boot_a|b, dtbo_a|b, vbmeta_a|b did defer.
Now all AB-partitions are identical, but still booting in 2. slot ends up in CrashDump.
(Anyway, after syncing all deferring partitions, mounting /data in TWRP now works on both slots.)
What else could be wrong, that I am not able to boot to 2. slot?
How can I fix this problem?
Edit: I have no Windows machine - Linux only, so using MSM tool would be a big issue for me...
Help is really appreciated.
Tnx in advance,
Enkidu

Use the MSM tool to get your device bootable again...
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com

Ramme said:
Use the MSM tool to get your device bootable again...
[OP8T][OOS KB05AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
Click to expand...
Click to collapse
Great! Tnx for fast reply!
Hmmm... I do not own a Windows system.
May there be a different way to fix my problem?

Download what you want, you can Update later to the Last Version , all MsM Work fine

Ramme said:
Download what you want, you can Update later to the Last Version , all MsM Work fine
Click to expand...
Click to collapse
Tnx. I needed a second to understand it.
But next problem is, I do not own a Windows system. Linux only...
May there be a different way to fix my problem?

Sorry, I'm out of that one. I'm sure there is a command method, but your bootloader is crashed, so you don't have a command option, so the only thing left is the MSM tool.

Ramme said:
Sorry, I'm out of that one. I'm sure there is a command method, but your bootloader is crashed, so you don't have a command option, so the only thing left is the MSM tool.
Click to expand...
Click to collapse
Maybe I was not clear enough. Only booting for slot A does not work. Booting from B or recovery works fine.

I think you can use fastboot mode from one of the working slots to flash oos into both the slots using Linux. Guide attached.
upfiles - Make Money by Sharing Files!
upfiles is a file-sharing platform that allows users to make money by sharing files. We offer the best storage and payout rates ever!
upfiles.com

@enkidu70 you shouldn't care about not being able to boot into one of the slots.
The A/B configuration is specifically designed for dealing with seamless updates. These (updates) result in only one of the slots being bootable at any one time.
Since you have one slot that works fine, that's good. And don't bother with trying to restore your phone to its original setup - that will still leave you with one bootable slot!
If you're planning to install a custom rom using TWRP, then have a look at how things get flashed: https://forum.xda-developers.com/t/...ect-8t-kebab-2021-09-04.4302449/post-85910241

BillGoss said:
@enkidu70 you shouldn't care about not being able to boot into one of the slots.
Click to expand...
Click to collapse
Tnx. Tried it. Works!
(For some reason, It was a bit tricky to get /data formatet - but now everything seems fine!)
Tnx for your great support!

Did you ever get both slots to work? I have the same problem. I can go into fastboot to change the active slots to boot into Slot b, but Slot A is still not working. Will it ever work?

Question Your device is corrupt. Oneplus 9

I tried putting the beta of OOS13 on my Oneplus and now i get that error message and ive been trying for so long.
the serial number is fb7b98a9

Flash by edl if you can't do it then pm I'll fix it by tv

Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck

applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Click to expand...
Click to collapse
applyscience said:
Could you elaborate a little further? Are you just not able to flash OO13 beta or has the attempt of doing so corrupted your device completely?
If the latter, You will most likely need to flash an emergency MSMToolkit. It is an Indian OP9Pro variant but will bring your device back from the dead. Once that is done, you will just run a proper MSMToolkit and be right as rain.
EtherealRemnant wrote up an amazing guide on how to carry this out. SO amazing that its the only guide stickied on the 9 forums, currently.
- Here is a mega hosted copy of the Indian OP9Pro MSMToolkit,
I can personally vouch for the guide, as my 9 went into a bricked state with vague errors about corrupted system. I tried every toolkit, recovery and ROM and nothing worked. Thats when EthRem came to my rescue. Hopefully his work can come to yours as well.
and if that isn't what you meant and are just dying to get into OOS13, id just stick with one of the many A13 ROMs currently available. OOS13 is beautiful but, i just cant honestly suggest using Oneplus software anymore.
Good luck
Click to expand...
Click to collapse
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day

SubColdSnow said:
The tool that you linked doesnt have o2 as he is saying in the guide.
Also yes, i tried flashing OOS13 and it just corrupted my device i've been endlessly working to fix it all day
Click to expand...
Click to collapse
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above

rizzmughal said:
1st of all flash with op9pro india msm with uncheck sah and check lite firehorse if u have hard bricked ur device then the next steps as mention above
Click to expand...
Click to collapse
i tried and just get device does not match image

SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try it again. if anything, you will be attempting on the other slot. Many haves had issues and it just started working.
it could have been slot related, or possibly some minor detail that is finicky. (ex. you usually want to start the msmtoolkit and let it stay in the "waiting for device" phase and plug in your phone (which should be in EDL mode . youll know by the peeps of it habitually connecting/disconnecting on your PC)
assure you have india selected, assure you have the proper conditionals on/off per the guide's explication.
Assure you have the qualcom drivers installed, and they reflect the naming convention.
follow along the guide again and Just keep attempting it and don't get discouraged. Part of the reason people offer guides here is that they themselves failed many times until they got they figured it out and are trying to save people from it.
youll get it, dont worry.

I had this problem because I flashed a custom kernel on a custom rom today

SubColdSnow said:
i tried and just get device does not match image
Click to expand...
Click to collapse
try the modded msm tool. it worked for me.

Unbrick OnePlus 8 5G UW [IN2019] after failed LineageOS install

I was under the impression my phone was compatible and began the install instructions for LineageOS after unlocking my phone through this guide. I flashed the two partitions, flashed the recovery, attempted to boot into recovery and it gets stuck on boot. After attempting to ask the LineageOS community I realized Verizon's version is not supported, woo. I then tried to follow the unlock guide to flash back the stock image and Msm fails on Param preload with the error "Device not match image." Googling that I only found someone implying they were using the incorrect global image, however, I know I'm not. Is it possible to recover my phone now and if so, how?

LineageOS is a base ROM for many other custom ROMs such as crDroid. Try using their recoveries and installation guides; crDroid worked perfectly in the past.

Xryphon said:
LineageOS is a base ROM for many other custom ROMs such as crDroid. Try using their recoveries and installation guides; crDroid worked perfectly in the past.
Click to expand...
Click to collapse
I'm waiting for the phone to recharge now before attempting. I feel like it will fail however as the crDroid steps require you having stock 11 on "both slots." I am too new to this scene to understand what that means or if I can even do that anymore.

rusty-op8 said:
I'm waiting for the phone to recharge now before attempting. I feel like it will fail however as the crDroid steps require you having stock 11 on "both slots." I am too new to this scene to understand what that means or if I can even do that anymore.
Click to expand...
Click to collapse
You might want to the follow this guide as a basic requirement for flashing any Custom ROM on 'instantnoodle'.
It's always good to re-read, proofread and re-read again before proceeding.

rodken said:
You might want to the follow this guide as a basic requirement for flashing any Custom ROM on 'instantnoodle'.
It's always good to re-read, proofread and re-read again before proceeding.
Click to expand...
Click to collapse
Thank you for the resource. I will attempt this instead once I can. I see that it makes a very important note about copying slot a to b to prevent potential hard-bricks. Since the "official" guide I started with did not mention that before I attempted going down this route, does this mean I'm ruined anyways? I only flashed 2 "boot" images and then the recovery image when this happened. This is all because I was using 19.1 without realizing that a) it's A12 and b) one of the maintainers said the Verizon version wasn't supported. Seeing as I can grab the last 18.1 from the link you provided me, maybe there's hope after all.

rusty-op8 said:
Thank you for the resource. I will attempt this instead once I can. I see that it makes a very important note about copying slot a to b to prevent potential hard-bricks. Since the "official" guide I started with did not mention that before I attempted going down this route, does this mean I'm ruined anyways? I only flashed 2 "boot" images and then the recovery image when this happened. This is all because I was using 19.1 without realizing that a) it's A12 and b) one of the maintainers said the Verizon version wasn't supported. Seeing as I can grab the last 18.1 from the link you provided me, maybe there's hope after all.
Click to expand...
Click to collapse
All is not lost as long as your device can power on and is not completely bricked.