OK, don't kill me. New here, just got my Gtab today. I have read a lot and a lot and a lot. Maybe too much. I have not touched my tab yet. Can I start following the easy steps to adding a new ROM, or do I need to do something to the tab first? It looks like vegan is the one to use, but exactly what file is it that I use? I am tech savy, but very new to doing these types of things. Sorry for asking such a noob question. But my brain is in overload right now.
Thanks
Stolly
Just follow the instructions on the vegan thread. You will find the files you need there ;-)
Good luck!
I was ready to roll, but what got me thinking was the bootloader thread. Would that apply to me?
Thanks for the reply
Make sure you know which version android you are on and what bootloader you have. There is a 1.1 and a 1.2 dev branch and I think it makes a big difference. I'm still on 1.1 Vegan 5.1. Froyo and happy with that. Newer builds use different boot loader, make sure you read instructions thoroughly before you flash device.
stolly23 said:
I was ready to roll, but what got me thinking was the bootloader thread. Would that apply to me?
Thanks for the reply
Click to expand...
Click to collapse
Check your version in the settings about tablet screen. Most likely you will have a 1.1 based kernel. So to answer your question, No, it does not apply to you.
Look under system and find "about device". Android version is listed there.
Ok, so I just powered up for the first time. Adroid OS 2.2, Tap 1.1-3389. BUT, to really make things worse, I think I have a dead pixel in the display. CRAP
Well wifey says the pixel does not bother her, So I will go ahead and get the ROM going. Is the Vegan 5.1.1 the correct version?
Thanks again
Yes, vegan 5.1.1 is a 1.1 based Rom, you'll be fine with it. HOWEVER, I do suggest that you at least update to 3588. It's still a 1.1 based Rom so flashing vegan 5.1.1 will be the same. it's just a newer version, and useful in case you want ot go to the 1.2 rom's later on.
HOWEVER, me, personally, since you're stock, I would update to 3588, theen flash teh stock 4349, then flash Brilliant Corners (it's just a 1.2 bootloader port of Vegan 5.1.1) That way, if you want to ever get on the honeycomb bandwagon when all the wrinkles are ironed out, you're already on the 1.2 bootloader.
I WAS running Vegan 5.1.1, and I liked it, don't ge tme wrong. I decided to take the plunge and get to the 1.2 bootloader, since most roms will be going that direction in the future anyway. It was more work to undo what I had already done, just to get back to where you are starting from, so you are already halfway there.
I'm not allowed to post a link to another forum that contains the files and information for Brilliant Corners, but if you use some googling skills, I'm sure you can find it. The developer that was part of Vegan 5.1.1, and created TNT lite, and is currently working on the Honeycomb port, switched most 1.1 roms over to the 1.2 bootloader, including Brilliant Corners.
I'm new to all this rooting as well what helped me was some of the video tutorials on youtube. It helps to see something being done before you do it. I have Vegan-tabs 7.0.0 running on mine.
Related
I've been playing around a lot with the gtablet today. It came with the stock firmware and then I updated it to 3588 OTA. Afterwards I tried several roms, and ended up with a brick (magic value mismatch error), and used NVFlash to go back to stock rom.
Once I had the stock rom on I wasn't able to upgrade to 3588 OTA because I kept getting an error once it would try installing it. I tried to manually put 3588 on, and it partially worked, but I got some sort of error about installing the bootloader, but 3588 still loaded up and worked fine. So then I went ahead and installed one of the custom roms.
So my question is... how do I find out what bootloader version I have installed right now? I played around quite a bit with trying lots of stuff out, so I want to make sure I have the most recent version running.
Thanks!
finally found it
From roebeet on another forum
to check which branch you are on: Go to Settings -- About Tablet -- Tapu UI Version. If your firmware starts with "1.1", then you are on the 1.1 (old) branch. If your firmware starts with "1.2", then you are on the 1.2 (new) branch. Also an obvious difference between the two is that the 1.2 branch adds a lockscreen to the tablet.
the only way to be on 1.2 is to flash to it intentionally. 4349 was an OTA that did it automatically, but that update has been pulled. So, unless you've flashed to 4349 stock, you are on 1.1.
Newbe - want to try different Roms
qgirene said:
From roebeet on another forum
to check which branch you are on: Go to Settings -- About Tablet -- Tapu UI Version. If your firmware starts with "1.1", then you are on the 1.1 (old) branch. If your firmware starts with "1.2", then you are on the 1.2 (new) branch. Also an obvious difference between the two is that the 1.2 branch adds a lockscreen to the tablet.
Click to expand...
Click to collapse
I'm a very new user to GTab and android, I've been learning so I'm sorry if my question(s) have been answer elsewhere.
1. Thanks for the info on where to find out which bootloader. This really help, I had the same question as I'm trying to try other custom ROMS.
2. When I first got my GTab (by the way, I love it) I try to install TnT Lite 4.2.4 with no luck, so I install Vegan Tab Gingerbread edition and I had to reflash while trying to install TnT Lite again and got the Harmony edition of Gingerbread (not even sure if it is the same one, Newbe for you ). Now I have lock screen on it. According to your post that should be 1.2. bootloader. So, installing Vegan Tab 7 Harmony updated my bootloader I guess.. is that true??
3. Now I want to try CM7 with overclock Kernel, can someone give some feedback?? or should I just want for Beta of Honeycomb "Bottle of Smoke"??
Thanks all
SkyDragon8 said:
2. When I first got my GTab (by the way, I love it) I try to install TnT Lite 4.2.4 with no luck, so I install Vegan Tab Gingerbread edition and I had to reflash while trying to install TnT Lite again and got the Harmony edition of Gingerbread (not even sure if it is the same one, Newbe for you ). Now I have lock screen on it. According to your post that should be 1.2. bootloader. So, installing Vegan Tab 7 Harmony updated my bootloader I guess.. is that true??
Click to expand...
Click to collapse
I believe there is a lock screen on most ROMs whether they're 1.1 or 1.2. The obvious way to determine which version of *stock* you're on is whether or not it has a lock screen. 1.1 doesn't but 1.2 does.
The only 1.2 ROMs I'm aware of are:
Stock 4349
Brilliant Corners (what I use)
Century Eyes
Mountain Laurel
Beasty
Honeycomb (alpha build)
Thanks
Thanks for the information. I will check my G Tab when I get home tonight and look for it in the "About Tablet" in Setting..
Hey all,
I've been perusing these and "other" forums trying to decide if I should perform the stock update and reflash one of the new roms.
I'm currently running Vegan 5.1.1 and loving it. Everything works like I want it to, it's very stable, and I've spent a lot of time "making it mine."
With the new update, and subsequent new roms released by our dear friend Roebeet, I was wondering if there would be much of a benefit for me to Nvflash to stock, perform the stock update, then reflash one of the newer roms, ie Brilliant Corners, Mountain Laurel, or his newest Adam based rom?
I've always been of the school that if it's not broken, don't fix it. I figured that these new roms were intended for those that received their gtablet with the already updated 1.2 bootloader, but I've read people on forums going from 1.1 custom roms, back ot stock, then to 1.2 then reflashing a newer rom. Most of them only report on bugs etc in the new rom, but I've not seen anyone comment on whether it was actually better than their 1.1 rom, or what, if any benefits they saw from it.
I planned on using my current setup until it's outdated significantly. For instance, if Nvidea provides drivers, and VS creates a GB update, then the wonderful devs that are working on gtablet make a true working, supported gingerbread rom, THAT'S when I'll update.
so, bottom line, would it be worth it to nvflash to stock, update to 1.2 bootloader, then install Brilliant Corners? or an I best just not fixing what isn't broken?
thanks for the replies, and I apologizse if this was addressed in another thread. I've searched, read, and couldn't find anything this specific. I've read what the update contains, and what it does, and the problems with it, but I have not read anyone adress a direct comparison betweeen the options that are currently available.
Hello everyone, I'm trying to do a buddy of mine a favor by upgrading his Vibrant to something a lot better (he's on stock) but I'm a bit unclear on a few things. First of all let me get out of the way that I'm a Fascinate (Verizon) owner that recently modded my own phone to run AOKP ICS Milestone 6 with great results, so I figured since he pretty much had the exact same phone I could do it for him. The problem I'm running into is the procedure I used to flash my phone doesn't seem to apply to the Vibrant (or at least what I was searching for) so I just wanted to clear up a few steps before I try to flash his phone.
He's not a very tech savvy guy, so he won't be updating ROMs on the bleeding edge or anything, he just wants his phone to run better so I figure ICZen is the way to go right, considering it's based off of what I'm using now (AOKP M6)? Everything needs to work, so that pretty much rules out any JB right now because of the GPS issues. Okay now onto the specific flashing questions:
1) This thread seems to be the go to thread for flashing the Vibrant, but it hasn't been updated since Dec '11, so would I just follow the same procedure for the newer ICS roms?
2) Here is the guide I used for my Fascinate (see section 4), which has a few extra steps that I notice are lacking for the Vibrant... namely installing cwm4 fixed for cm7 first, then installing THS Build 2, then flash over that with whatever ICS Rom you need.
3) Devil Kernel is what's considered best on my phone running AOKP M6... is that true as well for ICZen?
4) Since the Vibrant never got 2.3, what is the best modem to be using? On the Fascinate the EH03 (GB) stock modem is best, but I'm unsure what the deal is for the Vibrant since they never got an official GB update. Also along the same topic, Verizon has a code you can input that updates your PRL and improves reception... does T-Mobile have such a code or not?
I appreciate any and all input, as I want this to go as smoothly as possible. Thanks
You seem to have a pretty good grasp on what your doing.
From stock, install gingerbread bootloaders then go to recovery via volume rocker down and hold power button, until the logo. Might have to practice it a couple times.
Once in recovery click reinstall packages, might have to do it s couple of times. This installs your update.zip
From here I always perform wipes and flash a custom Froyo ROM. Maybe overkill but, only takes a second and I don't mind.
From here I flashed the latest CM9 nightly and on to Helly Bean.
Do your wipes in between flashes, and you should be fine.
I haven't ever heard about a T-Mobile code for tower updates, I think its automatic.
Well I didn't have to worry about bootloaders on my Fascinate since I was already on GB, so that's a bit new to me... but doing a quick google search I found this guide. Is that an accurate guide to follow? Alright so basically what you're saying is before I root at all I need to do this?
Also like I was saying earlier, he wants everything to work so I think Helly Bean is out of the question because of GPS, right? I was thinking ICZen looks the cleanest, with everything working nicely, and it's based on what I'm currently using on mine.
Can you clarify on why you're flashing a custom froyo rom? I won't mind to do that either, if it has any benefit.
Also, I checked his phone last night and it's on stock 2.2, not 2.1 if that makes any sort of difference. Thanks again
First root and get cwm recovery then flash bootloaders. The vibe never got an official GB, so that's why boot loaders are recommended. The guide you have is fine. Second the GPS on the vibrant has been notoriously hit or miss. I have a captivate, the GPS works great but my vibe couldn't get a lock to save my life.
Now as far as iczen or hellybean, you have to weigh the options:
Iczen is a great ROM and might have a better chance getting a GPS lock. IMO if you can get a lock with ICS you will probably get a lock with JB. But with ICS you have to be concerned with the EU bug. What's that you ask:
There has been an issue with people randomly looking at phone and a message saying encryption unsuccessful press to reset. If you press the button you have basically just locked up your internal SD card. If you don't press you MIGHT be able to recover it. There is a workaround if this happens, to use ext SD only but your friend will not like that.
I'm currently running hellybean on both of my devices and I love it. Like I said, cappy gps works great and my vibrant not so much. If you really want stable go with bionix as toast recommended or one of moped Ryder's ROMs . If you want to be wowed, go with hellybean.
There are some things you can try with it to get a GPS lock. The general consensus is turn on GPS, reboot, wait it out till you get an initial lock. After that locks will be quicker. I hope this helped in some way, if so hit thanks. As far as the guides etc you are good to go.
its peanut butter jelly(bean) time
That did help quite a bit, thank you. I have never even heard of that bug, do you know if that's Vibrant specific or can that happen on any of the others? I have been wanting to try Helly Bean on my Fascinate, but unfortunately my sdcard isn't very stable and I don't trust to flash anything until I can buy a new one. Honestly, I don't even think he cares much about the GPS, my original point was more along the lines of that I wanted to give him as much of a glitch-free experience as possible, so my fault for not being more specific. If Helly Bean is as stable as you're saying, then maybe I'll just do that instead then, especially after you explained that glitch. Also, since I don't have any Helly Bean experience myself, does it offer as much customization as AOKP? I've grown quite fond of all the little tweaks they include
Hellybean is pretty stable. When I did my vibrant I didn't have to use a boot loader I went straight to ICS then jellybean. If you want ICS then you may want to try aokp for his vibe its nice. If you end up trying aokp milestone 6 and have unknown baseband let me know and I'll link you to a linario build that should fix that
Sent from my SGH-T959 using xda app-developers app
I have a complete guide to install ICS ROMs in my signature if you feel so inclined. PM me if you need any of the files or I may just host them on my Dev-Host account. I'll be out most of the day, but I can upload them later on tonight.
When I need to go back to stock and root and flash cwm I use the AIO toolbox. I just put the rom on the internal flash and then use AIO to get cwm on it from the flash custom rom option. Then cancel the file and the phone will reboot into recovery where you install packages twice and should end up in cwm.
The EU bug has hit vibrant and captivates that I know of. It seems rare though, if you think about the number of users compared to the reported number of cases of the EU bug, its a small percentage.Hellybean doesn't have nearly as much customization but it does offer theming and some launcher/lock screen tweaks. You could always use a custom launcher. There are a few other jellybean ROMs you could try. Honestly any way you go will be better than stock!
*I forgot to tell you, you will need to Odin back to stock 2.1!
its peanut butter jelly(bean) time
Yeah.. I don't think root is actually necessary to do any of this. You'll be rooted when the process is complete however. The custom ROMs come with root access.
But to elaborate on Samsgun357's last post, if you are currently on Froyo 2.2 stock, you'll need to Odin back to stock 2.1 prior to starting, because Samsung fixed the bug that allows installation of custom recovery when they released 2.2
It's simple to do, search the forums and you'll find a guide on Odining back to JFD. That's stock Eclair. If I have time in a few I'll locate it for you and post it.
There are YouTube videos about it with links to the files as well. I think djeddie1west posted a good one with links to all files needed, if they are still working links.
Edit: http://forum.xda-developers.com/showthread.php?t=1117990
There's the link for installing GB bootloader.
Also, I am on my phone and haven't tested links, but as long as they work, near the bottom of the post you'll find the files needed to Odin the JFD files.
Eh, I just gave up and told him to go get an iPhone instead, to increase his hipster status.
Or... that's right, I'd rather be dead than own one of those ugly bricks.
You have all been extremely helpful, and I think I have more than enough to go on. I think for now I'll just throw ICZen on his phone since it's based on the rom I'm most familiar with... and when I have more experience with Helly Bean (I finally ordered a new sdcard that's on the way, so I can play with it on my own phone soon enough :good I'll just flash his again. He'll be okay with the risks mentioned so far in this post, and honestly his upgrade is coming up soon so I'm sure I'll be drooling over his S3 when that time comes.
@Woodrube That guide you made to install ICS was exactly what I was looking for, and I wish I had found it earlier so thank you for making such an excellent post.
I'll post back here with the results, thanks for all the help once again
Afternoon all,
I have a Prime that presently has Android version "4.0.3" and build number "AndroWook Prime v2.1". I am attempting to upgrade to the lastest Hairybean release, but I am uncertain as to which instructions to follow as I am unable to determine my bootloader version. Any suggestions?
Thanks
CoosaCounty said:
Afternoon all,
I have a Prime that presently has Android version "4.0.3" and build number "AndroWook Prime v2.1". I am attempting to upgrade to the lastest Hairybean release, but I am uncertain as to which instructions to follow as I am unable to determine my bootloader version. Any suggestions?
Thanks
Click to expand...
Click to collapse
I got confused there for a minute but you are talking about Androwook 2.1 and not Androwook Hairybean 2.1.
By the Android version number you are still on ICS.
I would highly advise that you go thru the nvflash process first as you can only do it while on ICS and it makes you brick proof.
Once you have done that you just have to follow the instructions in the Hairybean thread for 2.2 which will upgrade your bootloader and recovery and then flash the rom.
I'd wait a week tho as 2.3 is due soon.
flumpster said:
I got confused there for a minute but you are talking about Androwook 2.1 and not Androwook Hairybean 2.1.
By the Android version number you are still on ICS.
I would highly advise that you go thru the nvflash process first as you can only do it while on ICS and it makes you brick proof.
Once you have done that you just have to follow the instructions in the Hairybean thread for 2.2 which will upgrade your bootloader and recovery and then flash the rom.
I'd wait a week tho as 2.3 is due soon.
Click to expand...
Click to collapse
Thank you very much for the reply; I was unaware that they are two different roms. I am going to find how to follow the nvflash process as you advised.
Thanks again.
CoosaCounty said:
Thank you very much for the reply; I was unaware that they are two different roms. I am going to find how to follow the nvflash process as you advised.
Thanks again.
Click to expand...
Click to collapse
Androwook was based off ICS. When it switched to Jellybean it became Androwook HairyBean.
nvflash is definitely worth it mate. There are people on here who would kill to go back to ICS so they could nvflash backup
Related question to this thread
flumpster said:
Androwook was based off ICS. When it switched to Jellybean it became Androwook HairyBean.
nvflash is definitely worth it mate. There are people on here who would kill to go back to ICS so they could nvflash backup
Click to expand...
Click to collapse
My query is somewhat related, and apologies before it it has previously been addressed in another thread, so I won't start a new thread for my related query.
I have just purchased an ex-display model Asus EeePad Prime here in the UK on eBay for about the third of the price as a new one. So far, all seems to be working and running fine, dongleless Wi-Fi included, but I have a question.
As soon as I turned on Wi-Fi and connected with my router, my Asus Prime started 'automatically' downloading what I assume is (the latest) firmware, I couldn't find a way to cancel the download (no user-manual, unfortunately), so I immediately turned off Wi-Fi, as I have no idea what version firmware my Prime is downloading. Right at the moment, it's running stock 4.0.3, but I don't want it downloading some firmware that I may regret at some point later. So, may I ask, is it advisable to let the firmware download and do its thang, or wait for another, different or better firmware. I am totally new to using tablets and my only other Android device is a Samsung Galaxy S3 running JB 4.1.2,
Without reading through an online manual (probably a fruitless exercise anyway) or wading though hundreds of forum posts, would one of you more experienced in firmware than I, be good enough to advise me about which is the best, most stable firmware I should be running on my Asus Prime, as well as how to disable automatic firmware updates (I couldn't find an option for that in the settings yet), and any more cautionary steps I should be advised to take before I mess up or brick my new tablet....OR point me to a thread that already has the answers to my questions here?
I'm finding this a bit frustrating, as obviously, I can't use Wi-Fi for anything else until I have an answer as to how to stop automatic downloading of firmware via Wi-Fi.....help?!?
Many thanks before.
NB.
My Kernel version:-
2.6.39.4
android @venus #1
Al.Gray said:
My query is somewhat related, and apologies before it it has previously been addressed in another thread, so I won't start a new thread for my related query.
I have just purchased an ex-display model Asus EeePad Prime here in the UK on eBay for about the third of the price as a new one. So far, all seems to be working and running fine, dongleless Wi-Fi included, but I have a question.
As soon as I turned on Wi-Fi and connected with my router, my Asus Prime started 'automatically' downloading what I assume is (the latest) firmware, I couldn't find a way to cancel the download (no user-manual, unfortunately), so I immediately turned off Wi-Fi, as I have no idea what version firmware my Prime is downloading. Right at the moment, it's running stock 4.0.3, but I don't want it downloading some firmware that I may regret at some point later. So, may I ask, is it advisable to let the firmware download and do its thang, or wait for another, different or better firmware. I am totally new to using tablets and my only other Android device is a Samsung Galaxy S3 running JB 4.1.2,
Without reading through an online manual (probably a fruitless exercise anyway) or wading though hundreds of forum posts, would one of you more experienced in firmware than I, be good enough to advise me about which is the best, most stable firmware I should be running on my Asus Prime, as well as how to disable automatic firmware updates (I couldn't find an option for that in the settings yet), and any more cautionary steps I should be advised to take before I mess up or brick my new tablet....OR point me to a thread that already has the answers to my questions here?
Many thanks before.
NB.
My Kernel version:-
2.6.39.4
android @venus #1
Click to expand...
Click to collapse
You are still on ICS and at the moment you can make nvflash backups that will make you completely brickproof. It will also allow you to go back to ICS from jellybean if you wanted to which people without the backups cannot do.
I would highly advise that you make these backups before upgrading anything.
You will need an unlocked bootloader to be able to do nvflash.
http://androidroot.mobi/pages/tegra3-guide-nvflash/
flumpster said:
You are still on ICS and at the moment you can make nvflash backups that will make you completely brickproof. It will also allow you to go back to ICS from jellybean if you wanted to which people without the backups cannot do.
I would highly advise that you make these backups before upgrading anything.
You will need an unlocked bootloader to be able to do nvflash.
http://androidroot.mobi/pages/tegra3-guide-nvflash/
Click to expand...
Click to collapse
Thanks for that tidbit, certainly something I'll need to look into (after finding 'Nerves of Steel' <g> ).....but more concerned about disabling this (unknown) firmware update auto-downloading first?.......Diolch i ti ffrind!
NB.
Guess I should read up as much as I can on AndroWook too, eh?
Oddly, the automatic firmware update OTA download has (thankfully) stalled/stopped/stuck at 23% and I have no idea what I did to stop it downloading or even how. Anyone got a clue to help me figure it out? All other downloads via Wi-Fi are working as they should.
But, saying the firmware download has stopped, is there any way that anyone knows off to cancel/delete the 23% of it that has been automatically downloaded and taking up valuable space on my internal memory, please? (I'm guessing I'd need to root my Prime to do that?)
One last important (important to me anway lol), question.....is it advisable or not to make those nvflash backups before of after rooting my ICS 4.0.3 firmware (I was thinking of using 'Viper' to root it, or maybe you guys can suggest a better application to use?), or won't rooting it before I've made those backups make any difference? Please advise, thanks.
Hope that's not too many dumb questions, but hope one of you if good and has time enough to answer them for me........ANYone......please??
Hello everyone, I just joined after installing 6.0 on my Asus tf201. I have flashed ROMs from hairybean up to 6.0 and back as well as bricked this poor tablet several times. I have also replaced android with various versions of Linux using other sites so I'm no stranger to playing with nvflash and fastboot. I can also do some how-tos if anyone wants, anyways I made this thread cause I have a weird issue, I downloaded Super SU twice and both times TWRP 2.8.1.5 (I might have the numbers wrong) just rebooted like it was a soft crash or something. I would post in the thread I got the ROM from but I don't have enough posts yet, would an older version work without issue or do I have to just deal with no root ATM?
The version of Super SU that I'm trying is 2.52 BETA as the post specified that one but doesn't say if an older will work. I look forward to having a great time here, and I welcome any and all feedback.
Thank you for your time.
Tiger
Tiger,
I'd just update the recovery to the latest Area 51 version. It's got a few new features that are pretty slick. From there, grab one of the SU's from one of Taconikki's Rom's. They worked for me every time.
O
I can use a howto which is current if anyone has one for flashing from stock.
Admiral688 said:
I can use a howto which is current if anyone has one for flashing from stock.
Click to expand...
Click to collapse
If you still need a how-to Ill get started on it, if you do I just need to know if you have done any backups or anything in case you brick the tablet. Mine is currently running android 7.1, I havent checked to see if 8 is available yet (presuming someone ports it of course) and Ill even cover how to go back to stock if you need that info as well.
Thanks! I finally did upgrade it to 7.x and am waiting to see if someone gets an oreo build
Sent from my 2PS64 using Tapatalk
I keep checking every now and then, but my tf201 keeps randomly rebooting, so it hasnt seen much use as of late. I am currently working on porting ubports (formerly ubuntu touch) to my galaxy note 4 though. I might try and get it on my tf201 eventually cause when I tried it on there it was butter smooth and tank reliable. I switched it back to android cause there were no apps at the time and the build has been abandoned since then, so who knows.