i have a pixel 3a unlocked bootloader and running android 10 {hate it} trying to roll back with no luck also i have no recovery installed maybe its me phone is fine i want to install twrp but the biggest thing is i want to roll back to android 9 because of cell service problems this is harder then my pixel 2xl and 2 also are there any roms for this i only see two thanks
Wrong forum
Pixel 3a does not support twrp on android 10 yet afaik, https://twrp.me/site/update/2019/10/23/twrp-and-android-10.html
If you want to revert back to Android 9, download a Factory Image for your device from here https://developers.google.com/android/images, extract, boot phone in to bootloader and run the flash-all.bat. Make sure to back everything up first as this will wipe your device.
Related
Hey everyone, I've been trying to search for a solution to rooting my OP7 from T-Mobile and I think I have hit a dead end so I went ahead and created this post to ask for some advice.
So backstory: I have a business account with T-Mobile and they allow me to unlock my phone with little to no hassle at all, I unlocked my T-Mobile phone, and my OP7 got updated to Android 11 over night that I didn't realize it happened my current build is: Oxygen OS 11.0.1.1.GM31CB and my model is GM1915.
Okay so I am following this guide: https://www.xda-developers.com/unlock-bootloader-root-oneplus-7-pro/
I have followed through with Step 1, unlocking my OEM, and Step 2, unlocking my bootloader. So for step 3, the guide says to flash TWRP and from what I've read there is no TWRP that works for Android 11 right now so I am not sure if I can do that. Then step 4 is to flash Magisk after booting to recovery, but I am not sure if I can actually do that with TWRP?
So the question I got is how do I go about rooting my OP7? Can I root without TWRP? The guides video also said I needed a bin file of the current OS but there seems to be none available for GM31CB. Curious where I go from here. Can I roll back to Android 10? Do I need to switch over to the international version? and if I did would I be able to downgrade back to Android 10?
Thanks in advance.
Edit 1: I just converted to the international version and will be rooting that way.
was just about to answer you...hope u got it working the international way...i have twrp working...u must flash a zip to decrypt your internal...search or hit me later...i can email it to you or something...and if possible...next time you update to A11 Tmobile can you save it?....can't find it anywhere online...
That guide is pretty outdated I feel like. If you have you phone unlocked through T-Mobile you can simply follow this guide: https://forum.xda-developers.com/t/...unlock-twrp-root-and-update.3940368/#poststop
It's the one I followed to get my phone rooted + twrp installed.
I am in the same boat, T-mobile decided to push android 11 and rebooted. Android 11 is running fine with all my data intact but i have lost root and recovery. Trying to figure out easiest way to regain root, not worried about TWRP at the moment. Seems like patching the boot.img with magisk is the way to go but I cannot find a download from T-mobile for the full update to extract the payload.bin and boot.img. Is the payload.bin accessible using a file manager on the phone to copy to sdcard then transfer to PC? If not looks like waiting for some workaround or formatting data and starting from scratch
OOO just saw OPs edit, looks like i might be switching over to international firmware too and going that route. Did not plan on doing this today.
Hello all, after lurking here for a while, I found something that's making me post.
I have a carrier locked OP9. I just received the update to Android 12, and it has broken critical features. (Particularly not being able to stop apps from being closed accidentally!)
I have looked at Lineage OS in the past, and the process to get the LE2117's bootloader unlocked was... complicated.
However, while trying to fix other problems, rooting around in the developer options, I noticed that "unlock bootloader" was actually toggleable!
I think I have an unlocked bootloader now, but it's on android 12, and all the guides for rooting and installing a custom MOD for this phone say you must revert to android 11 before anything else.
So what now? Am I waiting for lineageOS 19 to come out, because that's the one based on android 12? I'm new to custom roms, and don't get the coding side of how all this works. (But I'm pretty determined to figure this out.)
Thanks for any help or advice you've got!
each stock update has a new firmware right now atleast all the roms are based on a11 latest firmware im not sure since oneplus got a12 if roms will switch to the newer firmware here is to hoping!
Gotcha, thanks. So waiting for lineage 19 it is, it sounds like, since that one is based off android 12.
dark_sable said:
Gotcha, thanks. So waiting for lineage 19 it is, it sounds like, since that one is based off android 12.
Click to expand...
Click to collapse
I am pretty sure there is root for 12. All you need to do is dump the payload from the 12 update OnePlus let's loose, and patch it with magisk and flash it via fastboot. Via bootloader it is easy I am using a TMobile OnePlus 9. All you need to do is revert back to 11 via a msm tool. There is a post here for that. After downgrading to unlock your bootloader is easy only takes time. There is a post for it I don't remember all the details but all you have to do is get you imei code and email OnePlus. Soon they will sent you a code to fastboot flash to unlock the bootloader. After that most of these 12 work for us on our model phone. I am using evolution x. It tells me every day I can go to 12 .
funkybear34 said:
each stock update has a new firmware right now atleast all the roms are based on a11 latest firmware im not sure since oneplus got a12 if roms will switch to the newer firmware here is to hoping!
Click to expand...
Click to collapse
Yes yes they do.
I've run into this same issue with wanting to use a Custom ROM. I have the T-Mobile version on A12 and it's now rooted. Another user shared the patched image file with me. I flashed it with fastboot boot boot.img then direct installed through Magisk to gain root. But all the custom roms here require A11 downgrade through the MSM tool and you have to use an MSM tool for T-Mobile, which was shared with me and explained but I'm not willing to downgrade. Until a custom ROM releases that I can flash on top of A12 I won't use it. I've had bad experiences with MSM tool to recover from brick and didn't succeed and had to send back to OnePlus for repair.
JimmyL216 said:
I've run into this same issue with wanting to use a Custom ROM. I have the T-Mobile version on A12 and it's now rooted. Another user shared the patched image file with me. I flashed it with fastboot boot boot.img then direct installed through Magisk to gain root. But all the custom roms here require A11 downgrade through the MSM tool and you have to use an MSM tool for T-Mobile, which was shared with me and explained but I'm not willing to downgrade. Until a custom ROM releases that I can flash on top of A12 I won't use it. I've had bad experiences with MSM tool to recover from brick and didn't succeed and had to send back to OnePlus for repair.
Click to expand...
Click to collapse
It amazes me how many people have problems with the MSM Tool. I was afraid I was going to have problems after reading all the issues people have had and had zero and I've used it twice. Both times I just put the phone in EDL and connected it to the USB-C port on my tower. Windows 11 surprisingly didn't even give me any issues.
EtherealRemnant said:
It amazes me how many people have problems with the MSM Tool. I was afraid I was going to have problems after reading all the issues people have had and had zero and I've used it twice. Both times I just put the phone in EDL and connected it to the USB-C port on my tower. Windows 11 surprisingly didn't even give me any issues.
Click to expand...
Click to collapse
I can't get my phone to go into EDL mode. Ever. Took every suggestion I've read. It just never went into EDL mode
JimmyL216 said:
I can't get my phone to go into EDL mode. Ever. Took every suggestion I've read. It just never went into EDL mode
Click to expand...
Click to collapse
What worked for me was shutting the phone off, removing my case, holding both volume up and down, then plugging the phone in. The screen won't show anything, you have to look at the MSM Tool and see that it's connected to know you did it right. Both times I tried it worked perfectly.
You can also use adb reboot edl if you can get the thing to boot and have USB debugging turned on.
i've never flashed firmware partitions before on my other 2 moto devices, i understand having read the install of lineage that this step is req'd for this model.
i'll be using the lineage recovery to install the rom flash, this is the method ive done before. My question is once i sideload the firmware partitions, will this automatically asign which partion the rom will be written too or do i have to tell it which one, im understanding that it will be either A or B partition??
I'd like to wipe/erase as much of the stock rom off the phone, remove everything and then flash the operating rom to a clean phone. Am i understanding this correctly or missing anything? Is there anything that i need or should know or do when at this step? any help/advice would be greatly appreciated.
This is a brand new phone out of the box, is there other ways that any of you would approach this phone to totally wipe it, i'm hoping that ill get the android 11 update immediatley over ota, i understand that i will have to go through intial setup, to get to unlocking the bootloader, wish i didnt have to do that, also i dont believe kiev has an official android 12 oem/factory rom but lineage has 19.1, im thinking install 18.1 and then later reflash android 12 when it comes out. Im talking to much.... any advice be great. TIA
First things first, know your device. Is it an XT2113-2 RETUS variant or something else? As long as the bootloader can be unlocked, it seems any kiev (qualcom) variant should work with lineageos - just best to know what you started with in the event you need to ask for assistance or you want to revert back to stock.
My suggestion assuming you are starting from a new phone out of the box with the plan of putting official lineageos (either 18.1 - android 11 or 19.1 - android 12) on it:
Have the phone ota update to the most recent stock firmware. For XT2113-2 RETUS at the time of this post, this is android 11 version RZKS31.Q3-45-16-8-3 released 2022.06.30. Lineageos currently uses the binary blobs from this version. I suspect having the latest stock radios and bootloader on your device will result in fewer issues and may likely make your life easier later.
After updating to the most current stock version, request the bootloader unlock key from the moto www site. You may need to wait 24-72 hours or longer before the phone will allow unlocking. Leave the phone on, connected to your (primary) carrier, and use your carrier data (i.e. not wifi) during this time.
After updating to the most current stock version, put all the sims in the phone for the carriers you plan to use and let the phone provision the carriers (I've read this can only be done on stock firmware - switching carriers without having done this step apparently requires going back to stock). Test that you can swap sims and use the phone as you need to (e.g. wifi calling, try visual voice mail, try 5 G, etc).
Unlock the bootloader. Be sure to leave the oem unlocking toggle to allow after unlocking the bootloader.
Most important: when coming from stock (either now or in the future), follow the instructions on the lineageos www site. In particular, flash the copy-partitions.zip following the sequence described in the lineageos instructions. Don't worry about the A/B partitions for now, the device will take care of itself. You only need to flash the copy-partions.zip when comming from stock (either now or if you reflash stock in the future and then want to go back to lineageos).
Flash official linageos 18.1, android 11 (not 19.1- android 12). 19.1 is the newest version; however it may have issues. 18.1 works great (for me) and it will likely be easier for you to check if everthing is working as you expect. Upgrade (via ota) to lineageos 19.1 in a month or two.
Updating official lineageos via ota, the device will flash to the appropriate A or B partition. You should not need to do anything unless there is an issue.
I'd like to wipe/erase as much of the stock rom off the phone ...
Click to expand...
Click to collapse
Following the lineageos installation instructions will accomplish that.
Good luck.
notmyrealhandle, thanks for your time and reply, perfect write, i understood everything you said. i never thought of doing ota via data as opposed to wifi, thanks. perfect​
Hello, I've been searching and lurking.. I've unlocked the bootloader on my Pixel 3a. I've rooted before, restored before, nandroids etc etc. So I've been in the game for a little while. (all the way back to my LG Ally!) Anyways. I was wondering what would be the best method of Rooting and installing TWRP on the Pixel 3a at this point in time, and if TWRP is even possible at this point. (September 2022) Should I use Magisk? NetHunter seems to rely on the device having TWRP in order to flash the kernel. (but we don't NEED it to flash the kernel do we?) I keep coming across old posts which do not apply to the build of my phone and I'm feeling very lost. This phone is not my daily driver, and I am confident when it comes to restoring a soft-brick. It's a Google Fi pixel, bought from the google store, maybe that helps.
Android 11, RQ2A.210405.005 (info from recovery)
BL Version : b4s4-0.3-7062600 (fastboot)
Baseband Ver: g670-00105-210113-B-7078968 (fastboot)
Secure Boot - Yes (fastboot)
HW Ver - MP1.0 (fastboot)
EDIT: Rooted phone successfully using Magisk/patched boot.img.
NEW ISSUE! : The phone is showing up as a Pixel 5 now. In rootchecker, my first successful root shows Pixel 3a as the device. This has never happened to me before. Any input would be greatly appreciated!
First, I apologize if these answers are already posted elsewhere, in which case please point me in the right direction.
So I use to be able to root my phones with my eyes closed (back when HSPA was the fastest and I needed to overclock my single core processor to 1.2GHz because my phone didn't have 8 cores), but its been 2 years since I've rooted my one plus 9 and I was pretty rusty then so I'm pretty much lost now. I know that over the years there's been changes to the way things must be done depending on the phone, version, etc. I'm trying to update my phone to either android 12 or 13, and unless I'm mistaken, I can't just flash an android 13 custom rom over the rooted OOS rom that is stock with the exception of having Magisk of course. If that's incorrect, that would be very convenient. But if I am, what steps do I need to do to get this done? I have SDK platform-tools ready, but I no longer have backups of the stock boot.img, or anything for that matter. My mother is a hypochondriac of sorts, so I can't have my phone not work for more than a day, or I'll have the police at my door doing a wellness check. Thanks in advance for any help!
Model: LE2117
SW ver. 11.2.3.3LE54CB
Use MSM Tool to reset your phone to initial factory firmware, which is OOS11. You can then update through OTA all the way to the latest.
And next time you root your phone, DON'T flash the patched boot.img. Instead, temporarily boot by the command fastboot boot <your_patched_boot.img> and then from Magisk app, use Direct Install. That way, Magisk will backup your original boot.img which you can restore later if there is a new OTA.
Do you have a token? Get one if you dont.
unlock token - OnePlus (United States)
www.oneplus.com
Takes a couple days to a month to get it. Check back at that page, they will not notify you when its ready.
Once you get it, MSM to global base A11\OOS11 to debrand, and also allow for easier updates since Tmobile is stingy about pushing out A13 recently.
Get to latest OTA update, fastboot flash cust-unlock <unlock_token.bin> to unlock BL, install Magisk anyway you want.