Hi,
This thread will be devoted for presenting known info on WP7.
Please do not post here, but post your [Q] here:
http://forum.xda-developers.com/showthread.php?t=876463
Regards. ansar.
No 1
How to identify your inital ROM version:
Suppose you see in the about screen this:
******************************************
Firmware revision number: 2250.09.10906.162
Hardware revision number: 0003
Radio software version: 5.50.09.15_22.23.50.09U
Radio hardware version: A.102.0.D4
Bootloader version: 1.9.2250.6(111329)
Chip SOC version: 2.2.5.0
******************************************
Then your initial ROM version is something like this:
RUU_DeviceName_Operator_1.09.162.06_DeviceName1_5.50.09.15_22.23.50.09U_RELEASE.exe
Where:
DeviceName is: Schubert,Mozart,Spark,Surround etc.,
DeviceName1 is: missing or as above.
Operator is: Europe, TMO_DE, TMO_AT, HTC_Generic, Telsta_WWE etc
The radio is straigthforward.
The firmware version must be rearranged as follows:
these last digits .10906.162 to 1.09.162.06
End of No 1
Post #2
Post #2 is for future use
Post #3
Post #3 is for future use.
Post #4
Post #4 is for future use.
Post #5
Post #5 is for future use.
ansar, why do you make these useless threads?
indiekiduk said:
ansar, why do you make these useless threads?
Click to expand...
Click to collapse
instead of demoralizing those who contribute, its better to be quiet, yes?
itje said:
instead of demoralizing those who contribute, its better to be quiet, yes?
Click to expand...
Click to collapse
normally yes, but this particular user is confusing everybody but saying something is possible when it isn't.
Its more for future usage then right now. But all this will come in handy...u'll see (perhaps )
What rom to use?
Phone information
name: HTC 7 Trophy T8686
Model: HTC 7 Trophy T8686
Firmware revision: 2250.09.10908.401
Hardware revision: 0003
Radio: 5.54.09.21_22.33b.50.10U
Radio hardware: A.102.0.D4
Bootloader: 1.20.2250.0(117833)
chip soc: 2.2.5.0
I'd like to flash it so i can unlock with chevron WP7 and then update with 7390 again.
my phone is not operator locked but i am using it in sweden
Well, hello and good day to all of you!
I'm a new guy here at the forums by the way, I need help or instructions on how to root this particular Spreadtrum smartphone I just recently bought two days ago.
I tried searching the forum and found some similar or related threads, but I'm not quite taking the risk in following those threads without asking someone with the knowledge about this phone... I was even shocked to know that some Spreadtrum powered phones are not really an ICS device. XD
So anyway, here are the specs:
Model Number: SKK A6 (re-branded company/device name)
Android Version: 4.0.4 (?)
Baseband Version: DM_BASE_12A_W12.32
Kernel Version: 2.6.35.7 [email protected] #5
Software Version: MocorDroid 2.3.5.W12.20_P0_20130506.11023
Hardware Version: 1.1.0
Any help would be appreciated, thanks!
Just to bump this thread, added info, I accessed the factory test mode and did a full phone test:
Can't really make up what's the rest written, the screen is too small to display it:
sprdroid_base-user 2.3.5 MocorDroid 2.3.5.W12.20_P0_20130506.11023
3PlatformVersion: MOCOR_880X (screen is to small too display the rest of this info)
W12.43_P1_Debug Project Version
20_modem$BASE Version: DM_B (again too small to display the rest of the information)
W12.43 HW Version: SC682 (?? and again, to small too display the rest)
(I'm assuming the next following lines is the modified firmware of the rebrander company
11-02-2012 17:53:08CUSTOM Version
RWF-SKK.20120506.B02V10
SN1:
SN2
This thread is intended to collect the MCU and ROM Updates for the different MTCD Headunits (Not Joying) based on the Sofia 3230RK (X3) Intel+RockChip SoC.
Many users are buying their headunits and the information between MTCD and Joying (non MTCD) is mixed.
Information about the processor is presented by [email protected] on the following thread:
https://forum.xda-developers.com/an...t/intel-cpu-mtcd-mtc-units-intel-cpu-t3494083
Other thread for Intel Sofia Units (Joying and MTCD) is:
https://forum.xda-developers.com/an...opment/2gb-ram-intel-cpu-heres-specs-t3468322
This Unit is an upgrade of the MTCD based on RK3188 Chipset.
It has been released on late 2016 and it seems to be the MTCD standard (lollipop 5.1.1) prior to manufacturers upgrade to the new PX5 platform
The unit consists on two parts:
MCU board, which controls physical buttons and A/V inputs/outputs to/from the headunit. This board interacts with Android OS.
ANDROID part. The main Operating System.
Both MCU and Android ROM interact together to achieve the functionality of the unit
Joying Intel Sofia Units are not supported in this thread as they have different MCU type, and, therefore, the Android part will be customized as well to interact with that MCU
When an update is released two files are provided:
The Android ROM (update.zip file)is based on Lollipop 5.1.1 and it is common for all the MCTD Sofia Units
the MCU (dmcu.img) is specific for each manufacturer and it should never be updated with other manufacturer mcu update file (unpredicted response from physical buttons - or CAN bus responses, or bricking the unit)
Manufacturers.
The Manufacturer is identified by the XXX when consutling the device information [MTCD_XXX_Version]:
e.g: MTCD_HA_1.93_1 (MTCD Unit with MCU for HOtAudio under 1.93_1 version)
Known manufacturers for MTCD Intel Sofia are:
HotAudio --> HA
???????? --> HXD
BonRoad--> HCT
Erisin/Pumpkin --> LM
Xtrons --> GS
(this list will be updated according to users report new manufacturers)
MTCD Unit Types
All units are close the same. Only physical buttons or added functionalities by external CAN bus decoder (provided by the manufacturer) can differenciate them. Two main different types are identified:
MTCD Sofia Intel units with WIFI Only (not 3G built in - SIM slot) - called sofia3grw
MTCD Sofia Intel units with 3G built in - SIM slot and 3G Antenna - called sofia3gr
Roms for WIFI version can´t be installed onto Headunits with Built in 3G and viceverse. Initially the updating script detects which version of headunit is installed and aborts the installation. A script modification can be done to force the update, but it has been reported that RIL and BASEBAND is missing (3G capability is lost) if WIFI version ROM is forced to update over 3G built in headunit (rest of the funcionality is not affected)
Android ROM Updates.
The following links provide the update for the Android part of the system. The file shall be renamed to update.zip. NOrmally the links below contains both Android ROM and MCU updates. Be careful to not use the dmcu.img file if you are not sure that it fits to your headunit's manufacturer.
September 22th 2016:
WIFI --> https://drive.google.com/file/d/0Bz8umNL1qrsoTDcwX1ViMG1BbFU/view
3G --> N/A
October 21th 2016:
WIFI -->http://mail.qq.com/cgi-bin/ftnExs_d...4d4a574b357e&t=exs_ftn_download&code=9549cc86
3G --> http://mail.qq.com/cgi-bin/ftnExs_d...16145541637d&t=exs_ftn_download&code=74f8f43c
December 20th 2016
WIFI --> https://mail.qq.com/cgi-bin/ftnExs_...50a52151646500747061d4f0a46345b&code=f3c35c64 or https://drive.google.com/open?id=0B5k39tJWUEHIMFFuVTdXSThNSzA
3G --> https://www.dropbox.com/s/fw2ghw8m4f6nvun/update 20161220.zip?dl=0 (Source: Pumpking. Thanks @sorinblu)
January 3rd 2017
WIFI --> N/A
3G --> https://drive.google.com/file/d/0B6c7wyyjyJofNlB1U0VFOG91aUE/view?usp=drive_web [Source: HotAudio. Thanks Mr.Yuan (@hotaudio)]
March 2nd 2017
WIFI --> N/A
3G --> https://mega.nz/#!RdkTADJa!_7dmoYNMMC-BfyQUqfvM8zLWGV9B0_Gf2HR-kI_2ZxU [Source: Pumpkin. Thanks (@manderson77)]
March 28th 2017
WIFI --> N/A
3G --> https://mega.nz/#!BRsC1TrL!I9DMTHJzfso3GlPtEGy7iMCvFLVPESrgAHfntdHi_uo [Source: Pumpkin. Thanks (@manderson77)]
April 24th 2017 --> MARSHMALLOW!!!
WIFI --> N/A
3G --> https://www.sendspace.com/pro/dl/3wj088 [Source: Dasaita. Thanks (@hotaudio)]
MCU Updates.
The following links provide the update for the MCU board. The file shall be renamed to dmcu.img
HA --> Date: ?????? Version: 1.97: https://mega.nz/#!Q8YQjYTY!qZxma-VF3HQXlN0yklxWaNZFPH9tdYRzeHcF9sNdm8g
HA --> Date Feb 27, 2017 Version 2.30: https://mega.nz/#!xxhjySaB!qoAYJBPv4cKsAOviU4QtE8W-Ys7k5XEo6CtcLdoQxp0
HXD --> Date: ????? Version: 2.05: https://drive.google.com/open?id=0BzpR8k0kgZq3Y1ZoTW53VVo4OWM
HXD --> Date: ????? Version: 2.15: https://yadi.sk/d/zbHCpME33HgJsQ
LM --> Date: Dec, 17, 2016 Version: 2.04: https://www.dropbox.com/s/naqrfnjzf2yubh0/LM_12-17-16_v2.04_1dmcu.img?dl=0
LM --> Date: Feb, 28, 2017 Version: 2.30_2: https://mega.nz/#!Fc1DHDgJ!SzSj01-uwRumYAlJ-mTWZpwPwXz-TqDd1QFL3Qq5o6g
LM --> Date: March 2017, Version: 2.41_1: https://mega.nz/#!dQdkiDQR!PeaZO5QSrG7L-755GWUwlMsuxnbB85WHZK3C-lr52Eo
GS -->
Date: ? Version: 1.87_2:
Date: ? Version: 1.93_1:
Date: Dec 23, 2016. Version: 2.04: https://mega.nz/#!st4xFarS!kKV_-CqvWB19jmSS3gGb0Rfhbj-guQx6C_hPi2szDjM
HCT --> Date: ? Version: ?
HXD -->
Date: Jan 23, 2017. Version: 2.05: https://mega.nz/#!YxpiVIJQ!hQDMiUEOsAbVtxbDNw8ndDyFGHcazapcQTaVzt5s3Kg
Erisin ES3092Y
http://www.erisin.com/erisin-es3092...d-51-os-car-gps-sat-nav-dab-3g-wifi_p726.html
ANDROID ROM CHANGELOG
(this changelog will be updated as new releases were found)
Magenta versions are those included in repository (OP)
20160910
* Separate the Bluetooth music and Bluetooth applications
* Remove the system default music application in addition to preview part of the application UI
* Remove the side control learning is not practical key learning, optimization of the non-functional keys can not learn
* Remove the system with their own input method desktop shortcut
* Status bar Bluetooth icon policy optimization
* Fixed Music4 autoplay lock time to 8 seconds
* Modify the audio policy BUG
* Repair the Bluetooth music playback pause state to get too slow strategy
* Update the GPS patch
* Remove the side control learning inside the voice and intercom icon
* Added a third-party button to confirm the key support up and down
* power amplifier mode to increase the touch area
* the control settings
* the factory set the default length of other models increased
* prevention and control, touch, panel learning to change the volume of a single learning
* canbus05 update
20160921
* factory setting plus encoder knob mode
* change the main interface Bluetooth music Click to enter the Bluetooth application
* to solve the Bluetooth music interface switch does not return to the Bluetooth interface after the ACC problem;
* update the kernel, MtcManager on switch machine strategy
* handle the download phone book when the cancellation of mobile phone side caused by abnormal restart vehicle;
20160922
* update the camera driver, AVIN and driving records at the same time running off ACC and then turn on driving record does not start
* Radio RDS display incomplete BUG
20160923
* KERNEL modified ADV7180 some chip initialization identification BUG, ??CVBS may not be able to show some of the conditions are improved
20160926
* update wing card software;
* update the mobile Internet software;
* Fixed radio rds psn problem
* Add canbus96 Beiqi Shenbao (wisdom City)
20160928
* update the mobile Internet software;
20160929
*GPS patch restore back to August 31 state ?
20160930
*Factory setting other prohibited to enter the reversing screen to be V1.91 version of the above mcu
20161010
* canbus21 Yan flutter Honda agreement
* TV touch bias
* to optimize the browser to close wifi 3g Internet access problems
20161017
* GPS patch optimization search star problem
20161019
* modify the default power settings factory boot volume
20161021
* update the Bluetooth phone book Bug;
* in the choice of GPS applications to increase the selection of driving assistant map navigation;
* canbus
20161027
* factory settings increase usbdvr and cvbsdvr hidden display
* avin Audio mode through mcu configuration
20161028
* steering wheel control to increase voice wake-up, intercom learning;
20161101
* Factory settings and amplifier volume and dvr settings and mcu v1.95 and above to upgrade the role of Kai
* canbus 81
20161102
*Update canbus81 increase 97 surging Mercedes-Benz agreement 98 Chery City Chery agreement
20161104
*Factory Settings Translation
*Modify AVIN focus issues;
*Steering wheel control to increase voice wake - up, intercom learning;
20161109
*Off acc memory navigation problem
*Canbus
*Modify the Bluetooth can download the card inside the phone book information;
20161112
*Factory default password to 3333 only show the logo settings
20161115
* touch auxiliary function will be added to the system comes with settings, Settings -> Display -> touch support
20161117
* canbus
* the factory settings mcu configuration hidden logo
20161118
* modify the public version of the audio BUG
* Factory settings BUG repair
20161123
* off AC off B + off in the AC does not remember the problem
* optimization of low temperature Huaping
20161125
* Sofia important update RK, to solve the very few cases of panic and camera crashes,
20161128
* Resolve CVBS in some cases synchronization loss, resulting in the screen flash BUG
20161130
* The last version can not solve the standby problem
20161201
* SOFIA standby timing adjustment
20161207
* Add the patch optimization card logo
* Update recovery
20161217
* Exit reversing flash about the problem
* Update google play
20170103
* Update Google Pack 20161220
* Update HCTCarTouch
* Canbus
Root and Other Stuff
MTCD Intel Sofia Units Rooting Methods: METHOD1
The easiest way to root our units is by using an update.zip file. It will be detected by the unit as a normal update.
This file injects the root privileges into the boot partition.
boot.img is being used, modified and reinstalled onto the Headunit, so it is recommended to use the same boot.img as was into the non rooted system.
I have prepared some root files for both 3G and WIFI units using differents boot.img files (extracted from different ROMs - they shall be renamed to update.zip prior copied into the USB/SD).
EDIT -> root update.zip file only can be installed from recovery menu.
To enter into recovery menu:
* Press reset button and hold until you see the button lights blinking (10 secs approx.)
* Release and press again until you see the lollipop logo
* Release and wait to the recovery menu.
Once into recovery, use the reset button for:
* Move along the options (short press)
* Select an option (long press)
Sofia3gr (3G version):
Based on boot.img from October 2016 ROM: https://drive.google.com/open?id=0BzpR8k0kgZq3c08teWJJbHpqLVE
Based on boot.img from December 2016 ROM: https://drive.google.com/open?id=0BzpR8k0kgZq3eUp4c0F3dV9Hd28
Based on boot.img from March 2017 ROM: https://drive.google.com/open?id=0BzpR8k0kgZq3bTlDdG5Qc2ZoNDA
Sofia3grw (WIFI only version):
Based on boot.img from September 2016 ROM: https://drive.google.com/open?id=0BzpR8k0kgZq3bkdhMFdyQ2lSbTA (the one published on the russian forum)
Based on boot.img from December 2016 ROM (latest): https://drive.google.com/open?id=0BzpR8k0kgZq3U1RjMThZSFhHZlk
MTCD Intel Sofia Units Rooting Methods: METHOD 2
This Method is by using adb over WIFI. This has been reported to work under New Android 6.0.1 ROM
Instructions:
In Android:
1) Download "Terminal" apk from Google Play
2) Open Terminal and put the following commands:
su
setprop persist.adb.tcp.port 5555
In PC:
3) Download the zip file from this post
4) Decompress the zip on a folder of your Hard Disk
5) execute CMD in Windows
6) Go to that folder and put the following command: install xxx.xxx.xxx.xxx
(xxx.xxx.xxx.xxx is the IP of your HeadUnit under the same WIFI as your PC)
Wait for the Succeed Message
7) Reboot your Unit
Differences between 3G version and WIFI only version ROMS
According what i have seen, only differs on the default.prop file. This file can not be edited into the installed ROM, as it is part of the boot and, even edited (i.e with root explorer), once rebooted, the file will be reverted to the original state, as it is written into the ramdisk.
MTCD Intel Sofia Units TWRP
On Russian 4Pda forum (Thanks InvisiBot & Lemegor) have built a compatible TWRP 2.8.7.0 for our Units. I have semi-translated the previously google translated russian text and included the attachments (thanks @lemlY):
TWRP is available in two versions:
Temporary - TWRP uncompressed onto a ramdisk (in memory) over the stock recovery. It is a relatively safe option, TWRP disappears after a reboot;
Permanent - TWRP is replacing stock recovery.
Installation known Issues:
As a result of testing, after a number of installations in a few days, it has been found that during the installation of the zip-file with TWRP (temporary or permanent) the unit can enter in a freeze state.
In the case of freezing when you try to install the Temporary TWRP, you need to remove the stick and interrupt the power (which may already be for someone to challenge).
In the case of freezing during installation of permanent TWRP , after the restart noted that the partition recovery is inoperable.
If hung but loaded into Android, the recovery partition can attempted to be restored by using the dd method (see below)
If hung and not loaded into Android, you may get broken in bootloop recovery. The only solution to restore the device may be achieved only by soldering hub (to 27 & 28 pin) to the Headunit be detected by Computer USB and then flash firmware via FlashToolE2 .
Flasher Program (FlashToolE2) --> https://drive.google.com/open?id=0BzpR8k0kgZq3eWhXZHdjNDEzSlU
Recovery Flash for Sofia 3GRW (WIFI) --> https://drive.google.com/open?id=0BzpR8k0kgZq3TEpSeG9Na0RJQ0E
Recovery Flash for Sofia 3GR (3G) --> NOT AVAILABLE
After a successful install of TWRP, it works fine .
Perhaps a more reliable version of the installation - is flashing TWRP / recovery using dd from under Android:[/B]
adb connect ip-address-HU
adb root
adb shell "dd if = / mnt / usb_storage3 / = recovery.img of / dev / block / mmcblk0p10"
TEMPORARY TWRP
* Sofia 3GR 2.8.7.0 --> https://drive.google.com/open?id=0BzpR8k0kgZq3QTdLQzNBXzVTNlE
* Sofia 3GRW 2.8.7.0 --> https://drive.google.com/open?id=0BzpR8k0kgZq3YTNxU2JrUy1xd1U
PERMANENT TWRP
* Sofia 3GR 2.8.7.0 -->
* Sofia 3GRW 2.8.7.0 -->
IMPORTANT!!
All this process has been tested on WIFI version of units. Files can't be interchanged between 3GR & 3GRW because of different electronics.
After TWRP , the MCU upgrade will no loger works. In case of needed to upgrade the MCU, you can go back to stock recovery:
* Sofia 3GR Stock Recovery --> https://drive.google.com/open?id=0BzpR8k0kgZq3NVJPNnEzY1lfY1E
* Sofia 3GRW Stock Recovery --> https://drive.google.com/open?id=0BzpR8k0kgZq3RnZLc0ZpTmM2QkE
MTCD Intel Sofia Units 3GR vs 3GRW
default.prop differences are shown on the following image (left=WIFI; right=3G)
Tools for Our MTCD Intel units
Developing Tools
Update.zip has some files inside:
Boot.img --> contains the boot partition data. In this partition is injected the SuperSU for granting Rooting
system.new.dat --> contains the Android System data (all apps and everithing)
fwu_image.bin --> Not sure about this file... it seems to be related with some kind of fastbooting.
A) Android Image Kitchen v2.32 --> To pack/unpack partition images (boot.img)
B) Auto Tool v3.0 x64 --> To pack/unpack System ANdroid images (system.new.dat)
All the packages included in ROM (system.new.dat) are odexed. It contains the apk file (style of application) and a .odex file (with the operation code of the app) inside a "x86" folder
in order to get the source code for any package:
1) Unpackage the system.new.dat included on update.zip by using Auto Tool v3
2) look for your package to be studied (located on "\system_\app\PackageName" or on "\system_\priv_app\PackageName")
3) deodex the file (located on "..\PackageName\x86" (convert .odex to dex). this can be achieved with oat2dex.jar included on BackSmali package
4) Get the Java File (.jar) from dex File with dex2jar package (included on dex-tools-2.1)
(e.g. d2j-dex2jar MTCManager.dex will create a MTCManager-dex2jar.jar file
5) you can decompile the jar file to a human readable java format by jd-GUI package
UPDATE: Here you can find a decompiled version for all MTCXXXX apps for any debug/investigation purpose. They are in smali format.
https://drive.google.com/open?id=0BzpR8k0kgZq3cFFsczB0bS1vTWs
According to some screenshots posted by [email protected], the BonAudio MCU is MTCD_HCT_xxxx.
I'm very interested in getting a BMW E46 version of these units - MTCD with Intel processor. From what I have read the Bluetooth on these is available to android, and not restricted by the MCU.. this would solve many Bluetooth issues - hopefully these will be able to pair with devices that have a Bluetooth pin code.
gumanov said:
According to some screenshots posted by [email protected], the BonAudio MCU is MTCD_HCT_xxxx.
I'm very interested in getting a BMW E46 version of these units - MTCD with Intel processor. From what I have read the Bluetooth on these is available to android, and not restricted by the MCU.. this would solve many Bluetooth issues - hopefully these will be able to pair with devices that have a Bluetooth pin code.
Click to expand...
Click to collapse
These MTCD intel can pair with any bluetooth device (including those with PIN code)....there is an option to select the PIN prioir to pair the devices
ikerg said:
These MTCD intel can pair with any bluetooth device (including those with PIN code)....there is an option to select the PIN prioir to pair the devices
Click to expand...
Click to collapse
Is it similar to an android phone with a pop up message asking for the pin? Or is it like my MTCC unit where you can set a default unit pin in the Bluetooth settings page?
gumanov said:
Is it similar to an android phone with a pop up message asking for the pin? Or is it like my MTCC unit where you can set a default unit pin in the Bluetooth settings page?
Click to expand...
Click to collapse
Like mtcc. You set a default pin. I have a icar3 obd2 bt paired that handles a 1234 pincode running perfectly with torque and dashcommand
Enviado desde mi D6603 mediante Tapatalk
ikerg said:
Like mtcc. You set a default pin. I have a icar3 obd2 bt paired that handles a 1234 pincode running perfectly with torque and dashcommand
Enviado desde mi D6603 mediante Tapatalk
Click to expand...
Click to collapse
Ah ok. I have an OBD2 adapter with modified firmware specific for BMW's - it's supposed to connect with the android app "Deep OBD for BMW". My MTCC unit pairs and connects with the adapter but the app does not see the adapter at all. Does this have to do with the fact that the Bluetooth is managed by the MCU and not the android OS? Is that not the case for these new MTCD Intel units - Is the OS managing the Bluetooth now?
I'm hoping I'll be able to use my modified OBD if I end up buying an MTCD Intel.
Does a single DIN unit of this type exist yet?
MTCD Intel, single DIN unit (Not Joying, since it isn't MTCD)
Since there currently isn't one specific to the BMW E46, I was thinking about getting a generic single DIN unit, and takings its' internals out (everything but the display), and putting it all into my single din MTCC unit which is specific to the BMW E46 (physical layout).
gumanov said:
Does a single DIN unit of this type exist yet?
MTCD Intel, single DIN unit (Not Joying, since it isn't MTCD)
Since there currently isn't one specific to the BMW E46, I was thinking about getting a generic single DIN unit, and takings its' internals out (everything but the display), and putting it all into my single din MTCC unit which is specific to the BMW E46 (physical layout).
Click to expand...
Click to collapse
I dont know if the Display is the same between MTCC and MTCD... go to this thread to see some images (OP) of the interior of a MTCD/intel in order you figure out if this can be feasible:
https://forum.xda-developers.com/an...opment/2gb-ram-intel-cpu-heres-specs-t3468322
I think you can ask manufacturer all the parts (except any display and/or frame) in order to reduce the final price.
I am planning to release a Prerooted Versions for 3G and WIFI MTCD units. Meanwhile on Post#4 you can find Rooting update files for latest December versions of ROM.
Some info needed
Hi, I'm new owner of a Pumpkin Rq0278 unit that seems apparently a rebranded Erisin one. The unis has Sofia3gr processor and the MCU is an LM type. The unit work almost good except the AF of the FM tuner that is not working at all. My questions are:
- can I try to flash my unit with your firmware avoiding issues?
- can I root my unit using your root update without modifying my firmware?
- I don't know very well how the android units work, the tuner is managed by the android part or by the MCU? In last case would be useful to try a MCU firmware update?
Many thanks in advance
zio_mario said:
Hi, I'm new owner of a Pumpkin Rq0278 unit that seems apparently a rebranded Erisin one. The unis has Sofia3gr processor and the MCU is an LM type. The unit work almost good except the AF of the FM tuner that is not working at all. My questions are:
- can I try to flash my unit with your firmware avoiding issues?
- can I root my unit using your root update without modifying my firmware?
- I don't know very well how the android units work, the tuner is managed by the android part or by the MCU? In last case would be useful to try a MCU firmware update?
Many thanks in advance
Click to expand...
Click to collapse
What kind of problems you have with the Tuner?
Have you set it up to your Region? Tuner in America/Asia/Europe manages different frequency ranges.
the Tuner is managed by the MCU. You can set it up on Settings > Factory Settings
enter the password 126
You can see specific options for the Radio and check that you have it configured properly to your region
If not solved you have to ask for newer MCU update to Pumpkin
The Android part (ROM) is interchangeable between different manufacturers (check that you have a MTCD unit based on INtel platform):
If your unit has 3G built in --> You have a sofia3gr-car and sofia3gr device
If your unit has not 3G built in (WIFI only) --> You have a sofia3gr-car ans sofia3grw device
You can update your Android ROM by using the corresponding update to your device from the repository on the OP
The rooting method SHOULD NOT ALTER anything, just adds the root permissions from the boot image.
I published different root files according to the Boot image data and device type
The 126 at factory settings not working for me. Is there anyone know the right number?
Dear Ikerg,
Thanks for your quick answer!
My unit has an Intel CPU with 3g built-in so is a Sofia3gr. The problem of my tuner is the AF functionality that is not working properly. I already checked the configuration in the factory menu (3368 is the pass code), I tried also to change it using China, Australia and so on but nothing changed. I saw that my MCU is not in the last release but for the moment Pumpkin support didn't provide me any upgrade, only for the Android part. Looking in the forum it seems that the img of my unit has the same code name as the Erisin Intel 2gb units (LM). I would like to try one of the available update but I don't won't to brick the unit!!!
About the Android part I'm interest to have root permissions as usually in my android devices in order to be able to perform some backup and other operations. So I can use one of the two update.zip you posted without flashing your complete firmware? At the end of the flashing I can simply do a cache format or a full wipe is needed? I have some doubts because you wrote that the root update contains a boot.img file that must match with the one of my non rooted image. Now I have my original Pumpkin image. The size of the file is exactly the same but comparing the content the files are not equal.
Last question about the Android ROM, you posted several version with related changelog, those versions are made by you or did you collected it from the different brand? Do you think I can have some benefit to install the most updated one from you against the one I have now in my unit (version date is 20.12.2016)?
Thanks again!
zio_mario said:
Looking in the forum it seems that the img of my unit has the same code name as the Erisin Intel 2gb units (LM). I would like to try one of the available update but I don't won't to brick the unit!!!
Click to expand...
Click to collapse
If your unit is LM you can safely update the mcu as it is sourced from same manufacturer (pumpkin and erisin probably will have same rebranded models)
zio_mario said:
...I have some doubts because you wrote that the root update contains a boot.img file that must match with the one of my non rooted image. Now I have my original Pumpkin image. The size of the file is exactly the same but comparing the content the files are not equal...
Click to expand...
Click to collapse
With respect to the root....i only had a update.zip with root that was published some months ago in a Russian forum, which was for wifi version. Some guy reported that flashing that update file on a 3g built-in model can caused to loose the 3G capability.
So I did extract the boot.img and compared with the non rooted boot.img and checked what changed.
I did compare as well two boot.img (non rooted) from same build for wifi and 3g versions and noticed what changed
So finally I put it altogether on a new boot.img from last version i had and build the zip back and signed.
I have not tried it yet, but it is supposed to work.
When I said that boot.img shall match I meant that it is recommended to be for the same date build. If you flash an older boot.img over newer release you can loose any enhancements that could be performed on the newest release. (But according I saw, nothing remarkable)
All the boot.img files for our units must be same sized as it is uploaded onto partition of the unit (which matches that partition the size)
zio_mario said:
...Do you think I can have some benefit to install the most updated one from you against the one I have now in my unit (version date is 20.12.2016)?...
Click to expand...
Click to collapse
If you look at the changelog (just google-translated from the original Chinese changelog from the developer - I think developer is the same for all the brands) only changed the update of Google services (which you can update from google play) so I don't think you will notice any change. (It could be fine if you provide me a link with your december release for 3g built-in model rom to complete the repository)
Anyway if something was wrong you can safely go back with a original update.zip from the recovery menu.
Enviado desde mi D6603 mediante Tapatalk
ikerg said:
If you look at the changelog (just google-translated from the original Chinese changelog from the developer - I think developer is the same for all the brands) only changed the update of Google services (which you can update from google play) so I don't think you will notice any change. (It could be fine if you provide me a link with your december release for 3g built-in model rom to complete the repository)
Click to expand...
Click to collapse
Here you are the link containing the December release from Pumpkin (only Android ROM)
h t t p s ://mega.nz/#!UQsD1DiC!VolW1UbNkRHq8D65aMoxJ1G2B5qmqxYuuyCrhn_Sp8s
Is it possible for you to prepare a root update.zip containing the boot.img of the release I linked? (I have no experience in this kind of operations).
The purpose is to have a unit much updated as possible, a clean installation and root present. The maximum would be to have also a recovery able to perform backup/restore like TWRP but I didn't find nothing till now.
For info, about my AF problems I flashed the last MCU firmware (LM 2.04) but I tried the FM tuner only in the park so wasn't possible to appreciate some progress... Tomorrow I'll try
Last thing, why the password is not the same if the ROM is supposed to be the same for all the brands? You said 126, mine is 3368
Is this thread also for pumpkin RQ0278E?
Στάλθηκε από το BTV-DL09 μου χρησιμοποιώντας Tapatalk
Hello All:
I'm new here, so please forgive me if I accidentally have bad etiquette or break any rules. Also, please forgive the length of the post - I'm trying to include as much useful info as possible.
I'm trying to install TWRP on my refurbished Samsung A5 2017 I'm following the LineageOS instructions at https://wiki.lineageos.org/devices/a5y17lte/install. The TWRP images I've tried to install can be found at https://dl.twrp.me/a5y17lte/.
When I try to install "twrp-3.5.2_9-0-a5y17lte.img", Heimdall ends with "Uploading RECOVERY 100% RECOVERY upload successful Ending session... Releasing device interface...". So everything looks good, but the progress bar on the phone never changes even after 6 hours. When I hold Volume Down and Power buttons the phone reboots into the OS that came with it.
When I try to install an older version, ("twrp-3.5.0_9-0-a5y17lte.img"), the behaviour is slightly different. Heimdall returns the same success messages, but the phone immediately reboots into the OS without me pressing any buttons.
I've done some searching on XDA and via Google and found problems that sound similar to mine, but the descriptions aren't close enough for me to be confident that they're the same problem. My searching so far makes me think that one of the software updates that occurred before I purchased the phone made it either more difficult, or impossible, to put LineageOS on the phone. I also got the impression that I might need to install an earlier official Samsung ROM before I proceed, but that safe and reliable ones are hard to find.
Here is (I hope) all the information needed for some of you wizards to figure out what I should try next:
Phone: Galaxy A5 2017
Model Number: SM-A520W
Android Version: 8.0.0
Samsung Experience version: 9.0
Branding: Telus
Baseband version: A520WVLSECTJ1
Kernel: 3.18.14-16556433-QB35318982
Android security patch level: Nov. 1 2020
Used for installing images: Linux Mint Ulyana and Heimdall via command line commands
Other possibly relevant info:
-"Secure Download : Enabled" shows on 'Downloading' screen
-Seems to be a Telus branded phone
-OEM Unlock is ON
-USB Debugging is ON
-All other switches under 'Developer Options' are OFF
-No SIM installed yet
-Phone has never been connected to WiFi or Cellular Data since I received it.
Thanks in advance for any help you can give!
jenningsthecat said:
Hello All:
I'm new here, so please forgive me if I accidentally have bad etiquette or break any rules. Also, please forgive the length of the post - I'm trying to include as much useful info as possible.
I'm trying to install TWRP on my refurbished Samsung A5 2017 I'm following the LineageOS instructions at https://wiki.lineageos.org/devices/a5y17lte/install. The TWRP images I've tried to install can be found at https://dl.twrp.me/a5y17lte/.
When I try to install "twrp-3.5.2_9-0-a5y17lte.img", Heimdall ends with "Uploading RECOVERY 100% RECOVERY upload successful Ending session... Releasing device interface...". So everything looks good, but the progress bar on the phone never changes even after 6 hours. When I hold Volume Down and Power buttons the phone reboots into the OS that came with it.
When I try to install an older version, ("twrp-3.5.0_9-0-a5y17lte.img"), the behaviour is slightly different. Heimdall returns the same success messages, but the phone immediately reboots into the OS without me pressing any buttons.
I've done some searching on XDA and via Google and found problems that sound similar to mine, but the descriptions aren't close enough for me to be confident that they're the same problem. My searching so far makes me think that one of the software updates that occurred before I purchased the phone made it either more difficult, or impossible, to put LineageOS on the phone. I also got the impression that I might need to install an earlier official Samsung ROM before I proceed, but that safe and reliable ones are hard to find.
Here is (I hope) all the information needed for some of you wizards to figure out what I should try next:
Phone: Galaxy A5 2017
Model Number: SM-A520W
Android Version: 8.0.0
Samsung Experience version: 9.0
Branding: Telus
Baseband version: A520WVLSECTJ1
Kernel: 3.18.14-16556433-QB35318982
Android security patch level: Nov. 1 2020
Used for installing images: Linux Mint Ulyana and Heimdall via command line commands
Other possibly relevant info:
-"Secure Download : Enabled" shows on 'Downloading' screen
-Seems to be a Telus branded phone
-OEM Unlock is ON
-USB Debugging is ON
-All other switches under 'Developer Options' are OFF
-No SIM installed yet
-Phone has never been connected to WiFi or Cellular Data since I received it.
Thanks in advance for any help you can give!
Click to expand...
Click to collapse
Doh! I solved the problem myself by watching a YouTube video. The LineageOS directions are correct but a bit confusing - the video clarified the procedure by showing someone doing it with phone in hand and computer connected. Case closed!
Hello Friend! I have the same problem! Could you provide the video that helped you? thankful!
Giropedal said:
Hello Friend! I have the same problem! Could you provide the video that helped you? thankful!
Click to expand...
Click to collapse
Sure! The video is here:
. There are no verbal instructions - the soundtrack is just music. As I watched the video I was pausing it and following the written instructions on the LineageOS site: https://wiki.lineageos.org/devices/a5y17lte/install. I forget what it was now that I had missed, but the combination of the video and the instructions got me sorted out. Good luck! And if you you find an earlier version of LineageOS for the A5 2017 please post it. My phone works great, but I find Oreo really annoying and I'd like to install a more sensible version.