When I installed xposed at first it was working and i installed all my modules but then i installed per app hacking cause my battery was draining fast.So i started stopping wakelocks on certains apps I thought was draining my battery and next thing you know my phone started acting crazy so i used odin and flash the stock nb4 firmware in odin but didnt factory reset my phone. So my phone booted up and it was stock firmware and i had re rooted it using cf auto root i already had the xposed installer but the framework wasnt activated so when i activated it said sucess and rebooted but when it rebooted it got all the way to the tmoible 4g lte screen and didnt go past that it didnt bootloop but it like wont turn on just stays on the tmobile 4g lte screen.Can anyone help i used xposed for everything its a main part of my phone i need.When i go into xposed it says "app_process version 58 has been installed previously but version "_" was found now.If you didnt expect an old file to be restored,you might want to try installing via recovery(auto or manual)
Related
I just recently rooted my i747 using the No Trip Counter method using ODIN and the stock ROM with root injected into it already. I had a fair amount of stuff frozen with TiBu but nothing on the "unsafe" list. I made sure screen rotation was on, tried to calibrate via the motion settings (little blue dot didn't move at all), even tried battery pulling, reflashing the ROM, wiping the cache, clearing the cache for System UI and Touchwiz. I don't have a custom recovery flashed. I flashed the unrooted stock ROM and called up AT&T. I've got a new device that auto rotate works now but a bit hesitant to re-root. Has anyone heard of this feature being disabled due to something done during/after root? I've Googled my butt off but couldn't find any issues related to rooting.
Note: I got jumped over the weekend and my phone was swiped. It was later returned to an AT&T store but who knows what it went through. That's my guess as far as why it didn't work anymore (probably thrown/dropped/who knows what) but I just wanted to see if there was a possible software issue that I may not have been able to find.
Cheers!
I recently switched over to slimkat version 8.10 and everything is working like butter so far. The only issue I have come across is anything that needs superuser permissions automatically gets denied. It shows the option on the screen to allow but when i click the field it just does not select., landscape or vertical. I aleady followed the steps to enable developer mode and turn on root access. What could be happening to cause this? It always takes me an hour to configure everything the way i like it so reinstalling would be the last thing I would ever want to do.
I just attempted to use Odin to install cf-auto-root. Still not working. I guess I might opt for the final option... wipe and reinstall rom.
Try flashing supersu from here in recovery:
Super SU 2.16
https://plus.google.com/app/basic/stream/z13tvntrmsmozdc2023wcdp55terwvove
Somehow 2.13 was included with the cf-autoroot that I installed via odin. I did install 2.16 through recovery but I am still having this problem. I mean it doesn't really hurt the usage of the phone... everything is working flawlessly. This is just a rock in my shoe. The only thing I can think might be causing me an issue is that I flashed the dkp kernel. Could that be it?
When you flashed dkp did you clear cashe and dalvik?
Hello,
I had on my Note 2 t0ltecan Dn3V5 and it started to restart ever so often and my youtube app dissapeared and woudnt work. So I tried to wipe the data and it didnt work, from many TWRP versions and Philz recovery. Then i used Odin to install a stock rom, which then finally everything worked and I then tried to restore my Dn3.
Everything worked except my Action Memo which stopped working so I did the procedure again. Samething, so I tried installing Dn3V5 rom instead of restore. It didnt work because it kept saying bad zip, I tried TWRP 2.8+, 2.7.1, 2.6.3, 2.6.1, 2.5 and Philz. Only 2.5 worked but it woudnt boot after the graphic logo. Then i tried again and the same thing. So i restored again and this time it either doesnt boot after graphic logo or I get IMS Framework problem.
What should I do, restore Stock or DN4?? What could my problem be?
UPDATE:
I used odin again to install stock kernel again, this si the farthest I have got with it booting and not restarting. It is still doing that, sometimes more than others, but I have disabled 5 apps, one google play services and the other google chrome. So far so good, nothing has happened but I will have to experiment more.
I have been formating it many times and closing and opening it by taking out battery, will that affect my phone?
UPDATE 2:
I found the problem, I used my bros Note 2 battery and everything ran fine. My original battery died so I had bought a second hand battery. The whole time (for 2 months) it was causing me problems but I did not realize. After ripping the sticker off the battery I figured out it says 2000mAh on the inside XD.
Hi all.
I have a Note 8 GT-N5110 that's still running Stock 4.4.2. It's rooted and has Xposed 2.6.1 installed along with some modules. Last night I flashed TWRP 3.0.2-0 with the intention of flashing Magisk, forgetting at the time that it only works on Lollipop and up. I did not do a backup (I know) and rebooted back to the Stock OS just fine. I updated some Xposed modules and rebooted. Then I added some new Xposed modules, updated AdAway and its host files, and rebooted.
Now I cannot boot past the Samsung logo screen no matter how long I wait. I've gone into TWRP and wiped Dvalik and Cache, which lets me boot past the Samsung logo and get to a screen that says "Android is upgrading, starting the apps." It's been sitting on this screen for about 1 hour, which makes me think I can't boot past it. Any ideas how to easily fix this? If I need a full refresh, can anyone point me to the US version of the Stock 4.4.2 ROM?
This may help: https://updato.com/firmware-archive-select-model?q=gt-n5110&exact=1
Im new to this and im not shure if this is the right place to post this please tell me if its the wrong place
I recently rooted my a8 with magisk, everything worked and I have twrp installed too (DM verity and forceencrypt are both disabled)
I now decided to download zANTI the instalation worked and I read that I would need Busybox for these kind of programs so I installed the Magisk Busybox module and restarted.
The problem is when I start the zANTI app, after a few minutes my phone suddenly goes black and then restarts, this also happens if I try to use the scan funktion, it goes up to 7% and even finds a few host but then when it sais starting nmap it restarts again after a few seconds.
Any help or tips would be appreciated!
Thanks
So far ive tried Zanti 3.19-1, Zanti 3.19, Zanti 3.18
None worked