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
Related
TWRP Recovery 3.2.3-0 For Xiaomi Redmi 6 (cereus) by TWRPBuilder
Code:
#include
/*
* 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.
*/
Welcome, all Redmi 6 users, This is Lastest TWRP Recovery For your device By TWRPBuilder Team
CHANGELOG for 3.2.2-0:
* adb backup fixes
* OTA style update zips will now install automatically without prompting for decrypt
* minor tweaks to handling date/time on Qualcomm devices
* updates to some language translations
DownloadsXiaomi Redmi 6 Recovery img
Sources:
Code:
[CENTER][URL="https://github.com/TwrpBuilder/android_device_xiaomi_cereus"][COLOR="bule"]Device tree[/COLOR][/URL]
[URL="https://github.com/TeamWin/Team-Win-Recovery-Project"][COLOR="bule"]TeamWin Github
[/COLOR][/URL][/CENTER]
How to install:
You must have fastboot installed on your pc and then:
Code:
adb reboot bootloader
fastboot flash recovery recovery.img
Notes:
You have to disable force encryption in order to access data partition:
- Format data
- Flash Magisk DFE or DisableForceEncryption zip, attached below.
- If you flashed miui global/china you must flash magisk or the DisableForceEncryption zip before rebooting to the system, or recovery will be replaced!
Don't Forget to Hit Thanks :good:
https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
Screenshots
attached :silly:
and this also
Anyone tried? Does it work?
Works for redmi 6 pro?
i dont get it, i've tried several times to install this twrp.img.
but as soon as i reboot {fastboot boot twrp.img} it just goes into the system, instead of recovery, and then when trying to reboot to recovery its still the xiaomi recovery.
how do i prevent it from constantly replacing the twrp with the standard recovery??
i dont know how to install magisk or the other zip if i even cant get into twrp...
mauritsivs said:
i dont get it, i've tried several times to install this twrp.img.
but as soon as i reboot {fastboot boot twrp.img} it just goes into the system, instead of recovery, and then when trying to reboot to recovery its still the xiaomi recovery.
how do i prevent it from constantly replacing the twrp with the standard recovery??
i dont know how to install magisk or the other zip if i even cant get into twrp...
Click to expand...
Click to collapse
same here: no chance to boot into twrp, even tough flash was successful
webc82 said:
same here: no chance to boot into twrp, even tough flash was successful
Click to expand...
Click to collapse
it actually works. Make sure you keep the vol+ button pressed for a while when you do the fastboot boot command.
It will eventually go to a black screen after the mi logo. now wait about one minute and press the volume buttons and twrp suddenly appears!!.
After installing ROM, it got soft-bricked, Had to wipe cache and dalvik again after rebooting, then it worked.
jackint said:
Works for redmi 6 pro?
Click to expand...
Click to collapse
No, it's different device
1.installed DisableForceEncryption_Treble.zip would restart forever.
2.MTP/ADB sideload don't work
3.everytime reboot show “Android System there's an internal problem with your device.Contact your manufactirer for details."
4. reboot is very solw.
Dachtire said:
1.installed DisableForceEncryption_Treble.zip would restart forever.
2.MTP/ADB sideload don't work
3.everytime reboot show “Android System there's an internal problem with your device.Contact your manufactirer for details."
4. reboot is very solw.
Click to expand...
Click to collapse
I have the same “Android System there's an internal problem with your device.Contact your manufacturer for details." message after installing global rom 9.6.4 and DFE
And i couldnt get my sim card working
has anyone been able to install a working rom on this device?
TWRP is not working.
I flash Magisk successfully and reboot the system normally. when i go back to twrp i don't find mount data. when my flash ROM from micro sd will work? please answer dev @TwrpBuilder
(Rom from Xiaomi.eu)
TWRP is working. But do not install custom rom. (Rom from Xiaomi.eu)
Good news. Now waiting a lineageos rom to leave MIUI.
gogojuy said:
TWRP is working. But do not install custom rom. (Rom from Xiaomi.eu)
Click to expand...
Click to collapse
If flash rom miui stable grobal wil work?
What is Xiaomi's wait time for unlocking BL on this device?
unlock time was 15 days for me...
i succesfully unlocked with no problems.
after flashing TWRP i ran into the same problems like Dachtire:
“Android System there's an internal problem with your device.Contact your manufactirer for details."
Click to expand...
Click to collapse
SIM wasn't working.
after several reflashing attemps i eventually flashed miui_HM6Global_V9.6.4.0.OCGMIFD_fb107cc63b_8.1.zip with success.
i'm experiencing problems with OTA right now... haven't figured out what the problem is.
---------- Post added at 07:38 PM ---------- Previous post was at 07:37 PM ----------
[/COLOR]
snoerme said:
unlock time was 15 days for me...
i succesfully unlocked with no problems.
after flashing TWRP i ran into the same problems like Dachtire:
SIM wasn't working.
after several reflashing attemps i eventually flashed miui_HM6Global_V9.6.4.0.OCGMIFD_fb107cc63b_8.1.zip with success.
i'm experiencing problems with OTA right now... haven't figured out what the problem is.
Click to expand...
Click to collapse
Thx are aware of this, its good information?
https://www.xda-developers.com/xiaomi-anti-rollback-protection-brick-phone/
Arround 1 minute on proses unlocking
I got device on 13 pm
Adding mi account on 13.20 pm
Ubl on 15.00 pm
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".
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.
*
*/
Features:
- Decryption Works
- Backup works
- Wipes Work
- Android 10 support
- Compatibility.zip errors fixed
- Davinciin support
- Fastboot boot supported
- Vibration have some problems
- Remember that the unofficial builds are always more updated of the official builds
- Android 11 Decryption
Download:
TWRP 3.4.0-10 Unofficial by mauronofrio
TWRP 3.4.0-0 Unofficial by mauronofrio
TWRP 3.3.1-12 Unofficial by mauronofrio
TWRP 3.3.1-11 Unofficial by mauronofrio
Official Builds
TWRP 3.3.1-8 Unofficial by mauronofrio
TWRP 3.3.1-3 Unofficial by mauronofrio
To Flash the TWRP:
if it's the first time you flash the TWRP or you are getting problems of TWRP lost or device doesn't boot after flashed magisk or something else you need to flash a script to patch your vbmeta:
VBMETA PATCHER
To flash the TWRP:
Code:
fastboot flash recovery twrp-3.3.1-xx-xxxxxx-mauronofrio.img
Then reboot in TWRP manually or using a fastboot command.
Code:
fastboot boot twrp-3.3.1-xx-xxxxxx-mauronofrio.img
or
Code:
fastboot oem reboot-recovery
Flash the VBMETA PATCHER and reboot.
REMEMBER: is important that from fastboot you directly go in TWRP mode or the TWRP will be overwritten.
Reccomended ADB and Fastboot binaries:
Adb and Fastboot Installer
Source code:
https://github.com/mauronofrio/android_bootable_recovery
https://github.com/mauronofrio/android_device_xiaomi_davinci
Using precompiled stock one
Donations:
Credits:
Created 2019-08-25
It is possible flash over last russian Twrp without wipe and format DATA?
Installed with the greek TWRP, boots perfectly (vendor and firmware: xiaomi.eu 9.8.15)
Still have to test it tho. Not sure about encryptation because my device is unencrypted.
Marlenio said:
It is possible flash over last russian Twrp without wipe and format DATA?
Click to expand...
Click to collapse
Yes yes
Schnedi said:
Not sure about encryptation because my device is unencrypted.
Click to expand...
Click to collapse
Unencrypting work well for me.
Schnedi said:
Installed with the greek TWRP, boots perfectly (vendor and firmware: xiaomi.eu 9.8.15)
Still have to test it tho. Not sure about encryptation because my device is unencrypted.
Click to expand...
Click to collapse
Why?
9.8.15 and greek TWRP encrypt perfectly, once you deal with a pin. It is no reason to live naked without encryption.
,
I'm on EEU rom V10.3.12.0.PFJEUXM.
I can install this twrp version, but after installing, the phone keeps rebooting to TWRP instead of rebooting the system.
No Idea how to solve this atm. Had this also with the Greek TWRP.
Bart1981 said:
I'm on EEU rom V10.3.12.0.PFJEUXM.
I can install this twrp version, but after installing, the phone keeps rebooting to TWRP instead of rebooting the system.
No Idea how to solve this atm. Had this also with the Greek TWRP.
Click to expand...
Click to collapse
You need to format data in TWRP then boot to recovery again then go to mount and mount internal storage then boot to system.
Aserar said:
You need to format data in TWRP then boot to recovery again then go to mount and mount internal storage then boot to system.
Click to expand...
Click to collapse
So to get tarp working properly you first need to format 'data'? That's quite f*cked up if you ask me. Is this a xiomi thing? This wasn't needed with the previous EEU xiaomi roms (and on all my previous phones/tablets).
I guess this way I'll loose all the stored apps, pictures, etc?
yep you loose everything.
Verstuurd vanaf mijn Mi 9T met Tapatalk
beaverhead said:
yep you loose everything.
Verstuurd vanaf mijn Mi 9T met Tapatalk
Click to expand...
Click to collapse
Where are the good old days you could install TWRP without loosing anything....???
if you have a backup in twrp you can transfer him to you pc. and you'r apps with titanium. the whole map of you apps also transfer it to pc. its because twrp al these troubles. my too a new xiaomi user. coming from 5t latest phone.
Verstuurd vanaf mijn Mi 9T met Tapatalk
---------- Post added at 07:52 PM ---------- Previous post was at 07:50 PM ----------
of it is because the encryption.???
Verstuurd vanaf mijn Mi 9T met Tapatalk
Since encryption ist implemented WE have to to get used to it!
Every unofficial Twrp Deals with it somehow different.
But you can Backup Data with all of them and restore.
MIUI also hast a backup function which works Well, Just Copy the Data to PC or USB Drive! Done it many Times?
Hi Dev, will you make it official in the near future or consider that?
Thanks for your time and effort in TWRP and others devices.
Bart1981 said:
So to get tarp working properly you first need to format 'data'? That's quite f*cked up if you ask me. Is this a xiomi thing? This wasn't needed with the previous EEU xiaomi roms (and on all my previous phones/tablets).
I guess this way I'll loose all the stored apps, pictures, etc?
Click to expand...
Click to collapse
Well, it's a new device without official recovery. I, even after 5 weeks of having the 9T, still haven't let go my old phone. I use it like %75 of the time. MIUI has bugs too regardless of recovery so I feel like I can't rely on it as a daily driver just yet. I'm pretty sure I won't let go of my old device until I have a good custom rom on my 9T
Guys, I really need some help because I'm not seeing what I'm missing.
I've unlocked my BL and have been on the EEA stock ROM. When trying to flash this recovery, I only got it to boot into the recovery once, where it decrypted my storage successfully, but adb didn't work for whatever reason, so I tried rebooting the recovery which sent the device into a bootloop. I tried to save the device by flashing back to a stock image and retrying flashing the recovery, but ever since I can't seem to get it to work. I'm using the regular "fastboot flash recovery" command which flashes the recovery fine, but after that I can't get into TWRP by holding vol+ & power. Since that's the same procedure I used to flash the recovery the first time, I don't see what I'm doing wrong. Anybody have an idea?
After flashing TWRP have you tried the command 'fastboot boot TWRP.img'?
Bart1981 said:
After flashing TWRP have you tried the command 'fastboot boot TWRP.img'?
Click to expand...
Click to collapse
Also sent the device into a bootloop. Actually managed to flash this TWRP again last night after flashing the Russian one first, but yet again, can't push any files to internal storage, neither by sideloading or MTP. Device does get recognized (as a K20 but w/e), but Explorer can't see its capacity and every transfer fails. I'll copy the error messages and try to get a log once I'm back home.
e: Somehow got ADB working after lots of trial & error, thanks a lot for your work OP!
Avarast
How did you do?
mauriciocardoso said:
Avarast
How did you do?
Click to expand...
Click to collapse
Assuming you're coming from stock:
1. flashed the Russian TWRP again. Booted into it, formatted the device and flashed LOS + Gapps, which worked now for the first time.
2. rebooted to fastboot and flashed OPs TWRP build. Now ADB etc worked, so I did another regular wipe, booted into system fine.
3. With a proper TWRP now flashing Magisk also went fine.
So i tried updating my phone and rerooting but as soon as i flashed the patched image something got corrupted and its only been pain now for the last few hours. Ive been super irresponsible in not backing up my phone away from the phone so I would rather not lose everything by flashing the factory image so anything and everything helps. for context it booted into 11 fine but as soon as I touched fastboot and the latest .img files is when stuff started going south.
edit: fixed the issue another way but an answer for that question would be nice to finally have on the internet.
I'm not very clear about what you did... The regular Magisk OTA process is:
1. Uninstall Magisk.
2. Install the OTA (do not reboot).
3. Install Magisk (after OTA).
The more involved process I've used (when the Magisk backup isn't valid) is:
1. Fastboot flash the vanilla boot.
2. Fastboot boot the patched boot.
3. Install the OTA (do not reboot).
4. Install Magisk (after OTA).
If you are doing a fastboot flash or boot you need to make sure the image you are using exactly matches your system. Which is especially important for the initial install. If you boot the wrong image, rebooting will fix it. If you flash the wrong image you have to flash the right image to fix it. That's why Magisk install has you fastboot boot and install from Magisk manager, less chance of a permanent issue
If you were going from Android 10 to 11 with Magisk 20, that will be a problem.
To answer the question in the title... You cannot access user data from fastboot. But you can probably fastboot boot TWRP and use that to access your data. I've done that before, but not on this phone.
Unfortunately the only build of TWRP that anyone has posted is unable to boot on Android 11 and I've not seen any other serious effort.
Assuming you were working entirely with stock ROMs, my best recovery from an unbootable state has been to reflash the stock boot.img, then boot into recovery, and apply over ADB the full downloadable OTA zip. No data wipe occurs.
I just tried to boot TWRP and it didn't work. Odd because it shouldn't depend on anything on the device... Looks like the bootloader is rejecting it
"Error verifying the received boot.img: Invalid Parameter"
a1291762 said:
I just tried to boot TWRP and it didn't work. Odd because it shouldn't depend on anything on the device... Looks like the bootloader is rejecting it
"Error verifying the received boot.img: Invalid Parameter"
Click to expand...
Click to collapse
It does depend on what's on the device because recovery is no longer its own partition. It's part of the kernel (boot.img). This unofficial TWRP was built against Android 10. And the entire partition layout changes around with the upgrade from 10-11. So it is just not valid and won't boot.
cmstlist said:
Assuming you were working entirely with stock ROMs, my best recovery from an unbootable state has been to reflash the stock boot.img, then boot into recovery, and apply over ADB the full downloadable OTA zip. No data wipe occurs.
Click to expand...
Click to collapse
I tried to access adb in stock recovery, and it didnt work. I made a new hread specific to it here.
Cant get ADB in recovery mode, but works in live mode, and so does fastboot
On my Rooted Pixel 4a, I can use: Fastboot - I flashed the latest update firmware as well as the rooted boot image ADB Over WiFi - This is the most comnon way I connect for ADB ADB While the Android OS is running What I cannoit get woirking is...
forum.xda-developers.com
Can you see what I a doing differently or have missed that made it work for you?
on a side note...
cmstlist said:
Unfortunately the only build of TWRP that anyone has posted is unable to boot on Android 11 and I've not seen any other serious effort.
Click to expand...
Click to collapse
I have built TWRP for one of my previous devices, and i am not sure why no one has built one for A11, for our device; but i can think of a couple of reasons. Right now i have a major sprain In my right wrist/hand, so typing is one handed, and its not my dominate hand. Even if i got it to build, i would be looking for test pilots.
DiamondJohn said:
...snip...
on a side note...
I have built TWRP for one of my previous devices, and i am not sure why no one has built one for A11, for our device; but i can think of a couple of reasons. Right now i have a major sprain In my right wrist/hand, so typing is one handed, and its not my dominate hand. Even if i got it to build, i would be looking for test pilots.
Click to expand...
Click to collapse
just came across this post, which may help explain why TWRP is problematic for our device. But the thread did hint about running twrp from fastboot. (Post by cmstlist)
TWRP 3.7.0-12 for Sunfish[Testing]
[RECOVERY] TWRP 3.7.0-12 - TeamWin Recovery Project Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and...
forum.xda-developers.com
DiamondJohn said:
I have built TWRP for one of my previous devices, and i am not sure why no one has built one for A11, for our device; but i can think of a couple of reasons. Right now i have a major sprain In my right wrist/hand, so typing is one handed, and its not my dominate hand. Even if i got it to build, i would be looking for test pilots.
Click to expand...
Click to collapse
As a software developer that's been doing embedded Linux for 20 years, it saddens me that I haven't got past app development for Android
I'd love to help get TWRP going for the Pixel 4a but probably I'd get nowhere. I can certainly test TWRP builds though. My Pixel 4a is my daily driver but it's unlocked and rooted and I've got a solid off-device backup so I'm relatively fearless with hacking
DiamondJohn said:
I tried to access adb in stock recovery, and it didnt work. I made a new hread specific to it here.
Click to expand...
Click to collapse
I was not saying you can execute arbitrary ADB commands in stock recovery. However if you have a full OTA zip and can get into stock recovery, you can choose the option on-device to flash an update over ADB according to Google's instructions. This will only work with a signed official OTA zip. But if you happen to have corrupted your stock ROM to an unbootable state, it is a possible path to get it back to bootable so you can access the contents.
Unsure if this is the place since its also related to TWRP 3.7, any help is appreicated
Got stuck in a weird situation and wondering if anyone has ideas.
Current State:
Slot_A on OOS 11, can boot TWRP via Fastboot
Slot_B on OOS 12, can only boot into Fastboot
Originally on OOS 11, booted TWRP and made backups of all partitions (data, boot, system image, vendor image, etc.). Forgot to move this to computer so this is all still stored on device.
Proceeded with OOS 12 upgrade (into Slot B). Patched magisk, rebooted, then flashed TWRP 3.7 (FBEv1), direct installed magisk, rebooted. - Everything was functional, but decided to go back to OOS 11.
Thinking I could just use the TWRP backup made on OOS 11, I did the following:
Booted into 3.7 TWRP
Restored the backup for boot, system image, and vendor image
Set active slot to Slot A and reboot
It doesn't allow me to boot into the OS (Presumably because the data was re-encrypted for OOS 12?)
Set active-slot=b and reboot, but it's locked to fastboot.
I've attempted a few things, but I can't boot back into OOS. I would prefer to retrieve my TWRP backups first before doing an MSM reset.
When on Slot_A (older), I can only boot into TWRP 3.6.2 and 3.7. I'm guessing 3.6.2 can't decrypt since it's only configured for A11 and under, but not sure why 3.7 can't decrypt my data.
- It doesn't even ask for pin when TWRP launches; maybe it's reading the System for Slot_A and thinks i'm still on A11?
- running `twrp decrypt {pin}` doesn't seem to work. Unsure if there's something done to my lockscreen pin to be used as the encryption key/password?
When on Slot_A, attempting to boot into either the system or TWRP hangs.
Things I've tried:
Flashing A11 boot.img and magisk-patched boot.img to Slot_A -> Hangs on 1+ Spinning dots
Flashing A12 boot.img and magisk-patched boot.img to Slot_B -> Hangs on 1+ logo (Does show up on ADB though)
Booting Slot_B into TWRP 3.6.2 (Official, and Nebrassy unofficial for A12) and TWRP 3.7 -> Gets stuck on "Fastboot Mode" screen (fastboot cli still responds) or Hangs on snapdragon logo
Edit: Ended up using MSM. Needed device for work
I have a similiar problem to flash twrp to my phone ,
each time i try i get a fastboot loop too and i have to reset/unbrick it with the msm tool back to android 11
i use the OnePlus_7_Pro_Global_OxygenOS_11.0.5.1 package to unbrick the phone , i dont know how long and often i tried now to get twrp to work so that i can flash a custom fw ... i want root and a android 13 based cfw but i dont get it to work :/
I got it working with crdroid. heres some stuff
guacamole - Google Drive
drive.google.com
be carefull
¯\_(ツ)_/¯
------------------------------------
I got stable and decrypted fs RW working on crdroid 9.1 firmware other than some weird bugs
i put it in the 2023-twrp
MissAnthropin said:
I have a similiar problem to flash twrp to my phone ,
each time i try i get a fastboot loop too and i have to reset/unbrick it with the msm tool back to android 11
i use the OnePlus_7_Pro_Global_OxygenOS_11.0.5.1 package to unbrick the phone , i dont know how long and often i tried now to get twrp to work so that i can flash a custom fw ... i want root and a android 13 based cfw but i dont get it to work :/
Click to expand...
Click to collapse
I have the exact same problem! Have you found a fix yet? This seems to happen when I try to install Android 13 based roms, and when I install a rom like Lineage OS, using their recovery, it works just fine.
No, and I don't know why, maybe i do something wrong or it is the Modell that make this trouble.
I thinking to sell my OP7PRO and buy another one ( and then I have the same problem with the new phone )
No no let the jokes aside, it must work, i mailed with OnePlus Support Germany but they only helped me to install A11 w/root and recovery, i thought ok now I can update to A13 so I loaded A13, unpacked the boot.img, Patched the boot.img
Installed A13 w/out errors, rebooted - Fastboot loop
RIP
Started ranting instead
TWRP for guacamole development seems to be fairly scarce, last working recovery I tried was when they started using fastboot boot to enter it. It was pretty hacky even then, currently it seems that nebrassy is the maintainer for twrp for guacamole.
Github: https://github.com/nebrassy Android 12 thread: https://forum.xda-developers.com/t/recovery-12-official-teamwin-recovery-project.4269551/ Nebrassys Telegram has helpful info as well: https://t.me/NSSFB
last update I found was 2022:10:2 - https://www.pling.com/s/Phones/p/1835156
after a few days of torture I read a thread on here saying if you flashed twrp via magisk like you would if it was a magisk moule it would work normally. It worked on my device so I assume that its universal. I have filled my computer with guacamole related files Im uploading here before im forced to reinstall my os:
guacamole - Google Drive
drive.google.com
Just a fyi from what I have gathered from my experience you can get a stable twrp recovery with persistant / read write access and disabled encryption and basically use it with little error up until you try flashing a newer custom rom. My guess is when flashing a cfw the bootloader gets rewritten causing our boot image to become corrupted. Flashing twrp over / booting to twrp via fastboot or trying to install it via another custom recovery causes boot / recovery failures... meaning you cant really use it for flashing custom roms. I cant find the post with the install instructions I seen that helped me so here is what I think it was,
Found it: https://forum.xda-developers.com/t/how-to-make-twrp-work-in-your-stock-a12.4522667/#post-87985325
~ I have bricked this device constantly while ****ing around so unless youre prepared to go to war with the ****er, Id quit messing with it.
MSM flashing with windows is the only way to recover from the void.
Click to expand...
Click to collapse
using Linux systems for EDL is a bit more difficult to figure out but can be done > EDL https://github.com/bkerler/edl/blob/master/edl | https://github.com/andersson/qdl
Click to expand...
Click to collapse
~If you do brick I created a fastboot flashable A13 Oxygen os recovery rom and uploaded it to my google drive found under recovery_brick_fastboot.zip ~
Click to expand...
Click to collapse
lastly be mindful of a/b partition configuration or youll find yourself lost or bricked
Installation:
1. Obviously unlock the bootloader - OEM Unlock
2. Flash custom recovery (lineage/crdroid/etc)
3. (Personally I root here and again on the active slot so) flash magisk.zip
4. Reboot into installed ROM and install magisk android app and complete setup, reboot system
5. (another thing I like to do before flashing twrp) setup magisk enable all the basic options like prophide, deny list then set root userspace option to global.
6. Flash TWRP .zip (https://dl.twrp.me/guacamolev2/twrp-installer-3.7.0_12-0-guacamolev2.zip) via magisk
Alright! After all that you should be able to reboot into recovery via adb reboot recovery / fastboot or power menu and you find a working twrp recovery installed.
If you need help or want to **** around with the device you can @ me anytime and ill do my best to halp
2600 IRC (cornelius.scuttled.net >Nick captain >channel #guac)
Telegram https://t.me/+pxvpKToFo6pkMGYx
Discord https://discord.gg/MhvWgEfY
Pics
RolandStoner said:
Pics
Click to expand...
Click to collapse
You Confussing me a lot with your Posts before ...
i´m unsure what you mean exactly,
my bootloader is unlocked, with magisk i got a working root but after that i fail
what you mean with flash twrp with magisk ?
after unlocking the bootloader and get root, i tryd to flash twrp like before on other devices but that seems not working because i get then the fastboot loop
on another thread i found here on xda too, the guy wrote dont forget to activate the fastboot loop fix in the advanced options
but i not tried it yet again , so what should i do now ?
for now , i´m back on android11 , with stock oxygen os firmware
i have to do now the things like i did before again , unpack boot.img from the firmware that is installed on the device
patch it with magisk, flash it with "fastboot flash boot boot-patched.img" or is this step senseless ?
i mean you only wrote unlock bootloader and flash a cfw , but i don´t have a chance to flash a custom fw without a custom recovery ??
my recovery on my op7pro have no options for "install zip" or something else
addendum:
like i said you confused me a lot
addendum two:
or i do what i said before .. i sell my op7pro and buy me a one where i havent so much trouble installing twrp and root
i never had a phone before that made so much trouble in installing simple twrp ...
but i don´t found a phone yet that is compatible with kali and the pentest tools or wardriving tools like the oneplus , so i have a problem ,... i think i should drink now my selfmade blackberry liquor ( or blackberry booze ? ) and let the smartphone be a smartphone for now and power off my brain for a while
Yes, you need to patch your boot image via magisk and flash it with fastboot.
After you let magisk do its first time setup and then once it reboots you go to Magisk > Modules and flash the twrp recovery .zip file you got from twrp. link:https://twrp.me/oneplus/oneplus7pro.html just like you would if it was a magisk module.
the password for twrp decryption is your pin. Here are simpler instructions
https://forum.xda-developers.com/t/how-to-make-twrp-work-in-your-stock-a12.4522667/#post-87985325
****... I forgot a step.
after flashing twrp as a module in magisk you dont reboot, you go back to the main screen hit the install button and choose direct install
Now I understand it more, i had before rooted the phone successful with magisk, but then I made a wrong decision and booted into Fastboot and flashed TWRP in Fastboot Mode as I did it before with all my Smarties i had before, coz those way with Fastboot worked before all the time so I never thought that this is the error in the procedure
I give the twrp flashing with magisk a try.
Thx for the help
MissAnthropin said:
Now I understand it more, i had before rooted the phone successful with magisk, but then I made a wrong decision and booted into Fastboot and flashed TWRP in Fastboot Mode as I did it before with all my Smarties i had before, coz those way with Fastboot worked before all the time so I never thought that this is the error in the procedure
I give the twrp flashing with magisk a try.
Thx for the help
Click to expand...
Click to collapse
Thank @yassine2217 because I would never have done so either.... Still many bugs but twrp is twrp