Hi all, I posted a question in the giant general "ask question here" thread but I'm thinking this might be more nuanced than I realize after I saw that thread about downgrading=brick.
I've got Z00A, I bought it new a month or two ago--'just tested' seller said but it looks like it was used up until october of last year. It was running android 5 and CM 12.1 (I think) and had TWRP 2.7 (I think). When setting it up I saw update about an update "CM13... nightly". Installed it, booted phone and it had no gapps and tried too many half assed solutions so I started over and installed TWRP 3, got Open Gapps and CM13-0522 and started over. Seemed to work great but then I noticed stuff like the camera would freeze or take pics that would come out a blank green screen and the mobile data connection almost never worked (though I'm on new carrier) and a few other problems. Is it possible that since I went from CM12 (and presumably no updates since october) straight to CM13-0522-nightly that I missed or somehow 'skipped' a bunch of firmware updates? Does the latest version not include the updates from previous versions?
I was going to try rolling back to stock via one of the ASUS ROMS but I have no idea what version to get because I cannot determine what I currently have or what the phone had to begin with (version as in "V2.20.##.###"). Also, I don't think I installed any ASUS rom before----I just installed CM13 and OpenGapps. Then I see posts about sideloading the ASUS firmware roms in regard to users trying to revert/reinstall firmware: is this what I should be doing?
I read the FAQ thread and searched what I could but it has only left me more confused. I'm fairly technically apt but cell phones are not at all my usual foray so any help is greatly appreciated.
ohituna said:
Hi all, I posted a question in the giant general "ask question here" thread but I'm thinking this might be more nuanced than I realize after I saw that thread about downgrading=brick.
I've got Z00A, I bought it new a month or two ago--'just tested' seller said but it looks like it was used up until october of last year. It was running android 5 and CM 12.1 (I think) and had TWRP 2.7 (I think). When setting it up I saw update about an update "CM13... nightly". Installed it, booted phone and it had no gapps and tried too many half assed solutions so I started over and installed TWRP 3, got Open Gapps and CM13-0522 and started over. Seemed to work great but then I noticed stuff like the camera would freeze or take pics that would come out a blank green screen and the mobile data connection almost never worked (though I'm on new carrier) and a few other problems. Is it possible that since I went from CM12 (and presumably no updates since october) straight to CM13-0522-nightly that I missed or somehow 'skipped' a bunch of firmware updates? Does the latest version not include the updates from previous versions?
I was going to try rolling back to stock via one of the ASUS ROMS but I have no idea what version to get because I cannot determine what I currently have or what the phone had to begin with (version as in "V2.20.##.###"). Also, I don't think I installed any ASUS rom before----I just installed CM13 and OpenGapps. Then I see posts about sideloading the ASUS firmware roms in regard to users trying to revert/reinstall firmware: is this what I should be doing?
I read the FAQ thread and searched what I could but it has only left me more confused. I'm fairly technically apt but cell phones are not at all my usual foray so any help is greatly appreciated.
Click to expand...
Click to collapse
You can flash mr gouravs work here via twrp
download all his files to phone ... follow his flashing procedure and you will be on the latest stock via twrp ..
http://forum.xda-developers.com/zenfone2/development/stock-rom-ul-z00a-ww-2-20-40-168-t3354526
So i followed the instructions to flash TWRP. this is the first time i have used a phone with the A and B type boot and when it was supposed to reboot to TWRP after flashing TWRP to A (my default boot.img was B) it instead loaded the OS. Confused i tried the process again and was relived to boot into TWRP. However i then discovered that TWRP had been flashed to both A and B. I am on the Three UK Razer phone and i can only access TWRP. I did a backup but I think it either didn't work or was wiped while i was trying to fix the issue. I would appreciate any suggestions or help anyone can offer. Thanks in advance.
Same here
And used also the backup files that was uploaded by one of members in here but so far not work
I purchased mine from amazon us
Anyway to fix our phones
Please
hi there, i got the same problem i flashed twrp exactly like you , i can only boot in twrp not in os . with boot.img from another guys here i managed get the bootanimation with the green circle but i can't boot or past that screen. i leave it for 4 hours ,drains the battery and shut itself off. after i read somewhere on this forum that if the boot partition(kernel) is matched with your system and won't boot in another phone ,i got the backup tried to restore none work. my phone is dead on the drawer , meanwhile i bought oneplus 5t sandstone white 128GB and i got like 12 roms on the Data partition and i don't know witch one to flash , so the difference for support for this two device is major . i will never buy a non popular phone
i will wait for them to release the factory image, (at the end of this year) i will flash it and i will sell it with 300 pounds less because razer
Just for you to know , they just released the robin phone factory image after that phone is obsolete
i also got a ****y phone from china witch is AndroidOne (xiaomi mi a1) witch meens is nexus /pixel like witch i got android 8.1 and in two weeks i got 4 updates streight from google .i was just amaze what support got this cheap phone . the point is next time when you buy a phone check if is popular on XDA forum
The razer phone got good spics and potential
But I wonder why it's unlike op5t in terms of support.
Let's skip the factory part but my main point on the developers in here , why we can't find help in here and support.
The reason there is fewer developers on this phone is cause there aren't factory images yet. Developers don't want to get there phone in a state that can't be reset and right now, that's razer phone. Razer has said that they are coming but I suspect like others, they haven't released them yet cause they are trying to get everything tweaked right before they release them. There really is no point having images for a phone that reintroduces issues they have already fixed with updates. I don't expect it will be much longer though.
OP and the like already have an established following that's why there are so many options. Also remember the 5t is still based on the 5 which already had a development community. Razer on the other hand is a new company and this is there first go at it. Once we see images released alot more developers will be more willing to jump on board. You see this with almost all new phone manufacturers.. You don't think htc and the like had developers lined up out the gate do you?
This phone wasnt released as a developer phone like the nexus line was. Razer has been quite good so far in terms of software updates and being in touch with the community as a whole.
I totally agree with you , my main point is to find solve for our corrupted phones and not only me having that issue.
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.
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
Hey all,
It's been a long time since I've been on these forums... Nexus 6p days to be exact.
I have a pixel 6 pro now and a pixel 2 XL just sitting around so I decided I wanted to try ROMing it.
I got root pretty easy but I cannot get TWRP to work right. I can boot from the recovery image but I cannot get it to install. It always says cannot mount system or vendor.
Any suggestions? Thanks
Edit: I am attaching pictures to show what happens when I switch slots A or B
Well, first thing is that you do not want to install TWRP, but only boot from it if you're planning to root. Magisk and TWRP have a bad interaction on the P2XL, and the device tends to bootloop. Second, you don't specify which version of TWRP you're using. You should be using v. 3.6.0 which was recently uploaded to the site. That should resolve the error messages you're seeing.