Install the Flashify app. Among other things, it will allow you to easily boot into recovery.I am new to rooting and custom recoveries, so please be gentle.
I've been rooted for a while now and using some apps with root access and I'm quite happy with it.
So I'm ready for the next step, installing my first custom recovery.
With flashify and the method hereunder, I think I managed to get TWRP installed.
If I now look in flashify, TWRP 2.6.3.2 shows up as current recovery for backup, so I guess TWRP installed succesfully.
My next step would be to make a full backup I guess.
But how do I "open" or get "into" TWRP, do I have to use a key combination or something while rebooting?
It's probably a stupid question but if anyone can clarify I'd appreciate it.
[RECOVERY] [TWRP 2.8.0.0] [v500] [9-11-2014]
- Thread starter Drgravy
- Start date
Just picked up a G Pad late this week.
@Drgravy
Are you using the TW_BRIGHTNESS_PATH and TW_MAX_BRIGHTNESS flags in your BoardConfig.mk/BoardCommonConfig.mk? I find the darkness too low. It's 120 of a possible 255 and it would be nice to have the slider to control it rather then echo-ing it.
adb shell cat /sys/class/leds/lcd-backlight/brightness
I get 120 for default. Brightness looks nice at 255(max).
adb shell "echo 255 > /sys/class/leds/lcd-backlight/brightness"
On the next build if you add these flags it would add the slider for the GUI under Settings-Screen in TWRP
TW_MAX_BRIGHTNESS := 255
TW_BRIGHTNESS_PATH := "/sys/class/leds/lcd-backlight/brightness"
On a side note I really have never been a huge fan of the default TWRP theme, and this G Pad has such a dark screen I thought I would see what I could do with a theme to make it better for myself. I build/maintain the TWRP recoveries for the Fuhu Nabi tablets and I am use to just building the theme in to the source so I have never tried to make an "external" theme. Kind of fun to play with this higher resolution G Pad. Thought I would see if anyone else was interested in it, don't want to thread jack but I'm not going to make a new thread if no one is interested in it. Images below are compressed looks better on the Pad.
Here is a flashable zip for anyone that wants it TWRP 2.6.3.2 Theme
Remove by deleting ui.zip from /sdcard/TWRP/theme with TWRP File Manager.
@Drgravy
Are you using the TW_BRIGHTNESS_PATH and TW_MAX_BRIGHTNESS flags in your BoardConfig.mk/BoardCommonConfig.mk? I find the darkness too low. It's 120 of a possible 255 and it would be nice to have the slider to control it rather then echo-ing it.
adb shell cat /sys/class/leds/lcd-backlight/brightness
I get 120 for default. Brightness looks nice at 255(max).
adb shell "echo 255 > /sys/class/leds/lcd-backlight/brightness"
On the next build if you add these flags it would add the slider for the GUI under Settings-Screen in TWRP
TW_MAX_BRIGHTNESS := 255
TW_BRIGHTNESS_PATH := "/sys/class/leds/lcd-backlight/brightness"
On a side note I really have never been a huge fan of the default TWRP theme, and this G Pad has such a dark screen I thought I would see what I could do with a theme to make it better for myself. I build/maintain the TWRP recoveries for the Fuhu Nabi tablets and I am use to just building the theme in to the source so I have never tried to make an "external" theme. Kind of fun to play with this higher resolution G Pad. Thought I would see if anyone else was interested in it, don't want to thread jack but I'm not going to make a new thread if no one is interested in it. Images below are compressed looks better on the Pad.
Here is a flashable zip for anyone that wants it TWRP 2.6.3.2 Theme
Remove by deleting ui.zip from /sdcard/TWRP/theme with TWRP File Manager.
auto search cmupdater folder possible in future TWRP builds?
When I originally updated from stock ROM to CM Nightly it was from an external card "sdcard1" which worked fine, until CM prompted for a nightly update,
I Okay'd the update & when the update finished downloading & confirmed, it auto rebooted into TWRP to do the auto update but it read the following,
Updating partition details . . .
Running boot script . . .
Finished running boot script.
Processing AOSP recovery commands . . .
Unable to locate zip file '/sdcard 0/cmupdater/cm-11-20140131-NIGHTLY-v500.zip'.
E:Error installing zip file '/sdcard 0/cmupdater/cm-11-20140131-NIGHTLY-v500.zip
Done processing script file
note* when i looked in sdcard 0 for the cmupdater file folder cm-11-20140131-NIGHTLY-v500.zip existed,
so I manually rebooted into TWRP
pressed install,
Changed directory from "storage micro SD card" sdcard1 to "internal storage" sdcard0 & okay'd,
Opened the cmupdater folder & selected cm-11-20140131-NIGHTLY-v500.zip
swiped to confirm flash/ flash successful, manually rebooted system..
The original install error was caused because TWRP was looking in sdcard1 not sdcard0 for the cmupdater folder.
It's no big deal as CM is auto updating fine now after I set to sdcard0.
In future TWRP releases is there a way of making TWRP auto look in sdcard0 when searching for the cmupdater folder as sdcard0 is the default location for CM auto updates.
When I originally updated from stock ROM to CM Nightly it was from an external card "sdcard1" which worked fine, until CM prompted for a nightly update,
I Okay'd the update & when the update finished downloading & confirmed, it auto rebooted into TWRP to do the auto update but it read the following,
Updating partition details . . .
Running boot script . . .
Finished running boot script.
Processing AOSP recovery commands . . .
Unable to locate zip file '/sdcard 0/cmupdater/cm-11-20140131-NIGHTLY-v500.zip'.
E:Error installing zip file '/sdcard 0/cmupdater/cm-11-20140131-NIGHTLY-v500.zip
Done processing script file
note* when i looked in sdcard 0 for the cmupdater file folder cm-11-20140131-NIGHTLY-v500.zip existed,
so I manually rebooted into TWRP
pressed install,
Changed directory from "storage micro SD card" sdcard1 to "internal storage" sdcard0 & okay'd,
Opened the cmupdater folder & selected cm-11-20140131-NIGHTLY-v500.zip
swiped to confirm flash/ flash successful, manually rebooted system..
The original install error was caused because TWRP was looking in sdcard1 not sdcard0 for the cmupdater folder.
It's no big deal as CM is auto updating fine now after I set to sdcard0.
In future TWRP releases is there a way of making TWRP auto look in sdcard0 when searching for the cmupdater folder as sdcard0 is the default location for CM auto updates.
thanks so much
instruction were as simple as you like and pretty straight forward
thanks again
instruction were as simple as you like and pretty straight forward
thanks again
Yes, I'm also interested about this. My PAD was updated recently, but I'm considering to install another ROM. Which version should we use, v50010a?
Thank you!
Just wanted to report that flashing the twrp.lok via flashify works.
I am on software b and used the linked twrp.lok from the V50010a download.
good evening everyone,
after installing TWRP 2.6.3.1 tried to install TWRP 2.6.3.2 zip through the recovery but I always fail zip
after installing TWRP 2.6.3.1 tried to install TWRP 2.6.3.2 zip through the recovery but I always fail zip
Hi,
I have version V50010b my build.prop is:
What file should I download?
I have version V50010b my build.prop is:
What file should I download?
Hello darkvoid,
the user katsika just answered me regarding this topic on the previous page
http://forum.xda-developers.com/showthread.php?t=2551499&page=21
Best regards
So once Rooted i would:
-Download Flashify
-Move twrp.lok into internal tablet storage as twrp.img
-Use flashify to flash twrp.img
-I'll have TWRP recovery installed.
That all?
Last edited:
Yes, exactly.
My twrp.lok was on my sdext but that should make no difference.
My twrp.lok was on my sdext but that should make no difference.
Awesome. And I don't need all the other files from the loki zip, just the twrp.lok file?
Maybe someone else can clarify what the other files are. As far as I know they are files (like adb and skript files) which your computer needs in order to connect to your tablet. I think the files are provided by flashify and are standard files you need to flash every android device. Just make sure to make a nandroid backup in advance
You are right. I just flashed the twrp .img file within my device and flashify did the rest. Then once in twrp I flashed the 2.6.3.2 zip from the 1st page and all was well.
I love XDA.
Hi,
I had the bad idea to upgrade my lg g pad stock rom with the new update available on the LG software update app, but then it got stuck on booting in recovery only.
Previously I put this TWRP recovery on the pad, so the problem is that the lg update pack is not able to update the stock rom with a different recovery than the original one.
I tried to wipe everything from the recovery mode and to flash CM11, but no way, it keeps booting directly in recovery.
Any clue how to solve this messy situation?
Should I try to flash the stock recovery back? where can I find it and how to flash it?
Thank you very much, any help appreciated.
I had the bad idea to upgrade my lg g pad stock rom with the new update available on the LG software update app, but then it got stuck on booting in recovery only.
Previously I put this TWRP recovery on the pad, so the problem is that the lg update pack is not able to update the stock rom with a different recovery than the original one.
I tried to wipe everything from the recovery mode and to flash CM11, but no way, it keeps booting directly in recovery.
Any clue how to solve this messy situation?
Should I try to flash the stock recovery back? where can I find it and how to flash it?
Thank you very much, any help appreciated.
i would try what is says in this thread (its for the G2, but since they are LG loki devices and rooted almost the same way it seems worth a shot) exactly that same thing happened on my roommates g2 and it fixed it right away
http://forum.xda-developers.com/showthread.php?t=2451696
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone