Z3 sony sol 26 not showing any unlocking menu - Xperia Z3 Q&A, Help & Troubleshooting

i have a sol26 for unlocking,i have got the codes for it through online server but i dont know how to enter the code, when i insert the sim card it just says no service and not showing any unlocking menu

Before making any manipulations in Flashtool be sure that "Unknown sources" is allowed in Security and "USB debugging" is on in Developer menu. Be sure that connection with PC is stable (USB is quite fragile on Xperia devices esp. with time, when flashing anything never interrupt connection) and the PC is always trusted on phone after USB connect.
In the Flashtool Xperifirm download same firmware that you have now (KDDI) but only for Docomo carrier Z3 version phone and install this completely. The last one is Lollipop 5.0.2 (if you are on Kitkat - you can upgrade by installing first KDDI 23.1.G.2.244-Lollipop 5.0.2). Before installing i recommend reset and erase all on device to factory setting. After you install Docomo version put the sim card and unlocking menu appears. I recommend using only Japanese OS versions - because you don't loosing the 32Gb storage, on european version the storage is only 16Gb.
After successful code unlocking the phone function will be open completely forever - so you can even return on KDDI (Au) firmware back and not loosing sim unlock. I personally returned because there's specific japanese neat features which is missing on Docomo version - 1) no Private manager in Security, 2) no Accelerated GPS by Qualcomm in Location and others specific things. Take out sim card and just install downloaded KDDI Lollipop, after all done put sim inside. There's quite serious difference between Docomo & KDDI in phone function - esp. turning off LTE or other data-hungry, it's harder to change 3G to 2G on KDDI - you will need to do that manually in network preference (on Docomo it's much easily in menu).
I think you can easily safe sim unlock and install here a european Android 6 version which is latest, but you will loose 32Gb storage to the 16Gb and there will be no more specific japanese features like Accelerated GPS - which very very very helping with speed of GPS determination (almost on iPhone level, i tested - without it the GPS works much slower).
If you on Kit-kat beware that this all will upgrade you to Lollipop where's no specific KDDI "Face unlock" function anymore, it's deleted in 5.0.2. I want to even return on Kit kat but can't find old firmware file anymore anywhere - the 23.0.C.0.350, i think you can save sim unlock even there, but without Docomo you can't unlock sim and the Docomo is only Lollipop too.
I used Flashtool 0.9.22.3 on Win 7.

So, i've tried a different firmwares after unlock.
The KDDI (au) which is most rich by features are not really usable because of fixed number prefix with calling every time. The sim card is recognized, it's ok, but the phone putting a prefix to every number you calling. How to remove that prefix i don't really know, no settings for that, maybe it's need to be rooted and manually do something with code.
there's other models of compatible Z3 firmwares with 32Gb storage:
D6616-USA old
D6646-USA Marshmallow 6.0.1
D6708-USA old
401SO-Japan Android 5.1.1
• 23.1.G.2.244 KDDI 5.0.2 - everything work except call - fixed number prefix. Even step counter works, from version 5 new charging optimization function like in all other Sony smartphones.
• same 5.0.2 Docomo - everything work, call is ok, but no special features like in KDDI, no privacy app manager, no Qualcomm express GPS.
• 23.0.C.0.350 KDDI 4.4.4 - same problem with call prefix, very good battery 8 days.
• 23.5.A.1.291 USA D6646 - 32Gb, NFC not working not tuned for japanese version, Call is ok (everything), GPS is very good & fast, Free Navigon automobile navigation app coming only with this firmware for all Z3 users (it works), step counter not working (Google Fit), bad battery showing - only 3-4 days, for multi-tasking need a root and little code changing (the function to use 2 app windows together is present here in developer but turned off by standard)
I'm not sure yet, but if battery will be really bad on 6.0.1 i will try 5.1.1 for 401SO model, where i think that NFC can work.

I deleted Marshmallow, too bad battery, only 3 days on one charge.
I was a fool, the 401SO firmware is also Lollipop 5.0.2, flashed normally but with some dancing of downgrading flashtool, it don't see this ftf even if you put it right, with flashtool back to version 0.9.20.
So, the only 5.1.1 for Z3 with 32Gb is only USA Verizon for D6708, but it's not flashing at all, some error with partition or etc. (i downloaded it by flashtool from Xprefirm).
There's a cumbersome method on japanese site to obtain OTA update for Docomo Lollipop to the Marshmallow, i'm too lazy to test it with all IMEI masking and etc. Standalone Docomo Lollipop even with unlocked SIM are not getting OTA update at all.
Other method which promised also root much easier and i'll try it - it's by putting on top of Docomo version the D6603 Global but with only kernel and system (appslog, cache, data wiped), so flashing 23.0.B.1.59 with 23.0.A.2.93. Not sure about result, but looks interesting.

Nah, i've flashed Developer Preview Nougat 7.0, the last one. Working quite good, sim unlock and phone works perfectly. The battery is good, people complained that it's bugged, i've noticed only like 2-3, the NFC not working here and storage only 16Gb, i want to test battery here, very good battery during screen off with that "Doze" function than Marshmallow like not spending a percent at all.
The Music app from Sony even installs here by Google store and it works, even equalizer work, no clear+, but with bass and surround.

Related

I just accidentally bought a rooted HTC M8 on eBay with issues. Should I keep it?!

I am in Australia and have just recently bought an HTC M8 on eBay which was originally listed as new, and factory unlocked for $530. A few days later I found out it was actually rooted now unlocked, but was originally locked to Sprint. This was confirmed by a Sprint Connections application update etc, and the root was confirmed by the SuperSU app that was already installed in the phone. I'm recently confirmed this by the Root Checker app.
My phone's software is Android version 4.4.2, HTC Sense 6, software number 1.54.651.8, HTC SDK api LEVEL 6.17, PRI version 1.52_003, Kernel version [email protected] #1 SMP PREEMPT, Baseband version 1.05.20.0321_2.
The phone is pretty functional for everyday use except for the following issues:
- The internet network settings had to be manually obtained from my carrier as the phone did not automatically pick it up.
- The internet seems slower than usual (Signal strength -79 dBm 17-20 asu) compared to my old phone (Xperia Z1), despite the settings being specifically on 3G/UTMS mode which is faster than having it on Global Mode, and the required setting with my carrier Optus.
- I cannot access anything under System Updates. i.e. Update profile, Update PRL, UCICC Unlock and most importantly, HTC software update. This update takes >20minutes to search to no avail. This error message at times pops up when I try selecting Update profile: “vDM Client has stopped unexpectedly. An error report will be sent to HTC to help us improve our products”. This error screen would pop up intermittently when my internet didn't work but, I rarely see it now.
- Wifi would randomly switch on. I've turned off all system selections that may be caused on this. I haven’t tried booting my phone into safe mode to determine if an app is causing this.
I don't know much about phones (I had no idea what rooting was until I looked it up to get a rough idea), so I'm wondering if you experts could be some advice
I'm planning on keeping the phone for about 2 years and wondering what issues I may receive from having a rooted phone with the already above issues? Would the phone play up more? Can I use my current android version for that period relatively smoothly?
I am able to return my phone for a full refund but I don't have a spare phone and don't want to go in to the hassle of doing so if I can keep the phone (I would prefer to leave them negative feedback on eBay to be honest ). What do you guys think?
Thanks in advance for any asisstance.
Update your phone to android 4. 4. 4
Sent from my SM-G530H using XDA Free mobile app
Just reflash the stock rom and relock the bootloader and everything should be fine.

No Wi-Fi on Nexus 5 - on any version of Android

The Wi-Fi on my wife's unrooted Nexus 5 (Sprint version) which was upgraded (via OTA) to Marshmallow last month suddenly stopped working last week. The slider would get hung while moving from Off to On (like it was trying to turn on) and therefore was not detecting any available Wi-Fi signals.
After trying many things, I eventually did the extreme and did a full factory data reset. No dice. Still not detecting anything.
Figuring it might be an OS issue with Marshmallow (given we're seeing a lot of forums indicating Nexus 5 issues based on Wi-Fi with both Marshmallow and Lollipop), we downgraded the OS first to Lollipop and then all the way back to KitKat (4.4). Still not working. At initial phone setup, the phone is not detecting any available WiFi signals and gets hungup trying to find networks for me to choose from - so I end up having to skip this step.
Any other tips out there on what I can try? Is this a sure sign of hardware problems? Don't think my wife's phone is under warranty any longer (have had it slightly over a year, I think).
PS - Now I can no longer even upgrade the phone (OTA, at least) from 4.4.4 because my phone is saying it needs Wi-Fi to download the update - with no option to do it over my data plan.
I'm in the same situation and it appears to be a hardware failure. The wifi chip can't be replaced so a motherboard swap is required.
You can upgrade to the latest stock ROM by flashing the entire ROM from a command prompt in Win7.
Plot thickens
So, I figured out a way to get the OTA's over LTE (by manually changing my phone's date up a week). While going through each OS update from 4.4 KitKat to 6.0 Marshmallow (about 5 or 6 rounds of them) my phone briefly was able to detect WI-FI, I believe during set up at 5.1.1 Lollipop - and I was able to get on my home network.
Probably should have just stopped updating after that, but definitely was not detecting anything after that. I lost it during one of the Lollipop updates - well before getting to 6.0. Not sure if WiFi was actually working well or not.
Maybe the chip is in the process of failing? Not sure but it seems like you are having better luck than me.
audit13 said:
Maybe the chip is in the process of failing? Not sure but it seems like you are having better luck than me.
Click to expand...
Click to collapse
I wish. Don't want to go through all those steps again after doing a clean wipe to have a fleeting glimpse of Wi-Fi.
pagalbengal said:
So, I figured out a way to get the OTA's over LTE (by manually changing my phone's date up a week). While going through each OS update from 4.4 KitKat to 6.0 Marshmallow (about 5 or 6 rounds of them) my phone briefly was able to detect WI-FI, I believe during set up at 5.1.1 Lollipop - and I was able to get on my home network.
Probably should have just stopped updating after that, but definitely was not detecting anything after that. I lost it during one of the Lollipop updates - well before getting to 6.0. Not sure if WiFi was actually working well or not.
Click to expand...
Click to collapse
Hi, pagalbengal. I'm having the same problems right now, and I wanted to check with you to see if there have been any developments with your situation over the past month. Still hopeless? Have you contacted Google tech support? Do they still even support this phone? Thanks for any info.
You guys might want to try reflash the modem firmware.
Couldn't get my wi-fi to work so I replaced the motherboard. Every stock and custom ROM I tried could not enable wi-fi.

[HELP] Problem with dual-sim firmware

Hello everybody!
I'm a user of Lenovo A536, and soon i decided to customize it. So i wanted firstly to install fresh version of stock. My phone is single SIM version, and after few hours of googling it looks like there is not singe SIM version firmware available for download. I tried about 5 different versions(last digits of releases):
*910
*725
*141115
*813
and maybe one more... And all is Dual-SIM.
After installing DS Stock ROM, everything seems OK, but, there is network issue. I'm available to use just GSM(2G) networks. My default SIM is SIM 2, not SIM 1 where WCDMA(3G) is setted by default. (Why is this really important to me: most of a day, i'm not at home, so slow network is like i don't have it. ) In SIM Managment there is no another SIM. Just SIM 2, and when i click on it, there is two options, SIM 2 and "off".
What have i tried more:
CODES
I have tried to dial *#*#4636#*#* but, i got two phone infos(Phone info 1 and Phone info 2) and "radio off" is not working as changing mode, on both of it.
Build.prop
I have looked what is seeking there... I saw option something like "...active.sim..." and it has value of 2, and i set that to 1, but that caused bootloop after rebooting....
APPS
I have downloaded some SIM Managers and try to enable/disable SIM 1, and to set 3G to SIM 2, but that was unsuccessful also.
Is there any way to change some system file which contains these settings, to disable one SIM, or just to change SIM 2 to SIM 1?
Or can you find correct singe SIM ROM?
I'm currently on MIUI 8.
Thanks to everyone for attention.
(I'm sorry to MODS if i have posted this thread on wrong place, or named it incorrectly)

Android Q Developer Preview 3 coming to Xperia XZ3

https://developer.sony.com/develop/android-q-beta
Someone tried it?
https://youtu.be/W6BzFQqtOKg
I tried, but the problem is that the Xperia Companion gives me an error saying that my device doesn't support Developer Preview.
I will try to flash a non Operator customized firmware.
Vampirelu said:
I tried, but the problem is that the Xperia Companion gives me an error saying that my device doesn't support Developer Preview.
I will try to flash a non Operator customized firmware.
Click to expand...
Click to collapse
That's what you will need to do. Carrier branded firmware not eligible for beta
Anyone try Camera2 probe APP on Android 10 Beta?
Maybe support RAW?lol
Mine had EE UK firmware, I changed to Custom US firmware to try the Q preview mode.
All I can say is that it's not worth to leave 9 behind just yet. It's pretty much stock Android without Sony stuff in it, kinda miss it already, but all in all I only noticed one bug.
Connecting earphones with Jack will still have the speakers playing music, but you're fine with Bluetooth connection.
The gesture thingy is pretty weird by the way, fortunately there's the option to go to the classic three buttons.
Don't know if this answers you question but here's a snapshot of the raw Info
Tried it last night, some of the open issues makes it quite unusable.
Setup wizard can sync down backup data from google account/cloud, but not restore via BT/Wifi from other Xperia device
Delay with black background after the “Android Beta” information is shown before entering home screen
Camera functionality and quality are limited compared to Xperia SW
Camera button press is not starting camera, but double press on power button starts camera
Chromecast does not work for audio/video as cast icon is not shown
Media playback support is not on par with Xperia SW.
External SDcard is not fully supported for media playback and MTP
Audio routing with PHF is not fully working
Adoptable storage is not supported
Sd card is basically useless. So is dual sim.
chadd1039 said:
Don't know if this answers you question but here's a snapshot of the raw Info
Click to expand...
Click to collapse
Thank you bro.
It looks still not support raw
Hope xz3 can use Gcam on Q
This is a copy from the website and seems to not give a full actual experience..... I've been using all day and it runs well .... The Google cam app that's in it is crap bit I've installed open camera and it works great ...... And I can also play videos and use the SD card as normal ... No issues ....... Google camera does not seem to be compatible as of yet .... Until it's developed specifically for Sony I guess
It seems more stable than the Android P Beta that was pushed for Xperia XZ2 Premium. I have it installed and using it without too many issues yet either. SD card is normal but camera is very basic. All apps installed and are running well also which wasn't the case with P Beta.
Out of curiosity, how many versions do Betas usually get?
I rolled back already btw, I was already missing all the quirks that Sony brought to this phone. Also that bug I mentioned earlier - about having headphones connected *physically* and still having sound coming out of the phone speakers - was annoying me.
I installed it right after it was announced and only sort of regret it. It's stable-ish but so many things have been made useless. I just got the xz3 two weeks prior so I'm still in my adjustment phase. I think I'll stick it out until the next beta in June. Lack of SD card slot use, camera that barely works... It's not pretty.
Beta time-line described here:
https://developer.android.com/preview/overview
I rolled back as well. I have been with Sony phones for twelve years and like the skin and apps also. I do enjoy test driving the new Android version as well but only temporarily.
In order to Flash a Customized UK version & update to Q, I unlocked the bootloader . Guys, do you know a way to lock it back, since Flashtool doesn't support it and also when I try from command lines it gives me command not found. Do I have a chance to restore it back to original state ?
Don't think so. No need to unlock bootloader to flash another regional firmware.
The folder 'c:\ProgramData\SonyMobile\Update Engine\[date]\localstorage\' contains the firmware downloaded by the Xperia Companion stored in *.file ~ 2.3 GB. I extracted and seems to be all the files that FlashTool downloads. Did someone tried to flash Android Q like this ?
Does it have Wifi calling for T-Mobile USA?
daviddem said:
Does it have Wifi calling for T-Mobile USA?
Click to expand...
Click to collapse
I don't know if it's network related or not, I'am on US firmware and Wi-Fi calling feature is missing. On Original firmware the feature was present.

Baseband / radio - what's the most stable firmware version?

I have been using a Droid Mini for many years now, and am still quite happy with it. One of my few complaints, is that the radio does not play nicely with Canada's Bell/Telus LTE network.
I've used the versions in both 4.2.2 (doesn't hand off to HSPA properly after a call or MMS, repeated service drop-outs) and 4.4.4 (hand-off is fine, but LTE connection is started/lost many times a day regardless of signal strength). While the latter one is an improvement, there are other weird bugs that seem to come with 4.4.4 ("this SIM is from an unknown source" errors which randomly kill your connection, prompting to connect to WiFi when opening apps even if all available relevant settings have been disabled).
I know the radio firmware from the Moto X is compatible, but I have a few questions before I start toying with this as it is my daily driver:
Is it OK to flash the radio partition from a newer major version? (Lollipop radio to Kitkat)
Is MSM8960PRO_BP_23255.140.93.00R the best option available? What is included with the available CyanogenMod releases?
Is the radio partition the only one that must be flashed to support this?
What's the easiest way to backup the partition before I try to update it?
Does anyone know if there is a working repository for the XT1030's stock images?

Categories

Resources