Hello guys,
i'm kind of desperate, because i really dont know where to search anymore, so i go ask now.
here are the sad facts:
i got a s4-clone, which should be hdc galaxy s4 lte with mt6589 processor. i bricked it (won't tell how, too retarded), do not have a recovery, but preloader still working. as i try to flash some random rom (as there are many for s4 clones with mt6589 ) using flash tool i always get the same error, telling me the rom is 6589 and target is 6572.
so the first guess is i got a different phone with mt6572 processor, but droidtools reads as follows:
Hardware : MT6589
Model : GT-I9502
Build number : JDQ39.I9502ZSUAMDF
Build date UTC : 20130705-144259
Android v : 4.2.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V1, 2013/06/29 17:32
Kernel v : 3.4.5 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP Fri Jul 5 22:40:30 CST 2013
i'm stuck at a very disappointing point, because i really dont know what to do anymore as there are no roms for mt6572 to try. does any of you professionals have a guess what to do now? (flash tool and droid tools are latest version)
iLike- said:
Hello guys,
i'm kind of desperate, because i really dont know where to search anymore, so i go ask now.
here are the sad facts:
i got a s4-clone, which should be hdc galaxy s4 lte with mt6589 processor. i bricked it (won't tell how, too retarded), do not have a recovery, but preloader still working. as i try to flash some random rom (as there are many for s4 clones with mt6589 ) using flash tool i always get the same error, telling me the rom is 6589 and target is 6572.
so the first guess is i got a different phone with mt6572 processor, but droidtools reads as follows:
Hardware : MT6589
Model : GT-I9502
Build number : JDQ39.I9502ZSUAMDF
Build date UTC : 20130705-144259
Android v : 4.2.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V1, 2013/06/29 17:32
Kernel v : 3.4.5 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP Fri Jul 5 22:40:30 CST 2013
i'm stuck at a very disappointing point, because i really dont know what to do anymore as there are no roms for mt6572 to try. does any of you professionals have a guess what to do now? (flash tool and droid tools are latest version)
Click to expand...
Click to collapse
I think your phone is mt6572...
Yes, no roms result when google, seem too hard to find the rom...
Its many type s4 clone, i think you dont know your phone model, like me...
Maybe you need search in china forum or ask to russian dev...
Hope you got lucky...
MY S4 SPEC :
Hardware : MT6572
Model : GT-i9500
Build number : JDQ39.I9500XXUAMDK
Build date UTC : 20130522
Android v : 4.2.2
Baseband v : MOLY.WR8.W1315.MD.WG.MP.V1, 2013/05/22 10:08
Kernel v : 3.4.5-526212 [email protected] #1 Tue Apr 23 23:00:57 KST 2013
With the rush of clone S4's available it would be impossible to safely flash your firmware...
You are stuck on whatever version of Android you have, be it gingerbread, ICS or Jellybean....
ok, i know noobish questions are not wanted here, but due to my noobishness and kind of intense research i have to ask: if i got a copy of masterofdarker's formware and i'd flash it except the preloader (as mine still works ) would there be the slight possibility of unbricking my phone??
Bricked MT6572
masterofdarker said:
I think your phone is mt6572...
Yes, no roms result when google, seem too hard to find the rom...
Its many type s4 clone, i think you dont know your phone model, like me...
Maybe you need search in china forum or ask to russian dev...
Hope you got lucky...
MY S4 SPEC :
Hardware : MT6572
Model : GT-i9500
Build number : JDQ39.I9500XXUAMDK
Build date UTC : 20130522
Android v : 4.2.2
Baseband v : MOLY.WR8.W1315.MD.WG.MP.V1, 2013/05/22 10:08
Kernel v : 3.4.5-526212 [email protected] #1 Tue Apr 23 23:00:57 KST 2013
Click to expand...
Click to collapse
Hi there, I'm a new member to the forum, but have been browsing XDA for some time.
I too have an S4 clone which I bought from a Chinese retailer through Amazon, and have bricked mine through a comedy of errors!
I can't remember which app I used to get the following, but this is the read-out from my device:
ALPS GT I9502
SYSTEM (Android 4.2.2)
Model: GT-I9502
Manufacturer: alps
Chipset: MT6572
Device: android_4x_wet_jb3
Product: android_4x_wet_jb3
Brand: GT-I9502
Android Version: 4.2.2 (Jelly Bean)
API Level: 17
Build ID: JDQ39
Fingerprint: GT-I9502/android_4x_wet_jb3/android_4x_wet_jb3:4.2.2/JDQ39/1377237676:user/test-keys
Click to expand...
Click to collapse
Does this look similar to anything in your device?
The only thing I think will work to get the device working again would be to get hold of the stock ROM, however I can't find one anywhere which matches the chipset.
I've heard that using the Android Kitchen, it's possible to create a new ROM using a dump of the "/system" from a working device; apparently using Terminal Emulator on the device and type the following:
Code:
tar -c system/* >> sdcard/system.tar
Is that correct? If so, if anyone recognises the above specs on their own device, I would be really grateful for any help. Obviously being a new member I'm not expecting anyone to start sending me a dump of their "/system" (!) but any help would be much appreciated!
Thanks in advance
hi guy. help me Model : GT-I9500 Build number : TY_V1
i have i9500 clone. i have restart problem. device is always 10-15 minutes for restart. it's big problem. i want help.
Hardware : MT6589
Model : GT-I9500
Build number : TY_V1
Build date UTC : 20130911-091656
Android v : 4.2.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V1.P3, 2013/07/30 19:22
Kernel v : 3.4.5 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP Tue Sep 10 01:18:33 CST 2013
Uboot build v : ----- should be root shell
LCD Driver IC : 1-otm9608a_qhd_dsi
try this tutorial http://forum.xda-developers.com/showthread.php?t=2656547
can I have the link for rom of my clone s4 alps i9502
jdq39.i9500zsuamdf?
iLike- said:
Hello guys,
i'm kind of desperate, because i really dont know where to search anymore, so i go ask now.
here are the sad facts:
i got a s4-clone, which should be hdc galaxy s4 lte with mt6589 processor. i bricked it (won't tell how, too retarded), do not have a recovery, but preloader still working. as i try to flash some random rom (as there are many for s4 clones with mt6589 ) using flash tool i always get the same error, telling me the rom is 6589 and target is 6572.
so the first guess is i got a different phone with mt6572 processor, but droidtools reads as follows:
Hardware : MT6589
Model : GT-I9502
Build number : JDQ39.I9502ZSUAMDF
Build date UTC : 20130705-144259
Android v : 4.2.2
Baseband v: MOLY.WR8.W1315.MD.WG.MP.V1, 2013/06/29 17:32
Kernel v : 3.4.5 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP Fri Jul 5 22:40:30 CST 2013
i'm stuck at a very disappointing point, because i really dont know what to do anymore as there are no roms for mt6572 to try. does any of you professionals have a guess what to do now? (flash tool and droid tools are latest version)
Click to expand...
Click to collapse
Be careful with the preloader part!
need system.apk and system.odex of this rom who can post
Please send me system.apk file need from this rom urgent thanks
Please post
Hello - Unofficial phone so I respect that you may not want to or can't help me.
This is a copy phone, looks and works just like the real thing but is not the real thing. Not sure what hard/software is different to a real one.
Model
GT-I9500
Android Version
4.2.2
Kernel 3.0.13
1313 V75
SMP PREEMPT Wed Sep 25 09:48:20 CST 2013
Build number
JDQ39.I9500ZHUAMDE
Custom build version
1378866812
If I hold Vol Up and Power I can boot into some kind of system test.
If I hold Vold Down and Power I get "android system recovery <3e>" with the options to Install from SD
Tests tell me that the phone is not rooted but is custom/not true stock.
-- I wonder if it is safe to try and root this phone?
-- Does anyone have experience with fakes? Any caveats when rooting/flashing?
-- Am I right to be suspicious that this ROM would have some spyware in it as this is my strongest motivation to get root and install a ROM I trust.
Thanks if you can help! :laugh:
Hi, I have been attempting to unlock the QUALCOMM US Boot-loaders, and have been able to find flags In the ODIN boot-loader files.
EDIT: got some "keys"
ANY DEVS PARTCIPATING, Sign your packages with one of these
-ffffffffffffffffffffffffffff16a2e0b8f03e13dd29455c5c2a3d
-5ac635d8aa3a93e7b3ebbd55769886bc651d06b0cc53b0f63bce3c3e27d2604b
-6b17d1f2e12c4247f8bce6e563a440f277037d812deb33a0f4a13945d898c296
-4fe342e2fe1a7f9b8ee7eb4a7c0f9e162bce33576b315ececbb6406837bf51f5
-ffffffff00000000ffffffffffffffffbce6faada7179e84f3b9cac2fc632551
-b3312fa7e23ee7e4988e056be3f82d19181d9c6efe8141120314088f5013875ac656398d8a2ed19d2a85c8edd3ec2aef
-3617DE4A96262C6F5D9E98BF9292DC29F8F41DBD289A147CE9DA3113B5F0B8C00A60
---------------------------------
Also, another interesting part in keymaster.mbn was
KEYMASTER_SECURE_WRITE_PROTECT
0123456789ABCDEFkeymaster
da9008f709
-------------------
all flags from devcfg.mbn are
keystore_retain_wrong_passwd_attempt
OEM_counter_enable_rpmb
OEM_allow_rpmb_key_provision
OEM_disable_rpmb_autoprovisioning
OEM_sec_wdog_bark_time
OEM_sec_wdog_bite_time
OEM_reset_reason_list
OEM_l2_wa_enable
OEM_rot_enable_transfer_APPS
OEM_rot_enable_transfer_MODEM
OEM_rot_pk_hash1_fuse_values
OEM_pil_secure_app_load_region_size
OEM_pil_subsys_load_region_start
OEM_pil_subsys_load_region_size
OEM_disable_secure_app_pimem
client_00
client_01
client_02
client_03
client_04
client_05
client_06
client_07
cmnlib_gppo_rpmb_enablement
cmnlib_gppo_root_path license_data_store_path
proprietary_play_enabler_video_protect
proprietary_play_enabler_default_behaviour
IV_constraint robustness_version
proprietary_play_enabler_profile
proprietary_opl_profile_0
disable_security_stream_check provision_constraint_flag
use_legacy_hdmi_hdcp_check
get_IV_constraint
maximum_hdcp_2x_capability
enable_kcb_logging_flag
hdcp1_storage_type
chamomile_ips
hdcp2p2_storage_type
chamomile_ips_hdcp2p2
kernel_version
kernel_version_str_length
challenges
challenges_array_length fpta_name
gk_timeout_config
QFPROM_rail_id
QFPROM_rail_type
pam_qfprom_rail
ddr_rail_reg
arb_priority_cfg
number_priorities
number_pvc_port
pvc_port_cfg spmi_channel_cfg
spmi_channel_cfg_size
tz_mpu_rg_cfg
rg_cfg_size
pmic_arb_hal_id_xpu
spmi_rg_config
blsp_spi_mosi[6]
blsp_spi_miso[6]
blsp_spi_cs_n[6]
blsp_spi_clk[6]
blsp_spi_mosi[5]
blsp_spi_miso[5]
blsp_spi_cs_n[5]
blsp_spi_clk[5]
blsp_spi_mosi[1]
blsp_spi_miso[1]
blsp_spi_cs_n[1]
blsp_spi_clk[1]
blsp_spi_mosi[7]
blsp_spi_miso[7]
blsp_spi_cs_n[7]
blsp_spi_clk[7]
blsp_spi_mosi[11]
blsp_spi_miso[11]
blsp_spi_cs_n[11]
blsp_spi_clk[11]
blsp_i2c_sda[1]
blsp_i2c_scl[1]
blsp_i2c_sda[2]
blsp_i2c_scl[2]
blsp_i2c_sda[3]
blsp_i2c_scl[3]
blsp_i2c_sda[4]
blsp_i2c_scl[4]
blsp_i2c_sda[5]
blsp_i2c_scl[5]
blsp_i2c_sda[6]
blsp_i2c_scl[6]
blsp_i2c_sda[7]
blsp_i2c_scl[7]
blsp_i2c_sda[8]
blsp_i2c_scl[8]
blsp_i2c_sda[9]
blsp_i2c_scl[9]
blsp_i2c_sda[10]
blsp_i2c_scl[10]
blsp_i2c_sda[11]
blsp_i2c_scl[11]
blsp_i2c_sda[12]
blsp_i2c_scl[12]
blsp1_spi_cs1_n
tlmm_gpio_test_pin
tlmm_base tlmm_offset
tlmm_total_gpio
mst_pd
mst_md
gcc_blsp1_ahb_clk gcc_blsp1_qup5_spi_apps_clk
"fidocrypto" "" "/efs/" "/data/misc/qsee/" "/data/misc/qsee/" "Linux version 3.14.26-g43b1178-00038-g96ef344 ([email protected]) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Jun 5 15:15:57 PDT 2015" authhat
-----------
the most interesting was
-OEM_rot_pk_hash1_fuse_values
as in the efuse value?
I would really love for some people to give some support
I will give these files as-is or I can give as raw text.
Edit: these flags are based off of QA6
Edit2: I wonder if we could find a dev with the Qualcomm version of the s7 (china), grab the Odin files, (AP,BL,CP) (flash your own csc carrier) and use CROM SERVICE
Devman-0903 said:
Hi, I have been attempting to unlock the QUALCOMM US Boot-loaders, and have been able to find flags In the ODIN boot-loader files.
all flags from devcfg.mbn are
keystore_retain_wrong_passwd_attempt
OEM_counter_enable_rpmb
OEM_allow_rpmb_key_provision
OEM_disable_rpmb_autoprovisioning
OEM_sec_wdog_bark_time
OEM_sec_wdog_bite_time
OEM_reset_reason_list
OEM_l2_wa_enable
OEM_rot_enable_transfer_APPS
OEM_rot_enable_transfer_MODEM
OEM_rot_pk_hash1_fuse_values
OEM_pil_secure_app_load_region_size
OEM_pil_subsys_load_region_start
OEM_pil_subsys_load_region_size
OEM_disable_secure_app_pimem
client_00
client_01
client_02
client_03
client_04
client_05
client_06
client_07
cmnlib_gppo_rpmb_enablement
cmnlib_gppo_root_path license_data_store_path
proprietary_play_enabler_video_protect
proprietary_play_enabler_default_behaviour
IV_constraint robustness_version
proprietary_play_enabler_profile
proprietary_opl_profile_0
disable_security_stream_check provision_constraint_flag
use_legacy_hdmi_hdcp_check
get_IV_constraint
maximum_hdcp_2x_capability
enable_kcb_logging_flag
hdcp1_storage_type
chamomile_ips
hdcp2p2_storage_type
chamomile_ips_hdcp2p2
kernel_version
kernel_version_str_length
challenges
challenges_array_length fpta_name
gk_timeout_config
QFPROM_rail_id
QFPROM_rail_type
pam_qfprom_rail
ddr_rail_reg
arb_priority_cfg
number_priorities
number_pvc_port
pvc_port_cfg spmi_channel_cfg
spmi_channel_cfg_size
tz_mpu_rg_cfg
rg_cfg_size
pmic_arb_hal_id_xpu
spmi_rg_config
blsp_spi_mosi[6]
blsp_spi_miso[6]
blsp_spi_cs_n[6]
blsp_spi_clk[6]
blsp_spi_mosi[5]
blsp_spi_miso[5]
blsp_spi_cs_n[5]
blsp_spi_clk[5]
blsp_spi_mosi[1]
blsp_spi_miso[1]
blsp_spi_cs_n[1]
blsp_spi_clk[1]
blsp_spi_mosi[7]
blsp_spi_miso[7]
blsp_spi_cs_n[7]
blsp_spi_clk[7]
blsp_spi_mosi[11]
blsp_spi_miso[11]
blsp_spi_cs_n[11]
blsp_spi_clk[11]
blsp_i2c_sda[1]
blsp_i2c_scl[1]
blsp_i2c_sda[2]
blsp_i2c_scl[2]
blsp_i2c_sda[3]
blsp_i2c_scl[3]
blsp_i2c_sda[4]
blsp_i2c_scl[4]
blsp_i2c_sda[5]
blsp_i2c_scl[5]
blsp_i2c_sda[6]
blsp_i2c_scl[6]
blsp_i2c_sda[7]
blsp_i2c_scl[7]
blsp_i2c_sda[8]
blsp_i2c_scl[8]
blsp_i2c_sda[9]
blsp_i2c_scl[9]
blsp_i2c_sda[10]
blsp_i2c_scl[10]
blsp_i2c_sda[11]
blsp_i2c_scl[11]
blsp_i2c_sda[12]
blsp_i2c_scl[12]
blsp1_spi_cs1_n
tlmm_gpio_test_pin
tlmm_base tlmm_offset
tlmm_total_gpio
mst_pd
mst_md
gcc_blsp1_ahb_clk gcc_blsp1_qup5_spi_apps_clk
"fidocrypto" "" "/efs/" "/data/misc/qsee/" "/data/misc/qsee/" "Linux version 3.14.26-g43b1178-00038-g96ef344 ([email protected]) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Jun 5 15:15:57 PDT 2015" authhat
-----------
the most interesting was
-OEM_rot_pk_hash1_fuse_values
as in the efuse value?
I would really love for some people to give some support
I will give these files as-is or I can give as raw text.
Edit: these flags are based off of QA6
Edit2: I wonder if we could find a dev with the Qualcomm version of the s7 (china), grab the Odin files, (AP,BL,CP) (flash your own csc carrier) and use CROM SERVICE
Click to expand...
Click to collapse
Look guys, I know things look bad for the QUALCOMM variants, but with a good team of devs, we can do this! I'm tired of this crap that our OEM'S give us.
Stuff is too advanced for me but seems like some good ideas. I agree, we can do it if we work as a team.
I'm not a developer but, let me know how I can help. Can do basic odin flashes and such.
I wouldove to help in anyway I have been wanting this phones bootloader unlocked for a while now. I have the Sprint variant SM-G935P. please contact me.
There isn't a lot of info here, but this might be a lead.
http://google.com/newsstand/s/CBIwvuP0_Tk
Now we are getting somewhere, Let's attempt use bootstomp on 6.0.1 odin files all the way up to the latest 7.0
I would be glad to help and do some research, i dont know too much lingo but I can figure it out
@Devman-0903 , we can't use China's firmware, different partition sizes :/
Hi,
this is my first post here on XDA Developers and I'm new to Android. This HU is my first device with Android for my Smart car.
So I bought this unit from Aliexpress.
Model: PX5
Android Version: 9
Build: rk3368-userdebug 9 PQ2A. 190305.002 20190628.103151 test-keys
Kernel Version: 4.4.167 ....... #98 Thu Jan 27 17:21:19 CST 2019
MCU Version: MTCE_GS_V3.17_3 ....... Jun 21 2019 20:14:31
CPU: Octa-Core Cortex-A53 @ 1.5 G
RAM: 4 GB
So my biggest goal is to get rid of ads in Youtube. I tried Lucky Patcher but it requieres Root access. So I googled a bit and found out about Kingroot and installed it. After installation rooting my device failed. I also tried a how-to from this forum LINK but when I open 1. Disable DM-Verity.bat and enter my IP it always says "Disable DM-Verity...error: device '(null)' not found". I don't know what to do here.
Further I want to get the latest update on this HU. After I install it in my car I don't want to take it out anymore to experiment. What I need to download? I saw here some CFW but I don't know yet if they fit my device. Is there any recommended firmware I can put on this HU?
I do some research in the meantime to aquire more knowledge but this first questions would help me very much. Thank you very much for taking some time <3
Hello, i have an old android car device and i updated it because it became very slow and i couldn't use it anymore... But it seems i put wrong firmware, now its working faster but the problem is that the resolution is not correct and it cut off the screen. The problem is that i don't have much information for the device, i tried to put many different firmwares but i get the same error message: "Fail, please check usb and files" This is the information that i have:
before the update:
Model:
8227L
Android version:
9
Kernel version:
3.18.79 (gcc version 6.3.1.20170404 (Linaro GCC 6.3-2017.05)) [email protected]#72
Full_8227L_demo-userdebug 9 011019 1550112051 userdebug
Custom build version:
alsps-mo-o1.mp5
And the screen shots are after the update. I tried to update it trough the both usb ports but it didnt work, should i try to do it trough the SD card? If someone has similar device or problem please let me know if you have any solution, also if you have the right firmware. The pictures are after the update. Also i cant find much information about the device because i bought it 4 years ago..