Root [CWM][ROOT][GB ONLY] Clockworkmod Recovery for the LG Spectrum 4G

[MrB206]

You're not alone... I've never understood why anyone would pay for the pro version of RM. Other than rom updating and some 'premium' roms, I don't see the benefit... and those features are worthless on a phone like the Spectrum, because all our roms are in the forums. On phones like the DX, GNEX and other highly-dev'd devices, it *might* make some sense... but even when I had a D2 and OG Droid, I could just as easily update manually... for free.

 

[hollywoods14]

i can understand why some people would buy it, just for ease of it being a one click option. But your right doesnt make any sense for a device like ours where its all on the forums and easy as pie to do manually.

 

[IMUcarmen]

one reason to buy may be to support the dev...

I know I've bought more than one app just for that reason. The free version gave me everything I needed in those instances and didn't have ads but I felt it my duty to throw a few dollars the devs way just to show my support for their work. Most, if not all of us blow 5-10 dollars on crap we don't need all the time, and a alot of those times we aren't even satisfied with what we got for it.

At least with these great apps provided to us by many many hours of hard work on account of the developers of apps, and roms, and themes we have the option to pay for it after we try it :]

 

[atomilluminati]

Capitalism at its finest. Koush owns cwm, so of course he'll be the one to most benefit/profit from it. It's unfortunate devs create cwm for devices and then he reaps the rewards, but there's 2 things I always remember:
1- he can't dev every device out there... He has a day job, after all.
2- devs don't generally care about the money or the fame... They dev because they want to hack and explore a device. I think the average Joe needs to consider that when looking at this issue.

Average Joe yes... Understood but I am fluent in this shit and I think it's unfair.... I don't develop but I do know my way around... I helped write the first all in one with Mt... Just to say I could lol I see both sides but I disagree with Koushik

 

[MrB206]

one reason to buy may be to support the dev...

That's exactly why I bought rtb pro over titanium pro.

 

[IMUcarmen]

That's exactly why I bought rtb pro over titanium pro.

I bought both And ultimate backup pro not knowing RTB pro came with it I was a noob then though.

 

[tdm]

@PlayfulGod: Thank you, this is awesome! CWMT and adb. Love it! :thumb:

 

[tdm]

Just did my first backup to play with CM9 and I'm a bit nervous:

/sdcard/clockworkmod/backup/1970-01-02.02.19.02 # ls -l
-rwxrwxrwx 1 root root 10485760 Jan 2 02:19 boot.img
-rwxrwxrwx 1 root root 514 Jan 2 02:27 cache.ext4.dup
-rwxrwxrwx 1 root root 246729 Jan 2 02:27 data.ext4.dup
-rwxrwxrwx 1 root root 296 Jan 2 02:27 nandroid.md5
-rwxrwxrwx 1 root root 16777216 Jan 2 02:19 recovery.img
-rwxrwxrwx 1 root root 219368 Jan 2 02:25 system.ext4.dup

I know dedupe is cool, but come on... 219k cannot possibly hold all of /system. What gives? Do the dedupe files in /sdcard/clockworkmod/blobs hold most of the data? "du" shows that there's about 1gb of space used under blobs.

 

[ortrigger]

I'm trying to root my device with this. I'm not new to flashing or anything and I use Ubuntu. But every time I try to root and install the recovery, I get this error:
Clockwork Mod Recovery
[*] Press enter to install CWM to your phone...
Pushing CWM to Phone
error: insufficient permissions for device
error: insufficient permissions for device
error: insufficient permissions for device
Rebooting device
error: insufficient permissions for device
Waiting for device to reboot

I've tried switching the script around to where it roots first but nothing is working. Any ideas?

 

[tdm]

Just did my first backup to play with CM9 and I'm a bit nervous:

That backup is fscked. I tried to restore and got "Error while restoring /system!".

/tmp/recovery.log says:

Checking MD5 sums...
boot.img: OK
cache.ext4.dup: OK
data.ext4.dup: OK
recovery.img: OK
system.ext4.dup: OK
.android_secure.vfat.dup: OK
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/1970-01-02.02.19.02//system.ext4.dup
Restoring system...
Creating filesystem with parameters:
Size: 1073741824
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 4096
Label:
Blocks: 262144
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/65536 inodes and 8536/262144 blocks
warning: wipe_block_device: Discard failed

system
3rd_party
smartmovie
lib
libMvMMAS.so
... more files ...

setkeycodes
setlogcons
setsid
sha1sum
sha256sum
Error while restoring /system!

Good thing there's adb and I took a tarball of /system and /data for safe keeping. Gonna restore from those now.

Since this new dedupe thing obviously cannot be trusted (well, I can't trust it), is there a way to rebuild CWMT without dedupe and just use the good old tarball method?

 

[tdm]

BTW, after the failed restore, "df" says this:

# df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 399544 48 399496 0% /dev
/dev/block/mmcblk0p27
266072 25308 240764 10% /cache
/dev/block/mmcblk1p1 7952656 2111956 5840700 27% /sdcard
/dev/block/mmcblk0p26
1032088 1032088 0 100% /system

BTW2, the timestamp on the backup is 1/1/1970 -- the clock isn't reading correctly or something.

 

[MrB206]

The timestamp issue is a known one that can't be resolved (afaik).

 

[ortrigger]

I'm trying to root my device with this. I'm not new to flashing or anything and I use Ubuntu. But every time I try to root and install the recovery, I get this error:
Clockwork Mod Recovery
[*] Press enter to install CWM to your phone...
Pushing CWM to Phone
error: insufficient permissions for device
error: insufficient permissions for device
error: insufficient permissions for device
Rebooting device
error: insufficient permissions for device
Waiting for device to reboot

I've tried switching the script around to where it roots first but nothing is working. Any ideas?

Any help? I even tried combining two different scripts and am still coming up with nothing. For some reason, I can't get my terminal to recognize adb commands though either... Maybe I should update my sdk. I'll try that and post back with results. In the meantime, y'all have any other ideas what could cause this?

 

[Neph81]

Try manually using ADB. If you can get in that way, then it's a script issue. Last time I saw this happen thou, it was because the user didn't have ADB set up correctly on their linux box. Once they fixed that, the install script worked fine.

 

[tdm]

Try manually using ADB. If you can get in that way, then it's a script issue. Last time I saw this happen thou, it was because the user didn't have ADB set up correctly on their linux box. Once they fixed that, the install script worked fine.

+1

Also, I never mess with the USB permissions. Instead, I start adb as root:

sudo adb start-server

Then anyone can use adb.

That's just me though.

 

[ortrigger]

turns out my adb wasn't configured right. I'm rooted now. Thanks for the help everyone.

 

[PlayfulGod]

That backup is fscked. I tried to restore and got "Error while restoring /system!".

/tmp/recovery.log says:



Good thing there's adb and I took a tarball of /system and /data for safe keeping. Gonna restore from those now.

Since this new dedupe thing obviously cannot be trusted (well, I can't trust it), is there a way to rebuild CWMT without dedupe and just use the good old tarball method?

Dd is what u used to install cwm in the first place

 

[tdm]

Dd is what u used to install cwm in the first place

Not sure I understand that. Are you suggesting that I use dd to do my own backups instead of using nandroid?

I just want a working, reliable backup and restore...

 

[Neph81]

Not sure I understand that. Are you suggesting that I use dd to do my own backups instead of using nandroid?

I just want a working, reliable backup and restore...

Grab the 6.0.1.1 version of our recovery from here:
ClockworkMod ROM Manager - Recoveries

Install using DD commands.
When in recovery go to "backup and restore" -> "choose backup format" -> and pick "tar" .

Consider everything good to go unless you swap out your SD card as it keeps your choice stored in the clockworkmod directory.

 

[finndo77]

Oh sweet, been avoiding the new CWM because of the de dupe. Now I guess I don't have to.

 

[MicroMod777]

Is AllnOne pkg, on 1st post up to date n failsafe to install cwm recovery?

 

[finndo77]

so I finally pushed this CWM to my Spectrum... then started a backup... then noticed the link to DL 6.0.11 to get the option of .tar for backups.
It took about 5-10 minutes before it told me it was backing up data, now it has been sitting on that for 45 minutes.

at one point a REALLY long file name ending in .so was there on the screen, but it disappeared in about 25 seconds and was overwritten with the "Backing up Data..." line. about 20 minutes maybe earlier) in the 45 minute timeframe that it has been "backing up data..." a new line showed up with a single period.

is my phone actually doing something? or should I just yank the battery and push 6.0.11 to it and try again?

none of the physical buttons have any affect, and the key backlights are and have been off. I'll give it another 20 minutes, if no progress, I'm a gonna yank the sucka!


-----------------
so, it is almost an hour and 40 minutes later (I received 9 pages for work right after I put in that last post) there has been no change on my spectrum.


---------------------
10 hours later...
I pushed 6.0.11 to my spectrum and set it to a tar backup and it is running fine now, already finished backing up the system partition and working on the data.

just a note though, after pushing it over with adb I did an adb reboot recovery and was met with a blank screen and unresponsive phone. the backlight for the display was on, but that was it. a battery pull and the phone booted fine, adb reboot recovery again and all is well.

----------------------
10 minutes later...
all done...
now IK@#JR( QN#U$"TG(U#$%QTUQ#$!!!!!
it looks like CWM reset it's date time...
my new backup is no longer incrementing in time, it has started back over at 1970-01-01 very annoying, as now my backups will be out of order... and of course the file creation date (for all my backups) is jan 1st 1980 on every single CWM backup over the last 6.5 months...

 

[bzr]

Kind of a noob with the Spectrum, have rooted my Eris and Incredible without problems before. One question about including the 6.0.1.1 recovery: Do I need to modify the adb commands to look at that file instead of the default one in the AIO? Should I just drop the 6.0.1.1 into the Files folder or do I need to rename the files?

Thanks,
-bzr

 

[Neph81]

Kind of a noob with the Spectrum, have rooted my Eris and Incredible without problems before. One question about including the 6.0.1.1 recovery: Do I need to modify the adb commands to look at that file instead of the default one in the AIO? Should I just drop the 6.0.1.1 into the Files folder or do I need to rename the files?

Thanks,
-bzr

If you grab the 6.0.1.1 file from koush, just delete the other image and rename 6.0.1.1 to what that file was. Much easier then trying to edit the .bat file.

 

[bzr]

Worked like a charm, no hang ups or anything, I'm able to get up to root in File Explorer.

Now just need to find a good ICS ROM for the Spectrum. Any suggestions on a stable daily driver??

-bzr