yashsingh1/xdaforums huggingface dataset:
[G Tablet Q&A, Help & Troubleshooting] MartyB95:
tekrhino,

I pretty much did the same thing but for a BL1.1 ROM. I have been able to NVFlash repeatedly from roebets 3588 package and put myself back to a stock 3588 TNT.

I also did the following:

1) Ran "backup_gtablet_rev2" to make an NVFlash Backup.

2) I renamed Part-11.img to system.img

3) I renamed the remaining parts by removing the -(dash) from the rest of the parts (Part2.img through Part10.img)

4) I renamed backup.bct to gtablet.bct

5) I tried both of the following:

a. Renaming the partitions.txt to gtablet.cfg. That gave me syntax errors

b. Editing the orginal gtablet.cfg and updating the APP size to match my system.img

6) I copied the nvflash_gtablet.bat from roebet's package to my nvflash dir.

7) I executed the nvflash_gtablet.bat.

Everything ran successfully and I thought I had it but as I mentioned before I hung up in the boot process. I tried clearing the cache, and the Dalvik cache, but nothing helped. In the end I had to load the ROM again using CWM.

I am hoping someone with more NVFlash experience could comment or point me in the right direction. I really feel that I am close to the answer but just need a kick in the right direction.
[G Tablet Q&A, Help & Troubleshooting] tekrhino:
@MartyB95

It seems we both had the very same results..

my next attempt, (When I get my device back to the way I want it) is to use the original gtablet.bct file in the original BL1.2 nvflash kit instead of renaming the backup.bct from the backup files to gtablet.bct. leaving all other steps the same...

OR (and this might be more difficult for me)

1) Editing the renamed Partition.txt (To gtablet.cfg) to include the same [tags] as the original .cfg file because it seems the renamed txt file is missing a lot of information that NVFlash is looking for but can't find.. Hence the Syntax Error shorty after the first line of execution..

2) And still using the original gtablet.bct file from the nvflash kit.

3) Leaving all other steps the same afterwards.
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
No you did not.

It looks like there are 2 different nvflash programs each of which produces a different partition table output. Still, this is only a minor irritation. Since the nvflash program can both read and write (and create) partitions, just use bekit/roebeet's nvflash to also do the backup. Copy over only p00r's backup batch file and edit it so that it produces the *.img files and the gtablet.cfg that is wanted by bekit's. ie. *.img files w/o the '-'; system.img instead of part11.img, and gtablet.cfg instead of partition.txt.

They would be different. Those 2 partitions are not raw partitions dumps. They contain YAFFS2 filesystem images and the file sizes will change depending on how full your /system (APP) and /cache (CAC) filesystems are. The sizes of some of the other partitions might also differ depending on whether the partition is a raw dump using nvflash (in which case you'll get everything) or an image file containing just the needed files for that partition. Part9.img (the recovery partition) is an example. It is allocated 16MB of space on the NAND flash, but, bekit's recovery.img is only 3.5MB. BTW, you can skip part12 (CAC) in your backups.

You could, I suppose, but, really, there is no need to do things like that. Just decide on a nvflash program (either bekit's or p00r's) and use it for both backup and restore with the correctly modified batch files. You guys are making this much too complicated. And, really, there is no need to use nvflash. As long as you don't switch bootloaders, CWM does backups and restores pretty well.
[G Tablet Q&A, Help & Troubleshooting] tekrhino:
My reasoning for wanting to make a 3.3 nvflash is so in the event of a soft brick I wont have to start from scratch on a tap n tap rom and work my way back to 3.3. Also, my goal is to make a clean install nvflash that everyone can use to restore from.

Marty and I are only looking for a way to eliminate a few steps from that process.
[G Tablet Q&A, Help & Troubleshooting] tekrhino:
Success? maybe

1. I wiped everything from the Gtab (Cache, Data, Boot, System) so I can do a clean install of 3.3 note: Wiping everything may not have been necessary but I wanted to start with a clean slate.

2. I ran the stock tapntap (BL1.2) nvflash… successfully

3. Via recovery, I flashed a clean install of GtabComb 3.3/BL1.2… successfully

4. Via recovery, I backed up GtabComb 3.3

5. Via recovery, I used (Mounts & Storage/Mount USB Storage) to copy the newly created backup folder to my PC. (for later use)

6.Using the nvflash backup kit found here, I used backup_gtablet_rev2.zip to make a backup of my clean install of 3.3 Big Thanks to P00r for putting this together.

7. I copied over the system.img file from my CWM backup folder to the nvflash backup folder; this system file is going to replace the “Part11.img” file!

8. I snagged the file “gtab.nvflash.1.2.branch.20110508 with cwmv3028.zip” http://viewsonic-gtablet-for-dummies.webs.com/nvflash.htm (Big thanks to GoodIntentions for this Site) and unzipped the contents.

9. From the unzipped folder I deleted the img files Parts 2 through 10 and deleted the system.img file also.

10. I copied over the img files parts 2 through 10 from the nvflash backup I made over to the unzipped gtab.nvflash.1.2.branch.20110508 with cwmv3028 folder.

11. I copied over the system.img file from the CWM backup folder over to the gtab.nvflash.1.2.branch.20110508 with cwmv3028 folder.

12. From the gtab.nvflash.1.2.branch.20110508 with cwmv3028 folder I edited the gtablet.cfg file to reflect the correct file size of the newly inserted system.img file on the appropriate line.

 [partition]

 name=APP

 id=11

 type=data

 allocation_policy=sequential

 filesystem_type=yaffs2

 size=195258624 (Note: size may differ for different ROMS and versions)

 file_system_attribute=0

 partition_attribute=0

 allocation_attribute=0x10

 percent_reserved=0

 filename=system.img

13. From the 3.3 nvflash backup I made I copied the backup.bct file over to the gtab.nvflash.1.2.branch.20110508 with cwmv3028 folder and renamed the file to gtablet.bct.

14. At this point I was ready to test it out, so I re-wiped everything from my Gtab (just so I can have a clean slate with “Magic Value Mismatch” showing on boot attempts.

15. Via APX mode I successfully nvflashed the newly created nvflash kit.

16. Boot up was successful with GtabComb 3.3 presenting me with the first Set up screen.

17.	YAY!

:cool:

Download zip file here: gtabnvflash12BLGtabComb33BR.zip

I'm hoping someone would be willing to test it out on thier device.

The zip file has both a Backup and a Restore Batch file in it.

I left the backup batch file on there in the event anyone wanted to try this on thier own.
[G Tablet Q&A, Help & Troubleshooting] MartyB95:
Ok i followed your work and am going to try on my 1.1 setp.

If i followed you correcty everything is basically the same except for the following:

1. Used the system.img from the cwm backup instead of the nvflash backup

2. Used the backup.bct from the nvflash backup instead of the gtablet.bct in nvflash

If this is so i wonder why the part11.img created by the nvflash backup is different from that of the cwm backup?
[G Tablet Q&A, Help & Troubleshooting] tekrhino:
Don't know the answer to that, I got the suggestion from the other thread to use the CWM system.img file from one of P00r's posts and it worked. The system.img file from the CWM backup was considerably smaller than the nvflash backup file part 11.

I should also note that during my next several attempts to nvflash backup I got stuck on part 7 so I had to edit the backup batch file removing the part 7 command. Luckily for me I had the first part 7 file from my original attempt and inserted that one in its place. I'm not sure but I think part 7 is the boot animation because the resulting effect after the nvflash restore was the third bootup screen was the psychedelic honeycomb animation I had on my rom before I started messing with trying to make a clean install nvflash kit.
[G Tablet Q&A, Help & Troubleshooting] residentorca:
Thanks for documenting and sharing your work. I installed gTabComb 3.2 (after testing CM7) on GF's tablet which has 1.1 bootloader. Would this nvflash procedure work with 1.1? I've read enough about the gTab to know that bootloader version can be critical and I'm guessing it is in this case as you have 1.2.
[G Tablet Q&A, Help & Troubleshooting] tekrhino:
I believe it will work with 1.1 also, MartyB95 is working on a 1.1 version since that is what he is using on his device.

Also, I have hunch that with this method of nvflashing it will be possible to simply nvflash any rom with any bootloader via AXP mode regardless of what bootloader you currently have installed since the nvflash process is essentially a low level complete wipe of whatever rom is on there now and flashing the new rom in its place.

But this is a question for a recognized developer like Roebeet to best answer.
[G Tablet Q&A, Help & Troubleshooting] roebeet:
If you are using one of my 4349 nvflash's as a baseline, the app partition CFG is already expanded a bit.

The "quick" way is to just replace the boot and app partitions (and optionally the recovery one) with an image from your HC ROM, usually using cwm to create the .img files. But that might not be 100% effective.

The "better" way is backup all the partitions via nvflash. From memory, you'd want to do something like this:

./nvflash --bct gtablet.bct --setbct --bl bootloader.bin --configfile gtablet.cfg --create --sync
./nvflash --resume --getpartitiontable partitiontable.txt
./nvflash --resume --read 2 part2.img
./nvflash --resume --read 3 part3.img

etc. up to part 10. Then use your cwm'd backup system.img for part11. Basically you're taking bekit's original structure and just replacing the various .img files with your own backups img's. Dev branch doesn't matter - you'd just use the correct bootloader.bin for the dev branch you're backing up.
[G Tablet Q&A, Help & Troubleshooting] tekrhino:
So basically your answer is yes?

We can jump to different roms regardless of bootloaders as long as the baseline bootloader.bin file in the nvflash kit is the correct one for the rom you want to switch to?

Then using either the quick or better methods to insert the remaining img files corresponding to whatever rom you to nvflash, is this correct?

Thank you for your input on this thread, it is very appreciated brother!

:cool:

Edit: in the words of Columbo, "Just one more question sir"

Is it possible you can browse over to this thread and help out with a part7.img issue we are having with using nvflash to make backups... folks there, including myself are getting stuck on part 7.

http://xdaforums.com/showthread.php?t=1010659
[G Tablet Q&A, Help & Troubleshooting] aabbondanza:
Working Fine
[G Tablet Q&A, Help & Troubleshooting] tekrhino:
Sweeeet!

Awesome! I'm very happy this worked even with the FC issues on the initial setup. And yeah, the layout of HC is a huge difference coming from Froyo and GB. it took me some time to get used to but I love desktop layout with the sliding widgets.

I will shorten the batch names.. I will cut it down to Backup.Bat and Restore.Bat and I will shove the APX drivers for windows into the nvflash kit.

Thanks for trying this out, I was very curious if this work for someone else.

:cool:
[G Tablet Q&A, Help & Troubleshooting] residentorca:
The amazing Robeet seems to confirm the answer is "yes". What a simple and elegant way to switch between bootloader versions and backup/restore. My GF's gTab is far away right now so cannot try on 1.1 but will be keeping this as a reference for when I can. Thanks again for sharing this information!
[G Tablet Q&A, Help & Troubleshooting] MartyB95:
I can confirm that I was able to get the flash of GTabComb (BL1.1) working by replacing the system.img with the one from CWM backup instead of using the one from the NVFlash backup.

I also had the same problem with part7.img. I was able to use the file that was created from the NVFlash backup and replace the part7.img that was giving me the problem. I reflashed the entire thing using NVFlash again and then commented out the restore of part7.img. This got everthing working again as it was supposed to.

If one of the senior members who has worked with NVFlash images cares to comment on the following 2 points I would be extremely thankfull. It would also help educate some of us "newbies" who are plugging away at things.

My questions are as follows:

1. I don't understand why the NVFlash backup of system.img (image 11) does not work and we must resort to the file created by CWM. Why???

2. Why is NVFlash hanging when trying to send the part7.img (image 7) when we build the new gtablet.cfg. Seems to only be able to download 8K out of the 16k that is supposed to be sent? Any ideas??

Thanks for all the feedback on this topic it has been great!!!!
[G Tablet Q&A, Help & Troubleshooting] tekrhino:
Good Job Marty, I suggest holding onto that Part7.img file in a safe place until a solution is found or an answer is found as to why it's happening..

Right now I can only guess that part7 is the 3rd "Animated" Bootscreen image.

From the Other Thread, P00r seems to believe the problem with Part7 is a bad block.

Is your nvflash kit from a clean install of the ROM or is it from a backup with your personal stuff on it?

Reason Being, I want to try and nvflash a 1.1 hc version directly to see if we can switch bootloaders (And ROMS) without having to start with a TapNTap rom and work our back to HC..
[G Tablet Q&A, Help & Troubleshooting] MartyB95:
tekrhino,

It is specific to my GTabComb with all my apps, but I can create one that is based on the generic install of GTabComb for BL1.1. I will try to create one over the weekend and post it here when I am done.
[G Tablet Q&A, Help & Troubleshooting] roebeet:
Yes for the first question. Back when 1.1 / 1.2 was more problematic for me as far as soft-bricking (while testing), I made the 3588 and 3991 (and later 4349) nvflash images because that made the bootloader irrelevant. I could flip between them easily, after that point.

The "better" way was the way I made those images, as I believe I had issues between 1.1 and 1.2 with the "safe" way (1.2 changes one for the other partitions, so it's necessary to do that). Once I figured that out, I had effectively retired the old bekit November image that I had been using for months (and of course many thanks to bekit to making that first image!!).

I'll take a look at that other thread. And btw, "I was in disguise. Lots of dames go in those joints. I never kissed nobody..."
[G Tablet Q&A, Help & Troubleshooting] tekrhino:
Dude, You Rock!

Thank you very much for putting together the NVFlash Kits that we use for experimenting with now.. And thank you for all your input on here. It does not go unappreciated.
[G Tablet Q&A, Help & Troubleshooting] MartyB95:
It looks like I had some time today and put together the GTabComb BL1.1 NVFlash package. Once the flash completes and you reboot...be patient!! It took about 4 minutes on mine to rebuild and install. Much quicker after that.

This NVFLash package installs the following:

1. GTabComb Beta3.3 for BL1.1

2. Clockworkmod as the recovery tool

The "restore.bat" will flash the images to the gTablet. The "backup.bat" will create new images called part2.img to part10.img and system.img in the Backup directory so you don't have to worry about overwritting the current images. It currently excludes the backup of part7.img.

To download the package follow the link below

http://www.mediafire.com/?roy39v1pnp2bdby

Have fun!!
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
I would change those batch files:

1. The .bct file is not stored in the Backup\ directory.

2. The partition layout file partition.txt is created in Backup\, but it is not used. Why create it if it is not used by restore.bat?
[G Tablet Q&A, Help & Troubleshooting] aabbondanza:
Backup.bat

Made similar changes to tekrhino's backup.bat yesterday as well. I had the .bct save to backup dir & also added a "md .\backup" command at the begining of the batch file because nvflash was failing if the \backup directory didn't already exist. Didn't notice the partitiion.txt file not being needed. Good catch. Thanks.

Al
[G Tablet Q&A, Help & Troubleshooting] tekrhino:
I haven't started my edits yet.. no time the past couple of days..

Thanks to you both for the revisions. I'll merge them with my next attemps.
[G Tablet Q&A, Help & Troubleshooting] rajeevvp:
Those are minor points. The main thing is that the partition.txt that is created by backup.bat is not used by restore.bat. This is a pretty bad mismatch and is sure to cause problems later on.

Plus, there is the fact that a single directory named \Backup is used each time. This single, fixed, directory and the partition.txt mismatch makes the batch files far less general-purpose than they could be. Consider using, instead, the approach taken by ClockworkMod:

Both backup.bat and restore.bat take a single argument, which is the name of a directory where gtablet.bct, partition.txt and the *.img files will be stored, and from where backups will be restored. Eg:

[B]C:\> backup.bat gtabcomb-3.3-bl1.1[/B]
C:\> [B]backup.bat cyanogenmod-7.1RC1-bl1.2[/B]
C:\> [B]restore.bat flashback-7.0a1-bl1.2-20110815[/B]

BTW, I've just found out that the version of the bootloader.bin you use with nvflash is not critical--you can use either the 1.1 or 1.2 bootloaders with the "--bl" command line--as long as it is for the gTablet. The bootloader.bin file passed on the command line to nvflash is not stored on any of the normally visible partitions (2 - 12). It's a) either loaded into memory and then executed directly, or b) it is stored on the mysterious (and invisible) partition 1 and run from there. In any case, this behaviour makes sense. nvflash, being a low-level repair utility, should be able to bootstrap the gTab almost from scratch if needed--eg. if every partition on the gTab's NAND flash gets corrupted or is wiped.
[Galaxy Tab 10.1 General] ganiman:
I got the TW update this morning, and with it came a new calendar app. I don't like it. I think the stock HC 3.1 calendar app was much nicer. Any way to get it back?

I saw a lot of people getting hyped for this update, but honestly I'm not sure I like it much at all. The replacement for the taskbar popup, where you can see your wifi network, settings button, etc, isn't all that great. It's too big, and I can't click on the wifi network name anymore which would jump me right to the wifi part of settings. Annoying.

I'd be happy with getting the old calendar app back, and short of that would be interested in rolling back to the previous version if possible.
[Galaxy Tab 10.1 General] jchorton4:
I totally agree. I hate the new calendar app and desperately want to switch back to the old version. I haven't figured out how to do it yet.

Also, the color change of the bottom menu bar from black to gray is really bothering me for some reason.
[Galaxy Tab 10.1 General] IRIE4IPIER:
That's what you guys get I saw all this bull**** from reviews on youtube and I decided not to update
[Galaxy Tab 10.1 General] rjj1976:
I like the new calendar app just fine. To each his own I guess.
[Galaxy Tab 10.1 General] TheDave1022:
I agree. The skinned apps stink overall. The samsung apps social hub and photo editor are pretty good. I might just flash back.
[Galaxy Tab 10.1 General] bluskye:
The stock google calendar is hw accelerated. You can tell Samsung did not use hw acceleration for their calendar. Its not as smooth when you scroll around. Disappointing.
[Galaxy Tab 10.1 General] neonlite:
been searching whole xda and found 2 links to the stock honeycomb.apk from the NOOK section. but these are for honeycomb 3.0, didnt try it yet.

any dev who has the stock calendar.apk for honeycomb 3.1?

seems more users are having problems with getting the stock calender back while having touchwiz UX.
[Galaxy Tab 10.1 General] xxtreem11:
:confused:

Bumpity bump bump bump bumpy bump....

Isn't there a way to download this apk from Google directly? Dump from a Xoom rom?

I've even *****ed at @SamsungSupport for the poor Calendar implementation. The TW "improvement" is about as worthless as keeping your calendar on a napkin.
[Galaxy S II General] OHDUSER:
so.. my screen glass has been broked.

I bought the phone through the UK (im from Israel) and not through a carrier.

so im screwed.. you think a private store could fix my glass? i mean things are pretty bad.. the screen is STILL showing everything..

but the glass is broken badly.. even the capcitive button is broken and there is a crack that shows the led light of the front buttons...

do you think its fixable? I'm aware it will cost alot and I dont care that it wil..

the question is, is it fixable?

and if its.. wont they put a regular glass instead of gorilla glass? i will loss glass toughness huh..?:(:(
[Galaxy S II General] angelomaldito:
Does the screen still responsive to touch in spite of the damage? If yes, probably you just need to fix a new glass. On eBay for an iphone it costs around £15-30 to fix it (service included). If it's not responsive to touch then you have to change another piece (digitizer) which is more expensive, around £75-150 for SGS2 (without the service).

Check on eBay for "i9100 screen lcd digitizer" or hit the link

http://shop.ebay.co.uk/i.html?_trkp...d+digitizer&_trksid=p3286.c0.m14&_sop=2&_sc=1

Of course, as you'll have to pay the service in Israel, you should know the average price for this in your region better than me.

It can definitely be repaired, so don't worry too much. ;)

Good luck!

PS.: Don not worry too much about the gorilla glass either, as your gorilla glass wasn't so tough, was it? Anyway, it is possible that the replacement is a gorilla as well, who knows...
[Galaxy S II General] psp888:
It's really easy to replace the screen yourself. You have to change the whole glass and screen as they are bonded together.

I've got a used screen for sale, look at my sig below
[Galaxy S II General] atype007:
Isnt gorrila glass supposed to be so tough ? i myself had a screen scratched frm one time putting the phone in my pocket with a key along with it !!
[Galaxy S II General] bruflot:
Tough, as in harder to crack/break. Not scratch proof ^^
[Galaxy S II General] EarlZ:
I could be wrong but isnt the glass on the SAMOLED consturction a part of a whole thing? I mean you can have the glass just replaced you need to get the entire screen, I see a lot of people posting spare screens on the other thread, quality is of question though if its a real SAMOLED Plus or just a Class A replacement.
[Galaxy S II General] OHDUSER:
yea the touch is working just fine.. :)

just worried about the fact that there are cracks where i can see the light of the buttons coming out....

I hope it can be fixed... hopefully with gorilla glass...
[Galaxy S II General] OHDUSER:
any 1 got anymore tips?
[Galaxy S II General] rwj5279955:
Please let us know what route you take and the outcome. You know, just in case.
[Galaxy S II General] BarryH_GEG:
I can't read Hebrew but I'm guessing since they sell phones in Israel they probably have an authorized repair center there. Take it to them and at least your warranty will remain intact.

http://www.samsung.com/il/consumer/...nes/smartphones/index.idx?pagetype=subtype_p2
[Galaxy S II General] atype007:
That's actually not a link to s2. In israel s2 promotion started but no actuall contracts or selling availaibe but it will be very soon and its more expensive there that many other countries so will be the repair in it.
[Galaxy S II General] BarryH_GEG:
I only posted that so OP could find a service center. They should be able to repair a SGS2 even if it's not sold there.
[Galaxy S II General] OHDUSER:
its sold here.. by all 3 carriers..

expesnive..

yet they wont fix my sgs2..

i need a private stoe.. just hoping it will put new gorilla glass into it..

any other tips?