Announcement

**andbroe** · 05 July 2013, 11:22

Missing recovery.img

Trying to flash your 1.2 ROM I discovered that the recovery.img is missing in the zip file. I then used the file from your 1.1 ROM and as it looks, all went well. Will start testing the new ROM asap.

Regards
andbroe

**andbroe** · 07 July 2013, 09:34

Installed version 1.2 and it is working good

Hi Randy
Hope this is the correct place to send you feedback on your ROM.

Just to let you know, that I installed your version 1.2 (using the recovery.img from V1.1) and everything seems to work well. I had some initial problems installing the drivers on my PC. But this semms to be a very common problem with those drivers. Another short moment of panic occurred when doing the "EraseIDB" stuff. The RKAndroidtool only counted to 4096. Did it twice, same thing, crossed my fingers and continued, hoping i had not bricked my M6.But in the end, all was well. The device rebooted quickly into CWM and then the new bootanimation started.

Pity, we dont have a fully working CWM Recovery yet. I would like to save a copy of my system before starting to tweak it using PimpMyROM and tools alike. But who knows... one day.

Thank you for your excellent work on this ROM. Hope to see still some more in the future.

**rrileypm** · 07 July 2013, 12:21

Pipo M6 4.2.2 RileyROM 1.2

I know in the readme I state a higher number on the erase IDB. Sorry for that. I'm rewriting my instructions to be less specific in some places...and more specific in others.

Thanks for the feedback. I am trying to learn how to make my own CWM for my ROMs. I'm more of a TITANIUM guy, myself...more options.

Randy

**030basti** · 10 July 2013, 19:49

Did you already update the readme file here (http://www.freaktab.com/showthread.p...hlight=pipo+m6)

I have the 3g version of the M6, but when i download your zip it says "This ROM is based on the PiPo M8pro offical firmware released on 6-26-13", so I guess your read me isn't updated for beginners like me^^.

Thanks for your help

**pr0xZen** · 10 July 2013, 23:44

Originally posted by rrileypm View Post

I know in the readme I state a higher number on the erase IDB. Sorry for that. I'm rewriting my instructions to be less specific in some places...and more specific in others.

Thanks for the feedback. I am trying to learn how to make my own CWM for my ROMs. I'm more of a TITANIUM guy, myself...more options.

Randy

I see both sides. I too, prefer Titanium Backup for app & launcher restoration - great stuff with plenty of options - and as long as we're thread lightly in regards to restoring system applications, we're good. Its a great and flexible tool - although everything has its limits.

In regards to total nandroid backups, complete "snapshots" - and the restoration of these - this is CWM (or TWRP) domain. There's some kinks to be worked out across different kernels if I understand correctly, but my point stands.

Wasn't there a TWRP release for the M9... ?

**rrileypm** · 11 July 2013, 00:48

Re: Pipo M6 4.2.2 RileyROM 1.2

The point to watching the erase idb process is very simple...and while the specific number doesn't really matter, you need to watch and make sure it counts up to the whole number. Sometimes it will count up 5 or 6 blocks and tell you it is complete...but it really didn't erase the idb. I'm trying to explain in those instructions that if it does this...you need to either wait a few seconds longer before you start after getting into flash mode...or you need to recheck your USB connection. It is a solution to a common problem. I explain it better in my new readme file...which will be included in all future ROMs.

You guys are keeping me on my toes...but that is great. If I can do more to make this an easier process please let me know.

I'm just happy that more people are discovering that these devices can be improved upon sooooo much with custom firmware.

Sent from my M5

**captkronos** · 12 July 2013, 11:32

Problem with flashing

Just received by M6 3G and thought I would try flashing your RileyROM however I am experiencing a problem with the flashing process.
I run RKAndroidTool and get the "Found RKAndroid Mass Storage USB" message. (Your instructions state "Mass Storage Device" rather than "Mass Storage USB" - not sure if that is significant.) I then click on Reboot2Flash and get the Flash Mode Success message. I click on OK. And then nothing else happens apart from the status message gets updated to "No Found RKAndroid rock usb" and the M6 screen goes black and seems to lock up. I have waited for a couple of minutes in this state but nothing happens.

To get the M6 working again I hold down the power button. At which point RKAndroidTool displays the "Found RKAndroid Mass Storage USB" message again.

Andy ideas?

Thanks.

**pr0xZen** · 12 July 2013, 13:44

Originally posted by captkronos View Post

Just received by M6 3G and thought I would try flashing your RileyROM however I am experiencing a problem with the flashing process.
I run RKAndroidTool and get the "Found RKAndroid Mass Storage USB" message. (Your instructions state "Mass Storage Device" rather than "Mass Storage USB" - not sure if that is significant.) I then click on Reboot2Flash and get the Flash Mode Success message. I click on OK. And then nothing else happens apart from the status message gets updated to "No Found RKAndroid rock usb" and the M6 screen goes black and seems to lock up. I have waited for a couple of minutes in this state but nothing happens.

To get the M6 working again I hold down the power button. At which point RKAndroidTool displays the "Found RKAndroid Mass Storage USB" message again.

Andy ideas?

Thanks.

The difference in those instructions and what you're seeing, isn't important in this case - its clearly the same thing. But, good of you to make note of it - means you're paying full attention

The reason nothing happens when you Reboot2flash - is that RockShip drivers aren't installed. Open Device Manager (its in Control Panel). Once you've rebooted to flash mode - you should (hopefully) see an "Unknown Device" in the device manager. Right-click that, select update driver. Do NOT let windows search for a driver, but browse for it yourself. In the ROM kit you downloaded there should be a folder with drivers. Make sure you select the folder wich is right for your system (x64 for 64-bit, x86 for 32-bit) and Windows Version.

After you've done this - the flash tool should show "Found RKAndroid Loader Rock Usb". If it still doesn't show it, boot to flash mode again (When in flash mode - the device will automatically power off if there is no flashing activity, within 2 minutes).

**captkronos** · 12 July 2013, 15:02

Originally posted by pr0xZen View Post

The difference in those instructions and what you're seeing, isn't important in this case - its clearly the same thing. But, good of you to make note of it - means you're paying full attention

The reason nothing happens when you Reboot2flash - is that RockShip drivers aren't installed. Open Device Manager (its in Control Panel). Once you've rebooted to flash mode - you should (hopefully) see an "Unknown Device" in the device manager. Right-click that, select update driver. Do NOT let windows search for a driver, but browse for it yourself. In the ROM kit you downloaded there should be a folder with drivers. Make sure you select the folder wich is right for your system (x64 for 64-bit, x86 for 32-bit) and Windows Version.

After you've done this - the flash tool should show "Found RKAndroid Loader Rock Usb". If it still doesn't show it, boot to flash mode again (When in flash mode - the device will automatically power off if there is no flashing activity, within 2 minutes).

Excellent, that worked. (I did need to boot into flash mode for a second time for it to be recognised.)

Thanks.

**pr0xZen** · 12 July 2013, 15:20

Originally posted by captkronos View Post

Excellent, that worked. (I did need to boot into flash mode for a second time for it to be recognised.)

Thanks.

Glad to hear it worked out

**030basti** · 13 July 2013, 12:59

Originally posted by rrileypm View Post

The point to watching the erase idb process is very simple...and while the specific number doesn't really matter, you need to watch and make sure it counts up to the whole number. Sometimes it will count up 5 or 6 blocks and tell you it is complete...but it really didn't erase the idb. I'm trying to explain in those instructions that if it does this...you need to either wait a few seconds longer before you start after getting into flash mode...or you need to recheck your USB connection. It is a solution to a common problem. I explain it better in my new readme file...which will be included in all future ROMs.

You guys are keeping me on my toes...but that is great. If I can do more to make this an easier process please let me know.

I'm just happy that more people are discovering that these devices can be improved upon sooooo much with custom firmware.

Sent from my M5

Hey Riley,

can you upload your new readme file here? I'd like to flash my device (M6 MAX 3G) but would prefer to do it with the new readme file since I'm new to all this (ex iOS user

)

Thanks for your work!

**pr0xZen** · 13 July 2013, 14:12

Yeah Randy - maybe you could upload it to Freaktab and post a link to it on your ROM threads initial post. This way, I'tll be easily available for those ROMS already uploaded - even though it isn't bundled in the kit

**rrileypm** · 13 July 2013, 16:28

Pipo M6 4.2.2 RileyROM 1.2

I'm working on it. My Internet connection is giving me trouble this morning. Stay tuned.

Randy

**rrileypm** · 13 July 2013, 16:37

Here is a link to my new First Time User Guide.

Download

Thanks to Pr0xZen for making this for me.

Announcement

Announcement

Pipo M6 4.2.2 RileyROM 1.2

Pipo M6 4.2.2 RileyROM 1.2

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

What's Going On