Database Info

Cannot root magic

Hello,
When I do this command I see the device in the list:
adb devices.
The the next step is to go in fastboot, witch I do with BACK button + POWER on. The fastboot mode is on, but I couldn't see the device anymore. So the next command doesn't work at all:
fastboot boot recovery-new.img
Do I have to put on the phone again, because that is not written in the manual.
Greetz,
Dries

Droned said:
Hello,
When I do this command I see the device in the list:
adb devices.
The the next step is to go in fastboot, witch I do with BACK button + POWER on. The fastboot mode is on, but I couldn't see the device anymore. So the next command doesn't work at all:
fastboot boot recovery-new.img
Do I have to put on the phone again, because that is not written in the manual.
Greetz,
Dries
Click to expand...
Click to collapse
Windows vista for example tries to install the incorrect drivers. Adb drivers are not recognized for it in fastboot mode, or will install different drivers.
Use usbdeview to delete all the HTC or android drivers. Go into fastboot mode connect phone, manually install your drivers from the sdk/tools/usb drivers folders. Boot the recovery, backup, then flash the recover. Feel free to PM and I will try to help.

when your in fastboot its
fastboot devices rather than adb devices
make sure your phone is connected and in fastboot mode
as well as make sure it reads
"fastboot USB"

minogue has the correct information listed for you (assuming that you have the USB drivers installed for "fastboot" mode as well.
I had the exact same problem as you, but after typing in "fastboot devices"... bingo, there it was.

OK, I went in the control panel of vista and delete the device, plugged in the phone and installed the correct drivers and it works.
Thanks

Droned said:
OK, I went in the control panel of vista and delete the device, plugged in the phone and installed the correct drivers and it works.
Thanks
Click to expand...
Click to collapse
Sounds like I was correct.

How do you know when its rooted? ive got 2 partitions (Fat32 and Ext2) i can seee them in paragon partition manager but when i look on sd settings on my g2 it says under secondary storage unknown?

bonesy said:
How do you know when its rooted? ive got 2 partitions (Fat32 and Ext2) i can seee them in paragon partition manager but when i look on sd settings on my g2 it says under secondary storage unknown?
Click to expand...
Click to collapse
Terminal immulator type $ su
if it changes to # you have root.
Also, adb shell, # you have root.

Brilliant thanks. So what abiout it not showing on my phone? Says "SD Secondary storage" But under says unknown?

[Q] ADB error device not found OSX

Alright, I know this is a known issue and I've read every thread detailing people saying they have this issue but none that have it solved so I'm posting it here since we have some pretty smart guys browsing our forums and I'm hoping one of them can help.
Here is the problem: My 2010 MacBook Pro will recognize my phone as a USB drive but whenever I try to run ADB commands I get "Error device not found". I've tried both USB ports on the machine and with both the computer knows the Nexus S is plugged in (I checked the System Information and it lists the Nexus S, exactly like that, as plugged into a USB port) but it won't recognize it. In the past I've used an older MacBook which could recognize the phone but that is no longer an option. I've tried uninstalling and reinstalling the SDK a few times but never to any avail. Any help would be greatly appreciated.

Forgive me for asking the obvious, but do you have USB Debugging enabled?

distortedloop said:
Forgive me for asking the obvious, but do you have USB Debugging enabled?
Click to expand...
Click to collapse
Absolutely forgiven, I should have stated in the OP that I do in fact have USB debugging enabled.

Had to ask, just to be sure.
Does fastboot work with it (ie, boot to fastboot on the phone and try a fastboot devices command)?

distortedloop said:
Had to ask, just to be sure.
Does fastboot work with it (ie, boot to fastboot on the phone and try a fastboot devices command)?
Click to expand...
Click to collapse
I haven't been able to get any commands to work because once I start the ADB shell I get the device not found error. I could try a different command if you told me what to try

Kill the adb server in your terminal shell:
Code:
adb kill-server
Then try again:
Code:
adb devices
If no joy with that, reboot the phone to fastboot (power off, then press/hold vol+up and then press power on).
Once in fastboot, plug the phone into the Mac USB port, then from the command line in terminal:
Code:
fastboot devices
or might have to be
Code:
./fastboot devices
Not sure what that will tell us, but it would be interesting to know. edit: actually this will tell us if it's a driver type problem or just an adb problem.
FYI - on my MBP the Nexus S shows up as you describe in device manager, so you seem normal in that regard.

distortedloop said:
Kill the adb server in your terminal shell:
Code:
adb kill-server
Then try again:
Code:
adb devices
If no joy with that, reboot the phone to fastboot (power off, then press/hold vol+up and then press power on).
Once in fastboot, plug the phone into the Mac USB port, then from the command line in terminal:
Code:
fastboot devices
or might have to be
Code:
./fastboot devices
Not sure what that will tell us, but it would be interesting to know. edit: actually this will tell us if it's a driver type problem or just an adb problem.
FYI - on my MBP the Nexus S shows up as you describe in device manager, so you seem normal in that regard.
Click to expand...
Click to collapse
Okay, so there were no devices listed for the abd devices and I'm not sure what to preface the fastboot command with since I can't seem to find that in my sdk folder...perhaps I should try reinstalling it again? I know on my windows partition there is a file called fastboot but I've never seen the one for mac

kenvan19 said:
Okay, so there were no devices listed for the abd devices and I'm not sure what to preface the fastboot command with since I can't seem to find that in my sdk folder...perhaps I should try reinstalling it again? I know on my windows partition there is a file called fastboot but I've never seen the one for mac
Click to expand...
Click to collapse
Try the files in this archive attached. Change your working directory in terminal to the one you put them in, doesn't matter what it is. You'll have to use the ./ in front of the commands (./fastboot or ./adb).

Also, have you tried a clean power off and total reboot of the MacBook Pro? Just a shot in the dark with that one, but maybe clean out some memory or something that's screwing you up.

distortedloop said:
Try the files in this archive attached. Change your working directory in terminal to the one you put them in, doesn't matter what it is. You'll have to use the ./ in front of the commands (./fastboot or ./adb).
Click to expand...
Click to collapse
Giving it a shot now
distortedloop said:
Also, have you tried a clean power off and total reboot of the MacBook Pro? Just a shot in the dark with that one, but maybe clean out some memory or something that's screwing you up.
Click to expand...
Click to collapse
I've been booting between Windows and Mac OSX all day trying to get this to work so I've rebooted several times only to have the same issue.

Fastboot devices gave me this output:
serial# fastboot

kenvan19 said:
Fastboot devices gave me this output:
serial# fastboot
Click to expand...
Click to collapse
Glad you noticed that long number was your serial and changed it.
Okay, this tells us that there is nothing wrong with the Mac talking to the phone. That's good news in a way.
I noticed in the Dev section you were asking about this same issue in regards to regaining root.
It seems to me that at this point, with that being your primary concern, you should just use the fastboot mode to fastboot flash recovery clockwork.img or fastboot boot instead of flash. Then you can use clockwork to install the su zip file.
We can worry about getting adb working later on.

distortedloop said:
Glad you noticed that long number was your serial and changed it.
Okay, this tells us that there is nothing wrong with the Mac talking to the phone. That's good news in a way.
I noticed in the Dev section you were asking about this same issue in regards to regaining root.
It seems to me that at this point, with that being your primary concern, you should just use the fastboot mode to fastboot flash recovery clockwork.img or fastboot boot instead of flash. Then you can use clockwork to install the su zip file.
We can worry about getting adb working later on.
Click to expand...
Click to collapse
=O You rule! I was able to fastboot the recovery image and reapply root. Distortedloop you're a ****ing god. I apologize for the profanity but thank you. Thank you. Thank you.

kenvan19 said:
=O You rule! I was able to fastboot the recovery image and reapply root. Distortedloop you're a ****ing god. I apologize for the profanity but thank you. Thank you. Thank you.
Click to expand...
Click to collapse
Great. Glad you're running root again.
Try adb with the file I posted earlier. Also, try cycling the USB debugging a couple of times for good measure.

distortedloop said:
Great. Glad you're running root again.
Try adb with the file I posted earlier. Also, try cycling the USB debugging a couple of times for good measure.
Click to expand...
Click to collapse
Will do both. Again, thank you so much...not being rooted was killing me hehe

kenvan19 said:
My 2010 MacBook Pro will recognize my phone as a USB drive but whenever I try to run ADB commands I get "Error device not found".
Click to expand...
Click to collapse
Hi, I fixed this by installing the Android File Transfer application on the mac. Of course, I had to do the 7 taps on the build number so that I could get to the development settings on the nexus and turn usb debugging on. Also, I had to restart the adb server (adb kill-server; adb start-server).
Occasionally the adb server won't die on a 'kill-server' and I have to kill it manually from the terminal (ps axu |grep adb to find the PID first).

Ahhh wow I've been googling this problem - exact same situation. Now... this might sound ludicrous, but someone asked you if you had enabled USB debugging. Every time I read that bit of advice I was like 'well duh, of course I did, I went and clicked Build number 7 times and became a super rad developer'.
... in short, I made the rather hasty mistake of assuming that enabling the developer options was the same thing as enabling USB debugging. Now ADB is behaving nicely. So - on the off chance you made this same mistake - after enabling developer mode, did you find the now unhidden developer menu and enable USB debugging from there? (please don't flame!) ha ha good luck

[Q] Windows drivers for Nabi2

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.

Fastboot will not detect my device while rooting

I've been trying for the past couple of days to root my Oneplus One. I started with this tutorial: (http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471) which is featured in the FAQ (which I've read through) and I've gotten stuck at one location.
You can test fastboot by connecting your device to your PC while booted into fastboot mode (power + volume up) and issuing this command:
Code:
fastboot devices
It should return your device serial number, if so, fastboot is working.
Click to expand...
Click to collapse
The ADB command appears to be working, but when I boot into fastboot mode (and when I'm not in it as well), the PC does not detect the phone. I've tried connecting it to multiple USB ports, and I'm using the official Oneplus One cable, so I'm at a bit of a loss of what to do.
However, I feel like I've identified where the source of the error is. If you see here: (http://i.imgur.com/IE1Bxjs.png), you can see that the phone is being detected under Portable Devices. In all of the tutorials I've looked through so far, it's been detected under something like "Android Phone" or "ADB Interface". I've tried various things to fix this, the most common of which is installing drivers onto/for the phone. I've tried the one here: (http://forum.xda-developers.com/showthread.php?t=1413293), which I know is for Archos phones, but should work similarly, as I tried both the Universal ADB driver and the Google one, from the SDK Manager. I kept getting an error telling me that: "the folder you specified doesn't contain a compatible software driver for your device."
I've also tried the one here: (http://www.makeuseof.com/tag/android-wont-connect-windows-adb-fix-it-three-steps/) (let me know if external links aren't allowed and I'll remove it.) This doesn't seem to work either, as I get this error (http://i.imgur.com/CLATXsl.png) when it tells me to:
If you cannot get any driver to work, you will need to force installation. Instead of choosing “Let me pick from a list of device drivers on my computer” in the previous step, you will choose “Browse for driver software on your computer” and manually find the directory where you installed Koush’s drivers.
The location on your hard drive looks something like this:
C:\Program Files (x86)\ClockworkMod\Universal Adb Drivers\
Windows will then install the drivers. From now on, whenever you connect the Android device with debugging enabled, Koush’s drivers will load in place of the ones that failed to work.
Click to expand...
Click to collapse
And now I'm posting here, praying that someone will have some sort of idea what to do. Any help at all would be greatly appreciated,
Fappled
EDIT: Managed to get it working, messing around with the drivers in device manager while in Fastboot mode seemed to work.

Fappled said:
The ADB command appears to be working
Click to expand...
Click to collapse
Feel your pain, I've been thru some pain myself with some weird issue, posted here yesterday. Though, my issue is different from yours, I have some ideas for you.
You say that adb works, so I assume your usb cable & PC are OK here.
I aslo assume that your Device Manager screenshots taken when connected to your phone in device mode (rom running). Don't worry about what you see in Device Manager just yet. Your goal is to make fastboot work, right. Note: Adb works in recovery mode and device mode, but not in fastboot mode. Fastboot works only in fastboot mode.
You could try this, put your phone in fastboot mode, then connect to your PC. Now, see what in your Device Manager. In my case, the phone is under Android Device>Android Bootloader Interface and I use Google driver. Then, try "fastboot devices" to see if your phone is detected.
If not, play with the driver in Device Manager (uninstall, rescan, install another). No need to unplug the phone. After the driver changed, see your Device Manager changed, and then try "fastboot devices".
I played with the driver changing a few time and got fastboot to work. I hope you get it to work too.

Enable USB Debugging in Recovery Mode

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.