Develop Bugs

[HELP] Samsung claims my i747 is water damaged. Never spilled even a drop on it.

I'll try to make a short story short. I bought an AT&T S3 full price, off contract, in the States if that matters. (I live in Canada.) Five months ago it bit the dust out of nowhere in a most peculiar way - it does not power on regularly with only the battery (I have tried a friend's working battery) nor charge with USB inserted, but does power into download mode when a 301K jig is inserted with only the battery, and it lets me fully flash an ODIN image. When ODIN autoreboots the device, it boots to the first boot logo (no animation or sound) and does not proceed. Pulling the battery gets us back to square one, device does not boot at all.
Let me be clear before I proceed: this phone has been babied, never come into contact with any water of any form, and never dropped. The liquid damage indicators are, of course, white as ghosts.
So what to do? Call Samsung and send in for repair. Their findings?
Code:
Original Problem:
INSTALLATION - POWER - WILL NOT POWER UP
Problem found:
CORROSION, LIQUID DAMAGE
Solution:
BER
BER means beyond economic repair, apparently. So, I call them back, insist they fix their damn products, speak with a manager
(who describes that the damage as corrosion to the menu/back key connector, she specifically described "14 vertical components and they look very rusted, yeah that looks damaged to me")
I insist they are wrong, the whole nine yards, etc, they clear the BER flag and let me send it in again.
...and they say it's liquid damaged AGAIN. Exact same story. Just now apparently it magically migrated to a new location. The tech stuck a red chevron on my board over the PM8921 IC, which would make sense if the device won't power on I suppose, but there's no corrosion to be found anywhere.
This is where I am right now. I'm pretty furious at Samsung and I cannot go to my carrier because I was an idiot and bought the device full price.
Here are pics of my device to prove what BS Samsung is trying to pull here. Sorry for bad quality, the Nexus 4 is horrible at macro focus.:
http://imgur.com/a/P5AEC
All looks good here (menu/back key connection):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Full board:
Closeup of chevron:
Even closer:
Does anybody know who I can complain to in order to actually get my phone fixed under warranty? It has warranty until December (which is useless by the looks of it) Small claims court? Better Business Bureau?
Any help is appreciated. Thanks in advance.

Update: Called Samsung again today (got to Tier 1 right away), and after politely asking to speak with Tier 2 (and being put on hold for nearly a half hour...), I asked to speak with Executive Customer Support. This was the department I ended up with last time that was actually able to resolve issues instead of repeating themselves over and over. I was informed that they are only in on weekdays.
Looks like I'll be calling back on Monday...

Another update: Finally got through to Executive Customer Relations, who promised me a call back to go over the details of the case. I will be giving them links to these photos to compare what they claim versus what I see, so hopefully we get somewhere.

Was your phone used or new?

New, sealed.

[Repaired?] Bootlooped SN506 back from LG

Hello,
so my device died (bootloop) on 5th dec, got it back today after warranty.
I sent in a rooted 5.1 lollipop (bootloader locked) and got the same thing back with mm 6.0
IMEI same, serial number, same.
Repair report:
http://i.imgur.com/xwU33uZ.jpg
They claim to have changed the main pcb, wouldn't the IMEI have changed then?!
There's even a dedicated "IMEI Nr." and "IMEI Nr. New" field on the report...
Does anybody have a clue what they actually did? Did they replace the motherboard and put "my old" IMEI in there?
Is there any way to check what 'serial number' the new mainboard has had before? Sticker behind the battery still sais 506....

I sent back a Canadian G4 for repair 2 times. After the second repair I still had the same phone both times it was rooted on lollipop a d came back with marshmallow.. I have no idea what they do but whatever it was they didn't do it right the first time.

Jason123420 said:
I sent back a Canadian G4 for repair 2 times. After the second repair I still had the same phone both times it was rooted on lollipop a d came back with marshmallow.. I have no idea what they do but whatever it was they didn't do it right the first time.
Click to expand...
Click to collapse
Mhh, thanks for the info. I was hoping to get a new motherboard with a new serial number (610 is the newest i think?) since i haven't read much about bootlooping issues with those recent ones...
But then, they also could start bootlooping in a few months from now.. who knows.
I wanted to unlock the bootloader on my repaired device, but when the "repair" might just be temporarily and the phone is still vulnerable to this issue i wonder if thats a good idea.
But then, some ppl got their phones "repaired" with bootloader unlocked?! Meh. Decisions decicions.

This folder "zarządzanie" is in Polish language that means "management"

blake_spector said:
Mhh, thanks for the info. I was hoping to get a new motherboard with a new serial number (610 is the newest i think?) since i haven't read much about bootlooping issues with those recent ones...
But then, they also could start bootlooping in a few months from now.. who knows.
I wanted to unlock the bootloader on my repaired device, but when the "repair" might just be temporarily and the phone is still vulnerable to this issue i wonder if thats a good idea.
But then, some ppl got their phones "repaired" with bootloader unlocked?! Meh. Decisions decicions.
Click to expand...
Click to collapse
If they have replaced the whole motherboard your IMEI must have changed and you would have had new sticker behind the battery with new SNxxx. My guess is that they may have found cheaper way of repairing bootlooped LG G4 and instead of replacing the motherboard they might be just replacing the affected components or just re-soldering the old ones. Generally LG issued repair guidelines to their repair centers to keep the costs down and just to replace what is only a must to replace.

Azargardius said:
This folder "zarządzanie" is in Polish language that means "management"
Click to expand...
Click to collapse
Thanks, yeah it's just a folder with stock LG settings shortcuts...
Something else, on the repair status it sais the used replacement part (logic board) is "EBR81224301" - and i found it here in this online shop https://north.pl/karta/plyta-glowna-do-smartfona--ebr81224301-,1C9-XK-CL2S-X36.html
Since my repaired phone has the same IMEI and S/N as before, i have no idea what production date this replacement part has.
Maybe a kind soul with a S/N 6xx (609, 610) wants to dissassemble his phone and take a picture of what part-number their main logic board has?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That part. This one sais (?) EAX66400601 ... 1.0 ...

gedas5 said:
If they have replaced the whole motherboard your IMEI must have changed and you would have had new sticker behind the battery with new SNxxx. My guess is that they may have found cheaper way of repairing bootlooped LG G4 and instead of replacing the motherboard they might be just replacing the affected components or just re-soldering the old ones. Generally LG issued repair guidelines to their repair centers to keep the costs down and just to replace what is only a must to replace.
Click to expand...
Click to collapse
You're right, that's why im curious. As the repair report shows, changed main board, EBR81224301 replacement part.
Perhaps like this
But that doesn't fit the repair report either as the replacement part is seemingly the whole main circuit.

If you would like to raise that with LG I would suggest doing it. If they said they replaced the motherboard (which they didn't as you IMEI hasn't changed) then I would doubt if they did anything else apart from maybe re-soldering the components and that would make their repair report false. I would understand LG that they don't want to spend anymore money on this bootloop disaster with LG G4 but they have to ensure that they provide the best service to the customer which from my LG bootloop repair experience is a lot to be desired...

They do the same thing in the US too. When I sent my phone in for repair, it also came back with same IMEI, serial, and everything, but the repair report stated that they replaced the motherboard. Since all my data was gone and the phone is working fine again, I assume that's what they did. They probably have some tool to set the IMEI number back to the one of the original board's to make the whole process as smooth as possible.

Yep, same as me..report says they swap motherboard but when do the checking,everything is same.

Google Pixel 2 XL DVT Models

Hey, So I got my hands on some Google Pixel 2 XL devices (actually 8) which were shipped here on 29th of August 2017 (Pixel 2 XL released on first week of Oct 2017)These devices are up for auctions by the Customs department here and I'am thinking to buy them however I have some doubts regarding the DVT sticker and "Not for Sale" marking on back-panel. I have some pics from inspection. It would be really great if you could help me out in buying decision.
My main doubts are:
1. Can build no. be changed after a normal update ? (i guess yes, but still looking for a sure answer)
2. Will it be a good deal to get them at 40% of the present retail price ? (I mean will people would like to own a Pixel 2 XL @ 40 to 50% discounted rate, 'cause "Not for Sale" is mentioned on back-panel)
Looking forward that community members will help.

The "Not For Sale" item on the back is a red flag. It tells me these are engineering samples. The software in an engineering sample is rarely finished and of beta quality. Worse, the bootloader may be locked, something Verizon owners are all too familiar with. The engineering sample bootloader however isn't a Verizon device and ignores any and all attempts to unlock it.
Google may have changed its development practices and these could be something else, but I would be wary regardless.

Strephon Alkhalikoi said:
The "Not For Sale" item on the back is a red flag. It tells me these are engineering samples. The software in an engineering sample is rarely finished and of beta quality. Worse, the bootloader may be locked, something Verizon owners are all too familiar with. The engineering sample bootloader however isn't a Verizon device and ignores any and all attempts to unlock it.
Google may have changed its development practices and these could be something else, but I would be wary regardless.
Click to expand...
Click to collapse
Thanks for your reply . Initially I too had same doubts and after checking about word "DVT" I found it stands for "Design Validation Testing" and it's one step before Mass Production for consumers. And also noticing the date of shipment which is 29th Aug 2017 (almost 35 days before official launch) I don't think there would be any hardware differences.
however one thing I would really like to know is Build No. I mean can we change that through a normal update ?
Here are the links/images of back-panel
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and About me section in settings

Your image links are screwed up. Let's try that again.
Back Panel
About Me - Settings
Now, in answer to your question, probably not. The software here is a pre-release version of Android 8.0, as noted by the build number. From past experience with people who have come across these devices thinking they got a good deal, what usually happens is they attempt to update the device and it fails. Where these devices are intended for testing the software, Google locks down the device so that only testing images can be loaded. Unlocking the bootloader will not be possible, and Verizon owners know all about that, but this will be worse. The option to allow OEM Unlocking will most likely be grayed out.
Unless you don't care about unlocking the device and never seeing an update of any kind, this is not a good deal. Not when you can go to Swappa and purchase a production model that has potentially been used even less than these units.

https://drive.google.com/file/d/1G6G_YgwFOL0ktOSEw3G-wv33b5c6w7oZ/view?usp=drivesdk
https://drive.google.com/file/d/1h2ZdbqIyqtTpqFinYzRP1Lx29CYVK0cD/view?usp=drivesdkSo here are updated image links.
Build No. is taimen-userdebug 8.0.0 OPD1.170816.007

rasi_rana said:
Thanks for your reply . Initially I too had same doubts and after checking about word "DVT" I found it stands for "Design Validation Testing" and it's one step before Mass Production for consumers. And also noticing the date of shipment which is 29th Aug 2017 (almost 35 days before official launch) I don't think there would be any hardware differences.
however one thing I would really like to know is Build No. I mean can we change that through a normal update ?
Here are the links/images of back-panel
and About me section in settings
Click to expand...
Click to collapse
I do something similar for the Dept of Defense as far as testing weapons systems, software, etc. and if these units are indeed test validation units, they have been stressed in super heated, super cold, harsh environmental conditions, attempts to overcharge the battery, leave it plugged in during heavy use, overheating the CPUs, and a ton of other tests that validate it's consumer usability.
Basically, these units, if test validation pieces, have been abused both physically and software to represent the worst use the average consumer would put them through.
With some of our software testing, earlier versions are unable to be overwritten, or updated via conventional methods because it is still under testing. IF these units are similar, they might be stuck on whatever OS is currently on them.
If they are being sold AS IS, or you can verify they are actually TEST units, I'd put my money somewhere else.
Just my .02.
Good luck!
If it were me, I wouldn't risk ANY funding I wasn't willing to lose on these. With some

Az Biker said:
With some of our software testing, earlier versions are unable to be overwritten, or updated via conventional methods because it is still under testing. IF these units are similar, they might be stuck on whatever OS is currently on them.
If they are being sold AS IS, or you can verify they are actually TEST units, I'd put my money somewhere else.
Just my .02.
Good luck!
If it were me, I wouldn't risk ANY funding I wasn't willing to lose on these. With some
Click to expand...
Click to collapse
thanks for stopping by and putting forward your views.
How about investing 1/4th of the retail price on a single device ? and btw Build No. is "taimen-userdebug 8.0.0 OPD1.170816.007" (in case you could offer some more help)

rasi_rana said:
thanks for stopping by and putting forward your views.
How about investing 1/4th of the retail price on a single device ? and btw Build No. is "taimen-userdebug 8.0.0 OPD1.170816.007" (in case you could offer some more help)
Click to expand...
Click to collapse
If it were me, I would stop at Verification Test Device.
Only you can determine whether you're willing to risk how ever much 25% would total.
Especially if you don't know that you can sell these as upgradable, unlockable, or if they even have all the final release apps and features installed.
Since you asked, my advice is: walk away save your $ for another venture that has more reliable resale and profit tied to it. Way too many IFs and unknowns with these devices in my opinion.

(Official Support Answer) Rooting your Oneplus 8 Series DOES NOT VOID IT'S WARRANTY

Hi, I am an ex OP3 user who switched to a OP8P recently and I was going through all the forums related to OP 8 Series to find out if rooting this device will void my warranty or not (It didn't void the warranty of OP3 back in 2016 and I was curious if OP has changed their stance related to rooting).But there was no official or forum answer available for this query so I did the next best thing and I asked the official oneplus chat support.The answer was UNLOCKING YOUR BOOTLOADER or ROOTING YOUR ONEPLUS 8 SERIES DOES NOT VOID IT'S WARRANTY.
PS: Of course, if something happens to the phone hardware it will not be covered under warranty though.
PPS: I am from India, It may be different for your country
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

RounakCreationz said:
Hi, I am an ex OP3 user who switched to a OP8P recently and I was going through all the forums related to OP 8 Series to find out if rooting this device will void my warranty or not (It didn't void the warranty of OP3 back in 2016 and I was curious if OP has changed their stance related to rooting).But there was no official or forum answer available for this query so I did the next best thing and I asked the official oneplus chat support.The answer was UNLOCKING YOUR BOOTLOADER or ROOTING YOUR ONEPLUS 8 SERIES DOES NOT VOID IT'S WARRANTY.
PS: Of course, if something happens to the phone hardware it will not be covered under warranty though.
PPS: I am from India, It may be different for your country
Click to expand...
Click to collapse
I think they meant if something happens to device HW because of rooting (like overclocking etc.) It voids warranty. I have got my display replaced and then fingerprint sensor calibrated. Both times my device was rooted (didnt bother to remove it) and they didnt care about it in a service center. I am from Finland. Actually I didnt even need a receipt to get my device serviced..

pyry666 said:
I think they meant if something happens to device HW because of rooting (like overclocking etc.) It voids warranty. I have got my display replaced and then fingerprint sensor calibrated. Both times my device was rooted (didnt bother to remove it) and they didnt care about it in a service center. I am from Finland. Actually I didnt even need a receipt to get my device serviced..
Click to expand...
Click to collapse
Yes I know, I too have used warranty while being rooted multiple times when I was using OP3. That not including hardware is for things like frying up your motherboard by overclocking (as you said) or flashing some unstable kernel.

this is even published on OP web page
https://www.oneplus.com/si/support/shopping-help/details#85000005+GD00000034

RounakCreationz said:
Hi, I am an ex OP3 user who switched to a OP8P recently and I was going through all the forums related to OP 8 Series to find out if rooting this device will void my warranty or not (It didn't void the warranty of OP3 back in 2016 and I was curious if OP has changed their stance related to rooting).But there was no official or forum answer available for this query so I did the next best thing and I asked the official oneplus chat support.The answer was UNLOCKING YOUR BOOTLOADER or ROOTING YOUR ONEPLUS 8 SERIES DOES NOT VOID IT'S WARRANTY.
PS: Of course, if something happens to the phone hardware it will not be covered under warranty though.
PPS: I am from India, It may be different for your country
Click to expand...
Click to collapse
It's there is the OnePlus website it self, this post is not required

Have rooted many OnePlus devices and it's always been able to be RMA'd, it'll be the same.
Rooting isn't actually the issue, it's usually unlocking the bootloader, but OnePlus doesn't have the same stringent warnings as other OEM's.
Much to everyone who buys one plus devices fortune.
Personally I would relock the bootloader if I was to RMA a device, unless it was a brick in which case it doesn't matter.

Question Message "This Device is Managed" , what can i do?

Hello Dear community, i have two Phones , one Pixel 6 and one Pixel 6 Pro and when i try to setup the phone it show me the message " This device is managed" and you can see on the screenshot. Please how can i solve this issue? I bought the phones in second hand by Ebay.
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If the phone is showing that message and was purchased off of eBay, then the phone was stolen from a business. The phone cannot be utilized as it will be flagged and will have its IMEI blacklisted after some time. That message you are seeing confirms that.
Unfortunately for you, there is no work around to resolve this - as theft isn't a 'real' phone problem. The protection with phone management is just a corporate move to give companies more control over the devices that they purchase. So essentially, there is a much lower chance of them being stolen. Because once they are stolen, they're basically just local music players that cannot be utilized as a cellphone and will automatically wipe themselves clean on a timely basis (once they are reported as being stolen).

NippleSauce said:
If the phone is showing that message and was purchased off of eBay, then the phone was stolen from a business. The phone cannot be utilized as it will be flagged and will have its IMEI blacklisted after some time. That message you are seeing confirms that.
Unfortunately for you, there is no work around to resolve this - as theft isn't a 'real' phone problem. The protection with phone management is just a corporate move to give companies more control over the devices that they purchase. So essentially, there is a much lower chance of them being stolen. Because once they are stolen, they're basically just local music players that cannot be utilized as a cellphone and will automatically wipe themselves clean on a timely basis (once they are reported as being stolen).
Click to expand...
Click to collapse
Thanks vor your reply,
i don´t think the phones was stolen because the selers of this phones is a company in Germany and they have more than 50 pieces of this phones, They wrote on the listing that the phones was used only for demostration purposes , so google will not remove the mdm lock if i contact them on the geving email adress?

If the device is truly legally sold, you need to get into contact with the seller to see if they can release it from their MDM server. If they cannot, only they can be the ones to contact Google. Google will NOT help you if you do not have the original purchase order from when it was MDM enrolled. Even if the user has a ton of devices for sale, that doesn't mean they were acquired legitimately. It's possible they were supposed to be destroyed and kept enrolled to prevent them from being resold, which is what sounds most likely to me. As someone who works in IT asset management, the ONLY reason we leave our devices DEP or MDM enrolled is to prevent someone from snagging it before we dispose of it.