Related
There is an easier way to install themes for the Arc than the ADB shell commands.
Simply copy the .zip file to the root folder of your SD card on a rooted stock ROM, with an unlocked bootloader.
Then, using Fastboot and the recoveryArc.img file, use the command:
fastboot boot recoverARC.img
This boots the phone the phone temporarily with the ClockwordMod boot recovery image. You can then just scroll down to the install zip option using the volume rocker and then the power button to select. Choose install zip and there you go. Reboot and them installed.
Sorry of this is a repost, but I was having no joy with the ADB method.
Ax
AscalonX said:
Then, using Fastboot and the recoveryArc.img file, use the command:
Click to expand...
Click to collapse
Which is only good for those that have their bootloaders unlocked, and those that do, will already know.
Yeah well, I was impressed. ;-)
But then again I am, easily, not to mentioned distracted—oh look! A bee!
A
Damn I spoke too soon!
WIth both the Gingerbread theme and the Green X-Themes, the installation appears to go OK, but only the boot animations, unlock screens and the battery icons appear to have actually changed. Little else appears to be implemented.
It seems as if this is not a good installation method.
Sorry!
A
AscalonX said:
Damn I spoke too soon!
WIth both the Gingerbread theme and the Green X-Themes, the installation appears to go OK, but only the boot animations, unlock screens and the battery icons appear to have actually changed. Little else appears to be implemented.
It seems as if this is not a good installation method.
Sorry!
A
Click to expand...
Click to collapse
That will only work if the dev has made the .zip into a flashable CWM .zip, its needs to have the correct edify script and binarys.
Theme installation without unlock bootloaders was little harder maybe some developer can make an application to replace the system files. It would make a great application.
Hello friends,
I have an Asus TF-201(rooted), on which I would like to install Android. I have downloaded the Cyanogenmod ROM/OS from here, which is in a ZIP file(200Mb), contains files like boot.blob, system.new.dat(405.9mb), etc.
I have copied the zip file in a Pen-drive and the pen-drive is plugged in. After that, I tried to boot into recovery mode, but I just saw the android logo lying down with red mark on stomach.
After this, I tried to go Clockwork mod recovery way, unfortunately, I don't have its premium version, so it wont let me boot through images located on disk.
Final step I tried was to install a boot to recovery app, which again did nothing.
So my question is, how can I boot from that zip file and install Lollypop. Can anyone tell me. Thank you.
Please note, I am using Ubuntu Linux and it has adb installed, if that is for some reason required.
DISCLAIMER: So if you're thinking this is the same as [GUIDE] TWRP, ROOT and XPosed - Only J320FN ! you're right, but you're also wrong. The process is somewhat the same of course, but i did not followed that guide nor use any of his files, i'll explain a lot of things, introduce you to magisk.... And here we're talking of the J320F and J320F/DS , which is the variant I have. Yes FN stuff works on F and F/DS most of the time, i'm aware.
With that out of th way let's talk business, I'm running stock 5.1.1 on my Samsung Galaxy J3 2016 J320F. This guide is for Stock ROM, custom roms come pre-rooted or use their own Root addon like Lineage, in the other hand, Samsung's stock roms based on Android L and M are not compatible with the official Xposed Framework from Rovo89, it will bootloop the device, instead we have to use a modified Xposed made by Wanam, more on that later.
I'm going to split this guide in 3 parts, first we're gonna install the custom recovery TWRP via Odin, the recovery will enable us to flash zip files which will allows us to Root the device and finally install Xposed.
How to Install TWRP on the J3 J320FThe tool to flash firmwares files on Samsung phones running Android is called Odin, and in order for Odin to recognize your phone in Download Mode (more on that later) it also needs some drivers. You can download both things from the following links:
Odin 3.10 from MEGA*
<Mod Edit> 4shared link removed
PLEASE READ [*]
1. Both files are in .RAR5, so you need to use WinRAR 5 or above to be able open them.
2. They also are password protected (sorry about that, but i offer them on several sites already). Password is: Tecnoriales
TWRP 3.0.2 for J320F - is a *.tar file, leave it as is, i mean don't extract it.
Before you star please charge your battery to 100%.
1. Install the Samsung Drivers.
2. In your J320F go to Settings>About phone>Software Info and tap 7 times on the Build Number, you'll see a toast message about "Developers Options" being now enabled.
3. Head back to Settings and now youll see Developer Options, enter there turn the toggle for Disable OEM Unlock, you'll face your security challenge, whatever it is you have (pin, password, pattern...).
NOTE: From now on leave Disable OEM Unlock thicked (what i mean is, if you turn the toggle to his original state will enable OEM Unlock). otherwise when you reboot your phone it won't boot again showing you the Custom Binary blocked by FRP Block" error in red letter. This can only be fixed Flashing the stock rom on your J320F, although you might not lose your data you will lose TWRP, root and Xposed. So, BE CAREFUL!
4. Turn off your phone and enter Download Mode pressing Vol+- Home and Power. You'll see a warning in the screen, accept it pressing Vol+.
{
"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"
}
5. Plug your phone to the PC using your usb cable and give it some time for the driver to kick in if it is the very first time.
6. Run Odin as Admin. Check the COM Port is illuminated and you see Added in the log below.
7. Click the AP button and load the *.tar file of the TWRP.
8. Go to Options Tab and disable Auto-Reboot.
9. Press Start and wait Odin to say Pass in green. It's only a couple of seconds.
10. Unplug your phone from the PC and remove the battery and put it back. Now turn in on with the key combo: Vol+, Home and power.
Your J320F will boot straight to TWRP- Change the language from Russian to whatever you want and swipe to the right the slider in the bottom of the screen to enable the TWRP to modify the system. That's it.
How to ROOT the J3 J320F using SuperSu or MagiskGrab your rooting tool:
SuperSu - Good old SuperSu from Chainfire. Might hang from time to time and refuse to grant root access, kinda has bad temper.
or
Magisk + Magisk Manager APK. Newest and systemless root. Works like a charm, I used v16.0.
Before you star please charge your battery to 100%. You might want make a nandroid backup with TWRP before rooting.
1. Copy the *.zip file to the sdcard of your J320F
2. Boot into TWRP.
3. Go to Install and navigate to your sdcard to find and select the zip file.
4. Swipe to the right the slider control on the bottom of the screen to start the flashing process, which you can follow in the log.
5. Once it has finished touch on Reboot System and wait for the phone to boot. It might take a loot of time if you installed SuperSu.
You will have in your launcher the app of your root manager app. Test that root is working with root checker, Link2Sd, or whatever needs root access.
Note: If you rooted with Magisk and don't see Magisk Manager on your launcher, install the apk manually.
How to Install Xposed Framework on the J3 J320FAs I said at the beginning of this post, YOU CAN'T USE OFICIAL XPOSED on Samsungs stock roms (Android 5.x and 6.x) it will make your device loop on the boot process. This is due to the heavy modifications Samsung make to Android to turn it into his TouchWiz UI.
To install Xposed you need:
Xposed Framework by Wanam - The current (and probably final) version is 87.1, download the zip for ARM and SDK22. Optional: Also download Xposed Uninstaller zip in case you get a bootloop.
Xposed Installer App - Is an APK file attached to this thread, which by the way is the official Xposed Framework thread by Rovo89, don't used Xposed zips from there!
Before you star please charge your battery to 100%. You might want make a nandroid backup with TWRP before rooting.
1. Copy files to your sdcard. And install Xposed Installer.
2. Boot into TWRP, go to install and select the xposed-v87.1-sdk22-arm-custom-build-by-wanam-20161125 zip.
3. Swipe to the right the slider control on the bottom of the screen to start the flashing process and wait.
4. When it finishes select Reboot System. This will be a long boot, be patient.
After booting go to the Xposed Installer, or install it if you havent already, and see if Xposed is enabled. You should see the version and the samsung warning like in this pick
NOTE: DO NOT UPDATE XPOSED from the Xposed Installer app, it will flash official Xposed and you will get ****ed, i mean, a bootloop.
Xposed has tons, and tons, and tons of modules, most of them won't work on Samsung roms, again, due to all the changes Samsung made to Android in his stock roms. Always read carefully the info of any module before installing it, believe me they are state it when they wont work on Samsung roms. There's one module you should never even try to install:
It's called Gravity Box... The most powerful and famous module of all, and no, it wont work on your Samsung.
However, theres something called Wanam Xposed, made by the same dev from the modified Xposed we are using, it has some of the features you can find in GB.
All the above information is in this video i made. Video is in Spanish tough.
Sorry for my english, good luck and happy flashing.
can you make an English video please thx!
DeblaGaming said:
can you make an English video please thx!
Click to expand...
Click to collapse
Not happening.
DeblaGaming said:
can you make an English video please thx!
Click to expand...
Click to collapse
Seems pretty straight forward. A word of advice. When doing things like this for first time and if you don't know what to do rather follow text tutorials than videos. Easier to keep up...
Can twrp be updated with latest version or is this some custom twrp only for this model?
I haven't played a lot with flashing on samsungs so I'm doing my reading before. I have FN model. Is there some custom ROM that offers better experience or should I just root stock and get rid of bloatware and tweak it as I like with xposed?
the_bulk said:
Seems pretty straight forward. A word of advice. When doing things like this for first time and if you don't know what to do rather follow text tutorials than videos. Easier to keep up...
Can twrp be updated with latest version or is this some custom twrp only for this model?
I haven't played a lot with flashing on samsungs so I'm doing my reading before. I have FN model. Is there some custom ROM that offers better experience or should I just root stock and get rid of bloatware and tweak it as I like with xposed?
Click to expand...
Click to collapse
Theres no official TWRP for Speadtrum based 2016 J3s. There are newer versions for the J30F/FN i think, but atm i don't care/need it.
Since we don't have an Exynos or Qualcomm SoC, the custom rom scene doesn't look so good. Pretty much you have Lineage (MM & N), RR (N) and more recently DotOS (N), but they all suffer from pretty much the same problems give or take, in top of that most of the other roms are dead since the devs moved on to other phones, the ones I mentioned before don't really receive updates oftem. Right now im using stock with root and Xposed, is working fine, however im thinking about giving a second chance this rom: https://forum.xda-developers.com/galaxy-j3-2016/development/j2-pro-port-markus-rooted-t3657383 is stock MM, a port from the j210F wich i think is newer and somewhat better than this other j2 port: https://forum.xda-developers.com/galaxy-j3-2016/development/marshmallow-rom-j320f-t3623551
Can it flash newest SuperSu v2.82 flashable zip,through TWRP?
Odin Faild
Hi Guys!
I tried to flash the TWRP recovery on my J3 (2016) , but odin saids its faild could you help me with it please?
milewap said:
Can it flash newest SuperSu v2.82 flashable zip,through TWRP?
Click to expand...
Click to collapse
I flashed latest Magisk v18,with TWRP and yes TWRP vorks great tnx dev...for all :good:
Here's another one TWRP custom recovery,this one he has a bekap EFS....downloaded from 4pda ru site.All credits goes to them
SM-J320F-TWRP-F2FS.tar.md5
And here SM-J320FN-TWRP-F2FS.tar.md5 for FN but it does,on J320F i flashed today and works without problems.
Here it is PIT J320F if someone needs it...
Need help
mauriciognr said:
DISCLAIMER: So if you're thinking this is the same as [GUIDE] TWRP, ROOT and XPosed - Only J320FN ! you're right, but you're also wrong. The process is somewhat the same of course, but i did not followed that guide nor use any of his files, i'll explain a lot of things, introduce you to magisk.... And here we're talking of the J320F and J320F/DS , which is the variant I have. Yes FN stuff works on F and F/DS most of the time, i'm aware.
With that out of th way let's talk business, I'm running stock 5.1.1 on my Samsung Galaxy J3 2016 J320F. This guide is for Stock ROM, custom roms come pre-rooted or use their own Root addon like Lineage, in the other hand, Samsung's stock roms based on Android L and M are not compatible with the official Xposed Framework from Rovo89, it will bootloop the device, instead we have to use a modified Xposed made by Wanam, more on that later.
I'm going to split this guide in 3 parts, first we're gonna install the custom recovery TWRP via Odin, the recovery will enable us to flash zip files which will allows us to Root the device and finally install Xposed.
How to Install TWRP on the J3 J320FThe tool to flash firmwares files on Samsung phones running Android is called Odin, and in order for Odin to recognize your phone in Download Mode (more on that later) it also needs some drivers. You can download both things from the following links:
Odin 3.10 from MEGA*
<Mod Edit> 4shared link removed
PLEASE READ [*]
1. Both files are in .RAR5, so you need to use WinRAR 5 or above to be able open them.
2. They also are password protected (sorry about that, but i offer them on several sites already). Password is: Tecnoriales
TWRP 3.0.2 for J320F - is a *.tar file, leave it as is, i mean don't extract it.
Before you star please charge your battery to 100%.
1. Install the Samsung Drivers.
2. In your J320F go to Settings>About phone>Software Info and tap 7 times on the Build Number, you'll see a toast message about "Developers Options" being now enabled.
3. Head back to Settings and now youll see Developer Options, enter there turn the toggle for Disable OEM Unlock, you'll face your security challenge, whatever it is you have (pin, password, pattern...).
NOTE: From now on leave Disable OEM Unlock thicked (what i mean is, if you turn the toggle to his original state will enable OEM Unlock). otherwise when you reboot your phone it won't boot again showing you the Custom Binary blocked by FRP Block" error in red letter. This can only be fixed Flashing the stock rom on your J320F, although you might not lose your data you will lose TWRP, root and Xposed. So, BE CAREFUL!
4. Turn off your phone and enter Download Mode pressing Vol+- Home and Power. You'll see a warning in the screen, accept it pressing Vol+.
5. Plug your phone to the PC using your usb cable and give it some time for the driver to kick in if it is the very first time.
6. Run Odin as Admin. Check the COM Port is illuminated and you see Added in the log below.
7. Click the AP button and load the *.tar file of the TWRP.
8. Go to Options Tab and disable Auto-Reboot.
9. Press Start and wait Odin to say Pass in green. It's only a couple of seconds.
10. Unplug your phone from the PC and remove the battery and put it back. Now turn in on with the key combo: Vol+, Home and power.
Your J320F will boot straight to TWRP- Change the language from Russian to whatever you want and swipe to the right the slider in the bottom of the screen to enable the TWRP to modify the system. That's it.
How to ROOT the J3 J320F using SuperSu or MagiskGrab your rooting tool:
SuperSu - Good old SuperSu from Chainfire. Might hang from time to time and refuse to grant root access, kinda has bad temper.
or
Magisk + Magisk Manager APK. Newest and systemless root. Works like a charm, I used v16.0.
Before you star please charge your battery to 100%. You might want make a nandroid backup with TWRP before rooting.
1. Copy the *.zip file to the sdcard of your J320F
2. Boot into TWRP.
3. Go to Install and navigate to your sdcard to find and select the zip file.
4. Swipe to the right the slider control on the bottom of the screen to start the flashing process, which you can follow in the log.
5. Once it has finished touch on Reboot System and wait for the phone to boot. It might take a loot of time if you installed SuperSu.
You will have in your launcher the app of your root manager app. Test that root is working with root checker, Link2Sd, or whatever needs root access.
Note: If you rooted with Magisk and don't see Magisk Manager on your launcher, install the apk manually.
How to Install Xposed Framework on the J3 J320FAs I said at the beginning of this post, YOU CAN'T USE OFICIAL XPOSED on Samsungs stock roms (Android 5.x and 6.x) it will make your device loop on the boot process. This is due to the heavy modifications Samsung make to Android to turn it into his TouchWiz UI.
To install Xposed you need:
Xposed Framework by Wanam - The current (and probably final) version is 87.1, download the zip for ARM and SDK22. Optional: Also download Xposed Uninstaller zip in case you get a bootloop.
Xposed Installer App - Is an APK file attached to this thread, which by the way is the official Xposed Framework thread by Rovo89, don't used Xposed zips from there!
Before you star please charge your battery to 100%. You might want make a nandroid backup with TWRP before rooting.
1. Copy files to your sdcard. And install Xposed Installer.
2. Boot into TWRP, go to install and select the xposed-v87.1-sdk22-arm-custom-build-by-wanam-20161125 zip.
3. Swipe to the right the slider control on the bottom of the screen to start the flashing process and wait.
4. When it finishes select Reboot System. This will be a long boot, be patient.
After booting go to the Xposed Installer, or install it if you havent already, and see if Xposed is enabled. You should see the version and the samsung warning like in this pick
NOTE: DO NOT UPDATE XPOSED from the Xposed Installer app, it will flash official Xposed and you will get ****ed, i mean, a bootloop.
Xposed has tons, and tons, and tons of modules, most of them won't work on Samsung roms, again, due to all the changes Samsung made to Android in his stock roms. Always read carefully the info of any module before installing it, believe me they are state it when they wont work on Samsung roms. There's one module you should never even try to install:
It's called Gravity Box... The most powerful and famous module of all, and no, it wont work on your Samsung.
However, theres something called Wanam Xposed, made by the same dev from the modified Xposed we are using, it has some of the features you can find in GB.
All the above information is in this video i made. Video is in Spanish tough.
Sorry for my english, good luck and happy flashing.
Click to expand...
Click to collapse
Hey man youre the best guid i found on the internet
I have a j320f, stock rom, 5.1.1.OS and i rooted it twice with superus and magisk. I flashed em with twrp
At first the root checker said root is not installed correctly. Then i rooted it with kingo root and problem solved
I didnt install Xposed
But after some hours my phone restarted and kept bootlooping. I flashed the firmware... my phone worked again. Then again i rooted it but this time i made a backup.
I flashed magisk again (your exact version) and pressed root on kingo root again to make the root checke say the device is rooted
And the bootloop happened again
I wanna know that XposedFramework by wanam does prevent bootloop?
Or is there anything that can be done for preventing bootloop?
AminNadery said:
Hey man youre the best guid i found on the internet
I have a j320f, stock rom, 5.1.1.OS and i rooted it twice with superus and magisk. I flashed em with twrp
At first the root checker said root is not installed correctly. Then i rooted it with kingo root and problem solved
I didnt install Xposed
But after some hours my phone restarted and kept bootlooping. I flashed the firmware... my phone worked again. Then again i rooted it but this time i made a backup.
I flashed magisk again (your exact version) and pressed root on kingo root again to make the root checke say the device is rooted
And the bootloop happened again
I wanna know that XposedFramework by wanam does prevent bootloop?
Or is there anything that can be done for preventing bootloop?
Click to expand...
Click to collapse
You should use latest Magisk. If you install magisk you dont need anything else, if you dont see the magisk app after rebooting just go an download an install latest magisk manager from their thread. Stay away from kingo, use magisk, pay atention to what you are doing, youre using magisk and kingo at the same time, of course youll get a bootloop.
PD: Never quote OP.
Sorry for bothering again.
mauriciognr said:
You should use latest Magisk. If you install magisk you dont need anything else, if you dont see the magisk app after rebooting just go an download an install latest magisk manager from their thread. Stay away from kingo, use magisk, pay atention to what you are doing, youre using magisk and kingo at the same time, of course youll get a bootloop.
PD: Never quote OP.
Click to expand...
Click to collapse
Hey man thanks for the help...i did as you told and i installed magisk v19 using the TWRP.the magisk manager was installed after the reboot BUT the root checker said that the root was not installed properly. In fact the prompt and grant pop up never showed up. I had this problem with superSU too and that was the reason i used the kingo root. And only after that i could see the phone is rooted in root checker...i didnt installed kingo root this time. Thanks for the warning.
But what can i do? My apps does not have root permission.
I tried installing different versions of magisk. The latest v19 and the one u used v16.0. It didnt helped.
The app was not hibernated i checked but it was never in the running apps in application manager
SuperSU had the same problem.
What should i do?
Any solutions?
Youre the best. Thanks
AminNadery said:
Hey man thanks for the help...i did as you told and i installed magisk v19 using the TWRP.the magisk manager was installed after the reboot BUT the root checker said that the root was not installed properly. In fact the prompt and grant pop up never showed up. I had this problem with superSU too and that was the reason i used the kingo root. And only after that i could see the phone is rooted in root checker...i didnt installed kingo root this time. Thanks for the warning.
But what can i do? My apps does not have root permission.
I tried installing different versions of magisk. The latest v19 and the one u used v16.0. It didnt helped.
The app was not hibernated i checked but it was never in the running apps in application manager
SuperSU had the same problem.
What should i do?
Any solutions?
Youre the best. Thanks
Click to expand...
Click to collapse
First, perform a factory reset and flash your stock ROM (with odin), afterwards twrp and then magisk. Whatever problem you might have it will go away after a clean install of your rom. Use latest magisk.
Odin
Can I do this without computer???
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.
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?