My Samsung Galaxy Note

I buy a vanilla device from amazon.

I root it following

This will void my warranty, and a yellow exclamation mark on booting will tell Samsung so. However, I do not care. I know that the device works, and I have already bathed it once in coffee, so Samsung won’t pay anyways. And I can afford a new one if it breaks.

I use ODIN 3 v1.85 and CF-Root-SGN_XX_OXA_LA4-v5.0-CWM5.tar

Download and start Odin, connect mobile while switched on => loads some usb drivers; switch mobile off.

Boot into download modus by holding Vol.Down+Home while pressing Pwr.On; acknowledge warnings

In Odin: “PDA”, select the .tar; Start. After a few seconds the device boots.

My messages On odin look different in the last step, I get:

<ID:0/009> Added!!
<ID:0/009> Removed!!
<ID:0/008> Added!!
<ID:0/008> Removed!!
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> zImage
<ID:0/010> NAND Write Start!!
<ID:0/010> RQT_CLOSE !!
<ID:0/010> RES OK !!
<ID:0/010> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/010> Removed!!
<ID:0/009> Added!!
<ID:0/009> Removed!!
<ID:0/008> Added!!
<ID:0/008> Removed!!

Start CWM app => asks for root => accept (SUCCESSFULLY ROOTED!).

I immediately start a backup to the external SDcard; I will now sleep much better.

I think I need no custom rom for this device. Most features seem to work much better than on my Milestone 1. Let’s see.

Disable volume buttons


Analoguous to


key 115   VOLUME_UP    WAKE


comment lines out with #

(Does not work with Root Explorer, but with ES File Manager)


=> ok! The keys are dead!

Change LCD density


With LCD Resolution (root) to 260 DPI from original 320. There is a graphics problem with the phone app, in portrait mode not all buttons are visible for resolution below or equal 240.

Go for a Ice Cream Sandwich 4.X custom ROM


  • Why ICS? Mainly because auf the bug in the Text Edit field in practically all browsers (Android Issue#9828).

Why not wait for official Samsung ICS?

  • Who knows whether it ever comes, and whether it works (see my Motorola Milestone page).
  • It will not have root for some time
  • Because it will be heavily bloated. I want AOSP.

Whay AOSP and root? Because E.g. …

  • Stock will not allow to change screen resolution, and I have reasonably good eye sight. Even with root, the Samsumg bloatware (e.g. Phone Dialer) will just not work properly with changed resolution, and it will be close to impossible to replace it.
  • I really need backups
  • I’m physicist. If I encountert something new, I dismantle it…

I use the following information information:

First I check whether I have really root and copy a file to /system (with Root Explorer).

First I make a nandroid backup with “CWM” app (with “Backup”). The backup is quite large (1.21 GB) and is stored in /mnt/sdcard/external_sd/clockworkmod/backup and I’ve named it 2012-05- I copy this, and an older backup, to my laptop.

I make a Titanium backup of all user apps with changed data.

Now I make an “/efs” backup (which seems to be my IMEI and baseband info) following

I have to unzip an app in Windows (“EFS Pro.exe”) and move it to myNote  directory. Enable USB debugging. Connect Note to PC via USB. Start app. Check “Save Backup to Device Storage” -> says will be saved to /sdcard/EPSProBackup; check “Save backup to PC storage” -> says in subfolder EFSProBackup in same folder as EFS_Pro.exe. “Backup EFS”, says sucess, stuck, files not on PC. Kill, repeat with “Use Internal Busybox” -> works. However, on the device there are now two versions, I delete the older one.

I hope I never need the backups.

I download the ICS repack following I have to bypass all java security to get this download. I use the five parts instead of the large one.

OOOPS! My laptop is infected by the “Smart Fortress 2012”  trojan! *** DONT *** use the Java interface for the download above. I get rid of it by doing a system restore after booting into the restricted mode of Vista.

Go on with the Note…

I copy both the repack…rar and the stunner…zip onto the SDcard. Start “Mobile Odin Pro”. Open the .rar, wipe data … flash… inject everything…

I end up in a recovery, I do restart … I think I’m in some 4.0 now. However, not the Stunner ROM!

I can call my wall phone (connected with a copper line).

Mobile Odin Pro is still there, but the Stunner…zip is not visible; hm; probably wrong format!

No, but I have to install it via another method: cwm restore! Unfortunately, for this the file has to be on the internal sdcard; I connect the phone via usb -> works, I can move the file from “Card” to “Phone”.

One can boot into recovery on the note by pressing volume-up + home + power-on for 10 sec until start screen appears.

I select wipe data (it says among others “wipe sd-ext…” – we will see …), and cache  “install zip from sd card” – “choose zip from internal sd” – does something … and I end up in Stunner ICS 4.0.4.

After connecting to my google account, I can install Titanium Backup, and with that most of the apps.

I test Jotter – OOPS, does not work, S-Pen makes no lines while the Palm touches the screen.

I test whether issue 9828 is solved – IT IS NOT!

The message app always sends messages on the return key, this cannot be switched off.

I make another nandroid backup of this system, and will go back to Gingerbread, as before. I cannot find any reason to go for ICS.

WHen I try to restore the backup, the restore fails at “restore /system”. Maybe because the charger was connected? I retry it without charger… passes system… works on data… hope I run not out of battery now… Restoring .android_secure… Error! Restoring single partitions does not work, MD5 mismatch! Retry complete restoer woth charger connected…boot…system…data… again fails on this step! However, I can reboot the device now properly… seems to work.

Phone and Wlan work. I hope it is stable.

Summary: I cannot see any reason to go to ICS.

Official release of ICS from Samsung


Two weeks ago the official release of ICS in Germany was made available.

Why will I install this, if I did not keep Stunner ICS?

1) Full support of S-Pen should now work, different from Stunner.

2) All apps will now be updated only for ICS

3) Chrome Beta for ICS; I hope this resolves issue 9828 finally

I will install it, but want to keep root. Therefore I follow
N7000XXLPY 4.0.3 2012 May N7000OXALPY Open Germany posted to OP

LPY seems to denote this ICS version in the following
This is Non Wipe version
Installation note : How to update from GB ROM to ICS

Install using Mobile Odin safely
– Download N extract ROM

“N” seems to denote “and”. I make a backup with CWM during this to external SD card. Unfortunately, this boots the device. Now I do not know whether the download is complete. CWM should ask whether to restart really! Now I have to wait for 25 min to download again… Now the download of the ROM also is possible again. However, the download fails again after a few minutes. Probably the bad connection through the telekom austria ADSL (I’m at the countryside). I try it with the laptop -> I had to wait for 29 minutes! I decide to vnc to a linux server at the university, which is connected directly to the internet (without any provider). From there I start the download. It says it will take some 31 min – this works; now I have to download it from the server to my laptop – I get here only 330 KB/s. I have to wait again for about half an hour. Then it takes two min to transfer the file over usb. I extract it using Astro on the phone in the folder /sdcard/ICS-ROM. This produces two files:

N7000XXLPY__…._HOME.tar.md5 and one SS_DL.dll

– Copy Extracted file to a folder e.g ICS ROM On Ext/Int SD card

I hope this is the files hea means…
– Download CF Root for LPY

I have some CF Root already, but I think I need the proper one for the ICS ROM. Searching in xda for “Download CF Root for LPY” forwards me to the link In the sixt post I find a link to I download this to the phone.

– Extract CF root till get zImage file

I can “Extract” is with Astro, pruduces a .tar, which I extract again and get the “zImage”.

– Copy zImage file to same above said folder in SD car

I copy it to new folder /sdcard/ICS-ROM.
– Open Mobile Odin
– Select ‘Open file’ N point to ROM file

Ok. It says that several partitions have been set, also kernel. The tabs in Mobile Odin read now Int.SD/ICS-ROM/N7000….tar.md5 for Kernel?, System, Cache, Modem, Hidden.
– select Kernel tab N point to zImage file

Ok. Kernel tab  reads now Int.SD/ICS-ROM/zImage.
– select Ever Root option

– Flash

Asks to check MD5, I select check… Checks… Reboots… Boot screen MobileOdin… Kernel Clearing/Flashing… System Flashing… Prograss bar grows for about 1 min… Rooting… Modem Clearing/Flashing … more, too fast to read… Reboot… Samsung boot sound there again… 1 min “SAMSUNG” display… “Android OS wird optimiert/App XX von 131 wird optimiert.” (XX counts up till 131) … SIM nummer wird verlangt … “starting apps” … Black screen, some notification bar icons … lockscreen with pen … I unlock … “Installieren der Anwendungen” “Mit WLAN verbunden” … GO Launcher EX starts, homever, in low resolution.
– You will get ICS ROM + Root + CWM

This is true.

Note After flsing finish, it will optimize installed application for ICS, then will auto restart

Does not restrt for me, restart manually
I have experienced Applicatioin installer crash first time, Then i have restarted device
Then again application Installation happened N worked Normally
Titanium Backup, checked. I have restore one old app N worked without issue.

LCD Resolution does not work. It rather seems to break something, fortunately I have not set on boot yet. I have to live with 320 for the first. Grmph. I try LCD density modder… Stalls first time, asks for root in sendond try … reboots … stuck at boot screen.

With VolumeUp+Home+On: restore the backup from this morning. I hope this works… No! device crashes. I have bricked my device.

I will try to follow to recover.

Error: The backup GPT table is not at the end of the disk, as it should be.
This might mean that another operating system believes the disk is smaller.
Fix, by moving the backup to the end (and removing the old backup)?
Fix/Ignore/Cancel? F
Warning: Not all of the space available to /dev/block/mmcblk0 appears to be
used, you can fix the GPT to use all of the space (an extra 2048 blocks) or
continue with the current setting?
Fix/Ignore? F

Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt

Number  Start   End     Size    File system  Name       Flags
1      4194kB  25.2MB  21.0MB  ext4         EFS
2      25.2MB  26.5MB  1311kB               SBL1
3      27.3MB  28.6MB  1311kB               SBL2
4      29.4MB  37.7MB  8389kB               PARAM
5      37.7MB  46.1MB  8389kB               KERNEL
6      46.1MB  54.5MB  8389kB               RECOVERY
7      54.5MB  264MB   210MB   ext4         CACHE
8      264MB   281MB   16.8MB               MODEM
9      281MB   1174MB  893MB                FACTORYFS
10      1174MB  3322MB  2147MB  ext4         DATAFS
11      3322MB  15.2GB  11.9GB  fat32        UMS
12      15.2GB  15.8GB  537MB   ext4         HIDDEN

Uff. Seems to live again. What I did: follow post #12 literally; however, had to download sdk from, this from post #??? of this thread could not be extracted from the archive.

parted complained “Warning: Not all of the space available to /dev/block/mmcblk0 appears to be used” which I fixed. When I tried to upgrade the ext2 to ext4, there was a message about mtab not existing. I had to mount the /data and the /system partition from CWM recovery, then it warned but worked. When making UNS the device complained about a write error, therefore I made it only from the start suggested by post #12, to 10.0 GB.

Odin (1.85) did not work for me at all for the stock ROMs (GB and ICS), always stuck at “veryfying MD5” or “system.img/Write to NAND”. I did not try any custom ROM. I could apparently flash the kernel from post #12 with Odin. However, there was still CWM when booting into recovery. I put the AbyssKernel on the (external) sdcard, and renamed it to, and applied this with CWM recovery. There is apparently  a mixup in CWM recovery: I’m not sure, but I think it confuses internal and external sd card.

After having the Note rest over night with power off, reboot into download and recovery ended up in AbyssNote. From there I did try a restore of a backop I had made some time ago with the CWM app, after rooting stock Gingerbread, and it ran through!

Wireless works, I’m currently charging and updating apps. I did not try the SIM yet, but I expect no problem. Once the phone is fully charged, I will have a try to parted again, to get more memory in internal, and maybe flash a newer backup.

Update: unfortunately it crashed after updating the apps, again ending in aboot loop. I flash a new backup, try it, repeat,.. and accidently flash a ICS at some time, and continue without thinking – and have again flashed with an ICS kernel! Again, some space on the emmc is broken. I flash the proper kernel for adb parted again (does not work with abyss):

Number  Start   End     Size    File system  Name       Flags
1      4194kB  25.2MB  21.0MB               EFS
2      25.2MB  26.5MB  1311kB               SBL1
3      27.3MB  28.6MB  1311kB               SBL2
4      29.4MB  37.7MB  8389kB               PARAM
5      37.7MB  46.1MB  8389kB               KERNEL
6      46.1MB  54.5MB  8389kB               RECOVERY
7      54.5MB  264MB   210MB   ext4         CACHE
8      264MB   281MB   16.8MB               MODEM
9      3322MB  4215MB  893MB   ext4         FACTORYFS
10      4215MB  6362MB  2147MB  ext4         DATAFS
11      6362MB  10.0GB  3638MB  fat32        UMS        msftres
12      15.2GB  15.8GB  537MB   ext4         HIDDEN

=> EFS has lost the ext4 label! This might becone difficult.

However, I first delete and rebuild the CACHE: seems to work.

Delete and rebuild FACTORYFS: stuck at 85%. This corresponds to 7XX MB; my system in CWM backup has some 824 MB. Will not fit.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: