[RECOVERY][ROOT]TWRP 3.1.0-1 Samsung Galaxy J3 Emerge SM-J327P - Samsung Galaxy J3 (2017) ROMs, Kernels, Recoveries

Unofficial release -TWRP recovery for the Galaxy J3 Emerge - SM-J327P, Qualcomm MSM8937
{
"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.1.0-0 Released
Mar 10, 2017
TWRP 3.1.0-0 is out now for all currently supported devices.
What's new in 3.1.0-0:
vold decrypt on a few select HTC devices, TWRP will now attempt to use the system partition's vold and vdc binaries and libraries to decrypt the data partition (nkk71 and CaptainThrowback)
adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
tweak MTP startup routines (mdmower)
support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
support POSIX file capabilities backup and restore to fix VoLTE on HTC devices and possibly other issues (Dees_Troy)
better indicate to users that internal storage is not backed up (Dees_Troy)
improve automatic determination of TW_THEME (mdmower)
minimal getcap and setcap support (_that)
try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
shut off backlight with power key (mdmower)
timeout during FDE decrypt (Dees_Troy and nkk71)
support for FBE decrypt and backing up and restoring FBE policies (Dees_Troy)
boot slot support (Dees_Troy)
TWRP app install prompt during reboot (Dees_Troy)
support for AB OTA zips (Dees_Troy)
support new Android 7.x log command (Dees_Troy)
update recovery sources to AOSP 7.1 (Dees_Troy)
numerous bugfixes and improvements by too many people to mention
Official TWRP App
Mar 11, 2017
Official TWRP App
The official TWRP app is the first and only first-party app developed by Team Win for TWRP. Please bear with us as we work to fix any bugs and build out the features. The initial version of the app does not support flashing on the Pixel due to the Pixel's A/B partition layout. In addition, the app may not support finding and flashing images from external storage locations. We are working hard to improve these items and bring you more new features.
Download Links:
We recommend downloading the app from the Play Store.
If you do not have Play Store access, you may download the Official TWRP App here: https://dl.twrp.me/twrpapp/
How do I use the app?
When you first open the app, you will be greeted by a few options. First, you will need to agree not to hold us responsible for anything that happens to your device while using the app. You may also grant the app root permissions. The app will work without root, but some functionality like image flashing will be disabled. Lastly, you can opt into enabling InsightCore (more on this feature later).
Once you have passed this initial screen, you will be greeted with the app home screen where you can choose TWRP FLASH or NETWORK STATISTICS (more on the network statistics later). On the TWRP FLASH screen you will need to select a device. Once you have selected a device, the app will periodically check for new TWRP versions for the device that you have selected. The default interval is once per day, but you can tap on the settings icon in the upper-right to change the interval or disable the update check entirely.
If you enabled root access, you will see options for selecting an image and buttons for flashing the selected image to boot or recovery. Note that you should flash TWRP images to recovery. The boot image flashing is for flashing full boot images (not just kernel zImages) and should not be used for flashing TWRP.
Update 15/3/2017
TWRP 3.1.0-1 MM build released.
Current status: BETA
Features:
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.
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.
Instructions:
Flash with ODIN 3.12.7 in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0 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.
DOWNLOAD:
twrp_3.1.0-1_j327p_14317
To Root:
Flash the latest SuperSU release with TWRP:
https://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/
To disable forced encryption and mount internal storage:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install SuperSU (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patch
no-verity-no-encrypt_ashyx
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my testers @Doctur, @infixremix, Teamwin
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
.
.

Reserved

Might of bought you a pack of smokes not the beer....either way donation was just a small thankyou...its been awhike withiut root im almost forgetting why i wanted it rooted in the first place lol Enjoy the smokes or w.e the donation goes to
Ur tha sh#$ bro

Doctur said:
Might of bought you a pack of smokes not the beer....either way donation was just a small thankyou...its been awhike withiut root im almost forgetting why i wanted it rooted in the first place lol Enjoy the smokes or w.e the donation goes to
Ur tha sh#$ bro
Click to expand...
Click to collapse
Thanks for the heads up with the other member and your support. I'll report it.

@ashyx by any chance do you have this device? .. i have 7.0 J327P seen it in the Samsung kitchen but not sure if its for the Sprint or Boostmobile worst case odin wont flash it

JUSMEJOSE said:
@ashyx by any chance do you have this device? .. i have 7.0 J327P seen it in the Samsung kitchen but not sure if its for the Sprint or Boostmobile worst case odin wont flash it
Click to expand...
Click to collapse
No sorry i don't own this device.

@ashyx, forgive me for not knowing, I am not familiar all that much with the various Samsung's and pre-paid phones. I have Nexus'.
Question, the boy got a prepaid from Best Buy and it is a Samsung J327P, running 6.0.1 yet the a search on Google shows different chip, a MSM8917. So will this recovery work or not on it? Here is a picture of the about screens.
View attachment 4081849
Don't want to screw it up since I don't have original firmware to flash back to it.
PS I seen in the thread talk of a link to where you can buy a copy of the firmware for some of these could you PM me that link please?
Thank you.
Sent from my Nexus 5X using XDA-Developers Legacy app

rekids said:
@ashyx, forgive me for not knowing, I am not familiar all that much with the various Samsung's and pre-paid phones. I have Nexus'.
Question, the boy got a prepaid from Best Buy and it is a Samsung J327P, running 6.0.1 yet the a search on Google shows different chip, a MSM8917. So will this recovery work or not on it? Here is a picture of the about screens.
Don't want to screw it up since I don't have original firmware to flash back to it.
PS I seen in the thread talk of a link to where you can buy a copy of the firmware for some of these could you PM me that link please?
Thank you.
Click to expand...
Click to collapse
Yes that's the same device. MSM8917 is the same platform as MSM8937.
You have no worries.
Just post back if you get stuck and need the firmware.

Thank you so much ?, will let you know how it goes.
Sent from my Nexus 5X using XDA-Developers Legacy app

I want to try this root but I get enter pin request when I try to turn on OEM unlocking. What should I do?

joeyjojojjjjjj said:
I want to try this root but I get enter pin request when I try to turn on OEM unlocking. What should I do?
Click to expand...
Click to collapse
Pin request? Never heard of that before. Have you set a pin/password on your device?

Nevermind, my daughter pit an unlock pin on it. Got it now going to try this.

Everything went smooth! Thank you so much!

rekids said:
Everything went smooth! Thank you so much!
Click to expand...
Click to collapse
Thanks for the click, out of 141 downloaders only 3 were clickers.
I find it amsusing that the author of the thread below using stolen files from this one has just as many clicks.
https://forum.xda-developers.com/an...-j3-emerge-t3573551/post71443474#post71443474
.

No problems at all... Everything went perfect!

I flashed TWRP and everything is now force closing.. Imma try to root since that factory resets the devices (hope i already had a previous backup of everything)
Edit: Everything worked! Thank you, Dev. One question, do we disable KNOX in SuperSU?

Cyclic said:
I flashed TWRP and everything is now force closing.. Imma try to root since that factory resets the devices (hope i already had a previous backup of everything)
Edit: Everything worked! Thank you, Dev. One question, do we disable KNOX in SuperSU?
Click to expand...
Click to collapse
Yes I'd advise disabling Knox.

need help!!!!
ashyx said:
Yes that's the same device. MSM8917 is the same platform as MSM8937.
You have no worries.
Just post back if you get stuck and need the firmware.
Click to expand...
Click to collapse
Any chance you have the firmware or boot.img? after i flashed the patch all went to hell and now my phone says it has no OS

pumkinhead13 said:
Any chance you have the firmware or boot.img? after i flashed the patch all went to hell and now my phone says it has no OS
Click to expand...
Click to collapse
There's no way the patch did that. You must have wiped the system partition in twrp.
https://www.androidfilehost.com/?fid=817550096634755921

ashyx said:
There's no way the patch did that. You must have wiped the system partition in twrp.
Click to expand...
Click to collapse
uuuh no, so I did all the above said to do and everything was fine, it booted up (before i flashed the patch) then I went back into recovery, flashed the patch and selected "boot to system" it booted to samsung logo then at the top in small yellow writing just said "kernal" it sat there for 15 mins, before i pulled the battery, then flashed again....this time upon finish it stated "NO OS"

Related

[RECOVERY]TWRP 3.0.3-1 unofficial [SM-T700/T705/800/805/807] - UPDATE 10/02/2017

UPDATE 10/02/2016- New version of TWRP has been released v3.0.3-0. See below:
https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html
I have updated versions SM-T800/805 with new builds. TWRP is now v3.0.3-1
TWRP OFFICIAL APP RELEASED: https://twrp.me/app/
Fixes:
Download mode now available in REBOOT options.
Root Shell now available in ADB.
Radio and Recovery backup.
System image backup/restore
Factory image flashing.
Supersu root option removed. This is to pre-empt the upgrade to MM which would cause a bootloop.
MTP fix - MTP now finally working in recovery.
Note: On my PC MTP works perfect in windows 7, but on Windows 8.1 was a little quirky. If you get a USB DEVICE NOT RECOGNISED error after enabling MTP, disable then quickly re-enable MTP and this should fix it.
This version also has system image backup and restore included. It is also possible to flash factory firmware images via the Image install button. (see the TWRP changelog above for more info)
UPDATE 5/3/16:
Have modified the twrp source code and extended factory image partition flashing to include all images except SBOOT.bin (still working on how to flash the bootloader via recovery)
This means BOOT, SYSTEM, RECOVERY, CACHE, HIDDEN, MODEM(RADIO) can all be flashed from the factory firmware. No need for ODIN anymore. As far as I know the Tab S is the only device supporting this at the moment.
(Note: to flash the modem it is necessary to rename MODEM.bin to MODEM.bin.img first)
TWRP_3.0.2-1-T700
TWRP-3.0.2-1-T705
TWRP-3.0.2-1-T800
NOTE: Certain models of the T800 version have a bug at the moment where the screen will be blank when booting to TWRP recovery until the screen timeout kicks in. After that pressing any button will show the screen. As a work around setting the timeout to 15 secs will shorten the wait.
TWRP-3.0.2-1-T805/T807(ATT or Verizon not supported)
twrp_3.0.3-1_sm-t800_10217
twrp_3.0.3-1_sm-t805_10217
FLASH WITH ODIN OR FLASHFIRE OR EXTRACT THE RECOVERY.IMG AND FLASH WITH TWRP
NOTE: It is important to boot to recovery after flashing with Odin or twrp may not stick and will be replaced with stock recovery.
When flashing uncheck auto reboot in Odin, immediately after flashing manually reboot and boot into twrp.
Manual reboot is POWER + HOME +VOL DOWN then as soon as the screen goes blank immediately change to VOL UP whilst still holding the other buttons.
{
"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"
}
FEEDBACK IS APPRECIATED PLEASE
DONATE ME HERE IF YOU WANT TO BUY ME A BEER OR HIT THE THANKS BUTTON IF I HELPED YOU
.
Is it possible to rebuild or for the sm-n9100? Note 4 duos?
Offering a bounty of $20 bucks to anyone's paypal account.
gcappa said:
Is it possible to rebuild or for the sm-n9100? Note 4 duos?
Offering a bounty of $20 bucks to anyone's paypal account.
Click to expand...
Click to collapse
As long the bootloader is unlocked, and if someone has an stock recovery pulled from it, then he could be twrp for it
Bootloader is unlocked. But I already flashed a modified cwm which doesn't work too well. So not sure if I could pull the stock recovery unless I reflash the stock rom.
gcappa said:
Bootloader is unlocked. But I already flashed a modified cwm which doesn't work too well. So not sure if I could pull the stock recovery unless I reflash the stock rom.
Click to expand...
Click to collapse
If you have the firmware downloaded just right click on the md5 and open it with 7zip or Winrar, then simply just drag the recover IMG to your desktop and send it here(or link to download). I'm not going to go to much in depth as I don't want this thread to be filled with non related to twrp stuff. I'm also unsure if he has time but ash is one good recovery builder
Ok, I'll do all that when I get home and upload a link.
gcappa said:
Is it possible to rebuild or for the sm-n9100? Note 4 duos?
Offering a bounty of $20 bucks to anyone's paypal account.
Click to expand...
Click to collapse
Should be possible as long as the right files are available. This is a snapdragon 805 device?
Seeing as I don't have this device you would have to test the builds and I would need some info from the device. Might take a few builds to get a proper working one.
I take it you are currently rooted? Also could you send me a link to the version of cwm you are using?
gcappa said:
Ok, I'll do all that when I get home and upload a link.
Click to expand...
Click to collapse
Is the sm-n9100 the Chinese version Note 4 Duos?
The TWRP recovery below is for this version, please test:
twrp-2860-n1900
Stock Recovery:
Stock-recovery-n1900
Note: You take responsibility for testing this.
Failed to flash on my T-800.
dwarfer66 said:
Failed to flash on my T-800.
Click to expand...
Click to collapse
What failed to flash? It's made for the t800. It flashes fine on a t805. No one else has had any issues. What is the full version of your device?
ashyx said:
Unofficial version of the latest TWRP, don't think it's been released yet.
Found it by accident for another device, so have rebuilt it for the Tab S Exynos version only.
TWRP-2.8.6.1
Click to expand...
Click to collapse
Thank again ashy this is awesome, keep up the good work.
Confirmed its working T800 5.0.2
ashyx said:
What failed to flash? It's made for the t800. It flashes fine on a t805. No one else has had any issues. What is the full version of your device?
Click to expand...
Click to collapse
This unofficial TWRP fails to flash, just says failed when trying to install.
dwarfer66 said:
This unofficial TWRP fails to flash, just says failed when trying to install.
Click to expand...
Click to collapse
Again, you need to confirm what your exact model is and build number. As you can see from the post above it flashes fine on a T800.
Post a screenshot of the issue with Odin.
It's flashing for me ok on my T800 with IronRom 2.0. Only thing is the root ain't working. Or do I need to unselect auto-reboot and do a forced shutdown? And clear cache and reboot?
Well it didn't boot up with the auto reboot it was stuck in bootloader so now trying to wipe cache/dalvik and it hangs on formatting cache using make_ext4fs function
edit: reflashed IronRom 2.0 to fix cache issue. After the cache wipe it boots up
edit2: it appears to be rooted but it ain't working. But when an app should ask for root permissions the app goes black screen. For Titanium backup it just hangs on checking
RDDraco said:
It's flashing for me ok on my T800 with IronRom 2.0. Only thing is the root ain't working. Or do I need to unselect auto-reboot and do a forced shutdown? And clear cache and reboot?
Well it didn't boot up with the auto reboot it was stuck in bootloader so now trying to wipe cache/dalvik and it hangs on formatting cache using make_ext4fs function
edit: reflashed IronRom 2.0 to fix cache issue. After the cache wipe it boots up
edit2: it appears to be rooted but it ain't working. But when an app should ask for root permissions the app goes black screen. For Titanium backup it just hangs on checking
Click to expand...
Click to collapse
Did you update the supersu app as requested? You need to post a screenshot of root validator so I can see the status of root.
You may just need to select full unroot from settings in the supersu app then boot into twrp and run the root process again or flash the supersu2.46 zip.
Also regarding wiping cache, it can sometimes take longer depending on what's in cache at the time. It may seem like it's hung but eventually completes. On occasion I've seen it take up to a few minutes to wipe.
Just saying that root is broken on custom roms such as iron rom. It's an known issue with touchwiz lollipop roms.
-DUHA
So it's a Rom issue?
What's the actual problem?
Isn't the Rom already rooted, unusual for a custom Rom to not be prerooted?
Guess that explains why it wasn't working. (Tkkg1994 managed to get IronRom working with root in v2.0.5) so its fine for me now.
RDDraco said:
Well it didn't boot up with the auto reboot it was stuck in bootloader so now trying to wipe cache/dalvik and it hangs on formatting cache using make_ext4fs function
Click to expand...
Click to collapse
Looked into this issue and have fixed it. Wipe Cache should work now.
ashyx said:
Unofficial version of the latest TWRP, don't think it's been released yet.
Found it by accident for another device, so have rebuilt it for the Tab S Exynos version only.
TWRP-2.8.6.1
NOTE: If after using TWRP to root you don't see the notification to update Supersu, just install the latest Supersu app from Play. Check root status with Root Validator
Supersu
Root validator
Click to expand...
Click to collapse
Just today, I rooted my new Tab S (SM-T800) AFTER allowing it to OTA update to Android 5.0.2. After that, I used Odin to flash the latest version of CWM I could find for this device, and that trashed recovery altogether. Couldn't get into recovery at all. So I used Odin again to flash TWRP 2.8.6.0 and had recovery back, BUT I kept getting notifications that SuperSU needed to be updated. What I did then was flash "BETA-SuperSU-v2.48.zip", and that resolved the "update needed" problem, and all seems to be working smoothly now. :good:
I'm running stock Touchwiz Lollipop 5.0.2 . Haven't tried changing ROM's, but don't really have a desire to do that just yet.

[WIP][Recovery][Root] TWRP 3.0.2-0 Galaxy Note 7 All Exynos Model: N930F/FD/S/L/K

[Kernel] Stock Rootable Kernel Galaxy Note7 N930F/FD/S/L/K Without TWRP (08/20/2016)
TWRP 3.0.2-0 Galaxy Note 7 All Exynos Model Only: N930F/FD/S/L/K
Install TWRP
Consider before flash anything (Knox tripped), all you risk !!!
Stock firmware for full restore:
http://samfirm.net/forums/samsung-galaxy-note7.86/
Click to expand...
Click to collapse
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy Note7 stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below, in order, to allow system modifications without the risk of a boot loop!
DOWNLOAD
Official: http://teamw.in/devices/samsunggalaxynote7exynos.html
Beta: http://forum.xda-developers.com/note-7/development/recovery-official-twrp-galaxy-note-7-t3446047
- Download Odin 3.12.3 & Samsung Android USB Driver for Windows
In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
{
"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"
}
Extract Odin 3.12.3.zip to your computer.
Install Samsung Mobile Phone Drivers for Odin to find your device.
Download a .tar image of TWRP for herolte.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot without touching any other options, then press [Start].
Hold [Volume Up] + [Home] buttons near the end of the flash, and keep holding them until you are in recovery.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 11 you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
Only if you want internal storage or data to work in TWRP:
Go to [Wipe] -> [Format Data] (not advanced wipe) -> type "yes".
WARNING: This will wipe your internal storage, disable encryption, and factory reset your phone!
Go to [Reboot] -> [Recovery].
If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you only want a bootable system partition or writable data in TWRP:
Download dm-verity and force encryption disabler.
Without exiting TWRP, transfer no-verity-opt-encrypt.zip to your device over MTP* and flash it using [Install] in TWRP.
Go to [Reboot] -> [System].
FEATURES
MTP support
USB Mass Storage support
Micro SDcard and USB OTG storage support
f2fs file system support (read, write, format, backup & restore)
exFAT file system support (read, write, format, backup & restore)
NTFS file system support (read, write, format)
ADB root
Full SELinux support
Built in android 6.0 tree
Thank & Credit @jcadduono - S7/S7e TWRP install instructions
Source: @Manh_IT http://choimobile.vn/threads/huong-dan-cai-twrp-galaxy-note-7-all-exynos-model-n930f-s-l-k-w8.67874/
W8 is the Snapdragon variant. Do not flash this on that.
This TWRP could not have been built from OSRC as it hasn't been released yet, so is likely using a stock kernel leak and missing support for ADB, MTP, UMS, F2FS, NTFS etc. (unlike the post copypaste from my threads says )
As is usual of Manh_IT and outside Vietnam forums, the sources are unavailable and you're pretty much on your own flashing this.
Once OSRC is out (August 19th for Snapdragon, anywhere between August 19th and September 2nd for Exynos), then official TWRP will be out soon after with all the other features supported.
PS. Would be nice to know if no-verity-opt-encrypt zip works on this device, it isn't working on the new 7870 devices due to forced encryption in vold (encrypts even when encryption disabled in boot image)
great , good news for new user note7 exynos model
Wow, first recovery for the epic note7!!:good:
Wow thank you
Sent from my SM-N930F using Tapatalk
jcadduono said:
W8 is the Snapdragon variant. Do not flash this on that.
This TWRP could not have been built from OSRC as it hasn't been released yet, so is likely using a stock kernel leak and missing support for ADB, MTP, UMS, F2FS, NTFS etc. (unlike the post copypaste from my threads says )
As is usual of Manh_IT and outside Vietnam forums, the sources are unavailable and you're pretty much on your own flashing this.
Once OSRC is out (August 19th for Snapdragon, anywhere between August 19th and September 2nd for Exynos), then official TWRP will be out soon after with all the other features supported.
PS. Would be nice to know if no-verity-opt-encrypt zip works on this device, it isn't working on the new 7870 devices due to forced encryption in vold (encrypts even when encryption disabled in boot image)
Click to expand...
Click to collapse
Look who's been lurking around the n7 thread.
Nice to see you here man!????
Hopefully later your team will release the official TWRP, for both model exynos and snapdragon.
And also your idleKernel. It's been an amazing kernel for my note3 up until now. Bravo. . .and bravo too OP.
It does not work for me. Flash is ok, but cannot boot into recovery. Stuck at Samsung screen.
Normal boot works.
SM-N930FD
I did a factory reset, now it does not boot at all anymore. Any help please?
I also cannot flash anything in odin anymore.
After initializing, it immidiatly stops with the error:
<ID:0/004> FAIL! (DeviceInfo)
bill340 said:
It does not work for me. Flash is ok, but cannot boot into recovery. Stuck at Samsung screen.
Normal boot works.
SM-N930FD
Click to expand...
Click to collapse
Me too no work stuck at Samsung screen boot
Sent from my SM-N930F using Tapatalk
I cannot go into recovery. Only download mode works. But when trying to flash something in odin, I get this error as mentioned.
Is there any way to get back on the device?
MSH2000FF said:
Me too no work stuck at Samsung screen boot
Sent from my SM-N930F using Tapatalk
Click to expand...
Click to collapse
bill340 said:
I did a factory reset, now it does not boot at all anymore. Any help please?
I also cannot flash anything in odin anymore.
After initializing, it immidiatly stops with the error:
<ID:0/004> FAIL! (DeviceInfo)
Click to expand...
Click to collapse
bill340 said:
It does not work for me. Flash is ok, but cannot boot into recovery. Stuck at Samsung screen.
Normal boot works.
SM-N930FD
Click to expand...
Click to collapse
bill340 said:
I cannot go into recovery. Only download mode works. But when trying to flash something in odin, I get this error as mentioned.
Is there any way to get back on the device?
Click to expand...
Click to collapse
Your devices model and build number ?
Worried to try as it's not working for many above - and still the Stock Firmware TAR is not available to re-flash if something goes wrong.
WolfW said:
Your devices model and build number ?
Click to expand...
Click to collapse
SM-N930F
bill340 said:
SM-N930F
Click to expand...
Click to collapse
Flash N930FXXU1APG7 firmware and try again !
http://samfirm.net/threads/official-rom-full-galaxy-note-7-sm-n930f-n930fxxu1apg7-xxv-23-07-2016.98/
JazonX said:
Worried to try as it's not working for many above - and still the Stock Firmware TAR is not available to re-flash if something goes wrong.
Click to expand...
Click to collapse
If your device model is SM-N930F or N930FD, use this firmware: http://samfirm.net/threads/official-rom-full-galaxy-note-7-sm-n930f-n930fxxu1apg7-xxv-23-07-2016.98/
WolfW said:
If your device model is SM-N930F or N930FD, use this firmware: http://samfirm.net/threads/official-rom-full-galaxy-note-7-sm-n930f-n930fxxu1apg7-xxv-23-07-2016.98/
Click to expand...
Click to collapse
Thanks, Downloading now. Hope you'll rebuild the recovery sans the issues others faced.
I still have the issue, that I cannot flash in Odin, due to the mentioned error... Any idea?
bill340 said:
I still have the issue, that I cannot flash in Odin, due to the mentioned error... Any idea?
Click to expand...
Click to collapse
Take error screenshots on Odin and Download screen on your phone !
Here are the screenshots....
bill340 said:
Here are the screenshots....
Click to expand...
Click to collapse
You should ad tar only to AP and press start. Read the OP very carefully.

[RECOVERY][ROOT]TWRP 3.3.1-1 Samsung Galaxy J3 2017 SM-J330F/J330FN/J330G/DS

Unofficial release -TWRP recovery for the Galaxy J3 2017 - SM-J330F/FN/FZ/G/DS EXYNOS 7570
{
"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.3.1-0 Released
May 22, 2019
TWRP 3.3.1-0 is out now for most currently supported devices.
What's new in 3.3.1-0:
* Fix selinux issues during formatting - dianlujitao
* Various fixes for toybox and toolbox builds - CaptainThrowback and bigbiff
* Flash both A and B partitions when installing a recovery ramdisk - Dees_Troy
* Add option to uninstall TWRP app from /system - Dees_Troy
* Create digest for subpartitions - bigbiff
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
UPDATE 10/8/2019
TWRP 3.3.1-1 OO/PP build released
Current status: Beta
Update 15/9/2018
TWRP 3.2.3-1 OO build released.
Current status: Stable
Update 27/1/2018
TWRP 3.2.1-1NN build released
Current status: Stable
Update 23/11/2017
TWRP 3.1.1-1 NN build released.
Current status: Stable
Features:
TOUCHSCREEN working
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest source
Factory Image flashing(see below)
NTFS support
F2FS support >> To be added
Twrp app support
New feature available in TWRP v3 is system image backup and restore and factory image flashing (see TWRP changelog for details)
Basically this means factory system images from the official firmware can now be flashed with TWRP.
This feature can be found under INSTALL >> INSTALL IMAGE >> select image to flash >> select partition.[/B]
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.
Instructions:
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.
Flash with ODIN in the AP slot.
1. Put your device in DOWNLOAD mode.
2. Uncheck Auto reboot. (NOT REQUIRED FOR INSTALLING TWRP 3.3.1-1)
3. Load the respective file below into the AP slot and hit start.
4. After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME. (NOT REQUIRED FOR INSTALLING TWRP 3.3.1-1, THE DEVICE WILL AUTO BOOT TO RECOVERY)
5. Flash the V3 RMM bypass zip
https://forum.xda-developers.com/showpost.php?p=79745844&postcount=627
NOTE: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT AND BECOMING RMM LOCKED FOR 7 DAYS.
I ALSO SUGGEST BACKING UP ANYTHING YOU NEED ON INTERNAL STORAGE. AT SOME POINT YOU MAY EXPERIENCE A 'VERIFICATION FAILED MESSAGE' .
THIS IS NORMAL, BUT WILL REQUIRE THE DATA PARTITION TO BE FORMATTED IN TWRP.
DOWNLOAD:
twrp_3.3.1-1_sm-j330x_13819
twrp_3.2.3-1_j330_13918
twrp_3.2.1-1_sm-j330f_270117
twrp_3.1.1-1_sm-j330f_231117
Nougat Root instructions:
Install latest Magisk release with TWRP:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable forced encryption, disable dmverity and mount internal storage:
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install the boot image patch.
Boot image patch
no-verity-no-encrypt_ashyx
5. Install Magisk(if root is required)
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
6. Reboot
OREO ONLY ROOT INSTRUCTIONS:
1. Install the Root patch kernel with TWRP.
J330F-FN_root_no_sim_patch
NOTE:This is a custom Oreo J330F/FN XXU3BRG3 permissive/enforcing kernel and patch built from source. It makes changes to the system partition also.
What does it do?:
*It installs a custom kernel to fix the no SIM issue when rooting.
*Patches the system to fix WIFI and Bluetooth not turning on when using custom kernels.
*Patches DM-Verity.
*Removes forced encryption and patches /data not able to be mounted (after formatting).
*Removes the SecurityLogAgent nag when using a custom kernel.
2. If you wish to mount /DATA for access to internal storage then FORMAT the /DATA partition.
3. To root install the latest Magisk below.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
PIE ONLY ROOT INSTRUCTIONS:
To root install latest Magisk below.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
To disable encryption (mount DATA in TWRP) install the zip below with TWRP:
Disable_Dm-Verity_ForceEncrypt_Quota_08.02.2019
Finally FORMAT /DATA in TWRP.
Reboot.
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, my tester @lemlis, Teamwin
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
UPDATE: Touchscreen fixed
.
Arggghh i feel something goes wrong with my device intead of succesfull installation. Yes i can flash zip and make nandroid backup. But my device not running properly. I can't adjust screen brightness even camera not functioning. Now i'm waiting for full batery charge to flash stock rom & try to flash twrp once again
---------- Post added at 22:19 ---------- Previous post was at 22:16 ----------
Anual said:
Arggghh i feel something goes wrong with my device intead of succesfull installation. Yes i can flash zip and make nandroid backup. But my device not running properly. I can't adjust screen brightness even camera not functioning. Now i'm waiting for full batery charge to flash stock rom & try to flash twrp once again
Click to expand...
Click to collapse
Now my j330g working normally after i flash cf auto root without flashing stock rom. What's the problem??
Anual said:
Arggghh i feel something goes wrong with my device intead of succesfull installation. Yes i can flash zip and make nandroid backup. But my device not running properly. I can't adjust screen brightness even camera not functioning. Now i'm waiting for full batery charge to flash stock rom & try to flash twrp once again
---------- Post added at 22:19 ---------- Previous post was at 22:16 ----------
Now my j330g working normally after i flash cf auto root without flashing stock rom. What's the problem??
Click to expand...
Click to collapse
Probably the version of SuperSu you flashed.
ashyx said:
twrp_3.1.1-1_sm-j330f_231117
Click to expand...
Click to collapse
Thanks.now color in TWRP is blue.Only in screenshot yellow.backup CPEFS is 0 ? with changed recovery.fsab i have CPEFS 8MB
Works all good.
lemlis said:
Thanks.now color in TWRP is blue.Only in screenshot yellow.backup CPEFS is 0 ? with changed recovery.fsab i have CPEFS 8MB
Works all good.
View attachment 4340464View attachment 4340476
Click to expand...
Click to collapse
Seems I didn't include my updated FSTAB in the new build. Corrected, thanks for pointing it out.
ashyx said:
Probably the version of SuperSu you flashed.
Click to expand...
Click to collapse
Yeaa you right..i use super su which remain in my memory card almost 2 years ago ???
Sorry for this offtopic but can anyone post a link of latest firmware for J330G/DS, which doesn't want to grab my money for Fast download speed please? I want to try this recovery but still afraid if something bad happens. Thanks in advance!
@ashyx, thank you so much for this recovery sir! I've been waiting for a recovery for this phone for so long and now it's here! you managed to create this recovery for this phone even without one! I'm impressed sir!
BlackDragonz said:
Sorry for this offtopic but can anyone post a link of latest firmware for J330G/DS, which doesn't want to grab my money for Fast download speed please? I want to try this recovery but still afraid if something bad happens. Thanks in advance!
@ashyx, thank you so much for this recovery sir! I've been waiting for a recovery for this phone for so long and now it's here! you managed to create this recovery for this phone even without one! I'm impressed sir!
Click to expand...
Click to collapse
updato.com
i cant flash super su twrp didn't show the file to flash
File to flash have to be on sd card ?
Help Me
azhar960225 said:
Help Me
Click to expand...
Click to collapse
Police. Fire or ambulance?
I Want root j3 pro 2017..but how
azhar960225 said:
I Want root j3 pro 2017..but how
Click to expand...
Click to collapse
Flash SuperSU or Magisk.
How? To Flash How? Cannot root j3 How to Flash?
7.11 Android...
arabarabow said:
twrp didn't show the file to flash
Click to expand...
Click to collapse
put zip file inside any folder.File to flash have to be in folder
Just done flashing latest build and flashed magisk, all are running fine. Tysm @ashyx !
can anyone help me telephone stuck on logo and i cant do nothing even reboot to twrp @ashyx
arabarabow said:
can anyone help me telephone stuck on logo and i cant do nothing even reboot to twrp @ashyx
Click to expand...
Click to collapse
Boot to TWRP and flash Supersu or Magisk. Use the three button combo.
Can i just use cf auto root to root my phone without installing a recovery? Or it's better to root using this method?

[recovery][root]twrp-3.2.x galaxy j2 pro 2018 sm-j250f

Unofficial release -TWRP recovery for the Samsung Galaxy J2 PRO 2018 - Qualcom msm8917
{
"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"
}
THIS FOR FIRMWARE BASED ON "ARD3" OR "ARD*" . SO PLEASE MAKE SURE YOUR FIRMWARE IS "ARD3 OR "ARD*" :
Current status: BETA
Features:
SEANDROID warning fix
TWRP and Kernel built from latest source
system Image backup and flashing support
efs backup support
WHATEVER YOU DO BEFORE FLASHING ANYTHING WITH TWRP MAKE A BACKUP OF YOUR DEVICE WITH TWRP AND HAVE THE STOCK FIRMWARE TO HAND JUST IN CASE DOWNLOADED FROM SAMMOBILE OR UPDATO.
THIS WILL TRIP KNOX AND MAY VOID YOUR WARRANTY!
Instructions:
(Note: failure to follow these instructions implicitly will cause TWRP to be replaced by stock recovery at boot!)
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 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.
Download:
recovery.tar.md5 For J250f
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery.
If you choose to 'Allow' then SuperSU or the boot patch needs flashing below to disable dm-verity.
To Root:
Flash the latest magisk with TWRP:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
This device forces encryption.
To disable forced encryption, mount internal storage(DATA) and disable dm-verity you must flash the boot patcher below:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install magisk (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patcher
no-verity-no-encrypt-5.1
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin, Omnirom, my tester ilmiawan budi utomo @FBGroup
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
Reserved
readme
this for firmware base on "ard3" please make sure your firmware "ard3"
andii_nr said:
readme
this for firmware base on "ard3" please make sure your firmware "ard3"
Click to expand...
Click to collapse
help me please J250FDXU1ARA2
Khang140401 said:
help me please J250FDXU1ARA2
Click to expand...
Click to collapse
First update to ARD3
andii_nr said:
First update to ARD3
Click to expand...
Click to collapse
I updated and flash this with odin but it not work ☹☹ my board msm8937 ? Work? Please reply me.
---------- Post added at 06:10 AM ---------- Previous post was at 06:04 AM ----------
[/PHP]
andii_nr said:
First update to ARD3
Click to expand...
Click to collapse
Khang140401 said:
I updated and flash this with odin but it not work ☹☹ my board msm8937 ? Work? Please reply me.
---------- Post added at 06:10 AM ---------- Previous post was at 06:04 AM ----------
[/PHP]
Click to expand...
Click to collapse
Are you sure your phone sm-j250f and firmware ARD3 ?
If yes that recovery work fine , am also test with 3friend and work ..
andii_nr said:
Are you sure your phone sm-j250f and firmware ARD3 ?
If yes that recovery work fine , am also test with 3friend and work ..
Click to expand...
Click to collapse
see it ??
andii_nr said:
Are you sure your phone sm-j250f and firmware ARD3 ?
If yes that recovery work fine , am also test with 3friend and work ..
Click to expand...
Click to collapse
My devices _J250FDXU2ARD3
problem
team win worked with me but when i want to open my phone it reboot himself and i should install rom
Khang140401 said:
see it ??
Click to expand...
Click to collapse
Read all instruction ..
This phone has deencrypt .. so you must FORMAT DATA -> flash magisk -> flash boot-patcher ..
Costum ROM s8 for j250f
andii_nr said:
Unofficial release -TWRP recovery for the Samsung Galaxy J2 PRO 2018 - Qualcom msm8917
THIS FOR FIRMWARE BASED ON "ARD3" OR "ARD*" . SO PLEASE MAKE SURE YOUR FIRMWARE IS "ARD3 OR "ARD*" :
Current status: BETA
Features:
SEANDROID warning fix
TWRP and Kernel built from latest source
system Image backup and flashing support
efs backup support
WHATEVER YOU DO BEFORE FLASHING ANYTHING WITH TWRP MAKE A BACKUP OF YOUR DEVICE WITH TWRP AND HAVE THE STOCK FIRMWARE TO HAND JUST IN CASE DOWNLOADED FROM SAMMOBILE OR UPDATO.
THIS WILL TRIP KNOX AND MAY VOID YOUR WARRANTY!
Instructions:
(Note: failure to follow these instructions implicitly will cause TWRP to be replaced by stock recovery at boot!)
Flash with ODIN in the AP slot.
Put your device in DOWNLOAD mode.
Uncheck Auto reboot.
Load the respective file below into the AP slot and hit start.
After flashing and ODIN reports PASS immediately reboot to recovery by holding POWER + HOME + VOL DOWN.
As soon as the screen goes blank change to VOL UP whilst still holding POWER + HOME.
You should now see TWRP recovery.
NOTE: ON SOME ANDROID 5.1.1/6.0/7.0 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.
Download:
recovery.tar.md5 For J250f
IMPORTANT! This device enforces dm-verity. ANY modifications or even mounting system will put the device into a bootloop. To prevent this TWRP will ask at first boot if you want to keep system 'Read only' or 'Allow modifications to system'. If you choose to keep 'Read only' you will have to flash TWRP at every boot to recovery.
If you choose to 'Allow' then SuperSU or the boot patch needs flashing below to disable dm-verity.
To Root:
Flash the latest magisk with TWRP:
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
This device forces encryption.
To disable forced encryption, mount internal storage(DATA) and disable dm-verity you must flash the boot patcher below:
(Note this MUST be flashed after SuperSU if you intend to root)
1. Boot to Twrp
2. Format Data partition using FORMAT DATA button under Wipe options.
(Note: This will wipe the internal storage)
3. Check DATA is mountable.
4. Install magisk (if root is required)
5. Install boot image patch below.
6. Reboot
Boot image patcher
no-verity-no-encrypt-5.1
DEVICE TREE: soon
PLEASE DO *NOT* DIRECT LINK TO THESE FILES. PLEASE LINK TO THIS POST
Credits: Me, Teamwin, Omnirom, my tester ilmiawan budi utomo @FBGroup
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
Click to expand...
Click to collapse
Thanks bro for twrp
ARD3 doesn't support current root. Why? Only restart... Phone is not opening.
TWRP => all directory 0 mb. There is a problem.
Thanks for your hard work. The recovery works really fine with our device if instructions were followed carefully.
Now all we need is a custom kernel with selinux set to permissive. I appreciate any help.
Help me
I have a problem with my mobile device that shows me this message when running
"Set warranty bit: kernel"
What is the solution?
i can't use camera when rooted!
pls help me!
timtini said:
i can't use camera when rooted!
pls help me!
Click to expand...
Click to collapse
Latest version of SuperSU or Magisk.
ashyx said:
Latest version of SuperSU or Magisk.
Click to expand...
Click to collapse
of course!
i was try to root with Super SU and Magisk but it still bug!
So I thought of twrp caused!
Nice kang ?

[RECOVERY][UNOFFICIAL]TWRP 3.4.0-0 Touch Recovery [m30lte]

{
"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 is an open-source, community project. A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like LineageOS or OmniROM.
Code:
[SIZE="4"]#include <std_disclaimer.h>
/*
* 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 doing this to your device
* 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.[/SIZE]
Downloads
TWRP - View
ODIN Tool - View
Device tree - View
Installation
Read this before attempting to proceed with this guide.
Make sure you've backed up your personal data and have Samsung USB drivers installed.
Samsung implemented something call RMM Lock since 2017.
@corsicanu and @BlackMesa123 found out about this and gave us insight into what's happening.
This feature is meant as extra security to prevent theft.
As of latest update from Samsung, the RMM is reimplemented as KG Lock, known as KnoxGuard Lock.
However this new implementation made it more friendly and simple for devs.
You will need to update to latest Android 10 firmware with May 2020 security patch
AP Version:M305FDDU5CTF2
CSC VERSION: M305FODM5CTF2
Find the firmware over here https://samfw.com/
After flashing, boot back into Android and go to Developer Options by tapping Build Number under Software Information seven times.
Go into Developer options and enable OEM unlock.
It will ask for PIN/PASSWORD enter and device will reboot and wipe everything, unlocking the bootloader.
After rebooting back into Android you should find that it says "Bootloader already unlocked" under OEM Unlock
Switch off device.
Press Volume+ & Volume- key simultaneously and plug in USB CABLE connected to your computer.
There will be a warning screen. Press Volume+ to continue to Odin Download Mode
Observe the screen, there will be a flag saying "KG STATE: checking..." and "OEM LOCK: OFF"
If this is there for some time that means your bootloader accepts unofficial images. Thanks to @corsicanu for this insight.
Proceed to flash TWRP.
Open up Odin Downloader and uncheck Auto Reboot.
Select downloaded recovery.tar in AP field
Connect device and then click start.
Once done, press Volume- and Power button for 7 seconds to reboot, IMMEDIATELY PRESS VOLUME + AND PWR BUTTON SIMULTANEOUSLY TO BOOT INTO TWRP.
Thanks a lot to @Akhil99 for helping me figure out xD
XDA:DevDB Information
TeamWin Recovery, Tool/Utility for the Samsung Galaxy M30
Contributors
Sahil_Sonar
Akhil99
Version Information
Status: Stable
Current Stable Version: v3.4.0-0
Stable Release Date: 2020-06-27
Created 2019-06-23
Last Updated 2020-06-27
Changelog:
Build 2019-06-23
Updated on latest omni sources
Fix notch cutout overlay
Build 2020-06-27
Synced with latest TWRP sources
Updated kernel image with SM-M305F_SWA_QQ_Opensource
Build 2020-06-29
Fixed MTP
Sync ramdisk with stock Android 10
Join our new Telegram community
[OLD]Video guide: https://www.youtube.com/watch?v=NIUhuEc5WVA&feature=youtu.be
--- blank two ---
Sahil_Sonar said:
Edit: I did flash it via ODIN said "sucess" but still goes to stock recovery will surely fix up!
Edit 2: I am currently testing v1.1 will be up soon! Stay tuned (Yea... those links deleted don't want to keep users trying it because that just doesn't work!)
Click to expand...
Click to collapse
nice, i just bought it, I can test new versions if you want.
maybe we need to apply those "dm-verity" stuff right after flashing recovery for twrp to stick after boot?
thalesbraga said:
nice, i just bought it, I can test new versions if you want.
maybe we need to apply those "dm-verity" stuff right after flashing recovery for twrp to stick after boot?
Click to expand...
Click to collapse
I can help too , i flashed it but still boots to stock recovery and i have the dm verity thingy ,tried installig a zip to bypass it ,didnt work ,let me know if you have any new versions you need to test
You tested that on pie updataed M30 bro
StarkTonyXUV said:
You tested that on pie updataed M30 bro
Click to expand...
Click to collapse
No ,on a 8.1 one , i cant update it because the phone detected that i tried to flash it
???
pankspoo said:
Can some one tell me is it genuine?
http://www.droidthunder.com/root-samsung-galaxy-m30/
Click to expand...
Click to collapse
I am working on it there is no reason of being non geninue :good:
Sahil_Sonar said:
I am working on it there is no reason of being non geninue :good:
Click to expand...
Click to collapse
Genuine means its working or not?
pankspoo said:
Genuine means its working or not?
Click to expand...
Click to collapse
Tried installing TWRP ...unable to boot in to recovery mode
Sahil_Sonar said:
TWRP is an open source, community project. A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom “ROM” like LineageOS or OmniROM.
Note: This recovery is un-tested I cannot assure if works or not. Please proceed at your own. I am not responsible for any damage caused to your device nor xda-developers. If you are unaware how stuffs work please search on google:fingers-crossed:
Downloads
TWRP - View
ODIN Tool - View
Device tree - View(Coming soon! :victory
Installation
Unlock bootloader (Hint: Developer options OEM Unlock :angel: )
Turn off your device and go to download mode, connect via USB to PC(Hint: adb reboot bootloader)
Kick ODIN and flash the recovery
Boot into TWRP and format data (or else face encryption issues)
You are good to go! :laugh:
XDA:DevDB Information
TeamWin Recovery, Tool/Utility for the Samsung Galaxy M30
Contributors
Sahil_Sonar
Version Information
Status: Testing
Current Beta Version: v0.1
Beta Release Date: 2019-05-19
Created 2019-05-19
Last Updated 2019-05-19
Click to expand...
Click to collapse
I dont know how to reply cuz a lot of things are complicated in this site ,but when will it be ready ?
Well it's ready! Download links will be available in a short time!
more147 said:
Tried installing TWRP ...unable to boot in to recovery mode
Click to expand...
Click to collapse
Because RRM Lock is enabled please check op and download latest files! I have sucessfully booted and flashed AOSP GSI on my phone
pankspoo said:
Genuine means its working or not?
Click to expand...
Click to collapse
Yep it is!
Nonneed to type commands to unlock oem.
Like fastboot oem unlock before doing everything. Just enabling oem umlock in developer option works??
pankspoo said:
Nonneed to type commands to unlock oem.
Like fastboot oem unlock before doing everything. Just enabling oem umlock in developer option works??
Click to expand...
Click to collapse
No need Samsung bootloader are easy to unlock just make sure it isn't RMM locked. However it will simply wipe your data so make sure you have a backup
---------- Post added at 09:12 AM ---------- Previous post was at 09:09 AM ----------
[/COLOR]
Sahil_Sonar said:
Well it's ready! Download links will be available in a short time!
Click to expand...
Click to collapse
i tried posting a reply multiple times but couldnt for some reason ...
anyway , i got an md5 error , binary invalid , removed md5. from the file's name , odin says its a success but my phone is stuck on the loading bar under downloading word , note : i have auto reboot disabled and my phoen isnt rmm or frp or locked in any other way and i flashed it using AP
edit :i reseted the file to its original (.tar.md5) and it worked like there was no error (this didnt work when i tried it on other files i had the same problem with ) i enabled force reboot , i couldnt boot to twrp and my phone was working like nothing happend , no verity check , nothing
---------- Post added at 09:30 AM ---------- Previous post was at 09:12 AM ----------
Sahil_Sonar said:
Here's an important note for those you got stock recovery instead of TWRP
--> Make sure auto-reboot is disabled in Odin
--> You will have to reboot into TWRP for the first time after flashing it [/url]
No more thanks :laugh: custom ROM's coming!
Click to expand...
Click to collapse
how do i reboot to twrp if im dtck on stock reboot after flashing ?
Urgent help.
Dm Variety zip is not flashing its showing updater sript error.
Except that everything is ok still i booted in os.
But now my phone showing sim card changed restart u r phone everytime i cant able to use phone
pankspoo said:
Urgent help.
Dm Variety zip is not flashing its showing updater sript error.
Except that everything is ok still i booted in os.
But now my phone showing sim card changed restart u r phone everytime i cant able to use phone
Click to expand...
Click to collapse
So this process of twrp is highly unsafe. Please mention possible solutions in your thread.
When you flash custom binary on your phone(i. E: twrp and root) Samsung automatically trigger it even after flashing RRM bypass file, so it unregister the device thats why sim errors strats evoking after doing this all.
To solve this i flashed stock firmware (how big and slow is that?) ruined whole night and now no sim Error(sim changed restart your phone) this is possibly CSC error. But still my over the air updates not working its showing device is modified.
So please do all this at risk and thread owner please give possible solution to this before giving customs roms or GSI stuff.

Categories

Resources