Related
Hello to all Devs and fans at XDA who see my first post. For years I have watched the community and benefited from the knowledge they shared on the smartphones frontier. But today, I humbly ask for a hand from whoever might be be able to provide me with what I need.Here is situation:
1- I do hate Sony firmwares of Android 4.3 and the new 4.4 firmware because I want to stay LB and I do need to root and mount SYSTEM partition
which are difficult on such firmwares and I simply don't like deodexed flashable roms dear devs here provide.In my opinion Android 4.2.2 FW 14.1.G.2.257 seems to be the best one for me...but how to get this one rooted and stay odexed on LB? here are the steps I took :
2- I was on 4.3 and when i went to 14.1.G.534 my phone lost IMEI and GSM SIGNAL and couldn't OTA to 14.1.G.2.257(much to my surprise the phone downloaded the OTA update but the installation failed, so I flashed 14.1.G.2.257 and then went all the way back to the first firmware of z1 which is rootable: 14.1.G.534
3- I rooted this firmware with Kingo root , updated superSU Pro to the latest version enabled survival mode in its settings and installed recovery but now the OTA updater on the phone detects Android 4.3 FW 14.2.A.0.290 and I have no clue how to make it OTA to 14.1.G.2.257 NOT 14.2.A.0.290. As of now, I am stopped here and wondering if a small flashable zip with my desired OTA update could be provided to solve my problem or any other idea how to have my phone in the desired state...
Your help is highly appreciated :crying:
I'm not sure but I believe that not all firmware versions allows for OTA update from 534 to 257. You might have flashed a 534 firmware that only allows for OTA from 534 to 290. Have you tried the firmware from this thread?
If you are already on the firmware in the above thread, it may be the case that the OTA to 257 is just no longer available. You'll have to flash a de-odexed and pre-rooted 257 firmware (e.g. here).
Thank you for your reply. I am indeed on the firmware you mentioned. If you noticed I had said if Iflashed directly from 290 to 534 I would lose IMEI but my phone detected 257 for OTA update but when it restarted to install, it failed and i was back with no change. If I downgrad from 290 to 257 and then to 534 I will have IMEI and signal back but this time 290 is detected for OTA.Yeah i read the post related to my firmware but I don't need a deoexed rom and I don't know how to redoex it if using that would be my last choice.
hfaz63 said:
Thank you for your reply. I am indeed on the firmware you mentioned. If you noticed I had said if Iflashed directly from 290 to 534 I would lose IMEI but my phone detected 257 for OTA update but when it restarted to install, it failed and i was back with no change. If I downgrad from 290 to 257 and then to 534 I will have IMEI and signal back but this time 290 is detected for OTA.Yeah i read the post related to my firmware but I don't need a deoexed rom and I don't know how to redoex it if using that would be my last choice.
Click to expand...
Click to collapse
On NUT thread you'll find firmware 534.
You can flash that one from 4.3 or even 4.4 and you'll preserve IMEI.
Without IMEI you can't update firmware through OTA so, probably, that was the problem.
Now you should be able to update firmware through OTA.
If that fails or OTA offers latest firmware you don't want to use you can try to find flashable firmware 290 but I doubt we have that...
Sent from my C6903 using Tapatalk
OK i think I know what is going on but could I have a rooted UN-DEODEXED 14.1.G.2.257 on my z1??The method you proposed for upgrading to 257 and keeping root now want's to install 290 on my phone....I wish to install 257 NOT 290
I searched but couldn't find any rooted un-deodexed 257 firmware, and that's why I didn't point you to one in my previous post. I think most of us upgraded via OTA to 257 and kept root, hence there wasn't a need for a developer to create a rooted un-deodexed 257 firmware.
Hi,
Finally since November we are getting an update, but it isn't Marshmallow.
The update N9200ZHS2APC1 was out on March 24, and weighs only 40mb.
We can see that the build for HK is now ZHS2, unlike before which was ZHU2.
Changelog mentioned only security (we got March 1st security update, yay!) , but my theme store got updated and now looks like the S7 theme store: white with 3 rows in most popular.
I got it in OTA, but quick google search gave me this:
Mod Edit
Update: I think it comes with samsung pay framework, it is uninstallable.
Update 2: HK N9200 getting Marshmallow update, build N9200ZCU2BPC4
Mine said something about preparations for future upgrades but come on... 5 months without updates for this?
I just got the update to Mm for Hong kong version
N9200 - HK update OTA MM today. please check OTA
dunghaha said:
N9200 - HK update OTA MM today. please check OTA
View attachment 3700369
View attachment 3700370
View attachment 3700371
View attachment 3700372
Click to expand...
Click to collapse
I just got Marshmallow, Updating now. Thanks dunghaha
Checked my phone yesterday and I have a 10D update, released on November 17, size at 690.97 MB, this is for the H990N, has anyone come across it and updated.
Any update on the changes.
When does an OTA come for L31-C150? Still on Marshmallow, don't want to update with dload.
Jhnsn said:
When does an OTA come for L31-C150? Still on Marshmallow, don't want to update with dload.
Click to expand...
Click to collapse
For C150 is available version B360/B361.
You can update with Firmware Finder via Proxy... Is almost like with OTA...
Is it really only 982 mb big?
No. It should be 1.94GB. Everything under 1.9GB is a test build which will be missing apps. If you find in firmware finder a full ota update C360 or C361 or C370 or C371 at about 1.94GB do the update via system update but check that the updater is really downloading 1.94GB and not a smaller package.
But there's no full package. Only a OTA which is 982 mb big. Should I install it? Bootloader locked, no root.
Jhnsn said:
But there's no full package. Only a OTA which is 982 mb big. Should I install it? Bootloader locked, no root.
Click to expand...
Click to collapse
Man, you have to find:
- VNS-L31C150B360 FullOTA-MF-PV - 2,229GB
- VNS-L31C150B361 FullOTA-MF-PV - 2,229GB
- VNS-L31C150B360 FullOTA-MF-PV - 2,230GB
- VNS-L31C150B361 FullOTA-MF-PV - 2,230GB
For VNS-L31C150 is not available B370/B371
Lots of people are getting the OTA from Beta 6 but I've not seen anyone yet coming from Pie.
So please only those on Pie let us know when you get the OTA, the size (no screen shots please) which carrier you're on, which device ( I will not cross post this) and whether you are bootloader unlocked or not. Identify if you have root if you wish. This way we don't have to hit every thread that states OTA is live which we already know. TIA
edit: figures, I jumped the gun. As soon as I posted this I got the OTA from Pie. I'm on a Pixel 3, Google brand, Verizon sim, bootloader locked. Update size 1337.4 Mb.
edit2: Pixel 3a on Fi, bl locked, Google phone, update from Pie just arrived at 1188.7 Mb. I'll post the versions after reboots.
Final edit: Pixel 3 on VZW got .20 update P3a on Fi got the .19 update
Got the OTA right now
Size: 1188.8 Mb
Carrier: Wind (Italy)
Device: Pixel 3a - Pie - Unlocked
EDIT: version installed QP1A.190711.020
Checking In!
.bucch said:
Got the OTA right now
Size: 1188.8 Mb
Carrier: Wind (Italy)
Device: Pixel 3a - Pie - Unlocked
Click to expand...
Click to collapse
Size: 42.1 MB (update/upgrade from RC2)
Carrier : T-Mobile/Tracfone (MVNO/USA)
Device: Pixel 3a (sargo) (unlocked)
got the ota (USA, MST) 1188.7 MB. Has anyone sideloaded this OTA or does it require a reflash over 9? (rooted and have twrp)
bonfire62 said:
got the ota (USA, MST) 1188.7 MB. Has anyone sideloaded this OTA or does it require a reflash over 9? (rooted and have twrp)
Click to expand...
Click to collapse
I sideloaded it because I didn't want to wait for the OTA to be pushed out to me. I was on Pie. I sideloaded the .020 version and it did not wipe the phone during the process. It was actually pretty quick to install and then it took about 5 minutes for the phone to completely boot the first time. Don't get impatient and just let the phone do it's thing.