• 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}

Thanks. Now to restore all the settings that were lost during the unlocking and NOT covered by Helium Backup (all my sounds, wallpaper, alarms, etc...), then look into making a nandroid backup.
 
Thanks. Now to restore all the settings that were lost during the unlocking and NOT covered by Helium Backup (all my sounds, wallpaper, alarms, etc...), then look into making a nandroid backup.

So, what new phone are you getting?

And btw, a nandroid is only good for the exact same model - so you'll want to do that plus increase your normal backup.

I think most people use Titanium Backup, I like MyBackup Root.
 
So, what new phone are you getting?

I think most people use Titanium Backup, I like MyBackup Root.

I'm still torn between the HTC One M8, or a Galaxy S5. For the most part, I like the specs on the M8 better, but I don't like the extra size created by the dual front speakers, and I don't like HTC's stance about the camera. My pictures are NOT intended for social media, so I want the high pixel capacity. Plus side-by-side comparisons on the image quality place Samsung as the winner.

On the other hand - I have a 3-year-old, so the water resistance of the Galaxy S5 is very appealing. Combined with the aforementioned higher pixel camera, and the fingerprint scanner to lock my son out from making unauthorized purchases, and I'm currently leaning towards the Galaxy S5.

My research shows they're both rootable already.

As for backup, I was thinking Titanium, but will now compare it with MyBackup Root.
 
I'm privy to Viper roms myself, but there are a few good AOSP roms like Beanstalk.

If you update your phone to 4.3 using the method Cap'n Throwback provides here: http://androidforums.com/evo-4g-lte...-sense-5-android-4-3-update-4-13-651-1-a.html you can run the latest Viper 4.0 or the newer KitKat AOSP roms. :)


so ive been using beanstalk since ive been rooted, i like but i think i need to update to the latest version. im just not sure how this is done.
im running beanstalk version version 4.3.05.
 
so ive been using beanstalk since ive been rooted, i like but i think i need to update to the latest version. im just not sure how this is done.
im running beanstalk version version 4.3.05.

To use either the new Viper4G or Beanstalk using the new partition layout, you must follow Cap'n Throwback's instructions (linked at both roms, so it's true) -

http://forum.xda-developers.com/showthread.php?t=2639180

Note he says going with the RUU for this is best.

The Beanstalk thread lets you get to 4.4.249 using the old partition format you have now, or up to 4.4.285 with the new -

http://forum.xda-developers.com/showthread.php?t=2637130

Both are 4.4.2, so you can try the slightly older one hassle free if you prefer.

Does this help?
 
To use either the new Viper4G or Beanstalk using the new partition layout, you must follow Cap'n Throwback's instructions (linked at both roms, so it's true) -

[ROM][FIRMWARE][RECOVERY][STOCK] Sense 5, Android 4.3 Final Update - 4.13.651.4 - xda-developers

Note he says going with the RUU for this is best.

The Beanstalk thread lets you get to 4.4.249 using the old partition format you have now, or up to 4.4.285 with the new -

[ROM][KitKat][4.4.2][Unofficial]BeanStalk Build 4.4.285 NEW_FORMAT- 4.4.2 [Jewel] - xda-developers

Both are 4.4.2, so you can try the slightly older one hassle free if you prefer.

Does this help?

i took the hassle free route, but i was hoping the update would fix my bluetooth not working. and no luck
 
So dumb question...
So I tried to move my MicroSD card from my Evo 4G LTE to my M8. I was stupid for not making a copy of it beforehand but my Hard Drive has been low on space for a while, so my complete backup method was not really feasible.
Something got boogered up and the card crashed - the M8 boots up but then during normal loading process hangs and says "unfortunately com.process.android.gapps has stopped". A failure of some sort because of the broken card?
The filesystem is FUBAR. The card only shows 30.6MB plus is stuck as RAW and cannot be formatted. Partition cannot be accessed. I've tried everything 8 times and 8 ways. I have about 95% of the cards data 'full copy' backed up in the past, but it had been a while. And as always that 5% of data was the newest and now most desired data, probably because I can't recall exactly what all was there. :(

I had success recovering some files (or fragments) from my PC using TestDisk. I had dropped the MicroSD contents to the PC before cutting and pasting them to a new card. Great little program. I wondered if there is a way I can get the Evo 4G LTE internal storage to mount as a drive so that I can use TestDisk (or one of the other 12 programs I've tried) to search for any breadcrumbs on it?
The Android change, to MTP only, kind of sucks and is inhibiting things. When I select mount as Disk Drive on the phone(with no MicroSD installed), with USB Debugging enabled, my PC shows a greyed out 'hidden' USB drive, but nothing can be done with it?

I did a TWRP backup not that long ago. I don't know much about TWRP backups or their files besides the fact that they are infinitely helpful and good to create before flashing a new ROM. I think I recovered my last TWRP backup via TestDisk. Hopefully they aren't corrupted. Is there a way to use my TWRP backup files to recover some data? Some of my data would have been on the internal storage and then moved to the MicroSD at a later date.

Got an RMA open with SanDisk to replace the card, and I've come to terms with the total loss feeling regarding the data. Just wondering if there is any last ditch ideas I could try...?


Working on getting a bigger hard drive, before the one I have fails :D
 
I can't reboot right now but basically -

Go to TWRP, Advanced (I believe) and look through the options - you'll find one to mount internal storage for usb access.
I don't know what effect running the test program will have but it's worth a shot.

Remember to unmount (eject) on the pc side and stop the usb access in TWRP when done before removing cable or rebooting.

Gapps - Google apps - Gmail, Talk, etc etc.

In main settings, Apps, All, find Google Play Services and Google Services Framework, clear any data and cache you find there. Back to TWRP, Advanced, and Fix Permissions.

That often helps but it's not 100%. If it's something on storage you'll have to fix it as well.

I've forgotten but my gapps started force closing on boot, I had to disable Talk to stop it. Got busy and didn't get back to sorting that one out. :p

Sorry for the frustration. Let me know if the instructions make sense or if I missed anything.
 
Sorry. :(

Is it Beanstalk or hardware?

If you have an earlier Sense nandroid from before you started Beanstalk, that would say for sure.

I think, I do have it. What do I do flash it using twrp to return my phone back how it was and Test Bluetooth conectabilty.
Another issue I'm having. Is I'm having randomly losing my network connection. I can get it to reconnect if I reboot.
My phone says its in " digital romiming " I don't know that means
 
I think, I do have it. What do I do flash it using twrp to return my phone back how it was and Test Bluetooth conectabilty.
Another issue I'm having. Is I'm having randomly losing my network connection. I can get it to reconnect if I reboot.
My phone says its in " digital romiming " I don't know that means

It might all be related, so let's check both your current software and settings first.

Very important question - do you have s-off?

If not, begin by getting a copy of your nandroid that you want to restore over to your PC. You'll need to extract the boot.img file - and I need to know if you're on Windows, Mac or Linux to advise on that.

TWRP, Backup, make a nandroid of what you have, use the default settings for boot, system and data.

Back to main TWRP screen, Restore, choose the old Sense nandroid. If s-on, don't bother with boot, otherwise, restore boot, system and data.

Back to main screen, Wipe. Choose to wipe cache and Dalvik and nothing else.

Back to main screen, Reboot. If you're s-off, just reboot system.

If s-on, choose to reboot to bootloader. From there get to FASTBOOT mode. Either your phone will go there and you'll see it listed at the top, or it be in the menu list and you have to go there.

Connect to usb if not already.

Move or copy the boot.img file to where your fastboot is. If you used our Mini SDK and followed our instructions when you first rooted, that will be under the sdk-tools folder.

Open command window in that folder. Then enter in command window -

fastboot flash boot boot.img

When done with success, enter -

fastboot reboot

And test out your phone.
 
I can't reboot right now but basically -

Go to TWRP, Advanced (I believe) and look through the options - you'll find one to mount internal storage for usb access.
I don't know what effect running the test program will have but it's worth a shot.

Remember to unmount (eject) on the pc side and stop the usb access in TWRP when done before removing cable or rebooting.

Thanks as always Early
When I try to mount, it is not popping up on the PC side (Windows 7). TWRP 2.6.3
(Updated to Android 4.3 in Feb.)
 
It might all be related, so let's check both your current software and settings first.

Very important question - do you have s-off?

If not, begin by getting a copy of your nandroid that you want to restore over to your PC. You'll need to extract the boot.img file - and I need to know if you're on Windows, Mac or Linux to advise on that.

TWRP, Backup, make a nandroid of what you have, use the default settings for boot, system and data.

Back to main TWRP screen, Restore, choose the old Sense nandroid. If s-on, don't bother with boot, otherwise, restore boot, system and data.

Back to main screen, Wipe. Choose to wipe cache and Dalvik and nothing else.

Back to main screen, Reboot. If you're s-off, just reboot system.

If s-on, choose to reboot to bootloader. From there get to FASTBOOT mode. Either your phone will go there and you'll see it listed at the top, or it be in the menu list and you have to go there.

Connect to usb if not already.

Move or copy the boot.img file to where your fastboot is. If you used our Mini SDK and followed our instructions when you first rooted, that will be under the sdk-tools folder.

Open command window in that folder. Then enter in command window -

fastboot flash boot boot.img

When done with success, enter -

fastboot reboot

And test out your phone.

i am S-OFF. turns out i dont have a nandroid before beanstalk (or i just cant find it :confused:)
 
i am S-OFF. turns out i dont have a nandroid before beanstalk (or i just cant find it :confused: )

Boy, I know that story.

Ok, all is not lost.

Check our sticky thread, I bet we still have the link for the earlier (non-4.3) stock Jellybean rom.

See if you can still download it.

I bet you can.

Make a nandroid backup, grab that and install it.

Doesn't matter about all your apps etc etc etc like a nandroid restore - we don't care about that right now, just testing your hardware with stock HTC software.
 
Boy, I know that story.

Ok, all is not lost.

Check our sticky thread, I bet we still have the link for the earlier (non-4.3) stock Jellybean rom.

See if you can still download it.

I bet you can.

Make a nandroid backup, grab that and install it.

Doesn't matter about all your apps etc etc etc like a nandroid restore - we don't care about that right now, just testing your hardware with stock HTC software.
I tried to run this one but i got as far a the HTC screen i waited about 10 minutes and it didnt bootup.i went back to recovery and restored back to where was.
 
I tried to run this one but i got as far a the HTC screen i waited about 10 minutes and it didnt bootup.i went back to recovery and restored back to where was.

Dang, it's always something.

Let me think...

Ok - no Aroma installer? It just went right to installing? In such a case -

TWRP, Wipe - boot, system, data, cache, Dalvik - install old Sense rom.
 
Thanks as always Early
When I try to mount, it is not popping up on the PC side (Windows 7). TWRP 2.6.3
(Updated to Android 4.3 in Feb.)

Yeah, I forgot about that - mine worked pre-4.3 when /sdcard really was it's own filesystem, not shared with /data. :(

Sorry to bug again.
So referring back to my prior post. You think there is anything that can be gleaned with the potential TWRP back up files (nandroid)? I'm not sure about where to start on restoring from them, converting them, or searching/extracting files from their image.
 
Sorry to bug again.
So referring back to my prior post. You think there is anything that can be gleaned with the potential TWRP back up files (nandroid)? I'm not sure about where to start on restoring from them, converting them, or searching/extracting files from their image.

Your nandroids prior to the 4.3 partition changes aren't going to be helpful for use as nandroids.

If your nandroids included the files you want from your internal storage, yes, you can get to the files inside.

Did you recover those nandroids from your external SD?

Btw, you caught me on the way out the door, let me know any details and I should be back in about an hour and a half.

And - you are never bugging. :)
 
Back
Top Bottom