I am currently running Froyo 2.2 Red Glass Nov 2 Update using the Firerat Partition Mod. I am using Windows 7 Ultimate and I can't get ADB to work. It's something with the drivers. Does anyone have the drivers needed to get ADB working on Windows 7. I think it may be the updates Windows pushed down but it could be something else. Also I wanted to know, if there's a way to flash a recovery without using adb. My recovery is f*cked...I had RA-1.7 (Darch Unofficial) working properly, but wanted to see what was the benefit of using ClockWorks and I went from Clockwork to 1.6.2 and now I can't boot into recovery at all. If you need a log let me know. Thanks!
SN: I know this is in the wrong forum but I can't get my phone to boot into recovery nor use adb on my pc to flash a new recovery image. I need help because I'm gonna go crazy...AAAHHHH...wouldn't you do the same for your Hero???...lol...but seriously, I need help like yesterday if anyone has a solution please PM me or post. Thanks Guys...
I can't remember why but that happened to me. I'm running windows 7 64 bit. Try using the flash_image command and push a new recovery I always use amon ro 1.6.2. You can do that from terminal on your phone if you have to. I don't know if your s-off but if worse comes to worse then you could use a HERCIMG.zip Also another guy wrote about this in the q&a section. But it could have been deleted. I remember I ended up running the ruu at the end. It's not the computer it's the phone
WOW..you really need to search and put this in the right section. you even knew this was the wrong section and only posted cuz its a busier section!!
If you would have just even looked through this section a bit you wouldve found this thread that has the drivers.
http://forum.xda-developers.com/showthread.php?t=832240&highlight=drivers
Read this also it will help
http://www.xda-developers.com/announcements/a-reminder-from-the-xda-moderator-team/
As for your problem im sorry i cant help you out but if you post in the Q&A section like your supposed to then im sure someone there can figure it out. Possibly IMPALER as he seems to be on alot.
Good Luck with finding something out.
Correction for ^^^
t12icky0 said:
WOW..you really need to search and put this in the right section. you even knew this was the wrong section and only posted cuz its a busier section!!
If you would have just even looked through this section a bit you wouldve found this thread that has the drivers.
http://forum.xda-developers.com/showthread.php?t=832240&highlight=drivers
Read this also it will help
http://www.xda-developers.com/announcements/a-reminder-from-the-xda-moderator-team/
As for your problem im sorry i cant help you out but if you post in the Q&A section like your supposed to then im sure someone there can figure it out. Possibly IMPALER as he seems to be on alot.
Good Luck with finding something out.
Click to expand...
Click to collapse
I need x32 not x64...so I'm back at square one. Plus I did post in the right section in addition to this one. I got 41 views and no replies...that sucks right...
Try using Rom manager to re-flash clockwork?
Plan C: RUU your phone, and re-root and go from there...
There is no reason for him to reflash any recovery, as adb connectivity starts in recovery and drops when you pass it or reboot the phone and picks up from the rom itself (the adb communication interface is built into all versions of android)
Win7 32bit works fine with the 32bit ADB drivers, but just like the 64bit win7, it has hickups sometimes. That's your problem I am sure. Sometimes when you disconnect and reconnect a device (or it reboots) in windows 7 the drivers crash, and what win7 does as opposed to xp or vista, is sort of blacklisting the driver to stop it from crashing the rest of the windows system.
Ergo, you just need to reinstall the drivers you already have.. Have you tried that?
BTW, HTC Sync drivers are completely different than ADB drivers, and will cause conflicts. Did you install HTC Sync lately?
One last thing, you remember where you installed adb? Or rather your Android-sdk-Windows directory? From there it is in the usb_driver folder.
i.e. if you installed to the root of your drive, it would be in:
c:\android-sdk-windows\usb_driver\
The name of the file is android_winusb.inf
Well when you do, or either way, someone move this to the q-n-a section.
Problem solved.
"Gregory House 1, God 0" - Gregory House
B-Nice_88 said:
I need x32 not x64...so I'm back at square one. Plus I did post in the right section in addition to this one. I got 41 views and no replies...that sucks right...
Click to expand...
Click to collapse
Hows this going? Try pming carbon kang he had the same issue back in May it's happened to quite a few of us after using a different recovery and flashing this one rom. I know it sounds crazy and shouldn't be happening but it did. The thread that it was in got deleted probably by mistake.
Related
Hey guys Sorry for repost of the same questions im freaking out here... I just did some research (something i should have done before posting first , but im in freak out mode)....
Im stuck in bootloop after using the latest TnT lite...I would like to get that back .
I researched how to address this, however i see a couple of ways to get this thing running again, here is what I found:
Using Nvflash got this on TegraTabs site... does this require using my computer?
Here XDA... I saw that someone had the same issue and Clockworkmod Recovery was suggested.
OK this is where i am comfused If i use Clockwork I need my windows (vista) computer correct ? and it looks like I am going to be using command lines also (not a big deal for me)... I saw that i am going to need android SDk and also tegra drivers as well?
I am not looking for the easiest way looking for the best way ... Sorry for asking again however being a noob to Android I just want to make sure that I am doing things right.. is there any other information that would help you guys help me? let me know... again thanks you guys... still in freak out mode and dont want for my money to have been thrown away...I appreciate the help....you guys rock
RyuFDAC01 said:
Hey guys Sorry for repost of the same questions im freaking out here... I just did some research (something i should have done before posting first , but im in freak out mode)....
Im stuck in bootloop after using the latest TnT lite...I would like to get that back .
I researched how to address this, however i see a couple of ways to get this thing running again, here is what I found:
Using Nvflash got this on TegraTabs site... does this require using my computer?
Here XDA... I saw that someone had the same issue and Clockworkmod Recovery was suggested.
OK this is where i am comfused If i use Clockwork I need my windows (vista) computer correct ? and it looks like I am going to be using command lines also (not a big deal for me)... I saw that i am going to need android SDk and also tegra drivers as well?
I am not looking for the easiest way looking for the best way ... Sorry for asking again however being a noob to Android I just want to make sure that I am doing things right.. is there any other information that would help you guys help me? let me know... again thanks you guys... still in freak out mode and dont want for my money to have been thrown away...I appreciate the help....you guys rock
Click to expand...
Click to collapse
Best way is to download the Android SDK (to get ADB), the Tegra drivers and NVidia's SDK which includes nvflash. You can get the Tegra stuff here or over at our sister site, tegratab.com (we started putting stuff up there while waiting to get our own forums here on XDA). To get nvflash access, you'll need to modify the Android SDK's INF file (if you're on Windows). Nvflash can get you out of almost anything. Best to back up your images using nvflash before you flash anything else, that way you've got a copy of what's on YOUR tablet as it comes, stock. Since you're stuck in a bootloop, I'd guess you no longer have any stock partitions so maybe just pick up the stock images from over on tegratab.com. They should be fine for you but it's nothing like having a pristine copy of your own images.
Hope that helps. Not sure if I gave enough detail but shout if you need more. We have some really good people here.
Yes you need a PC for NVflash. If clockwork fails then your going to have to NV flash back to stock.
Hey guys I would like to thank you for your responses
I was actually able to bring back my Gtab with the help of forum member dcom222 in this thread
http://forum.xda-developers.com/showthread.php?t=852286
RyuFDAC01 said:
Hey guys I would like to thank you for your responses
I was actually able to bring back my Gtab with the help of forum member dcom222 in this thread
http://forum.xda-developers.com/showthread.php?t=852286
Click to expand...
Click to collapse
I plan to incorporate his method into my TnT Lite post, there's some good stuff in there.
i need some help rooting my strat i been following this guide http://rootzwiki.com/topic/7840-kernel-guide-root-your-stratosphere/
and i already flashed the kernel already and im on the part where u need to put your phone into usb debugging and so i plug my phone in and let it install its drivers and then i open up CMD in windows and i copy and paste this command F:\Downloads\heimdall-suite-1.3.1-win32>adb devices
to see if it detects my device and it just says device not ready... soo that is where i am stuck at i have downloaded and installed android sdk and did the updates with it and i close out of it and then do the same thing in cmd and still says device not ready..... im lost
i placed android sdk under the root of my C drive called android im running windows 7 64bit
redid the WHOLE walkthrough went and reinstalled adk, and re doing the kernel file to the phone and now im back at the same part but now i get this, there is no disk in the drive please insert a disk into the drive /device/harddisk2/DR2.
and all i get is cancel try again and continue and when i do it again its the same thing..... it seems this is just a simple thing but being stupid
ill donate 15$ to who ever helps me and completes this with me lol
good job? lol didnt do anything
Did u get it I'm in the middle of rooting mmine. Still seting up adb on new laptop.
yea im still stuck BUT someone on a different forum gave me this http://rootzwiki.com/topic/9711-untested-odin-for-stratosphere/ but im a little scared to test this because this is the only phone i have
rooting thur odin right now.... wish me luck
well that didnt work and bricked
does anyone have the stock files to odin back to stock?
.
Thread moved. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
I can't seem to find a Clockwork Recovery install anywhere and was wondering what the progress was in the port? I seen that someone posted they were working on it on the root thread and need to know if any updates on it? I know there are a ton of people that won't go without a slider and seeing as this phone is the only 4g slider right now I figured there would be all kinds of rom support for it. Its unlocked bootloader was the reason i got it along with my fiancee's need for a keyboard. First time i seen any android device without cwr.
cydetrakd said:
I can't seem to find a Clockwork Recovery install anywhere and was wondering what the progress was in the port? I seen that someone posted they were working on it on the root thread and need to know if any updates on it? I know there are a ton of people that won't go without a slider and seeing as this phone is the only 4g slider right now I figured there would be all kinds of rom support for it. Its unlocked bootloader was the reason i got it along with my fiancee's need for a keyboard. First time i seen any android device without cwr.
Click to expand...
Click to collapse
Ill donate to a dev who doesnt have the phone buts wants to dev
Sent from my SCH-I405 using Tapatalk
samsung stratosphere trouble!!
Hi everyone. I was looking for some help to fix the samsung stratosphere that i tried rooting the other day. I will explain to the best of my knowledge as to what i did and how i got where i am with trying to root my phone and where i believe things went bad. i downloaded heimdall and all the necessary files that i got off of the rootzwiki forum specifically for rooting this phone. I was following the instructions exactly as they are posted. Well i than tried to use a different method within heimdall called heimdall - front end. i tried flashing the kernel from the rootzwiki forum using this method. i loaded the stratosphere.pit and went to the flash menu and checked repartition and reboot phone and clicked flash. Thats where the trouble began,now it seems that my phone is stuck in a bootloop,where it will either go to the screen where it asks if you wanna flash a custom rom or it will go into recovery mode if i try to reboot the phone. When my phone is plugged in, it dont show thats its charging but the power button will work sometimes or i just have to hold the power and volume down button and it will go to the custom rom screen. If anyone could help me figure this out,it would be greatly appreciated and thanks in advance for any help or advice on my situation.
I have a problem. I just got my Android a couple of days ago and I really badly want to root it. I've tried multiple different programs and with each one the problem I get is "Waiting for device" in the cmd/terminal (Tried on multiple platforms: Vista, Win7, Ubuntu). I've tried installing drivers too and still didn't work (maybe the wrong drivers?).
Yes I realize that I am a "noob", but I really need some help here.
Got USB Debugging enabled ??
Got the correct upto date drivers ?
You navigated to the right location in ADB ??
azzledazzle said:
Got USB Debugging enabled ??
Got the correct upto date drivers ?
You navigated to the right location in ADB ??
Click to expand...
Click to collapse
>Yes
>I think so, not positive.
> What do you mean?
bumpp someone help?
Well Redownload the drivers and see if that helps, You could try Hasoon2000's All In One Kit to help with this. http://forum.xda-developers.com/showthread.php?t=1604677
As for ADB, (Android Debug Bridge) you should have this already, You need it to get unlock the bootloader and flash superboot (root) http://forum.xda-developers.com/showthread.php?t=1583427
Be sure to check out those links and also look at my FAQ section http://forum.xda-developers.com/showpost.php?p=24884624&postcount=3
I have all the files that it says are necessary to unlock the bootloader. It's just when I type "fastboot oem get_identifier_token" it just sits there saying "waiting for device".
I've tried hansoon's all in one program as well and it didn't work either.
Well that means it cannot find your phone, So the issue lies with the drivers and/or the location from which the command prompt is opened..
Put all of the files into 1 folder called android or adb and move that 1 folder to the root of your C Drive..
This should make navigating easier. Also, In that folder should be adb.exe and fastboot.exe do you have these ?
I fixed this by just playing around with it a bit more. Thanks for the help, though.
infam0us me said:
I fixed this by just playing around with it a bit more. Thanks for the help, though.
Click to expand...
Click to collapse
what exactly did you do? I am stuck with this problem for a long time now. nothing seems to help. what does "playing around" mean?
windows 8.1
htc one s (c2)
morphication said:
what exactly did you do? I am stuck with this problem for a long time now. nothing seems to help. what does "playing around" mean?
windows 8.1
htc one s (c2)
Click to expand...
Click to collapse
Well man, I really wish I could help you out because I remember how frustrating this was for me. This post was 2 and a half years ago though. Just really make sure that your drivers are up to date. If I could remember my exact solution I would help you out for sure.
infam0us me said:
Well man, I really wish I could help you out because I remember how frustrating this was for me. This post was 2 and a half years ago though. Just really make sure that your drivers are up to date. If I could remember my exact solution I would help you out for sure.
Click to expand...
Click to collapse
ok. it was windows 8 not allowing unsigned drivers to install properly. note: not "not installing at all", but "not installing properly". meaning: htc drivers installed somehow, so I was able to see the device and copy files around, but it was not enough for flashing roms.
so I started this guide to disable driver signature:
https://www.youtube.com/watch?v=gmw86KplqmU
... but my laptop is a business laptop and this guide demands BitLocker key if hard drive is encrypted (mine is). I also have a windows 7 desktop machine. So I decided to go the easy and quick way of simply doing flashing on my desktop computer. Windows 7 worked like a charm. But I'm sure the guide above would've helped as well. If somebody tries that, please post results.
I was working fine, enjoying my new HTC One S with CM9 rom installed. Well the battery life wasnt the best on it, and i didnt install the custom kernel. So I looked for the custom kernel download(on my phone, not on my computer) and i found a .zip file. Well I thought that you could just download the kernel straight to my phone and open it up with "Rom Manager" which i did, it than said i needed to reboot the phone in recovery to continue the installation, so I did... it took me to recovery "to continue the installation" well than I looked away, looked backed down and it was black.... and i have tried powering up, booting into boot loader, booting into recover, and nothing... its just BLACK! nothing works, its literally useless ATM. I really messed up, is there anyway to fix this? Thanks in advanced!
----EDIT----
I think I accidentally flashed the kernel like i would normally flash a rom.... cause i downloaded the .zip file(directly to my phone, not using a computer), than i tapped the download and it asked me if i wanted to open it up with rom manager, so i did. and i think rom manager thought i was flashing a rom, when i wasnt, it was a kernel.... am i screwed? or is there anyway out of this?
Do you know the exact kernel you flashed--where did it come from
Some you need to extract and push
Assume you just tried to boot into bootloader thru phone buttons
Does your pc recognize your phone when plugged in, if so can you open a command window and try to access phone as in adb devices then adb reboot bootloader
assuming you are familiar with sdk adb/fastboot comands
otherwise i don't know what else to say--may be bad--sorry
Came from an XDA thread
Here is where it came from: http://forum.xda-developers.com/showthread.php?t=1708676 from "sun90" (half way down the page "CM9 KERNEL remix edition.zip - [Click for QR Code] (5.53 MB, 9 views) ")
i downloaded that straight to my phone and opened it up with Rom Manager, which i think the app took it as a rom, and installed it like a rom even though it was not a rom. I just tried to access it through adb, it comes up with no devices my PC does recognize it when i plug it in though...
Ive tried to get into bootloader tons of times, it just stays black... :'(
Thanks for your answer!
You flashed a galaxy s2 kernel on your one s? why would you ever think that was a smart thing to do?
Looking at the updater script in that zip it seems it wipes some partitions, the partitions on a SGS2 and the ONE S are different, so if that script accidentally wiped say the hboot partition, or some other critical-for-boot partition, you have a fully bricked phone.
For any devs that may know what partitions are what on the One S, the script wiped
mmcblk0p7, and wrote a zimage to mmcblk0p5
---EDIT---
Normally this is a cwm flashable zip on the Samsung Galaxy S II, which is why rom manager flashed it, as it met all the requirements, the only issue is, it was not made for the ONE S and probably overwrote some important things.
I tried for hours and hours to fix the same issue on a friend's One S (same symptoms, not same cause) to no avail. I tried QPST and telnet and a ridiculous amount of things. Had to bring it to the store and get a new one.
Good luck, but I don't believe there's anything you can do to fix it.
Just answered your question in the help thread, Didnt see this thread too !
Im afraid its not looking good, I think your best bet would be to call your provider and blame it on an OTA update.
And hope for the best
Alright, thanks for the help!
Well it looks like i bricked my phone than.... I thought that CM9 was only on the One S, so I just looked for the CM9 kernel, which obviously was for the sg2, i feel like such a dumb ass now! haha well thanks for all the help guys! ill be heading to the t-mobile store today to blame it on a OTA:]
yeah, others wont agree with what your about to do but........
just act like a complete noob, dont mention anything about software / firmware / ROMs / bootloader etc ect
just say your phone made a noise, you selected update and it died lol
good luck--I know it is heartbreaking
not sure of your situation with carrier, but you could go thru Retention if needed
Hi peeps.
i'm very new to all this but sort of know the basics
i'm running on Axiom now but tried to flash cm10 but after install i got a black screen so had to do a restore.
Today i just flashed venom and after the instal process is done, i hear the start up music but nothing on the screen.
I have had 3 other roms on my phone and never had a problem!
these are the steps i do
download rom - place on sd
put phone in recovery
reset factory
reset cache
install from sd
when it finish's reboot
blank screen.
Am i missing something?
Any help would be great and i can't post on the thread because i'm a noob with less than 10 and dont want to spam my way to the 10 :silly:
you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe
rugmankc said:
you are missing a lot, like reading the OP page and following install instructions
you missed separate flash of boot image and wiping system plus data and caches
i wipe system 3x to be safe
Click to expand...
Click to collapse
Thanks but i think that is now the least of my problems!
I used Goomanager and installed CM10, When I did it i installed teamwin recovery. It started to do a lot of strange things, when it finally rebooted i got a load of errors "phone is not working" nearly every 10 seconds?
it will not connect via usb, i discovered the the SD was not mounted.
I tried to mount the SD but it doesnt work, so i rebooted to recovery and tried to mount there but its coming up with - error unable to mount? ive tried everything but no joy
please please help
Thanks:crying:
see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands
rugmankc said:
see if this is your situation
http://forum.xda-developers.com/showthread.php?t=1630459
can you connect phone to pc and use fastboot commands
Click to expand...
Click to collapse
I've got a mac
not sure what fastboot is.
I'll check out the link, and thank you very much for trying to help:good:
sorry i do know what fastboot is, yes can get in to it. but ive gone from CWM to teamwin recovery if i go in to the recovery section but that wont let me do anything because the mount. cant even load the phone up
I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track
rugmankc said:
I don't know Mac commands
My idea is to install htc drivers and set up fastboot/adb on pc--the info can be found in dev section on rooting
then open a command window and and boot into fastboot and flash a new recovery, maybe stock per the link, clear storage and try to get mounted
how did you unlock bootloader--
you will need to do alot of reading on adb/fastboot and flashing roms--first step is to have backups of rom and sdcard
since i don't the Mac commands to do fastboot, someone else will chime in at some point
you can alos go to the noob section in Q&A and resubmit your issue
someone will work you thru this, but in meantime study up on android sdk/fastboot/adb. a necessity to get out of these problems
you are not bricked, just need the info and right steps to get back on track
Click to expand...
Click to collapse
im going to use someone elses alp top with windows. i'll ytry the all in one thing because thats how i rooted it in the first place. thanks for helping it means alot
good luck on it
Hi there
I just got a new laptop running Window 8.1
I want to flash the latest TWRP to able to flash android 4.4 kitkat. But after i install "htc sync manager" and "htc sync", still dont have usb-driver on fastboot mode. So i cant flash the TWRP recovery.
Can any1 help me step by step how to get the fastboot-usb to install the TWRP on Window8?
My phone got everything already, just need the usb-driver, so in the fastboot can recognize the usb, so that i can flash latest TWRP.
(My phone running TWRP 2.3.3.0 already)
(My new laptop had Android-sdk already)
Thank for helping me guys :good:
Have you searched for a solution? I've seen a few threads discussing this problem.
Sent from my Evita.
timmaaa said:
Have you searched for a solution? I've seen a few threads discussing this problem.
Sent from my Evita.
Click to expand...
Click to collapse
i did, but not step by step, i quite noob, thats why i am asking man :crying:
If you found any thread that have a detail and step by step, please let me know
There are threads that detail it step by step but you need to find them.
Sent from my Evita.
lol, if i can do that, i am not spending my time to create this thread.
Any1 else please???
Surely you can use the XDA search feature and/or Google?
Sent from my Evita.
timmaaa said:
Surely you can use the XDA search feature and/or Google?
Sent from my Evita.
Click to expand...
Click to collapse
actually, i did that already, but after that, still nothing change. Even reinstall htc sync manager, but still when i reboot the phone to bootloader and go to fastboot, usb still not working. I dont know why, like i said, i am quite noob, thats why i am asking for some help if any1 know my problem.
Anyway, thanks alot for your help man, very appreciate but the problem still here
PS: another thing is my laptop using AMD cpu, and all of solution is just for intel-usb @[email protected] i cant follow someway, such as this:
http://forum.xda-developers.com/showthread.php?t=2347317&page=4
Unfortunately I don't run Windows 8 so I don't have any personal experience with getting it to work. The best solution I've seen people talk about is to use a different version of Windows.
Sent from my Evita.
Run a Linux live cd and use fastboot that way.
Sent from my iPhone using Tapatalk
There is no signed Windows 8.1 Android driver.
To make it work there is several hoops to jump through. Really its easier to just boot into Linux or use another computer.
Eg my Desktop runs Windows 8.1 but my laptop has Windows 7, so I use the laptop for fastboot.
thinhletien said:
Hi there
I just got a new laptop running Window 8.1
I want to flash the latest TWRP to able to flash android 4.4 kitkat. But after i install "htc sync manager" and "htc sync", still dont have usb-driver on fastboot mode. So i cant flash the TWRP recovery.
Can any1 help me step by step how to get the fastboot-usb to install the TWRP on Window8?
My phone got everything already, just need the usb-driver, so in the fastboot can recognize the usb, so that i can flash latest TWRP.
(My phone running TWRP 2.3.3.0 already)
(My new laptop had Android-sdk already)
Thank for helping me guys :good:
Click to expand...
Click to collapse
windows 8.1 wont recognize my htc one x with ICS rom. however when i updated to jellybean 4.1.1 and connected to the windows 8.1, it installed all the required drivers itself and now I am able to connect the phone/fastboot etc. I tried installing HTC Sync previously but that doesnt help cuz while the installation process the Htc Driver Installer fails to install.