Database Info

Couldn't install system update (november security patch)

I have just received the OTA and it is failing to install...
Anybody else facing this issue? Any ideas on how to fix it?
I have my Pixel 2 rooted right now, not sure if this can affect OTA?

luizffgarcia said:
I have my Pixel 2 rooted right now, not sure if this can affect OTA?
Click to expand...
Click to collapse
Being rooted is your issue

krelvinaz said:
Being rooted is your issue
Click to expand...
Click to collapse
What is the easiest way around it then? Do i have to download the factory image and flash it losing everything i have configured? Or is there another way?

https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Follow them steps
Nothing seems to work for me though i cant install ota no matter what but hopefully it should work for you.
It has for everyone else!

UpGrad3 said:
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Follow them steps
Nothing seems to work for me though i cant install ota no matter what but hopefully it should work for you.
It has for everyone else!
Click to expand...
Click to collapse
Thanks but this also does not work for me, it starts step 1 but then the installation fails...
Any other options?
EDIT: LOL and now i lost magisk and root

luizffgarcia said:
Thanks but this also does not work for me, it starts step 1 but then the installation fails...
Any other options?
EDIT: LOL and now i lost magisk and root
Click to expand...
Click to collapse
I'm in the same boat...dies at step 1. Look familiar?
https://forum.xda-developers.com/showpost.php?p=74518728&postcount=53
Only I didn't lose root, as I re-installed Magisk before rebooting.

JayBlack_686 said:
I'm in the same boat...dies at step 1. Look familiar?
https://forum.xda-developers.com/showpost.php?p=74518728&postcount=53
Only I didn't lose root, as I re-installed Magisk before rebooting.
Click to expand...
Click to collapse
Yeah i sideloaded the OTA and it worked, but now i am struggling to put back snoke and magisk...
Every time i try i get stuck in the google logo, not sure whats going wrong

luizffgarcia said:
Yeah i sideloaded the OTA and it worked, but now i am struggling to put back snoke and magisk...
Every time i try i get stuck in the google logo, not sure whats going wrong
Click to expand...
Click to collapse
That happened the first time I tried to root. Had to flash the factory image and start over. Guess I could do that...but seems there has to be an easier way. I'm really curious why the method in that guide doesn't work for me.

Does flashfire work to install the OTA?

luizffgarcia said:
Thanks but this also does not work for me, it starts step 1 but then the installation fails...
Any other options?
EDIT: LOL and now i lost magisk and root
Click to expand...
Click to collapse
JayBlack_686 said:
I'm in the same boat...dies at step 1. Look familiar?
https://forum.xda-developers.com/showpost.php?p=74518728&postcount=53
Only I didn't lose root, as I re-installed Magisk before rebooting.
Click to expand...
Click to collapse
Download the full factory image. Open the flash all bat file with notepad and edit out the -w and save it. Then run it. That will flash the full factory image but leave apps and data in place.
Then you reroot it.

TonikJDK said:
Download the full factory image. Open the flash all bat file with notepad and edit out the -w and save it. Then run it. That will flash the full factory image but leave apps and data in place.
Then you reroot it.
Click to expand...
Click to collapse
Thanks. When I re-root, do I need to do the whole patch boot image process again? Or should I reuse the patched_boot.img that I used when I rooted the first time?

JayBlack_686 said:
Thanks. When I re-root, do I need to do the whole patch boot image process again? Or should I reuse the patched_boot.img that I used when I rooted the first time?
Click to expand...
Click to collapse
Redo it, otherwise you are a month behind on the boot IMG.

TonikJDK said:
Redo it, otherwise you are a month behind on the boot IMG.
Click to expand...
Click to collapse
Thank you. One last question: when I rooted, I used the snoke kernel and pointed to that .img file when patching the boot image (no reason, other than that's what everyone seemed to be using when root first happened). It sounds like this time, I should get the full factory image, extract, grab the boot.img from within that and patch THAT to be up to date. Correct?

JayBlack_686 said:
Thank you. One last question: when I rooted, I used the snoke kernel and pointed to that .img file when patching the boot image (no reason, other than that's what everyone seemed to be using when root first happened). It sounds like this time, I should get the full factory image, extract, grab the boot.img from within that and patch THAT to be up to date. Correct?
Click to expand...
Click to collapse
Correct, you can use whatever boot IMG you want. Snoke may be updated to November... don't know...bit if it is and you like it use it.

Waiting for answers. I finally succeeded with rooting my xiaomi mi a2 lite, everything works perfect, I was so excited to install Xposed but then my phone started to lag AF. I uninstalled it and then the update show up in the notification bar, great but "couldn't install system update". Is it because of the root or TWRP?

Bootloop headache

Hello All
Just got my OP 6...coming from 5T I have 5.1.9 installed
I unlocked bootloader
Installed twrp 3.2.2.0
Installed boot.img.... From Max Lee site
Installed Magisk 16.4
All good went to reboot system and now stuck in bootloop??
Is the boot.img different for 5.1.9?
Anybody have any ideas to help? Thanks in advance!

skyeking69 said:
Hello All
Just got my OP 6...coming from 5T I have 5.1.9 installed
I unlocked bootloader
Installed twrp 3.2.2.0
Installed boot.img.... From Max Lee site
Installed Magisk 16.4
All good went to reboot system and now stuck in bootloop??
Is the boot.img different for 5.1.9?
Anybody have any ideas to help? Thanks in advance!
Click to expand...
Click to collapse
why would you install boot.img from some site that may or may not be for our phone.
you could just reinstall stock boot or choose custom kernel from the forms here and get something that works like
cleanslate https://forum.xda-developers.com/oneplus-6/development/kernel-cleanslate-v1-7-0-oo-t3797668
elementalx https://forum.xda-developers.com/oneplus-6/development/kernel-elementalx-op6-1-00-t3799054
flash kernel https://forum.xda-developers.com/oneplus-6/development/op6-flash-kernel-1-00-t3801652
these are some of the custom kernels for our OP 6.

MrSteelX said:
why would you install boot.img from some site that may or may not be for our phone.
you could just reinstall stock boot or choose custom kernel from the forms here and get something that works like
cleanslate https://forum.xda-developers.com/oneplus-6/development/kernel-cleanslate-v1-7-0-oo-t3797668
elementalx https://forum.xda-developers.com/oneplus-6/development/kernel-elementalx-op6-1-00-t3799054
flash kernel https://forum.xda-developers.com/oneplus-6/development/op6-flash-kernel-1-00-t3801652
these are some of the custom kernels for our OP 6.
Click to expand...
Click to collapse
Max's site is "High on Android" I followed his boot loader unlock and OP 6 root plan.....it was for the OP6....but I don't know
if the image is the same on 5.1.7 to 5.1.9 ? That's the only thing that my novice mind can thing the problem is?
I don't really want a custom kernel..I keep things stock, just root for a few apps adaway, TI backup...... But thanks!

skyeking69 said:
Max's site is "High on Android" I followed his boot loader unlock and OP 6 root plan.....it was for the OP6....but I don't know
if the image is the same on 5.1.7 to 5.1.9 ? That's the only thing that my novice mind can thing the problem is?
I don't really want a custom kernel..I keep things stock, just root for a few apps adaway, TI backup...... But thanks!
Click to expand...
Click to collapse
Use your backup then? Or are you another one that didn't do any? :s (yes we had a few last couple of days)
https://androidfilehost.com/?fid=5862345805528053217
Stock kernel, latest

whizeguy said:
Use your backup then? Or are you another one that didn't do any? :s (yes we had a few last couple of days)
https://androidfilehost.com/?fid=5862345805528053217
Stock kernel, latest
Click to expand...
Click to collapse
YES!! I was that guy!!! Funny I always made a backup on my 5t...but this was new nothing on it I wasn't thinking!!
Geez now my twrp is freezing on the opening screen???
Thanks!!

**** happens I guess
Try a newer version of twrp if you can, via fastboot first and then flash (like you did before)

whizeguy said:
**** happens I guess
Try a newer version of twrp if you can, via fastboot first and then flash (like you did before)
Click to expand...
Click to collapse
what is the newest version ?

https://dl.twrp.me/enchilada/
Just saw that that was the latest.. That you had installed before.. Hmm.

whizeguy said:
https://dl.twrp.me/enchilada/
Click to expand...
Click to collapse
Thank you very much!!!! worked!! it must have been the boot.img Cheers!!!!

skyeking69 said:
Thank you very much!!!! worked!! it must have been the boot.img Cheers!!!!
Click to expand...
Click to collapse
This phone does not work like the 5T or other phones without A/B partitions. There is a lot of bad advice out there. You're better off sticking with the guides posted here.

iElvis said:
This phone does not work like the 5T or other phones without A/B partitions. There is a lot of bad advice out there. You're better off sticking with the guides posted here.
Click to expand...
Click to collapse
I don't really understand the a/b partitions? I know its for seamless updates, but don't really understand. Advice here is the best for sure.
Max Lee's method works but he had an outdated boot.img ...once I got the correct one for 5.1.9 all went well...twrp, magisk...
plus and I hate to say this..all I have now is a Macbook and he had directions for that...

skyeking69 said:
I don't really understand the a/b partitions? I know its for seamless updates, but don't really understand. Advice here is the best for sure.
Max Lee's method works but he had an outdated boot.img ...once I got the correct one for 5.1.9 all went well...twrp, magisk...
plus and I hate to say this..all I have now is a Macbook and he had directions for that...
Click to expand...
Click to collapse
All you need to know about A/B is here: https://forum.xda-developers.com/oneplus-6/how-to/guide-noobs-guide-to-b-partitions-op6-t3816123
This phone is really not that hard to mod, even with a MacBook. I've used Macs for years for rooting. It's just a matter of knowing how to use Terminal . . . that's it.

why are you flashing the boot img?...

Because the boot.img I originally use wasn't for 5.1.9..
I flashed the correct one and all good...

skyeking69 said:
Because the boot.img I originally use wasn't for 5.1.9..
I flashed the correct one and all good...
Click to expand...
Click to collapse
The reason we ask about boot.Img is b/c flashing magisk would have patched your boot.img. The only reason for flashing boot is for custom kernels.

MrSteelX said:
The reason we ask about boot.Img is b/c flashing magisk would have patched your boot.img. The only reason for flashing boot is for custom kernels.
Click to expand...
Click to collapse
I'm not sure... But when I installed the boot.img for 5.1.9 then Magisk 16.4 it fixed the bootloop

skyeking69 said:
I'm not sure... But when I installed the boot.img for 5.1.9 then Magisk 16.4 it fixed the bootloop
Click to expand...
Click to collapse
Everyone else here know that the reason for the boot loop is b/c you flashed an older boot.img then the system was expecting. What we are trying to say is if you did not flash that boot.img in the first place, This problem never would have happened.

【HELP!】Installed a module in Magisk Download manager and now i'm f*****

Sup guys, i had this problem with the SafetyNet Check that always kept failing, done some tutorials here at the forum but none of them worked, so i gave up... yesterday i was searching for some modules at the download page in the Magisk Manager app and found a module that was supposed to correct SafatyNet problema, after that installation my Magisk don't want to open anymore, all my modules still installed but i can't open the app anymore, i rooted my cellphone without TWRP so i can't use it to manage the dependencies of the app... any suggestion?
obs.: I'm not using TWRP cuz i just keep having a problem at the installation, i'm runnig the last version of the Android Pie OS (Beta 3)

You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.

DiGtal said:
You could temporarily boot into TWRP via ADB and a PC and flash the uninstaller.
Click to expand...
Click to collapse
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.

The Marionette said:
He can boot it through fastboot, adb push the uninstaller and flash it.*
But isn't the safetynet fix just a build.prop tweak?
He can technically adb pull the build.prop, fix it and put it back in. Or just take a working build.prop from a fellow OB3 user ( me included ) and push it into the system through adb.
Click to expand...
Click to collapse
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.

tabletalker7 said:
I think the OP mentioned the problem they are having is from a Magisk module that is incompatible with the OP6. My recommendation, without TWRP on the phone, might be a Fastboot Rom to get your phone functional again.
Click to expand...
Click to collapse
I know that and the OP probably does too, but I guess they don't want to lose their current data?

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
I don't know if that can be helped at this point. That bad Magisk module may have made that decision for him

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk

s3nn4 said:
That's right, i know that i can fix this issue just installing the ROM again but i don't want to lose my data, i just want to delete a specific module from Magisk
Click to expand...
Click to collapse
restore stock boot.img. no root, no mods to load. fix it then reroot.

You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.

mdl054 said:
You don't need to restore. Follow this guide: https://forum.xda-developers.com/apps/magisk/module-core-mode-bootloop-solver-modules-t3817366
It's called CoreOnlyMode4Magisk and it's flashed through TWRP. Magisk modules are systemless and this module will fix your problem.
Click to expand...
Click to collapse
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3

MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Oh sorry I missed that part

You can use the modified boot.img with TWRP preinstalled from the OB3 thread:
https://forum.xda-developers.com/showpost.php?p=77390204&postcount=2

Just reflash OB3 from system updater and that will get rid of root and also keep your data. Then start over.
Sent from my OnePlus6 using XDA Labs

The Marionette said:
I know that and the OP probably does too, but I guess they don't want to lose their current data?
Click to expand...
Click to collapse
MrSteelX said:
he does not have twrp installed, but your way would work as well. the choice is up to op then to make.
http://www.mediafire.com/file/5h1hzimcj1irbn5/stockboot.img stock boot.img for OB3
Click to expand...
Click to collapse
Already fixed it, installed the last version of blu spark TWRP along with the Magisk 17.2, all perfect, had a problem with my OS at the beginning but just flashed again and did all the process to root, thanks for your help!

Next time don't be a twrp and use twrp

dgunn said:
Next time don't be a twrp and use twrp
Click to expand...
Click to collapse
The last update wouldn't let me install it, the Blu stuff made my day when I saw the compatible update

Warning - Notchbarkiller Magisk Module!

Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.

That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk

wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.

Maj3sty said:
That's why I bought this mobile with stock Android to be sure I'm not install something on it and the truth it's not worth to change something on it.
This mobile work pretty good without needing to root it.
No offense only my opinion.
Thanks
Mi A2 Lite using Tapatalk
Click to expand...
Click to collapse
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom

For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!

Voodoojonny said:
For anyone who gets bootloops caused by a magisk module: Just flash back stock kernel! Then Magisk is gone and the module doesn´t work too. You can delete the module from your magisk manager and root again - voilla!
Click to expand...
Click to collapse
I tried it and doesnt work. It seems the module changed any files in system(via root).

wenna.speedy said:
I dont think so. you havent right, because of magisk. Did you ever try viper4android? Its really some kind of magic! this is only one case. no root = no lot of great stuff. If anything bad happened, you have ever last option = flash vanilla rom
Click to expand...
Click to collapse
Nice try, but looks like you are not the only person with the same issue! I'm using Jetaudio and I have great sound with my JBL (Bluetooth) & Sennheiser wired headsets. I'm pass!!!
Mi A2 Lite using Tapatalk

lbsilva said:
Same happened to me on Android Pie, it completely broke my phone and when restarting it I had bootloop as well.
Had to flash ROM from scratch.
Click to expand...
Click to collapse
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help

hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!

Voodoojonny said:
Did you place system.img into your fastboot folder? It sounds like fastboot can´t find the file you want to flash!
Click to expand...
Click to collapse
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?

hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
You can try install twrp and mount internal storage. I dont know if exists new version with working mounting.

hckrm said:
I get booloop from this module, now when i try to flash system, i get error: cannot load '.\system.img'. Pls i need help
Click to expand...
Click to collapse
Did you try using MiFlashTool?

hckrm said:
yes, i have tried to flash the whole rom (except userdata) from .bat script of the official pie rom. But i get bootloop again. I have a lot of important data in my phone, is there a way to resolve without touching data?
Click to expand...
Click to collapse
Hmm, as told above, then your only option is a backup with twrp. If you can't decrypt data with twrp (after you installed it - not booting) you can try to boot to slot b - that sometimes help. Just select under reboot in twrp or type "fastboot set_active b"...

wenna.speedy said:
Be careful. Yesterday I have installed this module on my pie rom and had bootloop when I tried to uninstall it. Nothing cant solve this issue, I had to flash whole pie rom.
Click to expand...
Click to collapse
There is no wipe required, I just got caught in the loop as well.
Two things you need:
-TRWP installed
-Uninmod installed (magisk module remover)
1. If you are stuck in the loop, boot into fastboot,
- connect your pc and run ADB & fastboot cmd, run the command fastboot boot recovery.img(or your TRWP image) and run TRWP
2. Download Uninmod zip, transfer to phone. https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242&nocache=1
- Use TWRP to install Uninmod,
- remove the Notchkiller mod
- credits to veez21
3. find this file overlays.list and delete it from /data/resource-cache/overlays.list https://github.com/Magisk-Modules-Repo/NotchBarKiller/issues/3
- credits to MatChung
Reboot and there was like a minute of delay on same boot screen, but then it should boot fine.
If you are not stuck in the loop but just installed the module:
-remove the module in magisk
-find the file and delete it.
TLDR: remove the Notchbarkiller mod and remove overlays.list file. Reboot!
Hope it works. It did for me. Poco F1

I flashed this madule last night and found that it break calls. Could not make and receive phone calls. Huawei P20 Pro with EMUI 8.1 running.

Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw

D1stRU3T0R said:
Guys don't flash that LITERALLY SHIET module. It's bricking phones, i dirty flashed my rom and still couldn't recover it! I used Poco btw
Click to expand...
Click to collapse
Written in the first post...

wenna.speedy said:
Written in the first post...
Click to expand...
Click to collapse
I know...

Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853

SnoopDoggyStyleDogg said:
Strange, I was using the January update when I first installed it and everything worked fine, no issues what so ever. I haven't tried it on the latest update but xiaomi's update might have messed the module. There's no reason what so ever to blame the module for not working on the latest update as they tend to break things. Just report back to the developer with something helpful like a logcat instead of making useless threads.
As of the bootloop there's no reason to wipe your data or reflash the ROM unless you have to. Just boot up in twrp and flash the magisk uninstaller which might be in the Magisk Manager folder or just search it online. Another way to do it is just to mount magisk in twrp and delete the module. Learn about how to mount magisk here: https://forum.xda-developers.com/apps/magisk/magisk-mount-resize-img-t3675853
Click to expand...
Click to collapse
UPDATE: This thread is a false alarm as I managed to install the module on the March update and the only crash I get is from google play services with no bootloop and everything working. Maybe the OP has another phone and except that a module that is on the Mi A2 Lite thread should work on any phone or he's done something wrong. I will attach some screenshots to confirm that the module is indeed working and OP's post is a false alarm for stock A2 Lite ROMs (No custom ROM and not other phones)
NOTE: As you can see in the YouTube screenshot there's no black back on the left side of the screen as it should be without the module installed

T-Mobile Root

Has anyone successfully rooted their T-Mobile variant as of yet? My bootloader unlock token should be available in a couple hours, and I'm trying to decide which is the best method. I was thinking of going with patching the boot.img myself, however I can't find a full ROM zip of 9.5.5 (which I'm on now). The next choice is obviously TWRP...I'm just hesitant because of the encryption issue. Does anyone know if formatting data and then moving files back to my internal storage will allow me to decrypt, just as it did on the 6T? Thanks in advance

sabrdawg said:
Has anyone successfully rooted their T-Mobile variant as of yet? My bootloader unlock token should be available in a couple hours, and I'm trying to decide which is the best method. I was thinking of going with patching the boot.img myself, however I can't find a full ROM zip of 9.5.5 (which I'm on now). The next choice is obviously TWRP...I'm just hesitant because of the encryption issue. Does anyone know if formatting data and then moving files back to my internal storage will allow me to decrypt, just as it did on the 6T? Thanks in advance
Click to expand...
Click to collapse
Mine should be here today. And I'll tell you my plan.
I'm going to try to flash twrp and try to get the stock img files from the unmodified slot. Then I will feel safe. To do anything

Well, I did it! I unlocked my bootloader and flashed TWRP! I then formatted data, and transferred the TWRP installer and Magisk to internal storage. I flashed both, and rebooted to recovery. Both files were still there, and did not get encrypted! Now, my wifi and sound seem to be broken, but I did see something about that somewhere else...now to find it, hah!

sabrdawg said:
Well, I did it! I unlocked my bootloader and flashed TWRP! I then formatted data, and transferred the TWRP installer and Magisk to internal storage. I flashed both, and rebooted to recovery. Both files were still there, and did not get encrypted! Now, my wifi and sound seem to be broken, but I did see something about that somewhere else...now to find it, hah!
Click to expand...
Click to collapse
Did it come exactly 7 days later

twinnfamous said:
Did it come exactly 7 days later
Click to expand...
Click to collapse
Mine came 7 days later almost exactly to the minute

ScottOtis said:
Mine came 7 days later almost exactly to the minute
Click to expand...
Click to collapse
I still got an HR left then.
I'll make sure to post all img files I extract if no one else does.

It did! About 10 minutes later than the time I applied for it Now, I rebooted to recovery again, and now I don't see my files anymore I guess formatting data DIDN'T fix decryption. Now to get my sound and wifi working again...

Figured I'd try formatting data a second time. It's worked for me on the 6T in the past

I think your going to need the boot.img to restore WiFi and sound.

Xshooter726 said:
I think your going to need the boot.img to restore WiFi and sound.
Click to expand...
Click to collapse
Where can I get it for T-Mo? I'm wondering how I lost them :\

sabrdawg said:
Where can I get it for T-Mo? I'm wondering how I lost them :\
Click to expand...
Click to collapse
Go into twrp.
Did u use installer or flash twrp img

twinnfamous said:
sabrdawg said:
Where can I get it for T-Mo? I'm wondering how I lost them :
Click to expand...
Click to collapse
Go into twrp.
Did u use installer or flash twrp img
Click to expand...
Click to collapse
I flashed the img, and then installer while in TWRP, thinking I needed to do that to keep TWRP (which Iater learned I didn't as I had flashed TWRP, not just booted it).

sabrdawg said:
I flashed the img, and then installer while in TWRP, thinking I needed to do that to keep TWRP (which Iater learned I didn't as I had flashed TWRP, not just booted it).
Click to expand...
Click to collapse
I'm going to upload a boot.img give me a few. Then just flash it to both slots

Interested in this thread bc of possible decrypt solution

twinnfamous said:
I'm going to upload a boot.img give me a few. Then just flash it to both slots
Click to expand...
Click to collapse
Omg, you're a lifesaver!

sabrdawg said:
Omg, you're a lifesaver!
Click to expand...
Click to collapse
I'm real sorry my bootimg got twrped by accident. So until we get a stock.boot we only have stock system and vendor img files from twrp backup.

twinnfamous said:
I'm real sorry my bootimg got twrped by accident. So until we get a stock.boot we only have stock system and vendor img files from twrp backup.
Click to expand...
Click to collapse
Hmm...shoot. well, maybe someone will come up with something soon enough. Thx for trying, though!

twinnfamous said:
I still got an HR left then.
I'll make sure to post all img files I extract if no one else does.
Click to expand...
Click to collapse
Im going to get my unlock bin hopefully this afternoon. What is the best way to do that before messing with anything?

Try flashing this patched 9.5.5 boot.img . The boot image has to match the same version your currently on. From your screen shots it looks like your on 9.5.5 so it might be your best bet in restoring your Sound and Wifi.
https://www.dropbox.com/sh/0nnqtvfuhbavrl5/AADyGWwA2UmIi_ivbQ7MGHSsa?dl=0

Xshooter726 said:
Try flashing this patched 9.5.5 boot.img . The boot image has to match the same version your currently on. From your screen shots it looks like your on 9.5.5 so it might be your best bet in restoring your Sound and Wifi.
https://www.dropbox.com/sh/0nnqtvfuhbavrl5/AADyGWwA2UmIi_ivbQ7MGHSsa?dl=0
Click to expand...
Click to collapse
Thx! I was able to fix sound and wifi by flashing SkyDragon kernel. I appreciate your help