Some of you might know my name already - I own the TNT Lite and gADAM mods (active) and TwoTapsX mod (currently inactive). I'd like to make this statement now, so hopefully you will read this.
First and foremost : READ MY ORIGINAL POSTS for instructions on using my mods. I try to make it clear and break down what you need and how I recommend to proceed. For TNT Lite, gADAM and TwoTapsX, that is the first post in those threads - the same place where the download links are.
If you post in General or jump on the IRC, you might get ten power users telling you ten different ways of how to mod your device. I cannot control that, and have no intention to. I can only control the directions for my own mods, so I ask you to please read the instructions carefully. I do NOT recommend clockworkmod as an ongoing flashing tool, others here swear by it. I have my reasons for considering it a risk when flashing it because of problems with TNT Lite 5, and problems over in the Notion Ink Adam forums. This is already causing some confusion since not all the devs and power users agree, and it will probably continue to be this way. Again, I can only recommend with the mods I personally support, and my recommendations and directions are listed in my posts for each of the mods I support.
Please use the search button - we know it's not the greatest but there are a lot of redundant posts already. There's a very good chance that your question has already been addressed. Thanks in advance for trying a search, first. Unfortunately, there is no Wiki here yet, just a few FAQ's (I would recommend reading those, as well).
I believe that you should do an OTA update to 3588 before you start modding. That's my opinion, others disagree. But I think that's the best baseline you can have right now. Best to "play it safe", again imo. 3389 is a good baseline, but 3588 is a better one.
Lastly, I am not a moderator. People have asked me to create subforums, authorize new ROMs and ask me questions about other ROMs which I don't support. If you have any moderator questions, you should PM "theimpaler747" or post in his thread in the General section. Or if your question is in regard to a ROM I don't support, please contact that developer directly. They do not support my mods, and I don't support or control theirs.
Thanks for reading! I hope your stay in XDA is a fruitful one!
Roebeet,
I just was wondering:
About your recommendation NOT to use CWM (specifically, CWM .8) to flash, is that recommendation just for TNT version > 3588?
The reason for my question is that, per the other thread, I just flashed my Gtab from stock 3452 to stock 3588 last night, using CWM .8, which was already installed.
So, after that, I now have stock 3588 recovery (since flashing to 3588 overwrites CWM), and have been wondering whether or not I should re-install CWM .8.
As you may know, I'm pretty much a "stock kind of guy", i.e., the main reason that I updated to 3588 was in preparation for the next OTA, whenever that happens, because of the incompatible bootloader in 3991.
If I'm reading your post above correctly, your recommendation in my case would be "no, don't install/use CWM .8 anymore", right?
Now, for the benefit of others, who may want to go back to say a TNT version previous to 3588, or may want to flash a current, but other ROM (e.g., TNT lite earlier than 5.x), what about them?
Are they ok using CWM .8 still?
Jim
I would not recommend clockworkmod for flashing ROMs, unless the dev / modder specifically states it's required.
Example: TNT Lite 4.3.0 is a 1.1.-based ROM that is "close to stock". Because of that, standard recovery is recommended if you are coming from stock, because you probably won't boot loop. But, if you do, you can add clockworkmod after-the-fact via a microSD and I have instructions on how to do that in my TNTL first post.
For gADAM, you will almost certainly boot loop so I ask that clockworkmod be used that one time, to get it installed. That's because I know boot loops will occur and data wipes are required. But, you can add standard recovery back later.
The problem here is that we don't have a 1.1-based recovery solution that does BOTH user data wipes AND bootloader updates. The Notion Ink Adam, for example, has a standard recovery that does. And Viewsonic's UAT 3991 (the non-released firmware) also does. So, eventually, this will be a non-issue I believe. But right now, it's tricky.
As I mentioned in other posts, TNT Lite 4.3.0 and gADAM 1.3.0 have something called the "3588 Recovery Pack" -- two scripts that allow a user to easily flip back and forth between 3588 standard recovery and clockworkmod. I even have a standalone version that should work with any 1.1-based rooted ROM.
I personally still use clockworkmod for anything non-firmware flash related (like the nandroid backups and data wipes), but flip back to standard recovery if I plan to flash to another firmware, because of the bootloader flashing support.
roebeet - I know you've recieved countless kudos from the members here but I'd like to thank you myself for all of your efforts, I've only been on here a few days and I already see the impact of your contributions.
I'm guessing I will keep the stock ROM for awhile but as I said in a previous post I'm sure all your and all the other developers hard work contributed to a better more stable stock release.
DJ
Roebeet,
When you say "flip" between std recovery and CWM, do you mean you replace what's in the recovery partition? Are those scripts using nvflash? Or something else?
Jim
jimcpl said:
Roebeet,
When you say "flip" between std recovery and CWM, do you mean you replace what's in the recovery partition? Are those scripts using nvflash? Or something else?
Jim
Click to expand...
Click to collapse
They are using a tool called "flash_image" - this is a binary found on other Android devices. I had a version on TNT Lite, but it really never worked very well, but I manged to fix it and wrote two shell scripts that flash the recovery partition while the GTAB is running. It actually works and I've been using it for the last week or so.
So, for example, the "fixrecovery.sh" script runs this:
Code:
/system/bin/flash_image recovery /system/etc/recovery/recovery.img
Where "recovery.img" is the 3588 stock recovery. I also have a script that will flash clockworkmod .8, if needed.
Full details: http://forum.xda-developers.com/showthread.php?t=1005080
New wooter here. Just want to say thanks to all the devs for the hard work and continued support! Lots of good information being posted and it all has been extremely helpful. Still waiting for my G-Tablet but I plan to play around with the stock ROM for a little while before I dive into any kind of modding. Thanks again!
roebeet said:
They are using a tool called "flash_image" - this is a binary found on other Android devices. I had a version on TNT Lite, but it really never worked very well, but I manged to fix it and wrote two shell scripts that flash the recovery partition while the GTAB is running. It actually works and I've been using it for the last week or so.
So, for example, the "fixrecovery.sh" script runs this:
Code:
/system/bin/flash_image recovery /system/etc/recovery/recovery.img
Where "recovery.img" is the 3588 stock recovery. I also have a script that will flash clockworkmod .8, if needed.
Full details: http://forum.xda-developers.com/showthread.php?t=1005080
Click to expand...
Click to collapse
Hi,
Ahh! That makes sense. I think I remember seeing a flash_image binary when I adb shelled into the gtab when CWM was running, probably because CWM itself uses it to flash partitions.
That may be why CWM doesn't have that option, I.e., it'd have to overwrite itself, since it itself is in the recovery partition...
Jim
Related
Earlier before reading the forum and all the "recall" related business, I was working on my "stock" G-Tablet. It has had no updates and I have been trying to keep it as stock as possible.
It popped up offering me OTA 1.0.1-3053.
Seems the most recent number I ever heard before was like 2960-something.
Description said it offers: (1) Improved overall system performance; (2) Improvements to the Weather application; and (3) Improved reliability of the Factory Data Reset procedure.
Is this just one of the old OTA updates I never saw before -- or is this something new?
I'm not installing it until I know what's going on.
Rev
I just got my Gtab last week, and I think that was the OTA that popped up when I powered up. Flash (from xda) works with it, whereas I have the impression that it didn't before that. Also Slingplayer, albeit with the "start it many times" problem.
Jim
OTA from stock today..
Picked up a new gtab at Sears. Had the OTA 3053 update. It's much snappier than the original. Still a bit sluggish, but much more usable than the original.
butchconner said:
Earlier before reading the forum and all the "recall" related business, I was working on my "stock" G-Tablet. It has had no updates and I have been trying to keep it as stock as possible.
It popped up offering me OTA 1.0.1-3053.
Seems the most recent number I ever heard before was like 2960-something.
Description said it offers: (1) Improved overall system performance; (2) Improvements to the Weather application; and (3) Improved reliability of the Factory Data Reset procedure.
Is this just one of the old OTA updates I never saw before -- or is this something new?
I'm not installing it until I know what's going on.
Rev
Click to expand...
Click to collapse
BTW, did you have TNT lite installed? I think roebeet said that he removed the TNT updater. Maybe that's why no notification before?
Jim
Oops. Didn't notice you said 'stock'. So not sure why you didn't get a notification before this....
jimcpl,
I deliberately kept the wifi off while I was checking out all the "stock" stuff I wanted to know.
Ironically, I installed CWM to make a backup of the original stock stuff and forgot that CWM would change the recovery.img.
Now I have to either find and replace recovery.img in the backup or find another way to take out CWM.
Or......just go ahead and MOD it, which is what I intended anyhow after checking out the stock stuff.
Thanks.
Rev
Hi.
OK. Got it.
I think that roebeet said that there's now a way to go back to stock recovery, after CWM. Might want to check with him?
That was one of the reasons I've stayed stock, plus didn't want to lose OTA yet...
Jin
jimcpl,
I found the thread, which has two images from VS in it. But when I deleted the recovery "assert" from the .zip file as it said is required not to conflict with CWM -- it didn't. It just left it there and so I still have v. 2967 with CWM.
I will leave him a note in Development.
Anyhow, thanks. I'll either find a way or move on to the next project.
Rev
3053 came out a week(?) ago - TnT Lite 2.3.0 / 2.4.0 are based on it.
There's are stock ROM's if you want to backout of a mod (see the link in the FAQ area of my sig), or you can use nvflash and use bekit's original firmware image with it.
roebeet,
I have successfully run the 2967 rom update as you suggested, but took out the "assert" line for the recovery.img as the thread says is necessary. As a result, it didn't take out CWM -- which is my main goal.
Is there a way to overwrite CWM short of going to nvflash. I think I have the files to do a flash, but not the utilities needed to do it. So it would be easier if I could overwrite.
Rev
It's bad when you have to reply to yourself???!!!
But I also had a thread in Development which Roebeet answered and triggered me to find the answer to this too.
I wound up taking the Vanilla 3053 rom as listed in Roebeet's FAQ thread. I made a "Recovery" file with Command in it to start the update. Then put that along with the downloaded 3053 update.zip in the /sdcard directory. Brought up CWM and started the zip file running. It picked up the recovery file the first time through, showed the boxwitharrow that goes with regular recover and completed.
Then it rebooted again and repeated the same load using regular recovery. When all was done, I had a OTA 3053-level tablet. I then reset the user data to make sure all was OK there, and I went in manually in ES file manager and deleted the old CWM directory and backup directory under it.
So now I am back to 3053 totally stock and should be able to get any OTA update that might come along.
Thanks to all who made suggestions.
Rev
EOT (End of Thread)
butchconner said:
roebeet,
I have successfully run the 2967 rom update as you suggested, but took out the "assert" line for the recovery.img as the thread says is necessary. As a result, it didn't take out CWM -- which is my main goal.
Is there a way to overwrite CWM short of going to nvflash. I think I have the files to do a flash, but not the utilities needed to do it. So it would be easier if I could overwrite.
Rev
Click to expand...
Click to collapse
Ah, I was the one who wrote that as I recall. Weeks ago, but it feels like a lot longer. I think earlier revisions of clockworkmod required that or else update.zip file updates would fail. But .08 seems A-OK.
roebeet, et al:
I think it would be a really good thing if folks would confirm what you are saying here -- which is what I experienced last night when I took mine back down to OTA 3053 version.
I was able to setup, flash the 3053 rom and cover up CWM (after doing necessary repairs with it) without doing an nvflash -- just using the recover process.
I think this is important because lots of folks would have the reassurance that they could recover if they make a mistake with only the normal flash procedure.
Or if someone wants to try modding they can know that they will be able to get back to an essentially "stock" machine if they need return/warranty options.
Rev
butchconner said:
roebeet, et al:
I think it would be a really good thing if folks would confirm what you are saying here -- which is what I experienced last night when I took mine back down to OTA 3053 version.
I was able to setup, flash the 3053 rom and cover up CWM (after doing necessary repairs with it) without doing an nvflash -- just using the recover process.
I think this is important because lots of folks would have the reassurance that they could recover if they make a mistake with only the normal flash procedure.
Or if someone wants to try modding they can know that they will be able to get back to an essentially "stock" machine if they need return/warranty options.
Rev
Click to expand...
Click to collapse
At this point I would recommend flashing to 3053 anyway - it's the latest one and you can do the next person who owns your device a favor. I wouldn't even look at the previous two firmware updates, at this point.
For me, it definitely works with cm .08 and it definitely wipes recovery with standard. Do that, plus a user data wipe, and you are 100% vanilla.
Yea!!!!!!
Merry Christmas to All and to all -- how about let's get some sleep and then get down to some serious modding!
Rev
Ok, I've got to ask this, even though I know it could probably be pieced together with just the right posts from the forum here. But I've got several mental issues, one of those being comprehending at times, and also I have a bad problem with wording sometimes. So if I can't find all the information I need in a single place (maybe two lol), then the chances of me screwing something up are immensely increased. So please just bear with me, and lemme see if I can spit this out as simply as possible.
I've just rooted my USCC Mesmerize with SuperOneClick, so now I need to know some things. Forgive me if they seem out of order at all, but just gonna ask as they come to my mind.
I wanted to install the Voodoo kernel. Do I have to flash a custom ROM before I can do this, or can I do it just by rooting the phone and having all the OEM software untouched?
I'm pretty sure that no matter what I choose to do next, that I first need to do a full back-up of my phone in case of error. I saw the post mentioning the install of Titanium Backup and then ROM Manager. Before I go and install anything, I just wanna make sure that it IS one of those 2 apps that I'm supposed to use to make that initial back-up. And if not, what app would it be?
I know that CWM has to be installed sometime also. Also in the same post I mentioned above, the OP stated "In ROM Manager I did "Flash ClockworkMod Recovery" and chose the Fascinate option and was told that it downloaded the latest ClockworkMod Recovery.". So what I now need to clarify is this. Does ROM Manager just download the newest ClockworkMod Recovery files and then I have to install them manually via the forum sticky, or does it download AND install them completely for me?
And I've seen/heard a lot all night as I've been researching about Nandroid back-ups. But am unclear at this point as to which app is responsible for making those. Not sure if it's one I've already mentioned above, or a totally different one I may have missed. So help there would also be much appreciated.
At this moment, I think those are all the questions I really need a little more clarity on. Other than that, I think I can handle it by myself for the time being. And thank you again for bearing with me as I learn my way around a little bit more. I chose this forum out of all the others I stumbled across last night due to the level of professionalism I've seen so far here. I just wish the other Dev forum I've been a member of for a long time had the same level of professionalism that I've seen here so far lol.
lets try this again...
1. first thing you need to do is flash cwm on your phone...follow the directions on the page...link : http://forum.xda-developers.com/showthread.php?t=850898
2. figure out what Rom you wanna flash...link : http://forum.xda-developers.com/forumdisplay.php?f=890
3. finally...flash the voodoo kernel onto your phone and make sure to get the one for the mesmerize...link : http://forum.xda-developers.com/showthread.php?t=871915
4. as far as backing up you can use titanium or flash your mesmerize back to stock...link : http://forum.xda-developers.com/showthread.php?t=881064
all this worked well for me and i hope it works just as well or better for you!
I hate to say this, but you confused the hell out of me and I've written a lot of how-to's on every one of these subjects.
Sent from my SCH-I500 using XDA App
1. Install RomManager from the marketplace. Then, in RomManager, install ClockworkMod Reocvery. However, you need to follow the steps in the CWM thread to get it to work correctly.
2. After you have clockworkmod recovery working, do a Nandroid backup. You can do this from RomManager and should. Titanium backups are for apps and such.
3. After you backup immediately flash the Voodoo kernel for the Mesmerize with Voodoo Sound. It's great! But more importantly, it flashes a 'permanent' recovery onto your phone so you can boot straight into a functional recovery and not have to use ODIN.
4. Find ROMs you like and install them. Make sure you always wipe your data before a ROM flash. When you want to go back to your stock ROM, just restore your backup from the recovery.
Note, after you install the Voodoo kernel it will take a while to boot because it is converting your phone's filesystem. Once you have Voodoo enabled you should not flash another kernel unless you turn off the Voodoo lagfix. This can be done in recovery menu it provides.
Just got my G-Tablet off of WOOT and wanted to let everyone know that it shipped with version 1.1-3389. Just thought I would ease everyones mind around here.
A few others have said the same - thanks! 3389 is a good baseline for mods, FYI.
3588 is what you'd get with the OTA updater, and I would actually recommend doing that first - 3588 came out in January and is a pretty rock-solid stock ROM. It's an even better baseline than 3389, imo. And the 3588 recovery is the only recovery that works with the 3991 UAT, so it might be a requirement for future stock ROMs. We don't know this for a fact yet, but better safe than sorry.
The first thing mine did was update to 1.1-3588. I'm off to figure out how to get the Market on it.
roebeet said:
A few others have said the same - thanks! 3389 is a good baseline for mods, FYI.
3588 is what you'd get with the OTA updater, and I would actually recommend doing that first - 3588 came out in January and is a pretty rock-solid stock ROM. It's an even better baseline than 3389, imo. And the 3588 recovery is the only recovery that works with the 3991 UAT, so it might be a requirement for future stock ROMs. We don't know this for a fact yet, but better safe than sorry.
Click to expand...
Click to collapse
Well apparently there will be a second batch, which I guess mine will be a part of, so there is still a chance for 3991 to still be used.
Just because you're in the second batch to be processed doesn't mean that it's a second batch of tablets. I seriously doubt that they would (or are even could) send out orders based on the build date (oldest units first). The warehouse guys just didn't get to print out your shipping label before the end of their shift.
I'm guessing they are all 3389 - I'm sure they work off the same image.
However, I'd check it anyway - better safe than sorry, imo.
Tonydiv said:
Just because you're in the second batch to be processed doesn't mean that it's a second batch of tablets. I seriously doubt that they would (or are even could) send out orders based on the build date (oldest units first). The warehouse guys just didn't get to print out your shipping label before the end of their shift.
Click to expand...
Click to collapse
Yeah I agree your tablet will be like the rest from woot!!!! So if we even see 3991 it will be a ota update!!!!
sigvader said:
Yeah I agree your tablet will be like the rest from woot!!!! So if we even see 3991 it will be a ota update!!!!
Click to expand...
Click to collapse
If you see 3991 on your Woot tablet, please tell us immediately. I would very shocked at this point if that happened, but then again I didn't expect 3389 either. I really thought they were going to be 3588.
Tonydiv said:
Just because you're in the second batch to be processed doesn't mean that it's a second batch of tablets. I seriously doubt that they would (or are even could) send out orders based on the build date (oldest units first). The warehouse guys just didn't get to print out your shipping label before the end of their shift.
Click to expand...
Click to collapse
One of the woot staffers gave an unofficial update the day after the purchasing ended and said that they were getting a rush shipment on Monday from the vendor to fulfill the second half of the orders. So they are physically a separate set from the first batch.
Just FYI, I got mine today and it was 3389.
Is there a point to doing the update?
Going to flash Vegan and the 5.1.1 add on now.
I copied the update.zip and all the files off the Gtab before I did anything. I'm betting that's a restore to 3389.
Edit: Updater-script says it's 3389.
theroblog.com said:
Just FYI, I got mine today and it was 3389.
Is there a point to doing the update?
Going to flash Vegan and the 5.1.1 add on now.
I copied the update.zip and all the files off the Gtab before I did anything. I'm betting that's a restore to 3389.
Edit: Updater-script says it's 3389.
Click to expand...
Click to collapse
It's not a requirement, but I think it's a good idea to flash to 3588 first. The reason is that you'll get the latest bootloader and recovery, which ROMs like VEGAn don't touch.
Recovery is the one that concerns me, as 3588 recovery seems to be a kind of "gateway" recovery that might (and I stress "might") be needed to get you to a future firmware level. So, imo, I would flash to 3588 first, THEN start using ROMs if you want. It's a safer bet, again imo.
Thanks for the confirm on that update.zip -- sounds like it's stock 3389, like you mentioned.
received my tablet from woot today. ill post back as soon as its charged and powered up with the version.
roebeet said:
It's not a requirement, but I think it's a good idea to flash to 3588 first. The reason is that you'll get the latest bootloader and recovery, which ROMs like VEGAn don't touch.
Recovery is the one that concerns me, as 3588 recovery seems to be a kind of "gateway" recovery that might (and I stress "might") be needed to get you to a future firmware level. So, imo, I would flash to 3588 first, THEN start using ROMs if you want. It's a safer bet, again imo.
Thanks for the confirm on that update.zip -- sounds like it's stock 3389, like you mentioned.
Click to expand...
Click to collapse
I am new to all this, so excuse me for some newbie questions.
Most of the walkthroughs to install a moded ROM, seem to install Clockworkmod first. How is that different from what you call "recovery" here. Will it replace the stock 3588 recovery? Or by the "3588 recovery" do you mean the bootloader part that calls the Clockworkmod. Is there a way to install a ROM without Clockworkmod? This is specifically for 3588.
I ask because I see some discussions about TNT Lite 5 where it seems to break with Clockworkmod. So if we want to get to TNT Lite 5 in the near future, should we now install Clockworkmod?
I am asking this specifically for the woot buyers who it looks like get 3389->3588
Any pointers would be very helpful.
thanks
cbay said:
I am new to all this, so excuse me for some newbie questions.
Most of the walkthroughs to install a moded ROM, seem to install Clockworkmod first. How is that different from what you call "recovery" here. Will it replace the stock 3588 recovery? Or by the "3588 recovery" do you mean the bootloader part that calls the Clockworkmod. Is there a way to install a ROM without Clockworkmod? This is specifically for 3588.
I ask because I see some discussions about TNT Lite 5 where it seems to break with Clockworkmod. So if we want to get to TNT Lite 5 in the near future, should we now install Clockworkmod?
I am asking this specifically for the woot buyers who it looks like get 3389->3588
Any pointers would be very helpful.
thanks
Click to expand...
Click to collapse
Clockworkmod is non-vendor third party recovery replacement, wheras "standard recovery" is stock recovery (this is what the vendor supplies).
TNT Lite 5 was pulled after about a week, due to more than a few issues where users were soft bricking their devices. Going on metrics I tried to compile, the majority of the problems stemmed from the use of clockworkmod, thus my reasoning for not recommending its use anymore. This is despite the fact that the update it was based on was a non-released firmware. I will explain further. Btw, we are seeing similar issues over in the Notion Ink Adam forums in notioninkhacks.com, for the same exact reasons (clockworkmod).
In the case of the GTAB, the vendor (Viewsonic) adds the bootloader.bin to its stock update firmware. And it has been updated at least twice tmk - once in a November firmware update, once in a December firmware update. And also with this 3991 UAT update, but for the sake of argument we won't count that one. But they have updated it in released firmware.
But clockworkmod users do not get that update, as the program doesn't support updating the bootloader.
3388 to 3588 seems to have the same bootloader so, for the short term, using clockworkmod is probably OK. But there is no guarantee that a future update will not require a bootloader change. Again, we have already seen this happen with the NI Adam, and also the Viewsonic non-released UAT. So, with all that being said, I cannot recommend Clockworkmod as a flashing tool.
I've actually kept TNT Lite 5 (which is now TwoTapsX) on ICE specifically because of the expected surge of new Woot users. The last thing I want to happen is for a large number of inexperienced users with mixed information to flash that firmware with the wrong tool (clockworkmod) and then soft-brick their device.
I actually require clockworkmod for my gADAM mod because that mod requires a user data wipe, which standard recovery does not support. But gADAM has a "Recovery Pack" built-in - what this does is allow the user to easily flip between standard recovery and clockworkmod, as needed. Since gADAM is a 1.1-based mod, the use of clockworkmod to flash it is low risk. But if you later flashed to a mod that might require a new bootloader, the Recovery Tool allows you to put standard recovery back before you flash again.
I know this is all very confusing - believe me, it is for me as well. Suffice is to say that modded ROMs are risky business and you should read the instructions very carefully before proceeding. I have started to add the firmware type in my own ROMs as a guide - "1.1" for example. So, a "1.1" to "1.1" firmware mod change should be a low risk, for example. Right now, most of the stock ROMs and probably all the modded ROMs are "1.1" based.
If it is possible, maybe some admin could update the last message in the thread (http://forum.xda-developers.com/showthread.php?t=1006571) you had posted on woot's discussion page. Either link here, or just update and say: hey, people got some woot gTabs in already and they are the 3389 version.
I read this above post, but have not received my woot gTab (so no idea what version I'm getting). Good thing I searched first and found this post. Just to put my mind at ease
eak0703 said:
If it is possible, maybe some admin could update the last message in the thread (http://forum.xda-developers.com/showthread.php?t=1006571) you had posted on woot's discussion page. Either link here, or just update and say: hey, people got some woot gTabs in already and they are the 3389 version.
I read this above post, but have not received my woot gTab (so no idea what version I'm getting). Good thing I searched first and found this post. Just to put my mind at ease
Click to expand...
Click to collapse
i can't update it as the moderators locked it (trust me, I want to update it). I already PM'd jerdog to either open it up or delete it, as I don't think it's needed anymore. I'm not a moderator so I cannot do this, myself.
EDIT: It's been unstickied and updated. TheImpaler handled the unsticky / unlock.
roebeet said:
Clockworkmod is non-vendor third party recovery replacement, wheras "standard recovery" is stock recovery (this is what the vendor supplies).
But clockworkmod users do not get that update, as the program doesn't support updating the bootloader.
Click to expand...
Click to collapse
Thanks for the detailed answer Roebeet!
CWM not updating the bootloader is the main problem isnt it?
Also that it overwrites stock recovery.(True?)
If CWM overwites stock recovery, reverting to 3588 using CWM, might still not enable things like OTA update, right?
So, I see that CWM will work with current ROMS (except TNT Lite 5) and everyone will be happy till the newer ROMS come along based on 3991 or later. At that point, it will become a lot harder for people to get to the new ROM as the new bootloader will have certainly changed.
Alternatively, if people wait for a Viewsonic 3991 or later OTA update from Viewsonic, CWM will work again for some time until the bootloader changes significantly. (possibly).
So how does one get a new ROM without CWM?
I have searched some on the forums and I see
1. Use CWM, but comment out some "assert". This was used by people reverting to stock, and seems sketchy.
2. Use nvflash. Is there a walkthrough for this for Vegan/TNT Lite? I see one for going to bekit 's original image but not to any arbitrary ROM. Also this repartitions the SD, has this caused problems with OTA updates?
3.Using adb. Maybe 2 and 3 are related, but I think did see somewhere to get back to stock recovery using adb. Can we do a new rom update through adb, without risking breaking stock recovery?
I wish I had bought 2 gtablets, one to enjoy and one to tinker with
cbay said:
Thanks for the detailed answer Roebeet!
CWM not updating the bootloader is the main problem isnt it?
Click to expand...
Click to collapse
Correct.
cbay said:
Also that it overwrites stock recovery.(True?)
Click to expand...
Click to collapse
Yes, they cannot co-exist. Stock recovery (specifically 3588) will update the bootloader, I've tested this repeatedly. clockworkmod .8 does not.
cbay said:
If CWM overwites stock recovery, reverting to 3588 using CWM, might still not enable things like OTA update, right?
Click to expand...
Click to collapse
Not exactly. If you have cwm and revert to stock 3588, you might not have the latest bootloader (since clockworkmod doesn't touch that) but everything else should be reverted back to stock. But an important note: I've heard stories from users who used clockworkmod to revert to 3588 stock and, although it worked, recovery was actually broken. This happened to a lot of users who were trying to get back to 3588 stock before they upgraded to my later-pulled TNT Lite 5. This is actually the reason why I created the 3588 Recovery Pack.
cbay said:
So, I see that CWM will work with current ROMS (except TNT Lite 5) and everyone will be happy till the newer ROMS come along based on 3991 or later. At that point, it will become a lot harder for people to get to the new ROM as the new bootloader will have certainly changed.
Alternatively, if people wait for a Viewsonic 3991 or later OTA update from Viewsonic, CWM will work again for some time until the bootloader changes significantly. (possibly).
Click to expand...
Click to collapse
Possibly. Lets assume for a moment that the new firmware is a released "1.2" with a new bootloader. Once everyone moves off the "1.1" to "1.2", the issues with the bootloader will probably stabilize. Until there's a "1.3", of course.
And yes, this is all speculation. Viewsonic could throw us a curve balll with their next firmware.
cbay said:
So how does one get a new ROM without CWM?
I have searched some on the forums and I see
1. Use CWM, but comment out some "assert". This was used by people reverting to stock, and seems sketchy.
2. Use nvflash. Is there a walkthrough for this for Vegan/TNT Lite? I see one for going to bekit 's original image but not to any arbitrary ROM. Also this repartitions the SD, has this caused problems with OTA updates?
3.Using adb. Maybe 2 and 3 are related, but I think did see somewhere to get back to stock recovery using adb. Can we do a new rom update through adb, without risking breaking stock recovery?
I wish I had bought 2 gtablets, one to enjoy and one to tinker with
Click to expand...
Click to collapse
Right as the Wooters were buying their GTABs, I did a few things to help users out with recovery options.
1) I created a "3588 Recovery Pack". This is a flash update.zip that will add few sripts to your rooted 1.1-based ROM and will allow you to flip between clockworkmod and 3588 stock recovery with a minimum of fuss.
2) I added the Recovery Pack to TNT Lite 4.3.0 and gADAM 1.3.0, the two active mods that I support. So it's built-in there.
nvflash is a different animal. Think of it as a low-level format tool for when your device is messed up and cannot boot anymore. It's good to know about it and learn how to use it, imo - some devices like the Advent VEGA and even Viewsonic's Viewpad10s offer nvflash updates, only. nvflash is a tool specifically for Tegra 2 devices.
adb is a generic "remote shell" tool that is part of the Android SDK. You can find information about adb here or on other Android sites, and that would apply to the GTAB as well. you can make changes via adb, including flash updates, but you need to know what you're doing.
roebeet said:
2) I added the Recovery Pack to TNT Lite 4.3.0 and gADAM 1.3.0, the two active mods that I support. So it's built-in there.
Click to expand...
Click to collapse
That is great! I dont think I will have the patience to wait for Viewsonic to release an update beyond a few weeks.
I was debating between Vegan and TNT Lite, the Recovery Pack will push me towards TNT Lite, at least till I can get a 1.2 bootloader.
Thanks for all the help
--
Recently received G tablet from woot
I'm new to this and would like to know what the best thing to do to my viewsonic g tablet purchased from woot that makes it run the best way. I'm not sure how many and what mod's are recommneded. I've read alot of the posts here and figure TNT Lite (version?) is highly recommended. It is 3588, build frf91. Please give me the best mod's to do, what versions, and where I can find the step-by-step to make it all happen. thanks
(moderators - I know this probably belongs in apps, but I feel this is so critical that it should really be in General, right now)
This is one of those things that general forum is aware of, but I wanted to state it here, as I have seen this mentioned several times in the Woot! forum as well as at least two PM's I've received in the last two days.
PLEASE DO NOT USE THE CLOCKWORKMOD IN ROM MANAGER. IT DOES NOT WORK AND YOU WILL LIKELY SOFT BRICK YOUR DEVICE IF YOU FLASH FIRMWARE WITH IT.
To be sure, I just installed clockworkmod from ROM Manager TODAY, and ran one of of mods to see if the issue still existed. And it does. What happens is that, after flashing you might see this message:
"Magic Value Mismatch"
At this point, you have soft-bricked your device and you will need nvflash to fix it. Do yourself a favor and don't get yourself in this situation - avoid avoid avoid ROM Manager like it was the plague.
There is only one version of clockworkmod that is known to work reliably with the GTAB, and that's bekit's .8 version. There are links to it in my mods and in other threads, here. Make sure it's the .8 bekit version, if you want to use clockworkmod.
Note: To make things even more confusing, there are actually TWO versions of bekit's .8 version (that's my fault), One is for legacy 1.1 mods, and one is for 1.2 mods. Most of the links are for the 1.1-based version - the only time you'll probably see the 1.2-based version is with TwoTapsX. Just be aware that there are two of them.
For the 1.2-based one, it has "TNTlite5" in the file name. That's how you'll know.
If you decide to use the .8 bekit recovery don't install the clockwork app. To many people have accidentally installed a different recovery and softbricked their tab as cwm prompts you to "update" your recovery when opening the app. You can do everything from recovery that the app does for you.
Sent from my Chromatic Magic using XDA Premium App
Hello everyone. This is my first post, so please be gentle. I've been reading around and I can't seem to find specific answers to my questions so I figured it would be best to make a post. This is my first Android phone and also the first phone I have rooted so I'm trying to be extra careful. I've already received tons of help from other threads in these forums, but as I said I've still got a few questions.
I rooted my SGS4G using SuperOneClick v2.1.1, then proceeded to install CWM ROM Manager as per the instructions I found in many articles online. Once I got that installed I was unable to make backups as it would boot me into the stock recovery menu, which led me here searching for answers. That is when I came across this thread: [RECOVERY]CWM FINAL for the SGS4G After following the instructions I wasn't exactly sure what to do, so I attempted to boot into the "new" recovery menu which ended at an infinite boot logo, which I assumed was a soft brick after reading around a bit.
After thoroughly freaking out about my phone being bricked I looked around a bit more and came across this thread: [GUIDE] Noobs guide to Odin to flash your SGS4G (Windows) Following that thread I was able to install the T959VUVKB5 Stock + Root ROM which restored my soft brick. Once that was installed I installed CWM ROM Manager again thinking the Recovery Menu would be fixed and I could finally make a backup before moving on, but it wasn't. Then I came across this thread: [Odin][Kernel] drhonk's Bali 3.3 for Froyo, Installs CWM!
After installing drhonk's Bali 3.3 for Froyo kernel I was finally able to make a single nandroid backup (and backup my apps using Titanium Backup)! I messed around on the phone for a few days with no issues (other than the Android flickering in the boot logo). Now I am ready to move on to trying out a few ROMS. So, first thing first I said: I need to make another backup. So I entered the Recovery Menu via the CWM ROM Manager and attempted to make another backup, and this is what I get:
E: failed to open /etc..... (I couldn't write fast enough to copy the entire message)
E: unknown volume for path [/sdcard] (10s)
The second of which repeated over and over until it reached 0s and then my phone was rebooted.
TL;DR
- Rooted using SuperOneClick
- Installed ROM Manager and couldn't make a nandroid backup correctly
- Attempted to install CWM FINAL for the SGS4G, which resulted in a soft brick
- Restored using ODIN and installed T959VUVKB5 Stock + Root ROM and drhonk's Bali 3.3 for Froyo kernel
- Cannot make nandroid backups (other than the initial one apparently), Recovery Menu does not seem to be working correctly
- I am not comfortable trying new ROMs until I am able to make backups correctly
Anyway, so here are my questions:
1. What do I need to install to allow me to make nandroid backups correctly? Or is there another app besides CWM ROM Manager that will allow me to do this?
2. I would like to try a few other ROMs, but I when I reach the so-called "Do the mounting stuff" step I am unable to continue as my Recovery Menu isn't working correctly. What do I need to install in order to be able to do complete this step? I have a feeling the answer to #1 will solve #2 as well.
3. I would like to try a few of the GB ROMs (such as Valhalla v1.3.2 or Stock Gingerbread 2.3.3 Deodexed + Root), but I am not sure exactly where to go from here. Is the GB Ext4 Starter Pack the way I need to go, or would this way be better? Can I do either of these without a working Recovery Menu?
Thanks in advance for all the help!
Your first mistake was rom manager. It does not work for this phone correctly. Odin one of Dr honks kernels to get cwm recovery. They are in the dev section.
Sent from my SGH-T959V using xda premium
im not sure how many times this has been posted (i think i say this once a day....) but rom manager DOES NOT WORK ON THIS PHONE.
it is fine. if you can wait a day or two, i will make a nice noob guide on getting from stock to a custom rom. i will be sure to link every pertinent thread and be sure to have a little FAQ section. hopefully it will help you.
Exodian said:
Your first mistake was rom manager. It does not work for this phone correctly. Odin one of Dr honks kernels to get cwm recovery. They are in the dev section.
Click to expand...
Click to collapse
As I said in the post, I've already installed drhonk's Bali 3.3 for froyo kernel.
jager555 said:
im not sure how many times this has been posted (i think i say this once a day....) but rom manager DOES NOT WORK ON THIS PHONE.
it is fine. if you can wait a day or two, i will make a nice noob guide on getting from stock to a custom rom. i will be sure to link every pertinent thread and be sure to have a little FAQ section. hopefully it will help you.
Click to expand...
Click to collapse
Thanks, but I figured that out shortly after installing it. What alternative are we supposed to use? Hopefully your noob guide will help.
are you sure you understand? seeing as you mentioned BOTH bali and krylon's cwm, yet you still do not know how to get the custom recovery on the phone. once again, i will write a nice guide for you, so for now, just odin back to stock and give me a day or two. once im out of work, i will take a nap and write this for you.
jager555 said:
are you sure you understand? seeing as you mentioned BOTH bali and krylon's cwm, yet you still do not know how to get the custom recovery on the phone. once again, i will write a nice guide for you, so for now, just odin back to stock and give me a day or two. once im out of work, i will take a nap and write this for you.
Click to expand...
Click to collapse
Apparently I do not understand. I guess I will just wait for your guide. Hopefully it will pick up where the other guides failed (for me anyway).
Edit: After reading around a bit I think I understand where I went wrong. As a noob I was confusing CWM with ROM Manager (after all, they're both made by the same people right? I believe that's what was confusing me ). I have since uninstalled ROM Manager and have booted to the Recovery Menu and successfully made a backup.
I myself have been a member for coming up on one year. And when I originally joined I was modding my Mytouch 3G. Much easier phone to mod and especially with ROM manager. This phone on the other hand requires more attention to detail. It is very important to do your due diligence to research this site for answers before posting. The reason is, all the wonderful and talented folks making all this possible are providing us all these great hacks, cracks, and roms for free. The information is here if you just look for it. Now if you are having trouble understanding the info that is also understandable. I find questions are better received if you show everyone what you have researched and then say what your are confused about.
Enough of the lecture, the end result is that everyone here is really nice and helpful. Here are the 3 links you should save. The Bible lists everything about our phone. Now at this stage in the game unless you really want to get more background on how the phone has evolved from Froyo to GB you won't need to read the Bible. The first thing you will need to do is follow the instructions for Bali 3.3 + CWM. This will provide you with the Red CWM recovery making it possible for you to flash Froyo Roms. Once you have completed this step you can move on to the GB Starter Pack. This guide will prepare your phone with the correct bootloaders it requires to run GB Roms. Once this process has been completed you can flash GB Roms. And if you need a quick list of the roms available just look in the Bible. Hope this helps, just be patient and make sure you understand what you are reading and attempting before doing anything. And if you don't understand a step or a process then come and ask and you'll get better answers and better understanding of what you're actually doing to your phone.
SGS4G Bible
http://forum.xda-developers.com/showthread.php?t=1117554
Bali 3.3 + CWM
http://forum.xda-developers.com/showthread.php?t=1195860
GB Starter Pack
http://forum.xda-developers.com/showthread.php?t=1223765
Thanks for the help. I tried to do as much research as I could before posting (as you can see, I've posted two of the three links you suggested in my OP, and I basically keep the Bible open at all times ). It's just the little things that I find confusing, which is why I posted this thread. It's nice to know that from this point I can proceed to the GB Starter Pack and play around with the GB ROMs, but I think I'd like to try a few Froyo ROMs before I take that step Thanks for confirming that!
Sorry for the double post but I have another question.....
I've been reading over FB's GB Ext4 Starter Pack thread and I just wanted to make sure that once you get to the part where you flash your "favorite GB rom" that Valhalla v1.3.2 would be an acceptable ROM to flash there. If not, which ROM should I flash first, then flash Valhalla? Thanks in advance.
Yes, Valhalla would be fine to flash at that point (any version). just as long as you went through each step of the directions first. you'll be fine.