Develop Bugs

various problems with rooted z1 compact

hello everyone,
I am having some big trouble with my phone. since the update to lollipop its getting worse.
and now the problems:
1.) I can't reboot to recovery anymore.. it's unbelievable but it doesn't work no more. neither with an app nor manually. (phone off. phone on. press power and volume down simultaneously and let go when Sony logo appears.) tried NTR Utilities which was pre-installed..nope. tried quickboot.. nope.
2.) sometimes when I used my phone a lot I cannot turn off my 3g or my GPS from the status bar. you know you can customize your bar with 3g or hotspot or GPS etc. and my shortcuts in the downer part of the status bar don't work no more. I can press them shortcuts but it won't work. than I have to restart my phone. and it works again..
3.) when my phone is locked and I press the power button to enter my pattern the display gets bright as the sun (seriously!) all the background gets almost white and afterwards it's getting normal brightness again.. still don't know why this is happening..
4.) and sometimes when I want to take a picture the standard camera app says that I don't have a SD card in my phone (I have one ) . so it changes the save directory of the photos. but when I release the SD card and put it back in the phone everything is normal..
anyone has the same issues?
hope one of you guys can help me.
phone:
Lollipop Stock Z1C root

#3 happens to me all the time, stock not rooted 5.0.2, I hope someone replies a solution, I thought I was the only one

none of you ever experienced one of these problems?
Lollipop Stock Z1C root

really.???
no one can help??
Lollipop Stock Z1C root

rakdumafo said:
really.???
no one can help??
Lollipop Stock Z1C root
Click to expand...
Click to collapse
I don't know much, but it may help to know if you're using locked or unlocked boot loader, which kernel, which ROM, which recovery, did you flash any other mods, (xposed etc.)... These things help people help you. I don't know technical stuff, but I know that some ROMs have recovery built in, and some don't, so you have to flash yourself. Some ROMs work with some recoveries and not others. If you're rooted and unlocked BL, it may be as simple as installing Rashr, and flashing a new rec. image. In general, I've found that CM type ROMs do better with TWRP, whereas stock-based work well with CWM. If your BL is locked, it seems like Nut's dual recovery might be best. Use the PC installer for best results if you can't get any recovery at all.
The other problems you described also sound to me like ROM or kernel issues, and not necessarily lollipop related. Did you do a full wipe before updating, (system,data, and cache)? Did you flash a kernel first, etc., etc...
Like I said, I'm no expert, but I've been helped enough that I'm glad to help if I can. You just might need to add some more info.

The issue with a very bright display is true for my phone as well. I guess that it's rom or kernel related...

Heres what I suggest you do since It worked on mine:
1) Unlock your bootloader here.
2) Re-flash Lollipop FW using Flashtool
3) Boot the phone
4) Reboot Into fastboot mode and in Flashtool flash a custom kernel that has a dual recovery and is for lollipop.
5) Once the phone boots, vol - to enter recovery and flash the latest Supersu zip file to get your fw rooted
6) Download SELinuxMode Changer and set it to permissive
7) This should pretty much fix all problems

RMM STATE:Prenormal

So I have been playing with my SM-A520F for a while now.
First I used TWRP and Magisk to root, and as I explained on other post I am now trying to install Magisk directly on the Firmware without using TWRP which trips Knox
So I needed to make a boot.img dump, for which I found a tutorial but I need a UK Firmware. I don't know If this has to do with it but it turned out to be a carrier firmware and I had to delete hidden.img to make it work - The next time I enetred into DL Mode to check if everything was official after flashing, one new item had appeared on the list;
RMM STATERENORMAL
I tried to re-flash my last ROM (was a Russian one) but sadly the 'RMM' didn't disappeared with the UK ROM
I need to know, if it's possible, an explanation of why it appeared (Maybe the firmware? Maybe I flashed to many things on little time?)
When it will will go away. (I heard that you need to have your phone 1 week on without turning it off or rebooting, +168 hours of uptime)
And if after it deactivates I have the risk of it enabling itself back on,
Many questions, but this has literally f*cked my mind up, and a google search hasn't clarified anything, because apparently no body in the world knows what is it for, and Samsung itself will keep its mouth shut about it.

carlosmedia said:
So I have been playing with my SM-A520F for a while now.
First I used TWRP and Magisk to root, and as I explained on other post I am now trying to install Magisk directly on the Firmware without using TWRP which trips Knox
So I needed to make a boot.img dump, for which I found a tutorial but I need a UK Firmware. I don't know If this has to do with it but it turned out to be a carrier firmware and I had to delete hidden.img to make it work - The next time I enetred into DL Mode to check if everything was official after flashing, one new item had appeared on the list;
RMM STATERENORMAL
I tried to re-flash my last ROM (was a Russian one) but sadly the 'RMM' didn't disappeared with the UK ROM
I need to know, if it's possible, an explanation of why it appeared (Maybe the firmware? Maybe I flashed to many things on little time?)
When it will will go away. (I heard that you need to have your phone 1 week on without turning it off or rebooting, +168 hours of uptime)
And if after it deactivates I have the risk of it enabling itself back on,
Many questions, but this has literally f*cked my mind up, and a google search hasn't clarified anything, because apparently no body in the world knows what is it for, and Samsung itself will keep its mouth shut about it.
Click to expand...
Click to collapse
This is not for the A5 but I could only find this (hope this help):
"In download mode the "RMM STATE: PRENORMAL" is gone. that line only appeared after the bootloader was unlocked"
On this post:
https://forum.xda-developers.com/showpost.php?p=74045971&postcount=1076

arys64 said:
This is not for the A5 but I could only find this (hope this help):
"In download mode the "RMM STATE: PRENORMAL" is gone. that line only appeared after the bootloader was unlocked"
On this post:
https://forum.xda-developers.com/showpost.php?p=74045971&postcount=1076
Click to expand...
Click to collapse
Yeah...a few users are testing the 168 hour theory. We will find out what happens in 6 days

carlosmedia said:
So I have been playing with my SM-A520F for a while now.
First I used TWRP and Magisk to root, and as I explained on other post I am now trying to install Magisk directly on the Firmware without using TWRP which trips Knox
So I needed to make a boot.img dump, for which I found a tutorial but I need a UK Firmware. I don't know If this has to do with it but it turned out to be a carrier firmware and I had to delete hidden.img to make it work - The next time I enetred into DL Mode to check if everything was official after flashing, one new item had appeared on the list;
RMM STATERENORMAL
I tried to re-flash my last ROM (was a Russian one) but sadly the 'RMM' didn't disappeared with the UK ROM
I need to know, if it's possible, an explanation of why it appeared (Maybe the firmware? Maybe I flashed to many things on little time?)
When it will will go away. (I heard that you need to have your phone 1 week on without turning it off or rebooting, +168 hours of uptime)
And if after it deactivates I have the risk of it enabling itself back on,
Many questions, but this has literally f*cked my mind up, and a google search hasn't clarified anything, because apparently no body in the world knows what is it for, and Samsung itself will keep its mouth shut about it.
Click to expand...
Click to collapse
Here's the answer to your questions:
The new RMM security is designed to stop the theft of new phones by disabling the OEM-Unlock settings for 168-hours, whenever a non-original/un-signed firmware is flashed.
What you need to do is flash it with a full official stock firmware which was designed specifically for your phone model using Odin v3.13.1 https://forum.xda-developers.com/galaxy-s8+/how-to/guide-flash-oreo-g955fxxu1crb7-using-t3755789, keep it turned on constantly for 168 hours about 7-days (do not restart!), then enable OEM-Unlock. During this waiting period do not touch the phone, do not try to flash anything, just leave it turned on and plugged into the charger.
Finally, flash a custom recovery like TWRP, BUT do not let the system to boot up normally. Immediately after the recovery flash reboot into recovery by holding Vol Up + Home/Bixby + Power, and flash the RMM Disabler zip ( https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22 ) through recovery.
This way when you boot the system, the RMM lock will be already disabled so you won't get locked again.
However, you must redo all these steps again every time you flash a full system firmware, because that enables RMM security again.
Looks like it's only affecting the international Exynos models for now, the US Qualcomm models do not have this RMM yet, but of course Sammy could activate it at anytime with a simple firmware upgrade.

billa said:
Here's the answer to your questions:
The new RMM security is designed to stop the theft of new phones by disabling the OEM-Unlock settings for 168-hours, whenever a non-original/un-signed firmware is flashed.
What you need to do is flash it with a full official stock firmware which was designed specifically for your phone model using Odin v3.13.1 https://forum.xda-developers.com/galaxy-s8+/how-to/guide-flash-oreo-g955fxxu1crb7-using-t3755789, keep it turned on constantly for 168 hours about 7-days (do not restart!), then enable OEM-Unlock. During this waiting period do not touch the phone, do not try to flash anything, just leave it turned on and plugged into the charger.
Finally, flash a custom recovery like TWRP, BUT do not let the system to boot up normally. Immediately after the recovery flash reboot into recovery by holding Vol Up + Home/Bixby + Power, and flash the RMM Disabler zip ( https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22 ) through recovery.
This way when you boot the system, the RMM lock will be already disabled so you won't get locked again.
However, you must redo all these steps again every time you flash a full system firmware, because that enables RMM security again.
Looks like it's only affecting the international Exynos models for now, the US Qualcomm models do not have this RMM yet, but of course Sammy could activate it at anytime with a simple firmware upgrade.
Click to expand...
Click to collapse
I just upgraded my firmware, deactivated Developer options and waited the week.
The RMM security line has disappeared and was replaced by the regular FRP lock. Knox was also tripped

carlosmedia said:
I just upgraded my firmware, deactivated Developer options and waited the week.
The RMM security line has disappeared and was replaced by the regular FRP lock. Knox was also tripped
Click to expand...
Click to collapse
Try to flash it with combination firmware, enable OEM Unlock, remove screen lock and Google account.
Finally disable the RMM app called RLC, and modify the build.prop as posted earlier. If your don't do all those, the RMM lock will re-activate as soon as you try to flash a custom recovery.
Unfortunately simply waiting for a week, will not auto-magically solve all you problems, you must disable it manually.
The reason you had to wait, is to able able to flash signed firmware again.

billa said:
Here's the answer to your questions:
The new RMM security is designed to stop the theft of new phones by disabling the OEM-Unlock settings for 168-hours, whenever a non-original/un-signed firmware is flashed.
What you need to do is flash it with a full official stock firmware which was designed specifically for your phone model using Odin v3.13.1 https://forum.xda-developers.com/galaxy-s8+/how-to/guide-flash-oreo-g955fxxu1crb7-using-t3755789, keep it turned on constantly for 168 hours about 7-days (do not restart!), then enable OEM-Unlock. During this waiting period do not touch the phone, do not try to flash anything, just leave it turned on and plugged into the charger.
Finally, flash a custom recovery like TWRP, BUT do not let the system to boot up normally. Immediately after the recovery flash reboot into recovery by holding Vol Up + Home/Bixby + Power, and flash the RMM Disabler zip ( https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22 ) through recovery.
This way when you boot the system, the RMM lock will be already disabled so you won't get locked again.
However, you must redo all these steps again every time you flash a full system firmware, because that enables RMM security again.
Looks like it's only affecting the international Exynos models for now, the US Qualcomm models do not have this RMM yet, but of course Sammy could activate it at anytime with a simple firmware upgrade.
Click to expand...
Click to collapse
Tbh, I will just stop this root sh*t for a while.
My main concern now is:
Now that there is a way to leave RMM disabled, is there a way to untrip knox?
I just want to untrip it and then install an official firmware to not touch my phone's software for a while, I just had enough for now.
I know this is completely unreleated to the main post but I just feel a new post would be much of an space waste

carlosmedia said:
Tbh, I will just stop this root sh*t for a while.
My main concern now is:
Now that there is a way to leave RMM disabled, is there a way to untrip knox?
I just want to untrip it and then install an official firmware to not touch my phone's software for a while, I just had enough for now.
I know this is completely unreleated to the main post but I just feel a new post would be much of an space waste
Click to expand...
Click to collapse
Unfortunately there's no way for us mere mortals to "untrip Knox". I'm pretty sure Samsung can do it internally but not us, so you just gonna have to live with it. It's not the end of the world, just a flag to tell Samsung that someone has messed with it.

Cannot root my S9

Hi everyone,
this is crazy. I followed different guides on how to root my phone but I get the idea I really have to wait for 7 days to have another chance at rooting, or is this just a myth?
I installed twrp, flashed resurrection remix. I had problems with my camera when trying to record video. I always got green flickering on screen. also not able to record more than 60fps (why? isn't s9 supposed to?).
But what struck me most was the fact that my phone wasn't rooted. When installing supersu in the recovery I get the message "sepolicy failed" or something. I guess this is why I cannot root my phone? Installing superuser from the playstore shows me also that I am indeed not rooted.
What can I do? I am all out of ideas and websites...
Should I reflash stock and do the OEM and odin procedure again, and wait 7 days?

Nairozed said:
Hi everyone,
this is crazy. I followed different guides on how to root my phone but I get the idea I really have to wait for 7 days to have another chance at rooting, or is this just a myth?
I installed twrp, flashed resurrection remix. I had problems with my camera when trying to record video. I always got green flickering on screen. also not able to record more than 60fps (why? isn't s9 supposed to?).
But what struck me most was the fact that my phone wasn't rooted. When installing supersu in the recovery I get the message "sepolicy failed" or something. I guess this is why I cannot root my phone? Installing superuser from the playstore shows me also that I am indeed not rooted.
What can I do? I am all out of ideas and websites...
Should I reflash stock and do the OEM and odin procedure again, and wait 7 days?
Click to expand...
Click to collapse
Try use magisk 16.6 for root issues, ofc when you use custom rom you dont get full camera potential and these green flickers are just minor cosmic bugs.

"Myth" might want to read up more.
You need to flash twrp and flash the no verity file then flash the custom rom
Or even better, flash soldiers rom instead of the resurrection remix. Didnt you read that theres a camera problem?
Better use magisk for rooting btw, use the 16.6

Now I am in a never ending boot sequence loading resurrection remix. I can only hard reset and enter twrp.
I don't know if the installation or magisk did it, because I cannot boot to the system.
anyideas?

Nairozed said:
Now I am in a never ending boot sequence loading resurrection remix. I can only hard reset and enter twrp.
I don't know if the installation or magisk did it, because I cannot boot to the system.
anyideas?
Click to expand...
Click to collapse
try flash rom + gapps and boot system after that boot recovery and flash magisk 16.6 and boot system

Thanks for the advice. I flashed back to stock firmware to have the zerocam mod working perfectly. But now my lockscreen freezes after a few minutes. So I tried to deactivate my phone going into lockscreen. I get the Black screen of Death now instead when the display turns off into sleep mode. Only way out is rebootingby hard reset, power button+volume down.
What can I do?.... Thanks for Any further advice.

not have logo to sharj

I'm root my A2lite(ptchboot and install Magisk)
but i turn off my phone and connect to sharj
is turn down,no go logo to sharj!!!

hosseinj2 said:
I'm root my A2lite(ptchboot and install Magisk)
but i turn off my phone and connect to sharj
is turn down,no go logo to sharj!!!
Click to expand...
Click to collapse
You turned off the phone, and while off, you connected a charger.
You expect to see something on the screen...
I'm not sure if this works because I never have my phone off
It could be the unlocked bootloader rather than Magisk that has caused this?
I'll do some tests tonight.

yes, turn off your phone and connect to charge,you see logo to charge battery!
but I don't have,
I think i flash patchboot this happen

Ok, so first some disclaimers...
1) I am running 10.0.10.0 with an unlocked bootloader.
2) I have both TWRP (3.3.1-dees_troy) and Magisk (19.3) installed.
3) I have a custom splash screen (https://forum.xda-developers.com/mi-a2-lite/themes/splash-image-maker-t3914702).
I turned off my phone and plugged it into the charger.
I saw the Android one logo for a bit.
I saw a battery indicator briefly.
The screen turned off.
I unplugged the phone and tried to turn it on... I'm not sure what was going on but the power button wasn't working, probably the phone was "turning off" after charging?
I plugged the phone into the charger again and it showed the battery indicator, but the screen was flickering on and off. I seem to recall discussion of this on these forums back when I first got the phone. As I said, I don't normally turn my phone off so I don't see this issue.
I did a bit of digging and found this old thread, which suggests that both TWRP and Magisk cause the charging animation to break, and that the phone won't charge while in this state. https://forum.xda-developers.com/mi-a2-lite/help/battery-animation-charge-power-off-t3875783
Both TWRP and Magisk modify the boot partition. I guess they do something that interferes with the charger animation. If I'm reading this right, /init looks at /init.rc and there's a case for running /charger -> /sbin/charger -> /root/charger, which is I guess what is responsible for doing the charging animation.
I found a page where someone describes bypassing this state and just booting the phone when the charger is connected. If I turned my phone off more often, I might be interested in doing this... https://appdictive.dk/blog/android/how-to/2017/04/20/disabeling_offline_charge_on_android/

a1291762 said:
Both TWRP and Magisk modify the boot partition. I guess they do something that interferes with the charger animation.
Click to expand...
Click to collapse
I feel like I'm going to sink a bunch of time into this...
I compared my vanilla and Magisk-patched boot images. It looks like Magisk changes both the kernel (zImage) and init, but not init.rc or charger. The patched image has a backup of the original init on it, so maybe the modified init just does Magisk stuff before restoring the original init and booting normally...
I kind of curious now and interested in trying to poke at this but it's going to be very slow going. Making changes, repacking the boot image, fastboot flashing then powering off and booting with the charger. And it'll be even slower if I can't figure out a way to start adb from that state (or save logs somewhere persistent, not sure if this happens before /data has been mounted).
I wish this phone had a serial port in the headphone Jack like Asus/Nexus devices do... but I couldn't find any information suggesting it has and I'm not about to put voltage into the microphone pin in the hope that it does.

thank you to answer.but I don't understand good
if i flash this file which fastboot my logo charge is come back?and root is working?(my build is v 10.0.9 Android 9)

hosseinj2 said:
thank you to answer.but I don't understand good
if i flash this file which fastboot my logo charge is come back?and root is working?(my build is v 10.0.9 Android 9)
Click to expand...
Click to collapse
No, that does not seem to be the case.
Based on the old thread, you need to go back to stock boot image (no twrp or Magisk) to get charging while off to work again.
I plan to try some tests of custom boot images to see if I can get it to work right, but it may take some time.

a1291762 said:
No, that does not seem to be the case.
Based on the old thread, you need to go back to stock boot image (no twrp or Magisk) to get charging while off to work again.
I plan to try some tests of custom boot images to see if I can get it to work right, but it may take some time.
Click to expand...
Click to collapse
ok , I'm waiting than you

I did a bit of digging...
charger is the binary that runs when you boot with the charger plugged in. It's in AOSP (code for Mi A2 Lite is probably different and probably not open sourced): https://android.googlesource.com/platform/system/core/+/jb-mr1-dev-plus-aosp/charger
I unpacked a few images and looked at the charger binaries. I found that there seems to be many versions of this binary. One for each of Oreo, Pie, TWRP (dees_troy), TWRP (offain).
I found a reference to the MIUI charger binary being used for the Mi A2 Lite Linage build (because it works?)...
https://github.com/33bca/android_device_xiaomi_daisy/commit/47fd114e0062659a840e6bebaf57f4fb77b976c1
I downloaded both the Lineage ROM and a Redmi 6 Pro boot.img and confirmed that Lineage is using the Redmi 6 Pro's chargeonlymode binary.
Alas, when I attempted to pack this into a boot.img and flash it, both twrp and the system failed to start. But that could just be because I can't actually pack a working boot.img...
I was able to copy the binaries onto the phone and run them from TWRP (I use 3.3.1-dees_troy). The binaries fought with the recovery for control of the screen occasionally, but I was able to observe at least some of the binaries apparently working correctly.
- oreo - screen lit but black
- pie - screen lit but black
- twrp 3.3.1-dees_troy - displayed as numbers and text
- twrp 3.3.1-offain - screen lit but black
- lineage - graphical display
I also noticed that when the binary worked, it fairly aggressively turned off the display. I had to press the power button, sometimes several times, to get the display to come on briefly showing the charging image before it turned off again.
When I unpacked my actual boot.img (extracted from the phone), it had TWRP's charger binary (ie. installing TWRP replaces your charger binary?) but when I actually boot the phone, that's not the binary I see. Instead, /sbin/charger is a link to /root/charger, which is the Pie binary. When I boot to TWRP, I see the TWRP charger binary. I wonder if this is something to do with Magisk?
I'm not yet sure what all this means... When I flashed a vanilla image and plugged my phone into a charger, it sort-of seemed to work but the screen turned off quickly. But maybe that's just the "aggressive" screen turning off I noted when I ran the binaries from TWRP?
I'll try to confirm this, plus any difference between having only TWRP, only Magisk or both.
And there's always that Lineage binary, if I can get it packed into a boot.img...

[HELP] what to do on a Boot loop Galaxy A50

Hi everyone, so long story short. my galaxy A50(SM-A505GN) was suddenly in a bootloop.
long story, the phone is doing just fine, everything works well. I was in a middle of a call when it suddenly froze then restarted itself an then voila it's stuck on the "Samsung Galaxy A50 secured by Knox powered by android" Logo WHICH never shows up on startup before. it only shows the samsung logo on startup before, there is a pending update on the notification bar but I have not installed it yet so I don't think that is the culprit. no apps installed before the boot loop. if you need any more info about the phone that I might have missed just mention it. I'll try to answer it the best that I can.
Things I have tried:
wipe cache
wipe data and cache
flash latest stock rom (dumb thing won't let me downgrade)
things the phone can do:
go into recovery mode ONLY if the USB is plugged to a PC/laptop
go into download mode from recovery mode
force restart with volume down + power button
it is still on boot loop even after flashing the stock rom. Is there anything I can do to this phone WITHOUT returning it to Samsung, because we all know why that idea sucks. btw, I live in the Southeast Asia region where the warranty for mobile phone is sooo bad.
more than willing to flash custom ROM into it just so it could return to being usable but unfortunately I can't unlock the bootloader without the doing the OEM unlocking thing on dev options. any suggestion on how I could fix this damn phone would be so much appreciated. I really can't afford a new one right now. Thank you.

This happened with me too. Did you update the security patch which came in as OTA update ?
I think this happened because of the security patch.

youhavereachedsahilkalra said:
This happened with me too. Did you update the security patch which came in as OTA update ?
I think this happened because of the security patch.
Click to expand...
Click to collapse
there is a pending update but I have not downloaded nor install it. looks like I will have to wait next month and try flashing the latest patch.

Bro, install recovery 3.4 and the rom fresh. i had some problem. i fix it intro to recovery with download mode, and go to recovery