Develop Bugs

Need some guidance to update my phone... please...

I realize I'm late to the party with this phone, again... but if I can get any help it would be greatly appreciated.
I really haven't gotten into this phone as much as I did the Rezzy so I want to be sure about what I'm doing.
I had someone root it for me and I flashed ViperRom back in around January 2016. Haven't flashed anything since. Shocking, I know! At least for anyone on these forums, not so much for me.
Anyway, now I would like to update to Nougat. Haven't read anything saying it's a problem going to Nougat, right? I have TWRP, am rooted and s-off.
So... first question is that if I'm s-off, can I simply wipe and flash the Nougat RUU and get the firmware with it? Then flash TWRP and a ROM?
If not... this is what I think I need to do based on what I've read and found:
1 - flash new firmware
I believe this one: 4.49.605.16_NoBoot-NoRecovery_firmware.zip
I found here: https://forum.xda-developers.com/showpost.php?p=65358020&postcount=2
But I'm not clear if I need to prep for that, like take it back to stock or not.
Also, can I flash it off my sd card or do I need to use adb? (All the usb ports on my computer are 3.0 and I don't have the original cable that came with the phone.)
2 - I plan to run the RUU and make a nand of it to have for safety on my sd card. Can't remember if this takes me to a stock recovery, I want to end up with TWRP. Maybe I don't really need to do this anyway...???
3 - Flash ROM of choice. I think I might try LeeDroid's ROM. Do I need to do anything manually for SU? (I've been getting prompts that I need to update SU but have been afraid to do it, not knowing if I should since I'm running an older ROM at this point.)
Does that sound right? Did I miss anything?
I appreciate any and all input!

I go: (with S-OFF & TWRP), ADB, Flash Firmware (via @santod040's fantastic resources), move Stock Nougat ROM onto internal SD, Flash via TWRP and follow the Aroma prompts (if I remember correctly, it'll wipe and do everything for you). Works just fine. Then a generally flash Xposed via the Magisk Manager.
My current set-up and the fact that I have three m9's is honestly the only reason I haven't moved on to a new phone. I can just flash my nandroids between the devices as needed, provide WiFi to my apartment, and use Youtube with background playback and Adblocking.

Exokan said:
I go: (with S-OFF & TWRP), ADB, Flash Firmware (via @santod040's fantastic resources), move Stock Nougat ROM onto internal SD, Flash via TWRP and follow the Aroma prompts (if I remember correctly, it'll wipe and do everything for you). Works just fine. Then a generally flash Xposed via the Magisk Manager.
My current set-up and the fact that I have three m9's is honestly the only reason I haven't moved on to a new phone. I can just flash my nandroids between the devices as needed, provide WiFi to my apartment, and use Youtube with background playback and Adblocking.
Click to expand...
Click to collapse
Thanks.
I guess I'll go ahead and use ADB to flash the firmware then and keep TWRP in the process. So from what I've been reading, SU has been replaced with Magisk now?
And yeah, I might try Xposed now. Was running Viper which already had a bunch of tweaks, some of which didn't work that well and caused annoyance, so maybe I'll also go stock Nougat with Xposed. Hopefully you'll be back here if I have questions about Magisk Manager!!!
That's the problem with wanting to totally geek out but not really. I mean I keep my phones for 4 years. Nothing wrong with my M9 except the battery (and this one file it keeps wanting to download but never does). Hehe... Plus, I don't have the time to keep up with things on a regular basis and nor the time to really learn all the internal workings of things for each phone.

Exokan said:
I go: (with S-OFF & TWRP), ADB, Flash Firmware (via @santod040's fantastic resources), move Stock Nougat ROM onto internal SD, Flash via TWRP and follow the Aroma prompts (if I remember correctly, it'll wipe and do everything for you). Works just fine. Then a generally flash Xposed via the Magisk Manager.
My current set-up and the fact that I have three m9's is honestly the only reason I haven't moved on to a new phone. I can just flash my nandroids between the devices as needed, provide WiFi to my apartment, and use Youtube with background playback and Adblocking.
Click to expand...
Click to collapse
Hey Bro
My Htc M9 Stuck at Htc Logo And i dont know how to get back in stock rom ......... i read so much threads on XDA but nothings work for me ... may be my poor knowledge of technical line
below are the info about my device
C:\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) kernel: lk
(bootloader) product: htc_himawl
(bootloader) version: 1.0
(bootloader) imei: 990005024443625
(bootloader) version-main: 3.37.605.28
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 0PJA30000
(bootloader) cid: 11111111
all:
finished. total time: 0.080s
Do you have any idea to resolve this problem...... all process i saw on XDA. device is in Working condition to follow but my device is brick for me please help me what should i do

[CLOSED][OFFICIAL] TWRP 3.4.0-0 | Team Win Recovery Project | Nokia 7.2 | Daredevil |

{
"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"
}
Note - Iam Not Responsible for bricked devices
About Team win recovery project
TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
Installation procedure
Note - download twrp according to your phone security patch
1 . Download twrp-3.4.0-0-DDV_sprout_sprout.img copy in one folder
2. connect phone to pc boot your phone to bootloader mode
3. open cmd in that folder
4. type fastboot devices
5. type fastboot flash boot twrp-3.4.0-0-DDV_sprout.img
6. now get back to phone select recovery mode and now your phone boots in to twrp
7. now flash magisk or what ever your wish and press reboot system
bugs- none
well still you people can flash magisk.zip using sideload
just download magisk.zip & and click on sideload in twrp and open cmd and type adb sideload magisk.zip and after completion reboot system
Download Android 9 Twrp-3.3.1-0 From Here
Download Android 10 Twrp-3.4.0-0 From Here
​For More Information About Status Official Click Here​
​Join Nokia 7.2 Community​
​
XDA:DevDB Information
TWRP 3.4.0-0 , for the Nokia 7.2
Contributors
Raghu varma
My build script: https://github.com/RaghuVarma331/scripts
Source Code: https://github.com/omnirom/android_bootable_recovery
Device Source Code: https://github.com/TeamWin/android_device_nokia_DDV_sprout.git
Version Information
Status: beta
Created 2019-11-07
Last Updated 2020-06-25

Thanx.
Thanx for the effort and hope this phone will have good Custom
ROMs too

nuwanmw1988 said:
Thanx for the effort and hope this phone will have good Custom
ROMs too
Click to expand...
Click to collapse
Soon roms will be out

Does anyone have a stock recovery.img? In case that i will install OTA.

pinh3ad said:
Does anyone have a stock recovery.img? In case that i will install OTA.
Click to expand...
Click to collapse
Nokia 7.2 is an A/B system, not sure where you would get a recovery.img
Additionally, coming from 00WW_1_200 (September update), WiFi module fails after flashing TWRP, and it seems you have to reflash original kernel/boot.img to get the WiFi back. It would be helpful if someone is willing/able to provide it.

KohGeek said:
Nokia 7.2 is an A/B system, not sure where you would get a recovery.img
Additionally, coming from 00WW_1_200 (September update), WiFi module fails after flashing TWRP, and it seems you have to reflash original kernel/boot.img to get the WiFi back. It would be helpful if someone is willing/able to provide it.
Click to expand...
Click to collapse
The reason behind this we need a proper kernel sources from hmd Nokia . For that reason i used prebuilt kernel from stock rom and that rom is based on August so here August kernel & wifi modules signed with different keys and September kernel & wifi modules signed with different keys so here August kernel and September wifi modules signatures are different that's why wifi got broken

Hi Guys,
i'm having a problem, I' able to fastboot flash boot twrp-3.3.1-0-DDV_sprout-9.0-20191119.img but when I restart it, i still not having twrp booting and now, the wireless module is not booting
Anyone to help?
D:\userdata\...\Desktop\Nokia 7.2> fastboot flash boot "D:\userdata\...\Desktop\Nokia 7.2\twrp-3.3.1-PL2.img"
target reported max download size of 536870912 bytes
sending 'boot' (38736 KB)...
OKAY [ 0.849s]
writing 'boot'...
OKAY [ 0.246s]
finished. total time: 1.101s
D:\userdata\...\Desktop\Nokia 7.2> fastboot reboot
rebooting...
finished. total time: 0.002s

JoSoFer said:
Hi Guys,
i'm having a problem, I' able to fastboot flash boot twrp-3.3.1-0-DDV_sprout-9.0-20191119.img but when I restart it, i still not having twrp booting and now, the wireless module is not booting
Anyone to help?
D:\userdata\...\Desktop\Nokia 7.2> fastboot flash boot "D:\userdata\...\Desktop\Nokia 7.2\twrp-3.3.1-PL2.img"
target reported max download size of 536870912 bytes
sending 'boot' (38736 KB)...
OKAY [ 0.849s]
writing 'boot'...
OKAY [ 0.246s]
finished. total time: 1.101s
D:\userdata\...\Desktop\Nokia 7.2> fastboot reboot
rebooting...
finished. total time: 0.002s
Click to expand...
Click to collapse
You have to flash twrp According to your security patch
For example September security patch download from 2019-09-19
For example August security patch download from
2019-08-19
And also if you want to boot back to twrp after flashing twrp and rebooting in to system
Just power off your phone and reboot to download mode and press reboot to recovery now you will boot in to twrp.
If you know what exactly you are doing you won't get confused just follow steps
If you still can't able to boot then you are unlucky because all of the people who viewed this thread successfully booted as well

Hi, I tried to flash this TWRP 2 times, and in all cases the touch does not work. Nokia 7.2 TA-1196. Any ideas how to fix this?

Which TWRP to Flash?
i have model TA-1193 on november 5 security patch, os version is 00ww_1_200_SP01.
was able to successfully un lock bootloader today. Which TWRP should i flash? there are multiple images in https://sourceforge.net/projects/ddv-sprout/files/TWRP/PIE/2019-11-05/\
tried Flashing all the recoveries from the folder, wifi doesnt work.! any help how to fix it?

I wiped my SD card, now instead of 256GB it shows as 16MB, any ideas? Crap, now when i boot into Recovery, i just get a dead robot and 'No Command".

Why do the instructions here say to flash it to the boot partition, but the instructions on the twrp site say to flash it to the recovery partition? IMO recovery makes more sense but I'm no expert.
Which one is correct?
Code:
fastboot flash boot twrp.img
or
Code:
fastboot flash recovery twrp.img
I've had bat luck flashing things to boot in the past so want to make sure.
----- EDIT -----
Nvm my silly question. I've been out of the loop for a while and didn't realise there isn't even a recovery partition anymore. I've now flashed TWRP, boots up fine. No issues with anything on the stock rom afterwards.
However, my question now is how to get TWRP to work with the internal storage? I wanted to make a somewhat stock backup before rooting and the internal storage is full of jibberish folders and files. (See attached image)

CGarz said:
Why do the instructions here say to flash it to the boot partition, but the instructions on the twrp site say to flash it to the recovery partition? IMO recovery makes more sense but I'm no expert.
Which one is correct?
Code:
fastboot flash boot twrp.img
or
Code:
fastboot flash recovery twrp.img
I've had bat luck flashing things to boot in the past so want to make sure.
----- EDIT -----
Nvm my silly question. I've been out of the loop for a while and didn't realise there isn't even a recovery partition anymore. I've now flashed TWRP, boots up fine. No issues with anything on the stock rom afterwards.
However, my question now is how to get TWRP to work with the internal storage? I wanted to make a somewhat stock backup before rooting and the internal storage is full of jibberish folders and files. (See attached image)
Click to expand...
Click to collapse
Well even I appreciate the work of this guy, you have to be careful. 1st - if you on Nokia 7.2 keep in mind that all his stuff based not on Nokia 7.2 sources because Nokia not released any souses yet. 2nd - he warned about it if read carefully. 3rd - all his ROMs for Nokia 7.2 have same trouble as LineageOS and treble. I prefer stay on stock with MicroG, at least all stuff works. 4th - for internal access from twrp you have flash DisableForceEncryption_Treble. Don't use Disable_Dm-Verity_ForceEncrypt_10.20.2019 it has bugs and not works. Just look for same name as I give Disable_Forse_Encryption_Treble. Careful with, it removes encryption but leaves verity in tact. Read all warning about using it, google in help. After reboot in twrp you would read internal and data. Hope that helps. Also check version twrp that he uploading, they base on security patch and I guess it have to match your system. But I'm using fine 11/28 on august security patch.
O, and one more thing - don't relay completely on twrp backups, they not working in 100%, just try restore before. Good luck.

Thanks for the tips boomo15. I ended up installing the Lineage OS rom though.
WiFi works now, data is decrypted and the other system UI crashing bug I had has gone as well. Very pleased with the phone now.
NFC and DDTW don't work and cam quality is poor but even with those issues Lineage is still preferable to me.

CGarz said:
Thanks for the tips boomo15. I ended up installing the Lineage OS rom though.
WiFi works now, data is decrypted and the other system UI crashing bug I had has gone as well. Very pleased with the phone now.
NFC and DDTW don't work and cam quality is poor but even with those issues Lineage is still preferable to me.
Click to expand...
Click to collapse
As I told before stock works best for me, but last week I install AOSP phh_treble version for Pie 123. Since 109 a lot off better.All works smooth and fine, detects my sim card w/o problems (got 1 sim not dual). Replaced camera (crashed all time) with ported by Balu GCam works fine for me. Got one issue - can send sms but can't receive. Tried fix myself but no luck, so asked for help on AOSP treble tread. Hope somebody know what's going on. Don't use NFC can't tell if it works or not.

boomo15 said:
As I told before stock works best for me, but last week I install AOSP phh_treble version for Pie 123. Since 109 a lot off better.All works smooth and fine, detects my sim card w/o problems (got 1 sim not dual). Replaced camera (crashed all time) with ported by Balu GCam works fine for me. Got one issue - can send sms but can't receive. Tried fix myself but no luck, so asked for help on AOSP treble tread. Hope somebody know what's going on. Don't use NFC can't tell if it works or not.
Click to expand...
Click to collapse
That' strange about SMS. Did you set your APN correctly? Or does your carrier auto set it like mine does?
Also for NFC could you see if you have the option for it in settings? It should be around WiFi, Bluetooth, etc.

Hi,
I was trying to install the TWRP recovery but when I saw people in a other XDA forum everyone crying about there WiFi that wont work.
So I was wondering can I install the TWRP recovery without those problems.
Here some info about my phone:
Nokia 7.2 TA-1196
Android version: 9
Security patch level: December 5, 2019
Some help would be appreciated.

VictorAcid said:
Hi,
I was trying to install the TWRP recovery but when I saw people in a other XDA forum everyone crying about there WiFi that wont work.
So I was wondering can I install the TWRP recovery without those problems.
Here some info about my phone:
Nokia 7.2 TA-1196
Android version: 9
Security patch level: December 5, 2019
Some help would be appreciated.
Click to expand...
Click to collapse
Not sure about your version, I got Nokia 7.2 TA-1178 no any problems on stock. The problem that I experienced with was when I used Disable_Dm-Verity_ForceEncrypt_10. - bootloop. For root I used Magisk versions from 19.3-20.2 w/o any problems. Read couple treads above what I used to disable encryption. Also I use w/o problems Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip - it do all job remove encryption and verity if you interested. Also not all backups that I made using TWRP posted here worked.
---------- Post added at 05:31 PM ---------- Previous post was at 05:23 PM ----------
CGarz said:
That' strange about SMS. Did you set your APN correctly? Or does your carrier auto set it like mine does?
Also for NFC could you see if you have the option for it in settings? It should be around WiFi, Bluetooth, etc.
Click to expand...
Click to collapse
Sorry I can't tell you anything about NFC. As I told before can't receive SMS and this I my business phone not playing toy I return back on stock. For me root and removing not wanted stuff enough. Bad that not all my TWRP backups working, have to always format data. Right now I do adb backup.

boomo15 said:
Not sure about your version, I got Nokia 7.2 TA-1178 no any problems on stock. The problem that I experienced with was when I used Disable_Dm-Verity_ForceEncrypt_10. - bootloop. For root I used Magisk versions from 19.3-20.2 w/o any problems. Read couple treads above what I used to disable encryption. Also I use w/o problems Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip - it do all job remove encryption and verity if you interested. Also not all backups that I made using TWRP posted here worked.
---------- Post added at 05:31 PM ---------- Previous post was at 05:23 PM ----------
Sorry I can't tell you anything about NFC. As I told before can't receive SMS and this I my business phone not playing toy I return back on stock. For me root and removing not wanted stuff enough. Bad that not all my TWRP backups working, have to always format data. Right now I do adb backup.
Click to expand...
Click to collapse
Okay lets not try it this is my main phone :/

I tried to build TWRP myself using your device tree and the latest stock kernel that I extracted from the OTA. The result was a working wifi module, but whenever I set a device unlock PIN, entering the correct PIN doesn't unlock the device. It just says "Wrong PIN". Do you have any thoughts about what could be happening? I'm at a loss.

[ROM][SOFIA*/RAV*][10][UNOFFICIAL] OmniROM

{
"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"
}
Supported devices :
sofia
sofiap
sofiap_ao
sofiar
rav
rav_t
Download (GApps included)
Kernel source
Device tree source
MAJOR BUGS:
you tell me
FLASHING
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot -w (mandatory if coming from stock, warning tho : it will erase all your data)
UPDATE
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Telegram support group : https://t.me/Motorola_G_Stylus
20200821 Changelog :
- Add support for g8/g fast
- Add LED support
- Add selinux enforced for all
- Safetynet should pass for all devices (can't check my self, let me know)
- Fix crash when turning off wifi hotspot
XDA:DevDB Information
OmniROM, ROM for the Moto G Stylus
Contributors
vache
Source Code: https://github.com/omnirom/
ROM OS Version: 2.3.x Gingerbread
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2020-08-28
Created 2020-08-28
Last Updated 2020-08-28

2.3.x Gingerbread?

Just installed on my device, works great first try, only thing I've found to not work is Moto Audio with any sort of headphones, works with internal speaker tho. great work thanks!

googl-fi sofiap cannot flash to system
I am unable to flash to the system. It will not let me delete the super or system file. not sure what to do tried everything that is listed on the flash gsi. anyone with some help

lightningdude said:
2.3.x Gingerbread?
Click to expand...
Click to collapse
Typo, dude. F

rooted?
is this rom rooted?
vache said:
Supported devices :
sofia
sofiap
sofiap_ao
sofiar
rav
rav_t
Download (GApps included)
Kernel source
Device tree source
MAJOR BUGS:
you tell me
FLASHING
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot -w (mandatory if coming from stock, warning tho : it will erase all your data)
UPDATE
Boot to fastbootd mode (adb reboot fastboot or fastboot reboot fastboot)
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash product product.img
fastboot flash vbmeta vbmeta.img
fastboot reboot
Telegram support group : https://t.me/Motorola_G_Stylus
20200821 Changelog :
- Add support for g8/g fast
- Add LED support
- Add selinux enforced for all
- Safetynet should pass for all devices (can't check my self, let me know)
- Fix crash when turning off wifi hotspot
XDA:DevDB Information
OmniROM, ROM for the Moto G Stylus
Contributors
vache
Source Code: https://github.com/omnirom/
ROM OS Version: 2.3.x Gingerbread
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Based On: AOSP
Version Information
Status: Beta
Beta Release Date: 2020-08-28
Created 2020-08-28
Last Updated 2020-08-28
Click to expand...
Click to collapse

stolirocks said:
is this rom rooted?
Click to expand...
Click to collapse
Nope.

Although not "rooted" you can root after installation just like you would with stock.

Thank you for the ROM. First time using OmniRom and loving it so far. I have not run into any issues so far. Even on t-mobile, my WiFi calling, visual voicemail and text messages all are working without any issues.
Will you be releasing a version with just MicroG instead of gApps? I ended up just uninstalling all the gApps anyways, but just curious.
Keep up the great work!

GApps Dilemma
I am really looking forward to not having Gapps on this device, I haven't installed yet due to this, and wonder. Is this OpenGApps implentation removable using the same instructions as if it were installed manually after the CFW was flashed? Also, if it is not too much extra work, could you post a non GApps build?
Thanks for the hard work!

griz.droidx said:
Although not "rooted" you can root after installation just like you would with stock.
Click to expand...
Click to collapse
I tried rooting with the latest & second latest SuperSU flashable zip, but it didn't work. Do you know what build I could use?

.Solotato said:
I tried rooting with the latest & second latest SuperSU flashable zip, but it didn't work. Do you know what build I could use?
Click to expand...
Click to collapse
Greetings Solotato and Moto/Android community ,
I know this post is long excessively but hopefully it'll get the point across. Please don't think I'm talking down to you or anyone else. This whole process had me baffled at first as well and I've used others work to root and rom fur years. I've used Linux on the desktop by dual and even triple booting (Nix,Xpor2K, and 98 for old hardware slash gaming support) I even wrote a config for a guy's app called js2mouse to use 2 pointers at the same time in X(wanted to use my old logitech wingman cordless as a remote. But I'm no expert and still consider myself a little above novice. This isn't meant to offend anyone. Shew (the us is just too politically correct)
You can use twrp i think with magisk. BUT...im pretty sure i flashed twrp once in the recovery bootloader before but nothing else would take and twrp didn't function correctly.
I agree with many others now that it's easier to put a copy of the boot image on your device after installation. It's simple really
Just boot your device,
Enable developer options first thing then adb, then you can connect with a usb cable and approve adb access in your phone.
Copy the boot image to your phone and use the latest official magisk to patch the boot image. In magisk pick install then pick image, you pick your boot image which is then patched and renamed magisk_patched or similar.
It'll be in your downloads folder. Move it back to your pc, the patched one of course, and then just
fastboot flash boot magisk_patched.img
A TIP if you're new to the command line/powershell(win) or terminal(nix/bsd/mac (which is based on bsd)You can even use the up arrow if you dunt want to retype the commands then just replace boot.img with magisk_patched.img just start typing magis then hit tab and it'll complete it for you..
All this looks complicated but trust me after you do it a few times you'll be doing it in a minute or two.
Good luck take your time and read everything you can find. Don't forget to ask the command line for --help! You can find help in a jiffy that way.
Example
fastboot --help i think is the syntax i can't see it on my phone but there's a space between the two dashes and the command your asking for help. And for more details help is included in Linux with man pages. Those are handy in a pinch.
Even though I've done this since the droidx days on many phones, it still took me a lot of research and reading to get this new a/b partitioning and fastboot stuff down to where i can do it quickly.
Read and search these threads you'll be more likely to get answerers from xda members if they can tell you've been reading up on it.
Good luck!
Practice practice practice. That's the advice my uncle gave me on shooting a bow (instinctive or without sights) and he was right. This applies to everything in life.
Anyway I've preached enough. I know it's a long post but hopefully you and others who are relatively new to these moto's will get some help here.
Don't forget to thank the developers and others who made all this coolness possible for us who benefit from
If i helped any at all or you enjoyed my way too many useless details style, please hit thanks. I appreciate that. Sorry for the delay in posting I'm still setting up my most recent rom and I've doing a lot of stuff outside my home before winter.
Sent from my Moto G Stylus using XDA Labs

Sorry guys that was waaaaay too long.
Sent from my Moto G Stylus using XDA Labs

Could anyone point me in the right direction for recompiling this rom's kernel with a different config? I'm looking to poke around & try to get USB OTG/ACA mode to work (i.e. have the phone charge as well as use a usb device, like a mouse/keyboard/storage), which is apparently possible by setting CONFIG_USB_MSM_OTG and CONFIG_USB_MSM_ACA.
I've never compiled a kernel for another arch before, and I assume I need a toolchain that targets arm64 to begin with - I've also never really built anything for android before, and all the guides I've found thus far seem to either be for a specific device or building an entire system image, which seems to be too much - I'm given to understand I can replace the kernel image in boot.img by itself with a tool like mkbootimg.
Any help with where to start would be appreciated, thanks!

My Screen isn't working anymore... using an OTG to move around....
It's the touch screen

Another user asked this previously without any response ... Could you post a degoogled Omni ROM without gapps? Or give any advice how to remove it ? You were the one to put it all together so surely for you it must be easy removing it? As for me, I've been stuck.

Hi I am really struggeling here ... Everytime I try to flash system it ends with
writing 'system_b' 2/3...
FAILED (remote: Operation not permitted)
my bootloader is unlocked and I am in fastbootd.
I so far tried:
- other USB cables
- other ROM´s
- factory wiping
- flashing stock image again (which does work in both fastboot and fastbootd)
- reflashing recovery with stock one
- relocking and unlocking
- booting in to fastbootd via command and buttons
- diffrent minimal adb and fastboot versions
anyone have any ideas what I am doing wrong?

ianspy1 said:
Hi I am really struggeling here ... Everytime I try to flash system it ends with
writing 'system_b' 2/3...
FAILED (remote: Operation not permitted)
my bootloader is unlocked and I am in fastbootd.
I so far tried:
- other USB cables
- other ROM´s
- factory wiping
- flashing stock image again (which does work in both fastboot and fastbootd)
- reflashing recovery with stock one
- relocking and unlocking
- booting in to fastbootd via command and buttons
- diffrent minimal adb and fastboot versions
anyone have any ideas what I am doing wrong?
Click to expand...
Click to collapse
I am in no way a professional like other members here who probably can give you better advice but I was more successful when I downloaded platform tools version 26.0.0. I wasn't successful on my device but after using a older version I was able to get a different set of errors. But I also at the end was unable to flash. Maybe this will help you ?

gatorz_4z said:
I am in no way a professional like other members here who probably can give you better advice but I was more successful when I downloaded platform tools version 26.0.0. I wasn't successful on my device but after using a older version I was able to get a different set of errors. But I also at the end was unable to flash. Maybe this will help you ? My hope is that with that version you will be successful? Another person told me to redownload the ROM and try with a fresh one.
Click to expand...
Click to collapse

Gotta love how unsupported this ROM is... Or just busy dev...

[UNOFFICAL][TWRP][Recovery] TWRP 3.5.2_9-2 [ysl][UNIFIED]

{
"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:
#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:
- Always updated with latest twrp changes
- Decryption Works "Official miui, custom roms"
- Works with any 32bit and 64bit roms
- Treble enabled
- F2FS support
- FDE/FBE & SAR/NON-SAR Unified support
Notes:
- It works only with pie fw
Install guide: "You must have the Bootloader unlocked"
- Install ADB & Fastboot tools on your pc
- Go on fastboot mode
- Run "fastboot flash recovery yourrecoveryimage.img"
- Reboot and enjoy
Bugs:
- Maybe something i didn't saw during my usage, in case send logs if you encounter in a bug
Download:
Here
Support Group:
Here
Source code:
TWRP
Device tree
Kernel
Credits:
@Dees_Troy
@krasCGQ
@mahajant99
@Lostark13
@m_vaisakh
ROM OS Version: Android 9
ROM Kernel: Linux 4.x
ROM Firmware Required: pie
Based On: OMNI
Version Information
Status: Stable
Current Stable Version: 20210130
Stable Release Date: 2021-01-30
Created 2021-01-30
Last Updated 2021-01-30

11/08/2021 Build
HTML:
Source Changelog:
- Synced with latest twrp.me changes
- Merge aosp/pie-gsi changes
- Update f2fs-tools to v1.14.0
- Update nano to v5.2
- Squeeze performance while flashing a zip
- Start progress bar thread only when is required
- General fixes
Device Changelog:
- Build toybox
- Build userspace ExFAT driver
- Fixup encryption issues
- General fixes
Old Builds:
Spoiler
01/03/2021 Build
HTML:
Device changelog:
- Synced with latest twrp changes
- Readd /cust on partitions list
- Backup /persist as image
- Rename /sdcard1 to /external_sd
- General bug fixes

New update is out https://androidfilehost.com/?fid=17248734326145746072
changelog https://forum.xda-developers.com/t/...p-3-5-0_9-1-ysl-unified.4226279/post-84394617

twrp release: 3.5.1_9 · TeamWin/[email protected]
Change-Id: I13dfadea507d7050cec35d00d5cfabdf25462b15
github.com
everything is setted up for the first unofficial 3.5.1 release
waiting for seeing whole changelog on twrp.me ...

interesting, even if i write it, and i can see in cmd that is erasing and writing, getting okay message, bootloader is unlocked, and full adb acces, and still, my recovery is still the stock one, may im doing something wrong?

gherv1 said:
interesting, even if i write it, and i can see in cmd that is erasing and writing, getting okay message, bootloader is unlocked, and full adb acces, and still, my recovery is still the stock one, may im doing something wrong?
Click to expand...
Click to collapse
Reboot directly to twrp after you flashed it via fastboot "vol + and power button"
Miui replace the custom recovery with the stock one

Its_Vixano said:
Reboot directly to twrp after you flashed it via fastboot "vol + and power button"
Miui replace the custom recovery with the stock one
Click to expand...
Click to collapse
maybe this is what i was doing wrong, but i've one problem, my buttons band is not working, it's kinda removed from the phone, long story )
so i can boot recovery just from adb
i typed adb reboot bootloader
fastboot flash recovery twrp.img
fastboot boot twrp.img (and is just staying stuck there forever)
as i know is unlickely to restart into recovery from fastboot. Exist some solutions for me in this case?
Tried fastboot reboot and after that adb reboot recovery, so it's start making logic i need to boot directly onto recovery.
It's possible to flash it from test point?
also, i was thinking of a downgrade, but idk if ill work to reboot from fastboot and after that adb reboot recovery.

gherv1 said:
maybe this is what i was doing wrong, but i've one problem, my buttons band is not working, it's kinda removed from the phone, long story )
so i can boot recovery just from adb
i typed adb reboot bootloader
fastboot flash recovery twrp.img
fastboot boot twrp.img (and is just staying stuck there forever)
as i know is unlickely to restart into recovery from fastboot. Exist some solutions for me in this case?
Tried fastboot reboot and after that adb reboot recovery, so it's start making logic i need to boot directly onto recovery.
It's possible to flash it from test point?
also, i was thinking of a downgrade, but idk if ill work to reboot from fastboot and after that adb reboot recovery.
Click to expand...
Click to collapse
Might be tricky but it should be fine
- Get the stock boot img from a stock recovery rom, or download this "took from china latest release, should works fine"
- Patch it with magisk app "it will disable dm verity"
- Reboot to bootloader and flash the patched boot img "fastboot flash boot patched_boot.img"
- Reboot to system
If magisk app say that magisk is installed, you can flash the twrp with flashify
I forgot also to say that fastboot boot is broken on our device "the reason is still unknown"

Its_Vixano said:
Might be tricky but it should be fine
- Get the stock boot img from a stock recovery rom, or download this "took from china latest release, should works fine"
- Patch it with magisk app "it will disable dm verity"
- Reboot to bootloader and flash the patched boot img "fastboot flash boot patched_boot.img"
- Reboot to system
If magisk app say that magisk is installed, you can flash the twrp with flashify
I forgot also to say that fastboot boot is broken on our device "the reason is still unknown"
Click to expand...
Click to collapse
Ok, i tried right now, flashed it, and now rebooted to the system, i see miui logo, and is not moving from there ) and i've the latest stock update, i guess is similar to global ver

removed the battery, and now is fastboot bootloop, so i guess the boot.img was the problem

gherv1 said:
removed the battery, and now is fastboot bootloop, so i guess the boot.img was the problem
Click to expand...
Click to collapse
I had only this one on my drive disk, try to extract it from https://bigota.d.miui.com/V12.0.2.0.PEFMIXM/miui_HMS2Global_V12.0.2.0.PEFMIXM_668a87d737_9.0.zip
sorry for the inconveniences

Its_Vixano said:
I had only this one on my drive disk, try to extract it from https://bigota.d.miui.com/V12.0.2.0.PEFMIXM/miui_HMS2Global_V12.0.2.0.PEFMIXM_668a87d737_9.0.zip
sorry for the inconveniences
Click to expand...
Click to collapse
There is something else wrong, i just downloaded this one https://xiaomifirmwareupdater.com/miui/ysl/stable/V12.0.2.0.PEFMIXM/
flashed the boot img, and it's still stuck at miui logo, i mean, i have some experience with dead phones, but this one is very strange, oopa, worked now, so it was just the cn boot img, and needed a little bit of time to boot with his normal one
ill try to mod with magisk and flash again, i keep you in touch
I also flashed cache.img, i don't know if helped, but just in case if someone else have same problem

O yeaa, is working ) i can't belive it, i searched a lot on the internet, and not even one solution was helping me, so everything you need is just a smart person who know even better than the internet, thanks you a lot mate, now i can use google camera yay

gherv1 said:
O yeaa, is working ) i can't belive it, i searched a lot on the internet, and not even one solution was helping me, so everything you need is just a smart person who know even better than the internet, thanks you a lot mate, now i can use google camera yay
Click to expand...
Click to collapse
You are welcome

New update is out https://androidfilehost.com/?fid=7161016148664784278
changelog https://forum.xda-developers.com/t/...p-3-5-0_9-1-ysl-unified.4226279/post-84394617

Greetings to the creators of twrp recovery and to the moderators of this thread
I wonder if anyone knows if there are themes to customize this version of recovery 3.5.2 9 0?
Thanks

Development [RECOVERY][OFFICIAL] TWRP 3.7.0-3 for Galaxy A52s 5G

Team Win Recovery Project
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 doing this to your device
* 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.
*/
{
"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"
}
Disclaimer:
I am not responsible about any damage of any kind that this custom binary may cause.
Please pay attention to this post & related ones before proceeding and follow the guide correctly. I will not offer support for any issues that have been already stated.
Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox features. It can't be resetted in any way, so think twice before flashing this.
Bugs can be reported here in XDA or via the community's Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs.
What's TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, root your device and more.
Read more about TWRP here: https://twrp.me/about/
How do I flash and set it up correctly?
Please notice that the following guide is meant for full stock devices, if you've already rooted your device you can skip it and flash directly the recovery without any extra steps.
Before starting, make sure to backup all your data and important files stored in your phone, since this procedure will format your data partition.
Download Odin3, Samsung's Android USB Drivers, the latest TWRP's tar and a disabled vbmeta image.
Make sure your phone's bootloader is unlocked, follow the guide below in case it isn't:
Spoiler: Unlock the bootloader
Open the Settings app, enter Developer Options and enable OEM unlocking (If you don't see Developer Options, enter into About phone>Software info and tap "Build number" 10 times to show it).
Enter Download Mode: to do so power off your device, connect it to a computer via an USB cable and hold both volume up and volume down buttons.
Long press volume up to unlock the bootloader. This will wipe your data and your phone will automatically reboot.
Go through the initial setup. Skip through all the steps since data will be wiped again later. Make sure to connect the device to Internet during the setup.
Enter Developer Options and check that the OEM unlocking option exists and is grayed out. This means our bootloader is unlocked and your phone has no KnoxGuard lock set.
Connect your phone to your PC and boot in Download Mode (power off your device and hold both volume up and volume down buttons).
Open Odin3, select the TWRP tar by clicking the "AP" button and the patched vbmeta tar by clicking "USERDATA", then press the Start button.
Reboot your phone in recovery mode: while it still plugged in your PC, hold both the power and volume up buttons.
Once TWRP has booted you need to format again your data partition in order to be able to boot in system again. To do so touch Wipe>Format Data and follow the instructions in screen.
Bugs:
Decryption will only work if no password/PIN/pattern is set in Android (One UI).
Download:
Galaxy A52s 5G (a52sxq):
twrp.me
Bootloader/Modem collection:
GitHub
Sources:
Kernel source code: https://github.com/BlackMesa123/android_kernel_samsung_sm7325/tree/sep-14.1/twrp-12.1
Device tree: https://github.com/TeamWin/android_device_samsung_a52sxq
Changelog:
Check Post #2.
A52s 5G Community Telegram Groups:
General
Development
Credits:
Samsung for the kernel source code
TeamWin for their awesome recovery
@Captain_Throwback for his help and troubleshooting
@ShaDisNX255 & @ronardnx for testing out the recovery

Changelog:
Please note that this only includes device-specific changes. For global TWRP changes, go to twrp.me.
20230104 (3.7.0_12-3)
- Fix /vendor backup restoring
20221224 (3.7.0_12-2)
- Updated kernel to DVK5
- Support Android 13 decrypt with no password
- Fix /efs, /sec_efs backup
20221208 (3.7.0_12-1)
- Fix fastbootd
- Disable stock recovery patching in /vendor
20221012 (3.7.0_12-0)
- First release

It's been a while since I released something here in XDA. I'm happy to join the modding train again with this custom recovery, hoping to see more cool stuff come out for this device soon

Amazing work, always happy to test. Great step towards more development.

Nice job plus Nice instructions. Thanks a lot

Most peru dev

Hi, gr8 to see TWRP for this device.
If my phone is already rooted, can I just install without data loss?

Brilliant!! Thankz for this. Now bring on custom stuff lol.

Essentrix said:
Hi, gr8 to see TWRP for this device.
If my phone is already rooted, can I just install without data loss?
Click to expand...
Click to collapse
Am a bit also confused with all this files.. i suppose recovery image is the only thing needed for a allready rooted phone right?

Finally!!

Essentrix said:
Hi, gr8 to see TWRP for this device.
If my phone is already rooted, can I just install without data loss?
Click to expand...
Click to collapse
BlueChris said:
Am a bit also confused with all this files.. i suppose recovery image is the only thing needed for a allready rooted phone right?
Click to expand...
Click to collapse
Yes, the guide is for those that are starting with an unrooted device. If you already had the old TWRP or have installed a patched vbmeta you can just flash the new recovery.img without any extra steps

New minor build released to mitigate the /data and /efs backup errors. If you're still having issues, try to delete the /sdcard/TWRP folder and reboot again to recovery.

New version works perfect. Thanks!!

BlackMesa123 said:
Yes, the guide is for those that are starting with an unrooted device. If you already had the old TWRP or have installed a patched vbmeta you can just flash the new recovery.img without any extra steps
Click to expand...
Click to collapse
Ok i was rooted and i passed only the recovery. Now i rebooted in twrp and the phone asks for a password of myne... i tried to put my pin and then it tries to decrypt FBE it says for user 0 but stays there for ever...

BlueChris said:
Ok i was rooted and i passed only the recovery. Now i rebooted in twrp and the phone asks for a password of myne... i tried to put my pin and then it tries to decrypt FBE it says for user 0 but stays there for ever...
Click to expand...
Click to collapse
Seems like decrypt currently works when no lockscreen password/PIN is set. I'm going to look at this

BlackMesa123 said:
Seems like decrypt currently works when no lockscreen password/PIN is set. I'm going to look at this
Click to expand...
Click to collapse
I changed to pattern and the same is huppening. If i try to change to nothing it will remove my fingerprints etc.. its not biggy but this could be a solution for me?

Yeap i changed to none and is working now.... i will do a full backup now and then i will put the security on again.
Thx anyway.. a full phone backup was what i was needing.

BlueChris said:
I changed to pattern and the same is huppening. If i try to change to nothing it will remove my fingerprints etc.. its not biggy but this could be a solution for me?
Click to expand...
Click to collapse
Unfortunately with the current build you'll have to choose between disabling encryption in your /data partition or remove any kind of lockscreen protection. I'm already working on fixing this issue, found out it's due to gatekeeper not working correctly

BlackMesa123 said:
Unfortunately with the current you'll have to choose betweeb disabling encryption in your /data partition or remove any kind of lockscreen protection. I'm already working on fixing this issue, found out it's due to gatekeeper not working correctly
Click to expand...
Click to collapse
No worries m8, take your time and again thank you for this.

BlueChris said:
No worries m8, take your time and again thank you for this.
Click to expand...
Click to collapse
I have some bad news: unfortunately decrypt with password/PIN set in lockscreen is not supported in the TWRP itself, so posting a new build with fixed gatekeeper would be useless anyway. As soon as the android-12.1 TWRP branch fixes this issue I'll be posting a new build for the recovery, hoping this issue will be addressed asap