Related
Hey people.
I'm just looking to findout how many of us have the issue of bootlooping (splash screen) overclock kernel is installed...?
I have seen at least 10 ppl on here - please post so it gets known how many we are.
I have tried formatting SD-card w both HP-formatter and Panasonic SD Formatter - neither helped -
I have Cleared Dalvik, Wiped Cache, Wiped to Factory Settings - and redone it over and over.
Nothing helps. Bootloop. As soon as i reflash Froyo kernel official (0050 on WildPuzzle Rom) everything works perfectly.
I have ruled out that the problem would be in SD-card. I have tried three diff cards of various brands and sizes - and also tried without SD-Card. All resulting in Bootloop when OC is flashed.
ADB won't let me get a logcat - as it don't find a device connected - or - as in the latest v5 OC kernel, says Device is offline.
How many - and who - has this issue - There has gotta be something we can do? POST to show the devs you exist please.
I have the same problem too. I've just installed new roms and also kernels. Nothing happened. My wildfire won't boot-up
I understand your frustration guys, really.
Unfortunately though, it is hard for me to be able to fix it without any logs, and I don't have time to play around with potential causes at the moment.
Hope you guys understand
We so do.
But is there noway to get a log w-o booting past splash?
HCDR.Jacob said:
I understand your frustration guys, really.
Unfortunately though, it is hard for me to be able to fix it without any logs, and I don't have time to play around with potential causes at the moment.
Hope you guys understand
Click to expand...
Click to collapse
Here's a question to everyone who cant boot OC - what color is your phone?
the 2 i gave physically encountered that have the problem are both red...?
I solved my bootloop by simply removing my SD-card and then booting. :O Format didnt work forme neither.
try it out
I have - made no difference. As i said before - there is no way that the issue is with the sd-card... I have tried everything regarding that. Results are the very same with - or without sd-card...
But thanks for trying to help...
danne_jo - adeadrat? any of you two live anywhere near stockholm..? if yes i could meet either of you and you can see the issue 1st hand..? maybe you can dig out a log somehow?
worst case scenario (i am desperate yes) maybe i can mail my phone to you jacob and you send it back in two weeks or so? (can't believe i'm saying this)
Phinxy said:
I solved my bootloop by simply removing my SD-card and then booting. :O Format didnt work forme neither.
try it out
Click to expand...
Click to collapse
fireplayer said:
We so do.
But is there noway to get a log w-o booting past splash?
Click to expand...
Click to collapse
Perhaps you can get the logcat via adb when in recovery?
naserbaser said:
Perhaps you can get the logcat via adb when in recovery?
Click to expand...
Click to collapse
There's a kernel debug message system too, although I'm not sure if it'd work if adb doesn't
fireplayer said:
I have - made no difference. As i said before - there is no way that the issue is with the sd-card... I have tried everything regarding that. Results are the very same with - or without sd-card...
But thanks for trying to help...
danne_jo - adeadrat? any of you two live anywhere near stockholm..? if yes i could meet either of you and you can see the issue 1st hand..? maybe you can dig out a log somehow?
worst case scenario (i am desperate yes) maybe i can mail my phone to you jacob and you send it back in two weeks or so? (can't believe i'm saying this)
Click to expand...
Click to collapse
I don't want you to mail me your phone. I'll help out where I can, but if you send your phone to me and it gets lost in the post or I accidentally kill it, I'll feel really bad so I'd rather you didn't :/
hehe, no im not living close to stockholm, and sorry I can help out either
I had the bootlooping too, but that was untill i used the Remove HTC apps puzzle piece, maybe it's sense / rosie thats causing the issue, i'll try my best to look into it.
Been stupidly busy as of late, haven't had time to even work on my own rom lol, peace yall
So how would I get to that..? Everything is worth a try..
HCDR.Jacob said:
There's a kernel debug message system too, although I'm not sure if it'd work if adb doesn't
Click to expand...
Click to collapse
Sent from my HTC Wildfire using XDA App
understandable lol. just trying to make something happen ;p it's frustrating...
HCDR.Jacob said:
I don't want you to mail me your phone. I'll help out where I can, but if you send your phone to me and it gets lost in the post or I accidentally kill it, I'll feel really bad so I'd rather you didn't :/
Click to expand...
Click to collapse
tried that - didn't help, tried openfire rom too - same result.
Elbie said:
I had the bootlooping too, but that was untill i used the Remove HTC apps puzzle piece, maybe it's sense / rosie thats causing the issue, i'll try my best to look into it.
Been stupidly busy as of late, haven't had time to even work on my own rom lol, peace yall
Click to expand...
Click to collapse
fireplayer said:
tried that - didn't help, tried openfire rom too - same result.
Click to expand...
Click to collapse
Curious but which version of the touch screen do you have?
You can find out by pressing the Vol Down button and Power button at the sam time when turning on the wildfire.
A Load of txt will come up, Will tell you if you have the Atmel or not.
Could be that as I know the PSFreedom guys are having issues with the other type of touch panel.
Elbie said:
Curious but which version of the touch screen do you have?
You can find out by pressing the Vol Down button and Power button at the sam time when turning on the wildfire.
A Load of txt will come up, Will tell you if you have the Atmel or not.
Could be that as I know the PSFreedom guys are having issues with the other type of touch panel.
Click to expand...
Click to collapse
I have the same problem.
My touch panel is ATMELC03_16ac.
I too have the atmel, and I have no issues, although I have gone back to the non OC kernel as it seams more stable. I had a few force closes on a few apps...allllll the time, double twist mainly lol.
Ummm confusing one this..
Hi all the guru,
Please..Need help.. My wildfire have problem that is always bootlooping also..
I just updated from puzzlerom 8.07 to 8.10.. successfull then I do partition sdcard ext.. the WF rebooting it seft... until now..
Just flash rom again, but this theme is about OC problems...
Hey,
So I flashed a custom rom on my AT&T Galaxy S IV. Everything seems to be working fine.
Until, I hold on my power menu than click on Reboot my phone. When I do that, my phone shuts down and reboots but it's always stuck in the Samsung Custom Screen. The max I have waited is 30 minutes for it to work. But it never does.
I'm running TWRP Recovery Mode.
I tried every roms in the AT&T Section. All of them seems to have that problem. I also used ktoonsez kernel. Nothing at all.
With stock AT&T rom everything seems to be fine.
I was wondering if it's happening to you guys as well. If you can try, please hold into your power button and reboot your phone clicking on reboot.
Thank you!
I have that happen sometimes, but if I go into recovery when that happens and fix permissions it boots up fine after.
Sent from my SGH-I337 using Tapatalk 4 Beta
Flash a different kernel.
Period
your welcome
TehZam said:
Hey,
So I flashed a custom rom on my AT&T Galaxy S IV. Everything seems to be working fine.
Until, I hold on my power menu than click on Reboot my phone. When I do that, my phone shuts down and reboots but it's always stuck in the Samsung Custom Screen. The max I have waited is 30 minutes for it to work. But it never does.
I'm running TWRP Recovery Mode.
I tried every roms in the AT&T Section. All of them seems to have that problem. I also used ktoonsez kernel. Nothing at all.
With stock AT&T rom everything seems to be fine.
I was wondering if it's happening to you guys as well. If you can try, please hold into your power button and reboot your phone clicking on reboot.
Thank you!
Click to expand...
Click to collapse
make sure you flashed the correct ktoonsez kernal..one for aosp, one for touchwiz
And flash Loki Doki patch if required, although you'd probably get the 'software not compatible' error if Loki was missing.
KonoeKyon said:
I have that happen sometimes, but if I go into recovery when that happens and fix permissions it boots up fine after.
Sent from my SGH-I337 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I'll try and post back to you!
TheAxman said:
Flash a different kernel.
Period
your welcome
Click to expand...
Click to collapse
If you don't mind me asking, what kernel are you using?
mixlex said:
make sure you flashed the correct ktoonsez kernal..one for aosp, one for touchwiz
Click to expand...
Click to collapse
I have used the Touchwiz kernal.
blyndfyre said:
And flash Loki Doki patch if required, although you'd probably get the 'software not compatible' error if Loki was missing.
Click to expand...
Click to collapse
Tried that and done that, no go.
________________________________________
Thank you everybody for the help.
what procedures are you using for all of this? is there a specific guide you are following?
xBeerdroiDx said:
what procedures are you using for all of this? is there a specific guide you are following?
Click to expand...
Click to collapse
So at first I used this [ROOT] Root Samsung Galaxy S4 with Motochopper. Same problem.
Went back to stock and used this
[ROOT[RECOVERY] Loki + TWRP + Motochopper CASUAL-R527b release:27May13. Same problem encountered.
Went back to stock and did it again using Same problem with this one as well.
It happens with every custom rom besides the stock rom and Cyanogenmod Rom. I can't even reboot to do anything .
Thanks for the help guys, I greatly appreciate it.
There is something else happening, does this happen on a backup you may have?
You do have a backup correct? It is rule #1
TheAxman said:
There is something else happening, does this happen on a backup you may have?
You do have a backup correct? It is rule #1
Click to expand...
Click to collapse
Yes, I do have a backup. It happens to every custom ROM that I have encountered with.
Stock & Cyanogenmod roms work fine when rebooting.
Would you mind sharing what kernel you are using? I jused used faux kernel. Same thing.
i meant more like what procedures are you using when you wipe and flash? your issue is not related to root method or a particular custom recovery.
xBeerdroiDx said:
i meant more like what procedures are you using when you wipe and flash? your issue is not related to root method or a particular custom recovery.
Click to expand...
Click to collapse
Sorry for the confusion, I used your guide!
I have the solution.
I can bet that when you wiped your phone you didnt just factory reset on twrp you WIPED the whole partition.
So when TWRP made another one it messed up thats why it doesnt work after a reboot.
I am 1000000% sure of this.
So go back to stock then factory reset through STOCK recovery and then install rom and factory reset click the icon on the left not the one on the right that makes you type 'yes'
TWRP doesnt format the partition correctly for our phones.
and the fact that the bootloader is still locked messes things up.
I am 1000000% sure of this.
are you really sure?
j/k, perfect.
TheAxman said:
I am 1000000% sure of this.
are you really sure?
j/k, perfect.
Click to expand...
Click to collapse
yep I am that sure haha.
jetlitheone said:
I have the solution.
I can bet that when you wiped your phone you didnt just factory reset on twrp you WIPED the whole partition.
So when TWRP made another one it messed up thats why it doesnt work after a reboot.
I am 1000000% sure of this.
So go back to stock then factory reset through STOCK recovery and then install rom and factory reset click the icon on the left not the one on the right that makes you type 'yes'
TWRP doesnt format the partition correctly for our phones.
and the fact that the bootloader is still locked messes things up.
Click to expand...
Click to collapse
Your method worked! Thank you very much, I greatly appreciate it.
Hello,
I don't know why this is happening to my phone. I recently got this phone. I rooted it but it is a stock flash. I only keep apps that I need and disable everything else. However, about 50% of the time, any calls that I get, as soon as I accept it, it's restarts. Also, Whenever I am making a call, the phone goes dark, never comes back on to cancel a call or something and restarts if no one picks up. If someone picks up, the screen goes back on.
What gives?
rationalthinker1 said:
Hello,
I don't know why this is happening to my phone. I recently got this phone. I rooted it but it is a stock flash. I only keep apps that I need and disable everything else. However, about 50% of the time, any calls that I get, as soon as I accept it, it's restarts. Also, Whenever I am making a call, the phone goes dark, never comes back on to cancel a call or something and restarts if no one picks up. If someone picks up, the screen goes back on.
What gives?
Click to expand...
Click to collapse
Most probably ROM problems. Try changing the ROM.
abaaaabbbb63 said:
Most probably ROM problems. Try changing the ROM.
Click to expand...
Click to collapse
But it's a stock ROM. I didn't even install any other ROM.
rationalthinker1 said:
But it's a stock ROM. I didn't even install any other ROM.
Click to expand...
Click to collapse
Yeah, but system errors can occur, like a file being corrupted. This is solved by reflashing the system partition.
abaaaabbbb63 said:
Yeah, but system errors can occur, like a file being corrupted. This is solved by reflashing the system partition.
Click to expand...
Click to collapse
Hey, can you provide me a link or a tutorial on how I can do that?
Thank you.
rationalthinker1 said:
Hey, can you provide me a link or a tutorial on how I can do that?
Thank you.
Click to expand...
Click to collapse
You just take your ROM (Be sure it's the exact version you have installed), and flash it from recovery, without wiping anything.
My phone reboots on DP5 whenever the device locks and it's not charging. It happens in safe mode too, and after factory resets. Any advice?
Thanks!
Tiduszk said:
My phone reboots on DP5 whenever the device locks and it's not charging. It happens in safe mode too, and after factory resets. Any advice?
Thanks!
Click to expand...
Click to collapse
It may be far fetched but check and make sure your case is not putting pressure on Power button.
Witek_M said:
It may be far fetched but check and make sure your case is not putting pressure on Power button.
Click to expand...
Click to collapse
Using a live case, complete cutouts for the buttons. Thanks for offering any help though!
Tiduszk said:
Using a live case, complete cutouts for the buttons. Thanks for offering any help though!
Click to expand...
Click to collapse
I am running N preview since March as daily driver. Just looked at up time. Last reboot was after DP5 update. Try flashing official factory image and see if that cures the problem.
Witek_M said:
I am running N preview since March as daily driver. Just looked at up time. Last reboot was after DP5 update. Try flashing official factory image and see if that cures the problem.
Click to expand...
Click to collapse
Is a dirty flash okay, or should I clean flash?
Witek_M said:
I am running N preview since March as daily driver. Just looked at up time. Last reboot was after DP5 update. Try flashing official factory image and see if that cures the problem.
Click to expand...
Click to collapse
Also, will I still get OTAs if I flash it?
Tiduszk said:
Also, will I still get OTAs if I flash it?
Click to expand...
Click to collapse
Clean flash only. Of your device is enrolled on preview program you will receive OTA when it becomes available.
Witek_M said:
Clean flash only. Of your device is enrolled on preview program you will receive OTA when it becomes available.
Click to expand...
Click to collapse
Okay. Thank you! I'll report back with results
Witek_M said:
Clean flash only. Of your device is enrolled on preview program you will receive OTA when it becomes available.
Click to expand...
Click to collapse
Two new developments. The reboots survived two clean flashes (the first time didn't boot for some reason), and the real cause of the reboots is nothing to do with Google play movies; the phone reboots wherever it locks while connected to a carrier network. I however did find a temporary fix for this, just putting my phone into airplane mode whenever I'm not using it, but that is not sustainable for obvious reasons.
Tiduszk said:
Two new developments. The reboots survived two clean flashes (the first time didn't boot for some reason), and the real cause of the reboots is nothing to do with Google play movies; the phone reboots wherever it locks while connected to a carrier network. I however did find a temporary fix for this, just putting my phone into airplane mode whenever I'm not using it, but that is not sustainable for obvious reasons.
Click to expand...
Click to collapse
Try changing or reflashing the radio?
DJBhardwaj said:
Try changing or reflashing the radio?
Click to expand...
Click to collapse
I'll give it a try, where can I get my hands on it?
Tiduszk said:
I'll give it a try, where can I get my hands on it?
Click to expand...
Click to collapse
Radio flash-able image files are present inside every factory image. What radio version are you currently operating on?
DJBhardwaj said:
Try changing or reflashing the radio?
Click to expand...
Click to collapse
I just reflashed "radio-angler-angler-03.72.img"
I'll reply again with whether or not it worked.
Tiduszk said:
I just reflashed "radio-angler-angler-03.72.img"
I'll reply again with whether or not it worked.
Click to expand...
Click to collapse
Good luck. If it doesn't, try radio version 3.61 from the latest MM factory image (MTC20F).
DJBhardwaj said:
Radio flash-able image files are present inside every factory image. What radio version are you currently operating on?
Click to expand...
Click to collapse
It did not fix it. Thanks for your help though.
DJBhardwaj said:
Good luck. If it doesn't, try radio version 3.61 from the latest MM factory image (MTC20F).
Click to expand...
Click to collapse
Is the marshmallow radio compatible with DP5?
Tiduszk said:
Is the marshmallow radio compatible with DP5?
Click to expand...
Click to collapse
Theoretically, it shouldn't harm at all. Kindly wait for someone with more experience on this. Until then, post your query at this thread: http://forum.xda-developers.com/nexus-6p/general/android-n-doesnt-t3332989
DJBhardwaj said:
Theoretically, it shouldn't harm at all. Kindly wait for someone with more experience on this. Until then, post your query at this thread: http://forum.xda-developers.com/nexus-6p/general/android-n-doesnt-t3332989
Click to expand...
Click to collapse
Well, I'll try it tomorrow. The worst that could happen is that I need to do a clean flash again.
Tiduszk said:
Well, I'll try it tomorrow. The worst that could happen is that I need to do a clean flash again.
Click to expand...
Click to collapse
DJBhardwaj said:
Theoretically, it shouldn't harm at all. Kindly wait for someone with more experience on this. Until then, post your query at this thread: http://forum.xda-developers.com/nexus-6p/general/android-n-doesnt-t3332989
Click to expand...
Click to collapse
Unfortunately it did not help, the issue persisted. I then tried to flash all the way back to stock marshmallow, and that didn't work. With Nougat released today, I flashed to it and my phone still reboots. I was able to further isolate the cause though; the phone reboots when it has a mobile data connection regardless of carrier (I tried Sprint, T-Mobile, AT&T, and China Unicom).
I think my only option left is to RMA it again.
Hello, im new here so sorry in advance if i seem like a noob haha
I have a S8 with stock rom but rooted with magisk.
I have firmware AQK7 installed but would like to upgrade with flashfire to AQL5 so i keep all my data and root.
I use flashfire and select the zip file, uncheck the inject supersu, add to flash magisk v15.0 zip and start to flash.
The screen just turns black and the phone just reboots and nothing has changed.
What am I doing wrong?
pls help
silverik1 said:
Hello, im new here so sorry in advance if i seem like a noob haha
I have a S8 with stock rom but rooted with magisk.
I have firmware AQK7 installed but would like to upgrade with flashfire to AQL5 so i keep all my data and root.
I use flashfire and select the zip file, uncheck the inject supersu, add to flash magisk v15.0 zip and start to flash.
The screen just turns black and the phone just reboots and nothing has changed.
What am I doing wrong?
pls help
Click to expand...
Click to collapse
Its probably starting to flash. The screen for some devices is VERY dim while doing flashfire flashes and can look like its off. Take it into a dark room and check.
Although if you have g950f why not just use twrp?
Its not a dark screen....it just reboots.
And if I use twrp do I keep my data?
Sorry im a rookie at this.
Learning fast but still....
silverik1 said:
Its not a dark screen....it just reboots.
And if I use twrp do I keep my data?
Sorry im a rookie at this.
Learning fast but still....
Click to expand...
Click to collapse
Nobody???
I guess if nobody knows its not possible???:crying:
silverik1 said:
Nobody???
I guess if nobody knows its not possible???:crying:
Click to expand...
Click to collapse
Use titanium backup on the playstore to backup all your apps incase somthing happens.
silverik1 said:
Its not a dark screen....it just reboots.
And if I use twrp do I keep my data?
Sorry im a rookie at this.
Learning fast but still....
Click to expand...
Click to collapse
Same thing happens for me, buddy. Sadly I haven't found out why.
amon-san said:
Same thing happens for me, buddy. Sadly I haven't found out why.
Click to expand...
Click to collapse
Are you sure the screen isn't just really dim? That's a known issue with flashfire, especially older versions and older roms
partcyborg said:
Are you sure the screen isn't just really dim? That's a known issue with flashfire, especially older versions and older roms
Click to expand...
Click to collapse
no, i know how it should look like because it worked fine on another device.
there is was rather dim but legible. took quite a lot of time to finish.
on my new device it really just quickly rebooted without doing any work.
amon-san said:
no, i know how it should look like because it worked fine on another device.
there is was rather dim but legible. took quite a lot of time to finish.
on my new device it really just quickly rebooted without doing any work.
Click to expand...
Click to collapse
I finally got it working using magisk v14 instead of v15.
Works great with v14.