Related
Long story short; I sent the phone to a former NTSB investigator who confirmed what I already knew. Thermal damage.
The refurbished phone that they sent as a replacement was FULL of issues, so I had to have it replaced, as well. The camera would not focus, the sound recorder only recorded static, it wouldn't retain my preferences that I set in the phone, and randomly reverted to the default ringtone.
When I called back to get it replaced; I was greeted by a VERY friendly, helpful, and understanding representative who told me that the original claim WAS NOT handled properly. She overnighted a new phone and battery and asked me to return the original phone to a different address for examination. She agreed that they would probably just take one look at it and claim that it was physical damage. She reversed the charges for the replacement - even though I had the "Premium" insurance on it. She also noted that I had a written report with photos to verify that it was a manufacturing defect - with the obvious caveat that if there really was physical damage that I would have to pay the deductible. Naturally; I used my Sony video microscope to take photos of every angle of the phone, the edges, etc. - to prove that there wasn't so much as a single blemish anywhere on the phone that they could construe as being "physical damage" - aside from the obvious darkening to the inner plastic from the internal heat, and it was isolated to the rear of the display.
I got back in town early yesterday and the newest replacement was already waiting. I charged the battery and fired it up. So far; so good. Works like a champ. Bear in mind, it's been less than 24 hours...
Oddly; I didn't start having issues until AT&T forcefully crammed the firmware update down my throat. And, no; I had done no modifications - such as rooting or work-arounds to either phone. So; I actually have a legitimate question: Have any of you experienced any phantom issues with your S4's, post firmware (FM3, I think) update? I know that it gave me a message: "Updating Camera Firmware", and the camera would no longer focus. I took copious photos and videos with it and have saved them for reference. In the videos; you can see that the camera is constantly zooming in and out of focus - even though it was stationary, aimed at a fixed subject, and at a very reasonable distance. Many of my downloaded programs also no longer worked, or would freeze up for no apparent reason. They all had worked perfectly prior to the update, as well as on my previous Motorola Atrix HD. They still are working perfectly on the Atrix HD that I passed down to my kids, after I unlocked it, rooted it, and installed the Pac-Man 4.3 ROM. When I got the first replacement S4; it kept prompting me to download the firmware update, and I kept denying permission - in the event that I felt frisky enough to do some fancy footwork on it later down the road. One morning I woke up and it had a message on the screen: "Software Update Successful!" After I angrily cleared that screen, it gave me the message about updating my camera firmware. Now; I'd only had it a day or so, so I can't verify that everything was working properly before - it just seemed to be OK.
My next question is: Is there any way to block them from updating this phone, and constantly bombarding me and forcing me to install useless "bloatware" that I'll never use and only uses up more of my internal memory. I have the 32GB S4 so it's not a huge issue, but it's obnoxious, at the very least that they think that they know better than I do what I want to be installed on my phone. I can hide them, uninstall the updates and put them out of sight, but they're there, none the less, and I don't want them! Yeah; I know I agreed to their terms, but that just seems downright controlling and unfair. And, by the way; even if I do hide them, and uninstall the updates; they magically reappear in a few days and it seems like I'm constantly receiving messages prompting me to update them. Even if I decline; they download anyway. Sort of a "Wash, Rinse, Repeat" scenario.
OK; after my last nasty rant, I expect (and deserve) some nasty feedback, but I'd really appreciate any suggestions or insight to these issues. Any similar experiences? I'd been foaming at the mouth waiting to get this phone, but it seems like it's been one terrific headache after another. I've only owned Motorola phones (since 1985) until now. Motorola now seems lackluster compared to the newer models or I'd have never jumped ship. Now; it seems like I made a $700.00 mistake. I really hope I'm wrong and just unfamiliar with other manufacturers equipment. Save me from myself!
Thanks, everyone!
Nukesnooper
The Samsung updates are kind of like the old "Window Updates needs to restart, postpone for X hours." But if you leave it there, then it will reboot by itself. Kind of like this updated by itself. The only way to avoid updates is rooting the phone and freezing or deleting that service, or of course, changing ROMs. (But I believe you're on MF3 firmware now so..)
Other than that, can't say much as I have the T-Mobile variant.
If you have MDB or MDL firmware do this. It will stop AT&T updates. I would freeze anything that even looks like a Samsung updater also.
Link Here
Thanks!
~wolverine~ said:
If you have MDB or MDL firmware do this. It will stop AT&T updates. I would freeze anything that even looks like a Samsung updater also.
Link Here
Click to expand...
Click to collapse
I guess the next obvious question is: "How?" I don't want to root the phone yet, but didn't think you could freeze any of their apps without rooting or modifying the stock firmware. I'm afraid to do any mods to it until I know it's going to be a stable device - and hence; not taking any chance of voiding my warranty. Sorry for what's probably a dumb question, but I'm new to modifying phones.
Also; what is the best way to sterilize the phone that I'm returning of contacts, remnants of uninstalled programs, etc?
Added: It already has the MF3 update installed. Grrr!
Thanks again!
NS
nukesnooper said:
Also; what is the best way to sterilize the phone that I'm returning of contacts, remnants of uninstalled programs, etc?
Added: It already has the MF3 update installed. Grrr!
Thanks again!
NS
Click to expand...
Click to collapse
A factory reset from settings/accounts/backup & restore will wipe out all that. I would think it would be safe to do that with MF3, but I'm no expert. You might want to get other opinions also.
ptguca cross
~wolverine~ said:
A factory reset from settings/accounts/backup & restore will wipe out all that. I would think it would be safe to do that with MF3, but I'm no expert. You might want to get other opinions also.
Click to expand...
Click to collapse
Great until I went to confirm that I was going to delete everything in my brain and give them a pint of virgin blood; then it asked for a "New Password" and wouldn't give me anything but a numeric keypad. Huh??? Sup wid dat? It wouldn't delete ANYTHING until I confirmed my "password" which isn't numeric at all, but gave me no other options. I'm going to try booting it up from "off" and see if there's a way to do it from there. FEAR.
Android 5.1.1 Experience and Discussion
OTA 5.1.1 Link https://android.googleapis.com/pack...gned-volantis-LMY47X-from-LRX22L.5cb0c625.zip
Factory Images 5.1.1 https://dl.google.com/dl/android/aosp/volantis-lmy47x-factory-3efdc8d4.tgz
marcomsousa said:
Android 5.1.1 Experience and Discussion
OTA 5.1.1 Link https://android.googleapis.com/pack...gned-volantis-LMY47X-from-LRX22L.5cb0c625.zip
Factory Images 5.1.1 https://dl.google.com/dl/android/aosp/volantis-lmy47x-factory-3efdc8d4.tgz
Click to expand...
Click to collapse
Wish these were also available for the LTE model
[/COLOR]
Zylograth said:
Wish these were also available for the LTE model
Click to expand...
Click to collapse
Want to trade?
*WARNING* RE-enable OEM Bootloader Unlocking after Update!!!
Just a heads up and REMINDER to go into Developer Options and turn OEM Unlocking back on after the OTA update because it had turned mine back off after sideloading.
I wish I had my laptop set up so I could remote in from work right now and begin downloading the image.
I take it Root is still working?
bjacks12 said:
I wish I had my laptop set up so I could remote in from work right now and begin downloading the image.
Click to expand...
Click to collapse
I've been thinking off using one of my phones as a hotspot for my laptop...Just not thinking it will be quite fast enough and stable enough to download and get a good MD5. My company watches everything.
techiedj said:
Just a heads up and REMINDER to go into Developer Options and turn OEM Unlocking back on after the OTA update because it had turned mine back off after sideloading.
Click to expand...
Click to collapse
Why not just get it over with and UNLOCK it? Once you are unlocked, the state of that checkbox is irrelevant.
techiedj said:
Just a heads up and REMINDER to go into Developer Options and turn OEM Unlocking back on after the OTA update because it had turned mine back off after sideloading.
Click to expand...
Click to collapse
Why is that important? Will I brick my device if I don't? Please explain for an absolute newbie!
Thank you!!!
s0101 said:
Why is that important? Will I brick my device if I don't? Please explain for an absolute newbie!
Thank you!!!
Click to expand...
Click to collapse
If you don't unlock, and leave your bootloader unlocked it can. If you have the check box checked then the bootloader remains locked. So if you get caught with a bad flash or anything else that causes a bootloop there is no way to gain access to the bootloader and run fastboot.
Not off to a great start. I've had my 3rd crash triggered simply by browsing to the reddit nexus 9 board. Now it appears to be on a forced cache erase after the consecutive crashes.
From this we can safely say nobody in Google pays any attention the forum moaning otherwise they might have noticed this issue.
Anyone get an OTA for the LTE version yet? They haven't posted the factory images which scares me a little that LTE might get left behind. The 5.0.2 links went up for both at the same time.
stuken said:
Not off to a great start. I've had my 3rd crash triggered simply by browsing to the reddit nexus 9 board. Now it appears to be on a forced cache erase after the consecutive crashes.
From this we can safely say nobody in Google pays any attention the forum moaning otherwise they might have noticed this issue.
Click to expand...
Click to collapse
Mine's still running really warm and it's losing power over USB just by being on. I'm watching the battery drain simply from the screen idling on Google Now. Come the **** on Google, heat and battery drain should have been primary concerns.
Edit: Fortunately though, it seems like the entire device is running buttery smooth, which is literally a first on stock Android for me. Even my Nexus 6 hiccups without a custom ROM and that has the S805 and 1 more GB of memory.
Still no OTA for LTE on 5.01 -> 5.02 ...
What the hell is Google doing... firstly releasing almost beta Lollipop that on our Nexus have serious issues.. after waiting and being the last device to be updated still no upgrade to LTE which is more expensive and deserves at least same support.
If our model is left behind, I will surely not buy a Nexus device ever again.
atomikpt said:
Still no OTA for LTE on 5.01 -> 5.02 ...
What the hell is Google doing... firstly releasing almost beta Lollipop that on our Nexus have serious issues.. after waiting and being the last device to be updated still no upgrade to LTE which is more expensive and deserves at least same support.
If our model is left behind, I will surely not buy a Nexus device ever again.
Click to expand...
Click to collapse
LTE takes time. I wouldn't worry about it. I bet factory images are up within a day or two. I'm an LTE owner too, so I'm in the same boat. I'm just happy it actually started rolling out, as it started to look like it wasn't happening. This is a much bigger update than 5.0.1 -> 5.0.2
Updated this morning. So far so good
So far, it's definitely an improvement on performance but it remains to be seen with this is another cache-wipe factor or something. One of the first-impression fixes is that the light sensor seems to actually work now, while it was almost useless before.
I noticed the stock kernel is now on 2,5GHz high and that both cores are allways on, which i am not sure if it was happening on 5.0.x. I remember Franco noticing it on Nexus 6 5.1 too, so i guess it's a common practice by google to not turn cores off anymore.
Well so far so good. I never had major issues before. OTA side loaded fine. Did a factory reset to set up fresh. Now that everything is set up I'm just waiting for it to charge completely. It did get warm installing and updating everything, but no issues so far. Everything went smoothly.
There's a new apk named 'Who Am I?' That is disabled by default in this update. Turns out it's a widget that literally shows you the time and what your name is. Maybe it's for people with dementia or short term memory.
The way things have been going, most of us might have needed that widget by the time this update got to us if we'd waited much longer.
Hi figured we could use our own separate thread to discuss the killswitch Nvidia supposedly put in place on our old Shield tablets and see what has worked for those who have received their replacement units. If you've gotten a replacement please share if your old unit has been destroyed or not...if not please let others know what the old tablet has on it or what you did to attempt to prevent the brick! Thanks for helping us all out here!
As I said in the other thread, I received my new one, and my old one is still usable on rooted latest stock, unlocked bootloader, with the only app missing being Chrome for some reason. Nothing else disabled or uninstalled. Maybe they haven't turned on the server that sends the kill signal yet.
If the company wants the other device back (dunno if that is true), why keep it? You are breaking a deal while making it less appeling for companies to do this type of thing...+its a saftey risk for you and others around you.
Nvidia said they do not need it back
ManualG on the Nvidia forum said they are not requiring you send it back
"We don't require you to send it back to us to receive the replacement and are collecting them only to make it less of a burden on everyone else who dont have drop off locations like that close by." So you can keep it if you want ?
16 gig tablet, got it this morning. My original is still functional, it was stock rom, rooted with xposed on it. That's as much modding as I've done with mine.
does anyone have more informations about this killswitch?
Is it a service that needs to be deactivated or deleted or a kernel feature?
I just want to make sure it doesn't kill my old tablet when I set up the new one.
Alternatively, I could just flash an older factory image or custom firmware.
From what I've read on other forums (i.e. reddit) most have indicated that the killswitch is embedded in the bootloader and will activated on the defective tablet once the replacement tablet is registered on the nvidia side. I of course cannot confirm for this to be the case but just sharing what others have reported.
yea but it must communicate with the server then and that only works when Android is booted up and all communication drivers loaded.
So there must be another service running in Android that gives this information to the bootloader to kill itself.
If it's bootloader based, flash a bootloader from one of the older recovery images.
Will try that. BL from Update 2.2.2 should be fine?
actually if I flash it back to 2.2.2 it should be fine too since the changes to 3.X aren't that big
That should work just fine.
big time noob question but where are you getting the old bootloaders from to flash?
Until somebody's tablet gets deactivated and a log is captured during the deactivation process, everything said here or anywhere else is just speculation.
bluegizmo83 is right, however the discussion has to start somewhere so kudos to the OP for getting this thread started.
chicodelta said:
bluegizmo83 is right, however the discussion has to start somewhere so kudos to the OP for getting this thread started.
Click to expand...
Click to collapse
Oh I completely agree. I'm all for conversion. But I don't want people to get the wrong impression, like trying to flash an older bootloader. That may stop the deactivation, but it also may not. Its only speculation at this point.
bluegizmo83 said:
Oh I completely agree. I'm all for conversion. But I don't want people to get the wrong impression, like trying to flash an older bootloader. That may stop the deactivation, but it also may not. Its only speculation at this point.
Click to expand...
Click to collapse
Well said. I apologize if my post came through as a solution. I was only mentioning that as folks had mentioned a possible bootloader lock.
Any thoughts on whether flashing CM would serve as a way to circumvent the killswitch? I see that release for this tablet is already available http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043. Thoughts?
scorpionx said:
Well said. I apologize if my post came through as a solution. I was only mentioning that as folks had mentioned a possible bootloader lock.
Click to expand...
Click to collapse
No problem. As I said, I'm all for the discussion, I just wanted to make it clear to everyone that its all just speculation at this point.
I think the old bootloaders are in the old full OTA's someone correct me if I'm wrong. You can also extract them from the full OTA
chicodelta said:
Any thoughts on whether flashing CM would serve as a way to circumvent the killswitch? I see that release for this tablet is already available http://forum.xda-developers.com/shi...-cyanogenmod-12-shield-tablet-lte-na-t3055043. Thoughts?
Click to expand...
Click to collapse
To me, this is the most logical place to start at this point! Maybe it works, maybe it doesn't, but unlocking the bootloader, rooting, and installing a custom rom seem like a good starting place. If the stock devices are definitely getting wiped anyways, any changes we make now can't hurt the chances of keeping it alive!
I'm not sure what is up, this isn't a new thing, but people keep coming to me (1-2 a day) with this issue.
If your phone isn't stock, DO NOT RELOCK your bootloader. You will 'soft brick' it, and at this time there is no easy route to fixing it.
If you are on EE UK, Verizon or another carrier blocking bootloader unlocks, and you used dePixel8 to unlock it, DO NOT relock your bootloader unless you are sure you don't want it unlocked again.
Finally, dePixel8 is UNSUPPORTED. Don't come to me if you can't get it to work, don't come to me if you used it them messed up your phone by flashing something bad or whatever. Its on you.
What's the fix if this does happen?
infamousjax said:
What's the fix if this does happen?
Click to expand...
Click to collapse
There isn't one and no guarantee there will be one. Don't do this.
tw1tch175 said:
There isn't one and no guarantee there will be one. Don't do this.
Click to expand...
Click to collapse
Fair enough. Thanks
This should be pinned!!
Mods?
It was all just an illusion
Interesting.. glad this didn't happen to me. I did relock my bootloader once because i was having issues activating my SIM card. I wanted see if that was the reason. Once i did manage to get the SIM activated i went through the process of unlocking using the dePixel8 method again. I guess i won't be doing that again.
Hah this would have been nice to see first. I ended up soft-bricked on my pixel xl. I hope a fix comes soon. Even a jtag or direct method somehow.
Flashing needs to be done directly since fastboot reads oem unlock and denys it.
Cataire said:
Hah this would have been nice to see first. I ended up soft-bricked on my pixel xl. I hope a fix comes soon. Even a jtag or direct method somehow.
Flashing needs to be done directly since fastboot reads oem unlock and denys it.
Click to expand...
Click to collapse
This isnt a new warning, its pretty much standard "Dont relock with non stock firmware".
JTAG is a no go, would have to attack to the ufs and rewrite at the best least the boot.img
Eh things happen. I know better now. And now I need to learn how to make it right
I don't understand why anyone WOULD relock the bootloader of not stock
318sugarhill said:
I don't understand why anyone WOULD relock the bootloader of not stock
Click to expand...
Click to collapse
Some people are not as experienced as us. Not hard to imagine, just noobs, no offense guys. You live and learn, no biggie. I say respect them and help them, I say welcome noobs.
If we expect our community to grow, we need to be respective of new comers.
318sugarhill said:
I don't understand why anyone WOULD relock the bootloader of not stock
Click to expand...
Click to collapse
I've heard of people doing it to try to reenable Android Pay since it won't work with an unlocked bootloader.
Alpione said:
I've heard of people doing it to try to reenable Android Pay since it won't work with an unlocked bootloader.
Click to expand...
Click to collapse
This is honestly the biggest reason I can see as to why this happens
Sent from my Pixel XL using Tapatalk
DELETED
ScytheSniper said:
First of all, I'd like to say thanks to all the hard work put into the dePixel8 BL unlock.
With that said, I would like to say a couple things about this particular statement.
1. It is slightly misleading, you can relock your bootloader and still unlock it again under the right circumstances. If your software is all stock and you use dePixel8 after relocking, it will unlock again.
2. This statement contradicts the previous one. You should probably avoid telling people "they can never unlock their bootloader again if they relock it" if there is ANY possibility that they can. After reading this statement from you in the unlocking thread I spent about 2 hours scouring threads to find out if this statement was always true, which it is not.
Again, thank you for all the hard work on getting this unlock out. The intent of my post here is only to help improve communication of potential problems.
Click to expand...
Click to collapse
There is nothing misleading about the post. The statements are true. Wait til tomorrow, when complaints start coming in about how people cant seem to unlock.
DELETED
ScytheSniper said:
I'm sorry, but this is just not the case. I have verified this myself with my own Pixel XL from Verizon. On a stock image load I can unlock and lock the bootloader as many times as I want using dePixel8 to perform the unlock. Your statement in my opinion implies that if I relock the bootloader AT ALL it will fail to unlock ever again.
This may not be your intention to be misleading, but I know I am not alone in my interpretation of your statement. All I am asking is that you not make statements like the one I quoted which are provably false. Also, I did not say that your entire post was misleading, only the statement in quotes is.
Click to expand...
Click to collapse
I'm not sorry. You are lacking information/knowledge on the subject. The OP statement is accurate.
The statement was made with good reason, based on fact and prior knowledge. You will see why tomorrow, when people start complaining.
DELETED
ScytheSniper said:
I'm sorry, but this is just not the case. I have verified this myself with my own Pixel XL from Verizon. On a stock image load I can unlock and lock the bootloader as many times as I want using dePixel8 to perform the unlock. Your statement in my opinion implies that if I relock the bootloader AT ALL it will fail to unlock ever again.
This may not be your intention to be misleading, but I know I am not alone in my interpretation of your statement. All I am asking is that you not make statements like the one I quoted which are provably false. Also, I did not say that your entire post was misleading, only the statement in quotes is.
Click to expand...
Click to collapse
The next security release should rollout tomorrow... And with that there will be a fix for VZW models preventing depixel8 from working. So IF you relock your bootloader after taking this update, we'll you'll be SOL. It's only misleading if you don't have prior knowledge of pretty much anything android.
I mean of course you can lock and unlock as many times as you want right NOW. Tomorrow will be a different story I guarantee.... But go ahead and be our guinea pig. I for one just say thank you @jcase and @beaups and listen to their advice. They've been around a long time and given us lots of goodies. I don't question them.
ScytheSniper said:
If I am lacking in knowledge and information why am I able to unlock and relock my bootloader at will on my Pixel purchased at Verizon?
Click to expand...
Click to collapse
I'm guessing you dont understand how depixel8 works.
I'm guessing you dont realize that google could remotely nix this in the butt any any moment
I'm guessing you are unaware of NDE63X at this point and it's effect on the situation.
Why don't you lock your bootloader for a few days, then try? or just sit back, watch ppl ignore the PSA, then start compaling about being stuck locked.
SO I did some research and found some very interesting info about the bootloader bull**** that is going on with Android.
read about it here.
This means good bye to un locking bootloaders... Mine is unlocked and because of android/google my dam phone keeps showing an aggravating massage that its not trusted when i turn it on ... Im pretty sure now after Nougat, people will be going to Apple in droves...
nickcaper said:
SO I did some research and found some very interesting info about the bootloader bull**** that is going on with Android.
read about it here.
This means good bye to un locking bootloaders... Mine is unlocked and because of android/google my dam phone keeps showing an aggravating massage that its not trusted when i turn it on ... Im pretty sure now after Nougat, people will be going to Apple in droves...
Click to expand...
Click to collapse
1) This is Sony's choice to allow the unlocking of bootloaders or not, there's no reasons that they don't allow it in the future.
2) Do you know that 90% of android users aren't rooted, so...
niaboc79 said:
1) This is Sony's choice to allow the unlocking of bootloaders or not, there's no reasons that they don't allow it in the future.
2) Do you know that 90% of android users aren't rooted, so...
Click to expand...
Click to collapse
Yes yes.. but...... Google is making it harder to root phones. Nougat will be even worse...
nickcaper said:
Yes yes.. but...... Google is making it harder to root phones. Nougat will be even worse...
Click to expand...
Click to collapse
Rooting devices with a locked bootloader can be seen as a security exploit, and the ability to do so means that Android is insecure.
What you basically complain about here, is that Google is trying to make Android more secure.
If you want to root your phone, just unlock your bootloader and flash SuperSU. That will always be possible.
The trick is, that unlocking your bootloader will wipe your data partition (hence securing your data from a potential breach when somebody stole your phone). The security warning at the beginning, is to let you, and potential reselling partys know that the bootloader is unlocked, and that with little to no effort all Android internal security measures can be worked around (flash a recovery and root it, and you're a happy data thief).
Of cause from an XDA-Users point of view it looks like that is something bad, but keep in mind that people like the ones you can find on XDA make up a roughly 1% of all Android Users. You need to keep in mind, there are also a lot of business users on Android, and these feel a lot better knowing that there secure company data is save on an Android device. Security used to be one of the major reasons why in the initial Android days nobody was using Android as a business device, and rather was sticking to Apple, cause iOS Devices were a lot securer by that time.
The message at the beginning is one of the reasons why I am still searching for a root exploit on my XP, so I can backup the TA partition and in case I resell it some day I can just relock the bootloader by restoring the partition, but after all, you need to admit that the warning itself is sensible, when you keep the above points in your mind
Myself5 said:
Rooting devices with a locked bootloader can be seen as a security exploit, and the ability to do so means that Android is insecure.
What you basically complain about here, is that Google is trying to make Android more secure.
If you want to root your phone, just unlock your bootloader and flash SuperSU. That will always be possible.
The trick is, that unlocking your bootloader will wipe your data partition (hence securing your data from a potential breach when somebody stole your phone). The security warning at the beginning, is to let you, and potential reselling partys know that the bootloader is unlocked, and that with little to no effort all Android internal security measures can be worked around (flash a recovery and root it, and you're a happy data thief).
Of cause from an XDA-Users point of view it looks like that is something bad, but keep in mind that people like the ones you can find on XDA make up a roughly 1% of all Android Users. You need to keep in mind, there are also a lot of business users on Android, and these feel a lot better knowing that there secure company data is save on an Android device. Security used to be one of the major reasons why in the initial Android days nobody was using Android as a business device, and rather was sticking to Apple, cause iOS Devices were a lot securer by that time.
The message at the beginning is one of the reasons why I am still searching for a root exploit on my XP, so I can backup the TA partition and in case I resell it some day I can just relock the bootloader by restoring the partition, but after all, you need to admit that the warning itself is sensible, when you keep the above points in your mind
Click to expand...
Click to collapse
No I still do not agree. Maybe they should just show it one time. Or a couple of times. not every friggin time I boot the phone. This is clearly to have people start to really consider NOT rooting there personal property.
When I buy a car. I can do what ever the want with it. Same with a house. But, these phone companies want us to use this device the way THEY want. Why? cause they want to track everything we do on it. Rooting stops that. Rooting enables me to delete apps that are totally useless and take up space and data on the phone. Rooting allows me to edit files, delete files, ad files the way I WANT THE PHONE to work. Not the way THEY want it to work.
It is super easy for these companies to let the new buyer know that the boot loader has been unlocked, let the person click a button to approve the unlock, then move on and let the person use the phone with no further warnings.
This warning is just about the same thing if you would change your cars radio or tires or engine parts, not use the factory parts, and the car would play a alert through the dash board or speakers every time you turn on the car that someone used there own parts, not the factory parts, to fix an issue.
NO I dont agree with you. Its no sensible....
If you think its sensible.... cool... Let people start doing this on every device, washing machines, microwaves, stoves, cars, TV,s stereos..... See how happy people get...
nickcaper said:
No I still do not agree. Maybe they should just show it one time. Or a couple of times. not every friggin time I boot the phone. This is clearly to have people start to really consider NOT rooting there personal property.
When I buy a car. I can do what ever the want with it. Same with a house. But, these phone companies want us to use this device the way THEY want. Why? cause they want to track everything we do on it. Rooting stops that. Rooting enables me to delete apps that are totally useless and take up space and data on the phone. Rooting allows me to edit files, delete files, ad files the way I WANT THE PHONE to work. Not the way THEY want it to work.
It is super easy for these companies to let the new buyer know that the boot loader has been unlocked, let the person click a button to approve the unlock, then move on and let the person use the phone with no further warnings.
This warning is just about the same thing if you would change your cars radio or tires or engine parts, not use the factory parts, and the car would play a alert through the dash board or speakers every time you turn on the car that someone used there own parts, not the factory parts, to fix an issue.
NO I dont agree with you. Its no sensible....
If you think its sensible.... cool... Let people start doing this on every device, washing machines, microwaves, stoves, cars, TV,s stereos..... See how happy people get...
Click to expand...
Click to collapse
Do you own a car? almost every state has safety inspections, you can't drive around with a compromised airbag/seatbelts/brakes. you'll get pulled over if even a lightbulb is broken. Sure you can do anything to your car, as long as it doesn't compromise its safety.
Do you own a house? every state has safety regulations when building one. Sure you can do anything you want to your house, as long as it doesn't compromise safety.
Android is securing their platform, there's nothing wrong with that. You're even given an OFFICIALLY supported method to root, just unlock the bootloader. You're crying about a warning you only see when you boot the phone for half a second? really? the ENTIRE world Android population needs to be held hostage by crippled security because you don't like a yellow exclamation point on a boot screen for a few milliseconds? Jesus christ the entitlement on some kids
/rant
Oh my... It reminds me of the time when I had an HTC with s-off, every time I booted the phone it showed the joker with the s-off message.
It destroyed my life.!
The phone still works fine though.
Sent from my F8131 using XDA-Developers mobile app
acme64 said:
Do you own a car? almost every state has safety inspections, you can't drive around with a compromised airbag/seatbelts/brakes. you'll get pulled over if even a lightbulb is broken. Sure you can do anything to your car, as long as it doesn't compromise its safety.
Do you own a house? every state has safety regulations when building one. Sure you can do anything you want to your house, as long as it doesn't compromise safety.
Android is securing their platform, there's nothing wrong with that. You're even given an OFFICIALLY supported method to root, just unlock the bootloader. You're crying about a warning you only see when you boot the phone for half a second? really? the ENTIRE world Android population needs to be held hostage by crippled security because you don't like a yellow exclamation point on a boot screen for a few milliseconds? Jesus christ the entitlement on some kids
/rant
Click to expand...
Click to collapse
Come on now... You really think that a phone should be treated this such ridiculous nonsense?
They can secure there platform without the stupid notification. Geez man.. you must really like being under control of corporations...
nickcaper said:
Come on now... You really think that a phone should be treated this such ridiculous nonsense?
They can secure there platform without the stupid notification. Geez man.. you must really like being under control of corporations...
Click to expand...
Click to collapse
Yes! unlike you some people do serious work with their phones. It's so important Blackberry is banned in some countries over security concerns. This is not a ****ing game.
A warning on your boot screen is not a restriction, it's a compromise. Learn the difference.
Mod Edit
Thread Closed and addressed. This thread and OP has ran it's course....
nickcaper said:
Ohhh ook..
Mod Edit.
!
Click to expand...
Click to collapse