This thread acts like a index to find the threads that were important and got lost in all the “junk” people keep creating, if you feel something is missing just say so and ill update.
I would also take this chance to make a request to the people that just create threads to be noticed or to be the “first” or whatever other $#%T& reason , that if you create a thread you keep it and you maintain it.
What do I mean by maintaining it ? Don’t abandon it and keep the info inside updated in the first post..
How to:[FONT="]
[Noob Proof Video Guide] How to Root Samsung Galaxy S III i9300[/FONT]
References:
[REF][INFO][R&D] "Secret Codes" and other hidden features
[REF] Stock Firmware Details Listing
Triangle Away Tool
Analysis/Discussion:[FONT="]
Official Sound Quality thread[/FONT][FONT="]
Battery time[/FONT][FONT="]
Actual Ram Available[/FONT][FONT="]
VIDEO ~ Post examples of your videos here[/FONT][FONT="]
CAMERA | Post photos taken with you S3 here![/FONT]
[FONT="]All new games reviews for Galaxy S 3[/FONT]
Known Issues/Troubleshooting/Fixes:
[INDEX]Troubleshooting & Issue Tracking
Galaxy S3 Display Problem! A bit pink tint confirmed ...[FONT="]
[/FONT]Known Faults/Issues
*reserved for future use*
Dear all,
As you may know, there is no section in the XDA community board dedicated to the SGH-I757M model. This phone is NOT the same as the Galaxy S2 I19100, and newbies may damage their phone by installing a ROM, kernel..etc that was not designed to run for their phone. Other Galaxy S2 users may also harm their phone by thinking because the SGH-I757M stuff is posted in their forum, they have the green light to proceed.
Another version of the galaxy s2, the AT & T skyrocket have been able to have their own forum.
I understand that the SGH-I757M fanbase isn't as large as many other phone models, but we have active dev and testers willing to give their support. Bell has sold thousands of these models, and it is continuously being featured in their website. I believe we would have even more supporters if people knew where to locate us. As of now, the only way to view things for the SGH-I757M model is using the search function.
I think the moderator wants to know if its worth opening a forum for a phone that is not widely use.
Tell them what you think, show you support by signing the petition (you may also add other reason(s) for support in the comment)
http://www.ipetitions.com/petition/i757m-/
Note: I chose not to include a poll because it can be vague, whereas a petition is more explicit and accurate.
I signed it! need more supporters for this phone.
I have purchased a phone from a private individual that appears to be a brand spanking new Samsung Galaxy S4. What ROM would you recommend? Currently I am running M.O.A.R. ROM for my SG3 phone at this time. I really prefer not to have a slimmed down ROM but one that adds more control and features like MOAR but still has the stock appearance otherwise.
Flash them all and find out. Do your research. So you know Verizon Roms work on sprint. Just have to take a few extra steps.
Sent from my SPH-L720 using Tapatalk
I am asking what is a ROM that has added features with nothing removed that is pretty much stock. In other words a stock ROM that has added battery tweaks, volume tweaks, wifi hotspot, in call recorder, and other additional features but without removing anything. I tried to do a search but unlike SG3 none really describe themselves like this. I had two choices in SG3 the People's ROM and M.O.A.R.
XDA is a development site not a support site. As such members are expected to do the research, read through the development threads and decide what is BEST for them. The only results that would be posted here are what each member has found to be BEST for them by experimentation based on their phone/usage/setup/apps/signal strength. Please take the time to read through those development threads to learn all about the software you are about to drastically alter your very expensive device with.
Sorry for the inconvenience and thank you for your cooperation.
EFM
Have a great day!
Hello everyone,
most of you probably don't know me since I did not develop for Samsung devices for quite some time now.
I would be interested in aiding the Exynos 5420 development scene (in particular on the Galaxy Note 10.1) and prepare a custom Android distribution for it (Team EOS 5.0 - Lollipop).
I can get all the required drivers and binaries I need for development, since most of it is open source luckily.
And the Nexus 10 (manta) can still be used as reference for many things.
All I need is a development device to debug on.
It is particularly important that this is the Galaxy Note 10.1 EXYNOS (WiFi-only variant), and not the LTE (Qualcomm) variant.
I created this thread to ask whether someone has a spare device lying around, maybe because of the little development on Exynos 5 devices, or if people would be willing to donate a device (I'm a university student and unfortunately can not afford the full price for a new device. I'm willing to dive into the Exynos development scene and spend time on this device though, including extensive debugging).
You can leave a reply in this thread or contact me on gmail: [email protected]
I have a better idea. Sending device is a problem. But we can donate to you, and then u can purchase P600 or P601 on SWAPA or EBAY. not new but fully working
I would be glad to see working AOSP/MAHDI or other ROMs runnig on my P601
Yeah, that was the initial idea.
I would pay any shipping costs or parts of a device (a used one is perfectly fine).
The issue I see is that probably not enough people willing to donate enough small amounts of money, hence I asked if someone had a spare device I could buy or pay the shipping costs.
RaymanFX said:
Yeah, that was the initial idea.
I would pay any shipping costs or parts of a device (a used one is perfectly fine).
The issue I see is that probably not enough people willing to donate enough small amounts of money, hence I asked if someone had a spare device I could buy or pay the shipping costs.
Click to expand...
Click to collapse
I think it would be better to ask for donations because there is not a lot of people here although it would be hard. There have been previous instances where at least 2 different devs raised donations for this device before stopping development shortly after so people do have some trust issues. It would take a while but i'm sure people would donate considering you are offering an AOSP experience. If you renamed this thread to something like: Donations needed for new device- AOSP rom development. Then it would catch a lot of eyes because that's what a lot of people want The question remains whether people would actually donate. The average cost for you would be around 250-300 euros I think. That means you would need around 28 people (10 each). Whatever way you decide to go down, I wish you luck and I look forward to any rom developments if you do manage to get the device :good:
You seem to have quite a respectable history (in both Rom & kernel developement), so I think getting enough donations should be doable (and I'd be willing to donate a few bucks myself)
But I do have a few questions:
1) What about warranty? Some devs who had collected donations for a (used) device, have bricked their devices -> no more developement
Therefore P600 owners might be scared / hard to convince
2) what exactly is "Team EOS 5.0" and what makes it different from other Roms? Would you perhaps consider developing other Roms / kernels as well? (like porting over PA for example?)
Or would you maybe consider becoming the official P600 CyanogenMod maintainer (since we don't have one, yet)? [<- I think this one would be reason enough to donate]
Last but not least:
You could ask one of the XDA members who managed the previous donation-collections for help (they have successfully done it before, so they might be able to do it again :fingers-crossed: )
PS: The Note 10.1 2014 is great for college, trust me - I'm a student, too . All you need is the Papyrus-App from the Play Store.
Thank you two for your reasonable thoughts.
I think the main reason why the previous developers stopped developing for this device rather quickly is the Exynos chip.
The main difference between me and anyone else is (or so I believe) the fact that I am especially interested in developing for the Exynos 5420 chip and the drivers for it (mainly from the Insignal forum source).
As far as bricked devices, I can say I had a Samsung device before, and as long as the bootloader is unlockable and access to ODIN (The firmware flashing tool) is granted, a hard brick is rather hard to achieve. I see little risk here, and I assume my previous development experience will prevent me from making major mistakes in that regard.
A new device would cost me approximately 350€, so if we could collect about 300$ with donations (which would equal something like 270€), I'd pay the remaining costs.
People are of course free to check my development history and/or references first and see if they think I would benefit the aosp development scene for this device.
The ROM I mentioned (Team EOS 5.0 lollipop) is essentially AOSP 5.0 with selected features that we code ourselves, like EOS Weather, or the NX gesture interface.
If people however see the need for an official CM maintainer, I'd be happy to become this as well, all I need is a device to debug and develop on, I'd be willing to spend the time to officially maintain this device.
Other developers and/or contributors should also expect support from me in areas of kernel development or AOSP custom ROM development. I believe in 'sharing is caring', so all my knowledge and achievements on this device shall benefit the community.
If some of you could maybe contact the people who raised donations before, I'd be thankful and gratious for the support. All donations will be listed here and the whole process shall be as transparent as possible.
RaymanFX said:
Thank you two for your reasonable thoughts.
I think the main reason why the previous developers stopped developing for this device rather quickly is the Exynos chip.
The main difference between me and anyone else is (or so I believe) the fact that I am especially interested in developing for the Exynos 5420 chip and the drivers for it (mainly from the Insignal forum source).
As far as bricked devices, I can say I had a Samsung device before, and as long as the bootloader is unlockable and access to ODIN (The firmware flashing tool) is granted, a hard brick is rather hard to achieve. I see little risk here, and I assume my previous development experience will prevent me from making major mistakes in that regard.
A new device would cost me approximately 350€, so if we could collect about 300$ with donations (which would equal something like 270€), I'd pay the remaining costs.
People are of course free to check my development history and/or references first and see if they think I would benefit the aosp development scene for this device.
The ROM I mentioned (Team EOS 5.0 lollipop) is essentially AOSP 5.0 with selected features that we code ourselves, like EOS Weather, or the NX gesture interface.
If people however see the need for an official CM maintainer, I'd be happy to become this as well, all I need is a device to debug and develop on, I'd be willing to spend the time to officially maintain this device.
Other developers and/or contributors should also expect support from me in areas of kernel development or AOSP custom ROM development. I believe in 'sharing is caring', so all my knowledge and achievements on this device shall benefit the community.
If some of you could maybe contact the people who raised donations before, I'd be thankful and gratious for the support. All donations will be listed here and the whole process shall be as transparent as possible.
Click to expand...
Click to collapse
Hi. Here's the most recent donation thread which was successful :good:
http://forum.xda-developers.com/showthread.php?t=2742793
I don't see why another thread is needed though. I don't mind opening one up for you but you might as well use this one if you just rename it and state your intentions in the op.
22sl22 said:
Hi. Here's the most recent donation thread which was successful :good:
http://forum.xda-developers.com/showthread.php?t=2742793
I don't see why another thread is needed though. I don't mind opening one up for you but you might as well use this one if you just rename it and state your intentions in the op.
Click to expand...
Click to collapse
Okay, so if maybe one of you guys, with good contact to the community, could open a new donatiion thread to collect the ~300$, I'd be grateful.
Or maybe @drrasii could chime in here and edit his first donation thread and link here as a reference to let people know what I want to do.
As I said above, I'd be willing to become the official CM maintainer, or if CM refuses to accept this for some reason, I'd host the needed sources for the device on my personal GitHub and keep it updated so people can build whatever ROM they want.
Of course, the first goal would be to get Lollipop running on this tablet, which I'd start with as soon as the device is ordered/has arrived.
Hey guys. That donation thread I started a while ago was on a whim cause I wanted Hyperdrive by sbreen on my Note. Was lucky enough to have him commit and get enough people chipping in for the tablet which was met with success. I'm by no means a great organizer or somebody with tight connections here on XDA . Probably would be best if someone who wanted to head it up would start a new thread stating the case.
Best of luck!
RaymanFX said:
Okay, so if maybe one of you guys, with good contact to the community, could open a new donatiion thread to collect the ~300$, I'd be grateful.
Or maybe @drrasii could chime in here and edit his first donation thread and link here as a reference to let people know what I want to do.
As I said above, I'd be willing to become the official CM maintainer, or if CM refuses to accept this for some reason, I'd host the needed sources for the device on my personal GitHub and keep it updated so people can build whatever ROM they want.
Of course, the first goal would be to get Lollipop running on this tablet, which I'd start with as soon as the device is ordered/has arrived.
Click to expand...
Click to collapse
Thanks for the quick answer.
Could one of you guys (@22sl22 or @r4yN) then open a new donation thread and explain a bit about this thread and my plans?
If we manage to handle this process rather quickly, people should be able to enjoy L on this tablet soon hopefully.
RaymanFX said:
Thanks for the quick answer.
Could one of you guys (@22sl22 or @r4yN) then open a new donation thread and explain a bit about this thread and my plans?
If we manage to handle this process rather quickly, people should be able to enjoy L on this tablet soon hopefully.
Click to expand...
Click to collapse
Sure, i'll open one now :good:
I'll also post a message in here after the new thread has been created so that people know http://forum.xda-developers.com/galaxy-note-10-2014/general/rumours-plans-to-android-5-0-t2861225
EDIT: before I open the thread, how much do you actually need? $300 is about 240 Euros, not 270 so we will need a bit more, say $350, would that be OK?
Thank you very much.
Actually, 300$ (240$) is enough, I'd be willing to pay the other 100€ myself if it needs to be.
I want to get started rather quickly and have L running on this device, so I'd order the device as soon as the 300$ are collected.
Why a P600 model and not the P601 model?
The p601 to develop is exactly the same from p600 plus the phone side.
Sent from my SM-P601 using XDA Free mobile app
Why the delay? Here are the first 10 €!
RaymanFX said:
Thank you very much.
Actually, 300$ (240$) is enough, I'd be willing to pay the other 100€ myself if it needs to be.
I want to get started rather quickly and have L running on this device, so I'd order the device as soon as the 300$ are collected.
Click to expand...
Click to collapse
Hi RaymanFX!
Glad to see that a real dev wants to take our device and port CM11 for us.
I do not make many words, but simply push the first $ 12.12 to you.
That's the current rates for 10, -€.
Hope it works as good as for sbreen (dev from HyperdriveRom) and many people jumps like lemmings behind me. :good: Haha!
Hope also we get the money quickly together and will try to continue to encourage people to make a small donation.
10,-€
Transaktionscode:
7R473626855605042
You also get a short pm
Hey RaymanFX, excited for asop 5.0 but curious about some of the stock features that make this tablet. Is there any way to preserve multi window support or s-pen features ?
I've opened this thread so that there can be a CLEAN thread for devs to discuss the development of a kernel mod to the Sprint userdebug firmware to allow a hybrid T-mo/Sprint ROM to be built that preserves T-Mo features such a Wi-Fi Calling and VoLTE.
If you are not a dev currently contributing to this particular effort, please refrain from posting in this thread and use the "ALL THINGS ROOT..." thread here for all other root related discussion.
See Post #2 for ORDER OF EVENTS, CURRENT STATUS AND REQUEST FOR HELP.
See Post #3 for a compiled summary of everything we know and have tried as of this moment.
Let me know if there is anything that you think I should add to this post that might help keep this process on track.
I believe this goal to be attainable but it will likely require some teamwork and collective imagination.
YOU CAN DO IT! :good:
Click to expand...
Click to collapse
ORDER OF EVENTS, CURRENT STATUS AND REQUEST FOR HELP:
1. T-Mo Note 7 ships with locked bootloader.
2. freeza manages to supply Sprint Note 7 users with a userdebug firmware that allows root access to be gained on the N930P
3. ethanscooter posts the following info in which he shares his experience that the N930P userdebug flashes normally to the N930T, allows boot and root:
Here's how you do it: Follow the EXACT SAME GUIDE FROM THE SPRINT NOTE 7 SECTION!
Click to expand...
Click to collapse
http://forum.xda-developers.com/spri...alaxy-t3447202
To get LTE to work again just add the T-Mobile APN (not that hard).
Also, you might want to freeze all the "Sprint OMADM" packages with titanium backup once you're rooted (will cause less of a hassle every time you boot. I understand the devs in the "all things root" thread are holding this from you because they want to fix WiFi calling but I think giving you root at all will tie you over for now. Also, I'm having problems downloading the gear VR apps with this so it's related to following this tutorial.
Thank you so much to the developers who made this possible for the Sprint note 7 and for everyone who brought this to the other variants (the T-Mobile note 7 was the easiest imo). It's a little funny to think that this whole time it was this easy and we could've been rooted all along. *If you really need the T-Mobile firmware rooted so you can enjoy wifi calling I've been working on something for a few hours but it's not ready.*
T-Mobile APN: https://bestmvno.com/apn-settings/t-...-apn-settings/
Click to expand...
Click to collapse
5. The loss of WI-Fi Calling and VoLTE as well as other T-Mo specific customizations (Visual Voicemail?) is identified as a major drawback of using the Sprint fw.Edit: Other issues as reported so far: Samsung Apps cannot be updated, any Bluetooth pairings that are made must be re-paired after every reboot 6. A T-Mobile engineering build is being sought to no avail as of yet. This would resolve the primary issue by allowing us to use a T-Mobile FW with the appropriate T-Mobile modifications for WiFi Calling and VoLTE. (Not sure yet what might be causing the issues with Samsung apps and Bluetooth)
7. In the absence of a Tmo eng boot, several devs are organizing to find a solution. The current idea is to dd a modded kernel after flashing the Sprint fw which would (hypothetically) remove the validation checks that prevent flashing modified images. Then build a deodexed T-Mobile build with the modded kernel and su included.
Progress has been somewhat limited up until now. Partially because most devs have been working quietly in their own silos and communicating ideas and knowledge has been a challenge with the previous threads becoming dominated by chatter rather than the facts as they have and are being discovered.
The other hindrance has been that many devs who are keen to work on this issue are without a device such as Rx8Driver and Chainfire.
ATTENTION:
ANYONE THAT IS NOT A DEVELOPER BUT IS LOOKING TO CONTRIBUTE TO THIS EFFORT, PLEASE DONATE TO THE TWO DEVS MENTIONED ABOVE SO THAT THEY CAN HAVE A DEVICE WITH WHICH TO WORK. ALSO, SINCE I KNOW YOU ARE ALL EAGERLY POURING OVER THESE THREADS, KEEP AN EYE OUT FOR OTHER DEVS INTERESTED IN HELPING THAT MAY NEED A DEVICE AND TRY TO HELP THEM GET THEIR HANDS ON ONE.
ANOTHER OTHER WAY TO CONTRIBUTE WOULD, OF COURSE, BE TESTING. BE WARNED THAT NO ONE HERE AT XDA ASSUMES ANY RESPONSIBILITY FOR ANY CODE THAT IS PROVIDED TO TESTERS OR USERS AND BRICKING YOUR DEVICE IS A VERY REAL POSSIBILITY.
THOSE INTERESTED IN TESTING, PLEASE START A SEPARATE THREAD IN DEV SO THAT GUINEA PIGS CAN ADD THEIR NAME TO THE LIST OF WILLING TESTERS. (PLEASE KEEP THAT THREAD SIMPLE AND TO THE POINT)
In Post #3, I will do my best to provide a straight-forward compilation of all we know and have tried as of this moment.
WHAT WE KNOW (OR AT LEAST THINK WE KNOW):
The following is the list of details that we currently know regarding the T-Mobile Samsung Galaxy Note 7 (SM-N930T) and its locked bootloader including concepts, ideas and loosely confirmed information:
FROM CHAINFIRE ON G+ (regarding SU challenges and some work-arounds):
New exploit protections
As isn't uncommon with Samsung, they've built-in some new (and arguably ineffective to actual exploits) protections directly to the kernel code, that cannot be turned off by just modifying the boot image ramdisk.
This time, they've decided to kernel panic in case a 'priviliged' process (uid or gid below or equal to 1000, so this includes root and system processes) creates another process that isn't stored in /system or rootfs. SuperSU itself does this, but so do a great many root apps. Any time this happens: immediate reboot.
I'm not going to elaborate why in my opinion this is a fairly useless protection exploit-wise, but needless to say it is fairly bothersome for the normal root user, which is probably a lot more relevant for the average reader here.
Unfortunately - unlike many of the security features developed by Google - this feature is not easily disabled by modifying initramfs (boot image ramdisk), and requires further trickery to bypass.
Maybe a better bypass is yet to by found, but for the time being, I have resorted to patching the check inside the kernel itself when the systemless SuperSU boot image is created. This prevents the user from needing a custom source-built kernel, but it's questionable how long this hex patch will work. The code that performs this patch is fairly trivial - it may keep working the rest of the Note7's lifetime, or stop working the next update.
In other words, this could end up being resource intensive to support, or not. We don't know yet. We have to wait and see what Samsung is going to do.
Bearer of bad news
We know S and Note development are generally strongly related, so we should assume to see the same 'protections' appear in the S7 sooner or later as well. This is probably the (ugly) way forward.
Workarounds
Aside from the binary/hex patch SuperSU employs (see common/hexpatch inside the ZIP), there are some more ways to get around this protection.
If you're compiling kernels from source, it seems that setting CONFIG_RKP_NS_PROT=n gets rid of these protections. You may want to disable other RKP and TIMA settings as well, but that is the one directly relating to this issue.
This protection also disables itself in recovery mode, so simply copying a boot image with these protections to the recovery partition and rebooting into recovery (which will then just launch Android) will work beautifully as well.
CF-Auto-Root
The test CFARs I have made so far for the Note7 have not worked, so since both TWRP and SuperSU ZIPs are already available for this device, I'm dropping CFAR development until I have a device in-hand.
Click to expand...
Click to collapse
FROM
STILL WORKING ON THIS - NEED TO TAKE A BREAK - FEEL FREE TO BEGIN USING THIS THREAD FOR DEV RELATED DISCUSSION ONLY
REMINDER: See above link to "ALLTHINGS ROOT..." thread for open discussion that is not directly related to solving this issue. Thanks!
Post #4
RESERVED
This is a spectacular thread with solid information and an accurate description of our intentions....i want to state that although i appreciate any efforts made that contribute to obtaining a development device I CANNOT IN GOOD FAITH MAKE ANY PROMISES OF RESULTS NOR CAN I SUPPLY A TIME FRAME SHOULD A DEVICE BECOME AVAILABLE. That said, in time I'll have the device no matter what (assuming i don't just buy an Intl F variant- although that's unlikely since $150 on the barrel head is much more palatable than $900 when i literally just had a baby 4 days ago... plus i work 50hrs a week at my regular job) so i don't want folks to think if they don't contribute I'll never get the device- in fact, honestly if I buy it myself there's even MORE likelihood it'll be a T variant- because i will...
Also, be aware the Chinese model is said to be sd820 as well, and has it's own chances of being unlocked, so when everyone's pitched in to buy myself or Chainfire a device then Samsung releases a Chinese Bootloader we can use that's unlocked and solve all our problems, i don't want a bunch of butt hurt fellow members angry with me because the necessity dried up before i could produce the intended Results. I think @freeza and a few other members who have known me around the forums these past few years will vouch that I'm a Stand Up Dude and truly intend to go as far as reverse engineering the T Bootloader to unlock it. Can I? Idk. Am i knowledgeable enough at this very moment to do it? Probably not. Can i still figure it out? I hope so. Will i brick the device? Good chance. Will i try my best and promise to research and learn whatever is necessary to make it happen? Absolutely.
Those are my terms. If you as an individual reading this don't 100% agree then keep your money in your wallet and wait until i can buy the device myself. That's as straight up as i can be. I'll make another promise. Should anyone donate but the total come up short of obtaining a device before i can on my own, i will leave all the donations in my PayPal and refund everyone's money. Only if enough is gained to buy a device will the money move from PayPal, and then it'll be one transaction to purchase the device using the account. If not enough is collected I'll refund everything that was donated...I'll also agree to prove with screenshots...
So again if you're uncomfortable then DO NOT SEND MONEY.
Thanks to all and i look forward to busting this whole Bootloader open! Or giving it one heck of a try if not!
Sent from my SM-N930F using Tapatalk
Thread moved to General
Thanks for starting something like this gentleman, but as with the bootloader thread, this is not actual development so it belongs in general. Carry on.