Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy S23 Ultra

Development [RECOVERY][UNOFFICIAL] TWRP for Galaxy S23 Ultra - Samsung Galaxy S23 Ultra

Changelog:
GitHub History

mine

afaneh92 said:
Bugs:
- Encryption not fully working.
- No erofs r/w support yet.
Click to expand...
Click to collapse
Data decrypt support should be mandatory for this device expecially with the newer A13 EROFS partitions, please consider adding it.

BlackMesa123 said:
Data decrypt support should be mandatory for this device expecially with the newer A13 EROFS partitions, please consider adding it.
Click to expand...
Click to collapse
I tried on S20+ and S22 ultra it was harder than A series. But will try again when the device delivered, I may ask for your help. Thanks.

afaneh92 said:
I tried on S20+ and S22 ultra it was harder than A series. But will try again when the device delivered, I may ask for your help. Thanks.
Click to expand...
Click to collapse
Implementing crypto support is not that hard as it seems, in the S23 family it should even be easier since you can just implement the official TeamWin QSEE scripts in your device tree. I imagine the big deal on S20/S22 is due to those device having an Exynos SoC with TEEgris TZ, but even in that case it should be easy to handle. What I'm more afraid of is that this device probably has Knox SDP in vold so decrypt with PIN/password set won't work, but it's better than nothing atm.

BlackMesa123 said:
Implementing crypto support is not that hard as it seems, in the S23 family it should even be easier since you can just implement the official TeamWin QSEE scripts in your device tree. I imagine the big deal on S20/S22 is due to those device having an Exynos SoC with TEEgris TZ, but even in that case it should be easy to handle. What I'm more afraid of is that this device probably has Knox SDP in vold so decrypt with PIN/password set won't work, but it's better than nothing atm.
Click to expand...
Click to collapse
I was referring to snapdragon, and never worked. I used your implementation and device wasn't able to decrypt data. S22 was harder since data wasn't able to mount. I will wait for device, thanks again.

afaneh92 said:
I was referring to snapdragon, and never worked. I used your implementation and device wasn't able to decrypt data. S22 was harder since data wasn't able to mount. I will wait for device, thanks again.
Click to expand...
Click to collapse
We can surely work it out to fix it

@afaneh92 it looks like S23 vold has no crap A11 code leftovers which does break decrypt with PIN/password on TWRP, I compared the vold bin with my A52s' one and certain stuff is clearly missing. So it might just work out of the box once support for it gets added

BlackMesa123 said:
@afaneh92 it looks like S23 vold has no crap A11 code leftovers which does break decrypt with PIN/password on TWRP, I compared the vold bin with my A52s' one and certain stuff is clearly missing. So it might just work out of the box once support for it gets added
Click to expand...
Click to collapse
I hope so.

Nice work!

I followed the steps above, and when trying to reboot to system I get back to to twrp. Help please?

I just want to ask if anyone has tried installing viper4android yet and does it work? If it's like the s22 ultra and doesn't work. I might sound crazy but I wouldn't buy it. Music is more important to me then spen and camera although admittedly they are good to. It's mind blowing to think 1200 dollar won't sound as good as my Poco f3 or even my lg tribute 10 years ago.

lcd047 said:
I followed the steps above, and when trying to reboot to system I get back to to twrp. Help please?
Click to expand...
Click to collapse
I have exactly the same:
- after following all steps one by one there is only a reboot into TWRP itself possible
I compared the steps from this thread with the steps which are successfully working on my Galaxy Tab S8 Ultra ( https://forum.xda-developers.com/t/...-for-galaxy-tab-s8-series-snapdragon.4455491/ ) and I see a difference at step 7:
7. Flash custom kernel and magisk apk in twrp.
Click to expand...
Click to collapse
I do not see any "custom kernel" to download in this thread (at least for now) so I think this is the missing part. Or it only works correct in combination with "dr.ketans rom" (which I do not want to use for now).
@afaneh92: Thank you very much for your work (on "root" and also with "twrp")!
Edit: I just read the installation pdf from "dr. ketans rom". There is written in red letters:
DON'T run multidisabler from TWRP termial/zip or any system-rw script after flashing ROM else device won't boot.
Click to expand...
Click to collapse
So maybe the not booting system is related to the work which the "multidisabler" should do.
I will be happy if there will be some light regarding the non booting system after flashing TWRP.
Maybe I will give "dr. ketans rom" a try and have an eye on this thread how the things go on.
________________________________________
@Techguy777: This is very offtopic but I am with you that "Viper4Android" is a very important part also of my daily used tools. I just have found a (for me) good running workaround.
Search the fDroid store for the app "RootlessJamesDSP". Depending on which parts of "Viper4Android" you care about, the app is an extremely good working replacement. In my example, the "Convolver" with the impulse response files are important and that works wonderfully with the players I use.

hurray said:
I will go back for now to (rooted) stock ROM and Recovery and will have a look how this thread will go on.
Click to expand...
Click to collapse
Sadly flashing "dr.ketans rom" (or the "unroot" one, for that matter) doesn't fix the problem for me. Ironically everything was working fine with "dr.ketans rom" alone, but I just had to try disabling encryption. Well I suppose better is the enemy of good.

lcd047 said:
Sadly flashing "dr.ketans rom" (or the "unroot" one, for that matter) doesn't fix the problem for me. Ironically everything was working fine with "dr.ketans rom" alone, but I just had to try disabling encryption. Well I suppose better is the enemy of good.
Click to expand...
Click to collapse
I just flashed the orginal FW from samfw.com and my S23 Ultra is booting correctly into the system. Now I will try the current "S918B_WA6_DrKetan_ROM_T02". It seems that TWRP is build in into the ROM. If this works I will try a backup & restore of user data (this is the most important part from TWRP for me).

hurray said:
I just flashed the orginal FW from samfw.com and my S23 Ultra is booting correctly into the system. Now I will try the current "S918B_WA6_DrKetan_ROM_T02". It seems that TWRP is build in into the ROM. If this works I will try a backup & restore of user data (this is the most important part from TWRP for me).
Click to expand...
Click to collapse
After flashing my ROM + Format dara (Read changelog) TWRP backup/restore data should work as expected. And for that purpose mentioned in OP

dr.ketan said:
After flashing my ROM + Format dara (Read changelog) TWRP backup/restore data should work as expected. And for that purpose mentioned in OP
Click to expand...
Click to collapse
Yup, flashing the full ROM works. Many thanks, and keep up the amazing work!

dr.ketan said:
After flashing my ROM + Format dara (Read changelog) TWRP backup/restore data should work as expected. And for that purpose mentioned in OP
Click to expand...
Click to collapse
You have convinced me of your ROM. After flashing I had to reformat "data" but afterwards the system booted correctly.
The ROM works very well so far and the additional functions via "ROM Tools S23" are also good (especially that they can be selectively enabled and disabled).
Backup and recovery of user data has also worked flawlessly.
So now I can start with the actual setup of all apps.
Thanks a lot for your work!

hurray said:
You have convinced me of your ROM. After flashing I had to reformat "data" but afterwards the system booted correctly.
The ROM works very well so far and the additional functions via "ROM Tools S23" are also good (especially that they can be selectively enabled and disabled).
Backup and recovery of user data has also worked flawlessly.
So now I can start with the actual setup of all apps.
Thanks a lot for your work!
Click to expand...
Click to collapse
I have seen many users don't want "custom" roms, but my ROM will have complete stock look + single click all critical fix. It won't force users to use customised look. Also it have more options to make modifications in ui but everything will be by user's will.

Related

[Recovery][TWRP] TWRP 2.8.7.0 for LG L7 2

TWRP Recovery 2.8.6.0 for LG L7II
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or any other damage made to your device. Please
* do some research if you have any concerns about features included in this
* RECOVERY 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.
*/
In this thread you can find:
Post#1:
1. Presentation
2. Changelog
3. Known bugs + fixes
Post#2:
1. Flashing instruction
2. Thanks
3. Donator Hall of Fame
4. Download links
Post#3:
1. Tutorial on how to make ADB work on windows (with or without MTP)
2. Images of the recovery
1. Presentation:
TeamWin Recovery Project – or TWRP for short – is a fully touch-based custom recovery that was initially developed for Nexus devices, but has since been made available for countless other smartphones and tablets as well, in form of both official and third-party builds.
2. Changelog:
Code:
[U]07.08.2015 - Twrp 2.8.7.0[/U]
Updated to latest Twrp
Added IMEI back-up
[U]12.06.2015 - Twrp 2.8.6.0[/U]
Settings storage is by default External SD
Ext-sd will not be wiped on factory reset (even if the text says so; ignore it)
You have all 3 partitions (internal, external, ext-sd) in MTP now
Updated to latest TWRP 2.8.6.0 source
[U]06.01.2015 - Stable2[/U]
improved code a little
disabled things that are not used
reduced maximum brightness
added Qcom time fix
NEW: added support for sd-ext (2nd partition on sdcard)
[U]02.01.2015 - Working Internal[/U]
Read the warnings (in RED) in the 2nd post.
Internal storage is working now xD
[U]25.12.2014 - Updated to latest TWRP 2.8.3.0[/U]
[U]19.11.2014 - Final release[/U]
- bugs: none
Aroma Fm inverted is not because of recovery.
Not mounting internal is not because of recovery and will not be added because you can mess up your data partition losing all data (our internal is in data/media)
We have full working brightness and screen timeout
[U]10.11.2014 - Beta 1[/U]
- bugs:
after entering screen timeout mode the led backlight won't turn on again
- fixed bugs:
messed up display
flipped screen
unresponsive touch screen
partition problems
[U]09.11.2014 - Closed Alpha 2 - No public download[/U]
- bugs:
flipped screen
unresponsive touch screen
partition problems
after entering screen timeout mode the led backlight won't turn on again
- fixed bugs:
messed up display
[U]05.11.2014 - Closed Alpha 1 - No public download[/U]
- first release
- bugs:
messed up display
flipped screen
unresponsive touch screen
partition problems
after entering screen timeout mode the led backlight won't turn on again
3. Known bugs:
NONE!

1. Flashing instruction:
METHOD 1:
*OUTDATED: Just open the zip from last version and copy that recovery.img if you want to use this.
Copy the "recovery.img" from download to the root of the SD card.
Code:
1. With terminal emulator or using adb do this:
2. adb shell
3. su
4. dd if=/storage/external_SD/recovery.img of=/dev/block/mmcblk0p17
METHOD 2:
Download the version you like (the zip) and flash it in any recovery.
VERY IMPORTANT: EVERYTIME YOU FLASH TWRP AGAIN GO TO SETTINGS AND RESET DEFAULTS.
THE DEFAULT STORAGE MIGHT BE INTERNAL STORAGE PRESS ON THE PLACE THAT SAYS STORAGE: INTERNAL STORAGE AND CHANGE TO EXTERNAL STORAGE IF YOU WANT TO USE THAT (TWRP will remember the choice).
IF WINDOWS RECOGNIZES THE INTERNAL STORAGE IT WILL TRY TO FORMAT IT TO USE IT (this is because of the ext4 extention). DO NOT FORMAT OR YOU LOSE YOUR INTERNAL STORAGE DATA. LINUX DOESN'T HAVE ANY PROBLEM.
2. Thanks:
All Omni and TWRP team.
@Dees_Troy
The IRC channel for TWRP.
3. Donator Hall of Fame:
@vlmaxx - huge thank you man! ^.^
4. Download link:
TWRP_2.8.7.0_L7II.zip
Old:
TWRP_2.8.6.0_L7II.zip
Any kind of mirroring, repacking, uploading this files or files that come from this files on other websites/forums is not allowed. If you want guys on other forums to get this, give them the link to this. Thanks. Please respect my work and do not reupload this files.

How to make ADB to work on Windows:
adb-setup-1.4.2.exe: http://tinyurl.com/qca8abd
LG Drivers: http://tinyurl.com/l3mgf49
1. Delete all LG Drivers you have and all related to LG (Pc suite or anything else) and restart PC.
2. Install the LG Drivers from the rar and also the installer for ADB answering Y, Y, Y and follow the on screen driver installer.
3. Get in recovery and go under Mount and disable MTP if it is enabled. Connect USB. You will get this. Open device manager and you will find that our pictures are alike.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Right click the yellow triangle icon and right-click it choosing Update Driver Software. You get this.
5. Click the down option. You get this.
6. Click the Let me pick from a list option. You get this.
7. Select ADB Interface and press Next. You get this.
8. Scroll down selecting the LGE Mobile Adb. Press Next. You get this.
9. Press Yes and then Close and you are done.
Proof working recognized with MTP off in Recovery and Sideload and last picture with MTP on (recognizing the sdcard).
Hit thanks please if this helped you. Have a nice day.

Good job I will test this in the night
P.S. I can install this on cwm??

sirion123 said:
Good job I will test this in the night
P.S. I can install this on cwm??
Click to expand...
Click to collapse
Hmm maybe if i make a flashable zip though I have seen ppl prefere to flash it via fastboot. We don't have fastboot so just flash it like i said. It's easy ^.^..
EDIT: NVM made the cwm flashable zip.

Ok. Maybe I'll wait for the others and then install

sirion123 said:
Ok. Maybe I'll wait for the others and then install
Click to expand...
Click to collapse
Just flash that with CWM it's safe it won't destroy your data or system will catch on fire it is tried on my own device.

I install this and this is very good work! But when I reboot to system screen flipped at the moment. I found this one bug

sirion123 said:
I install this and this is very good work! But when I reboot to system screen flipped at the moment. I found this one bug
Click to expand...
Click to collapse
If you like it press the THANKS BUTTON that is in the bottom right of the post. I know about this bug it is normal and it's not really a bug blame lg ^.^. badly mounted screen for this models. This bug won't interfere with anything ^.^ You can see it just when you close the recovery.

Excellent job! It's works on P713 KK CIS!
Themes are applied successfully!
The option "Disable MTP" disables ADB mode too. - SOLVED!
UMS mode for external SD is not supported.
AROMA FM still inverted.
We are waiting for the final version and fixes! Good luck!

Thx, sir. Its work on my LG P713 (4.1.2)

the_vanya1 said:
Thx, sir. Its work on my LG P713 (4.1.2)
Click to expand...
Click to collapse
You are very welcome my friend. Giving back the work haha. Respect to you when i was on 4.1.2 I used your custom rom. EPIC. Respect.

And recovery is perfectly compatible with nandroid manager...

maxx_hr said:
And recovery is perfectly compatible with nandroid manager...
Click to expand...
Click to collapse
Thanks for letting people know.

TWRP Recovery
christi9503 said:
Thanks for letting people know.
Click to expand...
Click to collapse
Please tell me whether it is possible to install on the LG P715 Dual.

vlmaxx said:
Please tell me whether it is possible to install on the LG P715 Dual.
Click to expand...
Click to collapse
Not tested on P715 but it should work. 99,9% it will work my friend. Also no chance you will manage to hard brick it just by flashing. I did not include preloader and bootloader partitions. At most a soft brick but not even that. Just flash it.
EDIT: @vlmaxx Report after flashing please. But for sure it will boot.

TWRP
christi9503 said:
Not tested on P715 but it should work. 99,9% it will work my friend. Also no chance you will manage to hard brick it just by flashing. I did not include preloader and bootloader partitions. At most a soft brick but not even that. Just flash it.
EDIT: @vlmaxx Report after flashing please. But for sure it will boot.
Click to expand...
Click to collapse
Ok. I will try tomorrow to try. Then I will unsubscribe.

TWRP
christi9503 said:
Not tested on P715 but it should work. 99,9% it will work my friend. Also no chance you will manage to hard brick it just by flashing. I did not include preloader and bootloader partitions. At most a soft brick but not even that. Just flash it.
EDIT: @vlmaxx Report after flashing please. But for sure it will boot.
Click to expand...
Click to collapse
Sorry, I'm not good at English. Lost your message, so I answer here.
Sew through CWM Recovery. Starts but tach screen almost does not work or is not adequate. Reacts only INSTALL and offers mount, and then nothing can be done. Rollback on old CWM.
Forgot to specify: I have 4.1.2. Maybe that's why is not working?

vlmaxx said:
Sorry, I'm not good at English. Lost your message, so I answer here.
Sew through CWM Recovery. Starts but tach screen almost does not work or is not adequate. Reacts only INSTALL and offers mount, and then nothing can be done. Rollback on old CWM.
Forgot to specify: I have 4.1.2. Maybe that's why is not working?
Click to expand...
Click to collapse
Nope that is not the case. Think it's the touch drivers can be different or smth. Please make a video place on youtube. I'll make a different build with p715 kernel.

TWRP
christi9503 said:
Nope that is not the case. Think it's the touch drivers can be different or smth. Please make a video place on youtube. I'll make a different build with p715 kernel.
Click to expand...
Click to collapse
Sorry, but it's all too complicated for me. Years and brains are not the same .... unfortunately. In any case, thank you very much for your help.

[SM-T580][SM-T585][UNOFFICIAL] 20180906 Treble Project 64Bits

I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
As we all know - the tablet does not support treble. And we do not have a separate /vendor partition, i'm using /cache as /vendor.
Instructions
1. flash my twrp from link above - this is latest twrp with system_image support, it need to restore system treble images
2. download system image from https://forum.xda-developers.com/project-treble/trebleenabled-device-development
Known Issues
1. rotate sensor working, but strange - on rotate tablet show black screen for a moment and then back to normal in right state
2. SM-T580 only: gps
Links
Treble images
SM-T585:
1. 20180827: initial treble: https://drive.google.com/file/d/1uX5JYqLCTMPpT5Zx2Wvi0U-Ms49S0YrW/view?usp=sharing
2. 20180904: camera recording in oreo images, both sdcards in pie images: https://drive.google.com/file/d/1cTEXJb9n5oZad0O3DXT5nlEhnlBDP6QB/view?usp=sharing
3, 20180906: remove shim for mediaserver - only for pie!!!: https://drive.google.com/file/d/1C0MfHt0SNYL4hD-BtOj3i7O_qBBPD25t/view?usp=sharing
SM-T580:
1. 20180828: initial treble: https://drive.google.com/file/d/1sgB1xQjRWyGM1OfF73Yhl5vRNunP04iK/view?usp=sharing
2. 20180904: camera recording in oreo images, both sdcards in pie images: https://drive.google.com/file/d/13WL9_Q_WoStf0WVHbmoYaL2CHbCluzNO/view?usp=sharing
3, 20180906: remove shim for mediaserver - only for pie!!!: https://drive.google.com/file/d/15dN2DugPBjhi_m0SOy4qYwVmR03nyY69/view?usp=sharing
Root
Use Magisk, it's should work. If during install Magisk give error about missed /vendor, run my prepare script and the install Magisk: https://drive.google.com/file/d/10JnOtyF5Y_4q1OE3FOZYPDcR7TK1jRhA/view?usp=sharing
GApps - Pie only!!!
Right now on T580\T585 pie images with gapps dnw, it's stuck on the start wizard, what is strange.
Solution: flash image without gapps and then flash gapps. It's working. I'm playing right now with aosp 9.0 and gapps.
We have 32bit recovery and right now standalone gapps think about arm and 6.0.1 version, what is wrong. I took gapps from https://forum.xda-developers.com/android/development/gapps-unofficial-opengapps-builds-t3828141 and fix script inside to arm64 and right sdk version, this is gapps with my fix, what should work on T580\T585: https://drive.google.com/file/d/1kkHUPSznfibcER0DV89GhDdepEjqjCl9/view?usp=sharing
How install gapps:
1. install treble image, then pie system image
2. boot to system
3. restart to twrp and install gapps
4. boot to system, go to play market and login
For now working only this sequence
Recovery
SM-t585:
1. twrp-3.2.3-0: https://drive.google.com/file/d/16D-sFDt41n-wxNu1A0q01oRRKiZ-AsfF/view?usp=sharing
SM-T580:
1. this is original twrp (from https://dl.twrp.me/gtaxlwifi/twrp-3.2.3-0-gtaxlwifi.img.html), I just added system_image support and repack: https://drive.google.com/file/d/10LgZ1rabkgVSyIyd38BxIxNr22_9PJY5/view?usp=sharing
All firmware say about wrong vendor version. This is normal, just press OK.
System images:A only and 64Bits
Checked firmwares
Almost all oreo roms from treble's thread working.
Even new Android 9.0 Pie roms working, but it has issue with sdcard, it will require additional checks from me.
Installation
1. (optional): "Wipe\Format Data": type yes and press ok
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. wipe data: "Wipe\Advanced Wipe" and select "Dalvik/ARP Cache" / "Data" / "Internal Storage" / "System" / "Cache"
3. install treble: "Install", then navigate to lineage-15.1-20180827-treble.zip and "Swipe to confirm Flash"
4. install system: "Install", then press "Install Image" then navigate to system images, then select "System Image" and "Swipe to confirm Flash"
5. reboot
let's experiment together!

Valera1978 said:
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
If you want to check firmware - please make backup. Better to store all partitions, at least efs and may be modem.
As we all know - the tablet does not support treble. And we do not have a separate /vendor partition, i'm using /cache as /vendor.
Instructions
1. go to the current twrp and full wipe
2. flash my twrp - this is latest twrp with system_image support, it need to restore system treble images (twrp-3.2.3-0-gtaxlltexx.img): https://drive.google.com/file/d/16D-sFDt41n-wxNu1A0q01oRRKiZ-AsfF/view?usp=sharing
3. flash zip with vendor data and boot image (lineage-15.1-20180827-treble.zip): https://drive.google.com/file/d/1uX5JYqLCTMPpT5Zx2Wvi0U-Ms49S0YrW/view?usp=sharing
4. now you device is ready to flash any treble system image from: https://forum.xda-developers.com/project-treble/trebleenabled-device-development - download img, copy to sdcard and then flash as system image in twrp
5. if you wanna check another rom, just make 1-4 again
Known Issues
1. video-recording
2. rotate sensor working, but strange - on rotate tablet show black screen for a moment and then back to normal in right state
All firmware say about wrong vendor version. This is normal, just press OK.
System A only
Checked firmwares
Almost all oreo roms from treble's thread working.
Even new Android 9.0 Pie roms working, but it has issue with sdcard, it will require additional checks from me.
let's experiment together!
Click to expand...
Click to collapse
You are amazing dude thanks so much for releasing this to us. Keep up the great work.

Wow, can you Do the same for the WiFi Version SM-T580?

This is by far the best news for our device. I am wondering if when we'll get official Oreo, Samsung will provide us with a treble rom as well.
Thanks Valera for you support.

I get "No OS installed"

Wow. Good job, my friend! I already want to try it on T580 wifi version. I remember that the roms of t585 work in the wifi version, can you flash this without problems?
Many cravings
Thank you!

paulo boë said:
I get "No OS installed"
Click to expand...
Click to collapse
just ignore this error. look like twrp not quite correctly handle the situation with restore via system_image and think that there is no system.

alanloax said:
Wow. Good job, my friend! I already want to try it on T580 wifi version. I remember that the roms of t585 work in the wifi version, can you flash this without problems?
Many cravings
Thank you!
Click to expand...
Click to collapse
I can build version for t580, the kernel and almost all stuff is not a problem, question only in the gps. In the t585 it's connect to the ril, but t580 using own gps chip. I don't know, where I can get 64bit binary for it. In case of t585 i'm using proprietary bin\libs from a5'17. Need to check, can I use 32bit gps in 64bit system.
And may be can be a problems (not sure now) - all treble's images created for phones. tablet with lte is close to phone, but not a witi version. but in any way - it's need to check.

Valera1978 said:
I can build version for t580, the kernel and almost all stuff is not a problem, question only in the gps. In the t585 it's connect to the ril, but t580 using own gps chip. I don't know, where I can get 64bit binary for it. In case of t585 i'm using proprietary bin\libs from a5'17. Need to check, can I use 32bit gps in 64bit system.
And may be can be a problems (not sure now) - all treble's images created for phones. tablet with lte is close to phone, but not a witi version. but in any way - it's need to check.
Click to expand...
Click to collapse
Oh I understand. Luckily I use little the gps. At least to try haha.
Thank you very much again for contributing to these devices, very good work!

Valera1978 said:
just ignore this error. look like twrp not quite correctly handle the situation with restore via system_image and think that there is no system.
Click to expand...
Click to collapse
And still it reboots over and over. The Galaxy Tab logo, then 6 7 secs black screen and the the Galaxy tab logo again.

paulo boë said:
And still it reboots over and over. The Galaxy Tab logo, then 6 7 secs black screen and the the Galaxy tab logo again.
Click to expand...
Click to collapse
Did you flashed anything other than rom? Magisk, gapps?

EugenStanis said:
Did you flashed anything other than rom? Magisk, gapps?
Click to expand...
Click to collapse
Nope, but I kinda forgot to mention that I use it on the T580

Hey, very good job. Please make a 580 version, GPS doesn't matter. You said it was experimental.

paulo boë said:
Nope, but I kinda forgot to mention that I use it on the T580
Click to expand...
Click to collapse
It's cannt work on T580 right now, because treble require changes in DTB. Without DTB changes system cann't mount /cache as /vendor and you will get boot before animation.
Will try build T580 today.

Please someone check version for T580

Valera1978 said:
Please someone check version for T580
Click to expand...
Click to collapse
And the twrp for t580? Cuz when I flash I get "this is for wifi this is lte"
Also can you post some screenshots with a link to the treble rom that works?

paulo boë said:
And the twrp for t580? Cuz when I flash I get "this is for wifi this is lte"
Click to expand...
Click to collapse
are your right now on twrp for lte? In this case in the gtaxlwifi-20180828-treble.zip - go to "\META-INF\com\google\android\updater-script" and remove first line with assert
Or you can use my twrp repack for t580: https://drive.google.com/file/d/10LgZ1rabkgVSyIyd38BxIxNr22_9PJY5/view?usp=sharing
this is original 3.23 version, I added only system-image

Valera1978 said:
are your right now on twrp for lte? In this case in the gtaxlwifi-20180828-treble.zip - go to "\META-INF\com\google\android\updater-script" and remove first line with assert
Or you can use my twrp repack for t580: https://drive.google.com/file/d/10LgZ1rabkgVSyIyd38BxIxNr22_9PJY5/view?usp=sharing
this is original 3.23 version, I added only system-image
Click to expand...
Click to collapse
I flashed it. Tried to flash a img, but still reboots back into galaxy logo

paulo boë said:
I flashed it. Tried to flash a img, but still reboots back into galaxy logo
Click to expand...
Click to collapse
can you send me /data/tombstones and /proc/last_kmsg?

SM-T285YD
Hi,
I have twrp for SM-T285YD but I cannot find any rom for my SM-T285YD. So can I flash this rom in my SM-T285YD.
If not then tell me what I need to do to get it working in my SM-T285YD and also I have the twrp but tell me how can make my twrp treble supported twrp....
Best regards....

[RECOVERY]TWRP 3.3.1.0 for Galaxy A20

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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:
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards, thermonuclear war, or your getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this Recovery
* before flashing it! YOU are choosing to make these modifications
* If you point the finger at me for messing your device. i will laugh at you
Special Notes:*
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options).
2. KNOX will be tripped once you flashed custom binaries to your phone.*
(Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status.)
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. All apps that use KNOX like Samsung pay, Secure Folder and maybe more will no more work.
If you like my work please hit the "Thanks" button and feel free to donate to me via my Paypal
Guide
1.Make sure u have rooted device.
If Not follow this (Root For U3,S3,S4)
2. Download the custom recovery[TWRP]
3. On the PC rename the unpatched recovery as recovery.img*
4. Use 7zip to make it into recovery.tar*
(right click and choose add to archive)
5. Use 7zip to add your patched boot.img to recovery.tar
(right click and choose add to archive and choose recovery.tar)
6. Use 7zip to add vbmeta.img to recovery.tar
(right click and choose add to archive and choose recovery.tar)
7. Install recovery.tar to ap slot using Odin.
To ensure that data is not encrypted*so as to enable data to be backed up follow these steps
8. Boot the A20 into TWRP and mount everything that you can.
9. Format Data (not just wipe)
10. Flash*Disable_Dm-Verity.
11. Reboot into Recovery. It will reboot into download mode.
12. On the pc repeat step 7.
13. Reboot phone and re-enter all data.
14. Reboot into Recovery.
15. Flash Magisk
16. Backup*boot, data & system
17. You can now restore boot, data & system.
If u are getting vbmeta.img fotter error when booting to twrp Then flash this vbmeta.tar via odin ap solt.
Downloads
Twrp [U3][U4][S3][S4]
Build with A205FXXS4ASJ4 Source.
Thanks:
TWRP team
@topjohnwu for root
@ianmacd for TWRP flash guide
@afaneh92 for device tree
- @fahadali2315 Good friend, Always support me
Contributors
@Agrim720
Version Information
Status:*Stable
Current Stable Version:*1.0
Stable Release Date:*2019-12-02
Created*2019-12-02
Last Updated*2019-12-17

Quick Root and TWRP.
A quick method is found here.https://forum.xda-developers.com/galaxy-a20/how-to/guide-quick-root-twrp-galaxy-a20-t4069423
Make sure you backup boot, data & system (not system image) before you go on to install GSIs
This TWRP was originally designed for Android 9 but works perfectly with Android 10.
It also comes with MTP built-in.

physwizz said:
Your title says A10. Is that a typo?
This is for the A20 yes?
Click to expand...
Click to collapse
Yes.
Wrong typed.
Fully updated thread with easy guide.

Agrim720 said:
Yes.
Wrong typed.
Click to expand...
Click to collapse
Fixed.
Magic???
Looking forward to seeing more A20 people with TWRP who can backup and restore. ?

physwizz said:
Fixed.
Magic???
Click to expand...
Click to collapse
What Magic?
i didt understand.

Agrim720 said:
What Magic?
i didt understand.
Click to expand...
Click to collapse
The title has been changed from A10 to A20.

What about U4?

TBM 13 said:
What about U4?
Click to expand...
Click to collapse
I'll wait for U8

I can see you mention me then you changed your mind.

afaneh92 said:
I can see you mention me then you changed your mind.
Click to expand...
Click to collapse
Yeah didt put device tree link thats why i remove.
i tryped soon in sources ill put link today and mention you Then ppl will know why thanks goes to u.

TBM 13 said:
What about U4?
Click to expand...
Click to collapse
i dont think it is even released.

Please help. I can't backup data with this recovery

thatha said:
Please help. I can't backup data with this recovery
Click to expand...
Click to collapse
Format data and flash dm-virety.

Agrim720 said:
i dont think it is even released.
Click to expand...
Click to collapse
Take a look to the attached image.

TBM 13 said:
Take a look to the attached image.
Click to expand...
Click to collapse
Twrp will work.
Bcz its built from December security patch sw source.
U can try and report for U4.

Agrim720 said:
Twrp will work.
Bcz its built from December security patch sw source.
U can try and report for U4.
Click to expand...
Click to collapse
Im on U4 and it's confirmed that TWRP is working and installing custom kernel as well.

Deluriane said:
Im on U4 and it's confirmed that TWRP is working and installing custom kernel as well.
Click to expand...
Click to collapse
can you backup and restore

physwizz said:
can you backup and restore
Click to expand...
Click to collapse
Haven't tried yet, but I will in a bit. Kept on getting boot loop when installing custom kernel.
Note: Tried already! Backup and restore works.

Deluriane said:
Haven't tried yet, but I will in a bit. Kept on getting boot loop when installing custom kernel.
Note: Tried already! Backup and restore also working on my end.
Click to expand...
Click to collapse
Maybe the custom kernel that you are installing is more older and doesn't works with U4

TBM 13 said:
Maybe the custom kernel that you are installing is more older and doesn't works with U4
Click to expand...
Click to collapse
Yeah, probably. Tried it also when I was on OCT and it didn't boot also. Have to wait for a newer version.

[RECOVERY] [SHRP] [Dreamlte and Dream2lte] <Shrp version 2.1.1> [12-28-2019]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is... still valid?
*
* 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 Recovery
* 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.
*/
SHRP is inspired by Material design 2 to bring the newest design to the native TWRP. SHRP provides much more along side of it's rich UI experience. New dashboard makes it very easy to interact with TWRP. SHRP got some cool features like Whole new theming section ,Flash Magisk (root or unroot), Camera2api enabler Directly from dashboard, Password protection etc. It's all started , lot more to come.
- Themes
- List view mode along with grid dashboard
- Status bar customization
- New rounded icons added on dashboard
- Notch mode with toggle to disable
- Dark mode or pure white, it's on you
- Navigation bar customization
- Settings + Advanced Settings
- Flash Magisk
- Clear fingerprints.
- Flash ViperFX
- Recovery Locking , Pin or Pattern lock
- CPU core lock/unlock
- Language changing
- Hal3 / CameraAPI2 enabling/disabling
- Oreo+ Reboot menu style
- Redesigned lock screen interface
- Flashlight
- Magisk manager - Enable, disable or delete magisk modules right from SHRP
- and many more, flash right now to find out
1. Make sure you have a custom recovery installed
2. Download the latest SHRP recovery for your device
3. Boot into recovery
4. Flash shrp recovery zip
5. Reboot to recovery.
6. Done
You tell...
Dreamlte(Galaxy S8)
GoogleDrive
OneDrive
Dream2lte(Galaxy S8+)
Google Drive
OneDrive
Mainteiner Telegram
Website
Telegram Group
EpicX
DNI9
TeamWin
osmOsis
VR25
Special Thanks
Giovix92
Pritish
Kirill
Burak D.
ZJRDroid
Corsicanu
AleX
Please inform if we forgot to mention your name here , thanks !

Maintainer: Renatoh
Based On: TWRP
TWRP Version: 3.3.1-0

Thanks, going to try, will report back.
Okay, reporting back, everything works fine except for the prompt to install twrp app (which is not displaying properly)

Working fine on S8+ but 2 things
1. In the reboot menu, to install the TWRP (app*) is kinda glitched
2. Using USB meanwhile in recovery, does not load the SD card in the PC (it hangs out), it works fine on Internal Storage tho

panchovix said:
Working fine on S8+ but 2 things
1. In the reboot menu, to install the TWRP (app*) is kinda glitched
2. Using USB meanwhile in recovery, does not load the SD card in the PC (it hangs out), it works fine on Internal Storage tho
Click to expand...
Click to collapse
Send me the recovery logs

aww! i see this having great potentials. ?

RuizLenatoh said:
Send me the recovery logs
Click to expand...
Click to collapse
Sorry for the delay, I was kinda busy yesterday :C
The important code is this one I guess
Code:
I:[MTP] created new mtpserver object
E:[MTP] Failed to start usb driver!I:[MTP] mtppipe add storage 65537 '/data/media/0'
I:[MTP] mtppipe add storage 65538 '/external_sd'
libc: Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) in tid 3142 (recovery), pid 3142 (recovery)

its the first of its specific kind since of recent, i love and appreciate the fact that it is "Password Protected" ????☺..
meaning your current ROM, lock state cannot be simply wiped after lost or stolen..
flashed on TWRP 3.1.1-1...
BUG: cannot turn on flash light on my Samsung S8 G950 from the recovery screen, everything else is a gooooooooo...
Thank you Dev..........?

Thank you Dev..........?

So it's reliable for every day use?

What is the point of protection recovery ?

Zendesk2 said:
What is the point of protection recovery ?
Click to expand...
Click to collapse
Well, if someone steals your phone, and it is password protected, they can just go to recovery and wipe data or flash a new rom. With passwors protected recovery they cant.

zachar093 said:
Well, if someone steals your phone, and it is password protected, they can just go to recovery and wipe data or flash a new rom. With passwors protected recovery they cant.
Click to expand...
Click to collapse
They still can flash a custom recovery the old fashioned way via ODIN, which would make the password obsolete ... It's just a little inconvenience for the potential thief, not more, not less. But yes, it could at least lock absolute dummies out (e.g thiefs, partners or parents or dorm mates or whatever who want to sneak around your phones data and are not at all technically interested beyond barely being able to use Instagram and so on, so lacking the basic skills and/or patience needed for learning about and executing such tasks)

Zendesk2 said:
What is the point of protection recovery ?
Click to expand...
Click to collapse
i would think it basically locks the recovery to a point where it wont allow flashing or wiping unless unlock. at least no virgin wont have access to it...
but somehow odin mode can bypass it i guess, i'm just a noob trying a thing & two.
---------- Post added at 01:26 AM ---------- Previous post was at 01:26 AM ----------
The_Black_Dahlia said:
They still can flash a custom recovery the old fashioned way via ODIN, which would make the password obsolete ... It's just a little inconvenience for the potential thief, not more, not less. But yes, it could at least lock absolute dummies out (e.g thiefs, partners or parents or dorm mates or whatever who want to sneak around your phones data and are not at all technically interested beyond barely being able to use Instagram and so on, so lacking the basic skills and/or patience needed for learning about and executing such tasks)
Click to expand...
Click to collapse
yes, i figured.
---------- Post added at 01:37 AM ---------- Previous post was at 01:26 AM ----------
ZeroCount said:
So it's reliable for every day use?
Click to expand...
Click to collapse
yes in a low crime or area, lol. or not you're neglectful with ur pone, daily usage?!... you would have to be ur judge on that..
personally for me its convienent enough in such a useful way, the fact it manage magisk modules, internal & external files etc, on such a userrr friendly level.
bugs may differ for some..

Ok, but what if someone instead of recovery mode enter in download mode on to the phone that has been stolen and flash stock ROM through Odin ..

Does not see usb flash drive. Please help.
SM-G950F cihazımdan Tapatalk kullanılarak gönderildi

Will it support other languages? Simplified Chinese?

Does this work with latest twrp?

This custom recovery is relly good. Why is nobody supporting ?
How can i build SHRP 2.2 on dream2lte?

could you also add a feature to disable Xposed/edxposed modules becuase lets face it theyre the real culprit in making your phone bootloop
edit: lol just figured I could disable the whole edxposed module lmao
why does it ask me to install TWRP app after I flash

This is pretty nice, can't lie about it. It brings some useful features to the already "feature-packed" TWRP recovery. The thing I like the most is the ability to theme your menu and the password protection.

How To Guide [GSI][PHH][13] Guide & Support [Mojito][Sunny]

Why should I use a GSI ? Mojito already have custom ROMs ¯\_(ツ)_/¯Yes. But this thread exists due to the following reasons:
You don't wanna fear about devs stop shipping updates.
You don't wanna re-flash your custom recovery / kernel after each update.
Unlike some ROMs, no clean flashes necessary after you update.
You don't wanna be a flashoholic / beta tester of a ROM maintainer.
GSIs are like Linux Distros. Flexible, hasslefree & minimal.
All GSIs support signature spoofing out of the box.
Differences between GSIs & ROMs:
ROM updates modify all the partitions (boot, recovery, kernel, system, vendor, etc). A GSI update is just a system partition that updates "only" the system, that runs upon stock firmware.
ROMs might pass safetynet out of the box. But for GSIs, you must root & use magisk modules to achieve that.
You can't flash gapps on vanilla GSIs, as you do on vanilla ROMs. You must use bgS/bgN GSI variants.
For now, GSIs have to be installed via fastbootd, as recoveries still yet to support logical partitions. So you need computer available when you update or change them.
AOSP GSI project is being alive for almost many years now. I've been daily driving his project on this device for almost two years. Everyone claim GSIs are buggy & not daily drivable, which is a complete false claim. There are no compromises with GSIs when compared to ROMs.
PREREQUISITES
USB Drivers (guide to install)
Platform Tools (guide to setup)
Stock ROM (fastboot)
MicroG (for vanilla)
vbmeta.img (from google)
TWRP (thanks to Nebrassy)
Magisk (thanks to topjohnwu)
SafetyNet Fix (thanks to kdrag0n)
Recommended GSIs :
TrebleDroid (thanks to phhusson)
Pixel Experience (thanks to ponces)
LineageOS (thanks to AndyYan)
More to test from here
INSTALLATIONNOTE: I'm assuming you've already unlocked bootloader, backed up your data & know all the technical consequences of flashing & modding.
Download / extract all prerequisites in one place.
From stock firmware, edit flash_all_except_data_storage.bat/sh & modify last line to fastboot reboot fastboot
Enter fastboot mode {vol_down+power}, connect to PC & flash firmware using above edited script. When device enters fastbootd, from terminal/cmd execute :
fastboot erase userdata
fastboot flash vbmeta vbmeta.img
fastboot flash system <gsi-file.img> (ignore INVALID SPARSE warning)
fastboot reboot & make sure your GSI boots up. Power off & return to fastboot again.
fastboot boot <twrp-file.img>, head to Advanced & run flash current TWRP to make recovery persistent across reboots.
Finally Magisk (for root, safetynet fix, additional modding, etc).
BUG_1: Don't touch the screen while booting to avoid touch issues after you boot (this bug occurs only on custom kernels).
BUG_2: Don't set up password on startup wizard. Instead, set it up later & then disable Android Setup app if it exists. Else it'll crash fingerprint settings.
UPDATE / DIRTY FLASH HOW ?
fastboot reboot fastboot
fastboot flash system <new-gsi.img> & reboot twice
All phh based GSIs are dirty flashable (unless you switch between vanilla & gapps). If any GSI doesn't boot up, you can always reflash the older GSI & restore the previous state without any data wipes.
POST CONFIGURATION
Enable the following Settings > Phh Treble Settings:
Qualcomm features / Use alternate camera profile & audio policy
Misc features / Disable audio effects
IMS features / Force the presense of 4G calling & Install IMS Apk for Qualcomm vendor from notification panel.
Setup magisk, hide the app, enable Zygisk & Enforce Denylist.
Use SafetyNet-Fix module to pass safetynet. Still won't pass? Try Pixel-Props (redfin) that ensures fingerprinting.
microG module if you chose vanilla variant (Safetynet works. Most of the banking apps work except gpay).
NOTE: Flash custom kernels only through your custom recovery. Flashing through kernel managers (FKM, SPKM, etc) is not suggested.
MAGISK NOT WORKING ?In this case, the GSI you selected isn't securized (comes with su bydefault). Through TWRP, do
mount -o rw /dev/block/mapper/system_a /system_root from terminal
Code:
rm /system_root/system/xbin/su
rm /system_root/system/bin/phh-su
rm /system_root/system/etc/init/su.rc
Or instead, you can use recovery's file manager to delete the above files. Then reboot.
EXTRASMy Recommendations for great experience:
SPKM to set GPU > GPU Governor > Performance (fixes UI lags)
Lawnchair / Quickswitch for launcher customization with gesture navigation support.
Lineage Dialer for built-in call recording (push into /product/priv-app/Dialer/Dialer.apk).
ANXCam for MIUI camera's post processing.
GCam for google camera's post processing.
Aurora Store / Droid for microg users.
Kiwi Browser for chrome extensions support.
Migrate to backup / restore user apps & data, incase you lose your setup.
Thanks for reading all the way through here.

I have been using GSIs on my old Huawei P10 lite for almost 3 years, and it was a very good experience.
Now with mojito I find myself lazy always using Roms -_- '
Thanks for the guide!

Hami_Do said:
I have been using GSIs on my old Huawei P10 lite for almost 3 years, and it was a very good experience.
Now with mojito I find myself lazy always using Roms -_- '
Thanks for the guide!
Click to expand...
Click to collapse
The only official dev for this device, who's actually from core development of a reputed project (PE), is Zid. There aren't any, as I do not find others to be helping from core (except couple of kernel devs).
ROMs have no complete guarantees for future updates. Although you can use other project GSIs such as crD by Nazim, LOS by Andy, phhusson's the one who's consistently providing regular monthly updates with built-in OTA.

Can I install MIUI gsi roms like this?

Furkantaner said:
Can I install MIUI gsi roms like this?
Click to expand...
Click to collapse
You can install any AOSP GSIs with this guide. Not sure of other skins, as they're proprietary.
And why would you need MIUI GSI? Mojito stock "is" MIUI.

Furkantaner said:
Can I install MIUI gsi roms like this?
Click to expand...
Click to collapse
Miui and its similar sGsi ( semi gsi ) such as OneUi , Color os .. and other AOSPs based ported with Erfan tool aren't real gsi.
They miss patches from Phh and Andy.
The recommanded gsis with full patches (minimum issues) are from Phh (aosp), AndyYan (LOS 18.1/19.1), Ponces (PE) and many others you can check them here for example :
Treble-Enabled Device Development A/AB ROMS
Treble-Enabled Device Development A/AB ROMS
forum.xda-developers.com
There are also more by Nazim and eremitein, you can check them in telegram groups.

can i use this method from aosp?
and what stock rom version should i use?

AlsoKouki said:
can i use this method from aosp?
and what stock rom version should i use?
Click to expand...
Click to collapse
Any version would work. Open stock ROM link in main post & make sure it's fastboot, not recovery.
As for AOSP, you can use any of them from this list (except A13).

in the last line i should change it to "fastboot %* reboot fastboot" or "fastboot reboot fastboot" ?

AlsoKouki said:
in the last line i should change it to "fastboot %* reboot fastboot" or "fastboot reboot fastboot" ?
Click to expand...
Click to collapse
Both work & imply the same btw. That line I've wrote just to make device go to fastboot instead of stock miui.

Adding fingerprint force closes settings.
Youtube fc aswell.

MPK99 said:
Both work & imply the same btw. That line I've wrote just to make device go to fastboot instead of stock miui.
Click to expand...
Click to collapse
i already execute the "flash_all_except_data_storage.bat" but nothing happen should i execute it with mi flash tool?

Samir2298 said:
Adding fingerprint force closes settings.
Youtube fc aswell.
Click to expand...
Click to collapse
No issues here. The procedure I've laid out is exact to that of my device. Some more info from your side might help, such as what you did from the start.

AlsoKouki said:
i already execute the "flash_all_except_data_storage.bat" but nothing happen should i execute it with mi flash tool?
Click to expand...
Click to collapse
I bet it's usb drivers issue. There's guide link in main post.
You should know the issue if you flashed a fastboot rom before.

MPK99 said:
I bet it's usb drivers issue. There's guide link in main post.
You should know the issue if you flashed a fastboot rom before.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nah its already installed and its detected in fastboot
i tried move the firmware to plarform-tools/ after i execute it this happen

MPK99 said:
No issues here. The procedure I've laid out is exact to that of my device. Some more info from your side might help, such as what you did from the start.
Click to expand...
Click to collapse
Followed exactly as in OP.
I did remove some apps tho from product app/priavpp and system app/privapp, so maybe that caused an issue? Is there anything related to fingerprint in those folders?

AlsoKouki said:
tried move the firmware to plarform-tools/ after i execute it this happen
Click to expand...
Click to collapse
This is redmi Note 10 forum mate. So I had stock ROM link of mojito/sunny. Your device (3rd screenshot) closely states it's Rainbow (Wiko).
Although this is a GSI guide, I suggest you to flash your own device's stock rom.
Still, it won't be enough caz I don't have overlay patch of your device.

Samir2298 said:
I did remove some apps tho from product app/priavpp and system app/privapp, so maybe that caused an issue? Is there anything related to fingerprint in those folders?
Click to expand...
Click to collapse
Probably. Try removing only one or two apps that are disablable from settings.. For overlay just 20kB is needed.
You can reflash system image from fastbootd & boot up without wiping again.

MPK99 said:
Probably. Try removing only one or two apps that are disablable from settings.. For overlay just 20kB is needed.
You can reflash system image from fastbootd & boot up without wiping again.
Click to expand...
Click to collapse
Alright, thanks! I'll try reflash.
Sorry for off-topic, does microg support whatsapp google drive backup/restore? I searched google but all answers are years old.

MPK99 said:
This is redmi Note 10 forum mate. So I had stock ROM link of mojito/sunny. Your device (3rd screenshot) closely states it's Rainbow (Wiko).
Although this is a GSI guide, I suggest you to flash your own device's stock rom.
Still, it won't be enough caz I don't have overlay patch of your device.
Click to expand...
Click to collapse
ahh sorry its because the spoofing feature from the rom,i forgot to disable that, will disable it and try again

Better Mobile App

welcome