Pipo M9 Pro KitKat 4.4.4 Rom

[kheno]

Ok, I'm fast learning here.
And with the vacation in a few days, it's a big rush in getting all things done at work.

Give me some time, and I'll make dumps of all those files.

M-M-C, I've red that in the meantime a new version of that 4.4.4 rom would be avalable (probably widget stuff could be solved.)

I've tried to get access to that qq group, but no luck at the moment.

Could you have look into it and provide me that new version? thx

[kheno]

Just missed your post!
Thanks erik90!



Would it not work, I'll try to dump the images.
In the meanwhile I'll ask M-M-C if he can follow up and see if the new version has something new to offer.

[rrileypm]

OK, I will see what I can do with these files. It helps having everything from a working ROM.

[kheno]

checked it; no new version of the rom available.

erik90, did you manage to get the needed files? Do I need to look into dumping them?

[erik90]

checked it; no new version of the rom available.

erik90, did you manage to get the needed files? Do I need to look into dumping them?

Yes the dump was successful and Randy made a new rom of them for me to try. I tried to flash his rom successful two times but unfortunately I get stuck in a bootloop.

[kheno]

dumped all except userdata
attached torrent file. download should be fast

If torrent is a no go, let me know, I'lll look into upping the file to a direct download host.

[rrileypm]

So far, every time I try to put this in a ROM kit, it won't boot. I'm sure it is something simple.

[erik90]

So far, every time I try to put this in a ROM kit, it won't boot. I'm sure it is something simple.

I´m thinking, maybe it can have something to do with the recovery?
Everytime after the flash has been completed with one of your other roms the tablet has booted into recovery to wipe some stuff (data etc.) and then reboot, but not with this one you cooked for me. It goes straight to the bootlogo and then bootloops.
The recovery that you needed to install this rom was some other chinese TW recovery, "Oh yeah, you NEED the chinese teamwin recovery, TWRP won't work!".
Quoted from M-M-C post #382

[rrileypm]

Possibly so. I don't remember...and can't check because I'm at work...but I don't think there was a recovery image in the original Omni zip....was there?

[SirHastur]

No, only a boot.img

Possibly so. I don't remember...and can't check because I'm at work...but I don't think there was a recovery image in the original Omni zip....was there?

[erik90]

After some testing I have successfully booted the rom you sent to me.

What I did was to first install RileyROM 3.4 in the usual way.
Then I flashed your OmniROM 1.0 without erasing NAND (IDB).
Then I ended up in a boot loop as usual, after that I rebooted the tablet to recovery mode and did a wipe with "Full Wipe" "Data" and "Internal Storage".

After these steps the tablet started up!

I don´t know if it just was the last step that fixed things but at least we are one step closer.



EDIT: I have done some more testing and it doesn´t boot if you don´t dirty flash omnirom over rileyrom and then wipe from recovery.

Another thing that I noticed is that the omnirom uses all the space that is left on the internal memory (no size parameters) for apps so depending on which parameter you use, you just lose that space.

[SirHastur]

Hello Kheno,

Can you please upload the full dump?

dumped all except userdata
attached torrent file. download should be fast

If torrent is a no go, let me know, I'lll look into upping the file to a direct download host.

[kheno]

Here you go:

http://ul.to/4c6jxzs1

[erik90]

Here you go:

http://ul.to/4c6jxzs1

I downloaded your dump and realized that your system.img is smaller than the one I dumped, maybe something went wrong with mine. rrileypm maybe you should try to make a build from his dump as well.

[rrileypm]

The size of the system.img in a dump depends on the parameter file that was on the device when you flashed the update.zip. As with all of the files, the dump method saves the contents of the whole allocated space of the partition. When I'm working with these files, I have to remove all of the extra unused space to get down to the actual working file.

As for the system.img. My process involves making a new system.img of the whole partition size allocated in the parameter, so all of the space can actually be used. Then I copy the contents of the original system.img over to it. I started doing this when it was necessary to upgrade the file system to ext4. Now they just come that way...but I've kept the same process.

I'm still not sure why my version of this ROM isn't booting.