I am happy with GB, don't want to upgrade to ICS (I haven't heard of any features I really want, don't want to risk 4G speed downgrade), so I wanted to get rid of the ICS update notification on my non-root E4GT. I played with killing the background processes programmatically, but it didn't help. But the following simple trick seems to have worked like a charm.
1. Make sure you close any current OTA update dialog, e.g., by tapping on Later.
2. Go to the device's Settings, and choose Date and Time.
3. Uncheck Automatic.
4. Tap on "Set date" and choose a date far into the future. Try for several years in the future, but it may not let you. (I had odd behavior when I set for several years in the future--it set it momentarily, but then changed the date back by itself. If it doesn't let you set several years in the future, you can also put it in airplane mode, which makes it more flexible with respect to time setting.)
5. After tapping on "Set", you should immediately get the OTA update dialog again. Tap on "Later". This should make the OTA update dialog come up later than the date you set in step 4, or maybe not at all. (On my device, I can't get it to come up at all, no matter what date I set. )
6. Put a checkmark beside Automatic.
And that's it.
After reboot, you still get a status bar icon (which you can clear with the Clear button), but not the annoying dialog.
I tested this by setting the date to various dates in the future. Prior to the trick, as soon as I moved the clock forward by an hour, it would pop up the dialog. Now it doesn't. I'll have to see if it pops it up if I just wait naturally. But so far so good, despite several test reboots.
or not deal with the status bar icon at all.....
http://forum.xda-developers.com/showthread.php?t=1774282
geeksmurf said:
or not deal with the status bar icon at all.....
http://forum.xda-developers.com/showthread.php?t=1774282
Click to expand...
Click to collapse
Yeah, but I think those methods need root. For instance, without root one can't access /cache. I don't have root (because despite having the phone for a couple of months I haven't found a root method that's both safe and 100% legal; the standard methods involve downloading a modified copy of the firmware from an unofficial source, and that's a likely violation of Samsung's/Sprint's/Google's copyright, though IANAL). My method doesn't need root.
arpruss said:
Yeah, but I think those methods need root. For instance, without root one can't access /cache. I don't have root (because despite having the phone for a couple of months I haven't found a root method that's both safe and 100% legal; the standard methods involve downloading a modified copy of the firmware from an unofficial source, and that's a likely violation of Samsung's/Sprint's/Google's copyright, though IANAL). My method doesn't need root.
Click to expand...
Click to collapse
Your reasons for not rooting are silly. Download the Kernel source from Samsung which they have to give you. Compile a rooted kernel and then flash it to your phone, enjoy the yellow triangle but you were "safe and legal". Taking updates over the air is as unsafe as flashing through ODIN. After your bricking trying OTA because a power fault in your phone caused it to shut off mid update you would take it to a Sprint store that services and likely have your phone flashed through ODIN as long as the bootloader is not corrupted. Though thats the free option that you can do yourself. Warranty exchange costs money Firmware updating any device you own with any method is extremely unsafe. People will always have to live with that.
Samsung must have given Galaxy S2's to the CyanogenMod team asking them to put CM on it because they wanted both Google's Open Source OS to not be on it and for them to not use Samsungs source to develop a rooted and custom os for it
But any method working would be valid for those normal users who don't wish to update. I do laugh at those poor unknowing souls who have this phone as a phone and they have an update crammed down their throat.
I was wondering how people would deal with this and while most would at some point get home and click update if the Super Brick bug had not been fixed how many would end up like Galaxy Note owners.
RainMotorsports said:
Your reasons for not rooting are silly. Download the Kernel source from Samsung which they have to give you. Compile a rooted kernel and then flash it to your phone, enjoy the yellow triangle but you were "safe and legal".
Click to expand...
Click to collapse
Unfortunately, the so-called kernel file (zImage) includes not just the Linux kernel itself, but also the initramfs. While Samsung provides complete Linux kernel source, it does not (as far as I know; I last checked in April) provide source code to all the binaries contained in the initramfs, such as redbend_ua. So if you build from Samsung-provided source, you get a zImage that won't work on the device, unless you add in the initramfs files. This is a loophole in the GPL2, it seems. Now, I guess I could pull these copyright-encumbered files from my device into the initramfs, but I am worried that I'll omit some necessary file and then get a device that won't boot, with no legal way of restoring the stock ROM (other than bringing it in to Sprint service, but Sprint would have the right to refuse service, since it'd be my own fault), since without root I can't run dd to backup the original kernel from the device. Plus I have little experience with initramfs. In any case, this is getting offtopic. Though if someone has a way around my difficulties, or is able to hand-hold me through creating a working initramfs, I would be very, very grateful for a PM.
arpruss said:
Unfortunately, the so-called kernel file (zImage) includes not just the Linux kernel itself, but also the initramfs. While Samsung provides complete Linux kernel source, it does not (as far as I know; I last checked in April) provide source code to all the binaries contained in the initramfs, such as redbend_ua. So if you build from Samsung-provided source, you get a zImage that won't work on the device, unless you add in the initramfs files. This is a loophole in the GPL2, it seems. Now, I guess I could pull these copyright-encumbered files from my device into the initramfs, but I am worried that I'll omit some necessary file and then get a device that won't boot, with no legal way of restoring the stock ROM (other than bringing it in to Sprint service, but Sprint would have the right to refuse service, since it'd be my own fault), since without root I can't run dd to backup the original kernel from the device. Plus I have little experience with initramfs.
Click to expand...
Click to collapse
So your actually afraid of legal action from Sprint or Samsung from downloading the unrooted EG30 tar and ODIN which itself is also a leak? Wow. As an end user about the only thing you have to worry about is your ISP and had you done it a couple months ago I wouldn't have worried. At this point in the US we now have to worry about an ISP falsely accusing you for downloading trial software from its distributor lol.
You will never get the source to the proprietary binaries and most often will not get replacements for them either. Sony apparently was very kind to the CM team giving them a stripped down camera driver for alot of their phones.
Compile the kernel and send it to me I will test it for you. I flash every day. Oh wait thats right you wouldn't want to distribute something I distribute 500 times a day. Nevermind.
RainMotorsports said:
So your actually afraid of legal action from Sprint or Samsung from downloading the unrooted EG30 tar and ODIN which itself is also a leak?
Click to expand...
Click to collapse
I have no fear of legal action here. However, I believe that in normal situations one has a moral duty to obey the law, except when the law is fundamentally unjust (parts of copyright law are stupid, but it's not fundamentally unjust), or something like that. But as I said, this is getting off-topic.
Compile the kernel and send it to me I will test it for you. I flash every day. Oh wait thats right you wouldn't want to distribute something I distribute 500 times a day. Nevermind.
Click to expand...
Click to collapse
If it's one copy and for testing purposes, it might qualify as fair use. I'll think about your kind offer. I'm kind of busy with other projects, though, at the moment.
Back to the original topic: it's a new day, and no update notification. It's looking like my simple method works. Plus, if I change my mind, the update is still there on the device.
Thanks for this simple fix! It worked great.
cg
@ arpruss:
Kudos to this creative yet simple workaround! Brilliant! I also applaud your conviction about right vs wrong & the moral aspect of your conduct. History has shown us that small compromises can often lead to the fall of great people & great nations. There is no shame in trying to do what is right. Good job mate!
Edit: gahhh, fixed your name, sorry!
chconser said:
@ arpuss:
Kudos to this creative yet simple workaround! Brilliant! I also applaud your conviction about right vs wrong & the moral aspect of your conduct. History has shown us that small compromises can often lead to the fall of great people & great nations. There is no shame in trying to do what is right. Good job mate!
Click to expand...
Click to collapse
Thanks!
By the way, I discovered a previously unknown exploit that let me root the phone without downloading any unofficial firmwares. Here's my report on the vulnerabilities that make the exploit possible.
arpruss said:
Thanks!
By the way, I discovered a previously unknown exploit that let me root the phone without downloading any unofficial firmwares. Here's my report on the vulnerabilities that make the exploit possible.
Click to expand...
Click to collapse
While this comment takes away from your op, and since you made it a comment here, i just have one thing to say.
Since your ethical view leaves to in a quandary of what is legal or not, you're simply rehashing an issue that dates back to 2010 and jailbreaking.
Its already been deemed appropriate for electronic devices to be made code available to the owner.
Good for you on ethics, but don't preach legalities.
:edit: And just because your ethical view leaves to question what you are doing, the above quote leaves you in hypocrisy status alone. You sir, found an exploit. Is that not the definition of hacking?
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2
While I await your undoubtedly educated response, i leave this amusing excerpt from Doc Holiday.. "My hypocrisy knows no bounds.."
http://www.youtube.com/watch?v=5v2ZBqjZyjA&feature=youtube_gdata_player
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2
MoHoGalore said:
You sir, found an exploit. Is that not the definition of hacking?
Click to expand...
Click to collapse
There is a DMCA exception for jailbreaking/rooting a phone (it's expiring this year, but hopefully the Library of Congress will renew it; even Apple isn't challenging the exemption this time around!), so as far as I know it is legal to root a phone if one can do so by legal means. My only objection is to downloading modified copyrighted firmwares without the firmware copyright holders' (Samsung and Sprint) permission. I have no objection to rooting one's phone when it can be done without such downloads. There is nothing wrong with hacking when (a) it's done by legally permissible means and (b) one's purposes aren't unethical.
p.s. I passed the vulnerabilities on to Samsung two weeks prior to publicly posting them, in accordance with responsible disclosure procedures.
Please show me, or anyone else here, where we or anyone is violating copyright laws..
The DCMA of 1998, which you are referring, has been appealed and over ruled. That is what gave (gag) Apple users the right. And undoubtedly the rest of the electronic community.
If we, or anyone else here, was violating copyright laws, do you really think XDA would be in existence?
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2
I think this off topic discussion would be better carried on privately. If you want to continue it, email me, please.
You made it public. With your response to Rain. Then again w your response about the "exploit" you found.
I just pointed out the obvious.
It is a good op. And it helps people. But don't sidestep your previous comments.. Ill leave it at this - leave the legal talk to the legal folks.
Good day sir.
:edit: Daddy told me a long time ago "Son, don't run the fence. Sooner or later you'll run into barbwire."
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2
THANKS
Thanks so much for this info!!! The OTA nag dialog was really getting old - just reset my phone back to GB after the ICS - see how fast I can drain your battery life, upgrade. I'm assuming that since you haven't posted otherwise, it is still working for you .
NLM1962 said:
Thanks so much for this info!!! The OTA nag dialog was really getting old - just reset my phone back to GB after the ICS - see how fast I can drain your battery life, upgrade. I'm assuming that since you haven't posted otherwise, it is still working for you .
Click to expand...
Click to collapse
I assume it would be working still, but ever since I got root on the device, I disabled the OTA update component of the Google Framework by using Autostarts, so it's a moot point on my device.
By the way, I get the impression that my wife's E4GT, which came from the store with ICS, has better battery life than my GB-based one. It could just be all the apps I've got installed, of course, but I get the impression that she gets a lot less drain with 4G than I do.
arpruss said:
I assume it would be working still, but ever since I got root on the device, I disabled the OTA update component of the Google Framework by using Autostarts, so it's a moot point on my device.
By the way, I get the impression that my wife's E4GT, which came from the store with ICS, has better battery life than my GB-based one. It could just be all the apps I've got installed, of course, but I get the impression that she gets a lot less drain with 4G than I do.
Click to expand...
Click to collapse
And your battery is how old?
Sent from my SPH-D710 using xda premium
Related
Is there any way to unroot on epictouch 4g i dont like the root is heating my phone
Most of us are not liking this root. Next time we will not be so quick to install it without a plan to take it off.
Sent from my SPH-D710 using Tapatalk
Just pull at it's base after it's rained.
Flash back to stock to unroot. Either the stock kernel or stock system image. If there isn't one then, well, that sucks. Think and read a little more before jumping in. I'm not trying to be a ****, I imagine you have already realized this.
Check here: http://forum.xda-developers.com/showthread.php?t=1272186
daneurysm said:
Flash back to stock to unroot. Either the stock kernel or stock system image. If there isn't one then, well, that sucks. Think and read a little more before jumping in. I'm not trying to be a ****, I imagine you have already realized this.
Check here: http://forum.xda-developers.com/showthread.php?t=1272186
Click to expand...
Click to collapse
thx bud
Definitely waiting for a better root. Too many people jumped the gun.
Sent from my SPH-D710 using XDA App
Kivamaki said:
Definitely waiting for a better root. Too many people jumped the gun.
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
It's not that there is an issue with the root method...it's just that compiling a kernel with (even without modifications) is not guarantee of an identical kernel (to stock), and that's assuming that there were no modifications to the code that made it's way into the 'stock' kernel the phones are shipped with...and then they modify it to be rooted and it the fallout blows outwards from there. That's the nature of experimental kernels. It takes a little while for a kernel to mature.
The root that is the most 'sure thing' is exploit based, for now. I'd imagine there are many teams working on that right this second. Sit tight, it'll happen.
Either that or Cyanogen (most likely) or another AOSP kernel will come out with a little polish on it--perhaps even derived from this early work--and things will grow from there.
This is fantastic progress this early in the game. Sit tight and enjoy for now. Only the "i have to tether" folks have much reason to be antsy. If you need to restore backups there is a way (by hand), if you need speed then you have it...The roms are on their way.
daneurysm said:
It's not that there is an issue with the root method...it's just that compiling a kernel with (even without modifications) is not guarantee of an identical kernel (to stock), and that's assuming that there were no modifications to the code that made it's way into the 'stock' kernel the phones are shipped with...and then they modify it to be rooted and it the fallout blows outwards from there. That's the nature of experimental kernels. It takes a little while for a kernel to mature.
The root that is the most 'sure thing' is exploit based, for now. I'd imagine there are many teams working on that right this second. Sit tight, it'll happen.
Either that or Cyanogen (most likely) or another AOSP kernel will come out with a little polish on it--perhaps even derived from this early work--and things will grow from there.
This is fantastic progress this early in the game. Sit tight and enjoy for now. Only the "i have to tether" folks have much reason to be antsy. If you need to restore backups there is a way (by hand), if you need speed then you have it...The roms are on their way.
Click to expand...
Click to collapse
thanks for the info ill be waiting for better Version
i have heard updating the "prl" and "profile" (menu > settings > about phone > system updates) makes u lose root... might as well try it, cant do any harm
daneurysm said:
If you need to restore backups there is a way (by hand)
Click to expand...
Click to collapse
How doI do this?
Thanks in advance
Sent from my SPH-D710 using xda premium
vikramjatt11 said:
i have heard updating the "prl" and "profile" (menu > settings > about phone > system updates) makes u lose root... might as well try it, cant do any harm
Click to expand...
Click to collapse
I did that but it still shows root. lol ..
To make the story short, I found a BB 20 minutes away and exchanged it there. I just tell them what the problem was:
data reset randomly , and have to reboot to get it working again.
1 red dot pixel in the middle of the screen
battery over heat after 5 minutes of playing Asphalt 6 ...
can't make/receive calls
Those were enough to get a replacement... Root was not mentioned (durh)
Thanks everyone that gave there input on this topic...
It's an article that I came across.
http://www.xda-developers.com/android/hard-brick-bug-on-galaxy-s-ii-and-note-leaked-ics-kernels/
If this article has been posted, sorry, Mods could delete this.
Sent from my SPH-D710 using Tapatalk 2
Its a non issue in my opinion. If you flash leaks, you know the chances. I flash the leaks and know o could end up with an epic doorstop. Long as its fixed when the official ota comes, it's cool
Sent from my SPH-D710 using Tapatalk 2
Nice article. Very informative. I personally never flash anything while on ICS. But based on that article that might not even be enough. It also gives us an idea that until Samsung/Google has fixed the issue we won'tbe sseeing an OTA updates. At least I would hope they wouldn't OTA an update that is going to brick a **** ton if devices.
I was victim of the superbrick towards the beginning. Whatever it did it really messed that thing up. If JTag can't repair it then it's hosed. Thanks for sharing.
It's faulty firmware from Samsung. Like was said above, until it's fixed, we likely won't see an OTA, and should never flash anything from ICS recovery.
Unlike Wizard Knight, I do see it as an issue, because it's faulty code from Samsung. People are not going to pay attention, or not read the full OP in an ICS thread and brick their phone. The fault here lies on both the person that flashed and on Sammy for their crappy code.
On the other hand, the kernel that Sbrissen is building from international GSII source is confirmed to have this code issue fixed, so we may not have to wait on Sammy to drop source to be able to use recovery again.
blackroseMD1 said:
It's faulty firmware from Samsung. Like was said above, until it's fixed, we likely won't see an OTA, and should never flash anything from ICS recovery.
Unlike Wizard Knight, I do see it as an issue, because it's faulty code from Samsung. People are not going to pay attention, or not read the full OP in an ICS thread and brick their phone. The fault here lies on both the person that flashed and on Sammy for their crappy code.
On the other hand, the kernel that Sbrissen is building from international GSII source is confirmed to have this code issue fixed, so we may not have to wait on Sammy to drop source to be able to use recovery again.
Click to expand...
Click to collapse
Yep Sbrissen and entropy got this fixed. Ive used his 3.0 Kernel and flashed about a billion times to test it lol. Its awesome and brick proof :] I just hope people wait for sbrissens 3.0 to be finished before they starting "borrowing" from it and calling it their own -_-.
Your post is a little misleading at best. This just a rehash of the conversation in two threads, including one in this forum:
http://forum.xda-developers.com/showthread.php?t=1644364
Let's avoid hype on this, OK?
garwynn said:
Your post is a little misleading at best. This just a rehash of the conversation in two threads, including one in this forum:
http://forum.xda-developers.com/showthread.php?t=1644364
Let's avoid hype on this, OK?
Click to expand...
Click to collapse
Avoid hype? This is very interesting. Ive been very very curious as to what was at the root of this since I was around for the first night of ICS leaks and a brick. Hype or not, its wonderful to see that information is being passed around and this is being worked on. Feels like a wonderful thing for the E4GT users.
HaiKaiDo said:
Avoid hype? This is very interesting. Ive been very very curious as to what was at the root of this since I was around for the first night of ICS leaks and a brick. Hype or not, its wonderful to see that information is being passed around and this is being worked on. Feels like a wonderful thing for the E4GT users.
Click to expand...
Click to collapse
My concern is that the information given to us is a big deal... It can easily be thought that someone either was negligent or worse by not addressing this sooner. I would rather see this through and hope the fix comes out soon... And hopefully without a blame game; otherwise people like Mr. Sumrall might not be willing to respond to future inquiries.
Hope that clears up why I mentioned hype.
Sent from my SPH-D710 using XDA
garwynn said:
My concern is that the information given to us is a big deal... It can easily be thought that someone either was negligent or worse by not addressing this sooner. I would rather see this through and hope the fix comes out soon... And hopefully without a blame game; otherwise people like Mr. Sumrall might not be willing to respond to future inquiries.
Hope that clears up why I mentioned hype.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Ahh yeah I got ya. I agree, I would much much rather see a fix and the knowledge that comes with it than seeing people get upset. I for one am happy to see things progressing and have no wish to blame anyone for anything. Even though it was a serious issue, we all take the risk of flashing things that are unknown upon ourselves.
blackroseMD1 said:
The fault here lies on both the person that flashed and on Sammy for their crappy code.
Click to expand...
Click to collapse
You're kidding me, right? Fault of Samsung? We are flashing ROMs that are for internal purposes only. They could introduce an unknown android virus or brick code just to test the response time of their workers, and if we flash it then it is soley our fault. I won't fault Samsung or any other company for our crazy obsessions or need to be on the cutting edge, download their internal projects, and put them on our fully functional devices before they have said to do so.
Now if they release it as official and it bricks the device it is exactly the opposite and 100% their fault, not the flasher.
Yeah. Anything other then official released software is on our heads. If I flash a leak and I brick my phone, which I did, then its my fault. I flashed Sbrissens CM9 back when he first released it. He sent me a test build. I flashed it. I bricked it. It was completely my fault. Wasn't Samsung or Sbrissens. Now if Samsung had officially released that file to the public and said oh yeah this is 100% safe to flash. Then maybe it would have been on them.
LudoGris said:
You're kidding me, right? Fault of Samsung? We are flashing ROMs that are for internal purposes only. They could introduce an unknown android virus or brick code just to test the response time of their workers, and if we flash it then it is soley our fault. I won't fault Samsung or any other company for our crazy obsessions or need to be on the cutting edge, download their internal projects, and put them on our fully functional devices before they have said to do so.
Now if they release it as official and it bricks the device it is exactly the opposite and 100% their fault, not the flasher.
Click to expand...
Click to collapse
If a person flashes a pre-release rom and bricks their phone, yes, it is their fault. However, for Samsung to be as far along as they are in development, and to still have a bug that physically destroys eMMC chips...yes, that is their fault.
The thing is, the coders at Samsung do this for a living, and a bug that's this bad should have been among the first things to be fixed. Considering that it's still present in builds, when the final should be out within the next couple months, is awful.
So yeah, again, it's the fault of the person flashing the rom if they brick their device, but to say that Sammy has no fault at all is ludicrous, because this bug is ridiculous and should have been killed through internal testing a long time ago.
blackroseMD1 said:
If a person flashes a pre-release rom and bricks their phone, yes, it is their fault. However, for Samsung to be as far along as they are in development, and to still have a bug that physically destroys eMMC chips...yes, that is their fault.
The thing is, the coders at Samsung do this for a living, and a bug that's this bad should have been among the first things to be fixed. Considering that it's still present in builds, when the final should be out within the next couple months, is awful.
So yeah, again, it's the fault of the person flashing the rom if they brick their device, but to say that Sammy has no fault at all is ludicrous, because this bug is ridiculous and should have been killed through internal testing a long time ago.
Click to expand...
Click to collapse
How are any of these leaks anything but internal testing? It is absurd to think that these bricks are of any fault to Samsung, they obviously aren't releasing these to us and then saying "Hey, flash this."
Granted, not all of us on here are adults, but for a second, let's be mature and take some ownership for our actions.
The part about it being Samsung's fault, is in regard to the Note. Not our device. They did release software that had the bug, and bricked devices.
But, that's so overblown. Replacing the device is more than enough, in my eyes, for taking responsibility. They are just required to provide a working device.
Any expectation above that, just shows impatience and naivete of the software development cycle.
Sent from my SPH-D710 using Tapatalk 2
So im ready to upgrade my phones on Tmobile and I read that the SGS 3 does not support LTE on Tmobiles network. Is this a deal breaker? Ive read that LTE is a battery vampire. Tmobile LTE network isnt due till next year. I plan on keeping the SGS 3 for 2 years, hoping it would be a bit of future proofing for me since its the hottest phone right now.
Is no LTE support a deal breaker?
Nope... I'm getting 10-15 down on a rough day in greater Los Angeles area. You really need it faster? Think it's good enough to perform every day activities on the phone.
Sent from my SGH-T999 using xda app-developers app
Yeah no way. I'm getting 20mps steady. That's stupid fast. Lte if available is quicker with better ping but the phone is excellent and Lte isn't needed with the new radios.
Sent from my SGH-T999 using xda premium
derek210 said:
Yeah no way. I'm getting 20mps steady. That's stupid fast. Lte if available is quicker with better ping but the phone is excellent and Lte isn't needed with the new radios.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Not only this but our device supports 41mbps, which by the time LTE rolls out, will be in most cities if not already.
(I know we wont get 41mbps realistically)
I already get 25mbps in NYC which is faster than my home internet speed. Seriously LTE is overkill (literally) as it just kills your battery.
androidmonkey said:
So im ready to upgrade my phones on Tmobile and I read that the SGS 3 does not support LTE on Tmobiles network. Is this a deal breaker? Ive read that LTE is a battery vampire. Tmobile LTE network isnt due till next year. I plan on keeping the SGS 3 for 2 years, hoping it would be a bit of future proofing for me since its the hottest phone right now.
Is no LTE support a deal breaker?
Click to expand...
Click to collapse
You should probably read before posting something that has been asked already.
The T999 has LTE bands already, they are just disabled by default.
Sent from my SGH-T999 using xda premium
I've looked at a billion comparisons...
androidmonkey said:
So im ready to upgrade my phones on Tmobile and I read that the SGS 3 does not support LTE on Tmobiles network. Is this a deal breaker? Ive read that LTE is a battery vampire. Tmobile LTE network isnt due till next year. I plan on keeping the SGS 3 for 2 years, hoping it would be a bit of future proofing for me since its the hottest phone right now.
Is no LTE support a deal breaker?
Click to expand...
Click to collapse
I'm no expert, but not much of a life living in a new state, so I read A LOT! And most of that reading has been about computers and mobile phones. I've seen about a million opinions on this; seen a lot of speed tests and other tests comparing the 2, and absolutely every piece of factual evidence so far has shown me that the T-Mobile's HSPA+ network is absolutely comparable to LTE. There are only very slight insignificant differences in the tests - some a few degrees higher, some a few lower - according to the tester's location, device, and environment. But they always come extremely close to the same numbers. I've heard LTE does eat a lot of battery, but that's (as always) depending upon individual usage. The SGS III, from what I understand, is capable of supporting LTE, even on the T-Mo model, it's just not being used since they aren't on it, so if/when they do go LTE, your phone will support it. Until then, I think you'll be just as happy with their network. I hope that helps ya! At least I'd feel like I accomplished something with my endless hours lookin at all this crap! Good luck!
Thanks. I ended up going with the SGS 3. So far I like it a lot, its very fast. I am coming from a SGS Vibrant with Slim ICS ROM on it, so I had to install a launcher to get rid of TouchWiz (currently Im using Nova Launcher).
U'll love it!
androidmonkey said:
Thanks. I ended up going with the SGS 3. So far I like it a lot, its very fast. I am coming from a SGS Vibrant with Slim ICS ROM on it, so I had to install a launcher to get rid of TouchWiz (currently Im using Nova Launcher).
Click to expand...
Click to collapse
Oh cool! Me too, had the Vibrant and alternated between 2 ROMs at the end - ICS Passion and Doc's Master, they were both so great! Don't care for TouchWiz at all. I'm currently using Apex right now, it's simple, quick n user-friendly, and comes with the customizing I like - plus it has the capability of running themes from other home launchers, ie; GoLauncher, which I think is friggin awesome! Check it out if ya haven't already, there's not a whole lot it CAN'T do! Anyway, I think you'll LOVE this phone! I never in a million years thought I'd part ways with the Vibrant! I'm really stoked, now that I know how to do everything! If u have any questions, need help with dev stuff, or u just want recommendations, like I said - bored, not much of a life here, so helping is no problem at all! I've been through XDA quite extensively, so I know pretty much all there is to know about the 2 devices I have, just have the noob status still cuz I never post! So feel free to ask anytime! Have fun!!
crayzeeteri said:
Oh cool! Me too, had the Vibrant and alternated between 2 ROMs at the end - ICS Passion and Doc's Master, they were both so great! Don't care for TouchWiz at all. I'm currently using Apex right now, it's simple, quick n user-friendly, and comes with the customizing I like - plus it has the capability of running themes from other home launchers, ie; GoLauncher, which I think is friggin awesome! Check it out if ya haven't already, there's not a whole lot it CAN'T do! Anyway, I think you'll LOVE this phone! I never in a million years thought I'd part ways with the Vibrant! I'm really stoked, now that I know how to do everything! If u have any questions, need help with dev stuff, or u just want recommendations, like I said - bored, not much of a life here, so helping is no problem at all! I've been through XDA quite extensively, so I know pretty much all there is to know about the 2 devices I have, just have the noob status still cuz I never post! So feel free to ask anytime! Have fun!!
Click to expand...
Click to collapse
Thanks, I installed Apex last night. I might buy the Pro version if it becomes my fav. I was on the fence about waiting to get the HTC One X+ that is rumored to be released at the end of Sept. Since I have a track record with Samsung and its a very popular device (more support from devs), I decided to go with Samsung again. The only thing I really need right now is ROOT. I watched a video on Youtube and it looks like its a fairly simple process, not as easy as the Vibrant though. I mainly need ROOT to install Titanium Backup. I'm still confused though about the "flash counter" that some people mention and how Tmo/Samsung can see that you flashed your device if it were sent in for replacement/repair. Any ideas on that?
androidmonkey said:
Thanks, I installed Apex last night. I might buy the Pro version if it becomes my fav. I was on the fence about waiting to get the HTC One X+ that is rumored to be released at the end of Sept. Since I have a track record with Samsung and its a very popular device (more support from devs), I decided to go with Samsung again. The only thing I really need right now is ROOT. I watched a video on Youtube and it looks like its a fairly simple process, not as easy as the Vibrant though. I mainly need ROOT to install Titanium Backup. I'm still confused though about the "flash counter" that some people mention and how Tmo/Samsung can see that you flashed your device if it were sent in for replacement/repair. Any ideas on that?
Click to expand...
Click to collapse
It's a counter that counts custom binaries, if serviced by Samsung they may check it and decline warranty. There is a no trip method in the development section that I highly recommend. Right now there is also an app anyways by guru ChainFire called triangle away, that resets the counter. Either way here's the link to the no trip method that is easy as pie for anyone. Enjoy !
http://forum.xda-developers.com/showthread.php?t=1739426
Yep!
androidmonkey said:
Thanks, I installed Apex last night. I might buy the Pro version if it becomes my fav. I was on the fence about waiting to get the HTC One X+ that is rumored to be released at the end of Sept. Since I have a track record with Samsung and its a very popular device (more support from devs), I decided to go with Samsung again. The only thing I really need right now is ROOT. I watched a video on Youtube and it looks like its a fairly simple process, not as easy as the Vibrant though. I mainly need ROOT to install Titanium Backup. I'm still confused though about the "flash counter" that some people mention and how Tmo/Samsung can see that you flashed your device if it were sent in for replacement/repair. Any ideas on that?
Click to expand...
Click to collapse
Yeah, I bought the Apex Pro, and I don't normally buy many paid apps - I just really like how easy it is to integrate with other things like themes, which I mentioned earlier, and then other things too, ie; lockscreen apps, status bar apps, fonts, icons...so even if I want just one thing different that Apex doesn't have, I can still get that thing and use Apex at the same time!
Rooting!! OK here's what I did, and not a single problem! This is the fastest, easiest time I have ever had rooting and/or flashing by a MILE! I was leery due to the IMIE issues being reported and also, like you, the flash counter voiding the warranty. (if anything happened and I was out of an almost $700 phone, I'd be seriously PISSED!!) So if you do decide to root and/or flash, I would HIGHLY recommend doing these things! 1st, go here: http://forum.xda-developers.com/showthread.php?t=1804123 and back up your IMEI. Just follow the instructions (super simple) to make a backup. I don't think u need to do a full NV backup (u'll understand what that means if u read thru the posts on this issue, but it doesn't matter) because you'll already have your IMEI backed up beforehand. I did it anyway tho, just because I felt safer that way. Up to you! Bookmark that thread tho, in case you ever encounter any IMEI or data probs cuz they're the go-to guys for that, and have all the RIGHT fixes! You'll see the other guy I'm referring to's method and a link to his thread referenced there, where there's a lot more background info, but the guy's thread I gave you the link for is WAY easier for performing the backup. As far as checking the backup to be sure it's there, that can get confusing - If you followed the directions, I promise it worked, just gets techie when trying to read phone stuff on a PC. All info on the subject is in those 2 threads, you'll see it! N E way, do that FIRST BEFORE ANYTHING!!
Next, go here: http://forum.xda-developers.com/showthread.php?t=1746682 and install this to your PC. This is the coolest thing ever to get you backed up, rooted, flashed, whatever. It's called the "Snapdragon Toolkit" I cannot begin to say enough about it! It does EVERYTHING you need - installs the correct drivers, roots, unroots, flashes ROMs, gives u ClockworkMod Recovery AND Odin, and also gives you a full perfect backup - Nandroid backup for CM, .tar file for ODIN - of your stock firmware to keep on your PC in case you run into an issue or just decide to go back to stock. Also provides a walk-thru for resetting the flash counter back to zero using an app called Triangle Away by Chainfire!! It gets u into download mode, roots, gives you Superuser, busybox, CWM, all necessary root stuff, and reboots your phone all automatically in just a quick click! You might have read secure vs insecure kernels - gives you the choice. Insecure leaves you rooted. You can also use it to just kind of temp-root to do something that like say, requires ADB (which requires you to be rooted to use) Do it thru the toolkit, and it will get you (for instance for adb access) the insecure kernel alone, temporarily, until you're done with your task. You can do each thing separately like that or everything all at once. His thread, as well as inside the toolkit itself, when you open it on your PC, gives you total kindergarten instructions and explanations for each thing it does. I have never seen a faster, simpler, more user-friendly program for getting these things done - and all in one place! So get that, and per the instructions, open it and install the drivers 1st before plugging in your phone with ur USB. You probably have the right drivers already, but just in case there are extra drivers there needed for the program or anything it does, I'd go ahead and install them. It'll then open a window that looks old DOS command-line like, and will ask which model you have. Every time you're making any choice in the program, you'll be typing your answer at the bottom of the screen and hitting "enter" to submit. Type the number 3, it's the one for T-Mo T999 UVALEM, and hit enter. It then displays the menu with the list of all the options. You can plug in to be sure the phone's detected, and check it by looking at the top of the window; it'll show it under "List of devices attached." If you do what I did, which was the all-at-once option, you'll hit the number 2 and enter for thr rooting options menu, then 3, enter to choose all-in-one and follow the on-screen instructions for when to plug in the phone and such.
To simplify things further, so you can save some time, I've got all the files you need already, to do your IMEI backup, stock firmware backup,(the Nandroid copy of the firmware and the .tar ODIN copy), the drivers, the most recent ClockworkMod Touch and ODIN files, the Toolkit, and all the .apk files of the apps that are safe to remove from the original firmware if you want that. I didn't remove all of these, for the same reason I haven't flashed AOKP or CM9/CM10 yet; I'm not sure I want to lose the new Samsung stuff like SVoice and the motion features. It's a list others comprised, actually probably really outdated, containing the ones confirmed safe to remove. I just kept in case I wanted any of 'em back! I can personally confirm all the T-Mobile ones, ChatOn, Flipboard, all the Yahoo stuff, self, factory and LCD tests, Samsung's Media Hub, Game Hub, SSuggest, and More Services, Google's Books, Music, TV/Movies, Talk, and Google+(Plus One), Amazon, Polaris Viewer, Facebook SMS, and the system Music and Video apps. I say probably outdated cuz I'm sure the Maps from Google and Samsung, the Cloud sync apps from them all, and the Email apps, for example, are all fine to go too, and probably verified by now. (I mean seriously, do I need Samsung, T-Mo, Google+, GMail, Dropbox, Sugarsync, AND Facebook ALL syncing my stuff?! JEEZUSS!!!) Anyway, all the files are in my dropbox here:
https://www.dropbox.com/sh/8f2wjlz1enkb8wp/saTe7MW0fE
There's also a way to flash CWM Touch Recovery without having to pay for Rom Manager Premium and without tripping the flash counter in there with instructions if you want it, but you have to be ok with entering command line script with adb or a terminal emulator. I just used the Triangle Away app, worked perfect!
Whew! What a novel, huh?! Just wanted to be sure I was thorough so you or anyone reading has specifics so there are no problems for you! I honestly didn't have a single hiccup, and all of it took less time than it's probably gonna take u to read this post! Have fun!
https://www.androidroot.us.com/how-to-root-lg-g4/
I stumbled on this when I googled the status on our root. I don't think it's real, but could it be?
If this is a stupid question/ thread please delete
prochargedls2 said:
https://www.androidroot.us.com/how-to-root-lg-g4/
I stumbled on this when I googled the status on our root. I don't think it's real, but could it be?
If this is a stupid question/ thread please delete
Click to expand...
Click to collapse
ugh, really? This (and other similar sites) have been brought up before. Unless a Dev releases it on HERE or mentions about where he will release it on HERE, IGNORE THEM.
Give it a shot and report back.
Gonna run the .exe in a virtual machine to see what happens.
https://www.androidroot.us.com/how-to-root-samsung-galaxy-s7/
it seems like they cracked S7 already. Wonderful. *pun intended*
Yeah, I stumbled upon bogus sites like those back when I was trying to see if anybody ever rooted an Asus Fonepad 8. You know if someone rooted a relatively obscure device like that, there would also be a thread about it here.
For all of those that "stumble" upon this "root" method......don't post a question on if it works, just try it and see if it works......simply put, the Top Devs that have achieved root and unlocking bootloaders on various devices have not come up with a stable method as of yet, one of them does this type of work for a living, why would you think some third party site is able to crank out a root method on a device that just became available to the public and claims to have root for devices that do not exist yet??????????
Clearly, it will fail and will ask you to pay a fee for professional technical remote support. Then it will tell you they can not help and there is no refund.
Remember this, Root is NOT for everyone.
oneclickroot review
https://review.easycounter.com/oneclickroot.com
Root exploit was found by devs but it is dangerous. They are currently looking for other methods. Fortunately since those devs *can* root, they can dive deeper into the paritions and system to look for it. Easier to find a key inside a house then standing outside the gate.
Fortunately the LG phones are pretty solid and I personally need to change nothing. Outside of Xposed for Statusbar tweaks and themes, it is fine.
Full root..... Whatever. I want unlocked boot.
No, this is a scam/garbage...don't do it, won't work.
player911 said:
Root exploit was found by devs but it is dangerous. They are currently looking for other methods. Fortunately since those devs *can* root, they can dive deeper into the paritions and system to look for it. Easier to find a key inside a house then standing outside the gate.
Fortunately the LG phones are pretty solid and I personally need to change nothing. Outside of Xposed for Statusbar tweaks and themes, it is fine.
Click to expand...
Click to collapse
I agree. First LG phone for me. Previous devices were Samsung dating back to S2 all the way through S5. Felt that the removable battery and SD were too important to me to go with S6. Thus far, I'm much more impressed with the LG UI than Touchwiz. It's good without root. Could be great with it. Only two things I would use root for on this device. All of the ads are driving me nuts (short drive) and I really want to regain unlimited tethering. Fortunately, have T-Mobile so at least have 5 gb of tethering.
Have ur Pay Pal rdy LG4 owner's gonna be first to pay for su access when it does release supposedly.
What's the angle of this website? Do they hijack your phone and make you pay?
Dozenboy0012 said:
Have ur Pay Pal rdy LG4 owner's gonna be first to pay for su access when it does release supposedly.
Click to expand...
Click to collapse
When is that happening?
Sent from my SM-G920T
I just bought a new (used) Note 4. It is fresh, stock, BOB7.
If I root, install recovery, and install a new rom, I figure it will trip Knox and turn it "custom".
My question - is it possible after that to return to out-of-the-box-stock? Do I have to take an image of the current config or something?
Thanks!
Mike
resarfekim said:
I just bought a new (used) Note 4. It is fresh, stock, BOB7.
If I root, install recovery, and install a new rom, I figure it will trip Knox and turn it "custom".
My question - is it possible after that to return to out-of-the-box-stock? Do I have to take an image of the current config or something?
Thanks!
Mike
Click to expand...
Click to collapse
Yes. You can odin the stock ob7 tar and the phone will be as out of the box but of course Knox will still be tripped.
Get the stock tar here in the OP :
http://forum.xda-developers.com/showthread.php?t=2944867
Full instructions are there also.
jhill110 said:
Yes. You can odin the stock ob7 tar and the phone will be as out of the box but of course Knox will still be tripped.
Get the stock tar here in the OP :
http://forum.xda-developers.com/showthread.php?t=2944867
Full instructions are there also.
Click to expand...
Click to collapse
Wow, you Note 4 guys are quick. Thanks for the reply!
So, not that it matters too much, but there is no way to retain/restore the Knox counter then? On my Note 2, there was a flashable back-to-stock image.
resarfekim said:
Wow, you Note 4 guys are quick. Thanks for the reply!
So, not that it matters too much, but there is no way to retain/restore the Knox counter then? On my Note 2, there was a flashable back-to-stock image.
Click to expand...
Click to collapse
Not at this time and unlikely in the future.
jhill110 said:
Not at this time and unlikely in the future.
Click to expand...
Click to collapse
Wasnt there talk in the past, forgot who or what thread it was in/about and it was stated that after the repair center gave them their phone back the knox-counter was reset to 0x0 ?
Ive seen many mentions of xda users in this forum(N910P) of working at sprint stores, if not that, working in the repair center. With the FUSE counter itself being an issue and the Signature also being an issue, i wonder the validity of that claim(counter reset), let alone if anyone who claims to work at sprint, could provide feedback on that claim, which at the time, there was none and yet to be.
And the surprising jump in members alone from the last year and a half to current date(wasnt it like 5.5 mil and now its sitting at a cool 6.5 mil) no telling how many Samsung employees probably just sit and search to counter hurdles that have been leaped, only to have updates, like OE1, magically and inconveniently push out updates thwarting what devs have accomplished.
xxSTARBUCKSxx said:
Wasnt there talk in the past, forgot who or what thread it was in/about and it was stated that after the repair center gave them their phone back the knox-counter was reset to 0x0 ?
Ive seen many mentions of xda users in this forum(N910P) of working at sprint stores, if not that, working in the repair center. With the FUSE counter itself being an issue and the Signature also being an issue, i wonder the validity of that claim(counter reset), let alone if anyone who claims to work at sprint, could provide feedback on that claim, which at the time, there was none and yet to be.
And the surprising jump in members alone from the last year and a half to current date(wasnt it like 5.5 mil and now its sitting at a cool 6.5 mil) no telling how many Samsung employees probably just sit and search to counter hurdles that have been leaped, only to have updates, like OE1, magically and inconveniently push out updates thwarting what devs have accomplished.
Click to expand...
Click to collapse
Well. I had run across a tmo thread that had posts stating phones had been returned with the Knox bit reset. There was a guy posting in that thread saying he worked out front at a Samsung authorized repair joint and had techs tell him the bit can be restored. Others elsewhere thought it would take replacing the mother board to achieve that. Bottom line I took from all that was samsung will repair a clearly bad hardware issue even with the bit tripped. Of course a lot of legend in their own mind types put the pupu on that but it has happened.
And yes, Samsung has been engaged in a we'll show you thing. Now I'm probably going to catch a lot of flack for saying this but I'm going to.
Most of the development for Android devices comes from the US... I think it's very likely the Koreans (samsung) hate that and take it as a challenge to show how much better/smarter they are than we.
Just my non insider opinion...
jhill110 said:
Well. I had run across a tmo thread that had posts stating phones had been returned with the Knox bit reset. There was a guy posting in that thread saying he worked out front at a Samsung authorized repair joint and had techs tell him the bit can be restored. Others elsewhere thought it would take replacing the mother board to achieve that. Bottom line I took from all that was samsung will repair a clearly bad hardware issue even with the bit tripped. Of course a lot of legend in their own mind types put the pupu on that but it has happened.
And yes, Samsung has been engaged in a we'll show you thing. Now I'm probably going to catch a lot of flack for saying this but I'm going to.
Most of the development for Android devices comes from the US... I think it's very likely the Koreans (samsung) hate that and take it as a challenge to show how much better/smarter they are than we.
Just my non insider opinion...
Click to expand...
Click to collapse
Yep, TW, Tizen, Knox, KnoxII, menu/recents button. Need I say more: Samsung/Galaxy app store, Milk, Chrome plug-in, security updates. Google has a rocky relationship with Samsung. One minute they're slapping then on the wrist, the next minute they're defending them in court against Apple.
All the while Samsung is copying Google to be their own standalone mobile platform. They may succeed eventually.
Competition is good. Truth is Samsung needs Google right now with its dwindling sales.
When the S5 came out with the menu switch from recents back to menu as an option, I was with Samsung on that but the Note 4 seemed to be a wink at Google like Samsung was more willing to do things Google's way. That gave us the silly white background menus and removed the menu/recents option in settings. What a cave in! Wrong move giving us KnoxII with non-user trip reset and this ugly UI. I hear they messed with the S5 on updates too. Yuck Samsung!
Sent from my SM-N910P using Tapatalk
Yes... The awful "material" white background, so retro low tech, so dos ansi... I was one very happy user when @tx_dbs_tx came with the dark mod... It wasn't perfect but it was what I preferred.