I just reflashed to asper cfw. Everything worked well and the message OK was written in the tool. Then i rebootet my console since then im stuck.
Hekel,
I know this is an old post however I'm very curious because I know a bit about the RockChip and it does not sound like all 15 partitions have been restored to this device.
RockChips are very hard to break.
There is nothing wrong or dangerous with using Lower Format and re-flashing ALL of those partitions proper.
If the devices is restarted after a Lower Level format is performed it will still boot into the Loader.
As long as the Loader is there, the NAND will recover the Data in those pre-defined Partitions that have been backed up in advance.
No reason to use MASK Device to replace the Loader because at that point the entire ROM image must be replaced and while that is possible it cannot be done with the specific RK3036 loader that was used build the original ROM image at the factory. The physical NAND can break down or be damaged and the software Loader corrupted and or lost but that is extreme.
I'm serious when I say if you include ALL 15 you'll have a very good chance at recovering any RockChip Device.
No Video and Loader Device Only. Fixed.
Not only that the method will absolutely convert an OBB device to a non-OBB device if you use the repo on mdfbrew.
The reverse can be done just as easily with a complete copy of OBB device images.
I have done this several times and if the NAND was going to fail it would in different ways.
If the Loader Device Loader is there and you have all 15 partitions then your chance of recovery is very high.
Follow the directions on mdfbrew and add the last 3 partitions line by line by right clicking.
Add all Partition lines to the AndroidTool and Flash the Uboot.img last.
0x00006000 baseparamer Output\baseparamer.img
0x00006800 resource Output\resource.img
0x00002000 uboot Output\uboot.img
No Video and Stuck in Loader Device mode. Fixed.
To be clear I could not restore the console fully using the method as described on mdfbrew but I plan to gracefully update it as wiki's allow.
I also learned that the NAND can be put into MASKLOADER mode by shorting pins 7,8 and 9 and then applying power to the console.
This will allow a new loader+bin for a newly signed ROM but that is way down the road.
The NAND changes the way it is mounted in Windows between the two img sets.
MTP Device for Non-OBB and RK2039 NAND for OBB devices.
If you want to know how to use ADT v2.39 without using 2 different consoles please let me know.
Again immediately after flashing UBoot.img the console will immediately start ADB Mode.
See an image of the fully loaded ADT recovery console.
Remove the spaces to view the image.
https://image.ibb.co/cmBzzz/recovery.png
@
Xdqwerty:
