Ok I'm confused now. is this BOOTLOOP HANG/FREEZE issue now referred to as a "soft brick" problem? Or are they different?
Was running sweet v10.5, started getting mad battery drain and it wouldn't enter deep sleep (suspected My Quitbuddy to be the culprit). Whilse I was trying to find apps to investigate better I noticed v11.1 was out.
Downloaded v11.1, Flashed following instructions. Went to do first boot and it froze on the "Samsung galaxy note gt-n7000b" screen. After 20minutes I gave up and assumed something went wrong.
MD5 check passed. Flashed again, no worries.
Started usual setup of phone and it would randomly reboot. Found Xposed installer and got a big smile from the modules then went to work to push the note to it's limits once again. Mainly changing simple things (button actions, look of phone) stayed away from any kernel settings. But I did install a fair few modules just to suss it out. Can these modules interfere with eachother? I was assuming when I came across the same settings in other modules if I kept them set the same I would be safe (same init.d scripts unless the coder was a numpty).
Spent the next 6 hours going through all my new toys as google play decided it wanted to install every single app I had on sweetrom v10.5 on my phone (which would be great... if I didn't have a battery problem in 10.5).
Passed out after doing a reboot. Phone was at boot screen not the gt-n7000 initial splash screen and was plugged into charger. Woke up to the splash screen. Spent the next 2 hours simply trying to get the phone to boot and/or get into CWM after swapping between 2 batterys numerous times she finally booted up properly. Now to hope like F that my battery drain issue is under reasonable control that the stupid thing will charge while plugged into ac not keep draining but I think that's a "when pigs fly" scenario.
Can you PLEASE recommend a firmware that does not have this boot loop issue? I was thinking of trying hello world's kernal hoping that would sort the issue. I class the note as a legacy device. It's a disappointment that I STILL am yet to find a phone that can handle me.
Do you think changing kernals will help? I am using philz that came with sweet rom v11.1. Please keep in mind I have done the test. My phone is one of the models that CAN get the brickbug, however I passed the tests and it shows 11-12gb available space (did the test a few months ago)
I find it a joke that some of you are being smart arses on the subject. The note uses battery, I have 2 spare in my pocket. The only time I realise my phone has actually turned off is when it does the single vibration in my pocket. No need to be an immature kid, I am trying to figure out a fix.
Anyone who want's to improve the note please help, rest of you shut ya gob before I shut it for ya! Feel free to inbox me personally I am at the point where I have tried numerous firmwares over the last year and am ready to make my own. Just such a shame hardly anyone can be clear with instructions on this site and it's like reading a damn QBasic book from the 90's.
Thanks for the rom Not-i I appreciate the fact that you are still atleast making that effort. This latest rom is running smoother and looks nicer on my note. If you could pm me where you made a start on custom roms that would be great. I have the time and the understanding to give it a go. It's just this site is very daunting with people not sticking to correct terms or even half arsing the written guides.
I sincerely think switching to hello world kernel after a full wipe will resolve your issue. If you contonue to have issues after that PM me
Sent from my GT-N7000 using Tapatalk 2