So I tried to flash the zip file I did everything what they said on website http://downloads.oneplus.net/oneplus-3t/oneplus_3t_oxygenos_openbeta_3/ but when I tried command adb and this showed up http://imgur.com/9ScdkMC My device haven't been rooted or anything so it shouldn't be a problem.
I believe you are missing the file extension for the zip. It'll be easier if your rename the file (for example, rename it to OOSOB3). OnePlus releases the updates as zips, so you'll have to specify the file format.
In adb, use the command:
adb sideload OOSOB3.zip
Note three things:
1) The zip file has to be in the same folder as where you opened the command prompt, otherwise you will have to specify its exact location (for example, /C/user/yourname/desktop/OOSOB3.zip)
2) You have to specify the file name, but you can name it anything you want (such as OOSOB3.zip in the example). You do not have to add the ".zip" when renaming your file if your operating system is already hiding the file extensions, you only have to specify .zip in the command prompt.
3) You must include the .zip at the end of the command
Anova's Origin said:
I believe you are missing the file extension for the zip. It'll be easier if your rename the file (for example, rename it to OOSOB3). OnePlus releases the updates as zips, so you'll have to specify the file format.
In adb, use the command:
adb sideload OOSOB3.zip
Note three things:
1) The zip file has to be in the same folder as where you opened the command prompt, otherwise you will have to specify its exact location (for example, /C/user/yourname/desktop/OOSOB3.zip)
2) You have to specify the file name, but you can name it anything you want (such as OOSOB3.zip in the example). You do not have to add the ".zip" when renaming your file if your operating system is already hiding the file extensions, you only have to specify .zip in the command prompt.
3) You must include the .zip at the end of the command
Click to expand...
Click to collapse
I did what you've told me but it didn't work, I will try to download the zip file again
ms1021 said:
I did what you've told me but it didn't work, I will try to download the zip file again
Click to expand...
Click to collapse
Which part didn't work?
---------- Post added at 07:12 PM ---------- Previous post was at 07:07 PM ----------
If you are renaming the file, make sure you don't accidentally rename it to OOSOB3.zip.zip.
In Windows, set the file manager to show you "File Name Extensions" so there's no confusion.
Anova's Origin said:
Which part didn't work?
---------- Post added at 07:12 PM ---------- Previous post was at 07:07 PM ----------
If you are renaming the file, make sure you don't accidentally rename it to OOSOB3.zip.zip.
In Windows, set the file manager to show you "File Name Extensions" so there's no confusion.
Click to expand...
Click to collapse
That's the message I get when I do as you told me
C:\Users\Miłosz_PC\Desktop>adb sideload OOSOB3.zip
loading: 'OOSOB3.zip'
* cannot read 'OOSOB3.zip' *
ms1021 said:
That's the message I get when I do as you told me
C:\Users\Miłosz_PC\Desktop>adb sideload OOSOB3.zip
loading: 'OOSOB3.zip'
* cannot read 'OOSOB3.zip' *
Click to expand...
Click to collapse
It might be that your command prompt is not opening where you zip file is.
Move your zip file to your desktop, then hold shift and right click your desktop. From the menu, select "Open command window here"
Test to make sure your adb is enabled system-wide by simply typing in:
adb
If a context menu shows up with a list of commands that you can use, then sideload as described earlier from there.
You can also test to make sure that adb can detect your phone by typing in:
adb devices
This will return your phone's serial number if it is properly connected.
Anova's Origin said:
It might be that your command prompt is not opening where you zip file is.
Move your zip file to your desktop, then hold shift and right click your desktop. From the menu, select "Open command window here"
Test to make sure your adb is enabled system-wide by simply typing in:
adb
If a context menu shows up with a list of commands that you can use, then sideload as described earlier from there.
Click to expand...
Click to collapse
I cannot see sideload command in this menu :/
ms1021 said:
I cannot see sideload command in this menu :/
Click to expand...
Click to collapse
It won't show every command, just the most commonly used ones. The point of that was just to make sure that you can use adb from your desktop. Sideload should work anyways.
Also, make sure you have enabled USB debugging in the developer's options.
Anova's Origin said:
It won't show every command, just the most commonly used ones. The point of that was just to make sure that you can use adb from your desktop. Sideload should work anyways.
Also, make sure you have enabled USB debugging in the developer's options.
Click to expand...
Click to collapse
I enabled USB debugging but I get the same thing, maybe I should use "Install from internal storage" option :/
ms1021 said:
I enabled USB debugging but I get the same thing, maybe I should use "Install from internal storage" option :/
Click to expand...
Click to collapse
Eh, internal storage works just as well. Bummer you couldn't get adb working, but I guess it doesn't really matter if you rarely use it.
Anova's Origin said:
Eh, internal storage works just as well. Bummer you couldn't get adb working, but I guess it doesn't really matter if you rarely use it.
Click to expand...
Click to collapse
I did it with internal storage option thanks for help
Related
Ok so Ive seen a few people posting in the dev section that they cant get adb working. So heres a quick write up on how to get it working on windows and linux (ubuntu) machines. Follow these directions and you should have no problems. If you notice any errors dont hesitate to point them out to me! This is meant to help, not confuse.
First you need to download ADB.
Click here and select the download appropriate for your operating system: Android SDK
For Windows:
1.Extract the .zip file you downloaded and make a note of where you extracted to.
2.Go into the extracted android-sdk_r12-windows folder.
(if you go into this folder and have another folder named 'android-sdk_r12-windows' then cut and paste it outside of the extracted folder)
3.Open SDK Manager. Let it do its thing and then make sure 'Select All' is checked and click 'Install'
4.When its done it will say ADB has been updated and needs to restart. Select OK.
5.Now go back to your android-sdk_r12-windows folder and you should have a new folder called 'platform-tools'
6.Go into that folder and you should see 'adb'
7.Now to make things easy you're going to create an adb shortcut:
Right click your desktop and choose to create a new shortcut.
It will ask you to type a location for the shortcut. Enter "CMD" without the "".
Click 'Next'
For the name type "ADB" without the "".
Now right click the shortcut you just created and select 'Properties'
Now in the Properties dialog where it says Start In, type the path to your Android SDK foler. In my case I extracted the folder to my desktop, so my path would be C:\Users\Jason\Desktop\android-sdk_r12-windows.
Then click 'OK'
Now all you have to do is click this shortcut and you're automatically in adb in the command prompt.
For Linux:
Everything above is going to be pretty much the same except for the way you get into adb.
So do steps 1-6 above.
Now, instead of a shortcut you're going to open terminal and type the following:
sudo cp <path to your sdk platform-tools folder> /usr/bin
(for <path to your sdk platform-tools folder> it will depend on where you extracted the .zip to. In my case it would look like this because I extracted it to my desktop on MY computer:
sudo cp /home/jason/Desktop/android-sdk-linux_x86/platform-tools/adb /usr/bin
now you can access adb directly from Terminal.
Now I dont own a Mac so Im not going to put a writeup for that. But someone can feel free to post one and I can add it to my original post.
Thats it you now have access to adb on your computer! Go flash alternate recoveries and roms and be merry in 3D!
I am on my mobile app right now and haven't been able to find the link yet in the development section, but can pretty much guarantee that most ppl are having the issue I had with error messages about being denied BC u don't have permission. You have to change the permissions to get read and write access. If someone with better knowledge than me knows about it, then please feel free to elaborate. I spent hours trying to find answers before I stumbled across how to fix permissions. I know it requires u to enter adb shell and the into su to enter the code to change permissions so u can use adb push as well as adb root, etc. If no one addresses this shortly then I will find the link on my laptop and update.
Sent from my LG-P925 using xda premium
http://forum.xda-developers.com/showthread.php?t=1259603
Sent from my LG-P925 using xda premium
Holy cow! I have a new found respect for developers. I wanted the adb tools just so I can flash CWM recovery. Now I'm having to download updated java and there's a ton of stuff to download for the SDK tools.
I'll have to admit that I loved my Captivate in how easy it was to flash CWM and roms and really anything else.
how can i do this if my phone is bricked stuck on lg logo
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
trying to push file but not having success.
are there any different commands than the regular commands for the G2?
adb push update.zip /sdcard
is there something i'm missing?
CWM puts you in ADB mode on launch right?
adb devices shows phone attached recovery
adb push update.zip /sdcard returns nothing
am i missing a command? do I need to open a shell? or let it sit for awhile as it is a 1gb+ file
JoeProcopio said:
adb devices shows phone attached recovery
adb push update.zip /sdcard returns nothing
am i missing a command? do I need to open a shell? or let it sit for awhile as it is a 1gb+ file
Click to expand...
Click to collapse
You would need to specify the correct path... /sdcard is not a real path (its a symbolic link), try
adb push update.zip /data/media/0
that could be an issue, lol
hadn't done pushes for a long time so i haven't used the command
JoeProcopio said:
that could be an issue, lol
hadn't done pushes for a long time so i haven't used the command
Click to expand...
Click to collapse
Actually, the more I think about, that is incorrect as well, you have to specify the filename of the destination too...
adb push update.zip /data/media/0/update.zip
would be more correct.
once i hit enter, what should i see? should i see a progress bar? the file is 1.3GB, will it take a while?
yup....took awhile! trying the flash now
JoeProcopio said:
yup....took awhile! trying the flash now
Click to expand...
Click to collapse
I'm having a similar issue - seems like adb is set up correctly, but I'm unsure if the push command is working. About how long did you have to wait? Did you have any notifications on progress, etc?
Thanks!
---------- Post added at 10:26 AM ---------- Previous post was at 10:08 AM ----------
Nvm! Worked out - just took some time like the OP's.
For future reference - it took mine about 15-20 minutes to transfer a file that was about 1.3gb (similar to the OP's) and the terminal window (using OSX) showed a blank line after submitting the push command. The blank line was replaced by a summary of the file transfer (speed, time, and size) once the transfer was completed.
Ok there is a lot info about this however I have a few issues that makes it difficult for me to get past.
I unlocked and rooted just fine. No issues.
I flashed the elemental kernel as I wanted the knock on feature. That was when I ran into problems and my backup doesn't work.
I started getting the "com.htc.htcdailer" isn't responding issue. Then the phone reboots. I am not up long enough to load a rom to flash either.
When I try to sideload anything it doesn't work. I did update all the SDK files like I found in some searches. No go.
I am at a loss now what to do. Any thoughts?
Thanks
mothmansound said:
Ok there is a lot info about this however I have a few issues that makes it difficult for me to get past.
I unlocked and rooted just fine. No issues.
I flashed the elemental kernel as I wanted the knock on feature. That was when I ran into problems and my backup doesn't work.
I started getting the "com.htc.htcdailer" isn't responding issue. Then the phone reboots. I am not up long enough to load a rom to flash either.
When I try to sideload anything it doesn't work. I did update all the SDK files like I found in some searches. No go.
I am at a loss now what to do. Any thoughts?
Thanks
Click to expand...
Click to collapse
Boot into TWRP, download this driver:
http://www.koushikdutta.com/post/universal-adb-driver
Connect it to your PC in TWRP mode to your computer and Windows Device Manager, update the driver pointing to the one downloaded.
It should install with out an issue and the device should be detected thru ADB. Now all you need to do is push the rom via ADB. I recommend Cyanogenmod as its very small to push. I cannot quite remember the command to push a file as it can be complicated in the folder parts, but use this to push easily:
http://skipsoft.net/download/toolkit/nexus7toolkit/Google_Nexus_7_ToolKit_v5.0.0.exe
Ignore the fact that it's for the Nexus 7. Once it's installed, navigate to My Computer, click your hard drive and you should see a folder called Nexus 7 toolkit or similar (if not there check in Program Files). Look for an exe called "tkmain" and create a shortcut of it on your desktop. Keep that folder section open for now. Double click it. MAKE SURE YOU CAN SEE YOUR DEVICE SERIAL ON TOP TO ASSURE ITS CONNECTED. Now go to the same folder you saw the tkmain.exe and you should see a folder that says "Put Files to Push here". Drop the rom in there. I recommend naming it something short like "cyanogen.zip" for example. Now back on the toolkit, select the option that says Push file (I think it's option 13), answer Yes to the insecure boot image question, when it says select a file to push you should see the name of the rom zip , type it exactly as its name/you renamed it. When it says select a location, select /sdcard/ and proceed with the rest. It may seem like nothing is going on, and it may say something about "failed: success" beforehand, but trust me it's pushing, once it says complete, your ready to flash the rom.
Remember that if your S-Off, you need to flash the boot.img seperately via fastboot.
Crossvxm said:
Boot into TWRP, download this driver:
http://www.koushikdutta.com/post/universal-adb-driver
Connect it to your PC in TWRP mode to your computer and Windows Device Manager, update the driver pointing to the one downloaded.
It should install with out an issue and the device should be detected thru ADB. Now all you need to do is push the rom via ADB. I recommend Cyanogenmod as its very small to push. I cannot quite remember the command to push a file as it can be complicated in the folder parts, but use this to push easily:
http://skipsoft.net/download/toolkit/nexus7toolkit/Google_Nexus_7_ToolKit_v5.0.0.exe
Ignore the fact that it's for the Nexus 7. Once it's installed, navigate to My Computer, click your hard drive and you should see a folder called Nexus 7 toolkit or similar (if not there check in Program Files). Look for an exe called "tkmain" and create a shortcut of it on your desktop. Keep that folder section open for now. Double click it. MAKE SURE YOU CAN SEE YOUR DEVICE SERIAL ON TOP TO ASSURE ITS CONNECTED. Now go to the same folder you saw the tkmain.exe and you should see a folder that says "Put Files to Push here". Drop the rom in there. I recommend naming it something short like "cyanogen.zip" for example. Now back on the toolkit, select the option that says Push file (I think it's option 13), answer Yes to the insecure boot image question, when it says select a file to push you should see the name of the rom zip , type it exactly as its name/you renamed it. When it says select a location, select /sdcard/ and proceed with the rest. It may seem like nothing is going on, and it may say something about "failed: success" beforehand, but trust me it's pushing, once it says complete, your ready to flash the rom.
Remember that if your S-Off, you need to flash the boot.img seperately via fastboot.
Click to expand...
Click to collapse
Thank you very much for the help.
When I get to the point of typing which file to push the application cannot find the file.
I have been flashing roms for a while since the OG Droid and I can't understand why this has happened. I'm close to being beat.
mothmansound said:
Thank you very much for the help.
When I get to the point of typing which file to push the application cannot find the file.
I have been flashing roms for a while since the OG Droid and I can't understand why this has happened. I'm close to being beat.
Click to expand...
Click to collapse
The ROM must be in the folder that says "put files to push here" (make sure its that folder as I remember that another one seems similarly worded) from the toolkit program directory. You have to manually place your file there. If anything, close the toolkit and reopen it (remember, tkmain, the other section of the program is all Nexus related) and try again. Remember also to shorten the name so you don't have to type it in completely. Somewhere above where your supposed to type the file name you should see your ROM file. That's when you type it in exactly as you see it, for example, "rom.zip" you will type it in exactly like that.
Crossvxm said:
The ROM must be in the folder that says "put files to push here" (make sure its that folder as I remember that another one seems similarly worded) from the toolkit program directory. You have to manually place your file there. If anything, close the toolkit and reopen it (remember, tkmain, the other section of the program is all Nexus related) and try again. Remember also to shorten the name so you don't have to type it in completely. Somewhere above where your supposed to type the file name you should see your ROM file. That's when you type it in exactly as you see it, for example, "rom.zip" you will type it in exactly like that.
Click to expand...
Click to collapse
Yessir I double and triple checked that, I can't get it to find the file. I did rename a couple of different ways and tried with and without the".zip" part. No luck. I do appreciate the help.
mothmansound said:
Yessir I double and triple checked that, I can't get it to find the file. I did rename a couple of different ways and tried with and without the".zip" part. No luck. I do appreciate the help.
Click to expand...
Click to collapse
Do you have an adb/fastboot folder set up? If so, time for some manual method. Grab the ROM zip and put it in the same folder as your ADB and fastboot folder. Start adb thru command prompt then type in:
Code:
adb push ROM.zip /storage/sdcard
Hopefully I remembered it correctly. Should be that way.
Crossvxm said:
Do you have an adb/fastboot folder set up? If so, time for some manual method. Grab the ROM zip and put it in the same folder as your ADB and fastboot folder. Start adb thru command prompt then type in:
Code:
adb push ROM.zip /storage/sdcard
Hopefully I remembered it correctly. Should be that way.
Click to expand...
Click to collapse
Its saying device not found and doesn't seem to push.
Crossvxm said:
Do you have an adb/fastboot folder set up? If so, time for some manual method. Grab the ROM zip and put it in the same folder as your ADB and fastboot folder. Start adb thru command prompt then type in:
Code:
adb push ROM.zip /storage/sdcard
Hopefully I remembered it correctly. Should be that way.
Click to expand...
Click to collapse
Its saying device not found and doesn't seem to push.
I finally got the RUU to work. What a week and seems fine now.
Last piece of advice hopefully. All I want is the tap to wake feature. Stock is fine.
What is the best way to do that? When I tried using other kernals is when I ran into problems.
Thanks for the help.
mothmansound said:
I finally got the RUU to work. What a week and seems fine now.
Last piece of advice hopefully. All I want is the tap to wake feature. Stock is fine.
What is the best way to do that? When I tried using other kernals is when I ran into problems.
Thanks for the help.
Click to expand...
Click to collapse
Lol i misread that disregard the rest. What custom kernel are you trying to use? Remember each device is the same but also different. I had 2 LG G2s that would not double tap to wake, but would double tap to sleep. All the rest of them worked perfectly. Have also came across friends with G2s that wouldnt work
mothmansound said:
I finally got the RUU to work. What a week and seems fine now.
Last piece of advice hopefully. All I want is the tap to wake feature. Stock is fine.
What is the best way to do that? When I tried using other kernals is when I ran into problems.
Thanks for the help.
Click to expand...
Click to collapse
Best way is to flash the kernel in my signature. After you flash it, double tap to wake should be working automatically.
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?