EDIT: Mounted system as R/W and i'm now restoring my stock unrooted backup of the system. But My "System Image" backup gives me ERROR=2?
So I had the xposed disabler zip on my SD, I had a system image backup from before I rooted, a full normal backup as well.
It wouldn't boot after I flashed the Xposed Zip from here: http://forum.xda-developers.com/showthread.php?t=3034811
I flashed the one for SDK21-arm64.
I was like okay, and flashed the disabler, it said no backup of something made so no way to restore.
I sighed and tried restoring the system image, error, I tried restoring the full normal backup, mounted read only can't restore?
What should I do?
I have TWRP installed so I can boot into bootloader and recovery, not sure how to fix this.
Found out how to mount the system as read/write. Trying to restore again.
"Process ended with ERROR=2"
Mounted system as R/W and i'm now restoring my stock unrooted backup of the system. But My "System Image" backup gives me ERROR=2?
Yep. It doesn't work. Basically I just booted twrp, installed the uninstall zip and wiped cache to fix.
I think there's a version 22 that also didn't work. It gave an error trying to install. Here's the thread if you want to try it.
http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
Xposed Framework for Alcatel Idol 3
Was there any error when installing xposed? Did anyone do an adb logcat on bootup to a text file to catch the error? Did anyone report the issue to the Xposed for Lollipop thread? (not sure why you'd be looking in the xposed for 5.1 thread since we are still on 5.0.2 but I found no sign of the words "alcatel" or "idol" in either thread. They can't fix it if they don't know about it.
oh man i wouldnt risk installing it hope theres a build compatible for us
gecko702 said:
oh man i wouldnt risk installing it hope theres a build compatible for us
Click to expand...
Click to collapse
Oh I don't plan on installing it till it's known to work but for folks who already did they should report as much as possible to the xposed thread so it can be corrected although we now have system images to revert to if necessary. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
neilownz said:
Yep. It doesn't work. Basically I just booted twrp, installed the uninstall zip and wiped cache to fix.
I think there's a version 22 that also didn't work. It gave an error trying to install. Here's the thread if you want to try it.
http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
Click to expand...
Click to collapse
don't even try this one it's 5.1 ONLY!!!!
i'll test v68 from romracer as soon as the ****in post office will bring me my phone
famewolf said:
Oh I don't plan on installing it till it's known to work but for folks who already did they should report as much as possible to the xposed thread so it can be corrected although we now have system images to revert to if necessary. http://forum.xda-developers.com/idol-3/general/want-to-able-to-install-ota-updates-t3163745
Click to expand...
Click to collapse
well i went to the xposed unofficial build thread and it says its for 5.1 though still im not going to risk it lol im a very cautious person ><
gecko702 said:
well i went to the xposed unofficial build thread and it says its for 5.1 though still im not going to risk it lol im a very cautious person ><
Click to expand...
Click to collapse
As mentioned multiple times by me and others...no one should be going to the unoffical xposed for android 5.1 thread...if it was gonna work it would be the offical "android for lollipop thread (5.0)". Of course if no one reports the errors then it will never get fixed. Oh well...will re-evaluate it in a few months.
Hopefully this will work soon, I miss Xposed. There was a guy that posted a logcat from his Idol in the Xposed 5.0 thread, but I don't seen any responses to him.
KryPTiCk0d3 said:
Hopefully this will work soon, I miss Xposed. There was a guy that posted a logcat from his Idol in the Xposed 5.0 thread, but I don't seen any responses to him.
Click to expand...
Click to collapse
i miss it too i had once on my htc one sv it was great plus the adblocker for youtube was phenomenal
edit: well heres something for 5.0 maybe should work? http://forum.xda-developers.com/showthread.php?p=62065892#post62065892
gecko702 said:
i miss it too i had once on my htc one sv it was great plus the adblocker for youtube was phenomenal
edit: well heres something for 5.0 maybe should work? http://forum.xda-developers.com/showthread.php?p=62065892#post62065892
Click to expand...
Click to collapse
The OP had a different error, so I'm not sure if that newer version would help... I would try it out, but I have too many things to do this weekend other than fix my phone :laugh::laugh:
Ill give it a shot ill post results later im busy now going to have my coffee now
Edit: i flashed the xposed arm64 version rebooted and i got stuck in the white alcatel logo that says smart move i left it alone for a few minutes and nothing so i flashed the uninstaller and went back to normal not sure if i need to wipe the dalvik after i install the xposed hmmm might retry again
So I flashed xposed-v69-sdk21-arm64.zip, wiped Dalvik & Cache, and it still hung at boot, I did get an adb logcat on boot for it, and I have attached that in the Xposed thread. Hopefully it will help us get this resolved. I was able to revert back with the uninstaller.
KryPTiCk0d3 said:
So I flashed xposed-v69-sdk21-arm64.zip, wiped Dalvik & Cache, and it still hung at boot, I did get an adb logcat on boot for it, and I have attached that in the Xposed thread. Hopefully it will help us get this resolved. I was able to revert back with the uninstaller.
Click to expand...
Click to collapse
oh yeah i havent thought about making a logcat...have you gotten any responses?
gecko702 said:
oh yeah i havent thought about making a logcat...have you gotten any responses?
Click to expand...
Click to collapse
No, I haven't.
had just one answer after posting logcat, they said it was something with odexed rom
tested r70 and still no luck
keyra74 said:
had just one answer after posting logcat, they said it was something with odexed rom
tested r70 and still no luck
Click to expand...
Click to collapse
so we basically need to have a deodexed rom huh?
Related
I'm having an odd problem, and I'm not sure what to do about it.
This morning when I woke up, I noticed that there was a BusyBox update in my notification bar. Upon trying to update it failed.
So, I uninstall BusyBox, and try to reinstall it, but I'm met with a message that I don't have root access. Upon checking with Root Checker, I DO have root access. But, now all of a sudden, my wifi is not working, when it has worked flawlessly up to this point.
I'm not sure what to do. I don't have a nandroid backup to roll back to, and I need my wifi to work. Would doing a factory reset and flashing a new ROM solve this problem?
lukas_s said:
I'm having an odd problem, and I'm not sure what to do about it.
This morning when I woke up, I noticed that there was a BusyBox update in my notification bar. Upon trying to update it failed.
So, I uninstall BusyBox, and try to reinstall it, but I'm met with a message that I don't have root access. Upon checking with Root Checker, I DO have root access. But, now all of a sudden, my wifi is not working, when it has worked flawlessly up to this point.
I'm not sure what to do. I don't have a nandroid backup to roll back to, and I need my wifi to work. Would doing a factory reset and flashing a new ROM solve this problem?
Click to expand...
Click to collapse
What ROM are you on...Gingerbread or ICS?
you must be on a custom rom or you on stock, rooted?
---------- Post added at 04:48 PM ---------- Previous post was at 04:40 PM ----------
ok need to go into CWM and flash these files, should correct it, I had this issue on a ROM dont recall which one or it might of been on a rooted stock....
but before you do anything.....
download these files and put them on your sd card of the phone, NOT THE EXT memory card, you are gonna flash them like you would a ROM ok, in cwm, you can flash them back to back while you are in CWM...kk
download this file first and flash this file first: FLASH ME FIRST
download this file second and flash it second: FLASH ME SECOND
bigjoe2675 said:
What ROM are you on...Gingerbread or ICS?
you must be on a custom rom or you on stock, rooted?
Click to expand...
Click to collapse
I'm on Gingerbread, MIUI 2.3.9
lukas_s said:
I'm on Gingerbread, MIUI 2.3.9
Click to expand...
Click to collapse
try what I suggested and let us know if it works...kk
Didn't seem to work. Still can't install BusyBox. I'm not sure what kinda bearing that has on my wifi, my wifi just stopped working when the BusyBox update failed this morning.
lukas_s said:
Didn't seem to work. Still can't install BusyBox. I'm not sure what kinda bearing that has on my wifi, my wifi just stopped working when the BusyBox update failed this morning.
Click to expand...
Click to collapse
check the MIUI thread...
http://forum.xda-developers.com/showthread.php?t=1294549
I think MIUI occasionally loses recovery. Possible kernel issue.
Read through the thread to see if you can get some additional info.
I'm not sure if it has any bearing on your wifi..possible.
If you know how, you can try extracting the kernel from MIUI rom and reflashing just the kernel using SGS kernel flasher to retain your data.
qkster said:
check the MIUI thread...
http://forum.xda-developers.com/showthread.php?t=1294549
I think MIUI occasionally loses recovery. Possible kernel issue.
Read through the thread to see if you can get some additional info.
I'm not sure if it has any bearing on your wifi..possible.
If you know how, you can try extracting the kernel from MIUI rom and reflashing just the kernel using SGS kernel flasher to retain your data.
Click to expand...
Click to collapse
I definitely don't know how to do that haha. I'm a noob when it comes to this whole game, although I'm slowly learning.
Do you think doing a factory reset, wiping everything, and then flashing a new ROM might fix my issue? I did want to try out one of the new ICS ROMs, so if that will fix my problem I might as well go ahead and try one of them out.
Flashing Uniporn seemed to have fixed my issue. I first re-flashed MIUI and that didn't solve anything, so I guess the issue was with MIUI? Just odd that the wifi would drop out after using it flawlessly for 4 months.
Oh well, got something new to play with again. Thanks for the help guys!
lukas_s said:
Flashing Uniporn seemed to have fixed my issue. I first re-flashed MIUI and that didn't solve anything, so I guess the issue was with MIUI? Just odd that the wifi would drop out after using it flawlessly for 4 months.
Oh well, got something new to play with again. Thanks for the help guys!
Click to expand...
Click to collapse
that bld of miui, i was reading was not stable, idk...coming from the other miui users, but each user has a their ver of the story...
but glad it worked out, thx qkster...and don't forget to thx Nun for the rom he worked on...Uniporn
I was hoping to try out one of the 4.2 builds tonight, but every time I try to flash one through TWRP it just says "Failed"; I've tried CM10.1 and Eclipse ROM and they both had the same result. Also tried redownloading ROMs and re-copying them to my SD card, still no change. Can anyone tell me what I'm doing wrong here? I've never had a problem flashing any ROM before.
Devilicus said:
I was hoping to try out one of the 4.2 builds tonight, but every time I try to flash one through TWRP it just says "Failed"; I've tried CM10.1 and Eclipse ROM and they both had the same result. Also tried redownloading ROMs and re-copying them to my SD card, still no change. Can anyone tell me what I'm doing wrong here? I've never had a problem flashing any ROM before.
Click to expand...
Click to collapse
What version of TWRP are you running?
If you haven't done it lately, I would suggest updating your twrp to the latest and trying again.
I'm running the newest TWRP (I think), version 2.4.1.0
Devilicus said:
I'm running the newest TWRP (I think), version 2.4.1.0
Click to expand...
Click to collapse
Weird. I am on that same version and have been flashing 4.2 roms for the last few weeks without any issues.
A few things I would try:
-Double check the md5 of the rom you are flashing
-Make sure it is a d2vzw rom
-Wipe caches, delete user data and wipe system
-Put the rom on the internal sdcard before flashing.
Other than that, I got nothing
Relentless D said:
Weird. I am on that same version and have been flashing 4.2 roms for the last few weeks without any issues.
A few things I would try:
-Double check the md5 of the rom you are flashing
-Make sure it is a d2vzw rom
-Wipe caches, delete user data and wipe system
-Put the rom on the internal sdcard before flashing.
Other than that, I got nothing
Click to expand...
Click to collapse
Damn, yeah I can't figure it out; all the ones I've tried were Verizon ones, made sure to wipe everything as usual, tried putting it on the internal SD card and the external, won't work on either one. Very frustrating. But thanks for the help anyway
Ok, I think I figured out the problem (won't be sure until I try it), but I think what happened is I edited my build.prop to the Sprint GS3 to get Google Wallet to work, forgot to change it back, and updated TWRP (which installed the Sprint version, not Verizon), and that's why the flashes are failing. So if any other people are having the same problem, that might be why. Yes I'm an idiot lol. Hopefully this fixes it
Try carbon ROM.
First to work for me.
Sent from my SCH-I535 using xda app-developers app
Devilicus said:
Ok, I think I figured out the problem (won't be sure until I try it), but I think what happened is I edited my build.prop to the Sprint GS3 to get Google Wallet to work, forgot to change it back, and updated TWRP (which installed the Sprint version, not Verizon), and that's why the flashes are failing. So if any other people are having the same problem, that might be why. Yes I'm an idiot lol. Hopefully this fixes it
Click to expand...
Click to collapse
What baseband [modem] do you have installed? ...and some more info if build prop wasn't the issue. Would also be interested if, "but I think what happened is I edited my build.prop", was the issue and you fixed it. Let us know. Goodluck
JohnAreBee said:
What baseband [modem] do you have installed? ...and some more info if build prop wasn't the issue. Would also be interested if, "but I think what happened is I edited my build.prop", was the issue and you fixed it. Let us know. Goodluck
Click to expand...
Click to collapse
Yeah it turns out that was the problem. I edited my build.prop to match the Sprint GS3, so I could download Google Wallet from the Play Store and use it. I just never bothered to change the build.prop back. And when I updated TWRP through GooManager, it assumed I had a Sprint GS3 and installed the wrong recovery. When I flashed the correct Verizon version of TWRP everything worked fine. Thanks for the suggestions everyone
Devilicus said:
Yeah it turns out that was the problem. I edited my build.prop to match the Sprint GS3, so I could download Google Wallet from the Play Store and use it. I just never bothered to change the build.prop back. And when I updated TWRP through GooManager, it assumed I had a Sprint GS3 and installed the wrong recovery. When I flashed the correct Verizon version of TWRP everything worked fine. Thanks for the suggestions everyone
Click to expand...
Click to collapse
Good call. Might be worth mentioning over in the wallet thread. It could save someone the headache you just experienced. Congrats on getting it working.
Sent from my SCH-I535 using Tapatalk 2
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Matthewlawson3 said:
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Click to expand...
Click to collapse
First of all, stop using the stock recovery.
Since you had root access, were you using any modifications such as Xposed?
You can pull your internal storage with adb pull /sdcard/, and your app data with adb pull /data/data/ while in custom recovery.
You can also try pushing a stock ROM .zip downloaded from here to your device with ADB push, then dirty flashing it in recovery (obviously after flashing a custom recovery, also assuming you're on stock ROM).
Also, don't use toolkits. Click the first link of my signature and read some threads if you don't know how to use ADB/fastboot.
On a sidenote I do have xposed framework installed. However, I've never had any problems out of it and I have not modified anything in months.
Matthewlawson3 said:
Hi Guys! Really hope you can help.
My Nexus 5 when I turned it on this morning booted up into 4.4.4 and suddenly showed that the process "com.android.systemui" has stopped. I rebooted several times and even cleared the cache through stock recovery and I still get the message. I have no idea what caused it. It was fine last night when I turned it off.
My phone is rooted and I do have a nandroid that is about two months old and I could boot TWRP using the Nexus Root Toolkit, but I was wondering if there is any other options? I would prefer not to lose anything up to this point.
I could kick myself for not making a more current nandroid. I've just been busy.
If the nandroid restore is the best approach could you refresh me on the exact options needed for both a clean restore with a nandroid and a dirty flash? I would probably dirty flash it first.
Hope you can help! Thanks so much!
Click to expand...
Click to collapse
Matthewlawson3 said:
On a sidenote I do have xposed framework installed. However, I've never had any problems out of it and I have not modified anything in months.
Click to expand...
Click to collapse
Read my previous post, and since you're running Xposed try using it's safemode disable feature, explanation on how that works here: http://forum.xda-developers.com/showpost.php?p=51306764&postcount=9879
Do you think this is caused by Xposed? You want me to disable it to see I assume?
Matthewlawson3 said:
Do you think this is caused by Xposed? You want me to disable it to see I assume?
Click to expand...
Click to collapse
It's entirely possible that a module/Xposed itself is causing a SystemUI crash, it's happened to me before. I'd do it just to be sure, then proceed to what I said in my previous post if it still happens.
Ok its been awhile since I dirty flashed. If I have to do that, what are the exact things that need to be cleared to maintain data after recovery?
Lethargy said:
It's entirely possible that a module/Xposed itself is causing a SystemUI crash, it's happened to me before. I'd do it just to be sure, then proceed to what I said in my previous post if it still happens.
Click to expand...
Click to collapse
Matthewlawson3 said:
Ok its been awhile since I dirty flashed. If I have to do that, what are the exact things that need to be cleared to maintain data after recovery?
Click to expand...
Click to collapse
What do you mean? No data is lost if you dirty flash a ROM, it only reformats /system.
Custom recovery, download stock ROM flashable zip, ADB push zip to your device while it's in recovery, then flash it.
It looks like I may not have to flash anything. The Xposed Disable worked. But how do I proceed if I want to use Xposed still?
Lethargy said:
What do you mean? No data is lost if you dirty flash a ROM, it only reformats /system.
Custom recovery, download stock ROM flashable zip, ADB push zip to your device while it's in recovery, then flash it.
Click to expand...
Click to collapse
Matthewlawson3 said:
It looks like I may not have to flash anything. The Xposed Disable worked. But how do I proceed if I want to use Xposed still?
Click to expand...
Click to collapse
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
OK.
My modules are AC Display, Bootmanager, DS Battery Saver, Google Search API, Gravity Box (KK), Greenify, Immerse Me, Notify Clean, Swype Tweaks, Xblast Tools, and Youtube Adaway.
Lethargy said:
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
Click to expand...
Click to collapse
Matthewlawson3 said:
OK.
My modules are AC Display, Bootmanager, DS Battery Saver, Google Search API, Gravity Box (KK), Greenify, Immerse Me, Notify Clean, Swype Tweaks, Xblast Tools, and Youtube Adaway.
Click to expand...
Click to collapse
Continue with what I've said to try, a few of your modules modify the system and could be causing it.
Go to the xposed module repository and find which of those modules updated recently. I'd bet that's the culprit. Or at least it's a good place to start looking.
Ok before I proceed. I have went into Xposed and disabled all modules. I am now in Root Explorer and have dug down to the "disabled" file following the path indicated. Do I just delete "disabled" and then reboot?
Lethargy said:
Continue with what I've said to try, a few of your modules modify the system and could be causing it.
Click to expand...
Click to collapse
Matthewlawson3 said:
Ok before I proceed. I have went into Xposed and disabled all modules. I am now in Root Explorer and have dug down to the "disabled" file following the path indicated. Do I just delete "disabled" and then reboot?
Click to expand...
Click to collapse
Yep, delete the folder named "disabled"
It may be faster to see which module updated recently and see if that fixes the problem first before going one by one. What do you think?
Lethargy said:
Yep, delete the folder named "disabled"
Click to expand...
Click to collapse
Matthewlawson3 said:
It may be faster to see which module updated recently and see if that fixes the problem first before going one by one. What do you think?
Click to expand...
Click to collapse
Worth a shot. In the end it's probably a single module, or a combination of conflicting modules, that's causing the issue.
Looks like the latest updated was Bootmanager on July 26.
Lethargy said:
First of all we have to see if it's an individual module or Xposed itself causing the issue. List your modules?
Disable all your modules, and delete /data/data/de.robv.android.xposed.installer/conf/disabled using a file explorer (to re-enable Xposed like the post says).
Reboot with no modules active, and see if it happens again.
If it doesn't, enable one module, reboot.
If it still doesn't happen, disable the module and enable a different one, reboot again. Keep doing it until you find the culprit.
Click to expand...
Click to collapse
Matthewlawson3 said:
Looks like the latest updated was Bootmanager on July 26.
Click to expand...
Click to collapse
Try enabling them one by one by update date.
I'll reboot with all modules off first. Ok, I no longer am getting the error message. At least it's not Xposed itself!
Matthewlawson3 said:
Looks like the latest updated was Bootmanager on July 26.
Click to expand...
Click to collapse
Had anybody seen a situation where the recovery won't keep the correct date and time? I've flashed TWRP 2.7.1.0, 2.8.0.1, and the latest Philz, and all of them kept changing the time, the timezone, and the date... and they were acting a little buggy in their responsiveness.
Thoughts?
WarAxe said:
Had anybody seen a situation where the recovery won't keep the correct date and time? I've flashed TWRP 2.7.1.0, 2.8.0.1, and the latest Philz, and all of them kept changing the time, the timezone, and the date... and they were acting a little buggy in their responsiveness.
Thoughts?
Click to expand...
Click to collapse
I've experienced the same issue since I got my S5. KT TWRP 2.8.1.0 doesn't have that problem. It also fixes the backup to extSD problem, if you were experiencing that.
Ramer84015 said:
I've experienced the same issue since I got my S5. KT TWRP 2.8.1.0 doesn't have that problem. It also fixes the backup to extSD problem, if you were experiencing that.
Click to expand...
Click to collapse
THANKS! I had KT's downloaded but didn't flash it yet... I certainly will now. And yes, the extSD issue bit me, too.
Nope... date is 1/1/2014 and the time is 3 hours lagging for the timezone.
Let's hope at the very least my nandroid backups won't disappear.
WarAxe said:
Nope... date is 1/1/2014 and the time is 3 hours lagging for the timezone.
Let's hope at the very least my nandroid backups won't disappear.
Click to expand...
Click to collapse
Try this: Using something like Root Explorer, look for the TWRP folder on your internal SD card. There's a file called ".twrps". It's the config file for TWRP. Delete it and then boot back into TWRP. You'll have to redo your setting (timezone, screen timeout etc.). See if that fixes it. If that doesn't do it, not sure what else will.
Ramer84015 said:
Try this: Using something like Root Explorer, look for the TWRP folder on your internal SD card. There's a file called ".twrps". It's the config file for TWRP. Delete it and then boot back into TWRP. You'll have to redo your setting (timezone, screen timeout etc.). See if that fixes it. If that doesn't do it, not sure what else will.
Click to expand...
Click to collapse
I had tried peeking into the file with Notepad++ but nothing jumped out at me. Now I feel silly for not trying what you suggested.
I deleted it and it had no effect. The one I deleted and the one it created had the wrong date/time stamps on them... as did the two backups I created (both in metadata and filename convention).
On the bright side... my two backups are as yet undeleted.
WarAxe said:
I had tried peeking into the file with Notepad++ but nothing jumped out at me. Now I feel silly for not trying what you suggested.
I deleted it and it had no effect. The one I deleted and the one it created had the wrong date/time stamps on them... as did the two backups I created (both in metadata and filename convention).
On the bright side... my two backups are as yet undeleted.
Click to expand...
Click to collapse
Very strange, I was sure that was it. My date/time have been correct since using it. The only other thing I may have done was using KT Kernel as well, but I don't think that was it. If you decide to try KT Kernel and want to go back to stock kernel, here's a link for stock: http://forum.xda-developers.com/showpost.php?p=54632862&postcount=1702
Another thought: What version is your firmware? Should be NE5. If not, here's that link: http://forum.xda-developers.com/showthread.php?t=2798079
Ramer84015 said:
Very strange, I was sure that was it. My date/time have been correct since using it. The only other thing I may have done was using KT Kernel as well, but I don't think that was it. If you decide to try KT Kernel and want to go back to stock kernel, here's a link for stock: http://forum.xda-developers.com/showpost.php?p=54632862&postcount=1702
Another thought: What version is your firmware? Should be NE5. If not, here's that link: http://forum.xda-developers.com/showthread.php?t=2798079
Click to expand...
Click to collapse
Thanks for the links.
I didn't flash the KT Kernel because the post said it needed to be flashed onto a TouchWiz based ROM... and right now I have PacMan (AOKP). I had MOAR (NE5) installed for a bit but I'm not used to stock. Truthfully, MOAR had everything I could want... I may just have to get over my snootiness.
Oh, it's coming back to me... with MOAR I was getting a lot of error popups of processes stopping running. i think "acore" was a common one. I could have troubleshot but didn't.
WarAxe said:
Oh, it's coming back to me... with MOAR I was getting a lot of error popups of processes stopping running. i think "acore" was a common one. I could have troubleshot but didn't.
Click to expand...
Click to collapse
Make sure your backup works and come on over I'm a big supporter of MOAR! Do a clean install though and I bet 99.9% of your problems will be solved
Ramer84015 said:
Make sure your backup works and come on over I'm a big supporter of MOAR! Do a clean install though and I bet 99.9% of your problems will be solved
Click to expand...
Click to collapse
There's the main install 2.1, and the new stuff 1.7, and of course Gapps. Do folks typically flash them all together... Or separately sequentially?
My clean install is usually wiping cache, dalvik, data, and system.
WarAxe said:
There's the main install 2.1, and the new stuff 1.7, and of course Gapps. Do folks typically flash them all together... Or separately sequentially?
My clean install is usually wiping cache, dalvik, data, and system.
Click to expand...
Click to collapse
MOAR is TW, so gapps is included. My FAQ and guide for MOAR may help you get a feel for it.
Ramer84015 said:
MOAR is TW, so gapps is included. My FAQ and guide for MOAR may help you get a feel for it.
Click to expand...
Click to collapse
Okay... MOAR's on there now. I'll read up and tweak to the extent I'm able and see if I have any questions.
WarAxe said:
Okay... MOAR's on there now. I'll read up and tweak to the extent I'm able and see if I have any questions.
Click to expand...
Click to collapse
Feel free to post any questions on the Q&A thread. :good:
I installed marshmallow yesterday through Odin, using one of the walkthroughs on XDA. I was going from a custom ROM to marshmallow. The OP in the guide I was following said he didn't completely wipe his phone beforehand. I didn't either and everything installed perfectly fine, when I booted up everything seem to be fine. But then 30 seconds passed and I started to receive incessant notifications letting me know that several apps we're not responding and had to close. In total there are about 20 to 25 apps that were not responding or working or opening. I figured out though that it's a simple fix if you have this issue. Just a simple uninstall and reinstall could fix the issue if it's just happening with one app. If this happens to you though and it's like my case where it's a bunch of apps, you can simply just back everything up with titanium backup and simply restore all the apps you backed up... no uninstalling necessary. No issues since then. I don't know if I'm the only one who had this issue but hopefully this can help someone.
Also kind of off topic, does anyone know if Xposed for marshmallow on our phones is available.
I cannot say if this warrant a new thread, should have posted it in the threat you follow and let the users who will be following that guide about what you went through.
Honestly, everyone I know (especially those rooted) typically wipe their phone and more specifically ODIN the latest update before and not just dirty odin / flash it.
In my many ODIN guide you will see, they usually recommend a wipe after odin there is a reason for that, to avoid what you just went through. Permissions get all jacked up, apps FCs, wont start up, phone locks up, yadi...yada....
WIPE
P.S xpose for marshemellow been available eons ago, just look around xda.
Hey there. Xposed is available. I already installed and tested a bunch of modules. Use this guide.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
You just need the xposed installer, sdk23 arm64 version and the uninstaller in case things get squirly.
Sent from my SM-N920T using Tapatalk
ariazad said:
Hey there. Xposed is available. I already installed and tested a bunch of modules. Use this guide.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
You just need the xposed installer, sdk23 arm64 version and the uninstaller in case things get squirly.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Thank you ariazad!