Related
dear all even senior and moderator your majesty are invited to share to find a commun way to fix our stuck breeze...
so i'm inviting you all " one's who succed to repair their breeze" to share their experience with us to be be able to repair many stuck breeze to reach the ultimate goal of this site: xda-developers the most expert in ppc and pda phone ..........
Sorry; What?
hotrod101 said:
Sorry; What?
Click to expand...
Click to collapse
what you didn't understand???.....
did you ever had a bricking problem with your breeze and you succeed to repair your device...
so you and all the other who had the same problem are invited to share their experience to find a final solution to repair our breeze and o be able to flash a ROM...
is it clear enough to you...
moiisse said:
what you didn't understand???.....
did you ever had a bricking problem with your breeze and you succeed to repair your device...
so you and all the other who had the same problem are invited to share their experience to find a final solution to repair our breeze and o be able to flash a ROM...
is it clear enough to you...
Click to expand...
Click to collapse
I am sorry that you got offfended. Wait a minute, no I'm not. I see that you have edited your post above. Good because it made absolutely no sense the way you first wrote it. It seemed to be something that was written by a 10 year old. Your spelling and grammar are horrible. Just look at the post I quoted. "did you ever had a ...." -
I will rewrite it for you.
"Have you ever bricked your Breeze and then successfully repaired your device. If so, please share your experience and step by step instructions taken to fix your device in this thread to help those less cerebrally gifted like myself to fix our own devices, because we just don't have a clue."
Is this clear for you?
I have taken the liberty to check out your posting behaviour. You seem to have been having problems for quite some time but have not gotten a straight answer and for that I am sorry for you. I cannot help you because:
1. I do not own a Breeze
2. I don't have much experience with flashing custom ROM's and have never Bricked my device, (Because I am really careful and do lots and lots of reading in these forums to learn everything I need to learn before doing anything.)
When I responded to your post, I was only trying to help you by getting you to be more clear with what your problem was and what you wanted out of this thread. It really made absolutely no sense the way you had orriginally written it. With this attitude you have - you might find it difficult to get anyone to help you.
Good bye... Good luck. I hope you get what you are looking for
hotrod101 said:
I am sorry that you got offfended. Wait a minute, no I'm not. I see that you have edited your post above. Good because it made absolutely no sense the way you first wrote it. It seemed to be something that was written by a 10 year old. Your spelling and grammar are horrible. Just look at the post I quoted. "did you ever had a ...." -
I will rewrite it for you.
"Have you ever bricked your Breeze and then successfully repaired your device. If so, please share your experience and step by step instructions taken to fix your device in this thread to help those less cerebrally gifted like myself to fix our own devices, because we just don't have a clue."
Is this clear for you?
I have taken the liberty to check out your posting behaviour. You seem to have been having problems for quite some time but have not gotten a straight answer and for that I am sorry for you. I cannot help you because:
1. I do not own a Breeze
2. I don't have much experience with flashing custom ROM's and have never Bricked my device, (Because I am really careful and do lots and lots of reading in these forums to learn everything I need to learn before doing anything.)
When I responded to your post, I was only trying to help you by getting you to be more clear with what your problem was and what you wanted out of this thread. It really made absolutely no sense the way you had orriginally written it. With this attitude you have - you might find it difficult to get anyone to help you.
Good bye... Good luck. I hope you get what you are looking for
Click to expand...
Click to collapse
thank you for your english and grammar correction...
sorry that you couldn't help me...
happy that you didn't ever brick your device...
and about my attutude i see that you saw my posting behavior, which show why i'm so Angry, ( i bricked my device, that i don't have any experience in the world of smartphone, and i wasn't carefull before trying to upgrade it...)
and finally, thank you for wishing me good luck
hope to get a straight aswer....
best regards Moiisse
Have you read this thread - May be helpful. I have not read it fully; however, noticed that you have not posted in it.
http://forum.xda-developers.com/showthread.php?t=387522
If you have any questions about the process described, may I suggest in addition to posting in the thread itself, send a private message to jerpelea as he created this thread and Guide. You will have to try to provide as much information as possible to him / her - What you did? how you did it? etc... What rom you were trying to flash. Answer any questions he asks and don't get frustrated with him / her if it takes time for him / her to figure out what happened to your device. You have to remember that you did this to your device / not anyone else and you are the one with the device in front of you. Be patient - Listen to their advice, follow their instructions - answer their questions - don't give up and start looking for someone else to help you out because you will just annoy people and will have to start all over again explaining your situation. If you want your device fixed then you need to listen up and stop being so aggressive - it puts people off and pushes them away. I know that it is frustrating, but look - your tactics have not been working so far. I have seen in several threads that there were some people trying to help you but you just disappeared from that thread before they could finish. You had failed to answer some peoples questions . Remember, they need to know what is what before giving you direction because the last thing they want to do is rush you into doing something that might actualy permanently brick your device. Also remember that it will not be a quick fix - May take several days / weeks as most people here have lives outside of this forum. USE Private messaging though once you have found someone who will take the time to guide you. If you try to rush it - you might truely end up with a paper weight
There is also a lot of information in the WIKI here. I strongly urge you to read all of this to learn everything there is to learn about your device. It will not only possibly lead to helping you figure out how to solve your problem, but also help you to understand what others are asking you with regards to your device.
WIKI - http://wiki.xda-developers.com/index.php?pagename=HTC_Breeze
hotrod101 said:
Have you read this thread - May be helpful. I have not read it fully; however, noticed that you have not posted in it.
http://forum.xda-developers.com/showthread.php?t=387522
If you have any questions about the process described, may I suggest in addition to posting in the thread itself, send a private message to jerpelea as he created this thread and Guide. You will have to try to provide as much information as possible to him / her - What you did? how you did it? etc... What rom you were trying to flash. Answer any questions he asks and don't get frustrated with him / her if it takes time for him / her to figure out what happened to your device. You have to remember that you did this to your device / not anyone else and you are the one with the device in front of you. Be patient - Listen to their advice, follow their instructions - answer their questions - don't give up and start looking for someone else to help you out because you will just annoy people and will have to start all over again explaining your situation. If you want your device fixed then you need to listen up and stop being so aggressive - it puts people off and pushes them away. I know that it is frustrating, but look - your tactics have not been working so far. I have seen in several threads that there were some people trying to help you but you just disappeared from that thread before they could finish. You had failed to answer some peoples questions . Remember, they need to know what is what before giving you direction because the last thing they want to do is rush you into doing something that might actualy permanently brick your device. Also remember that it will not be a quick fix - May take several days / weeks as most people here have lives outside of this forum. USE Private messaging though once you have found someone who will take the time to guide you. If you try to rush it - you might truely end up with a paper weight
There is also a lot of information in the WIKI here. I strongly urge you to read all of this to learn everything there is to learn about your device. It will not only possibly lead to helping you figure out how to solve your problem, but also help you to understand what others are asking you with regards to your device.
WIKI - http://wiki.xda-developers.com/index.php?pagename=HTC_Breeze
Click to expand...
Click to collapse
thanks for your reply...
sorry for my week english....
despite i didn't post in both, but i tried what is mentioned in these 2 posts, and i didn't succed to fix my imate spjas...
desperate... do i have to throw down my device????
is their a way to fix it, is their for exampl a no vender id RUU or something like i can use it to repair either my bootloader and update any rom i want....
asking for you, and all who has enough experience in building a rom, or whatever to find a way a universal way to repair our devices....
thank you, and thx for all who can help, and post a solution....
I am sorry that I cannot help you, I just don't know about your device or ROM upgrading. You seem to be very desperate and let your emotions get the best of you in your posts. This with the language barrier can make it very difficult. I really hope that someone here who is capable of helping you can be patient enough with you to help you. You have to remember to be patient to with them though or they will just walk away and leave you with a device that doesn't work.
If no one here can help you, what about taking your device in for service. I don't know how long you have had your device for (Warranty) (Upgrade to a new device that works)
Good luck
hotrod101 said:
I am sorry that I cannot help you, I just don't know about your device or ROM upgrading. You seem to be very desperate and let your emotions get the best of you in your posts. This with the language barrier can make it very difficult. I really hope that someone here who is capable of helping you can be patient enough with you to help you. You have to remember to be patient to with them though or they will just walk away and leave you with a device that doesn't work.
If no one here can help you, what about taking your device in for service. I don't know how long you have had your device for (Warranty) (Upgrade to a new device that works)
Good luck
Click to expand...
Click to collapse
thank you very much for your help...
i'm sure that their is other's with the same problem...
hope to find someone that can help us...
I've been trying to figure out on the forums which device has which path to get root and wow it doesn't make sense to me. I'm no noobie but I don't get all the updates and processes.
I just want root so i can use Xposed. i don't care about loading different roms or kernels.
I bought it from swappa. It has android version 4.4, system 140.44.5.ghost_att.en.US, Build 13.11.1Q2.X-69-3
this thing sucks HARD without root. there is so much you could do that you can't. It astounds me how diligently manufacturers and carriers are about preventing you from using the phone to its fullest. So i void a warranty, i don't care...
a10fjet said:
I've been trying to figure out on the forums which device has which path to get root and wow it doesn't make sense to me. I'm no noobie but I don't get all the updates and processes.
I just want root so i can use Xposed. i don't care about loading different roms or kernels.
I bought it from swappa. It has android version 4.4, system 140.44.5.ghost_att.en.US, Build 13.11.1Q2.X-69-3
this thing sucks HARD without root. there is so much you could do that you can't. It astounds me how diligently manufacturers and carriers are about preventing you from using the phone to its fullest. So i void a warranty, i don't care...
Click to expand...
Click to collapse
I have an AT&T Moto X running Kit Kat 4.4 (from OTA) and I'm also not clear on whether I can root my phone. I'm also unclear about whether I can unlock my phone
I would also appreciate guidance and direction.
Many thanks!
The AT&T branded Moto X cannot be unlocked, but the GSM unlocked DE will work on AT&T and is unlockable. The TMobile Moto Maker Moto X will work on AT&T and has an unlockable bootloader, too, but if you unlock the bootloader on it, your warranty is void. So I would stick with the GSM unlocked DE. There may be some issues with 4G LTE on AT&T using the TMobile devices but I am not sure. That is probably covered in the forum somewhere if there are any issues.
Click to expand...
Click to collapse
Okay, so I can root, but not unlock. I think I'll wait till an easier and simpler root method is developed like there was for my Samsung GS2.
I appreciate the guidance.
CartlandSmith said:
We are lucky to even have this method. Google is making Android more and more secure by incorporating SELinux. If a root method for 4.4.2 is ever found, it will likely be even more complicated.
4.4 Security Enhancements
Also, the dev who came up with the current root method, jcase, is not interested in finding a root method for Motorola phones running 4.4.2.
So rooting now is likely your only chance at rooting. If you take the 4.4.2 OTA unrooted, it is doubtful you will ever be able to gain root because the 4.4.2 bootloader is not downgreadable.
Since the developer edition phones are so readily available from Motorola at such a good price and since only AT&T and Verizon retail/customized phones are not unlockable, there isn't much interest in trying to find a way to root locked Motorola phones running 4.4.2. Sprint, US Cellular and TMobile retail/customized Moto X's are unlockable as are the developer edition Moto X's.
Click to expand...
Click to collapse
Thanks for the thoughtful and informed reply, Cartland. My last phone was a Samsung GS2 and it was easy to root (all automated). Though I have rooted and flashed ROMs on a number of phones, this process seems complicated and readily screw-upable (not a real word, I admit). I like being rooted, so I can flash tweaked-out ROMs that are better than stock.
I'll explore rooting more and see how comfortable I am with it.
Much appreciated.
CartlandSmith said:
We are lucky to even have this method. Google is making Android more and more secure by incorporating SELinux. If a root method for 4.4.2 is ever found, it will likely be even more complicated.
4.4 Security Enhancements
Also, the dev who came up with the current root method, jcase, is not interested in finding a root method for Motorola phones running 4.4.2.
So rooting now is likely your only chance at rooting. If you take the 4.4.2 OTA unrooted, it is doubtful you will ever be able to gain root because the 4.4.2 bootloader is not downgreadable.
Since the developer edition phones are so readily available from Motorola at such a good price and since only AT&T and Verizon retail/customized phones are not unlockable, there isn't much interest in trying to find a way to root locked Motorola phones running 4.4.2. Sprint, US Cellular and TMobile retail/customized Moto X's are unlockable as are the developer edition Moto X's.
Click to expand...
Click to collapse
CartlandSmith said:
It takes some time to do it. I did it on a relative's phone. There are unfortunately some pointers that are left out of the original posts that help everything to go smoothly if you know them. You can find them in the threads, but the threads have gotten so long it makes the process take longer when you have to read through them to find all of the pointers.
If you are only flashing using RSD Lite - RSD Lite will stop you from bricking your phone.
You are never going to get a simpler method with a locked bootloader Motorola phone - it is only going to get harder and I predict the devs won't invest much energy in it going forward because it is just not worth it when there are developer editions available to us. I think those that are doing it get a kick out of it, but when it becomes too time consuming, well, they have their day jobs they have to make sure they focus enough time on to pay their bills. They get donations for this sort of thing, but I am sure the donations don't compensate them very well for all of the time they take trying to find exploits the more secure Android becomes.
With a locked bootloader, you can't flash ROMs because you don't have a custom recovery. But what you can do it use Xposed Framework and its modules like Gravity Box if you are rooted.
I spent some time this weekend rooting a relative's Verizon Moto X with a locked bootloader due to the 4.4.2 OTA coming. You have some breathing room on AT&T right now to root, but don't wait too long or you will lose the opportunity once the OTA comes.
Click to expand...
Click to collapse
I don't think I have the time or energy to go through the process of finding those pointers and then going through the root method. I'm wondering if anyone will compile those pointers (as you suggest, I have noticed with previous rooting and flashing methods, some key steps aren't described which can cause major problems).
A clarification. You say that if I just want to flash ROMs, I can use RSD Lite. But then you say that with a locked bootloader, you can't flash ROMs.
I do appreciate your taking the time.
POINTER - sell or trade your phone for a Dev edition
It is difficult to root if you can't unlock your bootloader. There is a thread in this forum telling you how to root your device with both locked and unlocked bootloader.
Rooting this device isn't difficult. If you can read and type verbatim, letter for letter, you can get root. People need to stop psyching themselves and others out.
CartlandSmith said:
Yes you can get root, but it takes a bit of work
First you have to downgrade to 4.2.2 by flashing the sbf firmware for your device.
Click to expand...
Click to collapse
can you specify what sbf is? searching didn't help. Try not to use so many acronyms for us dummies.
CartlandSmith said:
Then use RockMyMoto to get root on 4.2.2. Then use MotoWPNoMo to disable write protection.
Then reflash 4.2.2 and use SlapMyMoto.
Click to expand...
Click to collapse
do i use ODIN? what do i use to flash?
CartlandSmith said:
You will be rooted on 4.4 and write protection will be disabled when you are done with all of that.
Once you have root, be sure and freeze MotorolaOTA to stop the 4.4.2 OTA. If you take the 4.4.2 OTA, you may keep root, but write protection will be enabled.
Click to expand...
Click to collapse
Does motorolaOTA automatically download the latest updates and install them without warning you?
thanks for giving me hope!
EDIT: does anyone know if http://forum.xda-developers.com/moto-x/orig-development/script-root-moto-x-root-script-locked-t2603051 will work?
I'm getting close to knowing what to do!
But the individual steps are not very well written.
For example on the RockMyMoto page, he just starts giving you commands. He doesn't tell you what to type them into. In the video, everything is already open. I tried the command in cydia impactor and it didn't do anything. I though maybe you do it in adb, I don't really know what that is but I found adb.exe and launched it but the command window it opens goes through a bunch of commands and then closes. I can't even get past step one because he never said how he got to the point where he starts!
CartlandSmith said, in the third post, that i am supposed to reflash 4.2.2 at the end.. Did he mean 4.4? Or 4.2.2 then slapmymoto then take 4.4 over the air?
It would be really helpful (to me at least) if someone could put step by step instructions. Like humiliatingly degradingly redundant instructions for a complete idiot. I will put them up if I ever figure it all out. It's so frustrating when the instructions are so detailed from where they start, but they never show you how they got to where they are.
Thanks to everyone for the help.
EDIT: probably stupid question but does the phone ever need to be connected by USB? none of the posts mention it but all other devices i've used needed it. adb (here is a tutorial)/ isn't recognizing my device with USB connection or not. Both connected to same router, all drivers and everything updated, Debugging enabled...
No offense intended...at all....but if you value your phone, you really need to study up and read LOTS of stuff here. Until you understand what you are about to do, don't do anything.
Just trying to save you from a bricked phone. You seem very unsure of everything at this point. No one can post anything here that isn't already covered in the guides. Look at the stickies, complete Moto x guide is there.
Good luck.
Sent from my Nexus 5 using Tapatalk
Hmm i rebooted my computer and factory reset my X and now everything is connecting. Guess you should always try the IT Crowd's advice before doing anything else lol
I agree that everything is covered on this site, it's just not organized.
It seems unorganized when you don't understand. Read enough of it and it all makes sense eventually. This has everything about bootloaders, rooting...etc. BUT, you need to know what applies to your situation. And again...that comes when you understand the stuff.
http://forum.xda-developers.com/showthread.php?t=2603358
Sent from my Nexus 5 using Tapatalk
CartlandSmith said:
It's even more clear how unorganized the info here is the more educated you become.
The thing that becomes the most clear eventually is how much misinformation is posted.
Sorry but the "it only appears disorganized and unreadable and full of misinformation" because you don't understand it won't fly with those of us who do understand it.
Click to expand...
Click to collapse
The OP of the thread I linked is well organized. Its about the only one that is. Its also stickied, so should be incredibly easy to find.
As far as misinformation goes, that's due to people being quick to post advice when they clearly don't have a handle on this stuff themselves.
How to avoid the clutter and misinformation? Maybe point people to good threads that already exist instead of filling new ones with more misinformation. No? Or God forbid, suggest they search for the information that already exists? Instead of helping to grow yet another repeated thread with both good and poor information within it.
Xda's number one rule was created for a reason. To keep clutter and thread after thread of similar content to a minimum. A lot of inaccurate information gets repeated over and over as well. But, so many refuse to search cause its too much work, and just as many others condone this behavior by answering.
I know most don't agree with what I'm saying, as the forums prove with the repeated information here in truck loads. And I also know when any of us remind people of rule number one here on xda....we're called trolls, flamers and much worse....even when the reminder was posted respectfully.
So who exactly are the flamers? LOL
Its looking like reminding members to search and read and actually help them help themselves is becoming a dangerous practice. I'm tired of the misinformation and cluttered forums....and if reminding is just going to start drama at every turn, I suppose reporting the offenders is the easier option. Tho not my first choice.
But if you read this carefully, you'll see I'm completely agreeing with you. LOL. So lets agree to agree and leave it at that.
And as a member who's been around a while, I won't stop doing my part to try to cut down the misinformation and lack of respect for the xda rules. Not abiding by rule number one is EXACTLY why the mess of confusing information exists. You see that, right?
If the newer members want to make me the bad guy for this, fine. I'll be the bad guy.
And I help more people here than most as well.....but that's forgotten if you disagree with anyone or remind anyone of the rules here. Fine. Again.....call me the bad guy. Better get used to it too, I'm not going anywhere.
I'd apologize for the off topic, but this thread should have been closed anyway.
Have a good one!
Sent from my Nexus 5 using Tapatalk
CartlandSmith said:
The most confusing thing of all is why someone with a Nexus 5 self-appoints themselves to be the "hall monitor" of the Moto X forums. *shrugs*
Click to expand...
Click to collapse
Um, perhaps I own both.
How bout you drop it and stop commenting on multiple posts of mine since you appear to dislike the things I say. K?
Try the ignore member feature.
Sent from my Nexus 5 using Tapatalk
Please search before posting
Check the sticky guides before asking questions about rooting
Thanks
FNSM
kennyglass123 said:
Please search before posting
Check the sticky guides before asking questions about rooting
Thanks
FNSM
Click to expand...
Click to collapse
Ninja'd .....:good:
So, after looking around the threads, I've noticed that it is apparently possible to root an S6A running the 5.02, which mine is, because I never bothered to update it. However, I only found bits and pieces of info, and am in need of a clear guide if possible. I am only a poweruser, and my programming knowledge is limited to gaming mods and one time when I made a batch file to use my printer as an alarm clock, so I need something I can understand as a lowly wannabe nerd. Anywho, I'd be very grateful to anyone who could help me out by explaining the process. Help me XDA-Developers, you're my only hope.
P.S. I'm not overly concerned with voiding a warranty or messing up Knox, I use a BlackBerry as my primary device and as such all my important junk is on it, so as long as I can de-bloat and use root apps, I'll be very happy.
P.P.S. I apologize in advance if I overlooked a good rooting guide, I looked around for a good ten minutes before posting this, but didn't see anything, however this may simply be due to my own ineptitude.
P.P.P.S. Also, my device doesn't have a SIM, I use it as wifi only, I don't know if that's important, but I thought I might should mention it.
Hi everyone. I'm new to the forum, and new to all of this, so please forgive my ineptness and general cluelessness.
I have a Samsung Galaxy S5 Active (AT&T version) model SM-G870A. It was running 5.1.1 but was rooted. It also had debugging checked.
I was getting really irritated with all the bloatware that was installed by Samsung and AT&T because I hated opening my apps drawer and having to wade through panel after panel of useless apps. Not only this, but they ate up far too much of the space and resources on my device. And, just out of principal, the phone belongs to me. I paid cash for it, I don't have any kind of contract with AT&T, so why should they force me to have all their useless junk on my phone?
At first, I would have been happy just debloating it. So I used Dr.Fone to root it, and then I attempted to get rid of all the unwanted apps using Debloater by Gatesjunior. Long story short, I've now managed to get my phone into bootloop. Since then I've tried the different solutions recommended on XDA and nothing has worked so far for me.
At this point, I'd prefer just to be able to flash a custom rom for my phone, but honestly, if I can't do this I would be happy just to go back to where I was before this whole ordeal started... me with a functioning phone (albeit, full of useless bloatware). It would be horrible to admit defeat to AT&T, but I just want a working phone now
Any advice?
Thanks.
Bump.
Nobody? The post has gotten 59 views so far. I mean, I know it's not a hot new model S8, but can nobody point me in the right direction? I'd really appreciate it as this is the only phone I have, I like it despite all the bloatware it had, and I can't afford another. Or is it only worth throwing in the bottom of some drawer to collect dust?
Thanks.
111 views now and still no suggestions or advice. Seems there are loads of helpful people replying to other requests for help. I'm not sure what's different about this.
Read read read .... There is currently NO root method for the active this is stated over and over on this forum . You should be able to use Odin and flash a stock non rooted firmware ....again there are several posts and threads explaining this in detail ....good luck .... Do some searching and reading before making posts whining about no one helping you ....
I did read read read as you say. I did lots of searching, lots of reading, and tried lots of the suggestions (including flashing factory firmware with Odin) and nothing's worked. I also said in my original post that I'm not a phone enthusiast, I don't know anything about this stuff. I thought the point to the site was that there were advanced users and developers who wouldn't mind helping out the clueless. But no, everything I've read is quite cryptic in its terminology as to be basically opaque to most but it's spoke of in a way that's clearly meant for an audience with a similar knowledge base. I mean, I just wanted all the extra crap off my phone, I wasn't hoping to hack it into The Superphone, I got in over my head, and I realize I should have just left it alone. Don't open a watch unless your job is fixing watches. I understand that this is a site supported mostly by niche enthusiasts. Phones are your fun (which I don't get, but to each their own, mine is cameras and bicycles, so I understand having a passion other people don't get) but to most people phones are just something they have. If you're knowledgeable about this stuff, then I get why you might not understand why it's confusing to people like me.
In short, thanks for nothing.
P.S. - It IS rootable. I rooted mine. It is rooted right now. It's rootable using Dr.Phone. I mentioned this, so why don't you read? I could go on and on about the lame traits of users of niche interest sites (including photographers and cyclists, they can be so irritating) one being that of false authority... but why bother when I'll just receive another boring snide response (another lame trait of some enthusiasts which they seem to get no end of satisfaction from "Umm, there's this thing called the search function... duh".)
Lol enjoy your junk phone ...
Yeah, that's about what I expected. Thanks for proving my point. Enjoy your lame hobby.
This is probably more of a rant, but I think it needs to be said. Please try to remember when responding to posts asking for help that the OP may be totally new at this, or like me, has done it before but doesn't do it often enough to remember how to do it. I see far too many responses to "how do I root" and "how do I load a custom ROM" posts that are either highly technical and assume expertise in the topic, lack actual instructions, or state "do a search, this has been asked before". It is very probable that the OP is not technical, has already searched and read countless threads, and has looked for instructions already and not gotten a clear answer. It is also highly probable that the other threads were so drawn out that they were not easy to follow, and very confusing to someone who is not so well versed in rooting and custom ROMs. Now, I am a technical person by profession who has rooted a number of devices and loaded custom ROMS on them, and I get lost reading many of these threads. Imagine how a person who has never attempted this before feels.
So please, I beg of you, be considerate in your responses. If you know it has been asked before, link to a few threads to point the OP in the right direction. Maybe they didn't know the proper search term to get to what they were seeking. If you are a developer and need the person to provide you with logs, provide the instructions on how to get the log, or at least a link to a post with them. And above all else, try to remember that there was a time when you were that new person who had no clue what they were doing, and give them the answer that might have helped you root or load a ROM on your first device.
graewulf1 said:
This is probably more of a rant, but I think it needs to be said. Please try to remember when responding to posts asking for help that the OP may be totally new at this, or like me, has done it before but doesn't do it often enough to remember how to do it. I see far too many responses to "how do I root" and "how do I load a custom ROM" posts that are either highly technical and assume expertise in the topic, lack actual instructions, or state "do a search, this has been asked before". It is very probable that the OP is not technical, has already searched and read countless threads, and has looked for instructions already and not gotten a clear answer. It is also highly probable that the other threads were so drawn out that they were not easy to follow, and very confusing to someone who is not so well versed in rooting and custom ROMs. Now, I am a technical person by profession who has rooted a number of devices and loaded custom ROMS on them, and I get lost reading many of these threads. Imagine how a person who has never attempted this before feels.
So please, I beg of you, be considerate in your responses. If you know it has been asked before, link to a few threads to point the OP in the right direction. Maybe they didn't know the proper search term to get to what they were seeking. If you are a developer and need the person to provide you with logs, provide the instructions on how to get the log, or at least a link to a post with them. And above all else, try to remember that there was a time when you were that new person who had no clue what they were doing, and give them the answer that might have helped you root or load a ROM on your first device.
Click to expand...
Click to collapse
I agree with you in general - civility and professionalism goes a long way.
That being said...
It isn't hard to look for the answers you need. Not only do we have a search function on this site, but external search engines can be used as well. Many basic questions have already been answered, and a lot of the frustration from more experienced members is the apparent failure of those who are less experienced to find information that is readily available.
However, I completely understand what you mean - everyone has a different style, so whereas one person's guide might be clear and easy to read, another's might be quite confusing.
If only the search function worked better. I can't count the number of times I've searched for something and not found it, only to have someone else post a link to a thread with exactly what I was looking for. A search is only as good as the knowledge of the person performing the search. If they don't know the proper search terms to use they may never find the earlier posts explaining the same thing.
Most excellent observations from all that have posted so far in this thread.