Related
the end of august is fast approaching and no update for a few weeks now.. there are rumors of gps fix in the works. and better gps in the african latest august release.. how about a release newer than jm5 thanks.
I read somewhere that the Russian guy who was leaking the FW's got caught and although he didnt get sacked he has been told no more leaks.
alferret said:
I read somewhere that the Russian guy who was leaking the FW's got caught and although he didnt get sacked he has been told no more leaks.
Click to expand...
Click to collapse
hes lucky sammy good job for not sacking him
It's a shame . I don't understand. The samsung just had to win with this situation. Everyone knows that the best beta testers are the people of XDA.
Now what do I do with my life without one (or five) firmware a month to test: '(
Hope it's not true
Actually there is a newer version: The official JM1 which is not to be confused with the inofficial JM1
This Version is said to sport some updates over the most current inofficial 2.1 JM5 build.
There is a trick getting it which involves flashing the phone back to JF3 and then getting an update via Kies by accessing a test mode (done by: Ctrl+Alt+u+p)
There is a german thread visable here: http://www.android-hilfe.de/root-ha...ielle-update-jm1-jetzt-schon-zu-bekommen.html
I for one am sticking to JP3. It's not the smoothest but definatly the most good looking and I am hoping for a new 2.2 build in the near future. The browser is just sooo much better than eclair!
i am sure sammy didnt want any very "young" firmwares to leak to the public. i am sure that we will get a leak by the end of the month, but a pretty much almost ready for launch one. they prolly want to take care of good implementaion of froyo features ( JIT mailnly) before anything goes out, even if leaked.
I am having withdrawal effects from not flashing any firmwares... IT'S BEEN ALMOST 2 WEEKS SINCE MY LAST FLASH! lol I'd never gone so long without a flash since I got the phone. I do have to say that JM5 with the ext2 lag fix works very well and I don't plan on flashing unless I see people getting significant improvements, or a stable froyo firmware. I think Sammy should leak and let us point out the bugs haha, even if it's early builds...
yeah what's with the lack of leaks firmwares seriously with my touch HD I was flashing every other day Not having new firmware to flash is really "unusual" for me. I want firmwares
Someone claims to have upgraded to JM6 through kies. This would be great as it would be the newest official firmware I think.
http://forum.xda-developers.com/showpost.php?p=7743693&postcount=121
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
I'm just curious if anyone else here besides me is still on the ATT 4.1.1 or 4.1.2 only because they are still skeptical about updating or just refuse to accept it, and the reasons why. I feel like I'm the bad guy around here because I refuse to rush and play with the latest toy (Ooops, I mean the 4.3 update).
I'm even reading some of the members, and even some devs here wondering why some people are refusing to update, because you can do just about anything on the new bootloader that you can do on the old ones.
Well, I always thought that us rooters who are non-developers are not suppose to accept OTA updates from our carriers, and should only be flashing the Roms from our developers (good devs by the way). OTAs tend to fix previous issues and attempt to make the phones more secure, but at the same time, create new issues and further lock down the phones.
Look at all the posts around here right now that are just filled with 4.3 issues. One of the most common for example: (I'm having issues, have soft bricked, or just don't like the update?) Is there a way to flash back to complete 4.3 stock so that I can start over? No! And without any official firmware released from AT&T, if something goes wrong with your phone, then all you have to flash is a custom ROM, which I was taught that we should be doing any way, while avoiding the OTAs.
I just want to see here if there is anyone else thinking the same way and why, or is this just going to turn into people who OTA-ed becoming defensive.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
shortydoggg said:
I'm just curious if anyone else here besides me is still on the ATT 4.1.1 or 4.1.2 only because they are still skeptical about updating or just refuse to accept it, and the reasons why. I feel like I'm the bad guy around here because I refuse to rush and play with the latest toy (Ooops, I mean the 4.3 update).
I'm even reading some of the members, and even some devs here wondering why some people are refusing to update, because you can do just about anything on the new bootloader that you can do on the old ones.
Well, I always thought that us rooters who are non-developers are not suppose to accept OTA updates from our carriers, and should only be flashing the Roms from our developers (good devs by the way). OTAs tend to fix previous issues and attempt to make the phones more secure, but at the same time, create new issues and further lock down the phones.
Look at all the posts around here right now that are just filled with 4.3 issues. One of the most common for example: (I'm having issues, have soft bricked, or just don't like the update?) Is there a way to flash back to complete 4.3 stock so that I can start over? No! And without any official firmware released from AT&T, if something goes wrong with your phone, then all you have to flash is a custom ROM, which I was taught that we should be doing any way, while avoiding the OTAs.
I just want to see here if there is anyone else thinking the same way and why, or is this just going to turn into people who OTA-ed becoming defensive.
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
For starters i can't imagine why anyone who is rooted and running a custom ROM would ever dream of installing an official OTA. By the time the carrier's have had time to update their own ROM and distribute the update it will have long been incorporated into most custom ROM's. Point and case is 4.3 (which i have been running thanks to Task650 for many months)...boom all of a sudden you are stuck with a bootloader that you cannot change, or how about the case of the S4's who blindly or unknowing installed an OTA that gives them a locked bootloader that cant be downgraded (in the case of those of us with carriers who are evil bastards). The only case where i would personally find it 'acceptable' to install official OTA's is someone who has no interest in rooting or installing any custom software to their device. Yes the current S3 bootloader is rootable but one day, probably the next (if there is one) update i would imagine it will be locked down like the new devices. Its sad to say but the direction Google seems to be moving all Android devices may end up this way which will be a dark day indeed.
dntesinfrno said:
....Its sad to say but the direction Google seems to be moving all Android devices may end up this way which will be a dark day indeed.
Click to expand...
Click to collapse
I don't think it's Google locking the devices down. It's the manufacturers: Samsung, HTC, Motorola, etc... that are incorporating the locked bootloaders. I may be wrong, but that's the way it seems.
jack man said:
I don't think it's Google locking the devices down. It's the manufacturers: Samsung, HTC, Motorola, etc... that are incorporating the locked bootloaders. I may be wrong, but that's the way it seems.
Click to expand...
Click to collapse
Yes currently its the manufacturers, at the behest of the carriers...hence why att and verizon are locked on the s4 and up samsung devices but not sprint or tmo. I was simply stating that if things continue to go the way they seem to be with googles decisions moving forward with android it could end up that way.
They can lock em down but you know some talented dev will find a way in
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
rumrnr62 said:
They can lock em down but you know some talented dev will find a way in
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
True, but that can take months, and until then, you're stuck.
Can always buy a dev version or a nexus
Sent from my SAMSUNG-SGH-I747 using XDA Premium 4 mobile app
I'll wait until the dev 4.3 rom stable then flash. Not much difference IMO.
ibuddler said:
I'll wait until the dev 4.3 rom stable then flash. Not much difference IMO.
Click to expand...
Click to collapse
Same here.
I wonder if for some reason another toy (Ooops, update) comes to this phone, will the rooters who OTA-ed, and then re-rooted or flashed another ROM (and tripped their new warranty bit counters in the process) be able to receive the new update, or will it be blocked because of the counter increment, and once again, will have to rely on custom ROMs, which they should already be doing?
shortydoggg said:
I'm just curious if anyone else here besides me is still on the ATT 4.1.1 or 4.1.2 only because they are still skeptical about updating or just refuse to accept it, and the reasons why. I feel like I'm the bad guy around here because I refuse to rush and play with the latest toy (Ooops, I mean the 4.3 update).
I'm even reading some of the members, and even some devs here wondering why some people are refusing to update, because you can do just about anything on the new bootloader that you can do on the old ones.
Click to expand...
Click to collapse
...Anything, except flashing back to stock for reflashing purposes or for warranty service or resetting the Knox warranty bit. OTA may also damage resale value, among other downsides.
shortydoggg said:
Well, I always thought that us rooters who are non-developers are not suppose to accept OTA updates from our carriers, and should only be flashing the Roms from our developers (good devs by the way). OTAs tend to fix previous issues and attempt to make the phones more secure, but at the same time, create new issues and further lock down the phones.
Look at all the posts around here right now that are just filled with 4.3 issues. One of the most common for example: (I'm having issues, have soft bricked, or just don't like the update?) Is there a way to flash back to complete 4.3 stock so that I can start over? No! And without any official firmware released from AT&T, if something goes wrong with your phone, then all you have to flash is a custom ROM, which I was taught that we should be doing any way, while avoiding the OTAs.
I just want to see here if there is anyone else thinking the same way and why, or is this just going to turn into people who OTA-ed becoming defensive..
Click to expand...
Click to collapse
There are diverse camps among the rooters & other members here. Through my GS1, GS2 & GS3 I've used mostly debloated stock TW roms; for work, on the road constantly & needing a maximum stable daily driver; like other stock TW enthusiasts.
Apart from user (flashing) errors, the stability, the flexibility & connectivity complaints you cited are what I measured against when deciding to flash a 4.3 rom, kernel & modem from |ROM|Bootloader|Kernel|Modem| AT&T Official 4.3 MJB |24 Nov 2013| .
What designgears, upndwn4par, loserskater & the others have posted on multiple threads I read & reread here before flashing allowed me to attempt the 4.3 upgrade with a solid backout plan & maximum control, reaching my desired result:
Stable, debloated (by me, it's personal) permission edited (using App Ops) battery optimized 4.3 using the same bootloader as on 4.1.2.
The resources exposed in that one thread I linked, plus miles of reading in prep here on XDA showed me how to have the upgrade my way, so even stock a enthusiast can get a first class passage thanks to our devs. Buy them a drink when you can!
I haven't been able to fully take advantage of my rooted phone and I get tired of re reading and trying to use other roms and doing back up and always finding myself clueless and returning here to ask you guys what where the steps by steps guide.
I can't get another phone yet because I have a contract with AT&T and it will take a few more months.
I am using SlimBean rom probably a very old version and I haven't update it yet and well I get many bugs and other issues such as my pho0ne restarting when playing videos on full screen.
Sometimes I feel desperate and just want to restart from scratch and unroot the phone by installing the latest update of the official phone.
So, the phone is practically unscratched and well taken cared if any of you are interested.
Suggestions are welcome.
Asking price? Age of phone?
audit13 said:
Asking price? Age of phone?
Click to expand...
Click to collapse
Make your offer.
Age would be... around 2 years or so...
Harkadenn said:
Make your offer.
Age would be... around 2 years or so...
Click to expand...
Click to collapse
I would except I am in Canada and you're probably in the USA.
Harkadenn said:
I haven't been able to fully take advantage of my rooted phone and I get tired of re reading and trying to use other roms and doing back up and always finding myself clueless and returning here to ask you guys what where the steps by steps guide.
I can't get another phone yet because I have a contract with AT&T and it will take a few more months.
I am using SlimBean rom probably a very old version and I haven't update it yet and well I get many bugs and other issues such as my pho0ne restarting when playing videos on full screen.
Sometimes I feel desperate and just want to restart from scratch and unroot the phone by installing the latest update of the official phone.
So, the phone is practically unscratched and well taken cared if any of you are interested.
Suggestions are welcome.
Click to expand...
Click to collapse
Have you tried going to Swappa.com? You'd probably get a better selling price there than on places like that online auction site. Plus you don't pay any fees and it's the XDA recommended option for buying and selling phones.
Seriously though, you may want to revert to a full stock ROM to fix the performance issues. Reverting to a stock ROM would often let you know if any performance issues are firmware or hardware based as different custom ROMs often come with their peculiar issues.
If anyone gets this update please let us know! I am currently still on "N910AUCU1ANIE" and have not received the update for "XXU1ANJ4". Look forward to see what positive enhancements this has, have read good comments about the positive impact on battery life.
http://www.androidauthority.com/galaxy-note-4-firmware-update-xxu1anj4-536934/
The update mentioned isn't for the AT&T variant. No word on when we will get our update.
That's for T-Mobile variant
Even if we do get an update, there is no way I am applying it. I want root, and don't want to risk any chance that I might miss it.
At Att pace for updates we wont get it until next year and when we do it will mess our phones up.
raiu said:
At Att pace for updates we wont get it until next year and when we do it will mess our phones up.
Click to expand...
Click to collapse
Lol so true
pseudoSequential said:
Even if we do get an update, there is no way I am applying it. I want root, and don't want to risk any chance that I might miss it.
Click to expand...
Click to collapse
You might not have a choice. AT&T is known for force pushing updates to phones and without root you can't stop the OTA push service so you don't really have anything to worry about. Unless you disconnect from the network, you'll eventually get the update without a choice. This happened to a lot of people on the Galaxy S4 when they patched loki. Many went to bed to wake up the next morning with there phone rebooted. Some didn't even notice planning to install loki the next day only to find AT&T pushed the patch to there phone unless you remembered to disable OTA service.