Forum switched to read-only as of 2020/06/01


Latest product reviews
ARCHOS 50 Diamond
ARCHOS GamePad2
ARCHOS
Smartphones
ARCHOS
TV Connect
ARCHOS 101 XS

A A A
Avatar

Please consider registering
Guest

Search

— Forum Scope —






— Match —





— Forum Options —





Minimum search word length is 3 characters - maximum search word length is 84 characters

Register Lost password?

ClockworkMod (CWM) Recovery easy install for RK3066 and RK3188 -- TWRP/CWM Flash-Tool and root for RK3288

 Please donate to support OMA and CrewRKTablets firmware work, thank you !

sp_Feed sp_TopicIcon
[ ROM ] Odys Iron OmniRom 4.4.4 custom root firmware (2014/05/30)
Avatar
Oma7144

Moderator

Firmware Guru
Forum Posts: 6315
Member Since:
2012/10/06
sp_UserOfflineSmall Offline

Thanks Received: 1386
316
2014/11/30 - 15:49
sp_Permalink sp_Print

Sorry, haven't noticed your post.

Here is a similar feedback: http://forum.xda-developers.com/showpost.php?p=56246334&postcount=2023

Two different orientations means two different kernel. Which kernel do you use?

- Oma -

Avatar
Loko222
Member
Forum Posts: 17
Member Since:
2014/08/06
sp_UserOfflineSmall Offline
317
2014/11/30 - 16:00
sp_Permalink sp_Print

Oma7144 said
Sorry, haven't noticed your post.

Here is a similar feedback: http://forum.xda-developers.com/showpost.php?p=56246334&postcount=2023

Two different orientations means two different kernel. Which kernel do you use?

- Oma -

The kernel for yuandao, namely: http://crewrktablets.arctablet.com/?wpfb_dl=1911

 

But seeing as my install was pretty messed up, had no recovery at first (was using stock), then forgot to change the kernel to the yuandao etc it might be a severely butchered up installation.

 

Could you tell me the correct order of flashing the rom?

Since now I have CW recovery, I connect it wipe IDB, change the default kernel with the yuandao one, press run.

Run factory reset, reboot tablet, hit no on both questions? (first is about recovery, 2nd is about su)

After it boots in, reboot to recovery and run format_NAND & model2 fix (which contains the 160dpi fix)

Avatar
Oma7144

Moderator

Firmware Guru
Forum Posts: 6315
Member Since:
2012/10/06
sp_UserOfflineSmall Offline

Thanks Received: 1386
318
2014/11/30 - 16:07
sp_Permalink sp_Print

Should be ok. The model fix you can install directly after the factory reset.

- Oma -

Avatar
Loko222
Member
Forum Posts: 17
Member Since:
2014/08/06
sp_UserOfflineSmall Offline
319
2014/11/30 - 22:06
sp_Permalink sp_Print

Oma7144 said
Should be ok. The model fix you can install directly after the factory reset.

- Oma -

I followed the steps (installed only the model fix 2, not 1 too)

"rom may flash stock recovery on boot, fix?" I chose no.

Problem persists.

the format_NAND said some permissions could not be set log:

AROMA Installer version 2.70RC2
  (c) 2013 by amarullz xda-developers

ROM Name    : AROMA Installer
ROM Version : 2.70RC2
ROM Author  : <support@amarullz.com>
Device      : Not Defined
Start at    : Sun Nov 30 20:44:01 2014

    installing samsung updater extensions
Starting the install process
  Setting up required tools...
 
Format internal sd card
    unmount of /emmc failed; no such volume
  (emmc is already unmounted)
    about to run program [/tmp/mkdosfs] with 3 args
    mkdosfs 3.0.9 (31 Jan 2010)
    unable to get drive geometry, using default 255/63
    about to run program [/tmp/dosfsck] with 3 args
    dosfsck 3.0.9, 31 Jan 2010, FAT32, LFN
    /dev/block/mtdblock10: 0 files, 1/254046 clusters
  Complete
 
Wipe data and cache
    unmount of /data failed; no such volume
  (data is already unmounted)
  wipe data...
    Creating filesystem with parameters:
    Size: 15156117504
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 8192
    Inode size: 256
    Journal blocks: 32768
    Label:
    Blocks: 3700224
    Block groups: 113
    Reserved block group size: 903
    Created filesystem with 11/925696 inodes and 99903/3700224 blocks
    warning: wipe_block_device: Discard failed
    about to run program [/sbin/sleep] with 2 args
  wipe cache...
    Creating filesystem with parameters:
    Size: 134217728
    Block size: 4096
    Blocks per group: 32768
    Inodes per group: 8192
    Inode size: 256
    Journal blocks: 1024
    Label:
    Blocks: 32768
    Block groups: 1
    Reserved block group size: 7
    Created filesystem with 11/8192 inodes and 1550/32768 blocks
    warning: wipe_block_device: Discard failed
    about to run program [/sbin/sleep] with 2 args
    unmount of /system failed; no such volume
  (system is already unmounted)
  tune system...
    about to run program [/tmp/tune2fs] with 4 args
    run_program: execv failed: No such file or directory
    run_program: child exited with status 1
    about to run program [/tmp/tune2fs] with 4 args
    run_program: execv failed: No such file or directory
    run_program: child exited with status 1
    about to run program [/tmp/e2fsck -p /dev/block/mtdblock8] with 1 args
    run_program: execv failed: No such file or directory
    run_program: child exited with status 1
    about to run program [/sbin/sleep] with 2 args
  cleaning...
    about to run program [/tmp/mount] with 2 args
    about to run program [/tmp/mount] with 2 args
    mount: mounting /dev/block/mtd/by-name/cache on /cache failed: Device or resource busy
    run_program: child exited with status 255
    about to run program [/tmp/mount] with 2 args
  Complete
 
    set_perm: chown of /system/bin/whtest.sh to 1000 1000 failed: No such file or directory
    set_perm: chmod of /system/bin/whtest.sh to 777 failed: No such file or directory
    script aborted: set_perm: some changes failed
  set_perm: some changes failed

Installer Error (Status 7)

End at : Sun Nov 30 20:45:43 2014


Avatar
Oma7144

Moderator

Firmware Guru
Forum Posts: 6315
Member Since:
2012/10/06
sp_UserOfflineSmall Offline

Thanks Received: 1386
320
2014/12/01 - 06:59
sp_Permalink sp_Print

Leave the format NAND fix out. Just do instead a factory reset in CWM.

- Oma -

Avatar
Loko222
Member
Forum Posts: 17
Member Since:
2014/08/06
sp_UserOfflineSmall Offline
321
2014/12/02 - 01:26
sp_Permalink sp_Print

Oma7144 said
Leave the format NAND fix out. Just do instead a factory reset in CWM.

- Oma -

Sadly no change. I get some lines about not being able to access or load some logs when it goes into recovery.

Maybe factory reset is not enough? Need to go deeper? That rotation bug, might be mainly cosmetic but it's pretty annoying.

If you want me to provide logs, try other stuff, I 'll be happy to do my part.

Avatar
Oma7144

Moderator

Firmware Guru
Forum Posts: 6315
Member Since:
2012/10/06
sp_UserOfflineSmall Offline

Thanks Received: 1386
322
2014/12/02 - 16:14
sp_Permalink sp_Print

Oh, that means it boots now into Android? Check out both model fixes as they are rotating the screen differently.

- Oma -

Avatar
Loko222
Member
Forum Posts: 17
Member Since:
2014/08/06
sp_UserOfflineSmall Offline
323
2014/12/02 - 16:48
sp_Permalink sp_Print

Oma7144 said
Oh, that means it boots now into Android? Check out both model fixes as they are rotating the screen differently.

- Oma -

It always did boot into android, except the first time I messed up the kernel.

Model fix 1 has the same problem and also is 180 degrees opposite, so no matter how I have it in my hands, the screen is set on the opposite side.

Avatar
Oma7144

Moderator

Firmware Guru
Forum Posts: 6315
Member Since:
2012/10/06
sp_UserOfflineSmall Offline

Thanks Received: 1386
324
2014/12/02 - 17:04
sp_Permalink sp_Print

Hm, can't imagine why this is the case. Can you pls check out if this build works for you?

- Oma -

Avatar
Loko222
Member
Forum Posts: 17
Member Since:
2014/08/06
sp_UserOfflineSmall Offline
325
2014/12/02 - 18:42
sp_Permalink sp_Print sp_EditHistory

Oma7144 said
Hm, can't imagine why this is the case. Can you pls check out if this build works for you?

- Oma -

Should there be a link there? :P

Would there be a point in removing pretty much everything from the tablet (without perma bricking it!) like os, kernel, recovery etc and doing everything correctly from the start? Or it's not possible a previous fuc* to still damage something (permissions, partitions) etc cause when I used the wrong kernel I tried a lot of random stuff to make it work.

 

edit: also I am pretty sure I never replaced the parameter file with the either the one linked in mandatory or the 8/32 version (since they are not for my model).

Avatar
Oma7144

Moderator

Firmware Guru
Forum Posts: 6315
Member Since:
2012/10/06
sp_UserOfflineSmall Offline

Thanks Received: 1386
326
2014/12/02 - 19:14
sp_Permalink sp_Print

You cannot brick an RK tab. If everything crashed on the NAND you can start it in mask-rom modus (1st stage bootloader) by shorting two NAND pins. By flashing a strange kernel you can, for sure, "damage" the hardware. In some cases the kernel will flash a firmware into i.e. the touch-controller. A strange firmware in the chip is the end of the road ...

The parameter file defines the partition layout on the NAND. EraseIDB will wipe this layout. If there is a missmatch the Flashtool will report download failed.

So, pls use the firmware packs as they are, just change the kernel (which is the interface to your specific hardware). Plus may be additional advises.

Can you pls test with build 1.4? Maybe we have some difficulties with the frameworks fakerotation.

- Oma -

Avatar
Loko222
Member
Forum Posts: 17
Member Since:
2014/08/06
sp_UserOfflineSmall Offline
327
2014/12/02 - 23:53
sp_Permalink sp_Print

Oma7144 said
You cannot brick an RK tab. If everything crashed on the NAND you can start it in mask-rom modus (1st stage bootloader) by shorting two NAND pins. By flashing a strange kernel you can, for sure, "damage" the hardware. In some cases the kernel will flash a firmware into i.e. the touch-controller. A strange firmware in the chip is the end of the road ...

The parameter file defines the partition layout on the NAND. EraseIDB will wipe this layout. If there is a missmatch the Flashtool will report download failed.

So, pls use the firmware packs as they are, just change the kernel (which is the interface to your specific hardware). Plus may be additional advises.

Can you pls test with build 1.4? Maybe we have some difficulties with the frameworks fakerotation.

- Oma -

Well 1.4 doesn't work at all :/ Moved the kernel to the image dir, lower format was fine, everything else was loaded / downloaded fine but even after 10 min no response from the tablet and it won't start.

Re grabbed the kernel and replaced it, did it again, nada.

Avatar
Oma7144

Moderator

Firmware Guru
Forum Posts: 6315
Member Since:
2012/10/06
sp_UserOfflineSmall Offline

Thanks Received: 1386
328
2014/12/03 - 17:50
sp_Permalink sp_Print

Lower format? Which Flashtool did you use?

- Oma -

Avatar
Loko222
Member
Forum Posts: 17
Member Since:
2014/08/06
sp_UserOfflineSmall Offline
329
2014/12/03 - 18:53
sp_Permalink sp_Print

Oma7144 said
Lower format? Which Flashtool did you use?

- Oma -

Grabbed for 1.4 : Oma_RK32_Pipo_P4_KK_4.4.4_v1.4.7z

In "2. RKAndroidTool" used AndroidTool.exe

Avatar
Oma7144

Moderator

Firmware Guru
Forum Posts: 6315
Member Since:
2012/10/06
sp_UserOfflineSmall Offline

Thanks Received: 1386
330
2014/12/03 - 18:56
sp_Permalink sp_Print

No, Omni build v1.4 is here: http://crewrktablets.arctablet.com/?p=3555

- Oma -

Forum Timezone: Europe/Paris

Most Users Ever Online: 749

Currently Online:
82 Guest(s)

Currently Browsing this Page:
1 Guest(s)


Devices in use: Desktop (72), Phone (10)

Top Posters:

finless: 604

DarthJabba: 551

maikal: 394

mussonero1: 350

alex: 252

damo: 243

DanielVd: 237

Mark06: 222

Newest Members:

swan12

fansosagelos

Snowm

andrewbest

heftpflaster

ruta6

Forum Stats:

Groups: 10

Forums: 185

Topics: 6037

Posts: 60500

 

Member Stats:

Guest Posters: 43

Members: 262194

Moderators: 5

Admins: 1

Administrators: admin

Moderators: globula_neagra, exelletor, JochenKauz, Oma7144, cracktech


CrewRKTablets moderators: JochenKauz and Astralix