Team Win Recovery Project 3.0.2-0
This is for the Chinese SM-G9300 and SM-G9308 Qualcomm models only! Do not flash on Exynos models!
If you have a SM-G9350 look here instead!
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 S7 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!
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/samsunggalaxys7china.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.
{
"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"
}
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.
You will need to unlock your bootloader now. To do this, download the app "CROM Service By Samsung Electronics Co., Ltd." from the Galaxy Apps store and run it.
Follow the instructions in the CROM Service app to allow your device to accept custom images in download mode.
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 heroqltechn.
Reboot your device into Download mode. To do this, select reboot from the power menu and hold the [Volume Down] + [Home] buttons while your device reboots.
Once you reach the Download mode warning screen, press [Volume Up] to continue.
Open Odin and place that TWRP tar file in the [AP] slot 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 7.
At this point, you will reach the screen asking you if you want to allow system modifications.
By swiping right, you will trigger dm-verity, and if you don't follow step 10 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 no-verity-opt-encrypt zip.
Without exiting TWRP, transfer the no-verity-opt-encrypt zip to your device over MTP* and flash it using [Install] in TWRP.
It will allow your system to boot after swiping to enable modifications or using backup/restore in TWRP.
It should also allow you to use [Format Data] and prevent encryption, allowing you to use your data partition and internal storage inside TWRP.
Go to [Reboot] -> [System].
Wait 2-5 minutes for your device to finish setting itself up.
* MTP, known as Media Transfer Protocol, is the same way you transfer files from your PC to your device when booted into system.
CHANGES
v3.0.2.0 - Official release on twrp.me
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 (USA): https://github.com/jcadduono/android_device_samsung_heroqlte (android-6.0)
Device tree (China): https://github.com/TeamWin/android_device_samsung_heroqltechn (android-6.0)
Kernel: https://github.com/jcadduono/android_kernel_samsung_msm8996 (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 S7 China, Tool/Utility for the Samsung Galaxy S7
Contributors
jcadduono, Team Win & friends
Source Code: https://github.com/TeamWin/android_device_samsung_heroqltechn
Version Information
Status: Stable
Current Stable Version: 3.0.2-0
Stable Release Date: 2016-09-09
Created 2016-09-10
Last Updated 2016-11-22
As a joke, here you go USA!
https://idlekernel.com/twrp/heroqlte/twrp-3.0.2-0-heroqlte.tar.md5
It works for all USA variants of the S7, but you can't boot it because of your signature enforcement (locked bootloader)! Muahahahaha!
jcadduono said:
As a joke, here you go USA!
https://idlekernel.com/twrp/heroqlte/twrp-3.0.2-0-heroqlte.tar.md5
It works for all USA variants of the S7, but you can't flash it! Muahahahaha!
Click to expand...
Click to collapse
xD I'm waiting for the damn bootloader's to be unlocked!
I have a Samsung Galaxy S7 SM-G930U (unlocked version) ........I currently am using this device in nigeria and i want to unlock bootloader/root/ install TWRP but it doesnt allow the TWRP install on ODIN.... MY device is using the Qualcomm/ not the EXYNOSS
phone model: SM-G930U
device type: heroqlteue
product name: heroqlteue
product code: SM-G930UZKAXAA
CSC: XAA USA/US
BOOTLOADER: G930UUEU2APG9
Hardware: qcom/msm8996
please help.
obone410 said:
I have a Samsung Galaxy S7 SM-G930U (unlocked version) ........I currently am using this device in nigeria and i want to unlock bootloader/root/ install TWRP but it doesnt allow the TWRP install on ODIN.... MY device is using the Qualcomm/ not the EXYNOSS
phone model: SM-G930U
device type: heroqlteue
product name: heroqlteue
product code: SM-G930UZKAXAA
CSC: XAA USA/US
BOOTLOADER: G930UUEU2APG9
Hardware: qcom/msm8996
please help.
Click to expand...
Click to collapse
U = USA (only SIM unlocked, still bootloader locked, it's the same as all the other USA variants)
it will never be able to use TWRP.
jcadduono said:
U = USA (only SIM unlocked, still bootloader locked, it's the same as all the other USA variants)
it will never be able to use TWRP.
Click to expand...
Click to collapse
WHY HAST THOU FORSAKEN ME!!!!
But really tho when you say never... Will I never be able to use GOV Tuner?
Also for anyone stuck in a loop after trying to flash TWRP (don't ask how I know this!) if you restart into download mode and press up you can get it to restart normally from there. FYI.
Any luck with the v variants? G935v / G930v? Could we boot a recovery and not flash it like the guys in the amazon fire forum?
G9300 APE3 root ok, but modem version unknown. modem fatal.
来自我的 Mi-4c 上的 Tapatalk
i have a s7 g9308 from china mobile, pls confirm if this will gonna work and can i install gapps aftet thid method works?
knoxgin said:
i have a s7 g9308 from china mobile, pls confirm if this will gonna work and can i install gapps aftet thid method works?
Click to expand...
Click to collapse
no idea, you should let me know. back up system in twrp and then flash your gapps package, probably "ARM64 -> 6.0 -> Nano" (it is minimal but has everything that can't be installed from play store) from opengapps.org to be safest. Any other google app can be installed from play store if that succeeds.
If it fails to work, simply restore the system backup you made and you're back to how you were!
jcadduono said:
no idea, you should let me know. back up system in twrp and then flash your gapps package, probably "ARM64 -> 6.0 -> Nano" (it is minimal but has everything that can't be installed from play store) from opengapps.org to be safest. Any other google app can be installed from play store if that succeeds.
If it fails to work, simply restore the system backup you made and you're back to how you were!
Click to expand...
Click to collapse
ok tnx sir. but this method really work? if i follow the steps? coz if i brick it , i dnt know How to flash it back to stock tru odin.
installing twrp works, but if i flash supersu only, then reboot, root works but lost my signal and if i flash no-verity-opt-encrypt zip. only then reboot, it works and has signal, and if i flash both, rooted but no signal, pls help.. also, gapps x64 6.0 nano get errors in google play services, cant download or update apps, i think the problem sir is in supersu, coz everytime i flash it i lost my signal, im glad i have my backup in twrp , pls help fix this bug, i want a rooted and working gapps, coz china mobile dnt have gapps pre installed
jcadduono said:
As a joke, here you go USA!
https://idlekernel.com/twrp/heroqlte/twrp-3.0.2-0-heroqlte.tar.md5
It works for all USA variants of the S7, but you can't flash it! Muahahahaha!
Click to expand...
Click to collapse
Holly sh**!!! I flashed this and I have TWRP in on US variant now.
Can't read!
---------- Post added at 06:20 PM ---------- Previous post was at 06:18 PM ----------
KillerClaw321 said:
xD I'm waiting for the damn bootloader's to be unlocked!
Click to expand...
Click to collapse
There is always hope (Looks at Note 4)
evrycard said:
Holly sh**!!! I flashed this and I have TWRP in on US variant now.
Click to expand...
Click to collapse
So flashed this on which US S7 variant and software , 930U or ?
evrycard said:
Holly sh**!!! I flashed this and I have TWRP in on US variant now.
Click to expand...
Click to collapse
Seriously? Or troll?
jcadduono said:
As a joke, here you go USA!
https://idlekernel.com/twrp/heroqlte/twrp-3.0.2-0-heroqlte.tar.md5
It works for all USA variants of the S7, but you can't flash it! Muahahahaha!
Click to expand...
Click to collapse
What do you mean it works but we can't flash it? I understand that our bootloader is locked but can we flash this with FlashFire on our G930A?
Thank you
dirtydodge said:
What do you mean it works but we can't flash it? I understand that our bootloader is locked but can we flash this with FlashFire on our G930A?
Thank you
Click to expand...
Click to collapse
Joking with the OP.
dirtydodge said:
What do you mean it works but we can't flash it? I understand that our bootloader is locked but can we flash this with FlashFire on our G930A?
Thank you
Click to expand...
Click to collapse
fixed the post, you can flash it but you can't boot it due to locked bootloader (signature enforcement)
Help me
i tried to flash your recovery and stock rom after that. So my mobile is starting bootloop. Can you help me to solve this problem. I think a stock recovery is a solution to solve that
Related
I have combined the OnePlus 3 and OnePlus 3T TWRP threads into a single thread for the unified build.
Please visit:
https://forum.xda-developers.com/oneplus-3/development/recovery-official-twrp-oneplus-3-3t-t3543391
I apologize for the inconvenience.
XDA:DevDB Information
Team Win Recovery Project for the OnePlus 3T, Tool/Utility for the OnePlus 3T
Contributors
jcadduono, Team Win
Source Code: https://github.com/jcadduono/android_device_oneplus_oneplus3t
Version Information
Status: Stable
Current Stable Version: 3.0.3-1
Stable Release Date: 2017-01-16
Created 2016-11-26
Last Updated 2017-01-22
Reserved
ONEPLUS FULL OTA ZIPS
You can flash these zips in TWRP to update your device or save yourself from a broken or soft-bricked state.
They are official zips distributed by OnePlus.
OxygenOS 3.5.3: https://s3.amazonaws.com/oxygenos.o...8_OTA_027_all_1611222319_884473ff95304c30.zip
OxygenOS 3.5.4: http://oxygenos.oneplus.net.s3.amaz...8_OTA_029_all_1612131737_17e7161d2b234949.zip
OxygenOS 4.0.0: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_035_all_1612310259_2dc0c.zip
OxygenOS 4.0.1: http://otafsc.h2os.com/patch/amazon...ygen_28_OTA_037_all_1701041831_a2ba632ce9.zip
OxygenOS 4.0.2: http://otafsc.h2os.com/patch/amazon...s3TOxygen_28_OTA_039_all_1701140132_400a7.zip
Warning: Do not flash partial update OTAs (under 1 GB) on a modified device! If you want to use partial OTAs, you must first flash a full OTA that it applies to, and then flash the partial OTA from stock recovery. Flashing partial OTAs from TWRP will either fail or soft brick your device. You can return to a usable state by flashing one of the above full OTA zips in recovery.
Now if I have already rooted and installed a kernel will flashing TWRP wipe that stuff? I had to boot TWRP to flash SU and Kernel but did not flash it.
ghettopops said:
Now if I have already rooted and installed a kernel will flashing TWRP wipe that stuff? I had to boot TWRP to flash SU and Kernel but did not flash it.
Click to expand...
Click to collapse
TWRP will only wipe if you ask it to wipe something. OnePlus is using the usual separated recovery partition style which is great so you don't have to worry about TWRP breaking anything by flashing it.
jcadduono said:
TWRP will only wipe if you ask it to wipe something. OnePlus is using the usual separated recovery partition style which is great so you don't have to worry about TWRP breaking anything by flashing it.
Click to expand...
Click to collapse
So that means it doesn't use that new layout which includes dual A/B partitions right? If the only benefit of dual partitions is seamless updates, I guess the traditional layout is fine or even better.
Edit: Both this TWRP thread and the Tyranus kernel thread came out pretty quick, and seem very well documented and professional compared to some of the other Non Nexus device threads. I'm impressed. I just hope the threads stay uncluttered. Thank you.
So that I understand, separate recovery partition means that I can have both TWRP and Oxygen Recovery installed. Allowing me to get updates and install them through Oxygen Recovery while maintaining a TWRP recovery? Also is it just a matter of booting into them via fastboot?
Perhaps, the step between 2 and 3 should be go into the 'system>about' menu, keep tapping 'build number' to enable 'developers option', then go back out and into 'setting>developers option' and turn on 'OEM unlocking'. w/o this option turn on, you can do 'fastboot oem unlock'
And maybe perhaps, before doing anything, why not update the system via OTA first? If the OTA zip is OnePlus official, you should be able to flash it using stock recovery, doesn't it?
side note tip: if you wipe the data partition in TWRP, the default would be ext4, but the OP stock use F2FS. I think it may be wise to change that before wiping the data partition.
someone0 said:
Perhaps, the step between 2 and 3 should be go into the 'system>about' menu, keep tapping 'build number' to enable 'developers option', then go back out and into 'setting>developers option' and turn on 'OEM unlocking'. w/o this option turn on, you can do 'fastboot oem unlock'
And maybe perhaps, before doing anything, why not update the system via OTA first? If the OTA zip is OnePlus official, you should be able to flash it using stock recovery, doesn't it?
side note tip: if you wipe the data partition in TWRP, the default would be ext4, but the OP stock use F2FS. I think it may be wise to change that before wiping the data partition.
Click to expand...
Click to collapse
Done. Should now default to f2fs on data wipes as well. (redownload, I didn't change the version number)
Yes that is an option.
ghettopops said:
So that I understand, separate recovery partition means that I can have both TWRP and Oxygen Recovery installed. Allowing me to get updates and install them through Oxygen Recovery while maintaining a TWRP recovery? Also is it just a matter of booting into them via fastboot?
Click to expand...
Click to collapse
No, separate recovery partition means you can flash kernels and recoveries separately. It means recovery isn't part of the system boot image, which is an idiotic design of the Pixel phones that is hurting custom development for them. See example:
OnePlus 3T (and every other sane device):
boot partition = system boot image
recovery partition = recovery boot image
result = you can use twrp to flash custom roms! any issues = just try in twrp again!
Pixel:
boot partition = boot image with recovery ramdisk that loads system (???)
boot_a partition = the same thing as boot partition (??? again)
recovery partition = nowhere to be found
result = flash a bad custom rom? say goodbye to twrp!
Can't decrypt data so can't flash any files. Just updated to twrp in the op.
charlieb620 said:
Can't decrypt data so can't flash any files. Just updated to twrp in the op.
Click to expand...
Click to collapse
need recovery.log ... i'm guessing this is happening due to changing default partition type for data from ext4 to f2fs, might need to change it back
in the meantime, setting default back to ext4....redownload (again)
in the meantime, anyone crazy enough to test https://build.nethunter.com/test-builds/oneplus/kernel-nethunter-oneplus3t-marshmallow-test1.zip for me?
yes, this device is getting official Kali NetHunter support
Log
http://www87.zippyshare.com/v/7OhpiOv2/file.html
jcadduono said:
in the meantime, anyone crazy enough to test https://build.nethunter.com/test-builds/oneplus/kernel-nethunter-oneplus3t-marshmallow-test1.zip for me?
yes, this device is getting official Kali NetHunter support
Click to expand...
Click to collapse
Woah! Now official nethunter? I can test this Monday when I get the device. I would be surprised if we got copperhead OS too.
Another known issue: I can't get USB-OTG to work. Even in the StockOS, it seem disable by default and have to enable first, otherwise it won't provide power back out to the USB port. Not sure if this is related.
charlieb620 said:
Log
http://www87.zippyshare.com/v/7OhpiOv2/file.html
Click to expand...
Click to collapse
that's stock recovery....enable xda signatures and you will see how to get logs in my signature
someone0 said:
Another known issue: I can't get USB-OTG to work. Even in the StockOS, it seem disable by default and have to enable first, otherwise it won't provide power back out to the USB port. Not sure if this is related.
Click to expand...
Click to collapse
i'll look into it i guess, might be a /sys file we can trigger on init to enable it if you want to do the investigation for me
probably related to dash charge stupidity
jcadduono said:
that's stock recovery....enable xda signatures and you will see how to get logs in my signature
i'll look into it i guess, might be a /sys file we can trigger on init to enable it if you want to do the investigation for me
probably related to dash charge stupidity
Click to expand...
Click to collapse
{
"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"
}
Sent from my ONEPLUS A3000
---------- Post added at 05:58 AM ---------- Previous post was at 05:25 AM ----------
Ok started from scratch
Have latest twrp, root and net hunter kernel running.
charlieb620 said:
Sent from my ONEPLUS A3000
---------- Post added at 05:58 AM ---------- Previous post was at 05:25 AM ----------
Ok started from scratch
Have latest twrp, root and net hunter kernel running.
Click to expand...
Click to collapse
That screenshot seem like somebody is trying to run adb from within the android shell. I would just
'adb shell'
'su'
'cd /sdcard' or /tmp or whichever directory that's writable.
then run whatever command you need from there. Having another DOS windows open up is also a good idea. That way, one window is always running shell, and another is just DOS. so no confusion and no need to keep exiting shelf and get back in.
Fails to decrypt data. Here is logs from 3t 128gb model.
Black screen
Followed instructions to a "T" (haha)
Everything gets installed, i have root, but when i try to reboot into recovery/twrp - i just get a black screen. I can still turn the phone off, and start up the phone no problems, so its usable - but just not into twrp.
Any thoughts of suggestions?
hawki said:
Followed instructions to a "T" (haha)
Everything gets installed, i have root, but when i try to reboot into recovery/twrp - i just get a black screen. I can still turn the phone off, and start up the phone no problems, so its usable - but just not into twrp.
Any thoughts of suggestions?
Click to expand...
Click to collapse
How did you get root (superSU) installed w/o twrp?
BTW, you may have the same problem I had earlier, which is the stock OS is on version 3.5.1. You need to follow the instruction again, and flash recovery and boot into twrp.img After that, patch your OS to the latest via OTA, I think you need to re-root again after that.
just to be clear. Since I am already rooted am I just flashing twrp and swiping for Mods?
ATTENTION S8 USERS ONLY!!!
S8 FIRMWARES WITH V3 & HIGHER BOOTLOADERS HAVE BEEN PATCHED AGAINST THE SAMFAIL METHOD STAY ON V2 BOOTLOADERS!!!
S8+ USERS V5 BOOTLOADERS CAN STILL BE USED WITH SAMFAIL METHOD!
Please Note This Is Not A Root Method For Oreo. As Of Now There Is Still No Root Method For OreoThis Takes Some Patience To Install
S8 SM-G950W Install Instructions And Files Can Be Found On My Verizon Thread For Now
In Post Count 3
Click to expand...
Click to collapse
S8+ SM-G955W Install Instructions And Files
Discussion About Flashing OTA's and OTA Method Can Be Further Researched In My Verizon Thread Here
Download
SM-G955W_BRJ2_SAMFAIL_OTA_FRIENDLY.7z
Google Mirror
Install Instructions SamFail Method
ON THESE STEPS ONLY FLASH FILES FOUND IN THE SAMFAIL_INSTALL_FILES FOLDER
Make Sure The Latest Samsung Drivers Are Installed. They Can Be Found Here
1. Flash BL_ENG_BOOTLOADERS_G955_V5.tar in odin
2. Reboot back to download
3. Flash AP_G955_CR**_SYSTEM_IMAGE.tar in AP slot and pit file in pit tab in odin
4. When done flashing it will say fail and phone will reboot then either force reboot to download or wait about 30 seconds to a minute and phone will reboot automatically to download mode failed software update installation screen this is fine its still in download mode. If phone reboots too upload mode for some reason force it back to download mode
5. In odin load BL_DELETE_CACHE_G955_V5_BL.tar in BL slot and flash
6. Phone will reboot to recovery it will try and process update then on blue screen you get an Error(Click For Pic) and recovery will start rebooting let recovery bootloop once then force back to download mode and goto step 7.
If on blue screen you get the No Command(Click For Pic) title instead of the Error(Click For Pic) title on the blue screen then let phone bootloop and force back to download
mode and In odin load BL_ENG_BOOTLOADERS_G955_V5.tar in BL slot and flash. Phone reboot to stock recovery there wipe
cache and reboot back to bootloader from recovery and goback and start again from step 5
7. In odin load BL_G955USQU5CRK1.tar in BL slot and HOME_CSC_OYN_G955U*****tar in CSC slot and flash
8. Phone will reboot to recovery and process cache then your ready to flash an OTA update zip in stock recovery. If you get an Error(Click For Pic) in stock recovery and phone does not automatically reboot at this point wait until recovery options come up and wipe cache in stock recovery reboot from recovery to bootloaders and repeat step 7.
9. It should then process csc fine this time and from recovery phone should reboot automatically. If for some reason this still fails start from Step 5 again.
Flashing An OTA update.zip
US OTA Downloads With Odin FIles Can Be Found Here
I Don't Know Where To Get Canadian OTA's So Unless You Are Able To Capture Your OTA Update Zip I Suggest Not Taking An OTA Because You Will
Have No Way To Create The Needed Bootloader Files For Exitin Safestrap
1. Download the G955_CR**_TO_CR**UPDATE_AND_ODIN.7z and unzip Place G955_CR**_TO_CR**.zip on your external sdcard on your phone it must be external sd card. Then place the AP_SM_G955_CR**tar in the ENTER_EXIT_SAFESTRAP folder you will need it later to enter exit safestrap
2. Reboot to stock recovery
3. Choose to flash update.zip from sdcard and choose the G955_CR**_TO_CR**.zip you placed on there
4. If OTA fails to flash make sure you are flashing the the right OTA. If so then you modified something in system and you will have to start over with the SamFail Method above
To Enter And Exit Safestrap
ON THESE STEPS ONLY FLASH FILES FOUND IN THE ENTER_EXIT_SAFESTRAP FOLDER
1. Before leaving Safestrap wipe cache and dalvik cache then leave safestrap and put phone in download mode. From the ENTER_EXIT_SAFESTRAP folder flash BL_ENG_BOOTLOADERS_SAFESTRAP_G955U_V5.tar in BL Slot in odin
2. To leave safestrap reboot to bootloader or download still does not work so you still need to manually reboot to bootloader
3. Use modded Odin and load BL_DELETE_CACHE_G955_V5_BL.tar In BL Slot and flash
4. Phone will reboot to recovery it will try and process update then on blue screen you get an Error(Click For Pic) and recovery will start rebooting let recovery bootloop once then force back to download mode and goto step 5
If on blue screen you get the No Command(Click For Pic) title instead of the Error(Click For Pic) title instead of the Error(Click For Pic) title on the blue screen then let phone bootloop and force back to download
mode and In odin load BL_ENG_BOOTLOADERS_SAFESTRAP_G955U_V5.tar in BL slot and flash. Phone reboot to stock recovery there wipe cache and reboot back to bootloader from recovery and goback and start again from step 3
5. Flash BL_ENG_BOOTLOADERS_SAFESTRAP_G955U_V5.tar in odin phone will reboot to recovery
6. In recovery wipe cache then from recovery reboot to bootloader
7. Use modded Odin and load BL_G955_CRK1_V5.tar In BL Slot, AP_CR**.tar(This is the file you will get from the OTA_Update_Zips) in AP Slot and flash (Or file you created from update zip or leave AP slot blank if you are stil on CRK1 firmware
8. As soon as phone powers off force reboot to recovery. If you get an Error(Click For Pic) in stock recovery instead of No Command(Click For Pic) and phone says dm verity failed reboot from recovery to bootloaders and start on step 3 in To Enter And Exit Safestrap
9. If you get the No Command(Click For Pic) and it says successfully verified dmverity hashtree(Click For Pic) Wipe cache in recovery then reboot and you are done
Alt Method Creating Your Own Stuff (Only For Experienced Users!)
Can Be Found HERE
Feature:
System Can Still Flash OTA Update zips
SafeStrap Recovery PreLoaded
Xposed Framework Can Be Flashed
Official Oreo
Safetynet Passes
Samsung Pay,Pass,Secure Folder Working
Samsung Cloud Enabled
Places Tab Enabled
Spam Caller Id Enabled
Call Recording Enabled
Native Status Bar Speed Meter Enabled
Custom Boot Animation
Helpful Key Combos
Recovery Mode
Bixby + Volume Up + Power @ Same time
Download Mode
Bixby + Volume Down + Power @ Same time
Safe Mode
Phone Powered Off
Press and hold the Power key past the model name screen.
When “SAMSUNG” appears on the screen, release the Power key.
Immediately after releasing the Power key, press and hold the Volume down key.
Maintenance Mode
Press and hold the Power + Volume Down buttons for approximately 10
Bugs:
DO NOT USE ENCRYPTION
Safestrap is still beta so there are some bugs
All reboot options in safestrap only reboot the phone.
Safestrap might not read larger than 64gig sd cards on some cards
Formating data in safestrap may cause reboot so make sure to format data very last thing
What Is Safestrap
Safestrap is a Bootstrap / Recovery for locked bootloader phones. Safestrap is now based on TWRP Recovery (a touch based recovery) and you can perform .zip installs, backups and restores here.
{
"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"
}
Credits:
- @Raymonf for modified odin
- @afaneh92 for safestrap Main Thread Here Consider a donation to him he worked along time on this Donation Link
- @me2151 for finding this method
- @tytydraco for some instructions
- @mweinbach for some instructions
- @Craz Basics for xposed on non rooted
- @partcyborg for finding the root method!
- @elliwigy for being great help and original S8 root
- @rayan-refoua for boot animation
- @SamGuy2020 for testing S8 install method
Click to expand...
Click to collapse
SafeStrap Flashable Zips
OTA Friendly Zips That Will Not Break OTA Updates
Google_Style_OTA_Friendly_With_ADB_Disabler.7z
SM_955W_Canadian_Mods_Safe_OTA.zip
Add cscfeatures.xml with the call recording, places tab, spam call blocking also custom boot animation and this mod will not affect the
flashing of OTA update zips however after you flash an OTA update zip you will have to reapply this zip
Remove FRP Protection Safestrap Flashable Zip
View attachment 4503818
Directions For FRP
So if your stuck and dont know google account info Do the samfail process when all done flash file to enter safestrap once in safestrap mount and unmount system then flash SS_Remove_FRP zip then follow direction to leave safestrap. After your phone reboots from recovery the last time force phone back to recovery wait until options come up and wipe data and you can now enter new google account in setup or skip
SafeStrap Recovery Update
Safestrap-4.07-B1-DREAM2QLTE_XBIN.zip
Flash in safestrap recovery then reboot back to safestrap
Click to expand...
Click to collapse
Below Zips Will Break OTA
Dolby Atmos Mod
SoundAlive_8.0.63.zip HeadPhones Working
SoundAlive_8.0.21.zip Speaker/Headphones Working
SM_G955U_Dolby_Installer_1.5.zip
SM_G950U_Dolby_Installer_1.5.zip
Choose The SoundAlive you want to install
Flash in Safestrap
Then Choose The Dolby Installer and flash right after you flash the SoundAlive zip
If you want to try different SoundAlive zip once Dolby Installer is installed you can just flash the SoundAlive zip without flashing the Dolby Installer zip again
ALL Zips Below Will Break OTA Updates
Extreme Aroma based debloater for S8/S7/S9 devices by OrelMadK
https://forum.xda-developers.com/galaxy-s8/themes/4-2-18-extreme-aroma-based-debloater-s8-t3744608
This aroma debloater probably one of the best I have seen by @orelta
The above zips cannot be undone If you want to go back to stock you would need to do the Install process over but you shouldnt need to wipe data this time
Xposed Framework Installer zip
View attachment 4476475 Flash In safestrap
Xposed Installer APK
View attachment 4476478 Install as normal apk then open app make sure framework is installed (the box will be yellow) then reboot open and box will be green showing its working
Xposed Uninstaller zip
View attachment 4471891
Xposed Edge And Google Sans & iOS 11 Emojis
ATT CSC Edits
Dual Speaker Mod
Click to expand...
Click to collapse
Uninstall Apps Using ADB
Enable Developer Options in settings goto system/about/software tap build info like 7 times
In devlopers options enable USB debugging and make sure to accept prompt on phone to allow debugging
In adb command type
adb shell pm list packages -f > Installed_Packages.txt
this will give you a list
then too delete type
adb shell pm uninstall -k --user 0 com.the.name.of.package
Helpful Ones
adb shell pm uninstall -k --user 0 com.samsung.sdm
This will disable OTA on Verizon
adb shell pm uninstall -k --user 0 com.samsung.sdm.sdmviewer
This will disable OTA on Verizon
adb shell pm uninstall -k --user 0 com.samsung.android.securitylogagent
This will disable Security Log Agent
Deleting apps like this will not affect ota's
Warning this can only be undone with a system wipe
Click to expand...
Click to collapse
Credits
- @SamGuy2020 For Dual Speaker Mod
- @FatalONEM8 For ATT CSC Edits
- @ImbaWind For Dolby Atmos Mod
- @rovo89 for xposed Main xposed thread
- @IDan1109 base of debloat script
- @EmperorEye for some build.prop tweaks script
- @xdanilva for xposed edge
Mine
Thank for Canada people
I wait for the oem unlock and I wonder if i have to worry about it or i flash all?
deadedge7 said:
Thank for Canada people
I wait for the oem unlock and I wonder if i have to worry about it or i flash all?
Click to expand...
Click to collapse
Oem unlock doesn't exist for your device. Regardless, this ROM is safe to flash. Just follow the OP.
Sent from my SM-G950U using XDA Labs
bradical711 said:
Oem unlock doesn't exist for your device. Regardless, this ROM is safe to flash. Just follow the OP.
Sent from my SM-G950U using XDA Labs
Click to expand...
Click to collapse
I look oem unlock and turn on after flash g955u and return stock missing oem unlock 7 day wait
Switch turn on parameter dev option exist for me, but i did not try to flash twrp yet view i have to wait 7 days
new cell buying
Tell me if I'm wrong, but if I have this option is it just a fake to install twrp
G955W
deadedge7 said:
I look oem unlock and turn on after flash g955u and return stock missing oem unlock 7 day wait
Switch turn on parameter dev option exist for me, but i did not try to flash twrp yet view i have to wait 7 days
new cell buying
Tell me if I'm wrong, but if I have this option is it just a fake to install twrp
G955W
Click to expand...
Click to collapse
Just because you have an oem unlock button doesn’t mean you can flash twrp. You need unlocked bootloader for that. Sm-G955W has a locked bootloader
Sent using some kind of device I modified
jrkruse said:
Just because you have an oem unlock button doesn’t mean you can flash twrp. You need unlocked bootloader for that. Sm-G955W has a locked bootloader
Sent using some kind of device I modified
Click to expand...
Click to collapse
Ok thank very much for help me info, jump 7 day wait lol and flash your rom now
I'm glad you're here and you're taking care of this rom my friend:good:
Can I have safestrap and rom?
If I flash bL safestrap boot in safestrap
I need to flash the bL stock to get back to system
I losing safestrap
I miss something?
Very thank support
fast rom
deadedge7 said:
Can I have safestrap and rom?
If I flash bL safestrap boot in safestrap
I need to flash the bL stock to get back to system
I losing safestrap
I miss something?
Very thank support
fast rom
Click to expand...
Click to collapse
The instructions are the way it is. Every time you enter and exit safestrap you must follow the instructions
Sent using some kind of device I modified
Wait root eagerly
thank you, this is my gift
of Christmas
deadedge7 said:
Wait root eagerly
thank you, this is my gift
of Christmas
Click to expand...
Click to collapse
It clearly states in the OP this is not root nor will there be any root for Christmas
Sent using some kind of device I modified
Help deleted
If I modify the system in safestrap debloat or deodex
what can I do to pass dm verity failed
gamer_421 said:
If I modify the system in safestrap debloat or deodex
what can I do to pass dm verity failed
Click to expand...
Click to collapse
You can’t deodex the system. If debloat or add some mods you follow the directions to enter and exit safestrap
Sent using some kind of device I modified
Did this work. Not one person ever actually commented and said it worked. So I’ll assume there is really no need to continue with updates to this thread
Sent using some kind of device I modified
jrkruse said:
Did this work. Not one person ever actually commented and said it worked. So I’ll assume there is really no need to continue with updates to this thread
Sent using some kind of device I modified
Click to expand...
Click to collapse
yes nice way open
100% battery
debloat
perfect xposed
Nougat would be appreciated G955W 7.0 rooted
no problem rom
My best rom
jrkruse said:
Mine
Click to expand...
Click to collapse
Will this work for 950u? On rev 2 bootloader ???
Good work as always great to see more life left in them
TheMadScientist said:
Will this work for 950u? On rev 2 bootloader [emoji6][emoji6][emoji6]
Good work as always great to see more life left in them
Click to expand...
Click to collapse
I have a method in my s8+ Verizon pie thread to flash pie with safestrap it does require updating to v5 bootloader but you still maintain the ability to enter and exit safestrap. So from that point forward you use safestrap to flash stuff and to revert back to oreo with safestrap or even rooted nougat. You are just v5. The only drawback is if you ever screwup your system so bad that you can’t enter safestrap then you are screwed and would be stuck on stock v5. If you don’t want to update bootloaders I do have this method in the OP for v2 bootloader but with US firmware
Sent using some kind of device I modified
Can someone verify if the FM chip works on this rom?
T-Mobile V30 H932 30d (Pie) Stock Collection
Based on OEM 30d KDZ. Extracted and Repacked.
DISCLAIMER
Proceed at your own risk. I am not responsible for any damage to your device.
Flashing LAF WILL REMOVE TWRP from your laf partition and restore stock DL Mode
Bins in these packages are unmodified and you may need to flash no-verity-opt-encrypt and rctd remover after to keep force-encryption away.
REQUIRED
TWRP on LAF or Recovery
TWRP 3.2.3-7
Latest Magisk Zip (if performing clean flash)
Magisk
@Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019
@JohnFawkes AK3 RCTD Remover
Link to thread
FILE BREAKDOWN
None of these Zips flash the Recovery partition.
Besides StockLAF, these Zips DO NOT flash the LAF partition.
If you want to restore DL Mode and Stock LAF, you must flash the StockLAF package separately.
Bootloader: 30d Stock Bootloader ONLY
Modem: 30d Stock Modem ONLY
FullStock: Full 30d Stock Firmware Only (bootloader, modem, boot, system) - Instructions in Section A
StockLAF: Individual LAF image for returning to stock DL mode
Global Instructions
Always make a backup first
Zip has been tested VIA Clean AND Dirty Flash following the provided instructions
If device has been encrypted, see encryption notes at the bottom before continuing.
A - FullStock
Copy All Zips to SDCard
Boot to TWRP.
Flash h93230d_FullStock.zip
Flash Magisk
Flash Disable DM-Verity Force Encrypt
Flash AK3 RCTD Remover
Reboot to system and install Magisk Manager (if not installed)
DOWNLOADS
Stable v1.0
Project files are hosted on SourceForge
Bootloader - md5:8ae313d033e883c60d8d4fea89f13c4e
Modem - md5:4ebf96eb1c8bafe06d96502d1558c324
FullStock ROM - md5:6bc9c4af2080003ff80587f98c2348e9
StockLAF - md5:799362769b0712a10818c0f26258efc2
*************************************************************************************************************
Encryption Notes
In Android, a stock device will have it's data encrypted. Often when working in TWRP on an encrypted device, you will be greeted by prompt asking for a passcode in order to decrypt the device. Unless that port of TWRP has been written for your specific device and supports decryption, you will not be able to decrypt the data on your phone. If you cannot decrypt the data, then TWRP cannot mount system and/or other partitions it needs to mount in order to safely flash anything. In order to solve this problem, sadly, you have to format the data partition on your phone (losing all personal data accumulated on the internal storage, so back it all up manually) The steps for this process are Format Data in TWRP, Reboot to recovery (to mount partitions), then flash your rom and root. There are a few tools out there to disable force encryption on your device. See the Required section above for links for this device.
FullStock has been tested VIA Clean AND Dirty Flash.
If anyone has any issues with one or more of these packages, please let me know. Thank you!
-weakNPCdotCom
XDA:DevDB Information
[STOCK] H93230d, ROM for the LG V30
Contributors
weakNPCdotCom
Source Code: https://sourceforge.net/projects/t-mobile-v30-firmware/files/h932/30d/
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
Based On: 30d KDZ
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2019-10-09
Created 2019-10-09
Last Updated 2019-10-09
Official FullStock Zip is now available.
DEBLOATED
I will be working on a debloated zip in the near future (as soon as I can find a few hours to spare IRL).
In the mean time, there is a trick for a "debloated" PIE install.
1. Clean Flash 20r FullStock (unless you are already on it). Do not reboot.
2. Flash 20r Debloated Image.
3. Flash Magisk, and the RCTD Remover, Opt-Encrypt zips in the 20r thread.
4. Reboot to system, (DO NOT UPDATE ANY APPS) and set things up the way you like them. If any system apps get updated, make sure you uninstall any updates for those apps before step 4
5. Dirty flash 30d, Magisk, and the RCTD Remover and Disable DM-Verity zips in the 30d thread.
The removed system apps should not be installed, and you should have a "debloated" version of 30d on your device.
When I dirty-flashed 30d coming from debloated Oreo, my system was still debloated with the exception of a couple google apps like Duo.
KNOWN ISSUES
1. Broken Lock-Screen after Dirty Flash
Solution = TWRP - Advanced - File Manager - data/system -> Delete lock/pattern settings .db files and gatekeeper files. Reboot and set your lock screen again. FP will not be lost.
Special thanks to:
@ChazzMatt
@immns
@JohnFawkes
@Zackptg5
and thanks for all the support from the xda-developers community.
Personal Update
I have traded my H932 in for the OnePlus 7 Pro (which I am pretty happy with). I will continue to help create zip packages for the H932 in the near future. However, I will not be able to test those zips. Going forward, ill need some help with testing when updates come out, but I will do my best to continue creating packages for everyone.
Yay! Thanks for all you do!
Awesome! Thanks for working on getting these packages put together, @weakNPCdotCom!
PUTTING THIS ON THE FRONT PAGE. From a post later in the thread.
For those who want to dirty flash -- if you have no problems, good for you.
If you find you need to clean flash in TWRP, then follow these steps:
TWRP-FLASHABLE NOTES:
Make sure you are using stable TWRP 3.2.3-7 from post #1.
a. Wipe Data – Factory Reset
b. Install – set storage to the External SD (if you have a microSD card) OR drag necessary files over from PC once in TWRP.
c. Flash the full stock zip.
d. Install the latest stable Magisk zip. (This is to give the encryption disabler root privileges)
e. Install @Zackptg5 Disable_Dm-Verity_ForceEncrypt_08.18.2019 (encryption disabler).
f. Install @JohnFawkes AnyKernel 3 RCTD Remover (root checker disabler); this disables LG's firmware root checks, which may impede performance.
g. FORMAT DATA (Select WIPE, then FORMAT DATA, then select yes.)
Do NOT delete your OS, but you do need to FORMAT your data , not just "wipe" it this time. Otherwise you may get an encryption error when you boot up the first time. If you get any red mount errors, go back to the TWRP reboot menu and select reboot to recovery and try to FORMAT DATA again. Then, after successfully formatting...
h. Reboot – "Reboot Recovery" from TWRP reboot menu (choose to reboot back to Recovery). Now that the data partition has been formatted, TWRP needs to reload the recovery partition for usage. If you skip this step, when Magisk is installed again below, it may think that /data is still encrypted and set "preserve force encryption". This is also a good sanity check that LG encryption has been removed from /data.
i. Re-flash the latest stable Magisk zip again. (This is to make sure, due to Pie changes.)
j. Reboot – to System (NOW you are finally rebooting your phone! Until now this whole section has been done within TWRP.)
STRONG SUGGESTION: After successfully doing all this, when you finally boot back to LG Pie, install an app like this to easily facilitate rebooting to TWRP recovery in the future: Recovery Reboot. Allow it root privileges when asked by Magisk and put icon shortcut on your desktop.
{
"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"
}
ChazzMatt said:
Yes, we all know what it says!
---------- Post added at 10:55 PM ---------- Previous post was at 10:45 PM ----------
Need to update the encryption disabler and root check remover files, please. We found we needed newer versions for Pie.
Click to expand...
Click to collapse
Thank you for this. I did run into a problem dirty flashing due to Force Encryption, but i have confirmed clean flash works. I will update the package files you mentioned prior to publishing the link.
@ChazzMatt I cannot find a newer RCTD disabler release than 2017.
weakNPCdotCom said:
@ChazzMatt I cannot find a newer RCTD disabler release than 2017.
Click to expand...
Click to collapse
@JohnFawkes recently made root check remover for us.
@Zackptg5made the new encryption disabler.
See attachments at this link for both new encryption disabler and root check remover:
https://forum.xda-developers.com/showpost.php?p=79972563&postcount=107
Also here's @JohnFawkes thread link:
https://forum.xda-developers.com/lg-v30/development/stock-anykernel-3-rctd-remover-t3953692
so people can download themselves if they wish.
In most posts I include both attachment, credit and thread link when possible.
I'm using TWRP version 3.2.3-7. Is there a newer version that is required to flash Pie or is that one fine?
weakNPCdotCom said:
@ChazzMatt I cannot find a newer RCTD disabler release than 2017.
Click to expand...
Click to collapse
How do I download the new update?
Sent from my LG-H932 using XDA Labs
jsgraphicart said:
I'm using TWRP version 3.2.3-7. Is there a newer version that is required to flash Pie or is that one fine?
Click to expand...
Click to collapse
that version is perfect
BROKEN1981 said:
How do I download the new update?
Sent from my LG-H932 using XDA Labs
Click to expand...
Click to collapse
I just updated the FullStock link in the OP
jsgraphicart said:
I'm using TWRP version 3.2.3-7. Is there a newer version that is required to flash Pie or is that one fine?
Click to expand...
Click to collapse
No, that's what is recommended by our TWRP dev -- who also creates TWRP flashable zips.
Iam on liquid now, can I jump to stock via clean flash?
Thanks very much
The smoothest update ever for h932
weakNPCdotCom said:
that version is perfect
I just updated the FullStock link in the OP
Click to expand...
Click to collapse
Thank you!!
Sent from my LG-H932 using XDA Labs
Works great! thanks. There was no need to wipe nor format anything.
Almost done reinstalling all my apps, seems great! Thank you!
Anyone else having issues with pie? I'm getting system UI stops responding non stop.
Want to mention that this happens when first booting up to even when all apps are installed.
Successfully dirty flashed from stock 20s. Just remember to delete gatekeeper/lock database (instruction).
ReddotCleaner said:
Iam on liquid now, can I jump to stock via clean flash?
Click to expand...
Click to collapse
clean install using full stock zip will do just fine. follow #1 page instruction
BROKEN1981 said:
Anyone else having issues with pie? I'm getting system UI stops responding non stop.
Click to expand...
Click to collapse
please provide more information. did you come from stock 20s or other os? dirty/clean flashed? do you have any xposed things?
I did uninstall any xposed module and framework, and even delete all magisk module as I assume they will break on pie due incompatibility.
immns said:
snip.
Click to expand...
Click to collapse
I got everything set up. Don't know what the trouble was. I was clean flashing. I formatted data, reinstalled TWRP, installed 30D over 10 times.
Whatever the issue was, it's fixed now.
HOWEVER!!! T-Mobile hid where they put the boot animations. It's no longer in root-system-media.
If anyone finds the location, please post it.
Sent from my LG-H932 using XDA Labs
Hi all. Hope you are good and safe from Covid-19.
If you like TWRP as your recovery and want to keep root access as well, I am going to show you how to do that. Because if you take the stock boot.img and patch it via magisk, you will lose TWRP as your recovery and if you flash TWRP then you will lose root access. For the advance users, they probably already know how to do this but I haven't seen any guides so I am creating one myself.
Disclaimer:
I am a Textile engineer and do not have the slightest idea about computer engineering but my passion for computers and gadgets has taught me all this.
So, if anything happens to your device, it's not on me. I have done this on my device and it worked, so I am sharing this knowledge with you guys.
Let's cut to the chase and start our work:
Before we start, I am hoping you have your bootloader unlocked and have previous experience on flashing roms.
Step 1: Installing Stock/Xiaomi.EU/Custom rom
Go ahead and install one for your favorite roms from the threads. Luckily, Poco F3 has so many roms to choose from and they're all good.
Step 2: Installing magisk.apk
Install Magisk.apk from here
Step 3: Installing TWRP
Install TWRP from @vasishath's thread. (You'll lose root access if you had any).
Step 4: Backing up your boot image
- Boot into TWRP recovery and select backup.
{
"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"
}
- Tick on boot and untick rest of the boxes.
- This will create 3 files in your TWRP folder on the phone. "boot.emmc.win" is your main file that you want to patch via magisk.
- After creating a backup of your boot image, boot into system normally.
Step 5: Patching the backed up boot image
- Open Magisk app and tap on install next to magisk.
- Now select "Select and Patch a file".
- Go ahead and select the boot.emmc.win file that is in your TWRP folder created earlier via TWRP backup.
- This is patch the boot.emmc.win and name it something like "magisk_patched-23000_randomalphanumeric.img"
- Rename the file via any file explorer to boot.img because something when the phone is plugged into the pc, your pc can't read the file. So, just to be safe, unplug the phone and re-plug to read the drive again.
- Copy this boot.img and take it to the folder where fastboot is installed/saved.
Final Step: Flashing the boot.img
- Reboot your phone to fastboot mode via pressing and holding the volume down + power buttons (or if you have custom roms installed and have the option to boot into fastboot mode directly).
- Once in fastboot mode, type following to flash the boot.img
fastboot flash boot boot.img
Click to expand...
Click to collapse
- once the flashing is done (in about 5-10 seconds), type the following:
fastboot reboot
Click to expand...
Click to collapse
Congratulations! you now have TWRP installed as your recovery and have root access as well. To verify this you should have the below screen in your magisk app
If my guide helped you in any way, please do like it as it motivates me to write more guides to take my time out from my busy work life.
Thanks.
Very detailed and comprehensive guide indeed, however I just unlocked my almost a week now. Initially, I have 3 choices on how I will run my device after unlocking bootloader.
Either I use XiaoMi.EU testing non-root, AOSP non-root or worse can scenario I'll root and run it on stock firmware.
No I do not think that F3 users are lucky, instead I think the reality is the trend of really good coders and programmers have past. You think F3 have a huge variety of custom roms to choose? 90%+ above are based on AOSP, which I don't understand why we have 10+ AOSP roms, with only 1-2 difference. It's such a waste of time. They are only interested in making new custom roms, never in maintaining them. Always abandon project and go missing after a while. This generation is full of "enthusiasts", "wanna-be" developers most noticeable after POCO entered India's market. You can try search in YouTube, poco f3 then you will get 70-80% of tech/mobile influencers with tons of guides. The sad part is, most of them are literally talking about the same stuff, and what I hate the most they love to decorate their website with tons of ads.
Hi,
thanks for your guide I really needed it because I already have custom ROM, root, Magisk... but TWRP I used to start it from the computer every time I needed it.
If I follow your method I don't lose the installed apps and my data, right?
pegasoc said:
Hi,
thanks for your guide I really needed it because I already have custom ROM, root, Magisk... but TWRP I used to start it from the computer every time I needed it.
If I follow your method I don't lose the installed apps and my data, right?
Click to expand...
Click to collapse
No, you won't lose your data.
regedit12345 said:
...
Step 3: Installing TWRP
Install TWRP from @vasishath's thread. (You'll lose root access if you had any).
...
Click to expand...
Click to collapse
Hi,
to be sure I understand correctly, at point 3 where there is to install the TWRP I always started the TWRP from PC I do not have to do it again, right?
pegasoc said:
Hi,
to be sure I understand correctly, at point 3 where there is to install the TWRP I always started the TWRP from PC I do not have to do it again, right?
Click to expand...
Click to collapse
Yeah, once you boot from pc and "install current twrp", you dont have to do it again.
When i have bootloader unlocked how do i flash xiaomi.eu rom without twrp installed?
__halvar__ said:
When i have bootloader unlocked how do i flash xiaomi.eu rom without twrp installed?
Click to expand...
Click to collapse
You have to install TWRP through fastboot, look for a guide, there's a couple
still works like a charm
thank you for the guide!
I already have xiaomi.eu and TWRP installed but my first time installing Magisk on this device.
do I have to wipe /data ?
katcj said:
thank you for the guide!
I already have xiaomi.eu and TWRP installed but my first time installing Magisk on this device.
do I have to wipe /data ?
Click to expand...
Click to collapse
No. Just install magisk.apk and patch the boot image extracted via twrp and go ahead and flash it.
regedit12345 said:
No. Just install magisk.apk and patch the boot image extracted via twrp and go ahead and flash it.
Click to expand...
Click to collapse
PLEASE stop patching the BOOT image
.
.
.
DIRECT INSTALL (Recommendend) is the option on your screen.
that's all you needed.
and your TWRP is OLD
please, use new officel TWRP from
and there you will find the correct instructions for installing TWRP
[RECOVERY] [12] [OFFICIAL] TeamWin Recovery Project
Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added...
forum.xda-developers.com
Thank you for taking your time to contribute value to community resources!
There seem to be so many different guides and methods
I followed nebrassy's guide for TWRP
0. miflash latest stock -> flash desired rom
1. fastboot boot twrp.img (3.6 official)
2. advanced -> flash current twrp (now its permanent)
3. flash latest magisk alpha zip (usb otg or put in storage pre fastboot)
4. reboot.. launch magisk app -> update -> direct install -> reboot
5. profit
Hello. Could you help me with rooting my phone, please?
I'm on Xiaomi.eu 21.12.8 (the last android 12 weekly update). I tried flashing Magisk.zip with the TWRP but it didn't work at all.
It's like I never flashed it. So I decided to try your method to see if it would go any different, and it didn't.
I could root Evolution X (android 12), ArrowOS 11 and 12 with this method of flashing Magisk.zip on TWRP but I can't understand why it didn't worked on Xiaomi.eu 21.12.8. I could even root Xiaomi.eu 21.9.17, which was the last android 11 weekly update.
Desperate, I went to the "advanced" section of TWRP and there was an option of "Flash magisk alpha" and it ended up rooting the phone but I don't understand why the previous 2 methods didn't work.
Could you help me understand that?
Root only works with magisk canary in Android 12
Latest Magisk Canary release adds support for Android 12, drops MagiskHide
The newest update on Magisk's "bleeding edge" canary release channel brings in support for Android 12 and the new Zygisk feature. Read on!
www.xda-developers.com
Thank you!!
Using canary worked on xiaomi.eu, although, I still cannot understand why using the magiskv23.apk can root aosp android 12 rom but not xiaomi.eu android 12, if you could explain me, I'd greatly appreciate it.
Also, canary seems to have the magiskhide function removed, is there a way to hide it for certain apps (banks, mostly) with a module or is it disabled permanently now?
Wiilsoonj said:
Thank you!!
Using canary worked on xiaomi.eu, although, I still cannot understand why using the magiskv23.apk can root aosp android 12 rom but not xiaomi.eu android 12, if you could explain me, I'd greatly appreciate it.
Also, canary seems to have the magiskhide function removed, is there a way to hide it for certain apps (banks, mostly) with a module or is it disabled permanently now?
Click to expand...
Click to collapse
yes the new "hide" is zygisk in the options
How do I flash the canary version of magisk though? I have an A12 rom on my F3. I can't flash it in TWRP as I can't mount any partitions to see the file. And I can't flash it via adb sideload as it crashes my TWRP immediately.
Any advice or suggestions? Thanks.
Aceyalone said:
How do I flash the canary version of magisk though? I have an A12 rom on my F3. I can't flash it in TWRP as I can't mount any partitions to see the file. And I can't flash it via adb sideload as it crashes my TWRP immediately.
Any advice or suggestions? Thanks.
Click to expand...
Click to collapse
Either use usb OTG.
Aceyalone said:
How do I flash the canary version of magisk though? I have an A12 rom on my F3. I can't flash it in TWRP as I can't mount any partitions to see the file. And I can't flash it via adb sideload as it crashes my TWRP immediately.
Any advice or suggestions? Thanks.
Click to expand...
Click to collapse
You can use this TWRP.
Download this: twrp-3.6.0_11-v3.2_A12-alioth-skkk.img
From this link: https://androidfilehost.com/?w=files&flid=322193
This one is able to see the internal storage of the phone with android 12. But you need to remove your screen lock to do so, you must not have a password set up so TWRP can see your internal storage, then just flash magisk normally and afterwards set up your screen lock again. Everytime you want to see the internal storage, disable screen lock. Also, you could follow the tutorial in the first post, but instead of making a backup of boot with TWRP, just use boot.image from the desired ROM, patch it with magisk and then flash the boot using adb.
Hope it helps.
- WARNING -
This Guide is not failproof, if you do anything wrong with your device while following this guide, i won't be held responsible if you brick or hard damage your device. I insist about that but you must extract all of your data (Photos, Videos, Music, Apps, Accounts, Messages, ETC) Before proceeding or else you will end up with a loss of data, again i'm still not responsible if you lose all of your data without backing up. I WARNED YOU.
Well, you have a Galaxy S6 edge+ lying around and you want to get back to Lolipop? You want to downgrade? Well then you're in the right place!
So......downgrading to lolipop...... some people claimed it can be done by deleting some file in the odin .tar but that never worked for me.
If you have the sw rev check fail error upon downgrading....this is the guide for you!
This will wipe all your data including internal storage (depending on how you do it)
Confirmed working on my Galaxy S6 edge+ SM-G928F [It should work on Note5 but no promises from now on]
Advantages :
Downgrade procedure is safe, simple.
Your phone should boot faster
battery life should last longer [i said it should]
You can get the animated lock screen animations back.
Get old touchwiz back. [i like the 5.1.1 version]
disadvantages:
1. You cannot boot TWRP while on the downgraded bootloader
2. You will only have system-wide root. DO NOT flash systemless or it will not boot (but nobody cares)
3. Fingerprint is not working (still working on that)
4. You can only flash stock nougat from odin. You cannot flash lolipop, marshmallow tar,twrp tar,cf auto root tar or anything else [except if you have a combination firmware]
Ok, let's get started.
Requirements :
A laptop or home PC : At least running Windows 8/8.1 or Windows 10
Your device
Genuine Samsung charging cable [NOT SPONSERED]
Stable internet connection.
Files :
The lastest SAMSUNG Drivers which can be found here : https://developer.samsung.com/android-usb-driver
Odin3 : https://www.samsungodindownload.com/fr/download-for-windows
The firmware you want to downgrade to : I will link my ROM so u can install it.
TWRP [Newest version] : https://twrp.me/samsung/samsunggalaxys6edgeplus.html
Classy Kitchen [for bulding your rom] : https://forum.xda-developers.com/t/...kitchen-for-android-roms-development.3862584/
Now let's get started!
Let's start first by cooking the ROM! Open Classy Kitchen, and then open the ROM you want to use :
{
"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"
}
Normally the first time you open the program, there shouldn't be any project [except if you used this app before]
Next click "Create new project", "From PC (Browse for one)"
And then chose the path where you saved your firmware. After chosing your firmware, Classy Kitchen will open the firmware automaticly.
After the ROM is now open, click on "ROM utils" and then click on "Deodex ROM" After you Deodex the ROM, we will have to de-bloat it.
On Classy Kitchen, click on "Debloat / Re-Bloat ROM" to Debloat your ROM.
Last step [optional] We will have to De-Knox our ROM. (again optional) But De-Knoxing our ROM can save a lot of space in our phone storage. So i recommend you do.
After De-Knoxing our ROM, we will have to disable DM-Verity Force Encryption in order to Boot into the ROM [Otherwise if you don't your phone will never boot]
Click on "Remove DM-Verity / Force Encryption"
Next that we disabled DM-Verity, We will have to remove the "meta-inf installer"
Click on "Re-Build META-INF installer" and click on remove.
Finally once we have done the modifications on our ROM, we just have to save.
Click on "Build (system.new.dat) ROM (for recovery)"
and then we are done cooking our ROM!
But the guide is not done yet. We will have to install TWRP in the phone.
HOW-TO-PROCEED?
Step-1 Press and hold the power button on your device
Step-2 Chose "Power Off"
Wait for your device to completly Shut-Off.
Step-3 Re-Boot in download mode "odin mode"
Step-4 connect the phone to your computer
Step-5 open Odin3
In Odin, we will have to install TWRP, click on the AP box and chose your TWRP file [the one that you downloaded]
Don't forget to disable "Auto-Reboot" after installation, otherwise your phone will re-boot normal into Android.
At this point, Knox is tripped in your device meaning that your warranty is now expired. Also the Knox features are no longer usable.
On TWRP, click on wipe, "Format Data". A keyboard will pop-up, type "yes"
Type "yes"
Once Data Format is completed, hit home, reboot, recovery.
your phone will reboot into recovery again, hit wipe again, this time we won't format data. Instead we're going to wipe the phone's partitions
Chose in TWRP,
Then swipe to wipe. Then hit home again. Next hit "Install"
Install the ROM you just made with Classy Kitchen. It can be found in "Documents" - "Output" - "Your-ROM"
Transfert it to your phone
Click on the ROM / ZIP file and "swipe to confirm flash"
After the flashing procedure is complete, you will have to wipe the "cache" / Dalvik.
Hit "wipe dalvik/cache"
Then "swipe to wipe"
After you wiped the cache, hit "Reboot System" and hit "Do Not Install"
One last step before you get back to Lolipop. You will need a custom Bootloader in order to boot.
Just download my "custom Bootloader" https://drive.google.com/file/d/1207Guvk8J_L9FSJv2C9BpkeLpWkXtViQ/view?usp=drive_link
After you downloaded my "custom bootloader" you will have to install it.
so get Odin3 and install my bootloader!
After the Bootloader installation is complete, you just have to reboot your device, cross your fingers and hope it boots!
Congratuations! You are back on Lolipop! Enjoy!
1 : If you want to flash a mod in TWRP, you will have to put your phone in download mode, install the stock bootloader in BL tab, install TWRP in AP tab and then click on "start"
2 : If you want to get back into marshmallow / Nougat, you just have to flash stock firmware in Odin3
If you have any issues or any questions, you can DM me but it isn't guaranteed that i will reply.
Here are some screenshots of Lolipop :
Here the device i used.
what about system sound because on 6.1.1 (sorry 6.0.1) sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
iskender4444 said:
what about system sound because on 6.1.1 sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
View attachment 5922017
Click to expand...
Click to collapse
Nevermind. This comment is deleted
iskender4444 said:
what about system sound because on 6.1.1 sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
View attachment 5922017
Click to expand...
Click to collapse
Actually
iskender4444 said:
what about system sound because on 6.1.1 sound was weird and glitchy idk why
oh btw i need a access the drive to download bootloader
View attachment 5922017
Click to expand...
Click to collapse
Try download downloading my bootloader again. I made it public
TheWiiGuy said:
Actually
Try download downloading my bootloader again. I made it public
Click to expand...
Click to collapse
Why sound coming like creepy from buzzer only on 6.1.1 interesting..
iskender4444 said:
Why sound coming like creepy from buzzer only on 6.1.1 interesting..
Click to expand...
Click to collapse
Have you downgraded to Lollipop yet?
TheWiiGuy said:
Have you downgraded to Lollipop yet?
Click to expand...
Click to collapse
i had bootloop on samsung galaxy s6 edge plus here the photo:
and can you share the twrp? and is this correct one?
"twrp-3.1.1-0-zenlte.img"
iskender4444 said:
and can you share the twrp? and is this correct one?
"twrp-3.1.1-0-zenlte.img"
Click to expand...
Click to collapse
Yes. This is The Good TWRP. Are you trying to get into recovery? If not then there is a problem with my bootloader
Mind if i upload the New bootloader tomorrow?
iskender4444 said:
i had bootloop on samsung galaxy s6 edge plus here the photo:
Click to expand...
Click to collapse
It looks like the phone is trying to get into stock recovery.
TheWiiGuy said:
It looks like the phone is trying to get into stock recovery.
Click to expand...
Click to collapse
idk and i dont get it why doing this i just re-download twrp official website and still same issue i just flash the twrp but can't enter twrp recovery right know.
iskender4444 said:
idk and i dont get it why doing this i just re-download twrp official website and still same issue i just flash the twrp but can't enter twrp recovery right know.
Click to expand...
Click to collapse
Actually i forgot to mention that you can't boot into TWRP on My custom bootloader. Get back in odin. Re-flash stock bootloader in BL Tab and flash TWRP in the AP Tab. Then try to re-boot onto Custom recovery. Tell me some news.
TheWiiGuy said:
Actually i forgot to mention that you can't boot into TWRP on My custom bootloader. Get back in odin. Re-flash stock bootloader in BL Tab and flash TWRP in the AP Tab. Then try to re-boot onto Custom recovery. Tell me some news.
Click to expand...
Click to collapse
Oh yes. Have you backed up all of your partitions on TWRP?
TheWiiGuy said:
Oh yes. Have you backed up all of your partitions on TWRP?
Click to expand...
Click to collapse
i solved twrp but can't boot same as issue on picture
iskender4444 said:
i solved twrp but can't boot same as issue on picture
Click to expand...
Click to collapse
So you can boot onto TWRP ?
OK. I see the problem.
I Will upload my New bootloader tomorrow.
The current bootloader does not allow to Boot onto TWRP and it can't boot into stock recovery either.
Hopefully the New bootloader should fix your problem. It has stock recovery
TheWiiGuy said:
So you can boot onto TWRP ?
OK. I see the problem.
I Will upload my New bootloader tomorrow.
The current bootloader does not allow to Boot onto TWRP and it can't boot into stock recovery either.
Hopefully the New bootloader should fix your problem. It has stock recovery
Click to expand...
Click to collapse
i have another problem i was trying to flash stock 7.0 rom but gives error same like this.
iskender4444 said:
i have another problem i was trying to flash stock 7.0 rom but gives error same like this.
Click to expand...
Click to collapse
Nevermind this comment is deleted
TheWiiGuy said:
What is your phone model number? I see you are installing firmware for a sm-g780f.
Click to expand...
Click to collapse
no this is for example man mine was g928c