Related
Trying to upgrade to http://forum.xda-developers.com/showthread.php?t=2687443
Android 4.4 Kitkat. Phone already rooted and process done before twice no problems.
Cant flash eft.. I am pulling my hair out over this. Please help!
25/009/2014 07:09:43 - INFO - <- This level is successfully initialized
25/009/2014 07:09:43 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
25/009/2014 07:09:51 - INFO - Device disconnected
25/010/2014 07:10:02 - INFO - Device connected in flash mode
25/010/2014 07:10:16 - INFO - Selected C6903 / 14.3.A.0.681 / Customized_FR
25/010/2014 07:10:16 - INFO - Preparing files for flashing
25/010/2014 07:10:17 - ERROR - 1
25/010/2014 07:10:17 - INFO - Cannot open bundle. Flash operation canceled
solrazr said:
Trying to upgrade to http://forum.xda-developers.com/showthread.php?t=2687443
Android 4.4 Kitkat. Phone already rooted and process done before twice no problems.
Cant flash eft.. I am pulling my hair out over this. Please help!
25/009/2014 07:09:43 - INFO - <- This level is successfully initialized
25/009/2014 07:09:43 - INFO - Flashtool Version 0.9.13.0 built on 2013-06-04 22:50:00
25/009/2014 07:09:51 - INFO - Device disconnected
25/010/2014 07:10:02 - INFO - Device connected in flash mode
25/010/2014 07:10:16 - INFO - Selected C6903 / 14.3.A.0.681 / Customized_FR
25/010/2014 07:10:16 - INFO - Preparing files for flashing
25/010/2014 07:10:17 - ERROR - 1
25/010/2014 07:10:17 - INFO - Cannot open bundle. Flash operation canceled
Click to expand...
Click to collapse
Use the newest Flashtool Version 0.9.15.0
harfot said:
Use the newest Flashtool Version 0.9.15.0
Click to expand...
Click to collapse
Ill give it a try and update in a few.
solrazr said:
Ill give it a try and update in a few.
Click to expand...
Click to collapse
Updating your flashtool to the latest version should fix the problem :highfive:
I've faced that problem before
Yep that did the trick. Thank both of you. I cant post on the original thread I linked, but I was going to reply to him to update his info on making sure every1 uses the latest flashtool so others don't have the same issue, but I can't post a reply there, (guessing because Im new to posting, even though I been on this forum awhile.)
Many Thanks.
dear friend i have the same problem. however i have found the solution on my own risk! i would like to share the solution that worked for me and i am sure that will work for you as well. just go to C:\Users\Milan\.flashTool\firmwares there you will find some files or folders. just delete them. after deleting those files, just switch off your phone(without connecting USB cable to it) then hold volume down button and same time connect usb cable. flashtool shows that you have connected your phone in flashmode. thats it! leave your phone aside and select the file you wish to flash. relax! everything will be done automatically.
furthemore, it may take some time to see your phone in home screen so just wait for 5minutes. then you will see that you have successfully flashed your firmware. for more, write to me @ [email protected]
24/025/2015 11:25:48 - INFO - Device connected in flash mode
24/026/2015 11:26:13 - INFO - Selected Bundle for Shakira E15. FW release : 2.6.32.63-XPerience-KK06. Customization : XPerience-06
24/026/2015 11:26:13 - INFO - Preparing files for flashing
24/026/2015 11:26:13 - ERROR - ./firmwares/prepared/kernel.sin (No such file or directory)
24/026/2015 11:26:13 - INFO - Cannot open bundle. Flash operation canceled
how do we solve this
??????
sadhuu said:
24/025/2015 11:25:48 - INFO - Device connected in flash mode
24/026/2015 11:26:13 - INFO - Selected Bundle for Shakira E15. FW release : 2.6.32.63-XPerience-KK06. Customization : XPerience-06
24/026/2015 11:26:13 - INFO - Preparing files for flashing
24/026/2015 11:26:13 - ERROR - ./firmwares/prepared/kernel.sin (No such file or directory)
24/026/2015 11:26:13 - INFO - Cannot open bundle. Flash operation canceled
how do we solve this
??????
Click to expand...
Click to collapse
Just Go to ./firmwares/prepared/ this folder remove all files.go back again to flashtool select file again for flash wait few mints until flashtool asks u for connect a phone in flash mode.you are done
it,s happen sometime when ftf file did,nt extract by flashtool properly.
20/050/2017 11:50:26 - INFO - Preparing files for flashing
20/050/2017 11:50:26 - ERROR - null
20/050/2017 11:50:26 - INFO - Cannot open bundle. Flash operation canceled
как мне решить эту проблему?
Sony xperia me dual d2302 I was installed Expedia z3style custom ROM now I want to reflash my official firmware when I want to flash .Flash tool says
ERROR : Cannot open bundle flashing process canceled
Had the same error during my attempts to flash Xperia SO-02K firmware which I needed to flash for DRM keys backup. Tried Flashtool v0.9.18.6 and v0.9.15 for windows, both were able to read it, but threw "root : this bundle is not valid" and "Cannot open bundle. Flash operation canceled" errors during flashing (v0.9.34 and v0.9.28 didn't even recognize the firmware). Tried four different versions of the firmware and ultimately used newflasher v20 instead (latest version failed).
Hi,
I'm having a serious issue with my flashtool. Recently I was flashing my phone to 14.1.G.1.534. I was playing a video game at the time. My computer ran out of RAM and crashed in the middle of flashing. My phone is inoperable and flashtool has a problem. I uninstalled it and grabbed the latest version. It read..
Code:
20/036/2014 23:36:53 - INFO - Selected Bundle for Sony Xperia Z1 (C6903). FW release : 14.1.G.1.534. Customization : [NUT]
20/036/2014 23:36:53 - INFO - Preparing files for flashing
20/036/2014 23:36:53 - ERROR - Cannot delete C:\Flashtool\.\firmwares\prepared\boot
I also tried the other ftfs that I had (my phone disconnected) and it still output errors.
Code:
20/036/2014 23:36:53 - INFO - Cannot open bundle. Flash operation canceled
20/038/2014 23:38:17 - INFO - Selected Bundle for Sony Xperia Z1 (C6903). FW release : 14.3.A.0.757. Customization : Unbranded
20/038/2014 23:38:17 - INFO - Preparing files for flashing
20/038/2014 23:38:17 - ERROR - Cannot delete C:\Flashtool\.\firmwares\prepared\boot
20/038/2014 23:38:17 - INFO - Cannot open bundle. Flash operation canceled
20/042/2014 23:42:39 - INFO - Selected Bundle for Sony Xperia Z1 (C6903). FW release : 14.3.A.0.681. Customization : Customized_FR
20/042/2014 23:42:39 - INFO - Preparing files for flashing
20/042/2014 23:42:39 - ERROR - Cannot delete C:\Flashtool\.\firmwares\prepared\boot
20/042/2014 23:42:39 - INFO - Cannot open bundle. Flash operation canceled
I'm really scared for my device. Flashtool is my secuity blanket, and now it doesn't work. Help!
THREAD SOLVED
Figured it out!
I went through C:\flashtool and deleted the "prepared" folder under the folder "firmwares". That fixed the problem, apparently.
kentexcitebot said:
THREAD SOLVED
Figured it out!
I went through C:\flashtool and deleted the "prepared" folder under the folder "firmwares". That fixed the problem, apparently.
Click to expand...
Click to collapse
thanks buddy, this help alot. Was starting to panic...
kentexcitebot said:
THREAD SOLVED
Figured it out!
I went through C:\flashtool and deleted the "prepared" folder under the folder "firmwares". That fixed the problem, apparently.
Click to expand...
Click to collapse
thnx a ton man... u saved my life... my phone :good:
unale to solve by above mentioned procedure. Any help
24/025/2015 11:25:48 - INFO - Device connected in flash mode
24/026/2015 11:26:13 - INFO - Selected Bundle for Shakira E15. FW release : 2.6.32.63-XPerience-KK06. Customization : XPerience-06
24/026/2015 11:26:13 - INFO - Preparing files for flashing
24/026/2015 11:26:13 - ERROR - ./firmwares/prepared/kernel.sin (No such file or directory)
24/026/2015 11:26:13 - INFO - Cannot open bundle. Flash operation canceled
how to solve this
????
this is in mac
I'm not able edit any part of flattop
love u men hats off for u
kentexcitebot said:
THREAD SOLVED
Figured it out!
I went through C:\flashtool and deleted the "prepared" folder under the folder "firmwares". That fixed the problem, apparently.
Click to expand...
Click to collapse
5 years later and it's still helpful. Thanks man
thanks
kentexcitebot said:
THREAD SOLVED
Figured it out!
I went through C:\flashtool and deleted the "prepared" folder under the folder "firmwares". That fixed the problem, apparently.
Click to expand...
Click to collapse
thanks u r my saved
Worked like a charm thank you
still doesn't work. I'm trying to flash my Xperia X Performance
Hey folks, I was following the how-to-root thread and made it to the very end without seeing any error messages. Unfortunately, when I booted up the device, it got stuck at the black 'sony' screen. So I dutifully scrolled up to step 1, as I have done plenty of times before, but I am having some trouble recovering my device. Also I feel like I should say, my previous 5.0.2 install was done using that thread with no issues, but I'd like to get up to 5.1.1 since I heard the memory management issues I've been having were improved.
FWs were acquired from the sticky firmware thread:
23.0.1.A.5.77 - Unbranded - USA (1289-7524)
23.4.A.0.546 - Unbranded - USA (1289-7524)
I have tried this on W7 and W10. I am using the OEM cable with a USB 2.0 port on my motherboard.
Here is my flashtools error:
21/054/2015 21:54:52 - INFO - Flashtool Version 0.9.19.3 built on 13-09-2015 17:00:00
21/054/2015 21:54:52 - INFO - Executing search strategies to find proxy selector
21/054/2015 21:54:52 - INFO - No proxy found for IE. Trying next one
21/054/2015 21:54:52 - INFO - Strategy firefox failed trying next one : No Firefox installation found
21/054/2015 21:54:52 - INFO - No proxy found for java. Trying next one
21/054/2015 21:54:52 - INFO - Syncing devices from github
21/054/2015 21:54:53 - INFO - Scanning devices folder for changes.
21/055/2015 21:55:01 - INFO - Pulling changes from github.
21/055/2015 21:55:01 - INFO - Devices sync finished.
21/055/2015 21:55:05 - INFO - Device disconnected
21/057/2015 21:57:00 - INFO - Selected Bundle for Sony Xperia Z3 Compact (D5803). FW release : 23.0.A.2.93. Customization : USA
21/057/2015 21:57:00 - INFO - Preparing files for flashing
21/057/2015 21:57:12 - INFO - Please connect your device into flashmode.
21/057/2015 21:57:19 - INFO - Device connected in flash mode
21/057/2015 21:57:19 - INFO - Opening device for R/W
21/057/2015 21:57:19 - INFO - Reading device information
21/057/2015 21:57:19 - INFO - Phone ready for flashmode operations.
21/057/2015 21:57:19 - INFO - Opening TA partition 2
21/057/2015 21:57:20 - INFO - Current device : Unknown: Apr 13 2015/13:21:35 - YT91127UXN - Unknown: Apr 13 2015/13:21:35 - 1285-6521_23.1.A.1.28 - Unknown: Apr 13 2015/13:21:35
21/057/2015 21:57:20 - INFO - Closing TA partition
21/057/2015 21:57:20 - INFO - Start Flashing
21/057/2015 21:57:20 - INFO - Processing loader.sin
21/057/2015 21:57:20 - INFO - Checking header
21/057/2015 21:57:20 - INFO - Flashing data
21/057/2015 21:57:20 - INFO - Loader : S1_Root_9c84 - Version : MSM8974AB_22 / Boot version : S1_Boot_MSM8974AC_LA3.0_52-2 / Bootloader status : ROOTABLE
21/057/2015 21:57:20 - INFO - Max packet size set to 512K
21/057/2015 21:57:20 - INFO - Parsing boot delivery
21/057/2015 21:57:20 - INFO - Ending flash session
21/057/2015 21:57:21 - ERROR -
21/057/2015 21:57:21 - ERROR - Error flashing. Aborted
21/057/2015 21:57:21 - INFO - Device connected in flash mode
21/057/2015 21:57:21 - INFO - Device disconnected
21/057/2015 21:57:24 - INFO - Device connected in flash mode
21/005/2015 22:05:21 - INFO - List of connected devices (Device Id) :
21/005/2015 22:05:21 - INFO - - USB\VID_0FCE&PID_ADDE\5&1E313DEC&0&4 Driver installed : true
21/005/2015 22:05:21 - INFO - List of ADB devices :
21/005/2015 22:05:21 - INFO - - none
21/005/2015 22:05:21 - INFO - List of fastboot devices :
21/005/2015 22:05:21 - INFO - - none
And I'm also having trouble with PC Companion's repair function:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit: I have heard on the grapevine that PC Companion does not download firmwares properly on Windows 10, so I threw W7 on my secondary hard drive. Sure enough, it downloaded just fine. If your PC companion is giving you "Unable to communicate with Sony Update Engine" and you are on W10, there's your problem.
UNFORTUNATELY, I am now getting "Sony Update Engine doesn't have software available for your device." I've taken it to the search engines and it seems the general idea is to use flashtool instead. Unfortunately, flashtool's behavior on W7 is completely identical to what I've gotten on W10.
Hi,
Did you tried with another firmware like 23.0.A.2.93 - Unbranded - USA (1289-7524) ?
Regards.
Oijkn said:
Hi,
Did you tried with another firmware like 23.0.A.2.93 - Unbranded - USA (1289-7524) ?
Regards.
Click to expand...
Click to collapse
Yes, I've tried with D5803_23.0.A.2.93_USA.ftf with the same results.
I remember having a similar problem on my Z aswell on a friends Z phone. The only solution I found was this one:
Unlock bootloader
Fastboot a kernel with recovery which supports Ext.SD - OR - if you still have a working recovery you can try to flash the kernel through recovery
Use another phone/cardreader to put a flashable zip containing your ROM on the Ext.SD. - Use a homemade flash-able zip using PRFC including only system and superSU and recovery, do not include kernels.
Boot into the new recovery and flash the ROM. Restart the device
--> At this point phone should be working again but bootloader is still unlocked
With an unlocked bootloader, flash a completely stock ROM and kernel ( you'll lose recovery ) - Try flashtool. For me, flashtool still didn't want to flash so I made a flashable FTF INCLUDING the kernel this time.
relock bootloader -
Flash rootable firmware ( for Z this was the current firmware, for Z3C you'll need to flash the old one ) - Now, with the bootloader unlocked, flashtool should again be able to flash to your device. IF flashtool still doesn't want to flash, I'm afraid you'll have to live with an unlocked bootloader for now and use the DRM tool linked in the post for the AndroPlus kernel to recovery DRM functions.
root the old firmware, upgrade to newest firmware using the known method to keep root and restore TA-partition ( hope you have it backed up ).
Neither flashtool nor SPC could flash to the phone, but after this everything went back to working and the phone being flashable again.
PS: Beware with what kernel you flash, on my first Z I flashed a kernel which prevented me from charging the phone until it was completely fixed. Due to problems with the ROM I was down to 7 percent when I flashed the original kernel and was able to charge again
EDIT: Some extra info added
Alright, so thanks for your post instead of shotgunning 'reboot it' like the folks at the sony forums are doing
I'm going to run over to Walmart for a cardreader since my nexus 4 doesn't have a slot.
Do you remember what kernel you used? I'll probably use TWRP with it since it had no problem putting nandroids on my sdcard before and I know how to work it.
Jake3 said:
Alright, so thanks for your post instead of shotgunning 'reboot it' like the folks at the sony forums are doing
I'm going to run over to Walmart for a cardreader since my nexus 4 doesn't have a slot.
Do you remember what kernel you used? I'll probably use TWRP with it since it had no problem putting nandroids on my sdcard before and I know how to work it.
Click to expand...
Click to collapse
On the original Z I used doomkernel, which was at the time the simpelest kernel which had recovery. For the Z3C I would recommend this kernel:
HTML:
http://forum.xda-developers.com/z3-compact/development/kernel-andropluskernel-t2937173
Since it is based of Doomkernel's kernel.
Just remember to have your TA partition backed up before you begin and only start with 100% battery left, you wouldn't want to be down to your last 7% like what happened to me ( I lost atleast 5 years that day )
EDIT: V60 of that kernel is for 23.4.A.0.546 so use that one and use a home-made flashable zip of that FTF file using PRFC creator but only include system, superSU and recovery, do not include the kernel or FOTA kernel or the other options.
I added some more info to my previous post. Hope you get the phone working again!
Isocadia, thanks again for your expert advice. I'm pleased to report that I have managed to unlock my bootloader, flash in the kernel & recovery, boot to recovery, and restore to a nandroid. I'm not quite in the clear as I still need to relock, restore drm, and actually get that 5.1.1 complete, but that shouldn't be a problem now that everything is behaving like I'd expect.
I used "Minimal ADB and Fastboot" for the fastboot commands and v60 of the kernel at your recc. I let the device charge for a few hours before starting and was pleased to see it at 98% when recovery loaded.
edit: no flashtool errors so far
edit2: op success! Either I had some old drivers around or W10 itself was the problem, because everything went fine in my fresh w7 install.
Great to hear you got it working again!
Sent from my D5803 using XDA Free mobile app
I installed a rom kitkat on my xperia sp, he's with bootloader locked, (LBL), I would like to know the step-by-step procedure to re-stock ROM, or if there is any way to unlock the bootloader on this version to install the UBL lollipop if possible also the pass-by-step?
They write in a simple way because I speak Portuguese-BR, and I do not quite understand.
I used the google translator excuses!
gabriel2mm said:
I installed a rom kitkat on my xperia sp, he's with bootloader locked, (LBL), I would like to know the step-by-step procedure to re-stock ROM, or if there is any way to unlock the bootloader on this version to install the UBL lollipop if possible also the pass-by-step?
They write in a simple way because I speak Portuguese-BR, and I do not quite understand.
I used the google translator excuses!
Click to expand...
Click to collapse
You can go back to stock rom using Flashtool
How to use flashtool : http://forum.xda-developers.com/showthread.php?t=2658952
How to unlock bootloader : http://forum.xda-developers.com/showthread.php?t=2354721
Use TWRP to flash a Lollipop rom ,other instructions are the same :good:
$Moses said:
You can go back to stock rom using Flashtool
How to use flashtool : http://forum.xda-developers.com/showthread.php?t=2658952
How to unlock bootloader : http://forum.xda-developers.com/showthread.php?t=2354721
Use TWRP to flash a Lollipop rom ,other instructions are the same :good:
Click to expand...
Click to collapse
guy I followed all the steps that you gave me, but the first step to go back to stock rom I found the following error .:
Code:
26/030/2015 19:30:23 - INFO - Flashtool Version 0.9.19.8 built on 24-09-2015 22:00:00
26/030/2015 19:30:23 - INFO - Executing search strategies to find proxy selector
26/030/2015 19:30:24 - INFO - No proxy found for IE. Trying next one
26/030/2015 19:30:24 - INFO - Strategy firefox failed trying next one : No Firefox installation found
26/030/2015 19:30:25 - INFO - No proxy found for java. Trying next one
26/030/2015 19:30:25 - INFO - Syncing devices from github
26/030/2015 19:30:26 - INFO - Scanning devices folder for changes.
26/030/2015 19:30:58 - INFO - Changes have been found. Doing a hard reset (removing user modifications).
26/031/2015 19:31:00 - INFO - Pulling changes from github.
26/031/2015 19:31:02 - INFO - Devices sync finished.
26/031/2015 19:31:09 - INFO - Device disconnected
26/031/2015 19:31:49 - INFO - Selected Bundle for Sony Xperia SP (C5303). FW release : 12.1.A.1.201. Customization : GENERIC BR
26/031/2015 19:31:49 - INFO - Preparing files for flashing
26/034/2015 19:34:45 - INFO - Please connect your device into flashmode.
26/035/2015 19:35:00 - INFO - Device connected in flash mode
26/035/2015 19:35:00 - INFO - Opening device for R/W
26/035/2015 19:35:01 - INFO - Start Flashing
26/035/2015 19:35:01 - INFO - Processing loader.sin
26/035/2015 19:35:01 - INFO - Checking header
26/035/2015 19:35:01 - ERROR - Processing of loader.sin finished with errors.
26/035/2015 19:35:01 - INFO - Ending flash session
26/035/2015 19:35:01 - ERROR -
26/035/2015 19:35:01 - ERROR - Error flashing. Aborted
26/035/2015 19:35:04 - INFO - Device connected in flash mode
help me, what do I do now?
Make sure to install the correct drivers and uncheck the reset factory in the flashing process
did you install the appropriate drivers which can be seen in the drivers folder within the flashtool folder in c drive? There u must install 3 of them (Flashmode Drivers, Fastboot Drivers, Common drivers Viskan board)
XZ/KAGURA/F8331 OmniROM BUILDS
OREO 8.1
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (Optional) Flash a gapps package
4. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. Wifi sometimes disconnects (fixed by enabling/disabling wifi)
2. No USB tethering
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-8.0
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
[ROM][XZ][O][8.1][WEEKLY]OmniROM, ROM for the Sony Xperia XZ
Contributors
oshmoun, humberos
Source Code: https://github.com/omnirom
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: latest stock ftf
Version Information
Status: Beta
Created 2018-01-14
Last Updated 2018-02-21
what a surprise! finally, a 8.1 on xz
thats is great message for me today i will flash it
F8332
Does F8332 support this post, have you ever tried?
---------- Post added at 02:21 PM ---------- Previous post was at 02:08 PM ----------
Fuly support F8332 ? Any more sim card issues?
orsngepzr said:
Does F8332 support this post, have you ever tried?
---------- Post added at 02:21 PM ---------- Previous post was at 02:08 PM ----------
Fuly support F8332 ? Any more sim card issues?
Click to expand...
Click to collapse
It should boot, but not sure about whether it will detect the second sim slot
This's patch for F8332 supporting.
Hi! When can I find changelog?
I guess that this doesn't support exfat partition, but, does it support writting to external SDCard.
L'ily said:
It seems to, I have Newsstand and Play Music writing to my card, so do TWRP and TiB, no issues there. I've seen you asking in over 9000 threads about exFAT, I'm legitimately curious as to why. Are there major benefits to exFAT formatting?
Click to expand...
Click to collapse
Other AOSP rom like pure AOSP cant write to External SDcard. I use titanium backup on EXSDcard and when I select the folder where are the backup files, there is a line that says that that folder is read only.
The reason for using exFAT is that you can have files in size more that 2Gb, like a movie or other big files.
Hello,
I'm trying to upgrade from version 7.1.2 to version 8.1.0 of OmniRom.
But I have a problem with flashing the partition OEM.
I have this message when I launch the command "fastboot flash oem odm_tone.simg"
target reported max download size of 268435456 bytes
sending sparse 'oem' (244164 KB)...
OKAY [ 9.799s]
writing 'oem'...
FAILED (remote: Command not allowed)
finished. total time: 9.818s
Click to expand...
Click to collapse
Somebody can help me?
ZackaruS said:
Hello,
I'm trying to upgrade from version 7.1.2 to version 8.1.0 of OmniRom.
But I have a problem with flashing the partition OEM.
I have this message when I launch the command "fastboot flash oem odm_tone.simg"
Somebody can help me?
Click to expand...
Click to collapse
Do you mean 7.1.2 stock rom?
If so, is your bootloader unlocked? You definitely need that
You also have to tick that OEM option in the developer settings to be able to unlock or do modifications.
On this phone, I have OmniRom v7.1.2-20171120. The bootloader is unlocked.
But the flash don't work.
It's strange because it's worked with the Xperia X of my father (same version of OmniRom).
I have successfully flash the partition OEM.
ZackaruS said:
Hello,
I'm trying to upgrade from version 7.1.2 to version 8.1.0 of OmniRom.
But I have a problem with flashing the partition OEM.
I have this message when I launch the command "fastboot flash oem odm_tone.simg"
Somebody can help me?
Click to expand...
Click to collapse
unlock bootloader and try any other country oreo stock rom (I tried Thailand .58) and try.
Kernel Update
A notice for the upcoming weekly:
The kernel has been updated to a new version. This requires an updated odm image, which Sony has supplied here
Please note that the zip is not flashable, simply unpack it then flash the img file inside using "fastboot flash oem <img_file>"
If you update to the weekly of 20180128, when it's released, then you MUST flash the new odm image, otherwise you'll end up with issues like a nonfunctional camera.
L'ily said:
Can the 29th build be dirty flashed after updating the ODM partition?
Click to expand...
Click to collapse
yes that should work, no changes to userdata are needed by the kernel and odm update far as I know.
L'ily said:
Outstanding. Where are merging the latest Substratum commits and bluetooth battery level APIs in terms of priorities? Substratum as root is less than ideal and it would be nice if my phone reported an accurate battery level for my headphones and not "100%" all the time. I'm guessing these are low though.
Click to expand...
Click to collapse
I don't think that omnirom merges WIP commits from the substratum team.
L'ily said:
Lul, no this would be unlikely, I am distracted right now and misspoke. I meant integrating Substratum support as I think Omni 7.1.2 did.
Click to expand...
Click to collapse
Not sure about that, but about bt battery, that one already works fine. I see a battery bar next to the bt symbol, and the qs tile reports the battery percentage just fine.
L'ily said:
Damn it. Reporting the Sony MDR-1000X BT headphones as incompatible then. Unless they've somehow gained the ability to charge themselves via magic and/or science. Which would be pretty sweet, but somehow I don't think they have.
Click to expand...
Click to collapse
I'm pretty new to how bt devices work, but I think the issue here is that these headphones use Apple's method of reporting battery life. Could be (very) wrong there though.
I have a problem with flashtool
Yes, you said I have to flash .ftf to flash odm file.
But I can't flash.
look the other of writing.
I am an user of ExistenZ Oreo 2.0.0
And I have a problem with flashing ftf file.
Flashtool notice me a log.
28/055/2018 21:55:55 - INFO - Closing TA partition
28/055/2018 21:55:55 - INFO - Start Flashing
28/055/2018 21:55:55 - INFO - No loader in the bundle. Searching for one
28/055/2018 21:55:55 - INFO - No matching loader found
28/055/2018 21:55:55 - WARN - No loader found or set manually. Skipping loader
28/055/2018 21:55:55 - INFO - Loader : S1_Root_de8d - Version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_117 / Boot version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_117 / Bootloader status : ROOTED
28/055/2018 21:55:55 - INFO - Max packet size set to 4M
28/055/2018 21:55:55 - INFO - USB buffer size set to 512K
28/055/2018 21:55:56 - INFO - Parsing boot delivery
28/055/2018 21:55:56 - INFO - No flash script found.
28/055/2018 21:55:56 - INFO - Flash script is mandatory. Closing session
28/055/2018 21:55:56 - INFO - Ending flash session
28/055/2018 21:55:56 - INFO - Flashing finished.
28/055/2018 21:55:56 - INFO - Please unplug and start your phone
28/055/2018 21:55:56 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
28/056/2018 21:56:00 - INFO - Device disconnected
28/056/2018 21:56:01 - INFO - Device connected in flash mode
What's the problem?
XperiaXZperson said:
Yes, you said I have to flash .ftf to flash odm file.
But I can't flash.
look the other of writing.
I am an user of ExistenZ Oreo 2.0.0
And I have a problem with flashing ftf file.
Flashtool notice me a log.
28/055/2018 21:55:55 - INFO - Closing TA partition
28/055/2018 21:55:55 - INFO - Start Flashing
28/055/2018 21:55:55 - INFO - No loader in the bundle. Searching for one
28/055/2018 21:55:55 - INFO - No matching loader found
28/055/2018 21:55:55 - WARN - No loader found or set manually. Skipping loader
28/055/2018 21:55:55 - INFO - Loader : S1_Root_de8d - Version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_117 / Boot version : 1299-4832_S1_Boot_MSM8996_LA2.0_N_117 / Bootloader status : ROOTED
28/055/2018 21:55:55 - INFO - Max packet size set to 4M
28/055/2018 21:55:55 - INFO - USB buffer size set to 512K
28/055/2018 21:55:56 - INFO - Parsing boot delivery
28/055/2018 21:55:56 - INFO - No flash script found.
28/055/2018 21:55:56 - INFO - Flash script is mandatory. Closing session
28/055/2018 21:55:56 - INFO - Ending flash session
28/055/2018 21:55:56 - INFO - Flashing finished.
28/055/2018 21:55:56 - INFO - Please unplug and start your phone
28/055/2018 21:55:56 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
28/056/2018 21:56:00 - INFO - Device disconnected
28/056/2018 21:56:01 - INFO - Device connected in flash mode
What's the problem?
Click to expand...
Click to collapse
you're missing the FSC script. Looks like you made a mistake somewhere when preparing the ftf file to flash.
Please note that this thread is not for flashtool issues, so please check the relevant threads for that.