Soft brick Htc one m7 - One (M7) Q&A, Help & Troubleshooting

Hello guys i need help regarding my htc one m7.
I tried to go back to stock rom with a HTC ONE m7 fw 1.29.401.12 and did not know that ruu version have to match exactly the fw version since i have s-on.
I locked the bootloader and therefore all data were deleted on my phone so all my backups and cyanogenmod installation files.
My bootloader still works this goes also for twrp.
I researched for hours and found a solution with adb sideload but i am just not able to properly transfer the file.
I have htc sync installed and also sdk tools adb etc.
When i go into recovery and open cmd command in platform tools and type "adb devices " i get this : List of devices attached
name of device device
so everything is good till now.
Now i go to twrp and put the one into adb sideload then i get the following result when i type adb devices :
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
name of the device sideload
So this is my problem guys i need to transfer the file but i dont know what is causing the problem would be awesome if you can help somehow.
Have a nice weekend all!

See Question (2 in this faq post to fix your drivers http://forum.xda-developers.com/showthread.php?p=52135024 :good:

ioakimakos93 said:
Hello guys i need help regarding my htc one m7.
I tried to go back to stock rom with a HTC ONE m7 fw 1.29.401.12 and did not know that ruu version have to match exactly the fw version since i have s-on.
I locked the bootloader and therefore all data were deleted on my phone so all my backups and cyanogenmod installation files.
My bootloader still works this goes also for twrp.
I researched for hours and found a solution with adb sideload but i am just not able to properly transfer the file.
I have htc sync installed and also sdk tools adb etc.
When i go into recovery and open cmd command in platform tools and type "adb devices " i get this : List of devices attached
name of device device
so everything is good till now.
Now i go to twrp and put the one into adb sideload then i get the following result when i type adb devices :
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
name of the device sideload
So this is my problem guys i need to transfer the file but i dont know what is causing the problem would be awesome if you can help somehow.
Have a nice weekend all!
Click to expand...
Click to collapse
Danny201281 said:
See Question (2 in this faq post to fix your drivers http://forum.xda-developers.com/showthread.php?p=52135024 :good:
Click to expand...
Click to collapse
Ok I read your post again and think I misunderstood your problem. Your drivers are working as adb see's the device so what exactly is the problem? The sideload does not complete?
You should uninstall HTC Sync for starters it will do you no favours while using adb/fastboot commands it has the potential to cause hangs. if
Code:
adb sideload name-of-zip
is not working for you.
Try adb push instead with the one on the TWRP home screen (Not in Sideload mode)
Code:
adb push name-of-zip.zip /sdcard
The command window will appear unresponsive until the push completes. (several minutes) When it's done select Install from the TWRP menu and select the rom zip file.
If you still get problems copy and paste the error from your command window here :good:
Or flash TWRP 2.8.5.0 it has the ability to use MTP in recovery so you can see your phones Internal Storage while in recovery and just drag and drop the rom to your phone :good:

Related

[Q] adb returning "error: closed"

Hi,
I'm currently trying to use adb to push some data into my phone but i always get "error: closed". I'm using windows 7 x64 and im running it from cmd.
Almost everything i tried using adb (push, shell, remount) returns this. I've searched over the forums and tried "adb devices" as well to see if my phone is connected, but what is different from the others is i am getting
List of devices attached
XXXXXX host
instead of what most other people got
List of devices attached
XXXXXX device
Is this a problem? What am i missing? Thanks a lot for ur time in reading this
Try:
Code:
adb usb
then
Code:
adb devices
or
Code:
adb kill-server
then
Code:
adb start-server
then
Code:
adb devices
Guich said:
Try:
Code:
adb usb
then
Code:
adb devices
or
Code:
adb kill-server
then
Code:
adb start-server
then
Code:
adb devices
Click to expand...
Click to collapse
Thank you! Although after doing these commands it still returned error:closed it listed my device as being in sideload mode so all sideload commands worked after that including sideloading a rom .zip
Did you update the SDK Manager??? Try updating that, my ADB problem were gone after i updated them.....
xlxcrossing said:
Thank you! Although after doing these commands it still returned error:closed it listed my device as being in sideload mode so all sideload commands worked after that including sideloading a rom .zip
Click to expand...
Click to collapse
I've got the same situation with "error closed" message. I ran the suggestions above but am still getting the error message.... Thoughts?
jflora1 said:
I've got the same situation with "error closed" message. I ran the suggestions above but am still getting the error message.... Thoughts?
Click to expand...
Click to collapse
Try to download this, un-zip and try the tips with this
Guich said:
Try to download this, un-zip and try the tips with this
Click to expand...
Click to collapse
I downloaded the zip but haven't had any success, still getting an error:closed message
ozo012 said:
I downloaded the zip but haven't had any success, still getting an error:closed message
Click to expand...
Click to collapse
which recovery are you on? (name and version number please)
nkk71 said:
which recovery are you on? (name and version number please)
Click to expand...
Click to collapse
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
ozo012 said:
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
Click to expand...
Click to collapse
isnt "error closed" something to do with out of date adb?
ozo012 said:
This is actually the only place I've found that might have had a solution to my problem (different device: Nexus 7, Stock 4.3 JWR66Y, unrooted, I'm attempting to sideload the 4.4 update but continually get this error:closed message.
Click to expand...
Click to collapse
Some people had solved the issue with the command:
Code:
adb usb
and after a reboot of device.
But seems don't work for all.
nkk71 said:
isnt "error closed" something to do with out of date adb?
Click to expand...
Click to collapse
Umh, no, i don' think
Guich said:
Some people had solved the issue with the command:
Code:
adb usb
and after a reboot of device.
But seems don't work for all.
Umh, no, i don' think
Click to expand...
Click to collapse
I haven't tried rebooting the device seems to be the only thing I left out.
I was having the same problems. Couldn't sideload. When I would run "adb devices" , my device would be listed. If I ran "adb usb" I would get "error: closed" . The sideload command would just bring up a list of commands. This may help someone, I installed a new version of adb. Not sure if I can post links but the file name was adb-setup-1.1.exe. This installs the needed files, the installer didn't notify me where the files were installed but they installed right to my C:\ drive. This seemed to eliminate the problem for me. I did a lot of searching and couldn't find anyone with this specific issue, so if anyone finds themselves with this problem give this a try.
worked for me
i had the same problem
i coulnt send anyfile to my htc one but after updating plate-form tools and replacing the old adb and fastboot files with the new ones
i entered the commend adb sideload rom.zip and it started sending the rom
and the phone was on twrp recovery-advanced-sideload
morheb said:
i had the same problem
i coulnt send anyfile to my htc one but after updating plate-form tools and replacing the old adb and fastboot files with the new ones
i entered the commend adb sideload rom.zip and it started sending the rom
and the phone was on twrp recovery-advanced-sideload
Click to expand...
Click to collapse
Yay. That Just worked for me using Crunchbang Debian. Thanks morheb that little tweak of using 'sideload' was the key
Can anyone help me push vold.fstab file with adb?
Stock Recovery on mediatek platform. with adb i got same error as this thread. Error:closed
KoolAidBigMan said:
I was having the same problems. Couldn't sideload. When I would run "adb devices" , my device would be listed. If I ran "adb usb" I would get "error: closed" . The sideload command would just bring up a list of commands. This may help someone, I installed a new version of adb. Not sure if I can post links but the file name was adb-setup-1.1.exe. This installs the needed files, the installer didn't notify me where the files were installed but they installed right to my C:\ drive. This seemed to eliminate the problem for me. I did a lot of searching and couldn't find anyone with this specific issue, so if anyone finds themselves with this problem give this a try.
Click to expand...
Click to collapse
Perfect - worked for me - exact same issue - adb wasnt recognising my phone was in sideload and sideload command wouldnt work but push would - plus getting error closed message on adb usb command. Googled the above adb file, downloaded, 15 second install and now sideloading is working on my SG2 with CWM recovery 6.0.2.9 (kitkat). I was obviously using an outdated ADB driver (1.0.29).
Thanks a lot KoolAidBigMan !! Big up...
Jimbo
EDIT : Spoke too soon - now getting another error when trying to sideload.. will google it.. failed to write data 'protocol fault (no status)'
EDIT : Sorted. Ended up getting round it by pushing the files instead - found instructions on Cyanogenmod forums. Thanks once again.
http://forum.xda-developers.com/sho...wQFjAA&usg=AFQjCNGgPmMne0aYCd9RojZZhy89cQjnCw
Try this
Sent from my C6916 using XDA Free mobile app
Link not working?? Im ok now anyway.. Time to test my screen casting to my Chromecast.. :fingers-crossed:
mtk6572 have same error
I have same error.. but I know that my phone's usb debugging is not enable.. so I got this error:close..
My phone is on bootloop so I can't enable the usb debugging.. Is there any way to enable the usb debugging using adb commands? I trying to push the framework-res.apk on my phone.. because it is the cause of the bootloop.
i'm a nood

[Q] Device not found on ADB | TWRP Sideload and CWM mount problems

My friend has HTC One. He wiped all the data on SD including the ROM files and One is not booting right now. It's rooted and has Trickdroid's 4.2.2 based ROM.
We tried lots of things so far;
- Pushing files via ADB
Trying ADB, it says device not found, no matter we did we couldn't manage the pc to recognize the phone.
- Mounting SD via CWM
I have HOX, when I enter CWM I can see the option to mount the SD but on One there's no line like this.
- Activating Sideload on TWRP
We also flashed TWRP and tried to use Sideload feature but when we tried to activate it, it says something like "unable to mount .."
- Flashing the RUU
And lastly we tried to flash the RUU, we checked the CID and it says o2___001 and there's no RUU for it.
I just saw that One could be S-OFF and got Super-CID, but to do that again, I have to pull and push some files via ADB so we stuck here.
Could you plese help me on this?
Try cwm recovery it has sideload feature I was in a similar situation once before and it worked using cwm recovery
Also. If you want to try use adb again, try to plug in your device and then wait for few seconds before running a push command. It worth mentioning that once adb fail one time, it is not going to work again by repeating the same push command. Once it fails run this command: adb kill-server
This command will stop the previous failed process after killing the server then try to push again
NiMH_999 said:
Try cwm recovery it has sideload feature I was in a similar situation once before and it worked using cwm recovery
Also. If you want to try use adb again, try to plug in your device and then wait for few seconds before running a push command. It worth mentioning that once adb fail one time, it is not going to work again by repeating the same push command. Once it fails run this command: adb kill-server
This command will stop the previous failed process after killing the server then try to push again
Click to expand...
Click to collapse
We tried a different computer and solved the ADB problem, then I did just like you told and it's OK now.
Thank you.
You're welcome. glad it's all all OK for you
Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.
Same problem as you --> fixed
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
If you found that adb worked from a different machine, you might check whether you had any tethering drivers installed (eg EasyTether) on the machine that was not able to see the phone via adb. I found that they interfered with adb's operation on my Macbook previously; it was maddening.
woraz said:
My friend has HTC One. He wiped all the data on SD including the ROM files and One is not booting right now. It's rooted and has Trickdroid's 4.2.2 based ROM.
We tried lots of things so far;
- Pushing files via ADB
Trying ADB, it says device not found, no matter we did we couldn't manage the pc to recognize the phone.
- Mounting SD via CWM
I have HOX, when I enter CWM I can see the option to mount the SD but on One there's no line like this.
- Activating Sideload on TWRP
We also flashed TWRP and tried to use Sideload feature but when we tried to activate it, it says something like "unable to mount .."
- Flashing the RUU
And lastly we tried to flash the RUU, we checked the CID and it says o2___001 and there's no RUU for it.
I just saw that One could be S-OFF and got Super-CID, but to do that again, I have to pull and push some files via ADB so we stuck here.
Could you plese help me on this?
Click to expand...
Click to collapse
if you have problems always use Hasoon All-In-One_Kit for HTC
Am having the same issues, have tried everything I can think off and everything google has suggested. I'm beyond stuck any and all help would be greatly appreciated
my bad exp
I don't know if that help anyone but I had the problem "device not found" when I was trying to side load with HTC AIO KIT.
I removed all my drivers for htc from the control panel and installed only the htc driver (binary100100.googlecode.[com]/files/HTCDriver3.0.0.007.exe). Then the adb started to work. (after the htc drivers install you need to restart your OS)
When I installed new ROM and reboot the device it showed me the screen with the developer's rom. I thought that I failed and flashed new rom then suddenly the new ROM after one minute started to work. So looks like that I should wait long enough for the first and may be it would also starts to work.
Was he by chance having issues charging his phone before he wiped it?
Myself and my brother both a had issues with the USB port going. Couldn't charge while phone was on. PC wouldn't pick it up so no adb. However was able to pickup fastboot and charge while in fastboot mode.
If that's the case you could try running a zip in oemRUU mode just to get an os on there.
Is he soff?
Sent from my HTC One using xda premium
makkasi said:
I don't know if that help anyone but I had the problem "device not found" when I was trying to side load with HTC AIO KIT.
I removed all my drivers for htc from the control panel and installed only the htc driver (binary100100.googlecode.[com]/files/HTCDriver3.0.0.007.exe). Then the adb started to work. (after the htc drivers install you need to restart your OS)
When I installed new ROM and reboot the device it showed me the screen with the developer's rom. I thought that I failed and flashed new rom then suddenly the new ROM after one minute started to work. So looks like that I should wait long enough for the first and may be it would also starts to work.
Click to expand...
Click to collapse
This worked for me. Thanks!!
Once I removed all the extra crap from control panel and used the latest I was able to do adb devices successfully from bootloader / recovery.
I was just having the same problem on the new LG G2 (D803). It was perplexing because the computer *bleeped* every time it attached so I knew that it saw something. Based on the tips here I went to the Device Manager and sure enough there it was... I reinstalled the drivers inside device manager and then I got an easy adb hit on the phone... hmmm :fingers-crossed:
EazyVG said:
Boot TWRP, then select “Mount”, then select only “Data” and connect your HTC One to your computer.
Considering you have adb.exe (Windows, part of fastboot.zip) or on Linux:
cd Downloads\ROM.zip
adb push ROM.zip /sdcard/
Replace ROM.zip with the ROM filename you copied earlier to Downloads (or any other) folder, then install the ROM.
It should be nearly same running CWM recovery. Hope that helps.
Click to expand...
Click to collapse
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
This worked for my Nexus 4 and TWRP installed. Running the ADB sideload commad from TWRP did not, and just trying to push or sideload from command prompt on PC (Win 8) did not. I had drivers for Nexus 4 recognition installed previously from Nexus Root Toolkit which worked when the Nexus 4 was booted into system, but did not recognize it when wiped and/or in recovery mode. Loading these drivers the Nexus 4 was recognized in recovery mode, and I was able to push the ROM and install using TWRP.
Thanks much!
:good:
timekills said:
This worked for my Nexus 4 and TWRP installed. Running the ADB sideload commad from TWRP did not, and just trying to push or sideload from command prompt on PC (Win 8) did not. I had drivers for Nexus 4 recognition installed previously from Nexus Root Toolkit which worked when the Nexus 4 was booted into system, but did not recognize it when wiped and/or in recovery mode. Loading these drivers the Nexus 4 was recognized in recovery mode, and I was able to push the ROM and install using TWRP.
Thanks much!
:good:
Click to expand...
Click to collapse
Man, I just wanted to say thank you. I've been stuck on this for hours and this did the trick!
Worked
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
the drivers mentioned here worked for me.
Device : HTC One M7
Recovery : TWRP
Thanks
Thank you so much! This universal driver worked for me! (HTC One Mini with TWRP, soft-bricked)
NiMH_999 said:
Try cwm recovery it has sideload feature I was in a similar situation once before and it worked using cwm recovery
Also. If you want to try use adb again, try to plug in your device and then wait for few seconds before running a push command. It worth mentioning that once adb fail one time, it is not going to work again by repeating the same push command. Once it fails run this command: adb kill-server
This command will stop the previous failed process after killing the server then try to push again
Click to expand...
Click to collapse
Years later, thank you sir, for helping a noob with "adb kill-server"
I was so freaked as to why TWRP wasn't sideloading but PhilZ was.
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
ADB didn't recognize my Xperia SP in Clockworkmod. That driver worked like a charm Thank you!
This worked for me...
flsurf7 said:
I was able to recognize my device in device manager when using fastboot, but wasnt able to recognize the device as soon as I switched to recovery mode.
I found this universal driver which would recognize both: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi
(remove brackets from [.com] above)
I was now able to use adb sideload to transfer the .zip to my sd card and flash my new rom.
Hope this helps anyone else.
Click to expand...
Click to collapse
Thank you so much for this. This really helped me out.

ADB problem and no OS on device

Last night, on TWRP I formated data on the SD card, which is why I have no OS. Now looking for how to fix this on xda/google, I get into the bootloader, have fastboot usb and try to adb shell but I keep getting the "error no device found". I already installed latest drivers from HTC on to my laptop and still nothing. Any other idea?
windows 8?
First off, make sure you have HTC Sync Manager installed because that will give you the proper drivers in order to be able to use ADB commands.
Afterwards, make sure you install Java JDK and Android SDK.
Just follow this tutorial here: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Follow it word for word and make sure you install JDK X86 even if you have a X64 computer. And then download SDK Manager, put it in C:/ drive, open SDK Manager, and download the necessary tools (also all in the tutorial).
I was in the same position as you just before yesterday and I followed this tutorial with success.
skinsfanbdh said:
windows 8?
Click to expand...
Click to collapse
Windows 7, and mac.
Evolancer13 said:
Windows 7, and mac.
Click to expand...
Click to collapse
try downloading all in one toolkit and try that. just make sure to read the onscreen instructions as you go through the process
TarekElsakka said:
First off, make sure you have HTC Sync Manager installed because that will give you the proper drivers in order to be able to use ADB commands.
Afterwards, make sure you install Java JDK and Android SDK.
Just follow this tutorial here: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/
Follow it word for word and make sure you install JDK X86 even if you have a X64 computer. And then download SDK Manager, put it in C:/ drive, open SDK Manager, and download the necessary tools (also all in the tutorial).
I was in the same position as you just before yesterday and I followed this tutorial with success.
Click to expand...
Click to collapse
skinsfanbdh said:
try downloading all in one toolkit and try that. just make sure to read the onscreen instructions as you go through the process
Click to expand...
Click to collapse
I'll look into both things, thanks.
EDIT: even on my mac adb does not see any devices, before when I entered ./adb devices it would show "list of devices:" and it would be blank.
Good luck, man. It's fairly easy once you read the tutorial carefully and follow all the steps to the word. After it's all done and the command prompt says Sideload 100%, boot into TWRP, tap INSTALL and then scroll down to sideload.zip and that's your ROM. Also after copying the desired ROM to platform-tools in the SDK folder, rename it to rom.zip, it seems to work 100% that way while it struggles a bit with long names.
TarekElsakka said:
Good luck, man. It's fairly easy once you read the tutorial carefully and follow all the steps to the word. After it's all done and the command prompt says Sideload 100%, boot into TWRP, tap INSTALL and then scroll down to sideload.zip and that's your ROM. Also after copying the desired ROM to platform-tools in the SDK folder, rename it to rom.zip, it seems to work 100% that way while it struggles a bit with long names.
Click to expand...
Click to collapse
Still getting the error: device not found.
I even ran the all in one tool kit and attempted the "ADB sideload a ROM" follow the steps but get an error on CMD "C:\users\(username) is not recognized as an internal or external command, operable program or batch file"
I really do not understand why adb is not working, I did s-off and supercid myself maybe less than a week ago.
Are you sure you followed all the steps in the tutorial including installing JDK, using SDK Manager to download some tools and such? And are you sure you have the proper drivers installed (e.g HTC Sync Manager)? I used to get that error before I installed it. Go to Device Manager while in ADB mode in TWRP and see if the device is recognized or if there's a yellow sign beside it indicating that there are no drivers for it.
TarekElsakka said:
Are you sure you followed all the steps in the tutorial including installing JDK, using SDK Manager to download some tools and such? And are you sure you have the proper drivers installed (e.g HTC Sync Manager)? I used to get that error before I installed it. Go to Device Manager while in ADB mode in TWRP and see if the device is recognized or if there's a yellow sign beside it indicating that there are no drivers for it.
Click to expand...
Click to collapse
It came up under Android USB Devices as My HTC. When I was following the steps on the link you provided, when I tried to update the drivers with the google usb driver wouldnt work, it would say "windows had determined the driver software for your device is up to date". When I go into My HTC properties says the driver version is 2.0.7.18.
The Google USB drivers did not work for me either, only the ones provided by HTC Sync Manager did. I have not experienced that problem, mate, so I do not know what to do at this point, I am very sorry. If you are not able to fix this, I suggest getting an OTG cable and directly loading the ROM from the PC to your SD card. I ordered one a couple of days ago and it is coming tomorrow, it's very helpful
TarekElsakka said:
The Google USB drivers did not work for me either, only the ones provided by HTC Sync Manager did. I have not experienced that problem, mate, so I do not know what to do at this point, I am very sorry. If you are not able to fix this, I suggest getting an OTG cable and directly loading the ROM from the PC to your SD card. I ordered one a couple of days ago and it is coming tomorrow, it's very helpful
Click to expand...
Click to collapse
Crap, I appreciate your help though.
EDIT: nevermind googled it, gonna pick one up. Phoneless till wednesday
I am sorry to hear that, but I suppose that's the only thing you can do at the moment. Even if somehow get ADB working, do not cancel your order because OTG cables aren't only used for mounting the device, but also for things like connecting gamepads and controllers to play games on your device.
USB 3
If you have USB3 port adb.exe wan't recognize your device.
I triend first on USB3 and after on other older computer on USB2 all was fine
Evolancer13 said:
Last night, on TWRP I formated data on the SD card, which is why I have no OS. Now looking for how to fix this on xda/google, I get into the bootloader, have fastboot usb and try to adb shell but I keep getting the "error no device found". I already installed latest drivers from HTC on to my laptop and still nothing. Any other idea?
Click to expand...
Click to collapse
You can't acces to "adb shell" without OS, there is special mode in adb named "adb sideload" , not shell !
1) Check version adb by "adb version" you need version 1.0.29 or higher
2) Check TWRP version (2.3 or higher) Go to TWRP recovery -> adb sideload
3) Connect PC to phone , at PC in device manager must be MY HTC device.
4) Type jn PC adb sideload /yourpath/yourrom.zip
tash2013 said:
You can't acces to "adb shell" without OS, there is special mode in adb named "adb sideload" , not shell !
1) Check version adb by "adb version" you need version 1.0.29 or higher
2) Check TWRP version (2.3 or higher) Go to TWRP recovery -> adb sideload
3) Connect PC to phone , at PC in device manager must be MY HTC device.
4) Type jn PC adb sideload /yourpath/yourrom.zip
Click to expand...
Click to collapse
check first with "adb devices" to see does your PC recognize your HTC
tash2013 said:
You can't acces to "adb shell" without OS, there is special mode in adb named "adb sideload" , not shell !
1) Check version adb by "adb version" you need version 1.0.29 or higher
2) Check TWRP version (2.3 or higher) Go to TWRP recovery -> adb sideload
3) Connect PC to phone , at PC in device manager must be MY HTC device.
4) Type jn PC adb sideload /yourpath/yourrom.zip
Click to expand...
Click to collapse
Tash2013 YOU ARE AMAZING! Got my One back up running!
Oh man I'm so glad it's working. I thought you already knew that it is sideload not shell lol.
Sent from my HTC One using Tapatalk 4 Beta
TarekElsakka said:
Oh man I'm so glad it's working. I thought you already knew that it is sideload not shell lol.
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
If I knew I would have tried lol, and it no one said anything about sideload but oh well.
Haha! Damn. I am glad it worked out, though.

USB not showing up in cwm recovery

My phone recently lost its ROM, and is now stuck on the 'HTC quietly beautiful screen', i did manage to get it into clock work mode recovery and have a backup of my old rom on a usb, however, when i plug in the USB before starting the phone it doesn't show up, meaning i cannot restore. Please help! Any help or feedback is much appreciated! :good:
When you're in recovery, you have to use the command:
Code:
adb devices
for see your phone.
After use adb command like push or sideload for put a rom into the phone
Guich said:
When you're in recovery, you have to use the command:
Code:
adb devices
for see your phone.
After use adb command like push or sideload for put a rom into the phone
Click to expand...
Click to collapse
Thanks, but how would i do that on a mac?
That's why I have parallels!
I had this problem the other day and I fixed it by going to data/media in recovery and installing an old Rom that was downloaded. I could then restore afterwards.
Sent from the one and only HTC One
Shadow Samurai said:
That's why I have parallels!
I had this problem the other day and I fixed it by going to data/media in recovery and installing an old Rom that was downloaded. I could then restore afterwards.
Sent from the one and only HTC One
Click to expand...
Click to collapse
Yes, but i cannot copy anything to my device, and when i attempt to use adb, it says "error: device not found"
Check the thread in my signature
Sent from my HTC One using xda app-developers app
MacHackz said:
Check the thread in my signature
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
i have tried following your help, but when i type ./adb devices it says
"adb server is out of date. killing...
* daemon started successfully *
List of devices attached
"
it doesn't show the serial code
g4slyness said:
i have tried following your help, but when i type ./adb devices it says
"adb server is out of date. killing...
* daemon started successfully *
List of devices attached
"
it doesn't show the serial code
Click to expand...
Click to collapse
Is it turned on booted into Android, or in recovery?
MacHackz said:
Is it turned on booted into Android, or in recovery?
Click to expand...
Click to collapse
Yes
You have the latest adb binaries installed??
Sent from One with Tapa4 Beta
Guich said:
You have the latest adb binaries installed??
Sent from One with Tapa4 Beta
Click to expand...
Click to collapse
I am not sure what a binary is (HTC One is my first android phone so I'm new) but if it is the recovery mode, i only installed it about a week ago
Do you have the folder containing the adb and fastboot files on your Desktop? And do you have HTC Sync installed? It will load the proper drivers, even though I heard it may not be necessary anyway.
This method worked for me on my Mac. It is very simple using Terminal.
You don't actually have to download the whole SDK, just download the file attached in the threat, which is this http://forum.xda-developers.com/attachment.php?attachmentid=1396782&d=1350078941
Place it on your Desktop, and follow the instructions. After ADB successfully lists your device, move the ROM file to your android folder and use the following command: adb sideload rom.zip of course replacing 'rom.zip' with whatever your rom's name is. You can also use adb push if you want to move your Nandroid backup to your device, but I am not sure where it will be located on the device itself afterwards.
Oh and you should be in TWRP > Advanced > ADB Sideload mode if you want to sideload the ROM. I am not sure how it works on CWM but it should be the same way.
TarekElsakka said:
Do you have the folder containing the adb and fastboot files on your Desktop? And do you have HTC Sync installed? It will load the proper drivers, even though I heard it may not be necessary anyway.
This method worked for me on my Mac. It is very simple using Terminal.
You don't actually have to download the whole SDK, just download the file attached in the threat, which is this http://forum.xda-developers.com/attachment.php?attachmentid=1396782&d=1350078941
Place it on your Desktop, and follow the instructions. After ADB successfully lists your device, move the ROM file to your android folder and use the following command: adb sideload rom.zip of course replacing 'rom.zip' with whatever your rom's name is. You can also use adb push if you want to move your Nandroid backup to your device, but I am not sure where it will be located on the device itself afterwards.
Oh and you should be in TWRP > Advanced > ADB Sideload mode if you want to sideload the ROM. I am not sure how it works on CWM but it should be the same way.
Click to expand...
Click to collapse
Thanks, i have tried this method already and am in Clockworkmod recovery, i don't have TWRP

[Q] HELP! Wiped everything by accident!

I accidentally wiped everything from my HTC One which was previously running Android Revolution HD 31.0. I tried using ADB sideload from TWRP recovery, which is still on my phone, and when typing ADB devices, I do see a random string of numbers with the text ''sideload'' next to it. However, when I try to sideload the rom I get an error: closed or cannot read 'sideload' message. Any ideas? I really need my phone to work..
YoungStarDC said:
I accidentally wiped everything from my HTC One which was previously running Android Revolution HD 31.0. I tried using ADB sideload from TWRP recovery, which is still on my phone, and when typing ADB devices, I do see a random string of numbers with the text ''sideload'' next to it. However, when I try to sideload the rom I get an error: closed or cannot read 'sideload' message. Any ideas? I really need my phone to work..
Click to expand...
Click to collapse
What have you tried..
Assume you have latest drivers and ADB installed fully on PC?
Not sure as I don't use TWRP, but can you mount storage? (if so copy ROM onto sd card via PC)
If you have everything loaded and still no go, is your device s-off?
have you tried "ADB Push" ??
some times this works...when adb sideload fails
"adb push yourrom.zip /data/media/0/"
even this one has to be done from recovery
Harish_Kumar said:
have you tried "ADB Push" ??
some times this works...when adb sideload fails
"adb push yourrom.zip /data/media/0/"
even this one has to be done from recovery
Click to expand...
Click to collapse
flash this recovery and chose side load it will work tested by me. though it takes abt 5min to load 1gb file.
this progress will be showin in your cmd
just place the zip in your adb folder and run
adb push (name of the zip)
http://goo.gl/Q5mfQl

Categories

Resources