Hello,
When I install Android P with ADB sideload on my Nokia 7 Plus, I get an error at the end :
E: Failed to open driver control: No Such file or directory
After reboot, my phone work properly but, I have some issues like :
GPS don't work
Video on twitter and other app won't start
Double tap don't work
Youtube's vidéo won't work sometime
The phone have random reboot
My phone isn't bricked, I just have some issues with some features.
I tried to re-install the image couple times with linux/windows, but still the error, still the issues...
Anyone can help me ?
The Android P update, from what I have read, is only for the Google Pixel at the moment (the official release anyways)
Bowserman16162 said:
The Android P update, from what I have read, is only for the Google Pixel at the moment (the official release anyways)
Click to expand...
Click to collapse
Nope, there is 12 devices, for now, able to have Android P
See : developer [.] android [.] com/preview/devices/
(i cannot post URL)
Are you sure that you are installing the update for the correct device? You may have downloaded the update for the Nokia 7 and not the Nokia 7 Plus. If you already have the correct zip just delete the zip and download it again from the Nokia website.
Bowserman16162 said:
Are you sure that you are installing the update for the correct device? You may have downloaded the update for the Nokia 7 and not the Nokia 7 Plus. If you already have the correct zip just delete the zip and download it again from the Nokia website.
Click to expand...
Click to collapse
Yep, totally sure, there is no update for Nokia 7, only 7 Plus, plus Nokia require the IMEI for download the file.
{
"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"
}
Like i say in my post : I tried to re-install the image couple times with linux/windows, but still the error, still the issues...
Are you using Android SDK? The official website States you must use Android SDK 3.1 or higher. Android SDK 3.2 is recommended for the install of Android P.
Go to this link for more information https://developer.android.com/preview/setup-sdk
Bowserman16162 said:
Are you using Android SDK? The official website States you must use Android SDK 3.1 or higher. Android SDK 3.2 is recommended for the install of Android P.
Go to this link for more information https://developer.android.com/preview/setup-sdk
Click to expand...
Click to collapse
i tried with the 3.2 installed, but nothing change, I dont think ADB Sideload use the SDK...
Vulture_ said:
i tried with the 3.2 installed, but nothing change, I dont think ADB Sideload use the SDK...
Click to expand...
Click to collapse
The adb sideload does use it because it says 3.2 is the most stable version of Android SDK to use to download it. It says on the page there will be problems if you dont have version 3.1 or up. Also try uninstalling both Android SDK and anything to do with adb and fastboot and then reinstall Android SDK 3.2.
Let me know if that helps!
Sent from my ZTE Z835 using XDA Labs
Bowserman16162 said:
The adb sideload does use it because it says 3.2 is the most stable version of Android SDK to use to download it. It says on the page there will be problems if you dont have version 3.1 or up. Also try uninstalling both Android SDK and anything to do with adb and fastboot and then reinstall Android SDK 3.2.
Let me know if that helps!
Sent from my ZTE Z835 using XDA Labs
Click to expand...
Click to collapse
I don't understand how to do this haha ?
I downloaded Android Studio Canary with SDK 3.2, all installed
But how i'm supposed to install the Nokia 7 Plus Android P image with the new SDK ?
I could always do it for you (using a remote computer type application)
Sent from my ZTE Z835 using XDA Labs
I tried with the PC of a friend of mine, he have the same phone than me, he install Android P on his phone, no problem, but, after, we tried on my phone, but still the problem, so the problem isn't from ADB but the phone itself...
I tried to rollback, the boot freeze on the NOKIA screen...
nice...
Vulture_ said:
I tried to rollback, the boot freeze on the NOKIA screen...
nice...
Click to expand...
Click to collapse
Bootloop huh now your basically screwed unless you can find a stock rom of Android 8
Sent from my ZTE Maven 3 using XDA Labs
Related
I've tried everything. IT WILL NOT recognize my phone.
When trying to install the drivers it says the Authenticode does not have permission. I got the damn drivers directly from Android.com but it still doesn't think its authentic. Because of this, o cannot get the computer to recognize it as an adb device to root the phone.
I'm going nuts now. 2 days with literally 8 to 10 hours of trying with no success.
Can someone please please PLEASE help me?
I was having the same issue. Install PDAnet. Works like a charm. The program installs the drivers for you. You can uninstall the program after you get the drivers working if you'd like.
http://www.junefabrics.com/android/
rk0 said:
I was having the same issue. Install PDAnet. Works like a charm. The program installs the drivers for you. You can uninstall the program after you get the drivers working if you'd like.
http://www.junefabrics.com/android/
Click to expand...
Click to collapse
Didn't work.
During "installing drivers" it gave me this error (err=0xe000023f).
uoY_redruM said:
Didn't work.
During "installing drivers" it gave me this error (err=0xe000023f).
Click to expand...
Click to collapse
http://www.junefabrics.com/android/driver.php
Tried USBDeview, doesn't seem to let me uninstall anything even though it says you can.
Nothing appears to work.
This is what I keep getting, no matter what I do:
{
"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"
}
and what makes no sense is when trying to manually install new hardware, it SHOWS there are authenticodes for those drivers:
theres a way of turning off driver signature checks, try that
http://www.google.com/search?q=windows+7+disable+driver+signature
Are you on Vista or a Windows server version?
I had the same issue, turned out it was a hardware bug.
I sent it to the repair center at HTC in United Kingdom and i had it returned 5-6 days after, working and with locked bootloader
britoso said:
theres a way of turning off driver signature checks, try that
http://www.google.com/search?q=windows+7+disable+driver+signature
Are you on Vista or a Windows server version?
Click to expand...
Click to collapse
Vista.
I've tried a few of those suggestions and non of worked. Most involved the bcedit trick but its disabled or doesn't exist in the newer security updates.
Vista 32 bits or Vista 64bits ?
in hardware management console what do you see ? yellow question mark ?
Sometimes you need to go in it and find your device to check the HID number and copy it manually in the driver *..inf files to be detect by your OS.
I remembered doing this for my G1 long time ago (years).
If you can, get your hands on another n1 or android device to see if its a hardware problem with the phone, which i doubt. Also try a diff OS.
uoY_redruM said:
I've tried everything. IT WILL NOT recognize my phone.
Click to expand...
Click to collapse
This is for windows 7 64bits : http://tinyurl.com/2548qh4
take a look @ post #4
Hope you solve your problem !
In case you have Windows 7 you can try the following.
http://www.killertechtips.com/2009/...gning-in-windows-7-using-group-policy-editor/
Are you installing the usb drivers using the utility in ADB? If not, delete the drivers in hardware manager, and try installing them with the utility.
I had no problems doing this on Vista, but I prefer to use ADB on Linux.
Sent from my Nexus One using XDA App
hey .
maybe i´ve got something for you.
download my file here
install the binaries and then reboot (i said you don't have to, but i think in your case it would be better)
EDIT: is the debug function enabled in your device?
OK, after a few hours and still no success with Vista, I went to storage and pulled out my personal PC I built that hasn't run in a few years thanks to corrupt hard drives.
I spent 4 hours repairing and fixing the hard drives and SUCCESS, I got it to detect it on my Windows XP PC.
NOW! Still not working! In the command prompt, it shows adb devices as one connected but still when I do an adb push nothing happens. Just recycles the adb menu....
Any suggestions?
Your first mistake is using a PC that you know is not working properly. Try a known working pc.
Sent from my Nexus One using XDA App
Try using a Linux distribution. Saves a lot of time and headache.
or just reinstall your windows. win7 would be better than vista.
malevolent000 said:
Your first mistake is using a PC that you know is not working properly. Try a known working pc.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
The PC I'm using now IS working. It recognizes adb device but wont push the flash images or anything.
Hey Remixers! We are happy to announce that Remix OS for PC Beta version has been released! Please go to http://www.jide.com/en/remixos-for-pc for free download. Don't forget to subscribe to our newsletter for future update releases! #RemixOn
Version Number: 2.0.102
Release Time: 3/1/2016
Package Type: 64-bit version for Legacy BIOS & EFI boot / 32-bit version for Legacy boot
Update:
1) Installation on hard disk
2) Supports over-the-air (OTA) system updates
3) Release for 32-bit ROM
4) Better compatibility on new Intel CPUs (Update to Linux kernel 4.4）
5) New Installation tool that supports hard disk and USB flash drive
6) Larger data space (up to 8GB for hard disk and up to 64GB for USB flash drive)
7) Faster USB boot-up
8) Battery display bug fixed
9) Supports 1080p display on YouTube and Netflix apps.
10) Terminal app pre-installed for developers
11) Image file supports both EFI and Legacy mode
Wow, Downloading
cool!!
but, they links in the site it is still the alpha version...
eager to test rsrsrsrsrs
p.s.: sorry, my english is poor.
HoangTuBot said:
Wow, Hopefully it will online soon. Still Alpha
Click to expand...
Click to collapse
Hi there, it is up!
RemixOS_Joshua said:
Hi there, it is up!
Click to expand...
Click to collapse
It most certainly is not. Direct torrent link?
EDIT: Finally just showed up for me, here's direct link: https://otacdn.jide.com/release/Remix_OS_for_PC_64_B2016030106.zip
All links are fine/fixed now.....
Not workingon ufi. Says boot failed
Sent from my SM-N920T using Tapatalk
@RemixOS_Joshua Its posibble to upgrade from Alpha to BETA directly?
Ufi i get this error..
{
"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 managed to get it to boot via legacy but i preffer to keep my system as ufi
Sent from my SM-N920T using Tapatalk
]Download the Remix OS for PC package, which contains the Remix OS for PC ROM & Installation Tool.
Open the Remix OS Installation Tool and follow the instructions to install Remix OS for PC on your hard disk.
Reboot your PC.
Select Remix OS in Windows Boot Menu.
Click to expand...
Click to collapse
what's with the Windows Boot Menu? a windows OS installed is a prerequisite?
64bit version didn't work for me on my ASUS TP500L. I got the following error:
tsg2513 said:
64bit version didn't work for me on my ASUS TP500L. I got the following error:
Click to expand...
Click to collapse
Try legacy boot i was unable to get ufi to boot
Sent from my SM-N920T using Tapatalk
Up and running on 64bit verson on a Lenovo with i7 and 16gb ram , looks good
Can the torrent be peered on torbox.net? It gives fastest speed of upto 14MB/s (for me) on torrents
I got this message. "Failed to find cpu0 device node" i dont know what it means
Sent from my MotoE2(4G-LTE) using Tapatalk
Installed x64 successfully, start to install Google Play services and bang.. it freezes. Reboot -> installing second time - works fine. Went to Play Store, start downloading Google Chrome, installation finished and bang.. another freeze. I want to notice it is happening on my machine at work. Will give another shot when back home. Hope it will work fine.
egren58 said:
Try legacy boot i was unable to get ufi to boot
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Thanks for the suggestion. I'm not having much luck switching to Legacy Boot (tried F2, Ec, Del, F9, F12, Etc....but none of them get me into the BIOS Settings Screen).
Cristian Dante said:
I got this message. "Failed to find cpu0 device node" i dont know what it means
Sent from my MotoE2(4G-LTE) using Tapatalk
Click to expand...
Click to collapse
Same issue here on a Dell.
I have tried Legacy and it has no boot devices at all.
Won't boot even selection menu on Toshiba encore, alpha did, wont recognise this as boot device
Sent from my HTC One M8 using XDA Free mobile app
Uefi bios only !
Hey Guys,
So i have download the beta on the Remix OS (32BIT) although for the life of me cannot get it working. I have a linx Tablet which doesn't seem to have legacy support within the BIOS. As far as i am aware the 32BIT version of the OS is Legacy only so how am i meant to install the OS? Here's what i have tried so far.
- Used the beta software to install Remix OS on the same drive, installs fine but when i restart the tablet it boots straight into windows 10. Also when looking at the boot manager there's nothing there to boot from.
Installed the 64 BIT version which also doesn't boot although if i go into my boot manager it appears but when selecting the screen goes black. Most likely due to the fact I'm trying to boot 64 BIT on a 32BIT tablet.
Now this seems like its going to be an issue for many people with 32BIT systems with no legacy option available.
Has anyone had luck getting this working ???
My device Mi3 is running on CyanogenMod 13 and latest TWRP recovery. Unable to install weekly updates of CyanogenMod. Recently, got an update cm-13.0-20160516-NIGHTLY when i tried to install that there is an dialog box of "Apply Update" You are about to update bla bla bla... Note: This feature requires a compatible Recovery or updates will need to be installed manually. I didn't get what it means and i thought TWRP is a valid recovery so proceeded from that. After few minutes it rebooted the device top recovery and nothing happened from that. So i rebooted the system again searched over Internet about the issue haven't found any perfect solution (within what i found) but i tried by copying the update file to /sdcard (i mean root directory) and tried to install the update manually by using TWRP recovery but it is showing an error "Updater process ended with ERROR: 7 Error installing zip file '/sdcard/cm-13.0-20160516-NIGHTLY-cancro.zip' Updating partition details......done"
Can you help me out how to install the update and also tell me what I've done wrong so that i will not do that again.
Thanks in advance.
Dude, the answer to your question is in the first post of CM13 FAQ.
Go in here and follow the guide.
https://jrizzoli.github.io/dotfiles/
Hi @diongdyh
sorry for late reply, please help me with a step that is mentioned in the link you've given.
"Run flash_all.bat (on windows) or flash_all.sh (on OS x and Linux - it's suggested to open it from a terminal in these systems)"
Does it mean to run in cmd or what. Please help me out. If you can please elaborate that step.
manideeproyal said:
Hi @diongdyh
sorry for late reply, please help me with a step that is mentioned in the link you've given.
"Run flash_all.bat (on windows) or flash_all.sh (on OS x and Linux - it's suggested to open it from a terminal in these systems)"
Does it mean to run in cmd or what. Please help me out. If you can please elaborate that step.
Click to expand...
Click to collapse
Just connect your device and double click on "flash_all.bat"(I'm assuming you to be on Windows) and it'll do the rest
Well I encountered the same problem a while ago.. I just flashed miui 8 through twrp.. and booted and again flashed latest cm13 and it worked.. No problems so far..
Sent from my MI 3W using XDA-Developers mobile app
@ssasin.monish said:
Just connect your device and double click on "flash_all.bat"(I'm assuming you to be on Windows) and it'll do the rest
Click to expand...
Click to collapse
ok i'll do the same. I doubt whether the device needs to be in fastboot mode or normal system. If you can clear this i'll proceed because previously i tried the same but in fastboot and the device is recognized i checked by 'fastboot devices'.
manideeproyal said:
ok i'll do the same. I doubt whether the device needs to be in fastboot mode or normal system. If you can clear this i'll proceed because previously i tried the same but in fastboot and the device is recognized i checked by 'fastboot devices'.
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"
}
It is literally written in the second step. Bootloader=Fastboot mode.
diongdyh said:
It is literally written in the second step. Bootloader=Fastboot mode.
Click to expand...
Click to collapse
i've done the same @diongdyh, after selecting run something went in a flash on the desktop screen and nothing happened on my device and its still in fastboot mode. i think booting to miui 8 and then installing cm13 will be a better option as suggested by @sidhg for me as i'm not getting exactly what to do
even I am having the same problem, I nothing happpens on clicking on flash all file.........
manideeproyal said:
i've done the same @diongdyh, after selecting run something went in a flash on the desktop screen and nothing happened on my device and its still in fastboot mode. i think booting to miui 8 and then installing cm13 will be a better option as suggested by @sidhg for me as i'm not getting exactly what to do
Click to expand...
Click to collapse
Yes it'd be best that you flash miui 8 with fastboot/bootloader
http://bigota.d.miui.com/6.6.1/cancro_alpha_images_6.6.1_20160516.0000.22_6.0_cn_2231b4fcb7.tgz
Android DollhouseThe Definitive Android Flashtool.
This is the support thread for Pixel 6. If you have another device, please check the other threads:
Pixel 2XL: Support Thread
Pixel 6 Pro: Support Thread
Click to expand...
Click to collapse
I'm releasing the first user-facing preview of this tool, which is a convenient wrapper for common ADB/Fastboot controls.
It already comes preloaded with ADB and Fastboot binaries. There's no need to download anything else.
You need this .net runtime to run it: https://dotnet.microsoft.com/download/dotnet/thank-you/runtime-desktop-5.0.11-windows-x86-installer
For now, this is the first test run, which is Windows only. Mac OS + Linux versions will be released separately depending on how this performs.
Full cross-platform compatibility is planned.
{
"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"
}
Click to expand...
Click to collapse
For now, it is still a work in progress. I would like your feedback on this tool. Post here a screenshot of your Device info so I can improve compatibility with your device! Make sure to blur/hide your IMEI!
It includes an auto-updater so you will definitely be getting the latest improved release whenever I make changes.
Download + Source code : Github
General Pixel Development Channel : Telegram
Pixel 6 & 6 Pro Official Chat : Telegram
Click to expand...
Click to collapse
I already have access to the 6 and 6 Pro, although I don't use telegram because I already have enough ways for people to contact me lol
KaptinBoxxi said:
I already have access to the 6 and 6 Pro, although I don't use telegram because I already have enough ways for people to contact me lol
Click to expand...
Click to collapse
Can you use ADB / USB debugging? If possible, please show me the output of
adb devices -l
I will be picking up my Pixel 6 today when BestBuy let's me, I can post the output of this for you. I really want to get this thing running Lineage or CalyxOS asap, so I am open to helping out with development. I see that Lineage already has a stable Android 12 build, so it seems that may be coming first.
Dollscythe said:
Can you use ADB / USB debugging? If possible, please show me the output of
adb devices -l
Click to expand...
Click to collapse
Hi, I have a pixel 6, and here the result of : adb devices -l
theoh88 said:
Hi, I have a pixel 6, and here the result of : adb devices -l
View attachment 5443579
Click to expand...
Click to collapse
Awesome. Tool is out. Download links uploaded
Updated with .net runtime.
Just downloaded this tool, it loaded right up and found my Pixel 6, thank you!
Updated! Just open the program, it should automatically update to the latest version with pixel 6 support.
Dollscythe said:
Updated! Just open the program, it should automatically update to the latest version with pixel 6 support.
Click to expand...
Click to collapse
to install, just adb devices -l only?
trai_th said:
to install, just adb devices -l only?
Click to expand...
Click to collapse
you dont need that anymore
Dollscythe said:
you dont need that anymore
Click to expand...
Click to collapse
I installed .net but I can't run the application, what should I do?
Have the same issues. Have install net but can not start the Tool. Get always the rror i must flash net but i have it.
Hot-Proton said:
Have the same issues. Have install net but can not start the Tool. Get always the rror i must flash net but i have it.
Click to expand...
Click to collapse
I installed from the link provided above and it works now.
Hot-Proton said:
Have the same issues. Have install net but can not start the Tool. Get always the rror i must flash net but i have it.
Click to expand...
Click to collapse
I link the necessary .net binaries in the thread...
Stream the screen works pretty well, just low quality for some reason. My bootloader is not unlocked yet, I bought the device from T-Mobile so God-knows how long it will take.
You say this tool only works on Windows, but you use .NET 5.0 to build it, which is cross platform. What makes it Windows only?
I see there's been no updates or information since November, what is the current state of this project?
Info: https://support.google.com/pixelphone/thread/175255708/google-pixel-update-android-13?hl=en
Download page https://developers.google.com/android/ota#oriole
Be aware:
{
"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"
}
There is face unlock in this device now?
Cause this is what i see in the changelog:
Fix for issue preventing face unlock to trigger in certain conditions *[3]
Edit: My bad, this is for pixel 4 devices
root real android 13 yet?
Sideloaded on my US T-Mobile P6, seems good so far.
TheUndertaker21 said:
root real android 13 yet?
Click to expand...
Click to collapse
Magisk 25.2 works fine.
Nova launcher working with gestures?
Lughnasadh said:
Magisk 25.2 works fine.
Click to expand...
Click to collapse
How you update? Patch boot.img with Magisk Manager, flash image & pateched boot like before?
Sh0X31 said:
How you update? Patch boot.img mit Magisk, flash image & than boot like before?
Click to expand...
Click to collapse
After updating to A13 stable, yes, patch and flash.
Does it allow multiple bluetooth devices to be connected simultaneously?
Oh and does it simply update your current install or does it wipe and install?
poit said:
Sideloaded on my US T-Mobile P6, seems good so far.
Click to expand...
Click to collapse
How do you sideload with the bootloader locked? Does it wipe your phone? Waiting (impatiently) for T-Mobile to send out the new update.
So if I'm on beta 4.1 and take this update it will put me on stable release. And if I unenroll immediately after the update I should be placed on the stable channel? No qpr updates n such?
mojorisin7178 said:
So if I'm on beta 4.1 and take this update it will put me on stable release. And if I unenroll immediately after the update I should be placed on the stable channel? No qpr updates n such?
Click to expand...
Click to collapse
Correct.
"If you’re currently enrolled in the Android Beta program, you’ll get the Android 13 final release and remain enrolled to receive ongoing Beta updates for Android 13 feature drops, starting later this year. If you’d like to opt out of ongoing Beta updates without needing to wipe your device, just visit the Android Beta site and opt out after you get the Android 13 final release and before taking the first beta for Android 13 feature drops."
Android 13 is in AOSP!
News and insights on the Android platform, developer tools, and events.
android-developers.googleblog.com
inumugi said:
How do you sideload with the bootloader locked? Does it wipe your phone? Waiting (impatiently) for T-Mobile to send out the new update.
Click to expand...
Click to collapse
Don't know if my phones bootloader is locked, but I bought it direct from T-Mobile US. Instructions for sideloading using ADB are on the top of the download page. It didn't wipe my phone and it's quicker than an OTA install. https://developers.google.com/android/ota#oriole
Anyone get it OTA yet? Purchased unlocked from Google and on AT&T; nothing yet for me.
Trying to sideload the OTA image file downloaded from Google, using latest version of adb, seems to getting stuck at "serving: 'oriole-ota-tp1a.220624.021-a13fd9d0.zip' (~3%)" - phone displaying "Verifying update package..."
I've sideloaded OTA images in the past without any issues, anybody have a suggestion?
Steve53 said:
Trying to sideload the OTA image file downloaded from Google, using latest version of adb, seems to getting stuck at "serving: 'oriole-ota-tp1a.220624.021-a13fd9d0.zip' (~3%)" - phone displaying "Verifying update package..."
I've sideloaded OTA images in the past without any issues, anybody have a suggestion?
Click to expand...
Click to collapse
When you say "using the latest version of adb", are you referring to the latest version of Platform Tools? Are your drivers up-to-date? Try using different cables and/or ports?
Yep, latest version of platform tools. Have tried 2 different cables (one of which is the one that came with the phone). Will check for driver updates, but have used this same PC to perform previous updates on my Pixel 6.
Steve53 said:
Yep, latest version of platform tools. Have tried 2 different cables (one of which is the one that came with the phone). Will check for driver updates, but have used this same PC to perform previous updates on my Pixel 6.
Click to expand...
Click to collapse
Did you confirm you got a clean download by running a SHA-256 checksum? Just a stab in the dark