[Galaxy S II Original Android Development] en11gma:
hi and glad to see i not alone

um i to scared to do to much. not gonna do 'nv backup' or 'nv restore' commands just yet.

i been reading quite a bit and i think you are on the right track

the partitions that i could not back up i think are the ones you mentioned

keep in mind about what i said about having to try and keep backing it up by unchecking some of those partitions when you look at this screenshot

http://i.imgur.com/brjbiiD.png

what we are looking at in that picture are the extractions of my official stock odin file (android 4.4.2) and a twrp backup right before i did the efs pro bakup also in that pic (lower right)

im not sure what to trust in there

i did a file compare of aboot with winhex of efs pro and nab and it says files are the same but different sizes

it looks like efs pro is adding quite a bit of nothing which might be normal but i not sure

im trying to figure out if i can even trust the backups (size and content) and then to make sure if i did restore it went into the correct locations

my /efs looks good (compared to an /efs i had made a copy of with es file manger) previous to all this mess)

you can forget about this dev helping

i should have known not to trust this app as it messed up a previous device i had)

i even tried to help the dev by letting him basically use my device as a test bed) and he wouldnt do a thing.

i cant remember what device it was or even if it was the same nick i using now (i dont think it was)

i swear i think he is out to break our cdma devices

it should clearly state

DONT USE IF YOU HAVE A CDMA DEVICE or something along that nature.

how can making a nv backup destroy our $700 devices?

the dev is well aware of what is going on and he is not a noob

he knows this app through and through and knows what it does to some cdma devices

anyhow me and you should hook up and chat on freenode (irc)

im in #cyanogenmod and #twrp and #koush all the time

Koush is the maker of CWMR and im good in TWRP

if you ask questions there be careful how you word them as they are usually geared towards those apps but sometimes you get good info

i talked to bigbiff in #twrp and he thinks our emmc is messed up and i offered to donate to him and he said he wouldnt touch it

lol

anyhow i was looking at this info here

root@hlteusc:/ # ls -la

ls -la

drwxr-xr-x root root 1969-12-31 18:07 acct

drwxrwx--x system cache 2012-12-31 18:00 cache

-rwxr-x--- root root 284276 1969-12-31 18:00 charger

dr-x------ root root 1969-12-31 18:07 config

lrwxrwxrwx root root 1969-12-31 18:07 d -> /sys/kernel/debug

drwxrwx--x system system 2012-12-31 18:00 data

-rw-r--r-- root root 136 1969-12-31 18:00 default.prop

drwxr-xr-x root root 2012-12-31 18:03 dev

drwxrwx--x system radio 2014-03-18 18:55 efs

lrwxrwxrwx root root 1969-12-31 18:07 etc -> /system/etc

lrwxrwxrwx root root 1969-12-31 18:07 extSdCard -> /storage/sdcard1

lrwxrwxrwx root root 1969-12-31 18:07 external_sd -> /storage/sdcard1

-rw-r--r-- root root 10863 1969-12-31 18:00 file_contexts

dr-xr-x--- system system 1969-12-31 18:07 firmware

dr-xr-x--- system system 1969-12-31 18:07 firmware-modem

-rw-r----- root root 1546 1969-12-31 18:00 fstab.qcom

-rwxr-x--- root root 187952 1969-12-31 18:00 init

-rwxr-x--- root root 3184 1969-12-31 18:00 init.carrier.rc

-rwxr-x--- root root 6159 1969-12-31 18:00 init.cm.rc

-rwxr-x--- root root 919 1969-12-31 18:00 init.environ.rc

-rwxr-x--- root root 7064 1969-12-31 18:00 init.qcom.class_core.sh

-rwxr-x--- root root 2530 1969-12-31 18:00 init.qcom.class_main.sh

-rwxr-x--- root root 3326 1969-12-31 18:00 init.qcom.early_boot.sh

-rwxr-x--- root root 5451 1969-12-31 18:00 init.qcom.lpm_boot.sh

-rwxr-x--- root root 25740 1969-12-31 18:00 init.qcom.rc

-rwxr-x--- root root 7100 1969-12-31 18:00 init.qcom.sh

-rwxr-x--- root root 3265 1969-12-31 18:00 init.qcom.syspart_fixup.sh

-rwxr-x--- root root 44934 1969-12-31 18:00 init.qcom.usb.rc

-rwxr-x--- root root 6959 1969-12-31 18:00 init.qcom.usb.sh

-rwxr-x--- root root 21243 1969-12-31 18:00 init.rc

-rwxr-x--- root root 2115 1969-12-31 18:00 init.recovery.qcom.rc

-rwxr-x--- root root 2890 1969-12-31 18:00 init.ril.rc

-rwxr-x--- root root 301 1969-12-31 18:00 init.superuser.rc

-rwxr-x--- root root 23806 1969-12-31 18:00 init.target.rc

-rwxr-x--- root root 1795 1969-12-31 18:00 init.trace.rc

-rwxr-x--- root root 3915 1969-12-31 18:00 init.usb.rc

-rw-r--r-- root root 2988 1969-12-31 18:00 lpm.rc

drwxrwxr-x root system 1969-12-31 18:07 mnt

drwxr-xr-x system system 1969-12-31 18:07 persdata

drwxrwx--x system system 1969-12-31 18:09 persist

drwxrwx--x system system 1969-12-31 18:07 preload

dr-xr-xr-x root root 1969-12-31 18:00 proc

-rw-r--r-- root root 2161 1969-12-31 18:00 property_contexts

drwxr-xr-x root root 1969-12-31 18:00 res

drwx------ root root 2014-02-20 18:46 root

drwxr-x--- root root 1969-12-31 18:00 sbin

lrwxrwxrwx root root 1969-12-31 18:07 sdcard -> /storage/emulated/legacy

-rw-r--r-- root root 711 1969-12-31 18:00 seapp_contexts

-rw-r--r-- root root 76956 1969-12-31 18:00 sepolicy

dr-xr-x--- system sdcard_r 1969-12-31 18:07 storage

dr-xr-xr-x root root 1969-12-31 18:07 sys

drwxr-xr-x root root 1969-12-31 18:04 system

lrwxrwxrwx root root 1969-12-31 18:07 tombstones -> /data/tombstones

-rw-r--r-- root root 25599 1969-12-31 18:00 ueventd.qcom.rc

-rw-r--r-- root root 5896 1969-12-31 18:00 ueventd.rc

lrwxrwxrwx root root 1969-12-31 18:07 usbdisk -> /storage/usbdisk

lrwxrwxrwx root root 1969-12-31 18:07 vendor -> /system/vendor

root@hlteusc:/ #

right now im in basically cm11 android 4.4.2 but not official as the device is unsupported as there is no DEV edition with unlocked BL like the device you have :)

you see the dates?

are those supposed to be like that on some of the files?

i can only restore backups that were made with twrp (which i do have a stock android 4.4.2 tw rom that was rooted and twrp cust recovery)

i cant install a fresh odin of the stock official tw android 4.4.2 because it puts me in RUIM/SIM subscription mode and that will basically timeout at the activation screen and reboot

i cant change the mode because we locked down on our RF (not that i know of anyhow) would have to be done from twrp with a command probably before it boots up to the UI

the files dates prob dont mean anything but maybe it does because stuff is disabled that shouldnt be

i dont think im in factory mode because i dont see any yellow overlay when im in TW ui

i have had a problem with that before

i pretty good at researching and know good people too

like i said this dev dont care about the cdma users

he will say he dont have a cdma device to test on or something like that

remember i tried with this guy a year or two ago.

i gonna be on for awhile so hit me up on irc if you need help getting it done let me know and we can message each other on this forum until you get it installed

im betting you have it or know what it is so just message me if you get on one of those channels

you can make a new channel if you want and we can get a couple more people in there so we can talk live and then if we ever make any profress we can report it in the forums

my grammar is horrible but i think good and know my way around linux a bit. i get rusty sometimes because i will run windows for a year and then linux for a month or 2 and then go back to windows but i been doing it for years so i not a noob and know what to search for if i forget a command or what not

DD that file back might be a good idea but i need to make sure i have that partition in the backup and make sure its correct info in it (if possible) and make sure it goes in the right spot too

:)

ttyl