Database Info

Create Odin flashable rom on Tab 2

I'm working on customizing my rooted tab 2 and then exporting to an Odin flashable ROM (following instructions from (http://forums.androidcentral.com/dr...create-custom-odin-images-backup-restore.html)
The reason for this, rather than using CWM to more easily make a backup, is that I need to flash my customizations onto a BUNCH of tablets, and don't want to go through the process of unlocking the bootloader and installing CWM for each of them.
What I'm wondering is this:
Which partitions should I be copying to build an Odin flashable rom. The instructions I linked say that I need zImage, factoryfs.rfs and recovery.bin - which I'm hoping is the case.
I'm not sure which partitions correspond to the necessary files for creating the flashable ROM. Any ideas?
Here are my partitions by name:
1|[email protected]:/ # ls -al /dev/block/platform/msm_sdcc.1/by-name
lrwxrwxrwx root root 1970-11-16 22:48 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1970-11-16 22:48 backup -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1970-11-16 22:48 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1970-11-16 22:48 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1970-11-16 22:48 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1970-11-16 22:48 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1970-11-16 22:48 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1970-11-16 22:48 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1970-11-16 22:48 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1970-11-16 22:48 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1970-11-16 22:48 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1970-11-16 22:48 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1970-11-16 22:48 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1970-11-16 22:48 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1970-11-16 22:48 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1970-11-16 22:48 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1970-11-16 22:48 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1970-11-16 22:48 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1970-11-16 22:48 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1970-11-16 22:48 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1970-11-16 22:48 system -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1970-11-16 22:48 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1970-11-16 22:48 userdata -> /dev/block/mmcblk0p15
Thanks again for the great thread!

I'm not sure what you're following.
But in my limited experience all you will ever need is a system.img, boot.img and a cache.img to tell the recovery to wipe the data. And a recovery.img is optional. The zImage is the kernel and it is in the boot.img.
Also wrong section.

... and crossposting http://forum.xda-developers.com/showpost.php?p=48143832&postcount=177

Luigi2012SM64DS said:
I'm not sure what you're following.
But in my limited experience all you will ever need is a system.img, boot.img and a cache.img to tell the recovery to wipe the data. And a recovery.img is optional. The zImage is the kernel and it is in the boot.img.
Also wrong section.
Click to expand...
Click to collapse
Cool, thanks for the help. Which section would be better to post this in?
so I pull
boot (/dev/block/mmcblk0p7) to zImage
and
system (/dev/block/mmcblk0p14) to factoryfs.rfs
The instructions I linked to say that cache is optional if I don't want to pull personal data, so I might omit that.
If I don't pull the recovery.img, how does that impact the next tablet I install this on? Does it mean a factory wipe would reset it to its previous image, or is that unrelated.
Thanks again for the help - sorry for the cross-post, I'm pretty new to this entire thing.

Android-Andi said:
... and crossposting http://forum.xda-developers.com/showpost.php?p=48143832&postcount=177
Click to expand...
Click to collapse
Should I delete that one? I figured it was relevant to that thread / people who were interested in rooting that tab, but I guess not posting twice supersedes that. Thanks.

evrkusd said:
Cool, thanks for the help. Which section would be better to post this in?
so I pull
boot (/dev/block/mmcblk0p7) to zImage
and
system (/dev/block/mmcblk0p14) to factoryfs.rfs
The instructions I linked to say that cache is optional if I don't want to pull personal data, so I might omit that.
If I don't pull the recovery.img, how does that impact the next tablet I install this on? Does it mean a factory wipe would reset it to its previous image, or is that unrelated.
Thanks again for the help - sorry for the cross-post, I'm pretty new to this entire thing.
Click to expand...
Click to collapse
The thread has already moved from development to Q and A.
And no, i'm still not understanding. you should pull /system and make it into a system.img
And for the boot.img, I am not really sure how you can pull that from that tab. But I think you can just get a stock kernel boot.img from any ol' stock rom.

Luigi2012SM64DS said:
The thread has already moved from development to Q and A.
And no, i'm still not understanding. you should pull /system and make it into a system.img
And for the boot.img, I am not really sure how you can pull that from that tab. But I think you can just get a stock kernel boot.img from any ol' stock rom.
Click to expand...
Click to collapse
Hm ok. I guess other threads are pointing me to think that I need more than just a system.img.
See here:
http://forum.xda-developers.com/showthread.php?t=960946
or the original link I posted.
If all I need is system (/dev/block/mmcblk0p14) dumped to system.img, that would be easier, but I'm not sure that's all I need. If so, I guess I could pull system.img and tar it and try it out..
Thanks for the advice

evrkusd said:
Hm ok. I guess other threads are pointing me to think that I need more than just a system.img.
See here:
http://forum.xda-developers.com/showthread.php?t=960946
or the original link I posted.
If all I need is system (/dev/block/mmcblk0p14) dumped to system.img, that would be easier, but I'm not sure that's all I need. If so, I guess I could pull system.img and tar it and try it out..
Thanks for the advice
Click to expand...
Click to collapse
That guide is not for tab 2.
You only need a modem.bin if you have the P3100 the gsm tab and not the wifi only.
The zImage is the same as boot.img
The cache is only needed as, again, you need to make it so the data will be wiped to avoid bootloops if coming from custom roms.
And the system is the rom so you will obviously need that.

Luigi2012SM64DS said:
That guide is not for tab 2.
You only need a modem.bin if you have the P3100 the gsm tab and not the wifi only.
The zImage is the same as boot.img
The cache is only needed as, again, you need to make it so the data will be wiped to avoid bootloops if coming from custom roms.
And the system is the rom so you will obviously need that.
Click to expand...
Click to collapse
Ok, thanks. The tab 2 I'm using is the Verizon SCH-I705, btw, so should I include modem.img? It seems like I could just leave the existing modem partition on the device, since I don't want to make any changes there.
Here's my current setup
/boot send to boot.img
dd if=/dev/block/mmcblk0p7 of=/sdcard/boot.img bs=4096
/system send to system.img
dd if=/dev/block/mmcblk0p14 of=/sdcard/system.img bs=4096
/recovery send to recovery.img
dd if=/dev/block/mmcblk0p18 of=/sdcard/recovery.img bs=4096
/cache send to cache.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/cache.img bs=4096
Then I'll roll all 4 of them into a tar package with:
tar -H ustar -c system.img cache.img boot.img recovery.img > package.tar
md5sum -t package.tar >> package.tar
mv package.tar package.tar.md5
and flash via Odin
Does it sound like that will work?
Thanks again for the help

evrkusd said:
Ok, thanks. The tab 2 I'm using is the Verizon SCH-I705, btw, so should I include modem.img? It seems like I could just leave the existing modem partition on the device, since I don't want to make any changes there.
Here's my current setup
/boot send to boot.img
dd if=/dev/block/mmcblk0p7 of=/sdcard/boot.img bs=4096
/system send to system.img
dd if=/dev/block/mmcblk0p14 of=/sdcard/system.img bs=4096
/recovery send to recovery.img
dd if=/dev/block/mmcblk0p18 of=/sdcard/recovery.img bs=4096
/cache send to cache.img
dd if=/dev/block/mmcblk0p17 of=/sdcard/cache.img bs=4096
Then I'll roll all 4 of them into a tar package with:
tar -H ustar -c system.img cache.img boot.img recovery.img > package.tar
md5sum -t package.tar >> package.tar
mv package.tar package.tar.md5
and flash via Odin
Does it sound like that will work?
Thanks again for the help
Click to expand...
Click to collapse
Oh the verizon tab.
Yes you should have the modem.
Don't take the cache from the /cache partition you should make a cache.img from scratch.

Luigi2012SM64DS said:
Oh the verizon tab.
Yes you should have the modem.
Don't take the cache from the /cache partition you should make a cache.img from scratch.
Click to expand...
Click to collapse
Ok, thanks. Am I right in thinking that if the tab already has a working modem (since verizon is working on it), do I need to flash modem.img if I haven't made any changes on the new version?
Also, not sure how to make a cache.img from scratch. I've searched for similar terms on xda and haven't come up with anything.
Thanks again.

Hard Brick, Stuck on Boot logo!!!!

I've been dealing with this problem for a couple of weeks now, I have gathered bits and pieces of information but I've had no luck getting this fixed. I was running a 4.3 release of Omni ROM and everything was running ok till I rebooted into recovery (CWM v6.0.3.6) and it asked me to fix root when I tried to reboot back to android. I did that and the tablet rebooted just fine, however the next morning when I woke up I found it stuck on the Samsung Galaxy Note 10.1 logo. I'm still able to get into recovery and download mode but after installing a few other ROMs through recovery and even returning back to stuck with ODIN, nothing has worked yet. Whenever I install a custom ROM in recovery the installation always completes without errors but once I reboot I can't get past the boot logo. On CWM I'm receiving the following errors: "Error Mounting /data!" and "Error mounting /efs!". On ODIN I have tried to return back to stock with and without a PIT file in hopes of re partitioning everything but still no luck. I have also tried to install a different recovery through CWM and ODIN but even though it always completes successfully, I'm unable to override my old CWM recovery partition.
These are the logs I was able to pull with ADB from Recovery:
Code:
/tmp # cat recovery.log
Starting recovery on Fri Jan 13 08:13:39 2012
framebuffer: fd 4 (1280 x 800)
ClockworkMod Recovery v6.0.3.6
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /efs ext4 /dev/block/mmcblk0p3 (null) 0
2 /boot emmc /dev/block/mmcblk0p5 (null) 0
3 /recovery emmc /dev/block/mmcblk0p6 (null) 0
4 /cache ext4 /dev/block/mmcblk0p8 (null) 0
5 /system ext4 /dev/block/mmcblk0p9 (null) 0
6 /data ext4 /dev/block/mmcblk0p12 (null) -16384
7 /preload ext4 /dev/block/mmcblk0p10 (null) 0
8 /modem emmc /dev/block/mmcblk0p7 (null) 0
9 /sdcard datamedia /dev/null (null) 0
10 /external_sd vfat /dev/block/mmcblk1p1 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
Warning: No file_contexts
Warning: No file_contexts
I:device_recovery_start()
Command: "/sbin/recovery"
ro.boot.debug_level=0x4f4c
ro.boot.emmc_checksum=3
ro.boot.bootloader=N8013UEUCMB3
ro.boot.serialno=41070cd112309f57
ro.serialno=41070cd112309f57
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=N8013UEUCMB3
ro.hardware=smdk4x12
ro.revision=6
ro.emmc=0
ro.boot.emmc=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=JDQ39E
ro.build.display.id=cm_n8013-userdebug 4.2.2 JDQ39E eng.hudson.20130824.094402 test-keys
ro.build.version.incremental=eng.hudson.20130824.094402
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Sat Aug 24 09:44:46 PDT 2013
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=hudson
ro.build.host=koushik-lion
ro.build.tags=test-keys
ro.product.model=GT-N8013
ro.product.brand=samsung
ro.product.name=GT-N8013
ro.product.device=GT-N8013
ro.product.board=smdk4x12
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=exynos4
ro.build.product=GT-N8013
ro.build.description=samsung/p4notewifiue/p4notewifi:4.0.4/IMM76D/N8013UEALH2:user/release-keys
ro.build.fingerprint=samsung/p4noterfxx/p4noterf:4.0.4/IMM76D/N8000XWALG9:user/release-keys
ro.build.characteristics=tablet
ro.cm.device=n8013
dalvik.vm.dexopt-data-only=1
ro.sf.lcd_density=160
ro.lcd_min_brightness=20
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=10.1-20130824-UNOFFICIAL-n8013
ro.modversion=10.1-20130824-UNOFFICIAL-n8013
ro.config.ringtone=Orion.ogg
ro.config.notification_sound=Argon.ogg
ro.config.alarm_alert=Hassium.ogg
ro.carrier=unknown
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
hwui.render_dirty_regions=false
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
adb.recovery=1
init.svc.adbd=running
service.adb.root=1
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p12 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p12 (Invalid argument)
Error mounting /data!
W:failed to mount /dev/block/mmcblk0p3 (Invalid argument)
Error mounting /efs!
/tmp #
along with this other info regarding the partitions on my device:
Code:
CWM Errors:
Error mounting /data!
Error mounting /efs!
~ # find /dev/block -path \*/by-name -exec ls -l {} \;
lrwxrwxrwx 1 root root 20 Jan 13 08:04 BOOT -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 13 08:04 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Jan 13 08:04 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Jan 13 08:04 CACHE -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Jan 13 08:04 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 13 08:04 HIDDEN -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 13 08:04 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 Jan 13 08:04 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 13 08:04 RADIO -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Jan 13 08:04 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 13 08:04 SYSTEM -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 13 08:04 USERDATA -> /dev/block/mmcblk0p12
/etc # ls
fstab mtab recovery.fstab
/etc # cat recovery.fstab
# mount point fstype device
/efs ext4 /dev/block/mmcblk0p3
/boot emmc /dev/block/mmcblk0p5
/recovery emmc /dev/block/mmcblk0p6
/cache ext4 /dev/block/mmcblk0p8
/system ext4 /dev/block/mmcblk0p9
/data ext4 /dev/block/mmcblk0p12 length=-16384
/preload ext4 /dev/block/mmcblk0p10
/modem emmc /dev/block/mmcblk0p7
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1p1
/etc # cat fstab
/dev/block/mmcblk0p8 /cache ext4 rw
/dev/block/mmcblk0p12 /data ext4 rw
/dev/block/mmcblk0p9 /system ext4 rw
/dev/null /sdcard datamedia rw
/dev/block/mmcblk1p1 /external_sd vfat rw
~ # ls
cache fstab.smdk4x12 sbin
data init sdcard
default.prop init.rc sys
dev lpm.rc system
efs preload tmp
etc proc ueventd.goldfish.rc
extSdCard res ueventd.rc
external_sd root ueventd.smdk4x12.rc
~ # cat fstab.smdk4x12
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mmcblk0p3 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait
/dev/block/mmcblk0p9 /system ext4 ro,noatime wait
/dev/block/mmcblk0p8 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait
# data partition must be located at the bottom for supporting device encryption
/dev/block/mmcblk0p12 /data ext4 noatime,nosuid,nodev,discard,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=footer
Any help would be greatly appreciated.
Thanks in advance.

Any ideas? Anyone????

Seems like a EFS problem.
AlexFG said:
I've been dealing with this problem for a couple of weeks now, I have gathered bits and pieces of information but I've had no luck getting this fixed. I was running a 4.3 release of Omni ROM and everything was running ok till I rebooted into recovery (CWM v6.0.3.6) and it asked me to fix root when I tried to reboot back to android. I did that and the tablet rebooted just fine, however the next morning when I woke up I found it stuck on the Samsung Galaxy Note 10.1 logo. I'm still able to get into recovery and download mode but after installing a few other ROMs through recovery and even returning back to stuck with ODIN, nothing has worked yet. Whenever I install a custom ROM in recovery the installation always completes without errors but once I reboot I can't get past the boot logo. On CWM I'm receiving the following errors: "Error Mounting /data!" and "Error mounting /efs!". On ODIN I have tried to return back to stock with and without a PIT file in hopes of re partitioning everything but still no luck. I have also tried to install a different recovery through CWM and ODIN but even though it always completes successfully, I'm unable to override my old CWM recovery partition.
These are the logs I was able to pull with ADB from Recovery:
Code:
/tmp # cat recovery.log
Starting recovery on Fri Jan 13 08:13:39 2012
framebuffer: fd 4 (1280 x 800)
ClockworkMod Recovery v6.0.3.6
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /efs ext4 /dev/block/mmcblk0p3 (null) 0
2 /boot emmc /dev/block/mmcblk0p5 (null) 0
3 /recovery emmc /dev/block/mmcblk0p6 (null) 0
4 /cache ext4 /dev/block/mmcblk0p8 (null) 0
5 /system ext4 /dev/block/mmcblk0p9 (null) 0
6 /data ext4 /dev/block/mmcblk0p12 (null) -16384
7 /preload ext4 /dev/block/mmcblk0p10 (null) 0
8 /modem emmc /dev/block/mmcblk0p7 (null) 0
9 /sdcard datamedia /dev/null (null) 0
10 /external_sd vfat /dev/block/mmcblk1p1 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
Warning: No file_contexts
Warning: No file_contexts
I:device_recovery_start()
Command: "/sbin/recovery"
ro.boot.debug_level=0x4f4c
ro.boot.emmc_checksum=3
ro.boot.bootloader=N8013UEUCMB3
ro.boot.serialno=41070cd112309f57
ro.serialno=41070cd112309f57
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=N8013UEUCMB3
ro.hardware=smdk4x12
ro.revision=6
ro.emmc=0
ro.boot.emmc=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
ro.build.id=JDQ39E
ro.build.display.id=cm_n8013-userdebug 4.2.2 JDQ39E eng.hudson.20130824.094402 test-keys
ro.build.version.incremental=eng.hudson.20130824.094402
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Sat Aug 24 09:44:46 PDT 2013
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=hudson
ro.build.host=koushik-lion
ro.build.tags=test-keys
ro.product.model=GT-N8013
ro.product.brand=samsung
ro.product.name=GT-N8013
ro.product.device=GT-N8013
ro.product.board=smdk4x12
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=exynos4
ro.build.product=GT-N8013
ro.build.description=samsung/p4notewifiue/p4notewifi:4.0.4/IMM76D/N8013UEALH2:user/release-keys
ro.build.fingerprint=samsung/p4noterfxx/p4noterf:4.0.4/IMM76D/N8000XWALG9:user/release-keys
ro.build.characteristics=tablet
ro.cm.device=n8013
dalvik.vm.dexopt-data-only=1
ro.sf.lcd_density=160
ro.lcd_min_brightness=20
ro.rommanager.developerid=cyanogenmod
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.cm.version=10.1-20130824-UNOFFICIAL-n8013
ro.modversion=10.1-20130824-UNOFFICIAL-n8013
ro.config.ringtone=Orion.ogg
ro.config.notification_sound=Argon.ogg
ro.config.alarm_alert=Hassium.ogg
ro.carrier=unknown
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
hwui.render_dirty_regions=false
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=2m
dalvik.vm.heapmaxfree=8m
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
adb.recovery=1
init.svc.adbd=running
service.adb.root=1
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p12 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p12 (Invalid argument)
Error mounting /data!
W:failed to mount /dev/block/mmcblk0p3 (Invalid argument)
Error mounting /efs!
/tmp #
along with this other info regarding the partitions on my device:
Code:
CWM Errors:
Error mounting /data!
Error mounting /efs!
~ # find /dev/block -path \*/by-name -exec ls -l {} \;
lrwxrwxrwx 1 root root 20 Jan 13 08:04 BOOT -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 Jan 13 08:04 BOTA0 -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 Jan 13 08:04 BOTA1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 Jan 13 08:04 CACHE -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 Jan 13 08:04 EFS -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 21 Jan 13 08:04 HIDDEN -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 Jan 13 08:04 OTA -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 20 Jan 13 08:04 PARAM -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 Jan 13 08:04 RADIO -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 20 Jan 13 08:04 RECOVERY -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 Jan 13 08:04 SYSTEM -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 Jan 13 08:04 USERDATA -> /dev/block/mmcblk0p12
/etc # ls
fstab mtab recovery.fstab
/etc # cat recovery.fstab
# mount point fstype device
/efs ext4 /dev/block/mmcblk0p3
/boot emmc /dev/block/mmcblk0p5
/recovery emmc /dev/block/mmcblk0p6
/cache ext4 /dev/block/mmcblk0p8
/system ext4 /dev/block/mmcblk0p9
/data ext4 /dev/block/mmcblk0p12 length=-16384
/preload ext4 /dev/block/mmcblk0p10
/modem emmc /dev/block/mmcblk0p7
/sdcard datamedia /dev/null
/external_sd vfat /dev/block/mmcblk1p1
/etc # cat fstab
/dev/block/mmcblk0p8 /cache ext4 rw
/dev/block/mmcblk0p12 /data ext4 rw
/dev/block/mmcblk0p9 /system ext4 rw
/dev/null /sdcard datamedia rw
/dev/block/mmcblk1p1 /external_sd vfat rw
~ # ls
cache fstab.smdk4x12 sbin
data init sdcard
default.prop init.rc sys
dev lpm.rc system
efs preload tmp
etc proc ueventd.goldfish.rc
extSdCard res ueventd.rc
external_sd root ueventd.smdk4x12.rc
~ # cat fstab.smdk4x12
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mmcblk0p3 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait
/dev/block/mmcblk0p9 /system ext4 ro,noatime wait
/dev/block/mmcblk0p8 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait
# data partition must be located at the bottom for supporting device encryption
/dev/block/mmcblk0p12 /data ext4 noatime,nosuid,nodev,discard,noauto_da_alloc,journal_async_commit,errors=panic wait,check,encryptable=footer
Any help would be greatly appreciated.
Thanks in advance.
Click to expand...
Click to collapse
This guide is for all GT-N80XX tablets.
As I see few days ago, many people have same problem as you. It's seems that your NAND partition corrupted and have EFS problem.
Easiest way (My BOOT LOGO MODDER) which one rewrite partition block 03,04 by new PARAM.BIN file:
Try this long story here: http://forum.xda-developers.com/showthread.php?t=2682626
And user Kavin Zhao use my MODDER and if doesn't work made this: http://forum.xda-developers.com/showthread.php?t=2682004
Everything is about EFS problem or corrupted NAND partition.
I hope your device will be fine! :good:
In my signature you can see my device configuration. So try solve problem and then write if you solved problem or not.
For other people which have (almost) same problem as you, they can try this trick: (easy way)
1. Go to download mode (Hold Power more than 30 sec. for sure it's your device is really OFF and then hold POWER + VOLUME DOWN),
USB cable must NOT be connected!!!
2. RUN Odin 3.07 - 3.09 (important) on your PC, your tablet will show you ...ehm... black screen
(or you will see Download Mode screen according to how much is your NAND broke into your device.
3. Connect your USB cable with your PC where is ODIN software running. You should hear sound from your PC as always,
when you connect some device to USB PC port... I suppose that you have USB drivers for Samsung Galaxy Note 10.1 installed in your PC.
If no, go before step 1. download the drivers and then continue.
4. If everything will be O.K your ODIN software will be green (mean port)
5. You must have ORIGINAL STOCK ROM for your country!!! For example CSC for Czech republic is N8000XEZCMG1 and it's very important use the same CSC for your country or operator (otherwise IMEI lost, WiFi doesn't work).
Link is here:
http://www.sammobile.com/firmwares/2/ On this webpage you will see so called CHECKER, just choose MODEL, PRODUCT CODE, here you can choose your country (and carrier/operator in some country only), then will be automatically filled PDA, CSC, MODEM and then finally click on CHECK FIRMWARE and voila, you'll see DOWNLOAD button.
After that, you can read instruction and there is possibility also to download newest ODIN SOFTWARE (3.09) and after download software and ROM continue to step 2. or you can download STOCK ROM from this site:
http://samsung-updates.com/device/?id=GT-N8013 (As I see for GT-N8013 is only ONE firmware ?) Well, looks like it is!
6. In ODIN UNTICK REBOOT and F.RESET TIME and TICK (mean choose) NAND ERASE ALL.
IT'S VERY DANGEROUS because you reformat all your partition so I hope that you have some Backup file.
But I don't needed any backup and after click on PDA button and choosing the STOCK FIRMWARE and click on START button, my tablet was succesfully flashed.
7. If everything will work good = problem solved. If you will see strange WHITE STRIPES instead BOOT LOGO, get my BOOT LOGO MODDER, which one is in my signature and use it.
Harder way (assumed that you have GT-N8013 and EFS problem, no backup and so on):
(Thanks to tripijb)
1.- Install CWM recovery in your rooted tablet.
2.- Install ADB in your PC to be able to communicate with the tablet via com window. Install busybox as well.
3.- Google a nv_data.bin file till you find one. I found one.
4.- BOOT your Tablet in Recovery mode push both the power and the volume up button (the farthest to the power button). When the First letters appear, release the power button, not the volume up until entering in recovery mode.
5.- Go to your PC, connect the USB cable to your tablet and go to C:\Program Files\Android\android-sdk\platform-tools>
6.- Type adb shell and hit return
7.- if you see # good, you have access to your tablet. Do not type su because does not work. You are root (I assume).
8.- type busybox df -h and check you do not have the efs mounted. In fact it does not even appear.
9.- Try to mount mmcblk0p3 (mount -w -t ext4 /dev/block/mmcblk0p3 /efs ) YES 0p3. I have found a lot of forums saying it is 0p1 but not in the Galaxy Note N8013 as you see in your post.
10.- Of course did not mount!!! That is the error. So we have to....
11.- Now try to make that partition, by typing mke2fs /dev/block/mmcblk0p3
12.- Now try to mount it again by typing mount -w -t ext4 /dev/block/mmcblk0p3 /efs It worked!!
13.- Now you have to keep the downloaded nv_data.bin file in the root of your sdcard, and a text file named factorymode with the letters ON inside.
14.- do busybox ls -ltr and you will see there is a folder called sdcard -> /data/media
15.- create a folder inside the /efs/ folder named FactoryApp
16.- Copy the factorymode from the root of your sdcard to the /efs/FactoryApp folder by typing: busybox cp /data/media/factorymode /efs/FactoryApp
17.- Copy the nv_data.bin from your sdcard to your efs folder by typing: busybox cp /data/media/nv_data.bin /efs
18.- Now change permissions to all those files inside efs with 0744 by typing: busybox chmod 0744 /efs/FactoryApp/factorymode Do it with all!!
19.- Now change owner of the directory efs down with: busybox chown 1001.1001 /efs
11.- in CWM go to advanced and fix permissions.
12.- Boot in recovery mode.
13.- Try to mount efs partition and it works!!! Check with ADB that all your files are there and a lot more.
14.- Reboot the Tablet and the efs is there for good.
If you need some files like a PIT file or BOOT.IMG everything is here: http://www.arizzle.com/android/gt-n8013/
Wish you luck, Peter :fingers-crossed:

Thanks for your tips but I guess my internal memory is fried; I tried all the steps above multiple times but once I reboot the device I'm still unable to get past the samsung logo. None of the changes survive a reboot; I can't even install a new recovery partition. The device is out of warranty maybe I should just sell it on ebay for parts or buy a new motherboard. Even though at this point I'm not even sure if it'd be worth it to spend money repairing it versus buying a new tablet. I'm certain about one thing though, I'm not buying any more Samsung devices; this is the second time I face this issue in less than a year - my old Galaxy Nexus phone had the same problem.

tanker32 said:
This guide is for all GT-N80XX tablets.
As I see few days ago, many people have same problem as you. It's seems that your NAND partition corrupted and have EFS problem.
Easiest way (My BOOT LOGO MODDER) which one rewrite partition block 03,04 by new PARAM.BIN file:
Try this long story here: http://forum.xda-developers.com/showthread.php?t=2682626
And user Kavin Zhao use my MODDER and if doesn't work made this: http://forum.xda-developers.com/showthread.php?t=2682004
Everything is about EFS problem or corrupted NAND partition.
I hope your device will be fine! :good:
In my signature you can see my device configuration. So try solve problem and then write if you solved problem or not.
For other people which have (almost) same problem as you, they can try this trick: (easy way)
1. Go to download mode (Hold Power more than 30 sec. for sure it's your device is really OFF and then hold POWER + VOLUME DOWN),
USB cable must NOT be connected!!!
2. RUN Odin 3.07 - 3.09 (important) on your PC, your tablet will show you ...ehm... black screen
(or you will see Download Mode screen according to how much is your NAND broke into your device.
3. Connect your USB cable with your PC where is ODIN software running. You should hear sound from your PC as always,
when you connect some device to USB PC port... I suppose that you have USB drivers for Samsung Galaxy Note 10.1 installed in your PC.
If no, go before step 1. download the drivers and then continue.
4. If everything will be O.K your ODIN software will be green (mean port)
5. You must have ORIGINAL STOCK ROM for your country!!! For example CSC for Czech republic is N8000XEZCMG1 and it's very important use the same CSC for your country or operator (otherwise IMEI lost, WiFi doesn't work).
Link is here:
http://www.sammobile.com/firmwares/2/ On this webpage you will see so called CHECKER, just choose MODEL, PRODUCT CODE, here you can choose your country (and carrier/operator in some country only), then will be automatically filled PDA, CSC, MODEM and then finally click on CHECK FIRMWARE and voila, you'll see DOWNLOAD button.
After that, you can read instruction and there is possibility also to download newest ODIN SOFTWARE (3.09) and after download software and ROM continue to step 2. or you can download STOCK ROM from this site:
http://samsung-updates.com/device/?id=GT-N8013 (As I see for GT-N8013 is only ONE firmware ?) Well, looks like it is!
6. In ODIN UNTICK REBOOT and F.RESET TIME and TICK (mean choose) NAND ERASE ALL.
IT'S VERY DANGEROUS because you reformat all your partition so I hope that you have some Backup file.
But I don't needed any backup and after click on PDA button and choosing the STOCK FIRMWARE and click on START button, my tablet was succesfully flashed.
7. If everything will work good = problem solved. If you will see strange WHITE STRIPES instead BOOT LOGO, get my BOOT LOGO MODDER, which one is in my signature and use it.
Harder way (assumed that you have GT-N8013 and EFS problem, no backup and so on):
(Thanks to tripijb)
1.- Install CWM recovery in your rooted tablet.
2.- Install ADB in your PC to be able to communicate with the tablet via com window. Install busybox as well.
3.- Google a nv_data.bin file till you find one. I found one.
4.- BOOT your Tablet in Recovery mode push both the power and the volume up button (the farthest to the power button). When the First letters appear, release the power button, not the volume up until entering in recovery mode.
5.- Go to your PC, connect the USB cable to your tablet and go to C:\Program Files\Android\android-sdk\platform-tools>
6.- Type adb shell and hit return
7.- if you see # good, you have access to your tablet. Do not type su because does not work. You are root (I assume).
8.- type busybox df -h and check you do not have the efs mounted. In fact it does not even appear.
9.- Try to mount mmcblk0p3 (mount -w -t ext4 /dev/block/mmcblk0p3 /efs ) YES 0p3. I have found a lot of forums saying it is 0p1 but not in the Galaxy Note N8013 as you see in your post.
10.- Of course did not mount!!! That is the error. So we have to....
11.- Now try to make that partition, by typing mke2fs /dev/block/mmcblk0p3
12.- Now try to mount it again by typing mount -w -t ext4 /dev/block/mmcblk0p3 /efs It worked!!
13.- Now you have to keep the downloaded nv_data.bin file in the root of your sdcard, and a text file named factorymode with the letters ON inside.
14.- do busybox ls -ltr and you will see there is a folder called sdcard -> /data/media
15.- create a folder inside the /efs/ folder named FactoryApp
16.- Copy the factorymode from the root of your sdcard to the /efs/FactoryApp folder by typing: busybox cp /data/media/factorymode /efs/FactoryApp
17.- Copy the nv_data.bin from your sdcard to your efs folder by typing: busybox cp /data/media/nv_data.bin /efs
18.- Now change permissions to all those files inside efs with 0744 by typing: busybox chmod 0744 /efs/FactoryApp/factorymode Do it with all!!
19.- Now change owner of the directory efs down with: busybox chown 1001.1001 /efs
11.- in CWM go to advanced and fix permissions.
12.- Boot in recovery mode.
13.- Try to mount efs partition and it works!!! Check with ADB that all your files are there and a lot more.
14.- Reboot the Tablet and the efs is there for good.
If you need some files like a PIT file or BOOT.IMG everything is here: http://www.arizzle.com/android/gt-n8013/
Wish you luck, Peter :fingers-crossed:
Click to expand...
Click to collapse
But what you think about nand erase if i have kitkat 4.4.2? and what you think that is there anyway to make that boot image mod work for kitkat? is it impossible?

Well
Vihru said:
But what you think about nand erase if i have kitkat 4.4.2? and what you think that is there anyway to make that boot image mod work for kitkat? is it impossible?
Click to expand...
Click to collapse
There is all about Odin or Kies Samsung Rom update. So nand erase all has been break point! That was problem, not the solution! And yes, even if you have KitKat, your hardware is still the sma N8000. So again, yes, everything must work great! I'm the proof

tanker32 said:
11.- Now try to make that partition, by typing mke2fs /dev/block/mmcblk0p3
12.- Now try to mount it again by typing mount -w -t ext4 /dev/block/mmcblk0p3 /efs It worked!!
Click to expand...
Click to collapse
Hi
I have the same issues as OP (my last_log looks very familiar).
The ODIN part fails because when trying to erase NAND it always tells me it fails....So I was happy you suggest a different method :laugh:
Thing is when i try your repair guide i get to run
Code:
mke2fs /dev/block/mmcblk0p3
and receive
Code:
~ # mke2fs /dev/block/mmcblk0p3
mke2fs /dev/block/mmcblk0p3
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
5136 inodes, 20480 blocks
1024 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=20971520
3 block groups
8192 blocks per group, 8192 fragments per group
1712 inodes per group
Superblock backups stored on blocks:
8193
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 34 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
after that when trying to mount i get
Code:
mount -w -t ext4 /dev/block/mmcblk0p3
mount: can't find /dev/block/mmcblk0p3 in /etc/fstab
taking a look at fstab in fact there is no entry:
Code:
cat fstab
/dev/block/mmcblk0p8 /cache ext4 rw
/dev/block/mmcblk0p12 /data ext4 rw
/dev/block/mmcblk0p9 /system ext4 rw
/dev/null /sdcard datamedia rw
/dev/block/mmcblk1p1 /external_sd vfat rw
after that i tried mounting with
Code:
mount -w -t ext4 /dev/block/mmcblk0p3 /efs
but now I get
Code:
mount: mounting /dev/block/mmcblk0p3 on /efs failed: Invalid argument
:crying::crying::crying::crying:
any other suggestions? any help is appreciated....and at least I know i am not the only poor sucker with this kind of problem

tanker32 said:
This guide is for all GT-N80XX tablets.
As I see few days ago, many people have same problem as you. It's seems that your NAND partition corrupted and have EFS problem.
Easiest way (My BOOT LOGO MODDER) which one rewrite partition block 03,04 by new PARAM.BIN file:
Try this long story here: http://forum.xda-developers.com/showthread.php?t=2682626
And user Kavin Zhao use my MODDER and if doesn't work made this: http://forum.xda-developers.com/showthread.php?t=2682004
Everything is about EFS problem or corrupted NAND partition.
I hope your device will be fine! :good:
In my signature you can see my device configuration. So try solve problem and then write if you solved problem or not.
For other people which have (almost) same problem as you, they can try this trick: (easy way)
1. Go to download mode (Hold Power more than 30 sec. for sure it's your device is really OFF and then hold POWER + VOLUME DOWN),
USB cable must NOT be connected!!!
2. RUN Odin 3.07 - 3.09 (important) on your PC, your tablet will show you ...ehm... black screen
(or you will see Download Mode screen according to how much is your NAND broke into your device.
3. Connect your USB cable with your PC where is ODIN software running. You should hear sound from your PC as always,
when you connect some device to USB PC port... I suppose that you have USB drivers for Samsung Galaxy Note 10.1 installed in your PC.
If no, go before step 1. download the drivers and then continue.
4. If everything will be O.K your ODIN software will be green (mean port)
5. You must have ORIGINAL STOCK ROM for your country!!! For example CSC for Czech republic is N8000XEZCMG1 and it's very important use the same CSC for your country or operator (otherwise IMEI lost, WiFi doesn't work).
Link is here:
http://www.sammobile.com/firmwares/2/ On this webpage you will see so called CHECKER, just choose MODEL, PRODUCT CODE, here you can choose your country (and carrier/operator in some country only), then will be automatically filled PDA, CSC, MODEM and then finally click on CHECK FIRMWARE and voila, you'll see DOWNLOAD button.
After that, you can read instruction and there is possibility also to download newest ODIN SOFTWARE (3.09) and after download software and ROM continue to step 2. or you can download STOCK ROM from this site:
http://samsung-updates.com/device/?id=GT-N8013 (As I see for GT-N8013 is only ONE firmware ?) Well, looks like it is!
6. In ODIN UNTICK REBOOT and F.RESET TIME and TICK (mean choose) NAND ERASE ALL.
IT'S VERY DANGEROUS because you reformat all your partition so I hope that you have some Backup file.
But I don't needed any backup and after click on PDA button and choosing the STOCK FIRMWARE and click on START button, my tablet was succesfully flashed.
7. If everything will work good = problem solved. If you will see strange WHITE STRIPES instead BOOT LOGO, get my BOOT LOGO MODDER, which one is in my signature and use it.
Harder way (assumed that you have GT-N8013 and EFS problem, no backup and so on):
(Thanks to tripijb)
1.- Install CWM recovery in your rooted tablet.
2.- Install ADB in your PC to be able to communicate with the tablet via com window. Install busybox as well.
3.- Google a nv_data.bin file till you find one. I found one.
4.- BOOT your Tablet in Recovery mode push both the power and the volume up button (the farthest to the power button). When the First letters appear, release the power button, not the volume up until entering in recovery mode.
5.- Go to your PC, connect the USB cable to your tablet and go to C:\Program Files\Android\android-sdk\platform-tools>
6.- Type adb shell and hit return
7.- if you see # good, you have access to your tablet. Do not type su because does not work. You are root (I assume).
8.- type busybox df -h and check you do not have the efs mounted. In fact it does not even appear.
9.- Try to mount mmcblk0p3 (mount -w -t ext4 /dev/block/mmcblk0p3 /efs ) YES 0p3. I have found a lot of forums saying it is 0p1 but not in the Galaxy Note N8013 as you see in your post.
10.- Of course did not mount!!! That is the error. So we have to....
11.- Now try to make that partition, by typing mke2fs /dev/block/mmcblk0p3
12.- Now try to mount it again by typing mount -w -t ext4 /dev/block/mmcblk0p3 /efs It worked!!
13.- Now you have to keep the downloaded nv_data.bin file in the root of your sdcard, and a text file named factorymode with the letters ON inside.
14.- do busybox ls -ltr and you will see there is a folder called sdcard -> /data/media
15.- create a folder inside the /efs/ folder named FactoryApp
16.- Copy the factorymode from the root of your sdcard to the /efs/FactoryApp folder by typing: busybox cp /data/media/factorymode /efs/FactoryApp
17.- Copy the nv_data.bin from your sdcard to your efs folder by typing: busybox cp /data/media/nv_data.bin /efs
18.- Now change permissions to all those files inside efs with 0744 by typing: busybox chmod 0744 /efs/FactoryApp/factorymode Do it with all!!
19.- Now change owner of the directory efs down with: busybox chown 1001.1001 /efs
11.- in CWM go to advanced and fix permissions.
12.- Boot in recovery mode.
13.- Try to mount efs partition and it works!!! Check with ADB that all your files are there and a lot more.
14.- Reboot the Tablet and the efs is there for good.
If you need some files like a PIT file or BOOT.IMG everything is here: http://www.arizzle.com/android/gt-n8013/
Wish you luck, Peter :fingers-crossed:
Click to expand...
Click to collapse
with nand erase all this is the result
<ID:0/022> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XWALG9_N8000OXXALG7_N8000XXLGA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/022> Odin engine v(ID:3.1005)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Erase...
<ID:0/022>
<ID:0/022> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

ameer3adel said:
with nand erase all this is the result
<ID:0/022> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N8000XWALG9_N8000OXXALG7_N8000XXLGA_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/022> Odin engine v(ID:3.1005)..
<ID:0/022> File analysis..
<ID:0/022> SetupConnection..
<ID:0/022> Initialzation..
<ID:0/022> Erase...
<ID:0/022>
<ID:0/022> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Same Situation encountered. Did you get a solution?

Same here. Anyone find a workaround for this?
Aramis4u said:
Same Situation encountered. Did you get a solution?
Click to expand...
Click to collapse

[MOD] Galaxy core 2 recovery SM G355HN

UPDATE :
CWM recovery : http://forum.xda-developers.com/gal...de-how-to-install-cwm-samsung-galaxy-t2990852
TWRP: http://forum.xda-developers.com/galaxy-core/development/samsung-galaxy-core-2-sm-g355h-m-t2998094
-----------------------------------------------------------------------------------------------------------------------------------
Just wanted to get extra help on this one ...
1. st find and extract image (recovery) on SM Galaxy core 2 SM-G355HN by adb :
Code:
C:\ADB\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>adb shell
[email protected]:/ $ ls -l /dev/block/platform/*/by-name/
ls -l /dev/block/platform/*/by-name/
lrwxrwxrwx root root 2014-11-10 14:25 CSC -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 2014-11-10 14:25 FIXNV1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-11-10 14:25 FIXNV2 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-11-10 14:25 FOTA_SIG -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-11-10 14:25 HIDDEN -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 2014-11-10 14:25 KERNEL -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 2014-11-10 14:25 MODEM -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-11-10 14:25 MODEM_BACKUP -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2014-11-10 14:25 OTA -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2014-11-10 14:25 Odin_reserved -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 2014-11-10 14:25 PARAM -> /dev/block/mmcblk0p13
[COLOR="Red"][B]lrwxrwxrwx root root 2014-11-10 14:25 RECOVERY -> /dev/block/mmcblk0p18[/B][/COLOR]
lrwxrwxrwx root root 2014-11-10 14:25 RUNTIMENV1 -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2014-11-10 14:25 RUNTIMENV2 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2014-11-10 14:25 SBL1 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-11-10 14:25 SBL2 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-11-10 14:25 WDSP -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-11-10 14:25 WDSP_BACKUP -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-11-10 14:25 efs -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 2014-11-10 14:25 fixnv1 -> /dev/block/platform/sprd-sdhci.3/by-name/FIXNV2
lrwxrwxrwx root root 2014-11-10 14:25 fixnv2 -> /dev/block/platform/sprd-sdhci.3/by-name/FIXNV1
lrwxrwxrwx root root 2014-11-10 14:25 prodnv -> /dev/block/mmcblk0p15
lrwxrwxrwx root root 2014-11-10 14:25 runtimenv1 -> /dev/block/platform/sprd-sdhci.3/by-name/RUNTIMENV1
lrwxrwxrwx root root 2014-11-10 14:25 runtimenv2 -> /dev/block/platform/sprd-sdhci.3/by-name/RUNTIMENV2
lrwxrwxrwx root root 2014-11-10 14:25 system -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 2014-11-10 14:25 userdata -> /dev/block/mmcblk0p22
[email protected]:/ $ su
[email protected]:/ # cat /dev/block/mmcblk0p18>/storage/extSdCard/recovery.img
cat /dev/block/mmcblk0p18>/storage/extSdCard/recovery.img
[email protected]:/ # cd storage
cd storage
[email protected]:/storage # cd extSdCard
cd extSdCard
[email protected]:/storage/extSdCard # unmkbootimg -i recovery.img
unmkbootimg -i recovery.img
kernel written to 'kernel' (12071152 bytes)
ramdisk written to 'ramdisk.cpio.gz' (1612341 bytes)
To rebuild this boot image, you can use the command:
mkbootimg --base 0 --pagesize 2048 --kernel_offset 0x00008000 --ramdisk_offset
0x01000000 --second_offset 0x00f00000 --tags_offset 0x00000100 --cmdline 'conso
le=ttyS1,115200n8' --kernel kernel --ramdisk ramdisk.cpio.gz -o recovery.img
[email protected]:/storage/extSdCard #
Ok, we found the recovery partition in /dev/block/mmcblk0p18 we copy the block to SDCard, unpack it with 'unmkbootimg' (tool for unpacking), we got the 'kernel' file and 'ramdisk.cpio.gz' file :
Unpack and cpio alined :
Code:
[email protected]:/storage/extSdCard # mkdir ramdisk
mkdir ramdisk
[email protected]:/storage/extSdCard # cd ramdisk
cd ramdisk
[email protected]:/storage/extSdCard/ramdisk # gunzip -c ../ramdisk.cpio.gz | cpio -i
isk.cpio.gz | cpio -i
cpio: can't create symlink from sbin/ueventd to ../init: Function not implemented
cpio: can't create symlink from sbin/watchdogd to ../init: Function not implemented
4252 blocks
[email protected]:/storage/extSdCard/ramdisk #
C:\ADB\adt-bundle-windows-x86_64-20140702\sdk\platform-tools>
Ok, forget about the symlink errors in this try,it's vfat extSdCard related,everything will be fine in internal procedure.
If we look more carefully in the ramdisk ..
init.rc,default.prop,recovery.fstab in /etc/ and the most importand recovery.do in /res/ and recovery in /sbin/
Start making and modding things he,he ... it's the start for now ...
If any1 have the linux machine and sources installed I could help him to make a CWM recovery for this phone.
Here is the guide (CWM) :
http://forum.xda-developers.com/showthread.php?t=1866545
Make backup of your current recovery (build) or you will have to flash the whole thing again with odin ...
Looking for a modded recovery with full (nand) backup, that would be greatest !

I have a building machine....and some time....I will send you a PM so we can chat in g+

Ok,thx.Just asking what else you need for my phone,accept working machine synced git with latest cwm module for 4.4.2 android,guess u will need partition table for the phone for full nandroid backup and some source samsung files or modded in mine disassembly and of course compiled cwm elf program -recovery.Looking forward ...
Sent from my SM-G355HN using XDA Free mobile app

CWM/TWRP recovery
Still looking for ppl who are willing to create/build a custom recovery for Galaxy Core 2. The image and all requested support is here.

StratOS_HTC said:
Still looking for ppl who are willing to create/build a custom recovery for Galaxy Core 2. The image and all requested support is here.
Click to expand...
Click to collapse
I got this CWM Recovery in our country forum (PH) others can make it work using Mobile Uncle but for me it doesn't work i think or i've missed some of the instructions.
DISABLE INTERNET TO PREVENT MOBILE UNCLE TO DOWNLOAD ANOTHER RECOVERY
1.Download recovery(cwm).zip and extract
2.Copy recovery.img and put it to your Internal
3.Install Mobile Uncle (Included in the zip)
4.Tap recovery update then tap recovery.img
5.Reboot!

I have checked this type or recovery. I guess it's not for our phone Galaxy Core 2. U don't need Mobile Uncle to flash an image to your recovery partition. The kernel and ramdisk are different then they have to be for our phone, don't want to meess with the recovery this type. Guess I'll have to backup whole lately nand copy ...

StratOS_HTC said:
I have checked this type or recovery. I guess it's not for our phone Galaxy Core 2. U don't need Mobile Uncle to flash an image to your recovery partition. The kernel and ramdisk are different then they have to be for our phone, don't want to meess with the recovery this type. Guess I'll have to backup whole lately nand copy ...
Click to expand...
Click to collapse
Ohhh thanks for the information. If only i could help. I am currently looking forward studying about this well yeah I am a newbie.

is this CWM for my galaxy core 2 duos ??
is this CWM for my galaxy core 2 duos ??

Odin recovery stock
Odin stock recovery file.
Android 4.4.2
SM-G355HN
Un 7zip it and use the recovery.tar.md5 with odin as AP
Use Auto Reboot and reset time.
Odin log :
Code:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Removed!!
<ID:0/005> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)

CWM Recovery
I made a bootable cwm recovery but I mismatch mount (recovery.fstab) points so no nand backup for now

Y300-0100 said:
I made a bootable cwm recovery but I mismatch mount (recovery.fstab) points so no nand backup for now
Click to expand...
Click to collapse
Recovery.fstab file located in /etc/ for G355HN :
Code:
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/platform/sprd-sdhci.3/by-name/efs /efs ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.0/mmcblk1p1 /sdcard vfat default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/system /system ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/HIDDEN /preload ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/userdata /data ext4 default wait,length=-16384
/dev/block/platform/sprd-sdhci.3/by-name/CSC /cache ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/KERNEL /boot emmc default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/RECOVERY /recovery emmc default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/MODEM /modemcp emmc default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/WDSP /modemdsp emmc default recoveryonly
Nice JOB !
Share a link to test it ?

CWM Recovery
StratOS_HTC said:
Recovery.fstab file located in /etc/ for G355HN :
Code:
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
/dev/block/platform/sprd-sdhci.3/by-name/efs /efs ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.0/mmcblk1p1 /sdcard vfat default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/system /system ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/HIDDEN /preload ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/userdata /data ext4 default wait,length=-16384
/dev/block/platform/sprd-sdhci.3/by-name/CSC /cache ext4 default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/KERNEL /boot emmc default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/RECOVERY /recovery emmc default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/MODEM /modemcp emmc default recoveryonly
/dev/block/platform/sprd-sdhci.3/by-name/WDSP /modemdsp emmc default recoveryonly
Nice JOB !
Share a link to test it ?
Click to expand...
Click to collapse
I know that's recovery.fstab I used it but it must be defined somehow different.
Something like this:
/dev/block/mmcblk0p1 /sdcard vfat default recoveryonly
Click to expand...
Click to collapse
Here is test version. It has to be flashed via odin as PDA file but it does not do anything because it doesn't mount any partition. And I used a litlle biger font
http://www.mediafire.com/download/oj94o0sdo0amvvy/recovery.tar.md5

CWM Recovery
new build I have been able to mount all partitions but not ext Sd and int SD.
I used this recovery.fstab. If anyone have idea how to define vold managed partitions let's hear it.
edit.
fixed mount internal sd
add.
my sources for cwm recovery only. If anyone can contribute please do.
what is left to be done:
-bacup is made in /data/media instead in root of internal sd.
-mount point is not well formed for extra card so it can't be mounted at all
https://github.com/Y300-0100/android_device_samsung_kanas3gnfcxx

Backup
Backup option log :
Code:
I:Cannot load volume /misc.
mount:mounting /dev/block/mmcblk0 on /sdcard0 failed: [COLOR="Red"]Device or resource busy[/COLOR]
W:failed to mount /dev/block/mmcblk0 (No such file or directory)
Error mounting /sdcard0!
mount: mounting /dev/blockmmcblk1p1 on /sdcard1 failed: [COLOR="Red"]Invalid argument[/COLOR]
W:failed to mount /dev/block/mmcblk1p1 (No such file or directory)
Error mounting /sdcard1!
I:Cannot load volume /misc.
[COLOR="SeaGreen"]I:using /data/media for /sdcard.[/COLOR]
I:Cannot load volume /misc.
none (internal or external) partition is mounted !
The backup is being created internaly in /data/media/ - no more space left after trying to create backup ...
Will try this :
Code:
/dev/block/platform/sprd-sdhci.0/mmcblk1 /sdcard[STRIKE]0 [/STRIKE] vfat default
/dev/block/platform/sprd-sdhci.0/mmcblk1p1 /sdcard[STRIKE]01[/STRIKE] vfat default
It's hard 'couse both are fuse'd or vold'ed by default. Could try media or datamedia type for internal or /dev/null ?
Update : blocks are mmcblk1 & mmcblk1p1 !
Fixed internal as default mount :
So internal SD /data/media for /sdcard !
extSDCard to go ...

StratOS_HTC said:
Backup option log :
Code:
I:Cannot load volume /misc.
mount:mounting /dev/block/mmcblk0 on /sdcard0 failed: [COLOR="Red"]Device or resource busy[/COLOR]
W:failed to mount /dev/block/mmcblk0 (No such file or directory)
Error mounting /sdcard0!
mount: mounting /dev/blockmmcblk1p1 on /sdcard1 failed: [COLOR="Red"]Invalid argument[/COLOR]
W:failed to mount /dev/block/mmcblk1p1 (No such file or directory)
Error mounting /sdcard1!
I:Cannot load volume /misc.
[COLOR="SeaGreen"]I:using /data/media for /sdcard.[/COLOR]
I:Cannot load volume /misc.
none (internal or external) partition is mounted !
The backup is being created internaly in /data/media/ - no more space left after trying to create backup ...
Will try this :
Code:
/dev/block/platform/sprd-sdhci.0/mmcblk1 /sdcard[STRIKE]0 [/STRIKE] vfat default
/dev/block/platform/sprd-sdhci.0/mmcblk1p1 /sdcard[STRIKE]01[/STRIKE] vfat default
It's hard 'couse both are fuse'd or vold'ed by default. Could try media or datamedia type for internal or /dev/null ?
Update : blocks are mmcblk1 & mmcblk1p1 !
Fixed internal as default mount :
So internal SD /data/media for /sdcard !
extSDCard to go ...
Click to expand...
Click to collapse
what is the right mount point to fix internal and external sd ?

mout points for sdcards
cleverior.ipul said:
what is the right mount point to fix internal and external sd ?
Click to expand...
Click to collapse
Question is not addressed to me but I will give a small contribution
It's kind of tricky regarding mount point of "internal SD".
Internal sd it's on same device (mmcblk0) as /data and it has multiple mount points but if you take a closer look with root explorer at /data/media/0 you will open emulated sdcard0.
So let's presume that src for internal sd is /dev/block/mmcblk0 and and let's say that mount point is /sdcard0.
Now let's go to BoardConfig.mk. I would suggest that we define internal storage path and mount point something like this:
Code:
RECOVERY_SDCARD_ON_DATA := true
BOARD_HAS_NO_REAL_SDCARD := true
INTERNAL_STORAGE_PATH := "/data/media/0"
INTERNAL_STORAGE_MOUNT_POINT := "data"
and now in recovery.fstab something like this:
Code:
#<src> <mnt_point> <type> <mnt_flags and options>
/dev/block/mmcblk0 /sdcard0 auto default
Why fs type as auto? Because I am not sure is vfat and it share same device as /data.
Also there is: /mnt/obb, /mnt/asec, /mnt/secure and /storage/emulated an for all file system is = tmpfs
And one more thing. Internal sd is definitely 'emulatedsd,nonremovable'
Regarding external sdcard you already fix that.

Y300-0100 said:
Question is not addressed to me but I will give a small contribution
It's kind of tricky regarding mount point of "internal SD".
Internal sd it's on same device (mmcblk0) as /data and it has multiple mount points but if you take a closer look with root explorer at /data/media/0 you will open emulated sdcard0.
So let's presume that src for internal sd is /dev/block/mmcblk0 and and let's say that mount point is /sdcard0.
Now let's go to BoardConfig.mk. I would suggest that we define internal storage path and mount point something like this:
Code:
RECOVERY_SDCARD_ON_DATA := true
BOARD_HAS_NO_REAL_SDCARD := true
INTERNAL_STORAGE_PATH := "/data/media/0"
INTERNAL_STORAGE_MOUNT_POINT := "data"
and now in recovery.fstab something like this:
Code:
#<src> <mnt_point> <type> <mnt_flags and options>
/dev/block/mmcblk0 /sdcard0 auto default
Why fs type as auto? Because I am not sure is vfat and it share same device as /data.
Also there is: /mnt/obb, /mnt/asec, /mnt/secure and /storage/emulated an for all file system is = tmpfs
And one more thing. Internal sd is definitely 'emulatedsd,nonremovable'
Regarding external sdcard you already fix that.
Click to expand...
Click to collapse
Have you tried this method in CWM for galaxy core 2 ? whether successful mounting sdcard and extsdcard ?
btw, thanks for ur answer

cleverior.ipul said:
Have you tried this method in CWM for galaxy core 2 ? whether successful mounting sdcard and extsdcard ?
btw, thanks for ur answer
Click to expand...
Click to collapse
Didn't try it. Just an idea because of multiple mounts points.

Y300-0100 said:
Didn't try it. Just an idea because of multiple mounts points.
Click to expand...
Click to collapse
Have tried with custom ramdisk = recovery.fstab - won't work - have to redefine BoardConfig and recreate the whole thing from the start.
Since I don't have linux machine I can't rebuild from the source. Still fixing the laptop, guess will have to buy new one
Looking forward for solution.
And once again internalsd is fixed, externalsd is not
Regards.

StratOS_HTC said:
Have tried with custom ramdisk = recovery.fstab - won't work - have to redefine BoardConfig and recreate the whole thing from the start.
Since I don't have linux machine I can't rebuild from the source. Still fixing the laptop, guess will have to buy new one
Looking forward for solution.
And once again internalsd is fixed, externalsd is not
Regards.
Click to expand...
Click to collapse
Just build TWRP recovery. Working external sd but no internal.
Apsurd.

SM-G361F - Pre-rooted rom development

Hello,
I'm not able to build (repackage) correctly system.img for SM-G361F, output is always rejected by both Odin (10.3.7) and Heimdall
I'm trying to repackage (pre-root) system.img taken from "G361FXXU1APA2_G361FOXX1APA1_G361FXXU1APA2_HOME.tar.md5" (taken from ETL factory image named ETL-G361FXXU1APA2-20160202095551.zip )
Step-by-step:
1) tar xvf G361FXXU1APA2_G361FOXX1APA1_G361FXXU1APA2_HOME.tar.md5 system.img
2) simg2img system.img system.img.raw
3) mount system.img.raw /mnt
4) made changes
5a) make_ext4fs -s -g 32768 -b 4096 -T -1 -S file_contexts -f -l 1843M system.repack.img /mnt/
5b) mkuserimg.sh -s /mnt system.repack.img ext4 system 1843M file_contexts
6) tar --owner 0 --group 0 --numeric-owner -H ustar -c system.img > G361F_SYSTEM.tar
7a) Load either system.img through Heimdall (PIT file downloaded through Heimdall is here: http://forum.xda-developers.com/showpost.php?p=65779994&postcount=146 )
7b) Load G361F_SYSTEM.tar in Odin v3.10.7 in AP tab and flash it
On ODIN/Download screen I can see that
1) FRP LOCK: OFF
2) KNOX: 0x0
3) System status: official
4) RP SWREV: S1, L1, M1
Notes
1) I have checked the box "OEM Unlock" in Developers settings to enabled
2) "file_contexts" is taken from booted up device through ADB (adb pull /file_contexts)
3) I've tried repackage the image without making any changes
4) When I compare original and repackaged images ("ls -lsaR" outputs), it seems like owner:group permissions are not persisted
5) I've tried both simg2img/make_ext4fs/mkuserimg.sh from CM12.1 repository (up to date today) and from https://github.com/ASdev/android_img_repack_tools (branch android-5.1.1)
6) I'm not sure about size 1843M, however flashing fails in the same manner when I go with 1536M and 2048M and anything between those two
7) Heimdall fails at about 6% of flashing single (sparse system.img) file with error "Failed to unpack received packet"
OSS Kernel for SM-G361F is here: https://github.com/smarek/G361F-Kernel
OSS Platform for SM-G361F is here: https://github.com/smarek/G361F-Platform
Questions are:
1) Is there anything special to be aware of when building for Samsung devices?
2) Did I miss or misunderstood any step in system.img repackaging process?

Help: Trying and failing with arch linux on note 10.1 - stuck in loop

Hi
I would be very glad if anyone could help me with this. Possibly somebody with experience in installing Arch on Note 10.1 (GT-8000).
I had LineageOS installed on the note, but when reading about installing Arch from https://forum.xda-developers.com/showthread.php?t=2195778 I wanted to give it a try.
The thing was about downloading 2 files - recovery (recovery.img) and rootfs (linux.img). The linux.img file was to be stored on the "Real" SD card.
"Real" sdcard card is : >>>>> /mnt/shell/emulated as described in the text, - but since I had LineageOS, - not Cyanogenmod 10.1, I googled a little and thought they meant /mnt/storage. Used root privileges and placed linux.img there. I then executed
dd if=recovery.img of=/dev/block/mmcblk0p6 to setup recovery.
I took a reboot and the tablet looked like linux booting up, but eventually it stopped on this:
.
.
[ 3.016883] c0 [E-PEN] wacom_i2c_init: Sleep type-PEN_LDO_EN pin
losetup: /dev/loop0: No such file or directory
mount: special device /host/media/linux.img does not exist
mount: mount point /new_root/mnt/sdcard does not exist
fsck.ext2: Invalid argument while trying to open /deu/loop0
/dev/loop0:
The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
ERROR: fsck failed on '/dev/loop0'
ERROR: Failed to mount the real root device.
Bailing out, you are on your own. Good luck.
sh: can't access tty; job control turned off
[rootfs /]#
What to do now?
The tablet will try to boot every time I shut it off - so it is in a constant loop.
Is there any way to get back to TWRP or other way to boot up LineageOS?
Or is it possible to do something about the files and "recovery.img", possibly re-locating them: If so - should linux.img be placed under /host/media/linux.img as the system cannot find it there? Maybe it was the analogue location for LineageOS (parallell to Cyanogenmod).
Thanks in advance

<<What to do now?
The tablet will try to boot every time I shut it off - so it is in a constant loop.>>
Flash your stock rom with Odin .

Odin
JJEgan said:
<<What to do now?
The tablet will try to boot every time I shut it off - so it is in a constant loop.>>
Flash your stock rom with Odin .
Click to expand...
Click to collapse
Thank you. I will try that.
Note: Tried with Heimdall from Linux, without being able to "detect device".

Cannot flash with Odin
memorie said:
Thank you. I will try that.
Note: Tried with Heimdall from Linux, without being able to "detect device".
Click to expand...
Click to collapse
Tried to flash with Odin;
I first downloaded an english stock rom for my norwegian device and tested. Then I found and downloaded stock rom (2015 edition). My device was bought in 2013. Odin finds devices and goes on, but does not get past ;
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> param.bin
<ID:0/004> tz.img
<ID:0/004> boot.img
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Is it another way to undo the process with commands that set the tablet in this state?
I suspect the dd if= ... command caused this stuck in bootloop.
Is it any way to reverse it?

Are you 100Sure you are using correct Note model firmware ??