Related
I have used all drivers and two different tot files, and it works to reboot, then it fails when I try to get past the first welcome screen... Does it make a difference if the sim card is in or out???
It makes it to preactivation and set phone name, then a second or two later goes back into the reboot stage.
I made it to the settings screen and phone info, and all areas were UNKNOWN
pitbull8265 said:
I have used all drivers and two different tot files, and it works to reboot, then it fails when I try to get past the first welcome screen... Does it make a difference if the sim card is in or out???
It makes it to preactivation and set phone name, then a second or two later goes back into the reboot stage.
I made it to the settings screen and phone info, and all areas were UNKNOWN
Click to expand...
Click to collapse
I don't know what went wrong but since you don't have a reply I'll say this... I would start from scratch. Download the tot file AND dll again to a new place on your PC (like desktop). Run LG flash tool again and browse to those 2 files (flash tools likes to remember previous settings). Flash again and let us know the result. Sim card doesn't make a difference.
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware if you need it, always flashed reliably for me.
...
scottdanpor said:
I don't know what went wrong but since you don't have a reply I'll say this... I would start from scratch. Download the tot file AND dll again to a new place on your PC (like desktop). Run LG flash tool again and browse to those 2 files (flash tools likes to remember previous settings). Flash again and let us know the result. Sim card doesn't make a difference.
http://downloads.codefi.re/autoprime/LG/LG_G2/LS980/Stock_Firmware if you need it, always flashed reliably for me.
Click to expand...
Click to collapse
Ive done this.. no luck
pitbull8265 said:
Ive done this.. no luck
Click to expand...
Click to collapse
Did you get anywhere with this? Under status, is your IMEI listed as unknown? This seems like your efs partition might be messed up. Did you make a backup of it?
scottdanpor said:
Did you get anywhere with this? Under status, is your IMEI listed as unknown? This seems like your efs partition might be messed up. Did you make a backup of it?
Click to expand...
Click to collapse
I just read elsewhere that if you used ioroot you may have a backup anyways. On the computer in ioroot. You may find a couple files called, modem st1, and modem st2.
Hopefully they will speak of it. Watch this thread..,.
http://forum.xda-developers.com/showthread.php?p=51932057
@scottdanpor for the info and hopefully how to use it.
pitbull8265 said:
Ive done this.. no luck
Click to expand...
Click to collapse
Sent from my Nexus 7 using Tapatalk
secret.animal said:
I just read elsewhere that if you used ioroot you may have a backup anyways. On the computer in ioroot. You may find a couple files called, modem st1, and modem st2.
Hopefully they will speak of it. Watch this thread..,.
http://forum.xda-developers.com/showthread.php?p=51932057
@scottdanpor for the info and hopefully how to use it.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yeah but he has basically access to download mode and fastboot it seems. I haven't found a way to push files without at least recovery
Well, if he has access to stock recovery should be able to push files that way through ADB
NOPE
scottdanpor said:
Yeah but he has basically access to download mode and fastboot it seems. I haven't found a way to push files without at least recovery
Well, if he has access to stock recovery should be able to push files that way through ADB
Click to expand...
Click to collapse
it just hangs and reboots still... cant access fastboot.. tried every file available nothing is working
rrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrrr
scottdanpor said:
Yeah but he has basically access to download mode and fastboot it seems. I haven't found a way to push files without at least recovery
Well, if he has access to stock recovery should be able to push files that way through ADB
Click to expand...
Click to collapse
I have a recovery I made using twrp saved to my pc, and I chose the option to backup my efs, so all of my info is on my pc in the backup file.
HOW can I use adb sideload or ADB to push it to my phone???
HAS TO BE DONE FROM STOCK RECOVERY ADB, as i cant even get into the ui long enough to activate usb debugging
pitbull8265 said:
I have a recovery I made using twrp saved to my pc, and I chose the option to backup my efs, so all of my info is on my pc in the backup file.
HOW can I use adb sideload or ADB to push it to my phone???
HAS TO BE DONE FROM STOCK RECOVERY ADB, as i cant even get into the ui long enough to activate usb debugging
Click to expand...
Click to collapse
It will take a bit of reading but you will learn a lot!
Here's a guide with some commands, you just need to tailor it to your needs/paths, it says Samsung but all you need are the commands.
http://forum.xda-developers.com/showthread.php?t=2141817
If you have ioroot on your computer you have ADB. Plug in your phone in recovery mode and check device manager. It's probably under "unknown" as LG-LS980. You need to right-click and select "update driver", then manually select driver. From the list, you should be able to find something like Android composite ADB device. Select that one and it should then be recognized as ADB.
Hold Shift and right click on the ioroot folder and select "Open command window here", then in cmd type "adb devices". If all is good you will get a serial number as it detects your device. Once you got this you are ready to enter commands, check that guide for the right command to push the file to: /dev/block/platform/msm_sdcc.1/by-name/
as stated by Autoprime here: http://forum.xda-developers.com/showthread.php?t=2451390
I hope that's enough info to get you going. You should type "adb shell" first in ADB so you have access to root.
---------- Post added at 09:12 AM ---------- Previous post was at 09:03 AM ----------
Oh crap... I just re-read that. I don't think this will work if your backup is from TWRP. That needs to be restored from TWRP. Do you not have a backup from ioroot? That contains the img files you need.
---------- Post added at 09:18 AM ---------- Previous post was at 09:12 AM ----------
Ok, I found this...
"Even though all TWRP backup files carry the extension .win, they are either tar archives or filesystem images. System, data, cache and .android_secure are backed up as tar archives or gnu-zipped tar archives if compression is enabled. You can rename those .win files to .tar (.tar.gz if compressed) and extract them like a regular archive. Boot and recovery partitions are backed up as .img files using dd"
from: http://forum.xda-developers.com/showthread.php?t=1694617
I couldn't find out if TWRP backs up EFS to .tar or .img. Once you figure that out you should be able to rename them to modemst1.img and modemst1.img. I just verified on mine that the files are the same size, so I would guess they are actually img files and not compressed. They should be 3MB in size.
There's a lot more info in that thread by Autoprime that should help.
So I decided to try to run ubuntu touch on my Samsung Galaxy Nexus(verizon). All went well, but now it seems I cant start the phone, can only get into fastboot mode. Can anyone please walk me through the steps of putting stock android back on my phone? I have adb and fastboot installed on my computer. There's a guide here that walks you through the process of returning the phone to stock software/firmware, but it requires USB debugging to be on, which I can't turn on because the phone won't boot up. I greatly appreciate any help!!!
Phone Info(what's written in fastboot):
PRODUCT NAME-Tuna
VARIANT- toro 32GB
HW VERSION- 9
BOOTLOADER VERSION: PRIMELC03
BASEBAND VERSION- I515.FK02 CDMA-I515.FK01
CARRIER INFO- NONE
SIGNING- production
LOCK STATE- UNLOCKED
You dont need USB debug on in order to use fastboot
---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------
Debugging is only needed if using adb.
But if u already in fastboot bootloader mode then u don't need to do "adb reboot bootloader" command
ashclepdia said:
You dont need USB debug on in order to use fastboot
---------- Post added at 05:39 PM ---------- Previous post was at 05:38 PM ----------
Debugging is only needed if using adb.
But if u already in fastboot bootloader mode then u don't need to do "adb reboot bootloader" command
Click to expand...
Click to collapse
Thanks for the pretty fast response! I'm still lost as to how I can make everything go back to the way it is (i.e, get rid of ubuntu and get android back on ) . Definitely my last time trying to muck around with roms and such D;
vsp3317 said:
Thanks for the pretty fast response! I'm still lost as to how I can make everything go back to the way it is (i.e, get rid of ubuntu and get android back on ) . Definitely my last time trying to muck around with roms and such D;
Click to expand...
Click to collapse
Don't give up!
Once you've done it once or twice it becomes easier, everything starts to make sense
Did you download one of the Google factory img for toro to your computer? Get it from here
https://developers.google.com/android/nexus/images
(It will be under the Mysid/toro name) any of the available ones will work that are for toro.
---------- Post added at 06:19 PM ---------- Previous post was at 06:17 PM ----------
Then you just uncompress the file, open command prompt(aka terminal) in that folder/directory , put device into fastboot mode(bootloader), and then execute the flash all script that comes with the factory IMG download.
---------- Post added at 06:26 PM ---------- Previous post was at 06:19 PM ----------
Oh, and to easily open a command prompt in that directory, uncompress the factory img download file from that site linked above, then open the folder to view it's contents. Hold shift and right click within the folder and choose "open command prompt"
Then all you should need to do is put "flash-all.exe" and hit enter in the command prompt that pops up once device is connected and in fastboot(bootloader)mode. (No quotes...just enter the text) and then be patient. The flashing of the radio files might seem to take a long time especially the CDMA radio. Do NOT unplug or anything before it is completed fully)
If need anymore info ask away
ashclepdia said:
Don't give up!
Once you've done it once or twice it becomes easier, everything starts to make sense
Did you download one of the Google factory img for toro to your computer? Get it from here
(It will be under the Mysid/toro name) any of the available ones will work that are for toro.
---------- Post added at 06:19 PM ---------- Previous post was at 06:17 PM ----------
Then you just uncompress the file, open command prompt(aka terminal) in that folder/directory , put device into fastboot mode(bootloader), and then execute the flash all script that comes with the factory IMG download.
---------- Post added at 06:26 PM ---------- Previous post was at 06:19 PM ----------
Oh, and to easily open a command prompt in that directory, uncompress the factory img download file from that site linked above, then open the folder to view it's contents. Hold shift and right click within the folder and choose "open command prompt"
Then all you should need to do is put "flash-all.exe" and hit enter in the command prompt that pops up once device is connected and in fastboot(bootloader)mode. (No quotes...just enter the text) and then be patient. The flashing of the radio files might seem to take a long time especially the CDMA radio. Do NOT unplug or anything before it is completed fully)
If need anymore info ask away
Click to expand...
Click to collapse
Wow, I can't thank you enough man!!! :highfive: That worked like a charm , no problems at all . And oh it's "flash-all.bat" not .exe, for the people that might come across this thread later. Thanks again though, I really don't know what I would've done. Definitely going to do a **** ton more research next time I decide to go and flash a rom haha.
vsp3317 said:
Wow, I can't thank you enough man!!! :highfive: That worked like a charm , no problems at all . And oh it's "flash-all.bat" not .exe, for the people that might come across this thread later. Thanks again though, I really don't know what I would've done. Definitely going to do a **** ton more research next time I decide to go and flash a rom haha.
Click to expand...
Click to collapse
No problem buddy
That's what these forums are for, learning, helping, development, all that good stuff! Just happy it went smoothly for ya.
I think it used to be named .exe, at least it shows as exe on my laptop but I use Linux so it could just be seeing it differently(since I have wine installed)
There is usually a windows executable and a Linux .sh script that can be executed from the terminal to start the process.
See, it's not all THAT bad now is it? Especially since now you know how to do it, messing up the device isn't such a daunting thing anymore lol.
As for keeping status 7 from happening again I highly recommend bookmarking the TWRP or CWM official sites so that before flashing things in the future, you can make sure you have the most up to date custom recovery installed by comparing what is available vs what you have installed(booting into recovery mode will usually have the version info somewhere on the main screen) and of course having a recent nandroid backup made within your current custom recovery. I prefer TWRP but it's a personal choice to each user which they use
Just don't be afraid to play around
Congrats again on your first soft brick&restore! Lol
It's such a relieving feeling once you bring device back from the dead ain't it?
Like many of you new flashers, I have flashed the SkyDragon ROM and have noticed that there is no connectivity to the computer whatsoever, so I did a little digging. I went back and forth between 2 Nandroid backups and kept flashing parts of them until I could narrow down where this problem was coming from. I found out that it comes from the specific folder - data/property
There is a missing file called persist.sys.usb.config ,13B in size, and I have no idea what it does (maybe some of you could enlighten me) but throwing the old file into that folder, changing the permissions to rw-------- and rebooting worked like a charm.
I apologize for not sticking this into the development thread, however I'm a lurker with no input! :victory:
Without further ado,
I TAKE NO RESPONSIBILITY FOR ANY BORKEN DEVICES. IF YOU DON'T KNOW WHAT YOU'RE DOING, DON'T DO IT!
1. Download Root Browser and RB Text Editor
2. Navigate to /data/property
3. On the bottom bar, tap the "New" button
4. Click on "New file"
5. Enter the file name as follows:
persist.sys.usb.config
6. Click the file you just made and hit "Open as..."
7. Hit "Text file"
8. Click RB Text editor
9. Delete whatever is there and enter as follows:
auto_conf,adb
No spaces or caps!
10. Save the file by clicking the save button on the top right corner.
11. Reboot your phone
12.Profit
----------------------------------------------------------------------------------------------------------------------------------------
Steal this information, spread it around, someone post it to the development thread and make this ROM better!
If you're having any problems, don't hesitate to ask
i could just drop this in the proper location before flashing the rom yes ??
CheesyNutz said:
i could just drop this in the proper location before flashing the rom yes ??
Click to expand...
Click to collapse
Only if you're going to dirty flash it, but at that point, I'd just dirty flash it anyways. The file should already be there if you're on a ROM that can recognize your phone. I also do recommend a clean flash. I'm sorry if I made this difficult. When flashing the rom, it'll format /data which is where the file is held so if you had the file there already, it would just wipe it.
88keys6strings said:
Only if you're going to dirty flash it, but at that point, I'd just dirty flash it anyways. The file should already be there if you're on a ROM that can recognize your phone. I also do recommend a clean flash. I'm sorry if I made this difficult. When flashing the rom, it'll format /data which is where the file is held so if you had the file there already, it would just wipe it.
Click to expand...
Click to collapse
i was talking from a clean install
drop file in the proper location then wipe phone flash rom with new file and them proceed to set up the phone
CheesyNutz said:
i was talking from a clean install
drop file in the proper location then wipe phone flash rom with new file and them proceed to set up the phone
Click to expand...
Click to collapse
As long as it's after the wipe then yes. If you opened up the zip that contains the ROM, you could head into /data then create a new folder called property and throw the file in there then zip it back up and flash it. But you MUST put the file in /data/property AFTER you flash the ROM. You could drop the file into a downloads or media folder because those don't get touched then flash the rom then move it and change permissions then reboot as well.
So no, you cannot drop the file in it's PROPER location before you wipe, otherwise it'll get deleted. However, you can copy/paste it into say, mnt/sdcard/Download, via your root browser, beforehand then follow my instructions
I'll try when I get home in about six hours.
partylikeaninjastar said:
I'll try when I get home in about six hours.
Click to expand...
Click to collapse
For sure! Will await results
I hope the developers get to see this for the next update
I tried creating my own file as per the instructions (came to 13b size for the file too), but my phone isn't being recognized in android file transfer.
Then again, it wasn't recognized either when I was on stock rom (prior to flashing anything).
On my phone, the file already existed. Its contents read....
Code:
boot,adb,mtp
I changed it accordingly based on your instructions, reboot and nothing.
I found that if you turn USB debugging off, then on again, the file will get overwritten with the original code...boot,adb,mtp.
Could it be that this command simply enables USB debugging? That's what my testing showed. I turned off debugging, made the file change, reboot and debugging was enabled. Disable debugging and the file gets overwritten. Rinse, repeat. If I delete the file, it is recreated when enabling USB debugging....boot,adb,mtp.
Just a preliminary finding. I'm not well versed enough to explain or troubleshoot it any further. It did nothing to cure my USB problem.
Cablespider said:
On my phone, the file already existed. Its contents read....
Code:
boot,adb,mtp
I changed it accordingly based on your instructions, reboot and nothing.
I found that if you turn USB debugging off, then on again, the file will get overwritten with the original code...boot,adb,mtp.
Could it be that this command simply enables USB debugging? That's what my testing showed. I turned off debugging, made the file change, reboot and debugging was enabled. Disable debugging and the file gets overwritten. Rinse, repeat.
Just a preliminary finding. I'm not well versed enough to explain it further. It did nothing to cure my USB problem.
Click to expand...
Click to collapse
I may have overlooked something. I deleted some usb portion of the build.prop. Didn't change anything so i didnt think about it. If you make a backup then edit it deleting the usb part, then reboot that might get it to work.If you need specifics, I'll be next to a computer in about an hour and a half
Can someone just post the file here?
Sent from my LG-D851
---------- Post added at 10:44 PM ---------- Previous post was at 10:36 PM ----------
I copied one of the persist.sys files from that folder to my sdcard and edited it with Rom Toolbox Pro. I opened it as a text file and deleted what was there, then added the stuff in the OP and saved. I then renamed the file to persist.sys.usb.config and added it to that folder and changed permissions and rebooted. Worked fine.
Sent from my LG-D851
Skizzy034 said:
Can someone just post the file here?
Sent from my LG-D851
---------- Post added at 10:44 PM ---------- Previous post was at 10:36 PM ----------
I copied one of the persist.sys files from that folder to my sdcard and edited it with Rom Toolbox Pro. I opened it as a text file and deleted what was there, then added the stuff in the OP and saved. I then renamed the file to persist.sys.usb.config and added it to that folder and changed permissions and rebooted. Worked fine.
Sent from my LG-D851
Click to expand...
Click to collapse
Awesome! Glad it worked for you
This is from my stock rom with the modified skydragon kernel. place in root\data\property. let me know if this works. just rename it and drop the .zip part.
Cablespider said:
On my phone, the file already existed. Its contents read....
Code:
boot,adb,mtp
I changed it accordingly based on your instructions, reboot and nothing.
I found that if you turn USB debugging off, then on again, the file will get overwritten with the original code...boot,adb,mtp.
Could it be that this command simply enables USB debugging? That's what my testing showed. I turned off debugging, made the file change, reboot and debugging was enabled. Disable debugging and the file gets overwritten. Rinse, repeat. If I delete the file, it is recreated when enabling USB debugging....boot,adb,mtp.
Just a preliminary finding. I'm not well versed enough to explain or troubleshoot it any further. It did nothing to cure my USB problem.
Click to expand...
Click to collapse
Jephre said:
I tried creating my own file as per the instructions (came to 13b size for the file too), but my phone isn't being recognized in android file transfer.
Then again, it wasn't recognized either when I was on stock rom (prior to flashing anything).
Click to expand...
Click to collapse
partylikeaninjastar said:
I'll try when I get home in about six hours.
Click to expand...
Click to collapse
CheesyNutz said:
i was talking from a clean install
drop file in the proper location then wipe phone flash rom with new file and them proceed to set up the phone
Click to expand...
Click to collapse
UPDATED
Much easier now. Just tested it with a Nand that didn't work at all and followed the instructions and it worked flawlessly. Let me know if you have any more issues
aclegg2011 said:
This is from my stock rom with the modified skydragon kernel. place in root\data\property. let me know if this works. just rename it and drop the .zip part.
Click to expand...
Click to collapse
It should work just fine as long as you didn't actually compress it lol. Thank you for the upload!
ALSO
THIS IS MY 10TH POST!!! DEV SECTION HERE I COME!! :victory:
88keys6strings said:
1. Download Root Browser and RB Text Editor
2. Navigate to /data/property
3. On the bottom bar, tap the "New" button
4. Click on "New file"
5. Enter the file name as follows:
persist.sys.usb.config
6. Click the file you just made and hit "Open as..."
7. Hit "Text file"
8. Click RB Text editor
9. Delete whatever is there and enter as follows:
auto_conf,adb
No spaces or caps!
10. Save the file by clicking the save button on the top right corner.
11. Reboot your phone
12.Profit
Click to expand...
Click to collapse
I can now confirm that this does work. I now have working MTP again.
You guys could try adding "persist.sys.usb.config=mtp,adb" to the build.prop and see if that works.
Root is no longer working on MM update.
Don't suppose anybody knows how to get to recovery with hardware button?
hecksagon said:
Don't suppose anybody knows how to get to recovery with hardware button?
Click to expand...
Click to collapse
Swipe from top-left to bottom-right at the Asus logo. That gets you to fastboot mode, then swipe up and down to change menu items, swipe right to select.
Or you can enable debug mode and use adb reboot recovery.
CSX321 said:
Swipe from top-left to bottom-right at the Asus logo. That gets you to fastboot mode, then swipe up and down to change menu items, swipe right to select.
Or you can enable debug mode and use adb reboot recovery.
Click to expand...
Click to collapse
You are a hero. I have looked for the better part of 2 hours for this. Anyway I'll sideload the LP update and start over. Hopefully somebody can make use of the recovery and boot pulls and get us a working recovery.
I would be very interested in REMOVING the Wellness app. This is the only reason I want root. Guess I will need to wait until we have a root enabled file manager. Alas, I can write in C++ fairly well, but know nothing of coding for android. Be glad to test any recoveries and operating systems on my ZenWatch.
nethead72 said:
I would be very interested in REMOVING the Wellness app. This is the only reason I want root. Guess I will need to wait until we have a root enabled file manager. Alas, I can write in C++ fairly well, but know nothing of coding for android. Be glad to test any recoveries and operating systems on my ZenWatch.
Click to expand...
Click to collapse
It can be done without a file manager. If you have root, you can enable debugging, connect to a PC by USB, use adb to get a root shell, then adb uninstall package_name.
Edit...Which Benton are you in, BTW. I'm not far from Benton, IL.
CSX321 said:
It can be done without a file manager. If you have root, you can enable debugging, connect to a PC by USB, use adb to get a root shell, then adb uninstall package_name.
Edit...Which Benton are you in, BTW. I'm not far from Benton, IL.
Click to expand...
Click to collapse
Es File Explorer works fine and has an OK interface when on the watch. Also the KingRoot app that gets pushed has an uninstaller too for system apps. The biggest issue I've had is that when the prompt to allow root comes up you can not select allow. You have to cover the screen to back out, then go into KingRoot and open the log, then select the app you want to allow and set it to always allow. You have to do this after the initial failed prompt.
Edit: Freeport, IL here. Worlds a small place.
File Types?
hecksagon said:
The latest Windows version of kingroot works on the zenwatch. I currently have root that persists after reboot and I am working on pulling the boot.img and recovery.img. Not sure what to do after that, hope somebody can pick up on this.
Recovery.img
https://drive.google.com/file/d/0BxOsuCVqSlnfVzVGRWo4bmZZZHc/view?usp=docslist_api
Boot.img
https://drive.google.com/file/d/0BxOsuCVqSlnfLVp4Z19EQ0owdTQ/view?usp=docslist_api
Click to expand...
Click to collapse
Am I looking at .iso files here, tarballs, or some other kind of binary? I need to add file extensions to make them useful.:good:
---------- Post added at 09:30 PM ---------- Previous post was at 09:28 PM ----------
Benton Arkansas.
---------- Post added at 09:32 PM ---------- Previous post was at 09:30 PM ----------
hecksagon said:
Es File Explorer works fine and has an OK interface when on the watch. Also the KingRoot app that gets pushed has an uninstaller too for system apps. The biggest issue I've had is that when the prompt to allow root comes up you can not select allow. You have to cover the screen to back out, then go into KingRoot and open the log, then select the app you want to allow and set it to always allow. You have to do this after the initial failed prompt.
Edit: Freeport, IL here. Worlds a small place.
Click to expand...
Click to collapse
I use ES File Explorer on my Nexus 6, CyanogenMod 12.1
I do not have a wearable app on my ZenWatch. Is it in settings somewhere?
nethead72 said:
Am I looking at .iso files here, tarballs, or some other kind of binary? I need to add file extensions to make them useful.:good:
---------- Post added at 09:30 PM ---------- Previous post was at 09:28 PM ----------
Benton Arkansas.
---------- Post added at 09:32 PM ---------- Previous post was at 09:30 PM ----------
I use ES File Explorer on my Nexus 6, CyanogenMod 12.1
I do not have a wearable app on my ZenWatch. Is it in settings somewhere?
Click to expand...
Click to collapse
You have to download the normal phone apk from apkmirror or some other site and use adb to sideload it. Google sideloading apps to Wear, should work the same for any watch. Otherwise you can buy Apps2Wear on the play store. I have done that because its more convenient.
Ok, went through the whole process, is there a way to check root access using ADB?
You should have KingRoot app installed on your watch. That will tell you if you have root. I imagine you could try to pull some files from /system or something that would normally not be accessible. I wouldn't recommend writing to system yet. I soft bricked by watch just by pasting a modified build.prop over the original, trying to turn off low bit depth ambient mode.
Root confirmed, having issues side-loading the ES File explorer apk, though. I'm using the App2Wear method. Still trouble shooting.
nethead72 said:
Root confirmed, having issues side-loading the ES File explorer apk, though. I'm using the App2Wear method. Still trouble shooting.
Click to expand...
Click to collapse
Make sure you have adb debugging and adb bluetooth debugging enabled on watch. Make sure you have usb adb debugging turn on on phone. Then make sure you have bluetooth debugging turn on in Wear app. Make sure you do these in that order because the toggle in the wear app wont show up unless you have debugging enabled on phone first.
This is the KingRoot file you need for windows.
https://onedrive.live.com/redir?res...3077&authkey=!AA2AI4RkRdiA4tg&ithint=file,exe
Attached is the latest ES File Explorer APK
EDIT: I rebooted everything, and worked fine. Funny how rebooting fixes so many issues... Will test when side-load is completed.
EDIT 2: Looks like its gonna take a long time. Gonna go do dishes and whatnot and be patient.
nethead72 said:
Am I looking at .iso files here, tarballs, or some other kind of binary? I need to add file extensions to make them useful.:good:
Click to expand...
Click to collapse
Sorry, they are .img. They were pulled using Flashify. The extension must have been stripped when I uploaded them to Drive.
nethead72 said:
This is the KingRoot file you need for windows.
https://onedrive.live.com/redir?res...3077&authkey=!AA2AI4RkRdiA4tg&ithint=file,exe
Attached is the latest ES File Explorer APK
EDIT: I rebooted everything, and worked fine. Funny how rebooting fixes so many issues... Will test when side-load is completed.
EDIT 2: Looks like its gonna take a long time. Gonna go do dishes and whatnot and be patient.
Click to expand...
Click to collapse
Sometimes it fails once and works when you retry. Not sure why.
hecksagon said:
Sometimes it fails once and works when you retry. Not sure why.
Click to expand...
Click to collapse
ES is 28 MB when installed, according to App2Wear, that should be 45-60 minutes to install.
nethead72 said:
ES is 28 MB when installed, according to App2Wear, that should be 45-60 minutes to install.
Click to expand...
Click to collapse
Maybe 10-15 mins when I did.
hecksagon said:
Maybe 10-15 mins when I did.
Click to expand...
Click to collapse
Seems like its taking way too long (going on 1 hour+). Gonna reboot and try again.
---------- Post added at 11:55 PM ---------- Previous post was at 11:25 PM ----------
If it fails this time, I will connect it to ADB with command line and manually push the apk onto the watch. I will give it until after dinner to complete the process.
Cant get it to install, and adb says its an invalid apk file when i try to push it. I suppose its not really necessary anyway. Ill just use KingRoot app if I need to do file management.
nethead72 said:
Seems like its taking way too long (going on 1 hour+). Gonna reboot and try again.
---------- Post added at 11:55 PM ---------- Previous post was at 11:25 PM ----------
If it fails this time, I will connect it to ADB with command line and manually push the apk onto the watch. I will give it until after dinner to complete the process.
Cant get it to install, and adb says its an invalid apk file when i try to push it. I suppose its not really necessary anyway. Ill just use KingRoot app if I need to do file management.
Click to expand...
Click to collapse
Did you confirm the apk was good? I'd try installing it on your phone. I don't think KingRoot has file management capabilities.
On a side note, I would advise against uninstalling anything. I just went to flash the previous OTA and it failed because I didn't have Jawbone installed.
I am trying to install the latest community build , I download a latest version of 3.5.3 from OnePlus's download section.
Currently I am on 3.2.7 , not rooted and boot loader is locked. All factory setting
these are the steps
check and make sure USB debugging is on
connect the device to PC
adb reboot recovery
device goes to recovery , select language and select install from adb on my phone
checking to make sure device is recognized and authorized
adb devices
50f4f77f sideload
************************************
adb sideload Update.zip
loading: 'Update.zip'
* cannot read 'Update.zip' *
I know I am in a correct folder as I already a did a <dir> and verified update.zip is in the current folder but lets try this
adb sideload C:\adb\Update.zip
loading: 'Update.zip'
* cannot read 'Update.zip' *
:crying:
at this point I am sure there is something wrong with the zip file. so I delete it and download the 3.2.6 just to test it out and I was able to downgrade to 3.2.6 with adb sildeload. once installation was complete I tried again to download 3.5.3 and sideload it but still getting a cannot read <filename> error.
any idea what I am missing here ?
By the way , I have tried several options such as :
1- changing the location of the file from adb folder to other location
2- renaming the file
3- launching cmd prompt as an administrator and navigating to the file location
Hello,
I have a strong feeling that you are trying to flash a wrong zip file. Can you mention the size of file that you mentioned as "update.zip"?
catrawalkar said:
Hello,
I have a strong feeling that you are trying to flash a wrong zip file. Can you mention the size of file that you mentioned as "update.zip"?
Click to expand...
Click to collapse
"OnePlus3Oxygen_16_OTA_003_all_1609142002_2a17363c90cd462e.zip" is the name of the file
nima352000 said:
"OnePlus3Oxygen_16_OTA_003_all_1609142002_2a17363c90cd462e.zip" is the name of the file
Click to expand...
Click to collapse
Then why are you giving command of update.zip? You should write the name of file in the command.
Replace "update.zip" in your command to the name of file as it is.
catrawalkar said:
Then why are you giving command of update.zip? You should write the name of file in the command.
Replace "update.zip" in your command to the name of file as it is.
Click to expand...
Click to collapse
As I mentioned in my post I have already tried that this was my last attempt as many folks out here saying that "renaming" the file helped them
nima352000 said:
As I mentioned in my post I have already tried that this was my last attempt as many folks out here saying that "renaming" the file helped them
Click to expand...
Click to collapse
Can you post a screenshot of your command prompt and folder that contains zip file?
catrawalkar said:
Can you post a screenshot of your command prompt and folder that contains zip file?
Click to expand...
Click to collapse
sure , here it is
I had this issue when I tried to download the first time. The zip is corrupted. I downloaded the file again and update your adb and fastboot version. I am sure it should work fine.
---------- Post added at 08:35 AM ---------- Previous post was at 08:29 AM ----------
I also suspect the issue could be due to renaming the filename manually into update.zip and when the extension is hidden, it becomes update.zip.zip. please crosscheck to be double sure.
Reboot your computer after you download the file.
I know it sounds weird but I have to do it every time I download the community builds and I've no idea why...otherwise they give the same error. Don't rename the file either there's no need.
nima352000 said:
sure , here it is
Click to expand...
Click to collapse
There could be renaming issue. Try re-downloading file and let me know if you have resolved the issue..
Renaming the file is only for the sake of convenience. Or else you may end up giving a wrong file name by typing error when giving the sideload command as the file names are usually too long.
In this case the file should have been corrupt (not fully downloaded).
Try opening the .zip file.
If it is corrupted, the CRC will fail and it won't open.
In which case you know you have a bad download.
debasish.patra said:
I had this issue when I tried to download the first time. The zip is corrupted. I downloaded the file again and update your adb and fastboot version. I am sure it should work fine.
---------- Post added at 08:35 AM ---------- Previous post was at 08:29 AM ----------
I also suspect the issue could be due to renaming the filename manually into update.zip and when the extension is hidden, it becomes update.zip.zip. please crosscheck to be double sure.
Click to expand...
Click to collapse
Hi , I did try to reinstall the adb drivers , but I will give it a shot again. Also as far as renaming the file the file in the above screen shot is originally downloaded from OnePlus's website without renaming. >dir command shows the file extension to be correct ending with .zip not zip.zip ..
anyways I will reinstall the adb drivers again today
Roxas598 said:
Reboot your computer after you download the file.
I know it sounds weird but I have to do it every time I download the community builds and I've no idea why...otherwise they give the same error. Don't rename the file either there's no need.
Click to expand...
Click to collapse
will give this a try . download a fresh copy with original name , reboot the PC and retry ? is that the sequence you are suggesting ?
kgs1992 said:
Try opening the .zip file.
If it is corrupted, the CRC will fail and it won't open.
In which case you know you have a bad download.
Click to expand...
Click to collapse
doesn't look like that was the case . was able to open the .zip file just fine
nima352000 said:
will give this a try . download a fresh copy with original name , reboot the PC and retry ? is that the sequence you are suggesting ?
Click to expand...
Click to collapse
Yep that's it mate
debasish.patra said:
I had this issue when I tried to download the first time. The zip is corrupted. I downloaded the file again and update your adb and fastboot version. I am sure it should work fine.
---------- Post added at 08:35 AM ---------- Previous post was at 08:29 AM ----------
I also suspect the issue could be due to renaming the filename manually into update.zip and when the extension is hidden, it becomes update.zip.zip. please crosscheck to be double sure.
Click to expand...
Click to collapse
by the way may I get the link to "adb and fastboot version" which you are referring to ? just wanted to make sure I am on the right track
What version of adb are you using?
Your screen print shows 944,128 bytes whereas mine shows 1,479,680 bytes for adb.exe
eg output from the command "adb version"
Android Debug Bridge version 1.0.36
Revision 8f855a3d9b35-android
Looks like you are on:
>adb version
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
Roxas598 said:
Yep that's it mate
Click to expand...
Click to collapse
it actually worked ! thanks a bunch mate !
for anybody who is having the same issue and interested what was the solution , I download a new copy of .zip file from OnePlus websire . restarted my PC and tried again and it worked . Can't make any sense of it but that was the solution