Related
Windows Edition - v0.9.11.0 - MD5 : A0F880F3CF420A31D86026F49A2013D7
Updated on 12/06/2013 ©2011 by Androxyde
More information at http://androxyde.github.com/
Flashtool Release Notes:
* 0.9.11
This version is a big split with every previous ones.
And not fully featured as previous can be.
I changed the UI framework from Swing to SWT because of a better integration with Mac UI.
Here is what is missing from previous releases :
- No multilingual UI
- No recovery installer
- No kernel installer (for 2010 devices)
- No ROM cleaner.
- Cannot Add/Edit/Remove devices.
No TA hex editor (in pro mode)
Version fully compatible with all 2013 devices (Z/ZL/Tablet Z etc etc)
Unified Bootloader unlock feature with the new BLU icon. No more unlock plugin.
As for flashing, BLU is available even without any connected device, even with
unrecognized devices.
Updated SuperSU package. Added servicemnu root hack
(works with Z/ZL for all FW up to .434)
Known working for Xperia T/V too
Added TA partition backup/restore. Using this feature, you can backup TA before unlock.
Restore TA will relock the devicee and get DRM back as well as BE2
(full complete relock). You cannot count on this feature if ever your device is
already unlocked. Missuse of this feature can brick the device
Introduction to Flashtool:
Flashtool is a flashing software that can be used to :
1. Flash original Images (Android 1.6, 2.1, 2.3 Images)
2. Root your phone
3. Install Recovery, Busybox, custom kernels
4. Clean your Rom (remove /system/apps apps of your choice)
(Be careful, unless you really know what you do, do not modify the default list.
This can make your phone stuck at the SE Logo)
5. Clear dalvik cache
6. Optimize (install of JIT v2)
(Disabled in 0.4, will readd it as a plugin for 2.1 phones only)
7. Customize (installs apps found in the custom/apps folder of the flashtool)
8. Clean uninstalled (remove any references to system apps removed in the
Clean (root needed) step)
9. Edit any text file on the device
10. Rebrand your device
Download Link
MOD EDIT: Not authorized mirror links.
MD
HIT THANKS BUTTON IF IT HELPED
This is not yours, and you are unable to support it. Moving this to General.
I'm pretty sure the devs of flashtool don't want it mirrored.
Sent from my Xperia Tablet Z using xda developers app
Thread Closed
As this is an info post to somebody elses work, the following actions have been taken.
1. Mirror download link removed.
2. Thread is closed as there is no need to post replies.
MD
FEATURED ON THE PORTAL
Thanks @Doug Lynch for the mention!
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
CHANGELOG for 3.0.2-0:
-Fix a bug with the input box that affected masked inputs (passwords). This fixes decrypt of full device encryption on devices that support decrypt. This bug also impacts encrypted backups. Users are highly encouraged to stop using 3.0.1 if you use encrypted backups or if you need decrypt of data in TWRP.
-Add Greek translation to some builds.
CHANGELOG for 3.0.1-0:
-support new CM 13.0 pattern encryption (sultanqasim)
-fix slow flashing issue due to modprobe (present on only some devices) (#twrp)
-libtar updated to latest upstream and fixes (jcadduono)
-fixes for loading custom themes (_that)
-TWRP will now detect and install TWRP themes automatically through the normal zip install process (Dees_Troy)
-translation updates - added Italian, Czech and Polish and significant updates to Dutch
-progress bar improvements - progress bar updates during image flashing and better tracks progress during file system backups (tar) (Dees_Troy)
-fix input box text display (Dees_Troy)
-reboot option after zip install complete (bigbiff)
-other mostly invisible bug fixes and improvements
CHANGELOG for 3.0.0-0:
-Completely new theme - Much more modern and much nicer looking (by z31s1g)
-True Terminal Emulator - Includes arrow keys, tab and tab completion, etc. (by _that)
-Language translation - It won’t be perfect and especially some languages that require large font files like Chinese & Japanese won’t be availble on most devices. Also some languages may only be partially translated at this time. Feel free to submit more translations to OmniROM’s Gerrit. (mostly by Dees_Troy)
-Flashing of sparse images - On select devices you will be able to flash some parts of factory images via the TWRP GUI (by HashBang173)
-Adopted storage support for select devices - TWRP can now decrypt adopted storage partitions from Marshmallow
-Reworked graphics to bring us more up to date with AOSP - includes support for adf and drm graphics (by Dees_Troy)
-SuperSU prompt will no longer display if a Marshmallow ROM is installed
-Update exfat, exfat fuse, dosfstools (by mdmower)
-Update AOSP base to 6.0
-A huge laundry list of other minor fixes and tweaks
WARNING: This is our first release in a long time. We have a lot of new and somewhat aggressive changes in this new release. The changes to the graphics back-end may cause some devices to not boot up properly or have other display-related issues. If you are not in a position to reflash an older build of TWRP, then wait until you are or at least wait until others have tried the new version for your specific device. You don’t want to end up with a non-working recovery and have to wait several hours or days to get to a computer to be able to fix it.
Notes for themers: In addition to the udpated theme, we have introduced a theme version variable to the TWRP theme system. If the theme version does not match the version that TWRP expects, TWRP will reject the custom theme and load its stock theme. This change will ensure that people who update TWRP without updating their theme will still have a workable recovery. We have removed libjpeg support. The stock theme was only using a jpeg image for the splash / curtain. This change means that any custom themes will no longer be able to use jpeg images. It also means that tools used to repack recovery images with a different curtain / splash will need to be updated to use the new method.
Version number notes: For a while we’ve been using a 4 digit version number and reserved the 4th digit for device-specific updates. For instance, we find and fix a device-specific issue like decryption of data on Nexus 5, we would release that as a 2.8.7.1. After a while, some people would start asking where 2.8.7.1 was for other devices. So, going forward we have decided to change the numbering scheme to 3.0.0-2, etc. Our hope is that this version numbering scheme will more clearly identify that the 4th digit does not indicate a version change for the code base.
We need your help! The bulk of TWRP work is done by 3 people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
CHANGELOG for 2.8.7.0:
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
DOWNLOAD:
Most devices can be updated quickly and easily within TWRP if you already have version 2.8.4.0 or higher installed
1) Download the latest version from our website on your device
2) Reboot to TWRP
3) Hit Install and tap the "Images..." button in the lower right
4) Browse to the location of the TWRP image on your device and select it
5) Select recovery from the partition list and swipe to flash
OR:
You can find more information and download links on our website.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
TWRP 3.0.2-0 for LAVA Pixelv1, Tool/Utility for the OEM Cross Device Development
Contributors
MSF Jarvis, varun.chitre15
Version Information
Status: Stable
Created 2016-04-06
Last Updated 2016-04-20
Reserved
Credits
varun.chitre15 for his base trees
@DHARMESH17 for being a great tester
@arvinquilao for making me jealous!
Reserved
I would like you to recognize some misunderstanding.
On the official website of TWRP are 2 different Android One devices listed.
The first is "sprout" which stand for MTK powered devices
The other entry is called "2nd generation MTK (seedmtk)" which is simply wrong and might mislead some people. 2nd gen devices are powered by Snapdragon 410 CPUs.
You may want to change the listing on your website for a better understanding.
body150165 said:
I would like you to recognize some misunderstanding.
On the official website of TWRP are 2 different Android One devices listed.
The first is "sprout" which stand for MTK powered devices
The other entry is called "2nd generation MTK (seedmtk)" which is simply wrong and might mislead some people. 2nd gen devices are powered by Snapdragon 410 CPUs.
You may want to change the listing on your website for a better understanding.
Click to expand...
Click to collapse
@body150165, you might wanna do some homework now. Second gen devices are victim of fragmentation, causing two different variants to exist. The first, the Snapdragon 410-powered seed devices, have TWRP from @arvinquilao, and he's also running CM13 builds. The second one, the MT6582-powered Infinix Hot One and Lava Pixel v1, are classified as sprout by their manufacturers, which would have caused the confusion it somehow triggered in you. All said and done, as the only developer actively working towards CM13 and TWRP for the device, I took the liberty of renaming the device.
@body150165 thanks for bringing up your concern. Official TWRP build for the Snapdragon variant is already available via dl.twrp.me/seed, but the website is yet to be updated (probably in the next couple of days). As soon as it's updated I'll make a new thread here for the Snapdragon variant.
Second Partitiin (SD partition) working??
Sent from my SM-J500F using XDA-Developers mobile app
Nur_Alom said:
Second Partitiin (SD partition) working??
Sent from my SM-J500F using XDA-Developers mobile app
Click to expand...
Click to collapse
Who needs it?
I ported this TWRP 3.0.0-2 for my smartphone (Ulefone Paris, MTK6753), but I have 2 problems....I wrote here, because I want know if is a porting bug or also in others terminal there are the same bug:
1) I created in past a backup of my rom with TWRP 2.8.7.0 Version, and the 3.0.0-2 version isn't able to see my backup when I go on "restore" and choose my MicroSD, but if I navigate with file explorer, I can find it.
2) Battery bug: Always show me 50% of charge, no more, no less...
Are this common bugs, or porting bugs??? How can I fix it??
Thanks!!!
cuvetto said:
I ported this TWRP 3.0.0-2 for my smartphone (Ulefone Paris, MTK6753), but I have 2 problems....I wrote here, because I want know if is a porting bug or also in others terminal there are the same bug:
1) I created in past a backup of my rom with TWRP 2.8.7.0 Version, and the 3.0.0-2 version isn't able to see my backup when I go on "restore" and choose my MicroSD, but if I navigate with file explorer, I can find it.
2) Battery bug: Always show me 50% of charge, no more, no less...
Are this common bugs, or porting bugs??? How can I fix it??
Thanks!!!
Click to expand...
Click to collapse
I'll get back to you in a while after checking these. And this is TWRP 3.0.2-0, not 3.0.0-2.
I would like to know what steps have you taken to port it to determine whether I can source build for the device and make it official.
cuvetto said:
I ported this TWRP 3.0.0-2 for my smartphone (Ulefone Paris, MTK6753), but I have 2 problems....I wrote here, because I want know if is a porting bug or also in others terminal there are the same bug:
1) I created in past a backup of my rom with TWRP 2.8.7.0 Version, and the 3.0.0-2 version isn't able to see my backup when I go on "restore" and choose my MicroSD, but if I navigate with file explorer, I can find it.
2) Battery bug: Always show me 50% of charge, no more, no less...
Are this common bugs, or porting bugs??? How can I fix it??
Thanks!!!
Click to expand...
Click to collapse
@cuvetto : No, these bugs don't exist in my build. Tested as working fine by @DHARMESH17.
Will these work on 1st generation android one device i mean sprout 4 ?
DarkHeart Z said:
Will these work on 1st generation android one device i mean sprout 4 ?
Click to expand...
Click to collapse
It will not, sadly. TWRP seems to have not updated sprout devices for ages, so I'll run you guys a 3.0.2-0 build in some time and post it here.
MSF Jarvis said:
It will not, sadly. TWRP seems to have not updated sprout devices for ages, so I'll run you guys a 3.0.2-0 build in some time and post it here.
Click to expand...
Click to collapse
Then I am waiting for that
Bootloop
My device is lava pixel v1. After flashing this recovery from fastboot my device goes into bootloop. It always start with recovery and then says failed to mount /data etc and again reboots.
ashokvishnoi1994 said:
My device is lava pixel v1. After flashing this recovery from fastboot my device goes into bootloop. It always start with recovery and then says failed to mount /data etc and again reboots.
Click to expand...
Click to collapse
After fastboot flash recovery twrp-3.0.2-0-seedmtk.img, what exactly did you do?
You need to press both Volume Up + Power for about 15 seconds till device reboots back into bootloader mode and then go to recovery mode and open it. This has been tested as working. What steps did you take?
MSF Jarvis said:
@body150165, you might wanna do some homework now. Second gen devices are victim of fragmentation, causing two different variants to exist. The first, the Snapdragon 410-powered seed devices, have TWRP from @arvinquilao, and he's also running CM13 builds. The second one, the MT6582-powered Infinix Hot One and Lava Pixel v1, are classified as sprout by their manufacturers, which would have caused the confusion it somehow triggered in you. All said and done, as the only developer actively working towards CM13 and TWRP for the device, I took the liberty of renaming the device.
Click to expand...
Click to collapse
It should be Infinix Hot 2. Also I tried flashing via flashify and the recovery does not boot on Hot 2.
anarchtic said:
It should be Infinix Hot 2. Also I tried flashing via flashify and the recovery does not boot on Hot 2.
Click to expand...
Click to collapse
That's bad.... Can you provide me with your boot image? I will have to end up deunifying this recovery if it isn't booting :/
I would recommend that you also try a fastboot flash to see if it's a flashify thing.
MSF Jarvis said:
@body150165, you might wanna do some homework now. Second gen devices are victim of fragmentation, causing two different variants to exist. The first, the Snapdragon 410-powered seed devices, have TWRP from @arvinquilao, and he's also running CM13 builds. The second one, the MT6582-powered Infinix Hot One and Lava Pixel v1, are classified as sprout by their manufacturers, which would have caused the confusion it somehow triggered in you. All said and done, as the only developer actively working towards CM13 and TWRP for the device, I took the liberty of renaming the device.
Click to expand...
Click to collapse
MSF Jarvis said:
That's bad.... Can you provide me with your boot image? I will have to end up deunifying this recovery if it isn't booting :/
I would recommend that you also try a fastboot flash to see if it's a flashify thing.
Click to expand...
Click to collapse
I will when I get home, I am at work now which is why I used Flashify. Did you test using Hot 2?
anarchtic said:
I will when I get home, I am at work now which is why I used Flashify. Did you test using Hot 2?
Click to expand...
Click to collapse
Don't own one. I believed it would boot, just like it does for Android One first gen devices(One recovery for all devices)
{
"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"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About the project
Boot Bridge for Sony ELF is born out of an idea to create support
of systemless tools like SuperSU on the Sony ELF bootimages.
The structure being different from regular Android boot partitions,
these tools never worked to edit the content of the boot image
present on devices like the Xperia SP, T, TX, V, ...
Boot Bridge for Sony ELF allows you to choose the systemless zip
by simply replacing the file install/install.zip with the one to flash.
Warning: BootBridge for Sony ELF is meant to be used on custom ROMs.
For stock ROMs, you'd need to patch the ROM (bootimage securities) first.
Please refer to the currently supported devices list in the second post.
When you flash the Boot Bridge zip, a fake regular bootimage is created
with the contents of the original ELF partition, mapped in the fstab,
then the install.zip is automatically flashed as if you did yourself,
and finally the ELF partition is updated accordingly.
Boot Bridge for Sony ELF also supports being used with MultiROM secondary ROMs.
The project is an extension of the libbootimg originally created by Tasssadar,
that I then reworked to add Sony ELF boot support for Xperia MultiROM.
Downloads (Unlocked Bootloader only)
BootBridge-SonyELF.zip : https://github.com/AdrianDC/android_boot_bridge/blob/master/release/BootBridge-SonyELF.zip
Preview of the installation
OPTION 1) Root with Magisk by topjohnwu
Magisk (Latest version) : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Rename the downloaded zip to install.zip
Open the Boot Bridge zip with a zip manager
Replace the file install/install.zip with the new one
Flash the new Boot Bridge zip in the TWRP recovery
Reboot to Android
OPTION 2) Root with SuperSU by Chainfire
In order to get root access on AOSP based ROMs (2.78 SR5 or newer for 7.1.x),
you need to download the SuperSU project by Chainfire.
SuperSU zip (Latest version) : http://forum.xda-developers.com/apps/supersu
Rename the downloaded zip to install.zip
Open the Boot Bridge zip with a zip manager
Replace the file install/install.zip with the new one
Flash the new Boot Bridge zip in the TWRP recovery
Reboot to Android
OPTION 3) Root with phhSuperUser by phhusson
In order to get root access on AOSP based ROMs (7.1.1 included),
you need to download the phhSuperUser project by phhusson.
superuser.zip : http://forum.xda-developers.com/android/software-hacking/wip-selinux-capable-superuser-t3216394
Rename the downloaded zip to install.zip
Open the Boot Bridge zip with a zip manager
Replace the file install/install.zip with the new one
Flash the new Boot Bridge zip in the TWRP recovery
Reboot to Android
Install the phh's SuperUser application
Source code
Project sources - https://github.com/AdrianDC/android_boot_bridge (branch master)
libbootimg sources - https://github.com/AdrianDC/multirom_libbootimg (branch master)
MultiROM sources - https://github.com/AdrianDC/multirom_core (branch master)
Boot Bridge for Sony ELF created also thanks to :
- Tasssadar for the original libbootimg / MultiROM sources
- The XperiaMultiROM team for our evolution of MultiROM
- Chainfire for the flashable OUTFD export and boot detection
- Everyone involved in testing it
XDA:DevDB Information
Android Boot Bridge for Sony ELF, Tool/Utility for the OEM Cross Device Development
Contributors
Adrian DC
Version Information
Status: No Longer Updated
Created 2016-11-25
Last Updated 2020-08-29
Reserved
Changelog
Code:
Boot Bridge for Sony ELF - 26/12/2018
======================================
* Resolve compatibility with Magisk v17+ due to an
internal evolution of its boot partitions detection
Boot Bridge for Sony ELF - 28/05/2017
======================================
* Use android_boot as potential bridge to fix SuperSU
Boot Bridge for Sony ELF - 20/12/2016
======================================
* Fix the 32/64 bits dual support
Boot Bridge for Sony ELF - 18/12/2016
======================================
* Added support for Sony Stock ELF (64 bits) bootimages
* libbootimg changes from my recent updates
Boot Bridge for Sony ELF - 29/11/2016
======================================
* Fix the boot partition detection with symlinks
* Restore phhSuperuser support
Boot Bridge for Sony ELF - 27/11/2016
======================================
* Add support for newer Sony ELF partitions
* Allows to root Stock Sony ROMs on the Xperia Z2
* Updated in collaboration with Alexander Diewald
Boot Bridge for Sony ELF - 25/11/2016
======================================
* Initial public release on XDA
Devices supported
Code:
Sony Xperia SP (Huashan): Magisk, SuperSU, phhSuperSU
Sony Xperia T/TX/V (Mint, Hayabusa, Tsubasa): Magisk, SuperSU, phhSuperSU
Sony Xperia Z2 (Sirius): SuperSU on Stock ROMs
Sony Xperia X Performance (Dora): Stock ROM patching
...
It's great news! thanks a lot, will try it soon. :fingers-crossed:
hi @Adrian DC,
Thanks for your mail that pointing me on this thread.
As you now I'm maintaining a ROM for Xperia S and your project can be a good fit for it
For now I have a built-in support of root but no solution for those who wants SuperSU.
I'm generating the boot.img for Xperia S with the commandline :
python $(MKELF) -o [email protected] $(PRODUCT_OUT)/[email protected]$(BOARD_KERNEL_ADDR) $(PRODUCT_OUT)/[email protected]$(BOARD_RAMDISK_ADDR),ramdisk $(RPMBIN)@$(BOARD_RPM_ADDR),rpm
With parameters below :
# boot image
BOARD_KERNEL_ADDR := 0x40208000
BOARD_RAMDISK_ADDR := 0x41500000
BOARD_RPM_ADDR := 0x20000
Is your project compatible with the way I'm generating boot.img for Xperia S ?
If yes, I will test it with SuperSU (sepolicy for SuperSU systemless is already supported on the ROM).
Thanks for your feedback and work on that topic
mickybart said:
Thanks for your mail that pointing me on this thread.
Click to expand...
Click to collapse
No problem.
Normally the full port of Sony ELF partitions I made inside libbootimg for MultiROM
is compatible with all bootimages structures from these series of Sony devices.
I invite you to have your ROM's boot.img flashed into boot directly,
then flash my Boot Bridge as it is, even without a rooting zip, like in my screenshot,
and let it run to see the bridge creation then restore perform.
If anything goes wrong and the bootimage is not readable,
the process will stop and nothing will be done.
In the very worst case, the rebuilt boot image doesn't start
and you simply fastboot the image you came from.
Also recently I worked with Diewi (Alexander) to extend ELF support
to the newer version of Sony's last ELF devices, the 8974 (Z2) boot
that had ELF Stock images but also support for Android normal ones.
Once fully tested and confirmed, the update will be done on this project too.
On a side note, about root, SuperSU works fine on my devices on 6.0 & less,
for 7.1 the installation is fine too but the root features failed (with sepolicies totally fixed),
this is apparently common / randomly affecting some devices,
Chainfire is aware of it, so do not be surprised if that happens on yours,
and give phhSuperUser a go too as it is the fully working method on my AOSP 7.1 now.
Bye !
Amazing! Worked like a charm..no issues at all..thanks a [email protected] Adrian DC
Boot Bridge updated to support newer Sony ELF devices,
including the Stock Sony ROMs, allowing an easy SuperSU root process.
Hi Adrian, Sorry if is a noob question but im facing ERROR: 7 after instaling the BootBridge-SonyELF.zip, i've already replace the install.zip, it says in TWRP ------> Found bootimg @ /dev/block/platform/msm_sdcc.1/by-name/kernel ----> assert failed: run_program(''/tmp/boot_bridge/flash_zip.sh'', ''/tmp/boot_ brdge'', ''install.zip'') == 0 .... what i'm doing wrong? .. Im on AOSP 25/11 . Thanks for your time
Miggystar said:
Hi Adrian, Sorry if is a noob question but im facing ERROR: 7 after instaling the BootBridge-SonyELF.zip, i've already replace the install.zip, it says in TWRP ------> Found bootimg @ /dev/block/platform/msm_sdcc.1/by-name/kernel ----> assert failed: run_program(''/tmp/boot_bridge/flash_zip.sh'', ''/tmp/boot_ brdge'', ''install.zip'') == 0 .... what i'm doing wrong? .. Im on AOSP 25/11 . Thanks for your time
Click to expand...
Click to collapse
I've got the same error, did everything exactly according to instructions.
Where could the error be?
MichaBit said:
I've got the same error, did everything exactly according to instructions.
Where could the error be?
Click to expand...
Click to collapse
Thanks for reporting the issue.
It was introduced with the new update to support Z2 devices, and affected only phhSuperuser.
The issue is now fully fixed, please download the new version and try again.
Adrian DC said:
Thanks for reporting the issue.
It was introduced with the new update to support Z2 devices, and affected only phhSuperuser.
The issue is now fully fixed, please download the new version and try again.
Click to expand...
Click to collapse
Installation completed!
#root successfully :good:
Many thanks and greetings Adrian :highfive:
does it work with locked bootloader?
I have Xperia Z2 MM deodexed rooted with xposed
a.hamameh96 said:
does it work with locked bootloader?
I have Xperia Z2 MM deodexed rooted with xposed
Click to expand...
Click to collapse
This mod intervenes in boot image (kernel) so most probably it wont work. But I am not 100% sure
MichaBit said:
Installation completed!
#root successfully :good:
Many thanks and greetings Adrian :highfive:
Click to expand...
Click to collapse
Work for lbl???
vandiaz_sairavinz said:
Work for lbl???
Click to expand...
Click to collapse
dont try on lbl it will brick ur phone
nhicko95 said:
dont try on lbl it will brick ur phone
Click to expand...
Click to collapse
Ok, thank you
This is happening to me when I move App to system in link2Sd...
Greetings Adrian,
So nice that you still support our old Sony devices, particularly Xperia V. :good:
The thing is I used your Elf Bridge and succeeded to install Magisk 11.6. But then a new version of it came, 12.0. And I did all the same way as with 11.6 but failed. It was written that the boot image was so small. However, I flashed Magisk 12.0 with no Elf Bridge. And the weird thing that that time there was enough space. I knew that flashing without the Bridge would cause soft-brick, but I knew what to do next in that case, I flashed the proper boot image after all and the device started working again.
The question is following: is it possible to flash Magisk 12.0? I also forget to tell that the size of these two versions are almost similar. The log is attached here.
Thanks!
magisk 11.6 and above have elf support
Speed of a Puma, Brain of a Chicken
myxomop25 said:
Greetings Adrian,
So nice that you still support our old Sony devices, particularly Xperia V. :good:
The thing is I used your Elf Bridge and succeeded to install Magisk 11.6. But then a new version of it came, 12.0. And I did all the same way as with 11.6 but failed. It was written that the boot image was so small. However, I flashed Magisk 12.0 with no Elf Bridge. And the weird thing that that time there was enough space. I knew that flashing without the Bridge would cause soft-brick, but I knew what to do next in that case, I flashed the proper boot image after all and the device started working again.
The question is following: is it possible to flash Magisk 12.0? I also forget to tell that the size of these two versions are almost similar. The log is attached here.
Thanks!
Click to expand...
Click to collapse
Thanks.
Yes I got reports on that, but I think the faulty half-ELF support causes the issues you are having.
Better stick to the working version for the time being.
flipside101 said:
magisk 11.6 and above have elf support
Click to expand...
Click to collapse
Not really, it's faulty and breaks ELF bootimages (tunrs them back to regular bootimages,
which is where BootBridge plays a role to have proper read and write of the ELF bootimages
structures (32bits 8960 or newer 64 bits like 8996 Stock) without ELF support in the tools.
THIS IS JUST SHARE HOW I SUCCESS BRING BACK MY SONY APPS WORK LIKE A CHARM, DRM REALY FIXED
I realize that since Oreo, when I flash drmfix.zip shared in this forum I dont realy get drm fixed, just get camera working, not for other apps like X-Reality, Super-vivid and Sony Services (for loging in Xperia Longe) and mybe other related with sony feature.
After some research, evidently Oreo move some files from boot.img to system partition, this files in important for patching so that drm fix work. I followed tutorial in Xperia Z5 thread and get an idea for try to aplicated for XZs and its work like a charm.
I don't own anything for this tool so you can just go to this thread and follow every single instruction in there.
What I get after followed that method :
- dm-verity (disabled) > now I can do debloat system apps
- Sony RIC (disabled) > as above function
- force-encrypt (disabled) > /data fully decrypted, no red message anymore in TWRP
- DRM Loader Patched to boot.img > Flashing drmfix.zip now will bring back Sony Apps Feature (X-Reality, Vivid Mode, Xperia Account Services)
Credit goes for him : serajr
But if you are helped by this information then don't hesitate to click thanks button...
THIS METHOD SHOULD WORK ON LATEST OFFICIAL STOCK ROM [ G823X_41.3.A.2.234 ], AND MAYBE WORK ON NEXT UPDATE
Last thing.... DO WITH YOUR OWN RISK
Screen mirroring not working on xperia xzs
XtremE16 said:
Screen mirroring not working on xperia xzs
Click to expand...
Click to collapse
Never do mirroring cause I dont have devices to cast my XZs, so I have no idea abut that.
I'm having some trouble with the modem (and LTE compatability) on my XZ1 Compact, and I was wondering if anyone has experience with the different kinds of boot modes and/or Qualcomm transfers.
There's some Qualcomm software (QPST) that supposed to let you write to the modem partition. There are some instructions here
Modify Sony XZ, XZs, XZ Premium, XZ1 and XZ2 LTE-A band combos - MT-TECH.FI
On this instruction we will modify on Sony smartphone band combo profiles with Qualcomm software. Sony smartphones have software limitation and we will unlock this. We have tables of supported CA combos per group: Sony XZ(s) Sony XZ Premium Sony XZ1 & XZ1 Compact Sony XZ2 & XZ2 Compact We will...
mt-tech.fi
and here
Getting VoLTE and VoWiFi on unlisted carriers by flashing mbn file
I live in Canada and I have a BC72 (Asian version). I am struggling to get VoLTE and VoWiFi working. I know that mbn file is the key to getting IMS support and sony seems to block some carrier mbn files (only mbn in sales areas are available). So...
forum.xda-developers.com
That I was trying to follow along with, but doing the setopt doesn't seem to change the mode of my phone/usb connections, and so I can't update the drivers or connect the QPST software to read or write the filres.
There's also supposedly an EDL mode that Qualcomm phones can get into, which should also connect to the software
What is EDL Mode and How to Boot your Qualcomm Android Device into it
Android phones and tablets equipped with Qualcomm chipset contain a special boot mode which could be used force-flash firmware files for the purpose of unbricking or restoring the stock ROM.
www.thecustomdroid.com
but those instructions don't work either - adb reboot edl just reboots the phone back into the rom, and fastboot oem edl tells me that's not a supported function.
Does anyone have experience getting either of these to work and/or updating the modem software?
I can't follow these steps:
XZ1 Compact - MetroPCS VoLTE + Latest Pie + Fingerprint + Wi-Fi Calling Step by Step Guide
Overview: This guide provides step-by-step instructions for flashing any existing Sony stock rom Android 8 or 9 to the latest Sony stock ROM Android 9 Build v47.2.A.11.228 for use on the MetroPCS network. The finalized flash is a hybrid of Sony...
forum.xda-developers.com
since I don't seem to have this overlay functionality baked into my rom.
I recognize that part of this might be something to do with my ROM - which I believe is AOSP based instead of stock based - but even in the worst cast scenario it seems like I should be able to override whichever default mbn file the phone is deciding to use (perhaps set from a partition flash?) with whichever one I'd like it to use, instead. I just can't figure out how to determine what my phone is currently picking, or how to correct it.
Any tips or suggestions would be greatly appreciated. Thanks!
I'm having some trouble with the modem (and LTE compatability) on my XZ1 Compact, and was trying to experiment with adjusting the files manually.
Does anyone have experience with the different kinds of boot modes and/or Qualcomm transfer?
I've tried on both an XZ1c and a Z5c, both of which result in similar behaviors.
Extra context:
There's some Qualcomm software (QPST) that supposed to let you write to the modem partition. There are some instructions here
Modify Sony XZ, XZs, XZ Premium, XZ1 and XZ2 LTE-A band combos - MT-TECH.FI
On this instruction we will modify on Sony smartphone band combo profiles with Qualcomm software. Sony smartphones have software limitation and we will unlock this. We have tables of supported CA combos per group: Sony XZ(s) Sony XZ Premium Sony XZ1 & XZ1 Compact Sony XZ2 & XZ2 Compact We will...
mt-tech.fi
and here
Getting VoLTE and VoWiFi on unlisted carriers by flashing mbn file
I live in Canada and I have a BC72 (Asian version). I am struggling to get VoLTE and VoWiFi working. I know that mbn file is the key to getting IMS support and sony seems to block some carrier mbn files (only mbn in sales areas are available). So...
forum.xda-developers.com
That I was trying to follow along with, but doing the setopt doesn't seem to change the mode of my phone/usb connections, and so I can't update the drivers or connect the QPST software to read or write the filres.
There's also supposedly an EDL mode that Qualcomm phones can get into, which should also connect to the software
What is EDL Mode and How to Boot your Qualcomm Android Device into it
Android phones and tablets equipped with Qualcomm chipset contain a special boot mode which could be used force-flash firmware files for the purpose of unbricking or restoring the stock ROM.
www.thecustomdroid.com
but those instructions don't work either - adb reboot edl just reboots the phone back into the rom, and fastboot oem edl tells me that's not a supported function.
Does anyone have experience getting either of these to work and/or updating the modem software?
I figured I'd try asking in the cross-device forum since most of the Sony phones use a Qualcomm modem, so it seems like it should be applicable to more than just one model.
Any tips or suggestions would be greatly appreciated. If I get it working, I'll happily follow up with a guide for others.
Unfortunately, SONY seems to have banned edl from the factory. Unless your phone is an engineering sample.
laojiefang said:
Unfortunately, SONY seems to have banned edl from the factory. Unless your phone is an engineering sample.
Click to expand...
Click to collapse
NO, My xperia xz2 detect as edl mode
{
"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"
}
cuynu said:
NO, My xperia xz2 detect as edl mode
View attachment 5774603
Click to expand...
Click to collapse
Can you use the public version of elf files to read your phone partition? Like this?
laojiefang said:
Can you use the public version of elf files to read your phone partition? Like this?View attachment 5774611
Click to expand...
Click to collapse
No, qfil say timeout error
cuynu said:
No, qfil say timeout error
Click to expand...
Click to collapse
First of all, according to your screenshot, you don't seem to have the edl driver installed. Second, your xz2 is a retail phone, which cannot use edl mode for all operations.
Sorry for the delay; it's been a weird week.
laojiefang said:
Unfortunately, SONY seems to have banned edl from the factory. Unless your phone is an engineering sample.
Click to expand...
Click to collapse
Interesting, thanks for this info! It at least explains why I was unable to get into it, despite the Qualcomm modem.
Do you have any experience with the "setprop persist.usb.eng 1" setting, and what it's doing?
As far as I can tell that's sometimes doing triggering a similar mode for folks, with some ROMs, but I don't understand it enough to grok why it's not doing the same for my device, and if it's even possible to get it working or if I need to switch to a completely different ROM.
It seems like the modem configuration should be independent of the ROM, but I have a sneaky suspicion that backing up, switching/re-configuring, then restoring my current one won't end up with it working any better.
laojiefang said:
a retail phone, which cannot use edl mode for all operations.
Click to expand...
Click to collapse
Do you know anything about which operations are or aren't possible? The Xperia 1 III post suggests that some of them are possible - at least to download and upload files, which is hopefully enough here to tweak my settings so I'd have better LTE/VoIP compatibility.
Thanks again for your insight!
tonsofquestions said:
Sorry for the delay; it's been a weird week.
Interesting, thanks for this info! It at least explains why I was unable to get into it, despite the Qualcomm modem.
Do you have any experience with the "setprop persist.usb.eng 1" setting, and what it's doing?
As far as I can tell that's sometimes doing triggering a similar mode for folks, with some ROMs, but I don't understand it enough to grok why it's not doing the same for my device, and if it's even possible to get it working or if I need to switch to a completely different ROM.
It seems like the modem configuration should be independent of the ROM, but I have a sneaky suspicion that backing up, switching/re-configuring, then restoring my current one won't end up with it working any better.
Do you know anything about which operations are or aren't possible? The Xperia 1 III post suggests that some of them are possible - at least to download and upload files, which is hopefully enough here to tweak my settings so I'd have better LTE/VoIP compatibility.
Thanks again for your insight!
Click to expand...
Click to collapse
Do you mean that you can use certain ROMs to trigger edl mode? (I'm sorry that I'm Chinese, and I can't understand your words with machine translation.)
I don't know if it's the same as EDL mode, but it seems like certain ROMs (likely stock at least) can get into some kind of Qualcomm mode by following the instructions outlined here:
Modify Sony XZ, XZs, XZ Premium, XZ1 and XZ2 LTE-A band combos - MT-TECH.FI
On this instruction we will modify on Sony smartphone band combo profiles with Qualcomm software. Sony smartphones have software limitation and we will unlock this. We have tables of supported CA combos per group: Sony XZ(s) Sony XZ Premium Sony XZ1 & XZ1 Compact Sony XZ2 & XZ2 Compact We will...
mt-tech.fi
Otherwise, the instructions probably wouldn't exist.
I just can't get it to work on _my_ ROM.
Happy to try and rephrase if you can point out what wasn't clear in the translation!
tonsofquestions said:
I don't know if it's the same as EDL mode, but it seems like certain ROMs (likely stock at least) can get into some kind of Qualcomm mode by following the instructions outlined here:
Modify Sony XZ, XZs, XZ Premium, XZ1 and XZ2 LTE-A band combos - MT-TECH.FI
On this instruction we will modify on Sony smartphone band combo profiles with Qualcomm software. Sony smartphones have software limitation and we will unlock this. We have tables of supported CA combos per group: Sony XZ(s) Sony XZ Premium Sony XZ1 & XZ1 Compact Sony XZ2 & XZ2 Compact We will...
mt-tech.fi
Otherwise, the instructions probably wouldn't exist.
I just can't get it to work on _my_ ROM.
Happy to try and rephrase if you can point out what wasn't clear in the translation!
Click to expand...
Click to collapse
Oh I see, this mode is not edl mode, it is Qualcomm diag port, it is used to modify the xml configuration file of the phone to remove some software level band restrictions. For example, in mainland China where I live, LG mobile phones cannot use 5G. By this method, you can use 5G in mainland China by brushing the xml file of the Chinese version of LG mobile phones
OK, that makes sense.
In my research to be able to do this, I saw mentions of both the diag and edl modes, but nothing highlighted the distinctions, so I thought they were different names for the same thing.
So if edl mode is disabled by Sony for these devices, perhaps the correct question to ask is "how can I enable this diag mode/port", if this command is not available? Is it part of the ROM, or available in some other way?
For that matter, if it's a software level-band restriction, is that software itself in the ROM or the modem files? Do changes persist across ROMs?
For example, if you fix the 5G settings in one setup, then switch to a different OS build/version, will you still be able to use 5G, or would you have to reconfigure again?
tonsofquestions said:
OK, that makes sense.
In my research to be able to do this, I saw mentions of both the diag and edl modes, but nothing highlighted the distinctions, so I thought they were different names for the same thing.
So if edl mode is disabled by Sony for these devices, perhaps the correct question to ask is "how can I enable this diag mode/port", if this command is not available? Is it part of the ROM, or available in some other way?
For that matter, if it's a software level-band restriction, is that software itself in the ROM or the modem files? Do changes persist across ROMs?
For example, if you fix the 5G settings in one setup, then switch to a different OS build/version, will you still be able to use 5G, or would you have to reconfigure again?
Click to expand...
Click to collapse
edl mode is disabled at the factory. diag port is not disabled. I have never seen a phone with diag mode disabled.
LG mobile phones need to be re-cracked after changing the SIM card in mainland China, because the carrier_policy.xml file will change with the change of the SIM card, but after the cracking is completed when the SIM card is inserted, the third-party ROM such as MIUI does not need to be re-cracked. However, after replacing the SIM card, it cannot be cracked through the diag port again, unless the original firmware is flashed back. Sony I'm not sure if that's the case.
If you want to enable diag on a phone that is disabled by default, you must root the phone and then open it using adb shell command in the Android debug bridge (like the link you sent me).
tonsofquestions said:
Sorry for the delay; it's been a weird week.
Interesting, thanks for this info! It at least explains why I was unable to get into it, despite the Qualcomm modem.
Do you have any experience with the "setprop persist.usb.eng 1" setting, and what it's doing?
As far as I can tell that's sometimes doing triggering a similar mode for folks, with some ROMs, but I don't understand it enough to grok why it's not doing the same for my device, and if it's even possible to get it working or if I need to switch to a completely different ROM.
It seems like the modem configuration should be independent of the ROM, but I have a sneaky suspicion that backing up, switching/re-configuring, then restoring my current one won't end up with it working any better.
Do you know anything about which operations are or aren't possible? The Xperia 1 III post suggests that some of them are possible - at least to download and upload files, which is hopefully enough here to tweak my settings so I'd have better LTE/VoIP compatibility.
Thanks again for your insight!
Click to expand...
Click to collapse
here is my post with info about persist.usb.eng:
[DEVONLY] LineageOS 16
This is the development thread for Lineage 16. Everyone who knows C, Java and strace is welcome to participate. Please send git formatted patches! Device Trees https://github.com/cryptomilk/android_kernel_sony_msm8998...
forum.xda-developers.com
[DEVONLY] LineageOS 16
This is the development thread for Lineage 16. Everyone who knows C, Java and strace is welcome to participate. Please send git formatted patches! Device Trees https://github.com/cryptomilk/android_kernel_sony_msm8998...
forum.xda-developers.com
and this one in particular:
[DEVONLY] LineageOS 16
This is the development thread for Lineage 16. Everyone who knows C, Java and strace is welcome to participate. Please send git formatted patches! Device Trees https://github.com/cryptomilk/android_kernel_sony_msm8998...
forum.xda-developers.com
concerning EDL mode (as discussed a different thing to diag mode) - you can boot into EDL with retail xz1c using a kernel patch which re-adds support for 'adb reboot edl', but it is not useful, because it needs sony signed EDL image that is loaded via usb (I happen to have it, but all interesting commands are protected by sony authentication, so it is not useful anyway)
laojiefang said:
LG mobile phones need to be re-cracked after changing the SIM card in mainland China, because the carrier_policy.xml file will change with the change of the SIM card, but after the cracking is completed when the SIM card is inserted, the third-party ROM such as MIUI does not need to be re-cracked. However, after replacing the SIM card, it cannot be cracked through the diag port again, unless the original firmware is flashed back. Sony I'm not sure if that's the case.
If you want to enable diag on a phone that is disabled by default, you must root the phone and then open it using adb shell command in the Android debug bridge (like the link you sent me).
Click to expand...
Click to collapse
Yes, the phone is rooted (thus the custom ROM, though I guess you could unlock and not root, but that just seems silly).
Thanks for the context on changing the SIM card, perhaps that's my underlying issue, and I'll just have to bite the bullet and go back to the original firmware.
j4nn said:
here is my post with info about persist.usb.eng:
[DEVONLY] LineageOS 16
This is the development thread for Lineage 16. Everyone who knows C, Java and strace is welcome to participate. Please send git formatted patches! Device Trees https://github.com/cryptomilk/android_kernel_sony_msm8998...
forum.xda-developers.com
[DEVONLY] LineageOS 16
This is the development thread for Lineage 16. Everyone who knows C, Java and strace is welcome to participate. Please send git formatted patches! Device Trees https://github.com/cryptomilk/android_kernel_sony_msm8998...
forum.xda-developers.com
and this one in particular:
[DEVONLY] LineageOS 16
This is the development thread for Lineage 16. Everyone who knows C, Java and strace is welcome to participate. Please send git formatted patches! Device Trees https://github.com/cryptomilk/android_kernel_sony_msm8998...
forum.xda-developers.com
concerning EDL mode (as discussed a different thing to diag mode) - you can boot into EDL with retail xz1c using a kernel patch which re-adds support for 'adb reboot edl', but it is not useful, because it needs sony signed EDL image that is loaded via usb (I happen to have it, but all interesting commands are protected by sony authentication, so it is not useful anyway)
Click to expand...
Click to collapse
Ah, this is super interesting info, thank you j4nn! I am on Oreo, so maybe it's just as easy as setting a few of the extra props. I'll read through the read more later this evening.
Very neat about being able to custom-patch in the EDL reboot, and it makes sense that it wouldn't support random unsigned flashes, even if the phone is bootloader unlocked.
Do you have any additional experience with unlocking additional bands from the diag mode? I'm not sure what you were experimenting with at the time - if it was for your root exploit or something else.
no, I do not have any experience unlocking additional bands, I do not know any other stuff about that diag apart from what has been posted there
but I find following thread very interesting and I guess it might be related to what you want too:
XZ1 Compact - MetroPCS VoLTE + Latest Pie + Fingerprint + Wi-Fi Calling Step by Step Guide
Overview: This guide provides step-by-step instructions for flashing any existing Sony stock rom Android 8 or 9 to the latest Sony stock ROM Android 9 Build v47.2.A.11.228 for use on the MetroPCS network. The finalized flash is a hybrid of Sony...
forum.xda-developers.com
Yup, I'm well familiar with that thread. I helped eparr with the guide a little, and gave him the older stock image that he couldn't find online anymore.
We also had a separate conversation about a similar problem I was/we were having (relevant to this discussion) here: https://forum.xda-developers.com/t/carriers-for-xperia-xz1-compact-in-us.4477627/ where we talked about his guide, custom flashing, the Sony CustomizationSelector app, modem overlays, and a few other things.
I think because I'm running an AOSP-based (rather than stock-based) ROM, some of these options aren't available to me, which is why I was trying to investigate EDL and diag modes to connect with and adjust the modem configurations directly.
I should probably explore some alternative ROMs but since this phone is also my daily driver, there's a high cost/interrupt to wiping, reinstalling, and repeatedly experimenting, so I've been reluctant to do anything too extreme until the holidays.
Did you test LOS? I believe they have implemented very special stuff for modem and customizations handling there...
I have not yet. I'm currently running an Oreo AEX build. But LOS is one of the ones on my list to experiment with when I get a chance to upgrade.
I think this is the stuff integrated in LOS:
GitHub - whatawurst/OpenCustomizationSelector
Contribute to whatawurst/OpenCustomizationSelector development by creating an account on GitHub.
github.com