To All Who Use Easy Root Methods - Thunderbolt General

Stop getting angry when we do not want to help you fix the problem you are having. Seriously, quit it. You are warned left and right that you may not or will not get support for it. The simple fact is that auto/easy root methods are too questionable. It leaves you in the dark when something goes wrong. We cannot easily figure out what happened, why it happened, or what exactly the issue is because it is automatic. I'm annoyed at the amount of users who go onto IRC begging for help and start freaking out on us because YOU wanted the easy way out. It doesn't take more then a Google search to learn exactly what to do, what it is doing, and how it works for the manual root method. I can only speak for myself but I'm plenty sure other members can agree and attest to this. I, myself, spend more time helping lazy/scared people FIX their phones BECAUSE of an easy root method then doing any real development! And when I decline to, the AndIRC chatroom becomes a hated place and gets bashed on. Use at your own risk. Enjoy.
Sent from my ADR6400L using XDA Premium App

If you don't want to help, don't help. People have every right to ask for help and if they freak out on you for not helping, ignore them. All you're doing by posting this thread is returning the sarcasm and snarkyness that you're accusing them of dishing out.

No no no. ProTekk is 1000% right on this. I get tired of lazy assholes on IRC who want to be spoon fed.
Sent from my ADR6400L using Tapatalk

Tbh, this wasn't an "I'm better and smarter than you" post. It was meant to be a clear and valid warning to all. In no way was I trying to come off as snarky or a know it all. If you take this the wrong way then maybe you need to.reread this and start over again.
Sent from my ADR6400L using XDA Premium App

Oh, also, I explain in detail why and what my reasoning is. Don't start flaming buddy
Sent from my ADR6400L using XDA Premium App

I agree 100%.
There are a lot of new people moving into android with this phone, and a lot of progress has been made through development inthe few weeks it has been out.
People really need to slow down, and read before jumping. I think that was proven this morning...good one Jcase
I've had a rooted phone for over a year now, been through roms like mad, but still get nervous and re-read every post before I put something on my phone and understand exactly what it's doing.
Take your time people, read, re-read, ask questions, then flash, your phones not going anywhere unless you do something dumb and end up with a brick....which would more than likely be your fault if it happens.

Bimmer323 said:
I agree 100%.
There are a lot of new people moving into android with this phone, and a lot of progress has been made through development inthe few weeks it has been out.
People really need to slow down, and read before jumping. I think that was proven this morning...good one Jcase
I've had a rooted phone for over a year now, been through roms like mad, but still get nervous and re-read every post before I put something on my phone and understand exactly what it's doing.
Take your time people, read, re-read, ask questions, then flash, your phones not going anywhere unless you do something dumb and end up with a brick....which would more than likely be your fault if it happens.
Click to expand...
Click to collapse
Forgot about the questions. They.are more than welcome if it is about rooting. Ask away. We share knowledge. We don't hoard it and say go home. Glad to see some voices in here besides mine.
Sent from my ADR6400L using XDA Premium App

Completely agree with protekk. Devs can not help you if they don't know the exact process of rooting went wrong if you use a "1 click" method. Using the process put out by jcase a person can start over or even go back to the prior step. The process jcase put out was a step by step (copy & paste commands) process. I am no better than any of you, but I can read and follow simple instructions, and in doing so have gotten a good understanding of adb. As for getting help, I have never had a problem with getting help, even when I started.
When rooting or flashing, you need to read, read, read, read, until you are comfortable with the instructions. Xda has info to getting everything setup and running. Research before you flash or root.

+1 man. I've only had my Thunderbolt for a few days and ended up deciding to root manually because I wanted to know what was going on, step by step. It's taking a little time to get used to CWM coming from the Eris where I've used Amon Ra's recovery.
<soapbox>
I've noticed a trend of folks really beating up on the dev's. Guys, our dev's do this for free or donations. Some even insist that we donate to the homeless or our favorite charity. You're not paying for support, these guys do what they do out of love and commitment to the community. Please remember this before you log onto IRC or make a new thread. The dev's have gone through a lot of trouble to learn these systems and write scripts for you, usually through reverse engineering and a lot of time. Respect their time by searching first.
Additionally, if you need help - please and thank you goes a long way. So do logcats and output from the screens that you're currently working with
Now, back to your regularly scheduled discussion.
</soapbox>

All I'm saying is I remember a lot of people complaining about jcase, not wanting a 1 click root released . He wanted people to know what was being done and how to do it. And people complained saying he had no right. I believe this is why he didn't want it released to soon. Damn I hate mind readers. Lol
Sent from my ADR6400L using XDA App

"ProTekk is 1000% right on this."
"+1"
If someone doesn't want to put in the time to understand what is going on and the processes taken to make it happen they shouldn't even bother rooting.

This is my first android phone ever. I have successfully rooted it on both a mac and pc. I followed the instructions and learned how to use adb (nothing fancy of course). If I can learn others can too.
Sent from my ADR6400L using XDA App

Thats a good point OP.
The method posted by JCASE is so simple that anyone should be able to do it.
1) Install drivers for your phone
2)copy files to your ADB directory and to your phone SD card
3)Open a command prompt
4)Copy and paste a bunch of ADB commands
5)Put the other PG05IMG.BIN on your phone
6)Copy and paste some more adb commands
7)Download a few market apps
8)Success
I mean where is that difficult? Its basically spoon fed. If you don't have the ability to copy files to your phones SD card, copy and paste commands into a DOS prompt, follow clear instructions, and install driver software for your phone, then you probably shouldn't bother doing anything. I don't even consider myself an ADB pro, I learned how to use some of it with my MOTO Droid and I still don't know what a bunch of the commands are. I know how to push files to my phone, how to pull files from my phone, and some other misc commands.

I agree. I was frustrated sure. Took me another 7 tries and a few different methods. But in the end I was the one responsible. I could have chose to give up , but because I didn't want to be left behind I kept learning and trying. I finally got it last night. It even feels better knowing how much trial and error I had to try. Makes me appreciate it more.
Sent from my ADR6400L using Tapatalk

TNS201 said:
Thats a good point OP.
The method posted by JCASE is so simple that anyone should be able to do it.
1) Install drivers for your phone
2)copy files to your ADB directory and to your phone SD card
3)Open a command prompt
4)Copy and paste a bunch of ADB commands
5)Put the other PG05IMG.BIN on your phone
6)Copy and paste some more adb commands
7)Download a few market apps
8)Success
I mean where is that difficult? Its basically spoon fed. If you don't have the ability to copy files to your phones SD card, copy and paste commands into a DOS prompt, follow clear instructions, and install driver software for your phone, then you probably shouldn't bother doing anything. I don't even consider myself an ADB pro, I learned how to use some of it with my MOTO Droid and I still don't know what a bunch of the commands are. I know how to push files to my phone, how to pull files from my phone, and some other misc commands.
Click to expand...
Click to collapse
I'm considering moving to Android, possibly the Thunderbolt. I'm experienced with flashing custom ROMs to WinMo 6.X phones, but that's not a root process (at least not on any phones I've owned), it's a simple process of connecting the device tp a PC via USB, launching a program on the PC, clicking a few buttons and restarting the phone. Done.
Coming from that simplcity, the rooting process looks kinda daunting, but not impossible. I've been reading as much as I can in different forums, but without having the phone in front of me and trying it out, I'm not understanding the process.
For instance, "Open a command prompt." Is this on a connected PC, or directly on the phone? If on the phone, how do I get to a command prompt on it?
I guess I'd like to ask the knowledgeable folks here for a website they'd recommend for an absolute beginner to bone up before attempting his first root? Or multiple sites, where I can not only read how it's done, but what is actually happening at each step. I know my way around Windows pretty well (up to XP anyway), but have no idea when it comes to Linux.
As to folks who dork up their phones while trying to root/modify - the devs are offering their knowledge, free of charge. You aren't being forced to root, it's your choice and ultimately your responsibility. I've seen the occasional Sp.Ed. flip out because his phone bricked while flashing a WinMo custom ROM that someone spent many hours working on and tweaking. Not often, I'm glad to say - most folks are grateful for the effort.

This was my first android phone, and initially I was too scared to do the manual method. But, I manned up and decided to do it, and to be honest, it was simple. After that, I tried reading all the threads and being active in the community. That's the thing with attaining knowledge, you have to be proactive. Read through everything, and often. Don't just ask questions only when it pertains to your problem, because from what I've seen, it's always answered in some thread.
tl,dr:The gist, just be proactive. read read read

tedkord said:
I'm considering moving to Android, possibly the Thunderbolt. I'm experienced with flashing custom ROMs to WinMo 6.X phones, but that's not a root process (at least not on any phones I've owned), it's a simple process of connecting the device tp a PC via USB, launching a program on the PC, clicking a few buttons and restarting the phone. Done.
Coming from that simplcity, the rooting process looks kinda daunting, but not impossible. I've been reading as much as I can in different forums, but without having the phone in front of me and trying it out, I'm not understanding the process.
For instance, "Open a command prompt." Is this on a connected PC, or directly on the phone? If on the phone, how do I get to a command prompt on it?
I guess I'd like to ask the knowledgeable folks here for a website they'd recommend for an absolute beginner to bone up before attempting his first root? Or multiple sites, where I can not only read how it's done, but what is actually happening at each step. I know my way around Windows pretty well (up to XP anyway), but have no idea when it comes to Linux.
As to folks who dork up their phones while trying to root/modify - the devs are offering their knowledge, free of charge. You aren't being forced to root, it's your choice and ultimately your responsibility. I've seen the occasional Sp.Ed. flip out because his phone bricked while flashing a WinMo custom ROM that someone spent many hours working on and tweaking. Not often, I'm glad to say - most folks are grateful for the effort.
Click to expand...
Click to collapse
look on you tube they have a real nice walk thru you should watch first
http://www.youtube.com/watch?v=mc6EMdPpF6o&annotation_id=annotation_68322&feature=iv
thanx nat3mil

Bimmer323 said:
re-read every post before I put something on my phone and understand exactly what it's doing.
Click to expand...
Click to collapse
Ayup. either a long contract or an expensive phone I do not want anything bad to happen to it
with my og droid I would do just about anything to it because that thing was bulletproof and I got buy 1 get 1 free .
my thunder bolt, it's treated with kid gloves
this is not a signature I type it in every time maybe sent from my phone or my computer

I have to agree for the most part...I rooted my bolt with the very first method released and it took me quit a while...had to do allot of reading (adb). I got most of my questions answered by going threw the threads.... reading other peoples problems they posted and then the fixes or answers left by knowledgeable forum members. Yes that takes time but it does help...I will vouch for that...lots of knowledge and answers here just have to put in the time.
I think people should be able to ask questions on here...thats part of why the forums are here, but if you ask and you don't get answer it's more than likely you have ask a question that has been asked before...several before's....Its just to basic of a question which could have several answers (not enough info in the question)....or you ask to many questions which means you have not done your home work.
Read and then read some more....google and google some more.....then ask the question....

+1000
People want to be spoon fed - doing things the right way is too hard for them

Related

Newbie guide to rooting Inspire 4G?

So I'm curious if anyone can point me in the direction of a good guide for a first-time rooting experience.
I am BRAND NEW from the iPhone world. Over there I was very comfortable jailbreaking, with the process and terms, and ins and outs of the jailbreaking world.
Now I just got my inspire 4g and I'm lost in trying to learn the root\flash\rom process. I feel like such an idiot because I always get pissed when people ask for step by step newbie process in the iOS jailbreak forums, now I'm doing it, lol
My goal is to root is for the sole purpose of enabling the HSUPA feature. I'm unlocked already (bought an unlock code), so that's really the primary reason for unlocking for me.
An additional benefit would be able to remove the AT&T bloatware, which is annoying me. Does anyone actually use the ATT branded barcode scanner? LOL.
Anyhow, if anyone is willing to help, I would appreciate it greatly.
Thanks!
check out this video guide.
http://forum.xda-developers.com/showthread.php?t=957559
epicKA8 said:
check out this video guide.
http://forum.xda-developers.com/showthread.php?t=957559
Click to expand...
Click to collapse
I followed this video.. this is my first Android phone and first time rooting a phone... the video was perfect and rooted and installed a custom ROM with no problem.
epicKA8 said:
check out this video guide.
http://forum.xda-developers.com/showthread.php?t=957559
Click to expand...
Click to collapse
I seriously can't be this stupid. LOL. I have watched this 20x and I figure I can follow it step by step and have success, but the question I have is this:
- Is there a way to not have to do step 1 then step 2 to correct the audio? In other words has anyone compiled a video or written step by step on a process that does it without having to go back and fix the audio?
- If I do this method, when I re-login to google, will it re-download all the apps I had previously downloaded? And will it re-add the email accounts, or do I have to set it all up as new?
- I see many referring to the "stock ATT" ... so that'll bring back the ATT stuff, but remove the limitation and allow HSUPA? And does it re-add bloatware but I can then delete it? Do all the stock themes\apps come loaded still?
Thanks, I really wish there was a "here's exactly what to do, step by step, keystroke by keystroke" kinda to-do style list... I know many prefer seeing on youtube, but I'm more of a process\step-list type, and it's confusing because the forum has about 10 sets of instructions, some say they have audio problems, others have an amendment to fix the audio after, some say it's possible not to have the issue to begin with, just trying to make sense of it all as I'm totally new to Android.
I an having nothing but trouble also!
Finally I can make it to the bootloader screen but any option I choose locks thephone with the "Scary Emblem" and I have to remove the Battery to restart it.
Anybody able to help?
Please?
http://forum.xda-developers.com/showthread.php?p=11908710
bella92108 said:
I seriously can't be this stupid. LOL. I have watched this 20x and I figure I can follow it step by step and have success, but the question I have is this:
- Is there a way to not have to do step 1 then step 2 to correct the audio? In other words has anyone compiled a video or written step by step on a process that does it without having to go back and fix the audio?
- If I do this method, when I re-login to google, will it re-download all the apps I had previously downloaded? And will it re-add the email accounts, or do I have to set it all up as new?
- I see many referring to the "stock ATT" ... so that'll bring back the ATT stuff, but remove the limitation and allow HSUPA? And does it re-add bloatware but I can then delete it? Do all the stock themes\apps come loaded still?
Thanks, I really wish there was a "here's exactly what to do, step by step, keystroke by keystroke" kinda to-do style list... I know many prefer seeing on youtube, but I'm more of a process\step-list type, and it's confusing because the forum has about 10 sets of instructions, some say they have audio problems, others have an amendment to fix the audio after, some say it's possible not to have the issue to begin with, just trying to make sense of it all as I'm totally new to Android.
Click to expand...
Click to collapse
Please let me know if you find instructions like that. I am the same way. I literally have had my Inspire from ATT for 2 days after having six BlackBerry's and all I get are rude remarks, links to videos that assume I've done this before and absolutely no questions answered. I was referred to use the Unrevoked3 which is supposed to be "painless" and could work with the Inspire since it's similar to Desire, but all I got was a link to the download and if I try to ask questions, I'm not allowed because I'm a noob or I get the "Google it" response...which...duh..that's how I found this place. Every Android forum reminds me of my Business Calculus professor. When asked if he could walk us through a six page homework problem, he threw a desk at the wall and called us names. LOL I guess only elite are allowed info. I can't even get a response as far as whether or not Unrevoked3 will actually work on the Inspire! Sigh. *smh*
StoopidNoob said:
Please let me know if you find instructions like that. I am the same way. I literally have had my Inspire from ATT for 2 days after having six BlackBerry's and all I get are rude remarks, links to videos that assume I've done this before and absolutely no questions answered. I was referred to use the Unrevoked3 which is supposed to be "painless" and could work with the Inspire since it's similar to Desire, but all I got was a link to the download and if I try to ask questions, I'm not allowed because I'm a noob or I get the "Google it" response...which...duh..that's how I found this place. Every Android forum reminds me of my Business Calculus professor. When asked if he could walk us through a six page homework problem, he threw a desk at the wall and called us names. LOL I guess only elite are allowed info. I can't even get a response as far as whether or not Unrevoked3 will actually work on the Inspire! Sigh. *smh*
Click to expand...
Click to collapse
I have found all the information I have needed to date by reading first. It's not an attitude unique to this forum... it happens elsewhere on the internet.
With processes like this, I would think one would want to be armed with as much knowledge prior to starting, as possible.
People get stuck on unique problems, and ask for help, and nearly without exception, if some degree of effort has been made by the person asking, then people are pretty willing to assist.
If people come in an ask questions that would have been easily answered had they taken the extra five minutes to check if it had been addressed already, it shows... its easy to tell if someone has made even the slightest effort to educate themselves first, or if they're just expecting free technical support.
Sent from my Inspire 4G using Tapatalk Pro
Can't we all just get along?
For any newbies wanting to get started and have step-by-step instructions, you should visit the Hack Kit thread, download the zip file, and read that readme!
Link to hack kit thread:
http://forum.xda-developers.com/showthread.php?t=952352
To be honest, I think if the hack kit thread was made into a sticky it might get more attention from the new inspire owners.
EDIT: Just to be clear. The hack kit contains a full step-by-step procedure. The only change to this I recommend is using the gold card maker in the following thread (unless it's now included with the kit) :
http://forum.xda-developers.com/showthread.php?t=970157
Give a man a fish and he'll eat tonight teach a man to fish and he'll eat the rest of his life, or something.
[harsh mode]This stuff isn't brain surgery. If you want root badly enough you'll figure it out. [/harsh mode]
gunnyman said:
Give a man a fish and he'll eat tonight teach a man to fish and he'll eat the rest of his life, or something.
[harsh mode]This stuff isn't brain surgery. If you want root badly enough you'll figure it out. [/harsh mode]
Click to expand...
Click to collapse
LOL, i get that, but you cant throw him a pole, a hook, and bait and say, read this and learn.
I think there is an important difference between a newbie who wants the answers spoonfed to them, and a newbie who is genuinely trying but just doesn't get it. Some people (myself included) need a little hand holding through the process. It's sort of like pulling someone out of a third world country who's never seen a car, and expecting them to learn to drive by reading a drivers ed manual.
Sent from my Inspire 4G using XDA App
I've seen a few please root my phone for me threads. These people make me crazy. I don't know what else to say. We have bubbys super easy method and the hack kit which has a easy to follow step by step and a video. I've only had one phone that was 1 click root capable, the Captivate. The others were work, so I learned. I was a noob once, we all were. But I educated myself. There are folks which don't want to even try to do that.
Sent from my Desire HD using Tapatalk
I have to say, I'm with NOOB here.
As far as "bubby's" super easy one click, ya, maybe IF I had time to read through 238 pages of geekchat banter and decode the "FAQ" that was written in a haphazard method.
Nothing personal, but maybe YOU guys know how to do this but many of us do not.
I've spent 3 days going over instructions, videos and other how-to's only to find myself frustrated at the process and procedures.
I'm now at the point where I can get to my boot loader but no matter what mod.zip file I have on the root of the card I get a black screen.
2 things RIGHT off the top of my head that were not discussed (or at least I didn't find them in).
1- The original CID I sent to have a gold card made from was bunk. Only during my (IDK) 10th attempt at running bubby's one click root did I notice the CID had changed and sent that one in for a gold card did it work.
2- NO where in any instructions or FAQ did it mention to hold the "UP" button when rebooting to access the recovery mode. Which BTW, still doesn't work properly.
Maybe I got a bunk phone. Who knows. But I do know this. It took my less time to root my nexus one and even less time to quickpwn my iFails.
You would think with all the knowledge that exists in this forum, someone would sit down and make a step by step guide on how to root your HTC Inspire from start to finish INCLUDING potential pitfalls and errors.
Instead, new users such as myself and NOOB are left to decypher and piece together a way to root the phone.
No one has asked you to root their phone. All the NOOBS like myself are asking is for you to pool your collective intelligence and come up with a GUIDE even an IDIOT like myself can follow.
... and make it a sticky with NO additional chatter on the thread.
corbin dallas said:
I have to say, I'm with NOOB here.
As far as "bubby's" super easy one click, ya, maybe IF I had time to read through 238 pages of geekchat banter and decode the "FAQ" that was written in a haphazard method.
[...] No one has asked you to root their phone. All the NOOBS like myself are asking is for you to pool your collective intelligence and come up with a GUIDE even an IDIOT like myself can follow.
... and make it a sticky with NO additional chatter on the thread.
Click to expand...
Click to collapse
I mean no hatred, but rooting this phone isn't an easy process. I've been hacking windows phones for years but this was my first android root and it took me over 4 horus start to finish - and i had to troubleshoot a lot of problems on my own since it was 6 am with no one on xda. the problem with creating a complete hacker's guide is that there are SO MANy unique issues that people have, that there's no way to account for all of them if you're able to do it on your own successfully - then in that case why would you go back and try to mess stuff up to create a page about waht to do if XXXXXX happens? I had some issues during my root process, but I posted somewhere asking for help, detailing exactly which steps i had taken prior to having trouble, what my issues were specifically (including code), as well as what i did to FIX my issues after I had figured it out. People here don't like being asked vague and general questions about why xxxxxxx isn't working, which is why usually tehy like for people to be as specific as possible. I'm not angry with your or any other person that has issues rooting, but i'm simply trying to explain why other people get pissy and are brief when a little morehelp would do. a lot of people just need to read a bit more before they post, which is what pisses everyone off, but hey, we all need to start somewhere right?
as for your specific issues, did you use the CID1 or the CID2? The guides (video and hack kit) both call for you to use the CID2 so if you didn't use that right off the bat, that's waht your issue was. As for your black screen, what step are you talking about? Are you able to downgrade your rom? or is taht where you're having issues? and i didn't use any of bubby's one click stuff, but what's teh mod.zip file supposed to do? I followed the hack kit and video walk through both and adb sent the downgrade rom to my phone, it rebooted into recovery (ON ITS OWN - i didn't have to get it into recovery myself) and i had to scroll to tell it to load the rom and that was it. maybe your issue is that you're skipping steps? do you have a good connection to your phone between your comp/is teh whole downgrade rom being transferred to your phone? I know i had that issue where after 4 or 5 commands from the command prompt, it would lose connection with my phone and i would have to restart before i could send another command through adb...
lastly, to answer your question about the one click rooting, i think we all wish tihs phone had that, but it doesn't and it sucks. as i'm sure you've read, the only way to do this is through a radio exploit in a downgraded rom thanks to att being a bi***a** about sideloading and whatnot. it is waht it is.
anyways, i hope i answered your questions adn maybe even helped you out with the rooting. if you need more help, feel free to start another thread and PM me the link to it. hopefully i'll check my PM's and be able to help you with it. jsut remember, be as descriptive as possible and no one will flame you
Scott_S said:
I have found all the information I have needed to date by reading first. It's not an attitude unique to this forum... it happens elsewhere on the internet.
With processes like this, I would think one would want to be armed with as much knowledge prior to starting, as possible.
People get stuck on unique problems, and ask for help, and nearly without exception, if some degree of effort has been made by the person asking, then people are pretty willing to assist.
If people come in an ask questions that would have been easily answered had they taken the extra five minutes to check if it had been addressed already, it shows... its easy to tell if someone has made even the slightest effort to educate themselves first, or if they're just expecting free technical support.
Sent from my Inspire 4G using Tapatalk Pro
Click to expand...
Click to collapse
/begin rant
You read my mind...
Honestly people, the development thread has practically every answer to any question that could come to mind throughout the process, but you have to be willing to put in the effort to read pages upon pages of advice.
A few days of reading and learning will reward you with a perfectly rooted device, but you can't be lazy about it.
If after sifting through the development thread (and using a handy little tool called google...) you still can't make any sense of this, maybe you should ask yourself if you should really be doing this in the first place?
These developers work hard to put out what we have available today and they really jumped on this particular phone rapidly, and the methods available today work. I used bubby323's "HTC Inspire 4G Simple Root and S-Off" and from start to finish I rooted two Inspires and loaded them with custom ROMs in under an hour.
At least meet them halfway in the effort department people.
/end rant
Keep in mind also that those of us who rooted had to read through pages and pages and pages if we got stuck, it's rather annoying to read "I didn't want to have to go through that huge thread to find my answer" What makes you so special?
corbin dallas said:
I have to say, I'm with NOOB here.
As far as "bubby's" super easy one click, ya, maybe IF I had time to read through 238 pages of geekchat banter and decode the "FAQ" that was written in a haphazard method.
Nothing personal, but maybe YOU guys know how to do this but many of us do not.
I've spent 3 days going over instructions, videos and other how-to's only to find myself frustrated at the process and procedures.
I'm now at the point where I can get to my boot loader but no matter what mod.zip file I have on the root of the card I get a black screen.
2 things RIGHT off the top of my head that were not discussed (or at least I didn't find them in).
Click to expand...
Click to collapse
Where exactly are you at in the process? Do you have S-OFF and can you confirm you are rooted? If so, you have already done the hard part. Am I reading correct that when you try to get into recovery mode (via rom manager or by Vol-Down + PWR) that the phone reboots and then fades to black?
this would require you to do eng s-off, i had the same issue with inspire
I researched for a. Week...reading everything I could find....which included 238 pages and an faq that...was written haphazardly (though I found useful) prepared myself for any eventuality.

Dear all wooters, please don't try to do modding yoga

I may be imagining it, but it seems like there's a steady increase of "help, I bricked my gtab" threads as people are starting to receive their woot's gtabs. Please stop and think. Have you ever done something like modding an android device before? Is it worth it?
If it ain't broken, don't try to fix it.
I currently got 2 gtabs. One I have modded the hell out of and the other I'm keeping the stock rom. What you can do is go to settings and set it to classic. The annoying weather TnT thing will go away and your gtab will work just fine. Very fast. Very sexy. Love you long time.
I beg you, please help yourself and consider just staying with the classic stock rom. I've been playing with it and I see nothing wrong with it. Works wonderfully.
One user on here came and said when he first started playing with the gtab in office depot he was expecting the worst screen ever because of all the negative reviews about the screen. But to his surprise, it turned out to be very pleasant. Why? Because people on the internet like to exaggerate.
And in this case, people really did exaggerate the unusability of the stock rom. If you're not doing aerobics and yoga with the gtab, you won't notice it. Please do yourself (and us all) a favor by not simply plunging into modding as soon as your gtab arrives. Play with the stock rom first. Make sure you set it to classic. Give it a couple days before you decide to whether put a custom rom on there or not.
Please think about what I just said. Amen.
+1 good advice!!!!!!
x2. And please read up on things like adb and nvflash BEFORE you you start modding. Imo, anyone modding their device should have these tools handy, in advance.
"adb", for example, is almost a standard requirement in other Android phone forums. But for some reason it's not stressed here - I am guilty of that as well. I think that, if you are taking the risk (and it IS a risk) to mod your device, you should have the tools to save yourself from yourself. There's a nice writeup on nvflash that I posted (and "Rev" wrote) and adb instructions are all over the place, not just here.
Thanks!
i dont understand where all the problems come from. if you do it just like the guide tells you, shouldnt it work? i havent dont it myself but ive read and reread the guides. arent they all exactly the same out of the box if there ota version is the same? is it people are just not following directions? cause its seems pretty simple to me even though i havent done it before.im planning on doing it and if i follow the directions exactly and it doesnt work, im just gonna throw it out the window.
Also, I forgot to add.
I work in a research lab. Even though I'm an engineer, I'm really the acting tech guy. As a side job, occasionally I make house calls to fix people's computer problems.
It is my experience that not-so tech savy people always manage to find problems that us techies would never find. Not only that, not-so tech savy people most of the time can't remember what they did and can't verbalize what they did. This makes it 100x harder on us techies.
You see, there are unspoken rules in the world of tech. For example, dealing with system files is risky. Deleting them is bad. Things like that. Not-so tech savy people don't know these rules and so they just stumble all over the place finding and creating problems that the tech people would never find.
What I just said above means that when you find (or create) a problem and you didn't follow the proper procedures, you're not always going to find someone that knows a solution. Why? Because the rest of us never dared to go down that dark narrow alley that you decided to run into. We don't know what's in there. And if you manage to find a 3 headed troll, how are we to know what to do since we've never been down that alley?
Take it for what it's worth. If I haven't detered you, at least have adb and nvflash ready. And make sure you know what you're doing with those.
fridge011 said:
i dont understand where all the problems come from. if you do it just like the guide tells you, shouldnt it work? i havent dont it myself but ive read and reread the guides. arent they all exactly the same out of the box if there ota version is the same? is it people are just not following directions? cause its seems pretty simple to me even though i havent done it before.im planning on doing it and if i follow the directions exactly and it doesnt work, im just gonna throw it out the window.
Click to expand...
Click to collapse
(1) Not-so tech savy people like to take short cuts for whatever reason. They also sometimes skip important steps in a procedure even though it's right there in front of them. At least one wooter has already bricked his gtab without backing up.
(2) No, they're not all exactly the same out of the box. Nothing is ever all exactly the same out of the box.
(3) Everything seems simple to me, too. But according to my experience, what seems simple to someone with experience isn't always simple to everyone else.
Just last week, I went to a woman's house to help her with computer problems. She made it sound like life and death on the phone. The only reason I tolerate her is because she might be my in law one day. Anyway, it turned out that the problem was she thought the monitor was the computer. We have explained to her over and over that it's only the monitor and that the box sitting below is the computer. Seems silly to us, but there it is.
fridge011 said:
i dont understand where all the problems come from. if you do it just like the guide tells you, shouldnt it work? i havent dont it myself but ive read and reread the guides. arent they all exactly the same out of the box if there ota version is the same? is it people are just not following directions? cause its seems pretty simple to me even though i havent done it before.im planning on doing it and if i follow the directions exactly and it doesnt work, im just gonna throw it out the window.
Click to expand...
Click to collapse
My transition from stock 3588 to tnt lite 5 now twotapsx went smooth as butter however some devices moving from other mods back down to 3588 and then to twotapsx had problems!!! The biggest issue was a confusion on using clockwork mod recovery as those who tried it with the ttx mostly found themselves semi-bricked which led to a literal borkathon . Most issues were from user error but on some cases there were oddball problems that just popped up!! So my point is that in Modding your tablets to anything other than stock you are risking a BORK but if you follow directions and have the proper backouts tools ready such as nvflash and adb you should be ok.
goodintentions said:
(1) Not-so tech savy people like to take short cuts for whatever reason. They also sometimes skip important steps in a procedure even though it's right there in front of them. At least one wooter has already bricked his gtab without backing up.
Click to expand...
Click to collapse
+100 on this one. I have a friend that I had to help with rooting her evo and Gtab, and had to ask her every step she took to make sure she actually took them. Luckily she learned early on to use Nandroid and keep a backup of the stock rom and any working roms before you switch to another one.
fridge,
I've skipped posts after yours to answer you, so I apologize if I duplicate something.
YES, if you do everything right bad things CAN happen:
1. Android is not a well-documented operating system and something you just "think" your doing it right.
2. The G-Tablet can be cranky. Unexpected things happen. The other day my pristine, perfect tab
was shut down properly. Next time I turned it on I had huge
"android.process.acore" errors and I had to fix it.
3. I don't know of anyone who has revealed themselves on this forum that thoroughly
understands the structure of the OS software on the G-Tablet. Read all the posts
on boot.img and partition structure. It really would help us all if we knew more.
4. There are a lot of good people who "help" others on this forum Most give good
advice most of the time -- but those of us that are human make mistakes once in a while.
And honestly, some helpers may not give good advice -- don't do it if you don't
understand and feel good about it.
5. Some people don't abide by good IT practices. I saw someone trying to get help
the other day that had barely gotten started with the G-Tab and already had CWM and had
tried three or four ROMS and other related software -- and had a soft-brick!
People need to move slow and check things out more carefully.
6. And some of the software posted here for your use may not even work right. I know a
couple of programs I have seen associated with lots of crashes. If a program
is listed in the threads with lots of crashes around it -- you better be careful!
I could go on for a long while further. If you REALLY read the forum and what's going
on instead of just looking for things to install, you will see these patterns.
Rev
Agreed completely with the intention of this post but I don't think the increase of people messing theirs up is due to woot just yet. I ordered one from the woot sale and i am fairly sure that it hasn't even shipped yet, the email said within 5 days. They aren't the fastest at shipping stuff.
It's probably more so just due to the dropping price in general.
People who have not done any moding of other android devices before should absoltely so slow and wait on loading whole roms until they get familiar with it and read up a lot and do their homework otherwise they will risk breaking their device.
Sent from my ACS frozen Epic
May or may not be Wooters but several *have* posted that they have recieved them.
Adding one small thing I've learned over the years: sometimes an install/upgrade/mod just doesn't take the first time. Or the second. Or the third. Patience is a key to sucess in these things. If it doesn't work the first time, come back the next day and try it again.
Repeating again: READ the forums and all the old threads. Go back and read them again.
And if you don't do backups, I have no pity for you.
iamchocho said:
Agreed completely with the intention of this post but I don't think the increase of people messing theirs up is due to woot just yet. I ordered one from the woot sale and i am fairly sure that it hasn't even shipped yet, the email said within 5 days. They aren't the fastest at shipping stuff.
Click to expand...
Click to collapse
Actually, mine from woot is due to arrive tomorrow. May be that's because I ordered mine 10 minutes after midnight.
But regardless, people need to think twice before deciding to take the plunge.
Edit.
And I'm just cranky because I just found out this morning I've been a victim of credit card fraud. Someone's been doing a lot of shopping online with my credit card. Mostly games, so I'm guessing it's some spoiled brat somewhere who got lucky at hitting random numbers and got mine.
roebeet said:
x2. And please read up on things like adb and nvflash BEFORE you you start modding. Imo, anyone modding their device should have these tools handy, in advance.
"adb", for example, is almost a standard requirement in other Android phone forums. But for some reason it's not stressed here - I am guilty of that as well. I think that, if you are taking the risk (and it IS a risk) to mod your device, you should have the tools to save yourself from yourself. There's a nice writeup on nvflash that I posted (and "The Rev" wrote) and adb instructions are all over the place, not just here.
Thanks!
Click to expand...
Click to collapse
I've been lurking on the gTab forums here for the last several days, and have been trying to absorb all of the info I can. I tend to research everything in depth before I plunge into anything. While much information is here, it is fragmented, and what is easy to follow for a developer is not as easy to follow for others. roebeet, you do the best of any I've seen, and I appreciate it. I've done a lot of searches which have helped some. I'm not new to Android (or XDA) as I have a stock Droid Incredible, but I am new to mods to Androids. I have also used Linux in the past, and modded kernels for newer drivers using cookbook approaches, so little scares me if I have enough information. I've sort of figured out how to install and use nvflash, ADB, and CWM using the various guides, but I'm missing some fundamental knowledge on WHEN and WHY I should really be prepared to use them. I've also tried to do some reading on Nandroid, but have found little pertinent to the gTab. So here goes:
1. What is the primary use of each of the following tools, nvflash, ADB, and CWM? When should I expect to have to use each of them? Are there gTab specific guides to their uses and the options for each outside of ROM installation guides, etc? Specific examples of when I should use each, and even more important, when NOT to use them, would be helpful. I've read all of the ROM, nvflash and ADB installation guides, and the various FAQs, and I understand HOW to install each of, just want to understand the best practices for each.
2. After reading a lot, it appears that having a complete backup of my particular ROM would be a good idea since partitions seem to differ even on stock gTabs. I've read posts here that refer to Titanium, and the use of ADB and CWM to do backups, and others that refer obliquely to Nandroid. What is the use of each of the above to do backups? It appears that Nandroid is a piece of CWM, but I may be mistaken. And if I install TnTlite using roebeet's guide, I'm not supposed to use CWM anyway. So how do I do a backup?
3. I plan to use my gTab as I get it, allowing it to do OTA updates only, for a few days, playing with the TNT and normal Android interfaces. I understand that a major OTA may be imminent anyway, possibly based on the leaked 3991 ROM, so my current plan is to wait for it, at least for a week or two. I plan to explore the guts of the file system carefully to fully understand the various instructions I've found here. Is there a way to safely install nvflash and ADB and explore more, or do I need to have an already rooted ROM installed on the GTab.
4. Some people recommend updated to newer or tweaked kernels. I've found the kernels, but haven't found any good step by steps on how to install them. Any links you can point to?
As an aside, I think roebeet's idea of a good wiki for this forum is a good one. The main XDA wiki is about useless. I would expect to see beginners guides to nvflash, ADB, CWM, etc.
Thanks for your help.
Jon
Suggestion. If you are going to install a ROM, pull the detailed instructions from one of the reputable Devs here, paste it into a word processor and add a check box before each step ( can use bullet tool) Then make sure you go thru one step at a time and check the box just in case you get interrupted. If you are unclear on a step ( ie clear cache) research it before you do anything.
thanks for your replies guys, it is definitely good to know that even if i do it perfectly it might still not work the 1st time. ill just nvflash it and try again. this is a really informative forum.
I think a centralized FAQ and / or Wiki is needed, for all the concerns you stated.
"How do I setup adb? What is it used for?"
"What is nvflash? How do I backup all my partitions?"
"What's the difference between clockworkmod and standard recovery? What are the pros and cons of both?"
"What are the difference ROMs available and what are their differences?"
"What is a customized kernel and why would I use it?"
"I have an error <fill in the blank> -- what do I do?"
etc etc. With potentially hundreds of Woot users about to jump into XDA, I think this would be a fantastic thing to have. Heck, it would a good thing to have for ALL of us, myself included.
It's NOT an easy task, however. I would argue that it's a very arduous task and something that would need to be ongoing. But I think it would ease some of the repeat questions here, and give new users a good guide to understand some of the basics.
lamchocho,
Wrong! The wooters are here!
And as the days go by there's going to be more.
Gonna be interesting.
Rev
jonalowe said:
I've been lurking on the gTab forums here for the last several days, and have been trying to absorb all of the info I can. I tend to research everything in depth before I plunge into anything. While much information is here, it is fragmented, and what is easy to follow for a developer is not as easy to follow for others. roebeet, you do the best of any I've seen, and I appreciate it. I've done a lot of searches which have helped some. I'm not new to Android (or XDA) as I have a stock Droid Incredible, but I am new to mods to Androids. I have also used Linux in the past, and modded kernels for newer drivers using cookbook approaches, so little scares me if I have enough information. I've sort of figured out how to install and use nvflash, ADB, and CWM using the various guides, but I'm missing some fundamental knowledge on WHEN and WHY I should really be prepared to use them. I've also tried to do some reading on Nandroid, but have found little pertinent to the gTab. So here goes:
1. What is the primary use of each of the following tools, nvflash, ADB, and CWM? When should I expect to have to use each of them? Are there gTab specific guides to their uses and the options for each outside of ROM installation guides, etc? Specific examples of when I should use each, and even more important, when NOT to use them, would be helpful. I've read all of the ROM, nvflash and ADB installation guides, and the various FAQs, and I understand HOW to install each of, just want to understand the best practices for each.
2. After reading a lot, it appears that having a complete backup of my particular ROM would be a good idea since partitions seem to differ even on stock gTabs. I've read posts here that refer to Titanium, and the use of ADB and CWM to do backups, and others that refer obliquely to Nandroid. What is the use of each of the above to do backups? It appears that Nandroid is a piece of CWM, but I may be mistaken. And if I install TnTlite using roebeet's guide, I'm not supposed to use CWM anyway. So how do I do a backup?
3. I plan to use my gTab as I get it, allowing it to do OTA updates only, for a few days, playing with the TNT and normal Android interfaces. I understand that a major OTA may be imminent anyway, possibly based on the leaked 3991 ROM, so my current plan is to wait for it, at least for a week or two. I plan to explore the guts of the file system carefully to fully understand the various instructions I've found here. Is there a way to safely install nvflash and ADB and explore more, or do I need to have an already rooted ROM installed on the GTab.
4. Some people recommend updated to newer or tweaked kernels. I've found the kernels, but haven't found any good step by steps on how to install them. Any links you can point to?
As an aside, I think roebeet's idea of a good wiki for this forum is a good one. The main XDA wiki is about useless. I would expect to see beginners guides to nvflash, ADB, CWM, etc.
Thanks for your help.
Jon
Click to expand...
Click to collapse
I'm quoting Jon's post in its entirety because he both perfectly articulates a number of my questions as well as captures my sense that after days worth of information mining on this site, I'm semi-well-informed enough to do the kind of damage that will surely add to the confusion you all seem to realize is imminent here.
I may be able to help with question 4. Buried in Clemsyn's kernel thread (52 pp!) ...
http://forum.xda-developers.com/showthread.php?t=895825
...is this:
INSTALLATION INSTRUCTIONS:
1. ROOT, Flash CWM Recovery (if you haven't done this yet)
2. Create a FULL nandroid backup (optional since its just a kernel)
3. Download a kernel of choice
4. Put the kernel on root of sd
5. Boot into Clockwork MOD recovery (either from ROM Manager or manually- hold volume up and down at same time and press power button, then select "apply sdcard: update.zip"
6. In recovery select "Install zip from sd card"
7. Select "Choose zip from sd card"
8. Navigate to the kernel file and select it
9. Let it install, it will take a few minutes...screen will go weird (black with big blue letters) then take you back to recovery.
10. Reboot phone
Click to expand...
Click to collapse
goodintentions said:
Just last week, I went to a woman's house to help her with computer problems. She made it sound like life and death on the phone. The only reason I tolerate her is because she might be my in law one day. Anyway, it turned out that the problem was she thought the monitor was the computer. We have explained to her over and over that it's only the monitor and that the box sitting below is the computer. Seems silly to us, but there it is.
Click to expand...
Click to collapse
Just a fair warning, they (the in-laws) never change.
A little note as to why we'll probably start seeing a lot of uninformed people here is because Viewsonic actually has a link to XDA on the "Favorite gTablet Apps and Resources" page of their site, which is accessible from the main G Tablet home page
It's in the developer resources section, but as everyone already knows that doesn't stop some people.

One Click Root App

Any chance of a One Click Root App being developed to eliminate the multiple steps of rooting our Thunderbolts currently? WOuld make like that much more easier for the ones not too comfortable in the current process.
mrwebb said:
Any chance of a One Click Root App being developed to eliminate the multiple steps of rooting our Thunderbolts currently? WOuld make like that much more easier for the ones not too comfortable in the current process.
Click to expand...
Click to collapse
not to flame but really if you are messing around with root/recovery/roms/kernels/etc being able to execute a few commands in a terminal should be considered the bare minimum of competency
A) search is your friend
B) there is a windows program available, I think its in the stickys.
Edit: yep. It's in the stickys. Look up a few threads.
Sent from my ADR6400L using Tapatalk
nitsuj17 said:
not to flame but really if you are messing around with root/recovery/roms/kernels/etc being able to execute a few commands in a terminal should be considered the bare minimum of competency
Click to expand...
Click to collapse
^^^ +1 Very true..and although its almost impossible to brick your phone nowadays you definitely need to know how to use sum type of commands just in case you do happen to mess you phone up...not saying you will BUT theres always that chance...
It's so easy. If you follow all of the steps properly literally NOTHING can go wrong. It's kind of frustrating to see all this posts pop up when smart people have given you step by step guides for root.
If you don't understand enough to copy and paste commands into command line, the last thing you need to worry about is root.
It's not the first time I've used cmd but it is the first time I used ADB and honestly, it was simple. There is a step by step tutorial, what else could you possibly want?
i think that the biggest problem for most people is the fact that setting up sdk and getting the nerve to take the leap to adb commands takes alot of know how that a lot of people on here take for granted. At one point in time we all were f'n n00bs.
I just get extremely tired of seeing people being asshats about helping others. Hell I am a noob just getting started to.
But on the other hand you can't help stoopid, and I agree most problems can be resolved with a few solid moments of reading and brain work.
.o2ยข
no idea why this is posted in development.
If you can't run a few shell commands, then are you ready to root your phone? If something were to miraculously go wrong, you NEED to be familiar with your shell to recover.
Don't root until you know about how to flash partitions on a device. It's all well and good to use a one-click batch script, but come on... Rooting is a risky process. What if the power to your PC were to cut out while flashing? What if Windows were to crash?
Learn to use commands yourself, rather than using a one-click button... You learn nothing by pressing buttons. You learn by reading commands, working out what they do, and doing them yourself
Moved to general btw
dude really just do it the old fashion way. ive rooted a G1, N1 and now a TB. its so simple and easy. literally. took me less than 30 minutes to do the whole thing. all i did was a lot of copy and pasting into the terminal. i could have gotten my 7 year old nephew to do this for me
As I said be 4, its just the terminology that scares people. I am a newbie but didn't take long to get my phone rooted. Words like "push" this file vs copy & paste. Or "terminal" vs command window. I am glad I did not use any one click solutions I would be in even more darkness.
Sent From Rooted Stock Rom Thunderbolt
The method of root using ADB is by far the most reliable way of rooting the thunderbolt. Unfortunately a "one click" root solution is bad in my opinion because you need to know whats actually happening when you are rooting your phone. If you need assistance send me a PM and I can guide you through the process of getting root on your t-bolt. I already helped one person do it and now he understands better how to use ADB and what needs to happen to root your phone. ADB is useful in so many different ways when you have an android phone its definitely worth figuring it out. Just my $.02

Auto root.

http://forum.androidcentral.com/thunderbolt-rooting-roms-hacks/77617-auto-root-unroot-windows.html
just passing it along. i know some are afraid to use adb i myself would recommend using it to know the basic of adb but if not well here it is. GL
i do know its a heated debate with auto and manual etc. don't hate the messenger.
I love auto-rooters for myself. I've done 3 different phones via ADB because I wasn't going to wait, but if I lose root for whatever reason, an auto rooter sure is nice.
I think everybody should root via ADB before they ever root with an auto rooter, though.
Sent from my ADR6400L using XDA App
Nice find, thank you.
That soft bricked me so I did it manually
Sent from my ADR6400L using XDA Premium App
And to think I just did the manual root yesterday.. D'oh! Well, good to learn some of the stuff I did, I guess. Thanks OP for passing it along.
Anyone know if the 'unroot' process will still unroot if you rooted it the manual way?
Thanks will root my phone tomorrow using this
Sent from my ADR6400L using XDA App
EgoDogg said:
And to think I just did the manual root yesterday.. D'oh! Well, good to learn some of the stuff I did, I guess. Thanks OP for passing it along.
Anyone know if the 'unroot' process will still unroot if you rooted it the manual way?
Click to expand...
Click to collapse
as far as I know, just loading the stock PG05.img (or whatever the name is) in bootloader will return you to stock
and, auto-root is great, but will lead to so many more of the "I bricked my phone" type threads from people that don't know what they are doing...
papi92 said:
That soft bricked me so I did it manually
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Soft bricked your phone? please elaborate on this
I (personally) had no problems. Did you miss a step?
Jaxidian said:
I think everybody should root via ADB before they ever root with an auto rooter
Click to expand...
Click to collapse
+1
anyone interested in rooting should know how to access their phone via adb. if the auto root process goes bad, adb is the only tool available
Rooting manually via ADB or rooting via auto root?
That's a discussion folks should flesh out and really chew on. It's not been discussed enough here in the past and is a highly neglected topic that deserves many original posts such as the ones above this one. Let's get this debate going and see if we can tread some new ground.
Sucks
No matter what method of root I try to use it always says device error, so its not connecting, any suggestions?
Old MuckenMire said:
Rooting manually via ADB or rooting via auto root?
That's a discussion folks should flesh out and really chew on. It's not been discussed enough here in the past and is a highly neglected topic that deserves many original posts such as the ones above this one. Let's get this debate going and see if we can tread some new ground.
Click to expand...
Click to collapse
I'm still in the "to root or not to root" discussion..
FP5241 said:
I'm still in the "to root or not to root" discussion..
Click to expand...
Click to collapse
I hear you. I rooted and flashed the hell out of my Nexus One but have held off with the TB. Rooting and flashing Sense ROMs on my N1 is what made me want the TB in the first place.
That said, I would like to use cache-mate and ad-free. This ROM is also tempting me:
http://forum.xda-developers.com/showthread.php?t=1013577
I have to hold off tho. They are getting ready to flip the 4G switch in my area soon an I want to be stock when that happens because when I root I want to know how my device is supposed to behave when stock. That way I'll know if an issue I am having is a TB/Verizon issue or a flashed ROM/Kernel/Radio/root issue.
Rooting on the N1 was a no-brainer given the lack of app space and the urgent need for A2SD. Given the ability to move some apps to SD now, plus the TB's extra app storage space, the need for more storage just isn't there for me with the TB. And believe it or not, for me personally, flashing ROMs and kernels got old in and of itself. Every ROM is different, but I can never find the perfect one and always end up wishing I could cherry pick features from a variety of ROMs. I felt like a damn nomad going from one ROM to the next.
Old MuckenMire said:
Rooting manually via ADB or rooting via auto root?
That's a discussion folks should flesh out and really chew on. It's not been discussed enough here in the past and is a highly neglected topic that deserves many original posts such as the ones above this one. Let's get this debate going and see if we can tread some new ground.
Click to expand...
Click to collapse
There is nothing to discuss.
If you are doing any type of hack you are doing so at your own risk,assuming all responsibility to anything that may happen to your phone, and you should take it upon yourself to learn, at the very least, the basics of adb and its command functions.
I am attempting to make the process as painless as possible, no where in my thread do i call it easy or simply . I call it auto root because its Automated.
I am not saying im not noob friendly because if you know me you know thats not true i spend many many hours helping people, im just saying that if you are attempting a hack that you should know what you are getting yourself into.
vwlove09 said:
No matter what method of root I try to use it always says device error, so its not connecting, any suggestions?
Click to expand...
Click to collapse
This is a connection problem, make sure HTC sync is installed. Make sure you are in debugging mode and it is set to stay awake, make sure you are in USB setting Charge only. Use the USB ports in the back of the computer
id none of that works, try a different,USB port, cable or different computer.
DroidXcon said:
There is nothing to discuss.
If you are doing any type of hack you are doing so at your own risk,assuming all responsibility to anything that may happen to your phone, and you should take it upon yourself to learn, at the very least, the basics of adb and its command functions.
Click to expand...
Click to collapse
It was a joke man. It's been discussed here ad nauseum...plus, don't you think it's a little ironic that you create an auto root app where the user DOES NOT NEED TO LEARN OR USE one single manual ADB command, while at the same time preaching that users should learn ADB?
the only reason you say this stuff is to pay lip service to your developer clique about ADB and noobs, then you turn right around and give noobs a manual ADB free root app.
don't get me wrong, I appreciate it as much as anyone, but the irony is a little thick here.
Old MuckenMire said:
It was a joke man. It's been discussed here ad nauseum...plus, don't you think it's a little ironic that you create an auto root app where the user DOES NOT NEED TO LEARN OR USE one single manual ADB command, while at the same time preaching that users should learn ADB?
the only reason you say this stuff is to pay lip service to your developer clique about ADB and noobs, then you turn right around and give noobs a manual ADB free root app.
don't get me wrong, I appreciate it as much as anyone, but the irony is a little thick here.
Click to expand...
Click to collapse
this is automated for anyone, where does it say in my thread, this is for noobs?
so because something is posted or because its easy to use its automatically hypcritical? . this is for anyone. i know that if i return to stock that i am not going to want to have to type out every command just to root again.
so if what you are saying it true then no one should post anything that makes the process easy for other people.
Did you install the drivers?
Sent from my THUNDERBOLT
DroidXcon said:
this is automated for anyone, where does it say in my thread, this is for noobs?
so because something is posted or because its easy to use its automatically . this is for anyone. i know that if i return to stock that i am not going to want to have to type out every command just to root again.
so if what you are saying it true then no one should post anything that makes the process easy for other people.
Click to expand...
Click to collapse
Hey man like I said I appreciate it...but some developers on this forum drone on and on about how easy manual ADB is and that there is no need for automated root apps. If you already know ADB there is really no point in the automated app except to save, what, typing??
The automated app still takes almost as long...it just saves typing...and the risk of a mistake. That has been my point all along.
AGAIN, I highly appreciate your app and work...I just wish devs would stop harping on the need to lean ADB when it's not needed thanks to apps like yours. For whatever reason there is this clique of devs who think if you don't know ADB you don't "deserve" root access. It's lame.
But let's be real here: 90% of the users that will use your app are rooting noobs. The experienced users did it manually on day one.
Old MuckenMire said:
Hey man like I said I appreciate it...but some developers on this forum drone on and on about how easy manual ADB is and that there is no need for automated root apps. If you already know ADB there is really no point in the automated app except to save, what, typing??
The automated app still takes almost as long...it just saves typing...and the risk of a mistake. That has been my point all along.
AGAIN, I highly appreciate your app and work...I just wish devs would stop harping on the need to lean ADB when it's not needed thanks to apps like yours. For whatever reason there is this clique of devs who think if you don't know ADB you don't "deserve" root access. It's lame.
But let's be real here: 90% of the users that will use your app are rooting noobs. The experienced users did it manually on day one.
Click to expand...
Click to collapse
im in no clique of devs i dont even know if anyone likes me lol. im not saying you should be an expert. but you should know how to use adb because at some point a problem may happen and automation doesnt let you trouble shoot very well. Im not hard core either way adb or no adb. but with any hack sometimes the only way to save yourself from a phone becoming useless is through adb..
thanks for the appreciation,,,,oh and not for nothing, i would rather watch a show then have to be putting in line after line of commands , then on commercial i can just flash the ruu

Bricked one phone.. Got replacement. Need Help

Okay so I had a G2x and tried rooting it and I think i did something wrong. With all these instructions ramble on about one thing and another hard for me to really understand all the correct steps.
So can I please have someone give me a hand with this? As in a step by step process of everything? This is my second G2X brand new from T-Mobile has the Gingerbread 2.3.3. So if anyone can actually tell me step by step and what files I am going to need so I don't brick this one because 300USD is getting expensive.
u payed for ur replacement? lol
use the one click flash nvidia tool, to flash the clockworkmod, you dont evne have to root it
http://www.youtube.com/watch?v=kG08Uc8pQT0
yeah I had to pay for a second one. GRRR T-Mo actually checks their phones with sprint if I bricked or something just dip it in water and send it in. They would never check to see if you rooted it. So anyways do I install Clockwork or only do the steps in the video with the nv flasher?
And whats the best rom? I really like the looks of MIUI sorta looks like my wifes iPhone.
i think you screwed yourself on this one... this phone is like virtually unbrickable, nvflash should be able to bring you out of any soft bricks you might run into and ive run into a fair share of them and never had a problem...
i would recommend you sift though the development section and read all of the tutorials and have a very good understanding of what you are doing instead of having someone spoonfeed you everything when you really dont know what you are doing... (im a high school math teacher and cannot stand it when students are just spoonfed information because in the end they really dont understand what they are doing)
start here though http://forum.xda-developers.com/showthread.php?t=1056847
Yeah, what he said. maybe you shouldn't be messing with your phone if you don't understand the implications.
JHaste said:
(im a high school math teacher and cannot stand it when students are just spoonfed information because in the end they really dont understand what they are doing)
Click to expand...
Click to collapse
+1
Best thing I've ever read. It helps shine a light on why so many people almost daily are asking for help on how to do something when this forum is riddled with tutorials. I personally stopped helping months ago with any questions on how to root or flash or just anything that there are tutorials for. It just gets crazy redundant.
Sent from my LG-P999 using XDA App
Beekersguy said:
Yeah, what he said. maybe you shouldn't be messing with your phone if you don't understand the implications.
Click to expand...
Click to collapse
JHaste said:
(im a high school math teacher and cannot stand it when students are just spoonfed information because in the end they really dont understand what they are doing)
Click to expand...
Click to collapse
guitarist5122 said:
+1
Best thing I've ever read. It helps shine a light on why so many people almost daily are asking for help on how to do something when this forum is riddled with tutorials. I personally stopped helping months ago with any questions on how to root or flash or just anything that there are tutorials for. It just gets crazy redundant.
Sent from my LG-P999 using XDA App
Click to expand...
Click to collapse
Then why even post in here? Don't be a ****. Even more frustrating than people who can't use a search feature are people too uptight and high-strung to help someone. Yeah, maybe the OP could have found the answer himself. But he's obviously been following a tutorial (likely in this very forum) that's not working for him (hence his replacement phone). The guy just needs two seconds of help from someone. In the amount of time it took me to copy/paste the following links, I could have torn him a new one thirty times over. But I'm not a ****. So, if you absolutely HAVE to post here, at least make it constructive. Incessant *****ing does no good for anyone.
To the OP:
Firstly, you'll need to flash CWM. This is super simple, given you're on a PC. If you're on Mac, things will get tricky (i.e. virtual Linux environment, headaches, etc).
Next, you can find an easy to follow rooting method here. It even has an unroot .zip option given you have to send your phone in again (will save you another $300 ).
And of course, you can PM me if you need any help. If these are the steps you have already followed, here's a YouTube video with some visuals. When I'm stuck on something, that usually helps me a lot.
http://www.youtube.com/watch?v=7CEjInNY5Y0
Good luck!
Uhhhh... i really dont understand how i was being a ****... I simply stated that he should have a holistic understanding of what hes doing before he starts tinkering because the figure it out as you go method can lead to a 300 dollar paper weight. Not to mention I pointed him in the right direction to start....
All I did was give a bit of advice that I felt was in his best interest and then sent him on his way...
If you think what I originally posted was flaming then you clearly have never seen me tear somebody a new one lol
Dont worry man
sent from my Sensation XD
ericalanMICHAEL said:
Then why even post in here? Don't be a ****. Even more frustrating than people who can't use a search feature are people too uptight and high-strung to help someone.
Click to expand...
Click to collapse
Cuz I thought what he said was funny and agreed. I didnt realize the average joe had the right to question peoples right to agree and post. Don't get self-righteous on us.
Sent from my LG-P999 using XDA App
ericalanMICHAEL said:
Then why even post in here? Don't be a ****. Even more frustrating than people who can't use a search feature are people too uptight and high-strung to help someone. Yeah, maybe the OP could have found the answer himself. But he's obviously been following a tutorial (likely in this very forum) that's not working for him (hence his replacement phone). The guy just needs two seconds of help from someone. In the amount of time it took me to copy/paste the following links, I could have torn him a new one thirty times over. But I'm not a ****. So, if you absolutely HAVE to post here, at least make it constructive. Incessant *****ing does no good for anyone.
To the OP:
Firstly, you'll need to flash CWM. This is super simple, given you're on a PC. If you're on Mac, things will get tricky (i.e. virtual Linux environment, headaches, etc).
Next, you can find an easy to follow rooting method here. It even has an unroot .zip option given you have to send your phone in again (will save you another $300 ).
And of course, you can PM me if you need any help. If these are the steps you have already followed, here's a YouTube video with some visuals. When I'm stuck on something, that usually helps me a lot.
http://www.youtube.com/watch?v=7CEjInNY5Y0
Good luck!
Click to expand...
Click to collapse
They are being difficult. What they realize is that the OP has already stated that he's bricked one device because he cannot follow directions. He obviously does not know what he's doing, and has problems following instructions because, as he put it..they go on and on... In the end even if he successfully roots his phone, he may wind up causing himself problems by having access to system files because it's obvious he doesn't really know what he's doing. Everyone shouldn't root. If you cannot follow the simple instructions to root without "bricking" a device, and you cannot follow simple instructions to bring the device back to an operational state, then perhaps rooting is not for you (OP). It just sounds like he is going to cause himself even more problems.
mysterioustko said:
They are being difficult. What they realize is that the OP has already stated that he's bricked one device because he cannot follow directions. He obviously does not know what he's doing, and has problems following instructions because, as he put it..they go on and on... In the end even if he successfully roots his phone, he may wind up causing himself problems by having access to system files because it's obvious he doesn't really know what he's doing. Everyone shouldn't root. If you cannot follow the simple instructions to root without "bricking" a device, and you cannot follow simple instructions to bring the device back to an operational state, then perhaps rooting is not for you (OP). It just sounds like he is going to cause himself even more problems.
Click to expand...
Click to collapse
^^this... root access to phones is not a hand out, it has to be earned, and you earn it by educating yourself about your device and its capabilities and by following simple instructions...
sabwjawdjw said:
yeah I had to pay for a second one. GRRR T-Mo actually checks their phones with sprint if I bricked or something just dip it in water and send it in. They would never check to see if you rooted it. So anyways do I install Clockwork or only do the steps in the video with the nv flasher?
And whats the best rom? I really like the looks of MIUI sorta looks like my wifes iPhone.
Click to expand...
Click to collapse
I can't believe no one has said this yet.
Most phones have water sensors, so dipping it in water would just void the warranty. Sorry if you were joking. But as many have said, it's pretty easy to flash the phone back to normal so the TMobile doesn't know it's been hacked. Did you ask here first?
I am thankful for all the responses. Sorry if I caused grief and headache to anyone. I was finally able to get my phone rooted giving the information that someone provided to me on here. I sent him a PM to personally thank him.
By all means I should probably be *****ed at if I don't follow instructions very well. I have always considered myself a visual learner. If I don't have hands on and able to see it done, it really complicates things for me. I guess you can call it a disability.
Anyways I have come from a long line to HTC which I can say is way different in rooting then these phones. I root them to begin with to get rid of all the stupid software T-Mobile places in my phone and to normally switch to CM7 which I have found out is giving me problems which I am currently trying to figure out.
So please negative comments and put downs are always accepted it comes with the questions. But I don't want to sound like an ass or anything when I say this because I mean it in the upmost respect to everyone, but isn't this a forum? A community forum?
Someone once had to show you, all I did was ask for the same help. And this whole GSM network ways of doing things is different from my typical Sprint CDMA network that I am used to. Everything was pretty much the same when it came to that.
Again please I AM VERY SORRY truly if I caused any problems. Please don't be upset at me. Thanks.
I don't think anyone is upset with you. We're all here to contribute and help. Have fun with your rooted G2X
sabwjawdjw said:
Okay so I had a G2x and tried rooting it and I think i did something wrong. With all these instructions ramble on about one thing and another hard for me to really understand all the correct steps.
So can I please have someone give me a hand with this? As in a step by step process of everything? This is my second G2X brand new from T-Mobile has the Gingerbread 2.3.3. So if anyone can actually tell me step by step and what files I am going to need so I don't brick this one because 300USD is getting expensive.
Click to expand...
Click to collapse
Don't feel bad. I bricked mine upgrading to GB, and I'm still not sure what went wrong. I got it fixed for free by sending it into LG.
sabwjawdjw said:
I am thankful for all the responses. Sorry if I caused grief and headache to anyone. I was finally able to get my phone rooted giving the information that someone provided to me on here. I sent him a PM to personally thank him.
By all means I should probably be *****ed at if I don't follow instructions very well. I have always considered myself a visual learner. If I don't have hands on and able to see it done, it really complicates things for me. I guess you can call it a disability.
Anyways I have come from a long line to HTC which I can say is way different in rooting then these phones. I root them to begin with to get rid of all the stupid software T-Mobile places in my phone and to normally switch to CM7 which I have found out is giving me problems which I am currently trying to figure out.
So please negative comments and put downs are always accepted it comes with the questions. But I don't want to sound like an ass or anything when I say this because I mean it in the upmost respect to everyone, but isn't this a forum? A community forum?
Someone once had to show you, all I did was ask for the same help. And this whole GSM network ways of doing things is different from my typical Sprint CDMA network that I am used to. Everything was pretty much the same when it came to that.
Again please I AM VERY SORRY truly if I caused any problems. Please don't be upset at me. Thanks.
Click to expand...
Click to collapse
Do not sweat the whiners. Here is the way I look at it... It is a forum for developers. I can not develop crap, so I try to do my part by being helpful when I can. Everyone here was brand new at one point. Make sure you do your part by reading as much as you can. If you still have questions/issues, send me a PM.
Why does every noob question get followed up with a bunch bullshizz. We were all noobs at one point, I remember when my Huawei ascend scared me. Nothing is worse than bricking your phone and being upset than a bunch of know it all asses being pricks. Is the g2x forum the only one full of d-ckheads? I've never heard so much whining and holier than thou bs. I'm surprised we have any devs, ungrateful bunch of *****es. Wah, nvidia never, wah, everyone else has ics, wah, that noob asked a question, wah, I suck. I love my g2x, it's a typical musclecar, way over powered and finicky as hell. The g2x is not a beginners device, this is for big boys and girls. I wonder what the whiners would do if they owned a ferrari? Newsflash, they break down, a lot! I remember when xda was where you went for help and support, now I come here to be entertained by the ignorance of the know it alls. Go ahead, blast me, I'm a writer for an Android website and I'll make it painful. OK, then, how bout all these new roms and updates? It's like the g2x is reborn. Hey, wait a minute, I thought the g2x was a useless, unsupported piece of ka ka? Frickin morons!
Sent from my LG-P999 using xda premium
Well first I am glad you were able to fix the phone however I understand knowledgeable people get frustrated because this phone is simple to root. With a phone that has been out this long there is no reason anyone can not find out what to do on there own.
There are so many YouTube videos and forums like this. You are not the second person to too your phone or to brick it so why create a new post looking for help when you can simply Google it. I know your lazy and expect someone else to do your work for you.
http://www.google.com/search?hl=en&...9l19l0l3l3l0l1535l5020l1.0.3.0.2.2.1.0.1l10l0
See plenty of info on the subject I am sure one of these other people have been helped.
This is why devs are tired of these questions they have been answered over and over. You may find this mean to say but you most likely found this forum by using Google so use it to fix your phone. Stop wasting peoples time by being lazy and use your head.
Sent from my LG-P999 using xda premium
The problem is this. Ppl dont know how to research their issue. Also ppl in our generation cant seem to follow directions worth ****. I was the same way. I learned on my g1. Rooted it successful and then bricked my friends. Over the years ive learned alot about computers/phone/cdma flashing. Playing with the big boys. You develop problem solving skills that you can apply outside of this. It truly makes you smarter. So yea. Maybe we are know it all asses.
sent from an HTC sensation on CM7 alpha #10

Categories

Resources