• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [One Click][Updated]LG Spectrum All in One Pkg for Root, CWM Touch Recovery, and Unroot

Either they changed the naming scheme or they have not pushed it to the update server, because I'm i'm getting is a lot of file not found.
 
I can take a look, but I have a working Linux script based off the one click windows root.

http://www.joelperryproductions.com/wordpress/2012/04/02/lg-spectrum-one-stop-download-shop/

KOOOL I have it rooted....I think

Code:
[*] Device found.
[*] Rebooting device...
[*] Waiting for device to reboot...
[*] Rebooting device again...
[*] Waiting for device to reboot...
[*] Attemping persistence...
remount succeeded
420 KB/s (22364 bytes in 0.051s)
4829 KB/s (1867568 bytes in 0.377s)
5051 KB/s (843503 bytes in 0.163s)
[*] Cleaning up...
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
./run.sh: 94: read: Illegal option -n

Does that look about right?

Next should be CWM right? How do I proceed to get CWM to work? Power and down give me the wipe, take back to factory settings....I think I am missing some steps. I have forum crossfade now...can't remember all the correct steps. The initial steps are cool....but a full on tutorial would rock....again....certified noob here but I am ready to learn....yes I searched....have a few points that go one way, several that talk about windows...not a whole lot that talk about straight linux installs. If you could point me to your all in one script that would be cool
 
KOOOL I have it rooted....I think

Code:
[*] Device found.
[*] Rebooting device...
[*] Waiting for device to reboot...
[*] Rebooting device again...
[*] Waiting for device to reboot...
[*] Attemping persistence...
remount succeeded
420 KB/s (22364 bytes in 0.051s)
4829 KB/s (1867568 bytes in 0.377s)
5051 KB/s (843503 bytes in 0.163s)
[*] Cleaning up...
[*] Rebooting...
[*] Exploit complete!
[*] Press any key to exit.
./run.sh: 94: read: Illegal option -n
Does that look about right?

Next should be CWM right? How do I proceed to get CWM to work? Power and down give me the wipe, take back to factory settings....I think I am missing some steps. I have forum crossfade now...can't remember all the correct steps. The initial steps are cool....but a full on tutorial would rock....again....certified noob here but I am ready to learn....yes I searched....have a few points that go one way, several that talk about windows...not a whole lot that talk about straight linux installs. If you could point me to your all in one script that would be cool

Here is the other message
Code:
~/Downloads/Phone root fix files/Here Second$ sudo ./linux.sh
This script will push the ClockWork Mod Touch Recovery,
insTall a blocking hosts file, and put the CWM Boot loop
fix on your SD card.
: not found 4: ./linux.sh: echo
Pushing CWM Touch to Phone
./linux.sh: 6: ./linux.sh: ./adb: not found
./linux.sh: 7: ./linux.sh: ./adb: not found
./linux.sh: 8: ./linux.sh: ./adb: not found

Rebooting device
./linux.sh: 11: ./linux.sh: ./adb: not found
Waiting for device to reboot
./linux.sh: 13: ./linux.sh: ./adb: not found
: not found 14: ./linux.sh: echo
adding blocking hosts file
./linux.sh: 37: ./linux.sh: Syntax error: Unterminated quoted string

Ummmmm what's next?
 
Is that output from my script? Or the other one?
Yes that is from the cwmbootloop fix


I think I am stabbing in the dark here...I can tell I am rooted, I for a test, installed CWM from Play Store and it is very function less in regards to the spectrum...I haven't done much with it at all. I know SU is installed and functioning because it asked if I wanted my installed CWM to have SU control....I am just uncertain where to start, where to go next, and so on. I have the latest OTA as well which maybe introducing problems although there are several on here that say the contrary.

Help me Obi Wan LOLOLOL
 
Yes that is from the cwmbootloop fix


I think I am stabbing in the dark here...I can tell I am rooted, I for a test, installed CWM from Play Store and it is very function less in regards to the spectrum...I haven't done much with it at all. I know SU is installed and functioning because it asked if I wanted my installed CWM to have SU control....I am just uncertain where to start, where to go next, and so on. I have the latest OTA as well which maybe introducing problems although there are several on here that say the contrary.

Help me Obi Wan LOLOLOL

Now in looking at your "bootloop fix" script...I see where you are sending the CWM img to the phone....methinks there is a hiccup....I have since removed the CWM from the store from SU, cleaned cache via the application manager, then removed data and uninstalled it.

Let me know if I should start over somewhere...
 
Now in looking at your "bootloop fix" script...I see where you are sending the CWM img to the phone....methinks there is a hiccup....I have since removed the CWM from the store from SU, cleaned cache via the application manager, then removed data and uninstalled it.

Let me know if I should start over somewhere...

Alrighty here is the latest attempts and it looks like file permission issues
Code:
~/Downloads/Phone root fix files/Here first$ sudo ./linux.sh 
Pushing Exploit
cannot create /data/local.prop: permission denied

Rebooting device again
: not found 6: ./linux.sh: echo
Waiting for device to reboot

Installing Root Files
mounting phone file systems read-write
Android Debug Bridge version 1.0.29

 -d                            - directs command to the only connected USB device
                                 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 running.
 -s <serial number>            - directs command to the USB device or emulator with
                                 the given serial number. Overrides ANDROID_SERIAL
                                 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 devices.

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] <file> - push this package file to the device and install it
                                 ('-l' means forward-lock the app)
                                 ('-r' means reinstall the app, keeping its data)
                                 ('-s' means install on SD card instead of internal storage)
  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|-nosystem] [<packages...>]
                               - write an archive of the device's data to <file>.
                                 If no -f option is supplied then the data is written
                                 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 default is noshared.)
                                 (-all means to back up all installed applications)
                                 (-system|-nosystem toggles whether -all automatically includes
                                    system applications; the default is to include system apps)
                                 (<packages...> is the list of applications to be backed up.  If
                                    the -all or -shared flags are passed, then the package
                                    list is optional.  Applications explicitly given on the
                                    command line will be included even if -nosystem 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 specified device
  adb remount                  - remounts the /system partition on the device read-write
  adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader 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 the 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 updated.

  - 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 priority over this if given.
  ANDROID_LOG_TAGS             - When used with the logcat option, only these debug tags are printed.
removing etc/install-recovery.sh
This script will root your LG Spectrum VS920
and will install a blocking hosts file
: not found 16: ./linux.sh: echo
not sure if this is necessary, if things dont work,
echo take the "echo " out from the next two commands 
echo -----------
echo ./adb shell "rm /system/etc/install-recovery.sh"
echo removing recovery-from-boot.p
echo ./adb shell "rm /system/recovery-from-boot.p"
echo -----------
echo pushing su package to bin on phone
./adb push su /system/bin/su
echo changing permissions for su
./adb shell "chmod 6755 /system/bin/su"
echo creating a link to su in xbin
./adb shell "ln -s /system/bin/su /system/xbin/su"
echo pushing busybox package to phone
./adb push busybox /system/xbin/busybox
echo changing permissions for busybox
./adb shell "chmod 755 /system/xbin/busybox"
echo installing busybox on phone
./adb shell "/system/xbin/busybox --install /system/xbin"
echo pushing superuser to phone
./adb push Superuser.apk /system/app/Superuser.apk
echo adding blocking hosts file
echo making a backup of the systems host file
failed on '/etc/hosts' - Read-only file system
pushing new hosts file to phone
': Read-only file systemo '/etc/hosts
changing permissions on the hosts file
Unable to chmod /etc/hosts: Read-only file system

Removing Trash
rm failed for /data/local.prop, No such file or directory
rm failed for /data/gpscfg/*, No such file or directory
Unable to chmod /data/: Operation not permitted
: not found 50: ./linux.sh: echo

Finished Rooting!!! 
Restarting phone one more time

Then I go to the CWM Touch Bootloop fix extracted folder which is called Here Second and this is the latest:
Code:
:~/Downloads/Phone root fix files/Here Second$ sudo ./linux.sh 
This script will push the ClockWork Mod Touch Recovery,
insTall a blocking hosts file, and put the CWM Boot loop
fix on your SD card.
: not found 4: ./linux.sh: echo
Pushing CWM Touch to Phone
./linux.sh: 6: ./linux.sh: ./adb: not found
./linux.sh: 7: ./linux.sh: ./adb: not found
./linux.sh: 8: ./linux.sh: ./adb: not found

Rebooting device
./linux.sh: 11: ./linux.sh: ./adb: not found
Waiting for device to reboot
./linux.sh: 13: ./linux.sh: ./adb: not found
: not found 14: ./linux.sh: echo
adding blocking hosts file
./linux.sh: 37: ./linux.sh: Syntax error: Unterminated quoted string

-----tried the install without sudo------

:~/Downloads/Phone root fix files/Here Second$ ./linux.sh 
This script will push the ClockWork Mod Touch Recovery,
insTall a blocking hosts file, and put the CWM Boot loop
fix on your SD card.
./linux.sh: line 4: $'echo\r': command not found
Pushing CWM Touch to Phone
./linux.sh: line 6: ./adb: No such file or directory
./linux.sh: line 7: ./adb: No such file or directory
./linux.sh: line 8: ./adb: No such file or directory

Rebooting device
./linux.sh: line 11: ./adb: No such file or directory
Waiting for device to reboot
./linux.sh: line 13: ./adb: No such file or directory
./linux.sh: line 14: $'echo\r': command not found
adding blocking hosts file
./linux.sh: line 16: unexpected EOF while looking for matching `''
./linux.sh: line 37: syntax error: unexpected end of file
 
let me ask a couple of questions, since I used this script to root my phone and it worked then...

you are:
1. have already gone to menu_.settings->applications->development->usb debugging is checked?
2. plugging your phone in with an USB cable to your computer
3. changing your phone to usb connected ->internet connection ->ethernet?
4. then running these commands?

what happens if you type " ./adb devices "

hmm...
I just bought a new HDD for my laptop and have not installed much beyond linux mint on it so far... getting this when I run ./adb devices (same with sudo, which you should not need)


$ ./adb devices
List of devices attached
???????????? no permissions

I'll try installing the Android SDK tomorrow and see if that fixes it... I'll also try booting my old HDD and see if works there.
 
let me ask a couple of questions, since I used this script to root my phone and it worked then...

you are:
1. have already gone to menu_.settings->applications->development->usb debugging is checked?
2. plugging your phone in with an USB cable to your computer
3. changing your phone to usb connected ->internet connection ->ethernet?
4. then running these commands?

what happens if you type " ./adb devices "

hmm...
I just bought a new HDD for my laptop and have not installed much beyond linux mint on it so far... getting this when I run ./adb devices (same with sudo, which you should not need)


$ ./adb devices
List of devices attached
???????????? no permissions

I'll try installing the Android SDK tomorrow and see if that fixes it... I'll also try booting my old HDD and see if works there.

1 - 4 yup

will also try the ./adb devices

in a sec

Rich
 
1 - 4 yup

will also try the ./adb devices

in a sec

Rich

Here is what I got:
Code:
~/Downloads/Phone root fix files/Here first$ ./adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached 
????????????    no permissions

Rich
 
hi, thx in advance for any kind help. I'm new to android and thus rooting. I used the 1-click and successfully rooted and installed cwm. i got the paid vers. of titanium backup, froze the bloat, and made a backup of apps with that. believe I also had made a backup with cwm.

now, about 10 days after all this, phone randomly went into cwm loop. that is, i hadn't made any changes, out of nowwhere cwm screen appeared, and phone won't reboot or turn off. i tried both backing up and restoring. backup seemed to work. i believe in backup (perhaps in restore) there was a message about sd card error. fyi, sd card is a 32gb c10 card that has worked totally fine for weeks.
 
hi, thx in advance for any kind help. I'm new to android and thus rooting. I used the 1-click and successfully rooted and installed cwm. i got the paid vers. of titanium backup, froze the bloat, and made a backup of apps with that. believe I also had made a backup with cwm.

now, about 10 days after all this, phone randomly went into cwm loop. that is, i hadn't made any changes, out of nowwhere cwm screen appeared, and phone won't reboot or turn off. i tried both backing up and restoring. backup seemed to work. i believe in backup (perhaps in restore) there was a message about sd card error. fyi, sd card is a 32gb c10 card that has worked totally fine for weeks.

What were you doing just before you booted into cwm? Or was the phone idle and you picked it up already booted into cwm? Is it possible you phone took the v6 update while idle? When you choose the option to reboot system does it loop back jnto cwm or just unresponsive?A little more info could be helpful.
 
What were you doing just before you booted into cwm? Or was the phone idle and you picked it up already booted into cwm? Is it possible you phone took the v6 update while idle? When you choose the option to reboot system does it loop back jnto cwm or just unresponsive?A little more info could be helpful.

I have an identical problem, mine updated in my pocket I think. It loops into cwm after I choose to reboot.
 
I have an identical problem, mine updated in my pocket I think. It loops into cwm after I choose to reboot.

In the 1st post of those thread i believe, there is a link for a zip file to fix cwm bootloop. You'll need to find a way to get that file on your sd card and flash it. use another device to download it, or if you have an sd card reader for your computer( along with an adapter for the micro sd). What rom were you running? If you were running Broken out and still have that zip on your card you can just reflash that also, as that has the boot loop fix built into it.

Edit: I lied its not this thread, its Neph's CWM Touch recovery Thread. anyways here is the link for the zip

http://androidfiles.massivefilehost.com/cwm_touch/cwm_bootloop_fix.zip
 
In the 1st post of those thread i believe, there is a link for a zip file to fix cwm bootloop. You'll need to find a way to get that file on your sd card and flash it. use another device to download it, or if you have an sd card reader for your computer( along with an adapter for the micro sd). What rom were you running? If you were running Broken out and still have that zip on your card you can just reflash that also, as that has the boot loop fix built into it.

Edit: I lied its not this thread, its Neph's CWM Touch recovery Thread. anyways here is the link for the zip

http://androidfiles.massivefilehost.com/cwm_touch/cwm_bootloop_fix.zip

Thanks for all the help, I'm back up and running.
 
What were you doing just before you booted into cwm? Or was the phone idle and you picked it up already booted into cwm? Is it possible you phone took the v6 update while idle? When you choose the option to reboot system does it loop back jnto cwm or just unresponsive?A little more info could be helpful.

Though I assume you're suggestions apply to me as well as CWSchrad83, I'll answer your questions anyway as my case may be different. As described in my first post, I have done anything besides rooting, no ROM on the phone yet. Yes, phone was idle when it booted into cwm, and yes reboot option boots phone back into cwm.

I'll assume your advice applies to me as well, about downloading the same zip file, and getting it on the card. Will the phone automatically detect this utility?
 
Though I assume you're suggestions apply to me as well as CWSchrad83, I'll answer your questions anyway as my case may be different. As described in my first post, I have done anything besides rooting, no ROM on the phone yet. Yes, phone was idle when it booted into cwm, and yes reboot option boots phone back into cwm.

I'll assume your advice applies to me as well, about downloading the same zip file, and getting it on the card. Will the phone automatically detect this utility?

Sounds like your phone took the update, the boot loop fix should fix the issue. Once on your card and the card is back in your phone, navigate to the flash zip option , then find the zip file and flash it. let it do its thing, then reboot
 
picking option 7 makes my phone reboot into a black screen..

Mine is also rebooting to a black screen, can tell it's on but nothing shows up, looks like it installed correctly...


Clockwork Mod Recovery
Press any key to continue . . .
* daemon not running. starting it now *
* daemon started successfully *
Device found.
Pushing CWM to Phone
3705 KB/s (16777216 bytes in 4.421s)
Rebooting device
Waiting for device to reboot
Pushing Exploit
Rebooting device again
Waiting for device to reboot
Installing CWM Recovery
remount succeeded
rm failed for /system/etc/install-recovery.sh, No such file or directory
rm failed for /system/recovery-from-boot.p, No such file or directory
4096+0 records in
4096+0 records out
16777216 bytes transferred in 2.757 secs (6085315 bytes/sec)
Removing Trash
Finished Recovery!!!
Press any key to continue . . .

I was running Broken Out 2.0, used the Revert to v4 Stock, installed the update to v6, rooted it (confirmed by Root Checker Basic and Superuser) but can't get CWM to work. Any ideas?
 
Back
Top Bottom