Related
My phone hardbricked for no apparent reason, and I'm not sure what to do. Battery was at about 50% yesterday, it turned off and wouldn't turn back on. I did a soft reset, and it turned on. I watched it go as far as the logo and then had to walk away. When I came back, the phone was black again. And it hasn't turned on since. No logo, nothing. I've tried a soft reset, plus multiple other reset combinations. I plugged my phone to the computer, I get the normal connecting 'ding', but then it says that driver's device cannot be found.
I'm running stock firmware, no mods. No history of battery issues (except the normal slow decline). I've had the phone for a year and three weeks, so I'm out of warranty too. I called T-mobile and they said it sounds like a hardbrick and are willing to switch it out for $20 since I'm out of warranty. I can't do that since I'm out of the country for the next 1.5 months, so I was wondering if anyone out there had any suggestions on what to do or why this even happened?
Thanks!
goeundiane said:
My phone hardbricked for no apparent reason, and I'm not sure what to do. Battery was at about 50% yesterday, it turned off and wouldn't turn back on. I did a soft reset, and it turned on. I watched it go as far as the logo and then had to walk away. When I came back, the phone was black again. And it hasn't turned on since. No logo, nothing. I've tried a soft reset, plus multiple other reset combinations. I plugged my phone to the computer, I get the normal connecting 'ding', but then it says that driver's device cannot be found.
I'm running stock firmware, no mods. No history of battery issues (except the normal slow decline). I've had the phone for a year and three weeks, so I'm out of warranty too. I called T-mobile and they said it sounds like a hardbrick and are willing to switch it out for $20 since I'm out of warranty. I can't do that since I'm out of the country for the next 1.5 months, so I was wondering if anyone out there had any suggestions on what to do or why this even happened?
Thanks!
Click to expand...
Click to collapse
does it respond to plugging in to charge? im not 100% but if its responding at all when it gets plugged in its not hardbricked only softbricked so go from there. when i hardbricked my first s2 due to a corrupt kernel file i flashed it would not react to anything at all. complete dead weight
U stated that when u plugged it into ur computer u got a ding then says driver device not found. Sounds to me that ur not in a hard birck when I bricked mine I didn't even get that. Check out the link it well help.
http://galaxys2root.com/t-mobile-ga...ck-t-mobile-galaxy-s2-sgh-t989-android-2-3-6/
on my t989 enjoying sith3, thank u to all
Thanks for everyone's help. I ended up sending in my phone to a Samsung service center (while I was in Korea). They confirmed that it is a hardbrick. They opened it up and said it looked like there was a short and it fried the motherboard. They couldn't tell me what caused the short--they said maybe some water got into the phone through the charging port, but I know that isn't true... I had it plugged into an old power strip and maybe that's why? :crying:
Either way, I was told my only option was to get the motherboard replaced which would be $200. I told them no thanks and that I'd just get a replacement phone from T-mobile for $20.
sounds like another " I swear i didn't do anything.. it just happened" story.. classic..
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
PJcastaldo said:
sounds like another " I swear i didn't do anything.. it just happened" story.. classic..
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I know my story sounds unlikely, but it's the truth. Isn't this forum around to help fellow users? I have no reason to lie here. I actually take very good care of my phone and (after almost losing a laptop to a water spill) am extremely cautious about liquids around my electronic devices. You don't have to believe me since I'll get my phone replaced regardless. I just thought I would share the information in case someone else ends up facing the same problem.
Even now, the only cause I can come up with still is the old power strip frying the motherboard. *shrug* I would love to hear any other explanations.
Good night xda,
I am once again turning to the forum for help,this time for my older SGS3. While I upgraded to the S4,I gave my ATT s3 to my sister. I've had the phone since it was released. It does not have any physical or water damage.
Initially,I had a custom rom on it and all was well. When I gave it to my sister she did not like the rom so I flashed the stock ATT rom back on it. She used the phone for about 6 months after that with no issue,but about a month ago she complained that the phone sometime shut down randomly with no warning. The screen just went black completely,sometimes when she was not using it at all. I did witness this a few times while looking at it so I was pretty puzzled with what could cause that.
Now yesterday,she called me because the phone was completely dead. It shut down randomly again but she was not able to power it up again this time. I investigated,tried different batteries and plugged it in the pc and had to concur. It does not react at all. Black LCD,no battery logo,no even the power up vibration so I cannot access download mode. I understand the phone is now hard bricked.
I am extremely surprised the phone bricked over a certain period while I was not even flashing it. I did not flash it in the past 3 months. How could it get brick with no flash ?
I tried the SD Card image file from this thread http://forum.xda-developers.com/showthread.php?t=2345860 but it did not work. However,I do not have a 16GB micro sd like the thread suggest using,so I will try again tomorrow after I buy one.
Any ideas regarding this situation ? Is the s3 dead completely ? Would a jtag service work ? Or the sd card method ?
Thanks.
kiwi32 said:
Good night xda,
I am once again turning to the forum for help,this time for my older SGS3. While I upgraded to the S4,I gave my ATT s3 to my sister. I've had the phone since it was released. It does not have any physical or water damage.
Initially,I had a custom rom on it and all was well. When I gave it to my sister she did not like the rom so I flashed the stock ATT rom back on it. She used the phone for about 6 months after that with no issue,but about a month ago she complained that the phone sometime shut down randomly with no warning. The screen just went black completely,sometimes when she was not using it at all. I did witness this a few times while looking at it so I was pretty puzzled with what could cause that.
Now yesterday,she called me because the phone was completely dead. It shut down randomly again but she was not able to power it up again this time. I investigated,tried different batteries and plugged it in the pc and had to concur. It does not react at all. Black LCD,no battery logo,no even the power up vibration so I cannot access download mode. I understand the phone is now hard bricked.
I am extremely surprised the phone bricked over a certain period while I was not even flashing it. I did not flash it in the past 3 months. How could it get brick with no flash ?
I tried the SD Card image file from this thread http://forum.xda-developers.com/showthread.php?t=2345860 but it did not work. However,I do not have a 16GB micro sd like the thread suggest using,so I will try again tomorrow after I buy one.
Any ideas regarding this situation ? Is the s3 dead completely ? Would a jtag service work ? Or the sd card method ?
Thanks.
Click to expand...
Click to collapse
is it possible that the LCD went bad?? when you plug it into charge does it react (lcd or vibrate?) I would also suggest trying out a known battery. could be that if it is the original battery that it is so dead that I got "spikey" and finaly just died.
hope it is that simple
kiwi32 said:
Good night xda,
I am once again turning to the forum for help,this time for my older SGS3. While I upgraded to the S4,I gave my ATT s3 to my sister. I've had the phone since it was released. It does not have any physical or water damage.
Initially,I had a custom rom on it and all was well. When I gave it to my sister she did not like the rom so I flashed the stock ATT rom back on it. She used the phone for about 6 months after that with no issue,but about a month ago she complained that the phone sometime shut down randomly with no warning. The screen just went black completely,sometimes when she was not using it at all. I did witness this a few times while looking at it so I was pretty puzzled with what could cause that.
Now yesterday,she called me because the phone was completely dead. It shut down randomly again but she was not able to power it up again this time. I investigated,tried different batteries and plugged it in the pc and had to concur. It does not react at all. Black LCD,no battery logo,no even the power up vibration so I cannot access download mode. I understand the phone is now hard bricked.
I am extremely surprised the phone bricked over a certain period while I was not even flashing it. I did not flash it in the past 3 months. How could it get brick with no flash ?
I tried the SD Card image file from this thread http://forum.xda-developers.com/showthread.php?t=2345860 but it did not work. However,I do not have a 16GB micro sd like the thread suggest using,so I will try again tomorrow after I buy one.
Any ideas regarding this situation ? Is the s3 dead completely ? Would a jtag service work ? Or the sd card method ?
Thanks.
Click to expand...
Click to collapse
If she wasn't trying to flash anything, doesn't sound like a brick which, to my understanding, results from software failures. The procedure posted in the thread applies when you are trying to recover from a brick caused by firmware failure from attempting to flash the wrong bootloader so I'd be doubtful if it would help you here. This could be a specific hardware failure which is not unheard of with equipment like this. Also sounds like it gave warning of the gradual failure. When you plug it into a charging outlet, does it show any sign of life - a light or vibration? If it's an LCD failure, it probably wouldn't affect charging or recognition by your PC. If there is no sign of life at all even with different batteries, you may want to try a professional repair service as I presume exercising the warranty is not an option in view of the firmware history.
Hi,
Thanks for the replies.
I did try different batteries. The phone does not vibrate or react at all even when plugged in which does not suggest an LCD failure.
I guess you are right,it must be a hardware failure. I'm quite suprised,I thought these phones were well buit and resistant.Oh well.
She's getting a Nexus 5 now.
Thanks for the help !
So I had Paranoid ROM but for some reason when my phone would turn off completely, i would try to charge it and it would turn on for a second then turn back off, as a quick fix I would just externally charge my battery if my phone ever completely turned off (I would try to make sure to always have a charger on me) but today I got tired of it, and tried to flash CM, but I kept getting error messages trying to flash the zip. So I tried completely wiping everything (including the OS) on my phone then flashing it, still no luck. Came across this https://forums.oneplus.net/threads/fix-e-error-executing-updater-binary-in-zip.311160/ and tried it, now my phone is hardbricked... won't turn on at all, but it shows up as QHSUSB_BULK in my device manager on my computer. I've been reading some fourmes on how to unbrick a hardbricked G3 but I'm still lost. I'm coming across term like JTAG and now I'm reading that I have to completely dismantle the phone... Could someone please link me into the right direction on how to do this correctly. Do I need some type of special wiring or anything?? I know this is kind of a noob post, personal **** - family member just passed today, I have to leave in a few hours to meet my family who left at 3AM last night, in a different state... I really need a phone right now haha. If someone please could just give me a quick rundown of what i need to do that would be awesome....
P.S. - would it be worth it to just go into verizon and tell them my phone just won't turn on anymore, and they'll abide by the warrenty since it's still new, or would they still be able to figure out that it's bricked and make me pay the $600 fee??
aye_4694 said:
So I had Paranoid ROM but for some reason when my phone would turn off completely, i would try to charge it and it would turn on for a second then turn back off, as a quick fix I would just externally charge my battery if my phone ever completely turned off (I would try to make sure to always have a charger on me) but today I got tired of it, and tried to flash CM, but I kept getting error messages trying to flash the zip. So I tried completely wiping everything (including the OS) on my phone then flashing it, still no luck. Came across this https://forums.oneplus.net/threads/fix-e-error-executing-updater-binary-in-zip.311160/ and tried it, now my phone is hardbricked... won't turn on at all, but it shows up as QHSUSB_BULK in my device manager on my computer. I've been reading some fourmes on how to unbrick a hardbricked G3 but I'm still lost. I'm coming across term like JTAG and now I'm reading that I have to completely dismantle the phone... Could someone please link me into the right direction on how to do this correctly. Do I need some type of special wiring or anything?? I know this is kind of a noob post, personal **** - family member just passed today, I have to leave in a few hours to meet my family who left at 3AM last night, in a different state... I really need a phone right now haha. If someone please could just give me a quick rundown of what i need to do that would be awesome....
P.S. - would it be worth it to just go into verizon and tell them my phone just won't turn on anymore, and they'll abide by the warrenty since it's still new, or would they still be able to figure out that it's bricked and make me pay the $600 fee??
Click to expand...
Click to collapse
They shouldn't be able to tell why its bricked. Would you rather unbrick it for a small fee? I know someone who will do it for like $35 shipped. I sent it to him on Monday and it'll be here Friday. Same model, bricked flashing a different rom.
Sent From My HTC One (M9)
Hi all, ok tonight/this morning at work while on my break i went to do my usual thing of having food and watching a tv show via cartoon hd about 2mins in and my phone switched off.....now i thought it was dead so plugged in the charger but no led light, or screen on to say its charging.....i did a bit of googling and find out about the bootloop thingy buuuuut mines not looping, its swtiching on to the LG logo [i did the bootloader unlocker thingy etc so it says tha in the top corner] then it goes off.......i also get pulsing blue led lights too.....if i press, hold the power button after i get nothing, i have to take the battery out and then its rinse and repeat
Hi,
Same thing happened to me today. I was taking a shot and it switched off and same scenario.It seems that we had encountered an bootloader brick in which our device enters in some special bootloader mode in which when you connect it to the computer in the device manager it shows up as Qhsusb_bulk. I read the whole internet and there is a similar brick with G3 the guys were able to fix it. Even there is a tutorial on how to do this which I think is applicable to our device. I was able to install the required drivers and etc. but there is one big problem - I followed the guide and came into one serious problem - we need a special mbn file so we can recover our device and the sad thing is nobody on the internet doesn't have it still. There are many people like us who got selfbricked G4 and cannot fix it without this file. Please if somebody can help us please share the file so we can fix our devices. THANK YOU !
Link to the g3 unbrick guide
ive seen lots about the bootloop issue, but the thing is mine isnt doing a loop [i have to take the battery out/ pop it it back in, to switch it on then after 10-20 seconds on the LOGO it turns off
thewhisper said:
Hi,
Same thing happened to me today. I was taking a shot and it switched off and same scenario.It seems that we had encountered an bootloader brick in which our device enters in some special bootloader mode in which when you connect it to the computer in the device manager it shows up as Qhsusb_bulk. I read the whole internet and there is a similar brick with G3 the guys were able to fix it. Even there is a tutorial on how to do this which I think is applicable to our device. I was able to install the required drivers and etc. but there is one big problem - I followed the guide and came into one serious problem - we need a special mbn file so we can recover our device and the sad thing is nobody on the internet doesn't have it still. There are many people like us who got selfbricked G4 and cannot fix it without this file. Please if somebody can help us please share the file so we can fix our devices. THANK YOU !
Link to the g3 unbrick guide
Click to expand...
Click to collapse
on G2 you get security boot error phone is detected as QHUSb_BULK. on G2 the fix was to enter download mode. in G2 vol up then plug usb.
using TOT method and flash tools . flash stock firmware fixed my soft brick.
not sure about the file you mention, maybe you do need it..
jamious-daywalker said:
now i thought it was dead so plugged in the charger but no led light, or screen on to say its charging.....i did a bit of googling and find out about the bootloop thingy buuuuut mines not looping, its swtiching on to the LG logo [i did the bootloader unlocker thingy etc so it says tha in the top corner] then it goes off.......i also get pulsing blue led lights too.....if i press, hold the power button after i get nothing, i have to take the battery out and then its rinse and repeat
Click to expand...
Click to collapse
I have the issue. I don't do anything special but my phone reboot and stuck on lg logo. But now my phone doesn't want to boot. Sometimes he detect when I'm trying to charge it but often not. Yesterday I boot on download mode and recovery but today it's impossible... I think I have some hardware issue ? Or software with the bootloader...
I don't know how to fix that without access to download/recovery mode :crying:
Same here. Sometimes it boots into recovery/download but most of the times it doesn't. It's a hardware problem I think as LG officially confirmed that there were problems during the building proccess of the first G4 series. I don't want to sound bad but soon or later all phones built before october last year will get into bootloop. I was hoping it won't happen to me - I'm very light user with only light standart apps with no games and other heavy stuff, so the problem wasn't caused by overheating by heavy multitasking. Anyway it happened and I'm pretty sure it's harware related but if somebody can provide the tot and mbn files I will be more than happy to try the g2/g3 unbrick method. The main problem is that these files are not available for h815. I found on other forum tot files for other variants than h815 So if somebody have the tot filesfor h815 please share so we can try to unbrick our G4. Thanks!
same thing heppened to my g4 this week. i called lg last night and they agreed to repair it. i'd just gave them a call.
I sent mine for repair today. I hope they will agree to repare it even that it's with unlocked bootloader and with rooted custom rom !!! What you think ? Will I have problems with them because of that ?
Happened with my phone as well. It was rooted so i was hella scared if they didn't accept my phone. But soon they told me phone's motherboard has gone bad and will be replaced. Got my phone with a brand new motherboard after a couple of hours.
P.s. all your data will be gone
Sent from my LG-H818 using XDA-Developers mobile app
clotveins said:
Happened with my phone as well. It was rooted so i was hella scared if they didn't accept my phone. But soon they told me phone's motherboard has gone bad and will be replaced. Got my phone with a brand new motherboard after a couple of hours.
P.s. all your data will be gone
Sent from my LG-H818 using XDA-Developers mobile app
Click to expand...
Click to collapse
So the same problem just happened to my lg H815 with unlocked bootloader, am really f***ed without my phone, gonna call LG UK tomorrow, anything in particular I should say? also looking for solutions I saw many people are starting to have this issue now too - any official comments from LG?
P.S. if you have an LG G4 you should start backing up all your data now
This literally just happened in the last 15 minutes to me as well. Random reboot right after I woke up the phone and now stuck on the LG splash screen. Light user here, never did anything with the phone that would have heavily stressed it physically or computing-wise, so I also concur it's an inevitability for earlier runs of G4 phones.
Luckily, I backed up everything through TWRP last Thursday by chance because I was updating Xposed to the latest version and swapping to a faster 128GB microSDXC. At worst, I might have lost a handful of unimportant text messages.
Not worth the time to try to figure out any cheap fixes myself, I just got done submitting a repair request to LG.
I ordered LG G4 H815 and I hope to not see any kind of these issues
irishlad99 said:
So the same problem just happened to my lg H815 with unlocked bootloader, am really f***ed without my phone, gonna call LG UK tomorrow, anything in particular I should say? also looking for solutions I saw many people are starting to have this issue now too - any official comments from LG?
P.S. if you have an LG G4 you should start backing up all your data now
Click to expand...
Click to collapse
Guy at service center said its internally communicated all LG G4's motherboard will have to be changed at least once.
And just say you dont know what happened exactly. Slept and in the morning my phone won't work
clotveins said:
Guy at service center said its internally communicated all LG G4's motherboard will have to be changed at least once.
And just say you dont know what happened exactly. Slept and in the morning my phone won't work
Click to expand...
Click to collapse
at least once?? many had sent phone , then again having bootloop after repair..???
raptorddd said:
at least once?? many had sent phone , then again having bootloop after repair..???
Click to expand...
Click to collapse
I have got my phone repaired for like 4-5 times. 3 times motherboard change, 1 time display change and 1 time volume button pannel change.
clotveins said:
I have got my phone repaired for like 4-5 times. 3 times motherboard change, 1 time display change and 1 time volume button pannel change.
Click to expand...
Click to collapse
all under warranty?? not counting display? or did you get dead pixel?
raptorddd said:
all under warranty?? not counting display? or did you get dead pixel?
Click to expand...
Click to collapse
Yup. All under warranty and counting display replacement as well. No dead pixels as well and phone was rooted once during motherboard replacement
Sent from my LG-H818 using XDA-Developers mobile app
Hi guys, I would like to share my experience with a bricked OP3, I own my OP3 about 3 months ago, currently I'm running 3.5.3 CB, and zero problems with the device until now.
My younger brother has his OP3 about two months ago, and I don't know what's he thinking but he flashed a CM12 on his OP 3. Really I don't understand why a person could do that, however he really screw the phone. Never return from death.
I've tried all guides and possible solutions for the brick, there is no bootloader, no recovery, no vibration, no anything. The phone is really dead.
The device it's recognized by the pc after installing qualcomm drivers and after pressing power +volume up buttons, like qualcomm 9008, and it gets recognized by the unbrick took (msm download tool v3.0).
And when I start the tool it start to flash anything goes apparently well, green successful message. But phones continue as a expensive brick.
When I plugged the phone like it should be, pressing only volume up and connecting cable it gets correctly recognized like qualcomm 9008, and by the tool, but when I hit start, it give me that saharra communication failed message.
But when I unplugged and connect again and hit power + volume up, gets recognized again but I doesn't have that Sahara error and even its flashed with the tool, but phone continue to be dead.
I've disassembled the phone to see if I can see some simple trouble in the hardware maybe, I tested changing parts with my phone to see if the trouble is in some charging or display or anything like that, but all parts are working well.
Even I've put my motherboard on the dead phone and it works perfectly.
I can give up to leave this phone dead like that but I've tried anything possible so I'm planning selling spare parts.
In my country I don't have any SAT or any place like that to repair the phone.
dannytgt said:
Hi guys, I would like to share my experience with a bricked OP3, I own my OP3 about 3 months ago, currently I'm running 3.5.3 CB, and zero problems with the device until now.
My younger brother has his OP3 about two months ago, and I don't know what's he thinking but he flashed a CM12 on his OP 3. Really I don't understand why a person could do that, however he really screw the phone. Never return from death.
I've tried all guides and possible solutions for the brick, there is no bootloader, no recovery, no vibration, no anything. The phone is really dead.
The device it's recognized by the pc after installing qualcomm drivers and after pressing power +volume up buttons, like qualcomm 9008, and it gets recognized by the unbrick took (msm download tool v3.0).
And when I start the tool it start to flash anything goes apparently well, green successful message. But phones continue as a expensive brick.
When I plugged the phone like it should be, pressing only volume up and connecting cable it gets correctly recognized like qualcomm 9008, and by the tool, but when I hit start, it give me that saharra communication failed message.
But when I unplugged and connect again and hit power + volume up, gets recognized again but I doesn't have that Sahara error and even its flashed with the tool, but phone continue to be dead.
I've disassembled the phone to see if I can see some simple trouble in the hardware maybe, I tested changing parts with my phone to see if the trouble is in some charging or display or anything like that, but all parts are working well.
Even I've put my motherboard on the dead phone and it works perfectly.
I can give up to leave this phone dead like that but I've tried anything possible so I'm planning selling spare parts.
In my country I don't have any SAT or any place like that to repair the phone.
Click to expand...
Click to collapse
Damn that sucks. He probably flashed the wrong rom or something else. You should contact oneplus and see if they can do something about it cuz i reckon your brother's phone still has warranty.
dannytgt said:
Hi guys, I would like to share my experience with a bricked OP3, I own my OP3 about 3 months ago, currently I'm running 3.5.3 CB, and zero problems with the device until now.
My younger brother has his OP3 about two months ago, and I don't know what's he thinking but he flashed a CM12 on his OP 3. Really I don't understand why a person could do that, however he really screw the phone. Never return from death.
I've tried all guides and possible solutions for the brick, there is no bootloader, no recovery, no vibration, no anything. The phone is really dead.
The device it's recognized by the pc after installing qualcomm drivers and after pressing power +volume up buttons, like qualcomm 9008, and it gets recognized by the unbrick took (msm download tool v3.0).
And when I start the tool it start to flash anything goes apparently well, green successful message. But phones continue as a expensive brick.
When I plugged the phone like it should be, pressing only volume up and connecting cable it gets correctly recognized like qualcomm 9008, and by the tool, but when I hit start, it give me that saharra communication failed message.
But when I unplugged and connect again and hit power + volume up, gets recognized again but I doesn't have that Sahara error and even its flashed with the tool, but phone continue to be dead.
I've disassembled the phone to see if I can see some simple trouble in the hardware maybe, I tested changing parts with my phone to see if the trouble is in some charging or display or anything like that, but all parts are working well.
Even I've put my motherboard on the dead phone and it works perfectly.
I can give up to leave this phone dead like that but I've tried anything possible so I'm planning selling spare parts.
In my country I don't have any SAT or any place like that to repair the phone.
Click to expand...
Click to collapse
Really sorry To hear it?? BUT CM12 rom??? ? where he find it....?? if you hard bricked phone.. go to a expart devs shop.. he may be solved your problem
If your phone will not power on oneplus service center person are also not able to check how your phone will dead i think so you can claim the warranty.
CM 12 roms developed for One Plus 2,I don't really now why in the hell he do that, but he did it: https://forums.oneplus.net/threads/cyanogenmod-os-12-1-yog4pas1n0-update-25-08-15.349531/
What do you mean with expert dev shop?
Anyway I didn't think I will find some like that shop, I'm in Buenos Aires, Argentina, and maybe 99% of the cellphones technician didn't know anything about Oneplus 3,that's the reason why I've disassembled by miself.
dannytgt said:
CM 12 roms developed for One Plus 2,I don't really now why in the hell he do that, but he did it: https://forums.oneplus.net/threads/cyanogenmod-os-12-1-yog4pas1n0-update-25-08-15.349531/
What do you mean with expert dev shop?
Anyway I didn't think I will find some like that shop, I'm in Buenos Aires, Argentina, and maybe 99% of the cellphones technician didn't know anything about Oneplus 3,that's the reason why I've disassembled by miself.
Click to expand...
Click to collapse
No wonder why it got bricked xD. You should see if you still have the warranty for your brothers phone. Contact oneplus and see if they can replace the phone.
I contact oneplus and they say me I wanna contact my seller to review warranty, but I bought on "Mercado libre" some trading online place like ebay.
So we are in a really bad situation.
dannytgt said:
I contact oneplus and they say me I wanna contact my seller to review warranty, but I bought on "Mercado libre" some trading online place like ebay.
So we are in a really bad situation.
Click to expand...
Click to collapse
Well ****. Can't you contact the seller that you bought it from? Also your brother should be careful next time he flashes a rom. We all make mistakes, sometimes ppl have to learn it the hard way.
Yes this will be the first phone since 2005 year when I started to flash custom roms on samsung omnia i900, thats really dead, I bring from the death a lot of bricked phones. But this phone is really dead so I think I will start sparing parts, maybe we can recover some of the money invested on the device.