Database Users

LG G2 Wont power on (bricked?)

I have the D803 and I was trying to get KK before the OTA as Canada we never get an OTA.
I rooted the LG, I installed the custom Rom, I installed an updated GAPPS and it wasnt working. I then went and installed another GAPPS overtop and I got stuck in boot loop. After I tried recovery from ADB I tried to restore from TRWP and it didnt take. After I rebooted nothing turned on, no LED, I tried ALL button combinations and nothing comes on at all. I am wondering if the phone died and now will not charge...I started with 60% but the last time i saw it it was down to 15% just thinking maybe it died completely and without any software to boot it wont charge...I have had it on charge for 8 hrs since and still nothing...ADB does not read it.
Please help!

Usualy is good to have at least 50% battery. Did you tried to charge it trough the wall charger ? Can you enter in download mode ? From fully shutted down , hold vlume up while plugging it to the computer. It should start by displaying Download mode logo. If you get to this point then the device is not bricked, and from here you should be able to reinstall the original 4.2.2(in my case is D80210A_00.kdz, because i have the 802 variant ).

Alexzander said:
Usualy is good to have at least 50% battery. Did you tried to charge it trough the wall charger ? Can you enter in download mode ? From fully shutted down , hold vlume up while plugging it to the computer. It should start by displaying Download mode logo. If you get to this point then the device is not bricked, and from here you should be able to reinstall the original 4.2.2(in my case is D80210A_00.kdz, because i have the 802 variant ).
Click to expand...
Click to collapse
Thanks for your reply,
I did have at least 50% and I believe I blew through the 50% during the process. I tried through wall charger for 8 hours yes Still nothing. I tried entering download mode (I tried all button combinations while plugged into the computer, plugged into the wall, not plugged in). I would love to be able to reinstall the original 4.2.2 This whole process has discouraged me from furthering my Custom rom use lol.

Bobert the great said:
Thanks for your reply,
I did have at least 50% and I believe I blew through the 50% during the process. I tried through wall charger for 8 hours yes Still nothing. I tried entering download mode (I tried all button combinations while plugged into the computer, plugged into the wall, not plugged in). I would love to be able to reinstall the original 4.2.2 This whole process has discouraged me from furthering my Custom rom use lol.
Click to expand...
Click to collapse
We're you trying to install a lg based kit Kat Rom or an aosp based Rom. You say you wanted to get it before the ota in Canada so it makes it seem as though you were wanting to flash an lg Rom but you say you flashed gapps. Gapps are only used on aosp based custom roms
Sent from my LG-D801 using Tapatalk

rawdaddymagraden said:
We're you trying to install a lg based kit Kat Rom or an aosp based Rom. You say you wanted to get it before the ota in Canada so it makes it seem as though you were wanting to flash an lg Rom but you say you flashed gapps. Gapps are only used on aosp based custom roms
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
I was installing a custom rom, Mahdi It was not a LG rom. I am sorry If I got you confused here.

Bobert the great said:
Thanks for your reply,
I did have at least 50% and I believe I blew through the 50% during the process. I tried through wall charger for 8 hours yes Still nothing. I tried entering download mode (I tried all button combinations while plugged into the computer, plugged into the wall, not plugged in). I would love to be able to reinstall the original 4.2.2 This whole process has discouraged me from furthering my Custom rom use lol.
Click to expand...
Click to collapse
"This whole process has discouraged me from furthering my Custom rom use lol." Not at all. Just a few days ago I "soft bricked" my phone. I had D80210a and i forgot to update it to D80210e, and went streight to root it and add recovery twrp. Everything was oky doky till i started updating the 10e the OTA way. It just stoped. I had no download mode anymore. But I was lucky enough to still have the twrp recovery . So I used the terminal command inside the twrp . I unbricked it using this command : dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Note that if for some reason if I didn't had any recovery mode my other option was adb . Of course this thrilling adventure didn't stop me to customise my phone.

Sorry to sound dumb here, I am pretty much a rookie at this stuff I just follow directions well lol.
Where did you use that command?

Alexzander said:
"This whole process has discouraged me from furthering my Custom rom use lol." Not at all. Just a few days ago I "soft bricked" my phone. I had D80210a and i forgot to update it to D80210e, and went streight to root it and add recovery twrp. Everything was oky doky till i started updating the 10e the OTA way. It just stoped. I had no download mode anymore. But I was lucky enough to still have the twrp recovery . So I used the terminal command inside the twrp . I unbricked it using this command : dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
Note that if for some reason if I didn't had any recovery mode my other option was adb . Of course this thrilling adventure didn't stop me to customise my phone.
Click to expand...
Click to collapse
I am guessing this was done through Ubuntu Which i do not have. What is the best way to run ubuntu on Windows? I have done some searching and would you think the virtual box (virtual machine) would be best?
Thank you again!

Is there Anyone in southern Ontario familair with this that wants to make alittle extra cash on the side?
I just want my phone fixed....

Bobert the great said:
Is there Anyone in southern Ontario familair with this that wants to make alittle extra cash on the side?
I just want my phone fixed....
Click to expand...
Click to collapse
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2582142&page=18
---------- Post added at 08:14 AM ---------- Previous post was at 08:14 AM ----------
Bobert the great said:
Is there Anyone in southern Ontario familair with this that wants to make alittle extra cash on the side?
I just want my phone fixed....
Click to expand...
Click to collapse
PM me, I may be able to help you out

[Q] Alcatel One Touch Pop C7 Bricked (?)

There is this thing. I have bought this phone not so long ago. Recently, after a night of loading, using for a bit and hiding it in my pocket, I discovered that it "turned off". Thought to myself: "Yo, that is weird." But I also thought that it's probably discharged (but that's impossible!). I took it home and plugged it into my computer. The PC kept playing connected and disconected sounds in short succesion, but the LED on the phone was glowing like it was supposedly charging. I stupidly voided my warranty by rooting and installing CWM (with which I didn't do anything).
So the question is: Is my battery busted or is the phone bricked somehow? Can I do anything about it?
No wait. That's two questions. Anyway. Thanks in advance!

Oh come on! Anybody? I'm in a bad situation here.

Did you flash anything through ClockWorkMod?
Btw have you left your phone simply charging for 1+ hour straight? If you didn't try it. If your phone heats up like (let's say hell for now) then it's probably bricked. Anyway try to turn it on. I have this phone to. If the battery is empty it simply needs to be put on a charging for a while.
And I got the phone to now. Avoid to root mediatek devices that aren't that widely used.
It's a pain to find support for it.

Well, as I said, I didn't do anything with CWM. Although I tried to install a custom ROM and ended up just wiping data. But then the phone worked. Now it's just dark, and, when plugged in, the LED is glowing, but nothing really happens (except for plugged in and out sounds on the PC).
Could it be that I overcharged it?

It's possible you could restore the phone using this tool: http://forum.xda-developers.com/showpost.php?p=44509214&postcount=407
Here are a couple of backups I found:
http://forum.xda-developers.com/showpost.php?p=51243254&postcount=12
http://forum.xda-developers.com/showpost.php?p=51647278&postcount=17
http://forum.xda-developers.com/showpost.php?p=51658198&postcount=18
I do not know how much it matters on these phones about which carrier or firmware is compatible with each other, so you are on your own for that part. I can not confirm all or even any of the files linked work or will work for you.

If I could even turn on the phone there would be no problem. The whole problem is that the freaking Alcatel won't even go into recovery. It's just black

Archimondde said:
If I could even turn on the phone there would be no problem. The whole problem is that the freaking Alcatel won't even go into recovery. It's just black
Click to expand...
Click to collapse
My understanding is that to get to the mode to make the flash tool work, you have to have it off anyway. Then you load the file in the flash tool and then tool will tell you when to plug the phone in. Read here for more details: http://forum.xda-developers.com/showthread.php?t=1982587

It all seems for naught when I can't even get the computer to recognize the phone. Just keeps playing these annoying sound effects (plugged in and out). My guess is that the battery's fried, or maybe just overcharged, because the PC keeps ding donging like the phone was trying to turn on but couldn't. I'll try with a new battery and get back to you.

Well. As I have a replacement phone, and no time to check the battery, I think this thread can be counted as closed, for I see no further developments on this topic. Thanks for trying. Really appreciate it

Sorry! Hate to see a device go down like that. Hope the new one serves you better!

es0tericcha0s said:
Sorry! Hate to see a device go down like that. Hope the new one serves you better!
Click to expand...
Click to collapse
i actually bricked mine becous im impatiant its 7040a it has no recovery menu and doesnt boot and ive been getting annoyed at it for a while nothing seems to work at all i cant flashany firmware at all although the small led on the front of the device is lit and the drivers on the computer are working and are picking up the device just fine im finding this quiet a puzzle do you have any more sugestions ??

If you guys want some custom roms for you Alcatel Pop c7 device i found some link and it works just fine .. just message me and ill give you the link here are some screenshots

Link.Please.
---------- Post added at 06:17 PM ---------- Previous post was at 06:15 PM ----------
xmak17(AlcatelPopC7) said:
If you guys want some custom roms for you Alcatel Pop c7 device i found some link and it works just fine .. just message me and ill give you the link here are some screenshots
Click to expand...
Click to collapse
Link.Please.

here is a link for s5 custom rom : http://www.mediafire.com/download/hatcbk3s6krkp7g/S5+LUIS+ALEAN.zip (this is not mine)

xmak17(AlcatelPopC7) said:
here is a link for s5 custom rom : http://www.mediafire.com/download/hatcbk3s6krkp7g/S5+LUIS+ALEAN.zip (this is not mine)
Click to expand...
Click to collapse
Thank you.I tested this ROM.All is well,but this ROM is battery killer.

mugy said:
Thank you.I tested this ROM.All is well,but this ROM is battery killer.
Click to expand...
Click to collapse
no i dont think so .. mine is perfectly normal when i tested it..

xmak17(AlcatelPopC7) said:
no i dont think so .. mine is perfectly normal when i tested it..
Click to expand...
Click to collapse
30% battery for 8h,on stand by.
I tested ROMS:
Xperia LUIS ALEAN (battery killer).My favorite custom rom.
Rom Samsung Note Pop c7(no permissions to remove apps from internal to external memory)
Style L LUIS ALEAN(no see internal memory)
STYLE Lv1.6 LUIS ALEAN(no see internal memory)
Rom JMCHCY(works fine,but ugly interface).This is stock rom 01001.
I am now on stock 01004 ROM.

mugy said:
30% battery for 8h,on stand by.
I tested ROMS:
Xperia LUIS ALEAN (battery killer).My favorite custom rom.
Rom Samsung Note Pop c7(no permissions to remove apps from internal to external memory)
Style L LUIS ALEAN(no see internal memory)
STYLE Lv1.6 LUIS ALEAN(no see internal memory)
Rom JMCHCY(works fine,but ugly interface).This is stock rom 01001.
I am now on stock 01004 ROM.
Click to expand...
Click to collapse
yeah i would say stock rom is better but the problem is its too boring and i cant even use gravitybox with it cuz it just bootloop ..

Alcatel Pop C7 7041x bricked (help)
Hello,
I have Alcatel Pop C7 7041x and I've done all the previous steps and I can not start. Can you help me?
thank you
https://www.youtube.com/watch?v=1pHTZm7FhGM
https://www.youtube.com/watch?v=qENMjLKz-t8

goncaje said:
Hello,
I have Alcatel Pop C7 7041x and I've done all the previous steps and I can not start. Can you help me?
thank you
https://www.youtube.com/watch?v=1pHTZm7FhGM
https://www.youtube.com/watch?v=qENMjLKz-t8
Click to expand...
Click to collapse
For custom ROM,you need to install custom CWM.I see on your phone's stock CWM.You must re-install stock ROM.Download from Alcatel site Mobile Upgrade S 4.3.1,follow the instructions and re-install.

Slow charging + not recognized by PC, only on Nougat ROMs?

I decided to go into custom ROMs, but it's been nothing but trouble ever since.
NOTE: I own two cables and it's the same with both
I updated to the latest nougat build with Cosmic OS, and then realized my phone wasn't recognized by my computer anymore.
Tried RR, same deal.
Went back to MM oxygen OS, and all my problems were gone.
I loved Nougat, so I made a backup of MM and decided to stay on Cosmic OS for now, even though It's not recognized by my computer unless I put it in fastboot mode.
Two weeks into Cosmic OS, I realized that my phone has been charging a lot slower than usual (I used to just leave it overnight, and when I tried to charge during the day I realized that it was charging too slow)
I then thought: what if it's my cable about to die?
So I broke out my backup cable, same thing.
Again, back in Oxygen OS, the problem was gone.
I don't know what to do about this. I am tired of OOS, and don't want to go back, but slow charging is a huge disadvantage and I don't think it's good for my battery either.

update: I've tried RR, CosmicOS, LineageOS, and AOSiP.. all of them with the same issue for me.. I don't know why
I just keep having to restore that OOS 3.6.0 backup i made after accidentally bricking my phone after trying CosmicOS/RR for the first time lol

It is because of the ****ty charging drivers by Oneplus. They work for half of the users and break for other half. Boeffla has a kernel with 2 different versions of this driver baked in his kernel. Try both these variants and see if any works for you.

Harpratap said:
It is because of the ****ty charging drivers by Oneplus. They work for half of the users and break for other half. Boeffla has a kernel with 2 different versions of this driver baked in his kernel. Try both these variants and see if any works for you.
Click to expand...
Click to collapse
Thanks! I'll give it a try!
Never messed with kernels in the past, but it's worth the shot
EDIT: I forgot to mention in the OP, that my computer will not recognize the phone even when i am on TWRP, for some strange reason.. would the kernel solve that as well?
Also, I see that boeffla is only for CM based ROMs, I don't really like LineageOS compared to Cosmic OS, do you think it would work anyway?

Niko. said:
Thanks! I'll give it a try!
Never messed with kernels in the past, but it's worth the shot
EDIT: I forgot to mention in the OP, that my computer will not recognize the phone even when i am on TWRP, for some strange reason.. would the kernel solve that as well?
Also, I see that boeffla is only for CM based ROMs, I don't really like LineageOS compared to Cosmic OS, do you think it would work anyway?
Click to expand...
Click to collapse
No, a kernel won't fix that. Something wrong with your PC driver. Nothing related to phone.
You can try but it has slim chances of working.

Harpratap said:
No, a kernel won't fix that. Something wrong with your PC driver. Nothing related to phone.
You can try but it has slim chances of working.
Click to expand...
Click to collapse
I tried it on two PCs and had the same problem on both
the installation thing for the OP drives wasn't even showing up

Niko. said:
I tried it on two PCs and had the same problem on both
the installation thing for the OP drives wasn't even showing up
Click to expand...
Click to collapse
Download universal adb drivers? It's just a simple setup file and works for almost all Android phones

Niko. said:
I tried it on two PCs and had the same problem on both
the installation thing for the OP drives wasn't even showing up
Click to expand...
Click to collapse
Do you get the option to change from charging to file transfer on the phone when you plug it in.
When you pull the menu down you should have a USB setting thing.

pops106 said:
Do you get the option to change from charging to file transfer on the phone when you plug it in.
When you pull the menu down you should have a USB setting thing.
Click to expand...
Click to collapse
I dont have that option when I drop down the status bar. In developer options when I select file transfer , it goes back to charging . I've used two different PC's and I'm pretty confident that I have installed the drivers correctly . And MTP doesn't work in twrp either . I'm on stock oxygen os right now any ideas ?

Everything you say tells me you should try a different cable. If that doesn't work, I have no idea.

Murbert said:
Everything you say tells me you should try a different cable. If that doesn't work, I have no idea.
Click to expand...
Click to collapse
I've used 3 cables and 4 different PC's nothing

Thanks to everyone for all of your replies. I was kinda stubborn about the whole "trying a different cable" thing because everything was working normally on my old cable, as long as I was on Oxygen OS..
I will never know why, but changing the cable did the trick. Now getting charging a lot faster than I was used to, even on my old setup!
Loving Nougat on CosmicOS!

Niko. said:
Also, I see that boeffla is only for CM based ROMs, I don't really like LineageOS compared to Cosmic OS, do you think it would work anyway?
Click to expand...
Click to collapse
Buddy read the boeffla's OP carefully. Its for stock OOS right?

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!

[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.