yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Q&A, Help & Troubleshooting] JJEgan:
Thats what i do format SD card via |Windows .

Plus for overkill via CWM advanced format system sd card etc .

jje
[Galaxy S II Q&A, Help & Troubleshooting] rich345:
Will This un root my phone ?
[Galaxy S II Q&A, Help & Troubleshooting] Intratech:
That is kind of what I suggested the hard reset will do. It will wipe everything!
[Galaxy S II Q&A, Help & Troubleshooting] lfabresm:
did you try this?

http://xdaforums.com/showpost.php?p=6948568&postcount=6

this will really wipe everything, including internal storage
[Vibrant Q&A, Help & Troubleshooting] Deezy88:
my phone got a problem its said it scanning media for the internal sd,and in seconds,its complete,the problem its not media scanning very well, so for media ,music,videos etc,its not scanning well,i tried everything from factory data format,like the first time i installed a rom,its working then the problem comes back,CAN ONE HELP ME PLZ,I JUST GOT THE REPLACEMENT OF THIS PHONE AND I ADDED THE FFC,AND I DONT WANNA SWITCH THIS PHONE.ANYONE PLZ HELP ME
[Vibrant Q&A, Help & Troubleshooting] lapdog101:
Do a file explorer check for a .nomedia file . A friend of mine purchased a rooted phone that had the file and it hid his media from the music player and the gallery.
[Vibrant Q&A, Help & Troubleshooting] Deezy88:
i also i think its a titanium back up,i installed fresh new apps,its runing well now,but who knows
[General Questions and Answers] robertosaget:
[back story to understand question]

I wanted to make a 2d Android game. I am pretty familiar with developing applications for it from my job and I thought it could be a fun project. I have not distributed an application yet because i am still working on the project for my job. I understand the Android market is different than the Iphone and WP7 market , but I still want to develop the game because I own the phone already(Iphone dev looks really expensive, and i dont know anyone who owns a wp7) and I have knowledge of Java and other tools that the game would take.

My problem and question come in when I proposed this idea to my friend who is proficient in creating game assets and he said it would be a bad idea. He said that the game would get pirated a lot, the ads would be blocked, and that someone could easily decompile the project and distribute it as their own. He then said he would rather work on Iphone development or something with less piracy.

My main concern is not the piracy or the ad blocking but the decompiling. I read a thread on this forum and did not want to necro post it, but they message of the thread is that it is very easy to decompile a game and then distribute it. Is this true? How do you prevent this from happening where someone could claim that they created what you did? Is this just like what happened to Blender where someone tried to sell it and claim that they made it?

[question]

Is decompiling a game that easy that anyone can redistribute your project or is my friend just over reacting to a media post he could of read ona forum.

Thanks. Sorry for the long back story
[Eee Pad Transformer Android Development] JD82:
###########################################################################
# WARNING #
###########################################################################
# I am not responsible for bricked devices, loss of data, meltdown of #
# your device or thermonuclear war. #
# YOU are choosing to make these modifications, and if you point the #
# finger at me for messing up your device, I will laugh at you. #
###########################################################################

Backup

First of all I would like to make it clear I am not an nvflash expert: as you can guess from my avatar I am a linux user but I downloaded this tool for the first time just yesterday, upon the arrival of my TF.

Thanks to the work of Rayman I think I managed to do a backup of all tablet partitions.

I created a script to simplify the backup process:

#!/bin/bash

BACKUP_DIR="tf101-backup-`date +%Y%m%d%H%M%S`"
mkdir $BACKUP_DIR

./nvflash --bct transformer.bct --setbct --configfile flash.cfg --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --sync

./nvflash --resume --getpartitiontable $BACKUP_DIR/partitiontable.txt
./nvflash --resume --read 2 $BACKUP_DIR/02_BCT_raw.img
./nvflash --resume --read 3 $BACKUP_DIR/03_PT_raw.img
./nvflash --resume --read 4 $BACKUP_DIR/04_EBT_raw.img #bootloader
./nvflash --resume --read 5 $BACKUP_DIR/05_SOS_raw.img #recovery
./nvflash --resume --read 6 $BACKUP_DIR/06_LNX_raw.img #kernel
./nvflash --resume --read 7 $BACKUP_DIR/07_BAK_raw.img
./nvflash --resume --read 8 $BACKUP_DIR/08_GP1_raw.img
./nvflash --resume --read 9 $BACKUP_DIR/09_APP_raw.img #system
./nvflash --resume --read 10 $BACKUP_DIR/10_CAC_raw.img
./nvflash --resume --read 11 $BACKUP_DIR/11_MSC_raw.img
./nvflash --resume --read 12 $BACKUP_DIR/12_USP_raw.img
./nvflash --resume --read 13 $BACKUP_DIR/13_PER_raw.img
./nvflash --resume --read 14 $BACKUP_DIR/14_YTU_raw.img
#./nvflash --resume --read 15 $BACKUP_DIR/15_UDA_raw.img #media (/!\ ~14/30GB large)
./nvflash --resume --read 16 $BACKUP_DIR/16_GPT_raw.img

If you want to make also a backup of the media partition uncomment this line, but know that this operation will generate a 14/30GB img file and take a long time:

#./nvflash --resume --read 15 $BACKUP_DIR/15_UDA_raw.img #media (/!\ ~14/30GB)

Restore

At the moment I have not yet tried to restore a full backup, but I managed to push the kernel partition.

If someone else wants to try, the restore command should be this:

./nvflash --bct transformer.bct --setbct --configfile flash.cfg --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --sync
./nvflash --resume --download 5 <path-to-your-backup-dir>/05_SOS_raw.img
[...]
./nvflash --resume --download 16 <path-to-your-backup-dir>/16_GPT_raw.img
./nvflash --resume --sync
[Eee Pad Transformer Android Development] JD82:
I tried to restore the kernel partition and it worked like charm (06_LNX_raw.img) :)
[Eee Pad Transformer Android Development] rayman:
Good work! Overall it looks correct :)

Just FYI, you *don't* want to restore partition 2 and 4 at the very least. (and probably others!)

Partition 2 and 4 are encrypted. nvflash does not decrypt it when --read'ing, but at least during --create, it does encrypt it. I'm not entirely sure whether it encrypts it during --download, but if it does, the tablet will appear bricked after flashing.
[Eee Pad Transformer Android Development] Doward:
Perfect! I intend to be working on installing Gentoo tonight, and this will be an excellent first step in case I botch anything ;)
[Eee Pad Transformer Android Development] JD82:
Thanks for reporting. I updated the topic :)
[Eee Pad Transformer Android Development] dasbooter:
Hmm, was there a way back to safety if one was to brick this way. Just curious. Thanks again for the knowledge being passed along.
[Eee Pad Transformer Android Development] eljean:
I am not a developer so I have no idea what those lines are. So how do I basically do this? I am trying to restore the nv files of my Dinc because I bricked it. I have backed up the nv files.

Any help would be appreciated.
[Eee Pad Transformer Android Development] JD82:
If your tablet is bicked you better ask for help in this topic: http://xdaforums.com/showthread.php?t=1123429

Without a backup "those lines" are useless :(
[Eee Pad Transformer Android Development] gee one:
Thanks! I just unbricked my TF! I flashed all the partitions except 2, 4, and 15 and it seems to have restored everything just fine. There was an error trying to sign into email, but I think that happens when my computer or phone are checking at the same time. I opened the stock app manually and it was working after that.

A little background: I was running stock rooted 8.4.4.11 with CWM-solarnz. I tried to flash Prime 1.5, which I kinda knew would be bad since it's based on 8.4.4.5. My TF was stuck at the splash screen and wouldn't stay off. I held the power button down for 10+ seconds which seemed to do the trick. I put it into APX mode and flashed away. I restored all the partitions except 2, 4, and 15. According to the thread, 2 and 4 are encrypted, and I never bother to back up 15.

Thanks again!
[Eee Pad Transformer Android Development] HuskerWebhead:
So how does this differ, or what are the advantages to backing up this way versus a nandroid backup?
[Eee Pad Transformer Android Development] gee one:
This method will let you restore even when the recovery is boogered up and you have bootloops when you try to turn on the TF.

This will unbrick your TF when no other method can. It's kinda like the A-team.
[Eee Pad Transformer Android Development] evilmonkey1987:
Can someone post this type of backup of a completely untouched stock system? I am sure it would be much appreciated by people who muck up their TFs trying to do some ROM or rooting wazardry. Thanks!
[Eee Pad Transformer Android Development] gee one:
I had an interesting encounter tonight with nvflash. I was testing a little theory and flashed the previous 8.2.3.9 bootloader onto a working 8.4.4.11 system.

It confirmed my theory, but bricked my tablet. I was trying to just restore the bootloader using nvflash, but didn't check my script and used the --create command instead. This formatted my TF and wiped out partition 15, which is the only thing not backed up. :(

While trying to restore my latest backup, one thing that I noticed is that the partition table changed, so I had to update flash.cfg. I also updated the nvflash scripts to use the latest bootloader. With a completely wiped TF, I had to restore using the --create command and put all the filenames in flash.cfg. This might be because I wiped and formatted using the old flash.cfg file.

Eventually, I was able to restore my backup, but for some reason, userspace was gone completely. I had nothing in /data. I was able to restore with CWM.

Still not sure about why partition 12 would not flash. I didn't receive any error messages. So, as a backup to the backup, use CWM to backup!
[Eee Pad Transformer Android Development] hachamacha:
Hi - I was just trying to do this backup because I can't get cwm working on US TF 84411 (latest US version). Now I think I realize that nvflash perhaps is also not working on 84411.

It sounds , at least, like you had the correct version of flash if you were even (unfortunately) able to brick yours. I'm using linux, and the nvflash the OP used and keep getting back this:

[QUOTE]$ /Downloads/transformer/Prime16r2$ ./nvflash --resume --getpartitiontable $BACKUP_DIR/partitiontable.txt
Nvflash started
[resume mode]
connection failed NvError 0x8
$~/Downloads/transformer/Prime16r2$

[/QUOTE]

Also: Have you got CWM working now on US 84411? If so could you point me at the entry that does that?

Thanks and good luck unbricking.

Hashi

edit: I just realized I'd forgotten to get out of normal boot mode and into (vol+/power) mode. Nvflash works fine now as far as doing what the OP says.

I am still wondering about 84411 with CWM. Thanks.
[Eee Pad Transformer Android Development] gee one:
Here's the short version:

I think the flash.cfg file is different for the 84411 files. Compare flash.cfg with partitiontable.txt in the backup directory. Look at the file sizes- I recall that a few of them are larger.

Also, bootloader.bin is from the 8239 update or something like that. I used the blob.EBT that can be extracted from the ota update. This is the 84411 boatloader.

For CWM-solarnz that works with 84411, look in the pure root thread by mashi in the dev forum. I posted a recovery.img that will work in post 385 or so.

sent from my cyanogen(mod) vision
[Eee Pad Transformer Android Development] gee one:
Also, I found that you can reboot out of APX mode after flashing with this command

./nvflash -r --go

It only works after you sent the original nvflash command. You can use it from the command line after backing up all your partitions and want to reboot the TF.

sent from my cyanogen(mod) vision
[Eee Pad Transformer Android Development] hachamacha:
Thanks gee - I think you're right about flash.cfg. It's not easy to tell because of the format differences. I did the math (sectors * bytes) for the first few partitions and didn't see a size difference, but there are other things that are too odd about each format.

I'll go back and give that cwm a try that you mentioned. I have the recovery.img mentioned, but had heard so much negative stuff that I wasn't sure about it anymore.

Hashi.
[Eee Pad Transformer Android Development] gee one:
I think it's only 2 partitions 12_USP and some other ones. An easier way might be to compare the actual file size that was downloaded with flash.cfg.

sent from my cyanogen(mod) vision
[Eee Pad Transformer Android Development] hachamacha:
Point taken: I suppose the good news is that before the recovery partition, there isn't any changes I can see, but which flash.cfg were you recommending you use in post 385 in the pure root thread? I'm not too sure of what I'm doing with flash.cfg yet, but I'm making some assumption that it has to be created or fetched for that first ./nvflash command, or else you are not working in sync with the partition table on the tf. Is there an automated way to recreate it where you're running nvflash from ?

Forgive me if those are pretty dumb questions. I just hate starting from scratch, and now that I've got an nvflash backup, I no longer trust it since your post about 5 up.
[Eee Pad Transformer Android Development] gee one:
I just did the math with a calculator. I used the sector*bytes/sector from partitiontable.txt (from the backup files) to update the flash.cfg file that nvflash calls. I think it is something like nvflash .... -cfg [flash.cfg]... I changed the option here. Likewise, I would recommend changing -bl [ bootloader.bin ] to the bootloader that matches your backup, although I'm not sure this is necessary unless you use the --create command. I'm still figuring out how to use nvflash, so be careful, be cautious.

sent from my cyanogen(mod) vision
[Eee Pad Transformer Android Development] hachamacha:
I just tried the same thing and am very wary of the results::

Partition 3 is a good example:: From flash.cfg we get this: 4096

Partitiontable.txt gives us 524288, using numSectors * bytesPerSector,

Or did you not show something along those lines. As soon as I saw that, I thought it couldn't be so far different. It would also throw everything past that (assuming it's using those numbers to figure out offsets), is past that point.

Could you post the flash.cfg you came up with for 84411?

My main concern is probably how the heck does nvflash calculate (if it even uses a calculation) the offset to beginning of a partition (like SOS/recovery) for example? Maybe it just uses the id from nvflash (5 in this case) and then all is well.

My idea here is just to use nvflash to flash recovery.img for 84411 and then to use CWM if it works. Once past that, I'd use nvflash only for unbricking, and when unbricking, I'd be sure to use the correct flash.cfg/bootloader, and distribution that all match, so not a big issue then.

(oops -- I have a feeling I've completely derailed the thread with this stuff).

edit:: messiness beyond comprehension.

To make this epic a little more abstruse; Here is a command executed from the adb shell:

bash-4.1# more /proc/partitions

major minor #blocks name

179 0 15097856 mmcblk0

179 1 524288 mmcblk0p1

179 2 542208 mmcblk0p2

179 3 2048 mmcblk0p3

179 4 542208 mmcblk0p4

179 5 5120 mmcblk0p5

179 6 512 mmcblk0p6

179 7 13457920 mmcblk0p7

179 8 15558144 mmcblk1

179 9 15554048 mmcblk1p1

bash-4.1#

This kind of supports the notion I've got that flash.cfg is 'more' right than partitiontable.txt when it comes to the partition sizes. I suppose for difference partitions, the sizes could have different meanings. Partition 3 is supposed to be a "partition table" itself, so it may be another type of entity.
[Eee Pad Transformer Android Development] gee one:
I'm not sure those partition numbers match up with the ones used by nvflash.

Also, I think the flash.cfg only matters when using the --create command. If you are just restoring a partition to the same place, it should fit based on the existing partition table.

I noticed it because I accidentally wiped and formatted my TF with the original flash.cfg and some of the partitions would not flash because they were too large. This might be an issue if you try to flash back to an 8445 or 8239 backup.

As for the size, look at the configuration for partition 16. I think it just uses that to fill the rest of the space.

sent from my cyanogen(mod) vision
[Eee Pad Transformer Android Development] deeren:
i think that the 4096 partition 3PT is good. As you can see, even though i rooted with nvflash, my backup of partition 3 turned out to be 524288.

here is a partition table from a rooted tf with nvflash- running prime 1.6r2.

-rw-r--r-- 1 root root 3145728 2011-07-28 22:26 02_BCT_raw.img
-rw-r--r-- 1 root root 524288 2011-07-28 22:26 03_PT_raw.img
-rw-r--r-- 1 root root 4194304 2011-07-28 22:26 04_EBT_raw.img
-rw-r--r-- 1 root root 5242880 2011-07-28 22:26 05_SOS_raw.img
-rw-r--r-- 1 root root 8388608 2011-07-28 22:26 06_LNX_raw.img
-rw-r--r-- 1 root root 5242880 2011-07-28 22:26 07_BAK_raw.img
-rw-r--r-- 1 root root 1048576 2011-07-28 22:26 08_GP1_raw.img
-rw-r--r-- 1 root root 536870912 2011-07-28 22:27 09_APP_raw.img
-rw-r--r-- 1 root root 555220992 2011-07-28 22:28 10_CAC_raw.img
-rw-r--r-- 1 root root 2097152 2011-07-28 22:28 11_MSC_raw.img
-rw-r--r-- 1 root root 555220992 2011-07-28 22:29 12_USP_raw.img
-rw-r--r-- 1 root root 5242880 2011-07-28 22:29 13_PER_raw.img
-rw-r--r-- 1 root root 524288 2011-07-28 22:29 14_YTU_raw.img
-rw-r--r-- 1 root root 524288 2011-07-28 22:29 16_GPT_raw.img
-rw-r--r-- 1 root root 1496 2011-07-28 22:26 partitiontable.txt
deeren@deeren:~/Downloads/tf-backup-v0.1/tf101-backup-20110728222624$

PartitionId=2
Name=BCT
DeviceId=18
StartSector=0
NumSectors=1536
BytesPerSector=2048

PartitionId=3
Name=PT
DeviceId=18
StartSector=1536
NumSectors=256
BytesPerSector=2048

PartitionId=4
Name=EBT
DeviceId=18
StartSector=1792
NumSectors=2048
BytesPerSector=2048

PartitionId=5
Name=SOS
DeviceId=18
StartSector=3840
NumSectors=2560
BytesPerSector=2048

PartitionId=6
Name=LNX
DeviceId=18
StartSector=6400
NumSectors=4096
BytesPerSector=2048

PartitionId=7
Name=BAK
DeviceId=18
StartSector=10496
NumSectors=2560
BytesPerSector=2048

PartitionId=8
Name=GP1
DeviceId=18
StartSector=13056
NumSectors=512
BytesPerSector=2048

PartitionId=9
Name=APP
DeviceId=18
StartSector=13568
NumSectors=262144
BytesPerSector=2048

PartitionId=10
Name=CAC
DeviceId=18
StartSector=275712
NumSectors=271104
BytesPerSector=2048

PartitionId=11
Name=MSC
DeviceId=18
StartSector=546816
NumSectors=1024
BytesPerSector=2048

PartitionId=12
Name=USP
DeviceId=18
StartSector=547840
NumSectors=271104
BytesPerSector=2048

PartitionId=13
Name=PER
DeviceId=18
StartSector=818944
NumSectors=2560
BytesPerSector=2048

PartitionId=14
Name=YTU
DeviceId=18
StartSector=821504
NumSectors=256
BytesPerSector=2048

PartitionId=15
Name=UDA
DeviceId=18
StartSector=821760
NumSectors=6728960
BytesPerSector=2048

PartitionId=16
Name=GPT
DeviceId=18
StartSector=7550720
NumSectors=256
BytesPerSector=2048
[Eee Pad Transformer Android Development] gee one:
hhhmmm??? When you rooted did you use the pure root method (which also uses nvflash) or did you use the "nvflash unbrickable forever" method, which is the same as the one from androidroot.mobi, with the 5 step process... 4) ??? 5) profit! I think that method installed one of the Prime roms.

sent from my cyanogen(mod) vision
[Eee Pad Transformer Android Development] deeren:
the nvflash unbrickable forever method.

sent you a PM.

i think it is a normal behaviour. even on dumps( taking reference to nexus s dumps, desire dumps) found for e.g, the recovery.img is usually larger than the actual size and needs to be edited with hex editor in order to be flashed. so i think that the backups being larger doesnt neccessarily mean that the partition should fit the size.
[Eee Pad Transformer Android Development] gee one:
Thanks! I did a little testing to verify as well and I get the same results.

I did get a "file too large" error once, but I haven't been able to recreate it. It might have been from an abused nvflash command. My poor tablet :(

Most of the partitions are empty space and the ones that have data aren't too full. Also, I noticed that the 3_PT is the same 4096 bytes repeated over and over.
[Eee Pad Transformer Android Development] deeren:
ok. let me ask you a 'stupid question'. this was somewhat intriguing me. extracting the blob from a custom rom, you get files for header,PT,kernel,recovery,system,bootloader. what do the rest of the partitions contain?

during nvflash, everything is wiped out right and the partitions are recreated , right? do these partitions somewhat contain files unfound on stock roms?
[Eee Pad Transformer Android Development] gee one:
I'm not an expert, but here is my view of nvflash.

header is info used to pack the blob and is not seen in the partitions

PT is the partition table

kernel is EBT/bootloader

recovery is SOS

system is APP (everything in /system)

10_CAC I think is /cache

12_USP is userspace or everything in /data

15_UDA I think is the internal sdcard

The rest of the partitions, I have no idea. Some of them aren't that big. The others seem to be mostly empty. The blobs don't even flash them, so they are probably used by the system after flashing.
[Eee Pad Transformer Android Development] hachamacha:
I just got around (work.. ) to flashing (nvflash as per post 385 in pure root thread) recovery into partition 5. While I suppose the good news is that I didn't brick it, I also see no sign of recovery. I did the flash to 5, then a sync, and a reboot with vol - , and don't see any sign that recovery is there.

Was there any changes to this procedure since it was posted in 385? Thanks very much --

I'd just done an nvflash backup which appeared to work fine.

Afterward I fetched partition 5 from the TF and it is different (diff f1 f2) from the one before the flash.

edit:: Just for the heck of it , I reflashed partition 5 with the backup .img file. That also changed nothing, then I redid the post 385 instructions as follows:

#!/bin/sh

# uses the nvflash method to install cwm-solarnz (solarnz-R3-240511-1908) http://xdaforums.com/showthread.php?t=1093818

./nvflash --bct transformer.bct --setbct --configfile flash.cfg --bl bootloader.bin --odmdata 0x300d8011 --sbk 0x1682CCD8 0x8A1A43EA 0xA532EEB6 0xECFE1D98 --sync

# adjust to whatever path you like
./nvflash -r --download 5 ./recovery.img #(where recovery is actually the downloaded recovery in the post).

./nvflash -r --sync

Nada as far as getting to a recovery screen.
[Eee Pad Transformer Android Development] gee one:
What kernel are you using? The recovery that I posted in that thread is for 8.4.4.11. It's the same recovery ramdisk for 8.2.3.9/8.4.4.5, but with the newer kernel.

sent from my cyanogen(mod) vision
[Eee Pad Transformer Android Development] hachamacha:
It is the stock kernel for 8.4.4.11.

uname -a returns :: 2.6.36.3-00011-g3eb19ec #1 SMP Preempt
[Eee Pad Transformer Android Development] hachamacha:
Never mind ;)

Apparently my button handling on boot required more finesse that I could muster up. I'm in cwm and making a backup now.

To save my buttons I installed a free reboot-to-recovery app.

Thanks -- Hashi
[Eee Pad Transformer Android Development] gee one:
Edit: yeah, the boot time commands are tricky sometimes, especially when it's bootlooping.

sent from my cyanogen(mod) vision