Database Develop

Samsung Note Warranty from a different country

Hi, I'm in the US currently with a Samsung Note GT-N7000 that I purchased from Amazon (the phone imei showed that it is from the UK). After about 8 months of use without using custom roms, it seems to have hardbricked through normal usage (At the time of bricking I believe I was deleting some photos in a program called QuickPix when it froze and eventually had to be manually turned off. Then it would struggle booting on the Samsung logo and after a retry, it just would not boot anymore). It is completely unresponsive when you press any of the buttons and won't get recognized when hooked up to the computer. I even tried using new batteries but that did not work. I don't think the Jig will work in my case either.
I called Samsung US and they told me that the phone would have to be covered in the country where the phone was originally manufactured for which is the UK in my case. I was wondering if anyone else have been in my situation where you are in a different country with a phone that needed repairs. Samsung UK requires that you have an address in the UK so it makes it difficult for me to file a claim. Has anyone been able to get Samsung US to take your non-US claim or have found a way to file a claim without a UK address?
Thank you so much.

chumpburger said:
Hi, I'm in the US currently with a Samsung Note GT-N7000 that I purchased from Amazon (the phone imei showed that it is from the UK). After about 8 months of use without using custom roms, it seems to have hardbricked through normal usage (At the time of bricking I believe I was deleting some photos in a program called QuickPix when it froze and eventually had to be manually turned off. Then it would struggle booting on the Samsung logo and after a retry, it just would not boot anymore). It is completely unresponsive when you press any of the buttons and won't get recognized when hooked up to the computer. I even tried using new batteries but that did not work. I don't think the Jig will work in my case either.
I called Samsung US and they told me that the phone would have to be covered in the country where the phone was originally manufactured for which is the UK in my case. I was wondering if anyone else have been in my situation where you are in a different country with a phone that needed repairs. Samsung UK requires that you have an address in the UK so it makes it difficult for me to file a claim. Has anyone been able to get Samsung US to take your non-US claim or have found a way to file a claim without a UK address?
Thank you so much.
Click to expand...
Click to collapse
Excuse me, but doesn't Amazon have the obligation to be the liaison between Samsung and you? I mean, they are no different than if you had bought it from BestBuy. You should be able to contact Amazon, and tell them that your phone broke and you'd like to have it repaired under warranty. I live here in Spain, and I bought something from Amazon Spain but it was imported from the UK. I sent it back and Amazon paid for it to be sent back and everything.
I'd try contacting Amazon, and tell them the same situation. Tell them that you got the phone through them and then it broke, and you went directly to Samsung and they said that they won't honor the warranty as it was imported from Europe. Amazon has an obligation to offer the warranty. Not to mention, Amazon is probably one of the best companies I've ever worked with. Fast responses, fast shipments and awesome service in general.
Give them a try.
Hope I've helped.

First of all was the phone all the time on stock roms ? If yes then please contact or wait to get contacted by entropy512 if the phone is died du to emmc bug. Just hold a few hours I guess
Sent from my GT-N7000 using Tapatalk 2

Braxos said:
First of all was the phone all the time on stock roms ? If yes then please contact or wait to get contacted by entropy512 if the phone is died du to emmc bug. Just hold a few hours I guess
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
I'd need a lot more details, but:
What exact firmware was it on? What build?
As much as I would like for this to be an example of an eMMC brick on stock, the fact that it occurred when deleting files means that unless Samsung has enabled the "discard" mount option for storage in a new build I am unaware of, it's something else like a bad solder joint.

Entropy512 said:
I'd need a lot more details, but:
What exact firmware was it on? What build?
As much as I would like for this to be an example of an eMMC brick on stock, the fact that it occurred when deleting files means that unless Samsung has enabled the "discard" mount option for storage in a new build I am unaware of, it's something else like a bad solder joint.
Click to expand...
Click to collapse
I had the phone up to date through the samsung / settings / update so whatever the last ICS update was unless there has been a new update within the past 5 days. The last major update, I remember it installed some German apps, latest version of Kies, and made the Note a lot smoother. As I mentioned before, the phone did try to reboot to the samsung logo after it froze but it never was able to boot all the way. I should have stopped at that point but I tried to reboot a couple times and that is when it became unresponsive.

Motherboard swap?

Hey folks, longtime lurker, first time poster. I want to say a quick thanks to everyone here for all the work you folks do, and all of the super informative posts here that have helped me throughout the years.
My question is this, I just recently got an AT&T Note 3 from a friend, and wanted to flash CM to it, but I soon learned that the bootloader is locked and this would not be possible for me. I know development for this (now 3ish year old) phone is probably long dead, but I hope somebody will stumble upon my post, and be kind enough to help me with an idea I'm working out in my head. I have a friend who has a tmobile note 3 that has a busted screen, and was wondering, if I either a) swap my screen into it, or b) swap the tmobile motherboard into my phone, would I be able to then flash Cyanogenmod, considering that I would have the tmobile motherboard in my phone, or just the working t mobile version in general? In theory, I would assume even the motherboard swap would work, though it would be annoying to have to do it.
What do you think, can I do this, should I attempt to?

Yes, the T-Mobile board should fit on the n900a.
The n900t does not have a locked bootloader so cm can be used.

Thanks for the reply, I may just give that a try then. Best case scenario, it'll be successful, and I'll have CM 13 on my device... worst case, I fail, and end up needing to replace the phone (which I should probably do eventually anyhow) this should be fun.

warlikewings said:
Thanks for the reply, I may just give that a try then. Best case scenario, it'll be successful, and I'll have CM 13 on my device... worst case, I fail, and end up needing to replace the phone (which I should probably do eventually anyhow) this should be fun.
Click to expand...
Click to collapse
It would be much easier for you to replace the cracked screen on your buddy's phone than replacing your motherboard with his.

Was sold a retail mode Huawei P9 and I want to swap to stock ROM [UK]

Back story:
I bought a Huawei P9 from cash converters online, everything worked fine except the battery wouldn't go past 72%. I spoke to Huawei via their live chat who sent me a baggy to send it off to "Sbe" under warranty. Sbe then sent me a letter saying it's not in warranty because it's in Carphone Warehouse retail demo mode. I had to pay Sbe £15 in order to get my phone back and hopefully it'll arrive tomorrow. I went to Carphone Warehouse and gave them all the phone's information and they said it isn't blacklisted, but that they couldn't "fix" it for me either.
I love the phone, I really do...and I don't want to send it off again for a refund, I've been reading up on it and there's been stuff about bootloaders and rooting, I have no idea what any of this stuff is...but the Dload flashing method seems like something I could manage without much hassle.
Actual question:
The phone is an EVA-L09, I just want to know which ROM I should use, I've downloaded "P9 EVA-L09 B136" based on a similar post but it's a year old and so might not be right.
I'm sorry that I'm a noob about this stuff and things might be wrong, but I need help and this seems like the place to get it.
Thank you, Thorpy
P.S If someone does reply with a link to the correct rom to use, would I need to format the micro SD?

Thorpy4p said:
tl;dr
Click to expand...
Click to collapse
When you get the phone back, look in Settings -> About Phone and see what build number you have there. This will give you a clue as to which ROM you should flash.
Also, try enabling Developer Options and looking for Demo mode - could be something as simple as toggling this on/off?
Peace...

chris5s said:
Click to expand...
Click to collapse
Well the phone finally arrived back after so long , It's apparently a special "ex-display" firmware or something like that.
Build number: EVA-L09C652B118

Here?
Peace.

chris5s said:
Here?
Peace.
Click to expand...
Click to collapse
That was the one I had downloaded originally, but it was nice to have the validation that it was the right one, worked perfect!
Cheers Chris, It feels like the end of an era with all the **** this phone put me through, thank you!

I have the same problem. Someone can tell me exactly what to do.

N920F that might be either a N920G or P

So, some background first. I bought a Note 5 from ebay about a week ago, in hindsight that was my first mistake but what's done is done. It turned out to be from China which worried me a little. On checking the version, it was claiming to be a N920F. Having not done my background reading first (second mistake) I hadn't realised that I'd not be finding a legit copy of firmware anywhere but I went ahead and went to root it anyway. Had an absolute mare of a time, got caught in a bootloop for awhile and struggled to find any coherent/non-contradicting information on what roms would and wouldn't work but never the less somehow managed to get it to play nicely (ish). While running, I looked into the device info and it was claiming to be a N920P in the recovery/download screen but in the phone itself from device info claiming to be N920F. Fast forward to today and it decided to have frozen and become unresponsive so I thought no bother, I'll reflash it. This is where the house of cards start crashing down.
Now, it is (seemingly)perma stuck in a bootloop and won't accept the N920P rom's associated with the code claimed in the recovery screen etc and not found any N920F roms. I'm assuming it's soft bricked at this stage, I read in another post to check the IMEI to see what it came up as and this is where things get even more confusing. On checking, it came back as being an N920G.
So. As it stands, no rom I've tried works and I've got an expensive paperweight. Seller has yet to reply to me, so I'll give them another day before I raise a case with Ebay... while this is going, has anyone else got any suggestions that I could try or information I can provide that might help? (Other than yeh, I dropped a bollock!)

theredtom said:
So, some background first. I bought a Note 5 from ebay about a week ago, in hindsight that was my first mistake but what's done is done. It turned out to be from China which worried me a little. On checking the version, it was claiming to be a N920F. Having not done my background reading first (second mistake) I hadn't realised that I'd not be finding a legit copy of firmware anywhere but I went ahead and went to root it anyway. Had an absolute mare of a time, got caught in a bootloop for awhile and struggled to find any coherent/non-contradicting information on what roms would and wouldn't work but never the less somehow managed to get it to play nicely (ish). While running, I looked into the device info and it was claiming to be a N920P in the recovery/download screen but in the phone itself from device info claiming to be N920F. Fast forward to today and it decided to have frozen and become unresponsive so I thought no bother, I'll reflash it. This is where the house of cards start crashing down.
Now, it is (seemingly)perma stuck in a bootloop and won't accept the N920P rom's associated with the code claimed in the recovery screen etc and not found any N920F roms. I'm assuming it's soft bricked at this stage, I read in another post to check the IMEI to see what it came up as and this is where things get even more confusing. On checking, it came back as being an N920G.
So. As it stands, no rom I've tried works and I've got an expensive paperweight. Seller has yet to reply to me, so I'll give them another day before I raise a case with Ebay... while this is going, has anyone else got any suggestions that I could try or information I can provide that might help? (Other than yeh, I dropped a bollock!)
Click to expand...
Click to collapse
Woww! I have the same issue did you have any luck with it ?

Unfortunately no good news no. After several weeks the seller replied and said it was indeed an N920G from the US... BUT with some differences and that they had a specific ROM that they wouldn't give me to reflash with. So no, I didn't solve it and I was stuck with an expensive paperweight and neither Ebay or Paypal would help so I didn't even get my money back. expensive lesson!

Have you tried flashing stock roms for n920p and n920g through Odin? I managed to easily flash my n920f with stock n920p N920PVPS3BPJ2 (it had N920FVPS3BPJ2 rom initially so I assumed it was just modified version).

Yes, I tried them both with no luck. I've since given up on it though. OnePlus 5 has been a much nicer phone to use

Question Zenfone 8 suddenly died - no sign of life - Asus EU support not covering because of an unlocked bootloader

Hi,
A week ago I was using my < 4 months old Zenfone 8 while traveling in Germany, and at 19% battery the screen turned black. I went back home, tried charging it for as long as possible, it was staying cold and never showed any sign of life.
So I opened a RMA on Asus Belgium website (as I am from Belgium), and shipped the phone to their repair center.
Today, I got an email from them, saying that the warranty wasn't covering the damage, and that I had to pay 500,28€ for a replacement of the motherboard.
When going into their OOW website, I saw this table :
Warranty start:2021-05-16Warranty end:2023-05-15Issue date:2021-09-13Receive date:2021-09-15Charge reason:OOWCustomer agree to quotation:Charge reason:OOW - Out of warranty ASUS Product Unlock Flag-oow scratched
It seems to me that the "unlock flag" is their bootloader unlock tool, that I had indeed used to root the phone before, and wanted to try a few custom ROM - which I actually never did since there were none at the time. Of course, this is completely unrelated to the issue, as it is not even rooted anymore and I basically did nothing with it.
As I am from the EU, I saw that there are laws that protect consumers from these types of abusive behaviors from companies, as explained here https://piana.eu/root/
I am therefore
1) looking for people who had this problem with their Zenfone 8 (what is it actually? never seen a brand new phone die like this)
2) looking for people who had their warranty denied for an unlocked bootloader in the EU, and what is possible to do
Thank you very much for your attention and for your help

There loads of people that has the same bricked state:
ZenFone8 stuck on waiting for flashing full ramdump
As requested by the mod - opening new discussion for the issue. The Flashing Full Ramdump happened to me too - the phone was being charged over the night and the error was waiting when I woke up. I hope that at least your service will fix it quickly.
zentalk.asus.com
I had it on my 1st ZF8, complety dead. Sent it for repair but ASUS refunded it.
2nd one seems resistent to this bug, rooted, flashed all kinds of roms etc, ended in ramdump state but can always boot to fastboot.

NisseGurra said:
There loads of people that has the same bricked state:
ZenFone8 stuck on waiting for flashing full ramdump
As requested by the mod - opening new discussion for the issue. The Flashing Full Ramdump happened to me too - the phone was being charged over the night and the error was waiting when I woke up. I hope that at least your service will fix it quickly.
zentalk.asus.com
I had it on my 1st ZF8, complety dead. Sent it for repair but ASUS refunded it.
2nd one seems resistent to this bug, rooted, flashed all kinds of roms etc, ended in ramdump state but can always boot to fastboot.
Click to expand...
Click to collapse
I've seen that but I'm not sure it's the exact same state, as for me it didn't even display anything anymore. Also, did Asus refund you even with your bootloader unlocked?

flolaff said:
I've seen that but I'm not sure it's the exact same state, as for me it didn't even display anything anymore. Also, did Asus refund you even with your bootloader unlocked?
Click to expand...
Click to collapse
Yes, it was bootloader unlocked.
You can also check state when you plug it to computer, even with dark screen.
Check what the usb connection says in device manager

NisseGurra said:
Yes, it was bootloader unlocked.
You can also check state when you plug it to computer, even with dark screen.
Check what the usb connection says in device manager
Click to expand...
Click to collapse
Yeah I tried it back when I had the phone (since it’s now hostage at Asus) and nothing showed up in the device manager

So update: After a bit of back and forth emailing, I finally got an answer: « Im really sorry but our answer will not change. By using the unlock tool you have agreed that the warranty will be dropped, no matter what problem you are experiencing and regardless of how the problem arose. »
So basically they openly agree that they are scamming me of 500€ after selling me a faulty device, but thanks to an abusive clause, they think they can do it.
Great customer service, always a pleasure to give business to such a great company as Asus… I’ll get my lawyer involved now, anyone who has advices on the legal process in the EU is very welcome.

Seem to be some hardware fault with the 1st batch. Really bad customer response from asus, loads of reports of dying zf8's now

NisseGurra said:
Seem to be some hardware fault with the 1st batch. Really bad customer response from asus, loads of reports of dying zf8's now
Click to expand...
Click to collapse
What type of zenfone did you have?
I am wondering whether only 256GB phones have this issue

Blumi511 said:
What type of zenfone did you have?
I am wondering whether only 256GB phones have this issue
Click to expand...
Click to collapse
256GB that died, new 128GB is ok

NisseGurra said:
256GB that died, new 128GB is ok
Click to expand...
Click to collapse
I really hope my small 128 GB phone won't have this issue. I really like this phone...

There are reports on Zentalk forums of both 128 and 256 models dying
We are basically all held in suspense wondering if our phones will die or not. Personally, I have a second phone (Xperia z5 premium) that is fully set up and I can easily switch in case of problems, but it is still not a nice feeling

Possible battery failure. Inspect.

I dont think its battery fail, seems more likely that storage or RAM gets corrupt, the 1st state is
"waiting for flashing full ramdump". I have this state on my 2nd zf8 but can always reboot to fastboot. That was not the case on the first unit

blackhawk said:
Possible battery failure. Inspect.
Click to expand...
Click to collapse
Ramdump is a battery failure?

assasss said:
Ramdump is a battery failure?
Click to expand...
Click to collapse
If you already found the cause disregard...

blackhawk said:
If you already found the cause disregard...
Click to expand...
Click to collapse
I haven't found the cause. My phone is working normally.
However people on Zentalk forums which have sent their phones for repair have reported that the service report has information that motherboard was replaced. I can't confirm or deny this

Blumi511 said:
What type of zenfone did you have?
I am wondering whether only 256GB phones have this issue
Click to expand...
Click to collapse
Was the 128GB model for me, we still don’t know what the issue is.
If I can’t get the phone fixed the legal way I think I’ll pay the 60€ to get it back unrepaired (because yes, I have to pay for that) and open it myself to try and find the issue. Maybe I’ll be more competent than their lame service at identifying the issue

flolaff said:
Was the 128GB model for me, we still don’t know what the issue is.
If I can’t get the phone fixed the legal way I think I’ll pay the 60€ to get it back unrepaired (because yes, I have to pay for that) and open it myself to try and find the issue. Maybe I’ll be more competent than their lame service at identifying the issue
Click to expand...
Click to collapse
Oh man I feel sorry for you. In Germany, they'd have to prove it was not their fault in the first 6 month after buying

Blumi511 said:
Oh man I feel sorry for you. In Germany, they'd have to prove it was not their fault in the first 6 month after buying
Click to expand...
Click to collapse
I know, it’s the exact same law here in Belgium but they don’t care…

22 dead zf8 so far in the asus forum thread. #asusZF8DeadGate