[Galaxy Note II Q&A, Help & Troubleshooting] E90 Commie:
I posted an old thread about this but now I have spent a lot of time trying to investigate and I am at a complete loss of ideas now.

The first thing that has to be stated is that my N7100, bought in Sweden, is rock solid under the ALJ3 based BatteryPlus 0.2 ROM. It works absolutely excellent, not a single problem. Just stable and reliable operation.

The problem:

Now to the very strange problem.

The 4.1.2 ROMs causes the device to reboot randomly. I have tried the following options:

1. Stock ROM XXDLL7 flashed through Odin 3.0.4 in Windows 7.

It reboots very often, even without a single app or mod installed. Even before rooting, it reboots. When it reboots, it can perform the whole process and return to a working state.

2. Omega 9.1 flashed through CWM 6.0.1.5.

It reboots less than with stock DLL7 but still very often. The longest uptime I managed to get was approximately 10 hours and that was with the memory card removed as an experiment. During many of those reboots, it fails to boot up completely, it just hangs at the Omega animation. A reboot by pressing the power button works.

3. JellyBam 3.3.0 flashed through CWM 6.0.1.5.

This ROM worked great for a couple of hours but then started to reboot. I.e. it worked for approximately 4-5 hours without any problems and then the rebooting started and reached a high frequency.

4. Kingdroid 2.1 flashed through CWM 6.0.1.5.

This ROM carried my farthest with approximately 8 hours between the reboots. It worked reliable for that amount of time between the reboots while the other ROMs showed a tendency to reboot frequently when that "cycle" started.

5. WanAm Lite DLL5 based flashed through CWM 6.0.1.5.

It rebooted in a similar fashion to the Omega ROM.

The interesting thing with all this is that stability and reliable operation returns immediately when I flash back to BatteryPlus 0.2. I can experience random reboots with a high frequency with a 4.1.2 ROM and then immediately flash BatteryPlus 0.2 and get stability. One example is a ROM that reboots within 5 minutes or even during initial setup, if I then flash the BP 0.2 - everything works perfect again without any reboot.

The steps I have taken in order to troubleshoot are:

1. Full wipe - every flash has been made with full wipe including format /system and /preload.

2. I removed the memory card as one step, unfortunately the random rebooting continued but with a longer period.

3. I reformatted the card both from CWM and from the Settings but the rebooting continued.

4. I tried an older 8 GB SanDisk Ultra card from my Vivaz - and it still rebooted.

5. I removed the SIM card (Straight Talk mini SIM cut to micro SIM) - and the rebooting persisted.

6. I downloaded the emergency restore ROM and made a .PIT repartitioning through Odin - and the rebooting persists.

7. I flashed the latest XXDLL7 through Odin - and it reboots.

The interesting detail is that the flashes itself has been successful and I have been unable to pinpoint anything, for example radio or bootloader. I am now running BatteryPlus 0.2 with the latest DLL7 bootloader and radio - without any single problem.

The fact that the reboot behavior differs between different ROMs (some experiences random reboots within 10 minutes, others works for hours) together with the fact that BatteryPlus 0.2 works perfect clearly points AWAY from hardware problems. The memory card and everything runs perfectly well under that older ROM.

The only thing I have been thinking about is if there is a recovery problem. On my N7000 I had to revert to HyperDroid RedPill Recovery (Abyss Kernel 3.9 RedPill) since I noticed that CWM didn't properly wiped the cache partition (I got "Android is updating xx of yy" even after a full wipe) and instability. With the RedPill, everything worked perfectly well.

I have also tried to do some logcat but has been unable to pinpoint any single process causing a reboot. I suspected the Pure Messenger Widget for example (which works perfect in 4.1.1) but when the rebooting started without a single application installed etc, that theory failed.

The recovery I have used is the CWM 6.0.1.5 flashed through Odin as a part of the root package.

I tried to flash DLJ2 ROMs through TWRP as an experiment one month before but still with rebooting.

I am at a complete loss at this stage, the only thing I can think about is if there are some kind of "mismatch" between 4.1.2 based ROMs and CWM 6.0.1.5 - or if there is something going on with the CSC that is Nordic (I have never changed it).

The Note was delivered with ALJ1 originally if I remember that correctly.

This problem annoys me since it would be nice to upgrade to 4.1.2 ROMs but all random reboots prevents this.:(

Is there anyone that has experienced the same problem?

To me is it a bit strange that the device works perfectly under the 4.1.1 based BP 0.2 but acts up with random reboots under anything 4.1.2. Since I got farthest with JellyBam 3.3.0 and Kingdroid 2.1, it is obvious that the reboots are triggered differently. With some ROMs, I have noticed reboots when the USB cable is plugged in. Not immediately but after a while (5 minutes or so). In BP 0.2, this don't happen.

I would be grateful for any kind of help here.

I am not interested in sending the device for service since I clearly suspect a software problem - the extremely reliable operation in BP 0.2 indicates this. If it would be the hardware, it would act up in a very similar manner - and certainly in BP 0.2 too.