Announcement

**Deadphyre** · 02 January 2014, 05:38

When you go to install CM11 are you destroying all the partitions, save the recover partition and making them over from scratch?

I've been looking at how to create a custom ROM using stock ROM and CM but I'm not sure which kitchen to use for cooking it. Thankfully we are able to have a working TWRP as most tutorials have them as something you need. I haven't been able to get far though as I'm trying to figure out how to access all the TWRP backup stuff...and chase after RL kids at the same time.

If there is anything I can do to help let me know.

**AManofFewWords** · 02 January 2014, 05:50

Well I installed it using PhoenixSuit, which I'm afraid is likely the reason. I've searched on Google anywhere, this doesn't seem like a very spread-out problem.

TWRP 2.6.3.0 doesn't work for KitKat sadly, we need a CWM 6.0.4.3+.

Addition: I'm also using stock kernel, which could be a reason.

**Deadphyre** · 02 January 2014, 06:17

Originally posted by AManofFewWords View Post

Well I installed it using PhoenixSuit, which I'm afraid is likely the reason. I've searched on Google anywhere, this doesn't seem like a very spread-out problem.

TWRP 2.6.3.0 doesn't work for KitKat sadly, we need a CWM 6.0.4.3+.

Addition: I'm also using stock kernel, which could be a reason.

Yeah, when I tested out the ROM I was installing it through TWRP and then it would do a repeated boot loop and I have yet to find out which buttons I need to push to get into recovery. This device is pretty different compared to what I'm used to. I'm used to putting CWM on an external SD card and doing custom partitions and installing CWM. Then installing the ROM through that.

From what I've read the kernel from CM may need to be modified to work with our A/S8's. I would like to get CWM to work on the Polaroid but most of what I've found is that it has issues with touch screen. Which shouldn't be a problem since there is a physical volume rocker to use.

**AManofFewWords** · 02 January 2014, 06:28

Yeah, CWM doesn't need to be touch screen, I'm pretty sure we'll go better without it.

Hopefully it's just PhoenixSuit's flashing that's being the problem. If not, I'm gonna compile a new kernel.

**Deadphyre** · 02 January 2014, 06:38

Originally posted by AManofFewWords View Post

Yeah, CWM doesn't need to be touch screen, I'm pretty sure we'll go better without it.

Hopefully it's just PhoenixSuit's flashing that's being the problem. If not, I'm gonna compile a new kernel.

Best bet would be to compile a new kernel to install without PhoenixSuit and through CWM. Probably end up with less issues as far installing goes. I've noticed that when you install the stock ROM or the modded stock ROM with PhoenixSuit, it wipes everything, all partitions and all data and creates all the partitions based on what the img has. If we need to go by the way of PS then we'll need to have all partitions set up, including the recovery partition, data, system, cache etc etc. It's the only thing I can think of right now.

**AManofFewWords** · 02 January 2014, 06:58

If you could upload the CWM img you have right now, that would be fine.

**Deadphyre** · 02 January 2014, 23:16

Question maybe you know the answer to. I'm doing a dump of the modded stock ROM (guess's modded rom) and I have the misc, boot, recovery and system.img's but not sure which partition is the kernel partition. I think the backup partition is databk but not really clear on that one. Do you know?

**AManofFewWords** · 02 January 2014, 23:23

Kernel has no partition, kernel is built inside the boot partition, along with ramdisk.

**Deadphyre** · 02 January 2014, 23:26

interesting, so I'm working on dumping the ROM and most of the directions and tuts I've found which talk about doing dd if="blah blah" mention doing an boot.img and a kernel.img but nothing about the kernel being inside the boot.

This is what I'm going by http://www.freaktab.com/showthread.p...LASHABLE-IMAGE

**AManofFewWords** · 02 January 2014, 23:53

That is a Rockchip 3188 device. This is an Allwinner A20 device. They have different partition layouts, the kernel is found inside the boot.img when it is unpacked.

**elektrik** · 03 January 2014, 00:49

Originally posted by AManofFewWords View Post

That is a Rockchip 3188 device. This is an Allwinner A20 device. They have different partition layouts, the kernel is found inside the boot.img when it is unpacked.

Specifically called the zimage file btw.

**AManofFewWords** · 03 January 2014, 01:32

I think it's a uImage.... but the difference between a zImage and a uImage is that the uImage uses a modified header for u-boot.

**Deadphyre** · 03 January 2014, 01:44

Alrighty, makes sense. So then what does [private] located at /dev/block/nanj have? I also see [UDISK] at /dev/block/nandk and another [env] at /dev/block/nandb. I'm just not used to seeing these label as such. Are they needed when doing a dump or just boot, data, misc, recovery and system?

**elektrik** · 03 January 2014, 02:02

Re: CM11 for A/S8 (in-progress)

Re:uimage-

Possible. I'm going off info for the a10

Sent from my SM-N900P using Tapatalk

Announcement

Announcement

CM11 for A/S8 (in-progress)

CM11 for A/S8 (in-progress)

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

What's Going On