Database Users

Micromax Canvas Knight A350 Phone totally dead...

Hi,
My Mediatek Micromax Canvas Knight A350 is totally dead. Not responding at all to any buttons. No lights or battery indicator is displayed. But some warmth can be felt on the phone.
When I connect the phone to the pc with a USB cable it is detected as MTK USB Port Comxxxx
But when I use SP flash tools to download the preloader...it does nothing. Please let me know what to do...Thanks and God bless you.

Frank Morris said:
Hi,
My Mediatek Micromax Canvas Knight A350 is totally dead. Not responding at all to any buttons. No lights or battery indicator is displayed. But some warmth can be felt on the phone.
When I connect the phone to the pc with a USB cable it is detected as MTK USB Port Comxxxx
But when I use SP flash tools to download the preloader...it does nothing. Please let me know what to do...Thanks and God bless you.
Click to expand...
Click to collapse
when connecting in sp tools, press volume down button and see if the preloader starts.....mine worked this way

harvir46 said:
when connecting in sp tools, press volume down button and see if the preloader starts.....mine worked this way
Click to expand...
Click to collapse
I tried it but did not worked. when i open device and printer, i can see DA USB VCOM PORT when battery is in and MTK USB PORT when battery is removed, i guess i should see preloader but that is not happening. when i connect karbonn without battery then i see preloader there and flashing get completed successfully.
Please help my phone is not charging, power buttons also not working, Tried to hard reset by pressing power button, volume up and down simultaneously but still phone does not respond.
I request members to help. i am trying from last 15 days.

raghubar said:
I tried it but did not worked. when i open device and printer, i can see DA USB VCOM PORT when battery is in and MTK USB PORT when battery is removed, i guess i should see preloader but that is not happening. when i connect karbonn without battery then i see preloader there and flashing get completed successfully.
Please help my phone is not charging, power buttons also not working, Tried to hard reset by pressing power button, volume up and down simultaneously but still phone does not respond.
I request members to help. i am trying from last 15 days.
Click to expand...
Click to collapse
Sorry but this thread limits to A350 only.
---------- Post added at 07:55 PM ---------- Previous post was at 07:50 PM ----------
Frank Morris said:
Hi,
My Mediatek Micromax Canvas Knight A350 is totally dead. Not responding at all to any buttons. No lights or battery indicator is displayed. But some warmth can be felt on the phone.
When I connect the phone to the pc with a USB cable it is detected as MTK USB Port Comxxxx
But when I use SP flash tools to download the preloader...it does nothing. Please let me know what to do...Thanks and God bless you.
Click to expand...
Click to collapse
Using SP Flash Tool, flash the preloader.bin first.Use meta mode if not detected,all three buttons together while connecting and keep pressed until flashing starts.
If flashing was successful then your phone should at least be able to vibrate when you press the power button or boot if the correct files are present on your phone; else, flash other necessary files to make the phone boot up and start working normally again.
P.s. writing again and again is painful as I'm lazy-ass.
I'm thinking of making a thread about this but again,I'm lazy-ass.

it worked...wow...thanks ...but now it gets into a boot loop
harvir46 said:
when connecting in sp tools, press volume down button and see if the preloader starts.....mine worked this way
Click to expand...
Click to collapse
Thanks buddy, the phone started but now it ends into a bootloop. Tried getting into custom recovery and doing a factory reset. It starts and goes all the way through and finally restarts and the same thing again...bootloop....Please suggest what should I do...Thanks and God bless.
In the meanwhile i tried flashing a new custom ROM from xdafirmware.com. But the SP flash tools downloads upto 9.86MB and then the download stops...What could be the reason? Also please let me know if Miracle Box is any kind of solution for these kind of problems! Thanks and God bless.

Mr.Ak said:
Sorry but this thread limits to A350 only.
---------- Post added at 07:55 PM ---------- Previous post was at 07:50 PM ----------
Using SP Flash Tool, flash the preloader.bin first.Use meta mode if not detected,all three buttons together while connecting and keep pressed until flashing starts.
If flashing was successful then your phone should at least be able to vibrate when you press the power button or boot if the correct files are present on your phone; else, flash other necessary files to make the phone boot up and start working normally again.
P.s. writing again and again is painful as I'm lazy-ass.
I'm thinking of making a thread about this but again,I'm lazy-ass.
Click to expand...
Click to collapse
I am also talking about Micromax A350 and i am facing same problem
as written by thread creator.Please help me, all things mentioned in this thread i tried but none worked.
Please tell whether i should do all these step with battery or without battery.

Frank Morris said:
Thanks buddy, the phone started but now it ends into a bootloop. Tried getting into custom recovery and doing a factory reset. It starts and goes all the way through and finally restarts and the same thing again...bootloop....Please suggest what should I do...Thanks and God bless.
In the meanwhile i tried flashing a new custom ROM from xdafirmware.com. But the SP flash tools downloads upto 9.86MB and then the download stops...What could be the reason? Also please let me know if Miracle Box is any kind of solution for these kind of problems! Thanks and God bless.
Click to expand...
Click to collapse
What did you actually do?
What caused bootloop if full v3 rom was actually flashed?
Also,there's no custom roms on xdafrimware.com,it's only stock roms and make sure whatever you flash is for A350 only!
You can find everything on our blog:
www.canvasknightroms.blogspot.in
Good luck!
---------- Post added at 03:34 PM ---------- Previous post was at 03:32 PM ----------
raghubar said:
I am also talking about Micromax A350 and i am facing same problem
as written by thread creator.Please help me, all things mentioned in this thread i tried but none worked.
Please tell whether i should do all these step with battery or without battery.
Click to expand...
Click to collapse
Do you even know A350's battery is non-removable?
The only way you can remove it is by disassembling the device but doing that will compromise with your battery life.It should only be used in worst case scenario and everything else fails to work!

Mr.Ak said:
What did you actually do?
What caused bootloop if full v3 rom was actually flashed?
Also,there's no custom roms on xdafrimware.com,it's only stock roms and make sure whatever you flash is for A350 only!
You can find everything on our blog:
Good luck!
First of all, I apologize for my mistake. It was not a custom ROM but a Canvas Knight Stock ROM... The file name is this...Micromax_A350_V2_040614_KitKat_(by_xdafirmware.com). It's a version 2 (unmerged storage). However, earlier I had flashed a version 3 (merged storage) ROM and since it was constantly giving me trouble I tried to reflash version 2 ROM...But unable to do so...it gets stuck at 9.6MB or 0% in the SP Flash tool.
I tried the format+download option too. But in vain. Guess I am doing something wrong! What could it be? Thanks and God bless.
Btw, I have been through your blog in the past and benefited from the same. Thanks
Click to expand...
Click to collapse

Frank Morris said:
Mr.Ak said:
What did you actually do?
What caused bootloop if full v3 rom was actually flashed?
Also,there's no custom roms on xdafrimware.com,it's only stock roms and make sure whatever you flash is for A350 only!
You can find everything on our blog:
Good luck!
First of all, I apologize for my mistake. It was not a custom ROM but a Canvas Knight Stock ROM... The file name is this...Micromax_A350_V2_040614_KitKat_(by_xdafirmware.com). It's a version 2 (unmerged storage). However, earlier I had flashed a version 3 (merged storage) ROM and since it was constantly giving me trouble I tried to reflash version 2 ROM...But unable to do so...it gets stuck at 9.6MB or 0% in the SP Flash tool.
I tried the format+download option too. But in vain. Guess I am doing something wrong! What could it be? Thanks and God bless.
Btw, I have been through your blog in the past and benefited from the same. Thanks
Click to expand...
Click to collapse
What was the problem with v3?
Click to expand...
Click to collapse

Version 3 problem...
Mr.Ak said:
What was the problem with v3?
Click to expand...
Click to collapse
Version 3 booted well the first time...it went all the way...i was setting it up nicely...and it hung and just stopped. Ever since then I tried to reboot it would not load...the Canvas Knight logo with the sound would come on and then restart or get hung at that point. In short, it would not fully boot anymore except for that once!
So I decided to do away with version 3 and thought version 2 would be fine because that's what was originally on my phone...but now this is the problem...i mean the SPFT gets hung at 0%.
Thanks and God bless you.
On a different note, I would still love to have version 3 if possible since I plan to install a custom ROM...most likely Cyanogenmod....

Latest update...
Latest Update…
I finally managed to successfully flash a Kitakat 4.4.2 vs. 2 (unmerged storage) stock rom…I downloaded the file again from xdafirmware.com and flashed it. There was no problem. The phone has started and its up since the last one hour or so.
Before booting I entered into stock recovery and did a wipe data/factory reset and also wipe cache partition. So far no problem. I have not yet switched on my wifi coz I am worried it might go off again and enter a bootloop.
Battery was 95% when booted...its now 94% since one hour...I have not used the phone at all though...
Now I have a barrage of questions…
1) The IMEI is gone…I know how to get it back. But would appreciate a proper guidance on this…I have tried using Maui Meta 3G ver 6.1 and was successful in restoring my original IMEI numbers. Is there a better way out? Or should I stick to this one? Should I use IMEI&SN Writer?
2) NVRAM WARNING: Err= 0x10 …how do I fix this…I have never tried fixing this before. So no idea whatsoever. I have no backups of the original stock rom. Greatest mistake I ever did.
3) How to restore my original serial number (S/N) of the phone? I have the Original S/N but don’t know how to do it. Also, is S/N being restored a necessary requirement like IMEI numbers since it is linked to the SIM/Network?
4) How to unlock the bootloader? This is the biggest headache. I believe one cannot install custom ROM’s without unlocking the bootloader.
5) What are the best rooting apps? Is SuperSu good enough to root?
6) Which is the best custom recovery for Canvas Knight?
7) Final question, how to go about using this tool Mtk_Droid_Tool_v2.5.3
Sorry for the trouble. But I have messed up many times in the last one month with innumerable flashing of the ROM’s and zip files. Now, once bitten twice shy I want to play safe.
So please let me know your thoughts if they are fail proof and time tested. Thanks for all your help. God bless.

Frank Morris said:
Latest Update…
I finally managed to successfully flash a Kitakat 4.4.2 vs. 2 (unmerged storage) stock rom…I downloaded the file again from xdafirmware.com and flashed it. There was no problem. The phone has started and its up since the last one hour or so.
Before booting I entered into stock recovery and did a wipe data/factory reset and also wipe cache partition. So far no problem. I have not yet switched on my wifi coz I am worried it might go off again and enter a bootloop.
Battery was 95% when booted...its now 94% since one hour...I have not used the phone at all though...
Now I have a barrage of questions…
1) The IMEI is gone…I know how to get it back. But would appreciate a proper guidance on this…I have tried using Maui Meta 3G ver 6.1 and was successful in restoring my original IMEI numbers. Is there a better way out? Or should I stick to this one? Should I use IMEI&SN Writer?
2) NVRAM WARNING: Err= 0x10 …how do I fix this…I have never tried fixing this before. So no idea whatsoever. I have no backups of the original stock rom. Greatest mistake I ever did.
3) How to restore my original serial number (S/N) of the phone? I have the Original S/N but don’t know how to do it. Also, is S/N being restored a necessary requirement like IMEI numbers since it is linked to the SIM/Network?
4) How to unlock the bootloader? This is the biggest headache. I believe one cannot install custom ROM’s without unlocking the bootloader.
5) What are the best rooting apps? Is SuperSu good enough to root?
6) Which is the best custom recovery for Canvas Knight?
7) Final question, how to go about using this tool Mtk_Droid_Tool_v2.5.3
Sorry for the trouble. But I have messed up many times in the last one month with innumerable flashing of the ROM’s and zip files. Now, once bitten twice shy I want to play safe.
So please let me know your thoughts if they are fail proof and time tested. Thanks for all your help. God bless.
Click to expand...
Click to collapse
Well I hate giving bad news to people but I might know what causing all this.
As you say,the phone booted fine now but you'll likely see random hangs and sudden reboots in using it,to be sure,use it for atleast 2 hrs constantly and then we can proceed further with your questions.
In mean time,check this post:
https://forum.xda-developers.com/showpost.php?p=69482562&postcount=697

Mr.Ak said:
Well I hate giving bad news to people but I might know what causing all this.
As you say,the phone booted fine now but you'll likely see random hangs and sudden reboots in using it,to be sure,use it for atleast 2 hrs constantly and then we can proceed further with your questions.
In mean time,check this post:
https://forum.xda-developers.com/showpost.php?p=69482562&postcount=697
Click to expand...
Click to collapse
Well I tried using it for a while...no internet...just going through settings and checking...then I enabled Developers options and connected USB. Tried to check if the phone was listed on ADB etc....but then it went into a bootloop and kept shutting down after periodic bootloops...now its totally down...not responding at all.
Anyway, I think I know how to get it back when everything else fail. Until then stay blessed and don't give up.
God bless.

Frank Morris said:
Well I tried using it for a while...no internet...just going through settings and checking...then I enabled Developers options and connected USB. Tried to check if the phone was listed on ADB etc....but then it went into a bootloop and kept shutting down after periodic bootloops...now its totally down...not responding at all.
Anyway, I think I know how to get it back when everything else fail. Until then stay blessed and don't give up.
God bless.
Click to expand...
Click to collapse
How?

The Phone has been up and about for the last 6 hours now...
Mr.Ak said:
How?
Click to expand...
Click to collapse
Hi, Sorry for the sudden disappearance. I really didn't know how to reply to your "HOW"? But I knew there was a CERTAIN possibility of getting the phone back...I call it faith in God. And I have plenty of faith and I believe in the impossible coz I have seen some of the most impossible things happen in my life and around me over the years. So plain hope and faith in God was what I banked on. But I have no logical explanation to give on the phone starting again smoothly. I have been struggling with this phone for the last 45 days. And this is the first time the phone has really stayed put and it got booted in just one go!
Also your signature line was a source of continued inspiration to hit out against all the odds and doubts.
I would now kindly appreciate any help in restoring the phone to full functionality...I mean would love to hear answers for my questions from the previous post.
In the meanwhile, I did a bit of study on the Miracle Box and a tool called ALL-IN-ONE-TOOL_V2.1...
But, I don't want to jump the gun and get going...Will wait for expert advice. Until then God bless us all. Stay blessed. And yes, thanks for all the help. Shalom.

Frank Morris said:
Hi, Sorry for the sudden disappearance. I really didn't know how to reply to your "HOW"? But I knew there was a CERTAIN possibility of getting the phone back...I call it faith in God. And I have plenty of faith and I believe in the impossible coz I have seen some of the most impossible things happen in my life and around me over the years. So plain hope and faith in God was what I banked on. But I have no logical explanation to give on the phone starting again smoothly. I have been struggling with this phone for the last 45 days. And this is the first time the phone has really stayed put and it got booted in just one go!
Also your signature line was a source of continued inspiration to hit out against all the odds and doubts.
I would now kindly appreciate any help in restoring the phone to full functionality...I mean would love to hear answers for my questions from the previous post.
In the meanwhile, I did a bit of study on the Miracle Box and a tool called ALL-IN-ONE-TOOL_V2.1...
But, I don't want to jump the gun and get going...Will wait for expert advice. Until then God bless us all. Stay blessed. And yes, thanks for all the help. Shalom.
Click to expand...
Click to collapse
You don't need all those tool box.
Sp flash tools is enough to give life to your device.

Help required to set up the device fully...now that it is working!
Mr.Ak said:
You don't need all those tool box.
Sp flash tools is enough to give life to your device.
Click to expand...
Click to collapse
Hi Ak,
Thanks for your reply. My device is up and about since the last hmmm...to be exact...26 hours. I didn't have any reboots or bootloops or anything for that matter.
However, I need to set it up complete...customization I mean...and these are some of the problems I am facing... Quoting a part of the previous post to save typing...
Quote "Now I have a barrage of questions…
1) The IMEI is gone…I know how to get it back. But would appreciate a proper guidance on this…I have tried using Maui Meta 3G ver 6.1 and was successful in restoring my original IMEI numbers. Is there a better way out? Or should I stick to this one? Should I use IMEI&SN Writer?
2) NVRAM WARNING: Err= 0x10 …how do I fix this…I have never tried fixing this before. So no idea whatsoever. I have no backups of the original stock ROM. Greatest mistake I ever did.
3) How to restore my original serial number (S/N) of the phone? I have the Original S/N but don’t know how to do it. Also, is S/N being restored a necessary requirement like IMEI numbers since it is linked to the SIM/Network?
4) How to unlock the boot-loader? This is the biggest headache. I believe one cannot install custom ROM’s without unlocking the boot-loader.
5) What are the best rooting apps? Is SuperSu good enough to root?
6) Which is the best custom recovery for Canvas Knight?
7) Final question, how to go about using this tool Mtk_Droid_Tool_v2.5.3" Unquote.
In the meanwhile, I have done a little bit of study and RnD of the miracle box/MTK Droid Tools/S&N Writer tool etc. on my old Canvas HD 116. And I realized that the Miracle Box is one good tool. The IMEI No. can be changed in a jiffy. Rooting is extremely easy using this box. I did via adb.
In short, a bit too confused with too much knowledge on hand. Looking for wisdom to apply this knowledge correctly. There could be many simpler ways too!!! Any help in this regard is much appreciated.
Thanks and God bless us all. Shalom.

Frank Morris said:
Hi Ak,
Thanks for your reply. My device is up and about since the last hmmm...to be exact...26 hours. I didn't have any reboots or bootloops or anything for that matter.
However, I need to set it up complete...customization I mean...and these are some of the problems I am facing... Quoting a part of the previous post to save typing...
Quote "Now I have a barrage of questions…
1) The IMEI is gone…I know how to get it back. But would appreciate a proper guidance on this…I have tried using Maui Meta 3G ver 6.1 and was successful in restoring my original IMEI numbers. Is there a better way out? Or should I stick to this one? Should I use IMEI&SN Writer?
2) NVRAM WARNING: Err= 0x10 …how do I fix this…I have never tried fixing this before. So no idea whatsoever. I have no backups of the original stock ROM. Greatest mistake I ever did.
3) How to restore my original serial number (S/N) of the phone? I have the Original S/N but don’t know how to do it. Also, is S/N being restored a necessary requirement like IMEI numbers since it is linked to the SIM/Network?
4) How to unlock the boot-loader? This is the biggest headache. I believe one cannot install custom ROM’s without unlocking the boot-loader.
5) What are the best rooting apps? Is SuperSu good enough to root?
6) Which is the best custom recovery for Canvas Knight?
7) Final question, how to go about using this tool Mtk_Droid_Tool_v2.5.3" Unquote.
In the meanwhile, I have done a little bit of study and RnD of the miracle box/MTK Droid Tools/S&N Writer tool etc. on my old Canvas HD 116. And I realized that the Miracle Box is one good tool. The IMEI No. can be changed in a jiffy. Rooting is extremely easy using this box. I did via adb.
In short, a bit too confused with too much knowledge on hand. Looking for wisdom to apply this knowledge correctly. There could be many simpler ways too!!! Any help in this regard is much appreciated.
Thanks and God bless us all. Shalom.
Click to expand...
Click to collapse
Okay don't panic!
Clearly your device is fine by hardware stuff so let's fix some myths and problem of yours.
Firstly,this is mt6592 so you don't have to unlock any boot loader stuff.You can just root your device using kingroot or kingoroot(google it).
For more please read out this whole section,
https://canvasknightroms.blogspot.com/2015/10/rooting-canvas-knight.html?m=1
Now I believe you have root by now. Now all you need to do is get a recovery and as you're on v2 you can find it here,
https://drive.google.com/file/d/0B5W6R0DsDjWTU1o3TEpfWGFsMEE/view
This is philz recovery with OTG support.As you've root just download the IMG file and flash it though flashify,you can find it on Play store.So you've recovery!
Again,these are just suggested methods,you can do all that with other methods too.Also please stop wasting time on stuffs like miracle boxes and etc etc.
Secondly to get your imei back it would be very easy as you've recovery.
https://drive.google.com/file/d/0B6-QF5uchBNhbFlfVk1wOEthbms/view
Just flash this file in recovery and everything shld be fine.
Now to fix Nvram error,just extract the folder from this backup zip,
https://drive.google.com/file/d/0ByuIKfMkBBxBaXBZRHJnNHVRMVk/view
And using any root explorer(I prefer es file manager) go to /data root and replace nvram folder with the folder in this zip
Now the best recovery would be philz recovery for v2 but I greatly suggest you to flash v3 for a variety of reasons and custom ROMs.Yes,you need to shift to v3 to get LP or MM and new updated ROMs though you can still flash available ROMs for v2 which you can find here,
https://canvasknightroms.blogspot.in/2015/10/all-roms-link-for-v2.html?m=1
Very less isn't it? That's because storage barrier in v2.
You can find various mods here,
https://canvasknightroms.blogspot.in/2015/10/mods.html?m=1
You can find correct stock ROMs here,
https://canvasknightroms.blogspot.in/2015/10/stock-rom.html?m=1
Flashing the sim fix above will eventually fix SN too.
And yes many custom ROMs are bundled with SuperSU so you should use that.
To convert from kingroot user to super su use this guide,
https://forum.xda-developers.com/ca...ck-switch-kingroot-to-supersu-easily-t3426965
And lastly mtkdroidtools is a good tool and you should definitely have it just in case for backing up stuff and tinkering with ADB.
With all that said,you should join our Whatsapp group for more faster help and updates by messaging me on my Whatsapp No. +919468519959
Enjoy!
Edit: writing all this is a pain in ass,at least one thanks is deserved

Thank you so much...
Mr.Ak said:
Okay don't panic!
Clearly your device is fine by hardware stuff so let's fix some myths and problem of yours.
Firstly,this is mt6592 so you don't have to unlock any boot loader stuff.You can just root your device using kingroot or kingoroot(google it).
For more please read out this whole section,
https://canvasknightroms.blogspot.com/2015/10/rooting-canvas-knight.html?m=1
Now I believe you have root by now. Now all you need to do is get a recovery and as you're on v2 you can find it here,
https://drive.google.com/file/d/0B5W6R0DsDjWTU1o3TEpfWGFsMEE/view
This is philz recovery with OTG support.As you've root just download the IMG file and flash it though flashify,you can find it on Play store.So you've recovery!
Again,these are just suggested methods,you can do all that with other methods too.Also please stop wasting time on stuffs like miracle boxes and etc etc.
Secondly to get your imei back it would be very easy as you've recovery.
https://drive.google.com/file/d/0B6-QF5uchBNhbFlfVk1wOEthbms/view
Just flash this file in recovery and everything shld be fine.
Now to fix Nvram error,just extract the folder from this backup zip,
https://drive.google.com/file/d/0ByuIKfMkBBxBaXBZRHJnNHVRMVk/view
And using any root explorer(I prefer es file manager) go to /data root and replace nvram folder with the folder in this zip
Now the best recovery would be philz recovery for v2 but I greatly suggest you to flash v3 for a variety of reasons and custom ROMs.Yes,you need to shift to v3 to get LP or MM and new updated ROMs though you can still flash available ROMs for v2 which you can find here,
https://canvasknightroms.blogspot.in/2015/10/all-roms-link-for-v2.html?m=1
Very less isn't it? That's because storage barrier in v2.
You can find various mods here,
https://canvasknightroms.blogspot.in/2015/10/mods.html?m=1
You can find correct stock ROMs here,
https://canvasknightroms.blogspot.in/2015/10/stock-rom.html?m=1
Flashing the sim fix above will eventually fix SN too.
And yes many custom ROMs are bundled with SuperSU so you should use that.
To convert from kingroot user to super su use this guide,
https://forum.xda-developers.com/ca...ck-switch-kingroot-to-supersu-easily-t3426965
And lastly mtkdroidtools is a good tool and you should definitely have it just in case for backing up stuff and tinkering with ADB.
With all that said,you should join our Whatsapp group for more faster help and updates by messaging me on my Whatsapp No. +919468519959
Enjoy!
Edit: writing all this is a pain in ass,at least one thanks is deserved
Click to expand...
Click to collapse
Hi Ak,
I went through your entire post and more or less got most of the useful and helpful information. I have not gone through all the links and will do so in due course.
I have been on your website and have read quite a bit and was happy to see the dedication and commitment to help people like us.
I am sure the phone like you said is stable and away from hardware issues. I will consider flashing vs. 3 soon. Yes, i agree with you there are more choices for vs. 3. I did peep into the website last week to see the big list of custom ROM's for vs. 3.
Last but not the least, God bless you. Shalom.

Frank Morris said:
Hi Ak,
I went through your entire post and more or less got most of the useful and helpful information. I have not gone through all the links and will do so in due course.
I have been on your website and have read quite a bit and was happy to see the dedication and commitment to help people like us.
I am sure the phone like you said is stable and away from hardware issues. I will consider flashing vs. 3 soon. Yes, i agree with you there are more choices for vs. 3. I did peep into the website last week to see the big list of custom ROM's for vs. 3.
Last but not the least, God bless you. Shalom.
Click to expand...
Click to collapse
What about joining our whatsapp group?

Lenovo a6000 Plus total dead

Help my device is total dead.. first i want to revert back from lollipop to kitkat, i flash L2KK.zip from the right thread (for a6000 plus) then reboot recovery and stuck at bootloop. i want to try to install twrp for kitkat but i end up installing something else with fastboot. now i cant even turn on my device. however my pc still show "device driver is not successfully installed". Please help me.

Irwan Fauzi said:
Help my device is total dead.. first i want to revert back from lollipop to kitkat, i flash L2KK.zip from the right thread (for a6000 plus) then reboot recovery and stuck at bootloop. i want to try to install twrp for kitkat but i end up installing something else with fastboot. now i cant even turn on my device. however my pc still show "device driver is not successfully installed". Please help me.
Click to expand...
Click to collapse
Plz any developers help him
Sent from my Lenovo A6000 using Tapatalk

Find how to flash device with qfil in google

Irwan Fauzi said:
Help my device is total dead.. first i want to revert back from lollipop to kitkat, i flash L2KK.zip from the right thread (for a6000 plus) then reboot recovery and stuck at bootloop. i want to try to install twrp for kitkat but i end up installing something else with fastboot. now i cant even turn on my device. however my pc still show "device driver is not successfully installed". Please help me.
Click to expand...
Click to collapse
Explain the exact steps and error you received after trying to flash recovery for kk through fastboot. Then only I can be able to help.
Also check if you can enter into fastboot (by pressing POWER + VOL DOWN) and recovery (POWER + VOL DOWN + VOL UP and leave the POWER key once the lenovo logo shows up).

sasukay said:
Explain the exact steps and error you received after trying to flash recovery for kk through fastboot. Then only I can be able to help.
Also check if you can enter into fastboot (by pressing POWER + VOL DOWN) and recovery (POWER + VOL DOWN + VOL UP and leave the POWER key once the lenovo logo shows up).
Click to expand...
Click to collapse
Im on rr 5.7.3
- first i wipe data,dalvik,cache and system in twrp
- flash L2KK.zip
- reboot recovery and stuck at boot (lenovo powered by android)
i know i have to flash twrp for kitkat right? but i end up flashing something about partition because i wasnt giving attention. not my phone cannot go into recovery or fastboot. just a red notification light. i know this is my fault.

@Irwan Fauzi, You've told these steps earlier. I want to know if you can boot into recovery or fastboot.

sasukay said:
@Irwan Fauzi, You've told these steps earlier. I want to know if you can boot into recovery or fastboot.
Click to expand...
Click to collapse
nope

Irwan Fauzi said:
nope
Click to expand...
Click to collapse
Then the only method is qfil method
Btw, did you tried the methods i advised to boot into recovery and fadtboot. Because in 90% cases, people were not doing it the right way to boot into recovery, and were stating that it's a hard brick.

sasukay said:
Then the only method is qfil method
Btw, did you tried the methods i advised to boot into recovery and fadtboot. Because in 90% cases, people were not doing it the right way to boot into recovery, and were stating that it's a hard brick.
Click to expand...
Click to collapse
maybe i have to send my phone to service center because qualcomm doesnt detect my device.

sasukay said:
Explain the exact steps and error you received after trying to flash recovery for kk through fastboot. Then only I can be able to help.
Also check if you can enter into fastboot (by pressing POWER + VOL DOWN) and recovery (POWER + VOL DOWN + VOL UP and leave the POWER key once the lenovo logo shows up).
Click to expand...
Click to collapse
You are the best developer here I've ever seen helping other developers and thanks a lot really....while others don't even open their mouth except for saying don't post this here don't ask this question here......They think they are gods but I hope they realize soon that they are nothing to anyone of us here . Making some **** modifications to an existing software and creating WhatsApp grps and feeling as legends themselves.Everybody knows they don't even know how to make a small toast in any android app.......

Sloved
i have sent my device to service center.. thanks to everyone who trying to help me..

Irwan Fauzi said:
maybe i have to send my phone to service center because qualcomm doesnt detect my device.
Click to expand...
Click to collapse
For QFIL to work you have to use the diagnostic mode on your device. First DOWNLOAD THESE USB DIAGNOSTIC DRIVERS and install them. Then press VOL UP + POWER on the device. A menu will open where you have to choose "Download". Then the screen will turn black and then connect your phone to pc. The device manager should show USB diagnostic on 9008 on com5 or something in the PORTS. Update the driver, using the drivers I provided; if the drivers didn't get installed automatically for the phone. Then, if everything is fine, you should see your phone on QFIL. Then click on choose build and flash the row firmware for your phone, which you can DOWNLOAD FROM HERE.
bvsbrk said:
You are the best developer here I've ever seen helping other developers and thanks a lot really....while others don't even open their mouth except for saying don't post this here don't ask this question here......They think they are gods but I hope they realize soon that they are nothing to anyone of us here . Making some **** modifications to an existing software and creating WhatsApp grps and feeling as legends themselves.Everybody knows they don't even know how to make a small toast in any android app.......
Click to expand...
Click to collapse
Bro, its nothing like that. I'm just another guy, like you, who has done things and hence know how to do them. I'm not a dev. I have no idea how a ROM, or kernel, or for that matter how a bug is fixed or how a patch is made or even how to ise Git. So, basically I just test things, that's what I do. You can't even me with the repected devs.
And, you should not crirticise them, in any way. They cook up the roms and kernels for us for whatever time they could manage. And, note this, They do not do it for themselves. They are not making any money out of this. They are doing all this hardwork for us. So, the least you could do is to be respectful to them, for what they are doing.
And, moreover, they don't reply much at such threads because, firstly they don't have thay much time. All the spare time they have, they use it to bring something good for us. Guys like me, who have some time, are the ones who can (and should) reply and help others. Secondly, the bricking issue has been reported hundreds, or even thousands, of times now. So, instead of asking the same question again and again, which kind of is spamming the forums, one should first check google and xda if the same question has been answered earliet. I, myself, has answered the same things to folks hundreds of time now. That, even makes me angry sometimes. I'm like, Due Seriously. You could get the answer a few posts below. And even a blind person could see that. But, alas, it is what it is.
So, in all, Respect Devs, for what they are doing for us. They are not obliged to do it for us and are not even paid for it. They do it just so that guys like us, who otherwise would've stuck with stock KK or buggy stock LP can enjoy the goodness of Marshmallow and Nougat roms.
Sigh...I don't write this long usually. But you made me type all of this.
---------- Post added at 12:53 PM ---------- Previous post was at 12:50 PM ----------
@Irwan Fauzi, Ok I was a bit late. But, you were too fast at that. BTW, what fid they ask you. And did they just accepted to repair it, considering it was you fault.

sasukay said:
For QFIL to work you have to use the diagnostic mode on your device. First DOWNLOAD THESE USB DIAGNOSTIC DRIVERS and install them. Then press VOL UP + POWER on the device. A menu will open where you have to choose "Download". Then the screen will turn black and then connect your phone to pc. The device manager should show USB diagnostic on 9008 on com5 or something in the PORTS. Update the driver, using the drivers I provided; if the drivers didn't get installed automatically for the phone. Then, if everything is fine, you should see your phone on QFIL. Then click on choose build and flash the row firmware for your phone, which you can DOWNLOAD FROM HERE.
Bro, its nothing like that. I'm just another guy, like you, who has done things and hence know how to do them. I'm not a dev. I have no idea how a ROM, or kernel, or for that matter how a bug is fixed or how a patch is made or even how to ise Git. So, basically I just test things, that's what I do. You can't even me with the repected devs.
And, you should not crirticise them, in any way. They cook up the roms and kernels for us for whatever time they could manage. And, note this, They do not do it for themselves. They are not making any money out of this. They are doing all this hardwork for us. So, the least you could do is to be respectful to them, for what they are doing.
And, moreover, they don't reply much at such threads because, firstly they don't have thay much time. All the spare time they have, they use it to bring something good for us. Guys like me, who have some time, are the ones who can (and should) reply and help others. Secondly, the bricking issue has been reported hundreds, or even thousands, of times now. So, instead of asking the same question again and again, which kind of is spamming the forums, one should first check google and xda if the same question has been answered earliet. I, myself, has answered the same things to folks hundreds of time now. That, even makes me angry sometimes. I'm like, Due Seriously. You could get the answer a few posts below. And even a blind person could see that. But, alas, it is what it is.
So, in all, Respect Devs, for what they are doing for us. They are not obliged to do it for us and are not even paid for it. They do it just so that guys like us, who otherwise would've stuck with stock KK or buggy stock LP can enjoy the goodness of Marshmallow and Nougat roms.
Sigh...I don't write this long usually. But you made me type all of this.
---------- Post added at 12:53 PM ---------- Previous post was at 12:50 PM ----------
@Irwan Fauzi, Ok I was a bit late. But, you were too fast at that. BTW, what fid they ask you. And did they just accepted to repair it, considering it was you fault.
Click to expand...
Click to collapse
Bro don't misunderstand me. Whatever you said is totally correct. I'm not criticizing any developer and as you said without them we would have stuck in buggy lp kk roms. But every body has their own perspective .There is no offence in not answering any question but instead of that some people insult by saying you don't know anything(Though the question is not nerdy type) . You can see this happening in WhatsApp groups as I experienced this personally.
I meant that to those people. So no offence to any developer. You need not take it to that serious . It's just my opinion and I'm sure everybody has their own opinions.

bvsbrk said:
Bro don't misunderstand me. Whatever you said is totally correct. I'm not criticizing any developer and as you said without them we would have stuck in buggy lp kk roms. But every body has their own perspective .There is no offence in not answering any question but instead of that some people insult by saying you don't know anything(Though the question is not nerdy type) . You can see this happening in WhatsApp groups as I experienced this personally.
I meant that to those people. So no offence to any developer. You need not take it to that serious . It's just my opinion and I'm sure everybody has their own opinions.
Click to expand...
Click to collapse
I can understand who you are talking about
No problem
I never considered myself above anyone so something

Already sent my phone to repair and they told me it was motherboard. Strange because I can see the red notification light even if the phone is dead so I doubt it was motherboard. I still didn't receive the phone, I just canceled it. However I will try your method. I end up buying a new phone lenovo s60-a. It has the same hardware as lenovo a6000/+. Does it safe to flash any custom ROM from lenovo a6000/+ to lenovo s60-a? I'll make a backup first of course. This device is awesome but no custom ROM.

Irwan Fauzi said:
Already sent my phone to repair and they told me it was motherboard. Strange because I can see the red notification light even if the phone is dead so I doubt it was motherboard. I still didn't receive the phone, I just canceled it. However I will try your method. I end up buying a new phone lenovo s60-a. It has the same hardware as lenovo a6000/+. Does it safe to flash any custom ROM from lenovo a6000/+ to lenovo s60-a? I'll make a backup first of course. This device is awesome but no custom ROM.
Click to expand...
Click to collapse
I would not suggest flashing a6000 s ROM on your new phone or you may end up like your a6000

Irwan Fauzi said:
Already sent my phone to repair and they told me it was motherboard. Strange because I can see the red notification light even if the phone is dead so I doubt it was motherboard. I still didn't receive the phone, I just canceled it. However I will try your method. I end up buying a new phone lenovo s60-a. It has the same hardware as lenovo a6000/+. Does it safe to flash any custom ROM from lenovo a6000/+ to lenovo s60-a? I'll make a backup first of course. This device is awesome but no custom ROM.
Click to expand...
Click to collapse
Don't you ever try to flash custom ROM that not supported for your phone

HardBricked OP5, plz help! :(

Hi, guys.
Today, my OP5 decided to troll me. I was using normally him, when suddenly it started to lags pretty bad. I restarted and he continued to lags and freeze. I made a wipe cache via stock recovery (i didnt made any change at all in it, no unlocked bootloader, no root). That's when my nightmare begins. It begins to bootloop. Sometimes i was able to start the boot animation, but then it just restarts to the beginning. I tried a lot of tips, wiping cache, system, etc. Then, i left it charging. When i tried to turn on again, it worked like nothing ever happened to him. I made a backup of my personal data fast, scared to him suddenly restart again. After that, i decided to made a Factory Reset, clean up everything. When i did it, he started the lag and freezes again. I was at lost. That's was when i decided to use the official unbrick tool, to make the cleanest OP5 ever possible. I grabbed the archives from this link and followed this tutorial. When i was executing the programa, in the userdate.img, he showed a error. When i saw it, i just stopped and closed the program. Now, my OP5 is hardbricked. The only sign of life that i get from him is when i connect him at the PC. I can identify it as qualcoom 9008, but when i try to run the program, he just fail and show me error 258.
Plz, i need some orientations. I have been read things for about 10 hours and didnt found a solution. I live abroad for any oneplus tech center, and i believe, for the other posts that i read, that online tech support wouldn't help me a lot. I really don't like to make this kind of post but i am kind of desesperate. I dont have money to afford another phone
Again, sry to disturb you all. Sry if i broke some rule of the forum too. And sry for my bad english, i hope that i was able to communicate right.
EDIT: I just tried in another computer. Same error appears. :'(

Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine

I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Maybe you have a encryption problem, all your Tools/Topic are so old for the actual versions (Oreo 8.X OOS / 8.1 OOS)
I advise to you (in the first time), to flash this TWRP (using fastboot, very simple) just follow this guide : here
If you can flash TWRP, your phone is not bricked, you will boot in TWRP:
- Format Data > tape "yes" > Reboot in TWRP
- Copy/Past xXx 10.0 ROM to test, install and xXx Rom will fix/install for you the best OOS Custom ROM for your OP5 with a great Aroma Installer.
If TWRP with this rom work perfectly, you wil able to restore a official stock OOS for sure, just flash original/stock recovery (fastboot), wipe all data/partitions, install your OOS rom and it's fine
Click to expand...
Click to collapse

Pho3nX said:
Hummm why follow a Unbrick Topic with tools for ...3T ?
Click to expand...
Click to collapse
I used the tools for 5. Just the procedure that i get from this topic. :T I am gonna try the method that you gave me now brb.
EDIT: Just tried this. My cellphone cant be recognized in fastboot devices. As a said, i am not getting any response for him, just when i plug it in the PC. So i wasn't able to unlock bootload or anything like that. I tried just to plug it and see if fastboot was able to identifying it, but it wasn't.

bartito said:
I think @cidsantiago says they bootloader isn't unlocked.
He needs to know that unlock the bootloader implies lost all /sdcard data and also installed apps and settings) before start the TWRP install process...
Click to expand...
Click to collapse
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.

cidsantiago said:
Yes, it should not be unlocked. But at the moment, i am taking anything, really. I just want to use my phone.
Click to expand...
Click to collapse
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.

bartito said:
Wipe your device data from the stock recovery.
You loss the settings and downloaded apps but not requires to unlock the bootloader.
Click to expand...
Click to collapse
I can't access recovery anymore, as i said. The only sign of life that i get is when i connect it in the PC.

I guess i have to do something to restore the basics partitions of my cellphone. Like recovery, boot, etc. But i just have the official tool to do that. There is another way? Like transfering directly by the COM port?

Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol

Mash1ro said:
Have you tried following this guide? https://forum.xda-developers.com/oneplus-5/how-to/guide-unbrick-guide-hard-bricked-t3761706
---------- Post added at 01:30 PM ---------- Previous post was at 01:26 PM ----------
I had the same exact problem with my old One plus One. Spent like 4 days trying to unbrick it. That msm tool did the fix for me. Also, in that link to the guide you provided, doesn't it flash the Chinese version of the OS? If that's the case, I don't think it was a good idea to do so lol
Click to expand...
Click to collapse
In one of the links, it had the OOS and the HOS. I tried to use the msm tool in one of them, but it didnt worked I'm gonna try the archives in this link that you gave me. It may work brb with updates.

Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.

I am getting the same error 258 in this post. :T I posted there to see if the OP can help me. But thx for your help @Mash1ro

Mash1ro said:
Don't worry though, it happens to plenty of people. It happened to me as well, and everyone eventually fixes it. It is unlikely that it is a hardware problem, so just following the correct steps should get it working. Keep trying stuff out, it's very good that your computer recognizes it as a qualcomm port, as far as I know that's all you need to flash the necessary things in order for it to boot.
Click to expand...
Click to collapse
Thx for your support! I will continue to try stuff

Try reading the comments from this post as well https://forum.xda-developers.com/oneplus-3t/help/hard-bricked-op3t-t3574720/page2
2 of the people had the same error as you, and one of them solved the issue by changing the USB port.
---------- Post added at 02:26 PM ---------- Previous post was at 02:23 PM ----------
But don't use the same files and all that stuff, since that's for the 3T. Try to pick out the things that might help but use the files for the OnePlus 5 only

After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?

cidsantiago said:
After try the unbrick procedure in 3 different PCs, using about 10 different USB ports, i still getting the same error in the same step. When downloading cache.img, he stuck in about mid bar, and shows me the warning: SendProgramCommand Failed, Error: 258". Besides that, he turns on the green led and stop being recognize by the PC. Then i have to hold power and turn off the green led. :T Maybe i can use a linux to access the partitions?
Click to expand...
Click to collapse
it seems like a hardware problem, i was facing this on different phone ( 5X )

Apayah said:
it seems like a hardware problem, i was facing this on different phone ( 5X )
Click to expand...
Click to collapse
yeah... But it is kind of weird. He was running smoothly, until suddenly started lag and freeze. He didn't fall or any of that... I think is just a defective phone. Doesn't find another explanation to that.

I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.

david19au said:
I think your best option is to RMA the device through OnePlus. Since you haven't rooted it or anything, they should repair it for you.
Click to expand...
Click to collapse
I already contact the store that i bought to get my warranty. Unfortunately, i didn't bought it in oneplus.net, bcs they don't deliver in my country. I am hoping that everything work out

Guys, in the end, i RMA my device back to the seller and gonna have a refund Thank you for your help. So sad that this phone came faulty :T
Best regards to you all!

OP6T won't boot

Hi all,
I'm facing a really strange & annoying issue ... I'm running latest OOS version, unlocked bootloader, TWRP installed, root via Magisk. & substraturm theming.
I uninstalled all my overlays, rebooted my phone and boom, here the deal : my phone won't boot at all.
I tried to press the power button for something like 30sec, nothing, not even a vibration.
I tried to reboot in recovery/fastboot via the volume keys + power button, nothing happens.
I tried to charge the phone, maybe I was running out of battery..? Nevertheless, nothing happens ...
I tried to reboot into recovery via `fastboot boot twrp-xxx.img`, but fastboot can't detect my phone as it stay totally powered off....
Anyone get a idea about the how to fix it & how it happend ? It's really annoying as I'm in travel and I don't get any extra phone ...
Thanks all
edit: Ho yeah, I'm running linux & I don't have access to any windows computer

hard brick mode, try msm download tool

edsmat said:
hard brick mode, try msm download tool
Click to expand...
Click to collapse
Thanks for your reply, I was about to try that.
But after letting my phone cool down for 1h or so; I tried to press ALL the buttons in the same time for 1min or so and guess what, my phone rebooted ... No idea why ...
Where are the custom rom :crying:

allen2398 said:
Thanks for your reply, I was about to try that.
But after letting my phone cool down for 1h or so; I tried to press ALL the buttons in the same time for 1min or so and guess what, my phone rebooted ... No idea why ...
Where are the custom rom :crying:
Click to expand...
Click to collapse
You don't want a custom ROM. Fingerprint sensor doesn't work under custom ROMs at the moment.
Also trying to charge with the phone off with Magisk installed will give the perception of a brick.
You will need to jump through hoop to get the device to boot again.
Don't ever try to charge with the phone off with Magisk.

tech_head said:
You don't want a custom ROM. Fingerprint sensor doesn't work under custom ROMs at the moment.
Also trying to charge with the phone off with Magisk installed will give the perception of a brick.
You will need to jump through hoop to get the device to boot again.
Don't ever try to charge with the phone off with Magisk.
Click to expand...
Click to collapse
strange that

tech_head said:
You don't want a custom ROM. Fingerprint sensor doesn't work under custom ROMs at the moment.
Also trying to charge with the phone off with Magisk installed will give the perception of a brick.
You will need to jump through hoop to get the device to boot again.
Don't ever try to charge with the phone off with Magisk.
Click to expand...
Click to collapse
What are you talking about. I charge all the time with my device powered off and I always have magisk installed and never got the perception of a brick like you describe it. And custom rom are all extremely stable for this device fp is the only issue and it's got work being done and its already working on custom in the test groups on telegram. And they is always face unlock which is better than fp anyways.

se7ensde said:
What are you talking about. I charge all the time with my device powered off and I always have magisk installed and never got the perception of a brick like you describe it. And custom rom are all extremely stable for this device fp is the only issue and it's got work being done and its already working on custom in the test groups on telegram. And they is always face unlock which is better than fp anyways.
Click to expand...
Click to collapse
With Magisk charging with power off will cause the phone to stop at the "you phone corrupt" screen.

tech_head said:
With Magisk charging with power off will cause the phone to stop at the "you phone corrupt" screen.
Click to expand...
Click to collapse
LMAO no it won't. Like I said earlier I do this all time with no issues. You have something weird going on with your device.

se7ensde said:
LMAO no it won't. Like I said earlier I do this all time with no issues. You have something weird going on with your device.
Click to expand...
Click to collapse
Actually not. With the latest, I guess one or two releases of Magisk this is now fixed. Magisk forces something other than a normal boot from a patched image. My Essential had the charging while off for a year and this phone up until I installed the latest release.
So you are correct current version of Magisk does not cause the issue.

Another thing which is strange.
Since that bug yesterday I can't connect my phone to the computer to browse the internal DD.
Instead my file explorer (on the computer) display me a unknown dir in which I've got some sh script & window exe (I think they're there to install the op drivers).
No one get a idea of the why & how to fix it to go back to the OG behavior ?

allen2398 said:
Another thing which is strange.
Since that bug yesterday I can't connect my phone to the computer to browse the internal DD.
Instead my file explorer (on the computer) display me a unknown dir in which I've got some sh script & window exe (I think they're there to install the op drivers).
No one get a idea of the why & how to fix it to go back to the OG behavior ?
Click to expand...
Click to collapse
That's odd.... It sounds like a driver issue with your computer more than anything. BUT, do you get an option to change to file transfer mode from your pull down menu? I had an issue where it wouldn't even give me that option, and what actually worked for me was to plug my 6T into a USB 2.0 port on the BACK of my computer. Try these things out.
---------- Post added at 05:56 AM ---------- Previous post was at 05:56 AM ----------
Also, about the magisk charging thing? I've never tried to charge my phone while it was off with magisk installed, but that just sounds...... Weird!

allen2398 said:
Another thing which is strange.
Since that bug yesterday I can't connect my phone to the computer to browse the internal DD.
Instead my file explorer (on the computer) display me a unknown dir in which I've got some sh script & window exe (I think they're there to install the op drivers).
No one get a idea of the why & how to fix it to go back to the OG behavior ?
Click to expand...
Click to collapse
I have the extra same issue after the latest stable update....

H4X0R46 said:
That's odd.... It sounds like a driver issue with your computer more than anything. BUT, do you get an option to change to file transfer mode from your pull down menu? I had an issue where it wouldn't even give me that option, and what actually worked for me was to plug my 6T into a USB 2.0 port on the BACK of my computer. Try these things out.
---------- Post added at 05:56 AM ---------- Previous post was at 05:56 AM ----------
Also, about the magisk charging thing? I've never tried to charge my phone while it was off with magisk installed, but that just sounds...... Weird!
Click to expand...
Click to collapse
Yes I get the option to change to file transfer mode. My computer only got USB 3.0 port, I'll try to connect it to a 2.0 when I'm back from my trip. Thx for the tips 
 @loganville did you try the 2.0 trick ?

allen2398 said:
Yes I get the option to change to file transfer mode. My computer only got USB 3.0 port, I'll try to connect it to a 2.0 when I'm back from my trip. Thx for the tips
@loganville did you try the 2.0 trick ?
Click to expand...
Click to collapse
Yeah for sure! Report back when you get back and let us know if any of this worked! :good:

H4X0R46 said:
Yeah for sure! Report back when you get back and let us know if any of this worked! :good:
Click to expand...
Click to collapse
Just came back; and what a oddly thing :
- usb2 work on windows
- usb3 work on windows
- can't test usb2 on linux
- usb3 doesn't work on linux
I'll investigate the web about that

allen2398 said:
Just came back; and what a oddly thing :
- usb2 work on windows
- usb3 work on windows
- can't test usb2 on linux
- usb3 doesn't work on linux
I'll investigate the web about that
Click to expand...
Click to collapse
Odd. Yeah these newer Android devices are just weird like that! I've been told the Pixel devices are just as finicky as the 6T and I'm sure others out there are as well! Glad you're able to get a connection on Windows though! [emoji106]

After 2 month or so I think I found the reason of the bug : tremble !
The bug occured since I did the last oxygenos update (at the time) - maybe it came from the fact that the update was installed on the second partition !
I gonna try to make the new oxygenos update (which will be installed on the first partition) to ensure that. I'll come back here once it's done !

It was that ! After a update to the last OOS (which was installed on partition A) I can finally access my internal storage from a usb 3 on linux

[RE-OPENED] Possibly Bricked My Phone. AGAIN.

Edit: My phone is miraculously recovered, see last post for details. Big thanks to everyone throwing in suggestions! :highfive::good:
Edit 2: Here we go again... Had my phone set up for a day and after installing the "App Systemizer" Magisk module, the restart upon booting is back. Please help, is magisk causing this??
So, I'm reaching out because I'm now at a loss. I have no other ideas as to how I could fix my phone.
Background:
A few days ago, I was setting my alarm for work in the morning and I noticed the UI was extremely sluggish. I then locked my phone with the lock button and a notification saying "Powering down..." came up and proceeded to shut off. At this point, I knew I should re-flash my ROM/boot.img first. Didn't help, every boot up ended in the same "Powering down..." message and shutting down within 15 seconds of unlocking the device. At this point, I think to fully wipe and revert to stock. Now, I try to install the latest stock OOS via fastboot. Same result as before when I booted after the fastboot install. And this is where it ended... I tried to use the MSM tool and the device went BLACK with no response after that.
What I've tried:
- fastboot
-MSM Tool
- randomly pressing/holding all physical buttons in every order
- leaving the device plugged in to charge overnight
Conclusion:
Any suggestions other than what I've tried would greatly be appreciated. If, by some chance, my phone is truly bricked... would anyone know about whether T-Mobile would replace the device for me if I act clueless as to what happened to my device? lol, I'm on the Jump! plan, so this phone isn't even paid off yet.
Thanks!

Only time I saw this "powering down" issue was when I updated my phone without disabling my Magisk modules. That time I just removed the module using TWRP and the phone booted.
When you used the MSM tool did it complete successfully? It should take around 5 minutes to restore. Mine took 302 seconds on the dot. That should clear out any and all software issues. If the problem still persists after a successful MSM restore then my thoughts would be hardware damage.

I assume your battery is still working (?), and you can't reach TWRP either?
Have you tried this https://www.getdroidtips.com/oneplus-6t-black-screen-death-issue/ ?

When my 6T didn't respond at all. It would stay black no matter what but I knew it was charged. All I did was hold volume up and the power button for a good 15 to 30 seconds. Then it booted up
Sent from my [device_name] using XDA-Developers Legacy app

Car Transport in mumbai
Car Transport In Mumbai[/URL]

Hey u...I also had the same issue...SHUTTING DOWN...in every boot....and I had fixed it....anyways if u have fixed it ...m glad....if not whatsapp or telegram me on +918898340211

Jager said:
Only time I saw this "powering down" issue was when I updated my phone without disabling my Magisk modules. That time I just removed the module using TWRP and the phone booted.
When you used the MSM tool did it complete successfully? It should take around 5 minutes to restore. Mine took 302 seconds on the dot. That should clear out any and all software issues. If the problem still persists after a successful MSM restore then my thoughts would be hardware damage.
Click to expand...
Click to collapse
MSM didn't even pick up my device... it said something along the lines of "No communication"
F5:ed said:
I assume your battery is still working (?), and you can't reach TWRP either?
Have you tried this https://www.getdroidtips.com/oneplus-6t-black-screen-death-issue/ ?
Click to expand...
Click to collapse
Thanks for the suggestion! Unfortunately, all steps were tried before seeing this post and didn't help.
i7vSa7vi7y said:
When my 6T didn't respond at all. It would stay black no matter what but I knew it was charged. All I did was hold volume up and the power button for a good 15 to 30 seconds. Then it booted up
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
This is important... but did not help me... initially.
sanjeev7 said:
Hey u...I also had the same issue...SHUTTING DOWN...in every boot....and I had fixed it....anyways if u have fixed it ...m glad....if not whatsapp or telegram me on +918898340211
Click to expand...
Click to collapse
Well boys, she's up and running again!
Here's what happened:
- I left my phone on the stock charger (wall-block and cord) to make sure the battery wasn't just dead. This resulted in nothing, still no response from the device.
- Early in the morning, while getting ready for work, I continued to press all physical buttons in any and every order as well as holding different combinations of the buttons. Nothing.
- Gave up, took it off the charger, and tossed the damned thing to the side. I took my iPhone X to work and hated every minute of it lmao.
- I then get off work and decide to mash the physical buttons in a half fit-of-rage and half last-ditch-effort.. and BOOM! The screen flashes with a screen saying the battery is dead in a few different languages.
(I never plugged a device in to charge so fast... lol)
At this point, I decided to fastboot the latest stock OOS (.13) to both A/B partitions and she's like brand new!!!! I spent the day rooting and reinstalling everything today and I'm honestly relieved. :victory: All of my data is lost... pics of my baby sister after just being born and of my fiance But order has been restored.
tl;dr - My phone is fixed, don't ever underestimate the power of button mashing! :good:

..Cory.. said:
MSM didn't even pick up my device... it said something along the lines of "No communication"
Click to expand...
Click to collapse
I suggest you re-read the thread on the MSM tool. It will always work unless there is physical damage to your device. The reason you got the "No communication" error is because you were not in the Qualcom bootloader mode or whatever, not fastboot and not TWRP, there is a third mode accessible by holding certain buttons while plugging in your phone to the computer, in this mode the screen does not light up or anything. Read the thread, the steps are in there. I guarantee that if you can get the MSM tool to restore your phone everything will be working on it.
I even tested the MSM tool once. I wiped all partitions on the phone including the boot partition. The MSM tool can always fix a Software issue.
Edit: Didn't see that you said it was fixed already. My message here is still valid though. Some day you will have to use the MSM tool so it's a good idea to get familiar with it.

Jager said:
I suggest you re-read the thread on the MSM tool. It will always work unless there is physical damage to your device. The reason you got the "No communication" error is because you were not in the Qualcom bootloader mode or whatever, not fastboot and not TWRP, there is a third mode accessible by holding certain buttons while plugging in your phone to the computer, in this mode the screen does not light up or anything. Read the thread, the steps are in there. I guarantee that if you can get the MSM tool to restore your phone everything will be working on it.
I even tested the MSM tool once. I wiped all partitions on the phone including the boot partition. The MSM tool can always fix a Software issue.
Edit: Didn't see that you said it was fixed already. My message here is still valid though. Some day you will have to use the MSM tool so it's a good idea to get familiar with it.
Click to expand...
Click to collapse
Well, like I said... I couldn't just change modes at will... I was legit stuck with the screen completely off and no response to any physical button being pressed. So as long as switching modes was impossible... so was the MSM tool. I read a F*CK-TON of threads before I posted this, I haven't seen anyone else post about being in my situation of not being able to boot into ANY kind of a mode... at all lol.

Bumping to ask for help again...
I had my phone all set up, stable OOS (.13) on both partitions. I installed the "App Systemizer" Magisk module in order to move an app to the system. When I rebooted after the module installation, the "Phone is rebooting..." message comes up after a few seconds post-boot and go straight to recovery every time.
I'm lost at this point. :/

You'd probably be better off seeking support in the mod thread.

..Cory.. said:
Bumping to ask for help again...
I had my phone all set up, stable OOS (.13) on both partitions. I installed the "App Systemizer" Magisk module in order to move an app to the system. When I rebooted after the module installation, the "Phone is rebooting..." message comes up after a few seconds post-boot and go straight to recovery every time.
I'm lost at this point. :/
Click to expand...
Click to collapse
Go to TWRP
go to file manager
Delete /data/adb/ *all files related to Magisk*
This will work

..Cory.. said:
Bumping to ask for help again...
I had my phone all set up, stable OOS (.13) on both partitions. I installed the "App Systemizer" Magisk module in order to move an app to the system. When I rebooted after the module installation, the "Phone is rebooting..." message comes up after a few seconds post-boot and go straight to recovery every time.
I'm lost at this point. :/
Click to expand...
Click to collapse
I have never read about a really bricked OP6T, there is always a solution (and use MsmDownloadTool if nothing else work....).
Now, when you already have "bricked" your phone once and fixed it, you are asking the community for help again... It's obvious to me that you are fiddling around with your device without any clue, and creates a mess for yourself. Why?
Stay outside what you do not understand, and stick to stock version only in the future.
To try to help you, I suggest you use MsmDownloadTool.

WOOOOOOOW.
So this whole time it was Magisk. I never knew about Magisk Manager for recovery. That thing is a MUST HAVE.
So what happened was the new Magisk update broke a few modules I use daily. After using MM to disable every module one-by-one, I found the culprit.
The thing that always gets me is the A/B partition BS. But I guess Magisk was really the pain in my ass!
Closing thread for good, thanks to everyone giving suggestions!!! :good:

Cablespider said:
You'd probably be better off seeking support in the mod thread.
Click to expand...
Click to collapse
Right, thank you! I just feel as if this section is less intrusive for noob questions haha
sanjeev7 said:
Go to TWRP
go to file manager
Delete /data/adb/ *all files related to Magisk*
This will work
Click to expand...
Click to collapse
Thank you! Used this to clean some of the files up when reinstalling the new stable update.
F5:ed said:
I have never read about a really bricked OP6T, there is always a solution (and use MsmDownloadTool if nothing else work....).
Now, when you already have "bricked" your phone once and fixed it, you are asking the community for help again... It's obvious to me that you are fiddling around with your device without any clue, and creates a mess for yourself. Why?
Stay outside what you do not understand, and stick to stock version only in the future.
To try to help you, I suggest you use MsmDownloadTool.
Click to expand...
Click to collapse
If you don't think I deserve help, move on to another thread! :good: No problems here though; I took advice I found helpful and I fixed my phone :victory:
I'm far from a noob though, this is just my first A/B parition device. I had an iPhone for years and was last active on XDA before Magisk was even released.We all need to brush up on the basics every once in a while, though!

..Cory.. said:
Right, thank you! I just feel as if this section is less intrusive for noob questions haha
Thank you! Used this to clean some of the files up when reinstalling the new stable update.
If you don't think I deserve help, move on to another thread! :good: No problems here though; I took advice I found helpful and I fixed my phone :victory:
I'm far from a noob though, this is just my first A/B parition device. I had an iPhone for years and was last active on XDA before Magisk was even released.We all need to brush up on the basics every once in a while, though!
Click to expand...
Click to collapse
Thank you for the arrogance.
I have already tried to help you (twice, in this your own thread). Your arrogant answer tells me that the iPhone-comfort zone suite you best.
In short: you act as an imbecile (since I have experience of you, and have "discussed" with you, before outside this thread).
So, sell your OP6t and buy an iPhone - problem solved.

F5:ed said:
Thank you for the arrogance.
I have already tried to help you (twice, in this your own thread). Your arrogant answer tells me that the iPhone-comfort zone suite you best.
In short: you act as an imbecile (since I have experience of you, and have "discussed" with you, before outside this thread).
So, sell your OP6t and buy an iPhone - problem solved.
Click to expand...
Click to collapse
That systemize tool is not very stable in my experience. There is two location's of system apps in my experience which is most always only about at least half correct a little less than half the time. Is that if you use something like MiXplorer and move the apk into either system apps or priv apps then reboot it is much easier to do than rely on scripts that may not be setup for the device you are using. It shouldn't take any longer than 25.89 seconds to manually move an app.

..Cory.. said:
WOOOOOOOW.
So this whole time it was Magisk. I never knew about Magisk Manager for recovery. That thing is a MUST HAVE.
So what happened was the new Magisk update broke a few modules I use daily. After using MM to disable every module one-by-one, I found the culprit.
The thing that always gets me is the A/B partition BS. But I guess Magisk was really the pain in my ass!
Closing thread for good, thanks to everyone giving suggestions!!! :good:
Click to expand...
Click to collapse
Download the magisk uninstaller zip , put it on your internal storage
So when magisk modules messing up with your boot
Go to twrp, flash the uninstaller zip , reboot to twrp, reflash magisk and then you're be able to boot again to your rom ..

F5:ed said:
Thank you for the arrogance.
I have already tried to help you (twice, in this your own thread). Your arrogant answer tells me that the iPhone-comfort zone suite you best.
In short: you act as an imbecile (since I have experience of you, and have "discussed" with you, before outside this thread).
So, sell your OP6t and buy an iPhone - problem solved.
Click to expand...
Click to collapse
Sorry, I forgot ur the internet law enforcement. Yes, sir! Please dont shoot! :HandsUp: :ShakingInFear: :Terrified: :NotReally: :WatchOut_InternetBadAss:

Jager said:
I suggest you re-read the thread on the MSM tool. It will always work unless there is physical damage to your device. The reason you got the "No communication" error is because you were not in the Qualcom bootloader mode or whatever, not fastboot and not TWRP, there is a third mode accessible by holding certain buttons while plugging in your phone to the computer, in this mode the screen does not light up or anything. Read the thread, the steps are in there. I guarantee that if you can get the MSM tool to restore your phone everything will be working on it.
I even tested the MSM tool once. I wiped all partitions on the phone including the boot partition. The MSM tool can always fix a Software issue.
Edit: Didn't see that you said it was fixed already. My message here is still valid though. Some day you will have to use the MSM tool so it's a good idea to get familiar with it.
Click to expand...
Click to collapse
The MSM Tool does not fix everything. The 6T I have is brand new was working fine until I installed LOS on A & B and deleted the persist partition. I have flashed the original stock rom as well as 3 other OOS roms. MSM Tool completes the flash no problem with no errors, but on every rom it only makes it to the boot screen and hangs. If the MSM Tool is supposed to fix this, then why isn't it getting fixed? I don't know what else to try to fix? Usually it fixes most problems for me, but on this occasion it is not.