Related
UNIVERSAL GINGERBREAD ROOT SAMSUNG GALAXY MODELS: GT-S5570, GT-S5570B, GT-S5570I, GT-S5570L, GT-S5571, GT-S5578 (Chinese Mini), GT-S5660, GT-S5660M, GT-S5660L, GT-S5660V, SHW-M290K (Korean Gio), GT-S5670, GT-S5670B, GT-S5670L, GT-S5830, GT-S5830B, GT-S5830C, GT-S5830D, GT-S5830F(La Fleur), GT-S5830i, GT-S5830L, GT-S5830M, GT-S5830T, GT-S5830V(new), GT-S5830Z, GT-S5839i, GT-S6802, GT-B5330, GT-B7510, GT-B7510B, GT-B7510L, GT-B7800, GT-B5510, GT-B5510B, GT-B5510L, GT-B5512, GT-B5512B, GT-S6102, GT-S6102B, GT-S5300, GT-S5300B, GT-S5302, GT-S5360, GT-S5360B, GT-S5360L, GT-S5360T, GT-S5363, GT-S5369, GT-S5690, GT-S5690M, GT-S5690L, GT-I8150, GT-I8150B, GT-I5510, GT-I5510B, GT-I5510L, GT-I5510M, GT-I5510T, SCH-i509, SGH-T499(new), SGH-T589(new), SGH-T589R(new), SGH-I827(new), SGH-I837(new), SGH-I857(new).
DISCLAIMER: ---You will have sucessfully rooted Samsung phone only for the models that are mentioned above. Any other phone model is incompatible at the present time. Phone models like GT-S6500, GT-S7500, GT-I9000 have a diferent structure from diferent point of view. Diferent certificate pass key to the signed zip files, diferent update binary in the zip file and so on. If anything new comes out you will be informed untill then it is strictly on the models that are presented.---
This is only for the people that they are using Gingerbread and can't root their phone with SuperOneClick. You can root your phone with universal_gb_root_v24.zip file for your phone model.
Question: How do I Root Gingerbread on my phone?
Answer:
- First enable Unknown sources on your phone (Settings -> Applications -> Unknown sources)
- Download the universal_gb_root_v24.zip file and put in your SD card.
* How do I transfer universal_gb_root_v24.zip on my SD card?
(You can tranfer the universal_gb_root_v24.zip to your phone via Wifi, Bluetooth, SD micro Adapter or USB cable. To transfer it via USB cable you need first to download KIES from the offical Samsung Web Site and after installing restart your PC so the USB drivers can be recognized properly.Enable USB debugging on your phone, Settings -> Applications -> Development -> USB debugging. Plug in the USB cable and enable the connection on you mobile phone like the picture in the bottom. After couple of seconds your SD card will be showed on your PC like Removable disk. Copy universal_gb_root_v24.zip to your SD card.)
{
"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"
}
- After transferring your file on your phone disable the USB by pressing "Disconnect storage from PC" after that remove the USB cable and turn off your phone "Power off".
Entering recovery mode on Samsung Galaxy: (Young CDMA SCH-i509 and Chinese Version CDMA SCH-i509)
- Make shure you start the phone like this : Long press and hold the (Volume up Button) + (Power Button)
Entering recovery mode on Samsung Galaxy: (551 GT-i5510/B/L/M/T) (Pro GT-B7510)
- Make shure you start the phone like this : Long press and hold the (T Button) + (Power Button)
Entering recovery mode on Samsung Galaxy: (Ace GT-S5830/B/C/D/L/M/T) (Gio GT-S5660/M/L/V) (Fit GT-S5670/B/L) (Mini GT-S5770/B/L, GT-S5771)
- Make shure you start the phone like this : Long press and hold the (Power Button) + (Home Button)
Entering recovery mode on Samsung Galaxy : (Ace GT-S5830i) (Mini GT-S5570I) (W GT-I8150/B) (Xcover GT-S5690/M/L) (Young GT-S5360/B/L/T, GT-S5363, GT-S5369) (Y-Duos GT-S6102/B) (Y-Pro GT-B5510/B/L) (Y-Pro Duos GT-B5512/B) (M-Pro GT-B7800) (Pocket GT-S5300/B)
- Make shure you start the phone like this :
Method 1:
Long press and hold the (Volume up Button) + (Home Button) + (Power button)
* If for some reason with Method 1 the phone reboot always when entering recovery mode (depends on the models) please use the Method 2 option
Method 2:
Long press and hold the (Volume up Button) + (Home Button) + (Power button) when you see the samsung logo for the second time release (Home Button) and press again the (Home Button) and after that release the (Power button)
- After couple of seconds you will see your phone booting in recovery mode
- Move in the menu with the Volume - Volume + to scroll up and down and choose "apply update from sdcard" with the Home button and choose the universal_gb_root_v24.zip and press once again the Home button to apply it.
- You will see a message "Install form sdcard complete".
- Then press on the "reboot system now"
- When you open SuperSU it will ask you to upgrade the SU binary just press continue your phone will reboot once and you are done!
Download link for Universal Gingerbread Root (by StoneBoyTony) :
universal_gb_root_v24.zip
What's new in this version:
- SuperSU Application v0.94 (new)
- SuperSU binary v0.93 (new)
- Root Validator
- BusyBox binary v1.20.2 (new)
- New signed release key of the zip files for better compatibility on the phone models (new)
IMPORTANT: Root and Unroot method is designed to work in recovery mode on Stock ROM's. CWM Recovery and Custom ROM's are not supported! And never try to unroot your phone when you are using Custom rom!
FAQ
AFTER ROOTING I SEE ONLY ROOT VALIDATOR BUT NOT THE SUPERSU APPLICATION?
As some people reported there is sometimes problem with the rooting procedure files can't be extracted properly (applications,binaries) so from today (04.08.2012) in every new update there will be an extra second alternative root zip file recognized with the letter "b" in the end of the version number. As always in life we must have a B PLAN. In this root zip file package it will be only the SuperSu application and the supersu binary, no Busybox, Rootvalidator or anything else. So if the rooting procedure from above didn't work for you then you should run again in recovery mode the universal_gb_unroot_v8.zip to delete all the half extracted files from the root procedure previously done. After that you can apply universal_gb_root_v24b.zip known as Root Only.
IMPORTANT: If for some reason after rooting with the universal_gb_root_v24b.zip want to install Busybox then when you open the application it will give you a location to install busybox to /system/bin (this is for the reason becouse there is no busybox binary in this root zip file) you just need to simply relocate the installation to /system/xbin (to relocate the path simply press on the text /system/bin it will open a new window and change it to /system/xbin) . This is for a reason becouse in the future you might want to remove busybox and many times happend that it can't be uninstalled properly leaving all the applets in bin folder mixing the files with the system files from your Android OS. Then you need to install root explorer and delete all the applets manualy and trust me is a painful job. So the problem it will be solved very quickly by installing in /system/xbin. if you don't like it to have anymore later just use the procedure for unroot (READ: HOW CAN I UNROOT MY PHONE?) universal_gb_unroot_v8.zip it will delete all the remaining stuff from busybox in /system/xbin and use again the universal_gb_root_v24b.zip to root.
Download link for Universal Gingerbread Root ONLY (by StoneBoyTony) : universal_gb_root_v24b.zip
THERE IS NO SU BINARY AFTER ROOT?
From today (02.04.2012) I can proudly present the third update zip universal_gb_c.c.b.s.f_v7.zip. C.C.B.S.F stand for "Cleanup Carrier Branded System Files" What makes this package very interesting is allowing you to cleanup your System files (applications) from your branded carrier provider such as Shops, Music, Web Launchers, Widgets...Games: Tetris,Sims3 etc ...making free space in the system partition ROM (not internal memory) so later the root installation can take place and have a sucessfully rooted phone. This package will clean up most of the carrier providers like:
What's new in this version:
Added Carrier Network Providers:
- 3 (new)
- Aircel (new)
- Airtel
- Asda (new)
- Axis (new)
- Banglalink
- BT Mobile (new)
- Cellone (new)
- Dialog
- Dolphin (new)
- E-Plus
- Etisalat
- Globe
- Grameenphone
- H3G (new)
- Hutch
- IDEA
- Indosat (new)
- IR MCI (new)
- IRANCELL (new)
- Loop Mobile (new)
- M1
- Meteor
- Mobitel
- Movistar
- MTCE (new)
- NCELL
- NepalTelecom
- O2
- Optus
- Orange
- Poland Plus
- Reliance (new)
- Robi
- SFR
- STEL (new)
- Taliya (new)
- Talkmobile (new)
- TataDOCOMO (new)
- Telcel
- Teletalk
- Telkomsel (new)
- TelstraOne
- TESCO (new)
- TKC (new)
- T-Mobile
- tuenti
- Uninor (new)
- Videocon (new)
- Virgin
- Vodafone
- XL (new)
- New signed release key of the zip files for better compatibility on the phone models (new)
IMPORTANT: The universal_gb_c.c.b.s.f_v7.zip can be applyed in recovery like the rest of the zip files for root and unroot. It will delete all Carrier Branded System Files (Applications) without to interfere with the system files of Samsung Stock ROM's all functions will work normaly only the applications from the carrier branded apps will be deleted. In order to bring them back you need to unroot your phone and make a Factory Reset and all will be back as usual. This zip file should be only applyed if you have Carrier Provider Phone (like the above list already mentioned) and can't root the phone becouse of the carrier apps making a full capacity of the Android OS (system partition).
Download link for C.C.B.S.F (by StoneBoyTony) : universal_gb_c.c.b.s.f_v7.zip
I HAVE TRY ALL THE ABOVE METHODS NOTHING IS WORKING?
Chapter I
-Removing Quickoffice-
Well some Stock Firmwares have been made that in the system partition you can not even copy via recovery a single file. So my task search begin and finaly I found the bug to solve the problem. In many Stock Firmwares they put Quickoffice application, this stock firmwares in some cases are very problematic to make root on them. So finaly here is the solution and very simple to make a free space for rooting. Apply in recovery the universal_gb_remove_quickoffice.zip and then you can use the universal_gb_root_v24b.zip to finaly root your phone. So Quickoffice will be deleted from your system partition but you can always install the Quickoffice.apk whenever you want and it will be installed on your SD card (you can have the rooted phone and using again the Quickoffice). If for some reason you need to take your phone to the samsung service center problem with hardware,software or anything like that you can reverse the process to install Quickoffice back to the system partition (if you have installed the Quickoffice.apk uninstall it first from the Task Maneger)using first the universal_gb_unroot_v8.zip to unroot and after that use the universal_gb_install_quickoffice.zip to install Qucikoffice back to your system partition and all will be back as normal.
Download link to Remove Quickoffice (by StoneBoyTony): universal_gb_remove_quickoffice.zip
Download link to install Quickoffice application: Quickoffice.apk
Download link to install Quickoffice back on your system partition (by StoneBoyTony): universal_gb_install_quickoffice.zip
Chapter II
-Removing Thinkfree Office-
Same as Chapter I in many Stock Firmwares we find the application Thinkfree Office, this stock firmwares in some cases are very problematic to make root on them. The solution is very simple we just need to make a free space for rooting in your system partition and remove Thinkfree Office. Apply in recovery the universal_gb_remove_thinkfreeoffice.zip and then you can use the universal_gb_root_v24b.zip to finaly root your phone. Thinkfree Office will be deleted from your system partition but you can always install the ThinkfreeOffice.apk whenever you want and it will be installed in your internal memory (you can have the rooted phone and using again the Thinkfree Office). If for some reason you need to take your phone to the samsung service center problem with hardware,software or anything like that you can reverse the process to install Thinkfree Office back to the system partition (if you have installed the ThinkfreeOffice.apk uninstall it first from the Task Maneger) using first the universal_gb_unroot_v8.zip to unroot and after that use the universal_gb_install_thinkfreeoffice.zip to install Thinkfree Office back to your system partition and all will be back as normal.
Download link to Remove Thinkfree Office (by StoneBoyTony): universal_gb_remove_thinkfreeoffice.zip
Download link to install Thinkfree Office application: ThinkfreeOffice.apk
Download link to install Thinkfree Office back to your system partition (by StoneBoyTony): universal_gb_install_thinkfreeoffice.zip
HOW CAN I REMOVE ROOT VALIDATOR I DON'T NEED IT ANYMORE?
- You need to open SuperSu application and under "Apps" press the icon or the text for RootValidator. A new window will open and press "Forget". Power off your phone and enter in recovery mode to apply universal_gb_remove_validator_v3.zip file.
Download link for Remover of RootValidator (by StoneBoyTony) : universal_gb_remove_validator_v3.zip
HOW CAN I UNROOT MY PHONE?
- First thing you need to remove all the applications that they are depended from root, after that open SuperSU -> Settings -> Full Unroot and press Continue. Your phone will reboot once and after that enter Recovery mode and use the universal_gb_unroot_v8.zip to delete all the traces remaining. If you were having Superuser app (the older one) just get in the Recovery mode and then apply the universal_gb_unroot_v8.zip
You can download the UNROOT (by StoneBoyTony) from here: universal_gb_unroot_v8.zip
What's new in this version:
- Deleting all traces of Superuser
- Deleting all traces of Suhax
- Deleting all traces of Busybox and Busyboxpro (and all applets created in xbin that they are symlinked causing sometimes Busybox to fail of uninstalling them so that problem is solved i add them all to be deleted and for the leatest version 1.20.2. )
- Deleting all traces of Superoneclick
- Deleting all traces of SuperSU and SuperSU Pro
- Deleting Root Validator
- New signed release key of the zip files for better compatibility on the phone models (new)
*NOTE* - FOR ALREADY ROOTED PHONES WITH SUPERUSER
For those who already have root with Superuser or any other kind of root method and want to update your root with the new SuperSU package you need first uninstall all app that they are depended from root then apply in recovery mode the universal_gb_unroot_v8.zip and enter again in recovery mode to apply the universal_gb_root_v24.zip or you can use Only Root universal_gb_root_v24b.zip .
This is how it looks rooted phone you will have application SuperSU
This post is good for noobs lik me. . But a similar post abt apps is already posted in themes and apps section...here --
http://forum.xda-developers.com/showthread.php?t=1569607
JoK€R said:
This post is good for noobs lik me. . But a similar post abt apps is already posted in themes and apps section...here --
http://forum.xda-developers.com/showthread.php?t=1569607
Click to expand...
Click to collapse
The diference is providing root and unroot for more phones that they didn't have any luck untill now.
hello
Newbie here,
Rooting my froyo with a tutorial whitout problems but now i have a new one with
gingerbread 2.3.6
It's a mt 6573 dapeng A7 and no real solution ar found to root.
Will this update zip also works on this device or not or is it just for the samsung bootrom.
I have boot into recovery an made a full backup.
So if i apply this update and it's not work for some reason can i still be enter the recovery mode or not to restore my backup from sdcard or is my phone bricked.
just learning so sorry if there are noob questions because there is no real tutorial for 2.3.6
grts b,
hi op you should know soc support rooting gb from a long time but this method is more easy
---------- Post added at 05:42 PM ---------- Previous post was at 05:36 PM ----------
have you checked it manually I have open the script and found that you have written a command which will format /system
and without how mobile will boot
Samsung Galaxy GT-S7500
Does not work with the s7500.
I got the following:
E: failed to verify whole-file signature
E: signature verification failed
Also downloaded the file again three times and got the same message
dhlalit11 said:
hi op you should know soc support rooting gb from a long time but this method is more easy
---------- Post added at 05:42 PM ---------- Previous post was at 05:36 PM ----------
have you checked it manually I have open the script and found that you have written a command which will format /system
and without how mobile will boot
Click to expand...
Click to collapse
You should know what is the sign before format command is "#" that mean that the command is not in function
sab65 said:
Does not work with the s7500.
I got the following:
E: failed to verify whole-file signature
E: signature verification failed
Also downloaded the file again three times and got the same message
Click to expand...
Click to collapse
Sorry about that it was experimental for Ace Plus removed from the Tutorial.
rcbadboy said:
hello
Newbie here,
Rooting my froyo with a tutorial whitout problems but now i have a new one with
gingerbread 2.3.6
It's a mt 6573 dapeng A7 and no real solution ar found to root.
Will this update zip also works on this device or not or is it just for the samsung bootrom.
I have boot into recovery an made a full backup.
So if i apply this update and it's not work for some reason can i still be enter the recovery mode or not to restore my backup from sdcard or is my phone bricked.
just learning so sorry if there are noob questions because there is no real tutorial for 2.3.6
grts b,
Click to expand...
Click to collapse
My friend you have mixed the pots. This is for Samsung Galaxy phones and nothing to do with Mediatek phones; Need to search for the forum about your phone.
StoneBoyTony said:
My friend you have mixed the pots. This is for Samsung Galaxy phones and nothing to do with Mediatek phones; Need to search for the forum about your phone.
Click to expand...
Click to collapse
hey
ik know this is the samsung sub but because i saw "universal gingerbread" it's maybe works for other phone's also.
But now i think not
i could just try because i have try everything to root my phone to get rid of this unwanted chinese apps.
grts b,
I know adding # before any line will tell system not to read that line but why take risk when we can remove that
StoneBoyTony said:
Sorry about that it was experimental for Ace Plus removed from the Tutorial.
Click to expand...
Click to collapse
Yes it is a pity. Have not been able to find a way to root the Ace Plus. It is very frustrating. This was the closest I got to doing it.
This worked perfect on samsung galaxy mini.
Thank you.
doesnt work on 2.3.4 galaxy ace
Gyku said:
This worked perfect on samsung galaxy mini.
Thank you.
Click to expand...
Click to collapse
Hi,
Certainly doesnt work on a Samsung galaxy ace S5830T on 2.3.4 and GINGERBREAD.DVKQ3.
anyone know what i can root this phone with ??
I tried everything on the web ..no luck.
oldernerd said:
Hi,
Certainly doesnt work on a Samsung galaxy ace S5830T on 2.3.4 and GINGERBREAD.DVKQ3.
anyone know what i can root this phone with ??
I tried everything on the web ..no luck.
Click to expand...
Click to collapse
It not support in script. Just edit update-script and change something to GT-S5830T from GT-S5830 and flash
Sent from my GT-S5570 using XDA
oldernerd said:
Hi,
Certainly doesnt work on a Samsung galaxy ace S5830T on 2.3.4 and GINGERBREAD.DVKQ3.
anyone know what i can root this phone with ??
I tried everything on the web ..no luck.
Click to expand...
Click to collapse
Redownload v14 now is fixed problem was that I forgot to put the script it in Unix Format...see if you have any luck now
tried this method with galaxy s6102 and worked with no issues.
thx
worked perfect on samsung galaxy y dous
Rename zip file
<THOR> said:
You have try to rename the package zip in upd_1.zip and then flash from recovery? if not, try.
Click to expand...
Click to collapse
Thor,
Thanks for your reply...
Rename it to what ??
Already called upd_.zip
---------- Post added at 12:30 PM ---------- Previous post was at 11:52 AM ----------
Hi,
Just downloaded V14 and whilst it says it is rooted and superuser app is loaded, i do not believe the phone is rooted.
Is there a definitive and SIMPLE way i can test
to see if it is actually rooted and that the software i am trying to use is incorrect ??
OR maybe, i dont have the latest V14....
Can i get a link to the latest V14 ??
oldernerd said:
Thor,
Thanks for your reply...
Rename it to what ??
Already called upd_.zip
---------- Post added at 12:30 PM ---------- Previous post was at 11:52 AM ----------
Hi,
Just downloaded V14 and whilst it says it is rooted and superuser app is loaded, i do not believe the phone is rooted.
Is there a definitive and SIMPLE way i can test
to see if it is actually rooted and that the software i am trying to use is incorrect ??
OR maybe, i dont have the latest V14....
Can i get a link to the latest V14 ??
Click to expand...
Click to collapse
install root apps like root explorer, titanium backup or freespace.. if these apps prompt you to allow or deny SU access, choose allow.. if you're phone is rooted, SuperUser app will display that these apps were granted superuser permissions.. simple..
new version
would be great of we could get a new version cut (V15 ??) with Thor's recommendations as well....
I am nearly at wits end with this S5830T rooting issue.
Hi,
I want to root my phone, a Galaxy Mini, but before I do that I have some noob questions, because I don't want to do something stupid...
1. This should work on android 2.3.6 S5570XWKT2, right?
and...
2. Is there any risk that this can brick my phone?
Thanks!
Sent from my GT-S5570 using XDA
Q&A for [ROM][4.4.2]Kitkat STABLE V2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
pranavaryans said:
its buggy. may b ill upload pie etc in next vrsion
Sent from my Q1000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have the following problem by connecting a mini bluetooth keyboard is recognized only then that does not work.
bluetooth keyboard
I have a problem I connected a bluetooth keyboard just that I recognized and configured in the settings bluetooth only that the system does not work.
are the bugs fixed? like slow wifi connection?
hi dev. im Having trouble here. i did a full wipe. my first installed got stock in bootloop. and second install somehow survive "the bootloop" i thought. it actually load the screen. but just keep restarting.. help please.
---------- Post added at 12:19 PM ---------- Previous post was at 11:57 AM ----------
please provide me steps how to install..onejay's runny kitkat and pacrom works well with me. and i want to try this one..thanks..
i need help, i did a full wipe and still ended up in bootllop. tried it three times with the same outcome. please give me the steps in flashing.. just a newbie hope you could help, thanks.
basic steps
1. install twrp recovery
2. copy rom .zip to sd card directory
3. go to recovery
4. select wipe option > advanced wipe > tick on dalvic, cache, data, android secure and system ( no sdcard should be ticked)
5. click on WIPE
6. go to home of TWRP
7. click on install
8. go to directory where you had been put rom.zip
9. click on rom.zip
10. slide the progress bar to right nd installation starts
11. after installation select wipe dalvic and cache option
12. then click on "back"
13.there should be now "reboot to system" option will be seen.
14.selct it
15. wait for 3 to 4 min for bootup process
16.for confirmation try to connected to pc by cabel, when it will be completed your mobile as well as pc will give you sound and red light on mobile
17. done
why is the download link showing "complete an offer"?
Too bad I can't just post this in the right thread but here goes:
I also want to help you test and would love to see a 4.4.4 come to my sensation XL. I would be happy to pay you a few bears of cours Do you think you can make the rom as 'clean' as possible?
Thank you in advance!
HTC Sensation XL
I have installed this android but the sound disapears suddenly.i have put in normal mode but jus the vibration works.sound disapears in all part of sounds: music,clock alarm,ringone calls.what should i do? thanks
---------- Post added at 04:38 PM ---------- Previous post was at 04:29 PM ----------
What should i do about the disaperance of audio,thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
* [B][U]Your warranty is now void.[/U][/B]
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or your getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
Odin
- Odin3 v3.13.3
Heimdall
- Glass Echidna
TWRP for Samsung Galaxy Tab S2 8.0 2015 (LTE)
TWRP for Samsung Galaxy Tab S2 8.0 2015 (Wi-Fi)
TWRP for Samsung Galaxy Tab S2 9.7 2015 (LTE)
TWRP for Samsung Galaxy Tab S2 9.7 2015 (Wi-Fi)
How to flash a bootloader and/or modem1. If your tablet is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu,
2. In Odin, import either the bootloader.tar or bootloader_modem.tar file, depending on your variant, with the "AP" button.
How to flash TWRP with Odin1. If your tablet is turned on normally, turn on Advanced reboot in Developer options and select "Download" from the Restart menu. Alternatively, power it off and press the Power, Volume Down, and Home buttons simultaneously. When the blue screen appears, release all 3 buttons and press Volume Up.
2. In Odin, import the appropriate twrp.tar file for your variant with the "AP" and press the "Start" button.
3. You can then boot directly into TWRP by pressing the Power, Volume Up, and Home buttons simultaneously. Release all three buttons as soon as you see the boot screen ("Samsung Galaxy Tab S2").
How to flash TWRP within a previous version of TWRP1. If your tablet is turned on normally, turn on Advanced reboot in Developer options and select "Recovery" from the Restart menu. Alternatively, power it off and press the Power, Volume Up, and Home buttons simultaneously. Release all 3 buttons when the boot screen appears ("Samsung Galaxy Tab S2").
2. In TWRP, tap "Install" then "Install Image".
3. Navigate in the folder structure to the location of the appropriate twrp.img file for your variant and tap it.
4. Select the "Recovery" radio button.
5. Move the slider to the right to flash the TWRP image.
6. Tap "Reboot System" or, alternatively, tap the back arrow 3 times to return to the main menu, then tap "Reboot" and "Recovery" to reboot into the TWRP image you have just flashed.
Changelog
- See post #2.
Bugs
E:recv error on uevent
- This warning appears during the process of making a nandroid backup. I assure you that it's perfectly innocence: your backup should complete successfully and it should restore successfully without any reference to this warning. This is a known bug that affects other Exynos devices as well, such as the Samsung Galaxy S7 Edge (hero2lte).
- Technical explanation from bigbiff himself: "I think it must be a bug, probably shouldn't print the log out if we aren't using ueventd to pull in partition information on a target device. I am not sure what devices we are supporting using ueventd however. Looks like it only runs from the process_fstab function. It's harmless, but I wonder if it should be put in an ifdef guard."
Credits
- Inspiration in motivating me to learn how to build TWRP: ashyx
- Updated partition sizes: jcadduono
- Testing of my gts28wifi builds to figure out the X-Y orientation bug: tripLr
- Providing source to fix MTP and ADB: bonuzzz
- Every other open source developer and user who contributes directly or indirectly to the TWRP community in the development of and in providing feedback for the gts28ltexx, gts28wifi, gts210ltexx, and gts210wifi.
Sources
- gts2 kernel repository
- gts28ltexx repository
- gts28wifi repository
- gts210ltexx repository
- gts210wifi repository
- TWRP repository
XDA:DevDB Information
TWRP 3.5.2_9-0, ROM for the Samsung Galaxy Tab S2
Contributors
ripee
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Current Stable Version: 3.5.2_9-0
Stable Release Date: 2021-04-05
Created 2017-12-15
Last Updated 2022-12-09
Reserved
CHANGELOG
3.2.3-0
* Device now appears properly in adb shell, as per @t-o-f-u's patch in post #69.
Reserved
T710 only
Tested original version bad
Tested version ending in 1 working.
Backup all partitions pic below
T710 only Root access confirmed in file manager
You Might change title to [TWRP][Unofficial] xxxxxxxx
TotalNoobTrucker said:
You Might change title to [TWRP][Unofficial] xxxxxxxx
Click to expand...
Click to collapse
Good idea about the title.
About the 3 different version of gts28wifi I posted a few hours ago: can you please confirm that versions 2 and 3 DO NOT WORK? I removed the number from version 1 in my TWRP folder, so if that's the one that works, that code will be send back to TeamWin for the official build.
ripee said:
Good idea about the title.
About the 3 different version of gts28wifi I posted a few hours ago: can you please confirm that versions 2 and 3 DO NOT WORK? I removed the number from version 1 in my TWRP folder, so if that's the one that works, that code will be send back to TeamWin for the official build.
Click to expand...
Click to collapse
Ok,
Flashed back to ashyxx
Flashed file ending in 2. It works ...!
Flashed back to ashyx
Flashed file ending in 3. It works too!!!
Don't know what u did, but 1 2 and 3 worked.
I checked your md5 and they were all different.
So something was different in each one but the last 3 of 4 work.
Flashing your un numbered file now.. rechecking
There are 2 TWRP flash that rotate the screen orientation from portrait to landscape that must be added if the TW_THEME is set to landscape:
RECOVERY_TOUCHSCREEN_SWAP_XY := true
RECOVERY_TOUCHSCREEN_FLIP_Y := true
My first link from a few hours ago was build with both of these included, and we established that it didn't work.
Build 1 from a while ago had both of these removed, build 2 only included the top one, and build 3 only had the bottom one. Do all 3 numbered builds work equally well?
Great! Just tried lastest version of TWRP for T710 (dec-15) and touch is working great! Thank you for your work!
ripee said:
Good idea about the title.
About the 3 different version of gts28wifi I posted a few hours ago: can you please confirm that versions 2 and 3 DO NOT WORK? I removed the number from version 1 in my TWRP folder, so if that's the one that works, that code will be send back to TeamWin for the official build.
Click to expand...
Click to collapse
Ok. Reloaded the file from basket build with no number. It works same as 2 and 3
Send it off. By the way if there is a way to append the 3.2.1-0 with ripee I would do it ashyxx did. Haha
---------- Post added at 04:04 AM ---------- Previous post was at 04:02 AM ----------
ripee said:
There are 2 TWRP flash that rotate the screen orientation from portrait to landscape that must be added if the TW_THEME is set to landscape:
RECOVERY_TOUCHSCREEN_SWAP_XY := true
RECOVERY_TOUCHSCREEN_FLIP_Y := true
My first link from a few hours ago was build with both of these included, and we established that it didn't work.
Build 1 from a while ago had both of these removed, build 2 only included the top one, and build 3 only had the bottom one. Do all 3 numbered builds work equally well?
Click to expand...
Click to collapse
Your build one is now not named 1 it works but does not rotate.
Lemme check 2 and 3
TotalNoobTrucker said:
Ok. Reloaded the file from basket build with no number. It works same as 2 and 3
Send it off. By the way if there is a way to append the 3.2.1-0 with ripee I would do it ashyxx did. Haha
Click to expand...
Click to collapse
I'd have to add the optional flag TW_DEVICE_VERSION := _ripee to the BoardConfig.mk file, but with all due respect to ashyx, I'm not particularly interested in labelling my builds. But TWRP's Jenkins builder just appends the next available version number after the dash anyway.
Ok, the code is sent off for official support!
1 2 and 3 do not rotate. Portrait only, no landscape, flip, or flip landscape . Who cares. The root works in all 3 with touch screen on each file and directory. So the screen works great
I tested a full backup in 1, 10 gig to the SD card. So mounts are working.
Wohoo
---------- Post added at 04:16 AM ---------- Previous post was at 04:15 AM ----------
By the way rebooting into download mode directly from TWRP saved a ton of boot time
---------- Post added at 04:26 AM ---------- Previous post was at 04:16 AM ----------
Running twrp-3.2.1-0-gts28wifi.tar from Odin now full time. Thanks.
Let me know if you want to play with lineage 8.0. the t710 has 64 bit processors, and the developer from posiedon 1.0 got the source from Samsung to build it.
I just tested the version for the T810:
- flashing is successful
- touchscreen is working well
- besides the normal partitions there are "modem" and "efs" listed
- a test backup throws a lot of "E:recv error on uevent" errors.
So for now I went back to TWRP 3.1.1
hurray said:
I just tested the version for the T810:
- flashing is successful
- touchscreen is working well
- besides the normal partitions there are "modem" and "efs" listed
- a test backup throws a lot of "E:recv error on uevent" errors.
So for now I went back to TWRP 3.1.1
Click to expand...
Click to collapse
I can imagine that they used the same partitions as the mobile data variants. Do modem and efs cause problems with backing up? I'll run my own backup today to confirm.
If you're using my 3.1.1, well I built it from the same sources as 3.2.1 so let's see.
I did not run the backup till the last partitions as the error came directly with the first partition. Then I interrupt the backup. I can upload the recovery.log if it is useful for you.
hurray said:
I did not run the backup till the last partitions as the error came directly with the first partition. Then I interrupt the backup. I can upload the recovery.log if it is useful for you.
Click to expand...
Click to collapse
Sorry but I'm unable to reproduce your error so please post the log. Here's what I did:
I made 2 separate backups on my T810, one with a password and one without, of the 3 partitions that are checked off by default when you go into the Backup screen. Yes, modem and EFS are present and listed as having some data, but I didn't check either of them off.
At no point in either of the backup or restore procedures did I get the "E:recv error on uevent" error, or any error for that matter.
ripee said:
Sorry but I'm unable to reproduce your error so please post the log. Here's what I did:
I made 2 separate backups on my T810, one with a password and one without, of the 3 partitions that are checked off by default when you go into the Backup screen. Yes, modem and EFS are present and listed as having some data, but I didn't check either of them off.
At no point in either of the backup or restore procedures did I get the "E:recv error on uevent" error, or any error for that matter.
Click to expand...
Click to collapse
Here is the log of my backup. As I wrote I did not finished the backup. I interrupted it as soon as I saw the error.
I don't think that the error cames from selecting the modem and EFS partitions.
Here is a litte snipped from the relevant part of the log (on line #2641 in the log):
Code:
I:addFile '/system/fonts/RobotoCondensed-BoldItalic.ttf' including root: 0
==> set selinux context: u:object_r:system_file:s0
E:recv error on uevent
I:addFile '/system/fonts/RobotoCondensed-Italic.ttf' including root: 0
==> set selinux context: u:object_r:system_file:s0
I don't know why this behaviour accours. The TWRP "twrp-3.1.1-0-gts210wifi.img" from you works without error (backup AND restore ). I don't use a password or encryption on the Tab S2. The only option I use is "compress" to save some space as my backups are space consuming on the external sdcard without it.
@ripee
Hello my friend. Thank you for your effort, I want to mention about the issue in TWRP , when you run any aroma it ru in wrong orientation. I want to ask If you fix that issue in your build.
My device is T815
Sent from my SM-T815 using Tapatalk
hurray said:
Here is the log of my backup. As I wrote I did not finished the backup. I interrupted it as soon as I saw the error.
I don't think that the error cames from selecting the modem and EFS partitions.
Here is a litte snipped from the relevant part of the log (on line #2641 in the log):
Code:
I:addFile '/system/fonts/RobotoCondensed-BoldItalic.ttf' including root: 0
==> set selinux context: u:object_r:system_file:s0
E:recv error on uevent
I:addFile '/system/fonts/RobotoCondensed-Italic.ttf' including root: 0
==> set selinux context: u:object_r:system_file:s0
I don't know why this behaviour accours. The TWRP "twrp-3.1.1-0-gts210wifi.img" from you works without error (backup AND restore ). I don't use a password or encryption on the Tab S2. The only option I use is "compress" to save some space as my backups are space consuming on the external sdcard without it.
Click to expand...
Click to collapse
Please allow the backup to finish without stopping it. Let me know of any other errors that pop up and, if it stops by itself, which partition it was backing up when it stopped. In the meantime, I'll take a look at your log.
NeWONEx said:
@ripee
Hello my friend. Thank you for your effort, I want to mention about the issue in TWRP , when you run any aroma it ru in wrong orientation. I want to ask If you fix that issue in your build.
My device is T815
Sent from my SM-T815 using Tapatalk
Click to expand...
Click to collapse
Is Aroma displaying in portrait orientation while TWRP is in landscape? Which exact Aroma build are you trying to flash? Did this also occur on older versions of TWRP? Are you able to tap on Aroma's menus properly, or does the tap location not correspond to the place that Aroma thinks you tapped? I need more details to be able to help.
There is a chance that Aroma needs to be updated to TWRP 3.2.
UPDATE OF JULY, 13th 2019 : IMPORTANT INFO : This guide is no longer updated. The recent update of June 2019 broke compatibility with my Bootloader Ver. 2 I was using which worked fine from the first Nougat release to the first Pie update (included). As I'm still daily running Android Nougat (7.0), I can't risk to upgrade to BL Ver. 5 and find myself locked under Pie. And the main risk is that I can't know if BL v5 is breaking modem compatibility or not and if it does it means that I'll lose all wireless connectivity under Nougat. So, as I can't risk my device (which is my daily) I have no choice other than dropping the support of this device. I apologize.
SAMSUNG Galaxy Note Fan Edition
Exynos 8890 - International Ver. [SM-N935F/DS]
{
"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"
}
Current Status :
(Pie 9.0) - POST 06/21/2019 Update - Unknown
(Pie 9.0) - PRE 06/21/2019 Update - Rootable
(Oreo 8.0) - Rootable
(Nougat 7.0) - Rootable
Latest Ver. of TWRP: v3.3.1-0
Latest Ver. of Android: Pie (Android 9.0)
1 - ▼ DISCLAIMER ▼
- I DECLINE TOTAL RESPONSIBILITY IF YOU DAMAGE OR BRICK YOUR PHONE WHILE TRYING THIS METHOD ! YOU'RE DOING IT AT YOUR OWN RISKS !
- THIS METHOD IS ONLY VALID FOR THE GALAXY NOTE FAN EDITION (EXYNOS Ver.) SM-N935F/DS VERSION ! IT'S NOT SUITABLE FOR THE KOREAN VARIANTS !
- FLASHING ANY CUSTOM BINARY WILL IRREMEDIABLY VOID YOUR WARRANTY AND KNOX COUNTER WILL BE TRIGGERED (0x1).
- MAKE SURE THAT YOUR DEVICE HAS AT LEAST 70% BATTERY BEFORE ATTEMPTING ANY STEPS !
- ALL THE DATA ON THE INTERNAL STORAGE WILL BE DELETED ! BACKUP ALL YOUR FILES IN A SAFE PLACE BEFORE PROCEEDING !
2 - ▼ Important Infos ▼
To avoid making any mistakes, I HIGHLY recommend you to READ CAREFULLY the WHOLE guide BEFORE attempting anything! Prevention is better than cure remember
The Galaxy Note FE (like many other Samsung devices) use dm-verity and data partition encryption.
► Android 9.0 (Pie) - UPDATE OF THE 06/21/2019 (Bootloader V5) :
The Note FE (International Ver.) Android Pie update of (June 2019) support is unknown.
As I can't try if my patch works, (see above), I can't test if the latest update is rootable or not.
However, the problem is probably similiar to the first Pie release of March 2019, the fix is also probably the same
but due to changes to the kernel or boot routines, the old fix dosen't work anymore.
If you're under an older Pie release (typically with a v4 BL or less) or even under an other Android version, you can still follow this guide.
► About RMM State :
The Note FE (International Ver.) is shipped with a component called "RMM".
This component is able to prevent the end-user from flashing any custom binary on the device while it's active.
You can check if your RMM is enabled or disabled by putting your device in Download Mode :
- If the line "RMM State: Prenormal" is present, then RMM is enabled and you won't be able to flash any custom binary.
- If it's absent, then it has already been disabled which means that you'll be able to flash any custom binary.
This component suddenly disable itself after 7 days of continuous uptime since the device has been last powered on.
You can check your device actual uptime by going into : "Settings" > "About phone" > "Status" > "Uptime"
Or use CPU-Z : "System" tab and "System Uptime". (CPU-Z displays the uptime in days rather than hours.)
Once 7 days are elapsed, it will be desactivated BUT! If you format the data partition for example, which's required to disable data encryption for rooting, it will be back!
Even worse, if you reboot once you've setup your phone, you'll get blocked with a message when you'll powering it on saying ("custom binary has been block due to remaining installment balance") and you'll have to reflash stock to get your device working again...
To avoid that, once the /data partition has been wiped, you'll need to apply the RMM fix (prerequisites section, see below) which prevents the device from re-self-locking itself after rebooting, once the initial setup has been completed.
Everytime you install a new official firmware, RMM might be active again.
It is triggered by an hidden system app called "Rlc" which acts on the bootloader lock.
If your Rlc app is still present, the best thing to do is to simply delete it ASAP to prevent any unpredictable action on your bootloader. (system/priv-app/Rlc)
For custom ROMs, normally they're safe. But still, check if the dev has already deleted Rlc, otherwise you'll have to do it by yourself.
3 - ▼ Prerequisites ▼
1 - A SAMSUNG Galaxy Note FE [SM-N935F/DS]
2 - The Samsung USB Drivers (If not already installed, => [HERE] <= )
3 - Download the lastest Odin (v3.13.1) => [HERE] <=
4 - Download TWRP for the Galaxy Note7 [SM-N930F] (v3.2.1-0.img.tar) => [HERE] <=
5 - For Android Nougat (7.0) :
Download Magisk (v18.1) [HERE]
Download the RMM Patch [HERE]
Click to expand...
Click to collapse
5 - For Android Oreo (8.0) :
Download Magisk (v18.1) [HERE]
Download the RMM Patch [HERE]
Download the /data partition fix (for Android Oreo) [HERE]
Click to expand...
Click to collapse
5 - For Android Pie (9.0) :
Download Magisk (v18.1) [HERE]
Download the RMM Patch [HERE]
Download the Kernel Patch (for Android Pie) [HERE]
Click to expand...
Click to collapse
6 - A PC and a USB-C Cable
7 - A brain, a pair of eyeballs and some fingers (Yeah, that could help... especially the first one..)
4 - ▼ Flashing TWRP 3.2.1-0 on the Galaxy Note FE ▼
If Your RMM is locked you will have to wait 7 days (or 168 hours) while maintaining your device up and running. (NEVER REBOOT DURING THIS TIME ! IT WILL RESET THE RMM TIME COUNTER!)
=> For more info and/or if you don't understand what I'm talking about, please refer to section 2 of this page and read it all.
Once RMM is desactivated (or already desactivated), you can proceed to the next steps :
Make sure to enable "USB Debugging" and "OEM Unlock" in the Dev Options.
Connect your phone to your PC and drag and drop the Magisk package and the RMM fix at the root of your microSD card.
Now, depending on the Android version you're running, drag and drop the additional fix that you've downloaded earlier at the root of your mSD card too. (Only if you're on Oreo or Pie)
Once it's done, backup everything valuable and power off your device.
Enter the Download Mode by pressing simultaneously the "Home" + "Vol. Down" + "Power" buttons for 5 sec. Read the warning message and just answer "Continue".
Launch Odin and select TWRP 3.2.1-0 archive by clicking on the "AP" button.
Go to the "Options" tab and untick "Auto-reboot"
Connect your phone which is in DL Mode to your PC.
/IMPORTANT!\ Make sure Odin is seeing your device properly.
(Once connected, you should see the box under the "ID:COM" tab displaying "0:[COM*]" in blue, meaning your phone has been detected successfully. If not, Install the Samsung USB Drivers, link available in the prerequisites section.)
Flash TWRP.
Wait while Odin in flashing the recovery. /AVOID TOUCHING ANYTHING DURING FLASH PROCESS\
When Odin shows "PASS", take your device in hands, disconnect the USB-C cable and press simultaneously the "Home" + "Vol. Down" + "Power" buttons until the DL mode disappears.
When at the precise moment the screen becomes black, immediately release the "Vol.Down" button and press the "Home" + "Vol. UP" + "Power" buttons during 10 to 15sec to enter TWRP recovery.
You should see TWRP logo just after the Note FE splash-screen.
Click to expand...
Click to collapse
Now TWRP is successfully installed. But we're not done yet ! We still have to deal with the data encryption and disable dm-verity in order to boot properly.
5 - ▼ [9.0] Rooting the Galaxy Note FE under Android Pie ▼
Once TWRP is showing up, tick the option labeled "Never show this screen during boot again" and slide the cursor to allow modifications.
On the main menu, tap on "Wipe"
Then, tap on "Format Data" and confirm that you want to erase all data by entering "YES" in the text box and validate.
Data is now wiped and encryption removed.
Return to the main menu and tap "Reboot" and then "Recovery"
Once the device has rebooted in Recovery again, tap "Install" and Install the RMM fix package from your SD card.
Once it's done, wipe cache & dalvik and return to the main menu.
Install the kernel patch for Android Pie.
Once it's done, wipe cache & dalvik and return to the main menu.
Install the Magisk package, the root solution.
Once it's done, wipe cache & dalvik and return to the main menu.
Last step, tap "Reboot" and then "System"
Click to expand...
Click to collapse
Your device will now reboot. It may stay a couple of minutes on the "SAMSUNG" logo as the whole ROM is being reinstalled. Once the setup screen is appearing, setup your phone as usual.
Note : All Samsung Pay, Pass, Knox etc.. features and Secure Folder won't be usable anymore as Knox as been triggered. For Samsung Health, there is an easy fix. Just read the whole guide
6 - ▼ [8.0] Rooting the Galaxy Note FE under Android Oreo ▼
Once TWRP is showing up, tick the option labeled "Never show this screen during boot again" and slide the cursor to allow modifications.
On the main menu, tap on "Wipe"
Then, tap on "Format Data" and confirm that you want to erase all data by entering "YES" in the text box and validate.
Data is now wiped and encryption removed.
Return to the main menu and tap "Reboot" and then "Recovery"
Once the device has rebooted in Recovery again, tap "Install" and install Magisk package from your SD card.
Once it's done, wipe cache & dalvik and return to the main menu.
Install the RMM fix package.
Once it's done, wipe cache & dalvik and return to the main menu.
Install the /data partition fix package.
Once it's done, wipe cache & dalvik and return to the main menu.
Last step, tap "Reboot" and then "System"
Click to expand...
Click to collapse
Your device will now reboot. It may stay a couple of minutes on the "SAMSUNG" logo as the whole ROM is being reinstalled. Once the setup screen is appearing, setup your phone as usual.
Note : All Samsung Pay, Pass, Knox etc.. features and Secure Folder won't be usable anymore as Knox as been triggered. For Samsung Health, there is an easy fix. Just read the whole guide
7 - ▼ [7.0] Rooting the Galaxy Note FE under Android Nougat ▼
Once TWRP is showing up, tick the option labeled "Never show this screen during boot again" and slide the cursor to allow modifications.
On the main menu, tap on "Wipe"
Then, tap on "Format Data" and confirm that you want to erase all data by entering "YES" in the text box and validate.
Data is now wiped and encryption removed !
Return to the main menu and tap "Reboot" and then "Recovery"
Once the device has rebooted in Recovery again, tap "Install" and install Magisk package from your SD card.
Once it's done, wipe cache & dalvik and return to the main menu.
Install the RMM fix package.
Once it's done, wipe cache & dalvik and return to the main menu.
Last step, tap "Reboot" and then "System"
Click to expand...
Click to collapse
Your device will now reboot. It may stay a couple of minutes on the "SAMSUNG" logo as the whole ROM is being reinstalled. Once the setup screen is appearing, setup your phone as usual.
Note : All Samsung Pay, Pass, Knox etc.. features and Secure Folder won't be usable anymore as Knox as been triggered. For Samsung Health, there is an easy fix. Just read the whole guide
8 - ▼ Disable SecurityLogAgent pop-up & Samsung Anti-Malware ▼
Samsung provides an anti-malware on their phones and the Note FE is one of them. The system will detect that Magisk has been installed and a service called "SecurityLogAgent" will regularly
pop-up in your notification bar to invite you to launch the Device Maintenance app and reboot the device using an orange button to "eliminate" the threat. => DO NOT REBOOT USING THIS BUTTON ! <=
You'll end up soft-brick your phone. And this, won't disappear on it's own.
Here's how to disable and definitively hide that anti-malware crap from the Device Management app :
Download the lastest version of MiXplorer => HERE <= (Or any file manager of your choice. MiXplorer is lightweight, nice to use, free and made on XDA.)
Access the root partition in the left panel and go into the "/system/csc" folder
Open the file "others.xml" with the text editor.
Add the following line at the end :
Code:
[I]<CscFeature_SmartManager_DisableAntiMalware>TRUE</CscFeature_SmartManager_DisableAntiMalware>[/I]
Save the changes, and close the app.
Reboot.
Click to expand...
Click to collapse
The Samsung Anti Malware is now disabled as well as the annoying pop-up.You're good to go, enjoy!
9 - ▼ Fix Samsung Health ▼
For whatever reasons, Samsung locks-up Samsung Health once Knox has been triggered.. But go figure why, there's only a simple thing to do to re-enable the app and be able to use it again easily.
You can either use a file manager or the app "BuildProp Editor".
Download the lastest version of MiXplorer => HERE <= (Or any file manager of your choice. MiXplorer is lightweight, nice to use, free and made on XDA.)
Access the root partition in the left panel and go into the "/system" folder
Open the file "build.prop" with the text editor.
Simply change the line
Code:
ro.config.tima=[COLOR="Red"][B]1[/B][/COLOR]
to
Code:
ro.config.tima=[COLOR="SeaGreen"][B]0[/B][/COLOR]
Save the changes, and close the app.
Reboot.
Click to expand...
Click to collapse
Samsung Health is now working again. :good:
10 - ▼ Troubleshooting ▼
You have a problem with your Note FE ? Take a look at those answers before posting :
Q: I try to flash TWRP with Odin but a message pops up on my device and says "custom binary has been block due to remaining installment balance". What's happening ?
A: RMM. This message is more likely to appear if you still have RMM enabled. Boot your phone, keep it powered on and running and never reboots during 7 days and it should disappear.
Q: I've flashed TWRP with success, formatted data and stuff but I see the message "custom binary has been block due to remaining installment balance" at boot and I can't boot ! What's happening ?
A: RMM again ! Once data has been formatted and Android first reinstalled, RMM lock is back! Same thing can happen if you did not install the RMM fix with TWRP. To unbrick it, you have 2 options : 1 - Flash stock BUT with HOME_CSC. (It will keep the RMM elasped time, but you'll have to keep in mind since how much time has elapsed already.) or 2 - Reflash stock and follow the entire procedure again and the waiting again. The first one might work, if not, then try the 2nd one.
Q: I've managed to install TWRP, root and get my phone up and running but I've clicked on the orange "Reboot" in the Anti-Malware tab in the Device Management app.
Now my phone bootloops (or) shows the message "custom binary has been block due to remaining installment balance" and I'm stuck with it.
A: You've got trapped into Samsung Anti-Malware crap. This utility can't delete Magisk. Any solutions ? Restore one of your previous TWRP backup but if you have none, the only solution is to re-flash stock, repeat the entire procedure, disable SecurityEventLog service to get rid of those annoying security pop-ups AND stay away from the anti-malware utility !
11 - ▼ Extras ▼
Thanks. If there is any mistakes or errors, please feel free to report them to me, I'll correct them
Credits goes to :
Magisk (@topjohnwu & @phhusson, @Chainfire, @nkk71, @osm0sis, @Captain_Throwback, @Didgeridoohan, @jenslody, @digitalhigh, @DVDandroid)
TWRP Recovery (@TeamTWRP)
The RMM Fix (@BlackMesa123)
The /data partition Fix (@dr.ketan & @RicePlay33)
Odin Soft (@anycallmongolia)
MiXplorer File Manager (@HootanParsa)
How to keep the elasped time (@societyragdoll)
SAMSUNG... (@Samsung) (duh)
Author : RicePlay33
Thanks ! I'll give it a try.
Do you think we can use all the flashable mods and custom roms from S7/S7 edge?
Well the answers are : Maybe and No.
Some mods that you can apply with TWRP may work, some not.
Concerning custom ROMs it's totally no. ROMs are designed for specific hardware and phone models. Unless someone creates a custom ROM for the Note FE, it's not possible.
RicePlay33 said:
Some mods that you can apply with TWRP may work, some not.
Concerning custom ROMs it's totally no. ROMs are designed for specific hardware and phone models. Unless someone creates a custom ROM for the Note FE, it's not possible.
Click to expand...
Click to collapse
Yes you can use custom roms from the Note 7 or Note FE of Korea [emoji12]
Envoyé de mon SM-N935F en utilisant Tapatalk
benyou54 said:
Yes you can use custom roms from the Note 7 or Note FE of Korea [emoji12]
Envoyé de mon SM-N935F en utilisant Tapatalk
Click to expand...
Click to collapse
I wouldn't try it lol. At your own risks
@RicePlay33 just out of curiosity, what mods have you tried ?
Paninno12 said:
@RicePlay33 just out of curiosity, what mods have you tried ?
Click to expand...
Click to collapse
I've only tried the Dual Speaker mod for the S7 edge as it was my previous device, but it only works partially on the FE actually. Whenever I make a phone call for the first time just after rebooting, the microphone works fine but then if I try any more times after, the microphone stops working without any reasons :/ Quite a weird problem.. Like I said, some mods may work, some not.
any mod you want to try i suggest take it from s8/s8+ version. anyway since you guys has root your device... try to update some of the old apps in system. got a better one out there.
I've tried the Dual Speaker for the Note 8 (Magisk mod) but it simply didn't work. That would be awesome if the dev of this mod for the S7/ S7 edge version could release a NFE one (@zubi182)
Does anyone know if Secure Folder can be somehow enabled? I managed to do it on my rooted S7 Edge , but with dark lord rom and some sort of kernel. I'm guessing this isn't possible on this rooted stock rom?
Anyone know where i can get an international note fe?dont want dual SIM version
Secure Folder can be fooled with a modified kernel yeah. To my knowledge too, it's not possible with the stock one.
please help me remove knox on samsung s7 nN935F. picture in attach. thanks all
Hi ! Was able to reboot and edit some lines (using root explorer) in build.prop ro.securestorage to false and ro.config.tima to 0. Problem is.. the securestorage even at false value i still cant view the saved wifi passwords. So i tried changing the permission to 777 thats when i had the red custom binary blocked and rmm prenormal. Flashed to stock rom last night. Not sure how but i tried flashing only with csc_home but red warning is still there. But with ap it worked. Didnt flash bl, cp etc. Am i doing this right? So now i have to wait again. Can i use supersu instead of magisk? the root is not giving me full privelege in this androdumpper app (on the saved password section ). Thank you for your awesome post RicePlay33.
@donart81 I've searched a bit and I've found this => http://phuongpn.com/how-to-decrypting-wifi-password-on-samsung-galaxy-phone-solved/ Did you done the rest of the operation ?
Also, changing the value of "ro.securestorage to false" maybe triggers the RMM lockdown as it seems related to the security of the device. (Encrypting WiFi passwords)
The message was still there because you've ONLY flashed "HOME_CSC", it was specified to flash stock (so including everything BL/AP/CP etc) but for the CSC, choosing the HOME_CSC one. It will flash stock 99% like usual but the HOME_CSC will keep the time elapsed of RMM, reducing the time needed to re-root it again.
You should have tried to disable RMM Maybe it wouldn't have bricked itself.
oh so that's how you flash hehe. i'm such a noob.
yup i think i have done the rest of the operation. I've successfully rebooted after changing the value of the build.prop (ro.securestorage + ro.config.tima) to see if it was not reverted back to original. device was working. it was only when i changed its permission checked it all suddenly it bricked my phone hehe.
next time i'll try to change the value of the "Support Rmm" in the experiment section and report back if it worked
thank you for your informative reply.
There has been some development about a possible RMM State Fix Over here.
Did anyone try it?
I'm just waiting for the 7 days to pass, and this wait itself is killing me!
Yeah I saw that. I was thinking to talk about it but I didn't had the time recently.
I'll update the main post, although I may need someone to try it first and report me what is going on on his device to be able to document it as clear as possible and also to see if it works without any problems.
Don't worry, 7 days and you'll be free like a bird is
hello i installed twrp on the device and made root and then waited 7 days and 7 days is completed. When the device is off and the device is open, the device has failed.
My fault : custom binary blocked due to remaining installment balance
Please melp me mate
what should I do ?
RicePlay33 said:
Yeah I saw that. I was thinking to talk about it but I didn't had the time recently.
I'll update the main post, although I may need someone to try it first and report me what is going on on his device to be able to document it as clear as possible and also to see if it works without any problems.
Don't worry, 7 days and you'll be free like a bird is
Click to expand...
Click to collapse
I will do it as soon as I'm released from the jail.!
However, "This being free is temporary" I guess as it seems like after a new firmware update from Samsung, This will be a routine process.
mest47 said:
hello i installed twrp on the device and made root and then waited 7 days and 7 days is completed. When the device is off and the device is open, the device has failed.
My fault : custom binary blocked due to remaining installment balance
Please melp me mate
what should I do ?
Click to expand...
Click to collapse
Hi, Im not really qualified to answer your query, But from What I have learned -
You need to flash a Stock Rom,
Do the 7 Day wait until the RMM State is disappeared,
Then Follow the steps in the OP, and Flash the RMM State fix immediately to prevent getting locked again.
*Name officially landed on Mars aboard the Perseverance rover on 2nd of March 2021*
Note Fan Edition Rom
[OneUI 1.0][Android 9.0]
For S7/S7E F/FD
From MKUltraBlack
Jack O'Neill Kernel
Based on stock NFE from:
https://github.com/ananjaser1211/Helios_8890
This rom is straight flash with autodetect for kernel and battery text built into updater-script and omc will choose the csc, no aroma. Just flash and let boot, give 5-10 mins for first boot
Credits to @Kill-Switch for a LOT of his time and expert help and porting lessons
Also thanks to @ananjaser1211 for his expert help in the kernel and a lot of help in the rom too.
Thanks to @corsicanu for the recovery method and other help
Great guys
MKUltraBlack NFE V6.0 link:
https://www.androidfilehost.com/?fid=17248734326145734344
Base on Korean K firmware:
https://www.sammobile.com/samsung/g.../SM-N935K/KTC/download/N935KKKU4CUA1/1262323/
MKUltraBlack NFE V6.0:
Feb 2021 security patch
Secure folder
Screen recording
Long press reboot to recovery
Telegram group link in settings
GameTools
Game Launcher
Dual messenger
Applock
USSD codes
Bixby vision
Live draw
Google assistant
MKUltraBlack font
Network speed toggle
Straight flash - No aroma
NFE logo on power menu
Custom NFE boot animation
Auto detect (S7/S7E) install correct kernel and battery text
# Removed Bixby home
***************************************************
Flashable blcp for F international variant
Binary 8:
https://www.androidfilehost.com/?fid=17248734326145734341
***********************************************
******************
How to install
custom rom
******************
You will need:
*PC with Odin 3.13.1 or above
(https://samsungodin.com)
*TWRP .tar image for your model
Flat: https://eu.dl.twrp.me/herolte/
Edge: https://eu.dl.twrp.me/hero2lte/
*Rom
(Stored on external memory/sdcard)
*Unlocked OEM
To unlock OEM
********************************************
Go to settings, phone information, and tap build number until it says developer options unlocked, press back twice and go into developer options turn on OEM unlock
********************************************
1. Put your phone into download mode by turning your phone off, now press volume down, power and home key at the same time until the screen turns green, then release the buttons.
2. Open Odin on your PC and plug the USB cable into your phone and press volume up.
You will see it is connected to Odin, (there will be a blue rectangle saying com(number)
3. Select the AP section and load your TWRP .tar image in there.
4. Get ready to press volume up, home and power button at same time on your phone now press start on Odin, it will only take a few seconds, as soon as the box goes green and says pass, press the volume up, home and power button combo until TWRP splash screen shows up on your phone screen. Now release button combo and unplug USB cable from your phone.
5. In twrp press wipe, then format. A keyboard will appear, type yes and press enter. Now press back to go to TWRP main screen and press reboot and select reboot to recovery. It will now reboot back into TWRP.
6. Press wipe again, then format, type yes, press enter. (Do this 3 times)
Press back to go to TWRP main screen and press wipe, select advanced wipe, check all boxes apart from OTG and SDCARD and swipe. (Do this 3 times)
Press back to go to TWRP main screen and press wipe then swipe to factory reset. (Do this 3 times)
********************************************
Your phone is now completely clear with no operating system and ready to flash a custom rom. When you downloaded your rom, you stored it on your sd card or external storage, you need to do this as when you do all the wipes it wipes your internal storage but not your sd card, that's why it says in advanced wipe don't check the sd card or OTG boxes.
********************************************
7. Press back until you go to main screen in TWRP and select install, select storage, external (sd card) and select the rom zip. Now just swipe to flash.
Normally it will go into aroma which contains check boxes of extra items to add into the rom, this rom however is a straight flash, it will automatically detect your phone model and select the correct kernel and battery capacity. It will say Installation finished when done. Now go back to main twrp screen and select reboot and press system. The phone will reboot, leave it 10-15mins to allow it to load the rom, be patient. Then you will be at the set up page just like starting a new phone. Set up from there and enjoy the rom.[/PLAIN]
Good job. Congrats
Will try soon
Download link would be helpful
Kai Disobey said:
Download link would be helpful
Click to expand...
Click to collapse
Forgot to put link lol was in a rush yesterday.
Recovery button and twrp link in menu
MKUltraBlack said:
Forgot to put link lol was in a rush yesterday.
Click to expand...
Click to collapse
OOPS !
No mirrors Found. on AFH !!!
Kai Disobey said:
OOPS !
No mirrors Found. on AFH !!!
Click to expand...
Click to collapse
Gdrive link added
MKUltraBlack said:
Note Fan Edition Rom
For S7/S7E F/FD
From MKUltraBlack
Based on N935F:
https://www.sammobile.com/samsung/g...e/SM-N935F/CAM/download/N935FXXU6CSK1/308356/
Jack O'Neill Kernel
Based on stock NFE from:
https://github.com/ananjaser1211/Helios_8890
Secure folder working
Debloated Bixby Pretty much everything else left in
Link to MKUltraBlackTWRP in settings
MKUltraBlack font added
Recovery button in power menu
High Brightness warning removed
High volume warning removed
Sith Empire walllpaper added
Custom boot animation
November 2019 patch waiting for next security patch to update
Just a little thing I threw together to try porting, so nothing special
This rom is straight flash with autodetect for kernel and battery text built into updater-script and omc will choose the csc, no aroma. Just flash and let boot, give 5-10 mins for first boot
Credits to @Kill-Switch for a LOT of his time and expert help and porting lessons
Also thanks to @ananjaser1211 for his expert help in the kernel and a lot of help in the rom too,
Great guys
Link: https://www.androidfilehost.com/?fid=4349826312261725389
Gdrive link: https://drive.google.com/drive/u/2/...7h0kWG7PRnn3PjagUMQPlhtox?sort=13&direction=a
Chat:
https://t.me/MKUltraBlack_Rom
Click to expand...
Click to collapse
will you please guide?
How can I add a secure folder in another custom rom?
zasprince007 said:
will you please guide?
How can I add a secure folder in another custom rom?
Click to expand...
Click to collapse
Ask the developer of that rom to add it, there are guides here on xda
MKUltraBlack said:
Ask the developer of that rom to add it, there are guides here on xda
Click to expand...
Click to collapse
I tried but nothing works.
I also asked the developer to add The secure folder in their custom rom,
If you do help me I'm very thankful to you.
zasprince007 said:
I tried but nothing works.
I also asked the developer to add The secure folder in their custom rom,
If you do help me I'm very thankful to you.
Click to expand...
Click to collapse
Use this rom, it has working secure folder.
To get secure folder working you would need to have all Knox apps (which are probably debloated from his rom)
Do a build.prop edit and an smali edit in services.jar
I am not going to rebuild somebody else's rom
Any chance for Galaxy watch to pair ?
Thanks !
nicohak said:
Any chance for Galaxy watch to pair ?
Thanks !
Click to expand...
Click to collapse
Try this https://forum.xda-developers.com/s7...rary-fix-samsung-gear-devices-t3931738/page11
Removed Gdrive link, AFH is working now, it was just down for a bit. I want to use AFH so I can see how many downloads
MKUltraBlack said:
Note Fan Edition Rom
For S7/S7E F/FD
From MKUltraBlack
Based on N935F:
https://www.sammobile.com/samsung/g...e/SM-N935F/CAM/download/N935FXXU6CSK1/308356/
Jack O'Neill Kernel
Based on stock NFE from:
https://github.com/ananjaser1211/Helios_8890
Secure folder working
Debloated Bixby Pretty much everything else left in
Link to MKUltraBlackTWRP in settings
MKUltraBlack font added
Recovery button in power menu
High Brightness warning removed
High volume warning removed
Sith Empire walllpaper added
Custom boot animation
November 2019 patch waiting for next security patch to update
Just a little thing I threw together to try porting, so nothing special
This rom is straight flash with autodetect for kernel and battery text built into updater-script and omc will choose the csc, no aroma. Just flash and let boot, give 5-10 mins for first boot
Credits to @Kill-Switch for a LOT of his time and expert help and porting lessons
Also thanks to @ananjaser1211 for his expert help in the kernel and a lot of help in the rom too,
Great guys
Link: https://www.androidfilehost.com/?fid=4349826312261725389
Chat:
https://t.me/MKUltraBlack_Rom
Click to expand...
Click to collapse
I want to know about gaming performance?
I'm using a rom in which game does lagging like hell especially PUBG Mobile.
Will you share with us your rom game performance?
zasprince007 said:
I want to know about gaming performance?
I'm using a rom in which game does lagging like hell especially PUBG Mobile.
Will you share with us your rom game performance?
Click to expand...
Click to collapse
Download the rom, install pubg, play it and let me know.
I don't play that game, also I'm not sure there is a way to show "rom game performance", don't even know what that is.
Game tools
game tools and game launcher not available!!!
anwarmazaz said:
game tools and game launcher not available!!!
Click to expand...
Click to collapse
Debloated!!!
Thank you!
Thank you!!
Enviado desde mi SM-N950F mediante Tapatalk