Related
As a new Android user who is very familiar with the command line and with Linux/Unix environments, I still feel extremely overwhelmed with the amount of 'fixes' and 'root' hacks going around.
I've played with linux for 100's of hours and have broken the install and fixed it...
But this is a phone that bricks, not a computer. I don't like playing "oh I'll just try this and see what happens" with my $400 phone.
Plus I honestly can't determine which one is best for me.
I started this thread so that someone could assist me in creating a guide for what you want to do and what is best to do it.
For example, I want to upgrade to Froyo when it releases.
In the mean time I want to install a lag-fix/ custom rom.
mymansionisabox said:
As a new Android user who is very familiar with the command line and with Linux/Unix environments, I still feel extremely overwhelmed with the amount of 'fixes' and 'root' hacks going around.
I've played with linux for 100's of hours and have broken the install and fixed it...
But this is a phone that bricks, not a computer. I don't like playing "oh I'll just try this and see what happens" with my $400 phone.
Plus I honestly can't determine which one is best for me.
I started this thread so that someone could assist me in creating a guide for what you want to do and what is best to do it.
For example, I want to upgrade to Froyo when it releases.
In the mean time I want to install a lag-fix/ custom rom.
Click to expand...
Click to collapse
Do people not know how to read stickies? there are guides and how-to's in this section alone. There are more in the development section. If you don't know how to search a forum, I'm not entirely sure you should be messing with your phone's firmware.
Kaik541 said:
Do people not know how to read stickies? there are guides and how-to's in this section alone. There are more in the development section. If you don't know how to search a forum, I'm not entirely sure you should be messing with your phone's firmware.
Click to expand...
Click to collapse
I actually have read all of the stickies.
Im not asking 'how-to' do anything.
What I am saying is that this forum has an absolute overload of 'information' and 'solutions'
There should be a more concise sticky discussing the advantages/disadvantages of each rom/lag fix/flash/recovery/etc. (Or at least about the ones anyone cares about)
If this exists, I sure as hell don't see it.
mymansionisabox said:
I actually have read all of the stickies.
Im not asking 'how-to' do anything.
What I am saying is that this forum has an absolute overload of 'information' and 'solutions'
There should be a more concise sticky discussing the advantages/disadvantages of each rom/lag fix/flash/recovery/etc. (Or at least about the ones anyone cares about)
If this exists, I sure as hell don't see it.
Click to expand...
Click to collapse
I think you're in a wrong forum if you want someone to give you any kind of "distilled", spoon-fed info just because you're afraid to mess with your "$400" phone.
Again, to second the other reply, all the info is posted. Just RTFW/S.
mymansionisabox said:
I actually have read all of the stickies.
Im not asking 'how-to' do anything.
What I am saying is that this forum has an absolute overload of 'information' and 'solutions'
There should be a more concise sticky discussing the advantages/disadvantages of each rom/lag fix/flash/recovery/etc. (Or at least about the ones anyone cares about)
If this exists, I sure as hell don't see it.
Click to expand...
Click to collapse
there are tons of guides and they're all condensed. I have to agree with the other poster, if you aren't going to take the time to read and learn what you're doing, don't do it. each sticky offering to help you through all of these processes are there for a reason.
There's the "Pimp My Captivate" thread which is exactly what you say you want. And there have been comparisons of each lagfix by Zilch25, clockwork recovery by Koush is clearly explained in his thread, each ROM is discussed in their own thread.
Ironically, you're asking for a sticky so as to have less stickies. Finding out which ROM you want to use is up to you and if you're not going to take the time to figure out what each tool offers or what each base ROM means, then maybe flashing your phone is something you should steer clear of for now.
If you're afraid of bricking it, just do a Nandroid backup. If something goes wrong, then you can just flash back and it'll be A-OK. If you seriously brick your phone and it's 100% messed up, it's probably because you tried to mess it up.
Hydrocharged said:
If you're afraid of bricking it, just do a Nandroid backup. If something goes wrong, then you can just flash back and it'll be A-OK. If you seriously brick your phone and it's 100% messed up, it's probably because you tried to mess it up.
Click to expand...
Click to collapse
Even guys that intentionally tried to brick their phone can't do it. I don't have much to say as it already has. Just take the time to read. There is a condensed version of what you can do to your phone, the pimp my captivate. Otherwise there are many different ways of rooting, lax fixes, firmwares to flash etc...so there is not one thing that you can do that will make your decision easier.
flashman2002 said:
Even guys that intentionally tried to brick their phone can't do it. I don't have much to say as it already has. Just take the time to read. There is a condensed version of what you can do to your phone, the pimp my captivate. Otherwise there are many different ways of rooting, lax fixes, firmwares to flash etc...so there is not one thing that you can do that will make your decision easier.
Click to expand...
Click to collapse
don't say that. there have been several confirmed bricks from i9000's using the i897 one-click downloader. While there is no immediate, known, for-certain brick method for your phones... you never know who or what may be the first... always read as much as you can in the threads before you attempt to do anything
As someone who was new to the Captivate scene, but not XDA, just two weeks ago the best advice I can give you is start with the "Pimp my Captivate" PDF file. Read through that and then move forward to other stuff like flashing new firmware and using odin. Trust me you will catch on. I am no move on to working on friends phones for them without any worry of breaking (bricking) them.
Just read, read, read, and sometime read some more. If you have a question about a certain hack, fix, firmware...ect then just ask that question in that thread. Trust me there will be very useful helpful people to answer your questions.
I did what is probably the easiest method. I used unleash the beast and then one click lag fix. That's it and my phone is amazing now. I plan on sitting tight until froyo comes out and whatever the top rom happens to be.
I do appreciate everyone's answers.
Despite that, I really don't understand this particular forum's aversion of being more organized and concise. (imo)
I don't think any of you who told me to read actually understood my intentions of making this post since,although I didn't state it, I have already flashed mods to my Captivate and I have modded my previous phones.
I'm new to XDA so maybe this site is far more trustworthy than where I've been.
I'll check it out and read at least the last 10 pages of each thing that I install.
Thanks though.
Mod please close this thread.
mymansionisabox said:
I do appreciate everyone's answers.
Despite that, I really don't understand this particular forum's aversion of being more organized and concise. (imo)
I don't think any of you who told me to read actually understood my intentions of making this post since,although I didn't state it, I have already flashed mods to my Captivate and I have modded my previous phones.
I'm new to XDA so maybe this site is far more trustworthy than where I've been.
I'll check it out and read at least the last 10 pages of each thing that I install.
Thanks though.
Mod please close this thread.
Click to expand...
Click to collapse
we have nothing against being "organized," I just believe your definition of organization is far too complex. You want all the ROMs compared side by side, followed by the tools, and the rooting methods, and the lagfixes and to know which is "best."
Each thing is kept separate from the other because there would be an absolute and definite overload of information in each thread. Look at SRE (a fine example of how to do it properly), he details the result for the end-user and then provides links to where each part of what he did came from. The development section provides a thread on reverting to stock and just that because it should focus on that, rooting can be left for a thread on rooting. SRE shouldn't be tossed into a thread with UTB because they provide different effects.
If you were to compile everything into one big mega-thread, questions would never be answered because there would be far too much crossover. The Pimp My Captivate thread is as good as it gets in that regard, they provide optimizations and suggestions and where to find more information, which is good enough.
I understand.
After this post I am done though, because I'm getting no where with this.
Check out the web page below, this is really what I meant. I can't post links so just close the gap between http:// and ga..
http:// gadgets.boingboing.net/2008/12/17/osx-netbook-compatib.html
I belong to several forums that had been attempting to put mac osx on netbooks and on one of them a chart of compatibility was compiled, which is similar to what I was suggesting we needed.
Ignore the comments below the chart; that would be unnecessary.
All I was proposing to do was have a locked/stickied thread that only a moderator could change up as new changes/improvements occurred.
Each root/lagfix/rom would have a href connected to their actual thread.
So there would be no need to have comments/ questions asked on that particular page. ****.. it could just be a damn wiki page, but I digress..
If no one thinks that would be beneficial to the community, that is fine.
I don't care, I can easily figure it out myself.
Mod, please close thread.
So, I suppose you -- like me -- opened this thread to find out how to take your brand new (or new to you) GT+wifi and take the power back from Samsung by rooting and installing custom firmware! Well... Here's the deal: this forum is a complete mess. The small number of guides are either difficult to follow or incompatible with one another. Links for downloads are mostly dead and everything is completely out of date. If you're like me this drives you crazy...
The best forums in XDA have become so because of a few people. Most importantly, of course, are the developers; without them this place wouldn't have a reason to exist. But almost as important as the developers are a small number of users who take up the task of helping other users by writing guides and instruction manuals, and answering questions. This is what the GT+ forum lacks.
So here's what I'm proposing to do. I'd like to create a wiki post that I'll update with guides and working links. I'll keep it up-to-date so that a newbie can open the thread, look at the TOP of the first post, and get their tablet working within a few hours. It will make the entire experience more satisfying both both users and developers. But I can't do it without your help: I don't know jack about this tab (just got it last week). So post your info below and I'll update soon.
Good one buddy. But I don't agree with you on the mess part. There is no much cfw because samsung does not want to release some code. So we have "only" optimized and cleaner versions of stock rom, and a heroically port of cm9 but without wifi.
And if you try to put a lot of links and information on first post, good luck. Noobs dont like to read, you will get 95% of posts of people asking how to root or other thing that someone answered 1 post above.
The idea of make mirrors of links is very welcome.
EDIT: This will be very helpful: http://www.youtube.com/watch?v=JmvCpR45LKA
Enviado de meu MB525 usando o Tapatalk 2
slack04 said:
So, I suppose you -- like me -- opened this thread to find out how to take your brand new (or new to you) GT+wifi and take the power back from Samsung by rooting and installing custom firmware! Well... Here's the deal: this forum is a complete mess. The small number of guides are either difficult to follow or incompatible with one another. Links for downloads are mostly dead and everything is completely out of date. If you're like me this drives you crazy...
The best forums in XDA have become so because of a few people. Most importantly, of course, are the developers; without them this place wouldn't have a reason to exist. But almost as important as the developers are a small number of users who take up the task of helping other users by writing guides and instruction manuals, and answering questions. This is what the GT+ forum lacks.
So here's what I'm proposing to do. I'd like to create a wiki post that I'll update with guides and working links. I'll keep it up-to-date so that a newbie can open the thread, look at the TOP of the first post, and get their tablet working within a few hours. It will make the entire experience more satisfying both both users and developers. But I can't do it without your help: I don't know jack about this tab (just got it last week). So post your info below and I'll update soon.
Click to expand...
Click to collapse
I suggest that someone instead creates an index with all the roms most important info, links etc. like this one: http://forum.xda-developers.com/showthread.php?t=809328
I'd be able to do it, but a little help would be appreciated
In short, what I am trying to break out into discussion is simple - we need to figure out a way to reduce user-related/caused damaged devices.
I know we all put our disclaimers in our ROM threads, if you break your device, not my fault, etc. etc.... and before we discuss this I will say it is not our sole responsibility to make sure nobody does something dumb by installing firmware to their devices that may cause issues. What is inspiring this discussion are threads and posts such as this one, and they seem to be popping up more and more:
http://forum.xda-developers.com/showthread.php?t=2056369
http://forum.xda-developers.com/showpost.php?p=35793341&postcount=10
For the benefit of the general community and for people who, quite honestly, have almost no idea what they are doing when installing custom software to their devices, I think there should be a little more clarity and warning to users regarding what they should and shouldn't be flashing on top of their custom/packaged ROMs. And for the record I am in no sense of mind saying this could have been avoided by this user. In an analogical way I would say it is similar to teaching a child how to walk, or not play with light sockets. We cannot simply say, "oh be careful" because most people are careful, their issue is simply that they don't know. As developers we know EXACTLY what is compatible with our ROMs and what is not. This would include firmware, of all types - kernels, radios, build versions and modifications to the framework through flashable zip files in recovery.
More and more I am seeing threads like this one mentioned springing up about boot looping, lost IMEI's, and devices being destroyed because a user is (most likely) unaware of small differences between a device or installation method which if was aware, could have avoided an issues, and could have avoided another thread being posted wondering why "x" issue is happening. Of course there will always be these threads, issues, etc., but I feel like some type of quality control could be done on our part. This is what I propose, and I think we should encourage this among ourselves to avoid issues:
At the very top of our threads, the very top, before they see a download link, before they see a list of all of the exciting modifications amplifying their eagerness to flash, and dulling their eagerness to read, we should implement some "OP structure" so to speak. What I would propose is we all try to lay out our threads in this manner:
1. Name of ROM
2. List of ALL known compatible working (in this order): kernels, UI modifications (themes, etc.), firmwares. I would say that THIS is where our disclaimers should go. Right after telling the user what they should and shouldn't flash. This will strike up awareness on the other end (the user) that anything done outside of this instruction is a risk to the device and can permanently damage the device. This should be stressed even more in a thread where the developer has chosen to implement firmwares, builds/ROMs of other devices. The idea is more warning and thorough explanation of what can and can't be installed on top of our ROMs will in fact decrease user error. It is our responsibility to make an effort to decrease this possibility as much as possible. A quick list of useful information will go a long ways.
3. Recommended installation method as the developer has tested and proven - with a step by step instruction to flash.
People need to see this kind of thing before they see a download link. It will help the forum not be overridden by threads and posts of people wondering why something is broken (sometimes permanently), or not working correctly. This will also help troubleshoot issues as somebody will ALWAYS come back with "x" issue, and the first response by somebody should be "well did you follow all the instruction at the top of the OP?" and right away in a productive manner we are troubleshooting issues.
I believe we can ourselves "do some reading" and follow the work of our fellow developer members who spend tiresome hours building for various devices. Knowing what issues are going on with each other's work and thus knowing what our users are expecting will again only help everyone. Let's promote proper cautious behavior as an initial emotion when seeing a new update to a ROM, rather than the excitement of simply a new update. I know this will help, and it will make it easier on those of us who build and produce the software for our users.
I am curious to know people's thoughts about this idea - a structured method of laying out our threads with instruction and information, then the great things they have to expect after installation is complete. These are computers, not phones, let's treat them as such.
:highfive:
I am copying a thread over to this forum that I wrote up in the S3 section about proper flashing methods that have always worked for me flawlessly. There is never fault in taking extra time to make sure something is done 100% correct the first time, to rule out variables that might have caused "x" issue.
Here is the thread I was referring to. http://forum.xda-developers.com/showthread.php?t=1946701
This will be posted in the dev section as this is where people go to flash ROMs, putting it in QA is useless as that is where people go once they already have an issue.
Chime in boys, I really want to know what people think.
As someone who reads a lot of help i broke my phone posts the simple fact is that a large number of users if not the majority of noobs refuse point blank to read the instructions .
jje
This is also true. What I am getting at is by making information like this the first thing they would see, it would likely help reduce the "flasher flurry" that some people get into simply because of excitement and ignorance.
For those who don't read simply because they choose not to, we cannot help them. I believe there are many people, however, that proceed with caution, but are not informed enough. Simply saying "I am not responsible for your damaged device" is not enough in my opinion. I would revert to the child near the light socket analogy. It is not a enough to say "hey kid, you stick that fork in the light socket you may or may not be electrocuted - proceed with caution." We can do more, and we should.
I don't disagree about the need for this type of thread, but I'm not sure this is the proper section for it. This type of thread could (and probably should) be discussed across ALL android (and maybe even non-android) devices - not specific to samsung, exynos, touchwiz, etc. As well, it's not really a discussion of process, but more a discussion of how to advertise and support a firmware "product."
So, please explain how the OP fits the section guidelines here: http://forum.xda-developers.com/showthread.php?t=2017367
Thank you
Gary
Probably correct there Gary. If it needs to be moved I apologize. Not sure what I was thinking posting it here... it was late... I was tired lol
A simple solution would be to "hide" the download link in OP, so ppl are forced to read at least some of the OP.but there will always be ppl there is out of reach.
garyd9 said:
I don't disagree about the need for this type of thread, but I'm not sure this is the proper section for it. This type of thread could (and probably should) be discussed across ALL android (and maybe even non-android) devices - not specific to samsung, exynos, touchwiz, etc. As well, it's not really a discussion of process, but more a discussion of how to advertise and support a firmware "product."
So, please explain how the OP fits the section guidelines here: http://forum.xda-developers.com/showthread.php?t=2017367
Thank you
Gary
Click to expand...
Click to collapse
I agree gary, I've moved this to XDA general as this would cover pretty much any device, WP or Android.
I do not know and don't have more time to dig into the details of rooting a phone (although I have already spent hours scrolling here and looking for basic knowledge). However I want to root my new u12+.
I successfully rooted my last phone according to a guide I found on this forum, which was a friendly, step-by-step, detailed guide for noobs like myself: https://forum.xda-developers.com/lg-k10/how-to/friendly-root-method-lg-k8-k10-t3531223
I know there's a guide for u12+ here but it isn't detailed enough which I find it difficult to follow. I am looking forward to a guide which is as detailed as the one above. Please help.
GphonePrince said:
I do not know and don't have more time to dig into the details of rooting a phone (although I have already spent hours scrolling here and looking for basic knowledge). However I want to root my new u12+.
I successfully rooted my last phone according to a guide I found on this forum, which was a friendly, step-by-step, detailed guide for noobs like myself: https://forum.xda-developers.com/lg-k10/how-to/friendly-root-method-lg-k8-k10-t3531223
I know there's a guide for u12+ here but it isn't detailed enough which I find it difficult to follow. I am looking forward to a guide which is as detailed as the one above. Please help.
Click to expand...
Click to collapse
If my guide is too difficult to follow for you, you should probably wait a bit longer until twrp is available. This will make things easier.
But to be honest my guide is pretty detailed and describes each step that needs to be taken.
as already mentioned in the thread you should always research properly before blindly following “friendly” guides.
I think with a tiny bit of research the guide is pretty easy to follow.
with that said, if you face a specific hurdle or question you cannot solve with proper research, just post in my thread and I’m sure myself or somebody else will help you out
Thread moved
Freak07 said:
If my guide is too difficult to follow for you, you should probably wait a bit longer until twrp is available. This will make things easier.
But to be honest my guide is pretty detailed and describes each step that needs to be taken.
as already mentioned in the thread you should always research properly before blindly following “friendly” guides.
I think with a tiny bit of research the guide is pretty easy to follow.
with that said, if you face a specific hurdle or question you cannot solve with proper research, just post in my thread and I’m sure myself or somebody else will help you out
Click to expand...
Click to collapse
it's not only about 'researching properly'.
Thing is, for instance, reading the first few lines from your 'detailed' guide, I already don't know how to obtain the 2 prerequisites:
- latest adb and fastboot binaries
- working adb and fastboot environment
and for the first prerequisite, I already have a bunch of questions to ask despite already researching for hours on XDA:
1. I searched and found something called 15 seconds adb but how can I ensure it's the latest? it was posted a few years ago
2. I know fastboot is a mode which my phone can boot to but what are fastboot 'BINARIES'? what is a binary even? is the thing included in the package I download from the above thread?
3. what is a working adb and fastboot environment and how to obtain/achieve/test whether I have already got it?
and then what are boot images and I couldn't find/download the boot.img of my version. I cannot see mine from the google drive link from another thread - this problem has been described in your thread too
I think more descriptions or download links would be more helpful for guiding us to achieve these - to be more specific, a presentation like the thread of rooting K10 I provided above is what I am looking for. I know it might be just noobs like me who need it but yea, I do need something like this so I would insist on requesting a more 'friendly' and detailed guide of your same method so that I could perform what you are describing in your guide accurately. See if anyone can help if you are not into writing one.
GphonePrince said:
it's not only about 'researching properly'.
Thing is, for instance, reading the first few lines from your 'detailed' guide, I already don't know how to obtain the 2 prerequisites:
- latest adb and fastboot binaries
- working adb and fastboot environment
and for the first prerequisite, I already have a bunch of questions to ask despite already researching for hours on XDA:
1. I searched and found something called 15 seconds adb but how can I ensure it's the latest? it was posted a few years ago
2. I know fastboot is a mode which my phone can boot to but what are fastboot 'BINARIES'? what is a binary even? is the thing included in the package I download from the above thread?
3. what is a working adb and fastboot environment and how to obtain/achieve/test whether I have already got it?
and then what are boot images and I couldn't find/download the boot.img of my version. I cannot see mine from the google drive link from another thread - this problem has been described in your thread too
I think more descriptions or download links would be more helpful for guiding us to achieve these - to be more specific, a presentation like the thread of rooting K10 I provided above is what I am looking for. I know it might be just noobs like me who need it but yea, I do need something like this so I would insist on requesting a more 'friendly' and detailed guide of your same method so that I could perform what you are describing in your guide accurately. See if anyone can help if you are not into writing one.
Click to expand...
Click to collapse
@Freak07 went out of his way to give everyone a VERY user friendly guide for rooting. It really couldn't be simpler. Sorry but if there are things in there you don't understand then it is on you to research it and learn, rather than the responsibility of the community to break it down. If you post your questions people will be more than willing to help explain things but the responsibility is on you.
The guide for rooting really couldn't be easier than what was posted. Very user friendly. If that's still too much than just as Freak said, you should wait for twrp to be available.
GphonePrince said:
it's not only about 'researching properly'.
Thing is, for instance, reading the first few lines from your 'detailed' guide, I already don't know how to obtain the 2 prerequisites:
- latest adb and fastboot binaries
- working adb and fastboot environment
and for the first prerequisite, I already have a bunch of questions to ask despite already researching for hours on XDA:
1. I searched and found something called 15 seconds adb but how can I ensure it's the latest? it was posted a few years ago
2. I know fastboot is a mode which my phone can boot to but what are fastboot 'BINARIES'? what is a binary even? is the thing included in the package I download from the above thread?
3. what is a working adb and fastboot environment and how to obtain/achieve/test whether I have already got it?
and then what are boot images and I couldn't find/download the boot.img of my version. I cannot see mine from the google drive link from another thread - this problem has been described in your thread too
I think more descriptions or download links would be more helpful for guiding us to achieve these - to be more specific, a presentation like the thread of rooting K10 I provided above is what I am looking for. I know it might be just noobs like me who need it but yea, I do need something like this so I would insist on requesting a more 'friendly' and detailed guide of your same method so that I could perform what you are describing in your guide accurately. See if anyone can help if you are not into writing one.
Click to expand...
Click to collapse
it´s all about researching properly! I will demonstarte it to you!
1. if I google "latest fastboot and adb binaries"
https://www.google.com/search?q=latest+adb+and+fastboot+binaries
the very first article from xda points you to a direct download link from google.
https://www.xda-developers.com/google-releases-separate-adb-and-fastboot-binary-downloads/
the article even states that these will remain the latest binaries. But just so you can see the actual version try "adb version" in terminal.
there are many guides on xda on how to set up your fastboot/adb folder/environment depending on your OS! just try to follow one and see if adb/fastboot commands actually work.
2. https://en.wikipedia.org/wiki/Binary_file
the adb and fastboot binaries are the files inside the downloaded package from 1. called adb and fastboot. (the filename extension may vary with your OS)
3. regarding researching
https://forum.xda-developers.com/showthread.php?t=1021205
this was the first link that appeared on a simple google of
"how to check if adb is working"
I think I will include this actually in my guide as it seems a good idea to check if adb/fastboot is working.
Working adb environment can be checked with the command
Code:
adb devices
working fastboot environment with
Code:
fastboot devices
DaConcho said:
@Freak07 went out of his way to give everyone a VERY user friendly guide for rooting. It really couldn't be simpler. Sorry but if there are things in there you don't understand then it is on you to research it and learn, rather than the responsibility of the community to break it down. If you post your questions people will be more than willing to help explain things but the responsibility is on you.
The guide for rooting really couldn't be easier than what was posted. Very user friendly. If that's still too much than just as Freak said, you should wait for twrp to be available.
Click to expand...
Click to collapse
You said freak's guide requires further researching on your first paragraph and then said his guide cannot be more friendly on your second. isn't it contradicting? To the noobs like myself, if it cannot be more friendly, no further researches should be needed just like the example I posted for LG K10. Also, I have never said that it's the responsibility for anyone to break it down. I simple knew that a more detailed guide is possible and requested it. If someone is willing to write one, they will; and if not, then nothing I can do. It was never a burden/responsibility on anyone. Are you hinting that I don't have the rights of requesting a more detailed guide because requesting = believing that it is the the responsibility of someone?
I mean, all I want is also very simple - a step-by-step guide that is as detailed and 'friendly' enough for noobs so that no researches are required as the one for LG K10. I am not here to invoke any disappointments or criticising freak's guide or anything in the first place. I already said it is just not noobs-friendly and it's on the noobs like myself, who couldn't understand/don't have the time to understand freak's guide. I am not blaming/have never blamed anyone. You all don't need to be defensive for freak's guide, it's a good enough guide for non-noobs I acknowledge. Therefore, I standby my request for a more 'friendly' guide for noobs just like the one example I shown above for LG K10. I hope someone understands what I want and would spend some time on writing one, instead of wasting time arguing/defending for "freak's guide is friendly".
Freak07 said:
it´s all about researching properly! I will demonstarte it to you!
Click to expand...
Click to collapse
maybe you're right about researching properly. Again, it's on the noobs being a noob not on you and I appreciate your good work. but still, my main point is, I would like to cordially request a step-by-step guide that is detailed and 'friendly' enough that even noobs can use without further researches just like the example I have shown for LG K10. why? because
1) noobs like me don't have the time/the ability to 'research properly' (I have already spent hours to research, and still encountering problems, and every time I get stuck, I need to ask some nooby questions (which could clearly be solved by simply stating more steps) in the thread and wait for someone to reply and I get stuck nearly every single step. How many more weeks/months do I need to spend on this? I have a very busy schedule.)
2) You have made a great guide for non-noobs, I appreaciate it but the fact is, even it might be the fault of being a noob, only a guide like the one I posted for LG K10 could actually help me rooting my phone. Therefore, I standby my request for a more 'friendly' guide for noobs just like the one example I shown above for LG K10. I hope someone understands what I want and would spend some time on writing one, instead of wasting time arguing/defending for "freak's guide is friendly for all or for experts only".
I am not blaming/have never blamed anyone and don't want to argue. I have only one clear goal from start - a request on a more detailed guide. If you don't want to fulfill my request, that's fine you can just walk away but please stop trying to argue that the forum doesn't need a guide for noobs and drive away potential members who are willing to write them. It is always good for the forum to have both versions, 'noob-friendly rooting guide' and 'rooting guide for experts'.
GphonePrince said:
You said freak's guide requires further researching on your first paragraph and then said his guide cannot be more friendly on your second. isn't it contradicting? To the noobs like myself, if it cannot be more friendly, no further researches should be needed just like the example I posted for LG K10. Also, I have never said that it's the responsibility for anyone to break it down. I simple knew that a more detailed guide is possible and requested it. If someone is willing to write one, they will; and if not, then nothing I can do. It was never a burden/responsibility on anyone. Are you hinting that I don't have the rights of requesting a more detailed guide because requesting = believing that it is the the responsibility of someone?
I mean, all I want is also very simple - a step-by-step guide that is as detailed and 'friendly' enough for noobs so that no researches are required as the one for LG K10. I am not here to invoke any disappointments or criticising freak's guide or anything in the first place. I already said it is just not noobs-friendly and it's on the noobs like myself, who couldn't understand/don't have the time to understand freak's guide. I am not blaming/have never blamed anyone. You all don't need to be defensive for freak's guide, it's a good enough guide for non-noobs I acknowledge. Therefore, I standby my request for a more 'friendly' guide for noobs just like the one example I shown above for LG K10. I hope someone understands what I want and would spend some time on writing one, instead of wasting time arguing/defending for "freak's guide is friendly".
maybe you're right about researching properly. Again, it's on the noobs being a noob not on you and I appreciate your good work. but still, my main point is, I would like to cordially request a step-by-step guide that is detailed and 'friendly' enough that even noobs can use without further researches just like the example I have shown for LG K10. why? because
1) noobs like me don't have the time/the ability to 'research properly' (I have already spent hours to research, and still encountering problems, and every time I get stuck, I need to ask some nooby questions (which could clearly be solved by simply stating more steps) in the thread and wait for someone to reply and I get stuck nearly every single step. How many more weeks/months do I need to spend on this? I have a very busy schedule.)
2) You have made a great guide for non-noobs, I appreaciate it but the fact is, even it might be the fault of being a noob, only a guide like the one I posted for LG K10 could actually help me rooting my phone. Therefore, I standby my request for a more 'friendly' guide for noobs just like the one example I shown above for LG K10. I hope someone understands what I want and would spend some time on writing one, instead of wasting time arguing/defending for "freak's guide is friendly for all or for experts only".
I am not blaming/have never blamed anyone and don't want to argue. I have only one clear goal from start - a request on a more detailed guide. If you don't want to fulfill my request, that's fine you can just walk away but please stop trying to argue that the forum doesn't need a guide for noobs and drive away potential members who are willing to write them. It is always good for the forum to have both versions, 'noob-friendly rooting guide' and 'rooting guide for experts'.
Click to expand...
Click to collapse
So I took a look at the guide you linked us to.
Half of the links are deleted by a moderator. They probably pointed to some videos that are not allowed on XDA, because they generate income of some sort. So it seems to me.
Personally I feel that my guide is as detailed as the one you linked. And less confusing.
My guide explains how to root the your U12+ (with the current state of things - means no fully working TWRP) and a ton more things. I intentionally left out how to unlock your bootloader, set up adb and fastboot. The simple reason is that there are tons! of guides out on XDA which are just a simple XDA or Google search away.
Ultimately XDA is a place to learn and strive forward as a community. You don´t want to learn, you just want a guide that explains every little detail. ( at best with photos and videos) If you don´t have the time to research at least a little bit, my offer still stands. Wait for a working TWRP as it will simplify the matter.
We already explained to you, there are many people that answer specific questions that arise on your path. Other people profit from these answered questions, in case you ask them and post them in the corresponding thread.
I already answered your last 3 questions. So you should at least be able to start and see where it brings you.
I´m also not deaf to any valuable feedback. I already added that "how to check if adb is actually working" to the guide as it seemed a good idea to me.
So please feel free to contribute, what´s ultimately the purpose of a community.
The other question were asked and answered. If there is no firmware zip for your current firmware version, wait until it is uploaded or kindly ask in the firmware thread if anybody is able to share it.
Otherwise there is a bit of risk involved because you have no way of obtaining the stock boot.img from your current firmware.
here is answered what a boot.img is
https://stackoverflow.com/questions/21173628/what-is-boot-img-file-in-android
I even give you one more information. Because this is an A/B device with a bit of a different partition layout, the recovery, which usually has its own partition, sits in the ramdisk, which is part of the boot.img.
Freak07 said:
So I took a look at the guide you linked us to.
Half of the links are deleted by a moderator. They probably pointed to some videos that are not allowed on XDA, because they generate income of some sort. So it seems to me.
Personally I feel that my guide is as detailed as the one you linked. And less confusing.
My guide explains how to root the your U12+ (with the current state of things - means no fully working TWRP) and a ton more things. I intentionally left out how to unlock your bootloader, set up adb and fastboot. The simple reason is that there are tons! of guides out on XDA which are just a simple XDA or Google search away.
Ultimately XDA is a place to learn and strive forward as a community. You don´t want to learn, you just want a guide that explains every little detail. ( at best with photos and videos) If you don´t have the time to research at least a little bit, my offer still stands. Wait for a working TWRP as it will simplify the matter.
We already explained to you, there are many people that answer specific questions that arise on your path. Other people profit from these answered questions, in case you ask them and post them in the corresponding thread.
I already answered your last 3 questions. So you should at least be able to start and see where it brings you.
I´m also not deaf to any valuable feedback. I already added that "how to check if adb is actually working" to the guide as it seemed a good idea to me.
So please feel free to contribute, what´s ultimately the purpose of a community.
The other question were asked and answered. If there is no firmware zip for your current firmware version, wait until it is uploaded or kindly ask in the firmware thread if anybody is able to share it.
Otherwise there is a bit of risk involved because you have no way of obtaining the stock boot.img from your current firmware.
here is answered what a boot.img is
https://stackoverflow.com/questions/21173628/what-is-boot-img-file-in-android
I even give you one more information. Because this is an A/B device with a bit of a different partition layout, the recovery, which usually has its own partition, sits in the ramdisk, which is part of the boot.img.
Click to expand...
Click to collapse
Despite already answered by you, since that actually further brings up tons of follow up questions of mine, mind leaving me your instant messaging contact? Like WhatsApp or telegram or discord etc. As you have admitted, your guide needs tons of further researching (as you know there are tons of articles but I don't know which one is the one I'm looking for and suitable for my phone) and the link I have as an example doesn't (deleted links were screenshots and YouTube videos by the op). is not I am expecting rapid back and forth asking and clarifying into details on each question. Asking in the forum is too slow and not time efficient
GphonePrince said:
Despite already answered by you, since that actually further brings up tons of follow up questions of mine, mind leaving me your instant messaging contact? Like WhatsApp or telegram or discord etc. As you have admitted, your guide needs tons of further researching (as you know there are tons of articles but I don't know which one is the one I'm looking for and suitable for my phone) and the link I have as an example doesn't (deleted links were screenshots and YouTube videos by the op). is not I am expecting rapid back and forth asking and clarifying into details on each question. Asking in the forum is too slow and not time efficient
Click to expand...
Click to collapse
No sorry I won´t do that. If this forum is too time inefficient for you, you can look elsewhere for a more detailed guide or wait until a better one appears here that suits your needs.
You´re asking others to invest time so you can save your own time. You´re asking for knowledge from people, who invest time to obtain this knowledge. Part of this forum is to post questions here, so others can actually profit from the questions answered. Just like you would profit if you´d actually start searching here.
And please don´t put any words into my mouth, that I never said. My guide doesn´t need "tons" of research, just because there are more than enough guides out there.
We can stop here, because you´re clearly asking for a thing which XDA is not about.
If anyone else steps up and writes a more detailed guide that person is very welcome to do so I´m not preventing anyone.
Freak07 said:
No sorry I won´t do that. If this forum is too time inefficient for you, you can look elsewhere for a more detailed guide or wait until a better one appears here that suits your needs.
You´re asking others to invest time so you can save your own time. You´re asking for knowledge from people, who invest time to obtain this knowledge. Part of this forum is to post questions here, so others can actually profit from the questions answered. Just like you would profit if you´d actually start searching here.
And please don´t put any words into my mouth, that I never said. My guide doesn´t need "tons" of research, just because there are more than enough guides out there.
We can stop here, because you´re clearly asking for a thing which XDA is not about.
If anyone else steps up and writes a more detailed guide that person is very welcome to do so I´m not preventing anyone.
Click to expand...
Click to collapse
I remember once there was a chat group for rooting a phone on stacks, WhatsApp or discord. Why not make one for u12+ to ease everyone? It's 2018, maybe the mode of forum isn't fast enough and needs to be changed. Forum is for complete detailed guides. But if you insist, this thread can become one with hella short questions and answer posts. That's also not aesthetical. Also, do think about your initial aim of releasing a guide. isn't it helping others who don't know how to root u12+? if so, why declining an even effective way of teaching people (me) by allowing me to send you my questions instantly whenever I encounter problems following your guide? Or, which you should disagree with, is it only for your self-gratification to gain recognition from others in this 'community'?
Anyway, even you are not physically preventing anyone from fulfilling my request, what you said already to a certain extent have driven potential writers away. It's actually kinda selfish because it's totally fine if you are not writing one but you don't have to drive people away from writing one. Anyway, so, provided no hopes on anyone writing a rooting guide for noobs, let me start my follow up questions although as I have expected, I will be asking for every small detail which probably most of the experts here already know because I don't have the ability to research properly (I did researched for more hours but I still can't find my answers). I said to 'save time' means to use time effectively - if I use my time to research and actually get what I am looking for, time is not wasted; but if I cannot reach what I want anyway after spending the time, it is wasted.
GphonePrince said:
I remember once there was a chat group for rooting a phone on stacks, WhatsApp or discord. Why not make one for u12+ to ease everyone? It's 2018, maybe the mode of forum isn't fast enough and needs to be changed. Forum is for complete detailed guides. But if you insist, this thread can become one with hella short questions and answer posts. That's also not aesthetical. Also, do think about your initial aim of releasing a guide. isn't it helping others who don't know how to root u12+? if so, why declining an even effective way of teaching people (me) by allowing me to send you my questions instantly whenever I encounter problems following your guide? Or, which you should disagree with, is it only for your self-gratification to gain recognition from others in this 'community'?
Anyway, even you are not physically preventing anyone from fulfilling my request, what you said already to a certain extent have driven potential writers away. It's actually kinda selfish because it's totally fine if you are not writing one but you don't have to drive people away from writing one. Anyway, so, provided no hopes on anyone writing a rooting guide for noobs, let me start my follow up questions although as I have expected, I will be asking for every small detail which probably most of the experts here already know because I don't have the ability to research properly (I did researched for more hours but I still can't find my answers). I said to 'save time' means to use time effectively - if I use my time to research and actually get what I am looking for, time is not wasted; but if I cannot reach what I want anyway after spending the time, it is wasted.
Click to expand...
Click to collapse
please don´t get personal with your arguments.
everyone, including you, is free to start such a chat! Open it up and get it going. It´s just, that I won´t start it nor will I maintain or support it.
Again my guide is complete and detailed. and if there is indeed something missing or a little change to be made to make it a bit more polished I will update it. As I already did.
Feel free to ask your questions in the thread and I´m sure they will be answered at some point. Then everyone can profit from your research and from the questions and answers that arose while doing the research.
time spent on researching is never wasted. even if you don´t find all answers swiftly it is never wasted. The journey is the reward!
Thread closed. This seems to have become a thread less focussed on finding an answer and more so on flaming your peers. Given that that seems to be the case for the entire thread, there is no point in leaving this open if all it is going to do is cause excessive drama.
Thank you,
RJ
Forum Moderator
Sadly after years of being on XDA, the threads here are still a mess. Especially if you're looking for information about what variants to get or avoid, if you want to achieve root or custom rom.
I simply want a sticky FAQ thread on each device category detailing vital information like: variants for rooting or custom roms, updates to avoid that breaks exploit to achieve root, etc.
I envy Reddit for having this system implemented by users voluntarily. Like for example, if you go to the Nintendo Switch Hacks subreddit, they have a FAQ thread there detailing everything you ned to know about hacking the Nintendo Switch. But here in XDA, it's always a mess. I have to go through a lot threads just to find the answer I'm looking for. I hope this system gets implemented.
noddledizzy said:
Sadly after years of being on XDA, the threads here are still a mess. Especially if you're looking for information about what variants to get or avoid, if you want to achieve root or custom rom.
I simply want a sticky FAQ thread on each device category detailing vital information like: variants for rooting or custom roms, updates to avoid that breaks exploit to achieve root, etc.
I envy Reddit for having this system implemented by users voluntarily. Like for example, if you go to the Nintendo Switch Hacks subreddit, they have a FAQ thread there detailing everything you ned to know about hacking the Nintendo Switch. But here in XDA, it's always a mess. I have to go through a lot threads just to find the answer I'm looking for. I hope this system gets implemented.
Click to expand...
Click to collapse
There have been several attempts at something like this, which always fails for lack of volunteers.
sd_shadow said:
There have been several attempts at something like this, which always fails for lack of volunteers.
Click to expand...
Click to collapse
What a shame.
noddledizzy said:
What a shame.
Click to expand...
Click to collapse
My advice, if you want a Sticky thread, start a thread and ask that it gets pinned to the top.
If you are looking for a thread template see
The Index Project
and
The FAQs Project
Many of my threads are stickies.
I wasn't asked to create them, and most of them, I requested that they be stuck to the top.
One of the biggest problems is many people don't keep their phones very long anymore. They move on to the next phone So, they don't keep their threads up to date.
sd_shadow said:
My advice, if you want a Sticky thread, start a thread and ask that it gets pinned to the top.
If you are looking for a thread template see
The Index Project
and
The FAQs Project
Click to expand...
Click to collapse
I could do that, but it'll be pointless if I am the only one to do it. I wish XDA users have the same mentality as redditors.
About not being updated since people move on to different devices, it's not really a problem since informations such as what variants are rootable, or any simple info like that that does not change. Thank you for reading
Custom ROMs are always changing. It's not really feasible to keep an FAQfor things like that. It would be forever changing.
A Switch is a Switch, and info found in an FAQ will always be relevant. But smartphones are a different beast. Updates, new versions etc mean the FAQ would need updated on a weekly or close to daily bais on newer devices.
It's a good idea in theory, and some forums have or had them. But it's too much work for members.
Plus a lot of it is subjective. There's no "best" or better ROM. A lot is really personal preference. Most of the info you're talking about is already in each forum throughout the various threads. You just need to doa bit of reading.