Related
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
EASY ROOT/UNROOT FOR S7 OR S7E ALL NOUGAT OR OREO STOCK ROMS
THANKS @klabit87 FOR OREO ROOT
TEMPORARY TWRP RECOVERY VIA ADB THANKS TO @afaneh92
This is for AT&T, T-Mobile and Verizon and Sprint running V4 bootloaders only!
This tool will allow you too easily root any stock rom allowing you to make any modifications you might want then easily unroot for better performance
This will Also give you a fully functional TWRP recovery that can be accessed via adb. TWRP is fully functional on OREO Roms but is limited on Nougat roms
The initial setup does require a data wipe.
S7 G930A Flat Odin Factory FIrmware Downloads
G930AUCU4CRI2_8.0_4File_USA (AT&T).7z
ADB_Root Temporary Twrp Tool Download
S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z
S7 G935 Edge Root/Unroot Odin Files Downloads
These Files Are Needed To Unroot Your Phone
SM_G935_EDGE_OREO.7z
SM_G935_EDGE_NOUGAT.7z
S7 G930 Flat Root/Unroot Odin Files Downloads
These Files Are Needed To Unroot Your Phone
SM_G930_FLAT_OREO.7z
SM_G930_FLAT_NOUGAT.7z
Instructions
1. Download S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z and your model and version you want from above
2. Unzip S7_S7E_ROOT_UNROOT_ADB_TOOLS.7z to S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
3. Unzip the Model/Version file you downloaded and copy the files to the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and place them in the Odin folder
4. Prepare your phone for a data wipe
5. Reboot your phone to download mode and flash the AP_ROOT_G93*.tar in the Odin AP slot and reboot your phone to recovery
6. Once phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
7. Now in the cmd window make sure your device is connected and choose Option (1) Launch TWRP
8. Your phone should launch TWRP leave phone plugged in and command window open on computer
9. Now In Twrp choose wipe and choose format data. Type yes in the box when it ask
10. Now in cmd window choose Option(8) Push Root.zip to Phone
11. Now in TWRP choose install and select the Root.zip
12. After zip is installed reboot and go through setup.
13. Once through setup make sure you are rooted
To Unroot Your Phone
1. In the Root Control app choose phone settings and unroot phone make sure phone is connected to computer
2. Now depending on the type of root you choose your phone will reboot to download if you chose system root or stock recovery if you chose systemless root. If your phone reboots to download mode skip to number 5
3. If your phone reboots to recovery once your phone is in recovery run the Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder
4. In cmd window choose Option(3) Unroot phone will reboot too download mode
5. In Odin BL slot choose the BL_G93*_DELETE_CACHE.tar and flash phone will reboot to recovery and say processing update then get an error and strart rebooting recovery
6. Let recovery bootloop at least once thin force phone back to download mode
7. In Odin AP slot flash BL_ENTER_ENG_RECOVERY_G93*.tar and flash phone will reboot to recovery with a bunch of red cache errors
8. In recovery choose wipe cache then reboot back to bootloader from recovery
9. In Odin BL slot choose BL_OREO_STOCK_G93*.tar for Oreo or BL_RESET_DM_VERITY_G93*.tar for Nougat and flash
10. This is important as soon as odin is done flashing and phone powers off immediately hold buttons to force phone to recovery
11. When phone reboots to recovery you will get no command error then when phone shows recovery options in black box at very botton it should say Successfully verified. If it says unsuccessful or failed then start at number 5 again. If successful and on oreo you are done.
12. If on Nougat and successful from recovery reboot to bootloader in Odin BL slot flash BL_NOUGAT_STOCK_G93*.tar
To Reroot Your Phone
1. Reboot to download in Odin AP slot flash AP_ROOT_G93***.tar
2. Phone will reboot then will reboot one more time and you will be rerooted
To Enter TWRP When Rooted
Remember with Nougat TWRP cannot mount data because of encryption so some zips wont work
1. Manually reboot phone to recovery launch Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and choose Option(1) Launch TWRP
2. To Exit TWRP simply choose reboot
To Enter TWRP When Unrooted
Remember with Nougat TWRP cannot mount data because of encryption so some zips wont work
1. Put phone in download mode In Odin AP slot flash AP_ROOT_G93***.tar force phone to reboot to recovery. If you let phone boot it will reroot and you will have to run the unroot from the root control app.
2. In recovery launch Setup.exe in the S7_S7E_ROOT_UNROOT_ADB_TOOLS folder and choose Option(1) Launch TWRP.
3. Do whatever you need too do
4. To exit Twrp choose reboot to Download
5. In Odin BL slot choose the BL_G93*_DELETE_CACHE.tar and flash phone will reboot to recovery and say processing update then get an error and strart rebooting recovery
6. Let recovery bootloop at least once thin force phone back to download mode
7. In Odin AP slot flash BL_ENTER_ENG_RECOVERY_G93*.tar and flash phone will reboot to recovery with a bunch of red cache errors
8. In recovery choose wipe cache then reboot back to bootloader from recovery
9. In Odin BL slot choose BL_OREO_STOCK_G93*.tar for Oreo or BL_RESET_DM_VERITY_G93*.tar for Nougat and flash
10. This is important as soon as odin is done flashing and phone powers off immediately hold buttons to force phone to recovery
11. When phone reboots to recovery you will get no command error then when phone shows recovery options in black box at very botton it should say Successfully verified. If it says unsuccessful or failed then start at number 5 again. If successful and on oreo you are done.
12. If on Nougat and successful from recovery reboot to bootloader in Odin BL slot flash BL_NOUGAT_STOCK_G93*.tar
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
jrkruse said:
Beware If you update to new V8 bootloader then rooting and everything will not work. You will be stuck on stock possibly for good
Click to expand...
Click to collapse
It is not possible to install Magisk, because he is installing his own boot.img and i will be stuck at bootloop? Everything is working by the way, many thanks, but i flashed Viper4Android, it doesn't work, asks for drivers all the time.
Brilliant! Many thanks as I just got this device a few days ago so the timing on this guide is perfect! I had a little trouble after I flashed the BL_ENG_BOOTLOADERS where it constantly boot-looped but once I was able to get it back into download mode (holding volume down, home button, and power button) and start again from step 5 of the unrooting process everything worked according to plan then. I'm happy to announce I've rooted, customized, and unrooted thanks to the simple ease in which this method works so many thanks to jrkruse!
SCUZZY1337 said:
It is not possible to install Magisk, because he is installing his own boot.img and i will be stuck at bootloop? Everything is working by the way, many thanks, but i flashed Viper4Android, it doesn't work, asks for drivers all the time.
Click to expand...
Click to collapse
If you just download viper4 android in xda labs store and install drivers via the app it works fine
Sent using some kind of device I modified
jrkruse said:
If you just download viper4 android in xda labs store and install drivers via the app it works fine
Sent using some kind of device I modified
Click to expand...
Click to collapse
Will try, thank you, magisk ain't work right?
---------- Post added at 07:21 PM ---------- Previous post was at 07:12 PM ----------
jrkruse said:
If you just download viper4 android in xda labs store and install drivers via the app it works fine
Sent using some kind of device I modified
Click to expand...
Click to collapse
The app is installing the driver for ages and never stops, why?
SCUZZY1337 said:
Will try, thank you, magisk ain't work right?
---------- Post added at 07:21 PM ---------- Previous post was at 07:12 PM ----------
The app is installing the driver for ages and never stops, why?
Click to expand...
Click to collapse
Reboot your phone
jrkruse said:
Reboot your phone
Click to expand...
Click to collapse
Installed thru twrp, works perfectly.
Added ATT factory firmware to the OP
jrkruse said:
Added ATT factory firmware to the OP
Click to expand...
Click to collapse
What?
SCUZZY1337 said:
What?
Click to expand...
Click to collapse
What is your what for. I didnt know adding factory firmware to OP needed an explanation
Sent using some kind of device I modified
jrkruse said:
What is your what for. I didnt know adding factory firmware to OP needed an explanation
Sent using some kind of device I modified
Click to expand...
Click to collapse
Is it possible to install magisk?
SCUZZY1337 said:
Is it possible to install magisk?
Click to expand...
Click to collapse
No it is not
Sent using some kind of device I modified
jrkruse said:
No it is not
Sent using some kind of device I modified
Click to expand...
Click to collapse
Could you please tell me the difference between V4 and V8 bootloaders?
SCUZZY1337 said:
Could you please tell me the difference between V4 and V8 bootloaders?
Click to expand...
Click to collapse
Yes v8 bootloaders means the party is over enjoy totally stock because you are not rooting or anything else unless a v8 eng boot gets released and i doubt it because v5 v6 and v7 never got released
Sent using some kind of device I modified
jrkruse said:
Yes v8 bootloaders means the party is over enjoy totally stock because you are not rooting or anything else unless a v8 eng boot gets released and i doubt it because v5 v6 and v7 never got released
Sent using some kind of device I modified
Click to expand...
Click to collapse
Idk i hav V4 and i dont have any lags, everything runs super smooth.
Bonjour,
Il est impossible de télécharger le fichier file:///C:/Users/Yves%20local/Downloads/S7_S7E_ROOT_UNROOT_ADB_TOOLS(1).7z. Le téléchargment démare et puis echec impossible de télécharger???
Merci de votre aide et bravo pour votre travail.
pyveswebsud said:
Bonjour,
Il est impossible de télécharger le fichier file:///C:/Users/Yves%20local/Downloads/S7_S7E_ROOT_UNROOT_ADB_TOOLS(1).7z. Le téléchargment démare et puis echec impossible de télécharger???
Merci de votre aide et bravo pour votre travail.
Click to expand...
Click to collapse
English is required use on xda. Please translate to English
Sent using some kind of device I modified
how compatible do you think this would be with the s7active (native to AT&T carrier) ?
especially now the S7active has recently been updated to Oreo, which also updated its bootloader to v4 ...
worth a go ?
miniminus said:
how compatible do you think this would be with the s7active (native to AT&T carrier) ?
especially now the S7active has recently been updated to Oreo, which also updated its bootloader to v4 ...
worth a go ?
Click to expand...
Click to collapse
Unless you have an eng recovery for oreo for the active and an eng boot.img for oreo you won’t be able to do anything
Sent using some kind of device I modified
LG Joan H933 GLOBAL CANADA 20i ROM
DO NOT USE THIS ZIP FOR CONVERTING YOUR MODIFIED TO US998 PHONE BACK TO H933!
Your phone needs to be on H933 software with TWRP kept via LGUP partition dl mode (leaving recovery partition out when flashing kdz). Have a look at the second post, @cloud1250000 wrote a guide for that with an massive amount of help from @christopherrrg.
Also, there's a Telegram Group Chat available for H933 users only, for sorting out eventually arising problems:
LG V30 H933 Canada
Hi!
This Rom is 100% Stock. Most recent TWRP should first be installed. Then you can install this Rom and have Oreo with working TWRP.
This zip is created from the original KDZ. It contains almost the complete 20i firmware, but the partition table rewriting part and recovery image (beside five to eight other images) is removed. I changed the system.img, so you do not have to reinstall TWRP (recovery-from-boot.p deleted) when ROM once booted. I also changed the partition size of system.img, so the vendorized people can install this too without having problems because of a too small system partition.
This is a continuation of westwood24's idea and work, I've updated it to the newest fw version and edited it a bit. I followed his idea and made this for users who can not take OTA's because they have Custom Recovery / Root installed.
Features
Stock build made from official KDZ
Stock Build.prop
Unrooted
system.img modified to keep TWRP
System image size shrunk for being able to flash this on a smaller system partition, mainly caused by vendorizing
Removed dm-verity
Removed rctd (LG's root checker tool daemon)
Enabled opt-encrypt, it's your choice now if you want to encrypt your phone, it's no more forced. TWRP now is capable of decryption (both AOSP and stock) since a few versions
VoLTE and VoWiFi critical OP partition separate download, flashable via TWRP (Download / MD5: add01810ddb6da99ace26645acfb5d97)
Separate OP Partition download available here
Installation
What you need
Unlocked Bootloader[/URL]
Working TWRP installed [Link to newest unofficial TWRP]
When you need Root, flash latest Magisk afterwards [Download]
The zip!
How to install
When you are still on Nougat,
you should start fresh: Reboot to recovery using button combo or reboot app (needs root; btw, Magisk offers this possibility too: Menu -> Modules -> three dot menu top right - Reboot to recovery)
Then flash this latest TWRP.img via image flashing function in TWRP, reboot to recovery again (for fully working new recovery) and do a backup, then copy this backup to your PC.
Then initiate a factory reset. Wipe your system partition too in TWRP advanced wiping menu, copy the 20i firmware zip to your SD and install it. Reboot and enjoy
From Oreo:
For clean install: Factory reset and wipe system
You can also keep your data by simply dirty flashing the zip. *Be aware that problems may occure, maybe you need to do a factory reset to start fresh*
Flash the 20i zip, then Magisk zip when you need root, then reboot to System = you're DONE
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no (in newest TWRP SU is disabled, and the option to install the TWRP app is disabled too.)
Just give a thanks if you like the zip! :good:
@christopherrrg wrote a "little guide" for the peoples, who may ever have thought about going back to h33 original (rooted or not) sw. Give him some thanks pls, he's now a few nerves lost in this procedure i can imagine :good: thanks!
Here it is:
Okay so the steps below are for AFTER using the WTF thread to convert device and unlock bootloader; these steps are for canadian model users who would prefer to go back to stock canadian kdz with working root and twrp intact.
Step 1 - Attach converted US998 (bl unlocked and twrp installed) to LGUP.
Step 2 - PARTITION DL the canadian kdz but do not include recovery.
Step 3 - Let phone boot right from kdz flash and it will automatically boot TWRP.
Step 4 - While in TWRP; 1st factory reset AND AFTER format data then reboot recovery. (If not done TWRP has mount issues with cache and or system.)
Step 5 - After TWRP is rebooted flash no-verity-opt-encrypt-6.0.zip + lg-rctd-disabler-1.0.zip and afterwards flash magisk.
Step 6 - While still in TWRP use the option to power device down.
Step 7 - Attach device to PC while holding vol+ and it will automatically start download mode.
Step 8 - PARTITION DL the canadian kdz again EXCEPT uncheck everything BUT stock recovery; let it flash and reboot.
Step 9 - Should reboot 3 - 4 times.
Step 10 - Once booted to setup; get past then activate USB debugging, also open magisk and click yes as many times as it asks you. (Magisk remains because only RECOVERY is flashed at this point)
Step 11 - Download TWRP and rename to just twrp then place it in the root directory of your internal storage.
Step 11 - Connect device to android debug bridge, and start a shell with 'adb shell' command.
Step 12 - then type 'su' and hit enter in order to gain root privilege. (Will have to click accept on super user on device)
Step 13 - then type 'dd if=/sdcard/twrp.img of=/dev/block/bootdevice/by-name/recovery'
If done correctly you should see flashing (almost like fastboot) however you will not have anything happen to your device graphically SO open magisk and click modules then click reboot to recovery and profit!
You should be on H933 kdz with TWRP and root.
However for some weird reason, cloud is correct as the battery drain is abysmal. My phone used to go from 9am 100% to about 60% by the time I get home at 5pm. Today it's gone down to 22% from 100% at 9am and it's only 2pm. @cloud1250000's brain was mostly picked for this so he deserves any and all credit; I just confirmed and wrote this up for reference.
Enjoy!
Credits to @cloud1250000
hey, it's cold out there, what about a chilled-out evening on an open fire and flashing new software on your phone...? a tester is welcome this doesn't brick your phone...
I edited this right out. For my excitement I skipped almost every single thing in the thread and I apologize however I'm willing to test and will report my findings right away!
ok, link follows via pm :good:
christopherrrg said:
I edited this right out. For my excitement I skipped almost every single thing in the thread and I apologize however I'm willing to test and will report my findings right away!
Click to expand...
Click to collapse
Someone else PM'ed me so we have two testers.
seadersn said:
LG Joan H933 GLOBAL CANADA 20G ROM
DO NOT USE THIS ZIP FOR MODEL CONVERSIONS!Hi!
This Rom is 100% Stock. Most recent TWRP should first be installed. Then you can install this Rom and have Oreo with working TWRP.
This needs testing first, please hit me a PM for getting the link.
This zip is created from the original KDZ (H93320g_00_OPEN_CA_OP_0910.kdz). It contains almost the complete 20G firmware, but the partition table rewriting part and recovery image (beside five to eight other images) is removed. I changed the system.img, so you do not have to reinstall TWRP (recovery-from-boot.p deleted) when ROM once booted. I also changed the partition size of system.img, so the vendorized people can install this too without having problems because of a too small system partition.
This is a continuation of westwood24's idea and work, I've updated it to the newest fw version and edited it a bit. I followed his idea and made this for users who can not take OTA's because they have Custom Recovery / Root installed.
Features
Stock build made from official KDZ
Stock Build.prop
Unrooted
system.img modified to keep TWRP
System image size shrunk for being able to flash this on a smaller system partition, mainly caused by vendorizing
Removed dm-verity
Removed rctd (LG's root checker tool daemon)
Enabled opt-encrypt, it's your choice now if you want to encrypt your phone, it's no more forced. TWRP now is capable of decryption (both AOSP and stock) since a few versions
Installation
What you need
Unlocked Bootloader [How to do]
Working TWRP installed (should be installed already, otherwise you wouldn't need this zip )[Link to newest unofficial TWRP]
When you need Root, Latest Magisk [Download]
The zip!
How to install
When you are still on Nougat,
you should start fresh: Reboot to recovery using button combo or reboot app (needs root; btw, Magisk offers this possibility too: Menu -> Modules -> three dot menu top right - Reboot to recovery)
Then flash this latest TWRP.img via image flashing function in TWRP, reboot to recovery again (for fully working new recovery) and do a backup, then copy this backup to your PC.
Then initiate a factory reset. Wipe your system partition too in TWRP advanced wiping menu, copy the 20G firmware zip to your SD and install it. Reboot and enjoy
From Oreo:
For clean install: Factory reset and wipe system
You can also keep your data by simply dirty flashing the zip. *Be aware that problems may occure, maybe you need to do a factory reset to start fresh*
Flash the 20G zip, then Magisk zip when you need root, then reboot to System = you're DONE
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no (in newest TWRP SU is disabled, and the option to install the TWRP app is disabled too.)
Rom Version
Android Version: 8.0 Oreo
Android security patch level: 2018-09-1
Just give a thanks if you like the zip! :good:
You want to help me with a [donation?] Not asking for it, I have fun doing this for you, but feel free...
Click to expand...
Click to collapse
Please can you explained me something, you wrote DO NOT USE THIS ZIP FOR MODEL CONVERSIONS!, but we must convert the H933 to US988 in order to install TWRP and root. So now I can install it, go back from US988 to H933 and keep TWRP and root ?
Thanks
so actually; as the above user is mentioning I attempted a partition DL flash of the kdz minus recovery and it constantly boots to recovery after flash (which i'm sure is totally normal as stock will not boot with custom recovery without no verity etc) buuuuut my stupid behind didn't flash those and assumed it would not work so decided to panic and flash the us998 kdz back in order to restore my backup and I think I screwed up my download mode as it now shows download mode for 2 seconds then reboots right into recovery; I believe I may have corrupted my laf partition and am now currently working on getting back to a functioning device; luckily the bootloader is still unlocked and I can still flash things as system and data both mount no problem.
my apologies for the lengthly message but or anyone else who is planning to test please remember if you're flashing back from US998 to H933 not to do as i've done and remember no verity etc so it can at least boot so you can THEN flash this zip here.
after all of that i've still got nothing to report as flashing it seems to look great but because I kdz back to us998 i'm afraid to use this zip until I get a booting phone again; also please dont take this as me flaming or anything. i'm sure i'll fix my device with fastboot soon and shall resume testing.
christopherrrg said:
so actually; as the above user is mentioning I attempted a partition DL flash of the kdz minus recovery and it constantly boots to recovery after flash (which i'm sure is totally normal as stock will not boot with custom recovery without no verity etc) buuuuut my stupid behind didn't flash those and assumed it would not work so decided to panic and flash the us998 kdz back in order to restore my backup and I think I screwed up my download mode as it now shows download mode for 2 seconds then reboots right into recovery; I believe I may have corrupted my laf partition and am now currently working on getting back to a functioning device; luckily the bootloader is still unlocked and I can still flash things as system and data both mount no problem.
my apologies for the lengthly message but or anyone else who is planning to test please remember if you're flashing back from US998 to H933 not to do as i've done and remember no verity etc so it can at least boot so you can THEN flash this zip here.
after all of that i've still got nothing to report as flashing it seems to look great but because I kdz back to us998 i'm afraid to use this zip until I get a booting phone again; also please dont take this as me flaming or anything. i'm sure i'll fix my device with fastboot soon and shall resume testing.
Click to expand...
Click to collapse
Thanks for the update, good luck recovering the phone. Maybe ou can try LG software from recovery ....
[email protected] said:
Please can you explained me something, you wrote DO NOT USE THIS ZIP FOR MODEL CONVERSIONS!, but we must convert the H933 to US988 in order to install TWRP and root. So now I can install it, go back from US988 to H933 and keep TWRP and root ?
Thanks
Click to expand...
Click to collapse
Yes you must be on a global Canadian kdz that is BEFORE this version.
when you convert back make sure you use partition DL and uncheck recovery; then when you flash canadian kdz and boot up flash dm no verity and the other zip to make stock kdz boot with twrp still intact; then once system boots at least once you reboot into twrp with the master reset combo and then use the zip provided by these gentlemen. ( at least now that my phone is down for the moment this is my theory ) heh:silly:
christopherrrg said:
Yes you must be on a global Canadian kdz that is BEFORE this version.
when you convert back make sure you use partition DL and uncheck recovery; then when you flash canadian kdz and boot up flash dm no verity and the other zip to make stock kdz boot with twrp still intact; then once system boots at least once you reboot into twrp with the master reset combo and then use the zip provided by these gentlemen. ( at least now that my phone is down for the moment this is my theory ) heh:silly:
Click to expand...
Click to collapse
Thanks again, but flashing back the H933 will relock the bootloader ?
[email protected] said:
Thanks again, but flashing back the H933 will relock the bootloader ?
Click to expand...
Click to collapse
nope! it remains unlocked.
I did manage to recover my device and my download mode (thanks to Matts amazing WTF guide.)
so give me about an hour or so and i'll retry; just going to take a quick shower.
Edit - had quite a few issues. Can't seem to get TWRP to actually work after doing partition DL all except recovery. (TWRP acts as if there is no system and when I try to boot it just reboots back into recovery.) Almost as if my Canadian device WANTS to stay US998 lol I got some issues to sort but will report back once I figure out how to make twrp flash AFTER full Canadian kdz, not sure if it's possible to flash recovery without fastboot is it?
recovery *would* be flashable with a rooted system and the dd (diskdump) command from within booted android.
so h933 is a device which needs conversion. this zip can then only be used when:
- you converted your h933 to us998 to get the fastboot commands and install twrp etc.
- your phone is then *converted back* to h933 with original h933 kdz, but with keeping twrp via partition dl mode of lgup.
- this way you lose fastboot commands (which normaly shouldn't be needed anymore), but can keep twrp and flash roms.
this method should work. because bootloader remains unlocked and is writable by twrp, even if you are on full h933 firmware, except recovery partition.
looks like we really need to work this out, carefully not that one of you nice testers have a non working phone because of this zip used in the wrong place (with us998 kdz installed) and moment (before full h933 kdz is installed with keeping twrp).
we need to try too, if this zip is installable on a converted to us998 phone and then at least boots as usual, or if sth. gets mixed up then (because it then has mixed partitions, ⅔ of the phones partitions are h933 fw then, and ⅓ is us998 partitions).
christopherrrg said:
nope! it remains unlocked.
I did manage to recover my device and my download mode (thanks to Matts amazing WTF guide.)
so give me about an hour or so and i'll retry; just going to take a quick shower.
Edit - had quite a few issues. Can't seem to get TWRP to actually work after doing partition DL all except recovery. (TWRP acts as if there is no system and when I try to boot it just reboots back into recovery.) Almost as if my Canadian device WANTS to stay US998 lol I got some issues to sort but will report back once I figure out how to make twrp flash AFTER full Canadian kdz, not sure if it's possible to flash recovery without fastboot is it?
Click to expand...
Click to collapse
this may be because of a differing partition table. *may*, i don't know this. i would like to have such a device for intensive testing... or visit canada and a person who's willing to drink much beer while testing this out :good:
seadersn said:
recovery *would* be flashable with a rooted system and the dd (diskdump) command from within booted android.
so h933 is a device which needs conversion. this zip can then only be used when:
- you converted your h933 to us998 to get the fastboot commands and install twrp etc.
- your phone is then *converted back* to h933 with original h933 kdz, but with keeping twrp via partition dl mode of lgup.
- this way you lose fastboot commands (which normaly shouldn't be needed anymore), but can keep twrp and flash roms.
this method should work. because bootloader remains unlocked and is writable by twrp, even if you are on full h933 firmware, except recovery partition.
looks like we really need to work this out, carefully not that one of you nice testers have a non working phone because of this zip used in the wrong place (with us998 kdz installed) and moment (before full h933 kdz is installed with keeping twrp).
we need to try too, if this zip is installable on a converted to us998 phone and then at least boots as usual, or if sth. gets mixed up then (because it then has mixed partitions, ⅔ of the phones partitions are h933 fw then, and ⅓ is us998 partitions).
Click to expand...
Click to collapse
I got my phone fully working again and my backup restored. (US998)
So I think what I'm going to attempt today is flashing FULL canadian kdz (fresh stock including recovery) and let it boot then I'm gonna try to dd the recovery to get TWRP access.
And go from there.
I got your PM and will need to pull out my nexus 4 for telegram but will set it up after work today and join you guys.
---------- Post added at 01:17 PM ---------- Previous post was at 01:15 PM ----------
seadersn said:
this may be because of a differing partition table. *may*, i don't know this. i would like to have such a device for intensive testing... or visit canada and a person who's willing to drink much beer while testing this out :good:
Click to expand...
Click to collapse
Heheh I'm willing to drink much beer wish I had my 2nd device because I'd have mailed you guys this H933 to crack.
We will get it soon, a lot more H933 people coming out of hiding really helps. ?
V
[email protected] said:
Thanks for the update, good luck recovering the phone. Maybe ou can try LG software from recovery ....
Click to expand...
Click to collapse
What actually got me out of the loop was Westwoods stock US998 TWRP ROM zip. I believe it restored my LAF partition and download mode worked no problem in order to use LGUP.
However these issues were of my own accounts; essentially from step 1 this is what the full procedure I assume will be like for us H933 users.
Step 1. Convert H933 to US998 and unlock bootloader using WTF guide.
Step 2. Using LGUP, 'REFURBISH' US998 device back into H933 kdz (accept partition layout changes) [attempted to use partition DL with all partitions minus recovery; however stock system won't boot with custom recovery unless rooted and no decrypt and dm verity flashed before system boots {failed to try this due to panic and forgetfulness so this may work but I'd like to attempt using dd from fresh stock also.}]
Step 3. Attempt dd recovery flash on bootloader unlocked H933 due to missing fastboot etc.
Step 4. Hope for profit? ?
I also apologize to you all for the lengthly posts as well but from all my years here on this website it's reading through the users problems where solutions are generally found so even though I followed wrong directions at first it's up to show everyone how I messed up and can be avoided.
christopherrrg said:
V
What actually got me out of the loop was Westwoods stock US998 TWRP ROM zip. I believe it restored my LAF partition and download mode worked no problem in order to use LGUP.
However these issues were of my own accounts; essentially from step 1 this is what the full procedure I assume will be like for us H933 users.
Step 1. Convert H933 to US998 and unlock bootloader using WTF guide.
Step 2. Using LGUP, 'REFURBISH' US998 device back into H933 kdz (accept partition layout changes) [attempted to use partition DL with all partitions minus recovery; however stock system won't boot with custom recovery unless rooted and no decrypt and dm verity flashed before system boots {failed to try this due to panic and forgetfulness so this may work but I'd like to attempt using dd from fresh stock also.}]
Step 3. Attempt dd recovery flash on bootloader unlocked H933 due to missing fastboot etc.
Step 4. Hope for profit? ?
I also apologize to you all for the lengthly posts as well but from all my years here on this website it's reading through the users problems where solutions are generally found so even though I followed wrong directions at first it's up to show everyone how I messed up and can be avoided.
Click to expand...
Click to collapse
absolutely ok, the more info the better so when one wants to stay stock h933, steps are
step 1: jep
step 2: jep, partition dl with *recovery excluded* to h933 kdz (after unlocking via us998). twrp should be present and bootable after that.
step 3: boot recovery, format data, reboot to recovery, flash opt-encrypt, no verity and make sure, /system/recovery-from-boot.py is deleted or renamed. and eventually flash magisk and then boot to rom, jep.
could imagine that this works, but, i know too little about frankensteined phones. there may be hassles and hiccups. first boot up and test, then trying a restore, in hope it will be succesful :good:
seadersn said:
absolutely ok, the more info the better so when one wants to stay stock h933, steps are
step 1: jep
step 2: jep, partition dl with *recovery excluded* to h933 kdz (after unlocking via us998). twrp should be present and bootable after that.
step 3: boot recovery, format data, reboot to recovery, flash opt-encrypt, no verity and make sure, /system/recovery-from-boot.py is deleted or renamed. and eventually flash magisk and then boot to rom, jep.
could imagine that this works, but, i know too little about frankensteined phones. there may be hassles and hiccups. first boot up and test, then trying a restore, in hope it will be succesful :good:
Click to expand...
Click to collapse
WOW; there it is.
Format Data. Another neglected procedure on my end grrr.
Saves the whole issue of using DD period.
And would explain why TWRP also half worked.
Gonna give it another crack as soon as I'm home. I'll also have telegram set up as to not spam this thread much further.
@cloud1250000 has posted a way to have a rooted canadian ROM https://forum.xda-developers.com/lg...odem-to-converted-us998-t3824769/post77613655 but from his instructions. He said he installed magisk to the canadian system to ensure root in order to use adb shell to install twrp. But I can't for the life of me figure out how he kept magisk but nothing else... so maybe he can help us.
No matter what I do after conversion of US998; H933 will not boot with TWRP on stock unless it's 100% stock. (Even after attempting dm verity, no encrypt and root) by trying your advice and tinkering with a bit of my own. LGUP also still reports the H933 device as a US99820d
Basically if he can help explain how he got magisk on there or I can figure it out then unfortunately at the moment we can't really flash this as we need a working recovery and sadly he's the only Canadian user reported so far having working twrp, root and lte working no problem.
Thing's I've tried so far:
- converted US998 to H933 with PARTITION DL and unchecked RECOVERY; recovery sticks however after formatting data then rebooting into recovery I then remove /system/recovery-bak (may have spelt that wrong but you get what I mean) I try flashing no encrypt and dm verity then flash root everything works (no red error messages of any kind) Boots back to recovery.
- converted US998 to H933 with PARTITION DL and made sure ALL checkboxes were checked. Phone booted but obviously no working recovery and no (at the current moment) known method of rooting without fastboot commands.
So sadly until we figure that I think we're stuck. ?
Will PM you my telegram info in the next few minutes.
So...
I have no clue why but when going back to the h933 from the us998... There's an extra partition called OP where, I assume, information about the carriers/modem can be found.
You should be aware that in canada now... there's no carrier locked phone anymore... so my guess is... this OP partition is configured on the first boot by looking at the sim that was inserted in the phone.
The problem.
TWRP doesn't have the command to setup the OP partition correctly and the phone do send this command to the recovery on first boot..
(found by looking at recovery log)
So what I did was...
1. Keep TWRP and use LGUP to go back to H933.
2. Boot into twrp and flash all needed zip (root + the other 2)
3. Flash the stock recovery and allow the phone to setup the OP partition correctly upon reboot (there will be a weird circle with "erasing" text on the screen)
4. Boot in the phone and launch the magisk app. Say yes a bunch of time.
5. Use a rooted adb shell to flash back twrp.
6. Profit/Enjoy
In my original guide, I did flash a bunch of partition that I got from a working h933.. so maybe it's missing some steps in order to work.
https://forum.xda-developers.com/lg...rted-us998-t3824769/post77613655#post77613655
Good luck.
cloud1250000 said:
So...
I have no clue why but when going back to the h933 from the us998... There's an extra partition called OP where, I assume, information about the carriers/modem can be found.
You should be aware that in canada now... there's no carrier locked phone anymore... so my guess is... this OP partition is configured on the first boot by looking at the sim that was inserted in the phone.
The problem.
TWRP doesn't have the command to setup the OP partition correctly and the phone do send this command to the recovery on first boot..
(found by looking at recovery log)
So what I did was...
1. Keep TWRP and use LGUP to go back to H933.
2. Boot into twrp and flash all needed zip (root + the other 2)
3. Flash the stock recovery and allow the phone to setup the OP partition correctly upon reboot (there will be a weird circle with "erasing" text on the screen)
4. Boot in the phone and launch the magisk app. Say yes a bunch of time.
5. Use a rooted adb shell to flash back magisk.
6. Profit/Enjoy
In my original guide, I did flash a bunch of partition that I got from a working h933.. so maybe it's missing some steps in order to work.
https://forum.xda-developers.com/lg...rted-us998-t3824769/post77613655#post77613655
Good luck.
Click to expand...
Click to collapse
Yeah I got lost on your step about dd recovery I was like uh wait how did he retain root?!
Thanks so much for your input! Very much appreciated.:highfive:
Also if we figure this out; that's an enormous contribution towards us getting custom ROMs working; thank you again!
Dear all,
I (newbie who trying to root for the first time) have tried to root my Samsung S9 with SuperSu via Odin. My device is now stuck at the S9 loading screen which will not boot up anymore.
Source of learning:
https://www.youtube.com/watch?v=g3IppGISkP0
Here's what I have done:
Stage 0 - Download all needed files
1. Odin 3.13.1
2. no-verify-opt-encrypt-6.0-star
3. RMM-state-ByPass_Mesa.zip
4. Samsung-anti-removal.2.4.zip
5. SupserSu-v.2.82.201705271822.zip
Stage 1 (Setup environment)
1. Enable Developer mode - OEM unlock enabled & USB Debugging enabled
2. Turn off my device, enter download mode (volume down button + bixby button + power button)
3. Connect my S9 device to my laptop
4. Launch Odin 3.13.1 on my laptop (S9 device recognized!) - Select AP, choose TWRP 3.3.1.1, press on start. (Device turn off itself)
5. As soon as device begins to boot, I enter recovery mode (volume up button + bixby button + power button)
Stage 2 Managed to entered TWRP
1. Swipe to Allow Modification
2. Tap on Wipe > Format Data > type in YES
3. Back to Menu
4. Tap on Install, (no-verify-opt-encrypt-6.0-star) - success
5. Reboot - Recovery
6. Tap on Install - (RMM-state-ByPass_Mesa.zip) - success
6. Hit back button
7. Tap on (SupserSu-v.2.82.201705271822.zip) - success
8 . Hit back button
9. Tap on (Samsung-anti-removal.2.4.zip) - success
10. Reboot system
11. Device begins reboot (Device stuck at Samsung S9 Screen)
Any advice what should I do now? Am I making any mistakes?
Please help. Appreciate!
CounteReborn said:
Dear all,
I (newbie who trying to root for the first time) have tried to root my Samsung S9 with SuperSu via Odin. My device is now stuck at the S9 loading screen which will not boot up anymore.
Source of learning:
https://www.youtube.com/watch?v=g3IppGISkP0
Here's what I have done:
Stage 0 - Download all needed files
1. Odin 3.13.1
2. no-verify-opt-encrypt-6.0-star
3. RMM-state-ByPass_Mesa.zip
4. Samsung-anti-removal.2.4.zip
5. SupserSu-v.2.82.201705271822.zip
Stage 1 (Setup environment)
1. Enable Developer mode - OEM unlock enabled & USB Debugging enabled
2. Turn off my device, enter download mode (volume down button + bixby button + power button)
3. Connect my S9 device to my laptop
4. Launch Odin 3.13.1 on my laptop (S9 device recognized!) - Select AP, choose TWRP 3.3.1.1, press on start. (Device turn off itself)
5. As soon as device begins to boot, I enter recovery mode (volume up button + bixby button + power button)
Stage 2 Managed to entered TWRP
1. Swipe to Allow Modification
2. Tap on Wipe > Format Data > type in YES
3. Back to Menu
4. Tap on Install, (no-verify-opt-encrypt-6.0-star) - success
5. Reboot - Recovery
6. Tap on Install - (RMM-state-ByPass_Mesa.zip) - success
6. Hit back button
7. Tap on (SupserSu-v.2.82.201705271822.zip) - success
8 . Hit back button
9. Tap on (Samsung-anti-removal.2.4.zip) - success
10. Reboot system
11. Device begins reboot (Device stuck at Samsung S9 Screen)
Any advice what should I do now? Am I making any mistakes?
Please help. Appreciate!
Click to expand...
Click to collapse
I believe you need magisk.
Instead of using SuperSU try using Magisk, it's more simple has has more features compared to SuperSU.
Also I think the reason why you stuck at the bootscreen is that after you format your phone, that means your phone got no rom/ system. Maybe you can try installing the ROM from the custom one which you can find in the cross device section in Here (Exynos Only).
And each of them has the instruction on how to install Magisk to root your phone
Edit: The video you refered to I believe is for the android 9 version, if your phone is on android 10 then it's outdated for your phone
TheMadScientist said:
I believe you need magisk.
Click to expand...
Click to collapse
I actually tried with Magisk.. but it stays the same. Basically I replace stage 2, step 7 with Magisk instead of Supersu.
Flashing only Magisk does not mean I have any system in place correct?
B1nz said:
Instead of using SuperSU try using Magisk, it's more simple has has more features compared to SuperSU.
Also I think the reason why you stuck at the bootscreen is that after you format your phone, that means your phone got no rom/ system. Maybe you can try installing the ROM from the custom one which you can find in the cross device section in Here (Exynos Only).
And each of them has the instruction on how to install Magisk to root your phone
Edit: The video you refered to I believe is for the android 9 version, if your phone is on android 10 then it's outdated for your phone
Click to expand...
Click to collapse
My device was on Android 9 actually.. so I have the exact same version as the video shown. Today I have flashed back my device with Stock ROM on Android 10. Im not sure with the steps Im doing it is right, when should I actually flash a custom rom? Please correct me if im wrong, my stage 1 should be all correct. Stage 2, before step 10 rebooting system, I should actually flash Custom ROM? Because after formatting my device and installing Magisk on Stage 2 step 7, my device still got no rom right?
After flashing back my device with Stock ROM on Android 10, I tried to root my device again with the steps give in video (still failed, device stuck at Samsung Logo again).
Flashing back again with Stock ROM. Tried to enter download mode to start TWRP via Odin.
Then I was given a message "Only official release binaries are allowed to be flashed (RECOVERY)" in Download Mode
Now what? Does that mean I can't go flash anymore? :crying:
CounteReborn said:
My device was on Android 9 actually.. so I have the exact same version as the video shown. Today I have flashed back my device with Stock ROM on Android 10. Im not sure with the steps Im doing it is right, when should I actually flash a custom rom? Please correct me if im wrong, my stage 1 should be all correct. Stage 2, before step 10 rebooting system, I should actually flash Custom ROM? Because after formatting my device and installing Magisk on Stage 2 step 7, my device still got no rom right?
Click to expand...
Click to collapse
Yes, the steps that I did on my own by coming from stock ROM:
1. Flash TWRP from odin, disable the automatic reboot
2. If success, then manually reboot to TWRP
3. Then I formated my phone
4. Follow the custom ROM installation steps
5. Done!
note:
- Steps 1 & 2 is basically the same as what you've done.
- If you still want to running the stock ROM, you have to flash the modified one or you'll stuck on the boot screen.
My suggestion is using the Alexis ROM, which is more updated (already on oneUI 2.1), more light, has alot of features (which you can choose in the aroma installer), and built in Magisk. so you don't have to install magisk manually
---------- Post added at 12:55 PM ---------- Previous post was at 12:51 PM ----------
CounteReborn said:
After flashing back my device with Stock ROM on Android 10, I tried to root my device again with the steps give in video (still failed, device stuck at Samsung Logo again).
Flashing back again with Stock ROM. Tried to enter download mode to start TWRP via Odin.
Then I was given a message "Only official release binaries are allowed to be flashed (RECOVERY)" in Download Mode
Now what? Does that mean I can't go flash anymore? :crying:
Click to expand...
Click to collapse
is it written "Prenormal"?
there's this stage called prenormal where you failed to modified your phone for the firstime, basically you have to wait like 7 days until you can modify your phone again.
and if still failing, it will back to the prenormal stage.
so far that's what i know, correct me if i'm wrong
if not then you can try to flash TWRP to see if it works
Also the thing i realize is that to be able to flash TWRP in Odin you have to finished doing the first time setup on the ROM, idk why but that's what i'm facing back then
Are you on Android 10? If yes, i followed this video.
https://m.youtube.com/watch?feature=youtu.be&v=HSqam9CYNGU
---------- Post added at 09:19 AM ---------- Previous post was at 09:13 AM ----------
CounteReborn said:
After flashing back my device with Stock ROM on Android 10, I tried to root my device again with the steps give in video (still failed, device stuck at Samsung Logo again).
Flashing back again with Stock ROM. Tried to enter download mode to start TWRP via Odin.
Then I was given a message "Only official release binaries are allowed to be flashed (RECOVERY)" in Download Mode
Now what? Does that mean I can't go flash anymore? :crying:
Click to expand...
Click to collapse
Because you flashed the stock firmware, you might forgot to enable oem bootloader unlock?
B1nz said:
Yes, the steps that I did on my own by coming from stock ROM:
1. Flash TWRP from odin, disable the automatic reboot
2. If success, then manually reboot to TWRP
3. Then I formated my phone
4. Follow the custom ROM installation steps
5. Done!
note:
- Steps 1 & 2 is basically the same as what you've done.
- If you still want to running the stock ROM, you have to flash the modified one or you'll stuck on the boot screen.
My suggestion is using the Alexis ROM, which is more updated (already on oneUI 2.1), more light, has alot of features (which you can choose in the aroma installer), and built in Magisk. so you don't have to install magisk manually
---------- Post added at 12:55 PM ---------- Previous post was at 12:51 PM ----------
is it written "Prenormal"?
there's this stage called prenormal where you failed to modified your phone for the firstime, basically you have to wait like 7 days until you can modify your phone again.
and if still failing, it will back to the prenormal stage.
so far that's what i know, correct me if i'm wrong
if not then you can try to flash TWRP to see if it works
Also the thing i realize is that to be able to flash TWRP in Odin you have to finished doing the first time setup on the ROM, idk why but that's what i'm facing back then
Click to expand...
Click to collapse
Not sure what actually happened, but the message is now gone after restart.
Anyway, Do you know this website (https://desktop.firmware.mobi/) instead, can I just use the ROM here to flash my device?
Not sure if I could just do the same, downlaod the recovery and boot img, then flash via Odin?
mkl.xda said:
Are you on Android 10? If yes, i followed this video.
https://m.youtube.com/watch?feature=youtu.be&v=HSqam9CYNGU
---------- Post added at 09:19 AM ---------- Previous post was at 09:13 AM ----------
Because you flashed the stock firmware, you might forgot to enable oem bootloader unlock?
Click to expand...
Click to collapse
Not sure what I did again, but the message "Only official release binaries are allowed to be flashed (RECOVERY)" is now removed. I just recall I did a restart I think. I tried your video, it didn't work. I end up in the same screen which I now think this is expected case? Because once we completely wipe the phone, the device has no more ROM. So in the video, we only flash back Magisk and Disable Verify.
Do you know this website (https://desktop.firmware.mobi/) instead, can I just use the ROM here to flash my device?
Not sure if I could just do the same, downlaod the recovery and boot img, then flash via Odin?
CounteReborn said:
Not sure what actually happened, but the message is now gone after restart.
Anyway, Do you know this website (https://desktop.firmware.mobi/) instead, can I just use the ROM here to flash my device?
Not sure if I could just do the same, downlaod the recovery and boot img, then flash via Odin?
Click to expand...
Click to collapse
Never knew that before tho, but if you want to download the official one I would recomend you downlaod from the SamMobile, which I highly recommend and is already trusted by alot of users here, just choose the right model number and country and you're done!, or if you want a faster download then I recommend you to use either Frija or SamFirm which is the same, and both are tools to download firmware from SamMobile.
It will download a zip of firmware, you just have to extract it and flash it by using Odin, also for the CSC file choose the HOME_CSC don't choose the normal CSC,
if you able to get into the normal rom, then you can do the instruction that i give before
hope it works
- 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