Introducing XDA:DevCon – A Conference For Developers By Developers
XDA Developers Android and Mobile Development Forum
Forgot your password?
 
Post Reply+
Tip us?
 
vxbinaca
Old
#211  
Senior Member
Thanks Meter 15
Posts: 162
Join Date: Jan 2011
One last question about the ROM: When will NAND encryption be working?
 
droideastcoast
Old
(Last edited by droideastcoast; 28th August 2012 at 06:17 AM.)
#212  
droideastcoast's Avatar
Member
Thanks Meter 4
Posts: 32
Join Date: Aug 2012
Question: Will CM Team be working on Android 4.1 Jelly Bean for the (T-Mobile MyTouch Q - LG C800) , (Bell/Virgin Eclypse - LG C800G) ?
 
chui101
Old
(Last edited by chui101; 28th August 2012 at 07:21 AM.)
#213  
chui101's Avatar
Senior Member - OP
Thanks Meter 279
Posts: 286
Join Date: Sep 2010
Location: Lexington, KY

 
DONATE TO ME
Quote:
Originally Posted by vxbinaca View Post
One last question about the ROM: When will NAND encryption be working?
The phone does not have a NAND; everything is eMMC (even the bootloader). I don't think it will work. If it could encrypt the device it would also encrypt the bootloader, recovery, radio, etc. and you would probably not have a working phone.

Edit: nevermind, looks like that's something else. I'll look into it.
# cat /etc/motd
cm9 for lg c800/t-mobile mytouch q
cwm recovery for lg c800/t-mobile mytouch q
cm10 ffc mod for vibrantmtd
# ls -l /dev/android
drwxr-xr-x 1 chui101 users 4096 Dec 09 2010 01:28 bn_encore
drwxr-xr-x 1 chui101 devel 4096 Jun 28 2012 15:24 lge_c800
drwxr-xr-x 1 chui101 users 4096 Sep 24 2010 03:07 samsung_vibrantmtd

The Following User Says Thank You to chui101 For This Useful Post: [ Click to Expand ]
 
vxbinaca
Old
#214  
Senior Member
Thanks Meter 15
Posts: 162
Join Date: Jan 2011
Quote:
Originally Posted by droideastcoast View Post
Question: Will CM Team be working on Android 4.1 Jelly Bean for the (T-Mobile MyTouch Q - LG C800) , (Bell/Virgin Eclypse - LG C800G) ?
If it's getting auto-built I imagine it'll just auto-build. Theres no reason I can see why the Q can't handle JB.

Quote:
Originally Posted by chui101 View Post
The phone does not have a NAND; everything is eMMC (even the bootloader). I don't think it will work. If it could encrypt the device it would also encrypt the bootloader, recovery, radio, etc. and you would probably not have a working phone.

Edit: nevermind, looks like that's something else. I'll look into it.

"Encrypted Phone" under Security in Settings, thats what I was looking to get working.
 
whitetiger_0603
Old
#215  
Senior Member
Thanks Meter 15
Posts: 254
Join Date: Mar 2012
Location: Boutte, LA
Quote:
Originally Posted by gagdude View Post
You should be on command prompt and I think you need to type in "adb root" first to get adb root access.
Btw, I have discussed this with chui101 and I've bricked my phone. Hard bricked. So I guess Ill be leaving the... device threads...?lol. Damn. Surprised I'm taking it so well considering the fact I only had the phone for a week and rooted it for an hour before I messed up.

Sent from my MB508 using xda premium
And this is EXACTLY what I mean. I don't need to be bricking my husband's phone. Granted I can always take it back if using SDK doesn't help me fix it, but our cell phones are our only phone lines and he's already annoyed that i wiped his phone last night trying to access ADB and such. I truly appreciate the work that is done with these phones and ik now how hard it can be, but being mouthy when a few questions are asked isn't winning any points for anyone. I tried command prompt and that wouldn't work either.
 
gagdude
Old
#216  
gagdude's Avatar
Senior Member
Thanks Meter 498
Posts: 2,366
Join Date: Jun 2012
Location: Northbrook
Quote:
Originally Posted by whitetiger_0603 View Post
And this is EXACTLY what I mean. I don't need to be bricking my husband's phone. Granted I can always take it back if using SDK doesn't help me fix it, but our cell phones are our only phone lines and he's already annoyed that i wiped his phone last night trying to access ADB and such. I truly appreciate the work that is done with these phones and ik now how hard it can be, but being mouthy when a few questions are asked isn't winning any points for anyone. I tried command prompt and that wouldn't work either.
Oh no I hard bricked because I decided to mess with the bootloader, not because I did something wrong on this guide.
You can also access adb fully booted up.
And in order for it to work you go to the adb folder, push SHIFT + RIGHT CLICK, and open in command prompt (or something like that). Then type in adb root [enter] and start using the guide.

Sent from my DROID2 using xda premium
MY LINE OF DEVICES

iPod Touch 4
Motorola Cliq
LG Ally
Motorola Droid
Motorola Droid 2
Samsung Focus
Motorola Flipside
LG MyTouch Q
Kyocera Rise
LG Nexus 4
Motorola Atrix 2

The Following 2 Users Say Thank You to gagdude For This Useful Post: [ Click to Expand ]
 
whitetiger_0603
Old
#217  
Senior Member
Thanks Meter 15
Posts: 254
Join Date: Mar 2012
Location: Boutte, LA
Quote:
Originally Posted by gagdude View Post
Oh no I hard bricked because I decided to mess with the bootloader, not because I did something wrong on this guide.
You can also access adb fully booted up.
And in order for it to work you go to the adb folder, push SHIFT + RIGHT CLICK, and open in command prompt (or something like that). Then type in adb root [enter] and start using the guide.

Sent from my DROID2 using xda premium
Thanks. Much better. I'll give this a shot later

Sent from my LG-E739 using xda app-developers app
 
whitetiger_0603
Old
#218  
Senior Member
Thanks Meter 15
Posts: 254
Join Date: Mar 2012
Location: Boutte, LA
Wow this thread died....... no updates?
 
kdog1202
Old
#219  
kdog1202's Avatar
Senior Member
Thanks Meter 49
Posts: 728
Join Date: Feb 2012
Location: green bay wi
On the LG e379 were kinda experiencing the same problem..

Sent from my LG-E739 using xda premium
 
bernz508
Old
#220  
bernz508's Avatar
Senior Member
Thanks Meter 4
Posts: 107
Join Date: Jul 2012
Default Please help!!

Hello all, i have just rooted my lg mytouch q and am having a bit of difficulty getting CWM soi can flash a ROM.. i have followed all of the steps on the wiki page but at the end where i put in the cwm code i keep getting this....Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Tess>CD c:\android-sdk-windows

c:\android-sdk-windows>CD platform-tools

c:\android-sdk-windows\platform-tools>adb
Android Debug Bridge version 1.0.29

-d - directs command to the only connected USB devic
e
returns an error if more than one USB device is
present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is r
unning.
-s <serial number> - directs command to the USB device or emulator w
ith
the given serial number. Overrides ANDROID_SERI
AL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.

If -p is not specified, the ANDROID_PRODUCT_OUT

environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number
is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number
is specified.
Using this command with no additional arguments

will disconnect from all connected TCP/IP devic
es.

device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport

adb install [-l] [-r] [-s] [--algo <algorithm name> --key <hex-encoded key> --
iv <hex-encoded iv>] <file>
- push this package file to the device and instal
l it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data
)
('-s' means install on SD card instead of inter
nal storage)
('--algo', '--key', and '--iv' mean the file is
encrypted already)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories
)
adb bugreport - return all information from the device
that should be included in a bug report.

adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
- write an archive of the device's data to <file>
.
If no -f option is supplied then the data is wr
itten
to "backup.ab" in the current directory.
(-apk|-noapk enable/disable backup of the .apks
themselves
in the archive; the default is noapk.)
(-shared|-noshared enable/disable backup of the
device's
shared storage / SD card contents; the defau
lt is noshared.)
(-all means to back up all installed applicatio
ns)
(-system|-nosystem toggles whether -all automat
ically includes
system applications; the default is to inclu
de system apps)
(<packages...> is the list of applications to b
e backed up. If
the -all or -shared flags are passed, then t
he package
list is optional. Applications explicitly g
iven on the
command line will be included even if -nosys
tem would
ordinarily cause them to be omitted.)

adb restore <file> - restore device contents from the <file> backup
archive

adb help - show this help message
adb version - show version num

scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specifie
d device
adb remount - remounts the /system partition on the device re
ad-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on th
e specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns

adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:

- If <directory> is not specified, both /system and /data partitions will be u
pdated.

- If it is "system" or "data", only the corresponding partition
is updated.

environmental variables:
ADB_TRACE - Print debug information. A comma separated list
of the following values
1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes prior
ity over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these de
bug tags are printed.

c:\android-sdk-windows\platform-tools>adb devices
List of devices attached
80A012826001498082 device


c:\android-sdk-windows\platform-tools>adb reboot bootloader

c:\android-sdk-windows\platform-tools>fastboot flash recovery cwm-6.0.1.2-lgc800
-chui101.img
error: cannot load 'cwm-6.0.1.2-lgc800-chui101.img'


c:\android-sdk-windows\platform-tools>fastboot flash recovery cwm-6.0.1.2-lgc800
-chui101.img
error: cannot load 'cwm-6.0.1.2-lgc800-chui101.img'


c:\android-sdk-windows\platform-tools>fastboot flash recovery cwm-6.0.1.2-lgc800
-chui101.img
error: cannot load 'cwm-6.0.1.2-lgc800-chui101.img'


c:\android-sdk-windows\platform-tools>fastboot flash recovery cwm-6.0.1.2-lgc800
-chui101.img
error: cannot load 'cwm-6.0.1.2-lgc800-chui101.img'


Please any and all help is greatly appreciate it..

 
Post Reply+
Tags
clockwork, cwm, mytouch q, recovery
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

report this ad
Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Go to top of page...