Related
Everything I know about Android, I learned from XDA.
I run a little Android blog and a lot of non-tech people have been asking for help with getting cupcake installed. I really struggled with the idea of posting a guide since so many have been done before. With all the recent cupcake builds, I thought I would attempt a guide geared towards people who have never rooted their phones and want cupcake.
Anyways, I just posted the first draft and I need help with suggestions and fact checking. I think most of it is factual, but I prob made mistakes.
If you got 5 minutes and want to help out the community, give it a quick read.
I tried to take the easy route when rooting. When I first hacked my phone, we didnt have a lot of the tools and scripts that are out now. If any step could be simplified, please let me know. Thanks.
http://www.androidandme.com/2009/05...r-rooting-your-android-g1-to-install-cupcake/
nice blog..
Nice 50 screenshots of Haykuro. Can't wait to see his next release.
Easiest way for noobs to root their phone to the latest 1.1 ROM before flashing the 1.5 ROM is to use the root app. It can be found here, along with step by step instructions.
http://allshadow.com/forum/viewtopic.php?f=9&t=5229
When I was a noob, I first rooted my phone using that app, but now I remember all the commands by heart lol.
edit: just looked at your blog, you already have it there.
Any other takers? I just wanted to make sure this was as friendly as possible before I offered it to people. Thanks.
You may want to check out this guys method of the root procedure. It's similar to yours, but it doesn't use the .apk file. I did it his way, and I pushed everything from my laptop to the phone, so rooting took me about 10 minutes or so.
http://several.amplify.com/2009/05/02/video-tutorial-g1-jailbreak-root-and-cupcake/
I would make a fork for those who don't have wifi access, or want to do the rooting a little quicker.
very organized your blog is though.
Thanks for the link. That looks like a good resource, but I think it is too many commands to type for some people. I'll watch all the videos and see what I think.
Good job!! Looks likes a nice guide. One thing I might add is the recovery instructions since the current JF1.5 ROM
HTML:
does not include it.
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.
I just read a post by roebeet (well known dev who put together the TNT Lite ROMS) and something he said made enough sense to me that I thing everyone needs to hear it.
If you are going to flash and try everything you find on this site -- you run a real risk have having problems. Everything you flash adds, changes and deletes stuff from your tablet and some of that gets carried over from ROM to ROM to program.
Just because you partition/erase/delete/overwrite does not mean your tablet content is destroyed. There are a bunch of partitions on your tablet (12?) and some are preserved and some are modified depending on what you do.
So am I saying "Don't mod you G-Tablet" or "Don't try out new stuff." NO.
1. Make real sure you know what you are doing. Too many people just rush ahead and wind up with real problems.
2. Read directions and read all the posts about others who have done the same thing you want to do.
3. When you are making changes, do them one at a time and make sure it's working right before moving on. When you change a bunch of stuff it's hard to tell what the problem/problems is and where it came from.
4. IMHO, too many people see the modding as a game and then they get mad at the dev or people who are trying to help them -- when all the time it was their own fault!
I think it would even be a good idea if someone knowledgeable could help us see if we could put together a flash which would actually delete/erase what's on a
troubled tab so it could be rebuilt. Sorry, but I don't talk enough Android yet to do that.
Think about it.
Rev
butchconner said:
I think it would even be a good idea if someone knowledgeable could help us see if we could put together a flash which would actually delete/erase what's on a
troubled tab so it could be rebuilt.
Rev
Click to expand...
Click to collapse
I would recommend running a format zip before any reloading on a Gtab whether a new rom or the stock. Just like all the computers I work on for people the first thing I do is run a program to erase the hard drive to make sure nothing old can interfere with a new reload of the operating system
Calkulin has this format zip from his rom thread or you could use the other one from here
http://forum.xda-developers.com/showthread.php?t=974422
Start fresh don't just overwrite!
ale
Calkulin's Format all is awesome
Exactly. Calkulin's format all is a life saver. It is much cleaner and faster way than to do three or four steps to clean stuff out (Invariably one forgets one of the steps which causes all the problems).
I have used this file to solve many problems going from rom to rom... Good stuff.
[Q] Should I step back and use the format zip?
notsob2002 said:
I would recommend running a format zip before any reloading on a Gtab whether a new rom or the stock. Just like all the computers I work on for people the first thing I do is run a program to erase the hard drive to make sure nothing old can interfere with a new reload of the operating system
Calkulin has this format zip from his rom thread or you could use the other one from here
http://forum.xda-developers.com/showthread.php?t=974422
Start fresh don't just overwrite!
ale
Click to expand...
Click to collapse
Two days ago I reset my gtab to stock. I have the 3389 zip saved and installed that using clockwork. I also used clockwork and did the data wipe/factory reset right before actually applying the rom.
Loading the stock VS rom removes clockwork and after reboot it pulled the OTA update and currently running the 3588 version.
I did this in anticipation of the upcoming VS update. The tablet seems to be running fine and as I said it's able to find and apply OTA updates.
Would you still recommend running this format zip, and then re-apply the 3389 I have saved?
Thanks,
Neudle
** Would like to point out there is a comment in the referenced post concerning using this format zip..."So this is a "detox" program for our gtablet that we can choose to run prior to NVflash process. And this process should not be done unless absolutely necessary, right?" "Yes, exactly..."
Neudle,
If you were at 3389 and did 3588 via OTA, I would try my recovery. If it does not
come up with your old CWM, then it should be stock recovery and you should be
good to go.
If needed, you always have the option of manually loading recovery and the 3588 update.zip into /sdcard and flashing stock again.
Rev
butchconner said:
Neudle,
If you were at 3389 and did 3588 via OTA, I would try my recovery. If it does not
come up with your old CWM, then it should be stock recovery and you should be
good to go.
If needed, you always have the option of manually loading recovery and the 3588 update.zip into /sdcard and flashing stock again.
Rev
Click to expand...
Click to collapse
Thank you for the response.
Actually I think my tablet is fine. Unless I'm really confused (which is certainly possible) 3389 was the update from late december/early january. The 3588 is the update that came up in like febuary. Isn't 3588 the most recent?
This isn't the first time I've reloaded the stock rom and it seems it always over-writes/removes the clockworkmod.
I was simply more curious if you folks do feel it's always best to use the format.zip when swapping roms?
As I said, I'm simply prepping and anticipating the upcoming update from Viewsonic and not worried about clockworkmod for the time being. From what I've seen the update includes a recovery that looks similar.
Thanks again,
Neudle
I think the OP makes an excellent point for all us weekend tinkerers. The G-Tab is my first experience with an android device and although I have experience with rooting and flashing roms and kernals on another platform (WEBOS on my Palm pre), I have spent my first few weeks with this device just reading as much as I can on these forums before trying anything myself.
I was fortunate enough to get a great deal on this tab second hand from somebody who had already flashed it with Vegantab ( I believe 5.1.1). As it stands, it pretty much does everything I need it to do and there is no reason to break what alreday works...... except that I am a weekend tinkerer...... and I am thinking that I would like to try Calkulin's rom.
At the moment, I am not sure that it represent's an upgrade over what I have and I may wait for something gingerbread or honeycomb based that people report to have a signifigant benefit over Vegan 5.1.1...although I am sure I will convince myself differently at some point.
I know that I have CWM installed and that I can use this to clear up caches and personal info before flashing another ROM. Does Calkulin's format erase this? If so, does it need to be re-installed before putting on a new ROM? I am reading posts about people flashing back to stock and receiving updates before flashing a new rom. This completely confuses me as I don't understand the benefit unless, as the OP seems to indicate, there are bits that are left over from the old ROM when a new one is flashed. Is this desirable?
Sorry if I am asking so many questions in this thread. I know that there are bits and pieces of info scattered among many threads but some of it seems contradictory and some I am sure is outdated.
Can someone either outline or point me in the right direction to a step by step that outlines the most current and least likely way to brick upgrade from Vegan to Calkulin's ROM?
Thanks
butchconner said:
2. Read directions and read all the posts about others who have done the same thing you want to do.
Click to expand...
Click to collapse
Here's my problem. Where is the step by step, this is how you take a GTab you just bought, to ROM "XYZ" the correct way? There are lots of "how to"s scattered all over this forum, but no one sticky at the top that says "Here's a step by step". Right now, I'm reading through everything again, before I try and mod my tablet, and it's a mess. It would be nice is someone+moderator made a nice, straight forward LOCKED thread that is stuck, that explains it all. The FAQ isn't quite the information necessary (in my eyes).
I'm pretty technical (engineer by trade) and if it takes me a bit to figure out how to do something, the general n00b is going to screw something up.
Just my thoughts.
h3llphyre said:
Here's my problem. Where is the step by step, this is how you take a GTab you just bought, to ROM "XYZ" the correct way? There are lots of "how to"s scattered all over this forum, but no one sticky at the top that says "Here's a step by step". Right now, I'm reading through everything again, before I try and mod my tablet, and it's a mess. It would be nice is someone+moderator made a nice, straight forward LOCKED thread that is stuck, that explains it all. The FAQ isn't quite the information necessary (in my eyes).
I'm pretty technical (engineer by trade) and if it takes me a bit to figure out how to do something, the general n00b is going to screw something up.
Just my thoughts.
Click to expand...
Click to collapse
I haven't found that to be the case at all. In fact, I've seen nothing but repetitive reinforcement of proper procedures from every knowledgeable source. If the ROM Creator says use clockworkmod to install then wipe data... well do it. If he/she says use standard recovery... well... This isn't rocket science. I've installed and tested every ROM listed here with no failures by following the included instructions. I can't believe that is an anomaly.
If you want to be truly successful, learn what each of these tools (clockworkmod, nvflash, etc.) does and more importantly what they do not do. When you educate yourself to their proper use you won't be finding yourself using a hammer when you need a screwdriver.
hotfire!,
I think that's one of the points I hoped to make in this thread.
I appreciate the "format" tips -- but I have not used it and none of the folks whose opinion I watch for have put their stamp of approval on it -- so my opinion of it is still
in the making. I will use it only cautiously until I have confidence it is good.
But as you have said, we do have a hodgepodge of stuff here. People try to do
too much too fast -- and others suggest stuff that doesn't need to be done.
For example -- if somethings crashes on my G-Tablet, I go back to a basic CWM/ROM combo that I know is good so I have a solid place to start and then rebuild. Takes a little longer, but I think it save me a lot of anquish.
So like a lot of others, I just help where I can. But I do try to be conservative and consistent making suggestions the will not "snow" the new or offend those who think
they know what they are doing.
And to everyone I suggest the wrong thing, OOOOPs, and apologies. To those who
help me an give others good help -- thank you.
Rev
K J Rad said:
I haven't found that to be the case at all. In fact, I've seen nothing but repetitive reinforcement of proper procedures from every knowledgeable source. If the ROM Creator says use clockworkmod to install then wipe data... well do it. If he/she says use standard recovery... well... This isn't rocket science. I've installed and tested every ROM listed here with no failures by following the included instructions. I can't believe that is an anomaly.
If you want to be truly successful, learn what each of these tools (clockworkmod, nvflash, etc.) does and more importantly what they do not do. When you educate yourself to their proper use you won't be finding yourself using a hammer when you need a screwdriver.
Click to expand...
Click to collapse
But therein lies the problem. There *is* a great thread on installing CWM and then ROMs using that. Step by step, it's fantastic. Installing a new kernel *is* found in some of the threads, but I wish that great thread with the CWM and ROM installation also had Kernel info.
Regardless of if you know how these tools work, it's nice to have a step by step to follow, just to ensure you're doing everything in order. I do it at work when I'm working with a new system (I write it myself) just to make sure I follow the same procedure every time. It helps when problems arise.
I'm just saying, for the n00bs, it would be nice to have a "one size fits all" thread. I was able to successfully install CWM and Vegan without a single problem, as I've been reading this forum for MONTHS, but I'm not a normal person (nor are most of the regulars here).
One thing I try to do, is demystify technology. Make it easy, explain it in simple ways while still being effective as describing what is going on, and then you don't get "stupid questions" later. Essentially, trying to run in the opposite direction that most Linux forums tend to be. Threads buried 2 years back have the info, everyone screams at the n00bs saying "USE THE SEARCH".
Love this forum, the people here are REALLY helpful, but there is room for improvement. That's all I'm saying.
h3llphyre said:
But therein lies the problem. There *is* a great thread on installing CWM and then ROMs using that. Step by step, it's fantastic. Installing a new kernel *is* found in some of the threads, but I wish that great thread with the CWM and ROM installation also had Kernel info.
Regardless of if you know how these tools work, it's nice to have a step by step to follow, just to ensure you're doing everything in order. I do it at work when I'm working with a new system (I write it myself) just to make sure I follow the same procedure every time. It helps when problems arise.
I'm just saying, for the n00bs, it would be nice to have a "one size fits all" thread. I was able to successfully install CWM and Vegan without a single problem, as I've been reading this forum for MONTHS, but I'm not a normal person (nor are most of the regulars here).
One thing I try to do, is demystify technology. Make it easy, explain it in simple ways while still being effective as describing what is going on, and then you don't get "stupid questions" later. Essentially, trying to run in the opposite direction that most Linux forums tend to be. Threads buried 2 years back have the info, everyone screams at the n00bs saying "USE THE SEARCH".
Love this forum, the people here are REALLY helpful, but there is room for improvement. That's all I'm saying.
Click to expand...
Click to collapse
Short answer: Great idea! When will you have it ready? ;-)
Long answer...
I understand what you're saying. What I'm saying is that there isn't a one size fits all answer to this "problem" (certainly not since the addition of TwoTapsX). The step by step instructions for installing ROMs, kernels, other hacks, etc. exist in the threads that contain the product (and most of those are stickied) because they aren't always identical. One "Superpost" meant to encompass all of those instructions would grow to be much too large and include far too many logical branches to be effective when you take into account the individual caveats for each. However, the methods for installing many of the products is similar in most cases even if the tools are not identical. Understanding which tool to use and how it works is the key to a successful experience.
For example are the recent cases of problems with TwoTapsX (formerly TnTLite 5.0.x). The instructions in the thread clearly stated that the users should start from a clean Viewsonic ROM without CWM (very different from other ROMs). It even stated an nvflash might be necessary if you had any problems with the install (also not usually necessary with other ROMs). Still, the overwhelming majority of users that had problems had failed to follow the instructions correctly and were unprepared to do an nvflash. These were generally not people that were new to the process, either. In cases where they were, a simple search for the error message they were getting or the condition they were experiencing turned up an answer within the first two or threes responses and virtually all of them were addressed in the original instruction thread or another recent thread with a similar title.
Another example, I still see threads daily about someone recently installing VEGAnTab 5.11 and all of a sudden their media disappears from their sdcard. This is a well known and very well documented problem with a long used successful work around. It isn't a case where their particular installation went awry, it's a known issue with the ROM. How many of those issues would need to be addressed in the "Superpost" in order to be effective and yet not be cumbersome?
To complicate things further, we now have indications that the next official release may change recovery to be incompatible with previous methods. It's possible we'll see further forking of these processes based on the developers preference of recovery which would reinforce the need to customize instructions for a particular product.
Room for improvement? Sure. I just think education is better than hand holding. I always encouraged my engineers to learn more and develop their own processes because they might actually be better, cheaper, more efficient, than whatever we currently had. I understood that MY answer might not always be the best one and I preferred to empower my associates.
All that being said... I'm all for anything that improves the community and more importantly helps its members. If you feel that it would be helpful then feel free to put something together or team with a few others to produce a document to address the issues you've identified. I'll be more than happy to link people to it if it fills a need for them just as I have to others in previous threads ;-)
Modding
You know normally I just read and lurk around here, but I can't keep my mouth shut any longer.
**WARNING** Not that I expect anyone to notice because apparently half of you can't read or don't comprehend what you do read, but anything past this point is probably not contributing to the conversation in a constructive way and should be considered as me ranting.
I have had my tab since December and have flashed every single Rom found on this forum at one time or another and the problems I see people have just amaze me. It's amazing because 9 out of 10 times it's because they didn't bother to read/comprehend the darn instructions or they are to lazy to search/read/comprehend on how to fix it or start over.
I am by no means a rocket scientist/programmer/developer/modder myself but I can read something 3-4 times first to make sure I comprehend before I go off deliberately voiding the warranty on a $400 device. And if I break it? Guess What?? There are instructions for that to if people would bother to look. Granted the information can be scattered around but if you can't be bothered to search/read then you should probably not be using a android device.
Last thing and I'll shut up. The entitlement I see coming from alot of people really makes my blood boil. You are an early adopter of bleeding edge technology, there are going to be problems and alot of them! If you didn't do research on the tab before you bought it you have no right to complain. The devs are not paid except by an occasional donation. They do this on their own time with their own equipment for the community. THEY DO NOT OWE YOU A THING, AND YOU SHOULD WORSHIP THEM SINCE WE ALL GET TO BENEFIT FROM THEIR HARD WORK!!!
Be Contented....
After tried two ROMs (TnT and NI) and finally sticked to NI, am well contented and satisfied. I think being contented may less your problem...
K J Rad said:
Short answer: Great idea! When will you have it ready? ;-)
<Plus lots of other stuff you said>
Click to expand...
Click to collapse
As you can see from my post count, I'm historically a lurker. I've literally read every single thread in the GTab section since December. The problem for me, mostly came down to once I bought the device (I research stuff to death before I pull the trigger) and was ready to try a new ROM, it was information overload. There *is* a good thread about ROMs and CWM as I said, so I followed that, after reading it 6 times to ensure there were no gotchas.
I want to try out Pershoot's kernel, but I don't feel like I've read the procedure enough times to feel confident I'll be able to do it without having to fix something I broke. So, I'll read it a few dozen times, research the tools used, and finally get to it.
End of the day, I'll probably ask the person who did the ROM thread if they wouldn't mind added text that I've put together for the Kernels (as a supplement to what he did). I do want to give back to the community.
Also, you'll hopefully be seeing some hardware mods coming soon from me, fully documented. My true love is hardware, so I'll leave the ROMs and Kernels to the software guys, and focus on improvements on the physical side of things.
Thanks for keeping the conversation friendly. Always great to hear other people's opinions on matters.
Hardware mods would be VERY cool. Just remember to put something in the thread about how to talk your wife into letting you replace the smoldering mess on the kitchen table so I'll be covered... ;-)
h3llphyre said:
Also, you'll hopefully be seeing some hardware mods coming soon from me, fully documented. My true love is hardware, so I'll leave the ROMs and Kernels to the software guys, and focus on improvements on the physical side of things.
Thanks for keeping the conversation friendly. Always great to hear other people's opinions on matters.
Click to expand...
Click to collapse
I think I speak for everyone here when I say "Bring them on!"
2 cents to add
I have worked in various areas of IT for over 30 years. Unfortunately android has not been one of them but the basic ideas are always the same. As one reader noted (with a little bit of steam coming from his ears) no one owes you anything here. You aren't paying and you're pretty lucky to have so many talented people making their efforts available to you. I, for one, am very appreciative. I do see the point however about documentation. I have been slowly (and painfully) coming up to speed on the various facets of this g-tab experience. What I find most frustrating is not the lack of directions (there are plenty if you look) or even responses (Clemsyn responded to my request for kernel updating info) but the lack of basic information. I recognize a linux type structure when I snoop around the file system. What is the relation of the ROMS to that? What exactly does clockwork do and where does it live? When you "clear caches" what exactly are you clearing? etc. I'm not expecting answers to these questions here but I think that is the problem a lot of us "caught in the middle guys" have. Sure, we can follow directions and usually everything works just the way it is supposed to but we don't know WHY. If you just blindly follow directions that makes you a "user" not an "admin" and who wants to be a user???? ha-ha What I really want to know is how/where do the more experienced people here (including devs) get their base information to know how to tinker with kernels, ROMS, etc? Where is the G-Tab Development for Dummies book hiding????
enigmas 0456,
You will find that lack of documentation is the hallmark of Android -- not just
here but everywhere. Probably more info here than most places.
Rev
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.
I wanted to root my htc one s so i could put a custom rom on it. I unlocked the bootloader and then I flashed a custom recovery. So i rebooted into twrp recovery and wipe data, cache and dalvik and then proceeded to install cm 10. It installed and then i installed the gaaps which also installed sucesfully. So i rebooted and now all it does it just goes to a white screen with the htc logo. I did have s on but does that make a diffrence. I also tried making s off but it doesnt work since i have no rom.
Help!! My phone is basically useless now!!!
genardas said:
I wanted to root my htc one s so i could put a custom rom on it. I unlocked the bootloader and then I flashed a custom recovery. So i rebooted into twrp recovery and wipe data, cache and dalvik and then proceeded to install cm 10. It installed and then i installed the gaaps which also installed sucesfully. So i rebooted and now all it does it just goes to a white screen with the htc logo. I did have s on but does that make a diffrence. I also tried making s off but it doesnt work since i have no rom.
Help!! My phone is basically useless now!!!
Click to expand...
Click to collapse
You obviously didn't read/followed the install instructions. Read it again.
Then please tell me what you missed.
Verstuurd van mijn One S met Tapatalk
Seems you didn't flash the boot.img separately...
Sent from my HTC One S using xda app-developers app
Ah, now he doesn't have to look troby--:laugh: jk
I just downloaded someone else backup and restored to it all is well!
Sent from my SGH-T999
That's the easy way--you cheated--
If you don't learn not only how to do it correctly, but why, you will always have trouble and have to rely on nice guys like troby86 for help. They won't always be there. Most of us spent dozens, if not more hours, learning all this stuff. And continue to learn. Since you invested a lot of money in the phone, you should spend some time learning how to flash stuff safely/correctly.
Sorry for preaching, but just trying to prevent you from having more and maybe unrecoverable phone issues--
rugmankc said:
That's the easy way--you cheated--
If you don't learn not only how to do it correctly, but why, you will always have trouble and have to rely on nice guys like troby86 for help. They won't always be there. Most of us spent dozens, if not more hours, learning all this stuff. And continue to learn. Since you invested a lot of money in the phone, you should spend some time learning how to flash stuff safely/correctly.
Sorry for preaching, but just trying to prevent you from having more and maybe unrecoverable phone issues--
Click to expand...
Click to collapse
Care to explain/show us what you mean?
I don't know anyone's skill level by just reading posts like on this thread. You may know more than me on Android. And, the info is not, and never has been in one place in Forum or Web.
Here is a link in our Forum with a tutorial on rooting.
http://forum.xda-developers.com/showthread.php?t=2140967
You may already know all that.
A lot can be gleaned from tutorials and videos on web like youtube.
I used all those sources and bookmarked dozens of links till I started to piece it together and have it make sense.
I had to Google Android terms just to find out what rom/nandroid/flash etc even meant. At least as far as Android was concerned. I was familiar with terms like those from engineering classes 40 years ago. But, take on new meaning here.
Anyway, I believe all should download and install Android SDK and become familiar with adb/fastboot. Most experienced users will agree it is best and safest way to flash boots/radios etc. You can also push and pull files from and to phone. Some restrictions apply to those things like flashing radios which depends on your phones hboot on our One S. I was lucky with an early phone and low hboot and can do almost anything with or without adb/fastboot. But, being able to use it can help getting things to phone when other means won't work. Getting in trouble is easy but "understanding" how to get out of it is essential.
My second piece of advice would be to skim threads and find ones that offer this info from others asking these questions.
I would always have a nandroid and a recent sdcard bu on your pc.
Read the threads OP page completely and first and last 20 pages, at least, of the thread. Even after doing this for years, I have done this and have read posts that alerted me not to flash the latest, listed rom version or some other file on OP. Some threads, I believe, still don't state if rom is for s3 or s4. Maybe listed kernel had some issues not found on OP, but 10 pages back into thread.
Also, when flashing new rom or update with framework or major changes always wipe all including System 3X. Once or three times is up for debate. But, I do this and rarely have ever had flashing issues on any phone/rom.
Flash Image GUI is an app from Market that lets you flash boots independent of hboot. Never used it. But, many swear by it. Still think when you are in real trouble, adb/fastboot experience can be a life saver.
This is all pretty basic so don't know if I wasted time typing this. And not sure what exactly you wanted. No one will write a book on how to do all this flashing stuff. So, like mentioned you have to gather it from a lot of different places. We have become a society of "give it too me now and I don't want to know how you didi it".
But, maybe someone just starting will have some of this help in some way.
Believe me I looked up guides and guides and couldn't find what was wrong. Still don't know how to do it right but it's fine since I just sold the phone. On the s3 it's so much simpler u root it via some program by picking a file. Then just flash roms through recovery. This phone I thought you just unlock the bootloader and then just install super user and that's it. Just flash roms through recovery. But then some stuff came up with s on and s off and I tried figuring that out but I just got lost at hex editor. Anyways it doesn't matter just know to not get HTC phones.
Sent from my SGH-T999
HTC has made it harder than some other phones. I did have a Nexus One before the One S. Google, but still HTC. Still, I think is important to understand a lot of this. Since, you can get in trouble on any phone.
The procedures you are describing are what was/is called one-click rooting. Became popular on Nexus One. But, some found rooting by that method restricted them on doing certain things they wanted to do and troubleshooting and getting out of soft bricks. I think they could not use either adb or fastboot and needed that to restore phone.
Anyway, good luck on new phone--
rugmankc said:
I don't know anyone's skill level by just reading posts like on this thread. You may know more than me on Android. And, the info is not, and never has been in one place in Forum or Web.
Here is a link in our Forum with a tutorial on rooting.
http://forum.xda-developers.com/showthread.php?t=2140967
You may already know all that.
A lot can be gleaned from tutorials and videos on web like youtube.
I used all those sources and bookmarked dozens of links till I started to piece it together and have it make sense.
I had to Google Android terms just to find out what rom/nandroid/flash etc even meant. At least as far as Android was concerned. I was familiar with terms like those from engineering classes 40 years ago. But, take on new meaning here.
Anyway, I believe all should download and install Android SDK and become familiar with adb/fastboot. Most experienced users will agree it is best and safest way to flash boots/radios etc. You can also push and pull files from and to phone. Some restrictions apply to those things like flashing radios which depends on your phones hboot on our One S. I was lucky with an early phone and low hboot and can do almost anything with or without adb/fastboot. But, being able to use it can help getting things to phone when other means won't work. Getting in trouble is easy but "understanding" how to get out of it is essential.
My second piece of advice would be to skim threads and find ones that offer this info from others asking these questions.
I would always have a nandroid and a recent sdcard bu on your pc.
Read the threads OP page completely and first and last 20 pages, at least, of the thread. Even after doing this for years, I have done this and have read posts that alerted me not to flash the latest, listed rom version or some other file on OP. Some threads, I believe, still don't state if rom is for s3 or s4. Maybe listed kernel had some issues not found on OP, but 10 pages back into thread.
Also, when flashing new rom or update with framework or major changes always wipe all including System 3X. Once or three times is up for debate. But, I do this and rarely have ever had flashing issues on any phone/rom.
Flash Image GUI is an app from Market that lets you flash boots independent of hboot. Never used it. But, many swear by it. Still think when you are in real trouble, adb/fastboot experience can be a life saver.
This is all pretty basic so don't know if I wasted time typing this. And not sure what exactly you wanted. No one will write a book on how to do all this flashing stuff. So, like mentioned you have to gather it from a lot of different places. We have become a society of "give it too me now and I don't want to know how you didi it".
But, maybe someone just starting will have some of this help in some way.
Click to expand...
Click to collapse
+1000
The first time I tried to flash a ROM on my phone I softbricked it since I didn't follow directions. I searched the web for at least a couple of hours trying to figure out 1) what happened to my phone and 2) How to fix it. I eventually found a thread on here and a separate thread on another Forum with the solution to my problem. I learned UNIX in school so I had some knowledge with the commands to help me. I'm not a big fan of the All-in-One tools because as the poster above me said you don't learn and are bound to make the same mistake as a result. The knowledge also transfers across whatever Android device you're using so I think it's quite relevant to learn as much as you can
IntelligentAj said:
+1000
The first time I tried to flash a ROM on my phone I softbricked it since I didn't follow directions. I searched the web for at least a couple of hours trying to figure out 1) what happened to my phone and 2) How to fix it. I eventually found a thread on here and a separate thread on another Forum with the solution to my problem. I learned UNIX in school so I had some knowledge with the commands to help me. I'm not a big fan of the All-in-One tools because as the poster above me said you don't learn and are bound to make the same mistake as a result. The knowledge also transfers across whatever Android device you're using so I think it's quite relevant to learn as much as you can
Click to expand...
Click to collapse
I don't understand what there is to learn. Could you enlighten me as to what I am supposed to learn. From what I gather, all you are supposed to do when flashing a rom is flash the boot.img, factory reset and wipe data/cache a few times, install the rom and then wipe cache again. Isn't it all done then?
Well, I guess you got it figured out and I wasted my time on a lengthy post--
eLiTeOneS said:
... factory reset and wipe data/cache a few times, install the rom and then wipe cache again. Isn't it all done then?
Click to expand...
Click to collapse
I'm using Android on several phones and tablets for a while, but there's one thing i still don't understand. Why should i wipe more than once before installing a rom? I often read that, never did that and never had a problem. And: ain't factory reset and wipe data/cache the same?
Sent from my HTC One S using xda app-developers app
That is topic of discussion and disagreement for many. Most devs will recommend multi wipes. I have had on occasion issues with one wipe. Never with multi. If you don't wipe System, some remnants of previous rom can be left behind. Same for only one wipe for data. Caches I normally only do once or twice. All this is very quick to do. My analogy is doing a quick fomat as opposed to a full format on a disk. It is my opinion that one wipe does not get it all. Others can have a different opinion. But, I will continue to wipe all multi times. After 3 years and hundreds of successful flashes, I don't plan to change. If i have an issue I can't fix, normally an sdcard reformat works. Some files there are tied to the phone also and if become bad/corrupted can still cause issues even with multi wipes. I have read many posts where someone with problems got sorted after multi wipes and/or an sdcard reformat.
All imho--
You may continue to have no issues and great. My problem with the other poster is that after asking for advice and reading my post still thinks all you do is wipe data/caches, flash boot then rom and nothing else to know. My point is you need to read, read, read before flashing theses roms. You have an investment to protect. You also should know why you are doing things and there consequences and how to get out of trouble. I see many posts by people you just did what the other member mentioned, never read OP or any part of thread and wound up soft bricked, bootlooped etc. Not even paying attn to whether the rom was for an S3 or S4.
Again, I have no idea of anyones expertise here. And most know more than me. That is why I am cautious and respect tips/advice from more knowledgeable users. It took me a long time to force myself to learn adb/fastboot. Even with a lot of prodding by a much more learned member. Glad I finally did.
What I hate to see is someone asking a question answered one page back or "hey, just got phone. can someone give me a step by step on rooting/flashing. no I haven't read anything yet"
Anyway my 2 cents--
Sorry for rant, must be bored today--
rugmankc said:
That is topic of discussion and disagreement for many. Most devs will recommend multi wipes. I have had on occasion issues with one wipe. Never with multi. If you don't wipe System, some remnants of previous rom can be left behind. Same for only one wipe for data. Caches I normally only do once or twice. All this is very quick to do. My analogy is doing a quick fomat as opposed to a full format on a disk. It is my opinion that one wipe does not get it all. Others can have a different opinion. But, I will continue to wipe all multi times. After 3 years and hundreds of successful flashes, I don't plan to change. If i have an issue I can't fix, normally an sdcard reformat works. Some files there are tied to the phone also and if become bad/corrupted can still cause issues even with multi wipes. I have read many posts where someone with problems got sorted after multi wipes and/or an sdcard reformat.
All imho--
You may continue to have no issues and great. My problem with the other poster is that after asking for advice and reading my post still thinks all you do is wipe data/caches, flash boot then rom and nothing else to know. My point is you need to read, read, read before flashing theses roms. You have an investment to protect. You also should know why you are doing things and there consequences and how to get out of trouble. I see many posts by people you just did what the other member mentioned, never read OP or any part of thread and wound up soft bricked, bootlooped etc. Not even paying attn to whether the rom was for an S3 or S4.
Again, I have no idea of anyones expertise here. And most know more than me. That is why I am cautious and respect tips/advice from more knowledgeable users. It took me a long time to force myself to learn adb/fastboot. Even with a lot of prodding by a much more learned member. Glad I finally did.
What I hate to see is someone asking a question answered one page back or "hey, just got phone. can someone give me a step by step on rooting/flashing. no I haven't read anything yet"
Anyway my 2 cents--
Sorry for rant, must be bored today--
Click to expand...
Click to collapse
I'm actually glad you told me all this. I've been through many bootloops, but I don't really see how learning A LOT about all of this is required. Don't you just need to fullwipe/cache after booting into recovery and then just recover your device? Sorry if I come across as arrogant or something, I'm really not trying to be. I have read around about this, but none of the sites/tutorials I went to discussed ANYTHING about spending a long time researching the matter. I thought it was as simple as following the instructions from Developers.
No problem. The actual steps are relatively simple. But, not all Dev's give all needed steps. Some leave out wiping System, as an example. My only point is not only know the steps but why you are doing them and what to do if you get into trouble. The threads are sprinkled with folks just doing the steps and getting into trouble and not knowing how to get out of it. Then they want the easy step by step to get out of trouble and still don't want to understand the why's of what they are doing.
As I mentioned, you may not be one of them. It is hard to ascertain someone's skill level or true meaning just by the post itself. So, my comments are just general fyi.
Since XDA is a development forum, there won't be extensive how to's. But the wiki's and stickies do contain a lot of info. And, scanning certain threads that have subject matter you are interested in can give a lot of insight also. Lots of You Tube videos too.
Good Luck--
rugmankc said:
No problem. The actual steps are relatively simple. But, not all Dev's give all needed steps. Some leave out wiping System, as an example. My only point is not only know the steps but why you are doing them and what to do if you get into trouble. The threads are sprinkled with folks just doing the steps and getting into trouble and not knowing how to get out of it. Then they want the easy step by step to get out of trouble and still don't want to understand the why's of what they are doing.
As I mentioned, you may not be one of them. It is hard to ascertain someone's skill level or true meaning just by the post itself. So, my comments are just general fyi.
Since XDA is a development forum, there won't be extensive how to's. But the wiki's and stickies do contain a lot of info. And, scanning certain threads that have subject matter you are interested in can give a lot of insight also. Lots of You Tube videos too.
Good Luck--
Click to expand...
Click to collapse
Thanks, it's just the way you put it unnerved me quite a lot. I mean, I don't see how there is a LOT of skill required to do this, isn't most of it common sense? I mean, that's how I approach many things; by figuring them out. But if I'm doing everything right, then there's no problem
Cool--
Sounds like you got it all figured. Didn't mean to upset. But, it is hard to read btwn lines on posts. Mine included So, sometimes things are not taken correctly.
In time you will see more of the posts that make some of us scratch our heads and wonder why the question was even asked.
For now have fun and Nandroid--and backup sdcard to PC. Those are very important things I still see some not doing--
rugmankc said:
Cool--
Sounds like you got it all figured. Didn't mean to upset. But, it is hard to read btwn lines on posts. Mine included So, sometimes things are not taken correctly.
In time you will see more of the posts that make some of us scratch our heads and wonder why the question was even asked.
For now have fun and Nandroid--and backup sdcard to PC. Those are very important things I still see some not doing--
Click to expand...
Click to collapse
Yeah, I did one of them, but that was a silly mistake on my behalf. Anyway, if you were to backup your SD Card on your PC, what good would that do?