Was running CM12 nightlies that auto encrypted, so went to format data to remove encryption but keyboard in twrp wasnt accepting any characters so hence i wasnt able to decrypt, so i bootloader->fastboot erase userdata...now im back in twrp phone still encrypted (i know the password so im ok) but now theres obviously no rom on the phone how do i push a rom & kernel to my phone adb sideload seems to be hanging on "starting adb sideload feature" and when im in bootloader mode adb doesnt find my device
Fastboot erase userdata doesn't remove the ROM.
Adb isn't designed to work in bootloader. Use of in recovery. You can use adb to push files to /sdcard
See my thread here if you need help
http://forum.xda-developers.com/showthread.php?t=3006500
Plug the phone in to your computer and go to mount and enable mtp. Then go to your computer and copy and paste the rom zip as well as other zips (gapps kernel etc) onto your phone.
Sent from my Nexus 6 using Tapatalk
mak213 said:
Was running CM12 nightlies that auto encrypted, so went to format data to remove encryption but keyboard in twrp wasnt accepting any characters so hence i wasnt able to decrypt, so i bootloader->fastboot erase userdata...now im back in twrp phone still encrypted (i know the password so im ok) but now theres obviously no rom on the phone how do i push a rom & kernel to my phone adb sideload seems to be hanging on "starting adb sideload feature" and when im in bootloader mode adb doesnt find my device
Click to expand...
Click to collapse
Kinda had that issue I just used OTG with the ROM on it that solved my problem
or you can adb push files to your phone, via adb while you are in your recovery. but from what i understand/have heard, cm kernel does not allow decryption.
rootSU said:
Fastboot erase userdata doesn't remove the ROM.
Adb isn't designed to work in bootloader. Use of in recovery. You can use adb to push files to /sdcard
See my thread here if you need help
http://forum.xda-developers.com/showthread.php?t=3006500
Click to expand...
Click to collapse
ya but before i fastboot erase data, i did do a advanced wipe in recovery and did remove rom so cant boot ..
zephiK said:
Plug the phone in to your computer and go to mount and enable mtp. Then go to your computer and copy and paste the rom zip as well as other zips (gapps kernel etc) onto your phone.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
also when i try to mount i get no valid storage partitions found for mtp
simms22 said:
or you can adb push files to your phone, via adb while you are in your recovery. but from what i understand/have heard, cm kernel does not allow decryption.
Click to expand...
Click to collapse
adb is not being read for some reason in recovery, adb sideload is failing to start (never worked for me )
simms22 said:
or you can adb push files to your phone, via adb while you are in your recovery. but from what i understand/have heard, cm kernel does not allow decryption.
Click to expand...
Click to collapse
no they just don't give you an option to not encrypt with they're kernel, so you must flash another kernel after every nightly etc.
mak213 said:
no they just don't give you an option to not encrypt with they're kernel, so you must flash another kernel after every nightly etc.
Click to expand...
Click to collapse
right, that's the direction i was going..
---------- Post added at 03:25 PM ---------- Previous post was at 03:22 PM ----------
mak213 said:
adb is not being read for some reason in recovery, adb sideload is failing to start (never worked for me )
Click to expand...
Click to collapse
is the driver installed? and im not a adb sideload person, but adb push works great for me. just open the main page of twrp, dont press any options, then try adb push.
simms22 said:
is the driver installed? and im not a adb sideload person, but adb push works great for me. just open the main page of twrp, dont press any options, then try adb push.
Click to expand...
Click to collapse
Yea drivers installed was using adb few hours before incident, i unfortauntely resorted nexus toolkit and flashing stock to see if that works for some reason after i fastboot reboot'd out of fastboot it doesnt open twrp anymore just bootloops twrp, let ya know how it goes
EDIT: Just ended up flashing stock image and restarting from step 1 :/
mak213 said:
Yea drivers installed was using adb few hours before incident, i unfortauntely resorted nexus toolkit and flashing stock to see if that works for some reason after i fastboot reboot'd out of fastboot it doesnt open twrp anymore just bootloops twrp, let ya know how it goes
Click to expand...
Click to collapse
can always fastboot twrp again, or fastboot boot it
mak213 said:
adb is not being read for some reason in recovery, adb sideload is failing to start (never worked for me )
Click to expand...
Click to collapse
What does adb devices say when booted in recovery?
Related
USB OTG Info:
USB OTG will show up as external_sd. If external_sd is not mounting, reboot recovery. You must enter recovery with usb already inserted.
Installation:
Unlock bootloader at http://www.htcdev.com/bootloader/
Uncheck fastboot in the rom in power options
Turn phone completely off
Boot into HBOOT>Fastboot
Inside of fastboot. Erase cache. Use command "fastboot erase cache"
Use command "fastboot flash recovery recovery.img"
Root:
To gain root on stock rom. Flash recovery in fastboot then flash this inside of recovery. There are two root programs. Superuser and SuperSU. Both are listed.
Superuser - http://download.clockworkmod.com/superuser/superuser.zip
OR
SuperSU - http://download.chainfire.eu/supersu
Downloads:
http://goo.im/devs/Flyhalf205/MYSTUL/Recovery//recovery-clockwork-6.0.3.4-mystul.img
PC USB Mass Storage:
You can't! http://teamw.in/DataMedia
Touch version is a test. Not sure if it will work properly but the classic version should be fully working. Let me know of any problems.
Flyhalf205 said:
Touch version is a test. Not sure if it will work properly but the classic version should be fully working. Let me know of any problems.
Click to expand...
Click to collapse
At least on my device, the touch recovery does *not* work, but the classic recovery *does*. Cheers!
---------- Post added at 09:52 AM ---------- Previous post was at 09:51 AM ----------
One more thing to note: mounting the internal storage/sdcard does not seem to work either.
nuclear_eclipse said:
At least on my device, the touch recovery does *not* work, but the classic recovery *does*. Cheers!
---------- Post added at 09:52 AM ---------- Previous post was at 09:51 AM ----------
One more thing to note: mounting the internal storage/sdcard does not seem to work either.
Click to expand...
Click to collapse
I'll take down the Touch and get a test build out....Will never work mounting the storage The internal sdcard is actually located in /data/media. It can not be mounted as storage. The only way is to use ADB commands.
Flyhalf205 said:
I'll take down the Touch and get a test build out....Will never work mounting the storage
Click to expand...
Click to collapse
That's quite a shame then. Flashing from /sdcard is by far easier to manage than using adb sideload.... :'(
nuclear_eclipse said:
That's quite a shame then. Flashing from /sdcard is by far easier to manage than using adb sideload.... :'(
Click to expand...
Click to collapse
Adb sideload or adb push to the sdcard.
Sent from my ADR6425LVW using Tapatalk 2
Flyhalf205 said:
Adb sideload or adb push to the sdcard.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
I tried adb pushing to /sdcard while running the recovery image, but it still refused to flash from there because it would fail trying to mount /sdcard. adb sideload was the only method that actually worked. Unless I'm missing something...
nuclear_eclipse said:
I tried adb pushing to /sdcard while running the recovery image, but it still refused to flash from there because it would fail trying to mount /sdcard. adb sideload was the only method that actually worked. Unless I'm missing something...
Click to expand...
Click to collapse
Not sure. Newer HTC phones are strange in the recovery. You mind testing TWRP?
Sent from my ADR6425LVW using Tapatalk 2
Sure, I'll test it shortly.
nuclear_eclipse said:
Sure, I'll test it shortly.
Click to expand...
Click to collapse
So, were you able to successfully root the First as well? Or was that back-and-forth about adb loading/side-loading about root? I tried re-reading the posts, but my newb-translator is on the fritz.
lordlittlebrooks said:
So, were you able to successfully root the First as well? Or was that back-and-forth about adb loading/side-loading about root? I tried re-reading the posts, but my newb-translator is on the fritz.
Click to expand...
Click to collapse
Yes, I have successfully rooted my First with the recovery and Superuser zip from the first post. Flash the recovery and reboot into it, then choose install zip from sideload, and then have your phone connected to the PC with the superuser zip, and run `adb sideload path/to/Superuser.zip`. Once that completes, reboot the phone, and you should have full root access.
nuclear_eclipse said:
Yes, I have successfully rooted my First with the recovery and Superuser zip from the first post. Flash the recovery and reboot into it, then choose install zip from sideload, and then have your phone connected to the PC with the superuser zip, and run `adb sideload path/to/Superuser.zip`. Once that completes, reboot the phone, and you should have full root access.
Click to expand...
Click to collapse
Thanks for spelling that out. Beers headed for you and flyhalf. Can't wait to get home and root my First!
lordlittlebrooks said:
Thanks for spelling that out. Beers headed for you and flyhalf. Can't wait to get home and root my First!
Click to expand...
Click to collapse
Thanks Glad everything is working out. Uploading a new TWRP build if anyone likes that better.
I've added a few extra features into the classic version of CWM. Power off option in the menu and reboot to bootloader in advance menu. Regular CWM doesn't have those
nuclear_eclipse said:
Yes, I have successfully rooted my First with the recovery and Superuser zip from the first post. Flash the recovery and reboot into it, then choose install zip from sideload, and then have your phone connected to the PC with the superuser zip, and run `adb sideload path/to/Superuser.zip`. Once that completes, reboot the phone, and you should have full root access.
Click to expand...
Click to collapse
Is it not possible to just put zip on sdcard and choose install zip from sdcard?
Sent from my HTC first
phositadc said:
Is it not possible to just put zip on sdcard and choose install zip from sdcard?
Sent from my HTC first
Click to expand...
Click to collapse
Since the recovery currently can't mount the sdcard partition, any attempt to flash from sdcard fails. The only method that works afaik is the option to flash via sideload, which requires the phone to be attached to a PC running adb. I'm not certain, but it sounds like this would also prevent the CyanogenMod built-in update mechanism to fail as well...
nuclear_eclipse said:
Since the recovery currently can't mount the sdcard partition, any attempt to flash from sdcard fails. The only method that works afaik is the option to flash via sideload, which requires the phone to be attached to a PC running adb. I'm not certain, but it sounds like this would also prevent the CyanogenMod built-in update mechanism to fail as well...
Click to expand...
Click to collapse
Can you see the folders on the sdcard when you go to install zip from sdcard?
Sent from my ADR6425LVW using Tapatalk 2
Flyhalf205 said:
Can you see the folders on the sdcard when you go to install zip from sdcard?
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
No.
nuclear_eclipse said:
No.
Click to expand...
Click to collapse
Okay. I'll need to look over my configs again. New build of twrp graphics should be fixed. See if you can see sdcard on that.
EDIT: I think I see what I did wrong in my config file. Building a new build.
Sent from my ADR6425LVW using Tapatalk 2
New build of CWM classic is up. Internal storage should work.
Flyhalf205 said:
New build of CWM classic is up. Internal storage should work.
Click to expand...
Click to collapse
Internal storage worked like a charm! Thanks again FlyHalf!
Hey guys, I accidentley wiped my sdcard when I reunlocked the bootloader. I have a custom rom that was on previously but its stock in a loop. I tried to push another room using adb sideload but when i do I got * Cannot read 'sideload'. I dont know any other way i can connect the phone to computer to flash another rom. please help.
Thanks
Update:
I can push the rom but i get this error when trying to install "E: unable to mount 'data' "
p1mpin said:
Hey guys, I accidentley wiped my sdcard when I reunlocked the bootloader. I have a custom rom that was on previously but its stock in a loop. I tried to push another room using adb sideload but when i do I got * Cannot read 'sideload'. I dont know any other way i can connect the phone to computer to flash another rom. please help.
Thanks
Update:
I can push the rom but i get this error when trying to install "E: unable to mount 'data' "
Click to expand...
Click to collapse
when I had that problem, I ended up wiping everything and then rebooted to recovery and it finally worked.
p1mpin said:
Hey guys, I accidentley wiped my sdcard when I reunlocked the bootloader. I have a custom rom that was on previously but its stock in a loop. I tried to push another room using adb sideload but when i do I got * Cannot read 'sideload'. I dont know any other way i can connect the phone to computer to flash another rom. please help.
Thanks
Update:
I can push the rom but i get this error when trying to install "E: unable to mount 'data' "
Click to expand...
Click to collapse
Try what @JudgeFutta said. The error's most likely due to corrupt partitions.
p1mpin said:
Hey guys, I accidentley wiped my sdcard when I reunlocked the bootloader. I have a custom rom that was on previously but its stock in a loop. I tried to push another room using adb sideload but when i do I got * Cannot read 'sideload'. I dont know any other way i can connect the phone to computer to flash another rom. please help.
Thanks
Update:
I can push the rom but i get this error when trying to install "E: unable to mount 'data' "
Click to expand...
Click to collapse
Try to get in Recovery and from mount option mount system and then try it will work or try this
Make Sure HTC Drivers are installed and ADB is already working
1. Reboot into TWRP
2. in TWRP, Hit andvanced and find Sideload
3. Swipe to start Sideload
4. Open a CMD Prompt window and Change Directories to where your adb.exe is
5. type adb devices and it should show your device conntected and say sideload
6. Your ZIP file should already be in your adb folder
7. You are now ready to push the zip.....
8. type adb sideload nameofzip.zip
9. Wait until it says 100% and reboot back into recovery to flash the ROM
10. If hitting power does not make the screen come one, type adb reboot recovery
11. if adb reboot recovery does not work, hold power and volume down until it reboots to fastboot then go to recovery
ADB Push from Recovery - If Sideload Fails For You
adb push rom.zip /data/media/0/
Be sure u r in Recovery when using ADB Push command.
Thanks guys. What i found out is that i had a corrupt partition so I formated the sdcard since there was nothing on it and it worked. I pushed the rom through adb but i didnt do the sideload method. I have liquid smooth on it now but I want a sense rom. any suggestions for a good one?
p1mpin said:
Thanks guys. What i found out is that i had a corrupt partition so I formated the sdcard since there was nothing on it and it worked. I pushed the rom through adb but i didnt do the sideload method. I have liquid smooth on it now but I want a sense rom. any suggestions for a good one?
Click to expand...
Click to collapse
Why not try the best Sense rom available. http://forum.xda-developers.com/showthread.php?t=2502430
Gd luck
User420s said:
Why not try the best Sense rom available. http://forum.xda-developers.com/showthread.php?t=2502430
Gd luck
Click to expand...
Click to collapse
@p1mpin Can vouch for that ROM, it's amazing. Might also want to flash Kangaroo Kernel while you're at it. It'll give you great battery life.
Disclaimer: If you are not comfortable with using Fastboot and ADB and editing system files than this guide might not be for you. At this point this is what I have to offer.
Click here for the unofficial twrp image - Latest version as of 12/27/14
So getting right into it.
1. Turn on ADB mode on the watch by going to about and tapping the build info 7 times.
2. Download ADB and Fastboot utilties
3. Plug the watch into the computer and your phone should vibrate and ask you to accept the computers fingerprint, tick the check box to always allow and hit ok
4. Open up a command prompt or terminal inside of where the ADB utilities are located and enter
Code:
adb reboot bootloader
This next step will wipe your data!
5. Now you should be in fastboot, go ahead and on the terminal use the next code and follow prompts to unlock
Code:
fastboot oem unlock
6. Now after you re-set up your watch again you will need to do step 1 and 3 again.
Please do not skip step 6!
7. Go ahead and issue
Code:
adb reboot bootloader
8. Flash unofficial twrp, make sure the recovery image file is in the same location as fastboot than issue
Code:
fastboot flash recovery YOURIMGNAMEHERE.img
9. Upon successfully doing that you should have twrp installed
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB use the proper name of what you downloaded. Issue
Code:
adb push SUPERSUNAMEHERE.zip /sdcard/
11. Issue
Code:
adb reboot recovery
12. than using the very tiny TWRP and somewhat messed up go ahead and use it to install the supersu.zip under the folder /sdcard
13. Enjoy root and twrp.
I will make this guide into a much easier Java program in the very near future to make it easier to use.
This was typed up pretty fast and it is kinda hacky, I will work on a bat script and a shell script if we have enough osx users here. I'm sure someone will come along and make this better if I don't get around to it.
Credits:
Dees-Troy for his TWRP support for dory our fish brother device which worked on our device
Chainfire for all his hard work these many years
Q: ADB complains there is no device listed.
A: Install universal ADB drivers and then go to device manager and under the device with a yellow warning icon go to update driver, Browse my computer, let me pick from list of device drivers, than Google ADB interface. If it still complains turn off debugging, than turn it back on, revoke authorization, then disable and re-enable again.
One more just in case.
Great work!!
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?
hatefuel19 said:
Just got the watch today and couldn't be happier. Custom kernel, TWRP and root (well sort of) all within 6 hours of having this watch.
I say root (sort of) because SU is force closing when running su in adb shell. First time it crashed adb on PC and had to reboot watch. Now it just force closes on my watch and adb exits on PC. What is the most current version of SuperSU? I have 1.94 from Chainfire's site.
Thank you SO MUCH for this! Do you or your team have a paypal?
Click to expand...
Click to collapse
The latest supersu is version 2.36 dated 11.27.2014. 1.94 is well over a year old, you need to update for sure that is why you are force closing.
I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!
hatefuel19 said:
I figured that's what it was. Feeel real dumb for not finding the newest version the first time. Also most current is now 2.37 XD
Edit: That got it! Thanks tonu!
Click to expand...
Click to collapse
I'm here to help! I'm working on adding other mods to my other thread right now I'm working on getting busybox working.
Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
---------- Post added at 09:31 PM ---------- Previous post was at 09:28 PM ----------
jimmydigital00 said:
Thanks for doing all of this work.
I was hoping you could help me with a step I am stuck on.
10. Lots in one step here, download the latest supersu.zip flashable file and put it in the same folder as ADB. Issue "adb push SUPERSUNAMEHERE.zip /sdcard/
When I do this it is saying permission denied. Also, should the watch be in recovery or fully booted when I run this command?
Thanks
Click to expand...
Click to collapse
Disregard I did it again and for some reason it worked. Maybe I need to reboot first.
Recovery
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?
adamrobles said:
I went through your command and everything worked until I ran:
fastboot flash recovery UNOFFICIAL-openrecovery-twrp-2.8.0.0-lenok.img
Now the device just boots into the recovery and not into the system. The system/data partitions keep saying:
E:Unable to mount /data
E:Unable to mount /system
I am very comfortable with fastboot and adb so I do not know what I did wrong here.
Any ideas?
Click to expand...
Click to collapse
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app
reflashed
tonu42 said:
Try reflashing the recovery IMG again. And check back here.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.
adamrobles said:
I reflashed the recovery you provided and I keep rebooting to system but it takes me to twrp.
I am in the process of downloading the system dump from another thread to hopefully flash those to get back into the system.
Click to expand...
Click to collapse
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
Thank you for that information, I stopped the download of the dump.
Downloading the stock recovery now.
---------- Post added at 02:24 PM ---------- Previous post was at 02:10 PM ----------
tonu42 said:
The dump is extracted from the system.img, you won't be able to flash it in any way. None of this guide touches system files besides the root stuff which shouldn't affect boot. Try flashing the stock recovery.img instead.
Click to expand...
Click to collapse
I must have skipped a step...
installed stock recovery
booted into the watch system
enabled adb debugging
reboot to bootloader
install your recovery image
rebooted
pushed supersu
rebooted to twrp
installed supersu
rebooted to system
adb shell - verified root!
You are awesome! Thank you for taking the time to help me!
HYPE for 5.0.1
'm Hype! can't wait to flash the first 5.0.1 system dump on this as stated by +Darek Ross we MAY be receiving update as early as today!
I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...
zvieratko said:
I did this yesterday, and run into the same problem - TWRP spitting out errors when flashing
It was caused by NOT rebooting after unlocking bootloader, but proceeding with the flash rightaway - this apparently leaves the watch in an empty state (no /sdcard or /system contents) and it needs to boot up at least once before you flash anything
So the correct procedure is like this
1) enable development options
2) enable usb debugging
3) adb reboot-bootloader
4) fastboot oem unlock
5) let the watch boot normally, pair with your phone, enable development options and usb debugging again
6) adb reboot-bootloader
7) fastboot flash recovery recovery.img
8) fastboot reboot
9) adb push supersu.zip /sdcard/
10) adb reboot recovery
11) flash supersu.zip
Apparently, there is a problem when the original kernel is not present after "fastboot oem unlock" - the watch will be left empty, while on the original kernel it "reinstalls"
I typed this from memory, but I think you should know how these things work anyway, as there's not much for a "normal" user to do anyway... yet...
Click to expand...
Click to collapse
My guide is setup like the one you put there. In order to get adb working again you need to re setup the watch step 6. Read the instructions carefully. I'll post a batch script later to simplify this.
Sent from my A0001 using XDA Free mobile app
Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there
zvieratko said:
Step 6 doesn't really say "you need to do this, OR ELSE", it seems like you just rehash the factory reset thing
And you should put step 10 before step 6, it can't really be done in that order...
but again, I guess the people trying this should now how it works, so no biggie, but since a few of us got hit by that "no initial boot" issue, it would be better to put a note in there
Click to expand...
Click to collapse
By default debugging is disabled, I'm not sure how you were able to issue an ADB command on step 7 with out first performing step 6.
Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)
zvieratko said:
Aaah, sorry, should have been "after step 6"
another option is to do adb push with recovery loaded
I guess that's why I got that error before, because I combined 5+8 and flashed the recovery, but TWRP was unable to revive the watch from factory reset state (which makes me think it should not be on the watch unless needed...)
Click to expand...
Click to collapse
Ah I see, yea the guide is written as the absolute minimum to work right now. Like I said later today I'll try to post a script that automates all of this, its much easier.
Hello all,
I made a big mistake and wiped my Sd card on my rooted, Unlocked M7. I was able to get recovery(TWRP) back on but for the life of me cannot sideload a Rom on it? At the moment it has no OS. So that means I cannot open usb debugging so I could manually place the ViperOne rom back on the SD. I've never sideloaded anything but after watching many youtube videos and failing ( cannot read ROM.zip) its driving me nuts. Is there maybe an easier way? Maybe something else I can try?
I have tried to load for both desktop and platform tools( both I can see my device).
Splitshot said:
( cannot read ROM.zip)
Click to expand...
Click to collapse
This error is usually caused by the file being in the wrong location. Make sure "ROM.zip" is in the same folder where you have adb and fastboot on your computer.
---------- Post added at 10:36 AM ---------- Previous post was at 10:35 AM ----------
TWRP 2.6.4.0 also include mtp drivers so you can see your device storage on your ocmputer when booted in recovery mode.
Splitshot said:
Hello all,
I made a big mistake and wiped my Sd card on my rooted, Unlocked M7. I was able to get recovery(TWRP) back on but for the life of me cannot sideload a Rom on it? At the moment it has no OS. So that means I cannot open usb debugging so I could manually place the ViperOne rom back on the SD. I've never sideloaded anything but after watching many youtube videos and failing ( cannot read ROM.zip) its driving me nuts. Is there maybe an easier way? Maybe something else I can try?
I have tried to load for both desktop and platform tools( both I can see my device).
Click to expand...
Click to collapse
alray said:
This error is usually caused by the file being in the wrong location. Make sure "ROM.zip" is in the same folder where you have adb and fastboot on your computer.
---------- Post added at 10:36 AM ---------- Previous post was at 10:35 AM ----------
TWRP 2.6.4.0 also include mtp drivers so you can see your device storage on your ocmputer when booted in recovery mode.
Click to expand...
Click to collapse
Like alray said flash TWRP 2.8.4.0 and the phone will be seen in windows and you can just copy the file to the phone and flash it
I already had a "Install recovery v1.2" in my downloads so I tried this because I was unsuccessful with all the other attempts and low and behold it worked. although its an older version of TWRP (2.6.3). would it make a difference not having the latest? now that recovery is there I was hoping to push a ROM then update the recovery through root manager.
I just read alray's last line about the mtp drivers. OK, I will first get my folders working better, upgrade to a newer version TWRP and then push a rom. Is there a difference in "Fastboot adb sideload flash ViperOne.zip" and "
" adb sideload push ViperOne.zip"? Two video's used 2 different commands.
Splitshot said:
I already had a "Install recovery v1.2" in my downloads so I tried this because I was unsuccessful with all the other attempts and low and behold it worked. although its an older version of TWRP (2.6.3). would it make a difference not having the latest? now that recovery is there I was hoping to push a ROM then update the recovery through root manager.
I just read alray's last line about the mtp drivers. OK, I will first get my folders working better, upgrade to a newer version TWRP and then push a rom. Is there a difference in "Fastboot adb sideload flash ViperOne.zip" and "
" adb sideload push ViperOne.zip"? Two video's used 2 different commands.
Click to expand...
Click to collapse
you don't need adb at all if you load TWRP 2.8.4.0 you just copy the file in windows like to a flash drive
Splitshot said:
upgrade to a newer version TWRP and then push a rom.
Click to expand...
Click to collapse
If you are going to update twrp to 2.8.4.0, you will not need to push or sideload the rom, just copy it to your phone storage using the windows explorer. Navigate to "my computer --> One --> Internal storage" and copy your rom there.
Is there a difference in "Fastboot adb sideload flash ViperOne.zip" and "
" adb sideload push ViperOne.zip"? Two video's used 2 different commands.
Click to expand...
Click to collapse
These 2 commands means nothing. :laugh: SO no, there is no difference between these 2 commands, both will fail lol
if you want to use adb push:
Code:
adb push name_of_rom.zip /sdcard
if you want to sideload:
Code:
adb sideload name_of_rom.zip
But like i said, you don't need to use these commands to get your rom on your phone if you are gonna update twrp to 2.8.4.0.
download twrp 2.8.4.0, save it to the same folder where you have adb and fastboot installed on your computer. Open a command prompt from that folder, boot your phone in bootloader/fastboot usb mode.
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then boot in recovery mode
you'll now see your phone storage on your computer, copy (drag and drop) your rom.zip to your phone storage.
Here is a copy of the stock recovery.img from version 1.1.1.1929530 if anyone needs it:
Must enable ADB Debugging in developer menu! (About > tap build number to unlock developer options > developer options > Enable ADB Debugging) Make sure to grant access to your computer select ALWAYS.
Must have Unlocked bootloader: (which I assume you have if you are trying to go back to stock from TWRP)
Currently there is an unofficial build of TWRP that you can find here: http://forum.xda-developers.com/watch-urbane/general/twrp-2-8-6-0-test-build-t3122005 (thanks @Tasssadar)
Instructions:
ADB DEBUGGING ENABLED!
- adb reboot bootloader
- fastboot flash recovery <location of stock img file>
- reboot to recovery to make sure everything worked.
- adb reboot
I am not responsible for anything that happens to your device, please do not come to me if you brick your Android Wear, I am just providing the stock recovery for anyone who needs it.
I have tested this myself after flashing TWRP recovery. Works fine for me so you should have no issues.
Download Link:
http://1drv.ms/1FOVnNR
sharky481232 said:
Here is a copy of the stock recovery.img from version 1.1.1.1929530 if anyone needs it:
Must enable ADB Debugging in developer menu! (About > tap build number to unlock developer options > developer options > Enable ADB Debugging) Make sure to grant access to your computer select ALWAYS.
Must have Unlocked bootloader: (which I assume you have if you are trying to go back to stock from TWRP)
Currently there is an unofficial build of TWRP that you can find here: http://forum.xda-developers.com/watch-urbane/general/twrp-2-8-6-0-test-build-t3122005 (thanks @Tasssadar)
Instructions:
ADB DEBUGGING ENABLED!
- adb reboot bootloader
- fastboot flash recovery <location of stock img file>
- reboot to recovery to make sure everything worked.
- adb reboot
I am not responsible for anything that happens to your device, please do not come to me if you brick your Android Wear, I am just providing the stock recovery for anyone who needs it.
I have tested this myself after flashing TWRP recovery. Works fine for me so you should have no issues.
Download Link:
http://1drv.ms/1FOVnNR
Click to expand...
Click to collapse
Are backups and restores working? Or is there not enough memory? Anyone??
suzook said:
Are backups and restores working? Or is there not enough memory? Anyone??
Click to expand...
Click to collapse
I usually do a backup then once its done I use "adb pull" to my PC and delete the copy on the device. just safer that way. Anytime i need to restore I just "adb push" back to the same directory I pulled from.
sharky481232 said:
I usually do a backup then once its done I use "adb pull" to my PC and delete the copy on the device. just safer that way. Anytime i need to restore I just "adb push" back to the same directory I pulled from.
Click to expand...
Click to collapse
Thanks, gonna try and leave it on. I switch between my note4 and nexus 6...thinking I could just restore my backup when I switch. I wish wear was able to sync to multiple phones.
suzook said:
Thanks, gonna try and leave it on. I switch between my note4 and nexus 6...thinking I could just restore my backup when I switch. I wish wear was able to sync to multiple phones.
Click to expand...
Click to collapse
Havent tried this myself but seems like a faster process then restoring backups:
http://forum.xda-developers.com/and.../app-reset-wear-client-switch-phones-t3058962
sharky481232 said:
Havent tried this myself but seems like a faster process then restoring backups:
http://forum.xda-developers.com/and.../app-reset-wear-client-switch-phones-t3058962
Click to expand...
Click to collapse
Thanks, I'll give that a look. BTW, I'm trying to flash recovery, my adb sees my watch, but when I try fastboot OEM unlock, I get stuck at "waiting for device"..... Any ideas???
suzook said:
Thanks, I'll give that a look. BTW, I'm trying to flash recovery, my adb sees my watch, but when I try fastboot OEM unlock, I get stuck at "waiting for device"..... Any ideas???
Click to expand...
Click to collapse
If you are using Linux, make sure you are in SU mode, also sometimes - I have to wait til the watch is in bootloader mode then remove the watch from dock and put it back on then the computer will find it.
Any chance you could provide a system.img too? I semi-bricked my watch and I need a system.img dump to get it up and running again - I can't use adb to push and flash a .zip, so a .img is my only option right now.
BJSerpas said:
Any chance you could provide a system.img too? I semi-bricked my watch and I need a system.img dump to get it up and running again - I can't use adb to push and flash a .zip, so a .img is my only option right now.
Click to expand...
Click to collapse
Go here http://forum.xda-developers.com/watch-urbane/general/twrp-2-8-6-0-test-build-t3122005. There is a TWRP Urbane 5.1.1. image backup, including boot and system. Follow the instructions there and you'll be fined. I have just done so and recovered my urbane from a failed ROM.
Hello,
I have installed TWRP in order to root my Urbane (to increase the vibration intensity).
I need to reinstall the stock recovery to allow ROM to auto-install OTAs when available? or TWRP can be used by the system to install OTAs?
Thanks!