{
"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"
}
unofficial TWRP 3.5.0 for SM-N986x Snapdragon
*** This will only work on Snapdragon devices with an unlocked bootloader, but is technically compatible with all snapdragon Note 20 Ultra devices.
SM-N9860 - SM-N986U/U1
Telegram thread
Built using OMNI source 10.0
TWRP v3.5.0
See post #2 for install steps
Changelog...
3.4.0-1
Initial build
MTP, OTG and SDcard all working
Encryption not working
3.4.0-2
Fixed brightness
Updated kernel
3.5.0-11
* Android R only
* If you are using any other version of twrp for R, I would update. Same with kernel.
Updated twrp to latest bleeding edge
Fastboot now functional in twrp
Keyrefuge and keystore now wipeable
TWRP Downloads
TWRP 3.5.0 Downloads
WETA Kernel Downloads
OrangeFox Downloads
SkyHawk Downloads
Forced Encryption Disabler (included in TWRPx)
Telegram thread
--------------------->
Beer fund
XDA:DevDB Information
TWRP Note 20 Ultra (snapdragon), Kernel for the Samsung Galaxy Note 20 Ultra
Contributors
Mentalmuso, mentalmuso
Source Code: - Kernel Source | Device tree c2q | Device tree c1q
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 3.4.0-1
Created 2020-09-08
Last Updated 2020-09-08
Instructions
* Unlock bootloader - Enable dev settings, switch the oem unlock switch, boot into download mode, hold the
volume up button, confirm unlocking.
* Be aware, first clean boot, hangs on building cache, hard reboot after waiting about 3min and you'll boot past this
* If simply updating your existing TWRP, you only need to flash the TWRP.img in recovery.
Process from bone stock (TH* firmware)
1. Boot into stock recovery, and perform a factory reset before flashing TWRP
2. Boot into Download mode, Flash TWRP.tar in AP slot in Odin (uncheck autoreboot)
3. Reboot directly into TWRP (hold vol+ and Bixby)
4. Format data, reboot recovery (format, not wipe. You will be asked to type "yes" if you have done it right)
5. Flash kernel img in twrp.
6. Flash encryption disabler.
7. Flash Magisk.
8. Reboot system (first boot may hang on samsung boot animation, hard reboot to kick it on)
Process from existing TWRP
1. Flash TWRP.img to recovery partition from within TWRP
2. Reboot system
Telegram thread
--->
USA stuff
I personally own the SM-N9860 device. I successfully converted the csc region to USA (tmobile) by doing the following.
1. Created a .tar of super.img from TH3 SM-N986U1 firmware (AP)
2. Created a .tar of prism.img.lz4, optics.img.lz4, cache.img.lz4, omr.img.lz4 from TH3 SM-N986U1 firmware (CSC)
3. Flash with odin, super.tar in the AP slot, and the CSC.tar in the CSC slot.
4. Boot into stock recovery and perform a factory reset
You will also need to edit mps_code.dat inside /efs/imei to reflect the carrier you desire. This needs to be done from a rooted system or from TWRP. After doing this and rebooting, you will be booted into your carriers system.
--->
Mentalmuso said:
USA stuff
I personally own the SM-N9860 device. I successfully converted the csc region to USA (tmobile) by doing the following.
1. Created a .tar of super.img from TH3 SM-N986U1 firmware (AP)
2. Created a .tar of prism.img.lz4, optics.img.lz4, cache.img.lz4, omr.img.lz4 from TH3 SM-N986U1 firmware (CSC)
3. Flash with odin, super.tar in the AP slot, and the CSC.tar in the CSC slot.
4. Boot into stock recovery and perform a factory reset
You will also need to edit mps_code.dat inside /efs/imei to reflect the carrier you desire. This needs to be done from a rooted system or from TWRP. After doing this and rebooting, you will be booted into your carriers system.
--->
Click to expand...
Click to collapse
Mentalmuso My bro, Will this work on Exynos SM-N986B/DS version. Thanks for all your hard work buddy. :good:
Edited : Will Wait for latest Version of September from Sammobile then Will Give a try and Report later. thx bro.
Mentalmuso said:
USA stuff
I personally own the SM-N9860 device. I successfully converted the csc region to USA (tmobile) by doing the following.
1. Created a .tar of super.img from TH3 SM-N986U1 firmware (AP)
2. Created a .tar of prism.img.lz4, optics.img.lz4, cache.img.lz4, omr.img.lz4 from TH3 SM-N986U1 firmware (CSC)
3. Flash with odin, super.tar in the AP slot, and the CSC.tar in the CSC slot.
4. Boot into stock recovery and perform a factory reset
You will also need to edit mps_code.dat inside /efs/imei to reflect the carrier you desire. This needs to be done from a rooted system or from TWRP. After doing this and rebooting, you will be booted into your carriers system.
--->
Click to expand...
Click to collapse
What the benefit? I have it too and in Canada
---------- Post added at 10:12 AM ---------- Previous post was at 09:39 AM ----------
Mentalmuso said:
Instructions
* Unlock bootloader - Enable dev settings, switch the oem unlock switch, boot into download mode, hold the
volume up button, confirm unlocking.
* Be aware, first clean boot, hangs on building cache, hard reboot after waiting about 3min and you'll boot past this
* If simply updating your existing TWRP, you only need to flash the TWRP.img in recovery.
Process from bone stock (TH* firmware)
1. Flash TWRP.tar in Odin (uncheck autoreboot)
2. Reboot directly into TWRP (hold vol+ and Bixby)
3. Format data, reboot recovery
4. Flash kernel (use img flash, flash boot.img)
5. Flash encryption disabler.
6. Flash Magisk.
7. Reboot system
Process from existing TWRP
1. Flash TWRP.img to recovery partition from within TWRP
2. Reboot system
N986x TWRP 3.4.0 Downloads
WETA Kernel
Forced Encryption Disabler
Telegram thread
--->
Click to expand...
Click to collapse
can u elaborate, what do I pick in ODIN and is it the patched kernel which is in the root thread? u say img flash and boot.img
Are these 2 files
inningsdefeat500 said:
What the benefit? I have it too and in Canada
---------- Post added at 10:12 AM ---------- Previous post was at 09:39 AM ----------
can u elaborate, what do I pick in ODIN and is it the patched kernel which is in the root thread? u say img flash and boot.img
Are these 2 files
Click to expand...
Click to collapse
Pick AP in odin to flash twrp.
Use img flash function in twrp to flash the kernel/boot.img. and I have no idea about the root thread so no, this is my own source built kernel.
beautyangel said:
Mentalmuso My bro, Will this work on Exynos SM-N986B/DS version. Thanks for all your hard work buddy. :good:
Edited : Will Wait for latest Version of September from Sammobile then Will Give a try and Report later. thx bro.
Click to expand...
Click to collapse
I'm confident that flashing the super.img from a snapdragon device on an exynos won't work.
Though flashing the csc imgs may get you somewhere. But I had trouble getting the csc to stick before flashing the super.img also.
Will this work for n976n (Korean variant, snapdragon)
It has the bootloader unlock in developer settings
interestingkid said:
Will this work for n976n (Korean variant, snapdragon)
It has the bootloader unlock in developer settings
Click to expand...
Click to collapse
I responded in telegram, thanks
Mentalmuso said:
USA stuff
I personally own the SM-N9860 device. I successfully converted the csc region to USA (tmobile) by doing the following.
1. Created a .tar of super.img from TH3 SM-N986U1 firmware (AP)
2. Created a .tar of prism.img.lz4, optics.img.lz4, cache.img.lz4, omr.img.lz4 from TH3 SM-N986U1 firmware (CSC)
3. Flash with odin, super.tar in the AP slot, and the CSC.tar in the CSC slot.
4. Boot into stock recovery and perform a factory reset
You will also need to edit mps_code.dat inside /efs/imei to reflect the carrier you desire. This needs to be done from a rooted system or from TWRP. After doing this and rebooting, you will be booted into your carriers system.
--->
Click to expand...
Click to collapse
So this will get us off the hongkong firmware? And we will get updates with our carrier?
---------- Post added at 06:38 PM ---------- Previous post was at 06:31 PM ----------
Mentalmuso said:
USA stuff
I personally own the SM-N9860 device. I successfully converted the csc region to USA (tmobile) by doing the following.
1. Created a .tar of super.img from TH3 SM-N986U1 firmware (AP)
2. Created a .tar of prism.img.lz4, optics.img.lz4, cache.img.lz4, omr.img.lz4 from TH3 SM-N986U1 firmware (CSC)
3. Flash with odin, super.tar in the AP slot, and the CSC.tar in the CSC slot.
4. Boot into stock recovery and perform a factory reset
You will also need to edit mps_code.dat inside /efs/imei to reflect the carrier you desire. This needs to be done from a rooted system or from TWRP. After doing this and rebooting, you will be booted into your carriers system.
--->
Click to expand...
Click to collapse
So this will get us off the hongkong firmware? And we will get updates with our carrier?
Mentalmuso said:
Pick AP in odin to flash twrp.
Use img flash function in twrp to flash the kernel/boot.img. and I have no idea about the root thread so no, this is my own source built kernel.
Click to expand...
Click to collapse
I already have root with Magisk - should I bone stock and then follow this
Sent from my SM-N9860 using Tapatalk
Mentalmuso said:
unofficial TWRP 3.4.0 for SM-N986x Snapdragon
*** This will only work on Snapdragon devices with an unlocked bootloader, but is technically compatible with all snapdragon Note 20 Ultra devices.
SM-N9860 | SM-N986U + U1 (if oem unlock is ever achieved)
Telegram thread
Built using OMNI source 10.0
TWRP v3.4.0
See post #2 for install steps
Changelog...
v1
Initial build
MTP, OTG and SDcard all working
Encryption not working
TWRP Downloads
N986x TWRP 3.4.0 Downloads
WETA Kernel
Forced Encryption Disabler
Telegram thread
--------------------->
Beer fund
XDA:DevDB Information
TWRP Note 20 Ultra (snapdragon), Kernel for the Samsung Galaxy Note 20 Ultra
Contributors
Mentalmuso, mentalmuso
Source Code: [url]https://github.com/mentalmuso/android_kernel_samsung_sd865plus_twrp[/URL]
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 3.4.0-1
Created 2020-09-08
Last Updated 2020-09-08
Click to expand...
Click to collapse
Bud, I followed but its booting back in TWRP all the time
I started from Bone Stock
Reboots to TWRP only
I put Bone Stock back and followed Dr Ketans root and TWRP instructions but extracted recovery.img from this thread and the Encryption Disabler - all seemed OK in TWRP but
Reboots to TWRP only
Did this work for anyone?
---------- Post added at 08:25 AM ---------- Previous post was at 08:04 AM ----------
Mentalmuso said:
Pick AP in odin to flash twrp.
Use img flash function in twrp to flash the kernel/boot.img. and I have no idea about the root thread so no, this is my own source built kernel.
Click to expand...
Click to collapse
When I do this, I select Boot Partiton right?
Sorry, asking too many questions as OP instructions didn't work, it simply boots back to TWRP
Well, Just Follow OP Instructions.
My Phone Rooted, I Follow Dr.Ketan Instructions how to root in Exynos section.
Am on latest Stock Rom, All Bloatware Remove with Adb Shell command.
1. I do Not install TWRP.
I extract Patched AP (magisk) and copy Boot.img, then convert Boot to Patched Kernel.tar
And Follow OP Instructions for CSC
I confirmed All working Great Guys. We Can Change our CSC Carrier. "THAT'S A MAJOR MAJOR MAJOR GO". Really thats Awesome. Mentalmuso My Bro That's Awesome share Buddy. You Really Rock on this One. :highfive::good:
KURDKiNG said:
So this will get us off the hongkong firmware? And we will get updates with our carrier?
---------- Post added at 06:38 PM ---------- Previous post was at 06:31 PM ----------
So this will get us off the hongkong firmware? And we will get updates with our carrier?
Click to expand...
Click to collapse
I never said that, once rooted you aren't going to get any updates from anywhere. Rooting breaks ota
inningsdefeat500 said:
Bud, I followed but its booting back in TWRP all the time
I started from Bone Stock
Reboots to TWRP only
I put Bone Stock back and followed Dr Ketans root and TWRP instructions but extracted recovery.img from this thread and the Encryption Disabler - all seemed OK in TWRP but
Reboots to TWRP only
Click to expand...
Click to collapse
Did you format data?
beautyangel said:
Well, Just Follow OP Instructions.
My Phone Rooted, I Follow Dr.Ketan Instructions how to root in Exynos section.
Am on latest Stock Rom, All Bloatware Remove with Adb Shell command.
1. I do Not install TWRP.
I extract Patched AP (magisk) and copy Boot.img, then convert Boot to Patched Kernel.tar
]And Follow OP Instructions for CSC
I confirmed All working Great Guys. We Can Change our CSC Carrier. "THAT'S A MAJOR MAJOR MAJOR GO". Really thats Awesome. Mentalmuso My Bro That's Awesome share Buddy. You Really Rock on this One. :highfive::good:
Click to expand...
Click to collapse
I saw that as well, but can we install Root, TWRP and change CSC for this, my issues is getting stuck at going back to TWRP - u never tried that right
---------- Post added at 02:07 PM ---------- Previous post was at 02:02 PM ----------
[/COLOR]
Mentalmuso said:
I never said that, once rooted you aren't going to get any updates from anywhere. Rooting breaks ota
Click to expand...
Click to collapse
Mentalmuso said:
Did you format data?
Click to expand...
Click to collapse
I see your point about root, but like many I chose to do so - however, for inserting TWRP and making sure I do it right. I reloaded Stock Rom and followed your instructions. All went fine except, it boots back to TWRP only. In the end, didn't work and I gave up and just regular root now
Thus asking if this worked for anyone else, why is it that I got back to TWRP - if you like I can make a whole video of my process
** yes, I formatted data **
inningsdefeat500 said:
I got it rooted too , no issues - unsure what instruction abt CSC, as this is Snapdragon
Click to expand...
Click to collapse
Did you follow my methods in post #2 or ketans, just want to figure out what's happened to the other guys.
Mentalmuso said:
Did you follow my methods in post #2 or ketans, just want to figure out what's happened to the other guys.
Click to expand...
Click to collapse
I did yours which ended up going to TWRP
I tried Ketan's ( with how to get TWRP while rooting ) and it was same results - i.e, going back to TWRP
inningsdefeat500 said:
I got it rooted too , no issues - unsure what instruction abt CSC, as this is Snapdragon
---------- Post added at 02:07 PM ---------- Previous post was at 02:02 PM ----------
I see your point about root, but like many I chose to do so - however, for inserting TWRP and making sure I do it right. I reloaded Stock Rom and followed your instructions. All went fine except, it boots back to TWRP only. In the end, didn't work and I gave up and just regular root now
Thus asking if this worked for anyone else, why is it that I got back to TWRP - if you like I can make a whole video of my process
** yes, I formatted data **
Click to expand...
Click to collapse
I'm trying to figure out what happened to you is all. And I don't mean to offend by asking what seems to be obvious questions.
Giving me as much info as you can is only going to help. What firmware did you flash, and is your device BRI, TGY?? what csc did you come with when purchased.
I just downloaded and reflashed both kernel and twrp and had no problem. Though I did convert to usa system and vendor. I don't think that would matter
Related
I do not own the device anymore. So I can't support the thread anymore, if anyone wants to carry on just pm me. But as far as I know there are newer threads about this topic. Thank you
Hey there,
I decided to write a how-to on gaining root for the g531f Galaxy grand prime ve.
This should work for all grand prime devices based on marvel soc.
About this method:
Knox counter was not tripped for my device using this method.
The main steps, flashing latest stock and twrp, are perfomed by Odin. To gain root chainfire's supersu is flashed with twrp. If you are unsure about any step there are enough guides found on xda refering odin, twrp and supersu.
So let's get started.
I`M NOT RESPONSIBLE FOR ANY DAMAGE OR WARANTY LOST ON YOUR PHONE.
1. Make sure your device drivers is installed properly
2. Get Odin v3.09 for example here:
http://www.droidviews.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/
3. Get your latest firmware and extract it once
http://www.sammobile.com/firmwares/database/SM-G531F/
4. Get twrp
https://dl.twrp.me/grandprimevelte/twrp-2.8.7.1-grandprimevelte.img.tar.html
5. Get supersu by chainfire
Latest beta
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Or confirmed working version 5.52 beta, if the latest doesn't work thanks to @XelSam:
https://download.chainfire.eu/743/Su...erSU-v2.52.zip
6. Backup all things you need and copy supersu to external sd card
7. Boot to stock recovery and perform a factory reset and wipe internal memory.
(power off device and keep holding volume up, home and power button)
8. Reboot to download Mode, then start odin and connect your device
(holding volume down, home and power button to get into download Mode)
9. Flash your firmware with Odin by using the AP button and hit start. Make sure repartition is NOT selected and untick auto reboot. This step takes some time
10. Boot to download Mode again. And flash twrp as mentioned above. Using AP and the same selection.
--if twrp doesn't boot you have to use another firmware (step 9) post #20-- thanks to @bluepower
11. Boot into twrp recovery. Hit install and select the supersu zip file then clean cache and dalvic.
(holding volume up, home and power button)
12. Reboot your phone and see if everything is working.
13. Go to dev settings and tick "manufacturer unlock" to prevent fap lock.
(unlock dev settings: Settings - about phone - tap build number 7 times). If that doesn't work check post #4 and #6 and say thx to @hck5
14. Make a nandroid in twrp recovery to have a clean rooted rom to return to if anything gets messed up with further modding (eg. xposed framework etc.)
10.1 100%Working firmware
If you can't find a version that allows to flash twrp (carrier lock) use this unbranded one:
http://www.sammobile.com/firmwares/download/61237/G531FXXU1AOJ2_G531FDBT1AOI2_DBT/
Check gps. If it doesn't lock install this app and configure your region.
https://play.google.com/store/apps/details?id=by.zatta.agps
CREDITS and CUDOS
chainfire
Twrp team
Odin team
Samsung
If you are interested in xposed check wanams xposed thread.
http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3180960
The x86 version is working fine for me
For audio enhancement I'm using dolby atmos cause Viper didn't do the trick for me.
http://forum.xda-developers.com/android/apps-games/mod-dolby-atmos-t3109446
So have fun with your unchained device and hit thanks button.
Great job!
Hey there i have the same model and i'm happy that last night i've found your post
i used the pre-rooted firmware and i had the system ui rebooting problem after i uninstalled any of the apps
also i've seen guys who had that security tab problem from settings (didn't happened to me)
I am extracting the stock rom now i prepared everything
i also wanted so badly the viper fx cause the sound is pretty low
i searched for alternative but here you are with dolby atmos
i greatly thank you for the effort for posting this tuto
i will be back after i do the job!
Thanks!!!
---------- Post added at 12:46 PM ---------- Previous post was at 12:25 PM ----------
Root and twrp on stock rom it's working great!!
i just flashed the wanam xposed thu twrp everything done
the only bad part is the "recovery is not seandroid" but this is just a red small message above when i enter twrp and it has no bad effect! only visual
i am clearing dalvik and cache after every flash so i keep it smooth and nice i can't wait to test modules on this phone i will post screenshots as proofs
hck5 said:
Root and twrp on stock rom it's working great!!
i just flashed the wanam xposed thu twrp everything done
the only bad part is the "recovery is not seandroid" but this is just a red small message above when i enter twrp and it has no bad effect! only visual
i am clearing dalvik and cache after every flash so i keep it smooth and nice i can't wait to test modules on this phone i will post screenshots as proofs
Click to expand...
Click to collapse
Thx for your feedback and confirmation that it is working.
So have fun with your device.
BTW don't forget to make a nandroid backup before you mess around with xposed modules to get back to your rooted rom. I destroyed my system twice with xposed.... And I had to go through this procedure again (thanks touchwiz).
okay
ok. thanks for the advice i was just messing with the modules and i have no backup xD
there is a pic with all i have so far
{
"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"
}
---------- Post added at 02:25 PM ---------- Previous post was at 02:08 PM ----------
custom binary locked by fap lock.... shiet... this is the google account thingie
do you know any way to bypass it? it means i can't add my google account
i just tried to reboot in recovery and it's showing up and can't boot my phone so far...
ok flashing stock fixes it
and this is the ultimate fix
"i faced the same !steps you need to follow settings>search>reactivation lock>log in into Samsung account and disable" thanks to bhavstech xda member
hck5 said:
custom binary locked by fap lock.... shiet... this is the google account thingie
do you know any way to bypass it? it means i can't add my google account
i just tried to reboot in recovery and it's showing up and can't boot my phone so far...
ok flashing stock fixes it
Click to expand...
Click to collapse
Try to unlock via dev settings. Manufacturer unlock.
http://forum.xda-developers.com/attachment.php?attachmentid=3495074&d=1443947143
If that doesn't work you have to delete your Google account as far as I know.
For me it is working with Google account, but I can't remember if I ticked the dev setting option before or after adding my Google account.
for me has been this one
klausel said:
5. Get supersu by chainfire
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Click to expand...
Click to collapse
Probably a stupid question but why can't we just install SuperSU from Play Store?
Edit: Okay, I've noticed that the version in the xda thread is newer. Anyway why not install it the usual way (sideloading)?
eau4x6 said:
Probably a stupid question but why can't we just install SuperSU from Play Store?
Edit: Okay, I've noticed that the version in the xda thread is newer. Anyway why not install it the usual way (sideloading)?
Click to expand...
Click to collapse
I don't know exactly what you mean with sideloading app.
But as far as I know root is needed to install supersu via Google play store. Of course you can sideload the app via adb shell when booted to twrp. But I wanted to keep the tutorial simple without setting up adb etc.
Hope your question is answered.
Thank's for recovery
I thing a new nice rom will coming soon for 531F
klausel said:
Of course you can sideload the app via adb shell when booted to twrp.
Click to expand...
Click to collapse
Transfering APK to internal storage/sd card and installing from there (by opening it in file manager) is what I had in mind.
I don't think is that easy.. You must set system read and write and I guess twrp helps it installing supers in a better way than your file manager does
---------- Post added at 12:49 PM ---------- Previous post was at 12:45 PM ----------
We just need a hell of a rom
finally thank you very much! ?
Hello i have a new SM-G531F and i'm trying to install TWRP but don't result.
Version: G531FXXUAOI4
Compilation: LMY48B.G531FXXUAOI4
Lollipop 5.1.1
I have samsung drivers installed. Odin 3.10.7.
I install via ODIN the tar file of TWRP with sucess, but when i try to enter goes to stock recovery.
With volume up + home + power before enter the stock recovery i can see this message "recovery is not seandroid enforcing"
bluepower said:
Hello i have a new SM-G531F and i'm trying to install TWRP but don't result.
Version: G531FXXUAOI4
Compilation: LMY48B.G531FXXUAOI4
Lollipop 5.1.1
I have samsung drivers installed. Odin 3.10.7.
I install via ODIN the tar file of TWRP with sucess, but when i try to enter goes to stock recovery.
With volume up + home + power before enter the stock recovery i can see this message "recovery is not seandroid enforcing"
Click to expand...
Click to collapse
The same strange problem is @XelSam facing, too.
I don't know why it is booting to stock recovery instead of twrp. What is written on top when you boot to dl mode? Could you post a picture, please.
Maybe it is the odin version or the recovery partition is locked.
So here is what you might try
Make sure your device is not fap locked
1. Get the odin version from op
2. Flash firmware with reboot unticked
3. Power down device and boot directly to dl mode again (do not boot the system) and flash twrp with reboot unticked.
4. Power down the device and boot try to boot to twrp
Good luck
klausel said:
The same strange problem is @XelSam facing, too.
I don't know why it is booting to stock recovery instead of twrp. What is written on top when you boot to dl mode? Could you post a picture, please.
Maybe it is the odin version or the recovery partition is locked.
So here is what you might try
Make sure your device is not fap locked
1. Get the odin version from op
2. Flash firmware with reboot unticked
3. Power down device and boot directly to dl mode again (do not boot the system) and flash twrp with reboot unticked.
4. Power down the device and boot try to boot to twrp
Good luck
Click to expand...
Click to collapse
DL mode is written:
ODIN MODE(MULTI CORE DOWNLOAD)
PRODUCT NAME: SM-G531F
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX WARRANTY VOID: 0x0
SECURE DOWNLOAD: ENABLED
RP SWREV: S1, L1, M1
Ok. I'm going to try again.
Thanks
bluepower said:
DL mode is written:
ODIN MODE(MULTI CORE DOWNLOAD)
PRODUCT NAME: SM-G531F
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX WARRANTY VOID: 0x0
SECURE DOWNLOAD: ENABLED
RP SWREV: S1, L1, M1
Ok. I'm going to try again.
Thanks
Click to expand...
Click to collapse
Hmm, system status should be official.
And another line that says FAP LOCK : OFF
Isn't there the newer firmware j2 available for your device? Which country are you from?
When running odin, Kies is not allowed as background service. Check your windows task manager and kill it.
klausel said:
Hmm, system status should be official.
And another line that says FAP LOCK : OFF
Isn't there the newer firmware j2 available for your device? Which country are you from?
When running odin, Kies is not allowed as background service. Check your windows task manager and kill it.
Click to expand...
Click to collapse
The phone is brand new. I'm from Portugal, carrier MEO
I think the firmware is not avaiable.
bluepower said:
The phone is brand new. I'm from Portugal, carrier MEO
I think the firmware is not avaiable.
Click to expand...
Click to collapse
I see, looks like your rom is carrier specific. I just checked for your firmwares, I even could not find your version.
To unbrand your device you can try to flash another version.
I used this one:
http://www.sammobile.com/firmwares/download/61237/G531FXXU1AOJ2_G531FDBT1AOI2_DBT/
I DON'T KNOW IF THIS WILL WORK, CAUSE MY DEVICE IS UNLOCKED. SO THERE IS A SMALL POSSIBILITY THAT THIS WILL BRICK YOUR DEVICE. BUT THERE ARE SO MANY PEOPLE THAT FLASH THE PREROOTED ONE AND NOBODY REPORTED THAT, YOU CAN TRY THIS.
BE CAREFUL, THIS could RESULT IN WARRANTY LOSS. SO IF YOU HAVE TO SEND IN DEVICE FLASH BACK A CARRIER SPECIFIC ROM BACK.
So it is on you if you are willing to try it.
klausel said:
Hmm, system status should be official.
And another line that says FAP LOCK : OFF
Isn't there the newer firmware j2 available for your device? Which country are you from?
When running odin, Kies is not allowed as background service. Check your windows task manager and kill it.
Click to expand...
Click to collapse
klausel said:
I see, looks like your rom is carrier specific. I just checked for your firmwares, I even could not find your version.
To unbrand your device you can try to flash another version.
I used this one:
http://www.sammobile.com/firmwares/download/61237/G531FXXU1AOJ2_G531FDBT1AOI2_DBT/
I DON'T KNOW IF THIS WILL WORK, CAUSE MY DEVICE IS UNLOCKED. SO THERE IS A SMALL POSSIBILITY THAT THIS WILL BRICK YOUR DEVICE. BUT THERE ARE SO MANY PEOPLE THAT FLASH THE PREROOTED ONE AND NOBODY REPORTED THAT, YOU CAN TRY THIS.
BE CAREFUL, THIS could RESULT IN WARRANTY LOSS. SO IF YOU HAVE TO SEND IN DEVICE FLASH BACK A CARRIER SPECIFIC ROM BACK.
So it is on you if you are willing to try it.
Click to expand...
Click to collapse
I'm back. Thanks. I'm going to try now.
Edit: Ok, done.
I installed de G531FXXU1AOI4_G531FOXX1AOI3_TPH for Portugal.
Then get the software update to the J2.
Great job, thanks a lot.
bluepower said:
I installed de G531FXXU1AOI4_G531FOXX1AOI3_TPH for Portugal.
Then get the software update to the J2.
Great job, thanks a lot.
Click to expand...
Click to collapse
Glad to know you got it and thanks for your feedback.
To rule out all misunderstandings and help other people with the same problem.
1. You flashed a rom from another carrier for your region and 2. updated it to the latest version via ota.
3. You installed twrp and 4. supersu
Is that the way you proceeded.?
Did the line for fap lock appear in dl mode?
Thanks in advance
Introduction
Code:
/*
* Your warranty is now void.
*
* 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 ROM
* 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.
*/
Important!You MUST be updated to the lastest firmware or this ROM will not work properly!
How to install1- Boot to TWRP and wipe system, data, cache and dalvik-cache.
2- Flash the ROM.
3- Flash your choice of zips from here to disable dm-verity (no-verity-opt-encrypt will disable force-encryption, no-verity-force-encrypt will keep force encryption, but disable dm-verity).
4- Flash the latest Magisk if you want root.
5- If you want Magisk modules to work properly, flash the kernel here: https://forum.xda-developers.com/mo...release-f2fs-bug-fix-kernel-qualcomm-t3724103 then a zip to disable dm-verity and Magisk.
5- Reboot TWRP. (This is important to keep the stock recovery from replacing TWRP!)
6- Allow TWRP to modify system. (This important to be able to flash zips and have them actually make changes.)
7- Reboot.
DownloadsSprint XT1776 Stock NCR26.58-44 for Sprint All Variants Untouched-Sprint/Boost/Virgin Mobile
Retail XT1775 Stock NPR26.58-25 Untouched-Retail
Important!You MUST flash the deodexed oem.img zip with the deodexed ROMs!
No need to flash a zip for disabling dm-verity and forced encryption with the deodexed versions. The kernel is already patched for this along with init.d enabled.
Latest Deodexed Stock for Sprint All Variants Deodexed-Sprint/Boost/Virgin Mobile
Deodexed-debloated (deGoogled) Stock for Sprint All Variants Deodexed-debloated- Sprint/Boost/Virgin Mobile
Deodexed-fully-debloated (deGoogled/deMotoed) Stock for Sprint All Variariants Deodexed-debloated-deGoogled-DeMotoed-Sprint/Boost/Virgin Mobile
Deodexed-debloated oem.img for Sprint All Variants Deodexed-oem- Sprint/Boost/Virgin Mobile
Debloated, deodexed, and other variants coming soon.
DO NOT flash Gapps, because this is stock based they are already included and this will likely cause problems!
Contributors
Goose03
Credits
Big thanks to
SuperR. for
SuperR's Kitchen
ROM OS Version: 7.1 Nougat
ROM Kernel: Linux 3.18
Based on: Stock
Version Information
Status: Fully stable
Created 2018-3-02
Last Updated 2018-3-02
Reserved
Reserved.
If someone with the retail variant updates with the latest ota I'm hearing about, I'll make a flashable if you can provide me with a system backup before rooting.
Thank you for this. Now we have a stock option to flash with TWRP instead of fastboot. And no forced encryption.. That is going to speed this little device up some... Great job. As soon as you have a retail version out for use in the XT1775, I will test.
Sent from my Nexus 6 using XDA Premium HD app
glockman4519 said:
Thank you for this. Now we have a stock option to flash with TWRP instead of fastboot. And no forced encryption.. That is going to speed this little device up some... Great job. As soon as you have a retail version out for use in the XT1775, I will test.
Click to expand...
Click to collapse
I made a twrp flashable ota update zip (partition updater) for the sprint variants and the E4 sprint variants. They've been tested and work fine (this guy was happy https://forum.xda-developers.com/showpost.php?p=75854847&postcount=25) for use with the ROMs made from the same firmware version. If someone, after updating would pull me the required imgs along with the system backup, I'll make a retail version also. Otherwise you won't be able to use the updated ROM without taking the ota update or flashing the firmware with fastboot first when it is released.
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
If someone with the retail variant updates with the latest ota I'm hearing about, I'll make a flashable if you can provide me with a system backup before rooting.
Click to expand...
Click to collapse
When you say a system backup, what are all of the partitions that you need?
---------- Post added at 04:43 PM ---------- Previous post was at 04:40 PM ----------
Also how do I get the updated version full zip like it is here:
https://firmware.center/firmware/Motorola/Moto E4 Plus/Stock/
soaringowl2145 said:
When you say a system backup, what are all of the partitions that you need?
---------- Post added at 04:43 PM ---------- Previous post was at 04:40 PM ----------
Also how do I get the updated version full zip like it is here:
https://firmware.center/firmware/Motorola/Moto E4 Plus/Stock/
Click to expand...
Click to collapse
I only need a twrp system backup and the pulled boot.img, oem.img and modem.img, the only parts with patches in the ota. The rest installs fine being replaced rather than just patched. That newer firmware isn't released yet. You'll have to wait.
Edit: actually I need a twrp boot.img backup also, I like to have both just in case.
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
I only need a twrp system backup and the pulled boot.img, oem.img and modem.img, the only parts with patches in the ota. The rest installs fine being replaced rather than just patched. That newer firmware isn't released yet. You'll have to wait.
Click to expand...
Click to collapse
How exactly do I pull the OEM, and modem? Can it be done through fastboot or adb? Also will this zip need to be installed on top of the current retail zip or can we install it the first time?
soaringowl2145 said:
How exactly do I pull the OEM, and modem? Can it be done through fastboot or adb? Also will this zip need to be installed on top of the current retail zip or can we install it the first time?
Click to expand...
Click to collapse
With adb:
dd if=/dev/block/bootdevice/by-name/oem of=/oem.img
or you can also use the terminal in twrp:
dd if=/dev/block/bootdevice/by-name/oem of=sdcard/oem.img
or a terminal emulator from the Play Store and do it right on the phone while the OS is running with the same commands as for the twrp terminal. For the modem just replace oem with modem.
Edit: with a system backup, I will make a ROM that will be able to be clean installed, but anyone who hasn't updated with the ota or official firmware will have to flash the partition updater I make before flashing the ROM.
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
With adb:
dd if=/dev/block/bootdevice/by-name/oem of=/oem.img
or you can also use the terminal in twrp:
dd if=/dev/block/bootdevice/by-name/oem of=sdcard/oem.img
or a terminal emulator from the Play Store and do it right on the phone while the OS is running with the same commands as for the twrp terminal. For the modem just replace oem with modem.
Edit: with a system backup, I will make a ROM that will be able to be clean installed, but anyone who hasn't updated with the ota or official firmware will have to flash the partition updater I make before flashing the ROM.
Click to expand...
Click to collapse
I will use twrp to backup system, system image, and boot. Then I will use adb to pull the system, boot, oem, modem, and modemst1 and 2 and upload those. That is all you need right?
---------- Post added at 06:22 PM ---------- Previous post was at 06:20 PM ----------
soaringowl2145 said:
I will use twrp to backup system, system image, and boot. Then I will use adb to pull the system, boot, oem, modem, and modemst1 and 2 and upload those. That is all you need right?
Click to expand...
Click to collapse
Also after flashing twrp and doing a backup to take the next ota do I just need to flash stock recovery back and then do the ota?
soaringowl2145 said:
I will use twrp to backup system, system image, and boot. Then I will use adb to pull the system, boot, oem, modem, and modemst1 and 2 and upload those. That is all you need right?
---------- Post added at 06:22 PM ---------- Previous post was at 06:20 PM ----------
Also after flashing twrp and doing a backup to take the next ota do I just need to flash stock recovery back and then do the ota?
Click to expand...
Click to collapse
I only need what I asked for, no more. I don't need a twrp system image. Only the normal backup. Also, the modem.img nothing more.
I'm not sure your understanding this. What I need is for you to flash the existing stock firmware package with fastboot, the whole package. Boot up your device and install the ota update, then flash twrp and make the system and boot backup and then pull the oem and modem.
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
I only need what I asked for, no more. I don't need a twrp system image. Only the normal backup. Also, the modem.img nothing more.
I'm not sure your understanding this. What I need is for you to flash the existing stock firmware package with fastboot, the whole package. Boot up your device and install the ota update, then flash twrp and make the system and boot backup and then pull the oem and modem.
Click to expand...
Click to collapse
I think I understand this. Use twrp to backup system and boot. Then use adb to pull oem and modem.
Right?
Edit:. I have already done the fastboot full flash and done the ota.
soaringowl2145 said:
I think I understand this. Use twrp to backup system and boot. Then use adb to pull oem and modem.
Right?
Edit:. I have already done the fastboot full flash and done the ota.
Click to expand...
Click to collapse
Yes
Edit: please pull the boot.img with adb also.
If you can zip up the system backup by itself and the rest together in another zip so it's not all one big zip that would be great.
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
Yes
Edit: please pull the boot.img with adb also.
Click to expand...
Click to collapse
Should I do a factory reset as well? I did disable some of the system apps through the normal settings. Or is a reset unnecessary?
Also will any of my personal info be pulled as well or just the Moto stuff?
soaringowl2145 said:
Should I do a factory reset as well? I did disable some of the system apps through the normal settings. Or is a reset unnecessary?
Also will any of my personal info be pulled as well or just the Moto stuff?
Click to expand...
Click to collapse
A factory reset isn't necessary, as long as you only disabled apps through settings and didn't actually modify the system any other way. None of your data will be included in anything I'm asking for unless you were to give me a backup of your data partition.
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
A factory reset isn't necessary, as long as you only disabled apps through settings and didn't actually modify the system any other way. None of your data will be included in anything I'm asking for unless you were to give me a backup of your data partition.
Click to expand...
Click to collapse
In that case I will probably upload this tonight after 11:30 but before 12:00 am EST time.
@Goose03 To take the next ota do I just flash stock recovery back then update?
soaringowl2145 said:
@Goose03 To take the next ota do I just flash stock recovery back then update?
Click to expand...
Click to collapse
You might be able to do that, as long as you didn't do anything but make a backup with twrp.
Sent from my Moto E (4) Plus using XDA Labs
Thank you both for taking on this endeavor!
Unofficial release -TWRP recovery for the Galaxy A6 plus 2018 - SM-A605 MSM8953
{
"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"
}
TWRP 3.2.3-0 Released
Aug 6, 2018
TWRP 3.2.3-0 is out now for most currently supported devices.
What's new in 3.2.3-0:
* Fix automatic installing of OTA zips on encrypted devices
* Remove SuperSU from TWRP
* Support both md5 and md5sum file extensions when doing MD5 checking for zip files
Want to get notifications when we release new versions of TWRP? Install the TWRP app and select your device!
We need your help! The bulk of TWRP work is done by a handful of people on a volunteer basis. We have pushed most of our device files to our github and we have a gerrit instance. If you have the ability, please help us maintain our official devices and/or add your device to our official device list. Thanks in advance!
You can track the progress of builds here
Update 18/11/2018
Beta build released.
Current status - Beta (tested working)
Treble supported
Update 14/12/18 - OTG support added.
You flash this at your own risk. Please ensure you have the stock ROM to hand downloaded from SAMMOBILE in case of problems. This will trip the knox counter.
NOTE: ON ANDROID 5.1.1> DEVICES IT IS NECESSARY TO GO TO:
Settings -> Developer Options -> OEM unlocking
AND ENABLE OEM UNLOCK FIRST OR YOU MAY ENCOUNTER 'BLOCKED BY FRP LOCK' WHEN FLASHING.
*****INSTALL INSTRUCTIONS:*****
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
(Hold POWER + VOL DOWN + VOL UP)
2. Load the file below into the AP slot and hit start.
twrp_3.2.3-1_sm-a605_141218
3. After flashing and ODIN reports PASS immediately force reboot to recovery. Do NOT let the device boot to the OS.
You should now see TWRP recovery.
4. Flash the RMM bypass zip
https://forum.xda-developers.com/attachment.php?attachmentid=4481843&d=1524258795
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
5. Reboot to TWRP (Do not boot to the OS yet)
6. Move on to root instructions below. This is a requirement to get the device to boot.
*****OREO ROOT INSTRUCTIONS:*****
1. Flash the Forced encryption disabler patch. This is only required if you wish to have full functionality in TWRP.
Flashing this will disable Samsung's forced encryption. Disabling encryption will allow TWRP to mount the data partition.
After flashing the patch it is necessary to *FORMAT* (not wipe) the /DATA partition using the FORMAT DATA button under the wipe options.
PLEASE NOTE THIS WILL DELETE EVERYTHING ON INTERNAL STORAGE AND FACTORY RESET THE DEVICE, SO BACK UP ANYTHING YOU WISH TO KEEP.
A605_oreo_forced_encryption_disabler
2. To root I suggest installing Magisk as this is a currently supported project, SuperSu is no longer getting active development.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
3. Enjoy your rooted device.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin, @nebkas for initial testing, @BlackMesa123 for RMM bypass zip.
Please note I don't own this device and spend a lot of my free time bringing these builds for you to use and benefit from.
FEEDBACK IS APPRECIATED PLEASE.
THANKS.
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
Hi, I also collected my twrp for sm-a605fn but I have a memory card and it mounts all partitions at once, can I help you? You can write in a telegram to me
kes228 said:
Hi, I also collected my twrp for sm-a605fn but I have a memory card and it mounts all partitions at once, can I help you? You can write in a telegram to me
Click to expand...
Click to collapse
Not sure what you mean by it mounts all partitions at once?
ashyx said:
Not sure what you mean by it mounts all partitions at once?
Click to expand...
Click to collapse
I had in mind that my rekvari sees all partitions at once, it seems like without encryption, he also sees a memory card from me at once, already disassembled your rekari! Good job
---------- Post added at 02:08 PM ---------- Previous post was at 02:00 PM ----------
kes228 said:
I had in mind that my rekvari sees all partitions at once, it seems like without encryption, he also sees a memory card from me at once, already disassembled your rekari! Good job
Click to expand...
Click to collapse
you can follow the link https://t.me/joinchat/AAAAAElB-MiezOR9qbn4MQ
For communication
post was obsoleted
U writes that your recovery virus is detected, hmm weird
Finally the King @ashyx trying to help us with Galaxy A6+ ... unfortunately i can not test it on my phone because i am on RMM state of the boatloader and i am waiting for a stock firmware for CNX or BGL ( east european country s ) to be released .
Hope i will try it soon ...
Thanks @ashyx for your dedication !!!!!
you are great ashyx. does this boot.img work with all the different regions firmware?
nebkas said:
Thanks a lot @ashyx
I will try it out in the evening. 15:00 we have here now in Romania, I will be arround in 7 hours.
I recommend all testers, to patch the boot.img with magisk from their own localized firmware. Download your firmware from samsungbay.
1. Flash the whole firmware, all included 5 files with odin.
2. extract from the AP_ file the boot.img.lz4 .
3. unpack the boot.img.lz4 with a command line tool. I ran into problems and not patchable boot.img with extracting with 7zip.
4. Install magisk manager app and go to install. Choose the before extracted boot.img from the original firmware. Magiskt will now patch the boot img and you will be able to flash it via odin.
------------------------------------------------------
5. after all that worked fine, flash the recovery with odin.
Now you should have a twrp recovery and boot into it. Format the data etc. at mentioned in the inital post.
Click to expand...
Click to collapse
Can I ask why you are suggesting that people patch the boot image with Magisk manager?
It's unnecessary. Just flash the Magisk zip with TWRP and you're done for root.
ariber14 said:
you are great ashyx. does this boot.img work with all the different regions firmware?
Click to expand...
Click to collapse
There's a good chance as the sources are the same for all models.
In my experience with other devices it will work without issue.
It's not strictly necessary to flash the patched boot image as Magisk may be able to patch the boot image. However not always which is why I provided it pre-patched.
balanadi said:
Finally the King @ashyx trying to help us with Galaxy A6+ ... unfortunately i can not test it on my phone because i am on RMM state of the boatloader and i am waiting for a stock firmware for CNX or BGL ( east european country s ) to be released .
Hope i will try it soon ...
Thanks @ashyx for your dedication !!!!!
Click to expand...
Click to collapse
At least this indeed confirms this device supports RMM.
In that case I should provide a link to the RMM patch here.
hi . when i wanna flash the pached boot in download mode it says only offical binaries are allowed to be flash
what should i do?
ashyx said:
Can I ask why you are suggesting that people patch the boot image with Magisk manager?
It's unnecessary. Just flash the Magisk zip with TWRP and you're done for root.
Click to expand...
Click to collapse
I always had issus to flash the recovery.img with oding, when I didnt flashed the localized patched boot.img from my firmware before. I did that to not get in trouble with RMM
---------- Post added at 18:16 ---------- Previous post was at 18:12 ----------
erfanhsz said:
hi . when i wanna flash the pached boot in download mode it says only offical binaries are allowed to be flash
what should i do?
Click to expand...
Click to collapse
Delete the google account, and restart your phone to disable FRP LOCK. Also check in developer options, that you check OEM UNLOCK ENABLE
nebkas said:
I always had issus to flash the recovery.img with oding, when I didnt flashed the localized patched boot.img from my firmware before. I did that to not get in trouble with RMM
Click to expand...
Click to collapse
What you're suggesting is no different to flashing the Magisk zip with TWRP. Except using Magisk manager just makes it a more long winded process, as there are extra steps involved.
As long as Magisk and RMM patch are flashed before booting to system there shouldn't be an issue.
ashyx said:
At least this indeed confirms this device supports RMM.
In that case I should provide a link to the RMM patch here.
Click to expand...
Click to collapse
great news!! finally we have decent twrp and root thanks to ashyx keep up the good job bro
ariber14 said:
great news!! finally we have decent twrp and root thanks to ashyx keep up the good job bro
Click to expand...
Click to collapse
Any chance you could do me a favour and post me the recovery.log with an SD CARD installed?
ashyx said:
Any chance you could do me a favour and post me the recovery.log with an SD CARD installed?
Click to expand...
Click to collapse
I haven't flashed twrp yet. Propably tonight will be done. Of course i will send you the recovery log
to disable rmm prenormal from twrp
https://drive.google.com/file/d/1mm86XUJOji0fZRhd4WqwSZmNN272X1Y-/view?usp=sharing
Wow you did amazing thing! but there is a small problem. I cannot change brightess in recovery.
Hello ashyx again how can I contact you?
Android 10 was released today for Galaxy M30 (INS) ,
Here i am posting 2 links
1. For users Who Just Want Stock Rom as it is
2. For Users Who Need rooted stock rom
Steps :
1. Download Zip and Extract
2. For without root users just flashing via odin would be enough
3. Progress if you wana root
4. when your done with setting up your stock rom , go into Software info and activate developer option
5. Turn on OEM unlock and turn off Auto Update System
6. Boot into download mode again
7. open odin and turn off auto reboot
8. Choose the magisk patched zip and extract
9. In Odin under AP choose this tar and flashed
10. now be careful and press volume down and power till your device boots and quickly press volume up and power to boot into recovery mode
11. Wipe Data in stock recovery and reboot and your good to go
So Here's a Grive Link
Both Firmwares need to be extracted and flashed via odin
Unrooted Stock Firmware
Stock Unrooted
Magisk Rooted
Magisk Rooted
XDAevDB Information
ANDROID 10 (ONEUI 2) Stock Firmware and Rooted (M305FDDU3CSL4), ROM for the Samsung Galaxy M30
Contributors
Er. Aditya
ROM OS Version: Android 10
Thanks to ,
Samsung For Firmware
topjohnwu for magisk
reserved just in case
last one
Sorry for ignorance, but... how do I flash the stock unrooted firmware using Odin?
shrmp said:
Sorry for ignorance, but... how do I flash the stock unrooted firmware using Odin?
Click to expand...
Click to collapse
unzip the zip file and there u will find these files
AP_M305FDDU3CSL4_CL17406009_QB27774088_REV00_user_low_ship_meta_RKEY_OS10.tar.md5
BL_M305FDDU3CSL4_CL17406009_QB27774088_REV00_user_low_ship.tar.md5
CP_M305FDDU3CSL1_CP14521597_CL17406009_QB27626610_REV00_user_low_ship.tar.md5
CSC_OMC_ODM_M305FODM3CSL4_CL17406009_QB27774088_REV00_user_low_ship.tar.md5
HOME_CSC_OMC_ODM_M305FODM3CSL4_CL17406009_QB27774088_REV00_user_low_ship.tar.md5
in odin on your right you will find slots to select files
under BL choose BL_M305FDDU3CSL4_CL17406009_QB27774088_REV00_user_low_ship.tar.md5
under AP choose AP_M305FDDU3CSL4_CL17406009_QB27774088_REV00_user_low_ship_meta_RKEY_OS10.tar.md5
under CP choose CP_M305FDDU3CSL1_CP14521597_CL17406009_QB27626610_REV00_user_low_ship.tar.md5
under CSC choose HOME_CSC_OMC_ODM_M305FODM3CSL4_CL17406009_QB27774088_REV00_user_low_ship.tar.md5
make sure ur phone is in download mode and you have your drivers installed
I see, does updating with Odin erase userdata?
---------- Post added at 22:05 ---------- Previous post was at 21:08 ----------
Nevermind, I just tried flashing the update but it does not work with the SM-M305M variant. Back to waiting...
Er. Aditya said:
7. open odin and turn off auto reboot
8. Choose the magisk patched zip and extract
9. In Odin under AP choose this tar and flashed
Click to expand...
Click to collapse
But, in Magisk here, it states:
Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Will it be any issues, if we just flash the AP?
Thanks. Flashed Magisk now.
Can i simply falsh it with twrp??
i did everything correctly i'm stuck on Samsung Boot Logo
help
zer0C00L...... said:
i did everything correctly i'm stuck on Samsung Boot Logo
help
Click to expand...
Click to collapse
these steps have been tested alot of times so make sure you dont miss any
Prxtek said:
Can i simply falsh it with twrp??
Click to expand...
Click to collapse
Nope. Plus this phone does not have a TWRP for Q as of now. Moreover, please do not try any TWRP as of now.
Use ODIN only.
---------- Post added at 00:48 ---------- Previous post was at 00:46 ----------
Er. Aditya said:
these steps have been tested alot of times so make sure you dont miss any
Click to expand...
Click to collapse
By any chance you have a list of bloatwares to remove?
vdbhb59 said:
Nope. Plus this phone does not have a TWRP for Q as of now. Moreover, please do not try any TWRP as of now.
Use ODIN only.
---------- Post added at 00:48 ---------- Previous post was at 00:46 ----------
By any chance you have a list of bloatwares to remove?
Click to expand...
Click to collapse
with root you can simply use titanium backuo and remove according to you
Er. Aditya said:
with root you can simply use titanium backuo and remove according to you
Click to expand...
Click to collapse
I tried, and I end up in bootloop, millions of times..
Trouble is, some inbuilt apps are bound with /system, and unable to get through. Moreover, you cannot imagine, I have been into bootloop 11 times since last evening.
So, if a list is present, I would be happy.
Last thing, did you notice, even if you have not logged into google account, it still keeps installing those 5 bloody recommended apps.
vdbhb59 said:
I tried, and I end up in bootloop, millions of times..
Trouble is, some inbuilt apps are bound with /system, and unable to get through. Moreover, you cannot imagine, I have been into bootloop 11 times since last evening.
So, if a list is present, I would be happy.
Last thing, did you notice, even if you have not logged into google account, it still keeps installing those 5 bloody recommended apps.
Click to expand...
Click to collapse
thats google preload stuff but happens just once , i havent faced this issue yet between make a list of apps your removing il take a look
and il work on a debloated version once i get some time
Please upload to one of the alternative sites (google quota block)
Whats the deal with U3, U4, U5 and greater version of bootloaders with Exynos chipset?
I know Samsung has locked bootloaders of USA snapdragon variants, but can all exynos chip-set ones be unlocked?
Or till U2 bootloader can be unlocked and can have root but above U3 cannot be rooted?
It's so confusing, Please someone Help me
Posted for the latest Patched Magisk here: https://forum.xda-developers.com/ga...d-firmware-t4026819/post81336955#post81336955
---------- Post added at 01:52 ---------- Previous post was at 01:52 ----------
For guides: https://forum.xda-developers.com/galaxy-m30/how-to/guide-galaxy-m30-recovery-edl-modes-t4020231
The M305M variant firmware with Android 10 can be found on sammobile. Can it be flashed without regard for the country it was made for or it has to be the same as the original firmware?
kesleyf said:
The M305M variant firmware with Android 10 can be found on sammobile. Can it be flashed without regard for the country it was made for or it has to be the same as the original firmware?
Click to expand...
Click to collapse
Can be used. However ensure you have mounted system.
You may lose data due to that. So ensure to have a backup.
Hi guys so Many users are facing issue while they are rooted and twrp installed on there phone.
They can't able to Flash update through stock settings OR via twrp if they tries to flash it via twrp manually facing no wifi and Bluetooth.
So here is the process to flash any incremental update via twrp just we need update zip, vbmeta image and boot image of old oos version respective to your new update means if. We are upgrading to V11 we need V10 boot img
U can use following commands to extract your current stock boot img after connecting to PC
adb shell
dd if=/dev/block/sdc49 of=/sdcard/boot.img
exit
Note: Remember this process will replace your twrp and removes root to gain root access. We need to repeat twrp installation shown in the following tutorial
TUTORIAL TWRP AND ROOT NORD 2 OXYGEN OS 11 ( Links updated!)
SO finally I successfully rooted with TWRP and root access.thanks to all developers @Eastw1ng @TheMalachite Following are all download links combined in one post Also there are two threads like unlocking boot loader and twrp but there are some...
forum.xda-developers.com
You can gain root acess only by flashing magisk.zip file after step no 7 given under instructions but I didn't tested it yet.
DOWNLOADS:
1)Download update v11 from Telegram :
®D$ in OnePlus Nord 2 Community
t.me
2) DOWNLOAD V13:
®D$ in OnePlus Nord 2 Community
t.me
3) Download V14 update zip:
️ in OnePlus Nord 2 Community
t.me
4) Download A15 update zip:
e9708c8610bae8fa64d76e0f9a55dda444ce981a.zip
drive.google.com
We can also download update in system update process. Just download OTA update and when we boot in twrp just click install and then go to following folder there you will find update.zip
/data/OTA-package/update.zip
5)A17 update zip:
https://t.me/OnePlusNord2GlobalOfficial/81364
Download vbmeta:
vbmeta.img | by TheMalachite for OnePlus Nord 2 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Download boot.img:
1) upgrade from v10 to v11(indian)
boot.img
drive.google.com
2) upgrade from v11 to v13(indian)
bootnew.img
drive.google.com
3)Upgrade from v13 to v14:
Rose in OnePlus Nord 2 Community
t.me
4)Upgrade from A14 to A15:
Rose in OnePlus Nord 2 Community
t.me
5)15 Boot img india (update from A15 to AA16)
https://t.me/OnePlusNord2GlobalOfficial/57795
5)A16 boot.img to upgrade to A17:
Rose in OnePlus Nord 2 Community
A16 stock boot image
t.me
6)17 BOOT IMG Upgrade to A18 (boot.img vbmeta zip extract file)
Rose in OnePlus Nord 2 Community
t.me
Boot img for nord 2 EU REGION :
File folder on MEGA
mega.nz
This another thread for all boot img of EU region
Stock Boot & Patched images Oneplus Nord 2 Oxygen 11.3 DN2103_11_A.07/09/10 EEA
Flash at your own risk. I am not responsible for any damage or data loss to the device during this process! https://mega.nz/folder/fZx2nBaR#Q33lJstFRMQg6_0j7Z0TJw Special Thanks: @HofaTheRipper @phhusson
forum.xda-developers.com
Instructions :
1) Download all file from the link given under this thread place them at one place on your phone so it can be easily accessible when we boot in TWRP.
2)Now to boot in TWRP use following root acess app called as advance reboot. Open it and click reboot to recovery
Advanced Reboot Tools [ROOT] - Apps on Google Play
Provides lots of options for restarting your device; excellent for tweakers.
play.google.com
Or you can use adb command after connecting phone to pc in USB debugging mode.
adb reboot recovery
3) when phone boot in TWRP click install tab now go to folder where we placed All files.
4) click install image tab at bottom now you we see image files boot. img and vbmeta.img that we downloaded
5)now select boot.img and then select boot partation and slide bottom bar after successful installation
6)click reboot and select recovery phone will boots back to twrp( This step is optional)
7)Now again click Install and find our old folder now select update.zip file and slide bottom bar it will take 2min for complete falshing of zip.
8)now agian click install now click install image and select vbmeta.img
9)Now click reboot system phone will reboots and take 10min.
Now you are successfully updated and have new OOS 11.3 A11 version on your phone without any issues.
Follow the video:
New update v13 update process :
New update A14 update process:
New update A15:
New update A16:
New A18 update:
pankspoo said:
Hi guys so Many users are facing issue while they are rooted and twrp installed on there phone.
They can't able to Flash update via twrp if they tries to flash it via twrp manually facing no wifi and Bluetooth.
So here is the process to flash any incremental update via twrp just we need update zip, vbmeta image and boot image of old oos version respective to your new update means if. We are upgrading to V11 we need V10 boot img.
Follow the video:
Click to expand...
Click to collapse
good Instructions! Reboot after flashing boot.img isnt necessary. OTA Update zip can be downloaded within OTA App in Settings (do not press reboot). After downloading you can reboot to TWRP and the file location is: /data/OTA-package/update.zip.
HofaTheRipper said:
good Instructions! Reboot after flashing boot.img isnt necessary. OTA Update zip can be downloaded within OTA App in Settings (do not press reboot). After downloading you can reboot to TWRP and the file location is: /data/OTA-package/update.zip.
Click to expand...
Click to collapse
Yes but I don't want to go to automatic reboot and flashing process of OTA Update installation after download which may cause some issues for new users.
The old boot.img I image is the stock one not rooted right? How can you extract it from your firmware if you're not rooted? From the Nandroid backup maybe?
Edit, found out: https://forum.xda-developers.com/t/how-to-extract-your-boot-img-from-any-rom-adb.3760210/ Just had to google it
Don't wo
Raygen said:
The old boot.img I image is the stock one not rooted right? How can you extract it from your firmware if you're not rooted? From the Nandroid backup maybe?
Click to expand...
Click to collapse
Donts worry from here every new updates we will provide all stock boot. img
Thread updated for latest update v13 for India region
HI. This is my 1st OnePlus and OxygenOS. I am now on DN2103_11_A.11 and OTA is available. It is DN2103_11_A.12
Basically I can flash it from TWRP and I do not need to save and flash boot.img afterwards bec OS will be the same version. Is that so? Or am I wrong? And I have to follow threads instructions ?
Thank you
jis251 said:
HI. This is my 1st OnePlus and OxygenOS. I am now on DN2103_11_A.11 and OTA is available. It is DN2103_11_A.12
Basically I can flash it from TWRP and I do not need to save and flash boot.img afterwards bec OS will be the same version. Is that so? Or am I wrong? And I have to follow threads instructions ?
Thank you
Click to expand...
Click to collapse
NO u need A11 boot img of only DN 2103 firmware not indian I don't have that now first flash that then flash update zip of v12 then flash Vbmeta now that's done
pankspoo said:
NO u need A11 boot img of only DN 2103 firmware not indian I don't have that now first flash that then flash update zip of v12 then flash Vbmeta now that's done
Click to expand...
Click to collapse
HI. And thx for quick reply. I mange now, thank you.
DN2103 A.11 stock boot img :
HofaTheRipper said:
DN2103 A.11 stock boot img :
Click to expand...
Click to collapse
You got it do it now
HofaTheRipper said:
DN2103 A.11 stock boot img :
Click to expand...
Click to collapse
HI and thx. I have made TWRP backup, boot and vbmeta
So I can first restore boot then flash OTA and then restore vbmeta, yes? (Version 11)
I do not have to flash boot and vbmeta, restore does the same??
jis251 said:
HI and thx. I have made TWRP backup, boot and vbmeta
So I can first restore boot then flash OTA and then restore vbmeta, yes? (Version 11)
I do not have to flash boot and vbmeta, restore does the same??
Click to expand...
Click to collapse
Don't use backup boot image restore process.
Just download above boot image given
https://forum.xda-developers.com/attachments/boot_stock_a11-img.5461307/
and vbmeta image given in. My thread
vbmeta.img | by TheMalachite for OnePlus Nord 2 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
And u r update zip of device of your region not mine
First flash boot img then. Install update zip then. Flash Vbmeta done
pankspoo said:
Don't use backup boot image restore process.
Just download above boot image given
https://forum.xda-developers.com/attachments/boot_stock_a11-img.5461307/
and vbmeta image given in. My thread
vbmeta.img | by TheMalachite for OnePlus Nord 2 5G
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
And u r update zip of device of your region not mine
First flash boot img then. Install update zip then. Flash Vbmeta done
Click to expand...
Click to collapse
Thx. OK I do that.
Magisk is installed (patched) to boot image so after OTA and Vbmeta I flash Magisk to keep root.
jis251 said:
Thx. OK I do that.
Magisk is installed (patched) to boot image so after OTA and Vbmeta I flash Magisk to keep root.
Click to expand...
Click to collapse
Yes
pankspoo said:
Download boot.img:
1) upgrade from v10 to v11(indian)
boot.img
drive.google.com
2) upgrade from v11 to v13(indian)
bootnew.img
drive.google.com
Click to expand...
Click to collapse
Do the boot.img files in the original post only work on the Indian variant? Where can I get the A11 boot.img for the European variant if I want to update to A12?
NetSoerfer said:
Do the boot.img files in the original post only work on the Indian variant? Where can I get the A11 boot.img for the European variant if I want to update to A12?
Click to expand...
Click to collapse
Ok I will upload in thread
NetSoerfer said:
Do the boot.img files in the original post only work on the Indian variant? Where can I get the A11 boot.img for the European variant if I want to update to A12?
Click to expand...
Click to collapse
File folder on MEGA
mega.nz
Use boot images from stock folder
pankspoo said:
U can use following commands to extract your current stock boot img after connecting to PC
adb shell
dd if=/dev/block/sdc49 of=/sdcard/boot.img
exit
Click to expand...
Click to collapse
Still trying to wrap my head around this (although updating worked fine from A11 to A12 on my EEA variant, thanks @pankspoo!).
Can I actually extract a stock boot.img from a Magisk-rooted phone? Is it stock (in which case why is root removed by the update.zip) or is it modified (in which case, why can I extract it as stock)?
NetSoerfer said:
Still trying to wrap my head around this (although updating worked fine from A11 to A12 on my EEA variant, thanks @pankspoo!).
Can I actually extract a stock boot.img from a Magisk-rooted phone? Is it stock (in which case why is root removed by the update.zip) or is it modified (in which case, why can I extract it as stock)?
Click to expand...
Click to collapse
You can use those adb commands while booted in TWRP, without being rooted. So you'll extract the stock boot image