[RECOVERY] [TWRP 2.7.0.1] [altev | VK810] [4-21-2014]

Search This thread

TYMO68

Senior Member
Jun 24, 2012
452
76
Hello, I'm curious as the to if this new recovery can be flashed using the Flashify app from play store?

Sent from my VK810 4G using XDA Premium 4 mobile app
 

ibawanzingee

Senior Member
Dec 8, 2010
598
99
Probably not, and I wouldn't take the chance. This is a very different and specific method for flashing a recovery, because of Loki.

Hello, I'm curious as the to if this new recovery can be flashed using the Flashify app from play store?

Sent from my VK810 4G using XDA Premium 4 mobile app
 

TYMO68

Senior Member
Jun 24, 2012
452
76
Probably not, and I wouldn't take the chance. This is a very different and specific method for flashing a recovery, because of Loki.

Agreed, I didn't go that route with flashify. It was quick, easy, and simple based on the suggested method in the OP. I now have TWRP successfully and have already completed my first nandroid :) Now on to ROM developments hopefully to come soon.

Sent from my VK810 4G using XDA Premium 4 mobile app
 

ibawanzingee

Senior Member
Dec 8, 2010
598
99
I can't wait!!

Agreed, I didn't go that route with flashify. It was quick, easy, and simple based on the suggested method in the OP. I now have TWRP successfully and have already completed my first nandroid :) Now on to ROM developments hopefully to come soon.

Sent from my VK810 4G using XDA Premium 4 mobile app
 

cobra7361

Senior Member
Nov 10, 2013
401
202
I keep getting
Sh: cd/data/local/tmp : not found
Can anyone help me with this..
What am i doing wrong...installed adb...but have never used before...i knoe its working
Cause i can type adb devices and it shows mh tablet...or if i type adb reboot it works
Any help or advice would be great

I am a total noobie at adb....do i need to have my tablet in download mode or?
If someone could walk me through this step by step i would
Greatly appreciate it..
 
Last edited:

cobra7361

Senior Member
Nov 10, 2013
401
202
Thank u @Drgravy
But i am getting no such file or directory for the first command line..
Sorry for all the stupid questions. ..i just havr never used adb or pushed files before..

Guess i have alot of research to do..
If anyone knows good videos please let me k,ow
 

Drgravy

Senior Member
Mar 22, 2012
985
2,537
Thank u @Drgravy
But i am getting no such file or directory for the first command line..
Sorry for all the stupid questions. ..i just havr never used adb or pushed files before..

Guess i have alot of research to do..
If anyone knows good videos please let me k,ow

can you paste everything you have done in your terminal so far
I can probably help you but I need all the info on exactly what you have done so far
also when you ran the su command did you accept the prompt on your tablet?
 
  • Like
Reactions: cobra7361

cobra7361

Senior Member
Nov 10, 2013
401
202
I exited out of everything...
After u meantioned the space i looked at what i had writen down and i missed a few spaces..so i was entering
Things wrong...so once i enteted the first command line correctly it said no such file or directory..
Do i need to extract the zip to a certain place or file?...i am definatly lost here...lol
I need to start over maybe...i definatly need a step by step guide...lol
 

Drgravy

Senior Member
Mar 22, 2012
985
2,537
I exited out of everything...
After u meantioned the space i looked at what i had writen down and i missed a few spaces..so i was entering
Things wrong...so once i enteted the first command line correctly it said no such file or directory..
Do i need to extract the zip to a certain place or file?...i am definatly lost here...lol
I need to start over maybe...i definatly need a step by step guide...lol

Ok lets start over
unzip the file and then open it
hold SHIFT and right click
then select: open command window here

now that you have the command window open in the right directory start running the commands starting with:

adb push loki_flash /data/local/tmp/loki_flash
 

cobra7361

Senior Member
Nov 10, 2013
401
202
Ok lets start over
unzip the file and then open it
hold SHIFT and right click
then select: open command window here

now that you have the command window open in the right directory start running the commands starting with:

adb push loki_flash /data/local/tmp/loki_flash


Ok i did this and it went to next line...now do i just continue with the commands..
I didnt do the shift and right click the first times i was doing this
It wont let me type anything elsr..after i hit enter it went to next line and nw i cant type anymore commands
 
Last edited:
  • Like
Reactions: gtaguitar7596

jaredlappa

Member
May 11, 2007
28
1
I have a VK810 that I am trying to use with my ATT Sim card would appreciate some help.
I would like to root and install some custom roms, but looks like there are no roms available yet?
So I first need to root with this link : http://xdaforums.com/showthread.php?t=2703825
Then I can use your steps here to install roms if any are available?
I have changed the APN settings to the following:
APN: BROADBAND
MCC: 310
MNC: 410
but it still does not read the SIM card that i have with ATT.
If I root it will I be able to change the APN settings and get this working you think? Or is there a way I can unlock this to worK?
Thank you for any tips and advice!
 

cobra7361

Senior Member
Nov 10, 2013
401
202
Please help

@Drgravy
I accidentally hit the button to do a ota update and now I am stuck in bootloop with a error message at top left corner of lg screen...mmessage says...secure booting error cause:device unlock:so boot success
Then goes into twrp...
I have tried wiping...I have tried restoring nandroid and nothing....I have tried to go to factory recovery but will only go to twrp...
Also I have tried to enter download mode so I could use lg tool but when I plug in USB it just starts device and I get error message and the goes into twrp..
IF ANYONE CAN PLEASE HELP ME...PLEASE
 

id10terror

Senior Member
Nov 20, 2010
302
536
@Drgravy
I accidentally hit the button to do a ota update and now I am stuck in bootloop with a error message at top left corner of lg screen...mmessage says...secure booting error cause:device unlock:so boot success
Then goes into twrp...
I have tried wiping...I have tried restoring nandroid and nothing....I have tried to go to factory recovery but will only go to twrp...
Also I have tried to enter download mode so I could use lg tool but when I plug in USB it just starts device and I get error message and the goes into twrp..
IF ANYONE CAN PLEASE HELP ME...PLEASE

You probably just need to wipe your FOTA partition.. Just follow my instructions on this post and you should be fine. You can either do it manually or flash the zip included in that post.

http://xdaforums.com/showthread.php?p=51749086#post51749086
 

Top Liked Posts

  • There are no posts matching your filters.
  • 32
    Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.

    Phone look:
    AgsV.png
    WujW.png

    Tablet look:
    eIDZ.png

    fYob.png


    CHANGELOG for 2.7.0.0:
    -Faster graphics rendering by disabling alpha blending on fully opaque objects thanks to Tassadar
    -Allow sideloading from /tmp on encrypted devices
    -Check for a crypto footer before asking for a password to prevent user confusion
    -Additional checks for validity to auto generated backup names
    -Text wrap in the console output
    -Proper caps lock support in the keyboard
    -Mouse support via USB OTG for devices with a broken digitizer
    -Improve scanning of storage locations for OpenRecoveryScript
    -Haptic feedback for buttons, keyboard, and vibration at the end of longer running actions thanks to Samer Diab
    -Fixed ext4 wiping when no selinux contexts are defined for that partition (e.g. sd-ext)
    -Update SuperSU to 1.93 and improve installation process
    -Added selinux contexts restoration to fix permissions
    -Load RTC offset on Qualcomm devices to fix the date/time in recovery
    -USB Mass Storage fixes Add SELinux support checking
    -Add Disk Usage class to better handle excluded folders (e.g. Google Music cache)
    -Add 4.4 decrypt support
    -Add some toolbox utilities to TWRP (namely to support SELinux functions not supported in busybox)
    -Various SELinux fixes and bug fixes

    Note: 2.7 marks the first time that we are dropping support for older devices. We are doing this because of the SELinux support needed to install 4.4 Kit Kat ROMs. The non-TWRP parts of the recovery image have to be built in at least a 4.1 tree and the kernel that is included in the recovery image has to support writing SELinux contexts. We don't own most of the devices that we support so we depend on outside testers and developers to help us update devices. In many cases we can't find someone readily. Come to #twrp on Freenode if you want to help bring your device up to date. You can tell right away if your device will support 4.4 ROMs in 2.7. Boot TWRP and press the console button (the square-ish button either in the bottom middle or upper right) to view the console output. If it doesn't say "Full SELinux support" in the console, then your device still needs some work. Help us help you.

    CHANGELOG for 2.6.3.0:
    -Proper backup and restore of SELinux contexts (thanks to Tassadar)
    -Pull in some ROM information for backup name generation
    -Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
    -Add 1200x1920 theme (thanks to Tassadar)
    -A few other fixes and tweaks


    CHANGELOG for 2.6.1.0:
    -Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
    -Initial support for f2fs file system formatting (Moto X)
    -Update SuperSU install for 4.3 ROMs
    -Fixed a permissions bug on files created during backup
    -Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
    -Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
    -Ignore lost+found folder during backup and size calculations
    -Various other minor bug fixes and tweaks


    CHANGELOG for 2.6.0.0:
    Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
    -Can encrypt a backup to prevent theft of private data from your backup files
    -Updated graphics / icon courtesy of shift
    -Updated exFAT to latest commits
    -Fixed a problem with Samsung TouchWiz decryption
    -Update SuperSU binary
    -Fixed saving of backup partitions list
    -Fixed saving of last used zip install folder
    -Fixed backup of datadata on devices that use a separate partition for datadata
    -Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
    -Fixed some problems with partitioning a SD card
    -Various other bug fixes and tweaks

    Notes about encrypted backups:
    Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.

    Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.

    DISCLAIMER:
    I nor anyone else is responsible for what you do to your device.
    but if something goes wrong I will do my best to help

    This is for the Verizon Gpad Only

    DOWNLOAD:

    Please note this is for 4.2.2 only!
    Also if you want to take an OTA from Verizon you will need to put the stock recovery back and probably unroot

    VK810_twrp_2.7.0.1.zip just unzip it and follow the directions in the README

    update **
    VK810_twrp_2.7.0.2.zip just flash it in recovery (must have 2.7.0.1 installed first)

    Instructions:

    Code:
    open your terminal and cd to where loki_flash and twrp.lok is
    
    now run these commands:
    
    adb push loki_flash /data/local/tmp/loki_flash
    
    adb push twrp.lok /data/local/tmp/twrp.lok
    
    adb shell
    
    su
    
    cd /data/local/tmp
    
    chmod 777 loki_flash
    
    ./loki_flash recovery /data/local/tmp/twrp.lok
    
    exit
    
    exit
    
    adb reboot recovery
    
    That is it you will now be in recovery
    
    cheers

    CREDITS:

    @djrbliss for his bootloader patch LOKI this wouldn't be possible without it
    @Dees_Troy and team win for this wonderful recovery
    @id10terror for patching the aboot.img for this device. Be sure and thank him
    @traccdma for testing
    if I forgot someone please let me know
    8
    Awesome your commit was merged

    Yep, just saw that! Glad I could contribute something to the Verizon G Pad people!

    Sent from my VS980 4G using Tapatalk
    7
    Thanks for the mention @Drgravy! I've initiated a pull request for the loki_patch changes to djrbliss' git :)

    https://github.com/djrbliss/loki/pull/60

    Sent from my VS980 4G using Tapatalk

    Awesome your commit was merged
    4
    Hey do you happen to have the stock recovery img? I mean I have the stock aboot but not relay sure how the loki patch recovery works. Would like to have in case I would go back to get ota update(if there ever is any). I am also guessing it would need to be loki patched to push because of the locked bootloader. If you could posibly shed some light on how we would go about to go back to stock recovery that would be awesome. Thank You.

    sure get it here: http://goo.gl/cmrBwV

    shouldn't need to loki patch it
    just copy it to your internal storage and flash with dd

    open your terminal on your pc enter the following commands

    Code:
    adb shell
    
    su
    
    dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
    
    exit
    
    exit

    just make sure the commands are exactly right