Database Develop

need help rooting

trying to root 2.1 sprint hero, had the patched .6 version but redownloaded the .5 version on my phone, now says 2.27.651.5! Good right? Then I'm trying the regaw method for rooting. Downloaded the sdk, downloaded HTC Sync 2.0.33, downloaded hero-root. Renamed them to C:\android-sdk-windows\tools, went to the command prompt and typed it in. Then I type in adb devices and I get an error: adb not recognized as an internal or external command, operable program or batch file. I've checked debugging, and still get same error. Deleted files and redownloaded everything again and STILL get same error. Any help would be much appreciated

make sure you cd to that directory, or you can click-n-drag adb.exe (adb-windows.exe in some cases) into your CMD promt and type your command after... Little work around for odd computer setups
EDIT - you could also try to append the ".exe" at the end, i.e. >adb.exe devices

Thanks, I gave it a try! Still nothing,

Did you run the setup or did you just download, extract, and then run straight to CMD? try running the setup, don't download anything if you don't want to, and then try again.

I must be an idiot, the folder size is 54.2 mb. I'm at a loss. I will continue trying!!!!

Ok, total noob here! I've been at this for a while now and still can not get adb devices to recognize my phone. Device manager says everything working properly, drivers installed properly. I have searched and searched for an answer and still I can"t find one. Is there something I am doing wrong or have I not set up. All I want to do is root my phone, any answers would be a godsend.

[Q] ADB Sideload isn't working for me!

Hello there
I am stuck without a ROM and without a ROM zip file anywhere on the internal device that I can use TWRP to install. The only option I have at the moment is to use adb sideload, and this is my first time doing so.
I downloaded this:
adt-bundle-windows-x86_64-20130522
Anyway, I am trying to follow this tutorial but it's not working out for me:
http://forum.xda-developers.com/showthread.php?t=2317986
It looks simple and easy, but this is the problem I am facing:
"I changed directories to where the adb.exe is (inside platform-tools) and ADB Sideload is already started in TWRP. However, whenever I type "adb devices" it only says "List of attached devices" and nothing under it. Whenever I try flashing the ROM, it says error: device not found. What am I doing wrong here? I even changed the name of the ROM to rom.zip to make it shorter as per a suggestion in the first page of the thread, but that didn't work either."
Can someone please help me and tell me how to make it work? I have been without a ROM for hours waiting for the SDK to download this my internet is pretty slow. Thanks a lot!

Okay now I realize my device isn't actually recognized, although it works fine with fastboot usb.
What do I do? I tried having windows automatically search for drivers but it didn't find anything.

Okay after doing some more reading I realized I never actually opened SDK Manager, and when I try, it just opens a black command prompt window and then shuts down. I then came across this article and realized I need Java JDK drivers before I can actually run SDK Manager and then follow the rest of the tutorial. Maybe that is the problem??

You need HTC drivers , if you didn't install HTC SYNC, open "virtual CD", that appears at connection of phone with PC and you will see folders with drivers for different OS.

Thanks, mate. I already fixed the problem but I forgot to update this thread. You are right, I did not have the proper drivers, so I downloaded and installed HTC Sync Manager and then everything went great.

I had the same problem last night trying to flash my first rom ever, but thankfully i had a usb otg cable that I used to put the rom zip in my flash drive and flash it into the phone

TarekElsakka said:
Hello there
I am stuck without a ROM and without a ROM zip file anywhere on the internal device that I can use TWRP to install. The only option I have at the moment is to use adb sideload, and this is my first time doing so.
I downloaded this:
adt-bundle-windows-x86_64-20130522
Anyway, I am trying to follow this tutorial but it's not working out for me:
http://forum.xda-developers.com/showthread.php?t=2317986
It looks simple and easy, but this is the problem I am facing:
"I changed directories to where the adb.exe is (inside platform-tools) and ADB Sideload is already started in TWRP. However, whenever I type "adb devices" it only says "List of attached devices" and nothing under it. Whenever I try flashing the ROM, it says error: device not found. What am I doing wrong here? I even changed the name of the ROM to rom.zip to make it shorter as per a suggestion in the first page of the thread, but that didn't work either."
Can someone please help me and tell me how to make it work? I have been without a ROM for hours waiting for the SDK to download this my internet is pretty slow. Thanks a lot!
Click to expand...
Click to collapse
Just get the all in one tool, ins;tall the relevant drivers and then go to recovery and select sideload a rom, go to the all in one toolkit and select sideload a rom, then choose the rom, simples
Sent from my Transformer Prime TF201 using xda premium

Thanks, guys. I ordered an OTG USB cable this morning just to avoid any future problems.

[Q] Boot loop and ADB push problems. Please help.

Ok there is a lot info about this however I have a few issues that makes it difficult for me to get past.
I unlocked and rooted just fine. No issues.
I flashed the elemental kernel as I wanted the knock on feature. That was when I ran into problems and my backup doesn't work.
I started getting the "com.htc.htcdailer" isn't responding issue. Then the phone reboots. I am not up long enough to load a rom to flash either.
When I try to sideload anything it doesn't work. I did update all the SDK files like I found in some searches. No go.
I am at a loss now what to do. Any thoughts?
Thanks

mothmansound said:
Ok there is a lot info about this however I have a few issues that makes it difficult for me to get past.
I unlocked and rooted just fine. No issues.
I flashed the elemental kernel as I wanted the knock on feature. That was when I ran into problems and my backup doesn't work.
I started getting the "com.htc.htcdailer" isn't responding issue. Then the phone reboots. I am not up long enough to load a rom to flash either.
When I try to sideload anything it doesn't work. I did update all the SDK files like I found in some searches. No go.
I am at a loss now what to do. Any thoughts?
Thanks
Click to expand...
Click to collapse
Boot into TWRP, download this driver:
http://www.koushikdutta.com/post/universal-adb-driver
Connect it to your PC in TWRP mode to your computer and Windows Device Manager, update the driver pointing to the one downloaded.
It should install with out an issue and the device should be detected thru ADB. Now all you need to do is push the rom via ADB. I recommend Cyanogenmod as its very small to push. I cannot quite remember the command to push a file as it can be complicated in the folder parts, but use this to push easily:
http://skipsoft.net/download/toolkit/nexus7toolkit/Google_Nexus_7_ToolKit_v5.0.0.exe
Ignore the fact that it's for the Nexus 7. Once it's installed, navigate to My Computer, click your hard drive and you should see a folder called Nexus 7 toolkit or similar (if not there check in Program Files). Look for an exe called "tkmain" and create a shortcut of it on your desktop. Keep that folder section open for now. Double click it. MAKE SURE YOU CAN SEE YOUR DEVICE SERIAL ON TOP TO ASSURE ITS CONNECTED. Now go to the same folder you saw the tkmain.exe and you should see a folder that says "Put Files to Push here". Drop the rom in there. I recommend naming it something short like "cyanogen.zip" for example. Now back on the toolkit, select the option that says Push file (I think it's option 13), answer Yes to the insecure boot image question, when it says select a file to push you should see the name of the rom zip , type it exactly as its name/you renamed it. When it says select a location, select /sdcard/ and proceed with the rest. It may seem like nothing is going on, and it may say something about "failed: success" beforehand, but trust me it's pushing, once it says complete, your ready to flash the rom.
Remember that if your S-Off, you need to flash the boot.img seperately via fastboot.

Crossvxm said:
Boot into TWRP, download this driver:
http://www.koushikdutta.com/post/universal-adb-driver
Connect it to your PC in TWRP mode to your computer and Windows Device Manager, update the driver pointing to the one downloaded.
It should install with out an issue and the device should be detected thru ADB. Now all you need to do is push the rom via ADB. I recommend Cyanogenmod as its very small to push. I cannot quite remember the command to push a file as it can be complicated in the folder parts, but use this to push easily:
http://skipsoft.net/download/toolkit/nexus7toolkit/Google_Nexus_7_ToolKit_v5.0.0.exe
Ignore the fact that it's for the Nexus 7. Once it's installed, navigate to My Computer, click your hard drive and you should see a folder called Nexus 7 toolkit or similar (if not there check in Program Files). Look for an exe called "tkmain" and create a shortcut of it on your desktop. Keep that folder section open for now. Double click it. MAKE SURE YOU CAN SEE YOUR DEVICE SERIAL ON TOP TO ASSURE ITS CONNECTED. Now go to the same folder you saw the tkmain.exe and you should see a folder that says "Put Files to Push here". Drop the rom in there. I recommend naming it something short like "cyanogen.zip" for example. Now back on the toolkit, select the option that says Push file (I think it's option 13), answer Yes to the insecure boot image question, when it says select a file to push you should see the name of the rom zip , type it exactly as its name/you renamed it. When it says select a location, select /sdcard/ and proceed with the rest. It may seem like nothing is going on, and it may say something about "failed: success" beforehand, but trust me it's pushing, once it says complete, your ready to flash the rom.
Remember that if your S-Off, you need to flash the boot.img seperately via fastboot.
Click to expand...
Click to collapse
Thank you very much for the help.
When I get to the point of typing which file to push the application cannot find the file.
I have been flashing roms for a while since the OG Droid and I can't understand why this has happened. I'm close to being beat.

mothmansound said:
Thank you very much for the help.
When I get to the point of typing which file to push the application cannot find the file.
I have been flashing roms for a while since the OG Droid and I can't understand why this has happened. I'm close to being beat.
Click to expand...
Click to collapse
The ROM must be in the folder that says "put files to push here" (make sure its that folder as I remember that another one seems similarly worded) from the toolkit program directory. You have to manually place your file there. If anything, close the toolkit and reopen it (remember, tkmain, the other section of the program is all Nexus related) and try again. Remember also to shorten the name so you don't have to type it in completely. Somewhere above where your supposed to type the file name you should see your ROM file. That's when you type it in exactly as you see it, for example, "rom.zip" you will type it in exactly like that.

Crossvxm said:
The ROM must be in the folder that says "put files to push here" (make sure its that folder as I remember that another one seems similarly worded) from the toolkit program directory. You have to manually place your file there. If anything, close the toolkit and reopen it (remember, tkmain, the other section of the program is all Nexus related) and try again. Remember also to shorten the name so you don't have to type it in completely. Somewhere above where your supposed to type the file name you should see your ROM file. That's when you type it in exactly as you see it, for example, "rom.zip" you will type it in exactly like that.
Click to expand...
Click to collapse
Yessir I double and triple checked that, I can't get it to find the file. I did rename a couple of different ways and tried with and without the".zip" part. No luck. I do appreciate the help.

mothmansound said:
Yessir I double and triple checked that, I can't get it to find the file. I did rename a couple of different ways and tried with and without the".zip" part. No luck. I do appreciate the help.
Click to expand...
Click to collapse
Do you have an adb/fastboot folder set up? If so, time for some manual method. Grab the ROM zip and put it in the same folder as your ADB and fastboot folder. Start adb thru command prompt then type in:
Code:
adb push ROM.zip /storage/sdcard
Hopefully I remembered it correctly. Should be that way.

Crossvxm said:
Do you have an adb/fastboot folder set up? If so, time for some manual method. Grab the ROM zip and put it in the same folder as your ADB and fastboot folder. Start adb thru command prompt then type in:
Code:
adb push ROM.zip /storage/sdcard
Hopefully I remembered it correctly. Should be that way.
Click to expand...
Click to collapse
Its saying device not found and doesn't seem to push.

Crossvxm said:
Do you have an adb/fastboot folder set up? If so, time for some manual method. Grab the ROM zip and put it in the same folder as your ADB and fastboot folder. Start adb thru command prompt then type in:
Code:
adb push ROM.zip /storage/sdcard
Hopefully I remembered it correctly. Should be that way.
Click to expand...
Click to collapse
Its saying device not found and doesn't seem to push.

I finally got the RUU to work. What a week and seems fine now.
Last piece of advice hopefully. All I want is the tap to wake feature. Stock is fine.
What is the best way to do that? When I tried using other kernals is when I ran into problems.
Thanks for the help.

mothmansound said:
I finally got the RUU to work. What a week and seems fine now.
Last piece of advice hopefully. All I want is the tap to wake feature. Stock is fine.
What is the best way to do that? When I tried using other kernals is when I ran into problems.
Thanks for the help.
Click to expand...
Click to collapse
Lol i misread that disregard the rest. What custom kernel are you trying to use? Remember each device is the same but also different. I had 2 LG G2s that would not double tap to wake, but would double tap to sleep. All the rest of them worked perfectly. Have also came across friends with G2s that wouldnt work

mothmansound said:
I finally got the RUU to work. What a week and seems fine now.
Last piece of advice hopefully. All I want is the tap to wake feature. Stock is fine.
What is the best way to do that? When I tried using other kernals is when I ran into problems.
Thanks for the help.
Click to expand...
Click to collapse
Best way is to flash the kernel in my signature. After you flash it, double tap to wake should be working automatically.

[Q] Stucked in recovery badly.. Please help me

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....

Emulator-5554 error in fastboot

Im trying to install a fresh ROM and keep getting an error.
What am I missing? any insight is greatly appreciated.
ThANKS IN ADVANCE

I don't know if any of these will work but here are some things you can try:
1) Make sure you are on the latest sdk. I think latest is 30.0.4. Looks like you're using v30.0.0?
2) Try using adb -s ### sideload ***.zip. The ### is the the device id you get from adb devices. -s directs the command towards your phone instead of the offline emulator.
3) Try running adb sideload from the path where the zip is located rather than using quotes to include the entire long path. In other words: adb sideload Aosip***.zip. You may have to add the path to platform tools into your environment variables or include the path to adb in the command.

neo_lithic3K said:
I don't know if any of these will work but here are some things you can try:
1) Make sure you are on the latest sdk. I think latest is 30.0.4. Looks like you're using v30.0.0?
2) Try using adb -s ### sideload ***.zip. The ### is the the device id you get from adb devices. -s directs the command towards your phone instead of the offline emulator.
3) Try running adb sideload from the path where the zip is located rather than using quotes to include the entire long path. In other words: adb sideload Aosip***.zip. You may have to add the path to platform tools into your environment variables or include the path to adb in the command.
Click to expand...
Click to collapse
Its kind wierd, it only happens while trying to ADB sideload in the custom Boot.img (lineage, Aosip, etc)
but i have no problem flashing the boot.img vis bootloader.
Thanks for the response.

bignu77 said:
Its kind wierd, it only happens while trying to ADB sideload in the custom Boot.img (lineage, Aosip, etc)
but i have no problem flashing the boot.img vis bootloader.
Thanks for the response.
Click to expand...
Click to collapse
I don't think you're supposed to sideload a boot.img. usually the rom zips will install them as part of the install process

dragynbane222 said:
I don't think you're supposed to sideload a boot.img. usually the rom zips will install them as part of the install process
Click to expand...
Click to collapse
My bad, I worded that wrong it only happens once in the custom recovery and try to ADB sideload the rom, i get that error.
Fastboot boot.img via bootloader works fine.
My trouble starts one in custom recovery and it shows "emulator-5554". Please see attachment.
Thanks

bignu77 said:
Im trying to install a fresh ROM and keep getting an error.
What am I missing? any insight is greatly appreciated.
ThANKS IN ADVANCE
Click to expand...
Click to collapse
The computer is telling you what the error is. In fact adb tried to flash the ROM twice two different ways and still displayed the same error. "More than one device/emulator". The connection fails because you have another device/emulator/something connected to your computer that adb recognizes. Adb states that too. Adb will not flash to more than one device so you have to find what that thing is. Try removing things you have connected to your computer or the emulator, whatever it is, because we don't know. Or try what the other guy said, specifically method #2. You never replied wether or not you tried that specifically. That could work. One other thing, are you in the custom recovery selecting "apply update from adb/whatever it is" and trying to sideload it? Otherwise make sure to update the sdk too because we don't know if you actually tried that either.
Sent from my Pixel 4 XL using XDA Labs

bradical711 said:
The computer is telling you what the error is. In fact adb tried to flash the ROM twice two different ways and still displayed the same error. "More than one device/emulator". The connection fails because you have another device/emulator/something connected to your computer that adb recognizes. Adb states that too. Adb will not flash to more than one device so you have to find what that thing is. Try removing things you have connected to your computer or the emulator, whatever it is, because we don't know. Or try what the other guy said, specifically method #2. You never replied wether or not you tried that specifically. That could work. One other thing, are you in the custom recovery selecting "apply update from adb/whatever it is" and trying to sideload it? Otherwise make sure to update the sdk too because we don't know if you actually tried that either.
Sent from my Pixel 4 XL using XDA Labs
Click to expand...
Click to collapse
Thanks for clearing that up.
The only other thing connected it the cordless mouse reciever.
I also did update sdk platform. as shown in the attached. Yes i am trying to apply update from adb and then sideload command I also tried typing the specific file name instead of the whole path.
It only happens in adb mode. Flashing via fastboot works fine with no emulator error.
Ive been flashing for months using the standard adb method with no hiccups. Now im getting this error

SOLVED
I found it!! It was a game my kids downloaded that had a built emulator that causing the hiccup! Back to gold, thanks guys!!:good::highfive:

bignu77 said:
I found it!! It was a game my kids downloaded that had a built emulator that causing the hiccup! Back to gold, thanks guys!!:good::highfive:
Click to expand...
Click to collapse
Figured it something related to that, I'm happy you fixed it though, enjoy the ROM.:good: