Grsync workin on my ubuntu 13.10 saucy linux,backup failed with errors? please help

[PHYSC]

With what tool at what point? Forget the wendal- and RK3xxx Firmware Tools!


What readme?


Last try:

I find it difficult to understand i have learning problems as you are aware of,so i'm not going to take in something until i do it it's hard for many people to understand me at times,but once i get shown i can do it repeatedly normaly any way,but if i can't understand all the instructions i can't do it.
i do follow you want me to do a save of a file from a start point of 0 to a count of 2 but that's not recognized by androidtool 2.1 with the start and count stated,android tool 2.1 doesn't know what i am asking it.thought it only understandss counts beginnin 0x something?

The very best option would be someone makes a tool that simple for either backup and restore,or if they make a .img splitter guide in laymans terms would be good.
Believe me you i won't give up until i find something that works,and i will be looking elsewhere to to get responses which infact i have already done,at github.

I am not walking away from it i refuse no matter how long it takes me,if i have to ask a 1000 people i will do that,sick of reflashing the thing i want a 1 step method to recover everything,especially the firmware files.

I can't help it but i need a point and click option really,i can't take it in usually unless i am told/shown hands on with it,you've got me to dump it which nobody could do before,but now i can't read that dump and split it up although i wanted to.

Right the numbers you gave i couldn't use so i guessed it at this 0 at satrt and 0x800 for count it gives a 1mb file, mneaning that i am under the impression you were requiring this simply a nand file sized 1mb, from my k-r42 via nand dump, i hope that's what you asked any way :3

link http://wikisend.com/download/302346/ExportImage.img

[no_spam_for_me]

OK, I don't understand why Start: 0x0 and Count: 0x2 don't work, but no matter, your attachment is OK for me:

An example for a normal android parameter:

FIRMWARE_VER:4.1.1
MACHINE_MODEL:rk31sdk
MACHINE_ID:007
MANUFACTURER:RK31SDK
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 3066
CHECK_MASK: 0x80
KERNEL_IMG: 0x60408000
#RECOVER_KEY: 1,1,0,20,0
CMDLINE:console=ttyFIQ0 androidboot.console=ttyFIQ0 init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00002000@0x00002000(misc),0x00008000@0x00004000(kernel),0x00008000@0x0000C000(boot),0x00008000@0x00014000(recovery),0x000C0000@0x0001C000(backup),0x00040000@0x000DC000(cache),0x00400000@0x0011C000(userdata),0x00002000@0x0051C000(kpanic),0x00100000@0x0051E000(system),-@0x0063E000(user)

This is your parameter (ubuntu 13.x):

FIRMWARE_VER:4.0.4
MACHINE_MODEL:rk30sdk
MACHINE_ID:007
MANUFACTURER:RK30SDK
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 3066
CHECK_MASK: 0x80
KERNEL_IMG: 0x60408000
#RECOVER_KEY: 1,1,0,20,0
[B]CMDLINE: initrd=0x62000000,0x00800000 init=/sbin/init root=/dev/mtdblock2 mtdparts=rk29xxnand:[U]0x00008000@0x00002000(boot)[/U],[U]0x00008000@0x0000A000(kernel)[/U],[U]-@0x00012000(system)[/U][/B]

Important for us is "CMDLINE" and the following after "mtdparts"

So we can see, your system has much less partitions than at android...
Each ...@...(...) is a partition
You only have 3 partitions:
- boot
- kernel
- system
@ means like email-addresses "at"
so we know
- boot is at Start: 0x00002000
- kernel is at Start: 0x0000A000
- system ist at Start: 0x00012000

Give me time to find out, how Count: must be for the needing 3 Images, that than can be reflash...

The hole nand dump in 1 file don't help us...
You have to dump the nand per each of these 3 partition in 3 separate file...
HowTo follows...

[no_spam_for_me]

Some instructions by Finless (THX):
Note: Anytime we dump a partition the tool always makes a file called "ExportImage.img" in a folder called "Ouptut".
So every time we dump a different partition it will overwrite that file unless we rename them first!
Don't forget that please.

To do ANY dumping first we need to dump the parameter file of the ROM from NAND.
Why? Because we need the start (offset) and count (size) of the partition or we can’t dump anything.
(BTW: We have done it in last post)

The number before @ is the COUNT and the number after the @ is the START!

The -@ simply says to use the remaining NAND as all of system.
Thus to dump it we must calculate the size! To do this we must know how big our NAND chip is.

Let’s find out the size of the NAND chip.
In the advanced tab click the [ReadFlashInfo] button.
On the right it will display information but we are interested in this:
Flash Size: XXXXX MB
Where XXXXX is the size of your flash chip "page" (Flash CS) size.

Example my K-R42 says:
Flash Size 8192 MB
Flash CS: 0
Thus my full NAND size is 8192 as there is only 1 page
(yes the 0 is a page! The first page starts at 0 and a 1 is the 2nd page).

(((Example Finless Pipo M9 Pro says this:
Flash Size 8192 MB
Flash CS: 0 1 2 3
Thus he would take 8192 and multiply by 4 pages = 32768 MB NAND size.)))

So we now have our total NAND size!
Now a little more math but easy if you follow my instructions.

First we must make the size in MB a REAL GB number (not a MB number in 1000's).
I am going to use 8192 MB (8GB) NAND as an example. (It only had 1 page e.g. Flash CS: 0)

1) Open your PC calculator and again make sure it is set to programmer mode!
2) Make sure your set to Dec (decimal) not Hex mode!!!
2) Type in your NAND size you read or calculated with pages from the tool. My example 8192 MB.
3) Multiply that by 1024. My example 8192 MB x 1024 = 8388608 KB
4) Now do that one more time and multiply 8388608 KB by 1024. My example 8388608 KB x 1024 = 8589934592 Byte.
5) Now divide this number by 512 Byte. My example 8589934592 Byte / 512 Byte = 16777216 Blocks.
So you know what all this math did was take the proper number of bytes and divide them into 512Byte blocks.
This is what is needed by the flash tool and parameter file!
6) Now press the Hex button on the left of the calculator to convert this to a hex number. My example came to 1000000 Hex.
7) OK now we know the total size of our NAND chip in 512 byte blocks in Hex format!
8) Now take this number and subtract the "start" that what was shown in the parameter file.
In your parameter file you have -@0x00012000(system) so your start is 12000 (we don’t use the beginning 0's).
So again your case 1000000 - 12000 = FEE000
We now have our system size! It is FEE000 in hex!!!
9) Enter this number into the count box of the tool. Just add the 0x at beginning of the number so the tool knows it's hex. Again my example is now 0xFEE000
Just a note: 0's in front of any hex number are ignored. So 0x00FEE000 is the same as 0xFEE000.

================================================== ==================

Now the HowTo for you:

1.
please check via [ReadFlashInfo] at tab "Advanced Function" you really have:
Flash Size 8192 MB
Flash CS: 0
If yes, follow next stepps, if not, call me (with values)

2.
boot-partion
a) "Start:" 0x00002000
b) "Count:" 0x00008000
c) [ExportImage]
d) ...wait till finish
d) go to directory "Output" and rename "ExportImage.img" to "boot.img"

3.
kernel-partion
a) "Start:" 0x0000A000
b) "Count:" 0x00008000
c) [ExportImage]
d) ...wait till finish
d) go to directory "Output" and rename "ExportImage.img" to "kernel.img"

4.
system-partion
a) "Start:" 0x00012000
b) "Count:" 0x00FEE000
c) [ExportImage]
d) ...wait till finish
d) go to directory "Output" and rename "ExportImage.img" to "system.img"

System is backuped

[PHYSC]

Some instructions by Finless (THX):
Note: Anytime we dump a partition the tool always makes a file called "ExportImage.img" in a folder called "Ouptut".
So every time we dump a different partition it will overwrite that file unless we rename them first!
Don't forget that please.

To do ANY dumping first we need to dump the parameter file of the ROM from NAND.
Why? Because we need the start (offset) and count (size) of the partition or we can’t dump anything.
(BTW: We have done it in last post)

The number before @ is the COUNT and the number after the @ is the START!

The -@ simply says to use the remaining NAND as all of system.
Thus to dump it we must calculate the size! To do this we must know how big our NAND chip is.

Let’s find out the size of the NAND chip.
In the advanced tab click the [ReadFlashInfo] button.
On the right it will display information but we are interested in this:
Flash Size: XXXXX MB
Where XXXXX is the size of your flash chip "page" (Flash CS) size.

Example my K-R42 says:
Flash Size 8192 MB
Flash CS: 0
Thus my full NAND size is 8192 as there is only 1 page
(yes the 0 is a page! The first page starts at 0 and a 1 is the 2nd page).

(((Example Finless Pipo M9 Pro says this:
Flash Size 8192 MB
Flash CS: 0 1 2 3
Thus he would take 8192 and multiply by 4 pages = 32768 MB NAND size.)))

So we now have our total NAND size!
Now a little more math but easy if you follow my instructions.

First we must make the size in MB a REAL GB number (not a MB number in 1000's).
I am going to use 8192 MB (8GB) NAND as an example. (It only had 1 page e.g. Flash CS: 0)

1) Open your PC calculator and again make sure it is set to programmer mode!
2) Make sure your set to Dec (decimal) not Hex mode!!!
2) Type in your NAND size you read or calculated with pages from the tool. My example 8192 MB.
3) Multiply that by 1024. My example 8192 MB x 1024 = 8388608 KB
4) Now do that one more time and multiply 8388608 KB by 1024. My example 8388608 KB x 1024 = 8589934592 Byte.
5) Now divide this number by 512 Byte. My example 8589934592 Byte / 512 Byte = 16777216 Blocks.
So you know what all this math did was take the proper number of bytes and divide them into 512Byte blocks.
This is what is needed by the flash tool and parameter file!
6) Now press the Hex button on the left of the calculator to convert this to a hex number. My example came to 1000000 Hex.
7) OK now we know the total size of our NAND chip in 512 byte blocks in Hex format!
8) Now take this number and subtract the "start" that what was shown in the parameter file.
In your parameter file you have -@0x00012000(system) so your start is 12000 (we don’t use the beginning 0's).
So again your case 1000000 - 12000 = FEE000
We now have our system size! It is FEE000 in hex!!!
9) Enter this number into the count box of the tool. Just add the 0x at beginning of the number so the tool knows it's hex. Again my example is now 0xFEE000
Just a note: 0's in front of any hex number are ignored. So 0x00FEE000 is the same as 0xFEE000.

================================================== ==================

Now the HowTo for you:

1.
please check via [ReadFlashInfo] at tab "Advanced Function" you really have:
Flash Size 8192 MB
Flash CS: 0
If yes, follow next stepps, if not, call me (with values)

2.
boot-partion
a) "Start:" 0x00002000
b) "Count:" 0x00008000
c) [ExportImage]
d) ...wait till finish
d) go to directory "Output" and rename "ExportImage.img" to "boot.img"

3.
kernel-partion
a) "Start:" 0x0000A000
b) "Count:" 0x00008000
c) [ExportImage]
d) ...wait till finish
d) go to directory "Output" and rename "ExportImage.img" to "kernel.img"

4.
system-partion
a) "Start:" 0x00012000
b) "Count:" 0x00FEE000
c) [ExportImage]
d) ...wait till finish
d) go to directory "Output" and rename "ExportImage.img" to "system.img"

System is backuped

Thanks for all your help and the trouble you have gone through just to help a noob like me,i now have as follows in seperated files:

boot:16384kb
kernel:16384kb
system:8,351,754kb

The total 7.99gb this is including the folder named Android which is empty and automatically created in the output folder upon dumping i believe?

Now my final question is how do i restore? I take it i need to use either my old parameter file or need to make a new one? and i assume that the loader is still the prior used 1.4 version?

Thank you ever so much,you have spent forever teaching me this and it won't go unmentioned.

[no_spam_for_me]

restore / reflash

I have made a package so you only have to copy the directory "Output" in it and start the "ROM_Flash_Tool_137.exe" (by Finless)...
I'm not sure if [Erase NAND (IDB)] is really needing because you flash the nearly hole nand...

Worth case it crashes and you must reinstall, but I don't think so ...

To test it, you can make after the backup some significant changes at your system (perhaps at desktop) so you can see, whether it reflash the backup or not...

[no_spam_for_me]

1.) ... including the folder named Android which is empty and automatically created...
2.) and i assume that the loader is still the prior used 1.4 version?

1.) not at me, but only another mystery like why you don't able to dump Start: 0x0 to Count: 0x2 ...
2.) don't understand what you mean? I have now download the picuntu and took the "RK3188Loader(L)_V1.20.bin" and the parameter is the same as above I have extract...
BTW: with my pack it is able to use the original 3 img's too without unneeding overhead

[PHYSC]

I have made a package so you only have to copy the directory "Output" in it and start the "ROM_Flash_Tool_137.exe" (by Finless)...
I'm not sure if [Erase NAND (IDB)] is really needing because you flash the nearly hole nand...

Worth case it crashes and you must reinstall, but I don't think so ...

To test it, you can make after the backup some significant changes at your system (perhaps at desktop) so you can see, whether it reflash the backup or not...

Wow (made me a package) that is amazing,when you say copy the directory you mean copy and paste the androidtool 2.1 output folder into the ROM_Flash_Tool_137_ubuntu main folder?

I still can't get over the fact you created a package for me, it looks a work of art

Sorry to be a pain,my middle name must really be laymans lol.

[no_spam_for_me]

yes the folder, because I use the foldername in front of the filename (Output\boot.img)...

To archive your backub perhaps rename the folder like "Output_20140113" (YYYYMMDD) and make an archive with winrar or so on...
Don't forget to rename the folder after extract to "Output" if you want to flash it back...

[PHYSC]

yes the folder, because I use the foldername in front of the filename (Output\boot.img)...

To archive your backub perhaps rename the folder like "Output_20140113" (YYYYMMDD) and make an archive with winrar or so on...
Don't forget to rename the folder after extract to "Output" if you want to flash it back...

Going ahead i shall not erase 1st go,if it requires erase i'll leave it until the next go,and i shall get back.
Thanks you truly are amazing,i hope you have a job in this because you are very good at it.

Ok back already,erase nand must be used,but it is writing it currently i shall be back to confirm the restore.

Ok flash succeeds,but the system drops this error: the disk drive for /tpm is not ready yet6 or not presenty.press F to fix the errors or C to continue without mounting or M for manual recovery. so i say F to fix errors,and then it tries at mouse pointer black background. And there is no os booting up,however upon 1st error i remembered a 16gb card inserted,the only downside is i had formatted the lot of that card and set to ext4 partition after removing it from the unit silly i know?,once the card was inserted mid error i said fix errors.So it it proceeded to attempt the fix and to boot,it led to a black screen, then started reverting to the screen prior to shutdown, and then it was endlessly hanging at that screen,what i am in the process of now is preloading the original picuntu bootloader and parameter with this 16gb sd inserted just to see if it ammends anything at all? I triple erased nand prior to be sure it's empty not that i nbeed to take that step.Fingers crossed slowly probably but definately will be back to follow up my findings with you.

Just a note out of curiosity it states the files being flashed are 4190211kb i am no expert but i am thinking it sound small?

Ok done the method i previously said ie.added 16gb sd back,then flashed over a freshly erased nand after 3 erases,i used the parameter and the loader added from the picuntu 4.5 folder,and booted after flash.

I then got boot to a errors found window again with i for ignore option i selected that,and now it seems like a it's rebuilding or processing a huge list,kind of like a command line rebuild page,i am awaiting a fail or pass on this it's stating all kinds of things and in the lines it says set next to each as if assigning files to be utilized by an os boot.

eg. rtl818..........Fu_PwrMode_cmd

loads and loads of these 1 by 1 slowly appearing to be set?

[no_spam_for_me]

Just a note out of curiosity it states the files being flashed are 4190211kb i am no expert but i am thinking it sound small?

Can you explain? Witch file do you mean? At witch point? ...
Because you wrote

boot:16384kb
kernel:16384kb
system:8,351,754kb

The rest: Sorry can't help you...

[PHYSC]

Hi got a k-r42 which i managed to stick ubuntu 13.10 saucy salamander on,now some how i got Grsync running well,but it get's to 99% and produces a failed with errors message box after nearly 2hrs of waiting around,so i have uploaded it which you'll find the link for below,just extract the zip to read the .txt file inside containing the log report from Grsync.

LOG: http://wikisend.com/download/196914/rsync log errors.zip

Please can somone help me out herethe backup ,itself also has loads of files missing in the backup created, missing things i have found so far are eg.usr folder which is completely empty as are some other folders,don't know about files being missing though yet?
Was really hoping someone might have a fix for it or be able to guide me a bit as i am no developer.

Thanks in advance everyone.

Well the moaning i found is wifi related so i guess the kernel img was not dumped right but unsure realy,i'll try again but use the initial boot and kernel i used as an addition.As that is what i guess it will linking to the installation in the backup.

[PHYSC]

Can you explain? Witch file do you mean? At witch point? ...
Because you wrote



The rest: Sorry can't help you...

sorry never responded,the system file was the answer mate.in fact i am coming at it with a different aproach,i forgot as always,basically it took lewy on before nand erase previously to get picuntu on it with ubuntu simulttaneous,so trying now flash lewy hfwI then erase ththen your tool as stated to use.Lets see fingers crossed and touch wood (my head) lol

Be back soon with a result

The mentioned method failed i'll try to load lewy again then not erase and reflash using your tool then. As it stands it goes through to load and gives me 71.740123) EXT4 -fs error (device mtdblock2) ext4-nb_generate_buddy_736:group 35, 27648 blocks in bitmap, 22317 in gd

Or a line to that effect,then leading on to hang then produce shed loads of deleted inode :referenced errors that then hang they pertain to mtdblock2?

Going to reflash withoutr erase after lewy20041 firmware and then flash yopurs no erase and get right back.

[no_spam_for_me]

It's not my tool (Finless), I've only configured it... it is the "config.cfg" witch is loading by default...

1. but at right windows there are no errors during the flashing?
(you can find a log-file of the output at the folder "Log"... At the moment I don't know, how the tool handles different log at a same day... perhaps delete all log-files at the folder "Log"... than flash... after it is done, attach the log-file so I can have a look at it)

2. if there is an error, try to flash it more than once
(because I've read something that Finless has problems and flashes more than once (I think without erase nand between it))

3. try the "RKAndroidTool.exe" from the picuntu archive; it works if you only copy the exe to my folder because it use the same format at "config.cfg" and "setting.ini"

--------------------

BTW:
If I ask google about "tpm" I found out it means something with decryption...
If I ask google about "/tmp picuntu" I found out that aloksinha do at 3.0.8 something with it...
Generally Ubuntu (Linux) uses decryption for the filesystem...
If picuntu too and perhaps it uses the space Start:0x0 with Count: 0x2000 not only for parameterbut for decryption-information too, perhaps you get the problems because of that...
Aloksinha or any other picuntu guru is the only one who can answer that question...
Perhaps you should open a new thread at the linux-area http://www.freaktab.com/forumdisplay...u-Ubuntu-ports here at the board with a reference to that backup-way http://www.freaktab.com/showthread.p...l=1#post146019 what we try at the moment?...