[Discontinued]

Search This thread
By:
Advanced…
W

Wootever

Senior Member
Jun 27, 2012
1,089
2,818
Sure, but be warned i don't own this device so this build is experimental (for now).
 

Attachments

  • a510_twrp-2.6.img
    5.5 MB · Views: 108
Last edited:
W

Wootever

Senior Member
Jun 27, 2012
1,089
2,818
The recovery is actually build by myself. The build process itself is not rather complicated, it only needs some small configuration for proper working.
Code used for A700 version:
Code: 
DEVICE_RESOLUTION := 1920x1200
RECOVERY_SDCARD_ON_DATA := true
TW_INTERNAL_STORAGE_PATH := "/data/media"
TW_INTERNAL_STORAGE_MOUNT_POINT := "data"
TW_EXTERNAL_STORAGE_PATH := "/external_sd"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "external_sd"

For the A510 i used Shreps repo (https://github.com/Shr3ps/device_acer_a510) and created a modified cm.mk configuration file:

Code: 
DEVICE_RESOLUTION := 1280x800
RECOVERY_SDCARD_ON_DATA := true
TW_INTERNAL_STORAGE_PATH := "/data/media"
TW_INTERNAL_STORAGE_MOUNT_POINT := "data"
TW_EXTERNAL_STORAGE_PATH := "/external_sd"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "external_sd"

Code: 
## Specify phone tech before including full_phone
$(call inherit-product, vendor/cm/config/gsm.mk)

# Release name
PRODUCT_RELEASE_NAME := A510

# Boot Animation
TARGET_SCREEN_WIDTH := 1280
TARGET_SCREEN_HEIGHT := 800

# Inherit some common CM stuff.
$(call inherit-product, vendor/cm/config/common_full_tablet_wifionly.mk)

# Inherit device configuration
$(call inherit-product, device/acer/a510/full_a510.mk)

## Device identifier. This must come after all inclusions
PRODUCT_DEVICE := a510
PRODUCT_NAME := cm_a510
PRODUCT_BRAND := Acer
PRODUCT_MODEL := A510
PRODUCT_MANUFACTURER := Acer

PRODUCT_BUILD_PROP_OVERRIDES += \
    PRODUCT_NAME=a510_pa_cus1 \
    TARGET_DEVICE=picasso_m \
    BUILD_FINGERPRINT="acer/a510_pa_cus1/picasso_m:4.1.2/JZO54K/1354108731:user/release-keys" \
    PRIVATE_BUILD_DESC="a510_pa_cus1-user 4.1.2 JZ054K 1354108731 release-keys"
 
Moscow Desire

Moscow Desire

Retired Senior Moderator
Mar 31, 2011
7,653
6,880
Somewhere in a Deep Cave on the Troll Kings Throne
Wootever said:
The recovery is actually build by myself. The build process itself is not rather complicated, it only needs some small configuration for proper working.
Code used for A700 version:
Code: 
DEVICE_RESOLUTION := 1920x1200
RECOVERY_SDCARD_ON_DATA := true
TW_INTERNAL_STORAGE_PATH := "/data/media"
TW_INTERNAL_STORAGE_MOUNT_POINT := "data"
TW_EXTERNAL_STORAGE_PATH := "/external_sd"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "external_sd"

For the A510 i used Shreps repo (https://github.com/Shr3ps/device_acer_a510) and created a modified cm.mk configuration file:

Code: 
DEVICE_RESOLUTION := 1280x800
RECOVERY_SDCARD_ON_DATA := true
TW_INTERNAL_STORAGE_PATH := "/data/media"
TW_INTERNAL_STORAGE_MOUNT_POINT := "data"
TW_EXTERNAL_STORAGE_PATH := "/external_sd"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "external_sd"

Code: 
## Specify phone tech before including full_phone
$(call inherit-product, vendor/cm/config/gsm.mk)

# Release name
PRODUCT_RELEASE_NAME := A510

# Boot Animation
TARGET_SCREEN_WIDTH := 1280
TARGET_SCREEN_HEIGHT := 800

# Inherit some common CM stuff.
$(call inherit-product, vendor/cm/config/common_full_tablet_wifionly.mk)

# Inherit device configuration
$(call inherit-product, device/acer/a510/full_a510.mk)

## Device identifier. This must come after all inclusions
PRODUCT_DEVICE := a510
PRODUCT_NAME := cm_a510
PRODUCT_BRAND := Acer
PRODUCT_MODEL := A510
PRODUCT_MANUFACTURER := Acer

PRODUCT_BUILD_PROP_OVERRIDES += \
    PRODUCT_NAME=a510_pa_cus1 \
    TARGET_DEVICE=picasso_m \
    BUILD_FINGERPRINT="acer/a510_pa_cus1/picasso_m:4.1.2/JZO54K/1354108731:user/release-keys" \
    PRIVATE_BUILD_DESC="a510_pa_cus1-user 4.1.2 JZ054K 1354108731 release-keys"
Click to expand...
Click to collapse

Thanks Mate for clearing it up ;)

I guess I will try this out.

OP, sent you a PM.

MD
 
Last edited:
  • Like
Reactions: Wootever
W

Wootever

Senior Member
Jun 27, 2012
1,089
2,818
Elibl said:
is it safe regarding MMC_CAP_ERASE function? EMMC wipe?

all the best
Click to expand...
Click to collapse

This recovery is build with the same kernel as the a700 version:
https://github.com/CyanogenMod/android_kernel_acer_t30

pawitp has already disabled MMC_CAP_ERASE to prevent a hard brick:
https://github.com/CyanogenMod/andr...mmit/c0e6ee0b15cb48395384851c931b7baf4b8dde00

There is no guarantee that you won't get any problems, but since the a510 is very similar to the a700 it should not brick your device.


Edit:
content of BoardConfigCommon.mk:
# Samsung EMMC brick bug
# Already disabled in kernel, but disable again for safety
BOARD_SUPPRESS_EMMC_WIPE := true
Click to expand...
Click to collapse

respective commit:
https://github.com/CyanogenMod/android_system_extras/commit/60c5383fd093826fb3f95f3dda4f313aa54f4f69
 
Last edited:
  • Like
Reactions: Elibl
E

Elibl

Senior Member
Dec 20, 2011
686
448
Wootever said:
This recovery is build with the same kernel as the a700 version:
https://github.com/CyanogenMod/android_kernel_acer_t30

pawitp has already disabled MMC_CAP_ERASE to prevent a hard brick:
https://github.com/CyanogenMod/andr...mmit/c0e6ee0b15cb48395384851c931b7baf4b8dde00

There is no guarantee that you won't get any problems, but since the a510 is very similar to the a700 it should not brick your device.


Edit:
content of BoardConfigCommon.mk:


respective commit:
https://github.com/CyanogenMod/android_system_extras/commit/60c5383fd093826fb3f95f3dda4f313aa54f4f69
Click to expand...
Click to collapse

Thanks really nice review going to test it tomorrow;)

All the best

Gesendet von meinem NexusHD2 mit Tapatalk 4 Beta
 
N

nex86

Senior Member
Nov 9, 2010
632
48
whats the problem with external_sd?
It worked fine in the 2.5 build by pawitp.

Code: 
TW_EXTERNAL_STORAGE_PATH := "/external_sd"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "external_sd"

shouldn't it be /mnt/external_sd ?
 
Moscow Desire

Moscow Desire

Retired Senior Moderator
Mar 31, 2011
7,653
6,880
Somewhere in a Deep Cave on the Troll Kings Throne
nex86 said:
whats the problem with external_sd?
It worked fine in the 2.5 build by pawitp.

Code: 
TW_EXTERNAL_STORAGE_PATH := "/external_sd"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "external_sd"

shouldn't it be /mnt/external_sd ?
Click to expand...
Click to collapse

I think OP has updated the recovery according to the original post to address the issue.

The Op should respond a little quicker to issues ;)

MD
 
  • Like
Reactions: Sterist
Moscow Desire

Moscow Desire

Retired Senior Moderator
Mar 31, 2011
7,653
6,880
Somewhere in a Deep Cave on the Troll Kings Throne
Hate to say it mate. But on a 701 it's unable to mount basically about anything (when doing a backup). And the 700 uses the same mounting points. So not sure what's going on.

Did you make a mistake and post a wrong one in the latest download link? Because... Wow!

Also, is this for JB? Because it acts like you used an ICS kernel. That would explain all the mount point errors as I remember trying to use a JB based CWM on an ICS build.

Basically, it cannot mount most of the partitions, and get a TWRP fail.
 
Last edited:
  • Like
Reactions: Sterist
W

Wootever

Senior Member
Jun 27, 2012
1,089
2,818
Sorry for late response, i tested the recovery attached on my first post again and can't reproduce any of the errors you are reporting.
The recovery is based on recent kernel_acer_t30 and device_acer_a700 repositories both provided by cyanogenmod.

If you could provide a log (located on /tmp/recovery.log) i could take a closer look.
 
dadecamp

dadecamp

Senior Member
Nov 19, 2011
184
21
casa grande
I just want everyone to know that this recovery is the only one that recognizes my 64gb MicroSDXC . CWM 6.0.2.3 and 6.0.3.1 don't.

Sent from my A700 using Tapatalk 4
 
  • Like
Reactions: ExtremeRyno
You must log in or register to reply here.

Similar threads

Shreps
[ROM][4.4.4] CyanogenMod 11 for Acer A510/A511 (with UMTS/3G) [UNOFFICIAL]
Replies
562
Views
160K
M
mnom
N
[A510][RECOVERY][2012-12-15] CWM-based Recovery 6.0.1.9 (JB compatible)
Replies
289
Views
154K
N
nchc
A
Unlock bootloader
Replies
68
Views
101K
A
alan0923
Z
Full root for A700 and A701 tablets
Replies
176
Views
106K
B
bobnweaving
Shreps
[ROM][5.1.1] CyanogenMod 12.1 for Acer A510[UNOFFICIAL]
Replies
309
Views
111K
R
r3d4

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 6
    W
    Wootever
    [Discontinued]
    View
    3
    E
    Elibl
    TWRP 2.7.0.0

    here you can test
    View
    1
    Moscow Desire
    Moscow Desire
    Wootever said:
    The recovery is actually build by myself. The build process itself is not rather complicated, it only needs some small configuration for proper working.
    Code used for A700 version:
    Code: 
    DEVICE_RESOLUTION := 1920x1200
RECOVERY_SDCARD_ON_DATA := true
TW_INTERNAL_STORAGE_PATH := "/data/media"
TW_INTERNAL_STORAGE_MOUNT_POINT := "data"
TW_EXTERNAL_STORAGE_PATH := "/external_sd"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "external_sd"

    For the A510 i used Shreps repo (https://github.com/Shr3ps/device_acer_a510) and created a modified cm.mk configuration file:

    Code: 
    DEVICE_RESOLUTION := 1280x800
RECOVERY_SDCARD_ON_DATA := true
TW_INTERNAL_STORAGE_PATH := "/data/media"
TW_INTERNAL_STORAGE_MOUNT_POINT := "data"
TW_EXTERNAL_STORAGE_PATH := "/external_sd"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "external_sd"

    Code: 
    ## Specify phone tech before including full_phone
$(call inherit-product, vendor/cm/config/gsm.mk)

# Release name
PRODUCT_RELEASE_NAME := A510

# Boot Animation
TARGET_SCREEN_WIDTH := 1280
TARGET_SCREEN_HEIGHT := 800

# Inherit some common CM stuff.
$(call inherit-product, vendor/cm/config/common_full_tablet_wifionly.mk)

# Inherit device configuration
$(call inherit-product, device/acer/a510/full_a510.mk)

## Device identifier. This must come after all inclusions
PRODUCT_DEVICE := a510
PRODUCT_NAME := cm_a510
PRODUCT_BRAND := Acer
PRODUCT_MODEL := A510
PRODUCT_MANUFACTURER := Acer

PRODUCT_BUILD_PROP_OVERRIDES += \
    PRODUCT_NAME=a510_pa_cus1 \
    TARGET_DEVICE=picasso_m \
    BUILD_FINGERPRINT="acer/a510_pa_cus1/picasso_m:4.1.2/JZO54K/1354108731:user/release-keys" \
    PRIVATE_BUILD_DESC="a510_pa_cus1-user 4.1.2 JZ054K 1354108731 release-keys"
    Click to expand...
    Click to collapse

    Thanks Mate for clearing it up ;)

    I guess I will try this out.

    OP, sent you a PM.

    MD
    View
    1
    W
    Wootever
    Elibl said:
    is it safe regarding MMC_CAP_ERASE function? EMMC wipe?

    all the best
    Click to expand...
    Click to collapse

    This recovery is build with the same kernel as the a700 version:
    https://github.com/CyanogenMod/android_kernel_acer_t30

    pawitp has already disabled MMC_CAP_ERASE to prevent a hard brick:
    https://github.com/CyanogenMod/andr...mmit/c0e6ee0b15cb48395384851c931b7baf4b8dde00

    There is no guarantee that you won't get any problems, but since the a510 is very similar to the a700 it should not brick your device.


    Edit:
    content of BoardConfigCommon.mk:
    # Samsung EMMC brick bug
    # Already disabled in kernel, but disable again for safety
    BOARD_SUPPRESS_EMMC_WIPE := true
    Click to expand...
    Click to collapse

    respective commit:
    https://github.com/CyanogenMod/android_system_extras/commit/60c5383fd093826fb3f95f3dda4f313aa54f4f69
    View
    1
    Moscow Desire
    Moscow Desire
    nex86 said:
    whats the problem with external_sd?
    It worked fine in the 2.5 build by pawitp.

    Code: 
    TW_EXTERNAL_STORAGE_PATH := "/external_sd"
TW_EXTERNAL_STORAGE_MOUNT_POINT := "external_sd"

    shouldn't it be /mnt/external_sd ?
    Click to expand...
    Click to collapse

    I think OP has updated the recovery according to the original post to address the issue.

    The Op should respond a little quicker to issues ;)

    MD
    View

New posts