Database Info

Help Please Please with my bricked Alcatel Ot 5020 (Evolve)

This is my first time asking for help directly here, I always find the answers in the other threads solved, but this time I can not find an answer.
I have a alcatel one touch 5020t evolve its a MTK6575 (t-mobile but is used in el salvador), I used to MTKDroidTools to install CWM Revocovery, I did back up with the same program but apparently did not because i look and i cant find anything in the back up folder, only left some files called:
ALCATEL-ONE-TOUCH-5020T_130818__boot_patched_140129-175612.img
ALCATEL-ONE-TOUCH-5020T_130818__recovery_140129-175612.img
in the folder called recovery.
Now the phone on, the startup screen and then turns off, I can enter a menu by pressing on + vol +, where it says enter recovery mode or normal mode, before they tried to install cwm I could go in and delete everything from there, now I get the menu of recovery mode and normal mode but since does not enter recovery mode, got it turns off, like when entering the normal mode.
I tried to flash with sp flash tool but I get an authentication error that is on the img
The pc recognizes my phone, makes the sound when you connect something, now if we go to Device Manager, a device called first appears:
MTK USB Port
After that is disconnected and then a new one appears called :
Media Tek Preloader USB VCOM Port
But there ir a problem, then this becomes a repetitive one disconnects and connects the other, but only when I connect the phone without battery only stays in:
MTK USB Port.
Help what can i do to revive my phone ???????????????

you found any solution i have the same problem ?

:/
harold99 said:
you found any solution i have the same problem ?
Click to expand...
Click to collapse
Sorry, but i could not solve yet, nobody helps me

So were you able to flash cwm to the device? there are several threads requesting a custom recovery for this device and either way could you upload those first two .img files I may be able to use them to try to recover my device
*** Okay so the problem is that the boot loader on this device is locked and for the time being a custom recovery is not possible. I still have access to the recovery on my device so if I could find a way to build an update file from the source code or an official firmware update I could fix mine. Yours may be too far gone. sorry.

any luck with a solution? How close to one have you got to...

ipeedalil said:
*** Okay so the problem is that the boot loader on this device is locked and for the time being a custom recovery is not possible.
Click to expand...
Click to collapse
A friendly warning: Don't just mess around with the Bootloader, that's one delicate piece of software, try to find how to unlock it first, then we can talk of changing the recovery. For rooting purposes I can attest that you can safely root it using the OneClickRoot solutions around the net. I used some chinese root and it worked like a charm.

Soft Bricked 5020T
carlitox2301 said:
This is my first time asking for help directly here, I always find the answers in the other threads solved, but this time I can not find an answer.
I have a alcatel one touch 5020t evolve its a MTK6575 (t-mobile but is used in el salvador), I used to MTKDroidTools to install CWM Revocovery, I did back up with the same program but apparently did not because i look and i cant find anything in the back up folder, only left some files called:
ALCATEL-ONE-TOUCH-5020T_130818__boot_patched_140129-175612.img
ALCATEL-ONE-TOUCH-5020T_130818__recovery_140129-175612.img
in the folder called recovery.
Now the phone on, the startup screen and then turns off, I can enter a menu by pressing on + vol +, where it says enter recovery mode or normal mode, before they tried to install cwm I could go in and delete everything from there, now I get the menu of recovery mode and normal mode but since does not enter recovery mode, got it turns off, like when entering the normal mode.
I tried to flash with sp flash tool but I get an authentication error that is on the img
The pc recognizes my phone, makes the sound when you connect something, now if we go to Device Manager, a device called first appears:
MTK USB Port
After that is disconnected and then a new one appears called :
Media Tek Preloader USB VCOM Port
But there ir a problem, then this becomes a repetitive one disconnects and connects the other, but only when I connect the phone without battery only stays in:
MTK USB Port.
Help what can i do to revive my phone ???????????????
Click to expand...
Click to collapse
I have had a OT-5020T with all the same symptoms as you describe. After much research and diagnosis here is what I have learned and know to be true.
You have soft bricked your phone. For this phone it results in the boot loop you described. At present a Custom Recovery that works is not available for this phone and any attempt to flash an existing one results in a soft brick. There are apps that will flash a Custom Recovery while the phone is one but once you reboot ... !!! Bricked!! This is because ...
a) the memory mapping for this phone is different that other OT-5020 models, so the Custom Recovery placement and indexing is wrong when flashed, causing the boot-loop, and inability for Custom Recovery to load,
and ,
b) the bootloader is locked for the 5020T (different story for other OT 5020 models), and no one has found a way around it yet. Trying to flash back stock firmware for the OT-5020T requires it to be unlocked.
One Touch Update 2.8.0 doesn't seem to want to work one the phone has been altered in this way. SPtools won't work because you need an accurate OT-5020T scatter file (memory map) ,and certification file (bootloader unlocker) to flash any image. In addition to all this the phone doesn't maintain a steady usb connection long enough to allow use of android tools adb and fastboot commands although it does can stay connected in a different mode.
What I have used to restore my phones firmware is a package from Furious Gold that allows the phone to be flashed to factory firmware. I have used it successfully, so I can confirm that the phone wasn't a permanent brick.

Alcatel 5020t T-Mobile plis help flshe file

please am in need of alcatel 5020w firmware, please if someone is having it or having that same phone and want to read the firmware for me my email is [email protected]
thanks

failed root fastboot only help please

I bought a t mobile one plus 7 pro - version gm31cb-on 9.5.10 before I read about the hassle it can be compared to an unbranded phone. The bootloader is unlocked.
I tried the msm tool to go to international version but it got stuck on parameter preload so I decided to try to root and get rid of the tmobile flash screen later.
long story shortened, the phone is stuck on the warning screen.
Pressing buttons, I can get it into fastboot but adb doesnt see the phone to flash/push anything.
If I try to boot into recovery, it sticks at the warning screen.
can I somehow get adb to see the phone in fastboot mode?
do you know if i need a certain os/file so i can get past the parameter preload with msm?
i followed the steps in the msm tutorial.
if msm sees the phone and it gets to parameter preload does it mean it is not a driver issue but maybe the wrong software?
Any advice is appreciated.
thank you for your time and expertise
Marc
through fastboot
I am using the universal fastboot and adb tool and trying to flash boot twrp and start over
current error: failed remote recovery a no such partition
after fastboot --set-active=b
same error
update 2
somehow, after simply trying over and over i got twrp on partition a
i think i will stay here until a kind member can direct me to an img that will work
thank you

marcadamf said:
I bought a t mobile one plus 7 pro - version gm31cb-on 9.5.10 before I read about the hassle it can be compared to an unbranded phone. The bootloader is unlocked.
I tried the msm tool to go to international version but it got stuck on parameter preload so I decided to try to root and get rid of the tmobile flash screen later.
long story shortened, the phone is stuck on the warning screen.
Pressing buttons, I can get it into fastboot but adb doesnt see the phone to flash/push anything.
If I try to boot into recovery, it sticks at the warning screen.
can I somehow get adb to see the phone in fastboot mode?
do you know if i need a certain os/file so i can get past the parameter preload with msm?
i followed the steps in the msm tutorial.
if msm sees the phone and it gets to parameter preload does it mean it is not a driver issue but maybe the wrong software?
Any advice is appreciated.
thank you for your time and expertise
Marc
Click to expand...
Click to collapse
You just need to update Qualcomm drivers.
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659

blas4me said:
You just need to update Qualcomm drivers.
https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659
Click to expand...
Click to collapse
doing so now...
thank you for the help.
I somehow got it up and rooted.
will msm work while rooted or mess up root?
I have a gm1915 wich is not listed in the link for the drivers? any thoughts?

These should work. As for MSM tools use the international version.
If you can't shut off device, hold power + Vup for about 10 seconds without being connected to a power source. If your fast enough, keep device plugged, and just press Vdown, to boot recovery.
https://drive.google.com/file/d/1JoHF6RF1THVn3pQWywaJz2URGTPxL2pH/view

not sure where you are at right now, but i installed a wrong os version (android 10 on my phone with pie on it). It would only boot into fasdtboot screen no matter what I did or tried. Could not get adb to recognize it, had no twrp or rom installed correctly. No way to fix it, could not use MSM tool as phone had to be able to be shutoff, which mine couldn't. never recognized it due to that. tried drivers to no avail. not really many answers out there, til I found out about fastboot roms.
check out this page: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
* IMPORTANT: in above link, remember to only download the OS version that fits your phone previously. DO NOT try to update your phone to a different version using that method. Also this method will NOT work on a branded phone, so if your phone is originally a T-Mobile phone then unfortunately this is not a solution for ya.
You may also want to check out this page as well: https://www.reddit.com/r/oneplus/comments/3izejg/so_youve_just_bricked_your_oneplus/
I hope this helps. The Fastboot Rom solution worked for me, it saved me from throwing my phone in the trash. I ran the bat file and it did the rest.

Help installing custom ROM on Moto g8 plus

Code:
Boot failed. Press POWER KEY to retry.
Your device didn't start up successfully.
Follow these instructions if the failure cannot be recovered after retrying.
If this is a Verizon device, please use the Software Repair Assistant on computer to repair your device. Connect your device to your computer to get the Software Repair Assistant.
If this is not a Verizon device or Software Repair Assistant did not help for any reason, please contact customer care for furthur assistant.
AP Flashboot Flash Mode ( Secure)
No bootable A/B slot
Failed to boot Linux, falling back to fastboot
Fastboot Reason: Fall-through from normal boot mode
Hi everyone,
I've wanted to root my Android phone for a while now, so I decided to do it these holidays, following instructions on getdroidtips ( How to Install Lineage OS 17.1 for Moto G8 Plus | Android 10 [GSI treble] (getdroidtips.com) ). I couldn't boot into TWRP recovery mode for some reason, (maybe it didn't install properly) so I tried to install Havoc OS using ADB. My phone then rebooted several times and then gave an error message, saying I could either try rebooting again or factory reset. I chose factory reset and went through the whole process again twice, the third time with Lineage OS. It then gave a different error message (in the code block). I can use the volume keys like in the bootloader, but couldn't get it to boot. I also can't access the phone over ADB.
This was my first time messing with Android beyond basic ADB commands, so I didn't really know what I was doing. I might have messed up the instructions or made some other mistake. All of my data is backed up, so all I'm hoping for is to either boot Lineage OS or somehow flash the stock ROM again.
Does anyone know how to solve this issue?
BTW I am not on Verizon.

I've run into a few of these situations. I also tried this version of Android as a Custom Rom and got a Boot Loop
I had to use TWRP to reinstall my TWRP backup.
Just in case you don't have TWRP or TWRP access for some strange reason you could try this:
I have a moto g8 plus xt2019-2
Motorola_Moto_G8_Plus_XT2019-2_DOHA_RETBR_9.0_PPI29.65-43_(MobileGuru4.com)
Motorola Flash File For All Model (Stock ROM) - Mobile Guru4
Download Motorola Flash File for all Motorola models. Here all Stock ROM and firmware files given for Motorola phones are official original files
www.mobileguru4.com
Search for this on google, when you find it download it. Then inside the zip file once you unzip it find the directory that is labeled - firmware
Inside that directory there's a file labeled "flashfile.bat" This setup uses ADB with ADB Fastboot on the phone. I assume you know how to get ADB Fastboot on your phone. When you execute the above file you will see it working in the command prompt on your computer. Let it run. It will not show anything on your phone until your phone reboots. This is what I use as a DISASTER BACKUP in case TWRP is unusable or in any way I'm unable to get to it.
I hope this helps you, it worked on my phone.

Thanks for the reply. Unfortunately, I can't try it because I've already sent the phone away to be repaired. The repair company said they would have to send it away when I originally emailed them. The repair company had a no fix no fee arrangement, so if they can't do it I'll try using fastboot. Hopefully that will happen and I won't have to pay $200.

sorry my english, i have the same problem and already try everything, rsa always fails and rsd lite does not recognize my device in windows 10, i tried to short the motherboard and it didn't work, i am seriously thinking about changing the motherboard or sell the parts

Alcatel Joy Tab 1/3T 8 - "System UI has stopped"

Hi all, I have an Alcatel Joy Tab that's all of a sudden decided to keep looping this error.
Error only pops up outside of the lock screen: on the lock screen, I'm able to swipe down the notifications bar and enter settings from there. Additionally, UI seems to be functional in the Camera app as well.
I've already factory reset once, and it was back to normal for a little while, but then it came back again. Any suggestions?
Specs:
Alcatel Joy Tab 1
Model 9027W
Android 8.1.0
Baseband version MT6739
Kernel Version 4.4.95

Most times the sole reason behind the issue “Android System UI Has Stopped” is the improper installation of the OS update or the corrupted one.
Hence do a clear re-flash of Stock ROM.

jwoegerbauer said:
Most times the sole reason behind the issue “Android System UI Has Stopped” is the improper installation of the OS update or the corrupted one.
Hence do a clear re-flash of Stock ROM.
Click to expand...
Click to collapse
Thanks for the reply, I've been looking for a stock ROM since I first had the issue. However I haven't been able to have any luck finding one. Do you have any suggestions on where to look? If I ultimately still can't find one am I SOL?
I've heard that you can just return to stock by using Alcatel's official Mobile Upgrade tool here but it keeps giving me a message saying that the version I'm using is the most updated version.
Software Drivers - Alcatel
Software Drivers
www.alcatelmobile.com

I would like to know more about this too. Same issue with poster. Any custom roms or anything out there for this?

No custom ROMs. There is one out there that is unlocked. But, I've lost the post about it. Used it to carrier unlock mine. Haven't had the time to see if it unlocked more.

This issue happens to me. Going into settings and removing the screen lock solves it (but obviously no screen lock). Formatting data allows you to use a screen lock for a while, until the issue decides to pop up again. Usually though it followed doing something like installing xposed framework or something advanced like that. But other times it seemed it may have been a result of booting my custom TWRP image. It's built from a generated device tree so it's not perfect yet.
Edit to add: I modified my fstab and removed the metadata encryption entry for userdata. I haven't seen the issue appear since. Encryption is now gone, but this thing is pretty weak as it is and I don't generally keep data that needs encrypting on it.
Edit: "SystemUI has stopped working" is solved with the latest firmware. If you can't get latest firmware (The alcatel mobile upgrade tool kept telling me I was on the latest or it would just crash) Do a google search for MTK Sugar Tool. Versions after 2018 will force the latest updates to the device over usb
Now for a better bit of info I have:
Bootloader unlock and proper Magisk root is possible on this device. In order to get to fastboot to unlock bl:
1. If you have basic experience with python, you can use this script to boot to fastboot:
MTK Bootseq: enter alternative boot modes in MediaTek-based smartphones
MTK Bootseq: enter alternative boot modes in MediaTek-based smartphones - mtk-bootseq.py
gist.github.com
2. RISKY: If you are inexperienced, need to unlock bl, and have good AV software (This is how I did it the first time, but be warned: while my up-to-date installation of Kaspersky found nothing today (10-31-21), Virustotal.com showed that around 18 databases flag this program for trojan like behavior):
Search google for "MTK Boot Mode Selector Tool by mvirus team". There are several links available all over shady blogs and such. This tool does work and is a simple exe, requiring only that proper alcatel USB drivers and fastboot drivers are installed; However, it's sketchy as hell and I suggest you read up on python and just use the first option.
I AM NOT RESPONSIBLE FOR DAMAGE CAUSED BY POTENTIAL VIRUSES IF YOU USE THE SECOND METHOD
Use either method (but you should really learn how to run python scripts and identify the path or name of serial ports in linux or windows (respectively) and use the first method) to get to fastboot and bl unlock like normal.
In windows it's just a matter of rebooting your tablet while holding volume down and watching in device manager for the correct COM port number to enter as a parameter of the command. (I.E. COM7.) Once you have the port number, you send it to the script as a command.
I.E.:
Code:
python mtk-bootseq.py FASTBOOT COM7
To get the port number in windows:
My tablet rebooted three times and reconnected while holding the volume down key. Each time it reconnected, a new entry in the device manager named "Ports (COM & LPT)" appears. This will disappear as soon as it disconnects, which seems to be after something like 3 seconds, so you have to be actively watching. If you expand "Ports (COM & LPT), after the first two boots, "MTK USB Port (COM*)" will appear, with * being a number (I.E. COM7.) On the third boot, "Preloader USB VCom Port (COM*)" will appear. This is the COM port number you are after. It will likely be different than the port number of the first two, which were identical for me.
I may make a full tutorial on both the linux and windows python methods soon (though it's pretty simple if you have basic experience with python,) but it doesn't seem like demand for bootloader unlock on this device is very high. (I have put a lot of work into this post already, however.)

cheger32 said:
This issue happens to me. Going into settings and removing the screen lock solves it (but obviously no screen lock). Formatting data allows you to use a screen lock for a while, until the issue decides to pop up again. Usually though it followed doing something like installing xposed framework or something advanced like that. But other times it seemed it may have been a result of booting my custom TWRP image. It's built from a generated device tree so it's not perfect yet.
Edit to add: I modified my fstab and removed the metadata encryption entry for userdata. I haven't seen the issue appear since. Encryption is now gone, but this thing is pretty weak as it is and I don't generally keep data that needs encrypting on it.
Now for a better bit of info I have:
Bootloader unlock and proper Magisk root is possible on this device. In order to get to fastboot to unlock bl:
1. If you have basic experience with python, you can use this script to boot to fastboot:
MTK Bootseq: enter alternative boot modes in MediaTek-based smartphones
MTK Bootseq: enter alternative boot modes in MediaTek-based smartphones - mtk-bootseq.py
gist.github.com
2. RISKY: If you are inexperienced, need to unlock bl, and have good AV software (This is how I did it the first time, but be warned: while my up-to-date installation of Kaspersky found nothing today (10-31-21), Virustotal.com showed that around 18 databases flag this program for trojan like behavior):
Search google for "MTK Boot Mode Selector Tool by mvirus team". There are several links available all over shady blogs and such. This tool does work and is a simple exe, requiring only that proper alcatel USB drivers and fastboot drivers are installed; However, it's sketchy as hell and I suggest you read up on python and just use the first option.
I AM NOT RESPONSIBLE FOR DAMAGE CAUSED BY POTENTIAL VIRUSES IF YOU USE THE SECOND METHOD
Use either method (but you should really learn how to run python scripts and identify the path or name of serial ports in linux or windows (respectively) and use the first method) to get to fastboot and bl unlock like normal.
In windows it's just a matter of rebooting your tablet while holding volume down and watching in device manager for the correct COM port number to enter as a parameter of the command. (I.E. COM7.) Once you have the port number, you send it to the script as a command.
I.E.:
Code:
python mtk-bootseq.py FASTBOOT COM7
To get the port number in windows:
My tablet rebooted three times and reconnected while holding the volume down key. Each time it reconnected, a new entry in the device manager named "Ports (COM & LPT)" appears. This will disappear as soon as it disconnects, which seems to be after something like 3 seconds, so you have to be actively watching. If you expand "Ports (COM & LPT), after the first two boots, "MTK USB Port (COM*)" will appear, with * being a number (I.E. COM7.) On the third boot, "Preloader USB VCom Port (COM*)" will appear. This is the COM port number you are after. It will likely be different than the port number of the first two, which were identical for me.
I may make a full tutorial on both the linux and windows python methods soon (though it's pretty simple if you have basic experience with python,) but it doesn't seem like demand for bootloader unlock on this device is very high. (I have put a lot of work into this post already, however.)
Click to expand...
Click to collapse
Bootloader Unlock failed. Is there any solution?

Azukegi said:
Bootloader Unlock failed. Is there any solution?
Click to expand...
Click to collapse
Did you enable OEM unlock in developer settings first?

cheger32 said:
Did you enable OEM unlock in developer settings first?
Click to expand...
Click to collapse
I eventually got it, but there's a patch for this device preventing any root and on top of that there's no custom recovery for this device :/

Azukegi said:
I eventually got it, but there's a patch for this device preventing any root and on top of that there's no custom recovery for this device :/
Click to expand...
Click to collapse
Really? I built TWRP for it, I can send it to you if you want to try it. What block is there for installing root? Originally I used a temp root to get the boot image (There should be a few exploits currently available in the latest Android release for this tablet, at least enough to dd the boot partition) and then patched it with magisk, then once I found the MTK bootseq script I flashed it with fastboot. Didn't need TWRP at all. If we have the same firmware version I could also just send my currently patched boot image.

cheger32 said:
Really? I built TWRP for it, I can send it to you if you want to try it. What block is there for installing root? Originally I used a temp root to get the boot image (There should be a few exploits currently available in the latest Android release for this tablet, at least enough to dd the boot partition) and then patched it with magisk, then once I found the MTK bootseq script I flashed it with fastboot. Didn't need TWRP at all. If we have the same firmware version I could also just send my currently patched boot image.
Click to expand...
Click to collapse
Dude no way, I would love to get that TWRP from you if possible

Azukegi said:
Dude no way, I would love to get that TWRP from you if possible
Click to expand...
Click to collapse
TWRP 3.6.1 for Alcatel 3T 8 (Maybe also generic Joytab 1?)
I built this last night, seems to work well. Let me know if there are any issues. This will be my last post in this thread as I've gotten off topic. I'll create a new thread with a guide if I find the time.
This is built from a twrp compatible device tree generated from a recovery image with a few modifcations and corrections. The kernel was built from sources released by alcatel (it took me nearly a year and some legal threats to get them to release it to me.)
just flash that to recovery in fastboot mode:
Code:
fastboot flash recovery <img filename>
Be sure to make a backup of your original if possible.
I just remembered that there's a bypass method and a useful utility in existence (located here: http://www.mediafire.com/file/qtmkilaimympapf/mtk_bypass_rev4.7z/file) for enabling the use of spflashtool to make backups and even flash images without fastboot with this device. Sorry, I'm still dusting the cobwebs off of this project.
EDIT: 23 builds later and I fixed /data decryption. As I said this will be my last post here but in case I never make a formal thread, here is a fully working twrp.
Edit again: I realized adb push and sideload wasn't working so I fixed it. Here's the latest build

I've got a 3T that I use rarely and it seems if I leave it for a while I get the same lock screen issue. I've discovered mention of a T-Mobile update that might resolve this:
Does anyone know where I can get this build and if I can force it on to my 3T. My carrier has no updates available.
Android 8.1.0
Build number: 1AWKUMK0May 14, 2021Resolves issue preventing device unlockAvailable May 14, 2021
Devices that meet the update requirements can be upgraded to the current software version.

So, I'm having the same problem. Just bought the joy tablet on Amazon. Yesterday it was working fine, then this morning got this error. I can't unlock the screen. If I use the pulldown menu I can click on one thing before the error pops up and the screen goes black then back to lock. I can't do anything on the tablet at all. Since I just bought it, should I just return it?

mnpeaches78 said:
So, I'm having the same problem. Just bought the joy tablet on Amazon. Yesterday it was working fine, then this morning got this error. I can't unlock the screen. If I use the pulldown menu I can click on one thing before the error pops up and the screen goes black then back to lock. I can't do anything on the tablet at all. Since I just bought it, should I just return it?
Click to expand...
Click to collapse
If it's too late to return it you can put it in recovery mode and try to restore it that way if that doesn't work then you can reflash it with SUGAR MTK SP

mnpeaches78 said:
So, I'm having the same problem. Just bought the joy tablet on Amazon. Yesterday it was working fine, then this morning got this error. I can't unlock the screen. If I use the pulldown menu I can click on one thing before the error pops up and the screen goes black then back to lock. I can't do anything on the tablet at all. Since I just bought it, should I just return it?
Click to expand...
Click to collapse
You can try SUGAR MTK SP

SOLVED Bricked Phone

So I have 10 years of experience of rooting phones and flashing roms etc and I think this is the first time I really bricked my phone and until now did not find i solution my self.
So how got it bricked: I was on my work, in a bit of a hurry and wanted to update my phone (dirty flash) through TWRP but the installation hanged at the last 1% or such. I let it sit for 30 min. still hangs so decided to abort and do a clean flash but again the update hangs (maybe bad download?) but along the way (probably because I was at work and didn't take the time) I think I ****ed up switching partitions or something and now I have no OS installed on my.
I can boot in to Fastboot mode, TWRP EDL mode and such
But I can't flash an new OS through TWRP because it says the following: Unable to find Partition for path '/system_root' (will post screenshot when I get home from work )
I tried MSM tool but until now I could not get the tool to see my Phone so now I am calling for the help of the XDA Community!
So do you guys have any suggestions wich wil unbrick my phone?

Try running msm from different port on your pc. Preferably a 2.0 usb if you have. Many times makes a difference. Also make sure your adb drivers are updated to latest. Many threads around talk about it.

Extracted boot file from original oneplus rom, flashed that with fastboot and like magic my problem was solved