I have a Pixel presently running NDE63P, not rooted, bootloader locked. I downloaded the NDE63X OTA image, verified the download with the SHA-256 hash, and attempted to put it on the phone. Adb is version 1.0.36 from latest Android Studio. Adb loads the image into memory and then immediately puts out the message "failed to read command: Connection reset by peer", and returns me to the command prompt:
Code:
D:\Users\Nick\Downloads\Google>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
FA69X0309603 device
D:\Users\Nick\Downloads\Google>adb reboot recovery
D:\Users\Nick\Downloads\Google>adb sideload sailfish-ota-nde63x-59a512a1.zip
serving: 'sailfish-ota-nde63x-59a512a1.zip' (~0%) * failed to read command: Connection reset by peer
On the phone screen, I see:
Code:
Finding update package...
Opening update package...
Verifying update package...
and nothing further.
After rebooting both phone and PC I also tried the sideload using an older version of adb from adb-setup-1.4.3.exe. That version doesn't give an error msg about "failed to read command", but it never gets beyond 0% serving of the update, and viewing the adb process in Windows task manager shows it consuming no CPU and performing no I/O (I let it run for about half an hour before killing the process and rebooting the phone). I'm using the USB C<->A cable that came with the phone, and tried it in a couple of different ports in the PC.
Any suggestions on why this problem happens?
Are you placing the update file in the same folder as your ADB location. You might want to consider using a new folder location for the ADB. If you use your downloads location you could possibly use the wrong file while updating since there are so many items typically in that folder. For example I use "Android" folder on my desktop and only keep my SDK, ADB etc. in there so it's always pretty clean and easy to find. You open that folder and shift-right click and open command prompt here or if you've got a Mac it is very similar, cd desktop, cd android.
I think you missed a step
With the device powered on and USB debugging enabled, execute: adb reboot recovery The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the*Power*button and press*Volume Uponce, and a menu will appear. Select the option*Apply update from ADB.
Sent from my Pixel using Tapatalk
jay661972 said:
I think you missed a step
With the device powered on and USB debugging enabled, execute: adb reboot recovery The device is now in recovery mode and an Android logo with red exclamation mark should appear on screen.
Hold the*Power*button and press*Volume Uponce, and a menu will appear. Select the option*Apply update from ADB.
Click to expand...
Click to collapse
No, I did all that, and then selected "Apply update from ADB" before running "adb sideload <image>.zip" on the PC.
In any case, I found a workaround that didn't involve using ADB:
1. Copy the 820Mb NDE63V OTA image file I downloaded from the PC to Android/data/com.google.android.gms/cache on the phone.
2. Check for an update in Settings / About Phone / System updates. The phone found and downloaded a 47Mb update and then applied NDE63V.
About now shows Android security patch level as 5 November 2016 and Build number NDE63V.
NickJHP said:
No, I did all that, and then selected "Apply update from ADB" before running "adb sideload <image>.zip" on the PC.
In any case, I found a workaround that didn't involve using ADB:
1. Copy the 820Mb NDE63V OTA image file I downloaded from the PC to Android/data/com.google.android.gms/cache on the phone.
2. Check for an update in Settings / About Phone / System updates. The phone found and downloaded a 47Mb update and then applied NDE63V.
About now shows Android security patch level as 5 November 2016 and Build number NDE63V.
Click to expand...
Click to collapse
Did not work. Strongly suggests it was just coincidence that you got your OTA prompt after doing the steps.
Not to necro an old thread, but I had a similar issue and came across the solution. If anyone else encounters this problem, try different USB cords and USB ports. Very likely a USB port isn't supplying the proper data transfer.
Related
I've read a couple dozen of the pages from http://forum.xda-developers.com/showthread.php?t=1905674&page=95 titled
Nabi2 root and Gapps install
Click to expand...
Click to collapse
.
Using Win7 x64. Nabi2 version: 1.9.37 recently updated.
Can't post to above thread because this is my first post (restricted to "General" forums).
In "Jmz Nabi Recovery Installer" window it is always stuck in the "If stuck here drivers are not installed" step.
Prior to installing "PdaNet for Android" from http://junefabrics.com/index.php,
I had 2 devices in Control Panel under "Other devices" with a yellow '!'. One of the looked like the Nabi device. The other is named "MTP".
After installing PdaNet, only MTP remains with the yellow exclamation point.
What should the Nabi look like in the Control Panel if its properly configured with a driver and where would it be?
And what is MTP?
Apparently I'm still having a driver/connection problem from adb.
USB Debugging is on in the Nabi.
Put the nabi in 'fastboot' mode
Open a CMD Prompt and browse to the 'files' folder within 'jmzrootpackage'
Then type:
adb.exe
fastboot devices
It should return a value (fastboot working and drivers are installed)
Let me know how it goes.
Put the nabi in 'fastboot' mode
Open a CMD Prompt and browse to the 'files' folder within 'jmzrootpackage'
Then type:
adb.exe
Click to expand...
Click to collapse
Part of this command is missing right? Without input parms it just outputs the "uses" message.
fastboot devices
Click to expand...
Click to collapse
Unfortunately this returned nothing for me.
I'm glad you responded. Other suggestions?
Here is how i done it using Windows 8 x64
I done 3 nabi2's this way but had a lot of trouble first so here is what worked for me:
Sadly, i don't have any nabi2 with me now to explain exactly how i done it
1) First boot the Nabi2 normally and turn off usb debugging.
2) When fully booted connect USB cable.
3) Check device manager and drivers should be installed.
4) Unplug USB cable and turn on USB Debugging and Unknown Sources.
5) Reconnect USB Cable.
6) Drivers should install.
7) Install PDA Net on Laptop/PC
8) Select Samsung device from option screen when installing.
9) Wait for install to complete and drivers to install
10) Shut down Nabi2
11) Boot Nabi in fastboot (Hold + and Power buttons)
12) Select fastboot protocol
13) Here i seen Windows 8 take about 60 seconds installing fastboot drivers
To make sure fastboot drivers are installed i went to this thread
Code:
http://forum.xda-developers.com/showthread.php?t=1590800
and download ADB (save it to C:\SDK\platform-tools) and read over the helpful instructions in the thread.
Open command Prompt
Type the following (shown in RED) in the CMD window the opened:
cd\
cd C:\SDK\platform-tools
adb.exe (a list of options should be listed)
fastboot devices (it should list a number after you enter this)
If number displayed then you are good to go.
Reboot Nabi2 and wait to complete
Go to the location you saved jmzrootpackage
Go to files folder inside jmzrootpackage
Double click install.bat
Follow on screen prompts ( I took option 1)
TWRP recovery installs
I had trouble installing GAPPS.zip with an error being displayed about unable to mount /data
I copied GAPPS.zip to a SD Card and inserted to Nabi2
i install zip from EXT-SD Card even though it gives a load of errors about not able to mount /data
Wipe Cache/Dalvik
Reboot Nabi2
Go to daddy/mommy mode and you should have Google Apps installed.
Any problems let me know.
I'm using Windows 7 x64.
Your instructions with selecting "Samsung" for PdaNet install appears
to have done something right. So maybe I'm a little closer.
It completed the PdaNet install successfully and when I reconnect the
Nabi I see a message popup on Windows saying PdaNet connected something.
(It was too quick.)
So maybe I'm not doing the "Fastboot" portion correctly.
On Nabi hold <Power> and <Vol+> down at same time to turn it on.
Resulting Menu:
Boot Normally
Fastboot Protocol
Recovery Kernel
Forced Recovery
Use <Vol-> to move the selected item.
Moved selected item down to "Fastboot Protocol".
Use <Vol+> to "enter" selected item.
New Menu:
Bootloader
Continue
Reboot-bootloader
Reboot
Poweroff
Selected "Continue", and entered(<Vol+>).
At this point the Nabi boots up.
On PC in adminstrator mode for command window and with ALL anti-virus
security turned off:
> adb.exe kill-server
> adb.exe start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
> fastboot.exe devices
Nothing. (sigh)
After looking at Victoria Antonio's youtube of this process I'm convinced the driver install is still not correct.
Somehow it gets mucked up when I use PdaNet. Not sure how or why.
To make this picture clearer I posted some screen shots on my website: http <colon, 2 forward slashes>skippyvondrake.com
I hope someone can tell me how to unmuck what I've mucked.
skippyV said:
Selected "Continue", and entered(<Vol+>).)
Click to expand...
Click to collapse
Don't press Continue on the Nabi after selecting fastboot protocol
After selecting fastboot protocol leave it.
skippyV said:
> fastboot.exe devices
Click to expand...
Click to collapse
The command is:
fastboot devices
not
fastboot.exe devices
Thanks for telling me about when I'm in fastboot mode.
I DO get a device number when in fastboot mode and from 'fastboot devices'
But adb still cannot "see" the device. All commands using adb result in:
error: device not found
Regardless of what mode the Nabi is in.
SOLVED
I finally decided to try this with a different computer. Same OS and architecture.
But this computer didn't have various android development "kits" installed previously.
And it worked without a hitch.
The youtube by Victoria Antonio pointed out a few nuances I didn't know.
And you helped too, BBKGTTDi, so giving you "thank you" points.
Chow!
Glad you got it work SkippyV
I just need to figure out now, when i download a game to the Nabi2 from the playstore, how to get it so show in the kids mode
BBKGTTDi said:
Glad you got it work SkippyV
I just need to figure out now, when i download a game to the Nabi2 from the playstore, how to get it so show in the kids mode
Click to expand...
Click to collapse
When I get there - if I figure it out - I'll send you a private email sense that would be a different "thread'. There are other nuances I've noticed too...
show game in Nabi mode after rooting
@BBKGTTDi, I thought there would be a way to send private messages/emails on this forum - but I don't see it.
I ran into the same problem after rooting the Nabi. The "Add Apps" app doesn't work as its supposed to.
It worked prior to rooting.
It does list the newly installed apps, but selecting them for Nabi-Mode, rebooting, and they aren't there.
Only visible in Mommy/Daddy mode.
So if you figure it out please let me know!
The "Add Apps" app is working correctly now. Don't know what happened before.
I must be getting "Nabi-ed out".
Let me know if you're still having troubles.
skippyV said:
I'm using Windows 7 x64.
Your instructions with selecting "Samsung" for PdaNet install appears
to have done something right. So maybe I'm a little closer.
It completed the PdaNet install successfully and when I reconnect the
Nabi I see a message popup on Windows saying PdaNet connected something.
(It was too quick.)
So maybe I'm not doing the "Fastboot" portion correctly.
On Nabi hold <Power> and <Vol+> down at same time to turn it on.
Resulting Menu:
Boot Normally
Fastboot Protocol
Recovery Kernel
Forced Recovery
Use <Vol-> to move the selected item.
Moved selected item down to "Fastboot Protocol".
Use <Vol+> to "enter" selected item.
New Menu:
Bootloader
Continue
Reboot-bootloader
Reboot
Poweroff
Selected "Continue", and entered(<Vol+>).
At this point the Nabi boots up.
On PC in adminstrator mode for command window and with ALL anti-virus
security turned off:
> adb.exe kill-server
> adb.exe start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
> fastboot.exe devices
Nothing. (sigh)
Click to expand...
Click to collapse
I ve got the same problem using windows xp, 7 or 8.1 after OTA update to jellybean.
Any ideas of what is going on?
arvati said:
I ve got the same problem using windows xp, 7 or 8.1 after OTA update to jellybean.
Any ideas of what is going on?
Click to expand...
Click to collapse
I did have those problems last year. Still think they were driver related.
I use mehtuus's package now. He has a useful install script.
http://forum.xda-developers.com/showthread.php?t=2172843
And when I want to use adb in "manual" mode I just launch a command prompt from his
'adb' directory (package is named 'mn2ri-v1.5.0-beta2.zip').
Try playing with his installer. And see if anything is displayed using:
Code:
adb devices
Thanks skippyV. I got it in fastboot last week with ubuntu and installed TWRP sucessfully.
One of the great new features of Nougat on new devices like the Pixel is the seamless installation. Because there are two partitions, OTA updates can install and optimize in the background; then reboot straight into the updated version. I had read a while back that installing an OTA manually might not allow the same seamless update path. Does anyone know? Has anyone tried it?
I want to keep pure stock, non-rooted, etc. I just want my OTA now rather than potentially waiting weeks for it. Seems like installing the OTA manually via ADB could install it to the second partition and preserve all apps and user data...but I'm not about to find out the hard way.
Side loading the OTA won't wipe your user data or anything. The "seamless" update system simply allows Android to update itself while still letting you use the phone, needing only a reboot to switch once that's done. The only difference between that and sideloading is that it takes a while and you can't use your phone during the process.
Just took the update myself through sideloading on stock, so feel free to go ahead with it!
zphantom55 said:
Side loading the OTA won't wipe your user data or anything. The "seamless" update system simply allows Android to update itself while still letting you use the phone, needing only a reboot to switch once that's done. The only difference between that and sideloading is that it takes a while and you can't use your phone during the process.
Just took the update myself through sideloading on stock, so feel free to go ahead with it!
Click to expand...
Click to collapse
Thanks, appreciate that! Giving it a try now.
Super easy process. If this helps anyone else, here are the basics.
On Windows computer:
1. Download the appropriate OTA image from Google: https://developers.google.com/android/ota
2. Install the latest version of Minimal ADB and Fastboot: https://androidmtk.com/download-minimal-adb-and-fastboot-tool
On Pixel
3. Enable USB debugging from Settings > Developer Menu
4. Plug Pixel into USB port in your computer using the USB-C to USB-A cable that came with the phone. Windows 10 (and probably earlier versions) will install drivers if you haven't plugged it in before.
On Computer
5. In command prompt in Minimal ADB directory, type "adb devices". Make sure a device shows up with the word "device" after it. If it says "unauthorized", you need to accept the dialog box on the phone, then try again.
6. After OTA file is downloaded, check the checksum again the SHA-256 hash listed on the Google OTA page, if you want. Not really needed since the phone will check this later before it installs.
7. Move the OTA file into the Minimal ADB directory.
8. In the command prompt, type "adb reboot recovery"
On Pixel
9. You should now see Android logo with red exclamation mark on the screen. Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
On Computer
10. In command prompt type "adb sideload [filename of OTA file].zip"
On Pixel
11. Once the update finishes, reboot the phone by choosing Reboot the system now.
12. After Android loads, you should disable USB debugging for security.
There is no need to unlock bootloader for sideloading an OTA. (Don't do it--it will factory reset your phone.)
9. You should now see Android logo with red exclamation mark on the screen. Hold the Power button and press Volume Up once, and a menu will appear. Select the option Apply update from ADB.
....question ? doing same thing on my pixel...went ok, also got nexus 6p ...dont know how to enter to recovery mode on 6p
I never modified my phone whatsoever, I apply the OTA updates
Last day it bricked between my hands while I texted someone
I can boot it in "CSC FastBoot Mode" and here I can select what I want to do
Is there a way to reflash it without loosing data? Or anything, but retreiving my data
Please, someone can reply if it's possible?
Does it offer the option to access/start recovery? If yes once in recovery mode you should be able to choose apply update from adb or maybe even apply update from sd card.
Depending on the firmware you were on (Android 11 or Android 10) download the appropriate firmware version from https://www.asus.com/Mobile/Phones/All-series/ZenFone-6/HelpDesk_BIOS?model2Name=ZenFone-6 and rename it to update.zip and put in on your sd card if you have one and if that options is available. If that option is available choose that option and navigate to the appropriate folder and choose the update.zip.
If you only have the apply update from adb option or the other one doesn't work download the platform tools https://developer.android.com/studio/releases/platform-tools first, extract them, connect your phone to your pc, then in the extracted folder hold shift key while right clicking an empty space in the extracted windows explorer folder and choose the option "open command prompt here" or similar. On your phone choose the update from adb option, in the command prompt on pc put in adb devices first. If it hasn't already windows should install drivers now and the command prompt should say a long sequence of numbers and "sideload" besides it. If windows doesn't recognise the device or it doesn't show any device in the command prompt line go to windows updates, "show optional windows updates", open driver updates and it should offer an ASUS android bootloader or ASUS adb driver or something similar.
Once that works simply input the command shown on the phone adb sideload update.zip or similar into the command prompt and it should reinstall the full OTA again without wiping anything.
*double post*
regenwurm16 said:
Does it offer the option to access/start recovery? If yes once in recovery mode you should be able to choose apply update from adb or maybe even apply update from sd card.
Depending on the firmware you were on (Android 11 or Android 10) download the appropriate firmware version from https://www.asus.com/Mobile/Phones/All-series/ZenFone-6/HelpDesk_BIOS?model2Name=ZenFone-6 and rename it to update.zip and put in on your sd card if you have one and if that options is available. If that option is available choose that option and navigate to the appropriate folder and choose the update.zip.
If you only have the apply update from adb option or the other one doesn't work download the platform tools https://developer.android.com/studio/releases/platform-tools first, extract them, connect your phone to your pc, then in the extracted folder hold shift key while right clicking an empty space in the extracted windows explorer folder and choose the option "open command prompt here" or similar. On your phone choose the update from adb option, in the command prompt on pc put in adb devices first. If it hasn't already windows should install drivers now and the command prompt should say a long sequence of numbers and "sideload" besides it. If windows doesn't recognise the device or it doesn't show any device in the command prompt line go to windows updates, "show optional windows updates", open driver updates and it should offer an ASUS android bootloader or ASUS adb driver or something similar.
Once that works simply input the command shown on the phone adb sideload update.zip or similar into the command prompt and it should reinstall the full OTA again without wiping anything.
Click to expand...
Click to collapse
How can I know if I need WW version or another one?
I don't remember if I was on 10 or 11 but I applied all OTA until december 2020, something like that
And how can I know if I can take the last firmware version or not?
Booting into recovery mode gives a black screen for 10 seconds then a reboot
Even the charging mode display bolt before charging animation then black screen then reboot itself after a time
Only CSC mode works normally, displaying something and not rebooting
In general ASUS does only offer one firmware package for all regions as far as I know and the statement on the firmware page generally only means which regions it has been certified for. Further information can be found at https://zentalk.asus.com/en/categories/zenfone-6-(zs630kl)
It depends on where you bought the device.
If recovery mode isn't accessible you will most likely have to use on of the unbrick threads under https://forum.xda-developers.com/f/asus-zenfone-6-2019-guides-news-discussion.8906/ most probably https://forum.xda-developers.com/t/...k-your-zenfone-6-android-p-q-zs630kl.4189715/ will help you here.
Hi,
during the update the phone got stuck, daughter restarted couple of times but it always got to the 76%, hang there and then restarted itself in the endless loop.
I've tried the the hard reset (Power+VolUP) and it got to the screen saying "No Command". Then I pressed the same combo again to get to the bootloader and tried the wipe / reset. During that process I got the error message "E: Can't send SPI message. Try again" and then it said it was successful, but rebooting did nothing, got stuck in the restart loop.
So I've done the research and wanted to to upload the OTA update, have done that but that didn't do anything.
So I've found some articles on how to upload the stock rom/image but I'm unable to do so as sending adb commands is disabled due to the phone being LOCKED. I've learned that the USB debugging needs to be enabled, however I'm unable to get into the OS to set it up, so found this article:
How to enable USB Debugging in Android using recovery mode?
One million questions, Is it possible to Enable USB Debugging in Android Using Recovery Mode or any other technique? Well, the answer is Yes! It is now
www.isrgrajan.com
which outlines the following steps (in summary):
Download the Stock ROM for your device- Google it, I am dam sure you can find it. [DONE]
Download SuperSU from UPDATE-SuperSU-v1.65.zip [DONE][looks pretty old though]
Steps to Enable USB Debugging Using Recovery Mode
Unzip the stock ROM. [DONE]
Within the extracted folder, you will find the system.img well extract it too using Ext4 Unpacker [DONE but plenty of folder are empty, but eventually plentu of APK along]
Also, extract the Update-SuperSU.v1.65.zip file. [DONE, again, looks pretty old]
Now open the folder where you have extracted the system.img files [DONE]
Grab any .apk file from this folder and change the extension from .apk to .zip [PROBLEM: the apks are all over the shop. Which APK shall I pick up?]
And Copy the RSA Certificated to the Update-SuperSU.v1.65 folder (delete previous files if exist) [PROBLEM: unable to find any "RSA Certificated" like files once I open ANY apk]
Also, copy the build.prop to the system folder located within Update-SuperSU.v1.65 folder [BLOCKED by previous step]
Locate the update-script file within this folder and edit it using Notepad++ [BLOCKED by previous step]
You need to update the build.prop file after adding the following line at the bottom [BLOCKED by previous step]
persist.service.adb.enable=1
Next step is updating SQLite Database [WHERE would I do this step?]
Which can be done by adding the following code to the update-script file
sqlite3 /data/data/com.android.providers.settings/databases/settings.db "UPDATE global SET value=1 WHERE name='adb_enabled'"
What would I do then? How to actually apply the changes back to the phone?
Does anyone know of better / latest step by step process of enabling / unlocking the device or is my device now completely and unrepairably bricked?
Thank you.
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
jwoegerbauer said:
https://gist.github.com/varhub/7b9555cdd1e5ad785ffde2300fcfd0bd
Click to expand...
Click to collapse
For a while (since when, I don't know) persistent properties are not shared as individual files in /data/property.
They are all packed inside /data/property/persistent_properties.
Try setprop instead.
jwoegerbauer said:
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Click to expand...
Click to collapse
will give it a go. thank you.
jwoegerbauer said:
Android - Enable ADB from recovery
Android - Enable ADB from recovery. GitHub Gist: instantly share code, notes, and snippets.
gist.github.com
Click to expand...
Click to collapse
I've tried the steps but I'm crashing on sending any commands to the device. While I'm in the recovery, I see the following details and options:
```
Android Recovery
google/blueline/blueline
12/SP1A.210812.016.B2/8602260
user/release-keys
Use volume up/down and power
Warning: Previous installation has failed. Your device may fail to boot if you reboot or power off now
- Reboot system now
- Reboot to bootloader
- Enter Fastboot
- Apply Update from ADB
- Apply update from SD card
- Wipe data/factory reset
- Mount /system
- View recovery logs
- Run Graphics Test
- Run Locale Test
- Power Off
```
where I run the adb command:
`adb shell mount data` I get the `adb.exe: no devices/emulators found`.
when I go to the `Apply update from ADB` and run the command above I get `error: closed`.
Basically I'm unable to run any adb commands as of the first message, and the only place I can it's from within the update. I've noticed that while in the 'Update via ADB', then in the Win Device Manager I can see that the driver is changed to `Android Composite ADB Interface` and only now it's accepting very limited commands. `adb devices` command generates: `<device id number>: sideload`.
When in the fastboot, it switches to `Android Bootloader Interface` in the DEvice manager.
When in recovery, the device is disconnected from the computer. (is not listed in the device manager)
any thoughts. thanks
Note: that phone was never rooted.
Bootloader looks like this at the moment:
```
Fastboot Mode
Product revision: blueline MP1.0(ROW)
Bootloader version: b1c1-0.4-7617406
Basebandversion...
serial number:
secure booth: PRODUCTION
NOS Production: yes
DRAM: 4GB
Device State: Locked
Boot slot: a
```
vajnorcan said:
I've tried the steps but I'm crashing on sending any commands to the device. While I'm in the recovery, I see the following details and options:
```
Android Recovery
google/blueline/blueline
12/SP1A.210812.016.B2/8602260
user/release-keys
Use volume up/down and power
Warning: Previous installation has failed. Your device may fail to boot if you reboot or power off now
- Reboot system now
- Reboot to bootloader
- Enter Fastboot
- Apply Update from ADB
- Apply update from SD card
- Wipe data/factory reset
- Mount /system
- View recovery logs
- Run Graphics Test
- Run Locale Test
- Power Off
```
where I run the adb command:
`adb shell mount data` I get the `adb.exe: no devices/emulators found`.
when I go to the `Apply update from ADB` and run the command above I get `error: closed`.
Basically I'm unable to run any adb commands as of the first message, and the only place I can it's from within the update. I've noticed that while in the 'Update via ADB', then in the Win Device Manager I can see that the driver is changed to `Android Composite ADB Interface` and only now it's accepting very limited commands. `adb devices` command generates: `<device id number>: sideload`.
When in the fastboot, it switches to `Android Bootloader Interface` in the DEvice manager.
When in recovery, the device is disconnected from the computer. (is not listed in the device manager)
any thoughts. thanks
Note: that phone was never rooted.
Bootloader looks like this at the moment:
```
Fastboot Mode
Product revision: blueline MP1.0(ROW)
Bootloader version: b1c1-0.4-7617406
Basebandversion...
serial number:
secure booth: PRODUCTION
NOS Production: yes
DRAM: 4GB
Device State: Locked
Boot slot: a
```
Click to expand...
Click to collapse
On my pixel3, /dev/block/dm-4 is mounted to /data. Try "adb shell mount /dev/block/dm-4 /data".
The instructions you are following are very old, and likely obsolete. SuperSu is also obsolete. Try to find a newer method.
dcarvil said:
On my pixel3, /dev/block/dm-4 is mounted to /data. Try "adb shell mount /dev/block/dm-4 /data".
The instructions you are following are very old, and likely obsolete. SuperSu is also obsolete. Try to find a newer method.
Click to expand...
Click to collapse
the issue is I'm unable to run that command `adb shell mount...` with the `no devices/emulator found` message. I believe it's because the device is not even listed in the device manager (windows) when in recovery mode. When in the update mode, then it's listed in the DM. See my post above, I've updated it few times. Thanks
Btw on that link if you check the posts there are newer ones (1.5y back) claiming it works so might actually work
If you're unable to sideload the OTA via PC, I don't think there's any other option besides paying for a repair, or replacing the device. A locked bootloader definitely makes recovery a lot harder.
V0latyle said:
If you're unable to sideload the OTA via PC, I don't think there's any other option besides paying for a repair, or replacing the device. A locked bootloader definitely makes recovery a lot harder.
Click to expand...
Click to collapse
I'm able to sideload the OTA, but restart goes into start being stuck and back and forth but never gets any further than the first google load screen
vajnorcan said:
I'm able to sideload the OTA, but restart goes into start being stuck and back and forth but never gets any further than the first google load screen
Click to expand...
Click to collapse
Were you using adb/fastboot before this happened? Was the device recognised then? If not, are you sure you have the right drivers?
AlexKarimov said:
Were you using adb/fastboot before this happened? Was the device recognised then? If not, are you sure you have the right drivers?
Click to expand...
Click to collapse
I've used the adb to upload the ota and that went, according the message ok, but the system won't start up. Device is recognized only when I choose the "Apply update from ADB" option in recovery mode. The moment I choose it, it shows up as a device in device manager and "adb devices" lists it ok. In fastboot mode it does list it in device manager, but "adb devices" doesn't list it.
It's the latest driver
vajnorcan said:
I've used the adb to upload the ota and that went, according the message ok, but the system won't start up. Device is recognized only when I choose the "Apply update from ADB" option in recovery mode. The moment I choose it, it shows up as a device in device manager and "adb devices" lists it ok. In fastboot mode it does list it in device manager, but "adb devices" doesn't list it.
It's the latest driver
Click to expand...
Click to collapse
If I understand correctly, you're using "adb devices" when in fastboot mode? You need to use "fastboot devices". If that works and lists the phone then you may be able to use the flash tool on the Google website
AlexKarimov said:
If I understand correctly, you're using "adb devices" when in fastboot mode? You need to use "fastboot devices". If that works and lists the phone then you may be able to use the flash tool on the Google website
Click to expand...
Click to collapse
This requires OEM Unlocking to be enabled so it won't be much help here.
Rescue Mode might work though.
@vajnorcan try this:
Boot to bootloader and select Rescue Mode using the volume buttons, then press Power to enter it.
On your PC, go to pixelrepair.withgoogle.com and connect the USB cable to your device. Select your carrier or select "Other" if device is unlocked.
I don't know whether this will actually work...I haven't heard of anyone using this tool to successfully recover.
AlexKarimov said:
If I understand correctly, you're using "adb devices" when in fastboot mode? You need to use "fastboot devices". If that works and lists the phone then you may be able to use the flash tool on the Google website
Click to expand...
Click to collapse
'fastboot devices' is reading the device, which is good. but trying the online flash tool fails due to the device being locked. :/
V0latyle said:
This requires OEM Unlocking to be enabled so it won't be much help here.
Rescue Mode might work though.
@vajnorcan try this:
Boot to bootloader and select Rescue Mode using the volume buttons, then press Power to enter it.
On your PC, go to pixelrepair.withgoogle.com and connect the USB cable to your device. Select your carrier or select "Other" if device is unlocked.
I don't know whether this will actually work...I haven't heard of anyone using this tool to successfully recover.
Click to expand...
Click to collapse
The google tool has found and connected to the device, but it ends up in an error (on the device) and saying "disconnected", looked promising, but not for long. thanks.
I tried to sideload June OTA just as normal.
Code:
adb sideload F:\Pixel6a\bluejay-ota-tq3a.230605.010-a67dbf36.zip
serving: 'F:\Pixel6a\bluejay-ota-tq3a.230605.010-a67dbf36.zip' (~0%) adb: failed to read command: No error
that's the output of my terminal after trying to sideload it,.. on the phone nothing happens at all
it says verifying, but nothing about receiving anything and after leaving it for almost 10 minutes still nothing.
So I disconnect it and it says verification failed and it warns me
"Previous installation has failed, Your device may fail to boot if you reboot or power off now."
But it didn't even write anything did it? since it just failed at sending and verifying the ota in the first place.
Can I reboot my phone?
Edit: guess it's true that sideloading the OTA is really as safe as it gets, rebooting to System was no issue.
I just don't get what's wrong... using the same platform tools that I used for March, April and May update, 33.0.3-8952118
I re-downloaded the OTA from google to confirm it wasnt corrupt, same issue.
All my modules were disabled (not that that would stop adb from sending the file).
G5-User7080 said:
I tried to sideload June OTA just as normal.
Code:
adb sideload F:\Pixel6a\bluejay-ota-tq3a.230605.010-a67dbf36.zip
serving: 'F:\Pixel6a\bluejay-ota-tq3a.230605.010-a67dbf36.zip' (~0%) adb: failed to read command: No error
that's the output of my terminal after trying to sideload it,.. on the phone nothing happens at all
it says verifying, but nothing about receiving anything and after leaving it for almost 10 minutes still nothing.
So I disconnect it and it says verification failed and it warns me
"Previous installation has failed, Your device may fail to boot if you reboot or power off now."
But it didn't even write anything did it? since it just failed at sending and verifying the ota in the first place.
Can I reboot my phone?
Edit: guess it's true that sideloading the OTA is really as safe as it gets, rebooting to System was no issue.
I just don't get what's wrong... using the same platform tools that I used for March, April and May update, 33.0.3-8952118
I re-downloaded the OTA from google to confirm it wasnt corrupt, same issue.
All my modules were disabled (not that that would stop adb from sending the file).
Click to expand...
Click to collapse
Yeah, when sideloading an OTA (or updating via Settings) it puts the new version of the OS on the inactive slot. If something goes wrong with the update you'll still have your current slot to fallback on (like in your case).
Maybe try different cables/ports.
You can update through recovery if necessary; download the OTA to your device, reboot to recovery, and select Apply update from SD card.
V0latyle said:
You can update through recovery if necessary; download the OTA to your device, reboot to recovery, and select Apply update from SD card.
Click to expand...
Click to collapse
oh I remember seeing that option, does that mean I need to put the ota.zip in /sdcard/ ?
in essence that would circumvent adb sending issues / cable issues, I suppose?
G5-User7080 said:
oh I remember seeing that option, does that mean I need to put the ota.zip in /sdcard/ ?
in essence that would circumvent adb sending issues / cable issues, I suppose?
Click to expand...
Click to collapse
Yes. You don't need to use a PC at all. You can either download the OTA directly through your phone's browser, or if you want, you can use a USB cable to transfer the OTA file to your phone's storage. It doesn't matter where you put it; if you download it on your phone, it'll be in /sdcard/Downloads, if you use a USB cable you'll see the contents of /sdcard pop up as a USB drive in your computer.
V0latyle said:
Yes. You don't need to use a PC at all. You can either download the OTA directly through your phone's browser, or if you want, you can use a USB cable to transfer the OTA file to your phone's storage. It doesn't matter where you put it; if you download it on your phone, it'll be in /sdcard/Downloads, if you use a USB cable you'll see the contents of /sdcard pop up as a USB drive in your computer.
Click to expand...
Click to collapse
oki, I tried Pixelflasher first and interestingly it just worked.. same cable, same port, same adb, same everything
mhhhh.... using windows terminal wouldnt be the issue would it?
anyway, happy it works, but also frustrated I couldnt figure out why it refused to work typing the adb commands manually totally out of the blue
G5-User7080 said:
oki, I tried Pixelflasher first and interestingly it just worked.. same cable, same port, same adb, same everything
mhhhh.... using windows terminal wouldnt be the issue would it?
anyway, happy it works, but also frustrated I couldnt figure out why it refused to work typing the adb commands manually totally out of the blue
Click to expand...
Click to collapse
Were you using PowerShell or Command Prompt?
What were you doing on the phone?
There's two ways to get into sideload mode:
Manual way:
Manually enter recovery
Select Apply update from ADB
ADB way:
While in Android or recovery, issue the following command to your phone via ADB: adb reboot sideload
Either way, the device should read "Now send the package you want to apply to the device with "adb sideload <filename>"...
V0latyle said:
Were you using PowerShell or Command Prompt?
What were you doing on the phone?
There's two ways to get into sideload mode:
Manual way:
Manually enter recovery
Select Apply update from ADB
ADB way:
While in Android or recovery, issue the following command to your phone via ADB: adb reboot sideload
Either way, the device should read "Now send the package you want to apply to the device with "adb sideload <filename>"...
Click to expand...
Click to collapse
just windows 11 terminal, that should be powershell by default, dont think I've used anything else before tho
on the phone?
like nothing, I did it the way I asked you a few months back, the same I've done for the past 3 OTAs, disable modules, adb reboot sideload, followed by adb sideload <drag ota here>.
then the percentage didnt go up in terminal it said what I posted in OP
the phone only showed "verifying stuff", after like 8 mins I disconnected the phone and it showed like 100 lines of "failed to verify xxx" and then went back to fastbootd
i dont think the phone ever actually received the actual ota file.
it did read "now send the package..." then I did adb sideload ota-xyzyadayada.zip and thats what happened.
G5-User7080 said:
just windows 11 terminal, that should be powershell by default, dont think I've used anything else before tho
on the phone?
like nothing, I did it the way I asked you a few months back, the same I've done for the past 3 OTAs, disable modules, adb reboot sideload, followed by adb sideload <drag ota here>.
then the percentage didnt go up in terminal it said what I posted in OP
the phone only showed "verifying stuff", after like 8 mins I disconnected the phone and it showed like 100 lines of "failed to verify xxx" and then went back to fastbootd
i dont think the phone ever actually received the actual ota file.
it did read "now send the package..." then I did adb sideload ota-xyzyadayada.zip and thats what happened.
Click to expand...
Click to collapse
Odd, and Pixel Flasher worked - did you sideload or did you flash the factory image?
V0latyle said:
Odd, and Pixel Flasher worked - did you sideload or did you flash the factory image?
Click to expand...
Click to collapse
used PF's new "Full OTA" option, so sideload