[Recovery][UNOFFICIAL] TWRP 3.5.0 | Development & Discussion | 2021.01.18 - Sony Xperia M2

Unofficial build of TWRP 3.4.0 for the Sony Xperia M2 (eagle).
Disclaimer
Your warranty is now void!
You will be doing everything at your own risk.
I am not responsible for bricked or damaged devices.
Download
https://f2065.ru/android/Android_M2_en.htm
Changelog
TWRP 3.5.0_9, build 2021.01.18
Source TWRP updated to 2021-01-18.
TWRP 3.4.0, build 2020.07.23
Source TWRP updated to 2020-07-23.
TWRP 3.4.0, build 2020.06.10
Minor kernel changes.
Source TWRP updated to 2020-06-10.
TWRP 3.3.1, build 2020.05.01
Minor kernel changes.
Source TWRP updated to 2020-05-01.
TWRP 3.3.1, build 2019.10.17
Update kernel (SDCardFS, etc).
Source TWRP updated to 2019-10-17.
TWRP 3.3.1, build 2019.07.09
Source TWRP updated to 2019-07-09.
TWRP 3.3.1, build 2019.06.17
Update kernel.
Source TWRP updated to 2019-06-17.
TWRP 3.3.0, build 2019.04.21
Cleanup and update configs.
Source TWRP updated to 2019-04-17.
TWRP 3.2.3
Remove SuperSU from TWRP
Support both md5 and md5sum file extensions when doing MD5 checking for zip files
TWRP 3.2.2
adb backup fixes
minor tweaks to handling date/time on Qualcomm devices
XDA:DevDB Information
TWRP for Sony Xperia M2, Tool/Utility for the Sony Xperia M2
Contributors
f2065, galaxyfreak, Konstantinosj77, sgspluss
Source Code: https://github.com/f2065
Version Information
Status: Beta
Beta Release Date: 2021-01-18
Created 2019-04-21
Last Updated 2021-01-18

Reserved

Reserved

Build 2019-07-09 released.

The links are down in your webpage for TWRP. Would you mind reuploading them?

JORGETECH said:
The links are down in your webpage for TWRP. Would you mind reuploading them?
Click to expand...
Click to collapse
Fixed (there was a WordPress plugins conflict)

f2065 said:
Fixed (there was a WordPress plugins conflict)
Click to expand...
Click to collapse
I have a question, I have unlocked the bootloader and flashed the twrp recovery but I can't access it? Seems like I have no recovery at all? Powering the phone on with -vol button pushed down, but the phone is just booting normal, or sometimes in safe mode.
I feel like my recovery is wiped? I have even tried to flash the img file from the TWRP Manager, and then pressed restart to recovery, but nothing (phone is rooted with SuperSU atm)
I really need help to install a recovery on this phone..
Android version : 5.1.1 / kernel version : 3.4.0-gc82e70f / Build number : 18.6.A.0.182

julianb710 said:
I have a question, I have unlocked the bootloader and flashed the twrp recovery but I can't access it?
Click to expand...
Click to collapse
The bootloader must be updated - ft_bootloader.png
Any flashing 5.1.1/4.4 - removes the updated bootloader…
After re-flashing 5.1.1/4.4, you need to re-flash the updated bootloader and recovery
Code:
fastboot flash recovery recovery_20200610.img
- fastboot_twrp3210.png
julianb710 said:
I have even tried to flash the img file from the TWRP Manager
Click to expand...
Click to collapse
TWRP Manager is not needed. My build works autonomously.

Updated TWRP to 3.5.0, but it makes no sense - its innovations relate to the latest platforms. For us - on the contrary, it has become more inconvenient - various functions inaccessible to us take up space in the GUI.

Hi, I have a problem (hardbrick-not softbrick) open the bootloader, I did a full custom clean to reinstall the rom and shut it down to insert the SD card. The result was, no download, no recovery, no flashtool, no LED indicator, no vibration, no picture, no everything, like QHSUSB_BULK. help and suggestions please? (thanks and sorry for the English)
----------------------------
edit.
they helped me find a more specific driver. now it is Qualcomm HS-USB QDLOADER 9008 (comX) now there is one port at least
----------------------------
edit..
I found possible options, it seems like an interesting and long topic. summarizing option a... Requirements
Win32DiskImager + 8GB SD card +A card reader or a PC which has an SD card slot + The mmcblk0.img extracted via ADB from a working phone of the same model... option b.. qfil.. option c... qpst... Will someone have a copy or could you provide me with one? It would also be useful for other people.
----------------------------
edit...
And on another pc with the same versions but (more recent sonycompanion) it appeared as SOMC device.

ChaarlyZ said:
I did a full custom clean to reinstall the rom and shut it down to insert the SD card
Click to expand...
Click to collapse
After a complete cleaning, you cannot exit TWRP, you must first install a new firmware!!!
If a full wipe and exit from TWRP was done before installing the firmware, then this is not a problem.
It is necessary to turn off the phone with a hidden button located near the slots.
Then flash the stock firmware 18.6.A.0.182
It is important that flashtool is version 0.9.18.6
The phone should boot up normally.
Then update the bootloader again and flash the TWRP.

f2065 said:
After a complete cleaning, you cannot exit TWRP, you must first install a new firmware!!!
If a full wipe and exit from TWRP was done before installing the firmware, then this is not a problem.
It is necessary to turn off the phone with a hidden button located near the slots.
Then flash the stock firmware 18.6.A.0.182
It is important that flashtool is version 0.9.18.6
The phone should boot up normally.
Then update the bootloader again and flash the TWRP.
Click to expand...
Click to collapse
Hello, thanks for answering. you are very kind. I am already on the recommended version of the flash tool and firmware. It does not react to any key combination, I have used the hidden button, I have disconnected its battery for a long time even, and tried with another cable, there are no signs of life, only without drivers like qhsusb_bulk, with usb drivers qdloader9008 (com x). And on another pc with the same versions but (more recent sonycompanion) it appeared as somc device.

ChaarlyZ said:
It does not react to any key combination, I have used the hidden button, I have disconnected its battery for a long time even, and tried with another cable, there are no signs of life, only without drivers like qhsusb_bulk, with usb drivers qdloader9008 (com x). And on another pc with the same versions but (more recent sonycompanion) it appeared as somc device.
Click to expand...
Click to collapse
It should not be. Flashtool should restore it.
Probably you are pressing the wrong combination of buttons or a problem with the drivers.
Turn off the phone with the hidden button, hold down vol_down and connect the phone to USB. Driver installation should start. If the driver is installed, the phone's green LED should light up.

f2065 said:
It should not be. Flashtool should restore it.
Probably you are pressing the wrong combination of buttons or a problem with the drivers.
Turn off the phone with the hidden button, hold down vol_down and connect the phone to USB. Driver installation should start. If the driver is installed, the phone's green LED should light up.
Click to expand...
Click to collapse
No, not that kind of rookie mistake, sadly. this is the famous case and without much information of super hard bricks.
from what I think I have understood according to my boarding attempts. The connection addresses of its gpt table to the sectors are lost, either kernel, recovery, download, system, it remains as qdloader9008 floating empty, and its physical buttons stop responding because they are not loaded logically (including hidden button and its diode led) no longer find the sector where its internal drivers are .. it would be like .. similar to a case of bad flashing in the BIOS of the PC.

well.. I'm still looking for a solution, I don't know what else to try, I downloaded every magic app I found, some have returned info, others totally on purpose. with linux, i can't recognize it. if you have any suggestions please...

ChaarlyZ said:
well.. I'm still looking for a solution, I don't know what else to try, I downloaded every magic app I found, some have returned info, others totally on purpose. with linux, i can't recognize it. if you have any suggestions please...
Click to expand...
Click to collapse
what is your device? maybe i can help you with the mmcblk0.img thing. i have a D2303

JuniorCaesar said:
what is your device? maybe i can help you with the mmcblk0.img thing. i have a D2303
Click to expand...
Click to collapse
Hello, if you can do it please I still need to start it, the ideas I found, if I understood correctly is to make a complete copy of the memory to put it in a sd and if there is support it should start, mine is D2305 but how is it going to sd maybe work. I just need to boot it, what a crazy problem when partition table gets corrupted dd if=/dir |vp| dd of=/dir
you can't imagine what it's like to be in 2021 with an alcatel 4015

ChaarlyZ said:
Hello, if you can do it please I still need to start it, the ideas I found, if I understood correctly is to make a complete copy of the memory to put it in a sd and if there is support it should start, mine is D2305 but how is it going to sd maybe work. I just need to boot it, what a crazy problem when partition table gets corrupted dd if=/dir |vp| dd of=/dir
you can't imagine what it's like to be in 2021 with an alcatel 4015
Click to expand...
Click to collapse
i believe it requires linux to be installed, i'll do it when i'm done with my midterms. will let you know

still no news?
I have not been able to buy another cell phone
I've tried everything, please help!!
Sony M2 - D2305 Super-HardBrick
Hello, I ask for help and assistance, please. Sony M2 - D2305 The whole tutorial was read carefully and followed as is, it was achieved, used and tried to meet the objectives happily, it is not my first flash, nor the first device to die...
forum.xda-developers.com

f2065 said:
Unofficial build of TWRP 3.4.0 for the Sony Xperia M2 (eagle).
Disclaimer
Your warranty is now void!
You will be doing everything at your own risk.
I am not responsible for bricked or damaged devices.
Download
https://f2065.ru/android/Android_M2_en.htm
Changelog
TWRP 3.5.0_9, build 2021.01.18
Source TWRP updated to 2021-01-18.
TWRP 3.4.0, build 2020.07.23
Source TWRP updated to 2020-07-23.
TWRP 3.4.0, build 2020.06.10
Minor kernel changes.
Source TWRP updated to 2020-06-10.
TWRP 3.3.1, build 2020.05.01
Minor kernel changes.
Source TWRP updated to 2020-05-01.
TWRP 3.3.1, build 2019.10.17
Update kernel (SDCardFS, etc).
Source TWRP updated to 2019-10-17.
TWRP 3.3.1, build 2019.07.09
Source TWRP updated to 2019-07-09.
TWRP 3.3.1, build 2019.06.17
Update kernel.
Source TWRP updated to 2019-06-17.
TWRP 3.3.0, build 2019.04.21
Cleanup and update configs.
Source TWRP updated to 2019-04-17.
TWRP 3.2.3
Remove SuperSU from TWRP
Support both md5 and md5sum file extensions when doing MD5 checking for zip files
TWRP 3.2.2
adb backup fixes
minor tweaks to handling date/time on Qualcomm devices
XDA:DevDB Information
TWRP for Sony Xperia M2, Tool/Utility for the Sony Xperia M2
Contributors
f2065, galaxyfreak, Konstantinosj77, sgspluss
Source Code: https://github.com/f2065
Version Information
Status: Beta
Beta Release Date: 2021-01-18
Created 2019-04-21
Last Updated 2021-01-18
Click to expand...
Click to collapse
Hello. This is my first time flashing TWRP.
I've flashed the latest version (3.5.0) on the phone but I can not seem to load it. I've tried the button combinations but holding the Volume Down doesn't do any affect and just boots to the OS while the Volume Up button makes the phone vibrate 3 times, then pauses, then vibrates one time, pauses and then repeats the cycle endlessly. Am I missing something here?
Sincerely.
EDIT: Following the second option of this guide step by step did the trick. It is the bootloader updating guide that the OP suggests above to make TWRP work. Problem solved.
Guide link: https://forum.xda-developers.com/t/...der-update-ftfs-new-update-available.3288148/

Related

[BETA][OFFICIAL] Android 7.0 EMUI 5 (L04C567B320) for FRD-L04C567

Build Number: FRD-L04C567B320 (USA)
Files for DOWNLOAD:
Download link:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1278/g104/v68366/f1/full/update.zip
Region Patch:
http://update.hicloud.com:8180/TDS/...66/f1/full/hw/usa/update_data_full_hw_usa.zip
How to install:
1. Requirements: Your device needs to have TWRP custom recovery installed and has to be rooted.
2. Before proceeding make sure that your device model is FRD-L04 from Settings > About phone.
3. Download the update.zip package from above links and copy it to your Sdcard /dload folder.
4. Turn your phone off and reboot into recovery mode by hold Vol up + Power for a few seconds.
5. Back up all the partitions into the external microSD card (recommended).
6. Now go to Install and select the update.zip package you copied to your Sdcard.
7. Upon installation wipe the cache and reboot your phone.
8. In case you encounter issues with Bluetooth, NFC, etc you can try flashing the region package provided above through TWRP.
Warning: As mentioned earlier, this is a beta update that contains many bugs and has several compatibility issues with hardware and 3rd party apps.
USE IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE FOR ANY BROKEN RELATED TO IT
perzan07 said:
Build Number: FRD-L04C567B320 (USA)
Files for DOWNLOAD:
Download link:
http://update.hicloud.com:8180/TDS/data/files/p3/s15/G1278/g104/v68366/f1/full/update.zip
Region Patch:
http://update.hicloud.com:8180/TDS/...66/f1/full/hw/usa/update_data_full_hw_usa.zip
How to install:
1. Requirements: Your device needs to have TWRP custom recovery installed and has to be rooted.
2. Before proceeding make sure that your device model is FRD-L04 from Settings > About phone.
3. Download the update.zip package from above links and copy it to your Sdcard /dload folder.
4. Turn your phone off and reboot into recovery mode by hold Vol up + Power for a few seconds.
5. Back up all the partitions into the external microSD card (recommended).
6. Now go to Install and select the update.zip package you copied to your Sdcard.
7. Upon installation wipe the cache and reboot your phone.
8. In case you encounter issues with Bluetooth, NFC, etc you can try flashing the region package provided above through TWRP.
Warning: As mentioned earlier, this is a beta update that contains many bugs and has several compatibility issues with hardware and 3rd party apps.
USE IT AT YOUR OWN RISK, I'M NOT RESPONSIBLE FOR ANY BROKEN RELATED TO IT
Click to expand...
Click to collapse
Thanks ..
I might as well post this here -> -> How to: Root and repair data on the FRD-L04 - B320
https://forum.xda-developers.com/showpost.php?p=70266853&postcount=262
Will android pay stop working even if I use the official beta 7.0?
Thanks man, but is there any successful way to flash B324 so far?
Is Wi-Fi calling enabled in this beta?
Managed to do the same using Charles app (see https://forum.xda-developers.com/ho...-to-nougat-t3510275/post69885525#post69885525) without any unlocking and flashing.
I have the FRD-L04B567 phone. I installed the TWRP for the Honor 8. I have installed a different ROM (CM13.1 ROM) successfully. I followed your instructions to the "T" in post #1 . The install of update.zip stopped at /cust with an error. I tried wiping and rebooting but am stuck in the "honor" bootup screen. Unable to force back into TWRP or fastboot or ADB at this time. Still picking up the pieces....
UPDATE: I forced phone into Huawei eRecovery screen and selected factory reset/wipe That got Nougat running but there is no keyboard and Google will only allow voice for any input. Since my wifi is encrypted, I cant give Nougat a password to get on the internet. I am creating a temporary unencrypted network to see if I can get further.
UPDATE: TWRP was wiped so I will reinstall. Then I will try update the regional update (second update mentioned)
UPDATE: Reflashed TWRP 3.0.2.0 for Honor 8, I can get into the bootloader but not recovery, eRecovery works but...(worthless). I cant flash the second update.zip because I cant get TWRP started. Obviously 3.0.2.0 is not compatible with Nougat, I may try 3.0.3.0? why not...
UPDATE - Flashing TWRP 3.0.3.0 was dumb. Now ADB sees the device (good) but I can not get to bootloader or recovery. TWRP flashes (displays) once a second and will not start (bad) . Hopefully someone can learn from my quest.
So, can someone help me proceed from a state where ADB sees the device? thanks Maybe extract update.zip?
thekubiaks said:
So, can someone help me proceed from a state where ADB sees the device? thanks Maybe extract update.zip?
Click to expand...
Click to collapse
This guy
https://forum.xda-developers.com/member.php?u=4210629
Could help you recover, but he will be back only after 15th Jan.
Have you tried Huawei's hisuite? It has a recovery option..
yalokiy said:
This guy
https://forum.xda-developers.com/member.php?u=4210629
Could help you recover, but he will be back only after 15th Jan.
Have you tried Huawei's hisuite? It has a recovery option..
Click to expand...
Click to collapse
Thanks for the reply, I finally got TWRP 3.0.2.0 for Honor 8 flashed (but now it won't work), I believe Nougat and TWRP aren't compatible. Huawei Hisuite said that phone was fine and recovery not necessary??? I disagree. I think I will have to wait for TWRP that is Nougat compatible with FRD-L04
thekubiaks said:
I have the FRD-L04B567 phone. I installed the TWRP for the Honor 8. I have installed a different ROM (CM13.1 ROM) successfully. I followed your instructions to the "T" in post #1 . The install of update.zip stopped at /cust with an error. I tried wiping and rebooting but am stuck in the "honor" bootup screen. Unable to force back into TWRP or fastboot or ADB at this time. Still picking up the pieces....
UPDATE: I forced phone into Huawei eRecovery screen and selected factory reset/wipe That got Nougat running but there is no keyboard and Google will only allow voice for any input. Since my wifi is encrypted, I cant give Nougat a password to get on the internet. I am creating a temporary unencrypted network to see if I can get further.
UPDATE: TWRP was wiped so I will reinstall. Then I will try update the regional update (second update mentioned)
UPDATE: Reflashed TWRP 3.0.2.0 for Honor 8, I can get into the bootloader but not recovery, eRecovery works but...(worthless). I cant flash the second update.zip because I cant get TWRP started. Obviously 3.0.2.0 is not compatible with Nougat, I may try 3.0.3.0? why not...
UPDATE - Flashing TWRP 3.0.3.0 was dumb. Now ADB sees the device (good) but I can not get to bootloader or recovery. TWRP flashes (displays) once a second and will not start (bad) . Hopefully someone can learn from my quest.
So, can someone help me proceed from a state where ADB sees the device? thanks Maybe extract update.zip?
Click to expand...
Click to collapse
If you want to get back to any working state, i recovered from 7.0 unbootable to vanilla 6.0 like so (for frd-l09, but probably still applies):
https://forum.xda-developers.com/honor-8/how-to/honor-8-bricked-t3521813/post70326674#post70326674
// edit, also for completeness, i then flashed twrp 3.0.2 (official) and installed the cm 7.1.1 from the other thread here. All working fine.
fuflo,
thank you for your reply, it helped me get my Honor 8 back up and running.... I am now running CM 14.1 and Nougat 7.1.1 on my FRD-L04
Cheers
---------- Post added at 05:32 AM ---------- Previous post was at 05:31 AM ----------
fuflo,
thank you for your reply, it helped me get my Honor 8 back up and running.... I am now running CM 14.1 and Nougat 7.1.1 on my FRD-L04
Cheers
B320? I used these update files and mine says B317. Am I missing something?
jim262 said:
B320? I used these update files and mine says B317. Am I missing something?
Click to expand...
Click to collapse
Look again in the thread closely, you'll find another script to go to B320
Same problem as above, I could flash the update.zip, but not the USA package, maybe I didn't have the right TWRP version?

[TWRP 3.3.1.0] [SAWSHARK] TWRP recovery for Huawei Watch 2 LTE [10/21/19]

This is twrp compiled for sawshark a.k.a. Huawei Watch 2 LTE
Download: https://github.com/travismills82/tw...i_sawshark/blob/android-9.0/twrp_sawshark.tar MIRROR: https://www.androidfilehost.com/?fid=1899786940962615056
Sources:
Kernel: https://github.com/travismills82/android_kernel_huawei_sawshark
TWRP Tree: https://github.com/travismills82/twrp_android_device_huawei_sawshark
untar and flash with fastboot or flash image directly in twrp.
reserved...
This work on bx-l09?
I've been using the 3.1.x version of TWRP (from another thread), and I'm currently experiencing this reboot-to-recovery loop issue. Does this 3.2.3 version capable of working around this?
It's currently caused by two factors (either one would trigger):
- You invoked "Disconnect & Reset" to do a factory reset.
- The watch downloaded the October OTA update (which is yet to see a custom ROM) and rebooted itself.
It seems to set a flag in the bootloader so under such situation it'll automatically boot to recovery with a special parameter to update/reset the device. This parameter can only be understood by stock recovery, and only stock recovery could clear that flag so the watch can continue booting normally. My current TWRP version cannot understand this parameter and would boot in to the TWRP main menu, without clearing the flag.
For now, the solution is to flash the stock recovery and let it finish whatever it wants (be it doing the OTA update or factory reset), then flash back TWRP and whatever else.
I'll try flashing this one and see if it makes any difference, though in that thread someone said to never actually flash the recovery (use "fastboot boot" only) and keep the stock recovery in there...
EDIT: Flashed it, but I won't be actively testing this as it's hard enough to just set the watch up... the advice would be to disable OTA update (I'm not sure how, and whether the method works), and keep a backup copy of stock recovery in case something like this happens...
Updated recovery
travis82 said:
Updated recovery
Click to expand...
Click to collapse
@travis82 Hello I'd like to ask if this is the latest version of the recovery available? I bought Huawei Watch 2 Sport LTE and I'm thinking about rooting it. Thanks in advance!

[TWRP][OFFICIAL] TWRP 3.3.x for UMIDIGI One Max [MT6763]

This TWRP recovery is compiled from source & not official yet
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.
Code:
#include <std_disclaimer.h>
/*
*
* We are 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 us for messing up your device, we will laugh at you.
*
*/
Prerequisites
1. Unlocked bootloader.
Bugs
1. No bugs
2. If you have found a bug, please consider posting it to my GitHub Issues.
Instructions
1. Go to the fastboot mode.
2. Download the recovery.img and transfer it to the adb folder.
3. Open the cmd/terminal and change directory into the adb folder.
4. Now confirm/check that device is connected by typing:-
Code:
fastboot devices
If you got your device seriel number there then you are ready to continue otherwise try connecting device again and make sure USB debugging is on and you have granted permission to the PC to debug.
5. After that we will flash this TWRP recovery to the recovery partition by below command:-
Code:
fastboot flash recovery twrp-name.img
BooM ! TWRP flashed successfully.
6. Now unplug your device and then hold power button untill the phone turned off,after that press power button while holding vol down(-) button simultaneously and you will boot into TWRP recovery mode.
Enjoy !
Downloads
Official TWRP Website : https://twrp.me/umidigi/onemax.html
GitHub Release : Here (release name : TWRP-UMIDIGI-One_Max)
Version Information
ROM OS Version: 8.1.x Oreo
Source Code: Device Tree
Based On: TWRP
Credits
Omni Team for minimal TWRP source
@chankruze (myself) for device tree and compilation.
SUPPORT
Official Telegram Group
Official Telegram Channel
Hey ! Good job ! I tried building my own TWRP today but then noticed someone already did it ! Does encryption work ? I cant seem to decrypt the partition after flashing your TWRP.
EDIT : Couldn't wait, ended up formatting with encryption disabled via a zip + magisk
I've then proceeded to flash some GSI for Android 9 (even tried Q Beta 3) and if we want 9.0 one day, some heavy work will be needed : Cellular doesn't work; other than that, it all seems fine to me, camera is only 12mpx, front is 13mpx. Haven't tested more, i'm back to stock
EDIT 2: After comparing camera from stock and gsi, GSI wins easily. The camera is not as slow as stock.
Are there any decent ROMs yet for this phone? LineageOS would be fantastic.
@kgoerbig not to my knowledge. Maybe I'll try porting a 9.0 GSI soon.
I'm not sure if this is helpful or not, but Umidigi posts stock ROM on there forum. Can ROMs be ported based on there code? Or is it more complicated then that?
https://community.umidigi.com/m/?a=viewthread&tid=18692
_cab13_ said:
Hey ! Good job ! I tried building my own TWRP today but then noticed someone already did it ! Does encryption work ? I cant seem to decrypt the partition after flashing your TWRP.
EDIT : Couldn't wait, ended up formatting with encryption disabled via a zip + magisk
I've then proceeded to flash some GSI for Android 9 (even tried Q Beta 3) and if we want 9.0 one day, some heavy work will be needed : Cellular doesn't work; other than that, it all seems fine to me, camera is only 12mpx, front is 13mpx. Haven't tested more, i'm back to stock
EDIT 2: After comparing camera from stock and gsi, GSI wins easily. The camera is not as slow as stock.
Click to expand...
Click to collapse
I have tested LineageOS 16.0 GSI Android 9.0 (and many others ...) and it works well, even GSM and Camera.
The only thing I cannot have is a complete root : I install Magisk 19.3 correctly, but applications cannot get root permission (Titanium Backup cannot have su permission)
Hi to all!!!
I've unlocked bootloader, flashed twrp in post but when I power Off and On+Vol - my device doesn't power up...
Also if I make fastboot reboot recovery, my device reboot in fastboot mode again...
What's wrong??? I would test Descendant_ThreeDotZero_arm64_aonly rom!!!!
Pls Help me!!!!
silviuss82 said:
Hi to all!!!
I've unlocked bootloader, flashed twrp in post but when I power Off and On+Vol - my device doesn't power up...
Also if I make fastboot reboot recovery, my device reboot in fastboot mode again...
What's wrong??? I would test Descendant_ThreeDotZero_arm64_aonly rom!!!!
Pls Help me!!!!
Click to expand...
Click to collapse
If you use the stock boot.img with an GSI system image, it will not boot, you must first flash Magisk.zip before reboot!
It will disable dm-verity, and you can boot after.
If it continue reboot in bootloader mode, use spflashtool to flash a stock rom and all will be right
Or if you have a TWRP backup, restore all partitions except boot/recovery/cache/system/data and you can boot
@ dreambo Can you make a writeup of properly unlocking the bootloader/rooting? Or did you use these methods?
https://community.umidigi.com/forum.php?mod=viewthread&tid=17376
https://www.youtube.com/watch?v=xM_M5XP--Z8&t=176s
I should be receiving my Umidigi One Max in a day or so, and do not want to bork anything up! I have SPflash installed both on a Win10 laptop, and on a Ubuntu Linux machine.
dreambo said:
If you use the stock boot.img with an GSI system image, it will not boot, you must first flash Magisk.zip before reboot!
It will disable dm-verity, and you can boot after.
If it continue reboot in bootloader mode, use spflashtool to flash a stock rom and all will be right
Or if you have a TWRP backup, restore all partitions except boot/recovery/cache/system/data and you can boot
Click to expand...
Click to collapse
kgoerbig said:
@ dreambo Can you make a writeup of properly unlocking the bootloader/rooting? Or did you use these methods?
https://community.umidigi.com/forum.php?mod=viewthread&tid=17376
https://www.youtube.com/watch?v=xM_M5XP--Z8&t=176s
I should be receiving my Umidigi One Max in a day or so, and do not want to bork anything up! I have SPflash installed both on a Win10 laptop, and on a Ubuntu Linux machine.
Click to expand...
Click to collapse
You do not need to unlock you phone, mine is rooted with Magisk and have TWRP installed without unlock bootloader.
Just use spflashtool to flash a stock rom, but replace the recovery by TWRP and the boot.img by magisk_patched.img one.
Here how I do exactly:
1- in my running stock rom, I install MagiskManager and install Magisk by choosing the last option (patch existing boot.img)
2- give it your stock boot.img (extracted from stock rom) and it create for you /sdcard/Download/magisk_patched.img
3- use this to replace your stock boot.img and use also TWRP.img to replace stock recovery.img and flash the whole rom with SPFlashTool
Can you backup with TWRP with a locked bootloader? Isn't write access blocked with a locked bootloader?
dreambo said:
You do not need to unlock you phone, mine is rooted with Magisk and have TWRP installed without unlock bootloader.
Just use spflashtool to flash a stock rom, but replace the recovery by TWRP and the boot.img by magisk_patched.img one.
Here how I do exactly:
1- in my running stock rom, I install MagiskManager and install Magisk by choosing the last option (patch existing boot.img)
2- give it your stock boot.img (extracted from stock rom) and it create for you /sdcard/Download/magisk_patched.img
3- use this to replace your stock boot.img and use also TWRP.img to replace stock recovery.img and flash the whole rom with SPFlashTool
Click to expand...
Click to collapse
kgoerbig said:
Can you backup with TWRP with a locked bootloader? Isn't write access blocked with a locked bootloader?
Click to expand...
Click to collapse
If you can run the TWRP with a locked bootloader (and you can in case of umidigi one max) you can do any thing
dreambo said:
If you can run the TWRP with a locked bootloader (and you can in case of umidigi one max) you can do any thing
Click to expand...
Click to collapse
One last question. =)
Which boot file from stock did you use to patch with?
Downloadable from: https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
UMIDIGI One Max V1.0
or
UMIDIGI One Max E V1.0
kgoerbig said:
One last question. =)
Which boot file from stock did you use to patch with?
Downloadable from: https://community.umidigi.com/forum.php?mod=forumdisplay&fid=211
UMIDIGI One Max V1.0
or
UMIDIGI One Max E V1.0
Click to expand...
Click to collapse
I have used the European one, UMIDIGI One Max E V1.0
So I just received my One Max today. I was able to patch the boot image, and root the phone. I also, installed TWRP, but I'm running into an issue. From TWRP, I formatted with a normal wipe, It asked "Do you want to do this, it wipes data encryption Etc". I typed yes, and it did it's thing. Rebooted. Setup my basic settings on the phone. I rebooted back into TWRP, and it immediatly asked for a "decryption" password. It also won't allow me to mount internal partitions or sdcard. This even after I rooted via a patched boot file, and verified root access while booted in android (with root verify app). What am I doing wrong for TWRP to gain access to storage?
"Couldn't wait, ended up formatting with encryption disabled via a zip + magisk"
How did you format without encryption? I try to format from TWRP, type 'yes' , to verify, and encryption is still active. I'd like to disable encryption, so that I can properly backup everything from TWRP.
kgoerbig said:
So I just received my One Max today. I was able to patch the boot image, and root the phone. I also, installed TWRP, but I'm running into an issue. From TWRP, I formatted with a normal wipe, It asked "Do you want to do this, it wipes data encryption Etc". I typed yes, and it did it's thing. Rebooted. Setup my basic settings on the phone. I rebooted back into TWRP, and it immediatly asked for a "decryption" password. It also won't allow me to mount internal partitions or sdcard. This even after I rooted via a patched boot file, and verified root access while booted in android (with root verify app). What am I doing wrong for TWRP to gain access to storage?
Click to expand...
Click to collapse
Search in xda forum a zip that you can flash with TWRP before installing the Magisk zip from TWRP.
its name is disable_dm_verity????.zip, it disable in the boot.img the encryption.
After that format the data partition (format and not wipe, it's important!) and reboot normally, and your data partition will not be encrypted
dreambo said:
Search in xda forum a zip that you can flash with TWRP before installing the Magisk zip from TWRP.
its name is disable_dm_verity????.zip, it disable in the boot.img the encryption.
After that format the data partition (format and not wipe, it's important!) and reboot normally, and your data partition will not be encrypted
Click to expand...
Click to collapse
I eventually found all the correct files to remove encryption. I also installed AOSP. I'm kind of torn between the stock and AOSP. AOSP has better performance, but one annoying aspect is that I cannot find anywhere in the settings to switch the navigation buttons in AOSP (Back button is on the far left, I like it on the right side). Seems trivial, but it's annoying. I can now fully backup & restore in TWRP, which makes life a lot easier.
kgoerbig said:
I eventually found all the correct files to remove encryption. I also installed AOSP. I'm kind of torn between the stock and AOSP. AOSP has better performance, but one annoying aspect is that I cannot find anywhere in the settings to switch the navigation buttons in AOSP (Back button is on the far left, I like it on the right side). Seems trivial, but it's annoying. I can now fully backup & restore in TWRP, which makes life a lot easier.
Click to expand...
Click to collapse
Which AOSP ? where do you found it ?
dreambo said:
Which AOSP ? where do you found it ?
Click to expand...
Click to collapse
This thread:
https://forum.xda-developers.com/android/development/umidigi-one-max-custom-rom-modding-t3942521
This Rom
https://github.com/phhusson/treble_experimentations/releases
Do a complete backup of stock from TWRP onto microsd or USB first! System, data, modem, nvram partitions etc. That way you can restore from TWRP, and not lose os, data, or nvram (IMEI).
Specifically, system-arm64-aonly-gapps-su.img.xz
1. Download and extract file you downloaded, onto your phone.
2. Do a format (type yes)
3. Install from TWRP as "image".

[TWRP] [Port] L.R.-Team recovery OMFG-Mod-From Cactus -to -Umidigi-F1

First version shared was twrp 3.2
New version is 3.3.0
***ORIGINAL TWRP is not my work. Only the porting of it to this device. I take no credit for the source.
*** DISSCLAIMER ALLERT***
I started having issues with encryption coming back to enforcing when using the Ported Team LR TWRP 3.3
Did not have trouble yet with OMFG-Mod version.
Also @ghost45 has made a build of twrp 3.3.1 for F1. It works good as well
https://forum.xda-developers.com/showpost.php?p=79651368&postcount=49
--- all versions give trouble of loosing IMEI when using the remove force encryption patch I suggest below. Left logs with @Zackptg5 .
**May need more testing**
-decryption is broken
-MTP is working
-ADB is working
****--Advanced menu items are not correctly on 3.2 version.
-- Some of the advanced menu was fixed in 3.3.(install root is working)
- Advanced menu has extra features.(all from source twrp)
-- install magisk (currently has V17 on OMFG V19 on LR TEAM)
-- patch dm-verity and force encrypt remove.zip. ( personally I prefer the universal dm-removal patch from xda)
-- Remove system password, (from original dev, I have not tested)
--
--Install (basic directions only)--details may be added later if needed
Open zip and fastboot flash the recovery image if bootloader is unlocked.
or
Open zip , then open scatterfile (scatter file in test 1 has issue, updating it in next test )with sp-flashtool , select download
--First boot into TWRP will give errors for unable to mount /data. This is from the force-encryption.
- When boot into TWRP, select wipe -> format type 'yes' to format data
- When format is done, return to TWRP home page, select reboot -. recovery
--Now Patch device so no longer forces encryption
-- Use built in feature from 'Advanced Menu' or use the following directions--Fails to unpack boot. (current zip used is not compatible with system-as-root boot.img)
-To remove this I use 'Disable_Dm-Verity_ForceEncrypt' from
-- https://github.com/Zackptg5/Disable_Dm-Verity_ForceEncrypt -- currently based on magisk V19.2
-Download from the "Clone or Download" button on the above linked Github Page.
-Unzip the downloaded file. You will have a folder with same name as the zip package. Browse inside this folder, select all files and zip them.
-Put this new zip file onto your phone. ( Hay notice the MTP function on this TWRP works)
- in stall the zip like any normal twrp package.
--Next Install Magisk
--Use Built in Root Option from 'Advanced Menu' to use Magisk V19 or the following direction
- Goto the releases page of magisk github page. ==>LINK
- Download latest Magisk zip , Put file to phone, Install.
-- Download Folder For TWRP Ported from OMFG-Mod
https://www.androidfilehost.com/?w=files&flid=294886
-Screenshots.
- Ported OMFG-MOD gold Button TWRP V3.2
- Ported Team LR TWRP 3.3 standard Button
Attached Below
--Thanks --Mentions
recovery source from [LR TEAM] MIUI
http: //www.miui.com/forum.php?mod=viewthread&tid=19006123&page=1&mobile=2#pid257831639
link is newer version from ported recovery. They updated recently. Next port may use newer base as well.
hello @ColtonDRG. Long time.
I see you posted in umidigi forum that bootloader is not checking signature. So you CAN flash images with flashtool without unlocking. Is that correct.?
I have based the above install guide on that fact that you CAN.
But the first twrp posted by "ghost45" says no it must be unlocked.
edit:
I should be able to verify later today or this weekend, when my order arrives.
OK, verified, when i used flash tool and put twrp on phone before unlocking bootloader, on reboot I was stuck in "RED" status for boot loader. So must unlock
Flash this zip to remove the AdupsFota app
this is the update app. You will not be able to install OTA when rooted and twrp anyway, And if an OTA comes you will get stuck in recovery bootloop. So this flash file will rename the 2 apk related to OTA download and Force reboot that supposed to install that update.
Reserved
Will keep this post for working on issues .
Right now , I discovered after playing with the built in dm verity patch and root install lead imei's getting erased.
Restored the full rom with flash tool fixed, will update process as necessary
Restarted from the top again.
--1 Full stock rom flashed with sp flash tool.
--2 Twrp flashed in flash tool
--3 format /data, reboot recovery
--4 use mtp to copy Disable_Dm-Verity_Forceencrypt to phone
--5 flash the decrypt zip. And at the end of flash the output log showed 'failed to mount /nvdata file not exist'
*** Waiting for input from the Patch dev. Others on his xda thread with MTK have had similar trouble***
--6 use mtp , put stock recovery file on phone. Image flash stock recovery, reboot recovery, do factory reset in stock recovery. This fixed the /nvdata error.
--7 sp flash twrp again, use built in 'install root' option from advanced menu.
Bam all done
New Umidigi f1 recovery 3.3.1 test2 is pubblished.
Test this one if all is corrected...
http://www.mediafire.com/file/1emy4tk1gvnkj96/recovery-twrp-3.3.1_Umidigi_F1_test_2.rar/file
ghost45 said:
New Umidigi f1 recovery 3.3.1 test2 is pubblished.
Test this one if all is corrected...
http://www.mediafire.com/file/1emy4tk1gvnkj96/recovery-twrp-3.3.1_Umidigi_F1_test_2.rar/file
Click to expand...
Click to collapse
Thank you, this one has no displayed errors.
I have question though.
Do you know how to make system be mounted as /system instead of /system/system ?
Hey, buddy. Good to see you on the forums again. When I picked up this device I wondered if anyone from the R1 HD days would also be on it. I seem to have misplaced mine but I'll find it eventually, send me a DM if you wanna talk about it. I'm not 100% sure about this, but the bootloader verifying signatures might have been patched in because I don't remember mine doing that when they first came out. Of course even if it does, SPFT is still useful for unbricking and downgrading, but I really doubt UMIDIGI will patch out the unlock option like BLU did.
Hello again, all. I've been working on my UMIDIGI F1 again and after flashing the most recent firmware update using SPFT and trying to flash TWRP again I realized that something that changed in the latest firmware update has broken all of the existing TWRP images. Now the bootloader screen hangs for a while, sometimes a green bar appears at the top of the screen briefly, and then the phone reboots into Android. It is perhaps worth noting that when I tried to flash the upgrade in download only mode it just complained about the partition layout or something like that and then bailed, telling me to use the Format and Download option instead. I didn't do that because UMIDIGI told me not too and instead opted to try the Firmware Update option, which did work. I'm going to try to downgrade (hopefully I don't get bricked from downgrading preloader, efuses, etc) but I am a bit concerned about what has changed. Stock recovery still boots OK so it would seem to me that the bootloader isn't just completely borked, but either way it's a bit alarming that an OTA caused the custom recoveries we have to go kerplooie.
ColtonDRG said:
Hello again, all. I've been working on my UMIDIGI F1 again and after flashing the most recent firmware update using SPFT and trying to flash TWRP again I realized that something that changed in the latest firmware update has broken all of the existing TWRP images. Now the bootloader screen hangs for a while, sometimes a green bar appears at the top of the screen briefly, and then the phone reboots into Android. It is perhaps worth noting that when I tried to flash the upgrade in download only mode it just complained about the partition layout or something like that and then bailed, telling me to use the Format and Download option instead. I didn't do that because UMIDIGI told me not too and instead opted to try the Firmware Update option, which did work. I'm going to try to downgrade (hopefully I don't get bricked from downgrading preloader, efuses, etc) but I am a bit concerned about what has changed. Stock recovery still boots OK so it would seem to me that the bootloader isn't just completely borked, but either way it's a bit alarming that an OTA caused the custom recoveries we have to go kerplooie.
Click to expand...
Click to collapse
There is a newer twrp that has been released on 4pda.net that supposed to work on newest firmware release.
And downgrading with flashtool should work. Again need to use firmware upgrade option.
mrmazak said:
There is a newer twrp that has been released on 4pda.net that supposed to work on newest firmware release.
And downgrading with flashtool should work. Again need to use firmware upgrade option.
Click to expand...
Click to collapse
Downgrading worked. I couldn't find the newer TWRP version you were referring to and the website you mentioned redirects to a bunch of scammy crap.
ColtonDRG said:
Downgrading worked. I couldn't find the newer TWRP version you were referring to and the website you mentioned redirects to a bunch of scammy crap.
Click to expand...
Click to collapse
We have the twrp file copied to telegram group also. I'm stuck on mobile, or I would just copy the twrp here.
UMIDIGI
UMIDIGI unofficial TG group
https://t.me/UMIDIGI
Disable_Dm-Verity_ForceEncrypt failed
Hello, I'm trying to patch my F1 using the Disable_Dm-Verity_ForceEncrypt, but am stuck with an error "Dumping/splitting image failed. Aborting..." This occurs when I try using the Install from twrp. Has anyone encountered this issue before? I have done a wipe, and also tried installing Magisk (which installs fine).

[ROM][9.0_r46][mermaid] SonyAOSP

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.
*/
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc)
Whats Working:
Probably everything.
Whats not Working:
Everything should work. If you find bug then please report it here: https://github.com/sonyxperiadev/bug_tracker/issues
Steps to flash:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img (WARNING: This will delete all your data on device so have a backup before doing anything)
fastboot flash oem NameOfOEMFile.img
You only need to flash userdata.img when you are going from Stock Firmware to AOSP or when you get issues with future builds.
Downloads:
ROM Dual SIM: Download all the files in that folder
ROM Single SIM: Download all the files in that folder
OEM: OEM Unzip this and flash it as OEM. Instructions above
XDA:DevDB Information
[ROM][9.0_r46][mermaid] SonyAOSP, ROM for the Sony Xperia X10 Plus
Contributors
Haxk20
Source Code: https://android.googlesource.com/platform/manifest
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Version Information
Status: Beta
Created 2019-09-11
Last Updated 2020-01-03
Reserved
NOW: Build for both Dual and Single SIM variants is in to download and test.
Reserved
Help, brothers! Dual sim dont work!!! The network appears and disappears. I bought a phone in Russia. presented to my sister in Belarus. And stumbled upon this problem. Need detailed instructions for flashing the radio module, please!
[email protected] said:
Help, brothers! Dual sim dont work!!! The network appears and disappears. I bought a phone in Russia. presented to my sister in Belarus. And stumbled upon this problem. Need detailed instructions for flashing the radio module, please!
Click to expand...
Click to collapse
Is this issue with the ROM ? Or is the phone running stock firmware ?
If its stock then please move the discussion to questions and answers in 10 Plus forum.
If this is issue with AOSP then please flash stock firmware to check if its working on stock firmware.
I flashed and was able to boot up ok. Initially the phone would only boot up to a blank screen. You could see the volume change when hit vol+ or vol-, the background would remain black. Pulling the SD card and Sim out cause a reboot automatically that seemed to resolve this. The connection to wifi and lte connects and unexpectedly drops. This happens over and over, I cannot make calls or use sms . The browser works fine with the limited LTE time and wifi. There is a vzwinternet apn, I cannot edit them. I wasn't sure if here or where to post. The link to github doest work. The rom is fine otherwise and easily root with magisk 20.1
yitakumini said:
I flashed and was able to boot up ok. Initially the phone would only boot up to a blank screen. You could see the volume change when hit vol+ or vol-, the background would remain black. Pulling the SD card and Sim out cause a reboot automatically that seemed to resolve this. The connection to wifi and lte connects and unexpectedly drops. This happens over and over, I cannot make calls or use sms . The browser works fine with the limited LTE time and wifi. There is a vzwinternet apn, I cannot edit them. I wasn't sure if here or where to post. The link to github doest work. The rom is fine otherwise and easily root with magisk 20.1
Click to expand...
Click to collapse
Link to github is fixed. Thank you for that.
I can say that the ROM worked just fine for me. I switched to different ROM few months ago now and this ROM has no support now. It is very likely you installed wrong OEM image. Please install the latest one for 4.9 kernel.
Because we have started working on 4.14 and well its still in alpha and those 4.14 images there are for us to test it properly.
The WiFi dropping out is known bug and sadly we do not have a fix for it yet.
Please open a bug report on that github repo and explain the issue and post logcat and dmesg files there.
EDIT: Ah my bad. It seems like i already pointed to the correct OEM image. Interesting that calls dont work.
Yo, i've installed the ROM and tried to flash gapps but they didn't install. Is there a way to flash them?
demonic8383 said:
Yo, i've installed the ROM and tried to flash gapps but they didn't install. Is there a way to flash them?
Click to expand...
Click to collapse
You will have to boot TWRP and flash it trough TWRP as AOSP recovery doesnt support flashing openGapps.
Booting up TWRP can be a bit tricky so well good luck.
Haxk20 said:
You will have to boot TWRP and flash it trough TWRP as AOSP recovery doesnt support flashing openGapps.
Booting up TWRP can be a bit tricky so well good luck.
Click to expand...
Click to collapse
Booting into TWRP after the first boot into AOSP is kinda impossible - as far as I know the only way to get TWRP to boot for this device is first to flash the stock ROM -> wait for it to boot completely -> go to bootloader through the ADB command (key combination results in stuck TWRP logo) -> then boot into TWRP. Getting there through the key combination results in black screen. TWRP is in unofficial state - it works only on the stock ROM and only with "fastboot boot twrp.img", it cannot be flashed yet. I'm using this version - https://forum.xda-developers.com/10-plus/development/recovery-twrp-3-3-1-0-unofficial-t3954147
Installing it is possible, however the touchscreen stops working in TWRP when booting the installed version.
Any suggestions on that?
demonic8383 said:
Booting into TWRP after the first boot into AOSP is kinda impossible - as far as I know the only way to get TWRP to boot for this device is first to flash the stock ROM -> wait for it to boot completely -> go to bootloader through the ADB command (key combination results in stuck TWRP logo) -> then boot into TWRP. Getting there through the key combination results in black screen. TWRP is in unofficial state - it works only on the stock ROM and only with "fastboot boot twrp.img", it cannot be flashed yet. I'm using this version - https://forum.xda-developers.com/10-plus/development/recovery-twrp-3-3-1-0-unofficial-t3954147
Installing it is possible, however the touchscreen stops working in TWRP when booting the installed version.
Any suggestions on that?
Click to expand...
Click to collapse
Unfortunately no. SODP does not officially support openGapps and this rom isnt maintained anymore as we are working on 10.
Also twrp for our device will never be flashable image as its useless to do so. We do not have recovery partition and thus have to have recovery in boot image and we build AOSP with stock recovery as its almost impossible to build it with TWRP using AOSP sources. And my guess is that TWRP wont get any better until it supports android 10 which is when we can finally start working on it.
Also on twrp i was able to boot to twrp using this ROM. It was tricky and im guessing the times i did boot it it was just luck.
So so far its a mess.
Haxk20 said:
Unfortunately no. SODP does not officially support openGapps and this rom isnt maintained anymore as we are working on 10.
Also twrp for our device will never be flashable image as its useless to do so. We do not have recovery partition and thus have to have recovery in boot image and we build AOSP with stock recovery as its almost impossible to build it with TWRP using AOSP sources. And my guess is that TWRP wont get any better until it supports android 10 which is when we can finally start working on it.
Also on twrp i was able to boot to twrp using this ROM. It was tricky and im guessing the times i did boot it it was just luck.
So so far its a mess.
Click to expand...
Click to collapse
Damn that's sad, thanks for the info tho
Xperia i4213 problems with sound after flash. No touch sounds. No sound in youtube. The sound appears for 15 seconds after clicking on the flashlight icon. please help fix

Categories

Resources