android 5.1 dump files from chuwi dualboot 03 march serial

android 5.1 dump files from chuwi dualboot 03 march serial

TechTablets › Forums › Chuwi Forums › Chuwi Hi12 Forum › android 5.1 dump files from chuwi dualboot 03 march serial

Viewing 15 posts - 1 through 15 (of 16 total)
  • Author
    Posts
  • #33414
    spzjulien supercowz
    Participant
    • Posts: 172

    one french guy did receive is dualboot Hi12,  so i ask him if we can dump android boot.img system.ing ect.. he say yes so
    since chuwi dont provide any file i can be usefull for someone ..
    i will see with him if i can dump his bios with Hardware but i doubt it would work with win10 jan 01 serial … anyway here is the dump files i made

    https://mega.nz/#!PJhXnTya!fWSW7J7ewyMgCc156bqnNbAdZoJ2clBnQzovh5AwbvQ

    #33416
    winston smith
    Participant
    • Posts: 115

    How did he get this dump file ? With the the help of which software ?

    #33417
    winston smith
    Participant
    • Posts: 115

    If i can get trustfull dumpfile (that means coming not from jupiter’ass), i’m able to root and then will reconsider buy it.

    #33420
    spzjulien supercowz
    Participant
    • Posts: 172

    i dumped Myself by adb shell command .. they are good  🙂  (via teamviewer, with the Dualboot owner guy..)
    system.raw was recompress to system.img under my ubutnu
    try them u will see they are valid, do you want see build.prop to believe me ? 🙂

    #33421
    spzjulien supercowz
    Participant
    • Posts: 172

    build.prop
    # begin build properties
    # autogenerated by buildinfo.sh
    ro.build.id=LMY47I
    ro.build.display.id=cht_cr_mrd_w-userdebug 5.1 LMY47I eng.softteam.20160317.111935 release-keys
    ro.build.version.incremental=eng.softteam.20160317.111935
    ro.build.version.sdk=22
    ro.build.version.codename=REL
    ro.build.version.all_codenames=REL
    ro.build.version.release=5.1
    ro.build.version.security_patch=2015-11-01
    ro.build.version.base_os=
    ro.build.date=Thu Mar 17 11:21:20 CST 2016
    ro.build.date.utc=1458184880
    ro.build.type=userdebug
    ro.build.user=softteam
    ro.build.host=pdd-build
    ro.build.tags=release-keys
    ro.build.flavor=cht_cr_mrd_w-userdebug
    ro.product.model=CW-Hi12
    ro.product.brand=CW-Hi12
    ro.product.name=cht_cr_mrd_w
    ro.product.device=CW-Hi12
    ro.product.board=CW-Hi12
    # ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
    # use ro.product.cpu.abilist instead.
    ro.product.cpu.abi=x86
    ro.product.cpu.abilist=x86,armeabi-v7a,armeabi
    ro.product.cpu.abilist32=x86,armeabi-v7a,armeabi
    ro.product.cpu.abilist64=
    ro.product.manufacturer=CW-Hi12
    ro.product.locale.language=en
    ro.product.locale.region=US
    ro.wifi.channels=
    ro.board.platform=gmin
    # ro.build.product is obsolete; use ro.product.device
    ro.build.product=cht_cr_mrd_w
    # Do not try to parse description, fingerprint, or thumbprint
    ro.build.description=cht_cr_mrd_w-userdebug 5.1 LMY47I eng.softteam.20160317.111935 release-keys
    ro.build.fingerprint=intel/cht_cr_mrd_w/cht_cr_mrd_w:5.1/LMY47I/softteam03171121:userdebug/release-keys
    ro.build.characteristics=tablet
    # end build properties

    #
    # ADDITIONAL_BUILD_PROPERTIES
    #
    ro.dalvik.vm.isa.arm=x86
    ro.enable.native.bridge.exec=1
    sys.powerctl.no.shutdown=1
    dalvik.vm.heapstartsize=8m
    dalvik.vm.heapgrowthlimit=100m
    dalvik.vm.heapsize=174m
    dalvik.vm.heaptargetutilization=0.75
    dalvik.vm.heapminfree=512k
    dalvik.vm.heapmaxfree=8m
    ro.opengles.version=196609
    ro.setupwizard.mode=OPTIONAL
    ro.com.google.gmsversion=5.1_r1
    ro.gnss.sv.status=true
    ro.hwui.texture_cache_size=24.0f
    ro.hwui.text_large_cache_width=2048
    ro.hwui.text_large_cache_height=512
    drm.service.enabled=true
    keyguard.no_require_sim=true
    ro.com.android.dataroaming=true
    ro.com.android.dateformat=MM-dd-yyyy
    ro.config.ringtone=Ring_Synth_04.ogg
    ro.config.notification_sound=pixiedust.ogg
    ro.carrier=unknown
    ro.config.alarm_alert=Alarm_Classic.ogg
    persist.sys.language=zh
    persist.sys.country=CN
    persist.sys.timezone=Asia/Shanghai
    persist.sys.dalvik.vm.lib.2=libart.so
    dalvik.vm.isa.x86.features=sse4_2,aes_in,popcnt,movbe
    dalvik.vm.lockprof.threshold=500
    net.bt.name=Android
    dalvik.vm.stack-trace-file=/data/anr/traces.txt

    # begin fota properties
    ro.fota.platform=IntelZ3735F_5.1
    ro.fota.type=pad_phone
    ro.fota.oem=hampoo-cherrytrail_5.1
    ro.fota.device=CW-Hi12
    ro.fota.version=cht_cr_mrd_w-userdebug 5.1 LMY47I eng.softteam.20160317.111935 release-keys
    # end fota properties

    #33424
    BoORD_L
    Participant
    • Posts: 290

    We all know SUPERCOWZ for his work and his competence.

    I assure you he is trustworthy.

    @SUPERCOWS do you think we have to change (i don’t remeber exactly) that  bit from 0 to 1 as we have done for TECLAST tablets?

    What I've used and what I've got:
    TECLAST X98 AIR 3G, TECLAST X98 AIR II, TECLAST X98 PRO,CHUWI HI8, CHUWI HI12, CUBE I9

    #33426
    spzjulien supercowz
    Participant
    • Posts: 172

    We all know SUPERCOWZ for his work and his competence. I assure you he is trustworthy. @SUPERCOWS do you think we have to change (i don’t remeber exactly) that bit from 0 to 1 as we have done for TECLAST tablets?

    thank you 🙂
    dunno didnt dump his bios … yet ..

    #33428
    BoORD_L
    Participant
    • Posts: 290

    ok

    Anyway I think as you state before the problem could be digitizer driver.

    Let’s see what 4pda friends will tell us 🙂

    What I've used and what I've got:
    TECLAST X98 AIR 3G, TECLAST X98 AIR II, TECLAST X98 PRO,CHUWI HI8, CHUWI HI12, CUBE I9

    #33429
    spzjulien supercowz
    Participant
    • Posts: 172

    we need bios dump from dualboot 01 jan serial (factory converted win10) instead 03 march serial 🙂

    #33430
    winston smith
    Participant
    • Posts: 115

    dd comand ? Via adb ? no need to have root acces to do so ?

    #33433
    BoORD_L
    Participant
    • Posts: 290

    I think it depends on build.

    If the rom has been built as developement (ro.debuggable=1) you can have access to root via command “adb root”  or default.prop as got this directive ro.secure set to “0”.

    Anyway Supercows will explain i think

    What I've used and what I've got:
    TECLAST X98 AIR 3G, TECLAST X98 AIR II, TECLAST X98 PRO,CHUWI HI8, CHUWI HI12, CUBE I9

    #33438
    Cesar G Luque
    Participant
    • Posts: 6

    What bios versión have the dual boot march Tablet?

    #33442
    SanHayate
    Participant
    • Posts: 18

    I’m the owner of the hi12 dual boot who has been dumped by spzjulien / supercowz

    Here are the bios info for hi12 dual boot, march, serie 30

    Core version: 5.011
    Project version E4D6_HI-122LP.221 x64
    Build date: 03/22/2016 20:00:47

    View post on imgur.com

    Attachments:
    You must be logged in to view attached files.
    #33471
    Anonymous
    Inactive
    • Posts: 65

    I have to say I am so glad supercowz has this tablet. I know he also did quite some work for the X98 Air 3G which I also own.
    Btw, check my new topic: [OFFICIAL][WINDOWS + ANDROID 5.1] Dual Boot files from Chuwi
    DUAL BOOT FILES!!!!!!!!

    EDIT: @supercows: can you check the system files for a touchscreen driver being loaded? Because if we see some kind of goodix driver being loaded, then I think it has to be the GT9110P, right?

    #33520
    Cesar G Luque
    Participant
    • Posts: 6

    Mi Tablet is Windows 10 only and 010 serial number

    My bios versión is
    Core Versión: 5.011
    Compliancy: UEFI 2.4; PI 1.3
    Project Versión: C122.606 x64
    Build Date and Time: 03/07/2016 16:09:36

    Could I updated to Dual Boot?

     

    Attachments:
    You must be logged in to view attached files.
Viewing 15 posts - 1 through 15 (of 16 total)
  • You must be logged in to reply to this topic.

Lost Password

Skip to toolbar