Stock ROM 0719 Kernel#26 - Elijah - ROM - August Tablets

[Finless]

Is it possible to flash 1.5a with the dark kernel, and then also flash the dumps recovery.img and 'reboot to recovery' to see if having only the recovery with built in working lights kernel will make it light up?

Ok flashing 1.5a kernel 485 now but with the dumps recovery.img after installing it should boot into recovery with lights working and then itll use 485 and lights go out again perhaps?

Understand, my 1.5a only has one kernel. So everything should work with your #26 kernel and my recovery, boot, etc.

Bob

[Meneer]

Thats not the issue.

I was testing the following:

You said 'So it is in the kernel.... WIERD that recovery has lights with other kernels.'

And now I confirmed the reason I had backlight earlier with tuen's build, is that it was because the recovery had its built in #26 kernel providing the light, it was in fact this kernel and not 'other kernels'.

Now reflashed your complete package + #26 to get everything to work again here :-)

The next step is SD card testing + seeing what else is different in this kernel and in the new system.img

[Finless]

Elijah is an aliexpress seller, sells this tablet as OEM, I assume any new kernels we get will be rev2 compatible, unless this is a knockoff made by some other company. And even then, the knockoff company could still bring new kernels.

It amazes me that a "seller" would have the kernel sources to make new kernels!!!!!!
Then be able to mod hardware like this over and above what Yuandao has.....
This is not an easy task unless he has some "inside" info from Yuandao.... So he must have for sure! Only way I know to be able to make mods like this!

Bob

[Meneer]

I dont think elijah did any of it, he simply purchased tablets from supplier X and sold them to us, supplier X could be a knockof yuandao company, or it could simply be yuandao releasing this new stuff without putting it on the website etc. I assume its the latter.

In your tool, what is the backup.img option?

[Finless]

And now I confirmed the reason I had backlight earlier with tuen's build, is that it was because the recovery had its built in #26 kernel providing the light, it was in fact this kernel and not 'other kernels'.

Yes that is why.... this ROM has a kernel in boot and recovery! So you had lights in both those.

I never understood why ROM makers put the same kernel in 3 different places.... TOTALLY uneeded!
The ONLY reason you would do that is to have a different kernel for some reason in one or the other.
Someone needs to teach these people how to make ROMs... Having 3 kernels is a waste of NAND space!

Bob

[Meneer]

Is this all correct?

In recovery, system will use recovery supplied kernel, unless there is a seperate kernel.img, this seperate img will override the recovery one.

For rest of system the seperate kernel.img will be used, unless there is a boot.img kernel, in which case this will override the seperate one.

[Finless]

FYI, while my tab is doing CWM backups to test SDcard corruption, I compared the kernel to others. This is in fact heavily modified from all the others!

So this is a very unique kernel compared to the rest!

I am going to do a full compare on system.img but honestly my first go around, the file dates are different but I think not much here has changed! We shall see...
I bet I will have to still add my
Wifi Fix
Battery fix
Adhoc wifi patch
etc....

Much testing to do now.

Bob

[Meneer]

I can confirm your rom has better wifi than the stock one has.

I am now using the supplied explorer to MOVE 2 files off my 8GB FAT32 SD (3GB and 650MB) to internal memory, after which I will COPY them back, and put the SD back in my computer to compare MD5 hash before and after the copying.

Will this help aswell?

[Finless]

Is this all correct?

In recovery, system will use recovery supplied kernel, unless there is a seperate kernel.img, this seperate img will override the recovery one.

For rest of system the seperate kernel.img will be used, unless there is a boot.img kernel, in which case this will override the seperate one.

Not correct. So how this all works.
If misc.img is flashed, it will always reboot into recovery. Recovery will use it's kernel if it has one. If not, it will use kernel.img

Once recovery is done, it reboots and boot.img takes over. If boot.img has a kernel it will boot system using the kernel in boot.img. If boot.img does not have a kernel, then once again it will use kernel.img.

So as you see "you could" use different kernels if you needed to. So far in the 100's of ROMs I have done, I have never seen one with a different kernel in each place!

Bob

[Meneer]

Once one kernel is loaded it will never change kernels until there is a reboot towards a different kernel? Where boot.img will preffer its own, and recovery.img will preffer the seperate kernel.img? If there is no kernel.img AND recovery does not have its own, the boot to recovery will fail or it will use the one in boot.img?

I guess I understand now ;-)

[Finless]

Meneer, you a great guy to have around! Your quick and I like that
I hope you stick around after the initial "Tablet love wears off"!
If you get to a point of making ROMs, I can add you to the team here if you like.

Bob

[Meneer]

Thanks, I am even happier to have you around though ;-) I will stick around if the tablet convinces me I actually have a use for one haha, have not found that use yet... but in the past Ive either had brand name tablets that didnt even play 1080p or chinese -play it all- tablets with shitty screens and slow CPU and crap batterylife. This is something new for me.

I will report back after I have tested a few GB of SD card copy's within the booted OS as opposed to your CW pure kernel testing.

[Finless]

Well sorry to say... SDcard corruption still exists...

I did 2 CWM backups, booted the tab, turned on USB storage, and let windows check the file system. Same issue, corrupted file system!
I let windows fix it and then tried to do a CWM restore of those backups and got a MD5 check error


However.... A NEW IDEA!!!!!
Maybe Windows may report a corrupted file system but maybe Android has no problem. Android has no FAT32 check system. But maybe this kernel is doing something different and while Windows may report corruption, maybe to Android feels it is not corrupted?
So to test this, I am going to do a CWM backup again a few times, then try a CWM restore WITHOUT using Windows to inspect it, and see if CWM compains of MD5 checksum error.

If it does not, then maybe what we have here is the kernel using FAT in some way Windows does not like!

More testing to do....

Bob

[Finless]

Crap

When windows repaired the sdcard file system. It also hosed my previous backups not just the recent ones today

I am glad I backed up SDcard before trying this test..... Now to restore it and try again...

Bob

[Meneer]

Have copied 4GB of vid from sd to internal back to sd, will be watching the video from sd to see if it glitches or anything, after that will check in windows to compare MD5

I want to put 4GB+ files on my sd card, I also want to retain CWM backup capabilities.

Is it possible to format a 32GB SD card as 1GB FAT32 + remainder as NTFS or EXT4 (which, if either, would work?) and if it will work, will it be accessible through micro usb (I am assuming no) or only through putting the sd in computer (where windows will have trouble with either of them because its flash storage, so shouldnt have 2 partitions.. or simply not read ext4 aaargh I guess this is a no go, let me know if there is still an chance however :P