This post details the elimination of the sysscope service, entirely, from the international Note2. Would anyone with more knowledge than myself by able to port to our L900?
I am still working on centering my clock, so acquiring the knowledge to port to our L900 will take some time.
On August 29th at 02:14 my Note2 will become self-aware.
Related
Hey there! This is my first post ever on XDA, and hopefully not my last. I have been flashing ROMs since I bought a Samsung Captivate a couple years ago. I had always heard of the potential risks involved when flashing ROMs, and therefore had taken extreme caution when flashing. However, I eventually became comfortable with the process and took less heed than I should have with my Galaxy SIII AT&T. Long story short, I hard bricked it by installing a ROM meant for the international version of the SIII instead of the AT&T version, like so many other careless souls. After looking around the forums, I found that my only options were to:
1) Have my phone JTAGed by some mobile phone repair service.
2) Cry to Samsung pretending like I know nothing about my phone's demise.
Then I found this instruction manual (Uploaded to this post) describing how to JTAG the Galaxy SIII International version. I was wondering if anyone knew whether or not this manual would apply to the AT&T version of the SIII, as I could not find any post with information on it. Also, is it possible for someone to extract the bootloaders file off his/her AT&T Galaxy SIII and upload it here? If no one can validate whether or not this JTAG process will work on my phone then I will try it and post my results. I would rather not lie to Samsung about my phone's death and I wouldn't mind paying for my stupidity, but I see this as an opportunity to discover a more forgiving solution to such a common blunder. Any help would be greatly appreciated!
Hey guys,
i have a question. Shortly after i got S3 rooted after the 4.3 OTA Update i dropped and cracked the screen on my phone. Has anyone had any luck taking the phone in rooted for hardware replacement?
Or should i unroot prior to going in. The root process i took installed the TWRP recovery. I then removed the knox app as well. i'm not sure if there is a way to reset the KNOX bootloader back to the original state or not so it doesn't have custom set.
Thanks!
There used to be an internal sprint memo floating around this forum, or the Epic4G forum (I think it was the latter) that said that Sprint employees are to recommend against rooting the device but are to treat any device as if it's unrooted.
Of course, that was an old memo and sprint may have changed that policy. But they seem to be less strict on rooted phones, IME.
---------- Post added at 10:57 AM ---------- Previous post was at 10:12 AM ----------
http://www.reddit.com/r/Sprint/comments/1t6nbv/iama_sprint_technical_consultant_ama/ce530ml
toolegit said:
There used to be an internal sprint memo floating around this forum, or the Epic4G forum (I think it was the latter) that said that Sprint employees are to recommend against rooting the device but are to treat any device as if it's unrooted.
Of course, that was an old memo and sprint may have changed that policy. But they seem to be less strict on rooted phones, IME.
---------- Post added at 10:57 AM ---------- Previous post was at 10:12 AM ----------
Thanks, toolegit! i'll try my luck. I do have the stock rom, just custom recovery for rooting.
Click to expand...
Click to collapse
Worse comes to worse, if they do say something about your rooted device , not that day wait 2 or 3 days just to make sure its not obvious , and if you have insurance , call and say you lost it, granted you'll have to pay the deductible , but hey its a new phone and not stuck with a broken one
Sent from my Sprint Galaxy s3 , powered by Zerolemon 7000
Flashed my AT&T White S3 with CWM 6.0.4.7 about 6 months ago. Always had problems with the GPS working sometimes and other times it finds about the location I'm at but the blue circle is about 20 miles in diameter. Sometimes once it would find me then it would no longer track me down on roads. So I'd really love to fix this issue where I can actually use Maps and not get lost with it. The GPS and everything was working fine till I flashed it. Idk if I went wrong down the road because I tried a bunch of different things when flashing. I tried cyanogenmod, but didn't care for it and reverted back to the stock att/samsung version. Tonight I was trying to unroot and completely go back to stock like a brand new phone but can't seem to figure out how to do that. I flashed using this thread, http://forum.xda-developers.com/showthread.php?t=2658486. Still having those GPS issues. No clue why. So can anyone help me fix this GPS issue or completely unroot and put my phone back how it was when I took it out the box?
Report your own post and ask a moderator to move it for you, this forum is for the i9300 only.
boomboomer said:
Report your own post and ask a moderator to move it for you, this forum is for the i9300 only.
Click to expand...
Click to collapse
Sorry for posting in the wrong section! Although I might add that it seems that if I keep the stock version of Google Maps it can locate me perfectly and area is small. If I update, however, that's when the blue circle becomes huge!
GPS fix
This worked for me:
http://forum.xda-developers.com/showthread.php?t=1880810
There are also many threads about loose screws on the back of the phone and tightening them fixed the gps
Loose screws have never been an issue on the T-Mobile S3. Its very closely related to the I747 and uses the same inner casing, unlike Sprint and Verizon models. The best fix I know is linked in the sticky rollup thread in T-Mobile Q&A. Ill post the link in a moment. Seems a lot of AT&T users are needing it recently. You may have a similar thread here, but im not positive.
---------- Post added at 09:24 AM ---------- Previous post was at 09:23 AM ----------
http://forum.xda-developers.com/showthread.php?t=2211690
DocHoliday77 said:
Loose screws have never been an issue on the T-Mobile S3. Its very closely related to the I747 and uses the same inner casing, unlike Sprint and Verizon models. The best fix I know is linked in the sticky rollup thread in T-Mobile Q&A. Ill post the link in a moment. Seems a lot of AT&T users are needing it recently. You may have a similar thread here, but im not positive.
---------- Post added at 09:24 AM ---------- Previous post was at 09:23 AM ----------
http://forum.xda-developers.com/showthread.php?t=2211690
Click to expand...
Click to collapse
Thanks for the help, I don't have the srewedrivers to fit those tiny screws. I used to but I lost it Although I don't think that's the issue. The GPS works fine. I was using it at work after I tried what the other guy said, it worked fine until I got home and as I'm sitting at my computer it has the big 1 mile blue circle. After about 10 mins though it pinpointed me than went back to the big 1 mile circle. However, if I use the stock version of Google Maps, it pinpoints me damn near exactly where I am. So it has to be the app or something. I'd hate to keep it stock, for one it show up in my list of apps to update and the updated version might have better roads and stuff. Idk how to fix this
Did you try the gps fix I linked to? Never caused anyone problems so it cant hurt to try..
Hi,
I just wasted an hour with a samsung chat support trying to make my old S2 to work with sidesync 3.0.
After an hour chatting with a very inept rep closed he chat and began looking somewhere else.
I basically want to be able to control my phone from the computer as demonstrated by SideSync by Samsung. Yet, it looks like I fell on a crack. Version 3.0 claims to be compatible with the S2, but also says is compatible with KITKAT and higher. The latest stock rom from T-Mobile is 4.1.2.
Older versions of SideSync only worked with Samsung PCs apparently so I am stuck in between.
I wondered if anyone one succeeded making this combo work. (SGH-T989 with android 4.1.2 and Windows 7x64 Pro woth SideSync 3.0)
I guess my other choice is to install a custom ROM on my S2. Yet the many time I tried to ROOT it I failed and gave up. (Done it before with other phones and tablets) and that would be a subject for another thread.
Anyway, any input will be appreciated.
Thanks!
I think them listing the S2 was an error, it cleary lists 4.4 as a minimum requirement.
And if it relies on the touchwiz firmware, which is likely, it won't work on non touchwiz roms. (Aka anything above 4.1.2 on the t989.)
You're likely out of luck.
---------- Post added at 04:55 PM ---------- Previous post was at 04:50 PM ----------
Ah, some later made S2 models got official 4.4. Mystery solved.
lleiro said:
Hi
Click to expand...
Click to collapse
Hi - I moved your question thread to the Q&A section where you should have posted it originally - please post in the correct sections - thank you.
hI all
i was downloading the new kitkat update for my n5100 when i read about the many issue in this update and still couldnt find a fix from samsung
so do u advise me to update or stay with jellybean??
If you plan on keeping it unroofed, kitkak will be better with battery life but soon will be better over all with apps. Seems like developers spring into action late Dec through Feb for new devices under the tree. If you root, JB can be tweaked to be very stable and reliable.
Now that í have two devices running both kitkak and BJ, both are rooted' as there is no other way to live with them happily... I can say both are about equal, just JB needs system tweaking, while Miriam needs fixing and proper app builds from Google.
---------- Post added at 08:06 AM ---------- Previous post was at 08:04 AM ----------
If you plan on keeping it unroofed, kitkak will be better with battery life but soon will be better over all with apps. Seems like developers spring into action late Dec through Feb for new devices under the tree. If you root, JB can be tweaked to be very stable and reliable.
Now that í have two devices running both kitkak and BJ, both are rooted' as there is no other way to live with them happily... I can say both are about equal, just JB needs system tweaking, while kitkak needs fixing and proper app builds from Google.
I just heard about bugs in kitkat
is it true?? And the spen bug too
and thnx for replying
I don't know about spend bugs... Never seen it not work in my apps. If you have calibration issues, as what many complain about with all samsungs, just do a calibration.
Yes there are a few bugs with Miriam... Xposed modules will clear up most of them.
Yes, S-Pen went funky on me in 4.4.2; How to Calibrate?
My S-Pen ended up with horrible offset after doing the 4.4.2 update provided by Samsung. I no longer use the pen as a result, which sucks. I keep hoping for an update/fix from Samsung, but will probably eventually root and try custom ROMs that apparently resolve the issue.
In the meantime, gooberdude - you refer to a calibration? Have you done this on a Note 8.0, and if so, how? I've heard it referred to, but have never had any success in finding a way to do any kind of calibration.
-Mike
gooberdude said:
I don't know about spend bugs... Never seen it not work in my apps. If you have calibration issues, as what many complain about with all samsungs, just do a calibration.
Yes there are a few bugs with Miriam... Xposed modules will clear up most of them.
Click to expand...
Click to collapse
To calibrate... Open Shots and create a new note with spend.
Go from the upper corner along the edge of the screen and follow along to the next corner, and so on until you have made it back to where you began. You want to make n outline of your screen corner to corner in straight lines.
You may have to repeat a few times, but once you get the knack of it, it will be easy to perform again if needed.
I have a gorilla glass so depending on angle of spend my view of pixel my be distorted by the thickness of my screen protector. As it is very thick.
Try to keep your spen tip at a 45 to 60 degree angle, as it helps with calibration.
I have already updated my n5100 to 4.4.2 and I have no problems with spen.
the most important issue you will have after updatevto 4.4.2 is that you you will not have full access to the external sd card.
also you will have 4.4.2 bootloader with knox that if you root or ... your device the knox will
be tripped and your warranty will void.
the choice is yours .
It is worth to upgrade only if you are willing to run custom kernel.