Hi, I´m new to the whole Android scene and therefore to the Rooting/flashing scene. So far I have always used Apple devices.
A friend convinced me that Android was the best option, so I got a Z2 Tablet to give it a try.
I have searched on this forums and have not been able to get an answer on whether it´s possible to Root my device which is on 5.1.1
I have to say the community is a lot friendlier when it comes to Jailbreaking an IPad, here it seems to be a sin to be new.
Sorry for the rant, am just kind of pissed.
Is there a simple yes/no answer to my question? If the answer is yes, is there a guide I can follow to get started?
I´ve been led to several guides and all of them make it clear that they dont work in my case, ANY help would be greatly appreciated.
MXCorp said:
Hi, I´m new to the whole Android scene and therefore to the Rooting/flashing scene. So far I have always used Apple devices.
A friend convinced me that Android was the best option, so I got a Z2 Tablet to give it a try.
I have searched on this forums and have not been able to get an answer on whether it´s possible to Root my device which is on 5.1.1
I have to say the community is a lot friendlier when it comes to Jailbreaking an IPad, here it seems to be a sin to be new.
Sorry for the rant, am just kind of pissed.
Is there a simple yes/no answer to my question? If the answer is yes, is there a guide I can follow to get started?
I´ve been led to several guides and all of them make it clear that they dont work in my case, ANY help would be greatly appreciated.
Click to expand...
Click to collapse
Yes you can root, BUT you will likely have to downgrade to 4.4.2. See this thread here: http://forum.xda-developers.com/showthread.php?t=2784900&page=163 for the root method, and this thread here for the 4.4.2 firmware, there is also a link to the flash tool and a guide http://forum.xda-developers.com/xperia-z2-tablet/general/ftf-collection-locked-unlocked-bl-t3061431
Once you are rooted and have Nuts dual recovery installed you can flash prerooted firmwares to get you to rooted 5.1.1 if that is where you want to be. Look through the General thread to find the appropriate prerooted .zip for your device.
BladeRunner said:
Yes you can root, BUT you will likely have to downgrade to 4.4.2. See this thread here: http://forum.xda-developers.com/showthread.php?t=2784900&page=163 for the root method, and this thread here for the 4.4.2 firmware, there is also a link to the flash tool and a guide http://forum.xda-developers.com/xperia-z2-tablet/general/ftf-collection-locked-unlocked-bl-t3061431
Once you are rooted and have Nuts dual recovery installed you can flash prerooted firmwares to get you to rooted 5.1.1 if that is where you want to be. Look through the General thread to find the appropriate prerooted .zip for your device.
Click to expand...
Click to collapse
Thank you! will look into those right away, much appreciated man-----!
Rooting 23.5.A.0.570 Marshmallow / SGP521
Hi everyone.
Searched a lot of threads, but did not find the answer, so I dig out this one to ask.
I have a SGP521 castor with 23.5.A.0.570 Marshmallow and don't get this rooted. The bootloader is open.
I need the customized DE Fiirmware, so the russian Vodafone prerooted here is no Option, not to mention the Vodafone bloatware included.
With Lollipop, this was no problem. Just flashed the rather old custom Kernel "Z2Tab_DooMLoRD_AdvStkKernel_LTE-v03_17.1.1.A.0.402", with this I flashed SuperSU from the included recovery and then re-flashed boot from the stock ROM with Flashtool.
This procedure does not work anymore with Marshmallow. After flashing the stock Kernel, it does not boot (Bootloop) anymore.
I tried building a PRF with the latest PRFcreator 1.3 including SuperSU Beta v2.71-20160331103524 and TabZ2-lockeddualrecovery2.8.26-RELEASE.combined, but ths has no root and no Recovery after booting up, even when flashed with TWRP 2.8.7.0 from the Lollipop stock ROM DualRecovery.
I build a modified Kernel on NUT's DualRecovery Page by uploading the kernel.sin (SGP521_23.5.A.0.570_XZDRKernel2.8.26-RELEASE.flashable), but flashing this does not work either. The system does not boot with it. I tried to flash the boot.img in the TMP folder of it, but no luck.
Forgot to mention that I tried to flash TWRP to recovery partition, but since Sony devices with no TA Update have this FOTA crap, it does not boot the recovery of course. On my Xperia Z Ultra I flashed the dedicated recovery TA patch with Emma, so I did not had such problems there - but the Z Ultra has no Marshmallow of course.
Any suggestions?
Thank you.
TimeTurn said:
Hi everyone.
Searched a lot of threads, but did not find the answer, so I dig out this one to ask.
I have a SGP521 castor with 23.5.A.0.570 Marshmallow and don't get this rooted. The bootloader is open.
I need the customized DE Fiirmware, so the russian Vodafone prerooted here is no Option, not to mention the Vodafone bloatware included.
With Lollipop, this was no problem. Just flashed the rather old custom Kernel "Z2Tab_DooMLoRD_AdvStkKernel_LTE-v03_17.1.1.A.0.402", with this I flashed SuperSU from the included recovery and then re-flashed boot from the stock ROM with Flashtool.
This procedure does not work anymore with Marshmallow. After flashing the stock Kernel, it does not boot (Bootloop) anymore.
I tried building a PRF with the latest PRFcreator 1.3 including SuperSU Beta v2.71-20160331103524 and TabZ2-lockeddualrecovery2.8.26-RELEASE.combined, but ths has no root and no Recovery after booting up, even when flashed with TWRP 2.8.7.0 from the Lollipop stock ROM DualRecovery.
I build a modified Kernel on NUT's DualRecovery Page by uploading the kernel.sin (SGP521_23.5.A.0.570_XZDRKernel2.8.26-RELEASE.flashable), but flashing this does not work either. The system does not boot with it. I tried to flash the boot.img in the TMP folder of it, but no luck.
Forgot to mention that I tried to flash TWRP to recovery partition, but since Sony devices with no TA Update have this FOTA crap, it does not boot the recovery of course. On my Xperia Z Ultra I flashed the dedicated recovery TA patch with Emma, so I did not had such problems there - but the Z Ultra has no Marshmallow of course.
Any suggestions?
Thank you.
Click to expand...
Click to collapse
+1 in search info for rooting too...
flashed by XperiFirm of Flashtool 23.5.A.0.570 Marshmallow for my SGP512 and then tryed root device in flashtool and get it log
Code:
28/012/2016 22:12:23 - INFO - Flashtool Version 0.9.20.0 built on 04-10-2015 21:00:00
28/012/2016 22:12:23 - INFO - Executing search strategies to find proxy selector
28/012/2016 22:12:23 - INFO - No proxy found for IE. Trying next one
28/012/2016 22:12:23 - INFO - Strategy firefox failed trying next one : No Firefox installation found
28/012/2016 22:12:23 - INFO - No proxy found for java. Trying next one
28/012/2016 22:12:23 - INFO - Syncing devices from github
28/012/2016 22:12:23 - INFO - Opening devices repository.
28/012/2016 22:12:23 - INFO - Scanning devices folder for changes.
28/012/2016 22:12:27 - INFO - Pulling changes from github.
28/012/2016 22:12:28 - INFO - Quietly closing devices repository.
28/012/2016 22:12:28 - INFO - Devices sync finished.
28/012/2016 22:12:28 - INFO - Loading devices database
28/012/2016 22:12:28 - ERROR - root : this bundle is not valid
28/012/2016 22:12:28 - INFO - Loaded 86 devices
28/012/2016 22:12:28 - INFO - Starting phone detection
28/012/2016 22:12:32 - INFO - Device connected with USB debugging on
28/012/2016 22:12:33 - INFO - Connected device : Sony Xperia Z2 Tablet
28/012/2016 22:12:33 - INFO - Installed version of busybox : N/A
28/012/2016 22:12:33 - INFO - Android version : 6.0.1 / kernel version : 3.4.0-perf-g3189667 / Build number : 23.5.A.0.570
28/012/2016 22:12:33 - INFO - Root access denied
28/017/2016 22:17:34 - INFO - Pushing C:\Flashtool\custom\root\PsNeuter\psneuter.tar.uue to /data/local/tmp
28/017/2016 22:17:34 - INFO - Pushing C:\Users\Admin\.flashTool\devices\busybox\1.20.2\busybox to /data/local/tmp/busybox
28/017/2016 22:17:35 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\su to /data/local/tmp/su
28/017/2016 22:17:35 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\Superuser.apk to /data/local/tmp/Superuser.apk
28/017/2016 22:17:35 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\install-recovery.sh to /data/local/tmp/install-recovery.sh
28/017/2016 22:17:36 - INFO - Pushing C:\Flashtool\custom\root\subin\Supersu\99SuperSUDaemon to /data/local/tmp/99SuperSUDaemon
28/017/2016 22:17:36 - INFO - Running part1 of Root Exploit, please wait
28/017/2016 22:17:36 - INFO - Running rootit
28/017/2016 22:17:36 - INFO - Waiting for device. After 60secs, stop waiting will be forced
28/018/2016 22:18:37 - INFO - Forced stop waiting.
28/018/2016 22:18:37 - ERROR - The part1 exploit did not work
28/018/2016 22:18:37 - INFO - Cleaning files
thanks for any ideas.
I made a prerooted ZIP with PRFcrator already. I took the SUperSU, recovery and another ZIP from the russian Version here and activated legacy mode, that worked.
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
I had flashed my sk17 with LX11.0 but I want to restore my old version of rom (LX10.1). I did a restore of old rom (I had small problems to start recovery but I did flash of some old kernel and after that flash with kernel from 10.1 and recovery started) with restore from recovery.
what is problem? now my proximity and light sensors are not working. during call display is always ON and auto brightnes is not working. what should I do next? :cyclops:
Try wipe cache and dalvik cache. If it doesn't work, wipe /data too.
Gesendet von meinem Xperia Neo V mit Tapatalk 2
from recovery I wiped everything (cache, dalwik and data) and still no proximity and light sensor. after that I try to reflash kernel and the same thing is happening
is there some service menu for cyanogenmod? like sony one service menu just to check are sensors OK
I don't know, I'm not using restore option because I had problems with it in the past.
You can try to enable developer menu in Settings>About Phone>Tap several times on Build Number until you see You are developer and you will see new menu in settings, and try also stock ROM to see if problem persist there.
Gesendet von meinem Xperia Neo V mit Tapatalk 2
ReznorNInchNails said:
I don't know, I'm not using restore option because I had problems with it in the past.
You can try to enable developer menu in Settings>About Phone>Tap several times on Build Number until you see You are developer and you will see new menu in settings, and try also stock ROM to see if problem persist there.
Gesendet von meinem Xperia Neo V mit Tapatalk 2
Click to expand...
Click to collapse
I/m trying to flash stock ISC because it must be done but flashtool refuses to flash Now I don't know what to do next?
Can you post the error? Maybe it's broken download? Check file size.
Are you in flash mode (green led), or can you actually get in flash mode? Have you selected wipe cache, system, etc.?
If you can get into fastboot try to flash boot.img then flash CM11 and check developer options and test sensors.
Check this tutorial in case you missed something. http://talk.sonymobile.com/t5/Xperi...V-MT11i-2-3-4-update-4-0-2-A-0-62/td-p/134345
P.S. I heard that it is no go with Windows 8.1. If you use that, try with 7 or Linux in VBox.
I had downloaded 3 tft (different stock roms) and everytime I got different error. laptop has windows8 but errors are the same on xp also.
I can flash legacyXperia11 but does it have service menu to test sensors?
here is log from flashtool from linux machine:
22/018/2013 21:18:06 - INFO - <- This level is successfully initialized
22/018/2013 21:18:06 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
22/018/2013 21:18:06 - INFO - libusb version 1.0.17
22/018/2013 21:18:06 - INFO - Device disconnected
22/018/2013 21:18:32 - INFO - Selected SK17i / 4.1.B.0.587 / Customized_CE3
22/018/2013 21:18:33 - INFO - Preparing files for flashing
22/018/2013 21:18:53 - INFO - Please connect your device into flashmode.
22/019/2013 21:19:01 - INFO - Device connected in flash mode
22/019/2013 21:19:01 - INFO - Opening device for R/W
22/019/2013 21:19:01 - INFO - Device ready for R/W.
22/019/2013 21:19:01 - INFO - Reading device information
22/019/2013 21:19:02 - INFO - Phone ready for flashmode operations.
22/019/2013 21:19:02 - INFO - Current device : SK17i - BX902PDWPN - 1249-7382_R1I - 1244-7088_4.1.B.0.431 - WORLD-i_4.1.B.0.587
22/019/2013 21:19:02 - INFO - Start Flashing
22/019/2013 21:19:02 - INFO - Using an unofficial loader
22/019/2013 21:19:02 - INFO - Device loader has not been identified. Using the one from the bundle
22/019/2013 21:19:02 - INFO - Processing loader.sin
22/019/2013 21:19:02 - INFO - Checking header
22/019/2013 21:19:02 - INFO - Flashing data
22/019/2013 21:19:04 - INFO - Loader : S1_Loader_Root_773f - Version : R4A069 / Boot version : r9A029 / Bootloader status : ROOTED
22/019/2013 21:19:04 - INFO - Disabling final data verification check
22/019/2013 21:19:05 - INFO - Processing kernel.sin
22/019/2013 21:19:05 - INFO - Checking header
22/019/2013 21:19:05 - INFO - Ending flash session
22/019/2013 21:19:05 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_STATIC="SIN_HEAD_VER";ERR_DYNAMIC="Failed to verify sin header";
Click to expand...
Click to collapse
stefaca said:
I had downloaded 3 tft (different stock roms) and everytime I got different error. laptop has windows8 but errors are the same on xp also.
I can flash legacyXperia11 but does it have service menu to test sensors?
here is log from flashtool from linux machine:
Click to expand...
Click to collapse
Did you try checking "no final verification" in flashtool?
Sent from my Nexus 4 running Android 4.4
mihahn said:
Did you try checking "no final verification" in flashtool?
Sent from my Nexus 4 running Android 4.4
Click to expand...
Click to collapse
did that. this is error with verification OFF. flashtool started as root user. for me flashtool is unusable
There are apps for checking proximity sensor. Try searching Hardware Sensors or similar.
dimitars84 said:
There are apps for checking proximity sensor. Try searching Hardware Sensors or similar.
Click to expand...
Click to collapse
light sensors is stuck at 0lux and proxy sensor just do nothing all of that just stop after back from CM11
stefaca said:
light sensors is stuck at 0lux and proxy sensor just do nothing all of that just stop after back from CM11
Click to expand...
Click to collapse
Use flashtool to flash ftf for your phone. Check proximity and light sensor are working in stock firmware.
dimitars84 said:
Use flashtool to flash ftf for your phone. Check proximity and light sensor are working in stock firmware.
Click to expand...
Click to collapse
a few posts ago I posted error from flashtool. I can't flash stock tft. please if you can help me
stefaca said:
a few posts ago I posted error from flashtool. I can't flash stock tft. please if you can help me
Click to expand...
Click to collapse
I somehow skipped that post, sorry. Try using older version of flashtool, like 0.9.11 see here: https://unrestrict.li/flashtool
If its same result then try this:
1. extract ftf (in linux you will have extract option, in windows I think it will work if you change the extension ftf to zip, then extract)
2. go into the extracted folder with cmd
3. connect your phone to pc in fastboot mode
3. if you set the PATH for fastboot then just do "fastboot flash boot kernel.sin"
- if not, copy kernel.sin to your ./platform-tools folder and use the same command
write if you get an error
dimitars84 said:
I somehow skipped that post, sorry. Try using older version of flashtool, like 0.9.11 see here: https://unrestrict.li/flashtool
If its same result then try this:
1. extract ftf (in linux you will have extract option, in windows I think it will work if you change the extension ftf to zip, then extract)
2. go into the extracted folder with cmd
3. connect your phone to pc in fastboot mode
3. if you set the PATH for fastboot then just do "fastboot flash boot kernel.sin"
- if not, copy kernel.sin to your ./platform-tools folder and use the same command
write if you get an error
Click to expand...
Click to collapse
when I flash kernel with this method will I be able to flash whole stock ROM?
I did some research. error is because I'm tring to flash tft version 1249-7382 but mu phone finger print is 1254-2184.
how and where I can download ftf for my phone? ((
stefaca said:
when I flash kernel with this method will I be able to flash whole stock ROM?
Click to expand...
Click to collapse
Yes. First check if you get any error.
stefaca said:
I did some research. error is because I'm tring to flash tft version 1249-7382 but mu phone finger print is 1254-2184.
how and where I can download ftf for my phone? ((
Click to expand...
Click to collapse
I don't think this would be a problem, but better check in your section for other stock roms.
Hello guys. I have a problem with my Z2. Recently and unfortunately i have updated to 6.0.1 and now i want root access on my phone to install viper4android but i couldn't find any solution. I will give all the information and you can suggest me what to do.
Phone: Sony Xperia Z2
Model: D6503
Build Number: 23.5.A.0.575
Kernel: 3.4.0-perf-g43a728
Bootloader: Not unlocked but in service menu shows it can be unlockable (however official sony site doesn't show my phone to get the code)
What should I do in this case?
If I need to downgrade, I am okay with 5.1.1 but I don't know how to downgrade with locked bootloader.
If this is the case how do i downgrade?
Is there anyway to unlock bootloader at the moment for sony devices?
Is there any root method for 6.0.1 or will be soon for Z2?
Anything could work please help..
PS: English is not my native sorry for mistakes. Thank you all.
Another topic with this question.
So, for downgrade, you don't need unlocked bootloader, just use Flashtool program, install drivers for device and Flashmod and flash FTF for your device model.
For now, no way to root Android 6 with locked bootloader.
You can always unlock the bootloader, once in service menu is positive status (Yes).
If you want to unlock bootloader, use official metod for example, but don't need for this (unlock bootloader, flash custom kernel and ....), , only to install sound mod.
That is the problem, look at official sony web site, my device is not on the list for bootloader unlock. So can you offer me a guide how to downgrade to 5.1.1, a noob friendly guide.
1. Download and install the program flashtool by Androxyde. - http://www.flashtool.net/downloads.php
2. Install drivers from installation folder /Drivers - Driver for model Xperia and Flashmod drivers.
3. Download FTF file for YOUR MODEL DEVICE with 5.1.1 from here for example:
http://forum.xda-developers.com/showthread.php?t=2759934
and copy to folder with Flashtool/ Firmwares
4. Start Flashtool and click on Flash icon.
5. Choose Flashmod (not Fastboot), and find the FTF, that you download before with 5.1.1
6. Follow the guide in the program Flashtool and all will be the OK,
xhanty said:
Hello guys. I have a problem with my Z2. Recently and unfortunately i have updated to 6.0.1 and now i want root access on my phone to install viper4android but i couldn't find any solution. I will give all the information and you can suggest me what to do.
Phone: Sony Xperia Z2
Model: D6503
Build Number: 23.5.A.0.575
Kernel: 3.4.0-perf-g43a728
Bootloader: Not unlocked but in service menu shows it can be unlockable (however official sony site doesn't show my phone to get the code)
What should I do in this case?
If I need to downgrade, I am okay with 5.1.1 but I don't know how to downgrade with locked bootloader.
If this is the case how do i downgrade?
Is there anyway to unlock bootloader at the moment for sony devices?
Is there any root method for 6.0.1 or will be soon for Z2?
Anything could work please help..
PS: English is not my native sorry for mistakes. Thank you all.
Click to expand...
Click to collapse
Hey man,first,you need to downgrade to KK (.314 it´s the best one) and then root and install recovery,then update to LP .232 or .264 and then go to MM,follow the instructions that Monipeev gave to you (but choose .314 fw) and then follow this guide: http://forum.xda-developers.com/xpe...ck-d6502-03-23-4-0-546-completeguide-t3171219 Hope you get it
Bro i don't want MM right now. I just want root access so if its 5.1.1 i am okay with that. Monipeev i will try your method and notify you about the result tomorrow.
Monipeev said:
1. Download and install the program flashtool by Androxyde. - http://www.flashtool.net/downloads.php
2. Install drivers from installation folder /Drivers - Driver for model Xperia and Flashmod drivers.
3. Download FTF file for YOUR MODEL DEVICE with 5.1.1 from here for example:
http://forum.xda-developers.com/showthread.php?t=2759934
and copy to folder with Flashtool/ Firmwares
4. Start Flashtool and click on Flash icon.
5. Choose Flashmod (not Fastboot), and find the FTF, that you download before with 5.1.1
6. Follow the guide in the program Flashtool and all will be the OK,
Click to expand...
Click to collapse
Okay after this how do i root the easiest way? kingroot one click apk ? or you suggest something else for locked bootloader bro ?
Go through the steps of Root compilation .264 Android 5.1.1, with a version of the application Kingroot that uses the author of the video.
After root success, replace Kingroot with SuperSu.
Root Android 5.1.1, .264
https://www.youtube.com/watch?v=ZJ6OPXN3M0g
Monipeev said:
Go through the steps of Root compilation .264 Android 5.1.1, with a version of the application Kingroot that uses the author of the video.
After root success, replace Kingroot with SuperSu.
Root Android 5.1.1, .264
https://www.youtube.com/watch?v=ZJ6OPXN3M0g
Click to expand...
Click to collapse
thank you bro for helping, i've got an error message while flashing
29/032/2016 14:32:05 - INFO - Start Flashing
29/032/2016 14:32:05 - INFO - Processing loader.sin
29/032/2016 14:32:05 - INFO - Checking header
29/032/2016 14:32:05 - ERROR - Processing of loader.sin finished with errors.
29/032/2016 14:32:05 - INFO - Ending flash session
29/032/2016 14:32:05 - ERROR - null
29/032/2016 14:32:05 - ERROR - Error flashing. Aborted
29/032/2016 14:32:05 - INFO - Device connected in flash mode
what do i do...
If you use last version on Flashtool 0.9.22.2, download old version and try again.
Monipeev said:
If you use last version on Flashtool 0.9.22.2, download old version and try again.
Click to expand...
Click to collapse
it was about drivers. i have installed all of the drivers (even those i don't need) in flashtool folder. also windows installed semc and somc drivers by itself and i have successfully flashed. i hope i dont get bootloop because its been 2 minutes and im still waiting for it come to menu btw i didn't wipe the userdata and applog while flashing.
Edit: just a last thing how do i replace kingroot with supersu, i can google it but since you are guiding me through this
Edit2: okay no bootloop awesome, now the only thing left to do is rooting. thank you so much for your help bro. i will notice you if i have a problem again. i hope this thread will be helpful for others too like me
I think if you follow this guide, you will finish ok:
http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html?m=1
there is a program called superSuMe apk. does it work ? any idea ?
I'm sorry, but I have no experience with this app.
At least that is described in its description.
wow now i get ''unfortunately the process com.android.media has stopped'' message and phone keeps resetting..
Edit: i think i will reflash with wipe options..
Surely it would be better.
its done
Hello,
I made the mistake of installing Magisk trying to deal with safetynet. Now my tablet won't root (on lineageOS) and won't boot if I flash again the patched stock boot.ini and recover the previously working stock backup. Most worrying, flashtool won't work. Can anyone help with this flashtool error?
Code:
26/019/2017 06:19:05 - INFO - Selected Bundle for Sony Xperia Z2 Tablet(SGP512). FW release : 23.5.A.1.291. Customization : VMo FR/DE/AT/CH/BE/NL/PL
26/019/2017 06:19:05 - INFO - Preparing files for flashing
26/019/2017 06:19:24 - INFO - Please connect your device into flashmode.
26/019/2017 06:19:31 - INFO - Device connected in flash mode
26/019/2017 06:19:31 - INFO - Opening device for R/W
26/019/2017 06:19:31 - INFO - Device ready for R/W.
26/019/2017 06:19:31 - INFO - Reading device information
26/019/2017 06:19:31 - INFO - Phone ready for flashmode operations.
26/019/2017 06:19:31 - INFO - Opening TA partition 2
26/019/2017 06:19:32 - INFO - Current device : Unknown: Jul 24 2016/19:28:59 - CB5126LP0H - Unknown: Jul 24 2016/19:28:59 - Unknown: Jul 24 2016/19:28:59 - GENERIC_23.5.A.1.291
26/019/2017 06:19:32 - INFO - Closing TA partition
26/019/2017 06:19:32 - INFO - Start Flashing
26/019/2017 06:19:32 - INFO - Processing loader.sin
26/019/2017 06:19:32 - INFO - Checking header
26/019/2017 06:19:32 - INFO - Flashing data
26/019/2017 06:19:33 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_27 / Boot version : S1_Boot_MSM8074AB_LA3.0_M_3 / Bootloader status : ROOTED
26/019/2017 06:19:33 - INFO - Max packet size set to 512K
26/019/2017 06:19:33 - INFO - USB buffer size set to 512K
26/019/2017 06:19:33 - INFO - Parsing boot delivery
26/019/2017 06:19:33 - INFO - Ending flash session
26/019/2017 06:19:33 - ERROR - null
26/019/2017 06:19:33 - ERROR - Error flashing. Aborted
I'm guessing the issue is somewhat related to the "INFO - Current device : Unknown: " part of the log, anyone? I have a backup of the TA partition, if that helps.
I am having the exact same problem. I installed a Lineage OS rom and I think it had magisk pre compiled in it so that was installed too. I have tried multiple FTF's, 2 different computers (Windows 10 and 7), different drivers, usb ports. It is driving me crazy and I am still trying different things.
I am still able to install different roms, however I am getting random reboots so that is why I want to restore FTF then re flash rcstar's Lineage OS rom as recommended.
I always do full Wipes, even tried internal storage Wipe once hoping that would fix my random reboot problem, but it hasn't. Also most new roms won't even work on my tablet (Castor Windy) due to the setup crashing bug.
Edit:
Also I have used Flashtool before, successfully, on this tablet and it has worked before. But not anymore...
I have installed a 5.1.1 Rom for now and it is stable thankfully.
Install latest flashtool, it will install the room you selected no matter what kind of tft it was, make sure you selected the correct tft. and if it doesnt work, install a stock rom for the devices via TWRP, to solve the problem, I saw once who was deodexed and rooted on 6.0.1 android version flashable zip. Hope it works
kiukirimas said:
Install latest flashtool, it will install the room you selected no matter what kind of tft it was, make sure you selected the correct tft. and if it doesnt work, install a stock rom for the devices via TWRP, to solve the problem, I saw once who was deodexed and rooted on 6.0.1 android version flashable zip. Hope it works
Click to expand...
Click to collapse
Hi thanks for the reply.
I have the latest flashtool installed. Also tried different versions. It will not flash any tft no matter what. I have tried multiple including the same exact one I used before.
I haven't been able to find any flashable zips for a stock rom.
I repeat. I have used flashtool before on my tablet and it has worked. It will not work after flashing the latest 7.1.2 Lineage ROM by rcstarr. I am almost certain this is a problem with the tablet and has nothing to do with computer, drivers, files on the computer, ect.
Edit:
I guess I should also mention that I can root and flash roms no problem. And they boot just fine (other than the new 7.0+ builds that give me random reboots) I just can't use flashtool.
Edit again:
Hey OP. I found a flashable zip. I don't think its completely stock but its close. You can try flashing this and then try Flashtool if you want:
https://mega.nz/#!VcxGyRZK!U4NqLOSeg1X_3KNC1_xXm2WnH4_i2OoZ6NwuyaIR6Hw
I am staying on 5.1.1 PAC Rom unless it becomes unstable so I haven't tested it.
Crwys said:
Hi thanks for the reply.
I have the latest flashtool installed. Also tried different versions. It will not flash any tft no matter what. I have tried multiple including the same exact one I used before.
I haven't been able to find any flashable zips for a stock rom.
I repeat. I have used flashtool before on my tablet and it has worked. It will not work after flashing the latest 7.1.2 Lineage ROM by rcstarr. I am almost certain this is a problem with the tablet and has nothing to do with computer, drivers, files on the computer, ect.
Edit:
I guess I should also mention that I can root and flash roms no problem. And they boot just fine (other than the new 7.0+ builds that give me random reboots) I just can't use flashtool.
Edit again:
Hey OP. I found a flashable zip. I don't think its completely stock but its close. You can try flashing this and then try Flashtool if you want:
https://mega.nz/#!VcxGyRZK!U4NqLOSeg1X_3KNC1_xXm2WnH4_i2OoZ6NwuyaIR6Hw
I am staying on 5.1.1 PAC Rom unless it becomes unstable so I haven't tested it.
Click to expand...
Click to collapse
Ok, I have exactly the same symptoms - flashtool worked with my tablet until I installed LineageOS. I assumed it was Magisk that broke it, but could be wrong. I might try a flashable rom to see if it allows flashtool to work again. In the mean time, I'm going to try restoring the TA partition, as I had a backup done before unlocking the bootloader.
I was able to reflash and run LineageOS now, but with safetynet broken, and some instability.
Same Problems here - now im on ACIP and its for me the best rom But if i want one day back to real stock, the problem is still there... someone have any ideas?
Ok I ended up trying the flashable zip I shared and it didn't work. The file flashed successfully but was stuck in bootloop. I tried flashtool anyways but same issue.
Restoring the TA worked for me. At least flashtool is right now flashing my SGP512!
If you were prevident enough to do a TA backup, all you need is to have root on the tablet and do the following (linux, windows should be similar):
Change to the TA.img directory
Type the commands in bold as-is
adb push TA-18062016.img "/data/local/tmp/TA.img"
(replace TA-18062016.img with the name of your TA image backup)
create a file named restore.sh with the following content (adapted from the old tarestore.sh by DevShaft here):
Code:
#!/system/bin/sh
pl=`ls /dev/block/platform`
for p in $pl
do
platform=$p
break
done
tamd5=`md5sum /dev/block/platform/$platform/by-name/TA`
echo ""
echo "old TA MD5:\n$tamd5"
tamd5=`md5sum /data/local/tmp/TA.img`
echo ""
echo "TA file MD5:\n$tamd5"
dd if=/data/local/tmp/TA.img of=/dev/block/platform/$platform/by-name/TA &> /dev/null
tamd5=`md5sum /dev/block/platform/$platform/by-name/TA`
echo ""
echo "New TA MD5:\n$tamd5"
adb push "restore.sh" "/data/local/tmp/restore.sh"
adb shell "chmod 777 /data/local/tmp/restore.sh"
adb shell
su
/data/local/tmp/restore.sh
That should fix your TA and re-lock your bootloader. After that, flashtool should work again, and you'll be able to flash the stock tft
PS: my Z2 tablet just finished booting into stock ROM, showing the setup wizard now, so it works. I'll see what safetynet shows, before wiping it all again, unlocking boot, and trying LineageOS again.
Wow that's awesome. Good for you.
I don't have a TA backup or even know what that is lol. I've been on Verizon phones for quite some time now. So my Android knowledge of root, roms, ect. Is pretty limited. Hopefully I can flash a TA zip maybe?
Thanks for keeping us updated.
Crwys said:
Wow that's awesome. Good for you.
I don't have a TA backup or even know what that is lol. I've been on Verizon phones for quite some time now. So my Android knowledge of root, roms, ect. Is pretty limited. Hopefully I can flash a TA zip maybe?
Thanks for keeping us updated.
Click to expand...
Click to collapse
Check the thread I linked (here). Unfortunately, you needed to do the backup before unlocking the bootloader, and the TA is specific to your tablet....
jbbandos said:
Check the thread I linked (here). Unfortunately, you needed to do the backup before unlocking the bootloader, and the TA is specific to your tablet....
Click to expand...
Click to collapse
Well damn that sucks. Guess I'll be stuck on Pac Rom for a while then, (maybe forever Lol) at least it runs well.
Thanks again for contributing to this thread.
What a strange thing, I have been able to flash Lineage 7.1 many times on my SGP521, and always be able to get back to stock via Flashtool, I want to know if anyone having this problem owns this model of Z2 tablet, so I can be able to share the stock rom I got, flasheable by CWM.
kiukirimas said:
What a strange thing, I have been able to flash Lineage 7.1 many times on my SGP521, and always be able to get back to stock via Flashtool, I want to know if anyone having this problem owns this model of Z2 tablet, so I can be able to share the stock rom I got, flasheable by CWM.
Click to expand...
Click to collapse
I have the SGP512, but anyway, with this issue flashing stock via the recovery doesn't seem to fix it. The only way I got it to flash again with the flash tool was to recover the TA partition.
Thank you for taking an interest but i have the sgp511
Hey I got exactly the same problem with my SGP521. I installed lineageOS and after that, my tablet did random reboots every 3- 10 minutes. I got pretty annoyed by that and tried another rom. Problem still existed. So I wanted to get back to Stock Rom with the flashtool. But I get "error: null" right after I plug the tablet with Volume Down. I mean... The tablet is unusable for me, when it reboots 130 times a day.
Is there still no solution?
Flashtool 0.9.15 works well! This is solution for SGP521
Psylou said:
Hey I got exactly the same problem with my SGP521. I installed lineageOS and after that, my tablet did random reboots every 3- 10 minutes. I got pretty annoyed by that and tried another rom. Problem still existed. So I wanted to get back to Stock Rom with the flashtool. But I get "error: null" right after I plug the tablet with Volume Down. I mean... The tablet is unusable for me, when it reboots 130 times a day.
Is there still no solution?
Click to expand...
Click to collapse
Just relock your bootloader via flashtool, and install a brand new stock rom via lfashtool too.
I have the exact same problem. 2 days spent on it, I don't how to fix it.
"Parsing boot delivery” then Aborted.
SP-05F. docomo. Now even the firmware from XperiFirm.exe cannot be installed with flashtool 0.9.23.2.
All drivers setup.
I used TWRP to install AICP.
The tab now only could get in system normally, but WIFI doesn't work either.
You should try Flashtool 0.9.15. It works with my Z2 Tablet SGP521.
I have random reboots on my z2 tablet 16gb wifi only, after flashing carbon rom. Any solution ?
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 ...