Related
To enable USB Debugging you need to go to Settings > About > Software Information > More > Build number - tap Build number 7 times to enable developer mode. After you get the window saying "developer mode has been enabled" go back to the main menu in Settings and under the System section you will have "Developer Options" added. In there you will have the ability to enable USB Debugging among other things.
Looking into developer options a little more there are a few interesting settings, such as the Background Process Limit under the Advanced section.
how do I get the cool screen where I can toss around jelly beans?
Thanks
Thanks for pointing out how to get to the developer menu.
crazyg0od33 said:
how do I get the cool screen where I can toss around jelly beans?
Click to expand...
Click to collapse
Think you hit the Android version (4.2.2). (Don't have my phone on me to confirm)
i tried that over and over but nothing happened
crazyg0od33 said:
i tried that over and over but nothing happened
Click to expand...
Click to collapse
HTC takes all the easter eggs out of their ROMs. We don't have that.
IceDragon59 said:
HTC takes all the easter eggs out of their ROMs. We don't have that.
Click to expand...
Click to collapse
damn. wanted to have some fun haha
keep trying. it probably took me somewhere in the neighborhood of 15 taps.
I was unable to access the Jelly Bean Easter Egg in the stock rom but Newts GPE rom has the Jelly Bean Easter Egg.
To Access Jelly Bean Event:
1. Go to Settings
2. Click About
3. Tap the "Android Version 4.2.2" bar 3 times, you will have to tap quickly or the event will not start.
4. At the screen with the single Giant Jelly Bean, tap the screen once to make the Jelly Bean a happy Jelly Bean and a long press will start the event
- [ROM]NOS 1.0.0 m7wlv Google Play Edition [JB 4.2.2 Stock ](8.24.2013) Optimized -
Enjoy tossing the Beans!
Had to tap build number about 20 times for it to enable.
Sent from my HTC6500LVW using Tapatalk 2
Flyhalf205 said:
Had to tap build number about 20 times for it to enable.
Sent from my HTC6500LVW using Tapatalk 2
Click to expand...
Click to collapse
same, it seems it like didn't register the click even though I did click it.
Enable USB De-bugging for Android on Lenovo Zuk Z2 Pro with Nougat 7.0 ZUI
youtu.be/XBMY3m-hAPM
Learn how to configure Developer settings in your phone /
Enable USB De-bugging for Android on Lenovo Zuk Z2 Pro with Nougat 7.0 MUI version 2.5.462
Steps :
1. Go to settings / Advanced settings / Developer Options
2. If u dont find Developer Options, Go to About & click 7 times on your ROM version (eg ZUI, MOKEE, MIUI..)
Under Developer Option :
Enable USB debugging
Enable USB 2.0 (Optional)
Revoke USB debugging authorizations (Optional)
Now connect your phone to PC & click "Allow" in the pop up on the phone
Moin Moin
I got my Pixel 2 XL yesterday
Upgrade to my 1.Gerneration Pixel XL
This morning i got a OTA Update push (100MB) and I now have the Version
OPD2.170816.017
Normally I would see on the Firmware Page from Google the Previous and actuall files.
But, I am not seeing a OPD2 on the Google page, and the version 17 is also not appearing.
Anyone know what the Deal ist?
Was is a OPD1 or OPD2?
With my old Nexus Phone or Pixel I could pull the image and sideload it.
But right now, I have a little fear and have no idea which file ist correct.
The Website makes a Jump from 12 to the 25 Firmware....
Can anyone help me out?
It seems its not up to date yet. so just wait, at least when we arrive dec 17 patches it will be shown or integrated then.
OPD2.170816.015 is shown for Pixel 2, OPD2.170816.017 is not shown yet for Pixel 2 XL, maybe google will add it or you willst just receive an OTA in dec 17 with security patches.
There is no need for now to start flashing to a factory image unless your phone is broken (then i would flash the non-verizon build). No one will know why google is doing that, the device has been just released yet in germany.
. at least when we arrive dec 17 patches it will be shown or integrated then.
Click to expand...
Click to collapse
Excuse me?
What are you trying imply?
Screenshot
Here my actuall Version
Hey Guys how's it going ... I'm having a little trouble getting twrp touch screen to work , running latest update 8.1 dec patch ...read many , many forum discussions here so i wouldn't make any mistakes but for some reason twrp touch is not responsive. Started from absolute stock brand new device , unlocked boot loader and critical and fastbooted pixel 2 xl twrp.img 3.2.1 and while in temporary twrp i flashed the twrp 3.2.1 zip and then the magisk 15.1 zip and absolutely nothing else and rebooted ....everything's fine except when i reboot in to twrp from my device, the touch screen does not work downloaded file from official twrp site and tried a couple times from scratch but never seems to change .... if there's something i've done wrong or if anyone might be able to help it would be very much appreciated and i apologize in advance if there is a solution on here that i haven't located yet
Mr. Blanco said:
Hey Guys how's it going ... I'm having a little trouble getting twrp touch screen to work , running latest update 8.1 dec patch ...read many , many forum discussions here so i wouldn't make any mistakes but for some reason twrp touch is not responsive. Started from absolute stock brand new device , unlocked boot loader and critical and fastbooted pixel 2 xl twrp.img 3.2.1 and while in temporary twrp i flashed the twrp 3.2.1 zip and then the magisk 15.1 zip and absolutely nothing else and rebooted ....everything's fine except when i reboot in to twrp from my device, the touch screen does not work downloaded file from official twrp site and tried a couple times from scratch but never seems to change .... if there's something i've done wrong or if anyone might be able to help it would be very much appreciated and i apologize in advance if there is a solution on here that i haven't located yet
Click to expand...
Click to collapse
Your issue has been well documented. From what I've read, it seems to be much more prevalent when using the stock kernel (boot.img) I would try flashing a custom kernel..ie..Flash, Elemental X, or electron to name a few. Hopefully that will solve your problem :good:
Yep, custom kernel seems to resolve it... I'm using Flash's latest.
Badger50 said:
Your issue has been well documented. From what I've read, it seems to be much more prevalent when using the stock kernel (boot.img) I would try flashing a custom kernel..ie..Flash, Elemental X, or electron to name a few. Hopefully that will solve your problem :good:
Click to expand...
Click to collapse
Thanks Badger , i really appreciate your help and suggestions ...i'm gonna give it a shot after work tonight
was on stock and having the touch issue... switched to flash kernel and all is well
dadoc04 said:
was on stock and having the touch issue... switched to flash kernel and all is well
Click to expand...
Click to collapse
thank you dadoc and also galaxyS for your guys support , really appreciate it !!! Do you notice any improvements using the Flash Kernal compared to stock ?
Mr. Blanco said:
thank you dadoc and also galaxyS for your guys support , really appreciate it !!! Do you notice any improvements using the Flash Kernal compared to stock ?
Click to expand...
Click to collapse
You'll have much more control over your kernel, such as, color control, gestures, memory, governors, schedulers, vibration, and wakelocks :good:
Badger50 said:
You'll have much more control over your kernel, such as, color control, gestures, memory, governors, schedulers, vibration, and wakelocks :good:
Click to expand...
Click to collapse
Thanks Badger .....between the Flash , Electron and ElementalX kernals , do you have a preference ?
Mr. Blanco said:
Thanks Badger .....between the Flash , Electron and ElementalX kernals , do you have a preference ?
Click to expand...
Click to collapse
Flash and Ex have been my 2 favorites for a long time. Flash does a great job keeping it up to date with upstream changes, and Ex has been a solid performer for many years. Can't go wrong with either :good::good:
Badger50 said:
Flash and Ex have been my 2 favorites for a long time. Flash does a great job keeping it up to date with upstream changes, and Ex has been a solid performer for many years. Can't go wrong with either :good::good:
Click to expand...
Click to collapse
agree 100% with what he said... been using flash since the 6p
using adb reboot recovery also works
Badger50 said:
Flash and Ex have been my 2 favorites for a long time. Flash does a great job keeping it up to date with upstream changes, and Ex has been a solid performer for many years. Can't go wrong with either :good::good:
Click to expand...
Click to collapse
Hey Badger i have a question , i'm on stock 8.1 dec patch . and wanted to flash Ex kernal but i've noticed that it and a couple other kernals are on jan patch ... if i flash kernal with new jan patch , will i still be able to revert back to factory image with dec patch ....as that is all that is available for my device presently
Mr. Blanco said:
Hey Badger i have a question , i'm on stock 8.1 dec patch . and wanted to flash Ex kernal but i've noticed that it and a couple other kernals are on jan patch ... if i flash kernal with new jan patch , will i still be able to revert back to factory image with dec patch ....as that is all that is available for my device presently
Click to expand...
Click to collapse
Yeah, no problem. When you flash your factory images, it will overwrite your system and return to stock kernel. Question, what do you mean by "that is all that's available for my device"? There are factory images for the P2XL on Google's site. Why not just upgrade to the January build?
Badger50 said:
Yeah, no problem. When you flash your factory images, it will overwrite your system and return to stock kernel. Question, what do you mean by "that is all that's available for my device"? There are factory images for the P2XL on Google's site. Why not just upgrade to the January build?
Click to expand...
Click to collapse
Thanks Badger . that's what i figured , but wanted to be safe as ive read you can't revert back but i'm assuming that's to the 8.0 os builds. Yeah i was all over it looking for my device build to flash the jan build but it's only showing the dec build for mine on the developers google site 8.1.0 (OPM2.171019.012, Dec 2017, Telus Only)
Mr. Blanco said:
Thanks Badger . that's what i figured , but wanted to be safe as ive read you can't revert back but i'm assuming that's to the 8.0 os builds. Yeah i was all over it looking for my device build to flash the jan build but it's only showing the dec build for mine on the developers google site 8.1.0 (OPM2.171019.012, Dec 2017, Telus Only)
Click to expand...
Click to collapse
im pretty sure you can use the version (OPM1.171019.013, Jan 2018)
as you see, there isn't a Telus only build for every single release.
Hopefully someone who is more familiar will chime in and give you some assurance
dadoc04 said:
im pretty sure you can use the version (OPM1.171019.013, Jan 2018)
as you see, there isn't a Telus only build for every single release.
Hopefully someone who is more familiar with chime in and give you some assurance
Click to expand...
Click to collapse
I was kind of wondering that myself as i've noticed that too about the available builds , never the less i really appreciate your help bro
Hi,
I am using Pixel2 and had same touch issue with TWRP and got a fix from other forum (Thanks to Google)
Before rebooting into recovery disable Ambient display in settings screen.
Settings -> Battery -> Ambient display >> Switch off Always On
Now try to reboot into TWRP and it should work.
If its still not working try with disabling all options under Ambient display option.
Thank You
tiniwings said:
Hi,
I am using Pixel2 and had same touch issue with TWRP and got a fix from other forum (Thanks to Google)
Before rebooting into recovery disable Ambient display in settings screen.
Settings -> Battery -> Ambient display >> Switch off Always On
Now try to reboot into TWRP and it should work.
If its still not working try with disabling all options under Ambient display option.
Thank You
Click to expand...
Click to collapse
Tried this solution doesnt work on my pixel 2
6alaal said:
Tried this solution doesnt work on my pixel 2
Click to expand...
Click to collapse
I know the P2 is a little different than the P2XL, but, have you tried disabling screen lock security and then fastbooting into twrp?
Badger50 said:
I know the P2 is a little different than the P2XL, but, have you tried disabling screen lock security and then fastbooting into twrp?
Click to expand...
Click to collapse
Yeah it's really weird all this happened lost my root after installing the screen fix module in magisk sorry I'm using the P2XL
Hi there,
I recently received a Mi A2 Lite.
After setting it up for the first time, the sytem showed a notification saying "System update - Unable to install system update - Click here to know more".
No information is displayed when I click this notification.
I decided to try to search for an update manually. Unfortunately, I have to face a pretty uncommon problem. I do not have any "Check system update" menu.
I looked for it in Settings > System and in Settings > System > About the phone. Nothing. I even activated the Developers Tools settings to check if I could find it, with no results...
I am no developer and I am pretty unfamiliar with deep system modifications. However I have tried to follow many tutorials to try to flash and root the system in order to be able to install manually a newer Android version. No success so far...
FYI, there is also something I do not get, in the Developer tools settings, there is no OEM enable option...
Here are some info on the operating system :
- Android version : 8.1.0
- LineageOS API level : Ilama (9)
- Security patch update : December 5th 2018
- Provider security patch level : December 1st 2018
- Kernel Version : 3.18.131-Genom-AOSP-LA.UM.6.6.r1-10400-89xx.0+ (gcc version 4.9x 20150123 (prerelease) (GCC))
- Build date : Mon Dec 31 14:34:24 UTC 2018
- Build number : OPM1.171019.019.V9.6.6.0.ODLMIFF
Does anybody have an idea on what's the matter here ?
Many thanks in advance for your great help
Cheers;
One thing is confusing me, "lineageos API Level.."
Maybe you bought a used Phone and it's already modified so now you're on LOS 15.
You don't need much knowledge to get your Phone back to Stock Android One, follow this link to get all info/tools you need:
https://c.mi.com/oc/miuidownload/detail?guide=2
Greetings
Thomas
Before you flash stock ROM on your device make sure you check that your device codename is "daisy". Daisy is the codename for Xiaomi Mi A2 Lite AndroidOne version. If you see "Sakura" somewhere in the about phone settings, this means you've bought a Redmi 6 Pro (MIUI version). Many people reported issues like this where they bought a second hand "Mi A2 Lite" but then their device turned out to be a Redmi 6 Pro that's been flashed with Lineage OS. If you flash the stock Mi A2 Lite ROM on a Redmi 6 Pro, you'll most likely brick the device and it will be very hard to recover.
If your phone is actually Mi A2 Lite, it will have androidone logo on the back cover, if yours have it then continue to flash the stock ROM for Mi A2 Lite. But if you're missing that logo, you should go over to the Redmi 6 Pro forum and flash the ROM of your choice from there. Cheers.
EDIT: If you need further help, don't hesitate to PM me.
@marstonpear @ohwarumbloss,
Thanks for your replies and your help guys.
Unfortunately, I couldn't find any solution so far.
The phone does have the AndroidOne logo on its back cover, but I couldn't find any "daisy" mention in the "About the phone" information menu. Neither I found any "Sakura" mention, so I guess this is a normal AndroidOne version.
I have faced some problems while flashing the stock ROM with an error message from MiFlashTools claiming there was a missmatch between the device and the ROM.
I have decided to launch a final nuclear attack against the seller and they accepted to refund me. I'm pretty happy I will no longer have to deal with this mess.
Many thanks for your replies guys. I hope I'll be the only one facing this wierd update problem.
Oh well, glad you got rid of it
I figured I'd ask in here rather than open new thread. Where would I find stock update .zip files for this device already installed TWRP.
mbl1979 said:
I figured I'd ask in here rather than open new thread. Where would I find stock update .zip files for this device already installed TWRP.
Click to expand...
Click to collapse
I believe you can't. Stock updates can't be installed through TWRP. But one user had made a package for stock ROM himself, so you can grab that package if you can find it in the forum. I'm not sure where you can find it, but someone made a flashable zip for TWRP. Check the Telegram groups and the forum please. Cheers.
Same here
PoorMike said:
@marstonpear @ohwarumbloss,
Thanks for your replies and your help guys.
Unfortunately, I couldn't find any solution so far.
The phone does have the AndroidOne logo on its back cover, but I couldn't find any "daisy" mention in the "About the phone" information menu. Neither I found any "Sakura" mention, so I guess this is a normal AndroidOne version.
I have faced some problems while flashing the stock ROM with an error message from MiFlashTools claiming there was a missmatch between the device and the ROM.
I have decided to launch a final nuclear attack against the seller and they accepted to refund me. I'm pretty happy I will no longer have to deal with this mess.
Many thanks for your replies guys. I hope I'll be the only one facing this wierd update problem.
Click to expand...
Click to collapse
Hey, same issue here. My dad bought the same model and it keeps warning about this impossible updates. I don' have any nuclear weapon, so I'm planning to threaten the seller to get the money back.
@pntballer505 reports getting the .037.A1 OTA on Verizon at post #138.
Old Verizon OTAs:
Several reports of the actual Verizon .036.A1 OTA, starting with @stevek216 at post #126.
Click to expand...
Click to collapse
https://support.google.com/pixelpho...t-software-to-get-all-the-features?hl=en&s=09
Checking for the software update
[Please check your device to see if you already have the latest software installed. Verify your Build number matches the official build by checking Settings -> About phone -> Build number. See section below]
After you complete the phone setup, the software update automatically downloads silently in the background. After the download completes, it will prompt you to reboot the phone. In case the software update is not seen, follow the instructions below:
Go to Settings -> System -> System update -> Check for update
Install the software update
Depending on your network connection speed and amount of apps involved, this will take about 25-50 minutes
Reboot the device after taking the update
Updating your apps
Many of the key apps have new features and improvements for Pixel 6. Please check to make sure that your apps are up to date by going to Play Store -> Your Account Icon -> Manage apps & device -> Update all.
Timing
Due to deployment timelines and staged rollouts, some updates may not be available until 10/28.
Software update Build number
After the software update, your device software version (Settings -> About phone -> Build number) will be be one of the following:
SD1A.210817.036
SD1A.210817.036.A8 (Verizon customers)
Click to expand...
Click to collapse
Not available for me just yet. Will try again on the 28th as the article mentioned.
Already updated to SD1A.210817.036 with SP dated 05/11 (UK) edited for typo
My unlocked Pixel 6 Pro purchased from Google Store USA has SD1A.210817.019.C2 and no updates.
No update yet. Here's to hoping for sometime today or tomorrow.
Mine is updating now, 64.35 MB, I'll update with before and after build numbers when it finishes.
EDIT: Almost an hour later and it's still optimizing apps, around 50%. Took about an hour and a half and a reboot, finally updated.
Unlocked model from Google Store USA.
Before:
Build Number: SD1A.210817.019.C2
Android security update: Oct 5
Baseband: g5123b-91479-210916-B-7738070
After:
Build Number: SD1A.210817.036
Android security update: Nov 5
Baseband: g5123b-92009-211008-B-7805583
Taking a long time. Really sweet phone.
nxt said:
My unlocked Pixel 6 Pro purchased from Google Store USA has SD1A.210817.019.C2 and no updates.
Click to expand...
Click to collapse
Same, nothing to update to.
GohanBurner said:
Same, nothing to update to.
Click to expand...
Click to collapse
It will come if they build it. I setup and popped the sim in. Be patient. It takes an hour to download. Damn. It's still updating. Best phone I ever had. I don't understand these complainers
I have an unlocked Pro used on Verizon but didn't get an update. Currently on SD1A.210817.019.C2
Golf c said:
Taking a long time. Really sweet phone.
Click to expand...
Click to collapse
Yeah took forever for me too, optimising apps. Build Number: SD1A.210817.036
Cares said:
I have an unlocked Pro used on Verizon but didn't get an update. Currently on SD1A.210817.019.C2
Click to expand...
Click to collapse
They are rolling out slowly. You'll get it in time.
Cares said:
I have an unlocked Pro used on Verizon but didn't get an update. Currently on SD1A.210817.019.C2
Click to expand...
Click to collapse
Did you receive the update in the meantime? I still haven't
nxt said:
Mine is updating now, 64.35 MB, I'll update with before and after build numbers when it finishes.
EDIT: Almost an hour later and it's still optimizing apps, around 50%. Took about an hour and a half and a reboot, finally updated.
Unlocked model from Google Store USA.
Before:
Build Number: SD1A.210817.019.C2
Android security update: Oct 5
Baseband: g5123b-91479-210916-B-7738070
After:
Build Number: SD1A.210817.036
Android security update: Nov 5
Baseband: g5123b-92009-211008-B-7805583
Click to expand...
Click to collapse
My P6 Pro still can't find the update
Supposedly the update should fix my fingerprint reading issues, so I'm sorta stoked to see that one comin' rather sooner than late.
Any way to force it? Stil no factory images/OTA, so I'm out of options.
No update here yet either (Google Store Unlocked on the Verizon network).
Indashio said:
Fingerprint and description from AIDA64 ?
Click to expand...
Click to collapse
I saw your previous post but I don't know where to find those. Give me exact specific instructions on where to find those, if I have to download an app, no thank you.
Morgrain said:
My P6 Pro still can't find the update
Supposedly the update should fix my fingerprint reading issues, so I'm sorta stoked to see that one comin' rather sooner than late.
Any way to force it? Stil no factory images/OTA, so I'm out of options.
Click to expand...
Click to collapse
Does it really fix fingerprint issues? do we have the changelog?
No changelog yet that I am aware of, only reports of people claiming that after the update you have to re-learn the fingerprint scanner and then it supposedly works better.
thx, could be just feeling