I tried to sideload the Android 13. It was downloaded and said to restart. But when i restarted the device, it didn't boot with android 13. Aappeared as before (11). Anyone with any guideline/help/information would be highly appreciated.
Google has not made an Android 13 for our phone, so we have to turn to custom roms.
There is a beta version 13 of ArrowOS, but it is not really ready for normal use. But they are working on it.
At the moment, your best bet is a version 12 custom rom.
You don't need root to flash a custom rom, but an unlocked bootloader is necessary. If you have one of those phones that can't be unlocked (Verizon, I think), then you are out of luck.
runekock said:
Google has not made an Android 13 for our phone, so we have to turn to custom roms.
There is a beta version 13 of ArrowOS, but it is not really ready for normal use. But they are working on it.
At the moment, your best bet is a version 12 custom rom.
You don't need root to flash a custom rom, but an unlocked bootloader is necessary. If you have one of those phones that can't be unlocked (Verizon, I think), then you are out of luck.
Click to expand...
Click to collapse
Thank You
Related
Hello everybody!
I am fairly new to the modding world of android, all I know is that you need an unlocked bootloader to install a custom recovery to then root or install a custom rom. I have a specific set of questions to upgrading my phone software (Lenovo P2a42 on android 7.0):
1) Do you do anything after waiting for 14 days on the OEM unlock screen? Does it auto reset the phone, will a pop up appear, etc? Does it automatically unlock the bootloader or do I need to do adb fastboot oem unlock to finalize unlock?
2) Is there a complete all-in-one guide to installing a custom rom (bootloader unlock, TWRP, flashing, dealing with problems (encryption, fingerprint, wifi, safetynet, etc), etc) from scratch (stock rom)?
3) Is there a way I can back everything up (and recover of course, stock image and recovery, and anything else I might need to go back to factory defaults) in case I screw anything up?
4) What is the least buggiest / most popular / most supported android pie rom available for my phone (Lenovo P2a42)?
5) Anything I should know before proceeding? For example, I know it voids warranty and official support, potentially loosing google playstore, but is there anything else I should know?
I might require further assistance, as I have absolutely no experience. But hey, I gotta start somewhere right?
Thank you for your time.
1.on day 14 the option to unlock is shown in the settings menu.
2. I used this
https://forum.xda-developers.com/lenovo-p2/development/lenovo-p2-root-tool-t3800838
3.TWRP has a backup option in the Recovery menu.
Read the TWRP threads to understand better.
4.for me I like 8.1
https://forum.xda-developers.com/lenovo-p2/development/rom-aospextended-rom-v5-4-t3774641
But am currently using 9.0
https://forum.xda-developers.com/lenovo-p2/development/rom-arrowos-9-x-t3862818
5.anything else to know?
Just make sure you read the thread for whichever ROM you use.
And then enjoy
Treboeth said:
1.on day 14 the option to unlock is shown in the settings menu.
2. I used this
https://forum.xda-developers.com/lenovo-p2/development/lenovo-p2-root-tool-t3800838
3.TWRP has a backup option in the Recovery menu.
Read the TWRP threads to understand better.
4.for me I like 8.1
https://forum.xda-developers.com/lenovo-p2/development/rom-aospextended-rom-v5-4-t3774641
But am currently using 9.0
https://forum.xda-developers.com/lenovo-p2/development/rom-arrowos-9-x-t3862818
5.anything else to know?
Just make sure you read the thread for whichever ROM you use.
And then enjoy
Click to expand...
Click to collapse
The 8.1 rom you provided is AOSPExtended, is there a 9.0 version of it for the P2a42?
Thank you for your time.
404 Name Not Found said:
The 8.1 rom you provided is AOSPExtended, is there a 9.0 version of it for the P2a42?
Thank you for your time.
Click to expand...
Click to collapse
I believe 9.0 is being worked on,it has been released for other phones.
Glad to help
Hello,
I currently have a XZ2 compact H8324 rooted
Build number : 52.0.A.3.126
I rooted it some years ago and to be honest I don't remember well what I used to do it. I just remember DRM are safe.
The bootloader is unlocked if I remember well (warning message at boot)
Could someone please tell me how to update to latest Android version still rooted ?
I don't care about format it, but I would like it to work as usual (camera stuff) with root.
Is there some kind of precautions ? tools ?
Thank you.
Edit : downloading 52.1.A..3.49 with XperiFirm currently
Xperifirm might work. You can also try Emma (Sony's official flashing tool) which is easier to use but will wipe your device and uninstall any custom recovery you have installed. Your bootloader will remain ulocked, and your DRM keys intact, so you can always reinstall custom recovery after that.
You can also install LineageOS. They have an official 17.1 (Android 10) build for the XZ2 Compact, so it should be very stable and have minimal issues. I'd recommend installing LineageOS after flashing the latest firmware with Xperifirm/Emma because the stock ROM doesn't play nice if you have root or TWRP installed.
Thanks @dankcuddlybear for your answer.
I don't care about custom recovery and data as long as I'm able to flash back custom recovery and root after flash.
If your current Pie variant is fast, stable and is fulfilling its mission, be happy and leave it be.
Q is using cpu cycle wasting scope storage and is a downgrade in many ways from Pie.
Being rooted means you could (?) overcome many of these limitations but how much is your time worth?
Android 10,11(Apple) woke, go broke
blackhawk said:
If your current Pie variant is fast, stable and is fulfilling its mission, be happy and leave it be.
Q is using cpu cycle wasting scope storage and is a downgrade in many ways from Pie.
Being rooted means you could (?) overcome many of these limitations but how much is your time worth?
Android 10,11(Apple) woke, go broke
Click to expand...
Click to collapse
It is not... screen hangs for no reason and needs to switch it off and on
And last week i had to force hardware button reboot as it was stuck
Orphee said:
It is not... screen hangs for no reason and needs to switch it off and on
And last week i had to force hardware button reboot as it was stuck
Click to expand...
Click to collapse
Not good. Pie should be rock solid stable.
It sounds like it's fixing to crash and burn.
Look at the launcher and other 3rd party apps you're using. That load maybe corrupted or the original firmware was flawed.
I assume OTA would break root, is there a certain way to do this other than flashing a custom Android 11 Rom? I'd prefer to be on stock Android 11 with root but not sure how to go about it
BWA_Dallas said:
I assume OTA would break root, is there a certain way to do this other than flashing a custom Android 11 Rom? I'd prefer to be on stock Android 11 with root but not sure how to go about it
Click to expand...
Click to collapse
So, if it's rooted, you won't get an update, or rather you won't be able to apply it. So it won't 'break' root, it just won't happen.
Sure, just crossflash to the newer rom, it has no effect on root. Doing so doesn't affect root, it will stay exactly as it was prior to crossflashing.
BWA_Dallas said:
I assume OTA would break root, is there a certain way to do this other than flashing a custom Android 11 Rom? I'd prefer to be on stock Android 11 with root but not sure how to go about it
Click to expand...
Click to collapse
Forgot you're using an at&t rom, and those kdz aren't available. So, choices, go to an 'open' rom, which should have much of the at&t functionality, but maybe not all. Or, re lock the boot loader, do the update ota, and then root it again.
Be careful though, to relock a boot loader the rom has to be completely stock, no mods whatsoever.
personally, I'd just go with one of the 'open' roms... and I'd never use at&t lol, but that's just me.
AsItLies said:
Forgot you're using an at&t rom, and those kdz aren't available. So, choices, go to an 'open' rom, which should have much of the at&t functionality, but maybe not all. Or, re lock the boot loader, do the update ota, and then root it again.
Be careful though, to relock a boot loader the rom has to be completely stock, no mods whatsoever.
personally, I'd just go with one of the 'open' roms... and I'd never use at&t lol, but that's just me.
Click to expand...
Click to collapse
Do you have a particular open rom you recommend?
BWA_Dallas said:
Do you have a particular open rom you recommend?
Click to expand...
Click to collapse
LG G820QM(LMG820QM) aka LG G8 ThinQ - LG-Firmwares.com
LMG820QM download the firmware for free! Detailed installation instruction. Video review of the model and its features. User feedback and latest news.
lg-firmwares.com
I'd suggest the USA version, it's the us open, should have all the functionality for all the carriers, minus the bloatware.
Except for one thing, some carriers, like at&t, have in the past, not sure if they still do, limit things like volte ability to just their phones / roms.
that, and because they don't make their kdz available, I would never use them.
Hello everyone,
I have a problem. I tried installing Nameless ROM on my OnePlus 9 Pro with no success. After that I reflashed my phone using MsmTool. Than I've updated it do 11.2.10.10 and later to C.47. But when I installed C.47 phone rebooted to recovery and when I selected reboot It wouldn't boot. Don't know what I'm doing wrong. My bootloader is locked.
Which phone version do you have?
luckylui said:
Which phone version do you have?
Click to expand...
Click to collapse
You mean software version or phone model?
Right now I'm on 11.2.10.10
My phone model is LE2120
skrubxgt said:
You mean software version or phone model?
Right now I'm on 11.2.10.10
My phone model is LE2120
Click to expand...
Click to collapse
Phone model.
So, I'd try it this way..
Since you are already on 11.2.10.10, I'd unlock the bootloader. (It'll wipe the device)
Download Oxygen Updater and download the stock versions through their.
Local update through your phone settings.
Once you are on A12 I'd follow the steps to installing Nameless.
My phone model is 2127 and I'm running Pixel Experience with no issues.
luckylui said:
Phone model.
So, I'd try it this way..
Since you are already on 11.2.10.10, I'd unlock the bootloader. (It'll wipe the device)
Download Oxygen Updater and download the stock versions through their.
Local update through your phone settings.
Once you are on A12 I'd follow the steps to installing Nameless.
My phone model is 2127 and I'm running Pixel Experience with no issues.
Click to expand...
Click to collapse
Oxygen Updater shows C.47 is available, should I install it?
Yes, download it and local update through the phone settings.
Keep in mind you will need to unlock your bootloader in order to flash a custom Rom.
luckylui said:
Yes, download it and local update through the phone settings.
Keep in mind you will need to unlock your bootloader in order to flash a custom Rom.
Click to expand...
Click to collapse
Well it didn't work, local update wouldn't allow me to install it.
skrubxgt said:
Well it didn't work, local update wouldn't allow me to install it.
Click to expand...
Click to collapse
I wonder if you need to unlock the bootloader and root? I can't test it out unfortunately since I'm on the Pixel Rom :/
luckylui said:
I wonder if you need to unlock the bootloader and root? I can't test it out unfortunately since I'm on the Pixel Rom :/
Click to expand...
Click to collapse
I wonder why I can't install official update, when I installed C.47 it just bootloops. Tried installing Global, India and EU builds but after all it is the same situation.
skrubxgt said:
I wonder why I can't install official update, when I installed C.47 it just bootloops. Tried installing Global, India and EU builds but after all it is the same situation.
Click to expand...
Click to collapse
Yeah, that is very weird.
I wonder if something with your phones partitions got messed up, but I would figure doing an MSM restoration would bring everything back.
luckylui said:
Yeah, that is very weird.
I wonder if something with your phones partitions got messed up, but I would figure doing an MSM restoration would bring everything back.
Click to expand...
Click to collapse
Tried restoring it using MsmTool, still nothing
I have exactly the same problem, except my device is a LE2123. Running the stock version that came out of the box. 11.2.10.10.LE15BA. down load and install seem to be ok, but at the point to reboot the device loop several times and then recovers to 11.2.10.10....
If you guys are going custom Rom, I would just go ahead and install the custom Rom. Looks like the firmware will carry over once you transition. Maybe that'll work out better than updating to the next available stock firmware.
luckylui said:
If you guys are going custom Rom, I would just go ahead and install the custom Rom. Looks like the firmware will carry over once you transition. Maybe that'll work out better than updating to the next available stock firmware.
Click to expand...
Click to collapse
Yea, if you want a custom ROM, just do it and follow the instructions to the letter....
TheGhost1951 said:
Yea, if you want a custom ROM, just do it and follow the instructions to the letter....
Click to expand...
Click to collapse
I have the 2127 Tmo model and was on C.19 version. Downloaded and installed Pixel Experience Rom which is C.62 and it works fine. But, I have heard C.19 is pretty much C.62 and Pixel Rom you can install it on any version.. not sure about Nameless though. Worst case scenario is you would have to MSM back (which I know is a pain) but, I guess gotta try whatever works.
luckylui said:
I have the 2127 Tmo model and was on C.19 version. Downloaded and installed Pixel Experience Rom which is C.62 and it works fine. But, I have heard C.19 is pretty much C.62 and Pixel Rom you can install it on any version.. not sure about Nameless though. Worst case scenario is you would have to MSM back (which I know is a pain) but, I guess gotta try whatever works.
Click to expand...
Click to collapse
Hi my friend, I am on TMO with Model LE2127 running stock 11.2.9.9 and happy as a Lark. I got rid of bloatware, full root with partitions mounted as R/W, custom bootanimation and custom systemwide font. With just Magisk Root, you are not fully rooted. And stock OOS 12 is squirrelly anyway. The latest is not always the greatest.....hope you are having a great day! TheGhost!
To me, the main reason for root on any smartphone is to be able to customize it anyway you like without having to go and find this module or that module for Magisk. I tried the custom font module for Magisk and it was not systemwide. The way I am rooted, even the keys on the keyboard are changed to the custom font I have installed....if you don't have complete control of your phone, you are not truly rooted!
TheGhost1951 said:
Hi my friend, I am on TMO with Model LE2127 running stock 11.2.9.9 and happy as a Lark. I got rid of bloatware, full root with partitions mounted as R/W, custom bootanimation and custom systemwide font. With just Magisk Root, you are not fully rooted. And stock OOS 12 is squirrelly anyway. The latest is not always the greatest.....hope you are having a great day! TheGhost!
Click to expand...
Click to collapse
Hello, TheGhost! Glad to see an old timer on the forums from many moons ago! We've seen it all and still learning till this day as technology develops. Totally agree with ya and it sure does make a difference once you take full control of your phone. That's why Android will always be my go to! Cheers to ya!!
luckylui said:
Hello, TheGhost! Glad to see an old timer on the forums from many moons ago! We've seen it all and still learning till this day as technology develops. Totally agree with ya and it sure does make a difference once you take full control of your phone. That's why Android will always be my go to! Cheers to ya!!
Click to expand...
Click to collapse
You bet my friend,
I had a similar problem on my 9 with the C.48 ROM. I ended up MSM back to stock, unlocked the bootloader, then took the OTAs and it downloaded the full ones. All those flashed fine, then it got stuck at C.60 and said I was up to date so I had to grab the C.62 full India OTA and flashed that and now I'm back up to date.
I'm assuming based on the version and model that you're running the EU ROM? If so, grab Oxygen Updater and download the full OTA of C.62 from it (turn on advanced setting so you can select incompatible images, select EU full). Take that and copy to PC. Download Fastboot Enhance, reboot to fastbootd (adb reboot fastboot). Double click when it shows your device, go to partitions page. Search cow and select and delete each one you find there individually (you just keep searching cow after you delete each one, no idea why the program wasn't designed to just let you select all of them at once and delete them, maybe it's a safety design for dumb people). Then click flash payload.bin and choose the C.62 zip file you downloaded and it will flash to your phone. Reboot to system and you should be good to go.
Fastboot Enhance doesn't have all the checks that the regular updater does so as long as it's a full OTA and it's not corrupted, it should flash fine.
If you screw anything up, it's time to MSM again. Annoying but that's how it goes with these frustrating OnePlus devices.
I have a Moto G30 (bought in Australia) that I'd like to downgrade from Android 12 to Android 11. I've tried using the LMSA tool, but that just reflashes on Android 12. I'm following the tutorial here: https://www.droidwin.com/downgrade-motorola-moto-g30-from-android-12-to-android-11/
When I come to download the ROM, I'm not sure which one I want. From the list (https://mirrors.lolinet.com/firmware/motorola/caprip/official/RETAPAC/) I know it will be one with XT2129-2 as that's my phone model, and it will have 11 in it rather than 12 for the Android version. But that still leaves 4 choices:
XT2129-2_CAPRIP_RETAPAC_JPTW_11_RRCS31.Q1-3-68-1-3_subsidy-DEFAULT_regulatory-XT2129-2-APEM2_CFC.xml.zip
XT2129-2_CAPRIP_RETAPAC_SA_11_RRCS31.Q1-3-68-4_subsidy-DEFAULT_regulatory-XT2129-2-APEM-SAR_CFC.xml.zip
XT2129-2_CAPRIP_RETAPAC_TH_11_RRCS31.Q1-3-68-4_subsidy-DEFAULT_regulatory-XT2129-2-APEM_CFC.xml.zip
XT2129-2_CAPRIP_RETAPAC_TW_11_RRCS31.Q1-3-68-4_subsidy-DEFAULT_regulatory-XT2129-2-APEM2_CFC.xml.zip
Any ideas which I should pick? Or what the difference is between these?
just different updates, all the ones before S0RC or so, should be 11, all the RRCS ones are android 11 for sure, I'd pick the latest one of those, which would have the latest security patches
also, even for normal updates, I've only used LMSA to download the latest image, and then manually flashed it, I'm pretty sure LMSA will only download the latest version anyway, so unless you figure out how to manually override it, it won't downgrade
Thanks. Have managed to get the phone up and running with XT2129-2_CAPRIP_RETAPAC_SA_11_RRCS31.Q1-3-68-4_subsidy-DEFAULT_regulatory-XT2129-2-APEM-SAR_CFC.
The only issue I face now is that Google Pay no longer works.. Although my phone isn't rooted, the bootloader was unlocked during the process of going back to Android 11. Is there a way I can get Google Pay back whilst staying on Android 11?