i tried search everywere and im sorry if im opening a new topic.
Aniway my OPO3 just arived , the only issue is its stuck at 3.1.3 oxygenOS and if i try search for updates it says, the device is updated......... so i wanted to try sideload atleast the 3.2.0 update but when i enter the command adb sideload < zip name > the resoult is
loading: 'zipname'
* cannot read 'zipname' *
can someone figure it out better than me?
thank you everyone
athais said:
i tried search everywere and im sorry if im opening a new topic.
Aniway my OPO3 just arived , the only issue is its stuck at 3.1.3 oxygenOS and if i try search for updates it says, the device is updated......... so i wanted to try sideload atleast the 3.2.0 update but when i enter the command adb sideload < zip name > the resoult is
loading: 'zipname'
* cannot read 'zipname' *
can someone figure it out better than me?
thank you everyone
Click to expand...
Click to collapse
Try to sideload the whole rom instead. That worked for Me. Did you forget to add the ”zip" at the End?
markusviktorius said:
Try to sideload the whole rom instead. That worked for Me. Did you forget to add the ”zip" at the End?
Click to expand...
Click to collapse
nono i do type the filename.zip
also im new of the android
athais said:
nono i do type the filename.zip
also im new of the android
Click to expand...
Click to collapse
Are you connected to adb? Have you checked that you are connected by writing adb devices?
markusviktorius said:
Are you connected to adb? Have you checked that you are connected by writing adb devices?
Click to expand...
Click to collapse
yup i do those steps: put the oneplus in sidelode mode, open adb and typing : adb devices then i do adb sideload oneplus.zip and after
saying: loading oneplus.zip
cannot read oneplus.zip
Print screen when typing adb devices?
markusviktorius said:
Print screen when typing adb devices?
Click to expand...
Click to collapse
there isnt much to print screen, simply he found my device with his serial number and say its connected thats all i just can't understand why adb can't read the zip
Cant you just write adb sideload and then drag the file Into the commandline?
markusviktorius said:
Cant you just write adb sideload and then drag the file Into the commandline?
Click to expand...
Click to collapse
tried this also but if i try drag the zip nothin happen, laso i tried extract the zip and it say the image is damaged
Download from another link then?
don't ask me how but seem adb sideload have managed to work ^^. aniway ty for some tip mark
I have the same problem.
If I do the update it's erase all my data?
Sent from my ONEPLUS A3000 using Tapatalk
Download a vpn and use uk's sever then search for update. It will show you an update available. Disable vpn and download and install the update normally
I try to do this but it's not work
Sent from my ONEPLUS A3000 using Tapatalk
Did you make it work, I'm stuck with 3.1.3. I dont know how to make the adb sideload.
I rename the zip file to oneplus.zip and then type "sdb sideload oneplus.zip" and say cannot read oneplus.zip.
I know I got the download right because I can open the zip file.
Related
I wrote this guide a while back after fixing a friends phone, it has worked on others too so i decided id post it here for anyone that ran into this issue later down the road and did not want to run a ruu. This also works great if you want to start fresh before flashing roms.
Basically all this does it swap out recovery's and clean the SD, give it a fresh start.
You can find the full guide & Video here http://forums.team-nocturnal.com/showthread.php/1050
This involves unnecessarily deleting the contents of the internal sdcard.
The following method works 99% of the time, albeit in linux only:
1: reboot into recovery & do a mount usb storage (no mount sdcard)
this will just present your internal storage as a mass storage device to the system
2: do a
fsck.vfat /dev/sdX or /dev/ubX (whatever it gets detected as) - you can find out via (dmesg|tail)
Analogically, you can fix your data partition if it got corrupted.
You need to do it from recovery since not all roms have the fsck binaries available:
from recovery (copy - paste, unless you know what you're doing):
umount /cache
for x in {2,3,5}, do fsck.ext4 -fyD /dev/block/mmcblk0p1$x;sync;done;clear;echo done
XsMagical said:
I wrote this guide a while back after fixing a friends phone, it has worked on others too so i decided id post it here for anyone that ran into this issue later down the road and did not want to run a ruu. This also works great if you want to start fresh before flashing roms.
Basically all this does it swap out recovery's and clean the SD, give it a fresh start.
You can find the full guide & Video here http://forums.team-nocturnal.com/showthread.php/1050
Click to expand...
Click to collapse
Hi XsMagical this link no longer works. Can you provide me with the guide I'm having the issue with the corrupted SD card and my htc one x is bricked.
movadoevo8 said:
Hi XsMagical this link no longer works. Can you provide me with the guide I'm having the issue with the corrupted SD card and my htc one x is bricked.
Click to expand...
Click to collapse
what is your base number and hboot ?normally the sdcard thing is fixed long time ago
One-X-master said:
what is your base number and hboot ?normally the sdcard thing is fixed long time ago
Click to expand...
Click to collapse
How do i locate the Hboot number is that the serial# if so here it is HT265W300361
movadoevo8 said:
How do i locate the Hboot number is that the serial# if so here it is HT265W300361
Click to expand...
Click to collapse
no reboot into fastboot and you will see it there.... and base number you can see in settings/about then somewhere there
One-X-master said:
no reboot into fastboot and you will see it there.... and base number you can see in settings/about then somewhere there
Click to expand...
Click to collapse
hboot = 1.14.0002
movadoevo8 said:
hboot = 1.14.0002
Click to expand...
Click to collapse
do you have the one xl? try to update it to latest base
One-X-master said:
do you have the one xl? try to update it to latest base
Click to expand...
Click to collapse
Yes it's an XL, however i can't update, because any zip or file i throw in the SDCARD via twrp recovery after mounting as per my original post it disappears for some reason so i don't know how i would flash anything.
movadoevo8 said:
Yes it's an XL, however i can't update, because any zip or file i throw in the SDCARD via twrp recovery after mounting as per my original post it disappears for some reason so i don't know how i would flash anything.
Click to expand...
Click to collapse
can you not mount adb sideload and flash through that ?
I had yesterday night the problem that I wiped phone because I had some issues...then wanted to put Rom.zip through recovery on sdcard...problem was my pc didn't accepted it...so I tried to find a solution then I found the adb sideload function installed then again the adb and HTC one x driver and then I was able to put the zip on my sdcard...flashed then Rom and yes all is working now
Gesendet von meinem HTC One X mit Tapatalk 2
markb63 said:
can you not mount adb sideload and flash through that ?
Click to expand...
Click to collapse
I'm not sure how to do that and what that means. I know how to flash via TWRP recovery which is not working and flash boot images etc using "FASTBOOT".
---------- Post added at 09:34 AM ---------- Previous post was at 09:31 AM ----------
One-X-master said:
I had yesterday night the problem that I wiped phone because I had some issues...then wanted to put Rom.zip through recovery on sdcard...problem was my pc didn't accepted it...so I tried to find a solution then I found the adb sideload function installed then again the adb and HTC one x driver and then I was able to put the zip on my sdcard...flashed then Rom and yes all is working now
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
I can put the zip in there even if i remove the USB cable without unmounting and then plug the USB cable again i see the file inside the phone just fine, the problem is when I unmount to get back into TWRP recovery to install a zip then it doesn't show up. Very weird not sure what is going on, but from what i hear it's a corrupted SD CARD. I found a thread, that teaches you how to fix this, but the link is now broken. I have PM the original poster hope he will contact me back.
movadoevo8 said:
I'm not sure how to do that and what that means. I know how to flash via TWRP recovery which is not working and flash boot images etc using "FASTBOOT".
---------- Post added at 09:34 AM ---------- Previous post was at 09:31 AM ----------
I can put the zip in there even if i remove the USB cable without unmounting and then plug the USB cable again i see the file inside the phone just fine, the problem is when I unmount to get back into TWRP recovery to install a zip then it doesn't show up. Very weird not sure what is going on, but from what i hear it's a corrupted SD CARD. I found a thread, that teaches you how to fix this, but the link is now broken. I have PM the original poster hope he will contact me back.
Click to expand...
Click to collapse
http://teamw.in/ADBSideload if you use this you can flash direct from sdk,worth a shot !!
markb63 said:
http://teamw.in/ADBSideload if you use this you can flash direct from sdk,worth a shot !!
Click to expand...
Click to collapse
Thank you so much! I will definitely toy with this later to see if it works.
---------- Post added at 10:07 AM ---------- Previous post was at 09:45 AM ----------
markb63 said:
http://teamw.in/ADBSideload if you use this you can flash direct from sdk,worth a shot !!
Click to expand...
Click to collapse
adb sideload /path/to/rom.zip
this is not working for me instead of just displays all the commands that adb can do.
I have gone and go to advanced>adb sideload in twrp supported version
on my computer i have a folder called c:\fastboot with the adb software and it's the version that supports adb side load according to the instructions so i have met all the requirements. However when i run the command
adb sideload cm.zip
as i am already in the c:\fastboot folder via command prompt all i get is a display of all the commands i can use with adb as if i just typed "adb" and it displays all the commands.
I also tried typing
adb sideload c:\fastboot\cm.zip
this did not work either same result. FYI cm.zip is the name of the rom file.
I also tried typing
adb sideload /fastboot/cm.zip
Any thoughts?
movadoevo8 said:
Thank you so much! I will definitely toy with this later to see if it works.
---------- Post added at 10:07 AM ---------- Previous post was at 09:45 AM ----------
adb sideload /path/to/rom.zip
this is not working for me instead of just displays all the commands that adb can do.
I have gone and go to advanced>adb sideload in twrp supported version
on my computer i have a folder called c:\fastboot with the adb software and it's the version that supports adb side load according to the instructions so i have met all the requirements. However when i run the command
adb sideload cm.zip
as i am already in the c:\fastboot folder via command prompt all i get is a display of all the commands i can use with adb as if i just typed "adb" and it displays all the commands.
I also tried typing
adb sideload c:\fastboot\cm.zip
this did not work either same result. FYI cm.zip is the name of the rom file.
I also tried typing
adb sideload /fastboot/cm.zip
Any thoughts?
Click to expand...
Click to collapse
do you have sdk on your desktop ? ... if so reboot your phone into recovery and connect to your pc via usb-open up sdk\platform tools-enter into adb sideload in recovery,then put your curser in the platform tools folder-press and hold the shift key and right click mouse,you should see open command window here-click.then enter adb devices-your device should show as ********* sideload in the command adb window.your device should now be asking for you to flash ?
markb63 said:
do you have sdk on your desktop ? ... if so reboot your phone into recovery and connect to your pc via usb-open up sdk\platform tools-enter into adb sideload in recovery,then put your curser in the platform tools folder-press and hold the shift key and right click mouse,you should see open command window here-click.then enter adb devices-your device should show as ********* sideload in the command adb window.your device should now be asking for you to flash ?
Click to expand...
Click to collapse
okay i followed your instructions and when i type "adb devices" i get the following output
C:\fastboot>adb devices
List of devices attached
HT2AHW300413 host
However my phone does say "now send the package you want to apply to the device with "adb sideload <filename>"
but when i goto advance>sideload from twrp that is what displays on the phone from the get go even before i run the command. SDK i have ADB version 1.0.29
When you say to make sure i have SDK please see the following screen shot i have attached and let me know if you are referring to those files under my fastboot folder and/or if i'm actually missing something.
movadoevo8 said:
okay i followed your instructions and when i type "adb devices" i get the following output
C:\fastboot>adb devices
List of devices attached
HT2AHW300413 host
However my phone does say "now send the package you want to apply to the device with "adb sideload <filename>"
but when i goto advance>sideload from twrp that is what displays on the phone from the get go even before i run the command. SDK i have ADB version 1.0.29
When you say to make sure i have SDK please see the following screen shot i have attached and let me know if you are referring to those files under my fastboot folder and/or if i'm actually missing something.
Click to expand...
Click to collapse
I think your in fastbboot folder ? you need to be in platform tools .my platform tools has a lot more inside than yours
movadoevo8 said:
okay i followed your instructions and when i type "adb devices" i get the following output
C:\fastboot>adb devices
List of devices attached
HT2AHW300413 host
However my phone does say "now send the package you want to apply to the device with "adb sideload <filename>"
but when i goto advance>sideload from twrp that is what displays on the phone from the get go even before i run the command. SDK i have ADB version 1.0.29
When you say to make sure i have SDK please see the following screen shot i have attached and let me know if you are referring to those files under my fastboot folder and/or if i'm actually missing something.
Click to expand...
Click to collapse
You don't need whole sdk ...if you activate adb sideload in recovery go to device manager on pc there should be something with android device or so ...then right click on it then update drivers or so then something with from computer and download at first the adb drivers for windows 8 extract to a folder a then in the driver update thing select this folder and update it or so...sorry am atm to stupid to write in English but you can sideload because adb drivers aren't working properly...you should also install HTC sync manager etc so it should be fixed then ...if not Google HTC one x adb driver windows 8 many instructions to get all working properlY
Gesendet von meinem HTC One X mit Tapatalk 2
One-X-master said:
You don't need whole sdk ...if you activate adb sideload in recovery go to device manager on pc there should be something with android device or so ...then right click on it then update drivers or so then something with from computer and download at first the adb drivers for windows 8 extract to a folder a then in the driver update thing select this folder and update it or so...sorry am atm to stupid to write in English but you can sideload because adb drivers aren't working properly...you should also install HTC sync manager etc so it should be fixed then ...if not Google HTC one x adb driver windows 8 many instructions to get all working properlY
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
I'm setting this up on my windows 7 machine, now I think i had an issue once on win 8. Updates to follow, thanks.
markb63 said:
I think your in fastbboot folder ? you need to be in platform tools .my platform tools has a lot more inside than yours
Click to expand...
Click to collapse
EDIT:
I was trying to reflash JB 4.3 because of storage issues but unfortunately I accidentally deleted and formatted internal and sd storage, so Im left with no OS on my Gnex but I can boot on recovery and fastboot. Also before I deleted the internal I did not enable usb debugging yet at that time. Is there a way I can flash a stock image by just using toolkit? ty
I tried pushing through fastboot mode but it says error: device not found. I only have the platform tools on my pc.
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, 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. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
lastforone said:
Instead of using a toolkit, just push a file to ur sdcard using adb and flash it... Or you can download the official image, boot into fastboot and flash it..
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
well then i need to download sdk first ty anyways
lolobabes said:
well then i need to download sdk first ty anyways
Click to expand...
Click to collapse
You do not need the whole sdk package. Just the adb + fastboot and few required files ... You can find the zip in erants guide..
Sent from my Galaxy Nexus using xda app-developers app
when i tried to push error device not found lol
lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Use adb sideload from twrp and send the zip from your PC to your phone.
Sent from my Galaxy Nexus using xda app-developers app
lolobabes said:
when i tried to push error device not found lol
Click to expand...
Click to collapse
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.
If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.
Beauenheim said:
Go into your device manager if you have windows, and see if you have any errors.
If you do, you might have an exclamation mark for the device: Galaxy. You can manually install the drivers from here, point it to your toolkit, I guess, since you downloaded it already.
Click to expand...
Click to collapse
When I am on recovery yes theres an exclamation on samsung mtp device but in fastboot mode the samsung mtp does not appear but when I do fastboot devices there appears a device number so I thought I can do it on fastboot. thank you.
beekay201 said:
If he reads efrant's "android 101" -which is STICKIED ON GENERAL forum- just the first post, he'll know everything and downloaded everything he needs to know and have to interact with his device.
a manta wrote this.
Click to expand...
Click to collapse
I have read that already however I was hoping to just flash a file to the sdcard if is even possible considering I have formatted both internal and sdcard. I am very new to adb so its an easier way for me. But it seems then I will ave to do it the hard way. Thanks
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks
lolobabes said:
PS
Not sure if this has any bearing but when I accidentally formated internal and sdcard it was a fresh 4.3 install and so android debugging was not enabled. Thanks
Click to expand...
Click to collapse
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.
sui785 said:
Doesn't matter because if you reboot in bootloader you can use fastboot(if drivers are installed properly), fastboot always works, you don't need to enable anything for it.
Click to expand...
Click to collapse
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
Take it out of a USB 3.0 port.
lolobabes said:
tried doing this in fastboot "adb push romname.zip /sdcard/ROM/" had this error: device not found
Click to expand...
Click to collapse
lolobabes said:
So meaning I can use fastboot to just push file to sdcard right? Tried to look for the right command but I cant seem to find the right one that works for me. Thank you.
Click to expand...
Click to collapse
no, there's no ADB interface on FASTBOOT interface. You'll never be able to push anything through ADB in FASTBOOT interface. Please read the thread i talked about earlier, and this one too -> http://forum.xda-developers.com/showthread.php?t=1626895 - Just the first post of each will do.
Beauenheim said:
Take it out of a USB 3.0 port.
Click to expand...
Click to collapse
*EPIC*
*facedesk*
*grows more white hair*
xD I actually had this issue a few days ago, had issues for 4 hours, realized I had my cord plugged in a 3.0 port.
Really dumb noob moment.
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, 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. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
lastforone said:
Instead of using a toolkit, just push a rom to ur sdcard using adb and flash it via recovery.. Or you can download the official image, boot into fastboot and flash it..
-
L4.1
Click to expand...
Click to collapse
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi
lolobabes said:
UPDATE:
Finally got the file pushed into the sd card doing via recovery. Since I am using TWRP recevery it was not too obvious how to do it unlike CWRM which I used to use. I spent more than 24 hours looking for the right solution that would work for me and funny thing was I finally got the right way to one of the first threads i looked into but just didnt pay much attention to it which was here http://forum.xda-developers.com/showthread.php?t=1667929
"Boot your phone into Recovery and select the "Mounts & Storage" screen
- Plug your phone into your computer using USB Data Transfer Cable
- Ensure in Recovery that your phone shows "Unmount /sdcard/" and "Unmount /system/" (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount)
- Open Command Prompt on your computer by doing Start -> Run -> cmd
- In Command Prompt, type "cd c:\AndroidSDK\tools" replacing AndroidSDK\tools with wherever your adb and ROM are located.
- This is probably the most important part - Still in Command Prompt, 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. This may take a minute or two...or four, but you will see a message in Command Prompt saying something like <12345678kb to 1234567kb>. That is just telling you that the file was pushed properly. (I did not include that message in the picture below)"
You were right on spot unfortunately I didnt know how to do it. Thank you anyways...:highfive::highfive::highfive:
Ty for all those who tried to help me, thank you for the effort, well it was indeed a learning experience... ahihihihi
Click to expand...
Click to collapse
I'm glad you sorted it out, that's the thing instead of teaching you step by step just left a hint on what you should do, helps you learn to do it on your own..
Peace,
L4.1
Thanks
Thanks for this. Was stuck with no factory image because had to wipe data because of encryption. Then was in dilemma of how to load the ZIP to sdcard without having to reflash the stock all over. This saved me the time. Thanks again
_-_
phunkie123 said:
I have the latest version of twrp installed in my phone and thats about it.
I am s-off'd and unlocked.
verizion htc one
ran a full system wipe and that wiped out my .zip rom file along with it.
can someone please help me?
Click to expand...
Click to collapse
You can use adb to push a rom file to you phone storage. I found this link that should help you http://htconeroot.com/htc-one-tutorials/how-to-copy-files-to-htc-one-using-twrp-mount-and-adb/
_-_
adb
phunkie123 said:
i can access the TWRP recovery and also the fastboot. however, when trying to run ADB in my computer the device is not listed.
when running the command "adb devices". nothing gets found.
EDIT - also when i get into the ADB sideload section of TWRP, my device stays stuck at "starting ADB sideload feature..."
Click to expand...
Click to collapse
What is your PC's OS.. Where did you get adb and fastboot??
_-_
Fastboot/adb
phunkie123 said:
My PC's OS is windows 7 home premium service pack 1. the fastboot was unlocked through the firewater method. if you mean the android-sdk tools i got them here
developer.android.com/sdk/index.html?utm_source=weibolife
the fastboot still seems to work as i tried re-flashing TWRP. it was successful. but it still just seems to stay stuck at "Starting ADB sideload feature..."
Click to expand...
Click to collapse
Ok do this move everything from the folder platform-tools should be fastboot.exe and adb.exe and a few other files to the root of your c drive....
than open your CMD window as admin... make sure you open as admin... than type
Code:
cd /
to move to the root of you c dirve and then type
Code:
adb
let me know the out come of that....
_-_
phunkie123 said:
sorry for all your trouble! the reason behind my problems was that my computer needed to be restarted to refresh my drivers. i was then able to mount and push my rom through ADB. whew! thanks so much people! im booting up already. no bricks here! thanks to all of you guys!!
Click to expand...
Click to collapse
Great.... Hate to see anyone have trouble with there m7....Thx lj
Hi I tried flashing a custom rom on my ZE550ML last week and now have a soft brick(i think). I have looked through many threads and cannot seem to get the answers I need.
During the flashing of the rom I forced restart after about 15 minutes without indication of installation. I didn't make a nandroid backup like i normally do and wiped system cache. I have nothing on the internal storage now and am trying to push the latest firmware from the asus site to the phone but cant get it right.
I am not sure what I am doing wrong with adb. I have the drivers and the firmware. When I reboot to recovery to apply update from adb, I get error saying "closed".
I change the firmware zip filename after watching other vids and reading different posts. Can someone help me understand if either I can't restore my phone or what I am doing wrong.?Thanks in advance!
my command line reads C:\adb>adb push ULZ008WW.ziip /sdcard/ .
eborden said:
Hi I tried flashing a custom rom on my ZE550ML last week and now have a soft brick(i think). I have looked through many threads and cannot seem to get the answers I need.
During the flashing of the rom I forced restart after about 15 minutes without indication of installation. I didn't make a nandroid backup like i normally do and wiped system cache. I have nothing on the internal storage now and am trying to push the latest firmware from the asus site to the phone but cant get it right.
I am not sure what I am doing wrong with adb. I have the drivers and the firmware. When I reboot to recovery to apply update from adb, I get error saying "closed".
I change the firmware zip filename after watching other vids and reading different posts. Can someone help me understand if either I can't restore my phone or what I am doing wrong.?Thanks in advance!
my command line reads C:\adb>adb push ULZ008WW.ziip /sdcard/ .
Click to expand...
Click to collapse
Adb sideload not adb push
miku1024 said:
Adb sideload not adb push
Click to expand...
Click to collapse
I had tried both. Perhaps I was in the wrong location when i tried them. Do I have to go to apply adb update when issuing the adb push command or should i be somewhere else when issuing the adb push command?
Thanks in advance.
eborden said:
I had tried both. Perhaps I was in the wrong location when i tried them. Do I have to go to apply adb update when issuing the adb push command or should i be somewhere else when issuing the adb push command?
Thanks in advance.
Click to expand...
Click to collapse
Yes first apply adb upadate, then adb sideload command
miku1024 said:
Yes first apply adb update, then adb sideload command
Click to expand...
Click to collapse
Ok. I get that part. I do have a couple of other questions:
1. can the firmware be flashed from an external sd card? If so, can it be any firmware version or should it be the most recent I had installed or earliest version?
2. can the windroid universal android toolkit be used during the flashing of the firmware.
I used the toolkit to install drivers that didn't seem to be different from what i already had installed and when I checked that I had the adb drivers it said i had them.
I am Trying to flash the stock rom via side load i flashed that few days back to at that time it was flashed success fully but now it always gives me error
Code:
"C:\android-sdk\platform-tools>adb sideload OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8.zip
loading: 'OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8.zip'
* cannot read 'OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8.zip' *
C:\android-sdk\platform-tools>adb sideload <OnePlus3TOxygen_28_OTA_039_all_1701140132_de9036f11e2246a8.zip>
The syntax of the command is incorrect.
C:\android-sdk\platform-tools>"
Mine would not sideload either. I downloaded the zip file to my PC, connected the phone to the PC, put the phone in USB mode, dragged the zip file from the PC to the phone root directory, disconnected from the PC, and flashed the ROM from the phone hard drive.
Faulty ADB drivers I guess. If you have TWRP you can try adb push name /sdcard/
Puddi_Puddin said:
Faulty ADB drivers I guess.
Click to expand...
Click to collapse
Isn't obvious this is not a driver problem?! Read the error message that is staring him in the face. He has not specified the correct file/path.
bulletmark said:
Isn't obvious this is not a driver problem?! Read the error message that is staring him in the face. He has not specified the correct file/path.
Click to expand...
Click to collapse
Second one is a invalid command because of those <> first command mainly happenda with wrong drivers, I and many other get the error it is quite unexplainable.
Any resolution to this? I'm getting the same problem, saying it cannot read the zip file when I try to sideload
trying to update my wifes phone now. getting the same issue. i typed in adb devices and it shows up, so i know its not driver related. wonder if its a faulty image? ill keep trying
---------- Post added at 03:59 AM ---------- Previous post was at 03:55 AM ----------
funny i think i just foud the issue. someone posted saying older adbs cant see larger than 1gb (i have a opo so never even heard of this). ill give it a try and report back...
this is the adb ill be using https://forum.xda-developers.com/showthread.php?t=2317790
Okay, now that may work for others but I could not get it... Sorry
I ended up just removing the encryption, flashing twrp, and flashing OOS that way. Make sure to make a backup... I made a backup of everything... Except contacts because I thought gmail handled that like on my phone. I left my wife a note saying sorry for when she wakes up ha.
At least the annoying updates available message will be gone that we've had since Aug or something
I was getting the exact same errors and was frustrated to no end..... till I figured out how to fix it =)
I had to use this program on my adb.exe to make it large address aware
https://www.techpowerup.com/forums/threads/large-address-aware.112556/
Grab the laa_2_0_4.zip from the website, open and run as administrator
Click on select executable and go to where your adb.exe is installed, for me it was in C:\adb\adb.exe
Then make sure the checkbox on step 2 is selected and then hit save
I rebooted my PC and upon using the adb on reboot I was finally able to flash the stock OOS roms via adb sideload on my phone
Yipeee!!
shoemocker said:
I was getting the exact same errors and was frustrated to no end..... till I figured out how to fix it =)
I had to use this program on my adb.exe to make it large address aware
https://www.techpowerup.com/forums/threads/large-address-aware.112556/
Grab the laa_2_0_4.zip from the website, open and run as administrator
Click on select executable and go to where your adb.exe is installed, for me it was in C:\adb\adb.exe
Then make sure the checkbox on step 2 is selected and then hit save
I rebooted my PC and upon using the adb on reboot I was finally able to flash the stock OOS roms via adb sideload on my phone
Yipeee!!
Click to expand...
Click to collapse
I used the same tool