Develop Bugs

[LWX49K&LDZ22D&LCA43] Rooting made easy

I'm not believing my eyes just yet, but honestly...
Want root? Well, then I have some good news for you:
THERE IS NO REASON TO UNLOCK YOUR BOOTLOADER TO ROOT YOUR SMARTWATCH 3!
The fastboot mode is available on locked bootloader...
And the best news I can come up with right now? It allows hot booting custom kernels! :victory:
Code:
~$ adb reboot bootloader
~$ fastboot oem unlock
...
(bootloader) : WARNING: Unlocking your device will void your warranty
(bootloader) : and erase your personal data from the device.
(bootloader) : Run "fastboot oem unlock" again to confirm.
(bootloader) : Device still locked.
OKAY [ 0.008s]
finished. total time: 0.008s
~$ fastboot reboot
rebooting...
finished. total time: 0.001s
~$ adb shell
[email protected]:/ $ su
[email protected]:/ #
I can't believe it myself, but it's TRUE! :victory:
I have rooted my device using the TWRP from this thread, this is what I did:
Made sure I had the developer options enabled;
Enabled the ADB debugging option;
Made sure the device accepted my PC as authorized;
download the TWRP image from this thread (for 5.0.2) or from this post (for 5.1.1);
Download Wear-SuperSU-v2.46.zip;
adb reboot bootloader, saw it actually boot to fastboot... this is how I looked at that time: http://images.sodahead.com/polls/001047815/gobsmacked-15792349304_xlarge.jpeg;
fastboot boot unofficial-twrp-2.8.3.0-tetra.img (incredibly I saw it boot TWRP! Well... this is like the face my colleagues where watching me pull at that moment: http://mcp53.files.wordpress.com/2012/11/gobsmacked.jpg?w=500);
adb push Wear-SuperSU-v2.46.zip /sdcard/ (installed the zip in recovery);
Reboot to system from TWRP;
Did root test;
Was seriously gobsmacked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm investigating the possibility to have recovery on the locked device right now, which is actually something I did for many Xperia Z series devices already :angel:

What can we make of new after this?

Elpatii said:
What can we make of new after this?
Click to expand...
Click to collapse
Well, the good thing is, you can have root while you won't lose your warranty. Because unlocking bootloader === lost warranty.
What else we can do, the sky is basically the limit... or, the resolution is, of course

[NUT] said:
Well, the good thing is, you can have root while you won't lose your warranty. Because unlocking bootloader === lost warranty.
What else we can do, the sky is basically the limit... or, the resolution is, of course
Click to expand...
Click to collapse
Oh nice!
And with root in this Smartwatch, what do you think that we can make of more?

Elpatii said:
Oh nice!
And with root in this Smartwatch, what do you think that we can make of more?
Click to expand...
Click to collapse
Well, one of the things we might be able to do is create an app or a ROM modification, which will run on the phone smartwatch itself, allowing you access to the internal storage by USB cable, because that's not possible without a phone right now. Knowing Google, it was done by design, but it won't be hard to update the ROM to allow access to the internal storage through USB.
I'll be trying to get a recovery working on the device without overwriting the one in the recovery partition, which should then allow us to easily flash ROM modifications.

[NUT] said:
Well, one of the things we might be able to do is create an app or a ROM modification, which will run on the phone smartwatch itself, allowing you access to the internal storage by USB cable, because that's not possible without a phone right now. Knowing Google, it was done by design, but it won't be hard to update the ROM to allow access to the internal storage through USB.
I'll be trying to get a recovery working on the device without overwriting the one in the recovery partition, which should then allow us to easily flash ROM modifications.
Click to expand...
Click to collapse
Oh yeah, it's would be nice!
Continue to share your discovery

[NUT] said:
Well, the good thing is, you can have root while you won't lose your warranty. Because unlocking bootloader === lost warranty.
What else we can do, the sky is basically the limit... or, the resolution is, of course [emoji14]
Click to expand...
Click to collapse
Dude Great to see you here, i am very excited now as our SW3 will go in right direction, i have Asked Jerpelea about the Development of SW3 and he said it will start soon.
Also its a request Plz make a custom Kernel for this watch to Calibrate the Colors saturation and Gamma as its same yellowish Display as Honami had.

abbychauhan said:
Dude Great to see you here, i am very excited now as our SW3 will go in right direction, i have Asked Jerpelea about the Development of SW3 and he said it will start soon.
Also its a request Plz make a custom Kernel for this watch to Calibrate the Colors saturation and Gamma as its same yellowish Display as Honami had.
Click to expand...
Click to collapse
+1
Sent from my Xperia Z3

Is there a way to unlock the kernel and all four cores in the processor on latest LDZ22D build for Smartwatch 3?

[NUT] said:
I'm not believing my eyes just yet, but honestly...
Click to expand...
Click to collapse
Thanks for sharing your discovery!
I wrote an article that explores the bootloader vulnerability: http://spectrastudy.com/no-data-protection-on-sony-smartwatch-3-android-wear/
An Android Wear dev advocate at Google is now informed of it, it really should be fixed as it makes stealing data far too easy.

[NUT] said:
I'm not believing my eyes just yet, but honestly...
Want root? Well, then I have some good news for you:
THERE IS NO REASON TO UNLOCK YOUR BOOTLOADER TO ROOT YOUR SMARTWATCH 3!
The fastboot mode is available on locked bootloader...
And the best news I can come up with right now? It allows hot booting custom kernels! :victory:
Click to expand...
Click to collapse
Hi ive been trying to work this out above you said that there is away to root the watch on locked bootloader could you explain how? I can get into fastboot but theres no way to install TWRP on locked bootloader how would I flash the superuser zip on locked bootloader. Can it be done? Your method you explained is an unlocked bootloader method and with the stock recovery you can only sideload update.zips correct me if im wrong. Can you please explain the locked bootloader method??? Can it not be done on the latest build LCA43???

RJASSI21 said:
Hi ive been trying to work this out above you said that there is away to root the watch on locked bootloader could you explain how? I can get into fastboot but theres no way to install TWRP on locked bootloader how would I flash the superuser zip on locked bootloader. Can it be done? Your method you explained is an unlocked bootloader method and with the stock recovery you can only sideload update.zips correct me if im wrong. Can you please explain the locked bootloader method??? Can it not be done on the latest build LCA43???
Click to expand...
Click to collapse
fastbooting hotboot only. no flashing of custom recovery. only flash wear supersu after hotbooting.
˜xperia z3,d6653,5.1.1,v71,tapatalk

jemfalor said:
fastbooting hotboot only. no flashing of custom recovery. only flash wear supersu after hotbooting.
˜xperia z3,d6653,5.1.1,v71,tapatalk
Click to expand...
Click to collapse
Ok thanks for that
---------- Post added at 03:00 AM ---------- Previous post was at 02:28 AM ----------
jemfalor said:
fastbooting hotboot only. no flashing of custom recovery. only flash wear supersu after hotbooting.
˜xperia z3,d6653,5.1.1,v71,tapatalk
Click to expand...
Click to collapse
Just one other thing how can I check I have successfully rooted my device?

sideload an app and use its root feature. es explorer or terminal emulator
˜xperia z3,d6653,5.1.1,v71,tapatalk

RJASSI21 said:
Ok thanks for that
---------- Post added at 03:00 AM ---------- Previous post was at 02:28 AM ----------
Just one other thing how can I check I have successfully rooted my device?
Click to expand...
Click to collapse
jemfalor said:
sideload an app and use its root feature. es explorer or terminal emulator
˜xperia z3,d6653,5.1.1,v71,tapatalk
Click to expand...
Click to collapse
Or use ADB Shell to use the su command to gain root access.

[NUT] said:
Or use ADB Shell to use the su command to gain root access.
Click to expand...
Click to collapse
Ok thank you both the root features in es are very limited so its hard to tell I will try the su command later on thanks for that NUT
Edit: I did try TWRP on the latest firmware in the end LCA43 and it was successful im still yet to see if root was successful I dont have a superuser app is this normal?

This all works on the latest Android Wear build as well

RJASSI21 said:
Ok thank you both the root features in es are very limited so its hard to tell I will try the su command later on thanks for that NUT
Edit: I did try TWRP on the latest firmware in the end LCA43 and it was successful im still yet to see if root was successful I dont have a superuser app is this normal?
Click to expand...
Click to collapse
Yes, there is no app for wear (yet).

karl0ss said:
This all works on the latest Android Wear build as well
Click to expand...
Click to collapse
I will update the OP and subject after I confirmed it myself...

[NUT] said:
Or use ADB Shell to use the su command to gain root access.
Click to expand...
Click to collapse
Hi I dont think my smartwatch is rooted I ran the command but it just prints nothing I also tried system app mover app but it just keeps showing the looking for root message I cant grant root how do I do this I flashed the zip 4 times and moved it over twice what am I doing wrong?

[TOOL] WinDroid Toolkit | Unlock | Root | Flash | Install | Moto X Play

Link To Main Thread
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About
The WinDroid Toolkit is a Windows program built in Visual Studio using the C# programming language that simplifies the rooting process for many Android devices. The toolkit makes it easy to unlock your bootloader, flash a custom recovery and gain permanent root. It also includes other functions such as flashing kernels, pushing files and installing apps. If you find it helpful, give me a thanks and a donation if you can. If you find a bug or have a feature request, feel free to leave a reply. Thanks!
Download
WinDroid Toolkit
Changelog
Check out this document for current and past changelogs.
Supported Devices
Check out this spreadsheet for a list of currently supported devices.
Device not supported? Make a request here!
Contribute
Check out the source code on GitHub here.
Disclaimers
Please do not post, mirror, or take credit for this toolkit or any related work without explicit permission.
I am in no way responsible for any harm, damage, nuclear fission or bee infestation that may occur to your device through the use of this toolkit.

Reserved
Reserved.

WOW! That's just awesome!
Certainly I'll use this when my X Play arrives

Did anyone try this nifty tool yet? Looks promising!

that looks amazing, can anyone confirm it's working? I'm getting the XT1563 version soon

working flawlessly. thanks

Seems really promising! I am having a slight issue however.
After unlucking the bootloader succesfully, when i proceed to flash twrp, it says success. However, when I boot into recovery, i get the classic "Resting Android robot" saying "No Command"

SaladEsc said:
Seems really promising! I am having a slight issue however.
After unlucking the bootloader succesfully, when i proceed to flash twrp, it says success. However, when I boot into recovery, i get the classic "Resting Android robot" saying "No Command"
Click to expand...
Click to collapse
its because of the install-recovery.sh in system/etc folder

AnoopKumar said:
its because of the install-recovery.sh in system/etc folder
Click to expand...
Click to collapse
so you are suggesting to delete that file?
if so how can i becuase i have no root access

droider007 said:
so you are suggesting to delete that file?
if so how can i becuase i have no root access
Click to expand...
Click to collapse
after installing custom recovery using tool-kit and directly reboot to recovery from fastboot menu, then mount system and rename the install-recovery.sh :good:

Awesome tool. I just have one question. Is it possible to relock the bootloader without losing root? I unlocked bootloader manually, I boot twrp (not flashed, just boot) and installed SuperSU. So I still have the stock recovery, but I'd like to relock the bootloader without having to lose root.

ToYeD said:
Awesome tool. I just have one question. Is it possible to relock the bootloader without losing root? I unlocked bootloader manually, I boot twrp (not flashed, just boot) and installed SuperSU. So I still have the stock recovery, but I'd like to relock the bootloader without having to lose root.
Click to expand...
Click to collapse
Hallo , here is a Link with a Tut how to Unroot the Moto X Play.
My phone is hast not arrived yet. Can´t confirm the procedure. :silly:
Greeting... Kaz

i installed this program but when i reboot to recovery mod there`s "no command" (i followed the steps)

Serial Kazama said:
Hallo , here is a Link with a Tut how to Unroot the Moto X Play.
My phone is hast not arrived yet. Can´t confirm the procedure. :silly:
Greeting... Kaz
Click to expand...
Click to collapse
I want to relock the bootloader but keep root. I don't want to lose root or busybox as I need them for several functions. I just want to get rid of the annoying warning on boot that says I have an unlocked bootloader.

ToYeD said:
I want to relock the bootloader but keep root. I don't want to lose root or busybox as I need them for several functions. I just want to get rid of the annoying warning on boot that says I have an unlocked bootloader.
Click to expand...
Click to collapse
Then flash a different logo.bin
Sent from my XT1562 using XDA Free mobile app

rober788 said:
i installed this program but when i reboot to recovery mod there`s "no command" (i followed the steps)
Click to expand...
Click to collapse
That means you're still on stock recovery..

After rooting my moto battery life has benn reduced. Anyone has this problem too?

Hi guys! Just receive my new moto x play today and want to root it! Its good to go with this tool?!
Envoyé de mon Nexus 5 en utilisant Tapatalk

I've used the tool to unlock the bootloader and flash TWRP. Worked smooth and didn't really have any issues. I did had to flash TWRP twice, but that might have been an error on my part for not looking at my phone after the first flash attempt. SU installed via on screen notifications after booting into recovery, worked like a charm too.
I recommend this tool as it takes away a load of work, especially with the bootloader unlock.

When trying to boot in recovery i got "No Command" while the device is unlocked and i tried to flash new recovery...
EDIT:
You must enable "OEM unlock" after the reboot

How To Guide Tmo-eu (global) the way I did it.

Ok this procedure is the way I did it and I have tested it over and over still working to unbrick and even brick your phone. So please use at your own caution I am no way gonna be held responsible for anyone bricked phone. And your data will be formatted erase poof gone if you don't back it up. And I encourage y'all to read Craznazn post.
How To: Unlock the T-Mobile Bootloader
Hello all, this is a quick and simple guide to unlocking your T-Mobile locked bootloader. Just a reminder: unlocking the bootloader will wipe your data. The instructions here will apply to all T-Mobile OnePlus devices. Unlock your SIM. Some...
forum.xda-developers.com
Actually he has several post I used like this one too steps with oneplus 8t works on 9 pro too.
[GUIDE] Convert TMO to EU via MSM Tool, no SIM Unlock or Bootloader Unlock needed!
*** Use this at your very own risk. *** You will lose all data *** Backup your working modem and persist, just in case *** Read the entire post and follow the steps closely before asking for help. Post all error messages and steps you took...
forum.xda-developers.com
Big thanks to him for finding out bout the most important part the modem....
Here we go... I am assuming y'all know adb and fastboot so leaving that out. But make sure you have latest oneplus drivers and adb cause fastbootd has to be used when flashing.
First read Craznazn post on unlocking bootloader. And he has a t-mobile magisk patched link you can use to flash read his post. After your backed up unlocked and rooted. Get this app from play store.
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com
I went ahead and checked everyone of the blocks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
looks like this. Now this is gonna take a a min like 45-1 hour this is your phones active firmware. Mine ended up being 26gb. . While that's going go ahead and and get eu or global your gonna use from xda post or oneplus site full version only. I did global first could not update so I went ahead and did the eu ba 11.2.3.3 (updated one) everything is same works great.
After download use the payload extractor I hope y'all know how and what that is if not please stop and research. Label that folder after it's done global(eu) so I won't get confused. (Go ahead and patch the boot image if u want root);
Now on your phone find the zip file partition backup made for ya. Transfer it to pc. Extract it. Your gonna see some .img and .gz. it's gonna look like
( On the .img file I went ahead and erased the 2021-04-15 part)
Then I but both roms side by side and this is very important what I did was took the boot.img and renamed it to orginaleu/globalboot.img from the global/eu folder and placed renamed the magisk patched to boot.imgand place in the global folder.
IMPORTANT IF YOU WANT DATA TO WORK AT ALL. TAKE YOUR MODEM AND MODEMST1 AND MODEMST2 FILE OUT OF YOUR TMOBILE FIRMWARE FOLDER COPY THEM TO THE GLOBAL/EU FOLDER IF NOT YOUR NOT GONNA HAVE NO DATA NO SERVICE AT ALL. AND TAKE THE CARRIER.IMG FILE FROM TMOBILE FOLDER AND COPY IT OVER TOO.
I made this flashall.bat it worked just fine. I might have left out a few partitions but it is all good. Now on pc open a blank text document and copy and paste the change2 flashall.bat.txt and save as flashall.bat. put one in each folder and there conversation folder in one and the recovery folder in the t-mobile firmware folder. To flash just adb reboot bootloader then fastboot reboot fastboot. Make sure your in fastbootd. Screen will look like the recovery screen but it will say fastbootd. Once there click on the flashall.bat and let it do it thing. It may take like 5 mins to boot. Now if it stuck on the oneplus boot animation. Go back to. Fastboot and -- set-active =a or b. And if your rom acts little jumpy or crazy go back and check the boot.img u flashed might hot them mixed up.
My first guide maybe this will help you til the msmtool is ready. I know it get frustrating sometimes that's why I tried to describe much as I can

Anyone happen to have a back up of the stock Tmo firmware? I managed to get everything installed, but borked the mobile network after trying to OTA and preserve magisk. Restoring my backup partitions did nothing.

Just restore your tmo modem

craznazn said:
Just restore your tmo modem
Click to expand...
Click to collapse
I did that, no luck.
Edit: My bad. Had to flash through fastbootd. Thought the Partitions Backup app would restore them. It doesnt

So do you still get 5g on T-Mobile network after flashing the modems

Persianhawkes said:
So do you still get 5g on T-Mobile network after flashing the modems
Click to expand...
Click to collapse
Can confirm 5G on TMO after flashing the modems.

Deleted

No, I'm gonna support @amaroney55 on this guide. If you can't follow the guide or don't have the time to follow the guide, then you won't be able to troubleshoot it or have the time to troubleshoot it when something breaks. This is not a straightforward conversion and you may very well hard brick.

So I just got the 11.2.4.4ba update from the real system updated. It did everything it was supposed even magisk into other slot rebooted. Ok after reboot you will not have service you will have to flash tmo- modem.img to modem_a and _b. And flash the MODEMST1 and MODEMST2. Then you will have service again

amaroney55 said:
So I just got the 11.2.4.4ba update from the real system updated. It did everything it was supposed even magisk into other slot rebooted. Ok after reboot you will not have service you will have to flash tmo- modem.img to modem_a and _b. And flash the MODEMST1 and MODEMST2. Then you will have service again
Click to expand...
Click to collapse
Should only need to flash modem to the active slot, and shouldn't need to flash modemsts, those are not touched even by MSM

This is the thread about converting from tmo-global(eu). I flashed the modems only and still didn't have service. I had to flash all 4

Does this conversion enable dual SIM?

signal34 said:
Does this conversion enable dual SIM?
Click to expand...
Click to collapse
Idk let me check really fast. Nope still single.

Tbh. I don't use my camera like that. I use it everyday just for proof of delivery. But I don't really pay attention. But I do has the riru magisk installed with LS mod it has the every feature enabler for OnePlus cameras on it.

Very nice guide and there is only one thing I want to point out is there is A typo in your script (I guess)
you have 2 "fastboot flash system_ext_a system_ext.img" which I think one of them should be
"fastboot flash system_ext_b system_ext.img".
Took me a while to figure out, I got boot loop and bunches of errors like "Not enough space to resize partition" if I don't change it, after changing, everything back to normal.
Thanks again for this helpful guide!

I really want to do this but im very hesitant without a true recovery.

Ultraman666 said:
I really want to do this but im very hesitant without a true recovery.
Click to expand...
Click to collapse
We have a true recovery. All phones do.

im talking about twrp

TWRP is worthless for this kind of procedure and there's not a sufficiently working TWRP build for Android 11.
You want an MSM unbrick tool, not TWRP.

You are half right with the MSM unbrick tool, Twrp would still be helpful as you stated there isnt any so we will have to wait on both

Question Downgrade to Android 12

I'm having issues trying to downgrade to Andriod 12 from andriod 13 beta 3.
1. I've opted out of Beta
2. Software update notification received
3. Click on download and install
4. After a couple of mins get error message couldn't update 'Installation problem'
The screen remains on the update screen.
What am i doing wrong please help?
Device state: locked
edit:actually now I'm stuck in Fastboot Mode
Phone keeps rebooting back to Fastboot mode

With a locked bootloader, your only option to get fixed is to try sideloading an OTA - usually, the OTA has to be either the same as what you were most recently running or newer. Click the yellow How To Guide quick filter at the top of the list of threads for one of the root guides. Even though you're not rooting, one or two of them should tell how to sideload an OTA - just ignore things that reference root.
This is why the instructions for the Beta program say you should have an unlocked bootloader, as without an unlocked bootloader your choices to fix the situation are much more limited.

roirraW edor ehT said:
With a locked bootloader, your only option to get fixed is to try sideloading an OTA - usually, the OTA has to be either the same as what you were most recently running or newer. Click the yellow How To Guide quick filter at the top of the list of threads for one of the root guides. Even though you're not rooting, one or two of them should tell how to sideload an OTA - just ignore things that reference root.
This is why the instructions for the Beta program say you should have an unlocked bootloader, as without an unlocked bootloader your choices to fix the situation are much more limited.
Click to expand...
Click to collapse
thanks for that, any advice on how to ota pls?
Can't find any instructions sorry.

riz157 said:
thanks for that, any advice on how to ota pls?
Click to expand...
Click to collapse
You're welcome. Since I never do the OTA process, I always flash the full firmware zip (which you can't do with a locked bootloader), I can't advise any further than what I said about using the quick filter for the How To Guides. At least one or two of these threads should help you, although they may concentrate on doing so with rooting, as long as you ignore the root parts to the OTA method, you can still follow the instructions. You'll get better help to any questions in one of the threads that give OTA sideload instructions:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

roirraW edor ehT said:
Yo
You're welcome. Since I never do the OTA process, I always flash the full firmware zip (which you can't do with a locked bootloader), I can't advise any further than what I said about using the quick filter for the How To Guides. At least one or two of these threads should help you, although they may concentrate on doing so with rooting, as long as you ignore the root parts to the OTA method, you can still follow the instructions. You'll get better help to any questions in one of the threads that give OTA sideload instructions:
View attachment 5642011
Click to expand...
Click to collapse
much appreciated yes want to avoid root or unlocking the bootloader, why does google have it to make it so difficult to downgrade. Maybe take a leaf out of apple's book

To sideload you need USB debugging enabled. Reboot the device to recovery, either by powering off the device and holding power and volume up, let go of power when the phone vibrates, on the the android with an exclamation mark, tap on volume up I think it is. Or by typing in terminal
Code:
fastboot reboot recovery
since it's stuck in fastboot. In recovery tap on 'apply update from adb'
Then download the ota package from here.
Grab the platform tools (Google for it) and unzip it to c:\platform-tools if you're running windows. Open a terminal in the platform tools folder and type
Code:
adb sideload /path_to_ota.zip
Let it do its thing and you should be up and running. I wouldn't try to downgrade from the a13 beta, but you can try. Good luck!

riz157 said:
thanks for that, any advice on how to ota pls?
Can't find any instructions sorry.
Click to expand...
Click to collapse
Just a few things. You don't need USB debugging enabled for OTA updates (you can't boot into Android to enable it anyway).
Just be aware that with OTA's, you can't downgrade - only reinstall the same version or upgrade, so you need to make sure you're on Android 13 to reinstall ota version 13 (recovery mode will tell you your version).
Here's a video to help with the ota update.

riz157 said:
I'm having issues trying to downgrade to Andriod 12 from andriod 13 beta 3.
1. I've opted out of Beta
2. Software update notification received
3. Click on download and install
4. After a couple of mins get error message couldn't update 'Installation problem'
The screen remains on the update screen.
What am i doing wrong please help?
Device state: locked
edit:actually now I'm stuck in Fastboot Mode
Phone keeps rebooting back to Fastboot mode
Click to expand...
Click to collapse
Any luck with your device?

Alekos said:
Any luck with your device?
Click to expand...
Click to collapse
No luck finally contacted Google who will have this sorted.

riz157 said:
No luck finally contacted Google who will have this sorted.
Click to expand...
Click to collapse
What happened with the OTA updates? Did it complete? Getting the windows driver and fastboot/adb (platform-tools) to all work can be tricky..

what about the https:// flash.android .com/build/8151327?target=raven-user&signed=true Website?

jlede18 said:
what about the https:// flash.android .com/build/8151327?target=raven-user&signed=true Website?
Click to expand...
Click to collapse
Flash.android uses fastboot, which requires the bootloader to be unlocked. User can't unlock it since Android won't boot..

I don't think I'll be flashing beta version again lol, too much hassle to downgrade.
In the end decided to send in to Google to repair.
I think they will give me a replacement instead of repairing it.
Did anyone notice any major bugs with android 13, can't say I did?

Alekos said:
What happened with the OTA updates? Did it complete? Getting the windows driver and fastboot/adb (platform-tools) to all work can be tricky..
Click to expand...
Click to collapse
Decided against that, off to Google to fix

Alekos said:
Flash.android uses fastboot, which requires the bootloader to be unlocked. User can't unlock it since Android won't boot..
Click to expand...
Click to collapse
Copy that. Would of probably just been easier to reflash the beta back save everything, unlock the bootloader and then flash android 12

jlede18 said:
Copy that. Would of probably just been easier to reflash the beta back save everything, unlock the bootloader and then flash android 12
Click to expand...
Click to collapse
Yup, very easy to flash ota, but op didn't feel comfortable doing it unfortunately.

Might seem dumb but I used the web browser tool and flashed back to stock via that from 13 B3 it unlocks bootloader and flashes and re locks bootloader , back on stable 12 working fine then opted out of 13 beta

The way I did it was downloading the entire firmware from google and then changing the config to remove- w so your data doesn't get wiped. Then running the .su or .bat depending on your is. It worked for me. Cheers

Question Can't register fingerprints

After updating the requisite firmware, I performed a clean flash of the latest CRDroid build (previously I was using the March 28) build. During the initial setup, as well as after through the regular settings page, I was unable to register any of my fingerprints to the biometric unlock. In the setup screen, the UDFPS lights up when pressed (see screenshot), but no matter how long I keep my finger pressed on it the print will not register. I have rebooted, clean flashed, and dirty flashed the ROM, and the problem appears every time. I have tried installing both with and without GApps. I even tried flashing LineageOS instead of CRDroid, and I had the same issue. What steps should I be taking to troubleshoot this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Do you have the backup of persist partion?

PattasuBalu said:
Do you have the backup of persist partion?
Click to expand...
Click to collapse
No, the only backup I have of my previous install is the Swift Backup of apps and settings.

Try going to stock and check if the fingerprint is working. If its working then it may be a bug. If not then I think you have over written the persist partition.

PattasuBalu said:
Try going to stock and check if the fingerprint is working. If its working then it may be a bug. If not then I think you have over written the persist partition.
Click to expand...
Click to collapse
What's the easiest way to revert to Stock? Should I just download one of the packages in the pinned post on this forum and sideload?
And if my persist partition is corrupted, what recourse do I have?

Try MSM tool. Probably one or both slots are derped. Also maybe you use wrong base firmware for these roms

sumfahg said:
What's the easiest way to revert to Stock? Should I just download one of the packages in the pinned post on this forum and sideload?
And if my persist partition is corrupted, what recourse do I have?
Click to expand...
Click to collapse
If persist partition is corrupted you have no other choice except to give your phone to OnePlus service center as this is unique for every phone.

EugenStanis said:
Try MSM tool. Probably one or both slots are derped. Also maybe you use wrong base firmware for these roms
Click to expand...
Click to collapse
MSM Tool worked fine, but I was also unable to enroll there. Seems my only choice is to find a OP service center and get the phone sent out.

sumfahg said:
MSM Tool worked fine, but I was also unable to enroll there. Seems my only choice is to find a OP service center and get the phone sent out.
Click to expand...
Click to collapse
Just dont forget to lock your bootloader and say that the new update broke your phone. BTW dont forget to take a backup of persist.img when you flash a new rom.

Yeah I have one stored in the cloud before I ever even unlocked bl. Can't just use any model persist partition..it's particular to each device. Sending in is only option or don't use fp option.

PattasuBalu said:
If persist partition is corrupted you have no other choice except to give your phone to OnePlus service center as this is unique for every phone.
Click to expand...
Click to collapse
There's also a way to re-register it. Had this happen on my 8. Just didn't work the same since.

mattie_49 said:
Yeah I have one stored in the cloud before I ever even unlocked bl. Can't just use any model persist partition..it's particular to each device. Sending in is only option or don't use fp option.
Click to expand...
Click to collapse
How did you back it up before unlocking the bootloader? Wouldn't you need to unlock the bootloader in order to root your device to access the root directory?
Also, is there any other root directory I should back up after I get my phone back, besides persist?

sumfahg said:
How did you back it up before unlocking the bootloader? Wouldn't you need to unlock the bootloader in order to root your device to access the root directory?
Also, is there any other root directory I should back up after I get my phone back, besides persist?
Click to expand...
Click to collapse
I think he took the backup via Partitions Backupper app which was the same app I used take a backup of my persist.img. But the app requires super user access to take backup.

TheKnux said:
There's also a way to re-register it. Had this happen on my 8. Just didn't work the same since.
Click to expand...
Click to collapse
Can you please mention the steps and what are the backsides of doing this?

sumfahg said:
How did you back it up before unlocking the bootloader? Wouldn't you need to unlock the bootloader in order to root your device to access the root directory?
Also, is there any other root directory I should back up after I get my phone back, besides persist?
Click to expand...
Click to collapse
Many ways to accomplish without root. And you back up the persist partition. Not root directory. Msm Read back with F8. Then find persist and send it to the root directory of C drive with Read back feature. . Password oneplus

sumfahg said:
How did you back it up before unlocking the bootloader? Wouldn't you need to unlock the bootloader in order to root your device to access the root directory?
Also, is there any other root directory I should back up after I get my phone back, besides persist
sumfahg said:
How did you back it up before unlocking the bootloader? Wouldn't you need to unlock the bootloader in order to root your device to access the root directory?
Also, is there any other root directory I should back up after I get my phone back, besides persist?
Click to expand...
Click to collapse
Click to expand...
Click to collapse
You can backup persist and co with msm tool (read back modus)

PattasuBalu said:
Can you please mention the steps and what are the backsides of doing this?
Click to expand...
Click to collapse
Just search xda. Pretty sure it's on the OnePlus 8 or 8T forums.