Database Info

Received WOOT Tablet - Answering Version Questions

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

An open letter to the Woot users, in regards to my mods

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

[Q] Droid Charge Full backup?

I've had my Charge for a few weeks now. I've been silently reading the forum this whole time. I've downloaded the tools and I'm ready to kernel/root/rom it... But I like to be cautious. Everyone always says "HAVE A BACKUP YOU TARD!" but I can't seem to find any information on the topic pre-root.
So... Is there some way to backup everything on the phone prior to tinkering with it so I can put it back if something goes bad?
I did search.. Couldn't find anything for the droid. Lots of mentions of titanium. I downloaded it but it's for rooted phones as well.

No. Clockwork doesn't do a proper backup now. (And it doesn't back up the kernel anyway.)
Just changing the kernel and rooting won't alter anything that flashing the original kernel can't undo. So do that, get Titanium (I suggest the pro version, since it's the flasher's best friend), and use that to back up your user apps before you take the step of flashing a full ROM.

I'm a total newbie to this stuff, so this is something I've been wondering about as well.
s44- So changing the kernel and rooting you would say is a pretty safe venture to start with? I'm a fairly technical guy in general, but haven't ventured into the realm of phone rooting before, so I'm a little anxious about possibly bricking my phone right after I got it.
Is there something I would need to do beforehand to enable me to flash the original kernel, or is that just something you can always do after rooting? Thanks for any info.

We have odin. Thanks to odin we can always flash back to stock rom. If you look at the development forum you will find the stock package that no matter what you do you can always go back. Just dont mess with the radio or the pit file. Always us pda in odin unless you are flashing a new radio and you are instricted todo so. For user apps and data you can use titanium backup
Sent from my SCH-I510 using XDA Premium App

Excellent, thanks. I assume you're referring to the stock ROM at this link? http://forum.xda-developers.com/showthread.php?t=1085190
What exactly does flashing a new radio do? I'm not really familiar with the terminology

ColonelSeitan said:
Excellent, thanks. I assume you're referring to the stock ROM at this link? http://forum.xda-developers.com/showthread.php?t=1085190
What exactly does flashing a new radio do? I'm not really familiar with the terminology
Click to expand...
Click to collapse
Flashing a new radio means replacing the current modem/voice radio's software with a new/different one. There's currently no flashable radio softwares that I know of for the Charge. There are two radio softwares for the phone, though: the original version shipped with the phone, and the new one that started rolling out last week with the EE4 OTA update. That update is a patch to the old radio software (a patch is a method that changes only portion of the current software rather than overwriting the whole thing).
Hope that helps you understand a bit better.

Can't back up my phone.
I'm sorry if someone already posted this. I've been hours at it re installing ROMs. I have GummyCharged 2.0. I've tried doing a nandroid back up for the past couple of days. I've tried Rom Manager to back it up many different times and every time it shows that open box for a few seconds then it's just the android with a triangle /!\. I've tried backing up while on Recovery but at the end it can't find my SD-ext and doesnt back up. I can't find anything online relating to it. I'm gonna reinstall the stock and root it. I'll back up every time I change my phone and see when exactly it starts to fail. I'm still a noob at this.

BlackMagicNights said:
I'm sorry if someone already posted this. I've been hours at it re installing ROMs. I have GummyCharged 2.0. I've tried doing a nandroid back up for the past couple of days. I've tried Rom Manager to back it up many different times and every time it shows that open box for a few seconds then it's just the android with a triangle /!\. I've tried backing up while on Recovery but at the end it can't find my SD-ext and doesnt back up. I can't find anything online relating to it. I'm gonna reinstall the stock and root it. I'll back up every time I change my phone and see when exactly it starts to fail. I'm still a noob at this.
Click to expand...
Click to collapse
first of all don't use Rom Manager for anything on the Charge as it doesn't work right... second of all nandroid backups can be made on Gummy 2.0, you would need the most up to date CWM from Imnuts thread here: http://forum.xda-developers.com/showthread.php?t=1112804, it should be orange and version 4.0.1.4

BlackMagicNights said:
I'm sorry if someone already posted this. I've been hours at it re installing ROMs. I have GummyCharged 2.0. I've tried doing a nandroid back up for the past couple of days. I've tried Rom Manager to back it up many different times and every time it shows that open box for a few seconds then it's just the android with a triangle /!\. I've tried backing up while on Recovery but at the end it can't find my SD-ext and doesnt back up. I can't find anything online relating to it. I'm gonna reinstall the stock and root it. I'll back up every time I change my phone and see when exactly it starts to fail. I'm still a noob at this.
Click to expand...
Click to collapse
Rom Manager and the Charge do NOT work.
Make sure you're using the latest Recovery as that's the only one that's able to backup/restore and even then there's known to be issues.

Just gonna latch on here since this is a pretty recent last post...
I have recovery 4.0.0.8 and am trying to go to gummycharge GBE 2.0RC1.5, do I need to update my recovery first? I'm assuming I do to backup, but just wanted to confirm. And on the subject of updating recovery, I use ODIN just like I did for Gummy (except following what it says on that link, no auto reboot)?
Thanks, I've done enough rooting in the past, but not too familiar with CWM updating and ODIN.

JLCollier2005 said:
Just gonna latch on here since this is a pretty recent last post...
I have recovery 4.0.0.8 and am trying to go to gummycharge GBE 2.0RC1.5, do I need to update my recovery first? I'm assuming I do to backup, but just wanted to confirm. And on the subject of updating recovery, I use ODIN just like I did for Gummy (except following what it says on that link, no auto reboot)?
Thanks, I've done enough rooting in the past, but not too familiar with CWM updating and ODIN.
Click to expand...
Click to collapse
if you're trying to do a CWM backup first then yes you would need to update CWM to the latest 8/17 build which you can odin separately... odining or flashing the new Gummy rom should update your kernel and thus update CWM

What is the latest cwm for droid charge. I had 5.0 on tunderbolt now only have 3.0 on Charge.

mickrg123 said:
What is the latest cwm for droid charge. I had 5.0 on tunderbolt now only have 3.0 on Charge.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1112804

v4.0.1.4...backup no workee...MD5 mismatch!
When attempting to run a backup via CWM v4.0.1.4 I get MD5 mismatch! Yes...Im on the ROM that I'm attempting to backup. Any help would be kick [email protected]#...

Here's my 5 cents for what it's worth.
I only backup what I really need, rather than a full backup - that way I know I keep the DATA, not the old apps, outdated cache and setting etc.
To do this I use:
SMS Backup+ : Backs up SMS, Call Log
Evernote : I keep notes, screenshots, voice memos etc in sync using evernote. This of course only works if you like evernote
Eye-Fi : I move all my pictures of the phone using Eye-Fi. This cost of course, sorry, but it works (Plus you get a cool SD card for your digital camera). Other options exists, I hear a lot of good stuff about SugarSync.
Market and Amazon : All you apps are already backed up on Google Android Market or Amazon (dep. on where you bought/downloaded them from). Some people wants everything re-installed from the get go. I prefer re-install when I need it, I'm always near 4G so it literally takes seconds.
This has been working so well that I now don't think twice before factory resetting or upgrading firmware. I just do it.
Hope that helped...

[Q] "How-to" root VRBLK3 "CLN" delivered today?

I am fairly certain that simply using Odin 3.07 to change the recovery from stock/OEM to CWM 6.0.1.3 touch and than using that (CWM recovery) to flash the "SuperSU + Unlocked bootloader" found in the thread telling you how to flash the JB update with no data wipe is all I need to do (right?)...
Does anyone have any pointers or tips, or am I the first in line with such a thing? (i.e. JB pre-installed on a "Certified Like New" phone)

Check this out:
http://forum.xda-developers.com/showthread.php?t=2046439
Or your way also works.

MUST use ICS bootchain to flash custom recovery in JB ROM (at least for now)
aooga said:
Check this out:
http://forum.xda-developers.com/showthread.php?t=2046439
Or your way also works.
Click to expand...
Click to collapse
Thanks, much! "My way" does NOT work, actually: the way layed out in the reference you linked DOES work, however. :highfive:
Interesting that they added a little booger that sees that the "CWM 6 Touch" recovery is invalid and will not allow Odin to flash it. Fortunately, somebody is already ahead of me in the line and already figured out how to jump through the hoops to 'get 'er done'!
Sorry I had to create a new thread, I tried to find anything that related to my specific scenario even using the search properly. I guess his write-up doesn't specifically address my situation (receiving a newly "CLN" phone with VRBLK3 firmware already on it), but it certainly does the trick. I'll add a comment "over there" as well.
As always - the XDA-Dev community rocks! :victory:
Now, upward and onward with my 5th VZW GS3... Time to unleash Titanium Backup on it and restore my most recent copies of everything. Ah, the sweet smell of excess.

6045i usa latest 5.0.2-01001

hello i am rooted with twrp recovery installed. I was able to unroot and download the latest 5.0.2-01001 ota but im not able to install the update it would just take me to twrp recovery and stop there.?? i found the update zip and tried to flash it in twrp but it says it cant mount and failed to flash any help would be appreciated.

OTA updates will require a stock recovery. I'm in the process of getting an Idol 3 but I used to have an Idol 2 and, to return to a completely stock ROM, I had to use the Alcatel Mobile upgrade too which identified my phone, downloaded the correct firmware, and restored the phone. Prior to restoring back to stock, I had cwm and root.

Thanks for the reply I tried the software update but its not working keep saying I have the latest even when I did a full wipe. Using the latest 4.9.2 version...is there a way to make a twrp flashable ota zip from the downloaded update file in the ota cache..

lude86 said:
hello i am rooted with twrp recovery installed. I was able to unroot and download the latest 5.0.2-01001 ota but im not able to install the update it would just take me to twrp recovery and stop there.?? i found the update zip and tried to flash it in twrp but it says it cant mount and failed to flash any help would be appreciated.
Click to expand...
Click to collapse
You cannot be rooted and install a stock update...it's mentioned in several places throughout the forum. Quickest solution is to use the mobile q to restore the whole phone to factory (and in the process it will put the latest version on it). Otherwise you have to fully unroot AND if you have modified any files such as build.prop or other system files it still won't work. You CAN install with TWRP however in the process of the install it will overwrite it with stock recovery. If I had to guess I'd say you did not do the supersu FULL unroot.

famewolf said:
You cannot be rooted and install a stock update...it's mentioned in several places throughout the forum. Quickest solution is to use the mobile q to restore the whole phone to factory (and in the process it will put the latest version on it). Otherwise you have to fully unroot AND if you have modified any files such as build.prop or other system files it still won't work. You CAN install with TWRP however in the process of the install it will overwrite it with stock recovery. If I had to guess I'd say you did not do the supersu FULL unroot.
Click to expand...
Click to collapse
mobile Q is horse manure now. I ran into the same problem, whereby it says you're up to date (which it's not), even if you're running 5.0.2.7SMA-UEA1 ! I only know that one because I inadvertently flashed 5.0.2.7SMA-UEA1 today when I meant to flash 5.0.2.7SRA-UEA2.
Speaking of 5.0.2-01001, 5.0.2.7SRA-UEA2 is on longer the latest yeah... anyway we can update the firmware page? http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I just tried to OTA update to 5.0.2-01001, but OTA of course does not work if TWRP is acting recovery; it just reboots to TWRP and then if you reboot system, nothing happens. Although seemingly never mentioned, we must remove TWRP (even read only TWRP) before updating OTA?

tekka-maki said:
mobile Q is horse manure now. I ran into the same problem, whereby it says you're up to date (which it's not), even if you're running 5.0.2.7SMA-UEA1 ! I only know that one because I inadvertently flashed 5.0.2.7SMA-UEA1 today when I meant to flash 5.0.2.7SRA-UEA2.
Speaking of 5.0.2-01001, 5.0.2.7SRA-UEA2 is on longer the latest yeah... anyway we can update the firmware page? http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I just tried to OTA update to 5.0.2-01001, but OTA of course does not work if TWRP is acting recovery; it just reboots to TWRP and then if you reboot system, nothing happens. Although seemingly never mentioned, we must remove TWRP (even read only TWRP) before updating OTA?
Click to expand...
Click to collapse
The thread is closed. There is also no reason you NEED the most recent posted as you can flash any of them and then do an update. Mobile Q is the recommended method to re-do your phone if you can't manage to make a backup before messing with it. It has apparently worked just fine for people in this forum for every model type mentioned so the burden of proof is on your part if you can't get it to work.

famewolf said:
The thread is closed. There is also no reason you NEED the most recent posted as you can flash any of them and then do an update. Mobile Q is the recommended method to re-do your phone if you can't manage to make a backup before messing with it. It has apparently worked just fine for people in this forum for every model type mentioned so the burden of proof is on your part if you can't get it to work.
Click to expand...
Click to collapse
Why would the thread be 'closed'. OP's problem is unresolved.
'Worked' is the operative term for. Perhaps you haven't used to Mobile Q tool lately? As OP (and I) said (today), running OTA from 6045 now just reboots to TWRP, no install. Alternately, when attempting to update 6045 from Mobile Q, it just throws a funny English 'update no needed' kinduva message (pic). Incidentally, have you been to their website to find an update to this tool? Holy crap, in that respect, Mobile Q must be a virtual breakthrough for these boys! :laugh:
You're so helpful here famewolf. I've both appreciated and have been comforted by seeing your knowledge all over this subforum, since day 1. Please provide help. You tell me where this 'people' person is, and I'll wank on his boner for you. Then we have a definition of 'working fine' in stead of 'worked fine'. ? :angel:

tekka-maki said:
Why would the thread be 'closed'. OP's problem is unresolved.
'Worked' is the operative term for. Perhaps you haven't used to Mobile Q tool lately? As OP (and I) said (today), running OTA from 6045 now just reboots to TWRP, no install. Alternately, when attempting to update 6045 from Mobile Q, it just throws a funny English 'update no needed' kinduva message (pic). Incidentally, have you been to their website to find an update to this tool? Holy crap, in that respect, Mobile Q must be a virtual breakthrough for these boys! :laugh:
You're so helpful here famewolf. I've both appreciated and have been comforted by seeing your knowledge all over this subforum, since day 1. Please provide help. You tell me where this 'people' person is, and I'll wank on his boner for you. Then we have a definition of 'working fine' in stead of 'worked fine'. ? :angel:
Click to expand...
Click to collapse
The thread that is closed is the one YOU mentioned.... not the op. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I dont use mobile Q as I use Linux and they don't have a linux version. I use 3rd party roms such as AICP with the ARDE non OC rom. TWRP puts a log in /tmp...did you look at what the error message says? OTA updates will NOT apply if you have updated system files such as build.prop. Thats all I can tell you because I can't try what you are using.

famewolf said:
The thread that is closed is the one YOU mentioned.... not the op. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
I dont use mobile Q as I use Linux and they don't have a linux version. I use 3rd party roms such as AICP with the ARDE non OC rom. TWRP puts a log in /tmp...did you look at what the error message says? OTA updates will NOT apply if you have updated system files such as build.prop. Thats all I can tell you because I can't try what you are using.
Click to expand...
Click to collapse
I haven't updated the build.prop, I doubt the OP has either.
'There is no greater software version available to upgrade your phone,actual version of your phone is the latest'
Hehe! Only thing that would make this funnier is if they misspelled 'version'. At least I can derive some amusement from that message and their ****ty, convoluted website.
Shame you can't help on that front, but maybe you can at least guide me on what should be normal flow of this procedure.
When one does OTA update unrooted (but with custom recovery), at the point that the phone reboots, it should not (in theory) boot into TWRP right? I would think just continue with update, and maybe that's why I would need to remove TWRP in favor of stock recovery.
It would be easier to attack it from that angle as opposed to their crappy win32 program. which they probably didn't pay the GoDaddy bill on.:laugh:
I don't even know why I'm bothering as it's just a backup phone now. I just find it ridiculous that I can get their last measly update either from Q or from device (ostensibly so long as custom recovery remains). Holy bejebus, updating Shamu is so painless (6.0.1)
---------- Post added at 08:41 PM ---------- Previous post was at 08:22 PM ----------
likely they have not updated their server side to to UEN0 from UEA2 for their craptacular tool which would explain that problem.
Curious, did you lose Band 12 with UEN0. I haven't heard anything positive from this most recent update that is giving me a headache to get to. Perhaps it's for naught. They don't even have a changelog do they. Meh... I'm going to forget about it until something notable comes along or maybe even just sell this thing while I might still get over a hundred.

tekka-maki said:
I haven't updated the build.prop, I doubt the OP has either.
'There is no greater software version available to upgrade your phone,actual version of your phone is the latest'
Hehe! Only thing that would make this funnier is if they misspelled 'version'. At least I can derive some amusement from that message and their ****ty, convoluted website.
Shame you can't help on that front, but maybe you can at least guide me on what should be normal flow of this procedure.
When one does OTA update unrooted (but with custom recovery), at the point that the phone reboots, it should not (in theory) boot into TWRP right? I would think just continue with update, and maybe that's why I would need to remove TWRP in favor of stock recovery.
It would be easier to attack it from that angle as opposed to their crappy win32 program. which they probably didn't pay the GoDaddy bill on.:laugh:
I don't even know why I'm bothering as it's just a backup phone now. I just find it ridiculous that I can get their last measly update either from Q or from device (ostensibly so long as custom recovery remains). Holy bejebus, updating Shamu is so painless (6.0.1)
---------- Post added at 08:41 PM ---------- Previous post was at 08:22 PM ----------
likely they have not updated their server side to to UEN0 from UEA2 for their craptacular tool which would explain that problem.
Curious, did you lose Band 12 with UEN0. I haven't heard anything positive from this most recent update that is giving me a headache to get to. Perhaps it's for naught. They don't even have a changelog do they. Meh... I'm going to forget about it until something notable comes along or maybe even just sell this thing while I might still get over a hundred.
Click to expand...
Click to collapse
As I mentioned here: http://forum.xda-developers.com/showpost.php?p=64967202&postcount=4 you CAN install an OTA update with twrp...it will install it just fine however at the completion of the update you will no longer HAVE twrp installed because it will have been overwritten with stock recovery. (it does that at the END) This will be apparent the NEXT time you try to load recovery. Where do you imagine the update is processed? It's processed by the recovery app...it can't be done inside the rom because files would be in use. The last version I ever ran was UER0..was not even aware UEN0 was out. As I indicated, I switched to a rom based on cyanogenmod with some features I wanted...if I was going to switch NOW I'd choose blisspop and it's the one I intend to install the next time I have to do a reinstall. I don't see why you fight on 5.02 when 5.1.1 is available in various flavors and with the ARDE NON OC Kernel is rock steady. If you made full backups of your device (ie dd images of ALL partitions using the Backupall bat file or shell script running around the forum restoring to a previous radio is as simple as reflashing the partition using fastboot commands.
The radio is stored in the "modem" partition fyi.

famewolf said:
As I mentioned here: http://forum.xda-developers.com/showpost.php?p=64967202&postcount=4 you CAN install an OTA update with twrp...it will install it just fine however at the completion of the update you will no longer HAVE twrp installed because it will have been overwritten with stock recovery. (it does that at the END) This will be apparent the NEXT time you try to load recovery. Where do you imagine the update is processed? It's processed by the recovery app...it can't be done inside the rom because files would be in use. The last version I ever ran was UER0..was not even aware UEN0 was out. As I indicated, I switched to a rom based on cyanogenmod with some features I wanted...if I was going to switch NOW I'd choose blisspop and it's the one I intend to install the next time I have to do a reinstall. I don't see why you fight on 5.02 when 5.1.1 is available in various flavors and with the ARDE NON OC Kernel is rock steady. If you made full backups of your device (ie dd images of ALL partitions using the Backupall bat file or shell script running around the forum restoring to a previous radio is as simple as reflashing the partition using fastboot commands.
The radio is stored in the "modem" partition fyi.
Click to expand...
Click to collapse
So where is the latest update to flash with twrp (good dry run for me should a decent upgrade come out that isn't UEN0)? I just went with UER0 posted on yer thread thr with all the megaupload firmwares & flash restored system & boot (after full wipe); as an aside, it took, & I still have TWRP in tact. I'm well aware of your fastboot method & orig backup of ALL partitions. Seemed like a waste of space at the time, still kinda does.
Regarding your rhetorical question, I was referencing Alcatel's w32 Q tool. It seemingly wasn't updated to be keyed in on the latest update either. No wait, it said the same 'no greater version' crap even when I restored the original 6045i US system/boot fw from twrp, lmao

tekka-maki said:
So where is the latest update to flash with twrp (good dry run for me should a decent upgrade come out that isn't UEN0)? I just went with UER0 posted on yer thread thr with all the megaupload firmwares & flash restored system & boot (after full wipe); as an aside, it took, & I still have TWRP in tact. I'm well aware of your fastboot method & orig backup of ALL partitions. Seemed like a waste of space at the time, still kinda does.
Regarding your rhetorical question, I was referencing Alcatel's w32 Q tool. It seemingly wasn't updated to be keyed in on the latest update either. No wait, it said the same 'no greater version' crap even when I restored the original 6045i US system/boot fw from twrp, lmao
Click to expand...
Click to collapse
Why are you assuming I should know where the latest and greatest update for stock should be? Updates are customized based on the rom version you are running at the time you submit a request. I've already stated I'm using a 3rd party rom and using an OS that doesn't allow me to run their software. You consider my recommendations a waste of time so I'll quit making them and continue using my perfectly working device on 5.1.1.

famewolf said:
Why are you assuming I should know where the latest and greatest update for stock should be? Updates are customized based on the rom version you are running at the time you submit a request. I've already stated I'm using a 3rd party rom and using an OS that doesn't allow me to run their software. You consider my recommendations a waste of time so I'll quit making them and continue using my perfectly working device on 5.1.1.
Click to expand...
Click to collapse
Omfg buddy, you said, '... you CAN install an OTA update with twrp' ; all I did was point out that I flashed previous updates (presumably the same way you're talking about), TWRP remained in tact afterward, & asked you to follow through with that point with, you know, the actual update in question here that defies many of your assertions. One of your recommendations is broken (Q), the other is hindsight (full backup) & last (update via TWRP) seemingly not feasible (unless someone were to submit updated /system) . Anyway it's all a moot point now since we're just measuring our junk.
I'm tickled you're running 5.1.1, as you've said repeatedly... I tried it briefly on Shamu & was happy to leave the LP quagmire all together & get to 6.0.1. Sufficed to say, there isn't anything perfect about this device or 5.1.1, which is why I'll leave as is & sell it. :good:
Thanks anyway.