Yes & yes the onandroid log reports 2.6.0.0 and might be the reason twrp 2.6.3.0 failed the restore of Android secure.
Upvote
0
Gave it a go... I'm seeing exactly the same ADB behavior here as on CWM 6.0.4.5 assert fixed. ADB *does* work (confirmed from my MacBook using ADB from the 4.4 platform tools for Mac). When I connect to my Windows 8.1 PC, the phone just shows as and unknown device named VS920 using either your debug build or assert fixed. When I kick back to CWM 6.0.1.1 and reboot recovery, Windows does recognize the device and installs/activates the appropriate LG and/or Google drivers. I'm guessing it's a hardware id issue somewhere.Alright... so it looks like I can manually change the version, but my pulls from their github just keeps 2.6.3.0. I went ahead and added " - debug" to the end of it for now to differentiate versions.
This should install kitkat roms fine, I've removed the force rm -rf option so now it'll format instead of just deleting.
I've only done minor testing so far. Mounting usb storage works, restoring a backup worked. However... for some reason I can't get ADB access. Can someone try this and let me know how they fare?
Dev-Host - TWRP_Test.zip - The Ultimate Free File Hosting / File Sharing Service
*As Always, I'm not responsible if you mess up your phone using this*
Gave it a go... I'm seeing exactly the same ADB behavior here as on CWM 6.0.4.5 assert fixed. ADB *does* work (confirmed from my MacBook using ADB from the 4.4 platform tools for Mac). When I connect to my Windows 8.1 PC, the phone just shows as and unknown device named VS920 using either your debug build or assert fixed. When I kick back to CWM 6.0.1.1 and reboot recovery, Windows does recognize the device and installs/activates the appropriate LG and/or Google drivers. I'm guessing it's a hardware id issue somewhere.
Working USB "Hardware Id" from Device Manager / CWM 6.0.1.1
ADB = USB\VID_1004&PID_6204&REV_0227&MI_06
Unrecognized USB "Hardware Id" from Device Manager / CWM 6.0.4.5 Assert fixed
USB\VID_18D1&PID_D001&REV_0231
Unrecognized USB "Hardware Id" from Device Manager / TWRP Test/Debug
USB\VID_1004&PID_0001&REV_0231&MI_01
If it helps, I can also confirm that your build is capable of formatting sdcard, mounting USB storage, transferring (receiving) files, formatting system, and installing PacePlus 4.4 rc2b + PA Gapps 4.4 Full 20131126Interesting. So it does work, just not under windows. Once I get adb working I can work on/verify that the asserts work right (without having to continuously reflash roms on my DD >.> )
Should be able to tweak the hardware IDs. And for ADB to work, just make sure the IDs are in the ADB.inf file. So it will work if you force install the driver OR add the IDs to the inf.Interesting. So it does work, just not under windows. Once I get adb working I can work on/verify that the asserts work right (without having to continuously reflash roms on my DD >.> )
Should be able to tweak the hardware IDs. And for ADB to work, just make sure the IDs are in the ADB.inf file. So it will work if you force install the driver OR add the IDs to the inf.
I don't have a copy of the code synced, but I'll download it later and grep it to see if I can find where the changes should be made.
So I am trying to root my Verizon LG Spectrum VS920 then flash to Page Plus with 3G at the store or from an online flasher and I have had more than 30 tabs open today trying to find a solution that works. I still need to root, but I already have my copy of Beanstalk 4.3 ready to go for when I can get it rooted. I have the LG drivers installed right from the LG site, as well as a few other "all in ones" that did nothing. Is there a preferred way?
I would love an update, 2.6.3.8 is out.
Yeah, I'm working on that now.
TWRP also used to need an extra bit of forcing adbd to run as well as restarting it for root to work.
Hopefully I'll have it sorted shortly.
I'm trying to force the hardware id. The Vendor ID always gets forced to 1004. Attempting to force the Product ID, is causing windows to BlueScreen on me now... (even though it works fine under linux)... go figure.
Hey Yoinx. Did you ever get anywhere with a new TWRP update?
Does anyone still have the last TWRP_Test.zip they can PM me or post a link to? The dev host link says the file no longer exists.
If anyone still needs a copy of this... https://www.dropbox.com/s/t8n3kf45itxlirs/TWRP_Test.zipAlright... so it looks like I can manually change the version, but my pulls from their github just keeps 2.6.3.0. I went ahead and added " - debug" to the end of it for now to differentiate versions.
This should install kitkat roms fine, I've removed the force rm -rf option so now it'll format instead of just deleting.
I've only done minor testing so far. Mounting usb storage works, restoring a backup worked. However... for some reason I can't get ADB access. Can someone try this and let me know how they fare?
Dev-Host - TWRP_Test.zip - The Ultimate Free File Hosting / File Sharing Service
*As Always, I'm not responsible if you mess up your phone using this*
Give these a try, patience, it's the first time I shared a file with Drive. The first link is the md5 file which I hope you use.I want to try TWRP recovery but it seems that the download link is not working and also would and update to 2.7 be possible? Thanks to all the developers for making this device awesome
Give these a try, patience, it's the first time I shared a file with Drive. The first link is the md5 file which I hope you use.
https://docs.google.com/file/d/0B-hIwOVZTB95UC1oclVUd0VjVU0/edit?usp=docslist_api
https://docs.google.com/file/d/0B-hIwOVZTB95NVJodWxEdldnQUU/edit?usp=docslist_api
If you're going to be downloading and flashing files then learning about md5 sum is highly recommended, unless you like living dangerously. If you just keep the files together, most custom recoveries will check the sum before flashing.I'm not to sure what an md5 file is to be completely honest? Would it affect the installing of TWRP? But thanks for the link
We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.