Database Develop

[Q] Bricked Nokia 521 Lumia Stock ROMs?

Hello I have a Nokia 521 Lumia for T-Mobile and for some reason the phone bootloops when plugged into a charger. I am very familiar with restoring an Android and/or iOS, but have never done a restore for a Windows 8 phone such as this one. I am just wondering where I can find stock files and instructions on how to get this phone working again? Thanks!

simply solution for bricked Nokia device
http://mynokiablog.com/2013/10/11/how-to-easily-fix-the-lumia-reset-spinning-cogs-at-home/

dxdy said:
simply solution for bricked Nokia device
http://mynokiablog.com/2013/10/11/how-to-easily-fix-the-lumia-reset-spinning-cogs-at-home/
Click to expand...
Click to collapse
I don't think this is my exact issue, but I will give it a try. The reason I say that is because I don't even get rotating cogs, just "Nokia" then bootloop and repeat...

Have you try Hard Reset?

Yes first try the Hard Reset.
If that does not work, you can also try to flash with Nokia Care Suite.

anaheiim said:
Yes first try the Hard Reset.
If that does not work, you can also try to flash with Nokia Care Suite.
Click to expand...
Click to collapse
How exactly do you perform a hard reset on this phone?

Wow, I wonder where I could learn that??

bricked
Hi, after doing a Hard Reset, the cogs just turn (has been doing this for about 7 hours).
I've tried all the suggestions on here, but the soft reset doesn't work and I can't flash it using the Nokia "Product Support Tool" (Nokia Care Suite) as the "Firmware Repository" is password protected, so I can't download the Firmware required (Vodafone UK, Nokia Lumia 920 Black). help

BerriesWithMint said:
Hi, after doing a Hard Reset, the cogs just turn (has been doing this for about 7 hours).
I've tried all the suggestions on here, but the soft reset doesn't work and I can't flash it using the Nokia "Product Support Tool" (Nokia Care Suite) as the "Firmware Repository" is password protected, so I can't download the Firmware required (Vodafone UK, Nokia Lumia 920 Black). help
Click to expand...
Click to collapse
You can flash with Nokia Care Suite PST, it works. *Follow simply and correctly all steps*.

BerriesWithMint said:
Hi, after doing a Hard Reset, the cogs just turn (has been doing this for about 7 hours).
I've tried all the suggestions on here, but the soft reset doesn't work and I can't flash it using the Nokia "Product Support Tool" (Nokia Care Suite) as the "Firmware Repository" is password protected, so I can't download the Firmware required (Vodafone UK, Nokia Lumia 920 Black). help
Click to expand...
Click to collapse
Hi there, while Anaheiim method would work too it is somewhat more cumbersome, Nokia developed a tool specially for sittuations like yours, simply download Nokia Software Recovery Tool connect your device to PC and start the program, then simply press install, the tool will do all for you, no interactions needed.

VSparxx said:
Hi there, while Anaheiim method would work too it is somewhat more cumbersome, Nokia developed a tool specially for sittuations like yours, simply download Nokia Software Recovery Tool connect your device to PC and start the program, then simply press install, the tool will do all for you, no interactions needed.
Click to expand...
Click to collapse
And that tells you he does not want unbrand same time?

anaheiim said:
And that tells you he does not want unbrand same time?
Click to expand...
Click to collapse
He didn't mention anything about debranding, if he does want to unbrand, then indeed go Anaheiim route.

last of the lumia

I have looked and looked to no avail, is it no longer possible to flash Lumia firmware through the Nokia Care Suite anymore? I can not seem to find the RM-820 in the open product. Everything tutorial I have seen says to find it in there I did see a comment in a thread where someone said that they didn't think Nokia is allowing that anymore. Is this true? I have the spinning cogs so I wanted to flash the firmware...
So I'm stuck and all help on the internet seems outdated. Is there something I'm missing?

just read forum... there is few ways to download firmware....
http://forum.xda-developers.com/showthread.php?t=2515453

there is a new tool released by nokia that is supposed to help recover / flash phones if they become stuck during boot or flash.
From memory it is called nokia software recovery tool. maybe you could try that if you can find it. I read about it on a site lastnight but can not remember where i saw the info about.
Google may help or it may have even been on here..
Chris

CBDSonline said:
there is a new tool released by nokia that is supposed to help recover / flash phones if they become stuck during boot or flash.
From memory it is called nokia software recovery tool. maybe you could try that if you can find it. I read about it on a site lastnight but can not remember where i saw the info about.
Google may help or it may have even been on here..
Chris
Click to expand...
Click to collapse
I downloaded and installed Nokia Care Suite on a Windows 8.1 PC just last night (EST in New York). I then used to install the Amber update onto a RM-878 that I just bought from Amazon - worked flawlessly.
Instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2515453

I have installed pc suite for Lumia 520 ...but i am not getting usb connect option...
can anyone have idea?

docfreed said:
I downloaded and installed Nokia Care Suite on a Windows 8.1 PC just last night (EST in New York). I then used to install the Amber update onto a RM-878 that I just bought from Amazon - worked flawlessly.
Instructions in this thread: http://forum.xda-developers.com/showthread.php?t=2515453
Click to expand...
Click to collapse
That is exactly what I am talking about. I have read the thread, followed the thread up until it say under product type. Under the sim tray it says RM-820 and there isn't a RM-820 in there, thus this question got asked. I'm not asking for someone to hold my hand through this, I just wanted to know if the RM-820 is or isn't supported with Nokia Care Suite. I know that the software works, flawlessly even, not saying it didn't. I have the firmware downloaded don't need the firmware. Just wanted to know if the Lumia was still supported by Nokia Care Suite, if I was missing something obvious.

chasingeuphoria said:
That is exactly what I am talking about. I have read the thread, followed the thread up until it say under product type. Under the sim tray it says RM-820 and there isn't a RM-820 in there, thus this question got asked. I'm not asking for someone to hold my hand through this, I just wanted to know if the RM-820 is or isn't supported with Nokia Care Suite. I know that the software works, flawlessly even, not saying it didn't. I have the firmware downloaded don't need the firmware. Just wanted to know if the Lumia was still supported by Nokia Care Suite, if I was missing something obvious.
Click to expand...
Click to collapse
What Phone do you have - reason I ask is that the original thread is a little confusing - there is of course a Lumia 820 but its actual Product Type is RM-824 and if you use the 824 Product Type from this thread:Nokia Lumia 820 Product Code (Product Type RM-824)
at http://forum.xda-developers.com/showpost.php?p=49364933&postcount=10 it shows dozens of codes to use for the Nokia Care Suite depending on country and carrier.

docfreed said:
What Phone do you have - reason I ask is that the original thread is a little confusing - there is of course a Lumia 820 but its actual Product Type is RM-824 and if you use the 824 Product Type from this thread:Nokia Lumia 820 Product Code (Product Type RM-824)
at http://forum.xda-developers.com/showpost.php?p=49364933&postcount=10 it shows dozens of codes to use for the Nokia Care Suite depending on country and carrier.
Click to expand...
Click to collapse
It is a Lumia 920 product code RM-820 I saw the product code on that little pull out thing under the Sim tray
http://forum.gsmhosting.com/vbb/f60...ting-care-suite-download-1660094/#post9434336

Thor2 gives error 84000(0x14820) while flashing L925(RM910), ERR CONNECTION NOT FOUND

I have a L925 (RM-910, Code 059S9S8), it stuck while upgrading to win 10 TP. I used WPRT to revert to win 8.1. Initially, WPRT detected the device and tried emergency driver or something which failed and since then my phone is not detected by WPRT, no response if the power and vol- buttons are held, but windows key flashes randomly.
I tried the un-bricking method mentioned in the original post, at the point where they suggest to uninstall the QHSUSB driver, i uninstalled it and continued the procedure until FLASHING THE BOOTLOADER step. It gave me the subject error and code, i retried several times and found two reasons suggested by people for the said error:
1. Incorrect drivers
2. Incorrect files (.hex)
When i retried the step of uninstalling the QHSUSB drivers, i found out that my system doesn't have these installed nor is my phone detected as QHSUSB device.
I have been trying to find if any solution for the above mentioned error has been stated anywhere but i couldn't find one. I have been trying to flash the bootloader (i am an accountant by profession and i don't even know the ABC of programming and this stuff but i learned quite much when WPRT bricked my L925), the subject error appears every time. I have made my .bin file, my own .hex file, .mbn file all for my model but i am still unable to figure out the real issue.
In the original post of un-bricking L925 without JTAG, it was mentioned that the subject error means that wrong drivers are installed. I am using windows 10 on my laptop, and the drivers available for win 7 & 8 are older than the ones on win 10 and when i try to install the drivers downloaded from the link provided in the original post, i got a prompt from win 10 that NEWER VERSION ALREADY INSTALLED.
I kept searching the forums and found someone mentioned that the subject error also appears due to incorrect .hex files and the also mentioned a way to correct the download-available .hex for my model, so i corrected the downloaded ones and even double checked it with my .bin files and i am now sure that i am using the correct files.
So,
1. My drivers are updated versions of those suggested in the post.
2. My .hex file matches with my .bin file (.bin was created using cmd prmpt and from my model)
I cannot find anyother solution or reason for the error which appears.
Any help or guidance from you guys will be really appreciated.
P.S. After failure on windows 10, I have also tried the whole procedure on win 8.1 and the results were no different.
Hoping to get some guidance or help
Yasir H. Qureshi

help anyone?? been more than two weeks since i am trying to get my cell back to work... :|

Samsung SGH-T899M will not boot

Hi, this is my first post on this forum. I am not really all that tech savy, but I have in the past figured out how to flash roms to android phones.
Anyways, I am having trouble finding any information or instruction on a possible fix for my samsung sgh t899m. it suddenly gave me a boot screen that i cannot get past. I have tried hard and soft boot numerous times.
I would post a picture but it is not letting me as a new user. the screen that comes up is as follows:
Windows Boot Manager
A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source.
If you have a windows installation disc, insert the fisc and restart your computer. click "repair your computer," and then choose a recovery tool.
Otherwise, to start windows so you can investigate further, press the ENTER key to display the boot menu, press f8 for advanced boot options, and select last known good. If you understand why the digital signature cannot be verified and want to start windows without this file, temporarily disable driver signature enforcement.
file: \windows\system32\boot\winload.efi
status: 0xc0000428
info:the digital signature for this file couldnt be verified
windows key=recovery

Nobody has any ideas? My apologies, however, I really would appreciate some help as I cannot even afford a used phone at this point in time.
Thank you.

kylezasitko said:
Nobody has any ideas? My apologies, however, I really would appreciate some help as I cannot even afford a used phone at this point in time.
Thank you.
Click to expand...
Click to collapse
I can't remember if it's possible to flash it in that state (nor do I remember the key combo to get it in the right mode) but if so the tools and ROM you need would be here
HTML:
http://forum.xda-developers.com/windows-phone-8/development/taylors-super-rom-tool-dump-sgh-t899m-t3037789

[SOLVED!] ULTRA Brick - Oreo Firmware OB16 Over Nougat ROM/kernel/TWRP DESTRUCTION?

Or as bricked as these Qualcomm devices CAN be?
Hey all,
The TL;DR is basically where the list starts
I was running Blu's TWRP v45, the latest PureFusion, Blu's latest Custom kernel, had OB15 firmware underneath. I had been SO USED to simply downloading the newest firmware from kamilmirza's AFH page and just flashing it + it being totally fine that I did it without thinking for OB16. I wasn't too worried because about a week ago I had flashed the unofficial Oreo Lineage and it worked just fine! Plus, I just assumed if it died I could just restore a backup or re-flash the older OB. But as soon as I flashed the new firmware/modem by itself this time on an otherwise perfectly running device, I only saw the OnePlus splash screen. No booting, no access to recovery, no NOTHIN.
I tried flashing the beta TWRP version afterward via fastboot but no dice. Also tried temporary booting via fastboot to it, flashing Blu's again, booting to that. Everything the same result. Splash screen & nothing more. I then went to the extent of trying to format all the partitions and flash a boot.img or do a "-w update" or "flashall" command via fastboot. Because everything out in the universe is a recovery-flashable-zip, it seems like there's no way I can flash the necessary OTA stuff to bring it back to life!
My only remaining idea is getting this damn unbrick tool to work (duhh). I can see the Qualcomm HS-USB QDLoader 9008 in device manager after doing the Vol Up (only) and plugging the cable in. BUT the MSMDownloadTool just cannot see the device. Not in bootloader, not in the weird Vol-Up/cable state. [This is with Qualcomm drivers QUD.WIN.1.1 Installer-10037.3 Setup.exe, the official OnePlus drivers, ADB & Fastboot installed.]
Sorry for long explanation. In the end, what I'm left with is:
Blank formatted partitions (I hope... I'm not even positive they wound up formatted from the fastboot commands)
Fastboot is detected, but no ADB devices are found
Can get to bootloader, but nothing else
No recovery access - Flashing beta akhilnarang Oreo recovery does nothing. Flashing stock recovery does nothing. Flashing Blu_Spark recovery does nothing. (The fastboot commands succeed though each time somehow)
So far the only suggestion I've received is trying the MSMDownloadTool/unbrick process on another computer.
Does anyone have ANY ideas? From my experience, it seems like what might help me would be if a folder with the specific partition images existed for the OTAs, like how Google offers. (boot.img, recovery.img, user-data.img, system and so on). Am I wrong in thinking that? OnePlus has told me this simply does not exist and cannot give me anything like that (don't know why, when they already offer all the OTA flashables...)
PS - OnePlus support just absolutely refuses to even let me communicate to a "level 2" representative to ask a couple of the more technical questions about it. I can't understand why. They are insisting I start an RMA and send it for repair. They even initially scheduled a time for me to talk to higher level rep and then thought up a reason to cancel it via email an hour or so later...
Edit: Just in case the thread gets large and people don't read further posts, this is using:
Windows 10 Pro 64-bit
Test mode for the driver signing is enabled. Have the watermark bottom right of desktop
It's with the stock DASH cable
Tried multiple ports
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times
Tried starting the tool BEFORE the device is plugged in, as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
HOW IT GOT SOLVED:
At the end of the day, I had to fight and convince OnePlus support to grant me a remote session with Level 2 Support.
(Attached final image) These two password protected RAR files had almost identical tools as the Unbrick tutorial on XDA.
The major difference was that MSMDownloadTool was version 3.0.8 ***does anyone have this version??*** I can't get into these RARs. The 3.0 tool circulating did not work for me. We might need the newer version as time goes on?? Otherwise, the process was identical.
Unfortunately, the image they used was for 7.1.1. I had to unlock the bootloader and after doing that and getting OB15 & the RR build I wanted, etc, I then realized my phone was force-encrypted as well.
The only toolkit that worked for force decrypting once everything else worked was:
OnePlus_3_3T_5_64bit_TOOLKIT_by_Neisor
Finally, something like 3 clean flashes later, we Gucci.
Thanks for the attempted help to those that did! Hopefully this can help someone else.

Which Windows do you have? Have you tried MSMtool in safe mode? Or disabling Driver Signature Verification (any Windows after XP). I have got my phone so messed up that it was showing many lines with red "failed" text nearly on everything. No OS, no recovery, no boot, I think even modem was failed. This screen but I had way more fails https://forums.oneplus.net/attachments/win_20160928_21_31_49_pro-jpg.459494/
As long as you can turn your phone off and on, it's doable. But you need to do that USB plugging + volume up thing while phone is totally off (you can hear Windows making bling when you connect it while pressing volume up, but phone itself stays screen off). And there shouldn't be anything on the screen before/while MSMtool do its job.
You can try different USB ports too.

Eremitus said:
Which Windows do you have? Have you tried MSMtool in safe mode? Or disabling Driver Signature Verification (any Windows after XP). I have got my phone so messed up that it was showing many lines with red "failed" text nearly on everything. No OS, no recovery, no boot, I think even modem was failed. This screen but I had way more fails https://forums.oneplus.net/attachments/win_20160928_21_31_49_pro-jpg.459494/
Click to expand...
Click to collapse
Hahaha yes...... That's why I made this post though! It SEEMS like it should be possible to recover from this since fastboot commands + bootloader work! It SEEMED like it would be easy to recover from if anything went wrong... But, here I am.
Oh yeah forgot to mention ~
Windows 10 Pro 64-bit
Test mode for the driver signing is enabled. That part of the process went totally fine with BIOS and installing stuff, etc.
Also, shot in the dark but might @Funk Wizard have any ideas? Sorry to call out for this

Hopefully someone knows better how to solve this. For me the MSMtool part is always the hardest part too, usually it finds the phone, but throws some strange "Sahara communication failed" error. I noticed that even different USB cable can be a problem, but since your Windows finds "Qualcomm HS-USB QDLoader 9008" I guess that's not the case. Does it say something after that "Qualcomm 9008" -thing? For me it shows (COM3 or COM4 depending on which port it's in).
btw, I messed up my phone in nearly similar case, flashing wrong firmware when using leaked H2OS ROM.

Eremitus said:
Hopefully someone knows better how to solve this. For me the MSMtool part is always the hardest part too, usually it finds the phone, but throws some strange "Sahara communication failed" error. I noticed that even different USB cable can be a problem, but since your Windows finds "Qualcomm HS-USB QDLoader 9008" I guess that's not the case. Does it say something after that "Qualcomm 9008" -thing? For me it shows (COM3 or COM4 depending on which port it's in).
Click to expand...
Click to collapse
Yeah sorry again for not being more clear lol
It's with the stock DASH cable
Tried multiple ports (but no USB 2 ports hmm)
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times.
Also tried starting the tool BEFORE device plugged in as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
If I find a solution I'll definitely put it in OP for others

purplepenguin said:
Yeah sorry again for not being more clear lol
It's with the stock DASH cable
Tried multiple ports (but no USB 2 ports hmm)
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times.
Also tried starting the tool BEFORE device plugged in as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
If I find a solution I'll definitely put it in OP for others
Click to expand...
Click to collapse
Hmm, ok.
Stock dash cable works, so that part is ok. Also usb3.0 ports should work too, atleast for me. So everything else seems to be ok except the MSMtool itself

Try different cable, bin there done that!!

purplepenguin said:
Yeah sorry again for not being more clear lol
It's with the stock DASH cable
Tried multiple ports (but no USB 2 ports hmm)
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times.
Also tried starting the tool BEFORE device plugged in as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
If I find a solution I'll definitely put it in OP for others
Click to expand...
Click to collapse
I hope you find a solution, since my experience sounds similar to yours Ill share it and maybe you can find something to help out.
I was exactly where you are for about 3 hours last night.
Boot would always get stuck at the splash screen. Could boot into Fastboot, tried using the Skipsoft tool to fastboot flash a stock image but it kept failing.
As far as the Unbrick Tutorial goes, I know the first thing I kept messing up was thinking I needed to press the power button while holding the volume up and connecting to the PC
Also when I tried to manually update the driver on "Qualcomm 9088" it said it was already up to date.
Then I just ran the MSMTool it flashed 6.0.1 back on my phone and I was back in business.
Im sure this is the guide you followed: Here
I found another on the oneplus forums that is essentially the same but goes into a little more detail in the steps: Here
Since I was back completely Stock including Recovery I went ahead and sideloaded OB16 to get the firmware and modem then went about rooting, unencrypting etc...
Lost a few days worth of files but I'm back running LunuxOS Oreo right now.
Good luck I know how you feel. :good:

I've got it revived! I'll update OP. Sadly, it required OnePlus's intervention.

Hi. Trying to do brute force to get the passowrd here, don't you know how many characters that was? It will take days in my machine to search from 3 to 9 characters...
I think it is impossible to you to know, but if you know if they used only letters or something like that, it would be very useful

guilhermeferrari said:
Hi. Trying to do brute force to get the passowrd here, don't you know how many characters that was? It will take days in my machine to search from 3 to 9 characters...
I think it is impossible to you to know, but if you know if they used only letters or something like that, it would be very useful
Click to expand...
Click to collapse
Sorry man. The OnePlus guy was ready an hour early before our appointment time. So I didn't have time to set up screen recording or anything
if I had to narrow it down more itd only be like 4-9 chars lol I know that's not much help... Definitely let me know if you get it open though please! It would probably help a lot of us!

purplepenguin said:
Sorry man. The OnePlus guy was ready an hour early before our appointment time. So I didn't have time to set up screen recording or anything
if I had to narrow it down more itd only be like 4-9 chars lol I know that's not much help... Definitely let me know if you get it open though please! It would probably help a lot of us!
Click to expand...
Click to collapse
Well, I know the password. It's 10 character long. 7+3(7english small latter with 3 Numbers).
L2 Driver password is very very very very very loooooooong. can't even count accurately.

namefaisal said:
Well, I know the password. It's 10 character long. 7+3(7english small latter with 3 Numbers).
L2 Driver password is very very very very very loooooooong. can't even count accurately.
Click to expand...
Click to collapse
Jeez so wait you got it open or not?? Confused lol
Got the newer download tool ??

Yeah, I got it open
purplepenguin said:
Jeez so wait you got it open or not?? Confused lol
Got the newer download tool ??
Click to expand...
Click to collapse
Yeah it's the new 3.08 msmdownloadtool. OnePlus3T_28_A.57_171012.zip
I know the password and I won't share that but I will upload an UNLOCKED zip on google drive tonight. L2 Drivers too.

New Files without Password
namefaisal said:
Yeah it's the new 3.08 msmdownloadtool. OnePlus3T_28_A.57_171012.zip
I know the password and I won't share that but I will upload an UNLOCKED zip on google drive tonight. L2 Drivers too.
Click to expand...
Click to collapse
Latest 3.08 msmdownloadtool re-archived without password from OnePlus3T_28_A.57_171012.zip
https://drive.google.com/file/d/1kp2SBmhAByydol97o0yVlurVue9Ow8Aq/view?usp=sharing
And the L2+ driver.zip re-archived without password
https://drive.google.com/file/d/1JL_sRg86CczUeZ2cfw8GY6rxc43myif8/view?usp=sharing

@Sam Nakamura

namefaisal said:
Latest 3.08 msmdownloadtool re-archived without password from OnePlus3T_28_A.57_171012.zip
https://drive.google.com/file/d/1kp2SBmhAByydol97o0yVlurVue9Ow8Aq/view?usp=sharing
And the L2+ driver.zip re-archived without password
https://drive.google.com/file/d/1JL_sRg86CczUeZ2cfw8GY6rxc43myif8/view?usp=sharing
Click to expand...
Click to collapse
This totally worked for me. Yes it put me back on 7.1.1 but I have been having issues trying to flash Oxygen ROMS and getting them to take. Phone is back to bone stock which I wanted for now and is working great. Thank you for sharing,

cdorrell12000 said:
This totally worked for me. Yes it put me back on 7.1.1 but I have been having issues trying to flash Oxygen ROMS and getting them to take. Phone is back to bone stock which I wanted for now and is working great. Thank you for sharing,
Click to expand...
Click to collapse
You are most welcome.
Sadly everyone gets unbricked with these files but My device didn't. I have to send the device to the service center now. It seems my case is a hardware issue. Tough luck

namefaisal said:
Latest 3.08 msmdownloadtool re-archived without password from OnePlus3T_28_A.57_171012.zip
https://drive.google.com/file/d/1kp2SBmhAByydol97o0yVlurVue9Ow8Aq/view?usp=sharing
And the L2+ driver.zip re-archived without password
https://drive.google.com/file/d/1JL_sRg86CczUeZ2cfw8GY6rxc43myif8/view?usp=sharing
Click to expand...
Click to collapse
thanks a lot saved my day !!

purplepenguin said:
@Sam Nakamura
Click to expand...
Click to collapse
Sorry, I just saw your mentioning somehow I missed it, happy you got your phone back already, unfortunately not independent for big OP, did you guys already share this new 3.08 MSM-download-tool to the well established threads or did you I missed this too? This information and according files should be shared with the community and easy to find for those poor souls who unintentionally killed their beloved device...
---------
Edit: further sharing isn't necessarily needed, you did already a pretty good job by naming the thread and describing the situation thoroughly, only suggestion could be to link the updated MSM-download-tool download to the first post with some hint, just an idea though...
Cheers
Sent from my OnePlus 3T using XDA Labs