yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] forman forman:
Hello, I have a Samsung j2 phone (model j200g) and it shows me a black screen (in place of the Samsung logo) after the boot, and I want a solution from you, I will show you what I did after this problem occurred.

- When this problem occurred, I did not know what to do, so I had to flash it with its own file, and after the success of the flashing process, the same problem remained.

**I tried to flash it several times, but same problem, so I had to flash it with a custom ROM (lineage os 14.1).

-After failed attempts to flash, I installed the recovery module (twrp) and copied the custom rom file (lineage os 14.1) to the phone via otg, I flashed the custom and the installation succeeded. I turned on the phone and the “samsung galaxy j2” screen appeared, and then the custom ROM boot screen came, but here the boot (the circle that rotates for the custom ROM) remained as it was moving indefinitely. I left it for a whole day and it is still in this state.

I want you to solve this problem. I spent days looking for a solution to this problem.
[Android Q&A, Help & Troubleshooting] alecxs:
I understand you have flashed full Samsung ROM/firmware BL AP CP CSC from Odin3, then installed TWRP and installed LineageOS on boot + system. In case you haven't already done, disable dm-verity with this zip

https://build.nethunter.com/android-tools/no-verity-opt-encrypt

don't forget to format Data (wipe - advanced - format - type 'yes')
[Android Q&A, Help & Troubleshooting] forman forman:
thanks i will try, but the link not working
[Android Q&A, Help & Troubleshooting] alecxs:
check your VPN, link is fine
[Android Q&A, Help & Troubleshooting] forman forman:
i tried this but same problem
[Android Q&A, Help & Troubleshooting] alecxs:
try with stock ROM no TWRP no modifications.
[Asus Zenfone Max Pro M2 ROMs, Kernels, Recoveries,] DARSHAN MEVADA:
Project Xtended For X01BD​

View attachment 5829485​

#Xtended #UNOfficial #ROM #T #X01BD

Project Xtended XT - UNOFFICIAL | Android 13

Size: 0.93GB

Released: 31/01/'23

▪️ Download

▪️Changelog

Initial Stable Build

• Notes:

- Decrypted by default

- Clean flash recommended

- 4.4.302 Kernel

Flashing Guide :

- Rom + Permissiver + Gapps

Donate:

​
[Asus Zenfone Max Pro M2 ROMs, Kernels, Recoveries,] roirraW "edor" ehT:
<Moderator Note>: Kernel source missing, and Gcam & Permissiver Telegram links require Telegram registration in order to download.

@DARSHAN MEVADA, due to you previously having issues with Kernel Source links in your OPs, I can only give you 24 hours from now to fix your OP. Also, the Gcam and Permissiver Telegram links require Telegram registration in order to download, which goes against Post #5 "WhatsApp/Telegram Groups and Channels - Going Forward" from the stickied thread at the top of every section Guide to Asus Device Forums (Please Read before Posting), which also details the requirements for Development threads in Post #2 "XDA-Developers and the GPL" and Post #3 "ROMs, Kernel, Recoveries, & Other Development Forum".

I won't bother to quote the relevant parts of those posts, as you should be familiar with these by now.

Please PM me when these things are fixed, or in 24 hours I will remove all links from the OP and close the thread. Also, PM me if you have any questions about this, or if, once the thread is closed, and if you want to fix it, then just click the Report button in the bottom right corner of your OP and the next available moderator will re-open your thread so that you can fix it within 24 hours of re-opening it.

Thank you,

@roirraW "edor" ehT

Update: Due to not even receiving at least a response about this, I've closed the thread. Please use the Report button at the bottom right of your OP when you're ready to fix these items. If you post any new development threads without a direct link to the Kernel source, and with more than one Telegram link, but that Telegram link must not require Telegram registration if it's for downloading something related to the development), then you will receive an official warning next time. Once you receive enough official warnings, further action may be taken against your account.

The GPL legally requires everyone including XDA to link to the updated kernel source used in any Android ROM that's published on XDA.
[Google Pixel 7] bobby janow:
Does anyone know if it was pulled or simply never uploaded to the image pages? Full / OTA not available but probably by the time I post this it will be there.
[Google Pixel 7] V0latyle:
Just checked, it's there:

OTA - TQ1A.230205.002

Factory image
[Google Pixel 7] salamdiab:
404. That’s an error.
[Google Pixel 7] bobby janow:
I'm still getting an error. But I'll keep trying or just do the OTA this time although that is so annoying at optimizing.

@salamdiab Same here.
[Google Pixel 7] Lughnasadh:
I don't think it was pulled because they're available on Android Flash Tool. We'll just have to be patient. Same thing happened several months ago.
[Google Pixel 7] salamdiab:
i think you are correct

thanks
[Google Pixel 7] Lughnasadh:
Plus, some are already reporting they are receiving the OTA.
[Google Pixel 7] V0latyle:
You're an error...
[Google Pixel 7] xdagee:
give it sometime, and download later
[Google Pixel 7] poit:
Just got the T-Mobile OTA. That was quick (for once)
[Google Pixel 7] JimSmith94:
I have an unlocked Pixel 7 that I use on T-Mobile. Should I use the T-Mobile update or the regular one?
[Google Pixel 7] Lughnasadh:
Use T-Mobile.
[Google Pixel 7] poit:
My phone is an unlocked P7 on T-Mo, and I was sent the T-Mo update OTA. I'd love to know what the difference is between the base update and the T-Mo version. BTW, the OTA update was only 21MB.
[Google Pixel 7] JimSmith94:
Thanks for the quick reply, that worked! 👍🏼 This is the first update I recall that had a specific T-Mobile build. Any idea what is different?
[Google Pixel 7] kevinireland11:
I got the OTA about 9PM (Ireland)
[Google Pixel 7] kevinireland11:
Seems to be snappier and app opening times and system app opening seems to be faster and smoother
[Google Pixel 7] Lughnasadh:
No clue at the moment. T-Mobile was having problems with last month's update (most people on T-Mobile didn't get an OTA update) so I would imagine some of it addresses the problems they were having.
[Android Q&A, Help & Troubleshooting] D€INOS:
Is there a way to pin apps to stay alive in RAM for AOSP A13 like many of the closed flavors like One UI, OOS etc ?

With or w/out root.
[Miscellaneous Android Development] Sammm77:
View attachment 5829487

#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.
*/

About

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.

Features

- Status bar customization

- New rounded icons added on dashboard

- Dark mode

- Navigation bar customization

- Settings + Advanced Settings

- Flash Magisk

- Clear fingerprints

- Recovery Locking , Pin or Pattern lock

- Hal3 / CameraAPI2 enabling/disabling

- Oreo+ Reboot menu style

- Redesigned lock screen interface

- Flashlight

- Magisk manager - Enable, disable or delete magisk modules right from SHRP

- Text Editor

- Theme, Lock, Addon survival

- Some OTA functionalities

- SHRP Injection (A/B)

- Magisk injection

- and many more, flash right now to find out

Instruction

- Download IMAGE

- Reboot to custom recovery

- Flash SkyHawk how ramdisk

- Reboot recovery

- Enjoy

Issues

You tell me

Download

Here

Links

- Kernel Source

- SHRP Github

- SHRP Website

- TWRP Source

Build Maintainer: @Sammm77

ROM Firmware Required: Android 12

SHRP Version: 3.1

TWRP Version: 3.7.0-12

TWRP by: @Venkat.Yadlapati

Build Status: Stable

Created: 2023-02-06

Last Updated: 2023-02-06​
[Google Pixel 7] mautz001:
Greetings

is it just me or does "Faster Voice typing " / "Assistant voice typing" isnt available when rooted?

I always get the "You cant currently use assistant voice typing" error :(

Anyone else has this problem? Germany (de-de) should be supported and when unrooting it works.
[OnePlus 9 Pro] Bulauski2005:
Hey I'm on F.18 and cannot adjust screen color anyone else having this issue ?
[OnePlus 9 Pro] SaintZ93:
Works for me. F.18 TMO Converted as well. Unlocked, rooted. The whole 9 yards

Do a factory reset or use twrp to dirty flash F.18
[OnePlus 9 Pro] Bulauski2005:
With root access on F.18 do you have the unlocked bootloader warning screen ? Also can you run Substratum theme engine modules with Magisk ?
[OnePlus 9 Pro] SaintZ93:
Yes, I have root access and bootloader unlocked warning. That is due to OnePlus keeping the Qualcomm code for it in. Has no affected on day to day use. As for Substratum, I don't use it. I also don't see it working well on OOS13 tbh since Android 13/OnePlus modifications to theming is completely differently coded than previous Android versions.
[OnePlus 9 Pro] Bulauski2005:
What are some cool things I can do with F.18 rooted ?
[ASUS ZenFone 8] hawkins22:
I've managed to successfully install LineageOS 19.1 on my Zenfone 8 but I didn't realise you needed an entirely different release to use MicroG.

So I am now trying to install the LineageOS for MicroG release but I'm running into problems:

The MicroG release is a few weeks older than the LineageOS one. When I tried installing it I got an error "SPL is considered a downgrade" and it wouldn't let me install it.

The MicroG release doesn't provide a `vendor_boot.img` file which is required according to the LineageOS instructions. I tried using the file from the regular LineageOS release and it seemed to work the first time but now it won't boot into the recovery mode at all; it just boots into the bootloader menu.

I saw people saying that the MicroG release is missing some img files but I used the payload-extractor Python script and I cannot see any difference between the list of files in the MicroG release and the original LineageOS one. They both contain 29 img files.

I saw posts in the development thread that people are having similar struggles so I'm not sure how to proceed.

Ultimately, my request is: can someone please outline an easy-to-follow approach on how to install LineageOS with MicroG on the Zenfone 8?
[ASUS ZenFone 8] bnsmb:
AFAIK the LineageOS does not support SignatureSpoofing so MicroG will work in LineageOS but only with limited functionality.

Therefor I would recommend to install another OS:

OmniROM https://omnirom.org/

The OS images for OmniROM for the Zenfone 8 can be downloaded here:

https://dl.omnirom.org/zenfone8/

A new OS image of OmniROM with MicroG is created every Sunday.

The OmniROM image can be installed via sideload using the recovery image from the LineageOS.

And it works without problems (including MicroG) You can even install a patched version of the original playstore that will work with MicroG.

In case you want to stay with the LineageOS I recommend to use the LineageOS image without MicroG and use the NanoDroid image (which contains MicroG) from https://nanolx.org/

I used NanoDroid (installed as Magisk Module) on my previous phone several years for which no OS image with integrated MicroG exists.

regards

Bernd
[ASUS ZenFone 8] hawkins22:
Thanks for the recommendation. I would prefer to stick with LineageOS because of the larger community.

NanoDroid looks good but I don't think it'll be suitable. It looks very complicated and talks about patching ROMs for signature-spoofing support. It also doesn't actually say how to install it (the documentation literally just says "install NanoDroid" as one of the steps...) and finally it only supports Android 11 at the moment.

If anyone else has hints about using MicroG with LineageOS on a Zenfone 8 please let me know. I feel like it really shouldn't be this hard.
[ASUS ZenFone 8] bnsmb:
Understand

But for the records:

Signature-spoofing is only required to use all features of MicroG , e.g. to use the patched Playstore. If you don't need that you can ignore this.

The best method (IMHO) to install NanoDroid is:

- install Magisk into the booot partition

- install the ZIP file with NanoDroid using TWRP

Nanodroid will then install MicroG as Magisk Module .

regards

Bernd
[ASUS ZenFone 8] lama02:
Hello,

The issue is due to the fact that LOS+MicroG has a long delay in releases (at the time of this message, the latest LOS version is 2023-02-03 and the latest LOS+MicroG 2022-12-22). I think it is an issue because the main site announces a build every two weeks, and there are some tickets in their Git repository about this.

Anyway, I had the same issue few weeks ago and I managed to install LOS+MicroG using an old vendor_boot image; indeed you have to use the one provided by the LineageOS wiki, but you have to use one older than the LOS+MicroG release to avoid the SPL issue.

Unfortunately, I had a look and the previous version was deleted on their website since I installed my phone and I can't provide the one I used because I removed the file...

So I'm afraid you have to wait a new LOS+MicroG build or find a old vendor_boot.img to proceed.

But I agree with you: it's a shame that there is no straightforward way to install LOS+MicroG. It was easy in the time, but now it's more complicated to manage due to phones specification (I guess, I'm not a ROM dev) - but yes I think that discourage a lot of people to use it.

Good luck.
[ASUS ZenFone 8] Mario545:
Yeah, that's why "LineageOS for microG" exists in the first place. It is a fork of LineageOS where signature spoofing was enabled. So, there is no issue using LineageOS for microG. Please educate yourself before posting things like this.

There are (or at least in the past were) indeed some files missing from "LineageOS for MicroG" for the Asus Zenfone 8. It is/was a bug confirmed by the developers. I reported it to them, maybe they fixed it in the meantime. This would be good news! I haven't checked for a while.

However, then I don't understand why you say "The MicroG release doesn't provide a `vendor_boot.img`". So why exactly is this file missing and where did you find it in the official LineageOS? And for what step do you need it? I don't remeber that I was using this file for installing LineageOS. Only Magisk needed that file. But it was easy to retrieve from the extracted payload.
[ASUS ZenFone 8] hawkins22:
I managed to install it successfully using TWRP instead of Lineage's own recovery image. Maybe TWRP simply doesn't care if you're "downgrading" and lets you flash anyway?

The final step-by-step process I used was something like this:

Unlock the phone's bootloader using the official ASUS unlocking tool APK.

Restore the phone to its stock Android 12 state using the ASUS "raw" image (instructions):

https://dlcdnets.asus.com/pub/ASUS/...KS-31.1010.0410.61-MR0-2204-user-20220422.zip

Flash the "vendor_boot.img" file from the regular LineageOS release as detailed in the instructions.

Install TWRP recovery instead of the LineageOS recovery image.

Use TWRP recovery to flash the LineageOS-MicroG ROM.
[ASUS ZenFone 8] hawkins22:
The vendor_boot.img is required according to the LineageOS installation instructions and is provided as a separate download on the same page.

However after extracting both the LineageOS and the LineageOS-MicroG releases, I believe the vendor_boot.img files are actually identical (same filesize) so you can probably use them interchangably anyway.
[ASUS ZenFone 8] Mario545:
I see, probably was not required when I was installing an earlier version of LineageOS.

Anyway, vendor_boot.img should additionally be included in your payload file from the archive. The one they provide for download is probably just an extracted one to make it easier.
[ASUS ZenFone 8] bnsmb:
AFAIK the vendor_boot.img is also required by the LineageOS recovery image necessary to install the LineageOS image.

Therefor it must be installed before booting the LineageOS recovery.

regards

Bernd
[ASUS ZenFone 8] magicmckinney:
The best way to install any rom with a Windows computer is:

1. download and extract the rom (unzip).

2. take the payload.bin and extract it with payload dumper from here https://xdaforums.com/t/root-androi...payload-dumper-magisk_patched-guides.4175033/.

3. put all these files in your original extracted rom folder. This will give you all files to flash in 1 folder.

4. Boot your phone to the bootloader screen and hook it to your computer

5. open the folder where your extracted files are. There hold down shift and right click in a blank space in your folder. That will bring up the menu with OPEN POWER SHELL HERE. click there and you will powershell open that you can flash the following files in.

5. Fastboot flash 4 files to your phone, DTBO, VBMETA, BOOT, & RECOVERY. The flash format is FASTBOOT FLASH DTBO DTBO.img.

6. Once these files flash properly, You can then hit volume up until it says Recovery Mode and boot to Recovery

7. I usually Factory Reset before I install the rom but it can be done after and work fine.

8. Flash the Rom by hitting Apply update and typing ADB Devices to make sure ADB is fired up and recognizes your phone. Once it is ready ADB Sideload your rom. The easiest way is to type adb sideload and drag your rom into powershell. as long as you have 1 space after sideload it will work.

I know some of this basic stuff if your an experienced flasher but the original question was how to overcome the flashing an older rom. You can go back and forth with this method between A13 & A14.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] pchc_lx:
Hey all, I'm trying to reset my SM-T230NU to as close to Factory-Reset as possible including removing TWRP / CM etc

Could anyone point me toward boot image / stock recovery / ROM etc?

I think I remember how to do all the flashing well enough, just need the links. Thanks!
[Galaxy Tab 4 Q&A, Help & Troubleshooting] ze7zez:
Samsung GALAXY Tab4 7.0 Wi-Fi Firmware Download SM-T230NU Free Download

Samsung GALAXY Tab4 7.0 Wi-Fi Firmware Download SM-T230NU Free Download ⭐ Official and fast update ⭐ Max speed and free download ⭐ Best Samsung Galaxy website

samfw.com
[Redmi K20 Pro / Xiaomi Mi 9T Pro Questions & Answe] Tahsin Can:
Hello friends. I am using 9t pro. I went through Vayu. It was resetting when I put it in fastboot mode on Vayu. How do I reset on this device?View attachment 5829559
[Device Repair] Fetty5677:
My S20 Ultra LTE dual sim keeps detecting a SIM in the second SIM slot which is making the phone lose service. Is there a way to disable the SIM slot permanently or convert the phone through the firmware to single SIM. PLEASE HELP!!!!!
[Samsung Galaxy A20 Questions & Answers] arsfr:
Hello, XDA!

I know that A205U cannot be bootloader unlocked but I have recently found this thread, https://xdaforums.com/t/system-shel...devices-no-bl-unlock-required.4543071/page-25 which I think could be helpful for unlocking the A205U's bootloader as it makes us gain access to the system shell. Can someone please tell me if we can make the bootloader unlock option appear with this exploit?

Any response is appreciated.

Thank you!
[Google Camera Mods] Schroeder09:
Is there anyway to enable this with root? I was guessing this is probably just an option that's toggled "false" in one of the camera files that might be accessible with a file explorer. If so, what's the file path? I'm on A13 on a pixel 7 pro. I'm on the latest security update and have magisk 24.2 if it matters.
[Google Camera Mods] AlexS8519:
How to make it work on Xperia 1IV? Please help!
[Moto G Power (2021)] satanzmoma:
Its specifically threw total wireless. An its updated so I am stuck with it useless at this point. Anyone figured out a way around this yet?
[ASUS ROG Phone 5 / 5s] Tmthenu:
Greetings all. I'm hoping you can help me with my predicament. I followed the instructions here on rooting the Asus rog phone 5. I flashed the twrp recovery and install the magisk zip and when I found that it wasn't booting I tried it again but this time I change the storage to B. (that's where the problem begins).

I'm now in a boot loop. I tried changing slot (permission denied). I tried flashing the recovery but flashing non-hlos image is not allowed in locked state. I tried flashing unlock but permission is denied.

My situation is made more complicated as I don't have a pc. Only a 2008 laptop with Linux Mint installed (further exacerbated when now I cannot flash through Linux because the battery level is too low).

My only option to flash is through the Bugjaeger.

Anyone has advice to fix this problem?
[ASUS ROG Phone 5 / 5s] Andrologic:
Have you tried flashing a clean version of your boot.img back to your active slot? A RAW flash should clear things up too. IDon't know what butjaeger is however, you may need proper fastboot access...
[ASUS ROG Phone 5 / 5s] Tmthenu:
Attached is the bugjaeger terminal. It's an app from playstore.

Tried flashing the boot img

$ fastboot flash boot /storage/emulated/0/Android/data/eu.sisik.hackendebug/cache/cached_fastboot_imgs/boot.img

Sending 'boot_b' (98304 KB)

OKAY [ 3.679s]

Writing 'boot_b'

OKAY [ 0.149s]

Finished. Total time: 3.891s

Still won't boot. Any more ideas? Much appreciate it 🙏🙏🙏
[ASUS ROG Phone 5 / 5s] Doodler-12:
Similar problem with me I accidentally wiped all my system and stuck in fastboot and I only have access to bugjeager I tried flashing fastboot rom via bugjeager but I don't know why but it's taking so much time to flash system file I left it for 5 hours but it still won't flash I don't know what to do now . It was my first time flashing a custom rom and now I am stuck in fastboot my device is soft bricked 😢😢