Related
Found at USB\VID_0FCE&PID_ADDE\5&476FB6F&0&6
09/047/2011 13:47:31 - INFO - Start Flashing
09/047/2011 13:47:31 - INFO - VER="R8A027";DATE="20100505";TIME="17:14:00";
1 - INFO - Flashing loader
09/047/2011 13:47:31 - ERROR - Error flashing. Aborted
09/047/2011 13:47:31 - INFO - Now unplug the device and power it on
09/047/2011 13:47:31 - INFO - Then go to application settings
09/047/2011 13:47:31 - INFO - turn on Unknown Sources and Debugging
unknown sources and and debugging already turned on
usb driver problem
vhd99 said:
Found at USB\VID_0FCE&PID_ADDE\5&476FB6F&0&6
09/047/2011 13:47:31 - INFO - Start Flashing
09/047/2011 13:47:31 - INFO - VER="R8A027";DATE="20100505";TIME="17:14:00";
1 - INFO - Flashing loader
09/047/2011 13:47:31 - ERROR - Error flashing. Aborted
09/047/2011 13:47:31 - INFO - Now unplug the device and power it on
09/047/2011 13:47:31 - INFO - Then go to application settings
09/047/2011 13:47:31 - INFO - turn on Unknown Sources and Debugging
unknown sources and and debugging already turned on
Click to expand...
Click to collapse
are you using patched loader?
You don't use unlocked bootloader. unlocked bootloader has "r8A027" version.
@Blagus... dude where have you been? MSN?
Try with the older version of flasher "FlashTool_0.2.9.1" the 3.0 versios doesn't work with the mini.
aparici said:
Try with the older version of flasher "FlashTool_0.2.9.1" the 3.0 versios doesn't work with the mini.
Click to expand...
Click to collapse
it work's you just need to make profile for mini ..
aZuZu said:
it work's you just need to make profile for mini ..
Click to expand...
Click to collapse
How I make the profile? Could you explain it? Thanks. When we expect the next update of the kernel?
Blagus said:
You don't use unlocked bootloader. unlocked bootloader has "r8A027" version.
Click to expand...
Click to collapse
Why not? i allready unlocked it
ChavitoArg said:
Why not? i allready unlocked it
Click to expand...
Click to collapse
Try to unlock it again. Your first unlock wasn't successful.
Guide: http://forum.xda-developers.com/showthread.php?t=1254225
Note: Guide also includes how to check if unlock of bootloader was successful.
Cheers ,
SpyderX
aZuZu said:
are you using patched loader?
Click to expand...
Click to collapse
Gbready root xrec,i think its patched
@blagus i dont have any bootloader
I Have this problem, and He give me the solution!
Firstly, you need Flashtool. You can get it from here
http://forum.xda-developers.com/show....php?t=1351309
Secondly, you need an ftf file for your phone.
http://forum.xda-developers.com/showthread.php?t=1477440
Now, flash the ftf file on your phone using Flashtool.
thanks to meumangarora
Yeah, yhu can go back to stock by Flashing with Flashtool, dnt try to update using SEUS or PCC.........! get ftf file for yur mobile.
samu1player said:
I have a custom rom and a custom kernel, and unlocked bootloader.. Can I conect my phone to pcc and flash the original rom?
Please I need help, wotanserver isn´t free.. I don't know how to return to stock
Click to expand...
Click to collapse
Yes you can. Firstly, you need Flashtool. You can get it from here
http://forum.xda-developers.com/showthread.php?t=1351309
Secondly, you need an ftf file for your phone. Download the Stock ROM from here
http://forum.xda-developers.com/showthread.php?t=1477440
Now, flash the ftf file on your phone using Flashtool. Flashtool will itself write the new kernal no need to worry about that
meumangarora said:
Yes you can. Firstly, you need Flashtool. You can get it from here
http://forum.xda-developers.com/showthread.php?t=1351309
Secondly, you need an ftf file for your phone. Download the Stock ROM from here
http://forum.xda-developers.com/showthread.php?t=1477440
Now, flash the ftf file on your phone using Flashtool. Flashtool will itself write the new kernal no need to worry about that
Click to expand...
Click to collapse
Hi, i have the same problem... custom kernel and rom and i already downloaded flashtool and the stock rom in ftf but the problem is taht when i put mi xperia in flashmode (green led) it stays fine for exactly 40 seconds and then it reboot to the charging battery mode when its turned off and i dont wanna start flashing the stock rom until the phone stay conected in flashmode for more than 40 secs or i think it would get bricked because a desconnection in the middle of the flashing of my rom.
would you be so kind and helpme please?? im a noob and bad at english
samu1player said:
I have a custom rom and a custom kernel, and unlocked bootloader.. Can I conect my phone to pcc and flash the original rom?
Please I need help, wotanserver isn´t free.. I don't know how to return to stock
Click to expand...
Click to collapse
u better go to this thread, i have tested unlock n relock bootloader
http://forum.xda-developers.com/showthread.php?t=1560613
thanks! It Works! u Rock! I Go to put these information
PHAMTOMLIVEiv said:
Hi, i have the same problem... custom kernel and rom and i already downloaded flashtool and the stock rom in ftf but the problem is taht when i put mi xperia in flashmode (green led) it stays fine for exactly 40 seconds and then it reboot to the charging battery mode when its turned off and i dont wanna start flashing the stock rom until the phone stay conected in flashmode for more than 40 secs or i think it would get bricked because a desconnection in the middle of the flashing of my rom.
would you be so kind and helpme please?? im a noob and bad at english
Click to expand...
Click to collapse
Try Doing all steps first, and after, when flashtool show you the request to enter in flashmode, do it! xD In my device it works!
returning to stock with unlock bootloader
Sorry, tried many times to do that and the flashtool has an error messege:
Current device : WT19i - BX902U194P - 1254-9461_R2I - 1250-5521_4.1.B.0.431 - WORLD-a_4.1.B.0.587
21/047/2013 01:47:49 - INFO - Start Flashing
21/047/2013 01:47:49 - INFO - Processing loader
21/047/2013 01:47:49 - INFO - Using an unofficial loader
21/047/2013 01:47:49 - INFO - Ending flash session
21/047/2013 01:47:49 - ERROR - C:\Flashtool\devices\WT19\loader_unlocked.sin (El sistema no puede encontrar el archivo especificado)
21/047/2013 01:47:49 - ERROR - Error flashing. Aborted
21/047/2013 01:47:49 - INFO - Device connected in flash mode
21/047/2013 01:47:51 - INFO - Device disconnected
21/047/2013 01:47:52 - INFO - Device connected in flash mode
Please, I need to reinstall stock kernel on my lww with unlock bootloader
eli_porto said:
Sorry, tried many times to do that and the flashtool has an error messege:
Current device : WT19i - BX902U194P - 1254-9461_R2I - 1250-5521_4.1.B.0.431 - WORLD-a_4.1.B.0.587
21/047/2013 01:47:49 - INFO - Start Flashing
21/047/2013 01:47:49 - INFO - Processing loader
21/047/2013 01:47:49 - INFO - Using an unofficial loader
21/047/2013 01:47:49 - INFO - Ending flash session
21/047/2013 01:47:49 - ERROR - C:\Flashtool\devices\WT19\loader_unlocked.sin (El sistema no puede encontrar el archivo especificado)
21/047/2013 01:47:49 - ERROR - Error flashing. Aborted
21/047/2013 01:47:49 - INFO - Device connected in flash mode
21/047/2013 01:47:51 - INFO - Device disconnected
21/047/2013 01:47:52 - INFO - Device connected in flash mode
Please, I need to reinstall stock kernel on my lww with unlock bootloader
Click to expand...
Click to collapse
This error is due to some missing files...try reinstallinh all the drivers and then flash if it still gives the error try flashing with older version(I recommend 0.6.8.0) and install it drivers, then flash...
Regards,
AJ
Sent from my SK17i using Tapatalk 2
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.
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 ...