I've seen a lot of stuff using 'dd' but nothing that uses that for backuping the entire phone.
When I connect my phone I see both the external SDcard and the internal and just to be sure to take the correct one I pull the external out,
unless you know by its size, can I use this: (this assumes that /dev/sdb is the internal SDcard)
Code:
dd if=/dev/sdb of=/some/place/phone.image bs=4096 conv=notrunc,noerror
and later use that for a total recovery?
I've done this for lots of my Linux systems even just to backup some partitions (but then sdbN...)
but never on a phone and since it's Linux based....
//B52
Of course you can backup using dd, I suggest though that you do partitions seperately since restoring a single image be problematic if possible since some partitions are hidden and writing to the bootloader partitions is not a good idea incase of problems
Here is a list of the partitions with names.
[email protected]:/sdcard # ls -l /dev/block/platform/dw_mmc/by-name/
lrwxrwxrwx 1 root root 20 May 12 21:24 CACHE -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 May 12 21:24 DATAFS -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 20 May 12 21:24 EFS -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 May 12 21:24 FACTORYFS -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 May 12 21:24 HIDDEN -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 May 12 21:24 KERNEL -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 May 12 21:24 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 12 21:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 12 21:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 12 21:24 UMS -> /dev/block/mmcblk0p11
The ones I suggest backing up are:
EFS this is a must and the most important without it your phone could be unusable if the files become corrupt and you don't have a backup
DATAFS is user data
FACTORYFS is the system partition
HIDDEN if you are on Jelly Bean this adds to and extends the system partition
UMS is your internal sdcard (probably better ways to backup then a dd)
Even if you backup don't restore the SBL partitions since if something goes wrong it will screw your phone and they are not damaged if your phone boots at all if they get damaged you will be paying to get your phone jtaged
One thing though, since this is not under /dev/sdX, is it possible to use dd on these /dev/block/ ?
Never done that before and what is the difference between a block and a device?
Is it possible to restore a damaged device partition (eg. from below list) (eg : /dev/block/mmcblk0p8) using a backup from another working phone ?
lrwxrwxrwx 1 root root 20 May 12 21:24 MODEM -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 May 12 21:24 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 May 12 21:24 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 May 12 21:24 SBL2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 May 12 21:24 UMS -> /dev/block/mmcblk0p11
is the content of the partition different on each s2 phone ?
If we create a backup with following command :
[dd if=/dev/block/mmcblk0p8 of=/sdcard/phonebackup/mmcblk0p8.img bs=4096]
and restore in similar way,is there a risk of bricking the phone ?
Hello devs,
while I was digging into update-binaries (i found out also this little trick) I crashed into that /sbin/sh thing...
I searched over the net but couldn't find any reference to this folder and its contents, so I took the DIY route.
Well, here is the content of that /sbin at CWM5 (GB) Recovery time:
Code:
lrwxrwxrwx 1 root root 7 Jun 23 08:44 [ -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 [[ -> busybox
-rwxr-xr-x 1 root root 142656 Jun 23 08:44 adbd
lrwxrwxrwx 1 root root 7 Jun 23 08:44 ash -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 awk -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 basename -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 bbconfig -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 blkid -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 bunzip2 -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 busybox -> recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 bzcat -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 bzip2 -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 cal -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 cat -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 catv -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 chattr -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 chgrp -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 chmod -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 chown -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 chroot -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 cksum -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 clear -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 cmp -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 cp -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 cpio -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 cut -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 date -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 dc -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 dd -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 dedupe -> recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 depmod -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 devmem -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 df -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 diff -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 dirname -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 dmesg -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 dos2unix -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 du -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 dump_image -> recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 echo -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 edify -> recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 egrep -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 env -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 erase_image -> recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 expand -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 expr -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 false -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 fdisk -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 fgrep -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 find -> busybox
-rwxr-xr-x 1 root root 14795 Jun 23 08:44 fix_permissions
lrwxrwxrwx 1 root root 8 Jun 23 08:44 flash_image -> recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 fold -> busybox
-rwxr-xr-x 1 system system 10660 Aug 7 2012 fota.png
lrwxrwxrwx 1 root root 7 Jun 23 08:44 free -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 freeramdisk -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 fuser -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 getopt -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 grep -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 groups -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 gunzip -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 gzip -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 head -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 hexdump -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 id -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 insmod -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 install -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 kill -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 killall -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 killall5 -> busybox
-rwxr-xr-x 1 root root 409 Jun 23 08:44 killrecovery.sh
lrwxrwxrwx 1 root root 7 Jun 23 08:44 length -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 less -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 ln -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 losetup -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 ls -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 lsattr -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 lsmod -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 lspci -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 lsusb -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 lzcat -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 lzop -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 lzopcat -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 makedevs -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 md5sum -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 mkdir -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 mkfifo -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 mkfs.ext2 -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 mknod -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 mkswap -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 mktemp -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 mkyaffs2image -> recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 modinfo -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 modprobe -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 more -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 mount -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 mountpoint -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 mv -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 nanddump -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 nandroid -> recovery
-rwxr-xr-x 1 root root 216 Jun 23 08:44 nandroid-md5.sh
lrwxrwxrwx 1 root root 7 Jun 23 08:44 nandwrite -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 nice -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 nohup -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 od -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 patch -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 pgrep -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 pidof -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 pkill -> busybox
-rwxr-xr-x 1 root root 11 Jun 23 08:44 postrecoveryboot.sh
lrwxrwxrwx 1 root root 7 Jun 23 08:44 printenv -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 printf -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 ps -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 pstree -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 pwd -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 rdev -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 readlink -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 realpath -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 reboot -> recovery
-rwxr-x--- 1 root root 789784 Jun 23 08:44 recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 renice -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 reset -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 resize -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 rev -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 rm -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 rmdir -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 rmmod -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 run-parts -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 sed -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 seq -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 setconsole -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 setprop -> recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 setserial -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 setsid -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 sh -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 sha1sum -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 sha256sum -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 sha512sum -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 sleep -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 sort -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 split -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 stat -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 strings -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 stty -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 swapoff -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 swapon -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 sync -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 sysctl -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 tac -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 tail -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 tar -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 tee -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 test -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 time -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 top -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 touch -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 tr -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 true -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 ttysize -> busybox
lrwxrwxrwx 1 system system 7 Feb 4 22:00 ueventd -> ../init
lrwxrwxrwx 1 root root 7 Jun 23 08:44 umount -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 uname -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 unexpand -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 uniq -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 unix2dos -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 unlzma -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 unlzop -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 unxz -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 unyaffs -> recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 unzip -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 uptime -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 usleep -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 uudecode -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 uuencode -> busybox
lrwxrwxrwx 1 root root 8 Jun 23 08:44 volume -> recovery
lrwxrwxrwx 1 root root 7 Jun 23 08:44 watch -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 wc -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 which -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 whoami -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 xargs -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 xzcat -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 yes -> busybox
lrwxrwxrwx 1 root root 7 Jun 23 08:44 zcat -> busybox
I can't confirm this busybox in /sbin exists in the stock recovery (it should), but anyway who doesn't have CWM these days?
Bye
saw some rom require TZ/RPM? what are they ?
optimusv45 said:
saw some rom require TZ/RPM? what are they ?
Click to expand...
Click to collapse
Those are partitions, TZ=trust zone RPM=something power management. Short of it is they need to be updated to the official jellybean ones for 4.2 or 4.3 to work. If you got 4.1 ota, or used lgnpst with 20j or Teenybin files they will be up to date.
adfurgerson said:
Those are partitions, TZ=trust zone RPM=something power management. Short of it is they need to be updated to the official jellybean ones for 4.2 or 4.3 to work. If you got 4.1 ota, or used lgnpst with 20j or Teenybin files they will be up to date.
Click to expand...
Click to collapse
i never took the ota. phone had the stock ICS rom when i got it. i put eg8 on it ... i guess since i dont have the stock recovery anymore i cant take the ota. do all 4.2 and 4.3 need the TZ and RPM update ?
optimusv45 said:
i never took the ota. phone had the stock ICS rom when i got it. i put eg8 on it ... i guess since i dont have the stock recovery anymore i cant take the ota. do all 4.2 and 4.3 need the TZ and RPM update ?
Click to expand...
Click to collapse
All of the current Roms require it, the earliest cfx and possibly cm10.1 could run without it. I wouldn't recommend those as daily drivers compared to what's availible now.
optimusv45 said:
i never took the ota. phone had the stock ICS rom when i got it. i put eg8 on it ... i guess since i dont have the stock recovery anymore i cant take the ota. do all 4.2 and 4.3 need the TZ and RPM update ?
Click to expand...
Click to collapse
My cm-10.2 does not, as well as dvhexer's alternative cm-10.2. I can throw up a flashable zip if you'd like also or just use lgnpst and a teenybin,
Sent from my Nexus 7 using xda app-developers app
Shelnutt2 said:
My cm-10.2 does not, as well as dvhexer's alternative cm-10.2. I can throw up a flashable zip if you'd like also or just use lgnpst and a teenybin,
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you for catching my mistake @Shelnutt2. So I am clear, those can be flashed because they use LG based kernel? Also if you are saying you could make a zip to update partitions, that would be an awesome thing to have.
Shelnutt2 said:
My cm-10.2 does not, as well as dvhexer's alternative cm-10.2. I can throw up a flashable zip if you'd like also or just use lgnpst and a teenybin,
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Flashable zip would be awesome. I looked at the lgnpst thing a bit , it reminds me of RUU for my HTC phone. If I could I would rather not go back to 100 % stock and do everything all over again.
Shelnutt2 u mentioned you have cm 10.2 I couldnt find it in the development
optimusv45 said:
Shelnutt2 u mentioned you have cm 10.2 I couldnt find it in the development
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2411406
Shelnutt2 said:
My cm-10.2 does not, as well as dvhexer's alternative cm-10.2. I can throw up a flashable zip if you'd like also or just use lgnpst and a teenybin,
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
shelnutt2, can you put up a flashable zip for the TZ/RPM update ? i hope to have the capability to use all the available roms without having to learn lgnpst and teenybin. thanks.
http://webchat.freenode.net/?channels=lg-optimus-g
Spoke with Shelnutt2 on irc and he needs someone with updated rpm/tz to get md5 sums using adb or terminal emulator, then he can make the flashable zip. I tried but the WiFi I was on on wouldn't stay connected. If anyone wants to help out here is link for irc.
A flash able zip would be awesome, I'm not sure if it would help me or not but I believe my rpm/tz partitions are messed up
Sent from my LG Optimus G using Tapatalk 4
anyone with internet can help ?...
If you use teenybin you don't have to go back to stock
Sent from my Optimus G using Xparent BlueTapatalk 2
pcexpress said:
If you use teenybin you don't have to go back to stock
Sent from my Optimus G using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I understand there is teenybin. Flashable zip is just an easy way for people like me who don't want to learn LGNPST
adfurgerson said:
http://webchat.freenode.net/?channels=lg-optimus-g
Spoke with Shelnutt2 on irc and he needs someone with updated rpm/tz to get md5 sums using adb or terminal emulator, then he can make the flashable zip. I tried but the WiFi I was on on wouldn't stay connected. If anyone wants to help out here is link for irc.
Click to expand...
Click to collapse
I'd be glad to, my adb is my best friend when I keep recompiling and breaking roms, what comands give an md5 of the actual partitions?
or just an md5 of the contents? I'll screw around rq and edit this if it's a no brainer.
random results, if this counts:
Code:
/dev/block/platform/msm_sdcc.1/by-name # ll
ll
drwxr-xr-x 2 root root 740 Sep 15 09:35 ./
drwxr-xr-x 4 root root 800 Sep 15 09:35 ../
lrwxrwxrwx 1 root root 21 Sep 15 09:35 DDR -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 20 Sep 15 09:35 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Sep 15 09:35 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 Sep 15 09:35 cache -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 Sep 15 09:35 drm -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 Sep 15 09:35 eksst -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 Sep 15 09:35 encrypt -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 Sep 15 09:35 factory -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 Sep 15 09:35 fota -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 Sep 15 09:35 fsg -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 Sep 15 09:35 grow -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 Sep 15 09:35 m9kefs1 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 Sep 15 09:35 m9kefs2 -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 Sep 15 09:35 m9kefs3 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 Sep 15 09:35 misc -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 20 Sep 15 09:35 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 Sep 15 09:35 modemst1 -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Sep 15 09:35 modemst2 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 Sep 15 09:35 mpt -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 20 Sep 15 09:35 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Sep 15 09:35 persist -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 Sep 15 09:35 recovery -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 Sep 15 09:35 reserved -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 20 Sep 15 09:35 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 Sep 15 09:35 rpmbak -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 20 Sep 15 09:35 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Sep 15 09:35 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 Sep 15 09:35 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 Sep 15 09:35 sns -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 Sep 15 09:35 ssd -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 Sep 15 09:35 system -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 Sep 15 09:35 tombstones -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 20 Sep 15 09:35 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 Sep 15 09:35 tzbak -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 Sep 15 09:35 userdata -> /dev/block/mmcblk0p24
/dev/block/platform/msm_sdcc.1/by-name # cd rpm
cd rpm
/sbin/sh: cd: can't cd to rpm
/dev/block/platform/msm_sdcc.1/by-name # md5sum rpm
md5sum rpm
b1fa2c29e99349abb7104ea87ee9c0e1 rpm
/dev/block/platform/msm_sdcc.1/by-name # md5sum tz
md5sum tz
9913d95fb8bc67e2942bcd491fd07af3 tz
/dev/block/platform/msm_sdcc.1/by-name #
And just to be sure, cat > both to a file for sanity sake and md5 on windows, same results.
Code:
C:\android\md5sums-1.2>md5sums rpm.img
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\android\md5sums-1.2\]
rpm.img b1fa2c29e99349abb7104ea87ee9c0e1
C:\android\md5sums-1.2>md5sums tz.img
MD5sums 1.2 freeware for Win9x/ME/NT/2000/XP+
Copyright (C) 2001-2005 Jem Berkes - http://www.pc-tools.net/
Type md5sums -h for help
[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\android\md5sums-1.2\]
tz.img 9913d95fb8bc67e2942bcd491fd07af3
C:\android\md5sums-1.2>
files attached:
View attachment rpm.img
View attachment tz.img
In case some of you hadn't noticed, this is a Q&A, Help and Troubleshooting thread...
If you've got nothing constructive to contribute, I suggest you move along and troll somewhere else.
bump
optimusv45 said:
bump
Click to expand...
Click to collapse
If you want to update with lgnpst I will help you do it. It really isn't that hard, if you managed to root your phone you should be capable of doing it. It could even be done in real time on irc channel, we would just need to set a time.
adfurgerson said:
If you want to update with lgnpst I will help you do it. It really isn't that hard, if you managed to root your phone you should be capable of doing it. It could even be done in real time on irc channel, we would just need to set a time.
Click to expand...
Click to collapse
4.4 lured me into updating using teenybins. you were right, its not bad
I've spent so much time on this forum and learned so much that I thought this is best place to go for my last resort. I really need to root this phone. I want to be able to use some rooted apps and especially be able to get more apps on my SD Card. My phone is unlockable (In fact Cricket said all their current phones are) I have no fastboot, no proper recovery mode and not even a bootloader mode. When I type adb reboot bootloader it only reboots the phone. I've looked into flashing a new boot, but I don't completely understand how to make or how to get all the any of the Qualcomm flash tools required files. I'll need help with that if it comes to it. I can't even flash a different models stock, because all LG stock I can find is ARB00 and right now I'm ARB03 it doesn't matter if it's even a higher version stock like Pie or even a it's LG G7 ThinQ unless it's ARB03 or higher I can't flash it and of course I can't downgrade. Which would save me a lot of headaches because the Nougat version at least still has fastboot and is ARB00. Something I can work with.
I am about to go to Walmart and just buy it again, because their version is still Nougat. That's what I'll do if I find no answer here, but I want to give this phone another chance. I read this phone can be rooted with Magisk, but with no recovery and no fastboot unless there's another option I don't know if that's even an option. Is there any way to dd install Magisk? If so please let me know. I've also been told it needs to be manually rooted, but I don't know where to get started doing that. I know it's get the right su files in the right places, and busybox but how do I do that with no root to start with, and being unable to mount the system? Is there a way?
I'm seriously willing to try anything at this point even if it will brick my phone. I have insurance on it that will replace it no matter how much damage I cause it and like I said am willing to re-buy the phone at Walmart which might be the better option since getting it from Cricket will most likely just take me back to where I started with an 8.1 phone that I can't do anything with. I don't care much about custom roms or that sort of thing. There isn't any for this phone anyway. I just want it rooted! please if you can think of anything, anything at all please let me know!
I have Windows 10 and Ubuntu
Also If these will help
Partitions:
HTML:
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 DDR -> /dev/block/mmcblk0p44
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 aboot -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 abootbak -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 apdp -> /dev/block/mmcblk0p41
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 boot -> /dev/block/mmcblk0p46
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 cache -> /dev/block/mmcblk0p58
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 cmnlib -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 cmnlib64 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 cmnlib64bak -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 cmnlibbak -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 devcfg -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 devcfgbak -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 devinfo -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 dpo -> /dev/block/mmcblk0p43
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 drm -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 dsp -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 eksst -> /dev/block/mmcblk0p40
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 encrypt -> /dev/block/mmcblk0p39
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 factory -> /dev/block/mmcblk0p51
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 fota -> /dev/block/mmcblk0p35
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 fsc -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 fsg -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 ftm -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 grow -> /dev/block/mmcblk0p60
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 keymaster -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 keymasterbak -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 keystore -> /dev/block/mmcblk0p37
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 laf -> /dev/block/mmcblk0p47
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 lafbak -> /dev/block/mmcblk0p48
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 mcfg -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 misc -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 modemst1 -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 modemst2 -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 mpt -> /dev/block/mmcblk0p55
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 msadp -> /dev/block/mmcblk0p42
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 persist -> /dev/block/mmcblk0p54
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 persistent -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 raw_resources -> /dev/block/mmcblk0p52
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 raw_resourcesbak -> /dev/block/mmcblk0p53
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 rct -> /dev/block/mmcblk0p38
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 recovery -> /dev/block/mmcblk0p49
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 recoverybak -> /dev/block/mmcblk0p50
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 rpm -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 rpmbak -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 sbl1 -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 sbl1bak -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 sec -> /dev/block/mmcblk0p36
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 sns -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 spare1 -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 spare2 -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 spare3 -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 spare4 -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 spare5 -> /dev/block/mmcblk0p45
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 srtc -> /dev/block/mmcblk0p56
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 ssd -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 system -> /dev/block/mmcblk0p57
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 tz -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2018-01-12 14:32 tzbak -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 2018-01-12 14:32 userdata -> /dev/block/mmcblk0p59
Nothing?
Okay from the lack of any reply I'm guessing there isn't a current way to root this device or nothing anybody knows. So I guess I'll get the Nougat version then, and see if I have better luck with it or wait until I save up enough money for another phone that I can unlock and root. If anybody thinks of anything I'm still willing to try, but I'm getting it's about time to give up and just never buy directly from cricket again.
@sjjtnj
Rooting a phone's Android doesn't depend on its Android version but whether it's bootloader can get unlocked or not what basically prevents rooting Android. Take note that not all OEMs/Carriers allow this.
If phone in question is accessable via ADB then to find this out you run this command sequence
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If 1 is returned then phone's bootloader is unlockable otherwise not.
Thanks!
jwoegerbauer said:
@sjjtnj
Rooting a phone's Android doesn't depend on its Android version but whether it's bootloader can get unlocked or not what basically prevents rooting Android. Take note that not all OEMs/Carriers allow this.
If phone in question is accessable via ADB then to find this out you run this command sequence
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported"
If 1 is returned then phone's bootloader is unlockable otherwise not.
Click to expand...
Click to collapse
Thanks this is gave me some hope! I got a 1 so I guess it is unlockable! I can't use fastboot though. If I can figure a way to enable it maybe I can unlock and root it. The Nougat version still has fastboot enabled so that's why I wanted it, but it would be nice to find a way to unlock this one.
@sjjtnj
It's well known that not all OEMs/Carriers support Fastboot as intended by Google. They think that providing Revovery is enough.
FYI: The phone in question has a Recovery partition - as that's default with all Android devices. You enter Recovery mode this way
Code:
adb devices
adb shell "reboot recovery"
Now once you are in recovery, ADB will work instead of Fastboot.
Anyway:
Have you already tried
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
to unlock phone's bootloader - what requires the USB drivers suitable at 100% to the phone are got installed on your Windows computer?
How-To:
1. Download the Android Fastboot Tool v1.2 from here.
2. Once you have downloaded the file, extract the zip file.
3. When you are done with the extraction you open the tool by clicking on Android Fastboot .exe file as Adminstrator.
Note: Never have tried out this.
jwoegerbauer said:
@sjjtnj
It's well known that not all OEMs/Carriers support Fastboot as intended by Google. They think that providing Revovery is enough.
FYI: The phone in question has a Recovery partition - as that's default with all Android devices. You enter Recovery mode this way
Code:
adb devices
adb shell "reboot recovery"
Now once you are in recovery, ADB will work instead of Fastboot.
Anyway:
Have you already tried
to unlock phone's bootloader - what requires the USB drivers suitable at 100% to the phone are got installed on your Windows computer?
How-To:
1. Download the Android Fastboot Tool v1.2 from here.
2. Once you have downloaded the file, extract the zip file.
3. When you are done with the extraction you open the tool by clicking on Android Fastboot .exe file as Adminstrator.
Note: Never have tried out this.
Click to expand...
Click to collapse
Rebooting recovery gives me the little green guy passed out with a triangle with exclamation mark as a heart and says no command. I clicked the buttons you're supposed to click with that error to get the recovery options, but it just reboots. Sometimes though very randomly I do get to a place to wipe data and reset the phone. So I say the recovery works about .05% of the time. Unfortunately I can't flash new partitions with dd without root so no changing the boot.img or recovery.img like I had hoped either. Thank you! I haven't saw that tool before, I'm on Linux right now, but will download it as soon as I get back on Windows. I'll update after I try it.
Still need to try
jwoegerbauer said:
@sjjtnj
It's well known that not all OEMs/Carriers support Fastboot as intended by Google. They think that providing Revovery is enough.
FYI: The phone in question has a Recovery partition - as that's default with all Android devices. You enter Recovery mode this way
Code:
adb devices
adb shell "reboot recovery"
Now once you are in recovery, ADB will work instead of Fastboot.
Anyway:
Have you already tried
to unlock phone's bootloader - what requires the USB drivers suitable at 100% to the phone are got installed on your Windows computer?
How-To:
1. Download the Android Fastboot Tool v1.2 from here.
2. Once you have downloaded the file, extract the zip file.
3. When you are done with the extraction you open the tool by clicking on Android Fastboot .exe file as Adminstrator.
Note: Never have tried out this.
Click to expand...
Click to collapse
Sorry I haven't got this tried yet. I was trying to set up my Linux when it messed up and I had to restart the process. I'm keeping backups this time, but anyway just finishing that because I had to stop when I got a concussion. On the picture, it says to get in fastboot mode. I can't do that only download mode. So I don't think it will work, but I'll still try. I decided I'm going to rebuy the phone from Walmart that has Nougat and fastboot still enabled. That seems my only hope to unlock a phone and root it. The Nougat version is also ARB00 so I can flash firmware of a variant on that one if I need to as well. I know it sounds crazy to buy the same phone, but it's really all I can afford at this time. I'm saving up money for a better phone though, and my nephew has a really bad phone right now. So I can just give this one to him. He doesn't need root or anything so he'll like it.