I (rather, my 8-year-old daughter) have a had a Viewsonic G Tablet for a while, and would like to install a new ROM in it, in part because I suspect that the tablet may have been infested by malware. My goals are to be able to root the tablet, and to have full access to the Google market place (Google Play Store, as I believe it is called now.) After doing some reading on how to tackle this, I have noticed that, if anything, there is an excess of information, potential dependencies on the software version currently in the tablet - and many ways in which one can end up with a brick.
I would be grateful for recommendations on how to proceed. In particular, what is the ROM that members in this forum would recommend for me to use? I would like to minimize the probability to end up with a brick, which would seem to imply that relative installation simplicity is a factor. Also, do I need to reset to factory default before attempting to install a new ROM? Would this be advisable, or may be even necessary, in order to make sure to get rid of any malware potentially in place? The tablet is currently running the latest software update (1.2-5699) from Viewsonic, installed shortly after 01/31/12.
Addendum
newton1729 said:
I (rather, my 8-year-old daughter) have a had a Viewsonic G Tablet for a while, and would like to install a new ROM in it, in part because I suspect that the tablet may have been infested by malware. My goals are to be able to root the tablet, and to have full access to the Google market place (Google Play Store, as I believe it is called now.) After doing some reading on how to tackle this, I have noticed that, if anything, there is an excess of information, potential dependencies on the software version currently in the tablet - and many ways in which one can end up with a brick.
I would be grateful for recommendations on how to proceed. In particular, what is the ROM that members in this forum would recommend for me to use? I would like to minimize the probability to end up with a brick, which would seem to imply that relative installation simplicity is a factor. Also, do I need to reset to factory default before attempting to install a new ROM? Would this be advisable, or may be even necessary, in order to make sure to get rid of any malware potentially in place? The tablet is currently running the latest software update (1.2-5699) from Viewsonic, installed shortly after 01/31/12.
Click to expand...
Click to collapse
I forgot to add two other desirable features: The ROM should support Skype with video, and should be optimized for video and game playing; that's what my daughter uses it for.
I doubt you have malware that couldn't be easily removed. But rooting/romming will make the device far more useful.
That sai, for best stability and compatibility, I would suggest a Froyo rom, as the other kernels aren't quite there. Particularly for Skype and such. VeganTab is the best one I have seen, but I also like Beasty Clemsyn, and that is what I am using today.
If you want to tinker more, the new Smoother jb/ics are great, but not perfect. I plan to get back to those in the near future, as they are still being tweaked.
Sent from my SCH-I535 using xda app-developers app
Thanks for your feedback
schwinn8 said:
I doubt you have malware that couldn't be easily removed. But rooting/romming will make the device far more useful.
That sai, for best stability and compatibility, I would suggest a Froyo rom, as the other kernels aren't quite there. Particularly for Skype and such. VeganTab is the best one I have seen, but I also like Beasty Clemsyn, and that is what I am using today.
If you want to tinker more, the new Smoother jb/ics are great, but not perfect. I plan to get back to those in the near future, as they are still being tweaked.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks so much for your recommendations. I have been looking into the description given in
http://forum.xda-developers.com/showthread.php?t=865245
for installing a new ROM. Do you know if this is up to date? I am a bit concerned about the comments in the link for VeganTab having to do with incompatibilities between the bootloader in recent versions of the Viewsonic ROM and the bootloader mentioned in the link above. I just need some reassurance from those who know better that, by following the steps in the link, I am not going to brick the tablet.
I haven't heard of anyone really bricking the tablet. Some roms have caused an SOD (sleep of death) but after the battery dies out, it resets and can be booted back up. Or you can press the internal reset button. Most of these happen on the reverse engineered kernel for newer roms.
Get yourself comfortable with the nvflash routine (it's pretty easy) and keep a backup original rom on your computer, in case you need it. Nvflash can get you out of pretty much any issue.
VeganTab is very old as you can see. If you're on the same bootloader as required for that, then go ahead. If not, then you're probably on 1.2,which is why I switched to Beasty / Clemsyn (it's 1.2bl capable iirc).
Sent from my SCH-I535 using xda app-developers app
Thanks
schwinn8 said:
I haven't heard of anyone really bricking the tablet. Some roms have caused an SOD (sleep of death) but after the battery dies out, it resets and can be booted back up. Or you can press the internal reset button. Most of these happen on the reverse engineered kernel for newer roms.
Get yourself comfortable with the nvflash routine (it's pretty easy) and keep a backup original rom on your computer, in case you need it. Nvflash can get you out of pretty much any issue.
VeganTab is very old as you can see. If you're on the same bootloader as required for that, then go ahead. If not, then you're probably on 1.2,which is why I switched to Beasty / Clemsyn (it's 1.2bl capable iirc).
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks very much for your comments.
Related
Well my work just got a bunch of iPhones and the CEO got one of the. He had the Samsung before so I got it as an upgrade over my crackberry.
Now I really want to install a custom rom/kernel on the phone but I am hesitating because its really not my phone and my work owns it.
What do you guys think should I stick with stock or should I root the phone and install a rom?
Stock. There's nothing like explaining to the boss how you f'd up company equipment.
I dont know if one should/should not install custom roms on a work phone, as I don't have one. But I can tell you that if you do decide to root and install one of the custom roms, it's not that hard to unroot and go back to stock later on when you need to return the phone. There are several threads here that will guide you through the process too.
jenisiz said:
Stock. There's nothing like explaining to the boss how you f'd up company equipment.
Click to expand...
Click to collapse
I guess your right I just hate being stuck on 2.1 when I know I can have a nice Froyo install. It's just so hard not to do because I have done it with all my other devices.
dsf767 said:
I guess your right I just hate being stuck on 2.1 when I know I can have a nice Froyo install. It's just so hard not to do because I have done it with all my other devices.
Click to expand...
Click to collapse
I hear you...but who's to say he won't ask for it out the blue someday?
Idk, at this point, the fascinate is practically impossible to brick. You also say you have experience rooting and customizing other phones, correct? I say go for it. The only reason I could see not to is due to security issues. Work passwords and etc.. I really don't know too much about all of that tho.
Sent from my SCH-I500 using XDA Premium App
I have a rooted android work phone. All you have to do is read what ppl are saying about the roms and FOLLOW DIRECTIONS and youll be fine.
dsf767 said:
Well my work just got a bunch of iPhones and the CEO got one of the. He had the Samsung before so I got it as an upgrade over my crackberry.
Now I really want to install a custom rom/kernel on the phone but I am hesitating because its really not my phone and my work owns it.
What do you guys think should I stick with stock or should I root the phone and install a rom?
Click to expand...
Click to collapse
Used my fascinating voodoo powers
I seriously discourage doing anything to it. It's not yours for one, and (no disrespect to the devs ofcourse, their work is amazing) there really isnt anything spectacular for this phone at the moment due to samsung's failure to provide any source code. To be more specific... our kernels suck.
And oh yea this shouldve been in the Q&A section so be ready for ashasaur to move this thread. (hes really good at doing that )
Depends on your comfort level, and of course, your corporate policies.
Sent from my SCH-I500 using XDA Premium App
I would say root your phone at the most. It's fairly easy to recover from just rooting, but flashing roms/kernels/modems is much more risky. At least with rooting, you could fairly easily freeze the bloat with TiBu and have a more functional phone. Thawing everything and un-rooting would have you a stock phone back fairly quickly, and you could also still receive OTA updates as well.
I say go for it if anything goes wrong all you have to do is odin back to stock it removes everything its as simple as plugging the phone in load the stock file and click start I've done this countless times
We pick our work cell phones specifically because of the potential customization we can do. I hate being stuck with some company's version of what they think will be useful to me in my job. I can Odin this phone back to stock/factory defaults in less than 5 minutes if need be, so customizing this phone and expanding its abilities, and recovering from those customizations quickly, were what attracted me to it.
Android is Android, whether it's Samsung's stock version or one of the dev's version of it. Your phone is still going to perform the same tasks you need it to for your job. As long as you are both competent with the technologies involved and confident in your ability to restore to stock, I don't see why you should hesitate from exploring the options that are out there, especially when Froyo source drops and we see an explosion of dev-created customizations/enhancements.
Really? If your asking for advice on whether to mess with a business owned phone, it makes me wonder are you the ceo's mail clerk?
SuperClean2.9.1vNitroDark
Personally for a work phone, I'd update it for better usage in my work.
Increasing battery life usage duration.
Less irritating buggy glitches.
Removing the idiotic TW/BING/VZW craps. (too many add-on hacks from google default causing reliability and dependability problems)
Adding Backup and Restore nandroid for possible failures and migrations.
I suggest DJ05 + SuperClean + Blaze v2.3.1R2.
Hi, didn't want to clutter the "bad news" thread nontechnical noob questions. If the tablet won't boot from SD
1) Will it still possibly be rootable where I could side load apps? I could live with the stock ROM if I could sideload apks, maybe.
2) Am I right to assume even if it is rootable where I can add apps, it is much more likely that I could brick it somehow?
Dang, just really crappy timing. I actually bought gift cards to get it (so I could get some cash-back deals). I can't return the cards. I guess if this thing isn't worth it, I can use them to get a refurb color.
Very surprised and disappointed they went this route (if they really did).
Damn
Same here, I could live with side-loading. But I think it's a bit early to write off bootable SD. Hopefully it's here relatively soon as I'd like to leave the stock experience in place for family members.
As an aside, I've got the original Nook Color (rooted of course), as well as the Transformer. Even without the benefit of ICS, I found that I still resorted to grabbing the NC for my bedtime reading (Google Reader and articles in RIL, rather than actual books). 7" is perfect, 10" a bit unwieldy for me.
I picked up the NT today and am very happy I did. It's a nail in the coffin for the Transformer, gonna sell it as the NT will meet all my needs. I'm saying this based on the stock experience with the expectation that we'll have ROMs at some point.
But soon enough we'll have a) root and b) ICS on the NT. It's gonna be sweet!
Well, correct me if I'm wrong, but I'm yet to see an Android device that XDA geniouses couldn't root.
Including the crazy-ass encrypted Craporola devices.
Rooting might be doable, but if the bootloader is encrypted, then installing a custom ROM like CM7 might be out of the question.
Case and point: look at how much agony the owner of the Motorola Milestone (the GSM version of the Droid) went through. Far as i know, they just got the official Froyo ROM within last few month, and most likely won't get GB, ever.
DarkDvr said:
Well, correct me if I'm wrong, but I'm yet to see an Android device that XDA geniouses couldn't root.
Including the crazy-ass encrypted Craporola devices.
Click to expand...
Click to collapse
Yeah i figured as much but wasn't sure if there was something out there I wasn't aware of. I'm using an Atrix. Despite Motorola's best efforts, the community eventually got into this thing.
gordon1hd1 said:
Rooting might be doable, but if the bootloader is encrypted, then installing a custom ROM like CM7 might be out of the question.
Case and point: look at how much agony the owner of the Motorola Milestone (the GSM version of the Droid) went through. Far as i know, they just got the official Froyo ROM within last few month, and most likely won't get GB, ever.
Click to expand...
Click to collapse
That would suck but I think I could live with it. I just noticed that some of the nook apps are the tablet version rather than the phone versions. Evernote and Netflix, for example. Root and sideloading would probably suffice, although B&N would lose some goodwill.
Sent from my MB860 using XDA Premium App
I could honestly care less about custom roms or anything like that. I'm fine with the NT stock experience.
But sideloading would be a very very good thing, just so I can get the few apps I'd like to use onto the thing. I'm only gonna use it to consume media- but I'd like to decide which apps I use to do that.
Rooting will get most users far, but compare to a full blown CM7 rom, there still many short coming with just root.
Example:
1. Tablet soft buttons, the CM7 tablet soft key are vital in making a lot of side loaded application work in NC.
2. Custom keyboard. one of my favorite app on NC is the thumb keyboard, which make typing on the NC in landscape orientation feel natural. With Root, the user can install the keyboard, but won't be able to enable the keyboard, since B&N remove some of the menus settings.
3. Honeycomb and ICS, with the source code for ICS just came out, CM9 is on the horizon, without unlocking the bootloader, NT won't get a taste of either.
So Root is a great start, but for many android hackers and purist, it is not enough.
1. Tablet soft buttons, the CM7 tablet soft key are vital in making a lot of side loaded application work in NC.
I have button savior on my manually rooted NC. Works fine. Am I missing something?
2. Custom keyboard. one of my favorite app on NC is the thumb keyboard, which make typing on the NC in landscape orientation feel natural. With Root, the user can install the keyboard, but won't be able to enable the keyboard, since B&N remove some of the menus settings.
I got the Palm input keyboard working on my rooted NC. Worked great. I forget what I swapped it out for, but it wasn't a problem - you just have to tell the device that your preferred keyboard just happens to be named the same as its preferred keyboard and lives in the same place.
3. Honeycomb and ICS, with the source code for ICS just came out, CM9 is on the horizon, without unlocking the bootloader, NT won't get a taste of either.
This may be for the best.
I'm looking at Honeycomb now on a 10 incher, and I'm not as happy with what I'm seeing as I'd hoped. ADB is more challenging, and putting files on the device via mass storage device is right out, which means a lot of my tools for managing content on it are gone, too - manually copy over stuff that Calibre used to just take care of? Bleargh.
Honeycomb pretty much requires your real, fast computer talk to your honeycomb device, aka a ****ty slow computer, over a serial link as if it were a peer, rather than just being able to get the storage and write files to it.
And if you use linux, your good, fast computer can't even talk to the ****ty, slow one that google's deliivered because they didn't bothered to warn anyone about this far enough ahead of time for the linux folks to really get working on trying to port over that stupid set of media player commands. Who knew that anyone would all of a sudden decide they were going to pronounce a brain-dead media player communications interface as workable?
Once you unplug and being passively consuming your pr0n again, the tablet's all good and pretty.
http://soledadpenades.com/2011/06/12/honeycomb-mtp-and-linux/
Not to second guess anyone here, but there always OTHER ways of doing things. Witness the Droid X where even with an encrypted bootloader an exploit was found called 2nd Init (http://cvpcs.org/blog/2011-06-14/2nd-init._what_it_is_and_how_it_works) which allowed the Droid X to get custom roms (albeit with the stock kernel) such as CM7 and MIUI.
jhanford said:
Not to second guess anyone here, but there always OTHER ways of doing things. Witness the Droid X where even with an encrypted bootloader an exploit was found called 2nd Init (http://cvpcs.org/blog/2011-06-14/2nd-init._what_it_is_and_how_it_works) which allowed the Droid X to get custom roms (albeit with the stock kernel) such as CM7 and MIUI.
Click to expand...
Click to collapse
I truly hope that it won't be such an involved process for us, but still... very cool to read what the genius devs put together as a workaround on other devices. We just need to hope that they jump on the Nook Tablet like they did the NC.
jhanford said:
Not to second guess anyone here, but there always OTHER ways of doing things. Witness the Droid X where even with an encrypted bootloader an exploit was found called 2nd Init (http://cvpcs.org/blog/2011-06-14/2nd-init._what_it_is_and_how_it_works) which allowed the Droid X to get custom roms (albeit with the stock kernel) such as CM7 and MIUI.
Click to expand...
Click to collapse
I have a Defy, and it need too 2ndInit to start custom rom like CM7/MIUI.
I hope that NT will be no boot-locked, but if it's the sadly truth I think that port 2ndInit will be not too much hard.
well we already figured out how to side load apps. they dont pop up in NT's GUI, but with 2 buttons you can launch Go Launcher and within there you can see everything you installed.
I would actual prefer to have the stock Rom, just rooted. I had CM 7.1 on my NC but removed it because I actually do use the NC as bookreader and that would the primary use for a NT. I have a TF and soon a TF Prime for the full tablet experience, which IMHO really needs a 10 inch or bigger screen.
Hi All,
I'm currently running my Prime on the .21 with root (had it rooted on an earlier version) and I'm curious about installing a custom rom or starting to experiment a little more.. however, with all the topic here about issues and/or bricking I'm seriously scared to make any of these changes.
So my question is, what do I do, or shouldn't I ever do to ensure my Prime is not bricked ?
Thanks
DirtyWizard said:
Hi All,
I'm currently running my Prime on the .21 with root (had it rooted on an earlier version) and I'm curious about installing a custom rom or starting to experiment a little more.. however, with all the topic here about issues and/or bricking I'm seriously scared to make any of these changes.
So my question is, what do I do, or shouldn't I ever do to ensure my Prime is not bricked ?
Thanks
Click to expand...
Click to collapse
First off, I would suggest reading the forums over at xda. They have a lot of good information such as this http://forum.xda-developers.com/showthread.php?t=1515004 helpfully titled " [GUIDE] The DO's and DON'T's with your unlocked Prime"
Seriously, if you don't read things carefully before embarking on a flash fest, you WILL brick your device.
[Q] Howto prevent bricking ?
Click to expand...
Click to collapse
Don't unlock your Prime's bootloader.
Abstinence is the best protection, its that simple
I know people really like to tinker with their devices and that the fact you can tinker is part of what attracts people to Android. However I would look long and hard at all of the ROMs available and see if they really offer any benefits for you over the basically stock Android 4.x that the Transformer Prime ships with.
If you are looking to install a custom ROM on the hope it will fix a problem you are having with the Prime I would honestly recommend RMAing the Prime in order to deal with your problem in a manner that doesn't void your warranty and that doesn't have the risk of bricking your Prime.
Just for reference:
No ROM will ever make the GPS really work for navigation. It is not a software problem, so you cannot really solve it with software.
No ROM will ever significantly improve really crappy WiFi. WiFi either works or doesn't and for the majority of people with problems the problems are related to the physical WiFi antennae. RMAing the prime and have Asus fix the antennae and their connections has a far greater chance of improving your WiFi reception than any ROM.
I mean if you just want to install ROMs in order to play around and that is one of the primary reasons you bought the Prime, go for it. However for most people losing out on your warranty isn't a great trade-off for the benefits a few custom ROMs might bring.
Thank you both for the response. I had seen the initial topic but there is a lot of confusing information out there.. some people claim bricking due to the latest .21 update without ever having unlocked the bootloader, ... so that is the reason I started this topic / question.
Now, the response from almightywhacko, is basically along the same thinking pattern as myself.. I don't use GPS and the Wifi reception is "ok".. not great but workable (for now)... So basically besides attempting to improve the Wifi connectivity, I don't have a reason to go for a custom rom (at the moment).
DirtyWizard said:
Thank you both for the response. I had seen the initial topic but there is a lot of confusing information out there.. some people claim bricking due to the latest .21 update without ever having unlocked the bootloader, ... so that is the reason I started this topic / question.
Now, the response from almightywhacko, is basically along the same thinking pattern as myself.. I don't use GPS and the Wifi reception is "ok".. not great but workable (for now)... So basically besides attempting to improve the Wifi connectivity, I don't have a reason to go for a custom rom (at the moment).
Click to expand...
Click to collapse
I am suspect of the actions that people have taken that have lead to their bricked Prime when they haven't unlocked. People "claim" to have done nothing to their Prime however that is only their claim. The claim might be true or not, I can't evaluate it since I wasn't looking over their shoulders however some of the people who ask about unlocking bootloaders and rooting are also the people reporting bricked Primes after installing an OTA. That probably isn't a coincidence
If your Prime is 100% stock and not rooted, pretty much the only way you can brick it is to interrupt an OTA update that is in progress.
Interrupting an OTA can happen if you hit the rest button while updating, holding down the power button, plugging and unplugging the Prime during the update, etc. Basically while the Prime is updating, set it down and let it finish. Don't touch it.
If you are rooted, deleting certain system apps using Titanium Backup or a similar program and then trying to install an OTA can cause the OTA to fail. Basically if a system app has an update that is packed into the OTA, the OTA can hang if that app has been removed which will eventually cause the update to fail.
If you want to take the OTA update, it is better to not delete system apps. If you are rooted and have deleted system apps, wait until a rooted version of the update is released by an XDA member.
The biggest thing to avoid bricking your prime is to follow directions!
I can't say it enough. Follow them step by step and reread them to make sure. Almost every problem is people not following the rules.
Sent from my ADR6300 using xda premium
Well, I also suspected users not really knowing what they have done prior to the ota update.. on the other hand I foresee quite some progress in the future in the custom roms... My android phone also has a custom rom and I couldn't miss some of the added features..but "playing" with a 600 € device potentially reducing it to an expensive coaster is not something I'm willing to do
Sent from my Transformer Prime TF201 using XDA
I am one of the original WOOT buyers from ancient history. Tried Brilliant Corners, and Flashback. Currently running Clemsin's Beastly because it's fast and everything works. But some newer apps, etc, require later Android ROMs. I have read, and reread, the instructions for Smoother Bean but would like someone to take the time and do a cook book step by step for me.
I am on BL2. I have Clockwork MOD v3.0.2.8 installed. Do I have to go back to the POS Viewsonic ROM? Or can I go and do the DRH nvflash for 350 and then install SmoothBean?
I want to do it right as I got in LOTS of trouble before with the dreaded APX bootloop. Don't want to go through that again. I don't need a "hit this key after.." type instruction, just what procedures are necessary and in what order. And I'm unclear about the update under the instructions for the inverted playstore. Is that required and what exactly is it?
Thanks in advance for the help. This Gtablet is still a nice unit and the developers have done remarkable stuff.
It's quite simple, and well detailed in the op there. That said, it's using the DRH apx flash first, then get into recovery (no need to boot through), then wipe, and I choose to wipe /system and /data manually, do the formats as directed, then use recovery usb to load in the new rom and apply it.
Sent from my SCH-I535 using xda app-developers app
schwinn8 said:
It's quite simple, and well detailed in the op there. That said, it's using the DRH apx flash first, then get into recovery (no need to boot through), then wipe, and I choose to wipe /system and /data manually, do the formats as directed, then use recovery usb to load in the new rom and apply it.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Well, yes and no on the quite simple. I may be dense but I don't understand the bit just under the inverted play store in the OP. Is it just about a replacement for the birds? having read through the threads, there are those who don't have the sweet success that the dev got with his Gtab. He admits that it works on his. And others, well, nada. I was hoping to find out what is truly necessary, what is ' a good thing to try' and what is just useless to do when going to Smoother Bean. I am going to try it, just wanted to know what steps give the best chance of a decent install w/o having to tweak glitches after.... For instance, does one get a better result going all the way back to a Viewsonic ROM? Or is it just a waste of time?
The drh nvflash is required. This eliminates any need for considering the "original Viewsonic rom".
The problems people are running into are simply due to the continued tweaking happening. I have used the rom, and it works quite well, but slowed down for me, which is why I went back to Beasty. I have read that this issue has been resolved, but due to the flurry of tweaks still going on, I am waiting for a bit longer.
Bottom line, remember that these are all hacks. You may or may not have any issues, and the issues are not even fully understood. But the process is well layed out in the op. I added the extra wipes, that's all. If you have specific questions, feel free to ask, but I don't know what more to tell you.
Sent from my SCH-I535 using xda app-developers app
tincansailor said:
Well, yes and no on the quite simple. I may be dense but I don't understand the bit just under the inverted play store in the OP. Is it just about a replacement for the birds? having read through the threads, there are those who don't have the sweet success that the dev got with his Gtab. He admits that it works on his. And others, well, nada. I was hoping to find out what is truly necessary, what is ' a good thing to try' and what is just useless to do when going to Smoother Bean. I am going to try it, just wanted to know what steps give the best chance of a decent install w/o having to tweak glitches after.... For instance, does one get a better result going all the way back to a Viewsonic ROM? Or is it just a waste of time?
Click to expand...
Click to collapse
Just flash following the steps in the OP. I went from a 1.1 rom to this, it's simple. And honestly, the late November version is very good - the pace of revs seems to have slowed a bit
Video Instructions, better late than never
tincansailor said:
I am one of the original WOOT buyers from ancient history. Tried Brilliant Corners, and Flashback. Currently running Clemsin's Beastly because it's fast and everything works. But some newer apps, etc, require later Android ROMs. I have read, and reread, the instructions for Smoother Bean but would like someone to take the time and do a cook book step by step for me.
...
Click to expand...
Click to collapse
I am also a Woot buyer, and still using my gTab daily. I realize I'm posting 6 months after you did, but just in case... I found Ray Waldo's video helpful when taking the plunge from Froyo (I was running pershoot's overclockable kernel). Being a n00b, I can't post links here, but search for ray waldo jelly bean install video and you will find it on youtube and his site.
HTH.
Go to raywaldo.com site using http://raywaldo.com/2012/11/new-life-for-the-g-tablet/ for detailed instructions on installing Smoother bean v1.5.2
Sent from GTablet Smoother Bean v1.5.2
Wanted to get an idea from the group on options here:
Have seen quite a few postings on the issues with JB on the TF201 and how limited that makes things. Currently have a Gnexus phone running cyanogenmod 10 and really like it; started wondering what interesting features that rom might bring to the TF201.
So, first question is can any roms such as the CY10 even be installed given the JB limitations?
If so, are the benefits gained from custom roms worth whatever headaches are involved with the currently upgrade processes.
I am heading out on a deployment in about 6 days so access to pull down upgrade files will obviously be limited. Won't be returning to the US until the Sept timeframe, so definitely a needed decision on if anything can/should be done for improvements (to play with of course!) during the deployment.
I have the weekend to tinker but wanted to ask whether I'm better off just keeping the device as-is or putting in the time for possible upgrade steps.
Thanks!
militarymedic23 said:
Wanted to get an idea from the group on options here:
Have seen quite a few postings on the issues with JB on the TF201 and how limited that makes things. Currently have a Gnexus phone running cyanogenmod 10 and really like it; started wondering what interesting features that rom might bring to the TF201.
So, first question is can any roms such as the CY10 even be installed given the JB limitations?
If so, are the benefits gained from custom roms worth whatever headaches are involved with the currently upgrade processes.
I am heading out on a deployment in about 6 days so access to pull down upgrade files will obviously be limited. Won't be returning to the US until the Sept timeframe, so definitely a needed decision on if anything can/should be done for improvements (to play with of course!) during the deployment.
I have the weekend to tinker but wanted to ask whether I'm better off just keeping the device as-is or putting in the time for possible upgrade steps.
Thanks!
Click to expand...
Click to collapse
Hey militarymedic23,
There are definitely ROMs that can be installed currently, however most are unofficial ports from either a different device (TF700) or ported to the JellyBean bootloader (current OFFICIAL CM10 runs on ICS bootloader and will fail on updated JellyBean bootloader).
After experimenting with unofficial ports of CM10 (4.1), CM10.1 and JellyBeer (Android 4.2), I honestly recommend sticking to stock JellyBean as of right now. These ROMs, although offering a lot of customizations, are not "done" yet. There are many little bugs on each (ex: JellyBeer rom doesn't show dock battery, uses mobile mode aka. single pane, for play store, etc etc.) and although by itself doesn't take too much away from the experience, does tend to bother me over time.
It is these small bugs that I wouldn't recommend changing over from stock. A lot of the Asus features also missing (I really enjoy being able to change CPU modes from navigation menu-- which is a missing feature, for example). Also, assuming you already upgraded to the JellyBean bootloader, official CM10 ports DO NOT work, so you're getting unofficial ports.
Overall, I don't mind stock, and as long as you ROOT, you can go ahead and remove all the ASUS bloatware to get a pretty clean tablet experience. I also didn't find any performance enhancements after upgrading from stock (which I expected). I can include some pictures of stock vs unofficial CM10 benchmarks upon request.
My personal recommendation, due to the fact you will be deployed (so not sure if you'll have all the time to always flash the newest upgrades) is to continue with stock for now. The last thing you want is to be stuck with a buggy firmware without any way to update and restore. This way you can still receive OTA updates from Asus, which from my experience has been pretty timely (If you are out of the country, using an app like Hotspot Shield may help you get an OTA update if it isn't accessible from your current region).
Hope this helps.
Hi trophx, thanks for the input on this. I do agree that overall the stock software isn't actually that bad. In comparison to my phone, CM10 does give a nice assortment of features over the stock so I was thinking it might also do the same for the tablet. But for all of what I plan to be using the tablet for while deployed, keeping a stable release would eliminate one possible headache!
On a last note; I have seen other posts that mention some tablets have dropped by the wayside in terms of developers focusing on them vs the latest and greatest fresh meat hitting the market. Do you think the TF201 is among those tablets that probably won't be having things like CM written specifically for them?
Thanks again
militarymedic23 said:
Hi trophx, thanks for the input on this. I do agree that overall the stock software isn't actually that bad. In comparison to my phone, CM10 does give a nice assortment of features over the stock so I was thinking it might also do the same for the tablet. But for all of what I plan to be using the tablet for while deployed, keeping a stable release would eliminate one possible headache!
On a last note; I have seen other posts that mention some tablets have dropped by the wayside in terms of developers focusing on them vs the latest and greatest fresh meat hitting the market. Do you think the TF201 is among those tablets that probably won't be having things like CM written specifically for them?
Thanks again
Click to expand...
Click to collapse
The difference between the phone and THIS particular tablet is that the added dock functionality which is built into ASUS' stock firmware (which means support for a all dock keys-- screenshot, volume, brightness, lock, etc.--, USB, SDslot, etc.). This makes it different from almost all other tablets/phones in terms of how to get the best user experience. To address your point, the added functionality of CM10, for example, isn't THIS tablet specific, thus not as appealing in my opinion (just because of the instability of the build as of now). Although there definitely are a lot of added features-- very similar to all your phone features. But as I said before, I'd probably prefer stability over extra functionality at this time.
To your second point, I'm not sure. I certainly hope that development continues. On the plus side the similarity of this device to its siblings (tf300t and tf700) makes porting software across each device easier (One of the CM10 dev threads is a port from tf700). Currently CM does officially support the tf201, however, they haven't worked out the issues with the new JB bootloader, and doesn't seem to be too high on their priorities list. On another plus note, ASUS has been pretty quick about shipping out new firmware updates.
Hope this helps
I'd suggest Androwook 1.51. It's stock based so you get all the Asus compatibility with tweaks and performance out the @$$. It's definitely a lot better than stock and more stable/faster than AOSP based roms like CyanogenMod unofficial ports.
hmm, that androwook does look interesting. And you say that it pretty much adds to the base functionality without taking away any of the prime/keyboard specifics? I did a bit of searching on it and saw that many people like it and are awaiting 4.2 to be pushed out so the 1.51 -> 2.0 can go forward. Any rough timeline floating around on that?
Also, considering I will be overseas and on a limited connectivity basis, can anyone point out issues with 1.51 that would be a problem in this scenario?
Since my prime is completely untouched in the sense of no unlocking or rooting, is there a specific guide recommended, start to finish, for getting this loaded? Some of the articles I read seemed to expect a few steps to be done already. Messed around with my phone without too much problem but I get a bit edgy with wanting the exact process for the tf201. I bought it over a year ago now so the unlocking shouldn't be an issue with the one year warranty now expired, but I guess I'm more concerned on making sure I don't brick it!!! Currently use TWRP for my phone, and if that is installed on the tf201 would that allow a full restore back to the current image that is running right now (in case of whatever issue rendering it problematic)?
Thanks!
militarymedic23 said:
hmm, that androwook does look interesting. And you say that it pretty much adds to the base functionality without taking away any of the prime/keyboard specifics? I did a bit of searching on it and saw that many people like it and are awaiting 4.2 to be pushed out so the 1.51 -> 2.0 can go forward. Any rough timeline floating around on that?
Also, considering I will be overseas and on a limited connectivity basis, can anyone point out issues with 1.51 that would be a problem in this scenario?
Since my prime is completely untouched in the sense of no unlocking or rooting, is there a specific guide recommended, start to finish, for getting this loaded? Some of the articles I read seemed to expect a few steps to be done already. Messed around with my phone without too much problem but I get a bit edgy with wanting the exact process for the tf201. I bought it over a year ago now so the unlocking shouldn't be an issue with the one year warranty now expired, but I guess I'm more concerned on making sure I don't brick it!!! Currently use TWRP for my phone, and if that is installed on the tf201 would that allow a full restore back to the current image that is running right now (in case of whatever issue rendering it problematic)?
Thanks!
Click to expand...
Click to collapse
Yep-- for the most part. Since I don't believe you can use NVFlash (this can recover almost all bricks) on already Asus's OTA jelly bean bootloader, TWRP is next best option. I've been flashing and restoring and such for a few months now and no issues. Just be sure to READ very very carefully because the JB bootloader is very different from the ICS one, and (Cyanogenmod for example) some only support one-- installing the wrong one can brick your device permanently.
Ps. I don't want to seem like I'm recommending Stock over other roms in most scenarios, just in yours with limited connectivity, and I don't know how much time you'll have to mess around with a comp, and backing up your device and what not. I just think OTA updates from Asus is the easiest way to go.
**Androwook is extremely stable and super fast. It is exactly as McJesus15 said, based off Asus's rom-- I didn't know if you were asking about those too, because it doesn't offer the same tweaking and system settings CM10 or AOKP offer.
Hi guys, I'll throw in my 2 cents ... Mr medic u should unlock and flash Androwook. The McJesus poster above wrote a newbie guide that I followed and had success with, glitch free. I had been fully stock and read heaps before taking the plunge. You seem the type to read 1st act 2nd so ... no drawbacks. All Asus stock options remain available and Androwook uses an installer that gives you choices every step of the way.
Good luck.
Thanks for the additional feedback. Certainly am interested in the wooky version, but have a few questions on the process McJesus wrote.
An Unlocked Transformer Prime with a custom recovery and updated to the official JB bootloader..
NVflash installed if you want to go back to any other ROM not built on official JB. This is more a recommendation
Click to expand...
Click to collapse
The first would be an obvious download and run the unlocker (warranty buster) from Asus, and the second; that is more of an optional?
And per the instructions it seems once unlocked then doing the pwr_volume combo will allow the bootloader to see the SDcard contents of the wooky image?
Might be bordering on the paranoid level of doublechecking, but definitely can't afford to accidently brick this a day before shipping out!
Thanks!
militarymedic23 said:
Thanks for the additional feedback. Certainly am interested in the wooky version, but have a few questions on the process McJesus wrote.
The first would be an obvious download and run the unlocker (warranty buster) from Asus, and the second; that is more of an optional?
And per the instructions it seems once unlocked then doing the pwr_volume combo will allow the bootloader to see the SDcard contents of the wooky image?
Might be bordering on the paranoid level of doublechecking, but definitely can't afford to accidently brick this a day before shipping out!
Thanks!
Click to expand...
Click to collapse
Alright I'll take care of ya before you ship out. Good luck and God bless you.
NVflash is a utility that can only be used while you are on Ice Cream Sandwich. Since you are on Jelly Bean there is currently no way to do the process.
Unlocking your Prime is easy. Just use the app provided on the Asus website. Understand that your warranty is now void (not like Asus intended to do much for you anyways). Once you are unlocked use the automated utility in my guide to easily flash TWRP. It's not the latest version but I haven't had time to update my post. It's perfectly fine for your uses.
Once that's done just flash Androwook either by putting the .zip file on an external SD card or the internal storage of the Prime. Once you begin the process and start selecting options the rom is basically totally customizable for you. One suggestion I will make is when selecting the kernel go with Clemsyn's 1.7ghz custom kernel as it literally is the biggest performance boost you could possibly do for your Transformer Prime. If you need any help you can message me privately or ask in the Androwook thread. The guys there are genius's. Hope we helped you get your Prime in working order before you deploy.
Oh, also, when you first boot into recovery I suggest making a back up immediately. Always have a back up handy and I personally keep 2-3 rom zips on my Prime for the SHTF moment.
Thank you!
I actually started tinkering around with the unlocker just before you posted. Unlocked it fine, and put TWRP on it and did a full backup of stock. I did pull down the 1.51 wooky image and put it on. I guess after working with CM10 I was expecting all the fancy changes but so far I can't tell the difference between stock and androwook.
I did also try and put the Wooky Prime 2.1 image but the tablet would just sit on the asus logo and not go anywhere. Can you advise what major differences should be noticed between 1.51 and prime 2.1?
Thanks
militarymedic23 said:
Thank you!
I actually started tinkering around with the unlocker just before you posted. Unlocked it fine, and put TWRP on it and did a full backup of stock. I did pull down the 1.51 wooky image and put it on. I guess after working with CM10 I was expecting all the fancy changes but so far I can't tell the difference between stock and androwook.
I did also try and put the Wooky Prime 2.1 image but the tablet would just sit on the asus logo and not go anywhere. Can you advise what major differences should be noticed between 1.51 and prime 2.1?
Thanks
Click to expand...
Click to collapse
Wooky Prime 2.1???
oh I have to laugh at myself sometimes
Androwook Prime 2.1
militarymedic23 said:
oh I have to laugh at myself sometimes
Androwook Prime 2.1
Click to expand...
Click to collapse
I'm still not getting where you are seeing 2.1. Can you link me please.
it was buried fairly well, but here is the link:
http://www.teambamf.net/topic/3986-rom040712-androwook-prime-v21-complete-rom-customization/
militarymedic23 said:
it was buried fairly well, but here is the link:
http://www.teambamf.net/topic/3986-rom040712-androwook-prime-v21-complete-rom-customization/
Click to expand...
Click to collapse
Ahh, sorry mate but that is really old. That was when the rom was based on ICS. When it turned to jellybean it became hairybean and went back to version 1.
1.51 is the latest.
oh, no worries though. Since it was hanging at startup I went back to 1.51.
Is there a rough rumor when JB 4.2 might be coming out and HB goes up a version? It will of course be while I'm away but if I know a general date then I can try and watch for it.
militarymedic23 said:
oh, no worries though. Since it was hanging at startup I went back to 1.51.
Is there a rough rumor when JB 4.2 might be coming out and HB goes up a version? It will of course be while I'm away but if I know a general date then I can try and watch for it.
Click to expand...
Click to collapse
Someone correct me if I'm wrong but I believe the AndroWook rom is based of OTA releases from Asus, so it probably won't have JB 4.2 unless something along those lines comes out.
of course but I was just curious if anyone has heard if a major version change or new version of android scheduled to be released in the next 6 months.
militarymedic23 said:
of course but I was just curious if anyone has heard if a major version change or new version of android scheduled to be released in the next 6 months.
Click to expand...
Click to collapse
Oh no idea-- Asus said they would be supporting 4.2 back in November, but it'll probably take a bit. It isn't a Nexus after all. But so far I've been pretty satisfied with their software updates in terms of speed of release and quantity.