Related
Please start a new thread when you put out a new version of your rom.
By the time the second version comes out for the really good roms it's impossible to follow all the issues as there can be upwards of 1000 posts in the thread. Starting at the back doesn't help because of all the "how's your battery life?" posts. Then again, maybe that's the problem.
Anyway, I REALLY appreciate the work you guys do on these roms and kernels. I just wish it were easier to follow the flow of development.
Thanks for listening.
<flame retardant shield UP>
+1 .... i am with you !!!
+1 . Yeah it so annoying to go through thousands of old threads...
Moved to general
Moved? Do the people I'm talking to ever look in "general?"
I support this all the way people always tell everyone to use search but you barely ever get what your looking for..
michaelh99 said:
Please start a new thread when you put out a new version of your rom.
By the time the second version comes out for the really good roms it's impossible to follow all the issues as there can be upwards of 1000 posts in the thread. Starting at the back doesn't help because of all the "how's your battery life?" posts. Then again, maybe that's the problem.
Anyway, I REALLY appreciate the work you guys do on these roms and kernels. I just wish it were easier to follow the flow of development.
Thanks for listening.
<flame retardant shield UP>
Click to expand...
Click to collapse
+100000000
Great suggestion. totally agree.
michaelh99 said:
Moved? Do the people I'm talking to ever look in "general?"
Click to expand...
Click to collapse
Well it doesn't have anything to do with developing..
Although you do make a pretty good point, it is a LOT easier just to update the thread with a new download link & change log.
It would also cut down on a lot of clutter in that section.
If you are running an older version of what that dev posted, you shouldn't post bugs unless it didn't say it was fixed in the newest version of what they posted.
Master™ said:
Well it doesn't have anything to do with developing..
Although you do make a pretty good point, it is a LOT easier just to update the thread with a new download link & change log.
It would also cut down on a lot of clutter in that section.
If you are running an older version of what that dev posted, you shouldn't post bugs unless it didn't say it was fixed in the newest version of what they posted.
Click to expand...
Click to collapse
Master, your thread specifically is almost impossible to follow because of the almost 10,000 posts in it.
The easy fix to your update example above:
1) go to post for last release
2) hit edit
3) Ctrl-A to select all and Ctrl-C to copy
4) Hit Cancel
5) Open new thread and Ctrl-V to paste
6) edit pasted text and hit preview
7) review the post and make corrections as needed
8) hit submit and wait for the flood
T313C0mun1s7 said:
Master, your thread specifically is almost impossible to follow because of the almost 10,000 posts in it.
The easy fix to your update example above:
1) go to post for last release
2) hit edit
3) Ctrl-A to select all and Ctrl-C to copy
4) Hit Cancel
5) Open new thread and Ctrl-V to paste
6) edit pasted text and hit preview
7) review the post and make corrections as needed
8) hit submit and wait for the flood
Click to expand...
Click to collapse
9. Delete the old thread.
I think it's more of a "Let's see whose thread can get the mot posts" type of thing. Because it actually makes little to no sense to update a thread from months ago that is full of non-existent issues and then ask people to search through that thread as if the answer is supposed to jump out at them. Luckily I have given up on trying to read threads.
kangxi said:
9. Delete the old thread.
I think it's more of a "Let's see whose thread can get the mot posts" type of thing. Because it actually makes little to no sense to update a thread from months ago that is full of non-existent issues and then ask people to search through that thread as if the answer is supposed to jump out at them. Luckily I have given up on trying to read threads.
Click to expand...
Click to collapse
Well first, you cannot delete your own threads nor close them.
There is a search button in the threads for a reason also..
I guess it could be a thing to get people into saying what version they are on when they report a bug/ask a question..
Just a thought
I have to say I kinda agree with the OP, although obviously from your point of view its just making work.
I run your Axura 2.1 ROM Master, and was feeling a little lag from it here and there. I was looking for one piece of information... "can I use OCLF with this ROM"... had bad experiences with Voodoo in the past.
Man, it was no mean feat to find this out. Eventually, I put the new Voodoo kernel on my phone and its running flawlessly (utterly love this ROM by the way man. Seriously. Better than anything out there by a royal mile), but it was a hugely frustrating process to figure out whether I had any other options. To get a definitive answer. Just to find something simple.
I've often asked people direct questions in PM, and got no response, or at least an unhelpful one. As a technical guy, but not a developer, any questions I have are usually pretty specific, and not newbie in nature, and finding the answer is a massive problem. One of the biggest hurdles to this is 1000+ post threads.
Sent from my SGH-T959 using XDA App
Master™ said:
Well first, you cannot delete your own threads nor close them.
There is a search button in the threads for a reason also..
I guess it could be a thing to get people into saying what version they are on when they report a bug/ask a question..
Just a thought
Click to expand...
Click to collapse
Personally I think the old threads should remain anyhow. They help to keep the versions separate, not everyone upgrades right away. People should post in the correct thread for their version, but right not this is not possible.
Also, the old, dead thread clean up is not the responsibility of the OP, but of the forum admin. I have owned and run many forums. I have used ikonboard, vBulletin, Invision Power Board, MyBB, Phorum, phpBB, and my favorite Simple Machines Forum. All of them have in the administrative back end the option to cleanup old dead threads with no posts with a set time frame.
Problem is rom gets updated, 300 posts of "OMG Thank You, flashing soon!!!!"
They don't care.. The only thing they care about is getting donations. Higher post conts = more attention = more donations. In summary: they do not care
Sent from my SGH-T959 using XDA App
grennis said:
They don't care.. The only thing they care about is getting donations. Higher post conts = more attention = more donations. In summary: they do not care
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Sorry, gotta call BS on this one. Based on recent events I can guess that you are speaking at least generally if not specifically to Master, and he already addressed (IN THIS VERY THREAD) his thoughts both for and against. In fact so far he has been the ONLY developer to come forward and state he would be willing to do this.
Your statement does not contribute in any way to the discussion at hand, and I personally to not appreciate anyone that posts in running threads just to flamebait and be defamatory. Please check yourself.
I think an easier and better solution exists.
The problem for us the users is that we cannot find which posts relate to which rom version, correct?
The problem for developers if we choose to open a new thread for every release is to follow all 20 threads.
An easy solution would be to have one thread for the rom as it is now, BUT with every update of the rom (and the first page) the developer can add another post with update details at the end of his thread (basically a simple post reply) and put a link to it on the first page in the change log.
This way people viewing the change log will have links to the parts of the thread that discuss that update, while developers won't have 20 threads to maintain.
Sent from my Nexus One using XDA App
Whether you are following 20 threads or the same number of posts in 1 thread the work is the same because you have to reply either way. Also, all versions in 1 thread plus people still using old versions leads to confusion, and confusion equals having to clarify which ultimately means more posts. If you subscribe to the threads and use proper subjects for the thread you should get an e-mail that not only tells you there was a reply, but to which thread version and you can prioritize your replies, ie. Current version I will answer that now, 3 versions back and he can wait until I am done with what I am working on or else he can upgrade. Also since the older threads will get posted to less frequently the chance of multiple posts after the e-mail is less, so if the question is something that was fixed in a newer version you can decide it is not even worth your time to reply. As a developer you can not do that now because there may be many replies after the one that triggered your subscription e-mail that you will not see until you visit the forum.
Trust me, I have run a BUNCH of forums, and 1 thread per version is a better idea for many reasons you have not even thought of yet. If you fully think it out you will realize that it is actually easier to keep track of the 2 or 3 most resent threads people actually pay attention to then try to track the last 2 or 3 versions in 1 thread.
I've run a few big forums too so I do know what im talking about.
With 95% of users upgrade to a newer version of the rom there would be no need to keep the threads for the old roms because no one will write there. But you can't delete them. So instead of having 20 threads with 20 roms, we will have 400 threads for 20 versions of those 20 roms if we follow your idea
Sent from my Nexus One using XDA App
DO:
1) Hate Gingerbread and pester Samsung about official ICS update to Note
2) Google around for best ways to root your device. Specifically check out rootgalaxynote.com for noob-friendly advice and videos
3) Check out in your phone's about settings and note down the kernel version and the ROM version on your device. Also note the manufacturer's official designation of your device (i717, N7000 or i9220 in this case)
4) Realize that what you do to your device is your own responsibility. Samsung and/or XDA and/or your mom won't be there when you are staring at a fancy black brick as a result of the RISKY procedures here. Well, maybe your mom will be there, so be good to her
5) Check which features are and are NOT working in a given ROM before flashing it
6) Be in it for the long haul and be prepared to tinker, adjust, flash, reflash, backup and restore to mold your device to your liking. There is NO ONE SIZE FITS ALL solution to anything
7) Purchase MyBackup Pro and make complete backups of your apps every now and then
8) Develop sufficient proficiency with ClockWork Mod to be able to Nandroid backup before EVERY flashing
9) Go to your local market and check for fallback options in case you lose your phone. Either shortlist the same device (Note) or get some cheaper options (such as dirt-cheap and excellent Galaxy Nexus) shortlisted. Make sure your bank account has the requisite sum before you even think about hitting download mode on your device
10) Keep in mind that for some strange reason, flashing a Note is more complicated and risky than flashing a GS2 which confirms that earlier assumption regarding both devices being largely the same is not that true
11) Keep in mind that NO TWO GADGETS, NO TWO SETUPS and NO TWO CONNECTIONS are the same, even though they might be the SAME model from the same manufacturer. Some might have different memory, or a different radio, or your PC/Laptop might have a few kilobytes missing from the downloaded drivers, or there might be a power surge. Bottom line: following the same steps as another user might NOT give you the same results.
12) Hit search for 'ICS Repack' in any Note ROM forum. That, and the unstable leaked kernels (LP5/LP6) seem to be causing the most cases of bricking of Note while flashing. Avoid ICS repack if you can - I did with good results.
DON'T
1) Think that the ROM creator, or Samsung, or your mom, is in any way responsible for anything bad that happens to your device
2) Flash without ensuring that your kernel is up for it (see (3) above)
3) Skip steps or downloads in a lengthy procedure in hopes that things will work out in the end
4) Backup or restore system apps via MyBackup or Titanium
5) Conclude on the performance of your battery before going thru several charge/recharge cycles
6) Adopt an accusatory tone in your comments
Thanks captain obvious.
someone actually thanked the OP for this list?
panyan said:
someone actually thanked the OP for this list?
Click to expand...
Click to collapse
That's a bad thing why? If the majority of new Note users would actually read lists like these we'd have a lot less 'oh noes' and 'why doesn't this work' threads and posts.
Taking the time to make a list like this shouldnt be rewarded with ****ty remarks like yours or irish-sid's. At least he's trying to contribute something to this community.
DO:
11) Flame OP
Sent from my GT-N7000 using XDA
irish-sid said:
Thanks captain obvious.
Click to expand...
Click to collapse
panyan said:
someone actually thanked the OP for this list?
Click to expand...
Click to collapse
Beretta93 said:
DO:
11) Flame OP
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
you guys are what's wrong with this community and the world in general. zero tolerance for anything. The OP is just trying to be helpful, no need for snide comments, and useless posts unless its helping answer someone's question or making an informative post/thread. If something is misleading, then yes make a post that's letting someone know its misleading, THAT's informative. This may all be obvious, but its all the right information given, and it may help someone that's new here, and even to regular members.
It's a joke come on...
Sent from my GT-N7000 using XDA
fail0verflow - Long-ass dos and don'ts list with not a mention of ICS repack kernel issues, which is THE most important issue for this device right now.
Entropy512 FTW!
Sent from my GT-N7000
Nice list. Problem is: People who really need such info usually don't read or google They prefer to ask the same questions over and over again.
Sent from my rooted Galaxy Note using XDA Premium App
Thanks op.
Why would anyone need to search rootgalaxynote.com to know the best method when everything is here at xda (most of the time those guides are copied from XDA). Don't take me wrong I appreciate your efforts.
It should mention ICS kernel repack issues.
My friend bricked his phone while flashing with Odin.
He had custom power saving plan on his laptop that put it to sleep mode in the middle of flashing process.
You should never leave flashing with PC Odin unattended if you have kids or a nasty dog at home.
Boy124 said:
You should never leave flashing with PC Odin unattended if you have kids or a nasty dog at home.
Click to expand...
Click to collapse
*nods sagely*
Sound advice!
panyan said:
someone actually thanked the OP for this list?
Click to expand...
Click to collapse
Listen, if you go even in a cursory manner around the Galaxy Note ROM forums (esp Stunner) you will plainly see that this guide is badly needed.
And thanks for taking out the time and the effort for that constructive comment.
Boy124 said:
Thanks op.
Why would anyone need to search rootgalaxynote.com to know the best method when everything is here at xda (most of the time those guides are copied from XDA). Don't take me wrong I appreciate your efforts.
It should mention ICS kernel repack issues.
My friend bricked his phone while flashing with Odin.
He had custom power saving plan on his laptop that put it to sleep mode in the middle of flashing process.
You should never leave flashing with PC Odin unattended if you have kids or a nasty dog at home.
Click to expand...
Click to collapse
Many thanks for your support. I intended it to be a general guide leading up to the relevant information in the forums, rather than reproducing the information here. That's why I stressed on people reading all the posts on an entire forum. Reading this would easily lead people to ICS repack related issues, but still I am editing the OP to include a mention.
I plugged rootgalaxynote.com simply because it contains some helpful videos, otherwise I agree that XDA has everything needed.
Oh boy.. look's like I've managed to transgress with several of the items listed.
Is there any advisable way to restore apps + app data (not system data) after a fresh flash? I'm really not crazy about starting from scratch every time. Seems very un-Androidy.
Xephrey said:
Is there any advisable way to restore apps + app data (not system data) after a fresh flash? I'm really not crazy about starting from scratch every time. Seems very un-Androidy.
Click to expand...
Click to collapse
Titanium backup. I advise you to buy the pro version. It's really worth it. You cant have a rooted phone and not have this (that's if you are even rooted).
Sent from my GT-N7000 using xda premium
Oh! He said not to backup or restore -system- apps. I'm retarded. Dunno why I missed that.
I'm keeping a track of how many requests we get relating custom firmware, and from what I'm seeing the user base is not as interested in custom firmware as you might think, which is echoed by this thread (we've shipped 60,000+ units, and less than 10 people have commented in the last month in this thread about getting access to recovery mode).
That doesn't mean that we're shooting the idea down, you need to keep in mind that in terms of priorities this is way down the list as you'd expect from any feature where it's being requested by less than one tenth of one percent of the user-base.
I'm sure @Wajeemba is familiar with CM requests that a very small minority of the user-base are very passionate about, so hopefully you can understand why we're not rushing to work on this.
Click to expand...
Click to collapse
Go to this thread and let them know we want support:
http://forums.ouya.tv/discussion/1380/recovery-mode
Done! The mobile site won't connect to the create account page for me, so I logged in with Google. Didn't want to do that, but I wanted to be sure I made the request. I hope it's cool with you that I copied this post to another forum.
Sent from my SCH-I535 using Tapatalk 2
TadeoNYC said:
Done! The mobile site won't connect to the create account page for me, so I logged in with Google. Didn't want to do that, but I wanted to be sure I made the request. I hope it's cool with you that I copied this post to another forum.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks, the more the better!
I posted as well... I hope the admin/mod replies to my post though
Sent from my Nexus 10 using Tapatalk HD
Vinny75 said:
Thanks, the more the better!
Click to expand...
Click to collapse
I figured as much. Could this be moved to the general section? If there is a big groundswell of support it should make a better impact than posts trickling in over a few days.
Sent from my SCH-I535 using Tapatalk 2
Update: this what OUYA thinks of its customer's requests...
Posted by alsutton on http://ouyaforum.com/showthread.php?3193-Let-OUYA-know-we-NEED-to-be-able-to-boot-to-recovery
and a I monitor this forum as well, so thanks for the heads up you're trying to artificially raise the numbers beyond the level of people who'd normally ask for it.
My *personal* view (that's mine, not OUYAs) is that you don't NEED to be able to boot to recovery, you LIKE access to it. The system works fine without being able to boot to recovery, many people use it without even knowing what recovery is, so it's not needed to use your OUYA. A number of people have managed to make their device unbootable with just root access by experimenting with things like compiling new kernels, then expect OUYA to fix them. Personally I think this is a bit unreasonable (if you started changing parts of the engine in a car and it broke down would you go back to the dealership?), and I'm sure most of the user-base would like support focusing on things other than user created problems (yes, shipping, we know).
So just a "lets all post bomb -->this<-- thread" isn't going to get it raised up the priority list. All I have to do now is factor in the number of "me too posts" from people who may not actually know what they're asking for.
Click to expand...
Click to collapse
This is ridiculous and insulting.
Copied from Ouya's Google+ page.......
OUYA
Shared publicly *-* Jul 23, 2012
*
Hey +OUYA* devs! Don't worry about rooting your device (or purchasing the pre-rooted device). We will provide builds and instructions that can be used to restore the device to 'unrooted' factory state!
Official response to my support ticket:
The OUYA is based on Android which makes it far more open than other consoles, and an OUYA gives your root access which gives you access to far more access than most Android devices. We currently do not provide instructions on how to access recovery mode, and I can not comment on whether or not that may change in the future.
OUYA
Click to expand...
Click to collapse
Post-Bombing isn't helping anyone.
If someone's really interested in that matter, he'll find answers for his questions in this forum!
4rz0 said:
Post-Bombing isn't helping anyone.
If someone's really interested in that matter, he'll find answers for his questions in this forum!
Click to expand...
Click to collapse
These posts are not located in this forum and are relevant to the topic. thanks, though.
Post bombing either forum isn't helpful...
Sent from my SAMSUNG-SGH-I317 using xda premium
Voice your opinions here. I think it more clearly explains the situation we are working with.
s/with/against
http://www.reddit.com/r/ouya/comments/1gk0km/ouya_advertised_as_a_hackers_welcome_device_quite/
I was all set to buy an Ouya, but after reading this forum I'm not so sure. Ouya doesn't sound like a company I want to support. What do you guys think about the Mad Catz console coming out. I want Ouya's hardware not their restrictions. It seems like it will be more open. And to the guys at Ouya, don't hinder the peeps at xda, they are the ones that are going to make you successful.
I posted, thank you for the link. Was wondering where I should voice my concerns.
I posted[/URL as well. I based it mainly as a fail safe for things just happen. The other comments, were more based on others assumptions.
http://www.madcatz.com/m-o-j-o-android-micro-console/
What do you guys think about this. It seems like more what I want. I think if Ouya is going to be restrictive, all dev support should go to a better company. Lets face it, people are looking at the Ouya for what it could be not what it is. It has the hardware to easily replace all the Google Tvs, Apple TVs and Rokus. I actually want it to dual boot into Google TV. Anyway, the Ouya will be releasing soon and there will be many tech articles about it. If we can go onto those articles and leave comment about how the Ouya isn't the good solution we can make a good company popular. I think most people buying the Ouya are just assuming that they will be able to hack it any way they want.
Confused
So do we or dont we have access to a custom recovery? Based on the dev forum I see we have a customer recovery available..what issues are there with it? Also i see WIP for multiple custom roms and even a kernel. I can't imagine one would waste time and making these if there is no viable way to flash them.....
Any information would be much appreciated.
The custom recovery works, many confirmed it on that thread including myself, as for the rest there stillb WIP's
Sent from my Amazon Kindle Fire using xda app-developers app
ej_424 said:
So do we or dont we have access to a custom recovery? Based on the dev forum I see we have a customer recovery available..what issues are there with it? Also i see WIP for multiple custom roms and even a kernel. I can't imagine one would waste time and making these if there is no viable way to flash them.....
Any information would be much appreciated.
Click to expand...
Click to collapse
Ozz465 said:
The custom recovery works, many confirmed it on that thread including myself, as for the rest there stillb WIP's
Click to expand...
Click to collapse
Yes, we can do those things - the heart of the issue is that if any of those things mess up you have the potential to brick your device with no way to recover short of sending it back to OUYA, Inc. Most android device provide a method to enable a usb recovery mode in the event of such a drastic failure, the OUYA console does not. How many people are willing to test/use software that could potentially brick their $100 device that they have been waiting months to get?
ej_424 said:
So do we or dont we have access to a custom recovery? Based on the dev forum I see we have a customer recovery available..what issues are there with it? Also i see WIP for multiple custom roms and even a kernel. I can't imagine one would waste time and making these if there is no viable way to flash them.....
Any information would be much appreciated.
Click to expand...
Click to collapse
The thread title is a bit misleading/confusing, recovery is accessible by rebooting to recovery. The problem is that you there is no way to boot to recovery via hardware except crashing the device during boot up using a keyboard.
They have gone about it all wrong, by allowing users the tools to brick OUYA but not the tools to fix it. Forgive me if I am wrong, but booting in to recovery does not allow us to do anything we can't already do by rebooting in to recovery. I have to wonder if behind closed doors they are moving towards removing root access.
Sent from my SCH-I535 using Tapatalk 2
In attempt to stop repeated questions and thread clutter in "Let's Talk Root" thread by non-developers (myself included), I've created this thread. A place for newbies and general people to ask questions and share rooting ideas. This will save developers time in the original thread. Most devs already know or have tried what you think might work to gain root.
Please stay on the topic of root, be respectful and helpful, and use the search! (both this site and google)
Current Root Status:No Root
Things to keep in mind...
CF-AUTOROOT: Will not work with retail version of the note 4 (this means you bought it from verizon or another retailer) The CF-Autoroot you may come acrossed is the Developer edition. Unless you bought your phone specifically through samsung, you most likely have retail as Developer edition cannot be obtained through bestbuy, verizon, or any retailer. Also, CF-Autoroot works only with Unlocked bootloader. Verizon, At&T and some other Note 4 variants have Locked bootloaders. Flash CF-Autoroot and you might brick your device. For more information visit Chainfires cf-auto-root site.
TowelRoot Towelroot has been made popular due to it's wide spread ability to root a lot of devices. However, Towelroot doesn't work on the Note 4. Towelroot utilizes the Futex bug found in android. Futex is also known as CVE-2014-3153. This bug is confirmed patched on our device.
One click Root programs: While some programs do contain vulnerabilities present in the Note 4 as of now none of them contain one that allows developers to write to /system partition (which is important). where these vulnerabilities may come in handy is combining one or more to obtain root. Still the vulnerability doesn't exist yet. Before posting one click programs do your homework. Google the CVE it utilizes or ask the developer you found it from. Then google that CVE. Look at the date it was found and compare that date to the date the Note 4 was released. As non-developers, its pretty much safe to say any CVE found before the release of the device has been patched. Programs that were meant to root 4.4.2> X.X.X are also pretty safe to assume to be patched.
Know the difference between carrier unlock and bootloader unlock: While it would be nice, the government wouldn't make all phones unlockable in terms of bootloader. What government is doing is unlocking sims. Meaning they are giving you the ability to take your phone to another carrier if you choose to. Even though you maybe taking your Verizon note 4 to T-mobile (which has an unlocked bootloader note 4) You still have a verizon device. Therefore it still has a locked bootloader.
Things that may help...
A way to unlock the bootloader: Probably the least likely to happen, but would guarantee root. This includes turning a retail version into developer edition. (because developer edition is unlocked )
A CVE (vulnerability) that allows code to be written to system: Most probable way root will be achieved.
An app that has root permissions that can be exploited to run our code to inject root: There may be a way through gear VR as VR has special permissions over usual apps. That being said it's only a potential avenue for developers to look at. As VR is so new not much is really know about it.
Want to follow the progress?: Feel free to follow these post. Please do not comment on them asking questions unless you have absolute knowledge to what is being talked about. Keep those thread clean for developers.
Let's Talk Root
Root Attempt #1
Galaxy Note 4 Root Progress (At&t)
I am no way claiming to be a developer. I do not claim to know everything either. I am happy to clarify and change the O.P. to be more accurate .
When you say "an app that has root permissions that can be exploited to run our code to inject root..", do you mean ANY app? Or do you have some specific ones in mind? If it's any app, then man there are a lot of them that actually ask for shell permissions. I usually find that out through the " xprivacy" module that I use to block apps from gaining unnecessary perms on my phone. I have a good list of those ones if that helps. One of them is actually Facebook. lol
K-alz said:
When you say "an app that has root permissions that can be exploited to run our code to inject root..", do you mean ANY app? Or do you have some specific ones in mind? If it's any app, then man there are a lot of them that actually ask for shell permissions. I usually find that out through the " xprivacy" module that I use to block apps from gaining unnecessary perms on my phone. I have a good list of those ones if that helps. One of them is actually Facebook. lol
Click to expand...
Click to collapse
=======
Example.....VR apps...
Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / Custom Kernel-ed / TWRP 2.8.5.0.trltevzw
manbat said:
=======
Example.....VR apps...
Sent from my SM-N910V / VZW Note 4 DE / Factory Bootloader Unlocked / Rooted / Custom Kernel-ed / TWRP 2.8.5.0.trltevzw
Click to expand...
Click to collapse
Well, I'm no note 4 owner. I don't know if the VR app is just a regular app like any app in the play store or if it's something different. I looked it up in the play store and it wasn't there.
VR = virtual reality. It's a seperate device for VR and it is only for the Galaxy Note 4.
Sent from my SM-N910V using Tapatalk
In before close.
K-alz said:
When you say "an app that has root permissions that can be exploited to run our code to inject root..", do you mean ANY app? Or do you have some specific ones in mind? If it's any app, then man there are a lot of them that actually ask for shell permissions. I usually find that out through the " xprivacy" module that I use to block apps from gaining unnecessary perms on my phone. I have a good list of those ones if that helps. One of them is actually Facebook. lol
Click to expand...
Click to collapse
Certain apps have permissions that others don't. And some apps could be more vaulnerable dealing with the Gear VR.
eskomo said:
In before close.
Certain apps have permissions that others don't. And some apps could be more vaulnerable dealing with the Gear VR.
Click to expand...
Click to collapse
I'm just going out on a limb here. It may get closed, but when the same questions keep being asked and our root thread keeps going off topic it makes it hard for devs to even take it seriously. For the progression of root, those technical threads need to stay clean of side chatter. At least there is a place for people to go to have some of the popular questions answered. As a community we need to help each other and that doesn't happen by telling people to get lost because there technical skill is lower than the rest of the guys participating. I see no reason this thread cant have a chance. While I do believe we dont need anymore root threads, this one will be able to cut down on those post too.
K-alz said:
When you say "an app that has root permissions that can be exploited to run our code to inject root..", do you mean ANY app? Or do you have some specific ones in mind? If it's any app, then man there are a lot of them that actually ask for shell permissions. I usually find that out through the " xprivacy" module that I use to block apps from gaining unnecessary perms on my phone. I have a good list of those ones if that helps. One of them is actually Facebook. lol
Click to expand...
Click to collapse
K-alz said:
Well, I'm no note 4 owner. I don't know if the VR app is just a regular app like any app in the play store or if it's something different. I looked it up in the play store and it wasn't there.
Click to expand...
Click to collapse
eskomo said:
In before close.
Certain apps have permissions that others don't. And some apps could be more vaulnerable dealing with the Gear VR.
Click to expand...
Click to collapse
The way the Gear VR works is the api for that device grants the applications a hardware level access to connect, this means they basically have root access. Now these last I saw of this was a while ago and the vulnerability is pretty well known at this point, so patches are a possibility and it's also possible that it doesn't grant the correct permissions for attaining root, the report was pretty vague in that respect.
Now on to separate matters, do we really need another root discussion thread? I'm going to temporarily allow third one, let's see if it can stand on its own because I like the concept here and the op is pretty well organized. Keep in mind though, most of the chatter will be identical between the two threads, so it may not last.
Good luck guys.
Figured I'd mention this, looks like people in the AT&T side have possibly found an SYSTEM (not bootloader) exploit!
http://forum.xda-developers.com/showpost.php?p=58920677&postcount=1051
Stryke_the_Orc said:
The way the Gear VR works is the api for that device grants the applications a hardware level access to connect, this means they basically have root access. Now these last I saw of this was a while ago and the vulnerability is pretty well known at this point, so patches are a possibility and it's also possible that it doesn't grant the correct permissions for attaining root, the report was pretty vague in that respect.
Now on to separate matters, do we really need another root discussion thread? I'm going to temporarily allow third one, let's see if it can stand on its own because I like the concept here and the op is pretty well organized. Keep in mind though, most of the chatter will be identical between the two threads, so it may not last.
Good luck guys.
Click to expand...
Click to collapse
Thank you so much for the explanation, sir.
BTW, please don't close this thread because it's gonna be a stress relief for us non-devs people to gush our b!tching about root here since we are not willing to clutter those active threads with our useless posts. [emoji16] [emoji23]
Thank you in advance.
veteranmina said:
Figured I'd mention this, looks like people in the AT&T side have possibly found an SYSTEM (not bootloader) exploit!
http://forum.xda-developers.com/showpost.php?p=58920677&postcount=1051
Click to expand...
Click to collapse
They have definitely found something VERY promising. Even jcase chimed in stating that the bootloader isn't actually encrypted which amazing news for us. Vulnerability exists in the note 4 and they're catching it very soon. So exciting.
K-alz said:
Thank you so much for the explanation, sir.
BTW, please don't close this thread because it's gonna be a stress relief for us non-devs people to gush our b!tching about root here since we are not willing to clutter those active threads with our useless posts. [emoji16] [emoji23]
Thank you in advance.
They have definitely found something VERY promising. Even jcase chimed in stating that the bootloader isn't actually encrypted which amazing news for us. Vulnerability exists in the note 4 and they're catching it very soon. So exciting.
Click to expand...
Click to collapse
very promising indeed. In the event we receive root in the coming days, I will rewrite this thread into a noob guide.
Sent from my bandaid smelling s-pen
just a heads up, the att root thread was closed by moderators because the tards over there were much like the tards over here and couldn't keep off topic posts out of the discussion... i. e, how much they love devs, the phone, or hate the phone, or telling others root will come soon and to be patient.
either way, if the same people keep posting bs in our thread, it'll be closed too.
Sent from my Samsung Galaxy Note 4 using Tapatalk.
jayochs said:
just a heads up, the att root thread was closed by moderators because the tards over there were much like the tards over here and couldn't keep off topic posts out of the discussion... i. e, how much they love devs, the phone, or hate the phone, or telling others root will come soon and to be patient.
either way, if the same people keep posting bs in our thread, it'll be closed too.
Sent from my Samsung Galaxy Note 4 using Tapatalk.
Click to expand...
Click to collapse
The good news is that orc said that that thread will open when real progress is made, so if we see that thread reopen, we will know we're in business.
So this post isn't pointless and because this thread is for non-devs, I'll let people know where things were in that thread last.
There are two known CVE's that both the Verizon and AT&T Note 4 are vulnerable to. These CVE's, once exploited, will be a two-pronged attack and will likely achieve root. The developers are now trying to compile an apk that can implement these exploits. The mood from the devs wasn't so much "guessing" or "maybe", it was a mood of confidence. Many of them truly believe these CVE's will lead to root.
Sent from my SAMSUNG-SM-N910A using Tapatalk
I was wondering if we could implement something like safestrap or if anything like it could be used . I was just looking up info as for possible solutions for root and happened to come across this I hope I'm not off topic or derailing the thread if so I apologize in advance
http://gs5.wonderhowto.com/how-to/i...loader-locked-galaxy-s5-at-t-verizon-0156728/
Never mind sorry folks I just realized that the device had to be rooted in order to use safestrap I'm apologize please carry on..
Sent from my SM-N910V using XDA Premium HD app
rrjskj said:
I was wondering if we could implement something like safestrap or if anything like it could be used . I was just looking up info as for possible solutions for root and happened to come across this I hope I'm not off topic or derailing the thread if so I apologize in advance
http://gs5.wonderhowto.com/how-to/i...loader-locked-galaxy-s5-at-t-verizon-0156728/
Sent from my SM-N910V using XDA Premium HD app
Click to expand...
Click to collapse
It is a good question but however with safestrap you must have root access in order to install it into the system. I used it in the past on my DROID bionic. It hijacks the boot process giving you a form of custom recovery.
Lol I just realized that after I reread what the steps are in order to use it sorry I thought I might have been onto something thanks for the fast response though
Sent from my SM-N910V using XDA Premium HD app
rrjskj said:
Lol I just realized that after I reread what the steps are in order to use it sorry I thought I might have been onto something thanks for the fast response though
Sent from my SM-N910V using XDA Premium HD app
Click to expand...
Click to collapse
No problem! This is the non dev thread. Shouldn't be any bashing for questions like that.
While doing a search to see if there was root for my wife's lg g3 I stumbled across this it says it can root any android device I thought it might be useful so here goes
http://androidxda.com/download-root-genius
Sent from my SM-N910V using XDA Premium HD app
rrjskj said:
While doing a search to see if there was root for my wife's lg g3 I stumbled across this it says it can root any android device I thought it might be useful so here goes
http://androidxda.com/download-root-genius
Click to expand...
Click to collapse
Don't take my word for it completely, but if I remember correctly from some thread, the Galaxy Note 4 has a newer Kernel version, therefore would not be subject to the same exploit as the LG G3.
rrjskj said:
I was wondering if we could implement something like safestrap or if anything like it could be used . I was just looking up info as for possible solutions for root and happened to come across this I hope I'm not off topic or derailing the thread if so I apologize in advance
Click to expand...
Click to collapse
From what I understand, you need an unlocked bootloader for that, let alone, root as well. Again, don't take my word completely for it. Achieving root will give apps root access, but it won't allow us to change our bootloader and load custom ROMs....if I'm wrong, please someone correct me on this.
@ the OP...can you use some other color other than bright green? It's a little hard to read, but if I'm the only one, don't just change it for little ole me. Also, if I'm correct regarding (not) being able to install Safestrap and do custom ROMs, can you add that to the OP as well? Just want to help reduce redundancy. Very good thread as well. Thanks!
rrjskj said:
While doing a search to see if there was root for my wife's lg g3 I stumbled across this it says it can root any android device I thought it might be useful so here goes
http://androidxda.com/download-root-genius
Sent from my SM-N910V using XDA Premium HD app
Click to expand...
Click to collapse
So did you try it? I doubt it works
Picked up the S7 Edge from TMO after sadly surrendering my Note7. Wondering if there are Roms and a root method. I've searched the threads and don't see much. Any help is appreciated!!
TMO S7 Edge Root/Roms?
Sent from my SM-G935T using XDA-Developers mobile app
MOD EDIT:
Questions belong in the Help section, not How-To. I've moved your thread there.
Rooting Procedure
http://forum.xda-developers.com/tmobile-s7-edge/how-to/how-to-root-s7-edge-t3410470
Roms
http://forum.xda-developers.com/tmobile-s7-edge/development
literally on the page i found by googling "tmobile s7 edge xda", i found a guide for rooting, along with two rom threads. and that's without even searching.
Root removes samsungpay permanently and is a bad battery drain last o checked
and also causes the phone to overheat and consistently lag/stutter even after changing kernel peramseters. root is just not worth it on the s7 edge. we need aosp/cm on this thing.
Thx for all the input guys. Much appreciated
Sent from my SM-N920V using XDA-Developers mobile app
xVermicide said:
literally on the page i found by googling "tmobile s7 edge xda", i found a guide for rooting, along with two rom threads. and that's without even searching.
Click to expand...
Click to collapse
Wasn't asking for a root method just Roms. I've been away from root for about 1.5 years when I moved form my G3 to a Note 5 so it's been a while. Had to surrender my Note7 so I was looking around and didn't see much for the edge device and especially the snapdragon model. After some looking I'm seeing more posted in the S7 section but thanks for saying so.
I'm in the same boat, waiting to receive a S7 Edge. I can't believe the state of root with this phone, I mean the Note 7 has root and it doesn't really lag , stutter or effect battery. (it can blow up though!)
Anyone try the 2 roms? Do they help bring it back to normal?
Ippolito1971 said:
Wasn't asking for a root method just Roms. I've been away from root for about 1.5 years when I moved form my G3 to a Note 5 so it's been a while. Had to surrender my Note7 so I was looking around and didn't see much for the edge device and especially the snapdragon model. After some looking I'm seeing more posted in the S7 section but thanks for saying so.
Click to expand...
Click to collapse
actually, it says in your topic name and first post that you are looking for a root method and roms. both of which are found on the phone's XDA page without searching. also, you keep saying you were "looking around" and didn't find anything but literally all the information you need is in the guides section, which is where you should always start when you have extremely basic questions like this.
xVermicide said:
actually, it says in your topic name and first post that you are looking for a root method and roms. both of which are found on the phone's XDA page without searching. also, you keep saying you were "looking around" and didn't find anything but literally all the information you need is in the guides section, which is where you should always start when you have extremely basic questions like this.
Click to expand...
Click to collapse
Once again, thanks for the help.
Sent from my SM-G935T using XDA-Developers mobile app
Always someone lurking in the rafters waiting for the highlight of their day, which seems to be repetitive condescension disguised in the form of a response to a question, whether it's been asked and answered already or simply something they've decided is beneath them to read or simply just pass over (and yet not so much so that they can't pop in to dispense that oh so productive and about as necessary as the offending inquiry itself complimentary condescension) Not passing judgment on said question itself, since it doesn't bother me either way. XDA has been a complete congestion zone of information for several years now and I've seen bigger offenses handled with much more patience and maturity than this one (by those who were posting in threads for cheaper phones in need of much more help than this one js). Instead of repeating your amazing accomplishments in the area of Googling (which is always my first stop, unfortunately my next is almost always XDA where the Mods are Gods and everyone thinks they're too cool to pass along some of that precious wisdom they were clearly so preoccupied with acquiring they didn't have time to brush up on some proper grammar. Or punctuation. Maybe even a quick refresher course on basic manners, a better attitude and some other fundamental social etiquette) :fingers-crossed: ok, ok, ok for the sake of not appearing to be "bullying" or "targeting" anyone in particular...and because this unnecessary rant just ate up my Red Bull and cigarette break time, the time for my digression has arrived :angel: Yfw kiddies. Now play nice or I'll come back and taunt you a second time. Because your father was a hamster and your mother smelt of elderberries NOW HUG EACH OTHER!
i am oblivion said:
Always someone lurking in the rafters waiting for the highlight of their day, which seems to be repetitive condescension disguised in the form of a response to a question, whether it's been asked and answered already or simply something they've decided is beneath them to read or simply just pass over (and yet not so much so that they can't pop in to dispense that oh so productive and about as necessary as the offending inquiry itself complimentary condescension) Not passing judgment on said question itself, since it doesn't bother me either way. XDA has been a complete congestion zone of information for several years now and I've seen bigger offenses handled with much more patience and maturity than this one (by those who were posting in threads for cheaper phones in need of much more help than this one js). Instead of repeating your amazing accomplishments in the area of Googling (which is always my first stop, unfortunately my next is almost always XDA where the Mods are Gods and everyone thinks they're too cool to pass along some of that precious wisdom they were clearly so preoccupied with acquiring they didn't have time to brush up on some proper grammar. Or punctuation. Maybe even a quick refresher course on basic manners, a better attitude and some other fundamental social etiquette) :fingers-crossed: ok, ok, ok for the sake of not appearing to be "bullying" or "targeting" anyone in particular...and because this unnecessary rant just ate up my Red Bull and cigarette break time, the time for my digression has arrived :angel: Yfw kiddies. Now play nice or I'll come back and taunt you a second time. Because your father was a hamster and your mother smelt of elderberries NOW HUG EACH OTHER!
Click to expand...
Click to collapse
Lol I agree with you... I think people get tired of answering the same questions though. Especially when the answer is like 2 posts down lol.
Tmo S7 Edge
Hi there. I have 4 Tmo S7 Edge running ECHO Universal G935 Rom. First download the QUALCOMM SNAPDRAGON FILES From MAX on HIGHONANDROID for US SM-G930 and G935. Big thanks to MAX and the DEVELOPERS out there who create these things. Create a folder on your computer for all the files you'll need. Download the flashfire APK file, then ECHO Universal Rom from Verizon S7 Edge Forum. Put on your phone SD card. Watch MAX video if you don't understand, flash the modify tar file, then run superSU, then install flashfire apk. I do this process under 2 minutes, I tried different Roms from Verizon, Sprint and ATT root and unroot many times. Once you get a hang of the process it will come like brushing your tooth and putting on your jacket at the same time. Good ? luck Buddy
i am oblivion said:
Always someone lurking in the rafters waiting for the highlight of their day, which seems to be repetitive condescension disguised in the form of a response to a question, whether it's been asked and answered already or simply something they've decided is beneath them to read or simply just pass over (and yet not so much so that they can't pop in to dispense that oh so productive and about as necessary as the offending inquiry itself complimentary condescension) Not passing judgment on said question itself, since it doesn't bother me either way. XDA has been a complete congestion zone of information for several years now and I've seen bigger offenses handled with much more patience and maturity than this one (by those who were posting in threads for cheaper phones in need of much more help than this one js). Instead of repeating your amazing accomplishments in the area of Googling (which is always my first stop, unfortunately my next is almost always XDA where the Mods are Gods and everyone thinks they're too cool to pass along some of that precious wisdom they were clearly so preoccupied with acquiring they didn't have time to brush up on some proper grammar. Or punctuation. Maybe even a quick refresher course on basic manners, a better attitude and some other fundamental social etiquette) :fingers-crossed: ok, ok, ok for the sake of not appearing to be "bullying" or "targeting" anyone in particular...and because this unnecessary rant just ate up my Red Bull and cigarette break time, the time for my digression has arrived :angel: Yfw kiddies. Now play nice or I'll come back and taunt you a second time. Because your father was a hamster and your mother smelt of elderberries NOW HUG EACH OTHER!
Click to expand...
Click to collapse
Yes but how do you know she's a witch?
Sent from my SM-G935T using XDA-Developers mobile app
Rayn1328 said:
Yes but how do you know she's a witch?
Click to expand...
Click to collapse
Build a bridge out of her?
i am oblivion said:
Build a bridge out of her?
Click to expand...
Click to collapse
What else floats? Little tiny rocks!!!!
Sent from my SM-G935T using XDA-Developers mobile app
Sorry for lost I had to do the the same thing a few days ago it doesn't feel the same but android n is coming hold out and get red of the bloat ware on the s7edge I did it runs great can't wait for grace ux 7.0 cheers
drew272011 said:
Sorry for lost I had to do the the same thing a few days ago it doesn't feel the same but android n is coming hold out and get red of the bloat ware on the s7edge I did it runs great can't wait for grace ux 7.0 cheers
Click to expand...
Click to collapse
Anyway to get Grace UX apps from the Note 7 on S7E without root?