[Q] Incredible S (2.3.5) refuses to root!? - HTC Incredible S

Hey,
For the past 6 hours i've been trying to root my Incredible S so i can install ICS 4.0.3 and i've just had no luck!
I have absoloutly no 'rooting' experience (jailbreak experience, yes) and i have no idea how to install custom firmware/images/roms ect.
For the first 4 hours i just tried to get rid of S-on, after reading through about 50 articles i gave up and was told to go to htcdev.com and unlock my bootloader, which is done but i can't root the phone!
I've tried the following:
HTC Supertool v3 - Unlocked my bootloader but failed with 'S-on', said my phone was rooted but is not...
SuperOneClick - Looks like it worked but didn't...
Unlock Root - 'Failed to access Shell root'
Universal Androot - Incompatible
z4root - First time, got stuck on 'Running exploit in order to obtain root access'
Second time, got to 'Attempting to apply root' and stayed like that forever (tried removing battery and restarting)
My phone may (MAY!) be rooted, i was told to download ConnectBot and if it had '$' i was not rooted but if i had '#' i was, nevertheless it came up with '$'....
Please help! I am desperate to get TRUE ICS (and none of that ****ty HTC ICS thats coming soon...)
Thanks, Danz207

UPDATE!!
I had z4root version 1.10, so i upgraded to 1.30 and this time the second step was called 'Acquiring root shell' or something like that and then it closed, but it wasn't a crash, it faded out within half a second. Anyway i opened 'Rom Manager' and it told me that i needed to root first and ConnectBox still has '$'.......

Did you read through the stickies?
http://forum.xda-developers.com/showthread.php?t=1337105
Im guessing you're up to step 4 maybe
good luck mate

Have you tried the two links at the top of the dev forum? Read through them and you should be fine

Thank you markj338
markj338 said:
Did you read through the stickies?
http://forum.xda-developers.com/showthread.php?t=1337105
Im guessing you're up to step 4 maybe
good luck mate
Click to expand...
Click to collapse
IT WORKED! I have ClockWordMod on my phone and currrently backing up my current firmware!
THANK YOU SO MUCH!!!!

danz207 said:
IT WORKED! I have ClockWordMod on my phone and currrently backing up my current firmware!
THANK YOU SO MUCH!!!!
Click to expand...
Click to collapse
LOL seems you're happy

Related

[Q] I upgraded to FRG83D BIG MISTAKE. Want to get back FRG83

I update to FRG83D and I guess i lost root. I attempted to restore flash clock world mod again but .nothing happens when i confirm I tried to do a backup from Titanium backup and of course it says i'm not rooted. Then I tried to go into Superuser app and it asked me to update. I attempted to and I got an error the su was not updated. A zip file (su-2.3.1-bin-signed.zip) has been placed on your sdcard, please reboot into recovery mode and flash it to update your su binary.
Sorry for the long winded explanation, but i'm totally frustrated. I've been trying to fix this for 2hrs. Oh yeah I originally got root using universal androot and it still says im rooted. I clicked unroot but it doesn't work. I'm confused cuz androot says i'm rooted, but Superuser and Titanium backup says i'm not.
PLEASE HELP MEEE!!! I would like to get back cmod 6.1
was this:
cmod 6.1 rc1-n1
clockmod 2.5.1
kernel: 2.6.35.7
Build num: frg83
Now i'm this:
Android ver: 2.2.1
Kernel ver: 2.6.32.9-27240
Baseband ver: 32.36.00.28U4.06.00.12_7
Build num: FRG83D
fastboot oem unlock
Root again...
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials#Root
Sent from my Nexus One using XDA App
crachel said:
fastboot oem unlock
Click to expand...
Click to collapse
lol damn you evil bastards
Have some pity for the newbs
Newbs should start reading Wiki instead of wasting hours on irrelevant stuff
danger-rat said:
Root again...
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials#Root
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Thank you danger-rat. I'm back to stock frg83. It only took about 10mins. Now I'm trying figure out how to get back to root. None of the one click methods seem to be working. Superoneclick, z4root, androot. Once again Thank YOU
Super one click works for frg83 and frg83d. You will need a computer. I got it from the unlockr. It has step by step instructions. It was easy and works perfectly.
dls5375 said:
Super one click works for frg83 and frg83d. You will need a computer. I got it from the unlockr. It has step by step instructions. It was easy and works perfectly.
Click to expand...
Click to collapse
Is it the case for a Nexus One replacement unit that has never been rooted or altered in any way? I got it with FRG83 and installed FRG83D as soon as I received it. I tried SOC method but it was stuck on 'waiting for device' message. Not sure if it is because of an old XP machine or HTC Evo cable I was using.
Upgrade the SuperOneClick and the Nexus One drivers to their latest versions. It DOES work. The least it does is presenting you with a root shell in ADB - which is enough to root manually.
Jack_R1 said:
Upgrade the SuperOneClick and the Nexus One drivers to their latest versions. It DOES work. The least it does is presenting you with a root shell in ADB - which is enough to root manually.
Click to expand...
Click to collapse
I tried both SOC 1.5.1 and 1.5.5 with .net 2.0.5x in the XP machine. I just used the files included in the zip, isn't it that it has latest Nexus One drivers too? Sorry, I am a Mac,Linux guy and not much experience with ADB stuff on Windows.
It might not be the latest drivers, since the latest SOC (I don't remember, I believe it was 1.5.5) finished the rooting procedure correctly on FRG83D, tested several days ago, less than a week. The latest drivers are in the SDK, they need to be installed and the phone has to have "USB Debugging" enabled.
Jack_R1 said:
It might not be the latest drivers, since the latest SOC (I don't remember, I believe it was 1.5.5) finished the rooting procedure correctly on FRG83D, tested several days ago, less than a week. The latest drivers are in the SDK, they need to be installed and the phone has to have "USB Debugging" enabled.
Click to expand...
Click to collapse
Thank you! I guess I have no other option but to install Windows on my Mac. I was feeling lucky and I thought Linux or Mac can use SOC but it is proving difficult and I haven;t come across a single reply who stated success on Linux/Mac!
Uh, why SOC? Use any of the others you just run directly on the phone..
khaytsus said:
Uh, why SOC? Use any of the others you just run directly on the phone..
Click to expand...
Click to collapse
They don't exist for FRG83D just yet and I am not sure if we can downgrade to FRF91 or some other firmware without unlocking bootloader.
You can install Windows in any type of VM, as long as you can forward the USB to it. I can use my Nexus in Linux under VirtualBox, after I forward the USB device to VirtualBox.
Jack_R1 said:
You can install Windows in any type of VM, as long as you can forward the USB to it. I can use my Nexus in Linux under VirtualBox, after I forward the USB device to VirtualBox.
Click to expand...
Click to collapse
Is it true for Mac too? My previous attempts with VMWare and Parallels failed while trying to use USB at low level. I guess it is worth a shot, thank you!
when it hangs at waiting for device, unplug usb and then plug it back in and it should find your device.
dls5375 said:
when it hangs at waiting for device, unplug usb and then plug it back in and it should find your device.
Click to expand...
Click to collapse
Tried that already, no go..
kkiran said:
Tried that already, no go..
Click to expand...
Click to collapse
With all the time wasted searching for other methods, you would have had root on your device already if you just did it manually. It is so simple, takes like 20 mins, and it doesn't require a Windows PC.
I really don't understand why people search for so long for a "1-click" when doing it manually doesn't take that much more effort.
Rooting so is simple with the binaries available:
1) Put rageagainstthecage on your device, change permissions to allow it to run, run it, and presto, it gives you a root shell.
2) Now that you have a root shell, all you have to do is put su in the /system/bin directory, change the permissions so that it can run, and presto, you have root.
And given that rageagainstthecage exploits a vulnerability in the way adb works, this method will work for all devices without a NAND lock.
Rageagainstthecage so easy a caveman can do it.
Sent from my Nexus One

[Q] How to root Build # FRG83G 2.2.2

Hi, Can any kind soul poin tme in the right direction on How to root Build # FRG83G 2.2.2?
Superoneclick does not work and it does not look like anything is out there for superboot on build FRG83G.
I have ditched my Vibrant and returned to my N1. Bought it off of ebay and the boot loader remains intact.
Thanks again.
Larry
If SuperOne click doesn't work - it means you didn't do something right.
Read the Wiki, read the SOC guides, and try again - until you understand what you're doing, and it'll succeed.
Thanks for the reply. Maybe I should have been more clear. Superoneclick is not compatable with the 2.2.2 build.
Maybe I should have been more clear. It IS compatible:
http://forum.xda-developers.com/showpost.php?p=10570981
It was asked not once and not twice, and not even 10 times here. MUCH more. Multiple people rooted 2.2.2 builds with it.
It worked for me.
An error message would really help us help you... Or you could do the manual rage-against-the-cage method.
oklahomatulsa said:
Hi, Can any kind soul poin tme in the right direction on How to root Build # FRG83G 2.2.2?
Superoneclick does not work and it does not look like anything is out there for superboot on build FRG83G.
I have ditched my Vibrant and returned to my N1. Bought it off of ebay and the boot loader remains intact.
Thanks again.
Larry
Click to expand...
Click to collapse
SOC will work but you need to have your device recognised by the PC you are using. Is there a chance that the drivers for your N1 aren't installed properly? This is one reason why SOC rooting can fail.
Providing that you are on Windows, this can be checked by opening 'Device Manager'.
Confused
..Well... I went to a forum last night and saw that superone click ..hell, maybe it was oneclick root was not compatible. Obviously I was wrong. I originally rooted my first N1 the first week of January 2010.
SO I went to the unlockr and followed theor old method. Unforutnately the the "superboot that I attempted to unroot the phone with was for Build FRG83 and not "FRG83G". So the phone shows that the bootloader is unlocked( once it boots up) but according to "root checker and and trackball/powerbutton hold) that is not the case.
Also the superone click shows that it is waiting for my device. I have tried this on Laptop(win7) and desktop (XP)
Thanks
Manual root guide...
http://www.nexusoneforum.net/forum/...mple-sdk-setup-manual-root-guide-windows.html
Sent from my Nexus One using XDA App
oklahomatulsa said:
..Well... I went to a forum last night and saw that superone click ..hell, maybe it was oneclick root was not compatible. Obviously I was wrong. I originally rooted my first N1 the first week of January 2010.
SO I went to the unlockr and followed theor old method. Unforutnately the the "superboot that I attempted to unroot the phone with was for Build FRG83 and not "FRG83G". So the phone shows that the bootloader is unlocked( once it boots up) but according to "root checker and and trackball/powerbutton hold) that is not the case.
Also the superone click shows that it is waiting for my device. I have tried this on Laptop(win7) and desktop (XP)
Thanks
Click to expand...
Click to collapse
I think you are confusing a couple of things.
First of all, if, when you power-up your device, you see the padlock on the splash screen, your bootloader is unlocked. If that is the case, use fastboot to flash a custom recovery (i.e., download the recovery you want to the directory where the fastboot executable is and connect your phone and type fastboot flash recovery insert-name-of-recovery-here.img then you can flash ChainsDD superuser file found here: http://forum.xda-developers.com/showthread.php?t=682828 from recovery.

[Q] [QUESTION] Root Gingerbread 2.3.3

So, I've upgraded my Nexus One with the OTA from Google and I've lost root, is it anyway to root my device again? I want my crack back!! preferably without unlocking the bootloader, something like universal androot, or z4 root (none of them work, at least market versions), thx for your answers
Rikarudo said:
So, I've upgraded my Nexus One with the OTA from Google and I've lost root, is it anyway to root my device again? I want my crack back!! preferably without unlocking the bootloader, something like universal androot, or z4 root (none of them work, at least market versions), thx for your answers
Click to expand...
Click to collapse
I guess the only way is to unlock the bootloader. Why do you want it locked anyways? I guess your warranty is long gone + HTC doesn't check the unlocked bootloader as far as i know.
After unlocking you can install a custom recovery and use su.zip ( its there in the android dev section ) and flash it.
siddharthsai said:
I guess the only way is to unlock the bootloader. Why do you want it locked anyways? I guess your warranty is long gone + HTC doesn't check the unlocked bootloader as far as i know.
After unlocking you can install a custom recovery and use su.zip ( its there in the android dev section ) and flash it.
Click to expand...
Click to collapse
In guess I'll havce to unlock my bootloader then but I havent done it before so im kind of scared, just find it way more complicated doing it that way that whit the mentioned exploits, like universal androot: click root, install room manager, enjoy
You're kidding right? It takes 30 seconds to unlock the bootloader, install a custom recovery, and another minute to install a custom ROM and reboot. I had mine done as soon as I took it out of the shipping box.
YOU DO NOT HAVE TO UNLOCK THE BOOTLOADER. All you have to do is roll back to a build of Froyo. Search for PASSIMG.zip. Apply that through the bootloader. Then you can root using Super One Click or any of the other methods and flash a rooted GB ROM.
Know-Fear said:
You're kidding right? It takes 30 seconds to unlock the bootloader, install a custom recovery, and another minute to install a custom ROM and reboot. I had mine done as soon as I took it out of the shipping box.
Click to expand...
Click to collapse
..But an hour to learn about and set up the SDK first Once done though it makes life sooo much easier and gives you a lot more versatility.
DirkGently1 said:
..But an hour to learn about and set up the SDK first Once done though it makes life sooo much easier and gives you a lot more versatility.
Click to expand...
Click to collapse
That.
An hour might be more or less - depends on a user.
uansari1 said:
YOU DO NOT HAVE TO UNLOCK THE BOOTLOADER. All you have to do is roll back to a build of Froyo. Search for PASSIMG.zip. Apply that through the bootloader. Then you can root using Super One Click or any of the other methods and flash a rooted GB ROM.
Click to expand...
Click to collapse
I have to ask the question, why go to all that bother just to not have a unlocked padlock on the bootscreen when it really makes no difference?
Jack_R1 said:
That.
An hour might be more or less - depends on a user.
Click to expand...
Click to collapse
I think I can make it in less than an hour, lol, anyway, i just wanted to root again because i thought that after OTA the call wonkyness in CM7 got fixed, but it seems is still there, so I'll stay with official GB for a while or untill my abstinence syndrom comes back, and in that case ill try with passimg method just becuase it is a pain in the a55 to setup the SDK (I've done it before, too much data to download and Im currently reliying in thetering to have internet at home).Thnx for your answers.
shuflie said:
I have to ask the question, why go to all that bother just to not have a unlocked padlock on the bootscreen when it really makes no difference?
Click to expand...
Click to collapse
The only benefit is aesthetics, if it really matters to you. I don't much care for the lockscreen, lol. Aside from that, you're right..unlocking the bootloader isn't any worse. It's just personal preference. My point is that you never HAVE to unlock the bootloader.
Unlock Icon
shuflie said:
I have to ask the question, why go to all that bother just to not have a unlocked padlock on the bootscreen when it really makes no difference?
Click to expand...
Click to collapse
To not have a ****ing unlock padlock
Also I don't like thing the easy way. I like "flash_image" instead of "bootloader"'s way of flashing images.
shuflie said:
I have to ask the question, why go to all that bother just to not have a unlocked padlock on the bootscreen when it really makes no difference?
Click to expand...
Click to collapse
OMG!! Don't even mention it!! I can't stand open padlocks!!! they make me feel dirty!! like I have to wash my hands 20 times! LOL.
Seriously, I don't know, I just find it easier with exploits.
Having the bootloader unlocked is the easiest way to do anything.
Sent from my Nexus One using XDA App
Still, for people who just want to root it with a 1-click method, what's the way to do it for 2.3.3?
I used rageagainstthecage for 2.2, then used SuperOneClick for 2.2.1 and 2.2.2 ..... What now with 2.3.3 ?
EDIT: I should mention that most users (like me) want to root their phones without flashing this and that, losing all data/preferences along the way. We just want our phone to be exactly how it is now, down to the last shortcut ...... but rooted!
MitchRapp said:
Still, for people who just want to root it with a 1-click method, what's the way to do it for 2.3.3?
I used rageagainstthecage for 2.2, then used SuperOneClick for 2.2.1 and 2.2.2 ..... What now with 2.3.3 ?
EDIT: I should mention that most users (like me) want to root their phones without flashing this and that, losing all data/preferences along the way. We just want our phone to be exactly how it is now, down to the last shortcut ...... but rooted!
Click to expand...
Click to collapse
Gingerbreak... when it's released.
MitchRapp said:
Still, for people who just want to root it with a 1-click method, what's the way to do it for 2.3.3?
I used rageagainstthecage for 2.2, then used SuperOneClick for 2.2.1 and 2.2.2 ..... What now with 2.3.3 ?
EDIT: I should mention that most users (like me) want to root their phones without flashing this and that, losing all data/preferences along the way. We just want our phone to be exactly how it is now, down to the last shortcut ...... but rooted!
Click to expand...
Click to collapse
It's already been stated, use PASSIMG.zip method to downgrade to 2.2 or whatever you'd like then root. There is currently no way to root a 2.3.3 ROM with any sort of 1 click.
There is, but it's not 1-click - having unlocked bootloader allows you to flash SU and change permissions accordingly.
Those demanding 1-click will have to wait until there is any 1-click solution - and this might take time.
I just tried unlocking my bootloader but it says I'm missing AdbWinApi.dll ... I have it though. I've used the SDK for rooting before without any errors like this. Must be my day...
http://forum.xda-developers.com/showthread.php?t=781386
If you upgraded a rooted device - you can also try the "RErooting guide", in one of the threads where you've asked if it's wiping the whole device. It doesn't. But it might not work without unlocked bootloader - I'm not sure that locked fastboot allows you to boot non-stock, even to memory using "fastboot boot" command. If it does - it's a rooting option completely overlooked until now.

28/3/2012[UPDATED][ROOT]Sensation XL permanent root method - V4 ADDED.

*** unlocking bootloader from HTCDEV site is highly recommended for a permanent root solution***
1. enable usb debugging from settings - applications - development
2. plug phone to pc via usb cable - charge only
3. open extracted zip folder and click runme. thats all. (if experience any daemon hanging problems pls install htc sync and plug in phone so drivers are installed. once done delete htc sync and repeat root procedure)
PC will open a cmd screen with prompts that you need to follow. app does rest
4. After root is complete pls visit market and update SU app. once done root will be fully functional and eliminate any future FCs
5. Also as an extra tip you can install SU UPDATE fixer from market to update your binaries to 3.0
ALL DONE
***************** this isnt my work and i take no credit for it. i tried it and the results were good so i am sharing it. period*****************
****please see anzhi thread for clockwork mod and chinese boot.img and rom needed prior to flashing cappy's rcmix3d rom. files needed are posted by me in his rom thread!****
Update:
Software version 1.24.709.2 doesn't seem to be rootable via this method. Please try flashing another ruu from runnymede rom thread then attempt root again
28/3/2012
Added V4 of the Doomlord Exploit as may be why XL was rooted without bootloader being unlocked.
well i relocked my bootloader and flashed ruu 1.05.404 then I used Doolord V4 to root my phone. This was succesful in permanently rooting my phone without unlocking my bootloader. This was not possible with V2 so if anyone wants to root without unlocking bootloader this is now possible using V4 of the Doomlord Exploit attached below. PLEASE NOTE THAT STILL NEED TO UNLOCK BOOTLOADER TO FLASH CUSTOM ROMS AND RECOVERY
Here is proof. Root explorer superuser permissions in SU app on my phone
Sent from my HTC Nexus One using xda premium
i uploaded pic via xda premium app so not sure why not showing
terminal app wont give full access nor does rom manager. temp root seems to unmount sd card which is remount after reboot but then root access is gone. some apps work perfectly with root permissions and others don't. guess thats why it a temp solution so at least some of our apps that need root acess will work. i am sure someone who is a bit smarter that i am will know how to adapt this to a fully working solution even if temporary
shingers5 said:
http://forum.xda-developers.com/showthread.php?t=1340255
USED THIS METHOD FROM THE EVO 3D FORUM AND IT WORKED.
installed root explorer and granted SU permissions on my sensation xl
IT WORKS
Click to expand...
Click to collapse
Nice
Sent from my Desire HD using xda premium
capychimp said:
Nice
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
hey cappy the sulution seems to offer some level of control but apps like terminal says access denied but via adb access is granted. someone like you must be able to figure out how these evo3d root files can be amended to work fully on XL. i am also trying the sim unlock method on sensation forum but as root is not as deep as need the mmcblk0p6 files are not being accessed. permission denied
ive just unlocked my bootloader with the HTCDEV site it worked wonderfully, now how do i go about custom recovery and permaroot
nintendolinky said:
ive just unlocked my bootloader with the HTCDEV site it worked wonderfully, now how do i go about custom recovery and permaroot
Click to expand...
Click to collapse
how did you do it? apparently the sensation recovery should work with this phone
shingers5 said:
how did you do it? apparently the sensation recovery should work with this phone
Click to expand...
Click to collapse
I just went through the steps and followed each one, they emailed me an unlock_code.bin and i entered fastboot flash unlocktoken Unlock_code.bin and the screen appeared asking if i wanted to unlock the bootloader. Can you point me in the right direction for the recovery please.
yea just did it now i am gonna carry on trying to unlock this phone with the instructions from sensation forum as they should work on this phone. flashing temp root again to get root access and see where it gets me lol
actually i will flash the sensation cwm recovery nd see what happens
tried flashing the sensation recovery and got remote: image update error so not sure whats wrong, i now have a working superuser though by using the zerg exploit here Zerg Exploit v2
nintendolinky said:
tried flashing the sensation recovery and got remote: image update error so not sure whats wrong, i now have a working superuser though by using the zerg exploit here Zerg Exploit v2
Click to expand...
Click to collapse
already done that as my post in android dev forum. same thing. the root isnt a fully working option. try run terminal and type su and you get permission denied. aslo that method unmounts your internal sdcard and other apps like rom manager cant see it. have you tried the alpharev recovery image|? try the evo 3d recovery as the devices are quite similar
mate mine is actually working after a reboot, and root explorer and other root apps are working, the only one that isn't is titaniumbackup, not sure why but im looking into it. Terminal works and so does "adb shell" "su"
nintendolinky said:
mate mine is actually working after a reboot, and root explorer and other root apps are working, the only one that isn't is titaniumbackup, not sure why but im looking into it. Terminal works and so does "adb shell" "su"
Click to expand...
Click to collapse
yeah it is fully working even after reboot. i just done fix_permission from rom manager and working fine. i had to update my super user app via market first. also updated all binaries to 3.0.3 so all current now. you can take over now and start and post your solutions and i will help if i can. only started this to show it can be done. using the evo3dfiles worked a treat. supposed to be temp root but still rooted after reboot for even better. just gonna try sim unlocker then try evo3d clockwork mod and if that fails i will try revolutionary one
See if you can get titaniumbackup working, that's the only app I need or im kinda screwed and will have to go back to the Samsung Galaxy S 2
Here it is backing up all user apps plus ,data
Sent from my HTC Nexus One using xda premium
Was just about to say ive got it working also, right so now we have root we need custom recovery and woop, full on roms. I have also removed all the bloatware "Soundhound" anyone.
nintendolinky said:
Was just about to say ive got it working also, right so now we have root we need custom recovery and woop, full on roms. I have also removed all the bloatware "Soundhound" anyone.
Click to expand...
Click to collapse
still trying to get unlock................... have you tried evo3d recovery? no chefs in here as yet and i guess not many will have the device so might be a while for custom roms. i am happy with a working root solution for now but i am pretty sure evo3d recovery should do the trick
What do you mean by unlock, sim unlock or fastboot unlock, im a bit worried in trying another phones CWM recovery as i dont want to brick or restore my phone to stock,.
nintendolinky said:
What do you mean by unlock, sim unlock or fastboot unlock, im a bit worried in trying another phones CWM recovery as i dont want to brick or restore my phone to stock,.
Click to expand...
Click to collapse
sim unlock i meant. there is an unlock solution in the sensation forum but my device is too new so no code for me. none of the recoveries work as tried them all. phone is not bricked but stock recovery must be in a diff partition on this phone as it has no memory card slot. need like a sansung GS2 recovery as it runs off internal sdcard like this device will have too. may need actual custom kernel with recovery built in
Will this work on the sensation XE?
problems
my phone keeps rebooting into this mode ,i have already removed the battery nothing helps ,can somebody help me ? thx

HTC VIVID Super User Problems....

So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Have you checked with Root Checker Basic to see if you even have Root? If you didn't follow the Super Guide step by step your phone could have relocked after you turned your phone off/on.
If it still fails to update you could try SuperUser Update Fixer.
Yes I have check with root checker.
This may be a dumb question but how do I uninstall Superuser? When I go to the typical application management it does not give me the option. I have done an install again to overwrite the files and nothing changed there.
I followed the instructions step by step (though obviously I messed up somewhere...)
Sent from my HTC PH39100 using XDA App
Kraizk said:
So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Click to expand...
Click to collapse
Interesting... maybe your root didn't stick. We had a little trouble with that before but pirateghost fixed the CWM ROOT zip. You have a working CWM Recovery, correct?
In the superguide, I have a second option for root in case the first doesn't work. In your case, go ahead and try the second option. The one involving the supertool. That should get you perm root. If that doesn't even work, then we might have to put you back to stock and go at it again.
EDIT: BEFORE TRYING THE SUPERTOOL, try flashing the new CWM ROOT VER2 zip from CWM recovery and see if root sticks.
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Kraizk said:
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Click to expand...
Click to collapse
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
*Just a clarification*
You have to unroot your phone to get rid of it Idk why I put uninstall/reinstall earlier...still out there from last night I guess.
slapshot30 said:
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
Click to expand...
Click to collapse
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Kraizk said:
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Click to expand...
Click to collapse
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
slapshot30 said:
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
Click to expand...
Click to collapse
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Kraizk said:
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Click to expand...
Click to collapse
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Kraizk said:
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Click to expand...
Click to collapse
It's no problem, this isn't a dumb question or easy issue by any means. If the method I directed to you doesn't work, let me know. There is another way to do it without all the code.
slapshot30 said:
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Click to expand...
Click to collapse
Worked perfectly. I flashed it back to stock using the thread you linked me to. Then I did the CWM Root method and so far so good. I appreciate all of your help
Nice, I'm glad you were able to get everything working.
Sent from my HTC PH39100 using xda premium

Categories

Resources