Hey All,
Here's how to update to the latest version of Marshmallow, finally released. I rehosted everything on Google Drive in case AT&T pulls the files. This is the PD6 version of the firmware.
I was rooted running a custom rom on 5.0.2. If you're running the previous latest build (OJ9), you can start the instructions at step 7.
1. This will wipe your phone, so be sure to backup before doing any of this
2. Download Odin and the 5.1.1 OJ9 firmware files (4 of them) from Google Drive
3. Flash in Odin by clicking all 4 buttons (AP, CSC, etc) and matching them to the 4 files from the OJ9 firmware
4. Click start
6. Once your phone reboots and you verify you're running OJ9, you can flash the 6.0.1 update through ADB
7. Make sure you’re running the latest version of ADB (windows package included in the folder worked great for me on Windows 10)
8. The file named “SS-G925AUCU3BOJ9-to-U3CPD6-UP” is the 6.0.1 update, download it and rename it to “ota.zip” and place it wherever ADB is installed
9. Power it off
10. Once it’s off, hold the power, home, and volume UP buttons until it says installing update, this is entering recovery mode
11. Once the menu is up, use the volume buttons to select install update from ADB
12. Type “adb devices” to confirm your device is ready, then “adb sideload ota.zip”
13. It’ll take quite some time, but eventually your phone will reboot and you’ll be running the official PD6 version of the AT&T 6.0.1 update for the S6 edge. Enjoy!
EDIT: If you're having problems with ADB reading the 6.0.1 update, try first launching ADB from wherever it is installed (C:\Program Files (x86)\Minimal ADB and Fastboot\ for me), type "adb kill-server" then "adb start-server," then "adb devices" to confirm you see your device (it should say sideload beside it if it is ready for the update). Then, type "adb sideload " and simply DRAG the ota.zip file from wherever you downloaded it to the CMD window. It should complete the command so that it is "adb sideload ota.zip". NOW press enter, and give it half an hour to complete or so. Good luck!! Special thanks to XDA user gmccowan1 for the tip.
https://drive.google.com/open?id=0B04l-XMi07VKdkY0ZExzeEVHcFk
Have fun!
So, no matter what I try, adb "cannot read file ". I renamed the file to ota.zip. I renamed to ota. I zipped it and ranmed to ota.zip, and then ota. Am I missing something? No luck here. Thanks for any help.
i think u should zip the file not changing the name
TXRangerXDA said:
So, no matter what I try, adb "cannot read file ". I renamed the file to ota.zip. I renamed to ota. I zipped it and ranmed to ota.zip, and then ota. Am I missing something? No luck here. Thanks for any help.
Click to expand...
Click to collapse
A couple suggestions:
1) Don't zip the file; it is already compressed. Just rename it with a zip extension.
2) Make sure that you're using ADB version 1.0.35. The Minimal ADB and Fastboot zip in the Google Drive contains the proper version.
If that doesn't work, you probably have another version of ADB installed and your system variables path is pointing to the old version . To make things simple do the following:
1) Copy OTA.zip to C:\Program Files (x86)\Minimal ADB and Fastboot
2) Open command prompt from that folder (Shift + Right Click -> Open command window here). The file name doesn't matter as long as your command is adb sideload <filename>.zip (e.g. adb sideload ota.zip).
kapooo3 said:
i think u should zip the file not changing the name
Click to expand...
Click to collapse
Yep, I tried that as well. Both with and without .zip, and with and without zipping it.
AvenidaDelGato said:
Make sure that you're using ADB version 1.0.35. The Minimal ADB and Fastboot zip in the Google Drive contains the proper version.
If that still doesn't work, you probably have another version of ADB installed and your system variables path is pointing to the old version .
To make thing simple, copy the OTA.zip file to C:\Program Files (x86)\Minimal ADB and Fastboot and open command prompt from that folder (Shift + Right Click -> Open command window here). The file name doesn't matter as long as your command is adb sideload <filename>.zip (e.g. adb sideload ota.zip).
Click to expand...
Click to collapse
I installed it to c:\adb, then put my files there and ran from there. Downloaded everything from the google drive link. It is possible I have another version installed, will check that, but I don't think so.
TXRangerXDA said:
Yep, I tried that as well. Both with and without .zip, and with and without zipping it.
I installed it to c:\adb, then put my files there and ran from there. Downloaded everything from the google drive link. It is possible I have another version installed, will check that, but I don't think so.
Click to expand...
Click to collapse
I made a revision to my post while you were replying. Check it out. BTW if your ADB version is older than 1.0.35 your phone will output a line saying something like "please use version 1.0.35".
I'm on PC2, but whenever I try to flash PD4 to get to PD6, I get a Status 7 error.
Few tips for adb and sideload
When running adb devices in the command prompt you should see a device ID number and sideload next to it
When calling a new version of adb.exe (assuming you are using the same PATH location) suggest to close and reopen the command prompt (windows cmd)
check which version of adb server is running, adb version (note you need >x.x.35)
If needed adb kill-server then adb start-server, then run adb version make sure its .35 at least (note the location of where PATH is pointing!! It could be using a different location for adb.exe)
You can also do adb help, look for sideload option, if sideload is not listed in the help menu, guess what, your version of adb server doesn't support this command, do the above
Lastly if none of that stuff is working check in the device managler (i mean manager) and see what adb device driver you are using. I have one from 2010 and it seems to be happy
AvenidaDelGato said:
A couple suggestions:
1) Don't zip the file; it is already compressed. Just rename it with a zip extension.
2) Make sure that you're using ADB version 1.0.35. The Minimal ADB and Fastboot zip in the Google Drive contains the proper version.
If that doesn't work, you probably have another version of ADB installed and your system variables path is pointing to the old version . To make things simple do the following:
1) Copy OTA.zip to C:\Program Files (x86)\Minimal ADB and Fastboot
2) Open command prompt from that folder (Shift + Right Click -> Open command window here). The file name doesn't matter as long as your command is adb sideload <filename>.zip (e.g. adb sideload ota.zip).
Click to expand...
Click to collapse
Thanks, hope others find this useful. These exact instructions should prevent any headache when using ADB.
Note that the version of minimal fastboot and ADB I included is v1.4, but if you type "adb version" it says 1.0.35. It should still work fine!
Arcen1k said:
I'm on PC2, but whenever I try to flash PD4 to get to PD6, I get a Status 7 error.
Click to expand...
Click to collapse
Hrm, why are you flashing PD4 at all? PD6 is the latest one, but the file I gave is specifically for upgrading OJ9 (5.1.1) to PD6 (latest).
No idea if downgrading through Odin will work, but if you're on OJ9 you should have no issues sideloading.
TXRangerXDA said:
Yep, I tried that as well. Both with and without .zip, and with and without zipping it.
I installed it to c:\adb, then put my files there and ran from there. Downloaded everything from the google drive link. It is possible I have another version installed, will check that, but I don't think so.
Click to expand...
Click to collapse
Keep me posted, I'm interested to know if you get this resolved.
The package itself should contain an md5 and verify before flashing it... so I doubt there's anything wrong with the files I uploaded. Has anyone else besides me successfully installed marshmallow?
Sounds like the problem is with the ADB or the PC. Have you tried different ports (like USB 2.0 instead of 3.0) or a different computer?
EDIT: Users on reddit have successfully gotten marshmallow from the files I uploaded, so they are safe.
As for the "ota.zip" error, one user tried almost everything, and in the end restarting his PC fixed it oddly enough. See here:
https://www.reddit.com/r/GalaxyS6/c...l_att_601_marshmallow_update_flashing/d2sv6d5
For anyone who flashed PC2, or I guess for future reference to return from PD6.
I flashed PC2 not realizing we could flash PD6 directly. I was able to use ODIN to get back to OJ9, then sideload PD6.
---------- Post added at 05:32 PM ---------- Previous post was at 05:31 PM ----------
[/COLOR]
CitizenInsane said:
Hrm, why are you flashing PD4 at all? PD6 is the latest one, but the file I gave is specifically for upgrading OJ9 (5.1.1) to PD6 (latest).
No idea if downgrading through Odin will work, but if you're on OJ9 you should have no issues sideloading.
Click to expand...
Click to collapse
I flashed PC2, not realizing that we could go directly to PD6. I have since used ODIN to get back to OJ9. Then I flashed PD6 directly from there. Process worked fine.
AvenidaDelGato said:
A couple suggestions:
1) Don't zip the file; it is already compressed. Just rename it with a zip extension.
2) Make sure that you're using ADB version 1.0.35. The Minimal ADB and Fastboot zip in the Google Drive contains the proper version.
If that doesn't work, you probably have another version of ADB installed and your system variables path is pointing to the old version . To make things simple do the following:
1) Copy OTA.zip to C:\Program Files (x86)\Minimal ADB and Fastboot
2) Open command prompt from that folder (Shift + Right Click -> Open command window here). The file name doesn't matter as long as your command is adb sideload <filename>.zip (e.g. adb sideload ota.zip).
Click to expand...
Click to collapse
Im not sure what to do here when I install the ADB to my system I go into the folder and it wont run from the folder. I can only get the CMD window to open from start menu. And it always fails to read the file.
Arcen1k said:
I'm on PC2, but whenever I try to flash PD4 to get to PD6, I get a Status 7 error.
Click to expand...
Click to collapse
You should be able to upgrade directly from PC2 to PC6 using the upgrade file SS-G925AUCU3CPC2-to-U3CPC6-UP available here: <https://xdmd.sl.attcompute.com/agents/48652/1488/SS-G925AUCU3CPC2-to-U3CPC6-UP>
Make sure to add a .zip extension to the filename.
---------- Post added at 01:59 AM ---------- Previous post was at 01:19 AM ----------
cws754 said:
Im not sure what to do here when I install the ADB to my system I go into the folder and it wont run from the folder. I can only get the CMD window to open from start menu. And it always fails to read the file.
Click to expand...
Click to collapse
The steps below should help you avoid any issues:
Open command prompt and enter adb version. If it outputs "Android Debug Version 1.0.35", skip to Step 3. Otherwise proceed to Step 2.
Navigate to the directory of Minimal ADB and Fastboot by entering cd c:\<path to directory>. If you installed it to the default directory enter cd C:\Program Files (x86)\Minimal ADB and Fastboot
Enter adb sideload <filename.zip> (e.g. adb sideload ota.zip). If this doesn't work proceed to Step 4.
The "cannot read file.zip" error can also be a result of an incorrect file path. Try specifying the file path by entering adb sideload <%path%\filename.zip> (e.g. adb sideload C:\Program Files (x86)\Minimal ADB and Fastboot\ota.zip). If this doesn't work, paste the content of your command prompt window in a response (to copy text in command prompt right click -> select all -> Ctrl +C).
AvenidaDelGato said:
You should be able to upgrade directly from PC2 to PC6 using the upgrade file SS-G925AUCU3CPC2-to-U3CPC6-UP available here: <https://xdmd.sl.attcompute.com/agents/48652/1488/SS-G925AUCU3CPC2-to-U3CPC6-UP>
Make sure to add a .zip extension to the filename.
---------- Post added at 01:59 AM ---------- Previous post was at 01:19 AM ----------
The steps below should help you avoid any issues:
Open command prompt and enter adb version. If it outputs "Android Debug Version 1.0.35", skip to Step 3. Otherwise proceed to Step 2.
Navigate to the directory of Minimal ADB and Fastboot by entering cd c:\<path to directory>. If you installed it to the default directory enter cd C:\Program Files (x86)\Minimal ADB and Fastboot
Enter adb sideload <filename.zip> (e.g. adb sideload ota.zip). If this doesn't work proceed to Step 4.
The "cannot read file.zip" error can also be a result of an incorrect file path. Try specifying the file path by entering adb sideload <%path%\filename.zip> (e.g. adb sideload C:\Program Files (x86)\Minimal ADB and Fastboot\ota.zip). If this doesn't work, paste the content of your command prompt window in a response (to copy text in command prompt right click -> select all -> Ctrl +C).
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>adb version
Android Debug Bridge version 1.0.35
Revision fc2a139a55f5-android
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
05157df5438f7a1d sideload
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload ota.zip
loading: 'ota.zip'
* cannot read 'ota.zip' *
C:\Program Files (x86)\Minimal ADB and Fastboot>
This is what I got
cws754 said:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb version
Android Debug Bridge version 1.0.35
Revision fc2a139a55f5-android
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
List of devices attached
05157df5438f7a1d sideload
C:\Program Files (x86)\Minimal ADB and Fastboot>adb sideload ota.zip
loading: 'ota.zip'
* cannot read 'ota.zip' *
C:\Program Files (x86)\Minimal ADB and Fastboot>
This is what I got
Click to expand...
Click to collapse
Try checking to make sure your zip isn't corrupted. Are you able to view the contents of ota.zip by double clicking on it? What are the contents of the zip?
AvenidaDelGato said:
Try checking to make sure your zip isn't corrupted. Are you able to view the contents of ota.zip by double clicking on it? What are the contents of the zip?
Click to expand...
Click to collapse
Yeah I can open and view everything is there I downloaded again to make sure all the same everything there. I was going to try just using original file not renaming it or anything. Is that a bad idea? I promise I'm not 100% noob just cant figure why its not working.
cws754 said:
Yeah I can open and view everything is there I downloaded again to make sure all the same everything there. I was going to try just using original file not renaming it or anything. Is that a bad idea? I promise I'm not 100% noob just cant figure why its not working.
Click to expand...
Click to collapse
This might sound dumb but try adb sideload ota.zip.zip. Sometimes Windows hides the extra .zip when you have file name extensions hidden. If that still doesn't work try opening command prompt with Run as Administrator.
AvenidaDelGato said:
This might sound dumb but try adb sideload ota.zip.zip. Sometimes Windows hides the extra .zip when you have file name extensions hidden. If that still doesn't work try opening command prompt with Run as Administrator.
Click to expand...
Click to collapse
well I guess its just not wanting to work for me even tried different computer.
cws754 said:
well I guess its just not wanting to work for me even tried different computer.
Click to expand...
Click to collapse
This is baffling - I've read other people having a similar issue and it seems like something different fixed it each time.
Have you tried stuff like restarting? Or different ports on the PC?
Related
SETTING UP ADB FOR WINDOWS USERS
The example shown in the video tutorial is running Windows 7. XP, Vista should run the same way.
1) Download the SDK program for your OS Here..
2) Download the latest Java Platform if you don’t have an updated version.
3) The SDK program will download in a .zip file. Extract that file somewhere easily accessible [like your desktop!]
4) You should now have a folder on your desktop with a name: android-sdk-windows
5) Drag that folder into the root of your HD…
The pathway should be something like: Computer > Local Disk ( C: ) > android-sdk-windows
6) make SURE to install the USB driver package in SDK... this way your device will be recognized when running adb commands later on...
Now that you have placed the SDK program there you can run ADB commands. But you need to run them Manually. Most people go into the tools folder and click adb and expect it to work its magic… you can stare all you want, but all it’s going to do it open a command prompt, run commands, and disappear. Now, don’t go “ZOMG I DON’T KNOW WHAT TO DO! IT WONT WORK!” …. Trust me, it will work..
6) Open a command prompt, go to windows start menu and click “search” or “run…” and in the box type: cmd and then press enter. This will execute the command prompt [terminal]
7) Now connect your Eris via USB. MAKE SURE YOU HAVE USB DEBUGGING ON!! If you don’t, go to settings < applications < development and check the box: usb debugging
8) Don’t mount your SD card yet.
9) Now you are almost ready to execute your first adb command. But first you must re-direct the path in command prompt to be your tools folder in SDK… this is what command should look like before:
C:\Users\YourUserName>
Now type in command: cd
But DON’T press enter… drag and drop the path from your SDK tools into that command line, so it should look like this:
C:\Users\YourUserName> cd C:\android-sdk-windows\tools
Now press enter. NOW your command prompt should say:
C:\android-sdk-windows\tools
Ok, last part… to test adb type in command: adb devices
Now it should return something like:
List of devices attached
HT9ANXXXXX Device
Ok so now you can execute Adb commands. Make sure you always have your command prompt pathway set to SDK tools or it WILL NOT WORK! You can now also execute adb commands directly to your device from it’s shell by typing: adb shell followed by your command.
For Visual people here is my short Youtube video explain it all again... and here is my screen shot to show you what it should look like, pay attention to my command prompt.
Another example: Custom boot animation for NON-ROOT USERS.
1) Find / create a boot animation that works with the Eris
2) name the Zip file bootanimation.zip
3) place .zip file in SDK tools folder
4) Follow above instructions to set path in CMD to tools folder and connect your device
5) execute this command:
adb push bootanimation.zip /data/local
Feel free to PM if you have any questions... I hope this helps
adb
Could someone sticky this please?... and I think themes and apps is a good place for it..unless you think it belongs in general..
Help
I followed your instructions to the "T" everything worked but when I tried to push abd bootanimation command it says access denied is this because I don't have root? I am running on the 2.1 leak Version 2 OTA . Seems to be working fine for me. Although I wish I would have waited for root!! C'mon DEVS I'm pulling for you. Any suggestions?
cornjo said:
I followed your instructions to the "T" everything worked but when I tried to push abd bootanimation command it says access denied is this because I don't have root? I am running on the 2.1 leak Version 2 OTA . Seems to be working fine for me. Although I wish I would have waited for root!! C'mon DEVS I'm pulling for you. Any suggestions?
Click to expand...
Click to collapse
EDIT: See OP at bottom for directions.
how do i install an apk file right to my phone using the "cmd"
jibbz said:
how do i install an apk file right to my phone using the "cmd"
Click to expand...
Click to collapse
adb install whatever.apk
n1ghtwish said:
adb install whatever.apk
Click to expand...
Click to collapse
ok my problem is tht when i use the cmd n get to my SDK tool folder n type in adb install (app name).apk it dont do anything
Hopefully its this simple
jibbz said:
ok my problem is tht when i use the cmd n get to my SDK tool folder n type in adb install (app name).apk it dont do anything
Click to expand...
Click to collapse
You probably don't have the .apk file in the same directory as sdk tool folder
try moving it there and see if that works.
I tried to load the advanced menu mod and the phone wont go past the startup screen. I can get into TWRP but I don't know how to get a rom to the SD card when it wont mount. Funny, I've been doing the ROM thing for 4 years now and have never used ABD so I don't know how that works or if that's what I need........can someone please point me in the right direction for getting a ROM on my phone so I can flash in TWRP?
digthemlows said:
I tried to load the advanced menu mod and the phone wont go past the startup screen. I can get into TWRP but I don't know how to get a rom to the SD card when it wont mount. Funny, I've been doing the ROM thing for 4 years now and have never used ABD so I don't know how that works or if that's what I need........can someone please point me in the right direction for getting a ROM on my phone so I can flash in TWRP?
Click to expand...
Click to collapse
How did you unlock bootloader and flash recovery?
Sent from my HTC One using xda premium
redbull123 said:
How did you unlock bootloader
and flash recovery? All-In-One Toolkit?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Bootloader was unlocked long ago via HTC Dev. All-in-one wasn't out when I got the phone ...... I just downloaded that, but when I try to ABD sideload it opens up a CMD prompt that says C:\Users\myname\desktop\HTC is not recognized as an internal or external command, operable program or batch file.
Also when I enable ABD sideload in TWRP on my phone it hangs at "Starting ABD sideload feature..." and never does anything.
Try push instead of sideload
ArmedandDangerous said:
Try push instead of sideload
Click to expand...
Click to collapse
Sorry, I don't know how to Push, can someone give me quick instructions?? or point me in the right direction........XDA has become so huge it's actually a mess to search..........I appologize in advance.
Type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends.
digthemlows said:
Bootloader was unlocked long ago via HTC Dev. All-in-one wasn't out when I got the phone ...... I just downloaded that, but when I try to ABD sideload it opens up a CMD prompt that says C:\Users\myname\desktop\HTC is not recognized as an internal or external command, operable program or batch file.
Also when I enable ABD sideload in TWRP on my phone it hangs at "Starting ABD sideload feature..." and never does anything.
Click to expand...
Click to collapse
Download these files: http://d-h.st/RvD - call the unzipped folder with the four files 'android' or something and put it somewhere, either directly on your c:\ drive or on your desktop
Download a rom and put it in the folder along with those files you download
Select 'install zip from sideload' in recovery on your phone
Hold Shift and right-click on the folder and select 'Open Command Window Here'
Command:
adb sideload name_of_rom.zip
once it reaches 100% it should begin to install on your phone automatically.
Or you could
adb push name_of_rom.zip /sdcard/
this will put the rom on your sdcard and you will need to flash it normally. (you don't select 'install zip from sideload' for this)
redbull123 said:
Download these files: http://d-h.st/RvD - call the unzipped folder with the four files 'android' or something and put it somewhere, either directly on your c:\ drive or on your desktop
Download a rom and put it in the folder along with those files you download
Select 'install zip from sideload' in recovery on your phone
Hold Shift and right-click on the folder and select 'Open Command Window Here'
Command:
adb sideload name_of_rom.zip
once it reaches 100% it should begin to install on your phone automatically.
Or you could
adb push name_of_rom.zip /sdcard/
this will put the rom on your sdcard and you will need to flash it normally. (you don't select 'install zip from sideload' for this)
Click to expand...
Click to collapse
'abd' is not recognized as and internal or external command, operable program or batch file is the error I'm getting.............
digthemlows said:
'abd' is not recognized as and internal or external command, operable program or batch file is the error I'm getting.............
Click to expand...
Click to collapse
its adb, not abd - stands for Android Debug Bridge
---------- Post added at 05:09 PM ---------- Previous post was at 05:04 PM ----------
You should read this: http://www.androidcentral.com/android-201-10-basic-terminal-commands-you-should-know
Helped me out a lot with ADB, easy to understand...
redbull123 said:
its adb, not abd - stands for Android Debug Bridge
---------- Post added at 05:09 PM ---------- Previous post was at 05:04 PM ----------
You should read this: http://www.androidcentral.com/android-201-10-basic-terminal-commands-you-should-know
Helped me out a lot with ADB, easy to understand...
Click to expand...
Click to collapse
Man, I'm being such a noob. Ok, so when I run c:\fastboot>adb push name_of_rom.zip/sdcard/ it displays a menu of all the adb commands but does nothing.........
digthemlows said:
Man, I'm being such a noob. Ok, so when I run c:\fastboot>adb push name_of_rom.zip/sdcard/ it displays a menu of all the adb commands but does nothing.........
Click to expand...
Click to collapse
tried "adb remount" and get "error: device not found
I don't think my computer is seeing the device, gonna log in with admin rights and see what's up
digthemlows said:
Man, I'm being such a noob. Ok, so when I run c:\fastboot>adb push name_of_rom.zip/sdcard/ it displays a menu of all the adb commands but does nothing.........
Click to expand...
Click to collapse
Did you type 'name_of rom.zip'? Or did you replace it with the actual name of the ROM?
Edit: Sorry, you need to put a space before /sdcard/
redbull123 said:
Did you type 'name_of rom.zip'? Or did you replace it with the actual name of the ROM?
Click to expand...
Click to collapse
I typed the name of the rom......I'm going to update the drivers, because I'm seeing an error in device manager for the "android driver" .......
digthemlows said:
Man, I'm being such a noob. Ok, so when I run c:\fastboot>adb push name_of_rom.zip/sdcard/ it displays a menu of all the adb commands but does nothing.........
Click to expand...
Click to collapse
Ok let's make this easier. Go to where your ADB/fastboot files are, shift right click on empty space and select Open Command Window Here. Then type push name_of_rom.zip/sdcard/
name_of_rom.zip should be changed to whatever file name your ROM is that you want to install. If sdcard doesn't work, try /data/media
ArmedandDangerous said:
Then type push name_of_rom.zip/sdcard/
name_of_rom.zip should be changed to whatever file name your ROM is that you want to install. If sdcard doesn't work, try /data/media
Click to expand...
Click to collapse
adb push name_of_rom.zip /sdcard/
ArmedandDangerous said:
Ok let's make this easier. Go to where your ADB/fastboot files are, shift right click on empty space and select Open Command Window Here. Then type push name_of_rom.zip/sdcard/
name_of_rom.zip should be changed to whatever file name your ROM is that you want to install. If sdcard doesn't work, try /data/media
Click to expand...
Click to collapse
either of these get me the ADB menu as well, If I put as space after the rom name i get "error, closed"
yeah, I have tried everything I think. Any other ideas?
digthemlows said:
yeah, I have tried everything I think. Any other ideas?
Click to expand...
Click to collapse
Are you right clicking on the folder and open command window here?
Reboot your computer...
Shift+right-click, Open command window from folder
Go into fastboot in your bootloader and type
fastboot devices
If your device appears then go into recovery and type
adb devices
If your devices doesn't appear then there's something wrong with your drivers/adb files or folder
If it's found then just do a push or sideload...
The only thing I can think if it doesn't work is buy a usb otg cable and put the ROM onto a usb and flash it through TWRP that way.
Sent from my HTC One using xda premium
Ok, abd devices showed my device and "recovery" Went in and renamed the folder with adb and my ROM in it, double checked everything and was able to load the rom.......also I wasn't putting space after the rom name and between /sdcard/ ......
digthemlows said:
Ok, abd devices showed my device and "recovery" Went in and renamed the folder with adb and my ROM in it, double checked everything and was able to load the rom.......also I wasn't putting space after the rom name and between /sdcard/ ......
Click to expand...
Click to collapse
So... Everything's ok?
Sent from my HTC One using xda premium
Allright. I recently broke my S3 LTE's LCD when i was trying to change glass. Now my problem is that it tells my S3 is an portable media player, so it won't let me just open my folders and stuff. What i can do to save my important pictures and stuff. Thanks in advance!! :fingers-crossed::good:
Is adb enabled on the device?
Magik_Breezy said:
Is adb enabled on the device?
Click to expand...
Click to collapse
I don't think it's enabled, but i can't be sure im right.
Such Name said:
I don't think it's enabled, but i can't be sure im right.
Click to expand...
Click to collapse
Unfortunetly there is no instantaneous way to see if adb is enabled and you will be required to install the relevant tools to know.
1. Download and install the Samsung USB Drivers from http://developer.samsung.com/android/tools-sdks/Samsung-Android-USB-Driver-for-Windows
2. Download and install minimal adb and fastboot from http://forum.xda-developers.com/showthread.php?t=2317790 - thanks to shrimp208 for providing us with this so we don't have to install the whole SDK.
3. Run cmd and change directory to the location of adb.exe (e.g. cd C:\users\admin\downloads\apt), run 'adb.exe start-server' then 'adb.exe devices' to see if your phone has adb running.
If adb is running you can copy files from you're phone's file system to your pc with 'adb pull' (e.g. adb pull adb pull
/data/app C:\users\admin\downloads\apt).
Best of luck
Magik_Breezy said:
Unfortunetly there is no instantaneous way to see if adb is enabled and you will be required to install the relevant tools to know.
1. Download and install the Samsung USB Drivers from http://developer.samsung.com/android/tools-sdks/Samsung-Android-USB-Driver-for-Windows
2. Download and install minimal adb and fastboot from http://forum.xda-developers.com/showthread.php?t=2317790 - thanks to shrimp208 for providing us with this so we don't have to install the whole SDK.
3. Run cmd and change directory to the location of adb.exe (e.g. cd C:\users\admin\downloads\apt), run 'adb.exe start-server' then 'adb.exe devices' to see if your phone has adb running.
If adb is running you can copy files from you're phone's file system to your pc with 'adb pull' (e.g. adb pull adb pull
/data/app C:\users\admin\downloads\apt).
Best of luck
Click to expand...
Click to collapse
Huge thanks for this help. It tells me "List of devices attached: 430008b6b6f9a0b1 device" and sorry for stupid question, but what does that mean?
Such Name said:
Huge thanks for this help. It tells me "List of devices attached: 430008b6b6f9a0b1 device" and sorry for stupid question, but what does that mean?
Click to expand...
Click to collapse
That is your device id, this means you should be able to recover your files.
Initiate 'adb.exe shell' and it should automatically select your device. You can then navigate using the 'cd' command to change directory and 'ls' to list all files/folders in that directory. After finding the files you can pull them from your device to your computer
Magik_Breezy said:
That is your device id, this means you should be able to recover your files.
Initiate 'adb.exe shell' and it should automatically select your device. You can then navigate using the 'cd' command to change directory and 'ls' to list all files/folders in that directory. After finding the files you can pull them from your device to your computer
Click to expand...
Click to collapse
Thanks you very much . I was able to save all files/memories with ADB. I can't even thank you enough! :laugh:
I'm glad I could help, praise the ADB. Hit thanks if you wish
I was able to install MM using Sideload with MAC.
Procedure is the same as Windows the difference is that you NEED the most recent ADB.
https://developer.android.com/studio/index.html
Check using ./adb version that it is running at least 1.0.32
Davids-MacBook-Air:tools David$ ./adb devices
List of devices attached
XXXXXX sideload
Davids-MacBook-Air:tools David$ ./adb sideload update.zip
Total xfer: 2.07x
abcdavidefg said:
So I try to install sideload using my MAC but no luck.
I made sure the reactivation lock is "off"
I installed the ADB in my MAC.
I test:
./adb devices (and it shows my devices)
./adb reboot (and it reboots my phone)
I'm assuming that the ADB is working.
When I go into recovery mode and the "update ADB" this is what happened
Davids-MacBook-Air:mac David$ ./adb devices
List of devices attached
06157df643132f18 sideload
Davids-MacBook-Air:mac David$ ./adb sideload update.zip
error: protocol fault (no status)
Davids-MacBook-Air:mac David$
Phone wipes everything.
In the screen shows something like installing Hash tree
Hash tree successful
Phone reboots but it turns on regularly with everything wipe but no MM update.
Help!! anyone
Click to expand...
Click to collapse
Does this page help you?
http://forum.xda-developers.com/showthread.php?t=2720846
Jimmyvb98 said:
Does this page help you?
http://forum.xda-developers.com/showthread.php?t=2720846
Click to expand...
Click to collapse
No luck yet.
I try to transfer the file using
./adb push update.zip /sdcard (didn't work).... I'm assuming because I don't have a "/sdcard" directory.
Then I manually created a file called "sdcard" in the root of my memory.
Then copied the file from my computer to the memory of my phone.
Then reboot (power+home+volup) choosed update from external but I get an error saying no .../sdcard (file or directory)
I think the problem is that I can't move the file to the root of the phone. I guess I need root access (which I can't get)
I was able to sideload the file using MAC.
In general is relative the same method. Just make sure you have the most recent version of ADB for MAC.
Most of the "easy" installs of ADB for MAC are old version.
I'll post a more detail explanation. Step by Step if anyone ask for it
Hello folks!
Its been a while since i posted here - i havent been flashing roms for an age (kids etc got in the way!)
Anyway, i've picked up a Pixel 4 XL, and it was running a custom ROM, i'm trying to move back to stock and have been able to follow all the guides i've found up to using the 'fastboot flashall' in shell.
The command works and delivers the
Bootloader Version...:
Baseband Version.....:
Serial Number........:
values, but then errors out with the following error "fastboot: error: ANDROID_PRODUCT_OUT not set"
I'm stumped what that means and how to fix. I'm doing all of this on my Pixelbook, and have updated fastboot and adb as per the initial steps for flashing.
Can anyone shed any light on what i still need to do to get flashall to work as expected?
Thanks in advance if you are able to help out!
ptm
Welcome Back
Could you post the exact command you are using for fastboot flash please? It sounds like fastboot is not finding the files to flash. Usually, depending on the configuration of the fastboot install, it's easier to place the firmware in the same directory as the fastboot binary.
Thanks! It turns out i've missed this place!
So the firmware files are all on the chromebook and I've used 'shell' to navigate to where I've unzipped. Here's the command line with the command i'm using: "[email protected] ~/Downloads/ota_file $ fastboot flashall"
Before trying a full flash, i was trying to sideload the OTA as per instructions here https://developers.google.com/android/ota#instructions but moving the file from my pixelbook to the 4XL fails at 47% every time.
So i reverted to a full flash as per these instructions - https://developers.google.com/android/images and that is where i'm coming a cropper with the 'not set' error.
Thanks for your help!
ktmom said:
Welcome Back
Could you post the exact command you are using for fastboot flash please? It sounds like fastboot is not finding the files to flash. Usually, depending on the configuration of the fastboot install, it's easier to place the firmware in the same directory as the fastboot binary.
Click to expand...
Click to collapse
I thinnk you may be merging several approaches.
You are using the full factory image downloaded from the https://developers.google.com/android/images page, right? Then, once downloaded, you are unzipping the file and cd into the new directory (from the unzip). The command then should be
Code:
./flash-all.sh
As far as the OTA install is concerned, you are using the command
Code:
adb sideload "ota_file.zip"
, and at 47%, what happens that it appears to fail? My memory on my P3XL is at that point it takes awhile.
If you are using a C to C switch to an A to C cable and try it. You'll want to remove the wipe from the flash-all before you flash the full image and it's the flash all you should be using to flash.
Yeah i think you're right - so now just concentrating on the Full Flash method shown on the Google Developers page, and yes doing it exactly as you'd described.
Ok - using
Code:
./flash-all.sh
now returns the error
Code:
bash: ./flash-all.sh: Permission denied
I have tried to prefix './flash-all.sh' with 'Fastboot' but no dice here either. Is that required at all?
ktmom said:
I thinnk you may be merging several approaches.
You are using the full factory image downloaded from the https://developers.google.com/android/images page, right? Then, once downloaded, you are unzipping the file and cd into the new directory (from the unzip). The command then should be
Code:
./flash-all.sh
As far as the OTA install is concerned, you are using the command
Code:
adb sideload "ota_file.zip"
, and at 47%, what happens that it appears to fail? My memory on my P3XL is at that point it takes awhile.
Click to expand...
Click to collapse
ptm said:
Yeah i think you're right - so now just concentrating on the Full Flash method shown on the Google Developers page, and yes doing it exactly as you'd described.
Ok - using
Code:
./flash-all.sh
now returns the error
Code:
bash: ./flash-all.sh: Permission denied
I have tried to prefix './flash-all.sh' with 'Fastboot' but no dice here either. Is that required at all?
Click to expand...
Click to collapse
You need to give the "flash-all.sh" script execution rights (that is why the permission denied error). Use this code:
Code:
chmod +x ./flash-all.sh
You may need super user/root rights:
Code:
sudo chmod +x ./flash-all.sh
The "flash-all.sh" script is a stand-alone script that sequentially flashes the entire factory package. As was mentioned in another repsonse in this thread, in cases where you want to update, but not lose your installed user apps and data, you would edit the script and remove the "-w" augment. In this case, you are returning to stock and you should perform the wipe (-w).
The dot slash (./) that preceeds the flash-all.sh tells the bash interpreter (what runs commands you give) that the file is right here, in this directory.
The flash-all.sh is a standalone script (series of written instructions) and calls fastboot from within it.
Thanks for sticking with me on this ktmom!
OK, i've used both
Code:
chmod +x ./flash-all.sh
and
Code:
sudo chmod +x ./flash-all.sh
but still getting the permission denied error when i launch ./flash-all.sh
I'll do a screencast vid walking through the entire process i'm following, so that you can see what i'm up too and in case it gives any further clues for a solution.
Thanks again!
ktmom said:
You need to give the "flash-all.sh" script execution rights (that is why the permission denied error). Use this code:
Code:
chmod +x ./flash-all.sh
You may need super user/root rights:
Code:
sudo chmod +x ./flash-all.sh
The "flash-all.sh" script is a stand-alone script that sequentially flashes the entire factory package. As was mentioned in another repsonse in this thread, in cases where you want to update, but not lose your installed user apps and data, you would edit the script and remove the "-w" augment. In this case, you are returning to stock and you should perform the wipe (-w).
The dot slash (./) that preceeds the flash-all.sh tells the bash interpreter (what runs commands you give) that the file is right here, in this directory.
The flash-all.sh is a standalone script (series of written instructions) and calls fastboot from within it.
Click to expand...
Click to collapse
@ptm, No worries, I'll do my best to help. I'm typing this on a chromebook that I also use to fastboot to a P3XL.
Edit 1:
Just to make sure:
1) The bootloader is unlocked?
2) "fastboot devices" returns the serial number of your device?
3) you are running ./flash-all.sh command as root or as the default user? In other words, the same way that fastboot devices returns the serial number. Either sudo fastboot devices or just fastboot devices.
4) if you enter the linux command: ls -al flash-all.sh do you get something like:
-rwxr-xr-x. 1 chronos chronos 957 Jul 18 2019 flash-all.sh
In this example -rwxr-xr-x is depicting the file permissions where there are three groupings; owner group everyone else. The first rwx means read, write and execute permissions for the file owner. Others in the same group and everyone else has read and execute permissions. Execute (x) is required in order for a script to run. If your file does not have three x so that all three groups have permission to execute it, then we need to revisit that.
Edit 2:
Another thought that could be affecting you is ADB and Fastboot are old. in your crosh shell, type:
Code:
[email protected] ~ $ adb --version
Android Debug Bridge version 1.0.41
Version 29.0.5-5949299
[email protected] ~ $ fastboot --version
fastboot version 29.0.5-5949299
Installed as /usr/local/bin/fastboot
If either returns a version older than the output above, then the easy way to update these is to use the script on Nathan Chance's Githuib. This might look a little overwhelming but it's pretty easy. I suggest you read the page, but the operative information is in section 4. Run the setup script:
To install, run
Code:
curl -s https://raw.githubusercontent.com/nathanchance/chromeos-adb-fastboot/master/install.sh | bash
in your shell prompt.
This script very nicely updates your ADB/Fastboot to the newest version which will be required for your P4XL
Are you guys sure you aren't making it too hard? You don't have to give any commands to install the full image. Download the full image and put it into an empty folder, go ahead and extract it in that folder. Create another new folder, Copy everything into it so you still have the full image in the first folder. Now download the tools and put those into a folder and extract them in that folder. Take the entire contents of that folder and add it to the folder you copied the extracted image into. What you should have now is one folder that still has the full extracted image, one that has the full extracted tools, and one that has both. If you have not already done so the phone should have debugging enabled and oem should be on. Go ahead and put it into bootloader mode and plug it in, type cmd in the path bar of the folder with both tools and image and check devices which will tell you if the tools can see the phone. If you get your serial the tools can see the phone. If you're going to wipe you can go ahead and click the flash-all and it will start the process, you do not give any commands. If you don't want to wipe the edit the flash-all to remove the-w, save it, and click on it. Again, no command is given, you just click and the flash-all does the rest.
Edit... And dont forget, A to C, not the provided C to C.
krabman said:
Are you guys sure you aren't making it too hard? You don't have to give any commands to install the full image. Download the full image and put it into an empty folder, go ahead and extract it in that folder. Create another new folder, Copy everything into it so you still have the full image in the first folder. Now download the tools and put those into a folder and extract them in that folder. Take the entire contents of that folder and add it to the folder you copied the extracted image into. What you should have now is one folder that still has the full extracted image, one that has the full extracted tools, and one that has both. If you have not already done so the phone should have debugging enabled and oem should be on. Go ahead and put it into bootloader mode and plug it in, type cmd in the path bar of the folder with both tools and image and check devices which will tell you if the tools can see the phone. If you get your serial the tools can see the phone. If you're going to wipe you can go ahead and click the flash-all and it will start the process, you do not give any commands. If you don't want to wipe the edit the flash-all to remove the-w, save it, and click on it. Again, no command is given, you just click and the flash-all does the rest.
Edit... And dont forget, A to C, not the provided C to C.
Click to expand...
Click to collapse
What Tools do you need to do this?
Same page as the images, scroll up from them and in the description of the process they have a link to the platform tools.
@krabman, Since this is using a chromebook, not a PC, things are flakier than normal. I just replicated the problems experienced by @ptm and some of it is due to old ADB/Fastboot as described in my previous post. Some is because ChromeOS made a change in an update that mounts nearly all of the partitions noexec, which means scripts can not execute and give the reported, "no permissions" error. There is a workaround since /usr/local is mounted executable. It's also possible to remount a partition with exec permissions.
@ptm, as the easiest route, I suggest making sure the ABD is current using the script I linked yesterday, and then going back to the OTA sideload method. I tanked my phone for a few hours yesterday trying to make fastboot get through the entire system image. I finally resorted to my full ubuntu install on my chromebook.
airmaxx23 said:
What Tools do you need to do this?
Click to expand...
Click to collapse
A general Fastboot/ADB tutorial is available here. If you are not using a chromebook, this thread's discussion will just add confusion.
If you are using a chromebook, then you need to enter a crosh shell, make sure adb and fastboot are updated as described in an earlier post and read the rest of the information I posted about the associated problems.
My understanding is the sh should flash on chrome with the latest tools as I described and you use the bat for PC. If the device is down he would have nothing to lose trying, if not I'd be leery of trying it since a partial flash will definitely result in a softie. Of course the possibility that I don't fully understand it may explain my puzzlement.
ktmom said:
A general Fastboot/ADB tutorial is available here. If you are not using a chromebook, this thread's discussion will just add confusion.
If you are using a chromebook, then you need to enter a crosh shell, make sure adb and fastboot are updated as described in an earlier post and read the rest of the information I posted about the associated problems.
Click to expand...
Click to collapse
Thanks, I know how to use ADB on the PC but I have a ChromeBook that I'd like to use as well. I already have it in Developer Mode.
I got it working, I just to run the script to update ADB and Fastboot.
airmaxx23 said:
Thanks, I know how to use ADB on the PC but I have a ChromeBook that I'd like to use as well. I already have it in Developer Mode.
When I open a Crosh Window, type shell, then adb devices my Pixel 4 XL shows up but I get: no permissions; see [http://developer.android.com/tools/device.html]
Click to expand...
Click to collapse
My bet is your ADB/fastboot are to old. Go back to post 9 and read the lower portion under edit2. You should also read forward from that point as there are additional issues that ChromeOS introduced with the noexec mounting of partitions. It will mean that without a workaround, you can not execute the flash-all.sh.
ktmom said:
My bet is your ADB/fastboot are to old. Go back to post 9 and read the lower portion under edit2. You should also read forward from that point as there are additional issues that ChromeOS introduced with the noexec mounting of partitions. It will mean that without a workaround, you can not execute the flash-all.sh.
Click to expand...
Click to collapse
Hey there,
SO i decided to try the OTA sideload method on a friends PC - i got the following response through CMD prompt
Code:
C:\Users\LYALL\Downloads>adb sideload ota-file.zip
Total xfer: 1.00x 1
However the phone is reporting a failure verifying the file signature and giving
Code:
E: Error code: 21
What do you think is causing that? I saw that Google has a new browser based flash tool to allow for AOSP builds to flash - would using that work better for me do you think?
ptm
ptm said:
Hey there,
SO i decided to try the OTA sideload method on a friends PC - i got the following response through CMD prompt
Code:
C:\Users\LYALL\Downloads>adb sideload ota-file.zip
Total xfer: 1.00x 1
However the phone is reporting a failure verifying the file signature and giving
Code:
E: Error code: 21
What do you think is causing that? I saw that Google has a new browser based flash tool to allow for AOSP builds to flash - would using that work better for me do you think?
ptm
Click to expand...
Click to collapse
Make sure you have downloaded the correct OTA and for crosshatch coral. Use the sha256 checksum provided in the download page and ensure the file is not corrupted. I check the integrity of the file before using it especially if I've moved it since the last verification.
You are rebooting to recovery (not rescue mode) and using the OTA sideload action from *within* recovery, before using the adb command, right?
The Google update and repair tool is an option.
ktmom said:
Make sure you have downloaded the correct OTA and for crosshatch. Use the sha256 checksum provided in the download page and ensure the file is not corrupted. I check the integrity of the file before using it especially if I've moved it since the last verification.
You are rebooting to recovery (not rescue mode) and using the OTA sideload action from *within* recovery, before using the adb command, right?
The Google update and repair tool is an option.
Click to expand...
Click to collapse
I think Pixel 4 XL is Coral, not Crosshatch.
I have downloaded the OTA file thats third from the bottom on this page (https://developers.google.com/android/ota) which is the rom number - 10.0.0 (QQ1B.200105.004, Jan 2020).
Yes, followed the instructions and booted to recovery, selected 'update from adb' from within recovery and then checked
Code:
adb devices
to ensure it showed 'sideload'. I then ran the command
Code:
adb sideload ota_file.zip
The transfer seemed to work fine, but then i got the error above showing on the device.
I cant seem to use the Google update and repair tool, as I'm in the UK and it says its not supported.
I can get it working with a VPN but the carrier i'm on doesnt show, although i do have the option of selecting 'other' as the carrier - I'm happy to give that a go, but wanted to get your thoughts on it first. Will selecting carrier as 'other' work ok for a UK based phone?
ptm