hi,
so rooting on my redmi note 8 pro has been kind of a roller-coaster, on my old phone (mi a2 lite) patching the boot.img on magisk and then flashing the boot.img from fastboot would work, but for some reason it would result in a bootloop on my reno 8 pro, i also tried the twrp method by flashing the magisk zip and dm verity but that also results in a bootloop, flashing just the stock boot.img works, i've been trying to root this phone with every way i know but it just doesn't work,
any help would be appriciated, thanks.
Hey there,
I would try this method as it works on both MIUI 10 and 11 (on the global rom).
https://forum.xda-developers.com/re...de-unlock-bootloader-flash-twrp-root-t3995919
Don't do DM verity at the end, it causes a boot loop, but do do (lol), "close AVB 2.0", make sure DM verity is unchecked.
All thanks go to pritish1998
gigahurts said:
Hey there,
I would try this method as it works on both MIUI 10 and 11 (on the global rom).
https://forum.xda-developers.com/re...de-unlock-bootloader-flash-twrp-root-t3995919
Don't do DM verity at the end, it causes a boot loop, but do do (lol), "close AVB 2.0", make sure DM verity is unchecked.
All thanks go to pritish1998
Click to expand...
Click to collapse
Hey, sorry for the really late reply, but thank you for your reply, i tried it and it worked wonderfully
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ch3510 said:
Hey, sorry for the really late reply, but thank you for your reply, i tried it and it worked wonderfully
Click to expand...
Click to collapse
Hey ch3510,
No problem, really glad to help, I looked at a lot of different options and this seemed like the most straightforward. All thanks should go to https://forum.xda-developers.com/member.php?u=7443262 pritish1998. I was just his guinea pig, lol.
Related
Hi, i guess I can ask for help here since i don't see a g4 beat Subforum, but anyways.
About a week ago, i tried to flash Xposed, since it's 5.1.1 and there is no custom recovery for the h735, i used FlashFire, and i tried to flash the arm64 version of Xposed, because the phone has a 64bit processor, but it failed, and then i tried the arm version and flashfire flashed the zip without any problem that confused me a lot, i installed AnTuTu to see the version of android, and its running a 32bit version of android, but Why?
I'm so worried about that, is my phone 64 bit or not, it's making me sad.
Thanks for reading my post, and helping me to understand why is this happening
Here is a screenshot, if you need more tell me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welp, first you should hide your IMEI number...
LG G4S/Beat is an ARM64 powered smartphone so, should be running Android 64-bits.
Is it stock ROM or custom? What modifications have you done previously?
bel57 said:
Welp, first you should hide your IMEI number...
LG G4S/Beat is an ARM64 powered smartphone so, should be running Android 64-bits.
Is it stock ROM or custom? What modifications have you done previously?
Click to expand...
Click to collapse
Done, thanks, i'm such an idiot
It's a Stock ROM, Only Root and flashing Xposed
Try flashing latest ROM update? Also, see what other apps like CPU-Z and aida64 then report what they say about your system.
Hey everyone, I made a Flashable zip for fixing headphone wired volume keys in custom rom (tested in aex nougat).
If long pressed, it skip current song like in MIUI.
Reboot to recovery and flash it
(It's not a Magisk Module)
Let me know if it work with your custiom
GenLan said:
Hey everyone, I made a Flashable zip for fixing headphone wired volume keys in custom rom (tested in aex nougat).
If long pressed, it skip current song like in MIUI.
Reboot to recovery and flash it
(It's not a Magisk Module)
Let me know if it work with your custiom
Click to expand...
Click to collapse
ZIP file is corrupted...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reupped attach, thanks
GenLan said:
Reupped attach, thanks
Click to expand...
Click to collapse
Still error, tried many times on many computers on many systems.
Mifo_SVK said:
Still error, tried many times on many computers on many systems.
Click to expand...
Click to collapse
Reupped again. Now must go, sorry for inconvenience
GenLan said:
Reupped again. Now must go, sorry for inconvenience
Click to expand...
Click to collapse
Okey, great, now zip file is correct. But for now I can not test it. Will try later.
The full OTA is also available in Oxygen Updater
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Finally, i was waiting for this version!
Same here was looking for it... glad to see!
Just got it this morning.
And holy crap this website now has more ads on mobile than the Sunday newspaper.
Hmm, my device is now failing safetynet, didn't have any of this before with previous updates.
Anyone seeing the same?
plz delete
No issue with safetynet if this what you mean @emontes
Fre$h said:
No issue with safetynet if this what you mean @emontes
Click to expand...
Click to collapse
It is, yes. I have no idea why , though,it was fine on the previous version.
emontes said:
It is, yes. I have no idea why , though,it was fine on the previous version.
Click to expand...
Click to collapse
Did you try to simply disable any Magisk module then reboot just to the if the culprit isn't there ? Is Magisk Hide engaged ?
You can also try to fasboot boot the correct boot.img that is already patched too and see how the assertion react
Anyone notice any sound issues since the update when watching videos or listening to music? I have to crank the volume way up and there doesn't appear to be any bass.
Did you try to simply disable any Magisk module then reboot just to the if the culprit isn't there ? Is Magisk Hide engaged ?
You can also try to fasboot boot the correct boot.img that is already patched too and see how the assertion react
Click to expand...
Click to collapse
Didn't even think of that,been using edxposed for a while and didn't have any issues until now. Found some other people complaining and saying lsposed did the trick and that was it. Thanks!
This is my first question here.
I have SM-N975F. A couple of days ago I installed 12 version of Android (Official Star Wars, OSW) and got a root access with the help of Magisk 24.1. All is good, but one thing: if it is just stock firmware, then I have 256 Gb on board as expected. But after rooting I have only 32 Gb!
Can anybody explain me what happened? Is it possible to fix that problem?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm also on A12 ( ONEUI 4) and rooted using Magisk 24.1 and everything seems good here. May be you'd like to take a closer look on all the steps which u did to root the device!
U haven't did factory reset after flashing. To solve this just flash same stock rom and directly boot into stocl recovery and perform a factory reset and wipe cache partition
LinhBT said:
I'm also on A12 ( ONEUI 4) and rooted using Magisk 24.1 and everything seems good here. May be you'd like to take a closer look on all the steps which u did to root the device!
Click to expand...
Click to collapse
Yes, you are right. I missed some steps.... Thank you!
rc chanu said:
U haven't did factory reset after flashing. To solve this just flash same stock rom and directly boot into stocl recovery and perform a factory reset and wipe cache partition
Click to expand...
Click to collapse
Thats it! I haven't done factory recet. Now all is good, thank you so much!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello,
I have a question regarding the latest update for MIUI 14 14.0.7.0 EU.
My phone went bricked couple of times, even after clean install (fastboot). There was something call "Find device memory corrupted". So according to one thread, I must clean install from a different Android version, which in this case, A12 and from a custom ROM. So I did that and flash Pixel Experience which is great (PayPal for Google Wallet not working though).
After that I flash the latest MIUI again which is MIUI 14.0.7.0 EU, which in the beginning works greatly. The find device memory notification has disappeared, so I thought the problem disappear.
After a while, when I was surfing the internet, suddenly the phone turned off itself and just stuck on the poco logo. I tried to go to fastboot and recovery mode, which after several times trying, only the recovery mode is reachable. Then I went to the safe mode which is what I using now.
My question is, is this latest MIUI 14.0.7.0 contains bug that making people phone's bricked? I saw lately there's been a surge of thread about bricked phone in our lovely forum.
Thanks in advance for answering my worries.
Try a Xiaomi Eu rom.
The stock rom version for Europe is called EEA.
To avoid any confusion at the level of the title.
NOSS8 said:
Try a Xiaomi Eu rom.
The stock rom version for Europe is called EEA.
View attachment 5913309
To avoid any confusion at the level of the title.
Click to expand...
Click to collapse
Oh yes sorry. EEA it is