I just got the MT4GS after being a long time MT4G user and I'm wondering if it is worth it to root as there is currently no CM or stable Virtuous Rom which is what I used on the MT4G. Any helpful opinions are much appreciated.
micahman said:
I just got the MT4GS after being a long time MT4G user and I'm wondering if it is worth it to root as there is currently no CM or stable Virtuous Rom which is what I used on the MT4G. Any helpful opinions are much appreciated.
Click to expand...
Click to collapse
If Virtuous is what you like then I'd say yes, go for it and root. The Virtuous ROM might be in beta here in the MT4GS forums but it was smokin' fast and stable enough when I used it. I'm sure an official release is just around the corner anyway. good luck and welcome to the MT4GS family!!
siani_8 said:
If Virtuous is what you like then I'd say yes, go for it and root. The Virtuous ROM might be in beta here in the MT4GS forums but it was smokin' fast and stable enough when I used it. I'm sure an official release is just around the corner anyway. good luck and welcome to the MT4GS family!!
Click to expand...
Click to collapse
Thanks for the feedback and welcome, good enough reason for me. One thing I do like a lot on stock is the camera app, is that included in the beta or is there a flashable mod?
micahman said:
Thanks for the feedback and welcome, good enough reason for me. One thing I do like a lot on stock is the camera app, is that included in the beta or is there a flashable mod?
Click to expand...
Click to collapse
Yes sir, the Doubleshot camera app is included.
micahman said:
I just got the MT4GS after being a long time MT4G user and I'm wondering if it is worth it to root as there is currently no CM or stable Virtuous Rom which is what I used on the MT4G. Any helpful opinions are much appreciated.
Click to expand...
Click to collapse
Root it. Then you can:
Enhance your gps ability because of the generic gps file that's coded very poorly (in fact wrongly ... T-Mo doesn't maintain a good SUPL server, and if you're not on the T-Mo network your AGPS isn't working in stock configuration...well, maybe a little, but not anything worth mentioning. )
Flash a better security update to fix the big-brotheresque HTC spy mode (htcloggers.apk). HTC released an update to patch their security hole, but they are still monitoring everything you do with the device. Flash Undeadk9's security patch to just cut them off at the knees instead, or uninstall htcloggers.apk ( and other file I can't remember at the moment )
Change your hardware key files and re-map some buttons to be more useful.
Flash custom ROMs, as you're aware...
Play with the upcoming kernel files from myself and others...( give us time to make it stable )
...and so much more!
Generally do the things with the device that you've paid for that you should be able to do. Why spend all this money on something, and only use like 60% or less of what it can do?
If you're here and posting, then you should probably just go ahead and root it. It won't be long after you've been poking around in here reading through all the things we have been/are doing with the device before you'll go for it.
Check the sticky at the top of the general section to get a good handle on where to go first and what to read through. Take the time to read through the threads ( I know they are long ) - you'll see what all the problems were that people encountered, and how they were solved. Even if you don't run into the problems, at least you'll learn a whole lot and understand your device much, much more intimately.
...and if you get stuck, we're here to help. Many of us have been through this whole process countless times before, and are willing to lend a hand - just don't post random questions in the dev section and everything will be good.
Welcome to our little corner of the XDA universe - you'll love this device!
Blue6IX said:
Root it. Then you can:
Enhance your gps ability because of the generic gps file that's coded very poorly (in fact wrongly ... T-Mo doesn't maintain a good SUPL server, and if you're not on the T-Mo network your AGPS isn't working in stock configuration...well, maybe a little, but not anything worth mentioning. )
Flash a better security update to fix the big-brotheresque HTC spy mode (htcloggers.apk). HTC released an update to patch their security hole, but they are still monitoring everything you do with the device. Flash Undeadk9's security patch to just cut them off at the knees instead, or uninstall htcloggers.apk ( and other file I can't remember at the moment )
Change your hardware key files and re-map some buttons to be more useful.
Flash custom ROMs, as you're aware...
Play with the upcoming kernel files from myself and others...( give us time to make it stable )
...and so much more!
Generally do the things with the device that you've paid for that you should be able to do. Why spend all this money on something, and only use like 60% or less of what it can do?
If you're here and posting, then you should probably just go ahead and root it. It won't be long after you've been poking around in here reading through all the things we have been/are doing with the device before you'll go for it.
Check the sticky at the top of the general section to get a good handle on where to go first and what to read through. Take the time to read through the threads ( I know they are long ) - you'll see what all the problems were that people encountered, and how they were solved. Even if you don't run into the problems, at least you'll learn a whole lot and understand your device much, much more intimately.
...and if you get stuck, we're here to help. Many of us have been through this whole process countless times before, and are willing to lend a hand - just don't post random questions in the dev section and everything will be good.
Welcome to our little corner of the XDA universe - you'll love this device!
Click to expand...
Click to collapse
Wow, thank you for all the info, I am very grateful. I've noticed there are a few threads detailing how to root but can you tell me which one would be the best and most reliable? Thanks again for all the info, especially about that HTC spy stuff, I had no idea.
micahman said:
Wow, thank you for all the info, I am very grateful. I've noticed there are a few threads detailing how to root but can you tell me which one would be the best and most reliable? Thanks again for all the info, especially about that HTC spy stuff, I had no idea.
Click to expand...
Click to collapse
I used theunlockr.com to root it, worked like a charm and has a video walk throu.. which I'm a big fan of. Easier to follow. but the only difference is to flash modoco cwm not revolutionary.. so you can flash undeadK9's roms.. id suggest senseless.
Sent from my Senseless Doubleshot using xda premium
shady503403 said:
I used theunlockr.com to root it, worked like a charm and has a video walk throu.. which I'm a big fan of. Easier to follow. but the only difference is to flash modoco cwm not revolutionary.. so you can flash undeadK9's roms.. id suggest senseless.
Sent from my Senseless Doubleshot using xda premium
Click to expand...
Click to collapse
Thanks man! Got it rooted and running senseless! So far so good!
Not to contradict Shady's advice, especially since it seems like it worked for you, but i've previously and still do recommend against going to a third party web resource outside of XDA to root the device.
The reason being is that a lot of us did everything from the information available here, and we are familiar with the processes and common problems people run into following the guides posted here in the forums.
If you post questions about problems or an issue you run into, you run the risk of slow or no support because of the unfamiliarity the majority of us here have with outside methods and resources.
I know off the top of my head I could post a helpful response to someone having a problem with a method described here. For an outside resource...i'd probably have to go look it up, maybe download somehing, and probably try the method before being able to help.
Then i'd have to dig into the code of whatever offering was in question, to ensure it wasn't doing anything I didn't want it to do before installing anything.
Ultimately, this is a lot more time and trouble then just digging into my memory or looking up a specific thread to verify something, and also probably provide a link to the specific post that addresses the problem.
I'm hitting overtime consistently on my night job, and still picking up hours at my day job, and honestly would rather commit the level of time necessary to troubleshoot an outside resource on something more personally productive, like digging deeper into kernel source or something.
Just a thought to keep in mind as you (and others in the future) wander around here. I promise that everything you need to root your phone and install custom ROMs and such is right here in the MT4GS forums. (excepting the need to go to the revolutionary resource for S-OFF).
Cm7 just dropped like a bomb
sent from my real Gs move in silence like lasagna
mbernusg said:
Cm7 just dropped like a bomb
sent from my real Gs move in silence like lasagna
Click to expand...
Click to collapse
With a follow up by Official CWM Recovery. Today was a good day.
Coug76
Blue6IX said:
Not to contradict Shady's advice, especially since it seems like it worked for you, but i've previously and still do recommend against going to a third party web resource outside of XDA to root the device.
The reason being is that a lot of us did everything from the information available here, and we are familiar with the processes and common problems people run into following the guides posted here in the forums.
If you post questions about problems or an issue you run into, you run the risk of slow or no support because of the unfamiliarity the majority of us here have with outside methods and resources.
I know off the top of my head I could post a helpful response to someone having a problem with a method described here. For an outside resource...i'd probably have to go look it up, maybe download somehing, and probably try the method before being able to help.
Then i'd have to dig into the code of whatever offering was in question, to ensure it wasn't doing anything I didn't want it to do before installing anything.
Ultimately, this is a lot more time and trouble then just digging into my memory or looking up a specific thread to verify something, and also probably provide a link to the specific post that addresses the problem.
I'm hitting overtime consistently on my night job, and still picking up hours at my day job, and honestly would rather commit the level of time necessary to troubleshoot an outside resource on something more personally productive, like digging deeper into kernel source or something.
Just a thought to keep in mind as you (and others in the future) wander around here. I promise that everything you need to root your phone and install custom ROMs and such is right here in the MT4GS forums. (excepting the need to go to the revolutionary resource for S-OFF).
Click to expand...
Click to collapse
Very true. They use a lot of information found at xda to build their guides off of thou. And a video tutorial is always nice, for me anyways. but yeah.. don't expect support from theunlockr.com.
I always go their, sometimes their outdated or wrong. But still gave me a general idea and I was able to use multiple guides to give me the correct process..
Sent from my Senseless Doubleshot using xda premium
I'm glad I was able to find this thread, cause I've been wondering whether or not it would actually be worth it to root a MT4GS or not. And ya, I can agree that for the most part, rooting has more benefits than problems. And I always have gotten the same answer when asking that question about other devices, "Just root it; you'd have to be crazy not to; nothing compares to a rooted phone, etc...". So I gave in and rooted my MT3G 1.2 (w/ the headphone jack on top). After a while I noticed some definite problems: a few important features were gone, also it was impossible to update G. Maps (because of being rooted), and finally the worst scenario of all: not being possible to un-root the device. I must have tried 10 times, following the directions to the T and repeatedly getting the same failure error. I was finally able to find someone else with a similar problem who posted their solution. Tried, waited, failed. Fully bricked, I mean not even a flicker or a battery light would come on after that. Fortunately, I was able to lie to customer service and convince them to do a warranty exchange (Aeon-1, T-Mobile-0) so I got a replacement and haven't rooted since.
So I guess my point is, I'm actually scared to root my new MT4GS for the sake of potentially not being able to unroot it if need be. But, so far from what I've read it looks like it is reversable if I ever need to. I was likely considering using theunlockr.com's method due to clearly stated, and easily understood instructions. I wish I could say the same about the posts I've read @ XDA regarding rooting instructions.
-Which rooting methods are guaranteed to be un-rootable? That option is crucial, if I ever need to go back to stock or do a warranty exchange (for all those people who were gonna say "Why the hell would you ever consider unrooting?)
-So some people suggest ClockworkMod Recovery, others don't seem to care. I ask, is there any real difference between the two? And why?
-Also, which are the best/most stable roms you would suggest? Because I've done the trial and error thing before, comparing several different roms, and I never seemed to find anything worthwhile. (Also, I checked CyanogenMod's site and either I'm blind or they don't have a single rom for the MT4GS)
-I think you somewhat answer the question regarding features of the stock camera being available after rooting. But I need to know: After rooting, is the camera going to be the same as the stock one, including ALL available features (SweepShot, ClearShot HDR, Burst Shot, Macro, Night...)? And is that camera program featured within all rooted roms, or does it have to be installed seperately?
-And ditto that question in regards to G-Maps.
-And finally this may seem like a n00b question, but I've still never gotten a clear answer: How/When can a Nandroid Backup be performed? I know that it would be a safety precaution in case I ever f*cked up my device and needed to restore, but I've never been able to find clear, accurate, and relevant instructions on how to nandroid backup or even nandroid restore.
So I apologize for asking so many questions, especially since I imagine they seem redundant and novice. However, I have rooted phones before so I'm not a complete n00b; I'm just trying to be VERY thorough this time around, to avoid any potential for error. Thank you in advance for your time.
-Colton
@eon said:
I'm glad I was able to find this thread, cause I've been wondering whether or not it would actually be worth it to root a MT4GS or not. And ya, I can agree that for the most part, rooting has more benefits than problems. And I always have gotten the same answer when asking that question about other devices, "Just root it; you'd have to be crazy not to; nothing compares to a rooted phone, etc...". So I gave in and rooted my MT3G 1.2 (w/ the headphone jack on top). After a while I noticed some definite problems: a few important features were gone, also it was impossible to update G. Maps (because of being rooted), and finally the worst scenario of all: not being possible to un-root the device. I must have tried 10 times, following the directions to the T and repeatedly getting the same failure error. I was finally able to find someone else with a similar problem who posted their solution. Tried, waited, failed. Fully bricked, I mean not even a flicker or a battery light would come on after that. Fortunately, I was able to lie to customer service and convince them to do a warranty exchange (Aeon-1, T-Mobile-0) so I got a replacement and haven't rooted since.
Click to expand...
Click to collapse
Sorry to hear that didn't work out so well. I think you'll find that your MT4GS experience will be a lot better.
Check the link to my backup thread in my signature. Read through it, and feel free to ask any questions in that thread you may have. I or another will be happy to help you clear them up.
Link: Backups - After Rooting, before ROMing, take this step
@eon said:
So I guess my point is, I'm actually scared to root my new MT4GS for the sake of potentially not being able to unroot it if need be. But, so far from what I've read it looks like it is reversable if I ever need to. I was likely considering using theunlockr.com's method due to clearly stated, and easily understood instructions. I wish I could say the same about the posts I've read @ XDA regarding rooting instructions.
Click to expand...
Click to collapse
Yea, everything tends to happen first here, so trying to keep it all organized as things change and develop is difficult at times, much too convoluted at others.
Basically, you need to take your bootloader from S-ON to S-OFF. Do this with the Revolutionary exploit. It installs CWM 4.0.0.8 during the process.
Then you need to make a nandroid backup. (see my backup thread)
Then you should upgrade to the official Clockworkmod Recovery, replacing 4.0.0.8 that was installed with the S-OFF exploit. The version is 5.0.2.7
Dev section link for the official CWM:
http://forum.xda-developers.com/showthread.php?t=1329160
Once you do that, you should already have the superuser.apk you need for rooting that you found when you got the Revolutionary S-OFF tools. You can either have done it then, or now.
I'd wait until after getting the official CWM first, simply because that makes your first nandroid backup as fresh as it can be. It's up to you when you do it.
And that's basically it.
You now have a stock, rooted phone that you can start to play with. I'd say play with it for a little while on the stock ROM before switching to another, that way you'll get a feel for what you gain or lose, and if the various trade-offs are worth it.
Before doing any of that stuff, though, read through this thread:
Read this before posting. MT4G Slide Compendium
That will get you a little more familiar with the terminology, and provide helpful links to start exploring what you need to know.
Also read as much of this thread as you can stand:
S-OFF for Retail (S-ON) Devices, NOTE ADDED 8/17/11
This S-OFF for retail is the thread that officially announced the Revolutionary exploit for S-OFF here. The links in the OP will take you to where you need to go to get it.
If you get through that one, then this is a follow up:
PERMANENT-ROOT (NEW!) & Temp-Root (v2) for any MT4GS (Windows)
The temp-root thread is a bit confusing, because before we got S-OFF you could root the phone until you rebooted it. Once the Revolutionary S-OFF method was out, this thread also ran tandem with the official announcement thread. Because it was also dealing with temp root, it led to a lot of confusion.
There is some really good info in that thread, but I recommend reading the official release thread first. It'll make more sense that way, and you may not even have to check the temp-root thread.
(again, this lends to the evolving nature of what we're learning here - hard to keep it organized as it grows.)
Also, this thread: How To Turn S-Off, Install MoDaCo Clockworkmod Recovery, and Install a Rom For Dummie
Was written as a summary on how to get S-OFF and Root, because of how convoluted and looong the two previously mentioned threads got.
Once you hit this point, you're basically set.
My next move would be to install busybox, which you can find in the market, then immediately flash the Security patch to fix a glaring security flaw created by HTC.
At this point i'd make another nandroid backup.
@eon said:
-Which rooting methods are guaranteed to be un-rootable? That option is crucial, if I ever need to go back to stock or do a warranty exchange (for all those people who were gonna say "Why the hell would you ever consider unrooting?)
Click to expand...
Click to collapse
They are all un-rootable, but once you go from S-ON to S-OFF that's a one-way trip. Several people have reported exchanging their devices after returning to stock with an S-OFF bootloader without issue.
This is returning to T-Mobile, though, it's questionable if HTC will accept a return directly of a device with an S-OFF bootloader.
@eon said:
-So some people suggest ClockworkMod Recovery, others don't seem to care. I ask, is there any real difference between the two? And why?
Click to expand...
Click to collapse
As mentioned, upgrade to the official Clockworkmod recovery as soon as possible. From here on out it will be the only supported recovery.
@eon said:
-Also, which are the best/most stable roms you would suggest? Because I've done the trial and error thing before, comparing several different roms, and I never seemed to find anything worthwhile. (Also, I checked CyanogenMod's site and either I'm blind or they don't have a single rom for the MT4GS)
Click to expand...
Click to collapse
I'm working on releasing the updated version of Bulletproof right now, actually, and you'll like that one. Should be out in a day or so. The original developer is moving on and is handing it off to me.
I've just spent the last....dunno how long working at it, and needed to take 5 and clear my head. Cruised through the XDA MT4GS forums as i'm winding down for a break, and you caught me at a good time to give a response.
CM7 just got officially put on hold, but with your interest in the camera you probably wouldn't have gone for that right away. It's an alpha release, and we are very excited to have official CM support for the device, but since Ice Cream Sandwich ( Android 4.0 ) source code was just released, the CM team is focusing on that and it's likely to be a while before the CM7 for our phone sees an update.
Honestly, i'm more excited that they are focusing so exculsively on Ice Cream Sandwich, because that means a lot more for all the phones and devices beyond just our own version of CM7.
I'll leave other ROM recommendations to others who will surely come through here and tell you more about them.
@eon said:
-I think you somewhat answer the question regarding features of the stock camera being available after rooting. But I need to know: After rooting, is the camera going to be the same as the stock one, including ALL available features (SweepShot, ClearShot HDR, Burst Shot, Macro, Night...)? And is that camera program featured within all rooted roms, or does it have to be installed seperately?
-And ditto that question in regards to G-Maps.
Click to expand...
Click to collapse
Pretty much all of the ROMs will support both the Camera app (in its entirety, included in the ROM) and Google maps.
The alpha port of CM7 is the only one (pretty sure) that doesn't support the camera, because the camera is tied into the sense frameworks. CM7 has no Sense components to it, and it was stated very clearly in the thread that it never will. The CM team and their ROM is worth losing the camera app over to a lot of people, and they are the lone exception to the "no camera app" stigma.
Keeping the camera app is one of the things that has been driving development around here, and very few people were willing to use or invest time in making a ROM that would exclude it.
I should take this time to point out that the stock gps configurations are, well, flat out wrong. Misconfigured, and it doesn't work well.
Myself and another developer independently spent a lot of time working on fixing this issue, and when we realized what each other were doing we also realized that we had the piece of the puzzle the other needed to make it work.
We released a collaboration that solved the problem, which you can find here: GPS lock too long or not at all? Try this
If you want to know how my half of the puzzle works, that thread will explain it in almost excrutiating detail. I recommend my patch over the other developers, as he is no longer with us and I will only be continuing support in my thread.
@eon said:
-And finally this may seem like a n00b question, but I've still never gotten a clear answer: How/When can a Nandroid Backup be performed? I know that it would be a safety precaution in case I ever f*cked up my device and needed to restore, but I've never been able to find clear, accurate, and relevant instructions on how to nandroid backup or even nandroid restore.
Click to expand...
Click to collapse
Just cruise through my backup thread. Post 1 is an adb method, post 2 is the nandroid method. If you have any questions, post them in that thread and help us try to maintain some kind of order (hah!)
@eon said:
So I apologize for asking so many questions, especially since I imagine they seem redundant and novice. However, I have rooted phones before so I'm not a complete n00b; I'm just trying to be VERY thorough this time around, to avoid any potential for error. Thank you in advance for your time.
-Colton
Click to expand...
Click to collapse
Honestly, don't ever worry about asking too many or too long of a question, as long as you don't post the question itself as a new thread in the development section of the MT4GS forums.
I'm sorry to hear it took such a bad experience for you to become as cautious as you are, but now that you're long past it you are much better off.
I'd much rather see someone ask questions, read some stuff, ask more questions, and then act on knowledge then just go and do and then say "I broke it, what do I do".
I'm happy to help either way, but if the information is there already then reading it before you start is much better then retroactively. Save the "how do I fix it" for uncharted territory learning things that aren't already common knowledge.
Again, part of the problem is that information is so convoluted because we keep adding to it as we learn new things. You can't really structure it before you know what it's going to be.
Myself and a few others have been trying to put effort into organizing things, but it's really a monumental task and i'd like to develop new things more so then catalogue what we already know. It's a crappy balance, but I try to put equal time to developing and organizing/answering questions.
I hope this helped you out some, I know I didn't completely cover it all but it should give you some things to chew on and help you sift through the data by spending more time on the relevant parts. Even then it's still a lot that you should know.
Don't be afraid to ask questions, one of the reasons I go into such depth is because people can correct me precisely where i'm wrong if I am about something.
You learn more when you're willing to admit you don't know something, then to pretend you do for whatever reason. Asking the right questions depends on being honest about what you do and don't know with yourself, so fire away.
I've got to get outside for a few minutes, then get back into coding, but someone else will come along and add to this soon enough.
Take care!
Well I definitely very much appreciate your prompt, and very detailed response to my many questions. I've been reading over what you've written plus the links over the past day. The main issue I have is digging through each thread looking for relevant information, while trying not to get sucked into each and every tangent post/link/info. I lost track of how many hours I've wasted reading irrelevant info which I initially thought actually had something to do with what I was after. And now a day later, I have my desk covered in reference notes (which are no longer comprehensible) and I'm more confused than I was before.
There are plenty of issues I have with forums in general. First of which being, organization seldom exists. Its like going into a library with a single question about 'how to change a tire', and leaving with 15 random, heavy books on quantum theory and black-matter, because apparently someone implied they were somehow related (I'm referring to other people, not you). Discouraging to say the least. I thought this would be more black-and-white; more simple. When 'Android' was new, rooting was simple (less ways to re-invent the wheel).
I'm walking away from this for now. The headache isnt worth it (I literally feel like I got skull-f*cked by god himself). But thank you for your help and feedback.
micahman said:
I just got the MT4GS after being a long time MT4G user and I'm wondering if it is worth it to root as there is currently no CM or stable Virtuous Rom which is what I used on the MT4G. Any helpful opinions are much appreciated.
Click to expand...
Click to collapse
Yes it is DEFINITELY worth it... Root away my friend and welcome to the MT4GS family. This phones kicks ass and we are expanding every day like wildfire
Sent from my myTouch_4G_Slide using xda premium
@eon said:
...
I'm walking away from this for now. The headache isnt worth it (I literally feel like I got skull-f*cked by god himself). But thank you for your help and feedback.
Click to expand...
Click to collapse
Hah, yea, XDA is like that all over - just the nature of the beast.
This is not the quick-answer type of home, yet from a developers point of view there is no better place on the internet for android/phone development information and help.
It really does all start here, and the journey of discovery is much more prized and worthwhile then the actual end result. In that respect the way XDA is, is the way it should be.
Sometimes the best way to come to grips with something is to forget about it for a little while. Let your mind work it over running in the background, and when you bring it back into focus you'll have a better hold on what you need, and what you still have to learn.
Again, feel free to ask any questions you may have and we'll do the best we can to get you set in the right direction.
Ya, it was like mass overload the other day; it was like trying to make a PBJ sandwhich, then realizing I have to bake my own bread from scratch, grind up peanuts into butter, and somehow pick my own berries for jam, etc...
Anyways, I read over some of those topics again and some of it makes a little more sense. But still, some of those threads are so damn long, Im not gonna read each and every post from top to bottom of the thread, at least not yet. But the main issue I've realized is definitely going to be a problem is the fact that turning S-Off is irreversible. There is absolutely no method of turning S-On after its been turned off, which doesnt seem to make any sense; I figure, if you are able to flip a light-switch on, its only obvious you should be able to flip the switch off. So why is the 'S-Off' method a one-way path? And is this problem going to be fixed?
I read a bunch of articles and tutorials on 'unrooting' the MT4GS, and each one says that it will change the phone back to the stock factory condition it was in before rooting. Of course, once I scroll down and keep reading comments, everyone says that there isnt a way to turn "S-ON". SO, how the hell would someone be able to root their phone while still ever having the option to do a warranty exchange? Unrooting is great cause it gets you most the way there. But I've been reading that when T-Mobile recieves the phone, they send it to HTC for inspection/repair, and thats where they look at all the software/firmware/h-boot/recovery/S-ON Versions to make sure they are at factory specs. So once again, even though it is possible to "unroot" the MT4GS if need be, it still impossible to fully go back to factory standard (which is exactly what I was worried about).
Thats ****ty cause I was actually willing and ready to start rooting via theunlockr.com's method (cause its a hell of a lot easier than any tutorial in these forums, it does it the same way, its just easier to understand). BUT, that S-ON/S-OFF snafu is enough for me to reconsider. As I'm sure there are tons of benefits to rooting and therefore I may not ever want to unroot, I still may need to for the sake of the warranty exchange. And believe me when I say that I NEED to have the ability to exchange; I've had to exchange the MT4GS 5 times within 3 consecutive weeks because each one I recieved in the mail had some physical manufacturer defects. And since the most recent replacement is a refurb, I need to leave that Warranty-Door open in case I need to exchange.... again.
By the way, I forgot why S-Off was required in the first place. Is it possible to remain rooted without S-Off???
@eon said:
Ya, it was like mass overload the other day; it was like trying to make a PBJ sandwhich, then realizing I have to bake my own bread from scratch, grind up peanuts into butter, and somehow pick my own berries for jam, etc...
Anyways, I read over some of those topics again and some of it makes a little more sense. But still, some of those threads are so damn long, Im not gonna read each and every post from top to bottom of the thread, at least not yet. But the main issue I've realized is definitely going to be a problem is the fact that turning S-Off is irreversible. There is absolutely no method of turning S-On after its been turned off, which doesnt seem to make any sense; I figure, if you are able to flip a light-switch on, its only obvious you should be able to flip the switch off. So why is the 'S-Off' method a one-way path? And is this problem going to be fixed?
I read a bunch of articles and tutorials on 'unrooting' the MT4GS, and each one says that it will change the phone back to the stock factory condition it was in before rooting. Of course, once I scroll down and keep reading comments, everyone says that there isnt a way to turn "S-ON". SO, how the hell would someone be able to root their phone while still ever having the option to do a warranty exchange? Unrooting is great cause it gets you most the way there. But I've been reading that when T-Mobile recieves the phone, they send it to HTC for inspection/repair, and thats where they look at all the software/firmware/h-boot/recovery/S-ON Versions to make sure they are at factory specs. So once again, even though it is possible to "unroot" the MT4GS if need be, it still impossible to fully go back to factory standard (which is exactly what I was worried about).
Thats ****ty cause I was actually willing and ready to start rooting via theunlockr.com's method (cause its a hell of a lot easier than any tutorial in these forums, it does it the same way, its just easier to understand). BUT, that S-ON/S-OFF snafu is enough for me to reconsider. As I'm sure there are tons of benefits to rooting and therefore I may not ever want to unroot, I still may need to for the sake of the warranty exchange. And believe me when I say that I NEED to have the ability to exchange; I've had to exchange the MT4GS 5 times within 3 consecutive weeks because each one I recieved in the mail had some physical manufacturer defects. And since the most recent replacement is a refurb, I need to leave that Warranty-Door open in case I need to exchange.... again.
By the way, I forgot why S-Off was required in the first place. Is it possible to remain rooted without S-Off???
Click to expand...
Click to collapse
not permanently. you'd have to temp-root every time you reboot.
Revolutionary is about the easiest way to root a phone in existence so I'm not sure why you're so scared... assuming you have adb working, it's literally as easy as plugging your phone in and opening a single file in the Revolutionary zip archive. everything is done for you. as long as you don't download their faulty recovery (it will ask you if you want to... just say no), it's literally the easiest rooting method available that I've ever seen.
don't make it too complicated. I certainly believe in having all of your bases covered, especially when it comes to potentially screwing up a $500 bundle of plastic, metal and silicone, but rooting is not a big deal anymore.
many people will tell you that they have received warranty replacements after sending in S-OFF/rooted phones. my best guess would be that HTC/Tmo randomly pick phones to "thoroughly check" and the majority don't receive this type of treatment.. and even if they find a rooted device, there's no telling whether or not they will deny your replacement.
I received a warranty replacement (faulty hardware buttons, the leds never turned off) for my gal's rooted MT4GS simply by installing the stock rom and recovery, but still with Revolutionary's hboot installed. No issues whatsoever. I'm not saying it's "right" and I'm not guaranteeing you the same result, just offering my first-hand experience.
here's how you can obtain perma-root and s-off in ~10 minutes. no complicated guides:
www.revolutionary.io
download installer, enter serial # to get your code.
open archive and find the installer... let it run.
when it's done, you'll be rooted and s-off with a custom hboot. say "no" to the download recovery option and manually flash the official CWM recovery, or modaco's 4.0.0.9 recovery image. (either should be fine, although roms are going to start coming out that may have issues with the 4.0.0.9 modaco recovery so cwm is probably your best bet)
if not being able to flip the S-OFF switch back to S-ON at this point is something you can't get over, this isn't for you. personally, I spent $500 on this phone and I'm going to do whatever the hell I want to it, and if TMO and HTC have a problem with that, I will happily take my business elsewhere.
Its not rooting that I'm worried about, its the possibility of having to do (yet another) warranty exchange and being caught sending back a warranty-void device. And since I just found out that my premium phone insurance extends my warranty for an indefinite amount of time, I imagine that i will undoubtedly be exchanging this phone sometime in the future. I can only hope that by then either the S-Off thing has been fixed or T-Mobile announces they no longer care. I can see both happening, honestly.
Rooting is going to be the easy part, if/when I decide to do it. The last things I havent yet figured out are:
-Which Rom(s) I'm going to try. When I compare most roms side by side, they all seem vaguely identical. I remember Cyanogen having the option of fully customized visual aspects/themes, as well as tons of settings/features that werent offered through other roms. But the problem with CM is that, as you said before, the several camera options/modes in the stock rom are not being used by CM. I'm looking for a rom that is, above all, stable; lightweight/fast; includes all camera features of stock rom; and if apps like gmaps wont be included, I'd like to be able to find something that is comparable, or even better if possible. If not, I really hope the market allows gmaps to be installed on a rooted device (a while back on my rooted phone, the install of gmaps would always fail) Also, you had mentioned that you were nearing completion of a Rom of your own, so I might read up on that as well.
-I read up on that article on micro sd cards regarding speed comparisons, so I ended up running the benchmark app on my pc and found that my SanDisk 8bg Class 4 was (apparently) faster than my currently used Samsung 16gb Class 2, which sucks cause I like having more space than I use. But anyways it got me thinking, I realize that speed is important for file-transfers and also running apps that have been moved to the sd, but I could have sworn I remember someone talking about how they had rooted and then installed their OS/Rom onto their SD card instead of the phone itself. I dont know if I read that wrong or not. And if that was accurate, then I want to know if there is truly any benefit from doing that or not.
-Also, in regards to sd cards, I remember last year when I had a rooted MT3G with Amon Ra's recovery, there was an option to throw in partitions. Almost everyone I talked with on here told me to add a partition. Then after a few updates to the recovery, I noticed new options in the partition section: Ext.2, Ext.3, and Ext.4 as well as the options to select the partition size and "swap" size. I never did understand what exactly the difference (if any) between "Ext.2, Ext. 4.... etc" was.
And as far as the "swap" size, I remember there being a LOT of debate over what exactly this number should be. Some people started suggesting outrageously high numbers, while others explicitly explained to not do that, because apparently the lower the number the faster it becomes. Ok, so if thats the basic concept, great. But I still never did find any reliable information regarding "swap" size.
So ya, those are the final questions/issues that have been bugging me. Any advice/help is greatly appreciated.
Related
Hello everyone. I want to thank you all for this site, I have learned a great deal here and appreciate all your efforts. I have a question that many new comers have asked and they have been told to go read, so thats what I will do. I want you to know tho that its very hard when you have a baby, and very little time. I also want you to know that the only times I am really productive getting somewhere with my phone is staying up till like 4 am because everyone is asleep and I have the time needed to dedicate to all this reading, trying and learning.
I am not complaining, in fact I am grateful because I am getting somewhere thanks to your help, which has been more valuable than all the help Samsung and Rogers have given me washing their hands clean and leaving me with a defective phone. My problem has not been solved just yet, but I think a 2.2.1 rom will fix my problem. Ill keep reading and trying, ill get there.
I suggest you guys have a wikipage with a table with all the roms, what versions of android they are, what kernels, modems, etc they work with ( or not work with ), bugs, features, something all in 1 page for easy access. This would make it easier for people to access information. The easier it is the more people will use them and come here, the more ideas you will have, the more testers, its a win win situation!
I have been to the pages for all the roms, some of them tell you the bluetooh voice dialing is not working, most don't, id have to go looking for my answer. I have learned that for instance it seems people do not have an issue with it with froyo 2.2.1 but again, some roms tell you in the main page its 2.2.1, others don't.
I can't grasp all the information staying up at night till 4 am. Its the only time I have. I almost had a heat attack when I thought I bricked my phone, I can't afford another one. If all the important information is right there on 1 page, like links to the usb drivers, tools, roms, kernels, everything. Have the instructions to flash. Have a table with all the roms, their versions, what versions of kernels, modems, etc, they do ( or dont ) work with. maybe even some of the table cells are clickable, for instance bugs, click on it and a window pops up with a list of them.
I know all this information is in here somewhere. Thanks to everyone for it, but it needs to be on 1 page. Please make it easier for people who are new to this. You will benefit as well as them. Looking forward to being able to use voice dialing. I think it will be working by tomorrow or after tomorrow thanks to you guys. I could have done it in a day if all the information was right there .
Thanks for reading.
Try searching.
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/SGH-I897
I have that bookmarked. It is also a sticky in this section.
But it doesn't say for instance which ones are 2.2.1, or which ones have the terrible voice dialing over bluetooth..
I do search and end up with over 15 tabs...
I am getting by, I am just saying it could be organized better for everyones benefit. It could be made so someone who has never done this before can get it done in a couple of hours if even, without keeping asking you the same questions here. I understand why people keep asking to recommend a ROM. It is not they they do not search, not all of them anyway. Things can be better organized.
I hear what you're saying, I think it's just that within the course of a month, about 20 ROM's have been released, if not more. And no one has had time to update the wiki.
vunuts said:
I hear what you're saying, I think it's just that within the course of a month, about 20 ROM's have been released, if not more. And no one has had time to update the wiki.
Click to expand...
Click to collapse
+1
The thing is that its not just the number of ROMs, but also the number of versions that are released. It would be a real pain and an added overhead for anyone maintaining it.
Also note that most devs are working too, and doing this in their free time. The little time they have to spare is taken up for making improvements. But they do release changelogs to look into.
If anyone has time, I would suggest they take it up to create a wiki and maintain it, rather than relying or asking the devs to do it.
Try capfaq.com it has a ROM table section, and I've used it alot.
Same issues with being 100% up to date, but it's the best Rom table format I've seen.
i897 running Cognition 3.02
Madtowndave said:
Try capfaq.com it has a ROM table section, and I've used it alot.
Same issues with being 100% up to date, but it's the best Rom table format I've seen.
i897 running Cognition 3.02
Click to expand...
Click to collapse
http://www.capfaq.com/w/ROM_Table
Looks like they have updated it!
Thanks guys, I will check that table out tomorrow.
It'd be nice if there was a modem chart as well. I know there are modems in the modem thread
forum.xda-developers.com/showthread.php?t=835272
...but near as I can tell it's not up to date, or at least the first page is not up to date (ie base Cognition runs on JL1 and Andromeda on JL2, but aren't on the first page).
If anyone knows a good and current modem reference guide, please let me know.
I can't complain too much because obviously things change all the time and it's a PITA to constantly update info...I'd volunteer but I got a 2 year old and baby 2.0 due in April.
Madtowndave said:
baby 2.0 due in April
Click to expand...
Click to collapse
made me lol at the versioning of baby
diablo009 said:
made me lol at the versioning of baby
Click to expand...
Click to collapse
Yeah it's like Richter Scale difference at least 0 to 1, and 1 to 2 kids...people that have more than 2 are either really bad at birth control, Catholic, or gluttons for punishment.
distortionist said:
I want you to know tho that its very hard when you have a baby, and very little time. I also want you to know that the only times I am really productive getting somewhere with my phone is staying up till like 4 am because everyone is asleep and I have the time needed to dedicate to all this reading, trying and learning.
Click to expand...
Click to collapse
And I thought I was the only one!
Thanks pal for making my day...
Sent from my SGH-I897 using XDA App
I bricked my phone
distortionist said:
I bricked my phone
Click to expand...
Click to collapse
How? What happened?
I have no Idea what I did wrong, my goal before I started was getting voice dial over bluetooth working for me, its essential to me. It started with trying to install paragon, as per http://www.capfaq.com/w/ROM_Table mentioned above.
I was stock rogers 2.2 so I wiped it clean, and tried the update thing, it didnt work. The only step I skipped was flash to stock and the master clear since it was 2.2 recently and I did the factory wipe. It did not work but I did not brick anything just yet. I figured most people tell you to flash with the one click odin which puts stock at&t on it. I did that and the phone stopped going into download and recovery, it did not stop completely i have gone into download and recovery a few times after that but it was a battle with my phone, since it was booting, I used adt instead which worked like a charm. at&t rom was not happy on my phone, it was going into at&t reboot loops where it would just reboot the bios over and over. after trying and trying it would boot android, i was trying to fix it but each time it restarted the reboot loop would kick off. I could not go to recovery or download mode till i finally got back into the OS and used adt to tell it to go to download mode where i reflashed my stock rogers.
My phone now had at&t logo on boot before rogers, which is not that bad but i had read you can get rid of it, i tried going into download mode with the buttons but didnt try too hard, adt was easier.
I was following these instructions :
http://www.mmacleod.ca/blog/2011/01/removing-the-att-boot-screen-from-a-samsung-captivate/
it wanted me to use odin to flash a file. I used my oden 1.3, i think he says oden 1.0, I didn't think it would make a difference.
Odin started to flash and said fail. I got the screen with "android ! computer", I have been there before when I first ever tried using odin and had to fight with my phone to get to download mode at the time ( this was before at&t ever came close to the phone, i never used odin before so i probably had trouble because of inexperience ).
anyway, this time no matter what I do I cannot go to download mode, I plan on making a jig today if i find someone who sells resistors in this little town.
any help would be appreciated. I dont want to put any more roms on my phone, i just want it to work. I am worried. Ill wait till samsung releases 2.2.1 I just want my phone back to the way it was when I bought it
As the person who write most of the documentation for Team Komin (the developers who make Andromeda), I would say this would be an immense pain. copying all of our information from the website, formatting it into wiki form and then posting it would be very time consuming.
nbs11 said:
As the person who write most of the documentation for Team Komin (the developers who make Andromeda), I would say this would be an immense pain. copying all of our information from the website, formatting it into wiki form and then posting it would be very time consuming.
Click to expand...
Click to collapse
True, but once done, it would be much easier to maintain and navigate. There is going to be a lot of crossposting and people asking for insight and advice.
I'm sure we all understand the search feature in the forum, but to be honest things change topic within a thread, and where someone asks a question that is somewhat unrelated and gets a very good answer, it is not always apparent by poking through page after page of posts to find that nugget of gold. I mean, searching for 'kernel' will give literally thousands of hits. A wiki would be much better in terms of 1. Where you are starting out from 2. what you need to do what you want 3. where to find these things, and 4. maintaining updates and version revisions.
I really appreciate all the work people do here, and I have had to find everything I wanted to know the 'hard' way, but as Android grows in popularity and market percentage, more and more people are going to come here looking for this information. Pobably better to do it sooner than later.
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?
Hi,
I just bought a one s and read through the forums for root, s-off and so on.
Compared to my EVO 3D and Sensation, s-off seems to be less painfull since there are some convenient exploits around that don't need any hardware actions (as the wire trick or soft brick the device).
But I got a little bit concerned about some posts claiming that after s-off the 3g connectivity got lost,
though reading the threads of the latest/greatest custom roms, there's nothing mentioned.
There's one dedicated thread in dev section, but I found no clear statement on how this is to fix.
Some state, that simply changing rom helps to get 3g back.
Some say it's a radio thing.
One member described a method where memory block is manipulated, but this also didn't work for all.
Till now I s-offed each htc phone I owned immediately, but now I'm getting doubts.
I'd appreciate any feedback on this from you experienced ville users out there.
To save you money, time and grief DONT DO IT.
Surely me and most everyone else is thankful that these guys spend time developing and tinkering but I screwed 2 One S,
that is when those disclaimers kick in, and I also looked, not exhaustively, for a skilled JTAG tech/user, the guy I sent it to
said he couldn't figure it out.
Maybe someone here can; most people that JTAG said that doing it to that phone is hard because it has to be taken apart.
Honestly, S-Off would make sense if its a new device to come in the market, as you have noticed, most ROMs and apps just
disappeared and the latest radio put together by someone in here is a 1.35.XX.XX. Since ROMs are limited, and most developers
dont even bother with this device just leave it alone. If flashing the radios is what you want, try the Aroma radio installer for Sense,
if I remember correctly, I think I flashed a radio while running SlimROM and the radio did not reset after reboot.
P.S. If you decide to do it, before hand, find a JTAG tech that has experience with it and can fix this problem, and post it here, please.
I'm still holding on to it in case I find such a person.
sns00 said:
To save you money, time and grief DONT DO IT.
Surely me and most everyone else is thankful that these guys spend time developing and tinkering but I screwed 2 One S,
that is when those disclaimers kick in, and I also looked, not exhaustively, for a skilled JTAG tech/user, the guy I sent it to
said he couldn't figure it out.
Maybe someone here can; most people that JTAG said that doing it to that phone is hard because it has to be taken apart.
Honestly, S-Off would make sense if its a new device to come in the market, as you have noticed, most ROMs and apps just
disappeared and the latest radio put together by someone in here is a 1.35.XX.XX. Since ROMs are limited, and most developers
dont even bother with this device just leave it alone. If flashing the radios is what you want, try the Aroma radio installer for Sense,
if I remember correctly, I think I flashed a radio while running SlimROM and the radio did not reset after reboot.
P.S. If you decide to do it, before hand, find a JTAG tech that has experience with it and can fix this problem, and post it here, please.
I'm still holding on to it in case I find such a person.
Click to expand...
Click to collapse
OP is four month old ...
I never screwed up ANY HTC phone, because they are pretty nice to handle. If the phone fits the prerequisites S-OFF is easy to gain. That users screw their phones by wrong handling is not the dev's fault
Well, good for you:victory:. Since you know so much, why not show everyone else how to properly handle the device?
Did not mentioned methods/names, so I think I did not offended anyone. If software/hardware did not break, there wouldn't
be a disclaimer on the device and on the software.
That the post is 4 months old is irrelevant, we are not the only ones with One S. Next time provide a solution along with criticism.
If this post offended anyone in any way shape or form, complain to a moderator so my post can be erased.
LS.xD said:
OP is four month old ...
I never screwed up ANY HTC phone, because they are pretty nice to handle. If the phone fits the prerequisites S-OFF is easy to gain. That users screw their phones by wrong handling is not the dev's fault
Click to expand...
Click to collapse
sns00 said:
Well, good for you:victory:. Since you know so much, why not show everyone else how to properly handle the device?
Did not mentioned methods/names, so I think I did not offended anyone. If software/hardware did not break, there wouldn't
be a disclaimer on the device and on the software.
That the post is 4 months old is irrelevant, we are not the only ones with One S. Next time provide a solution along with criticism.
If this post offended anyone in any way shape or form, complain to a moderator so my post can be erased.
Click to expand...
Click to collapse
I'm fine with your post I try to help in any case I can. Since today I "bricked" one Samsung phone by following a incorrect guide from another forum, cost me 40$ to repair the bootloader. But that can happen and its totally okay for me and I won't stop modding phones just because of it. For most users S-OFF works without any problem and grant a lot of benefits. So just because you screwed up two One S you can't tell other members to don't set their phone S-OFF as it will probably brick...
Dude, they will do whatever they want with their devices, regardless of what you , me or anyone say.
And the same way you can speak your piece, I can speak my piece, so do not tell me that I can't say this or that. If you don't like what others have to say, there's a number of things you could do instead of reading what I type.
Just sharing an experience that things can go wrong, as it just happened to you. S-Off'ing a phone is something I wouldn't pontificate to a regular user, because if things don't work out I'm not going to pay for a replacement or repair costs. That mod is a "at your own risk" as most other mods are. Do you realize we are a minority, a big chunk of the world don't even install themes on their devices, millions of locked bootloaders, billions of S-On devices and I had nothing to do with it; what are you going to do about that?
S-On works for me, so far, with my M8 GPe, I don't earn a living working with phones or anything related to it, I don't even know how to make a simple app, so what I post is not the gospel, as I assumed it is implied.
"For MOST users S-OFF works..." I rest my case.
LS.xD said:
I'm fine with your post I try to help in any case I can. Since today I "bricked" one Samsung phone by following a incorrect guide from another forum, cost me 40$ to repair the bootloader. But that can happen and its totally okay for me and I won't stop modding phones just because of it. For most users S-OFF works without any problem and grant a lot of benefits. So just because you screwed up two One S you can't tell other members to don't set their phone S-OFF as it will probably brick...
Click to expand...
Click to collapse
sns00 said:
"For MOST users S-OFF works..."
Click to expand...
Click to collapse
Most off the poeple, who set their HTC One S and other HTC devices S-OFF, still enjoy a working phone after this modification.
Better?
I just got one question left.
After you broke one HTC One S, why you did you risk doing (probably the same thing) again?