Hi, guys I followed all instructions after bricking my phone, it only goes into twrp recovery, i don't have an os and i cant put the rom in device via usb since it wont recognize it, But I tried to push the rom via adb and using terminal like this:
/Users/BARKIN/desktop/Android/adb push slimbean.zip /sdcard/
etc, but it wont work, i try listing devices, it says no device found..
I USE a mac btw, help me out?
Since you have twrp find adb sideload and do it that way. If you need more info Google adb side load twrp.
Sent from my Nexus 7 using XDA Premium HD app
well, I have no file on the phone, i wiped system and everything only recovery is in place.. i cant push rom through adb on mac.
there is hasoons tool which you can make use off. there are actually two out there.. in orignal android section. find the one with mac support.
There is no mac toolkit
barkmarkin said:
well, I have no file on the phone, i wiped system and everything only recovery is in place.. i cant push rom through adb on mac.
Click to expand...
Click to collapse
With adb sideload it does not matter it will work as long as you can use adb commands
Sent from my HTC One using xda premium
So, step by step:
-Boot phone into TWRP
-Select Advanced, then ADB Sideload, swipe to start it
-Connect USB to Mac
-Launch command prompt on Mac
-"adb devices" should detect the phone.
-"adb sideload slimbean.zip" should flash the zip
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.
My device is Moto X (XT1060). I wiped my Internal storage, Cache, Data, System entirely.
I went to my TWRP v2.6.3.1 recovery and tried to sideload cm12.zip via adb.exe but it failed to recognize the device.
I tried
Code:
adb sideload cmfile.zip
but it show's
Code:
error: device not found
I installed Motorola Device manager.. but no luck so far.
I think I need drivers or something for XT1060.. Please help me.
You should search for twrp 2.8.4.0 for Moto X 2013. Also, make sure you have the latest android SDK and ADB files installed. You'll need to search for threads that help get your phone connected to a pc.
Or you could use 'adb push cm12.zip /sdcard' (without the apostrophes) in a cmd prompt then flash in recovery. Why does everyone resort to sideloading when there's any easier method that will always work?
Once you get your Android SDK and drivers set up and storage mounted in recovery.
nhizzat said:
Or you could use 'adb push cm12.zip /sdcard' (without the apostrophes) in a cmd prompt then flash in recovery. Why does everyone resort to sideloading when there's any easier method that will always work?
Once you get your Android SDK and drivers set up and storage mounted in recovery.
Click to expand...
Click to collapse
or you can boot your phone into bootloader if you can and flash the device back to stock and start over.
nhizzat said:
Or you could use 'adb push cm12.zip /sdcard' (without the apostrophes) in a cmd prompt then flash in recovery. Why does everyone resort to sideloading when there's any easier method that will always work?
Once you get your Android SDK and drivers set up and storage mounted in recovery.
Click to expand...
Click to collapse
That is basically all the sideload command does isn't it? I seemed to notice when I side loaded I was left with the zip I installed on my device... I could swear I deleted it manually, which would mean that sideload just pushes and installs for you in once nice package.
Either way, the issue he is having is that ADB won't find his devices... read the error message its not having trouble with the sideload or the zip... He just doesn't know how to use ADB and make it recognize his device...
Pushing doesn't always work when ADB doesn't recognize your device....
Adb and fastboot don't recognize phone. I've made sure I installed the correct jre and the SDK is installed at the latest version with the addons needed for it.
Am I missing something?
how about the nexus 6 or adb driver? is it installed? computer wont see your phone without it.
I figured it out. I had to uninstall the adb driver then install it manually pointing it towards the adb folder. Thanks though!
I have had a very eventful few hours and I'll do my best to explain. Earlier this morning I was rooted, twrp installed and running FreedomOS. I had this bright idea of flashing a file I had downloaded from the OP3T website. It was a firmware file (either the first option, the option before OB5). Everything was running smoothly until I got home and tried using fastboot at which point it just sticks on waiting for device. All normal options are checked (adb files installed, debugging selected, the works), but now I can not use fastboot what so ever. I did at one point sideload an OTA using adb sideload (filename.zip). I have tried just about every adb option I can think of to include: 15 second ADB and minimal adb and fastboot. I even deleted the OP3T drivers from my computer, reinstalled those drivers. I followed an article through technobuzz: http://www.technobuzz.net/download-oneplus-3-usb-drivers/
http://www.technobuzz.net/setup-adb-fastboot-drivers-for-nexus-oneplus-samsung-or-any-android/
I have been using adb and fastboot with no issues up til Open Beta 5 and now my PC and another PC is giving me crap and it's iritating the %%%k out of me.
adb reboot recovery works, adb devices work - showing that the device is connected. I checked the device manager and only found the portable devices. It's like my computer somehow magically deleted the adb driver and will not allow me to install an adb driver. I have no logs to check out....15 second adb was suppose to place a log file on the desktop, but it doesnt....it wont install
Here's what Im on:
OB5 (7.1.1) with stock recovery. I can not use fastboot commands. Here are some pics
http://imgur.com/a/y7iFE
http://imgur.com/a/SVVMg You should see something that says, "Android Device or ADB", but nothing - just MTP
http://imgur.com/a/62msw
I'm using windows 10, device signature is off
Essentially I just want to be able to fastboot flash TWRP and gain root.
Has anyone else experienced any kind of issues with OB5 and adb/fastboot
Btw I had the entire Android SDK installed on another computer and that did not work either....Any assistance would be greatly appreciated. I'm talking about you @redpoint73, lol
Oh boy, I've been summoned! I have to say, I'm not anywhere near knowledgeable yet with the 3T as I was with my past devices. But I'll try.
I assume you are properly trying fastboot commands while in fastboot mode (not in OS or recovery)? I assume so, since you already said it worked fine before the update. But it never hurts to ask the obvious, as a lot of folks forget that adb and fastboot work a bit differently (fastboot only in fastboot mode, adb only in OS or recovery - debugging only needed for adb, not fastboot).
Do you have the OP3T drivers installed? These are the files that Windows always opens whenever I connect the phone (while booted into phone OS), select File Transfer, and it gives the option to open the folder. Although I don't think you even need the drivers for fastboot to work. I unlocked the bootloader and flashed TWRP before I ever installed the OnePlus drivers. The generic fastboot drivers worked fine. But it's worth a try, to install the OP drivers.
I don't even know where to begin or how to reply to what you just said @redpoint73. I haven't attempted to use adb/fastboot commands since yesterday, so i have no idea as to rather it will work or not. If you have teamviewer, I can give your access to a backdoor to show you as it's easier to show then explain. Have you ever noticed when you download a zip from here: http://downloads.oneplus.net/devices/oneplus-3t/#title-section
it never saves the file as Open Beta 3, 4, or etc. It saves the file as this long-named file.zip rather than being something easy to understand. Im able to understand it now, but a few moments ago I wasnt. I "have" downloaded the OP3T drivers on multiple occasions with no success to to fastboot only adb. My computer recognizes the device though. When I go into device manager checking things out. I will have an option that says, "portable devices". when you select that option you'll go across through some contextual menus where you wind up seeing MTP. You should see MTP if you successfully installed the OP3T devices, but at the same time you should be able to see an option that says something along the lines of ADB or Android Debug Bridge, vice versa. My computer does not say that and I have no idea where to go from here. I have no logs or anything helping me out, so it's like finding a needle in the haystack. I do know that I have all of the prereq's such as debugging selected from developers options within the phone, device signature turned off through Windows, adb/fastboot installed, OP3T drivers installed - you know the works you usually need in order to get everything working right. What I might end up doing is just reformatting my entire laptop, installing a fresh copy of windows, fresh copy of adb/fastboot and going from there. My bootloader is unlocked and has been since I've owned the device. As of right now I'm on OB5 with stock recovery. Yesterday I tried three times to sideload one of the downloads from this site: http://downloads.oneplus.net/devices/oneplus-3t/#title-section
. However, my phone would end up saying, "installation failed" when Im in sideload mode. I'm thinking that might have something to do with a botched download from the OP3T server.
Looks like you found your solution here: https://forum.xda-developers.com/showpost.php?p=72046709&postcount=20
Fastboot/adb is usually as simple as reinstalling drivers, etc. as opposed to reformat the PC as you were considering. Reinstalling adb/fastboot was a good idea also, as I don't think I would have thought of that (although it makes perfect sense). So good job working it out!