Related
Soft bricked Nexus 6? - "Your device is corrupt. It can't be trusted and may not work
I unlocked the bootloader using the Nexus Toolkit (wugfresh) succesfully. However, while installing TWRP Recovery my device now appears soft bricked and I am unable to boot up nor get into Recovery mode.
This is the message I get:
{
"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"
}
It comes on briefly for a second or two, and then the phone shuts down. I attempted the suggestions listed here (
Dismiss the warning
The warning message should go away on its own after about 10 seconds and your device will continue starting up.
If you still see the warning message, you can choose to continue starting up your device by pressing the power button once.)
but they do not work. The phone will not continue to boot into System.
Help?
EDIT: I can get into Recovery Mode now. However, it wont go into TWRP (it did before), it now just has the Android on it's back with the red exclamation triangle reading "No command".
reflash twrp
flash a custom rom
Unlocking the bootloader shouldn't cause that message to show up. What were you expecting the toolkit to do? And do you know what it successfully did?
It happens whenever I try to root the device. I am able to get into the bootloader, and then reflashing to stock resolves the issue. But every time I try to root the device, it refuses to continue to boot into system after flashing the message. In summary, it successfully unlocked the bootloader but wont root/ flash TWRP.
Consult the guy who made the toolkit that ****ed up your phone. You clicked his button, rather then run a short list of well known commands we could help you with, so we have no idea what you did right or wrong... Maybe you didn't click hard enough.
Alternatively, read one of the many many many guides here, and use the single command needed, and if there are any errors copy and paste the console output (using code tags) here and we can sort you out in a minute or two.
Caebron said:
It happens whenever I try to root the device. I am able to get into the bootloader, and then reflashing to stock resolves the issue. But every time I try to root the device, it refuses to continue to boot into system after flashing the message. In summary, it successfully unlocked the bootloader but wont root/ flash TWRP.
Click to expand...
Click to collapse
What root are you using? That is probably the issue. If you use the older style root you need a modified boot image. I suggest the new systemless root.
So to fix this lets do this:
1 Use the toolkit to flash stock and unroot.
2 Flash TWRP
3 Copy the systemless root 2.65 to the !readytoflash folder. Delete the three files that are in there. The are from the old root way.
4 Reboot into TWRP and use it to flash the new root.
When you exit TWRP it will offer to root your phone. Say no. And stop after each step and make sure the phone is ok. So we can tell what went wrong if there are issues.
Thanks, I will give that a shot. FWIW, wugfresh Nexus Toolkit is an established tool and worked like a charm on my Nexus 5. But I also understand that things might be different for the 6 and the toolkit may not be the best option anymore. My fault for that assumption.
I will try TonikJDK's suggestion and report back.
Hi,
Had the same thing...
Really DONT know what the hack with with these wonderful people who developet these tools that do not mention ANYTHING regarding the issu in the main page of their tools here.
I think that you should follow the instructions:
1) Download shamu-mra58k => extract => take bootloader + radio + boot + cache + recovery + system + userdata => compy to platform-tools folder (under SDK).
2) Open CMD (open command prompt...) from platform-tools folder.
3) Type: fastboot devices (to know that pc recognized your N6) & than type the commands as shown at the attached screenshot.
That looks like a Wugfresh NRT log...
But why not go the whole way and use the latest 6.0.1 MMB29K?
https://developers.google.com/android/nexus/images?hl=en#shamu
Caebron said:
Thanks, I will give that a shot. FWIW, wugfresh Nexus Toolkit is an established tool and worked like a charm on my Nexus 5. But I also understand that things might be different for the 6 and the toolkit may not be the best option anymore. My fault for that assumption.
I will try TonikJDK's suggestion and report back.
Click to expand...
Click to collapse
Your not along in getting that message after using the Wugfresh Nexus Root Toolkit as I got the same message on my brand new Nexus 6. The toolkit installed TWRP fine, but somewhere in the three files it asked me to install in TWRP (beta superSU, busybox, and another file), there was a problem. I ended up clicking flash stock + unroot and I did this twice and it worked the second time. Then I locked the bootloader and did a factory reset. So far so good. I will root the device again, but by another method.
However do note that I have used that Toolkit for a Galaxy Nexus, Nexus 7 & very recently with a Nexus Player and its worked great every other time. I think it has something to do with Marshmallow, but I'm not sure.
thinkingbrian said:
Your not along in getting that message after using the Wugfresh Nexus Root Toolkit as I got the same message on my brand new Nexus 6. The toolkit installed TWRP fine, but somewhere in the three files it asked me to install in TWRP (beta superSU, busybox, and another file), there was a problem. I ended up clicking flash stock + unroot and I did this twice and it worked the second time. Then I locked the bootloader and did a factory reset. So far so good. I will root the device again, but by another method.
However do note that I have used that Toolkit for a Galaxy Nexus, Nexus 7 & very recently with a Nexus Player and its worked great every other time. I think it has something to do with Marshmallow, but I'm not sure.
Click to expand...
Click to collapse
Best and easiest method to root Marshmellow imo is to flash TWRP and CF`s latest systemless root zip 2.65.
dahawthorne said:
That looks like a Wugfresh NRT log...
But why not go the whole way and use the latest 6.0.1 MMB29K?
https://developers.google.com/android/nexus/images?hl=en#shamu
Click to expand...
Click to collapse
That's not the NRT log (just flahsed manually by fastboot without any script).
I think with up to 6.0.1 MMB29K(not included) there is no issues.
Just kidding...
I've been running MMB29K for a couple of weeks with no problems. I was just suggesting that if the OP was going to go to the effort of flashing then he/she may as wll use the most recent version. Or even hold off for a few days for the possible new one in January. Hey, that's today...
Caebron said:
Thanks, I will give that a shot. FWIW, wugfresh Nexus Toolkit is an established tool and
Click to expand...
Click to collapse
... it bricks your phone. Unless you know exactly what you're doing. But then you don't really need it anymore.
People, Marshmallow is already past the toolkits. It has an update once a month, and the toolkits don't have time to be updated fast enough. You'll be bricking your phones constantly if you don't learn your stuff.
Caebron said:
I unlocked the bootloader using the Nexus Toolkit (wugfresh) succesfully. However, while installing TWRP Recovery my device now appears soft bricked and I am unable to boot up nor get into Recovery mode.
This is the message I get:
It comes on briefly for a second or two, and then the phone shuts down. I attempted the suggestions listed here (
Dismiss the warning
The warning message should go away on its own after about 10 seconds and your device will continue starting up.
If you still see the warning message, you can choose to continue starting up your device by pressing the power button once.)
but they do not work. The phone will not continue to boot into System.
Help?
EDIT: I can get into Recovery Mode now. However, it wont go into TWRP (it did before), it now just has the Android on it's back with the red exclamation triangle reading "No command".
Click to expand...
Click to collapse
This error is the consequence of a " feature " of marshmallow that checks if your system is modified and issues this error message.
Here is how you "unbrick" your phone after running into a problem like this:
1- Download and flash a stock rom. Make sure all partitions are flashed (i.e. bootloader, radio, kernel (aka boot), recovery, cache, userdata, and system). If you don't know how to do it Google it.
2- Boot into the stock recovery and wipe data, cache, and factory reset.
Now that your system is restored, here is how you root it:
1- copy superSU 2.65 on your internal SD card.
2- reboot into bootloader
3- flash twrp
4- very important: do not boot from the bootloader back into Android, rather boot into recovery.
5- when you are booted into twrp recovery, flash superSU zip. It will both root your phone and patch the kernel so that it doesn't give you that curroptrd phone error.
One last thing, not to rub it in for the gentlemen who posted the question but for other who are considering the easy way of using a toolkit, and please don't get offended by this. No one is against convenience but if you are unable or unwilling to learn few simple commands to unlock and unroot your phone you probably are not the type of user who needs to root the phone and chances are that after using a toolkit something will go wrong and you will have to learn the steps the hard way after the effect. Toolkits are good intentioned tools that should be avoided at all cost.
najoor said:
This error is the consequence of a " feature " of marshmallow that checks if your system is modified and issues this error message.
Here is how you "unbrick" your phone after running into a problem like this:
1- Download and flash a stock rom. Make sure all partitions are flashed (i.e. bootloader, radio, kernel (aka boot), recovery, cache, userdata, and system). If you don't know how to do it Google it.
2- Boot into the stock recovery and wipe data, cache, and factory reset.
Now that your system is restored, here is how you root it:
1- copy superSU 2.65 on your internal SD card.
2- reboot into bootloader
3- flash twrp
4- very important: do not boot from the bootloader back into Android, rather boot into recovery.
5- when you are booted into twrp recovery, flash superSU zip. It will both root your phone and patch the kernel so that it doesn't give you that curroptrd phone error.
One last thing, not to rub it in for the gentlemen who posted the question but for other who are considering the easy way of using a toolkit, and please don't get offended by this. No one is against convenience but if you are unable or unwilling to learn few simple commands to unlock and unroot your phone you probably are not the type of user who needs to root the phone and chances are that after using a toolkit something will go wrong and you will have to learn the steps the hard way after the effect. Toolkits are good intentioned tools that should be avoided at all cost.
Click to expand...
Click to collapse
No offense taken I've rooted quite a few phones although I'm far from being an "expert". The toolkit was really just for convenience, and I went back to using it because it worked like a charm for the Nexus 5. It really was the go-to handy tool. To be sure: As I've stated above, I was able to recover the phone on my own. Still not rooted though, but I'm getting there. Sure, M is good enough on it's own, but frankly I can't wait to get back on a Cataclysm ROM.
najoor said:
Here is how you "unbrick" your phone after running into a problem like this:
1- Download and flash a stock rom. Make sure all partitions are flashed (i.e. bootloader, radio, kernel (aka boot), recovery, cache, userdata, and system). If you don't know how to do it Google it.
2- Boot into the stock recovery and wipe data, cache, and factory reset.
Now that your system is restored, here is how you root it:
1- copy superSU 2.65 on your internal SD card.
2- reboot into bootloader
3- flash twrp
4- very important: do not boot from the bootloader back into Android, rather boot into recovery.
5- when you are booted into twrp recovery, flash superSU zip. It will both root your phone and patch the kernel so that it doesn't give you that curroptrd phone error.
Click to expand...
Click to collapse
Just LOVE how you explain it!
Wish more users will explain these kinds of things in such an "user friendly" way
I used the Chain Fire method and ended up in the same place. I can still access TWRP and fastboot, I am in the process of downloading the stock image.
fyrmd said:
I used the Chain Fire method and ended up in the same place. I can still access TWRP and fastboot, I am in the process of downloading the stock image.
Click to expand...
Click to collapse
You have to flash back to stock first. Marshmallow is checking for system mods, so if you don't undo the previous changes it will trigger again. Flash stock, twrp then 2.65 chainfire.
Caebron said:
No offense taken I've rooted quite a few phones although I'm far from being an "expert". The toolkit was really just for convenience, and I went back to using it because it worked like a charm for the Nexus 5. It really was the go-to handy tool. To be sure: As I've stated above, I was able to recover the phone on my own. Still not rooted though, but I'm getting there. Sure, M is good enough on it's own, but frankly I can't wait to get back on a Cataclysm ROM.
Click to expand...
Click to collapse
... You don't need to root to install a rom.
In fact, while installing the rom you will likely wipe your /system partition and any other partition you mess with to root....
What is it you think rooting actually does? Why are you doing it? What part do you think it will actually play in you installing a rom? Don't just do random ****. Learn what things do, so you can do what you want. This is why people hate toolkits. They promote this kinda of mentality where you just do stuff you don't understand in the slightest.
managed to get twrp working on YB1-X90L (Yoga Book - Android - LTE)
it's my very first try to create sth. like that, so I have absolutely no idea if everything works as it should. (took the twrp from yoga tab 3 pro root thread and changed it to fit my device mainly using this guide and some minor changes on my own)
if you want to try, you do it on your own risk. if sth. breaks, please don't blame me!
I strongly suggest not to flash it, but just boot it via fastboot:
1. download recovery
2. make sure adb is working
3. put the recovery into your adb folder
4. unlock bootloader (attention: unlocking the bootloader does a factory reset. so back up your data before) see here how to unlock bootloader
5. boot into bootloader (either: 'press power + volume up' or use adb typing 'adb reboot bootloader' in terminal
6. open terminal and naviagte to your adb folder (with recovery.img in it) then type: 'fastboot boot recovery_twrp.img' (adapt file name in case you changed it)
7. tablet should reboot and boot twrp
this method does not flash twrp permanently. your stock recovery remains untouched!
!!!BEFORE YOU USE TWRP TO CHANGE ANYTHING, PLEASE MAKE A FULL BACKUP!!!
download: View attachment recovery_twrp.zip
as always... I mainly relied on other people's work. so all credits go to them, e.g. twrp team, joesnose (twrp yoga tab 3pro) and HostZero
screenshots:
{
"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"
}
as i said, it is a beginner's job. so here is what i noticed so far:
twrp freezes after a certain time when not used - I guess it is when twrp goes to 'standby', normally you wake it up again by sliding a button but it doesn't work here.
---reserved---
before you ask...
yes, of course, i have already tried to flash supersu, but unfortunately I had no luck so far. The script always aborts because it fails patching sepolicy of boot.img.
so if anyone knows a solution for this, feel free to help!
edit:
found another way to root, look here
Amazing! I never thought yb would have twrp. I've been looking for a way to install gapps since I bought yb. After my final I will definitely have a try.
Was it stable when you flashed some zip?
AndyVerne said:
Was it stable when you flashed some zip?
Click to expand...
Click to collapse
did backup 2 times and restored all partitions a several times which worked well.
only tried to install supersu, which in general went well although su couldn't patch boot.img (but has nothing to do with twrp I think)
danjac said:
did backup 2 times and restored all partitions a several times which worked well.
only tried to install supersu, which in general went well although su couldn't patch boot.img (but has nothing to do with twrp I think)
Click to expand...
Click to collapse
All right, I wil try to install supersu after take my final exam ,too .
I believe there will be a way to solve it .
(oh ,god , the root seems to have sloved , nice job!)
danjac said:
did backup 2 times and restored all partitions a several times which worked well.
only tried to install supersu, which in general went well although su couldn't patch boot.img (but has nothing to do with twrp I think)
Click to expand...
Click to collapse
I have one question, after I unlock the bootloader, it occurs the "intel ....untrusted,will boot in 5 seconds ", I wanna know how to lock the bootloader again.
AndyVerne said:
I have one question, after I unlock the bootloader, it occurs the "intel ....untrusted,will boot in 5 seconds ", I wanna know how to lock the bootloader again.
Click to expand...
Click to collapse
to lock the bootloader you must have stock recovery...hopefully you din't flash twrp.
I do not really know, whether locking the bootloader will work flawlessly due to the changes made by root
when you lock the bootloader it will once more wipe all data - so back it up before, normally root should stay (although I don't know for sure)
to lock the bootloader just use the following command in terminal:
Code:
fastboot flashing lock
if you are not sure, try to search xda for more information about relocking.
danjac said:
to lock the bootloader you must have stock recovery...hopefully you din't flash twrp.
I do not really know, whether locking the bootloader will work flawlessly due to the changes made by root
when you lock the bootloader it will once more wipe all data - so back it up before, normally root should stay (although I don't know for sure)
to lock the bootloader just use the following command in terminal:
if you are not sure, try to search xda for more information about relocking.
Click to expand...
Click to collapse
Oh, I gave it up... Thanks
Do not get me wrong but you say make a full back up with twrp before doing anything but based on your description twrp cant be installed without unlocking the bootloader which in return erases the device.
Is this catch22 or am I missing something here?
danjac said:
managed to get twrp working on YB1-X90L (Yoga Book - Android - LTE)
it's my very first try to create sth. like that, so I have absolutely no idea if everything works as it should. (took the twrp from yoga tab 3 pro root thread and changed it to fit my device mainly using this guide and some minor changes on my own)
if you want to try, you do it on your own risk. if sth. breaks, please don't blame me!
I strongly suggest not to flash it, but just boot it via fastboot:
1. download recovery
2. make sure adb is working
3. put the recovery into your adb folder
4. unlock bootloader (attention: unlocking the bootloader does a factory reset. so back up your data before) see here how to unlock bootloader
5. boot into bootloader (either: 'press power + volume up' or use adb typing 'adb reboot bootloader' in terminal
6. open terminal and naviagte to your adb folder (with recovery.img in it) then type: 'fastboot boot recovery_twrp.img' (adapt file name in case you changed it)
7. tablet should reboot and boot twrp
this method does not flash twrp permanently. your stock recovery remains untouched!
!!!BEFORE YOU USE TWRP TO CHANGE ANYTHING, PLEASE MAKE A FULL BACKUP!!!
download: View attachment 3994659
as always... I mainly relied on other people's work. so all credits go to them, e.g. twrp team, joesnose (twrp yoga tab 3pro) and HostZero
screenshots:
View attachment 3994696
View attachment 3994697
View attachment 3994698
as i said, it is a beginner's job. so here is what i noticed so far:
twrp freezes after a certain time when not used - I guess it is when twrp goes to 'standby', normally you wake it up again by sliding a button but it doesn't work here.
Click to expand...
Click to collapse
---------- Post added at 09:33 PM ---------- Previous post was at 09:30 PM ----------
So this process messed up your system? Not sure if I understand what is going on there.
AndyVerne said:
I have one question, after I unlock the bootloader, it occurs the "intel ....untrusted,will boot in 5 seconds ", I wanna know how to lock the bootloader again.
Click to expand...
Click to collapse
hajkan said:
Do not get me wrong but you say make a full back up with twrp before doing anything but based on your description twrp cant be installed without unlocking the bootloader which in return erases the device.
Is this catch22 or am I missing something here?
---------- Post added at 09:33 PM ---------- Previous post was at 09:30 PM ----------
So this process messed up your system? Not sure if I understand what is going on there.
Click to expand...
Click to collapse
to your first question:
1. well, here we are not talking about backing up your user data but your rom (stock rom so to speak). if anything goes wrong you can always go back to stock.
2. if you want to peform ota update you can't do it with modified system (ota will fail), so normally you must go back to stock, update, root again
to your second question:
it's just a warning that your bootloader is unlocked, nothing more. it shows with every boot and after 5secs just boots normally.
you can easily find out about the advantages and disadvantages of an unlocked bootloader e.g. here on xda.
I can't thank you enough for this. I live in China and was only able to buy the Chinese version of the Yoga Book, which doesn't come with Google Services installed. However, using this TWRP recovery I was able to flash Google Services (and get root) which makes my Yoga Book so much more useful! Thanks so much!
Have got as far as flashing TWRP, but find that any attempt to backup - to internal storage or sdcard - is cancelled. Have checked on googz but cannot find any specific info. Any help would be appreciated
zamzenos said:
Have got as far as flashing TWRP, but find that any attempt to backup - to internal storage or sdcard - is cancelled. Have checked on googz but cannot find any specific info. Any help would be appreciated
Click to expand...
Click to collapse
which yoga book version?
did you flash it or booted it?
how about a log (--> advanced --> copy to sdcard)?
is 'mount read-only' in 'mount' deactivated?
danjac said:
which yoga book version?
did you flash it or booted it?
how about a log (--> advanced --> copy to sdcard)?
is 'mount read-only' in 'mount' deactivated?
Click to expand...
Click to collapse
Left it overnight and tried again today. It's OK this time. I fiddled with settings, mainly to deselect the read-only system option. Each stage of this process has been pretty frustrating (I'm used to hacking sammy devices - this is first and last time with a lenny). Stuck now trying to get root - it will probably take until tomorrow! btw, ver is YB1 X90F (Europe/UK).
But thanks for taking the trouble to reply. And thanks for giving us the opportunity to hack the YB.
Worked on the wifi version too.
You may not be a developer but you are a pretty smart guy to be able to figure this out on your own, my hat is off to you. I rooted my wifi version of Yoga Book using your instruction and the only notable issue I ran into in the process was that i had to install new Android usb drivers in Windows to get the reboot-bootloader command to work, other than that little hiccup it worked like a charm. One other issue I ran into that was of my own making was that Titanium backup encouraged me to upgrade super user which led to a soft brick, thankfully I'd backed my book up and was able to restore it.
Thanks for taking the time to share this with us because rooting made this device a much better experience.
hi all, Im reslly happy to see the yb can really root. but all i want is to have the google app work on my yb china version.
am not a techy, hence most of the insturction mention here is very strange to me.
if anyone can help to write down the step by step on how to flash twrp and install google app to yb will be great thanks..
please...
kakit78 said:
hi all, Im reslly happy to see the yb can really root. but all i want is to have the google app work on my yb china version.
am not a techy, hence most of the insturction mention here is very strange to me.
if anyone can help to write down the step by step on how to flash twrp and install google app to yb will be great thanks..
please...
Click to expand...
Click to collapse
If you just want to install gapps, there is no need to root.
1. download gapps from opengapps.org. select x86_64 6.0 version. select nano or micro version if only want google play to be worked.
2. put the gapps zip file into your root of your YB.
3. just follow the instructions of this post to boot into TWRP
4. In TWRP, select install zip file from SD, then select the gapps to install
5. after finish, reboot to the system.
6. Done!
---------- Post added at 08:48 AM ---------- Previous post was at 08:44 AM ----------
The problem is that I fail to OTA updated after booting into TWRP and install gapps. Anyone can helps?
@danjac Hi, did you keep the boot to bios option in the reboot menu?
Hi everyone!
As you can see (according to the title), I'm newbie for this.
Is there a way to get rid of/remove/hide this message?
{
"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 was Samsung user for ages, this is my first Huawei device... i hope there is someone who can help & explain 'how to' step by step.
2 .app files downgrade + fastboot oem relock (code) didn't help
Sorry, english is not my native language, thx in advance.
As far as I know, this is how it works! There's no way to remove this message. Cheers!
roottree said:
As far as I know, this is how it works! There's no way to remove this message. Cheers!
Click to expand...
Click to collapse
Yup, I thought so... I expected such an answer, but I still wanted to be 100% sure that could not be undone afterwards. Thank you!
The first time I successfully re-locked it, there was just "Phone: Relocked" message in fastboot mode, but warning still appeared.
I played a bit more with my P9, trying to enable an OEM unlock option at last (wich is ofc unavailable/grayed out).
Now I can not even activate the command for some reason, it says this:
Well, i can live with this if there is no solution. Everything else works fine.
>> trying to enable an OEM unlock option at last (wich is ofc unavailable/grayed out).
Try the following: by Vol+ and Pow boot to eRecovery and take Hard reset with wiping Internal data.
Also, from Settings, Advanced, Backup and reset, Factory reset with Internal memory.
Before, remove password/pin/fingerprint
You can go back to stock and fully relock your bootloader. But for that you have to "rollback" to Android 6 and after you did that you can update normally trough EMUI to the latest version. Your bootloader will be locked again and the message will disappear.
Relocking the bootloader with modifications like root installed is not possible as far as I know.
Rollback will do it for sure but it takes longer (and user did not report which exact stock ROM, cust, etc he has, all that must be taken care when rolling back)
Btw, rollback implicitely includes Factory reset and wiping Internal memory
IMO, Factory reset with wiping Internal memory, directly from Nougat (without rolling back to MM), might be enough to get OEM Onlock button back functional.
After that, relocking Bootloader must work.
Note: If user wants to have Bootloader unlocked, then must live with the Warning on boot.
Unlocked Bootloader (as long as no root nor TWRP) does not prevent OTA.
It is just a warning on boot, nothing more.
Also, locking or relocking Bootloader automatically forces Hard reset
zgfg said:
IMO, Factory reset with wiping Internal memory, directly from Nougat (without rolling back to MM), might be enough to get OEM Onlock button back functional.
Click to expand...
Click to collapse
Nope, i wiped it... i will try to rollback to C900B300 -> C432B210. Thx!
I know that OEM switch is active even with M6 & unlocked Bootloader combined, but I want it active with N7 even with locked BL since i am done with playing, stock rom works smooth, and fast enough.
I will try to relock it again from M6 + OEM unlocked and let you know guys!
EDIT:
C900B300 (android 7) -> fastboot oem relock (code) didn't help, now flashing M6
__________
There is another problem with android 6:
OEM Switch works just fine, but can't relock bootloader. Fastboot command is accepted, but wiping data always fails at 7%
Prolly there is something that I am doing wrong. Not sure if it is flashing or something else.
Can you try wiping with the recovery before? First try TWRP and if it doesn't work then stock recovery.
christopherpfister said:
Can you try wiping with the recovery before? First try TWRP and if it doesn't work then stock recovery.
Click to expand...
Click to collapse
Sorry, could you be more specific? I am still newbie for this.
If You mean:
1. flash twrp recovery => wipe all
2. flash stock from B210 and retry
One more question. I am not sure how to flash full stock firmware?
a: Unzip "update.zip" to sd/dload and VOL+/- & ON combination
b: Flash .APP via fastboot?
What are cust package and public data for? Never flashed 'em to my device.
Even if reset/wiping on relock failed, did you reboot to system and check if OEM Unlock button is now workable (no more grayed)?
danilo0230 said:
Sorry, could you be more specific? I am still newbie for this.
If You mean:
1. flash twrp recovery => wipe all
2. flash stock from B210 and retry
One more question. I am not sure how to flash full stock firmware?
a: Unzip "update.zip" to sd/dload and VOL+/- & ON combination
b: Flash .APP via fastboot?
What are cust package and public data for? Never flashed 'em to my device.
Click to expand...
Click to collapse
That's what I meant. No success?
You have to extract the contents of the zip file into the folder called "dload". The folder has to be on the root of your *external* sdcard.
You need to do that with all available zips, not just the main one!
Otherwise you will be missing some data including huawei applications like the keyboard.
zgfg said:
Even if reset/wiping on relock failed, did you reboot to system and check if OEM Unlock button is now workable (no more grayed)?
Click to expand...
Click to collapse
OEM Button works fine since i am on android 6MM, but to get it work on Nougat i suppose that i have to relock bootloader, atm it's mission impossible to me
christopherpfister said:
That's what I meant. No success?
You have to extract the contents of the zip file into the folder called "dload". The folder has to be on the root of your *external* sdcard.
You need to do that with all available zips, not just the main one!
Otherwise you will be missing some data including huawei applications like the keyboard.
Click to expand...
Click to collapse
Didn't try to mess up with recoveries yet, i guess that i flashed it wrong and that's what causing stock-recovery unable to wipe data.
I will retry to flash it as you said (all files merged in dload) before re-flashing recovery. Thx!
danilo0230 said:
Didn't try to mess up with recoveries yet, i guess that i flashed it wrong and that's what causing stock-recovery unable to wipe data.
I will retry to flash it as you said (all files merged in dload) before re-flashing recovery. Thx!
Click to expand...
Click to collapse
Don't merge the files. I believe they have the same names so that wouldn't work. Do one after another. You can switch the files from your computer while TWRP is running after each flash.
If you are on b182, you should be receiving OTA for Nougat, you don't need to DLOAD Nougat installation
If OEM Unlocking button is functional now, it will stay so when you update to Nougat
I never relocked, I have no problem with the unlocked Bootloader and its warning - but you may try to 'lock' and then 'unlock' again
And double-check iare you using proper code - in other threads people used to report that relocking works
christopherpfister said:
Don't merge the files. I believe they have the same names so that wouldn't work. Do one after another. You can switch the files from your computer while TWRP is running after each flash.
Click to expand...
Click to collapse
Yup, there are same named files. I know that only TWRP can flash .zip -s, but isn't stock firmware without TWRP? Is there any sequence, which file comes first?
zgfg said:
If you are on b182, you should be receiving OTA for Nougat, you don't need to DLOAD Nougat installation
If OEM Unlocking button is functional now, it will stay so when you update to Nougat
I never relocked, I have no problem with the unlocked Bootloader and its warning - but you may try to 'lock' and then 'unlock' again
And double-check iare you using proper code - in other threads people used to report that relocking works
Click to expand...
Click to collapse
Ok then, updating it via OTA with OEM enabled ---> trying to relock again. I Will let you know if i succeeded
__________
Well... i tried to reduce battery drain, that's the main reason why i unlocked it.
Afterwards I found out i am shooting in the dark, it's a common hardware problem for P9 devices.
Code is 100% correct 'coz i am using copy/paste from calculation, thx for support guys!
danilo0230 said:
Ok then, updating it via OTA with OEM enabled ---> trying to relock again. I Will let you know if i succeeded
__________
Well... i tried to reduce battery drain, that's the main reason why i unlocked it.
!
Click to expand...
Click to collapse
If you are concerned about battery,
update up to b397 and install then Magic Rainbow v4
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
It's based on stock ROM but cleaned from bloatware, prerooted with Magisk, etc
Edit: Maybe OTA will stop yoy with b392 or b394.
Use HWOTA methods to update up to L19 c432 b397
https://forum.xda-developers.com/showpost.php?p=74913874&postcount=3
For that, of course, you need unlocked Bootloaderr and TWRP for Nougat
https://forum.xda-developers.com/p9/development/twrp-t3565703
zgfg said:
you may try to 'lock' and then 'unlock' again
Click to expand...
Click to collapse
Yes, but actually nope...
1. OTA automatically updated B210 => B386
2. fastboot relock worked as you said (wiped 100% this time)
3. OEM button still unavailable
4. Checked fastboot: Phone: unlocked; FRP: unlocked;
Damn! Never understood this
I don't understabd what do you really want, if Fastboot shows Phone unlocked, FRP unlocked then you are ready for TWRP, no matter how OEM Unlocking button shows (grayed out but isn't now in ON position?)
Or, you can do once again Rolling back and forth by OYA to Nougat, if you really want locked Bootloader.
zgfg said:
I don't understabd what do you really want
Click to expand...
Click to collapse
I want bootloader locked without any warning message at startup & working OEM button with Nougat if it's even possible in my case?
zgfg said:
if Fastboot shows Phone unlocked, FRP unlocked then you are ready for TWRP, no matter how OEM Unlocking button shows (grayed out but isn't now in ON position?)
Click to expand...
Click to collapse
Yup i know that I can and how to flash TWRP... but do i even need TWRP for that? If yes, how (step by step)?
zgfg said:
Or, you can do once again Rolling back and forth by OYA to Nougat, if you really want locked Bootloader.
Click to expand...
Click to collapse
I'm done with playing with customs, rooting etc, just wanna restore completely clean factory firmware (without warnins, greyed out buttons etc.)
Disclaimer: No guarantees. Follow at your own risk. I am not responsible for bricked phones.
Credits to 4PDA
Prerequisites:
Knowledge of OEM unlocking from Developer options, adb, and fastboot
Knowledge of QPST in case you encounter bootloop, so you can revert to a reliable stock ROM
Unlocked bootloader (from here)
1) Get your bootloader unlocked, if you haven't already.
- Visit https://www.zui.com/iunlock
- Enter the IMEI1 (Second number when you call *#06# with the phone)
- Enter the Device ID from the Bootloader/Fastboot (Hold VOL- and Power, while device is off)
- Enter your email and captcha and set the checkmark to acknowledge voiding your warranty.
- If you get an error saying that your IMEI1 is wrong, put in a sim card and wait a few hours. If it still doesn't work, write an email to [email protected]
- In the developer settings in android, enable usb debugging and oem unlock.
- Flash the sn.img file you receive with fastboot (again, hold vol- and power while the device is off). Command is 'fastboot flash unlock sn.img'. You need compatible usb drivers, qualcom drivers and adb/fastboot to do that. Use google or write me a PM if you have trouble with that.
- execute 'fastboot oem unlock-go'
- This allows you to use fastboot to flash custom system/boot/vendor/vbmeta images
Click to expand...
Click to collapse
@wzsx150's recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img MEGA Google Drive
@wzsx150's TWRP for Android 10 TWRP-3.3.2B-0508-LENOVO_Z5S-10.0-CN-wzsx150-fastboot.7z (extract the IMG file and flash using fastboot)
3) Now you can flash TWRP.
- Download ...
- Flash it from the Bootloader with 'fastboot flash recovery recovery-TWRP-3.3.1-1015-LENOVO_Z5S-CN-wzsx150.img'
- Press VOL UP / VOL DOWN to navigate to recovery.
Click to expand...
Click to collapse
11.3.169: L78071_11.3.169_DEV_FullOTA.zip
11.5.096 Update: ZUI_11.3.169_DEV_TO_ZUI_11.5.096_ST.zip
11.5.111 Update: ZUI_11.5.096_TO_ZUI_11.5.111_ST.zip
Other files, use at your own risk
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Official TWRP for jd2019
In recovery, Format data, then wipe Dalvik/ART Cache, Cache, Data
Reboot to recovery
Install in order, without rebooting, 11.3.169 -> 11.5.096 Update -> 11.5.111 Update.
Install Magisk 20.4
Install TWRP for Android 10 (above) using fastboot if the update replaces stock recovery after rebooting
Edited out from original
Wipe Data and flash Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
In order not to encrypt Data in the future, install Official TWRP immediately after installing updates. Install > Install Image > twrp-3.3.1-0-jd2019.img
Install GApps
Note: I do not know if the 11.5 update relocks the bootloader. It doesn't lock the bootloader.
I had bootloop from OpenGApps. 4PDA post advises to use BiTGApps. You can install Google Play Store from the built-in Lenovo App Center and that's what I did.
Haven't tried disabling dm-verity and forceencrypt.
Good job, my man, I'll check it out tonight and prepare ourselves an updateable package for people coming from any rom to avoid the hassle of going through all of that. As soon as I get it working will release a new TWRP for Android 10.
{
"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"
}
carlshark said:
View attachment 5036881
Click to expand...
Click to collapse
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier
jacoghi said:
Nice job man, so the update works as it should? I'm patching the images and will upload a full ota update to make it easier to move between Pie and 10. Regarding recoverys, did you test any twrp? Any decryption working? What about this official twrp, does it actually work? Thanks for the files man, this will make everything much easier
Click to expand...
Click to collapse
I've been using the phone on 11.5.111 for a couple of days now.
I flashed both the 3.3.2 TWRP of @wzsx150 and the official TWRP and they seem to be working. I didn't turn off encryption so it seems to work well.
Happy to have helped in a small way. Thank you for your hard work!
links not works
vesdan said:
links not works
Click to expand...
Click to collapse
Thanks for the heads up, apparently the original poster removed the links. Will be uploading the ones I used.
Reuploading done.
Thank you very much
Thanks for the rom my friend.
Can you please upload the latest update cause i am rooted and it cannot be installed via the system.
Also guys ,does anyone knows if i can put the latest android 10 with multilanguage rom ?Thank you for everything ,i appreciate.
thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number
sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?
galardo_2 said:
sorry guys, i rushed and flashed the gapps and now facing a bootloop, i prepared qpst and a stock rom but i verz rom i am missing a content.xml file, can anyone please help me?
Click to expand...
Click to collapse
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!
vesdan said:
https://mega.nz/folder/PegDDQ7I#bmCCIt1lAWAe7ui_gkmwSQ/folder/fOAQ1QCa
here is many ROMS
Do not install gapps on ZUI !!!!
Click to expand...
Click to collapse
but the qpst app need an aditional content.xml file, where can i get one
Install global via fastboot, all is included or in qfil ROM is all in zip file
vesdan said:
Install global via fastboot, all is included or in qfil ROM is all in zip file
Click to expand...
Click to collapse
I tried and failed again
i tired and failed again
galardo_2 said:
thx for the post, i am wondering if the ota will be avaliable, because the bootloader unlock site does not approve my imei number
Click to expand...
Click to collapse
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably
carlshark said:
I tried unlocking 2 Lenovo phones. The first attempt had sent me an email, but the second attempt did not. The unlock procedure went through though. So I tried changing the link provided in the first email http://cdn.zui.lenovomm.com/developer/lenovoboot/xxxxxxxx/sn.img (xxxxxxxx - serial number of phone) and it worked. This might not work for you though.
As for the OTA, I really am not sure... Probably
Click to expand...
Click to collapse
after a few atempts (3-4 days) the imei number got accepted, but now i have another problem as you can see, i flashed the gapps and now i have the bootloop and i dont have a clue how to undone it
hello friends I have all the updates installed, but it tells me that there is a new one, where can I download it?
On the other hand, what difference is there between installing by twrp and qfill?
galardo_2 said:
i tired and failed again
Click to expand...
Click to collapse
This is problem with program, drivers sahara. Try fastboot
{
"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"
}
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about doing this to your device
* YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, root your device and more.
Disclaimer:
- I do not claim this work as my own, this thread was created to have an XDA thread for A71 TWRP. I will try my best to keep it up to date with Ian's work, but can't promise that will remain for ever. If you want the latest TWRP and to be notified as soon as its published, be sure to join the Telegram channel.
- I am not responsible about any damage of any kind that this custom binary may cause.
- Please read the whole main post & related ones before proceed and follow the guide as it is wrote. I will not offer support for any issues that have been already stated.
- Your Knox Warranty Bit will be blown once you flash this or others custom binaries, preventing you to use Knox Features. It can't be resetted in any way, so think twice before flashing this.
- Bugs can be reported here in XDA or via our Telegram Group. Please be more clear as possible and make sure you provide detailed info when reporting bugs (device variant and logcat).
How to Install:
First, you need to unlock the bootloader. Here's how to do it:
- Backup all media before proceeding, this will erase everything in your internal storage including music and photos
- Go to developer settings and enable [OEM Unlock]
- Reboot to download mode
- When prompted, press and hold VOL + to enter bootloader unlock mode
- Press VOL + to confirm you want to unlock bootloader, this will wipe your data
- If you think the bootloader is fully unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will still reject any unofficial partitions before VaultKeeper explicitly allows it.
- Go through the initial setup. Skip through all the steps since data will be wiped again later when we flash TWRP and magisk
- Enable developer options, and confirm that the OEM unlocking option exists and is grayed out. This means the VaultKeeper service has unleashed the bootloader. This step is MANDATORY
- Your bootloader now accepts unofficial images in download mode.
After finally unlocking the bootloader, proceed with installing TWRP (tar) with Odin:
- Boot to download mode and load TWRP tar file and VBMeta disabler tar file in AP and BL of Odin, doesn't matter which goes where
- Disable [Auto Reboot] in Odin
- Flash
- Force a reboot by pressing VOL+, VOL - and POWER buttons at the same time
- After the screen goes black, IMMEDIATELY let go of all buttons and IMMEDIATELY press and hold VOL+ and POWER button at the same time to boot to TWRP
- After booting to TWRP successfully, go to WIPE in TWRP
- At the bottom, you should see an option to FORMAT DATA. After you select it, you will be asked to type "yes" in your keyboard. If you do not see this, you probably selected the wrong option.
- After formatting data, flash the Multidisabler zip with TWRP. This is done to avoid future bootloops.
(Optional) Flash magisk.zip to root (google where to find it)
- Reboot to system
- Wait patiently for the device to boot for the first time
How to flash TWRP (img):
- Reboot to recovery
- Select Install
- Select Install Image and search for the TWRP img file
- Flash as recovery
- Reboot to recovery
- Done
Downloads:
twrp-a71-3.5.1_10-A11_2b1_ianmacd.img
twrp-a71-3.5.1_10-A11_2b1_ianmacd.tar
Multidisabler zip by Ianmacd
VBMeta disabler
Source Code: https://github.com/ianmacd/twrp_a71
Source Code: https://github.com/ianmacd/a71
Change log:
17/03/21: Release for Android 11 BL
Credits:
- Samsung for kernel source code
- TeamWin for their awesome recovery
- @ianmacd for compiling, updating, and maintaining for A71
reserved 1
reserved 2
Sorry for the delay, this TWRP should work perfectly with Android 11 BL
Thanks! However, it kept encrypting after booting to Recovery? Already format and flash Multidisabler zip by Ianmacd.
After several tries, it did not encrpt any more. It really beats me. Anyway, great job. Thanks!
@ShaDisNX255 have you came across config files for Link to Windows / Your Phone Companion, namely something to do with features enabled ?
Now that A71 got OneUI 3.1 (A11) I was wondering if there is a way to enable multi-apps in Link to Windows.
I also wonder if this "multi-apps" new feature in A11 needs to be enabled in OneUI too (or maybe there isn't a Link to Windows special toggle at all, only system one).
All I know is that only the high tier Samsung phones has multi-apps streaming to Windows, like S21, Note20, Fold and Z Flip but also last gen S20 and Note10.
Would like to hear your thoughts on this.
EDIT: the backbone of the feature is this: https://www.xda-developers.com/android-q-splitscreen-multitasking-multi-resume/
donkeyman1234 said:
Thanks! However, it kept encrypting after booting to Recovery? Already format and flash Multidisabler zip by Ianmacd.
After several tries, it did not encrpt any more. It really beats me. Anyway, great job. Thanks!
Click to expand...
Click to collapse
Very strange. Hopefully your issue is fixed, I'll try and see what could be wrong. Thanks for the input.
ban.codrut said:
@ShaDisNX255 have you came across config files for Link to Windows / Your Phone Companion, namely something to do with features enabled ?
Now that A71 got OneUI 3.1 (A11) I was wondering if there is a way to enable multi-apps in Link to Windows.
I also wonder if this "multi-apps" new feature in A11 needs to be enabled in OneUI too (or maybe there isn't a Link to Windows special toggle at all, only system one).
All I know is that only the high tier Samsung phones has multi-apps streaming to Windows, like S21, Note20, Fold and Z Flip but also last gen S20 and Note10.
Would like to hear your thoughts on this.
EDIT: the backbone of the feature is this: https://www.xda-developers.com/android-q-splitscreen-multitasking-multi-resume/
Click to expand...
Click to collapse
I haven't used the Link to Windows feature, I don't really have a good understanding of what you mean.
ShaDisNX255 said:
Very strange. Hopefully your issue is fixed, I'll try and see what could be wrong. Thanks for the input.
Click to expand...
Click to collapse
I took a shot of log.
I'm running stock Android 11 and I've tried to make a backup with TWRP but failed with this message:
Can create '/data/media/o/TWRP/ folder (required key not available).
Failed to make backup folder.
It means that I'm encrypted, right ??. If I'm correct, should I format data and flash the new multidisabler ?
EDIT: on A10 it was unencrypted, flashing A11 encrypted it again?
viktor92 said:
I'm running stock Android 11 and I've tried to make a backup with TWRP but failed with this message:
Can create '/data/media/o/TWRP/ folder (required key not available).
Failed to make backup folder.
It means that I'm encrypted, right ??. If I'm correct, should I format data and flash the new multidisabler ?
EDIT: on A10 it was unencrypted, flashing A11 encrypted it again?
Click to expand...
Click to collapse
Yes, you must format and flash multidisabler.
Question, i went though the bootloader unlock but the option don't appear grey out on the dev menu, what should i do to really unlock it?
Edit:
Ok i manage to do it but idk how to reboot in to TWRP, is it vol+ and power? it isn't working
Pupet_Master said:
Question, i went though the bootloader unlock but the option don't appear grey out on the dev menu, what should i do to really unlock it?
Edit:
Ok i manage to do it but idk how to reboot in to TWRP, is it vol+ and power? it isn't working
Click to expand...
Click to collapse
Android 11 changes the way it works
Now, it is necessary to be connected to a PC to boot to recovery with that combination of keys.
ShaDisNX255 said:
Android 11 changes the way it works
Now, it is necessary to be connected to a PC to boot to recovery with that combination of keys.
Click to expand...
Click to collapse
Thanks Friend
I have a Samsung A71 Anroid 11 and I'm also trying to root it. Everything you have written I understand, up to this point:
"- After formatting data, flash the Multidisabler zip with TWRP. This is done to avoid future bootloops."
I answer "Yes" and than at the next screen I only can choose between Back or Reboot. How must I flash at this stage the Multidisabler?
Must I go back to the TWRP main menue to the Point "install"?
Greetings from Cologne
Germany
Norbert
Nobby52 said:
I have a Samsung A71 Anroid 11 and I'm also trying to root it. Everything you have written I understand, up to this point:
"- After formatting data, flash the Multidisabler zip with TWRP. This is done to avoid future bootloops."
I answer "Yes" and than at the next screen I only can choose between Back or Reboot. How must I flash at this stage the Multidisabler?
Must I go back to the TWRP main menue to the Point "install"?
Greetings from Cologne
Germany
Norbert
Click to expand...
Click to collapse
Yes, you have to go back to the main menu
Thank you, I'll try it again.
Norbert
Unfortunately, this method doesn't work for me. I've tried rooting three times. It went through every time without any errors. The device was not rooted afterwards. The smartphone then triggered a reset every few minutes when it was operated. What can I do?
Greetings from Cologne
Norbert
Nobby52 said:
Unfortunately, this method doesn't work for me. I've tried rooting three times. It went through every time without any errors. The device was not rooted afterwards. The smartphone then triggered a reset every few minutes when it was operated. What can I do?
Greetings from Cologne
Norbert
Click to expand...
Click to collapse
What ROM are you trying to root?
Are you Rooting with Magisk or Super SU? Do you install SUper SU App or Magisk Manager after?
About the reset, did you flash the multiboot disabler after flash the root zip file?
I root the original Samsung Stock Rom. "A715FXXU3BUB5_A715FOXM3BUB6_DBT". I followed the instructions here exactly.
First unroot and debug mode
1.) download mode
2.) with Odin TWRP + VBMeta-Disabler
3.) TWRP started, wipe, then yes, then back to install, Multidisabler.zip flashed.
4.) restarted
That was it
I don't have a Super_SU or Magisk installed
greeting
Norbert