Related
Hey everyone,
Yesterday I installed the new 32.3.A.0.376 update on my 100% Stock Z5 (E6653) via the xperia companion.
After the update it was stuck in a bootloop (crashes and restarts shortly after the android animation finishes)
Here is the full timeline:
Update via xperia companion -> bootlop
Remove SD Card and SIM -> bootlop
Repair via xperia companion -> bootloop
Second repair via xperia companion -> bootloop
Flash Nougat with the flashtool -> bootloop
Flash latest non-nougat firmware -> it boots!
This time I did the update to nougat via OTA -> bootloop
Flash different nougat firmare via flashtool -> bootloop
Back to marshmallow...
Factory reset & Install update via xperia companion on a different computer -> bootloop
Install marshmallow, factory reset & Install ota update -> bootloop
So basically i tried every possible combination of installing the update without unlocking the bootloader or other things that might void warranty. It just won't boot!
What do you guys think might be the cause for this? And what can i try to get nougat working on my device before sending it in for a repair? Thanks!
how about cables? have you tried using different usb cables? how about non sony cables? or any other authentic original cable! like samsung usb2 ?
Cables? Sounds more like voodoo too me I mean I did the whole thing without any cables attached, too (OTA).
nbzklr said:
Cables? Sounds more like voodoo too me I mean I did the whole thing without any cables attached, too (OTA).
Click to expand...
Click to collapse
sir
when you tried all these possible combinations of flashtool, MM, N, repairs via sony pc suite etc even on different computer,
my question is did you add trying different usb cable in all this process?
and when you say you have tried different version N, can you be specific what build you tried?
YasuHamed said:
sir
when you tried all these possible combinations of flashtool, MM, N, repairs via sony pc suite etc even on different computer,
my question is did you add trying different usb cable in all this process?
and when you say you have tried different version N, can you be specific what build you tried?
Click to expand...
Click to collapse
I flashed 32.3.A.0.376-R4D and 32.3.A.0.376-R5D (one is with provider customization, one without).
And I just tried it with a different cable on a different usb port. But I'm afraid it's still the same result.
nbzklr said:
I flashed 32.3.A.0.376-R4D and 32.3.A.0.376-R5D (one is with provider customization, one without).
And I just tried it with a different cable on a different usb port. But I'm afraid it's still the same result.
Click to expand...
Click to collapse
sir if possible
1. kindly paste Flashtool log here ( of both machines )
2. what is the operating system of those two different pc's ? win 7 and/or win10
3. have you ever successfully flashed your xperia using those ssytems before? (considering driver issues)
4. flashtool 0.9.23.2 supports N (ONLY) any other version can't install it , so can u check what version of flashtool you used ( in both machines?)
thank you
YasuHamed said:
sir if possible
1. kindly paste Flashtool log here ( of both machines )
2. what is the operating system of those two different pc's ? win 7 and/or win10
3. have you ever successfully flashed your xperia using those ssytems before? (considering driver issues)
4. flashtool 0.9.23.2 supports N (ONLY) any other version can't install it , so can u check what version of flashtool you used ( in both machines?)
thank you
Click to expand...
Click to collapse
To answer your questions:
1. I currently don't have one but I do not recall any errors appearing in the logs.
2. I'm using windows 10 and yes, drivers were installed correctly (by booting the system with signature checks disabled)
3. I did successfully flash marshmallow (32.2.A.5.11) multiple times after the failed nougat update.
4. My version of flashtools matches 0.9.23.2
I tried to update the the phone multiple time using official tools (OTA, xperia companion) before resorting to flashtool.
This, and the fact that flashtool works well otherwise, means the issue is with my device and/or the update itself and not with flashtool.
Is it possible to get some log files out of the device to see what's causing the crash?
nbzklr said:
To answer your questions:
1. I currently don't have one but I do not recall any errors appearing in the logs.
2. I'm using windows 10 and yes, drivers were installed correctly (by booting the system with signature checks disabled)
3. I did successfully flash marshmallow (32.2.A.5.11) multiple times after the failed nougat update.
4. My version of flashtools matches 0.9.23.2
I tried to update the the phone multiple time using official tools (OTA, xperia companion) before resorting to flashtool.
This, and the fact that flashtool works well otherwise, means the issue is with my device and/or the update itself and not with flashtool.
Is it possible to get some log files out of the device to see what's causing the crash?
Click to expand...
Click to collapse
after asking so many questions and reading all your answers ! i feel like saying i wish i could get hold of your device to see what actually got wrong in OTA flashing!
the reason why ask all these question is that it happend with my friends Z1 years ago when by simply updating to news OTA , device got stuck in bootloop! and the only thing he could do is unlock the bootloader and installed cynogenmod. at that time i could not find any possible reason why this has happend!
the ultimate solution for you could be unlocking boot loader OR wait until we get some sense on the internet about this issue! ( i will research more)
btw, I always flash my device on win7 64bit. if possilbe try flashing via win7 , just in case.
also i couldn't help thinking , it might have something to do with FSC script! even on the flashtool download page! they have mention how few devices get bricked if flashtool is used! but then you tried updating via xperia companion also!
http://www.flashtool.net/downloads.php
YasuHamed said:
The ultimate solution for you could be unlocking boot loader OR wait until we get some sense on the internet about this issue! ( i will research more)
Click to expand...
Click to collapse
Yeah, I already feared that this would be the only solution :crying:
Next week I'm gonna try to get a refund/replacement, so let's see how that goes first before I unlock the bootloader.
Thanks for your help though!
nbzklr said:
Yeah, I already feared that this would be the only solution :crying:
Next week I'm gonna try to get a refund/replacement, so let's see how that goes first before I unlock the bootloader.
Thanks for your help though!
Click to expand...
Click to collapse
to be honest there is nothing wrong with your device! you had rooted 5.11 easily! this means the stock android .372 or .376 having N kernel is not working properly with your hardware!
if you are replacing your device then no need to unlock your bootloader! unless u want rooted phone!
REMEMBER to research all about DRM KEYS and TA backups before you even think about unlocking in your dream.
nbzklr said:
Yeah, I already feared that this would be the only solution :crying:
Next week I'm gonna try to get a refund/replacement, so let's see how that goes first before I unlock the bootloader.
Thanks for your help though!
Click to expand...
Click to collapse
When you were making .ftf ,did you delete fwinfo and exclude .ta files ?
If not, that can lead to bootloop.
Hey guys, I just want to give you a quick update on the issue:
Last week I brought my phone to a local retailer, they sent it in and today I received a completely new device with Android 7.0 pre-installed!
So it seems like the issue was covered by warranty.
All in all I'm surprised how smooth everything went.
And thanks to everyone who tried to help me here!
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
EDIT:
Problem solved by rolling back to 4.1 b131 and then updated from internal updater app
Thanks in advance,
Federico
Federico Cervelli said:
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
Thanks in advance,
Federico
Click to expand...
Click to collapse
This Should Help You.
https://forum.xda-developers.com/honor-8/how-to/to-emui5-custom-roms-tested-openkirin-t3638445
I assume since you rolled back you have a locked bootloader atm.
Now i know these guides are somewhere but now that you mention it they do seem somewhat hard to find. ( on the app anyways)
But as for rolling back and then updating again via dload ( not TWRP) you need the rollback package and official firmware for your phone model.
Google and/or the guides section here should help you find those.
It should give you two zips containing an UPDATE.APP file each.
You need to put these on a folder named dload (one file at a time)on your sdcard( internal storage should do, too but no guarantees).
Create the folder if it doesn't exist.
Put in the rollback update.app in first.
Then power down and hold vol up+ vol down while powering up and it should flash the file.
Let it finish, boot up, put in the update.app from the firmware in the dload folder ( remove the old file) and repeat the process.
That should be it.
Also, you might be able to sinply dload the actual firmware from the test key build without rolling back but i haven't tried ( i think )
Should the dload process fail, you most likely have the wrong file in your dload folder, or multiple files.
I should mention that the rollback file actually brings you to a test.keys build. It's necessary to flash to full firmware afterwards and dloading the rollback file has always worked for me.
Personally i found that keeping the rollback update.app file for the rollback in the dload folder at all times is a good security measure. (besides the usual backups)
Sent from my OnePlus5 using XDA Labs
SharxX8 said:
I assume since you rolled back you have a locked bootloader atm.
Now i know these guides are somewhere but now that you mention it they do seem somewhat hard to find. ( on the app anyways)
But as for rolling back and then updating again via dload ( not TWRP) you need the rollback package and official firmware for your phone model.
Google and/or the guides section here should help you find those.
It should give you two zips containing an UPDATE.APP file each.
You need to put these on a folder named dload (one file at a time)on your sdcard( internal storage should do, too but no guarantees).
Create the folder if it doesn't exist.
Put in the rollback update.app in first.
Then power down and hold vol up+ vol down while powering up and it should flash the file.
Let it finish, boot up, put in the update.app from the firmware in the dload folder ( remove the old file) and repeat the process.
That should be it.
Also, you might be able to sinply dload the actual firmware from the test key build without rolling back but i haven't tried ( i think )
Should the dload process fail, you most likely have the wrong file in your dload folder, or multiple files.
I should mention that the rollback file actually brings you to a test.keys build. It's necessary to flash to full firmware afterwards and dloading the rollback file has always worked for me.
Personally i found that keeping the rollback update.app file for the rollback in the dload folder at all times is a good security measure. (besides the usual backups)
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
can you tell me what rollback package to use? i tried "(FRD-L19&L09, from Android 7.0, EMUI 5.0 to Android 6.0 EMUI 4.1, C900B300, Western Europe)" and didn't work
If you have an L09/19 it should work. Just make sure to flash the rollback package first.
Otherwise since you are on a test key build already, you might want to try to dload MM directly or if that doesn't work, try a stock nougat firmware via dload.
You could also try updating with Firmware Finder via proxy
Sent from my OnePlus5 using XDA Labs
SharxX8 said:
If you have an L09/19 it should work. Just make sure to flash the rollback package first.
Otherwise since you are on a test key build already, you might want to try to dload MM directly or if that doesn't work, try a stock nougat firmware via dload.
You could also try updating with Firmware Finder via proxy
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
i'm at 4.1 b131, now should i update via updater (ver. L09C432B380 2,36GB) or it's test keys?
Federico Cervelli said:
i'm at 4.1 b131, now should i update via updater (ver. L09C432B380 2,36GB) or it's test keys?
Click to expand...
Click to collapse
If you are on a regular version of MM, as I understand it, you can update normally, yes
SharxX8 said:
If you are on a regular version of MM, as I understand it, you can update normally, yes
Click to expand...
Click to collapse
but last time i did it it brang me to test keys .-.
EDIT: i tried and it's all working, Thanks!
Federico Cervelli said:
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
EDIT:
Problem solved by rolling back to 4.1 b131 and then updated from internal updater app
Thanks in advance,
Federico
Click to expand...
Click to collapse
I am in a very similar situation and unable to solve this. Could some one help in this?
I had unlocked bootload, TWRP and Root. I decided to unroot and lock the bootloader. So, by following the steps mentioned in a different thread, I could successfully flash Marshmallow B130 through Force Update.
Steps followed:
1. Flash Rollback package
2. Flash Full OTA (Marshmallow on B130) from Huawei website which flashed
Now, the real problem started while trying to upgrade to Nougat.
I tried downloading B350 firmware from Firmware Finder. After slow download, it installs fine. But, after reboot I face below problems.
1. The OS is very sluggish and crashes so often
2. The build number says NRD***-test keys
3. No keyboard installed, so not able to login to Google as well.
4. At this point, Factory Reset, Wipe Cache Partition, rollback everything fails.
I had to unlock the bootloader and again force update Rollback Package and then to Marshmallow B130.
Now, I am stuck with B130. I tried downloading B340 and B361 thru Firmware Finder. Both of them installed but with the same result. I mean No keyboard, Test-keys build, Crashes
My Honor 8 model: FRD-L02
What should I do upgrade to Nougat? I have no confidence in Firmware Finder method. Any help appreciated
It's EMUI 5.0.1 not 5.1, I think.
Hello dev's !
So I am surfing alot of threads here lately and I finally have this chance to post my problem & hopefully get some help regarding my problem.
Device Info - MHA-L29C185... (Middle East Version - Dual SIM). Don't remember which stock rom I was on but it was oreo so maybe somewhere close to 374 or earlier version.
Problem :
Firstly, I rooted following one of the threads from here and it was successful. However, I messed up when I downloaded an app which modifies framework or something and it bricked me and pushed me out.
But luckily I had some help and I used Chimera Tool to flash the International Version which brought my phone back to life but a lot of features like WiFi, Fingerprint Scanner didn't work.
So I decided to re-flash my firmware ie; C185B374 (Middle East Version) hoping it would solve the problem. It did solve the Fingerprint and WiFi problem but gave new problems like Gallery App (System APP) not working and Bluetooth not working.
:crying:
Note : I tried downloading firmware files from Firmware Finder & and flashing all 3 files using twrp and it fails as there is some mess in the Partition which isn't resolving. :crying:
I tried flashing using firmware finder app in the phone. It downloads the firmware and everything but doesn't flash. :crying:
Now, when I try to rebrand also which seemed a possible solution, I get stuck on the step where oeminfo files has to be replaced from the twrp backups. The script just doesn't respond.
Well, I am still living with the phone but alot of features don't work.
Help Required is :
1. Need solution to get stock firmware working properly as I am currently running my regions version but features don't work.
2. Lock back bootloader if possible. ( ADB Method & Team MT Multi Tool have been tried with no success)
3. Possibly get everything back to orignal. That's all I want !
Can anybody provide a possible solution to this ?
Nobody ?
My thought:
Download the firmware images you want to install.
Follow the instructions for using HuRupdater (search, I don't have the link handy for it); basically: put hurupdater and your update zips in the same folder on microsd, flash hurupdater with TWRP.
For relocking, you should be able to use "fastboot oem relock", though the phone will show that status. If that's fine, go for it.
I think this is a bad move to flashing this firmware. When i flashed it, I just wanted to use Android 9. I didn't really know the complication.
Recently after resetting the phone, Google pay stops working. Couldn't set up anymore as it said the firmware is altered or rooted.
And I tried different firmwares to flash it via dload folder method and none worked. Ended up with installation failed msg.
Mine is MHA-L29 C636.
So Can someone help me how I can go back to stock firmware which is Android 9 for c636?
Thanks a lot!!
I am wondering if there is any possibility to get an official Stock Rom (europe) of android 11 for xperia 5 ii. I tried to load version 58.1.A.5.530 with emma, but the install process aborted all the time. I was able to reinstall A12 via Xperifirm and new flasher command line tool and I'd like to install now A11 in the same ways. Any help? Thanks in advance
This is also my question! A12 is really frustrating me at the moment (calls dropping, bluetooth connect issues and also bluetooth volume control not working). Also the UI is just to gimmicky in my opinion. Spend the last 30 min to find a download for the official firmware for A11 europe, but wasn't able to track it down...
With more searching, I found a website with an archive of firmware files for the xperia 5 ii: https://support.halabtech.com/
It has the XQ-AS52_58.1.A.1.178_EE UK firmware. This should be it, right?
Firmware XQ-AS52 - Google Drive
drive.google.com
I'm a bit scared of bricking the device, so please let me know if this is the one for rolling back to A11
I don't know. It's definitely not the latest A11. I am not sure if there is a difference between UK and other Europe.
Any help?
I also see
XQ-AS52_EE UK_58.1.A.5.330.zip
and
XQ-AS52_Customized EEA_58.1.A.5.330.zip
these are more recent (aug 2021). Will download these two also and put those in the folder as well. Still not sure which version we need.
Check
https://www.reddit.com/r/SonyXperia/comments/tjpkgx
According to this guide 58.1.A.5.530 is the latest A11 and the author was able to reinstall it. Unfortunately I wasn't able to reinstall it via Emma flash tool but I may try via NewFlasher again, if I have the complete A11 stock rom
Check
https://www.reddit.com/r/SonyXperia/comments/tjpkgx
According to this guide 58.1.A.5.530 is the latest A11 and the author was able to reinstall it. Unfortunately I wasn't able to reinstall it via Emma flash tool but I may try via NewFlasher again, if I have the complete A11 stock rom
NewFlasher: Here
Guide for NewFlasher: Here
I wasn't able to get Emma working for some reason, but will try again. The website I found doesn't have the .530 version for EE_UK, only for RU and Vodafone and Orange phones.
Let me know when you get it working. Good Luck. At the moment my phone runs stable on A12. No freeze since 48 hours
But I think I need the get back on A11 anyway
OK, do NOT use the EE UK firmwares! We need the CUSTOM EEA.
Flashing the wrong one gave an error on booting.
I am now trying to get the 58.2.A.2.80 working again, but am stuck in a bootloop atm. Any ideas?
Try to install xperiafirm and use it to download the right firmware (Android12 only) then use newflasher and the guide I published to reinstall A12 - still better than bootloop
Try to install xperiafirm and use it to download the right firmware (Android12 only) then use newflasher and the guide I published to reinstall A12 - still better than
sociald27 said:
NewFlasher: Here
Guide for NewFlasher: Here
Click to expand...
Click to collapse
with the latest firmware reflashed I am now stuck in a bootloop. Factory reset does not work.
I can get into the recovery menu, but after a couple of loops it says 'device corrupted'
Ok, sorry to hear that. I guess then I was lucky with a NewFlasher Resetup
A12 running again via the official Xperia Companion app
I think I will just stick with it atm
I got another Update today. Build 58.2.A.4.52. I hope it's better now...
The latest Android 11 Europe ROM for Xperia 5 II can be downloaded here:
https://forum.xda-developers.com/t/looking-for-latest-android-11-firmware.4412601/
I have manually reverted it from the FTF format, so it can be used with the Newflasher, you can download it here:
http://koprajs.mx-net.cz/XQ-AS52_Customized EEA_58.1.A.5.530.zip
But if you've already installed Android 12, you cannot probably go back because of the "rollback protection" feature of the bootloader. The only way is to unlock the bootloader and reset the rollback index.
Thank you very much. It freezes all the time, I think I am going to try this.