hi
first i most apologize for my bad english
i got a htc tattoo and i tried to upgrade it's rom to one of cyanogen's rom.
it has android 1.6 (original rom)
first i must root the device (by the instruction of the cyanogen team in their wiki)
i do some steps and near the end i dont know what happend ( i was coping the commands of adb to cmd)
then it completed or not i pluged out phone
after that each time i connct the usb to phone it just charge and no connecting to pc (i have windows 7)
i dont know what to do and i need to upgrade the rom
if someone knows what i must do tell me please
i am so new in android and i dont know nearly anything
tnx for ur help
i must also add this
on the starting of pc (turning on) if the phone is connected i see the options for htc sync and removable storage ... but after loading windows it goes away and the phone just charges;
i tried one another pc but ther was no connecting
Turn on Mass storage
george.baskharon said:
Turn on Mass storage
Click to expand...
Click to collapse
i did this but not working
i even did hard reset to phone
Hi AEZ_BEST,
if i have understood well you actually have a stock rom (may be rooted) and htc_sync package installed on pc.
OK, trying this:
go there http://forum.xda-developers.com/showthread.php?t=950759 and download new version of 1-click root for tattoo (which occasionally you can use to easily root tattoo and install CWM recovery):
decompress dowloaded package into c:\rtatto folder
set tattoo to use ADB (android debug bridge) instead of mounting as a removable drive, it's possible but i not remember where the option is (sorry but two years and half that i not have stock rom installed ) and connect tattoo to pc [maybe it ask for ABD when you connect]
open cmd as administrator and issue these two commands
Code:
cd c:\rtatto
adb devices
it should reports you the list of attached devices
if your tattoo is in the list you can lately use adb to push the rom you wanna flash on sdcard.
Ops, i don't know if you have yet installed CWM recovery, if not look here: http://forum.xda-developers.com/showpost.php?p=27174485&postcount=129
bye
yen
_yen_ said:
Hi AEZ_BEST,
if i have understood well you actually have a stock rom (may be rooted) and htc_sync package installed on pc.
OK, trying this:
go there http://forum.xda-developers.com/showthread.php?t=950759 and download new version of 1-click root for tattoo (which occasionally you can use to easily root tattoo and install CWM recovery):
decompress dowloaded package into c:\rtatto folder
set tattoo to use ADB (android debug bridge) instead of mounting as a removable drive, it's possible but i not remember where the option is (sorry but two years and half that i not have stock rom installed ) and connect tattoo to pc [maybe it ask for ABD when you connect]
open cmd as administrator and issue these two commands
Code:
cd c:\rtatto
adb devices
it should reports you the list of attached devices
if your tattoo is in the list you can lately use adb to push the rom you wanna flash on sdcard.
Ops, i don't know if you have yet installed CWM recovery, if not look here: http://forum.xda-developers.com/showpost.php?p=27174485&postcount=129
bye
yen
Click to expand...
Click to collapse
every time i type adb devices in cm i dont get anything. the list is empty. no device attached it says.
and
the adb debgging mode is on.
if i have my phone connected then i can use ur typic (1 click root...)
so iwant to connect my phone first.
plz help
Change your USB cable
Hi AEZ_BEST;
one more try on another PC installing these usb drivers; http://goo.im/tools/drivers/USB_driver_20101122_release.zip
and trying with adb as in my praevious post (btw, when connecting to pc no notification message on tatto at all?)
Edit:
as kemoba say try also with another usb cable, standard mini usb cableshould work too
bye
yen
hi all.
i tried in 2 other pc s . but same resul
finally i reinstalled my windows seven!
then it worked
tnx to all of u
AEZ_BEST said:
hi all.
i tried in 2 other pc s . but same resul
finally i reinstalled my windows seven!
then it worked
tnx to all of u
Click to expand...
Click to collapse
Next time use Ubuntu then
but i use Windows 7 too..never had the problem!
Look on Google play for a 3rd party USB mounter / connecter
Sent from my Desire HD using xda app-developers app
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.
Hey guys
I did a terrible mistake. Instead of just normally resetting the phone to factory settings in CWM after unlocking it, my finger slipped to the "format /system" option.
This happened before, but then I just sideloaded the rom and everything was ok. Oddly enough, this doesnt work anymore.
Whenever I want to push something to my phone using adb, I get the error that the device was not found and I cannot do anything to access the phone (when entering the command "adb devices" for example, no device shows up). I installed every driver I can think of, I installed all the packages in the sdk manager and now I dont know what to do.
I know that the debug mode is required, but since theres no OS anymore, I really ran out of ideas.
Please help me! :crying:
PS: additional information:
- HTC One m7 (unlocked)
- Clockwerkmod Recovery
- Windows 8
- Hasoon2000's all in one kit
EDIT: I found this site that recommends flashing via fastboot. (blog.syedgakbar.com/2013/02/01/android-installing-system-images-using-flashboot/)
where do I find these images?
I rooted my HTC one after downloading a custom Rom it left me in a bootloop I tried adb sideload from twrp but my pc doesnt detect my device. I do have adb drivers installed. also tried the fastboot option also doesn't detect my phone. Pls help
If you can boot into TWRP, try to mount your internal storage as MTP (see here for a description). You could then load a different ROM onto the phone and then flash it.
To get fastboot to work, download the latest HTC Sync program, install it, but then uninstall it leaving the drivers. When you boot your phone into fastboot and plug it in, it should switch from "fastboot" in red to "fastboot usb" and hopefully it will then be recognized.
maybe he needs to flash the boot.img, if he's s-on, just my 2 cents
shooter7201 said:
I rooted my HTC one after downloading a custom Rom it left me in a bootloop I tried adb sideload from twrp but my pc doesnt detect my device. I do have adb drivers installed. also tried the fastboot option also doesn't detect my phone. Pls help
Click to expand...
Click to collapse
What rom are you trying to flash? If it's not from the Sprint forum it's most likely a GSM rom and does not have Sprint support.
That will cause your phone to react like you are talking about.
ADB Sideload 99 time out of 100 will not work.
Use adb push FileName.zip /sdcard/ to move files to your phone while in recovery.
As for the drivers try this:
On your PC go to device manager and find your phone(usually M7WLS), right click and select properties
Select the driver tab
Select update driver
Select browse my comp
Let me pick
Look for ADB USB device or similar should be one of the first couple choices
Select MyHTC install and you should be good