Database Users

Stuck on Samsung Custom Screen w/ Custom ROM

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.

Weird issues after kitkat upgrade

Was happily on CM and for some reason decided to try stock kitkat. Did everything via tutorial and all went all well - but been getting some strange issues which has made my phone unusable.
When i press vol up/down it takes ten seconds to pop up. Sound does not work at all whether calling/playing music. Settings f/c when I attempt to click the sound menu. I believe everything else is working fine.
Tried reflashing stock firmware countless times... Tried flashing numerous custom 4.4 roms.
Australian bought phone if it makes any difference.
Please help as Im stuck using a spare iphone 4 and its killing me! haha.
Thanks,

Riimez said:
Was happily on CM and for some reason decided to try stock kitkat. Did everything via tutorial and all went all well - but been getting some strange issues which has made my phone unusable.
When i press vol up/down it takes ten seconds to pop up. Sound does not work at all whether calling/playing music. Settings f/c when I attempt to click the sound menu. I believe everything else is working fine.
Tried reflashing stock firmware countless times... Tried flashing numerous custom 4.4 roms.
Australian bought phone if it makes any difference.
Please help as Im stuck using a spare iphone 4 and its killing me! haha.
Thanks,
Click to expand...
Click to collapse
Let's start from the beginning.
Can you describe your method of flashing in case you are doing something wrong? Please describe as much information as possible.
What is your phone model?

y2kkingboy said:
Let's start from the beginning.
Can you describe your method of flashing in case you are doing something wrong? Please describe as much information as possible.
What is your phone model?
Click to expand...
Click to collapse
9005. sorry it was a couple of days ago so I dont really remember. I flashed a 4.4 bootloader (standalone) then tried flashing a 4.4 rom i believe it was sweetrom.

Riimez said:
9005. sorry it was a couple of days ago so I dont really remember. I flashed a 4.4 bootloader (standalone) then tried flashing a 4.4 rom i believe it was sweetrom.
Click to expand...
Click to collapse
I believe the best thing to do now is to flash stock ROM and make sure to full wipe everything even internal memory.
If you have external memory, back up what ever you think necessary to it, the remove it from the device and keep it out.
That clean start well give you a good indication whether the problem is based on a bad flash or there is something wrong with the device.
If everything is running smoothly, we will see about flashing custom ROM.

y2kkingboy said:
I believe the best thing to do now is to flash stock ROM and make sure to full wipe everything even internal memory.
If you have external memory, back up what ever you think necessary to it, the remove it from the device and keep it out.
That clean start well give you a good indication whether the problem is based on a bad flash or there is something wrong with the device.
If everything is running smoothly, we will see about flashing custom ROM.
Click to expand...
Click to collapse
Yep its what ive done, reflashed stock completly and removed sd card. Still no dice - running complete stock 4.4 still with this problem.
Could this be an EFS problem?

If it were an efs problem you wouldn't even boot in most cases.
Can you describe how you flashed stock ROM? Maybe you did it wrong.
Sent from my SM-N9005 using Tapatalk

Sorry to hear that..base on my experienced happened also on my S4..luckily still under warranty..have to wait for 2 weeks...company says faulty mother board and speaker. Hope this helps....
Sent from my SM-N900 using xda premium

Riimez said:
Was happily on CM and for some reason decided to try stock kitkat. Did everything via tutorial and all went all well - but been getting some strange issues which has made my phone unusable.
When i press vol up/down it takes ten seconds to pop up. Sound does not work at all whether calling/playing music. Settings f/c when I attempt to click the sound menu. I believe everything else is working fine.
Tried reflashing stock firmware countless times... Tried flashing numerous custom 4.4 roms.
Australian bought phone if it makes any difference.
Please help as Im stuck using a spare iphone 4 and its killing me! haha.
Thanks,
Click to expand...
Click to collapse
NEE region? - if so it has issues with 4.4.2, @nex7er had the same issues, and if you're using SweetROM I believe he pm'd not-i the fix for it. -- It can be fixed though.

Maybe completely wipe it (System, Data and all) and then Flash stock with Odin?

After kitkat upgrade.. if i use camera app such as camera 360 Or picsart, i can't save my photo to sdcard. It's error, Has anyone had or know how to resolve this problem???

Blancos4Lyf said:
Maybe completely wipe it (System, Data and all) and then Flash stock with Odin?
Click to expand...
Click to collapse
Yep. Still no dice.

Riimez said:
Yep. Still no dice.
Click to expand...
Click to collapse
I did post the reason on the last page what I think it might be...... if you're in a Nordic region or even have a nordic model it's a common problem, if you search around you'll see others that have the same issue (notably ne7xer). -- If it's not that, then it's a warranty job due to faulty HW
EDIT: you could try a complete wipe including re-partitioning, but that's a bigger job that you'd want to do in all honesty.

radicalisto said:
I did post the reason on the last page what I think it might be...... if you're in a Nordic region or even have a nordic model it's a common problem, if you search around you'll see others that have the same issue (notably ne7xer). -- If it's not that, then it's a warranty job due to faulty HW
EDIT: you could try a complete wipe including re-partitioning, but that's a bigger job that you'd want to do in all honesty.
Click to expand...
Click to collapse
Could be my last option considering knox is tripped..
Got a link to a tutorial for re-partitioning?

Grab a PIT file for your device; - then you flash firmware with Odin / PIT file. - I have never done it, nor do I fancy doing it, but have a read (journeyman posted asking how and done it, it's in this section Q+A) - I can never remember whether you flash the PIT first then the firmware or both together. I wouldn't want to hazard a guess just in case though.
But if you've tripped KNOX, then yes, seems like it could be your last option, unless you have tried some various custom ROMs? ( I know sweetROM seems to be the master fix for any issues peple have on KK atm) could just be a stock issue currently that will more than likely get a fix at some point.
EDIT As yours is an AU phone, possible it could be a HK model? - from KOGAN? I know some AU users have had HK models from them.
EDIT2: When I flashed HAL ROM, @theresident stated in his how to OP that we needed to format /system during install - It's possible this may also fix it, but that wipes your entire system obviously and *IF* it doesn't boot up you then have issues
EDIT3 : quote from HAL ROM OP
Instalation:
1. Copy the zip to the phone
2. Reboot to Recovery/CWM
3. Wipe Data/Factory Reset
4. Wipe Cache
5. Wipe Dalvik Cache
6. Mounts and Storage then click "Format /System" (This won't delete any of your data)
7. Install.. wait one minute and ROCK !!!
Click to expand...
Click to collapse

crazy_777 said:
After kitkat upgrade.. if i use camera app such as camera 360 Or picsart, i can't save my photo to sdcard. It's error, Has anyone had or know how to resolve this problem???
Click to expand...
Click to collapse
You are hijacking.
Anyway,
1. Install es file manager or any file reader with root.
2. navigate to /System/etc/permissions
3. open "platform.xml" file to edit
4. look for the stack that has "WRITE_EXTERNAL_STORAGE"
you will find something like <group gid="sdcard_r" />
5. make sure these lines are there, if not, add them
<group gid="sdcard_rw" />
<group gid="media_rw" />
That's it

[Q] Freezing, rebooting, and can't flash stock rom (reverts to previous state)

Okay, so I feel like I've looked everywhere and tried everything for this problem with my Nexus 7. The closest thing I found was this:
(Google: Nexus 7 2012 rebooting reverts back to previous state)(I can't post outside links as I am a new member)
and there was no followup reply, and the thread was closed.
Here's my problem (I want to be very detailed in case I missed something):
I've had Cyanogenmod 11 on my Nexus 7 for a long time (I think I started with M1 release). I recently installed the M7 release after previous nightly and it was working so smooth that I had finally decided there was no need to install nighties anymore. Everything was going fine until the night after when I noticed it kept rebooting, so I reverted it back to the nightly I had before (June 11th?) because I assumed it was probably something bad with the update. Except it did the same thing, rebooting after a couple minutes, which is weird because it never did that with this nightly. There was never enough time to download the nightlies before it reboots so I tried downloading them on my laptop and then just transferring them to my nexus via usb. I put it in the cmupdate folder so that I could quickly go to settings and press install (as it can see the update from there). It rebooted to install, but it went into cwm with what appears that nothing happened, and I usually never see cwm when updating this way. So I figured, while I'm here, I could just "install zip" and find that zip I just transferred and install, right? Nope. The zip mysteriously vanished, yet the other two updates were still there (M7 and the previous nightly). So I just rebooted just to try the process again, maybe the file transfer didn't work. Same thing happened. So I went to cwm and tried wiping cache, nothing. Wiped dalvik cache, nothing. So I went and did it, wiped data/factory reset, that did NOTHING, as in I rebooted and everything was still there.
So I got to the point where I just wanted to see if I could just revert back to stock so I have a place to start from, maybe contemplate on just staying there for a while where there shouldn't be problems. So I got that all set up with fastboot, got the latest 4.4.3 image, unarchived until I could get to the flashall.bat I ran that and it was successful. Okay now I can just boot into that, right? Suddenly I see the cyanogenmod boot graphic. What happened? Even all of my apps are still there. Still freezing and rebooting.
I tried reverting to stock manually by erasing then formating everything that I can, flashed bootloader (grouper 4.23), flashed zip, locked bootloader, unlocked bootloader (trying to erase as much as I can). This did nothing, still cyanogenmod. I tried a third time while rebooting to bootloader with each step. Nothing. I tried doing a factory reset within cyanogenmod, but when I press the "erase everything" button it doesn't lead anywhere, so I could never get that to start the process. I also tried doing the erasing and formatting from cwm (which isn't being overwritten, as it seems, by all the attempts at flashing stock?), nothing.
I was curious. I uninstalled Netflix because it was right there in my dock. Then I rebooted myself. When it came back up, Netflix was still there. I tried various things, also going back to locking the bootloader and rebooting the bootloader, it still said it was unlocked. So I came to the conclusion that literally nothing was being written or committed to the sdcard no matter what I do.
I did some more research and found that article up top. So I tried uninstalling some apps because it said it may have something to do with a third-party app misbehaving (seems a bit extreme, I'll do it anyways), but there's never enough time to erase everything before it reboots. It also said to try to get it into safemode. I think I might have gotten there once but it still rebooted (which makes me think that it didn't get to safemode), the rest of the times it wouldn't even get to the lockscreen.
What I'm currently attempting is to see if I can get it into safemode, or I'm trying to uninstall or stop/clear data for every single app with an intentional reboot each time.
Anyone got any idea what's going on? Is it maybe a bad sector, or worse, bad sdcard?

Gonna bump this. Still no luck on my part.
Anyone have any idea?
Perhaps somehow something got triggered to prevent anything being written to the sdcard? (Kinda like the lock switch on actual sdcards?) Is everything I've been doing going straight to memory since everything reverts back after a reboot? That's the only explanation I can think of.
Perhaps there's more I could try. I'm only moderately knowledgeable with things like fastboot and roms, so maybe someone with more experience might have more insight. Please, chime in.
Thanks in advance,
JM

Same problem here....

Flash factory image

USBhost said:
Flash factory image
Click to expand...
Click to collapse
Although you flash the factory image, the previously ROM boots again, that is precisely the problem.

Amd64bits said:
Although you flash the factory image, the previously ROM boots again, that is precisely the problem.
Click to expand...
Click to collapse
O ok

Amd64bits said:
Same problem here....
Click to expand...
Click to collapse
Curious, how did you get to the point where it boots the previous rom? Same as me or something else? Are you using cyanogenmod? I want to try and rule out some possibilities.
I'm at the same point since last time. Trying to nuke the hell out of cyanogenmod but it won't go away!
This just outright baffles me!

Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash

USBhost said:
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
Click to expand...
Click to collapse
I have clockworkmod recovery v6.0.4.3 probably from installing cyanogenmod, however formating any of those partitions does literally nothing. I'm not sure what file system it formats it to, but the process seemed too quick for a full format.
I cannot flash a different recovery because... well... it doesn't remember me flashing a recovery (even when nothing "fails" when flashing). So I'm stuck with whatever is already on my internal storage. Nothing is writing to the sdcard, and nothing is being deleted.

violoncellemuse said:
I have clockworkmod recovery v6.0.4.3 probably from installing cyanogenmod, however formating any of those partitions does literally nothing. I'm not sure what file system it formats it to, but the process seemed too quick for a full format.
I cannot flash a different recovery because... well... it doesn't remember me flashing a recovery (even when nothing "fails" when flashing). So I'm stuck with whatever is already on my internal storage. Nothing is writing to the sdcard, and nothing is being deleted.
Click to expand...
Click to collapse
Boot twrp temporary from the bootloader

USBhost said:
Boot twrp temporary from the bootloader
Click to expand...
Click to collapse
I'm unfamiliar with this, how do I boot temporarily?

violoncellemuse said:
I'm unfamiliar with this, how do I boot temporarily?
Click to expand...
Click to collapse
1 set getting on computer

Okay, so I was able to boot twrp and change the partitions to f2fs. No dice. Still cyanogenmod.

violoncellemuse said:
Okay, so I was able to boot twrp and change the partitions to f2fs. No dice. Still cyanogenmod.
Click to expand...
Click to collapse
then you did boot twrp temporary

USBhost said:
then you did boot twrp temporary
Click to expand...
Click to collapse
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?

violoncellemuse said:
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
Click to expand...
Click to collapse
thats not normal
ok i know why its a new cyanogenmod feature
no matter what you do cyanogenmod is now unkillable lol
this is such a strage problem

USBhost said:
thats not normal
ok i know why its a new cyanogenmod feature
no matter what you do cyanogenmod is now unkillable lol
this is such a strage problem
Click to expand...
Click to collapse
Do you have any more info? Perhaps my sdcard is "softlocked" or something.

violoncellemuse said:
Do you have any more info? Perhaps my sdcard is "softlocked" or something.
Click to expand...
Click to collapse
i have been noticing CWMR is the root of all the problems
i dont sorry but your not the only one i think there are 3+ people that have this same problem
formating should have fixed it

USBhost said:
i have been noticing CWMR is the root of all the problems
i dont sorry but your not the only one i think there are 3+ people that have this same problem
formating should have fixed it
Click to expand...
Click to collapse
I do thank you for trying to help me out.
I found a thread with someone with the same problem I'd like to direct people towards: http://forum.xda-developers.com/showthread.php?t=2800064

violoncellemuse said:
Curious, how did you get to the point where it boots the previous rom? Same as me or something else? Are you using cyanogenmod? I want to try and rule out some possibilities.
I'm at the same point since last time. Trying to nuke the hell out of cyanogenmod but it won't go away!
This just outright baffles me!
Click to expand...
Click to collapse
Well, I have Paranaoid Android 4.4.4, not Cyanogen, and everything seemed ok until I installed Cloudmagic (and maybe Busybox?) that poped up a Play Store error (I don't remember which one), and suddenly all the problems began. It started to reboots, rebooted so many times that I decided to flash another ROM... but this wasn't possible.
My recovery is TWRP, so we can discard Cyanogen, ParanoidAndroid, CMW and TWRP as guilty, I think.
USBhost said:
Try this out format /system /cache /data with twrp to f2fs
If it doesn't boot then cheers you got out if the loop
Then adb sideload an f2fs ROM and kernel them flash
Click to expand...
Click to collapse
Tried that, nothing happened, still with Paranoid Android.
violoncellemuse said:
I did. I didn't know that was possible until now.
But still, changing the file system or formating anything doesn't do anything after I reboot. I even checked after I changed the file system to f2fs in twrp to see the "current file system" when changing the partitions again, but it says it's ext4 still.
I tried repairing system, which processed quickly. However, trying to repair cache and data led to an error. Perhaps this might mean something? or is this normal?
Click to expand...
Click to collapse
Same here.

Full Phone Encryption Stalling at 0%

ROM: Cloudy G3 2.0 (already posted in his thread)
Recovery: Team Win recovery v2.7.0.0
Whenever I attempt to Full Phone Encrypt it will reboot and stay at 0%. I've tried it a few times now.
It will let me reboot back to the OS so it's not even doing anything.
Due to Recovery/rom? I'd like full encryption...
Thanks for help.

@Unoid I think its the rom, but I am not sure about recovery. Also remember that if encryption fails during encrypting then bad things happen to your data. And also if you are flashing much roms then I suggest to not to encrypt, just use an password.

What stable rom will work with encryption?

I'm in the same boat -- encrypting stays at 0% and rebooting starts up normally like nothing happened. Any luck finding a stable ROM where encryption works?

Unoid said:
What stable rom will work with encryption?
Click to expand...
Click to collapse
boffo123 said:
I'm in the same boat -- encrypting stays at 0% and rebooting starts up normally like nothing happened. Any luck finding a stable ROM where encryption works?
Click to expand...
Click to collapse
Did you guys ever find a ROM that will work with encryption?

bamachevrolet said:
Did you guys ever find a ROM that will work with encryption?
Click to expand...
Click to collapse
I went back to the stock KitKat ROM. I'd still be interested in hearing if anyone gets encryption working on a custom ROM though.

I would be very interested to know a custom AOSP ROM with Encryption as well. I know it works for other phones. Is it specific to the kernal?

Android Nougat (7.0) ROMs have a freeze/constantly reboot issue

Title says it all. Nothing much else to say, but if it helps, the reboots occur more often after I install GAPPS (OpenGapps, to be specific), though I've experimented with DynamicGapps, only to be met with the same result.
Anyone else coming across this? If so, how did you solve it?

Shinuki said:
Title says it all. Nothing much else to say, but if it helps, the reboots occur more often after I install GAPPS (OpenGapps, to be specific), though I've experimented with DynamicGapps, only to be met with the same result.
Anyone else coming across this? If so, how did you solve it?
Click to expand...
Click to collapse
Nobody reporting that's kind of issue .I am using RR and Tesla and no problem.
Do clean flash and use pico gaaps.If problem exists then post on the specific ROM thread with ramoops and kmsg file ,so experts can help with reboot isuue.

Had the same problem while on AOSP EXTENDED, the rom is god damn smooth, just the freezes and the random reboots make it clear that Boi, u need to change the rom, NOW!😂😂😂

Shinuki said:
Title says it all. Nothing much else to say, but if it helps, the reboots occur more often after I install GAPPS (OpenGapps, to be specific), though I've experimented with DynamicGapps, only to be met with the same result.
Anyone else coming across this? If so, how did you solve it?
Click to expand...
Click to collapse
I had faced random reboots with most of N roms. Try changing the kernel.

adithbalan said:
I had faced random reboots with most of N roms. Try changing the kernel.
Click to expand...
Click to collapse
I've tried this, but the LateAutumn project kernel always causes bootloops.
i-AM-BoReD said:
Nobody reporting that's kind of issue .I am using RR and Tesla and no problem.
Do clean flash and use pico gaaps.If problem exists then post on the specific ROM thread with ramoops and kmsg file ,so experts can help with reboot isuue.
Click to expand...
Click to collapse
To be honest, I've seen a few people reporting the same issue. Already flashed with pico gapps, same problem. It happens with literally all Android 7+ ROMs I've seen here, including RR and Tesla. I'll just try to get the logs, thanks.
Ronnie.mac94 said:
Had the same problem while on AOSP EXTENDED, the rom is god damn smooth, just the freezes and the random reboots make it clear that Boi, u need to change the rom, NOW!😂😂😂
Click to expand...
Click to collapse
I had that problem in AOSP-OMS, Extended, RR, Tesla, CM 14.1... nothing seems to work now. But thanks anyway

@Shinuki get the logs and post to LA thread in detail. You're bootloader may be the root of the problem, which if is the reason, then is not upgraded to LP bootloader. Post dmesg and ramoops there.

iamsubhranil said:
@Shinuki get the logs and post to LA thread in detail. You're bootloader may be the root of the problem, which if is the reason, then is not upgraded to LP bootloader. Post dmesg and ramoops there.
Click to expand...
Click to collapse
Got it, but if that's the case, how can I upgrade bootloader? I flashed the MIUI 5.1 ROM recently and still got same issues

iamsubhranil said:
@Shinuki get the logs and post to LA thread in detail. You're bootloader may be the root of the problem, which if is the reason, then is not upgraded to LP bootloader. Post dmesg and ramoops there.
Click to expand...
Click to collapse
I have the same issues and I can't report becouse I never did a dmesg and a ramoops, I can't find how to do it on google, nobody told me, I know the ramoops command, but where I type it? twrp? or in the PC? becouse it keeps bootlooping and restarting
---------- Post added at 17:56 ---------- Previous post was at 17:56 ----------
Shinuki said:
Got it, but if that's the case, how can I upgrade bootloader? I flashed the MIUI 5.1 ROM recently and still got same issues
Click to expand...
Click to collapse
Is your device model 2014819?

TecnoTailsPlays said:
I have the same issues and I can't report becouse I never did a dmesg and a ramoops, I can't find how to do it on google, nobody told me, I know the ramoops command, but where I type it? twrp? or in the PC? becouse it keeps bootlooping and restarting
---------- Post added at 17:56 ---------- Previous post was at 17:56 ----------
Is your device model 2014819?
Click to expand...
Click to collapse
Yeah, it is. From Brazil, to be specific.

Shinuki said:
Title says it all. Nothing much else to say, but if it helps, the reboots occur more often after I install GAPPS (OpenGapps, to be specific), though I've experimented with DynamicGapps, only to be met with the same result.
Anyone else coming across this? If so, how did you solve it?
Click to expand...
Click to collapse
Signal Strength is good? In Android 7 signal issue is there , reboots occur when there is low or less signals

adithbalan said:
I had faced random reboots with most of N roms. Try changing the kernel.
Click to expand...
Click to collapse
Try to super clean flash. Wipe system > data > cache and dalvik. Reboot recovery and flash the roms.

ntoetsoekarno said:
Try to super clean flash. Wipe system > data > cache and dalvik. Reboot recovery and flash the roms.
Click to expand...
Click to collapse
I always clean flash, still same issue

Shinuki said:
I always clean flash, still same issue
Click to expand...
Click to collapse
Clean flash is only wipe data, cache and dalvik. Try to wipe system too, DON'T FORGET TO REBOOT RECOVERY FIRST before flash roms.

Try flashing pico or nano gapps...:good:

ntoetsoekarno said:
Clean flash is only wipe data, cache and dalvik. Try to wipe system too, DON'T FORGET TO REBOOT RECOVERY FIRST before flash roms.
Click to expand...
Click to collapse
Sorry. I always super clean flash and reboot to recovery.
udayjindal said:
Try flashing pico or nano gapps...:good:
Click to expand...
Click to collapse
I already tried both, no luck.
I honestly don't know what the issue is. A CM 14.1 ROM from October wasn't giving me this issue; same for 6.0 ROMs.