MP4 Nation Forums
Back to MP4 Nation - The MP4 Nation Blog - The Raz Special - Themes

i'll short out data pins of NAND chip for unbricking.

Allright I get it, when are you going to try?

well hopefully you wont need to go that far, shorting the pins -this is only needed in extreme cases, you will brick the player messing with the oppo firmware, that is for sure, but as they are nearly the same it will just render the player dead but recoverable with the update tool - BTW i have bricked this player already messing with the firmware and used the tool no problem to restore, so don't rip it apart just yet as you will also invalidate the warranty

_________________

• Phone: Samsung Galaxy Mini / Huawei G300 (just ordered)
• Fav App: Strava, IMDB, Jewels
• Portable Audio: currently none
• Headphones PC: Brainwavz HM5

-------------------------------------------------------------

• MP4nation webstore: Here

I don't really get why it would brick, the only differences between the Oppo and the Ramos are things not directly controlled by the rockchip chip (like the Yamaha amplfier the Oppo has). I injected the T11RK boot file into the Oppo firmware, if it bricks, will it be sure I can flash the original firmware back?

TBH cant be totally sure, all iknow is i have dont this before, you get a black screen and what appears to be a dead player (on older 27 series) the BASE.RKW is the main file here, all the code for running the individual hardware is compiled within there, and the main one is screen, different screen need different drivers in the BASE file, oppo and T11 will be different totally so odds are that you will basically end up either with a black screen player (use restore tool to restore) or maybe it wont even load at all, depends what failsafe routines rockchip have now included to prevent wrong firmware updates (i doubt they have)

it could totally break it or not, if this player were not for the whole family then i would do it now but i cant risk messing it up or im for the naughty step, normally i would give it a go for curiosity, so its up to others to have a go on this one

_________________

• Phone: Samsung Galaxy Mini / Huawei G300 (just ordered)
• Fav App: Strava, IMDB, Jewels
• Portable Audio: currently none
• Headphones PC: Brainwavz HM5

-------------------------------------------------------------

• MP4nation webstore: Here

I see, and BASE.RKW only takes care of the drivers or also the interface? because if it's only drivers, I could swap that one with the original firmware too.

it also maps all the folders, maps all the images etc etc, its the main controller for the whole firmware - it controls what the player does its the hearst of the player,all the other stuff in the firmware filoder are conpanion files needed for the file, it calls and references them from the BASE file,. all the players functionality resides within the BASE file

_________________

• Phone: Samsung Galaxy Mini / Huawei G300 (just ordered)
• Fav App: Strava, IMDB, Jewels
• Portable Audio: currently none
• Headphones PC: Brainwavz HM5

-------------------------------------------------------------

• MP4nation webstore: Here

So really there's no point in even trying the Oppo firmware, because altering the BASE file will render the device unbootable because it has some sort of md5 check built in.

What we need to do is alter the Oppo's BASE file so it contains the T11RK's hardware id's and drivers, and then find a way to edit the checksum....but I believe that's never been done before..

no, never been done before, but if you could then we will follow for sure -

_________________

• Phone: Samsung Galaxy Mini / Huawei G300 (just ordered)
• Fav App: Strava, IMDB, Jewels
• Portable Audio: currently none
• Headphones PC: Brainwavz HM5

-------------------------------------------------------------

• MP4nation webstore: Here

We probably can't do much as long as no Rockchip 28xx sdk is released, can't really do anything with the BASE file now.

I guess that with the T11RK's base file and the rest from the Oppo firmware we will just get the Ramos ui but messed up.