Related
Hi, i'm new at this forum and i found a thread to tweak the registry (2486387)
I wants to set the security limit on 'never' on mine Samnsun Ativ-S.
Can anyone explain to me, the steps i have to do, to get this done?(please step by step)
I included a print screen of the phone-settings.
Thanks for your help.
Hi,
My Sprint LG G4 is stuck in boot loop, tried to search the internet to find a method to disable big cores on ls991 but with no success.
Can someone lemme know the way so I can backup up my data?
I apologize, if this has been asked/answered previously.
I have looked too, but apparently the fix called "ILAPO" doesn't support Sprint LS991. ...and especially if you have updated to Marshmallow. The ILAPO fix is apparently only Lollipop based flashing , and the LS991 will brick if you try downgrading ZVB MM or above.
There is another type of temporary but risky fix is taking out the board and literally putting it in the oven with specific instructions. It heats up the solder joints on the problematic loose contacts that are defective. Some have had positive success., although most likely temporary.
poog said:
I have looked too, but apparently the fix called "ILAPO" doesn't support Sprint LS991. ...and especially if you have updated to Marshmallow. The ILAPO fix is apparently only Lollipop based flashing , and the LS991 will brick if you try downgrading ZVB MM or above.
There is another type of temporary but risky fix is taking out the board and literally putting it in the oven with specific instructions. It heats up the solder joints on the problematic loose contacts that are defective. Some have had positive success., although most likely temporary.
Click to expand...
Click to collapse
Okay, the oven trick is really risky.
btw I am on lollipop ZVB, which is why looking for alternatives to disable the cores.
A member named "Agimax" posted this in some other thread
Why not just edit the files below for the two large cores (if you have root):
/sys/devices/system/cpu/cpu4/online (open file and change from a one to a zero)
/sys/devices/system/cpu/cpu5/online (open file and change from a one to a zero)
You could also just have the startup file do it (can modify the ripped system partition & put back on phone):
etc/dir/init.qcom.post_boot.sh (find your processor code - 8992 and add echo lines there with the rest of the cpu commands)
Click to expand...
Click to collapse
Can someone vouch that if this works??
Hey there. I recently flashed Resurrection Remix OS on my My Mi A2 and rooted with Magisk. After that, for a purpose , I wanted to change the MAC address of my phone(Mi A2) to my previous phone's MAC Address , for which I did install a application from Playstore called "Change Mac Address". I gave that Root access and tried to change it , it showed success but it indeed didn't change the mac. After that i Tried installing 2-3 different apps and they also failed to change it. Few mintues later I rebooted my phone and I see that my MAC has been changed to the MAC address I wanted to change and its now permanent. I tried rebooting several times and it has been the same. And Also I don't remember my original mac address so I don't know what to do . Now please tell me what should i do , and how can i get my original MAC address back to Original . And yes when i reboot my phone it first show mac address as (02:00:00:00:00).. something like this untill i turn on my wifi. I'm a bit worried about this issue . And please tell me what should I do and does changing mac affects my Phone's performance ?!
Try flashing stock modem.img from your rom / from PIE
Erecik, will it wipe all my data and how I can I find the file?
you have the original mac on the box of the phone
before the wifi is turned on the mac address is always 02:00:00...
dont mess around with flashing the modem img, you can break a lot of other things, the app has written the new mac on the efs of the phone, only way to revert is to write the original from the box
laviniu_c said:
you have the original mac on the box of the phone
before the wifi is turned on the mac address is always 02:00:00...
dont mess around with flashing the modem img, you can break a lot of other things, the app has written the new mac on the efs of the phone, only way to revert is to write the original from the box
Click to expand...
Click to collapse
Thank you so much for the help man. Can you tell me how it happened or is it caused because I used several apps(each app has its own way to change) ? And also Tell me which is the best Mac changer app that I can use without any problem. Please give me link to that app. It will be so kind of you.
just pick the one with the best user reviews on the play store, use just one, doesn't matter which one. whichever you use, you probably need to set, it, restart the phone and then the new mac will show.if you write the original mac from the box it will be like you never changed it.
even if you then uninstall the app i t should still keep the previously set mac.
laviniu_c said:
just pick the one with the best user reviews on the play store, use just one, doesn't matter which one. whichever you use, you probably need to set, it, restart the phone and then the new mac will show.if you write the original mac from the box it will be like you never changed it.
even if you then uninstall the app i t should still keep the previously set mac.
Click to expand...
Click to collapse
Okay I didn't knew that we have to restart after changing the Mac. And also the first app didn't change Mac even after restarting so that maybe not working I'll use another app. Thank you so much man . I'll reply here or dm if I get any other query. Thank you so so much
no problem, sorry i've never used many of them so i can't recommend any, i just know how they work (they basically write with root the efs file that holds the mac address of the wifi chip) so it's quite normal for the os to need a restart before the change is "seen"
laviniu_c said:
no problem, sorry i've never used many of them so i can't recommend any, i just know how they work (they basically write with root the efs file that holds the mac address of the wifi chip) so it's quite normal for the os to need a restart before the change is "seen"
Click to expand...
Click to collapse
Thanks. There is also a issue with my newly flashed rom and that issue is about speaker sound . I made a thread about it( https://forum.xda-developers.com/mi-a2/help/low-speaker-volume-sound-installing-rr-t3927310) and still no one has replied. So if you can help me please also do check out that thread. I'm new to XDA so I'm directly pasting the link here. ? Thanks
cant help you there undortunatly, i havent installed the rr on mine... ever.. maybe search the thread whre you found the rom, high chances someone ran into the same issue and might know how or if it can be fixed...
Hi. I wonder if others see this same, odd behavior with their clocks? I have a 405QA with Pie 20e firmware, bootloader unlocked, rooted with Magisk, TWRP, etc.
At first, I noticed the clock inside of TWRP was not correct - showing a date from 2018. I kind of expected this as I have found incorrect time in TWRP on some of my old devices as well (although I could swear that early on after TWRP install, etc the clock in TWRP was correct - or close enough that I did not notice).
Then I noticed that if I: turn off wifi, turn on airplane mode, and reboot the phone that the clock is not correct when the reboot is complete - again showing a date from 2018.
If I then turn on wifi or turn off airplane mode, the time gets updated from the network as I expect and all shows correctly.
So the question is: is this device expected to be this way (none of my old Samsung and other devices do this)? Or is the result of something I have done in modifying my device? And, if the latter is so, how can I fix this?
Thanks for your time and help.
whitedavidp said:
Hi. I wonder if others see this same, odd behavior with their clocks? I have a 405QA with Pie 20e firmware, bootloader unlocked, rooted with Magisk, TWRP, etc.
At first, I noticed the clock inside of TWRP was not correct - showing a date from 2018. I kind of expected this as I have found incorrect time in TWRP on some of my old devices as well (although I could swear that early on after TWRP install, etc the clock in TWRP was correct - or close enough that I did not notice).
Then I noticed that if I: turn off wifi, turn on airplane mode, and reboot the phone that the clock is not correct when the reboot is complete - again showing a date from 2018.
If I then turn on wifi or turn off airplane mode, the time gets updated from the network as I expect and all shows correctly.
So the question is: is this device expected to be this way (none of my old Samsung and other devices do this)? Or is the result of something I have done in modifying my device? And, if the latter is so, how can I fix this?
Thanks for your time and help.
Click to expand...
Click to collapse
Grab this and flash, disables rctd
https://forum.xda-developers.com/lg-v30/development/stock-anykernel-3-rctd-remover-t3953692
R800x_user said:
Grab this and flash, disables rctd
https://forum.xda-developers.com/lg-v30/development/stock-anykernel-3-rctd-remover-t3953692
Click to expand...
Click to collapse
thanks for this. i had previously found where this was being started and commented it away as shown here. In reading the thread you pointed at, it references files with correct names but different locations on my phone. However, I followed those as clues and did find other places where RCT was being referenced. I commented those as well although I do not think they were much of a threat.
Are Your Clocks Right - Without Network?
As posted above, my 405QA7's clock in Android/TWRP is not correct if there is no network connection.
But I have just found the following strangeness as well:
1. Turn off wifi and turn on airplane mode.
2. Go into settings and turn off automatic time + set the correct time manually.
3. Reboot and discover that your manually set time is no longer there.
I also note that even though I have set the time to manual mode, as soon as I turn on networking it is updated. This doesn't seem quite right either.
Does no one else see this? Or is it a by-product of my unlocking, TWRP, Magisk, or mods?
Thanks
Grab this and flash, disables rctd
https://forum.xda-developers.com/lg-...mover-t3953692
Click to expand...
Click to collapse
What does rctd have to do with the clock?
In any case, when I read up on what the rcdt file does from this post in your linked thread, the terminal emulator indicated that there is no rcdt output. So perhaps the v40 with the LG KDZ is immune from it.
[NG]Owner
I inherited a Moto G6 XT1925-7 RETAPAC on Stock ROM. After resetting and going through the normal initial setup there was a notification of an OTA update that's available. I updated the ROM and after the reboot the screen started to flicker with the screen split into 2-3, showing the same parts of the screen in a distorted manner. The screen itself is impossible to view, but still registers the touches when I press the locations of where a button would've been on the screen.
Bootloader was locked when this happened. I have since been able to unlock the bootloader.
The flickers happen in fastboot (not very often) and recovery as well (worse in TWRP and OrangeFox than stock recovery).
Would this be a bootloader issue? Would I be able to overwrite the bootloader with another version since this is supposedly the latest and last version available? Or is it time to move on, and label the phone as beyond repair?
Appreciate all thoughts and assistance.
Try unlocking bootloader and reflashing stock rom. If the issue is still there after this try a custom rom. If issue is also in this other rom then the screen is bad and needs replacement. I never had any issue with screen flickering after an OTA update. You can download it here: https://mirrors.lolinet.com/firmware/moto/ali/official/RETAPAC/
mrsiri said:
Try unlocking bootloader and reflashing stock rom. If the issue is still there after this try a custom rom. If issue is also in this other rom then the screen is bad and needs replacement. I never had any issue with screen flickering after an OTA update. You can download it here: https://mirrors.lolinet.com/firmware/moto/ali/official/RETAPAC/
Click to expand...
Click to collapse
Ya, have tried both stock and custom ROMs, same result. Was hoping it was a software issue but I guess it's not. Just the timing of it perhaps, installed update and the issue started.
Unless I come across a cheap screen I will just sell the phone off for parts. There's also a chance the GPU is gone, so replacing the screen won't help.
shapes.online said:
Ya, have tried both stock and custom ROMs, same result. Was hoping it was a software issue but I guess it's not. Just the timing of it perhaps, installed update and the issue started.
Unless I come across a cheap screen I will just sell the phone off for parts. There's also a chance the GPU is gone, so replacing the screen won't help.
Click to expand...
Click to collapse
What if you try to install another GPU driver?
[DRIVER] [9.0+] Adreno 500 Series OpenGL & Vulkan Drivers [[email protected]] [1.1.128]
*** Disclaimer I am not responsible for any damage you made to your device You have been warned What Adreno Graphics Drivers do? Fully release the potential of GPU to continuously improve gaming experience. The main functions are optimize the...
forum.xda-developers.com
Installing new driver and clearing gpu cacge fixed some visual buga on a custom rom I was using.
Unlikely to be GPU drivers if it happens at fastboot and recovery too. Most likely hardware issue. Well, RIP phone!