Hey guys,
I tried flashing the November factory image, but my phone still says that it's on the stock (October) firmware version.
It's an unlocked, Google Store devices on Verizon. I flashed the QD1A.190821.014.C2 version (and it seemed succesful), but phone still says its on -.007. Rooted with Magisk prior to flashing but disabled all mods.
I tried to flash twice with the same results. Any idea? What am I missing?
well what did the flash log say it must have failed, update your platform-tools, change usb port on pc, change usb cable (or flip the usbC connection sometimes that works in a cable were one of the pins is bad), those things fix 99.9% of non syntax/user errors with fastboot flashes.
I also have Gstore version unlock and rooted no issues on update. Platform-Tools was updated since last release, that may have caused issue but not sure because i updated before the flash....
I had problems with the versions. I was on the .007 October version (bought unlocked from Google). Figured since I'm on T-Mobile, I'd flash the image that was for T-Mobile .014. Turned out it didn't take and it broke the Face Unlock. As soon as I flashed the .007.A3, it's working beautifully. Maybe since you were on .007 before (like me), try the .007.A3?
Well, I updated platform tools and flashed the C3 build and it worked like a charm. Not sure what the issue was, but one of those def fixed it!
Related
[History]
I suspect the phone was edited before
bought the phone used. It is unlocked. The phone was constantly rebooting, I bought a lemon from some low life.
Sent the phone in to Rogers [Canada] to get fixed.
Rebooting was fixed (YEAH!).
I proceeded to unlock the bootloader and install ViperOne.
Once ViperOne was installed, I noticed the camera wasn't working.
NOTE: I did not A) check if the camera worked once I got it back. B) I didn't update my phone from STOCK when I got it back.
[Where I am now]
relocked the phone.
I used the Signed RUU exe from htc1guru -- Rogers edition.
I then used the stock ROM to update the phone.
M7 is now Lollipop.
Still no Camera.
Unlocked phone, installed newest TWRP, newest ViperOne [8.0.0.0, I believe].
no camera, but I was expecting that haha.
[Specs]
See Attached.
Thoughts, suggestions?
I had the same issue as you have.
There may be two areas of investigation.
a) Faulty Camera - failing to initialise and therefore creating an error.
Solution - get a new camera replaced.
b) Daughter board may be faulty.
Solution - get a new replacement daughter board.
c) A combination of both.
Hope that helps.....?
cheers
_FBi said:
[History]
I suspect the phone was edited before
bought the phone used. It is unlocked. The phone was constantly rebooting, I bought a lemon from some low life.
Sent the phone in to Rogers [Canada] to get fixed.
Rebooting was fixed (YEAH!).
I proceeded to unlock the bootloader and install ViperOne.
Once ViperOne was installed, I noticed the camera wasn't working.
NOTE: I did not A) check if the camera worked once I got it back. B) I didn't update my phone from STOCK when I got it back.
[Where I am now]
relocked the phone.
I used the Signed RUU exe from htc1guru -- Rogers edition.
I then used the stock ROM to update the phone.
M7 is now Lollipop.
Still no Camera.
Unlocked phone, installed newest TWRP, newest ViperOne [8.0.0.0, I believe].
no camera, but I was expecting that haha.
[Specs]
See Attached.
Thoughts, suggestions?
Click to expand...
Click to collapse
Best suggestion so far haha
Thanks!
I updated my moto x4 from Oreo to pie using flash using boot loader. my boot loader is still locked and software status is official too. It still is unable to update to January security update. Please help !!
yes I have also facing same issue... i have also try by safe mode but shows something not right .... reconnecting to server... might be Moto update Services try to connect moto server which has not able to connect due some issue in server... hope so this is issue...
you can connect to moto support team let me know what they are say for this issue.
They told to reset and try again.. to do that I got to backup my data which LL take time.. so on hold as of now
Yup, same here. I got the Android 1 Google Fi model (Bootloader unlocked, unrooted). I'll try again in a week and see if it resolves itself.
And another ~ bought 2, mine showed the update 3 days before my wife's but won't start (download and install now, via wifi only and it reverts back to the settings screen). She got the notification last night and it took first try. First time I've had this issue in the 4 months I've had the phone, just glad I'm not alone here....
Since you're official/fully stock, there's not really any alternatives besides factory reset or await for full image is available to manually flash via fastboot method. You do not need to unlock long as you stick with motorola firmwares. Links in FAQs thread.
Nothing new here? Mine keeps nagging me to do the update, start it and it shows getting to 17% on step 3 of 6, then just kicks me back out to the setting screen.
This is my first android phone (from a flip), couldn't get lineageos to work with my provider (RedPocket) and have neutered as much of the google crap as possible. Right on down to disabling all permissions for Play Store. Could that be part of my issue?
It has been nagging me since last few weeks, no solution apparently
New Update:
Could actually able to fix the issue by installing a vpn and set it as a USA based server.
My phone was bought in US and I was using it elsewhere. After using an USA based IP it downloaded the update and voila.
Hello, I had tried posting this where I assume it belongs but I can't seem to post anywhere but here. Anyways, today me and a friend rooted his ROG Phone 2 via rooted ROM we had found here. Everything had gone to plan, unlocked the boot loader with Asus's tool, fastboot the custom ROM, ran Magisk and let it update, confirmed root with it and a cheapo Play Store root checker, all was good.
First issue, WiFi didn't work, but no big deal, unlimited data. Then he discovered that sound didn't work, so I immediately looked it up, didn't find a post specific to his phone but someone mentioned the mic not working in the one I read, gut feeling I told him to check the mic, loe and behold, not working.
He doesn't want to have to reset to factory ROM and lose the root. Ant idea what's wrong? I could find the post we followed if requested before I find and post it anyways.
As mentioned it's the new Asus ROG Phone 2
Model
ZS660KL
The 512GB/12GB RAM
As far as I'm reading is there shouldn't be any exact issues and is no particular reason. We read later on in the comments, someone had the WiFi issue but the OP assured his didn't have the issue.
WiFi isn't a major need, again, data. But the sound and mic is a huge issue as it's his daily. I'm familiar with rooting and custom ROMs, mainly Samsung's. I'm quite confused, I've never had a major issue with a ROM that doesn't have a simple work around.
What firmware version is he on? He has to make sure that the magisk-patched boot image matches the firmware he has installed or he will have issues like the ones you describe with WiFi, sound, and possibly abnormally long boot times.
This is a boot image issue
Had the same issue when rooted.. i flashed the ww rom again to unroot my device now everything works. Hopefully someone can give a solution
He's working on patching a fresh ROM from Asus, that's the only idea he can make right now.
Hi all
I have re-posted this to the G7 plus forum, I mistakenly posted it in the G7 forum previously.
I have a Motorola G7 Plus XT1965-3 RETGB, after being pestererd by the update to android 10 mesage for several weeks, I finally agreed, since then, the phone fails to work with my in car head unit bluetooth connection.
It pairs, and will stream music from the phone through bluetooth to the head unit, just will not work as a hands free phone.
The head unint is a Kenwood DNX4230DAB, it shows the device connected as A2DP, but the phone (HFP) just shows connecting forever, before the update to Android 10, it worked flawlessly.
I've tried doing a full device reset, didn't help, and following various things posted on forums on the web, again no luck, the phone is unrooted, and the bootloader is locked, it is essentially as was when purchased other than the Android 10 OTA update.
Can anyone tell me is it poossible to roll back the Andoroid 10 update, I should never have done it in fairness, i've been bitten many times before with updates breaking stuff.
If anyone has any suggestions as to how to get the handsfree calling working again, or can offer a easy to follow guide on how to roll back to Android 9, I would be super grateful, I need to get the device working as a handsfree phone before I go back to work this week if at all possible.
Hoping someone can help.
I have an similar issue. On LOS17 the phone app works well with bluetooth but all the other voip apps like zoiper, bria or groundwire dont. the audio over bt is one way only
Regarding your issue: I afraid an OTA downgrade is not possible. However with fastboot you should be able to flash every stock you want as long as it is stock
Unfortunately, I tried to flash the stock Android 9 retgb rom, now the phone is a brick!
I wasn't aware that you need to unlock the bootloader before you flash the rom, so now it will no longer start
k4tfish said:
I have an similar issue. On LOS17 the phone app works well with bluetooth but all the other voip apps like zoiper, bria or groundwire dont. the audio over bt is one way only
Regarding your issue: I afraid an OTA downgrade is not possible. However with fastboot you should be able to flash every stock you want as long as it is stock
Click to expand...
Click to collapse
You only need to unlock the bootloader when you are downgrading or switching to another version, like from retus to retbra, saying this, you phone turns on? does it do anything? maybe you just need to flash the rom again, you can go here: https://mirrors.lolinet.com/firmware/moto/lake/ and find the firmware for your phone, you may have to flash it manually, i have tried to flash the firmware for my phone with RSD Lite but it says that its not in bootloader, if you are flashing the same build that you had or a higher build you dont need to have an unlocked bootloader, just check the dates and the build numbers to make sure that its the same you had or a higher one, just search how to manually flash it, if its really bricked, that it will not boot into bootloader, you can use blankflash to save it, just search on the forum
Hi everyone,
Need some serious help please,
I have a xqat52, bought in January 21.
In the UK, on three the handset would not go into 5G.
After reading up, I decided to flash xq-at51 successfully to the UK rom. Everything was working lovely...
Received OTA updates and never had issues with updates or Google.
Device was certified and google pay and bank apps work fine.
2 weeks ago I received ota update and since then my device is no longer certified.
1 week ago received another ota now build 58.1.A.5.507 and device is still not certified.
I tried experia companion full repair with no luck, still same issue.
I sent the handset to Sony Uk for repair, and they factory reseted it back to stock XQat 52, but the device still shows as not certified and bank app and google pay no longer works,
at this point I am thinking in rooting my device and use magisk....
my bootloader is locked, never unlocked (i checked and so did Sony) but I am able to unlock it...
what do you guys think I should do, I want it to be a XQat51 for Uk and have it certified or rooted hidden.
any advise will be really appreciated, and this will bring back memories of rooting android when i had my HTC and where it all started
Thanks in advance
Update.
Went the rooted way. Not looking back.
Not so simple, but we'll worth it
Plenty of google search.
Android Kitchen which I didn't use before
Didn't really have a choice to get my 1ii working properly again.
All repairs / flash stock did not help no matter what I flashed UK / eu dual Sim / single Sim
Back to full stock from Sony HK version still didn't help
My android is now how I want it.
Shame on Sony for not helping and still waiting for a response.
Google store device now certified again.
Google pay working again.
All banks working
Fingerprint working
Netflix l3 not l1 but I don't use anyway.
Cinema Pro and photo Pro working
4k creator mode and Sony dynamic vibration working
Full root permission and able to customise like I use to when I 1st started with kitkat
Android is going down the apple way unfortunately, not so open anymore...
Good luck to anyone doing the same,
xdamanu1000 said:
Update.
Went the rooted way. Not looking back.
Not so simple, but we'll worth it
Plenty of google search.
Android Kitchen which I didn't use before
Didn't really have a choice to get my 1ii working properly again.
All repairs / flash stock did not help no matter what I flashed UK / eu dual Sim / single Sim
Back to full stock from Sony HK version still didn't help
My android is now how I want it.
Shame on Sony for not helping and still waiting for a response.
Google store device now certified again.
Google pay working again.
All banks working
Fingerprint working
Netflix l3 not l1 but I don't use anyway.
Cinema Pro and photo Pro working
4k creator mode and Sony dynamic vibration working
Full root permission and able to customise like I use to when I 1st started with kitkat
Android is going down the apple way unfortunately, not so open anymore...
Good luck to anyone doing the same,
Click to expand...
Click to collapse
I'm glad for you.
I just bought a second hand XQ-AT51, and didn't noticed when I bought it that the Wi-fi and Bluetooth are not working.
And also that the bootloader is unlocked, and it seems that fast charging is not working.
Everything works fine as far as I see (camera, features).
I don't know what the previous owner did.
I didn't find anybody saying about Wi-fi and Bluetooth not working after Bootloader unlock/root Xperia 1 ii.
I tried locking bootloader and Xperia Companion software repair, same version 58.1.A.5.507 (as I see the latest) before repair and after.
Nothing changed.
Then I unlocked the bootloader, flashed twrp as recovery (probably not necessary in my case) and flashed the stock software with Flashtool, latest (the same as before) from xperifirm. But I got some messages some things didn't flashed (didn't save the message).
Still the same.
Do you have any idea about DRM keys needed (as I know older Xperias pretty much lost the camera without backup and restore to some files)
Or do you have any "spare" backup files that I might need and work for different devices?
Thanks!
n8f said:
I'm glad for you.
I just bought a second hand XQ-AT51, and didn't noticed when I bought it that the Wi-fi and Bluetooth are not working.
And also that the bootloader is unlocked, and it seems that fast charging is not working.
Everything works fine as far as I see (camera, features).
I don't know what the previous owner did.
I didn't find anybody saying about Wi-fi and Bluetooth not working after Bootloader unlock/root Xperia 1 ii.
I tried locking bootloader and Xperia Companion software repair, same version 58.1.A.5.507 (as I see the latest) before repair and after.
Nothing changed.
Then I unlocked the bootloader, flashed twrp as recovery (probably not necessary in my case) and flashed the stock software with Flashtool, latest (the same as before) from xperifirm. But I got some messages some things didn't flashed (didn't save the message).
Still the same.
Do you have any idea about DRM keys needed (as I know older Xperias pretty much lost the camera without backup and restore to some files)
Or do you have any "spare" backup files that I might need and work for different devices?
Thanks!
Click to expand...
Click to collapse
I flashed xq-at51 from Xperia with flasher.
I don't think drm will affect Bluetooth or WiFi?
Mine are lost anyway, once bootloader unlocked its gone! I was prepare to loose them.
Connectivity issues you mention I
Never had that problem despite locking unlocking bootloader and flashing various rom xqat52 HK or Asian and xq-at51 UK and EU.
Might be something else you are experiencing on the phone directly , run a sony test through the app "support" it has a connectivity section. Might give you a better idea before flashing anything else.
I think you can also do it via phone codes *#.......
Google it, it will enter service menu, you can test your handset this way too.
Thanks for the suggestions, I didn't think of trying Support.
But forgot to say, in the Settings at About it says MAC address unavailable for both Wi-fi and BT.
With code *#*#4636#*#* it says Wi-fi Mac address 02:00:00:00.....
As I found some older forums for other devices with about the same issue and being from flashing not proper firmware, I honestly don't know what's going on, since I flashed the stock firmware again, maybe some files are not flashed again because I'm flashing over the same firmware.
Hopefully, I will find a solution.
n8f said:
Thanks for the suggestions, I didn't think of trying Support.
But forgot to say, in the Settings at About it says MAC address unavailable for both Wi-fi and BT.
With code *#*#4636#*#* it says Wi-fi Mac address 02:00:00:00.....
As I found some older forums for other devices with about the same issue and being from flashing not proper firmware, I honestly don't know what's going on, since I flashed the stock firmware again, maybe some files are not flashed again because I'm flashing over the same firmware.
Hopefully, I will find a solution.
Click to expand...
Click to collapse
Latest ver of flasher ? V52
With flasher, if I remember correctly
I chose command a android reboot
N to dump (did once the 1st time as a backup)
I did choose partition persist
No to everything else.
Maybe try and repair with companion make sure it gets back to factory stock rom with correct variant.
Do a factory reset within the phone
(I know I did several, after each flash)
Then reflash with flasher, also might be worth redownloading a clean rom and put in a new folder, so it's clean and not changed.
Add flasher (latest) to that folder and do another clean install.
The rapair tool from Sony failed few times on me, not sure why, but sony software somehow still knew my Xperia 1ii was originally a xq-at52 and would not repair / so I had to flash using flasher xq-at52 stock rom, then repair then flash back using flasher to xq-at51.
Sony repair if successful is your best bet... Once repaired properly you can do it again and again.
I just realised you mention flash tool, use flasher. Exe no issues...
Download from Xperia firm your rom. (always the same or higher)
Downloader flasher (latest)
Few files to copy straight into the same folder as the extracted Xperia firm folder.
Run the flasher. Exe
Follow instructions
Should flash everything correctly.
I bootloop mine and bricked few times...
Flasher rebooted it every time.
xdamanu1000 said:
I just realised you mention flash tool, use flasher. Exe no issues...
Download from Xperia firm your rom. (always the same or higher)
Downloader flasher (latest)
Few files to copy straight into the same folder as the extracted Xperia firm folder.
Run the flasher. Exe
Follow instructions
Should flash everything correctly.
I bootloop mine and bricked few times...
Flasher rebooted it every time.
Click to expand...
Click to collapse
Thanks, I didn't knew about newflasher.
But I see that it's skipping persist (flashtool was also skipping persist)
Skipping persist_X-FLASH-ALL-2389.sin
And also
Skipping partition-image-LUN0_124936192_X-FLASH-ALL-2389.sin
And I read somewhere that it's skipping .sin that are not matching.
But maybe if I flash them I will solve my issue.
As I see older versions have the options to write or skip. Did you write it? If I write it I will lose attest keys? Because at mine it says Android Attest Key Provisioned after relocking the bootloader, but was Not Provisioned before.
I guess I have to backup persist.sin if I want to flash it and for that I need to root.
Do you think that flashing persist might solve my issues? Or it will give me more issues