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
Related
My tablet has been hideously slow for the past 6 months or so. I've flash 15 or 20 different ROMs of various kinds, I always wipe factory reset and what not, but it remains slow. No matter what I do, after about 6 hours with the tablet on, it will slow down to a crawl then eventually crash.
Anyway I tried to wipe everything off my tablet. I completely wiped data and deleted every file off the internal sd. I figured just maybe it would help.
I was going to use ADB sideload to get stuff back on....but it just isn't working!
Is there some reason why ADB sideload doesn't work with TF300T and TWRP 2.4.4.0?
I am in TWRP in sideload mode with usb connected to computer, on my computer in the ADB command line when I type "ADB devices" I get:
012345689ABCDEF sideload
but when I try to actually use sideload "adb sideload rom.zip" I get "cannot read 'sideload'"
ADB push isnt' working either.
Neither is fastboot flash blob
Any ideas to get some rom back on my tablet?
having this problem too
zaner123 said:
My tablet has been hideously slow for the past 6 months or so. I've flash 15 or 20 different ROMs of various kinds, I always wipe factory reset and what not, but it remains slow. No matter what I do, after about 6 hours with the tablet on, it will slow down to a crawl then eventually crash.
Anyway I tried to wipe everything off my tablet. I completely wiped data and deleted every file off the internal sd. I figured just maybe it would help.
I was going to use ADB sideload to get stuff back on....but it just isn't working!
Is there some reason why ADB sideload doesn't work with TF300T and TWRP 2.4.4.0?
I am in TWRP in sideload mode with usb connected to computer, on my computer in the ADB command line when I type "ADB devices" I get:
012345689ABCDEF sideload
but when I try to actually use sideload "adb sideload rom.zip" I get "cannot read 'sideload'"
ADB push isnt' working either.
Neither is fastboot flash blob
Any ideas to get some rom back on my tablet?
Click to expand...
Click to collapse
You have probably already read and tried this but if not may give you an answer to using sideload.
How to Use Sideload
[FONT=ArialMT, sans-serif]1. Have a recovery installed on your device that supports ADB sideload like[/FONT][FONT=ArialMT, sans-serif] TWRP 2.3 or higher[/FONT]
[FONT=ArialMT, sans-serif]2. Have newer ADB binaries installed on your computer. If it's been a while since[/FONT][FONT=ArialMT, sans-serif] you installed ADB on your computer, you may need to get the latest ADB binaries in platform tools from the Android SDK. You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line.[/FONT]
[FONT=ArialMT, sans-serif]3. Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then[/FONT][FONT=ArialMT, sans-serif] ADB Sideload.[/FONT]
[FONT=ArialMT, sans-serif]4. From the command line, type adb sideload /path/to/rom.zip (rom.zip location on pc)[/FONT][FONT=ArialMT, sans-serif]. The file will be copied to the path you have mounted. (internal or external sdcard).[/FONT]
I made the two things blue that previously kept me from using sideload.
My nexus 7 (2013) just did the stuck on X during start up thing. I have a bunch of photos from my vacation on it that I would like not to lose.
I've been reading up on adb and so far have installed the SDK and toolkit. My PC recognizes that my nexus is attached when I put it into adb sideload mode.
But I'm too new to know where to go from there. There is a lot out there about using the sideloader to do various things but haven't found anything that would help me so far.
Can I somehow use an adb backup command if install a zip file with the proper commands?
Is there a way to reinstall the OS via adb sideload to get the nexus running again without wiping the internal storage?
There have been some methods mentioned that involve have USB debugging enabled or the bootloader unlocked.
But I don't have USB debugging enabled and my bootloader is locked. I couldn't find a way to enable USB debugging without the nexus being able to start up. It looks like unlocking the bootloader requires a factory reset.
You can try to use adb to get your pictures. It's located in %sdk_folder%/platform-tools.
Simply use this command to get your files
Code:
adb pull /sdcard/Pictures /destination_folder
You can also push files to your sdcard while using the push command. I would try this to push a backup to the sdcard.
Are you able to get in recovery mode (CWM etc.)?
lective renzak
Most adb commands gives me "error:closed"
adb devices gives <serial number> sideload
I can upload a zip file via sideload. I just uploaded a zip file with an empty text document. It gave me an error that the update package failed which was expected.
I know nothing about update packages.
Is there one I could install that would get the nexus working without wiping out my pictures?
I was able to install an OTA update over the adb sideloader. So at least something is working.
I was hoping that installing the update would fix things but the nexus still gets stuck on X when starting up.
I'm wondering if I can insert something into the update installer script to do a backup or pull....
There is an install-recovery.sh script that I could potentially edit and then back up.
I there a command I could put into it that would do something equivalent to an adb pull or backup?
If anyone could give me a place to start, I'd really appreciate it.
I am in the same situation as you I have found nothing and only your posts on other forums!
If you have the stock configuration with usb debugging off and the bootloader locked, you're stuck. At least I couldn't figure out anything after many hours and weeks of asking. Had to bite the bullet and do a wipe. I rooted it when I did the wipe so I could try various recovery tools.
I tried dr fone and hexamob recovery and some other ones but no luck.
The nexus toolkit helped me out a bunch to try out adb commands and install a rooted system.
Sorry I don't have better news.
For backup services, I think shutterfly gives you unlimited photo only backups. For others you can do a combination of google drive, dropbox, amazon, etc. Amazon has some special thing for music I believe.
do u have the link for OTA zip file
AM struck at the same point with my Samsung note 3 . i need the link for ota update so that i can update my OS using ADB sideload . i tried downloading a zip file from sammobile but its gives me an error
E: footer is wrong
E: signature verification failed
i don't know what else i can do .
i tried DR fone i shows my pictures but never completes the backup process and shuts down.
plz help guys
What's your problem with the note 3? Solution likely different than my nexus issue. The Samsung phones do have a power button issue. Either doesn't work or gets stuck in the pressed position so when you try to start it continues to restart. If that's the case try fiddling around with power button. I find it helpful to pull the phone apart so I can get at the actual button.
i checked the power button is fine because it say up in recovery mode but keeps restarting in safe mode or normal mode. i need to either backup my data on the device using the recovery mode or update my device so that i can fix the corrupted OS. but when i try to do a OTA update using adb sideload and a zip file that i downloaded from sammobile it gives me this error :
E: footer is wrong
E: signature verification failed
. or just help me to backup my pictures using the recovery so that i can just do a factory reset any help would be appreciated. Thanks
Haha, got the same problems. But I do have USB Debugging on - does not help anything. Crazy, if you consider that files are there but you have to delete them in order to correct the stubbornness of the OEMs....
I want to start off saying that I'm a complete noob to this and I now realize I was stupid for biting of waaay more than I can chew.
I turned s-off and rooted using firewater exploit. I installed ViperOne with TWRP and all was well, until I decided I wanted to try Android Revolution HD (here) I stupidly decided that in addition to wiping the normal stuff, I would just format. I backed up to my pc just by copying everything into a folder (downloads, pictures, etc) and I wiped it. Now I've got the ROM on my computer and I'm trying to put it on the phone. I've tried using adb sideloader, and adb push but neither are working (I'm fairly certain I typed everything in correctly in cmd.)
How can I install ANY rom so that I can download with the phone and install from TWRP without formatting?
you've booted into recovery, and you're unable to adb push the rom.zip to your internal storage?
adb push romname.zip /media/data/0
jova33 said:
you've booted into recovery, and you're unable to adb push the rom.zip to your internal storage?
adb push romname.zip /media/data/0
Click to expand...
Click to collapse
Yes when I type that line into the cmd and press enter, nothing happens. No feedback at all, it just moves the cursor to the next line. I do have the rom in the same directory as adb and I did type it correctly into cmd. I attached an image of what it looks like.
>EDIT: spoke too soon. After nothing happened for a few minutes the cmd said "protocol failure"
chobungus said:
Yes when I type that line into the cmd and press enter, nothing happens. No feedback at all, it just moves the cursor to the next line. I do have the rom in the same directory as adb and I did type it correctly into cmd. I attached an image of what it looks like.
>EDIT: spoke too soon. After nothing happened for a few minutes the cmd said "protocol failure"
Click to expand...
Click to collapse
You probably didn't have USB debugging enabled, do you have access to a micro SD card?
If you do, load the rom onto that and flash from there.
Sent from my HTC6525LVW using Tapatalk
Well I was able to get it working, but as usual, I don't really know how. I redownloaded adb and the rom and restarted my computer. Tried the exact same sideload command and it worked.
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.
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.