[Recovery][Exynos] Official TWRP for the Galaxy Note 7 (gracelte)
- Thread starter jcadduono
- Start date
@jcadduono Will the Note 7 SM-N9300 (graceqltechn) be supported in the near future?
As you can see from the image below, the bootloader for this device is unlocked via CROM service from Samsung.
As you can see from the image below, the bootloader for this device is unlocked via CROM service from Samsung.
I have done whole steps and wiped data. Now my device "optimizing apps" at every reboot. Did I miss something?
Stock rom, with xposed.
Stock rom, with xposed.
Last edited:
there's your problem, search the thread, this has been mentioned many times
at the moment all we can do is wait for Note 7 compatibility
Sent from my Galaxy S6 using Tapatalk
@jcadduono Will the Note 7 SM-N9300 (graceqltechn) be supported in the near future?
As you can see from the image below, the bootloader for this device is unlocked via CROM service from Samsung.
sure I have no problem supporting graceqltechn if anyone who has it ever shows up in #twrp for testing, it shouldn't be much trouble
update: https://github.com/jcadduono/android_device_samsung_graceqltechn
setting up kernel now
I wanted to do a similar thing. At first I started by trying to use ext2simg on my data partition (/dev/block/dm-0) from within a root shell which produced data.img of ~5 GB (my used space) on my external SD. While the image was technically valid and capable of being restored in TWRP, it was full of errors due to writes which happened during the conversion process (if I could somehow remount /data ro while booted, this could succeed!), these writes during the sparse image creation caused a mismatch between the data and the file metadata resulting in a really corrupt ext4 sparse image.
My next attempt will be to take the TWRP backup code and create a single binary (can be installed to /system/bin/backup-data via TWRP flashable zip) that when run will create a TWRP restorable tar backup of your data partition, optionally with gzip compression. At least using a tar I can forgo the ext4 metadata corruption issue, and then allow easy restore of that in TWRP.
Last edited:
@jcadduono Very appreciated that you are providing support to Samsung Galaxy Note 7 (SM-N9300) devices.
I am willing to test this variant of TWRP on my device (SM-N9300_HK), but I don't even know how to compile or setup my system to compile the code. If it is possible if you can help with output the tar image?
Also, Will the version "N9300ZCU1APGJ" work on devices on "N9300ZCU1APGI"?
Last edited:
you need to work with me in IRC at #twrp on freenode
https://webchat.freenode.net/?channels=twrp
I will compile for you
Just quick confirmation... If I just want root and a bootable system, do I have to flash the Samsung Anti-root protection removal zip, or should I just flash SuperSU 2.78?
Well I noticed that my N930FD is not happy with the fast wireless charger when in recovery.......
First off, sorry about the potato quality: This was filmed using an apple product.
https://www.youtube.com/watch?v=KxVGVRb4cbM
I just wanted to share this and see if anyone else has noticed this.
First off, sorry about the potato quality: This was filmed using an apple product.
https://www.youtube.com/watch?v=KxVGVRb4cbM
I just wanted to share this and see if anyone else has noticed this.
Very interesting, but why charge it wireles9when in recovery mode anyway
I was using recovery while watching netflix in bed and my wireless charger was next to me so i just left the phone on it out of habit haha. It's just something weird i noticed and felt like sharing.
Hello,
I'm trying to install Google Dialer 4.x in Note7
http://xdaforums.com/s7-edge/themes/root-stock-google-dialer-4-0-galaxy-s7-t3446793
This shall require only TWRP, right?
Is root required for this? Suggestions please?
I'm trying to install Google Dialer 4.x in Note7
http://xdaforums.com/s7-edge/themes/root-stock-google-dialer-4-0-galaxy-s7-t3446793
This shall require only TWRP, right?
Is root required for this? Suggestions please?
Last edited:
force70
Senior Member
I would politely suggest posting this in Q&A where it belongs as it has nothing to do with twrp.
Ot better yet ask in the thread you linked
Sent from my SM-N930F using Tapatalk 2
Zionator
Senior Member
- Jan 28, 2009
- 2,138
- 644
Not only was the music horrible but why r u posting that video here?
Do u not know where u r?
Sent from my SM-N930F using XDA-Developers mobile app
hello, i succeed in flashing TWRP. I can boot in TWRP. But i failed to wipe data. TWRP is unable to mount data partition.
No problem with system, EFS, storage...
Help would be appreciate...
No problem with system, EFS, storage...
Help would be appreciate...
Has been answered a thousand times here, your device is encrypted..
Sent from my SuperMan powered SM-G930F
Ok. I succedeed. Have to format data before and not wipe. Same word in french.... just install hydra Rom and testing. Will report in thread. Thanks
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
52Team Win Recovery Project 3.0.2-1
This is for the International SM-N930F/X, Duos SM-N930FD, and Korean SM-N930K/L/S Exynos models only! Do not flash on Snapdragon models!
WARNING #1: Flashing a custom recovery to your device will trip the Knox warranty bit on your phone. Check with your mobile provider to see if they will still cover warranty on Knox bit triggered devices. If you understand this risk, continue on.
You generally don't have to worry, as it's incredibly hard to brick a Samsung device, and physical damage warranties should be exempt from Knox triggering.
WARNING #2: The Galaxy Note 7 stock boot image has dm-verity, which prevents you from booting if you swipe to enable system modifications!
SOLUTION: Follow the full rooting steps below, in order, to allow system modifications without the risk of a boot loop!
WARNING #3: When using custom kernels on the Note 7, never turn off developer options or OEM unlock. If you do, you will lose all your data and have to flash a full stock firmware restore to use your device again!
WHAT IS TWRP?
Oh come on, you know what it is - don't try to fool me!
In case you're serious, though...
Team Win Recovery Project is a custom recovery for Android devices.
It allows you to back up and restore your data, flash custom ROMs to your device, repair broken file systems, and root your device.
DOWNLOAD
You can find the device page here:
http://teamw.in/devices/samsunggalaxynote7exynos.html
There is a download link there, as well as instructions on how to flash it.
I highly recommend using Odin 3.12.3+ to flash when possible.
You can find a zip containing Odin as well as Samsung's Mobile drivers here:
https://build.nethunter.com/samsung-tools/
FULL STEPS FOR OBTAINING ROOT
Follow these instructions until someone nice comes along and makes a video from them (without ads):
- In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
- Now go to Settings -> Developer options. (above About device)
You need to enable OEM unlock, otherwise you might end up with boot problems or be unable to flash later on.
Do not ever turn off Developer Options or OEM unlock. Doing so will cause your device to refuse to boot and require a full factory restore.
- Extract Odin_3.12.3.zip to your computer.
- Install Samsung Mobile Phone Drivers for Odin to find your device.
- Download a .tar image of TWRP for gracelte.
- Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] + [Power] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
- Open Odin and place that TWRP tar file in the [AP] slot and disable Auto-Reboot, then press [Start].
- Hold [Volume Down] + [Home] + [Power] to get out of Download mode and immediately swap to [Volume Up] when the screen blanks.
If you don't see then TWRP boot splash try again from step 6.
- At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow the next step you will be unable to boot!
If you are going to root your device and follow the rest of these steps, then it is safe to swipe right and enable modifications.
- If you want to be rooted with SuperSU:
Download the latest SuperSU by Chainfire.
Without exiting TWRP, transfer the SuperSU zip to your device over MTP* and flash it using [Install] in TWRP.
If you want to be rooted with something else or just want a bootable system:
Download the latest Samsung Anti-Root Protection Removal zip.
Without exiting TWRP, transfer the samsung-antiroot-removal zip to your device over MTP* and flash it using [Install] in TWRP.
This zip will allow you to flash SuperSU versions earlier than 2.77 and use other rooting methods.
It uses a hex pattern (by Chainfire) replacement method in the kernel that simply disables the anti-rooting protection.
It will also disable the status bar notification about unauthorized changes.
It includes the functions of the no-verity-opt-encrypt zip.
- Go to [Reboot] -> [System].
- Wait 2-5 minutes for your device to finish setting itself up.
CHANGES
- v3.0.2-1 - Fix restoring of non-ext4 partitions, update f2fs drivers, update to BPID source & Linux 3.18.43, add 60% battery charging limiter
- v3.0.2-0 - Official release on twrp.me
- v3.0.2-0-b3 - Fix colors and use NTFS-3G
- v3.0.2-0-b2 - Initialize new device tree based on Samsung OSRC N930FXXU1APGK kernel source.
FEATURES
- MTP support
- USB Mass Storage support
- Micro SDcard and USB OTG storage support
- f2fs file system support (read, write, format, backup & restore)
- exFAT file system support (read, write, format, backup & restore)
- NTFS file system support (read, write, format)
- ADB root
- Full SELinux support
- Built in android 6.0 tree
KNOWN ISSUES
- Samsung encryption is not supported yet in TWRP 3.0 (see: https://gerrit.omnirom.org/#/c/17308/)
CONTACT & SUPPORT
You can find us on IRC at #twrp on chat.freenode.net.
You can also post in this thread and I will attempt to answer any questions you may have.
SOURCE CODE
TWRP: https://github.com/omnirom/android_bootable_recovery (android-6.0)
Device tree (International): https://github.com/TeamWin/android_device_samsung_gracelte (android-6.0)
Device tree (Korea): https://github.com/TeamWin/android_device_samsung_graceltekor (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_universal8890 (twrp-6.0)
CONTRIBUTIONS
Gerrit for TWRP: http://gerrit.omnirom.org/
Gerrit for officially supported devices: http://gerrit.twrp.me/
XDA:DevDB Information
Team Win Recovery Project - Samsung Galaxy Note 7, Tool/Utility for the Samsung Galaxy Note 7
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/TeamWin/android_device_samsung_gracelte
Version Information
Status: Stable
Current Stable Version: 3.0.2-1
Stable Release Date: 2016-10-15
Created 2016-08-23
Last Updated 2016-11-082322SuperSU v2.77 BETA has been posted in the SuperSU BETA thread here: http://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
Release notes are still being written, be sure to check back later and read them. Useful stuff to know.
Having some issues getting CF-Auto-Root to work on Dr.Ketan's device right now, so I will probably delay official support for that until I have my own device.
Thanks to @dr.ketan and @SeraphSephiroth for their help.
EDIT: Release notes here: https://plus.google.com/+Chainfire/posts/S4ucYdfqPhq19@SeraphSephiroth 's device now has SuperSU apparently fully working. Hurrah.
Needs some more automation and testing, but should be released soon.19
So, me and @dr.ketan have been spending quite a few hours on this (remote debugging for the lose) and we did find the problem.
The quickest and dirtiest fix would be universal and give you basic root, but it would disable some of SuperSU's functionality and will still cause many root apps to fail (and trigger reboots).
Another option is a kernel built from source with the patch, but this is not universal. I also have not succeeded compiling a booting kernel from source yet for this device, but that failure is probably wholly mine.
I have another solution in mind that will be kernel-agnostic, but has some other drawbacks, like longer boot times and just being plain odd.
Anyway, time to catch some sleep. This sure would've been a lot faster if I had an actual device. - In your ROM, go to Settings -> About device. Tap 7 times on Build number to enable Developer options.
