Hi everyone. I am experiencing problems trying to flash RR Nougat to my Oneplus 3, currently on CM13 6.0.1. It just won't flash at all. I've wiped cache etc but it doesn't want to execute. I've also tried Lineage OS but failed, I have even tried pushing the file via Unified Android Toolkit and even that didn't work. Phone has an unlocked boot-loader (I'm pretty sure) USB debugging, root access etc. Unsure what the issue is so any help would be appreciated. This is what happened whilst using UAT.
Working out the best location to set for Internal Storage..
Waiting for Adb Mode
Device mode detected [device adb]
Pushing RR-N-v5.8.3-20170716-oneplus3-Weekly.zip to: /sdcard/
adb: error: cannot stat 'root\RR-N-v5.8.3-20170716-oneplus3-Weekly.zip': No such file or directory
File push did not work for sdcard
Setting push location to mnt/sdcard and trying again
Pushing RR-N-v5.8.3-20170716-oneplus3-Weekly.zip to: /mnt/sdcard/
adb: error: cannot stat 'root\RR-N-v5.8.3-20170716-oneplus3-Weekly.zip': No such file or directory
File push did not work for mnt/sdcard
Setting push location to storage/emulated/0 and trying again
Pushing RR-N-v5.8.3-20170716-oneplus3-Weekly.zip to: /storage/emulated/0/
adb: error: cannot stat 'root\RR-N-v5.8.3-20170716-oneplus3-Weekly.zip': No such file or directory
An Error Occured
The file did not push to the set location for some reason
Please report this in your device thread with details for more help
Press any key to return to the Main Menu..
Thank You.
I don't really have an answer for you but recently I tried to go back to stock, after I locked my bootloader I was unable to sideload anything with adb, have you tried flashing it with TWRP? Just a suggestion, are you able to use recovery at all, if uat can't find the directory, it could be a PC issue? I'm just throwing out ideas to try to help.
Update your adb drivers, now command prompt can push files larger then several mb's, don't know precisely how much.
Same problem I had couple of weeks back, don't know why but mine adb driver changed, set it back to the Google adb driver from sdk and the file was sideloaded.
Make sure you are on the latest firmware that is required.
I would just transfer through mtp or download on your op3, then just flash trough TWRP. That's what I do.
sv2203 said:
Update your adb drivers, now command prompt can push files larger then several mb's, don't know precisely how much.
Same problem I had couple of weeks back, don't know why but mine adb driver changed, set it back to the Google adb driver from sdk and the file was sideloaded.
Click to expand...
Click to collapse
Yup follow his method. This issue is somekind of adb sideload bug for huge files, name too long or not run as admin. Restarting PC, reinstall driver OP3 driver is another option if problem still persists.
Related
I'm in the process of routing my 2.2 evo. I'm running on a macbook pro right now but i'm running windows 7 via bootcamp. At first i downloaded all my files while i was using osx and then i copied them over to my c:\ BOOTCAMP partition and set up all the files and put them where they need to be ex. c:\android\tools\xxxxxxx.zip now i plugged in my evo and went to go transfer unrevoked to the sdcard in the command prompt and its not allowing me saying failed to copy permission denied. it didn't work so i redid all the downloading the files set up another directory all while on windows and i'm getting the same error. Can any one help me out with this?
you attempted via adb push?
yes i typed in adb push unrevoke-forever.zip /sdcard/ and it says could not copy "unrevoke-forever.zip" permission denied
I have the same problem
"C:\android\tools>adb push unrevoked-forever.zip /sdcard/
* daemon not running. starting it now *
* daemon started successfully *
failed to copy 'unrevoked-forever.zip' to '/sdcard//unrevoked-forever.zip': Perm
ission denied"
So what do I do to push these files to my evo? Thanks
Did you try
Code:
adb push unrevoked-forever.zip /sdcard/unrevoked-forever.zip
I dunno if it'll make a difference, but it might. Make sure you have USB debugging enabled on the phone (Settings --> Applications --> Development) and that you're setting it to charge-only when you plug it in.
If that doesn't work, I think you can just hook up the Evo in USB disk mode and copy the files that way instead of doing the adb push.
I got things to work by renaming the files and removing the dashes...weird
jspambox said:
I got things to work by renaming the files and removing the dashes...weird
Click to expand...
Click to collapse
Yeah, really weird. Glad that you got it working, though.
bump for this problem, anyone got a fix?
i was able to get all the files on as a disk drive when it goes to the next step adb shell should i go back into charge only mode or should i complete the rest of the process as a disk drive?
it only transfers the files over that will go to /data/local but not /sdcard and the rooting process isnt working for me! anyone care to give me a hand?
infoe said:
it only transfers the files over that will go to /data/local but not /sdcard and the rooting process isnt working for me! anyone care to give me a hand?
Click to expand...
Click to collapse
Your sdcard is not mounted. Select charge only on your phone's usb settings.
Hey-- try sliding down the notifcation bar, switching to disk drive mode then switching back to charge only mode. I was having the same problem and this seemed to fix it. Now I'm en route to my root...ed phone
^^^ Thanks! that worked.. i was searching online to figure out why i couldnt do this and your method of just redoing it worked!
thanks i was having the same problem, it worked for me.
I had the same problem. I switched the USB port and it started working.
So I have no idea why my G2 isn't being found with the htc sync but its not. I followed this thread here (http://forum.xda-developers.com/showthread.php?t=865685) I made sure i had the platform-tools installed before changing the path. I think this is the problem I am having. There are 2 paths that appear; One in user variables and then one in system variables. I have tried altering both but I am having no luck. Does anyone have any clue to what is going on?
HTC Sync will install the correct USB drivers for your G2. Although you cannot actually *run* HTC Sync with your G2 unless it is running a Sense (Desire Z) ROM. So just install it but don't try to actually run it or sync with it.
It's the System Variables path that you want to change, to add the appropriate directories. This just lets you run adb from any directory on your PC. Even if you haven't got it added, it should still work if you "cd" to the directory where adb resides (in which case you will need to put any files into there that you wish to "push" to your phone).
What is the problem you're having, is it saying "no internal command" or similar ?
DressedUpPanda said:
So I have no idea why my G2 isn't being found with the htc sync but its not. I followed this thread here (http://forum.xda-developers.com/showthread.php?t=865685) I made sure i had the platform-tools installed before changing the path. I think this is the problem I am having. There are 2 paths that appear; One in user variables and then one in system variables. I have tried altering both but I am having no luck. Does anyone have any clue to what is going on?
Click to expand...
Click to collapse
The PATH issue, relates to ADB, if you are running into errors like:
'adb' is not recognized as an internal or external command
Click to expand...
Click to collapse
When executing ADB commands that is your issue, it can be resolved by adding the path where ADB lives to either your user or system PATH in Windows. The PATH is irrelevant if you are running ADB from the folder where the ADB files live.
The other (common) issue is drivers, where ADB is working but won't see your device. Do you see an "ADB Device" or similar with a yellow icon in your device manager when your phone is connected to your PC? If so you don't have the correct driver loaded. The only reason you install HTC Sync is to load this driver but the driver can also be loaded separately.
Sorry to hi-jack this thread, and since I'm new to adb I might as well use this.
I have adb running, did the file paths and everything. I'm just trying to test it out, since I'm already rooted using visionaryr13 as well as s-off. Went back and gfree over that, and I've also verified through terminal emulator on my phone, but I'm just testing my skills with adb and failing miserably. I Have d/l the verify file, and unzipped in a folder inside my downloads folder I might add.
When it says:
"
VERIFY (using "gfree_verify")
Now you can try using a new SIM card to verify that it worked.
In addition you can use gfree_verify to verify the state of your locks.
Download gfree_verify.zip from gfree_verify_v01.zip
ON YOUR PC:
Unzip gfree_verify_v01.zip to a place on your computer. Navigate to where the file is on your computer, and type:
$ adb push gfree_verify /data/local
"
I'm having a problem with the navigate to where the file is on your computer and type. I have cmd open, and have tried everyway but the right way to push this through. This is the error I'm getting.
cannont stat 'gfree_verify': no file or directory
EDIT: I got it and I'm sure everyone is laughing at this idiot. So in the cmd prompt you have to navigate to where you put the folder, then push the file to your phone, DUH!
OK, stupid question number two, since I answered number 1.
When you are in a adb shell in your cmd, how do you get out of it besides exiting cmd?
mrbmg said:
When you are in a adb shell in your cmd, how do you get out of it besides exiting cmd?
Click to expand...
Click to collapse
Type "exit".
ty ty.
Ok so I updated something in adb and it's not working. LOL, well restarted, and now the sdk manager is updating some more stuff so hopefully that is the reason I was not getting in.
EDIT: everything is working now.
Ty stevie, really appreciate all your hard work helping us noobies man!
steviewevie said:
HTC Sync will install the correct USB drivers for your G2. Although you cannot actually *run* HTC Sync with your G2 unless it is running a Sense (Desire Z) ROM. So just install it but don't try to actually run it or sync with it.
It's the System Variables path that you want to change, to add the appropriate directories. This just lets you run adb from any directory on your PC. Even if you haven't got it added, it should still work if you "cd" to the directory where adb resides (in which case you will need to put any files into there that you wish to "push" to your phone).
What is the problem you're having, is it saying "no internal command" or similar ?
Click to expand...
Click to collapse
Ya my problem is that when I finally get to do the commands it tells me that "adb is not recognized as an internal or external command.
@raitchison- I checked my device manager and it says that i have the most current driver for the phone. Unfortunately it doesn't say anything about 'adb' it shows my 'portable devices' then into my 'E:/' drive and in the details there it stats 'Android phone'
DressedUpPanda said:
Ya my problem is that when I finally get to do the commands it tells me that "adb is not recognized as an internal or external command.
@raitchison- I checked my device manager and it says that i have the most current driver for the phone. Unfortunately it doesn't say anything about 'adb' it shows my 'portable devices' then into my 'E:/' drive and in the details there it stats 'Android phone'
Click to expand...
Click to collapse
You just need to add the correct directories onto the end of the path in System Variables. Go right to the end of the path, and then separated by semi-colons (do not put spaces in) add the two pathnames of the tools and platform-tools folder of the Android SDK. If you have done that and it is still not working, copy and paste the path variable up here and we can try checking it.
As I said, you could "cd" to the folder with adb in it, and then run "adb devices" from there, and it should work. But setting up the path will make it more convenient.
steviewevie said:
You just need to add the correct directories onto the end of the path in System Variables. Go right to the end of the path, and then separated by semi-colons (do not put spaces in) add the two pathnames of the tools and platform-tools folder of the Android SDK. If you have done that and it is still not working, copy and paste the path variable up here and we can try checking it.
As I said, you could "cd" to the folder with adb in it, and then run "adb devices" from there, and it should work. But setting up the path will make it more convenient.
Click to expand...
Click to collapse
Ok well here is the path that i have set up.
- C:\AndroidSDK\tools;C:\AndroidSDK\platform-tools
I saved the file right to my "C" drive so thats why i didn't go to the program files. I also changed the name of the folder so it was easier to type.
Edit: I got it to finally recognize my device. I went back to my path and found that i had spaced in between my ';' and 'C:/' so thank you very much Stevie on making me double check it!!!
So, my problem is that I have recently unlocked the bootloader on my HTC One X using my Mac and the very helpful guide provided on this YouTube link
http://youtu.be/8Y3VbFJIwWU
No problems with the process in that video and I've gotten to the end with the phone bootloader definitely.
My problem is that I've then attempted to install a custom ROM from the SD card. Again, this seems to work fine, but upon reboot I'm immediately hit with a continual pop-up 'unfortunately, the process com.android.phone has stopped' with the only option to press ok. It loops continuously.
I suspect I may have to reinstall the ROM onto the SD card, but this is my problem. I cannot get my phone's USB access to work on my Mac as I am stuck with the above pop-up preventing me. I can't seem to access it via Recovery either.
Can I use fastboot to 'flash' over the *.img or *.zip of a new ROM to get it onto the SD card? Stuck with a phone I can't use otherwise. :crying:
Thanks.
Mount usb storage from the recovery.
Sent from my HTC One X using xda app-developers app
or while in recovery type
Code:
adb push rom.zip sdcard/
Thanks for that, athulele . :good:
I have tried that. On a Mac, for USB access requires that I use software called 'Android File Transfer' rather than the way Windows would do it. That software doesn't kick in via Recovery mounting. So, I'm going to need a different approach.
Since I have Windows installed via Bootcamp, I think I'll try to connect the phone up via Windows and see whether I can access the SD card via USB using that route.
Any other help is most welcome.
you do not need that file, just boot into recovery and type the command above... it's the easiest way
matt95 said:
you do not need that file, just boot into recovery and type the command above... it's the easiest way
Click to expand...
Click to collapse
Having booted into recovery, using Terminal on my Mac and typing
adb push sentinelrom_v4_30_endeavoru.zip sdcard/
gives the following message:
-bash: adb: command not found
Am I doing something wrong here?
well, have you got the sdk installed on your mac?
matt95 said:
well, have you got the sdk installed on your mac?
Click to expand...
Click to collapse
I've now downloaded the sdk for mac. It's a adt bundle folder with many files inside. I've installed 'Eclipse' but I'm still getting the same message as before from the Terminal. What else do I need to do here?
Im not into macs .... but don't you need to enter sudo commands before the adb/fastboot commands ?
no, he only needs to navigate to the adb directory with the terminal and then type
Code:
./adb push rom.zip sdcard/
matt95 said:
no, he only needs to navigate to the adb directory with the terminal and then type
Code:
./adb push rom.zip sdcard/
Click to expand...
Click to collapse
Hi matt95
I'm grateful for the help you are giving me here. I've found the adb file within the following downloaded directory path:
act-bundle-mac-x86_64-20130219 - sdk - platform-tools - adb
When I changed directory in Terminal to this path and ensured the specific rom.zip was also in that path, Terminal is still giving me this:
./adb push sentinelrom_v4_30_endeavoru.zip sdcard/
-bash: ./adb: No such file or directory
I must be doing something not right. Please help further.
that's strange, could you provide me the platform-tools folder and the rom.zip folder? i'll write down what you exactly have to write...
matt95 said:
that's strange, could you provide me the platform-tools folder and the rom.zip folder? i'll write down what you exactly have to write...
Click to expand...
Click to collapse
Folder contents as described.
Thanks.
ok now i need their directory, for ex. /User/yourusernane/Docuemnts/ecc ecc......
matt95 said:
ok now i need their directory, for ex. /User/yourusernane/Docuemnts/ecc ecc......
Click to expand...
Click to collapse
/Users/srafferty73/Downloads/adt-bundle-mac-x86_64-20130219/sdk/platform-tools
and
/Users/srafferty73/Downloads/adt-bundle-mac-x86_64-20130219/sdk/platform-tools/sentinelrom_v4_30_endeavoru
Thanks.
ok, now open the therminal ans type
Code:
cd /Users/srafferty73/Downloads/adt-bundle-mac-x86_64-20130219/sdk/platform-tools
./adb push (drag the rom.zip into terminal) sdcard/
now it should work
matt95 said:
ok, now open the therminal ans type
Code:
cd /Users/srafferty73/Downloads/adt-bundle-mac-x86_64-20130219/sdk/platform-tools
./adb push (drag the rom.zip into terminal) sdcard/
now it should work
Click to expand...
Click to collapse
Slowly making progress. Latest Terminal message after doing that reads 'error: device not found'.
I am using ClockworMod Recovery v5.8.2.7 and have clicked on 'mount /sdcard'. I have tried to 'mount USB storage' but am getting an error message which reads 'E: Unable to open ums lunfile (No such file or directory).'
What should I do next?
Thanks.
fingerbob said:
Slowly making progress. Latest Terminal message after doing that reads 'error: device not found'.
I am using ClockworMod Recovery v5.8.2.7 and have clicked on 'mount /sdcard'. I have tried to 'mount USB storage' but am getting an error message which reads 'E: Unable to open ums lunfile (No such file or directory).'
What should I do next?
Thanks.
Click to expand...
Click to collapse
Flash a newer recovery.
Mr Hofs said:
Flash a newer recovery.
Click to expand...
Click to collapse
I managed to find a copy of ClockworkMod Recovery v5.8.4.0 and flashed this as advised. This has somehow enabled the USB facility on my phone to start working again and I can replace the ROM I've downloaded onto it.
I just tried reinstalling the ROM I had again, but once again got the original message stated in my first post. I'm about to now try a different ROM to see if that makes any difference.
:good:
I am unable to flash anything even official firmware with official recovery, when in adb sideload mode. whenever i try to push a zip to install terminal says:
C:\Users\nd4ios\Desktop>adb sideload a.zip
loading: 'a.zip'
* cannot read 'a.zip' *
the file is named a.zip
it is in the Desktop folder
ive tried doing this like this:
Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.
C:\Windows\system32>adb sideload C:\Users\nd4ios\Desktop\a.zip
loading: 'C:\Users\nd4ios\Desktop\a.zip'
* cannot read 'C:\Users\nd4ios\Desktop\a.zip' *
C:\Windows\system32>
but same issue
ive tried reinstalling the drivers -(adb, fastboot, and device)-
no avail
ive also tried moving the zip file to the system32 folder and still same error. ive tried multiple zips and nothing.
Ive looked at the ram - practically no ram usage on my pc
ive tried installing twrp recovery but it never can boot into it - just turns to black screen and stays there. (tried multiple different versions of twrp)
ive looked online for help and nothing has helped so far which is why im turning to here.
use this ADB . Yours is old
here
also use TWRP Recovery 3.0.2-1.28 if you are on Oxygen OS Open beta or 4.0 ( N)
it's a windows problem .. a simple restart will solve it ..
not windows probem but probably driver
Go to Computer/Devic manager /Kedacom USB devices or something similar...
change adb driver to ADB generic
thanks, well i was finally able to install the previous firmware via booting and transfering the zip file to the internal storage and installing it from there. so it was a windows problem or driver. im installing this now and hope it fixes it for the future.
I had the same problem with my computer not recognizing my phone with trying to transfer file and flash joints. I went to device manager > right click mtp > update driver software > browse my computer > let me pick > mtp USB device > happy me ??
ok well ive tried using the adb drivers you mentioned and it is still coming up with the same error, so im going to try booting into linux and trying it from there
It's because the ADB executable isn't large address aware and so it fails to allocate memory when you're trying to sideload something big (>1GB) like the OOS 4.0 for our OnePlus 3. You need an ADB that's been made large address aware or you can do it yourself if you have Visual Studio installed on your machine. I'd provide it myself but I've already sworn off posting files here.
i have Visual Studio Enterprise - i got it from being a student, so how would i go about making the adb large address aware? thanks
i found an app online to convert the adb to 64bit and see if that works on it.
ok so what you said is the issue, apparently my adb is not large address aware, as i tried pushing a zip file under a 1GB and it worked but when i push a file over it says it cannot read.
now if only if there was a thanks button so i could add a thank you
ok ive finally got it to work
heres what i did:
i used the original adb.exe in my C:\adb folder
then i right clicked the program and clicked properties and under compatability i chose run as administrator (probably dont need to do this but did it as an extra)
then used https://www.techpowerup.com/forums/threads/large-address-aware.112556/ to convert it to 64bit to allow for long address awareness. and viola it works.
also a side note:
does not work on the minimal adb and fastboot.exe adb program
HI all,
I've been trying to push a ROM to my phone using ADB push and it says that it works, but then it says
"adb: error: failed to read copy response"
I can't find it in the sdcard folder either.
When I have a ROM installed, adb push works, but when I fastboot format userdata it doesn't for some reason.
Anyone got any idea whats going on?
Same problem here with adb - Install
coud install 1 APK with --no-streaming
after this every try for another APK gives Message
1 File pushed with *++*MB/s in ***seconds
---Short brake few seconds and than getin' the error from Above
Install failed! .adb: error: failed to read copy response
I just replied on another adb topic, but I was having adb push issues after years of no problems. I ended up using a different computer. If you have the option, hopefully this works for you.
One additional thing would be to check for updated versions of ADB and Fastboot before switching computers.
I had slow transfers that always stopped with this error on OxygenOS on my OnePlus 9R. I rebooted into TWRP and tried again, and it was much faster and successful.