Develop Bugs

SD/System/Data all wiped. ADB is not reading my device HELP

so as stated i accidentally wiped my sd card while trying to install a rom. Everything was erased. ADB is setup although i get error device not found. My phone can go into CWR and i have tried mounting/unmounting system and than when i go to mount sd card it doesnt change to unmount... so not sure whats going on... PLEASE HELP
On a Verizon LTE

Ghxoxst said:
so as stated i accidentally wiped my sd card while trying to install a rom. Everything was erased. ADB is setup although i get error device not found. My phone can go into CWR and i have tried mounting/unmounting system and than when i go to mount sd card it doesnt change to unmount... so not sure whats going on... PLEASE HELP
On a Verizon LTE
Click to expand...
Click to collapse
- open windows device manager
- boot into CWM (it provides the ADB interface) and connect USB cable
- you should see your device being added to the list in device manager
- make sure you have the correct ADB driver installed, update if needed (use the naked driver v0.7: http://forum.xda-developers.com/showthread.php?t=1379875)
- push a ROM to /sdcard using adb push
- flash ROM via CWM

Petrovski80 said:
- open windows device manager
- boot into CWM (it provides the ADB interface) and connect USB cable
- you should see your device being added to the list in device manager
- make sure you have the correct ADB driver installed, update if needed (use the naked driver v0.7: http://forum.xda-developers.com/showthread.php?t=1379875)
- push a ROM to /sdcard using adb push
- flash ROM via CWM
Click to expand...
Click to collapse
Thank you for your reply
under device manager i do see my gnex but it has a yellow exclamation mark. i have deleted it and when i go to browse for the driver (the naked driver) i cannot find it under downloads...? so no driver is installed...

[please note I don't use an english windows version, I freely translated things, so don't expect to find exactly the mentioned caption on things in your Window]
first of all, don't worry, just did that 5 minutes ago
- Get the drivers (verizon version) for the galaxy nexus from the samsung website
- boot to recovery mode, go to device manager, select update driver - search for drivers on computer - select from a list of drivers on the computer, then select SAMSUNG Android Phone, then the latest one (just check their date) from the ADB drivers, ignore the warning that the driver maybe won't match - it does. That's it, now ADB will work.
Then in recovery do something like adb push myupdate.zip /sdcard/ to get somethinf on your SD card.
Edit:
link to driver download:
http://www.samsung.com/us/support/owners/product/SCH-I515MSAVZW then go to manuals & downloads -> software

Ghxoxst said:
Thank you for your reply
under device manager i do see my gnex but it has a yellow exclamation mark. i have deleted it and when i go to browse for the driver (the naked driver) i cannot find it under downloads...? so no driver is installed...
Click to expand...
Click to collapse
The yellow exclamation mark is the reason why ADB doesn't see your device. As for the driver, it is attached to the post I linked to. Download & unzip, then update the driver.

Petrovski80 said:
The yellow exclamation mark is the reason why ADB doesn't see your device. As for the driver, it is attached to the post I linked to. Download & unzip, then update the driver.
Click to expand...
Click to collapse
I got the drivers installed and adb now recognizes my device. I have gone into the Android folder all the way into the platform-tools subfolder where the actual rom zip i am trying to push is at. I opened cmd prompt and typed in "adb push romname.zip /sdcard/" which it then pushed onto my phone im assuming because it told me the data total and transfer rate /s.
Although now when i go to CWR i and go to INSTALL ZIP FROM SD CARD > CHOOSE ZIP FROM SD CARD it tells me there are no files found ?

its as if its not letting me mount the SDCARD, even when i go to hit the mount sd card on CWR it doesnt change it to unmount...? man im lost

do this:
a) either try
Code:
adb push rom.zip /data/media
b) or
- in recovery, go to install from sdcard, choose from sdcard;
- connect device (adb server should already have been started);
- push file again, either to /sdcard/, or /data/media/
- back out of "choose from sdcard" screen, and enter it again. the file you just transfered will be there.
i use the b) method when a) is not working, somehow it works.
note: you dont need to explicitly mount /sdcard. adb has full access to your device while on a custom recovery.
sent from my i9250

thanks to all whom chimed in and helped me out.
Option A) got it done, i guess the /data/media pushed it through. i see it in CWR now. Thanks a alot, i thought i was gonna have to go ODIN on my Nex.
THANK YOU GUYS. man, another android saved LOL THANK YOU
bk201doesntexist said:
do this:
a) either try
Code:
adb push rom.zip /data/media
b) or
- in recovery, go to install from sdcard, choose from sdcard;
- connect device (adb server should already have been started);
- push file again, either to /sdcard/, or /data/media/
- back out of "choose from sdcard" screen, and enter it again. the file you just transfered will be there.
i use the b) method when a) is not working, somehow it works.
note: you dont need to explicitly mount /sdcard. adb has full access to your device while on a custom recovery.
sent from my i9250
Click to expand...
Click to collapse

Ghxoxst said:
thanks to all whom chimed in and helped me out.
Option A) got it done, i guess the /data/media pushed it through. i see it in CWR now. Thanks a alot, i thought i was gonna have to go ODIN on my Nex.
THANK YOU GUYS. man, another android saved LOL THANK YOU
Click to expand...
Click to collapse
you never have to use odin if you can get into the bootloader.

Petrovski80 said:
- open windows device manager
- boot into CWM (it provides the ADB interface) and connect USB cable
- you should see your device being added to the list in device manager
- make sure you have the correct ADB driver installed, update if needed (use the naked driver v0.7: http://forum.xda-developers.com/showthread.php?t=1379875)
- push a ROM to /sdcard using adb push
- flash ROM via CWM
Click to expand...
Click to collapse
Thanks Petrovski80 ! I had softbricked my GNex and could not transfer anything into it. I was on TWRP. Flashed Clockwork through fastboot and used GNex Toolkit to push files into the phone.
You're a lifesaver !

i dont understand
beekay201 said:
do this:
a) either try
Code:
adb push rom.zip /data/media
b) or
- in recovery, go to install from sdcard, choose from sdcard;
- connect device (adb server should already have been started);
- push file again, either to /sdcard/, or /data/media/
- back out of "choose from sdcard" screen, and enter it again. the file you just transfered will be there.
i use the b) method when a) is not working, somehow it works.
note: you dont need to explicitly mount /sdcard. adb has full access to your device while on a custom recovery.
sent from my i9250
Click to expand...
Click to collapse
im trying to follow these steps you all have posted but im sorry, i dont fully understand how to push a rom or the ADB thing. i am going through the exact same issue stated at the start of this convo.... please help me

maximaspeed said:
im trying to follow these steps you all have posted but im sorry, i dont fully understand how to push a rom or the ADB thing. i am going through the exact same issue stated at the start of this convo.... please help me
Click to expand...
Click to collapse
Don't bump threads over a year old...
Anyways, should be pretty easy for you to understand if you read this.

[Q] accidentally formatted sd after formatting system... can't access to add ROM

Hey guys.
I've been installing roms on my Galaxy Nexus and my Nexus One before that... but today I was talking with my gf while installing a rom and after formatting the system I accidentally formatted the sd card. Now I don't have a ROM on the phone and am unable to access the phone from my mac or a PC to install a ROM... did I just brick this? I have CWM touch recover v6.0.3.1 and going into mount sd doesn't work.
Thanks for any assistance.

pikaia said:
Hey guys.
I've been installing roms on my Galaxy Nexus and my Nexus One before that... but today I was talking with my gf while installing a rom and after formatting the system I accidentally formatted the sd card. Now I don't have a ROM on the phone and am unable to access the phone from my mac or a PC to install a ROM... did I just brick this? I have CWM touch recover v6.0.3.1 and going into mount sd doesn't work.
Thanks for any assistance.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1529058
http://forum.xda-developers.com/showthread.php?t=1812959
10chars

beekay201 said:
http://forum.xda-developers.com/showthread.php?t=1529058
http://forum.xda-developers.com/showthread.php?t=1812959
10chars
Click to expand...
Click to collapse
I've worked through those How-Tos. I've attempted to push in adb and despite the fact that a fastboot devices shows my phone, a push produces the error: device not found
any further input?
Code:
./adb-mac push /Users/Aaron/Desktop/fastboot/ROMS /sdcard/
* daemon not running. starting it now *
* daemon started successfully *
error: device not found

fastboot != adb.

pikaia said:
Code:
./adb-mac push /Users/Aaron/Desktop/fastboot/ROMS /sdcard/
* daemon not running. starting it now *
* daemon started successfully *
[B]error: device not found
[/B]
Click to expand...
Click to collapse
somehow I doubt 'adb devices' outputs your device id. At least in Linux there's a adb parameter that is 'adb start-server'.. which is that "daemon not running, starting it now", and another one that is 'adb devices'..which in your case, comes up "error: device not found".
Check your ADB drivers. CWM had adbd enabled by default, from what I remember.
meet my maguro - ADB style ('adbdev' is just an alias for 'adb devices')
Code:
+6:59% adbdev
List of devices attached
016B*******1B010 device
and fastboot
Code:
+6:59% fastboot devices
016B*******1B010 fastboot
Oh and adb in recovery:
Code:
+7:07% adb shell ls /sdcard/
Alarms Podcasts
Android ROMs
DCIM Ringtones
Download TWRP
MAME4all UPDATE-SuperSU-v1.34.zip
MAME4droid UltimateCustomClockWidget
Movies cm-10.1-20130721-NIGHTLY-maguro.zip
Music gapps-jb-20130615-signed.zip
My Documents tapatalk4
Notifications uccwOutput
Pictures
+7:08% adbdev
List of devices attached
016B*******1B010 recovery

Zepius said:
fastboot != adb.
Click to expand...
Click to collapse
this.
fastboot and adb are not even close to being the same thing....

Pirateghost said:
this.
fastboot and adb are not even close to being the same thing....
Click to expand...
Click to collapse
Ok, clearly I was mistaken. With that said, adb is NOT finding my phone, so is there a way I can push a ROM to my phone using fastboot (which is finding my phone), Or some other feature which I am clearly missing?
I do appreciate the help, despite whatever it might seem I have gone through the help and How-Tos but have been unsuccessful... I'm sure there is something I'm missing... which is why I'm asking.
Thank you again for any assistance.

Are you in recovery when you are trying to connect to adb?
Sent from my Galaxy Nexus

pikaia said:
Ok, clearly I was mistaken. With that said, adb is NOT finding my phone, so is there a way I can push a ROM to my phone using fastboot (which is finding my phone), Or some other feature which I am clearly missing?
I do appreciate the help, despite whatever it might seem I have gone through the help and How-Tos but have been unsuccessful... I'm sure there is something I'm missing... which is why I'm asking.
Thank you again for any assistance.
Click to expand...
Click to collapse
you can flash the stock rom in fastboot very easily.

ADB Sideload Cannot Read Issue, Searched Nothing worked

I am unable to flash anything even official firmware with official recovery, when in adb sideload mode. whenever i try to push a zip to install terminal says:
C:\Users\nd4ios\Desktop>adb sideload a.zip
loading: 'a.zip'
* cannot read 'a.zip' *
the file is named a.zip
it is in the Desktop folder
ive tried doing this like this:
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\Windows\system32>adb sideload C:\Users\nd4ios\Desktop\a.zip
loading: 'C:\Users\nd4ios\Desktop\a.zip'
* cannot read 'C:\Users\nd4ios\Desktop\a.zip' *
C:\Windows\system32>
but same issue
ive tried reinstalling the drivers -(adb, fastboot, and device)-
no avail
ive also tried moving the zip file to the system32 folder and still same error. ive tried multiple zips and nothing.
Ive looked at the ram - practically no ram usage on my pc
ive tried installing twrp recovery but it never can boot into it - just turns to black screen and stays there. (tried multiple different versions of twrp)
ive looked online for help and nothing has helped so far which is why im turning to here.

use this ADB . Yours is old
here
also use TWRP Recovery 3.0.2-1.28 if you are on Oxygen OS Open beta or 4.0 ( N)

it's a windows problem .. a simple restart will solve it ..

not windows probem but probably driver
Go to Computer/Devic manager /Kedacom USB devices or something similar...
change adb driver to ADB generic

thanks, well i was finally able to install the previous firmware via booting and transfering the zip file to the internal storage and installing it from there. so it was a windows problem or driver. im installing this now and hope it fixes it for the future.

I had the same problem with my computer not recognizing my phone with trying to transfer file and flash joints. I went to device manager > right click mtp > update driver software > browse my computer > let me pick > mtp USB device > happy me ??

ok well ive tried using the adb drivers you mentioned and it is still coming up with the same error, so im going to try booting into linux and trying it from there

It's because the ADB executable isn't large address aware and so it fails to allocate memory when you're trying to sideload something big (>1GB) like the OOS 4.0 for our OnePlus 3. You need an ADB that's been made large address aware or you can do it yourself if you have Visual Studio installed on your machine. I'd provide it myself but I've already sworn off posting files here.

i have Visual Studio Enterprise - i got it from being a student, so how would i go about making the adb large address aware? thanks

i found an app online to convert the adb to 64bit and see if that works on it.

ok so what you said is the issue, apparently my adb is not large address aware, as i tried pushing a zip file under a 1GB and it worked but when i push a file over it says it cannot read.

now if only if there was a thanks button so i could add a thank you

ok ive finally got it to work

heres what i did:
i used the original adb.exe in my C:\adb folder
then i right clicked the program and clicked properties and under compatability i chose run as administrator (probably dont need to do this but did it as an extra)
then used https://www.techpowerup.com/forums/threads/large-address-aware.112556/ to convert it to 64bit to allow for long address awareness. and viola it works.
also a side note:
does not work on the minimal adb and fastboot.exe adb program

ADB no longer working

I have the latest Google driver on Windows 10 Pro. I have the latest 29.0.6 platform tools. I open a cmd prompt with admin privileges in platform tools and run "adb devices" and I get an error that I have attached. I have uninstalled and reinstalled Google driver to no avail. I have downloaded the platform tools again to make sure it was not corrupt, that didn't help. Afer I connect to the phone with usb debugging turned on it does not ask me if I want to trust the fingerprint of the computer. Can anyone give me some help? Thank you.

first attempt
Holysmoke99 said:
I have the latest Google driver on Windows 10 Pro. I have the latest 29.0.6 platform tools. I open a cmd prompt with admin privileges in platform tools and run "adb devices" and I get an error that I have attached. I have uninstalled and reinstalled Google driver to no avail. I have downloaded the platform tools again to make sure it was not corrupt, that didn't help. Afer I connect to the phone with usb debugging turned on it does not ask me if I want to trust the fingerprint of the computer. Can anyone give me some help? Thank you.
Click to expand...
Click to collapse
Download the latest:
https://developer.android.com/studio/releases/platform-tools
Unzip in a dir.
Copy following files to test dir:
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
Create one .bat file in the same 'test' dir:
adbreboot.bat:
@Echo off
set PATH=%CD%;%PATH%;
adb reboot
save it .... connect your device ... and run it (if necessary with admin privileges)
Good luck

Thanks for the advice but nothing happened.
I attached the folder contents. That is correct?

second attempt
Holysmoke99 said:
Thanks for the advice but nothing happened.
I attached the folder contents. That is correct?
Click to expand...
Click to collapse
Download and extract:
https://www.uwe-sieber.de/files/devicecleanupcmd.zip
On a windows X64 machine:
copy DeviceCleanupCmd.exe from extracted x64 folder to your previous test folder (with adb.exe, AdbWinApi.dll, etc...)
set the properties of DeviceCleanupCmd.exe for all users to run as administrator
create 2 .bat files:
DeviceCleanupCmdLoad.bat:
@Echo off
set PATH=%CD%;%PATH%;
DeviceCleanupCmd.exe * -t
PAUSE
DeviceCleanupCmdRemove.bat:
@Echo off
set PATH=%CD%;%PATH%;
DeviceCleanupCmd.exe * -s
PAUSE
Run the 2 . bat files (don't connect your device yet !)
Follow the instructions on the messages: ex: 'press any key to close': press any key, etc...
After that:
1. connect your device and run adbreboot.bat... see what happens
2. if no luck, run DeviceCleanupCmdLoad.bat and DeviceCleanupCmdRemove.bat again : REBOOT your windows, connect your device and run adbreboot.bat... see what happens
Good luck

It still did not work. Thanks again.

third attempt
Holysmoke99 said:
It still did not work. Thanks again.
Click to expand...
Click to collapse
- Disconnect USB between PC and device
- On device use "Revoke USB debugging authorizations" in "Developer Options"
- Reboot device
- Reconnect the device to the PC
- You should see now: the fingerprint of the computer ... allow it!
- run adbreboot.bat... see what happens

Thanks again, I have tried to revoke authorizations all day to no avail. I tried all the steps above and added revoking but it still won't give me option to trust fingerprint.

Holysmoke99 said:
Thanks again, I have tried to revoke authorizations all day to no avail. I tried all the steps above and added revoking but it still won't give me option to trust fingerprint.
Click to expand...
Click to collapse
last attempt
fully uninstall magisk (root)
update to the latest OTA firmware of google....
revoke the authorizations again

I had altered boot.img to obtain root. This morning the phone was running very slow so I did a factory reset. I updated to the latest OTA. Is magisk still on the phone?

After installing 15 seconds ADB Installer v1.4.3 your batch file worked and brought up the prompt to accept fingerprint!!!!!!!!! Thanks so much for taking the time to help me!

Holysmoke99 said:
I had altered boot.img to obtain root. This morning the phone was running very slow so I did a factory reset. I updated to the latest OTA. Is magisk still on the phone?
Click to expand...
Click to collapse
I always complete remove magisk before installing the latest OTA ... just in case

biontx said:
I always complete remove magisk before installing the latest OTA ... just in case
Click to expand...
Click to collapse
do you have to alter boot.img each time you install OTA to keep root?

Holysmoke99 said:
do you have to alter boot.img each time you install OTA to keep root?
Click to expand...
Click to collapse
Each time before I install an OTA I remove root and magisk
Download the latest factory image for you device:
https://developers.google.com/android/images#bonito
Unzip it and copy boot.img to a dir on your device
Reinstall magisk apk with the permissions (my favorite: Magisk v20.4: MagiskManager-v7.5.1.apk)
https://github.com/topjohnwu/Magisk
Patch your boot.img with MagiskManager-v7.5.1.apk
Copy your magisk patched . img to your computer to a dir with: adb.exe; AdbWinApi.dll;AdbWinUsbApi.dll;fastboot.exe
Create 2 .bat files:
0001fastbootmagicpatched.bat:
@Echo off
set PATH=%CD%;%PATH%;
fastboot boot <FullPathTo your magisk patched img file>\magiskpatched.img
example:
fastboot boot D:\PROJECTS\NOUGAT\PIXEL3A\magisk\20200405Stable\magiskpatchedboot\magiskpatched.img
0002fastbootflashbootmagicpatched.bat:
@Echo off
set PATH=%CD%;%PATH%;
fastboot flash boot <FullPathTo your magisk patched img file>\magiskpatched.img
example:
fastboot flash boot D:\PROJECTS\NOUGAT\PIXEL3A\magisk\20200405Stable\magiskpatchedboot\magiskpatched.img
Put your device into bootloader.
Connect your device and run 0001fastbootmagicpatched.bat
Disconnect your device.
After a full start of your device, don't start any other app... put your device into bootloader again.
Connect your device and run 0002fastbootflashbootmagicpatched.bat
After de cmd window ends on your computer, press start on your device
Once fully started, all should be well on your device.
Start magisk app and adapt to your needs

System Power app
@Holysmoke99
System Power app (see attachment): could you test this app please:
Preview: see pictures in attachment.
Made for android 10 or higher.
Root is needed.
Contains a tile to be added in your quick settings: makes it more easy to take a screenshot.
Contains the following functions:
- Power off
- Restart
- Recovery
- Bootloader
- Torch (toggle torch: added v 3.1 b 30013)
- Screenshot
- Screen off
Any comments appreciated

Easiest Way To Root Android 11 on Surface Duo

first off, huge shout out to @JengaMasterG for TWRP for these devices. Without him, this super simple method wouldn't be possible.
What You'll Need
- Android 11 most recent update
- TWRP: TWRP for Surface Duo (credits to @JengaMasterG )
- Unlocked Bootloader
- ADB/Fastboot: ADB/Fastboot Install (what i use)
- Magisk
video
YT Tutorial
Bootloader Unlock
1.) Enable Developer Options via tapping Build Number over and over in the About Device part of settings
2.) Enable USB Debugging and OEM Unlock
3.) Plug device into the computer, and type the following command in cmd.exe, hit enter
Code:
adb devices
4.) You may get a pop up on screen requesting permission, always allow it
5.) Type the following and hit enter
Code:
adb reboot bootloader
6.) Once in the bootloader, your device might not be recognized right away and will need the driver manually installed via Device manager (see video for that)
7.) Once device is recognized, type the following command
Code:
fastboot flashing unlock
8.) Allow the unlocking of the Bootloader on device screen. this will erase everything
9.) Allow the device to fully boot up, enable USB Debugging again and continue the tutorial!
Instructions
1.) Rename Magisk-vxx.x.apk to Magisk.zip
2.) Enable USB Debugging
3.) Type the following to make sure your computer sees the device (in cmd.exe)
Code:
adb devices
4.) You may get a pop up on your device's screen asking for adb permission, check the always allow and hit ok
5.) Type the follow command to reboot to bootloader (in cmd.exe)
Code:
adb reboot bootloader
6.) Once you're in the booloader and its unlocked, download the TWRP image from above
7.) Use the following fastboot command to boot into TWRP
Code:
fastboot boot twrp.img
8.) Once TWRP boots, keep your device plugged in via usb and type the following command into cmd.exe and hit enter
Code:
adb shell twrp sideload
9.) Once in sideload, you can type the following with magisk.zip and root your device!
Code:
adb sideload magisk.zip
10.) Use the following command to reboot and you're done!
Code:
adb reboot
congrats! you're rooted!

LETS GOOOO!! HEROOO!! Super easy and working on the latest December 2022 update! Felt way safer as well, not so much concern over twrp as we only booted into it, and then I just used the standard magisk and it worked excellent without worrying about all types of patches and versions aside from the latest twrp for android 12 from @JengaMasterG!
Thank you! I think the renaming the magisk file from apk to zip was probably what I was doing wrong trying to follow the other methods, on top of driver errors, that were solved by uninstalling all the drivers for the duo on my surface pro, which revealed a native 'Surface Fastboot' driver. Combine that with the 15 second ADB and it's .bat ready to go command line interface, idk... it wen't so smooth and worked perfectly.
Now I can try to see if I can improve my experience with some go to methods.. I really want to enable immersive mode and hopefully increase overall volume, if possible (many devices this can be done with engineeringmode, idk yet but hopefully it does have one and hopefully I can also calibrate the gyroscope)... obviously adblock without vpn is on the menu.... can utilize the full autoruns app to stop apps from starting up at boot like in windows... and then get into some other customizations.

cqqx2 said:
LETS GOOOO!! HEROOO!! Super easy and working on the latest December 2022 update! Felt way safer as well, not so much concern over twrp as we only booted into it, and then I just used the standard magisk and it worked excellent without worrying about all types of patches and versions aside from the latest twrp for android 12 from @JengaMasterG!
Thank you! I think the renaming the magisk file from apk to zip was probably what I was doing wrong trying to follow the other methods, on top of driver errors, that were solved by uninstalling all the drivers for the duo on my surface pro, which revealed a native 'Surface Fastboot' driver. Combine that with the 15 second ADB and it's .bat ready to go command line interface, idk... it wen't so smooth and worked perfectly.
Now I can try to see if I can improve my experience with some go to methods.. I really want to enable immersive mode and hopefully increase overall volume, if possible (many devices this can be done with engineeringmode, idk yet but hopefully it does have one and hopefully I can also calibrate the gyroscope)... obviously adblock without vpn is on the menu.... can utilize the full autoruns app to stop apps from starting up at boot like in windows... and then get into some other customizations.
Click to expand...
Click to collapse
Hello! I'm rooted, but I can only read and can't write. I am Android version 122022.821.13 of Att.
So I can't delete the apk inside the system directory

linlin2az said:
Hello! I'm rooted, but I can only read and can't write. I am Android version 122022.821.13 of Att.
So I can't delete the apk inside the system directory
Click to expand...
Click to collapse
Newer Android versions, especially stock ROM, generally doesn't let you write to the system partition. Only ROMs can do that, unless you can find a way to change the partition permissions. Root alone will not allow it, no matter what you do. I used to know of a TWRP script to fix that and make the system writable, but it doesn't work on andorid 11/12/13 anyway