Hi Guys,
Someone please guide me to flash Android Pie on my G8142. I have already downloaded G8142_Customized VN_1309-2181_47.2.A.0.306_R3C firmware via XperiFirm.
Note -
Locked BL
Currently on 47.1.A.16.20
Thanks in advanced.
Hi, frankly speaking, as your BL is blocked you should/can wait only some few days, it should come over the air very soon
Hi, I also have a locked bootloader, and its still locked after flashing the update using newflasher
all I did was download the VN firmware from xpericheck app that is integrated in flashtool application.
then I downloaded newflasher and it was a zip file, I extracted it, copied all files in it and pasted them in the same folder where the firmware files at, then ran newflasher, and thats it
I have Pie.
Did you delete any of the .TA files prior to flashing?
Hi @madshark2009,
can you provide me any guidelines to do it. I'm new to Sony.
@kw0n2k
No,all I did was simply flash using newflasher
@werty733
here is how i did it:
download xperifirm application:
https://softfamous.com/xperifirm-tool/
when you launch it, select Xperia XZ Premium (the dual one)
then you will get a bunch of fimrwares for different regions, simply select the VN region and it should show on the far right "latest update available" with a number of 47.2.A.0.306
download that to an empty folder of your choice
after download completed, download newflasher from here
https://forum.xda-developers.com/crossdevice-dev/sony/progress-newflasher-xperia-command-line-t3619426
download v13, you will get a ZIP file, copy all files in the file to the same folder where you downloaded the firmware files.
then simply run newflasher from that folder, press n for the first option, and another n for the second option, then it should start doing the magic, after its done, youre set. hope that helped
@madshark2009 thanks, will try your method and update.
@madshark2009 sorry I meant, the new firmware files that you downloaded with xpirifirm, the .TA files in that. correct me if im wrong, but i thought you had to delete them prior to flashing as it might over ride your DRM keys.
@kw0n2k
I dont think so, because i checked my keys stats and they are all ok, no one answered me that officially so i cant give you a concrete answer but i dont think flashing an update resets your drm, we all have been doing it before, i have done it before on oreo and nougat so yah, but get a more officially approved answer from a dev here better for you not to do anything that could harm your device on my word alone
Cheers mate
@madshark2009 Yeah, I converted my G8142 to G8141 cause I couldnt get VolTE in Australia. From what i read, i was under the assumption that .TA files had to be deleted on the new firmware prior to flashing as to not lose your DRM keys. But if you've done it and everything's fine, happy days! I'll just flash normally without deleting any files from now on.
the good @munjeni have exclu .ta in the script no problem for flash with any problem
@madshark2009, it worked perfectly without any issues. but I'm very disappointed there is no Gestures.
Related
Note: OTA updates don't work on my Nexus 5 due to TWRP blocking them. Now my phone doesn't recognize the OTA update anymore (When my phone went to install the OTA updated and rebooted, it rebooted into TWRP instead and completely ignores the updates existence since then). To fix this I plan to simply push the factory img of 5.0.1 to my device directly. I downloaded the factory .img from Google's website .
However instead of a .img file i'm used to, I got a .tgz. I extracted that and got a .tar and then extracted that to finally get my folder with the .img files. However now I'm not sure which one to push to my device. There is a img file called "radio-hammerhead-m8974a-2.0.50.2.22.img" but judging by the file size, I don't think that's the correct one (only 45MB). There is a .zip file called "image-hammerhead-lrx22c.zip" but this contains multiple .img files, the largest one called "system.img". I'm guessing this is the correct one to push to my device via adb since it's about 1GB in size?
I suspect pushing the entire .zip file to my phone and flashing that would be bad as it looks like it'll overwrite TWRP?
Any help would be greatly appreciated.
Here's a lot of useful information about OTA's Check it out: http://forum.xda-developers.com/google-nexus-5/general/info-nexus-5-ota-help-desk-t2523217
You'll need boot and system at least,
If you plan on keeping twrp and root, you may as well just flash one of the flashable zips already available in the development forum
Actually you should have a radio and bootloader img file. First one is - as the name says - the latest radio software (which is needed for GPS, WiFi, cellular network and so on). Second one is the latest bootloader. I'd update them both.
From the zip archive you should only flash certain imgs - if you flash all your data will be wiped (factory reset). What img files does the zip contain?
Why are you pushing them to your phone? You need to flash with fastboot from your computer. There is not just one img file for the update, there are several for different partitions on the phone. Have a look through some of the guides in the general section. Also, flashing one of the stock flashable zips would be much faster, but why not learn a little as you update.
Vomer has a thread of flashable 5.0 and 5.0.1 stock Google ROMs. Don't worry about factory images because you will lose everything once you flash these and it's a much bigger pain imo to back everything including internal on your phone up.
snappycg1996 said:
Don't worry about factory images because you will lose everything once you flash these
Click to expand...
Click to collapse
Not necessarily true.
You can flash bootloader, radio, and system without losing anything. You'll just have to reroot afterward.
DISCLAIMER: Since this is a third-party supplied file, flashing this file places any and all outcomes on YOU, the flasher (get your mind out of the gutter, thanks.) This file, though supplied by Samsung Kies 3, may cause issues or have undesirable effects. What these effects are, I have no clue. If you have a custom recovery, it will be overwritten with the stock recovery. Again, if you use this, you are the one responsible for any negative outcome.
This the official stock ROM flashable via Odin. This took me a few hours to download several times and locate the temp directory that housed it. It is a 2.12 gig tar.md5 file. Since Samsung does not have an open source copy for us to download, I used Kies 3 to download it.
FLASHING INSTRUCTIONS:
Using the most recent Odin, put the file in the AP section and flash it.
Link
Thank you so much it fixed my bricked device!
Thank you so much - Accidentally upgraded firmware and lost root and could not re-root. Worked like a charm and used kingroot to gain root again. You rock!
It downloads as a .RAR file if converted to .TAR, ODIN can not load it. How can the .rar file be used by ODIN?
bunivers said:
It downloads as a .RAR file if converted to .TAR, ODIN can not load it. How can the .rar file be used by ODIN?
Click to expand...
Click to collapse
The flashable .Tar file that you will use to restore your device via Odin, is located inside the .RAR provided in the download link. Once the .RAR file has been unrared/unzipped using 7zip, you will have your restore .Tar file that you're referring to. If you need to, you can Google 7zip and download it. The program is free and open-source, and it supports .RAR .TAR .ZIP etc. Happy Restore!
@jaywillsoul Please add to the OP that this firmware will wipe the device.
Thanks again for the firmware!
Sent from my XT1528 using XDA Labs
I was able to un-brick my wife's Verizon Core Prime with this. Thank you for your time and effort, @jaywillsoul.
Donation sent.
Fail
I downloaded the firmware, began to flash and Odin wrote "FAIL", and the screen after turning on is "Software update failed. Your device didnt update successfully. Use the Verizon Software Repair Assistant on a computer to repare your device and complete the update." But the Verizon Software Repair Assistant after this can not find the phone.
Thank you for this wonderful gift to the underdeveloped Core Prime! :good: worked for me and I was able to root afterwards!
is that process unlock the sim card lock for Verizon
ty it work's. I can root now
Sorry to bump this thread, but will updating through recovery mode end up wiping all the data of the phone? (like pictures, and files)
I was dumb and didn't enable usb debugging before my phone got soft bricked, now it freezes on the carrier animation
My phone is a model SM-G360T1
Link999123 said:
Sorry to bump this thread, but will updating through recovery mode end up wiping all the data of the phone? (like pictures, and files)
I was dumb and didn't enable usb debugging before my phone got soft bricked, now it freezes on the carrier animation
My phone is a model SM-G360T1
Click to expand...
Click to collapse
You have the wrong model - this guide is for the G360V, not the G360T1. Sorry.
Hello,
My device is the Mate 9 (MHA-L29C185B110) and I seem to have a problem with the camera.
When pressing the button to take a photo, the camera app restarts itself. I try again, but didn't work, to no avail.
I also tried to record a video. It seems to work, but the camera freezes but it's still counting, otherwise recording.
I have just recently flashed a custom recovery img (TWRP), the boot img on another thread that prevents the device from being automatically encrypted, and SuperSU root.
Do any of you have a solution to this problem?
Would this be because I haven't flashed Public_data.zip and Full_HW_data.zip?
And will this problem fix if I completely install the MHA-L29C185B172's firmware?
SeanPHTRPW said:
Hello,
My device is the Mate 9 (MHA-L29C185B110) and I seem to have a problem with the camera.
When pressing the button to take a photo, the camera app restarts itself. I try again, but didn't work, to no avail.
I also tried to record a video. It seems to work, but the camera freezes but it's still counting, otherwise recording.
I have just recently flashed a custom recovery img (TWRP), the boot img on another thread that prevents the device from being automatically encrypted, and SuperSU root.
Do any of you have a solution to this problem?
Would this be because I haven't flashed Public_data.zip and Full_HW_data.zip?
And will this problem fix if I completely install the MHA-L29C185B172's firmware?
Click to expand...
Click to collapse
It could be a problem if you flashed a boot image for a different model. You need boot image for C185B110. It should work without hw and Public zips, but a lot of other things break without flashing those. Updating to C185B172 will fix it.
By the way, which supersu did you use?
If the one from the "Decrypt" thread in Guides you don't need to flash a pre-decrypted boot image, the installer does it for you.
ante0 said:
It could be a problem if you flashed a boot image for a different model. You need boot image for C185B110. It should work without hw and Public zips, but a lot of other things break without flashing those. Updating to C185B172 will fix it.
By the way, which supersu did you use?
If the one from the "Decrypt" thread in Guides you don't need to flash a pre-decrypted boot image, the installer does it for you.
Click to expand...
Click to collapse
As for the SuperSU, I think I took it from the full root guide w/o decrypt img, but obviously I had to use a decrypt img because of stock
SUPERSU-2.79-MATE9-init.d_support
For the boot (No force encryption boot)
This is probably where things went wrong. I flashed the wrong build image.
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
I had to use above link because I couldn't flash SuperSU since I don't have an external sd to extract it from (Since you have to format your data before flashing it)
I couldn't find the hw and public zips for C185B110, so if you have it, a link would be generous.
Would flashing stock boot img for MHA-L29C185B110 fix it?
and what would happen if i flash stock boot.img?
and do you have a decrypt boot.img for C185B110?
Thanks!
SeanPHTRPW said:
As for the SuperSU, I think I took it from the full root guide w/o decrypt img, but obviously I had to use a decrypt img because of stock
SUPERSU-2.79-MATE9-init.d_support
For the boot (No force encryption boot)
This is probably where things went wrong. I flashed the wrong build image.
https://forum.xda-developers.com/mate-9/development/stock-boot-img-library-t3573312
I had to use above link because I couldn't flash SuperSU since I don't have an external sd to extract it from (Since you have to format your data before flashing it)
I couldn't find the hw and public zips for C185B110, so if you have it, a link would be generous.
Would flashing stock boot img for MHA-L29C185B110 fix it?
and what would happen if i flash stock boot.img?
and do you have a decrypt boot.img for C185B110?
Thanks!
Click to expand...
Click to collapse
It would probably fix it yes, but no boot image or hw/public exist for B110 so I'm guessing it shipped with that build.
You'd have to update, using https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
I don't think you can use Firmware Finder as you're probably missing the System Update feature.
Either that one I linked or FunkyHuawei, but Funky cost money to use.
Thanks,
I will try using the link you used.
although it is not clear.
On manual update step A, do you need to download all three?
the base, the OS(windows) and the model?
and where do i put these files?
and on b and c on update zip
do i have to download two update.zip?
for example, C185B110 and C185B172
do i also need to download full ota instead of just ota? fullota is incompatible, says firmware finder on mobile
SeanPHTRPW said:
Thanks,
I will try using the link you used.
although it is not clear.
On manual update step A, do you need to download all three?
the base, the OS(windows) and the model?
and where do i put these files?
and on b and c on update zip
do i have to download two update.zip?
for example, C185B110 and C185B172
do i also need to download full ota instead of just ota? fullota is incompatible, says firmware finder on mobile
Click to expand...
Click to collapse
Yes, download base, os and MHA. Extract all to the same folder. You should only have one folder named HWOTA and the files/folders in that. If it extracts to a folder with the same name as the zips, enter the folders and copy hwota folder then go back one folder and paste/merge so you end up with one folder named HWOTA. Easiest way is putting it directly in C:\hwota\, if your windows version allows it. Else place it on desktop. (long file paths or a path containing spaces might make hwota not function correctly).
You need to download all 3 files (fullota update.zip, hw zip and Public zip), easiest way is using firmware finder to download. Either mobile or the pc version. For pc go to the common base tab and search for your model and then download the build you want including public and HW zips.
You only need to download the fullota update, hw and Public zip of the build you're updating to. If you're on b110 and going to update to B172 you only need to download B172.
Rename the files according to the guide (update.zip, update_all_hw.zip and update_data_public.zip), place them in either hwota/update folder or make a HWOTA folder on your sdcard and put the renamed files there.
When running hwota, select script update folder or sdcard update folder depending on where you put the files. Select same model update.
One last question:
Does it have to be FULLOTA, not just OTA?
Hello Everyone!
I am not an expert, but I'd to know, if I can change my actual Firmware "Italian TIM Carrier " to an Official Italian NO Carrier.
It's possibile to follow any guide or link here ?
Actually I have Firmware Nougat 47.0.A.7.137/R15A and i would to updgrade to Oreo 47.1.A.5.51/R2B
If someone could help me, I will thanks in advance.!!
Just download Oreo Italian customized firmware with Xperifirm (you can search for it with Google and download the application). This program would download first the desired firmware and then extract it. Search on xda forum for Newflasher application by munjeni, just download zip and extract it in the same folder where you have downloaded and extracted oreo firmware. Delete all .ta files present in folder and user.sin if you don't want to have corrupted data when turning on your phone after flashing it. Make a backup of your important data and staff present on phone first. Charge your phone completely, when ready, shut it down completely. Hold volume down button and connect phone to pc with his own USB cable. Run newflasher.exe and follow instructions prompted in Windows ms-dos prompt window, it would search for phone and than start flashing. Beware for your PC to not shutting down before is all completed. When flashing is over, turn on your phone and let it setting for a while. If you have any problems can use Sony pc companion application to reset it completely
Good job and pay little attention to what you would do
If not completely sure of what you are going to do just stop and ask. It's better than having a bricked device
Take a look here, that's the guide I followed for flashing my xzp first time :
https://forum.xda-developers.com/xz-premium/help/version-flashing-internation-version-t3629823/page2
Hello Tony
Thanks a lot about your tips... I can tell you.. I did it! Very happy. My Phone it is upadted to Oreo No Italian Brand.
What i did...
I download Firmware from Xperiafirm
I unzipped partion zip folder into the same folder "firmware donwloaded"
I downloaded newflasher, and unzip it into the same folder of official firmware.
I run the newflassher apps, and wait to complete the operation.
Ths a Lot, very happy.
Tonyevol said:
Just download Oreo Italian customized firmware with Xperifirm (you can search for it with Google and download the application). This program would download first the desired firmware and then extract it. Search on xda forum for Newflasher application by munjeni, just download zip and extract it in the same folder where you have downloaded and extracted oreo firmware. Delete all .ta files present in folder and user.sin if you don't want to have corrupted data when turning on your phone after flashing it. Make a backup of your important data and staff present on phone first. Charge your phone completely, when ready, shut it down completely. Hold volume down button and connect phone to pc with his own USB cable. Run newflasher.exe and follow instructions prompted in Windows ms-dos prompt window, it would search for phone and than start flashing. Beware for your PC to not shutting down before is all completed. When flashing is over, turn on your phone and let it setting for a while. If you have any problems can use Sony pc companion application to reset it completely
Good job and pay little attention to what you would do
If not completely sure of what you are going to do just stop and ask. It's better than having a bricked device
Take a look here, that's the guide I followed for flashing my xzp first time :
https://forum.xda-developers.com/xz-premium/help/version-flashing-internation-version-t3629823/page2
Click to expand...
Click to collapse
Good to know it's all fine :laugh:
Um... So, apparently he did not "delete all .ta files present in folder and user.sin", and all went well. So, is it necessary to "delete all .ta files present in folder and user.sin" or not? And if it is, whey are these files even included into the download?
TheKorbenDallas said:
Um... So, apparently he did not "delete all .ta files present in folder and user.sin", and all went well. So, is it necessary to "delete all .ta files present in folder and user.sin" or not? And if it is, whey are these files even included into the download?
Click to expand...
Click to collapse
When I flashed my us dual SIM to fr firmware using newflasher, I flashed everything downloaded from xperiafirm I did have to reinstall apps and logins, but umid rather have a fresh start. I flashed to enable the fingerprint scanner
Sent from my [device_name] using XDA-Developers Legacy app
I live in pakistan, i need international Ftf file link. Please provide download link
please provide and also tell me what i need to select in flash tool during flash.
thanks
Still no reply..
S8232 or g8231???
Im confuse here... S8231 OR G8231? SOV35 AND G8231 its the same phone right?
xperifirm & effort
It's quite simple, you have to edit the firmware.xml file from the download folder in your flasher before packing the .ftf . I don't know what .ftf you need but if you have flashtool with xperifirm plugin you should be able to select your customization of the oem rom of your choice. Edit the file (firmware.xml) while you have xperifirm open in your rom downloads folder, change the tagged info where the model written is 8321 to SOV35. Then close xperifirm and the .ftf will bundle as SOV35 instead of 8321. When you flash the phone the system firmware itself will write/update the phone to 8321. You might get an error or two, flashing it again right after should get rid of those. Make sure you know how to create the partition folder with the right contents for XZ and later models. A bit late, let me know if you still have it and are successful.