yashsingh1/xdaforums huggingface dataset:
[Sony Xperia 1 Questions & Answers] KONR4D:
Solved. Flashed the stock rom and then use xperia self repair
[Moto X4 Questions & Answers] manishmg7:
View attachment 5927303I need that Firmware for Moto x4 , xt1900-2 as mine baseband was APAC and now I need to recover that Baseband, I searched whole internet but I was unable to get that rom, anyone who have can post their links here , Because now a days I am facing baseband and IMEI as Unknown or invalid like problems, and that is the only fix left
[Moto X4 Questions & Answers] nstark13:
You can find all firmwares specific to your variant in the following telegram group, also you can ask around in the group as well.

***Link removed by Moderator***
[Moto X4 Questions & Answers] V0latyle:
@nstark13 I have removed the Telgram link from your post. For more information please see the Telegram Policy link in my signature.

Thank you
[Moto X4 Questions & Answers] nstark13:
Acknowledged.

@manishmg7 you can find proper firmware links in some old xda thread or you can visit dedicated telegram channel for development of Payton. I'd have loved to share the proper file with you but you might need to register on telegram for that, so it is up to you.

Thanks.
[Moto X4 Questions & Answers] V0latyle:
You're more than welcome to upload the file to an acceptable host, with the permission of the developer of course. TG links for files are OK as long as the user doesn't need to use a Telegram account or client to download them, aka accessible to the general public.

As for TG group/channel links, we only allow ONE per development post, and we do not allow anyone using XDA to promote their TG group/channel
[Moto X4 Questions & Answers] nstark13:
I understand your point but it is not MY telegram group per se, I've been connected with this group for a long time and the group which has hundreds of members has helped me quite a few times and I'd like to extend the same to somebody in turmoil though I won't ask anyone to bend the xda rules for that.

Cheers.

@ExactExampl Hey man, do we have the required firmware uploaded on any other sources except telegram?

EDIT: LINK FOUND, SHARED BELOW.

Found this firmware link from a hosting website.

Motorola Moto X4 XT1900-2 Stock ROM Firmware (Flash File)

Download the official Motorola Moto X4 XT1900-2 Stock Firmware (Flash File) for your Motorola Smartphone. We also provide all other Motorola Stock Firmware.

motostockrom.com

Please note that I found this link from an old xda thread, I haven't verified the contents of this link and I am not associated with it anyhow, proceed with your own knowledge and understanding only.

Thanks
[Moto X4 Questions & Answers] manishmg7:
The rom link that you have posted is later based on Android 9 but I need a old version like 8.0 and also that should support APAC radio ,but Even though thanks for your link but the link that you have posted is my current rom but I want to downgrade that to 8.0 as this have some problems with baseband and and with WiFi too

Based on Retin
[Google Pixel 6 Pro] Flyview:
Hey guys,

Need some help troubleshooting what's going on with my Pixel 6 Pro.

Short version:

It's freezing up ~30-60s after booting and unlocking the phone, and then soft-rebooting some time after. If i don't unlock the phone it doesn't reboot. Safe mode also works but with lots of scary errors in logcat.

ROM: Stock, May 2023

Magisk: Yes

Kernel: Kirisakura Ravianth 1.0.5_6

Long version:

I rebooted manually to check something and then shortly after the screen froze up. It rebooted on its own and then it froze again. I then rebooted into safe mode and although it doesn't freeze up in safe mode, there are a lot of errors in the logcat (maybe these are normal for safe mode). Rebooting normally again, it freezes up every time 30-60s after unlocking, but is fine if I don't unlock. I then flashed the stock May 2023 image, without -w, so data was not wiped. I assume this means that Magisk and Kirisakura kernel is gone. The problem is still happening! Yikes!

What should I try? Can I clear data of the system without actually clearing all data on the phone (factory reset)?

We'll get to speculations on what could have caused this after I recover it...

I'm attaching two error level logcats:

1) During regular boot:

--------- beginning of kernel--------- beginning of system2023-06-06 22:35:2 - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com

2) During safe mode boot: Freeze_safe_mode_boot.txt

--------- beginning of main--------- beginning of kernel--------- beginning - Pastebin.com

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

pastebin.com
[Google Pixel 6 Pro] simplepinoi177:
I've never used Pixel 6 (so I'm not completely sure this is available, but I'm fairly certain it is), but you should be able to try loading it in (or have you tried/considered trying?) safe mode...
[Google Pixel 6 Pro] Flyview:
Try loading what in safe mode? Please read the whole post. It's able to boot into safe mode and stays unfrozen but there are still a lot of errors in logcat. I have posted the logs.
[Google Pixel 6 Pro] simplepinoi177:
My apologies...I didn't see/overlooked that you had loaded up in safe mode...

One of the main points of utilizing safe mode is to show/prove that it is Magisk and/or one of its modules that are causing issues. I suggest you either load them up one by one until you replicate the issue and/or remove all traces of Magisk and completely unroot and try flashing Magisk and modules again.

FYI, you state "I'm attaching two error level logcats: 1) During regular boot: Freeze_normal_boot.txt 2) During safe mode boot: Freeze_safe_mode_boot.txt" which I assume are text files, but no such files are attached in the post....thought you should know....
[Google Pixel 6 Pro] Flyview:
Thanks! The files must have been too big. I edited the post with external links to the logs.

I assumed that flashing the stock May update would un-root and get rid of Magisk. Is that not the case?
[Google Pixel 6 Pro] simplepinoi177:
Not necessarily. It is true that your device is unrooted, but that's only because the init_boot partition is flashed to stock ("May update") -- you merely just can't have "root" access. Magisk still remains in the root directory -- it's how modules and settings remain, even after flashing full factory images (removing -w from flash-all method of course, having -w remain would obviously remove it and wipe all other data to factory reset).
[Google Pixel 6 Pro] Kris Chen:
Your whole system has been broken. I would recommend you reflash all new system.
[Google Pixel 6 Pro] Flyview:
How can you tell?

Alright so what should I do? Is this recoverable without wiping all data? When I said I flashed the May update, I meant the entire image as I got it from Pixel Factory images:

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com
[Google Pixel 6 Pro] simplepinoi177:
If you wish to do what Kris Chen suggests (he may have gotten to his conclusion by reading your logs), you could simply flash the Full Factory image that you linked -- you could do it manually or there are multiple tools that can do it for you; you were able to root, so I imagine you already have a method. Try to back up as much as you can.

If you wish to completely unroot, there are guides and methods I imagine.

If I found myself in your situation, this is what I would do...

update every module

a bug may be what's causing glitching and corrected in newer version

disable every module

update/establish Magisk stable version -- this may mean downgrading if on canary or delta

unhide Magisk if hidden

reboot

enable one module and reboot and see if the system loads up correctly

see if can't narrow down if it is a specific module

if that does result in a stable loading system,

it was a buggy module

if that doesn't result in a stable loading of system,

take a photo of installed modules

I would remove/delete the Magisk subdirectory from the root directory

flash the stock init_boot

*I'm sure there are more official, better ways to "remove root"

if that does result in a stable loading of system

install Magisk stable version

patch stock init_boot; flash it

install single module -- rebooting right after each one & confirm system stability before installing next one

maybe Magisk just needed to be intensively re-initialized

if that does not result in a stable loading system

remove Magisk

flash stock init_boot

flash stock kernel

if that does result in stable loading of system

it's your kernel, not Magisk

if that does not result in stable loading of system

lost cause

back everything up

flash Full Factory image with wipe included

Those are just things I, personally, would do -- take it as much as a suggestion as you will (as you probably did many of them already anyways). Good luck to you!
[Google Pixel 6 Pro] Flyview:
Thanks for the suggestions! I have already flashed the full factory image, but without the "-w" so data was not wiped. The Magisk app itself has remained, yes, but the modules in Magisk don't show up, since there is no longer root. Correct me if I'm wrong, but I don't think the Magisk modules can be causing a problem once the stock boot.img has been flashed as part of flashing the full factory image.

I am seeing some scary things in the logs:

"WM-ForceStopRunnable E The file system on the device is in a bad state. WorkManager cannot access the app's internal data store."

and there are a lot of com.google.android.gms errors as if it doesn't even exist:

"JobScheduler.Component E Job exists for non-existent package: com.google.android.gms"
[Google Pixel 6 Pro] simplepinoi177:
I'm unsure, I don't know too much about "safe mode", but I just assume that if it all works in safe mode, it usually means it's a module -- in my experience, rooted users only enter that mode when there's an issue with Magisk and/or its modules.

And in the quintessential rooting guide in the P7P forum (and all his other guides), roirraW "edor" ehT suggests to disable modules before flashing the update (even if you are losing root) -- which I infer that modules can still mess with the system even if you don't have root access....

I'm unsure what else safe-mode disables -- if you research and figure that out, maybe you can narrow down what safe-mode is disabling that is causing your issue. Maybe uninstall the last 5-10 apps/modules you installed (if it's not Magisk related)? I doubt running in safe-mode reverts the kernel as well (so I can't imagine that's proving it), but maybe its the custom kernel (like something the custom kernel is interacting with it doesn't like and causing a glitch)?
[Google Pixel 6 Pro] Rachid.Ala:
I think the best thing would be to backup all your data and do a clean flash.
[Google Pixel 6 Pro] Flyview:
Yea I'm in the process of doing a backup of the sdcard right now, while I still can, if this turns out to be a hardware issue. I would still very much like to get to the bottom of what happened here so it doesn't happen again! There's two changes I made recently:

1) Disabled Digital Wellbeing with SwiftBackup last night.

2) Installed a magisk module that increased temperature throttling thresholds a few days ago. The phone was not hot at all when this happened, and I had been running it for a few days without issues.

https://xdaforums.com/t/test-mod-thermal-throttling-modifier-pixel-6-pro.4573745

I doubt either of these is the cause but all thoughts are welcome. Has anyone taken a look at the logs? What other logs should I grab?
[Google Pixel 6 Pro] Kris Chen:
Have you spent time on studying the log what's going on ?

I think most of us is similar as you that we may not understand what's going on but we have ability of doing debug.

- Reflash all system to check whether it's ok.

- Then disable digital wellbeing to check whether it's ok.

- If NG,how about enable it ?

- Next flash magisk module to check whether it's ok.

- If NG,how about removing it ?

I think it's not so hard to find out which one to result in so much error, right ?
[Google Pixel 6 Pro] Flyview:
Yes, I've been looking at the logs but I don't know what the problems point to. There are literally thousands of errors.

I have reflashed the entire factory image (so far only without wiping) and am still seeing the freezing and reboots. So clearly something is majorly messed up. Is there any way to only wipe the "system" partition? Or is that a thing of the past?
[Google Pixel 6 Pro] simplepinoi177:
I think what @Kris Chen is alluding to is that, while you have flashed the Full Factory image without wiping, you haven't done anything to narrow the issue down (by disabling everything [modules or any other possible conflicting aspect]) and enabling them one by one (sort of how you would find what switch is connected to what socket so you turn all switches off, plug something into each socket, and turn them on one by one) -- you seem to feel very strongly about not flashing to stock and losing all data, but unwilling to do the necessary troubleshooting outside of that method.

But it is unfortunate -- I feel as you do -- that gone are the days of TWRP (at least for the Pixel 7's and/or Android 13 [even Android 12 support is limited]) where you could wipe and re-apply (from a backup) the data & system partition only....
[Google Pixel 6 Pro] Kris Chen:
Well, it seems that you live in the past... Until now, no twrp support for A13.

So you cannot manage to wipe specific partition.

Yes!

Until now, no TWRP support for A13.
[Google Pixel 6 Pro] simplepinoi177:
I don't know if this will help -- especially with consideration of not wiping the device (don't know with this tool as I've never used it before); I have a small bit of experience using the Android Flash Tool, I imagine this is similar to that -- but I have just recently been made aware of this tool (url below)...maybe it might help where things did not manually with you; might have a better chance as it is an official Google tool....

Google Pixel - Update and Software Repair

With this or anything else, good luck!
[Google Pixel 6 Pro] Flyview:
Interesting! I might give that a shot but I have an

UPDATE:

I was up until 4AMtrying different things and somehow got it working again!?

Earlier, before reflashing the factory image, I had opened up Magisk and seen that my 2 modules, the "AK3 Helper Module", which is part of the Kirisakura Kernel, and the throttling mod were disabled. At this same time, I tapped on the delete icon for the throttling mod, which put a line through it. I didn't think about this at the time but perhaps it would have to get removed on the next boot? After this I flashed the factory image, which removed Magisk root, but possibly left that module installed?

After this, I could no longer see the modules as Magisk root was technically gone and only the app remained.

Around 3AM I reflashed the magisk rooted boot.img that I still had thinking that maybe I would see the modules again and check that it had been uninstalled. It still froze up after booting and unlocking, but I was able to check the modules and both AK3 Helper Module and the thermal throttling mod was gone. I figured re-flashing Magisk did nothing since it still froze, so I went back into safe mode. After some more time trying different things in safe mode, I rebooted normally again all of a sudden it was fine!?

So now I'm confused. Could it have been the thermal throttling mod, which needed Magisk to be there to get completely uninstalled? And that only happened once I flashed Magisk back and also rebooted again? I'd really like to get to the bottom of this! I suppose it could have been the thermal throttling mod causing the phone to somehow overheat, before CleanSlate was able to apply the battery saver which reduces the CPU frequencies. Perhaps I had never rebooted since applying the thermal throttling mod a few days ago, it's hard to remember now. I had been meaning to do this before, but now I'm going to take a look at exactly what values are changed with this mod I installed, comparing it to the stock file, and see what if anything could have been dangerous, and rewrite it.
[Google Pixel 6 Pro] simplepinoi177:
Curious/Interesting.... I always assumed clicking on the trash icon and rebooting simply but effectively uninstalled the module. But it's also why I stated that you should remove each module and reboot after each time....*very important the rebooting

I imagine somewhere between this

may be what corrected what was causing it to glitch...? That or, again, getting the module properly/completely removed or re-initialized properly corrected it -- we told you that it was most likely the modules; when things run smoothly in safe-mode, it's usually the culprit...

Tweaking with frequencies & thermal often end up with random glitches -- from my very limited experience of overclocking my CPU and GPU, the way to go about it is to tweak those things until just riiight about the system doing random reboots....It's easy to imagine this all being a symptom of such things...it's why I suggested even going back to stock kernel after removing all Magisk & modules....

Glad you stabilized your device though!
[Google Pixel 6 Pro] Flyview:
I think the problem may have been that although I tapped on remove (and it got crossed out), when I rebooted, I immediately flashed the stock image. I didn't let it reboot with Magisk intact to fully remove the module's changes. Could that be the problem? Then when I finally flashed Magisk again, it was able to remove the module after a (second) reboot. WEIRD. If anyone knows about how this works. Please chime in!

On another note, I've taken a careful look at that module and the one I flashed was modified further by a random user, not the OP. My mistake, I didn't check what was inside. It had pretty much completely removed any throttling up to 95c lol. I don't know how it ran fine for a few days and became a problem once I rebooted last night. I have now carefully modified the thermal mod myself, and am testing it now. I will be posting it in that thread.
[Touch Diamond, MDA Compact IV Themes and Apps] drsquid:
I have downloaded some of the focus color change files from XDA and found that they were very incomplete, missing many of the other 'green' elements in vanilla black manila, so I made a new one, which includes the focus elements for the landscape icons too. It also has a reg edit to change the enlarged start menu and task manager highlights to gray.

I could make other colors on request.

EDIT the communications menu is NOT orange if you use this with stock HTC black theme (but for some reason on the Alltel theme I tested it with it was), I did not check this, I guess the manila file names on Fuze manila comm menu are different. I did catch little things like the audio progress bar etc, but I will update soon to fix the Comm menu, with new colors too...

EDIT 2 HELP REQUESTED. I check the manila files I changed and all the correct ones for the comm manager are there, yet it is still stuck on green, at least with the Wildberry Manila landscape cab that I used..any of the more experienced people care to help me figure out why this is

EDIT 3 I figured it out I think - I am running a custom comm manager from my Juicy CDMA rom - so I have included those files in a revised version that is now 100% all green graphics to orange

EDIT 4 I have also added an optional orange tab cab file for the lower scrolling icon area - personal preference if you like this.

EDIT 5 I have fixed the transparency issues on the opera focus so it looks better, not shown in pictures below

EDIT 6 ORANGE CAB IS BUGGED - OPERA HIGHLIGHT IS PINK - Fix coming - and text is missing below opera globe on all colors

EDIT 7 - Text below opera globe is restored and install names bugs of cabs, shade of orange for opera focus are fixed. New files to be posted later tonight (dec 23 08). Red and Charcoal to follow soon.

ADDITIONAL COLORS CAN BE FOUND IN MY ADDITIONAL POSTS IN THIS THREAD
[Touch Diamond, MDA Compact IV Themes and Apps] dynamicwave:
Good job man:)
[Touch Diamond, MDA Compact IV Themes and Apps] bhekman:
Do you have any screens?

Is it for all the green focus elements like call screen, comm manager, settings tab, usb popup screen ?

If so, then it will be nice
[Touch Diamond, MDA Compact IV Themes and Apps] drsquid:
i am new to this - so how I capture screens I have to figure out, but yes it does everything that is green in orange - though it is possible I missed something

also any help with the reg settings to get the highlights in the start menu and dialer to go orange through reg settings would be nice - when ever I tried the hex code for orange in the registry the start menu highlight ended up going dark blue
[Touch Diamond, MDA Compact IV Themes and Apps] bhekman:
Hmm nice color, it will look nice on black!

I cannot help you with reg settings though.

I will follow this post to see the progress you're making to get it all orange.

Good luck!
[Touch Diamond, MDA Compact IV Themes and Apps] drsquid:
EDIT 2 HELP REQUESTED. I check the manila files I changed and all the correct ones for the comm manager are there, yet it is still stuck on green, at least with the Wildberry Manila landscape cab that I used..any of the more experienced people care to help me figure out why this is
[Touch Diamond, MDA Compact IV Themes and Apps] drsquid:
EDIT 3 I figured it out I think - I am running a custom comm manager from my Juicy CDMA rom - so I have included those files in a revised version that is now 100% all green graphics to orange

EDIT 4 I have also added an option orange tab for the lower scrolling icon area - personal preference if you like this.

Now that I have finalized the Orange version other colors will be forthcoming

Updated files in first post
[Touch Diamond, MDA Compact IV Themes and Apps] Klong4:
I took the liberty of doing the all blue one. Let me know if there are any problems.
[Touch Diamond, MDA Compact IV Themes and Apps] drsquid:
Thanks !

but the comm manager, audio manager, dialer etc do not use the manila files for the focus colors - they are separate PNGs in the windows folder, or registry edits
[Touch Diamond, MDA Compact IV Themes and Apps] wmiranda9:
Mew request in Red!!

Can you make it in RED???
[Touch Diamond, MDA Compact IV Themes and Apps] abumhmmd1:
THANKs

I do not have Diamond .

Could you make 4 GREEN color ??
[Touch Diamond, MDA Compact IV Themes and Apps] drsquid:
Light Pink

Here is my next color - a very light pink...really on suitable for TF3D themes with a dark font (ie doesn't work too well on my stock HTC black theme)

Again there is separate cab for a pink lower curtain icon tab (NOT SHOWN IN IMAGES BELOW), if you would like that too.

BTW the comm and audio manager focus files are not 'manila' files - they are simply png's in your windows folder on the device, so just changing the manila files doesn't change everything. Here are the file names that you need to edit

SIPMenu_BottomMenuItem_HL.png

SIPMenu_BottomMenuItem_HL_LS.png

SIPMenu_MenuItem_HL.png

SIPMenu_MenuItem_HL_LS.png

SIPMenu_TopMenuItem_HL.png

SIPMenu_TopMenuItem_HL_LS.png

Status_On.png

Status_On_Disable.png

L_Button_Down.png

L_Button_Focus.png

option-check-box-on.png

P_Button_Down.png

P_Button_Focus.png

P_Symbol_lock-lightOFF.png

P_Symbol_lock-lightON.png

Progressbar_L.png

Progressbar_P.png

Save_to_contact_checkbox_Check.png

ses_btn_eq_chked.png

ses_slr_bar_2f.png

ses_slr_bar_2lf.png

ses_slr_thumb_2f.png

Also these files will not change the focus in HTC apps like the camera etc - that is something I will work on eventually.

Note there is no image for opera focus, but bug with no text below globe in v1 light pink cab is fixed, and focus is pink as per the rest of the highlights
[Touch Diamond, MDA Compact IV Themes and Apps] drsquid:
Light Blue

As above, Light Blue focus, with separate cab for lower curtain icon tab.

as above bug of no text below opera focus is fixed in v2 file, and name in add remove programs is now correctly saying light blue
[Touch Diamond, MDA Compact IV Themes and Apps] _wizo_:
Can you please make a black one?