I am attempting to get s-off and I seem to be running into some issues. Here is the output of Control bear:
======== ControlBear 0.4 beta for JuopunutBear S-OFF ==========
Starting up......
Backing up......
Transferring backups....
Backup ok!!
Using eMMC dev /dev/block/mmcblk0
Using MMC dev /dev/block/mmcblk1
Boot partition is /dev/block/mmcblk0p22
Recovery partition is /dev/block/mmcblk0p23
Is information correct? You have 5 seconds time to press CTRL+C
Finding some beer.....
Found first....
Found second....
Found third....
Hmmmm... where is that last one....... Wait a sec....
Found fourth....
Rebooting.......
=== Waiting device....
(45/45)
Hmmm, still no device
Resetting connection....1........2....
(45/45)
Hmmm, still no device
Resetting connection....1........2....
(45/45)
Hmmm, still no device
Resetting connection....1........2....
(45/45)
Hmmm, still no device
Resetting connection....1........2....
(45/45)
Hmmm, still no device
Resetting connection....1........2....
(45/45)
Hmmm, still no device
Resetting connection....1........2....
(45/45)
Hmmm, still no device
Any ideas why it is unable to find the device? BTW, this is on linux, and I am running as root.
Same exact thing it does to me on windows. Once mine gets to the screen with the arrow it can't find my phone anymore. Odd since cleanflash has no trouble. I tried reinstalling adb and HTC drivers to no avail. I finally just gave up for the moment.
Sent from my ADR6425LVW using XDA
I ended up just copying all of the control bear stuff to my platform tools folder with rest of my adp stuff and bam.
Sent from my ADR6425LVW using xda premium
blestsol said:
I ended up just copying all of the control bear stuff to my platform tools folder with rest of my adp stuff and bam.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I tried that, still didn't work for me. I've installed and uninstalled the drivers multiple times. It just refuses to find my phone no matter what I do.
Just thinking out loud, but are you unlocked, custom recovery?
Sent from my ADR6425LVW using xda premium
trickster2369 said:
Just thinking out loud, but are you unlocked, custom recovery?
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I am unlocked, CWM recovery, usb debugging on (at least it is when control bear starts). adb just seems to be unable to connect to the device after the first reboot.
Unlocked aman-ra 3.15. Its odd that it finds the phone just fine to backup and reboot. Also reboots from fastboot no problem. Its once it gets to the green arrow and tries to find my phone it fails.
Sent from my ADR6425LVW using XDA
kain72 said:
Unlocked aman-ra 3.15. Its odd that it finds the phone just fine to backup and reboot. Also reboots from fastboot no problem. Its once it gets to the green arrow and tries to find my phone it fails.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
We seem to be having the exact same problem (except I am on CWM). Guess that eliminates the recovery as the culprit....
kain72 said:
Unlocked aman-ra 3.15. Its odd that it finds the phone just fine to backup and reboot. Also reboots from fastboot no problem. Its once it gets to the green arrow and tries to find my phone it fails.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
This is before the wire trick or after you do the wire trick?
CharliesTheMan said:
This is before the wire trick or after you do the wire trick?
Click to expand...
Click to collapse
Before the wire trick, immediately after the initial boot into JP.
trud9340 said:
Before the wire trick, immediately after the initial boot into JP.
Click to expand...
Click to collapse
I also had a very similar issue the day it launched. I can't remember what was keeping the program from running like it should, I believe that when I uninstalled or killed HTC syn running, and went to the task manager and killed ADB.exe in windows I realized that there was a droid explorer service running that kept instantly restarting ADB. Once I finally killed the service then restarted the program it worked.
Have you tried using a second windows computer just for kicks? If it's convenient I would try that and then just run a linux live cd if windows is still having driver issues.
I'm stuck with only my laptop for the moment. Its odd, I've killed HTC sync and everything else I can think of including antivirus
Sent from my ADR6425LVW using XDA
I had the same problems yesterday, there was some htcsyncupdate process running that kept on interfering with the process.
In task manager make sure to show processes of all users. Also be sure in msconfig.exe you have selective startup selected so that it's not just restarting what you kill when you reboot.
I can't think of much else off the top of my head, I'm willing to remote in and take a look on team viewer just to offer a second set of eyes if you would like. Someone else may post and tell you exactly where the issue lies.
Hmm
Query if enough permissions, drivers, and other services are running in safe mode to still allow for Controlbear to run without any HTC software interference.
I think I am going to give it a shot in safe mode here on the next try. Or at minimum make a custom boot state to kill everything but needed windows services. Unfortunately not near my pc for a while yet. Thanks for the suggestions guys can't hurt to try.
Sent from my ADR6425LVW using XDA
remote not allowed
Im trying to flash recovery through adb but it starts the install fails and says remote not allowed. Any suggestions? Im s-off, running 3.11
For recovery flashes I've always used clean flash. Just makes it easier for me.
Sent from my ADR6425LVW using XDA
Amon Ra
Please tell me you are NOT on CWM.
Lol not me aman-ra 3.15
Sent from my ADR6425LVW using XDA
Related
I was just attempting to root my thunderbolt and my computer crashed right after I finished the downgrade. What do I do next! I'm having a mild freak out right now, as this is my first attempt at rooting.. Any help would be appreciated.
Sent from my ADR6400L using XDA Premium App
Start over?
Sent from my ADR6400L using XDA App
Sky93 said:
I was just attempting to root my thunderbolt and my computer crashed right after I finished the downgrade. What do I do next! I'm having a mild freak out right now, as this is my first attempt at rooting.. Any help would be appreciated.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
No need to start over. Just pick up where you left off. The computer crashed, not the phone. Since you already downgraded, all you need to do is pick up in the directions where you left off. No damage has been done to your phone because your computer has nothing to do with flashing updates from the bootloader.
Sent from my rooted stock OTA MR2 Thunderbolt
But now my device isn't showing up under adb. It keeps saying device offline. I already restarted the phone, computer, and reinstated the drivers...
Sent from my ADR6400L using XDA Premium App
Sky93 said:
But now my device isn't showing up under adb. It keeps saying device offline. I already restarted the phone, computer, and reinstated the drivers...
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
If you just finished the downgrade, check Settings->Applications->Development to make sure Debugging is on and fastboot is off.
Also make sure you are in htc sync mode
Sent from my rooted stock OTA MR2 Thunderbolt
when i rooted my phone on sunday, i had a random reboot of my phone as soon as the downgrade was loaded. After that, the phone would show as offline in adb.
What i did to remedy that was to turn "USB Debugging" off, wait, then turn it back on. Then check if it shows up as online. Repeat this process until it works.
orkillakilla said:
Also make sure you are in htc sync mode
Sent from my rooted stock OTA MR2 Thunderbolt
Click to expand...
Click to collapse
I do not think that matters. I rooted my phone on charge only.
Sent from my ADR6400L using XDA Premium App
If it doesn't go right, make sure you start all the way over from the beginning. I don't know why, but this phone was a pain in the butt to get rooted. It took me a good six or seven tries before it finally worked for me.
Oh, also, for some reason you'll probably need to enable check "unknown sources" in applications before you'll be able to copy stuff to the SDcard. that freaked me out the first time I stumbled across this problem.
ramcharger1979 said:
I do not think that matters. I rooted my phone on charge only.
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Yea, I've never used an "htc sync" mode since I bought it so not sure about that one.
pdxphreek said:
If it doesn't go right, make sure you start all the way over from the beginning. I don't know why, but this phone was a pain in the butt to get rooted. It took me a good six or seven tries before it finally worked for me.
Oh, also, for some reason you'll probably need to enable check "unknown sources" in applications before you'll be able to copy stuff to the SDcard. that freaked me out the first time I stumbled across this problem.
Click to expand...
Click to collapse
It's pretty straight forward if you follow the step by step root guide instead of trying one of the scripts that have become oh so popular.
And I'm not sure about the "unknown sources" to copy to sdcard. The only reason you should need that is to actually install an apk that wasn't dl'ed through market.
Absolute_Zero said:
Yea, I've never used an "htc sync" mode since I bought it so not sure about that one.
It's pretty straight forward if you follow the step by step root guide instead of trying one of the scripts that have become oh so popular.
And I'm not sure about the "unknown sources" to copy to sdcard. The only reason you should need that is to actually install an apk that wasn't dl'ed through market.
Click to expand...
Click to collapse
For some reason after downgrading I wasn't getting the option to copy stuff to my SD card, i would charge but it wouldn't detect the connection.
I was following the guide.
The only reason I say put it in htc sync mode is because my phone shows offline unless it is in htc sync mode. Odd though.
Sent from my rooted stock OTA MR2 Thunderbolt
Rooting problem also
I have tried and tried and tried to root my Thunderbolt. I have followed the guide on xda to a T. The problem is this, once you get to step 4 where you boot to the bootloader and try to get the PG05IMG.zip to load, it loads it[blue status bar] checks it[gold status bar] then back to the hboot bootloader screen. Also i should note that when i put the file on my sd card the md5sums match, but after the process in hboot bootloader, they don't match. Oh, and i have asked in the irc chatroom also, they tell me im doing it wrong. Should note also tried to pull the ota update and no go either. It downloads and fails everytime! Bought the phone off of craigslist so no warranty, just would like to root because the phone force closes every program i bring up on it and its frustrating me. Thanx Dra$tiK
Well for the force closing problem, just try to do a factory reset on the phone. As far as the ruu failing in hboot, it sounds like maybe the misc.img file you pushed didn't take. Try restarting the whole process over again, and also redownloading the downgrade.
orkillakilla said:
Well for the force closing problem, just try to do a factory reset on the phone. As far as the ruu failing in hboot, it sounds like maybe the misc.img file you pushed didn't take. Try restarting the whole process over again, and also redownloading the downgrade.
Click to expand...
Click to collapse
How can I check to make sure that the file got pushed?
Is there an adb command I can try?
Also i have factory reset the phone 3 times from hboot.
Today however when i did reset it it went into a bootloop... thunderbolt screen constantly, was able to get it to the bootloader and all was well after that but still not rooted
Dra$tiK said:
I have tried and tried and tried to root my Thunderbolt. I have followed the guide on xda to a T. The problem is this, once you get to step 4 where you boot to the bootloader and try to get the PG05IMG.zip to load, it loads it[blue status bar] checks it[gold status bar] then back to the hboot bootloader screen. Also i should note that when i put the file on my sd card the md5sums match, but after the process in hboot bootloader, they don't match. Oh, and i have asked in the irc chatroom also, they tell me im doing it wrong. Should note also tried to pull the ota update and no go either. It downloads and fails everytime! Bought the phone off of craigslist so no warranty, just would like to root because the phone force closes every program i bring up on it and its frustrating me. Thanx Dra$tiK
Click to expand...
Click to collapse
Are you sure you have the downgrade as PG05IMG.zip and not .zip.zip?
Sent from my ADR6400L using XDA Premium App
ramcharger1979 said:
Are you sure you have the downgrade as PG05IMG.zip and not .zip.zip?
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
Yes, I have a windows 7 machine with file extentions turned on.
Because I thought the same thing and after it failed 4 times I checked it on astro file manager and I had put it in as zip.zip
Sent from my ADR6400L using XDA Premium App
ramcharger1979 said:
Because I thought the same thing and after it failed 4 times I checked it on astro file manager and I had put it in as zip.zip
Sent from my ADR6400L using XDA Premium App
Click to expand...
Click to collapse
No it is name PG05IMG.zip on my sd card.. this must be a common problem at least im hoping it is.. and a fixable one at that
Background: I just got a brand new rezound to replace a lost one. This was a full retail box, not a CLN. I S-offed with the last rezound with no other issues but the timing for the wire
Setup: Totally stock with the exception of unlocked, rooted, newest amon RA installed for recovery. Also SU and Busy box installed.
What I have done so far: several factory resets and several formats of a already formatted card.
Issue:
======== ControlBear 0.5 beta for JuopunutBear S-OFF ==========
Starting up......
Connecting to device...
Searching device.....
Found device.....
Backing up......
su: exec failed for /data/local/JuopunutBear -a -B Error:No such file or directo
ry
Transferring backups....
Secondary backup FAILED!!
Press ENTER to exit.....
Yes I have searched for the error but there is nothing posted anywhere for it. Either that or google gets a fail.....
Solution? My next move is to downgrage to 3.14 on AR. I am pretty sure that is where I was on the last one, but your suggestions in the eantime would be helpful
try finding an older version of control bear.
Sounds like you didnt run it as admin also
werdna87 said:
try finding an older version of control bear.
Sounds like you didnt run it as admin also
Click to expand...
Click to collapse
I went all the way back to .1 with no luck. Also I am running as administrator on a win7 64 machine
Thought of the downgrade for the Controlbear.
I did downgrade the AR to 3.14 with no luck
EDIT: i also set SU to just allow permissions without a prompt
piizzadude said:
I went all the way back to .1 with no luck. Also I am running as administrator on a win7 64 machine
Thought of the downgrade for the Controlbear.
I did downgrade the AR to 3.14 with no luck
EDIT: i also set SU to just allow permissions without a prompt
Click to expand...
Click to collapse
Use Linux. I had same problem a while back..ran smooth in Linux
Sudo ./ControlBear
Sent from my ADR6425LVW using xda premium
andrewp3481 said:
Use Linux. I had same problem a while back..ran smooth in Linux
Sudo ./ControlBear
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
not an option
Search wubi ubuntu installer, its not too difficult to set up and its easy to uninstall
Sent from my ADR6425LVW using Tapatalk 2
superchilpil said:
Search wubi ubuntu installer, its not too difficult to set up and its easy to uninstall
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Oh I am capable of going to Linux, but do not want to for a variety of reasons.
I need a Windows solution.
THe computer is not the problem, nothing has changed with that setup in months.
Try to delete that data/local/juopunutbear folder. Might still have data from your last phone and some ids might not match
Po1soNNN said:
Try to delete that data/local/juopunutbear folder. Might still have data from your last phone and some ids might not match
Click to expand...
Click to collapse
That was a good thought...a really good one.
The solution I came up with was to upgrade to the newest ICS leak (and all the pain that took to get there) then it went right to where it should have.
Thanks for the replies!
Try the wubi. It's seriously like installing a program. It doesn't go ontop of anything and can just be uninstalled whenever.
Sent from my ADR6425LVW using Tapatalk 2
K I'm using boot manager to install a cm9 Rom and it keeps failing at creating boot.img. I don't know what I'm doing wrong since I've herd of others installing cm9 roms sucessfully using boot manager. Maybe it's something in my settings? Tried making a thread at init2winit forums but have not gotten any response over there. Anyone here willing to help me out? I would greatly appreciate it.
Sent from my ADR6425LVW using Tapatalk 2
that usually means you dont have enough space
Thanks for the advice. I did check my SD storage and it said that I only had 1.16GBs left. So I thought that this could be true I suppose. So I switched to int. Storage as the install location(which I have 9.67GBs available on) and its causing my phone to lock up and freeze. Happened right at the part "extracting Rom please wait..." Weird...
Sent from my ADR6425LVW using Tapatalk 2
boot manager doesnt surport rexound officially，maybe thats the final answer. i encounterred the same issue too，but when i reinstall the app，it works just fine.
Sent from my ADR6425LVW using xda premium
anubis2k3 said:
Thanks for the advice. I did check my SD storage and it said that I only had 1.16GBs left. So I thought that this could be true I suppose. So I switched to int. Storage as the install location(which I have 9.67GBs available on) and its causing my phone to lock up and freeze. Happened right at the part "extracting Rom please wait..." Weird...
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Remember to disable logging in Superuser. That also causes some major issues. Just open superuser hit settings icon, and where it says logging set it to off. You should have much better luck that way
Cool, I will try that. I've uninstalled and reinstalled multiple times, with no luck. I'm interested though. What do you guys have setup in settings?
Sent from my ADR6425LVW using Tapatalk 2
live2die said:
boot manager doesnt surport rexound officially，maybe thats the final answer. i encounterred the same issue too，but when i reinstall the app，it works just fine.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
The Rezound is supported by bootmanager.
I've never been able to get boot manager to work correctly since I've started using it back on my dinc2. Had issues installing some roms on that phone too. Which is why I think my problem may be the settings I am using. Is there specific settings I need to use for the rezound?
EDIT: After I changed the settings SU I tried again at work and it froze still and even rebooted during the install.
Sent from my ADR6425LVW using Tapatalk 2
Ok, so I finally got cm9 roms to install correctly and now when I try to boot to them it just shows the splash screen for a couple seconds and my display turns off and it never boots. I've tried with kang and paranoid with the same results. I've tried going into recovery and manually flashing the update zip for rom 1, didnt work. Can't think of what could be the problem....
Sent from a galaxy far..far..away....
anubis2k3 said:
Ok, so I finally got cm9 roms to install correctly and now when I try to boot to them it just shows the splash screen for a couple seconds and my display turns off and it never boots. I've tried with kang and paranoid with the same results. I've tried going into recovery and manually flashing the update zip for rom 1, didnt work. Can't think of what could be the problem....
Sent from a galaxy far..far..away....
Click to expand...
Click to collapse
Doesnt look like anyone has asked you this, but are you S-Off?? You need to be S-off for this to work. Also make sure when installing you wipe system/data/cache. You should be able to use the ext.4/2 either one will work. I use the ext.4 since it installs faster....alot faster.
dalvear88 said:
Doesnt look like anyone has asked you this, but are you S-Off?? You need to be S-off for this to work. Also make sure when installing you wipe system/data/cache. You should be able to use the ext.4/2 either one will work. I use the ext.4 since it installs faster....alot faster.
Click to expand...
Click to collapse
He can be HTC unlocked and s-on it will still work bootmanager still hasn't updated since the rezound got s-off... His problem sound like the boot.img does not have the right kernel installed or something
Sent from my Dinc... I mean Rezound
yojoe600 said:
He can be HTC unlocked and s-on it will still work bootmanager still hasn't updated since the rezound got s-off... His problem sound like the boot.img does not have the right kernel installed or something
Sent from my Dinc... I mean Rezound
Click to expand...
Click to collapse
only mentioning that because in the instructions for the app. If he doesnt have to be S-Off then thats strange. Only thing i could suggest after that would be redownload ROM and check MD5
dalvear88 said:
only mentioning that because in the instructions for the app. If he doesnt have to be S-Off then thats strange. Only thing i could suggest after that would be redownload ROM and check MD5
Click to expand...
Click to collapse
i understand... he could probably do a dirty install of the same rom over top and make sure it has a boot.img in the zip that is not in any of the folders
Hello all
I was trying to get S-OFF, but my phone is not being recognized as online in ADB. I'm almost positive that I have the correct drivers, etc installed because I had no problem rooting it/being recognized in fastboot. But when I do ' adb devices ' it shows the phone, but says offline. I've done kill server, start server... I've updated everything in the sdk... Debugging is on... I'm completely lost and don't know what to do.
Thanks
What happens when you type a command like "adb reboot recovery" (without quotation marks)?
Sent from my EVO using xda premium
FinZ28 said:
What happens when you type a command like "adb reboot recovery" (without quotation marks)?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Before you responded, I manually rebooted to recovery to make a back up, then rebooted back to system. Now when I do "adb devices" it shows the device and says "device", is this what I'm looking for?
Also, I did the "adb reboot recovery" and noting happens.... The cursor moves to next line and just blinks. Nothing more. The phone doesn't reboot.
Thanks
It should output the device serial number when you type "adb devices".
Sent from my EVO using xda premium
FinZ28 said:
It should output the device serial number when you type "adb devices".
Sent from my EVO using xda premium
Click to expand...
Click to collapse
When I type "adb devices", I get
Code:
List of devices attached
HT25MS402628 offline
When I type "adb reboot recovery", nothing happens.
Strange. I've never seen the offline message in ADB before
You are booted into your ROM when trying to run ADB, correct?
Sent from my EVO using xda premium
FinZ28 said:
Strange. I've never seen the offline message in ADB before
You are booted into your ROM when trying to run ADB, correct?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Download HTC sync or pdanet drivers and you should be golden
Sent from my HTCONE using xda app-developers app
Thanks for the help everyone
I finally got it working; the problem was (apparently) the ROM... I was using RageLTE, but I restored a backup of Stock w/Goodies and everything was fine.
Unfortunately, It looks like my firmware is too new(?) and I can't use LazyPanda, and DirtyRancun has dropped support for Windows 8/64, so I guess I'll have to try the Live CD route....
Now im understanding, I have the same problem with Rage. I think i posted somewhere in that thtead. Didnt expierience it on any otber sense rom.
bjb_nyj101 said:
Thanks for the help everyone
I finally got it working; the problem was (apparently) the ROM... I was using RageLTE, but I restored a backup of Stock w/Goodies and everything was fine.
Unfortunately, It looks like my firmware is too new(?) and I can't use LazyPanda, and DirtyRancun has dropped support for Windows 8/64, so I guess I'll have to try the Live CD route....
Click to expand...
Click to collapse
What are u on? Try facepalm s-off yet?
scttydb411 said:
What are u on? Try facepalm s-off yet?
Click to expand...
Click to collapse
Hes on Rage Rom, its a known issue. Rom specific. I had the exact same issue with that rom
*Information IS the most dangerous weapon of all*
Thanks for the help everyone. Yeah, Rage was the problem, so I flashed back to Stock w Goodies and used dirty racun thru an ubuntu live CD. Finally s-off and running cm10.1!!
thanks for this thread. I was having the same issue my device was reading HT251W3005.... offline and it just so happen that I was running the Rage XL rom.
I guess search does work
Update Your Android
I was having this same problem with Cyanogenmod 10.1 (a.k.a. JellyBean 4.2.2). I figured out that I had an older install of the Android SDK. I updated it, then unplugged and replugged my USB cable. The device prompted me with something like "is it okay to accept ADB from this computer?" I told it yes and now I can see my device in adb devices output again.
i have the same problem
tried but nothing happened
i guess i have problem in rom
So as you all know the sense 5 update just came out today, which is great! Except for me... I've tried installing the update 2 times and it downloads perfectly fine. Then I click install now and it boots into recovery. It says "installing updates from Verizon wireless" or something like that. It gets half way through the bar and then quits out and goes to the little picture of a phone and the red triangle with the exclamation point in it right above the little phone. I have tried waiting to see if anything happens and then phone just shuts down and reboots into sense 4+. I am running stock recovery(just flashed back from twrp using .torrented's recovery) and I am moonshined. Any help would be appreciated very much.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Oh also as a little bit more information when the phone starts back up it gives me an error 410
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Another update. Just found out that after I updated it to the 2.08 kernel I lost my root. Yet my hboot still says tampered and unlocked. I'm assuming flashing the stock hboot will fix?
Sent from my HTC6435LVW using XDA Premium 4 mobile app
U should have waited for the ota update and rooted. Someone will releash in few months.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
xxdeathshadowxx9 said:
Oh also as a little bit more information when the phone starts back up it gives me an error 410
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think error 410 means something it's looking for is missing, could be the modified hboot. Try the stock hboot.
Use this to flash the stock hboot then go back into recovery and see if the update finishes the install.
http://forum.xda-developers.com/showthread.php?t=2219175
I am also having trouble updating. I was on a sense 5 ROM, then recovered to my stock ROM once I heard the update was out. I did all of the OTA updates, and the final one caused my phone to freeze at the HTC loading screen when the phone is turning on. Can someone help?
JJS714 said:
I am also having trouble updating. I was on a sense 5 ROM, then recovered to my stock ROM once I heard the update was out. I did all of the OTA updates, and the final one caused my phone to freeze at the HTC loading screen when the phone is turning on. Can someone help?
Click to expand...
Click to collapse
Are you on he stock recovery and hboot? If not try the link in my post above yours.
orangechoochoo said:
Are you on he stock recovery and hboot? If not try the link in my post above yours.
Click to expand...
Click to collapse
its keeps saying my device is not recognized...
JJS714 said:
its keeps saying my device is not recognized...
Click to expand...
Click to collapse
Update your drivers and sdk.
orangechoochoo said:
Update your drivers and sdk.
Click to expand...
Click to collapse
I'm pretty sure I have the newest SDK, and I could just install the drivers from that DROID DNA toolbox right?
JJS714 said:
I'm pretty sure I have the newest SDK, and I could just install the drivers from that DROID DNA toolbox right?
Click to expand...
Click to collapse
I believe you can, I'm not sure if the drivers in that app are the most current but it won't hurt to try.
Do you have USB debugging on? Also try a different USB port and/or USB cord.
orangechoochoo said:
I believe you can, I'm not sure if the drivers in that app are the most current but it won't hurt to try.
Do you have USB debugging on? Also try a different USB port and/or USB cord.
Click to expand...
Click to collapse
I tried that. For some reason the drivers don't seem to be installing. The thing is it recognizes my phone when im in android but not when I am in hboot
Use fast boot instead.
I'm sorry that's what I meant. In the toolbox I go to flash hboot, base 2.06, and then it says waiting for device. Flashboot USB shows up on my phone, but it says Windows was unable to recognize device because it malfunctioned the last time it was plugged in.
Restart the computer.
I have multiple times.. this is extremely frustrating
What is your computer's OS?
Windows 8.1
Those have been troublesome. Is that the same computer you used to s-off?
Try a Windows 7 computer.
Yes this is the same computer I used to get S-off. Just connected to a different computer (still windows 8) and I still got the message "USB device not recognized. The last USB device you connected to this computer malfunctioned, and Windows does not recognize it."