yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] aer0zer0:
Did you try

fastboot reboot fastboot

It should take you to fastbootd (not certain if it's unlock protected) then try to sideload a full ota from there
[Google Pixel 7 Pro] badabing2003:
Can you explain what you mean by:

And why would a wipe be necessary and fix the issue?

I think you're also making an assumption that the previous update was done through OTA and not a Factory Image.

When you flash a factory image (which is by default to the active slot), one of the things it flashes is system-other image, which is basically the *dex files, this is flashed to the inactive slot's system partition, effectively making that slot unbootable even if one manages to get around certain verifications in place.

Those files get copied to active partition on first boot.
[Google Pixel 7 Pro] tonydigimon:
< waiting for any device >

fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

PS C:\Users\tfcha\Downloads\platform-tools_r34.0.3-windows\platform-tools>

seems it is really a rom problem that nothing I can do now
[Google Pixel 7 Pro] badabing2003:
you can't use Android Platform Tools v34.0.3 to boot to userspace fastboot (fastbootd)

Switch to using Android Platform Tools 33.0.3 if you want that.
[Google Pixel 7 Pro] tonydigimon:
tried r33.03 running fastboot reboot fastboot

Rebooting into fastboot OKAY [ 0.000s]

< waiting for any device >

fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.

PS C:\Users\tfcha\Downloads\platform-tools_r33.0.3-windows\platform-tools>
[Google Pixel 7 Pro] WoKoschekk:
switching back to the previous slot could be a problem due to some (system) files stored on /data, modified by the new firmware build. in the worst case it ends up in a bootloop.

what I mean is: you can switch the firmware by switching the slots, but you can't switch back the files stored on /data. if any of them are incompatible with the old firmware you are lost.

yes, I do.

that's correct.

because /system_b (system_other) stores no files to boot the system.

no, they get copied to /data/preload. I assume they will then get copied to the dalvik-cache. This way they needn't to get compiled with dex2oat on first boot.

Verifying system_other Partition | Android Open Source Project

source.android.com

Spoiler content hidden.

Spoiler content hidden.

you can still use this version for a simple command. as you can see the connection isn't established (<waiting for any device>). but you shouldn't use it to flash a full firmware since Google messed up something in the 'fastboot update ZIP' command so that your device won't boot into fastbootd mode.
[Google Pixel 7 Pro] WoKoschekk:
your issue: <waiting for any device> => trouble with your drivers? device manager shows any errors when device is in fastboot mode and connected?
[Google Pixel 7 Pro] Lughnasadh:
Aside from making sure you have the correct and updated drivers installed, may also want to try different cables/ports. An A to C cable using a USB 2.0 port seems to work well for most. Maybe also try Command Prompt instead of PowerShell.
[Google Pixel 7 Pro] tonydigimon:
I don't think it is a driver issue as I can locate the device with fastboot devices. I believe the boot failure is making the device to restart so it become waiting for any device.
[Google Pixel 7 Pro] WoKoschekk:
unplug the cable and then plug it again.
[Google Pixel 7 Pro] Lughnasadh:
UPDATE: As tested by @badabing2003 on his Pixel 5, and tested on my Pixel 6 Pro & Pixel 7 Pro, it appears that if you sideload the full OTA to both slots you can switch back and forth between slots without having to first flash the firmware. This was done using the same monthly build.

What I did was:

Started with:

Platform Tools 33.0.3

A13 (May) (installed using flash-all.bat)

Rooted with Stable Magisk 26.1

Active slot=b

Sideloaded the A13 (May) full OTA

Booted up

Not rooted (of course)

Active slot=a

Then rooted with Stable Magisk 26.1

Switched slots to b (where firmware was installed via flash-all.bat method)

Tried to boot into that slot but it failed

Booted back into bootloader

Set slot back to a

Sideloaded the A13 (May) full OTA

Booted up

Not rooted

Active slot=b

Then switched slots to a and booted successfully

Slot a still rooted

Then switched slots to b and booted successfully

Slot b still not rooted

Then switched slots again back to a and booted successfully

Slot a still rooted

I know this is off topic to the OP's problem, but just thought I'd add this information given the earlier discussions.
[Realme C3 ROMs, Kernels, Recoveries, & Other Devel] @koushikdey:
<Moderator Edit>:

Thread closed and content removed! - @roirraW "edor" ehT
[Realme C3 ROMs, Kernels, Recoveries, & Other Devel] DiazPro!:
I tried to install this custom rom on my phone but sadly when I tried to flash it, it says

assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list"))error: 25

I had this problem before on other custom roms i've tried, but do you know how to fix it?
[Realme C3 ROMs, Kernels, Recoveries, & Other Devel] @koushikdey:
Use latest Pitch Black Recovery v4.0
[Realme C3 ROMs, Kernels, Recoveries, & Other Devel] DiazPro!:
Okay, thankz! I would try out the rom once my custom rom i'm using (Evolution X) bootloops
[Realme C3 ROMs, Kernels, Recoveries, & Other Devel] DiazPro!:
I tried out the ROM earlier and for some reason, the customizations thingy is missing on the settings
[Galaxy S3 Neo Themes and Apps] prototype74:
NeoInfo, a tool for the Galaxy S3 Neo​

About​

NeoInfo is a tool for the Samsung Galaxy S3 Neo which aim to figure out the bootloader, modem and camera sensor of the device. Those information are the most important prerequisites for modern Custom ROMs. Additionally it displays some more or less important information such as the current CSC, front cam type and more.

Features​

Works without root access​

Very obvious but yes, it displays your bootloader and modem versions​

Get the best possible accurate information about the camera​

Capable to detect the current battery/charger driver​

USB Host Notify and OTG Power Regulator​

Dark mode​

Requirements​

At least Android 4.4​

A Galaxy S3 Neo (Duos)​

Download/Installation​

You can get the latest APK from here. Install the App as normal APK.

Changelog​

Camera Permission​

NeoInfo needs on Android 4.4 access to the Camera to get two specific rear camera characteristics in order to check if the rear camera does actually work. On Android 5.0 or newer this permission is not required nor asked.

Source​

https://github.com/prototype74/NeoInfo
[Galaxy S3 Neo Themes and Apps] prototype74:
F.A.Q.​

Q: Does it need Root?

A: No, didn't I mention it in first post?

Q: The color of my Booloader/Modem version is orange. What does that mean?

A: Your Booloader/Modem is from 2015 release and might be outdated. If you face RIL issues or any other issue that might be related to your Booloader/Modem, consider upgrading if possible.

Q: The color of my Booloader/Modem version is red. That's not good right?

A: Yes, you have one of the

oldest

Booloader/Modem (from 2014) which will definitely cause RIL issues or bootloops at setup screen in modern Custom ROMs. You should upgrade to the latest Booloader/Modem if possible.

Q: What does SLSI_S5K4H5YB/SONY_IMX175 mean?

A: SLSI_S5K4H5YB = Samsung camera sensor | SONY_IMX175 = Sony camera sensor

Q: The app detects my camera sensor as Samsung Sensor and Vendor displays SLSI_S5K4H5YB but the camera status is Out of service. What should I do?

A: That means you either have a different camera sensor or (if you're sure its the correct sensor) your camera hardware might be broken. If the first one is the case, flash a different Firmware/ROM that supports your sensor. For example, if your Vendor displays SLSI_S5K4H5YB, flash a Sony firmware.

Q: The app detects my camera sensor as Samsung Sensor but Vendor displays SONY_IMX175 and the camera status is Out of service! Help!

A: If your camera is actually not working then you need to research how the ROM you flashed does manage that:

Does the ROM offer a camera patch? If so, flash it to fix the camera.

Does the ROM offer an option to select the camera sensor (e.g. SammyROM)? Then you selected the wrong sensor. Reflashing the ROM and selecting the other sensor should fix it.

Does the ROM offer different builds (e.g. LineageOS)? Then you flashed the wrong build. Flash the correct build to fix the camera.

Q: Vendor displays SLSI_S5K4H5YB && SONY_IMX175, does that mean I got both sensors!?

A: No, but there are two reasons why that could happen:

You flashed a camera patch fix that didn't remove the unused camera blobs

Or, the ROM developer does include both camera blobs in their builds

In this case it's not easy to figure out which camera sensor you actually have. Thus, the app cannot detect your sensor probably and displays Unknown in the camera section.

Q: Can I install the App on a different Android device than S3 Neo?

A: Yes, you can install the App on any Android device but the features the App offers will be limited as it was desinged for the Galaxy S3 Neo.
[HTC Typhoon] bubblinz:
Hi all.

I have problem with my T Mobile SDA music a.k.a. dopod 585 / HTC Amadeus

After upgrading to WM 6.1 by ALEUT everything going well but the charging.

When I plug the usb sync, LED indicator going amber, and battery indicator on LCD is charging , after a while (approx. 2-3 sec) LED going green and battery indicator is full, but if I disconnected the usb cable, battery indicator return to real state (half full on my case). It's going the same with the USB charger.

I've tried to drown the battery, still the problem persist. :confused:

FYI, I have 2 battery and resulting same problem.

Anyone could help me with this please...? Solution or suggestion would be very appreciated.:)

Regards
[OPPO Reno Z ROMs, Kernels, Recoveries, & Other Dev] BotchedRPR:
Hi. I have managed to patch the lk.bin of the Reno Z so that you can get fastboot access after unlocking the bootloader using mtkclient. I have not tested everything yet, so it's currently in beta and i can't guarantee it will work on all Reno Z phones.

I provide all of my patches here if you wish to patch the LK yourself.

And obviously:

/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this patch
* 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.
*
*/

So - how do you flash this?

I have only tested this with Android 9! This lk.bin that i've patched is from the Android 9 ROM. Downgrade if necessary.

Unlock your bootloader with MTKClient. - There are multiple guides available online, but the short version is you open MTKClient, boot your Reno Z into BROM (Vol- + Vol+ while off and while plugging in to PC) and click Unlock Bootloader under flashing tools

Files needed - If you are downgrading to Android 9 you'll have to download the ROM yourself. And if you're already on Android 9, you'll need SP Flash tool V5 with the DA for our SoC (search for MT6779 DA on any search engine) alongside with the MTK authentication bypass.

Flash! - Boot back into BROM mode, bypass the security using the MTK authentication bypass (guide), and using SP flash tool load the DA (MT6779.bin) and flash lk_NT_patched.rtf.bin as the lk partition.

You're done! - Fastboot will be available when you hold VOL- and power.

Let the development begin.

DOWNLOADS MOVED TO GITHUB, LOOK AT THE SECOND POST​

- BotchedRPR
[OPPO Reno Z ROMs, Kernels, Recoveries, & Other Dev] BotchedRPR:
Downloads moved here.

You'll also find BSDiffs for patching the files yourself, if you wish to do that.
[OPPO Reno Z ROMs, Kernels, Recoveries, & Other Dev] kailashkatheth1:
how did you do this ? , is it possible on other device
[OPPO Reno Z ROMs, Kernels, Recoveries, & Other Dev] BotchedRPR:
Reverse=engineering and patching.

What other device are we talking about?
[OPPO Reno Z ROMs, Kernels, Recoveries, & Other Dev] kailashkatheth1:
i was looking for realme device found working patcher at https://github.com/R0rt1z2/oplus-unlock
[OPPO Reno Z ROMs, Kernels, Recoveries, & Other Dev] Itz-Broken-xd:
Can u tell me how can I do the same for oppo f15

Chipset : mt6771

OS : ColorOS 11 (Android 11)
[OPPO Reno Z ROMs, Kernels, Recoveries, & Other Dev] BotchedRPR:
Can only be accomplished on android 9 for some reason
[Google Pixel 6a] driska:
i was under the impression that the unlocked bootloader warning was not possible to be removed at all, but recently i installed a custom rom (sputnik) on my other phone (s20fe) and the warning was gone... so is that only possible on samsungs or can it be done on pixels (and other phones) as well?
[Google Pixel 6a] Jan Skokan:
Hello 🤗 I think it only works on Samsung phones. I haven't seen it possible with other phone brands, but I could be wrong.🤗
[Google Pixel 6a] MrUrgit:
Pretty sure the warning was removed when I install Evolution X on my OnePlus 8 Pro.
[Realme X Questions & Answers] Bill_G:
Has anyone been able to get them to work with the Chinese variant?

I've turned on USB OTG in the settings, which is apparently required to enable them to work on other Realme devices, but to no avail.

I've also tried three different ones.

I'm running the stock RealUI v2.0 ROM, by the way.

Thanks in advance... 😎
[Red Magic 8 pro] vader2802:
Hi folks , my Nubia launcher is constantly restarting , no matter if I restart the phone . only when I clear cache & appdata then I stops until it's starting again a while later . when I use another launcher it works until some times later the default launcher is again the nubia launcher and then looping again . I cannot deactivate the stock launcher , when I change the standart launcher it works for a while . I have to rearrange my Homescreen every time . what can I do ?
[Red Magic 8 pro] tknguyencsu@gmail.com:
Download the following apk

ADB AppControl

Official website of the ADB AppControl application. Free Download. Latest release. The ultimate applications manager and debloat tool for Android devices.

adbappcontrol.com

You can use it to deactivate or even uninstall the stock launcher.
[Red Magic 8 pro] tknguyencsu@gmail.com:
You should first try to set the other launcher to be the default launcher then you do not have to deactivate the stock launcher.

Go to setting then applications then App info. Press the three dots in the upper right corner . Choose Default app settings, then Desktop. You can then set the default launcher.
[Red Magic 8 pro] vader2802:
Of course I did change the default launcher in the settings but it didn't help . it's always going back to stock after severel hours . and then it's looping
[Red Magic 8 pro] graynada:
I found it is not enough to set your preferred launcher as default, what I found worked is go in to the app settings for the Nubia launcher and clear the app defaults, then select the home button and select your preferred launcher as always. This worked for me.
[Red Magic 8 pro] Shang22:
I some ideas, but sure can help or not:Set your preferred launcher as default launcher, and then use ice box app to deactivate the stock launcher, gesture may not work after deactivate the stock launcher.

The second way is : extract the stock launcher app from an official rom, and install the stock launcher app again , to see work or not
[Advantage X7510 General] xacsx:
140 downloads are enough, only 10 thanks/feedbacks not!

i have spend a lot of time (about 3 weeks) to build this 2 roms, and i think everybody that have downloaded and use one of this roms have to say "thank you".

i will never build roms for all!

roms are only on my harddrive.
[Advantage X7510 General] theseas:
xacsx you now that I am always here with you to help and test your rom. tell me what would you like to do? appreciate your job.
[Advantage X7510 General] xacsx:
--removed--
[Advantage X7510 General] zrll2:
You're great! Thanks for all the hard work!
[Advantage X7510 General] berk_bear:
xacsx, i't really great work! Thank you very much!
[Advantage X7510 General] theseas:
hello xacsx, hope all is well with you. first of all the rom is really great. i have found two problems until now. the first one is that advance config tool cannot be opened (an error occurs) and also when u place the keyboard on the device the feature with the blue screen under the opening of the keyboard that shows notifications doesnt seem to work. otherwise the rom is very good. if i find anything else i will report it. thanx again for this great rom.
[Advantage X7510 General] xacsx:
problem fixed
[Advantage X7510 General] theseas:
No I tried the "subdisplay" in 192 dpi but doesnt work. Thanx for the registry repair will try it now.
[Advantage X7510 General] NeilM:
Did it work before? I have an operator supplied X7510, and the subdisplay has never worked :(
[Advantage X7510 General] theseas:
Yes of course it worked. I have the htc x7510 not ameo or xda flint. and it actually worked with the stock rom that came with it. I had installed realVGA and it worked in all three resolutions. Now it doesnt work at all. When I place the keyboard onto the device the screen just turns off. The subdisplay is a useful feature that I use all the time to check my notifications.
[Advantage X7510 General] cktlcmd:
Yes, subdisplay works for me in ALL dpi's: 192, 96, and 128, but I am running the stock ROM.
[Advantage X7510 General] theseas:
perhaps i should flash the latest stock rom that cmonex has posted to see if it works with all resolutions. I had tried realVGA with the stock rom that my device came with. xacsx do you mean that the german version of your rom has no problems with subdisplay? is there anybody that has flashed xacsx's wwe rom and can confirm that subdisplay works or not?
[Advantage X7510 General] NeilM:
Thx for confirming that :) I have one of the pre-release XDA Flints; 3 of us were testing them, and for 2 of us the subdisplay has never worked, regardless of which ROM or resolution is used, so I have to assume it is a hardware issue.
[Advantage X7510 General] xacsx:
i have updated the GER-Rom. Netcf now works correct without patches or registryrepair, subdisplay works with all resolutions.

i have prepared the wwe-rom, no need to repair registry for netcf, subdisplay works, advanced config tool added.
[Advantage X7510 General] theseas:
just downloaded the updated wwe rom. gonna flash and post feedback. thanx xacsx
[Advantage X7510 General] padanfain:
Just installed your ROM and I am starting to look a few things over. I wanted to switch to 96 dpi, but I can't seem to find real vga in the settings. I was able to launch it out of the windows directory... how can I create a settings shortcut for this?

Thanks for taking the time to put this together, I really appreciate it.
[Advantage X7510 General] xacsx:
oops, have forgotten again ?? (to make a shortcut to settings or programs for realvga). use fileexplorer (not totalcommander) to make a shortcut. tap realvga > copy, go to start menu > settings or programs > tap on "create shortcut". otherwise you can make it on your computer after connecting with active sync (xp) or device center (vista)
[Advantage X7510 General] padanfain:
Thanks.

Last question...

This was happening with the stock rom and I was hoping it would just go away with yours. When I plug the thing into a power source, be it computer or wall, the screen randomly turns on and off. Does anyone know why this happens and how I can fix it?
[Xiaomi Poco F5 / Redmi Note 12 Turbo (China)] Sanket012345:
I'm facing longer loading time of the in apps pages or slide whatever you say them, for example if I open YouTube and then search something it takes like forever to load, same happens in chrome, twitch, YouTube,

Both on WIFI & MOBILE NETWORK. what to do now
[Xiaomi Redmi Note 4 Guides, News, & Discussion] Concept48:
Hello Redmi Note 4 owners.

Today I like to announce Derpfest 13 by Nemix .

I installed it on my Mido and it works great,

Face unlock Finger print etc all works.

Comes with Google playstore build in.

Wanna give it a test drive?

{Mod edit: Link to Telegram removed. Oswald Boelcke, Senior Moderator}

Leave your test results and for the video check

channel48 Youtube

Special thanks to

Cafebabe and all that made this possible.

Wanna Donate Nemix ?

Pay Daki Aleksa using PayPal.Me

Go to paypal.me/Nem1xDev and type in the amount. Since it’s PayPal, it's easy and secure. Don’t have a PayPal account? No worries.

www.paypal.me

Thank You .
[Xiaomi Redmi Note 4 Guides, News, & Discussion] shadowstep:
@Concept48 The thread has been moved out of the development forum since that section is only reserved for sharing one's own development work. It's clear that you're neither the developer or the maintainer of the ROM you shared, and that's why your thread didn't qualify to be in the device's development forum. Additionally, I've also added the word [SHARED] in the thread title to clarify that the ROM is not your own.

Regards,

shadowstep

Senior Moderator
[Xiaomi Redmi Note 4 Guides, News, & Discussion] Concept48:
Thanks so much , it had to be posted in this section ..
[Xiaomi Redmi Note 4 Guides, News, & Discussion] Oswald Boelcke:
Hello and good morning, @Concept48. I've removed the links to Telegram from your OP.

Regarding social media links please observe that as an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we grant only developers the privilege to share references to their social media in their own development threads and if thorough support is provided in the thread. These conditions obviously don't apply to you, your threads or posts. Additional information is also available here:

Telegram Chat Channels - Way Forward

WhatsApp/Telegram Groups and Channels - Going Forward Hello XDA family! Just notifying all members that posting certain links to Telegram and other sites like WhatsApp is now allowed on XDA. What does that mean? We will allow links to messages...

xdaforums.com

In order to avoid consequences to your account, please refrain from sharing links to social media on XDA unless done in your own development threads.

Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator
[Xiaomi Redmi Note 4 Guides, News, & Discussion] Concept48:
Hi Thanks for your warning , it was just a announcement not even a thread cause developer did not want to make a thread because of the difficult communication on this Network. I,m not even on Telegram and I don't give a dang about Telegram.

Developer knows I made the thread ,just because I want this development to be on XDA and not only on telegram ,. so if Developer can announce Telegram support room I can to /.

i have better things to do then make threads to get attention on your Network.

I did not have to announce this at all , then XDA would not have this development on the site..

My Channel sends thousands of people over the years to XDA so I can be seen as a XDA promotor rather a spammer that needs people from XDA to go to bloody telegram.

I will not anounce anything anymore if you start threaten me with account removal etc ..think again . I,m not here to gain members of XDA I Bring them ..and BTW I will make a video and explain in simple words what kinda sucks about XDA . We keep in touch. Best regards Puck Darlington Channel48 Yourtube.
[Xiaomi Redmi Note 4 Guides, News, & Discussion] Concept48:
@Nem1x
[Samsung Galaxy A12] arsfr:
As the title says, What ROM/GSI are you using, and if you are using magisk what magisk modules are you using?

For me,

I use rooted stock (One UI 5.1 U8), and I don't use too many modules because of the fear of bootloops, but here are my modules:

Spoiler content hidden.
[Samsung Galaxy A12] Allehandro:
Which device are you using?
[Samsung Galaxy A12] arsfr:
A127F/DSN.
[Samsung Galaxy A12] Allehandro:
How are you using One UI 5
[Samsung Galaxy A12] Allehandro:
Wait wait, the a127 got one ui 5 but the a125 didn't?