Tips for the laymen rooting - myTouch 3G Slide Android Development

I wanted to contribute something to the development but I'm a dumby when it comes to code. For a living I coordinate techs and developers with end users, basically I'm a tech-speak translator. I've notice that around these parts there are a ton of questions that could be easier resolved by following some guidelines. So this guide isn't about how to root or rom specifically, it's tips to avoid common mistakes and make it easier to provide you with help if something does go wrong. Think of it like when you call your cable help line and they ask you "is it plugged in" if you checked to make sure it was plugged in before you called you'll get to a solution a lot quicker.
I ask that any devs who can add to this do because knowing what us regular users can do to make your job (unpaid job that is) easier benefits us all.
Back up
This is super important but a lot of us are in such a rush to play with the goodies that we skip it. Always always keep a current back up of your sd card on your pc/mac. You can create a folder called "mytouchbak" or whatever you want and just copy and paste all the files over there.
Also nandroid backup. You should keep at least 2 nandroid backups. If you're just now rooting make a nandroid back up before you do anything. Then once you have a good stable rom running make another nandroid back up. This way you can either return to a default build, or to your working rom build.
These things are important because usually if you screw something up it's usually quicker and easier to just start from the beginning rather than have someone try to figure out what tiny step out of the many involved you may have done wrong, then figure out how to fix it.
Try twice
This relates to "back up." If something seems broken start from the beginning and try it again. Most likely you missed a step, forgot a symbol in something you typed, or sometimes something just didn't quite go right. By rooting you are doing things that weren't meant to be done and sometimes some numbers just got crossed somewhere. Before you proclaim that things are broken just try it again. You would be suprised by the number of times things work the second time through.
Read the whole thread
We have all done it. You follow the instructions perfectly and something doesn't work so you run to the forum and immediately write a post saying "help, i can't get it to work" on page 80 of a thread when several other people experienced the same problem, already asked the question and a solution was posted on page 20. I know it's sometimes a pain to skim 80 pages of posts but those 80 pages are probably caused by other people not reading the thread before posting. A good tip for this is if there is something specific that isn't working like wi-fi tether, just open the search toolbar in your browser, type "tether" and then go to each page hitting search. That way you don't have to read every post but if anyone has mentioned anything about tethering it will point you right to it and you only have to read those posts.
Have a computer ready
This is one that most of us already do but the one time you forget things always go bad. Don't ever rely on remembering the instructions you read on your phones browser when working on rooting and romming. If you have a computer in front of you you can read the forums and follow the instructions word for word which gives you a better chance of success.
Read everything first
Before you start read everything from start to finish at least once. Sometimes devs skip steps that they assume we know and then mention them later. It's because a lot of things seem like something everyone should know, but we don't. In the same vein if you can find multiple tutorials read them all first. This will give you several view points on doing the same thing and will in general make the whole process make more sense to you and clue you in on things one tutorial may have skipped past.
The other benefit is sometimes a step is listed, and then right after it it will say something like "and don't do that until you do this." such as with our current rooting loop method. If you read all the steps first before starting you won't be caught off guard by things like this.
Asking for help
When you get stuck, you can't find any answers AFTER READING AND SEARCHING THE FORUM for your issue then definitely ask away. How you ask relates to how easily it is for someone to help you.
Avoid making general statements when possible, detail is a must. Instead of saying "I rooted, then did A2SD, then restarted" give the steps you took to root and A2SD by either referencing the method such as "I rooted as per the steps laid out in (link to instructions or name of method) or lay out the exact steps line for line as to what you did. If you assume you rooted right and what went wrong was you missed a step in the rooting process how is anyone supposed to tell you what step you missed.
Also format it to be easy to read. Development trains your mind to be very organized and structured. Basically don't format your post like this guide I'm writing, in large blocks of paragraph text. Instead put each command on a new line for instance:
"I did this
adb shell
adb push update.zip /sd
reboot into recovery....."
this makes it a lot easier to provide you with help.
Slow down, Find a good time
Don't rush through the process. That's how steps are missed, commands are mistyped and phones get bricked. I've done roots at 2am and couldn't for the life of me get it to work, I put it away and tried again in the morning and things went great. So don't mess with rooting and romming when you're exhausted, in a hurry, high, in the midst of an argument with your girlfriend, or any sort of other distractions.
That's all I have for now, I hope it helps. If anyone has anything to add please do.

great guide, most of us probably follow these general rules without really thinking about it and sometimes that is overlooked when a new guy comes in to try to do something.

tubaking182 said:
great guide, most of us probably follow these general rules without really thinking about it and sometimes that is overlooked when a new guy comes in to try to do something.
Click to expand...
Click to collapse
Thank you. I notice that happen a lot in my job where someone with no experience in the particular tech get's lost because the things we take for granted as common knowledge really aren't for someone new to the idea. Especially with the android devices becoming insanely popular theres a huge influx of new users looking at the goodies that come with root. install a custom rom or two and everything above becomes second nature.

skullkandy said:
Slow down, Find a good time
Don't rush through the process. That's how steps are missed, commands are mistyped and phones get bricked. I've done roots at 2am and couldn't for the life of me get it to work, I put it away and tried again in the morning and things went great. So don't mess with rooting and romming when you're exhausted, in a hurry, high, in the midst of an argument with your girlfriend, or any sort of other distractions.
Click to expand...
Click to collapse
So that's why I was having problems.

this tut is NOW IN SLIDE BIBLE! just send people there any chance you get with noobs, and we'll let them search

Aweome idea for a post! Thanks!
Sent from my T-Mobile myTouch 3G Slide using XDA App

Thanks for all the positive feedback guys. And especially thank you for getting this posted into the slide bible. I hope this cuts down on some of the repeat questions and makes it easier for some of the new folks to not be so overwhelmed when rooting for the first time.
@Bigshow281 : I have screwed up several rootings by being a little bit too foggy to be messing with something that requires precise typing and following instructions correctly.

Related

[Q] I think I can stump xda forums... seriously messed up 16gb

It's been a while since I've worked on this, and I still can't find anyone with a similar problem on xda. Does anyone have a clue what's going on with this thing?
First, I got it working just fine with CM7 installed to the nook itself, not running from an sd card. That worked for a bit, then it started just shutting off with no obvious reason.
Also, if I make any changes, like uninstalling apps, it goes right back after a reboot - which happens whether I want it to or not. This applies to changes done with CWM as well, even installing a new rom.
On top of that, it won't boot from an sd card, so that sucks too.
Lastly (I think, it's tough to keep track of all these problems) abd doesn't recognize the device, and for that matter the operating system doesn't either. I've been using Ubuntu Lucid if that matters, but it didn't have issues detecting the device before.
I'm pretty novice, but I think this is a very complicated problem in need of expert advice. Any answers, tips, advice, or pointing in the right direction for any of my problems here would be awesome. Does anyone have any ideas?
Thanks.
Dude you say your a novice thats one... Two you are being critical of people who volunteer on this stuff. You can't be serious. You obviously have not read the support threads because you are not the only one with these problems and those that have them also did not read enough initially and failed to follow some step. Moreover, even if your problem were unique who do you think you are getting upset at anyone but yourself for taking the risk. Read the support thread for cm7 Mr. Ungrateful... flash back to stock and leave this forum alone until you 1. Learn what it means to be grateful. 2. Learn to follow instructions. The end
it is impossible to stump xda...
rickyshortcuts said:
Dude you say your a novice thats one... Two you are being critical of people who volunteer on this stuff. You can't be serious. You obviously have not read the support threads because you are not the only one with these problems and those that have them also did not read enough initially and failed to follow some step. Moreover, even if your problem were unique who do you think you are getting upset at anyone but yourself for taking the risk. Read the support thread for cm7 Mr. Ungrateful... flash back to stock and leave this forum alone until you 1. Learn what it means to be grateful. 2. Learn to follow instructions. The end
Click to expand...
Click to collapse
Thanks, that reminds me, I did follow all steps to the letter without a hitch to get CM7 going. It wasn't until after it was running for a few days that this happened. Also, in the aftermath while trying to solve the problem, I did everything I can think of to completely brick the nook so that I might be able to use some of the methods here to unbrick.
And just to defend my good name, I think it's a stretch to imagine I've been critical of anyone. To reference your other post on these forums, perhaps you might reconsider how to be helpful. Let me help you out with that.
because it is SERIOUSLY a hard brick, then you gotta get serious about your attack on this sick puppy. get a #6 torx and open it up and get directly at the internal sd card ( which sounds like you have trashed... )
hth
.
let us know when you got it open...
Dude!!!
rickyshortcuts said:
Dude you say your a novice thats one... Two you are being critical of people who volunteer on this stuff. You can't be serious. You obviously have not read the support threads because you are not the only one with these problems and those that have them also did not read enough initially and failed to follow some step. Moreover, even if your problem were unique who do you think you are getting upset at anyone but yourself for taking the risk. Read the support thread for cm7 Mr. Ungrateful... flash back to stock and leave this forum alone until you 1. Learn what it means to be grateful. 2. Learn to follow instructions. The end
Click to expand...
Click to collapse
One: This was a completely pointless flaming. Two: For being a novice he seems to be a bit more informed than you are. This is an issue, however not a common one. And from what I have read in these forums there is not as yet a fix. Three: I didn't read any ungratefulness, criticism, nor any hint of being upset. And Four: If you can't help out or give any useful advice then maybe you should "leave this forum alone" until you learn to be more civil.
chuckweiss2 said:
Thanks, that reminds me, I did follow all steps to the letter without a hitch to get CM7 going. It wasn't until after it was running for a few days that this happened. Also, in the aftermath while trying to solve the problem, I did everything I can think of to completely brick the nook so that I might be able to use some of the methods here to unbrick.
And just to defend my good name, I think it's a stretch to imagine I've been critical of anyone. To reference your other post on these forums, perhaps you might reconsider how to be helpful. Let me help you out with that.
Click to expand...
Click to collapse
Well put, and Props.....
I don't know if I can help out but I think I can point you in the right direction.
http://forum.xda-developers.com/showthread.php?t=1619615
This seems to be a hardware problem, but I don't think anyone is sure what is causing this.
Good luck with finding a fix.
went and found a XDA link for res-erecting bricked devices. it by @adamoutler and looks like a goodie !
ModeDetect USBID Detector
http://forum.xda-developers.com/showthread.php?t=1257434
hth
.
( you can tell that Adam is passionate about his tech. what do they feed those boys down in Louisiana beside crawdads ? )
Alright, so thanks to old_fart and DavDoc I've determined two of my problems, and I think there are four.
First, DavDoc's linked thread describes perfectly what's happening with problem one, what I'm calling the Groundhog Day Syndrome for no particular reason. Any changes to my nook go right back after it's powered off.
Second, I checked out old_fart's linked thread and I'm pretty sure even though I have a blank screen it's still on in one mode or another. The program doesn't work though because of problem #3 (to be explained) but it seems sensible because to power it back on I must first hold the power button for an extended period of time and release, then hold it again for the normal power-up.
Problem number three is that the nook is not recognized by either Ubuntu or Windows when plugged in anymore. Thus that program not working, and also adb. I may be able to determine that one from error logs as soon as I figure out what in the world the error logs are saying.
Fourth and hopefully final, it won't boot from sd. I'll figure that out too.
Thanks for the advice so far, this forum is definitely indispensable for people who like to learn from playing with technology.

Dual Boot Official GB and ICS rom for HTC EVO 3D GSM and A Few Thoughts!

Disclaimer: Kindly Forgive My Long Post
Some Important Details of My Phone:
Hboot version HTC EVO 3D X515m PG86300 GSM:
***LOCKED***
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.49.009
eMMC-boot
July 18 2011, 12:09:31
ro.carrier:[HTC-India]
Shooteru
CID: [HTC_038]
Android Version: GingerBread 2.3.4
HTC Sense Version: 3.0
Software Number: 1.22.720.4
Kernel Version:
2.6.35.13-g28ad439
[email protected] #1
SMP PREEMPT Thu Jul 21 14:50:22 CST 2011
Baseband Version:
10.54.9020.00U_10.13.9020.20_M
Build Number:
1.22.720.4 CL115289 release-keys
Browser Version:
WebKit/533.1
Dear All, I have taken my time and read through and even posted on most of the forums, but unfortunately not one detailing the stuff I intend to do or proper/clear cut response. First off, I would like you to remember that I am a noob and your elaborate and detailed instructions of the steps involved would invaluably help me and hopefully others looking to do the same, so if you're in a hurry, please don't reply halfheartedly. When you have some free time, reply and I will wait patiently for your instructions on how to go about things. I will wholeheartedly appreciate whatever inputs I can receive from those with some know how about the possibilities/impossibilities of the same and please, like I said, spare the noob with some patience and offer some really helpful posts(even if delayed). Thank you.
My intention listed below: (Have already purchased a 64GB Class 10 Micro SD card)
1. Root to S-Off. (Hopefully with methods to revert back to Original state in case of Jelly bean update being released for the EVO3D or for receiving future updates).
2. Back up my Official GB and apps to be reinstalled with a boot manager to slot 1 as either recovery or First Rom.
3. Obtain The Official ICS update either via OTA or if there is an Official Ruu File for my device. Steps on how to get contacts and apps restored back to this too would be helpful.
4. Back up the ICS Rom to be installed on Slot 2 of boot manager so that dual boot of Official GB and ICS can be done.
5. Possible methods of adding the Jelly Bean Update If/When available to this mix to have a triple booting device with the official ROMs.
Based on the above, this is what I am looking for:
1. Fool proof methods and steps on achieving the same.
2, The necessary apps, recovery programs, region based Stock ROM/Ruu files(in case the backed up Official ROMs are not necessary or deemed applicable), and any other software/apps that may be needed to be downloaded/purchased for performing the same.
3. Step-by-step instructions pertaining to the particular Hboot version, CID, etc of my device.
4. Safety measures to look out for, checklist of files to have before hand and Probable methods of having a safe copy always at hand to recover mobile from any boot loops, bricking, etc.
5. Please note MOST of the links to files are not downloading, especially file factory links of the RUUs. All the other smaller files are there and can be got from alternate sources too, except the more important Big Ones Missing! Kindly rectify the same. Thank You.
I would like to inform some very important things I noticed on the forum/threads in PLENTY and what it would seem like to anyone new on the forums and if you are of sane mind, I am sure you will agree! Not that I'm asking you to, since to someone familiar with things a noob's point of view will ALWAYS seem inferior, because one very easily forgets that he was once a noob too:
1. You have instructions and threads, YES, PLENTY! BUT... There is always a drawback/s mentioned somewhere down the line that too when the thread has nearly 400+ pages! That would only make a person mad for having wasted time to find out that it is a nonworking method, etc. Either the thread has to be cleaned up of repeated questions or WRONG information. Faulty/half-working ROMs have to be either REMOVED or Carry A Warning in the TITLE as well as the 1st post itself so that people won't waste their time reading through the umpteen posts and pages or trying and failing and/or bricking their devices.
2. Too many threads of the same methods to do the same thing whereas there are issues mentioned and argued about with those methods too. Ever heard the saying, "Too many cooks spoil the broth!" ? Also, be more descriptive with titles or threads so that Search will catch it. Eg. If something is either related to GSM or CDMA(even for RUUs, if made known, would help immensely), please have it mentioned first off!
3. In the same way, Methods for Rooting, S-OFF, etc, would be BEST if they were mentioned with the supported/respective Hboot versions or CID numbers since these two seem to be the most important factors from what I have seen. It would be good if members posted their Hboot version [Power off phone, Remove battery, replace it, hold volume button down and then simultaneously press power button for 2 to 3 seconds to go to Hboot menu. Volume buttons to go up or down in the menu, To Exit, move to fastboot, with fastboot highlighted, press power button, scroll down with volume key to reboot, with reboot highlighted, press power button to Exit(see what I mean?! THIS is what a noob would want to know and Not KNOW! Unlike someone flashing 10 to 100 ROMs a day)] and CID version(CID Getter app download from Market/Google Play Store, install and Run. The First Line on TOP in Red shows the CID is...) when they say some method worked for them or DID NOT and be responsible enough to reply when the OP asks if the issue was resolved because it leaves someone reading 500 odd pages left in the dark! And trust me! It isn't an easy task!!!
4. If information is known as to which region RUU/s(Stock Roms) is for a particular CID and Hboot to work without conflicting, kindly link them TOGETHER, if others can be used mention the same, but also how and what files to have in handy in case restoration needs to be done for either warranty or other purposes, since the files will be needed according to the same by each member and having a List/Database in a separate thread with correct details of EACH would immensely help, and then at least the search function would prove more helpful. (Note to Others: Before you change CID or other Important Things, Note Down the About Phone Details of your Phone, CID number, Hboot Version, etc, on a notepad saved as HTC Evo or whatever your phone name is, with a Date in the note for each step you did and when, etc for You To Keep Track, in case the need arises down the line, NOT say you didn't think it was important! Ever try forgetting your wife's birthday or your wedding anniversary, Yeah Right! WE Don't think it's Important, but We'll know better later! ) This is a thousand times better Instead of guess work or time wasted on trial and error and reading a hundred threads that lead people in circles between will work and won't work fights, only to curse the day they thought of trying something with their device!
5. When there is a WRONG INFORMATION passed regarding a ROM/method of S-OFF, etc, get the facts verified ASAP and remove contraindicating or confusing posts or the thread itself if there is an issue, Make it compulsory for OPs to Put up A HUGE WARNING as to the drawbacks of doing something with a particular ROM (or better still Just Remove It), and make known of NON-WORKING things before Hand! Which method pertains to which versions, etc. That way noobs would not end up trying their hands at things that they are not familiar with and end up begging later PLEASE, HEELPPP, etc, on deaf ears in the forum. They can at least have working methods up and try them out and be happy once they succeed and can be even more happy to have entered XDA and can spread the good word!.:highfive:
6. This is supposed to be a forum for productivity, NOT Hold Egos OR Try and test others as guinea pigs and then claim d'oh, or Oh sorry I didn't see or notice that. Your small overlooking of an important factor might cost someone his/her device! Try and sort your $#!T Out BEFORE You post it in a forum! Give detailed answers. If You Don't Know, Say You Don't We Won't Think You Less Wiser, but will Appreciate Your Honesty! Not wait till someone gets Scr3W3D and then later cry hoarse all over the forum! And yet you try to act All High and Mighty After You are Caught With Your Pants Down! Catch My Drift?!
So admins please do clear up things a bit and get rid of unwanted posts or too many topics on the same thing, which would have consequential/negative effects on those visiting those threads, (let them bunch up all their names as credits in the single thread and oh to AVOID the EGO Clash Mention "In No Particular Order" just to make 'em happy!) because it will give a bad name to the forum which I'm sure none of us want to see happening! Just my 20 cents I hope would be useful!:angel: Oh and as a signing off to People Already on The Forum or Coming into the Forum, "I DON'T CARE if You GET Or NOT GET an EVO, JUST PLEASE DON'T GET AN EGO!!!" Take Care and God Bless!
Thank you for your thought out post. I did read the whole thing and agree that in an optimal world, posts would be much more detailed. But, to give that much detail would be a full time job and then some. So many of us give pointers to get people looking in the right direction.
When I rooted my phone as a noob, I had about 20 tabs open researching different sites and consolidating information. I learned a lot that way and am glad someone didn't spoon feed me. But to each his own I guess.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Please Tell Me My Post is Not in Vain!
coal686 said:
Thank you for your thought out post. I did read the whole thing and agree that in an optimal world, posts would be much more detailed. But, to give that much detail would be a full time job and then some. So many of us give pointers to get people looking in the right direction.
When I rooted my phone as a noob, I had about 20 tabs open researching different sites and consolidating information. I learned a lot that way and am glad someone didn't spoon feed me. But to each his own I guess.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Click to expand...
Click to collapse
Hi coal686, thanks for the reply. Reminds me of my school nickname thankfully which never stuck! lol Well I did type out the long post above because I wanted to mention the difficulties ANY noob would have on approaching the site and also what I DID NOT find Anywhere in the threads. (you have dual boot threads, but not the same) What would seem right direction/s to the "quickie" posters might not actually be the right direction if you read through the threads for the target. Like saying go this way, then that way; oh! and there's also this way and that way too and the person travels all those miles(pages in this case) through all those different paths(threads) only to reach the DEAD END of different sides of the SAME CLIFF to jump off! Don't believe me? Read the threads! You'll understand why and tell me honestly that you don't feel the same way when you see some or rather most of the threads after actually reading a gazillion pages.
You say difficult to give that much detail. I thought we all actually want an optimal world, not a world driven by chaos?! There is much MORE wrong detail given in a single thread or how do I put it?, Target-less detail, other than the intended purpose sometimes. If you did read my post, you would have been kinder to notice that that was what I was trying to mention and imply from my experience. Like I mentioned before, It is NO USE having SO much info(some wrong or non-working) scrambled all about with different variants with no proper target or what it is about. Do you know that if a person literally typed out a single page with proper working methods with so called "spoon-feeding explanations steps to a noob" like how I explained in my post(for the Hboot and CID) there would have been lesser space taken up in the forum and it would be BENEFICIAL to one and all who visit the forum. (also for those who don't have Mbps connections to see, again, misguiding or poorly shot videos on the same)
Don't you think those 4 or 5 points that I posted are obviously what is ideal for any/everyone. List of programs for each purpose, steps to do, Note down the About Phone info, Hboot, CID versions, correct files to download for the same, how and when to do the backup, rooting, But still if the methods were already there, there would be no need to revert or go in for warranty anyway! Tell me you see these important instructions in the best of threads up front and at the very beginning and I'll know how well you read those 20 tabs. Still don't trust me?!
I'll be frank with you, a person who is pretty confident too will come in, read, try, scream at least a million WTFs?!! and different profanities by the time he is done with just one part of the process, would have lost half or more of hair and brain cells, and read a "right-looking" thread which ends up being the wrong thread, mess up his phone, beg on the forums, curse in his heart, still beg more and by the end of it all would say $cr3W T#!s and maybe either kill his/her phone or himself/herself! lol I hope that's not the intention of the forum though, or a new depopulation method?! :laugh:MAO
However, Please tell me you don't believe I am asking to be SPOON FED according to you, and that I came and posted WITHOUT READING ANY THREAD. Just like you, I usually take just a day or two continuously reading stuff, actually more than 20 tabs at a given time to get a hold on any new topic and I'm usually done within that time because it's easy to identify the right stuff for me to get the various topics and have an understanding of what I need to know, but I cannot say the same for this experience. Multiple tabs reading of utter confusion, misguidance, so many pages bookmarked, read through, agonizing to learn, that I am asking something about a person's head(Evo 3D GSM) and two eyes(Dual boot GB/ICS) straight up and I am instead replied to with directions to a person's... tail(don't ask!), or what one or many persons think is a person's head, only directed to the wrong head! You get the picture?
Sorry for being a bit coarse, but I hope it puts my point through clearly or better for people to understand the flaw and rectify it, instead of trying to justify it. For that matter, when you see the so called multitude of videos(it's a PITA on 512kbps), which are supposed to be by people doing this stuff day in and day out, Just see the number of times, they stutter through their own stuff! They cannot go through the process correctly, forget a program in between, forget to post the links up front, or steps, things like commands and stuff are thrown about in different graphics! Are you serious?! Then go about it all haphazardly and then think to themselves, they HELPED someone!!! Boy if they were a Driving instructor there would be lesser population!
Just for entertainment purposes, This is how it would go:
noobie driver: What do I do sir?
Instructor: Well you put on your seat belt first, start the car, change the gear, slam down the accelerator.. oh $#!t wait I forgot to tell the mechanic to change the brakes, umm... adjust your mirrors, umm... oh yeah press the brakes, umm... there's a truck heading into us!
noobie driver: WTF?! What is the brakes and where is it sir?!
Instructor: What do you mean you don't know what or where the brakes are?!! It's that damn pedal down there you Noobie Nut job!!! (looks down) Oh s#!t!!! I forgot to refit the brake pedal that I took out too!!! Never mind Bubba say your prayers!!!
CRAAAAASHHHHH!
This is about the same scenario that's happening! Like with computers, just because I know a little, if I instruct someone who has never touched a computer or maybe owns a computer and types stuff on it, blindly saying, put the power cord into the SMPS socket, take the RAM out, clean it and RAM It into slot 1 not slot 2, the one next to the CPU is slot 1. Replace the CMOS battery, Check if Hard disk is connected, Check if DVD writer is SATA/IDE! Clear the CMOS jumper by moving it from pins 1-2 to 2-3 and then back to 1-2. Oh, but first, pull out the power cord before you do! Do you know what reaction I would get?! I would probably hear a BUZZ, see some sparks and have one less person and one less machine on the planet!
Now I know when reading this long post, some might be with their noses pointing in the air saying, Oh we don't have the time for this nonsense! But seriously, you think that others are enjoying the experience like I'm going through?! The neck, back and headache I'm having right now is all proof to it and if experienced by you, you'll definitely not hesitate to even spoon feed me! All this stuff will just put the TRUE picture of how things are, well, at least for now. If Anyone patient enough and want to seriously change things to an optimal world situation, and willing to guide me through though, I will STILL be Patiently WAITING for your knowledgeable inputs.
BTW, still the file factory downloads keep timing out or failing before the end and after three attempts, that too through DTA(down them all) to avoid any failure, it is coming as a failed download or simply beeps completed, but with a html of 21kb!!! Torrents Anyone?! Also for the said Hboot version and CID of my device(or am I supposed to change it?) Which are the RUUs to download? Shooter U GB/ICS Europe or Asia? I am guessing a backup of my own GB would be useful for the future just in case so how to do the needful would be good. Thanks once again for your patience on whoever gets to read this and will as usual appreciate ANY inputs on the same. Cheers and God Bless.
Comments withdrawn
Sorry, If You Missed the Point Be Patient, I Don't Want You To Lose Me! lol
@zcink: Thanks for the quick response. Oh, btw your logo pic is my pet name Micky (in case you change your pic) lol! Also what you mentioned is what I am somewhat hoping to do. Lol and I can imagine why it was quickly shot down! lol Care to post the steps though for my scenario, either here or on a separate thread and it may benefit some, if not many! I did try breaking up the paragraphs for easier reading bro. It's really not that difficult to read and sorry once again if it is. Well other than the seemingly unimportant stuff, this part from my first post being replied to in detail would be more than sufficient:
________________________________________________________________________________________________________________________
My intentions listed below: (Have already purchased a 64GB Class 10 Micro SD card)
1. Root to S-Off. (Hopefully with methods to revert back to Original state in case of Jelly bean update being released for the EVO3D or for receiving future updates).
2. Back up my Official GB and apps to be reinstalled with a boot manager to slot 1 as either recovery or First Rom.
3. Obtain The Official ICS update either via OTA or if there is an Official Ruu File for my device. Steps on how to get contacts and apps restored back to this too would be helpful.
4. Back up of the ICS Rom with apps, etc to be installed on Slot 2 of boot manager so that Dual boot of OFFICIAL GB and ICS ROMs can be done.
5. Possible methods of adding the Jelly Bean Update If/When available to this mix to have a triple booting device with the official ROMs.
Based on the above, this is what I am looking for:
1. Fool proof methods and steps on achieving the same.
2, The necessary apps, recovery programs, region based Stock ROM/Ruu files(in case the backed up Official ROMs are not necessary or deemed applicable), and any other software/apps that may be needed to be downloaded/purchased for performing the same.
3. Step-by-step instructions pertaining to the particular Hboot version, CID, etc of my device.
4. Safety measures to look out for, checklist of files to have before hand and Probable methods of having a safe copy always at hand to recover mobile from any boot loops, bricking, etc.
5. Please note MOST of the links to files are not downloading, especially file factory links of the RUUs. All the other smaller files are there and can be got from alternate sources too, except the more important Big Ones Missing! Kindly rectify the same. Thank You.
________________________________________________________________________________________________________________________
Lol, I can't help but notice that I mentioned the words "Official ROMs" many times just to be clear and it was so easily missed (Sorry, if I am to blame or wasn't clear enough) I am not all too keen on Custom ROMs having one or two (maybe unimportant to some, but important to me) features missing making my phone defunct, but rather thoroughly working with its original ROMs. I would however be more than happy to add Any FULLY working ROMs with maybe Sense 4.0 and Beats to the mix, but I was already told that there are NONE and also explained the reason why they are that way, so I do understand!
Let me guess my friend. Either the installed radio or the kernels must have been the issue because one would have been for GB whereas it won't work for ICS or vice versa. That's why I was hoping that someone who knows or tried out this stuff to the core would know which is the commonly working Kernel or Radio to install both ROMs without error, or if say Maybe Official backed up GB was installed back onto the phone as slot 1 and Official ICS was backed up and installed onto a partition on the SD card as slot 2, with maybe a separate partition for ROMs and Data so that say each ROM stays within that area having their own separate kernels, radios, etc when loaded into via the boot manager and hence not having issues with their working.
Sorry, I am not too well-versed with the workings of android, but I am just trying to give my thoughts based on what I know through my experience with dual booting computers, though I know we're talking different things here, but am sure some things might be common. Just out of curiosity, does maybe android not have ways to direct or redirect the phone to a separate portion to run each particular ROM and maybe because all the files are all dumped in the ROOT there are errors?
Because for example if I were to take both XP and Windows 7 files(though common platform) and place it on the same partition, there are definitely bound to be errors. Whereas GB and ICS are more like Windows XP and Linux(only Android Mobile being the common platform here) so probably placing them all in the same place(Root of phone) is scr3wing up things. Does Android segregate things(files to separate partitions) in the same way as computers do and the boot loader able to direct/redirect to the appropriate partitions/ROMs for smooth performance? OR Does it have NO method of doing so hence the chaos?!
If that was the case, any developers of the boot managers, ROMs, etc who manage to write stuff in a way that it is able to hold different kernels/radios for the respective ROM/s in separate partitions on the memory card (or Phone if enough memory on board) would be able to manipulate the system to make the boot loader redirect correctly to the appropriate partition and hence make it error free in operation since all the needed files would be present in that location. Also a common way to connect to other files(media, etc) on a Separate Data Partition, would enable each ROM to recognize/find/see those files instead of missing/not detecting files, or say getting apps and contacts for EACH Rom reinstalled again and again, similar to as on OS' of computers.
Am I just blabbering/rambling here not knowing what I'm talking about?! I guess so, but Well, just my 2 cents which could hopefully benefit for the future to someone or some developer who tries to think differently like me(err.. the thinking part that is, not the developer part! lol). Thanks and anticipating once again your knowledgeable inputs.
help needed
******LOCKED*******
SHOOTER_U PVT SHIP S-OFF RL
HBOOT-1.49.0018
RADIO-11.25.35.3504.06_M
openDSP-v02.6.0.2226.00.0202
eMMC-boot
oct 3 2011,15;03;01
need help how to revive this phone is urgent thanks in advance

[Q] Do I have to do a factory data reset for every new rom?

DISCLAIMER: It seems I, and all the other newbies, have to add this to the top of our posts. Yes, I have tried searching for my answer, and no, I did not find it quickly. I prefer the speed and intimacy of human interaction, as well as the fact that I usually learn new things that I would not have from a simple search. If I offend you by dirtying up your forums with a repeat question, please just ignore this thread entirely, I don't want to hear it. If I offend any mods by asking a repeat question, I apologise, please lock this thread and I'll be on my merry way
So I've got the base CM7 working on my Bell MB860, and I love it. I finally have HDMI mirroring, my phone's boot time is 1/10th of what it was before, I don't have any bloatware anymore... these people are getting a donation from me! And to think that some people expect you to pay $1.99 for a flashlight app on Google Play, and the Cyanogenmod is completely free... I just have a few questions:
1) Since I lost my backup of my stock ROM (CWM told me it made the backup just fine before I flashed it, CWM did NOT tell me it corrupted the MFT of my SD card to a point where even R-Studio could not recover the raw data), I just made a backup of the working CM7 installation. Am I correct in that the backup is stored in sdcard\\clockworkmod\backup? And is the timestamp on it supposed to not be adjusted for time zone? Just trying to make sure I have the right backup selected, but the time stamp is 4 hours before when I actually made the backup.
2) I would like to try out some of the ROMs based on CM7. I hear MROM is pretty good. But is there an easier way to install new roms than doing a factory data reset, and then reinstalling all my apps and reconfiguring all my settings for every new rom?
Other 2) And what's all this about downgrading your SBF version can hardbrick your device, would downgrading my CM version do the same?
3) Why do dogs have cold, wet noses?
Thanks in advance for anyone who donates their time to read and answer my questions!
You only have to wipe when switching to a different ROM "flavor". When upgrading to a new version of a ROM, a wipe is not necessary unless the upgrade instructions say otherwise. Or, you could go with the inverse logic - don't wipe unless absolutely necessary, ie. apps are crashing and/or malfunctioning after flashing.
You might also want to try Titanium Backup, it helps with transferring apps and user data to a new ROM.
Also...
moeburn said:
I prefer the speed and intimacy of human interaction
Click to expand...
Click to collapse
You will soon learn it is completely irrelevant what you do or do not prefer. If you want to be a part of a community, you have to adhere to that community's rules. Here, that includes searching and reading on your own as much as you can, with opening a new thread being the very last resort. People have put tremendous effort into writing tutorials and explanations and building compendiums and knowledge databases, asking the same question over and over again basically means all their effort was completely wasted. They have done so specifically to avoid every single newbie asking the same questions again.
ravilov said:
You only have to wipe when switching to a different ROM "flavor". When upgrading to a new version of a ROM, a wipe is not necessary unless the upgrade instructions say otherwise. Or, you could go with the inverse logic - don't wipe unless absolutely necessary, ie. apps are crashing and/or malfunctioning after flashing.
You might also want to try Titanium Backup, it helps with transferring apps and user data to a new ROM.
Click to expand...
Click to collapse
Thanks for the info!
ravilov said:
Also...
You will soon learn it is completely irrelevant what you do or do not prefer. If you want to be a part of a community, you have to adhere to that community's rules. Here, that includes searching and reading on your own as much as you can, with opening a new thread being the very last resort. People have put tremendous effort into writing tutorials and explanations and building compendiums and knowledge databases, asking the same question over and over again basically means all their effort was completely wasted. They have done so specifically to avoid every single newbie asking the same questions again.
Click to expand...
Click to collapse
I do not wish to be a part of any community that treats newbies asking repeat questions with such hostility. If anything, it helps make it easier to find the answer to your question if there is more than one thread asking that question. Part of the problem is that there are so many tutorials and explanations and knowledge databases that after about 30 minutes of trying to search for my answer, I simply give up. I didn't ask anyone to write a tutorial, if they feel their time was wasted, that's their problem. It is very sad to see that every single time someone asks a question, they almost always preface it with a statement to the effect of "I tried searching, but...". There's very little gain to be made by telling someone to "go use the search function and stop asking repeat questions". You make a newbie feel unwelcome, and make it harder for them to learn, at the expense of having a slightly tidier forum, and sensitive tutorial writers not having their feelings hurt.
You too should know that it is irrelevant to me what people like that prefer. I honestly would prefer no help at all, to that kind of 'help'. I would prefer to have my account banned, than to have some punk think that they can treat me like sh*t just because my Join Date and Post Count are less than theirs.
moeburn said:
I do not wish to be a part of any community that treats newbies asking repeat questions with such hostility. If anything, it helps make it easier to find the answer to your question if there is more than one thread asking that question. Part of the problem is that there are so many tutorials and explanations and knowledge databases that after about 30 minutes of trying to search for my answer, I simply give up. I didn't ask anyone to write a tutorial, if they feel their time was wasted, that's their problem. It is very sad to see that every single time someone asks a question, they almost always preface it with a statement to the effect of "I tried searching, but...". There's very little gain to be made by telling someone to "go use the search function and stop asking repeat questions". You make a newbie feel unwelcome, and make it harder for them to learn, at the expense of having a slightly tidier forum, and sensitive tutorial writers not having their feelings hurt.
Click to expand...
Click to collapse
Not sure how others feel like, but personally I think this is not so much about keeping "the precious forum clean", more like "give a man a fish" vs. "teach a man to fish". Not quite the best approach, I agree, but this kind of attitude (sometimes viewed as aggressive or hostile) does indeed often make people search (or search more), and then often times they do find the answer they've been looking for, written down in plain sight. And then they do it again, this time on their own. And so in due time they're not only able to find all the info they need, but they're also able to teach others to do the same. It's not even just about this forum, being able to research properly is IMO a very useful skill in general.
On the other hand, there is indeed a set of "very well known facts" around here, and anyone asking about them is immediately seen as a noob with little to no regard for the community and with either poor search skills or just plain lazy. This "ellitistic" attitude seems to plague most hi-tech communities sooner or later, and I agree it is not a good thing. I myself have been guilty of it, but I'm trying to get rid of it.
Anyway, that is just my personal opinion and view of the situation. I by no means own this forum and generally I'm trying to not tell people what to do, just point them in the right direction. I'm just trying to give you an insight of how communities like this function. I'm a part of another (highly technical) forum and the general atmosphere there is very comparable to here, so it's safe to assume that that is just how things go in communities like this. You can adhere to the same rules or you can choose to be hated because you don't, but you won't ever change the mindset.
Anyway, enough off-topic.
moeburn said:
DISCLAIMER: It seems I, and all the other newbies, have to add this to the top of our posts. Yes, I have tried searching for my answer, and no, I did not find it quickly. I prefer the speed and intimacy of human interaction, as well as the fact that I usually learn new things that I would not have from a simple search. If I offend you by dirtying up your forums with a repeat question, please just ignore this thread entirely, I don't want to hear it. If I offend any mods by asking a repeat question, I apologise, please lock this thread and I'll be on my merry way
So I've got the base CM7 working on my Bell MB860, and I love it. I finally have HDMI mirroring, my phone's boot time is 1/10th of what it was before, I don't have any bloatware anymore... these people are getting a donation from me! And to think that some people expect you to pay $1.99 for a flashlight app on Google Play, and the Cyanogenmod is completely free... I just have a few questions:
1) Since I lost my backup of my stock ROM (CWM told me it made the backup just fine before I flashed it, CWM did NOT tell me it corrupted the MFT of my SD card to a point where even R-Studio could not recover the raw data), I just made a backup of the working CM7 installation. Am I correct in that the backup is stored in sdcard\\clockworkmod\backup? And is the timestamp on it supposed to not be adjusted for time zone? Just trying to make sure I have the right backup selected, but the time stamp is 4 hours before when I actually made the backup.
2) I would like to try out some of the ROMs based on CM7. I hear MROM is pretty good. But is there an easier way to install new roms than doing a factory data reset, and then reinstalling all my apps and reconfiguring all my settings for every new rom?
Other 2) And what's all this about downgrading your SBF version can hardbrick your device, would downgrading my CM version do the same?
3) Why do dogs have cold, wet noses?
Thanks in advance for anyone who donates their time to read and answer my questions!
Click to expand...
Click to collapse
You don't need to complete a factory reset if you're going to a completely new ROM. You simply need to process a data and cache wipe in CWM. Use titanium backup, call log restore, SMS restore, and APN settings restore before wiping. That'll make the migration process much easier and seamless. It takes time, but it eliminates a few layers of complication during the process. Upload your backups to google drive or Dropbox as well as to your desktop.
About your disclaimer: I completely understand your frustration. However, including such a vociferously rebellious statement atop each thread that you post invites a negative reaction. And doing so isn't going to change the social dynamics of this community. It simply disrupts the integrity of our discussions. Simply search for your answer. If that fails to satisfy your needs, post a new thread. Ignore those who respond in a unhelpful manner. If they're not acknowledged, they're powerless. By specifically addressing and acknowledging that demographic during each post, you're inviting their hostility into the discussion.
Yes, there are great compendiums of technological knowledge available to us on XDA. However, a forum search engine hardly qualifies as a great organizer for such a repository. So, we will encounter redundant threads guys. Deal with it.
Sent from my iPad using Tapatalk HD

[Q] Comment about terminology and process

I am a new Xperia Ultra owner and whilst not planning to do any flashing just yet I thought tonight I'd take a quick look at threads discussing steps that would be involved in doing this.
Let me qualify what I'm about to say by stating that I appreciate people on this site who develop tools which allow us to hack our devices so we can make better use of our phones. They are incredibly skilled, gifted and generous with their time. I would love to be able to spend the time learning how to do this but I simply don't have the time. So please don't take what I am about to say as a criticism but more as an observation, considering the effort contributors put into this it would indeed be incredibly foolish of me to criticise anyone here.
I can probably safely say that none of the contributors are also trained technical writers and a fair number do not have English as their first language. Its my first and only language and I often have difficulty getting the meaning across succinctly not to mind getting the spelling right . And I know even for large software houses support documentation is not a priority.
I want to approach hacking my phone with confidence this time round. In the past I've reflashed several phones for myself and friends and simply followed steps and not really understanding completely what the hell I was doing. Lordmanhattan I know I sent you an email regarding a contradiction on your thread. And you very kindly got back to me very quickly.....amazing, thank you. And then there is the "TA partition", WTH is that? I did very briefly google this to find a quick answer but no joy....grrrr (also looked in the XDA Wiki acronyms) I'm sure if I looked hard enough I'd find it. It's mentioned everywhere but nobody seems to be offering an explanation what it is or what it does or why it's important or what it stands for !!!!
Very often I find threads on here describing how to do something hard to follow and this is often for the following reasons:
It could be that there is more than one way to achieve something so its a case of different people offering varied procedures, this can be confusing
A process may be described but then to the newbie the author seems to miss out on a step that to the experienced is obvious
The level of English used leads the reader to scratching their head wondering ...did he/she mean this or that
Threads not being updated or corrected even after feedback
Okay I won't go on.
So I have decided my time might be well spent doing some background research before delving into messing about with my Xperia Z Ultra and saving you guys from having to deal with daft questions from me.
Now does this mean I have to spend time reading through threads and trying to piece it all together to find the best way through and possibly getting the wrong end of the stick or reading superseded posts?
OR
Are there a couple of sites that will get me up to speed understanding the terminology, hardware, memory management, etc for my phone?
I have a feeling it's going to be a bit of both......your suggestions please
Oh, I stumbled across XDA University but got the impression it wasn't being maintained???
Some of the pages I visited....
A New User’s Guide to Android.......unfortunately none of the images for this page loaded
Video guides .................................had flash presentations which didn't load
Ferg8080 said:
I am a new Xperia Ultra owner...
Click to expand...
Click to collapse
A good and detailed post, and it's not just the dev's and support that could take note. Some of the people that ask questions really need to read your post and think about what they are trying to say, get help with -- we aren't mind readers either.
I always try and help anew user by using as few TLA as possible in a reply to them. I also try to do the steps as #'d lists with as many steps as possible.
I do think LordManhattan's guide needs a little love as a few things are a little out of date - but it is as comprehensive guide as you could get, and most vagaries are covered in the thread.
TA = trim area, where your unique DRM keys are stored, and god only knows what else.
Thanks for your well written post! First I want to say - like Blueether just did, that we are not mind readers, so we can't possible know people's skill level or what they want to do. That's why I've started to ask them straight up what they want to do and where in the process they are. That way it'll be easier for me to help the other person, and hopefully write a short but complete step by step guide. It won't happen that often, but if I got some time to spare, why not.
My guide is a little out of date now, and I have planned to update it for quite some time, but things are moving so god damn quick around here that even I will get outdated if I take a short break. I recently sent my Ultra in for repairs, and 12 days later when I got it back and ready to get back in the game, a new firmware had been released with a new rooting method. I knew everything one day, and nothing on the other. It's really hard to balance real life and being kept updated at all times. Don't forget that you must be sure about what you know and write when you make a guide, because you don't want to brick people's devices. One slipup and the consequences might be ugly.
There are (of course) one or four ways of doing things around here, and you'll probably get different ways of doing things if you ask me or blueether about rooting or flashing custom ROMs. I guess it's just the way it is. New methods also pop up once in awhile, so some people will adopt these new methods while some other people will stick with the old school method, thus making things a little more complicated for new people who are looking for reliable information.
The TA partition is, like blueether already said, your device's unique DRM keys which makes X-Reality (and other minor things, I guess) work. It's important to make a backup of this partition since you'll lose it when you unlock the bootloader. Why would you unlock the bootloader? You have to unlock it if you want to flash custom ROMs, or if you want to make rooting easier. The problem is that you need to be rooted to back it up, so you'll have to spend some time reading and researching before you start.
Just keep your Ultra stock for now, and just casually read and soak up stuff from different threads around here. Walk around like you do in a new city and check out the locals and see what they do and say. You'll pick up a few things here and there and things will start rolling from there.
Sent from my C6806_GPe using Tapatalk
blueether said:
A good and detailed post, and it's not just the dev's and support that could take note. Some of the people that ask questions really need to read your post and think about what they are trying to say, get help with -- we aren't mind readers either.
Click to expand...
Click to collapse
LordManhattan said:
a new firmware had been released with a new rooting method. I knew everything one day, and nothing on the other. It's really hard to balance real life and being kept updated at all times. Don't forget that you must be sure about what you know and write when you make a guide, because you don't want to brick people's devices. One slipup and the consequences might be ugly.
some other people will stick with the old school method, thus making things a little more complicated for new people who are looking for reliable information.
Just keep your Ultra stock for now, and just casually read and soak up stuff from different threads around here.
Click to expand...
Click to collapse
Yes you can see some people just rush in with questions without giving serious thought to what they want to achieve. I think its people who don't often understand the process properly, haven't thought it through and are following what seems like a straightforward step by step process. Understanding what you are doing requires patience and TIME.
XDA I think is an unrivalled repository of amazing contributions from amazing people on a technology that is constantly evolving. Its also a jungle. One doesn't go into the jungle unprepared
Thanks for the fantastic advice guys and I will heed but I can't promise I might come out with some corkers
One last thing, how on earth do you find the time to lead a normal life? You obviously love what you are doing. It might be easy to assume everyone who contributes here is in IT. I imagine there are plumbers, electricians, mechanics, office workers, retired folk.....

Need Help Getting Back to Stock Sense

Sooo, Ill start off by saying that I've unlocked, hacked, rooted, jailbroke pretty much every phone since it became available over the years. Im a careless tinkerer and have always stumbled across well written how to's to do everything I've need in forums like this and have great luck.
Well awhile ago, shortly after I got my AT&T M8, I decided to try and turn it into Google Play Edition. Somewhere along the way while in the process of doing S-OFF, something went wrong. I kept getting errors and couldn't get anything to flash. So I gave up and got the LG G3 and put the M8 aside for a bit. Well now I want to use it again, and along the way of "tinkering", I've managed to wipe TWRP, relocked the bootloader, have no OS and still S-OFF. I can boot into recovery or boot to the HTC screen so its not completely gone yet from what Ive researched.
Would anyone be willing to help me out in getting this thing back to stock Sense or point me in the right direction? I want it completely stock, without root or custom recovery. I'd rather a good step by step, if someone would be willing. I can't seem to piece together all of the information i need to do this myself. Thanks!
Have you tried this. http://forum.xda-developers.com/showthread.php?p=55094112
StupidN00b said:
Im a careless tinkerer and have always stumbled across well written how to's to do everything I've need in forums like this and have great luck.
Click to expand...
Click to collapse
Just RUU as suggested in the previous response.
I suggest leaving your phones stock, unless you are willing to put in the time to read, research, and obtain some real knowledge.
Step-by-step guides and toolkits are dangerous things. As you see, they just get you into trouble without giving you the knowledge or tools to get out of that jam.
I'm surprised you've modded as many phones as you say, and haven't gotten any real knowledge to this point. Either you are very humble; or your story is a testament to the fact that such step-by-step guides shouldn't be posted in the first place.
redpoint73 said:
Just RUU as suggested in the previous response.
I suggest leaving your phones stock, unless you are willing to put in the time to read, research, and obtain some real knowledge.
Step-by-step guides and toolkits are dangerous things. As you see, they just get you into trouble without giving you the knowledge or tools to get out of that jam.
I'm surprised you've modded as many phones as you say, and haven't gotten any real knowledge to this point. Either you are very humble; or your story is a testament to the fact that such step-by-step guides shouldn't be posted in the first place.
Click to expand...
Click to collapse
Thank you for your response but unfortunately I find it extremely arrogant and asinine. The fact is that I have put in a lot of time and knowledge to understand what I am doing. I may not have a conventional degree in coding as you might but I am able to successfully mod my phones by browsing forums like this where you can find an abundance of knowledge, especially step-by-step guides, as you are so against. If you are so against step by step guides then maybe you can be the voice about banning them from this forum. Do you see how I am a new member? I am one of the few that actually search the forums instead of posting another thread asking the same questions. Ive used tools and information from this site for a very long time without having to post one single thing until a few days ago. And this is the response I get? I was even humble enough in my screen name to call myself stupid because, with this specific issue, I knew it had to be something stupid that i was missing. You shouldn't tell people that step by step guides are dangerous things. All it takes is some balls and some command lines and you can accomplish many things. Have I messed up my phones and others before? Yes, but i had never run into a situation I haven't been able to get myself out of. To me, tinkering around, as a hobby, is fun. Like now, as I watch Sunday NFL Countdown, I am about to dust off my Nexus 5 and flash Lollipop on it. Guess what I am going to use? A STEP BY STEP GUIDE!!!! If I mess it up, then Im sure I wouldn't be the first to do so and Im sure Ill find a solution on great forums like this. Besides, my rooted/unlocked OnePlus One is my main phone. I wanted to play around with the M8 again to see if I would miss the smaller screen but I don't. So, thank you for just repeating the first response then proceeding to insult me because you think i don't have the skills needed to mod my devices. I will continue to do so however I please, just as many others will. Either contribute to threads or ignore them. No need for the insults. You've also insulted many other members who have posted tools and step by step guides on this specific site.
nuwayman said:
Have you tried this. http://forum.xda-developers.com/showthread.php?p=55094112
Click to expand...
Click to collapse
I actually did RUU but it ended up that I had a corrupt RUU file. I redownloaded it and put it on the MicroSD card and it worked like a charm. Thank you for your quick response.
StupidN00b said:
Thank you for your response but unfortunately I find it extremely arrogant and asinine.
So, thank you for just repeating the first response then proceeding to insult me
Click to expand...
Click to collapse
Quite frankly, incorrect on both points. You don't understand what an insult is, and there is nothing insulting in my post. If you read my post carefully, you will see there is no actual personal attack or insults.
redpoint73 said:
Just RUU as suggested in the previous response.
Click to expand...
Click to collapse
Contrary to what you suggest, backing up the previous suggestion is added value; as it adds credibility and consensus to the previous solution.
redpoint73 said:
I suggest leaving your phones stock, unless you are willing to put in the time to read, research, and obtain some real knowledge.
Click to expand...
Click to collapse
Its just a suggestion, and note that its conditional. Therefore, if you meet the latter part of the statement, the first part doesn't apply to you.
redpoint73 said:
Step-by-step guides and toolkits are dangerous things. As you see, they just get you into trouble without giving you the knowledge or tools to get out of that jam.
Click to expand...
Click to collapse
I stand by this statement. I've seen dozens dozens of instances where such tools just arm people with enough "knowledge" to get them into trouble, and don't equip them with any tools to get them out. Its then left to folks like me to even start to get these folks on the right track.
I'll step back a bit from my statement that these tools "shouldn't be posted in the first place". I'll agree that step-by-step guides and toolkits might be useful if combined with the proper research, learning and understanding. But in and of themselves, they can easily lead newcomers astray.
redpoint73 said:
I'm surprised you've modded as many phones as you say, and haven't gotten any real knowledge to this point. Either you are very humble; or your story is a testament to the fact that such step-by-step guides shouldn't be posted in the first place.
Click to expand...
Click to collapse
I already gave you the benefit of the doubt here, but you chose to react defensively and in my opinion, unreasonably.
In any case, as far as your knowledge and background, we can only go by what you've stated; and you clearly stated yourself as a "careless tinkerer" and "stumbled" upon solutions. Now in your later post you say "I have put in a lot of time and knowledge to understand what I am doing". So if you provide conflicting information as to your background, nobody can be blamed for making an incorrect assumption regarding your knowledge.

Categories

Resources