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

Root [RECOVERY] TWRP 2.8.5.0 (Lollipop)

whoshotjr2006

whoshotjr2006

Android Enthusiast
Bad_MOFO_33 made a lot newer updated Lollipop TWRP, with version number 2.8.6.0. He fixed wiping speed and also MTP and ADB. Go to his thread: http://androidforums.com/threads/cm12-1-unofficial-beta.905257/ and throw some thanks on his first post if you have not already and definitely check out CM12.1 since he did a hell of a job on it.

Note: This thread may be transferred from me to him so it could be a lot more up to date than I keep it, it just depends on if he wants it. Im just going to use this post to point to his download for now.

Download it here: https://www.androidfilehost.com/?fid=24052804347759569
 
Last edited:
Have you tried whipping up a copy of philz? I hear it has better compatibility with lollipop.

Edit: woah! Just noticed I got a shiny new badge! But I'm no developer, I'm more on the script kiddy level. How about we bring it down to contributor?
 
xry75 said:
Are the older backups OK to use with this? Or do we need to do fresh backups?
Click to expand...
older backups are ok to use. But you should make fresh backups every once in a while.

@whoshotjr2006 seems a little more responsive, just missing key lights(no biggie) Good work and no problems here flashing cm12 and restoring.
 
Couple screenies
 

Attachments

  • 1423926666403.jpg
    1423926666403.jpg
    38.3 KB · Views: 501
  • 1423926680312.jpg
    1423926680312.jpg
    50.2 KB · Views: 463
jothe 1 said:
Can someone explain what's the device zip and vendor for thank you
Click to expand...

Unless your building from source, don't worry about them. Those are just for devs to get stuff working.

Also halrulz yes it will work with KitKat no problem, I'm on the stock ROM and flashing, backup and recovery work just fine.
 
whoshotjr2006 said:
Unless your building from source, don't worry about them. Those are just for devs to get stuff working.

Also halrulz yes it will work with KitKat no problem, I'm on the stock ROM and flashing, backup and recovery work just fine.
Click to expand...
Whoops good thing I didn't try to flash it or something lol thanks
 
Would not let me restore from sdcard or mount it, i have a SanDisk 16gig, i also couldnt mount through usb used every usb cord even a new to see if that was a problem bht it wasn't.
 
bakerd62 said:
Would not let me restore from sdcard or mount it, i have a SanDisk 16gig, i also couldnt mount through usb used every usb cord even a new to see if that was a problem bht it wasn't.
Click to expand...

I haven't had that problem here. Can you pull some logs from twrp, and see if you can get a dmesg and adb logcat from twrp also? That should hopefully tell me what's going on.
 
bakerd62 said:
I dont have a pc at the moment. But tell me how to pull the logs of twrp and ill post them
Click to expand...

Probably not what you want to hear or do, but you should think about backing up everything off your sdcard and formatting it. On past phones, I have had the same problem and a backup and format worked wonders. That at least would rule out one possibility, and its not a bad idea to back everything up anyway and format once in a while.

I believe under one of the buttons in twrp there's a log function, can't remember which one possibly the advanced button. Never really had to use it to be honest since most devices I had before the volt were officially maintained by omni and had all the kinks worked out long before I flashed it.
 
If I wanted to SAFELY induce a soft brick that can be fixed with a nandroid restore to showcase the power of a custom recovery on Android to a friend, what file should I delete or modify.

(he wants to root his phone but is afraid of F-ing it up if he does and is unsure of the reliability of a custom recovery like TWRP)

I plan to show him how easy it is to make a nandroid backup, soft brick my phone, then restore the backup made at the beginning of the demonstration.

On a slightly different note, can TWRP restore a partition that was deleted, or does the partition have to be existent to be restored? I copied /system to my sd card so I could look around without F-ing anything upon accident, but I almost hit delete instead of copy. Just curious so I know to be much more careful next time or if I should be "safe" because I can restore a backup.
 
If you actually manage to hose your partition table, TWRP can't save you.

Deleting /system doesn't delete a partition, just its contents. A nandroid can restore that.

I'm tempted to answer your question but seeing as how I spend most of my time here helping people who have broken their phones, I think I'd rather not have my name on "how to brick" instructions. I'm sure you can dig it.

And fwiw - if it can be restored, it's not a brick. It's just temporarily broken.

If your friend doesn't understand the value of an image backup and restore, and doesn't trust TWRP, then frankly they have no business being near root.

Root is not for everyone.

If their instincts are telling them that not even TWRP can save them, then that's probably to be trusted.
 
whoshotjr2006 said:
I told you guys I would do it when the time was right, so here it is.

disclaimer: what you do with what I provide is your responsibility. if what I made messes up your phone, its on you not on me. So with that said, I will do what I can to help you recover, but its ultimately your fault if something breaks.

Flash this just like you flash clockworkmod recovery.

fastboot flash recovery twrpvolt_lollipop.img

Or use flashify, that should work too.

After first boot, just use an app inside android to reboot to recovery, I personally use APM+ and xposed: http://forum.xda-developers.com/xposed/modules/advanced-power-menu-apm-t2842792

What works:
everything that worked in kitkat twrp afaik, I tested a zv5 rom install, a backup and a restore and they all worked just fine. Read the below "what is currently wonky"

What is currently wonky:
factory reset took a few extra moments to complete, but worked fine
Flashing roms, backing up roms, and restoring roms took a little extra too, but worked just fine

I think the above wonkyness is a result of omnirom still working on their sources for twrp lollipop. I have not found any concrete evidence of that, but im going to keep checking into it.

Sources:
Kernel:
https://github.com/arj1231 (bad_mofo_33 cm11 kernel updated with quarx's commits for cm12, gonna switch to bad_mofo_33's lollipop kernel in the future when I have time.)

Device and vendor came from Quarx2k, but I modified quite a bit trying to get cm12 booting. Since bad_mofo is awesome and got us up and running with cm12, I'm going to switch to bad_mofo_33's trees in the future when I have time.
https://github.com/Quarx2k

Use these for now:
Device:
https://www.androidfilehost.com/?fid=95916177934528163
Vendor:
https://www.androidfilehost.com/?fid=95916177934528164

And finally, the TWRP Volt Lollipop download here:
https://www.androidfilehost.com/?fid=95916177934528139
Click to expand...
Hey I have a lg volt and I flashed the lollipop twrp above and the only problem is that when you eneter the recovery through the button combo it opens something called a openrecovery script and factory resets the phone.
 
You must log in or register to reply here.
Back
Top Bottom