Search Results for 's3'

[Linux User]

Stock ROM or stock Firmware S0450WW for BLU Studio J8M LTE is now available to download. Here is how to flash stock firmware S0450WW on BLU Studio J8M LTE using Mediatek SP Flash Tool.

Although I will make a very clean beginner’s step by step guide, but it is also advisable for you to go through all the steps in detail, so that you understand what are you doing.

 

[su_note note_color=”#F9D9D9″ text_color=”#AA4343″ radius=”3″ class=”” id=””]
DISCLAIMER:
THIS STOCK ROM FLASHING IS ONLY FOR BLU Studio J8M LTE WHICH IS MEDIATEK MT6737 CHIPSET BASED DEVICE.
DON’T TRY TO FLASH ON OTHER MT6737 BASED DEVICES OR ANY OTHER DEVICE TYPE.
[/su_note]

[su_note note_color=”#FBF4DD” text_color=”#A38C68″ radius=”3″ class=”” id=””]FLASHING A STOCK ROM ON BLU Studio J8M LTE WILL DELETE ALL DATA.
– IT ALWAYS A GOOD IDEA TO KEEP A BACKUP OF ALL DATA SUCH AS: SMS, PHONE CALL, CONTACT, MUSIC, IMAGES, etc.
– ALSO BACKUP THE IMEI AND NVRAM DATA OF YOUR PHONE.
[/su_note]

Required Guides and Downloads to Install Stock ROM/Firmware S0450WW on BLU Studio J8M LTE:

• Mediatek VCOM Driver
• SP Flash Tool
• ROM Download link of stock firmware S0450WW for BLU Studio J8M LTE
• Install stock ROM using SP Flash Tool

 

Why to flash S0450WW Stock Firmware/ROM on BLU Studio J8M LTE:

There could be various reasons why you may want to flash a stock firmware on BLU Studio J8M LTE to make it a new like phone. Following are some of the key benefits you get by flashing a stock firmware on BLU Studio J8M LTE:

• Flashing a stock ROM on BLU Studio J8M LTE will make the phone new like at least from software point of view.
• If your phone has become too slow or lagging in performance after a prolonged period of usage, then installing a stock ROM/firmware may bring back the speed.
• If you have rooted your Android phone, then flashing a stock ROM will help you to restore your phone software to original state.

  [su_note note_color=”#D7E3F4″ text_color=”#728095″ radius=”3″ class=”” id=””]Sometimes software factory reset from Android settings does not help you get rid of ROOT.
  In that case, you must flash a stock Firmware to bring back the phone to original state.[/su_note]

• Phone warranty will be VOID if you have ROOT on Android phone or have a custom ROM on Android phone. Flashing a stock Firmware/ROM will bring back the software to original state and will restore your warranty.

 

How to Flash Stock Fimrware / ROM S0450WW on BLU Studio J8M LTE using Mediatek SP Flash Tool:

1. Download and extract the BLU Studio J8M LTE stock firmware files.
2. Download and install the VCOM driver on your PC.

   [su_note note_color=”#D7E3F4″ text_color=”#728095″ radius=”3″ class=”” id=””]VCOM driver is required for the SP Flash Tool to recognize your BLU Studio J8M LTE Phone to be able to download stock Fimrmware.[/su_note]

3. Download and extract the Mediatek SP Flash Tool zip file.
4. Go to the extracted SP Flash Tool folder and open the flash_tool.exe file, which is the actual SP Flash Tool application.

   See the below screenshot:
   

5. By default the SP Flash Tool would have opened with the Download Tab open. If not then click on the Download Tab and then click on the choose button to load the BLU Studio J8M LTE stock ROM scatter file.

   [su_note note_color=”#D7E3F4″ text_color=”#728095″ radius=”3″ class=”” id=””]- You will find a scatter file with a name of somewhat MT6737_Android_scatter.txt in the BLU Studio J8M LTE stock firmware package.
   – This scatter file contains all the partition information of BLU Studio J8M LTE Mediatek phone and which binary file to flash on a which partition and address.[/su_note]

   See the screenshot below:
   

6. After that a file browser will be opened to find and select the BLU Studio J8M LTE S0450WW stock ROM scatter file.
   Go to the BLU Studio J8M LTE S0450WW stock firmware folder where you have extracted, select the Scatter file (somewhat MT6737_Android_scatter.txt) from there and click on Open.

   See the screenshot below:
   

7. After loading the scatter file, click on the Download button to start downloading the stock firmware to BLU Studio J8M LTE.

   [su_note note_color=”#FBF4DD” text_color=”#A38C68″ radius=”3″ class=”” id=””]Firmware download does not start just by clicking the Download button. You need to connect the phone in download mode, which we will be doing that in the later step.[/su_note]

   [su_note note_color=”#D7E3F4″ text_color=”#728095″ radius=”3″ class=”” id=””]- SP Flash Tool automatically takes all the information and will show you the details of partition and binary file information. Verify all the details before start flashing the stock ROM or the stock firmware on your Mediatek phone.
   – Verify the download mode before flashing (marked by number 1 in the screenshot).
   – Verify which all partitions are being flashed (marked by number 2 in the screenshot). MAKE SURE THERE IS NO NVRAM OR IMEI PARTITION SELECTED HERE.[/su_note]

   See the screenshot below:
   

8. Now turn off your Mediatek Phone and wait for few seconds.
   Then you hold both the volume up and Volume Down button and connect the phone PC using a USB cable.

   – You see in the SP Flash tool, it will start downloading the firmware to the Mediatek Phone automatically.

9. After the stock ROM is flashed successfully on BLU Studio J8M LTE, you will see a Download OK confirmation on SP Flash Tool.

   See the screenshot below:
   

After being successfully install S0450WW stock firmware or the stock ROM on BLU Studio J8M LTE, you can disconnect the phone and restart if it does not restart automatically.

If you face any problem installing the S0450WW stock firmware on BLU Studio J8M LTE using SP Flash Tool, then leave a reply on this thread. I will reply back as early as possible.

[su_note note_color=”#D7E3F4″ text_color=”#728095″ radius=”3″ class=”” id=””]Stay tuned or Subscribe to the BLU Studio J8M LTE forum for recovery, rooting, custom ROM guides etc. and all other device specific topics.[/su_note]s

[Linux User]

Hi shibaa987

Recovery TWRP 3.0.2.1
ROM Lineage 14.1.20171108.nightly.i9305.signed.zip
KERNEL m3xx/m3:4.4.4/KTU84P/I9305XXUFPB1
BASEBAND i9305XXUFNI3
BOOTLOADER i9305XXUFNI3

My last_kmsg if attached file is out

”
<6>[ 199.807734] c0 call_battery_notify : VID : 0x1d6b, PID : 0x1 skipped.
<7>[ 199.814150] c0 usb usb2: usb_probe_device
<7>[ 199.814242] c0 usb usb2: configuration #1 chosen from 1 choice
<7>[ 199.814731] c0 usb usb2: adding 2-0:1.0 (config #1, interface 0)
<7>[ 199.817143] c0 hub 2-0:1.0: usb_probe_interface
<7>[ 199.817234] c0 hub 2-0:1.0: usb_probe_interface – got id
<6>[ 199.817341] c0 hub 2-0:1.0: USB hub found
<6>[ 199.817448] c0 hub 2-0:1.0: 3 ports detected
<7>[ 199.817528] c0 hub 2-0:1.0: standalone hub
<7>[ 199.817602] c0 hub 2-0:1.0: no power switching (usb 1.0)
<7>[ 199.817694] c0 hub 2-0:1.0: global over-current protection
<7>[ 199.817790] c0 hub 2-0:1.0: power on to power good time: 4ms
<7>[ 199.817910] c0 hub 2-0:1.0: local power source is good
<7>[ 199.818000] c0 hub 2-0:1.0: no over-current condition exists
<7>[ 199.818100] c0 hub 2-0:1.0: trying to enable port power on non-switchable hub
<7>[ 199.825267] c0 s5p-ehci s5p-ehci: GetStatus port:2 status 001803 0 ACK POWER sig=j CSC CONNECT
<7>[ 199.825428] c0 hub 1-0:1.0: port 2: status 0501 change 0001
<7>[ 199.915243] c0 hub 2-0:1.0: state 7 ports 3 chg 0000 evt 0000
<7>[ 199.925436] c0 hub 1-0:1.0: state 7 ports 3 chg 0004 evt 0000
<7>[ 199.925577] c0 hub 1-0:1.0: port 2, status 0501, change 0000, 480 Mb/s
<7>[ 199.980305] c0 s5p-ehci s5p-ehci: port 2 high speed
<7>[ 199.980420] c0 s5p-ehci s5p-ehci: GetStatus port:2 status 001005 0 ACK POWER sig=se0 PE CONNECT
<6>[ 200.040206] c0 usb 1-2: new high speed USB device number 2 using s5p-ehci
<6>[ 200.210119] c0 mdm_subsys_powerup: mdm modem restart timed out.
<0>[ 200.210250] c0 Kernel panic – not syncing: subsystem_restart_wq_func[e56ff5e0]: Failed to powerup external_modem!
<4>[ 200.210448] c0 Backtrace:
<4>[ 200.210568] c0 [<c005322c>] (dump_backtrace+0x0/0x120) from [<c07783c4>] (dump_stack+0x20/0x24)
<4>[ 200.210711] c0 r7:e5734000 r6:c02d3e18 r5:c0778ad4 r4:c0c094a8
<4>[ 200.210844] c0 [<c07783a4>] (dump_stack+0x0/0x24) from [<c077897c>] (panic+0xac/0x204)
<4>[ 200.211003] c0 [<c07788d0>] (panic+0x0/0x204) from [<c0075f60>] (subsystem_restart_wq_func+0x2dc/0x2e0)
<4>[ 200.211154] c0 r3:c09a97a8 r2:e56ff5e0 r1:c0789500 r0:c09aa2f4
<4>[ 200.211271] c0 r7:e5734000
<4>[ 200.211349] c0 [<c0075c84>] (subsystem_restart_wq_func+0x0/0x2e0) from [<c00bf73c>] (process_one_work+0x168/0x558)
<4>[ 200.211528] c0 [<c00bf5d4>] (process_one_work+0x0/0x558) from [<c00bff20>] (worker_thread+0x178/0x410)
<4>[ 200.211697] c0 [<c00bfda8>] (worker_thread+0x0/0x410) from [<c00c4e14>] (kthread+0xb0/0xb4)
<4>[ 200.211882] c0 [<c00c4d64>] (kthread+0x0/0xb4) from [<c00a3d18>] (do_exit+0x0/0x92c)
<4>[ 200.212011] c0 r6:c00a3d18 r5:c00c4d64 r4:eb057e88
<6>[ 200.312538] c0 notifier_call_chain : NOTIFY BAD sec_debug_panic_handler
<0>[ 200.312660] c0 Rebooting in 1 seconds..
<7>[ 201.020055] c0 s5p-ohci s5p-ohci: auto-stop root hub
<0>[ 201.314555] c0 sec_reboot (104, emergency)

Samsung S-Boot 4.0 for GT-I9305 (Sep 12 2014 – 13:40:58)

EXYNOS4412(EVT 1.1) / 2044MB / 0MB / Rev 2 / I9305XXUFNI3 /(PKG_ID 0xe074018)

BOOTLOADER VERSION : I9305XXUFNI3

PMIC rev = PASS2(4)
BUCK1OUT(vdd_mif) = 0x03
BUCK3DVS1(vdd_int) = 0x28
cardtype: 0x00000007
SB_MMC_HS_52MHZ_1_8V_3V_IO
mmc->card_caps: 0x00000311
mmc->host_caps: 0x00000311
[mmc] capacity = 30777344

MODEL_NAME:{{GT-I9305}}
eMMC_SERIAL_NUMBER:{{1501004D4147344642F7A405D6089F8D}}

– read_bl1
pit_check_signature (PIT) valid.
initialize_ddi_data: usable! (5:0xe)
[RPMB] emmc_rpmb_open:
Get DATA success.

[RPMB] emmc_rpmb_close:
initialize_rpmb_data: usable! (GT-I9305:VERSION_-+A3)
PARAM ENV VERSION: v1.0..
set_charger_current: chg curr(bf), in curr(17)
set_charger_state: buck(1), chg(1), reg(0x05)
microusb_get_attached_device: STATUS1:0x3f, 2:0x00
set_auto_current: ta_state(0), curr(700)
init_fuelgauge: fuelgauge power ok
init_fuelgauge: not POR status
init_fuelgauge: is reset case, skip soc-cal.
get_table_soc: vcell(4001) is caculated to t-soc(77.927)
init_fuelgauge: start: vcell(4001), vfocv(4056), soc(76), table soc(77)
init_fuelgauge: finish: vcell(4001), vfocv(4056), soc(76), table soc(77)
init_microusb_ic: before MUIC: CDETCTRL:0x2d
init_microusb_ic: after MUIC: CDETCTRL:0x2d
init_microusb_ic: MUIC: CONTROL1:0x00
init_microusb_ic: MUIC: CONTROL1:0x00
init_microusb_ic: MUIC: CONTROL2:0x3b
init_microusb_ic: MUIC: CONTROL2:0x3b
PMIC_ID = 0x02
PMIC_IRQSRC = 0x00
PMIC_IRQ1 = 0x00
PMIC_IRQ2 = 0x00
PMIC_IRQ1M = 0xff
PMIC_IRQ2M = 0xff
PMIC_STATUS1 = 0x12
PMIC_STATUS2 = 0x00
PMIC_PWRON = 0x09
PMIC_RTCINT = 0x11
PMIC_RTCINTM = 0x3f
s5p_check_keypad: 0x0
s5p_check_reboot_mode: INFORM3 = 0 … skip
s5p_check_upload: MAGIC(0x66262564), RST_STAT(0x20000000)
s5p_check_upload: debug level is 4f4c!
s5p_check_upload: level low or unknown: skip 0
s5p_check_download: 0
microusb_get_attached_device: STATUS1:0x3f, 2:0x00
check_pm_status: normal reset, do not enter LPM mode.
cmu_div:1, div:7, src_clk:800000000, pixel_clk:38102400
s5p_dsim_display_config: VIDEO MODE
a2, 60, 90,
<start_checksum:481>CHECKSUM_HEADER_SECTOR :4096
<start_checksum:483>offset:50, size:6296
<start_checksum:485>CHECKSUM_HEADER_INFO : NeedChecksum:0 PartNo:20
Not Need Movinand Checksum
Movinand Checksum Confirmation Pass
[mobi_drv] add: 0x43e52500, size: 3933
MobiCore INIT response = 0
MobiCore RTM has initialized!
MobiCore IDLE flag = 0
MobiCore driver address 43e52500, size = 3933
MobiCore RTM Notified back!
MobiCore Driver loaded and RTM IDLE!
MobiCore RTM has been uninitialized!
load_kernel: loading boot image from 106496..
Verify_Binary_Signature: failed.
pit_check_signature (BOOT) invalid.
Set invalid sign flag
No need to update kernel type.

SMC Num = 0x83000001

mobismc success!!! [ret = 0]
[s5p_check_sboot_version_rpmb]cur_version:VERSION_-+A3, rpmb_version:VERSION_-+A3
rpmb_version:51, cur_version:51
ATAG_CORE: 5 54410001 0 0 0
ATAG_MEM: 4 54410002 20000000 40000000
ATAG_MEM: 4 54410002 20000000 60000000
ATAG_MEM: 4 54410002 20000000 80000000
ATAG_MEM: 4 54410002 1FC00000 A0000000
ATAG_SERIAL: 4 54410006 42f7a405 d6089f8d
ATAG_INITRD2: 4 54420005 42000000 163c82
ATAG_REVISION: 3 54410007 2
check_rustproof [0]
ATAG_CMDLINE: b1 54410009 ‘console=ram loglevel=4 androidboot.baseband=mdm sec_debug.level=0 sec_watchdog.sec_pet=5 androidboot.debug_level=0x4f4c sec_log=0x200000@0x46000000 sec_tima_log=0x200000@0x46202000 sec_avc_log=0x40000@0x46404000 s3cfb.bootloaderfb=0x5ec00000 lcdtype=96 consoleblank=0 lpj=3981312 vmalloc=176m oops=panic pmic_info=67 cordon=a9e8b102ee79091bce1a37f9ebc7c99d connie=GT-I9305_OPEN_EUR_c83922bf5d8c0260508331b814394821 androidboot.emmc_checksum=3 androidboot.boot_salescode= androidboot.odin_download=1 androidboot.bootloader=I9305XXUFNI3 androidboot.selinux=enforcing androidboot.warranty_bit=1 androidboot.sec_atd.tty=/dev/ttySAC2 androidboot.serialno=42f7a405d6089f8d snd_soc_core.pmdown_time=1000’
ATAG_NONE: 0 0

Starting kernel at 0x40008000…

SWITCH_SEL(3)
”

Previously, i used the aicp_i9305_n-12.1-rodman01-20170419 ROM, without random reboots (not so often)

hope this can help.

Newbie in Android ROM.
And many thanks for your job

[Linux User]

Installed on my S3 LTE i9305 successfully, everything is working except sim card :/
I am using Telenor sim in Pakistan and sim is not working. So please fix this bug soon and remind me to download the new update.
Overall great work, Thanks but this time going back to UnOfficial Marshmallow.

• This reply was modified 3 weeks, 2 days ago by Linux User.

[Linux User]

Can someone make a Android 8.0 or 8.1 (Oreo) ROM for the Leeco le S3 x626 Mediatek helio x20 ?
Others infos: 64 Gb – 21 Mp camera Sony IMX 230

Please :(

Thank you guys!

[Linux User]

Can I install this ROM on a S3 Neo GT-I9301I?

[Linux User]

[quote quote=24273]I’ve been trying to install several custom roms including this one and always I face the camera issue. It lacks functions or it just disconnect or freezes and I have to turn off-on the phone. I have Galaxy S3 i9300 International model but I can’t figure how to solve this. I’ve also installed CM10, CM11 and CM12 with the same results. The phone is a beauty piece of hadware and I want to keep it two more years -at least- 😉
[/quote]

If there would be a BUG on the ROM everybody would have reported the same.
If you face the problem on all of the ROMs, then I doubt it’s the camera module on your phone which might have gone bad.

You can install a stock ROM and confirm if the camera hardware is woring fine!!

• This reply was modified 3 weeks, 3 days ago by Linux User.

[Linux User]

No. This ROM will not work on S3 NEO.

S3 Neo only have CM12.1
Here is the:
Galaxy S3 NEO CM12.1 Lollipop ROM [GT-i9300i, i9301i and i9301Q]

• This reply was modified 3 weeks, 3 days ago by Linux User.

[Linux User]

I’ve been trying to install several custom roms including this one and always I face the camera issue. It lacks functions or it just disconnect or freezes and I have to turn off-on the phone. I have Galaxy S3 i9300 International model but I can’t figure how to solve this. I’ve also installed CM10, CM11 and CM12 with the same results. The phone is a beauty piece of hadware and I want to keep it two more years -at least- ;-)

[Linux User]

<pre id=”tw-target-text” class=”tw-data-text tw-ta tw-text-small” dir=”ltr” data-placeholder=”Traduzione” data-fulltext=””><span lang=”en” tabindex=”0″>Hi SIBA & CHRONO thanks to developing LineageOS for s3.

I tested version 15.1 and it worked great except for the useless PLAY STORE (I had to use UPTODOWN).

When I read your post I immediately tried 16.0.

Unfortunately, it starts transmitting the message right away
“THE BLUETOOTH APP CONTINUES TO BE DISCONTINUED”.
The app cannot be closed.

I try the LineageOS on s3 (purchased in 2013) just for fun.
 
I tried version 20190309 and lineage-16.0-20190411-UNOFFICIAL-i9300.zip
The result is the same.

Waiting for your reply, I send you my best regards.

Aldo Furlan</span>

 

 

[Linux User]

Sorry, but firmware is not working.
Bootloop.
Tested on Galaxy S3 Duos (i9300i)

Really waiting for the working version, thanks

• This reply was modified 1 week, 3 days ago by Linux User.