Introducing XDA:DevCon – A Conference For Developers By Developers
XDA Developers Android and Mobile Development Forum
Forgot your password?
 
Post Reply+
Tip us?
 
LKMR.PREZ
Old
#1  
Member - OP
Thanks Meter 1
Posts: 63
Join Date: Jan 2011
Default Quick question

Quick noob question everyone, if I have an unlocked bootloader and custom recovery, am I rooted? Because busybox and superuser still aren't giving me command prompts. I'm on stock ics
Sent from my HTC PH39100 using XDA
 
jigajay
Old
#2  
jigajay's Avatar
Senior Member
Thanks Meter 21
Posts: 339
Join Date: Feb 2011
Location: Brooklyn N.Y
Long story short no your not rooted but you did the hard part already just follow this guide you'll be rooted in under 2 minutes http://forum.xda-developers.com/show....php?t=1498003
I'm A Lean Mean Flashing Machine
 
LKMR.PREZ
Old
#3  
Member - OP
Thanks Meter 1
Posts: 63
Join Date: Jan 2011
THANKS!

Sent from my HTC PH39100 using XDA
 
MMVXIII
Old
#4  
Junior Member
Thanks Meter 0
Posts: 2
Join Date: May 2012
I have the same issue as the OP. Vivid with stock ICS 4.0.3. I've unlocked the bootloader via HTCDev. Flashed WCXs CWM (GB/ICS) recovery.

I've tried patiently to Perm Root with Vivid All-In-One Kit. No success. Device just reboots into recovery. I followed WildChild's instructions to boot into recovery and install superuser & su. Still nothing. TiBa and BusyBox still say Root Privileges are needed.

I've been up and down the Android and Vivid forums on different websites, but can't find the answer.

I'm not interested in flashing a kernel/ROM unless it's necessary. I just want root privileges to eliminate AT&T's junk.

Am I missing a step somewhere? I can't post to AIO forum because my post count isn't high enough. So at this point....any help is very much appreciated.

FYI...Vivid is set to USB debug. This is the return I get from Vivid AIO Perm Root:

C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server

C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .

C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
adb server is out of date. killing...
* daemon started successfully *
error: device not found

C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
error: device not found

C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
error: device not found

C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
error: device not found

C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
error: device not found

C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
 
kozmikkick
Old
#5  
Senior Member
Thanks Meter 1164
Posts: 1,203
Join Date: Nov 2010
Location: Seattle, WA
Quote:
Originally Posted by MMVXIII View Post
I have the same issue as the OP. Vivid with stock ICS 4.0.3. I've unlocked the bootloader via HTCDev. Flashed WCXs CWM (GB/ICS) recovery.

I've tried patiently to Perm Root with Vivid All-In-One Kit. No success. Device just reboots into recovery. I followed WildChild's instructions to boot into recovery and install superuser & su. Still nothing. TiBa and BusyBox still say Root Privileges are needed.

I've been up and down the Android and Vivid forums on different websites, but can't find the answer.

I'm not interested in flashing a kernel/ROM unless it's necessary. I just want root privileges to eliminate AT&T's junk.

Am I missing a step somewhere? I can't post to AIO forum because my post count isn't high enough. So at this point....any help is very much appreciated.

FYI...Vivid is set to USB debug. This is the return I get from Vivid AIO Perm Root:

C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server

C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .

C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
adb server is out of date. killing...
* daemon started successfully *
error: device not found

C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
error: device not found

C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
error: device not found

C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
error: device not found

C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
error: device not found

C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
Adb isn't set up properly or may need to ne run as administrator

Sent from my HTC PH39100 using xda premium
 
jigajay
Old
#6  
jigajay's Avatar
Senior Member
Thanks Meter 21
Posts: 339
Join Date: Feb 2011
Location: Brooklyn N.Y
Quote:
Originally Posted by MMVXIII View Post
I have the same issue as the OP. Vivid with stock ICS 4.0.3. I've unlocked the bootloader via HTCDev. Flashed WCXs CWM (GB/ICS) recovery.

I've tried patiently to Perm Root with Vivid All-In-One Kit. No success. Device just reboots into recovery. I followed WildChild's instructions to boot into recovery and install superuser & su. Still nothing. TiBa and BusyBox still say Root Privileges are needed.

I've been up and down the Android and Vivid forums on different websites, but can't find the answer.

I'm not interested in flashing a kernel/ROM unless it's necessary. I just want root privileges to eliminate AT&T's junk.

Am I missing a step somewhere? I can't post to AIO forum because my post count isn't high enough. So at this point....any help is very much appreciated.

FYI...Vivid is set to USB debug. This is the return I get from Vivid AIO Perm Root:

C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server

C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *

C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .

C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system
adb server is out of date. killing...
* daemon started successfully *
error: device not found

C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
error: device not found

C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su
error: device not found

C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su
error: device not found

C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
error: device not found

C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .
When using the all in one tool did you boot into bootloader when trying to perm root if it didn't automatically do it for you.
I'm A Lean Mean Flashing Machine
The Following User Says Thank You to jigajay For This Useful Post: [ Click to Expand ]
 
GlowingStar
Old
#7  
Member
Thanks Meter 0
Posts: 65
Join Date: May 2012
If you could get back to stick gb, Google zergrush root. Its a tempt root for users who still have their boot loader locked. But in your case, it should be locked.

Sent from my HTC PH39100 using XDA
 
MMVXIII
Old
#8  
Junior Member
Thanks Meter 0
Posts: 2
Join Date: May 2012
Quote:
Originally Posted by jigajay View Post
When using the all in one tool did you boot into bootloader when trying to perm root if it didn't automatically do it for you.
All In One automatically reboots into recovery, runs the batch then responds with "device not found" after each command.

I did try what you said. I booted into bootloader, then ran the perm root from AIO, but got the same "device not found" result.

---------- Post added at 05:46 PM ---------- Previous post was at 05:10 PM ----------

After much reading, booting and rebooting, I managed to get this response from All In One:

C:\Vivid_All-In-One_Kit_v2.0\data>adb kill-server
* server not running *

C:\Vivid_All-In-One_Kit_v2.0\data>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found

C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .

C:\Vivid_All-In-One_Kit_v2.0\data>adb shell mount /system

C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/su /system/xbin/su
349 KB/s (22364 bytes in 0.062s)

C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chown 0.0 /system/xbin/su

C:\Vivid_All-In-One_Kit_v2.0\data>adb shell chmod 06755 /system/xbin/su

C:\Vivid_All-In-One_Kit_v2.0\data>adb push SU/Superuser.apk /system/app
4800 KB/s (843503 bytes in 0.171s)

C:\Vivid_All-In-One_Kit_v2.0\data>pause
Press any key to continue . . .

However, no still no root. I've kept up to date with the AIO forum. Read the "under construction SuperGuide cover to cover. I have done exactly what many others have, except no joy for me. It appears I may have the only AT&T Vivid in the world that will not root.
 
GlowingStar
Old
#9  
Member
Thanks Meter 0
Posts: 65
Join Date: May 2012
http://forum.xda-developers.com/show....php?t=1529669

Flash that in boot loader. If it says update presses yes then you're back to gingerbread.

Sent from my HTC PH39100 using XDA
 
GlowingStar
Old
#10  
Member
Thanks Meter 0
Posts: 65
Join Date: May 2012
http://forum.xda-developers.com/show....php?t=1341162
Use that to root your phone. Follow instructions carefully.

Sent from my HTC PH39100 using XDA

 
Post Reply+
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Go to top of page...

XDA PORTAL POSTS

Job Interview Prep: Phone Screen Part 1 – XDA Developer TV

XDA Developer TV Producer Jayce has been very busy creating videos to help … more

Auto Test Your Android Apps with Robotium

You’ve just finished coding your very first app, but before you release it to the wild, you … more

Open Source CPU Info App for Windows

So you’re playing with your shiny new Windows 8 tablet PC, when one of your like-minded geeky … more

Guide to Using Adobe Air on Android

When writing an app with performance in mind, you most likely want to write it native code using the … more