Yesterday I upgraded to JB, everything was fine until I got the idea how to reset the odin counter with terminal emulator.
I rebooted and then came back the wizard and it was in Russian, if I tried to do it crashed.
The baseband has been lost (although I have recovered)
NOW
If I try to flash jb or any other rom:
--Copyng media file:
E:Failed to mount /efs (Invalid argument)
--Appling multi csc
e: failed to mount /efs (Invalid argument)
e: multi_csc:Can't mount /efs
Click to expand...
Click to collapse
my phone displays the name and imei no problems, the baseband I recovered by flashing the stock rom samsung
I have a backup of EFS folder
(I had done it long ago with root explorer, just that I did not make a binary copy but a tar archive)
but even if you put it back with root explorer disappears and returns a folder with a lot less efs file
Content of my TAR backup of /efs
Il volume nell'unit… D Š Doc - Prog
Numero di serie del volume: 86DA-7FA3
Directory di D:\Administrator\Desktop\efs
14/02/2013 02:15 <DIR> .
14/02/2013 02:15 <DIR> ..
14/02/2013 02:12 <DIR> .files
31/12/2011 16:00 1 .nv_state
14/02/2013 02:12 <DIR> bluetooth
20/11/2012 14:01 6 calibration_data
01/01/2012 01:05 9 cryptprop_applied_result
03/01/2013 17:40 10 cryptprop_lockscreen.lockoutattemptdeadline
03/01/2013 17:52 6 cryptprop_lockscreen.password_type
03/01/2013 16:59 5 cryptprop_lockscreen.patterneverchosen
03/01/2013 17:52 6 cryptprop_lock_pattern_autolock
03/01/2013 16:59 5 cryptprop_lock_pattern_tactile_feedback_enabled
03/01/2013 16:59 5 cryptprop_lock_pattern_visible_pattern
13/01/2013 00:37 5 cryptprop_onetimeboot
01/01/2012 01:06 3 cryptprop_persist.sys.language
04/01/2013 12:46 12 cryptprop_persist.sys.timezone
01/01/2012 01:00 1 cryptprop_rebootMode
13/01/2013 00:37 3 cryptprop_securewipedata
14/02/2013 02:12 <DIR> dmp
01/01/2012 01:01 1 essiv
14/02/2013 02:12 <DIR> FactoryApp
10/08/2012 17:57 0 GUARDFIL
14/02/2013 02:12 <DIR> imei
14/02/2013 02:15 0 lista.txr
31/12/2011 16:00 217 nv.log
31/12/2011 16:00 0 nv_data.bin.md5
14/02/2013 02:12 <DIR> RFHAL
14/02/2013 02:12 <DIR> RFHAL.DEF
14/02/2013 02:12 <DIR> wifi
19 File 295 byte
10 Directory 239.271.510.016 byte disponibili
Click to expand...
Click to collapse
How can i fix it?
UP =(
KiraHack said:
UP =(
Click to expand...
Click to collapse
up
Up
Одг: e: failed to mount /efs (Invalid argument)
KiraHack said:
Up
Click to expand...
Click to collapse
Maybe you should flash it with Odin, but I am not sure. And if somebody know he will already answer you.
Sent from Galaxy S Advance
Try to mount efs partition as rw and ext4 type, then try to extract your backup again
Sent from my GT-I9070 using xda app-developers app
frapeti said:
Try to mount efs partition as rw and ext4 type, then try to extract your backup again
Sent from my GT-I9070 using xda app-developers app
Click to expand...
Click to collapse
The partition can not be mount =(
Related
Hi all,
Can someone tell me what am I doing wrong here ?
[email protected]:~/android-sdk/build$ ls -altr
total 4824
drwxr-xr-x 8 kenny kenny 4096 2010-05-19 02:24 ..
-rw-r--r-- 1 kenny kenny 2621440 2010-05-19 02:41 mtd2.img
-rwxr-xr-x 1 kenny kenny 2310048 2010-05-19 02:54 zImage
drwxr-xr-x 2 kenny kenny 4096 2010-05-19 03:11 .
[email protected]:~/android-sdk/build$ ../tools/unpack-bootimg.pl mtd2.img
kernel written to mtd2.img-kernel.gz
ramdisk written to mtd2.img-ramdisk.cpio.gz
gzip: ../mtd2.img-ramdisk.cpio.gz: decompression OK, trailing garbage ignored
523 blocks
extracted ramdisk contents to directory mtd2.img-ramdisk/
[email protected]:~/android-sdk/build$ mkbootimg --cmdline 'no_console_suspend=1 console=null' --kernel zImage --ramdisk mtd2.img-ramdisk.cpio.gz -o kernel.desire
[email protected]:~/android-sdk/build$ ls -altr
total 9980
drwxr-xr-x 8 kenny kenny 4096 2010-05-19 02:24 ..
-rw-r--r-- 1 kenny kenny 2621440 2010-05-19 02:41 mtd2.img
-rwxr-xr-x 1 kenny kenny 2310048 2010-05-19 02:54 zImage
-rw-r--r-- 1 kenny kenny 342016 2010-05-19 03:11 mtd2.img-ramdisk.cpio.gz
-rw-r--r-- 1 kenny kenny 2277376 2010-05-19 03:11 mtd2.img-kernel.gz
drwxr-xr-x 8 kenny kenny 4096 2010-05-19 03:11 mtd2.img-ramdisk
-rw-r--r-- 1 kenny kenny 2654208 2010-05-19 03:12 kernel.desire
drwxr-xr-x 3 kenny kenny 4096 2010-05-19 03:12 .
[email protected]:~/android-sdk/build$ ../tools/fastboot flash boot kernel.desire
sending 'boot' (2592 KB)... OKAY
writing 'boot'... FAILED (remote: image update error)
[email protected]:~/android-sdk/build$ ../tools/fastboot flash zimage zImage
sending 'zimage' (2255 KB)... OKAY
writing 'zimage'... FAILED (remote: unknown fail)
[email protected]:~/android-sdk/build$ ls -althr kernel.desire
-rw-r--r-- 1 kenny kenny 2.6M 2010-05-19 03:12 kernel.desire
[email protected]:~/android-sdk/build$ ls -althr zImage
-rwxr-xr-x 1 kenny kenny 2.3M 2010-05-19 02:54 zImage
[email protected]:~/android-sdk/build$
Regards,
Kenny N
i think this has something to do with the bad block issue... try using this command to create the boot image
mkbootimg --base 20000000 --cmdline 'no_console_suspend=1 console=null' --kernel zImage --ramdisk ramdisk.gz -o boot.img
Thanks Craig - I will give it a try once I got home. It tooks me ~3 hours to customize and build the HTC Desire's kernel for Nexus One. It would be a waste if I can't actually see it in action
Regards,
Kenny N
tried -- still the same
Regards,
Kenny N
Did you clear cache? No idea how that would make a difference but I wipe cache before each kernel flash.
It failed to do the initial flash. Clearing cache won't help in my case.
Sent from my Nexus One
vnbuddy2002 said:
tried -- still the same
Regards,
Kenny N
Click to expand...
Click to collapse
Hmm... difficult to say... i don't know how to debug fastboot... try it via a recovery zip... and then check out the recovery.log for any errors...
i cant get passed clockword mod after i did a factory reset. i tried to restore decraped and the stock rom. it says restore complete then it loads the phone vibrate then the lg symbol shows up then it goes back to clockworkmod. i tried booting system in advanced restore and regular restore
---------- Post added at 05:25 AM ---------- Previous post was at 05:04 AM ----------
i just remembered that i also deleted all files on my internal memory before i tried to install the new rom. maybe that the problem, if it is, how do i get those files back on my internal memory?
try flashingent to stock rom
what are the steps for that process?
Download the stock root rom I'm development. Place it in external sd.clockworkwod.backup. go to backup and restore and select advamted restore and restore system from the stock rom
Sent from my VS910 4G using Tapatalk
i already did that, i was on revolt 1.3 then i went back to stock because im selling my phone, when i went back to stock, i wiped cache and erase data, went to advanced restore then i selected system, after that the phone said restore complete, but it boots up the lg symbol shows us and the phone goes back to clockworkmod. i also found a note in the clorkwork mod folder saying this, "Starting recovery on Thu Sep 22 04:38:02 2011
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v4.0.0.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/mmcblk0p9 (null)
2 /cache ext3 /dev/block/mmcblk0p6 (null)
3 /data ext3 /dev/block/mmcblk0p13 (null)
4 /recovery emmc /dev/block/mmcblk0p14 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 (null)
6 /system ext3 /dev/block/mmcblk0p12 (null)
7 /sd-ext ext4 /dev/block/mmcblk1p2 (null)
8 /emmc vfat /dev/block/mmcblk0p15 (null)
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GINGERBREAD
ro.build.display.id=full_revolution-eng 2.3.4 GINGERBREAD eng.root.20110613.235937 test-keys
ro.build.version.incremental=eng.root.20110613.235937
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=Tue Jun 14 00:00:02 PDT 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=root
ro.build.host=thinserver
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_revolution
ro.product.device=revolution
ro.product.board=revolution
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=revolution
ro.build.description=full_revolution-eng 2.3.4 GINGERBREAD eng.root.20110613.235937 test-keys
ro.build.fingerprint=Android/full_revolution/revolution:2.3.4/GINGERBREAD/eng.root.20110613.235937:eng/test-keys
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=qcom
ro.revision=0
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
No files found.
No files found.
No files found.
No files found.
-- Installing: /sdcard/update.zip
Finding update package...
I:Update location: /sdcard/update.zip
Opening update package...
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted.
That last post is interesting. But to get out of clockwork you need to flash the exitrecovery.zip found in the stuck in clockwork thread in the dev section.
Sent from my VS910 4G using xda premium
hey, mtmichaelson can u give me the link please
http://forum.xda-developers.com/showthread.php?t=1161537
mtmichaelson said:
That last post is interesting. But to get out of clockwork you need to flash the exitrecovery.zip found in the stuck in clockwork thread in the dev section.
Sent from my VS910 4G using xda premium
Click to expand...
Click to collapse
thanks it worked
---------- Post added at 09:25 PM ---------- Previous post was at 09:24 PM ----------
thanks for the link
---------- Post added at 09:25 PM ---------- Previous post was at 09:25 PM ----------
deftonesmw said:
http://forum.xda-developers.com/showthread.php?t=1161537
Click to expand...
Click to collapse
thanks for the link
{
"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"
}
how to install
download to http://www.4shared.com/file/XIqMjv5jba/v700_rootfsimg.html?
execute Odin
ap click
choice to v700_rootfs.img.tar
start
What does this do? Not really sure based on the information in the post.
Jijonhyuni said:
how to install
download to http://www.4shared.com/file/XIqMjv5jba/v700_rootfsimg.html?
execute Odin
ap click
choice to v700_rootfs.img.tar
start
Click to expand...
Click to collapse
I think it is a root method for Tizen, yet I myself am not quite sure what this actually benefits or achieves at this point.
Are there Tizen apps requiring root or a Tizen ROM I'm not aware of?
Thanks
root would be useful to remove the shutter sound for example...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Jijonhyuni said:
how to install
download to http://www.4shared.com/file/XIqMjv5jba/v700_rootfsimg.html?
execute Odin
ap click
choice to v700_rootfs.img.tar
start
Click to expand...
Click to collapse
Think he lives in Korea. I will ask.
루팅을 하면 혜택은 있나요? Custom rom이나 다른 기능이 추가가능한지?
전 아직까지 앤드로이드사용중인데 Tizen으로 프래쉬를해야하는지 고민중입니다.
혹시 시간 나실때 알려주시겠어요?
감사합니다
Flashing now. I'll report back in a minute or two when I'm done playing around with it, maybe even get a system dump.
---------- Post added at 10:56 PM ---------- Previous post was at 10:33 PM ----------
Okay...I got it working but I can't really do much with it. It's not even letting me change directories through SDB.
Here's a list of partitions for Tizen. Anyone want to be bold and try to make a system dump out of one of these?
Will TWRP work with Tizen? Or should we wait for it to be updated?
Thats the best way to get a backup isnt it?
And will that restore partitions from a backup? I have a backup of my Android setup, wondering if I install TWRP on Tizen will I be able to restore Android? Its a thought, probably a bad one but still....
shutter sound off
TML1504 said:
root would be useful to remove the shutter sound for example...
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
install tizen-sdk
sdb root on
sdb shell mount -o remount,rw /
sdb shell mv /usr/share/sounds/mm-camcorder/ /usr/share/sounds/mm-camcorder_bak/
sdb shell mv /usr/apps/com.samsung.w-camera-app/res/sounds /usr/apps/com.samsung.w-camera-app/res/sounds_bak
헤택이라....
escenkay012 said:
think he lives in korea. I will ask.
루팅을 하면 혜택은 있나요? Custom rom이나 다른 기능이 추가가능한지?
전 아직까지 앤드로이드사용중인데 tizen으로 프래쉬를해야하는지 고민중입니다.
혹시 시간 나실때 알려주시겠어요?
감사합니다
Click to expand...
Click to collapse
저도 지금 이것저것 시도를 해보고있습니다.
일단 카메라 사운드부터요
아직 타이젠이라는 운영체제를 모르다보니 어찌할지 모르겠어요
tizen partition info
blackknightavalon said:
Here's a list of partitions for Tizen. Anyone want to be bold and try to make a system dump out of one of these?
Click to expand...
Click to collapse
tizen partition info
sh-3.2# ls -al /dev/disk/by-partlabel
drwxr-xr-x 2 root root 360 Jun 3 07:32 .
drwxr-xr-x 8 root root 160 Jun 3 07:32 ..
lrwxrwxrwx 1 root root 15 Jun 3 07:32 boot -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Jun 3 07:32 bota0 -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Jun 3 07:32 bota1 -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 15 Jun 3 07:32 csa -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Jun 3 07:32 csc -> ../../mmcblk0p13
lrwxrwxrwx 1 root root 16 Jun 3 07:32 fota -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 16 Jun 3 07:32 module -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Jun 3 07:32 param -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Jun 3 07:32 ramdisk1 -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Jun 3 07:32 ramdisk2 -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 15 Jun 3 07:32 recovery -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Jun 3 07:32 reserved -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 16 Jun 3 07:32 rootfs -> ../../mmcblk0p16
lrwxrwxrwx 1 root root 16 Jun 3 07:32 system -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 16 Jun 3 07:32 system-data -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Jun 3 07:32 user -> ../../mmcblk0p15
Jijonhyuni said:
tizen partition info
sh-3.2# ls -al /dev/disk/by-partlabel
drwxr-xr-x 2 root root 360 Jun 3 07:32 .
drwxr-xr-x 8 root root 160 Jun 3 07:32 ..
lrwxrwxrwx 1 root root 15 Jun 3 07:32 boot -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Jun 3 07:32 bota0 -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 15 Jun 3 07:32 bota1 -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 15 Jun 3 07:32 csa -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Jun 3 07:32 csc -> ../../mmcblk0p13
lrwxrwxrwx 1 root root 16 Jun 3 07:32 fota -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 16 Jun 3 07:32 module -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Jun 3 07:32 param -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Jun 3 07:32 ramdisk1 -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Jun 3 07:32 ramdisk2 -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 15 Jun 3 07:32 recovery -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Jun 3 07:32 reserved -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 16 Jun 3 07:32 rootfs -> ../../mmcblk0p16
lrwxrwxrwx 1 root root 16 Jun 3 07:32 system -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 16 Jun 3 07:32 system-data -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Jun 3 07:32 user -> ../../mmcblk0p15
Click to expand...
Click to collapse
Let the custom ROM building begin!
Jijonhyuni said:
install tizen-sdk
sdb root on
sdb shell mount -o remount,rw /
sdb shell mv /usr/share/sounds/mm-camcorder/ /usr/share/sounds/mm-camcorder_bak/
sdb shell mv /usr/apps/com.samsung.w-camera-app/res/sounds /usr/apps/com.samsung.w-camera-app/res/sounds_bak
Click to expand...
Click to collapse
MY BAD.
Thanks for this Got it working and now deleted the shutter sounds.
NakedFaerie said:
MY BAD.
Thanks for this Got it working and now deleted the shutter sounds.
Click to expand...
Click to collapse
When I type sdb root on it get " Permission denied" ??
Gossieur said:
When I type sdb root on it get " Permission denied" ??
Click to expand...
Click to collapse
Have you rooted it yet?
go to the first post and get the file and root it then try again.
NakedFaerie said:
Have you rooted it yet?
go to the first post and get the file and root it then try again.
Click to expand...
Click to collapse
Donwloading now
escenkay012 said:
Think he lives in Korea. I will ask.
루팅을 하면 혜택은 있나요? Custom rom이나 다른 기능이 추가가능한지?
전 아직까지 앤드로이드사용중인데 Tizen으로 프래쉬를해야하는지 고민중입니다.
혹시 시간 나실때 알려주시겠어요?
감사합니다
Click to expand...
Click to collapse
no...right now
Flash. you get "Improved"Battery
Gossieur said:
Donwloading now
Click to expand...
Click to collapse
Strange ... Odin fails to upload the file ... (succeed 0/ failed 1)
---------- Post added at 12:34 PM ---------- Previous post was at 12:22 PM ----------
NakedFaerie said:
Have you rooted it yet?
go to the first post and get the file and root it then try again.
Click to expand...
Click to collapse
Strange ... downloaded the file but Odin fails to upload the file ... (succeed 0/ failed 1)
---------- Post added at 12:40 PM ---------- Previous post was at 12:34 PM ----------
Gossieur said:
Strange ... Odin fails to upload the file ... (succeed 0/ failed 1)
---------- Post added at 12:34 PM ---------- Previous post was at 12:22 PM ----------
Strange ... downloaded the file but Odin fails to upload the file ... (succeed 0/ failed 1)
Click to expand...
Click to collapse
STUPID ME !! Forgot to put the Gear in download mode ... :crying:
hi Jijonhyuni ,
Rooted gear, turn root mode on in Tizen sdk ,no problem .Thank you.!
My " quest/purpose " is to get/ to put custom ringtones/notifications on Gear ,
(as it has only 3 ringtones etc etc .)
Any suggestions ..how ?? or where to push ringtones to..... " Sounds/ringtones " ?
How ...cmd ?
thanks
willcor said:
hi Jijonhyuni ,
Rooted gear, turn root mode on in Tizen sdk ,no problem .Thank you.!
My " quest/purpose " is to get/ to put custom ringtones/notifications on Gear ,
(as it has only 3 ringtones etc etc .)
Any suggestions ..how ?? or where to push ringtones to ? How ?
thanks
Click to expand...
Click to collapse
I posted how on the Gear 1 Tizen thread.
They are located here /opt/share/settings/
To change them the easy way install the Tizen wearable SDK, run the root lines in SDB then goto the SDK and delete files and copy files over. (Make sure you root the device first or none of this will work)
This is my cheat sheet.
sdb root on
sdb shell mount -o remount,rw /
Ringtones located at:
/opt/share/settings/
Camera shutter at:
/usr/share/sounds/mm-camcorder/
hello guys .. i dont know if this is the right place to post this since this is my first post .. sorry .
my phone has no service .. i think some of the /dev blocks is corrupted .. tried restoring /efc using twrp but no luck .. i tried installing cwm using terminal emulator after downloading a marshmallow rom with a faulty recovery ..
so i want to ask .. does installing a stock rom reset the /dev blocks values ? or is there any other way that i can get my service back ? i searched threads but no luck finding any solution .. any help will be appreciated .. if you need any more info to help me just ask please .. and i tried doing so because i had no access to a pc at that time .. thank you
Can you check in settings>phone and see if your baseband/imei is written?
AutumQueen92 said:
Can you check in settings>phone and see if your baseband/imei is written?
Click to expand...
Click to collapse
Baseband version, imei, network, mobile network type, imei sv, Bluetooth address... All unknown...
Running biftor slimkat v11.0 if that helps
N00b... said:
Baseband version, imei, network, mobile network type, imei sv, Bluetooth address... All unknown...
Running biftor slimkat v11.0 if that helps
Click to expand...
Click to collapse
Ahhh, I see the problem. Your IMEI got erased, I do not have the solution for that sorry. Maybe try googling around?
AutumQueen92 said:
Ahhh, I see the problem. Your IMEI got erased, I do not have the solution for that sorry. Maybe try googling around?
Click to expand...
Click to collapse
No luck... Been searching since I woke up... I have backed up /efs... Restoring it was supposed to do the trick. But it doesn't work... Nothing changes when I restore it... Tried flashing different kk roms but none of them work... Will try to flash stock rom once I get back home... Not in a hurry for a solution since this is not the phone I use everyday... Got a nexus 6p 2 weeks ago
N00b... said:
No luck... Been searching since I woke up... I have backed up /efs... Restoring it was supposed to do the trick. But it doesn't work... Nothing changes when I restore it... Tried flashing different kk roms but none of them work... Will try to flash stock rom once I get back home... Not in a hurry for a solution since this is not the phone I use everyday... Got a nexus 6p 2 weeks ago
Click to expand...
Click to collapse
Have you tried setting the permissions of the folder for the efs backup? the phone will not accept folders placed without the proper permission.
You should change permission of efs backup folder as AutumQueen92 mentioned above.
AutumQueen92 said:
Have you tried setting the permissions of the folder for the efs backup? the phone will not accept folders placed without the proper permission.
Click to expand...
Click to collapse
It already has full permissions rwxrwxrwx
N00b... said:
It already has full permissions rwxrwxrwx
Click to expand...
Click to collapse
I don't think that's the right permission. Try rwx --- --- ? I'm not sure of the actual config but google should find some answers. Other than that, I can't help much.
Edit: I was curious myself since I'm re-using my Note.
Code:
permissions / owners / timestamp / file
-rw-r--r-- root root 1 2010-12-31 16:00 cryptprop_rebootMode
-rw-r--r-- root root 0 2011-07-18 15:16 cryptprop_onetimeboot
-rw-r--r-- root root 3 2011-07-17 11:56 cryptprop_securewipedata
drwxrwxr-x root root 2000-01-01 01:03 .files
-rwx------ radioradio 2097152 2011-07-17 12:29 nv_data.bin
-rw-rw-rw- radio radio 1065 2010-12-31 16:00 nv.log
-rwx------ radio radio 32 2011-07-17 12:29 nv_data.bin.md5
drwx------ system system 2010-12-31 16:01 dmp
-rw-r--r-- system system 9 2010-12-31 16:01 cryptprop_applied_result
drwxrwxr-x radio radio 2011-05-21 04:10 imei
-rw-rw-rw- system system 6 2000-01-01 01:04 calibration_data
-rwx------ radio radio 1048576 2010-12-31 16:00 .nv_core.bak
-rwx------ radio radio 32 2010-12-31 16:00 .nv_core.bak.md5
-rwx------ radio radio 2097152 2010-12-31 16:00 .nv_data.bak
-rwx------ radio radio 32 2010-12-31 16:00 .nv_data.bak.md5
-rw-rw-rw- radio radio 1 2010-12-31 16:00 .nv_state
-rw-r--r-- system system 3 2011-07-17 03:00 cryptprop_persist.sys.language
-rwxrwxr-- radio radio 880 2010-12-31 16:02 redata.bin
-rw-rw-rw- system system 256 2010-12-31 16:00 edk_p
-rw-r--r-- system system 18 2011-07-17 03:00 cryptprop_persist.sys.timezone
-rw-r--r-- system system 6 2011-07-10 18:12 cryptprop_lock_pattern_autolock
-rw-r--r-- system system 6 2011-07-10 18:12 cryptprop_lockscreen.password_type
-rw-r--r-- system system 5 2011-07-09 22:41 cryptprop_lockscreen.patterneverchosen
-rw-r--r-- system system 5 2011-06-19 09:09 cryptprop_lock_pattern_visible_pattern
-rw-r--r-- system system 6 2011-06-05 00:53 cryptprop_lock_pattern_tactile_feedback_enabled
AutumQueen92 said:
I don't think that's the right permission. Try rwx --- --- ? I'm not sure of the actual config but google should find some answers. Other than that, I can't help much.
Edit: I was curious myself since I'm re-using my Note.
Code:
permissions / owners / timestamp / file
-rw-r--r-- root root 1 2010-12-31 16:00 cryptprop_rebootMode
-rw-r--r-- root root 0 2011-07-18 15:16 cryptprop_onetimeboot
-rw-r--r-- root root 3 2011-07-17 11:56 cryptprop_securewipedata
drwxrwxr-x root root 2000-01-01 01:03 .files
-rwx------ radioradio 2097152 2011-07-17 12:29 nv_data.bin
-rw-rw-rw- radio radio 1065 2010-12-31 16:00 nv.log
-rwx------ radio radio 32 2011-07-17 12:29 nv_data.bin.md5
drwx------ system system 2010-12-31 16:01 dmp
-rw-r--r-- system system 9 2010-12-31 16:01 cryptprop_applied_result
drwxrwxr-x radio radio 2011-05-21 04:10 imei
-rw-rw-rw- system system 6 2000-01-01 01:04 calibration_data
-rwx------ radio radio 1048576 2010-12-31 16:00 .nv_core.bak
-rwx------ radio radio 32 2010-12-31 16:00 .nv_core.bak.md5
-rwx------ radio radio 2097152 2010-12-31 16:00 .nv_data.bak
-rwx------ radio radio 32 2010-12-31 16:00 .nv_data.bak.md5
-rw-rw-rw- radio radio 1 2010-12-31 16:00 .nv_state
-rw-r--r-- system system 3 2011-07-17 03:00 cryptprop_persist.sys.language
-rwxrwxr-- radio radio 880 2010-12-31 16:02 redata.bin
-rw-rw-rw- system system 256 2010-12-31 16:00 edk_p
-rw-r--r-- system system 18 2011-07-17 03:00 cryptprop_persist.sys.timezone
-rw-r--r-- system system 6 2011-07-10 18:12 cryptprop_lock_pattern_autolock
-rw-r--r-- system system 6 2011-07-10 18:12 cryptprop_lockscreen.password_type
-rw-r--r-- system system 5 2011-07-09 22:41 cryptprop_lockscreen.patterneverchosen
-rw-r--r-- system system 5 2011-06-19 09:09 cryptprop_lock_pattern_visible_pattern
-rw-r--r-- system system 6 2011-06-05 00:53 cryptprop_lock_pattern_tactile_feedback_enabled
Click to expand...
Click to collapse
My efs folder was corrupted .. Same goes for my dev folder .. Tried the first approach that any sane person would do .. Flash a stock ROM .. After lots of searching I found the n7000xxlso stock ROM and flashed it .. Everything worked like a charm .. Then I installed philz and flashed slimkat again .. Now everything is working
In other ROMs I've edited an XML file in /system/csc to make some changes to the keyboard -- specifically, to display alternate symbols when you press-hold a key. I flashed stock MM tonight and noticed that this folder no longer exists.
I checked the Maximum OvrDriVE MM ROM and it does have this folder with the appropriate file. So what happened to the CSC stuff in stock?
SteveRiley said:
In other ROMs I've edited an XML file in /system/csc to make some changes to the keyboard -- specifically, to display alternate symbols when you press-hold a key. I flashed stock MM tonight and noticed that this folder no longer exists.
I checked the Maximum OvrDriVE MM ROM and it does have this folder with the appropriate file. So what happened to the CSC stuff in stock?
Click to expand...
Click to collapse
which stock firmware you are using?
pvsgh said:
which stock firmware you are using?
Click to expand...
Click to collapse
The one DeeXii posted a couple weeks ago: N910TUVS2EPG2_N910TTMB2EPG2_TMB
http://forum.xda-developers.com/note-4-tmobile/development/stock-n910t-n910tuvu2epe3-6-0-1-t3407018
SteveRiley said:
The one DeeXii posted a couple weeks ago: N910TUVS2EPG2_N910TTMB2EPG2_TMB
http://forum.xda-developers.com/note-4-tmobile/development/stock-n910t-n910tuvu2epe3-6-0-1-t3407018
Click to expand...
Click to collapse
Those are the stock ODIN flashable files. Once you flash it via ODIN you will see CSC folder on your phone under /system directory.
pvsgh said:
Those are the stock ODIN flashable files. Once you flash it via ODIN you will see CSC folder on your phone under /system directory.
Click to expand...
Click to collapse
No CSC folder here.
Code:
[email protected]:/ # [B]ls -al /system[/B]
drwxr-xr-x root root 2016-08-11 23:53 app
drwxr-xr-x root shell 2008-12-31 07:00 bin
-rw-r--r-- root root 8080 2008-12-31 07:00 build.prop
drwxr-xr-x root root 2008-12-31 07:00 cameradata
drwxr-xr-x root root 2016-07-07 07:17 container
drwxr-xr-x root root 2016-08-12 01:00 etc
drwxr-xr-x root root 2008-12-31 07:00 fonts
drwxr-xr-x root root 2016-07-07 07:17 framework
-rw-r--r-- root root 10800 2008-12-31 07:00 kern_sec_info
drwxr-xr-x root root 2016-08-11 23:36 lib
drwx------ root root 1969-12-31 16:00 lost+found
drwxr-xr-x root root 2008-12-31 07:00 media
drwxr-xr-x root root 2016-07-07 07:16 preloadedmdm
drwxr-xr-x root root 2016-08-11 23:52 priv-app
-rw-r--r-- root root 4876860 2008-12-31 07:00 recovery-from-boot.bak
drwxr-xr-x root root 2008-12-31 07:00 saiv
-rw-r--r-- root root 417 2016-07-07 07:36 tima_measurement_info
drwxr-xr-x root root 2008-12-31 07:00 tts
drwxr-xr-x root root 2008-12-31 07:00 usr
drwxr-xr-x root shell 2008-12-31 07:00 vendor
drwxr-xr-x root root 2008-12-31 07:00 voicebargeindata
drwxr-xr-x root root 2008-12-31 07:00 wakeupdata
drwxr-xr-x root shell 2008-12-31 07:00 xbin
And a little bit of searching on /system and /data doesn't reveal anything much:
Code:
[email protected]:/ # [B]find /system -iname '*csc*'[/B]
/system/fonts/CarroisGothicSC-Regular.ttf
/system/lib/libcontrolcsc.so
/system/lib/libsccore_csc.so
/system/priv-app/CSC
/system/priv-app/CSC/CSC.apk
/system/priv-app/CSC/oat/arm/CSC.odex.xz
[email protected]:/ # f[B]ind /data -iname '*csc*'[/B]
/data/data/com.samsung.sec.android.application.csc
/data/data/com.google.android.gms/files/AppDataSearch/main/cur/ds.cscoring
/data/system/cscversion.txt
/data/dalvik-cache/profiles/com.samsung.sec.android.application.csc
/data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex
And this zero-byte file seems odd:
Code:
[email protected]:/ # [B]ls -al /data/system/cscversion.txt[/B]
-rw------- system system 0 2016-08-12 20:03 cscversion.txt
I've flashed the build a couple times now, same results. My procedure:
1. Ensure SuperSU zip is on external SD card
2. Boot TWRP recovery (currently 3.0.2 installed)
3. Wipe every partition except external SD
4. Boot the phone into download mode
5. Odin (3.0.9) the ROM to the phone
6. Odin TWRP back to the phone
7. Boot TWRP recovery
8. Flash SuperSU zip
9. Reboot and let settle for 15 minutes
SteveRiley said:
No CSC folder here.
Code:
[email protected]:/ # [B]ls -al /system[/B]
drwxr-xr-x root root 2016-08-11 23:53 app
drwxr-xr-x root shell 2008-12-31 07:00 bin
-rw-r--r-- root root 8080 2008-12-31 07:00 build.prop
drwxr-xr-x root root 2008-12-31 07:00 cameradata
drwxr-xr-x root root 2016-07-07 07:17 container
drwxr-xr-x root root 2016-08-12 01:00 etc
drwxr-xr-x root root 2008-12-31 07:00 fonts
drwxr-xr-x root root 2016-07-07 07:17 framework
-rw-r--r-- root root 10800 2008-12-31 07:00 kern_sec_info
drwxr-xr-x root root 2016-08-11 23:36 lib
drwx------ root root 1969-12-31 16:00 lost+found
drwxr-xr-x root root 2008-12-31 07:00 media
drwxr-xr-x root root 2016-07-07 07:16 preloadedmdm
drwxr-xr-x root root 2016-08-11 23:52 priv-app
-rw-r--r-- root root 4876860 2008-12-31 07:00 recovery-from-boot.bak
drwxr-xr-x root root 2008-12-31 07:00 saiv
-rw-r--r-- root root 417 2016-07-07 07:36 tima_measurement_info
drwxr-xr-x root root 2008-12-31 07:00 tts
drwxr-xr-x root root 2008-12-31 07:00 usr
drwxr-xr-x root shell 2008-12-31 07:00 vendor
drwxr-xr-x root root 2008-12-31 07:00 voicebargeindata
drwxr-xr-x root root 2008-12-31 07:00 wakeupdata
drwxr-xr-x root shell 2008-12-31 07:00 xbin
And a little bit of searching on /system and /data doesn't reveal anything much:
Code:
[email protected]:/ # [B]find /system -iname '*csc*'[/B]
/system/fonts/CarroisGothicSC-Regular.ttf
/system/lib/libcontrolcsc.so
/system/lib/libsccore_csc.so
/system/priv-app/CSC
/system/priv-app/CSC/CSC.apk
/system/priv-app/CSC/oat/arm/CSC.odex.xz
[email protected]:/ # f[B]ind /data -iname '*csc*'[/B]
/data/data/com.samsung.sec.android.application.csc
/data/data/com.google.android.gms/files/AppDataSearch/main/cur/ds.cscoring
/data/system/cscversion.txt
/data/dalvik-cache/profiles/com.samsung.sec.android.application.csc
/data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex
And this zero-byte file seems odd:
Code:
[email protected]:/ # [B]ls -al /data/system/cscversion.txt[/B]
-rw------- system system 0 2016-08-12 20:03 cscversion.txt
I've flashed the build a couple times now, same results. My procedure:
1. Ensure SuperSU zip is on external SD card
2. Boot TWRP recovery (currently 3.0.2 installed)
3. Wipe every partition except external SD
4. Boot the phone into download mode
5. Odin (3.0.9) the ROM to the phone
6. Odin TWRP back to the phone
7. Boot TWRP recovery
8. Flash SuperSU zip
9. Reboot and let settle for 15 minutes
Click to expand...
Click to collapse
Don't know if it would make any difference but you should be using Odin 3.11.1 with this latest EPG2 firmware. CSC related files reside in cache.img.ext4 , so it is possible that that particular file is not being flashed in your case.
pvsgh said:
Don't know if it would make any difference but you should be using Odin 3.11.1 with this latest EPG2 firmware. CSC related files reside in cache.img.ext4 , so it is possible that that particular file is not being flashed in your case.
Click to expand...
Click to collapse
Hm, you might very well have discovered the cause.
Examining the cache.img.ext4 file on my PC:
Code:
[email protected] ~/junk $ [B]simg2img cache.img.ext4 cache.raw[/B]
[email protected] ~/junk $ [B]sudo mount -t ext4 -o loop cache.raw /mnt[/B]
[email protected] ~/junk $ [B]ls -al /mnt[/B]
total 28
drwxr-xr-x 4 root root 4096 Dec 31 1969 .
drwxr-xr-x 1 root root 122 Dec 24 2015 ..
drwx------ 2 root root 4096 Dec 31 1969 lost+found
drwxrwx--- 2 steve 2001 4096 Jul 7 07:36 recovery
[email protected] ~/junk $ [B]ls -al /mnt/recovery/[/B]
total 82720
drwxrwx--- 2 steve 2001 4096 Jul 7 07:36 .
drwxr-xr-x 4 root root 4096 Dec 31 1969 ..
-rw-r--r-- 1 root root 78 Jul 7 07:36 command
-rw-r--r-- 1 root root 84691365 Jul 7 07:36 sec_csc.zip
[email protected] ~/junk $ [B]unzip -l /mnt/recovery/sec_csc.zip[/B]
Archive: /mnt/recovery/sec_csc.zip
signed by SignApk
Length Date Time Name
--------- ---------- ----- ----
{... many files, including several for system/csc ...}
--------- -------
104784820 113 files
I'm surprised the phone even works!
Hm, experiencing flash write failures. First time was about 15% finished. Second time seems about 95% finished.
Third flash completed. Before rebooting, I flashed TWRP. Then I booted TWRP and installed SuperSU. Booted normally and received the dreaded ddi: mmc_read failed message. Crap. Tried another flashing round, which also completed, and let it boot immediately. The Samsung recovery started (which I have never actually seen before) and ran through an installation cycle of something. After that, the phone booted and once again shows ddi:mmc_read failed. Is this thing kaput now?
----------
EDIT: I power cycled the phone and now it appears to be doing a normal first boot -- I'm staring at the T-Mobile splash and the status light is flickering blue/cyan. Wow!
SteveRiley said:
Third flash completed. Before rebooting, I flashed TWRP. Then I booted TWRP and installed SuperSU. Booted normally and received the dreaded ddi: mmc_read failed message. Crap. Tried another flashing round, which also completed, and let it boot immediately. The Samsung recovery started (which I have never actually seen before) and ran through an installation cycle of something. After that, the phone booted and once again shows ddi:mmc_read failed. Is this thing kaput now?
----------
EDIT: I power cycled the phone and now it appears to be doing a normal first boot -- I'm staring at the T-Mobile splash and the status light is flickering blue/cyan. Wow!
Click to expand...
Click to collapse
Did you use the latest version of ODIN now? Also if the phone looks stuck on T-Mobile logo for longer than 30 mins, then remove the battery from the phone and try to boot again.
pvsgh said:
Did you use the latest version of ODIN now? Also if the phone looks stuck on T-Mobile logo for longer than 30 mins, then remove the battery from the phone and try to boot again.
Click to expand...
Click to collapse
Yep, Odin 3.11.1 worked, but like I wrote before, it took three attempts. Weird.
BTW, not everyone agrees that the version of Odin was the actual problem:
http://forum.xda-developers.com/not...ow-updates-issues-t3415914/page2#post68173468
pvsgh said:
Don't know if it would make any difference but you should be using Odin 3.11.1 with this latest EPG2 firmware. CSC related files reside in cache.img.ext4 , so it is possible that that particular file is not being flashed in your case.
Click to expand...
Click to collapse
Worked like a charm. Now I have wifi calling and secondary characters on my keyboard again!
You'll also notice that Bluetooth tethering is gone. T-Mobile likes to disable that for some reason. I imagine that buried in one of the CSC files is a line you could delete to restore Bluetooth tethering.