• Title: Pulid F13 / Pulid S4 / Star S4
  • Listed: 10/23/2013 12:17 am
  • ROM Version: ROM Android 4.2.1
  • You must be logged for ROM download.


Overall Rating : 6


11086 total views, 4 today

2 Total favorites

  

Pulid F13 / Pulid S4 / Star S4
Pulid F13 / Pulid S4 / Star S4 - Image 1

Author adMember Info


DESCRIPTION


I made this rom as I could not find any working rom for my formerly bricked Pulid F13 in the internet (And Pulid itself is of NO help – nonexistant customer support).

This Rom is made and successfully tested with Pulid F13 MTK6589 1.2 Ghz FullHD 5" Display 1GB Ram/8GB Flash.


Devices known where this rom works on:

- Pulid F13 MTK6589 1.2Ghz 1GB Ram/8GB Flash

- Pulid F13 MTK6589T 1.5Ghz 2GB Ram/32GB Flash

- Pulid S4 (exact version unknown – assume all 6589 based versions are working)

- Star One S4 Turbo MTK6589T 1.5GHz 2GB Ram/32GB Flash

 

I might also work for its siblings like Miz Z4. But this is yet untested!

ATTENTION: You are flashing this rom entirely at your own risk!

 

Contents:

- Mainly stock Android 4.2.1

- rooted

- Google Apps

- CWM Recovery

- Multilanguage

This is my very first rom so please be gracious to me! :-)

 

Installation:

Archive contains Rom,USB Drivers and SPFlashtool 3.1316.0.150

1. Unpack the archive using 7zip

2. If not already done: Install USB Drivers.

3. Switch off phone and remove battery and ALL cards.

4. Connect usb cable to phone but not computer

5. Start SP Flashtool (Flash_tool.exe) as ADMINISTRATOR!

6. Load scatter file from rom folder: MT6589_Android_scatter_emmc.txt

7. Press "Download" button.

8. Connect phone to computer

9. Wait for download to finish (green circle window at the end).

10. Unplug phone

11. Insert battery and start phone

12. Process setup wizard.

13. Go to "Settings" -> "Storage" -> Scroll down and press "Erase phone storage" -> Confirm this

     (If you don't do this your phone might hang on first reboot and you will need to reflash!)

14. Reboot phone

15. Done

:-)

 

Have fun!

 

Roland

 

It would be nice – if you flash this rom – if you would leave a comment here on which phone you have flashed it (retail name, cpu frequency, ram size and flash size). Thank you very much.

 



※Please make a backup of your device before installing or updating ROM


51 Responses to“Pulid F13 / Pulid S4 / Star S4”







  1. 07/12/2013

    Serbia

    Hi everyone,

    I was installed few months ago stock firmware with Build number S4 20130604-182644. I see that you are using the same one. Can you explain what you customized in it?
    For me that one solved problems with unstable WiFi but still I have issue that Google sync is stop forking after day or two, so I need to restart the phone. Also I was noticed that I’m getting low disk space warning.
    I find out that something is making enormous log files in /data/log_other_mode so I need occasionally to erase all those files except properties file which is not growing.

    If all of you will be so nice to check if you have these log files it would be great.





    • 10/04/2013

      Germany

      Hi…

      Which phone do you have exactly?

      Which log is growing in /data/log_other_mode? My foldersize is 6MB.

      Maybe we should take a look in that logs to get clue what is going on on your phone. Maybe this comes from a specify app you are using

       

      Roland





  2. 07/12/2013

    Serbia

    Hi Roland,

    I have Star S4, (Pulid F13) and a have more than one log creating and growing. I think that those log are from the system, bad kernel. This is a list after only few days I didn’t erased them (217MB).

    events_log
    kernel_log
    kernel_log.1
    kernel_log.2
    kernel_log.3
    kernel_log.4
    main_log
    main_log.1
    main_log.2
    main_log.3
    main_log.4
    radio_log
    radio_log.1

    I have one file “properties” which does not grow. I’m using auto power on/off function and part of events_log is:

    11-25 06:00:14.085 131 131 I boot_progress_start: 8597
    11-25 06:00:14.429 287 287 I boot_progress_start: 8940
    11-25 06:00:15.048 287 287 I boot_progress_preload_start: 9559
    11-25 06:00:21.090 287 287 I boot_progress_preload_end: 15601
    11-25 06:00:21.898 512 530 I boot_progress_system_run: 16410
    11-25 06:00:22.501 512 530 I boot_progress_pms_start: 17012
    11-25 06:00:23.088 512 530 I boot_progress_pms_system_scan_start: 17599
    11-25 06:00:25.172 512 530 I boot_progress_pms_data_scan_start: 19683
    11-25 06:00:28.928 512 530 I boot_progress_pms_scan_end: 23440
    11-25 06:00:29.312 512 530 I boot_progress_pms_ready: 23823
    11-25 06:00:29.728 512 530 I battery_status: [2,2,1,2,Li-ion]
    11-25 06:00:29.728 512 530 I battery_level: [99,4108,190]
    11-25 06:00:30.057 512 531 I screen_toggled: 1
    11-25 06:00:30.579 512 530 I configuration_changed: 5624
    11-25 06:00:30.846 512 555 I configuration_changed: 5224
    11-25 06:00:31.349 512 577 I wifi_state_changed: InitialState
    11-25 06:00:31.360 512 577 I wifi_state_changed: DriverUnloadedState
    11-25 06:00:31.468 512 577 I wifi_state_changed: DriverLoadingState
    11-25 06:00:31.521 512 530 I free_storage_left: [786173952,66482176,118448128]
    11-25 06:00:31.522 512 530 I free_storage_changed: 786173952

    Part of kernel_log:

    <7>[14514.221078] (0)[444:mobile_log_d][444:mobile_log_d] sig 14 to [148:mtkbt]
    <6>[14514.415356] (0)[15821:Crashlytics Ini]socket_create[77362]:fd=67
    <6>[14514.415417] (0)[15821:Crashlytics Ini][mtk_net_dev]devinet_ioctl cmd = 0×8915 rtnl_lock++
    <6>[14514.415430] (0)[15821:Crashlytics Ini][mtk_net_dev]devinet_ioctl cmd = 0×8915 rtnl_lock–
    <6>[14514.415534] (0)[15821:Crashlytics Ini]socket_close[77362]
    <6>[14514.416252] (0)[15821:Crashlytics Ini]socket_create[77363]:fd=67
    <6>[14514.416279] (0)[15821:Crashlytics Ini][mtk_net_dev]devinet_ioctl cmd = 0×8915 rtnl_lock++
    <6>[14514.416290] (0)[15821:Crashlytics Ini][mtk_net_dev]devinet_ioctl cmd = 0×8915 rtnl_lock–
    <6>[14514.416340] (0)[15821:Crashlytics Ini]socket_close[77363]
    <6>[14514.417015] (0)[15821:Crashlytics Ini]socket_create[77364]:fd=67
    <6>[14514.417042] (0)[15821:Crashlytics Ini][mtk_net_dev]devinet_ioctl cmd = 0×8915 rtnl_lock++
    <6>[14514.417053] (0)[15821:Crashlytics Ini][mtk_net_dev]devinet_ioctl cmd = 0×8915 rtnl_lock–
    <6>[14514.417100] (0)[15821:Crashlytics Ini]socket_close[77364]
    <6>[14514.441583] (0)[15821:Crashlytics Ini]socket_create[77365]:fd=67
    <6>[14514.441619] (0)[15821:Crashlytics Ini][mtk_net_dev]devinet_ioctl cmd = 0×8915 rtnl_lock++
    <6>[14514.441631] (0)[15821:Crashlytics Ini][mtk_net_dev]devinet_ioctl cmd = 0×8915 rtnl_lock–
    <6>[14514.441690] (0)[15821:Crashlytics Ini][mtk_net_dev]devinet_ioctl cmd = 0×8919 rtnl_lock++

    Part of main_log:

    11-25 18:09:26.318 3138 3143 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.319 15453 15459 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.319 911 919 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.319 828 838 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.319 779 785 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.320 672 676 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.321 4410 4416 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.321 805 811 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.321 601 610 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.321 717 723 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.321 819 826 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.321 789 798 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.322 505 511 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.453 13668 13672 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.474 872 879 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.474 2609 2615 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.474 5672 5675 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.474 4341 4345 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.474 15467 15472 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.475 5708 5712 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.484 858 864 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.484 1654 1660 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.484 13650 13653 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.484 16568 16574 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.484 15485 15491 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.484 4520 4526 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.484 5721 5725 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.485 900 906 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.491 2456 2462 D jdwp : Can’t connect to ADB control socket:Connection refused
    11-25 18:09:26.578 505 550 D InputReader: AP_PROF:AppLaunch_dispatchPtr:Down:10675465
    11-25 18:09:26.578 505 550 I AP_PROF : unable to open /proc/mtprof/status entry
    11-25 18:09:26.578 505 549 D PowerManagerService: userActivityFromNative
    11-25 18:09:26.578 505 549 D PowerManagerService: userActivityNoUpdateLocked: eventTime=10675465, event=2, flags=0×0, uid=1000
    11-25 18:09:26.579 505 549 D PowerManagerNotifier: onUserActivity: event=2, uid=1000
    11-25 18:09:26.579 505 549 D PowerManagerService: updateUserActivitySummaryLocked: mWakefulness=Awake, mUserActivitySummary=0×5, nextTimeout=10676162 (in 695 ms)
    11-25 18:09:26.579 505 549 D PowerManagerService: newScreenState = 2
    11-25 18:09:26.580 505 549 D

    Part of radio_log:

    11-25 14:26:00.677 672 672 D GSM : [GDCT][simId2]isDataPossible(cbs): possible=true isDataAllowed=true apnTypePossible=true apnContextisEnabled=false apnContextState()=IDLE
    11-25 14:26:00.677 672 672 D PHONE : [GeminiDataSubUtil] [DataStateChanged]:state=DISCONNECTED,reason=nwTypeChanged,apnName=null,apnType=cbs,from sim_id=1
    11-25 14:26:00.677 672 672 D GSM : [GDCT][simId2]apnType = cbs
    11-25 14:26:00.677 672 672 D GSM : [GDCT][simId2]isDataPossible(cbs): possible=true isDataAllowed=true apnTypePossible=true apnContextisEnabled=false apnContextState()=IDLE
    11-25 14:26:00.677 672 672 D GSM : [GDCT][simId2]get active apn string for type:cbs
    11-25 14:26:00.680 672 672 D GSM : [GDCT][simId2]handleMessage msg={ what=270373 when=-231ms obj=android.os.AsyncResult@4383eda8 target=Handler (com.android.internal.telephony.gsm.GsmDataConnectionTracker) {431e6e68} }
    11-25 14:26:00.680 672 672 D GSM : [GDCT][simId2][SCRI]EVENT_NW_RAT_CHANGED
    11-25 14:26:00.680 672 672 D GSM : [SCRI]getScriNwType:15
    11-25 14:26:00.682 672 672 D PHONE : [GeminiDataSubUtil] Recv STATE_IN_SERVICE Intent from simId=1
    11-25 14:26:00.706 672 672 D RILJ : RIL(1) :[2393]> REQUEST_GET_NEIGHBORING_CELL_IDS
    11-25 14:26:00.708 475 488 I RILC : RIL(2) SOCKET REQUEST: GET_NEIGHBORING_CELL_IDS length:8
    11-25 14:26:00.708 475 488 I RILC : 4B 00 00 00 59 09 00 00 01 00 00 00 01 00 00 00
    11-25 14:26:00.708 475 488 D RILC : New command received from RIL(2)
    11-25 14:26:00.708 475 488 D RIL : GET_NEIGHBORING_CELL_IDS dispatched to RIL_URC2_PROXY
    11-25 14:26:00.708 475 477 I RIL : RIL_CMD_PROXY_3 wakeup

    If you have any clue…





  3. 11/28/2013

    Romania

    Hey man!

    My name is Andrei and I've bought this phone 2 days ago. So far so good, it's awesome(though mine has different specs, CPU-Z tested: 1GB RAM, 8GB internal flash, MTK6589Turbo 1.5GHz). Anyway, the video chipset barely holds it's own so I wanted to root/flash a new rom to OC the phone and change screen resolution. So I've came across your post here and I've tried it. 

    Here comes the problem: When I click download(Press "Download" button.) it says searching in the bottom and it stayed like that for 20 minutes until I've got bored and cancelled it. I've tried multiple times, it just won't download what it needs. Any idea why is that?

    If it matters, I'm running W8 64-bit and I did try compatibility mode(and admin, ofc). 

    I hope it will work, as I really like this phone and I want better performance out of it for high-end games. Thanks!


     





    • 10/04/2013

      Germany

      Are you sure you are having a Pulid F13  or S4 ?

       

      AFAIK there is no 1GB/8GB with MTK6589T… If you flash a phone with the wrong version you risk bricking it! Anyway you should make a backup of your stock rom first with MTKDroidTools.

       

      Because of your flashing problems:

      It might be that you also need to install the vcom driver from pdanet. You can search google for it…

       





    • 11/28/2013

      Romania

      I’m sure the phone is Pulid F13. I can give you some SShots if you want. Those are the specs of my F13 :)
      Anyway, I’ll try that tonight(busy right now) and I’ll let you know of the outcome. Thanks and have a nice day!





  4. 11/28/2013

    Romania

    Man, I got into that "MTKDroidTools" app and all the things to do to root the phone, backup etc and it's too hard for me. I'm not not all liking all the steps and sheer blindless with which I act to do everything. I'd rather not do anything than risk bricking the phone and not be able to recover. Is there any way to root the phone without side effects? I only want to lower resolution and I'm fine and the stock ROM can do that. I appreciate if you could help me with that. By the way, I've rated your ROM with 5 stars as I'm pretty sure it works and you seem a nice guy.





  5. 08/25/2013

    Netherlands

    I'm wondering if somebody else has also problems with wifi and gps. I've wifi connection but no data, only when I'm at 3 meter from my router.

    Getting a fast fix is not possible, I've tried a lot of things including apps, change ths gps file, build.prop etc. Even tried other roms, i.e. for the star S4.

    Does somebody encoutered these problems and has found an option. On thing is sure: I'll never buy Pulid again…





    • 11/28/2013

      Romania

      It's the bad antenna in the phone. Everyone has this problem, it's not software's fault. The phone has an amazing price/performance ratio, though.





  6. 08/25/2013

    Netherlands

    I' was so fed up with the gps signal, so I made myself an antenna. And it works until now. I only have to sophisticate it a little more.

     

    What about the Wi-Fi antenna? Is it also possible to make one yourself? Any one tried already?

     





  7. 12/09/2013

    Finland

    work greats at Pulid S4 (Build Number S4 20130604-224540)  Good Job! 

    ps.can you put in tags: Diel, M-Venti and 5.0





  8. 12/24/2013

    Israel

    thank you very much finally decent rom for pulid f13

    the rom are working for my phone:pulid f13 MTK6589T ,2g/32G

    thank you again for the hard work!!





  9. 07/12/2013

    Serbia

    Dear fellows sorry for my bad English,

    I was bothered with poor GPS and Wi-Fi reception like all of you so I decided to open the phone and see where is the problem.

    On the motherboard for both antennas there are contacts for ground and hot-end.

    The problem is that a factory antennas are constructed as self-adhesive foil on which are printed antenna lines and they are

    actually making short circuit.

    It is necessary, on the bottom of plastic you removed when you opened the phone, right below original antenna to stick the some

    ground surface about 10mm wide.

    I used self-adhesive aluminum foil. You must do so that the factory antenna make contact with the hot-end only and not with ground

    contact from the motherboard.

    When you open the phone and the screen is upside down, the battery compartment is under the motherboard, and on the left you can

    see the GPS contacts and on the right Wi-Fi. For GPS upper contact (further from the battery) is ground, and for Wi-Fi bottom (near

    the battery).

    Isolate parts of factory antenna (that one for ground contact) and tape over the aluminum foil that will have a hole at the part

    where the hot-end have to touch the factory-antenna. Finally you have to tape the duct tape over the aluminum foil or isolate with

    something, so when you close the phone that ground foil will not touches something inside.

    For GPS you should set all A-GPS and EPO settings but I will not explain it here because you can fined it on Internet.


    For more better Wi-Fi signal or let say even better data flow, especially when you are away from the router, you should attach over

    the factory antenna, on the outside, L-shaped aluminum foil.

    Unstable work of GPS and Wi-Fi was caused because contacts were shorted and there is no ground surface.

    If someone is interested in matter I suggest to look on wiki dipole antenna.

    My final results are:
    - 10 sec to lock GPS signal and SNR is around 33 dB, accuracy 3m = no more problems with GPS software I had
    - at point away from router where I had 0,001 Mbps I now have 30+ Mbps down/upload

    Regards


     





    • 10/04/2013

      Reserved

      Hi integralac!

      Thanks for this great guide! I believe this will help a lot of people!

      Do you have maybe also pictures showing the insides of your phone after the modifications?

      (eg. backside of plastic with the aluminium foil)?

       

      Again thanks for sharing the results of your hard work!

       

      Roland

       

       





  10. 02/23/2014

    Israel

    will this work with pulid f13 mt6577  (b92)


Leave a Reply

You must be logged in to post a comment.