Qualcomm Crash Dump Mode - PLEASE HELP - Hard Brick ?!

Qualcomm Crash Dump Mode - PLEASE HELP - Hard Brick ?! - OnePlus 8 Questions & Answers

Hello!
I wanted to update my oneplus 8 from 11.0.4.4 to newest version. OTA was not working idk why. I had magisk in place and I patched magisk to second partition or something like that [I dont remember how it was called] - I'm sure this is the reason of the problems. I turned off devices and wanted to boot into recovery, but suddenly it boot into Qualcomm crash dump mode with message: Attempted to kill init! exitcode: 0x00007f00 do_exit - that's all. I can't boot the system, I can;t boot into recover, I flashed patched boot, I flashed recovery - none of these works. Fastboot is present and recognized by PC.
First question can I do some backup through fastboot? To be honest I was not prepared for such problems. APKs are not even such a problem I care more about photos, documents and other data.
Can I flash some rom and restore phone back to life without wiping my personal data?
Maybe an idea would be to load TWRP recovery and then do backup, but how to boot into recovery when even after flashing recovery or booting via fastboot it enters in qualcoom crash dump mode. Something must be corrupted, but is it possible to fix some partition just in order to flash recovery to do backup of the files?
Please can you help me? I tried with some tutorials, but no success...

What did you try doing if OTA wasn't working?
You won't be able to use TWRP since you're on Android 11.

Okay I managed to get back to normal - since like I mentioned i patched the magisk into second slot, then probably this corrupted something. What has helped me is this: fastboot --set-active=b
It was not working via powershell I had to launch CMD and then it worked I switched slot to "b" and phone booted normally.
Regarding OTA I have no idea what has happened. The only things I have done is magisk with modules like xXx No Limits and YTB Vanced. To be honest nothing more. I'm at Oxygen OS 11.0.4.4.IN21AA with bootloader unlocked. What would you suggest to do in order to update to newest version?

I would disable the magisk modules first in case that is what caused problems. Then do a local upgrade using the full OTA zip. Then install magisk to the inactive partition. I think that would work, but I'm not sure if a messed up A partition might affect the installation. I don't think so, but I haven't read anything about it. After, you can try re-enabling the magisk modules.

I turned off all the modules obviously and still OTA is not working via the oneplus updater. It does not see the zip rom even though it's in the main directory. I don't know what is wrong...

Oh, that's strange. I don't know how to recover from there. If it were me, I would just backup my files and MSM, but that's a lot of work.
Did you check the obvious things for the zip file like making sure it ends in the right extension? Sometimes if you download it from OnePlus, it has a jar extension instead of zip.

L
trinidude4 said:
Oh, that's strange. I don't know how to recover from there. If it were me, I would just backup my files and MSM, but that's a lot of work.
Did you check the obvious things for the zip file like making sure it ends in the right extension? Sometimes if you download it from OnePlus, it has a jar extension instead of zip.
Click to expand...
Click to collapse
Lol yes you're right it was jar. Now the updater sees the zip file, but I'm afraid to update because I'm not sure if the phone won't brick or bootloop. What do you think?

I think it should be fine. I think the only thing that got messed up was the boot partition on the A slot and that will get overwritten with the OTA.

How about the root and magisk?

Okay I updated and it's working fine. I'm on 11.0.7.7 but now magisk is not working, how to get it back?

remialfa said:
Okay I managed to get back to normal - since like I mentioned i patched the magisk into second slot, then probably this corrupted something. What has helped me is this: fastboot --set-active=b
It was not working via powershell I had to launch CMD and then it worked I switched slot to "b" and phone booted normally.
Regarding OTA I have no idea what has happened. The only things I have done is magisk with modules like xXx No Limits and YTB Vanced. To be honest nothing more. I'm at Oxygen OS 11.0.4.4.IN21AA with bootloader unlocked. What would you suggest to do in order to update to newest version?
Click to expand...
Click to collapse
Any idea if it's possible to do something similar to rooted OP6?
I have a similar situation where I tried to update magisk and ended up with a bricked device.
I can reboot to fasboot, but I can't boot to recovery or flash anything through some pc flashing apps.

Related

Phone reboot to twrp and twrp doesnt decrypt data after OTA update

Hi,
So I followed this tutorial https://oneplus.gadgethacks.com/how...thout-losing-root-no-computer-needed-0192638/ (but I used more up to date downloads links than what was on the article) to update my phone to the latest oxygenos on my OnePlus 6.
The install went well, I could reboot on my phone without problems. The thing is when I ran magisk manager it said that magisk wasn't installed. So I rebooted to twrp and flashed again magisk then rebooted. Now when the phone rebooted and asked me for my pin number it automatically went to "Shutting down phone" and rebooted to twrp. So I flashed the magisk uninstaller but it didn't rebooted well. Then I thought I had to switch the active slot, so in twrp I switched to slot A. Then it rebooted on fastboot. I understood I did something really bad so I ran "fastboot --set_active=b" on my computer.
Now my phone cannot actually boot and everytime I get in twrp except that now it doesn't ask me to unlock the phone to decrypt it and just asks me if I want to get into twrp in read only mode. When I navigate to /sdcard, it is full of weird folder name which is because, if I understand well, twrp has failed to decrypt it.
Is my phone bricked? Can I recover data? Can I repair my installation?
EDIT: if you need more informations that I forgot to give don't hesitate to ask.
EDIT2: I tried to reboot to fastboot mode and issue on my computer "fastboot boot twrp-3.2.3-1-enchilada.img" to see if the official twrp could decrypt the data (I'm currently using bluespark's twrp). I get the following error: "FAILED (remote: unknown command)". I understand now I'm pretty ****ed. Right now I'd only like to recover my data (mostly hundreds of pictures) and then flash a stock rom (except if it's actually possible to repair the system and boot normally). How can I decrypt /sdcard if twrp can't do it?
Thanks in advance for your help, I'm pretty lost right now and it's quite an urgent situation.

I got a new error when issuing "fastboot boot boot.img" after I rebooted to System from twrp:
```
Downloading 'boot.img'
OKAY [ 0.692s]
booting
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Finished. Total time: 0.719s
```

Ok so now by restarting a couple of times to fastboot I successfully booted to official twrp using "fastboot boot.img" and it successfully decrypted my storage!!!
Now I think things are recoverable, how do I fix this bad boy? Reflashing last official oxygenos image could work?

noom4_5 said:
Ok so now by restarting a couple of times to fastboot I successfully booted to official twrp using "fastboot boot.img" and it successfully decrypted my storage!!!
Now I think things are recoverable, how do I fix this bad boy? Reflashing last official oxygenos image could work?
Click to expand...
Click to collapse
Once in your booted TWRP from 'fastboot boot twrp.img' ... Flash OOS (9.0.5 from xda forums), flash blu_spark-TWRP, reboot TWRP... Now you can root your phone (flash Magisk), flash a kernel. All should be good.
I would suggest in future, use these forums for download links, tutorials, and check this Q&A forum (literally 3-5 posts on first half of page 1 with similar problems. Just follow instructions to update if you don't know how (they are always on first page of the thread where you get your downloads from).

Thank you for your answer, everything's back to normal
I'll make sure to follow the official tutorials next time.

only4dank said:
Once in your booted TWRP from 'fastboot boot twrp.img' ... Flash OOS (9.0.5 from xda forums), flash blu_spark-TWRP, reboot TWRP... Now you can root your phone (flash Magisk), flash a kernel. All should be good.
I would suggest in future, use these forums for download links, tutorials, and check this Q&A forum (literally 3-5 posts on first half of page 1 with similar problems. Just follow instructions to update if you don't know how (they are always on first page of the thread where you get your downloads from).
Click to expand...
Click to collapse
Good advice. I'd also like to add so everyone is aware, it's a good idea to disable all magisk modules before an update. Also disable your lockscreen pin, fingerprint... Basically any security. You can always re-enable these once updated. It just makes for less complications when updating. I'd also recommend downloading magisk modules outside of the app and keep them in a folder called magisk modules. That way, if for some reason magisk didn't retain the ones you downloaded after disabling and installing an oos update, you don't have to rely on your memory to look up\install them.

thejase said:
Good advice. I'd also like to add so everyone is aware, it's a good idea to disable all magisk modules before an update. Also disable your lockscreen pin, fingerprint... Basically any security. You can always re-enable these once updated. It just makes for less complications when updating. I'd also recommend downloading magisk modules outside of the app and keep them in a folder called magisk modules. That way, if for some reason magisk didn't retain the ones you downloaded after disabling and installing an oos update, you don't have to rely on your memory to look up\install them.
Click to expand...
Click to collapse
I never disable/uninstall Magisk modules. Nor do I disable lockscreen pin, fingerprint.
Theres no point at all. If flash things logically (correctly) you won't reboot your system without non-stock recovery, or no root.

only4dank said:
I never disable/uninstall Magisk modules. Nor do I disable lockscreen pin, fingerprint.
Theres no point at all. If flash things logically (correctly) you won't reboot your system without non-stock recovery, or no root.
Click to expand...
Click to collapse
There absolutely is a point. Many people have had encryption issues in twrp when updating. In addition, I myself have had a magisk issue where one of the modules wouldn't run properly when updating to pie and as a result, it didn't boot. Using a terminal magisk module uninstaller in twrp to disable the module fixed the issue. This is merely advice to eliminate all possible failures when updating. If it works for you without doing these things, mazel tov, but this is for those that have had issues and want to minimize the odds of that happening again.

thejase said:
There absolutely is a point. Many people have had encryption issues in twrp when updating. In addition, I myself have had a magisk issue where one of the modules wouldn't run properly when updating to pie and as a result, it didn't boot. Using a terminal magisk module uninstaller in twrp to disable the module fixed the issue. This is merely advice to eliminate all possible failures when updating. If it works for you without doing these things, mazel tov, but this is for those that have had issues and want to minimize the odds of that happening again.
Click to expand...
Click to collapse
Fair enough. But moving from Oreo to Pie is a little bit different then Pie OTA updates. I have 6-7 modules recently in Magisk - and never uninstalled Magisk or removed modules while updating Android Pie.
When I came from Oreo, I did a clean wiped system. To me, that makes sense - because it is a dramatic change in the system (whereas OTA updates for same android version are pretty minuscule).

only4dank said:
Fair enough. But moving from Oreo to Pie is a little bit different then Pie OTA updates. I have 6-7 modules recently in Magisk - and never uninstalled Magisk or removed modules while updating Android Pie.
When I came from Oreo, I did a clean wiped system. To me, that makes sense - because it is a dramatic change in the system (whereas OTA updates for same android version are pretty minuscule).
Click to expand...
Click to collapse
The only module I had to manually remove, because OOS refused to boot after an update, was "OOS Native Call Recording Enabler".
And before I knew that was causing it... I factory reset, then everything was fine until the next update xD
I even made a Backup/restore magisk data script, but seeing as it backed up/restored that module too it would still refuse to boot after an update.

ante0 said:
The only module I had to manually remove, because OOS refused to boot after an update, was "OOS Native Call Recording Enabler".
And before I knew that was causing it... I factory reset, then everything was fine until the next update xD
I even made a Backup/restore magisk data script, but seeing as it backed up/restored that module too it would still refuse to boot after an update.
Click to expand...
Click to collapse
Same. But if you install it with version 8.0 after the update, it works again. Just f.y.i..

noom4_5 said:
I got a new error when issuing "fastboot boot boot.img" after I rebooted to System from twrp:
```
Downloading 'boot.img'
OKAY [ 0.692s]
booting
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Finished. Total time: 0.719s
```
Click to expand...
Click to collapse
noom4_5 said:
Ok so now by restarting a couple of times to fastboot I successfully booted to official twrp using "fastboot boot.img" and it successfully decrypted my storage!!!
Now I think things are recoverable, how do I fix this bad boy? Reflashing last official oxygenos image could work?
Click to expand...
Click to collapse
Can you tell me which TWRP image you used to get past this issue? I have tried both 3.2.3-1 and 3.3.0-0 several times with zero luck this far. Thanks!

wwwryan said:
Can you tell me which TWRP image you used to get past this issue? I have tried both 3.2.3-1 and 3.3.0-0 several times with zero luck this far. Thanks!
Click to expand...
Click to collapse
Answered my own question but wanted to leave this here for others just in case it is helpful. Using twrp-3.2.3-x_blu_spark_v9.91_op6.img I was able to fastboot boot the img file and this version of TWRP offered to decrypt. From there first thing I did was adb pull my entire sdcard to my PC for save keeping.
My issue was a result of restoring from an earlier backup to recover some data. I had recently updated to 9.0.5 but accidentally deleted something I had no backup for so was restoring a previous TWRP back from 9.0.4. After the restore I couldn't boot the OS and all official version of TWRP would no longer offer to decrypt my data. Of course, I could not restore the backup I had just taken either since it was encrypted on the internal SD card. From now on I will just take TWRP backups to external storage via OTG USB and not even risk it.

Happened to me a few days ago
You can NOT recover your data. But you will be able to fix your phone.
Just do a Factory Reset from TWRP (Wipes Everything) and a wipe of system etc
Then just sideload or put the latest OOS back on the phone and install it.
Trust me, I have tried everything for trying to recover and decrypt the data... Somehow our phones did change the Encryption Keys from /data/unencrypted so there is no way to recover unless you can get the same key out of luck of using the encryption algorithm and salting process that Android uses.
https://imgur.com/y8ENw77
https://imgur.com/q7BPOCy

I've done this a few times. Actually... every time I update; save for the last two times. Just two notes that you already seem to have figured out:
1) Always remember turn off your active modules. (Just turn them off, you don't need to uninstall them.) Simply doing that seems to have fix OTA issues for me. I try to do it before I even download the update and definitely before I install it.
2) No matter how badly I foul up (except for the first time), I never wipe it when trying to fix it. Just side boot Blu Spark TWRP and flash the OS again. Boot it up once without root. Then go ahead to side boot Blu Spark TWRP again to root. I never install TWRP to the device at all. Even with Blu Spark, it seems to get iffy with me. If I want to flash something, I just let it wait until I'm home so I can side load Blu Spark.

Can't reboot to Recovery after upgrade to Android 10

Hello everyone,
As I mentioned in the title, since I upgraded to Android 10, can't boot to recovery.
Dowloaded latest version of the Adb kit, and while issuing
adb reboot recovery
the phone reboots but goes to normal boot.
Tried manually (power + vol down etc.) and when choosing Recovery - same thing happens.
Needless to say that my laptop is authorized debug device and phone is in debug mode etc. - I have done this many times before Android 10 update.
All I try to do is to sideload the latest OTA as I did many times before because my phone is rooted and the updates do not install automatically.
Pixel (First generation)
Rooted with Magisk
Bootloader unlocked
Stock recovery (using TWRP without installing it when flashing Magisk)
Hope somebody can advise. Obviously there is something new in Android 10 which has to be set (like the need for debugging authorization for example, which I already did).
Thank you
John

Im getting a similar problem. I get stuck on th Google logo screen. I cant hard-reset, recovery mode or boot, the only things that works is th barcode.

Android 10 changed something in the ramdisk that you can't install TWRP directly on the phone. You have to boot it via PC using "fastboot boot <insert twrp image name>.img"

You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck

junglism93 said:
You can try installing twrp to ramdisk. Put twrp 3.3.1-0.img in your devices storage and then fastboot twrp 3.3.0-0 (disable pin etc first) then once it's booted go to advanced and select install to ramdisk and select the 3.3.1-0.img and it should install it. You may get a not enough storage error on 10/Q (I did) bit worth a punt. Make a back up first as usual, if no good flash a fresh factory.img and see if that cures it and then restore your apps/data etcfrom your Google back up (if you use it)
Good luck
Click to expand...
Click to collapse
Thank you for the advice, however as I mentioned in my original post I don't want to install TWRP permanently , and the problem is that I cannot go to the stock recovery mode which has no connection to TWRP. There is something with Android 10 which changed since 9 and I'm interested to find what. Everything worked fine before the upgrade.
Also, the option to flash factory image and restore (I also have Titanium in addition to Google backup) is a too much of a hassle. I use this phone for real, not only to play with it.
Anyway, again thank you for your input.
John

Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.

I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.

junglism93 said:
Sorry mate, re read your OP. I just tried booting into the aosp recovery and got the same issue! My guess is its magisk as I could boot into the aosp recovery prior to installing it. Re flash or restore the previous boot.img or a stock boot.img and it should boot into aosp recovery again. Magisk must be installing to or patching the aosp recovery ramdisk and stopping it booting. Other than that just fastboot twrp and use that.
Edit: it's magisk, restored original images and it booted into aosp recovery first try.
Click to expand...
Click to collapse
You are right. I did open Magisk and from the uninstall options choosed "Restore images" (no need to do complete uninstall, which is the other option). After that I was able to boot in recovery etc. I guess this is what you meant in your PS. At the end re-flashed Magisk and all is back to normal.
I will alert the Magisk team about the issue (if they are not already aware).
Case closed.
Thanks again.
John

Master Cylinder said:
I've had no problems installing TWRP 3.3.0.0 normally after using an *.img file to get TWRP started. EDIT: and booting into it.
Click to expand...
Click to collapse
Please read my OP. I was clear that I DON'T want to install TWRP permanently and this was never the problem.
The problem is solved (kind of). See the other posts.
Thank you.
John

I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things

aholeinthewor1d said:
I thought TWRP wasn't compatible with Android 10 yet? I am seeing mixed things
Click to expand...
Click to collapse
It works just fine.

Mzprx said:
It works just fine.
Click to expand...
Click to collapse
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks

aholeinthewor1d said:
Are there steps for how to install somewhere? I keep reading that it's not working on the Pixel with Android 10. Thanks
Click to expand...
Click to collapse
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John

Mzprx said:
It is a mess. It works with Pixel (I have this one and can confirm) and supposedly Pixel 2. It won't work for brand new phones arriving with factory installed Android 10.
Read the following:
https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html#
After that, if you want to try, go to the page below to find instructions for your device. Note that the list is by manufacturer, so if you are looking for Pixel, it is under Google.
https://twrp.me/Devices/
Just in case - backup and have the factory image for your phone handy in case something goes wrong. For google phones you can download the image and see instructions here:
https://developers.google.com/android/images
Note that I never installed TWRP permanently, so I can't say if the permanent installation will work (I think it should, but not sure). Typically I just load TWRP and use it to flash pakages, but at the end I'm keeping the stock recovery.
Hope this helps. Good luck.
John
Click to expand...
Click to collapse
Thanks. Yea from what I can tell no one has had luck actually installing it on the Pixel with Android 10 yet. I'm familiar with how to fix everything if something goes wrong. I would try but others have already tried and failed. It won't install for them.

firstly, dont use whatever ****ty platform-tools you are using, get them from here.
secondly, you dont install recovery on android 10 yet, it doenst work. you have to just boot to twrp using `fastboot boot twrp.img` once you are in bootloader mode.

Help, I can flash and boot LineageOS but not OxygenOS

Hi, as the title explains I can flash and boot into lineage os but when I try to flash a stock OxygenOS signed flashable zip from this thread (https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-mirrors-official-oxygen-os-t3792244)
and when I boot to system, the screen doesn't show a boot logo, it just goes black for a few seconds before rebooting back to twrp (also if it helps, when it goes to twrp all the files are gibberish, I have to shut off the phone and boot into it from fastboot or I can't see any files).
This all started because I misunderstood the instructions and tried to flash an ota package which then broke the system, it's working now but I'd much rather use OOS as Lineage is missing a lot of the features I'm used to on Oxygen.
I've also tried the "flash-all-partitins-fastboot" from https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665 but unfortunately that gave the same issue, it just went back to recovery and wouldn't load OOS.
If anyone has any ideas on how to get back to oxygen that'd be super helpful! I'm considering using the MSM tool but I'd rather not have to start from scratch and lose all my files.

I'm just guessing, but there might be something wrong with your TWRP, did you try re-flashing it?

mati11233 said:
I'm just guessing, but there might be something wrong with your TWRP, did you try re-flashing it?
Click to expand...
Click to collapse
I should've clarified in the post, I mean all the files are gibberish (as in not decrypted I think?) but when I
Code:
fastboot boot twrp.img
it works fine and I can see all the files.
I've probably tried flashing it 4 times through twrp but every time it just does the same thing, boot to system just shows a black screen for a few seconds then reboots to twrp.
I'd love to use blu_spark like everyone recommends but I can't find the blu_spark recovery for the op6, only their kernel.

The reason why it's gibberish is because your device is encrypted and you need to input the password in the twrp to be able to access it. Seems the twrp doesn't detect the encryption correctly so there might be something wrong with it.
Here is the bluespark twrp https://github.com/engstk/android_device_oneplus_enchilada/releases

mati11233 said:
The reason why it's gibberish is because your device is encrypted and you need to input the password in the twrp to be able to access it. Seems the twrp doesn't detect the encryption correctly so there might be something wrong with it.
Here is the bluespark twrp https://github.com/engstk/android_device_oneplus_enchilada/releases
Click to expand...
Click to collapse
I just tried with blu_spark and the same thing happens but I realised something else, twrp only doesn't work on slot A.
If I see that it didn't decrypt the files, I can set B to active, reboot to recovery, and it works perfectly.
I noticed after one of the failed boots it switched the active slot to B even though I had set it to A before flashing. So every time it doesn't show the logo or anything, it sets the active slot from A to B and reboots to recovery.
Also I just looked and from the Backup page, it shows 2.7 GB for system on slot A and 1.7GB on slot B so I'm going to try wiping both and reflashing the flashable signed zip on each then twrp.
UPDATE: Just did that and the twrp installer was giving an error saying unsupported android version so I looked and system is only 4MB after flashing that package (OnePlus6Oxgygen_22_OTA_034_all_...zip), I'm trying an older one (...OTA_026...zip) to see if that actually works.
So I tried with the older one and lineage and they both still left the system partition at 4MB and the blu_spark twrp installer isn't detecting an android version. The system image partition is at 2.6GB if that means anything.
Oh wait more update, I'm dumb and shut off the phone while taking the case off (got stuck and it was pushing the power button) and even though the twrp installer couldn't detect anything and twrp said No OS installed when trying to boot to system, lineage just started up, no problem. I am very confused I miss when there was one system partition.

How are you flashing the OS?

mati11233 said:
How are you flashing the OS?
Click to expand...
Click to collapse
I'm using twrp, blu_spark and normal, and both have the same result. They can flash lineage and it runs fine, but oxygen refuses to boot and just switches the active slot and goes to recovery instead.
I also tried the fastboot rom flashing thing from the thread I linked to in the OP and it's the same thing, just goes back to recovery and wont boot.
P.S. I'm currently copying over /sdcard to an external drive and if I can't figure out how to fix this by the time that's done, I'll just use MsmDownloadTool and start over.

And you are wiping each time before flashing it, right? If it is the case then the download tool is probably the easiest way to go about it, rather than spending days troubleshooting it.

mati11233 said:
And you are wiping each time before flashing it, right? If it is the case then the download tool is probably the easiest way to go about it, rather than spending days troubleshooting it.
Click to expand...
Click to collapse
I've tried it with and without wiping and it always seems to do the same thing either way, works with LOS not with OOS. Thanks for the help! but yeah I think I'm just going to end up using the download tool once everything's over.