Related
I promised myself show how Samsung treats its and how they assume responsibilities.
More here:
Samsung Galaxy S I9000 blog
Samsung Galaxy S I9000 Facebook Page
The main ideea is that i am a lucky owner of a phone that comes from a batch that was released on the market with manufacturing errors.
Other owner with same problem found out:
Finally they(samsung) informed us that the display needs to be replaced. This means the front panel in totality will be replaced. I hope to get it back in a couple
of days. The way they were handling the phone i am worried if i will get it back in acceptable condition. It has been a really traumatic experience. They informed me it was a manufacturing defect and there seems to be a batch which might have this issue.
Click to expand...
Click to collapse
After x time the displays of these phones coming from that batch lose color depth and increase brightness, the overall image quality being shattered to pieces.
To be shure my phone had this particular problem, i tried everything from the software point of view that could be done : changed to stock android, tried different custom roms, even the ones with voodoo color fixes, factory reset (of course) but nothing.
I was shure then i had that problem as the owner above and i brought it to service (i just bought the phone in november 2010). I did not know i had to put the original android from samsung, so i got a phone call the next day from samsung service, being told that i voided my warranty and i should pay 350 dolars to fix it.
I understand that rules are rules and that it says that if you use other than original samsung software you void the warranty, but they know, and i know that this is a production fault having NOTHING to do with the software .
The main ideea is the phone comes from a batch with manufacturing defects and they SHOULD asume responsability.
Don`t get me wrong, i loved this phone and Android, but the way samsung deals with this problem is outrageous and i must "be heard" .
I hope your phones do not come from that batch.
Thank you & happy flasing,
Dan Gheorghe
bbluee:
You wrote that You have master degree in computer science
BUT IT DOESN'T PROVE ANYTHING...
were were you living last years?
you were smart enough to flash new firmware but you failed with ensuring your own security and comfort as a common customer, poor you
I can bet that almost everybody on xda do know that before sending broken device (ANY device!!!) to ANY service the most secure way is to ensure it has system and enhancements oficially supported by manufacturer.
Greetings!
V.
voriax said:
bbluee:
You wrote that You have master degree in computer science
BUT IT DOESN'T PROVE ANYTHING...
were were you living last years?
you were smart enough to flash new firmware but you failed with ensuring your own security and comfort as a common customer, poor you
I can bet that almost everybody on xda do know that before sending broken device (ANY device!!!) to ANY service the most secure way is to ensure it has system and enhancements oficially supported by manufacturer.
Greetings!
V.
Click to expand...
Click to collapse
I know i did not have the "best" approach, and if any other given problem they could be right.
I did not want to brag with the degree, only to point out that i know i didn`t do anything to get the phone to have that display problem, and the fact that i know that the software in this case HAS NOTHING to do with the fact this product comes from a batch with manufacturing defects.
I know that here on xda, are people with far more android and phones knowledge than i have.
And you just gave up? This post looks like garbage to me.
"It is like i buy a laptop with windows 7 and i have a hardware problem , take it into service with a linux operating system and they say the warranty was voided." is NOTHING like modifying phone firmware. Samsung doesn't provide you with the tools to flash 3rd party firmware to your phone - if you used ODIN, you used STOLEN Samsung software.
Masters degree in computer science - lol, read the book, "overschooled but undereducated." When sending back a product for warranty service, you re-install all stock firmware; that's pretty basic knowledge.
Sounds like you're bad mouthing Samsung for something that is your fault. Personally, I wouldn't have taken it sitting down; they definitely should fix it, and making a stupid blog post to spout non-sense is just silly - demand they fix it, and know your rights under the law before you do.
phzi said:
And you just gave up? This post looks like garbage to me.
"It is like i buy a laptop with windows 7 and i have a hardware problem , take it into service with a linux operating system and they say the warranty was voided." is NOTHING like modifying phone firmware. Samsung doesn't provide you with the tools to flash 3rd party firmware to your phone - if you used ODIN, you used STOLEN Samsung software.
Masters degree in computer science - lol, read the book, "overschooled but undereducated." When sending back a product for warranty service, you re-install all stock firmware; that's pretty basic knowledge.
Sounds like you're bad mouthing Samsung for something that is your fault. Personally, I wouldn't have taken it sitting down; they definitely should fix it, and making a stupid blog post to spout non-sense is just silly - demand they fix it, and know your rights under the law before you do.
Click to expand...
Click to collapse
Ok, ok... Stop throwing rocks men ) . I said i know i have mistaken in not flashing the phone with the original firmware. Again i did not want to sound cocky in the first post.
Please excuse me if i did.
I just wanted to say i know that what i did, had nothing to do with the display problem.
Was it my fault i bought a product from a batch with manufacturing defects?
Thank you for your feedback.
Has anyone tried porting the Android 3.1 system.img from the SDK to the A500 yet?
I want to say it was sp3dev that tried flashing the xoom 3.1 images and ended up bricking his tablet, so note sure if anyone has tried it again.
I'm thinking of having a gom but I only just got this tablet today. Is there a recovery ROM image that I can use to reflash the tablet in case of brickage?
dr1337 said:
I'm thinking of having a gom but I only just got this tablet today. Is there a recovery ROM image that I can use to reflash the tablet in case of brickage?
Click to expand...
Click to collapse
No recovery yet as the bootloader is still locked.
Acer will issue an official update in the next couple of weeks, so why risk it? There's no rush.
Bragging rights......jk
I actually would like a clean system.img without the Acer bloatware too.
You can use this:
http://forum.xda-developers.com/showpost.php?p=14076075&postcount=2
to fully restore to stock US.
I recommend that 'how to' for recovering the tablet be placed in the HOW TO thread, and that thread be stickied.
dhruvmp said:
I want to say it was sp3dev that tried flashing the xoom 3.1 images and ended up bricking his tablet, so note sure if anyone has tried it again.
Click to expand...
Click to collapse
:facepalm:
Me? No, it was not me. Meh, i don't care for ****roid and the only thing i want to flash is a proper distro like ubuntu or fedora.
Would be interesting to see what the logcat dump produced to try and work out the incompatibilities.
FloatingFatMan said:
No recovery yet as the bootloader is still locked.
Acer will issue an official update in the next couple of weeks, so why risk it? There's no rush.
Click to expand...
Click to collapse
+1 on that...if acer sticks to a June time frame of getting 3.1 to us then it would be a better deal...thats just around the corner and there will be less bugs getting an update (at least i hope so) from the maufacturer then trying to port it from a different device. compared to the g-tab that i had...this thing runs pretty dam good with stock rooted Rom and bloatwate removed...once we get official 3.1 update with mouse and additional peripheral support...then thats gonna make that much sweeter.
Sent from my SCH-I510 using XDA Premium App
One thing to think before
Same for me once I removed those crap apps from Acer.I guess Acer will never learn about putting their own apps to blingbling the whole tablet. I don't need slow beautiful tablet I need an overboosted one They build slow PCs, they build slow laptops, slow tablets and I guess slow mobiles phones too and once you make a clean instal on it, oooohhhhh wonder its works like a rocket ------->>>>>>>>>
I guess it s marketing ... selling slow things so that people buy a new one earlier.
And then the other trouble that I m expecting to come......
I m not sure about it but in some threads they telling that if some apps are missing on
our tablet update won't work.
Ok, we know how to revert back to original Acer tablet and do the update to remove again those crap apps again wth....????
Atleast it s not nessecary to hack Acer laptop and PC to instal windows again.
What we need is bootloader from Acer or from a Dev if Acer won't, updates are secondary.
I don t trust them since they could make updates to prevent installing custom roms like
Apple with their never ending we need to block jailbreaking attempts
So be careful about those updates........
3.1 original
I would wait for 3.1, the problems of getting it from another tab would not be worth it.
It should be here hopefully this week sometime!!!
It has been reported that if your device was EVER rooted you wont have access to Google movies on market...even after factory reset/flashing stock rom...fyi this was on xoom. Not sure how much truth there is to this, but I'm not chancing it.
gmpdmd said:
It has been reported that if your device was EVER rooted you wont have access to Google movies on market...even after factory reset/flashing stock rom...fyi this was on xoom. Not sure how much truth there is to this, but I'm not chancing it.
Click to expand...
Click to collapse
Being fearful is the safer option... but you really should think this through clearly. How would they know if your tablet has EVER been rooted? Do they store the information on their servers? If so, what about when someone buys your tablet second hand? Are they denied from the movie market forever? Is the tablet forever "poisoned"?
The above scenario is the only way they could know as all traces of being rooted can easily be removed from the tablet itself... that is the nature of having root after all; total control.
Again, if you are fearful or uncertain, do not do anything to your tablet. Please do not spread your fear amongst others though because someone will soon be quoting you and claiming that "they" can tell if your tablet has ever been rooted. As you have already said, " It has been reported that...". Reported by whom? There is no answer. Did they verify the mechanism that testifies that the tablet has EVER been rooted? There is no answer.
It is fine to ask a question but as soon as you say, "it has been reported", then you are spreading fear, uncertainty, and doubt. Bad newbie. No cookie for you.
strikethree said:
Being fearful is the safer option... but you really should think this through clearly. How would they know if your tablet has EVER been rooted? Do they store the information on their servers? If so, what about when someone buys your tablet second hand? Are they denied from the movie market forever? Is the tablet forever "poisoned"?
The above scenario is the only way they could know as all traces of being rooted can easily be removed from the tablet itself... that is the nature of having root after all; total control.
Again, if you are fearful or uncertain, do not do anything to your tablet. Please do not spread your fear amongst others though because someone will soon be quoting you and claiming that "they" can tell if your tablet has ever been rooted. As you have already said, " It has been reported that...". Reported by whom? There is no answer. Did they verify the mechanism that testifies that the tablet has EVER been rooted? There is no answer.
It is fine to ask a question but as soon as you say, "it has been reported", then you are spreading fear, uncertainty, and doubt. Bad newbie. No cookie for you.
Click to expand...
Click to collapse
Post is on Droid Life...what I consider a reputable source. I cant post links yet. Go to site and search for "xoom google movies" Its second post down. I'm no noob...rooted many phones and tabs...just new too posting here. Sorry I did not provide link initially
Since Google Movies is about the most expensive way of watching video currently available, I'm not at all concerned over their decision to block rooted devices.
I've wondered this before about cell phones and tablets. I figured it would be more of a carrier thing, wanting to keep everyone in check on device warranties. The capability is certainly there on a carrier based device to simply track the sw version (mods) and root status. I figured it would come up at some point when there was a compelling enough reason for someone to make decisions based on that info. Hopefully it will be limited to content providers, such as in this case. I don't know that there is a need for fear and panic, just more for us all to think about before rooting. I thought about this before rooting my first phone, but also decided that rooting was a better way to avoid bloatware, etc. Until they cut my service for rooting, I'll always seek a better experience on my phone or tablet. Apparently there has been no compelling business reason for them to do that as of yet. Movie licensing is understandable, I'm 100% behind copyright protections. Just one more consideration before rooting a tablet.
Sent from my Xoom using Tapatalk
I just got couple Fire HD 8 6th Gen tablets for my kids, and thought I'd flash them right away with a custom ROM. I was quite disappointed with the absence of development for this tablet.
Anyway, as far as I understood from reading the forum (and I just started, sorry if I missed something), the first problem is the factory locked bootloader. And it sounded from a post I read like it's something that cannot be solved: http://forum.xda-developers.com/hd8-hd10/help/rooted-boot-img-t3508316 (bootloader locked discussion starts at the bottom of the 1st page).
Well, I am definitely not a pro in mobile development (I work on server side software for living), so I beg your pardon if I'm wrong. But unlocking a locked bootloader is not something unheard of.
So, I was wondering, if it could be done for other device, then probably it can be done for this one too. And the fact that it has not been done yet could mean for example, that this device is somehow different. Or, it could mean that there was no one yet with enough expertise AND the device at hand to do it.
So if the latter is true, and it's just lack of attention from good developers. Then I guess it could be arranged to donate a device to a reputable XDA dev. A dev that would be interested in having a challenge. And a free device.
I would definitely pitch in, and if you would too, please tell. And if you know an XDA dev who has expertise to do it, please tell too, and give an example of their work.
All the above is open for discussion of course, constructive suggestions would be much appreciated.
The 7" is locked but got a lot of love and is now rootable. If the guys at Kingroot that interest, we might see something but otherwise not. Until rooted, not much point porting a ROM.
So I suppose the proposition is to send a device to KingRoot guys?
...in China.....
I was wondering how the issue of locked encrypted bootloader was solved for other Fire devices. Here's how it's been done for Fire HDX 8.9: http://forum.xda-developers.com/kin...bootloader-unlock-procedure-software-t3030281 . I suppose the bug used in this method has been fixed already, this is just a demonstration that it can be done.
That was cracked using a crypto bug. Basically exploiting a weakness in the RSA encryption of the bootloader's signature. It's incredibly rare for encryption to get totally broken like this, and easily patched with system updates. Kinda got lucky on that one. Best thing to hope for first is root, then try to find a way around the bootloader's protection. These keep getting exponentially harder, and there's a lot more money on developing protections than breaking them.
I received one as a gift. I will probably never use it unless its opened up.... i mean im appreciative that someone gifted me it. But I become really upset by the fact that samsung and amazon... all the big players really lock up their bootloader and force me onto some ecosystem when i know the tablet or device could work just so much better. Anyways, if there is anything i can contribute let me know...
Download the Kingroot App then run it. After running it once or twice it will ask you to send a device request. Root may eventually be achieved for the 6th Gen but that may be as far as it gets. Very unlikely that the bootloader will be unlocked. Amazon actively puts a lot of effort into keeping them locked. Its been a while since any newer version of these Fire bootloaders have been unlocked. The HD 8 5th Gen is about 2 years old and the only thing thats been achieved was root and that was done by Kingroot..... But hey nothings impossible....
Now it's clear there's a security problem with the official build of Oreo before Sept builds.. now all the Oreo roms and official roms have this vuneralablity... If you're gonna continue to publish them without replacing them with the sept security patch you may as well put a damn virus in you're roms cause that's basically what you're doing...
Pixelxluser said:
Now it's clear there's a security problem with the official build of Oreo before Sept builds.. now all the Oreo roms and official roms have this vuneralablity... If you're gonna continue to publish them without replacing them with the sept security patch you may as well put a damn virus in you're roms cause that's basically what you're doing...
Click to expand...
Click to collapse
What's the vulnerability?
Plain and simple the software needs removed.. doesn't that apply to the devs policy's which they agreed to here on xda not to publish anything which may be a threat to someone... So you know what should of happened is the devs should of removed the software right away. That never happened so I've lost all faith in theses devs and publishers of official software threads...
I ignore all posts where the word "of" is used instead of the correct "have" or at least the contraction ending in 've that sounds like of.
...should of happened
sliding_billy said:
I ignore all posts where the word "of" is used instead of the correct "have" or at least the contraction ending in 've that sounds like of.
...should of happened
Click to expand...
Click to collapse
I ignore all posts that don't make sense like the OP's and this thread.
Pixelxluser said:
Now it's clear there's a security problem with the official build of Oreo before Sept builds.. now all the Oreo roms and official roms have this vuneralablity... If you're gonna continue to publish them without replacing them with the sept security patch you may as well put a damn virus in you're roms cause that's basically what you're doing...
Click to expand...
Click to collapse
First, there are no Oreo roms. Secondly, the devs who support our phones for free owe you nothing. Lastly, you need more than 12 posts to be taken seriously about anything around here. And, you can never post enough to attain the right to throw around accusations about the devs who, again, support our phone for free.
Pixelxluser said:
Now it's clear there's a security problem with the official build of Oreo before Sept builds.. now all the Oreo roms and official roms have this vuneralablity... If you're gonna continue to publish them without replacing them with the sept security patch you may as well put a damn virus in you're roms cause that's basically what you're doing...
Click to expand...
Click to collapse
Tell us how you really feel!
Windows people ?
Sent from my Pixel using XDA-Developers Legacy app
Pixelxluser said:
Now it's clear there's a security problem with the official build of Oreo before Sept builds.. now all the Oreo roms and official roms have this vuneralablity... If you're gonna continue to publish them without replacing them with the sept security patch you may as well put a damn virus in you're roms cause that's basically what you're doing...
Click to expand...
Click to collapse
If this is the case all root and bootloader exploits need removing also.
Any bootloader exploits or method of rooting without and unlocked bootloader is a SIGNIFICANTLY large security risk.
Sent from my Pixel using Tapatalk
Are we going to remove ALL the old ROMs from XDA? SHEESH.
In before the lock.
One thing I've found out over the years with hacking Android you eventually get tired of doing just hacking so you move onto security... Well that's the case with me anyways. Getting rid of vuneralable software is actually a good thing...
There's a reason why malware is successful with Android, and it's one that still hasn't been addressed: most phones are using old software and haven't been patched against it.
Google does a lot of work to make Android secure and keep it that way. It pays people to find security exploits, works with hardware vendors like Qualcomm or NVIDIA to fix them if needed, then writes a patch that can be injected into the existing version with no fuss. If you have a Pixel or Nexus or BlackBerry product, you'll then get these patches. If you have any other phone you roll the dice and hope the people who made it care enough.
Pixelxluser said:
One thing I've found out over the years with hacking Android you eventually get tired of doing just hacking so you move onto security... Well that's the case with me anyways. Getting rid of vuneralable software is actually a good thing...
There's a reason why malware is successful with Android, and it's one that still hasn't been addressed: most phones are using old software and haven't been patched against it.
Google does a lot of work to make Android secure and keep it that way. It pays people to find security exploits, works with hardware vendors like Qualcomm or NVIDIA to fix them if needed, then writes a patch that can be injected into the existing version with no fuss. If you have a Pixel or Nexus or BlackBerry product, you'll then get these patches. If you have any other phone you roll the dice and hope the people who made it care enough.
Click to expand...
Click to collapse
Nobody hacks individual phones. They hack companies and clouds.
****! Hey, can y'all hold it for just a moment? Need to run to the store real quick. I'm out of popcorn.
Seriously, though, just simply rooting your phone is a security risk. Also, from what i've seen, the majority of ROM users are smart about what they download. It's the general public that downloads mischevious apps that spread viruses. And as someone else mentioned, the malware and viruses don't target one person's phone. They are free floating and latch onto whatever moron downloads it. Your phone is not exactly the best place to download all your porn
But seriously, there are exploits with every security patch...it's the reason we get them every month, lol. Android is great and I love it but the OS itself is full of holes that malware developers consistently take advantage of.
Couldnt say this better myself..
Security is engineered into everything we do
Our goal is to make Android the safest computing platform in the world. That's why we invest in technologies and services that strengthen the security of devices, applications, and the global ecosystem.
It's also one reason Android is open source. Being open allows us to tap into a global network of security talent full of innovative ideas that help make Android safer every day. Security experts around the world can review our code, develop and deploy new security technology, and contribute to Android’s protections.
As the Android ecosystem evolves, we continue to invest in leading-edge security ideas. And we want to share our knowledge openly with you. Explore below to learn about the latest technologies and information that help secure Android.
Adrian Ludwig
Director of Android Security
Pixelxluser said:
Now it's clear there's a security problem with the official build of Oreo before Sept builds.. now all the Oreo roms and official roms have this vuneralablity... If you're gonna continue to publish them without replacing them with the sept security patch you may as well put a damn virus in you're roms cause that's basically what you're doing...
Click to expand...
Click to collapse
With some custom ROMs whether or not the have the Sept security patch is probably the least of your problems, if security is a concern of yours... you should be more concerned with things like;
- what keys are they using to sign their ROM (Apks included). Did they generate their own private signing keys and platform keys, or did they just use a devkeys or keys provided in the SDK?
- what changes have they made to aosp sources or not integrate (or revert) that could reduce security?
- have they messed with android's security or permissions model?
- have they included legacy code (like forward porting), that may have been dropped in the first place do to being insecure (legacy mediaserver without seccomp integration).
- have they modified selinux policies in ways that potentially could open up attack vectors.
- does the ROM have odexing enabled? The fact is, odexing while useful for booting/loading programs faster, also has the side benefit of making an apk harder to tamper with...
- have any changes that have been made been audited, or verified for correctness?
...and the list goes on. You are worried about a monthly security patch, with a handful or two of fixes for CVEs, yet make no mention of far bigger concerns that may be present in XYZ custom ROM.
Just saying.
contribute to Android’s protections. Is one thing which is lacking from what I see... I hope you understand that there are underaged people who don't know any better about what's best for them and come running off to try to be the cool kids by rooting or adding unsecured software on their phones.. rooting is so crazy to do now a days you're all really going to the extremes by bypassing security features just so you can have root... That's not the message the younger generation should be taught... They should be taught the importance of how security works not 50 ways to bypass it... There's not a feature out there which Google wouldn't consider adding officially but also Google doesn't go off and use unofficial code to pull features from it would look bad for their business..
And as long as there's a community of underaged people who do go off and root and install unsecured software you might wanna lead by example and provide them with the best security you can... A child with unsecured software is scary that someone would open up security holes for them to be a possible victim and the best you're actually willing to do is try to remove yourself from the responsibility of being responsible for it by saying if you install our software you are responsible for any damages. You can't just publish something then go out and say you take no responsibility when by law you're still responsible for any damages cause you never legally got you're software that way...
Since you're the ones distributing the software you're liable for damages if there was a defect in you're product which was distributed.. security flaws and security bypasses count as defects in a product..
Distributorship and Liability
Even though the distributor is not responsible for manufacturing a product, it can be held liable in the event of defects. Under strict product liability laws, the seller, distributor, and manufacturer of a defective product can be held liable if a person is injured due to the defect. Though manufacturers are typically most responsible since they created the product, the liability can also fall to those that distribute or sell the defective items.
This liability law prevents the plaintiff from the need to prove the chain of supply. In order for any entity in the line of distribution to prove it has no fault, it would need to show which entity is actually responsible for the defect
I suggest you stick with Windows dude
The only thing your posts are good for is making people spit their coffee with humour, and embarrassing yourself.
Sent from my Pixel using XDA-Developers Legacy app
So first off, this is not a stolen phone. My neighbor recently passed away and my family was able to buy the house with everything in it. She was quite the hoarder and we found like 20 phones, most were garbage but there were a few S8s and an S10+ preserved in an OtterBox.
When I powered the phone on it was already reset and asking for the previous Pin or Google account.
It's running on SM-G975USQS4DTF6.
The IMEI is clean and it appears to be fully paid off.
I've tried so many different methods (reflashing stock, trying to flash combos, Samsung FRP bypass, etc.) but at this point I feel like I have no idea what I'm doing so I thought I'd ask for some help.
Is there any way to salvage this phone? Or is it as good as a brick at this point?
Meh... we get this once a week or more.
For a concise explanation of XDA's position on this:
[CLOSED] FRP bypass on Android 11
Hello there, I recently got scammed buying new phone on the Internet. Indeed the phone got locked a few days later and I am now stuck with the Google Account. The phone is a European Samsung Galaxy A12. Before to write this post, I looked for a...
forum.xda-developers.com
blackhawk said:
Meh... we get this once a week or more.
For a concise explanation of XDA's position on this:
[CLOSED] FRP bypass on Android 11
Hello there, I recently got scammed buying new phone on the Internet. Indeed the phone got locked a few days later and I am now stuck with the Google Account. The phone is a European Samsung Galaxy A12. Before to write this post, I looked for a...
forum.xda-developers.com
Click to expand...
Click to collapse
Ah, that's what I was afraid of. Any idea what I could do with the phone? Donate it somewhere where they have the ability to wipe it and give it away to someone? It's just gonna be sitting in a drawer otherwise.
I'll even give it back to sprint, but I was hoping to avoid that since they'll probably just refurbish it and sell it.
Do a Google search. How well those solutions work I have no idea.
At least you didn't get irate like the last poster.
There are solutions and workarounds here though for many other problems with Samsung's.
Plus modes, rooting guides and custom roms.
I appreciate the advice! Unfortunately I've exhausted pretty much every method I've been able to find.
And yeah, you don't need to worry about me getting irate. I totally get it, 99.9% of FRP locked phones are stolen, if you guys encouraged FRP bypass discussions here it would open up a whole can of worms, and that's not worth it for the ~3 people per year who have a legit reason to bypass it.
Thanks for the heads up though! Good to know this isn't the best place to be looking for an answer.
It's a good place for Android answers... just not that one.
FRP is one of my most despised Gookill features.
Worse I have a very long, complex password so entering it by hand is really fun... not.
I disable my account and do the reset from settings to avoid having to deal with it when doing a factory reset. Find my Device is another I hate.
Scoped storage and forced encryption are on the top of my list though. I refuse to go higher then Android 10 because of that Apple like crapware