Related
If I am in a class of 1 in terms of rank stupidity please feel free to delete this post. :silly:I got sick of the updater nags. With a couple of previous Xiaomi phones I got away with finally saying yes to the OTA update which would inevitably fail after which the nags would stop for a good long while.
Not this time. I now have Miui 11 (which I did not want and which has a completely broken feedback function, btw) but lost root, magisk, and exposed.
I should also note that another Max 3 user posted here that permitting the OTA update bricked their device, so I guess things could be worse.
About to see if I can re root using the same method as before the update.
Sorry if I wasted anyone's time on the blindingly obvious.
Update: The Miui 11 OTA update completely broke screencasting on my phone. While previous updates crippled native miracast you could still use it within apps such as media players prime video etc. Not anymore. The new casting and widi settings see devices but do not connect successfully while apps with casting ability see no devices at all. If I can't get around anti rollback I'll have to buy a new phone.
brasscupcakes said:
Update: The Miui 11 OTA update completely broke screencasting on my phone. While previous updates crippled native miracast you could still use it within apps such as media players prime video etc. Not anymore. The new casting and widi settings see devices but do not connect successfully while apps with casting ability see no devices at all. If I can't get around anti rollback I'll have to buy a new phone.
Click to expand...
Click to collapse
Don't worry about anti-rollback unless you go back to rom that has no anti rollback. I go from miui 10 global to miuieu 11 P beta to miuieu 11 Q beta then back to miuieu 10 P stable. Now I settled on miuieu 11 P stable, yes miui 11 Q is very buggy. A few of my app don't work properly.
[Fix] Root on latest MIUI 11 build !
Just update Magisk Manager to 20.2 !
What's with a screen when charging, it keeps turnin on? Happens after MIUI 10 install...
Since the first version of Android Q, I could never do it Root, I can't make Magisk work, whatever I do.
I install it without problems, but when restarting it is not installed, I never have root.
Try 20.1 and 20.2, it still doesn't work.
I have a Mi Max 3 6/128
I installed the latest Miui 11 OTA update last night - taking a full Orangefox backup beforehand. After reboot, the phone was full of ads suddenly and it took me a while to figure out that root had been removed. I soon discovered that Orangefox had also been removed and replaced with a clunky-looking version of TWRP. I reflashed Orangefox and Magisk - coming back to recovery inbetween-times and it booted fine but the ads were still there so I tried to install Xposed via Magisk and that seems to have pretty much soft-bricked it. I can get into Orangefox where it said 'No Rom' which didn't seem like a good sign. I tried to re-flash the full backup I'd made with Organgefox yesterday (and this not really understanding Orange fox that well) but that hung at 'System image' - so I tried to flash without that and that succeeded but it's still totally bootlooping.
I'd very much appreciate some advice:
1. The Orangefox backup I made was with all the boxes ticked - i.e back up everything. I have the dim idea that trying to simply restore all of this won't work (it certainly doesn't seem to work). What parts of the full backup should I try to restore?
2. If I install the latest Global Miui 10 ROM - which is still Android 9 - using the Miui repair tool, will this brick the phone because of ARB? Or is it safe to do this?
3. Will dirty-flashing the latest Miui 11 rom via OrangeFox likely make something I can at least boot up and get some data (it turns out that 'SMS backup and restore' hasn't been working for weeks so I don't have a pile of work texts that I really wouldn't like to lose)?
4. Any other suggestion most gratefully received. Thanks in advance.
(Thinking about it, this thread is for the OTA breaking the MI Max 3, not my particular woes with restoring an Orange Fox backup - so, with apologies, I'll post in the Mi Max3/Orange Fox thread.)
PS: Flashing the OTA again fixed it, short term: no root is better than no phone.
This info is for people who are finding it difficult to install a custom ROM or who are just waiting for the right time to experiment. This method is fail-safe. Any support needed, I am here to help .
To start with:
I unlocked my RM5P bootloader was able to install custom recovery and even root my phone, but I was not able to install a custom ROM ----- till yesterday night (I am on EVO X now).
Failed attempts:
I was able to downgrade to RMX1971EX_11_OTA_0170 with stock recovery but after loading the ROM, I cannot load into FASTBOOT.. Again to get into fastboot, I needed to upgrade to CO1 (Android 10).
Then from fastboot mode, I tried installing ROM (very old version) thus maintaining the TWRP and Fastboot.
I tried to install custom ROM, it gave me error 7. This error is because the Firmware was too old for the custom ROM to be installed.
Success:
I then installed color os V 170 from TWRP (it can decrypt OZIP files-it will covert that to zip and install). Used just common sense, as all custom ROMs at present need color os (specifically version ...170), so after installing ROM using TWRP and staying in the recovery (because if I load ROM now, I will lose FB and TWRP), I Dirty Flashed (just to be on the safe side) custom ROM (EVO X) , and then format data (might still give you error, there is a workaround) and restart. That's it.
I am in Evolution X latest build.
ADVICE:
Whatever experiments you want to do on your mobile, do it while you are in WARRANTY (after confirming you have your service center nearby and working). If your phone ends up bricked (like me-before) get it fixed free of cost. BECOME A PRO WITHIN THE WARRANTY PERIOD.
Oh well that's extremely nice of you and useful. You're helping the community of this device a great deal with your informational and technical guides. I can safely thank you in the name of all users.
Though I'm feeling kind of sorry and bad for you. You really weren't able to use custom ROMs till 14th of May? Geez... That must've been horrible. I'm a fan of pure and stock like, simple, well modable/shapeable Android since I was a kid and got my Samsung Galaxy phone with Android 2.1 back in 2009. Since then I can't stand any limitation brought by Android skins like Miui or Color OS. I was on GSI ROM on the third day of having my Realme Q back in October of 2019. Not like warranty did count anything since there's no Realme in Hungary and it was an import device from AliExpress. So many testing and experience, lots of adventure. Can't even imagine what would I have done if I couldn't get rid of COS till now. Even the thought is maddening to me ? You've got my respect.
greenys' said:
Oh well that's extremely nice of you and useful. You're helping the community of this device a great deal with your informational and technical guides. I can safely thank you in the name of all users.
Though I'm feeling kind of sorry and bad for you. You really weren't able to use custom ROMs till 14th of May? Geez... That must've been horrible. I'm a fan of pure and stock like, simple, well modable/shapeable Android since I was a kid and got my Samsung Galaxy phone with Android 2.1 back in 2009. Since then I can't stand any limitation brought by Android skins like Miui or Color OS. I was on GSI ROM on the third day of having my Realme Q back in October of 2019. Not like warranty did count anything since there's no Realme in Hungary and it was an import device from AliExpress. So many testing and experience, lots of adventure. Can't even imagine what would I have done if I couldn't get rid of COS till now. Even the thought is maddening to me You've got my respect.
Click to expand...
Click to collapse
I appreciate your time and message.
I have only dared once in my lifetime to experiment on a tablet i bought online on the first day, that time i restored it with another rom, and even replaced that gadget after 2 days for another one because it didn't have multi touch, many years ago.
With realme, i was kind of scared to experiment till some months back and i even had to visit service centre thrice to restore. Now i have learned a bit on how we can BRICK our phone.
One important thing i learned is, STOCK rom is the best, and i am back on it.
Thank you.
jijojamie said:
I appreciate your time and message.
I have only dared once in my lifetime to experiment on a tablet i bought online on the first day, that time i restored it with another rom, and even replaced that gadget after 2 days for another one because it didn't have multi touch, many years ago.
With realme, i was kind of scared to experiment till some months back and i even had to visit service centre thrice to restore. Now i have learned a bit on how we can BRICK our phone.
One important thing i learned is, STOCK rom is the best, and i am back on it.
Thank you.
Click to expand...
Click to collapse
Ah I see! That's indeed a whole adventure. Thank you for sharing. It was worth reading
jijojamie said:
This info is for people who are finding it difficult to install a custom ROM or who are just waiting for the right time to experiment. This method is fail-safe. Any support needed, I am here to help .
To start with:
I unlocked my RM5P bootloader was able to install custom recovery and even root my phone, but I was not able to install a custom ROM ----- till yesterday night (I am on EVO X now).
Failed attempts:
I was able to downgrade to RMX1971EX_11_OTA_0170 with stock recovery but after loading the ROM, I cannot load into FASTBOOT.. Again to get into fastboot, I needed to upgrade to CO1 (Android 10).
Then from fastboot mode, I tried installing ROM (very old version) thus maintaining the TWRP and Fastboot.
I tried to install custom ROM, it gave me error 7. This error is because the Firmware was too old for the custom ROM to be installed.
Success:
I then installed color os V 170 from TWRP (it can decrypt OZIP files-it will covert that to zip and install). Used just common sense, as all custom ROMs at present need color os (specifically version ...170), so after installing ROM using TWRP and staying in the recovery (because if I load ROM now, I will lose FB and TWRP), I Dirty Flashed (just to be on the safe side) custom ROM (EVO X) , and then format data (might still give you error, there is a workaround) and restart. That's it.
I am in Evolution X latest build.
ADVICE:
Whatever experiments you want to do on your mobile, do it while you are in WARRANTY (after confirming you have your service center nearby and working). If your phone ends up bricked (like me-before) get it fixed free of cost. BECOME A PRO WITHIN THE WARRANTY PERIOD.
Click to expand...
Click to collapse
Can you guide me please , currently i am on realme ui c.04 latest update , wanna go back to color os ( for flashing custom roms ) how can i safely downgrade without loosing fastboot and custom recovery ( as of now bl is locked and everything is stock )
Here's the step i am thinking to follow
Unlocking bl and flashing twrp while in realme ui and from twrp flashing color os 6 zip file and and without booting , flashing the custom rom and then wipe data and then reboot
Will j have bootloader and recovery accessible then ?
grand2SD said:
Can you guide me please , currently i am on realme ui c.04 latest update , wanna go back to color os ( for flashing custom roms ) how can i safely downgrade without loosing fastboot and custom recovery ( as of now bl is locked and everything is stock )
Here's the step i am thinking to follow
Unlocking bl and flashing twrp while in realme ui and from twrp flashing color os 6 zip file and and without booting , flashing the custom rom and then wipe data and then reboot
Will j have bootloader and recovery accessible then ?
Click to expand...
Click to collapse
Correct. I had only twrp and no bootloader after installing custom ROM. Please avoid DIRTY FLASHING.
Gud luck.
jijojamie said:
Correct. I had only twrp and no bootloader after installing custom ROM. Please avoid DIRTY FLASHING.
Gud luck.
Click to expand...
Click to collapse
You saying avoid dirty flash then how to flash custom after color os ( assuming not booting into color os , staying in recovery )
Please help with steps after flashing color os through recovery
Andyou had no bootloader after custom rom , then how did you managed to get bootloader back
grand2SD said:
You saying avoid dirty flash then how to flash custom after color os ( assuming not booting into color os , staying in recovery )
Please help with steps after flashing color os through recovery
Andyou had no bootloader after custom rom , then how did you managed to get bootloader back
Click to expand...
Click to collapse
Avoid installing custom roms using duty flash, i mean the second custom rom should be done as clean install. I said that specifically because, i tried three roms in a span of 1 hour, the third duty flash (derpfest rom) gave me indefinite boot. Had to go to service centre because phone was not bootng to twrp.
I went back to custom rom, Android 10 to get BL back. Anyways, i was not that satisfied with the present custom roms available.
But that's me, you can go ahead and try roms.
jijojamie said:
Avoid installing custom roms using duty flash, i mean the second custom rom should be done as clean install. I said that specifically because, i tried three roms in a span of 1 hour, the third duty flash (derpfest rom) gave me indefinite boot. Had to go to service centre because phone was not bootng to twrp.
I went back to custom rom, Android 10 to get BL back. Anyways, i was not that satisfied with the present custom roms available.
But that's me, you can go ahead and try roms.
Click to expand...
Click to collapse
Thanks for help , but in any case , I don't wanna mess up to such extent that i have to go service center ,
Can scenario get that bad ?
I mean fastboot gone , twrp not booting up
Also you just flashed custom 10 rom from twrp n got bootloader
And one more thing i wanna try derpfest rom android 10 version
So please have a look at these steps
Color os zip flash by twrp , then wipe data without booting and flashing derpfest 10.0
How will that go , i mean will i have bootloader
grand2SD said:
Thanks for help , but in any case , I don't wanna mess up to such extent that i have to go service center ,
Can scenario get that bad ?
I mean fastboot gone , twrp not booting up
Also you just flashed custom 10 rom from twrp n got bootloader
And one more thing i wanna try derpfest rom android 10 version
So please have a look at these steps
Color os zip flash by twrp , then wipe data without booting and flashing derpfest 10.0
How will that go , i mean will i have bootloader
Click to expand...
Click to collapse
I suggest you check this with another derpfest user, please. I never got to boot to derpfest.
I downloaded Evolution X 4.7 Rom zip file and followed the instructions given in thread to flash zip file. But after flashing when I tried to reboot in system, it gave me a message on swipe screen that OS is not installed but still I swiped to boot in system. My device tried to boot a couple of time and ended up in fastboot again. Fortunately I had already made backup so I restored my backup.
As per your post I should have flashed color os 6 ozip file with twrp before flashing evox rom.
Every thing ok.i think you are not flash Vebeta after flash recovery.
As the title says. I've seen some older posts from 2019 about it not working, and need to know its status as of right now. I checked their website, and it provides a guide for this specific model, but it doesn't work. What else can I use?
Twrp has not worked on our phones since Android 9. So no it does not work on 10 or on 11
Tom Dude said:
As the title says. I've seen some older posts from 2019 about it not working, and need to know its status as of right now. I checked their website, and it provides a guide for this specific model, but it doesn't work. What else can I use?
Click to expand...
Click to collapse
According to the TWRP website their latest release 3.5 does work on Android 10 and they are working to get it usable on Android 11
Unfortunately our device tree is outdated; there is no android 10 branch let alone 11. The latest release for our device is for those still on android 9, as denoted by TeamWin's new naming convention. If a new branch for 10 and/or 11 can be added to Github, maybe we'll see a build that works for those that have moved on from pie.
GitHub - TeamWin/android_device_google_bonito
Contribute to TeamWin/android_device_google_bonito development by creating an account on GitHub.
github.com
41rw4lk said:
Unfortunately our device tree is outdated; there is no android 10 branch let alone 11. The latest release for our device is for those still on android 9, as denoted by TeamWin's new naming convention. If a new branch for 10 and/or 11 can be added to Github, maybe we'll see a build that works for those that have moved on from pie.
GitHub - TeamWin/android_device_google_bonito
Contribute to TeamWin/android_device_google_bonito development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
so what does this mean?
i just got a brand new 3a XL
i updated it to 11 and now the phone has so many issues that it is not even useable for me anymore, i need to go back to 9 or flash a custom ROM
so can i downgrade it to pie or dirty flash a stock pie rom and then install TWRP on it and flash a custom rom?
or am i now stuck on a 11 with no way to flash to an older stock rom or custom rom or install TWRP?
also if you install TWRP on 9 then i assume you can still flash a stock 10 or 11 rom and revert back to 9 right
gdroid666 said:
so what does this mean?
i just got a brand new 3a XL
i updated it to 11 and now the phone has so many issues that it is not even useable for me anymore, i need to go back to 9 or flash a custom ROM
so can i downgrade it to pie or dirty flash a stock pie rom and then install TWRP on it and flash a custom rom?
or am i now stuck on a 11 with no way to flash to an older stock rom or custom rom or install TWRP?
also if you install TWRP on 9 then i assume you can still flash a stock 10 or 11 rom and revert back to 9 right
Click to expand...
Click to collapse
i see you quoted my post but it is blank
also i am having major problems navigating this new site now , it logs me out whenever i do anything or move between pages and then i can no longer log in it gives an error " Security error occurred. Please press back, refresh the page, and try again. "
on chrome
First you might want to post what issues you are having in 11 as really there have not been many postings about issues on 11 at all.
That said to answer your question:
Android 9 is very old and of course no longer being updated. I cannot even think of a custom rom that is still based on android 9, but if your dead set on going back to 9 and being a huge security risk you need to download the last android 9 full from from google factory images and run the flash-all file either vat or sh depending on what os your on, This will completely wipe your phone.
If you want to try a custom rom there are very few that are actively updated. The only one I can think of that I KNOW is updadated and current is LOS. Unfortunately while it works really well there is absoluetly no support at all for it on our phone. Not even a dedicated xda thread for it. I wqas on it for a while but ran into an issue with dialing 911. Not sure if it was an LOS issue or not but immediately went bqck to stock with custom kernel after that and have been that way ever since.
To summarize:
Android 9 is basically dead and outdated.
Android 10 lives on only in the very few custom roms available
Android 11 at least for me is at least as stable and usable as 9 or 10 was
TWRP is likely never going to return to our phone and honestly really isnt needed anymore. Really the only thing we cannot do anymore is flash something directly from our phone. Without TWRP you must now flash all images and kernels and such from a pc.
Yeah this site is not quite ready for prime time yet. I also have constant issues with it. Hopefully the reply goes through this time
gdroid666 said:
so what does this mean?
i just got a brand new 3a XL
i updated it to 11 and now the phone has so many issues that it is not even useable for me anymore, i need to go back to 9 or flash a custom ROM
so can i downgrade it to pie or dirty flash a stock pie rom and then install TWRP on it and flash a custom rom?
or am i now stuck on a 11 with no way to flash to an older stock rom or custom rom or install TWRP?
also if you install TWRP on 9 then i assume you can still flash a stock 10 or 11 rom and revert back to 9 right
Click to expand...
Click to collapse
Haven't seen a reply
gdroid666 said:
i see you quoted my post but it is blank
also i am having major problems navigating this new site now , it logs me out whenever i do anything or move between pages and then i can no longer log in it gives an error " Security error occurred. Please press back, refresh the page, and try again. "
on chrome
Click to expand...
Click to collapse
Did you see the reply this time?
adm1jtg said:
Haven't seen a reply
Did you see the reply this time?
Click to expand...
Click to collapse
yes i can see it
the problems i have are
1)using assistant via "hey Google" does not respond to what i say, instead it brings up a menu of suggestions , and i have to repeat myself
or sometimes it won't work at all just says can't reach google try again later
2) smart lock trusted device does not work it constantly relocks my phone after minutes no matter what trusted bluetooth devices are paired , not only annoying but dangerously distracting while driving"
3) problems with android auto and android auto with assistant ,
4) bug where pressing the volume rocker to adjust media or ringer volume (in either direction) causes all sound, media or ringer to just stop
5)problems with the accessing the phone screen while in a call
when i pull the phone from my ear and go to use the screen when in a call the screen goes off and is not responsive to touch then it goes on for a split second , then off, then on, then off , then on
seems like the software service that controls the (light?) sensor that detects if the phone is being held to your ear is not working right, i had issues with this on my nexus 6p too though but it had a different sort of behavior , it would just be black and unresponsive and i had to press the power button to wake the screen again, and i had to stop using power button ends call cause it would end the call whenever i needed to use my screen while in a call and the glitch happened and kept the screen from waking when i pulled away from my ear
6) sometimes get glitches with the app switcher/recents
sometimes the "pill" gesture does not respond and i can not bring it up at all,
and the animations are all glitched out too nearly all the time
animations are a mess jumpy, glitchy ,shaky
it's going to give someone a seizure
7) no visual VM tab in the stock phone dialer app
this was working on 9 on another 3aXL ut stopped after update to 10 ,same carrier but this had been a problem on the nexus 6p too
off /on issue , mostly off
8) texting photos to IOS devices does not go through now
i thought it said you could install TWRP on the 3a XL if you were on Android 9
so what i was asking is, what happens if you dirty flash a stock Android 9 ROM? then would i be able to install TWRP from there
or i can not do it now since i updated it to 11?
I am just curious if it can be done, I will probably just take your advice and stay on 11 for now though and hope there is aoe improvements in android 12 developer preview
i am not at all hopeful though
and after testing my old phone some of the same assistant and auto bugs are on those devices too so i guess it is just issues with assistant that cropped up the same ties i updated
gdroid666 said:
yes i can see it
the problems i have are
1)using assistant via "hey Google" does not respond to what i say, instead it brings up a menu of suggestions , and i have to repeat myself
or sometimes it won't work at all just says can't reach google try again later
Cant comment on this as I dont use assistant
2) smart lock trusted device does not work it constantly relocks my phone after minutes no matter what trusted bluetooth devices are paired , not only annoying but dangerously distracting while driving"
Dont use smartlock either
3) problems with android auto and android auto with assistant ,
Dont use android auto either
4) bug where pressing the volume rocker to adjust media or ringer volume (in either direction) causes all sound, media or ringer to just stop
Never had this happen and had this phone on both stock 10 and 11 and also on LOS 17.1
5)problems with the accessing the phone screen while in a call
when i pull the phone from my ear and go to use the screen when in a call the screen goes off and is not responsive to touch then it goes on for a split second , then off, then on, then off , then on
seems like the software service that controls the (light?) sensor that detects if the phone is being held to your ear is not working right, i had issues with this on my nexus 6p too though but it had a different sort of behavior , it would just be black and unresponsive and i had to press the power button to wake the screen again, and i had to stop using power button ends call cause it would end the call whenever i needed to use my screen while in a call and the glitch happened and kept the screen from waking when i pulled away from my ear
Never had this happen with any of the above roms either
Could your tempered glass somehow be blocking the sensor as I have heard of symptoms like that being caused by one.
6) sometimes get glitches with the app switcher/recents
sometimes the "pill" gesture does not respond and i can not bring it up at all,
and the animations are all glitched out too nearly all the time
animations are a mess jumpy, glitchy ,shaky
it's going to give someone a seizure
Not helpful I know but also never seen this occur in all my time using many android phones
7) no visual VM tab in the stock phone dialer app
this was working on 9 on another 3aXL ut stopped after update to 10 ,same carrier but this had been a problem on the nexus 6p too
off /on issue , mostly off
Only seen this when your not using the correct/default stock phone apk
8) texting photos to IOS devices does not go through now
I text stuff to iphones all the time, could be a carrier or apn issue
i thought it said you could install TWRP on the 3a XL if you were on Android 9
I was never on android 9 on this phone but I believe thats correct. However you would lose all security updates for well over a year and a half or so. I BELIEVE the last android 9 rom update was aug 2019
so what i was asking is, what happens if you dirty flash a stock Android 9 ROM? then would i be able to install TWRP from there
or i can not do it now since i updated it to 11?
You could go back but it would not be advised and since twrp shares the boot partition as soon as you flashed any rom greater the android 9 you would lose twrp.
I am just curious if it can be done, I will probably just take your advice and stay on 11 for now though and hope there is aoe improvements in android 12 developer preview
i am not at all hopeful though
and after testing my old phone some of the same assistant and auto bugs are on those devices too so i guess it is just issues with assistant that cropped up the same ties i updated
Click to expand...
Click to collapse
ugh I really am not liking this new forum format. I answered each of your line items under each number but it really isnt showing up very well.
Sorry it has taken so long to respond but i wanted to give a complete answer. Given all the issues you are having and that in my personal opinion going back to 9 really isnt a good idea I would recommend giving los 17.1 a try. It will NOT get you twrp but it is based on android 10, and updated weekly. The only downside to LOS 17.1 is that there is literally no support at all. Even the responsibvle dm's I dont believe even own our phone. That said it ran perfactly for me except a wierd 911 issue that may or may not have been due to LOS. I am seriously thinking of going back to LOS myself, am just really lazy as I would have to redo my entire phone and start with a clean android 10 stock flash.
When you have backup religion: 'tWRp IsNt NEedEd ANyMoRE'
Yet nobody can answer OP's question.
ssurell said:
When you have backup religion: 'tWRp IsNt NEedEd ANyMoRE'
Yet nobody can answer OP's question.
Click to expand...
Click to collapse
There is no alternative for our device running 10 or 11. If we had a device tree newer than 9 we could probably get an auto build from teamwin, but as of now there is none.
As for backing up, most things are backed up using cloud services, not to mention twrp isn't so elegant on a/b devices. You have to reinstall after updates, it can interfere with built in updaters, and restoring backups on a/b devices seem to cause more problems that anything.
41rw4lk said:
There is no alternative for our device running 10 or 11. If we had a device tree newer than 9 we could probably get an auto build from teamwin, but as of now there is none.
As for backing up, most things are backed up using cloud services, not to mention twrp isn't so elegant on a/b devices. You have to reinstall after updates, it can interfere with built in updaters, and restoring backups on a/b devices seem to cause more problems that anything.
Click to expand...
Click to collapse
An often repeated mantra it seems that has little to do with creating and restoring partition images. Where I might agree is the lack of need for an elaborate gui to perform update and flash procedures. Seems LOS recovery could fit a dd function into the recovery partition. But lack of user control over boot slot after a crap system update is all the code politics I need to know. No wonder DU folded up.
I have a working TWRP for Android 11.
Captain_Throwback said:
I have a working TWRP for Android 11.
Click to expand...
Click to collapse
Well throw us a link and give any disclaimers you may have about us using it lol
adm1jtg said:
Well throw us a link and give any disclaimers you may have about us using it lol
Click to expand...
Click to collapse
I posted it in the Telegram group here: https://t.me/pixel3a/161825
Hello. My phone 1st received ota update miui 12 919mb. I tried to install it and something went wrong. Then I went back to settings check for update and this time it gave me full rum update with the new miui 12 with the volume of 2 GB with android 10 miui 12 integrated. It might be stupid question but I want to make sure if I install this full OTA update well the internal memory be formatted? Because my applications and internal files are very important to me and I don't want to reinstall whole application I can't waste time for that. Flash this downloaded update using TWRP? The main question is that well the internal memory will be formatted or this OTA update will reinstall the current one in the phone and the phone will work normally? My phone is redmi note 8 pro, TWRP installed and rooted and bootloader unlocked running on Android 10 MIUI 11
rovshanst said:
Hello. My phone 1st received ota update miui 12 919mb. I tried to install it and something went wrong. Then I went back to settings check for update and this time it gave me full rum update with the new miui 12 with the volume of 2 GB with android 10 miui 12 integrated. It might be stupid question but I want to make sure if I install this full OTA update well the internal memory be formatted? Because my applications and internal files are very important to me and I don't want to reinstall whole application I can't waste time for that. Flash this downloaded update using TWRP? The main question is that well the internal memory will be formatted or this OTA update will reinstall the current one in the phone and the phone will work normally? My phone is redmi note 8 pro, TWRP installed and rooted and bootloader unlocked running on Android 10 MIUI 11
Click to expand...
Click to collapse
Hello, The latest version of MIUI12 is buggy... my son's phone is rebooting in loop... I am coming here if someone has an idea to get data back from the phone.... . Before doing anything, it is much recommended to save your data first in a safe place ...
NeveRFT said:
Hello, The latest version of MIUI12 is buggy... my son's phone is rebooting in loop... I am coming here if someone has an idea to get data back from the phone.... . Before doing anything, it is much recommended to save your data first in a safe place ...
Click to expand...
Click to collapse
Thanx i got backups but just its very boring and time consuming to restore and get phone back to its previous state
rovshanst said:
Thanx i got backups but just its very boring and time consuming to restore and get phone back to its previous state
Click to expand...
Click to collapse
Yes, understood, but at least you have potentially your data. It is not the case of my son and his phone is on hold for more than a month now waiting for a solution ...
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.