Pipo M7 Pro RileyROM 2.8 KitKat

[Sokittoya76]

Recovery.img

I want to thank Chinese developer Edge Xuan for putting together a custom ROM based on an otherwise unreleased new version of KitKat. I normally wouldn't use another developer's work for a RileyROM, but this one seems to be the best firmware so far, and I'm not getting updates very quickly from Pipo.

I ported this ROM from the M9 Pro RileyROM v2.7...which basically means that I made the screens M7 Pro specific and used the kernel from my M7 Pro v2.7. I've been testing it all week on my M7 Pro, and I'm pretty happy with it.

While Edge Xuan provided an outstanding custom firmware, I did add some of the usual RileyROM features:

Rooted with SuperSU
Init.d Support added with Busybox commands
Debloated of all unneeded apps
Google Play Store fixes
Auto Install feature added LINK
TWRP recovery added after first boot by Abdul_Pt
English Default
For this ROM I added the standard KitKat keyboard (missing from the Chinese version)
Your choice of 2, 4, 6, 8, or 12gb user app space
Updated Google Apps
Boot Animation by me
Flash Tool by Finless
Made from 900SuperSport's Freaktab Kitchen
First Time User's Guide

Download

Edit: I was able to get the official Pipo firmware that this Edge Xuan ROM was made from, and made a whole new ROM without the changes he made. This is v2.8.1. Otherwise, it has all of the same features as the 2.8 ROM.

v2.8.1

Enjoy!!!!!!!

Please donate to support future RileyROM development.

Hey Riley,

First post on this forum so big thanx to everyone in the PIPO scene. What would we do without your Genius.

I thought I could start by posting a working TWRP recovery for your 2.8 Kitkat.

Thanks for all your hard work guys

See this Link DOWNLOAD

[georgeburke]

Need Help Getting My System Back... HELP HELP HELP PLEASE

I flashed the latest ROM and now I just have an android robot lying down with the front hatch opened and a red triangle on it. What do I do now?

[MFinchy]

Did you have flashed the loader as well??
Pipo users: READ THIS BEFORE FLASHING A KITKAT ROM!!!!!

[Mick J]

I flashed the latest ROM and now I just have an android robot lying down with the front hatch opened and a red triangle on it. What do I do now?

Guess you will have to try to flash again, sounds like a motown song - been singing it a bit myself

All the kitkat Riley rom's I have downloaded have the loader option "ticked" in the flash tool, it gets a bit more complicated if you want to switch back to jellybean but my understanding is that if you erase nand and flash say 2.8.1 with the flash tool you get the kitkat loader, assuming you did not tickoff the loader option?

My understanding is once the kitkat loader is installed there is no need to keep flashing it for new kitkat rom's, 2.9 or 3.0 say!!

To go back to jellybean or whatever you need to earse nand with the kitkat flash tool, then flash jellybean including the loader with the jellybean flash tool (this is ticked off in jellybean flash tools, need to tick on for first time) an easy step to miss.

[rrileypm]

I agree...the problem stems from not ticking the JB loader. That's an important step.

[Mick J]

Thanks for that Randy, I sometime think I could be giving the wrong advice

hence the use of "my understanding is" but as I cribbed it all from your posts.............

I also have a sneeking suspicion that georgeburke was only flashing kitkat not jumping back and forth, is it possible some M7pro's are having problems with kernels or other variables or was Scotty right - tab canna take it captain ......... I have seen the little green man myself a few to many times lately and it's not just the rioja.

[rrileypm]

Normally on first boot, recovery is supposed to format all of the partitions based on the information provided in the parameter file. In KK ROMs, the new metadata partition is expressed in the parameter file...but the loader must be correct to allow for this change. If those files don't match...you get the broken android from recovery.

The only solution is to get into flash mode manually...and flash the ROM with all of the parts checked...including the loader.

The same is true switching back to JB. The KK loader looks for a metadata partition, which isn't there...so recovery crashes.

You guys are lucky you even get the crashed recovery...sometimes the device is bricked.

[herrjemineh]

And it is a known problem for mor than three months, there are so many advices to find, e.g how to fix, or to do in advance or whatever, there are even whole manuals how to proceed. And still the same problems persist, because people don't read. I mean they even register to a help forum where they COULD FIND necessary informations, but once registered, people stop reading immidiately except the answers to their own questions.... a devil's circle....

[Mick J]

I can see the problem switching back from kitkat to a previous rom that needs the loader to be switched back as well, and yes the information is there, for some of us it takes a few reads to get the jist of whats happening or should be happening.

And yes we are lucky to see the crashed recovery and not a bricked tablet, lets hope georgeburke can pull it back.

My first kitkat flash went really well, why shouldn't it, everything is in the download, something changed after a while and my tablet started the rebooting stuff, I flashed back to jellybean with a few hickups, now the tablet is not quite right, still just closes after a while, I can reboot but same same, devil's circle indeed.

Do appreciate the work all you guys put in, thanks.

[rrileypm]

That's why I still check the loader by default on all of my KK ROMs...but from now on I guess I need to do the same on JB ROMs, too....I never even considered as many people going back and forth so much. I tend to move forward...not backwards. While there are some features like multi windows and full screen mode missing (which I never liked, anyway)...KK is faster, smoother and seemingly more reliable. Even though Pipo won't commit to a full fledged KK release.

IFive is shipping their tablets with KK. And their versions are about the same as the beta Pipo leaked versions...except they've figured out how to implement hiding the button bar. That's about all, though.

I'm sure that Pipo's hesitation stems from not wanting to support the thousands of people who can't read directions before bricking their devices trying to flash KK...you think we have that problem here...try doing it times a thousand...in every language on earth.

[koshk]

Hi all! I managed to brick my M7, I am pretty sure I followed all the steps correctly. Have to dig deeper into that later, but on another issue I had with M7 was Netflix dropping out and the tab rebooting or freezing after 5 to 10 minutes into watching. Is it a common phenomenon or was it just me?

[acasel]

My Impression: Deep sleep seems to work, if you switch modem power of. Otherwise not. I like it that this option is available again. WLAN very well, stable 30mbit download on a 50mbit fibrewire connection, clash of clans not working anymore, but this is due to the last update not to the Rom. So far quick and stable, only booting time seems long. The Kamera problem is still going on: no PDF scanner or barcode scanner working. Gps not tested. With 1704mhz cpu and 720mhz ram clock 21103 point antutu and 5600 quadrant but unfortunately still 37 fps instead of 44 in epic citadel compared to jellybean.

Hello FOR PIPO USERS who cannot play clash of clans

or rockchip tablet chipsets

Tick "Disable HW overlays" under the Developer options, and flickering and freezing should disappear.

BTW: Riley TYVM for the ROM.. ^_^
One thing that could make this better if we could have a button to kill all recent app history with just a press of a button.

Task killers on android wont erase the history in recent app list

any suggetions...Thanks in advance

[herrjemineh]

But does anyone know why the unreal engines like epic citadel show about 20% less power compared to jelly bean? The 3d parts of antutu or quadrant seem to be quite fast, but real racing 3 and epic citadel run MUCH faster on jelly bean, which sucks because the rest of the kit Kat system, except the Kamera thing perhaps, is running quite well

[herrjemineh]

Wheeee.... clash of clans is running again after enabling 'disable hw overlay' as adviced by acasel... i like

[Al33]

Does anyone use Evernote? Since i flashed, i can't use the page-camera anymore. The screen would freeze after a split second. I can still take a photo and access the settings etc. but the screen shows only what the camera has spotted when i turned it on. Now i can't "aim" with the camera because I can't see what I'm aiming for with the cam =(

The Android camera itself works just fine, it's only with the app implemented camera function. Any Idea what might causes this? I even reflashed but it didn't help.