Unofficial release -TWRP recovery for the Galaxy J3 2017 - SM-J327U 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.1.1-0 Released
May 19, 2017
TWRP 3.1.1-0 is out now for all currently supported devices.
What's new in 3.1.1-0:
Backups will now include adopted storage keys (Dees_Troy)
Fixed an adb restore issue (bigbiff)
Fixed rebooting when no OS is present (Dees_Troy)
Fixed line wrapping in the GUI terminal (_that)
Updated TWRP source code to AOSP 7.1.2 (Dees_Troy)Updated TWRP source code to AOSP 7.1.2
Update 25/11/2017
TWRP 3.1.1-1 NN build released.
Current status: BETA(testing)
Features:
TOUCHSCREEN working
MTP working
ADB working
SEANDROID warning fix
TWRP and Kernel built from latest nougat 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.
IMPORTANT: THIS DEVICE EMPLOYS DM-VERITY. ANY MODIFICATIONS TO THE SYSTEM WILL TRIGGER DM-VERITY CAUSING A BOOT LOOP.
AFTER FLASHING TWRP DM-VERITY WILL NEED TO BE DISABLED BY FLASHING SUPERSU OR MAGISK.
ALTERNATIVELY FOLLOW THE INSTRUCTIONS BELOW TO INSTALL THE BOOT PATCH.
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: FAILURE TO FOLLOW THE STEPS ABOVE IMPLICITLY WILL RESULT IN STOCK RECOVERY REPLACING TWRP AT FIRST BOOT.
NOTE: ON 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:
twrp_3.1.1-1_sm-j327u_271117
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, dm-verity 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, 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
Testing Stage
Please note:
I don't own this device so this is as yet untested. Please report any issues in as much detail as possible. Screenshots always welcome.
0 touchscreen functionality.
I can't get past the Swipe to Unlock screen which means I can't get past step 1 in the overall process xD
CSMNT said:
0 touchscreen functionality.
I can't get past the Swipe to Unlock screen which means I can't get past step 1 in the overall process xD
Click to expand...
Click to collapse
No worries. I had an idea this might be the case as I had the same issue on the J330F and had to fix the issue on that device also.
The 2 devices are fairly similar.
In the meantime an otg mouse should work.
Working perfect on SM-J327U???
Fdraco10 said:
Working perfect on SM-J327U???
Click to expand...
Click to collapse
It will be at some point today after the update to fix the touch screen.
ashyx said:
It will be at some point today after the update to fix the touch screen.
Click to expand...
Click to collapse
Oh ok! Please, I beg You, I need flash my SM-J327U :crying::crying::crying::crying::crying:
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
ashyx said:
It will be at some point today after the update to fix the touch screen.
Click to expand...
Click to collapse
Yeah, please fix it! I need Root my SM-J327U :crying::crying::crying::crying:
Fdraco10 said:
Oh ok! Please, I beg You, I need flash my SM-J327U :crying::crying::crying::crying::crying:
---------- Post added at 06:11 PM ---------- Previous post was at 06:10 PM ----------
Yeah, please fix it! I need Root my SM-J327U :crying::crying::crying::crying:
Click to expand...
Click to collapse
Touchscreen fixed build is up.
ashyx said:
Touchscreen fixed build is up.
Click to expand...
Click to collapse
Really works??
ashyx said:
Touchscreen fixed build is up.
Click to expand...
Click to collapse
Thank you, kind sir! Flashing it now.
Edit:
Touch screen is fixed. Now we have boot loop. Slowly making progress lol.
CSMNT said:
Thank you, kind sir! Flashing it now.
Edit:
Touch screen is fixed. Now we have boot loop. Slowly making progress lol.
Click to expand...
Click to collapse
What do you mean a boot loop? Is that from TWRP or SuperSU?
Please post the recovery log and more details.
ashyx said:
What do you mean a boot loop? Is that from TWRP or SuperSU?
Please post the recovery log and more details.
Click to expand...
Click to collapse
I think that boot loop is for SuperSU! I wanna try flashing the TWRP but I don´t know if I will have bootloop
Fdraco10 said:
I think that boot loop is for SuperSU! I wanna try flashing the TWRP but I don´t know if I will have bootloop
Click to expand...
Click to collapse
You can always flash the stock recovery to recover.
If you get a boot loop I'll post it up.
ashyx said:
You can always flash the stock recovery to recover.
If you get a boot loop I'll post it up.
Click to expand...
Click to collapse
Do you have link for Stock ROM for SM-J327U??
---------- Post added at 06:07 PM ---------- Previous post was at 05:50 PM ----------
@ashyx
Dude, Do you have teh stock recovery for SM-J327U??
Fdraco10 said:
Do you have link for Stock ROM for SM-J327U??
---------- Post added at 06:07 PM ---------- Previous post was at 05:50 PM ----------
@ashyx
Dude, Do you have teh stock recovery for SM-J327U??
Click to expand...
Click to collapse
Of course I'll post it if you need it.
ashyx said:
Of course I'll post it if you need it.
Click to expand...
Click to collapse
Yeah, I need it please, and so thanks!
Fdraco10 said:
Yeah, I need it please, and so thanks!
Click to expand...
Click to collapse
Why do you need it?
You can download it below:
https://desktop.firmware.mobi/device:1795/firmware:13890/download/recovery.tar/landing
ashyx said:
why do you need it?
You can download it below:
https://desktop.firmware.mobi/device:1795/firmware:13890/download/recovery.tar/landing
Click to expand...
Click to collapse
really!!!! So thanks dude!!! Thankkkkssss!!!
ashyx said:
Why do you need it?
You can download it below:
https://desktop.firmware.mobi/device:1795/firmware:13890/download/recovery.tar/landing
Click to expand...
Click to collapse
Just getting back to you now. I think the bootloop is caused by TWRP because I haven't even attempted to flash SuperSU.
My process:
I move SuperSU and the no-verity file over to my internal storage before flashing TWRP in Odin. I flash TWRP. I reboot into recovery. Touch screen works but I can't mount internal storage to flash no-verity or SuperSU. I reboot and instead of being asked to reset it's just a boot loop.
Flashed the stock rom.
CSMNT said:
Just getting back to you now. I think the bootloop is caused by TWRP because I haven't even attempted to flash SuperSU.
My process:
I move SuperSU and the no-verity file over to my internal storage before flashing TWRP in Odin. I flash TWRP. I reboot into recovery. Touch screen works but I can't mount internal storage to flash no-verity or SuperSU. I reboot and instead of being asked to reset it's just a boot loop.
Flashed the stock rom.
Click to expand...
Click to collapse
Yeah, same here bro!
Related
Alright.
I had this problem for a while and I figured out how to flash the update without the need to factory reset or change the update script of the update file.
Even if you get the user/release-keys error message. EXAMPLE:
{
"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"
}
You have to be using the latest lollipop release before updating. That means you have to be on YOG7DAS2K1 before attempting.
This worked out for me. But it might not work for you. I do not believe it can destroy your phone and switch some satellites off, but still, not responsible if it did so.
Requirments:
You have to have TWRP now or you at least have ROOT and any flashing app like flashify.
Download COS 13 update file. here https://www.androidfilehost.com/?fid=24459283995316311
Download the latest CyanogenMod Recovery https://download.cyanogenmod.org/?device=bacon
Download the cm-12.1-YOG7DAS2K1 full ROM [url]https://www.androidfilehost.com/?fid=24369303960686198[/URL]
Guide:
Make sure the update cyanogen recovery option is checked in developer options.
Flash CyanogenMod Recovery downloaded before.
Reboot into it.
Use the update function in CyanogenMod Recovery and choose cm-12.1-YOG7DAS2K1 as the update file. It might take a while.
Now reboot to your phone. When booted and running, reboot to recovery.
Now you are running COS recovery. Update with the incremental.
That is it.
I hope this works out for you.
EXTRA: How to ROOT and have TWRP as a recovery:
Requirements:
A laptop.
Download TWRP and adb drivers on the laptop and the SuperSU and TWRP on your phone
Download Oneplus One TWRP Recovery [url]https://dl.twrp.me/bacon/twrp-3.0.2-0-bacon.img.html[/URL]
Get any adb divers. This one suffice [url]http://forum.xda-developers.com/google-nexus-5/development/adb-fb-apx-driver-universal-naked-t2513339[/URL]
Download the latest SuperSu [url]https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip[/URL]
Guide:
Reboot into bootloader: you can do this in many ways. A simple google search will show you how. Easiest way is to turn the phone off and hold the volume up and power long enough for the phone to boot into bootloader.
Connect your phone to your laptop
Run the adb: I assume you are using windows of course. First put the TWRP .img file in this folder. Hold shift and right click in the folder downloaded above. A 'Open command window here' option will be there. Click it and write in the window
Code:
fastboot boot twrp-3.0.2-0-bacon.img
. A hint: you can just write twrp and hit TAB, it will complete the filename. Or you can rename the downloaded file to just twrp.img
Check your phone, you will be running TWRP temporarily. You now have the option to ROOT only by flashing the SuperSU file downloaded on your phone. If you reboot now you will lose TWRP and get back to the official COS Recovery. If you want TWRP for good flash the TWRP file downloaded on your phone before.
I hope this is easy. It actually is. just follow it step by step.
If you could provide us the guide to root and come back to twrp I would be extremely happy
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
fastboot flash latest twrp and flash SuperSU BETA
THANK the post if I deserve
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
if you need a guide to root, this means you are not rooted, and if you are not rooted most probably you already have stock recovery, which means you can just install the OTA update without any issues.
bisio971 said:
If you could provide us the guide to root and come back to twrp I would be extremely happy
Click to expand...
Click to collapse
Added as requested. I hope you find it easy.
y2kkingboy said:
Added as requested. I hope you find it easy.
Click to expand...
Click to collapse
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
bisio971 said:
Thank you, you made my life easier, but when I tried to run the twrp through fastboot I got an error and I got the solution writing "fastboot boot twrp.img" (after renaming the file).
Click to expand...
Click to collapse
Yeah. I mad a mistake there. Thank you and glad it helped.
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
thinleytsering9 said:
If I do this what happens to my data?? I'm on cm 12. 1.1, rooted & running twrp.
---------- Post added at 12:20 AM ---------- Previous post was at 12:18 AM ----------
Link for cos13 that works with this method?
Click to expand...
Click to collapse
As I stated before you have to be on COS 12.1 YOG7DAS2K1. This method should not format your phone or remove any data as there is no factory reset step.
As for the link they are all over the place now. I used the official one. I'll link it for your convenience.
can anyone please pull the stock recovery from COS 13, not 12. I kinda screwed up while updating and now stuck in bootloop.
Update: The issue is resolved. The issue was because of SuperSu 2.46. Installing the latest TWRP and SuperSu 2.66 fixed it. Marshmallow is now rooted!
Thank you very much! After going back to stock and still not receiving the update for more than a week (well at least it felt like a week, Lol) I decided to flash a full COS 13 zip floating around. Instantly liked the new ROM but it had root/symlink issues only to be resolved when flashing a custom kernel it seems. Not what I really wanted so then I stumbled onto your thread and this technique worked 100%! I was on DAS2K1 (flashed thru a custom recovery) already and had several failed attempts flashing just the incremental outright (thru stock recovery)., but by flashing DAS2K1 thru stock recovery first as you suggest then the incremental seems to do the trick.
I did it all the steps, but my phone doesn't not start. After optimizing aplications I have bootloop at "cyanogen modready".
L.E. I think the problem was one of old aplications. After a clean install everything works.
This is the best thing Oneplus one i ever experience.COS13 give my Oneplus one a new breathe of life .This update better than crap lolipop.No Bug for me until now,only google play service need to update twice in play store,its auto reboot itself twice and wholla,super speed UX.The best thing i ever have.I apply update from CM-12-0-YNG1TAS17L Build LRX22G using this method and it works flawlessly
I don't need to factory reset or wipe cache .
I flash full stock ROM cm-12.1-YOG7DAS2K1 and apply update through CyanogenMod Recovery only and nothing else.
Now my oneplus one is rooted and TWRP install using ADB and its fly.All rooted apps is working together with Adaway.
Thanks Cyanogen team for make this 2 years old flagship killer a beast .
Only thing not satisfied is gone signal and wifi status (connectivity indicator ).I need to swipe down to see my transfer data working (what a bummer ).
Thanks so much for this magical guide (y2kkingboy) Yours truly Oneplus one diehard fan.
I was already on cm-12.1-YOG7DAS2K1, however rooted. So even if I had been offered the OTA it would have failed.
Your guide got me updated, first time with no problems.
6.0.1 is such an improvement on 5.1.1, I tried a couple of other 6.0 roms, however this has by far been the most stable and bug free.
Cheers for the tutorial!
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
#sychrome# said:
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
InsaneNutter said:
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2522762
u can also add a trick i saw online i.e to remove lines of code from assets to - in updater file
Click to expand...
Click to collapse
Can you provide more info? i've always had trouble updating when rooted.
Click to expand...
Click to collapse
I had tried this before and it did not work for me. Kept getting an error saying "the signature file was not a complete file" and therefore it didn't flash. But it may have been editing error on my part. This method works just fine and no need to give up your data either.
Having tried many other ways, I got it done with this instruction.
Thank you!
marxu said:
Having tried many other ways, I got it done with this instruction.
Thank you!
Click to expand...
Click to collapse
Glad I helped.
{
"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"
}
Code:
OpenKirin presents unofficial TWRP for stock EMUI 5.x on Huawei P10.
Intended for usage on stock emui 5.x in combination with unlocked bootloader and
modded boot image with disabled dm-verity (depending on what you want to do).
Instructions
Code:
1. Enter fastboot mode on unlocked device
2. flash recovery using the following command: fastboot flash recovery twrp-3.1.1-0-vtr.img
3. reboot to recovery!
Bugs
Code:
1. /data does not work at the moment. Finding the right decryption method takes some time
because we have no device in front of us - [COLOR="red"][B]please exlude it from any backup for now[/B][/COLOR].
[COLOR="red"](If anyone is interested in helping us with testing - pm me!)[/COLOR]
Downloads
Code:
[LIST]
[URL="https://mega.nz/#!q55G2DTY!BfLGiilvnrkHBv9Je0-Ng9JSrgpE2fSD4k1reZBGDjQ"][U]download twrp-3.1.1-0-vtr.img[/U][/URL]
[/LIST]
FAQ
Code:
Q: What's the code status?
A: 02. July 2017
Q: which P10 models are supported?
A: every model should be supported.
Q: ETAs?
A: No.
Special Thanks
Code:
* [URL="https://forum.xda-developers.com/member.php?u=2335078"]surdu_petru[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=7354786"]XePeleato[/URL]
* [URL="https://forum.xda-developers.com/member.php?u=220328"]paulobrien[/URL]
XDA:DevDB Information
TWRP, Tool/Utility for the Huawei P10
Contributors
OldDroid, surdu_petru, XePeleato
Version Information
Status: Beta
Created 2017-04-11
Last Updated 2017-07-13
OldDroid said:
Hello P10 Users,
since we already created TWRP for the entire Kirin 950 Line-up, we are now looking forward to do the same on Kirin 960 platform, means P10.
Anyone who is interested in testing TWRP for P10 contact me via PM.
Regards, OldDroid - Team OpenKirin
Click to expand...
Click to collapse
I'm ready! (My model VTR-L29) I already killed my eRecovery and Recovery with an attempt to flash the twrp from Mate 9))) Then I flashed through adb the stock Recovery from VTR-L09
Sorry for my English)
Stock recovery and erecovery from VTR-L09C33B123 https://yadi.sk/d/s7aZkial3GgdFT
first really working version, only refinements left, release tomorrow.
EDIT: release delayed, data partition is unusable due to the new file based encryption huawei applies via its software. More to follow soon (i won't release an unstable version of twrp which would cause issues to users and i hope you understand this!)
Huge thanks to my tester @crucky, he was able to provide anything i needed!
Regards
need firmware vtr09 b113. p10 is not booting anymore since tried flashing supersu via twrp. restore doesnt work. does anybody have a idea where to get it?
kurvenmeister said:
need firmware vtr09 b113. p10 is not booting anymore since tried flashing supersu via twrp. restore doesnt work. does anybody have a idea where to get it?
Click to expand...
Click to collapse
I have the same problem.
Full firmware: VTR-L09C33B123.zip https://yadi.sk/d/8EQJP41R3Ggahk
I restore my Phone: Flash across adb stock recovery https://yadi.sk/d/MVQb3Bfz3Gk4go
Command for adb "fastboot flash recovery recovery.img"
Reboot recovery Format and restor
VTR-L09C432B113
update.hicloud.com:8180/TDS/data/files/p3/s15/G1473/g104/v78079/f1/full/update.zip
@crucky
how to flash? fastboot?
---------- Post added at 08:16 PM ---------- Previous post was at 08:12 PM ----------
[/COLOR @crucky
is your advice an IP Adress or downloadlink?
@cemaWork
thx a lot recovery restore worked
the only thing i need is the european version of the original huawei os VTR-L09C432B113
recovery is booting. system does not really want to boot. after selecting the language an wifi the phone reeboots again. flashing the original os might help, at least this was always the final solution at my previous samsung phones and tablets
@crucky
your link is not tapable. would you mind posting this again? thx
---------- Post added at 11:52 PM ---------- Previous post was at 11:47 PM ----------
[/COLOR @crucky
tried your link again and it seems to work. just downloading a 2gb file as zip. flashable with fastboot?
---------- Post added 8th April 2017 at 12:13 AM ---------- Previous post was 7th April 2017 at 11:52 PM ----------
@ crucky
need a small tutorial for your update. thank you for the file.
https://forum.xda-developers.com/p9/development/stock-emui-rom-c432b181-huawei-p9-t3543203
Is this way working at p10 too?
Stock Recovery and erecovery VTR-L09C423B113
https://yadi.sk/d/Mx4IOSTf3GmVKX
extracted the update zip and found no way to put the update.app an my 32 gig external sd card. my windows computer tells me all the time "not enough space" anybody an idea?
@cemaWork
thank you for the link. installed stock recovery but it didnt work. device is not booting anymore.
kurvenmeister said:
@cemaWork
thank you for the link. installed stock recovery but it didnt work. device is not booting anymore.
Click to expand...
Click to collapse
installed stock recovery and wipe / restor?
@ cemawork
you gave me a link for Stock Recovery and erecovery VTR-L09C423B113
do you have another one for vtr-l09c432b113?
kurvenmeister said:
@ cemawork
you gave me a link for Stock Recovery and erecovery VTR-L09C423B113
do you have another one for vtr-l09c432b113?
Click to expand...
Click to collapse
I think that is just a misspell, there is no C423.
Sent from my HUAWEI LON-L29 using XDA Labs
ok, thx
Mostar088 said:
I think that is just a misspell, there is no C423.
Sent from my HUAWEI LON-L29 using XDA Labs
Click to expand...
Click to collapse
Recovery_VTR-L09C432B113 https://yadi.sk/d/-npsnnvx3Gnxan
to all android cracks
i tried three different computers to extract the update.app from the update.zip and failed. is anybody of you so kind to give me a downloadlink for the update.app only. vtr-l09c432b113
thx in advance
kurvenmeister
problem solved.
funkyhuawei is the adress to know for restoring p10 device. signed in, payed a few dollars an got the file directly via erecovery. simple and clear instructions
thx to all who tried to help me. the only thing we need is a root file and xposed
Can someone PM me a link to the TWRP which boots on P10, even if it's unfinished or doesn't mount the data partition? I need to test some things.
Does anyone have magisk installed on Mate 8?
Didn't work for me. Phone rebooted but it wasn't installed/flashed.
Here is the same problem
https://github.com/topjohnwu/Magisk/issues/143
That sucks.
Same here.
You need b580+ and also TWRP built with b580+ (and that's not yet available).
Jake2kOne said:
Didn't work for me. Phone rebooted but it wasn't installed/flashed.
Here is the same problem
https://github.com/topjohnwu/Magisk/issues/143
Click to expand...
Click to collapse
cline2 said:
That sucks.
Click to expand...
Click to collapse
ScouserCL said:
Same here.
Click to expand...
Click to collapse
Boosik said:
You need b580+ and also TWRP built with b580+ (and that's not yet available).
Click to expand...
Click to collapse
I made a TWRP for the B581, but I think, in the case where it works for B581, it should work on the B580. The both has been released in the same moment.
My problem, I've the B560. When I test it, I can't boot into this TWRP, it blocks at "Your device is booting now". I think it could be due to the loop support which isn't integrated in the B560. So I come back on the version 3.1.0-2, no risk to test it. If you installed the TWRP 3.1.0-2, you could come back on this one in the case where mine won't work. I made it yesterday night.
So if you want to test it, it's here.
B.R
franzyroy said:
I made a TWRP for the B581, but I think, in the case where it works for B581, it should work on the B580. The both has been released in the same moment.
My problem, I've the B560. When I test it, I can't boot into this TWRP, it blocks at "Your device is booting now". I think it could be due to the loop support which isn't integrated in the B560. So I come back on the version 3.1.0-2, no risk to test it. If you installed the TWRP 3.1.0-2, you could come back on this one in the case where mine won't work. I made it yesterday night.
So if you want to test it, it's here.
B.R
Click to expand...
Click to collapse
I'll try it.
Previously tried on B520 and B580 with the same results, a random reboot.
Tried to install SuperSU via TWRP, same thing, reboot.
The only root method that worked for me was this: https://forum.xda-developers.com/mate-8/general/guide-root-nougat-mate-8-phh-superuser-t3570898
Maybe that "noverify" thing has something to do?
Actually using TWRP 3.1.0-0 and B580 firmware.
ScouserCL said:
I'll try it.
Previously tried on B520 and B580 with the same results, a random reboot.
Tried to install SuperSU via TWRP, same thing, reboot.
The only root method that worked for me was this: https://forum.xda-developers.com/mate-8/general/guide-root-nougat-mate-8-phh-superuser-t3570898
Maybe that "noverify" thing has something to do?
Actually using TWRP 3.1.0-0
Click to expand...
Click to collapse
Thanks for this next test!
franzyroy said:
Thanks for this next test!
Click to expand...
Click to collapse
Didn't worked, my phone got stuck on "Your device is booting now", and can't enter to recovery...
ScouserCL said:
Didn't worked, my phone got stuck on "Your device is booting now"...
Click to expand...
Click to collapse
OK. Thanks for report. I certainly made an error. I remove it.
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
You can flash the good TWRP in order to fix this issue. Via fastboot.
franzyroy said:
OK. Thanks for report. I certainly made an error. I remove it.
---------- Post added at 08:41 PM ---------- Previous post was at 08:40 PM ----------
You can flash the good TWRP in order to fix this issue. Via fastboot.
Click to expand...
Click to collapse
Thank you for the effort :good:
Yep, already flashed back TWRP 3.1.0-0 :good:
ScouserCL said:
Thank you for the effort :good:
Yep, already flashed back TWRP 3.1.0-0 :good:
Click to expand...
Click to collapse
Fine!
ScouserCL said:
Didn't worked, my phone got stuck on "Your device is booting now", and can't enter to recovery...
Click to expand...
Click to collapse
I fixed the issue, this one works fine, I tested on my firmware B560. It has the same modifications than here.
Link:
TWRP 3.1.0-3
Changes:
Code:
TWRP 3.1.0-3
* kernel updated for proper loop support
* magisk should now be installed and is supported by every rom running b580+ kernel
* native_package.xml has been changed to device specific version
B.R
is there any TWRP Version that is full working for EMUI 4.0 avaible?
harryhase said:
is there any TWRP Version that is full working for EMUI 4.0 avaible?
Click to expand...
Click to collapse
Here!
franzyroy said:
I fixed the issue, this one works fine, I tested on my firmware B560. It has the same modifications than here.
Link:
TWRP 3.1.0-3
Changes:
Code:
TWRP 3.1.0-3
* kernel updated for proper loop support
* magisk should now be installed and is supported by every rom running b580+ kernel
* native_package.xml has been changed to device specific version
B.R
Click to expand...
Click to collapse
Flashed it, flashed magisk perfectly but now I'm stuck on a bootloop
EDIT: Flashed my stock boot.img and reflashed phh's Superuser, and now my phone is back to life!
You recovery works perfect, somehow it manages to install Magisk without rebooting, but when it finishes it gets my phone stuck on a bootloop.
ScouserCL said:
I fixed the issue, this one works fine, I tested on my firmware B560. It has the same modifications than here.
Link:
TWRP 3.1.0-3
Changes:
Flashed it, flashed magisk perfectly but now I'm stuck on a bootloop
EDIT: Flashed my stock boot.img and reflashed phh's Superuser, and now my phone is back to life!
You recovery works perfect, somehow it manages to install Magisk without rebooting, but when it finishes it gets my phone stuck on a bootloop.
Click to expand...
Click to collapse
If you still have the issue, flash again the boot. It should fix the problem but you will have to root again and maybe with another method to avoid to have the same issue.
ScouserCL said:
EDIT: Flashed my stock boot.img and reflashed phh's Superuser, and now my phone is back to life!
You recovery works perfect, somehow it manages to install Magisk without rebooting, but when it finishes it gets my phone stuck on a bootloop.
Click to expand...
Click to collapse
I didn't see your EDIT!
Already fine that you solved it. Maybe an issue with Magisk. To see if it works with the Mate 8... I don't know!
You may be interested in my success of installing Magisk!
Everything works, except phone security. I'm unable to set pin/password/fingerprint (it looks like it is caused by incompatibility of some b560 .img with b581 boot.img - I only flashed boot.img and system.img from b581, but in the update.app, there are many other images, maybe anybody can further test this and flash all/more of those?).
Flashed b581 boot.img (extracted from update.app)
Flashed b581 system.img
Flashed recovery from @franzyroy
Flashed magisk 12.0
Now you have to wait about 5 minutes on the screen with "Your device is booting" message
Done
!!!! Before flashing, remove your phone security (pin/fingerprint/password/gesture) or you will not be able to unlock your phone. !!!!
{
"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"
}
Boosik said:
You may be interested in my success of installing Magisk!
Everything works, except phone security. I'm unable to set pin/password/fingerprint.
Flashed b581 boot.img (extracted from update.app)
Flashed b581 system.img
Flashed recovery from @franzyroy
Flashed magisk 12.0
Now you hqve to wait about 5 minutes in the screen with "Your device is booting" message
Done
!!!! Before flashing, remove your phone security (pin/fingerprint/password/gesture) or you will not be able to unlock your phone. !!!!
Click to expand...
Click to collapse
Great new!
You were with B581 system before?
Did you make any wipes?
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?
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 ?