Related
New Users and folks New to Android:
First let me say, "Been there. Still working on it!" But on to some practical suggestions and comments:
1. If you are new to all this, don't try to move too fast. Read these forums and you will find many messages saying "I don't know what I am doing, but I just finished doing it all and my tablet looks dead! Help?!" If you are new to all this, read these forums for a good while and make sure you understand before you leap. Definition: A "good while" is not minutes to an an hours -- how about a day for experienced Android people and a bunch more for the rest of us.
2. Learn the factory setup first. I can understand some of the early adopters moving too fast because the early gtabs had a mess for software and some of it worked really poorly. But whatever you buy now should flash to OTA (Over the Air Update) 3389 fairly quickly, and it is usable. You can use it to find out where all the settings, bells and whistles are to get what you want done.
3. Go a step at a time. When building computers or working with software, it is always better to work with and prove something before introducing complications. If you are burning a ROM (say CWM -- ClockWorkMod -- for example), don't just install it and move on. When you get it installed, learn it and test the functions and see what is there to be used -- before moving on. If it's not working right or you don't undestand it, don't move ahead -- look for answers or fixes.
4. Read the manual. Learn what you can from the paper and online manuals. There is a Vega site -- I have a thread posted in "Development Forum" which tells where the manual for the Vega tablet it and it does a fair job of introducing the Vegan ROM look and stock features. Viewsonic's G-Tablet site also has this kind of info. And the devs here have put together countless FAQs, guidelines, etc........
5. When things don't go right, take a breath and don't panic. I have had G-tabs for over a month now and I don't honestly know of any that were totally bricked. (I know many have been given up on and sold or returned or ???). I would say that by now most all the iterations of G-Tab failures that can happened have turned up in these Forums. Search and find answers. Ask questions about what you don't understand about the fixes. Then fix it.
6. REMEMBER WHAT THIS PLACE IS!!!! I have read any number of folks who have come here, messed up their tablet and then gotten angry with someone (or all of us) here about it. Remember that this is a place where private individuals are developing alternatives that are on the bleeding edge and sometimes even beyond!! If you are using anything except stock here, you have to assume the risk that all of us assume in trying to do something neat!
Don't fuss. Ask for help.
This post probably has been too long. But I have been developing hardware and software (not Android) since 1979 and I know a bunch about making mistakes!!! Also about preventing mistakes.
I hope the principles I suggest above will help you keep it together and accomplish something great!
Rev
Have you been spying on me?
This describes my situation exactly and I appreciate your input and advice.
I've never used Android, don't even own a smart phone. I'm in the situation of not knowing what I don't know, if that makes sense.
I managed to accidentally add some icons to the home screen and it took me a day and a half to figure out how to remove them.
I've been hesitant to try to make any changes but I realized that I've only been using the tablet to play Angry Birds and do some light surfing. The gtab has so much potential and I have barely scratched the surface.
I will be taking the plunge this weekend with some of the mods that are available, but as you've suggested I need to keep reading. Lots of reading.
Thanks again for the tips,
Neudle
Another thing I would emphasize is when doing something like flashing recovery or loading a new ROM make sure you follow all the instructions. I've had more than one friend come to me asking for help with their phone because they skipped a few steps when flashing a ROM ("Oh, well that didn't seem important so I didn't do it"). I can so far say that with my Nexus One and my Gtab I have never had an issue when I followed the exact steps for flashing/installing.
Also, if something does go wrong, don't go into full out panic, quite often there is a way to recover and a bit of searching or asking nicely for help will have you back up and running. Don't forget, backups are your friend. Before doing anything substantial I always back up my apps and data with Titanium Backup then boot into recovery and do a Nandroid backup.
Different people move at different speeds.
I am brand new to android, brand new to tablets.
Have had this a week.
Days 1-3 "yea ok this 3389 update works"
DAYS 4-5 "LOVE this peformance pack and fixed market"
DAY 6 "lets try vegan 5.1" followed by "I bricked it into a boot loop and none of the fixes worked. Can i take it back" followed by "nv flash is AWESOME, i can recover my gtab from ANY screw up!!!!!
DAY 7 VEGAN 5.1 INSTALLED (and invented my own modified way of flashing/recovery that is not exactly the same as the totorial why identifying which of the steps CANT BE skipped/Altered (WHAT i refer to as the "7-10"))
DAY 8 WHY wont vegan 5.1 acknowledge my new micro sdcard i bought today and do i need to format this or something?
By the way feel free to answer my day 8 issue before i start a new thread.
#8 MicroSd Card
The GTab calls internal storage sdcard and any microsd/microsdhc cards you install sdcard2. Look in your file directory under /sdcard2 or /mnt/sdcard2 and you will see your microsd card. You don't need to format the card first.
This is going to be long, but I have a lot to say.
There's been a LOT of heated debate about TNT Lite 5, lately. This build is based on the vendor's 3991 UAT build. This build is a "1.2" build which means it's a major update from Viewsonic, and it replaces the bootloader. Not only that but the new kernel REQUIRES the new bootloader. We are not certain yet, but Viewsonic is likely to be moving into this direction.
Now, many forum members use clockworkmod. What I have recently learned is that clockworkmod does NOT update the bootloader. In the case of stock 3991 (and TNT Lite 5.0.0) that means that clockworkmod cannot be used as an upgrade tool - IT DOES NOT WORK and, in this case, will actually break your device.
With that in mind it's my opinion that, since clockworkmod has this caveat, then it is a risk and the user community should be made aware of this. If you are willing to take this risk, be aware of the caveat and that, if needed, that you will need to use the nvflash tool to fix your device.
Some of us have been dancing around the issue saying that nvflash is not for non-technical users, and thus TNT Lite 5.0.0 should be pulled completely given the problems with upgrading with clockworkmod. My rebuttal is a simple one -- imo, if a forum user decides to take the risk of using clockworkmod, then they should also understand how to use nvflash as a backout - they go hand in hand and should be a requirement, not an option.
I have heard many complaints about TNT Lite 5 upgrades, but the two most common ones are these:
1. Backing out to stock 3588 breaks recovery (originally clockworkmod).
2. Upgrading to TNT Lite 5.00 by using clockworkmod, by mistake.
Imo, most of the issues we've seen have been clockworkmod related - that's not to say that there have not been other issues, but I believe that the vast majority of them were related to clockworkmod.
I am still under pressure to pull TNT Lite because of the increase in user issues - I think this is the wrong thing to do and I am getting some flak because of my stubbornness. If VS sticks with their new bootloader, this is something that every modder here is going to have to deal with, eventually. But if they backpedal, then I made the wrong choice and we'd need to undo TNTL 5. We just don't know yet.
I think you are right that it maybe something that needs to dealt with sooner or latter as this update could be in anticipation of a even bigger upgrade to 2.3 or 3.0?
It seems from reading threads that not everyone is familiar with reflashing or I hate to say but reading and understanding the steps. The very worse comment I read was "I'll just return my tab and blame insert a cause " What horse hockey.
If they don't know or care to take the time and proceed with caution and then not take responsible for it then they should leave well enough alone.
I actually would like to hear replies (for and against) because maybe I'm looking at this the wrong way. I am stubborn, but if someone gives me a good enough argument I could change my way of thinking. One valid argument is that Viewsonic hasn't even released 1.2 yet, which is a good point. They have to do something very soon (due to Flash) so hopefully by the EO this month we will know what happens.
One of my theories on why they updated the bootloader in this last release was to consolidate development between the GTablet and their newer devices. I don't know if I'm even close to the mark here, it's just a guess. Their kernel is back to an svn #1, so maybe they are using a new development branch.
I vote you not pull it. Like you've said here and in the TNT Lite 5 thread, if someone decides to use a rom they should read the instructions (several times if necessary) before they embark on trying this or any other rom.
If people are throwing caution to the winds and jumping in before they have an understanding of what they are about to do then I say the fault is on their part not yours. You can only do so much hand-holding but in the end the people that use this site and are interested enough to try different roms should know better. Personally, I think you're being more diplomatic than most people about this.
Who knows, since our gTabs have proven to be almost unbrickable maybe people have lost their usual caution?
Vote Don't Pull -- NVFlash Not That Bad...
I vote to keep 5.0.x up.
I have two tablets and had not had to flash one after several months.
But having had to learn nvflash and subsequently doing what I could to help
others -- it's just simply not that bad (at least for the Windows version since
that's what I use.)
Now that a number of us have made sure USB, nvflash and .img files are
available -- and that there are several posts with instructions out there -- I
don't think the nvflash process is any harder than learning the normal
"recovery" process.
If we -- any of us -- are going to play.....then we need to man up
(or woman up, sorry ladies!) and do it right and not complain about it.
Honestly, many times when folks have trouble, it is their own fault.
"Laissez le bon temps roulez" they say during the Mardi Gras celebrations down
here. "Let the good times roll."
Rev
Don't Pull It! Keep it up! We will support you
I have not and will not be flashing your rom at least until it is found out that there is a permanent change coming and the new bootloader is part of that change. I have tried just about every rom I have found for the gtab except tnt 5.0 but that is not because I don't want to screw up flashing it, I am sure with nvflash I would get it back on track, but it is because I have not found the previous releases my preference and I doubt 5.0 would make that change.
By the way no offence to you roebeet, your work and developing here have been beyond superb and are much appreciated. I unfortunately just don't prefer tnt on my tablet. But don't let anyone tell you that you need to remove your work. Your work is not the one borking their tablets they are.
Thanks for all your work Roebeet, even the work you do that I may not use myself
I had zero issues with the upgrade to 5. I thought the instructions for it were clear and concise . I used nvflash to fix my GTab after I noobishly tried to update from Rom Manager when I first started testing the different roms, so nvflash is my friend.
My GTab is running great on 5.0.1 right now, so I hope you will continue to to work on it and not pull it.
Thanks for all your hard work
Jeffrey
Keep it up. at least we have NVflash and its not a real brick. I remember having to update to Danger SPL on my G1, and people were getting real bricks.
IMHO if people are flashing ROMs they need to take a little time to learn what they're doing.
You can't pull it because of ignorance on our part... that defeats the whole point of hacking. Heck, it was the first full rom i installed and guess what? I followed one of the howto threads ignoring your instructions and got to learn all about nvflash. Pull the inaccurate howtos or get their ops to update them.... that'll definitely cut down the failure rate.
I'm glad I bricked my gtab after a whole hour of ownership. I now have a very nice Nvidia Tegra system post bitmap instead of the 10 year old viewsonic birds as a result of it!
The new viewsonic recovery does sd updating if I recall correctly... People can offer kernels and other updates in multiple formats.... They're going to have to if viewsonic goes GA with it.
Keep up the good work!
Sent from my Gingerbread VEGAn-TAB using Tapatalk
I agree with what seems to be the majority so far. Don't pull it.
I have been on this site for quite a while through at least 5 phones (all of them winmo). I do not count myself as an expert and rely heavly on others to develop what have turned out to be excellent ROMs and software and the means by which we can load them on our phones and tablets and other devices.
I have read and read and read and read some more. I have asked questions too. Most of the time becasue the knowledge is too technical for my small mind.
Too many people here expect hand holding and rather than reading, expect, or worse, demand, help when they haven't read the instructions.
To pull your ROM because people can't be bothered to read is to let them win and, in my opinion, dumb down this site.
There are warnings posted everywhere advising of the risks of modding our devices, including bricking the devices. In fact, the people most at risk of bricking are the developers, like you. If you are willing to risk bricking in the name of development, why can't others take responsibility for their actions?
No one points a gun at members' heads and tells them to flash. They join here of their own free will and perform upgrades to their devices in the hopes of making them better. If you are flashing a device, then you are aware that you could brick, or bork, your device.
Moreover, there are countless people here who are more than willing to help unbrick a device. So after bricking, people are forced to learn and read.
Here is a novel idea: Let's take responsibility for our own actions. Not just here, but everywhere.
Keep putting out your ROMs and mods and we can, as adults and willing participants, decide whether to use them or not.
I am now stepping down off the soapbox.
Just saying,
From what I have seen as a daily follower of this forum. It seems more and more users are just getting bolder knowing if something goes wrong, they have nvflash to rescue them from thier "Inevitable" - "User Error".
Heck, I've foolishly done it myself and I had to learn nvflash.
The risks of flashing Custom ROMs is clearly present. You (Roebeet) as Dev should not have to brunt the burden of an inexperienced user when something bad happens. After all, we were all inexperienced at some point or another. And the GTAB makes for a great learning device considering all the tools and support available here to backstep when something does go wrong.
I suggest you don't pull the ROM, but considering the extra complications involved with flashing 5, I could only suggest users clearly have an understanding
of said steps for a successful flash.
Best of Luck dude, and thank you for all your hard work.
It does not go unappreciated here!
T!
I think you should leave it up i myself accidently locked up my tab but i was able to find a resolution and get back up and running there are always issues with new things people just have to relax and go with the flow.
Thanks to everyone, so far! This was how I felt, as well - seems that it's not an easy path, but it's worth it in the end.
I just hope to FSM that Viewsonic doesn't beckpedal on me, because TNT Lite 6 will be as much fun as TNT Lite 5. /sarcasm
I don't see how anyone can complain. Rooting and installing software that is NOT from the manufacturer is at your own risk. I took that risk when I rooted and installed TNT 2.4 and then 4.2.5.
So keep it up and continue with 5.0.1 Let the reader decide if they wish to install the ROM.
With my history, I'll wait till TNT 6.2 before upgrading.
you've been given how to do/don't instructions, you're not to blame. Thank you for your hard work Roebeet;
Ok I am a total noob. .....a danger to mess anything up. ....I was spooked. Because I got this tab to mod and before I received it I studied here and YouTube on how to flash using cwm. .I thought. I was ready then came 5.0 and changed the game I then studied your tutorial and asked questions, alot of them until I felt comfortable I flashed to 5.0 without a hitch but I had nvflash ready to go...my point is that I knew I could Bork this up it was my risk I took it, roebeet has gone way far and above to give us this and help everyone out. Keep 5 up until a major change has to be done if not we know you will be on top of it...Thank you for your efforts!!!!
Signed,
Noob
I don't see any reason to pull it. The instructions and warnings are perfect.. And if you happen to be one of the ones that doesn't read the big giant print first then I suppose you deserve the lesson in learning NVflash. Might actually have a positive outcome by teaching people to read first...
One question I have though has to do with TnT 5 and Calkulins rom. They are both based off of 3991 yet Calkulins rom does not require a special clockwork, or need to be installed from 3588.. How come TnT 5 does? Calkulins rom is very fast, and from my impressions looks almost the same as TnT 5..
Just curious....
I vote to leave it up. I think those having issues are not reading /understanding correctly. I think some of the fear of nvflash is there are several conflicting sets of instructions also slightly vague instructions. Maybe one updated very detailed set of instructions (sticky) will eliminate fear and questions.
F*ck the haters, leave it up. I'm on 5.1 now, read everything and had no issues.
Keep it up, that's my vote. You are taking a calculated risk and that is valid in order to go forward. If VS takes another direction, so be it. The alternative is wait and do nothing and I don’t think you want to do that, but it's your call. We support you one hundred percent.
Thanks for your work I can say so because I'm a v5.∅.! User.
I have been trying to root and ROM my viewsonic gtab for days now ...... and Im at my limit!!!!!!!!!! there are so many "jack off know it alls" and massive amount of conflicting info / directions from hell... step one create a tablet from dust and sticks then load this thingie from this site not the wrong one because it has a temper and may cause your skull to bust open .....
here is the link I have tried at Last (http://forum.xda-developers.com/printthread.php?t=865245) now Xda has been a big help and I'm sure I am so electronically challenged I can't get the simple things right .... my first problem is I can't get the Clkmod8 to the internal "ROOT" folder it copies fine but will not paste into the Root folder (from computer or internet)......... I will also say one gtablet hacker stated not to put it in the root so I am further confused ......... I had it on a sdcard and the gtab would not load "unload clkmod" would not even get to the boot screen it just started like normal sort of? I have lost all patience and would like to have a massive fit ...... which part would be smashing the hell out of all the tech around me filming it and get it on youtube for money donations to pay one of you (*^&^%^%$#%$#^&*^%$#@@) computer savants to install it ......... PLEASE TELL ME HOW TO DO THIS (*^&%[email protected]#@*&@ing crap) so I can get on with my life. I never give up but my gtab may not survive this ..........??? desperate and frazzled
Time to take a break by the sounds of it!
I think many of of us have been in a similar situation. Best thing would be to start over, spend a couple of days reading and researching when you have the time, and then see if anything clicks into place.
I'm sure somebody here will have the same device and will be able to assist in the meantime. Thanks for the amusing post though. You managed to convey your frustration very well!
Hi everyone,
I would like to clear out some points before posting my issue.
1-I have been reading hard brick threads on this device in this forum for 3 days, I am posting my question because I want to get clear answers on what my options are at this point. I have not seen not even 1 solution via Jig, which seems to be the easiest method.
2- The reason I bricked my phone is [most likely] I flashed a kernel that was intended for the N7000 model, although this might not make sense to some of you , for the sake of getting proper help, please hold back on comments that point out how much of a non skilled fan I am and how could I have got caught on such an obvious mistake. Comments like the ones I am describing just wont help so please you might as well keep them to yourselves.
3- Please do not take me as a pedantic person, I just happened to have read enough answers to know that there are highly skilled people who want to help others while some others just love to spend their free time spamming threads. I certainly do not have enough knowledge and skills to perform the jtag method since I cant even solder.
I was trying the JellyBeer rom and I flashed their kernel on TeamWin Recovery, what I do not understand is why did it brick, because I actually realized my mistake soon enough and I performed a restore to my previous rom/kernel, to my understanding, this brick should not have happened in the first place. But when I went ahead and rebooted the phone, it just turned off in the middle of rebooting never to turn on again. Its dead, it wouldnt even charge nor go into download mode or recovery, no vibration no nothing...
Returning the phone to the store is not an option for me as I brought this phone from the states to my country (Dominican Republic ) and is out of warranty.
To me it almost means that I dont have no choice but to keep using my sisters pink motorola that btw is like 10 yrs old until I can wait till some day to have that kind of money again and get a new one. I am leaving the final answer to the experts in this forum.
..If you actually read the whole thing I must thank you, because I know its waaay to long. Counting on you guys.
nicoalmontec said:
Hi everyone,
I would like to clear out some points before posting my issue.
1-I have been reading hard brick threads on this device in this forum for 3 days, I am posting my question because I want to get clear answers on what my options are at this point. I have not seen not even 1 solution via Jig, which seems to be the easiest method.
2- The reason I bricked my phone is [most likely] I flashed a kernel that was intended for the N7000 model, although this might not make sense to some of you , for the sake of getting proper help, please hold back on comments that point out how much of a non skilled fan I am and how could I have got caught on such an obvious mistake. Comments like the ones I am describing just wont help so please you might as well keep them to yourselves.
3- Please do not take me as a pedantic person, I just happened to have read enough answers to know that there are highly skilled people who want to help others while some others just love to spend their free time spamming threads. I certainly do not have enough knowledge and skills to perform the jtag method since I cant even solder.
I was trying the JellyBeer rom and I flashed their kernel on TeamWin Recovery, what I do not understand is why did it brick, because I actually realized my mistake soon enough and I performed a restore to my previous rom/kernel, to my understanding, this brick should not have happened in the first place. But when I went ahead and rebooted the phone, it just turned off in the middle of rebooting never to turn on again. Its dead, it wouldnt even charge nor go into download mode or recovery, no vibration no nothing...
Returning the phone to the store is not an option for me as I brought this phone from the states to my country (Dominican Republic ) and is out of warranty.
To me it almost means that I dont have no choice but to keep using my sisters pink motorola that btw is like 10 yrs old until I can wait till some day to have that kind of money again and get a new one. I am leaving the final answer to the experts in this forum.
..If you actually read the whole thing I must thank you, because I know its waaay to long. Counting on you guys.
Click to expand...
Click to collapse
Hello, a week ago I was trying to restore my phone back to the stock rom, it is a Samsung Galaxy i727, and now is dead or HardBrick, I´m from Dominican Republic, searching in the internet I found a local Mobile Repair Center offering the Jtag service in just 24 hour my phone is back, their name is ALUMUN, if you are in Dominican Republic they are the best, you can find them in google as ALUMUN
I agree with you, we need help not lip service. I too bricked my phone, the site I got my roms added the galaxy 2 rom to the site not thinking it would be a bad thing to add it since they added it to the group of roms I could download for my phone, well that was the wrong thing to do!! I don't live in the Dominican Republic so I need to fix this myself.....HELP PLEASE!! Thanks guys
trayluv73 said:
I agree with you, we need help not lip service. I too bricked my phone, the site I got my roms added the galaxy 2 rom to the site not thinking it would be a bad thing to add it since they added it to the group of roms I could download for my phone, well that was the wrong thing to do!! I don't live in the Dominican Republic so I need to fix this myself.....HELP PLEASE!! Thanks guys
Click to expand...
Click to collapse
Hopefully this will help http://forum.xda-developers.com/showthread.php?t=2083353
Can someone with good experiance, possible write up a 'doc', or start a thread on what n00bs can or maybe should do with various things once they for instance root them etc.? (In this instance for the gt-p5113 specifically, if you would.) sure it will be opinion, etc. but for instance I just rooted my samsung galaxy tab 2 10.1 gt-p5113 (by the excellent docs here btw, I think they worked flawlessly.) But I just do not know what to do next.....it is freshly rooted.
and by next I do not mean things to use and do WITH it....I know somewhat some of the things I want to do there, but for instance making a backup...probably a good idea, but I do not really know the best way to go about it....or installing super user...it was mentioned, but I have no clue really how, or if they were talking about another device or needing to or not. or installing a firewall or some other type of protection. I don;t know...I guess I am expecting someone to do some thinking for me, and maybe that isn;t always the best thing to do, but it'd sure help me thats for sure, because I'm sorta weary at this point and not yet comfortable messing with it, sorta and could use some verification/validation of thinking with less of the fear of bricking my tech. I literally just rooted it like 5 minutes ago.
RS-232D said:
Can someone with good experiance, possible write up a 'doc', or start a thread on what n00bs can or maybe should do with various things once they for instance root them etc.? (In this instance for the gt-p5113 specifically, if you would.) sure it will be opinion, etc. but for instance I just rooted my samsung galaxy tab 2 10.1 gt-p5113 (by the excellent docs here btw, I think they worked flawlessly.) But I just do not know what to do next.....it is freshly rooted.
and by next I do not mean things to use and do WITH it....I know somewhat some of the things I want to do there, but for instance making a backup...probably a good idea, but I do not really know the best way to go about it....or installing super user...it was mentioned, but I have no clue really how, or if they were talking about another device or needing to or not. or installing a firewall or some other type of protection. I don;t know...I guess I am expecting someone to do some thinking for me, and maybe that isn;t always the best thing to do, but it'd sure help me thats for sure, because I'm sorta weary at this point and not yet comfortable messing with it, sorta and could use some verification/validation of thinking with less of the fear of bricking my tech. I literally just rooted it like 5 minutes ago.
Click to expand...
Click to collapse
Did the root method install a custom recovery?
RS-232D said:
I literally just rooted it like 5 minutes ago.
Click to expand...
Click to collapse
It will take a little more than 5 minutes to do your research.
My experience over the years has taught me that doing your own research is far more rewarding than having someone else do it for you and hand everything to you on a plate.
You can take it at your own pace, and you will get a far more rewarding experience of your tech if you put the effort in. Not only will you learn more, but you will discover other things as you search for the answers. This is truly mind expanding stuff, but it requires effort.
And that's the point of Android I find - if you don't want to make the effort and you want someone to do everything for you then buy a product from Apple. They are the masters at making things easy...as long as you are prepared to do things their way, and not expect too much from your device.
Android is flexible and configurable, but that means thinking, exploring and discovering things yourself.
If you're not comfortable then don't do anything. Read, read and read some more until you get comfortable - then act. That is the safest way to avoid problems as well as rewarding you with knowledge and understanding.
Good luck in your quest.
acefsw said:
Did the root method install a custom recovery?
Click to expand...
Click to collapse
Uhm.....uhm......I am not thinking so.....I used a method which used Odin....I started in I think recovery mode, by holding power and volume up, then switched to volume down, and selected a recovery file that I had put on my Sdram card, it did it's thing, and now I notice I have super user capability. I then installed supersu and quickboot . And that is where I am at. Pretty much.
Mr.Anderson....ya.....I hear you, and have run with the rtfm crowd enough to grasp the concept..... but perhaps that is why the other guy after joining Iin 2012, has a thank you meter of 16 and you have one of 6 after joining 4 years ago? I am not trying to really skip the 10 billion posts of reading time exactly, or learning on my own. What I am trying to do is avoid problems I might from more experianced people who wish to share, after looking and not finding a specific post that I am sure is up to date, thag answers the issue. Frankly, I'd like for there to be a sticky on it specifically for this model. I''ll write one myself and submit it once I know enough to do it probably......but I promise, if you do not wish to help me, I won't think any less of you, or blame you. I am sure you have gained all your knowledge and earned it on your own, or if not, on this subject specifically, it wasn't any help from me, so neither you nor anyone else owe me anything.
RS-232D said:
Uhm.....uhm......I am not thinking so.....I used a method which used Odin....I started in I think recovery mode, by holding power and volume up, then switched to volume down, and selected a recovery file that I had put on my Sdram card, it did it's thing, and now I notice I have super user capability. I then installed supersu and quickboot . And that is where I am at. Pretty much.
Mr.Anderson....ya.....I hear you, and have run with the rtfm crowd enough to grasp the concept..... but perhaps that is why the other guy after joining Iin 2012, has a thank you meter of 16 and you have one of 6 after joining 4 years ago? I am not trying to really skip the 10 billion posts of reading time exactly, or learning on my own. What I am trying to do is avoid problems I might from more experianced people who wish to share, after looking and not finding a specific post that I am sure is up to date, thag answers the issue. Frankly, I'd like for there to be a sticky on it specifically for this model. I''ll write one myself and submit it once I know enough to do it probably......but I promise, if you do not wish to help me, I won't think any less of you, or blame you. I am sure you have gained all your knowledge and earned it on your own, or if not, on this subject specifically, it wasn't any help from me, so neither you nor anyone else owe me anything.
Click to expand...
Click to collapse
Ok, go in to recovery mode volume up+power and see what it loads, if it is cwm, then you can select backup, I backup to my extsd because it takes up a lot of space on internal sd, then reboot. If not, then search for install cwm on the forum. I can explain later, but am on vacation visiting the parents, so I can't guarantee how timely my response will be.