[RECOVERY][TWRP 3.0.0-0]Samsung sm-T810 - Galaxy Tab S2 General

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

Related

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

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

[GUIDE] How to flash the COS 13 update. Even if you get the release keys error

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.

magisk ?

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?

[RECOVERY][UNOFFICIAL]TWRP 3.3.1 Touch Recovery [ALL MODELS]

{
"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

TWRP (Unofficial) SM-N980F Note20

Hi!!
This is my first contact with Android. I have compiled the TWRP for SM-N980F is fully working. I hope we find a custom rom to be able to install it.... I'm going to try to develop one. Let's see how it goes.
TWRP NOTE20
{
"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"
}
Shiresp said:
Hi!!
This is my first contact with Android. I have compiled the TWRP for SM-N980F is fully working. I hope we find a custom rom to be able to install it.... I'm going to try to develop one. Let's see how it goes.
TWRP NOTE20
View attachment 5588669
Click to expand...
Click to collapse
Thanks for your effort. Please let us know, 10 days later, are there any bugs or it works as planned? Are there any special steps we shoul do to install it?
sheebee said:
Thanks for your effort. Please let us know, 10 days later, are there any bugs or it works as planned? Are there any special steps we shoul do to install it?
Click to expand...
Click to collapse
Hi Sheebee,
I haven't found any bug usung the recovery.
And about the install steps, they are the usual to install twrp.
1. Unlock bootloader.
2. Flash with Odin in AP side the twrp file.
3. Reboot in recovery Mode.
---‐-------------------
4. If you want install magisk or rom. Install it
5. Reboot settings power off.
6. Automatically turn on in recovery Mode.
7. Wipe data.
8. Reboot settings and system.
And thats all.
Sorry for no show the steps.
Byeeee
Thanks Shiresp, may the force be with you! Let us know if you find appropriate ROM.
Shiresp said:
Hi!!
This is my first contact with Android. I have compiled the TWRP for SM-N980F is fully working. I hope we find a custom rom to be able to install it.... I'm going to try to develop one. Let's see how it goes.
TWRP NOTE20
View attachment 5588669
Click to expand...
Click to collapse
Where u got sources from ?
installed smoothly until i tried to boot to system and found that my device no longer boots to system lol now having a hard time finding the stock firmware for the usa model
i think you should try installing GSI ' s to your device
deathbypvp said:
installed smoothly until i tried to boot to system and found that my device no longer boots to system lol now having a hard time finding the stock firmware for the usa model
Click to expand...
Click to collapse
It's just for n980F model. Im using a european model and works properly
Ivan2005 said:
Where u got sources from ?
Click to expand...
Click to collapse
Twrp??? From github.. c1s model....
Shiresp said:
It's just for n980F model. Im using a european model and works properly
Click to expand...
Click to collapse
idk what region model my device was but its a n980f and it just boots to the custom recovery
I have a eu version sm-n980f/ds, android 12. Twrp is installed but you can not boot the system. it remains in twrp recovery
deathbypvp said:
idk what region model my device was but its a n980f and it just boots to the custom recovery
Click to expand...
Click to collapse
When twrp boots, after that you try reboot -> system???
edsoedso said:
I have a eu version sm-n980f/ds, android 12. Twrp is installed but you can not boot the system. it remains in twrp recovery
Click to expand...
Click to collapse
I'll do it with 4 n980F and work. After twrp boot, reboot -> system
Shiresp said:
I'll do it with 4 n980F and work. After twrp boot, reboot -> system
Click to expand...
Click to collapse
I have already rooted phone but have not installed recovery. I tried to install it through magisk but unsuccessfully. Could you please be more specific in steps you follow to install it through odin? Thank you
edsoedso said:
I have already rooted phone but have not installed recovery. I tried to install it through magisk but unsuccessfully. Could you please be more specific in steps you follow to install it through odin? Thank you
Click to expand...
Click to collapse
1. In Odin uncheck auto reboot.
2. In AP side select twrp file.
3. Flash the file.
4. Press In the device volume down and power, when phone rebooting and before logo press volume up and power. When warning about custom firmware installed, release power button.
5. Into twrp flash samsung disabler 3.0 and flash magisk.
6. Option reboot -> power off.
7. Device rebooting again in twrp automatically.
8. Factory data, no factory reset.
9. Option reboot -> system
10. Device will reboot normally. But this first power on system is normal that it takes a few minutes to start the phone completely.
That's the steps I follow with all twrp I have installed.
BYE!!!
Shiresp said:
1. In Odin uncheck auto reboot.
2. In AP side select twrp file.
3. Flash the file.
4. Press In the device volume down and power, when phone rebooting and before logo press volume up and power. When warning about custom firmware installed, release power button.
5. Into twrp flash samsung disabler 3.0 and flash magisk.
6. Option reboot -> power off.
7. Device rebooting again in twrp automatically.
8. Factory data, no factory reset.
9. Option reboot -> system
10. Device will reboot normally. But this first power on system is normal that it takes a few minutes to start the phone completely.
That's the steps I follow with all twrp I have installed.
BYE!!!
Click to expand...
Click to collapse
Thank you for your prompt reply. What should I do under number 8, wipe data? Thank you!
edsoedso said:
Thank you for your prompt reply. What should I do under number 8, wipe data? Thank you!
Click to expand...
Click to collapse
Jajajaj, that's right wipe data... sorry I was typing from memory.
Shiresp said:
Jajajaj, that's right wipe data... sorry I was typing from memory.
Click to expand...
Click to collapse
Thanks a lot! Really appreciate.
Shiresp said:
Twrp??? From github.. c1s model....
Click to expand...
Click to collapse
The tree was still WIP for official release, that's the reason for which it wasn't on XDA yet. I also see you didn't post any links to sources, neither credits whatsoever.
I opened a thread for Official TWRP here, with more instructions, FAQ and everything needed.
Regards
corsicanu said:
The tree was still WIP for official release, that's the reason for which it wasn't on XDA yet. I also see you didn't post any links to sources, neither credits whatsoever.
I opened a thread for Official TWRP here, with more instructions, FAQ and everything needed.
Regards
Click to expand...
Click to collapse
sorry,
I assumed that the sources we all knew are from github. Without the work of those people developing in the repositories, the compilation of the recovery would be impossible.
I have only compiled the recovery because I needed it personally for 4 n980f.

Categories

Resources