YES! Notpod's dump was good! But not all that is needed is here

[sabercatpuck]

Guess I was a bit late

Had just had the thought to mention that I had these too when I had to step away for a trouble call here at work. Guess I know what the answer would have been if I had asked.
( I am starting to be able to figure out things that might be usefull )

[Finless]

Based on what I have read you need a image called root.img.

This is what the threads on XDA talk about for the Ainol A10 All Winner. I believe root.img is the kernel. Thats pretty important

Bob

[notpod]

Arrggh!

OK. Pulling hair out.

I need 'COM MON _SYS_CONFIG000000.fex' from a extraction of OUR STOCK ROM that we don't have. Is there a way to dig that out of the .imgs? What .img is it in?

It is the HARDWARE description of our tablet, right? So there is no substitute.

ARRGH.

[sabercatpuck]

Might at least give an idea what you are looking for

This is the file from the Onda gingerbread rom I extracted earlier

[notpod]

Yep one of those...

but we need one specific for our tablets HARDWARE config, MEMORY map, etc. This is the spot where the rubber meets the road on having the rom *really* work on our pmid701c.

It is like a loop where we need the thing we don't have in order to create the thing we don't have.

The *real* fix is to get a ROM image from southentelcom. But it has not gone all dark on our star yet. I read somewhere that this info might be extractable from /proc/ on a running tablet, at least for 1 version of the Telecast tablet which is close to ours.

I will pursue that road.

On the simi-good news front: "slowcooker", the name of my ubuntu 10.04 box I put together for this project is up and running fine, is set up for remote SSH and has a successfully compiled thru a kernel / gingerbread build using the Telecast files.

I have busy weekend ahead. So don't expect much more till MON.

BUT IF YOU ARE BRAVE (or CRAZY) ---> You could try this with snowbreeze:

1 Extract a ROM (say the Telecast or ONDA) into the '_extract' folder. That will put A _SYS_CONFIG000000 in there at least.

2 The root.img is VFAT so mount it up and pull out a copy of the bImage (kernel) file and put it into the '_input' folder.

3 Put a copy of system.img, root.img, recovery.img into the '_input' folder. Rename from '.img' to '.fex' IE system.fex, root.fex, recovery.fex.

4 Tell snowbreeze to COOK your rom. If you get a 'output.img' then great. If you have the full android SDK try it in an emulator (my plan when I get there) OR if you are SUPER BRAVE and WON'T MIND NOT HAVING A WORKING pmid701c for a while then:

5 Try flashing with LiveSuite. I WOULD NOT AT THIS POINT!

If you simi-brick the tablet please do not RETURN IT FOR ANOTHER ONE! It can be fixed and you are the reason it needs fixed.

And thats the way it is April 6th, 2012

[sabercatpuck]

i was actually considering it anyway...

It seemed lile the best test of if this idea works is if we can recover from a brick so i was thinking of trying the onda rom anyway. I figure even if it only works to get into clockwork it will be enough to get me back by flashing the image from my other pmid. If it doesnt work at least then i have a good resson for calling sotel and saying i need a copy ( there was something about it being availabe on request)

We will see, not sure if i am brave enough yet

[Finless]

Let me have a look at this file and see what it is about. Downloading now.
My bet is it is similar to the parameter files for RK29. If so I may be able to construct one for you all.

Bob

[sabercatpuck]

think i found the command you were referencing

tried to pull config.gz from proc, when that didnt work i figured ehhh, so now i am pulling all of proc

[notpod]

double ARRG!

sabercatpuck: Thanks for trying the /proc/ bit. Arg #1

The other ARG: Yesterday while I messing with this stuff I missed the HTC Flyer @ Cowboom for $130. I am a HTC person since the WIZARD, I have been waiting and looking and waiting for a HTC flyer under $150 and I missed it! ARG #2!!!!

Bob: Any insights, clues, directions on what to try next is very welcome!

[Finless]

Well I found the binary that process that file.

Mount root.img

mkdir root
sudo mount -t vfat -o loop root.img root

Have a look at the file script.bin (there is a script0.bin which is a left over I think).
Looking at that with a hex editor you can see all of those parameters. Alas the data is not there for the parameters since this is the binary that processes the file.

Bob

[Finless]

Notpod, your recovery.img is not a good dump.

I was poking at it with a hex editor and for sure it looked like a file system to me.

So here is what I did in linux:

sudo e2fsck -v -y recovery.img

It repaired it as best it could.
Then I mounted it

mkdir recovery
sudo mount -t ext4 -o loop recovery.img recovery

All of the files are in the lost+found folder which is typical of a recovered file system. Now recovery.img is very similar to boot.img EXCEPT it has a recovery binary file that boot does not have. Very typical of other ROMs.

But you need to try and get a good recovery.img. You will know you have it when it mounts as ext4 in linux with no errors.

Bob

[notpod]

Eek!

OK Sorry, I will redo and recheck that this evening at the very least.

[artistlogic]

Did you get my dumps finless? In PM?

Sent from my PMID701C using Tapatalk

[sabercatpuck]

Well I found the binary that process that file.

Mount root.img

mkdir root
sudo mount -t vfat -o loop root.img root

Have a look at the file script.bin (there is a script0.bin which is a left over I think).
Looking at that with a hex editor you can see all of those parameters. Alas the data is not there for the parameters since this is the binary that processes the file.

Bob

Found this:

If you don't have a CONFIG1 partition, then you have to "disassemble" the script0.bin. There is a script disassemble ruby tool in one of the directory. You should download a proper sys_config1.fex file though. The ICS for the LY-F1 or Teclast have this file, so you might use them.

here:

http://forum.xda-developers.com/showthread.php?t=1490886&page=6

Trying to find the script now

[sabercatpuck]

Not sure it is all there but this is what I got

I ran the script2fex routine on the 2 script's in the NANDA and this is what came out of it (included the 2 ruby files too):