Develop Bugs

Help! Just cannot get rooted!

Hello, I have tried every root on the internet for my samsung galaxy s3 spring android 4.3 and I have the cwm installed and working, and I can flash without the error that you cannot mount the sdcard. I have tried every root and it still says that my phone is not rooted, through root checker and supersu also says that it is not rooted. Please, help! I've used the instructions at www . epiccm . org/2012/06/cwm-recovery-on-all-sgs3-lte-variants.html
I am very frustrated with this, and am about to give up. Please help.
Thanks.
-1998golfer

When i open supersu (i donwloaded it from the app store) it says:
"There is no SU binary installed and SuperSU cannot install it. This is a problem!"

Try flashing THIS in Recovery.

Try the repository for a odin one click @ http://rwilco12.com/

prboy1969 said:
Try flashing THIS in Recovery.
Click to expand...
Click to collapse
Nope. Didn't work =/ Still says I do not have root access in root checker.

still not working
Drennan said:
Try the repository for a odin one click @
Click to expand...
Click to collapse
I can't find what you're talking about but I tried all of the superuser flashable zips (supersu, superuser, and MIUI. None of them worked. They said updating android when I booted, but it still doesn't show as root. It tells me no su is installed and then KNOX comes up telling me that it tried to access a secure area.
Please help

So it sounds like knox is what is killing your attempts. You need to disable it and then reinstall your super user of choice (I like supersu, but I'm sure you can find experts to tell you more about them....). Assuming you have a super user app there, but it is just being squashed, this may work for you...
Go into your explorer of choice (I use explorer es), go into /system/app and find superuser.apk. Select it and force it to install again. When it installs, it will open and tell you that knox is there and ask you if you want to try to disable it. Click ok or yes... I don't recall which, but just get that thing out of there. My guess is at this point, you'll need to actually repeat this process (I did) to get everything "happy"... (repeat the install - but the next time the knox question won't come up).

Cluefree said:
So it sounds like knox is what is killing your attempts. You need to disable it and then reinstall your super user of choice (I like supersu, but I'm sure you can find experts to tell you more about them....). Assuming you have a super user app there, but it is just being squashed, this may work for you...
Go into your explorer of choice (I use explorer es), go into /system/app and find superuser.apk. Select it and force it to install again. When it installs, it will open and tell you that knox is there and ask you if you want to try to disable it. Click ok or yes... I don't recall which, but just get that thing out of there. My guess is at this point, you'll need to actually repeat this process (I did) to get everything "happy"... (repeat the install - but the next time the knox question won't come up).
Click to expand...
Click to collapse
How do i disable knox. I've stopped all the processes and even (tried to) delete all the files pertaining to it. i dont have permission to do so. I tried terminal emulator and it doesnt let me do it.... i type su and it tells me i dont have permission. ive tried flashing zips that claim to disable knox and they dont work.

Cluefree said:
So it sounds like knox is what is killing your attempts. You need to disable it and then reinstall your super user of choice (I like supersu, but I'm sure you can find experts to tell you more about them....). Assuming you have a super user app there, but it is just being squashed, this may work for you...
Go into your explorer of choice (I use explorer es), go into /system/app and find superuser.apk. Select it and force it to install again. When it installs, it will open and tell you that knox is there and ask you if you want to try to disable it. Click ok or yes... I don't recall which, but just get that thing out of there. My guess is at this point, you'll need to actually repeat this process (I did) to get everything "happy"... (repeat the install - but the next time the knox question won't come up).
Click to expand...
Click to collapse
I tried installing superuser.apk using that explorer and it installed. it doesnt ask about knox nor does it mention it... Nothing people suggest seems to help =/

Please... Anyone know what to do?

1998golfer said:
Please... Anyone know what to do?
Click to expand...
Click to collapse
Try going into the Play Store, uninstalling SuperSU and then reinstalling from the Play Store. I think it is also possible to flash an older version of SuperSU and then let the Play Store automatically update it. Just spitballing here.

Mr. Struck said:
Try going into the Play Store, uninstalling SuperSU and then reinstalling from the Play Store. I think it is also possible to flash an older version of SuperSU and then let the Play Store automatically update it. Just spitballing here.
Click to expand...
Click to collapse
Didn't work

1998golfer said:
Didn't work
Click to expand...
Click to collapse
What recovery are you using out of curiosity?
Sent from my SPH-L710 using Tapatalk

Mr. Struck said:
What recovery are you using out of curiosity?
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
Cwm - the version for new s3's

1998golfer said:
Cwm - the version for new s3's
Click to expand...
Click to collapse
I would highly recommend switching to Philz Touch recovery, then starting over with flashing the most recent SuperSU zip. Once you boot back into system, open the SuperSU app, choose yes when it asks if you want to disable Knox, and then let it update the binaries for you via the TWRP/CWM option.

This is the repository thanks to @rwilco12, http://rwilco12.com/ in case if the above option doesn't work. Odin down to a rooted jb, then flash a recovery I use Philz Touch (cwm based) and it works flawless, then choose a ROM. Also able to restore cwm or twrp. Be sure to clean install ROMs and always nandroid.

Good luck. I also recommend using philz. Although this process can be frustrating at times, these members @xda are amazing and will get where you need to be. Again, good luck.

Jessooca said:
These guys are definitely leading you in the right path.
From stock on the latest update. I used CF Auto-Root for the Sprint S3 by chainfire in Odin.... uncheck everything.... then after it's flashed take out your battery and boot into recovery and flash the latest supersu zip file then reboot after it reboots open Supersu and it should ask you if you'd like it to disable Knox.
This is what I did it worked for me with no issues
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Nothing has worked. supersu keeps getting:
1) blocked by knox
2) crashing
please link me to what you are talking about (latest supersu, cf auto root, what version of odin.)
when i try to open supersu knox blocks it. how can i open supersu to get knox disabled?
can i reinstall the latest firmware to get rid of anything i may have screwed up?

1998golfer said:
Nothing has worked. supersu keeps getting:
1) blocked by knox
2) crashing
please link me to what you are talking about (latest supersu, cf auto root, what version of odin.)
when i try to open supersu knox blocks it. how can i open supersu to get knox disabled?
can i reinstall the latest firmware to get rid of anything i may have screwed up?
Click to expand...
Click to collapse
Yes, Odin rooted MK3. Use the Knox Removal in this post after Odining a custom recovery-http://forum.xda-developers.com/showthread.php?p=47812894
{
"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"
}

What I do,
Download stock rooted deodexed ram from this site, also download knox app remover, also download wifi fix.
Load TWRP 2.6.3.0 Recovery. Flash that using odin.
Reboot to recovery (TWRP)
Having the stock ram on the SD card or the internal storage .. install it than before rebooting install knox app remover and wifi fix and boot..
Make sure than to update the supersu and all should be good.
I hope this helps.

[Q] NEED HELP! ROOT GT-I9192 S4 Mini DuoS 4.2.2 XXUBNB1

Hey guys,
i'm new here and i hope, that you can help me with my problem!
I've tried to root my Samsung I9192 S4 Mini DuoS, which is 4.2.2 and XXUBNB1.
I flashed the Custom Recovery (recovery-clockwork-6.0.4.5-serranoltexx.tar.md5) via Odin and after that, I've installed the S4Mini_RootKit_v2.zip via CWM Recovery.
SuperSU is installed, but if I check my root permisson, the message is, that i havent any root rights, although I installed the S4Mini_RootKit_v2.zip.
I can't understand it! I know that KNOX is the problem, and i dont know how to remove it. I've tried a lot of methods, like remove the KNOX files via ES Explorer, but it doesn't work! :crying:
My question: How can I root my Samsung I9192 S4 Mini DuoS with Android 4.2.2 and Built XXUBNB1?
Can I flash the Custom Kernel called "Amestris Kernel V2 for Samsung Galaxy S4 mini Duos (GT-I9192)" which is based of
MK4 on my I9192 with NB1?
THANK YOU!
AND SORRY FOR MY BAD ENGLISH

Follow this guide http://forum.xda-developers.com/showthread.php?t=2494435
Powered by CM11 - M6 snapshot

R_a_z_v_a_n said:
Follow this guide http://forum.xda-developers.com/showthread.php?t=2494435
Powered by CM11 - M6 snapshot
Click to expand...
Click to collapse
Thank You!
I follow the steps but i havent got any root permisson, although SuperSU is installed.
What can I do? Can i install the Amestris Kernel V2 for GT-I9192 via Odin (based on MK4) on my I9192
with NB1 ? KNOX is the problem, I Can't unistall it. But this Custom Kernel can deactivate it...

007lou said:
Hey guys,
i'm new here and i hope, that you can help me with my problem!
I've tried to root my Samsung I9192 S4 Mini DuoS, which is 4.2.2 and XXUBNB1.
I flashed the Custom Recovery (recovery-clockwork-6.0.4.5-serranoltexx.tar.md5) via Odin and after that, I've installed the S4Mini_RootKit_v2.zip via CWM Recovery.
SuperSU is installed, but if I check my root permisson, the message is, that i havent any root rights, although I installed the S4Mini_RootKit_v2.zip.
Click to expand...
Click to collapse
Neither I could achieve root on I9192UBUAMH1 doing the arco method. Also Saferoot failed.
I then flashed PhilZ Touch CWM Advanced Edition, reflashed stock ROM, boot into Recovery and select "PhilZ Sttings" --> "Re-root System (SuperSU)"
That did the job for me.

aguaz said:
Neither I could achieve root on I9192UBUAMH1 doing the arco method. Also Saferoot failed.
I then flashed PhilZ Touch CWM Advanced Edition, reflashed stock ROM, boot into Recovery and select "PhilZ Sttings" --> "Re-root System (SuperSU)"
That did the job for me.
Click to expand...
Click to collapse
did you re-flashed your Stockrom in the Custom Recovery or via Odin?
Can I flash the PhilZ Touch CWM Recovery over my Clockwork-recovery and do "Re-Root system", without reflash stock rom????

007lou said:
did you re-flashed your Stockrom in the Custom Recovery or via Odin?
Click to expand...
Click to collapse
I flashed system.img.ext4 (extracted from Stock firmware) with heimdall after I had wiped the ROM with PhilZ Touch CWM.
I think you should be able to achieve the same with Odin instead of heimdall.
007lou said:
Can I flash the PhilZ Touch CWM Recovery over my Clockwork-recovery and do "Re-Root system", without reflash stock rom????
Click to expand...
Click to collapse
Yes, it might work w/o re-flashing system. In my case I just wanted to make sure there were no leftovers from my previous attempts with arco/saferoot.
Here is a quick summary of all attempts I did:
- arco recovery --> works
- arco root --> fails
- saferoot --> fails
- PhilZ touch --> works
- clean ROM with PhilZ touch --> works
- re-flash Stock ROM (only system.img.ext4) --> works
- re-root with PhilZ touch --> works

aguaz said:
I flashed system.img.ext4 (extracted from Stock firmware) with heimdall after I had wiped the ROM with PhilZ Touch CWM.
I think you should be able to achieve the same with Odin instead of heimdall.
Yes, it might work w/o re-flashing system. In my case I just wanted to make sure there were no leftovers from my previous attempts with arco/saferoot.
Here is a quick summary of all attempts I did:
- arco recovery --> works
- arco root --> fails
- saferoot --> fails
- PhilZ touch --> works
- clean ROM with PhilZ touch --> works
- re-flash Stock ROM (only system.img.ext4) --> works
- re-root with PhilZ touch --> works
Click to expand...
Click to collapse
THANK YOU SO MUCH!
I will try it out today, but I have still a little question:
Does the PhilZ touch Recovery root my phone without any Zip file, i mean automaticly???? And does it works (with KNOX and with 4.2.2)?

Use saferoot,
But I the Knox notifications was preventing root access just force close all knox related apps on applications manager then open supersu, worked for 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"
}
If you have cwm recovery you have all you need
Solution 1) mount system and use aroma file manager to delete all the Knox related apps then reboot and update supersu,
Solution 2) You could also flash a rom cleaner script to delete all bloatware including Knox stuff reboot and update super su
Sent from my GT-I9192 using Tapatalk

007lou said:
I will try it out today, but I have still a little question:
Does the PhilZ touch Recovery root my phone without any Zip file
Click to expand...
Click to collapse
Yes, the re-root option of Philz CWM did that in my case. At least so I was able to run 'su' when in adb shell. You might have to install SuperSU additionally for running Android root apps.
I'm not on Knox, so I'm not of much help there. As far as I understood though, it doesn't prevent you from any rooting but will set a flag when you flash any custom firmware. By applying the arco root I guess you've triggered that flag already though. As fburgos said the Saferoot way should not trigger that flag, but it failed to run on my device.
007lou said:
THANK YOU SO MUCH!
Click to expand...
Click to collapse
Don't say that, just hit the "Thanks" button

aguaz said:
Yes, the re-root option of Philz CWM did that in my case. At least so I was able to run 'su' when in adb shell. You might have to install SuperSU additionally for running Android root apps.
I'm not on Knox, so I'm not of much help there. As far as I understood though, it doesn't prevent you from any rooting but will set a flag when you flash any custom firmware. By applying the arco root I guess you've triggered that flag already though. As fburgos said the Saferoot way should not trigger that flag, but it failed to run on my device.
Don't say that, just hit the "Thanks" button
Click to expand...
Click to collapse
I have a new problem, my Phone doesn' have Connection of mobile Data, so i can't use Internet outside (wifi works). I have checked the APN but its all right. The phone accepts the sim card, but i cant use the mobile data
What can I do?

Dear All,
I tired to root my devise Samsung GT-I9192 build I9192XXUBNB1 but I couldn't I tried Odin and Kingo from PC. I want only to root my phone not to install any custom rom

[RECOVERY][unofficial][anthias / zenwatch] TWRP 3.0.2

TWRP recovery 3.0 zenwatch
How to install ​Use this giude to unlock bootloader and boot fastboot/recovery
http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623
Warning ! Unlock bootloader wipe your data!​
update
Twrp 3.0.2 For android wear 1.4
NOT INSTALL ON ANDROID WEAR 1.3 !
Download twrp 3.0.2
installation
Code:
fastboot flash recovery twrp-3.0.2_anthias.img
Photos
{
"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"
}
Stock Recovery for Android Wear 1.4
installation stock recovery
Download stock recovery
Code:
fastboot flash recovery recovery_MEC23S.img
OLD VERSION FOR ANDROID WEAR 1.5 / TWRP 3.0 /TWRP 3.0.1
Download twrp 3.0.1-0 Zenwtach AW 1.4
Download twrp 3.0
OLD VERSION FOR ANDROID WEAR 1.3 / TWRP 2.8.7.0
old version (for android wear 1.3) download twrp mega.nz
Reboot into bootloader and flash recovery
Code:
fastboot flash recovery twrp_2.8.7.0_anthias.img
source https://github.com/asyan4ik/asus_anthias/tree/master

acbka said:
Twrp recovery 2.8.7.0 zenwatch
How to install ​
Use this giude to unlock bootloader and boot fastboot/recovery
http://forum.xda-developers.com/zenwatch/general/guide-how-to-access-recovery-zenwatch-t3167623
Warning ! Unlock bootloader wipe your data!
download twrp basketbuild.com
Reboot into bootloader and flash recovery
Code:
fastboot flash recovery twrp_2.8.7.0_anthias.img
Click to expand...
Click to collapse
I am not able to download the file. Getting a 404 error off the page. Any chance you could upload it to another service?
Thanks in advance!

btonetbone said:
I am not able to download the file. Getting a 404 error off the page. Any chance you could upload it to another service?
Thanks in advance!
Click to expand...
Click to collapse
Same. Thanks.

Ups , i fix this today ...
Sorry

hecksagon said:
Same. Thanks.
Click to expand...
Click to collapse
reload to mega . sorry

Fantastic! Flashed it and used it to flash a Wear version of SuperSU. Watch is rooted, without having to use KingRoot!
Let's see, somebody posted a system image a while back, didn't they? I guess I could flash that to unroot if there's a firmware update.

CSX321 said:
Fantastic! Flashed it and used it to flash a Wear version of SuperSU. Watch is rooted, without having to use KingRoot!
Let's see, somebody posted a system image a while back, didn't they? I guess I could flash that to unroot if there's a firmware update.
Click to expand...
Click to collapse
Yes, I pulled a system image and another user modified to successfully pass the checks that occur during updates (the original pull didn't pass). Check out this thread: http://forum.xda-developers.com/zenwatch/development/root-t3163248
Makes sure you read up on it, though, as it sounds like you'd need to do some legwork to get the system image to work. Relevant posts in that thread are 32, 52, and 54.
Hopefully, though, having TWRP means that someone smarter-than-I-am may develop even more elegant solutions!
Cheers!

Now that we have twrp we can do a system pull from an unrooted device. The system image posted in the other thread will only work on the previous version of Android Wear. Do not flash if you are up to date.

Flashing the system.img for the ZenWatch on LCA43 does work but I wouldn't recommend it (I had to recently wipe my watch to test something), as long as you do an update path from flashing to directly flashing the OTA zip, but it's long winded (of course now that we have TWRP, updates and flashing back to "stock" will be so much easier). That, and KingRoot seems to leave a lot of trace files.
Also as a sidenote, because of SuperSu, I was able to install Stericson's BusyBox from the app (sideloaded apk). KingRoot's root authorization window didn't play well with Android Wear.

itechnoguy said:
Flashing the system.img for the ZenWatch on LCA43 does work but I wouldn't recommend it (I had to recently wipe my watch to test something), as long as you do an update path from flashing to directly flashing the OTA zip, but it's long winded (of course now that we have TWRP, updates and flashing back to "stock" will be so much easier). That, and KingRoot seems to leave a lot of trace files.
Also as a sidenote, because of SuperSu, I was able to install Stericson's BusyBox from the app (sideloaded apk). KingRoot's root authorization window didn't play well with Android Wear.
Click to expand...
Click to collapse
The current system image in the other thread still has Kingroot on it. After removing that I tried to flash SuperSU but that force closes. Would like to get somebody who has not rooted to do a twrp backup and post it. We should be able to make a new flashable clean system image from that.

hecksagon said:
The current system image in the other thread still has Kingroot on it. After removing that I tried to flash SuperSU but that force closes. Would like to get somebody who has not rooted to do a twrp backup and post it. We should be able to make a new flashable clean system image from that.
Click to expand...
Click to collapse
Make sure you're using this zip file to install SuperSU (it seems to be the same binary as Chainfire's) since the app itself doesn't work, and this one doesn't require authorizations (not completely safe, but it works).
(also, don't forget to unroot from the KingRoot app first; the unroot seems to be clean enough to use Wear SuperSU)

itechnoguy said:
Make sure you're using this zip file to install SuperSU
Click to expand...
Click to collapse
That's the one I used, and it works. (Though there's no authorization popups, as you said.)

Theres an app called Super SUMe, in the Play Store that'll switch out KingRoot for SuperSU. Super easy to do, one click to complete the process. Have no idea if it'll work on watches, but I guess it doesnt hurt to try? Make sure you make backup first, now that TWRP is available..
Hoping to get this watch today! or maybe the Moto360..

Talysdaddy said:
Theres an app called Super SUMe, in the Play Store that'll switch out KingRoot for SuperSU. Super easy to do, one click to complete the process. Have no idea if it'll work on watches, but I guess it doesnt hurt to try? Make sure you make backup first, now that TWRP is available..
Hoping to get this watch today! or maybe the Moto360..
Click to expand...
Click to collapse
It'll probably remove KingRoot successfully, but the Zenwatch can't launch the SuperSU app, so root authorization dialogs never show up (the su binary still gets installed, but it can't do anything without permission from the app first).

Boooooo moto 360. It's sooo damn big.

@acbka How did you set up your build environment? I wasn't exactly sure what to initially use (other than not using the CyanogenMod sources since it doesn't work well with building TWRP; I'm assuming Omni 5?).

itechnoguy said:
@acbka How did you set up your build environment? I wasn't exactly sure what to initially use (other than not using the CyanogenMod sources since it doesn't work well with building TWRP; I'm assuming Omni 5?).
Click to expand...
Click to collapse
hi . i update first message .
add my github

Message for all you zenwatch 2 people.. Don't try to flash this recovery. You will have a soft brick. And with no resources at this time. There is no fix.
Sent from my ASUS_Z00A using Xparent BlueTapatalk 2

Has anyone pulled the stock system partition? I, stupidly, didn't do it before I installed SuperSU. I'd like to be able to go back to stock, if there's another firmware update.

I need a link to the stock recovery.IMG file

Cant install last version of Magisk 26.1 on my phone

When im try to download and install Magisk 26.1 on my phone nothing happend then when i close Magisk and i open again i receive this message : "Update to the full version of Magisk Manager to complete the installation. Do you want to proceed with the download and instrallation?" then i press ok and nothing happend....any tip?

roberto_1986 said:
When im try to download and install Magisk 26.1 on my phone nothing happend then when i close Magisk and i open again i receive this message : "Update to the full version of Magisk Manager to complete the installation. Do you want to proceed with the download and instrallation?" then i press ok and nothing happend....any tip?
Click to expand...
Click to collapse
It seems Magisk can´t redirect to your custom recovery. If your recovery can admit flash the latest Magisk apk as a zip, you can install it directly from there.

SubwayChamp said:
It seems Magisk can´t redirect to your custom recovery. If your recovery can admit flash the latest Magisk apk as a zip, you can install it directly from there.
Click to expand...
Click to collapse
Hi and ty for answer!
Im using custom recovery LR TWRP and i dont know if i can flash from there anyway i never had issue by updating magisk!
i saw other ppl with my same problem and seems like i can fix by unROOT and then install last magisk update 26.1 from zero!
Now im busy and cant unROOT my phone but tomorrow i will doing a fresh install and i let u know if all was good ty!!!

roberto_1986 said:
Hi and ty for answer!
Im using custom recovery LR TWRP and i dont know if i can flash from there anyway i never had issue by updating magisk!
i saw other ppl with my same problem and seems like i can fix by unROOT and then install last magisk update 26.1 from zero!
Now im busy and cant unROOT my phone but tomorrow i will doing a fresh install and i let u know if all was good ty!!!
Click to expand...
Click to collapse
Just to add more on this, waiting for your feedback, it seems to me, not an issue with Magisk itself, but with the inability of the device to be sent to recovery using scripts (Magisk is updated using recovery scripts, not on-the-go), versus the ability to boot to recovery using hardware buttons.

SubwayChamp said:
Just to add more on this, waiting for your feedback, it seems to me, not an issue with Magisk itself, but with the inability of the device to be sent to recovery using scripts (Magisk is updated using recovery scripts, not on-the-go), versus the ability to boot to recovery using hardware buttons.
Click to expand...
Click to collapse
Hi im back!
I did fresh install and i was able to install last magisk 26.1 BUT i received this 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"
}
Then i installed SafetyNet 2.4.0 and both basic integrity and CTS passed BUT everytime i open Magisk i receive the same messages from the first screenshot then i flashed again from magisk last update AGAIN and now seens like all fine...
what caused this problem? im really fixed??? ty so much for your support!!!

roberto_1986 said:
Hi im back!
I did fresh install and i was able to install last magisk 26.1 BUT i received this problem:
View attachment 5891073
View attachment 5891075
Then i installed SafetyNet 2.4.0 and both basic integrity and CTS passed BUT everytime i open Magisk i receive the same messages from the first screenshot then i flashed again from magisk last update AGAIN and now seens like all fine...
what caused this problem? im really fixed??? ty so much for your support!!!
Click to expand...
Click to collapse
Like device can´t sent to recovery, then no way to do it manually, because it´ll pass first for the off state, the script will be lost, probably, flashing first the app, and then flashing the zip through the recovery it is fine.
Anyway, TBH, not updating, atleast for now, won´t suppose a non-go.

roberto_1986 said:
Hi im back!
I did fresh install and i was able to install last magisk 26.1 BUT i received this problem:
View attachment 5891073
View attachment 5891075
Then i installed SafetyNet 2.4.0 and both basic integrity and CTS passed BUT everytime i open Magisk i receive the same messages from the first screenshot then i flashed again from magisk last update AGAIN and now seens like all fine...
what caused this problem? im really fixed??? ty so much for your support!!!
Click to expand...
Click to collapse
Ok > Direct install > "Let's go"

SubwayChamp said:
Like device can´t sent to recovery, then no way to do it manually, because it´ll pass first for the off state, the script will be lost, probably, flashing first the app, and then flashing the zip through the recovery it is fine.
Anyway, TBH, not updating, atleast for now, won´t suppose a non-go.
Click to expand...
Click to collapse
OK so u think its not worth update to 26.1 because there is nothing of relevant yet?
How about Madisk delta instead?
When i install recovery LR TWRP 3.3.1 - 1210 i can ROOT directly from there and its auto install Magisk v20.0.
Ty again for your support!!!

roberto_1986 said:
OK so u think its not worth update to 26.1 because there is nothing of relevant yet?
Click to expand...
Click to collapse
Probably, but what I´m saying is that you won´t have issues if you don´t update, only that annoying message.
roberto_1986 said:
How about Madisk delta instead?
Click to expand...
Click to collapse
Magisk is not the culprit.
roberto_1986 said:
When i install recovery LR TWRP 3.3.1 - 1210 i can ROOT directly from there and its auto install Magisk v20.0.
Ty again for your support!!!
Click to expand...
Click to collapse
I can´t remember what version I was using when succesfully updated Magisk, but, I couldn´t, the same as you, with other version.
The whole issue is that device can´t go directly to the recovery, adb reboot recovery is executed silently, but device can´t reach recovery, all resides in the recovery, try a different recovery, maybe OFR, if you care, and with the same Magisk, and you´ll see that you can.

How To Guide OxygenOS 13.1 (LE2125_13.1.0.500) for global with boot.img files

Hi,
I share with you the files for those who want to update from F21 to Android 13.1 and root the phone.
LE2125 OxygenOS 13.1.0.500
For those who get the message that the backup does not exist when uninstalling magisk by selecting image restore, you will not be able to install the update by uninstalling magisk completely , it will fail.
Here's how to do.
-uninstall magisk by selecting uninstall completely
- once the phone restarts, restart in fastboot mode
- flash the original F21 version boot image (9Pro_F21_Global ) by typing these two command lines
fastboot flash boot_a original_F.21_boot.img
fastboot flash boot_b original_F.21_boot.img
- restart the phone
-now you can install the update (you will need this apk to install the update OPLocalUpdate_For_Android13.apk)
- once the update is installed, you can root the phone.
{
"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"
}

Thanks for share

this update available for op9? if yes then can you provide me link of this latest ota?

Daniha said:
this update available for op9? if yes then can you provide me link of this latest ota?
Click to expand...
Click to collapse
NO, for op9 pro...don't use them for op9.

buu'buu said:
NO, for op9 pro...don't use them for op9.
Click to expand...
Click to collapse
no no I'm asking for this ota rom for op9?

@Daniha
Sorry, I don't have the op9, you have to wait OnePlus or Oxygen Updater provide it.

buu'buu said:
Hi,
I share with you the files for those who want to update from F21 to Android 13.1 and root the phone.
LE2125 OxygenOS 13.1.0.500
For those who get the message that the backup does not exist when uninstalling magisk by selecting image restore, you will not be able to install the update by uninstalling magisk completely , it will fail.
Here's how to do.
-uninstall magisk by selecting uninstall completely
- once the phone restarts, restart in fastboot mode
- flash the original F21 version boot image (9Pro_F21_Global ) by typing these two command lines
fastboot flash boot_a original_F.21_boot.img
fastboot flash boot_b original_F.21_boot.img
- restart the phone
-now you can install the update (you will need this apk to install the update OPLocalUpdate_For_Android13.apk)
- once the update is installed, you can root the phone.
View attachment 5914697
View attachment 5914699
View attachment 5914703
Click to expand...
Click to collapse
Thanks for the info... unfortunately I don't have a computer but, what I do is install F21 stock boot image using Ex Kernel manager and after doing that it allows me to install the update. It's doing the same thing that flashing thru fastboot does except I'm just flashing the stock boot image with a kernel flasher...

TENlll423 said:
Thanks for the info... unfortunately I don't have a computer but, what I do is install F21 stock boot image using Ex Kernel manager and after doing that it allows me to install the update. It's doing the same thing that flashing thru fastboot does except I'm just flashing the stock boot image with a kernel flasher...
Click to expand...
Click to collapse
Thanks, i'll test that at next update.

It keeps displaying: System update installation failed at 0% progress. I have removed magisk completely

Pourek said:
It keeps displaying: System update installation failed at 0% progress. I have removed magisk completely
Click to expand...
Click to collapse
Are you using the System update application? (system update apk.for Android 12)
If not use that...
Also, if you have TWRP installed that will keep the update from working correctly you'll have to install the stock boot image in a kernel manager like EKM. Besides that I'm not sure what else would cause that.. I just updated no problem it took like 2 minutes I didn't even have to flash my stock boot image this time. I thought I would have to after reading
Buu buu's post earlier.

TENlll423 said:
Are you using the System update application? (system update apk.for Android 12)
If not use that...
Also, if you have TWRP installed that will keep the update from working correctly you'll have to install the stock boot image in a kernel manager like EKM. Besides that I'm not sure what else would cause that.. I just updated no problem it took like 2 minutes I didn't even have to flash my stock boot image this time. I thought I would have to after reading
Buu buu's post earlier.
Click to expand...
Click to collapse
I am, i'm probably just going to factory reset and apply the update

Can we assume that updating to this, if rooted, can take the usual route?
1. Restore images in magisk
2. Download update in oxygen updater.
3. Install the update using that other update tool, not the system one.
4. Install magisk to inactive stlot
5. And only then reboot?

nabril15 said:
Can we assume that updating to this, if rooted, can take the usual route?
1. Restore images in magisk
2. Download update in oxygen updater.
3. Install the update using that other update tool, not the system one.
4. Install magisk to inactive stlot
5. And only then reboot?
Click to expand...
Click to collapse
Yeah and I guess you can skip "Restore images" part.
At least I did that every time i updated OSS before I went to a custom rom.

Smedslund said:
Yeah and I guess you can skip "Restore images" part.
At least I did that every time i updated OSS before I went to a custom rom.
Click to expand...
Click to collapse
I was asking about those of us on OOS.

nabril15 said:
I was asking about those of us on OOS.
Click to expand...
Click to collapse
I was on OSS until 2 weeks ago. But nvm.

Did you buy a 2125 model in Europe or are you from Canada?

Thank you for sharing this! How can I use this without root. Thank you

naxos said:
Thank you for sharing this! How can I use this without root. Thank you
Click to expand...
Click to collapse
Can you tell me what exactly you want to do. Version installed? Root?

buu'buu said:
Can you tell me what exactly you want to do. Version installed? Root?
Click to expand...
Click to collapse
Thank you for your time to answer me, I want to install just the new version. My firmware version is LE2123_11.F.75_2750_202303081536
Thanks