Related
Hi all,
So i am no developer and never will be but I do like to understand what i am doing, why i am doing it when I see instructions on the internet. I have just been flashing an unofficial custom LineageOS 15.1 ROM on my Samsung Galaxy A3 2017 and suffice it to say that took hours of working out what i need and I am still not entirely sure I was hoping someone could explain it in simple plain english?
I have seen videos on how to create a custom ROM based on ASOP and read a guide about including hardware drivers before you compile. I guess if the vendor (ex. Samsung) they make their drivers for the hardware open source and you can get them that is a big plus, but i guess those drivers is not everything, i can imagine bootloaders, recovery, root etc etc also plays a role?
So when i wanted to flash my Samsung Galaxy A3 (2017) i go on to XDA and look for my phone and scroll through the forum. Only to find out not that many roms for that model. probaly down to popularity
Anyway i was instantly overwhelmed regarding unlocking the OEM bootloader, installing TWRP recovery and then root the device with SuperSu, installing ODIN etc etc.
So i wonder could anyone explain all this in much simpler steps? I mean the process i read was basically this:
Enable developer options
enable OEM unlock
Install TWRP using ODIN but i also needed something named RMM-State_Bypass.zip ?? not sure what this is this needed to go on SDCARD
reboot phone into download mode and using ODIN to flash TWRP recovery
Boot into TWRP recovery and flash that RMM-State Bypass file
Then i had to root using SuperSU (is Magisk not preferred now?). but for this i was asked to download SuperSU and a "no-verify-opt-encrypt-6.0" file. which I am not sure what is. then put them on SDCARD and boot into TWRP recovery
Then i had to format data reboot into recovery and then flash RMM_State again from above, then flash that "no-verify-opt-encrypt-6.0" file followed by flashing the SuperSU zip file.
Now reboot device and I was root.
Now what the heck did i just do with those files and why is root needed when i shortly after had to copy LineageOS 15.1 to the SD card. boot into recovery and wipe "system, data, dalvik, cache" and then flash custom ROM followed by GAPPS.
When you wipe System, data, cache and dalvik. does that not undo the root we did above? I do not understand
I guess those no-opt-verify file and RMM State bypass probably has something to do with bypassing some Samsung stuff on the device. but really i would love for someone to take the time to write something up in plain simple english, or if this has already been done point to it so that i can read it.
Probably completely crazy but i would love to do a personal CUSTOM ROM for Samgung Galaxy A3 (2017) based on AOSP with GAPPS and thats it. obviously drivers from Samsung so the hardware works. I am fairly certain that following guides on the internet i could create my custom rom, provided that i have the samsung drivers. but i have no idea really what i am doing and why in order to install TWRP and root etc
Feel free to PM me if you feel like that instead
anddd use magisk.
Hello, all. This is my first time posting on XDA, so please bear with me.
I have succeeded in rooting my Samsung Galaxy Tab S6 (running Android 11) with Magisk using the System-As-Root method shown here. My primary reason for rooting my device was to get back the background clipboard access that was nerfed by Google in Android 10. I am utilizing the Magisk module Riru - ClipboardWhitelist as a workaround.
Unfortunately (and obviously), the Module only works when I boot to the Magisk in Recovery partition, through the key combos. Frankly, I have basically no use for the default boot partition since about 1/3 of the apps that I normally use rely on the clipboard access, and the other 2/3 rely on the previous group.
Is there any way to set the device to just automatically boot the the Magisk in Recovery Partition by default, so I don't have to hold down the key combo every time I start up my device? I am open to suggestions, and can follow written guides fairly well...
Otherwise, do I have to look at reflashing the firmware back to the Stock Android 9? If so, how to I get around the restriction in Samsung Download Mode that limits you to flashing the current firmware or newer?
Unless something has changed dramatically since I rooted my t860 (I think you transposed the digits) Magisk is not a recovery. For a recovery you need TWRP. Best help available is here: https://t.me/tabs6twrp
quasiperfect said:
Unless something has changed dramatically since I rooted my t860 (I think you transposed the digits) Magisk is not a recovery. For a recovery you need TWRP. Best help available is here: https://t.me/tabs6twrp
Click to expand...
Click to collapse
I used the method shown here. Magisk in Recovery refers to this.
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's a fully touch driven user interface , no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
Hello, this is TWRP, for Oneplus 7/Pro/5G that supports Android 11
can be flashed to boot with working decryption on android 11 roms
bugs:
backup/restore is unreliable
Installation:
1. fastboot boot twrp.img
2. go to Advanced > Flash Current TWRP
3. after that is done, if you were using a custom kernel, reflash it now
4. if you were using magisk, reflash it now
Updating to a newer build:
1. download new build to internal storage
2. go to Advanced > Install Recovery Ramdisk
4. select the new image
5. after that is done, if you were using a custom kernel, reflash it now
6. if you were using magisk, reflash it now
Send me a beer: Crypto(Preferred) | PayPal
Trees:
https://github.com/TeamWin/android_device_oneplus_guacamole
https://github.com/TeamWin/android_device_oneplus_sm8150-common
Telegram group: https://t.me/NSSFB
Download: https://twrp.me/oneplus/oneplus7pro.html
Unofficial 12 builds: https://www.pling.com/p/1835156/
Will there be an installer zip or just an .img?
bdwilk said:
Will there be an installer zip or just an .img?
Click to expand...
Click to collapse
Read the Installation instructions, there's a new experimental feature replacing the need for zips.
Nice, at least no more torturing my poor 7Pro with test images, haha.
Thanks.
And yes, the new feature is neat and works here pretty well.
Good job, @Nebrassy !
It says a11 ROMs can be decrypted is oos 11 also included in that ?
jaggillararla said:
It says a11 ROMs can be decrypted is oos 11 also included in that ?
Click to expand...
Click to collapse
Why don't you try it and give us feedback
@Nebrassy thank you . I am sure the entire Oneplus guys here appreciate it.
wartomato said:
Nice, at least no more torturing my poor 7Pro with test images, haha.
Thanks.
And yes, the new feature is neat and works here pretty well.
Good job, @Nebrassy !
Click to expand...
Click to collapse
Been using for awhile now it's awesome this will make things easier great job
jaggillararla said:
It says a11 ROMs can be decrypted is oos 11 also included in that ?
Click to expand...
Click to collapse
I'm using HavocOS 4.5 based on OOS 11 and managed to decrypt data partition just fine.
I can confirm it's working on OP7 with OB4 / Android 11.
Many thanks for the great job!
Uploaded new build with f2fs support
Toutatis_ said:
I'm using HavocOS 4.5 based on OOS 11 and managed to decrypt data partition just fine.
Click to expand...
Click to collapse
Did you need to wipe your phone? Recently installed Android 11 and I can't do nandroid backup and don't want to mess it again.
1 said:
Did you need to wipe your phone? Recently installed Android 11 and I can't do nandroid backup and don't want to mess it again.
Click to expand...
Click to collapse
No, I rebooted to bootloader mode, ran sudo fastboot boot filename.img and TWRP splash screen appeared, asking for password. I entered my password and that's it, data partition was decrypted. I finally rebooted to system.
@Nebrassy
Thanks for the great work btw. Appreciated.
This work with stock oos11 encrypted?
Can somebody elaborate this?
1. fastboot boot twrp.img (Which twrp is this? The one shared here?)
2. go to Advanced > Flash Current TWRP (What does current TWRP mean? Official TWRP? and where is that advanced? Advanced in new TWRP?)
1 said:
Can somebody elaborate this?
1. fastboot boot twrp.img (Which twrp is this? The one shared here?)
2. go to Advanced > Flash Current TWRP (What does current TWRP mean? Official TWRP? and where is that advanced? Advanced in new TWRP?)
Click to expand...
Click to collapse
Yes, run fastboot boot TWRP-3.5.1-guacamole-Nebrassy-2.img (this is the filename for the current latest version)
See my screenshot
Toutatis_ said:
Yes, run fastboot boot TWRP-3.5.1-guacamole-Nebrassy-2.img (this is the filename for the current latest version)
See my screenshot
Click to expand...
Click to collapse
Thanks a lot.
Can this be flashed within twrp if we're on the latest version from https://dl.twrp.me/guacamole/ ?
I know there are none to very few tech users who use Galaxy M40, and that is the reason we do not have any custom recovery or ROM. But we can change that, I can see there are some active tech users who are interested in building/porting.
If we all collaborate and discuss our plan, then one day we can have custom TWRP and GSI working on our device.
As an initial step, what I have tried so far:
1. Extracted recovery.img from stock firmware (downloaded firmware, not from the device) with Android 11.
2. Tried to port TWRP using Samsung Auto TWRP recovery porter by Team Hovatek but it does not work and gives error at the end.
If anyone want stock recovery.img or any other file, reply.
What all have you tried so far...? Please share.
Kernel source is available at https://opensource.samsung.com/uploadSearch?searchValue=m40
We got first TWRP recovery, please verify if its working for you [Recovery] TWRP for Samsung M40 (SM-M405F)
rohitrss said:
I know there are none to very few tech users who use Galaxy M40, and that is the reason we do not have any custom recovery or ROM. But we can change that, I can see there are some active tech users who are interested in building/porting.
If we all collaborate and discuss our plan, then one day we can have custom TWRP and GSI working on our device.
As an initial step, what I have tried so far:
1. Extracted recovery.img from stock firmware (downloaded firmware, not from the device) with Android 11.
2. Tried to port TWRP using Samsung Auto TWRP recovery porter by Team Hovatek but it does not work and gives error at the end.
If anyone want stock recovery.img or any other file, reply.
What all have you tried so far...? Please share.
Click to expand...
Click to collapse
i have the same problem with Samsung Galaxy A7 Lite, here is twrp recovery tree:https://github.com/Skorpion96/gta7lite_recovery
So, this is the first time I'm installing a custom rom and I was following along with this guy:
(I found the xda steps to be too confusing to follow) and everything was going just fine until around the 5.20 min mark where after flashing TWERP on the device through Odin I was supposed to press the volume - & the power key to restart the device and as soon as the device went black I was supposed to then press volume + & the power key which I did but then I got this: (attachment)
(btw, even when I don't press the volume + & power key afterwards I get the same result)
Can this still be fixed or have I bricked my device?
Hi @Winter413
I found a wonderful description on the installation of TWRP here .... maybe it's easier to follow though it's for the 8.
Just read the whole story .... your troubles while installing TWRP are not at all new.
It's a kind of trick which you learn as soon as you want to root your phone, or want a good user friendly recovery backup app.
HELP! S8 got bricked, can't access recovery mode and OEM is locked
Can I get some help? I bricked my phone because I was trying to install twrp. It flashed but I got an error where it reset my data, after data reset I was stuck at the boot screen with the logo . I've tried steps like flashing stock rom, odin...
forum.xda-developers.com
Hope it might be of help ....
Nice Sunday for you !
Here on the forum you will be able to meet all the specialists you need.
[RECOVERY] [OFFICIAL] TWRP 3.6.x for Galaxy A10 Exynos series [SM-A105] [4 January 2022]
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
Hi @xabu
First I'd like to greatly apologise you for answering so late. I did not mean to be rude I just didn't want to reply with "ok, I'll be working on it than" & I actually wanted to get something done first. I decided to do things that way becouse I thought that I'll find some time to do this rather soon however unexpected things happened that kept me from doing it but now I have some time & have done something in this regard so enough of my excuses let's get to what I did & what I want to ask you about:
So first I went onto the s8 thread you suggested & I flashed vbmeta_disabled & to my suprise when I restarted again & pressed volume up + power it actually booted into TWRP "and relief washed over me in an awesome wave" but then I went on to get lineage os on it and it doesn't show up in TWRP. I have also gotten some other stuff (magisk & a few files from NanoDroid) & those show up just fine. I got the file from here: https://sourceforge.net/projects/andyyan-gsi/files/lineage-16.x/
& the link I got from this thread: https://forum.xda-developers.com/t/rom-gsi-guide-lineage-os-a10-a105f.4078093/
& as far as I'm concerned that is the only thread about lineage os on this phone on xda so that doesn't work I guess.
I have also tried this: http://www.mediafire.com/file/4w6vaq4lu2tbjfj/lineage-17.0-20200110-UNOFFICIAL.zip/file
& this: https://mega.nz/file/gw4QTYSS#IqqswGusWIW5l10LyvSfmtVUoE4gqn6_g6jywH96Z5Q
& got this:
(I've done these sequentially but I hope that doesn't make any functional difference however one important thing is the first one goes 'till the first "done" and the second one is the rest. You surely could figure that out by yourself but I wrote this just for clarity's sake.)
P.S. I know that both of the error messages I got seem to refer in one way or another to the fact that I'm not using an sd card for this operation, however as far as I'm concerned it should also be possible to install lineage os to the internal storage of the phone & that is what I want to achieve with this.
P.S. 2
I forgot to mention that I obviously wiped everything properly before trying to install lineage os so that's not the problem.
Hi Winter ,
it's important to check if you found the right version of TWRP:
Samsung Galaxy A10
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
every other version might get you in trouble.
And then: there is still no official LineageOS for the A10 (this gives problems too)
[ROM] [GSI] [GUIDE] Lineage os A10 A105F
A guide for how to install Lineage OS [ GSI ] on Samsung A10 A105F Notes / Warning! Use at your own risk, I’m not responsible for bricking your device. Make sure to backup your important data before everything. here is a summary of the steps I...
forum.xda-developers.com
should be the place to be, though there is not too much activity there ...
but look at this thread too:
Samsung Galaxy A10 ROMs, Kernels, Recoveries, & Ot
Improve your Samsung Galaxy A10's battery life, performance, and look by rooting it and installing a custom ROM, kernel, and more.
forum.xda-developers.com
with many good ideas.
Whatever:
I learned that LineageOS should be installed before other additions like Magisk and G-apps. Do this from internal storage and not from an external sd-card.
In TWRP we always make a Zip queue before installing but always starting with the OS or ROM.
You should be successful now you experienced how to install TWRP.
Always check for the right version or ask in the threads.
Thanks for coming back to me though I just wanted to help you
with installing TWRP and I don't have a A10 at my disposal.
Sincerely @xabu
Ps: I saw that you had courage enough to experiment. Be careful but go for it.
Hi @xabu
So as I mention I made it work by flashing this file through odin while in dowload mode & then restarting & pressing the volume up + power buttons which was supposed to take me to twrp & it did & twrp for me seems to be working just fine so I'm a little hesitant to try & install some different version of it but if you think that's the issue than I will try installing those other versions.
As soon as you are in TWRP and it functions fine, then just look to it's version and go to the link which I gave you for the newest version of TWRP for the A10.
"
If you intend to root your (a10) device, be advised that Magisk will be installed to the recovery partition, not the usual boot partition. Both TWRP and Magisk-rooted Android boot using the recovery kernel, with the device's hardware keys used to choose between TWRP and Android at boot time.
You are therefore strongly advised to first root your device with Magisk and then pre-root a TWRP image before flashing it to recovery. The usual path of installing TWRP prior to rooting is problematic on this device, because the Magisk installer does not support installation to recovery from TWRP. Furthermore, prior rooting of the device with Magisk carries the significant advantage of disabling various device protection mechanisms that you will otherwise need to take care of manually."
In this website the instructions about flashing TWRP to your device goes further .... so try to understand it step by step.
If you want to install Magisk, then you should know that from some weeks ago, Magisk started a complete new life with new important instructions: look here:
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
As you can see .... there is a lot to do and to learn.
Hope you'll enjoy it like your
"and relief washed over me in an awesome wave"
no one could have said it better .
PS:
Flashing TWRP without first flashing a vbmeta image with verity disabled will render your device unable to boot.
is especially for your kind of device and certainly not in general.
Alright, so I checked my twrp version with your link & I have the latest one so everything is fine. I also got lineage os 18.1 & it seems to have installed just fine. So now it's time for Magisk. So first I'm also kinda following this guide:
& Wolfgang recommends to not only install the .zip file but also Magisk manager & I couldn't find any link to download it.
"The usual path of installing TWRP prior to rooting is problematic on this device, because the Magisk installer does not support installation to recovery from TWRP" so does that mean that I have to go back to the download mode & from there flash the root file in odin & then install magisk.apk like here?:
2. flash root file:
enter download mode ( see instructions above here )
flash the file in Odin ( choose PDA, select the file and the start )
3. install magisk:
install magisk.apk (download link above here > and then follow the instructions in the app (the app will ask once for reboot).
Also, If you're curious, the "and relief washed over me in an awesome wave" is an almost direct quote (I only changed "washes" to "washed") from my favourite movie - American Psycho.
@xabu
If you liked my previous post, does that mean that I should do the steps I mentioned?
Dearest @Winter413 ....
No, this does not mean that you should do the steps mentioned.
Again read the instructions on the official TWRP where they help you with Magisk. You can always upgrade the moment all works.
I'm not familiar enough with your device. All is working here on the S7.
A complete different device as I noticed while studying your situation.
My like also shows my admiration for your courage to root your phone and try out how to go further and further.
Ps: https://github.com/topjohnwu/Magisk/releases/tag/v24.1
What about Magisk Manager? Do I need that?
And also this :
2. flash root file:
enter download mode ( see instructions above here )
flash the file in Odin ( choose PDA, select the file and the start )
3. install magisk:
install magisk.apk (download link above here > and then follow the instructions in the app (the app will ask once for reboot).
Is from this:
https://forum.xda-developers.com/t/rom-gsi-guide-lineage-os-a10-a105f.4078093/#post-82196787
So that's why I asked where or not I should back off to the download screen and flash the root.
Winter413 said:
And also this :
2. flash root file:
enter download mode ( see instructions above here )
flash the file in Odin ( choose PDA, select the file and the start )
3. install magisk:
install magisk.apk (download link above here > and then follow the instructions in the app (the app will ask once for reboot).
Is from this:
https://forum.xda-developers.com/t/rom-gsi-guide-lineage-os-a10-a105f.4078093/#post-82196787
So that's why I asked where or not I should back off to the download screen and flash the root.
Click to expand...
Click to collapse
Yes you need the new Magisk manager. If you want a rooted phone.
But as I told you....Magisk is changed maybe a month ago .... this means totally new instructions ... so keep this in mind while working with older instructions.
And also regarding the root - If I've gone this far than I might as well go further & attain some more control over my device & also learn a bit about how computers work along the way. This is definitely not the last project of this kind that I'll be doing. I'm already running Pop os on my main computer instead of windows (however I did use windows for this whole process as Odin is unfortunately unavailable for linux). For now I'm also very very slowly learning javascript (I'll try to pick up the pace cuz it's really bad) & once I buy myself a new computer I'll try installing arch on it & using that as my daily driver & yeah, further carrer routes in IT & such are definitely also something that I'll be looking into so while pretty inconmpetent I'm not afraid to play around with computers.
Alright than. If everything is different about Magisk now than I will definitely look into how to properly install both Magisk.zip & Magisk Manager.
So I must admit I haven't looked to much into rooting yet & it seems that It is not required to install a custom rom, however this sounds pretty cool:
Advantages of rooting include the possibility for complete control over the look and feel of the device. As a superuser has access to the device's system files, all aspects of the operating system can be customized with the only real limitation being the level of coding expertise. mmediately expectable advantages of rooted devices include the following:
1. Support for theming, allowing everything to be visually changed from the color of the battery icon to the boot animation that appears while the device is booting, and more.
2. Full control of the kernel, which, for example, allows overclocking and underclocking the CPU and GPU.
3. Full application control, including the ability to fully backup, restore, or batch-edit applications, or to remove bloatware that comes pre-installed on some phones.
4. Custom automated system-level processes through the use of third-party applications.
5. Ability to install software (such as Xposed, Magisk, SuperSU, BusyBox, etc.) that allows additional levels of control on a rooted device or management of root access.
Winter413 said:
Alright than. If everything is different about Magisk now than I will definitely look into how to properly install both Magisk.zip & Magisk Manager.
Click to expand...
Click to collapse
Yes learn about the denylist and Zygisk !
So from my understanding currently the steps left are:
1. installing Magisk.zip & Magisk Manager
2. Installing NanoDroid
3. & perhaps locking my bootloader afterwards to make my device more secure? (I think that's something that should be done but correct me If I'm wrong)
& then I can finally start using my phone on Lineage os, right?