Does anyone know any specific instructions on how to do this revert? I attempted to do this and when I get into RSD, it tells me failed to switch into fastboot mode. I have tried everything with no luck. Can someone help? Android 12 in my opinion is sluggish and has bugs. I need to go back!!!
Related
Moto G Stylus Metro PCS brand:
I'm brand new to this subject so please forgive any ignorance. I'm decent with linux but new to android stuff.
Tried flashing the latest weekly build of OmniROM - now seems to be stuck at boot screen and won't go past. I am coming from latest OTA update from Motorola.
Phone was not rooted prior to starting this.
I also accidentally wiped slot A with my factory image on it (oops).
TWRP did not ask for any decryption key so I ran:
fastboot erase userdata
and this seemed to fix errors that I was getting while flashing with respect to denying access.
What I've done:
-Unlocked bootloader
-Installed TWRP 3.5.0-10 from the g-stylus forum.
-wiped and formatted via TWRP
-flashed 5/23 weekly build of OmniROM
Now no matter what I do or what slot I flash to it will not get past the Omni boot load animated screen. I've run this for almost 2 hours and nothing happens.
Any ideas?
Thanks!
nutsnax said:
Moto G Stylus Metro PCS brand:
I'm brand new to this subject so please forgive any ignorance. I'm decent with linux but new to android stuff.
Tried flashing the latest weekly build of OmniROM - now seems to be stuck at boot screen and won't go past. I am coming from latest OTA update from Motorola.
Phone was not rooted prior to starting this.
I also accidentally wiped slot A with my factory image on it (oops).
TWRP did not ask for any decryption key so I ran:
fastboot erase userdata
and this seemed to fix errors that I was getting while flashing with respect to denying access.
What I've done:
-Unlocked bootloader
-Installed TWRP 3.5.0-10 from the g-stylus forum.
-wiped and formatted via TWRP
-flashed 5/23 weekly build of OmniROM
Now no matter what I do or what slot I flash to it will not get past the Omni boot load animated screen. I've run this for almost 2 hours and nothing happens.
Any ideas?
Thanks!
Click to expand...
Click to collapse
Weekly builds may be unstable. I'm actually curious on how you got a hold of such build for the this device. Most, if not all ROMs are unofficial for the stylus and updates for each rom varies by contributed developers.....
However, you say you're decent with Linux. I'm sure there's some developers here that would help you with various tools to learn on how to make your own version of any type of OS.
As for OmniRom, I'd probably ask @vache for some help, for he has his own unofficial version.
Also, I recommend that you have the latest platform tools and the moto software tool if you don't have these yet...
nevermind I got it working. I was flashing p2pstate.bin directly (somehow this works?) when instead I was supposed to extract the image files and flash the respective files.
Seems to boot up now. Thanks!
nutsnax said:
nevermind I got it working. I was flashing p2pstate.bin directly (somehow this works?) when instead I was supposed to extract the image files and flash the respective files.
Seems to boot up now. Thanks!
Click to expand...
Click to collapse
That's good you got it to work. One developer once told me, when all else fails, think outside of the box. You'll eventually get it to work somehow
I have your solution cuz I went through the same thing.. you have to start out with stock Android 10 so you have to be bootloader unlocked and rooted that way you can downgrade your software and it's only the super images that you have to downgrade.. so just flash your supers and you'll be fine but they have to be stock Android 10 it doesn't matter what firmware version because you're keeping the same modem file
I was on Open Beta 2 and saw a new update come in (via settings, not Oxygen Updater) so went through with it. Now the phone gets to the splash screen, then goes dark and nothing works. I can get into the Fastboot menu, but same results. Anyone got any hints?
Usually a wipe will fix the problem if nothing else works. MSM tool for worst case scenario.
You could wipe in recovery, or run fastboot command.
I seen some mentioned a new update for Android 11 so that makes me wonder what is new, since I haven't seen anything yet on my device or oxygen updater. I know there is a rollback apk or something similar for downgrading but I haven't used it myself, I'm on 11 still on the unlocked pro version.
I have a 3xl rooted with Android 11 on it. I've never installed Android 12 because I wasn't sure if I had to de-root the phone prior to upgrading to Android 12. Can I simply go to Settings>System>System Update>Download and Install and be good to go or do I need to return it to factory prior to upgrading to Android 12? Also, I'd like to perform a factory reset on the phone because it's never had it done on this phone and the phones beginning to glitch up. What's the best order to factory reset vs upgrading to Android 12, etc? Thanks for all help in advance.
EDIT: I just saw that I have Majisk on the phone as well. It's out of date too. So any help on what order I need to perform all of the above actions in would be very helpful. I'm guessing step 1: update Majisk, 2. Upgrade to Android 12, 3. Factory Reset?
Per the title I tried to go to A13 to see if it would fix the low ringer volume on my Unlocked Pixel 6 Pro, or whether I have a hardware issue. It did not. I decided to go back to A12 and wait until the stable release and trying to flash via adb tells me I can't downgrade. When I try the Android Flash Tool and select the A12 build I need, it starts and then shows a "HEAD request failed: Unknown network error" and stops.
I'm soft-bricked now. I get a message that the device is corrupt and may not work properly, then the bootloader unlocked warning I've always gotten after I unlocked that. After that I At best I get to a white screen with the Google logo or bootloader mode.
Has anyone worked through this error or does anyone have a solution on how to recover my phone? Thanks!
Reflash A13 and make a backup then flash - wipe A12
Paz9 said:
Reflash A13 and make a backup then flash - wipe A12
Click to expand...
Click to collapse
Thanks - that's exactly what I did. I was traveling and trying to get my phone working again and you are on the right track. I got it fixed fairly quickly, but I left the thread open to give another instance of hope to folks who may stumble across this in the future. I'm guessing I was flashing the OTA image and not the factory image, and it was confusing because it would partially succeed and then fail with no obvious indication of the reason for the failure. I've since flashed the factory image several times and while it too has the .sig files missing errors that appears to be a non-issue, it works just fine and I'm back in business.
It may be related to what we seen today with A13 being released. The Bootloader cant be rolled back to earlier version.
Someone posted today they can get Android 12 installed back, AS LONG as they edit the factory image script to skip the bootloader flash part.
chaco81 said:
It may be related to what we seen today with A13 being released. The Bootloader cant be rolled back to earlier version.
Someone posted today they can get Android 12 installed back, AS LONG as they edit the factory image script to skip the bootloader flash part.
Click to expand...
Click to collapse
It's not, he was on the Android 13 beta and was trying to flash the full OTA when the recovery does not permit flashing a lower firmware than what is already running. He only had to instead flash the firmware from the bootloader to downgrade from the beta.
However yes, if you take the Android 13 release bootloader you cannot downgrade back to Android 12's bootloader. How long the Android 13 bootloader will continue to boot Android 12 or if they will put another antirollback measure in is unknown.
Upgrading from 11.0.9.1(Android 11) to Android 12 using HD1901_11_F.22 update from system upgrades bricks my phone. I live in India and decided to upgrade my phone to Android 12 just to find my phone bricked after rebooting(a white screen flash/blink followed by black screen) and reverted back to oos 11 and did the install again but same result. Is there any way I can install oos 12. P.S I am currently using a oos 11 based custom rom and I had replaced my phone screen with an unoriginal one(because I broke my original screen) if that makes a difference
Model:HD1901
Variant:India
Can somebody help me please
My best guess is that you need to be completely stock OOS11 to properly update to OOS12.
You say that your on a custom ROM that's Andriod 11 and you want a stock Andriod 12.
Therefore, I suggest that it's possible that you must be on stock Andriod 11 to update to stock Andriod 12.
I think that their is incompatibilities between the custom and the stock ROM causing the bootloop issue.
Which would mean the fill wipe of device and loss of all data I would assume. So save a back up what's needed.
So search for the MSM TOOL which will restore your device to it's wiped/stock state (might be only Andriod 11 at this point - not sure is MSM for Andriod 12 is available). Full update from 11 to 12 at that point should work. (I always utilize the full rom update - not the incremental update but not sure if that even matters).
Bottom line is that stock and custom ROMs irrespective of the Andriod base usually involve a complete device wipe and reset when switching from what little I know.
But, I believe I've been able to point you in the correct direction.
wugga3 said:
My best guess is that you need to be completely stock OOS11 to properly update to OOS12.
You say that your on a custom ROM that's Andriod 11 and you want a stock Andriod 12.
Therefore, I suggest that it's possible that you must be on stock Andriod 11 to update to stock Andriod 12.
I think that their is incompatibilities between the custom and the stock ROM causing the bootloop issue.
Which would mean the fill wipe of device and loss of all data I would assume. So save a back up what's needed.
So search for the MSM TOOL which will restore your device to it's wiped/stock state (might be only Andriod 11 at this point - not sure is MSM for Andriod 12 is available). Full update from 11 to 12 at that point should work. (I always utilize the full rom update - not the incremental update but not sure if that even matters).
Bottom line is that stock and custom ROMs irrespective of the Andriod base usually involve a complete device wipe and reset when switching from what little I know.
But, I believe I've been able to point you in the correct direction.
Click to expand...
Click to collapse
I was on stock oos 11 11.0.9.1 when I updated my phone through the oos system updates
Arnavgr said:
. P.S I am currently using a oos 11 based custom rom and I had replaced my phone screen with an unoriginal one(because I broke my original screen) if that makes a difference
Model:HD1901
Variant:India
Click to expand...
Click to collapse