Database Users

Partitioning the SD

Can someone please educate me on partitioning the sd? Based on what I've read and my discussions with others, ext swap is for cache, fat32 is for apps, and the remainder is for usb storage???
I have a 8 GB class 6 (supposed to be faster) Samsung sd partioned at ext swap - 0 and fat 32 - 500.
If I'm right about ext swap (please correct me if I'm wrong), I could make my phone faster if I allocated some sd space to it??? One forum I read said that the phone is usually faster but it could have been referring to a different phone and a slower card.
If I did decide to change my partition what affects would it have (wipe sd, reinstall custom rom, etc)?
Thanks for any feedback!

Partitioning the SD card allows you to utilize a2sd/app2sd and/or swap space on your SD card - if the ROM in question supports it.
Note that the ext and swap partitions are separate things, not one and the same thing.
swap is for swap - set it to 0 (you will never need it)
ext{2|3} is for the A2SD/APPS2SD space for storing applications (and dalvik-cache for some ROMs) - 512 MB will be more than you ever need.
the rest is the VFAT partition - the MS-DOS partition you see from your Windoze box when you mount it from the PC.
Note also that partitioning your card destroys all data on it - make a backup if you decide to partition.
Neither A2SD nor having swap space will speed your phone up. (Adding swap - for ROMs which support it - will actually slow your phone down, except certain pathological cases, unless you become an expert on the process trimmer configuration and experiment with swappiness controls. The reason this happens is because the as-configured process trimmer kicks in too late if you merely add swap and do not reconfigure the trimmer).
My recommendation? Keep your life simple and avoid both A2SD and especially use of a swap area on the SD card, until such a time as you "need it". You might find a practical need for A2SD if you are going to be trying out a whole bunch of new ROMs as they come out, or you are an app hoarder and run out of space in /data.
Probably you will never need to use a swap partition on your card.
Again, in neither case will you notice a perceptible gain in "performance" of the phone.
bftb0
PS Josh. Please stop putting usage questions in the Development forum. Please. Put them in the General forum.

Thanks for clearing that up......and i will stop posting in development.

TMOUS ROM/RAM - Partitions for CWR

This is probably a daft question but the TmoUS HD2 has 1gb ROM, so when we create partitions for CWR why dont we use the entire 1gb? It has an additional 500+mb of RAM to allow everything to run smoothly. What am I missing here? Why is 400mb the recommended size? Doesnt that just leave 600mb going to waste?
Thanks for any clarification.

It may not necessarily be daft, but it certainly is in the wrong forum.

You are completely not understanding how things works, you are messing ram with rom, you are messing cwr partitions with sd partitions..you are messing system partition with userdata partition.. summarizing: you are doing so much confusion that you will dont know also your name in some minutes
And, btw, wrong section.

btw I'm in a kind mood today:
When you flash CWR, all your availabe ROM will be used for data storage. The "400mb thing" is just for system partition, where the build will be stored
If you se a build that uses SD to store data, your availabel ROM is wasted also if you still need to use the 400mb thing (or less if the build is smaller)
Your RAM are never touched from those things.

First, not sure why this is the wrong section as it directly related to NAND/CWR, but thank for the psudo moderation.
Rafpinga: I'm not concerned with SD partitions, Don't use them as I have no need, but i gather the gist of your answer is that my 400mb ROM partition is strictly for the system (OS files) and the remainder of the 1gb will be used for data? That makes more sense.
So I basically have 1gb of ROM (700 something formatted), 400 is used for system/OS and the remaining 300 something is available for apps etc..?

Ok, I thought I had my answer but apparently not. How am I confusing NAND and SD partitions? I don't use SD partitions at all? I use NAND partitions only as far as I can tell. What did I miss? I didn't even mention SD partitions in my OP.
I have a 400mb System partition, which is on NAND, the remainder of my NAND is used for data correct? My SD card is irrelevant to this setup correct? I don't even need an SD card inserted for my setup to work...
If i'm confusing the two perhaps someone would explain how rather than just *****ing about the thread!.... If it's in the wrong place I'm sorry and I'm sure it'll get rightfully moved but that shouldnt negate trying to get an answer.

OK, you're all over the map, but lets do the quick rundown.
A partition is a chunk of named memory-space. aka c: in windows or the swap file in linux.
SD cards and internal ROM are essentially hard disks that can be written to. The ROM needs to be flashed, while the SD cards internally flash too. What you can do is partition either of them and name the partition. You can also choose the filesystem that a particular partition uses. Internal ROM for android needs to be partitioned into a proper linux filesystem with proper formatting to operate. One of the partitions is userspace, another is "system". SD partitions are extensions to the linux operating system and as such should not be considered "bad". Really, the more memory the better.
Random Access Memory (RAM), i believe some type of DDR in this phone, is a volatile memory that clears upon restart. It's only used during normal operation and never stores your Android.
Read-Only Memory (ROM) is NAND in this case. There is a large misnomer on these forums about NAND. They meant to call it Internal NAND. ROM, the 1gb, is where ALL operating system files are stored. You flash the bootstraps and system partitions once, then all your stuff is stored in a separate portion of the ROM.
NAND is the storage technology used to manufacture most consumer read-only memory(ROM). SD cards and the internal memory both use NAND type memory, the difference between the two is the bus speed between the internal NAND and the CPU.
On the TMOUS HD2, there is 1,000mb of space in the ROM. A 400mb system partition would leave 600mb for things like the swap file and the user data portion. In some cases, ie EU version, a 400mb system partition would eat the ~500mb available ROM, so developers figured out a way to partition the SD card and effectively expand the ~500mb to 1,000mb and beyond. APP2SD+ was the final solution.
The TMOUS when partitioned properly will have a huge amount of headroom for the Android to excel. Nothing really goes to waste as long as you use a TMOUS compatible ROM.
Next time, ask in the right forum and you'll get the answer you wanted without all the hassle.

Thank you. I really appreciate that explaination and again, sorry for being in the wrong forum.
Sent from my HTC HD2 using XDA App

Ok, now that the whole NAND/RAM/CWR thing is cleared and little badgering, I'll move this thread to the Q & A section. If you see a thread in the wrong section, just report it. Once you've posted the question in the wrong thread, there is nothing the OP can do to move it. So if you can answer then please do. This way when a MOD moves the thread to the correct place it has some useful information. So I'm deleting the SPAM/light Flaming and moving this along.
noellenchris
HD2 Forum MOD

APPS2SD and LINK2SD question.

Hello again, I need clarification with this subject...
I had a difficult time in rooting my android, thinking I failed. so for many times I rooted, installed xrecovery, then most importantly apps2sd. but I don't think it works, then I found all about Links2sd. I installed it, and each time after installing I always select the "link2sd" option, and I check the include davlik cache, but my phone memory is continually decreasing... is this normal or not? could there be a conflict with apps2sd and link2sd since I don't know if I have deleted apps2sd. sorry I'm an android newbie. Thanks..

Well... if you had app2sd link2sd would monit about it and asked you to uninstall it first.
If you don't know if your phone is rooted, look through apps - if you have a superuser app - you're rooted
As for link2sd working or not: connect your phone to the computer and open minitool partition wizard home. It will see your ext2 partition along with free and occupied space. If there are any apps on ext2 partition of your SD card - apps are installing there and the slight decrease of space is due to the existing shortcut files. Because you have created ext2 partition, haven't you?...

I did what you said and yes I found files on the other partition I created. but problem is, some files still go to the phone memory, for example the game app "ninjump" has 15mb installed on the phone memory while on links2sd it shows that it is linked to the sd card.
also, I tried removing the memory card, and when I turned on my x8 the programs were missing, so I suppose links2sd is working.
only problem is now is that some chunks are still installed to the phone memory. is there a way of totally redirecting everything to the sd card?

link2sd: Leave data files in Internal Memory, and you can choose the apps to SD
app2sd: Copy all data from the application to the SD, It's all automatic

nowonanx8 said:
I did what you said and yes I found files on the other partition I created. but problem is, some files still go to the phone memory, for example the game app "ninjump" has 15mb installed on the phone memory while on links2sd it shows that it is linked to the sd card.
also, I tried removing the memory card, and when I turned on my x8 the programs were missing, so I suppose links2sd is working.
only problem is now is that some chunks are still installed to the phone memory. is there a way of totally redirecting everything to the sd card?
Click to expand...
Click to collapse
Ok, here's the deal - how many times did you install ninjump in the past? If more then once, and meanwhile you moved it to or from ext2 it might have (though the probability is very slight) that you have two apps - one in internal storage and one in ext2 storage.
So, navigate into ext2 partition (it's a folder in root directory - sdext or so) and look for this app. It might be hard, as names of linked apps are somewhat messed up, but there should be icons If there is no app on ext2, try switching it back to internal mode and then onto ext2 again - perhaps without linking dalvik cache.
chequebo1 said:
link2sd: Leave data files in Internal Memory, and you can choose the apps to SD
app2sd: Copy all data from the application to the SD, It's all automatic
Click to expand...
Click to collapse
Thank you, that was sooooo relevant!

APP2SD
I having problem with the app2sd too..i dunno whether it works...This is what i had done..I had busybox, superuser, and xrecovery installed and rooted. But when come to partitioning the sd card, i partitioned it into 3 parts : FAt, ext2 and ext3...after that i installed the update.zip and custom zip of app2sd...the phone starts not recognizing the sd partition...anyone can help here??

I use titanium backup to see app2sd works or not. if a2sd decrease, so it work.
if internal still decrease, I guess some file or even some app just can't work with app2sd.
one question too, how or can I move games data from fat sdcard to ext2 partition? like gameloft data. I need my fat space for other file

Graveir said:
Ok, here's the deal - how many times did you install ninjump in the past? If more then once, and meanwhile you moved it to or from ext2 it might have (though the probability is very slight) that you have two apps - one in internal storage and one in ext2 storage.
So, navigate into ext2 partition (it's a folder in root directory - sdext or so) and look for this app. It might be hard, as names of linked apps are somewhat messed up, but there should be icons If there is no app on ext2, try switching it back to internal mode and then onto ext2 again - perhaps without linking dalvik cache.
Click to expand...
Click to collapse
I tried navigating to the ext2 partition using minitool partition wizard, and I indeed saw files that I have installed there. so do you mean that apps2sd is better than links2sd? thanks..

Well... I'm not saying anything is better, though I used both solutions in three different ways.
For stock SE ROM link2sd is better, since you only need to partition SD card into primary fat32 and primary ext2 - nothing more. Then you install an app and all works fine.
With custom ROM you cannot use link2sd, since they all have app2sd hack preinstalled (well, you can always modify files, but what for?). Problem occurs when you have this hack AND ext2 partition. The hack then moves automatically all your apps to ext2 memory along with dalvik cache if you install them in internal storage. If you install in external storage, the app goes to fat32 secure folder and dalvik cache remains in ext2. If you don't have any ext on custom ROM, dalvik cache is always in internal storage, while you can move any non-system app onto fat32 sd card.
The ext2 solution in custom ROMs may seem convinient, but for me it was not. When you use apps like phone locator, they should always dwell in internal memory, since SD card can be easily taken out, while deleting such an app from a remotely locked down phone would require flashing, otherwise the device is useless for the thief

Well actually both app2sd and link2sd are typically similliar. I've tried app2sd before and it still leave some files in internal memory. So will link2sd. But link2sd is much more easier to use because once your phone is rooted you just need to install it on your phone without going through the adb shell thing. Easy for newbie for sure. But you just have to manually link new installed applications and games. That's what differ link2sd with app2sd. Now I'm using link2sd. If you want to make sure, why don't you try those froyo phone. Try to use the app2sd stuff on those phone. They still install some applications on their internal as well although they have built in app2sd.
Sent from my E15i using XDA Premium App

[TUTORIAL] Everything you wanted to know about app2sd, ext3, ext4 partitions!!

I found this post in some other section!!
i am just giving the same information here for my fellow g3 mates!!
Full credit go to neoKushan
here the original thread!! http://forum.xda-developers.com/showthread.php?t=742351
Nows here what we are here for!!! Clear your doubts guys!!!
Ok, so here's the deal, in a very longwinded way that should hopefully explain everything and answer ALL questions.
You have an SD card in your phone and, a bit like normal PC Hard Drives, you can "partition" them (split them into two or more sections of different filesystems). Normally, your SD card is just one big FAT32 partition, which is fine for storing your pics, messages, emails, etc.
Now, other then your Phone's SD card, your phone will have its own internal flash memory (or "NAND") storage. Tradditionally with Android, you could only install applications to this NAND storage, you cannot install them onto your SD card. So if you have an empty 32GB SD card, but only 5Mb of internal phone storage, you still wont be able to install many apps, if any at all.
This was done to protect the apps from things like piracy - it's not easy to access the location where apps are installed on your phone's internal storage (normally impossible without root), so you can't for example buy an app, copy it, refund it, then install it again.
Still, this is no good for those of us who like to install lots and lots of apps, legitimately, as we run out of internal storage very quickly.
So Google came up with a way to install apps to the SD card. A folder is created called something like .android_secure and this stores (I believe) encrypted versions of applications, but there's a few catches:
1) Apps aren't automatically stored here, you have to manually "move" them
2) Not all apps are capable of being moved, in fact most apps aren't, the developer needs to update their app and allow it. Some apps aren't and wont be updated and some developers may not want to allow it for whatever reason.
3) Not all app data is moved, most of it is but some data is left on your phone so many people still run out of internal storage quickly.
4) You can force ALL apps to be moved to this area by default, but it breaks incompatible ones - such as Widgets, which are unable to load due to the SD card not being "prepared".
So that's Froyo's version. Before Froyo existed, some very clever people came up with a thing called "Apps2SD". Remember I said that your SD card normally is one big FAT32 partition? Well, Apps2SD works by having your SD card patitioned into TWO filesystems. A normal FAT32 partition for your usual stuff and a secondary "EXT" partition. EXT is just a filesystem, like FAT32 or NTFS, but it's the filesystem used by Android internally. The SD card is normally FAT32 because it's a "universal" filesystem, that just about any machine will be able to read, whereas EXT filesystems are generally Linux only, but I digress.
EXT has several different versions. The most common one you'll see is ext3. The main difference between ext2 and ext3 is "journaling", which is just a fancy way of saying that should an operation (such as copying, writing or reading) be interrupted unexpectedly (say, by you turning your phone off), then no data should be lost or corrupted. You know how when you turn your phone on, it says "preparing SD card"? It takes a few minutes, but what it's actually doing is checking that the FAT32 partition hasn't been damaged, because FAT does NOT have journaling. If you used a computer back in the Windows 98 days, you may remember that lovely blue "Scandisk" screen that had to run every time you didn't shut your computer down correctly - that's the same thing. But then Windows 2000/XP came along with NTFS, which also has journaling, meaning you had less chance of loosing data. But I digress once more.
So you have your SD card partitioned into EXT and FAT32. Generally it doesn't matter if it's ext3 or ext4, but you don't get any real advantage with ext4 over ext3 in this instance. Apps2SD then runs a special script on your phone which "symbolically links" the folder from your phone's internal storage where your apps are normally stored, to the ext partition on your SD card. A symbolic link is a bit like a shortcut for folders, except it's transparent to the OS: In other words, Android doesn't know that when it's installing it's apps to the internal phone storage, it's actually being stored on the SD card. This effectively boosts your internal phone memory from the previous 5mb that you had in my example above, up to whatever size you made the ext partition on your SD card (often 512Mb or 1Gb, but it depends on how many apps you install).
Plus, because it's "journaled", it doesn't need to be "prepared", meaning it's ready to go as soon as the phone starts - so your widgets and apps work immediately (unlike "forced" Froyo Apps2SD, where widgets disappear).
The catch with Apps2SD is that whatever space the ext partition takes up is taken away from the SD card. So if you have a 4Gb card (with something like 3.5Gb of actual storage) and you make a 512Mb ext partition, your SD card will "shrink" to 3Gb. The space isn't actually lost, it's just being used by the ext partition. If you reformat your card, you'll get it back.
Finally, there's a difference between "Apps2SD" and "Apps2SD+". Remember I said that your apps are stored on a special folder inside your Phone's NAND storage? Well, that was a bit of a lie. It's actually stored in TWO places. There's a second area which is called the Davlik Cache. You don't really need to worry about what this is for (Hint: IT's to do with the Java runetime your phone uses to run apps), all you need to know is that apps use it to store data, which also eats up internal phone memory. Apps2SD+ moves davlik cache to the ext partition on your SD card as well, freeing up even more space. Some people believe that this may come at the cost of performance, as the internal NAND memory should be faster than your SD card (Which is why you also get people arguing over which "class" SD card is better for Apps2SD - the logic being that a faster SD card means less impact from this move), but the truth of the matter is that your applications will be running from your Phone's RAM anyway, so performance isn't really impacted at all. Since most apps are only a few hundred Kb's in size, or a couple of MB at the most, it's a non-issue.
Finally, any recent version of Apps2SD/Apps2SD+ should work with an SD card that is or isn't formatted with an ext partition. It'll check for this partition when your phone first boots and if it's not there, just use internal phone storage.
Having an ext partition WITHOUT Apps2SD+ shouldn't cause any issues, either, so you can format your SD card whenever you're ready.
So in summary:
Apps2SD "fakes" your phone's internal memory and puts it all on a hidden section of your SD card.
Apps2SD+ pushes even more content to the SD card, freeing up even more space on the phone itself.
"Froyo" Apps2SD has various limitations that "old" apps2SD does not, but is much easier to handle as it doesn't involve any kind of "partitioning".

I don't really claim to be an expert but I wrote this and nobody really chimed in to say anything was wrong, so hopefully it applies here.
I'll try to keep an eye on this thread in case anyone has questions.

I don't really claim to be an expert but I wrote this and nobody really chimed in to say anything was wrong, so hopefully it applies here.
I'll try to keep an eye on this thread in case anyone has questions.
Click to expand...
Click to collapse
Thanks a lot buddy.. People may know all that but you have written in such a simple manner that even a small kid will understand..
Acid lestitious 2.0. Fugumod 2.2 build 1.9

thanx soo muxh for this info...it's getting really confusing out there with everyone claiming this type is better than that blah blah blah etcetc....this is very helpful
thanks again

JohnstonF said:
thanx soo muxh for this info...it's getting really confusing out there with everyone claiming this type is better than that blah blah blah etcetc....this is very helpful
thanks again
Click to expand...
Click to collapse
You're welcome
Acid lestitious 2.0. Fugumod 2.2

[Q] Not enough internal storage

Like everyone here, I have the famous HTC Leo. A friend installed Android on NAND, the 2.3.4 with the mod-HyperDroid CM7-v2.1.0.
This is a great device, but the more I use it, the more I have less internal memory.
At first, I installed a lot of applications, I was full of things and I ended up filling the internal memory. I moved the more applications possible on the SD card, but the internal memory ended up being full. So I uninstalled applications not too useful, and applications more useful, clean caches, remove data, but it is still too small. My system tells me that I only have 217.3 Mb total internal memory and while I hardly more than application system installed, I only have 21.3 MB available. Now, I know that this model has double.
I do not understand: what is this devilry? Where is my memory? How can I resume normal operation until all the memory is gone and my phone becomes unusable?
I can't be the only one to whom it happens, right?

only the data partition counts as internal memory, the rest is taken by the system, boot and recovery partitions, so your200+ sounds about right.
read up on creating an ext partition on your sd card, and either flash a rom that supports it already, or add a script to your current rom, , then, instead of using the data partition on the nand the system will use the sd-ext partition as if it were nand. (This is NOT the same as choosing 'move to sd' in the apps config screens, that moves it to the fat partition, and some apps wont work from there, , , all apps will work from the ext partition, and faster than the fat partition.)
There are two sets of scripts, some move the whole data partition to ext, meaning of course you are not using the 200+ mb on the nand, so for me i prefer the scripts that move only the apps to the ext partition, and keeps your actual data (txts, contacts, stuff like that) on the regular nand data partition, thus spreading the useage.
look out for keywords like 'app2sd+' 'data2ext' 'dataonext', , stuff like that when you're searching.

samsamuel said:
only the data partition counts as internal memory, the rest is taken by the system, boot and recovery partitions, so your200+ sounds about right.
read up on creating an ext partition on your sd card, and either flash a rom that supports it already, or add a script to your current rom, , then, instead of using the data partition on the nand the system will use the sd-ext partition as if it were nand. (This is NOT the same as choosing 'move to sd' in the apps config screens, that moves it to the fat partition, and some apps wont work from there, , , all apps will work from the ext partition, and faster than the fat partition.)
There are two sets of scripts, some move the whole data partition to ext, meaning of course you are not using the 200+ mb on the nand, so for me i prefer the scripts that move only the apps to the ext partition, and keeps your actual data (txts, contacts, stuff like that) on the regular nand data partition, thus spreading the useage.
look out for keywords like 'app2sd+' 'data2ext' 'dataonext', , stuff like that when you're searching.
Click to expand...
Click to collapse
Excellent advice, but I think you forgot to mention this
Late I think me brain is playing tricks on me...:cyclops:

shanman-2 said:
Excellent advice, but I think you forgot to mention this
Click to expand...
Click to collapse
so, pretty much exactly what i described, then....

shanman-2 said:
Excellent advice, but I think you forgot to mention this
Late I think me brain is playing tricks on me...:cyclops:
Click to expand...
Click to collapse
So, I don't really need to use this. I just can install a new ROM on my NAND after making extending place on my SD for the 'dataonext', can't I?
I have to choose a dataonext ROM (with french version) and make new partition on my CD card. I'm saving all the SD card data's just now (with luckyBackup, because I'm on ubuntu PC).
My problem is find a good ROM for my needs. So, I have HSPL 2.0.8 and MAGLDR. How can I find the rom radio number? I need this information to choose the good ROM. Any advices about good ROM for my needs?

r no need to change the radio,,, if magldr works then the radio is fine.

samsamuel said:
r no need to change the radio,,, if magldr works then the radio is fine.
Click to expand...
Click to collapse
I bought a new 16 GB SD card to try the method of post 1843062. I am trying to format as it should, and tonight or tomorrow, I'm trying to see if I can install the script without too much risk, I am not a very experienced user of ROM for HD2 and, in addition, as I'm 100% Linux Ubuntu, I saw that many procedures are more complicated or impossible to run from a Linux desktop.
Thank you for all your help and I'll let you know.

I need to understand.
I have a EU HD2 with HyperDroid CM7 installed on it.
Like many people here, my memory became too small over time. So I look for a solution and I was guided to this thread. While speaking, I read everything I could understand (and frankly there really is too much to read and understand, here ) and I ended up deciding to adopt the solution Kokotas.
So I bought a new SD card (16GB class 10 Duracell - I know, Duracell is a brand of batteries ...) and I formatted properly Gparted as shown, with one primary partition of 12 GB fat32 I named /données (French for datas) and a second primary partition 4 GB Ext4 I named /data.
Then I primed to install the script Kokotas (but I have not yet done so, this is the trick!) And there: surprise!
I suddenly 4 times more free memory internally (from 20 MB to 80 MB), but it is still the same overall size!
I wonder how it is done, because it's been months that I want to release the NAND memory, I deleted almost all my applications downloaded without great effect and there, before installing the solution Kokotas, hop, I have the place!
I run Nautilus on my HD2 connected via USB and what do I see? in the partition /data in ext4, records were Cres /app /app-private and /dalvik-cache.
What does that mean? My ROM can do one DATAtoEXT 2011 alone, when she sees a partition SD / data?
Do I install the script Kokotas or it is not worth it?
Do I flash a new ROM (I thought MIUI-MIX_3.3.1, but I'm not sure it's a good idea) without risk, in short I need to understand what happens with my phone.
Thank you.
(Sorry for my english : this is the fault of Google translation )

You might also consider just running an SD build instead of NAND. You can get a 2GB "internal storage" system.img and you don't risk getting bad blocks on nand by constantly flashing things. In my use of both I didn't really see any great speed increase or advantage in using NAND other than boot-up time is a bit less, but does that really matter?
Just another thought on this.

orangekid said:
You might also consider just running an SD build instead of NAND. You can get a 2GB "internal storage" system.img and you don't risk getting bad blocks on nand by constantly flashing things. In my use of both I didn't really see any great speed increase or advantage in using NAND other than boot-up time is a bit less, but does that really matter?
Just another thought on this.
Click to expand...
Click to collapse
I thought NAND is better for battery's management...

Monolecte said:
I thought NAND is better for battery's management...
Click to expand...
Click to collapse
I didn't see any great battery improvement with NAND.

ROM flashing don't work
I tried to flash MIUI-MIX_3.3.1, but, it wasn't working. I think this is because Resurection needs this specific table of partition and I don't how can I modify this table of partition. CMW had a partition tool? How can I do?

Monolecte said:
I tried to flash MIUI-MIX_3.3.1, but, it wasn't working. I think this is because Resurection needs this specific table of partition and I don't how can I modify this table of partition. CMW had a partition tool? How can I do?
Click to expand...
Click to collapse
use the nand toolkit

samsamuel said:
use the nand toolkit
Click to expand...
Click to collapse
With an Ubuntu PC?

After miles of thread reading here, I won against the machine!
I have something like a new phone.
Thank you everybody.
If I can do it, anybody can do it!

ubuntu or windows will be fine.

The NAND Toolkit is a Windows software... so...