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 ...
Related
Here's the FTF Files for Neo V - Nordic
Part 1: http://www.mediafire.com/?9dera4tes44pa7d
Part 2: http://www.mediafire.com/?7ik510cq7cy2p62
You may use: HJ Split to join the FTF files
HJ Split: http://www.hjsplit.org/windows/
Will it work for locked bootloaders ?
Sent from my Turbocharged MT11i
Downloading !!!!.. No it wont need an Unloacked Bootloader.. Will Work on Locked Bootloaders
Can we use other kernel? And how to root this ics? Or it's already rooted?
Sent from my MT11i using XDA
Is it in English or in nordict languages ..........
And anyone tested it on NEO V ???
Please give us a brief review .....
I got this in flashtools:
14/034/2012 09:34:36 - INFO - Flashing adsp.sin
14/034/2012 09:34:39 - INFO - Flashing amss_fs_haida.sin
14/034/2012 09:34:39 - INFO - Flashing kernel.sin
14/034/2012 09:34:42 - INFO - Flashing fota1.sin
14/034/2012 09:34:43 - INFO - Flashing fota0.sin
14/034/2012 09:34:44 - INFO - Flashing apps_log.sin
14/034/2012 09:34:44 - INFO - Flashing amss.sin
14/034/2012 09:34:54 - INFO - Flashing cache.sin
14/034/2012 09:34:54 - INFO - Flashing system.sin
14/037/2012 09:37:17 - INFO - Flashing userdata.sin
14/037/2012 09:37:17 - ERROR - Error flashing. Aborted
14/037/2012 09:37:17 - INFO - Now unplug the device and power it on
14/037/2012 09:37:17 - INFO - Then go to application settings
14/037/2012 09:37:17 - INFO - turn on Unknown Sources and Debugging
wilsonchuchu said:
I got this in flashtools:
14/034/2012 09:34:36 - INFO - Flashing adsp.sin
14/034/2012 09:34:39 - INFO - Flashing amss_fs_haida.sin
14/034/2012 09:34:39 - INFO - Flashing kernel.sin
14/034/2012 09:34:42 - INFO - Flashing fota1.sin
14/034/2012 09:34:43 - INFO - Flashing fota0.sin
14/034/2012 09:34:44 - INFO - Flashing apps_log.sin
14/034/2012 09:34:44 - INFO - Flashing amss.sin
14/034/2012 09:34:54 - INFO - Flashing cache.sin
14/034/2012 09:34:54 - INFO - Flashing system.sin
14/037/2012 09:37:17 - INFO - Flashing userdata.sin
14/037/2012 09:37:17 - ERROR - Error flashing. Aborted
14/037/2012 09:37:17 - INFO - Now unplug the device and power it on
14/037/2012 09:37:17 - INFO - Then go to application settings
14/037/2012 09:37:17 - INFO - turn on Unknown Sources and Debugging
Click to expand...
Click to collapse
Someone reported to me that error earlier, just ignore them ... just boot up your phone...
kvroath said:
Can we use other kernel? And how to root this ics? Or it's already rooted?
Sent from my MT11i using XDA
Click to expand...
Click to collapse
Yes you can use other Kernel such as from NightElf_ICS-Beta-RC2_NOZRAM, and you can only do that if you do have an unlocked bootloader.
Here's a root fix for this ROM (this will only work if you have CWM installed)
http://www.mediafire.com/?c943rhixt7q9f88
how to root with unlocked boot loader?
archijit said:
how to root with unlocked boot loader?
Click to expand...
Click to collapse
install CWM first and download this SU fix
http://www.mediafire.com/?c943rhixt7q9f88
then flash it via CWM
Grateful if someone could create a cwm flashable zip (or atleast provide the system dump)..
DrearierJester1 said:
install CWM first and download this SU fix
http://www.mediafire.com/?c943rhixt7q9f88
then flash it via CWM
Click to expand...
Click to collapse
means flash night elf kernel to have CWM.
any other way to have cwm without changing kernel?
DrearierJester1 said:
Someone reported to me that error earlier, just ignore them ... just boot up your phone...
Click to expand...
Click to collapse
But I got bootloop
rom is overall smooth.
baseband .70
playing games is same as on beta version.
I have unlocked bootloader and CWM. How to flash this ROM?
Have changed lines in build.prop and updated via Pc Companion Works nice No data/app lost
I have locked BL and looking for root? Tried form latest FT but getting error.
archijit said:
means flash night elf kernel to have CWM.
any other way to have cwm without changing kernel?
Click to expand...
Click to collapse
nope
Flashed!! Working Fine Except Screen Info
it wasnt Working on MIUI Either,,but working in Beta,,, Whats Wrong with it....
can i flash this using flashtool??I have a locked bootloader and am on pure non rooted Stock?? This is the my first try at flashtool too..
puttytatko said:
can i flash this using flashtool on a locked bootloader???
Click to expand...
Click to collapse
YES
Hi, whenever I am trying to flash the stock Xperia_Mini_ST15i_4.1.B.0.587 ftf using flashtool, I am encountering the following error. Below is the error
Code:
16/017/2012 23:17:44 - INFO - <- This level is successfully initialized
16/017/2012 23:17:44 - INFO - Flashtool Version 0.9.8.0 built on 2012-10-01 19:35:32
16/017/2012 23:17:44 - INFO - You can drag and drop ftf files here to start flashing them
16/017/2012 23:17:49 - INFO - Device disconnected
16/017/2012 23:17:55 - INFO - Device connected in flash mode
16/018/2012 23:18:00 - INFO - Selected Xperia Mini (ST15i)_4.1.B.0.587.ftf
16/018/2012 23:18:00 - INFO - Preparing files for flashing
16/018/2012 23:18:15 - INFO - Please connect your device into flashmode.
16/018/2012 23:18:16 - INFO - Opening device for R/W
16/018/2012 23:18:16 - INFO - Reading device information
16/018/2012 23:18:36 - INFO - Start Flashing
16/018/2012 23:18:36 - INFO - Processing loader
16/018/2012 23:18:36 - INFO - Checking header
16/018/2012 23:18:36 - INFO - Ending flash session
16/018/2012 23:18:36 - ERROR -
16/018/2012 23:18:36 - ERROR - Error flashing. Aborted
16/018/2012 23:18:36 - INFO - Device connected in flash mode
16/018/2012 23:18:37 - INFO - Device disconnected
I am currently using FXP 146 with MESA Kernel 2.3... Please help ..
Hmmmm...You should make Nandroid backup (stock .587) first before you flash FXP Roms....if you do then you have no problem restoring back to stock....
since you didn't make Nandroid backup, i suggest you flash stock kernel or custom kernel base on ICS (i recommended Mesa Kernel ICS v2.2)...after flashing kernel then try flashing stock roms....
Pusak Gaoq said:
Hmmmm...You should make Nandroid backup (stock .587) first before you flash FXP Roms....if you do then you have no problem restoring back to stock....
Click to expand...
Click to collapse
Does nandroid backup actually backup the kernel? From what I can see in my cwm backup folder, it doesn't seem to include kernel
tonasc said:
Does nandroid backup actually backup the kernel? From what I can see in my cwm backup folder, it doesn't seem to include kernel
Click to expand...
Click to collapse
No it doesn't backup kernel but restoring from CWM is much easy than flashing stock ROM using flashtool....
Sent Using iPusak Gaoq™
Problem solved... It was connecting the phone before Flashtool started the flashing process... Need to connect the phone when it pops up asking to connect the phone....
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.
i was trying to use the flashtool to save my bricked xpreia x,but it says
9/020/2016 02:20:39 - INFO - Selected Bundle for Sony Xperia X (F5122). FW release : 34.0.A.2.292. Customization : [email protected]
29/020/2016 02:20:39 - INFO - Preparing files for flashing
29/021/2016 02:21:00 - INFO - Please connect your device into flashmode.
29/021/2016 02:21:01 - INFO - Opening device for R/W
29/021/2016 02:21:01 - INFO - Start Flashing
29/021/2016 02:21:01 - ERROR - root : this bundle is not valid
29/023/2016 02:23:05 - INFO - Ending flash session
29/023/2016 02:23:05 - ERROR - C:\Users\yan\.flashTool\devices\F51XX\loader.sin (The system cannot find the file specified)
29/023/2016 02:23:05 - ERROR - Error flashing. Aborted
where can i get the loader.sin???
same problem here, no loader.sin file in any of x series folders (user/.flashTool/devices/Fxxx)....
How the hell do we build ftf files???
dmarinon said:
same problem here, no loader.sin file in any of x series folders (user/.flashTool/devices/Fxxx)....
How the hell do we build ftf files???
Click to expand...
Click to collapse
hi! i had the same Problem few days, but today i downloaded again the Firmware and make the ftf, this time i coud Flash it without the stupid error.
just try again download the Firmware and create the ftf.
hope i could help
xpt1 said:
hi! i had the same Problem few days, but today i downloaded again the Firmware and make the ftf, this time i coud Flash it without the stupid error.
just try again download the Firmware and create the ftf.
hope i could help
Click to expand...
Click to collapse
Thanks but problem was flashtool not being updated to latest version. X series firmwares don't have loader.sin files, but previous flashtool versions didn't know that
dmarinon said:
Thanks but problem was flashtool not being updated to latest version. X series firmwares don't have loader.sin files, but previous flashtool versions didn't know that
Click to expand...
Click to collapse
what version do you use ??
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 ?