Develop Bugs

[Q] Note 2 reboot loop [HELP]

I'm on stocked JB 4.1 with root active. I had installed some apps, like app2sd, busybox and airdroid. Just after this I did a reboot into recovery then
1) clear cache
2) clear daviak cache,
3) clear battery stats
4) fix permissions
5) reboot into system.
Just after following the above process my note 2 keeps on rebooting from Samsung N7100 boot logo to homescreen for (2 sec) and then again reboot.
I can't find a way to understand what went wrong please someone help me.

Go to download mode and flash rom again is the only way
Sent from my GT-N7100 using xda premium

happened to me couple of times. just took out the battery, and clipped it back again. i'm running on stock rom and no tweaks; first encountered after updating with multitasking.
for peace of mind, flash the rom and it should fix the problem. :victory:

@carlo I already tried that and which didn't work.
Later that day I did a nandroid backup and then restored to factory reset, and later recovered specific data with TB. I have used S2 and SNexus in the past and never is that such a thing happened forget Stock not even with Custom Roms.
Though I still wish to know what is triggering it to go into such kind of limitless Loop anyone?

when you restored to factory reset, did you still experience the loops? if so, might be time to take it to warranty and them check your unit.
but if doesn't, say a day of use, and no issues, then it could be triggered by something in your backed up tweaks and apps which you can just experiment on to ID what could be causing the issue.
*a friend however had similar issues like yours, but after a day or so of tinkering with his note2, we found out that it was his cheap TPU case that was causing the problem. it was a bit too tight! there were no cutouts for his volume and power buttons, so somehow the grip he has on the unit triggers the unit go wacko.
strange but true. no more issues with his note on capdase case with no changes on software and settings.
hope you get your issues figured out soon.
cheers!

@carlo: as soon as I did factory reset everything is well, no more boot loops.
I'm not using any case anyway. But I think it's because of davik cache. I'm not gonna do that again :-[
Sent from my GT - N7100 using xda premium.

Samsung Galaxy Note 2 stuck in boot loop
leonalewis said:
I'm on stocked JB 4.1 with root active. I had installed some apps, like app2sd, busybox and airdroid. Just after this I did a reboot into recovery then
1) clear cache
2) clear daviak cache,
3) clear battery stats
4) fix permissions
5) reboot into system.
Just after following the above process my note 2 keeps on rebooting from Samsung N7100 boot logo to homescreen for (2 sec) and then again reboot.
I can't find a way to understand what went wrong please someone help me.
Click to expand...
Click to collapse
After playing with the Cyanogenmod 10 nightly, I was missing some of the Samsung Stock items so went to the Jellybean 4.1.2 Stock ROM for my Samsung Galaxy Note 2 (n7100) via ODIN. As I rebooted I had a panic moment because it kept looping between the Samsung Logo and a floating purple blob. So I tried going back into the Clockword MOD option (Power / Home / PowerUp) and ran a the System Clean / Factory reset. Devices then booted just fine.

(Soft?) Bricked Galaxy Note 8.0

I have been running CivZ ROM on my new Note 8.0 WiFi. Yesterday I tried the unofficial CyanogenMod port and this morning the tablet powered off of it's own accord. When I turned it back on it was stuck on the initial splash screening saying "Galaxy Note 8.0 N5110" etc. I definitely flashed the correct file and it worked for a while.
But, now I can't boot. I can boot into TWRP recovery, but whatever I flash, the tablet still won't boot. Any suggestions?

You will probably have to install the kernel separately.

cruise350 said:
You will probably have to install the kernel separately.
Click to expand...
Click to collapse
I just got back home planning to flash a kernel as you suggested. Before the kernel, I first did a total wipe and reflashed the CivZ FlexBeam ROM. And then it just worked, no separate kernel needed
Good news, of course. But I'd still like to know why that didn't work the time before. I think last time AROMA installer froze just before the end, so maybe it was failing to flash the kernel for some reason... Guess I'll never know for sure, just glad I have my tablet again.
Thanks for your help!

Can't get CM11 nightly to install

I installed the nightly cm11 cm-11-20140104-NIGHTLY-d2spr.zip and gapps 4.4, and an ics modem, then rebooted, and all I get is a black screen after the Samsung logo. After that it doesn't go anywhere just stays that way. I can get into recovery again just fine.
Steps I have done are as follows:
Wipe data/factory reset
wipe cache partition
wipe dalvik
Install rom (above zip file)
install pa gapps 4.4
install ICS modem SPH-L710_LI3_Modem
I have tried 3 different types of recovery, CWM touch, CWM normal, and Philz recovery, all three ways result in the same black screen after the Samsung logo.
Someone suggested I needed the MG2 bootloader so I used this rom on this thread http://androidforums.com/boost-mobile-galaxy-s3-all-things-root/758586-odin-backup-sph-l710_mg2.html and got MG2 successfully installed and up and operational.
I thought maybe it was because gapps was giving me issues so I decided to install cm11 without anything else to rule out anything else, and make sure it wasn't the rom itself.....same black screen after the Samsung logo.
I then suspected the recoveries so installed different ones to rule them out, did the steps over again with each recovery, and still same black screen after the Samsung logo.
I am in the process of downloading other KK roms, but until then, does anyone have any ideas what I may have missed or am doing wrong....if anything or perhaps what the cause f this can be and how to fix it?
I've done this what seems a million times on my S2 so it's not like I'm not familiar with the process and how to do things, I just can't seem to get it working on this phone.

easyrider77 said:
I installed the nightly cm11 cm-11-20140104-NIGHTLY-d2spr.zip and gapps 4.4, and an ics modem, then rebooted, and all I get is a black screen after the Samsung logo. After that it doesn't go anywhere just stays that way. I can get into recovery again just fine.
Steps I have done are as follows:
Wipe data/factory reset
wipe cache partition
wipe dalvik
Install rom (above zip file)
install pa gapps 4.4
install ICS modem SPH-L710_LI3_Modem
I have tried 3 different types of recovery, CWM touch, CWM normal, and Philz recovery, all three ways result in the same black screen after the Samsung logo.
Someone suggested I needed the MG2 bootloader so I used this rom on this thread http://androidforums.com/boost-mobile-galaxy-s3-all-things-root/758586-odin-backup-sph-l710_mg2.html and got MG2 successfully installed and up and operational.
I thought maybe it was because gapps was giving me issues so I decided to install cm11 without anything else to rule out anything else, and make sure it wasn't the rom itself.....same black screen after the Samsung logo.
I then suspected the recoveries so installed different ones to rule them out, did the steps over again with each recovery, and still same black screen after the Samsung logo.
I am in the process of downloading other KK roms, but until then, does anyone have any ideas what I may have missed or am doing wrong....if anything or perhaps what the cause f this can be and how to fix it?
I've done this what seems a million times on my S2 so it's not like I'm not familiar with the process and how to do things, I just can't seem to get it working on this phone.
Click to expand...
Click to collapse
Unless it is a typo, this is the Sprint S3 forum. You are lucky you didn't mess up your phone using our modem. 2nd, if you are on an S3, you need the latest clockworkmod recovery and need to be on md4. I would not take update to MK3, but you can flash the modem and it will work much better. ?
-Whiplashh
Sent from a Premium Xda app using the Flo Nexus 7.

Whiplashh said:
Unless it is a typo, this is the Sprint S3 forum. You are lucky you didn't mess up your phone using our modem. 2nd, if you are on an S3, you need the latest clockworkmod recovery and need to be on md4. I would not take update to MK3, but you can flash the modem and it will work much better. ��
-Whiplashh
Sent from a Premium Xda app using the Flo Nexus 7.
Click to expand...
Click to collapse
Kinda confused at your post....I realize it's a s3 forums, that's why I posted here.....what typo?
I mentioned about the s2, that WAS what I had before, and I was comparing it with the s3 as far as install goes, if that's what yer referring to.
Perhaps I overlooked my post but I'm not seeing where I referred to anything but the s3, other than me saying about the s2 line.
If your referring to the fact it's a boost mobile s3, they are the same phones, one is branded boost one is branded sprint, both have the same internals and hardware, and both use the same name SPH-L710. You can also use sprint roms/modems/kernels on a boost s3....is this what yer wondering about?
Am I missing something??
As for the cwm, yes I have tried 4 different recoveries. I will cut and paste my steps and stuff from another forums so as to save typing.....here it is:
Symptoms:
When I install a rom via philz, cwm touch, or cwm normal, after install and reboot I get to the samsung logo, and then it goes to a blank screen. I have let it sit to upwards of a 1/2 hour and nothing happens. Battery does not get hot, just nothing happens.
Steps I take on install/wipe are as follows:
-Boot into recovery
-Data/Factory reset
-Clear cache partition
-clear Dalvik cache (under advanced)
-Flash Rom of choice
-Flash Gapps if it apply's (with touchwiz it does not apply)
-reboot to system
All that being said.......I just bought this phone at best buy 3 days ago.
While the phone works really well, samsung has done somthing to the os/phone that makes it harder to root or use roms.
I have tried numerous roms, and having no luck whatsoever installing them.
I have been compiling a list of roms and such and here is what I have so far:
Roms with a black screen after samsung logo:
-CM11 nightly latest build - blank screen after samsung logo
-Beanstalk 4.4 nightly build - black screen after samsung logo
-Cm10.2.0 - bails out on install
-CM10.1 - bails out on install
-Carbon Rom 4.4.2 - black screen after samsung logo
-Slimbean 4.3 - black screen after samsung logo
-Slimbean 4.4 - black screen after samsung logo
Roms that have worked fine:
-jdsingle MK5 Tw rom
-ODIN Backup for --> BOOST MOBILE SPH-L710_MG2 (tw) - no isues at all
-stock rooted MD7 rom (tw) - no issues at all
-stock rooted MG2 rom (tw) - no issues at all
-VanirAOSP nightly - installed with a modified cwm recovery, philz/cwm normal/cwm touch I got a black
screen after samsung logo - had a few glitches
-Fox - installed with a modified cwm recovery, philz/cwm normal/cwm touch I got a black screen after
samsung logo - no wifi or 3g/data
-Bam Android - installed with a modified cwm recovery, philz/cwm normal/cwm touch I got a black
screen after samsung logo - no data/3g
-Carbon rom 4.3.1 installed with a modified cwm recovery, philz/cwm normal/cwm touch I got a black
screen after samsung logo - had a few glitches
As you see above the list is getting quite long, sonsidering a ton of others have not had this issue, and I see on videos this same exact phone SPH-L710 people instlal just fine.
I have talked closely with struckn and some other devs as well, and nobody can figure out why I cannot install these roms. Speculation however is from reading and from what people have told me on xda and here, is that these newer s3's somehow have been modified via the hardware or software (I lean to the software) so it makes it really difficult to root/install roms.
I know it can be done because I am rooted, and I have used 3 or 4 different TW roms. Anything aside from that it just doesn't work, and throws me into a blank screen.
So I'm at a loss right now why this is giving me such problems, so I will throw this out there, in desperation and ask....does anyone have any ideas why, am I just destined to be stuck on touchwiz and not have any other choice or options??
Hope this clears things up a lil, sorry if I wasn't as thorough as I needed to be .

issue resolved.

easyrider77 said:
issue resolved.
Click to expand...
Click to collapse
What did you do to resolve this issue?

[Q&A] [SM-T525] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 10.1 LTE (picassolte)

[Q&A] [SM-T525] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 10.1 LTE (picassolte)
Q&A for [SM-T525] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 10.1 LTE (picassolte)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [SM-T525] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 10.1 LTE (picassolte). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

RaiBinger said:
Hi again!
In 211014 ROM trouble with video in YouTub. If set pause then after play again video not work. Tell me please in last build ROM nightly update this issue resolved?
Click to expand...
Click to collapse
I have the same problem. at the same time when it occurs in other players turns off hardware decoding.

@crpalmer "As far as I am concerned, installing Xposed is the exact opposite of a clean install. Xposed can cause all kinds of problems (it just randomly changes how internals of the system work!).
If you have problems with a clean install (without Xposed), please provide logs.
---------------
Admin Note: this thread has a dedicated questions and answers section which you can access here -->."
I have factory reset, data wipe cache and delvik wipe and then just flashed Nightly from 24.10.2014 and gapps. Cannot even get through the set up before the screen flickers and the device reboots.

So installed the nightly from 27.10 and all was good for a few hours then the random reboots have started again. No xposed or any other mods. Will provide logs.

joeb690 said:
So installed the nightly from 27.10 and all was good for a few hours then the random reboots have started again. No xposed or any other mods. Will provide logs.
Click to expand...
Click to collapse
So I'm not sure what to do next, device is unfortunately unusable, I must of made a mistake somewhere along the line.
What I have tried so far:
1. boot into cwm recovery
2. wipe data/factory reset
3. wipe cache
4. wipe delvik cache
5. install nightly 27.10.2014
6. wipe cache
7. wipe delvik cache
8. install gapps from link provide in OP
9. repeat steps 6 & 7
10 reboot system.
Sometimes it will boot normally and allow me to proceed through set-up but will then very quickly crash/reboot and the it seems to be in a bootloop, or other times it will show the Samsung splash and then power off.
Yesterday I was able to use it for several hours with out a problem but then suddenly it restarted and was once again very unstable.
Also getting very erratic battery readings ( I preformed a battery calibration before wiping Touchwiz probably a big mistake I realise now )
Any help or ideas would be greatly appreciated. :good:
not sure how to provide logs as the device is so unpredictable.

joeb690 said:
So I'm not sure what to do next, device is unfortunately unusable, I must of made a mistake somewhere along the line.
What I have tried so far:
1. boot into cwm recovery
2. wipe data/factory reset
3. wipe cache
4. wipe delvik cache
5. install nightly 27.10.2014
6. wipe cache
7. wipe delvik cache
8. install gapps from link provide in OP
9. repeat steps 6 & 7
10 reboot system.
Sometimes it will boot normally and allow me to proceed through set-up but will then very quickly crash/reboot and the it seems to be in a bootloop, or other times it will show the Samsung splash and then power off.
Yesterday I was able to use it for several hours with out a problem but then suddenly it restarted and was once again very unstable.
Also getting very erratic battery readings ( I preformed a battery calibration before wiping Touchwiz probably a big mistake I realise now )
Any help or ideas would be greatly appreciated. :good:
not sure how to provide logs as the device is so unpredictable.
Click to expand...
Click to collapse
There isn't any crash in the last_kmsg. Are the logs pulled after a crash?

Yes. Will provide another log today.

Unfortunately cannot provide another log as it the device will not work long enough to email the log, will flash stock ROM and see what happens. Maybe it a physical problem.

So flashed stock using odin and problems persist. Rebooting at what seems like random times. And then during the reboot it will reboot and then sometimes nothing it's dead and doesn't react to any action except putting it in download mode. Doesn't matter if I have several apps running or if I let it idle. Never had any issues like this before rooting. Any ideas as to where I went wrong.
I know this has nothing to do with your ROM but any feedback would be appreciated. Thanks.

joeb690 said:
So flashed stock using odin and problems persist. Rebooting at what seems like random times. And then during the reboot it will reboot and then sometimes nothing it's dead and doesn't react to any action except putting it in download mode. Doesn't matter if I have several apps running or if I let it idle. Never had any issues like this before rooting. Any ideas as to where I went wrong.
I know this has nothing to do with your ROM but any feedback would be appreciated. Thanks.
Click to expand...
Click to collapse
Are you sure you flashed the right Odin images? Did you factory reset?
One thing to try would be to flash the CM recovery (twrp would also be fine if it supports last_kmsg and I forget if it does) and let it sit and see if it reboots. If so, then grab the last_kmsg via adb. If you want to flash CM again, you can try to use adb to get a last_kmsg via adb since it just has to boot long enough for adb to access it.

I flashed the latest image for the German sm t525 model from sammobile. I have performed a factory reset but I thought that when you flashed an image with odin the device is wiped clean? Do you mean CWM recovery you provide in the OP? Thanks for you reply.

Hi,
I have Bluetooth issues since some versions. Cannot connect to any device....
Other question: is it still ro.sf.lcd_density=320 ?

dft601 said:
Hi,
I have Bluetooth issues since some versions. Cannot connect to any device....
Other question: is it still ro.sf.lcd_density=320 ?
Click to expand...
Click to collapse
Do you know (and if you not would you mind trying a couple of versions) when bluetooth problems would have started?
I recently changed the density setting to ro.sf.lcd_density=320 because it seemed to fix some apps that had weird issues (e.g. Chrome Beta's tabs). Is it causing a problem for you?

crpalmer said:
Do you know (and if you not would you mind trying a couple of versions) when bluetooth problems would have started?
I recently changed the density setting to ro.sf.lcd_density=320 because it seemed to fix some apps that had weird issues (e.g. Chrome Beta's tabs). Is it causing a problem for you?
Click to expand...
Click to collapse
Hmm, sorry, do not know which version I had last before 200141109, I already deleted from my device.. at least 200141107....
No, I have no problem with the density. It fixes also problems for me (e.g. Swiftkey, Navigon,....) Till now I added this manually.
Mike

Autorotate and Contact view
Hi
I'VE installed the latest version and untill now everything is fine for me,
But whenn I open my contacts the autorotate function stops to work and I have to turn my tab by 180°

Hello there!
The rom is working great, battery time is better than stock rom, and its much faster and smoother!
Altough I am having one issue with my tablet. Sometimes on random (really random!), when I try to unlock the tablet it stops responding to touch - at all! I cannot unlock it, cannot restart it normally, cannot do anything. I have to reboot the tab by holding power button down.
I changed dpi to 240, because 320 was too high for me, everything was so big - but I don't think that dpi has something to do with the issue.
Also sometimes my Link2SD script doesnt load the 2nd sdcard partition - but this might not be connected with the rom.
But anyway this rom is great and I am happy to have it on my tablet! You're doing great job mate! Thanks a lot. The only thing I miss is multi- and floating- windows, but I can live without it.
PS I noticed you are working on Cyanogenmod 12 for exynos version, do you plan building and trying it for our snapdragon version?

poleq16 said:
Hello there!
The rom is working great, battery time is better than stock rom, and its much faster and smoother!
Altough I am having one issue with my tablet. Sometimes on random (really random!), when I try to unlock the tablet it stops responding to touch - at all! I cannot unlock it, cannot restart it normally, cannot do anything. I have to reboot the tab by holding power button down.
I changed dpi to 240, because 320 was too high for me, everything was so big - but I don't think that dpi has something to do with the issue.
Also sometimes my Link2SD script doesnt load the 2nd sdcard partition - but this might not be connected with the rom.
But anyway this rom is great and I am happy to have it on my tablet! You're doing great job mate! Thanks a lot. The only thing I miss is multi- and floating- windows, but I can live without it.
PS I noticed you are working on Cyanogenmod 12 for exynos version, do you plan building and trying it for our snapdragon version?
Click to expand...
Click to collapse
I posted a status update in the sm-t320 thread. The snapdragons are in much better shape than the exynos...

joeb690 said:
I flashed the latest image for the German sm t525 model from sammobile. I have performed a factory reset but I thought that when you flashed an image with odin the device is wiped clean? Do you mean CWM recovery you provide in the OP? Thanks for you reply.
Click to expand...
Click to collapse
So I sent my Tab in for repair and all went well, they never mentioned KNOX but this was a private company contracted by Samsung here in Germany to do repairs. Not sure of all the details but its was a hardware failure.
Unfortunately my Tab was "lost" by the courier firm contracted to return my device. In the process of making a claim and will probably receive a new device.

random touchscreen knockout
Hi there,
Just curious: do some more people have random loss of the touchscreen functionality for some seconds or even until a reboot is performed?
Hardware buttons are always fine, though.
I found one post related to this, but no clear answer.
Wiped data and cache but did not install latest nightly yet.
Is that a "known issue something" for build 20141112?
Maybe I should mention that I'm noob level: ultra...

CWMR (Recovery) flash file for ODIN
CWMR (Recovery): (use latest version)
Download: http://download.crpalmer.org/downloads/picassowifi/
* Unzip the .ZIP file and then flash the .tar.md5 that it contains using Odin
Click to expand...
Click to collapse
crpalmer could you pleas upload your flash file again? it's the best way for me because I hate to use the free alternative to ODIN...
EDIT: SORRY SHOULD BE FOR USING WITH SM-T520 DEVICE - DID USE WRONG THREAD!!!

samsung galaxy note 2 GT-N7100 failure to flash ROM's over 5.0+

i have a samsung galaxy note 2 GT-N7100 international. i have been rooted for
over a year and have successfully loaded more than 10-15 ROM's. most of these
are in the 4.4.1 - 4.4.4 OS range. these load OK.
my problem is with most all of the rom's ported for the N-7100 coming from 5.0
to 6.0+ OS's. most of these are based off of cyangen mods compiles. the
symptom i have is: after following the directions in the compiler's post, i
get to the boot splash screen yet no further. no boot loop: it just never
boots up. i have waited 10" min for first boot. i waited 30" on 2 of them.
they just wont boot up. ever. my details are as follows below. im looking
for help on this because i know the problem must be on my end....all of these
compilers cannot all be wrong.
- im following OP directions always to the T; usually these include factory
reset (cache, dav cache, data wipes), sometimes they want system wiped too.
then you flash the ROM, then gapps. then you reboot.
this is standard. but sometimes they want you to also wipe cache + dav cache
AGAIN after the reload, then, reboot. in my mind, such a complete ROM install
removes all error from users like me...what more can you wipe?
- im always using ROM's designated only for the GT-N7100 int version note 2.
always.
roms that have NOT installed lately:
- [OFFICIAL][6.0.1][v6.0][STABLE]BlissRoms
- [ROM][5.1.1][Haxynox] AOSP for n7100
- [ROM][6.0.1][n7100]RESURRECTION REMIX 5.6.x[CM13]
- Alliance ROM for Galaxy Note 2 GT-N7100
roms that DO LOAD:
- Criskelo ROM for Galaxy Note GT-N7100
- Sungsonic HD ROM for Galaxy Note 2 GT-N7100
- DN4 ROM GT-N7100
- [ROM][GT-N7100][TW 4.4.4] Eclipse By AC
again: i need help with this problem which is my problem: in the list above
the unsuccessful rom's boot only to the splash screen, then hang. for 30+
min. no boot loop's, they dont boot at all.
i CAN later reboot into recovery or bootloader OK. i can re-install from previous
nandroid backup OK. i just CANNOT get them to boot. even after wiping both
caches and data and system before flashing, and, even after wiping both caches
afterwards.
more details:
1) im using both twrp 2.8.7.0 and latest cwm 6.0.4.3 touch recoveries. i
prefer and use twrp. ive tried loading the above failed roms above with both
recoveries, no help. i didnt think it mattered which recovery was used until
one time, the system partition didnt mount on twrp after a failed rom install.
it would'nt wipe nor format on twrp. i could not reinstall my nandroid
backup and was stuck.
i later flashed cwm 6.0.4.3 and it fixed it (the system partition problem,
but, cwm never installed the above rom's either). so there is a difference
after all but not much.
2) my roms are stored on my ext sd card. not sure if that's impt.
what's my problem?
1) if it's me please help
2) is it my phone? my GT-N7100 was bought in turkey. is my hardware really
different (ie chipset) from other international GT-N7100's. if so, what does
samsung mean by an international version?
i think the problem is on my end because other posters have said they loaded
same rom's OK.
any advice would be appreciated. im trying to upgrade to the 5.0+ OS's
because the new API's contained therein would open up the full manual camera
setting controls on the note 2...provided thru various apps that require 5.0+
android releases. granted, the note 2 camera wouldn't stop a clock, but it's
the phone i have. now. i like photograghy.
rather than buy a note 5 for $600, im trying to get these above rom's to
install. thanks all.
noted: im also looking into buy a nice camera for $600 that would take better
pics than a new phone: just pls help me with the above problem.