Tried out both these sets of instructions:
http://androidadvices.com/root-motorola-atrix-4g-45141-gingerbread-236-firmware/2/
http://www.androidauthority.com/atrix-4g-android-2-3-6-firmware-4-5-141-root-63533/
None of them since I can't even get past step one with the command lines. The command prompt won't recognize either saying "[name] is not recognized as an internal or external command, operable program, or batch file.
When I rooted while I was using 2.3.4, I had no issues doing it manually this way. I'm at my wits end. Don't know if it's a problem on my end or just the result of Motorola intentionally trying to make it hard to root and unlock this phone(apparently rooting also voids the warranty with them).
http://www.android-advice.com/2012/root-the-motorola-atrix-4g-running-4-5-141/
Thanks. Those are the same instructions in the first link though. Anyways. I managed to get past the first step by simply going to the folder and holding down shift and right clicking to get the command prompt to open the file from that location. Don't know why it wouldn't work the other way. After that I entered
moto-fastboot.exe flash preinstall preinstall.img
Click to expand...
Click to collapse
Now it's just stuck saying < waiting for device > which could mean it's a problem with the drivers. I did install the usb drivers from here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Don't know if there's a step I'm missing from that or if I have to do something manually form there since I went into the device manager and my computer couldn't detect anything for them so I assume they're up to date. Let me know if you if you need me to be more specific about something.
octahedron said:
Thanks. Those are the same instructions in the first link though. Anyways. I managed to get past the first step by simply going to the folder and holding down shift and right clicking to get the command prompt to open the file from that location. Don't know why it wouldn't work the other way. After that I entered
Now it's just stuck saying < waiting for device > which could mean it's a problem with the drivers. I did install the usb drivers from here:
http://www.motorola.com/Support/US-...tware_and_Drivers/USB-and-PC-Charging-Drivers
Don't know if there's a step I'm missing from that or if I have to do something manually form there since I went into the device manager and my computer couldn't detect anything for them so I assume they're up to date. Let me know if you if you need me to be more specific about something.
Click to expand...
Click to collapse
Did you try just fastboot instead of moto-fastboot? I had to use fastboot the other day and that held me up. But if its waiting for devices then it possibly is a driver issue. Im on the xda app so going to the link you provided wont work for me. Trying uninstalling and reinstalling the drivers.
Yeah I just did fastboot. Didn't even know if there was a moto-fastboot. How do I uninstall the drivers? I went through my applications but couldn't find them on my computer.
octahedron said:
Yeah I just did fastboot. Didn't even know if there was a moto-fastboot. How do I uninstall the drivers? I went through my applications but couldn't find them on my computer.
Click to expand...
Click to collapse
Go to device management of the computer and under usb should be your phone (when plugged in). If you aren't seeing it, then the drivers didn't install correctly. I can't remember where I got my drivers from to point you in the direction for that.
Alright thanks so far. It says the drivers aren't installed when I look them up in the manager. Don't know what I'm doing wrong, but if you could post the link when you get the chance then that would be helpful.
Just to clarify the one I'm referring to is "Motorola ADB Interface". "MB860" has everything current on it.
octahedron said:
Alright thanks so far. It says the drivers aren't installed when I look them up in the manager. Don't know what I'm doing wrong, but if you could post the link when you get the chance then that would be helpful.
Click to expand...
Click to collapse
When I get on my computer, ill see if I still have all the drivers that I dl. If so will ul to dropbox and post.
Ok this is what I have. Don't know what is what so included what I've got.
http://db.tt/jKixEKQL
http://db.tt/QmpO0ZUx
http://db.tt/CEu1k5q5
The description will pop up with each download. Hope it helps.
Thanks for the help!
I went back to an old bookmark I had when I rooted with 2.3.4 and found drivers. For some reason the motohelper link in my second post in this topic was not helpful. Here's a link for future reference in case anyone needs it:
http://db.tt/XHjBBnGh
I got my phone rooted again and now that I know that works I'll probably go ahead and try unlocking my bootloader to install cm7
Related
I did a search and it doesnt seem like anyone else had my problem. Basically, I'm on stock ICS with S-On, unlocked. I saw that the S-Off method now supports ICS and decided to give it a try.
I have all HTC drivers installed, downloaded jbear, extracted it to a directory all by itself, ran as admin..
All is going fine until my phone reboots to the green arrow screen. Then it just waits for the device, except it cant find my phone. I get an error message asking me to check my adb and fastboot drivers.
If I have the HTC drivers installed, doesn't that automatically give me the adb and fastboot drivers?
I've tried on 2 computers now, and still no luck. I've been flashing ICS all day. Help!
no, you need to have Android Development kit.. or w/e its called lol, I forgot its name..
either way, just get it from here:
http://developer.android.com/sdk/index.html
xologist said:
no, you need to have Android Development kit.. or w/e its called lol, I forgot its name..
either way, just get it from here:
http://developer.android.com/sdk/index.html
Click to expand...
Click to collapse
So I just download it, install it, and then I can attempt S-off again?
Anything special I need to do?
FINALLY got it to work. This was a crap shoot for me. Basically, what was happening was that I get stuck on the green arrow screen because Windows refused to recognize my phone as a phone ONLY ON THAT SCREEN, so my device manager didn't have an 'Android Phone' device. What I did to get it to recognize my phone was to relock my phone in fastboot, and then unlock it again in fastboot. And poof! My phone was recognized as an Android Phone on the green arrow screen. Got S-Off on 1st try
Thread can now be closed.
Hello XDA-Developers,
I've been a reader here for awhile now learning things about the android development for my devices and used many of your all members TUTs, but now i have came across a big issue that has broke my phone and need assistance getting it back online to be used with my carrier again. Below I'll explain my situation of what happen and what I need to be done so I can use the phone again or least get it back to factory stock so I can get a new phone... I will also offer someone $5-10 via PayPal for the assistance if you can help me get my phone back to the condition needed.
To start it off, I purchased a phone off a guy on craigslist, a AT&T HTC One M7 (Model: PN07120), when I purchased the device it was unlocked so I could use it on my carrier that was the reason I purchased it because I'm with T-Mobile. When I purchased the phone i went to setup the device to my needs and requirements and after two days of having the device, I noticed that the phone still had the previous owners information stored and was setup based on him, so because I didnt know the phone was rooted or anything, I googled how to factory reset my phone, so that way I could set it up to my wants, and requirements and below I'll explain the steps i'm at and what it is doing...
1. Searched google for the how-to method to factory reset my phone...
2. Went to 'Settings App', Backup & Restore, Reset Phone, Erase everything, Selected OK.
3. Followed the steps, phone rebooted..
4. Loaded up to the HTC (green logo) screen and stayed there...
5. Waited a few moments, phone never powered 100% back online just stayed at the HTC welcome logo when you first power phone back on.
6. So then I did the Boot Menu steps, (Hold Powerkey + Volume Down) to get into the boot menu,
7. When I got there it loaded to the boot manager window and I clicked FASTBOOT
8. Loaded new menu/logo "twrp" logo, then went to a menu "team win recovery project v2.6.3.3" with the list of options: INSTALL/WIPE/Backup/Restore/Mount/Settings/Advanced/Reboot.
9. I went to reboot to try to least get the phone booted, then when I was in the option to reboot, it gave me the warning of "No OS Installed", Continue without OS?"
10A. If I selected yes, it told me Install SuperSU, for root, otherwise phone wont be rooted.
10A1. I tried doing INSTALL SUPERSU did nothing..
10B. Did without installing SUPERSU and did nothing too, just when I boot comes back to this same menu Team Win Recovery Project.
So it seems I bricked my device as what everyone calls it to what I believe, I am unsure though or unsure how to fix this. I need to get the device either back to factory resetted to like the device comes out the box, so that I can use it, or what to do to get it back rooted successfully and working to be able to use the phone like i could at first.
I tried contacting the buyer but hes ignoring me now that I told him he told me the device wasnt rooted but the device was rooted and i seemed to have a major problem happen trying to restore the phone to factory defaults to set it up to my requirements...
My concerns and want is..
- My Carrier is T-Mobile USA LTE - So, I would have to get the device to stay UNLOCKED so I can still use the device on my carrier: T-Mobile, as it is a AT&T HTC One M7 Unlocked (Was working fine on my T-Mobile Sim prior to me trying to factory reset, besides the phone was named to the original owner and had all his settings and customizations that i didnt like or want.
- I NEED to get the phone back in a working condition. So please I'm really asking for your help I tried searching a couple articles here but couldnt find anything related to my situation.. This is why I am offering a payment for someone to be able to successfully restore my device back to working condition. Please help me!
- NOTE: When plugged up to the computer via USB Cord it did not connect or anything also. I also did not perform a backup because I didnt need any information that was currently on the device because it was the content and settings of the original owner i bought it from so I wanted to clear it all and set it up to my own.
- Overall, my phone is messed up because I tried factory resetting the device not knowing it was rooted, during the process found out it was rooted and now seem to have a bricked phone and need to know how i can fix it, and get android OS back installed, as it tells me there is NO OS installed when I reboot or try booting the device, and it remains at the HTC Bootlogo when powering it on without holding the power + volume down key to access a boot menu to perform a reset, install, etc, Like I mentioned I just want to restore my phone back to working condition even if that means to have to root the device again, etc. All I'm asking for is someone to either help me with each step or to write a step by step what I would need to do to recover and restore my phone.
Phone: HTC one m7 (AT&T)
Computer; Windows
Thank you,
PM or respond here.
Don't worry you device is not bricked...
Google Android Revolution HD 41.0 for HTC one. Download that ROM.
Second you will have to install android SDK to be able to access adb.exe and fastboot.exe...
Now once you installed the SDK move the ROM ARHD to where adb.exe is located.
run command prompt "CMD" from your computer until you are in the folder where you have you adb.exe
Now on your phone get into recovery TWRP and select advance, in advance the is an option called adb sideload click on it and at the bottom slide the button to initiate that mode.
Back to the computer in which you should be in CMD type command "adb devices" and make sure your device shows up. After successfully seen your device there type "adb sideload file-rom.zip and press enter, make sure the file-rom.zip is the exact name of the ROM you are trying to push into the phone.
Sent from my HTC One using xda app-developers app
TopoX84 said:
Don't worry you device is not bricked...
Google Android Revolution HD 41.0 for HTC one. Download that ROM.
Second you will have to install android SDK to be able to access adb.exe and fastboot.exe...
Now once you installed the SDK move the ROM ARHD to where adb.exe is located.
run command prompt "CMD" from your computer until you are in the folder where you have you adb.exe
Now on your phone get into recovery TWRP and select advance, in advance the is an option called adb sideload click on it and at the bottom slide the button to initiate that mode.
Back to the computer in which you should be in CMD type command "adb devices" and make sure your device shows up. After successfully seen your device there type "adb sideload file-rom.zip and press enter, make sure the file-rom.zip is the exact name of the ROM you are trying to push into the phone.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Where can I find this stuff I need to download? I tried doing a search and got a different version, Android Revolution HD 51.0, but could you please link me to the stuff I need to download on my computer, etc?
Okay I've done the steps you've instructed to me and I'm stuck at after launching the sideload feature on my phone; then going back to the computer and running 'adb devices' and under "List of Attached Devices" there isn't anything listed yet, and the phone says "Starting ADB sideload feature..." is the last line, I'm stuck with what to do...
I downloaded android SDK
downloaded the ROM
moved the ROM to the sdk folder where adb.exe and fastboot.exe are
launched adb sideload feature under advanced on mobile device
went back to the computer and ran, 'adb devices', and list of attached devices is none...
so I'm back at being stuck.
djay1127 said:
Hey again,
Okay I downloaded the android SDK, and I'm downloading the correct ROM now to install. Only questions I have for you is the following...
1) You said to move the ROM to where adb.exe is at... What do you mean by this? I don't have that file on my computer...
Where do I move it too once I have the android SDK downloaded and the rom downloaded...
Click to expand...
Click to collapse
Follow this video
http://android.mobilenicheapps.com/tag/android-sdk-installation
Sent from my HTC One using xda app-developers app
TopoX84 said:
Follow this video
[/url]
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I watched the video and got all of that working and checked based on the video and made sure all was installed, now i'm just still stuck at where you instructed me to do 'adb devices' after launching adb sideload under advanced on mobile, i did that, and i get
List of devices attached...
<nothing>
Then goes back to where I can type another command...
The phone itself screen is on the adb sideload feature, and in the textbox thing, shows the following
Updating partition details...
Starting ADB sideload feature...
then has a Cancel button underneath and then a loading bar underneath that... am I doing something wrong? or missing something?
Do I need to have the USB cord plugged into phone/computer also to do this? or dont have it plugged up...
djay1127 said:
Do I need to have the USB cord plugged into phone/computer also to do this? or dont have it plugged up...
Click to expand...
Click to collapse
In order to do a sideload you have to have the cord plugged to both the phone and the computer...
Sent from my HTC One using xda app-developers app
TopoX84 said:
In order to do a sideload you have to have the cord plugged to both the phone and the computer...
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I tried that and still get no devices attached.
djay1127 said:
I tried that and still get no devices attached.
Click to expand...
Click to collapse
Do you have HTC manager installed? If so uninstall it but leave the HTC drivers.
Which windows you are using as well ?
Sent from my HTC One using xda app-developers app
TopoX84 said:
Do you have HTC manager installed? If so uninstall it but leave the HTC drivers.
Which windows you are using as well ?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
HTC Manager = no
drivers = i dont know.
Note: I never had the phone plugged up to my computer before when it was working. I had just purchased the phone off of craigslist and the guy didnt inform me it was rooted or anything just that it was unlocked and worked on tmobile and when i got it it had all his info on it so i factory resetted it and it messed everything up as you can see.
So, I dont believe i have anything drivers installed and i know when i plug it up, there are 4 things windows says installing/etc, and only the first one says completed the other 3 fail.
I am using Windows 7.
You help me get my phone back in working condition I will personally paypal you $20.
djay1127 said:
HTC Manager = no
drivers = i dont know.
Note: I never had the phone plugged up to my computer before when it was working. I had just purchased the phone off of craigslist and the guy didnt inform me it was rooted or anything just that it was unlocked and worked on tmobile and when i got it it had all his info on it so i factory resetted it and it messed everything up as you can see.
So, I dont believe i have anything drivers installed and i know when i plug it up, there are 4 things windows says installing/etc, and only the first one says completed the other 3 fail.
I am using Windows 7.
You help me get my phone back in working condition I will personally paypal you $20.
Click to expand...
Click to collapse
Go to this website and download the HTC sync manager
http://www.htc.com/www/software/htc-sync-manager/
Once installed go to control panel > programs and uninstall a program... Look for the HTC sync manager and uninstall it, but leave the htc drivers alone.
Connect the HTC one to the computer and wait for the drivers to install automatically... After they are successfully installed try to run the CMD adb command adb devices
Sent from my HTC One using xda app-developers app
TopoX84 said:
Do you have HTC manager installed? If so uninstall it but leave the HTC drivers.
Which windows you are using as well ?
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Okay so I've done all that and after doing what you said, plugging the phone up to the computer everything installs besides the HTC MTP driver when the phone is plugged in. I still tried doing adb devices from cmd prompt to check and that didnt work still, no devices listed.
I get this error under the driver:
This device cannot start. (Code 10)
djay1127 said:
I get this error under the driver:
This device cannot start. (Code 10)
Click to expand...
Click to collapse
Based on what I've been reading that code error might be cause by a corrupted driver installed.
http://support.microsoft.com/kb/943104
Sent from my HTC One using xda app-developers app
TopoX84 said:
Based on what I've been reading that code error might be cause by a corrupted driver installed.
http://support.microsoft.com/kb/943104
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I answered your PM and awaiting for you to pop back up online... I also sent you a PM with some details and also wanted to let you know TV is installed.
djay1127 said:
I answered your PM and awaiting for you to pop back up online... I also sent you a PM with some details and also wanted to let you know TV is installed.
Click to expand...
Click to collapse
was a tough little driver... well the solution as we saw was that instead of trying to make recovery detect the drivers.... what needed to be done first was let fastboot detect drivers "android 1.0" and once that was done... the previous error was gone.
TopoX;
You know this guy right here is clutch in my book.... He actually walked me through step by step, customizing how i needed it, fixing everything, and getting it back up and even though we had to do alot of modifications on my computer-end, him with TeamViewer literally fixed my phone, upgraded my laptop, and got my phone running better then normal and actually showed me how to do everything and taught me things I didn't know how to do with these Android Phones.
I am now very happy and thankful of XDA-Developers for allowing me to get this assistance and for having a great community with members like TopoX who literally saved my ass and restored my phone back to working condition and fixed my laptop all together, even though I was a brand new member with hardly any posts and not really much background, anyone else wouldn't of wasted their time... but he helped and even was up until 3AM ish doing it with me to make sure I got it back to exactly how I wanted...
We had to get the HTC MTP Driver installed correctly which kept failing/getting code error 10 (Unable to start) which if you google the issue it seems ALOT of people get this issue, and we resolved it by fastbooting and letting it install Android 1.0 itself, then manually updating my pc with windows updates and getting rid of the junk to stop corrupting and failing the drivers needed, then getting everything needed to flash my phone and re-root the device getting everything back in a working condition, unlocked, got that done and now phone is working better then before...
I'm currently running Team Win Recovery Project, ARHDOne-61.0 Google Play Edition, Rooted, SuperUser and Unlocked.
I personally wanna thank TopoX for everything he did and dedicating his time to helping resolve the issue for me.
TopoX84 said:
was a tough little driver... well the solution as we saw was that instead of trying to make recovery detect the drivers.... what needed to be done first was let fastboot detect drivers "android 1.0" and once that was done... the previous error was gone.
Click to expand...
Click to collapse
Cool story bro. Seriously..... Cool story.
I love XDA.
If anyone is trying too get in contact with "djay1127", please contact me on this user, my original first account djay1127 I can no longer access the account as I set it up with my Google account, gplus login, and I can no longer access that email, it's closed out. So I created a new account with my main email account and username.
I plan to contact a admin after doing some searching to discuss getting my old account removed, and the posts and crap merged into this account instead...
Regards.
I can't for the life of me get adb to recognize my max. It's Verizon, H-boot 2.46. Trying to root and unlock. I've tried everything here....nothing. A little help please.
Only thing I can suggest, because it's happened to me, is to make sure you have the correct, most current device drivers loaded on your PC.
Sent from my HTC6525LVW using Tapatalk
they are correct up to date and most current.
HellRayzer said:
I can't for the life of me get adb to recognize my max. It's Verizon, H-boot 2.46. Trying to root and unlock. I've tried everything here....nothing. A little help please.
Click to expand...
Click to collapse
Are you unlocked, s-off, and rooted? Do you have developer options activated on your phone? Please explain what you´ve done up till now.
What happens when you type adb reboot. Does it start and not find it or come back with command not recognized?
Sent from my HTC6525LVW using xda app-developers app
i was having issues myself. then I found this thread and things worked again. http://forum.xda-developers.com/showthread.php?t=2588979
it doesn't find anything. I haven't been able to root s-off or anything because adb cant find my device. Do I need adb files in rumrunner folder on C drive to make it recognize it and work or what the hell am I doing wrong? I have rooted and s-offed every htc device I have ever owned...this one isn't working out. It's showing as a portable media player not android device. In the past I remember when I connected the usb I had the option to select media storage or connect as android.
HellRayzer said:
it doesn't find anything. I haven't been able to root s-off or anything because adb cant find my device. Do I need adb files in rumrunner folder on C drive to make it recognize it and work or what the hell am I doing wrong? I have rooted and s-offed every htc device I have ever owned...this one isn't working out. It's showing as a portable media player not android device. In the past I remember when I connected the usb I had the option to select media storage or connect as android.
Click to expand...
Click to collapse
my rumrunner folder was still in my downloads folder no where near my adb files and everything worked ok for me. also my Max shows up as a media device also but adb/fastboot still working fine. did you try to reinstall your adb with the link I provided in the above post, its the only thing that helped me when I was having pretty much the same problem as you.
you may also need to unlocked dev tools in your settings... have you done that yet
Where and how do you unlock developer tools...haven't found that under anything in the settings?
HellRayzer said:
Where and how do you unlock developer tools...haven't found that under anything in the settings?
Click to expand...
Click to collapse
Enter Settings, then scroll down to about... pick "Software Information" -- then "More" --- Then press the "Build" 8 times fast. You´ll then have access to the developer tools.
Well thanks for the help. still can't get anything to work, guess this will be the first device I've owned that will never be rooted unless I find something that tells me what to put where and what to do.
HellRayzer said:
Well thanks for the help. still can't get anything to work, guess this will be the first device I've owned that will never be rooted unless I find something that tells me what to put where and what to do.
Click to expand...
Click to collapse
When you type in adb devices, can you see your seriel number?
RayHeath said:
When you type in adb devices, can you see your seriel number?
Click to expand...
Click to collapse
no. it says list of devices, then it's blank.
HellRayzer said:
no. it says list of devices, then it's blank.
Click to expand...
Click to collapse
Ok, I´m not sure what you time zone is, but I can help you tomorrow. It´s 10pm here right now, and I´m gonna hit the hay soon. When you´re online tomorrow, pm me. I´ll log in, and we´ll start.
Hey relax bud, do me a favor and PM and I will help you out with everything and getting your phone to be recognized by dab and fast boot and make sure you properly s-off unlock and root if that's what you are trying to accomplish! Hit me up, I have nothing going on tonight so I can jump right in to it with you right away
HellRayzer said:
no. it says list of devices, then it's blank.
Click to expand...
Click to collapse
Have Win XP or server 2003?!?
This: http://forum.xda-developers.com/showthread.php?p=49045175
Don't know if you guys ever got this issue solved or not. I'm having the same issue S-on, cannot get adb devices command to recognize my t6spr for the life of me. on Hboot 2.46, it will detect the USB device malfunction if I put the device in fastboot mode, but thats about it. Device manager shows Unknown USB (Device Descriptor Request Failed). Tried the KB update for devices that fail enumeration on Windows 8.1 for x64 but the update package said my system is not affected so that never installed. Tried the alternative miniadb pakage previously mentioned but didnt seem to have an affect installing fastboot, adb, and drivers, across the system universally. Just not having any luck apparently. I guess I could just sell the phone Tampered and Unlocked haha with no fingerprint scanner functionality, flash ViperRom or some other stock look alike ROM. Was just really hoping to go back completely stock. At one point it time I was trying different PCs to see if it was just a system issue for me. Occasionally it seemed like if I let it sit in Fastboot AC it would eventually get detected and flip over to Fastboot USB long enough for me to push a couple commands to the phone. I have the right RUU but it dosent do me any good if the computer cant see the phone haha. Now no computer seems to recognize it. It all seemed to happen after I tried to S-Off the device with Firewater's method. Idk if I bricked something because it never worked or changed a CID or some other ID to where the USB isnt recognizable, but all I can get this phone to do is take an electric current from the USB, lol thats about it. I thought I had it fixed enough to where I knew what to do if i absolutely needed to get fastboot to recognize the phone but now, nothing.
Just a curiousity question here....a bad usb cable can produce this also...read through posts didnt see anyone trying a new cable...
ok so im having a few problems with my rooting process. one i have to manually put my device into fastboot since doing it threw my windows 7 CMD just seems to not work since it will say device offline. then once i do get to fastboot i run into my second problem. the recovery.img seems to be frozen during the sending process. in fact its still trying to send it to my device. my device is unloocked. what am i doing wrong? or am i missing something? i followed another titorial on here and im still stuck. mostly on the recovery.img part. it just doesnt seem to send. just sits there saying its sending it.please help if you can.
says S-On . how do i gewt it to say s-off?
LordXombie said:
ok so im having a few problems with my rooting process. one i have to manually put my device into fastboot since doing it threw my windows 7 CMD just seems to not work since it will say device offline. then once i do get to fastboot i run into my second problem. the recovery.img seems to be frozen during the sending process. in fact its still trying to send it to my device. my device is unloocked. what am i doing wrong? or am i missing something? i followed another titorial on here and im still stuck. mostly on the recovery.img part. it just doesnt seem to send. just sits there saying its sending it.please help if you can.
Click to expand...
Click to collapse
Sounds like you need to update to the latest version of ADB/FASTBOOT the "device offline" is usually due to an incomatible older version of ADB. Get the latest version on your PC then make sure that ADB is working before trying fastboot.
LordXombie said:
says S-On . how do i gewt it to say s-off?
Click to expand...
Click to collapse
We don't have an S-off solution for this phone yet but it is not required for root, although you will need to flash jmz's insecure kernel for changes to "/system" to stick after reboot even when rooted,
MiniBlu
i cant seem to get adb to update.
LordXombie said:
i cant seem to get adb to update.
Click to expand...
Click to collapse
Install the latest on your PC from here http://forum.xda-developers.com/showthread.php?t=2317790
MiniBlu
ok so i did that and it is still saying device offline. Now im trying a program i found on here. desire_610_root_v3.exe it was able to reboot the device into bootloader then it brought it into fastboot menu then it started to send the file then it just snags there. the file just keeps saying its sending. i dont know whats going on.
ok it still not getting teh recovery.img on the phone. it just keeps sending it with out doing anything..
ok so this htc is giving me way mopre problems then the htc one vx. i really need help. and now im kind of lost what to do. Currently all i have done is unlocked the device.
ADB says my device is there. Threw cmd i can't get it to fastboot using adb reboot fastboot. all it does it reboot teh device, it wont go to bootloader. I do have bootloader unlocked. when i go and make my device go to bootloader manually i try to do the fastboot flash recovery recovery.img it starts to send the file then fails. unknown error. what am i doing wrong?
ok so it seems changing my usb cord fixed it. i got the file sent and rooted my device. thanks for the help MiniBlu gave me !
LordXombie said:
ok so it seems changing my usb cord fixed it. i got the file sent and rooted my device. thanks for the help MiniBlu gave me !
Click to expand...
Click to collapse
That's info that more people should have. The right usb cord can be difference between failure & success. I remember I went through 6 different usb cables jailbreaking my atv2.
For this phone, however, I just used the one that came with it. But I found the automated process to be sticky (not a tech term) it seemed to freeze a lot during the process.
I wound up plugging and replugging the usb when it froze.
It rooted my phone, installed twrp but needed to flash jmz kernel manually. The root tool works though. And to be honest, until I read this I didn't even think that a different cable might fix those issues in the automated process.
The other night for fun I rooted an old kindle hd and I needed to unplug and replug to get that to work. I was using the same cable that came with HTC desire.
***Anyone ever use a fastboot cable? Apparently u need one to install a 2nd boot loader on kindle hd and I'm wondering if that type of cable would resolve issues like this? That's a question not a go ahead to try it. I know very little about that and don't know if it could possibly cause more serious issues. They're cheap on eBay and I'm getting one for the kfhd.
A few days ago my watch restarted on it's own and never got past the startup..which isn't that unusual, it'd happened a few times. No big deal just reset it with the button on the back. I tried that and again an endless loop. I tried searching for any help in this situation and the only lead I found was to reset and power it down through the boot menu and let it sit for a few minutes...but didn't matter. I've wiped and reset from the boot menu, hoping it might do something to get it past the startup, but no luck yet. I didn't open up the developer options and unlock anything...so I don't believe I could try anything from the computer right? Is there any other recourse to take or am I completely hosed?
JRSly said:
A few days ago my watch restarted on it's own and never got past the startup..which isn't that unusual, it'd happened a few times. No big deal just reset it with the button on the back. I tried that and again an endless loop. I tried searching for any help in this situation and the only lead I found was to reset and power it down through the boot menu and let it sit for a few minutes...but didn't matter. I've wiped and reset from the boot menu, hoping it might do something to get it past the startup, but no luck yet. I didn't open up the developer options and unlock anything...so I don't believe I could try anything from the computer right? Is there any other recourse to take or am I completely hosed?
Click to expand...
Click to collapse
You don't need developer options to do "fun" things from the boot menu. Just an unlocked bootloader.
I have a TWRP backup somewhere, so if you have a borked system, you can always flash (or better yet, boot) TWRP (make a backup of your broken), push the backup file folder to your watch (without overwriting the broken backup), and then restore mine.
Last thing to do is a factory reset to clean up any left over garbage. Hope this helps.
But isn't Developer Options necessary to allow that? It lets you turn on ADB Debugging which would then let you get on the computer and unlock the bootloader?
Or is there an alternate way to go about things...can I unlock the bootloader from the boot menu? I've only rooted a couple phones, with a lot of careful reading and reviewing of these forums...I'm not very knowledgeable.
JRSly said:
But isn't Developer Options necessary to allow that? It lets you turn on ADB Debugging which would then let you get on the computer and unlock the bootloader?
Or is there an alternate way to go about things...can I unlock the bootloader from the boot menu? I've only rooted a couple phones, with a lot of careful reading and reviewing of these forums...I'm not very knowledgeable.
Click to expand...
Click to collapse
Fastboot is independent of ADB, so you can unlock the bootloader from the boot menu. That is the way to unlock bootloader 90+% of the time.
Just need to issue these commands (like you would ADB) :
fastboot devices
fastboot oem unlock
...and then complete the on-screen (watch) confirmation. Hope this helps.
Sent from my ASUS_Z00AD
OfficerJimLahey said:
Fastboot is independent of ADB, so you can unlock the bootloader from the boot menu. That is the way to unlock bootloader 90+% of the time.
Just need to issue these commands (like you would ADB) :
fastboot devices
fastboot oem unlock
...and then complete the on-screen (watch) confirmation. Hope this helps.
Sent from my ASUS_Z00AD
Click to expand...
Click to collapse
All right, my new problem is that the computer doesn't recognize the watch. When I plug it in it only appears as an unknown device and there's an error about the device having malfunctioned. Trying to install drivers despite the error leads nowhere, Windows says that the drivers present on the computer are up-to-date. So with it being an unknown device, I can't communicate with the watch from the command prompt.
Remove the drivers from Device Manager (check delete driver), connect your device again to the computer then reinstall the drivers.
MihaiSG said:
Remove the drivers from Device Manager (check delete driver), connect your device again to the computer then reinstall the drivers.
Click to expand...
Click to collapse
No luck, I'd tried that a couple times before...just no progress, still sees it as an unknown device and trying to force install the drivers does nothing. It says the existing drivers are up to date.
I'm getting more and more discouraged. I can't seem to make any progress. I'm looking into sending it away for repair even though, of course, it's about two months out of the warranty.
You are not removing the drivers correctly, make sure that you have this option checked and try again:
http://www.sevenforums.com/tutorials/77614-device-manager-hidden-devices.html
MihaiSG said:
You are not removing the drivers correctly, make sure that you have this option checked and try again:
http://www.sevenforums.com/tutorials/77614-device-manager-hidden-devices.html
Click to expand...
Click to collapse
Anything more I should be doing? Everything mentioning Android or ADB is removed. I'd never plugged the watch in before and installed drivers, so there's nothing from the watch to delete. But still the same thing, Windows only sees it as a Unknwon Device under USB controllers and sees no need to update drivers when I try, since it doesn't seem to see it as a watch or Android device of any sort.
Are you sure that you have installed the correct drivers? What is the hardware id?
MihaiSG said:
You are not removing the drivers correctly, make sure that you have this option checked and try again:
http://www.sevenforums.com/tutorials/77614-device-manager-hidden-devices.html
Click to expand...
Click to collapse
MihaiSG said:
Are you sure that you have installed the correct drivers? What is the hardware id?
Click to expand...
Click to collapse
I think so? I'm far from an expert but I've messed with a handful of phones and tablets in the last five years and never had issues with drivers I didn't sort out fairly easily. I downloaded the official Google USB driver, I tried the LG Watch Tool which installs the Universal ADB driver.The LG Watch then finds no devices.
I'm a bit ignorant, what hardware ID do you refer to? Of the driver?
Of the device.
Here is a guide:
http://www.makeuseof.com/tag/how-to-find-unknown-device-drivers-by-their-vendor-device-id/
Can you post some screenshots from device manager?
MihaiSG said:
Of the device.
Here is a guide:
http://www.makeuseof.com/tag/how-to-find-unknown-device-drivers-by-their-vendor-device-id/
Can you post some screenshots from device manager?
Click to expand...
Click to collapse
Device Manager wasn't much help for finding the IDs, but I tried using USBDeview and it's reporting something as Android Bootloader Interface, which I'll have to assume is the watch. The vendor ID is 18D1 and the product ID is 4EE0. And here is a screen cap of the entry in the Device Manager that I've been seeing. If there's anything more specific in the device's properties that could be insightful, let me know.
Your device is seen as an unknown device. My only advice is to try on another PC your last working drivers and maybe it will work.