wdfowty said:
I'm having a few issues using my bootcamp partition for this (in Parallels), following eugene and king_fyo's tutorials, and was wondering what it would take to root my MyTouch3gS using osx?
I am semi-familiar with ADB, and I have made the loop.sh script, but i'm stuck at that point.
Here are my main questions:
-How to you get the loop to stop? I have to quit Terminal app to stop it.
-Any other things to know? Tips? Success stories? Tutorials maybe (or even a quick and dirty how-to?)
Thank you for your time, and for not flaming the newb
Click to expand...
Click to collapse
EDIT: SOLVED!
So, I'm waiting for my Nexus one to come in the mail, and I think to myself, "Why not give rooting the slide another go?"
Worked second try. How's that for random....
So, here's how I made it work...Dunno if it was 'luck of the draw', but here ya go anyways...Hope it helps someone!
1. Instead of turning off the phone normally, I rebooted straight into recovery, with the phone being on first.
Code:
./adb reboot recovery
2. While rebooting, MANUALLY search for devices as soon as you can type it in, repeating rapidly (This made the difference for me).
Code:
./adb devices
3. You should catch the device in offline mode right before the recovery screen. Unplug device for 5 seconds or so, then plug it back in.
Code:
./adb devices
List of devices attached
HT05MPS02279 recovery
4. You should see your device in recovery, then you're good to go. If not try again.
How to you get the loop to stop? I have to quit Terminal app to stop it.
Click to expand...
Click to collapse
No, simply hit <control> c from inside the Terminal app to break out of the shell script.
Any other things to know?
Click to expand...
Click to collapse
Not really, it may take you several tries to get this as it did for people using M$ Winblows. I tried it about 20 - 30 times on XP and never was successful. After switching to my mac, I got root on the 5th try!
My suggestion is to follow Eugene's guide, it worked great for me! If you have problems, post them here and myself or others will try to help you.
Good luck!
wdfowty said:
I'm having a few issues using my bootcamp partition for this (in Parallels), following eugene and king_fyo's tutorials, and was wondering what it would take to root my MyTouch3gS using osx?
I am semi-familiar with ADB, and I have made the loop.sh script, but i'm stuck at that point.
Here are my main questions:
-How to you get the loop to stop? I have to quit Terminal app to stop it.
-Any other things to know? Tips? Success stories? Tutorials maybe (or even a quick and dirty how-to?)
Thank you for your time, and for not flaming the newb
Click to expand...
Click to collapse
So I set up my camera to record myself rooting my phone using OSX and a couple friends walked into the room. I got distracted explaining what it was I was doing and didn't make the how to. If I have free time tomorrow afternoon I can make a how to vid. My girlfriend just got her slide yesterday and I believe she wants me to root it.
it's exactly the same doing it in Mac OSX as doing it in Windows except you don't have to worry about drivers. Make sure you get android SDK for Mac OSX and that you put it somewhere that is in your PATH variable.
But if you feel more comfortable doing it from Bootcamp Windows partition -- by all means do that.
Don't boot camp it... lol
I'll be posting a Mac OSX version of Eugene's Root Method shortly.
sk8rbebop, Fordude, stangri, Thanks for the quick replies! Wasn't expecting anything so soon!
I think I have tried to press CMD+C to stop the script, must have been my problem. lol.
@stangri What do you mean by PATH variable? I have the Android SDK installed in my home folder...
@sk8rbebop That's pretty funny . I'm going to have a go at it right now, I'll edit this post with my results.
edit: I don't know if this is right, but I stop the script when I see the device in offline mode. But when I unplug device, re-plug and run ./adb devices nothing shows up. The same happens if I don't unplug.
edit2: Still nothing. adb never recognizes device after I stop the loop.
I threw up a guide. Hope it helps.
Don't shut off the loop until something displays under the devices.
Re: Question: How to root MyTouch Slide using OSX?
When u connect the slide to your mac and type "adb devices", do you see your phone listed? Crucial first step before moving on.
To make things a little easier for me, I put the sdk tools folder in my path so I could issue adb commands in any directory I want to.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
@sk8rbebop Read the guide and i'm still stuck at the loop. I'm having the same issues as earlier, the device will show for a little bit but right before the recovery screen shows, it dissapears. I was stopping the script once I saw the device, before it "dissapeared". Stopping the script after it dissapears does the same...
BTW, I've noticed that I need to start the adb daemon before I run the loop in order for it to even see the device in the loop. Odd.
@Fordude Yes, if I run ./adb devices when the phone is on I get my serial number and it says "device".
edit: I found that I am running an out of date SDK revision, so I am updating to the newest (revision 6), lets see if that makes any difference...
edit 2: No dice. Lame. Oh well I guess...Try try again. My mac seems to be determined not to let this happen
update: So, I'm getting a nexus. Thanks all for your help, happy hacking!
SOLVED
post removed
Hey guys. Please forgive anything dumb I might say, and also that I've searched a bit for this, on google and on xda, but seem to be getting a bit confused. First, let me say, I rooted my evo months ago, using Unrevoked 3.21. I never really have had to use ADB for anything, I use terminal emulator or Root Explorer for anything I have needed to do. My friend just got an Evo today, and I'm assuming it will come with 3.70 software and hboot 2.1. She wants me to root it for her, which I will do, once I feel comfortable with the steps I need. I have followed ziktroniks thread of how to root the new hboot since it was called "like a boss" edition, and I feel like I shouldn't have a problem doing that. I can follow instructions pretty well. The problem I'm having is, since I rooted using Unrevoked 3.21, and I've never had to use ADB, I'm a little confused about what I need to do, and what drivers I need to install to get ADB working. I know that at the time I rooted, I installed Unrevoked hboot drivers on my computer. I downloaded the android SDK tools, but am having trouble getting it set up. When I try to run the installer, it says "android SDK relies on the Java SE Development Kit (JDK). Then it provides a link to the java website, and I downloaded and installed the JDK that it pointed me to. However, when I try to set up the android SDK, it brings me to same prompt, saying android SDK relies on Java SE Development Kit, and that i need to install it first, which I thought I already have. I'm sure it's something stupidly simple, and I feel embarassed that I haven't yet got ADB set up, but hey, I guess there's a first for everything. So if anyone could be so kind to help point me in the right direction to getting ADB set up, I'd be very gratefull for that. I've gone long enough without knowing how to use ADB, and I'd really like to get this ironed out.
My computer is running windows vista, 64 bit system, if that helps out at all.
Thanks in advance.
I just came over to check out your question from Myn's thread... I did not have the problem you mention when I set up ADB, so I cann't be of much use there.
I noticed you have WIN 64bit. You may have a hard time finding the drivers you will need for the computer to recognize your phone. If you end up needing them, PM me and I can throw them in dropbox and get a link for you. Good luck with everything.
Yeah, getting the 64 bit drivers might be a problem, but when you do it'll be easy if you remember this:
If you've used Terminal Emulator then ADB is demystified. Once you confirm the drivers are working, ADB is just Terminal Emulator on your computer.
I use Vista (I actually like it!), but I assume you have a Start Menu on W7...open it and at the bottom is the Start Search box. Type cmd and an old-style DOS prompt/box will come up. Once you've used the commands to log onto the phone (sorry I forgot them, but I'm sure they're in the directions, if not PM me and I'll look 'em up) that DOS box is exactly like Terminal Emulator.
And the rest should be easy to follow. It'll make you smile the first time the phone reboots after you issue a command on the 'puter, it did me.
Hope this helps...
[EDIT] here y'go...this is a good one...
http://forum.xda-developers.com/showthread.php?t=502010
Thanks for the quick responses guys, I've made some progress. I will post back in a few and let you know how I'm making out. Thanks again.
k2buckley said:
Hey guys. Please forgive anything dumb I might say, and also that I've searched a bit for this, on google and on xda, but seem to be getting a bit confused. First, let me say, I rooted my evo months ago, using Unrevoked 3.21. I never really have had to use ADB for anything, I use terminal emulator or Root Explorer for anything I have needed to do. My friend just got an Evo today, and I'm assuming it will come with 3.70 software and hboot 2.1. She wants me to root it for her, which I will do, once I feel comfortable with the steps I need. I have followed ziktroniks thread of how to root the new hboot since it was called "like a boss" edition, and I feel like I shouldn't have a problem doing that. I can follow instructions pretty well. The problem I'm having is, since I rooted using Unrevoked 3.21, and I've never had to use ADB, I'm a little confused about what I need to do, and what drivers I need to install to get ADB working. I know that at the time I rooted, I installed Unrevoked hboot drivers on my computer. I downloaded the android SDK tools, but am having trouble getting it set up. When I try to run the installer, it says "android SDK relies on the Java SE Development Kit (JDK). Then it provides a link to the java website, and I downloaded and installed the JDK that it pointed me to. However, when I try to set up the android SDK, it brings me to same prompt, saying android SDK relies on Java SE Development Kit, and that i need to install it first, which I thought I already have. I'm sure it's something stupidly simple, and I feel embarassed that I haven't yet got ADB set up, but hey, I guess there's a first for everything. So if anyone could be so kind to help point me in the right direction to getting ADB set up, I'd be very gratefull for that. I've gone long enough without knowing how to use ADB, and I'd really like to get this ironed out.
My computer is running windows vista, 64 bit system, if that helps out at all.
Thanks in advance.
Click to expand...
Click to collapse
I didn't use windows to root my evo, I used a mac, and I do all my java development on a debian linux box, but I think the problem may have to do with your computer using the wrong java by default. On mac and linux, this is controlled by the environmental variable $JAVA_HOME, on windows, I have to assume there is a similar variable, or registry entry - I am looking it up on google right now...
Here we go, I found it - try the directions on this page:
http://confluence.atlassian.com/display/DOC/Setting+the+JAVA_HOME+Variable+in+Windows
hopefully this helps
oh, one other thing, I noticed you said she has hboot 2.10, and I think "like a boss" technique is for hboot 2.02. I think for 2.10 you need to find a thread entitled something like "like wood on fire", or something - although I may be wrong, maybe they updated the "like a boss" thread to cover hboot 2.10 also. Just wanted to make sure you double-check.
Good luck.
Bleys43 said:
oh, one other thing, I noticed you said she has hboot 2.10, and I think "like a boss" technique is for hboot 2.02. I think for 2.10 you need to find a thread entitled something like "like wood on fire", or something - although I may be wrong, maybe they updated the "like a boss" thread to cover hboot 2.10 also. Just wanted to make sure you double-check.
Good luck.
Click to expand...
Click to collapse
Thanks for the heads up. Yea, that thread has been updated and the name has changed nearly daily. Right now it just changed to something else "The final edition" or something like that, yesterday it was "yea, yes im on top" or something like that. ha. I feel confident that I can execute the necessary commands, once i get this damn ADB up and running. I find myself getting confused. I got the java issued figured out, and installed the Android SDK started package. Im reading more before I attempt anything, but the problem I find is that half or more of the stuff I find while searching, is out dated I think. I keep landing threads and such from june and july, and i'm not sure if that's current or obsolete. **** changes so much. So where I'm at now, is the android SDK tools windows is installed, and I'm kinda at a standstill right now. Lol. I see a late night this evening.
And just to mention, to my surprise, her brand new white evo came with : hardware 004, hboot 2.02, software 3.30. I would've thought it'd come with the latest OTA update and hboot etc. Guess I was wrong. Anyways, shouldn't affect much I don't think, if I can ever get ADB to set up correctly. Any other/additional advice is more than welcomed. My pm inbox has plenty of room. THanks
Alright, I am kind of stuck here, I believe that I have everything installed and all the drivers I need, following the links you guys posted here. I open a command prompt, and when it opens initially, it reads : C:\Users\Kyle> Then I enter C:\ android-sdk-windows\tools Then the initial prompt changed from C: \users\kyle> to C:\android-sdk-windows\tools> Thats as far as I get. I tried typing adb devices, and I got 'adb' is not a recognized as an internal or external command.
Im not sure where to go from here. If anyone could point me in the right direction from here, it would be super appreciated. I feel like I'm getting very close here, I just don't know what to check next?? Thanks in advance.
Try this thread. It has a lot of ADB info.
http://forum.xda-developers.com/showthread.php?t=694250
damn, well I think I'm at a standstill for tonight. All the info you guys have posted has been very helpful, however I'm still unable to get it working. I'm pretty sure I have all the drivers that I need installed. I have usb debugging checked on the phone. HTC sync is installed, along with some other drivers that I have found while researching adb. I'm either missing something big, or I'm making stupid mistakes. I just can't seem to get it to work. Any time I type anything 'adb' into the command prompt, it says that adb is not a recognized command, internal or external. So I'm assuming that I must not have the right drivers. Also, just so I understand, if anyone could confirm this. While trying to use adb, does the phone have to be in bootloader? recovery? Booted into the OS, connected as charge only? I seem to be finding conflicting information.
First, I believe you need to get rid of HTC Sync, or at very least make absolutely certain it isn't running...it conflicts with adb.
Second, when it's plugged into USB, make sure your phone's in the "Charge Only" mode.
Third, make sure that under "Settings, Applications, Development" you've got "USB Debugging" checked.
Ok, so when SDK installed itself it should have created a sub-directory (I'm using your screen name as 2nd directory, but substitute the correct one)
C:\Users\K2Buckley\android-sdk-windows\platform-tools
In this directory should be 2 files: "adb.exe" and "adbwinapi.dll". Copy them to your windows\system32 (64?) folder. This will/should allow you to run ADB from any directory, and eliminate the need for you to add anything to your Environment Variables.
Now, if your drivers are running properly and your phone's plugged in, open the Command Prompt by going to the Start Menu, and in the Start Search box at bottom type CMD.
No matter which directory it opens in you should be able to run adb, so as a test, type
adb devices
If it's working, (and it should be), you'll see your phone's ID come up.
You can then do a directory change to whatever directory on your puter you have put all the files you're going to need for your process. For instance I would type
cd c:\users\neil\evo-rooting
That command prompt should pop up. From that point on follow your directions to push, pull, reboot, etc. whatever is called for right from that command prompt. As an example, if I wanted to "push" the file "warm22rom.zip" from that directory to the "zip" directory on my sd card, from that C:\USERS\NEIL\EVO-ROOTING command prompt I'd type
adb push warm22rom.zip sdcard/zip
And if I wanted to reboot my phone from the computer, from that command prompt I'd type
adb reboot
In fact, try that one as a test (be patient, it takes about 20-30 seconds to execute but it's a trip when your phone boots...).
I've just run through this whole process myself just to make sure it works. It does. So if it doesn't work for you, it's gotta be the drivers.
2 other quick checks:
In your computer's Device Manager should be "Android Phone" with "Android Composite ADB Interface" listed if you click the plus sign...
and/or
In Vista, when I plug the phone into the USB port, a little gray square with a white check in a green circle pops up on the right side of my task bar (you should have something similar). This is the "Safely Remove Hardware" icon, and if I double click it it opens a box that shows me what devices/drivers are installed. In that box are 2 things you need to look for: a single line that says "Android Composite ADB Interface" and a short "tree" that reads "USB Mass Storage Device, HTC Android Phone USB Device, Generic Volume - J" (this is my SD Card designation).
If you see these things, or something close, you've got it all installed right.
It's up to you now...go forth and Root, and ADB to your heart's content.
Good luck, I hope this helped.
Fail for me. I feel like a moron. Still can't get this going. Don't know what the hell I'm missing. Anything special that I'm missing about using a 64 bit system? I'm officially stumped. I don't know how much it matters, but can't seem to find any threads/guides specific to the Evo. I keep finding them for moto droid, g1, vibrant. I must be too tired and not thinking straight.
I also keep finding information saying that there should be an adb.exe file in the tools folder, as well as a couple .dll files. I can't find any anywhere on my computer, not even when I search. So does this mean I have either not extracted to the right place or something? Now I'm more lost. F*_k.
Persnlmgr said:
First, I believe you need to get rid of HTC Sync, or at very least make absolutely certain it isn't running...it conflicts with adb.
Second, when it's plugged into USB, make sure your phone's in the "Charge Only" mode.
Third, make sure that under "Settings, Applications, Development" you've got "USB Debugging" checked.
Ok, so when SDK installed itself it should have created a sub-directory (I'm using your screen name as 2nd directory, but substitute the correct one)
C:\Users\K2Buckley\android-sdk-windows\platform-tools
In this directory should be 2 files: "adb.exe" and "adbwinapi.dll". Copy them to your windows\system32 (64?) folder. This will/should allow you to run ADB from any directory.
Now, if your drivers are running properly and your phone's plugged in, open the Command Prompt by going to the Start Menu, and in the Start Search box at bottom type CMD.
No matter which directory it opens in you should be able to run adb, so as a test, type
adb devices
If it's working, (and it should be), you'll see your phone's ID come up.
You can then do a directory change to whatever directory on your puter you have put all the files you're going to need for your process. For instance I would type
cd c:\users\neil\evo-rooting
That command prompt should pop up. From that point on follow your directions to push, pull, reboot, etc. whatever is called for right from that command prompt. As an example, if I wanted to "push" the file "warm22rom.zip" from that directory to the "zip" directory on my sd card, from that C:\USERS\NEIL\EVO-ROOTING command prompt I'd type
adb push warm22rom.zip sdcard\zip
And if I wanted to reboot my phone from the computer, from that command prompt I'd type
adb reboot
In fact, try that one as a test (be patient, it takes about 20-30 seconds to execute but it's a trip when your phone boots...).
I've just run through this whole process myself just to make sure it works. It does. So if it doesn't work for you, it's gotta be the drivers.
2 other quick checks:
In your computer's Device Manager should be "Android Phone" with "Android Composite ADB Interface" listed if you click the plus sign...
and/or
In Vista, when I plug the phone into the USB port, a little gray square with a white check in a green circle pops up on the right side of my task bar (you should have something similar). This is the "Safely Remove Hardware" icon, and if I double click it it opens a box that shows me what devices/drivers are installed. In that box are 2 things you need to look for: a single line that says "Android Composite ADB Interface" and a short "tree" that reads "USB Mass Storage Device, HTC Android Phone USB Device, Generic Volume - J" (this is my SD Card designation).
If you see these things, or something close, you've got it all installed right.
It's up to you now...go forth and Root, and ADB to your heart's content.
Good luck, I hope this helped.
Click to expand...
Click to collapse
Whoa, thanks dude. I'm going to try that right now. I made my last post as you were typing that up apparently, I was ready to throw in the towel, but I'm going to try what you said. Thats very very close to what i was doing, out of all the different tutorials i was trying to follow.
I still couldn't find the .exe or .dll files, so I have no clue what happened there. I'm going to try re installing sdk all together and see if I can get this. Thanks again dude, I know it's late, I appreciate you taking the time to type that up.
. I'm going to give this a try.
And yes, by the way, the drivers listed in my "safely remove hardware" are the same as what you have there. I'm reinstalling the sdk tools now. Hopefully that adb.exe file is there. Before, all that was there was 'adb', among some other folders. I'm assuming there needs to be one that is actually 'adb.exe', correct? when i clicked on the properties of that 'adb' one that was there, it said 'file type: .exe (application)'. Is that what I'm looking for?
http://developer.android.com/sdk/index.html
that is the site I downloaded the sdk tools from, the one for windows that says 'installer ro8 windows.exe (recommended) Does that appear to be the correct one? Once i downloaded that, the installer popped up, installed everything, then sdk manager popped up, requested that I download and install some stuff (android platforms?). Once that's finished, that should be it, right? Just want to make sure I haven't been missing a step or something.
(and thanks for your patience with me, I'm learning though. all the flashing I've done in the past few months, still can't believe that I never took to the time to learn adb. now I know why people are against Unrevoked, cuz I didn't learn sh!t by doing that. A few clicks and I was rooted and flashing away!)
well. I fubared something, ha. This is becoming comical. I followed what you said. The only thing is, which I'm sure this is the issue...after sdk tools installed again, there was still no 'adb.exe' folder in platform-tools. just 'adb'. The adbwinapi.dll was there, and i copied it to "windows/system32" I copied the 'adb' to that folder as well. So either the 'adb' that i copied was incorrect, and I have no idea where that damned 'adb.exe' is at, or i was supposed to move or cut them, rather than copy. either way, i give up for tonight, need some sleep.
when I opened a command prompt, and typed 'adb devices', a windows error with a red x pops up (outside the command prompt) that reads "this application has failed to start because AdbWinApi.dll was not found. Re installing the application may fix the problem". Then I click ok.. Then it says "adb.exe has stopped working, a problem caused the program to stop working correctly. windows will close the program and notify you if a solution is available" HA. DAMn I suck.
Not thinking clearly right now, need some sleep. Thanks again, hopefully we can get this straightened out tomorrow, or later today i guess it is now, damn its late.
Edit!! whoa! My final attempt was to copy the adbwinapi.dll to windows\system (instead of system32), and i believe that worked. I typed in adb devices, and I got "list of devices attached HT0###L00069 device" I assume that's my Evo? Hooray! Thank you so much man, I cannot express how happy I am right now, ha. That adb reboot kicked ass, lol. Now I can learn some stuff.
Finally, last question. My friend (who's phone I was going to root) had to leave hours ago. I was using my phone to do this and get it working. When I go to root her phone, in theory, should it connect to adb just fine at this point? Thanks again man, you were a huge, massive help.
I suck. I had it working. For some reason, through my tiredness and confusion, I thought I had to type "adb kill-server" to exit adb. After I did that, now if I type anything starting with adb, it says:
"daemon not running. starting it now on port 5037
CreateProcess failure, error 2
failed to start daemon
error: cannot connect to daemon"
Have no idea what the eff I did. Tried doing some research, will have to check more tomorrow. I tried adb start-server, and got the same message. Rebooted phone and computer, same thing. So i messed something up. Anyone know what I did and what i could try to get it working again? damn i suck.
k2buckley said:
I suck. I had it working. For some reason, through my tiredness and confusion, I thought I had to type "adb kill-server" to exit adb. After I did that, now if I type anything starting with adb, it says:
"daemon not running. starting it now on port 5037
CreateProcess failure, error 2
failed to start daemon
error: cannot connect to daemon"
Have no idea what the eff I did. Tried doing some research, will have to check more tomorrow. I tried adb start-server, and got the same message. Rebooted phone and computer, same thing. So i messed something up. Anyone know what I did and what i could try to get it working again? damn i suck.
Click to expand...
Click to collapse
The "kill-server" should not have completely disabled ADB. Relax until you get her phone, then do everything you did to yours to hers. It should re-start. Yes, "adb.exe" was the proper file (not folder) to have moved into your computer windows\system(32,64,-) directory, as was the dll file. Obviously. Or it never would've told you the device ID.
You're on the right track.
And, when in doubt, issue that "adb reboot" command. It's not gonna hurt the phone and it'll let you know if ADB is working... Just don't do it halfway through any process.
And stop experimenting with things like adb kill-server, dummy!!! The only way you need to know to STOP adb is you DON'T NEED TO STOP ADB! It's not like a background program that you need to kill when you're done.
The way to "stop" or "kill" ADB is simply not to issue ADB commands. And when you close that Command Prompt box, ADB IS closed.
Okay, I just tried issuing the adb kill-server command. It takes me back to a DOS prompt with no notes. Then I typed ADB and my daemon started back up. I then issued adb start-server and it took me back to a blank (no notes) command prompt.
Don't know why it completely shut down your ADB, but I think when you plug her phone in you'll have a fresh start and it'll all work.
Start with adb devices, then if it shows her ID, issue adb reboot. If the phone reboots, you're good to go forward.
[EDIT] Okay, I just tried something I should've told you to try: without the phone plugged in, open the Command Prompt and type adb devices. Prompt should come back up as below. I then issued adb kill-server. Again, see below, nada. But then I issued adb start-server and got what you see in the string below:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Neil>adb devices
List of devices attached
[blank, so none]
C:\Users\Neil>adb kill-server
[blank]
C:\Users\Neil>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\Neil>[blank]
Yours should look and work like this. If it does, plug in the phone and get started.
If not, pull out that .38 on the top shelf of your closet. Put in only 1 bullet. Spin chamber. Point at head. Pull trigger.
If you're still standing, (that's a good sign), go back to step one (unplug phone, reboot phone and computer), and try, try again. (Or Google Chat me...I PMd my screen name to you).
Just saw this one...responses in Green
k2buckley said:
Whoa, thanks dude. I'm going to try that right now. I made my last post as you were typing that up apparently, I was ready to throw in the towel, but I'm going to try what you said....
I'm assuming there needs to be one that is actually 'adb.exe', correct? when i clicked on the properties of that 'adb' one that was there, it said 'file type: .exe (application)'. Is that what I'm looking for?
YES INDEED!!
that is the site I downloaded the sdk tools from, the one for windows that says 'installer ro8 windows.exe (recommended) Does that appear to be the correct one? Once i downloaded that, the installer popped up, installed everything, then sdk manager popped up, requested that I download and install some stuff (android platforms?). Once that's finished, that should be it, right? Just want to make sure I haven't been missing a step or something.
All Good
(and thanks for your patience with me, I'm learning though. all the flashing I've done in the past few months, still can't believe that I never took to the time to learn adb. now I know why people are against Unrevoked, cuz I didn't learn sh!t by doing that. A few clicks and I was rooted and flashing away!)
We all have to start somewhere. And I used Unrevoked, too, so had to go back and learn ADB
well. I fubared something, ha. This is becoming comical. I followed what you said. The only thing is, which I'm sure this is the issue...after sdk tools installed again, there was still no 'adb.exe' folder in platform-tools. just 'adb'. The adbwinapi.dll was there, and i copied it to "windows/system32" I copied the 'adb' to that folder as well. So either the 'adb' that i copied was incorrect, and I have no idea where that damned 'adb.exe' is at, or i was supposed to move or cut them, rather than copy. either way, i give up for tonight, need some sleep.
when I opened a command prompt, and typed 'adb devices', a windows error with a red x pops up (outside the command prompt) that reads "this application has failed to start because AdbWinApi.dll was not found. Re installing the application may fix the problem". Then I click ok.. Then it says "adb.exe has stopped working, a problem caused the program to stop working correctly. windows will close the program and notify you if a solution is available" HA. DAMn I suck.
No you don't. You're doing good...
Not thinking clearly right now, need some sleep. Thanks again, hopefully we can get this straightened out tomorrow, or later today i guess it is now, damn its late.
Edit!! whoa! My final attempt was to copy the adbwinapi.dll to windows\system (instead of system32), and i believe that worked. I typed in adb devices, and I got "list of devices attached HT0###L00069 device" I assume that's my Evo? Hooray! Thank you so much man, I cannot express how happy I am right now, ha. That adb reboot kicked ass, lol. Now I can learn some stuff.
Agreed. Totally trippy when you type on the 'puter and the phone reacts
Finally, last question. My friend (who's phone I was going to root) had to leave hours ago. I was using my phone to do this and get it working. When I go to root her phone, in theory, should it connect to adb just fine at this point? Thanks again man, you were a huge, massive help.
Click to expand...
Click to collapse
YES INDEED IT SHOULD CONNECT, and you're very welcome!!
I still really don't understand why anyone has to install SDK if they're only going to tweak their phone and not write programs. That's what SDK is for. I think the whole SDK Install thing is just to get those f-ing USB drivers...which seems patently absurd.
SO FORGET SDK AND JUST CONCENTRATE ON ADB...
Persnlmgr said:
Okay, I just tried issuing the adb kill-server command. It takes me back to a DOS prompt with no notes. Then I typed ADB and my daemon started back up. I then issued adb start-server and it took me back to a blank (no notes) command prompt.
Don't know why it completely shut down your ADB, but I think when you plug her phone in you'll have a fresh start and it'll all work.
Start with adb devices, then if it shows her ID, issue adb reboot. If the phone reboots, you're good to go forward.
[EDIT] Okay, I just tried something I should've told you to try: without the phone plugged in, open the Command Prompt and type adb devices. Prompt should come back up as below. I then issued adb kill-server. Again, see below, nada. But then I issued adb start-server and got what you see in the string below:
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Neil>adb devices
List of devices attached
[blank, so none]
C:\Users\Neil>adb kill-server
[blank]
C:\Users\Neil>adb start-server
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
C:\Users\Neil>[blank]
Yours should look and work like this. If it does, plug in the phone and get started.
If not, pull out that .38 on the top shelf of your closet. Put in only 1 bullet. Spin chamber. Point at head. Pull trigger.
If you're still standing, (that's a good sign), go back to step one (unplug phone, reboot phone and computer), and try, try again. (Or Google Chat me...I PMd my screen name to you).
Click to expand...
Click to collapse
Well I'm awake and rested! Now that I'm not stupidly tired, I think I remember something bad. For some reason, I'm thinking I might've, just possibly, typed adb kill. as opposed to adb kill-server. I probably did just that, killed adb! But yea, even with the phone disconnected, if I type adb devices, i get the same error message, failed to start daemon. Crap. Wonder if I should start all over? Or if "kill adb' did something worse. The reason I tried to do that (which I know I shouldn't have, and I've learned a lesson from it) is because when I tried to removed the device, from the "safely remove hardware", it wouldn't let me stop the "adb compositte interface" because it said something was still using it. I had everything closed, no windows of any sort open. I thought to myself, "hmm, adb must still be connected to my phone somehow, perhaps i need to kill it before I can unplug the phone." So, that was my dumbass reasoning. But I do think I typed "adb kill" When I typed that, no errors came up, and it did indeed allow me to stop the device. However, it's just when I try any other adb commands now. If I type "adb", it pops up a crapload of information, looks like it shows me a bunch of different adb commands. but as soon as I type anything after "adb" such as "adb devices," "adb start-server" or whatever, it gives me the error message and says failed to start daemon. So I believe i effed something up.
k2buckley said:
Well I'm awake and rested! Now that I'm not stupidly tired, I think I remember something bad. For some reason, I'm thinking I might've, just possibly, typed adb kill. as opposed to adb kill-server. I probably did just that, killed adb! But yea, even with the phone disconnected, if I type adb devices, i get the same error message, failed to start daemon. Crap. Wonder if I should start all over? Or if "kill adb' did something worse. The reason I tried to do that (which I know I shouldn't have, and I've learned a lesson from it) is because when I tried to removed the device, from the "safely remove hardware", it wouldn't let me stop the "adb compositte interface" because it said something was still using it. I had everything closed, no windows of any sort open. I thought to myself, "hmm, adb must still be connected to my phone somehow, perhaps i need to kill it before I can unplug the phone." So, that was my dumbass reasoning. But I do think I typed "adb kill" When I typed that, no errors came up, and it did indeed allow me to stop the device. However, it's just when I try any other adb commands now. If I type "adb", it pops up a crapload of information, looks like it shows me a bunch of different adb commands. but as soon as I type anything after "adb" such as "adb devices," "adb start-server" or whatever, it gives me the error message and says failed to start daemon. So I believe i effed something up.
Click to expand...
Click to collapse
Okay, well as I said, **** SDK, it's irrelevant.
"You need the driver only if you are developing on Windows and want to connect an Android-powered device to your development environment over USB."
So, go here ( http://developer.android.com/sdk/win-usb.html ) to get and (re)install the ADB Composite drivers. You should not have to do anything else. If they ask WHERE you want to install them, either direct them to the root of your harddrive, likely C:\ , or if you can set the directory where the DRIVERS (not the program) goes, choose WINDOWS.
Then you should be ready to go back and follow the rest of my instructions easily.
BTW, I assume you've checked UNRevoked.com to see if they have a fix for their super easy, automatic Root process to accomodate the new HBoot?
Jus' askin...
Keep me posted, or GChat me. I'm at my desk...
Welcome to the HTC One M8 S-Off GUIDE FOR NEWBIES!
Disclaimer:I am not responsible for any damage to your phone, in part, or in whole; including bad SD cards, broken reception, bad wifi, Windows 8 being installed, or anything else that could go wrong: Bricking, Bootloops, blips, beeps, boops, or sweeps. You chose to follow these instructions on your own accord and if you do so, agree that I am not liable in anyway, shape or form.
What Models/Carries Should this Work for?
USA: ATT, TMobile
European: Tmobile, VodaFone
I'm unsure if all of this works for Verizon/Sprint versions. You'll have to check the Toolkit's thread and the Firewater thread or official site for confirmation. The above models are just what I've read on the forums)
Credits:
Hansoon2000 for the HTC One Toolkit
Shrimp208 for Minimal ADB and Fastoot
Beups and Fuses for Firewater.
Ok, so, you want to achieve Root/S-Off and its many benefits. I'm going to walk you through what I did to make this process fairly simple.
Requirements:
HTC One M8
Windows 7, 8, 8.1
No Lockscreen on your phone.
Developer Options Enabled with the following:
1. USB Debugging Enabled
2. Allow Mock Locations (this may not be necessary, but I always do it just in case)
Hint: Don't know how to enable developer options? Go to Settings>About>Software Information>More and tap on "Build Number" 7 times. This will open Developer Options in the Settings menu.
Let's Root!Use the All-In-One toolkit here:
http://forum.xda-developers.com/showthread.php?t=2699065
Process:
When you open the ToolKit, you'll notice lots of little boxes with text inside. We're going to focus on the box at the very top left that says "To root the phone, follow in order." Fairly simple, right?
First, Download and install HTC Sync Manager and make sure it sees your One M8. Do not use the Install Drivers option from the toolkit, they're outdated/don't work for most people. HTC Sync will install the latest driver for the M8. You can then uninstall the HTC Sync Manager program itself. Link: http://www.htc.com/www/software/htc-sync-manager/
Register at HTCDev. This is needed for this process to gain permaroot at the time I write this. If it doesn't allow you to register, either use a different email address, or ask a friend to do this.
Once logged in, go to "Unlock Bootloader" and Select HTC One (M8) from the drop down list. Follow the steps/prompts and directions on the site.
Get Token ID. Plug your phone in to a USB 2.0 port on your PC (not a hub, not USB3.0, USB 2.0). You should be notified that the HTC One M8 has been plugged in. If so, Proceed. If not, you'll have to figure out the issues you're having with the drivers first.
Two windows will Pop Up. Hit close on the First Window.
The second window should pop up with text. Your token ID is a long series of alpha-numeric text. This is an example of everything you should copy:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Note: Copy ALL off that text. From the <<<<Identifier Token Start down to Identifier Token End>>>>
Now, Take that copied text and submit it at HTCDev where it asks you to. If it's successful and you've copied what you need to, an Unlock_Code file will be emailed to you. Download and Place this file in the HTC One Toolkit's Data folder.
Unlcok Bootloader: Again, two windows will pop up, close the first. Your Phone should reboot and the token ID Applied. Your phone will ask you if you want to proceed. Hit Volume Up for "Yes" and Power Button to confirm. This might take a minute, don't freak out.
Flash a Recovery. Once your phone is booted back to the Home screen, go to the far right top window and Select TWRP as the recovery. Select Flash Recovery. Your phone will again pop up with two windows, close the first, and let it do it's thing. Reboot back into the Recovery after this is all done.
Flash Supersu. Go into "Install" in TWRP and select "SuperSu" from the list, swype to begin process.
Congratulations, you should now be rooted!
Time to S-Off!
WARNING: Not all devices are supported by Firewater. There's really no way to tell until you start running the process to S-Off. If Firewater tells you that your device is not compatible, then it's not compatible. You'll have to wait until Firewater does support your device and is updated.
REQUIRMENTS:
ROOTED HTC ONE M8
ADB and HTC Drivers (htc drivers should be installed from Rooting)
Developer Options Enabled with the following:
1. USB Debugging Enabled
2. Allow Mock Locations (this may not be necessary, but I always do it just in case)
Hint: Don't know how to enable developer options? Go to Settings>About>Software Information>More and tap on "Build Number" 7 times. This will open Developer Options in the Settings menu.
Don't have ADB and don't know where to start? Then download and install MINIMAL ADB AND FASTBOOT:
http://forum.xda-developers.com/showthread.php?t=2317790
Once Downloaded and installed, go to your Start window on the PC and search "ADB". Minimal ADB and Fastboot (here on referred to as ADB) will show up, click on it to bring up a Command Prompt. Using Admin Rights isn't a bad idea either when using ADB.
Go to http://firewater-soff.com/instructions/ And make sure you Follow the Prerequisits to the letter! Read the Instructions for "Rooted, Normal Device Method"
Now that you have the Firewater file, go to Start and Search for ADB, RIGHT CLICK and choose SHOW FILE LOCATION. Drop your Firewater file here. Now we can begin!
Process:
Connect your phone to a USB 2.0 Port if you already haven't and make sure your phone is on the Home screen with NO LOCKSCREEN OF ANY SORT
In the Command Terminal, Type:
adb device (this should show you that your phone is connected. If it says that the phone is inactive/offline, then unplug your phone and replug it. Try again. It should now show up).
Type:
adb Reboot (this will reboot your phone)
After your device has rebooted, there's a 99.9999% chance that it will ":go offline" and not connect to adb (we can confirm this with "adb device" command. Unplug, Replug your phone and ensure it's online and ADB can see it).
Type:
adb wait-for-device push firewater /data/local/tmp
Type:
adb shell
Type:
su
Type:
chmod 755 /data/local/tmp/firewater
Type:
/data/local/tmp/firewater
If you're successful up to this point, Firewater will ask you if you're sure. Type:
Yes
At this point, the Command Prompt will start Chugging bottles of Firewater. Some Command Prompts only Chug One, others, 5,6, up to 12. If you reach 13 Bottles, Abort and try the steps again. This may take a while and several resteps, just be patient. The command prompt, when successful, will notify you that you are now S-Off!
To check this, boot in to Bootloader to confirm (it will say S-Off, not S-On).
The Why:
I believe the reason you need an internet connection is that the Firewater file connects to a server and the voodoo is all done by the server. Why would they do this? Probably to ensure that HTC doesn't screw us out of S-Offing our device like they're known to do by downloading and decompiling files used to S-Off or reverse engineering steps taken to S-Off If anything, this slows them down (and possibly makes it impossible for them to stop us from doing so.)
Special Thanks:
Beups, Fuses, Hasoon2000, and all Developers that are supporting our device with lots of goodies. Don't forget to donate to them to encourage them to spend time on our device, or, just buy them a beverage for all of the hard work and time they spend doing this for us.
If I have forgotten anything or forgot to give credit to someone, please let me know and I'll be sure to add it.
You might want to add that if firewater says your device is not compatible then it means exactly that and you just need to wait for firewater to be updated. There's no pattern to what is and isn't compatible its just luck of the draw and likely down to hardware variances.
Sent from my HTC One_M8 using Tapatalk
stuart0001 said:
You might want to add that if firewater says your device is not compatible then it means exactly that and you just need to wait for firewater to be updated. There's no pattern to what is and isn't compatible its just luck of the draw and likely down to hardware variances.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Ah, yes, you're correct. Thank you!
i'm having a nightmare.
having issues all the way through, seems the htc drivers i get from the toolkit don't install correctly. adb just wouldnt play. i got round that by installing htc sync from phone, that installed correct htc drivers. i then un installed htc sync.
now i've got as far as...
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
3082 KB/s (4519496 bytes in 1.431s)
C:\Program Files (x86)\Minimal ADB and Fastboot>shell
'shell' is not recognized as an internal or external command,
operable program or batch file.
any ideas what i've f'ed up?
---------- Post added at 01:47 AM ---------- Previous post was at 01:39 AM ----------
ok i think it should be adb shell yes?
Yes adb shell
Sent from my HTC One_M8 using xda app-developers app
Learoy1 said:
i'm having a nightmare.
having issues all the way through, seems the htc drivers i get from the toolkit don't install correctly. adb just wouldnt play. i got round that by installing htc sync from phone, that installed correct htc drivers. i then un installed htc sync.
now i've got as far as...
C:\Program Files (x86)\Minimal ADB and Fastboot>adb wait-for-device push firewat
er /data/local/tmp
3082 KB/s (4519496 bytes in 1.431s)
C:\Program Files (x86)\Minimal ADB and Fastboot>shell
'shell' is not recognized as an internal or external command,
operable program or batch file.
any ideas what i've f'ed up?
---------- Post added at 01:47 AM ---------- Previous post was at 01:39 AM ----------
ok i think it should be adb shell yes?
Click to expand...
Click to collapse
Did you get it all worked out?
Also, I updated the OP to use "adb shell," I apologize, I should have remembered that adb need to be there. As well, I've updated the OP to point to the latest HTC Sync with drivers.
Sorry for the question but it's my first HTC device and I'm studying in deep all the aspects of bootloader, s-off and so on.
What about I need to come back the M8 for warranty?
If I am right I can restore stock rom and recovery and relock the bootloader through s-off. At this point, what about s-off? Is there a way to revert it to stock s-on?
This Rooting method works for the International variant as well right?
Just can't seem to get my device online. I've tried just about everything, restarted phone, laptop, server, different port, different cable, etc. I see a notification that says "Media Device [MTP] connected", and I have an inkling that it could be causing issues, but I can't seem to find a way to disable it. Is anyone else having this issue?
(T-Mobile M8, perma-rooted)
*edit* After several attempts, I seem to have gotten the timing right, using the version of ADB that came with the all in one tool. Somehow it just started to work, but only with that version. Other versions of ADB still saw the device offline. Just one of those annoying things. Either way, I'm now S-OFF. That was the last piece I was missing. Thank you.
Not working!
Have htc one m8 (at&t version) and have tried all the steps but always fails at the end. It saids it wil not work with my device? Don't other people use this with at&t and it works for them? Why doesn't it work for me? Is there another method to s-off? Like from twrp recovery?
patstar5 said:
Have htc one m8 (at&t version) and have tried all the steps but always fails at the end. It saids it wil not work with my device? Don't other people use this with at&t and it works for them? Why doesn't it work for me? Is there another method to s-off? Like from twrp recovery?
Click to expand...
Click to collapse
HTC patched the old S-OFF method, it doesn't work anymore unless you're really lucky to get a device that's before the patch and you don't first update it...
You can try Sunshine S-OFF it's $25 but it seems to do the job right. It actually checks your device for compatibility before you even pay for it, at least that way you won't end up paying for something that "might" not work.
[Android][HTC S-OFF] SunShine for modern HTC devices It's from the same developers of firewater. So far those that did it seems quite happy about it.
Your choice though, it's the only alternative method available.
BerndM14 said:
HTC patched the old S-OFF method, it doesn't work anymore unless you're really lucky to get a device that's before the patch and you don't first update it...
You can try Sunshine S-OFF it's $25 but it seems to do the job right. It actually checks your device for compatibility before you even pay for it, at least that way you won't end up paying for something that "might" not work.
[Android][HTC S-OFF] SunShine for modern HTC devices It's from the same developers of firewater. So far those that did it seems quite happy about it.
Your choice though, it's the only alternative method available.
Click to expand...
Click to collapse
I can't believe I paid $25 but it did work. Wanted to change my software buttons to stock android. Well I guess now I can put other roms on it. If I flash a different custom rom on it, it would be like getting a new phone so I would have to transfer all my data again? Took forever to get apps to restore from helium (carbon) backup and some did not work, really don't want to put custom Rom if it does that again. If I make nandroid backup to internal storage, can I transfer it to my pc for use later on?
patstar5 said:
I can't believe I paid $25 but it did work. Wanted to change my software buttons to stock android. Well I guess now I can put other roms on it. If I flash a different custom rom on it, it would be like getting a new phone so I would have to transfer all my data again? Took forever to get apps to restore from helium (carbon) backup and some did not work, really don't want to put custom Rom if it does that again. If I make nandroid backup to internal storage, can I transfer it to my pc for use later on?
Click to expand...
Click to collapse
Yeah unfortunately if you flash any new ROMs it'll be like a "new" phone like you yourself stated. There will be no apps, nothing. You can back it up and restore with something like Titanium. Even through Google Store it's easy enough if you lock in with the same account again, just reinstall, easy as pie.
Yes if you make a nandroid backup of your device you can store it on your computer for use later on. It's actually advisable to do so, you "might not" find a nandroid backup for your device whilst searching online, so at least if something goes wrong you have a backup on your PC and all is good :good: If only more people would make backups before doing anything though...
BerndM14 said:
Yeah unfortunately if you flash any new ROMs it'll be like a "new" phone like you yourself stated. There will be no apps, nothing. You can back it up and restore with something like Titanium. Even through Google Store it's easy enough if you lock in with the same account again, just reinstall, easy as pie.
Yes if you make a nandroid backup of your device you can store it on your computer for use later on. It's actually advisable to do so, you "might not" find a nandroid backup for your device whilst searching online, so at least if something goes wrong you have a backup on your PC and all is good :good: If only more people would make backups before doing anything though...
Click to expand...
Click to collapse
Titanium backup won't let me backup to sd card, I guess I could backup to internal storage and put it on pc like nandroid or move it to sd card afterwards? I could just download custom rom to my phone, goto twrp and flash it without pc? Is there any dual boot method of roms? I know for m7 there was something that let you switch from sense to stock android with press of button.
Lost & Puzzled Newbie
Hi Guys,
I'm hoping someone can help me out here because I've ben sat in front of my pc for 16 hours straight through the night & I now don't appear to be much nearer than when I started!
So, I picked up my new One M8 & having had some success rooting my ASUS TF700T tablet, I decided that I would root my phone before I got started using it properly & wasted time personalising it. Before I get started, I'm currently on Android 4.4.2, Sense 6.0, & software number 1.54.206.10; if you need anything else, let me know.
I did loads of reading first, hence the night sat in front of my pc, & amongst many others, I was following this thread & the instructions here:
http://forum.xda-developers.com/showthread.php?t=2799796
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
I was doing really well to begin with & I managed to unlock the bootloader, flash TWRP, & install SuperSU. Then things started to go wrong. I was undecided whether or not to go for S-Off &/or Super CID but I'd read that S-Off might maximise my battery life even more, so I went for it. I only installed the HTC drivers, absolutely no HTC Sync, my USB Debugging was on, Security was off, & Fastboot was disabled. I downloaded Firewater & after discovering that the ADB folder on my pc wasn't just the folder I'd extracted my ADB zip file to, I found the correct ADB folder on my C: drive, dropped Firewater in & plugged my in M8. It's my own fault because normally, when my phone asks, 'do you want me to do this every time?', I say 'no, just once'......but for some unknown reason, once I'd hooked it up & was using the adb command window (Win 8.1), when the message popped up on the M8 about the phone allowing my pc to connect via adb every time, I, apparently stupidly, said yes.
What happened then was that the adb console, would recognise my phone, so when I typed 'adb device' (or whatever the instruction was), it gave me a page of all sorts of details but then every time I typed 'adb reboot', I got a message saying that the device was offline. If I typed 'adb device' again, I'd get the same page of data & I could see the phone in explorer, so I'm sure the drivers are there, but I also got the same message asking for the reboot.
I've spent hours trying to sort this out & if I'm honest, I got a bit lost (I'm normally quite good at problem solving but I don't suppose it helped not having slept for almost 30 hours now). Anyway, I remembered with my tablet that I just went into TWRP & flashed the 'CHROMi X' ROM from there & by this time, I just wanted to try to get things finished, so because I was most familiar with CyanogenMod, I downloaded it on the pc, transferred it to the phone & tried to flash it I thought I'd read that I neded the ClockworkMod bootloader but I was kind've hoping that TWRP would do the job......it didn't & just failed!
Then my problems really started because the phone went into a boot loop, staying on for only about 10-20 seconds after it booted up. Obviously, by this point I was quite worried that I was about to wreck my shiny new phone but I did some more reading & saw that for someone else, SuperSU had caused this, so I booted back to TWRP, wiped the Dalvik cache & re-flashed SuperSU. Thankfully, that stopped the boot loop
However, I now seem unable to access TWRP? When I hold down the volume down & power buttons, the phone just boots straight through to Android? SuperSU is still installed & it opens up fine (albeit with no apps logged) but it seems like now, the phone might not be unlocked, &/or rooted, or both, though that doesn't seem to make sense to me if SuperSU still runs?
EDIT: I've just tried deleting a folder on the external micro SD card using ES File Explorer & the 'operation failed', so it looks SuperSU, although it asked if I wanted to grant/deny the relevant permissions, isn't working. On 2nd attempt, it worked, so I'm still lost!
EDIT: Fastboot had sneaked back on, so I've switched it back off & I'm back into the bootloader, which says 'Tampered' & 'Unlocked' at the top, & I can boot into TWRP to make the backup of what I've got now that I wanted to make earlier
ANOTHER EDIT: I've now backed up the stock ROM with TWRP & downloaded a root checker app, so I now know that I'm still unlocked & rooted Now I could just do with some help deciding what ROM to install & help on how to go about it.....please
EDIT: After all that, I couldn't sleep, so I didn't try & I stayed up & have managed to sort it. I've got Android Revolution HD on for now but I think I'm correct in thinking that I'll be able to change to another ROM at a later date if I don't like this one? I was going to delete all this, so that people didn't think I was an idiot but it might prove useful to someone else, if only to prove that you probably shouldn't miss a night's sleep because you're trying to root your new phone!!!!
I hope all that makes sense to someone else though? All I wanted to do was get rid of all the O2 bloatware, & most of all, actually be able to write to my external micro SD card, without having to take it out of the phone constantly, so I wanted to install a custom ROM that would be as good as CHROMi X is on my tablet!! but as I said at the beginning, I now feel completely lost & unwilling to start trying again until I know what's happening/has happened.........oh, & I need some sleep!!
If anyone can help get me back on track again, I'd really appreciate it because I really have put the effort in & I don't normally give up but I'm worried that if I keep at it now, I'll end up bricking my phone!! I do want to get this sorted out & enjoy this amazing device for the next couple of years, so any advice on where to start next, which ROM I should use (at this point, I'm easy), or whatever, like I said, I'd really appreciate it
p.s. I didn't mention but once I've sorted my phone out, my girlfriend wants me to sort her HTC One Mini 2 out because she wants to be able to use her external micro SD card too!!
delete
I have hit dead end after dead end, after many hours, just want to get copy of text messages off this phone somehow, and then erase all data. I have spent many hours on this, my level of experience with all this is beginner/intermediate, as I'm sure you will be able to tell by the ramble below. Skip to the last paragraph **** with the asterisks to get to the important part of my inquiry. if you don't want to read about what I have tried already.
Before you suggest the obvious, replace lcd, let me say that the motherboard lcd connector is damaged beyond repair. water damage, but the phone boots normally and seems to run fine. phone calls ring and other sounds indicate the phone is able to function but no display or touch function obviously. the usb port works. Also there is no samsung account on the phone so that option to bypass screen lock does not help. Kies, smart switch, etc don't help due to the "screen lock"
ie... There is a basic swipe to unlock "lock" on the phone, so otg cable options also hit a dead end. There are workarounds to bypass other lockscreens, but no way to do the swipe over otg that I can find. And even if/once I am able to swipe to unlock over otg, there are other obstacles to get around that may not be possible (click ok, navigate to enable usb debugging). If I am wrong here and there is an obvious solution I am missing, let me know (explain in detail if you can) and I will get the hub & cable back out and try again!
Dr.phone android recovery (data recovery/damaged device option) looks like the most promising, and here I have also run into trouble. Dr phone will put the phone into download mode but then always seems to fail "flash recovery package failed" at some percentage. dr.phone downloads the recovery package (I am selecting the correct model n910v) successfully, but the percentage before flash recovery package fails changes. It hasn't made it past 85%. the dr.phone log files don't reveal anything to my untrained eye.
Before running dr.phone, adb "permission denied"...after using dr phone, however, while the phone is still powered on and in download mode, once I close dr phone, I am able to start to get somewhere with adb! adb devices shows the phone as an emulated device, and (some) adb commands start to work! I think if I just am able to find the exact location of the stock messaging log, I will be very close.
If anyone can suggest some commands to try in adb to grab just the sms log I would be very grateful!
I can run "adb backup", and have tried a few other adb commands, but none of the standard backup commands actually contain a sms log.
***Anyway, I think the best option might be to flash a custom recovery after getting the phone in download mode & adb working successfully (showing as an emulated device) with dr.phone as described above... However I have no way to tell what firmware version the phone is running (don't want to brick it or loose data), and I am really looking for specific directions on which clockworkmod or twrp recovery file to try for n910v, that will allow me to get a sms backup, and/or a recovery that will have usb debugging enabled.
Thanks for the input! sorry for the rambling post, I hope it's possible to make sense of it.. ANY help greatly appreciated!
beefriendly said:
I have hit dead end after dead end, after many hours, just want to get copy of text messages off this phone somehow, and then erase all data. I have spent many hours on this, my level of experience with all this is beginner/intermediate, as I'm sure you will be able to tell by the ramble below. Skip to the last paragraph **** with the asterisks to get to the important part of my inquiry. if you don't want to read about what I have tried already.
Before you suggest the obvious, replace lcd, let me say that the motherboard lcd connector is damaged beyond repair. water damage, but the phone boots normally and seems to run fine. phone calls ring and other sounds indicate the phone is able to function but no display or touch function obviously. the usb port works. Also there is no samsung account on the phone so that option to bypass screen lock does not help. Kies, smart switch, etc don't help due to the "screen lock"
ie... There is a basic swipe to unlock "lock" on the phone, so otg cable options also hit a dead end. There are workarounds to bypass other lockscreens, but no way to do the swipe over otg that I can find. And even if/once I am able to swipe to unlock over otg, there are other obstacles to get around that may not be possible (click ok, navigate to enable usb debugging). If I am wrong here and there is an obvious solution I am missing, let me know (explain in detail if you can) and I will get the hub & cable back out and try again!
Dr.phone android recovery (data recovery/damaged device option) looks like the most promising, and here I have also run into trouble. Dr phone will put the phone into download mode but then always seems to fail "flash recovery package failed" at some percentage. dr.phone downloads the recovery package (I am selecting the correct model n910v) successfully, but the percentage before flash recovery package fails changes. It hasn't made it past 85%. the dr.phone log files don't reveal anything to my untrained eye.
Before running dr.phone, adb "permission denied"...after using dr phone, however, while the phone is still powered on and in download mode, once I close dr phone, I am able to start to get somewhere with adb! adb devices shows the phone as an emulated device, and (some) adb commands start to work! I think if I just am able to find the exact location of the stock messaging log, I will be very close.
If anyone can suggest some commands to try in adb to grab just the sms log I would be very grateful!
I can run "adb backup", and have tried a few other adb commands, but none of the standard backup commands actually contain a sms log.
***Anyway, I think the best option might be to flash a custom recovery after getting the phone in download mode & adb working successfully (showing as an emulated device) with dr.phone as described above... However I have no way to tell what firmware version the phone is running (don't want to brick it or loose data), and I am really looking for specific directions on which clockworkmod or twrp recovery file to try for n910v, that will allow me to get a sms backup, and/or a recovery that will have usb debugging enabled.
Thanks for the input! sorry for the rambling post, I hope it's possible to make sense of it.. ANY help greatly appreciated!
Click to expand...
Click to collapse
This tool might work for you. Ive never used it myself but it looks promising. It supposed to be able to control your phone on your pc.
For the custom recovery, it should tell you what model you have when you boot into download mode but the TWRP for the note 4 has been unified so it should work either way. This link is for the most recent version. Get the .tar file if you're looking to use ODIN to install it.
Thanks for the reply! The tool you inked to requires USB debugging switched on. I was looking at it previously but didn't consider it because of this. I have USB debugging off, and the process I described with the dr phone windows application /download mode, doesn't turn usb debugging on.
Is there a way that I can flash a recovery for the note 4 that has USB debugging enabled from the start? If anyone knows please describe the process or post the link.
I think I need step by step instructions or screen shots for what to do with the Note 4 twrp recovery. I am trying to acquire a second phone so I can view the screen and know what buttons to press, but so far it is not looking like I have enough information to do sms backup from the twrp menus..on the device when I can't see the screen.
I see reference to being able to use adb commands to control the twrp recovery / backup process, but so far I haven't found anything that will help for my particular situation. If anyone knows what adb commands to use to pull the note 4 sms files , or a backup that includes them, PLEASE let me know.
thanks again