Need to root my m4 Aqua to be able to move the apps on sd card.
Thanks
M4 Aqua E2353
26.1.A.2.167
inchang27 said:
Need to root my m4 Aqua to be able to move the apps on sd card.
Thanks
M4 Aqua E2353
26.1.A.2.167
Click to expand...
Click to collapse
if you do have a backup image of the TA partition or you if don't what to take a backup, then unlock your boot loader, flash twrp recover, install SuperSu from recovery.
TWRP recovery link (http://forum.xda-developers.com/m4-aqua/development/recovery-twrp-touch-recovery-sony-m4-t3229873)
SuperSU link (https://download.chainfire.eu/696/SuperSU
if you do want to take a backup of the TA partition (has all the DRM Certificates), you would have to use flashtool and downgrade your software to get root on locked bootloader and take a backup of TA partition.
RohitBopnna said:
if you do have a backup image of the TA partition or you if don't what to take a backup, then unlock your boot loader, flash twrp recover, install SuperSu from recovery.
TWRP recovery link (http://forum.xda-developers.com/m4-aqua/development/recovery-twrp-touch-recovery-sony-m4-t3229873)
SuperSU link (https://download.chainfire.eu/696/SuperSU
if you do want to take a backup of the TA partition (has all the DRM Certificates), you would have to use flashtool and downgrade your software to get root on locked bootloader and take a backup of TA partition.
Click to expand...
Click to collapse
How to unlock bootloader?
RohitBopnna said:
if you do have a backup image of the TA partition or you if don't what to take a backup, then unlock your boot loader, flash twrp recover, install SuperSu from recovery.
TWRP recovery link (http://forum.xda-developers.com/m4-aqua/development/recovery-twrp-touch-recovery-sony-m4-t3229873)
SuperSU link (https://download.chainfire.eu/696/SuperSU
if you do want to take a backup of the TA partition (has all the DRM Certificates), you would have to use flashtool and downgrade your software to get root on locked bootloader and take a backup of TA partition.
Click to expand...
Click to collapse
I try it using flashtool. how can i unlock bootloader of this..
22/020/2016 17:20:47 - INFO - Loader : S1_Root_54c8 - Version : MSM8936_14 / Boot version : S1_Boot_MSM8939_LA2.0_36 / Bootloader status : NOT_ROOTABLE
22/020/2016 17:20:47 - INFO - Max packet size set to 512K
22/020/2016 17:20:47 - INFO - Opening TA partition 2
22/020/2016 17:20:47 - INFO - Start Reading unit 000008B2
22/020/2016 17:20:47 - INFO - Reading TA finished.
22/020/2016 17:20:47 - INFO - Closing TA partition
22/021/2016 17:21:13 - INFO - Ending flash session
22/021/2016 17:21:13 - INFO - Your phone bootloader cannot be officially unlocked
22/021/2016 17:21:13 - INFO - You can now unplug and restart your phone
22/021/2016 17:21:13 - INFO - Device connected in flash mode
22/021/2016 17:21:14 - INFO - Device disconnected
22/021/2016 17:21:17 - INFO - Device connected in flash mode
22/022/2016 17:22:18 - INFO - Device disconnected
if you cannot officially unlock then this is the only method http://forum.xda-developers.com/m4-aqua/development/bl-locked-twrp-touch-recovery-bl-locked-t3257430.
Downgrade firmware,
Root with Locked Bootloader (rootkitXperia_E23xx)
Install TWRP for Locked Bootloader (M4Aqua-lockedTWRP-0.1-installer)
Install latest version (twrp_prerooted_M4.zip) you need to creat.
all steps in the link..
Related
Hi There,
I’m wondering if anybody would be able to help me restore my bricked x10a (Telecom – New Zealand).
I was updating my phone from one wolf rom to another (Wolf_xperia 6.0.0.0s to ulBlDoom) . The rom worked but I was having issues flashing the doomkernel in order to get wifi. I tried to recover my old rom and bricked my phone. Now the phone locks at the sony erricson screen and I can’t enter recovery.
I’m unable to use SEUS or PC companion to revert back to stock as they say that my software is up to date (SEUS)/no software is available (PCC) and they do not give me the option to repair the phone.
I’ve attempted flashing several of the stock roms (and a few others) but flashtool gives the following errors. The closest I’ve got is with the US Generic 2.3.3 firmware, others fail at flashing kernel.sin or flashing loader.
13/049/2011 10:49:20 - INFO - Searching Xperia....
13/049/2011 10:49:20 - INFO - Found at USB\VID_0FCE&PID_ADDE\5&8E70AF1&0&2
13/049/2011 10:49:20 - INFO - Start Flashing
13/049/2011 10:49:21 - INFO - VER="r8A033";DATE="20100928";TIME="12:04:00";
13/049/2011 10:49:21 - INFO - Flashing loader
13/049/2011 10:49:22 - INFO - Device connected in flash mode
13/049/2011 10:49:25 - INFO - PROT_VER="02";DATE="20091222";TIME="15:39:00";VER="R4A024";CXC="1226-2250";TYPE="S1_LOADER";UNIQUE_DEV_ID="08572CA366314A97AD75DFA24CACB44D4D714BA6";SEC_LOCK_STATUS="LOCKED";OTP_DATA="4BBD770047140402094804304905157DF0C32000";IMEI="35942003202880";AID_VERSION="0004";EROM_AID="0001";LOADER_AID="0001";SW_AID="0001";CUST_AID="0001";SIM_LOCK_AID="0001";HWCONF_AID="0001";PROD_AID="0000";ACTIVE_LOADER_AID="0001";MAN_ID="002C";DEV_ID="00B3";SIN_VER="0001";AID_TAMP="NOT_TAMPERED";MAX_PKT_SZ="00010000";AUTH_LEVEL="NONE";AUTH_MET="0001";CARD_PRESENT="YES";CARD_SIZE="GB";CARD_DATA="";LOADER_ROOT="S1_Loader_Root_f851";EROM_ROOT="S1_EROM_Root_b15e";SW_ROOT="S1_SW_Root_ac12";CUST_ROOT="S1_Cust_Root_5789";SIM_LOCK_ROOT="S1_SL_Root_f20d";HW_CONF_ROOT="S1_HWConf_Root_ee5d";
13/049/2011 10:49:27 - INFO - Flashing kernel.sin
13/049/2011 10:49:30 - INFO - Flashing amss_fs.sin
13/049/2011 10:49:30 - INFO - Flashing dsp1.sin
13/049/2011 10:49:37 - INFO - Flashing fota1.sin
13/049/2011 10:49:38 - INFO - Flashing fota0.sin
13/049/2011 10:49:39 - INFO - Flashing amss.sin
13/049/2011 10:49:51 - INFO - Flashing cache.sin
13/049/2011 10:49:51 - INFO - Flashing system.sin
13/052/2011 10:52:28 - ERROR - Error flashing. Aborted
13/052/2011 10:52:28 - INFO - Now unplug the device and power it on
13/052/2011 10:52:28 - INFO - Then go to application settings
13/052/2011 10:52:28 - INFO - turn on Unknown Sources and Debugging
I’m wondering if there’s something I’m doing wrong to not be able to flash roms or if it may be possible to flash enough information for SEUS/PC Companion to recognise that the software needs to be updated.
Any help you could give me would be great, searching hasn’t provided me with any success.
Kind Regards,
Povotron
You tried to unlock the bootloader before updating to "ulBlDoom"?
No, I'd unlocked it previously for the earlier wolf rom I had. I just installed the ulBlDoom rom from xrecovery. Was this where I made my amateur mistake?
Any ideas where to go from here?
1. launch s1tool
restore BL
2. Download latest FlashTool 0.5.3.0
3. Flash stock ROM, get root, xrec and unlock BL by FlashTool
4. Flash custom ROM or custom Kernel and custom ROM (exclude kernel in FlashTool settings) or flash custom kernel, reboot to xRec and install custom zip with ROM
I hope your phone hasn't sim lock?
Sorry for my english
TangVLD said:
1. launch s1tool
restore BL
2. Download latest FlashTool 0.5.3.0
3. Flash stock ROM, get root, xrec and unlock BL by FlashTool
4. Flash custom ROM or custom Kernel and custom ROM (exclude kernel in FlashTool settings) or flash custom kernel, reboot to xRec and install custom zip with ROM
I hope your phone hasn't sim lock?
Sorry for my english
Click to expand...
Click to collapse
Don't need xrec if you are planning to unlock BL, just root, unlock then flash custom kernel.
aR_ChRiS said:
Don't need xrec if you are planning to unlock BL, just root, unlock then flash custom kernel.
Click to expand...
Click to collapse
Please, read again my post. I never said that xrec is necessary for unlock BL.
xrec need for stock ROM for them, who wants install a custom ROM by xrec-custom zip
TangVLD said:
1. launch s1tool
restore BL
2. Download latest FlashTool 0.5.3.0
3. Flash stock ROM, get root, xrec and unlock BL by FlashTool
4. Flash custom ROM or custom Kernel and custom ROM (exclude kernel in FlashTool settings) or flash custom kernel, reboot to xRec and install custom zip with ROM
I hope your phone hasn't sim lock?
Sorry for my english
Click to expand...
Click to collapse
You, kind sir, are a gentleman and a scholar.
I needed a different version of the S1 tool to get the restore option which allowed me to flash a stock rom without error. I now have the medium overclock ulbldoom working well. I had some errors flashing the kernal again but it seemed that a couple of repeat attempts was all it needed.
Thanks for all your help.
you are welcome)
perhaps this works for my problem forum.xda-developers.com/showthread.php?t=1388476
let me try this trick...
wish me luck
Sent from my X10i using Tapatalk
Good luck)
still not work. im downloaded FWs from forum.xda-developers.com/showthread.php?t=936733 (generic ver2.3.3 build 75 and 2.1 build 435) and forum.xda-developers.com/showthread.php?t=936733 (global generic 2.3.3 build 75)
Sent from my X10i using Tapatalk
Dears,
I've rooted my xperia mini pro to Android 4.0.4, Kernel version 2.6.32.9-perf [email protected] #1, Build Number: 4.1.B.0.431, before around 2 months,
Now, Sony has released an official update for the device with Build Number: 4.1.B.0.587, however, I've tried to update my phone using Update Service and with Sony PC Companion 2.1, and on both the update failed saying that because I've rooted my phone I can't update to the official stock rom.
I've also tried to download the update directly to my phone and tried to install it, but it also failed and didn't complete the update for the same reason,
Is there any way I can update my device to the same version, with the same stock rom?!
Have you unlocked your bootloader?
Sent from my ST15i using xda app-developers app
You can't update to official firmware via OTA or SUS or PC suite if your phone's bootloader is unlocked...
You must relock it...
http://forum.xda-developers.com/showthread.php?t=1560613
Above thread might help to relock the bootloader
And if your phone's bootloader is locked
http://forum.xda-developers.com/showthread.php?t=1568792
Follow the 4th topic "stock firmware and downgrade"
then try updating to official .587 update
Sent via SMULTRON
If your bootloader is unlocked never do updates over the air or your phone will brick!
You needn't relock the bootloader to get it working, just flash the .587.ftf and flash a prerooted kernel.
If your bootloader is locked, try to run the local-prop method on .431, flash .587 using flashtool (don't wipe data while flashing) and run push-root-files. Not sure if it works, but it could.
The 2nd method for locked bootloader is the kernel trick, look in my rooting guide there's a link on how to root 4.1.B.0.587
I've tried the local-prop method and it didn't work for me, I've updated to .587 and lost root :/
I assume that OTA on locked BL from .431 to .587 won't keep the root as well?
It will, if you do not done update with factory reset.....
Sent from my ST15i using xda app-developers app
I've tried everything to root to .587 knowing that my phone is unlocked, but each time i run the Flashtool i get the below error, though i've checked everything and enabled MSC mode, Unknown Sources, and USB Debugging.
.ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_STATIC="IMAGE_ADDRESS_RANGE";ERR_DYNAMIC="SIN-block eraseblock mismatch.
I just want to run .587, please help me with this!
17/045/2012 03:45:29 - INFO - Start Flashing
17/045/2012 03:45:29 - INFO - Processing loader
17/045/2012 03:45:29 - INFO - Checking header
17/045/2012 03:45:29 - INFO - Flashing data
17/045/2012 03:45:32 - INFO - Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTABLE
17/045/2012 03:45:32 - INFO - Disabling final data verification check
17/045/2012 03:45:32 - WARN - This file is ignored : simlock.ta
17/045/2012 03:45:32 - INFO - Processing kernel.sin
17/045/2012 03:45:32 - INFO - Checking header
17/045/2012 03:45:32 - INFO - Flashing data
17/045/2012 03:45:32 - INFO - Ending flash session
17/045/2012 03:45:32 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_STATIC="IMAGE_ADDRESS_RANGE";ERR_DYNAMIC="SIN-block eraseblock mismatch";
17/045/2012 03:45:32 - ERROR - Error flashing. Aborted
17/045/2012 03:45:32 - INFO - Device connected in flash mode
17/045/2012 03:45:34 - INFO - Device disconnected
17/045/2012 03:45:35 - INFO - Device connected in flash mode
17/045/2012 03:45:53 - INFO - Device disconnected
Any advice?
Hi guys, I have an Xperia Z2 running Stock 5.1.1 debloated and rooted.
I'm planning to unlock my bootloader to use the AndroPlus Kernel v63
I am confused on how to Unlock Bootloader via flashtool and then restore DRM keys back because 2014 threads here and comments are all that I can see.
from my current device state, How to unlock the Bootloader using Flashtool and afterwards restore the DRM keys.
I already made a backup of TA partition using this TOOL. And restoring the TA partition again using this tool will relock my bootloader. Which I only wish to be Unlocked and the DRM keys to be restored.
next is what resources do I need in restoring DRM keys. This LINK says that I need the .69 firmware and .690 firmware. these old firmwares are not available to the xperiafirm. and again can't seem to find the FTF files for this two firmwares.
If there is anyone that can help me, please This weekend is the only time that I can do this on my phone.
Thank you!
first of all lookup TABackup and backup your DRM keys.
This is how I did it with my TABackup, starting from unlocked bootloader :
- make sure DRM fix is on your sd card, not internal memory, which will be wiped.
- flash 5.1.1 rom in flashtools, wipe everything
- boot into android, do initial setup, enable usb debugging and unknown sources
- use TABackup to restore your DRM keys
- DO NOT ALLOW PHONE TO REBOOT INTO ANDROID, once the TABackup reboots your phone, turn it off by holding power+vol-up for 5 secs.
- flash Androplus kernel using flashtools or fastboot
- reboot phone and spam vol-up until you get into recovery
- flash DRM fix zip
- reboot into android and check your camera quality/sound quality
kinda in a hurry, so not fully details. if you still need anything I'll check thread later tonight
A new tool has just been released to backup TA using the Dirty Cow exploit. After that, you should be able to unlock bootloader, flash recovery, flash su and restore TA. Then your device should be rooted with DRM retained.
I don't have a XC so I'm unable to test.
http://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
itandy said:
A new tool has just been released to backup TA using the Dirty Cow exploit. After that, you should be able to unlock bootloader, flash recovery, flash su and restore TA. Then your device should be rooted with DRM retained.
I don't have a XC so I'm unable to test.
http://forum.xda-developers.com/crossdevice-dev/sony/universal-dirtycow-based-ta-backup-t3514236
Click to expand...
Click to collapse
I tested it on an Xperia X Compact running 34.1.A.1.198 and it seems to work, see my post here
ggow said:
I tested it on an Xperia X Compact running 34.1.A.1.198 and it seems to work, see my post here
Click to expand...
Click to collapse
Thanks!
But according to another post, actually it's impossible to keep root after TA is restored. Do you know if it's true?
itandy said:
Thanks!
But according to another post, actually it's impossible to keep root after TA is restored. Do you know if it's true?
Click to expand...
Click to collapse
That's correct. But it's important to have the TA backup for restoring full functionality.
There might be a way to use the previous DRM patches combined with flashing only the TA unit for the device key in order to have full stock functionality with root. Also would need a custom kernel for the latest stock firmware update.
Sent from my F5321 using Tapatalk
ggow said:
I tested it on an Xperia X Compact running 34.1.A.1.198 and it seems to work, see my post here
Click to expand...
Click to collapse
*Edit*
For those who are unable to navigate modern forums (like me) there is a downloads tab in the post that will have the files you need to backup TA.
JenItols said:
*Edit*
For those who are unable to navigate modern forums (like me) there is a downloads tab in the post that will have the files you need to backup TA.
Click to expand...
Click to collapse
I had the same difficulty finding where to download. lol!
but worked like a charm for me
Add firmware v.34.1.A.1.205 to the list.
http://forum.xda-developers.com/cro...ersal-dirtycow-based-ta-backup-t3514236/page7
(I have no idea why my browser crashes if I point it directly to my post lol)
I just was able to pull a copy of TA from the Customized CE1 (Central Europe) v34.1.A.3.49
When next version (hopefully Nougat) is available I plan to load the known compatible version 34.1.A.1.198 and compare checksums to verify. However, I did get a file with 34.1.A.3.49 which has the November 1st android security updates.
*edit*
After reading it appears that TA changes every boot. However, when the time comes to update software I will revert back to known version with compatibility and then re-pull TA.
ggow said:
That's correct. But it's important to have the TA backup for restoring full functionality.
There might be a way to use the previous DRM patches combined with flashing only the TA unit for the device key in order to have full stock functionality with root. Also would need a custom kernel for the latest stock firmware update.
Sent from my F5321 using Tapatalk
Click to expand...
Click to collapse
Now that we can have a backup image of TA, can we use this tool to repack the kernel and restore DRM functionality?
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
itandy said:
Now that we can have a backup image of TA, can we use this tool to repack the kernel and restore DRM functionality?
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
Click to expand...
Click to collapse
- Yes, I think we can. As long as the TA unit address for device key has not changed then it should work.
- After some rest when I have my Wits about me I am going to attempt it
Guys,
could someone please tell me step by step, how to restore TA?
EDIT - know, after restoring TA I have a password option - cant get over it? any ideas?
Ok... done
I can confirm, it works - backup and restoring
So...
This is an outline of how I have managed to get root with devicekey back into the TA partition.
NOTE:
- I am only interested in running rooted stock sony firmware so for me this is OK for the moment.
- I am looking into why FIDO_KEYS come back as unprovisioned, everything else seems fine.
Follow this at your own risk
- Install latest stock firmware via flashtool 34.1.A.3.49
- Backup TA Partition
- Unlock bootloader using Sony website
- Extract kernel.elf from kernel.sin using Flashtool
- Create root kernel using this tool
Code:
[email protected]:~/Desktop/rootkernel_v5.0_Windows_Linux$ ./rootkernel.sh kernel.elf boot.img
- Unpacking kernel
Found elf boot image
Kernel version: 3.10.84-perf-g2cfe3ef
Found appended DTB
- Detected vendor: somc (Sony), device: kugo, variant: row
- Unpacking initramfs
- Detected platform: 64-bit
- Detected Android version: 6.0.1 (sdk 23)
- dm-verity is enabled. Disable? (Say yes if you modify /system) [Y/n] y
Disabling dm-verity
- Sony RIC is enabled. Disable? [Y/n] y
Disabling Sony RIC
- There is no TWRP template for kugo. Install anyway? [y/N] n
- DRM fix is unsuppported/untested for model kugo. Install anyway? [y/N] y
- Install busybox? [Y/n] y
- Creating new initramfs
- Creating boot image
- Cleaning up
Done
- Create devicekey which is flashable via flashtool
Code:
[email protected]:~/Desktop/rootkernel_v5.0_Windows_Linux$ ./flash_dk.sh TA_F5321_QV705K140B_20161208-1905.img devicekey.ftf
- Extracting device key
- Creating FTF file for device F5321
- Cleaning up
Done
- Flash devicekey.ftf via flashtool
- Boot device into fastboot and flash boot.img
- I haven't flashed TWRP instead I booted it by:
Code:
fastboot boot twrp.img
- Flashed SR4-SuperSU-v2.78-SR4-20161115184928.zip
- Reboot device
Fantastic news! This is major. So in theory we should be able to get more rom availability now?
Android pay gets broken, right?
Will root now
tlxxxsracer said:
Fantastic news! This is major. So in theory we should be able to get more rom availability now?
Android pay gets broken, right?
Will root now
Click to expand...
Click to collapse
Should see new ROMs eventually surfacing
You're correct Android pay doesn't work with a rooted device
Dump question. I just downloaded the latest firmware using XperiFirm and created a FTF file using FlashTool. But FlashTool always show the following errors.
09/047/2016 22:47:46 - INFO - Start Flashing
09/047/2016 22:47:46 - INFO - No loader in the bundle. Searching for one
09/047/2016 22:47:54 - INFO - No matching loader found
09/047/2016 22:47:54 - WARN - No loader found or set manually. Skipping loader
09/047/2016 22:47:54 - INFO - Ending flash session
09/047/2016 22:47:54 - ERROR - null
09/047/2016 22:47:54 - ERROR - Error flashing. Aborted
Click to expand...
Click to collapse
itandy said:
Dump question. I just downloaded the latest firmware using XperiFirm and created a FTF file using FlashTool. But FlashTool always show the following errors.
Click to expand...
Click to collapse
When creating your FTF, did you include loader.sin ?
ggow said:
When creating your FTF, did you include loader.sin ?
Click to expand...
Click to collapse
In fact, there's no loader.sin in the download folder. I tried to download several firmwares using XperiFirm and they're the same.
itandy said:
In fact, there's no loader.sin in the download folder. I tried to download several firmwares using XperiFirm and they're the same.
Click to expand...
Click to collapse
I've never tried creating a custom FTF, so I'm not sure. I downloaded the UK version of 34.1.A.3.49 and was able to flash that successfully.
Have you unlocked your bootloader?
Just thinking FTF may be signed by Sony?
Maybe with a locked bootloader you can't flash custom FTF?
ggow said:
I've never tried creating a custom FTF, so I'm not sure. I downloaded the UK version of 34.1.A.3.49 and was able to flash that successfully.
Have you unlocked your bootloader?
Just thinking FTF may be signed by Sony?
Maybe with a locked bootloader you can't flash custom FTF?
Click to expand...
Click to collapse
Do you have the link where you downloaded the UK .49 firmware?
itandy said:
Do you have the link where you downloaded the UK .49 firmware?
Click to expand...
Click to collapse
I downloaded it via XperiFirm
I took a nandroid back up about a year ago and today when I restored it my phone gets stuck on the purple boot screen. How do I restore the stock rom?
Bootloader Unlocked
No DRM Keys
Nandroid Backup from twrp
I left it for about 2 hours straight....
Any help is appreciated
SirBottle said:
I took a nandroid back up about a year ago and today when I restored it my phone gets stuck on the purple boot screen. How do I restore the stock rom?
Bootloader Unlocked
No DRM Keys
Nandroid Backup from twrp
I left it for about 2 hours straight....
Any help is appreciated
Click to expand...
Click to collapse
If your previous rom was android 7 or 8 then you should flash stock rom first with flashtools then you can restore your backup
Don't forget to check all boxes of wipe section in flashtools
raminta said:
If your previous rom was android 7 or 8 then you should flash stock rom first with flashtools then you can restore your backup
Don't forget to check all boxes of wipe section in flashtools
Click to expand...
Click to collapse
I have a Sony z2 d6502 (India)
My previous stock rom was marshmallow 6.0.1
My phone is a d6502 but after flashing a custom rom (Resurrection Remix) Nougat, CPU-Z and Build.prop states that my variant is a d6503.Is that possible?
Also, I cannot flash any .ftf files on flashtool because of the bundle error.
The Sony FLASHTOOL log is given below:
21/024/2018 08:24:19 - INFO - Device disconnected
21/026/2018 08:26:47 - INFO - Selected Bundle for Sony Xperia Z2(D6503). FW release : 23.5.A.1.291. Customization : Customized UK
21/026/2018 08:26:47 - INFO - Preparing files for flashing
21/028/2018 08:28:04 - INFO - Please connect your device into flashmode.
21/030/2018 08:30:24 - INFO - Using Gordon gate drivers version 3.2.0.0
21/030/2018 08:30:24 - INFO - Opening device for R/W
21/030/2018 08:30:25 - INFO - Device ready for R/W.
21/030/2018 08:30:25 - INFO - Reading device information
21/030/2018 08:30:25 - INFO - Phone ready for flashmode operations.
21/030/2018 08:30:25 - INFO - Opening TA partition 2
21/030/2018 08:30:25 - INFO - Current device : Unknown: Jul 24 2016/19:28:59 - BH900X3A17 - Unknown: Jul 24 2016/19:28:59 - Unknown: Jul 24 2016/19:28:59 - GENERIC_23.5.A.1.291
21/030/2018 08:30:25 - INFO - Closing TA partition
21/030/2018 08:30:25 - ERROR - The bundle does not match the connected device
21/030/2018 08:30:25 - INFO - Ending flash session
21/030/2018 08:30:26 - INFO - Device disconnected
Also, flashtool is not able to detect my phone even though ADB and Unknown Sources are on , I also installed all the required drivers.
Is it because of the Custom Rom or the variant of my phone?
Just a reminder, my phones variant changed from d6502 to d6503 after resurrection remix......
I don't have a TA partition.....
I already when thought this forum
https://forum.xda-developers.com/z3/help/bundle-match-connected-device-t3749226
SirBottle said:
I have a Sony z2 d6502 (India)
My previous stock rom was marshmallow 6.0.1
My phone is a d6502 but after flashing a custom rom (Resurrection Remix) Nougat, CPU-Z and Build.prop states that my variant is a d6503.Is that possible?
Also, I cannot flash any .ftf files on flashtool because of the bundle error.
The Sony FLASHTOOL log is given below:
21/024/2018 08:24:19 - INFO - Device disconnected
21/026/2018 08:26:47 - INFO - Selected Bundle for Sony Xperia Z2(D6503). FW release : 23.5.A.1.291. Customization : Customized UK
21/026/2018 08:26:47 - INFO - Preparing files for flashing
21/028/2018 08:28:04 - INFO - Please connect your device into flashmode.
21/030/2018 08:30:24 - INFO - Using Gordon gate drivers version 3.2.0.0
21/030/2018 08:30:24 - INFO - Opening device for R/W
21/030/2018 08:30:25 - INFO - Device ready for R/W.
21/030/2018 08:30:25 - INFO - Reading device information
21/030/2018 08:30:25 - INFO - Phone ready for flashmode operations.
21/030/2018 08:30:25 - INFO - Opening TA partition 2
21/030/2018 08:30:25 - INFO - Current device : Unknown: Jul 24 2016/19:28:59 - BH900X3A17 - Unknown: Jul 24 2016/19:28:59 - Unknown: Jul 24 2016/19:28:59 - GENERIC_23.5.A.1.291
21/030/2018 08:30:25 - INFO - Closing TA partition
21/030/2018 08:30:25 - ERROR - The bundle does not match the connected device
21/030/2018 08:30:25 - INFO - Ending flash session
21/030/2018 08:30:26 - INFO - Device disconnected
Also, flashtool is not able to detect my phone even though ADB and Unknown Sources are on , I also installed all the required drivers.
Is it because of the Custom Rom or the variant of my phone?
Just a reminder, my phones variant changed from d6502 to d6503 after resurrection remix......
I don't have a TA partition.....
I already when thought this forum
https://forum.xda-developers.com/z3/help/bundle-match-connected-device-t3749226
Click to expand...
Click to collapse
Which version of flashtools are you using???
Use older versions like 0.9.18.x or 0.9.19.x
They may solve the problem
raminta said:
Which version of flashtools are you using???
Use older versions like 0.9.18.x or 0.9.19.x
They may solve the problem
Click to expand...
Click to collapse
Issue 1:
When I flash it, it gives error-root bundle is not valid
Is it a .ftf issue?
Issue 2:
Flashtool Log:
Checking Root Access
Root access denied
I already have magisk installed on my Sony z2.
SirBottle said:
Issue 1:
When I flash it, it gives error-root bundle is not valid
Is it a .ftf issue?
Issue 2:
Flashtool Log:
Checking Root Access
Root access denied
I already have magisk installed on my Sony z2.
Click to expand...
Click to collapse
Issue 1: maybe it is from ftf file but i don't think so
As i said use older versions of flashtools
Issue 2: that will not make any problem and it is not important
raminta said:
Issue 1: maybe it is from ftf file but i don't think so
As i said use older versions of flashtools
Issue 2: that will not make any problem and it is not important
Click to expand...
Click to collapse
I am using 0.9.18.6 (flashtool Version).. Should I install another FTF file if so, which variant do I choose (d6502 or d6503) or should I just try both?
Just wondering I still cant restore TWRP backup with system and boot backed up (It just gets stuck on the purple boot screen the waves one)
SirBottle said:
I am using 0.9.18.6 (flashtool Version).. Should I install another FTF file if so, which variant do I choose (d6502 or d6503) or should I just try both?
Just wondering I still cant restore TWRP backup with system and boot backed up (It just gets stuck on the purple boot screen the waves one)
Click to expand...
Click to collapse
choose d6502 and yes change FTF file
the problem with TWRP backup is because of the nought version of RR that you flashed and now you want to back to stock based rom so you should flash stock rom with flashtools and wipe everything
raminta said:
choose d6502 and yes change FTF file
the problem with TWRP backup is because of the nought version of RR that you flashed and now you want to back to stock based rom so you should flash stock rom with flashtools and wipe everything
Click to expand...
Click to collapse
Thanks So Much!!!!
:good::victory:
I got the stock rom installed on my phone it works flawlessly!
Is there any way to root marshmallow 6.0.1 on sony z2
SirBottle said:
I got the stock rom installed on my phone it works flawlessly!
But, for some reason I can't load twrp using adb.
Adb says it is successful but for some reason pressing power down or power up does not boot into twrp.
Click to expand...
Click to collapse
Flash elite kernel version 3
It has built-in recovery (TWRP)
raminta said:
Flash elite kernel version 3
It has built-in recovery (TWRP)
Click to expand...
Click to collapse
I realized I made a dumb mistake on my part..
Anyways is there a root for sony z2 6.0.1 firmware .291
Thanks
SirBottle said:
I realized I made a dumb mistake on my part..
Anyways is there a root for sony z2 6.0.1 firmware .291
Thanks
Click to expand...
Click to collapse
I think flashing Super SU using recovery should be enough
SirBottle said:
I got the stock rom installed on my phone it works flawlessly!
Is there any way to root marshmallow 6.0.1 on sony z2
Click to expand...
Click to collapse
here
Hafyzy said:
here
Click to expand...
Click to collapse
I have a d6502 variant,is it okay if I flash a D6503 Kernel on it?
SirBottle said:
I have a d6502 variant,is it okay if I flash a D6503 Kernel on it?
Click to expand...
Click to collapse
yes you can ...