So my phone was acting weird recently, with all sorts of various problems popping out and I simply could not live with it. Before continuing, I would like to say that I hope you guys could help me out here, and thanks a lot in advance. Anyways, I decided that instead of just re-flashing the same ROM on top of the current one on my phone, why not fully erase all the partitions first (big mistake) and fresh install the ROM?
I erased my individual partitions (TWRP - rajlko) with this command, and managed to erase up to 7 partitions.
mke2fs -T ext4 /dev/block/mmcblk0p1/2/3/4/5/6/7
After formatting ALL the partitions, I immediately rebooted my phone (another huge mistake - the boot.img or whatsoever is probably deleted now) and now, it boots up with a black screen, and that it shows up as Qualcomm HS-USB QDLoader 9008 in the device manager.
Please do give some insights and suggestions on this matter. I do not have the time to travel to the nearest service center as of now, and that the repair service takes at least 3 weeks. Hopefully there are solutions to this though. From what I know, the partitions (with the names) are there, just that the necessary files required to boot the phone is not there. Is there any way about this? Thank you!
at present we have no solution for this situation.
most important thing is service rom & we do not how to get it.
when I hard bricked my phone, i surrender this to service center & I got my phone back in 5 days.
there are approx 51 mmcblk in ze550kl.
Ouch. Sad news. There is a tool called QFIL from QPST bundle, which can download firmware to device in Qualcomm HS-USB QDLoader 9008 mode, but I don't know if we have the images to flash. This is all new, I don't believe anyone has tried to unbrick their laser on xda yet
wickedpygmy said:
Ouch. Sad news. There is a tool called QFIL from QPST bundle, which can download firmware to device in Qualcomm HS-USB QDLoader 9008 mode, but I don't know if we have the images to flash. This is all new, I don't believe anyone has tried to unbrick their laser on xda yet
Click to expand...
Click to collapse
I think I was first who hard brick my ze550kl, after doing one week research, I surrender it to my local asus service center.
I got my device repaired in 5 days.
we do not have necessary files of ze550kl.
rajlko said:
I think I was first who hard brick my ze550kl, after doing one week research, I surrender it to my local asus service center.
I got my device repaired in 5 days.
we do not have necessary files of ze550kl.
Click to expand...
Click to collapse
Rajiko are you able to explain exactly what the service rom does, and why it is needed? Or do you know any useful URL that we can read to learn more? I don't really understand how the service rom fits into the bigger picture and it would be great to understand more - for example, can we use any msm8939 unbrick tools if we have a snapdragon 615 device, or does it need to be from Asus?
wickedpygmy said:
Rajiko are you able to explain exactly what the service rom does, and why it is needed? Or do you know any useful URL that we can read to learn more? I don't really understand how the service rom fits into the bigger picture and it would be great to understand more - for example, can we use any msm8939 unbrick tools if we have a snapdragon 615 device, or does it need to be from Asus?
Click to expand...
Click to collapse
service rom is which have all data of partition which if by mistake deleted or currupted ,so we can full restore our mobile rom partition so can we dont have to go to service center and can have much time and have development of roms on way easier
wickedpygmy said:
Rajiko are you able to explain exactly what the service rom does, and why it is needed? Or do you know any useful URL that we can read to learn more? I don't really understand how the service rom fits into the bigger picture and it would be great to understand more - for example, can we use any msm8939 unbrick tools if we have a snapdragon 615 device, or does it need to be from Asus?
Click to expand...
Click to collapse
Have you every face a situation where there is no recovery, no fastboot, no system runs, you are unable to see any sign of booting device, no light on your mobile scree.
When you connect your mobile phone to your pc you found yourself in a new situation, your pc displays a popup installing driver for newly found device, when this installation done, you found a new device in your pc's device manager somename .... 9008.
In this situation, we need some tools that may detect our device & here it comes to role of service rom.
our xda forum is good url to read & learn with every situation regarding our mobiles.
every manufacture have different boot partitions & commands, so we need service rom from particular manufacturer for particular device.
Thanks for your help guys! I decided to send it in and it came back within 5 days. The engineers diagnosed the problem as the motherboard being "dead" (stated so on the letter), though I am pretty sure that's not the case, if you know what I mean.
Upon receiving my phone and popping off the back cover, there is actually a "hole" next to the SIM slot 2, which could be easily identified with a yellow taping around it. With the vague image of my previous ZenFone 2 Laser, as well as with the aid of images online, I am sure that this is definitely a new revision for that particulator motherboard, or so to say, a revised version. One thing I noticed is the dramatic improvement in battery life. Using the exact same applications as before, I would only get about 3-4 hours max screen-on-time, whereas with the repaired phone, I could easily get to about 8-11 hours of screen-on-time without limiting any of my application usages.
Another thing that I noticed was that the phone was significantly faster. I have the MSM8916 processor variant, and with the previous phone, it would lag occasionally. Whereas after being repaired, everything was butter smooth. Extremely smooth.
I am not sure if this is really because of the, so to speak, "updated" version of the motherboard, or simply a placebo effect, but hopefully it's not the latter.
Rizzed said:
Thanks for your help guys! I decided to send it in and it came back within 5 days. The engineers diagnosed the problem as the motherboard being "dead" (stated so on the letter), though I am pretty sure that's not the case, if you know what I mean.
Upon receiving my phone and popping off the back cover, there is actually a "hole" next to the SIM slot 2, which could be easily identified with a yellow taping around it. With the vague image of my previous ZenFone 2 Laser, as well as with the aid of images online, I am sure that this is definitely a new revision for that particulator motherboard, or so to say, a revised version. One thing I noticed is the dramatic improvement in battery life. Using the exact same applications as before, I would only get about 3-4 hours max screen-on-time, whereas with the repaired phone, I could easily get to about 8-11 hours of screen-on-time without limiting any of my application usages.
Another thing that I noticed was that the phone was significantly faster. I have the MSM8916 processor variant, and with the previous phone, it would lag occasionally. Whereas after being repaired, everything was butter smooth. Extremely smooth.
I am not sure if this is really because of the, so to speak, "updated" version of the motherboard, or simply a placebo effect, but hopefully it's not the latter.
Click to expand...
Click to collapse
That's strange. Could you run AnTuTu/Geekbench/Vellamo benchmarks a few times and post your average scores?
Maybe check your device info using CPU-Z to see if anything's changed?
Can you please post a picture of the back?
Rizzed said:
Upon receiving my phone and popping off the back cover, there is actually a "hole" next to the SIM slot 2, which could be easily identified with a yellow taping around it. With the vague image of my previous ZenFone 2 Laser, as well as with the aid of images online, I am sure that this is definitely a new revision for that particulator motherboard, or so to say, a revised version. One thing I noticed is the dramatic improvement in battery life. Using the exact same a
I am not sure if this is really because of the, so to speak, "updated" version of the motherboard, or simply a placebo effect, but hopefully it's not the latter.
Click to expand...
Click to collapse
Alright! I will post a picture of the back, as well as the benchmark scores when I get back.
Hardbriked like realy dropping it on the floor
Rizzed said:
Alright! I will post a picture of the back, as well as the benchmark scores when I get back.
Click to expand...
Click to collapse
I scrolled briefly through your posts and didn't see which model you have 550 or 551?
Also, what was the verdict on the possible new mainboard? What did CPU-Z report?
Please create a new topic, since this is not related to "hard bricked".
DELETED
rajlko said:
I think I was first who hard brick my ze550kl, after doing one week research, I surrender it to my local asus service center.
I got my device repaired in 5 days.
we do not have necessary files of ze550kl.
Click to expand...
Click to collapse
how much did it cost ? as my phone too is hard bricked and i see no solution! thanks in advance!!
het21 said:
how much did it cost ? as my phone too is hard bricked and i see no solution! thanks in advance!!
Click to expand...
Click to collapse
we have solution
addy692 said:
we have solution
Click to expand...
Click to collapse
actually i own ze551ml .. its completely hardbricked.. i went through the entire process of xfstk, isoc usb and other drivers and methods. So in xfstk is succesfully mounted (os + fw ) on the device. post that you get a 4 colored screen and then you boot into bootloader normally. in mine however the phone is stuck at the 4 colored screen forever. i have redone the entire process like 90 times but same , i have eeven tried other solutions but nothing worked. thats why i asked whether the service center guys replace the motherboard or actually unbrick it and how much they charge? thanks for the reply!
het21 said:
actually i own ze551ml .. its completely hardbricked.. i went through the entire process of xfstk, isoc usb and other drivers and methods. So in xfstk is succesfully mounted (os + fw ) on the device. post that you get a 4 colored screen and then you boot into bootloader normally. in mine however the phone is stuck at the 4 colored screen forever. i have redone the entire process like 90 times but same , i have eeven tried other solutions but nothing worked. thats why i asked whether the service center guys replace the motherboard or actually unbrick it and how much they charge? thanks for the reply!
Click to expand...
Click to collapse
they will unbrick it
And i cant guide coz i have qualcomm model
U should ask for help in ur device forum
addy692 said:
they will unbrick it
And i cant guide coz i have qualcomm model
U should ask for help in ur device forum
Click to expand...
Click to collapse
cool! they unbrick it! oh i tried asking in those forums but no result! thanks again!
Related
I have two Galaxy S gt-i9000m both with Bell and I live in Newfoundland which is the 850mhz radio as well.
One phone became bricked few months ago when I started getting random reboots I changed rom, it converted fs from rfs to ext4 and recovery gave some screens to go through but at this time I was only new, I messed up and my internal sd started causing issues. It was when gingerbread first arrived
I used odin to flash a number of firmwares, but now I feel I was not doing odin correctly, regarding bootloader and partitioning, anyway what ended up making the actual "BRICK" was when I flashed a vibrant rom and rebooted, now its a perm black screen.
If I have a fully charged battery and leave in, it dies overnight, If i plug usb in, the motherboard heats up very noticably, but no sound, no connection through device manage, nothing at all, no matter what tricks or buttons I try.
So not I have another identical phone that works perfectly. I have been researching if there was a way using my good phone to flash a chip, or solder something together could I fix it but I could not find any relevant info.
So I am left with the jtag/riffbox.
Can someone do this service for me, I dont want to actually buy one just to use it once, or can someone help me fix my bricked galaxy s, I will pay you for info that helps as well as put videos up, etc.
Please I have been last 4 months trying when I have free time, someone that knows how to help me, please do!!!
Thanks,
Dave Husk
709.764.7890
**EDIT**
I would love to work with someone, I attached pictures of my phone's internal parts including chip shots, and i also took a picture of my sim card writer, which is a serial to usb device and I'm sure somehow I can solder together to make a device to help unbrick our SGS's, I am even willing to send free of charge to the next person in need, and pay for shipping to continue the good will as every bricked SGS owner deserves HELP!
**EDIT 2**
I also already have a Download mode jig, the 301k resistor here as well
Does the download jig do anything?
If not your into specialized territory with the jtag stuff. I would add to an existing thread on that and hope someone is still watching it.
G
There are jtag shops in TO that can do it (on xda somewhere) and you could likely ship it to them and get the service.
Edit: [SOLVED]
Hi!
Yersterday I became an owner of a Note 3 (snapdragon variant). The problem is, when the system boots and is ready to use, the apps are just closing with an error message then the whole system collapses and then restarts. I think it's a ram problem. Or I don't know exactly but when i installed Lollipop it collapsed after 5 seconds, then i downgraded to KitKat, it was ok for 30 seconds and the last fw i installed was Cyanogenmod 12.1. It seems ok with CM but i can only use 1 app without crashing (for example i can't use FB Messenger with Internet Browser at the same time because one of them will crash...) So my theory is the following: The problem is not with the software but with the hardware, and i'm thinking of reflowing the chip (ram) with a heat gun. Any tips which i could try before reflowing? Or any tips on how to reflow properly with the smallest chance to make it a brick?
Any help would be appreciated!
Thank you!
Edem
Use Odin and flash a latest stock firmware. Do all wipes including data/cache/internal storage... If this not help, it would be a hardware issue.
newintage said:
Use Odin and flash a latest stock firmware. Do all wipes including data/cache/internal storage... If this not help, it would be a hardware issue.
Click to expand...
Click to collapse
Tried it again, but no luck... Is it possible that there is a code stuck in the ram which is causing all the problems? Sould i try debricking it with a pit file? Or it's useless even if I try? I'm really thinkig of reflowing it. Maybe the soldering let loose in one of the chips. But i couldn't even find a picture of which is the ram or the cpu or gpu on the pcb.
Any tips on how to reflow it? I mean temperature, time, and how to protect the other parts which I don't want to heat up.
Thanks in advance!
Edem
edemcrespo said:
Tried it again, but no luck... Is it possible that there is a code stuck in the ram which is causing all the problems? Sould i try debricking it with a pit file? Or it's useless even if I try? I'm really thinkig of reflowing it. Maybe the soldering let loose in one of the chips. But i couldn't even find a picture of which is the ram or the cpu or gpu on the pcb.
Any tips on how to reflow it? I mean temperature, time, and how to protect the other parts which I don't want to heat up.
Thanks in advance!
Edem
Click to expand...
Click to collapse
I don't think that there iz a code for something, firmware flashing overwrite all stuff kernel, system, modem already. Before going for hardware, try everything with software. Maybe pit file can help as it play with storages..
No luck...
Im 99% sure that this is a Hardware problem. Will try to reflow the ram on friday. I'll keep the post updated if I succeed or if not.
Thanks for the help! Wish me luck
Edem
Edit: I uploaded a video:
/watch?v=nlyuAQMFiK4
It behaves like this.
Ok tried to reflow it on 220°c for about a minute, but i don't know the exact melting temperature of the solder. It's the same, except it doesn't show the error messages (... closed). It's stable on KitKat for about 2 minutes, but when i open 2 or more apps the system just collapses. The solder may not melted enough or i don't know. Tomorrow i'll try to reflow it on 300°C (I don't care anymore if it'll be brick, I can't use it anyways...). So if you have any ideas on how to make it work, or you had the same problem before and solved it, I'm all ears Please guys! I need your help!
Cheers! :highfive:
Are you seriously reflowing a phone? It works on Graphic cards because the PCB and solders are big enough to give it a try, but you will just kill your phone like this (Solders on a phone's PCB are micro, you can't reflow them).
Try a PIT like you were saying before, if it doesn't work there's nothing much you can do beside sending it in RMA.
Pls keep us updated , I'm having same issue
samsumo said:
Pls keep us updated , I'm having same issue
Click to expand...
Click to collapse
Gave it in for repair to a store 2 weeks ago. Hopefully i'll get it back in a week or two, then if they describe the problem I can tell you what it was. It is a very difficult problem i think....
It's working now guys!
They repaired it in Poland for 40€. Changed the Snapdragon 800 to a new one and it's like a new phone now. Knox counter reseted to 0x0, and it's sim is unlocked now (they do just the sim unlocking in Hungary for 40€, so i'm very happy and surprised now ). Thanks for reading and replying to my post! If you have the same issue, just give it in for repair, because there is not much you can do at home...
Bye: Edem.
Hello everyone,
I've been experience a very ugly issue with my S7 Edge.
SCENARIO 1: When the sensor works (meaning when I can see in the screen what the camera "sees") and I try to take a picture, the camera throws an error message saying "Unknown error occurred", and then the phone reboots:
SCENARIO 2: In other occasions, the camera starts with a complete black screen and immediately throws this error:
One of the two scenarios above always happen, which basically means I'm never able to take a picture.
What I've tried so far:
1) Upgrade from Marshmallow to Nougat.
2) Reset settings.
3) Full phone reset (cache + data).
4) Phone reset from recovery mode (cache + data).
5) The issue are present in safe mode as well.
6) I tried downloading other camera apps. Errors again.
7) Tried changing the storage location from SD to Device. Didn't work.
8) Video recording works!!!!!
Is it a hardware problem in your opinion? How can a software issue still stay after a hard reset? I'm not sure because in SCENARIO 1 I can see that the sensor works, plus video recording works!
Any help is greatly appreciated!
FIXED by using ODIN and flashing Nougat with the CSC file
Maybe try flashing full stock rom through odin or smart switch since there might be a problem to the system files itself.
In my opinion though, this seem like a hardware problem.
Sent from my SM-G935F using Tapatalk
The problem re-appeared.
I also think it's a hardware problem. I'm just gonna send it back to Samsung.
IssamGS2 said:
The problem re-appeared.
I also think it's a hardware problem. I'm just gonna send it back to Samsung.
Click to expand...
Click to collapse
I've been having the exact same issue for months now. On 6.0, 6.0.1 and 7.0 as well.
Please let me know what Samsung tells you. The problem for me is that I bought the phone from amazon (8 months ago) and live in Argentina.
One thing I can't understand is that camera worked fine for the first couple of months. Also find really strange the fact that I'm able to take pictures with flash ON. Have you tried it?
ignaciogh said:
I've been having the exact same issue for months now. On 6.0, 6.0.1 and 7.0 as well.
Please let me know what Samsung tells you. The problem for me is that I bought the phone from amazon (8 months ago) and live in Argentina.
One thing I can't understand is that camera worked fine for the first couple of months. Also find really strange the fact that I'm able to take pictures with flash ON. Have you tried it?
Click to expand...
Click to collapse
I tried some days ago with the flash ON, and it didn't work (if I remember correctly). I didn't waste too much time, and as soon as I found out about the issue I sent it to Samsung for repair.
I have it back since today afternoon, and what I read from the attached papers is that there was a malfunctioning piece which they replaced. The list of operations Samsung did is:
- Boardswaping
- Software update (I doubt about this one as my phone was already updated)
I really think you should contact Samsung directly, and not Amazon. Here in Europe they have a good repair program: after max. 3 business days you get your phone back (and they will do the pick-up, and delivery). Maybe it's the same in Argentina.
Good luck!
IssamGS2 said:
I tried some days ago with the flash ON, and it didn't work (if I remember correctly). I didn't waste too much time, and as soon as I found out about the issue I sent it to Samsung for repair.
I have it back since today afternoon, and what I read from the attached papers is that there was a malfunctioning piece which they replaced. The list of operations Samsung did is:
- Boardswaping
- Software update (I doubt about this one as my phone was already updated)
I really think you should contact Samsung directly, and not Amazon. Here in Europe they have a good repair program: after max. 3 business days you get your phone back (and they will do the pick-up, and delivery). Maybe it's the same in Argentina.
Good luck!
Click to expand...
Click to collapse
Thanks for the info!
Do you know which board did they swap? The main board? :S
Argentina doens't handle international devices. I'd have to take the phone to de US .
I'll try to get it repaired here anyways.
Thanks again por the info.
ignaciogh said:
Thanks for the info!
Do you know which board did they swap? The main board? :S
Argentina doens't handle international devices. I'd have to take the phone to de US .
I'll try to get it repaired here anyways.
Thanks again por the info.
Click to expand...
Click to collapse
I'm sorry, I don't have that info. They did not specify.
So. I have used the unbrick tool several times before because sometimes I want to go back to out of the box factory. Locked bootloader, the whole nine. Well, it failed, so I unplugged it to try again, and no matter what I do, I can't get my computer to recognize that it's connected to the computer. I've been trying the holding volume up while plugging it in while in test mode. Like I said, I've used it before. I made sure I had plenty of battery life before I tried it, so I know the battery isn't dead. Do I need to look into getting another phone, or has anyone had a phone brick this badly and know how to fix it.
Just to rule out the obvious, have you tried different cable and computer?
gabriwinter said:
Just to rule out the obvious, have you tried different cable and computer?
Click to expand...
Click to collapse
Yeah. I've tried both of my laptops. Works perfectly on both for my s8+, but won't register my OP5 at all. I plug it in and nothing even shows up in device manager on both laptops.
godraistlin said:
Yeah. I've tried both of my laptops. Works perfectly on both for my s8+, but won't register my OP5 at all. I plug it in and nothing even shows up in device manager on both laptops.
Click to expand...
Click to collapse
I'm not very familiar with windows, you could try booting a Ubuntu livecd and typing in a terminal: dmesg
Then plug in the phone.
see if you can find any reference to the device being connected within the kernel messages.
How did you brick your OP in the first place? Does it still charge?
Z-Blade said:
How did you brick your OP in the first place? Does it still charge?
Click to expand...
Click to collapse
It bricked in the middle of using the unbrick tool. It literally doesn't do anything. No charging, no vibrations. Nothing.
gabriwinter said:
I'm not very familiar with windows, you could try booting a Ubuntu livecd and typing in a terminal: dmesg
Then plug in the phone.
see if you can find any reference to the device being connected within the kernel messages.
Click to expand...
Click to collapse
device descriptor read/64, error -32
That's the error I got. Problems with USB communication.
The fact it does not even charge sounds like a hardware issue. Even when its bricked it should at least charge.
godraistlin said:
device descriptor read/64, error -32
That's the error I got. Problems with USB communication.
Click to expand...
Click to collapse
This is an EPIPE error, this means the device is not answering the USB protocol requests and the pipe is broken.
In my experience this has always been due to a faulty cable, but in your case I'm afraid the device is juts not behaving as it should.
Next step would be to troubleshoot the hardware; This is not my area but maybe someone experienced can help out indicating what should be the next steps.
It may be that some small hardware parts could be replaced or the damage could be more severe.
Did you power down the phone then hold the power and volume down buttons at the same time to try and boot directly into recovery? If you can boot into recovery and have TWRP you could format the data on your phone using TWRP. That would erase everything on your phone except TWRP. Your computer would recognize your phone as an external hard drive and you could copy and paste a full ROM zip onto the phone memory and flash it with TWRP. If the tool you used installed the stock recovery I'm not sure what your options are but being able to boot into recovery would be a sign that your phone isn't actually hard bricked. Using automated tools to flash your phone is a really bad idea. It is much safer to flash manually.
I think there is close to zero chance that you have a hardware issue based on what you described. I've never heard of anyone hard bricking an OP5 so I think your phone is recoverable. If you can't figure it out a competent phone repair shop should be able to get you up and running again.
There's also One Plus tech support but if you try to get help from them I would probably just tell them your phone got borked after an update. If you tell them the entire circumstance they probably won't even try to help you.
Good luck.
Did you try holding power button for >40 seconds?
godraistlin said:
So. I have used the unbrick tool several times before because sometimes I want to go back to out of the box factory. Locked bootloader, the whole nine. Well, it failed, so I unplugged it to try again, and no matter what I do, I can't get my computer to recognize that it's connected to the computer. I've been trying the holding volume up while plugging it in while in test mode. Like I said, I've used it before. I made sure I had plenty of battery life before I tried it, so I know the battery isn't dead. Do I need to look into getting another phone, or has anyone had a phone brick this badly and know how to fix it.
Click to expand...
Click to collapse
If it's totalled then one plus will have no idea what is wrong either, send it back mate.
After reviewing all the replies, which won't work for you.
Way back in 2016, I faced the same issue with my op3. My issue was fixed by one of my friend by detaching the battery and reinstall the battery so that the board can boot. If that doesn't work for you, then suggest you to please check the type c connector funtionality.
dladz said:
If it's totalled then one plus will have no idea what is wrong either, send it back mate.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.
GAMIT PRUTHVI said:
After reviewing all the replies, which won't work for you.
Way back in 2016, I faced the same issue with my op3. My issue was fixed by one of my friend by detaching the battery and reinstall the battery so that the board can boot. If that doesn't work for you, then suggest you to please check the type c connector funtionality.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.
gabriwinter said:
This is an EPIPE error, this means the device is not answering the USB protocol requests and the pipe is broken.
In my experience this has always been due to a faulty cable, but in your case I'm afraid the device is juts not behaving as it should.
Next step would be to troubleshoot the hardware; This is not my area but maybe someone experienced can help out indicating what should be the next steps.
It may be that some small hardware parts could be replaced or the damage could be more severe.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.
jhs39 said:
Did you power down the phone then hold the power and volume down buttons at the same time to try and boot directly into recovery? If you can boot into recovery and have TWRP you could format the data on your phone using TWRP. That would erase everything on your phone except TWRP. Your computer would recognize your phone as an external hard drive and you could copy and paste a full ROM zip onto the phone memory and flash it with TWRP. If the tool you used installed the stock recovery I'm not sure what your options are but being able to boot into recovery would be a sign that your phone isn't actually hard bricked. Using automated tools to flash your phone is a really bad idea. It is much safer to flash manually.
I think there is close to zero chance that you have a hardware issue based on what you described. I've never heard of anyone hard bricking an OP5 so I think your phone is recoverable. If you can't figure it out a competent phone repair shop should be able to get you up and running again.
There's also One Plus tech support but if you try to get help from them I would probably just tell them your phone got borked after an update. If you tell them the entire circumstance they probably won't even try to help you.
Good luck.
Click to expand...
Click to collapse
I sent it back. They said the main board needed to be replaced. They fixed it under warranty. Just picked the phone back up today.
so, this phone died for me in 2017, and have been in a drawer since then. then i thought why not ask. so long story short if i remember correctly: bought it new. i rooted it since all the cool kids do that. then i did some update i think. and then in the winter of 2017 in beginning it just started behaving weirdly for me and then it turned off and all kinds of shenanigans. cant restart using different methods, sometimes it blinks, sometimes that bios menu comes up. blabla. so i tried to send it to the local repairshop that the seller used. but since i had it rooted they refused to fix it. so now i have a phone that costed 600 euro + 70 euro in service cost and it doesnt work. and then its been in a drawer since then.
i took it out, had it and the battery in a freezer for a while like some has said on internet didnt work.
anyway. does anyone here know any tips? if i want to flash the room can that be possible? or is this a lost cause? was this a common problem with note 4? i loved it and it crushed my heart when it stopped working. i still have a few months of pics etc on it from back then that ive never been able to get out. i attached it to the computer now and the computer makes a sound but nothing more.
any tips?
darknessviking said:
so, this phone died for me in 2017, and have been in a drawer since then. then i thought why not ask. so long story short if i remember correctly: bought it new. i rooted it since all the cool kids do that. then i did some update i think. and then in the winter of 2017 in beginning it just started behaving weirdly for me and then it turned off and all kinds of shenanigans. cant restart using different methods, sometimes it blinks, sometimes that bios menu comes up. blabla. so i tried to send it to the local repairshop that the seller used. but since i had it rooted they refused to fix it. so now i have a phone that costed 600 euro + 70 euro in service cost and it doesnt work. and then its been in a drawer since then.
i took it out, had it and the battery in a freezer for a while like some has said on internet didnt work.
anyway. does anyone here know any tips? if i want to flash the room can that be possible? or is this a lost cause? was this a common problem with note 4? i loved it and it crushed my heart when it stopped working. i still have a few months of pics etc on it from back then that ive never been able to get out. i attached it to the computer now and the computer makes a sound but nothing more.
any tips?
Click to expand...
Click to collapse
Sounds to me like either dead emmc or misconnection.
If it's just? misconnection there are tips (increasing the pressure by cardboard).
Can you access download mode?
Sometimes it shows there "dead emmc".
I somewhere read about a testing app.
Gotta search.
Where in Europe are you?
In the German Android-hilfe forum there is a member who fixes that.
Either exchanging the emmc or resoldering it.
If the chip is dead probably the data are lost.
afaik flashing the stock ROM deletes data.
It's a known problem, yes.
bmwdroid said:
Sounds to me like either dead emmc or misconnection.
If it's just? misconnection there are tips (increasing the pressure by cardboard).
Can you access download mode?
Sometimes it shows there "dead emmc".
I somewhere read about a testing app.
Gotta search.
Where in Europe are you?
In the German Android-hilfe forum there is a member who fixes that.
Either exchanging the emmc or resoldering it.
If the chip is dead probably the data are lost.
afaik flashing the stock ROM deletes data.
It's a known problem, yes.
Click to expand...
Click to collapse
Excellent feedback and assessment @bmwdroid . Thank you for sharing.
I only wish to add that there is a way to flash Samsung firmware while keeping user data. Of course, this method wouldn't be effective when it comes to emmc hardware failure so Im posting it for general information purposes only.
If you have downloaded the firmware for your Samsung Galaxy device you’ll find 2 CSC binaries with *.tar.md5*extension (namely CSC and Home_CSC ) inside along with BL, AP, and CP.*CSC*and*HOME_CSC*are necessary for different purposes, and you have to choose one or the other depending on your goal.
CSC –*If you flash the CSC file, it’ll perform a*factory reset*of your Galaxy device and wipe all data while installing a new firmware to bring your device to the same*state as it was when you purchased it. Go with CSC if you want a*clean installation.
HOME_CSC*–* On the other hand, if you want to*keep your Samsung phone’s data and settings*even flashing the stock firmware, you can select the HOME_CSC file.