I am currently a G1 owner on the fence about rooting my phone, as are many others. One of the first issues I've come across is being overwhelmed by forum threads. Unless I have missed something (and if I did, please point me in the right direction!), everything is posted in forums here, requiring people to pour through tons of posts and pick through the right information.
Is there an official wiki or something where all the latest news, guides, FAQs, etc. are being updated? If not, I'd love to start one, but unfortunately I don't have the knowledge to do so (yet, at least). I'm thinking of a super simple, jargon-free site for users to find answers to their questions, and a simple outlined "official" process for how to begin and where to go from there.
For example, some FAQs..
Can T-Mobile/Google "cut me off" in any way if they determine I have rooted my phone?
If I change my mind later, can I go back to original firmware and leave no trace that I ever rooted the phone in the first place? Future over-the-air updates will install with no issues?
Let's say I mess up during the rooting process. Is there always a way out, or am I screwed?
How safe is storing apps on the SD card? What can happen to my phone, and how do I avoid problems?
What are the JFvX.XX firmware releases? How do they work? Are they required? Are there other alternatives?
What if a future OTA can't be hacked, will we miss out on features?
I've seen various different methods of rooting the G1, which one is the most popular and why?
etc.
This is just an idea, but there's all these questions like this that I know many people have. While these questions can easily be answered in forums, I'm looking for a more convenient solution for the community. As official answers are nailed down, it would be great to have a reference to check with rather than flooding forums with questions.
Anyway, thanks for all the hard work from the developers here. It's really exciting to follow, and I can't wait to see what the future holds for the G1!
they have one:
http://wiki.xda-developers.com/index.php?pagename=HTC_Dream
look first
kay11224 said:
they have one:
http://wiki.xda-developers.com/index.php?pagename=HTC_Dream
look first
Click to expand...
Click to collapse
Thanks for the link, but unfortunately this doesn't seem user friendly (it's filled with unexplained links and jargon), and seems pretty outdated. I'm thinking about info aimed the average n00b end-user here, not developers or people actively following the forums and progress made.
I'm not sure if you understand fully what you're asking. Keeping your phone updated without "actively following the forums and progress made" is a simple task right now, just wait until Google pushes an update for you. If using the search function is too hard for you, I think root access is biting off more than you can chew. All of your FAQ's can easily be found in the development section of the forums. As far as step by step guides are concerned, read the stickies, use the search function, and then ask. It's not complicated at all.
dudinatrix said:
Can T-Mobile/Google "cut me off" in any way if they determine I have rooted my phone?
If I change my mind later, can I go back to original firmware and leave no trace that I ever rooted the phone in the first place? Future over-the-air updates will install with no issues?
Let's say I mess up during the rooting process. Is there always a way out, or am I screwed?
How safe is storing apps on the SD card? What can happen to my phone, and how do I avoid problems?
What are the JFvX.XX firmware releases? How do they work? Are they required? Are there other alternatives?
What if a future OTA can't be hacked, will we miss out on features?
I've seen various different methods of rooting the G1, which one is the most popular and why?
etc.
Click to expand...
Click to collapse
1) as far as i'm aware no. They can remove apps from peoples phones (allegedly) but i can't see how they would know you have root, or even care. It's good publicity for the phone if anything.
2) Yup, you can easily un-root your phone and the updates should work correctly.
3) Once you have the hardSPL bootloader loaded it's pretty much impossible to brick your phone, see this thread for details.
4) Not sure about this, so i can't comment
5) the JF firmware releases are essentially hacked firmwares, created by JesusFreke, that allow us to get root access (among other things ). they are incredibly easy to install and they are required for certain things such as, multi-touch. as far as i know, there are no alternatives.
6) They will be as everything is open source. I imagine xda will have a firmware hacked within hours of it's release
7) personally, i find this way the best. nice n simple and easy to follow.
have fun
Iceucold said:
I'm not sure if you understand fully what you're asking. Keeping your phone updated without "actively following the forums and progress made" is a simple task right now, just wait until Google pushes an update for you. If using the search function is too hard for you, I think root access is biting off more than you can chew. All of your FAQ's can easily be found in the development section of the forums. As far as step by step guides are concerned, read the stickies, use the search function, and then ask. It's not complicated at all.
Click to expand...
Click to collapse
I am perfectly capable of handling root access. I am a Linux system administrator (among other things) by profession. I admit, this would be my first attempt at "hacking" a device and thus voiding the warranty, hence my hesitation and "noob" questions. Using the search function is not my concern here, but I can appreciate where you're coming from.
What I'm talking about, and what appears to be misinterpreted, is an information source for common end users, not developers or tech-savy users. If I have questions about rooting the G1, certainly those less technically inclined do as well. And unfortunately for them, they don't necessarily even know where to begin looking. I'm talking about people like my brother in law, for example... who probably never used a forum in his life, but wants to have multi-touch on his phone, or change his themes, or find a solution to his constant "low storage" warnings. People like him don't care about hacking into the phone and getting all this flexible access for himself. They just want to take advantage of what's already been achieved, but unfortunately require root to do so.
I agree that it is pretty simple to root the phone, but face it you have to be somewhat comfortable with technology first, even just to obtain the information.
Perhaps now isn't the appropriate time to wrap things up in a bow and give to the general G1 user base in a tidy little easy-to-digest package. As things develop further it may just naturally come about, perhaps via installers or something. I just think it would be helpful to many to have a source written for the common folk with jargon-free information... considering the more people get their hands on it, the more successful the platform can become.
And to Metlus, thanks for being receptive and answering my questions kindly without making me feel judged for asking what I assume many think is a "just search for it" type of post.
Meltus said:
1) as far as i'm aware no. They can remove apps from peoples phones (allegedly) but i can't see how they would know you have root, or even care. It's good publicity for the phone if anything.
2) Yup, you can easily un-root your phone and the updates should work correctly.
3) Once you have the hardSPL bootloader loaded it's pretty much impossible to brick your phone, see this thread for details.
4) Not sure about this, so i can't comment
5) the JF firmware releases are essentially hacked firmwares, created by JesusFreke, that allow us to get root access (among other things ). they are incredibly easy to install and they are required for certain things such as, multi-touch. as far as i know, there are no alternatives.
6) They will be as everything is open source. I imagine xda will have a firmware hacked within hours of it's release
7) personally, i find this way the best. nice n simple and easy to follow.
have fun
Click to expand...
Click to collapse
Great post meltus!
If and when you do decide to root g1 take your time and breathe, really isn't too hard just nerve racking the first time. I did it and im not a pro at all so you will probably breeze through it! The advancements made so far are unreal, auto browser, themes and many more make rooting well worth it in my opinion
I'm not sure if it gets any easier than this, but gizmodo today posted what looks like the easiest "recipe" yet for rooting the G1:
How To: Hack Android For Multitouch Web Browsing on the T-Mobile G1
So, with all the interest in getting Android on Windows Mobile phones, I am wondering what sort of thing it would take for the community to start a project for hacked booloaders to allow the direct booting of Android. If I remember correctly, the next thing would be to learn to write directly to the DOC chip to allow Android to be flashed to the device.
So, would we as a community be willing to set some sort of bounty to get this in motion?
Hell yes! Let's make this happen. We need to get really organized in our effort to get android on WiMo phones.
I've had android phones for a while now, and I've always been interested in how to build custom roms, compile kernels, and so on, but no one has ever been willing to point me in the right direction to help.
If anyone can show me some really good info I can use to learn it would be greatly appreciated.
Thanks
BThomas wrote up a good how to for a bunch of stuff.
http://forum.xda-developers.com/showthread.php?t=967290
and there is a another build thread here
http://forum.xda-developers.com/showthread.php?t=968794
Use some of that and search and ask questions. Most of the devs seem to be VERY helpful as long as they are legit questions.
Teaching someone how to compile code is not easy...it's not always the same steps for every type of device. There are any number of things that can complicate the process.
Do you have any experience at all with writing/editing code? If not, you probably don't want to start by messing around with the kernel.
No dev experience or history. I don't care whether its the kernel/rom/whatever, I just want to learn to do this stuff so in the future, I can release good things for our users here, or so if I dont like my options I can always create my own stuff. You know?
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.
Okay I am new. Well I’ve been on the forums before but I joined just now. I’ve always been on iOS and still am because my family’s embedded in there ecosystem. Nuff said. However I want to take my android and other interests to the next level. I’ve a galaxy s10 5g and a burner lgkv500 I think. I want to root the galaxy for obvious reasons it’s a powerhouse of a phone. I can’t find a clear source of info as to its ability to be rooted. and the lg I want to practice on I can’t find a clear guide to root that either. I found this guide to root the galaxy. Can someone steer me to a good point to take off for either phone. I need to go through the process of rooting one of my devices and have it in my hand and mess around so I can learn. I need to learn the lingo so I can ask the proper questions and give the proper information. I’m a fast learner and can follow directions. Hope to hear something from a like minded.