yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] joshw0000:
I was rooted with Magisk on the April build and attempted to update to May. So I used Magisk to uninstall, accepted the OTA, then used Magisk to reinstall (before rebooting) but I got an error about the phone being corrupt,. So I've spent the past several hours flashing the stock boot image to both boot slots, creating new Magisk patched images, flashing those to both boot slots, rebooting, and flashing stock boot images again to both boot slots. I've done every combination of flashing stock to one boot slot and patched to another, patched to both slots, and now stock to both slots. Any time I try to boot a patched boot image the phone reboots a few times and finally tells me it's corrupt and asks to reset it (which I haven't done and prefer not to do).

I can confirm that I'm on the May update and that I'm using the May boot image in my attempts to root again. At this point, I've wiped the Magisk app (thinking a module could be causing the issue when I root) and I'm back on the stock boot image and the phone seems to be working fine, just without root.

I feel like I'm missing something simple. Can someone point me in the right direction?
[Google Pixel 6 Pro] Vincent_40:
I stopped to update ROM with this method since march because i had always a bootloop.

Now i install the update by android flash tool and flash boot patched with fastboot command.

You could do it. I hope Twrp wil be released quickly.
[Google Pixel 6 Pro] joshw0000:
I successfully updated to May and I've flashed the patched boot image in fastboot at least a dozen times (stock to patched, different partitions, patched to stock). The phone won't boot whenever I flash the patched image. It just bootloops and eventually gives me an error about being corrupt and asks if I want to factory reset.
[Google Pixel 6 Pro] shiftr182:
Flash your patched image, then boot to safe mode, then reboot. It should work. I had the same issue and it ended up being something I had in Magisk, even though I had everything disabled. I ended up uninstalling everything in Magisk, and reinstalling.
[Google Pixel 6 Pro] NippleSauce:
And if this doesn't work you might have to wipe your phone and re-flash the appropriate build. I remember seeing posts in the past with users discussing a wipe and re-flash resolving the "phone is corrupt" issue.
[Google Pixel 6 Pro] joshw0000:
I wiped data in Magisk since I can't access the modules to disable them right now (no root) and I also wiped data in Rice Tweaks since it was one of the mods I was using. I'll try this tonight and see if it works.
[Google Pixel 6 Pro] biTToe:
Before you wipe everything try this:

** ALSO: booting into safe mode automatically disables all Magisk modules **

How I root and update (which is identical whether rooting the first time or updating):

From here:

https://xdaforums.com/t/may-2022-fi...central-repository-of-relevant-links.4352027/
[Google Pixel 6 Pro] joshw0000:
Thanks. Do you know if I can run the flash-all.bat if I'm already on the current update? I have the full firmware on my PC (so I could get the boot image).

It sounds like booting to safe mode is the one thing I haven't tried.

When I updated last night I tried to disable Magisk from within the app but Magisk didn't have a backup (because I had rooted on the April build from fastboot) so I flashed the factory April boot.img, then fastboot boot magisk-boot.img, then allowed Magisk to root my phone. Then disabled all the modules, unrooted with Magisk, accepted the OTA which took unusually long to install (2+ hours), then used Magisk to restore root but I think I forgot to tell it to do the inactive partition which may have cause all of my issues. When I rebooted it gave me the corrupt error.

From there I spent a bunch of time fastboot flashing and fastboot booting the stock and modified May boot images. I've got about 4 copies of the modified boot image where I kept recreating it hoping it'd work again.

Tonight I'll try to flash the modified boot.img and boot directly into safe mode to see if I can get it to load. I may also try wiping cache in recovery to see if that helps.
[Google Pixel 6 Pro] biTToe:
YES you can.

Just make sure to edit the flash-all.bat and remove -w

otherwise you WILL wipe.

THEN... after you save the edited flash-all.bat, edit it again to make sure the -w is in fact not there.

Ive been where you are before. I forgot to disable a mod and boot-looped.

I booted to safe mode then re-flashed with flash-all, patched the boot.img and flashed that via Magisk and I was golden.

I always use this method. I even went from 12-beta to 12.1 w/o so much as a hiccup.

OTA can be problematic (or has been for me in the past). this is simple, quick, and works every time.

My suggestion is to start from scratch: delete all those previously used/attempted files -especially the patched image.

d/l the new factory image, extract/patch that boot.img This way you know everything is from the same place.

cheers
[Google Pixel 6 Pro] joshw0000:
Thanks guys for all the help. Safe Mode is going to work for me. I was able to root, boot to safe mode, and reboot normal. I'm slowly enabling modules until it errors again and I've found that Renovate Ice was the culprit. But whenever it errors, I can just boot to safe mode, reboot, and start fresh with modules. Thanks!
[XPERIA X1 General] soleimam:
Dear WinMo lovers, i need some advise

I am a UK vodafone customer and my contract is due for renewal. I am stuck picking BB storm or Xperia or getting Touch HD through a website which i have to wait for, i love xperia but it has some drawbacks for as follows

Is the screen too narrow? How is the text inputing using only the touch screen?

I will be gratefull for any advise and information.
[XPERIA X1 General] pontusf:
It is pretty small using just the touchscreen. Not easy if you have bad eyes or shaky hands or if you are sitting in a train. I only use the keyboard now.
[XPERIA X1 General] mrb_uk:
You can download some alternative software keyboards which are more touch screen user friendly than the standard built in one though.
[XPERIA X1 General] wingnutLP:
The t9 input is fine for use one handed and teh other keyboards are usable. The built in microsoft one neccssitates the use of the stylus. For one handed use the only real option is the on screen T9 and for two handed you can use the hardware keyboard.
[XPERIA X1 General] soleimam:
Thanks a lot everyone then it's a no go for me. the storm either. i guess i am stuck with my old curve 8310 then.
[XPERIA X1 General] Bxsteez:
Hmm but u can download better on screen keyboards pretty easily and have it automatically switch to it everytime the phone starts up
[XPERIA X1 General] TechDiane:
But why would you want to use an on-screen keyboard when the sliding QWERTY one can get the job done way faster, whenever you want to write something?

I'm seriously thinking about buying an X1 and the on-screen keyboard's usability is the last thing to consider.
[XPERIA X1 General] sevans21:
The Blackstone keyboards from the other thread here are a huge improvement over standard.
[XPERIA X1 General] NZtechfreak:
Just install the Touch HD keyboards - they're already available for the Xperia (I have them on my Xperia). Beautiful to use, much better than the awful standard one it comes with.

So basically if you're thinking about keyboards then the Xperia wins hands-down. It has a hardware QWERTY, but can run the Touch HD ones if you want it to.
[Samsung Galaxy J3 (2017) Questions & Answers] Mrozario214:
My phone is jacked up. I'm trying to install a ROM off of a micro SD card with a phone only. I have no access to a PC. I don't care if it's a custom ROM or factory rom. The main thing is I have no access to a PC. Only my j337v and a micro SD. Can anyone point my n00b ass in the right direction and walk me through it please. I'm willing to pay for help. Thank you
[G1 Android Development] Stericson:
1.) DO NOT try and make a symlink for /data/app onto your sdcard.

Why?

1. Your phone will go crazy!

2. It just doesn't work, even if you do make the symlink. Phone won't boot up.

3. Even if you get your apps back on your phone, many of them are corrupted and you must re download them...

Reasons

1. must be a communication area somewhere...another folder would need to be symlinked....maybe the data folder....

I will probably keep updating this as I go on....
[G1 Android Development] beartard:
Could it be that the sdcard is mounted later in the boot process than when the command is called to access the apps/data? In other words your symlink is telling the OS to load data from a partition that isn't mounted at that point.
[G1 Android Development] Stericson:
It is possible...don't know how to work it out....I did it again trying something else and it screwed up my phone to the point that I had to do a factory reset...home key wouldn't work, apps failed, background changed....lol bad scene...lol

Fun though....lol
[G1 Android Development] VR4Stryph:
uh

Also you think that maybe some apps were open at the time you moved the directories ?
[G1 Android Development] Stericson:
I thought of that but I also did it while the phone wasn't turned on.
[G1 Android Development] haitiankid4lyf:
something else you shouldn't do

did this by accident :)

you should not clear settings under: manage apps>settings it clears call logs messes up your background and some other things :eek:
[Redmi Note 10 Pro] Dantespalette:
I've been trying to go back to the stock rom for a few days now, I'm currently using the Pixel experience rom (A11). I've installed the latest mi flash tool and also downloaded the fastboot rom MIUI 12 for the Indian version. I've attached the log files from Mi flash. Is there a way to solve this issue ?

also anti value is 3, I got this from the command fastboot getvar anti
[Redmi Note 10 Pro] x3r0.13urn:
Download newer or latest fastboot for your region. The one you used is outdated.
[Redmi Note 10 Pro] Dantespalette:
I tired the same with MIUI13 too.. I got the same error
[Redmi Note 10 Pro] x3r0.13urn:
Seems that findstr program in your windows is missing, that's weird. Either you can remove the line that check anti rollback in clean_all.bat but it's not recommended, or you can check why findstr is missing in your windows.
[Redmi Note 10 Pro] ChiefSid:
I have a solution to this that might be helpful for you,if your issue isnt resolved then contact me on telegram @SiddhantPatil56
[Redmi Note 10 Pro] Harmeetsaggu:
Use windows 10
[G4] end123:
Hi,

Though it would be a good place for people to post WM6 and WM6.1 roms with Touchflo 2/3D or WizFlo installed.

Please Specify if its G3 or G4 rom.

This way people could have a good repository to choose from.

If this already exists please excuse my post, and replay with a link..

Thanks!! This community is awesome and I hope to help!
[G4] Myrddin Wyllt:
http://xdaforums.com/showthread.php?t=427328

Too late, mate.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] DJRepresent:
Is there a guide thay can walk me through a factory reset after rooting and wiping with a custom ROM? I'm looking to sell my phone.

Thanks.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] NOSS8:
1/Unroot

2/use this tool:

https://xdaforums.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] DJRepresent:
Thanks, but how do you unroot?
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] NOSS8:
With Magisk apk.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] DJRepresent:
It's doesn't appear to have that option. Is there a guide I can use?
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] DJRepresent:
I downloaded this:

Redmi Note 9S / Note 9 Pro / Note 10 Lite (curtana) India (IN) Fastboot & Recovery ROM | XiaomiROM.com

Xiaomi Redmi Note 9S / Note 9 Pro / Note 10 Lite (curtana) India (IN) official ROM, include stable, weekly and beta MIUI firmware which can be updated …

bit.ly

Now it's saying I have a Redmi 10 Lite? LOL what's up with that. Phone's UI is lagging in performance too.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] NOSS8:
The link you quoted only refers to recovery zips and cannot be used with Miflash.

You have probably used a rom that does not match the model of your phone.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] DJRepresent:
OK, where can I get the factory model? I tried flashing the Global version and it got a bit better but not sure if that's the correct image.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] NOSS8:
All explanations and links on post #2.

If you have a india model flash a india fastboot rom.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] DJRepresent:
I got it, thanks. TBH I'm not even sure I have the Indian model, I think I just remember seeing that from a while back. How would i find out exactly, is there an online resource I can look it up on?
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] NOSS8:
Where did you buy it?

5 versions

Global

Europe

india

Russia

Turkish

It should match your country.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] DJRepresent:
Oh I purchased it from Bonanza.com or some online retailer. They didn't make mention of where it was from. I live in the United States.
[Redmi Note 9S / Note 9 Pro (Indian Model) Question] NOSS8:
Flash a global version but dont relock the bootloader then try the phone,if all is ok,flash again and lock the bootloader.
[Samsung Galaxy S22 Ultra] bligui:
I have a Galaxy S22 Ultra S908E I was trying to do a downgrade of the firmware from S_22_ULTRA_SM-S908E_TPA_S908EXXU1AVCJ to S_22_ULTRA_SM-S908E_TPA_S908EXXU1AVC9 the firmware flashed was successful but on reboot it gives an error to a White android man logo and reboots and it won't go past there, I have some important information on it that would like not to loose any ideas?
[Samsung Galaxy S22 Ultra] dr.ketan:
Reboot to recovery and format data
[Samsung Galaxy S22 Ultra] bligui:
Figured so much will need to see how to recover some things.
[Samsung Galaxy S22 Ultra] dr.ketan:
If you want to preserve data then flash VCJ firmware and it will boot again, backup your data and then downgrade and format
[Samsung Galaxy S22 Ultra] donkeyman1234:
I was wondering if you have to format data or not while reflash back to VCJ, please tell us the result.
[Samsung Galaxy S22 Ultra] bligui:
I did it kept rebooting and had to format the device though I think t might have been my fault since I did not remove the FRP before doing the downgrade. I kept getting a white robot saying erasing then it just rebooted. After two or three reboots it got to a page that said "Try again, Factory data reset or view logs" and the bottom left corner had an error saying something similar to this "libfs_mgr failed to mount sd card"
[Samsung Galaxy S22 Ultra] donkeyman1234:
That(format data) is what I thought. I had the same experience with n20u downgrade. But my n20u has 1T sdcard which I can backup everything. With s22u I am hesitated to update becuase the hassle of data backup.
[Samsung Galaxy S22 Ultra] bligui:
I used to have a 512GB but you know how this is now days. I do have online backups of most everything but damn it's apain to download from them onedrive keeps at 1meg at the most so it will take me a day or two to see the real damage. Seems android 12 is not ok with downgrades even if they are from the same Bit
[Samsung Galaxy S22 Ultra] donkeyman1234:
The feeling is mutual. I dont like to set up the phone from scratch especially I have a lot data. Is there any reason to downgrade from AVCJ to AVC9?
[OnePlus 9] AtreyC:
I'm looking for a captain who could help me find solution. Like "EtherealRemnant" in his post, Im not able to get OOS 12 work on my OP9.

EtherealRemnant post:

https://xdaforums.com/t/fastboot-rom-pc-required-op9-stock-oos-11-2-2-2aa.4275727/post-86854951

Like "everyone" I've something messed up with TWRP boot and ended up with MSM tool. Cause I have LE2113 I have to use India MSM for 9Pro.

Then I use downgrade package to get stock OOS on my OP9, then use oficial way to update OOS, till highest A11. But whenever I use update to LE2113_11.C.47 it ended up with frozen/not working touch screen. Not just in OS but also in TWRP and stock recovery. I´ve tried also connect USB mouse, but with no successs.

My question, is there a way how to update to OOS (A12) without get freezed touchscreen?

EDIT:

Whole problem was in usage of wrong MSM (INDIAN OP9pro, EU OP9pro). So if you want to recover yours OP9 (EU) LE2113, you have to use MSM tool from allenjthomsen (Thank you!).

More abotu this tool here
[OnePlus 9] EtherealRemnant:
I was able to get my device back to stock software by modding the MSM Tool for global but then I gave it to someone else to try to help them and it didn't work. I have sent a PM to the person who mods these images for some help.

Have you tried using the full install zip for BA using the system updater? I didn't actually try that before I messed around with the MSM Tool. Put this in the root of your storage and go to updater and do the local upgrade.

https://otafsg-cost-az.coloros.com/OnePlus9_EEA/OnePlus9Oxygen_22.E.13_GLO_0130_2111112104/patch/amazone2/GLO/OnePlus9Oxygen/OnePlus9Oxygen_22.E.13_GLO_0130_2111112104/OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip

It seems like what is happening is even after you get it back to stock software, there is a flag somewhere that's designating the device as an Indian 9 Pro. Once I got the modified global MSM Tool I made to flash my phone, the problem stopped because my phone was fully global again and I've been back on OOS 12 C.48 since Saturday evening (for better or worse, OOS 12 has a lot of issues but I don't want to risk another brick for awhile, especially since I'm not sure that the mod I made actually worked and it wasn't just some freak coincidence that let me flash back).
[OnePlus 9] AtreyC:
Thank you for your reply, the link you've send is downloading:

OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip

I've presume that is for Global version, or is for EU version also?

EDIT:

Last try was:

MSM - OnePlus_9_Pro_EU_OxygenOS_11.2.2.2

Then update to:

OnePlus 9 Oxygen OS 11.2.10.10.LE25BA (EU)

- OnePlus9Oxygen_22.E.13_OTA_0130_all_2111112104_f4acbf.zip

Then, two options:

Oxygen updater -> C.47 ->Touchscreen death

OTA update -> OxygenOS 12.0 (C.48) (EU)

- OnePlus9Oxygen_22.E.11_OTA_0110_all_2107082125_downgrade_09b1a0a810824761.zip ->Touchscreen death

Im starting to be little bit despered, where is the problem. I've tried lost of combination but still no luck...
[OnePlus 9] imirwp:
The same thing happened to me 2 days before and the conclusion was to use stock Android 11 or any custom ROM.
[OnePlus 9] EtherealRemnant:
The link I sent you is the full stock EU image.
[OnePlus 9] jshinn1:
Did you unlock the bootloader before you upgraded, the frozen non working touchscreen only happened when I upgraded with an unlocked bootloader. If you havent already try to MSM back to stock and then upgrade to OOS12 before you unlock the bootloader
[OnePlus 9] EtherealRemnant:
The broken touchscreen happened to me with a locked bootloader too. I know this because I was on 11.2.10.10 after spending hours figuring out how to get it back on full global firmware and I made the conscious decision not to mess with a custom ROM anymore after updating to 11.2.10.10 before I chose to use the OTA to upgrade to C.48 so I didn't unlock the bootloader. Then I ended up having to do the MSM again when my touchscreen didn't work.
[OnePlus 9] jshinn1:
Hmmm Im definitely no expert but if that doesn't work then hopefully somebody else can chime in with a solution.
[OnePlus 9] EtherealRemnant:
The only thing that worked for me was getting back to the stock global firmware with the MSM Tool. I modded the MSM Tool to do this since I was stuck on the India 9 Pro software and it worked for whatever reason but I had someone else try it and it didn't work for them and asking someone who knows about the MSM Tool, my fix shouldn't have worked for me either, so I took it down so as not to mislead anyone. As you can see though, OOS 12 is running fine.

View attachment 5610655
[OnePlus 9] AtreyC:
@jshinn1 When I install MSM for OP9pro on my OP9, I've unlock bootloader to install downgrade for OP9 via TWRP. Then I try to update via OTAs, downloaded from Oxygen updater, or xda sources. Result is still same, death touch after install Android 12 update.

I've also tried swaping slots (A,B) in TWRP during install, no result.

So far only MSM capable unbrick my OP9 was Indian 9Pro and EU 9Pro. But in the end same result death touch.
[OnePlus 9] XxBigBuckxX:
I was able to fix it by modifying the settings.xml in the T-Mobile msm, I haven't had anyone else try but it's worked multiple times on my own. I can provide the link if anyone is interested. It's for the OP9 T-Mobile but I can easily change it to global if needed.
[OnePlus 9] AtreyC:
Sound promising, can you change it not to Global, but to EU (2113)?
[OnePlus 9] XxBigBuckxX:
Okay I will try it on my device and if all looks good report back with a download link.
[OnePlus 9] EtherealRemnant:
Can I ask how you did this? I modified the settings.xml on the global ROM to IN and it flashed mine that was stuck as an Indian 9 Pro but then failed params when I gave it to someone else and I haven't wanted to risk being stuck on IN firmware again to troubleshoot it. In my case all I did was change the Desc from O2 to IN and that did it but I gave it to someone with a T-Mobile device also flashed with Indian 9 Pro software and it didn't work... Figured it must be a fluke that it worked for me.
[OnePlus 9] AtreyC:
Problem SOLVED, see my edit in first post. Thank you all for participation.
[OnePlus 9] jshinn1:
Glad you figured it out
[OnePlus 9] sakib4e1:
i

i tried to covert my t mobile(le2117) to global then my touchscreen dont work what can i do?
[OnePlus 9] XxBigBuckxX:
Which version of OOS are you on?
[OnePlus 9] sakib4e1:
lemonadet_22_O.01_210307
[OnePlus 9] sakib4e1:
same problem in my le2117 then i flashed Oxygen OS 11.2.22.2.LE54CB then use a otg and mouse then update the softwore version then the display touch issues is solved

OnePlus 9 11.2.22.2 (T-Mobile) MSM Download Tool

Oxygen OS 11.2.22.2.LE54CB (T-Mobile) Download: https://drive.google.com/file/d/1-5RC9f8es6ZrwpYKKQBMmw5gW-rzDSfZ/view?usp=sharing Size: 2.92 GB MD5: b6fc004c81d311109f66cceb3f375862

xdaforums.com
[Touch Pro, Fuze General] amidsin:
I just got my AT&T Fuse and the first thing I did is testing performance. I did it before installing any software except for whatever is installed automatically for stock AT&T ROM.

Testing method (storage card and SIM card were inserted during testing, AC power is plugged in):

1. Hard reset the device.

2. Initialize the device (screen calibration, no password or mail setup).

3. Wait for all of the software from ExtROM to install.

4. Install SPB Benchmark from the storage card.

5. Turn on Airplane Mode.

6. Soft reset the device.

7. Start SPB Benchmark. Un-select tests involving Pocket Internet Explorer and Pocket Word.

8. Wait for test results.

You can see results in linked Google Docs spreadsheet:

http://spreadsheets.google.com/pub?key=p-q7Gtr4_r-sNB8t-hfm_LA

SPB Benchmark Index is 452.2

Overall, I'm impressed. I'm coming from Tilt. I though that my old device was pretty snappy with carefully selected cooked ROMs (WM6.0 - Q-MObile 1.2 and WM6.1 - Dutty 19700 Hybrid 2). Still Fuze outperformed it with stock ROM while obviously taking a hit from VGA screen.

Kudos!!!

BTW, if somebody will be working on compilation of performance test data for different Fuze ROMs for Wiki, please let me know. I would be interested in participating.
[Touch Pro, Fuze General] scdavis:
Awesome stuff amidsin...

but would it be possible for a larger version of the image? :) that one seems a little bit fuzzy...

-SCDavis
[Touch Pro, Fuze General] F2a:
Image is unreadable.
[Touch Pro, Fuze General] bfspider:
Hi,

The image is waaay to small to read :(
[Touch Pro, Fuze General] thehyecircus:
Did you bother plugging it in until the battery was full? Or is that unimportant
[Touch Pro, Fuze General] amidsin:
I apologize for unreadable image. I have replaced it with link to public Google Docs spreadsheet.