Related
Hello, I have a Samsung Taylor (developer device) stuck in version 7003, and I'm trying to force-update it.
So far, I have patched ChevronWP7.Updater to apply the update if it detects that the phone version is 7.0.7003.0 (by default it only works if version is 7.0.7004.0). Everything works well, the program says the device was updated successfully, but when it reboots, it's still stuck in 7003.
So, I was hoping if anyone knows the registry key/system file where the current OS version is stored, to try and change the value there.
Sorry, there is literally NO WAY to update the Taylor or the Panther. Changing the OS version, unbranding or even changing the model number (i've changed mine from GW910 to LG-C900) through the registry won't force the update.
But to answer your question the key is "ROMVersion" (string) which is located in
Code:
HKEY_LOCAL_MACHINE\System\Platform\DeviceTargetingInfo
fb401 said:
Changing the OS version, unbranding or even changing the model number (i've changed mine from GW910 to LG-C900) through the registry won't force the update.
But to answer your question the key is "ROMVersion" (string) which is located in
Code:
HKEY_LOCAL_MACHINE\System\Platform\DeviceTargetingInfo
Click to expand...
Click to collapse
Does anyone know if it's possible to change the version number in the registry to force an update? I'm stuck on 7003 on a Samsung Focus and want to try anything that will remotely give me a chance to upgrade this phone.
I've googled all over the place but haven't found a dump of hklm\system\platform\devicetargetinginfo or any other relevant areas of the registry. Hard with the SamsungRegistry app too, as you can only find/write to keys that you know the path to.
dstreefkerk said:
I've googled all over the place but haven't found a dump of hklm\system\platform\devicetargetinginfo or any other relevant areas of the registry. Hard with the SamsungRegistry app too, as you can only find/write to keys that you know the path to.
Click to expand...
Click to collapse
I found the WP7 Root Tools app, and I'm using that now to poke around the registry.
I gave up on this last night after poking around in the registry for 2-3 hours. There was nothing that specifically identified my OS version as 7003.
your in the wrong section , go to the developers section and look around there , no need to google, all the info you need is in there!good luck!
Hello friends.
This is intended to be a thread providing up-to-date versions of ZTE ROMs, mainly for the very unsupported (so far) ZTE V71A and ZTE V11A, but if you have other requests for ZTE roms, please ask and I'll see if I can provide.
--- VDF_IT_V11AV2.0.0B02.zip (466.13 MB) http://www.multiupload.nl/E709JNIJ2H
--- FWUpgrade_Pad_CDMA_V55.zip (215.24 KB) http://www.multiupload.nl/NP6EWS6K3B
--- SPT_AM_V55V1.3.0B09.zip (193.05 MB) http://www.multiupload.nl/YTMKD922CU - NEW v55 ROM
--------------------------------------
The above files are most probably all down, and I can no longer locate new versions for them.
I can, however quote:
dclou said:
Hello All:
The phone company in Taiwan(TWN GSM) has just released the offical 4.0.4 rom zte V71A
(Taiwan mobile mypad p4 is the OEM of ZTE V71A)
http://service.taiwanmobile.com/csonline/cellphone/download.html
Just Connect to the above hyperlink and press "P4 Android 4.04 升級檔 "
Then you can download it and upgrade to 4.0.4.
Please help to update this ROM to the first page of this thread...^^
Click to expand...
Click to collapse
I'm sorry friends. I've lost access to the ZTE servers from where I procured new roms for devices.
Unless I find a different source, I can't provide any updates.
Until further notice this thread may be considered dead.
Thanks man, soo is this older or newer? http://kepfeltoltes.hu/120218/tmp_-2133757290_www.kepfeltoltes.hu_.png
1.2.0B09 released in february 2012 vs 1.0S released in july 2011
Leave me your e-mail adress by pm if you want the file, but be advised that we still don't have a flashing utility to install it with, me and mobilx are still trying to figure out how we can get this software on our devices.
sangemaru said:
1.2.0B09 released in february 2012 vs 1.0S released in july 2011
Leave me your e-mail adress by pm if you want the file, but be advised that we still don't have a flashing utility to install it with, me and mobilx are still trying to figure out how we can get this software on our devices.
Click to expand...
Click to collapse
That would be good. did you get my pm?
Zte score roms?
Sent from my X500 using xda premium
Okay, so here is a pdf for the huaweii media pad 7, of the flashing process and the unlmt.cfg needed is 0byte also , it is supposed to be the same process, dont use the files from here, its not for v71a or v11a!
http://www.huaweidevice.com/tcpsdownload/downLoadCenter?category=&flay=software&downloadID=NDM5NzQ=
brd912, couldn't you have just said X500 in the first place? I'll look, if I find anything I'll let you know.
zsolti, so far I've had no success with using the huawei procedure to flash our tabs, and mobilx hasn't been online today so I haven't got a clue from him about this.
The bad news is, as confirmed earlier by mobilx, the builds are IDENTICAL to what we currently have on our devices. Not encouraging at all (Verified by comparing build.prop). And we don't even know how to flash them yet...
I'm attempting to obtain a carrier unlocked nandroid backup right now, to see if it's locked at a component firmware level or at software level. Maybe we'll see some good news on that front.
Hello there,
This guide in english explains a lot. So this unlmt.cfg file actually serves as a trigger to automatik or manual update.
That means
if it is present update will start on PWR off PWR on
if it is NOT present than you need to go to the FTM mode VOL+ & PWR and update process will start
dload folder must be on ext-sd card.
Again leaked FWs for V11a are the same as ones on our devices
Sangemaru can confirm if his internal FW name on 7 inch matches with the leaked ones.
Go to yours build.prop file and check ro.build.sw_internal_version=VDF_RS_V11AV1.0.0B03 example of mine device
VDF - network - vodafone
RS - country - serbia
V11A - model - 10 inch
V1.0.0 FW version - very first
B03 - localisation ( APNs, keyboards etc) Serbian network APNs and Cyrillic keyboard
Yea, I read it.
At least for my tablet, it didn't apply. Update would not trigger, either on reboot or ftm mode, with neither UPDATA.zip or update.zip names, with the file or not, with fresh sd card format or not, development mode or not, etc.
I'm assuming it worked on your V11A, so somebody should attempt it on their own V71A's if possible. I may have messed something up, or simply have an unsupported sd card.
The one in first post for V71a is :
ro.build.zte_build_number=SmartTab7-MSM8260-V02d-Dec022011-Vodafone-ES
ro.build.software_version=SmartTab7-MSM8260-V02d-Dec022011-Vodafone-ES
ro.build.sw_internal_version=VDF_ES_V71AV1.2.0B09
ro.com.google.clientidbase.ms=android-hms-vf-{country}
ro.com.google.clientidbase.am=android-vf-{country}
ro.build.date=Sat Dec 3 02:09:34 CST 2011
Mine is:
ro.build.zte_build_number=SmartTab7-MSM8260-V02d-Dec022011-Vodafone-HU
ro.build.software_version=SmartTab7-MSM8260-V02d-Dec022011-Vodafone-HU
ro.build.sw_internal_version=VDF_HU_V71AV1.2.0B09
ro.com.google.clientidbase.ms=android-hms-vf-{country}
ro.com.google.clientidbase.am=android-zte
ro.build.date=Sat Dec 3 03:44:43 CST 2011
.
Anyone know what will happen if we flash a firmware from another carrier, like in my case? Because the network id isnt the same for hungary it is 21670, for spain its different...
I'm assuming one thing will happen: nothing.
hei, did any of you has dialer app, it seems vodafone had removed this one
p.s. am on july rom
if there is one can some one post it
tanks
Honeycomb, friend. Honeycomb has telephony support removed. If you want phone service look into a VoIP service.
Hi all !!!!!
I'm Italian .......
My device specs :
M8660A-AABQNLYM-3.1.32T 1 Jul 23 2011 22:00:00
Kernel version :
2.6.35.11-perf.
[email protected]#2
Build Number :
SmartTab10-MSM8260-V02d-Dec022011-Vodafone-IT
huawei media tab
sangemaru said:
Honeycomb, friend. Honeycomb has telephony support removed. If you want phone service look into a VoIP service.
Click to expand...
Click to collapse
did notice that huawei media pad has a dialer app, however did not succed to start it.
I'm saying that in greate proportion the two tablets are just the same.
no luck
zsolti256 said:
The one in first post for V71a is :
ro.build.zte_build_number=SmartTab7-MSM8260-V02d-Dec022011-Vodafone-ES
ro.build.software_version=SmartTab7-MSM8260-V02d-Dec022011-Vodafone-ES
ro.build.sw_internal_version=VDF_ES_V71AV1.2.0B09
ro.com.google.clientidbase.ms=android-hms-vf-{country}
ro.com.google.clientidbase.am=android-vf-{country}
ro.build.date=Sat Dec 3 02:09:34 CST 2011
Mine is:
ro.build.zte_build_number=SmartTab7-MSM8260-V02d-Dec022011-Vodafone-HU
ro.build.software_version=SmartTab7-MSM8260-V02d-Dec022011-Vodafone-HU
ro.build.sw_internal_version=VDF_HU_V71AV1.2.0B09
ro.com.google.clientidbase.ms=android-hms-vf-{country}
ro.com.google.clientidbase.am=android-zte
ro.build.date=Sat Dec 3 03:44:43 CST 2011
.
Anyone know what will happen if we flash a firmware from another carrier, like in my case? Because the network id isnt the same for hungary it is 21670, for spain its different...
Click to expand...
Click to collapse
Hi majaelix,
Tried all proceudres described in this post with no luck updating firmware, I have a Vodafone Spain V71a with 1.0 software version.
Tired to create several folders in sd-ext and puting inside the update.zip and the .cfg file with no success
Tried to sign the zip with Signapk utility but when I try to update it from Recovery, it says: "signature check failed", I think one of the files nneded to sign a zip file is related to the recovery, so I don't know how to generate it.
Also tried to root it with fastboot boot superboot.img but my fastboot can't detect the device form pc, I'vhe checked if drivers are installed in device administration and all seems to be ok.
Did you make any advance on this issue, I'm looking forward.
caveman_78 said:
Hi majaelix,
Tried all proceudres described in this post with no luck updating firmware, I have a Vodafone Spain V71a with 1.0 software version.
Tired to create several folders in sd-ext and puting inside the update.zip and the .cfg file with no success
Tried to sign the zip with Signapk utility but when I try to update it from Recovery, it says: "signature check failed", I think one of the files nneded to sign a zip file is related to the recovery, so I don't know how to generate it.
Also tried to root it with fastboot boot superboot.img but my fastboot can't detect the device form pc, I'vhe checked if drivers are installed in device administration and all seems to be ok.
Did you make any advance on this issue, I'm looking forward.
Click to expand...
Click to collapse
No, but Please standby, a fellow Hungarian 10" user is probably going to make some kind of update we have obtained a build that is even newer, it is the following:
SmartTab7-MSM8260-V03a-Jan182012-Vodafone-HU
good news
zsolti256 said:
No, but Please standby, a fellow Hungarian 10" user is probably going to make some kind of update we have obtained a build that is even newer, it is the following:
SmartTab7-MSM8260-V03a-Jan182012-Vodafone-HU
Click to expand...
Click to collapse
Wow, those are good news. I can't wait for the update. maybe after, we can try to make some weird ICS port.
Please, keep us informed...
Thanks...
i have some problem
hello i have a V71A and i wanna take back the stock rom beacuse i formated system... and a CWM is buggy and usb mass storage is doesn't work and my pc don't see the tablet just CD-rom and not more "adb devices -list of devices atthaced (and nothing)" pls help (sorry for my english)
Uninstall and reinstall usb drivers. Your problem is a driver issue. And how exactly did you format the system?
Hi guys, hope somebody can help me.
I have an LY-F1 tablet with latest ICS 4.0.3 from manufacturer site.
It's pre-rooted already and i installed superuser and busybox.
My major problem is the market, my tablet is recognized has unknown MID which keeps me from getting acess to the full list of apps and gives me compatibility issues.
I've searched in build.prop and there's no field in that file that could define my tablet as MID.
Where can that info be stored for the market to read it?
On my about tablet it also shows MID for model number which means that must be stored somewhere else.
my ro.product.model has a value of A710, not MID!!
What the hell can i do to change this?
I was told to create a local.prop on /data folder, that local.prop should override the build.prop but with no result.
I used a build.prop file from a previous ICS firmware for the same device with no results too. That previous release had full market acess with that same file and the most strange thing was that when using that previous file whem going to about tablet nothing changed, model remains the same, build date remains the date of previous firmware also. Seems like nothing is read from build.prop.
Hope i made my point and sorry for the long post.
Thanks in advance
That's because "MID" model is defined in the "oem.prop" file. I suggest you to use a custom ROM based on the official one released on 10.3.2012.
Here is the video link, you can see how good it is, and it has a "MID" changed to other model so you can access a lot of more apps on makert.
Only bug I found in this one is the HDMI connection, but gaming is great, for the first time, I am able to play Aspahalt 6 on my Ly-f1 tablet.
http://www.youtube.com/watch?feature=player_embedded&v=Xx1jGxeeRyU
Alseo, today, manufacturer released the new version ROM and it says that it has a better market compatibility. I'm gona test it as soon it gets downloaded.
aldinezi said:
That's because "MID" model is defined in the "oem.prop" file. I suggest you to use a custom ROM based on the official one released on 10.3.2012.
Here is the video link, you can see how good it is, and it has a "MID" changed to other model so you can access a lot of more apps on makert.
Only bug I found in this one is the HDMI connection, but gaming is great, for the first time, I am able to play Aspahalt 6 on my Ly-f1 tablet.
http://www.youtube.com/watch?feature=player_embedded&v=Xx1jGxeeRyU
Alseo, today, manufacturer released the new version ROM and it says that it has a better market compatibility. I'm gona test it as soon it gets downloaded.
Click to expand...
Click to collapse
hey guys
i have a question, i read your post,but so i must change the information inside the file "oem.prop"??anf How ??....thanks.
Hi there,
This my first post, so I'll try to be short and to the point.
I just bought an sim-free HTC Radar (7720) from Expansys Japan, hoping to make a present to my Spanish mother. To my surprise, although my Japanese IS12T WP7 had several languages including Spanish, the HongKong market Radar Expansys sold me only has English and Chinese.
Since then I've been desperately trying to get a way to add Spanish display language. Found this thread on xda and thought I was saved.
Being a noob I did read every single post in the 85 pages before trying anything, unfortunately I still can't get Spanish display menu...
Here is what I did:
1) Checked I had latest Zune software (I'm running W8 CP 64bit)
2) Updated the radar up to 8107 through Zune (first 7740, then 8107).
3) Downloaded and installed WP7_update_tool
4) Downloaded and extracted WP7_Update_Cab_Sender
5) Downloaded all the Spanish language update cab files (1 for Nodo, 2 for Mango), and added them to the WP7_Update_Cab_Sender folder
6) Run the bat file, then choose "B" for backup+update
7) After a while, and a few restarts both the Update utility and the phone showed the message "Update successful".
I then went to change my display settings and found out that I still only had English and Chinese available...
Is there something I missed? Do you have any suggestions?
Right now the only thing I can think about is that maybe I shouldn't have used Zune to update. Should I try to roll back to 7740 with Zune, then update to 8107 using the Cab_Sender instead?
Thanks in advance.
Well, I got impatient so just tried to restore to the previous version using Zune...
Tried already 3 times, no particular error messages and everything seems to go fine. Yet at the end I always end up where I was, at 8107...
Am I stucked in here or is there something else I can try?
Any way of getting my phone back to 7720, or any idea of whether that would help me solve my problem ?
Having Spanish support is much more important than getting future updates... so that's not an issue...
CAB-sender takes a backup (technically "restore point") using the same mechanism that Zune does. If you didn't back up your older restore points, they were overwritten.
I'd suggest just flashing a European stock ROM. Here's a nice list of the ROMs for Radar phones: http://forum.xda-developers.com/wiki/HTC_Radar/Shipped_Roms. Make sure the device version matches (i.e. the TMoUS one probably won't work, though I don't know what hardware a Radar purchased by way of Japan will use).
GoodDayToDie said:
CAB-sender takes a backup (technically "restore point") using the same mechanism that Zune does. If you didn't back up your older restore points, they were overwritten.
I'd suggest just flashing a European stock ROM. Here's a nice list of the ROMs for Radar phones: http://forum.xda-developers.com/wiki/HTC_Radar/Shipped_Roms. Make sure the device version matches (i.e. the TMoUS one probably won't work, though I don't know what hardware a Radar purchased by way of Japan will use).
Click to expand...
Click to collapse
Thank you so much for your reply; now:
- I understood what I did wrong (over-write my previous backups when I run CAB-sender...
- Have some hope to get it done.
My hardware is: HTC Radar C110e, but unfortunately I found no file matching my current Firmware/Bootloader:
- Firmware: 1600.2200.20301.708
- RadioSofware: 16.23.03.17_16.27.00.23
- Bootloader: 2.3.160015.3(134621)
So additional questions:
- If I get one of these European ROM's, will I get also the language packs delivered by default in the European region (which include the one I want, Spanish)?
- Will my phone be updatable through the regular Zune channel afterwards?
- Should I rather get the newest, oldest, or it doesn't matter? (assuming I'll get the updates normally)
Your questions, in order:
1. Yes. These are the ROMs which are distributed on retail phones, and should include the standard language set for Windows Phones (which I'm pretty certain includes Spanish for the European phones, although I've never checked).
2. Yes. Flashing a stock ROM will make the phone behave exactly as though you'd bought it with that ROM, and it should work with Zune like any other Windows phone (including being updatable).
3. I suggest going with the newest ROM on that list, because it has the same major version number for its bootloader (2) and same revision version number for its radio (03). This reduces the risk of it not flashing correctly for some reason. That ROM is also 7740, so it will need fewer updates after flashing.
Do keep your restore point handy, in case the flash fails for whatever reason, but it shouldn't be needed. You can try recovering older restore points using the "Previous Versions" feature of Windows (requires Volume Shadow Copy service to not be disabled, and System Restore to be enabled for you user-profile disk and set to backup user files as well as system files).
Flashing a European ROM really seems like the best bet, though. You'll need to start the phone into SPL (bootloader) mode, which I believe requires turning off the phone, pressing and holding the Volume Down button, and turning it on again. You should see a screen with bands of color and info about your SPL in yellow text. At the bottom will be black text saying "Serial". Plug the phone into the computer. It will install some drivers (automatically, on Vista or later; on XP you may need to do this manually) and then the text at the bottom of the phone's screen should change to "USB". At that point, you can run the ROM Update Utility (RUU) that should have come packaged with the ROM image.
Thanks again for your precious help. It seems that's exactly what I need.
Now, sorry for asking again, but after a few hours I still couldn't find a suitable RUU... The links you gave me previously pointed to the ROM images only, any idea of where can I find "the RUU packed with those images"? Or "how to pack them myself"?
I did find a few threads in xda with a link to a RUU (here) , but it's only for the oldest version. Then they provide additional ROM images (.nbh), but it's not clear to me how can I pack those into a RUU.
Finally, I did find this other thread where someone was kind of explaining how to do it, but it seems the OP didn't even get it to work to begin with, so it doesn't feel reassuring...
Any further guidance would be appreciated.
I'm afraid you've reached the limits of my knowledge of such things. The only time I've manually flashed anything, the download came as a packaged RUU "installer" (basically just a self-unpacking archive, so far as I can tell) and included simple instructions for using it. If you tell me what file(s) your download contained, I could try to tell you how to lay them out like my phone has it, but I'm hesitant because I really don't know the intricacies of RUU.
I'm guessing you already checked the Radar forums? Alternatively, if you look at the threads for the other ROM downloads, at least some of them start with RUU and end with .EXE (which is how my download came) instead of starting with IMG and ending with .NBH (my download included some NBH files, though). Maybe grab one of the RUU bundles, run it, watch what files it extracts, and then replace the NBH file with the one you already downloaded? I can't promise this will work, but it's worth a shot.
GoodDayToDie said:
I'm afraid you've reached the limits of my knowledge of such things. The only time I've manually flashed anything, the download came as a packaged RUU "installer" (basically just a self-unpacking archive, so far as I can tell) and included simple instructions for using it. If you tell me what file(s) your download contained, I could try to tell you how to lay them out like my phone has it, but I'm hesitant because I really don't know the intricacies of RUU.
I'm guessing you already checked the Radar forums? Alternatively, if you look at the threads for the other ROM downloads, at least some of them start with RUU and end with .EXE (which is how my download came) instead of starting with IMG and ending with .NBH (my download included some NBH files, though). Maybe grab one of the RUU bundles, run it, watch what files it extracts, and then replace the NBH file with the one you already downloaded? I can't promise this will work, but it's worth a shot.
Click to expand...
Click to collapse
Well, thank you in any case for your kindness and having taken me here.
I think I'm ready to try … Just made up my mind to go in the following order:
1) Give a shot to the original RUU file (even though it has an old build of my phone); then hope that Zune updates come as you said they would (my phone unbranded phone came out of the box with Mango 7720 and it took only a few minutes to get the latest version).
2) If updates don't come, try to modify the RUU file with the newer ROM to see if I have better chance...
I'll be back to report what happened.
Well, I tried both the old and the newer ROMs, and:
- on the good side: my phone didn't get killed in the process
- on the bad side: I get an error message saying "ERROR [294] : INVALID VENDER ID" no matter what...
The ReadMe file says:
One of these error messages will appear when you use the wrong RUU to do the upgrade. RUU will check if the Model ID and Language ID are compatible with the device. Make sure you use the appropriate RUU tool to upgrade.
So I guess I'm slowly reaching a dead end... Someone has any further suggestions???
any updates here ?
Android 10 last build that came out this march solved lots of problems but still had one that was unforgivable for me, the low volume of voice recording while using whatsapp, telegram and messenger, so I looked for a way to make a downgrade to android 9 and without having to unlock bootloader and I found one that worked and want to share with you:
Requirements/materials:
-Sony drivers for your phone (I got them by installing latest version of Sony PC companion)
-New flasher v20 (original thread: https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426)
-XperiFirm (to download Android 9 firmware.) (you can get it by downloading flashtool or from the original post:
https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142)
-flashtool (I used 0.9.27.0 version) https://mega.nz/#!g24hXIQa!L22-invd46Onx7pzAEf0C4tkrAe87AR1JftRni8G6rA
Instructions:
1-open Xperifirm to download your firmware:
look your phone on the left side, then your specific model (in my case it was H8314, if you dont know your model check in your phone settings) once you selected your phone Xperifirm will show a list of firmwares on the right side, select one of the builds with the number 52.0.A.11.32 on it if you want the latest build of Android 9. In my case 52.0.A.11.32/R3B from chile worked (i´m from mexico). Once you have selected your build then click on the square button that is below of "availanle firmware" and a windows will open and show you two options to download the files, you hit the "Download" button. then another window will open and the program will start downloading your firmware.
Once it`s downloaded you should get this files:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
except the folder that says "Decrypted", I will explain about such folder later.
2-Open Flashtool and Decrypt the firmware files
2.1-select the next options on the menu: Tools>Bundles>FILESET Decrypt
2.2-look for the path of the folder in which you downloaded your firmware, and then move to the right the three files you have on the left and click on convert.
It will take around five minutes to convert all the files, Once flashtool is done with that, it will ask you to create a bundle, click on "cancel" to close the window. So now if you look at the folder where you have the firmware files you got a new folder called "Decrypted" that I mentioned and that you saw in the picture above in step 1, if you open it, it will look like this:
with a folder called "boot" and another called "partition", and some files as well.
3-Download (if you have not) and extract New flasher v20 in a new folder
(link posted above in the "Requirements/materials" section)
You should get this files:
4-Preparing the firmware files:
4.1-open the firmware folder, select and delete all of the .ta files in the main folder.
4.2-Now open the ‘boot’ folder within the main firmware folder. There is one .ta file in here called ‘Apollo_XBootConfig_MiscTA‘ that you also need to delete.
(Note: something else instead of "apollo" could be in the name of the file depending on your phone model)
4.3-Now the final step in preparing your firmware, is to copy the entire contents of the firmware folder to the Newflasher folder.
Once complete, your Newflasher folder should look like something below. The highlighted files are those copied across from your firmware folder.
5-Flash Xperia firmware
If you’ve reached this stage, then that’s the hardest part done. This next section involves the process of actually flashing your Sony Xperia device.
5.1-Connect your Sony Xperia device. Make sure the device is powered off and then hold the ‘volume down’ button whilst connecting the USB cable. You will see the led of your phone turns on and stays on, (that means it entered into flashmode)
5.2-Double click the ‘newflasher’ application as highlighted below.
5.3-A Windows command prompt will now open. It will ask you if you want to perform an optional step (if you need a gordongate flash drive) Type ‘n’ for no and press Enter.
5.4-newflasher will will ask you again if you want to perform an optional step, (dump trim area) Type ‘n’ for no and press Enter.
5.5-newflasher will ask you if you want to perform another optional step (flash bootloader,bluetooth,dsp,modem,rdimage to booth a,b slots)Type "n" for no and press Enter.
5.6-Your Sony Xperia device will now begin to flash new firmware.
You will see some files going through during the flashing
5.7-newflasher will ask you if you want to perform another optional step(flash persist partition).Type "n" for no and press Enter.
You will see some other files going through the screen
6- Once complete, you will receive a message that “You can disconnect your device when you close newflasher.exe“.
Congratulations, your Sony Xperia device has now been successfully flashed to new firmware.
7-Disconnect your Xperia device and power on the handset. Don’t worry if it takes a while for the handset to boot, this is to be expected. To confirm that you have upgraded the phone software, click on ‘Settings > About phone’, which will reveal your new Android version and firmware build number.
Final Note:
-some parts of this guide were obtained from here: https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/
I Did my best to attach good screenshots so the follow of the process could be be easier but I just realized the pictures are very tiny and pixelated, sorry, hopefully you will still understand as everything is explained in a very detailed way. If you know a goos site to attach images that I could use please let me know.
Oh, no. XperiFirm shows only the Android 10 firmware for H8314 in USA (Verizon). Verizon has no GSM, so Sony tweaked the US model to place calls ONLY over LTE. Where can I find the Android 9 firmware for USA?
UncleDick said:
Oh, no. XperiFirm shows only the Android 10 firmware for H8314 in USA (Verizon). Verizon has no GSM, so Sony tweaked the US model to place calls ONLY over LTE. Where can I find the Android 9 firmware for USA?
Click to expand...
Click to collapse
my thoughts about that are:
1-why are you looking for android 10 in this phone if it has so many bugs?
2does it really needs to be from USA? I dont think thats the only country with such configuration over calls.
and finally: 3- I think that such problem could be solved through configuration? or it has to do with the rom files?
ferluna18 said:
my thoughts about that are:
1-why are you looking for android 10 in this phone if it has so many bugs?
2does it really needs to be from USA? I dont think thats the only country with such configuration over calls.
and finally: 3- I think that such problem could be solved through configuration? or it has to do with the rom files?
Click to expand...
Click to collapse
Very good questions, thanks.
1. Why Android 10? Several thoughts. (a) the phone keeps bugging me to do it. (b) there may be features in Android 10 that would appear to me. (c) As far as I can tell, Android 9 is no longer getting any security fixes Having had several Android phones in the past that almost never got a security update, I have been pretty smug about my Sony "keeping up".
2. USA? Actually, "Global System for Mobile" (GSM) seems to mean "everybody in the whole planet except US and Japan." The Dual SIM version of the XZ2 Compact doesn't work on Verizon, only the H8413". Not being able to retreat to the "official" Android 9 for Verizon just worries me.
3. Configuration? Not willing to bet that Sony did not bury some code specific to Verizon in the "Official USA" firmware.
I absolutely LOVE this phone. Over the past year, it has become essential to my life. (Reads my diabetic sensor. Monitors my home security system. Keeps track of Amazon packages. Handles my 10 email accounts. Is my kitchen timer. Manages (what's left of) my calendar.) Seems like I pull out the phone at least 20-30 times a day. If I upgrade to Android 10 and it mangles my phone, I will be SO frustrated.
It is a great comfort that these forums have so many capable volunteers. If I start seeing posts, "Hey, I upgraded my Verizon H8413 and it works great!" , then I'll be much more likely to do it. So far, I simply don't see posts like that, only the opposite. And, "there's no way back." (I am sort of kicking myself that I failed to buy a second H8413 when they were on sale everywhere. I could just move the SIM card to it if Android 10 wrecks my current phone. That's how goofy I am. $400 for peace of mind.)
I understand, I have noticed something interesting about the update notification thing , I bought my phone on USA (xz2 compact single sim unlocked version) and of course it came with a US firmware so Igot the notification to update to Android 10 but very late, I don't know why, (android 10 March version) and I was hesitant about accepting such update but I did, then everything was okay except voice notes, the thing is that I decided to downgrade using the method I posted in this guide and installed a non US firmware, I have been using such firmware for like two weeks and the update center says that the next Android version is Android 10 but it doesn't give me the fastidious notification telling me that there is a mew update for my phone.
Hi, in Xperifirm Android 9 for H8324 ist just available as Rom for Saudi Arabia (52.0.A.11.32/R4B). Can I use this Rom for Europe, and is it including german language? Does anybodyknow?
Greetings Odiad
odiad said:
Hi, in Xperifirm Android 9 for H8324 ist just available as Rom for Saudi Arabia (52.0.A.11.32/R4B). Can I use this Rom for Europe, and is it including german language? Does anybodyknow?
Greetings Odiad
Click to expand...
Click to collapse
I successfully flashed the Saudi Arabian version 52.0.A.11.32/R4B from XperiFirm onto my XZ2c. There is possibility to choose German as language. My carrier (Tele2 / Sweden) works fine.
I was struggling trying to flash the phone using FlashTool and its .fsc scripts, but when i used newflasher with the advice given in this thread it worked perfectly.
Good luck!
PS. No more unresponsive touchscreen!
pyraohms said:
I successfully flashed the Saudi Arabian version 52.0.A.11.32/R4B from XperiFirm onto my XZ2c. There is possibility to choose German as language. My carrier (Tele2 / Sweden) works fine.
I was struggling trying to flash the phone using FlashTool and its .fsc scripts, but when i used newflasher with the advice given in this thread it worked perfectly.
Good luck!
PS. No more unresponsive touchscreen!
Click to expand...
Click to collapse
Hi Pyraohms.
-> Just to be sure - you did the downgrade with locked bootloader, correct?
-> And do you have now the update-info for android 10 in notification? Or is updating after downgrade just manually possible (if a perfect Android 10 will appear)?
Edit: I couldn't wait for an answer, because Android 10 annoyed me again. I tried successfully to downgrade with locked bootloader. All went fine. Now on Android 9 again fingerprintsensor works great again without lags..... I forgot how good it feels
odiad said:
Edit: I couldn't wait for an answer, because Android 10 annoyed me again. I tried successfully to downgrade with locked bootloader. All went fine. Now on Android 9 again fingerprintsensor works great again without lags..... I forgot how good it feels
Click to expand...
Click to collapse
Nice. Yeah, the fingeprint sensor works much better with A9, but I still get random freezes when unlocking and the screen becomes unresponsive until I hit the power button to lock and then use the sensor to unlock again. Does anybody else experience this?
I will probably send the unit for repair before my warranty is out. Should probably install the nordic version of A10 first though.
pyraohms said:
Nice. Yeah, the fingeprint sensor works much better with A9, but I still get random freezes when unlocking and the screen becomes unresponsive until I hit the power button to lock and then use the sensor to unlock again. Does anybody else experience this?.
Click to expand...
Click to collapse
Hi pyraohms. Up to now I haven't had this problem. Not with the original Android 9 (before update to Android 10), and also not after downgrading according to the guide in this thread.
Good luck that you can solve this....
odiad said:
Hi pyraohms. Up to now I haven't had this problem. Not with the original Android 9 (before update to Android 10), and also not after downgrading according to the guide in this thread.
Good luck that you can solve this....
Click to expand...
Click to collapse
Do you know which firmware version that you had before? Latest A9? If not, maybe we can get hold of an old version that do not have these issues somehow.
EDIT: Im downloading 52.0.A.3.27 from XperiFirm to try it now.
Has anyone been able to verify that flashing the Chile firmware on an H8314 on the Verizon network is possible?
I'd really love to get my phone's usability back!! But I'm also afraid to flash something that might not work as this is pretty much right at the edge of my technical scope. I think I would not know how to fix it if the firmware didn't work right.
pyraohms said:
I successfully flashed the Saudi Arabian version 52.0.A.11.32/R4B from XperiFirm onto my XZ2c. There is possibility to choose German as language. My carrier (Tele2 / Sweden) works fine.
I was struggling trying to flash the phone using FlashTool and its .fsc scripts, but when i used newflasher with the advice given in this thread it worked perfectly.
Good luck!
PS. No more unresponsive touchscreen!
Click to expand...
Click to collapse
Is it still the case that downgrading from android 10 51.1.A.0.672 to android 9 52.0.A.11.32 fixes the touchscreen issues?
theuchi said:
Is it still the case that downgrading from android 10 51.1.A.0.672 to android 9 52.0.A.11.32 fixes the touchscreen issues?
Click to expand...
Click to collapse
Unfortunately no. I tried this but when problems persisted I had the unit sent for repair. And I got it back with the remark "firmware reinstalled - passes functional tests". Phone was working OK for some week, then the touchscreen issues got back :/
hello,
according to this downgrade instruction I have to delete .ta-files. What is the reason for that? I am asking because I was on LOS17 (open bootloader and twrp), but had randomly freezing screen and I went back to android 9 using News-flasher (as described in this instruction). Now sometimes I have also in Stock Android 9 randomly freeze of screen. I never had this when I was in Android 9 before Android and LOS17 . So reason could be bootloader/twrp, or maybe that anything from LOS17 remains after flashing stock android 9.
- Is flashing Android 9 including delete .ta-files before just a kind of partly installation, that parts of former Rom can be still in firmware?
- What happens if .ta-files are not deleted before flashing?
Greetings Odiad
ferluna18 said:
Android 10 last build that came out this march solved lots of problems but still had one that was unforgivable for me, the low volume of voice recording while using whatsapp, telegram and messenger, so I looked for a way to make a downgrade to android 9 and without having to unlock bootloader and I found one that worked and want to share with you:
Requirements/materials:
-Sony drivers for your phone (I got them by installing latest version of Sony PC companion)
-New flasher v20 (original thread: https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426)
-XperiFirm (to download Android 9 firmware.) (you can get it by downloading flashtool or from the original post:
https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142)
-flashtool (I used 0.9.27.0 version) https://mega.nz/#!g24hXIQa!L22-invd46Onx7pzAEf0C4tkrAe87AR1JftRni8G6rA
Instructions:
1-open Xperifirm to download your firmware:
look your phone on the left side, then your specific model (in my case it was H8314, if you dont know your model check in your phone settings) once you selected your phone Xperifirm will show a list of firmwares on the right side, select one of the builds with the number 52.0.A.11.32 on it if you want the latest build of Android 9. In my case 52.0.A.11.32/R3B from chile worked (i´m from mexico). Once you have selected your build then click on the square button that is below of "availanle firmware" and a windows will open and show you two options to download the files, you hit the "Download" button. then another window will open and the program will start downloading your firmware.
Once it`s downloaded you should get this files:
except the folder that says "Decrypted", I will explain about such folder later.
2-Open Flashtool and Decrypt the firmware files
2.1-select the next options on the menu: Tools>Bundles>FILESET Decrypt
2.2-look for the path of the folder in which you downloaded your firmware, and then move to the right the three files you have on the left and click on convert.
It will take around five minutes to convert all the files, Once flashtool is done with that, it will ask you to create a bundle, click on "cancel" to close the window. So now if you look at the folder where you have the firmware files you got a new folder called "Decrypted" that I mentioned and that you saw in the picture above in step 1, if you open it, it will look like this:
with a folder called "boot" and another called "partition", and some files as well.
3-Download (if you have not) and extract New flasher v20 in a new folder
(link posted above in the "Requirements/materials" section)
You should get this files:
4-Preparing the firmware files:
4.1-open the firmware folder, select and delete all of the .ta files in the main folder.
4.2-Now open the ‘boot’ folder within the main firmware folder. There is one .ta file in here called ‘Apollo_XBootConfig_MiscTA‘ that you also need to delete.
(Note: something else instead of "apollo" could be in the name of the file depending on your phone model)
4.3-Now the final step in preparing your firmware, is to copy the entire contents of the firmware folder to the Newflasher folder.
Once complete, your Newflasher folder should look like something below. The highlighted files are those copied across from your firmware folder.
5-Flash Xperia firmware
If you’ve reached this stage, then that’s the hardest part done. This next section involves the process of actually flashing your Sony Xperia device.
5.1-Connect your Sony Xperia device. Make sure the device is powered off and then hold the ‘volume down’ button whilst connecting the USB cable. You will see the led of your phone turns on and stays on, (that means it entered into flashmode)
5.2-Double click the ‘newflasher’ application as highlighted below.
5.3-A Windows command prompt will now open. It will ask you if you want to perform an optional step (if you need a gordongate flash drive) Type ‘n’ for no and press Enter.
5.4-newflasher will will ask you again if you want to perform an optional step, (dump trim area) Type ‘n’ for no and press Enter.
5.5-newflasher will ask you if you want to perform another optional step (flash bootloader,bluetooth,dsp,modem,rdimage to booth a,b slots)Type "n" for no and press Enter.
5.6-Your Sony Xperia device will now begin to flash new firmware.
You will see some files going through during the flashing
5.7-newflasher will ask you if you want to perform another optional step(flash persist partition).Type "n" for no and press Enter.
You will see some other files going through the screen
6- Once complete, you will receive a message that “You can disconnect your device when you close newflasher.exe“.
Congratulations, your Sony Xperia device has now been successfully flashed to new firmware.
7-Disconnect your Xperia device and power on the handset. Don’t worry if it takes a while for the handset to boot, this is to be expected. To confirm that you have upgraded the phone software, click on ‘Settings > About phone’, which will reveal your new Android version and firmware build number.
Final Note:
-some parts of this guide were obtained from here: https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/
Click to expand...
Click to collapse
Thank you so much for this bro. Android 10 for my xperia xz2 compact ruined my device. Now after i follow your tutorial/instructions to downgrade to Android 9, my xperia xz2 compact become smooth as new specially the fingerprint now is very quick responsive.
ferluna18 said:
Android 10 last build that came out this march solved lots of problems but still had one that was unforgivable for me, the low volume of voice recording while using whatsapp, telegram and messenger, so I looked for a way to make a downgrade to android 9 and without having to unlock bootloader and I found one that worked and want to share with you:
Requirements/materials:
-Sony drivers for your phone (I got them by installing latest version of Sony PC companion)
-New flasher v20 (original thread: https://forum.xda-developers.com/cr...gress-newflasher-xperia-command-line-t3619426)
-XperiFirm (to download Android 9 firmware.) (you can get it by downloading flashtool or from the original post:
https://forum.xda-developers.com/cr...xperifirm-xperia-firmware-downloader-t2834142)
-flashtool (I used 0.9.27.0 version) https://mega.nz/#!g24hXIQa!L22-invd46Onx7pzAEf0C4tkrAe87AR1JftRni8G6rA
Instructions:
1-open Xperifirm to download your firmware:
look your phone on the left side, then your specific model (in my case it was H8314, if you dont know your model check in your phone settings) once you selected your phone Xperifirm will show a list of firmwares on the right side, select one of the builds with the number 52.0.A.11.32 on it if you want the latest build of Android 9. In my case 52.0.A.11.32/R3B from chile worked (i´m from mexico). Once you have selected your build then click on the square button that is below of "availanle firmware" and a windows will open and show you two options to download the files, you hit the "Download" button. then another window will open and the program will start downloading your firmware.
Once it`s downloaded you should get this files:
except the folder that says "Decrypted", I will explain about such folder later.
2-Open Flashtool and Decrypt the firmware files
2.1-select the next options on the menu: Tools>Bundles>FILESET Decrypt
2.2-look for the path of the folder in which you downloaded your firmware, and then move to the right the three files you have on the left and click on convert.
It will take around five minutes to convert all the files, Once flashtool is done with that, it will ask you to create a bundle, click on "cancel" to close the window. So now if you look at the folder where you have the firmware files you got a new folder called "Decrypted" that I mentioned and that you saw in the picture above in step 1, if you open it, it will look like this:
with a folder called "boot" and another called "partition", and some files as well.
3-Download (if you have not) and extract New flasher v20 in a new folder
(link posted above in the "Requirements/materials" section)
You should get this files:
4-Preparing the firmware files:
4.1-open the firmware folder, select and delete all of the .ta files in the main folder.
4.2-Now open the ‘boot’ folder within the main firmware folder. There is one .ta file in here called ‘Apollo_XBootConfig_MiscTA‘ that you also need to delete.
(Note: something else instead of "apollo" could be in the name of the file depending on your phone model)
4.3-Now the final step in preparing your firmware, is to copy the entire contents of the firmware folder to the Newflasher folder.
Once complete, your Newflasher folder should look like something below. The highlighted files are those copied across from your firmware folder.
5-Flash Xperia firmware
If you’ve reached this stage, then that’s the hardest part done. This next section involves the process of actually flashing your Sony Xperia device.
5.1-Connect your Sony Xperia device. Make sure the device is powered off and then hold the ‘volume down’ button whilst connecting the USB cable. You will see the led of your phone turns on and stays on, (that means it entered into flashmode)
5.2-Double click the ‘newflasher’ application as highlighted below.
5.3-A Windows command prompt will now open. It will ask you if you want to perform an optional step (if you need a gordongate flash drive) Type ‘n’ for no and press Enter.
5.4-newflasher will will ask you again if you want to perform an optional step, (dump trim area) Type ‘n’ for no and press Enter.
5.5-newflasher will ask you if you want to perform another optional step (flash bootloader,bluetooth,dsp,modem,rdimage to booth a,b slots)Type "n" for no and press Enter.
5.6-Your Sony Xperia device will now begin to flash new firmware.
You will see some files going through during the flashing
5.7-newflasher will ask you if you want to perform another optional step(flash persist partition).Type "n" for no and press Enter.
You will see some other files going through the screen
6- Once complete, you will receive a message that “You can disconnect your device when you close newflasher.exe“.
Congratulations, your Sony Xperia device has now been successfully flashed to new firmware.
7-Disconnect your Xperia device and power on the handset. Don’t worry if it takes a while for the handset to boot, this is to be expected. To confirm that you have upgraded the phone software, click on ‘Settings > About phone’, which will reveal your new Android version and firmware build number.
Final Note:
-some parts of this guide were obtained from here: https://www.xperiablog.net/2018/01/...-firmware-for-xperia-xz-premium-xz1-and-more/
Click to expand...
Click to collapse
Hi. Could you reload or restore the pictures attached in the first post?
dario82ct said:
Hi. Could you reload or restore the pictures attached in the first post?
Click to expand...
Click to collapse
Would really appreciate this as well. I got my phone back from Sony repairs under warranty but it's a refurbed phone with Android 10. Ew. With 5 mins of Pokego it drains 2% already so I am really anxious about either the battery life on this refurbed phone is **** (I had 92% on my old handset from 2 years of use), or if it's Android 10 being the culprit.
Also if this method doesn't include unlocking bootloader, does it mean my warranty won't be voided? (Any idea, I got 4 months left on warranty).
Instead of getting the software from xperifirm since it's all android 10 on it now, I downloaded the prev version I had of Pie 52.0.A.3.27 from the Sony developer website. Would I be able to use that instead? I tried unpacking it but it's so different to the files that I downloaded from xperifirm..... sorry I have no idea what I am doing.
Alternatively, would it be safe to download and flash the "Commercial and Journalists" version (I live in New Zealand) since it seems like it's the only Pie build on Xperifirm?
harpnote said:
Would really appreciate this as well. I got my phone back from Sony repairs under warranty but it's a refurbed phone with Android 10. Ew. With 5 mins of Pokego it drains 2% already so I am really anxious about either the battery life on this refurbed phone is **** (I had 92% on my old handset from 2 years of use), or if it's Android 10 being the culprit.
Also if this method doesn't include unlocking bootloader, does it mean my warranty won't be voided? (Any idea, I got 4 months left on warranty).
Instead of getting the software from xperifirm since it's all android 10 on it now, I downloaded the prev version I had of Pie 52.0.A.3.27 from the Sony developer website. Would I be able to use that instead? I tried unpacking it but it's so different to the files that I downloaded from xperifirm..... sorry I have no idea what I am doing.
Alternatively, would it be safe to download and flash the "Commercial and Journalists" version (I live in New Zealand) since it seems like it's the only Pie build on Xperifirm?
Click to expand...
Click to collapse
Hello. I have downgraded to android 8 (having tried them all since I bought the phone, it's my favorite), and everything works great again! The fingerprint sensor is very fast, no more bugs in whatsapp audio messages, the battery lasts much longer than Android 10.
The procedure in the first post is slightly imperfect, as on Xperifirm, the firmwares are downloaded already decrypted (in practice you have to skip steps 2 and 2.1 of the guide).
Obviously I don't take responsibility, but it worked for me.