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

Root [Verizon] Problems installing TWRP

B

breadnatty08

pain rustique
Alright, I think since the OG days, the G2 is the one giving me the biggest pain. I did get it rooted yesterday, but installing TWRP is making me: :banghead:
Trying to find the source of the problem but everytime I go to ADB Devices, says "Device offline". Found what could have helped and updated my SDK to R20, but it still isn't helping. Something with the drivers I imagine....
 
Make a live Ubuntu CD, boot it, grab your TWRP and our Mini-SDK, and you're done.

Instructions for most of what you need to do in the HTC Evo 4G LTE main rooting thread.

After you're impressed, instead of trying to make Windows work because it "should be able to," install VirtualBox, install Linux inside that, use it every time you want fastboot or adb, and eventually ask yourself why Windows is the only major operating system requiring usb device drivers in the first place.

Eventually you'll simply use Linux for everything, ditch Windows, and ask yourself why you didn't do it sooner.

Your G2 may be doing you a favor. :)

Either that or best luck finding the right drivers.
 
Thanks, I'll give it a shot.
I feel like it has something to do with the RSA Fingerprint that 4.2+ devices use to connect to "trusted" PCs. I know I hit to let it allow, but not sure why it's not working now.

Edit: Looks like it connects, but still saying offline. :(
 
If that doesn't work, others in the thread (from this last week) are reporting that Flashify (for root users) does.

Very interesting app btw.
 
Reading through the 30 pages of that thread I saw so much conflicting results. Maybe I'll give it a shot.
And I did. Doing a backup now, crossing fingers for no bootloops. :o
 
breadnatty08 said:
Reading through the 30 pages of that thread I saw so much conflicting results. Maybe I'll give it a shot.
Click to expand...

If you set your view to 50, it's only 10 pages and that's a lot easier than 30 pages.

:rofl:

Seriously though - wireless adb did NOT work?

I've never had a problem with it fwiw.

(edit - ninja'd by your edit)

Had I known you were already rooted, I'd have recommended it first.

I was also going to suggest downloading directly to your phone, managing the file actions with EStrongs File Explorer and then instead of adb shell, just do those commands in Terminal Emulator.

I didn't because I gathered that you don't have any button press on that phone to boot you into recovery, so eventually you'll need adb working anyway.

Not sure about the button press, really, just what I gathered skimming along.

PS - you have usb debugging turned on, yes?
 
You can button press to get into recovery, but it's reported causing big boot loop issues.
Either way, just finished a backup and rebooted. So far so good. :)
 
Yeahhhhh...I think I'm going to wait to root the G2? Unless, are you doing all this to add a ROM? I personally like the phone as is. At this moment the only reason I want to root is for tether. I would like to get rid of some this bloat too.
 
Didn't do anything, just transferred the recovery image to the phone and used Flashify.
Only issue I noticed was the text in TWRP is barely legible. Some DPI issue I imagine.
Halon, rooting wasn't too bad (shh, don't tell Stigy). It's just an issue of getting the right drivers which is the same with any device.
 
breadnatty08 said:
So much Windows hate. :p
Click to expand...

I don't hate Windows, I use it when I absolutely must.

I hate having my time wasted and that's what Windows does best.

If you avoid Windows, you avoid wasting time fixing the two dumbest things in the history of computing -

The registry.

USB device drivers.

How much of your life have you lost to those two things?

I've kept track.

Since the introduction of Windows 3.1, it's been 4 days and 2 hours.

The 4 days I got paid for.

So that's 2 hours of my time.
 
You must log in or register to reply here.
Back
Top Bottom