Adb Sideload - One (M7) Q&A, Help & Troubleshooting

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.

Related

Help needed, device wiped

I was changing rom according to instructions and accidentally I have deleted my rom.zip. Now I'm stuck in recovery with nothing to flash and no idea how to push rom.zip to phone memory. I have otg cable. Can anyone come up with a solution or direction to relevant topic ?
Pum4 said:
I was changing rom according to instructions and accidentally I have deleted my rom.zip. Now I'm stuck in recovery with nothing to flash and no idea how to push rom.zip to phone memory. I have otg cable. Can anyone come up with a solution or direction to relevant topic ?
Click to expand...
Click to collapse
Easiest thing would be to put your ROM.zip on your usb and plug it into your phone before entering recovery. I'm not sure if Cwm classic supports otg but Cwm touch and twrp do
Sent from my HTC One using xda premium
redbull123 said:
Easiest thing would be to put your ROM.zip on your usb and plug it into your phone before entering recovery. I'm not sure if Cwm classic supports otg but Cwm touch and twrp do
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
will try. Should I flash it from pendrive or copy to internal and then install ?
I've tried and even it should be possible the device cant mount externel sd what to do now ?
Pum4 said:
will try. Should I flash it from pendrive or copy to internal and then install ?
Click to expand...
Click to collapse
I think it's called external_sd in recovery. Just flash it from there.
Sent from my HTC One using xda premium
---------- Post added at 08:20 PM ---------- Previous post was at 08:11 PM ----------
Pum4 said:
will try. Should I flash it from pendrive or copy to internal and then install ?
I've tried and even it should be possible the device cant mount externel sd what to do now ?
Click to expand...
Click to collapse
Apologies, I've just tried it myself in CWM Touch 6.0.3.1...
Go to Bootloader screen and plug in your cable
enter recovery
install zip from sdcard
choose zip from external sdcard
Works for me...
Sometimes if it doesn't mount I go to 'backup and restore' -> restore from external sdcard -> Go Back -> Go Back -> try it flashing from 'install zip from sdcard' again. (Although I have a nandroid backup on my usb so that may not work for you)
redbull123 said:
I think it's called external_sd in recovery. Just flash it from there.
Sent from my HTC One using xda premium
---------- Post added at 08:20 PM ---------- Previous post was at 08:11 PM ----------
Apologies, I've just tried it myself in CWM Touch 6.0.3.1...
Go to Bootloader screen and plug in your cable
enter recovery
install zip from sdcard
choose zip from external sdcard
Works for me...
Sometimes if it doesn't mount I go to 'backup and restore' -> restore from external sdcard -> Go Back -> Go Back -> try it flashing from 'install zip from sdcard' again. (Although I have a nandroid backup on my usb so that may not work for you)
Click to expand...
Click to collapse
when i try to do that, there is a commend listed: E: Cant mount /external_sd damn it
Pum4 said:
when i try to do that, there is a commend listed: E: Cant mount /external_sd damn it
Click to expand...
Click to collapse
Can you use adb & fastboot commands?
redbull123 said:
Can you use adb & fastboot commands?
Click to expand...
Click to collapse
yes I can, is mini sdk enough ?
Pum4 said:
yes I can, is mini sdk enough ?
Click to expand...
Click to collapse
yeah...
put your rom.zip in your mini-sdk folder
put your phone to the bootloader screen -> select fastboot -> it should now say 'fastboot usb'
hold shift and right-click on your mini-sdk folder -> Open Command Window Here
command: fastboot devices
if your device shows, enter recovery
command: adb devices
if your device shows,
adb push name_of_your_rom.zip /sdcard be sure to put a space before /sdcard. be sure the 'name_of_your_rom' is named exactly the same as your rom.zip
After a while your rom should be on your sdcard, just flash it as normal.
redbull123 said:
yeah...
put your rom.zip in your mini-sdk folder
put your phone to the bootloader screen -> select fastboot -> it should now say 'fastboot usb'
hold shift and right-click on your mini-sdk folder -> Open Command Window Here
command: fastboot devices
if your device shows, enter recovery
command: adb devices
if your device shows,
adb push name_of_your_rom.zip /sdcard be sure to put a space before /sdcard. be sure the 'name_of_your_rom' is named exactly the same as your rom.zip
After a while your rom should be on your sdcard, just flash it as normal.
Click to expand...
Click to collapse
Just did as you said. The tricky part is with opening command line in the specified folder, I would never have guess that you have to hold shift.
Now waiting for the file being moved to sdcard, after push command the _ is blinking as the file is being send right. File is sent XXX bytes in 222.sec
I tried to instal from the sdcard the recovery reboots itself when I press instal from sdcard
Pum4 said:
Just did as you said. The tricky part is with opening command line in the specified folder, I would never have guess that you have to hold shift.
Now waiting for the file being moved to sdcard, after push command the _ is blinking as the file is being send right. File is sent XXX bytes in 222.sec
I tried to instal from the sdcard the recovery reboots itself when I press instal from sdcard
Click to expand...
Click to collapse
Maybe try fastboot screen again,
fastboot erase cache
redbull123 said:
Maybe try fastboot screen again,
fastboot erase cache
Click to expand...
Click to collapse
remote not allowed
Pum4 said:
remote not allowed
Click to expand...
Click to collapse
'fastboot usb' should be on the screen
again, open cmd from your mini-sdk folder
do 'fastboot devices' just to be sure your device is seen
redbull123 said:
'fastboot usb' should be on the screen
again, open cmd from your mini-sdk folder
do 'fastboot devices' just to be sure your device is seen
Click to expand...
Click to collapse
done, entered recovery and when I press instal from sdcard the device is re-booting
the charging led is not lighiting up i fear i will drain it to zero and it will not charge again
Pum4 said:
done, entered recovery and when I press instal from sdcard the device is re-booting
the charging led is not lighiting up i fear i will drain it to zero and it will not charge again
Click to expand...
Click to collapse
ok, can you select install zip from sideload or does it crash?
if you can, select it and command in cmd (from your mini-sdk folder)
adb sideload name_of_your_rom.zip
once its finished sideloading it should begin install on your phone automatically
If you can't do that, try re-flashing your recovery and try everything again.
fastboot flash recovery name_of_your_recovery.img
(in 'fastboot usb') (name_of_your_recovery.img should be in mini-sdk folder)
redbull123 said:
ok, can you select install zip from sideload or does it crash?
if you can, select it and command in cmd (from your mini-sdk folder)
adb sideload name_of_your_rom.zip
once its finished sideloading it should begin install on your phone automatically
If you can't do that, try re-flashing your recovery and try everything again.
fastboot flash recovery name_of_your_recovery.img
(in 'fastboot usb') (name_of_your_recovery.img should be in mini-sdk folder)
Click to expand...
Click to collapse
I pushed sideload:
failed to open driver control: no csuch file or directory (x2)
sideload started now sen the package you want to apply to the device with adb sideload <filename>
in cmd adb devices:
HTXXXXXXX sideload
after command sideload progress is showed but I fear I have deleted sth important on the device ;/
rom was sideloaded but instalation was far to quick and it is still stuck on htc quietly brilliant... I have bricked my device (
Pum4 said:
I pushed sideload:
failed to open driver control: no csuch file or directory (x2)
sideload started now sen the package you want to apply to the device with adb sideload <filename>
in cmd adb devices:
HTXXXXXXX sideload
after command sideload progress is showed but I fear I have deleted sth important on the device ;/
rom was sideloaded but instalation was far to quick and it is still stuck on htc quietly brilliant... I have bricked my device (
Click to expand...
Click to collapse
Just hold down volume down + power button until it reboots. You may have to do it under a bright light. Keep holding them until your fastboot/hboot screen appears.
Try re-flashing your recovery as I said above and try again - if that doesn't work then I'm afraid I'm out of ideas
What ROM are you trying to install??
redbull123 said:
Just hold down volume down + power button until it reboots. You may have to do it under a bright light. Keep holding them until your fastboot/hboot screen appears.
Try re-flashing your recovery as I said above and try again - if that doesn't work then I'm afraid I'm out of ideas
What ROM are you trying to install??
Click to expand...
Click to collapse
just stock 4.2.2... I will try to do that again and if it doesnt work I will try to use ruu method but I wonder do I have to flash stock recovery then ?
Pum4 said:
just stock 4.2.2... I will try to do that again and if it doesnt work I will try to use ruu method but I wonder do I have to flash stock recovery then ?
Click to expand...
Click to collapse
send a link to the page you got the rom. i've never used RUU but I think it flashes stock recovery during the process
redbull123 said:
send a link to the page you got the rom. i've never used RUU but I think it flashes stock recovery during the process
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2281365
http://forum.xda-developers.com/showthread.php?t=2207874
I'm trying to find modeid and cidnum and its pn07100000 and orangb10... dont know which to choose...
I need mz phone tomoorow and Im getting desperate
I have flashed stock recovery and still it bootloops, getting hopeless
Pum4 said:
http://forum.xda-developers.com/showthread.php?t=2281365
http://forum.xda-developers.com/showthread.php?t=2207874
I'm trying to find modeid and cidnum and its pn07100000 and orangb10... dont know which to choose...
I need mz phone tomoorow and Im getting desperate
I have flashed stock recovery and still it bootloops, getting hopeless
Click to expand...
Click to collapse
I don't know anything about RUUs but this is what I would do just to get a working phone:
Flash custom recovery again
Flash Android Revolution 10.2 from here:
http://forum.xda-developers.com/showthread.php?p=38939202
Using adb push or sideload
It's 4.2.2 and close to stock
Sent from my HTC One using xda premium

[Q] I think I bricked my One.

I have a UK Vodafone HTC One. It's running the Trickdrpid Rom with TWRP 2.5.0.0 recovery. Everything was working fine until I flashed tbaldens kernel to enable lock2wake function. Everything went ok with flashing (I think!) but upon reboot, nothing. Just flashing back and home keys when I press the power button. I can get into recovery but have no rom on my internal SD to reflash. The PC gives the USB spund when i boot into recovery, but the phone storage doesnt show up on PC. Is there any way to get another Rom on the storage to reflash, or is it bricked? Please help.
There is an option in TWRP to sideload with adb. Try pushing a new Rom with the ADB Push romname.zip
Then you should be able to locate it and flash it
Sent from my HTC One using xda app-developers app
gazlufc said:
There is an option in TWRP to sideload with adb. Try pushing a new Rom with the ADB Push romname.zip
Then you should be able to locate it and flash it
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Thanks for the quick reply. Is there a tutorial on ADB anywhere? I've not had experience using it before.
http://developer.android.com/tools/help/adb.html
You will need to install Android SDK if you don't already have it installed.
If you are using windows open Command prompt and Change in to the android-sdk/platform-tools folder.
In here you can run the ADB devices command to see if your device is showing up as connected.
If so copy the rom in the the platform-tools folder to make it easier.
so lets say your rom is called rom.zip the command to push would be
adb push rom.zip /sdcard/ (OR WHAT EVER LOCATION YOU WANT)
If all goes well you should be select zip from storage in TWRP and flash it.
Hope this helps
---------- Post added at 02:12 PM ---------- Previous post was at 01:18 PM ----------
liverman666 said:
I have a UK Vodafone HTC One. It's running the Trickdrpid Rom with TWRP 2.5.0.0 recovery. Everything was working fine until I flashed tbaldens kernel to enable lock2wake function. Everything went ok with flashing (I think!) but upon reboot, nothing. Just flashing back and home keys when I press the power button. I can get into recovery but have no rom on my internal SD to reflash. The PC gives the USB spund when i boot into recovery, but the phone storage doesnt show up on PC. Is there any way to get another Rom on the storage to reflash, or is it bricked? Please help.
Click to expand...
Click to collapse
I see that the command to sideload is 'adb sideload rom.zip'
My appologies if this didn't work up to now
gazlufc said:
http://developer.android.com/tools/help/adb.html
You will need to install Android SDK if you don't already have it installed.
If you are using windows open Command prompt and Change in to the android-sdk/platform-tools folder.
In here you can run the ADB devices command to see if your device is showing up as connected.
If so copy the rom in the the platform-tools folder to make it easier.
so lets say your rom is called rom.zip the command to push would be
adb push rom.zip /sdcard/ (OR WHAT EVER LOCATION YOU WANT)
If all goes well you should be select zip from storage in TWRP and flash it.
Hope this helps
---------- Post added at 02:12 PM ---------- Previous post was at 01:18 PM ----------
I see that the command to sideload is 'adb sideload rom.zip'
My appologies if this didn't work up to now
Click to expand...
Click to collapse
Ok. I've managed to upload the Rom via sideload. But now I can't find it anywhere on the SD card?
Coincidentally i'm having the same issue when installing the same exact kernal (lock2wake) last night.
It soft bricked after it was flashed using the AndroidRevolution rom
No USB access despite popups and there are no roms installed on my SD.
I can access the bootloader and recovery (Clockwork) but thats about it.
I'll follow the instructions Gaz posted above and see where it takes me.
There should be an option to install from side load in your recovery.
If you can't find it I would recommend flashing CWM for the flash. You can do it via the fastboot method or the HTC one AIO toolkit. The toolkit option is the easiest.
Then when you are in CWM select install zip. There should be an option in there to install from ADB sideload.
Here you push the the Rom zip via the adb sideload Rom.zip and then it should install. Let me know how you guys get on
If you need anymore help feel free to PM me and I'll try to explain it more if needed
Sent from my HTC One using xda app-developers app
got it working! thanks gaz
Review:
1. I (soft) bricked my phone flashing TeamSeven Sense "Home2Wake" kernel
http://forum.xda-developers.com/showthread.php?t=2255160
2. My phone currently had the android revolution 12.0 rom installed
http://forum.xda-developers.com/showthread.php?t=2183023
3. To unbrick my phone and get access to the bootloader/recovery, i perform the following step
gunnyman said:
put the phone under a bright light.
hold down power, lights will flash and phone will shut down in about 15-20 seconds
then hold volume down and power to get back to bootloader
Click to expand...
Click to collapse
4. Once i had access to the bootloader, i navigated to recovery (CWM-Touch) but couldn't reflash my rom since i no longer had the zip file on my internal SD.
5. So I followed Gaz instructions posted above by installing the Android SDK files from http://developer.android.com/tools/help/adb.html
6. After I installed the SDK on my Bootcamp Windows 7 Home (on a Macbook), I copied my rom to the platform-tools folder and renamed it something shorter.
7. Then I opened command prompt and used it to pushed the rom file to the root of the internal sd (followed gaz instructions above)
8. Once completed, I re-opened recovery and reflashed. Fixed.
I just want my PC to recognize my phone.. Once that happens, i think I'll be in good business... The list of devices attached is none...

[Root] Root and TWRP for R

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.

[Q] Can't Load OS via USB otg or computer, stuck in TWRP.

Ok so I screwed up.
I'm not a developer but i'm familiar with most of the basics. So my m7 was rooted with android revolution 81.0. I was having unrelated problems with calls and also some other small things like a lock screen delay. I decided I was gonna do a system wipe (which I've done plenty of times before with no problems) but this time I forgot to put the OS on the sd card before the wipe. As of now my phone turns on but stays on the HTC screen unless I force it into bootloader and I can also get into TWRP still. I also noticed I wiped the sd card as well by accident so everything is gone. I tried loading the OS via USB OTG but when i go to mount OTG in TWRP I can't select "USB-OTG".I can only select "system" "cache" and "data" I also tried mounting the phone via the computer but it doesn't show up but it does come up on device manager with a yellow exclamation sign next to it. I've heard you can do something with the ADB Sideload but I have no idea how to do that so if that's the answer please explain in detail.
If someone can get it to where I can mount the OTG then I can handle it from there.
Just some details:
S-on
TWRP version 2.6.3.2
I think i've wiped everyting there is to wipe trying to fix this, (
I've been without a phone for a week now and I'm desperate for any kind of fix. I'd greatly appreciate if someone could steer me in the right direction.
Aceboog33 said:
Ok so I screwed up.
I'm not a developer but i'm familiar with most of the basics. So my m7 was rooted with android revolution 81.0. I was having unrelated problems with calls and also some other small things like a lock screen delay. I decided I was gonna do a system wipe (which I've done plenty of times before with no problems) but this time I forgot to put the OS on the sd card before the wipe. As of now my phone turns on but stays on the HTC screen unless I force it into bootloader and I can also get into TWRP still. I also noticed I wiped the sd card as well by accident so everything is gone. I tried loading the OS via USB OTG but when i go to mount OTG in TWRP I can't select "USB-OTG".I can only select "system" "cache" and "data" I also tried mounting the phone via the computer but it doesn't show up but it does come up on device manager with a yellow exclamation sign next to it. I've heard you can do something with the ADB Sideload but I have no idea how to do that so if that's the answer please explain in detail.
If someone can get it to where I can mount the OTG then I can handle it from there.
Just some details:
S-on
TWRP version 2.6.3.2
I think i've wiped everyting there is to wipe trying to fix this, (
I've been without a phone for a week now and I'm desperate for any kind of fix. I'd greatly appreciate if someone could steer me in the right direction.
Click to expand...
Click to collapse
first thing is first, you need to sort out your driver, so when you see "one " with the yellow exclamation mark in your device manager, right click on it and select update driver, select the 2nd option, browse for driver software, again select the 2nd option which is something like let me choose the driver, it may give you a list after that of the type of device connected, select android devices, then select your latest myHTC driver from the list, it will give you some warning about it may not be the correct driver, are you sure you want to install, select yes.
Next, do you know how to use adb and fastboot ?
Seanie280672 said:
first thing is first, you need to sort out your driver, so when you see "one " with the yellow exclamation mark in your device manager, right click on it and select update driver, select the 2nd option, browse for driver software, again select the 2nd option which is something like let me choose the driver, it may give you a list after that of the type of device connected, select android devices, then select your latest myHTC driver from the list, it will give you some warning about it may not be the correct driver, are you sure you want to install, select yes.
Next, do you know how to use adb and fastboot ?
Click to expand...
Click to collapse
I know it involves the command terminal but no, I've never used it before.
Aceboog33 said:
I know it involves the command terminal but no, I've never used it before.
Click to expand...
Click to collapse
still need help?
madboy_maduka said:
still need help?
Click to expand...
Click to collapse
yes yes i dooo
Aceboog33 said:
yes yes i dooo
Click to expand...
Click to collapse
Sorry I had to leave for work, what you need is adb and fastboot files, so download this link and extract it to your desktop https://www.androidfilehost.com/?fid=23329332407580571
Then download either twrp 2.6.3.3 or 2.6.3.4 from the twrp recovery web site, when it's downloaded, rename it to recovery.img for ease and place it in the same folder as adb and fastboot.
You will then need to open a command Windows within that folder by holding control, shift and right mouse click on any white area within that folder, select open command window here.
Make sure your phone is plugged into the computer, and in the bootloader with fastboot usb showing on the screen.
At this point your drivers must be working as per my other post, then issue the following commands one at a time.
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Now enter recovery, your usb otg cable should work now for flashing a Rom, be sure to do a full wipe before flashing, your current recovery sounds too old to me for usb otg support.
---------- Post added at 11:09 AM ---------- Previous post was at 11:00 AM ----------
If your still having problems with usb otg cable at this point, take the Rom which you want to flash and again place it in the same folder on your desktop as adb and fastboot, rename it to Rom.zip for ease, put your phone into recovery and then plug it into the computer, with recovery main screen showing on the phone, once again open a command window on your computer from within the adb and fastboot folder and issue the following command
adb push Rom.zip /sdcard/
Takes about 5 mins and will look unresponsive but it will let you know when it's done, unplug your phone when done, wipe and install.
Seanie280672 said:
Sorry I had to leave for work, what you need is adb and fastboot files, so download this link and extract it to your desktop https://www.androidfilehost.com/?fid=23329332407580571
Then download either twrp 2.6.3.3 or 2.6.3.4 from the twrp recovery web site, when it's downloaded, rename it to recovery.img for ease and place it in the same folder as adb and fastboot.
You will then need to open a command Windows within that folder by holding control, shift and right mouse click on any white area within that folder, select open command window here.
Make sure your phone is plugged into the computer, and in the bootloader with fastboot usb showing on the screen.
At this point your drivers must be working as per my other post, then issue the following commands one at a time.
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Now enter recovery, your usb otg cable should work now for flashing a Rom, be sure to do a full wipe before flashing, your current recovery sounds too old to me for usb otg support.
---------- Post added at 11:09 AM ---------- Previous post was at 11:00 AM ----------
If your still having problems with usb otg cable at this point, take the Rom which you want to flash and again place it in the same folder on your desktop as adb and fastboot, rename it to Rom.zip for ease, put your phone into recovery and then plug it into the computer, with recovery main screen showing on the phone, once again open a command window on your computer from within the adb and fastboot folder and issue the following command
adb push Rom.zip /sdcard/
Takes about 5 mins and will look unresponsive but it will let you know when it's done, unplug your phone when done, wipe and install.
Click to expand...
Click to collapse
What the guy above me said was right, the problem I think with your phone is drivers I'll upload a link to adv drivers in my next post, basically using recovery (twrp recommend) wipe /data, /cache & /system. Then go to adb sideload which is in the recovery (it should say something like adb server started). Then using adb devices command check if your computer sees your device if not you gotta install drivers for your computer. In device manager on your computer your device should be something like ADB interface if not drivers are not correctly installed. Right click update drivers I'll link it in ma next post
---------- Post added at 10:30 PM ---------- Previous post was at 10:26 PM ----------
Follow these instructions to install the driver http://visualgdb.com/tutorials/android/usbdebug/manualinstall.php
Aceboog33 said:
yes yes i dooo
Click to expand...
Click to collapse
Use this guide. Saved me one time
http://android-revolution-hd.blogspot.ro/2013/12/how-to-copy-rom-zip.html?m=1

[Q] Erased Userdata how to push rom to phone

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?

Categories

Resources