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?
Related
UPDATE 12/3/2016 - All builds now posted in developer forum: http://forum.xda-developers.com/tab-s2/development/recovery-twrp-2-8-7-x-lollipop-5-1-1-t3205686
UPDATE 6/3/2016 - New version of TWRP has been released v3.0.0-0. See below:
https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html
I have updated versions SM-T810 with a new build. TWRP is now v3.0.0-1
NOTE: This is a test build, I do not own this device. I need someone who knows what they are doing to test this out and report back.. A lot has changed in this version.
Features:
System image backup/restore
Factory image flashing.
F2FS support.
Supersu root option removed which would cause a bootloop on 5.1.1 and 6.0 devices.
MTP fix - MTP now finally working in recovery.
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)
I 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.
(Note: to flash the modem it is necessary to rename MODEM.bin to MODEM.bin.img first)
TWRP-3.0.0-1-T810
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
.
Nice, are you planing on releasing TWRP 3 for T710? Would rly like to have Mount working.
mk89pwnz said:
Nice, are you planing on releasing TWRP 3 for T710? Would rly like to have Mount working.
Click to expand...
Click to collapse
I will, but nobody has confirmed if the t810 version is working yet. Looks like nobody wants the update.
ashyx said:
I will, but nobody has confirmed if the t810 version is working yet. Looks like nobody wants the update.
Click to expand...
Click to collapse
Not many active 810 users. Do u have 710 yourself? or non of these devices?
mk89pwnz said:
Not many active 810 users. Do u have 710 yourself? or non of these devices?
Click to expand...
Click to collapse
I build for loads of devices I don't own. I don't have the S2.
If you are willing to test I can make a T710 build.
As for the amount of T810 owners, there has been 55 downloads since posting this the other day and NOT ONE has bothered to provide feedback. :thumbdown:
ashyx said:
I build for loads of devices I don't own. I don't have the S2.
If you are willing to test I can make a T710 build.
As for the amount of T810 owners, there has been 55 downloads since posting this the other day and NOT ONE has bothered to provide feedback. :thumbdown:
Click to expand...
Click to collapse
I would definetly test it
Just tested it, tablet isn't booting anymore, it stucks on the samsung logo.
Neither in TWRP nor in system.
Reflashed your TWRP 2.8.7.1 and everything works again.
westernmg said:
Just tested it, tablet isn't booting anymore, it stucks on the samsung logo.
Neither in TWRP nor in system.
Reflashed your TWRP 2.8.7.1 and everything works again.
Click to expand...
Click to collapse
Can I ask which firmware build you are running? This build is using the latest kernel source BOJ1 which is a revision 2 firmware and may not be compatible with revision 1 bootloaders.
westernmg said:
Just tested it, tablet isn't booting anymore, it stucks on the samsung logo.
Neither in TWRP nor in system.
Reflashed your TWRP 2.8.7.1 and everything works again.
Click to expand...
Click to collapse
Can I ask which firmware build you are running? This build is using the latest kernel source BOJ1 which is a revision 2 firmware and may not be compatible with revision 1 bootloaders.
Please test this, it is built with the 5.1.1 kernel from the previous version: twrp_3.0.0-0_test2_t810
.
ashyx said:
I will, but nobody has confirmed if the t810 version is working yet. Looks like nobody wants the update.
Click to expand...
Click to collapse
??? http://forum.xda-developers.com/showpost.php?p=65197803&postcount=72
workdowg said:
??? http://forum.xda-developers.com/showpost.php?p=65197803&postcount=72
Click to expand...
Click to collapse
I changed a lot with this version, the build configuration itself is very different, kernel is built from latest source, modifications to the TWRP source code, mtp fix and hopefully even ADB working.
ashyx said:
I changed a lot with this version, the build configuration itself is very different, kernel is built from latest source, modifications to the TWRP source code, mtp fix and hopefully even ADB working.
Click to expand...
Click to collapse
Doesn't boot..
workdowg said:
Doesn't boot..
Click to expand...
Click to collapse
That's the test 2 version?
ashyx said:
That's the test 2 version?
Click to expand...
Click to collapse
The one from the OP is the only one I see....
workdowg said:
The one from the OP is the only one I see....
Click to expand...
Click to collapse
Post nr. 9
Flashing both from TWRP (using the image) and from Odin doesn't work, after restarting the recovery gets locked and unable to boot, as others wrote flashing the other TWRP from post 9 in your main TWRP thread works perfectly as far as booting, I did a couple of backups and worked fine, didn't restore the backups, so I can't tell you if restoring is fine.
Thanks for your efforts, I really appreciate them. :good:
kekinash said:
Flashing both from TWRP (using the image) and from Odin doesn't work, after restarting the recovery gets locked and unable to boot, as others wrote flashing the other TWRP from post 9 in your main TWRP thread works perfectly as far as booting, I did a couple of backups and worked fine, didn't restore the backups, so I can't tell you if restoring is fine.
Thanks for your efforts, I really appreciate them. :good:
Click to expand...
Click to collapse
Thanks, but you're confusing me, which version works? You say post #9, but that is this thread. :what:
I'm on LMY47X.T810XXU2BOJ1, the test2 is working so far.
But MTP doesn't seem to work for me.
On reboot to system it says "no OS installed ,are you sure to reboot?" but it boots fine....
ashyx said:
Can I ask which firmware build you are running? This build is using the latest kernel source BOJ1 which is a revision 2 firmware and may not be compatible with revision 1 bootloaders.
Please test this, it is built with the 5.1.1 kernel from the previous version: twrp_3.0.0-0_test2_t810
.
Click to expand...
Click to collapse
westernmg said:
I'm on LMY47X.T810XXU2BOJ1, the test2 is working so far.
But MTP doesn't seem to work for me.
On reboot to system it says "no OS installed ,are you sure to reboot?" but it boots fine....
Click to expand...
Click to collapse
It seems an issue with the kernel preventing boot to recovery with the earlier version. Not sure about the 'No OS installed' message, how can that be unless you wiped it?
Regarding MTP what actually happens?
Can you post the recovery.log on pastebin.com?
OK, it looks like TWRP is not able to mount anything.
The recovery.log cannot be written, also there is no access to the internal storage while trying to flash a zip or to restore a backup.
Got it on USB
ashyx said:
It seems an issue with the kernel preventing boot to recovery with the earlier version. Not sure about the 'No OS installed' message, how can that be unless you wiped it?
Regarding MTP what actually happens?
Can you post the recovery.log on pastebin.com?
Click to expand...
Click to collapse
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.
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!
{
"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"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. It's a full touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Downloads:
GitHub Releases
Instructions:
- Download recovery
- Boot into recovery using fastboot boot command
- Do what you want
Bugs:
- Can't be installed permanently
- Data restore has issues
- You tell me
XDA:DevDB Information
TWRP 3.3.1 Touch Recovery, Tool/Utility for the Nokia 6
Contributors
TheImpulson
Source Code: https://github.com/omnirom/android_bootable_recovery/
Version Information
Status: Stable
Current Stable Version: 3.3.1
Stable Release Date: 2019-07-01
Created 2018-08-06
Last Updated 2019-10-13
If you encounter any issue, kindly tell me so that I can fix. As on TA-1089 model that I hold, everything seems to be working.
Edit: Everything seems to be working as far now.
Reserved
Reserved
I don't mean to compare, but How is this different than Maher unofficial TWRP? Does it need to be updated after ever security update? I have the TA-1045 version of the Nokia 6.1 on the July update.
Danny1976 said:
I don't mean to compare, but How is this different than Maher unofficial TWRP? Does it need to be updated after ever security update? I have the TA-1045 version of the Nokia 6.1 on the July update.
Click to expand...
Click to collapse
For differences, You can always check my source which are linked in the 1st post. Nope, TWRP doesn't depends on device security patches.
can someone have a guide to flash the recovery?i cant flash it... at fastboot phone stuck and pc wait for device. thanks
Did not work on TA-1043, phone was stuck on Nokia logo
chriskleov said:
can someone have a guide to flash the recovery?i cant flash it... at fastboot phone stuck and pc wait for device. thanks
Click to expand...
Click to collapse
Solannae said:
Did not work on TA-1043, phone was stuck on Nokia logo
Click to expand...
Click to collapse
Alright, I will check. Thanks for testing.
Solannae said:
Did not work on TA-1043, phone was stuck on Nokia logo
Click to expand...
Click to collapse
Confirm, same here.
Also TWRP can't access external card.
chriskleov said:
can someone have a guide to flash the recovery?i cant flash it... at fastboot phone stuck and pc wait for device. thanks
Click to expand...
Click to collapse
Check your driver on pc install nokia driver or if already installed try to uninstall and reinstall the driver again
TheImpulson said:
If you encounter any issue, kindly tell me so that I can fix. As on TA-1089 model that I hold, everything seems to be working.
Edit: Everything seems to be working as far now.
Click to expand...
Click to collapse
I am trying to use the command "fastboot boot twrp-3.2.2-0-PL2.img" to boot into TWRP and not flash it. When I do that command it just boots completely into the system. Why is it not booting to TWRP?
Danny1976 said:
I am trying to use the command "fastboot boot twrp-3.2.2-0-PL2.img" to boot into TWRP and not flash it. When I do that command it just boots completely into the system. Why is it not booting to TWRP?
Click to expand...
Click to collapse
It is because initramfs is set to ignore by default on boot. I can change it unless I get kernel source.
TheImpulson said:
It is because initramfs is set to ignore by default on boot. I can change it unless I get kernel source.
Click to expand...
Click to collapse
As of right now.... There is no way of rooting the device without TWRP to flash Magisk? Once I flash TWRP I will loose stock recovery and will not get OTA.
I have restored stock boot and Unroot, but cannot install the August OTA.
Danny1976 said:
As of right now.... There is no way of rooting the device without TWRP to flash Magisk? Once I flash TWRP I will loose stock recovery and will not get OTA.
I have restored stock boot and Unroot, but cannot install the August OTA.
Click to expand...
Click to collapse
Locked bootloader?
TheImpulson said:
Locked bootloader?
Click to expand...
Click to collapse
unlocked
Danny1976 said:
As of right now.... There is no way of rooting the device without TWRP to flash Magisk? Once I flash TWRP I will loose stock recovery and will not get OTA.
I have restored stock boot and Unroot, but cannot install the August OTA.
Click to expand...
Click to collapse
Do you have the stock boot image so i can restore stock boot????? That would actually save my ass if you could hit me up with that.
toonmaster74 said:
Do you have the stock boot image so i can restore stock boot????? That would actually save my ass if you could hit me up with that.
Click to expand...
Click to collapse
Stock boot for June or July? Is it the Nokia 6.1 TA-1045?
Danny1976 said:
Stock boot for June or July? Is it the Nokia 6.1 TA-1045?
Click to expand...
Click to collapse
June if you have it! If you have July as well that would be literally amazing!!!!
toonmaster74 said:
June if you have it! If you have July as well that would be literally amazing!!!!
Click to expand...
Click to collapse
I got them from someone else to get back to stock and it works.
July Stock Boot
https://mega.nz/#!Zh1FHArI!35BD1uGbjzdKAD_QvimK102XVRFm9yyjiYeDst-5UGA
June Stock Boot
https://mega.nz/#!8t0XBSbL!-A5Lmzms5pGNtH-1AzoI4etmekEQNa78okneOricFRQ
When I go to about phone in my settings then update, I get a message that says IN2025_11.C.11 is ready to be downloaded and installed. When I click download and install it fills up the bar about 10% then crashes and says it was unable to be installed. Anyone have any advice or the update I can download to take care of it locally?
{
"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"
}
I installed it on mine today. So far so good, but I haven't been using it a bunch.
mkennedy455 said:
I installed it on mine today. So far so good, but I haven't been using it a bunch.
Click to expand...
Click to collapse
Did yours update normally? Did you have to local upgrade?
I just did the ota through system update in settings.. I read on here that there was an update so I manually checked and it showed up so installed it and it worked I was on open beta 1 Android 12 not rooted used incremental update. I used oxygen updater to install the beta I was on before. I'm a little confused because I thought I had to factory reset to go back to stable builds. Is this actually a stable build now or is it still a beta?
mkennedy455 said:
I just did the ota through system update in settings.. I read on here that there was an update so I manually checked and it showed up so installed it and it worked I was on open beta 1 Android 12 not rooted used incremental update. I used oxygen updater to install the beta I was on before. I'm a little confused because I thought I had to factory reset to go back to stable builds. Is this actually a stable build now or is it still a beta? View attachment 5565839
Click to expand...
Click to collapse
As far as I know its a stable but its only being rolled out to the beta users at the moment. I could be wrong
mkennedy455 said:
I just did the ota through system update in settings.. I read on here that there was an update so I manually checked and it showed up so installed it and it worked I was on open beta 1 Android 12 not rooted used incremental update. I used oxygen updater to install the beta I was on before. I'm a little confused because I thought I had to factory reset to go back to stable builds. Is this actually a stable build now or is it still a beta? View attachment 5565839
Click to expand...
Click to collapse
Idk why mine wont let me update through updates even tho it shows it there
it simply because you're rooted.. it's already known from a long time.
there're 2 way if you wanna update from OTA:
1. simple uninstall magisk, and restore image. then do update. then back install magisk again
2. localupdate again C.10 and because you're now lose root, then you should be able to update fine
dewa5227 said:
it simply because you're rooted.. it's already known from a long time.
there're 2 way if you wanna update from OTA:
1. simple uninstall magisk, and restore image. then do update. then back install magisk again
2. localupdate again C.10 and because you're now lose root, then you should be able to update fine
Click to expand...
Click to collapse
Oh alright. How would I install magisk again since I wont be able to patch ota?
dewa5227 said:
it simply because you're rooted.. it's already known from a long time.
there're 2 way if you wanna update from OTA:
1. simple uninstall magisk, and restore image. then do update. then back install magisk again
2. localupdate again C.10 and because you're now lose root, then you should be able to update fine
Click to expand...
Click to collapse
Did what you said, it updated. Rebooted. Then after a reboot again my phone only boots into recovery now....
H411UCIN093NIC said:
Did what you said, it updated. Rebooted. Then after a reboot again my phone only boots into recovery now....
Click to expand...
Click to collapse
what step that you actually do ?
If you like to do an OTA;
Go to Magisk, uninstall Magisk - restore Image
Download and Install the OTA but DONT reboot
Go to Magisk, install magisk to inactive slot after ota
Reboot
xtcislove said:
If you like to do an OTA;
Go to Magisk, uninstall Magisk - restore Image
Download and Install the OTA but DONT reboot
Go to Magisk, install magisk to inactive slot after ota
Reboot
Click to expand...
Click to collapse
Thank you
H411UCIN093NIC said:
Did what you said, it updated. Rebooted. Then after a reboot again my phone only boots into recovery now....
Click to expand...
Click to collapse
Try to change slot via fastboot
xtcislove said:
Try to change slot via fastboot
Click to expand...
Click to collapse
Yea I tried that. I had to use msm tool loose all data then start from scratch apply all updates then I was able to do what you said and it worked. I'm on the latest A12 with root but unfortunately I lost all data in the meantime.
Installing magisk in an inactive slot will result in a softbrick.
Maruli said:
Installing magisk in an inactive slot will result in a softbrick.
Click to expand...
Click to collapse
So lets say I am on the latest Android 11 stable build and I want to flash the C11 stable Android 12 build (full zip, not incremental) and keep root and data. Is there a way to do that?
Previously as others have said, we restore images in Magisk. Install the OTA, then direct install Magisk, then to inactive slot, reboot, and all is well. Does this no longer work? Can someone please give a full explanation of their understanding?
xgerryx said:
So lets say I am on the latest Android 11 stable build and I want to flash the C11 stable Android 12 build (full zip, not incremental) and keep root and data. Is there a way to do that?
Previously as others have said, we restore images in Magisk. Install the OTA, then direct install Magisk, then to inactive slot, reboot, and all is well. Does this no longer work? Can someone please give a full explanation of their understanding?
Click to expand...
Click to collapse
Do you have the IN2021 version? Because NA/global doesn't have a full ROM yet. I can only confirm what the guy above me has experienced - installing magisk (v24.3) into the updated slot will result in a softbrick. Without that step it's working fine (I managed to switch slots in fastboot and redo the update from previous slot again).
It seems like the boot.img from the IN2021 C11 ROM does work with the IN2025 software, since I couldn't extract the incremental OTA and patch the boot.img. That actually saved my phone and I almost used MSM tool.
Maybe it's different if you update from A11 to A12 - I updated from OB1 C10 to C11 and magisk messes something up in the process.
Maruli said:
Do you have the IN2021 version? Because NA/global doesn't have a full ROM yet. I can only confirm what the guy above me has experienced - installing magisk (v24.3) into the updated slot will result in a softbrick. Without that step it's working fine (I managed to switch slots in fastboot and redo the update from previous slot again).
It seems like the boot.img from the IN2021 C11 ROM does work with the IN2025 software, since I couldn't extract the incremental OTA and patch the boot.img. That actually saved my phone and I almost used MSM tool.
Maybe it's different if you update from A11 to A12 - I updated from OB1 C10 to C11 and magisk messes something up in the process.
Click to expand...
Click to collapse
Thanks, that helps a lot. I think I'm going to wait until the dust settles because I need my phone available for work. I can't be stuck in a bootloop for 3 hours trying to fix it.
I tried to extract the BOOT.IMG from the OTA file, trying many tools without success, although in the log of one of the extraction tools it told me that the boot had 100MB, in the output only a boot.img appeared with 0MB