HPH RK3288 ROM v1.2 by mo123 (20141117)

[mo123]

Hi mo123,to update the SU binary doesn`t work`in your ROM v.1.2. Is it realy important to do this or not ? I love tis Rom .It's great. And the second qustion : Is it possible to update this rom in a higher Version, without new flashing the box in the future( v 1.3).

For v1.3 you have to flash everything.
For v1.4 eg. the partitions will be the same size and you can just upgrade what you want.
Also tried to make simple zip updates, but TWRP recovery is not working properly on RK3288 devices, otherwise it would have been very easy.

You can use Titanium backup to easily backup your apps/data and restore to a new ROM.
Will try to include latest su binary in new ROM. The only reason it's necessary is to give root, doesn't matter if it's an old version.

[DuHaudegenDu]

You have to download the stock ROM of your device.
Then download my ROM with flash tool.
Then use the 2nd or last tab of the flash tool to 'unpack' the update.img(stock ROM).
Then copy the unpacked boot,resource & kernel into my ROM's rockdev/Image folder, replacing the 3 image files already there.
Then flash normally by 'lowerformat' and 'run' on the first tab of the flash tool.

Oh oh... Seems that something went wrong on my ENYBOX EKB328 clone :-(
Like oldhouse has one...
This is my parameter from stock:

FIRMWARE_VER:4.4.2
MACHINE_MODEL:rk30sdk
MACHINE_ID:007
MANUFACTURER:RK30SDK
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 3066
CHECK_MASK: 0x80
PWR_HLD: 0,0,A,0,1
#KERNEL_IMG: 0x62008000
#FDT_NAME: rk-kernel.dtb
#RECOVER_KEY: 1,1,0,20,0
CMDLINE:console=ttyFIQ0 androidboot.hardware=rk30board androidboot.console=ttyFIQ0 board.ap_has_alsa=0 init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0x00002000@0x00004000(misc),0x00008000@0x00006000(resource),0x00008000@0x0000e000(kernel),0x00010000@0x00016000(boot),0x00010000@0x00026000(recovery),0x0001a000@0x00036000(backup),0x00040000@0x00050000(cache),0x00002000@0x00090000(kpanic),0x00180000@0x00092000(system),0x00002000@0x00212000(metadata),0x00400000@0x00214000(userdata),0x00020000@0x00614000(radical_update),-@0x00634000(user)

I load your HPH RK3288 v1.2 2014/11/17 plus the 2GB Parameter file for 8GB Box
Then I try to flash it. Like you decribet here:

http://www.freaktab.com/showthread.php?18706-HPH-RK3288-ROM-v1-2-by-mo123-(20141117)&p=252943&viewfull=1#post252943

After 30minutes nothing happens, just "Testing device" was at status field.
So I log off and log in.
Every flasher now stop at: "Testing device"
Also the RKBatchTool.exe when I try to flash the stock-rom. :-(

WHAT CAN I DO?
WHAT WENT WRONG!

Here the log:

10:21:14 627 AndroidTool v2.3.0.0 start run
10:27:51 792 Layer<2-1-7>:Test Device Start
10:27:51 792 Layer<2-1-7>:Test Device Success
10:27:51 807 Layer<2-1-7>:Check Chip Start
10:27:51 807 Layer<2-1-7>: Check Chip Success
10:27:51 807 Layer<2-1-7>:Get FlashInfo Start
10:27:51 807 <LAYER 2-1-7> INFO:FlashInfo: 00 08 E7 00 00 04 04 00 28 00 01
10:27:51 823 Layer<2-1-7>:Get FlashInfo Success
10:27:51 823 Layer<2-1-7>:Prepare IDB Start
10:27:51 823 <LAYER 2-1-7> INFO:CS(1) (7393MB) (SAMSUNG)
10:27:51 839 Layer<2-1-7>:Prepare IDB Success
10:27:51 839 Layer<2-1-7>ownload IDB Start
10:27:52 681 Layer<2-1-7>ownload IDB Success
10:27:52 697 Layer<2-1-7>:Reset Device Start
10:27:53 697 Layer<2-1-7>:Reset Device Success
10:27:53 697 Layer<2-1-7>:Wait For Loader Start
10:27:54 930 Layer<2-1-7>:Wait For Loader Success
10:27:54 930 Layer<2-1-7>:Test Device Start
10:35:18 800 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_320A#6&1A81 23C&0&7#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
10:35:18 800 <LAYER 2-1-7> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_320A#6&1A8123C&0&7#{a 5dcbf10-6530-11d2-901f-00c04fb951ed}
10:35:19 807 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_320A#6&1A81 23C&0&7#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
10:35:19 807 <LAYER 2-1-7> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_320A#6&1A8123C&0&7#{a 5dcbf10-6530-11d2-901f-00c04fb951ed}
10:35:20 821 Error:RKU_Open-->CreateFile failed,err=2,path=\\?\USB#VID_2207&PID_320A#6&1A81 23C&0&7#{a5dcbf10-6530-11d2-901f-00c04fb951ed}
10:35:20 821 <LAYER 2-1-7> ERROR:TestDevice-->RKU_TestDeviceReady failed,RetCode(-1),path=\\?\USB#VID_2207&PID_320A#6&1A8123C&0&7#{a 5dcbf10-6530-11d2-901f-00c04fb951ed}
10:35:21 835 Error:Layer<2-1-7>:Test Device Fail
10:35:21 835 Layer<2-1-7>: RunProc is ending, ret=0

Greetings by DuHaudegenDu

[oldhouse]

Oh oh... Seems that something went wrong on my ENYBOX EKB328 clone :-(
Like oldhouse has one...
This is my parameter from stock:

FIRMWARE_VER:4.4.2
MACHINE_MODEL:rk30sdk
MACHINE_ID:007
MANUFACTURER:RK30SDK
MAGIC: 0x5041524B
ATAG: 0x60000800
MACHINE: 3066
CHECK_MASK: 0x80
PWR_HLD: 0,0,A,0,1
#KERNEL_IMG: 0x62008000
#FDT_NAME: rk-kernel.dtb
#RECOVER_KEY: 1,1,0,20,0
CMDLINE:console=ttyFIQ0 androidboot.hardware=rk30board androidboot.console=ttyFIQ0 board.ap_has_alsa=0 init=/init initrd=0x62000000,0x00800000 mtdparts=rk29xxnand:0x00002000@0x00002000(uboot),0x00002000@0x00004000(misc),0x00008000@0x00006000(resource),0x00008000@0x0000e000(kernel),0x00010000@0x00016000(boot),0x00010000@0x00026000(recovery),0x0001a000@0x00036000(backup),0x00040000@0x00050000(cache),0x00002000@0x00090000(kpanic),0x00180000@0x00092000(system),0x00002000@0x00212000(metadata),0x00400000@0x00214000(userdata),0x00020000@0x00614000(radical_update),-@0x00634000(user)

I load your HPH RK3288 v1.2 2014/11/17 plus the 2GB Parameter file for 8GB Box
Then I try to flash it. Like you decribet here:

http://www.freaktab.com/showthread.php?18706-HPH-RK3288-ROM-v1-2-by-mo123-(20141117)&p=252943&viewfull=1#post252943

After 30minutes nothing happens, just "Testing device" was at status field.
So I log off and log in.
Every flasher now stop at: "Testing device"
Also the RKBatchTool.exe when I try to flash the stock-rom. :-(

WHAT CAN I DO?
WHAT WENT WRONG!

Greetings by DuHaudegenDu

Same happened to me.
You have to open your device case, and boot it into maskrom mode to be able to flash it again.
Unluckily if no cooker have our device I doubt we will ever be able to flash any of these custom roms.

[DuHaudegenDu]

Same happened to me.
You have to open your device case, and boot it into maskrom mode to be able to flash it again.
Unluckily if no cooker have our device I doubt we will ever be able to flash any of these custom roms.

GREAT! But the question is: How to boot into maskrom mode with an eny ebk328 clone/oem?
This is my pcb.
And I think that this is my nand:


Greetings by DuHaudegenDu

[oldhouse]

GREAT! But the question is: How to boot into maskrom mode with an eny ebk328 clone/oem?
This is my pcb.
And I think that this is my nand:


Greetings by DuHaudegenDu

In the lowest picture, begin counting pins 7&8 from lower left corner: those 2 are the ones you are looking for.

[DuHaudegenDu]

In the lowest picture, begin counting pins 7&8 from lower left corner: those 2 are the ones you are looking for.

THX, it worked after some pm's with oldhouse.

So it is the black arrow you should count to 7-8 pin (only fpr ENY EBK328 clone device):

-connect only usb
-start Rockchip Batch Tool v1.7 as admin
-PIN the 7 & 8 connectors
-Then when you did this, connect the power cable
-Rockchip Batch Tool v1.7 should show you instead of an green device label a blue device label
-If is is blue you can simply flash yur stock rom again


To mo123:
We know that this device is not best (you show us here) but did you think you can told us how we can run your rom on our device? What did we wrong?
Stock rom is this here. (source: ENY2005) Or this older one.

Greetings by DuHaudegenDu

[no_spam_for_me]

...So it is the black arrow you should count to 7-8 pin (only fpr ENY EBK328 clone device)

BTW: not becuase of ENY EBK328 but because of the FORESEE nand/emmc chip and the little tiny white dot at the chip which indicates pin 1 ...

[trycatch]

Hi mo123,

i use your 1.2 rom in my device and its just great but
i also have a plan to run this device in CAR.

in old version or stok version, device was running with 2.1A power (from car)

but 1.2 version device is not booting in car
its ok with 3A power outlet at home.

i plan to get 3A power adapter for car, but it is posible to make a version non overclocked ?


thanks any way...

[mo123]

Hi mo123,

i use your 1.2 rom in my device and its just great but
i also have a plan to run this device in CAR.

in old version or stok version, device was running with 2.1A power (from car)

but 1.2 version device is not booting in car
its ok with 3A power outlet at home.

i plan to get 3A power adapter for car, but it is posible to make a version non overclocked ?


thanks any way...

The stock ROM and future ROM's are now 1.8Ghz by default, not overclocked.
You can try to use the kernel,resource.img file from the v1.0 ROM with the new ROM and see if it uses less power, will then run at 1.6Ghz for CPU.

[trycatch]

The stock ROM and future ROM's are now 1.8Ghz by default, not overclocked.
You can try to use the kernel,resource.img file from the v1.0 ROM with the new ROM and see if it uses less power, will then run at 1.6Ghz for CPU.

Ok, thanks for your reply. then, i think i will get 3A power supply...

[juliocunha]

hph-rk3288-android-ubuntu

hello. i wanto ask you if it is possible to do a rom like this (hph rk3288-android-ubuntu_20140924) but with your custom rom?

[mo123]

hello. i wanto ask you if it is possible to do a rom like this (hph rk3288-android-ubuntu_20140924) but with your custom rom?

Yes
Just made a new kernel, then have to dump Linux partition and combine everything into a new ROM.

[mo123]

Kodi Helix final will be released in less than 2 weeks, then a new SPMC will also be released.

Here is a new kernel to flash after unzipping
- NFS
- NTFS Support
- 30+ Cameras/Webcams Support added
- HDMI CEC working(also copy HDMI_CEC.kl file)
- Update the Blu-ray player library
- gpu:elevated GPU pll frequency 420
- rga/rga2 driver error handling fixed
- DDR : do not set the frequency when ddr initialization
- ethernet:gmac: fix the bug of connection failure with PHY because of wrong phy_addr
- mmc: workaround DDR mmc devices internal divider bug
PS: Only custom kernel with working HDMI IN.

http://www.mediafire.com/download/7wg8ztcpct86tz7/kernel.7z

Copy following file for HDMI CEC to system/usr/keylayout and to make D-Pad buttons work.

http://www.mediafire.com/download/w24x018dlawmtt3/hdmi_cec_key.kl

XBMC
Install 'XBMC Backup' from Program addons.
Setup backup directory to where you copied XBMC backup zip.
Restore backup.
Will take a while and need to restart XBMC/SPMC, say 'yes' to prompt that a different XBMC was used to make the backup.

http://www.mediafire.com/download/0t93aftwa43yny3/201412070546.zip

[mo123]

No one even tested new kernel

[m1pnk]

lol.... trouble is mo you do such a good job we are all just waiting for new rom with kodi/spmc