Database Develop

Soft bricked Nexus 6? - "Your device is corrupt. It can't be trusted and may not work

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.

X98 Plus II - TWRP + ROOT v1.2

Hi, with the help of kalijo, I have made an archive to install TWRP and root your X98 Plus II model C2D4.
Reported to also works on C2D6 and C2E3.
Use at your own risk.
You will need an USB mouse to navigate in TWRP.
Instructions are in the archive.
With v1.2, I've added instructions to save the original boot and recovery images, but this will only works with new install, not upgrade.
Download link
MD5: 8634eb14ed5add0c573649aba383daa7.
Version 1.2:
- Added commands to backup boot and recovery images
- Updated SuperSU to v2.79
Version 1.1:
- Updated SuperSU to v2.78
- Added some infos in this file
Version 1.0:
- Initial release

Version 1.1:
Updated SuperSU to v2.78

Thanks! I haven't had a chance to use it yet, but I'm the most recent download.

Here is the new flashable SuperSU:
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
You may have to install SuperSU on GooglePlay after.

Is this for the c2e3?
Sent from my SM-G935F using XDA-Developers mobile app

CountZer0 said:
Is this for the c2e3?
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
It might or might not work.
I have a C2D4, what is the specs of C2E3?

It's android only. 2gb Ram.
Skickat från min SM-G935F via Tapatalk

problem with superSU binaries
I have install this SuperSU following instructions. All was OK severals days and singe few days super SU ask for new binaries and no way to install thèse binaires.
What is the solution please ?
I precise that my C2D4 is rooted with your method.
Thanks a lot
Sée you

Good afternoon .. please can someone help me. today trying to get into the Android tablet hangs on teclast screen, I can not even get into recovery. I state that the tablet is original, someone can help me figure out how to fix it? thank you

miloucrabe said:
I have install this SuperSU following instructions. All was OK severals days and singe few days super SU ask for new binaries and no way to install thèse binaires.
What is the solution please ?
I precise that my C2D4 is rooted with your method.
Thanks a lot
Sée you
Click to expand...
Click to collapse
See post #4
carlo201983 said:
Good afternoon .. please can someone help me. today trying to get into the Android tablet hangs on teclast screen, I can not even get into recovery. I state that the tablet is original, someone can help me figure out how to fix it? thank you
Click to expand...
Click to collapse
What have you done before ? more infos needed.

Version 1.1:
Updated SuperSU to v2.78

Did anyone have any success so for on C2E3 (2GB Android only model)?
Or, maybe to the DEVS - as this is for the dual boot version, is there any reason it would definitely not work on the Android only model? Willing to take some amount of risk, but dont want to brick my device...

It should work. Worst case, you have to reinstall Android, so make sure you have the files before trying.
To obtain the files, type your model number here (you can use Chrome for auto translation):
http://www.teclast.com/tools/pad/pad.php?t=p
That will lead you here:
http://pan.baidu.com/s/1nvpQOGx
(Use Jdownloader to download the file).
The dl speed is rather slow, I'm trying to download right now, will update the post with a mirror soon.
Update: here is a mega mirror:
https://mega.nz/#!sFBCDJiJ!7fLWNkmdg0yUH1IgPlerDo_Og0Vw5Ypgnh4rf0ItnVI
Please report your findings, so I can update the first post.

Well bad news, I tried to flash according to the instructions but the whole thing stopped working/responding during the "fastboot boot loader.efi" stage. I tried restarting the process using dnx mode, however in the end I received "corrupt bzimage kernel" error and device would not boot. I then installed phone flash tool and tried restoring the default images, the process completed OK however when booting teclast logo stays on screen for around 10 minutes, then I get this error: "Bootloader error code 06. Multiple crash events have been reported."
I tried flashing both the "blank" and "recovery" profiles, flash completes OK but tablet is unsable
Any ideas how to solve this, or did I just brick it?
Edit: Screenshot
http://i.imgur.com/OmqhH1E.jpg

In my attempts to install xposed module, I destroyed my both boot and system.
Since you have the problems with bootloader, get android files for your tablet (C2D3) unpack and find the boot.img and system.img
First step flahs origin boot.img
fastboot flash boot boot.img
Then try fastboot boot loader.efi
If your tablet is stuck in a bootloop, then also flash the original system
fastboot flash system system.img
Hope it helps
BTW, did somebody succeeded in installing xposed on our tablet?(C2D4)

I got a working factory image up and running, turns out the issue was some kind of driver/USB problem, I reinstalled everything from scratch on a fresh PC and the recovery flash worked flawlessly the first time I ran it. I will try root procedure again on the other machine later today or tomorrow.

Hooray, I got it working on my c2e3 model using the files and instructions in the original post.
However I have to say this was one of the scarier rooting procedures I went through, even using the cleanly installed PC to flash I had to do it multiple times and kept getting various flashing errors, bootloops, TWRP exiting immediately upon launch etc.. But of course this could just be some kind of HW issue with my tablet, would not suprise me at this price.
Thank you all for your support! Now if we could only get Nougat on this baby...

@maxmax0 thanks for the feedback. @veaceslav No wonder you had issues, Xposed for X86-64 don't exist ! which one have you tried ?

@mooms I tried the normal version, which gave me a bootloop and then I tried the magisk version. Actually the magisk version is flashed, but it doesn't show..

You don't get the point, normal or Magisk version, they are not designed for x86-64, only ARM, ARM64, and X86.

HTC ONE M9 Install SuperSU without an operating system

Hey everyone,
So I am in quite the pickle here and need some help from experts. Seeing as how my google searches were leading more and more to this site, I figured the time had come to create an account and ask my specific issue question:
So here's the situation I'm currently in:
• My phone is bricked. Yes I have no backup (my first shooting of myself in the foot), and a pretty clear SD card (no OS so I cannot boot it. It gets stuck at the startup screen)
• I have the bootloader unlocked
• I have S-ON
• I do not have SU installed
• I have TWRP 3.0.2-0 installed
What I'm looking to do is stock reset my phone so I can just get it back to par. SO like any normal human being I go to google and enter "Stock reset HTC ONE M9" and find all kinds of videos and threads about how to do so. Unfortunately, most thread and videos assume that you have S-OFF and/or SU installed.
So here is my struggle now:
• I want to install SU so I can do things like lock the bootloader and flash a stock ROM to get my phone back to factory stock.
• However, It seems that I cannot install SU because I need an operating system to do so? (Not sure on that part) Reason being, using my current version of TWRP (3.0.2-0) I have tried to install SU versions 1.25, 2.75, 2.76, etc. etc. However, when I install them using TWRP it reboots about 100 times and then gets stuck on the startup screen. Then when I try to use ADB SHELL and enter the "su" command, I find out that SU is not found or in other words not installed.
So I'm not sure if I'm totally screwed and have the chicken and the egg problem where I can't install SU without an OS and I can't install an OS without unlocking the boot loader first which I need SU for)
If there is a way to flash a stock ROM in my current condition that is the answer I'm looking for. I just want to factory reset my phone.
Any thoughts, suggestions, or link are greatly appreciated. At this point I'm desperate to not buy an new phone. Throw your crazy methods of solving this problem my way please!
Also please note that I am still learning the ins and outs of things like the bootloader, RUU, ROM, Recovery so any definitions or helpful comments you provide about what something is and what it is meant to do is greatly appreciated for I am still learning.
Thanks.

hey man supersu only works with a system in place... soff or on doesnt give a crap about a system restore...but since you have twrp recovery , just download a ruu zip or a custom rom for the m9 flash it using twrp and have su installed then

Laddyboy22 said:
hey man supersu only works with a system in place... soff or on doesnt give a crap about a system restore...but since you have twrp recovery , just download a ruu zip or a custom rom for the m9 flash it using twrp and have su installed then
Click to expand...
Click to collapse
Awesome good to know! So I'm downloading a stock RUU zip.
But when I try to flash it though TWRP I get an error saying:
"Failed to mount '/system' (Invalid arguments)"
"Could not find 'META-INF/com/gogle/android/update-binary' in the zip file."
"Error installing zip file '/sdcard/M9_3.38.502.12_FullStock.zip'"
Can you lend me some information on what this means?
EDIT
I also tried to fastboot flash zip ROM.zip and get "RU_SECURITY_FAIL zip from usb command in download mode" which I think I need S-OFF for.

Great Unbrick and SU install guide
Finally fixed it. Found a great guide for both an unbrick and su install all-in-one.
(I'd post a link but I can't post links since I'm too new.)
I found it on teamandroid and the title was "Update HTC One (M9) to Android 6.0.1 Stock Rooted Marshmallow Custom ROM"

[Mate 10 Pro] Stuck in bootloop, need help with stock firmware

After unlocking the bootloader, I installed the latest versions of TWRP and Magisk. It worked after a few reboots, but after installing the Xposed Magisk module the phone got stuck in a boot loop.
I tried to use the Magisk uninstaller, didn't work, tried to use eRecovery and HiSuite recovery, and then I get an error how my phone is unsupported or how there was an issue getting package information for my device.
I tried to flash the SYSTEM.IMG of the same version thinking how it will let me factory reset my phone... and it didn't work. Tried using HWOTA (Which in the end fixed my problems)*, but then I realised it only works for Mate 10 Lite (or maybe I'm just dumb)
I got my phone softbricked and cought in a bootloop, and I don't know how to unbrick it. So I'm asking You guys for help because I really f***ed up, and Your help would be very much appreciated.
Model BLA-L29 (C432) - Europe
*Edit: Fixed by following this guide https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814

Boot to twrp and flash install the same exposed module (you can find it in MagiskManager folder) it should uninstall and get you out of bootloop. Hope it works!

Read You dingus
Nevermind it turns out it was error on My part (which I think You guys all expected), because it looks like I suck at reading REAL easy instructions.
So the problem was I didn't pay attention to one of the prompts of this tool/guide: https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-flash-oreo-update-package-t3716814
After downloading all 3 stock firmware/update files, dropping them, and then renaming them in the HWOTA8_Mate10\repack folder so I could run the repack.bat that would patch them. I did that part just easy, but then I managed to screw up a even easier thing, which was running the ota.bat and following the instructions.
What went wrong was I didn't press ENTER after opening the recovery, so My device never got to do the updating/installing part that all these previous steps were leading up to.
Lesson learned: Read, and follow the steps, it really isn't that hard
SOLVED

Please help -- got same bootloop issue.
I already had Magisc root installed, then decided to try "System-less Xposed Framework":
https://magiskroot.net/install-system-less-xposed-framework-oreo-8/
-- after I flashed (using TWRP) xposed-sdk26-topjohnwu.zip -- phone went into bootloop.

_hunter said:
Please help -- got same bootloop issue.
I already had Magisc root installed, then decided to try "System-less Xposed Framework":
https://magiskroot.net/install-system-less-xposed-framework-oreo-8/
-- after I flashed (using TWRP) xposed-sdk26-topjohnwu.zip -- phone went into bootloop.
Click to expand...
Click to collapse
Xposed oreo beta 4? Or an another version?
Sent from my HUAWEI BKL-L09 using XDA Labs

Need Help with Magisk

Hello Friends!
Straight up: I am somewhat tech-savvy but my skill level is quite low with android stuff -- I have spent a lot of time reading and trying to figure it all out. I realize I just need help to find the best path forward.
Basically, I rooted my Samsung A50 using the Odin with magisk_patched.tar. I did not install TWRP or CWM on the phone.
It worked amazingly!
...at first. Then I deleted some modules that I tried to check out.....
===> then Magisk Manager displayed "Magisk in not installed" and it seemed like root access was no longer available.
===> Clicked install
===> Would you like to Install Magisk 19.3?
===> Clicked Install ===> Given choice to 'Download Zip Only' or 'Select and Patch a File' -- I tried selecting and patching 'magisk_patched.tar' which seemed to work but now I believe the phone is in a bootloop (Samsung logo is displaying without getting anywhere)
I have everything on the phone backed up. I have 'magisk_patched.tar' on my PC.
I wanted to wipe the phone and re-do the whole process.
I then ===> reflashed 'magisk_patched.tar' file using odin in download mode.
It seemed to work at first -- the stock ROM was asking for language, privacy agreements, etc.
But it reboots within 30 seconds of android starting - I can't get past the privacy agreements.
It was stuck in a loop.
Then I tried to ===> flash TWRP using Odin (instructions here: https://www.******.com/root-samsung-galaxy-a50-with-magisk/)
Now I cannot access recovery.
I feel really F-ed.
Any suggestions? Any recommendations for tutorials?
I *really* appreciate any help!
And I apologize for being pretty inept at this stuff

..

doctadocta said:
Hello Friends!
Straight up: I am somewhat tech-savvy but my skill level is quite low with android stuff -- I have spent a lot of time reading and trying to figure it all out. I realize I just need help to find the best path forward.
Basically, I rooted my Samsung A50 using the Odin with magisk_patched.tar. I did not install TWRP or CWM on the phone.
It worked amazingly!
...at first. Then I deleted some modules that I tried to check out.....
===> then Magisk Manager displayed "Magisk in not installed" and it seemed like root access was no longer available.
===> Clicked install
===> Would you like to Install Magisk 19.3?
===> Clicked Install ===> Given choice to 'Download Zip Only' or 'Select and Patch a File' -- I tried selecting and patching 'magisk_patched.tar' which seemed to work but now I believe the phone is in a bootloop (Samsung logo is displaying without getting anywhere)
I have everything on the phone backed up. I have 'magisk_patched.tar' on my PC.
I wanted to wipe the phone and re-do the whole process.
I then ===> reflashed 'magisk_patched.tar' file using odin in download mode.
It seemed to work at first -- the stock ROM was asking for language, privacy agreements, etc.
But it reboots within 30 seconds of android starting - I can't get past the privacy agreements.
It was stuck in a loop.
Then I tried to ===> flash TWRP using Odin (instructions here: https://www.******.com/root-samsung-galaxy-a50-with-magisk/)
Now I cannot access recovery.
I feel really F-ed.
Any suggestions? Any recommendations for tutorials?
I *really* appreciate any help!
And I apologize for being pretty inept at this stuff
Click to expand...
Click to collapse
Try to flash Stock ROM via ODIN (full ROM, not only bootloader!).
Get into the system passing start up wizards etc.
Then you can flash patched bootloader once again.
Note: remember to flash corresponding version of bootloader with ROM. Do not flash elder version of bootloader on newer version of ROM.
It will work for you.
Sent from my SM-N960F via Tapatalk

zencooler said:
Try to flash Stock ROM via ODIN (full ROM, not only bootloader!).
Get into the system passing start up wizards etc.
Then you can flash patched bootloader once again.
Note: remember to flash corresponding version of bootloader with ROM. Do not flash elder version of bootloader on newer version of ROM.
It will work for you.
Sent from my SM-N960F via Tapatalk
Click to expand...
Click to collapse
thank you!
this worked.
Should I install TWRP? I am currently using the Magisk patched rom + Odin method.
Can I use TWRP Manager or something like that now that I have root access to install TWRP on the Samsung A50?
Thank you for your help!!!

doctadocta said:
thank you!
this worked.
Should I install TWRP? I am currently using the Magisk patched rom + Odin method.
Can I use TWRP Manager or something like that now that I have root access to install TWRP on the Samsung A50?
Thank you for your help!!!
Click to expand...
Click to collapse
It depends on why do you need TWRP.
What else except root do you need? Full man droid backup? Or something else...?
Sent from my SM-N960F via Tapatalk