Question Patched Magisk - Odin Root ( Lost Old Files ) - Samsung Galaxy A22 5G

Hello everyone.
I was using this method
Guide to root Galaxy A22 5G, unlock bootloader and flash official firmware (noob friendly)
Your warranty is now void. If you root your device, Your KNOX status will be tripped. You can still pass the safety net after you root if you follow the instructions. I am not responsible for bricked devices, dead SD cards although it is not...
forum.xda-developers.com
While patching with magisk I thought the patched file and flashing it will contain a clone or old files of my system.
After finishing root process and factory reset to unlock bootlocker it appeared there's no trace of anything even after completing root.
Does the patched file has any trace of files of my old system which I can redo it or recover it.

Unfortunately you won't be able to recover anything, as mentioned during OEM unlock the device gets formatted and all you data is gone.

Related

heyy my q.. is abt boot loader and rooting

rooting mobile phone is also unlocks tha boot loader...?? what does exact it means how to unlock boot loader and rooting and unlocking boot loader is same thing...??
Sent from my SM-G7102 using Tapatalk
I searched the forums for you and I found this post:
theq86 said:
Root
Rooting a device is a method to gain full access to the operating system. With root you can do all the administrative stuff, write to locations normally restricted to the system and customize your device deeper.
Root enhances your privileges and you are able to change almost anything inside of your rom.
The rooting, however, affects ONLY your operating system (Android)
Unlocked Bootloader
In most devices, the Bootloader is the instance that calls the operating system (Android) and manages direct access to the device's partitions. Having an unlocked bootloader enables you to flash custom roms, custom kernels, recoveries and so on.
Bootloader and Rooting Teamplay
Often it is the case, and so, too in our devices, that a locked bootloader also locks write access to several partitions like the system partition. This is the reason why rooting is not able without unlocked bootloader. Rooting needs write access to the system partition (for storing the superuser binary and the superuser app)
Without unlocked bootloader, only a temporary half-root can be achieved.
Click to expand...
Click to collapse
I would have linked to the topic but I don't have the 10 post requirement.

Magisk install on 905v no BL unlock or Custom recovery

So I recently found a few articles that say it's possible to install Magisk w/o a root or custom recovery.
Example:
https://forum.xda-developers.com/lg-g6/how-to/guide-insatll-magisk-root-recovery-t3900475?&ampcf=1
I also happen to have a Samsung Note Pro 12.2 (905v) that has a Verizon locked bootloader.
I am trying to use this method of installing Magisk on it, however I can't get the Adb to recognize the tablet. So my questions are,
Does the Verizon lock down the ability to connect via ADB?
Has anyone successfully installed Magisk in the above method on a Samsung Verizon device? and of so how?
Bonus Question(s): is there a way to wipe the entire tablet and bootloader and start from a blank motherboard without killing it?
Or
Can you boot from SD card?[/SIZE]
Sorry, I miss read the guides I was reading. (ADHD excitement/rabbit hole issues). Can't install Magisk w/o unlocked bootloader

Question about low level of android

Hi guys and girls,
I bought a oneplus 7 pro recently and wanted to unlock the bootloader and root it to install the xXx Nolimits mod except I made some errors (I believe I removed too much bloatware with the .profile file, my WIFI and my mobile data were no longer working), so I re-lock the bootloader except that I got this error message: "Your Device is corrupt. It can't be trusted and will not boot", I was scared for a moment but I managed to access the fastboot and re-unlock the bootloader this time to remove everything that was not there in the stock phone and re-lock the bootloader.
I did all the checks after re-locking my bootloader (root check, safety net check, sensor check, Widevine check and stock recovery check) and absolutely no problem, everything is in order.
My question is: is it possible that something has been changed in the low level of android? (I just install TWRP with fastboot, flash Magisk with TWRP and finally flash the xXx nolimits mod).
Thanks for your help !

Genuine Bootloader

Can the oem bootloader be replaced?
If the bootloader is locked, can you be sure the Recovery/System partitions are untouched?
Recovery - where it doesn't matter whether it's Stock or Custom - simply is a menu you can select actions to perform and apply, the lock state of device's bootloader basically isn't of interest.
System partition can get tampered as soon as it gets mounted as RW where it doesn't matter whether device's bootloader is locked or unlocked, but device's Android got rooted or not.
Thank you for replying.
I'm asking about replacing the bootloader system itself and not the recovery.
How can you root without an open bootloader on a modern phone??
The AVB won't let you boot at all(since android 8).
I tried to answer 2nd question in your 1st post here. I can't help it if you didn't realize it.
To answer the question you asked above:
Rooting is the act of unlocking the Android OS to gain complete control over the device through which you can access hidden files or install certain special apps. Rooting Android OS simply means to add Superuser functionality to it.
Again:
Device's bootloader MUST NOT get unlocked in order to root Android. Even device's /system partition must not get touched in order to root Android: hence bootloader's DM-VERITY / AVB must not get disabled.
Last note: I no longer participate this thread ...

How do i recover the imei after unlocking the bootloader?

Hello again! I have a problem, i have the original firmware and the tool to flash it in case anything goes wrong (MTK Client), so i unlocked the bootloader, the problem is that when you unlock the bootloader, the baseband says (020null) and imei is unknown. I tried to restore my own nvcfg, nvram and nvdata to no luck, when I lock the bootloader, they appear again without flashing anything. So there must be something in the system that checks if you have the bootloader locked or not... I want to know how to disable it because I want to have root (I have rooted it with no issues, but i want my imei you know), i thought init.rc may have something to do with it, here is it (https://gist.github.com/ThePinkLyna/a43e65572896a57af2624610f74d00f2).
By the way my phone is an Alcatel 5007G, MTK 6762. Any ideas in where could be the block? The bootloader? An script in the system? There must be a way, right?
Re-lock the bootloader.
Android can get rooted without having the bootloader got unlocked before.
It's the Android kernel that checks if bootloader is locked or not.
xXx yYy said:
Re-lock the bootloader.
Android can get rooted without having the bootloader got unlocked before.
It's the Android kernel that checks if bootloader is locked or not.
Click to expand...
Click to collapse
How to get root without unlocking the bootloader? Because if i patch boot.img to use with magisk, then it goes into red state because secure boot. I know, the last thing you said, but i was talking about the system, there must be something which checks if the bootloader is unlocked or not and if its unlocked then it blocks the imei, i doubt android does that by default.
well, not answer to your original question, however try bootless-root method. but read warnings about limitations on locked bootloader (do not modify boot, system, ...)
TheAndrew579 said:
How to get root without unlocking the bootloader? Because if i patch boot.img to use with magisk, then it goes into red state because secure boot. I know, the last thing you said, but i was talking about the system, there must be something which checks if the bootloader is unlocked or not and if its unlocked then it blocks the imei, i doubt android does that by default.
Click to expand...
Click to collapse
You can doubt all, it's on you. Also take note that
1. every Android device comes shipped with a recovery partition by default,
2. you can't use a Custom Recovery like TWRP to restore lost IMEI.
are you sure it's bootloader lock state and not Magisk? I have same issue with Redmi 6, when booted in Magisk from fastboot baseband is unknown. normal boot baseband reappear (nothing flashed)
my suspect is magisk mount overlay (have to dig more into)
https://github.com/topjohnwu/Magisk/issues/426
What Magisk version you tried?
xXx yYy > /dev/null
aIecxs said:
are you sure it's bootloader lock state and not Magisk? I have same issue with Redmi 6, when booted in Magisk from fastboot baseband is unknown. normal boot baseband reappear (nothing flashed)
my suspect is magisk mount overlay (have to dig more into)
https://github.com/topjohnwu/Magisk/issues/426
What Magisk version you tried?
xXx yYy > /dev/null
Click to expand...
Click to collapse
Its not Magisk, because the problem starts happening when i unlock the bootloader, when i unlock it (Without installing magisk or flashing anything), and androids appears again, i go to info and it says baseband = 020null and imei unknown, if i flash magisk, then i get root but still no imei.
Im talking about the original firmware, unlocked bootloader = no imei, when i lock it again after uninstalling magisk (By flashing the original boot.img) then the imei appears again.
aIecxs said:
well, not answer to your original question, however try bootless-root method. but read warnings about limitations on locked bootloader (do not modify boot, system, ...)
Click to expand...
Click to collapse
And my android security version is newer, so that method wont work, still, i want root so i can uninstall system apps, so an unlocked bootloader is a must, but how exactly if when i unlock it i lose the imei? Thats the problem
you don't need root to get rid of system apps. this will do it. be careful what you're doing, in case of bootloop the only way left is factory reset. do a backup before.
Code:
adb shell cmd package disable --user 0 <pkgname>
How to disable any pre-installed system app bloatware on Android without root
If you hate the bloatware or pre-installed apps on your Android smartphone, here's how to disable them even if Android doesn't normally let you.
www.xda-developers.com

Categories

Resources