Archer_cn

Members
  • Content count

    63
  • Joined

  • Last visited


Community Reputation

14 Good

About Archer_cn

  • Rank
    Regular

Previous Fields

  • Your Current Device(s) ZTE Racer

Archer_cn's Activity

  1. Archer_cn added a post in a topic [solved,tutorial updated]Dual boot possibility...   

    no, I won't post a video, don't have time for that and no interest. But I'll update post with a short version of [how to]
     
    • 1
  2. Archer_cn added a post in a topic [ROM][GB-B895] GBXTREME ROM - ✰29032014✰ (MULTIBASEBAND)   

    multi-baseband has nothing to do with the kernel IMO. It just the libcm.so file in /system/lib that matters. the baseband.sh script in this rom detect baseband version and make link to proper  libcm*.so automatically on very boot.
    thus the patch will be overridden  on first boot,,,applying the patch just so not necessary. 
    • 0
  3. Archer_cn added a post in a topic Installing gbxtreme from stock GB 2.3.6 (Baseband 109808)   

    just install old CWM recovery
    • 0
  4. Archer_cn added a post in a topic [ROM][GB-B895] GBXTREME ROM - ✰29032014✰ (MULTIBASEBAND)   

    I downloaded this ROM and saw baseband.sh in /system/etc, and both libcm2030.so, libcm109808.so in /system/lib.    so I think it was made for multibaseband.
    so I tried, and it does work under 2030 baseband!.. no need to flash extra fix at all!
    • 0
  5. Archer_cn added a post in a topic [solved,tutorial updated]Dual boot possibility...   


    Now I do find a way to do it. just use fdisk command to re-partition internal SD to 2 extra partition as System & Data for 2nd OS. and a little modification to the boot.img and CWM updater-script ,then can install ICS+ rom on internal memory.
    • 0
  6. Archer_cn added a post in a topic [JB] [4.3.1] CyanogenMod 10.2 [ROM]   

    just updated 1106 over 1019.. but I don't feel more fluid than 1019, in fact, it performs a little slower. And I think 1106 has less usable RAM. 
    good thing is green camera is fixed. But Hardware decoding/acceleration for video play back is still not working. 
    Auto brightness also not working well.
    So I'm thinking to revert to 1019 till the bugs solved, sure it won't be long because we have Dazz :wub: ,thank you for your hard work on G300.
    • 0
  7. Archer_cn added a post in a topic [JB] [4.3.1] CyanogenMod 10.2 [ROM]   

    Oh my Lady Gaga,,! After 1 day use of this ROM(1009 build), It surprises me with its absolute fluid operation! And the Browser works like a charm, never saw this performance on stock ICS or any other roms! My settings: 
    1. turn off animation in developer option and display settings;
    2. overclock to 1152MHZ;
    3. Enable Zram(18%), KSM, allow purging of assets, 16bit transparency
    4. Enable Force GPU Rendering in developer options
    5. Disable some useless system apps (most are wallpaper related).
    6. no Gapps installed. I use other alternative app stores to download apps( like aptoide, :D )
    7.Greenify, yeah, must-have app!
     
    That's it! Thank you Dazz for such a beautiful work!! :wub:  Hope the Bluetooth tethering can be fixed soon :)
    And again FYI, Do use TWRP to flash this ROM but the CWM recovery recommended in the op, I'm pretty sure something is not right with that recovery.
    • 0
  8. Archer_cn added a post in a topic [JB] [4.3.1] CyanogenMod 10.2 [ROM]   

    1. still no wifi-direct support;
    2. use of latest CWM recovery in flashing this rom will result in files missing occasionally, and then come up FCs. TWP works just fine.
    3. poor free RAM..
    • 0
  9. Archer_cn added a post in a topic Hi guies!Is there anything about Android 4.3?   

    I want a third party ICS+ ROM with WIFI direct support...but no... :( .
    Heard about Ubuntu Edge too, hope G300 can have Ubuntu Touch :D
    • 0
  10. Archer_cn added a post in a topic [JB] [4.2.2] CyanogenMod 10.1 [ROM]   

    still no wifi-direct support. I've been waiting for this too.
    • 0
  11. Archer_cn added a topic in Huawei Ascend G300 Development   

    [solved,tutorial updated]Dual boot possibility...

    Finally I manage to do it on my G300. It works, now I have Stock GB & ICS installed
     
    Here is a how to tutorial, Please do read ervery detail and do it carefully if you want to proceed.
     
    How it works: make internal sd smller so have free space to make 2 new partitons(system&data);, then modify boot.img(init.rc) to change default mount point to new partitions, and flash new boot.img to recovery block..Thus we lost recovery program but boot to new os. There's a way to keep both, but i don't konw how and no time to figure it out. so you can see , default os is not affected, can always start you phone with no problem.
     
     
    update:
    1. KK doesn't mount internal SD。same in newest recovery using kernel 3.4. 
    2.script to switch systems,recovery:
    (1) reboot recovery               #reboot to recovery or OS2
    (2)dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p16               #flash recovery ( be careful with dd command, make sure you write the correct partition!)
    (3)dd if=/sdcard/boot2.img of=/dev/block/mmcblk0p16                    #flash sencond boot image to recovery for OS2 to boot.
    (4)reboot oem-1                   # reboot to bootloader(fastboot)mode in case you want to flash something via fastboot.
     
    you can save these scripts in gscipt for convenient use.( here assume you have recovery.img & boot2.img under /sdcard)
     
     
    Edit: 1. if you don't want to touch internal storage for safety reason, can just do it on external sd( mmcblk1p1).make 3 primary partiton(fat32 first), it shall work too.
            2. second os must be ICS+.
     
     
    Ok, Steps
     
    1. Backup your internal SD data, because all data on it will be lost
    2. boot your phone into recovery, connect phone with PC, and open a CMD window
    3. Re-partition internal SD
    adb shell su fdisk /dev/block/mmcblk0 p then you should see current internal storage partitions;

     
    on G300 the correspondence is
    mmcblk0p12-------system
    mmcblk0p13-------Data
    mmcblk0p15-------boot
    mmcblk0p16-------recovery
    mmcblk0p19-------internal SD only list the partitions that matters)
     
    all we need to change is mmcblkop19!!! don't touch any other partitions
    First, we need to delete mmcblkop19,
    in CMD window, enter d, then 19
    Command (m for help): [6nd 19   Now Create a new internal SD partition with smaller size.(it's very necessary to have a internal sd on most ROMs) the size is up to you.
    Here I make a 500MB size for internal sd(mmcblk0p19)400M (second)system, and the rest for (second)Data.
     
    Notes: 1). fdisk usagem for help d to delete a partiton, n to create new partition, p to print partition info, w to save all changes!
               2). First cylinder should be upper partition's last cylinder+2. ( it should be +1,but here don't know why have to be 2).
    Command (m for help): [6np p Disk /dev/block/mmcblk0: 3909 MB, 3909091328 bytes 1 heads, 16 sectors/track, 477184 cylinders Units = cylinders of 16 * 512 = 8192 bytes Device Boot Start End Blocks Id System /dev/block/mmcblk0p1 * 1 3 20 4d Unknown Partition 1 does not end on cylinder boundary /dev/block/mmcblk0p2 3 41 300 45 Unknown Partition 2 does not end on cylinder boundary /dev/block/mmcblk0p3 41 16681 133120 c Win95 FAT32 (LB A) Partition 3 does not end on cylinder boundary /dev/block/mmcblk0p4 16681 477184 3684031+ 5 Extended Partition 4 does not end on cylinder boundary /dev/block/mmcblk0p5 16897 18432 12288 6a Unknown /dev/block/mmcblk0p6 18433 43008 196608 83 Linux /dev/block/mmcblk0p7 43009 43520 4096 63 GNU HURD or Sys V /dev/block/mmcblk0p8 43521 43904 3072 58 Unknown /dev/block/mmcblk0p9 44033 44544 4096 46 Unknown /dev/block/mmcblk0p10 44545 44928 3072 4a Unknown /dev/block/mmcblk0p11 45057 45440 3072 4b Unknown /dev/block/mmcblk0p12 45569 94720 393216 83 Linux /dev/block/mmcblk0p13 94721 193024 786432 83 Linux /dev/block/mmcblk0p14 193025 193536 4096 47 Unknown /dev/block/mmcblk0p15 193537 194560 8192 48 Unknown /dev/block/mmcblk0p16 194561 197120 20480 60 Unknown /dev/block/mmcblk0p17 197121 197632 4096 6c Unknown /dev/block/mmcblk0p18 197633 207872 81920 83 Linux Command (m for help): [6nn n First cylinder (16682-477184, default 16682): [6n207874 207874 Last cylinder or +size or +sizeM or +sizeK (207874-477184, default 477184): [6n +500M +500M Command (m for help): [6np p Disk /dev/block/mmcblk0: 3909 MB, 3909091328 bytes 1 heads, 16 sectors/track, 477184 cylinders Units = cylinders of 16 * 512 = 8192 bytes Device Boot Start End Blocks Id System /dev/block/mmcblk0p1 * 1 3 20 4d Unknown Partition 1 does not end on cylinder boundary /dev/block/mmcblk0p2 3 41 300 45 Unknown Partition 2 does not end on cylinder boundary /dev/block/mmcblk0p3 41 16681 133120 c Win95 FAT32 (LB A) Partition 3 does not end on cylinder boundary /dev/block/mmcblk0p4 16681 477184 3684031+ 5 Extended Partition 4 does not end on cylinder boundary /dev/block/mmcblk0p5 16897 18432 12288 6a Unknown /dev/block/mmcblk0p6 18433 43008 196608 83 Linux /dev/block/mmcblk0p7 43009 43520 4096 63 GNU HURD or Sys V /dev/block/mmcblk0p8 43521 43904 3072 58 Unknown /dev/block/mmcblk0p9 44033 44544 4096 46 Unknown /dev/block/mmcblk0p10 44545 44928 3072 4a Unknown /dev/block/mmcblk0p11 45057 45440 3072 4b Unknown /dev/block/mmcblk0p12 45569 94720 393216 83 Linux /dev/block/mmcblk0p13 94721 193024 786432 83 Linux /dev/block/mmcblk0p14 193025 193536 4096 47 Unknown /dev/block/mmcblk0p15 193537 194560 8192 48 Unknown /dev/block/mmcblk0p16 194561 197120 20480 60 Unknown /dev/block/mmcblk0p17 197121 197632 4096 6c Unknown /dev/block/mmcblk0p18 197633 207872 81920 83 Linux /dev/block/mmcblk0p19 207874 268909 488288 83 Linux Command (m for help): [6nn n First cylinder (268911-477184, default 268911): [6n268911 268911 Last cylinder or +size or +sizeM or +sizeK (268911-477184, default 477184): [6n +400M +400M Command (m for help): [6np p Disk /dev/block/mmcblk0: 3909 MB, 3909091328 bytes 1 heads, 16 sectors/track, 477184 cylinders Units = cylinders of 16 * 512 = 8192 bytes Device Boot Start End Blocks Id System /dev/block/mmcblk0p1 * 1 3 20 4d Unknown Partition 1 does not end on cylinder boundary /dev/block/mmcblk0p2 3 41 300 45 Unknown Partition 2 does not end on cylinder boundary /dev/block/mmcblk0p3 41 16681 133120 c Win95 FAT32 (LB A) Partition 3 does not end on cylinder boundary /dev/block/mmcblk0p4 16681 477184 3684031+ 5 Extended Partition 4 does not end on cylinder boundary /dev/block/mmcblk0p5 16897 18432 12288 6a Unknown /dev/block/mmcblk0p6 18433 43008 196608 83 Linux /dev/block/mmcblk0p7 43009 43520 4096 63 GNU HURD or Sys V /dev/block/mmcblk0p8 43521 43904 3072 58 Unknown /dev/block/mmcblk0p9 44033 44544 4096 46 Unknown /dev/block/mmcblk0p10 44545 44928 3072 4a Unknown /dev/block/mmcblk0p11 45057 45440 3072 4b Unknown /dev/block/mmcblk0p12 45569 94720 393216 83 Linux /dev/block/mmcblk0p13 94721 193024 786432 83 Linux /dev/block/mmcblk0p14 193025 193536 4096 47 Unknown /dev/block/mmcblk0p15 193537 194560 8192 48 Unknown /dev/block/mmcblk0p16 194561 197120 20480 60 Unknown /dev/block/mmcblk0p17 197121 197632 4096 6c Unknown /dev/block/mmcblk0p18 197633 207872 81920 83 Linux /dev/block/mmcblk0p19 207874 268909 488288 83 Linux /dev/block/mmcblk0p20 268911 317739 390632 83 Linux Command (m for help): [6nn n First cylinder (16682-477184, default 16682): [6n317741 317741 Last cylinder or +size or +sizeM or +sizeK (317741-477184, default 477184): [6n Using default value 477184 Command (m for help): [6np p Disk /dev/block/mmcblk0: 3909 MB, 3909091328 bytes 1 heads, 16 sectors/track, 477184 cylinders Units = cylinders of 16 * 512 = 8192 bytes Device Boot Start End Blocks Id System /dev/block/mmcblk0p1 * 1 3 20 4d Unknown Partition 1 does not end on cylinder boundary /dev/block/mmcblk0p2 3 41 300 45 Unknown Partition 2 does not end on cylinder boundary /dev/block/mmcblk0p3 41 16681 133120 c Win95 FAT32 (LB A) Partition 3 does not end on cylinder boundary /dev/block/mmcblk0p4 16681 477184 3684031+ 5 Extended Partition 4 does not end on cylinder boundary /dev/block/mmcblk0p5 16897 18432 12288 6a Unknown /dev/block/mmcblk0p6 18433 43008 196608 83 Linux /dev/block/mmcblk0p7 43009 43520 4096 63 GNU HURD or Sys V /dev/block/mmcblk0p8 43521 43904 3072 58 Unknown /dev/block/mmcblk0p9 44033 44544 4096 46 Unknown /dev/block/mmcblk0p10 44545 44928 3072 4a Unknown /dev/block/mmcblk0p11 45057 45440 3072 4b Unknown /dev/block/mmcblk0p12 45569 94720 393216 83 Linux /dev/block/mmcblk0p13 94721 193024 786432 83 Linux /dev/block/mmcblk0p14 193025 193536 4096 47 Unknown /dev/block/mmcblk0p15 193537 194560 8192 48 Unknown /dev/block/mmcblk0p16 194561 197120 20480 60 Unknown /dev/block/mmcblk0p17 197121 197632 4096 6c Unknown /dev/block/mmcblk0p18 197633 207872 81920 83 Linux /dev/block/mmcblk0p19 207874 268909 488288 83 Linux /dev/block/mmcblk0p20 268911 317739 390632 83 Linux /dev/block/mmcblk0p21 317741 477184 1275552 83 Linux Command (m for help): [6n now, last step, save all changes. before you do this ,make sure that no other partitions but old mmcblk0p19 are touched!
    Command (m for help): [6nw 4. Format new partitions.
    reboot to recovery again.
    use adb..
    adb shell # mke2fs -T ext4 -b4096 -m 0 /dev/block/mmcblk0p20 # mke2fs -T ext4 -b4096 -m 0 /dev/block/mmcblk0p21 5. make a new rom for new partitons.
    1). we need to edit boot.img. can use android kitchen,unpack boot.img  to edit init.rc, replace all mmcblk0p12 with mmcblk0p20
    mmcblk0p13 to mmcblk0p21, then repack boot.img.
    2).updater script in a zip rom (META-INF\com\google\android\updater-script)
    add these 2 lines to the beginning
    unmount("/data"); unmount("/system"); and replacement:
    mmcblk0p12 >> mmcblock0p20 mmcblk0p13 >> mmcblk0p21 mmcblk0p15 >> mmcblk0p16 done. repack rom with new boot.img and flash it to second system...Then when you enter recovery, you actually booting the second android os.
    Normal reboot will boot into default os.
     
    There's a better way to switch os with script , will update later..
     
     
    Here is the slimv13 rom I moded to fit new partitions,if you already done the repartition, flash this via recovery and then reboot into recovery, you should see it booting.
    Moded ROM Download:
    http://www.speedyshare.com/zJkZF/download/B952-slim-v13Moded-2ndOS.zip
    • 16 replies
    • 2871 views
  12. Archer_cn added a post in a topic [DEV][ROM] RacerMod 1.7 [19/04/2013] CyanogenMod 7.2 port with 2.6.35.7 kernel & CWM Recovery 5.0.2.8   

    Thanks for your work! Really amazing you're still on this since many not using Racer any more. We appreciate you work a lot !
    Personally, I think the touchscreen would never be good, unless port a alternative driver from other resistant device(ZTE's or non-zte's).
    • 0
  13. Archer_cn added a post in a topic G300 modem!!!   

    lol. I think all android phones support this function.
    As to our G300 , just

    Dial *#*#2846579#*#*
    Select Project Menu
    Select Background Settings
    Select USB Ports Settings
    Choose Normal Mode


    Here you go, congrats having modem back :P
    I know this is old topic, but still may be of help to some people
    • 0
  14. Archer_cn added a post in a topic [JB] [4.2.2] CyanogenMod 10.1 [ROM]   

    Can we have Wifi-Direct function in future version? An app "fqrouter" need this and can make our phone as a wifi hotspod whiout disconnecting current wifi. this app works good with stock ICS.
    • 1
  15. Archer_cn added a post in a topic [JB] [4.2.2] CyanogenMod 10.1 [ROM]   

    I read CM10.1 changelog they mentioned " add FM support in android" 30/1/2013,,, :D , I believe we'll have built-in FM app soon :wub:
    • 0

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.