I just got a used HTC One after being iPhone user ever since the very first one. I don't know what he did to it he only said it was unlocked for any carrier. I noticed the phone is acting a little bit weird, specially when I connect it to my MAC to try to sync some music, it makes my mac to freeze every time. I notices some USB Debugging every time I connect to my mac. So my friend told me, maybe the phone is rooted(whatever that means). He told me to find some icon saying SuperSU and when I click on it it says " There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just updated to Android 4.3, you need to manually re-root- consult revenant forums for your device". Well here I am trying to solve this problem. I just want to use my phone normally for now and sync music without my mac crashing all the time.
Can I just restore to an untouched andirod firmware just like I did on iPhone? Please any help is appreciated. I have some computer skills I used to jailbreak iPhone and hack PSP to run emulators. I also have a Windows computer available if needed. My friend told me is not easy but I think I can I just need to be pointed in the right direction and given NOOB level details.
I assumed this guy rooted the phone to be able to use it with any carrier then he updated and messes the crap out of it.
Writeu p
should I follow this write up to root? Is this like a clean install?
Related
Hey I am in need of some help.
Yesterday I decided that I need to root my ATT Motorola Atrix 4G in order to be to able to install third-party software and have the option of checking the unknown sources option and have full functionality of the phone.
So, I started by using the program Superoneclick and I followed all the instructions to the tee. During the rooting or shell rooting process it would freeze up at the 'running psneuter' and then loops and give me this message 'If it keeps looping, try disabling USB debugging now'. I did as it told me and it did not work. I tried the process over and over again for about 2-3 hours and still got the same issues.
So, after hours of researching and trying Superoneclick. I decided to use the Gingerbreak.exe found at briefmobile.com. So that worked I think because in Titanium backup it says it is rooted. What puzzles me is that the phone is supposedly 'rooted' but I don't have the unknown sources option to be checked. Also the superusers icon showed up but I do not even know what to do with that.
I would like assistances or advice when it comes to properly rooting my ATT Motorola Atrix 4G.
Thank you to anyone that can help.
my device doesnt show an option box to enable or disable sideloading but i can still sideload. i am pretty sure that i read the guy that made the hack didnt bother with the check box
also, if it doesnt work for you there is an app you can download from android central called the side loading wonder machine (or something like that). i have used it too and it works great when you are connected to your pc
I want to be able to install produces without having to keep connecting my phone to the computer.
Have you actually tried to install non market apps since rooting? As I said earlier, my phone doesn't indicate that I can side load but I can
Yes and it tells me i can't install it because i need to check that box. Which leads me to believe that the phone is not truly rooted. What do you think?
Being rooted and being able to side load are two different things. It sounds like you are rooted already so now you just have to enable side loading. Read the this thread carefully and see if it solves your issue
http://forum.xda-developers.com/showthread.php?t=1016060
Thanks...what will this do exactly? and will i be able to receive the updates from att for the atrix still?
I did everything you did and it worked wonderfully thanks.
One more questions. How come I can install over the air from the market when i am on my pc? Why do i have to do it from the phone directly?
Purenuttah said:
I did everything you did and it worked wonderfully thanks.
One more questions. How come I can install over the air from the market when i am on my pc? Why do i have to do it from the phone directly?
Click to expand...
Click to collapse
Is your question that you can or cannot use your pc to download to your phone over the air? You should be able to use your pc to push an app onto your phone from the market without wires.
Sent from my MB860 using XDA App
When i am on the market website on my pc and i try to push an app to my phone it doesnt work. I have to go into the market store from my phone in order to get the app.
Just curious, what does this have to do with rooting?
Sent from my Greyblurred Atrix
Well i originally was having rooting issues. Now that I was helped and finally got my phone rooted i am experiencing this issue after rooting my phone. So why start a new thread?
i need help, i have tried everywhere and can't find anything and any help would be greatly appreciated
i'm on the road to root my samsung galaxy fascinate and have ran into a laundry list of problems. i have rooted many android phones coming from eclair, froyo, and gingerbread, but seem to be stuck at the slightest of problems when it comes to the fascinate.
i can not install the drivers to the fascinate. i have searched through the web for all the drivers and have tried every possible galaxy driver. the driver simply won't install on my windows 7 prof 64bit machine. i have never ran into this problem before with any other phone. every time i try to install the driver it gets to the very end of the install then pops up with the message "windows was unable to install the driver"
It also gave me the option to view the failed windows installation log, which after many successful steps, at the end the log shows this error:
Action ended 1:26:53: ShowMsiLog. Return value 0.
=== Logging stopped: 12/16/2011 1:26:53 ===
MSI (c) (0C:08) [01:26:53:750]: Product: SAMSUNG USB Driver for Mobile Phones -- Installation operation failed.
MSI (c) (0C:08) [01:26:53:750]: Windows Installer installed the product. Product Name: SAMSUNG USB Driver for Mobile Phones. Product Version: 1.3.550.0. Product Language: 1033. Manufacturer: SAMSUNG Electronics CO., LTD.. Installation success or error status: 1603.
i have also attached the entire log
the first thing i did was plug in the phone, which windows sensed this and automatically installed a driver, not sure which. after this i unplugged the phone and then checked "usb debugging" for rooting purposes and plugged the phone back into the computer which windows then installed another driver automatically, then following the steps from xda to root the phone, i downloaded the given drivers which is where the problem first occurred and the drivers were unable to download.
I'm simply trying to get root access to the phone and can't do anything with the phone with crappy drivers...i can't even mount usb sd card now to transfer data anymore. the drivers have completely been shot. i desperately need help. please
also what is the absolute easiest way to root the fascinate? is it with one click root or with Odin? Because the fascinate just updated itself from 2.2.2 EH05 to 2.3.5 EH03 and i'm not sure which program supports rooting which version of android. also all other android devices simply give root access to the stock rom, which is great cause i get to keep all my apps, messages, contacts...etc, then simply titanium backup everything and transfer it over to the new rom. is it different with the fascinate? will rooting the device simply flash a completely new rooted rom? therefore loosing everything? if anybody has any answers to any of these questions, please be my hero. thanks
Uninstall everything you previously installed in the way of Samsung drivers (in fact, you could use Windows 7 backup and restore to restore your PC to the state it was in the day before you installed the drivers as they are sometimes hard to uninstall completely). Reboot and simply plug your phone (with USB debugging of course), and let Windows automatically install the drivers for you like it did before you installed the ones linked to on XDA. This time, if your PC recognizes your phone, just keep the drivers you have and don't install the ones linked to. Those drivers from the guide are for those whose PC doesn't automatically install working drivers. From that point, just follow the rest of the guide and skip the install drivers part. You will not have to install any further drivers unless you flash an AOSP ROM, in which case you'll have to follow the instructions in the OP of the ROM thread. I hope this works for you.
Has anyone seen John Connor?
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
bigwhat said:
awesome thank you, i will try this out, and if this doesnt work i can always try another pc.
and as to the question of rooting the fascinate, like i said before i've never had a phone that has been wiped when i got root access initially, but it seems that everyone is saying that a rooted rom must be flashed from Odin in order to have root access. In other builds it seem that all is done is busybox and superuser are just pushed to the phone. will the fascinate be wiped when initial root is acquired?
Click to expand...
Click to collapse
root is not flashed via odin, rather cwm is...then the root file su_2.6.3.1 is flashed via cwm. If you need directions section 5 of my guide in general section has it covered...everything needed is there including the correct recovery and root file.
I will tell you what...the Fascinate is probably the biggest pain in the ass phone...I tried forever to root my friends and couldn't get it done...need to try again I guess, but it was a driver issue as well..ODIN just wouldn't recognize the dam phone
Use Droidstyles guide. Very easy to follow. Also, the USB cable for some reason seams to be a bit finicky at times with this device. Unplug from phone and replug. Sounds odd but trust me, I have done this many times.
Sent from my SCH-I500 using XDA App
I am having a problem too and it's not covered anywhere i've seen to date. I've got an XP and a Win7 box at home. On both, I've tried with no drivers and i've tried with every other driver set I can find and every time I hook the phone up to the machine it pops up saying USB device couldn't be recognized or something. I'm going nuts! I've never had so much difficulty in my life, not even the first time changing ROMs on anything.
Droidstyle- I've seen your guide and unless I missed it doesn't cover this. Have you seen or heard of this and have any ideas at all?
Thanks!
Tried ViperMod, SparkyRoot with no success.
SparkyRoot fails at stage 2 as Asus Backup fails every time...
With ViperMod i can't see the device when connected to MacBook Air [./ADB devices - no devices listed]
SO... either looking for a way to get something like SparkyRoot to work or tips on how to get TFP visible with Mac OSX Lion OR something new.
Please devs help a man out!!
I also use a Mac and have rooted just fine using ADB Push.
If it's not detecting your device it sounds like you haven't enabled USB Debug Mode in Settings -> Developer. I'd double check that.
Thanks - yes tried all the usual stuff - must have read 100's of posts in case I'm missing something silly.
Tried on Mac OSX Lion - MacBook Air and Mac Mini
Mac OSX Tiger - old iBook
and even built a VM on Mac Mini running XP [scuppered there as couldn't get ADB drivers to work]
I wouldn't mind if I was fumbling around with the wrong commands in Terminal or something, but i'm not even getting the damned thing to be seen on any PC/Mac except as a sync device or camera.
Please please somebody find a true 'one stop root' that doesn't need tethering or ADB.
I really want to get bootloader unlocked, CWM and CM9 on this thing - and unleash the real potential.
trying to use SparkyRoot but need help please, asus prime TransformerTF201
Trying to use the SparkyRoot but getting message in step 1 saying exploit not working, then step 2 fails to backup. Am i supposed to have installed other stuff first?, or how can i get this to work
Just root manually through adb, it's easy enough if you know how to read.
still need specifics
rand4ll said:
Just root manually through adb, it's easy enough if you know how to read.
Click to expand...
Click to collapse
ok, i can do that :-> , but can you give me a specific link or directions, an it needs to be very specific breakdown of directions, i'm a total newbie, and don't even know what you mean by adb!! Yes there are still some of us like that who exist out there, :-€ but can follow a very laid out step by step procedure. Please don't say search cause then so much comes up an i'm just boggled! :9)
Root method for windows or Mac?
Is there a root method for the .15 build available for windows or Mac? I do not have linux. I have a Chinese machine and want to install the proper android market. I have found the instructions of what to do once the machine is rooted, but cannot get to root itself to work. Tried using Primetime, but that only works upto .11 from what I can tell.
Cheers for any replies,
David
Right, Ive had my TF201 for a good while now and I successfully rooted it once before. However I lost my root at one point when doing updates without realising the possibility of that happening. Now I hadnt bothered to look in to the matter too much over the past 6 or so months but now that I started dabbling with my tablet again I've come to realise that no matter which machine I connect the prime, it wont be recognized by ADB.
I've tried with Windows 7 64 and 32 bit machines and one ubuntu (I even tried to manually route the ADB to right tracks, but no avail).
When connecting to Windows machine, only unknown device shows up in the device manager and the drivers cannot be applied to the device.
Now I'm no expert in this whole topic, otherwise I wouldnt be where I am right now but the only conclusion is that my device is bricked to some degree. Can someone help me clean up my mess? >.< -or is it even possible to begin with?
Current situation: The device is sitting at Android 4.1.1 and Firmware 10.4.2.17 and the device is asus unlocked. Since the device isnt rooted my Voodoo OTA Rootkeeper and ROM Manager are completely useless because they were installed after the (possible) bricking happened.
Where should I go next?
ichihaifu said:
Right, Ive had my TF201 for a good while now and I successfully rooted it once before. However I lost my root at one point when doing updates without realising the possibility of that happening. Now I hadnt bothered to look in to the matter too much over the past 6 or so months but now that I started dabbling with my tablet again I've come to realise that no matter which machine I connect the prime, it wont be recognized by ADB.
I've tried with Windows 7 64 and 32 bit machines and one ubuntu (I even tried to manually route the ADB to right tracks, but no avail).
When connecting to Windows machine, only unknown device shows up in the device manager and the drivers cannot be applied to the device.
Now I'm no expert in this whole topic, otherwise I wouldnt be where I am right now but the only conclusion is that my device is bricked to some degree. Can someone help me clean up my mess? >.< -or is it even possible to begin with?
Current situation: The device is sitting at Android 4.1.1 and Firmware 10.4.2.17 and the device is asus unlocked. Since the device isnt rooted my Voodoo OTA Rootkeeper and ROM Manager are completely useless because they were installed after the (possible) bricking happened.
Where should I go next?
Click to expand...
Click to collapse
Sounds like the cable is faulty. Borrow a new one to test or get a cheap one off eBay.
flumpster said:
Sounds like the cable is faulty. Borrow a new one to test or get a cheap one off eBay.
Click to expand...
Click to collapse
While I find that unlikely, I will try to look for a new one. But meanwhile lets assume that its not indeed the case, is there anything I could do at that point?
ichihaifu said:
While I find that unlikely, I will try to look for a new one. But meanwhile lets assume that its not indeed the case, is there anything I could do at that point?
Click to expand...
Click to collapse
Why do you find that unlikely?
There are cases exactly the same as yours all over this forum where the cable can charge the prime but cannot be used to install drivers etc.
http://forum.xda-developers.com/showpost.php?p=37662700&postcount=539
http://forum.xda-developers.com/showthread.php?p=39303129&highlight=cable#post39303129
flumpster said:
Why do you find that unlikely?
There are cases exactly the same as yours all over this forum where the cable can charge the prime but cannot be used to install drivers etc.
http://forum.xda-developers.com/showpost.php?p=37662700&postcount=539
http://forum.xda-developers.com/showthread.php?p=39303129&highlight=cable#post39303129
Click to expand...
Click to collapse
Hmm, alright. Just because I havent really roughed up the cable at all and everything worked fine until the said date.
But for now theres no way to try another cable, I'l look for new one next week.
ichihaifu said:
Right, Ive had my TF201 for a good while now and I successfully rooted it once before. However I lost my root at one point when doing updates without realising the possibility of that happening. Now I hadnt bothered to look in to the matter too much over the past 6 or so months but now that I started dabbling with my tablet again I've come to realise that no matter which machine I connect the prime, it wont be recognized by ADB.
I've tried with Windows 7 64 and 32 bit machines and one ubuntu (I even tried to manually route the ADB to right tracks, but no avail).
When connecting to Windows machine, only unknown device shows up in the device manager and the drivers cannot be applied to the device.
Now I'm no expert in this whole topic, otherwise I wouldnt be where I am right now but the only conclusion is that my device is bricked to some degree. Can someone help me clean up my mess? >.< -or is it even possible to begin with?
Current situation: The device is sitting at Android 4.1.1 and Firmware 10.4.2.17 and the device is asus unlocked. Since the device isnt rooted my Voodoo OTA Rootkeeper and ROM Manager are completely useless because they were installed after the (possible) bricking happened.
Where should I go next?
Click to expand...
Click to collapse
I gained root on 4.1.x via twrp and supersu, just after unlocking it. I am not shure if reinstalling 4.1.was really useful...but I did.
I'm Fairly New To The Android Concept, And I See Its A Little Bit More To Trying To Jailbreak It Vs. The iPhone, I'm Getting Stuck Using The Casual "NoYouVerizon" Concept Of The "One-Click" Method, But As Going On, I Don't Understand The Log's, I've Tried Searching For It Constantly, And I've Been At This For A Week Straight Now, I Need STEP by STEP Instructions On What To Do, Because I'm Reading Alot Of Different Things, And It's Not Really Helping Me At All, I Have A Verizon Samsung Galaxy Note 2, With Version 4.1.2 On It, and I Have *Correct Me If I'm Wrong* VRAMC3? If Thats The Right Thing. Please Somebody Help Me. Send Me A Message For My Contact Information. I Wanna Get This Done Pleasee!!!
theres the step by step guide
http://forum.xda-developers.com/showthread.php?t=2024207
One click root not working XDA. Someone needs to go back in and put the fix in for ERROR: No partition with identifier "60" exists in the specified PIT
Ive tried everything so far, even uninstalling the phone driver driver to allow samsung driver to reinstall, even manually installed the dev driver. I even tried to use odin3 to install via xda instructions. Odin can detect device if I just plug the phone in but if I put the phone in down load mode and connect, nothing. I checked device mgr and it shows the device in usb connections. WTF, XDA is verizon winning??????
Update:
Well I did discover after all this that I am rooted but I think that s all. When I plugged my phone into the computer Casuals usb showed in the Device Mgr screen instead of Samsung. To confirm I downloaded root checker from the play store and I am rooted via super user. Theres an issue though with putting the phone in download mode and odin detecting.
Update 2
Well it finally just worked and I was able to get odin to detect the phone while in download mode. I am now on root66 !! Help for others: Be persistent, I think it took time for my pc to accept and activate the changes IE: the casual driver replacing the samsung. It literally just happened after about 5 or 6 failed attempts of running the one click root. And it happened after a couple of samsung driver deletions. When the phone was plugged in, I went to device manager on the pc , usb devices and deleted the samsung drivers. I wound up doing this about 3 times. I restarted my computer after this to. Then I plugged the phone in again and there was casual usb controller appearing in device manager, replacing samsung. That was when I discovered I was rooted even though I had gotten the error message that started this post. Later, I went ahead and was able to install root66 by following the xda directions. wow......it was an all day affair but hopefully this will take some of the grey area out for others with this problem.
Thank you XDA for working to [email protected]^! this phone that verizon and google so graciously shoved up our #$% with a warm smile. The wi fi button for the notification bar is not available, I believe this is due to verizon when they put their stink on the phone. I would like to get that back if possible. Also the google search popping up when you plug the headset jack in is still there, but you can go into settings/task mgr/ all aps and scroll down to google search and disable it. The annoying pop up voice search hasnt showed up since I did this.