is there anything i can do to get my fone back up and running atleast?
I too have a bricked lg esteem...when i got the phone, i used oneclickroot/run.bat and rooted very easily, was able to remove bloat apps...but then i got ahead of myself. Since the LG revolution is similar to esteem (so i thought), i tried to install a recovery intended for revolution and bricked my phone. Now stuck in LG boot screen. I am able to go into hard reset mode (vol up + down + power) and confirm reset, only to end up in the LG boot screen again. I tried LGNPST method to install stock rom on esteem, but there is no MS910.dll file and no MS910VZB.bin file to download. I also tried LG support tool and program able to recognize phone and analyze it, but then "software is not supported on this device" and have to exit program. Same thing happens in Recovery phone mode. I am posting this in hopes other will avoid my error in judgment in doing things that were not made for this phone just because the specs are similar, and that someone will be able to help me unbrick my phone. Thank you all ahead of time...awesome posts.
Sorry to burst your bubble, you have no clue. Research before you post, please. Saves you embarrassment.
That's why all the LG Rev guys wanted our files, to MAKE a 2.3 ROM for their phones. Our LG Esteem is a refresh of the LG Revolution and it has 2.3 out of the gate. LG never released 2.3 for the Revolution.
recovery has nadda to do with the OS version
I have a CWM built, but, I'm not sure on the partition sizes like thevistor said. I think I got em right, but not confident in em like I am with mtd.
I also have the esteem src code and working on a custom kernel for it.
Question, has anyone tried overclocking the stock kernel with any oc apps?
from what I can tell from the src it should be able to oc to 1.4 w/o modding. Thus far all I've done is added the needed lines so the cpufreqs broadcast so CM can see em.
I also plan to dig thru the android src and see if may give away any needed info. Mostly looks like patches for vanilla android src.
I may just have to do that. Thanks for the reply.i would say, take it back to metro and tell them after a update was install your phone restarted and thats what happen...
major minor #blocks name
7 0 2111 loop0
7 1 3150 loop1
7 2 4190 loop2
7 3 27059 loop3
179 0 7573504 mmcblk0
179 1 2048 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 7168 mmcblk0p3
179 4 1 mmcblk0p4
179 5 36864 mmcblk0p5
179 6 204800 mmcblk0p6
179 7 16384 mmcblk0p7
179 8 24576 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 16384 mmcblk0p10
179 11 16384 mmcblk0p11
179 12 1007616 mmcblk0p12
179 13 1572864 mmcblk0p13
179 14 16384 mmcblk0p14
179 15 4194304 mmcblk0p15
179 16 32768 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 8192 mmcblk0p18
179 19 8192 mmcblk0p19
179 32 16186368 mmcblk1
179 33 16185344 mmcblk1p1
254 0 2110 dm-0
254 1 3150 dm-1
254 2 4189 dm-2
254 3 27058 dm-3
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,size=58544k,nr_inodes=14636,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,size=58544k,nr_inodes=14636,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,size=58544k,nr_inodes=14636,mode=755,gid=1000 0 0
tmpfs /mnt/extasec tmpfs rw,relatime,size=58544k,nr_inodes=14636,mode=755,gid=1000 0 0
tmpfs /mnt/extobb tmpfs rw,relatime,size=58544k,nr_inodes=14636,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p12 /system ext4 rw,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p6 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p5 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/vold/179:15 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:15 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/179:33 /mnt/sdcard/_ExternalSD vfat rw,dirsync,nosuid,nodev,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/extsecure/extasec vfat rw,dirsync,nosuid,nodev,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/_ExternalSD/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.svox.classic.langpack.eng_gbr_fem-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-1 /mnt/asec/com.teamviewer.teamviewer.market.mobile-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-2 /mnt/asec/nikolay.android.ad-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/dm-3 /mnt/asec/com.occamy.android.motoxmayhem1lite-2 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
# mount mtd partitions
# Mount /system rw first to give the filesystem a chance to save a checkpoint
mount yaffs2 mtd@system /system
#mount yaffs2 mtd@system /system ro remount
mount yaffs2 mtd@userdata /data nosuid nodev
mount yaffs2 mtd@persist /persist nosuid nodev
mount yaffs2 mtd@cache /cache nosuid nodev
mount yaffs2 mtd@persist /persist nosuid nodev
on emmc-fs
# mount mmc partitions
wait /dev/block/mmcblk0p12
chmod 0777 /sbin/resize2fs_static
chmod 0777 /sbin/e2fsck_static
exec /sbin/resize2fs_static /dev/block/mmcblk0p12
exec /sbin/e2fsck_static -y /dev/block/mmcblk0p12
mount ext4 /dev/block/mmcblk0p12 /system ro barrier=1 data=ordered
wait /dev/block/mmcblk0p13
chmod 0777 /system/bin/resize2fs
chmod 0777 /system/bin/e2fsck
exec /system/bin/resize2fs /dev/block/mmcblk0p13
exec /system/bin/e2fsck -y /dev/block/mmcblk0p13
mount ext4 /dev/block/mmcblk0p13 /data nosuid nodev barrier=1 data=ordered noauto_da_alloc
wait /dev/block/mmcblk0p6
exec /system/bin/resize2fs /dev/block/mmcblk0p6
exec /system/bin/e2fsck -y /dev/block/mmcblk0p6
mount ext4 /dev/block/mmcblk0p6 /cache nosuid nodev barrier=1 data=ordered
wait /dev/block/mmcblk0p5
exec /system/bin/resize2fs /dev/block/mmcblk0p5
exec /system/bin/e2fsck -y /dev/block/mmcblk0p5
mount ext4 /dev/block/mmcblk0p5 /persist nosuid nodev barrier=1 data=ordered
# [START] LGE_USE_INTERNAL_FAT
wait /dev/block/mmcblk0p15
exec /system/bin/resize2fs /dev/block/mmcblk0p15
exec /system/bin/e2fsck -y /dev/block/mmcblk0p15
#mount vfat /dev/block/mmcblk0p15 /mnt/sdcard
# [END] LGE_USE_INTERNAL_FAT
Character devices:
1 mem
4 /dev/vc/0
4 tty
5 /dev/tty
5 /dev/console
5 /dev/ptmx
7 vcs
10 misc
13 input
21 sg
29 fb
81 video4linux
86 ch
89 i2c
90 mtd
116 alsa
128 ptm
136 pts
216 rfcomm
234 hdmitx
235 kgsl
236 msm_camera
237 gemini
238 dia
239 ttyGS
240 tty_lldm_LTE
241 ttyLTE
242 ttyHS
243 ttyMSM
244 msm_rotator
245 msm_vidc_enc
246 msm_vidc_dec
247 msm_vidc_reg
248 adsp
249 msm_audio_lpa
250 oncrpc
251 smdpkt
252 smd
253 sdio_al_test
254 rtc
Block devices:
1 ramdisk
259 blkext
7 loop
8 sd
31 mtdblock
65 sd
66 sd
67 sd
68 sd
69 sd
70 sd
71 sd
128 sd
129 sd
130 sd
131 sd
132 sd
133 sd
134 sd
135 sd
179 mmc
253 ramzswap
254 device-mapper
I've seen threads where people use the LG Update tool to recover from infinite boot loops... there's a recovery option in there. If that works then we can feel a little safer playing around.
http://androidforums.com/lg-esteem/429712-lg-esteem-infinte-boot-loop-possible-solution.html
As far as partition information here's what I got:
Code:major minor #blocks name 7 0 2111 loop0 7 1 3150 loop1 7 2 4190 loop2 7 3 27059 loop3 179 0 7573504 mmcblk0 179 1 2048 mmcblk0p1 179 2 2048 mmcblk0p2 179 3 7168 mmcblk0p3 179 4 1 mmcblk0p4 179 5 36864 mmcblk0p5 179 6 204800 mmcblk0p6 179 7 16384 mmcblk0p7 179 8 24576 mmcblk0p8 179 9 8192 mmcblk0p9 179 10 16384 mmcblk0p10 179 11 16384 mmcblk0p11 179 12 1007616 mmcblk0p12 179 13 1572864 mmcblk0p13 179 14 16384 mmcblk0p14 179 15 4194304 mmcblk0p15 179 16 32768 mmcblk0p16 179 17 8192 mmcblk0p17 179 18 8192 mmcblk0p18 179 19 8192 mmcblk0p19 179 32 16186368 mmcblk1 179 33 16185344 mmcblk1p1 254 0 2110 dm-0 254 1 3150 dm-1 254 2 4189 dm-2 254 3 27058 dm-3
For mounts:
Code:rootfs / rootfs ro,relatime 0 0 tmpfs /dev tmpfs rw,relatime,size=58544k,nr_inodes=14636,mode=755 0 0 devpts /dev/pts devpts rw,relatime,mode=600 0 0 proc /proc proc rw,relatime 0 0 sysfs /sys sysfs rw,relatime 0 0 none /acct cgroup rw,relatime,cpuacct 0 0 tmpfs /mnt/asec tmpfs rw,relatime,size=58544k,nr_inodes=14636,mode=755,gid=1000 0 0 tmpfs /mnt/obb tmpfs rw,relatime,size=58544k,nr_inodes=14636,mode=755,gid=1000 0 0 tmpfs /mnt/extasec tmpfs rw,relatime,size=58544k,nr_inodes=14636,mode=755,gid=1000 0 0 tmpfs /mnt/extobb tmpfs rw,relatime,size=58544k,nr_inodes=14636,mode=755,gid=1000 0 0 none /dev/cpuctl cgroup rw,relatime,cpu 0 0 /dev/block/mmcblk0p12 /system ext4 rw,relatime,barrier=1,data=ordered 0 0 /dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered,noauto_da_alloc 0 0 /dev/block/mmcblk0p6 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0 /dev/block/mmcblk0p5 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0 /dev/block/vold/179:15 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 /dev/block/vold/179:15 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0 /dev/block/vold/179:33 /mnt/sdcard/_ExternalSD vfat rw,dirsync,nosuid,nodev,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 /dev/block/vold/179:33 /mnt/extsecure/extasec vfat rw,dirsync,nosuid,nodev,relatime,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 tmpfs /mnt/sdcard/_ExternalSD/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0 /dev/block/dm-0 /mnt/asec/com.svox.classic.langpack.eng_gbr_fem-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 /dev/block/dm-1 /mnt/asec/com.teamviewer.teamviewer.market.mobile-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 /dev/block/dm-2 /mnt/asec/nikolay.android.ad-1 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0 /dev/block/dm-3 /mnt/asec/com.occamy.android.motoxmayhem1lite-2 vfat ro,dirsync,nosuid,nodev,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
Mount scripts found in init.rc
Devices:
Why not just call LG and ask them if they have an update because their current version doesn't work?
The recovery tool only works if your phone never received the update. Mine did. So it wont do anything.[
Since you can access recovery, then it sounds like it has messed up the boot.img. You will have to find the proper fastboot drivers and push the stock boot.img. I've got a copy of the stock boot.img if you need it.
That's because you are trying to update the firmware with that tool. There is a separate option in the tool that says "Recovery Phone", according to LG this is the option you use to recover a bricked phone.
I cant get the tool to even recognize my phone. Howi think the driver that installs from the autorun may conflict with the driver lg has you download with the update/recovery tool. But i cant figure out how to uninstall it.
Can someone explain to me what recovery does for your phone inn depth? I'm still new to all of this. I have my esteem rooted as we speak so i can tell this knowledge is essential for me.
A recovery will allow you to back up your current ROM and also flash a new one.. The backing up and restoring is the most important in case something goes wrong you can restore it to its original state..
Ok thanks alot. Now can someone explain to me how to use the titanium backup app precisely please?
1) Get the paid version...it's worth it! I can't emphasis that enough...just donate and get the license...don't question it...just do it! IT WILL SAVE YOU A TON OF TIME! When I flash a new ROM, I can have it COMPLETELY set up in about 15 minutes...everything installed...homescreen set...etc. Clear enough?
2) Before you backup, go into preferences and change the number of backups that you will keep. Default is 1 backup but I keep the last 3 backups in case you get a bad backup.
3) When you back up...BACKUP all user apps + system data...I'll explain why...
It is better to back up every possible thing on your phone vs. just apps. You can pull pieces of your system data back (like the data from Clock 2.1 so you don't have to set your alarms up all over again). Make sense?
4) When you need to do a batch restore (when using a new ROM most likely)..."Restore missing apps with data" just to avoid conflicts. BE SELECTIVE with what you restore! Meaning, don't restore system apps that have been superseded by a new app from a new ROM. In cases of software version upgrades (Android 2.1 to 2.2), don't restore "Clock 2.1" for example, as it will show you have a backup of that app...but that is a 2.1 app that will not play nice with your 2.2 firmware. Once that is done, you can "restore newer versions of user apps" but that is not always needed. In fact, the only reason you would probably need this would be if the ROM you install was an older ROM.
5) Here's how you restore the NECESSARY system settings (Things like Clock, Email, Home (Stock Home app, ADW, ADW EX, Launcher Pro, etc):
NOTE: Any backups listed in GREEN are close to 100% safe to backup (and usually included things like call logs, BT settings, etc).colored apps are usually safe to restore (apps, games, and various other user installed items are listed in white). Any thing in RED is telling you NOT to restore it! It could cause you to not be able to boot your phone and you would have to restore you system.
***I have had occasions where I restored something listed as GREEN and caused me to FUBAR my system. I suppose that it could be attributed to a bad backup or to incompatible data being transfered between ROMs***
Note: If you back up the way I said...you will backup your home screens via whatever launcher you had installed. So if you were running Launcher Pro and you go to a new ROM and install Launcher Pro again, this will bring all your apps and widgets back...although your widgets will not work, you have to remove each widget's placeholder and add the actual widget back...but at least you don't have to try and remember which icons you put where (the widgets, while not functional when restored, act as place holders so you know where you had them). Sorry...I'm trying not to make this confusing
To restore your POP3 email settings (who wants to set that up manually again??? Not me!): Open Titanium: Go to the "Backup/Restore" tab at the top of the screen > scroll to and select Email 2.1-update1 > a pop up will appear, just hit "Restore" on the most recent backup > it will ask you what you want to restore (probably just "Data Only" for email but some apps will give you the option of Data + App as well...just do Data if the app is installed.
Now your email is set up...easy...quick...done! Do that for your "System" apps and settings (bookmarks, SMS, Call Log, etc). You can use titanium to save yourself a lot of time, you just have to know how to use it.
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.