Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,781,962 Members 50,919 Now Online
XDA Developers Android and Mobile Development Forum

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

Tip us?
 
Chance77
Old
#61  
Senior Member
Thanks Meter 51
Posts: 149
Join Date: Dec 2012
Location: Monroe

 
DONATE TO ME
Quote:
Originally Posted by Drgravy View Post
Ah I see I forgot to update loki Please try this one
This says succesful.
Any word on a custom rom running on these altev models yet?

Sent from my VK810 4G using XDA Premium HD app
Sent From My Avatar Galaxy 4.2.2
 
paperWastage
Old
#62  
Senior Member
Thanks Meter 395
Posts: 805
Join Date: Mar 2009
Location: NJ
Quote:
Originally Posted by Chance77 View Post
This says succesful.
Any word on a custom rom running on these altev models yet?

Sent from my VK810 4G using XDA Premium HD app
well, I'm the only one trying right now.

if you don't mind flashing the ROM i compiled and PMing me the kernel log to see what's wrong with WiFi/BT/LTE connection

http://forum.xda-developers.com/show...9&postcount=14

I might have access to a friend's vk810 next week, so you could wait as well

Quote:
Originally Posted by traccdma View Post
that got much further and even booted into CyanogenMod 11 with the VZW Gpad V810!!

After unzipping your file, overwriting the update-binary file in meta-inf\com\google\android with the file from the thread you posted, it said successful. Rebooted once while it said Android is updating app xxx of xxx, then Welcome to CyanogenMod

Seems to be missing drivers though. First boot seemed stable except it didn't recognize Verizon mobile data (or SIM card). I was in there at least 10 minutes. In settings, I used the slider to try and turn on wifi, but it never turned blue and a few seconds later it reverted back off. I slid bluetooth on, and it did the same thing and went into a boot loop. It gets to the android desktop for about 5 seconds then reboots. I wiped cache and dalvik cache and it got no further.
Current Device:
Oppo Find 5 - experimental kernel
The Following 3 Users Say Thank You to paperWastage For This Useful Post: [ Click to Expand ]
 
ibawanzingee
Old
#63  
Senior Member
Thanks Meter 87
Posts: 536
Join Date: Dec 2010
Hey, this sounds promising! Thanks for taking this on!

Quote:
Originally Posted by paperWastage View Post
well, I'm the only one trying right now.

http://forum.xda-developers.com/show...9&postcount=14

I might have access to a friend's vk810 next week, so you could wait as well
 
NICG
Old
#64  
Member
Thanks Meter 9
Posts: 49
Join Date: Aug 2011
Location: Greensburg
Quote:
Originally Posted by Drgravy View Post
Has the Verizon tablet had a 4.4.2 ota yet?
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.
Devices:
Verizon HTC One m8 - ViperONEm8
Verizon LG Gpad 8.3 - Stock(No Roms YET )
Retired:
Verizon Galaxy S3 - Stock(Permanently Locked took update)
TMobile HTC Sensation - ViperS
 
Drgravy
Old
#65  
Drgravy's Avatar
Senior Member - OP
Thanks Meter 1,416
Posts: 660
Join Date: Mar 2012
Quote:
Originally Posted by NICG View Post
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
The Following 4 Users Say Thank You to Drgravy For This Useful Post: [ Click to Expand ]
 
rant
Old
(Last edited by rant; 29th May 2014 at 06:50 PM.)
#66  
Member
Thanks Meter 6
Posts: 38
Join Date: Nov 2004
Quote:
Originally Posted by Drgravy View Post
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
My home Internet has crapped out and I need to get data working on the VK810, so unfortunately need to revert to stock for a bit since data isn't working on this port of CM11 yet. However, tried the above and get the following:

/dev/block/platform/msm_sdcc.1/by-name/recovery: cannot open for write: Permission denied

Edit: interestingly, I was able to run this from the device itself with a Terminal Emulator, but it doesn't seem to restore the stock image, even after a reboot. Is that not the intent of these commands?
 
paperWastage
Old
#67  
Senior Member
Thanks Meter 395
Posts: 805
Join Date: Mar 2009
Location: NJ
Quote:
Originally Posted by rant View Post
My home Internet has crapped out and I need to get data working on the VK810, so unfortunately need to revert to stock for a bit since data isn't working on this port of CM11 yet. However, tried the above and get the following:

/dev/block/platform/msm_sdcc.1/by-name/recovery: cannot open for write: Permission denied

Edit: interestingly, I was able to run this from the device itself with a Terminal Emulator, but it doesn't seem to restore the stock image, even after a reboot. Is that not the intent of these commands?
Nope. Those commands are for restoring stock recovery instead of having the custom TWRP recovery. Stock recovery is required when applying an ota update ( which probably will never show up from Verizon)

To restore the stock ROM: remember how you are supposed to backup inside twrp before flashing cm11? Go back to twrp (you might need to reflash twrp since thode commands restored stick recovery ) and restore from that backup. Stock ROM will be restored and usable

(but recovery is still TWRP. If you want full stock ROM and stock recovery , then restore from the backup AND follow the DD instructions you quoted )
Current Device:
Oppo Find 5 - experimental kernel
 
rant
Old
#68  
Member
Thanks Meter 6
Posts: 38
Join Date: Nov 2004
Quote:
Originally Posted by paperWastage View Post
Nope. Those commands are for restoring stock recovery instead of having the custom TWRP recovery. Stock recovery is required when applying an ota update ( which probably will never show up from Verizon)

To restore the stock ROM: remember how you are supposed to backup inside twrp before flashing cm11? Go back to twrp and restore from that backup. Stock ROM will be restored and usable

(but recovery is still TWRP. If you want full stock ROM and stock recovery , then restore from the backup AND follow the DD instructions you quoted )
Thanks. I did eventually figure out that this isn't the stock ROM, just recovery. And stupid me, no backup before flashing CM11. Oops, guess I'll make do until we see a ROM with LTE support or a stock ROM, nothing on LG's site but the open source files.
 
rkmFL
Old
#69  
Senior Member
Thanks Meter 10
Posts: 105
Join Date: Dec 2010
I'm having an identical issue to an earlier user. That user had not originally assumed root (run "su"). In my case I've tried everything but can't get su to take, based on the instructions here.

Here are my details:
-------------------
* G Pad 8.3 Model# VK810 (Verizon VZW)

* Running 4.2.2(JDQ39B) - I have not accepted any OTA updates

* USB Debugging Enabled, USB > Internet > Ethernet Connection Enabled

* Successfully connects and shows devices with the ADB DEVICES command
-------------------

I have no problem with any of the adb commands, I am able to push both files, change permissions, etc.

The only thing I cannot do is invoke SU, I get:

/system/bin/sh: su: not found

Because I don't have superuser privileges, I then get this error when attempting to run the loki_flash:

./loki_flash recovery /data/local/tmp/twrp.lok
[+] loki_flash v2.1
[-] Failed to open aboot for reading.

All adb commands are working great, I can move around directories, etc. I just can't run su.

Thank you in advance for any insight!
rkmFL
 
Drgravy
Old
#70  
Drgravy's Avatar
Senior Member - OP
Thanks Meter 1,416
Posts: 660
Join Date: Mar 2012
Quote:
Originally Posted by rkmFL View Post
I'm having an identical issue to an earlier user. That user had not originally assumed root (run "su"). In my case I've tried everything but can't get su to take, based on the instructions here.
rkmFL
are you sure you are rooted?
you could check with root checker
also after the su command you will have to accept the su dialog on the device

** also you can run the same commands from your device through terminal emulator minus the "adb shell" of course

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes