• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root LTEVO ROOTING FOR DUMMIES {The Complete Guide}

I'm not sure if it worked....

There's some issue with certain MBP not booting because of some nvidia video issue, so I booted live from my PC. I extraced and ran soju and got to this...

Please wait....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (9/120)
Waiting
Test 2: Booting device
Waiting for ADB (20/120)
must ferment longer...

must sanitize, skunky rum is nasty
hold please..............................................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (9/120)
Waiting for ADB (20/120)
must ferment longer...

chilling..................
smells lovely in here....

bottles are packed, here we go, shhhhhh....

pouring (1)..................
pouring (2)................
pouring (3)...
WTF: What are you doing?

Then when I rebooted to bootloader, it showed S-OFF. How do I verify whether or not I'm really S-OFF? Also, what would be the best stock rom to try to use rumrunner? I was using Super-Jelly from XDA but I don't really know what "stock" means.
 
Congrats and welcome to s-off - your bootloader knows, that's all there is to it. :)

You're free to flash any rom you like, try a few, see what you like.

It won't matter - your s-off is permanent and now your rom and kernel flashing will go easier without the s-on impediment.

Stock simply means that the rom is based on an HTC distribution, usually just root access added.
 
Update, I reflashed this ROM, [XTC][ROM][5.3.13][3.46]Stock w Goodies|Sense 5 parts|Sinister edition - xda-developers, and then was able to get this....

Please wait....
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (5/120)
Waiting
Test 2: Booting device
Waiting for ADB (17/120)
must ferment longer...

must sanitize, skunky rum is nasty
hold please..............................................
[************************************************************]
Rebooting into bootloader (again)
Waiting for fastboot (5/120)
Waiting for ADB (16/120)
must ferment longer...

chilling..................
smells lovely in here....

bottles are packed, here we go, shhhhhh....

pouring (1)........
Waiting for ADB (16/120)
must ferment longer...

what's that in the bottle still? rum foul, sloppy, real sloppy...
wait for it.........
yep, done. Hope you enjoyed the rum!
Don't forget to send us all your money - rumrunnerdevs@gmail.com

!!!

Profit :D

Anyways, thank you very much EarlyMon!

As a suggestion to those that encounter issues with fastboot and Windows 8.1, I highly recommend flashing a Live Linux CD and then booting that to use rumrunner to gain S-OFF. Maybe my experience could help others if they're having the same issue.

Merry Christmas!
 
EarlyMon said:
Congrats and welcome to s-off - your bootloader knows, that's all there is to it. :)

You're free to flash any rom you like, try a few, see what you like.

It won't matter - your s-off is permanent and now your rom and kernel flashing will go easier without the s-on impediment.

Stock simply means that the rom is based on an HTC distribution, usually just root access added.
Click to expand...

I replied just as you did :) I'm trying to find a stable 4.4 rom. Do you recommend any?
 
I can't seem to root my phone...I keep getting the error in the command prompt:

"target reported max download size of 1526722560 bytes
error: cannot load 'C:\Users\ever8glades\Desktop\Unlock_code': No error"
 
Sorry for the delay. Yes, USB 2 and yes, I believe I was using the mini SDK from here. I'll have to double check.
 
i've noticed that the htc dev site sometimes can be buggy.....might be the amount of peeps using it at one time......have you tried and start over to get the unlock code?
 
Okay so I have software 3.17.651.4, hboot 2.09.00, radio 1.13.11.0830.
I sucessfully unlocked via htcdev.com.
I didn't know that would act like a factory wipe but it did.
So I proceeded to Rum Runner.
Disabled AV.
Downloaded the files 0.5.0 version.
It gives this the first time:
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (38/120)
must ferment longer...

must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at www.rumrunner.us
Click to expand...

So I put the mini-sdk file in the same directory and try again.
Then I get a little further but still FATAL:
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (39/120)
must ferment longer...

must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (39/120)
must ferment longer...

ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
!
Press ENTER to exit
Click to expand...

Is there some step I'm missing?
 
So I installed TWRP recovery, the one for the kitkat 2.6.3.0.
And SuperSu (CWM-SuperSU-v.94.zip)
This last one didn't take well at first and then wouldn't update from google play for some reason. Eventually I got it to update. Then booted into TWRP to get the binary installed.
Then I tried rum runner again but it failed. This time with just TTTT***********.
I checked the phone and supersu was apparently prompting me for the adb shell. So I changed the default to grant.
Then I rebooted and ran it again. Success. SOFF.

Thanks for your guides!

!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (39/120)
must ferment longer...

must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (39/120)
must ferment longer...

chilling..................
it's a little stinky here, hmm....

bottles are packed, here we go, shhhhhh....

hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
pouring (1)......................................
pouring (2).....................................
pouring (3).......
Waiting for ADB (38/120)
must ferment longer...

what's that in the bottle still? rum foul, sloppy, real sloppy...
wait for it.........
yep, done. Hope you enjoyed the rum!
Don't forget to send us all your money - rumrunnerdevs@gmail.com
Press ENTER to exit
Click to expand...
 
Trying to get started rooting a 3.17 device I just acquired and forgot how much a pain it is when the developers have started closing the loopholes. I have very little programming experience and can't seem to get ADB up and running on my Windows 7 machine. Any tips?
 
scottborasjr said:
Trying to get started rooting a 3.17 device I just acquired and forgot how much a pain it is when the developers have started closing the loopholes. I have very little programming experience and can't seem to get ADB up and running on my Windows 7 machine. Any tips?
Click to expand...

what is exactly wrong? is your device unlocked? if it is unlocked then you can use the same android folder. have you tried rumrunner?
 
Finally got the bootloader unlocked going to give rumrunner a go. Thanks for the reply
Think I was just distracted trying to do this and keep a eye on the kids.
 
Ok, I get to the same point that Will did above where it goes to about 45/120 adb and then says that it hasn't rooted the phone and the kernal is still secure. I went to try and install TWRP and both by using goo manager and loading using the PCIMG method in bootloader failed. I'm not having a great day.
 
On the phone or on the computer? I have access to adb when I'm in the folder that it is kept, but when I'm just on my standard cmd command prompt won't let me get to it.

I successfully unlocked using HTCDev last night, and I could be just getting frustrated again. Still don't have actual root access and still looking to S-Off
 
When you run adb commands you have to be in the adb folder not just on the command window.....so yes on the pc where you have adb setup from unlocking the bootloader before.
 
Ok, I get something about Daemon and I see the $ but I can't delete it to add the #. I can add the # but not delete. I'm sorry, I have only used one click root methods before, this is my first time having to actually mess with code myself.
 
scottborasjr said:
Ok, I get something about Daemon and I see the $ but I can't delete it to add the #. I can add the # but not delete. I'm sorry, I have only used one click root methods before, this is my first time having to actually mess with code myself.
Click to expand...
dont be sorry....after "adb shell" type "su" and it should change from $ to #

if that happens then try rumrunner again.
 
device not found after typing su
I put super su on the phone but still doesn't find the device.
rebooted phone and tried again and didn't work.

I know I'm missing something stupid but I've been reading for almost all of my free time for the last 36 hours and can't figure it out.
 
You must log in or register to reply here.
Back
Top Bottom