Ok so I am having a strange issue here. I tried to root my buddy's incredible using the newest version of unrevoked. It went through successfully but I noticed when going into the bootloader that it still states S-ON. Also, when I click on Recovery, it takes me to a black screen with white lines on the side. I have tried flashing the recovery multiple times by using the PB31IMG.zip method to no avail. I am guessing at this time the root did not take. So when I try to use Unrevoked again it tells me that root is unsuccessful, my software may be too new (or something to that affect. I have tried it 3 more times, no dice. Just for ****s, I downloaded terminal and it works, I can get superuser access. I tried flashing a recovery at that point with the flash_image method and that doesnt work either, it says image not found or something like that. I dont know if it rooted and didnt turn S-OFF, or if it isn't rooted at all. I tried downloading and just going back to an unrooted stock rom and it said that the software version is older and failed. I have been at it for hours. Please someone help. Thanks in advance.
I don't know why ADB is not working while normally booted! It works when in recovery, please help me. I am using Senseless version 3.7.1
cwest31 said:
I don't know why ADB is not working while normally booted! It works when in recovery, please help me. I am using Senseless version 3.7.1
Click to expand...
Click to collapse
Read this entire guide.
blackknightavalon said:
Read this entire guide.
Click to expand...
Click to collapse
koooooooooooool
reinstalled sdk following instructions carefully! its not an sdk problem
cwest31 said:
reinstalled sdk following instructions carefully! its not an sdk problem
Click to expand...
Click to collapse
ADB is part of the SDK.
Sent from a message in a bottle.
cwest31 said:
I don't know why ADB is not working while normally booted! It works when in recovery, please help me. I am using Senseless version 3.7.1
Click to expand...
Click to collapse
There is literally no information in this posting that someone can use to help you.
Blackknightavalon's direction to the SDK webpage is about as helpful of a reply as you can expect to solicit with the information you have provided.
This is like going to a car forum, and saying " I have a blue camaro. It won't start. I tried turning the key. Help please"
What commands are you trying to run through adb?
What errors are you getting, if any?
What do you see when you type "adb devices"
What operating system are you running on the computer you are trying to connect from?
Have you turned on "usb debugging" in the options menu on the phone?
There are a whole lot of things that can be your problem, and we'd love to help, but we can't help you if you don't tell us what's wrong.
Doubtless someone else will get back to you before I get a chance to, since my time is very limited these days online, but posting some more information about your problem will elicit a response that may actually help you.
Best of luck!
Blue6IX said:
There is literally no information in this posting that someone can use to help you.
Blackknightavalon's direction to the SDK webpage is about as helpful of a reply as you can expect to solicit with the information you have provided.
This is like going to a car forum, and saying " I have a blue camaro. It won't start. I tried turning the key. Help please"
What commands are you trying to run through adb?
What errors are you getting, if any?
What do you see when you type "adb devices"
What operating system are you running on the computer you are trying to connect from?
Have you turned on "usb debugging" in the options menu on the phone?
There are a whole lot of things that can be your problem, and we'd love to help, but we can't help you if you don't tell us what's wrong.
Doubtless someone else will get back to you before I get a chance to, since my time is very limited these days online, but posting some more information about your problem will elicit a response that may actually help you.
Best of luck!
Click to expand...
Click to collapse
Make sure you have current adb drivers for your phone. It will show android composite in device manager. Fastboot will show fastboot device. Seeing a yellow question mark is bad.
Make sure your pathing is set up right.
Typing "adb devices" and if you see your device. If so you're ready to roll.
I usually get fastboot errors like this when I don't have drivers installed right.
sent from my Agent Orange MT4G Slide using xda premium
Droidmoder said:
Make sure you have current adb drivers for your phone. It will show android composite in device manager. Fastboot will show fastboot device. Seeing a yellow question mark is bad.
Make sure your pathing is set up right.
Typing "adb devices" and if you see your device. If so you're ready to roll.
I usually get fastboot errors like this when I don't have drivers installed right.
Adb is part of the adk. It's to help debug and install things via a directlink to the computer. Its found in platform tools and is considered a dev tool.
sent from my Agent Orange MT4G Slide using xda premium
Click to expand...
Click to collapse
sent from my Agent Orange MT4G Slide using xda premium
I get Error Message with ADB
Hey guys, so I perm rooted with S-OFF my mytouch 4g slide, with theunlockr.com youtube video and guide using revolutionary. then I attempted to install a ROM with ROM MANAGER, and it got stuck on the splash/loading screen. After some searching I found out that this meant that I could have potentially BRICKED the phone, so I followed theunlockr.com's guide to UNROOTING the phone, and it worked, I flashed the original stock tmobile rom, and it loaded fine, I tried to start the whole process again, but now I get stuck in the very beginning, trying to get TEMP root, I start the fr3vo exploit like the guide stated, but then i keep getting error messages on the command line prompt saying that there is an error with ADB, then when I power the phone with volume down and power, the revolutionary is no longer on the top of the screen, but it still says SHIP S-OFF. Does that have to do anything with my problem? is there a way to GET S back to ON, so I can start the process over? or am I better off having S off??? I installed ROM MANAGER and tried to flash a recover image thinking that having S off would allow me to do this, but I get error messages saying there are problems with the permissions. the web site for the guide I used to root is this one incase anyone wants more details into what I did, any help would be greatly appreciated. theunlockr.com/2011/09/09/how-to-permanently-root-and-gain-s-off-on-the-t-mobile-mytouch-4g-slide-revolutionary-method
Use perm root method. Myself I flashed oneclick in recovery, but you can follow the guide the perm root part.
Btw rom manager supports flashing of the new cwm only. I checked the roms in rom manager they aren't supported. You have to go to the cm7 thread here and download and flash cm7 from recovery.
Just redo root process and install cwm from rom manager. Then go to the dev section and flash your favorite rom in recovery. My sig has directions on how to do everything.
Also if you're having permissions error use root explorer on the rom manager apk make sure it has execute checked. Also I think rom manager has a fix permissions button. Its never worked for me.
S off will allow flashing of cwm. However you need to be rooted to flash cwm threw rom manager. My sig has a guide on installing cwm without being rooted.
sent from my Agent Orange MT4G Slide using xda premium
Thanks for the QUICK reply, but I looked at the guide, and it stated I have to have recovery installed, BEFORE I do the perm root method, but I dont have recovery, when I do HBOOT, and I try to boot into recovery, I get a red exclamation mark on the screen and I have to end up taking out the battery. Thats why I was wondering if having S OFF from the beginning now is what is messing me up when I am trying to ROOT again, I mean, I am doing the same steps.... just now I get errors when I try to do the TEMP root step... so I cant continue... and I cant get ROM MANAGER to flash a recovery image... is there a guide or steps someplace that can guide me to root the MT4G slide already having S off?
I found the problem myself, I had to enable USB Debugging.
I had USB debugging enabled.... hmmmm you made me doubt myself... I guess I will try it again, since I flashed stock rom again all settings were reverted... so I cannot VERIFY I had USB debugging on, but I was sure I did... I will try again and post... I am reflashing the stock rom like 5 times a days trying to root again =(
wait... cwest31, you had which same problem? because I was writing about 2 problems: about booting into recovery with S off, but no recovery image (hence I got red exclamation mark), and trying to get ROM MANAGER to flash a recovery image on my phone since I have S off already, but I get error messages (problem with permissions)
RT2023 said:
I had USB debugging enabled.... hmmmm you made me doubt myself... I guess I will try it again, since I flashed stock rom again all settings were reverted... so I cannot VERIFY I had USB debugging on, but I was sure I did... I will try again and post... I am reflashing the stock rom like 5 times a days trying to root again =(
wait... cwest31, you had which same problem? because I was writing about 2 problems: about booting into recovery with S off, but no recovery image (hence I got red exclamation mark), and trying to get ROM MANAGER to flash a recovery image on my phone since I have S off already, but I get error messages (problem with permissions)
Click to expand...
Click to collapse
Umm...did you read the full instructions very carefully? When you get to the part where you flash the Superuser .zip file, you need to try it several times before it'll hold.
blackknightavalon said:
Umm...did you read the full instructions very carefully? When you get to the part where you flash the Superuser .zip file, you need to try it several times before it'll hold.
Click to expand...
Click to collapse
What he said.
Also ROM MANAGER WILL NOT WORK UNLESS ROOTED. Get rooted then try flashing the image. The compendium also has step by step guides using terminal emulator once rooted
sent from my Agent Orange MT4G Slide using xda premium
Also I want you op and the other one to be clear on what s off is and root.
Getting S OFF allows unsigned zips to be flashed. This means you can now flash roms and root. Without s off you cannot root, rom, kernels. S OFF is not root.
Root is gaining admin rights over your phone. this allows programs that require access to the root files to have access to them. ROM Manager, titanium backup, drocap, setcpu will be granted access to the root files and programs which unrooted phones would not be granted access .
This can be a reason why you two are having trouble using rom manager unrooted. Rom manager cannot access the files it needs
sent from my Agent Orange MT4G Slide using xda premium
Please go follow this thread ---> http://forum.xda-developers.com/showthread.php?t=1178606. It tells you how to Permanently root a device that is already s-off.
AWESOME!!! turns out i just had to run revolutionary TWICE, and the second time it figured out it was already rooted and then asked if I wanted to install recovery, I dont know how to do it manually so I clicked yes, and THEN i was able to go into recovery and flash the PERM root ZIP, rebooted and i had SUPERUSER in my app drawer!!!! awesome, now to try to get the version of google talk installed that actually allows for video chat!!! I HATE QIK!!!!!!
DROIDMODER, CWEST31: Thanks so much for the lenghty explanation and help. I have loved android for the ability to customize, and I had the G1, MOTOCLIQ, G2, and now MT4GS, I rooted my G2, but didnt do anything to it because i was scared to F it up, but with the MT4GS I got the balls to do it just because I was SOOOO UPSET that the phone comes with a version of GTALK that does NOT ALLOW FOR VIDEO CHAT!!?!?! WTF!!! whats the front camera for then?! and QIK sucks, not all my friends are on tmobile... i was even more upset when the HTC AMAZE has a version of GTALK that does allow for video chat straight out of the box!!! this is my main push to wanting to root... thanks for letting me vent! lol and thanks for all your great info
RT2023 said:
AWESOME!!! turns out i just had to run revolutionary TWICE, and the second time it figured out it was already rooted and then asked if I wanted to install recovery, I dont know how to do it manually so I clicked yes, and THEN i was able to go into recovery and flash the PERM root ZIP, rebooted and i had SUPERUSER in my app drawer!!!! awesome, now to try to get the version of google talk installed that actually allows for video chat!!! I HATE QIK!!!!!!
Click to expand...
Click to collapse
Your welcome! now procead to install undead's senseless ROM (Best Rom available) and also get rom manager and flash the official CWM recovery! Also proceed to "thank."
mmmm... I tried to install a ROM before and thats what F-ed everything up =/ I am hesitant, I really want a Gtalk version that allows for video chat, does the senseless rom have video gchat capabilities??
Hello,
I am having problems with perm rooting my new UK One X handset, I have managed to unlock the bootloader using Hasoons2000 all in one kit v1.0 however when I try and root the handset it keeps failing.
Basically if I press the perm root button, the phone goes into recover however it just says there and the command prompt shows that the phone is not connected so cant root.
I have even tried updating the clockwork recovery img however that is failing as well..
can am I doing wrong?
Many Thanks
Scott
I think you are in the wrong One X forum
I think you may be in the wrong forum. try this one:
http://forum.xda-developers.com/forumdisplay.php?f=1533
Hey guys, I'm new here and im looking for help. YES, I have already tried a million different things, YES my SDK is properly installed, YES my bootloader is unlocked from HTC dev, and NO, no method for rooting my shiny new HTC One X has worked so far. Ive spent countless hours on this forum, and have done everything possible, but to no avail, so its time for me to turn to you guys and ask for help.
My HTC's firmware is 1.94 which seems to be very uncommon, as most people have the 1.80 or 2.20 version.
I am running stock Rogers firmware with Android 4.0.3.
I have come close, I have even successfully done the whole daemon DOS process, but it had many errors, and even though the result said that the phone was successfully rooted, it did not install SU. However THERE IS A BROWN BAR that appears on the upper left side of the screen during the HTC boot sequence, and it only appeared after the daemon process.
Please, if someone could lead me in the right direction, id be very grateful. What should I do?
You don't need any fancy root processes. If you want to stay stock but rooted. Install twrp. And flash a stock rooted Rom. Or flash the superuser zip in twrp.
Sent from my HTC One XL using xda app-developers app
Follow instructions on htcdev to unlock unlock bootloader.. download goo manager and install twrp. Flashed rooted Rom and profit.
Sent from my HTC One XL using Tapatalk 2
Hey guys I have been searching all over the place for this answer and I just cant seem to find anything on the topic.
This is my first time tinkering with my HTC One X (old version 4.0.3) and downloaded the most updated drivers which is where I believe I went wrong.
I have the 4.2.0.001 drivers and when I open the root.zip file nothing happens I get no errors I just get the "your HTC One X is rooted..." yet my phone simply doesn't reboot.
So I attempted to install the downgraded drivers the 3.0.0.007 which looking back has been the recommended drivers, however; when I extract those files and head into my device manager it does not pull up the androidusb.inf file to upload the 3.0.0.007 drivers.
Am I missing a proper BMP USB Driver and where can I find it? Or is there a root file that will work with the 4.2.0.001 drivers?
If there is any link to this topic please post it, I am very new to rooting or if I have made any mistakes please let me know.
social_spider said:
Hey guys I have been searching all over the place for this answer and I just cant seem to find anything on the topic.
This is my first time tinkering with my HTC One X (old version 4.0.3) and downloaded the most updated drivers which is where I believe I went wrong.
I have the 4.2.0.001 drivers and when I open the root.zip file nothing happens I get no errors I just get the "your HTC One X is rooted..." yet my phone simply doesn't reboot.
So I attempted to install the downgraded drivers the 3.0.0.007 which looking back has been the recommended drivers, however; when I extract those files and head into my device manager it does not pull up the androidusb.inf file to upload the 3.0.0.007 drivers.
Am I missing a proper BMP USB Driver and where can I find it? Or is there a root file that will work with the 4.2.0.001 drivers?
If there is any link to this topic please post it, I am very new to rooting or if I have made any mistakes please let me know.
Click to expand...
Click to collapse
Drivers are drivers. You can root with either. Old new, doesn't matter. It just allows your phone to be recognized by fastboot and ADB, that's all.
exad said:
Drivers are drivers. You can root with either. Old new, doesn't matter. It just allows your phone to be recognized by fastboot and ADB, that's all.
Click to expand...
Click to collapse
Thank you :good: so this means its something wrong with the root.zip file or the process Im doing to root? I just attempted it a few seconds ago this time the phone rebooted 2 times but I am not seeing any Su app on my phone
social_spider said:
Thank you :good: so this means its something wrong with the root.zip file or the process Im doing to root? I just attempted it a few seconds ago this time the phone rebooted 2 times but I am not seeing any Su app on my phone
Click to expand...
Click to collapse
The root methods simply give you temp root and super cid so you can unlock the bootloader. *facepalm*
Then when your bootloader is unlocked you can flash recovery and then flash su through recovery or install a custom rom which will already be rooted.
exad said:
The root methods simply give you temp root and super cid so you can unlock the bootloader. *facepalm*
Then when your bootloader is unlocked you can flash recovery and then flash su through recovery or install a custom rom which will already be rooted.
Click to expand...
Click to collapse
damn im an idiot haha thank you for clearing this up
I guess I am not understanding the core concept here, so I now I theoretically have a temp root with Super CID. I was under the impression that I was supposed to download Titanium Backup before attempting to unlock the bootloader. So I went to download and it told me I did not have root access so I could not run Titanium. I am afraid to attempt a bootloader unlock with out my rom being backed up. Can you please shed some light on this or post a link that would explain the process after temp root in detail thank you
social_spider said:
I guess I am not understanding the core concept here, so I now I theoretically have a temp root with Super CID. I was under the impression that I was supposed to download Titanium Backup before attempting to unlock the bootloader. So I went to download and it told me I did not have root access so I could not run Titanium. I am afraid to attempt a bootloader unlock with out my rom being backed up. Can you please shed some light on this or post a link that would explain the process after temp root in detail thank you
Click to expand...
Click to collapse
You can backup after your bootloader is unlocked.. bootloader unlock is just a flag that allows you to flash certain partitions like recovery.
Backing up before or after will make no difference. If you end up really messing up your device, a backup won't save you anyway so I don't see why you'd be worried. If you S-OFF, you can RUU to get back to stock any time no problem, unless you full on brick. Then only jtagg will save you.
Typically before I root a phone, I read all the stickies in all the subsections to understand how things work since every phone has differences, some subtle some not so subtle.
exad said:
You can backup after your bootloader is unlocked.. bootloader unlock is just a flag that allows you to flash certain partitions like recovery.
Backing up before or after will make no difference. If you end up really messing up your device, a backup won't save you anyway so I don't see why you'd be worried. If you S-OFF, you can RUU to get back to stock any time no problem, unless you full on brick. Then only jtagg will save you.
Typically before I root a phone, I read all the stickies in all the subsections to understand how things work since every phone has differences, some subtle some not so subtle.
Click to expand...
Click to collapse
Thank you very much before I unlock Im gonna hit the stickies and make sure I completely understand everything :good: