Hi everyone, I am having an issue whenever I install a touchwork rom that it will inevitably randomly reboot, or crash then reboot at least once a day. I am not going to mention any specific roms here because it has happened consistently with several of the most popular touchwork roms on this forum. I also considered the possibilty of a rogue app causing these problems, however yesterdayI installed one of my favorite roms and did not install a single third party application, to rule out that possibility. Today it just rebooted again this morning out of nowhere.
Caveat is that when I tried a 4 day trial on a AOSP rom, i had no such issues, even though i TB'ed my apps and restored everything.
Now I know an easy solution is to just stay on a non TW rom, but I happen to like several TW features and can't seem to figure out whats going on here.
Any ideas?
I'm assuming you have an i337m. I'd Odin the stock firmware and see if you have the reboot issues on it. If you don't it's most likely the rom that is causing the issue our the way you're flashing them
Sent from my Nexus 5
jd1639 said:
I'm assuming you have an i337m. I'd Odin the stock firmware and see if you have the reboot issues on it. If you don't it's most likely the rom that is causing the issue our the way you're flashing them
Sent from my Nexus 5
Click to expand...
Click to collapse
US version
theraker007 said:
US version
Click to expand...
Click to collapse
So you're on mdl firmware? Are you doing full wipes, system, data, cache and dalvik, when you're installing the roms?
Sent from my Nexus 5
jd1639 said:
So you're on mdl firmware? Are you doing full wipes, system, data, cache and dalvik, when you're installing the roms?
Sent from my Nexus 5
Click to expand...
Click to collapse
every single time. Again, this is only happening with TW roms. I've also tried stock and KT kernel with same roms.
Related
I posted this over at rootz earlier today and didn't get any bites so I figured I'd give it a shot over here.
I may be the only one in the world experiencing this problem. Looked around quite a bit and don't see any sign of others having this issue... Anyway, my N7 doesn't seem to like it when I flash a new kernel. I've tried several different kernels and when ever I flash one my display will not wake up once it times out or if I turn the display off manually. Once the screen goes dark i have to hold the power button down and reboot. I have zero issues with custom kernels as long as they are baked into the rom. I typically wipe cache and dalvic after flashing kernels...
Sent from my Galaxy Nexus using xda app-developers app
Little bump here... 130 views and not a peep... :-/
scram99 said:
Little bump here... 130 views and not a peep... :-/
Click to expand...
Click to collapse
youre experiencing "sod", which is a fairly common problem with android 4.2.1 source code(not as common on the n7 as the gnex, but common enough). do you flash the kernel with the rom or do you flash the kernel separately?
This happens after switching out the kernel on any ROM I've used. Have not flashed a different kernel at the same time I flashed a ROM. I don't think that will make a difference. I can however flash kernels over my stock rooted backup... I don't know. Just weird and bums me out being limited like this...
scram99 said:
This happens after switching out the kernel on any ROM I've used. Have not flashed a different kernel at the same time I flashed a ROM. I don't think that will make a difference. I can however flash kernels over my stock rooted backup... I don't know. Just weird and bums me out being limited like this...
Click to expand...
Click to collapse
I would just factory reset and start from scratch. Do you have any settings set like UV??
Sent from my Nexus 7 using xda premium
I have tried flashing back to stock, relocking and starting from scratch. I do not undervolt...
A few good folks in the android community had experienced similar happenings and suggested lean kernel... Flashed it earlier this evening and working like a charm.
After updating the latest KtManta kernel my nexus 10 lost its root capabilities, super user won't just work, it is just me or it is a known issue?
I've flashed the December version of the kernel afterwards and the problem prevails (ktoonsez doesn't include every kernel download link, a bad practice in my opinion)
I am on CM now and everything is working fine, I wonder if anyone has been victim to this weird issue
Sent from my Nexus 10 using Tapatalk HD
zombiegenerator said:
After updating the latest KtManta kernel my nexus 10 lost its root capabilities, super user won't just work, it is just me or it is a known issue? ...
Click to expand...
Click to collapse
I am guessing but is this a permissions issue? I've flashed KTManta a number of times including just yesterday with TWRP and never had the issue you describe. Occasionally, right after flashing a ROM or Kernel, I have seen from TWRP a "Fix Permissions" message which I always execute. Some custom ROM/Kernels flash instructions even include a "Fix Permissions" instruction.
Also sometimes after flashing then rebooting I've had to "reinstall" Superuser so it can grant root permissions to various programs. As a habit, right after a new flash, I start Superuser once just to see if it says it needs to be reinstalled. This is not a reinstall from an apk but is a dialogue message displayed when the app is started.
As I wrote this is purely a guess on my part.
I had a laugh at the thread title. (sorry) You either have a corrupt download or something else really weird going on. A kernel wont remove root from your unlocked firmware and ROM files unless the flashing script is actually programmed to remove the files needed. Which its not.
Well this is strange, because I have fixed the permission issue and wiped cache and dalvik, not once but multiple times (I set up the kernel thrice, after it was malfunctioning).
But seeing you two replying, I set up KtManta over CM today and it is not giving me a bit of trouble, strange indeed.
btw, is it true that KTManta fixed the color issue a bit?
Yes it does fix the color a little bit.
What ROM were you on that you had this problem?
EniGmA1987 said:
Yes it does fix the color a little bit.
What ROM were you on that you had this problem?
Click to expand...
Click to collapse
Stock
Sent from my Nexus 10 using Tapatalk HD
zombiegenerator said:
Stock
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
It won't cause you to lose root but it is also not really designed to use with stock either. Most if not all custom kernel users are on CM, AOKP or AOSP ROMS.
brees75 said:
It won't cause you to lose root but it is also not really designed to use with stock either. Most if not all custom kernel users are on CM, AOKP or AOSP ROMS.
Click to expand...
Click to collapse
What's the difference between AOSP and stock roms?
And yes it's now working flawlessly with CM.
Sent from my Nexus 10 using Tapatalk HD
I have recently been switching my ROMs up alot and have been having issues going from AOSP back to TW through regular flashing of the ROMs.
I generally don't have any problems switching from TW to AOSP, but whenever I flash the other way I am just left with a black screen after the Sammy logo.
To effectively get TW back on my device I have to Odin back to stock and then Odin flash a recovery and start from scratch.
I was curious as to the rest of the communities experience with this as I may just be missing a crucial step when switching between the two systems.
I usually format the /system and do a factory reset and wipe both caches
Does anyone else have a problem like this?
sounds like a kernel issue since your wiping system and data and cache? so i wiould flash another tw kernel when going back to tw if it doesnt boot, i use the kt kernel.
jaaybs said:
I have recently been switching my ROMs up alot and have been having issues going from AOSP back to TW through regular flashing of the ROMs.
I generally don't have any problems switching from TW to AOSP, but whenever I flash the other way I am just left with a black screen after the Sammy logo.
To effectively get TW back on my device I have to Odin back to stock and then Odin flash a recovery and start from scratch.
I was curious as to the rest of the communities experience with this as I may just be missing a crucial step when switching between the two systems.
I usually format the /system and do a factory reset and wipe both caches
Does anyone else have a problem like this?
Click to expand...
Click to collapse
I have a stock rooted nandroid that I restore when I get bored with AOSP, and I haven't had any issues.
Sent from my SPH-L720 using xda premium
devoureddreams said:
sounds like a kernel issue since your wiping system and data and cache? so i wiould flash another tw kernel when going back to tw if it doesnt boot, i use the kt kernel.
Click to expand...
Click to collapse
Thats exactly it. I flashed Agats kernel with free gs4 and it worked perfectly. Thanks much
Sent from my SPH-L720 using xda app-developers app
jaaybs said:
Thats exactly it. I flashed Agats kernel with free gs4 and it worked perfectly. Thanks much
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
NP boss enjoy
Sent from my SPH-L720 using xda premium
I've been messing around with gpe roms since safestrap was released and yesterday I started having a problem. when I rebooted my phone I lost service. I've been using the same roms. deleted the rom slot and reflashed everything and still having the problem. I don't understand what's going on because this wasn't happening a few days ago
edit: on reboot my lockscreen says: roaming indicator off. and in settings under mobile networks, access points is missing. there's no apn settings and no option to add any
deadenz said:
I've been messing around with gpe roms since safestrap was released and yesterday I started having a problem. when I rebooted my phone I lost service. I've been using the same roms. deleted the rom slot and reflashed everything and still having the problem. I don't understand what's going on because this wasn't happening a few days ago
edit: on reboot my lockscreen says: roaming indicator off. and in settings under mobile networks, access points is missing. there's no apn settings and no option to add any
Click to expand...
Click to collapse
Which GPE rom have you flashed? 4.2.2 or 4.3? did you flash your kernel after you flashed the ROM?
If you read the OP it says to do so, this typically fixes cell service and wifi issues.
http://forum.xda-developers.com/showthread.php?t=2448925
FourPointedFreak said:
Which GPE rom have you flashed? 4.2.2 or 4.3? did you flash your kernel after you flashed the ROM?
If you read the OP it says to do so, this typically fixes cell service and wifi issues.
http://forum.xda-developers.com/showthread.php?t=2448925
Click to expand...
Click to collapse
I've flashed quite a few. both here in the att forum and virginrom from tmobile. they all worked fine up until a few days ago. yes they are 4.2.2 and yes I flashed the mf3 modules.
btw, this isn't happening when I flash a stock touchwiz rom. running shostock right now with no problems
deadenz said:
I've flashed quite a few. both here in the att forum and virginrom from tmobile. they all worked fine up until a few days ago. yes they are 4.2.2 and yes I flashed the mf3 modules.
btw, this isn't happening when I flash a stock touchwiz rom. running shostock right now with no problems
Click to expand...
Click to collapse
From my understanding, SafeStrap only supports TouchWiz roms and that's why you would or would not be seeing these problems.
FourPointedFreak said:
From my understanding, SafeStrap only supports TouchWiz roms and that's why you would or would not be seeing these problems.
Click to expand...
Click to collapse
yeah I know that already..
deadenz said:
yeah I know that already..
Click to expand...
Click to collapse
Then you would know that as of now there won't be a fix for these issues you're having on non-tw roms using SafeStrap. I'm now confused on why you've even posted at all if you had known that.
FourPointedFreak said:
Then you would know that as of now there won't be a fix for these issues you're having on non-tw roms using SafeStrap. I'm now confused on why you've even posted at all if you had known that.
Click to expand...
Click to collapse
I'm confused as to why you posted. I told you these roms were all working fine for me and only recently have I had this problem. the gpe roms I'm using ARE tw based
deadenz said:
I'm confused as to why you posted. I told you these roms were all working fine for me and only recently have I had this problem. the gpe roms I'm using ARE tw based
Click to expand...
Click to collapse
You're talking about two different things here now - if you've cleared everything correctly, including dalvik cache, flashed your rom and the kernel then it should be fine. If it's not, I would find another download of your GPE 4.2.2 rom and ensure it's not your ROM that's causing problems. Just because there aren't immediate problems, doesn't mean problems can't occur later on - as you've noticed.
Or perhaps try all of the appropriate steps on another ROM slot for troubleshooting purposes.
FourPointedFreak said:
You're talking about two different things here now - if you've cleared everything correctly, including dalvik cache, flashed your rom and the kernel then it should be fine. If it's not, I would find another download of your GPE 4.2.2 rom and ensure it's not your ROM that's causing problems. Just because there aren't immediate problems, doesn't mean problems can't occur later on - as you've noticed.
Or perhaps try all of the appropriate steps on another ROM slot for troubleshooting purposes.
Click to expand...
Click to collapse
I've done all that. I've deleted and recreated the rom slot and flashed 4 different gpe roms to see if it was a certain rom causing the problem but no it was all of them.. that's why I'm so confused because these roms worked perfectly up until a few days ago. and like I said I just flashed shostock last night and I haven't had the problem. when you say flash my kernel you're talking about the mf3 zip that hashcode provided correct?
deadenz said:
I've done all that. I've deleted and recreated the rom slot and flashed 4 different gpe roms to see if it was a certain rom causing the problem but no it was all of them.. that's why I'm so confused because these roms worked perfectly up until a few days ago. and like I said I just flashed shostock last night and I haven't had the problem. when you say flash my kernel you're talking about the mf3 zip that hashcode provided correct?
Click to expand...
Click to collapse
Yes, that's correct. If you've done that - then it makes no sense. Seems you have done it all in order, accordingly. Hopefully Shostock doesn't fail on you also.
FourPointedFreak said:
Yes, that's correct. If you've done that - then it makes no sense. Seems you have done it all in order, accordingly. Hopefully Shostock doesn't fail on you also.
Click to expand...
Click to collapse
exactly! it makes no sense! I'm hoping someone can help out though..
with virginrom, there was a at&t csc file to flash after the rom. other than apn settings what is this file for?
deadenz said:
exactly! it makes no sense! I'm hoping someone can help out though..
with virginrom, there was a at&t csc file to flash after the rom. other than apn settings what is this file for?
Click to expand...
Click to collapse
I'm not familiar with the Virginrom, but I know that CSC files are written scripts, usually for automation. They work with with programs that support OLE. Seeing that it was carrier specific, I'd think that was used along the lines of APN settings within the ROM to some degree.
FourPointedFreak said:
I'm not familiar with the Virginrom, but I know that CSC files are written scripts, usually for automation. They work with with programs that support OLE. Seeing that it was carrier specific, I'd think that was used along the lines of APN settings within the ROM to some degree.
Click to expand...
Click to collapse
I even had a backup of one of the gpe roms that I had been running for almost a week with no problem and after restoring it to a completely new rom slot I still have the problem..
deadenz said:
I even had a backup of one of the gpe roms that I had been running for almost a week with no problem and after restoring it to a completely new rom slot I still have the problem..
Click to expand...
Click to collapse
That's bizarre. I would also suggest manually uninstalling SafeStrap and re-installing it but your Shostock hasn't had any problems yet. I couldn't think of anything else that would be posing a problem.
I installed Pure Nexus on my Nexus 6P the other day. I was using the phone as stock for the past couple of months. I'm an old user of CM mind you.
Since the last 2 days, Ive had nothing but problems with the ROM. I've got several apps that keep crashing,, namely Minimalistic Text, Camera and others. This never happened at all on stock. Even when I use Airdroid to scan the QR code, it uses the wrong camera.
Unfortunately, I've decided to flush Pure Nexus and just in the middle of flashing CM 13 and will try it in a few minutes.
I think I've given enough time for Pure Nexus, but I can't blame the apps that I'm using, as I've used them before on various ROMs on my old Nexus 4 without incident as well as on my Nexus 7.
I've tried to post in another forum thread but since I'm unable to as I haven't posted many times, the forum has driven me here instead.
barry123 said:
I installed Pure Nexus on my Nexus 6P the other day. I was using the phone as stock for the past couple of months. I'm an old user of CM mind you.
Since the last 2 days, Ive had nothing but problems with the ROM. I've got several apps that keep crashing,, namely Minimalistic Text, Camera and others. This never happened at all on stock. Even when I use Airdroid to scan the QR code, it uses the wrong camera.
Unfortunately, I've decided to flush Pure Nexus and just in the middle of flashing CM 13 and will try it in a few minutes.
I think I've given enough time for Pure Nexus, but I can't blame the apps that I'm using, as I've used them before on various ROMs on my old Nexus 4 without incident as well as on my Nexus 7.
I've tried to post in another forum thread but since I'm unable to as I haven't posted many times, the forum has driven me here instead.
Click to expand...
Click to collapse
Hey Barry,
After you flashed Pure Nexus ROM, did you delete the cache? I would try it again, since things can go wrong and others are on Pure Nexus without issue.
deleted cache, dalvik, wiped entire phone, yes
LeftHandedWave said:
Hey Barry,
After you flashed Pure Nexus ROM, did you delete the cache? I would try it again, since things can go wrong and others are on Pure Nexus without issue.
Click to expand...
Click to collapse
Try flashing vendor image. Pure Nex is a solid rom one of the most stable roms there is.
Sent from my Nexus 6P using Tapatalk
I've done that too in my initial flashing
flashback7 said:
Try flashing vendor image. Pure Nex is a solid rom one of the most stable roms there is.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
barry123 said:
I've done that too in my initial flashing
Click to expand...
Click to collapse
Maybe grab some logs of these apps crashing and post them on pure nexus thread.
Sent from my Nexus 6P using Tapatalk
the apps you are having issues with, did you restore those from a backup (i.e. Titanium Backup)? If so i'd clear the app data/cache and force close them. Typically that helps.
I've lost everything since I've put in a different ROM, but have contacted the developers of the apps of my problem. After mant apps crashing, I decided that it was futile to contact the developers as I realized it was due to the ROM and not the apps I was using, as I've used them before without problems
flashback7 said:
Maybe grab some logs of these apps crashing and post them on pure nexus thread.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Nope, I did a fresh install of all my apps
one7dchevy said:
the apps you are having issues with, did you restore those from a backup (i.e. Titanium Backup)? If so i'd clear the app data/cache and force close them. Typically that helps.
Click to expand...
Click to collapse
barry123 said:
I've lost everything since I've put in a different ROM, but have contacted the developers of the apps of my problem. After mant apps crashing, I decided that it was futile to contact the developers as I realized it was due to the ROM and not the apps I was using, as I've used them before without problems
Click to expand...
Click to collapse
If I were you, I would try again. Download the ROM and verify that is the correct checksum. Like I said, others here have Pure Nexus without issue.
did a hashcheck [md5] of all files as I usually do. Now I'm even having problems flashing new ROMs since in the last hour or so. I've made a backup of Pure Nexus ROM, so I know I'm able to use it, but might have to do other things here in the next couple of days to get rid of it
LeftHandedWave said:
If I were you, I would try again. Download the ROM and verify that is the correct checksum. Like I said, others here have Pure Nexus without issue.
Click to expand...
Click to collapse
barry123 said:
I've lost everything since I've put in a different ROM, but have contacted the developers of the apps of my problem. After mant apps crashing, I decided that it was futile to contact the developers as I realized it was due to the ROM and not the apps I was using, as I've used them before without problems
Click to expand...
Click to collapse
I guarantee you it was not due to the rom. If it was others would be reporting the same thing you are. Logs are the only way to diagnose a problem. Its a waste of time discussing anything workout logs..
Sent from my Nexus 6P using Tapatalk
I just reverted to Pure Nexus again from my backup as I can't seem to flash any other ROM. I did some logs on one app but I can only do it while the app is running and not when it's crashed. I'm unable to attach the file here but only put the text which is too long for an xda submission. I've gone through help to attach but it seems I have to make a new post and not reply to this thread. Weird!
flashback7 said:
I guarantee you it was not due to the rom. If it was others would be reporting the same thing you are. Logs are the only way to diagnose a problem. Its a waste of time discussing anything workout logs..
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
barry123 said:
I just reverted to Pure Nexus again from my backup as I can't seem to flash any other ROM. I did some logs on one app but I can only do it while the app is running and not when it's crashed. I'm unable to attach the file here but only put the text which is too long for an xda submission. I've gone through help to attach but it seems I have to make a new post and not reply to this thread. Weird!
Click to expand...
Click to collapse
What recovery are you using? What version? How are you flashing?? Wipe data, system, cache, delvik cache, flash rom, flash gapps, reboot??
Sent from my Nexus 6P using Tapatalk
flashback7 said:
What recovery are you using? What version? How are you flashing?? Wipe data, system, cache, delvik cache, flash rom, flash gapps, reboot??
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Using TWRP 2.8.7.2 wiped everything u mentioned above but unable to attach log files, no attachment box is available to me here
flashback7 said:
What recovery are you using? What version? How are you flashing?? Wipe data, system, cache, delvik cache, flash rom, flash gapps, reboot??
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
did everything u mentioned above. I've flashed my old Nexus 4 many times over the past couple of years
Use pastebin and include a link to your logs.
dodgerslim said:
Use pastebin and include a link to your logs.
Click to expand...
Click to collapse
<script src="//pastebin.com/embed_js/NHEvqKc9"></script>
BTW I've installed CM 13 and minimalistic text works flawlessly on it, no hiccups no crashes, weird!!
When stuff like that happens to me and I feel I've tried everything I can think of, I usually make it easier on myself to run the script in Google's factory image and start new. Flash TWRP with ADB tools, format, reboot TWRP, transfer flashables, and start with that ROM from scratch with GApps. Most variables of messing up would have been avoided and chances of success should be high. Anyone else agree with that?
PKFR4Life said:
When stuff like that happens to me and I feel I've tried everything I can think of, I usually make it easier on myself to run the script in Google's factory image and start new. Flash TWRP with ADB tools, format, reboot TWRP, transfer flashables, and start with that ROM from scratch with GApps. Most variables of messing up would have been avoided and chances of success should be high. Anyone else agree with that?
Click to expand...
Click to collapse
LOL! I've done that a few times reverting to stock and going from there. I'v had to do that in the past to get out of trouble. But seeing how I've done this countless of times over the past few years and the last phone was also a Nexus [albeit quite a change from Lollypop to Marshmallow], the rules are the same for flashing. One thing I was concerned with initially was that the vendor.img file for Pure Nexus was MMB29P but I'm on MMB29T. I don't know if that's an issue. I'm using 6.0.1 Android.
I may try it again in a few days mind you and re-flash. Will def post something if it's a positive change!!