Related
Good day all I have a question regarding my new device which I attempted to root. I have searched these forums and can't find anyone with the same problem as mine. Running 4.4.4.
For reference, I was following this guide: http: //tinyurl.com/o6v3hqf
Everything was going swimmingly. I followed the steps in the guide exactly up to and including typing "fastboot reboot". Once I did this, my PC would no longer recognise the device that was plugged in. In addition, the Xperia M2 will not boot, the Sony logo will appear and then the screen will intermittently flash. I can boot it into recovery mode, just fine, but there is no file on my Xperia to boot from.
The next step in the guide says to install SuperSU from an SD card which I am confident I can achieve, but I am concerned that my PC won't be able to recognise my device if the root is successful (therefore I wouldn't be able to transfer over music etc).
Will my PC be able to recognise the device once the root is successful? Should there be additional steps I need to take?
Sorry if my questions seem Noob-ish this is my first smartphone.
Thank you for reading
.
Open the sim tray.
There will be a small hole. Jam a thin pen or a pin or paper click into it.
Wait a few seconds and make sure screen is off. Go into a dark room or somin. If it's not hold the pin in until it is.
Upon boot spam the down vol. as fast as you can.
It'll send you into CWM.
Then you should be able to follow into the rest.
Also using the UK and the International .ftf i was unable to root (i could but after it was bricked)
So i had to use the vietnam rom.
ALSO it was (here comes the hate m8)
You didn't read it properly and was partially your own fault. It clearly states it for 4.3.X running 18.0.A.1.30 – v01. By running a boot.img or kernel based on "completely wrong" generations you have bricked it your self.
I suggest you redo this but following this guide here.
http://forum.xda-developers.com/xperia-m2/help/tut-flashing-ftf-4-nbz-t2970145
Flash the vietnam .ftf also find out what model your phone is D2303 or D2305.
Wrong .ftf will waste a good 30mins of downloading and render your phone useless until further flashing a new rom or ftf.
Then flash the boot.img from here : http://forum.xda-developers.com/xpe...2303-cwm-based-recovery-6-0-4-6-root-t2884503
The 2 posts explains it very well in the posts it selves. But don't be afraid to ask questions.
Hope I helped
Thank you for the advice. I agree I started following a guide without doing the necessary research. 100% my own fault. I will read the guide you posted and report back!
I can't find this Vietnam ftf anywhere.
My model is D2303. I have followed the above guide but flashed to Central Europe 4.4.2. I am still looking for a Vietnam .ftf file. I have found links for Malaysia and Russia, but no Vietnam yet.
I used the internal/journalists jb4.3 ftf top one in list on flashtool. Has the 4.4.2 and 4.4.4 updates waiting once booted up. I'm in UK and it works 4g n data just fine ,I Rooted 4.3 with towelroot apk (one çlick) then updated over the air twice each time checking root with root checker. Then force root with flashtool then installed SuperSU but don't update binarys in SuperSU till you have forced root and updated to 4.4.4 this was my first time ever rooting a phone too.
It helps to do your home work though i did two months reading up on here and the net it helped loads
sent from my b/l 2303 rooted on 4.4
.4
Hello,
received the Phone with the t-mobile branding (german version).
What i did is to use the official device unlock from Sony so be able to flash another Firmware.
Then i downloaded the generic DE from the FlashTool, and flashed it.
This failed because the rom was already on Android 7.
I did not manage to aquire the -9090 Rom in Android 6.0.1
So i flashed the central europe version.
First problem: this version does not (yet?) update to Android 7 - and actualy is NOT the version i wanted to have in the end.
Second problem: The camera app did not work anymore (already in use)
So i've read through this forum, and got the information, i need to re-unlock the device.
Did that, camera works.
However now i always get "this device is not trusted"
What i actualy want to have:
- A stock ROM in german, whcih gets OTA updates.
- Working Stock-Apps
- No warning when starting the Phone.
I do not care wether the warning is disabled, or simply not shown because of another bootloader. There should simply be no annoying warning.
I also have the exact same phone twice (mine, and the one for my girlfriend) in case this help somehow. In theory the best situation would be to hard-sync every single byte on the disk (i assume?)
I did not read anything about "do not flash currently, as this will make you loose your drm keys forever and the stock camera will no more work at all". But after watching this forum for some days now, it seems that exactly that has happened? So using a locked bootloader will not work anymore due to lost and unrecoverable drm keys? I cannot copy them from the other phone? So i need to replace the bootloader with another one to get rid of the message? And i also need to reflash the firmware as soon as FlashTool supports Android 7?
In the end a total piece of crap, because of a goddamn branding -.-
What would you guys recommend to do now? Just want to make it work without an error or unsecure warning displayed at every boot.
You did not need to unlock to flash another firmware.
Now you have unlocked you can't use the camera without keeping it unlocked and if it is unlocked you will get the warning message.
Just flash a 6.0 ftf from a region with the update then you will get the ota update
Ps, there are plenty of warnings on the Sony site about drm keys that you must have visited to get your unlock code...
And you cannot copy drm keys from another device
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!
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 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.