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???
Related
Attached in this thread is TWRP repackaged for the SM-T285 built by @ashyx with the UI lag fixed and a new custom kernel that I built.
TWRP-3.1.1-0 for the SM-T285 is now available, you should hop on to this thread for more information.
Update 01/17/2017
==============
TWRP with F2FS support here. Use only if you plan to use the F2FS enabled CM13 builds for the SM-T285.
Update 11/24/2016
==============
* MTP should now be fixed
Installation Instructions
This installation instruction is only for the LTE enabled version of the Samsug galaxy tab A 7" 2016 (SM-T285). If you have a wifi-only version (SM-T280) go to this thread instead.
Disclaimer: I am not responsible for bricked devices and provide no warranty, make sure you made the proper backups and contingencies before you do this procedure. Make sure you have a stock firmware available as a contingency plan
Before going through this make sure your tablet is OEM Unlocked. Make sure you have developer settings enable and there should be a setting there that says OEM unlock. That should be enabled, otherwise your SM-T285 will not accept firmware changes. Also make sure your tablet has sufficient charge and is not about to die.
1. Put your tablet in download mode (Turn off. holding POWER + HOME + VOL DOWN until download mode appears. There will be a warning that about custom firmware blah- blah-blah just hit volume up to proceed). Connect your tablet to your computer using the provided micro usb cable.
2. Flash with ODIN 3.10.7 in the AP slot. Uncheck Auto reboot. (If you are on Linux you can use Heimdall
3. Load the respective attached file (TWRP_3.0.2-1_SM-T285_20161124.zip) in this thread below into the AP slot and hit start.
4. After flashing when ODIN says PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding the other buttons.
You should now see TWRP recovery.
Root and SuperSU
==============
1. Download the latest available SuperSu Zip from chainfire. Install Zip using TWRP. Reboot phone.
2.Your phone might reboot a couple of times, however at the end of the process you should be rooted.
enjoy!
jedld said:
Attached in this thread is TWRP repackaged for the SM-T285 built by @ashyx with the UI lag fixed and a new custom kernel that I built.
For the installation instructions, should be the same with the SM-T280 in this thread http://forum.xda-developers.com/galaxy-tab-a/development/recovery-samsung-galaxy-tab-a6-sm-t280-t3475381
enjoy!
Click to expand...
Click to collapse
Thanks! The lag is completely gone, making the recovery a joy to use. However, MTP is still not working.
Thanks
I rooted my device (Glaxy Tab a 7" T285)by your method and files.
Next day i saw my device was off ,i pressed power but it could not boot and show this:
Code:
custom binary blocked by frp lock
Afterward i tried to go recovery by pressing Home+Power+volum up but it could not go recovery and show me:
Code:
custom binary blocked by frp lock
Recovery is not Seandroid Enforcing
Therefor my device had been useless.
so I go to download by odin and install a stock ROM.
I search and saw 2 advises:
1)this problem occur if androd version is 5.1.1
2) this problem occur if in developer menu OEM Unlock Option is disabled.
IS THIS ADVISES TRUE? OR THAT PROBLEM HAS OTHER REASON?
I went dev menu and enabled OEM and afterward i did ROOT again.
I have some questions:
1) Is it important Factory reset after install new ROM ? Also after ROOT? Also after unroot?
2) How do i unroot my device?
I have some questions:
1) Is it important Factory reset after install new ROM ? Also after ROOT? Also after unroot?
Click to expand...
Click to collapse
If you install a new rom, then yes you have to factory reset. If it is just to install TWRP I don't think you need to do that.
2) How do i unroot my device?
Click to expand...
Click to collapse
Easiest way is to just flash stock again
Many thanks @jedld, root works perfectly in Galaxy Tab A6 (2016) SM-T285.
Flash twrp.tar by odin, then flash @Chainfire SuperSU SR 2.78 and get rooted !
acornkenya said:
Thanks! The lag is completely gone, making the recovery a joy to use. However, MTP is still not working.
Click to expand...
Click to collapse
MTP should now be fixed with the latest release.
jedld said:
MTP should now be fixed with the latest release.
Click to expand...
Click to collapse
MTP is now working like a charm; thank you
Adam Hui said:
Many thanks @jedld, root works perfectly in Galaxy Tab A6 (2016) SM-T285.
Flash twrp.tar by odin, then flash @Chainfire SuperSU SR 2.78 and get rooted !
Click to expand...
Click to collapse
Pls help subinary files not installed superSU v2.78.SR1
siukbah112 said:
Pls help subinary files not installed superSU v2.78.SR1
Click to expand...
Click to collapse
Just download & flash latest SR5 superSU.zip
@jedld
So just flash the TWRP file with Odin or follow the long steps provided in that thread about the T280?
The links seem to get outdated very quickly so a step by step guide would be really appreciated to avoid mistakes :good:
From beginning to end until I have SuperU :good:
Thanks in advance if I don't reply m8
Shook1 said:
@jedld
So just flash the TWRP file with Odin or follow the long steps provided in that thread about the T280?
The links seem to get outdated very quickly so a step by step guide would be really appreciated to avoid mistakes :good:
From beginning to end until I have SuperU :good:
Thanks in advance if I don't reply m8
Click to expand...
Click to collapse
ok, I've updated the instructions.
finally, I've managed to flash the recovery img to my Stock 285. I have compiled the heimdall from source (github), using Debian 8 Jessie. I also managed to download the stock firmware from sammobile using wget + cookies trick so it can be resumed without requiring a premium account. Thanks for the TWRP
BTW, after installing the SuperSU the SELinux is gone? do I need to flash your custom kernel too?
What do you mean? Was SELinux set to permissive? From what I know the stock kernel has SELinux configured to always enforce and can't be disabled that easily.
SCREENSHOT SELF DESTRUCT AFTER 24 HRS
{
"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"
}
Before I flashed TWRP nad ROOT (SR5-SuperSU-Chainfire) the SELinux can be seen Set to 'Enforcing' then it is now gone? THe SUperSU asked that 'Samsung KNOX has been detected, try to disable KNox?' I clicked 'Yes'. I have not used yet your kernel img, i am still using the 'stock' kernel, i've only flashed recovery img using heimdall 1.4.1
$ sudo heimdall flash --RECOVERY recovery.img
----
This may not be related but. The screen lock password prompt does not popup the keyboard (samsung or any other). I've also tried 'Pi Locker' the PIN code option and the keyboard still won't appear so there s no way to type the code/pin/password. I am trying to set the screen lock to pattern lock but it is greyed out it security settings because I used device encryption. Is there a adb/shell command to enable Pattern Lock method? Thanks
screen shots:
#1 Stock android lock screen
#2 Pi Locker (F-Droid)
gian20 said:
SCREENSHOT SELF DESTRUCT AFTER 24 HRS
Before I flashed TWRP nad ROOT (SR5-SuperSU-Chainfire) the SELinux can be seen Set to 'Enforcing' then it is now gone? THe SUperSU asked that 'Samsung KNOX has been detected, try to disable KNox?' I clicked 'Yes'. I have not used yet your kernel img, i am still using the 'stock' kernel, i've only flashed recovery img using heimdall 1.4.1
$ sudo heimdall flash --RECOVERY recovery.img
----
This may not be related but. The screen lock password prompt does not popup the keyboard (samsung or any other). I've also tried 'Pi Locker' the PIN code option and the keyboard still won't appear so there s no way to type the code/pin/password. I am trying to set the screen lock to pattern lock but it is greyed out it security settings because I used device encryption. Is there a adb/shell command to enable Pattern Lock method? Thanks
screen shots:
#1 Stock android lock screen
#2 Pi Locker (F-Droid)
Click to expand...
Click to collapse
Interesting, I haven't encountered that on my device, then again I'm not using encryption. In that case it could be related to something SuperSU is doing. Unfortunately I have no clue as to what that is, it does touch the sepolicy files in order to allow for root as far as I know.
jedld said:
Interesting, I haven't encountered that on my device, then again I'm not using encryption. In that case it could be related to something SuperSU is doing. Unfortunately I have no clue as to what that is, it does touch the sepolicy files in order to allow for root as far as I know.
Click to expand...
Click to collapse
I don't know if that issue (missing keyboard) was patched with the new stock firmware update on Dec 13, 2016 or if it may block installation of custom firmwares... I ended up not using a password on the lock screen, I deleted the passowrd.key and modified the android settings database to disable password lock, but seperating the necrpytion password using an app.
Unroot without rebloating?
I've rooted using this method (smooth as anything, by the way) in order to remove the various bits of bloatware. What I'm wondering is, is it possible to unroot, take the recovery back to stock and not end up with the bloatware back on?
Reason I'm asking is, my 6 year old loves playing Pokemon Go (honest!), but any of the custom ROMs I've tried meant I couldn't play the game anymore.
Failing that, is there a workaround?
DJThunderGod said:
I've rooted using this method (smooth as anything, by the way) in order to remove the various bits of bloatware. What I'm wondering is, is it possible to unroot, take the recovery back to stock and not end up with the bloatware back on?
Reason I'm asking is, my 6 year old loves playing Pokemon Go (honest!), but any of the custom ROMs I've tried meant I couldn't play the game anymore.
Failing that, is there a workaround?
Click to expand...
Click to collapse
If you have removed the bloatware it should stay like that unless you reflash the stock rom.
My device software info
Baseband version: T285XXU0APH4
Kernel version: 3.10.65-8968674
[email protected] #2
Wed Dec 28 11:00:16 KST 2016
Build Number:
LMY47V.T285XXU0APL7
I had software update few days back so wondering if the TWRP method to root would still work?
I could not select TWRP_3.0.2-1_SM-T285_20161124.zip file in AP slot so I selected TWRP_3.0.2-1_SM-T285_20161124.tar.md5 I hope this correct.
After seeing PASS on odin I could not go into recovery mode directly.
I did press power + vol down and home button but the device rebooted.
And when I did
adb reboot recovery there is not TWRP but stock recovery.
What am I doing wrong? can I still use TWRP method for with latest samsung software?
Is there a easy method to get into recovery mode after running odin?
thank you.
kannaiah said:
My device software info
Baseband version: T285XXU0APH4
Kernel version: 3.10.65-8968674
[email protected] #2
Wed Dec 28 11:00:16 KST 2016
Build Number:
LMY47V.T285XXU0APL7
I had software update few days back so wondering if the TWRP method to root would still work?
I could not select TWRP_3.0.2-1_SM-T285_20161124.zip file in AP slot so I selected TWRP_3.0.2-1_SM-T285_20161124.tar.md5 I hope this correct.
After seeing PASS on odin I could not go into recovery mode directly.
I did press power + vol down and home button but the device rebooted.
And when I did
adb reboot recovery there is not TWRP but stock recovery.
What am I doing wrong? can I still use TWRP method for with latest samsung software?
Is there a easy method to get into recovery mode after running odin?
thank you.
Click to expand...
Click to collapse
It's possible the stock rom overwrites the recovery since you rebooted straight to stock after flashing. Try to flash again but this time when the device reboots, try to press and hold power + home + vol up immediately to attempt to load TWRP recovery.
No More FRP Lock Problem While Installing Xposed.
Note: Before you start reading this thread. I am not responsible for any damage caused to your device do it at your own risk but this method is 100% working so be confident and if u got any errors while doing this process comment on the thread or pm me. This method is only tested with samsung smg531f stock rom (means original rom by samsung). Try this on other custom roms like CM,AOSP,MIUI etc. at your own risk.
Hi XDA today I am here to help people who are unable to install xposed framework in their Grand Prime SM-G531F their are not any threads of installing xposed so I thought of creating one and If you have a problem in installing xposed and getting errors then you are at the right place. If you occured frp lock problem while installing xposed then you are at the right place.
Also try:-
[MASTER THREAD]Samsung Galaxy Grand Prime SM-G531F
S6 S Voice For Grand Prime All Models 5.1.1 Only
Google PIXEL bootanimation For Samsung Galaxy Grand All Models 5.0+
Android Nougat bootanimation for Samsung Galaxy Grand Prime All Models 5.0+
[PORT]S6 Wallpaper Picker for Grand Prime All Models 5.0+
J5 Prime Keyboard + Android N Emojis for Grand Prime All Models 5.0+
Requirements:
1. A Brain.
2. Rooted device.
3. TWRP Recovery.
4. Root Explorer.
5. A Normal PC.
6. Samsung USB Drivers. ( Download them from Samsung official Website ) or If you have Samsung Kies then you have drivers already Installed.
7. Download all files in attachment.
Procedure: No 1.
Steps to Install TWRP and Root SM-G531F:.
1. First You need to install TWRP Recovery. So you can easily be able to root your device downloadtwrp-2.8.7.1-grandprimevelte.img.tar or twrp3latest.tar from attachment.
2. Now You have to go to settings>aboutphone> and then hit build number 7 times now you have developers option. go and check usb debugging and OEM Unlock.
{
"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"
}
3. After that remove your google account by going into settings>accounts.
4. Now shutdown your device and put it in download mode by holding Volume down+Home+Power button together to boot in download mode.
5. Connect your device with PC and open odin (make sure you have installed samsung drivers). after connecting in odin there will be a box that will become yellow. Now click PDA and select TWRP Recovery now hit start after this twrp will be installed.
6. Now put the downloaded BETA-SuperSU-v2.52.zip file in you sdcard and then reboot in recovery mode by pressing Volume UP+Home+Power Key together now you will get boot in TWRP recovery.
7. Now go click install and select the BETA-SuperSU-v2.52.zip file you downloaded and flash it.
8. Now do wipe dalvik cache.
9. Dont add google account because first u need to flash xposed module. I will tell u when to add google account.
OR
You can download the Pre-rooted system so you dont have to do the above steps:
https://www.androidfilehost.com/?fid=24665542585484026
Note:- You need to factory reset your device after you install pre-rooted system. ( I will suggest you to follow the twrp root method instead of prerooted system. )
Procedure: No. 2
Steps to Install Xposed Frimware:.
1. Download the xposed-v87.1-sdk22-arm-custom-build-by-wanam-20161125.zip and Xposed apk from attachment.
2. Now go into recovery mode by pressing Volume UP+Home+Powerkey together.
3. After you get into recovery click install and then select xposed-v87.1-sdk22-arm-custom-build-by-wanam-20161125.zip file flash it and reboot.
4. Now the xposed firmware has installed now install xposed apk file and grant the file root access.
5. Now the final and last step download Stock original recovery and reboot in download mode by pressing Volume down+Home+Power key together.
6. Now open odin and click pda and select stock original recovery file and click start now twrp recovery will be replaced with stock recovery now you will not get frp lock error. Now you can easily add your google account and there will be no frp lock and you can easily use xposed now.
For latest Update of Xposed Framework for grand prime visit:
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
Congrats You have successfully Installed Xposed.
Thanks @waleeds1 for reminding me to add this.
If you got Bootlooped while installing xposed:
Then Simply download xposed uninstaller zip from attachment and put it in your sd card and flash it.
Special Thanks: @wanam
If you like my work hit thanks.
Nice tutorial. What about backup, do I need to back up system when I experimenting with xposed. And are there good modules for G531f?
mita99796 said:
Nice tutorial. What about backup, do I need to back up system when I experimenting with xposed. And are there good modules for G531f?
Click to expand...
Click to collapse
Thanks bro
Yes Its upto u to make a backup of system but I have backup of system everytime. There are so much modules for g531f available. But now I am waiting for the google assistant I hope it will come on lollipop also.
P.s: can u tell me are u able to see the images on the thread?
Owen007 said:
Thanks bro
Yes Its upto u to make a backup of system but I have backup of system everytime. There are so much modules for g531f available. But now I am waiting for the google assistant I hope it will come on lollipop also.
P.s: can u tell me are u able to see the images on the thread?
Click to expand...
Click to collapse
Yes, all images are fine. ☺
mita99796 said:
Yes, all images are fine. ☺
Click to expand...
Click to collapse
Oh ok thanks for the info man
Owen007 said:
No More FRP Lock Problem While Installing Xposed.
Hi XDA today I am here to help people who are unable to install xposed framework in their Grand Prime SM-G531F their are not any threads of installing xposed so I thought of creating one and If you have a problem in installing xposed and getting errors then you are at the right place. If you occured frp lock problem while installing xposed then you are at the right place.
Requirements:
1. Rooted device.
2. TWRP Recovery.
3. Root Explorer.
4. A Normal PC.
4. Download all files in attachment.
Procedure: No 1.
Steps to Install TWRP and Root SM-G531F:.
1. First You need to install TWRP Recovery So you can easily be able to root your device download twrp-2.8.7.1-grandprimevelte.img.tar from attachment.
2. Now You have to go to settings>aboutphone> and then hit build number 7 times now you have developers option. go and check usb debugging and OEM Unlock.
3. After that remove your google account by going into settings>accounts.
4. Now shutdown your device and put it in download mode by holding Volume down+Home+Power button together to boot in download mode.
5. Connect your device with PC and open odin (make sure you have installed samsung drivers). after connecting in odin there will be a box that will become yellow. Now click PDA and select TWRP Recovery now hit start after this twrp will be installed.
6. Now put the downloaded BETA-SuperSU-v2.52.zip file in you sdcard and then reboot in recovery mode by pressing Volume UP+Home+Power Key together now you will get boot in TWRP recovery.
7. Now go click install and select the BETA-SuperSU-v2.52.zip file you downloaded and flash it.
8. Now do wipe dalvik cache.
9. Dont add google account because first u need to flash xposed module. I will tell u when to add google account.
OR
You can download the Pre-rooted system so you dont have to do the above steps:
https://www.androidfilehost.com/?fid=24665542585484026
Procedure: No. 2
Steps to Install Xposed Frimware:.
1. Download the xposed-v86.0-sdk22-arm-custom-build-by-wanam-20160709.zip and Xposed apk from attachment.
2. Now go into recovery mode by pressing Volume UP+Home+Powerkey together.
3. After you get into recovery click install and then select xposed-v86.0-sdk22-arm-custom-build-by-wanam-20160709.zip file flash it and reboot.
4. Now the xposed firmware has installed now install xposed apk file and grant the file root access.
5. Now the final and last step download Stock original recovery and reboot in download mode by pressing Volume down+Home+Power key together.
6. Now open odin and click pda and select stock original recovery file and click start now twrp recovery will be replaced with stock recovery now you will not get frp lock error. Now you can easily add your google account and there will be no frp lock and you can easily use xposed now.
Congrats You have successfully Installed Xposed.
If you like my work hit thanks.
Click to expand...
Click to collapse
How to get this...in setting menu shows information storage, language, android version, clock and charging information
Sahin551 said:
How to get this...in setting menu shows information storage, language, android version, clock and charging information
Click to expand...
Click to collapse
This is a feature of android N you can install it by using android nify module. But for installing this module u need to install xposed framework.
Owen007 said:
This is a feature of android N you can install it by using android nify module. But for installing this module u need to install xposed framework.
Click to expand...
Click to collapse
I already have xposed framework
Owen007 said:
This is a feature of android N you can install it by using android nify module. But for installing this module u need to install xposed framework.
Click to expand...
Click to collapse
Thanks bro))
Your device is looking cool now @Sahin551
Thread Updated with lastest twrp recovery.
Plz make a custom ROM for sm-531f
Sushant515 said:
Plz make a custom ROM for sm-531f
Click to expand...
Click to collapse
I am trying to make one custom rom be patience. I will release it soon.
Owen007 said:
I am trying to make one custom rom be patience. I will release it soon.
Click to expand...
Click to collapse
Thanks a lot
Hey guys. I tried this yesterday, and got to the end but something went wrong, and there was no superSu in my phone. Last night i installed original firmware and did factory reset to phone, and when i tried this today, i kept stuck on part where you install twrp via odin. In odin it says PASS, and looks like everything is cool, but then i pull out USB from phone, go into recovery mode with VOL UP+HOME+POWER and it starts original recovery mod, not twrp recovery mode. But yesterday it started twrp recovery mode instantly. Can anyone help me?
DzonTravolta said:
Hey guys. I tried this yesterday, and got to the end but something went wrong, and there was no superSu in my phone. Last night i installed original firmware and did factory reset to phone, and when i tried this today, i kept stuck on part where you install twrp via odin. In odin it says PASS, and looks like everything is cool, but then i pull out USB from phone, go into recovery mode with VOL UP+HOME+POWER and it starts original recovery mod, not twrp recovery mode. But yesterday it started twrp recovery mode instantly. Can anyone help me?
Click to expand...
Click to collapse
Tell me if u r still getting this error? U flashed twrp3 or twrp2?
Owen007 said:
Tell me if u r still getting this error? U flashed twrp3 or twrp2?
Click to expand...
Click to collapse
I just needed to unchek a. reboot in odin and it worked perfeclty fine! No more error. I used both of them when that happend
DzonTravolta said:
I just needed to unchek a. reboot in odin and it worked perfeclty fine! No more error. I used both of them when that happend
Click to expand...
Click to collapse
Oh ok If u got anymore problem ask me via pm and good luck with your android
Have anyone ever tried Linux deploy if yes please help me I am having great trouble using it
Sent from my SM-G531F using Tapatalk
Hack House said:
Have anyone ever tried Linux deploy if yes please help me I am having great trouble using it
Sent from my SM-G531F using Tapatalk
Click to expand...
Click to collapse
Linux deploy what it does? I want to know
Since i just found some request about rooting and custom recovery of C variante of Archos 50 platinum on xda. I decided to make a thread which works with both variantes 8 or 16GB and all firmware.
I installed TWRP 2.8.7 from Source
to a device with firmware:
Code:
[email protected]
Build fingerprint: archos/SCAC50CPL/ac50cpl:5.1/LMY47D/20151116.140537:user/release-keys
Platform: armeabi-v7a, 32-bit binary
and to a 2. device
[email protected]m
Today i saw, it seems like Archos provide two firmware for the SC7731g Euphoria or
Mesarthim (OTA pac download see below). Run firmware check OTA update 2x befor rooting to get latest - V05.
Firmware checkbox:
{
"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"
}
Mesarthim firmware
Root + TWRP via adb
To flash recovery >
Note: Install custom recovery delete all data on you storage so backup 1st. Maybe remove sd-card.
Enable developer option (tick ~10 times in system setting on build-number)
In developer option allow OEM-unlock and usb-debugging
Connect device to you pc in debugging mode (requires installed driver on pc)
On pc run fastboot (adb) and flash recovery
with following commands:
Code:
adb devices
press enter
now you see device port damones running
Code:
adb reboot bootloader
press enter
archos turns off
Code:
fastboot devices
press enter
archos boot into fastboot mode = black screen
Code:
fastboot flash recovery recovery.img
press enter
wait till all files are transfered
# Now you can reboot into TWRP by press power and volume +
# downloaded recovery has to be in minimal adb fastboot floder
Click to expand...
Click to collapse
If you done setup on your device, save a full backup with twrp
Driver and tools:
Keep in mind you have to install needed debugg usb-driver and fastboot (adb)
or use other tools as SPD upgrader tool + SpreadTrum driver.
Fastboot installer and driver:
https://forum.xda-developers.com/showthread.php?t=2588979
Fastboot as Live boot image
With twrp you can now install latest superuser to manage superuser authorization or xposed.
uninstalled superSU, now i use magisk
Switched back to supersu less bugs with xposed. The patched boot.img can be used to enable root if Archos update firmware
Do not blame me for any damage while installation
If you get into trouble booting your device. You can try
1. a) fully power it off by press Power off 10sec. or b) remove battery.
2. Copy V05 or V08 update.zip depents on your installed firmware to your Archos and reinstall firmware by apply message if usb is unplugged. Any flashable .zip get auto detected and became deleted from internal storage if not orginal.
3. flash update.zip via fastboot mode. (in case bootloop you maybe fastboot via button on boot into bootloader or adb)
4. flash stock rom pac file from update.zip to Spreadtrum Chip device via factory downloder +(driver) Download extract pac from .rar part 1 part 2
5. now you can flash via twrp my aroma rom if any needed stock app is missing. (see 2. post)
6. Flash v05 stock recovery = unroot
7. restore TWRP back ) if you did not do that 1st (o:
Inizialize twrp or superuser first time maybe take up to a minute and a reboot
Alternative way to get root & twrp:
Not test by myself but seems to work:
1.
a) Kingroot (to manage superuser authorization = root)
b) Flashify (to install twrp)
Click to expand...
Click to collapse
2.
a) https://www.supersupro.co then you can flash TWRP by
b) https://twrp.me/app/ or else
Click to expand...
Click to collapse
Extra stuff > # TWRP lock, dial engineer mode, videos
Password protection for TWRP (lock) with https://forum.xda-developers.com/xperia-z2/general/lockable-twrp-recovery-t3151283
To improve media handel (video rec. buffer, i´m not 100% on it) maybe replace codec_pga.xml of attached archiv on root floder \system\etc\codec_pga.xml
As far as i know it´s possible to swap a faster sd as internal memory to improve read and writte speed by tools e.g. Root External 2 Internal SD.
Dial: *#*#83781#*#* Open engineer mode
short video of xposed + manuel boot into recovery
https://youtu.be/83z0Inyx6UM
broken display or camera?
https://youtu.be/40xz3pRUfu8
Display and selfie-cam replacement seems to be not working
Here is a good video:
Camera (13mp) replacement is works (easy)
Just open housing by removing battery and screws, cam-cabel can be unplugged as simple as in b-versions display-cable
How to flash Archos 50c Platinum (Spreadtrum) stock rom
https://youtu.be/geko8jTLWHk
Today i wasted a lot time by try to flash a stock rom to SC7731g device. Now i got it :cyclops:
Chip can be checked under settings / about phone / Baseband version /
or by installed firmware
Download and install driver and SPD Upgrade Tool R2 or up. Then it is important to hold Volume down (-) if you connect usb to flash files, otherwise you get a CANCEL message! If SPD tool start download no need to hold volume down.
factory downloder +(driver) Download update.zip with pac file inside from 4pda.ru forum. If you flashed stock firmware by flashing tool. Install OTA V10 run update check again and install latest update befor flashing TWRP.
Code:
At the moment lastest version BSE70M ARCHOS AC50CPL 20160829 [email protected]
After flashing BSE70I_ARCHOS_AC50CPL_20151021_V08_FS031_CF2_BSE70I_Archos_CTS_L47630M_20151021_DDR3_HD_G4W18_ALS_182138.pac to my
[email protected] ...it´s now
[email protected]n ;) :)
Befor i flashed V08, i also put
BSE70M_ARCHOS_AC50CPL_20160506_V01_FS031_CF2_BSE70M_Archos_L68368_20160506_DDR3_HD_G4W18_ALS_091757_OTA.pac
to it but i was not able to update the older V01 so better not flash the OTG pac if you get it from www
As you can see i add sometimes new stuff to that thread maybe you add a bookmark to check your device thread soon
If you find thread helpful i please to hit thanks button or rate it.
Maybe more information on flashing is needed, feel free to reply. Request are welcome as well as suggestions
More in my following replies ----->>
PW: all-gsm-solutions.tk
Orginal charger is not effictive, so if yo got another replace!! you can save 50% input power even more.
Orginal 110-250V 0,3a my new charger just need 0,15a (6Watt) input!!!
If you are new to customize device and you just finish rooting maybe skip aroma installation
take a breath and backup phone!
Here my TWRP flashable aroma installer for you.
Video https://youtu.be/soFEBiRr8KY
Additional tools can be selected to keep your stock customized Aroma rom works with touch menu (did not as i used ASSAYYED kitchen).
Note: Installing apps via aroma zip to your device take 2-3min. till all installation is done. So wait till you can unlock screen, after reboot. It´s fast as installing all apps via apk and much faster as flashing a orginal firmware!!!
To prevent automatic earse of flashable update.zip from internal storage keep usb connected till you flashed files with TWRP or rename zip - like .zi -can be renamed with TWRP for flashing. Usually no wipe needed.
Most Xposed moduls need framework -->
Installer categories:
Browser (Puffin free, UC_browser)
Launcher / Keyboard (S-launcher, xperiaKeyboard mod)
Media (Root Explorer + root plugin, Es explorer, Media converter, Vlc)
Xposed installer:
(xposed installer -->Can be flashed with supersu & xposed framework / has to be installed to use most of following
Befor install Xposed, flash framework xposed framework sdk zip
Xposed moduls:
appsoppsXposed (manage authorization as on android 6 but better..thinking latest version was not working so i use a mod)
LightningWall, AFwall (firewalls)
Greenify (kind of taskkiller...maybe also work without xposed)
Roaming on national network? It can be fixed with https://forum.xda-developers.com/xposed/modules/app-roaming-control-v1-0-t3267154
Bootanimation can be flashed (install via twrp) a working once https://forum.xda-developers.com/crossdevice-dev/android-one-general/mod-boot-animation-t3062873
S-launcher or else (instead of shipped apo- or google launcher)
tk.wasdennnoch.androidn-ify 795 and up seems to support Lollipop now :good: several Android N features
added stockrom:
apps, priv-app, media all stock sounds + some free ringtones
(supersu from "stock" apps floder only works if it was flashed befor)
Archos+50c+Platinum+Aroma-installer+1.2.zip based on Euphoria V05. Latest stock from Archos ftp server. As long as you do not flash system files you can use all my archos aroma installer
Firmware checkbox (Mesarthin download):
Archos+50c+Platinum+aroma+1.2b.zip based on Mesarthin V05 stock from my OTA dumps
2. Firmware checkbox:
May not working with Mediatek chip use:
Lollipop toBsucht aroma.zip = http://www.mediafire.com/?pe7i7a92wo48mn7/ old aroma without stock rom apps ( Universal installer for ALL Lollipop not only Archos)
Now i got my doubts on a Mediatek chip on AC50CPl as written in 4pda thread, only two V05 firmware^^
After a websearch i saw Archos 50b Platinum use Mediatek MT6582 but not c variante
Other smartphones with SC7731g and same hardware: Archos 55 platinum, Archos 55b Platinum, Gigabyte gsmart classic joy
Mediatek MT6582 = archos 50 b platinum
use unofficial cyanogenmod and CWM PhilZ Touch 6.59.x or else.
You are new to flashing rom? Make full backup with TWRP & Titanium Backup to prevent yourself lossing any data
You like to mod the aroma feel free to share :fingers-crossed:
Opening a AC50CPL battery
Two days ago i "opened" a BSE70I battery as you can see in attached pictures. I like to run my Archos without battery since it seems like i´ve kind of blown usb port. Charge do not work since i used a 2000mAh (+1A) on it. It is showning charge but don´t.
edit:
Today i was thinking about my accu problem. Finally i note my old powerbank simply do not provide enough power. Then i used 3 batteries LR6 (AA) connected in series with success.
Be careful if you handle accu in a non supposed way. Good chance of getting smoke or fire!
Archos 50cpl
Hello pls I was directed to come here to make any complaints to seek help.please am really confused the problem is I installed the twrp file in my phone and rebooted it and my phone won't go back how it was. so it's still going to take me to the twrp custom recovery if I switch on and off so please what is the next thing and what am I to do next please can someone tell me??
Welcome blossomunuagba,
usually you can boot from TWRP into sytem...
If this is not working you can use recover backup in TWRP if dumped befor. If you did no backup you maybe lucky and wipe option works to enable boot system. If you still fail you maybe use the aroma-rom but you have to know what files you have to replace to minimize lost data, etc. maybe you are lucky. In privat you already told me you cann´t make your phone boot the system by flashing aroma.
If you did not wipe everything you still can make a backup to prevent data lose
My sugguest:
1) full flash firmware .pak file with factory download tool. Fix 100% likely !!!
2) Not sure which tools you used to install TWRP. You can replace custom recovery with stock recovery which maybe fix a corrupt recovery. Use same tool as you used to flash twrp or use install image option of twrp
3) ..last but not least maybe flash supersu.zip or xposed sdk since you wrote you tried to install aroma. Both zip files must be installed befor install the full aroma.
Here latest xposed sdk zip:
http://dl-xda.xposed.info/framework/sdk22/arm/xposed-v88.2-sdk22-arm.zip from http://dl-xda.xposed.info/framework/sdk22/arm/
If you use "magisk" you have to use another xposed.zip
In hope way 2 or 3 make your phone load the system.
Attached stock recovery so you can easy go back to stock
Archos 50c platinum
hello thanks for the reply it was helpful my phone is back and running although I have one more issue that's installing the twrp file on my phone the first alternative you gave is abit confusing but the second alternative looks easier that's (kingroot + flashify) I made an error some where and that lead to the issue I had with my phone..pls u said that u have not tested the second alternative I will be more grateful if you do that an explain in details if possible make a video so that others also facing this challenge can benefit from it. thank you:cool
@blossomunuagba
blossomunuagba said:
hello thanks for the reply it was helpful my phone is back and running although I have one more issue that's installing the twrp file on my phone the first alternative you gave is abit confusing but the second alternative looks easier that's (kingroot + flashify) I made an error some where and that lead to the issue I had with my phone..pls u said that u have not tested the second alternative I will be more grateful if you do that an explain in details if possible make a video so that others also facing this challenge can benefit from it. thank you:cool
Click to expand...
Click to collapse
I have to fully unroot my Archos to make such a video. Sorry i do not like to do so. Maybe if you use to go alternative way record and share
For sure you find a lot video showing how to use kingroot or flashify. Afaik if kingroot is used it install an alternativ superuser app which can be replaced with e.g. supersu. but if you have set up fastboot should be better to go on that..my opinion.
Basicly it seems you replaced stock-recovery, so just do it in the way with TWRP- recovery.img. Thinking you it already installed TWRP with success but you messed up aroma installation.
I´m sure about the point you stack at the moment but nice to see your phone is running again proper.
There are two other ways to get root / custom recovery
1. Flash a patched boot.img (magisk patch boot.img which can be used to root if twrp gets incompatible)
2. a) Replace trwp (recovery.img) inside stock-rom and flash recovery by factory downloder.
2. b) patched boot.img can be too
#today i flashed twrp recovery with SPD-tool but you know this factory reset phone (was helpful to fast recover a upper firmware backup)
The attached Magisk boot.img can be used if TWRP need to be updated. So we already got SU-permission on Anroid 6 and up
Debloat and silent systemsounds, camera click sounds - replacement.
example Camera_click.ogg
/system/media/audio/ui/
small download: https://forum.xda-developers.com/attachment.php?attachmentid=4396959
big pack: http://www.mediafire.com/?8pu3qv2ul7opn8z/
Did you know you can remove a lot more files in system? Files in following folders about 100mb extra space:
- system/preloadimage/
- system/preloadmp3/
- system/preloadmp4/
Also possible to remove "all" alarms, notififcation and ringtones. Just set an audio from sdcard befor delete
You can remove (debloat) more from root system folder. Uninstall bloat system apps with titanium backup or es explorer but becareful!
Additional i like to suggest more apps to install yourself to your phones.
######## xposed modul to clean recent app list #######
https://forum.xda-developers.com/xposed/modules/recent-app-cleaner-v2-0-t2734053
install, activate, reboot, start once and give SU permission
1. I use Whatscall, Dington, TalkU to make "free" phone call. You pay by watch ads. Whatscall is good to get fast free credits. TalkU and Dington are pretty similar. Autor is "our" phone manufactur Cheetah.
Benefit you can make real phone-call via wifi, safe expensive calls, etc.
If you have no playstore running you get less ads = less credits!
I use them since one year no problems. Me tested other "free" call/sms apps but did not find better once. Please no referal request!
2. shake2safety
Now i use it to enable emergency call by quickly press 4 times Power button. It can be enabled by shake also. That is a feature of new IOS as well as Samsung Galaxy. The benefit is you can automatic call even is screen is broken, eye or finger issue, else.
You can test your setup by automatic call friends number to prevent by mistake calling emergency
Only sms is working if not installed via playstore :/
** For location please keep your GPS on. When there is no Wi-Fi, GPS or mobile data then no location goes with the message/picture. Also it gives your last location if GPS is off.
Click to expand...
Click to collapse
So go and install that app!!! Alternative maybe SOS Stay Safe
Me also like https://play.google.com/store/apps/details?id=flar2.homebutton to enable flashlight by hardware button
edit: Started use s8+ launcher to unlink media volume via its sidebar
Alternative you can use quick volume contol
or maybe com.bhanu.androidpvolumeslider aka com.bhanu.volumebutton
Sadly not working this xposed modul (v1.6) https://forum.xda-developers.com/xposed/modules/mod-ringer-notification-volume-unlink-t2416768
Today i found BUSH AC50CPL looks 100% same as our archos maybe possible to use parts & TRWP on it or at least easy build a port
Also had to flash pac once again. Always used BSE70I today i failed then used BSE70M pac with success. By the way i seems on SPD-tool v2 you hold volume down button while plug usb to enable downloading, on v19 you have to power up device and hold volume down button.
Hey guys, I thought I'd spread the word on how to root this particular phone in 2018, if you're still stuck with it by any chance. TrapKernel has been breaking Wi-Fi when used on an updated Samsung firmware, and then there's the news of Chainfire quitting development on SuperSU. That being said, here is a fresh new root guide for this phone which would eliminate the need of TrapKernel and SuperSU (or even the development of a new custom kernel for this device altogether), using Magisk, which has become a pretty popular systemless root method.
Magisk comes with a ton of benefits, including a powerful systemless interface, as well as keeping device certification and SafetyNet intact, allowing you to use apps like Snapchat, Pokemon Go, Super Mario Run, and so forth.
Credit to @mcopeland1003` for the heads up on Magisk.
PREREQUISITES
A PC
Odin
Galaxy Core Prime not rooted by any other method, and has the stock kernel intact. (If you want to OTA update your phone be sure to do that before you root your Core Prime with this method!)
Unofficial TWRP SM-G360T1
Installing TWRP Recovery
Enable OEM Unlocking in developer options if you haven't already.
Then, put your device in download mode by pressing Power+Volume Down+Home Key.
Launch Odin on your PC, then connect your device to your PC.
Click on the AP Button and browse for your downloaded TWRP file.
Hit Start.
In my experience, my Core Prime for some reason did not let TWRP install on my phone; when I decided to boot into recovery it booted into Samsung's stock recovery. To get around this: before flashing TWRP, go into the options tab of Odin and uncheck Auto-Restart. Then flash TWRP and then remove the battery of your phone and unplug your device. This will not damage your device.
Now, boot your phone into recovery by pressing Power+Volume Up+Home to make sure TWRP's there. You can now boot back into android.
Installing Magisk
Sideload the Magisk Manager APK from this link onto your device.
Now we need to download the latest Magisk zip file to flash through TWRP. Open up Magisk Manager. Press the giant Install button, then Install, and finally Download Zip Only. The latest Magisk flashable zip will start downloading.
Once the file has finished downloading, boot into TWRP by powering off your phone then pressing the Power+Volume Up+Home keys simultaneously. Head into Install, and browse to /sdcard/MagiskManager. You should find a .zip file with a name like "Magisk-v16.0(1600).zip". Flash that, then reboot into system.
By the way, don't let TWRP install SuperSU. It'll pretty much defeat Magisk.
And there you have it, Magisk giving you root in a systemless fashion, without breaking Wi-Fi, device certification, and SafetyNet. Hope this guide helped you guys out.
Be still my heart
Glad you found it useful. I use it so my 7 year old can play his pokemon games and stuff like that, but use root for the extra storage.
twrp has official release for this phone i seen and used its app to add to recovery once rooted .. wish i didnt use first root method i seen as phone no wifi and cant get reconition from pc
It worked for a while then went belly up !
FazPhantom said:
Hey guys, I thought I'd spread the word on how to root this particular phone in 2018, if you're still stuck with it by any chance. TrapKernel has been breaking Wi-Fi when used on an updated Samsung firmware, and then there's the news of Chainfire quitting development on SuperSU. That being said, here is a fresh new root guide for this phone which would eliminate the need of TrapKernel and SuperSU (or even the development of a new custom kernel for this device altogether), using Magisk, which has become a pretty popular systemless root method.
.
Click to expand...
Click to collapse
Hello,
Using your method which worked for me initially on an SM-G360T1 then on bootup I got the dreaded Wrong Binary FRP enabled message. Since then I have flashed back to the stock ROM but the minute I install TWRP it won't boot past the Metro PCS screen. It just sits there and won't go any further. I have done this multiple times in hopes that it will somehow 'fix' itself...(yeah right) but that never happens.
One of the membes in the Androidcentral group sent me here to ask about the problem. I can't undestand if the frp was tripped by something, why did the phone work OK for 2 weeks and then quit? It would seem to me it would have done it right away but yet it worked fine with TWRP and magisk. I did NOT install any more apps or ROM's to the device that's what puzzles me.
Can you help me with some ideas? You guys are the decided experts and I am a newbie to all this but trying hard to learn as I go.
Many thanks in advance,
W T
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?