[sas_sas]

darkrickpr, on 13 October 2012 - 12:33 PM, said:

try again flashing the clock but before flashing click the ERASE NAND (IDB)

It does not erase IDB. It fails.
But this time, it does not start flashing after erasing IDB procedure even fails..
(Of course tablet is detected)

[darkrickpr]

sas_sas, on 13 October 2012 - 01:21 PM, said:

It does not erase IDB. It fails.
But this time, it does not start flashing after erasing IDB procedure even fails..
(Of course tablet is detected)

damn ... i dont know what else..... but come to my mind i was thinking if theres nothing more to loose why dont you try flashing Pipo max m11 4.1 firmware with the original RKBATCHTOOL clicking restore so that it reformat everything i have seen this firmware is very compatible with many tablet lets hope also work with ROCKX i have done this and it worked with my CUBE u20gt and load but happend to me no touchscreen but in my case is because cube hacent done a kernel for my tablet compatible with Jellybean then in your case i found out the kernel is included in the boot.img so if pipo firmload fine try reflashing just the boot.img from your ROCK x

[darkrickpr]

hhaahahah still don't loose fate jejeeje i got another idea if the pipo firm doesnt work. i will try and pack again the 4.0.4 dump you link me to and make a updade.img that could flash with original RKBATCHTOOL if no will do it with the modified Rk Tool i will post soon this let hope again

[Beurk]

darkrickpr, on 13 October 2012 - 08:49 AM, said:

hey @sas_sas

i found out that the ROCK X 4.1 firmware image doesn't have kernel.img inside when extract with wendal thats maybe the problem where it doesnt boot sometime and no touchscreen i dont think is hardware. anyway i have made the mod just with out system.img

I opened the 4.0.4 firmware with Linux kitchen tools and there's no kernel.img either.

Quote

unpacking update.img
================================================================================
FIRMWARE_VER:4.0.4
MACHINE_MODEL:ROCK X
MACHINE_ID:007
MANUFACTURER:RK30SDK

unpacking 10 files
-------------------------------------------------------------------------------
00000800-00000fff package-file:package-file 564 bytes
00001000-0002cfff bootloader:RK30xxLoader(L)_V1.10.bin 179498 bytes
0002d000-0002d7ff parameter:parameter:0x2000@0x0 603 bytes
0002d800-000397ff misc:Image/misc.img:0x2000@0x2000 49152 bytes
00039800-007f17ff boot:Image/boot.img:0x8000@0x8000 8093696 bytes
007f1800-011457ff recovery:Image/recovery.img:0x8000@0x10000 9781248 bytes
01145800-148ccfff system:Image/system.img:0xa0000@0x31a000 326662144 bytes
00000000-ffffffff backup:RESERVED:0xc0000@0x18000 0 bytes
148cd000-148cd7ff update-script:update-script 933 bytes
148cd800-148cdfff recover-script:recover-script 266 bytes
-------------------------------------------------------------------------------
================================================================================

[darkrickpr]

@Beurk i was told the firmware has the kernel in the same boot.img is a possibility i think?

@sas_sas

here it is the 4.0.4 firmware a made from the dump it should flash as the normal 4.1 that work for you remember to flash it with restore button so that is erase the IDB
Since i big file i compress it into two parts .7z and one part .zip

Part1
Part2

[Beurk]

darkrickpr, on 13 October 2012 - 05:07 PM, said:

@Beurk i was told the firmware has the kernel in the same boot.img is a possibility i think?

According to this page, sure it is. Before I found it, I checked the boot.img file, and it was a data file, not a disk image, system.img is an ext3 disk image.

Quote

boot.img: data
Image/system.img: Linux rev 1.0 ext3 filesystem data, UUID=3dbb4ebd-ee52-45b9-9d5b-288eb1d0b110, volume name "system"

Using the perl script, I could extract the kernel image and the ramdisk image.

Quote

Page size: 16384 (0x00004000)
Kernel size: 7225380 (0x006e4024)
Ramdisk size: 829635 (0x000ca8c3)
Second size: 0 (0x00000000)
Board name:
Command line:
Writing boot.img-kernel ... complete.
Writing boot.img-ramdisk.gz ... complete.

Tell me if you're interested in these files, cause I'm an average Linux user and a total noob with Android.

[darkrickpr]

Beurk, on 13 October 2012 - 07:44 PM, said:

According to this page, sure it is. Before I found it, I checked the boot.img file, and it was a data file, not a disk image, system.img is an ext3 disk image.



Using the perl script, I could extract the kernel image and the ramdisk image.


Tell me if you're interested in these files, cause I'm an average Linux user and a total noob with Android.

could you extract the kernel from this boot.img this is the one from RockX 4.0.4 dump some did. do you know if theres a motive to rock x developer to merge the boot.img and kernel in the same image? maybe to make it dificul to rom cooker. does it work the same separetd than merge.

by the way how can i install linux kichen could i do it on a virtual machine? any page how to

[Beurk]

The boot.img from dump is bigger (16MB) compared to the one downloaded from Hyundai site (7.7MB), but once extracted they look the same, I compared them byte by byte with cmp command and there's no difference.

Kernel from boot.img from Hyundai
Ramdisk from boot.img Hyundai

Kernel from boot.img dump
Ramdisk from boot.img dump

You can get the kitchen tools from here, looks like the bash scripts are made for Ubuntu, if needed, the sources are some posts below. You can try them in a virtual machine (Virtual Box, VMware) with Ubuntu install.

This post has been edited by Beurk: 14 October 2012 - 10:32 AM

[darkrickpr]

Thanks for the kichen

What about the kernel.img is the same on both boot from dump ics 4.0.4 and 4.1 jb can you extract make individual boot.img and kerne.img from the dump boot file i post

Sent from my HTC VIVID using Tapatalk 2

This post has been edited by darkrickpr: 14 October 2012 - 09:08 AM

[darkrickpr]

Anothing there no way to modifief a kernel with out source code right?
Got a cube u20gt thats boot fine with pipomax m1 kernel & boot.img but no touscreen if i just reflash the cube original boot and kernel made for ics 4.0 freeze with jellybean system from pipo firm 4.1. Any idea you may think

Sent from my HTC VIVID using Tapatalk 2

This post has been edited by darkrickpr: 14 October 2012 - 09:24 AM

[Beurk]

Don't know how it works with Android, you should have the source and a config file for compiling exactly the same kernel I guess.
The links I posted above are kernels and ramdisks extracted from boot.img for 4.0.4, kernel and ramdisk extracted from Hyundai 4.1 image :

Kernel from boot.img 4.1 Hyundai

Ramdisk from boot.img 4.1 Hyundai

[sas_sas]

darkrickpr, on 13 October 2012 - 05:07 PM, said:

@Beurk i was told the firmware has the kernel in the same boot.img is a possibility i think?

@sas_sas

here it is the 4.0.4 firmware a made from the dump it should flash as the normal 4.1 that work for you remember to flash it with restore button so that is erase the IDB
Since i big file i compress it into two parts .7z and one part .zip

Part1
Part2

I flashed first your v4.0.4 img file you gave here..
Applied restore and It flashed all stages except the final I think FW flashing. When it comes to FW flashing it failed. Of course the tablet not booted not opened not logo appeared. full black screen.

But the worst this time the tablet is fully bricked.. Because the tablet can not be connected to the computer any more.
The green or blue (I saw first time it was blue color when I connect in flash mode before flashing your img) flash mode connection confirmation color not turning on and not possible to flash any other FW image file..
I think this is the end of touch feature recovery efforts.

Thank you for all your support, seriously.. I do not blame you at all. You did your best to help to me.. I was aware that anything any time can cause full brick..
Good luck to you for future efforts..

[darkrickpr]

The rk chipset can not be fullbrick try pressing and holdin the power to make sure it is off even check darkroom backligt is off and no usb connected the prees and hold -volume or +volume and reconnect the usb it should get to bootloader en way would u sell it? Eb@ y

Sent from my HTC VIVID using Tapatalk 2

[sas_sas]

darkrickpr, on 14 October 2012 - 02:34 PM, said:

The rk chipset can not be fullbrick try pressing and holdin the power to make sure it is off even check darkroom backligt is off and no usb connected the prees and hold -volume or +volume and reconnect the usb it should get to bootloader en way would u sell it? Eb@ y

Sent from my HTC VIVID using Tapatalk 2

yes I was thinking so. Not brick-able..
I have tried all possible button combinations tens of times..
As if turning down and turning on as if flash mode etc..
Power must be okay, charged again with different adapters....

I have also tried all ADB interface and Android USB drivers to reinstall..
In all cases Windows never notices The tablet as an hardware..
Even if all drivers are installed The tablet is none.. NOT any device..

I do not understand but You may better interpret what it means ..

Sell Eb@ y ? how? who can buy such thing ?
As Spare part ?
I never cheat anyone..

[sas_sas]

Brought back to the flash able state.
How;
Open up back case, battery connection cable disconnected and connected.

Despite flashing/ restoring with the only working image It ended up failure then no boot up and bricked again.

Bringing back to Flash able state is again possible..
But What FW img can correct the whole situation I do not know...

This post has been edited by sas_sas: 17 October 2012 - 05:00 AM

[Mauricio R.]

Didn't you have a working rom in the tablet? No touch but with the tablet working?

[sas_sas]

Mauricio R., on 17 October 2012 - 01:32 PM, said:

Didn't you have a working rom in the tablet? No touch but with the tablet working?

Yes there was only one which was the final issued stock FW v4.1..

But this time even this can not be flashed with success.
If it can be flashed with success maybe it will be alright..
the failure result is probably coming out due to starting with blue color not green of RKbatch tool connected devices box..
Turning to green but how ?


Just Hyundai published a new FW..
I will try soon..

This post has been edited by sas_sas: 18 October 2012 - 04:17 AM

[darkrickpr]

Have you try on the rkbatchtool there is a button named switch clicking it should reboot the tablet and get you to green color mode.

Sent from my HTC VIVID using Tapatalk 2

[sas_sas]

sas_sas, on 18 October 2012 - 03:52 AM, said:

Just Hyundai published a new FW..
I will try soon..

@ darkrickpr

I fully unbricked.
Return to the previous state with the final FW of factory.
Meaning tablet works but the same no touch...