clean Install never solve bootloop bug.I too have a bootloop. Anyway of fixing this without having to do a clean install?
clean Install never solve bootloop bug.I too have a bootloop. Anyway of fixing this without having to do a clean install?
So, only 7 seconds power button leads to bootloop?Do all people understand that you have to pull battery while phone in on and booted in main system?
maintaining Power button only won't always work as Samsung tricked it and now phones starts immediately to shutdown. Shame fix instead of working around the real problem
Forcing a ROM .tar through Odin for several times in a row seems to have worked for a few people :silly: silly: silly: :laugh: . They claimed to be bootloop free.clean Install never solve bootloop bug.
No, I also try that method...:silly:Forcing a ROM .tar through Odin for several times in a row seems to have worked for a few people :silly: silly: silly: :laugh: . They claimed to be bootloop free.lol...
Sent from hyperspace
I don't know what I'm doing wrong, but just now again tested with previously installed kernel and both new ones - PhilZ-cwm6-ZSLO2-OZS-4.93.6-signed.zip and PhilZ-cwm6-XXLSZ-OXA-4.93.6-signed.zip.This why I did stop fixing the bootloop issue
No one else tested, and now that I took my time to edit, repack and upload all these, you come complain![]()
now i'm confused:silly:I don't know what I'm doing wrong, but just now again tested with previously installed kernel and both new ones - PhilZ-cwm6-ZSLO2-OZS-4.93.6-signed.zip and PhilZ-cwm6-XXLSZ-OXA-4.93.6-signed.zip.
Phone booted with long press button and battery removal when phone ON.
ROM - XXLSZ Italy stock odex.
May be there some misunderstanding relating to Hot Boot. Phone booted after battery removed. But if use program Quick Boot Plus with options Hot Boot, phone does not booted. And same if use big power menu and push options Hot Boot (or Hot Reboot) phone not booted too.
Google play link: https://play.google.com/store/apps/...pcml1c2FwcGxpY2F0aW9ucy5xdWlja2Jvb3QucGx1cyJd
And as wrote before - remember that N7000 is one model, but in reality it may have little different hardware as well as some changes in ROMs (customs)
Perhaps post the Zimage if you have downloaded already.@Philz
New firmware German DBT
my thread
http://forum.xda-developers.com/showthread.php?t=2241203
Inviato dal mio GT-N7000 con Tapatalk 2
I don't know what I'm doing wrong, but just now again tested with previously installed kernel and both new ones - PhilZ-cwm6-ZSLO2-OZS-4.93.6-signed.zip and PhilZ-cwm6-XXLSZ-OXA-4.93.6-signed.zip.
Phone booted with long press button and battery removal when phone ON.
ROM - XXLSZ Italy stock odex.
May be there some misunderstanding relating to Hot Boot. Phone booted after battery removed. But if use program Quick Boot Plus with options Hot Boot, phone does not booted. And same if use big power menu and push options Hot Boot (or Hot Reboot) phone not booted too.
Google play link: https://play.google.com/store/apps/...pcml1c2FwcGxpY2F0aW9ucy5xdWlja2Jvb3QucGx1cyJd
And as wrote before - remember that N7000 is one model, but in reality it may have little different hardware as well as some changes in ROMs (customs)
ADD: I do not tested Quick Boot with latest 2 kernels
Calm down everyone, HootBoot seems to be not kernel related issue.. further searching the problem I found everybody seems complaining in other forums as well.. Some said that installing new busybox with pkill module can solve the issue (read this post here).. I personally tried that method but no go.. but since there is someone who had solved this problem by just installing some extra busybox modules will at least give us a hint where to search..@Phil3759
Kernel for N7000XXLT4
http://d-h.st/w6y
Edit: trying hotboot, bootloop happened on this stock kernel too.
It goes to recovery, there is a red error saying that:
E:Error in /data/log/recovery_kernel_log.txt
(Read-only file system)
and cannot boot up the phone, I suppose flash you kernel and restore my backup again
The important thing is shoey- YOU should have fun and enhance your knowledge. Bugs will come and go.I would love to contribute to the bootloop issue, but I no longer have a Note1. In fact I have just ordered Sony Xperia Z. Waterproof, dust-proof, 5" TFT screen, JB 4.1.2 and no superbrick/Sudden Death Syndrome issues. Entropy512 and Codeworkx (Plus many other heavy hitters) are over there developing CM10.1 for the device. Codeworkx refuses to develop for SGS 4. "Samsung is history" - in his own words. I hope I have a little more luck with Sony....
i read that too but that doesnot explainCalm down everyone, HootBoot seems to be not kernel related issue.. further searching the problem I found everybody seems complaining in other forums as well.. Some said that installing new busybox with pkill module can solve the issue (read this post here).. I personally tried that method but no go.. but since there is someone who had solved this problem by just installing some extra busybox modules will at least give us a hint where to search..
You are great Philz and always I love your modified kernels and recoveries images in other devices.. BIG THANKS and RESPECT to YOU!!
NoIs it necessary to do a full wipe If I replace old philz kernel with new one? 4.90.8 by 4.93.6
Sent from my GT-N7000 using xda premium