Related
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 xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Info
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Geeks Empire said:
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Click to expand...
Click to collapse
Whoa! Don't tell him to wipe everything in the advanced wipe menu, that'll wipe the internal storage too which is completely unnecessary.
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
Which partitions are you backing up when creating the nandroid with TWRP?
Heisenberg said:
Which partitions are you backing up when creating the nandroid with TWRP?
Click to expand...
Click to collapse
System, data, boot - Installing the kernel made no difference, the device still corrupted on reboot. and then sometimes at least twice it has soft-bricked
Geeks Empire said:
Wipe everything > Advance Wipe Phone in recovery
Reinstall CM13 through Recovery and don't flash another kernel
:good:
Click to expand...
Click to collapse
Already tried it mate, a number of times. no joy.
Xtra-arrow said:
Hello xda community!
I received the nexus 6p christmas and after a few hours playing with it, I unlocked, installed twrp and installed cm13. I then installed ak kernal. My phone installs both fine and runs as normal without any FC. Then this is where it gets weird. When I had my new rom and kernal all set up. I go into TWRP and create a backup. I restart and I'm bootlooping. It tells me my device is corrupt. It did this with the original backup of stock rom, cm13, with and without ak kernal installed... and then sometimes my phone will soft-brick (gets stuxk on google logo) I really love cm engine as I habe a theme. But I'm unsure what is happening to my phone.
Any help is appreciated! - thanks.
Click to expand...
Click to collapse
The bootloader message won't go away until you lock the bootloader. Its just there as a warning to you in case you did not unlock your phone. As for CM I'm sure there are still many bugs to be worked out. I know I'm going to wait before Flashing it until I see people enjoying it as a daily driver. There are some great devs here in the n6p forums though so I recommend checking out some other ROMs too.
XxMORPHEOUSxX said:
The bootloader message won't go away until you lock the bootloader. Its just there as a warning to you in case you did not unlock your phone. As for CM I'm sure there are still many bugs to be worked out. I know I'm going to wait before Flashing it until I see people enjoying it as a daily driver. There are some great devs here in the n6p forums though so I recommend checking out some other ROMs too.
Click to expand...
Click to collapse
i understand the boot message and CM - i have tried other roms too. i'm not the only one who is getting bootloops on every rom. not sure what to do mate. it says corrupted then boot loops upon restart
Xtra-arrow said:
i understand the boot message and CM - i have tried other roms too. i'm not the only one who is getting bootloops on every rom. not sure what to do mate. it says corrupted then boot loops upon restart
Click to expand...
Click to collapse
Maybe this will be helpful. I think you have the red level warning like this user. Seems like the exact same situation.
http://forum.xda-developers.com/showthread.php?p=64403982
Turns out it isn't bootlooping. Its taking at least 3 minutes to turn on. It looks like bootlooping. BUt if finally loaded. After doing my uninstalling of aomw system apps. Its rebooted and keeps optimising apps. 2-4 then restarts and does same
Info
Heisenberg said:
Whoa! Don't tell him to wipe everything in the advanced wipe menu, that'll wipe the internal storage too which is completely unnecessary.
Click to expand...
Click to collapse
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Geeks Empire said:
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Click to expand...
Click to collapse
No it isn't necessary to wipe the userdata partition. No modifications are stored in the userdata partition. It would only be necessary to wipe system, data, cache, and dalvik cache. And probably flash the vendor partition too. Not userdata though.
I had a similar problem when I botched a SU flash, same warning then it would take forever to boot, then the rom would degrade over the next several minutes. I know its not fun to start over, but it was the only thing that cleared all the problems. I didn't want to take more time finding another solution when going back to stock is so simple with this device. Follow the instructions in step #11 of Heisenberg's guide (great guide, I link it to friends a lot). Then start again, I know, not what you wanted to hear. Hope this helps!
I am also in agreement with Heisenberg in regards to the userdata partition.
Geeks Empire said:
It s necessary to Wipe everything when don't know which modification cause the problem.
+ Recovering the backup also not working for this situation.
@Xtra-arrow
Can u explain step-by-step what u did so far
more detail = better help
:good:
Click to expand...
Click to collapse
Thank you very much for replying. I have found the root of the cause but no solution. Uninstalling or disabling system apps will cause my phone to go into a "optimising apps" boot loop on the next restart. What do you think? ++ every restore I make on twrp either soft bricks or bootloops. Crazy!
Info
Xtra-arrow said:
Thank you very much for replying. I have found the root of the cause but no solution. Uninstalling or disabling system apps will cause my phone to go into a "optimising apps" boot loop on the next restart. What do you think? ++ every restore I make on twrp either soft bricks or bootloops. Crazy!
Click to expand...
Click to collapse
If you are sure about reason Forget ur Backups.
you should completely install Stock Kernel, Rom, Boot.img >> Back to Stock
But If I remember correctly u did this before...
I just have to say Retry Also Install and use Nexus Root Toolkit
:good:
I have reinstalled original stock files from google. I've wiped everything numerous times. Installed ROMs just after. It took me a while but I think it comes down to the system apps. I'm running a custom ROM, cm13 and my phone is running fine. I know if I was to delete all the unwanted apps off my phone, on next reboot it will try and optimise apps, finish. Says starting apps... Then reboots. Follows the same process.
Xtra-arrow said:
I have reinstalled original stock files from google. I've wiped everything numerous times. Installed ROMs just after. It took me a while but I think it comes down to the system apps. I'm running a custom ROM, cm13 and my phone is running fine. I know if I was to delete all the unwanted apps off my phone, on next reboot it will try and optimise apps, finish. Says starting apps... Then reboots. Follows the same process.
Click to expand...
Click to collapse
Can I ask what gapps are you using? Are you using your google account to recover your apps, or are starting fresh each time?
Sent from my Nexus 6P using Tapatalk
Thanks for your reply. I've actually now narrowed itnright down to a few apps, maybe gapps. Sound recorder, voice recorder app and the google app. Either one or more of these cause my optimising apps bootloop.
Hey everyone I know you all probably get fed up helping noobs out and I do apologize in advance but have no idea what to do. My daughter has had gt-i9505 for a year and a half now she had an update about a week ago that she did. And now the phone was having sound problems and seems very unstable not sure if update has anything to do with it. Looked around the net tried a few different things did nothing serious just cleaned headphone jack and wiped cache nothing seemed to work. Just to say the phone was on 5.0.1 Now she has wanted me to root and install philz touch recovery for a while now but didn't really want to incase something went wrong. So given that all these problems were happening I decided I would do it for her and It all went smoothly so then I put new rom on it for her and that seemed fine to but sound problem still there and still seems very unstable is there any suggestions you guys can think of to fix it, would be greatly appreciated CHEERS :good:
Try flashing back to a completely stock rom using Odin.
Stock ROMs can be downloaded from sammobile.com.
Your best bet is to odin restore, if issue still pertains, then you have a problem in hardware, if you don't want to restore, then root device flash twrp, and factory reset there, if you have further questions, Google rooting flashing and bootloaders.
Just to say thanks to you guys I think back to stock is the only way cheers
Hey everyone just to say i have flashed back to stock now but no change even tried to update and still no sound,I even found this thread http://forum.xda-developers.com/showthread.php?t=2612167 and tried what they said and know go just notice now when i hit the volume control at all it crashes the phone. But if it was a hardware problem would it play music on the samsung logo screen on start up? any other idea of where to go from here would be great CHEERS AGAIN
Try a stock android based ROM.
Darth Vader said:
Try a stock android based ROM.
Click to expand...
Click to collapse
Can i try an android based ROM from where i'm at now or do i have to root again?
The phone is running the latest stock rom? Was it factory reset before booting for the first time? Possible hardware issue?
Sorry just a question is Cyanogenmod an android based stock rom?
audit13 said:
The phone is running the latest stock rom? Was it factory reset before booting for the first time? Possible hardware issue?
Click to expand...
Click to collapse
No its not running the latest stock rom i went back to 4.4.2 because the latest stock rom is where the problem seemed to start in the first place. And yes i did a wipe data/factory reset before restart.
eireusa said:
Sorry just a question is Cyanogenmod an android based stock rom?
Click to expand...
Click to collapse
Yup!You can try Viper4android, its a mod for audio and is really awesome.I'm pretty sure it can fix the issue
Here's the link: http://forum.xda-developers.com/showthread.php?t=2191223
It requires root.
Hey guys hypothetically if it was a hardware problem and i wanted to get it fixed is it hard to reset the knox counter?
Still no luck it seems to have gotten worse touch wiz has stopped and wifi won't turn on what the hell is happening?
I would try flashing the latest stock rom and perform a factory wipe before booting the rom for the first time.
audit13 said:
I would try flashing the latest stock rom and perform a factory wipe before booting the rom for the first time.
Click to expand...
Click to collapse
OK now i get what your saying before it starts, but do you not have to let it boot up for Odin to say pass and turn green?
Open Odin, uncheck everything except f.reset time. Flash the rom, when you see the word reset in the status window, remove cable from the phone, remove battery, wait 5 seconds, insert battery, use button combination to boot into stock recovery, factory wipe, and reboot.
audit13 said:
Open Odin, uncheck everything except f.reset time. Flash the rom, when you see the word reset in the status window, remove cable from the phone, remove battery, wait 5 seconds, insert battery, use button combination to boot into stock recovery, factory wipe, and reboot.
Click to expand...
Click to collapse
OK got it, I will try that hour of a download of sammobile.com thank you for your patience
Let us know how it goes. I suggested flashing a stock rom and wiping because, if it still doesn't work properly, it could be a hardware issue.
Good luck.
eireusa said:
Hey everyone I know you all probably get fed up helping noobs out and I do apologize in advance but have no idea what to do. My daughter has had gt-i9505 for a year and a half now she had an update about a week ago that she did. And now the phone was having sound problems and seems very unstable not sure if update has anything to do with it. Looked around the net tried a few different things did nothing serious just cleaned headphone jack and wiped cache nothing seemed to work. Just to say the phone was on 5.0.1 Now she has wanted me to root and install philz touch recovery for a while now but didn't really want to incase something went wrong. So given that all these problems were happening I decided I would do it for her and It all went smoothly so then I put new rom on it for her and that seemed fine to but sound problem still there and still seems very unstable is there any suggestions you guys can think of to fix it, would be greatly appreciated CHEERS :good:
Click to expand...
Click to collapse
Your daughter seems to know more than the average one Either that or kids just grow up fast these days!
It's highly unlikely that a software update would interfere with the phone's sound imo. How was the update done, e.g. wifi?
Me thinks your problem is hardware related. Also, you mentioned something about downgrading from 5.0.1 to 4.4. This might have something to do with your sound woes.
And then, once root counter has been tripped, there is no way to un-flag it. I believe there might be a way "trick" the counter to show "zero" but I haven't personally ever bothered to try it out.
Personally, I think it's the phone's hardware :good:
Hope you didn't get too much conflicting answers.
thundastruck said:
Your daughter seems to know more than the average one Either that or kids just grow up fast these days!
It's highly unlikely that a software update would interfere with the phone's sound imo. How was the update done, e.g. wifi?
Me thinks your problem is hardware related. Also, you mentioned something about downgrading from 5.0.1 to 4.4. This might have something to do with your sound woes.
And then, once root counter has been tripped, there is no way to un-flag it. I believe there might be a way "trick" the counter to show "zero" but I haven't personally ever bothered to try it out.
Personally, I think it's the phone's hardware :good:
Hope you didn't get too much conflicting answers.
Click to expand...
Click to collapse
No had my doubts about the update myself it was done over wifi I think she said it was one of the lollipop updates. Now regarding the downgrading from 5.0.1 the sound problem had already started on 5.0.1 only thing I done from that point forward was to root it an put philz recovery on it and then tried a custom rom to see if that would help which it did'nt sound prob still there, after that i was advised to try reverting back to stock then i downgraded to 4.4.2 stock to see if that would help no luck, just a question when i was rooting i was reading about triangle away does that not reset the counter?
My moto x pure keeps on rebooting and I think it is bootloader related as I accidentally pressed on the restart bootloader option in fastboot and my issues began since. I tried flashing 3 different roms since that and it still does the same thing, open for a few seconds then go to the ' Warning bootloader unlocked screen' boots into the rom and repeats. If anyone can provide any help i will really appreciate it since I can't find any solution.
Philo0o said:
My moto x pure keeps on rebooting and I think it is bootloader related as I accidentally pressed on the restart bootloader option in fastboot and my issues began since. I tried flashing 3 different roms since that and it still does the same thing, open for a few seconds then go to the ' Warning bootloader unlocked screen' boots into the rom and repeats. If anyone can provide any help i will really appreciate it since I can't find any solution.
Click to expand...
Click to collapse
Try flashing stock firmware.
yk1999 said:
Try flashing stock firmware.
Click to expand...
Click to collapse
is there any other solution?? If not how do I flash stock rom?
Philo0o said:
is there any other solution?? If not how do I flash stock rom?
Click to expand...
Click to collapse
I can't understand what the problem is but flashing stock firmware solves many problem.
Is there something wrong with bootloader flashing stock firmware with bootloader can solve it.
Is your phone model xt1575 . If so then read this
https://forum.xda-developers.com/mo...de-return-to-stock-relock-bootloader-t3489110
What else did you do in the bootloader? This doesn't "just happen" by doing a reboot bootloader...
Nevermind, I missed the part where you tried to flash 3 different ROMs somehow... Many custom ROMs change the data partition to f2fs, use TWRP to change it to ext4 and reflash a ROM, or preferably reflash stock.
acejavelin said:
What else did you do in the bootloader? This doesn't "just happen" by doing a reboot bootloader...
Nevermind, I missed the part where you tried to flash 3 different ROMs somehow... Many custom ROMs change the data partition to f2fs, use TWRP to change it to ext4 and reflash a ROM, or preferably reflash stock.
Click to expand...
Click to collapse
Hey ace, is f2fs actually prone to crashes? And are there performance improvements? I run handbag 2.3.3 and their thread says there should be no corrupting of data or issues with f2fs, but I wondered if I would see improvements with it?
Spencervb256 said:
Hey ace, is f2fs actually prone to crashes? And are there performance improvements? I run handbag 2.3.3 and their thread says there should be no corrupting of data or issues with f2fs, but I wondered if I would see improvements with it?
Click to expand...
Click to collapse
No, it's fine... just some ROM's, or more accurately some kernels, don't support it... such as stock Marshmallow.
In theory it's better for flash based devices, but in real world testing with Android devices it makes little difference.
acejavelin said:
No, it's fine... just some ROM's, or more accurately some kernels, don't support it... such as stock Marshmallow.
In theory it's better for flash based devices, but in real world testing with Android devices it makes little difference.
Click to expand...
Click to collapse
Okay thanks so much! I know there were issues with previous issues of handbag but those were fixed so it should be fine, but I guess there's no reason to change, thanks!
acejavelin said:
What else did you do in the bootloader? This doesn't "just happen" by doing a reboot bootloader...
Nevermind, I missed the part where you tried to flash 3 different ROMs somehow... Many custom ROMs change the data partition to f2fs, use TWRP to change it to ext4 and reflash a ROM, or preferably reflash stock.
Click to expand...
Click to collapse
I see, how do I change the data partition? All the tutorials I see are ext4 to f2fs conversion and not vice versa. Thank you
Philo0o said:
I see, how do I change the data partition? All the tutorials I see are ext4 to f2fs conversion and not vice versa. Thank you
Click to expand...
Click to collapse
Same thing. Exact same thing. TWRP -> wipe -> advanced wipe -> change data format and then change to ext4
Spencervb256 said:
Same thing. Exact same thing. TWRP -> wipe -> advanced wipe -> change data format and then change to ext4
Click to expand...
Click to collapse
I tried changing to both and now it doesn't even boot into the system, just stuck on the 'warning bootloader unlocked screen'
Philo0o said:
I tried changing to both and now it doesn't even boot into the system, just stuck on the 'warning bootloader unlocked screen'
Click to expand...
Click to collapse
You have to reflash the stock image after changing the partition type.
acejavelin said:
You have to reflash the stock image after changing the partition type.
Click to expand...
Click to collapse
Thank you I flashed the stock recovery and it works okay now. One last thing, does this mean I can't flash custom roms anymore?
I had this problem with a few customer ROMs I tried. Using Resurrection Remix 5.8.4 now and have not had that problem.
https://forum.xda-developers.com/mo...unofficial-resurrection-remix-v5-8-3-t3637204
My phone keeps resetting even when trying to get into recovery. When i'm in system it's like somebody is randomly pushing power button. Is there something i can do with it? I tried flashing stock ROM and it's still the same.
I've flashed numerous roms to my device and have decided that none are as good as stock. Yes, they may have all the bells and whistles, however, with those come instability, random reboots, battery drain, lag, etc.... Stock, for me at any rate, seems to work best. I'm also surprised that nobody appears to have really capitalised on the recently released kernel source code from Motorola for this device.
lmulli said:
I've flashed numerous roms to my device and have decided that none are as good as stock. Yes, they may have all the bells and whistles, however, with those come instability, random reboots, battery drain, lag, etc.... Stock, for me at any rate, seems to work best. I'm also surprised that nobody appears to have really capitalised on the recently released kernel source code from Motorola for this device.
Click to expand...
Click to collapse
I think you didn't flash any of this:
RRemix 24.04 + handbag or simple kernel,
RRemix 14.08 + any kernel,
Dirty Unicorns any build.
dzidexx said:
I think you didn't flash any of this:
RRemix 24.04 + handbag or simple kernel,
RRemix 14.08 + any kernel,
Dirty Unicorns any build.
Click to expand...
Click to collapse
I've tried them, and as stated above, none are as stable/smooth as stock. Fact. You can quote every custom rom and kernel combo you like, it doesn't change that fact.
lmulli said:
I've flashed numerous roms to my device and have decided that none are as good as stock. Yes, they may have all the bells and whistles, however, with those come instability, random reboots, battery drain, lag, etc.... Stock, for me at any rate, seems to work best. I'm also surprised that nobody appears to have really capitalised on the recently released kernel source code from Motorola for this device.
Click to expand...
Click to collapse
What? Link us plz
I bought oneplus 5 yesterday,it was working perfect in store and when I came home wifi stopped working (OOS 4.5.8).I manually updated it to 4.5.11 and wifi now works fast and perfect.But whenever I flash any custom roms wifi doesn't work at all not even on latest hydrogen OS.Can any one help with this problem? thnks
Dewang p3100 said:
I bought oneplus 5 yesterday,it was working perfect in store and when I came home wifi stopped working (OOS 4.5.8).I manually updated it to 4.5.11 and wifi now works fast and perfect.But whenever I flash any custom roms wifi doesn't work at all not even on latest hydrogen OS.Can any one help with this problem? thnks
Click to expand...
Click to collapse
Maybe it's related with the modem, look for that and get some information how to flash the correct one.
I don't know what custom ROMs you had problems with but some need specific firmware to be flashed in order for things to work right. Usually that information is somewhere in the description of the ROM features and sometimes download links are also included. When you flashed custom ROMs did you clean flash them? You need to wipe the cache, system and data when changing ROMs. You also might need to flash back to stock before flashing some custom ROMs but if that's the case it should say that in the instructions for the ROM.
jhs39 said:
I don't know what custom ROMs you had problems with but some need specific firmware to be flashed in order for things to work right. Usually that information is somewhere in the description of the ROM features and sometimes download links are also included. When you flashed custom ROMs did you clean flash them? You need to wipe the cache, system and data when changing ROMs. You also might need to flash back to stock before flashing some custom ROMs but if that's the case it should say that in the instructions for the ROM.
Click to expand...
Click to collapse
can you tell me correct firmware for lineageOS 15
Dewang p3100 said:
can you tell me correct firmware for lineageOS 15
Click to expand...
Click to collapse
if you are trying to use lineageos 15 for your daily driver you are insane. Just use stock oxygen or freedomOS. Oreo is not official on OP5 yet you cant expect to use it and have it be flawless. Most apps i use dont even run on Oreo when i tried it. just revert.
OcazPrime said:
if you are trying to use lineageos 15 for your daily driver you are insane. Just use stock oxygen or freedomOS. Oreo is not official on OP5 yet you cant expect to use it and have it be flawless. Most apps i use dont even run on Oreo when i tried it. just revert.
Click to expand...
Click to collapse
op5 is not my daily driver,I have youtube channel where I review custom roms I bought this phone just for that (search Dewang Rocker on youtube).Can you help me with wifi on LOS15? i got it working on 14.1 by flashing 4.5.10 firmware but no luck in 15.
Thanks for the info!
Dewang p3100 said:
op5 is not my daily driver,I have youtube channel where I review custom roms I bought this phone just for that (search Dewang Rocker on youtube).Can you help me with wifi on LOS15? i got it working on 14.1 by flashing 4.5.10 firmware but no luck in 15.
Click to expand...
Click to collapse
Yes im sure the answer is actually as simple as wiping the device completely. Wipe all partitions and then format data. When formatting data if you forget to fix your internal storage rights you cant download anything so make sure you go to advanced then fix contents in twrp before installing stock oxygen. Once it is done boot the phone and let it go and try to connect to wifi. If you can then wipe your phone out and reinstall LAOS 15
OcazPrime said:
Yes im sure the answer is actually as simple as wiping the device completely. Wipe all partitions and then format data. When formatting data if you forget to fix your internal storage rights you cant download anything so make sure you go to advanced then fix contents in twrp before installing stock oxygen. Once it is done boot the phone and let it go and try to connect to wifi. If you can then wipe your phone out and reinstall LAOS 15
Click to expand...
Click to collapse
Just tried this while installing ViperOS v3.0. No Luck...
This also happens when trying to install other roms such as AICP and Slimrom 7.
Any ideas?
ckrummi said:
Just tried this while installing ViperOS v3.0. No Luck...
This also happens when trying to install other roms such as AICP and Slimrom 7.
Any ideas?
Click to expand...
Click to collapse
Yea use twrp 3.1.1-1 to install the latest stock 4.5.13. make sure you wipe everything and re format everything. Just drop your necessary files onto a secondary source like a pc or google drive. After u wipe that stuff out reboot back to recovery. Go to advanced on the main menu and and fix contents. Do not skip this step or you wont have storage permissions which is necessary for installing roms properly. After that ensure everything is mounted on the mount section in the main menu. U should see a "firmware" option added as well, be sure that is checked too. Install stock 4.5.13 and see if wifi works. It should, if not it could be a hardware issue.
---------- Post added at 11:02 PM ---------- Previous post was at 10:53 PM ----------
ckrummi said:
Just tried this while installing ViperOS v3.0. No Luck...
This also happens when trying to install other roms such as AICP and Slimrom 7.
Any ideas?
Click to expand...
Click to collapse
Gonna do a second post for another manner on this topic. Just use stock. Aint nothing wrong with it, its actually beautiful. Dont listen to whoever says its bloated or whatever. Its all allowed to be disabled if u dont want it. Stock rom with stock kernel is far better than any rom or kernel out there. Think of it this way, you have a device that an entire company made sure the software worked on that specific device as opposed to a single person or a group of 5 or so people made software that needs to run on any device. IE Lineage/Aosp and whatever customized stock oxygenos is out there. I use stock and stock kernel with kernel adiutor to disable some kernel features i dont need like input boost for example to save a lot of juice. I always test certain scripts for stock oxygen on the 3t and the 5 to maximize battery. I play with linux a lot so i merely tweak a few settings and turn some stuff off and on and run whatever for about a week to see which script works best for battery life and performance. Gotta say i cant pull certain SoTs or performance tests off stock because of instability or them being simply inferior. Flashing a bunch of things is cool but try to simmer down and come back to stock after youve exhausted all possibility of gaining more battery time.
I do have WiFi on stock roms and all OOS roms, just a heads up. Every time I flash them I am good on WiFi.
I'll be sure to check out the fix contents button in recovery.
So to flash CM roms and AOSP I should do this...
Flash Stock 4.5.13 > wipe > format > fix contents> check mounts (firmware checked) > flash custom roms
ckrummi said:
I do have WiFi on stock roms and all OOS roms, just a heads up. Every time I flash them I am good on WiFi.
I'll be sure to check out the fix contents button in recovery.
So to flash CM roms and AOSP I should do this...
Flash Stock 4.5.13 > wipe > format > fix contents> check mounts (firmware checked) > flash custom roms
Click to expand...
Click to collapse
:good: