Develop Bugs

[Q] Phone bricked, possibly bad CWM flash file

So Ive had my GS3 for a few weeks now and no issues, been stock rooted with the 6.0.1.2 CWM (non touch).
Was browsing around on the General forum and noticed this sticky called "[INDEX] AT&T GS III - I747 {ROMs/Root/Recovery.. etc}"
In there was a 6.0.1.4 CWM, I noticed both were CWM flashable. One for touch and nontouch.
So I downloaded it directly to the phone, booted into CWM, flashed the touch version, and told it to reboot recovery. And since then the phone is basically bricked. It never turned back on, screen remains black. Nothing happens. Cant force it into Download mode either. I took the battery out and put the USB cable in and all I get is the RED LED for about 1min. I get a qhsusb_dload driver that doesnt load on the computer, nothing else. So the phone is basically bricked.
I then decided to see what happened, i downloaded the flash file that was in that thread which is here
http://dl.dropbox.com/u/31151290/CWM/CWM_Touch_6.0.1.4.zip
When I open it and look at the updater-script, I see a problem. This is flashing the recovery to mmcblk0p8
The i747's recovery partition is mmcblk0p18
So this thread that is referencing these two CWMs probably should be pulled or fixed, cause p8 partition is tz. Not sure what that is, but it almost looks like its completely screwed the bootloader part.
Any way to recover this or is JTAG service the only option for my paper weight?
Dixit

I've heard on another thread someone installing CWM Touch had the same problem, vaguely light yours.
All I can say from what knowledge I have is Odin or getting a Jig. Last resort's are better than Service, lol.
Goodluck :]

Jig won't work. You are hard bricked sorry for your bad luck!!! I had a hard brick and had to send mine for jtag repair. If you live in the states you could send your phone to get repaired and get it back in 4 business days average. (varies).
If you still have warrenty... go that route!!
Sent from my Desire HD using Tapatalk 2

http://forum.xda-developers.com/showthread.php?p=32113899
Check this thread
Sent from my SGH-I747 using xda app-developers app

What sucks is the thread is a sticky and points to these two CWM files to use and technically both are wrong. The moderators need to pull those two links. As I mentioned earlier, those two zips are flashing to pEIGHT (p8) when it whould be pEIGHTEEN(p18). Thats why it got bricked.
Dixit

I did the same thing. It was for the Galaxy Nexus. The person linked to a single post, so it was to hard to tell what that recovery was for. I still wonder if that person did it on purpose.
Sent from my SAMSUNG-SGH-I747 using xda premium

dixit said:
What sucks is the thread is a sticky and points to these two CWM files to use and technically both are wrong. The moderators need to pull those two links. As I mentioned earlier, those two zips are flashing to pEIGHT (p8) when it whould be pEIGHTEEN(p18). Thats why it got bricked.
Dixit
Click to expand...
Click to collapse
If you feel that strongly about it, report the thread. In Web view or on your pc, look to the right of a post, next to the post count for that thread. Little yellow triangle. Press that. I usually mark 99.9% of the stuff i report as post/thread maintenance. After that, you'll get a pm from the moderator handling the report. Then you'll get another when the report is considered to be handled.

ouch.. good luck man

mrhaley30705 said:
If you feel that strongly about it, report the thread. In Web view or on your pc, look to the right of a post, next to the post count for that thread. Little yellow triangle. Press that. I usually mark 99.9% of the stuff i report as post/thread maintenance. After that, you'll get a pm from the moderator handling the report. Then you'll get another when the report is considered to be handled.
Click to expand...
Click to collapse
Thanks, forgot to come back in here and update it, the moderators did get in touch with the OP of that thread and I talked to them and he did already pull the links for those files. He has been trying to get in touch (about 4 messages now) to the original developer but cannot so for now he is just going to leave them off as he agreed with me, it should NOT be flashing p8 when in fact its p18.
Thanks to the moderators on moving on this when we reported it.
Dixit

dixit said:
Thanks, forgot to come back in here and update it, the moderators did get in touch with the OP of that thread and I talked to them and he did already pull the links for those files. He has been trying to get in touch (about 4 messages now) to the original developer but cannot so for now he is just going to leave them off as he agreed with me, it should NOT be flashing p8 when in fact its p18.
Thanks to the moderators on moving on this when we reported it.
Dixit
Click to expand...
Click to collapse
What will you do with your bricked S3 ?

jorioux said:
What will you do with your bricked S3 ?
Click to expand...
Click to collapse
Tried a bunch of things, no go. Only QPST tools sees it but we dont have enough information from anyone on how to use this tool on the S3, we dont have all the files (or no one has developed them yet) like they have on some of the other threads like the HTC one where they can entirely bring the phone back in a hard brick (where it just shows up as QHSUSB download mode).
So probably send it into get JTAG'ed.
Dixit

My experience with LG G3's KillSwitch

KillSwitch​
Three different ways that I found to get rid of the KillSwitch
Through deactivating and then reactivating your google account/s.
Using the Hard Brick Recovery method.
Octopus/Octoplusbox.
Explanation​
The one I actually tried was the Hard Brick Recovery Method (WillCracker), but
even after that I was still unable to bypass the KillSwitch. So I went back BoardDiag and decided to flash the System, UserData, and Cache since I still couldn't get into download mode.
After about 5-6 hours it was completed. I try booting up download mode and guess what?! KillSwitch is still there xD. I'm absolutely fustrated now and all I could think of is to flash the rest of the files that the HBRM didn't say anything about.
I started flashing in this order: Modem, Misc, Persist, and RCT. Everything is now flashed and I hope everything worksout.
I turn on the phone, waiting patiently. Bootloop over and over again, but guess what?! I tried download mode one last time before I was going to go ape $h!t. Then to my surprise the download mode screen turned on, I used the LG Flash Tool and I am now killswitch free.
KillSwitch did come back after a few updates, but I was able to enter in a pin code allowing me in the future to turn it off at will
Well thank you all for listening, just wanted to share my experience.
as my first post, I do apologize in advance if this is the wrong area for this.
Keep on keeping on xD

Can you tell me the exact order you flashed the phone using boardiag? Thanks in advance!

siredux said:
Can you tell me the exact order you flashed the phone using boardiag? Thanks in advance!
Click to expand...
Click to collapse
Warning: This may or may not work, and might brick your phone.
Hope this helps
http://forum.xda-developers.com/lg-g3/general/guide-unlock-mcafee-lock-lg-g3-t3264963

Solved
JackTraits said:
Warning: This may or may not work, and might brick your phone.
Hope this helps
http://forum.xda-developers.com/lg-g3/general/guide-unlock-mcafee-lock-lg-g3-t3264963
Click to expand...
Click to collapse
Link u shared shows Test points for G2 .... Correct test Points for G3 are Shown in following video
https://www.youtube.com/watch?v=04AgASAWJu8

Unlocked Bootloader Message

Is there a way to avoid the message you get when you reboot after unlocking the Bootloader? The black screen where you can wait 5 seconds or tap the power to go on...
I understand that is correct to show it...but it's boring and I'm already aware of it.

http://forum.xda-developers.com/nextbit-robin/general/guide-install-twrp-root-robin-t3334171/page7
maybe try and follow the instruction on post number 69

Thanks for the reply but that's for Moto X. Actually before Robin I was using a Moto X and I know that procedure, point is that on Moto X was just a screenshot before booting and nothing else, here looks a bit different and you can also skip it pressing the power button. Plus I would avoid to flash/use the logo.bin of Moto X...
Can anyone of Nextbit team provide any info? Thanks !

I also don´t like the screen... the opportunity to hide would be great.

here's the same, maybe someone can make a xposed module?

kcl0801 said:
here's the same, maybe someone can make a xposed module?
Click to expand...
Click to collapse
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.

uberlaggydarwin said:
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.
Click to expand...
Click to collapse
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...

kcl0801 said:
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...
Click to expand...
Click to collapse
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:

any luck on the nag screen yet? maybe gone in the july update? =D lol

I get this message Everytime, any ideas? Help would be great

Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!

makbomb said:
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!
Click to expand...
Click to collapse
Thanks that worked

Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Replace "recovery.img" at the end with the actual twrp filename and it should work.

I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!

Saaber said:
I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!
Click to expand...
Click to collapse
The last several message in this thread regarding 'recovery.img' was for someone trying to flash TWRP in fastboot, it has nothing to do with the 5-second nag screen.
Since khang never responded, I'm assuming this won't change and the nag screen will remain. I'm so used to keeping my finger on the power button when i reboot that it's almost habit now, so really doesn't bother me too much.

How can a device that is marketed for its unlockable bootloader and warranty coverage have an jnlockable bootloader experience that is worse than basically all devices. You don't see unlocked Sony or LG phones having boot screens that require user input. The only device I know of that is worse is the Pixel c, which has a 30 second "integrity check" if the bootloader is unlocked.

Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
IS this going to change? really annoyed by it

..It's only 5 seconds, the only reason it seems longer is the fact that the message merges in with the boot logo

Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
Very old thread here, but could you guys maybe release an optional "developer/enthusiast" bootloader update that gets rid of that nag screen? Or at least give the option to confirm the warning in future updates, like "I have read and understood this warning. Don't show again."

I am posting hoping some progress may or may not have been made on this. Its atrocious.

TWRP (Ianmacd) Images, New Space.

This is NOT my work (Ianmacd) and guide is written by Mr Pickles all credits to him for his install method.
Also this is just a copy and paste but the guide is well written and TWRP should cause less issues.
I'm sure Gieti94 is just perhaps busy with other commitments, credit also to him for his fantastic efforts.
Just a new space for the currently working TWRP so all don't get in a pickle.
----------------------------
Download Maintained By Pickles (best all in one convenient place) will have everything necessary for twrp functionality. Credit to pickles.....:good:
http://bit.ly/2VlcqYd
Excellent installation Guide below
Install Guide
---------------------------
- NOT A SINGLE STEP IS UNNESSECARY
- DO THEM _ALL_ EXACTLY!
- ALL YOUR DATA WILL BE GONE - BACKUP!
---------------------------------------
DO NOT INSTALL MODPACK FROM SOLDIER - IT BREAKS TWRP!
---------------------------------------
If you have any problems - contact @PiCkLeS or on Telegram by PiCkLeS or @rp4k
---------------------------------------
All development is by @ianmacd (Ian Macdonald).
---------------------------------------
0 - No matter what you have today, no root or Magisk-only solution or TWRP with Magisk-solution, do ALL the steps..
1 - Make sure you copy the "Magisk_Manager_Ian_install.apk" file and "Multidisabler-g97x_by_Ian.zip" file to your sd-card before you start!
2 - Download latest firmware via Samfirm or Frija or in any way you can, and unpack.
3 - Boot your phone to Download mode (Power+Bixby+VolDown) and remember to have the USB connected to your computer, it won't boot to DL-mode otherwise
4 - Keep autoboot etc in Odin settings, put each file in its place (AP, BL, CSC etc) and _dont_ use HOME_CSC, use CSC-only-file.
5 - After Odin is done, your phone will reboot automatically - let it! It can feel like forever, but let it do its restarts and stuff until you are in system-setup
6 - Do the setup as per usual, CONNECT TO WIFI but you can safely just say Skip on sign in and other stuff
7 - When setup says its all finished and you get to the standard launcher - go into Settings and enable Developer settings
8 - This step IS necessary.. If you don't do this step, you might get in pre-normal rrm state and you will have wait 7 days to try again: Enter Developer settings and look for the "OEM Unlock" switch - if you are rooting for the first time, Enable it. If you already have root since before or unlocked your bootloiader before, just confirm that its Enabled and graded out.
9 - If you already have an unlocked bootloader, skip to step 12. If not, continue with step 10.
10 - IF you never have unlocked your bootloader before, Power off the phone and boot into download mode again. You will see the long press volUp option for unlock bl, do that.
11 - IF you never have unlocked OEM before, boot the phone again, do the setup without signing in etc but connect to wifi, enable dev settings, go into dev settings and check that OEM now is enabled and grayed out.
12 - Reboot the phone in recovery mode (Power+Bixby+VolUp and keep holding until you are in stock recovery. Choose and do a factory reset.
13 - Reboot to bootloader with option in Recovery.
14 - Flash the tar you got (S10x-TWRP+Magisk_fixed_by_Ian.tar I Odin in the AP-slot. DISABLE auto reboot in Odin first!
15 - When the tar has flashed - Do as instructed on the phone, hold Power+VolDown for a few seconds and AS SOON AS THE SCREEN GOES BLACK -> quickly press power+bixby+volUp for a _long_ time, and I mean it can feel as if its a full minute! After a while you will see TWRP starting with its start screen, you can now let go and enter TWRP.
16 - FORMAT data, then WIPE data AND Cache. DO NOT LET IT REBOOT
17 - Flash "Multidisabler-g97x_by_Ian.zip" from SD card
18 - Go back to start screen of TWRP, Choose Reboot, Choose Recovery - YOU MUST ALWAYS CHOOSE REBOOT TO RECOVERY and _NOT_ system!
19 - Let the phone reboot into system, it will do some reboots it self, and again it will feel like it takes FOREVER - Just let it do its thing and DO NOT PRESS ANY KEYS!
20 - When your phone is finally done booting, just do the normal setup/signing for real this time.
21 - When you are done and in system/launcher, install "Magisk_Manager_Ian_install.apk" from SD card and verify that you now have Magisk Manager installed.
22 - Start Magisk Manager and say YES to what it says, it will do some stuff and then say "Rebooting in 5 seconds" - LET IT BOOT AND DO NOT TOUCH ANY KEYS this time either..
23 - Now when booted to system, start Magisk Manager and see that you have all green and its installed.
24 - Now you have root.
** Every time you reboot manually, be prepared to hold Power+Bixby+VolUP until you see the Samsung S10x-logo, then release and let it reboot, you will have root.
** Every time you power off the phone, when you power ON again, hold Power+Bixby+VolUP until you see the Samsung S10x-logo, then release and it will boot with root.
** Every time you want to enter TWRP-recovery, do as above but KEEP HOLDING THE KEYS UNTIL TWRP-start screen shows then release. Remember to choose reboot to recovery afterwards and you will boot with root.
** IF you screw up and forget or miss the key combo, just let it boot to system, immediately when system is up - reboot again and do the key combo and all is fine again.
This is me just trying to get an emergency first aid space, nothing more, I'm NOT trying to take any credits or dismiss Gieti94.
Thanks All

Duncan1982 said:
This is NOT my work (Ianmacd) and guide is written by rp4k all credits to him for his install method.
Click to expand...
Click to collapse
This is my tutorial and not r4pk. And I'd prefer that you use the download I provide here and no where else to make sure the right files gets downloaded when updated.
http://bit.ly/2VlcqYd
/P

Yea I can keep the OP updated, this is just an emergency first aid thread, thanks to Pickles for his well written guide.
I'm really not wanting to offend anyone, just for all to make life a bit easier....

very nice to have a reliable twrp solution, pitty that we don't have too many things to flash in recovery

Please remove the alternate download link, I have updated the multidisabler zip with a important update, v1.1 and the one download link for all is just for things like that, the other download link still have the old zip.
Very important that everyone uses Ian Macdonald's new v1.1 multidisabler script.
/P

I can update the mega link with the new disabler I reposted it to mega because I can't access Google @PiCkLeS
And yes I never said I wrote the guide I just added myself for helping people

rp4k said:
I can update the mega link with the new disabler I reposted it to mega because I can't access Google @PiCkLeS
Click to expand...
Click to collapse
I understand. But that doesn't seem to be a big problem for any one else and the bigger problem is that you risk having a link that is being used by the people only see it here and don't read anywhere else, or this message, and end up with old information or even worse, outdated files.
I can help you get the files on PM but please remove these links outside of my drive, which I maintain every day and keep up to date. It's not for vanity, it's for safety.
For now please edit your text and remove the link. All must use v1.1 of the multidisabler zip by Ian.
/P

Maybe this thread was a bad idea, as stated I am around and willing to keep things up to date
I know the importance, and how things are at present.

Duncan1982 said:
Maybe this thread was a bad idea, as stated I am around and willing to keep things up to date
I know the importance, and how things are at present.
Click to expand...
Click to collapse
Listen, just to be clear. I and I dont think Ian have a problem with you having this thread.
All I am worried about is the download link. Things can and are happening fast. If there are multiple sources for downloading files in this case, and today one was updated with important improvements, and there are many places to download from people can miss that and download old files that can cause big problems.
Keep the downloading to one good source and everything will be fine. The thread in it self can do much good by showing that there is an alternative, it works and right now almost 100 people in 24 hours have used it. Fantastic!
So I dont think it was a bad idea, I just dont want PM:s from people in a week or two asking why their device suddenly lost data, only to find out that they downloaded from a source that didnt have the latest files.
Thats all.
//P

PiCkLeS said:
Listen, just to be clear. I and I dont think Ian have a problem with you having this thread.
All I am worried about is the download link. Things can and are happening fast. If there are multiple sources for downloading files in this case, and today one was updated with important improvements, and there are many places to download from people can miss that and download old files that can cause big problems.
Keep the downloading to one good source and everything will be fine. The thread in it self can do much good by showing that there is an alternative, it works and right now almost 100 people in 24 hours have used it. Fantastic!
So I dont think it was a bad idea, I just dont want PM:s from people in a week or two asking why their device suddenly lost data, only to find out that they downloaded from a source that didnt have the latest files.
Thats all.
//P
Click to expand...
Click to collapse
I fully appreciate and understand that, the reason I created as I have plenty of time to maintain, and will keep it up to date I have been around for quite some time, if you look at my posts (search) I have had almost every device you can think of, currently have the Vivo IQOO also, I have enough experience to understand the important and implications.
I don't want your PM's to be going crazy so I'll fully respect your decisions and will keep everything updated also. But it is better if everything is tody and not one thing here and there, OP has been updated with your direct link, is this cool?
Just thought by creating this thread that it might help, my sincere and good intentions are hopefully evident

PiCkLeS said:
Please remove the alternate download link, I have updated the multidisabler zip with a important update, v1.1 and the one download link for all is just for things like that, the other download link still have the old zip.
Very important that everyone uses Ian Macdonald's new v1.1 multidisabler script.
/P
Click to expand...
Click to collapse
Can I install multi Disabler 1.1 withouth lost data?

zubi182 said:
Can I install multi Disabler 1.1 withouth lost data?
Click to expand...
Click to collapse
Yes just flash it in twrp, nothing will be lost.
/P

I assume this is only for the Exynos version? Or does it work for Snapdragon as well?

mistermidas said:
I assume this is only for the Exynos version? Or does it work for Snapdragon as well?
Click to expand...
Click to collapse
You have a working snapdragon root? How did you get past step #9 of launching stock recovery after you flashed magisk

rp4k said:
You have a working snapdragon root? How did you get past step #9 of launching stock recovery after you flashed magisk
Click to expand...
Click to collapse
Man... did you even read my comment???
I was asking if this would work for Snapdragon, not saying I got it to work. It doesn't mention if it's a method for both versions in the OP or not.

mistermidas said:
Man... did you even read my comment???
I was asking if this would work for Snapdragon, not saying I got it to work. It doesn't mention if it's a method for both versions in the OP or not.
Click to expand...
Click to collapse
Sorry I responded when I was half asleep. My fault.

I will try this out and post and update, i had no luck with previous twrp, always boot loops regardless of what i do.
My bootloader is unlocked but not grayed out. Can i still do it?

mercifool said:
I will try this out and post and update, i had no luck with previous twrp, always boot loops regardless of what i do.
My bootloader is unlocked but not grayed out. Can i still do it?
Click to expand...
Click to collapse
Yes, just do exactly all the steps and use the new files in the link and you will be fine.
//P

deleted

Carotix said:
hi ,
do you have the OEM switched to on?
if not , you need it ..... if you can't get it because you are waiting the 7 days , you can make this trick
open settings and set the date 8 days before ... then reboot
so you can enable OEM in developer settings
Click to expand...
Click to collapse
Hi there, are these instructions for Exynos only or can I apply it to Snapdragon as well, please advise. Thank!

Unlock issue after screen replacement (device crashes frequently)

Hey guys
My ONEPLUS 3 display got broke down.
So I went for a display replacement in service centre.
For which they charged me 7500/- ₹
But after replacement.. the phone is crashig a lot.
I need to press power button end number of times & still the phone won't respond.
I don't know why this is happening.
Can someone suggest a solution?
Currently the device is on - Oxygen OS 9.0.5 (non-rooted)
Please help! ?

please try and unbrick your device by downloading this tool https://androidfilehost.com/?fid=6006931924117936392 then run msm download tool as administrator

kallum7 said:
please try and unbrick your device by downloading this tool https://androidfilehost.com/?fid=6006931924117936392 then run msm download tool as administrator
Click to expand...
Click to collapse
will this wipe device internal storage??

Lucifer213_ said:
will this wipe device internal storage??
Click to expand...
Click to collapse
yes

kallum7 said:
yes
Click to expand...
Click to collapse
what about caseium kernel?
someome told me to install it..but im not sure if it supports oxygen os latest build.

Lucifer213_ said:
what about caseium kernel?
someome told me to install it..but im not sure if it supports oxygen os latest build.
Click to expand...
Click to collapse
nope because the system drivers are corrupt so it needs to be reset by unbricking the device

ok thanks, but can u explain me the steps , cause i don't exactly know how to unbrick. Cause I've never done so.
I don't want anything wrong to happen.

Lucifer213_ said:
ok thanks, but can u explain me the steps , cause i don't exactly know how to unbrick. Cause I've never done so.
I don't want anything wrong to happen.
Click to expand...
Click to collapse
Firstly download the unbrick tool I have sent you through the link then switch off your phone and make sure cable is unplugged then hold the volume up button on your phone and then plug in the USB cable to the computer and phone then on your computer and open device manager and make sure under ports it says Qualcomm 9 and then extract the unbrick tool then run mam as admin then click start

Lucifer213_ said:
ok thanks, but can u explain me the steps , cause i don't exactly know how to unbrick. Cause I've never done so.
I don't want anything wrong to happen.
Click to expand...
Click to collapse
This has a collection of unbrick tools and versions of OOS.
This contains detailed instructions also.
Hope you solve your problem.
If not and you still have warranty for the display (OnePlus gives atleast 3 months warranty on replacement), take the phone to the Service Center. In fact, if you have warranty, that should be the first option.

Thanks for the response.
But I don't think my device is bricked, cause the phone is on working mode, but it's just that whenever I lock my phone.. It does not gets unlock on the first attempt. I need to press the unlock/power button end number of times & the phone still don't responds. It gets crashed and the System UI error occurs & asks for force stop & the phone is lagging a lot. I can't even use it properly.

I would still recommend doing it

have you got it sorted

kallum7 said:
have you got it sorted
Click to expand...
Click to collapse
I'll do it today/tomorrow
& Share the details.

kallum7 said:
have you got it sorted
Click to expand...
Click to collapse
I completed the process.
But it's still happening.
Not that much. But it is happening every 5th time I try to unlock my phone.

By this point you have two options get another device or get your op3 and take it to a OnePlus service center and get it repaired

kallum7 said:
By this point you have two options get another device or get your op3 and take it to a OnePlus service center and get it repaired
Click to expand...
Click to collapse
OnePlus service is worse.
I guess I need to purchase a new smartphone then, or find some other solution.

kallum7 said:
By this point you have two options get another device or get your op3 and take it to a OnePlus service center and get it repaired
Click to expand...
Click to collapse
Though, thanks a lot for helping me out.

Lucifer213_ said:
Though, thanks a lot for helping me out.
Click to expand...
Click to collapse
Welcome

Anybody here got solved this problem?am facing this issue too.please help

THREAD CLOSED! If interested in the subject please follow this already existing thread:
https://forum.xda-developers.com/oneplus-3/help/faulty-display-replacement-software-t3960068
All posts of this thread have been copied to the other one.
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
Click to expand...
Click to collapse