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

Root Twrp Recovery 3.0.0

About to flash and test the OTG, will edit this for the result
RESULTS: OTG is a SUCCESS! Mounted fine and read fine. I'm also loving the new theme :D
 

Attachments

  • Screenshot_2016-03-29-17-02-47.png
    Screenshot_2016-03-29-17-02-47.png
    33.1 KB · Views: 326
  • Screenshot_2016-03-29-17-02-39.png
    Screenshot_2016-03-29-17-02-39.png
    30 KB · Views: 342
Last edited:
so what i gather otg is like playing a ds emulator and being able to use a controller is that otg?? if so no wonder it never connected...lol
 
This is great! I'm glad my OTG patch is sparking some more development for the LG Volt. I still cannot believe it was such a dead simple fix, I wonder why LG left in all the code required for OTG but then deliberately turned it off in the DTS (Device Tree Source) file. During all my research into this usually the device has hardware support but lacks most of the code to turn on OTG, requiring a lot of code changes and add ins to enable.

EDIT: v3.0.0 with OTG appears to work great here.
 
Last edited:
Bad_MOFO_33 said:
I decided to jump back into this device. Updated Twrp to version 3.0.0. Also added @ShapeShifter499 OTG commit(not sure if it works or not, I dont have OTG device)
Hopefully everything works... Let me know

Link fixed https://www.androidfilehost.com/?fid=24459283995308541
Click to expand...
Thanx Bad_MOFO_33 your awesome work continues! Hey just wanted to tl ya a quick tidbit of info I haven't paid for my service since August of 2015! Ever since I flashed Lollipop ROMs! Believe me I'm not complaining, just baffled how my # hasn't been flagged as not active after 2 or 3 months of not re upping my monthly payments? So yah I et unlimited everything although 4G hasn't worked since October but oh well! Anyway I just wanted to thank you for the new recovery!
 
Is it possible to flash twrp through twrp itself? The system UI is crashing at startup because of some setting I had changed in the blisspop display options and for some reason my current twrp is failing at backing up /data and gives me an E:createTarFork() process ended with ERROR=255
Sadly I don't have a recent backup


Edit: it worked Fine
Thank badmofo for the update
 
Last edited:
I flashed a new kernel and I cannot be sure if it's something I flashed but now TWRP is in a boot loop. It boots to the TWRP loading logo, blanks, flashes backlight twice, then reloads the logo. Anything I should test for before I try to recover through "download mode"?
 
@Bad_MOFO_33 Ok I was able to recover my boot loop hell because somehow I could still get a shell with "adb shell" in TWRP v3.0.0 although it was looping it's load screen. I flashed the old v2.8.7.0 with OTG you gave me via the following command below. My bad kernel flash (I changed code I should not have) cause a bug or something to boot loop with v3.0.0. Not sure what to do from here, never had to debug a recovery so I dunno how.

dd if=/sdcard/TWRP_OTG.img of=/dev/block/mmcblk0p17

EDIT: My code change was different from the OTG change I made earlier. I was trying to get OTG plus charging working, the ACA Y cable. For whatever reason this change took out battery support, the device boots to the lock screen with a red X in the battery icon in the corner then goes to power off as if the battery was dead. My theory is that some value gets stored so when recovery loads it still believes the battery isn't there (or some bug). v2.8.7.0 doesn't react in this same manner, I just tested that fact with my faulty kernel change, it powers off but I'm still able to boot into recovery with v2.8.7.0. Could be some ultra rare bug no one will trigger normally but I'm really not sure.
 
Last edited:
ok going to flash this new TWRP 3.0.0 using older TWRP itself, forgot do I select BOOT or RECOVERY when flashing ? Im thinking RECOVERY but dont wanna mess this up. LOL
 
You must log in or register to reply here.
Back
Top Bottom