Develop Bugs

Black virtual cursor bug - are you affected? (Custom Roms)

For me and some users, while typing, or even scrolling up and down, time to time we see black virtual cursor for 0.5 sec
It's show ups for me about 10-100 times a day, very annoing!
I have seen this bug on every custom roms like RR 5.8.2, lineage os 14.1, Purenexus, etc, installed by TWRP 3.1.0-1 by nijel8/3.1.0.0 official one by strix
Changing different firmwares 7.2.9-7.3.16 - not helped.
Did a clean install throuth Mi flash tool - not helped.
Any ideas, how to fix this bastard?
Could it be recovery or even hardware problem?

If it were indeed a hardware issue, wouldn't we be seeing it on stock miui as well?
I suppose we need a common denominator - something that the custom roms have, but miui doesn't.
1) could it be related to root permissions? Has it been seen on both rooted and non-rooted devices?
2) Does it depend on how the ROM is flashed?
3) Has it been seen on other xiaomi phones? I assume both hydrogen and helium are impacted

just thinking out loud, what if we disable HID client drivers or the entire mouse support in kernel?

lukacsp said:
just thinking out loud, what if we disable HID client drivers or the entire mouse support in kernel?
Click to expand...
Click to collapse
Already tried and not helping.
Let start by taking some setup info and logs, guys. Make sure you have ran phone for a while and have seen cursor appearing at least few times. Run these commands on PC with phone USB connected:
Code:
adb shell dumpsys > c:\dumpsys.txt
Code:
adb shell dmesg > c:\dmesg.txt
Code:
adb shell logcat -d > c:\logcat.txt
or run their respective equivalents on phone terminal emulator...
Zip those files and post them here.

Haha I just saw the black mouse cursor pop up for a split second on my Helium running Pure Nexus. It's really not a big deal though. I'm sure it will eventually be fixed. It only pops up for like one tenth of a second. I'ts not even annoying but kind of funny.

Never seen it on my helium , on any Rom but then again i don't really stare at the screen looking for a cursor haha
Sent from my Mi Max using Tapatalk

Happening on Hydrogen RR5.8.2 - been happening on a few builds every now & again; annoying but not a deal breaker.

never seen on NitogenOS, but I saw it last day when I was trying nijie8's lineage, scroll up/down on the settings' About phone when back from about lineage.
Helium 3G/64G.

nijel8 said:
Already tried and not helping.
Let start by taking some setup info and logs, guys. Make sure you have ran phone for a while and have seen cursor appearing at least few times. Run these commands on PC with phone USB connected:
or run their respective equivalents on phone terminal emulator...
Zip those files and post them here.
Click to expand...
Click to collapse
I decided to clean flash your latest lineage 14.1 rom build 27.03.17 via your latest twrp 3.1.0-1, with latest firmware 23.03.17, and latest pico gapps 01.04.17
magic is happen, idk how, but for 3-4 days, I didn't see this mouse cursor bug at all... only one app that I didn't install is Google app for Google now (don't think that is a reason). BTW mb last kernel setup with hot plugging small cores give us instability and bugs ?
Will check for a while and get feedback if something changes.

It's a bug reported on Lineage's Jira. Here it is https://jira.lineageos.org/plugins/servlet/mobile#issue/REGRESSION-214

nijel8 said:
Already tried and not helping.
Let start by taking some setup info and logs, guys. Make sure you have ran phone for a while and have seen cursor appearing at least few times. Run these commands on PC with phone USB connected:
or run their respective equivalents on phone terminal emulator...
Zip those files and post them here.
Click to expand...
Click to collapse
After a free week of mouse cursor bag, I decided to reboot device..
After rebooting this bug coming back in 2-3 minute... WTF )

It happens to me on Pure Nexus which leads me to believe it's not a Lineage bug.

ajsmsg78 said:
It happens to me on Pure Nexus which leads me to believe it's not a Lineage bug.
Click to expand...
Click to collapse
We should to get some logs to nigel to fix this bastard

Get notice it on NitrogenOS v20170330...

Who used Android 7.1.2, bug still there ?) For a while, im coming back to MIUI Android 7, coz of this annoying bug

Resurrection Remix 7.1.2 Helium. BLACK VIRTUAL CURSOR CONFIRMED
Lineage OS 7.1.1-7.1.2 Helium. BLACK VIRTUAL CURSOR CONFIRMED
i noticed a battery drain since i first noticed the black cursor problem.
i started to think it is a stuck background process that kills battery. ( am i being so psychopath ? )

No cursor here. RR 5.8.3 on Helium. 7.4.13 firmware.

I have not seen the cursor in the last 11 days after enabling Settings -> Accessibility -> Large mouse pointer.

No i m not infected on any rom

I also occasionally see it. I am on stable MiUi 10 stock rom, but rooted with twrp & magisk

Locked bootloader, cannot OEM Unlock or access USB Debugging

Short version of question: How can I unbrick my ONEPLUS 3 (A3000) if I cannot boot to Android and OEM Unlock AND USB Debugging both have not been enabled?
Long version: Phone was recently purchased second hand from a third-party market (Kijiji, kind of like craigslist for Canadians). Person I bought it from claimed in the ad that the device was in a bootloop and couldn't access the OS. I had in the past successfully saved a ONEPLUS 1 from bricked status, so I didn't feel a simple bootloop would pose much of an issue. That, and at the price he was selling I really couldn't turn it down.
I tried various different methods of restoring the phone's partitions, OS, and firmware to stock/custom, but had no real luck with any (I will list below what I have attempted). If there was a root cause of this, I believe it's due to the fact that some part of the phone's storage partition (boot or system if I had to guess) had become corrupted at some point. Given the volume of threads I've seen here and elsewhere online, I wouldn't rule out a bad OTA flash, but doesn't really matter. What does matter, however, is that the Android OS is inaccessible despite my best efforts, and the bootloader is set to locked and ADB Debugging remains off.
Generally speaking, is there a way to access Developer Options to correct both these issues through terminal or a tool? I'm confident that I can get my device working again if I could access this menu, but as of yet I have had no luck.
Methods used to restore/info worth mentioning
While I don't doubt their effectiveness at large, for whatever reason I have yet to find a tool/guide that yields the anticipated results upon completion. MSM Download Tool (V3 and V4) have both been downloaded, executed, and completed numerous times, but will still not boot past the loading screen upon completion.
According to Unified Android Toolkit, my device build is being detected as "OnePlus3 7.0 NRD90M" and All-in-One Toolkit is showing that Android 6.0.1 is installed.
Drivers are all installed correctly, as proven both via tools downloaded and through Windows CMD terminal (adb devices, fastboot devices, adb get-state, etc)
Stock recovery and bootloader modes can both be reached through both hardware keys and software commands. I will note that it seems to take longer than I'd expect to boot to either of these modes using hardware keys.
I have utilized multiple USB ports, Type-C cables, different OS' on two laptops (MS Windows 10 and 7, FWUL Linux). I usually have no problem with the device being detected by the system. When I have, it usually involved one pesky USB cord.
common commands used and their effects:
fastboot OEM unlock: fails, cannot be done remotely
fastboot flash x: fails, remote: flashing partitions not allowed
ADB push: fails. cannot access partition
ADB devices: device is seen by system with serial and state
fastboot devices: device is seen by system with serial
ADB sideload: varying results. Some will fail at 0% citing "total xfer: 0.00x", some will reach 47% and fail (always exactly 47% oddly). Generally if the sideload operation passes 47% it will complete.
fastboot format/erase x: fails, partition formatting/erasing not allowed
fastboot continue: executes, but does not help with android bootloop issue as I had hoped
While I searched for an answer online, I did come across an infosec whitepaper regarding ONEPLUS 3 vulnerabilities, though it was over a year old. To my surprise, the command they had been entering works on my device, but I'm not sure how to properly use it effectively. The command used was fastboot OEM boot_mode [rf/wlan/ftm/normal]. Now, I was unable to determine what each of the triggers does, but what I did discover is that with boot_mode set to rf, my device would display chinese/korean lettering in lieu of the usual ONEPLUS logo with "powered by Android" below. This is also how I managed to have my device show up in CMD terminal for ADB commands to be issued. To the best of my knowledge though, there doesn't seem to be much point to it as I couldn't push/pull any files. Does anybody know where I could find more info on this command, as I'd like to know what the other triggers accomplish.
I've just about exhausted every available resource looking for an answer, but im still coming up short. I've gone as far as contacting ONEPLUS directly, but without proof of purchase they can't (more accurately won't) help me. And while it's not a business practice I would personally support, I can understand why they have it implemented. I've contacted a few phone shops in the area, but none have been able to assist me further than I've already gotten in this process.
I apologize again for creating a new thread about this, but I felt my circumstances warranted a new thread due to the bulk of the others having either an unlocked bootloader or TWRP installed, neither of which I do.
So, can anybody offer their help or suggest something I haven't already tried? Or should I be on EBAY looking for motherboards? Thanks in advance.

Calgary84 said:
Short version of question: How can I unbrick my ONEPLUS 3 (A3000) if I cannot boot to Android and OEM Unlock AND USB Debugging both have not been enabled?
Long version: Phone was recently purchased second hand from a third-party market (Kijiji, kind of like craigslist for Canadians). Person I bought it from claimed in the ad that the device was in a bootloop and couldn't access the OS. I had in the past successfully saved a ONEPLUS 1 from bricked status, so I didn't feel a simple bootloop would pose much of an issue. That, and at the price he was selling I really couldn't turn it down.
I tried various different methods of restoring the phone's partitions, OS, and firmware to stock/custom, but had no real luck with any (I will list below what I have attempted). If there was a root cause of this, I believe it's due to the fact that some part of the phone's storage partition (boot or system if I had to guess) had become corrupted at some point. Given the volume of threads I've seen here and elsewhere online, I wouldn't rule out a bad OTA flash, but doesn't really matter. What does matter, however, is that the Android OS is inaccessible despite my best efforts, and the bootloader is set to locked and ADB Debugging remains off.
Generally speaking, is there a way to access Developer Options to correct both these issues through terminal or a tool? I'm confident that I can get my device working again if I could access this menu, but as of yet I have had no luck.
Methods used to restore/info worth mentioning
While I don't doubt their effectiveness at large, for whatever reason I have yet to find a tool/guide that yields the anticipated results upon completion. MSM Download Tool (V3 and V4) have both been downloaded, executed, and completed numerous times, but will still not boot past the loading screen upon completion.
According to Unified Android Toolkit, my device build is being detected as "OnePlus3 7.0 NRD90M" and All-in-One Toolkit is showing that Android 6.0.1 is installed.
Drivers are all installed correctly, as proven both via tools downloaded and through Windows CMD terminal (adb devices, fastboot devices, adb get-state, etc)
Stock recovery and bootloader modes can both be reached through both hardware keys and software commands. I will note that it seems to take longer than I'd expect to boot to either of these modes using hardware keys.
I have utilized multiple USB ports, Type-C cables, different OS' on two laptops (MS Windows 10 and 7, FWUL Linux). I usually have no problem with the device being detected by the system. When I have, it usually involved one pesky USB cord.
common commands used and their effects:
fastboot OEM unlock: fails, cannot be done remotely
fastboot flash x: fails, remote: flashing partitions not allowed
ADB push: fails. cannot access partition
ADB devices: device is seen by system with serial and state
fastboot devices: device is seen by system with serial
ADB sideload: varying results. Some will fail at 0% citing "total xfer: 0.00x", some will reach 47% and fail (always exactly 47% oddly). Generally if the sideload operation passes 47% it will complete.
fastboot format/erase x: fails, partition formatting/erasing not allowed
fastboot continue: executes, but does not help with android bootloop issue as I had hoped
While I searched for an answer online, I did come across an infosec whitepaper regarding ONEPLUS 3 vulnerabilities, though it was over a year old. To my surprise, the command they had been entering works on my device, but I'm not sure how to properly use it effectively. The command used was fastboot OEM boot_mode [rf/wlan/ftm/normal]. Now, I was unable to determine what each of the triggers does, but what I did discover is that with boot_mode set to rf, my device would display chinese/korean lettering in lieu of the usual ONEPLUS logo with "powered by Android" below. This is also how I managed to have my device show up in CMD terminal for ADB commands to be issued. To the best of my knowledge though, there doesn't seem to be much point to it as I couldn't push/pull any files. Does anybody know where I could find more info on this command, as I'd like to know what the other triggers accomplish.
I've just about exhausted every available resource looking for an answer, but im still coming up short. I've gone as far as contacting ONEPLUS directly, but without proof of purchase they can't (more accurately won't) help me. And while it's not a business practice I would personally support, I can understand why they have it implemented. I've contacted a few phone shops in the area, but none have been able to assist me further than I've already gotten in this process.
I apologize again for creating a new thread about this, but I felt my circumstances warranted a new thread due to the bulk of the others having either an unlocked bootloader or TWRP installed, neither of which I do.
So, can anybody offer their help or suggest something I haven't already tried? Or should I be on EBAY looking for motherboards? Thanks in advance.
Click to expand...
Click to collapse
Thanks for the exhaustive description. You seem to have covered every known method. If the MSM Tool also fails, I think that it is a hardware issue and you are better off searching for a new motherboard instead of wasting further time on trouble-shooting.
Best of luck!

tnsmani said:
Thanks for the exhaustive description. You seem to have covered every known method. If the MSM Tool also fails, I think that it is a hardware issue and you are better off searching for a new motherboard instead of wasting further time on trouble-shooting.
Best of luck!
Click to expand...
Click to collapse
I was afraid of that..... is there a way to test a given hardware component?

Have you tried the unbrick tool FULL updated: https://mega.nz/#!NmhhgZyB!CM7Fw8VjECiMIhh4gRXUx24QVCiE599_ZFAPDf08AiM

acetone802000 said:
Have you tried the unbrick tool FULL updated: https://mega.nz/#!NmhhgZyB!CM7Fw8VjECiMIhh4gRXUx24QVCiE599_ZFAPDf08AiM
Click to expand...
Click to collapse
Indeed I have, dozens of times between the full and mini versions. I've even gone as far as running the toolkits featuring MSMDownloadTool v4.0 to see if it achieved different results (it did not). The mini tool would finish doing its thing (turned the text green upon completion),but I would face varying partitions not being flashed correctly. The full version completes and does not have these varying partitions missing, but the device would then be either stuck in a bootloop where it will eventually reboot itself, or would hang indefinitely on the "swirling dots" loading screen. I tried the remedy of deleting cache in recovery, but this did not help.

deleted

***UPDATE*** - As I mentioned in this thread earlier, I noticed a discrepancy between the variant type listed on my actual device and the variant type returned when queried via fastboot. This got me thinking, and to make a long story somewhat shorter, I found that while most stock Oxygen images I attempt to sideload onto the device fail (at precisely 47%, oddly), I was able to sideload two different Hydrogen images without any resistance at all. I'm guessing something to do with the eMMC vs UFS file storage systems and how each OS uses them.
So I got Hydrogen flashed onto my my device. Smooth sailing, right? Afraid not. Despite fastboot's output clearly stating it was a successful transfer, and the stock recovery on the device echoing this, I still cannot get the OS to load. Now i' stuck with the loading screen hanging indefinitely prior to animation occurring, so basically the static ONEPLUS logo. Factory resets and cache wipes have done nothing to help the situation along. Conventional wisdom from the threads here seem to say using the MSMTool is the right answer..... and thus the circle of frustration is complete with me arriving back where I started. Does anybody have another suggestion I can try out? Still can't flash/boot to TWRP, unlock bootloader, or access Android to activate USB Debug/OEM Unlock either btw.

Have you tried flashing just the firmware, i havent flashed in years but i would assume you could sideload the firmware as well?

voodooline said:
Have you tried flashing just the firmware, i havent flashed in years but i would assume you could sideload the firmware as well?
Click to expand...
Click to collapse
Guess who didn't read? And after a year without flashing + a lack of reading skills, you still think you could solve this case? That's a spirit.
===
You better do pm some devs in dev section and point them to this thread and see if they can help, if you are still curious.
My guess is dead emmc, it can be replaced without buying the whole board.

150208 said:
Guess who didn't read? And after a year without flashing + a lack of reading skills, you still think you could solve this case? That's a spirit.
===
You better do pm some devs in dev section and point them to this thread and see if they can help, if you are still curious.
My guess is dead emmc, it can be replaced without buying the whole board.
Click to expand...
Click to collapse
I did read it, its funny always someone who has to be a **** about things. I should have been more specific. He was able to flash h2os. So he could try to flash the firmware for h2os to see if that gets it to boot.

voodooline said:
I did read it, its funny always someone who has to be a **** about things. I should have been more specific. He was able to flash h2os. So he could try to flash the firmware for h2os to see if that gets it to boot.
Click to expand...
Click to collapse
Magnificent, bro.
You're a truly genius.

Kernel tree with mediatek connectivity drivers builtin

Hi all,
Since I haven't seen a kernel tree on XDA that had the mediatek drivers (the ones xiaomi has put in a separate git repo), I thought I'll put them back into the tree.
The drivers have been taken out of the tree from drivers/misc/mediatek. To make them work at all, the makefiles need some changes.
1) In the connectivity folder, to build more than just the wifi drivers, the others folders must be added back into the build (at least, obj-y += {folders}/).
2) The include directives must be changed to include from $(srctree)/drivers/misc/mediatek/... instead of $(TOP)/vendor/.../kernel_modules/...
Besides that, there are some minor changes here and there to get them working properly.
I've managed to get it to boot correctly after disabling stock modules (by moving the folder, otherwise they seem to get inserted even if the drivers are already in the kernel). However, even if the connac device appears in the /sys/devices/platform, wifi still fails to turn on. GNSS turns on, but it is very slow. Only some gps and glonass sats show up, much fewer than normally should, and I could not get a fix (this might be either because there's some firmware problem preventing beidou and galileo from showing up, or the system is too slow and hasn't yet loaded beidou and galileo data - can't tell because I've been indoors and even on stock kernel, cold TTFF is quite long).
Care to share some thoughts? Some resources, maybe?
P.S.: I've not published the merged tree because I've poked it a lot and it's a mess.

I've dug more into this. It's quite likely that the drivers released by Xiaomi don't match the shipped kernel (or the hardware on the device).
It looks like the released wifi driver has trouble accessing the hardware registers and ports on the wifi block. Also, the firmware binary specified in the driver source doesn't match those on vendor (it's searching for WIFI_RAM_CODE_soc1_0_1_1, while stock uses WIFI_RAM_CODE_soc1_0_2a_1; these are hardcoded in the driver). I've searched through the sources for the file loaded by the stock kernel and it's not mentioned anywhere in the source.
Edit: Actually it does match, it's the flavoured firmware branch. I was confused by the comments above the code.
Edit2: Everything boils down to a missing definition in the Makefiles/build options. See below.

Ok, finally found the problem. The modules need to be built with WIFI_IP_SET=2. This flag changes both the name of the firmware and some padding in the structures. That's why it failed so hard.
AAAArgh...
If this works ok, I'll try to post a working tree next couple of days.

I've put the sources on github. Wifi, GPS, NFC, Bluetooth work built-in.
That said, there still seems to be some problems (I'm seeing reboots every 15 mins or so).
I know for a thing that there's a problem with the embedded secure element (somewhere along the TEE/NFC stack), and I think that's what causes the reboots.

Couldn't get the eSE to work; if anyone's interested, the error looks like this:
Code:
[ 197.239862] -(0)[240:teei_switch_thr][TZ_LOG] ESE-S | [phNxpEsePal_spi.cc:171/spiread_dma] <err> dma read nad over time.\x0d
[ 197.241310] -(0)[240:teei_switch_thr][TZ_LOG] ESE-S | \x0d
Which sounds like the eSE server in the TEE can't talk properly to the eSE chip over the spi bus.
However, I've disabled the secure element in Android, and it seems like the problems are gone (though secure card wallets, like Google Pay will have to use a software implementation).
I've disabled the secure element in Android by (replace removal by moving to a backup location at your discretion)
Code:
rm /vendor/etc/init/[email protected]
rm /vendor/etc/init/[email protected]
rm /bin/hw/[email protected]
rm /bin/hw/[email protected]
pm hide com.android.se
It might be that only the last command is necessary though (if you do test this, please reply - I only went up on the chain of dependencies).

From locked bootloader to Lineage OS 19.0 on ANE LX3

* Prelude
What started this journey was noticing that Tasker had restricted call screening
to android versions 10+. I would be delighted to hear what techniques fellow
forum members use to fight spam calls. I am a complete beginner, and so I
thought I would detail my journey in case it proves useful for others. There is
some outdated information and plenty of online tutorials, it just takes some
time to sort it out.
I have a Huawei P20 lite ANE LX3.
* Unlocking the Bootloader
I believe this is by far the most tedious step. Now that I am free from carrier
contracts, I know that my next phone will not be from a manufacturer with a
locked bootloader. In any case you may have some luck emailing Huawei directly
or through paid third-party services. What worked for me was potatoNV
GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620 - GitHub - mashed-potatoes/PotatoNV: Unlock bootloader of Huawei devices on Kirin 960/95х/65x/620
github.com
The documentation on the repository is perfectly fine. Specifically in my case,
the device first showed under device manager as 'USP SER' and I had to reinstall
the test point drivers (found in the above README) for it to turn into 'Huawei
USB COM 1.0.' PotatoNV did its job and I managed to get my unlock code.
* Project Treble/GSI? Fastboot? ADB?
Again, being new to all of this, I did notice a lot of noise when searching
online for information. The most informative links I found useful:
- https://github.com/phhusson/treble_experimentations/wiki/Frequently-Asked-Questions-(FAQ)
- https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
- https://developer.android.com/studio/releases/platform-tools
What is worth repeating is to USE THE GOOGLE PLAY APP 'TREBLE INFO' over the
more popular 'Treble Check', which falsely informed my that I needed an A image
rather than being fine with an A/B image. This wasted a lot of my time.
Initially I went down the route of using TWRP to flash the image, but this led
me to a soft brick (could very well be my own fault). The phone was frozen to
the TWRP splash screen, 'adb reboot bootloader' would not work. Power plus
volume down or volume up also had no effect. With no access to e-recovery or the
bootloader, I had really dug myself into a hole.
* Unscrewing a bricked phone
My last chance at fixing this consisted of getting the stock service firmware.
[NO ROOT] [BOOTLOADER LOCK] How to install an update [DLOAD Method]
I'm very happy :D:D After spending a lot of time trying to figure out how to install an original firmware using the dload method, I managed to find a guide that explains how to do it and today I will report the main steps: First of all, we need...
forum.xda-developers.com
This forum thread was useful and on unscrewing the situation. The real useful
part of the above link was the 'Software Upgrade Guidelines' documentation.
So ultimately what unbricked my phone was following the direction to press all
three buttons (power, volume up, volume down) at once to enter "automatic
upgrade mode." I gather this was supposed to utilize the 'dload' folder I copied
over earlier. As an aside, it was a lifesaver that 'adb shell' gave me access to
some unix commands to make poking around easier. The automatic upgrade using the
'dload' folder failed.
BUT RESTARTING FROM THIS "AUTOMATIC UPGRADE MODE" GRANTED ME ACCESS TO RECOVERY
MODE VIA THE POWER BUTTON + VOLUME UP whereas before this was not the case. By
the grace of God this allowed me to download a recovery image from Huawei
servers. How much longer will their servers retain this image? I don't know, but
I'm grateful either way.
* Lineage OS successfully flashed
What instead worked for me was flashing the "GSI image without TWRP" - from the
2nd of the 3 links above. This is the image that I used:
lineage-19.0-20220211-UNOFFICIAL-treble_arm64_bgS-vndklite.img.xz
For sake of completeness M Rahman's 2018 article was still mostly accurate, the
'-u' flag may be omitted from 'fastboot -u flash system name_of_system.img'. The
only other thing I would append to his instructions is -AIF-'s recommendation to
4. Run command fastboot reboot, unplug your phone, when appears on screen yellow
warning, press and hold for 3 sec Volume Up . In eRecovery select 'Wipe
data/factory reset'.Reboot . - From:
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/
I say this because I had seen the power button + down volume/up volume technique
yield different results depending on whether the phone was connected to the
computer. I suspect this is the fault of HiSuite, but who is going to track down
a bug like this?
* Evaluation
Pros:
- I had solved my initial problem.
- The new phone feeling!
Cons:
The most noticeable deficiency was that adding an external SD card AS SYSTEM
STORAGE would never finish; I gave it about a day before giving up.
I will add further reports as they come up.
In conclusion I give props to Huawei for keeping that server image alive, but
last I heard they were pivoting away from smartphones into clean energy
altogether. If I were to do it all over again, I'm not sure it would be worth
it. This took a good day's worth of time.
Big thanks to the AOSP developers and the XDA community for buying
my old P20 lite a bit more time. I'm also interested in which companies the
community considers friendly to "popping the hood"/tweaker mentality.
Hope this was helpful for someone,

Question Android Beta to Factory Reset mucked up, plus a bunch of troubleshooting I've already tried

Okay. The android beta program was messing with an app I use regularly so I backed up my phone on google 1 and all that fun stuff then did the opt out and just ran stuff like it was supposed to. Then, it got stuck in fastboot mode and said that the installation failed. If this wasn't already obvious I'm not good at talking tech but I am decent at troubleshooting things, so I tried. Today I learned what fastboot and adb are, what sideloading is, stuff like lineageos and twrp if. If that's what that one was called, today is a blur. Okay let me be more specific.
It seems like what I need to do is sideload the right OTA image, but I can't find the one I need. The last two I tried, one being the very wrong one and one being (copied from official source):
12.1.0 (SQ3A.220705.003, Jul 2022)Linke66e2df393d5a0f885f62d2de086dcd80cdcf8eb28d567f4582ff67756876170
But this one also wasn't new enough? It says: error: recovery: update package is older than the current build, expected a build newer than the timestamp 1657306786 but package has timestamp 1654117437 and downgrade not allowed.
I've tried the flashing tool (my phone shows up but has a connection issue I couldn't fix), the google rescue mode tool (my phone connected but the browser tool just looped til the phone timed out), I've tried sideloading the twrp apk and such which didn't work due to "error: closed" which I also couldn't fix, but I'm pretty sure all these problems are caused by not having developer options and debugging and those things turned...whichever way they need to be.
If this is important, I'm in Canada, using Telus, the phone is still fairly new and was working perfectly I just had to opt in and then out of the android beta. Kicking myself for that now. If I need to be more specific I'll try but for now, can I unbrick my phone without taking it somewhere to be unbricked for me? I also don't have an SD card to use to do it that way. Thank you.

Try This link for help.

lilyhollow said:
Okay. The android beta program was messing with an app I use regularly so I backed up my phone on google 1 and all that fun stuff then did the opt out and just ran stuff like it was supposed to. Then, it got stuck in fastboot mode and said that the installation failed. If this wasn't already obvious I'm not good at talking tech but I am decent at troubleshooting things, so I tried. Today I learned what fastboot and adb are, what sideloading is, stuff like lineageos and twrp if. If that's what that one was called, today is a blur. Okay let me be more specific.
It seems like what I need to do is sideload the right OTA image, but I can't find the one I need. The last two I tried, one being the very wrong one and one being (copied from official source):
12.1.0 (SQ3A.220705.003, Jul 2022)Linke66e2df393d5a0f885f62d2de086dcd80cdcf8eb28d567f4582ff67756876170
But this one also wasn't new enough? It says: error: recovery: update package is older than the current build, expected a build newer than the timestamp 1657306786 but package has timestamp 1654117437 and downgrade not allowed.
I've tried the flashing tool (my phone shows up but has a connection issue I couldn't fix), the google rescue mode tool (my phone connected but the browser tool just looped til the phone timed out), I've tried sideloading the twrp apk and such which didn't work due to "error: closed" which I also couldn't fix, but I'm pretty sure all these problems are caused by not having developer options and debugging and those things turned...whichever way they need to be.
If this is important, I'm in Canada, using Telus, the phone is still fairly new and was working perfectly I just had to opt in and then out of the android beta. Kicking myself for that now. If I need to be more specific I'll try but for now, can I unbrick my phone without taking it somewhere to be unbricked for me? I also don't have an SD card to use to do it that way. Thank you.
Click to expand...
Click to collapse
what was the error you got in Android Flash Tool?

jcp2 said:
what was the error you got in Android Flash Tool?
Click to expand...
Click to collapse
{
"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 checked with all the troubleshooting tips for connection issues but nothing changed the status. Sometimes it would say already in use when I had the cmd open but then I use kill-server to free it up and it changes to this.

Is your bootloader unlocked? If it isn't (and if Telus is like the US phone carriers), then I don't think you would be able to revert back to Android 12. You will have to wait for Android 13 to officially launch and you can then manually flash the full image (as it seems that you cannot sideload the OTA). And you would have to manually flash the latest full Android 13 beta build for the time being.
Regardless, right now you should try looking into "platform-tools" here on XDA. Then, see if you can use adb to view your phone over USB connection with the stock Google USB cable that came with the phone (most random aftermarket cables work fine, however, a few do not seem to work). You would need USB Debugging enabled to do this, however, the phone may still respond since you had it fall into fastboot mode before (and you would essentially be using adb to put your phone into fastboot mode).
Leave a reply if you can put your phone into fastboot mode/if you can use adb. We can go further from there with what I know about this stuff.

NippleSauce said:
Is your bootloader unlocked? If it isn't (and if Telus is like the US phone carriers), then I don't think you would be able to revert back to Android 12. You will have to wait for Android 13 to officially launch and you can then manually flash the full image (as it seems that you cannot sideload the OTA). And you would have to manually flash the latest full Android 13 beta build for the time being.
Regardless, right now you should try looking into "platform-tools" here on XDA. Then, see if you can use adb to view your phone over USB connection with the stock Google USB cable that came with the phone (most random aftermarket cables work fine, however, a few do not seem to work). You would need USB Debugging enabled to do this, however, the phone may still respond since you had it fall into fastboot mode before (and you would essentially be using adb to put your phone into fastboot mode).
Leave a reply if you can put your phone into fastboot mode/if you can use adb. We can go further from there with what I know about this stuff.
Click to expand...
Click to collapse
Bootloader is locked. It's permanently stuck in fastboot mode, except when I switch to recovery or rescue, and then if I reboot the phone it goes into fastboot. When I use adb and use "adb devices" my device shows up as [devicenumber] sideload. Other adb commands won't work due to "error: closed" which I assumed was because debugging was off. Only thing I got to work so far was sideloading OTA, and you see how that went. But I do have platform-tools and adb and fastboot set up. So that's something. My USB cord is aftermarket but does seem to work.

are you using These drivers? for windows. which version of windows are you running? I think @NippleSauce is correct in that if you don't have usb debugging enabled (you don't) you'll have to wait for A13 final. Or, if you're in your 30 day return window.....take it back to Telus.

Sorry, I've been eating and lifting weights at almost the same time LOL. I also just got the Pixel Buds Pro in the mail (a day before the official release) and they are freaking amazing.
Anyway, since the phone keeps going into fastboot, perhaps we can move forward. What does the screen say on it when in fastboot? There are two different fastboot menus: regular "fastboot" and "fastboot d".
Feel free to post a screenshot if you have something to take a picture of the display with. We'll move forward from there once I'm done lifting =).

NippleSauce said:
Sorry, I've been eating and lifting weights at almost the same time LOL. I also just got the Pixel Buds Pro in the mail (a day before the official release) and they are freaking amazing.
Anyway, since the phone keeps going into fastboot, perhaps we can move forward. What does the screen say on it when in fastboot? There are two different fastboot menus: regular "fastboot" and "fastboot d".
Feel free to post a screenshot if you have something to take a picture of the display with. We'll move forward from there once I'm done lifting =).
Click to expand...
Click to collapse
how are those compared to the pixel buds a?

DespairFactor said:
how are those compared to the pixel buds a?
Click to expand...
Click to collapse
Holy shirtless cow with nine udders good. I'm really liking them. The 11mm drivers really amp up the quality and separation in the sound. I think they're quite close in sound quality to my Sennheiser True Wireless 3's - so I think the price makes it a good deal on today's market. But the thing that makes them such a good deal is that the transparency mode is awesome and is clear and audible to the point where you can't even tell via the audio that you're wearing earbuds. And on top of that, the noise cancellation is some scientific voodoo with its strength for specific sounds. Some light (and semi-enjoyable) sounds pass right through; like me typing on my keyboard or clicking my computer mouse. But other sounds that are generally more noticeable such as people speaking or audio from cellphones is completely gone. It's pretty weird but is very good!
And to top it off, I am also pretty poor in hearing after an sTBI a few years ago. Audio was important to me before the incident, and therefore has become more important to me now. But since my left ear hears sound in a way that makes the sound that goes to my brain sound like people speaking in Charlie Brown, I guess take my opinions with a grain of salt lol.

lilyhollow said:
Okay. The android beta program was messing with an app I use regularly so I backed up my phone on google 1 and all that fun stuff then did the opt out and just ran stuff like it was supposed to. Then, it got stuck in fastboot mode and said that the installation failed. If this wasn't already obvious I'm not good at talking tech but I am decent at troubleshooting things, so I tried. Today I learned what fastboot and adb are, what sideloading is, stuff like lineageos and twrp if. If that's what that one was called, today is a blur. Okay let me be more specific.
It seems like what I need to do is sideload the right OTA image, but I can't find the one I need. The last two I tried, one being the very wrong one and one being (copied from official source):
12.1.0 (SQ3A.220705.003, Jul 2022)Linke66e2df393d5a0f885f62d2de086dcd80cdcf8eb28d567f4582ff67756876170
But this one also wasn't new enough? It says: error: recovery: update package is older than the current build, expected a build newer than the timestamp 1657306786 but package has timestamp 1654117437 and downgrade not allowed.
I've tried the flashing tool (my phone shows up but has a connection issue I couldn't fix), the google rescue mode tool (my phone connected but the browser tool just looped til the phone timed out), I've tried sideloading the twrp apk and such which didn't work due to "error: closed" which I also couldn't fix, but I'm pretty sure all these problems are caused by not having developer options and debugging and those things turned...whichever way they need to be.
If this is important, I'm in Canada, using Telus, the phone is still fairly new and was working perfectly I just had to opt in and then out of the android beta. Kicking myself for that now. If I need to be more specific I'll try but for now, can I unbrick my phone without taking it somewhere to be unbricked for me? I also don't have an SD card to use to do it that way. Thank you.
Click to expand...
Click to collapse
I opted out of the A13 beta and ran into the sane issue as my bootloader is locked. I was able to get back to A12.
I Googled it and found that you need to use the volume buttons to scroll to recovery and select by pressing the power button. You will then see a screen that says no command, hold the power button and tap volume up and you will be in recovery mode. Scroll down and select install from ADB. You will need to place the most recent A13 OTA zip in platform tools which is what I use for all of my ADB stuff or whatever you use for ADB installation. DO NOT CHANGE THE FILE NAME. Once you have selected install from ADB on your device, type adb install (file name.zip), if you don't include.zip behind the file name, it will error out.
Once you hit enter, your device will say verifying file and you will see the percentage on the pc screen in adb. Once it completes the installation, reboot your device and skip through the setup. Once you skio through setup and get to the home screen, go into settings and go to where you check for updates, it should say update available,if not do a manual check. Once you are prompted about an update, select to download and install. It will install A12 with all the warnings about it wiping your device. Once this install completes and you restart, you will be back on A12.

Thank you everyone! Someone helped me out over telegram after I posted this and we worked through it, realized part of the problem was my cord, and then mostly fixed it the way truckerdewd said, except once android 13 was loaded, I used the Android Flash tool to set it back to 12 and it worked. I'm typing this from a working phone and very happy about it. <3
On a side note how are those fancy new ear buds comfort wise? I have a lot of trouble with pain from ear buds and only use really comfy over ear headphones that I like but I'm desperate for ear buds I don't hate.

lilyhollow said:
Thank you everyone! Someone helped me out over telegram after I posted this and we worked through it, realized part of the problem was my cord, and then mostly fixed it the way truckerdewd said, except once android 13 was loaded, I used the Android Flash tool to set it back to 12 and it worked. I'm typing this from a working phone and very happy about it. <3
On a side note how are those fancy new ear buds comfort wise? I have a lot of trouble with pain from ear buds and only use really comfy over ear headphones that I like but I'm desperate for ear buds I don't hate.
Click to expand...
Click to collapse
I got these Razer Chroma Earbads and they are super comfy and sound great. I got the ones that light up.
https://www.amazon.com/Razer-Hammerhead-Wireless-Bluetooth-Earbuds/dp/B099LZ2BGB/ref=mp_s_a_1_3?crid=V3S5O8UC9983&keywords=razer+chroma+earbuds&qid=1658996631&sprefix=Razer+chroma+ear%2Caps%2C152&sr=8-3

NippleSauce said:
Holy shirtless cow with nine udders good. I'm really liking them. The 11mm drivers really amp up the quality and separation in the sound. I think they're quite close in sound quality to my Sennheiser True Wireless 3's - so I think the price makes it a good deal on today's market. But the thing that makes them such a good deal is that the transparency mode is awesome and is clear and audible to the point where you can't even tell via the audio that you're wearing earbuds. And on top of that, the noise cancellation is some scientific voodoo with its strength for specific sounds. Some light (and semi-enjoyable) sounds pass right through; like me typing on my keyboard or clicking my computer mouse. But other sounds that are generally more noticeable such as people speaking or audio from cellphones is completely gone. It's pretty weird but is very good!
And to top it off, I am also pretty poor in hearing after an sTBI a few years ago. Audio was important to me before the incident, and therefore has become more important to me now. But since my left ear hears sound in a way that makes the sound that goes to my brain sound like people speaking in Charlie Brown, I guess take my opinions with a grain of salt lol.
Click to expand...
Click to collapse
I got my pair coming via amazon today