Related
Hello,
I am totally new to android hacking, so thanks in advance for replying with as much details as possible.
I have an HTC One and wanted to root and install ARHD 70.0.
I rooted unlocked the bootloader, then rooted the phone. All went well.
Default install of ARHD 70.0 (with all checkboxes by default: sense6 tool box, google packages). I also checked the first 2 checkboxes for performances: ext4 setting and nosql setting. Before installing i did a wipe as recommended.
Then i installed ARHD 70.0. Installation went well too.
Upon reboot im in Sense 6 and i'm loving it.
As soon as I reboot, after about 1min, my battery level jumps to a fixed value (77% on that case) and goes down really slowly. Im 100% sure there is not tat much left because the indicator was at 50% just before i rebooted and also right after the phone restarted. After about 1min, it gets to 77% and sticks there.
I reinstalled multiple times (always with wiping first). I tried without Xposed framework and Sense 6 tool box... The issue reappeared after the first restart (from Sense, not from installation of ARHD).
I am pretty sure it's not hardware related because when i was on my unmodified HTC Once with Sense 5.5, it never happened.
I have not (afaik) modified/installed a kernel.
Do you guys know what could be the problem ?
Is there a way to see whats happening once i reboot into a log file so i can see which process affects this ? It always happens after reboot when i'm about 1min in.
Thanks for your help. Tried searching the forums, but i couldnt find anything helpful
EDIT1: AFAIK i must be S-ON since i havent changed anything regarding that
EDIT2: I also tried to update Xposed framework (because it was reporting that it was runnign an old version) through recovery (because im S-On) and then i updated Sense 6 toolbox (cause it needed an update) and it didnt fix my issue.
I
I have a friends S4 here that I rooted for them a while back and installed Xposes + Wanam to make their locked bootloader device a bit more useful. It worked perfectly for many months.
Recently they come back to me to tell me their phone dies very quickly when it is not in use and does get pretty warm. Battery panel shows that Android OS is using majority of percentage and not any more detailed. I realized that it was definitely OTA updated and that Xposed stated that modules were no longer installed nor did Superuser have root. I realized I made a mistake and forgot to disable OTA services.
What I have done so far: Re-rooted by flashing old kernel, flashed back to new kernel. Reinstalled Xposed modules and things SEEM to be perfectly fine. Two days later, the same thing is still happening. Android OS is definitely still hogging the CPU doing something in a loop.
I understand that a possible factory wipe from recovery MAY fix this issue unless System files are messed up and needing to use Odin to restore BUT I figure it'd be a great idea to come here and see if there's a quick fix that may be possible that could also help other readers that have run into the issue of accidentally receiving OTA while rooted.
Thanks for reading.
stevey500 said:
I have a friends S4 here that I rooted for them a while back and installed Xposes + Wanam to make their locked bootloader device a bit more useful. It worked perfectly for many months.
Recently they come back to me to tell me their phone dies very quickly when it is not in use and does get pretty warm. Battery panel shows that Android OS is using majority of percentage and not any more detailed. I realized that it was definitely OTA updated and that Xposed stated that modules were no longer installed nor did Superuser have root. I realized I made a mistake and forgot to disable OTA services.
What I have done so far: Re-rooted by flashing old kernel, flashed back to new kernel. Reinstalled Xposed modules and things SEEM to be perfectly fine. Two days later, the same thing is still happening. Android OS is definitely still hogging the CPU doing something in a loop.
I understand that a possible factory wipe from recovery MAY fix this issue unless System files are messed up and needing to use Odin to restore BUT I figure it'd be a great idea to come here and see if there's a quick fix that may be possible that could also help other readers that have run into the issue of accidentally receiving OTA while rooted.
Thanks for reading.
Click to expand...
Click to collapse
You could downgrade back to nc5 by flashing the tar file. Nc5 tends to be more stable and battery life is decent. I tried running nk1 for awhile, running into the same issues. I went back to nc5 running echoerom v39.1
Edit: They do keep coming!
I looked into doing it, and there is no way in hell that I should be a) doing it, and b) unleashing it onto the world. It would be bad.
I only have the one phone to test it on and can't risk messing it up and I don't have the experience to work on it if it didn't come out perfectly.
I expect that it will be the last Sprint ROM released for this phone, We're nearing the end of support, so it would be good to have these final versions "fixed" and available
...on the off chance a few developers will jump right in and cook up a few mega ROMs for us.
DQG1 Root and Xposed (rewritten)
On a related note, I installed stock DQA1 DQG1, using the usual CF Autoroot, battery pull thingy process Odin for the ROM and TWRP, then booting once, booting into recovery, and then installing SuperSU and it rooted fine. No loss of settings or anything else as far as I can tell.
I did have to install the latest versions of the Xposed files. After rooting and custom recovery (TWRP works fine), install XposedInstaller_3.1.4.apk first like any other apk, then go to recovery and install Wanam v87.1-alt-sdk23-arm-custom-build, but everything (Xprivacy, etc.) worked fine. Keep in mind, you HAVE to use the "alt" (see the "alt" in the file name above?) version or else it won't work. Samsung made some changes, blah, blah, blah. Much thanks to Wanam!
New side note: I did do a factory wipe, and even after reinstalling everything, and using a ROM that contains bloatware, I still have like 40% more space on the phone. I truly don't know what happened there.
Anyone have any thoughts as to kernel? I downloaded Emotion r26 RC1, and BeastModeKernel 1.0BETA, but I haven't tried them yet.
EDIT: Emotion r26 RC1 works fine, but it doesn't seem like CPU freqs are ever going to stick.
No surprise that neither Emotion nor BeastModeKernel worked; I haven't seen anything else that may.
Thoughts anyone?
Both kernels are good, emotion has a few more options to tweak but I took an update a month or two ago and run NotEdge ROM fine , I just use SO launcher with it because I like TW, also latest xposed is 86.1 and I wish I could do what your asking but it probably would be just as bad you'll be fine with that ROM I just suggested it has everything u just requested just make a nandroid and do it at home in case you do something wrong you can always ODIN back your firmware
Sent from my HTC One M9 using XDA-Developers mobile app
D'oh!!
Eating a little crow here. So far, there have been two three 742 updates, maybe there will be more. Who knows?
But I edited the title of the first post. Again. Again. 741 times.
Do you guys have a link to the stock unrooted rom? My phone is royally screwed right now and still stock. I want to do a clean flash and see if that fixes it.
Over a year later, and the still keep coming.
Hmmmm.
I did take another gander around, but it seems that I would need Linux to do it correctly, so I am still opting out of doing it myself.
mictek said:
Do you guys have a link to the stock unrooted rom? My phone is royally screwed right now and still stock. I want to do a clean flash and see if that fixes it.
Click to expand...
Click to collapse
They all arrive here: https://www.sammobile.com/firmwares/galaxy-note-edge/SM-N915P/ eventually.
Hello i got a note 4 Sprint MM 6.0.1 N910PVPU5DQI5 . i am from Argentina, and i bought the phone used from a guy from USA. (i don`t know how but it`s working with the bands here but i dont know if 4g is working, the guy says it works, maybe i don`t have 4g singal in my zone) .
the phone works fine, but has some srpint stuff and ads that bother me. so i flashed TWRP , and now i am looking for any roms and kernels to flash.
for example, is safe to flash this: https://forum.xda-developers.com/note-4-sprint/development/rom-updated-1-14-2017-t3538051
or should i change something first ???.
After rooting my s9+ with the modified Magisk, my phone sometimes becomes unresponsive. I cannot identify any sort of trigger for this to happen, it just does. The AOD displays but does not update. The notification LED still blinks, but when I go to unlock the phone it freezes and I am forced to soft reset it. I am root with Magisk and have TWRP installed. I followed Max Lee's tutorial on how to root the S9+. Any ideas on why this is happening and how to fix it?
Hey, Did you have any luck with this, i am having the exact same issue?
having the same problem i followed Max Lee video and everything work fine until the phone started freezing
same issue on the G960F/DS....
wonder who can help us regarding with this issue.
For everyone having this freezing after rooting...attention to detail is absolute paramount, go back and re-read the twrp thread by jesec. For those (possibly those having freezing issues) who find that challenging, here is a snippet of jesec exact words..." Samsung implemented security measures such as "Real-time Kernel Protection (RKP)" and "RKP Control Flow Protection".
Those security measures are intended to block control flows such as privilege escalation, memory kernel code modification, etc which are not authorized by Samsung.
If those are not disabled, processes (such as daemon of root solutions) that violated those security rules will fall into deadlock.
Deadlocked processes will then consume large amount of resources (leads to performance issues, battery drains) and eventually crash the system.
Technically it is possible to disable those security measures by hex editing stock kernel but just simply flash a custom kernel is better in my opinion.
TL;DR: Flash custom kernel before root or be screwed.
To reiterate...flash a custom kernel before root or be SCREWED
I'm not saying this is 100% u guys issue, but seems kinda likely?
can someone post links or steps on how to fix this freezing lock screen issue, i tried reading the threads but did not find anything, thanks
I was facing the exact same issue after using his tutorial.
I've tested SOD Killer from the Playstore so far it's working fine! No freezes anymore .
Installing a custom kernel like elementalX should also work.
crs_dev said:
I was facing the exact same issue after using his tutorial.
I've tested SOD Killer from the Playstore so far it's working fine! No freezes anymore .
Installing a custom kernel like elementalX should also work.
Click to expand...
Click to collapse
Can we flash this Elementalx over the N965F_Root_for_OEM_issue_devices/Magisk we already installed ?
I already installed the TWRP, No-verity opt encrypt and the N965F_Root_for_OEM_issue_devices package on my friend's 960F.
I would be really greatful if anyone could help me with this.
I had the same issue after having troubles initially getting Lineage flashed and working on my S9.
I removed Magisk, reset and it still was freezing after a lock.
I reflashed Lineage through TWRP and now all seems to be back to normal with no freeze after lock.
Possibly try the steps I did and see if they worked out for you.
hey guys, you solved the issue?
i experience same Problem..
Any one notice , this issue occurs after we apply lock screen password or biometric security. in my device i notice, when i apply lockscreen password or biometric lock my phone freeze. after i remove all lock and set default to swipe...its not freezing. anyone sees that
I solved the same issue (1 hour ago, so I hope it's fixed now) installing first:
ElementalX Kernel
and than installing:
G965_Root_for_OEM_issue_devices_V5 (the lastest available right now)
Following the instruction on the XDA Thread
Hope this can be helpfull to solve it
Its because of dm verity issues...i assume that you rooted the phone over an odin flashable stock rom. To fix this try installing either a patched stock kernel from Soldiers website or other custom kernels if you consider doing over(under)clocking.
KevAngelo14 said:
Its because of dm verity issues...i assume that you rooted the phone over an odin flashable stock rom. To fix this try installing either a patched stock kernel from Soldiers website or other custom kernels if you consider doing over(under)clocking.
Click to expand...
Click to collapse
What is the different in Soldie between Patched Kernel and ELS custom kernel?
HI, All
I have had Nord 2 three months now. First Nord 2 was in service 3 times. So I got new device. Now this new has been two times at service. I have rooted both with TWRP (denniz) and Magisk of course.
I was wondering if TWRP is causing all the problems or is it just that Nord 2 does not like to be rooted.
And now I am thinking not to root but root has its benefits, so I guess I'll root but which method, TWRP or not.
Have you had problems after rooting? If you have, have you used TWRP and Magisk or just Magisk, no TWRP??
It would be nice if you would share your comments.
Thank you
My experience: if sent in for service, all they do is re-flash stock rom. This is where the problems start! I've been talking with an experienced guy from "The Phone Lab" in The Netherlands, which is the contractor for OnePlus repairs in my country.
Thing is, if your phone got messed up, THINGS REMAIN IN THE MEMORY after re-flashing stock. The ONLY thing that works to get a flawless CLEAN system (once even a TWRP-folder survived, but espacially the partition for your fingerprint etc. tempts to stay currupted in a way leading to several strange behaviours).
So to get a clean system, the "repaircompany" should:
- flash stock rom
- boot into STOCK recovery
- fully wipe
- flash stock rom again
NOW your device will work as stock WITHOUT strange behaviour. Mine has been stock flashed 5 times. I know what I am talking about. Every time different errors, which stopped / got eliminated after wiping inbetween.
The problem is, if you send your device to an OnePlus contractor or OnePlus servicepoint, they will not do this, since even THEY are not aware. Because after a stock flash the phone INTENTS to work normally. Strange behaviour sometimes even starts after set-up.
It's the most frustrating phone I ever had.
exis_tenz said:
My experience: if sent in for service, all they do is re-flash stock rom. This is where the problems start! I've been talking with an experienced guy from "The Phone Lab" in The Netherlands, which is the contractor for OnePlus repairs in my country.
Thing is, if your phone got messed up, THINGS REMAIN IN THE MEMORY after re-flashing stock. The ONLY thing that works to get a flawless CLEAN system (once even a TWRP-folder survived, but espacially the partition for your fingerprint etc. tempts to stay currupted in a way leading to several strange behaviours).
So to get a clean system, the "repaircompany" should:
- flash stock rom
- boot into STOCK recovery
- fully wipe
- flash stock rom again
NOW your device will work as stock WITHOUT strange behaviour. Mine has been stock flashed 5 times. I know what I am talking about. Every time different errors, which stopped / got eliminated after wiping inbetween.
The problem is, if you send your device to an OnePlus contractor or OnePlus servicepoint, they will not do this, since even THEY are not aware. Because after a stock flash the phone INTENTS to work normally. Strange behaviour sometimes even starts after set-up.
It's the most frustrating phone I ever had.
Click to expand...
Click to collapse
Hi and thank you for reply.
That was new to me but explains a lot. But also I remined that my 1st Nord2 got new motherboard (IMEI and S/N was different) and now my new Nord2 has new motherboard. So after replacing motherboard it should be as totally new. But still with 1st device I end up problems. I have not rooted my new Nord 2 because my intention was to find out if it is TWRP which is causing problems or is it the device - hardware vs OS after root rocess regardless TWRP or not.
Basically is Nord 2 working as "normal" devices after rooting or not.
To tell you the truth, I am fed up with this phone too
Hi jis251: we can shake hands. After the 4th (!) stockrom-flash by a OnePlus-servicecenter and still having strange behaviour (for example I was not able to set a fingerprint, the device-motor just kept shaking when I tried), they "decided" that my motherboard was broken. It was switched under warrantee and after that I messed up something and then a "regular" stock-flash didn't work either. You DO need to flash stock (@servicepoint or by yourself), then REBOOT into STOCK recovery, WIPE EVERYTHING, and flash stock again (with OnePlus-tool only they have).
The problem is that OnePlus (and their servicecenters) are NOT aware of this (and probably don't care). But once rooted with strange behaviour this is a must.
For now, fingers crossed, everything seems to work. I have TWRP 3.6 (Denniz) installed, Magisk 24.1, several modules (AFWall Boot AntiLeak, BuiltIn BusyBox, F-Droid privileged Extension, Magisk Bootloop Protector -not sure if this does anything, not tested-, Shamiko, Universal SafetyNet Fix and Zygisk LSPosed.
Also in LSPosed I have 4 modules activated: AFWall+, Disable FLAG_Seure, XPrivacyLua and GravityBox [R].
This setup works and passes SafetyNet without problem. Banking Apps work. The only thing I cannot get to work (keeps detecting root) is my Cupra App (for my car - same as Volkswagen App) as posted here: Cupra
The setup on my OnePlus 7 pro (A10) and Nord 2 5G (A11) - both stock roms - is the same. Both pass banking apps but the Volkswagen/Cupra app they do not. I can live with that as long as that is the only exception. It sucks, but privacy above all ;-)
after a week no broblem with my rooted nord 2 (twrp+ magisk canary) all working as well!
exis_tenz said:
My experience: if sent in for service, all they do is re-flash stock rom. This is where the problems start! I've been talking with an experienced guy from "The Phone Lab" in The Netherlands, which is the contractor for OnePlus repairs in my country.
Thing is, if your phone got messed up, THINGS REMAIN IN THE MEMORY after re-flashing stock. The ONLY thing that works to get a flawless CLEAN system (once even a TWRP-folder survived, but espacially the partition for your fingerprint etc. tempts to stay currupted in a way leading to several strange behaviours).
So to get a clean system, the "repaircompany" should:
- flash stock rom
- boot into STOCK recovery
- fully wipe
- flash stock rom again
NOW your device will work as stock WITHOUT strange behaviour. Mine has been stock flashed 5 times. I know what I am talking about. Every time different errors, which stopped / got eliminated after wiping inbetween.
The problem is, if you send your device to an OnePlus contractor or OnePlus servicepoint, they will not do this, since even THEY are not aware. Because after a stock flash the phone INTENTS to work normally. Strange behaviour sometimes even starts after set-up.
It's the most frustrating phone I ever had.
Click to expand...
Click to collapse
No way. I had my phone serviced at the same place and now I don't get OTA updates anymore and have to install them manually. My Bluetooth is also working less reliably. I had my suspicions but thanks for confirming it.
You DO need to flash stock (@servicepoint or by yourself), then REBOOT into STOCK recovery, WIPE EVERYTHING, and flash stock again (with OnePlus-tool only they have).
Click to expand...
Click to collapse
Just to be clear: is it possible to do by myself? Or is their tool required in this step? But yeah I was really hoping flashing would be as straight forward as with my previous OnePlus phones
Kenaestic said:
No way. I had my phone serviced at the same place and now I don't get OTA updates anymore and have to install them manually. My Bluetooth is also working less reliably. I had my suspicions but thanks for confirming it.
Just to be clear: is it possible to do by myself? Or is their tool required in this step? But yeah I was really hoping flashing would be as straight forward as with my previous OnePlus phones
Click to expand...
Click to collapse
Hi Kenaestic, so you are from The Netherlands as am I? Honestly, I don't know if you can do it yourself. Maybe with the tool from (I mean Pankspoo) you can put back all the partitions etc., get to some kind of "stock-state" and be able to wipe everything in stock recovery. But I am just not sure.
I am kind of "ready" with this phone. I am on version 17 (stock A11) and once rooted I decided to not take anymore OTA's. The phone is just way too unreliable. And it IS my daily driver for work, so I can't risk it. It freaks me out that I can't "normally" flash back a stock rom, an d I am too unexpierenced for ASB, commands, etc. I'm an user, not a programmer.
I got 5 (!) reflashes from The Phone Laband a new mainboard. Once, I got suspicious when a TWRP-folder was STILL THERE after a stock-re-flash. From that moment on, and all the problems with fingerprint and PIN-locks, that something just survives that factory flash (I always managed to mess things up by rooting).
Now the damn thing works (and really I still like it). I came from the OP7pro, but this device is just so much lighter and better in the hand (not top-heavy). It's snappy, it's fast. But in the meantime I will start working on my OnePlus 7 pro to get E/OS running and finally my goal is to de-google. Once that works, the OP Nord 2 will be sold and the OP7 pro will be my back-up phone.
The Nord 2 is good and I love it, but software is a failure. Never a MediaTek-device for me again.
exis_tenz said:
Hi Kenaestic, so you are from The Netherlands as am I? Honestly, I don't know if you can do it yourself. Maybe with the tool from (I mean Pankspoo) you can put back all the partitions etc., get to some kind of "stock-state" and be able to wipe everything in stock recovery. But I am just not sure.
I am kind of "ready" with this phone. I am on version 17 (stock A11) and once rooted I decided to not take anymore OTA's. The phone is just way too unreliable. And it IS my daily driver for work, so I can't risk it. It freaks me out that I can't "normally" flash back a stock rom, an d I am too unexpierenced for ASB, commands, etc. I'm an user, not a programmer.
I got 5 (!) reflashes from The Phone Laband a new mainboard. Once, I got suspicious when a TWRP-folder was STILL THERE after a stock-re-flash. From that moment on, and all the problems with fingerprint and PIN-locks, that something just survives that factory flash (I always managed to mess things up by rooting).
Now the damn thing works (and really I still like it). I came from the OP7pro, but this device is just so much lighter and better in the hand (not top-heavy). It's snappy, it's fast. But in the meantime I will start working on my OnePlus 7 pro to get E/OS running and finally my goal is to de-google. Once that works, the OP Nord 2 will be sold and the OP7 pro will be my back-up phone.
The Nord 2 is good and I love it, but software is a failure. Never a MediaTek-device for me again.
Click to expand...
Click to collapse
Haha ja zeker So this is something I have noticed as well. I'm in the same boat as you. I'm not a programmer and I come from a device where flashing was way easier. But for some reason this phone has persistent data on it that can not be reset or wiped. Maybe it was intended as a security measure. When you flash TWRP you probably noticed you can not boot into it without a commandline on your computer. Otherwise it will completely ignore the volume down + power combination and go straight to booting the OS. So I'm guessing OnePlus made it harder to tamper with the recovery. But for rooting it's only confusing, gives me headaches but most importantly; when you accidentally remove the ADB server authentication you're screwed because there is no recovery to boot into. I'm really hoping the miracle workers in the modding community find a way to work around these things. Because I first just thought it's kinda janky because they used a few work arounds to get TWRP running as fast as possible when the phone came out. But now I just don't know anymore. Anyway, I have an appointment with ThePhoneLab tomorrow and I'll report back if it did anything. Cheers.
exis_tenz said:
My experience: if sent in for service, all they do is re-flash stock rom. This is where the problems start! I've been talking with an experienced guy from "The Phone Lab" in The Netherlands, which is the contractor for OnePlus repairs in my country.
Thing is, if your phone got messed up, THINGS REMAIN IN THE MEMORY after re-flashing stock. The ONLY thing that works to get a flawless CLEAN system (once even a TWRP-folder survived, but espacially the partition for your fingerprint etc. tempts to stay currupted in a way leading to several strange behaviours).
So to get a clean system, the "repaircompany" should:
- flash stock rom
- boot into STOCK recovery
- fully wipe
- flash stock rom again
NOW your device will work as stock WITHOUT strange behaviour. Mine has been stock flashed 5 times. I know what I am talking about. Every time different errors, which stopped / got eliminated after wiping inbetween.
The problem is, if you send your device to an OnePlus contractor or OnePlus servicepoint, they will not do this, since even THEY are not aware. Because after a stock flash the phone INTENTS to work normally. Strange behaviour sometimes even starts after set-up.
It's the most frustrating phone I ever had.
Click to expand...
Click to collapse
I agree to some point... When it comes to rooting and updating when rooted this Phone is a p.i.a. If kept stock it is not to bad... But you want root for a reason. I think it is because of the mediatek processor. But I am struggling with it too. I am on A16, with TWRP, not rooted. I want to go back to stock (locked bootloader), but I am having a hard time to understand how to do it. I would appreciate a step by step guide.... The ones on XDA so-far haven't helped me any further...
Ik zit dus in hetzelfde schuitje... (sorry for the Dutch) really curious if "The Phone lab" can fix it
The Phone Lab can only re-flash stock (not repair). You'll loose all data.