help newb root sw version ls670zv9

shnuegums

Member
Feb 21, 2011
22
0
0
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Nicholas>cd c:\android sdk tools\platform-tools

c:\Android SDK Tools\platform-tools>adb push rageagainstthecage-arm5.bin /data/local/tmp/rageagainstthecage
cannot stat 'rageagainstthecage-arm5.bin': No such file or directory

c:\Android SDK Tools\platform-tools>
 
Last edited:
Is there a rageagainstthecage-arm5.bin file in your platform-tools directory?
 
no sir there is not and all the links for the 40 pages i have read thru point me to lg website so i go there down load there software run their little gizzmo for the drivers and thats as far or as clear as any website has been LOL
 
@shnuegums if you just installed the newest version of SDK, then you will need to put the files in the "platform-tools" folder. That can be a bit confusing, but once get the files in the right directory it should be pretty much copy and paste in the command prompt.
 
That is what I was missing for sure wish all the other sites I went to were just as simple. THANKS very much I will keep you updated on this forum if all goes well.

Also is there a particular rom you would recommend that will increase performance and battery life?
 
You really can't go wrong with the ROMs in the sticky posts. They are all good. The gingerbread ROM works, but zefie is still working out some of the bugs. I'm not sure if you can flash v 1.7 of ThundeROM with V9 firmware, so if you don't want to go to VC, then I would suggest nROM, Lego ROM, or if you can get your hands on ThundeROM v 1.6.2.

I have two Optimus S devices. One is running TR 1.6.2 and the other is on Lego ROM.
 
Smooth as silk those were the only files I was missing now its time to play :D

I am just learning root before I start on my evo so this is a great test phone.
 
Just keep in mind that though some root processes may seem the same, they each may have diffrences. Just always read everything 2 times before you start. Then read it all over again as you go along. Never assume you "know" what the next step is. Enjoy root and good luck. Its always a blast with seeing what a cellphone can do.
 
+1 to kronosx1's comment. Make sure you have a reasonable understanding of the process. Have fun.

Swyped from my LS670 using Tapatalk
 
nand backup before flashing

Ok so I went through the steps of rooting and everything finished to what seemed to be a complete root

next I installed the market place superuser app

next installed the titanium backup

finally installed quick boot

---------------------------------------------------------------------------

Ok I quick boot into recovery but I dont get the option to backup/restore

only four options as listed

reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition

so what has gone wrong here? :confused:
 
ok thanks again i thought for a bit i was a complete moron now its just 50/50 till i figure this all out :)
 
I would recommend zefie's custom recovery as it has some additional safeguards.

Swyped from my LS670 using Tapatalk
 
Thunderc custom recovery optimus sprint

after reading and reading and reading again because I dont want a paper weight this is the accumulation of what i did and still upon rebooting into recovery i get the stock????

Microsoft Windows
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

c:\Android SDK Tools\platform-tools>adb devices
List of devices attached
A0000028503CBE device

c:\Android SDK Tools\platform-tools>adb shell
$ su
su
# # mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system

# cat /sdcard/flash_image > /system/bin/flash_image

## chmod 755 /system/bin/flash_image
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system

# #
# cat /sdcard/flash_image > /system/bin/flash_image

# # # mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
#
chmod 755 /system/bin/flash_image
# # mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system

#
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak

# # # flash_image recovery /sdcard/recovery-RA-GNM-thunderc-s-1.1.0.img

# reboot recovery# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system

# # # flash_image recovery /sdcard/recovery-RA-GNM-thunderc-s-1.1.0.img

# #
 
after reading and reading and reading again because I dont want a paper weight this is the accumulation of what i did and still upon rebooting into recovery i get the stock????

Microsoft Windows
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

c:\Android SDK Tools\platform-tools>adb devices
List of devices attached
A0000028503CBE device

c:\Android SDK Tools\platform-tools>adb shell
$ su
su
# # mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system

# cat /sdcard/flash_image > /system/bin/flash_image

## chmod 755 /system/bin/flash_image
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system

# #
# cat /sdcard/flash_image > /system/bin/flash_image

# # # mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
#
chmod 755 /system/bin/flash_image
# # mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system

#
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak

# # # flash_image recovery /sdcard/recovery-RA-GNM-thunderc-s-1.1.0.img

# reboot recovery# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system

# # # flash_image recovery /sdcard/recovery-RA-GNM-thunderc-s-1.1.0.img

# #

Don't copy the '#' when copying the commands. When you typed 'su', the '$' changed to a '#' and this is good. The '#' signs listed in the commands to copy and paste represent the '#' that you got when typing 'su'. Copy and paste everything after the '#' and you'll be on track.
 
Did you unzip the flash image file and the custom recovery file and put them on the root of your SD card?
 
and I have made sure that both files were unzipped and placed on root. still i am only getting the stock
 
Microsoft Windows
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>cd c:\android sdk tools\platform-tools

c:\Android SDK Tools\platform-tools>adb devices
List of devices attached
A0000028503CBE device


c:\Android SDK Tools\platform-tools>adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /sdcard/flash_image > /system/bin/flash_image
cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
failed on '/system/etc/install-recovery.sh' - No such file or directory
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh
failed on '/system/etc/install-recovery.sh' - No such file or directory

#


Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system

cat /sdcard/flash_image > /system/bin/flash_image

chmod 755 /system/bin/flash_image

mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak

mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system

flash_image recovery /sdcard/recovery-RA-GNM-thunderc-s-1.1.0.img

reboot recovery
 

Forum statistics

Threads
957,475
Messages
6,973,217
Members
3,163,826
Latest member
eatmynuts