I have a Samsung Galaxy SII ( GT-I9100 ) which was retrieved from a dumpster. I love the removable battery. I would like to know what custom firmware you recommend for it. I could also use any tutorials you recommend to flash it. I have looked at some but I wonder which is best for my requirements:
* The latest Android release is unimportant (I can live with Android 5.0 to be honest)
* Having Google bundled apps is unimportant (all Google apps will be uninstalled, if present).
* I want the good reliability / stability and no alpha or beta releases.
I am only interested in root access & reliable firmware with which I can install open-source apps from f-droid.org. Thanks for any suggestions.
comfortable said:
I have a Samsung Galaxy SII ( GT-I9100 ) which was retrieved from a dumpster. I love the removable battery. I would like to know what custom firmware you recommend for it. I could also use any tutorials you recommend to flash it. I have looked at some but I wonder which is best for my requirements:
* The latest Android release is unimportant (I can live with Android 5.0 to be honest)
* Having Google bundled apps is unimportant (all Google apps will be uninstalled, if present).
* I want the good reliability / stability and no alpha or beta releases.
I am only interested in root access & reliable firmware with which I can install open-source apps from f-droid.org. Thanks for any suggestions.
Click to expand...
Click to collapse
Lineage OS 17.1 Android 10, that works pretty well.
[ROM][UNOFFICIAL][10.0.0][r41][I9100] LineageOS 17.1
/* ** Your warranty is now void. ** ** We are not responsible for bricked devices, dead SD cards, ** thermonuclear war, or you getting fired because the alarm app failed. Please ** do some research if you have any concerns about features included...
forum.xda-developers.com
Another opportunity for you would be replicant. It is based on LineageOS, but tries to run on free-software only and a mainlined kernel. They don't ship with any google apps and and offer Android 6 (currently upgrading to Android 9 for all of their devices.
You will need modified TWRP to flash this and do not ask me why.
You need odin 3.07 as it is the last version of odin that supports S II.
Odin 3.07 https://odindownloader.com/download/odin3-v3-07
Update offically to 4.1.2, Delete All Samsung and Google accounts, go to settings and phone information, click 7 times build number（Just randomly click All numbers 7x and you will eventually done）, go back to settings, click on developer Options, and toggle BOTH oem unlock and USB debugging.
Then follow below steps
Pit: i9100-LOS-16.0-Emulated-Storage.pit
PDA: i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
1. Boot your phone into Download-mode (Volume down + Power/Standby + Home and hold for 10 seconds).
2. Start ODIN 3.07 on your PC.
3. Connect your phone via USB to your PC.
4. Press volume up on your phone, ODIN should detect your phone.
5. In ODIN Options tab:
Auto Reboot : unchecked
Re-Partition: checked
PIT : i9100-LOS-16.0-Emulated-Storage.pit
PDA : i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
6. Press Start.
7. After succesful flash, reboot phone into Recovery:
- Press Volume up + Power/Standby + Home and hold for 10 seconds.
The phone shuts down.
- Repeat Press Volume up + Power/Standby + Home and hold for 10 seconds
Phone boots in recovery TWRP 3.3.1-1.
8. Swipe to Allow Modifications
9. In TWRP 3.3.1-1 you need to format partions
- Wipe -> Format Data -> Type [yes]
- Wipe -> Advanced Wipe -> Select:
* Davik / ART Cache
* Cache
* System
* Non-emulated Storage
10. Flash the modified TWRP here https://androidfilehost.com/?fid=8889791610682894303 by Transferring TWRP.img to phone via USB cable≧Flash≧select image≧this image
11.Go to home and Reboot≧recovery
12. In new TWRP flash this http://ww.androidfilehost.com/?fid=17248734326145712187 and then stable magisk and reboot.
well gapps also not builded in in lineageos.
Thanks for all the responses. All the choices sound like they will get the job done. I'm currently deciding which one to try first.
jjgvv said:
12. In new TWRP flash this http://ww.androidfilehost.com/?fid=17248734326145712187 and then stable magisk and reboot.
Click to expand...
Click to collapse
Much appreciated. I was preparing all the files you mentioned but got a broken link on this one. Could you re-check please?
comfortable said:
Thanks for all the responses. All the choices sound like they will get the job done. I'm currently deciding which one to try first.
Much appreciated. I was preparing all the files you mentioned but got a broken link on this one. Could you re-check please?
Click to expand...
Click to collapse
lineage-17.1-20210107-UNOFFICIAL-i9100.zip | by rINanDO for Galaxy S2
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
I downloaded both the Replicant files and the Lineage files. I had a look at replicant and the set-up seems to be a lot more invovled, so I have decided to do Lineage first. The firmware download size with Replicant is much less bloated, which appeals to me, especially for older hardware. So I will probably try that eventually.
jjgvv said:
go back to settings, click on developer Options, and toggle BOTH oem unlock and USB debugging.
Then follow below steps
Click to expand...
Click to collapse
I gave it a quick attempt yesterday. In Developer Options I found "USB debugging" but there was no "OEM Unlock" setting anywhere. In any case, I proceeded:
Odin says:
All threads completed. (succeed 0 / failed 0)
I'm led to believe I need to get the Samsung drivers so I will do that later today. I have read that installing Kies installs the drivers so maybe that's the best route.
comfortable said:
I downloaded both the Replicant files and the Lineage files. I had a look at replicant and the set-up seems to be a lot more invovled, so I have decided to do Lineage first. The firmware download size with Replicant is much less bloated, which appeals to me, especially for older hardware. So I will probably try that eventually.
I gave it a quick attempt yesterday. In Developer Options I found "USB debugging" but there was no "OEM Unlock" setting anywhere. In any case, I proceeded:
Odin says:
All threads completed. (succeed 0 / failed 0)
I'm led to believe I need to get the Samsung drivers so I will do that later today. I have read that installing Kies installs the drivers so maybe that's the best route.
Click to expand...
Click to collapse
you are not carrier locked or sth?
comfortable said:
I downloaded both the Replicant files and the Lineage files. I had a look at replicant and the set-up seems to be a lot more invovled, so I have decided to do Lineage first. The firmware download size with Replicant is much less bloated, which appeals to me, especially for older hardware. So I will probably try that eventually.
I gave it a quick attempt yesterday. In Developer Options I found "USB debugging" but there was no "OEM Unlock" setting anywhere. In any case, I proceeded:
Odin says:
All threads completed. (succeed 0 / failed 0)
I'm led to believe I need to get the Samsung drivers so I will do that later today. I have read that installing Kies installs the drivers so maybe that's the best route.
Click to expand...
Click to collapse
I will give you a alternative way. first, update to 4.1.2
then, install rashr https://m.apkpure.com/root-rashr-flash-tool/de.mkrtchyan.recoverytools but do not open it . you need to install it first because Otherwise installation will be blocked by kingroot.
then you guessed that root by kingroot https://kingroot.en.uptodown.com/android
Tutorial https://www.google.com/url?sa=t&sou...BMAF6BAgIEAE&usg=AOvVaw3cA8ZHKR3yqQaY6NvHnO4I
Then you can open rashr. download this TWRP as rashr only flashes.img files. https://www.androidfilehost.com/?fid=8889791610682894303
select RECOVERY FROM STORAGE and select the .img TWRP.
it will ask you to reboot recovery .
in recovery you wipe All in advanced wipe except microsd and USB otg. Then transfer the .zip rom to phone by dumping it into internal storage using a computer. Flash it by flash button and selecting the zip, but do not Install gapps. select Reboot and Pay attention here: Do not install TWRP app! Uncheck All prompt to install TWRP app and reboot system.
jjgvv said:
You will need modified TWRP to flash this and do not ask me why.
You need odin 3.07 as it is the last version of odin that supports S II.
Odin 3.07 https://odindownloader.com/download/odin3-v3-07
Update offically to 4.1.2, Delete All Samsung and Google accounts, go to settings and phone information, click 7 times build number（Just randomly click All numbers 7x and you will eventually done）, go back to settings, click on developer Options, and toggle BOTH oem unlock and USB debugging.
Then follow below steps
Pit: i9100-LOS-16.0-Emulated-Storage.pit
PDA: i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
1. Boot your phone into Download-mode (Volume down + Power/Standby + Home and hold for 10 seconds).
2. Start ODIN 3.07 on your PC.
3. Connect your phone via USB to your PC.
4. Press volume up on your phone, ODIN should detect your phone.
5. In ODIN Options tab:
Auto Reboot : unchecked
Re-Partition: checked
PIT : i9100-LOS-16.0-Emulated-Storage.pit
PDA : i9100-LOS-16.0-Emulated-Storage-TWRP-3.3.1-1.tar.md5
6. Press Start.
7. After succesful flash, reboot phone into Recovery:
- Press Volume up + Power/Standby + Home and hold for 10 seconds.
The phone shuts down.
- Repeat Press Volume up + Power/Standby + Home and hold for 10 seconds
Phone boots in recovery TWRP 3.3.1-1.
8. Swipe to Allow Modifications
9. In TWRP 3.3.1-1 you need to format partions
- Wipe -> Format Data -> Type [yes]
- Wipe -> Advanced Wipe -> Select:
* Davik / ART Cache
* Cache
* System
* Non-emulated Storage
10. Flash the modified TWRP here https://androidfilehost.com/?fid=8889791610682894303 by Transferring TWRP.img to phone via USB cable≧Flash≧select image≧this image
11.Go to home and Reboot≧recovery
12. In new TWRP flash this http://ww.androidfilehost.com/?fid=17248734326145712187 and then stable magisk and reboot.
Click to expand...
Click to collapse
↑quoted from Lineage 17.1 Thread and modified
jjgvv said:
you are not carrier locked or sth?
Click to expand...
Click to collapse
Not sure. I haven't put a SIM card in this thing at all. Does having no OEM Unlock option mean that it's locked to a single carrier? I literally found this phone in the dumpster and I will be using it on wi-fi (occasionally) and offline (mostly).
Re: Kingroot
Not keen on this at all since I have read it is malware.
comfortable said:
Not sure. I haven't put a SIM card in this thing at all. Does having no OEM Unlock option mean that it's locked to a single carrier? I literally found this phone in the dumpster and I will be using it on wi-fi (occasionally) and offline (mostly).
Re: Kingroot
Not keen on this at all since I have read it is malware.
Click to expand...
Click to collapse
try other 1 click root apps then
model number is I9100 or What I mean? or I9100g? it is different
jjgvv said:
model number is I9100 or What I mean? or I9100g? it is different
Click to expand...
Click to collapse
GT-I9100. There is no G
I will try with Samsung drivers later tonight & see if the first method works. I am not keen on many of those 'easy' rooting apps, but I appreciate the help. I have big trust issues with them.
glad to see that, also one click root apps can do whatever they want like installing a malicious app without permission and hack device, though I bite the bullet and tried on my xperia c.
very reasonable doubt
Lineage is installed. However, it is still unrooted. Does anyone have any tips for getting this rooted?
=======
* I have tried the Magisk app and patching "boot.img" several times. That resulted in an error: Unsupported / invalid file, or words to that effect.
* I have tried downloading the Magisk zip file using the Magisk app. I tried flashing that freshly-downloaded Magisk zip file in TWRP. No go. Error: 1
* I have tried downloading various Magisk zip files off Github and flashing in TWRP. No go. Error: 1
* I have tried the official TWRP app that seemed to insist on downloading an official I9100 TWRP file. I flashed this TWRP file using my existing TWRP Recovery. After that, I couldn't get into Recovery at all (using the 3 finger salute). It would always just boot LineageOS instead.
=======
So I decided to start-over. I started up Odin again and started from scratch. I have spent most of the day dicking-around here. Now I am back to having LineageOS installed without root again. I tried Magisk again. No go. Same error 1. Still no root.
I can't recall a time where installing custom firmware and rooting was 100% smooth. Even when flashing in Odin all the checkboxes were greyed-out, so I couldn't even select an option if I tried. I don't know why.
Anyway, any tips to get root are greatly appreciated! SuperSU?:
comfortable said:
Lineage is installed. However, it is still unrooted. Does anyone have any tips for getting this rooted?
=======
* I have tried the Magisk app and patching "boot.img" several times. That resulted in an error: Unsupported / invalid file, or words to that effect.
* I have tried downloading the Magisk zip file using the Magisk app. I tried flashing that freshly-downloaded Magisk zip file in TWRP. No go. Error: 1
* I have tried downloading various Magisk zip files off Github and flashing in TWRP. No go. Error: 1
* I have tried the official TWRP app that seemed to insist on downloading an official I9100 TWRP file. I flashed this TWRP file using my existing TWRP Recovery. After that, I couldn't get into Recovery at all (using the 3 finger salute). It would always just boot LineageOS instead.
=======
So I decided to start-over. I started up Odin again and started from scratch. I have spent most of the day dicking-around here. Now I am back to having LineageOS installed without root again. I tried Magisk again. No go. Same error 1. Still no root.
I can't recall a time where installing custom firmware and rooting was 100% smooth. Even when flashing in Odin all the checkboxes were greyed-out, so I couldn't even select an option if I tried. I don't know why.
Anyway, any tips to get root are greatly appreciated! SuperSU?:
Click to expand...
Click to collapse
You could either try heimdall (alternativ to odin, if odin does not work for you: https://www.glassechidna.com.au/heimdall/
or even try CF-Autoroot: https://desktop.firmware.mobi/
Related
This device is more reasonable to buy as it is small and elegant at a decent price.
It is IP68 water-friendly device and the display is much better - higher FPS than on higher resolution OLEDs - good for action games.
Root using CF-autoroot
Download the file from CF-auto-root repository:
https://download.chainfire.eu/1090/CF-Root/CF-Auto-Root/CF-Auto-Root-a3y17lte-a3y17ltexx-sma320f.zip
WARNING! KNOKX will be: tripped. E-fuse: << BLOWN >> Warranty: VOID!
If you have Nougat or after update to Android 7.0:
https://download.chainfire.eu/1090/CF-Root/CF-Auto-Root/CF-Auto-Root-a3y17lte-a3y17ltexx-sma320f.zip
Wipe data + cache before
Flash CF-autoroot before device initial configuration
WARNING! KNOKX will be: tripped. E-fuse: << BLOWN >> Warranty: VOID!
Click to expand...
Click to collapse
Unzip the file
Run Odin from the unzipped folder
Browse by clicking AP button the *.md5 file from the unzipped folder
Connect the A320F in download mode (start the device by holding Power+Home+Volume DOWN)
After starting the device in download mode, press Volume UP one to allow the download
A new COM port should be recognized by Odin after the device is connected via USB
Press Start button in in Odin
Rooting will take place automatically and the device will restart twice.
After the first restart you can disconnect the cable from the PC.
Second restart might take a few minutes.
After that you will find the SuperSU app installed.
Other, more complicated methods:
Rooting using custom recovery:
You will need:
SM-A320F with Exynos CPU (waiting for updates on other model)
Android Marshmallow 6.0.1 on your device
Odin v3.0.4 (download link below)
Team Win Recovery Project - TWRP (download link here) or ClockWork Mod Custom Recovery - CWM (download link below)
(Recommended custom recovery: Team Win Recovery Project :good: - more features, newer, works better)
SuperSU-v2.79-201612051815 (latest ZIP version available today - download link below)
SM-A320F TWRP & CWM recovery installation procedure:
On your device enable developer options and then disable OEM lock (FRP lock) for the device to allow you to flash custom recovery
(Activate OEM unlock from developer options menu)
Boot your device in Odin downlaod mode (hold VolDOWN + Home + Power)
Flash the *.tar file of TWRP or for the CWM using Odin's PDA option
(Uncheck Auto Reboot and F. Reset Time)
Force reboot your device (hold VolDOWN + Power for 10 seconds)
SM-A320F SuperSU ZIP installation procedure:
Copy SuperSU-v2.79-201612051815.zip on a microSD card (trough USB data cable or any other method)
Unplug the USB data cable from the phone and shut down the device
Start your device in Recovery mode (Hold VolUP + Home + Power)
(RECOVERY IS NOT SEANDROID ENFORCED - this warning is normal when booting into CWM custom recovery but not with TWRP)
The recovery menu will appear
> Using TWRP Recovery:
Swipe to allow modifications
Tap on Install
Tap on Select Storage at the bottom and select MicroSDCard then tap OK
Browse for the SuperSU-v2.79-201612051815.zip and tap on it to install it
Swipe to install SuperSU (confirm Flash)
> Using CWM Recovery:
Select Install zip update package (use VolDOWN/VolUP to navigate and Power to select)
Select Choose zip from sdcard
Select SuperSU-v2.79-201612051815.zip and press Power to install Super SU
The installation will perform automatically and the device will reboot twice.
First reboot will take longer. Please be patient. After the second reboot you will have SuperSU and root.
Downsides/bugs:
Knox will be tripped the second you flash a custom recovery (Warranty void: 1 - non reversibile)
(That means that you will lose the warranty for your device and that can not be changed)
(Perhaps that's why I personally can't invest more than $300 in a Samsung cellphone ever)
You won't be able to use Knox-related functions including Secure Folder ever again
Because of a SuperSU bug you won't be able to use Smart View (Miracast, project the screen to smart TV) unless you make an edit as follows:
Lewdog45 said:
Use a file browser such as Root Browser and go to the root of your device then locate the "System" folder and find build.prop and edit it with any application that can edit it and find the bottom line, right at the edge of the bottom line you need to press enter twice and then paste this:
wlan.wfd.hdcp=disable
And then save it and reboot your device.
Click to expand...
Click to collapse
Special thanks to: ashyx for compiling and updating TWRP recovery for SM-A320F and to XN Logos for providing compatible CWM recovery with SM-A320F.
Please feel free to post your attempts on rooting this device and the results. If other methods will show-up I will include them up here.
jnflos said:
Up to this point there is no success in rooting the Galaxy A3 2017 device.
This device is more reasonable to buy as it is small and elegant at a decent price.
Unfortunately there is no sign of working root method for the device.
Please feel free to update this topic with your attempts on rooting this device, and if success will strike, it will float up here for everyone to see.
Click to expand...
Click to collapse
+1
Thanks to developpers
News good, this one is Working , root cwm for galaxy A3 2017 Sm-A320F,
hit a Thanks if i helped you,
Here
I tried this morning without succes
copernic75 said:
I tried this morning without succes
Click to expand...
Click to collapse
Why didn't it work? Any errors in Odin?
No error in odin.
When i tried To reboot in revovery mode i don't have access to cmw .. just Android error message + Knox error
XN Logos said:
News good, this one is Working , root cwm for galaxy A3 2017 Sm-A320F,
hit a Thanks if i helped you,
Click to expand...
Click to collapse
Thanks! I will test this on my Galaxy SM-A320FL (single sim) to see...
Root was successful! I will update the first post with the mini tutorial and the files needed
REMOVED
I have indeed a a320-FL french model... Exynos inside.
What do you suggest?
jnflos said:
Root was successful! I will update the first post with the mini tutorial and the files needed
Click to expand...
Click to collapse
This cwm worked for Exynos?
tys0n said:
This cwm worked for Exynos?
Click to expand...
Click to collapse
Yes it worked. Please follow the tutorial that I wrote on the first post.
jnflos said:
Yes it worked. Please follow the tutorial that I wrote on the first post.
Click to expand...
Click to collapse
Ok good then I will remove my earlier post. I don't have the device so I can't try it.
I tried again this morning with success!
I can have access to recovery but not to sd card (internal or no)... so I can't root the device.
Any idea?
copernic75 said:
I tried again this morning with success!
I can have access to recovery but not to sd card (internal or no)... so I can't root the device.
Any idea?
Click to expand...
Click to collapse
Format the SD card on your PC using FAT32 option (use an USB adapter).
Copy the zip on the card, Insert it into the phone and reboot into recovery to test.
Yes... that's what I did. I found the solution into Google.
Thanks anyway for your help.
Do you think that it will be possible to install TWRP instead of CWM in recovery?
copernic75 said:
Yes... that's what I did. I found the solution into Google.
Thanks anyway for your help.
Do you think that it will be possible to install TWRP instead of CWM in recovery?
Click to expand...
Click to collapse
Yes. You can flash twrp in cwm and reboot to recovery. Twrp will be there instead.
wich version to choose?
Sorry. There's no twrp for a320 yet, but in general it's working fine to flash new recovery with existing one.
Hey guys, I will receive my a3 2017 soon and I was wondering if it would be preferable to root it now than waiting for the update to Nougat and re-root it then... Any idea when the update will be available for this phone? I was also wondering if I should use a specific brand or type of micro sd card with this phone?
Thanks
I had some trouble to root the Elephone S7 7.1.1 Stock Rom. Therefore here is the short HowTo...
*** Root and TWRP for Elephone S7 4GB 7.1.1 Stock Rom http://bbs.elephone.hk/thread-12886-1-1.html
* SP_Flash_Tool download latest version e.g.: SP_Flash_Tool_v5.1720_Win.zip from http://spflashtools.com/category/windows
* SuperSU download latest version e.g.: SuperSU-v2.82-201705271822.zip from http://www.supersu.com/download
* Stock Rom download latest version e.g.: s7_4g_20170517133805_v2.3.zip from https://mega.nz/#!Z4AmRRTK!XLyd4O8HaS4B_XVNMdSn5OPX76rXDkOYXVekvn-9lMM
* TWRP 3.0.3 by Jemmini download latest version e.g.: recovery.img from https://www.dropbox.com/s/b7u3k1mgpppxlyx/recovery.img?dl=0
* create two folders, one for Stock Rom and one for TWRP
* unpack Stock Rom and copy MT6797_Android_scatter.txt into TWRP directory
optional:
* OpenGAps arm64 / 7.1 / stock download latest version e.g.: open_gapps-arm64-7.1-stock-20170629.zip http://opengapps.org/
* in OpenGAps zip delete from \GApps\ folder whatever you don't want
optional:
* AdAway v2.3 download latest apk from https://labs.xda-developers.com/store/app/org.adaway discussion https://forum.xda-developers.com/showthread.php?t=2190753
* AdAway systemless hosts download latest version e.g.: AdAway_systemless_hosts_v2.zip from https://www.androidfilehost.com/?fid=24438995911977059
optional:
* my_bootanimation.zip
* change your favorite boot animation in my_bootanimation.zip\system\media\
* add your own tweaks in my_bootanimation.zip\system\tweaks.prop
SP_Flash_Tool for Stock Rom:
* select Download-Agent: SP_Flash_Tool_v5.1720_Win\MTK_AllInOne_DA.bin
* select Scatter-Loading-File: Stock Rom\MT6797_Android_scatter.txt
* Firmware Upgrade
* switch phone off
* click Download and press "Power" to connect the phone
* after "Download OK" unplug USB and press "Power" to start phone
SP_Flash_Tool for TWRP:
* select Download-Agent: SP_Flash_Tool_v5.1720_Win\MTK_AllInOne_DA.bin
* select Scatter-Loading-File: TWRP\MT6797_Android_scatter.txt
* Download Only
* switch phone off
* click Download and press "Power" to connect the phone
* !!! after "Download OK" unplug USB and press "Home + Power" (about 10 seconds) until enter recovery !!!
* on phone select "recovery" with "Home" and "Vol -" for OK
* in TWRP select and install
SuperSu
optional Open Gaps
optional AdAway systemless hosts
optional my_bootanimation.zip
* reboot (may loop some times)
tip:
* "adb reboot recovery" doesn't work
* therefore switch phone off and press "Home + Power" (about 10 seconds) until enter recovery
* select "recovery" with "Home" and "Vol -" for OK to enter TWRP
*** restore wrong IMEI's after update to 7.1.1 Stock Rom http://bbs.elephone.hk/thread-13641-1-1.html
* Maui META download latest version e.g.: MauiMETA_exe_v9.1724.0.rar from https://www.needrom.com/download/maui-meta-3g-ver-7-1444-0-0/
* IMEI's from phone box
Maui META:
* switch phone off and unplug USB
* press and hold the "Vol- + Power" Button and connect USB, release the "Vol- + Power" Button and click "Reconnect" (wait until the ball turns yellow)
* !!! retry if it not works !!!
* in the selection box scroll to the IMEI download option and select (it will open a new window)
* copy !!! only the first 14 digits !!! of the 1st IMEI and paste in the IMEI field
* click the "Download To Flash" button and wait until message "Download IMEI to flash successfully"
* repeat this two steps for SIM_2
* close the window, click "Disconnect", unplug USB and restart phone
* check IMEI's in Settings > About Phone > Status
*** restore rotating MAC after update to 7.1.1 Stock Rom https://androidrookies.com/how-to-change-wlan-mac-address-on-mtk/
* in Playstore install "Root Explorer"
* HxD Hex Editor for Windows download latest version https://mh-nexus.de/downloads/HxDSetup.zip
* in Root Explorer copy \nvdata\APCFG\APRDEB\WIFI to \sdcard
* now copy WIFI file to Windows and edit with HxD Hex Editor
* for Your last MAC e.g.: 00:08:22:a8:e3:fb write it in Offset (h) 04 to 09
00 01 02 03 04 05 06 07 08 09
06 01 00 00 00 08 22 A8 E3 FB
* copy WIFI back to \sdcard
* in Root Explorer copy \sdcard\WIFI to \nvdata\APCFG\APRDEB\ and set permission to 660 (rw-rw—)
Have Fun
Thanks
I have problems, this is what I do, for twrp:
- Connect USB to phone
- Start Smart phone flash
- Select scatter file
- Click on download
- Press power in the phone
There, it doesnt download anything. The phone just boots up normally. It could be a driver problem since when it boots it says that the device couldnt not be recognized but where I can find the drivers?
Edit: finally i got it to work but not in a nice way. I tried to turn driver signature off, installing new VCOM drivers for S7 but nothing. So I just went to my other computer with Windows 7 64 bit and it worked all fine the first time. In this computer I have Windows 10 64 bit and always have problems with these things related to phones and flashing.
Thanks for the instructions.
Some comments:
You never mention that you should create a TWRP folder, so that confused me for a while.
You explicitly refer to Windows versions of files in your instructions, even though it's unnecessary. I did the process on Linux and it worked perfectly fine.
The recovery is not fixed for OTA updates. The first OTA update I got bricked my system and I had to reinstall everything. Is there a fixed version of the TWRP available for this phone? I know there's a fixed version for the Elephone P7000 here: bbs.elephone.hk/thread-5332-1-30.html
OpenGApps gave me many issues with crashing services and apps not starting. I decided to leave it out entirely, since the necessary apps are available in the Stock ROM. (I tried all GApps variants from pico to stock)
Even with a rooted system, I could not remove some OEM apps (such as the OTA app that will break the system). Is there a way to remove those anyway?
Hi. TWRP installed on my s7 (X25 - 4/64 G} but can't reboot (hanging logo). Pls. help me to fix it. Thanks
d1237 said:
Hi. TWRP installed on my s7 (X25 - 4/64 G} but can't reboot (hanging logo). Pls. help me to fix it. Thanks
Click to expand...
Click to collapse
Please try to install original Stock Rom with SP_Flash_Tool. And then retry to install TWRP.
Ghostbird said:
Thanks for the instructions.
Some comments:
You never mention that you should create a TWRP folder, so that confused me for a while.
You explicitly refer to Windows versions of files in your instructions, even though it's unnecessary. I did the process on Linux and it worked perfectly fine.
The recovery is not fixed for OTA updates. The first OTA update I got bricked my system and I had to reinstall everything. Is there a fixed version of the TWRP available for this phone? I know there's a fixed version for the Elephone P7000 here: bbs.elephone.hk/thread-5332-1-30.html
OpenGApps gave me many issues with crashing services and apps not starting. I decided to leave it out entirely, since the necessary apps are available in the Stock ROM. (I tried all GApps variants from pico to stock)
Even with a rooted system, I could not remove some OEM apps (such as the OTA app that will break the system). Is there a way to remove those anyway?
Click to expand...
Click to collapse
Hi Ghostbird, thank You for Your support!
* I have added the TWRP folder in the HowTo.
* Do You have tested the HypoTurtle TWRP? Works OTA update now?
* OpenGApps working without any problems, but i never tried to remove OEM apps.
* I have installed Stock Rom, updated OTA and then installed TWRP. No problems since then.
below You find my GApps folder:
batteryusage-all.tar.lz
calculatorgoogle-all.tar.lz
calendargoogle-all.tar.lz
calsync-all.tar.lz
cameragoogle-arm64.tar.lz
cameragoogle-common.tar.lz
cameragooglelegacy-arm.tar.lz
cameragooglelegacy-common.tar.lz
chrome-arm64.tar.lz
clockgoogle-all.tar.lz
contactsgoogle-all.tar.lz
dialerframework-common.tar.lz
dialergoogle-all.tar.lz
exchangegoogle-all.tar.lz
gmail-all.tar.lz
hangouts-arm64.tar.lz
keyboardgoogle-arm64.tar.lz
messenger-arm64.tar.lz
newsstand-all.tar.lz
newswidget-all.tar.lz
pixelicons-all.tar.lz
pixellauncher-all.tar.lz
storagemanagergoogle-all.tar.lz
taggoogle-all.tar.lz
Hi everyone
Link for twrp is down
Someone can post in attachement please ?
Regard
Bradco said:
Hi everyone
Link for twrp is down
Someone can post in attachement please ?
Regard
Click to expand...
Click to collapse
This should work for you. Used on my S7.
bluiis48 said:
This should work for you. Used on my S7.
Click to expand...
Click to collapse
thank you very much for the file, it does not work for me. it starts well on the recovery but can not start the system, still block on the logo.
I'm on s7_4g_20170814163417_v2.4.
Ah, I am still on the July release, have been holding off on the August ROM waiting to see if anything showed up for September but it looks like that might be game over for updates. Thanks for letting me know, saves me some time. I find the July one not too bad. Roll back for root ?
bluiis48 said:
Ah, I am still on the July release, have been holding off on the August ROM waiting to see if anything showed up for September but it looks like that might be game over for updates. Thanks for letting me know, saves me some time. I find the July one not too bad. Roll back for root ?
Click to expand...
Click to collapse
you're welcome , for root it's all good with magisk.
you install the latest version of magisk manager, you get the file boot.img from your rom, you patch this file via magisk manager and you just flash the new boot.img via flashtool. After root is functional.
Y'll try this : https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861
Thanks, I will give that a try when I finally decide to load the 0814 update (or newer if one becomes available). Can I ask why you were needing TWRP ? Also did you notice any improvement with the 0814 update? I have an S8 in transit and will be passing this S7 on to my wife but the S8 could be a while yet when Canada Post gets it. Magisk may work on that also, same X25 and ram.
bluiis48 said:
Thanks, I will give that a try when I finally decide to load the 0814 update (or newer if one becomes available). Can I ask why you were needing TWRP ? Also did you notice any improvement with the 0814 update? I have an S8 in transit and will be passing this S7 on to my wife but the S8 could be a while yet when Canada Post gets it. Magisk may work on that also, same X25 and ram.
Click to expand...
Click to collapse
of course a custom recovery is always useful, nandroid backup and flash some .zip.
for it is the first version of android 7 that I test and I find it very stable without problems.
Ha yes I wonder the purchase of a s8 tell me if it great
Yes I will give you my opinion but it will be a while because our customs and mail is very slow. As I remember I had a hard time with TWRP when I loaded the 20170517 stock rom. I finally did a full format with SPflashtool and when it seemed stuck at the boot animation I left it alone for maybe half an hour and it finally came to life so that version of TWRP does work for 7.1.1 for me.
bluiis48 said:
Yes I will give you my opinion but it will be a while because our customs and mail is very slow. As I remember I had a hard time with TWRP when I loaded the 20170517 stock rom. I finally did a full format with SPflashtool and when it seemed stuck at the boot animation I left it alone for maybe half an hour and it finally came to life so that version of TWRP does work for 7.1.1 for me.
Click to expand...
Click to collapse
ok I understand, little question about SP flash tool to make a full format you used which option DOWNLOAD ONLY / FIRMWARE UPGRADE or the other so I no longer remember the name ?
Bradco said:
ok I understand, little question about SP flash tool to make a full format you used which option DOWNLOAD ONLY / FIRMWARE UPGRADE or the other so I no longer remember the name ?
Click to expand...
Click to collapse
The other is format all + download and that may work for you. It was a while ago, when I went from Android 6 to 7 and I do not want to steer you in the wrong direction. From what I remember I used the format tab on SP Flashtool and pretty much formatted everything. Yesterday I tried for the 0814 OTA by using the clean option in Super SU (which basically uninstalls it ) and flashing the stock recovery for the existing ROM version using SP Flashtool. The OTA would not complete because of a sector mismatch so I flashed TWRP recovery again, which actually rebooted pretty fast then reinstalled the Super SU zip using TWRP. If you want TWRP recovery maybe try it again without formatting anything and give the boot more time. I am not going to bother flashing the complete 0814 ROM until I pass on the phone to my wife because I don't want to go through the app and user credential reloads and fixing the IMEI's and WIFI mac. The Google backup to Drive feature is not available in settings - same for many who are on 7.1.1 even the "name brand" phones.
bluiis48 said:
The other is format all + download and that may work for you. It was a while ago, when I went from Android 6 to 7 and I do not want to steer you in the wrong direction. From what I remember I used the format tab on SP Flashtool and pretty much formatted everything. Yesterday I tried for the 0814 OTA by using the clean option in Super SU (which basically uninstalls it ) and flashing the stock recovery for the existing ROM version using SP Flashtool. The OTA would not complete because of a sector mismatch so I flashed TWRP recovery again, which actually rebooted pretty fast then reinstalled the Super SU zip using TWRP. If you want TWRP recovery maybe try it again without formatting anything and give the boot more time. I am not going to bother flashing the complete 0814 ROM until I pass on the phone to my wife because I don't want to go through the app and user credential reloads and fixing the IMEI's and WIFI mac. The Google backup to Drive feature is not available in settings - same for many who are on 7.1.1 even the "name brand" phones.
Click to expand...
Click to collapse
With each new installation of rom, I start all (long but more stable).
For the problem of wifi and IMEI for having 5 elephone I have never encountered this problem even with version 0814. For the recovery custom it is weird that the start of the phone is long. this afternoon I tried to make a port of TWRP with base on TWRP 3.1 (compatible android 7 for p9000) with stock recovery, but I'm not sure it is functional. i'm not understand everything .
I just saw that the thread be updated, even tuto with the rom s7_4g_20170517133805_v2.3.zip I'm not sure that it works.
I followed the tutorial on first page and it works for me but I am using the 0517 stock rom. I don't think you need to Port TWRP because it does work with the one I posted. If you have time try starting with the 0517 and follow steps on page one. If that works you can try the same with 0814.
IMPORTANT THOUGHT do you have OEM unlocking (allow the bootloader to be unlocked) enabled in developer options ? This is the first phone where I found that to be necessary.
bluiis48 said:
I followed the tutorial on first page and it works for me but I am using the 0517 stock rom. I don't think you need to Port TWRP because it does work with the one I posted. If you have time try starting with the 0517 and follow steps on page one. If that works you can try the same with 0814.
IMPORTANT THOUGHT do you have OEM unlocking (allow the bootloader to be unlocked) enabled in developer options ? This is the first phone where I found that to be necessary.
Click to expand...
Click to collapse
I just look into the options for developers and OEM unlocking is turned off. do you think I'll have to activate it ?
Ps : I never needed it
EDIT 1 :
at this stage :
SP_Flash_Tool for Stock Rom:
* select Download Agent: SP_Flash_Tool_v5.1720_Win \ MTK_AllInOne_DA.bin
* select Scatter-Loading-File: Stock Rom \ MT6797_Android_scatter.txt
* Firmware Upgrade
Before doing firmaware upgrade in what version of rom do I have to?
TWRP for C9LTECHN/SM-C9000 Galaxy C9 Pro
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options).
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status.)
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
PLEASE BEFORE YOU FLASH ROMS MAKE A COMPLETE BACKUP OF YOUR SYSTEM INCLUDING EFS SO YOU DO NOT BRICK YOUR MOBILE
WHAT IS TWRP?
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
How to intall TWRP using ODIN
1) Go to Settings » About phone » and tap “Build number” seven times to enable “Developer options”.
2) Go back to the main Settings page, scroll to bottom and select“Developer options” from there.
3) Under Developer options, look for “Enable OEM unlock”checkbox/toggle and make sure you Check it or turn it ON.
4) Now Boot your Samsung Android device into Download mode.To Do So Follow the steps below
5) Switch off your device.
6) Press and hold “Home + Power + Volume down” buttons for a few seconds until you see a warning screen.
Press Volume Up on the warning screen to accept it and boot into Download mode.
Once your device is in download mode, connect it to the PC with a USB cable. The Odin will automatically detect the device and show an “Added!!” message. If not then your device is not connected properly
7) Now click on the AP tab on Odin window and select the TWRP recovery .tar file that you downloaded for your device.
8) Click the Start button on Odin to start Flashing and wait for it to finish the process.
Once it finished successfully, a pass message on the Odin screen will pop up
Your device will automatically reboot when Odin is done flashing. Now You can disconnect your device.
Done!!! TWRP is now installed on your device
NOTE: YOU MAY HAVE TO UNCHECK AUTO REBOOT IN THE OPTIONS TAB IN ODIN
TWRP source code: https://github.com/TeamWin
Source code device tree: https://github.com/travismills82/twrp_android_device_samsung_c9ltechn https://github.com/TeamWin/android_device_samsung_c9ltechn/
TWRP Nougat Download: https://www.androidfilehost.com/?fid=889964283620775437
TWRP Oreo Download: https://www.androidfilehost.com/?fid=1322778262903985796
no-verity-no-encrypt: https://www.androidfilehost.com/?fid=745425885120752506
ROOT OPTIONS:
SuperSU: https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Magisk: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Contributors @travis82 @k2wl @deadman96385
I can confirm this works. backup, mount data, restore, otg usb, install.
I am runnung it now
Does this work on a SM-C9000?
Flavio said:
Does this work on a SM-C9000?
Click to expand...
Click to collapse
That's already for C9000. Can't you see the c9ltechn article. That's c9 pro's code
Thank you. I have already installed it.
I have flashed TWRP, formatted Data twice, flashed no-verity-opt-encrypt-5.1.zip, flashed SuperSU and after that I can mount Data. But after a reboot I can't anymore? Am I doing something wrong?
Flavio said:
Thank you. I have already installed it.
I have flashed TWRP, formatted Data twice, flashed no-verity-opt-encrypt-5.1.zip, flashed SuperSU and after that I can mount Data. But after a reboot I can't anymore? Am I doing something wrong?
Click to expand...
Click to collapse
You can flash any file still that just an article but you can't mount data anymore or backup data
I can flash files but cannot mount Data. I presume it is still encrypted despite being formatted twice?
Format data and reboot to recovery
ivanox1972 said:
Format data and reboot to recovery
Click to expand...
Click to collapse
So in TWRP format Data and then reboot again in TWRP.
And then flash SuperSU and no_verity?
Ok, I formatted Data twice in TWRP. Mounting Data works.
I flashed SuperSU in TWRP. Mounting Data works.
I flashed no_verity. Mounting Data works.
I rebooted into TWRP. Mounting Data works.
I rebooted into system and then switched off and rebooted into TWRP. Mounting Data does not work.
What am I doing wrong?
Correction:
I have now used this no-verity-no-encrypt_ashyx file:
https://www.androidfilehost.com/?fid=24591000424951049
And now Data stays decrypted!
I do have a stock debloated rom that is made out of HK firmware if this community is interested, I can put it up. All I see is you guys using Aurora. Anyone interested or do you all want to stick to Aurora rom?
I tested it few days, it works perfect and it is perfectly debloated
Please share Travis. Thank you for your work.
travis82 said:
I do have a stock debloated rom that is made out of HK firmware if this community is interested, I can put it up. All I see is you guys using Aurora. Anyone interested or do you all want to stick to Aurora rom?
Click to expand...
Click to collapse
can you share it please ???
I presume you would have to flash GApps separately with this ROM?
Flavio said:
I presume you would have to flash GApps separately with this ROM?
Click to expand...
Click to collapse
no god no, HK firmware has gapps built in like normal. I'll tweak it up some more and release it today on a separate thread. Right now I'm trying to get kernels to boot-up since they compile fine.
travis82 said:
I do have a stock debloated rom that is made out of HK firmware if this community is interested, I can put it up. All I see is you guys using Aurora. Anyone interested or do you all want to stick to Aurora rom?
Click to expand...
Click to collapse
I am interested, currently I just using the package disabler to disable all bloat samsung app..
do you have flashable s8 systemui for c9pro.. thanks
TWRP updated with a new kernel, USB MTP is now working. Everything should be working now.
travis82 said:
TWRP updated with a new kernel, USB MTP is now working. Everything should be working now.
Click to expand...
Click to collapse
Awesome work buddy, ill try to make my own ROM for this device :highfive:
will be pushing f2fs and ntfs support soon too when TWRP becomes official.
After updating my J5 2017 J530F to the latest Oreo 8.1 I was having trouble getting root and all things working again.
Hours of waiting for installs then something going wrong after applying the CF-Auto-root or trying to install Magisk or something and having to install again, Hours spent waiting..
Trying to install the auto-root would cause a verification error and force a system erase but not work again.
Thought i'd found the solution with the EDOs rom but then realised I had no bluetooth and had problems with mobile data.
After many efforts i found a way by simply installing the excellent Helios PRO kernel and manually installing Magisk after.
So I offer you the way i found to root my phone with Stock Oreo 8.1
A step by step breakdown of the method I used to fully root the fresh stock rom install.
First download the needed stuff
Latest Samsung Odin software. (3.13)
https://samsungodin.com/download
Download Link:
https://samsungodin.com/download/Odin3_v3.13.1.zip
USB Drivers.
https://samsungodin.com/SamsungUSBDriver/USB_Drivers_1.5.27.0.rar
New Oreo 8.1 Stock ROM
https://www.sammobile.com/firmwares/galaxy-j5/SM-J530F/BTU/
Download Link: https://www.sammobile.com/firmwares/galaxy-j5/SM-J530F/BTU/download/J530FXXU3BRL1/252803
TWRP
https://github.com/TwrpBuilder/andr...s/tag/TWRP-3.2.3-TwrpBuilder-2018-09-13_15-34
Download Link: https://github.com/TwrpBuilder/andr...2.3-TwrpBuilder-j5y17lte-2018-09-13_15-34.tar
The Helios Pro Kernel
https://forum.xda-developers.com/ga...velopment/kernel-refined-kernel-v1-0-t3675500
Note if you are not installing from fresh stock roms Helios kernel says...
If you have flashed Root through any means other than magisk, Please uninstall it (SuperSU>Full unroot)
Magisk , (All J5 roms kernels i installed that said they had magisk pre-installed never actually worked on my phone)
so I downloaded the files to manually install Magisk.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I used the main zip file and the manager apk
https://github.com/topjohnwu/Magisk/releases/download/v18.1/Magisk-v18.1.zip
https://github.com/topjohnwu/Magisk/releases/download/manager-v7.0.0/MagiskManager-v7.0.0.apk
Note: developer mode and OEM unlocking need to be enabled for most of these steps but many of the steps undo the settings so will need to be reapllied at various stages.
enable developer mode on phone by going to Settings/About phone/Software settings and keep pressing "Build Number" till developer mode activates then go back to main settings page and select "Developer Options" and make sure developer mode is enabled and USB debugging (i guess) and "OEM Unlock"
Method...
1. unpack Odin software and right click Launcher icon and select properties
Go to Compatibility settings and select Vista (service pack 2) compatibility.
Click okay and launch the Odin program.
2. Install stock ROM
Unpack the Oreo 8.1 files and use the buttons in Odin to load the BL , AP, CP and CSC files into each slot
Put phone into "Download Mode" by powering off and holding volume down - , home, and power buttons together till the screen pops up telling you to now press volume up to go to download mode.
Then plug in USB to computer.
Odin should report "Added" if you have correct samsung drivers on PC.
Then press "Start" in Odin.
Stock roms should all download to phone then it reboots.
3. Flash TWRP
Boot up phone, log into an account and get it all running then enable developer mode again.
Once set copy the Helios pro kernel zip file and the magisk zip and apk files to the phones SD card.
Now power down the phone and put it in download mode again.
Load Odin again and now put only the TWRP installer .tar file into the "AP" slot then select the "Options" tab in Odin and uncheck the auto reboot option. then hit start and flash twrp.
Load TWRP an install helios kernel
After flashing TWRP hold down the phones volume-down, home and power buttons and as soon as the screen goes blank immediately change volume down for volume up while still holding home and power.
then TWRP should load
Go to Wipe and select "Format Data" type yes to proceed , then back to wipe, select advanced wipe and wipe internal storage.
then back to TWRP main page and select "Install", select micro-sd card and point installer to the Helios Kernel zip file and install.
Install Magisk Manager app:
After booting up i still had no root so i installed the Magisk Manager apk using the "My files" app and launching it confirmed still no Magisk installed.
(I cannot recall if i had to go through the "Enable developer mode" again at this point but check if you need to or not)
Last Step, Manually Install Magisk.
Lastly I powered down the phone and held volume up, home and power key to launch TWRP
There i selected Install and installed the Magisk.zip file from SD card.
Finally the system booted, everything was working and i had root via an installed and working Magisk
Hope this helps someone..
Thanks! Worked ! even with existing OREO rom, did not flash rom, started with 2nd step
Sammobile is down
I can't download the stock oreo software. Are there any alternatives since im trying to reset my rooted phone back to stock..
Jens956 said:
I can't download the stock oreo software. Are there any alternatives since im trying to reset my rooted phone back to stock..
Click to expand...
Click to collapse
Use magisk uninstaller package?
palmbeach05 said:
Use magisk uninstaller package?
Click to expand...
Click to collapse
Man that wont work. I installed EDOS oreo ROM. I need to get it BACK TO STOCK, without any system modifications so i can sell my old phone to someone who wants it.
Jens956 said:
Man that wont work. I installed EDOS oreo ROM. I need to get it BACK TO STOCK, without any system modifications so i can sell my old phone to someone who wants it.
Click to expand...
Click to collapse
Ok well thats a bit more detail on your phone setup, i figured you had stock and were trying to unroot.
What is sammobile saying when you go to their site?
palmbeach05 said:
Ok well thats a bit more detail on your phone setup, i figured you had stock and were trying to unroot.
What is sammobile saying when you go to their site?
Click to expand...
Click to collapse
That the free downloads are unavailable because of maintenance
Jens956 said:
That the free downloads are unavailable because of maintenance
Click to expand...
Click to collapse
Try
http://updato.com/firmware-archive-select-model/
palmbeach05 said:
Try
http://updato.com/firmware-archive-select-model/
Click to expand...
Click to collapse
Yeah im currently downloading from there i think. It takes so many hours to download a 2gb zip :/
I can intall stock oreo and twrp but when reboot logo samsung is blocked
I have problem ... So when I put twrp file into odin AP section it gives me PASS message, but problem is after doing that it deletes all files in my phones internal storage my PC shows that 10gb out of 10gb internal storage in my phone is free. twrp works fine but if I try to boot system it gives me bootloop cuz there is no OS in my phone... any Ideas how to fix or what am I doing wrong? :/
BioBonus said:
After updating my J5 2017 J530F to the latest Oreo 8.1 I was having trouble getting root and all things working again.
Hours of waiting for installs then something going wrong after applying the CF-Auto-root or trying to install Magisk or something and having to install again, Hours spent waiting..
Trying to install the auto-root would cause a verification error and force a system erase but not work again.
Thought i'd found the solution with the EDOs rom but then realised I had no bluetooth and had problems with mobile data.
After many efforts i found a way by simply installing the excellent Helios PRO kernel and manually installing Magisk after.
So I offer you the way i found to root my phone with Stock Oreo 8.1
A step by step breakdown of the method I used to fully root the fresh stock rom install.
First download the needed stuff
Latest Samsung Odin software. (3.13)
https://samsungodin.com/download
Download Link:
https://samsungodin.com/download/Odin3_v3.13.1.zip
USB Drivers.
https://samsungodin.com/SamsungUSBDriver/USB_Drivers_1.5.27.0.rar
New Oreo 8.1 Stock ROM
https://www.sammobile.com/firmwares/galaxy-j5/SM-J530F/BTU/
Download Link: https://www.sammobile.com/firmwares/galaxy-j5/SM-J530F/BTU/download/J530FXXU3BRL1/252803
TWRP
https://github.com/TwrpBuilder/andr...s/tag/TWRP-3.2.3-TwrpBuilder-2018-09-13_15-34
Download Link: https://github.com/TwrpBuilder/andr...2.3-TwrpBuilder-j5y17lte-2018-09-13_15-34.tar
The Helios Pro Kernel
https://forum.xda-developers.com/ga...velopment/kernel-refined-kernel-v1-0-t3675500
Note if you are not installing from fresh stock roms Helios kernel says...
If you have flashed Root through any means other than magisk, Please uninstall it (SuperSU>Full unroot)
Magisk , (All J5 roms kernels i installed that said they had magisk pre-installed never actually worked on my phone)
so I downloaded the files to manually install Magisk.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
I used the main zip file and the manager apk
https://github.com/topjohnwu/Magisk/releases/download/v18.1/Magisk-v18.1.zip
https://github.com/topjohnwu/Magisk/releases/download/manager-v7.0.0/MagiskManager-v7.0.0.apk
Note: developer mode and OEM unlocking need to be enabled for most of these steps but many of the steps undo the settings so will need to be reapllied at various stages.
enable developer mode on phone by going to Settings/About phone/Software settings and keep pressing "Build Number" till developer mode activates then go back to main settings page and select "Developer Options" and make sure developer mode is enabled and USB debugging (i guess) and "OEM Unlock"
Method...
1. unpack Odin software and right click Launcher icon and select properties
Go to Compatibility settings and select Vista (service pack 2) compatibility.
Click okay and launch the Odin program.
2. Install stock ROM
Unpack the Oreo 8.1 files and use the buttons in Odin to load the BL , AP, CP and CSC files into each slot
Put phone into "Download Mode" by powering off and holding volume down - , home, and power buttons together till the screen pops up telling you to now press volume up to go to download mode.
Then plug in USB to computer.
Odin should report "Added" if you have correct samsung drivers on PC.
Then press "Start" in Odin.
Stock roms should all download to phone then it reboots.
3. Flash TWRP
Boot up phone, log into an account and get it all running then enable developer mode again.
Once set copy the Helios pro kernel zip file and the magisk zip and apk files to the phones SD card.
Now power down the phone and put it in download mode again.
Load Odin again and now put only the TWRP installer .tar file into the "AP" slot then select the "Options" tab in Odin and uncheck the auto reboot option. then hit start and flash twrp.
Load TWRP an install helios kernel
After flashing TWRP hold down the phones volume-down, home and power buttons and as soon as the screen goes blank immediately change volume down for volume up while still holding home and power.
then TWRP should load
Go to Wipe and select "Format Data" type yes to proceed , then back to wipe, select advanced wipe and wipe internal storage.
then back to TWRP main page and select "Install", select micro-sd card and point installer to the Helios Kernel zip file and install.
Install Magisk Manager app:
After booting up i still had no root so i installed the Magisk Manager apk using the "My files" app and launching it confirmed still no Magisk installed.
(I cannot recall if i had to go through the "Enable developer mode" again at this point but check if you need to or not)
Last Step, Manually Install Magisk.
Lastly I powered down the phone and held volume up, home and power key to launch TWRP
There i selected Install and installed the Magisk.zip file from SD card.
Finally the system booted, everything was working and i had root via an installed and working Magisk
Hope this helps someone..
Click to expand...
Click to collapse
You've helped me get an old J5 2017 rooted. Cheers!! Merry Christmas!!
{
"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"
}
Official TWRP 3.6.1-* For Galaxy Note 20 & Note 20 UltraOnly for exynos variants - N980F / N981B / N985F / N986B (Europe - Global, Single/Dual-SIM)
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Kernel Features:
N986BXXU3FVC5 kernel source (OneUI 4.1 / March 2022 sourcecode)
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
Recovery Features:
Android 11 tree
built in full 64 mode
toybox/busybox support
compatible with Android 12.0 and above
Downloads:
Galaxy Note 20 (c1s / N980F / N981B)
Galaxy Note 20 Ultra (c2s / N985F / N986B)
AVB disabled vbmeta
* official TWRP builds are not up yet, you can find latest test builds in post #2, below
Instructions:
Odin (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .tar file according to your device
Download AVB disabled vbmeta .tar
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Heimdall (Linux)
Install heimdall & additional required packages:
Code:
sudo apt-get update
sudo apt-get install heimdall-flash android-tools-fastboot android-tools-adb libusb-0.1-4 libusb-1.0-0 libusb-1.0-0-dev
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .img file according to your device
Download AVB disabled vbmeta .img
Open your preferred terminal in linux and type (replace red lines with the path of downloaded img files):
Code:
sudo heimdall flash --RECOVERY /path/to/recovery.img --VBMETA /path/to/vbmeta.img
and press enter - once you press enter grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
TWRP
Download .img file for your device and install from your current TWRP with Install image - browse to image location and select - Recovery
dd (Requires root)
Download .img file for your device, place it in the root of your /sdcard folder, rename it to twrp.img then run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13100000.ufs/by-name/recovery
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Sources:
Device trees - c1s / c2s
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9830/tree/android-11.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
As always, if you like what i do, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu
Compatibility and changelog:
06.05.2022 - Initial TWRP 3.6.1 release
Compatibility: Android 12 (OneUI 4.0 & 4.1)
Security patch: N/A
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
Further reading:
Full guide of how to unlock/root your device
Background on Android Verified Boot
Rollback protection
FAQ
Q: Can i use this recovery with other firmware then mentioned in compatibility?
A: Only with same Android version or Rollback protection might kick in and you won't be able to pass the lockscreen.
Q: Where do i get vbmeta.img?
A: From here, download the one you need according to install instructions.
Q: TWRP can't mount data partition, what to do?
A: Make sure you formatted data partition.
Q: Phone is not booting even after 20 minutes
A: Try to reboot. If still not booting, make sure you flashed multidisabler zip / formatted data partition.
Q: How to format data partition?
A:
Q: Phone is showing only Samsung logo
A: Try to reboot. If still not booting, consider installing an older TWRP build or a more recent firmware. If you still don't succeed, post here some details about your device and previous firmware and we might be able to help.
Q: Why do i need to format data partition?
A: Because old firmware encrypted your data partition and new rom can't decrypt and use that content / root needs access to data partition to place misc files / phone not booting after flashing root until data partition gets formatted.
Thanks for this. Where is twrp.img for Note 20 Ultra 5G / N986B
Updated first post with official pages from twrp.me, but since the builds are not up yet, i posted latest test builds in post #2.
Regards
Thanks, for this I'll keep for more year Note 20 Ultra. Time to wait or maybe make GSI for Note.
Yaayyyy
I m newbie to note 20 ultra...i want to flash root and twrp... What steps shld i follow.... Currently i m on stock non rooted.. Confused what to flash via odin..
@corsicanu
Many thanks for the latest update mate. It's working perfectly, as everything from you does
corsicanu said:
Compatibility and changelog:
06.05.2022 - Initial TWRP 3.6.1 release
Compatibility: Android 12 (OneUI 4.0 & 4.1)
Security patch: N/A
Misc links:
TeamWin official website
Telegram Support Group
Telegram Channel
Bootloaders / modems zips
Latest Magisk stable or canary
Further reading:
Full guide of how to unlock/root your device
Background on Android Verified Boot
Rollback protection
Click to expand...
Click to collapse
I notice I have bootloder on my device that I didn't install my self. I'm just a average user and have no clue how this was put on my phone. Also all of my apps are older versions an I'm unable to update them. I need help figuring out what's going on. Anyone please help!!!
@corsicanu
Many thanks for the latest update mate
1. Can I use this TWRP version with any custom ROM (e.g. Dr. Ketan ROM)?
2. Do I have to flash vbmeta.img, even when I have that custom ROM?
3. Is there a twrp.img for N986B that supports Android encryption, since right now encryption is somehow disabled after installing Dr. Ketan ROM: the lockscreen password has no effect and I can access and read all files on all partitions with the TWRP file manager !
monicaONxda said:
1. Can I use this TWRP version with any custom ROM (e.g. Dr. Ketan ROM)?
2. Do I have to flash vbmeta.img, even when I have that custom ROM?
3. Is there a twrp.img for N986B that supports Android encryption, since right now encryption is somehow disabled after installing Dr. Ketan ROM: the lockscreen password has no effect and I can access and read all files on all partitions with the TWRP file manager !
Click to expand...
Click to collapse
1. Yes as long as the rom dev doesn't have other instructions regarding the recovery used (i.e. LineageOs)
2. No, you already have some nulled vbmeta flashed since you are running a custom rom.
3. Nope, since samsung uses proprietary encryption. You can however preserve data encryption in the rom (talk that with the dev of your rom), but this will make it unreadable by twrp in any conditions. Please keep in mind that Samsung fw may not like it and it can trigger a data wipe without warnings.
Regards.
corsicanu said:
1. Yes as long as the rom dev doesn't have other instructions regarding the recovery used (i.e. LineageOs)
2. No, you already have some nulled vbmeta flashed since you are running a custom rom.
3. Nope, since samsung uses proprietary encryption. You can however preserve data encryption in the rom (talk that with the dev of your rom), but this will make it unreadable by twrp in any conditions. Please keep in mind that Samsung fw may not like it and it can trigger a data wipe without warnings.
Regards.
Click to expand...
Click to collapse
Where's 2.8
corsicanu said:
1. Yes as long as the rom dev doesn't have other instructions regarding the recovery used (i.e. LineageOs)
2. No, you already have some nulled vbmeta flashed since you are running a custom rom.
3. Nope, since samsung uses proprietary encryption. You can however preserve data encryption in the rom (talk that with the dev of your rom), but this will make it unreadable by twrp in any conditions. Please keep in mind that Samsung fw may not like it and it can trigger a data wipe without warnings.
Regards.
Click to expand...
Click to collapse
Many Thanks!
Re. 3.: With "fw" you meant FRP? But when I have root I can simply erase FRP and most Knox and other unwanted bloatware apks on /system, /product, /prism etc. ?
Btw. do you know if there is there a possibility to completely remove the Samsung ROM and replace it with a plain Android? You may lose one hardware driver for the "Sasmung Pen" but everthying else should work..?
monicaONxda said:
Many Thanks!
Re. 3.: With "fw" you meant FRP? But when I have root I can simply erase FRP and most Knox and other unwanted bloatware apks on /system, /product, /prism etc. ?
Btw. do you know if there is there a possibility to completely remove the Samsung ROM and replace it with a plain Android? You may lose one hardware driver for the "Sasmung Pen" but everthying else should work..?
Click to expand...
Click to collapse
Fw as in firmware. Regarding plain android - search for AOSP based projects, i'm not aware of the active developement so i can't properly advice you in this matter.
Regards
corsicanu said:
Official TWRP 3.6.1-* For Galaxy Note 20 & Note 20 UltraOnly for exynos variants - N980F / N981B / N985F / N986B (Europe - Global, Single/Dual-SIM)
Disclaimer
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this recovery before flashing it!
YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Kernel Features:
N986BXXU3FVC5 kernel source (OneUI 4.1 / March 2022 sourcecode)
disabled uh/defex/proca/knox/rkp/rooting protection/logging/audit/useless features
Recovery Features:
Android 11 tree
built in full 64 mode
toybox/busybox support
compatible with Android 12.0 and above
Downloads:
Galaxy Note 20 (c1s / N980F / N981B)
Galaxy Note 20 Ultra (c2s / N985F / N986B)
AVB disabled vbmeta
* official TWRP builds are not up yet, you can find latest test builds in post #2, below
Instructions:
Odin (Windows)
Prerequisites: Samsung USB drivers, Odin v3.14.1
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .tar file according to your device
Download AVB disabled vbmeta .tar
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Heimdall (Linux)
Install heimdall & additional required packages:
Code:
sudo apt-get update
sudo apt-get install heimdall-flash android-tools-fastboot android-tools-adb libusb-0.1-4 libusb-1.0-0 libusb-1.0-0-dev
If you already have the bootloader unlocked you can skip to step 6.
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode;
Long press vol up then confirm you want to unlock bootloader (this is needed one time only);
* Please be aware all your data will be erased including internal storage and phone will reboot!!
Let the phone boot normally, pass the setup and connect to internet (wireless or mobile data) in order to unlock RMM;
Make sure OEM Unlock is ON in developer settings;
Turn off the phone;
Use vol up + vol down + usb cable plugged to a pc to start the phone in download mode, short press vol up to confirm you want to go to download mode;
* If by any chance you see RMM state=Prenormal or KG state=Prenormal, redo from step 5!
Download appropriate TWRP .img file according to your device
Download AVB disabled vbmeta .img
Open your preferred terminal in linux and type (replace red lines with the path of downloaded img files):
Code:
sudo heimdall flash --RECOVERY /path/to/recovery.img --VBMETA /path/to/vbmeta.img
and press enter - once you press enter grab the phone and press vol up + power to force it boot straight in TWRP after flashing
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
TWRP
Download .img file for your device and install from your current TWRP with Install image - browse to image location and select - Recovery
dd (Requires root)
Download .img file for your device, place it in the root of your /sdcard folder, rename it to twrp.img then run the following commands via adb shell or a terminal emulator app:
Code:
su
dd if=/sdcard/twrp.img of=/dev/block/platform/13100000.ufs/by-name/recovery
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Sources:
Device trees - c1s / c2s
Kernel - https://github.com/corsicanu/android_kernel_samsung_universal9830/tree/android-11.0
Recovery - https://github.com/omnirom/android_bootable_recovery
Credits:
TeamWin, geiti94, jesec, dyneteve, ianmacd, testers, donors and anyone else involved in making this possible
As always, if you like what i do, you can always send me some pizza/coffee/drugs/drinks or anything else via paypal.me/corsicanu
Click to expand...
Click to collapse
i am trying to root my note 20 u device. when all succesfully start from magisk module and twrp, i find the screen flicker for a second every 15 seconds. I'm trying to figure out which app the problem is from. looked in screen recorder and found the problem. apparently from system ui. then start again from the initial step one by one. and the cause of the problem is after installing twrp. I'm on Ui5.1 N986B exyns. i feel twrp has a bug
Now im use back stock recovery and problem has gone
Hi it's been a while since I last install TWRP on SS phone, it got complicated now I have few question, can you help answering?
Open Odin v3.14.1 and place the downloaded TWRP .tar file in AP tab, downloaded vbmeta .tar file in CP tab and click Start - once you press start grab the phone and press vol up + power to force it boot straight in TWRP after flashing
Click to expand...
Click to collapse
- For this, do I have to press the key combo 1 time only after clicking Start Odin or I have to hold till the progress done?
2.
!! Only if coming from full stock (magisk patched) firmware
In TWRP home screen press wipe - format data - yes
Download and flash multidisabler-samsung-3.* zip to disable security and encryption.
Click to expand...
Click to collapse
- I never install TWRP on my phone, do I have to follow this step?
-If yes, do I have to install that file right after TWRP first boot (when odin completed flashing)
And finally, does it support android 13?
Thank you so much