Development/Reference.
==================================================
This is a development thread. Do not ask for help with this or that,
this is not a support thread! Make sure that any question you might
have, is directly related to the benefit of this thread and on-topic.
==================================================
Click to expand...
Click to collapse
This thread will contain Heimdall Firmware Packages made from Official Samsung Firmware Packages.
-->Post 1<--: General Announcement
-->Post 2<--: How to make Heimdall Firmware Packages
-->Post 3<--: Heimdall Firmware Packages
-->Post 4<--: How to flash on Linux(Windows and OSX is similar)
-->Post 5<--: reserved
-->Post 6<--: reserved
Click to expand...
Click to collapse
All released Heimdall Firmware Packages on this thread are succesfully tested by me!
I am not reponsible for any damages(brick) on your device by flashing since flashing is dangerous by nature!
Click to expand...
Click to collapse
If your needed Firmware is not released follow the the Guide in Post 2.
You cant handle it?
Just request it over "Feature Requests"(I do not accept any PM!) by following example(I will do it my free time so please be patience it will take a while!):
In line: "Enter a title for the feature" -> Enter this ->> Requesting Heimdall Firmware Package
In line: "Describe the feature"-> Enter this:
Latest firmware info
GT-I9506
PDA: I9506XXUAMJ2
CSC: I9506VDSAMJ5
MODEM: I9506XXUAMI1
Added: 2013-11-10
You can get this information from SAMMOBILE.COM by searching for Model: GT-I9506 and ProductCode: xxxxxx > Check Firmware
Click to expand...
Click to collapse
The main benefit of using Heimdall Firmware Packages(when Odin doesnt work) is that you get your Device in Download Mode the "Official" state back.
I will explain it later in thread detailed!
This works currently with the Firmwares 4.2.2!
Example Before and After:
Before flashing the right Heimdall Firmware Package!
Your device is in Download Mode and looks like that(Custom):
ODIN MODE
PRODUCT NAME: GT-I9506
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: 0x1b
WRITE PROTECTION: Enable
After flashing the right Heimdall Firmware Package!
Your device is in Download Mode and looks like that(Official):
ODIN MODE
PRODUCT NAME: GT-I9506
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: 0x1b
WRITE PROTECTION: Enable
Click to expand...
Click to collapse
---- PROGRAM HEIMDALL ----
Download:
Heimdall (c) 2010-2013 Benjamin Dobell, Glass Echidna
DISCLAIMER:
This software attempts to flash your Galaxy S device. The very nature of
flashing is dangerous. As with all flashing software, Heimdall has the
potential to damage (brick) your device if not used carefully. If you're
concerned, don't use this software. Flashing ROMs onto your phone may also
void your warranty. Benjamin Dobell and Glass Echidna are not responsible
for the result of your actions.
- Heimdall is a cross-platform open-source tool suite used to flash firmware (aka ROMs) onto Samsung mobile devices.
- Open Source
- over 1,000,000+ Downloads
GitHub
- Linux:
Linux/README
- OS X
OSX/README.txt
- Windows
Win32/README.txt
Click to expand...
Click to collapse
BIG THANKS TO @Benjamin Dobell
Okay lets do it!
XDA:DevDB Information
HEIMDALL FIRMWARE PACKAGES, a ROM for the Samsung Galaxy S 4
Contributors
xenix96
Version Information
Status: Stable
Created 2013-12-15
Last Updated 2013-12-14
How to make Heimdall Firmware Packages
How to Create a Heimdall Firmware Package:
Firstly, Heimdall's firmware package format is just a regular TAR archive
compressed with gzip. The only two real requirements are that a valid
firmware.xml must be included (refer to Appendix A) and you can only
include files (no directories, links etc.) As such if you'd like there is
nothing preventing you from creating Heimdall packages manually. Of course
Heimdall Frontend provides a simple user interface that takes care of all
the hard work for you.
There are two ways in which you can create a firmware package. You can
create a package from scratch, or you can load an existing package, apply
modifications and then save the package. Creating a package from scratch
is the preferred approach, by taking this approach you're far less likely
to run into file name length limitations.
Before you can access Heimdall Frontend's firmware creation functionality
(available from the "Create Package" tab) you must first specify which
files will be included in your package, as well as a few flashing options
i.e. Whether or not users should repartition when flashing. This
information must be filled out from the "Flash" tab in exactly the same
fashion you would provide information to flash your device (see "Performing
a Custom Flash with Heimdall Frontend"). As mentioned above, it's not the
preferred means, but you're able to load an existing package as a starting
point for this information.
Once you've specified the files/partitions you wish to include in your
firmware package the "Create Package" tab will become available. Clicking
this tab will display additional information that you can include in your
package. In order to continue you must fill out all sections except for the
URLs section, which is optional. The following is a break-down of what all
these options mean.
Click to expand...
Click to collapse
- General Firmware Information: -
Firmware Name - This is the name of your particular firmware. An
example would be "Cyanogenmod".
Firmware Version - This is the version identifier for your package. Any
valid string will be accepted, although the inclusion of decimal
point version number is preferred i.e. "7.1". If it makes sense
then feel free to append a text string like "RC1" or "Beta 1" to
the decimal point version.
Platform Name - This is the name of platform (or operating system) that
your firmware is based on. In most cases this will simply be
"Android".
Platform Version - This is the operating system version that your
firmware is based on. Again decimal point version numbers are
preferred over text, i.e. "2.3.4" is preferred over "Gingerbread".
Click to expand...
Click to collapse
- Developers -
URLs (Optional):
Homepage - Here you can enter your personal URL or a URL particularly
pertaining to the firmware being packaged. The URL must be well
formed for it to work. An example of a well formed URL is
"http://www.glassechidna.com.au/products/heimdall/". It is
important to include "http://" in order to specify the protocol as
other protocols such as "ftp://" are equally valid although
unlikely to be used.
Donate - Here you can enter a URL that will link users to a page to
make donations for the effort you've put into developing your
firmware. Once again the URL must be well formed but there is no
requirement on how your donation page should work. For instance
both "http://www.glassechidna.com.au/donate/" and
"http://forum.xda-developers.com/donatetome.php?u=2710388" are
equally valid.
Click to expand...
Click to collapse
Developer Info:
Name - Here you can enter in the name of individual team members or a
team name. Click "Add" and the developer will be added to the list
on the right. If you make a mistake you can select a developer from
the list and click "Remove". You can list as many developers as you
like, however visual constraints of the "Load Package" tab means
only a few names will be visible. Where possible you may want to
opt for team names over listing individual team members.
Click to expand...
Click to collapse
- Supported Devices -
This section allows you to create a list of devices that are supported by
your particular firmware. Although Heimdall isn't capable of enforcing this
we strongly recommend you take this section seriously. If filled out
correctly you could help save a number of accidental bricks!
Click to expand...
Click to collapse
Device Info:
Manufacturer - This is where you can enter the name of the manufacturer
for a particular device. For now this will most likely be
"Samsung".
Name - This is the human readable name for a particular device.
"Galaxy S", "Galaxy S II", "Droid Charge", "Vibrant" and
"Galaxy S (Telstra)" are all valid names. There are a lot of
possible variations here so be as specific as you think is
necessary.
Product Code - This is by far the most important bit of device
information. Device names tend to be region specific and further
subject to the whims of telecommunication companies and resellers.
Product Codes (or product IDs) are designated by manufacturers and
are generally the definitive means of referring to a particular
device. Examples are "GT-I9000", "GT-I9100" and "SCH-I897". If
you're unsure of a particular product code then both Google and
GSMArena are your friends!
After filling out all the necessary information the "Build" button will be
enabled. If it's still disabled then you know you're missing some required
information. In particular you must specify at least one developer and at
least one supported device. Pressing the "Build" button will bring up a
save dialogue where you must chose a file name for your particular package.
Don't worry about specifying the ".tar.gz" extension Heimdall Frontend will
take care of this automatically.
Once you've chosen a file name Heimdall Frontend will begin the process of
building the firmware package. In doing so a valid firmware.xml file will
be generated from the information entered. All files will be archived in a
single TAR file then the TAR archive will be compressed via gzip
compression. Compression will take a little while but you will see progress
bars so you know the application hasn't hung. When the progress bars
disappear you're finished making your package.
Congratulations! You're now ready to redistribute your firmware package
online or by any means you see fit.
Click to expand...
Click to collapse
Appendix A - firmware.xml
The following details a part of the Heimdall Firmware Package format. This
is only relevant to developers or advanced users who wish to create Heimdall
Firmware Packages outside of Heimdall Frontend or in some way integrate support
for the format in their own software.
All Heimdall Firmware Packages must contain a file called firmware.xml. This
file stores flash information and meta-data for the package as well as
information about other files contained within the package.
The format is fairly straight-forward so it won't be explained in great detail.
Nonetheless the following is an example of a valid firmware.xml file.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<firmware version="1">
<name>Test Firmware</name>
<version>1.1</version>
<platform>
<name>Android</name>
<version>2.3.4</version>
</platform>
<developers>
<name>Benjamin Dobell</name>
<name>Hedonism Bot</name>
</developers>
<url>http://www.glassechidna.com.au/</url>
<donateurl>http://www.glassechidna.com.au/donate/</donateurl>
<devices>
<device>
<manufacturer>Samsung</manufacturer>
<product>GT-I9000</product>
<name>Galaxy S</name>
</device>
<device>
<manufacturer>Samsung</manufacturer>
<product>GT-I9000T</product>
<name>Galaxy S (Telstra)</name>
</device>
<device>
<manufacturer>Samsung</manufacturer>
<product>GT-I9000M</product>
<name>Vibrant</name>
</device>
</devices>
<pit>Nl3276-I9000 s1_odin_20100512.pit</pit>
<repartition>0</repartition>
<noreboot>0</noreboot>
<files>
<file>
<id>0</id>
<filename>gq3276-boot.bin</filename>
</file>
<file>
<id>24</id>
<filename>Uh3276-cache.rfs</filename>
</file>
<file>
<id>22</id>
<filename>em3276-factoryfs.rfs</filename>
</file>
<file>
<id>11</id>
<filename>fl3276-modem.bin</filename>
</file>
<file>
<id>21</id>
<filename>Xd3276-param.lfs</filename>
</file>
<file>
<id>3</id>
<filename>if3276-Sbl.bin</filename>
</file>
<file>
<id>6</id>
<filename>cr3276-zImage</filename>
</file>
</files>
</firmware>
New lines need not be included and the order in which elements are specified
does not need to match that of the above example.
One and only one <firmware> element must be included. The <firmware> element
must also have a version attribute specified. The version must be parsable as
an integer and indicates what version of the Heimdall Firmware Package
specification the package adheres to.
All data is stored as strings, however a <file>'s <id> element must be parsable
as an integer. The <id> value represents the partition ID (according to the
specified PIT file) that the file should be flashed to.
A <firmware>'s <repartition> and <noreboot> elements must also be parsable as
an integer. However, as they represent boolean values, a value of zero ("0")
means false (or disabled) where as a non-zero value (typically "1") means true
(or enabled).
File names are specified relative to the TAR archive in which firmware.xml and
all other files are to be stored. Heimdall Firmware Packages do not support
directories or links, as such file names should only be a name and not a path.
<url> and <donateurl> are the only optional elements, all other elements must
be included.
Click to expand...
Click to collapse
REFERENCE
Heimdall Firmware Packages
This Heimdall Firmware Packages are only for the device Samsung Galaxy S4 LTE+ with ProductCode: GT-I9506!
Click to expand...
Click to collapse
Heimdall Firmware Packages:
- HEIMDALL_OPEN_NEE_I9506XXUAMI3_I9506NEEAMI1_I9506XXUAMHD.tar.gz
Click to expand...
Click to collapse
-->> DOWNLOAD <<--
Click to expand...
Click to collapse
more Heimdall Firmware Packages will be added later.....
How to flash on Linux(Windows and OSX is similar)
This Guide was is tested under following Environment:
Used OS: Linux(Ubuntu 13.10)
Program: Heimdall-Frontend 1.4.0
Under Windows and OSX i didnt tested but it should work since Heimdall was made for it!
Click to expand...
Click to collapse
The very very important thing is the installation procedure including the drivers/libs(Doesnt matter on wich OS).
If its not installed correctly this guide will not work! I dont explain how to install Heimdall!
Click to expand...
Click to collapse
If you dont want to use my guide you can also follow Benjamin Dobell`s OS specific README`s:
Flashing Heimdall Firmware Package with Heimdall Frontend:
- Linux:
Linux/README
- OS X
OSX/README.txt
- Windows
Win32/README.txt
Click to expand...
Click to collapse
Reboot to download mode and if you see following:
ODIN MODE
PRODUCT NAME: GT-I9506
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
QUALCOMM SECUREBOOT: 0x1b
WRITE PROTECTION: Enable
then you can get "Official" state back by following Guide:
Stay in Download Mode! and connect your device with usb cable on a usb port!
Click to expand...
Click to collapse
1.Get Root acces
{
"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"
}
2.Start Heimdall-Frontend
3. Go under Utilities and click "Detect" if you get message "Device detected" go to next step if not you installed Heimdall not correctly!
3.1 Again under Utilities click "Close" if your Device Reboots go to next step if not and get error message you installed Heimdall not correctly!
4. Reboot in to Download Mode again! Go now to Load Package and click "Browse"
5. Click on a Heimdall Firmware Package and then "Open"
6. Wait until Progress bar "Extracting files" is finished!
7. Now click "Load / Customise"
8. Do not touch anything and click "Start"
9. Wait until Progress bar "Flashing procedure" is finished!
10. When everthing is ended! Reboot in to recovery and let device finish the last procedure!
11. Reboot now in to Android set gmail account etc.
12. Reboot to download mode and you will see following:
ODIN MODE
PRODUCT NAME: GT-I9506
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
QUALCOMM SECUREBOOT: 0x1b
WRITE PROTECTION: Enable
Congratulation you have done it!!
Click to expand...
Click to collapse
....
reserved................
last one
After having flashed will I still find all my apps and settings or everything will be deleted?
And the previous recovery (PhilZ Touch)?
Cr4z33 said:
After having flashed will I still find all my apps and settings or everything will be deleted?
And the previous recovery (PhilZ Touch)?
Click to expand...
Click to collapse
It will wipe user data and data on your device so you will not find any apps or settings.
You will get a fresh installed firmware everthing stock and yes your recovery will be stock too
Cheers
Sent from my GT-I9506 using XDA Premium 4 mobile app
xenix96 said:
It will wipe user data and data on your device so you will not find any apps or settings.
You will get a fresh installed firmware everthing stock and yes your recovery will be stock too
Cheers
Sent from my GT-I9506 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Oh. :/
Sent from my Samsung Galaxy S4 LTE+ (GT-I9506) using Tapatalk 2
Cr4z33 said:
Oh. :/
Sent from my Samsung Galaxy S4 LTE+ (GT-I9506) using Tapatalk 2
Click to expand...
Click to collapse
can i install it on samsug s4 e330s?
Numero17 said:
can i install it on samsug s4 e330s?
Click to expand...
Click to collapse
read op its for i9506 device...
Sent from my GT-I9506 using XDA Premium 4 mobile app
xenix96 said:
read op its for i9506 device...
Sent from my GT-I9506 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i try but odin is locked i try with uk firmware (everywhere)
Numero17 said:
i try but odin is locked i try with uk firmware (everywhere)
Click to expand...
Click to collapse
this package work only with heimdall......not with odin.....you didnt read op....
Sent from my GT-I9506 using XDA Premium 4 mobile app
Xenix man...please give me the .pit file for i9506.I really need that and seems i can`t find it anywhere!please!
aresbv2000 said:
Xenix man...please give me the .pit file for i9506.I really need that and seems i can`t find it anywhere!please!
Click to expand...
Click to collapse
ill give it you asap ... before midnight today
Sent from my GT-I9506 using XDA Premium 4 mobile app
xenix96 said:
ill give it you asap ... before midnight today
Sent from my GT-I9506 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thank you mate.thank you sooooo much!i can`t wait for it.i was gonna sell my i9506 today and....boom after reflash get stuck at bootanimation.Thank you again!
aresbv2000 said:
thank you mate.thank you sooooo much!i can`t wait for it.i was gonna sell my i9506 today and....boom after reflash get stuck at bootanimation.Thank you again!
Click to expand...
Click to collapse
Well i advice you when you are able to boot in download mode that you better reinitialize your device with KIES:
Be sure that you installed latest KIES! and odin is not running in background processes!
!!!!ATTENTION!!!! :After this procedure your device will maybe have 4.3 firmware so do this NOT when you dont want KNOX enabled Bootloader!!!!
Click to expand...
Click to collapse
1. Start Kies
2. Click Tools-> Firmware upgrade and initialization
3. Type in model of your phone -> GT-I9506 click OK.
4. Then type serial number of the sticker under battery then click OK
5. There will be info about firmware click OK
6. Follow the instructions on screen and reboot in download mode by pressing volume down key, home button and power button then connect to PC using orginal USB cable click OK
7. Follow the instructions on screen
8. Phone will reboot by itself when all is done correctly!
________________________________________________________________________________
Otherwhise in attachement is the pit file that you requested but handling/flashing with pit files are dangerous ... in worst case if you dont know what you do you can brick your device so be warned !!!
Good Luck :good:
and
Cheers
PS: Please tell me the result .. Thanks
xenix96 said:
Well i advice you when you are able to boot in download mode that you better reinitialize your device with KIES:
Be sure that you installed latest KIES! and odin is not running in background processes!
1. Start Kies
2. Click Tools-> Firmware upgrade and initialization
3. Type in model of your phone -> GT-I9506 click OK.
4. Then type serial number of the sticker under battery then click OK
5. There will be info about firmware click OK
6. Follow the instructions on screen and reboot in download mode by pressing volume down key, home button and power button then connect to PC using orginal USB cable click OK
7. Follow the instructions on screen
8. Phone will reboot by itself when all is done correctly!
________________________________________________________________________________
Otherwhise in attachement is the pit file that you requested but handling/flashing with pit files are dangerous ... in worst case if you dont know what you do you can brick your device so be warned !!!
Good Luck :good:
and
Cheers
PS: Please tell me the result .. Thanks
Click to expand...
Click to collapse
Thank you my friend! I solved the problem.
It wasn`t the .pit file the problem for me.
I have explained how i`ve successfully flash the latest 4.3 firmware with no errors in this thread.
But again...THANK YOU for the .pit file! It`s a good thing to having it around here! Maybe I will need it sometime, but not this time!
Have a nice evening!
So is Knox flag tripped from 0 to 1 or not??
Sent from my GT-I9506 using XDA Premium 4 mobile app
xenix96 said:
....
Click to expand...
Click to collapse
Hello
control for windows too? (Command)
Envoyé de mon GT-I9305 en utilisant Tapatalk
Related
[TOOLKIT] UNIFIED ANDROID TOOLKIT - SAMSUNG GALAXY GEAR - Drivers, Root, Recovery + MORE
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports a multitude of Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus modules]
* Various Root options using insecure boot image or custom recovery
* 1-Click For All to Unlock, Root, Rename the Restore Files and install busybox [Nexus modules]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung modules]
* Fix “Superuser/SuperSU has stopped” message after rooting [Samsung modules]
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Phone Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Install BusyBox on your device
* Install Samsung Knox notification disabler on your device [Samsung modules]
* Install Root checker on your device [to be added to the Nexus modules]
* Extras, Tips and Tricks section with downloadable device user guide
* Auto Update ToolKit to latest available version at startup [PRO ONLY FEATURE]
* Check for latest versions of Superuser [root] and custom Recovery images [PRO ONLY FEATURE]
* Program up to 10 Quickpick slots and run them very quickly [PRO ONLY FEATURE]
* Mods section to automatically perform certain tasks on your phone
* Download Stock Firmware Image for extracting and flashing
* Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus modules]
* Flash Custom Recovery or Stock Firmware Image to device
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP or Stock Recovery without Flashing it [Nexus modules]
* Boot or Flash .img Files directly from your PC [Nexus modules]
* Install a single apk or multiple apk’s to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to various Modes automatically
* Display Important Information about your device
* Display various Help and Information screens and save a screenshot to your pc/send to default printer
* Many many more features
————————————————————–
Supported devices and latest supported builds *HERE*
————————————————————–
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--------------------------------------------------------------
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE2: As the exe files are not Digitally Signed with a Microsoft Certificate they ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted on first run. If this happens restore the file and exclude it from future scans to use it. This seems to happen mostly on AVG Free and Norton which is why I switched to BitDefender which is much better.
Credits: ChainsDD for Superuser, Chainfire for SuperSU, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, fOmey for TWRP for the Galaxy Gear
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE YOUR DEVICE. NO MAIN FUNCTIONS ARE RESTRICTED.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
IF YOU FIND THIS PROGRAM USEFUL PLEASE CONSIDER DONATING TO YOUR CHOSEN DEVICE TO GET AN ACTIVATION CODE FOR THE PRO VERSION. YOU WILL FIND THE PRO FEATURES VERY USEFUL, GET UPDATES DIRECTLY FROM THE PROGRAM AND SUPPORT FUTURE DEVELOPMENT. WITHOUT DONATIONS DEVELOPMENT WILL NOT BE ABLE TO CONTINUE.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
2. USING THE UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. The basic Toolkit files are included in the full install package but if you select a device then the working folders will be created and the device files downloaded. Once the files have been extracted the Toolkit will ask if you want to check if an Update is available (for pro users to download/install). If you type ‘no’ then you will be taken to the Model/Build selection screen where you can do a number of things:
Type ’00' to enter your activation code and enable pro features, ‘i’ will take you to the Information and Help Section, ‘a’ will give you information on how to add support for a new build, ’99' will take you to the Basic Toolkit for quick use or if you do not have a supported device and want to perform general android tasks.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest custom recovery and superuser files available (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers.
The Information section which you can get to from the Model Selection screen or from the Main Menu has a wealth of help and frequently asked questions. If you need help then please look there first before asking questions in the thread.
--------------------------------------------------------------
USEFUL INFORMATION
Enable Developer options for usb debugging
Go to Settings, Gear Info, About Gear and tap on Software version 7 times until it says you are now a developer. You can now go to Settings, Gear Info and enable USB debug.
How to get into Recovery Mode
1. Open the charging case (if the device is in it) and hold the power button [on the side] in for about 10 seconds until you see a “Rebooting…” message on the screen.
2. Release the power button then press it 3 times quite fast. Wait a second then press it 3 times again and a screen should appear with 3 reboot options [continue, download and recovery].
3. Tap the power button to scroll down to recovery then hold the power button in for 5 seconds and release.
You should now boot to recovery.
How to get into Download Mode (For Odin)
1. Open the charging case (if the device is in it) and hold the power button [on the side] in for about 10 seconds until you see a “Rebooting…” message on the screen.
2. Release the power button then press it 3 times quite fast. Wait a second then press it 3 times again and a screen should appear with 3 reboot options [continue, download and recovery].
3. Tap the power button to scroll down to download then hold the power button in for 5 seconds and release.
You should now boot to download mode.
--------------------------------------------------------------
ChangeLog
Unified Android ToolKit v1.2.6 [Galaxy Gear V1.0.0] 31st March 2014
+First version of Samsung Galaxy Gear ToolKit Module released
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
**FAQ**
Q. Help me I can't find my build in the Model Selection Screen
The Toolkit includes a selection of Insecure Boot Images to cover all the different builds available. As there are very many different builds it is impossible to include an image for every single build but some builds share the same Boot Image. If you have a build that isnt listed on the Model Selection Screen you can therefore use a similar build. The best way to go is up to the next available build as it should offer more compatibility with the build you are using but if that isn't available then try the next build below your one as it should still be almost identical as long as it is the same version (ie. 4.1.1).
The Model Selection Screen is there so that if a task in the ToolKit requires an insecure kernel [to perform adb root commands] and your phone doesnt already include one, a compatible boot image [with an insecure kernel included] can be flashed to provide adb root access.
If you have a Custom Rom flashed to your phone then it will most probably have an insecure kernel included so it doesn't really matter if your build is not listed on the Model Selection Screen and when asked [by certain functions] if you have an insecure kernel on your phone you can answer 'yes'. However if the function fails then your kernel may not be insecure in which case you can flash one from the ToolKit. If you need to do this make sure the right build [or closest available build] is set so you flash the right image for your phone.
----------------------------------------------------------------------------
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF like removing system apps.
----------------------------------------------------------------------------
Q. Why do I need to back up my IMEI/EFS and how do I do it?
There well protected section of your device that is virtually immune to any kind of flashing and manipulation (unless of course you know how to access it). This part of the device contains information such as IMEI (or MEID and ESN in the case of CDMA devices), programming parameters for the device such as your account information (phone number, etc), data provisioning parameters, and a whole bunch of other things that, when not handled properly, can render a device completely useless. All of these are contained in the infamous \EFS folder. If anything messes with your EFS folder, unlike flashing a device (which could potentially lead to bricks as well) it could render your device completely useless as it will no longer be recognized by your carrier. If you are not planning on flashing anything to your device and want to stay on pure Stock then you may never have any problems but it is still advisable to backup this information just in case (better to be safe than sorry).
----------------------------------------------------------------------------
Q. Does flashing a custom image increase my flash counter?
Any image that is flashed via Odin that has been modified will increase the flash counter that can be viewed in the Download Mode on your device (if booted by holding the Volume Down, Home and Power buttons). You can reset the flash counter using an app by Chainfire called Triangles Away and can find instructions on how to use that in the Downloads section in the Toolkit.
----------------------------------------------------------------------------
Q. Will flashing Stock ROM via odin using the toolkit replace everything that was flashed before? recovery? etc?
Yes a Stock Image flashed via Odin will replace all your key partitions (boot, recovery, system) with the stock firmware. If you want to reset the phone back to an 'out of the box' state then you want to enter recovery and do a wipe first which will reformat your userdata partition.
----------------------------------------------------------------------------
Q. I flashed Custom Recovery but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on certain Stock Android Builds that will reflash the Stock Recovery if you flash CWM on a Stock Rom.
Use Root Explorer to Mount the system folder as R/W (or use a free app from Google Play such as ES File Explorer). Rename the files /system/recovery-from-boot.p and /system/etc/install-recovery.sh (requires root). Now when you flash Custom Recovery it will NOT be overwritten after a reboot. You can also do this via the Toolkit.
----------------------------------------------------------------------------
Q. My AntiVirus program says the Toolkit files may be harmful
The exe compiled files are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) may pick it up as potentially harmful when it is not. They will pick up ANY file that doesn't contain a purchased Microsoft certificate in the same way. Just Restore the deleted file and exclude it from further scans and it will be fine. Or switch to a better AntiVirus program such as BitDefender.
----------------------------------------------------------------------------
Q. I flashed the Toolkit Boot Image, now my wifi + bluetooth won't work
The boot images are made from Stock with only needed changes made to the insecure boot images [modified adbd, default.prop and rc.local edited] and will work on all stock roms. If you flash them to a custom rom and the rom has been altered or uses a custom boot image then it will boot but certain modules may not load such as wifi or bluetooth. In this case you can use the boot image to root or perform adb root functions but will need to flash back the boot image for the custom rom to get other functions working again. This is not a fault of the Toolkit but a difference to stock in the custom rom.
----------------------------------------------------------------------------
Q. I am having trouble getting adb working with the drivers installed
Try switching your connection type from media (MTP) mode to camera mode (P2P). To do this open the notification area, click where it says connected as and change from MTP to PTP.
----------------------------------------------------------------------------
Q. I want to send my device back for warranty purposes
1. Follow the instructions to reset your flash counter with TriangleAway.
2. Download and flash a Stock Firmware image from the download section.
3. Boot into Stock Recovery and perform a wipe/factory reset
.
Your internal storage will be formatted and data and cache wiped. Your device should now be back to an out-of-the-box FULLY STOCK state with the flash counter [shown if you boot to download mode manually] reset and ready to send back.
----------------------------------------------------------------------------
Q. When connecting the phone I get 'USB Device not Recognized' and no serial number shows in the ToolKit
I actually had this problem recently and what fixed it for me was to make sure that the drivers have been installed, then shut my phone down plug the usb cable in and restart it. The phone booted up and the device was recognized and drivers installed correctly. May not work for everyone but worth trying.
----------------------------------------------------------------------------
Q. "Superuser/SuperSU has stopped" message after rooting
After updating Samsung device to newer builds of Android [4.3 and later] which contains the new security from Samsung "Samaung KNOX", you might face a problem if you tried to root your device.
This might happen because of KNOX security, it blocks/disables the Superuser app and you will see this notification after the first boot:
"Unfortunately, SuperSU has stopped" or "Unfortunately, Superuser has stopped" depending on the root method you used.
The easiest way to fix this problem is by installing the superuser apk file. Select option 6 from the Rooting Section and the Toolkit will attempt to extract the superuser.apk file from the root zip file in the Root folder and if successful it will then be installed. You can then run the app [Superuser or SuperSU] from the apps list. A warning message will pop up saying Samsung KNOX has been detected and ask if you want to try and disable it. Click OK, KNOX should be disabled and your device should now be properly rooted.
There is more Information/Help at http://www.skipsoft.net/?page_id=1269
**VIDEOS**
**UPDATES**
Well, there's a name I'm happy to see in Gear dev! Thanks mskip!
Thank you for the application.
Chosed option 5. Allinone. Now in Odin and starting the flashing process. How long is the process supposed to take. Or am I not just patient enough lol?
Sent from my SAMSUNG-SM-N900A using Tapatalk
darkchyldx101 said:
Chosed option 5. Allinone. Now in Odin and starting the flashing process. How long is the process supposed to take. Or am I not just patient enough lol?
Sent from my SAMSUNG-SM-N900A using Tapatalk
Click to expand...
Click to collapse
Flashing twrp only takes a few seconds. What exactly have you doneand what is happening on the pc and watch? I will start making some youtube vids soon to help users.
Mark.
Installed drivers. Started toolkit. Choose my Gear section. Choosed option 5 for Allinone root, recovery, busybox, backups. Then Watch went into download mode. USB debug enabled. Odin opened. I put tar file in pda slot toolkit provided. Hit start. Then it hangs for awhile.
Sent from my SAMSUNG-SM-N900A using Tapatalk
Hey Mskip, I have used a few of your toolkits in the past and have found all of them very useful. I have donated to upgrade to the pro version of all of them. I was just curious if you were planning on doing anything for the Samsung Galaxy Note Pro 12.2 tablet. I know there is the CF-Auto tool but I need something to root the Verizon version which is the SM-905V. Thank you in advance and keep up the excellent work!
Question
First thank you for your hard work in coming up with this process!!
Do we know if this will work with the newest galaxy gears? (gear 2, gear 2 neo and gear fit) My understanding is these devices aren't running android at all but an OS called Tizen. I know very little of this OS but I can say that the UI of my neo is nearly identical to my OG gear which makes me wonder if this method will work.
kingnarkissos said:
First thank you for your hard work in coming up with this process!!
Do we know if this will work with the newest galaxy gears? (gear 2, gear 2 neo and gear fit) My understanding is these devices aren't running android at all but an OS called Tizen. I know very little of this OS but I can say that the UI of my neo is nearly identical to my OG gear which makes me wonder if this method will work.
Click to expand...
Click to collapse
The new Gear smartphones work on Tizen as you said and the Galaxy Gear module will not work with them. I don't have a Gear 2 yet and don't know if its even rootable but if anything can be done with it in the future I will definitely look at adding it.
Mark.
Hi Op, I have used your toolkit on my nexus 5 and other samsung phones..so first thanks a lot man. Now I just bought a new gear. Whenever I select option 5 allinone and try to go to the folder in my C drive I dont see any tar file. I selected version 4.2.2 in the start. It says no extra files will be downloaded. I really want to root and install TWRP.
pro version not seeing tar.files in galaxy gear !!!!
Hi, just to say ive donated tonite to buy the pro version and when i go to root my galaxy gear , it gives me the option to enter number 3/root/unroot options/ then go to the root galaxy gear folders and select the root file for odin, but there are no files there !! can you help as i have donated but unable to root my galaxy gear. I can supply you with the pro code when i donated to prove i did buy.
---------- Post added at 09:20 PM ---------- Previous post was at 09:18 PM ----------
viny2cool said:
Hi Op, I have used your toolkit on my nexus 5 and other samsung phones..so first thanks a lot man. Now I just bought a new gear. Whenever I select option 5 allinone and try to go to the folder in my C drive I dont see any tar file. I selected version 4.2.2 in the start. It says no extra files will be downloaded. I really want to root and install TWRP.
Click to expand...
Click to collapse
Yeah im getting the same problem !!
any support please
Hi, are we getting any support please ?
has this thread been closed !!
read007 said:
Hi, are we getting any support please ?
Click to expand...
Click to collapse
Hi all, i posted last on the 27th may and have had no replys to my post, any help please
read007 said:
Hi all, i posted last on the 27th may and have had no replys to my post, any help please
Click to expand...
Click to collapse
read007 said:
Hi, just to say ive donated tonite to buy the pro version and when i go to root my galaxy gear , it gives me the option to enter number 3/root/unroot options/ then go to the root galaxy gear folders and select the root file for odin, but there are no files there !! can you help as i have donated but unable to root my galaxy gear. I can supply you with the pro code when i donated to prove i did buy.
---------- Post added at 09:20 PM ---------- Previous post was at 09:18 PM ----------
Yeah im getting the same problem !!
Click to expand...
Click to collapse
viny2cool said:
Hi Op, I have used your toolkit on my nexus 5 and other samsung phones..so first thanks a lot man. Now I just bought a new gear. Whenever I select option 5 allinone and try to go to the folder in my C drive I dont see any tar file. I selected version 4.2.2 in the start. It says no extra files will be downloaded. I really want to root and install TWRP.
Click to expand...
Click to collapse
Hi I just got a gear and am about to root... And wanted to make sure this toolkit was fully functional?
I see the most recent post were having trouble.. Was it fixed?
Sent from my Nexus 5 using Tapatalk
Its not donation, its purchasing and no i dont want to buy your product, you could have warned me before i did all of this. good day
Hey MSkip, I guess the latest updates put the Gear 1 on Tizen also. Your program ask to make the tar file and upload. I was wondering if you already have this update and are working on adding that to your program. Thanks. I also donated for the gear but have not done anything to it yet. I may root / install TWRP according to the forum threads in the mean time. Here is a link to the latest rom unrooted http://samsung-updates.com/details/30439/Galaxy_Gear/SM-V700/BTU/V700XXUCNF1.html it's the Great Britain file, but from what I understand it's the same for the US. Take it easy.
Chris
UPDATE: Tizen became really boring...so I'm back to Null rom. What was I thinking, it's nice and slick and good on battery. But even with root and setting up SDB (Sammy's ADB) and trying to customize a clock it was no longer exciting. So I came back to what I know and can use the MSkip's tool again.
Chris
Great work! Thanks!
Koodo Mobile: http://downloadmirror.co/android/tq/G900W8VLU1COI4_G900W8OYA1COI4_KDO.zip
SaskTel: http://downloadmirror.co/android/tr/G900W8VLU1COI4_G900W8OYA1COI4_BWA.zip
Virgin Mobile: http://downloadmirror.co/android/ts/G900W8VLU1COI4_G900W8OYA1COI4_VMC.zip
Bell Mobil: http://downloadmirror.co/android/tt/G900W8VLU1COI4_G900W8OYA1COI4_BMC.zip
Rogers: http://downloadmirror.co/android/tu/G900W8VLU1COI4_G900W8OYA1COI4_RWC.zip
Telus: http://downloadmirror.co/android/tv/G900W8VLU1COI4_G900W8OYA1COI4_TLS.zip
Fido Mobile: http://downloadmirror.co/android/tw/G900W8VLU1COI4_G900W8OYA1COI4_FMC.zip
Source: http://www.theandroidsoul.com/downl...1-update-g900w8vlu1coi4-with-root-info-85381/
Nice, which I've would I download for Wind Mobile?
If Flash fire shows protected on some partitions does that mean I have to use Odin on PC?
Spacemonkie4207 said:
Nice, which I've would I download for Wind Mobile?
Click to expand...
Click to collapse
The Wind Mobile firmware is always released under its parent company's name, Globalive, which is not listed here. It's CSC is GLO if you can find it elsewhere. But it really doesn't matter at all. The last few releases that were labelled Globalive were literally just the Bell version renamed. You can use any of the firmware versions above if you want. I used the Telus one a couple of times, just because I have a grudge against Bell and Rogers. But it makes absolutely no difference.
hexavoodoomal said:
The Wind Mobile firmware is always released under its parent company's name, Globalive, which is not listed here. It's CSC is GLO if you can find it elsewhere. But it really doesn't matter at all. The last few releases that were labelled Globalive were literally just the Bell version renamed. You can use any of the firmware versions above if you want. I used the Telus one a couple of times, just because I have a grudge against Bell and Rogers. But it makes absolutely no difference.
Click to expand...
Click to collapse
Where can I find the proper apn settings?
Zehlek said:
If Flash fire shows protected on some partitions does that mean I have to use Odin on PC?
Click to expand...
Click to collapse
use odin in pc
Spacemonkie4207 said:
Where can I find the proper apn settings?
Click to expand...
Click to collapse
Google it.
Whats new ?
Whhats new on 5.1.1 theme store coming out with this ? What can i find
Plz some one upload captures
brayhanrd said:
Whhats new on 5.1.1 theme store coming out with this ? What can i find
Plz some one upload captures
Click to expand...
Click to collapse
I have 900M so i cant install, maybe anyone can post anything, but 99% sure didnt have themes
Enviado de meu SM-G900F usando Tapatalk
brayhanrd said:
Whhats new on 5.1.1 theme store coming out with this ? What can i find
Plz some one upload captures
Click to expand...
Click to collapse
I think it is more under the hood updates
Sent from my SM-G900W8 using Tapatalk
Anyone figure out how to root this version. I tried to install TWRP and flashed Super SU, cleared cache and dalvik but it just boot loops on first boot after flashing firmware. Tried to install after it booted and set up user name and accounts by the same process but I had the same results.
Any suggestions?
Thanks.
daroco said:
Anyone figure out how to root this version. I tried to install TWRP and flashed Super SU, cleared cache and dalvik but it just boot loops on first boot after flashing firmware. Tried to install after it booted and set up user name and accounts by the same process but I had the same results.
Any suggestions?
Thanks.
Click to expand...
Click to collapse
Only with custom kernel
Enviado de meu SM-G900F usando Tapatalk
Thanks bro! I thought about it but I didn't think it mattered. I'll give it a go.
No dice as of yet, custom kernels are not booting either, good thing I had the sense to do a bacup first
☺
daroco said:
Thanks bro! I thought about it but I didn't think it mattered. I'll give it a go.
No dice as of yet, custom kernels are not booting either, good thing I had the sense to do a bacup first
Click to expand...
Click to collapse
The way I usually root is to flash CF-Auto-Root-kltecan-kltevl-smg900w8.tar using odin. Can you try that?
I haven't updated yet until I'm sure root is there as I gave the phone to my wife.
thanks
Still bootloops when I flashed CF-Autoroot. it also installed the original recovery from another BL version. I reflashed TWRP and cleared cache and dalvik (not that I expected it to do much) but still the same. restored a nandroid and I had all kinds of apps FC. End result was to factory reset the phone to be in a stable condition. If this was a car I could get this damn thing running right! I should have learned more about programming while I was in school...... 2 kids and a mortgage I have no time for it now.
[HOWTO] Root your 5.1.1 G900W8VLU1COI4 firmware
daroco said:
Anyone figure out how to root this version. I tried to install TWRP and flashed Super SU, cleared cache and dalvik but it just boot loops on first boot after flashing firmware. Tried to install after it booted and set up user name and accounts by the same process but I had the same results. [...]
Click to expand...
Click to collapse
mauriicio21 said:
Only with custom kernel
Click to expand...
Click to collapse
Not exactly
You need stock kernel but with sepolicy patched in ramdisk, according to @Chainfire's method.
I think I could help all G900W8's users
Rooting procedure (requires TWRP or CWM):
1. Download patched kernel and the latest SuperSU (2.52+):
>> KERNEL_G900W8VLU1COI4_Stock_patched.zip <<
>> SuperSU BETA by @Chainfire <<
2. Copy both zip files to phone or extSdCard
3. Go to TWRP / CWM and flash both files one by one. Order does not matter
4. Reboot the phone.
5. Enjoy your rooted 5.1.1 firmware
-------------------------------------------------------------------------------------------
It is time to say that I also need your help as there is no 5.1.1 firmware for other S5's variants yet. I need updated SELinux contexts and and permissions list from your 5.1.1 firmware (in all Snapdragon S5 variants contexts/permissions are the same). I require it as I would like to be well prepared with my custom ROMs for G900F/FD. I believe that Android 5.1.1 for G900F/FD is just a matter of a few days...
Please do as follow while running G900W8VLU1COI4 firmware:
- Install Terminal Emulator from Play Store (https://play.google.com/store/apps/details?id=jackpal.androidterm)
- Type commands as follow:
Code:
[COLOR="Red"]su[/COLOR]
cd /system
ls -aRZ > /storage/emulated/0/test1.txt
ls -aRn > /storage/emulated/0/test2.txt
- you will find above txt files in the internal sdcard's root directory - please zip these files and post here as attachment
NOTE1: Rooted phone is not a MUST. If you have not rooted 5.1.1 firmware - just bypass "su" command and ignore "Permission denied" messages. In fact it will also do the work as it should.
NOTE2: Don't worry. Your /system partition will remain untouched by these actions. No private data will be read as all private contents are stored on /data
_alexndr said:
Not exactly
You need stock kernel but with sepolicy patched in ramdisk, according to @Chainfire's method.
I think I could help all G900W8's users
Rooting procedure (requires TWRP or CWM):
1. Download patched kernel and the latest SuperSU (2.52+):
>> KERNEL_G900W8VLU1COI4_Stock_patched.zip <<
>> SuperSU BETA by @Chainfire <<
2. Copy both zip files to phone or extSdCard
3. Go to TWRP / CWM and flash both files one by one. Order does not matter
4. Reboot the phone.
5. Enjoy your rooted 5.1.1 firmware
------------------------------------------------------
It is time to say that I also need your help as there is no 5.1.1 firmware for other S5's variants yet. I need updated SELinux contexts and and permissions/symlinks list from your 5.1.1 firmware. I require it to be well prepared with my custom firmware for G900F. I believe that Android 5.1.1 for G900F is just a matter of a few days.
Please do as follow while running G900W8VLU1COI4 firmware:
- Install Terminal Emulator from Play Store (https://play.google.com/store/apps/details?id=jackpal.androidterm)
- Type commands as follow:
Code:
[COLOR="Red"]su[/COLOR]
cd /system
ls -aRZ > /storage/emulated/0/test1.txt
ls -aRn > /storage/emulated/0/test2.txt
- you will find above txt files in the internal sdcard's root directory - please zip these files and post here as attachment
NOTE1: Rotted phone is not a MUST. If you have not rooted 5.1.1 firmware - just bypass "su" command and ignore "Permission denied" messages. In fact it will also do the work as it should.
NOTE2: Don't worry. Your /system partition will remain untouched by these actions. No private data will be read as all private contents are stored on /data
Click to expand...
Click to collapse
Do you Know how can i get spanish on this Vertion plz. ? @_alexndr
_alexndr said:
Not exactly
You need stock kernel but with sepolicy patched in ramdisk, according to @Chainfire's method.
I think I could help all G900W8's users
Rooting procedure (requires TWRP or CWM):
1. Download patched kernel and the latest SuperSU (2.52+):
>> KERNEL_G900W8VLU1COI4_Stock_patched.zip <<
>> SuperSU BETA by @Chainfire <<
2. Copy both zip files to phone or extSdCard
3. Go to TWRP / CWM and flash both files one by one. Order does not matter
4. Reboot the phone.
5. Enjoy your rooted 5.1.1 firmware
------------------------------------------------------
It is time to say that I also need your help as there is no 5.1.1 firmware for other S5's variants yet. I need updated SELinux contexts and and permissions list from your 5.1.1 firmware (in all Snapdragon S5 variants contexts/permissions are the same). I require it as I would like to be well prepared with my custom ROMs for G900F/FD. I believe that Android 5.1.1 for G900F/FD is just a matter of a few days...
Please do as follow while running G900W8VLU1COI4 firmware:
- Install Terminal Emulator from Play Store (https://play.google.com/store/apps/details?id=jackpal.androidterm)
- Type commands as follow:
Code:
[COLOR="Red"]su[/COLOR]
cd /system
ls -aRZ > /storage/emulated/0/test1.txt
ls -aRn > /storage/emulated/0/test2.txt
- you will find above txt files in the internal sdcard's root directory - please zip these files and post here as attachment
NOTE1: Rotted phone is not a MUST. If you have not rooted 5.1.1 firmware - just bypass "su" command and ignore "Permission denied" messages. In fact it will also do the work as it should.
NOTE2: Don't worry. Your /system partition will remain untouched by these actions. No private data will be read as all private contents are stored on /data
Click to expand...
Click to collapse
Hope this helps, thanks for your help.
Here you go!
Just confirmed the camera can shoot in RAW format
First of all i want to make sure one thing to all the developers and users in this forum. I am not the developer of this rom. I am just sharing the work of a Great Developer. So i request everyone not to use any feature of this rom in yours. If you want to, then please ask proper permissions from the actual developer and give proper credits. Please must follow this
CAUTION: I will not be responsible for anything that will happen to your device while flashing or using this rom. Not even the developers too. You are solely responsible for everything that will happen to your device while using this ROM. Mind that Dudes
READ THIS FIRST
1. I am sharing this work here from some other forum with the permission of the developer.
2. So please don't ask for ETA's of updates.
3. If any one facing any new bug, please report here, but don't ask questions like "when it will be solved"?
4. It will be notified to the developer and it will be resolved off gradually.:good::good:
5. Don't use Harsh Language while posting in the comment sections.
Prerequisites:
1. You Must have the Stock Kitkat 4.4.2 in your phone before flashing this.
2. You must have the CWM recovery/Philz Recovery installed in your phone (Highly Recommended)
ROM FEATURES
1. Multiwindow
2. UPSM Mode
3. Private Mode
4. Toolbox
5. Statusbar Settings
6. Advanced Power-Off Settings
7. Animation Settings
8. Dynamic Statusbar
9. One Handed Operation
10. Circle Sidebar
11. Gesture Anywhere
12. Guest Mode
13. USB Fast Charge Support
14. Themes Support and So On........
Installation Instructions
1. First download the Firmware Package from below links.
For GT I9192 Users: https://yadi.sk/d/FwwmUW6knq3rS
For GT I9190 Users: https://yadi.sk/d/8M2V0av6npiug
For GT I9195 Users: https://yadi.sk/d/cl2m5Ujtnpisi
2. Flash the above firmware through ODIN. Complete the setup
3. Then download the following ROM file...
MOD EDIT
Links removed for containing warez
4. Download the rom from above link. Put it in your sdcard and flash via recovery.
5. The GT I9190 users can flash the rom and reboot the phone. No fixes are needed.
6. For GT I9192 and GT I9195 users, download the following corresponding fixes and place it in sdcard along with the Rom file. Flash the fix immediately after flashing the rom and then reboot. otherwise you may results in bootlop.
For GT I9192 Users: https://yadi.sk/d/QGSI0M8ioXyxe
For GT I9195 Users: https://yadi.sk/d/9P-gP3MPoXyzL
7. That's it..!!!!!
Post installation instructions
1. After flashing the ROM and fixes. No setup screen will come and dont get panic.
2. Also the phone language will be in Russian or serbian i think. Don't panic for that too.
3. Just go to settings (language is not needed for to select settings lol) and look for the language and input option...you can easily find it out. Or other wise check the screenshots. And in that you can see the option for language change. Change it to whichever language you want and phone will gets rebooted. Then you can enjoy all the features of the ROM..
4. Attached the screenshots in post #2.
Updates
Update 5.2.2
[/COLOR]
Update 5.3
http://forum.xda-developers.com/showpost.php?p=66420894&postcount=112
Download the above updates and flash through recovery. That's it...[/FONT]
Bugs
1. The GT I9192 users will not be able to see, in which sim they had received the calls in the call logs menu. To solve this problem, use "Zero Dialer" app from the playstore, it'll show you the sim numbers of the calls received.
2. Apps which has the drop down menu option will force closes whenever you press it. (mostly the payment apps only. The solution to this is you can use browser (instead of the app) for that :laugh::laugh::laugh
3. For GT I9192 users, system ui fc occurs if you make calls with the Heads Up option enabled. So don't use that
Miscellaneous Downloads/Fixes
S Planner Fix:: https://yadi.sk/d/F6RCXEfor6JLs
Highly Debloated Stock KK Firmware [GT I9192 only]: https://www.androidfilehost.com/?fid=23991606952601631
Alexax66 Kernel v0.1.2 for proper working of Init.d [for I9192 only]: https://yadi.sk/d/ZrbLcaxLprxiF
Smart manager Zip : https://yadi.sk/d/wRM32G-2nxvw2
Google Contacts and Calender Sync : https://yadi.sk/d/STiGJ3aFkTwjo
Kids Mode Zip: https://yadi.sk/d/D06Jn5Btee3G3 [This kids mode is having some problems, some force closes will occurs, so try this only you need this badly!!!!!!!]
Fantastic Audio Mod
http://forum.xda-developers.com/showpost.php?p=66441061&postcount=121 [Recommended only for music hearing geeks]
For themes: Go to the following link and download the theme packages and flash it through Recovery
http://forum.xda-developers.com/galaxy-s4-mini/themes-apps/theme-collection-theme-chooser-t3060241
For Fonts: Go to the following link, download the Samsungsans apk file and replace it with the original one in the system/app folder
http://forum.xda-developers.com/galaxy-s4-mini/themes-apps/fonts-styles-4-mini-t3119509
(also attached the CWM Recovery files for GT I9192 Only in post #3)
CREDITS
*Ploiki
*Chernoknijnik
*Narkoman88
Additional Credits
"Alexax66" for the Kernel
"Unknown 'VK Forum' Friends" for Additional files and YandexDisk Links
"Silviumik" for the Debloated Stock Firmware for Duos Version
"Fanion" for the themes
"Petravergil" for the fonts
"ruhul5" for the Google Drive Link
"yogi78" for checking the kernel and private mode for Duos Version
"syednawaz" for helping out the GT I9190 users
and most importantly "The XDA Community"
Update 5.3
http://forum.xda-developers.com/showpost.php?p=66420894&postcount=112
Download the above updates and flash through recovery. That's it...[/FONT][/SIZE]
Bugs
1. The GT I9192 users will not be able to see, in which sim they had received the calls in the call logs menu. To solve this problem, use "Zero Dialer" app from the playstore, it'll show you the sim numbers of the calls received.
2. Apps which has the drop down menu option will force closes whenever you press it. (mostly the payment apps only. The solution to this is you can use browser (instead of the app) for that :laugh::laugh::laugh
3. For GT I9192 users, system ui fc occurs if you make calls with the Heads Up option enabled. So don't use that
Miscellaneous Downloads/Fixes
S Planner Fix:: https://yadi.sk/d/F6RCXEfor6JLs
Highly Debloated Stock KK Firmware [GT I9192 only]: https://www.androidfilehost.com/?fid=23991606952601631
Alexax66 Kernel v0.1.2 for proper working of Init.d [for I9192 only]: https://yadi.sk/d/ZrbLcaxLprxiF
Smart manager Zip : https://yadi.sk/d/wRM32G-2nxvw2
Google Contacts and Calender Sync : https://yadi.sk/d/STiGJ3aFkTwjo
Kids Mode Zip: https://yadi.sk/d/D06Jn5Btee3G3 [This kids mode is having some problems, some force closes will occurs, so try this only you need this badly!!!!!!!]
Fantastic Audio Mod
http://forum.xda-developers.com/showpost.php?p=66441061&postcount=121 [Recommended only for music hearing geeks]
For themes: Go to the following link and download the theme packages and flash it through Recovery
http://forum.xda-developers.com/galaxy-s4-mini/themes-apps/theme-collection-theme-chooser-t3060241
For Fonts: Go to the following link, download the Samsungsans apk file and replace it with the original one in the system/app folder
http://forum.xda-developers.com/galaxy-s4-mini/themes-apps/fonts-styles-4-mini-t3119509
(also attached the CWM Recovery files for GT I9192 Only in post #3)
CREDITS
*Ploiki
*Chernoknijnik
*Narkoman88
Additional Credits
"Alexax66" for the Kernel
"Unknown 'VK Forum' Friends" for Additional files and YandexDisk Links
"Silviumik" for the Debloated Stock Firmware for Duos Version
"Fanion" for the themes
"Petravergil" for the fonts
"ruhul5" for the Google Drive Link
"yogi78" for checking the kernel and private mode for Duos Version
"syednawaz" for helping out the GT I9190 users
and most importantly "The XDA Community"
To change Language
To change the language after setup see the following screenshots...
CWM Recovery for Duos Users
Flash Via Odin
More Screenshots
there is a problem in power menu doesn't appear
Mo7amed_Gom3a said:
there is a problem in power menu doesn't appear
Click to expand...
Click to collapse
Activate the developer option, go to that and in the last you will see an option called "advanced system settings".
In that, you will see an option with the name "Power off button setting". There you will have all the options for the power menu..
Do not install this !! Its full of viruses and adds !!!! Once you installed you can't uninstall the adds and viruses !!
djares21 said:
Do not install this !! Its full of viruses and adds !!!! Once you installed you can't uninstall the adds and viruses !!
Click to expand...
Click to collapse
Viruses and adds?!?!?!?!
I don't understand.....
You talking about the stagefright bug?!?!?!
Sent 4m My S4 Mini Duos with S5 "STE" Rom by PLOIKI
djares21 said:
Do not install this !! Its full of viruses and adds !!!! Once you installed you can't uninstall the adds and viruses !!
Click to expand...
Click to collapse
Also what you mean by, "Once you installed you can't uninstall the adds and viruses?" LOL....Its funny....
Because for the past 2 weeks i am using this rom and before that also i used this and i changed to CM 13 and some other MM ports for short time. No problems arised while changing....
Now due to some reasons, i revert back to this.... And moreover some of the users here personally contacted me to give the links of this rom. That's why i created this thread....
And one more thing i am not making any fun of you. But i want you to make clear about the "Viruses and Adds" thing??!!!!!
Was really looking forward to trying it out, what viruses :crying:
Init.d will force close
Hi
If u get Init.d will force close use this kernel Alexax66 0.1.2 for I9192
Hello there. my phone never had kitkat officially so i am using s6&N5 port(which is 4.4).
do i still have to download I9190XXUCOC1_SER.zip? or can i directly flash S5_STE_Rom_v.5.2.1.zip.
because i heard kitkat update bootloader and i do not want my bootloader to be updated as i may want to go for jelly bean.
btw i updated s6 port(kitkat) from NEW S6 n N5 Project thread from jellybean. and worked fine.
okay i flashed it over s6 port(4.4.4). but i got random restarts. then i went in twrp recovery and wiped everything and freshed install only flash S5_STE_Rom_v.5.2.1.zip file. still crashed. i guess i have to follow your instruction but as i said i cant install kitkat stock firmware as it may update the bootloader.
syednawaz said:
okay i flashed it over s6 port(4.4.4). but i got random restarts. then i went in twrp recovery and wiped everything and freshed install only flash S5_STE_Rom_v.5.2.1.zip file. still crashed. i guess i have to follow your instruction but as i said i cant install kitkat stock firmware as it may update the bootloader.
Click to expand...
Click to collapse
You can remove the bootloader files from the stockfirmware.tar file using total commander and flash the firmware
Sent from my ASUS_T00J using XDA Free mobile app
DarkFrenzy said:
You can remove the bootloader files from the stockfirmware.tar file using total commander and flash the firmware
Sent from my ASUS_T00J using XDA Free mobile app
Click to expand...
Click to collapse
little bit more help please. How to do it? which file to delete? and total commander for pc right?
syednawaz said:
little bit more help please. How to do it? which file to delete? and total commander for pc right?
Click to expand...
Click to collapse
Here is a tutorial
http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html?m=1
Rename .tar.md5 to .tar and open using total commander and just
Just remove everything except system.img and boot.img
Then flash from odin
Sent from my ASUS_T00J using XDA Free mobile app
DarkFrenzy said:
Here is a tutorial
http://www.s4miniarchive.com/2013/12/how-to-remove-knox-bootloader-from-new.html?m=1
Rename .tar.md5 to .tar and open using total commander and just
Just remove everything except system.img and boot.img
Then flash from odin
Sent from my ASUS_T00J using XDA Free mobile app
Click to expand...
Click to collapse
have you tried like that for kitkat? i do not want to brick my phone . but if you have tried it i will try as well.
syednawaz said:
have you tried like that for kitkat? i do not want to brick my phone . but if you have tried it i will try as well.
Click to expand...
Click to collapse
Yes i have tried that. U can also try. Just remove all the files except system.img and boot.img then flash then you will have the kitkat firmware installed then u need to flash this rom
Sent from my ASUS_T00J using XDA Free mobile app
after deleting files and then selecting it in odin i get md5 error, binary is invalid. any help plz
and that link is for linux, i do not understand it.
solved. by removing md5. now installing
syednawaz said:
after deleting files and then selecting it in odin i get md5 error, binary is invalid. any help plz
and that link is for linux, i do not understand it.
Click to expand...
Click to collapse
Remove .md5 the firmware should be in xxx.tar not xxx.tar.md5
Sent from my ASUS_T00J using XDA Free mobile app
Dualboot patcher 101
Device : Galaxy Note 4
Difficulty level : Easy
This is a full guide to understand and use Dualboot Patcher App
Download latest app snapshot from : Noobdev
Files » DualBootPatcherAndroid-9.1.0.r80.gd5920b2-snapshot.apk
Latest as of Jan 8 2017
Install it like a normal apk
Dualbooting begins here ---
Main things to do are
Setup Dualboot boot enviroment
Setup Dualboot files
Flashing
Switch between roms
App sharing
Part 1
Setting up for first time use
-Open dualboot patcher app and do the following
-Go to Roms tab then click the 3 dot menu on "Primary"
-Press Set Kernel {if it didnt ask you at the beginning}
-Then press "Update RamDisk"
Part 2
Patching Files for dualboot
-Download the rom you want to dualboot / any mods for it / xposed or whatever flashableZIP you want to install on your secondary rom
-Go to "Patch Zip File" Press the + and click "Add Flashable Zip"
-Select your ROM Zip
-Select your Device (Trelte For exynos or Trlte For Snapdragon)
-Select "Data slot" in Partition Configuration
-The ID is your parition name , basicly SAME ID for zips = Same flash location, Type rom1 for example [No caps]
-Do the same for any other zips (making sure the ID is the excat same)
Part 3
Flashing
Once you are done patching files , you will end up with a duplicate collection of your original files, but they end with _data-slot-[ID].zip suffix
-Grab those files and go flash them in your recovery
-in the recovery screen you will see [Multiboot] prefix behind most scripts, that means you are flashing a patched zip
-Once you are done flashing just hit reboot from the recovery
Part 4
Switching
You will be greated with your new rom , do the first setup and you are now running your secondary rom
Now, to switch roms do the following
-Install your dualboot patcher app on your secondary rom
-Open it and go to "Roms" Section
-Suprise, you will see Primary and below it [ID] (Data Slot)
-Press the primary and reboot , thats it
Part 5
App Sharing
Lets say you want your app data to be available on all your roms , Whatsapp data , telegram data , game data etc
-Open the app on your primary rom , go to "App Sharing" Section and enable " Share Individual applications"
-Press "manage shared applications"
-Click on an app "whatsapp for example"
-Tick "Use shared data"
-Hit ok then Then go back after selecting all your apps
-It must show a toast saying "The changes will take effect next reboot"
-Reboot your device to the secondary rom and do the same thing for the same apps
App data is now shared across both roms,
F.A.Q please read before attempting this
1- Faild to set kernel due to unrecognized device
-Common issue with custom roms, you can fix it by editing your Buid.prop , changing device name , code etc and ro.patcher
2- Flashing files via recovery , will it affect my primary rom ?
- No , all the files are directed to your new rom enviroment , the only things that can affect dualboot is kernel changes
3- How to change primary / secondary kernel ?
-To change primary , just flash the new kernel , then follow " Part 1 " of the guide again
-To Change Secondary , Follow " Part 2 " of the guide to patch the Kernel zip then flash in recovery
4- Where are the files located ?
-your secondary system can be found under /data/multiboot/data-slot[ID]/System (only seen when you are using primary rom or Recovery file manager)
-Your shared app data can be found under /data/multiboot/_Appsharing
5- Enabling app sharing, my data for the app is gone.
-When you enable app sharing it changes the data location, so whatever data you had need to be moved with it, best thing to do is to backup the app you want to share with titaniumbackup (before enabling shared data for it) then restore it when you enable data sharing and rebooting
6- How many roms can i "dualboot"
-As much as you like aslong as you have storage in your data partition i had 4 roms dualbooted at one point
7- How much storage does it consume ?
-CM roms are usually around 1GB for system + few GBs for data (total of 3GB-4GB For normal user with some apps)
-TW roms are heavier around 2-3GB for system (most bloated AF roms) and same for data
8- My secondary rom broke due to a mod or something, how can i switch roms in recovery ?
-Download dualboot utilites
-Files » Utilities : DualBootUtilities-9.1.0.r80.gd5920b2.zip
-Flash in recovery and it will give you an aroma installer enviroment to select your roms
9- Switch roms without aroma
-In TWRP select flash IMG option instead of zip
-Navigate to /internalmem/Multiboot/[ID]/boot.img
-select flash boot
-swipe to flash then reboot
10- Can i install a rom with aroma installer ?
-Yes , just make sure that the aroma does NOT reboot your device after completion as the dualboot script needs to run after the rom script is done to set the new kernel etc
—---------------------------
Hope this helps whoever wants to use this app , its very simple ,it might look complicated but its easy, GL and have fun
This guide can be used for other devices , Dont forget to hit thanks and reply if it helped.
All thanks for the original devoloper and poster @Anik_khan
First here
Will give it a try ASAP and post my feedback soon
I tried to set it up but i keep getting the error message whenever I click on Set kernel: "Could not determine the boot partition because this device's codename 'hltedalvik.dex2oat-filter=speed' is not recognised". I am using the exynos variant, Dooola v12 rom. Can anyone help me, please?
the\downslash\ said:
I tried to set it up but i keep getting the error message whenever I click on Set kernel: "Could not determine the boot partition because this device's codename 'hltedalvik.dex2oat-filter=speed' is not recognised". I am using the exynos variant, Dooola v12 rom. Can anyone help me, please?
Click to expand...
Click to collapse
If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Here is screenshot of my dualboot testing list
webmaster750 said:
If you want to dualboot a TouchWiz ROM, I highly recommend installing TW as the primary ROM. Here is screenshot of my dualboot testing list
Click to expand...
Click to collapse
Very nice configuration, thank you
the\downslash\ said:
I tried to set it up but i keep getting the error message whenever I click on Set kernel: "Could not determine the boot partition because this device's codename 'hltedalvik.dex2oat-filter=speed' is not recognised". I am using the exynos variant, Dooola v12 rom. Can anyone help me, please?
Click to expand...
Click to collapse
F.A.Q number 2 : Common issue with Dooola roms , and DN7 roms due to changes in codename
ro.patcher.device=hltedalvik.vm.dex2oat-filter=speed
This line needs to be fixed in doola build.prop
Changing it to
ro.patcher.device=treltexx Used to work for me But some people reported bootloops , so take a back up first just in case
I have the n910v im running red dragon rom and its showing gracelte and its not compatible ive asked for the correct line for the build.prop and havent gotten an answer as wbat line to change and what to change it to ... can anyone help me?
happy2472 said:
I have the n910v im running red dragon rom and its showing gracelte and its not compatible ive asked for the correct line for the build.prop and havent gotten an answer as wbat line to change and what to change it to ... can anyone help me?
Click to expand...
Click to collapse
QUOTE=clewis.it;70300596]Add this line to the end of /system/build.prop
ro.patcher.device=trlte[/QUOTE
Try that it work for my n910w8.
BluePhnx said:
QUOTE=clewis.it;70300596]Add this line to the end of /system/build.prop
ro.patcher.device=trlte[/QUOTE
Try that it work for my n910w8.
Click to expand...
Click to collapse
ro.patcher.device=trlte ?
BluePhnx said:
QUOTE=clewis.it;70300596]Add this line to the end of /system/build.prop
ro.patcher.device=trlte[/QUOTE
Try that it work for my n910w8.
Click to expand...
Click to collapse
This is what i get
happy2472 said:
This is what i get
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?t=2447534&page=1099
This is the thread I got my info. Go to page 644.
That is what I used.
ro.patcher.device=trlte
Search for that thread for your model but I think it's the same.
BluePhnx said:
Tthttps://forum.xda-developers.com/showthread.php?t=2447534&page=1099
This is the thread I got my info. Go to page 644.
Click to expand...
Click to collapse
Nope still no good ... let me reboot and see
New
happy2472 said:
New
Click to expand...
Click to collapse
Are you on the latest version?
Wow im usually pretty good at doing this stuff ... is there a more simple set of i structions?
happy2472 said:
Wow im usually pretty good at doing this stuff ... is there a more simple set of i structions?
Click to expand...
Click to collapse
look for ro.product.device= instead of ro.patcher.device=
This worked for me -> ro.product.device=trlte
happy2472 said:
This is what i get
Click to expand...
Click to collapse
Sorry for late response. Your issue is due to your custom Rom changing treltexx names in prop to graceltexx. Usually renaming the changed text to treltexx must work. Use a file editor and search for any grace mention and make sure it says treltexx. Specially the device codename
And update the app It seems old
Sent from my SM-G935F using Tapatalk
Unable to access Roms after a Nandroid Restoration
After doing a nandroid back up in twrp... I restored with my 4 roms with the dualboot patcher....
Only one Rom boots and works the others dont work... whats causing this.... is there anyway to fix this because I have many good data on those roms....plus I would like to feel safe I can do a backup of my roms.
ananjaser1211 said:
F.A.Q number 2 : Common issue with Dooola roms , and DN7 roms due to changes in codename
ro.patcher.device=hltedalvik.vm.dex2oat-filter=speed
This line needs to be fixed in doola build.prop
Changing it to
ro.patcher.device=treltexx Used to work for me But some people reported bootloops , so take a back up first just in case
Click to expand...
Click to collapse
You mentioned making a back up... I have not been sucessfull in making a back up of this app roms... I used twrp and None of the Roms work after restoring the back up.
I got error while flashing zip file from recovery on my device... Seems like it does not support for "trltechn".
Help Please
Thanks a lot
I recently purchased the Galaxy Tab A7 10.4 (released in 2020) and couldn't help but notice that there's no dedicated thread in the forums for unlocking the bootloader or rooting (Although, the method should be very similar to what is followed for the Tab 10.1 (2019)).
It's been quite some time since I published a tutorial on XDA. So, I decided to put up this comprehensive tutorial, hope it helps everyone who's looking for it. We will take the direct approach of rooting the tab by patching the AP firmware and flashing the patched AP through Odin.
/* I will be using the same images I prepared for the tutorial to be posted on my blog. Sorry that they have been watermarked, that is to prevent scrapers from stealing. It took me enough time to capture them and do some post-processing. */
Before we start, here's the obligatory disclaimer and warning:
Unlocking the bootloader will erase all the data on your tab, including all the data that's on the internal storage. So, make sure that you have taken a complete backup of all your important data.
Flashing a custom binary (such as Magisk patched TAR in this guide) will trip the KNOX counter. Your device's official warranty will be void once KNOX is tripped.
You will not be able to use apps and services like Secure Folder, Samsung Pass, and anything that relies on KNOX.
Although I have tried this on my Galaxy Tab A7 (SM-500) and can confirm that this works, I will not take any responsibility of any bricked/toasted devices. Make sure that you fully understand what you're doing and accept the consequences if anything goes wrong.
If you do land your tablet in trouble, feel free to ask, I shall try my best to help.
Click to expand...
Click to collapse
Update log
Updated on March 2, 2021
Added more info about the warranty. It seems like some users are still not aware of how KNOX affects the warranty. If you're getting into software modifications such as rooting, I expect you to have some prior knowledge about such things.
Redacted the part where you needed to change Magisk's update channel under Step #5. Not needed anymore as Magisk v21.x was released to the Stable channel in January 2021.
Replaced all instances of "Magisk Manager" with "Magisk App". Starting with Magisk v22, Magisk Manager is gone and merged with the core Magisk. It's now called the "Magisk App".
Click to expand...
Click to collapse
Requirements
Your Galaxy Tab A7 with SM-T500 or SM-T505 model number
A compatible USB-C cable
A Windows computer. (Odin only works on Windows. If you're using Linux or Mac, you could try Heimdall)
Instructions
Step 1: Enable OEM Unlocking
In order to unlock the bootloader, you must first enable the 'OEM Unlocking' toggle. This toggle resides inside the 'Developer options' screen, which is hidden by default on most Android devices.
First, enable 'Developer options' by going to 'Settings' > 'About tablet' > 'Software Information' and repeatedly tap on the 'Build number' section five times. If you have a lock screen security set, you will need to input your PIN/Password/Pattern when prompted.
{
"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"
}
Once you do this, you should see a toast notification on the bottom of the screen saying that "Developer mode has been enabled".
Once that is out of the way, go to 'Settings' > 'Developer options' and turn ON the toggle next to "OEM unlocking". You will instantly be prompted to enter your PIN/Password/Pattern, so do it. Then select "Enable" to allow OEM unlocking.
Note: If the OEM unlocking toggle is grayed out, make sure that you have connected the tablet to the internet first (via WiFi or mobile network, your choice).
Step 2: Unlock the Bootloader
Start by powering off your tablet completely. Then while holding the Volume Up and Volume Down keys together, connect it to your computer using the USB cable. This should take you to the bootloader screen (I call it that because logically that's what directs you to either Download Mode or Device Unlock Mode). Long-press the Volume Up key to enter the 'Device unlock mode'.
Your tab should now prompt you with a confirmation screen, so press the Volume Up key to confirm and unlock the bootloader.
Your Tab A7's bootloader is now unlocked and it should reboot automatically. You should also see a warning message right before the Samsung splash screen, just as shown in the picture below. Don't worry, it's completely normal. And no, there's no way to get rid of it (unless of course, you relock the bootloader).
The first boot after unlocking the bootloader could take some time (took around 3-4 minutes for me). So be patient.
Now that the bootloader is unlocked, let's verify it. Samsung introduced a new feature known as "VaultKeeper", which will automatically relock the bootloader if you do not perform this step.
After your tab boots, connect it to the internet. Then enable the Developer options as shown in step #1 and go to 'Settings' > 'Developer options'. The OEM unlocking toggle should be greyed out and say that the bootloader is already unlocked. Again, refer to the picture below.
Step 3: Download the firmware package
With the bootloader properly unlocked, you can begin with the rooting part. As I mentioned, we will be patching the AP firmware file via Magisk App, as instructed by John Wu in his installation guide on Github.
So, you will need to download the firmware package for the software version that's currently installed on your tab. This is very important, do not use an older firmware, as it will result in issues. You could of course use a newer firmware, which will update your tab at the same time as rooting it.
To verify your software version, you can go to 'Settings' > 'About tablet' > 'Software information' and check the "Build number". The latter half of the mentioned build number is your tab's software version, which in my case as shown in the picture below is: T500XXU1ATJ2. So, I will need to download the firmware package for "T500XXU1ATJ2" and in your case you should download the one corresponding to the info you see under 'Build number'.
Where to download? You could use online FW databases like SamMobile, Samfrew, etc. However, I would recommend using Frija or Samloader as they allow you to download the firmware directly from Samsung's Firmware Update Servers and without any speed caps. If you're operating on Windows, use Frija. On macOS/Linux, use Samloader.
Step 4: Extract the AP firmware and transfer it to your Tab A7
Once you have the ZIP package downloaded, you will need to extract it to get The extracted folder should contain the individual firmware files like BL, AP, CP (only for SM-T505 LTE variant), and CSC/HOME_CSC (in .tar.md5 file format).
The file you'll require is the AP firmware, which in my case is "AP_T500XXU1ATJ2_CL19362637_QB34980135_REV00_user_low_ship_MULTI_CERT_meta_RKEY_OS10.tar.md5". Again, in your case, the filename would be a bit different, but it should follow the same structure.
After extracting the AP firmware, connect your tab to the computer, enable File Transfer (MTP) mode on it, and copy over the AP firmware to your tab's internal storage. Copy it to the root directory, that is, outside all the folders as shown below. The location of the file doesn't matter, you can copy it anywhere, but I prefer this for easier access.
Step 5: Patch the AP firmware using Magisk App
Now's the time to patch the AP firmware. To do this, download the latest version of the Magisk app from the official Github releases page to your Tab A7. This will be an APK file. Once downloaded, install the APK file using your choice of file manager.
Warning about unofficial sources of Magisk: Magisk does not have any officially registered domain. If you Google for it, you will probably come across multiple websites that have the word "Magisk" in their domain URL. They are there to deceive the users, and often misinform users, especially those who are new to the scene.
John Wu, as well as XDA have previously warned the users from falling into these deceptive websites. The only official place to get Magisk is from Github.
Click to expand...
Click to collapse
You do not need to change Magisk's update channel to Beta anymore. Starting January 12, Magisk v21.x was pushed to the stable channel (default).
After installing, go to the app drawer and launch the Magisk Manager app. Before you start patching, you would want to change Magisk Manager's update channel to Public Beta. This is because Magisk's latest version (i.e. v21.0) is only available on the beta channel and hasn't been pushed to the stable channel yet (at least at the time of publishing this tutorial).
To do this, press the settings icon on the top-right, tap on "Update channel" and select "Beta". Then go back to the app's main screen. It should refresh and show you the latest version as v21.0.
Press the "Install" button and then "Select and Patch a File" from the list of available methods. This should open the file selector, so navigate to the internal storage and select the AP firmware you transferred during the previous step.
Once the file is selected, hit "LET'S GO" to start the patching process. This should take a minute or so because the AP firmware is quite a heavy file. Once it is done, the patched AP firmware with the filename "magisk_patched_xxxxx.tar" (where "xxxxx" is an arbitrary code) should be stored inside the "Download" folder of your tab's internal storage.
Step 6: Flash the Patched AP Firmware using Odin
The last step is to flash the patched AP firmware to your Galaxy Tab A7 and root it. For this, connect your tab to the computer over USB and copy the "magisk_patched.tar" file from the Download folder. Paste this patched AP firmware inside the firmware folder that was extracted during step #5, along with the rest of the firmware files (BL, CSC, etc). Disconnect it from the PC after transferring the file.
Now, boot your Tab A7 into Download Mode. Power it off, and connect it to the computer over USB while holding the Volume Up and Volume Down keys together. This should bring up the bootloader screen. Simply tap the Volume Up key once to enter Download Mode. Here's what the Download Mode on the Tab A7 looks like.
Next, download Odin v3.14.1 from this XDA thread (NOT the patched version, but the regular one) and extract the contents of the downloaded ZIP package. Then launch Odin on your computer by double-clicking the "Odin3 v3.14.1.exe" executable and click "Ok" when prompted. You should see the Odin interface on your computer screen now.
Odin should automatically recognize your tab in Download Mode and display the COM ID on the top-left.
Click the 'Options' tab and uncheck the 'Auto Reboot' option. This will prevent the tablet from being automatically restarted after the flash is complete.
Now, load the firmware files in the respective slots of Odin.
The BL firmware file (BL_T500/5XXXXXXX_xxxxxxxxxxx.tar.md5) goes to the "BL" slot
The CP firmware file (CP_T505XXXXXX_xxxxxxxxxxx.tar.md5) goes to the "CP" slot. Note that the CP firmware only applies to the Tab A7 LTE variant with the SM-T505 model number.
The HOME_CSC firmware file (HOME_CSC_OMC_ODM_T500/5XXXXXXX_xxxxxxxxx.tar.md5) goes to the "CSC" slot. We will not be using the regular CSC, as it will erase all the data. If you want to do that, feel free to use it.
And finally, the patched AP firmware file (magisk_patched.tar) goes to the "AP" slot.
Once the files are loaded in their respective slots, hit the "Start" button to flash them to your tab.
Note: While you could get away with just flashing the patched AP firmware alone, John recommends NOT doing it. Always flash the patched AP along with the rest of the firmware files like BL, CSC, etc.
Wait for the flash to finish. Once it is, you should see the 'PASS!' message in Odin. Like so:
You can now close the Odin window and disconnect your tab from the computer.
Step 7: Perform a Factory Reset
Once the flash is complete, you will need to manually boot your tablet into the stock recovery mode and do a factory reset. This is only mandatory during the initial rooting process, which is exactly what we are doing here.
To do this, hold the Volume Down and Power keys together for about 7 seconds. As soon as the screen turns off, release the Volume Down key and quickly hold the Volume Up key, while still holding the Power key. Keep holding the keys until you see the stock recovery screen.
You should now see the stock recovery screen with some device information in yellow color at the top. Like so:
Use the Volume keys to move the selector to 'Wipe data/factory reset' and hit the Power key to confirm the selection.
You will now see a confirmation prompt on the screen. Select 'Factory Data Reset' to confirm and finally perform a factory reset.
Once done, select the 'Reboot system now' option from the recovery's main menu. Your Tab A7 should now reboot may be more than once, so be patient.
We're not done yet. After booting, you will need to open the Magisk app from the app drawer and follow the on-screen instructions to replace the Magisk stub with the actual full application, and further complete the required setup when prompted by Magisk app.
Once this is done, your Tab A7 should reboot one last time and should be rooted thereafter.
Your Tab is Rooted!
You may now go ahead and start using root applications, install some modules, etc. Since v20.4, Magisk Hide has been disabled by default on new installations in light of the new hardware-backed SafetyNet attestation. So, to use banking/security, or any other sort of apps that may detect root, you will need to turn ON Magisk Hide from within the Magisk App settings.
Before you leave, there are a few key things you should note:
Unlike some other Samsung phones, you will not need to follow any complex button combinations to boot into the stock recovery. A normal reboot will always boot your Tab A7 into the rooted Magisk system. On the other hand, the regular Volume Up + Power key combo will get your tab into the stock recovery mode.
Second, if a new software update is rolled out, you will need to repeat the same process from step #4 all the way to step #7. When updating the FW, you can simply use the HOME_CSC instead of the regular CSC to prevent your data from being wiped. A backup should still be taken.
Click to expand...
Click to collapse
That's all from my side. If you run into any issues, feel free to post. Don't forget to share details like the software version your tab is on, the firmware package you downloaded and used, and of course your tab's complete model number.
Thank you for posting this! I bought a 2019 Tab A just before the A7 released and have been tempted to return it and pick up the A7 but wanted to make sure I could root it. How is the performance if this?
jserio said:
Thank you for posting this! I bought a 2019 Tab A just before the A7 released and have been tempted to return it and pick up the A7 but wanted to make sure I could root it. How is the performance if this?
Click to expand...
Click to collapse
I was really inclined to the Tab S6 Lite. But being honest, I wouldn't have used the SPen that much. So, I dropped it.
I saw Tab A 10.1 (2019), the one you're referring to, and it was a steal for the specs. The reviews were good too. But then the A7 was released, an upgraded model along the same lines. I like it very much. For a budget tab, it really delivers decent performance and a premium-ish design. And, great speakers I must say.
Unlocking and rooting were really fun and easy as well. Overally, it's a pretty darn good tab for the price.
Thanks for the guide, I've been undecided for days if I should pull the trigger or not and no info on rooting was one of the things that was making me hesitate.
The other one is 3gb of ram, how's your experience been so far? I don't play games on my phone/tablet so that's not an issue.
Gitah. said:
Thanks for the guide, I've been undecided for days if I should pull the trigger or not and no info on rooting was one of the things that was making me hesitate.
The other one is 3gb of ram, how's your experience been so far? I don't play games on my phone/tablet so that's not an issue.
Click to expand...
Click to collapse
You're welcome!
For me, 3GB of RAM is enough, of course given my usage. I usually use it for browsing and streaming only. Not much of a mobile gamer, use real consoles and PC for that, lol.
I like Samsung's One UI experience, compared to any other OEM skin (apart from OxygenOS). It's quite smooth IMO. Already removed the bloatware via ADB, might as well come with a guide for that.
It could however be different under heavy multi-tasking usage, like playing mobile FPS titles, etc. Couldn't tell on that.
storage problem
you can not move any app to the sdcard no option tried different formats as well tried app2sd pro creating a adaptable storage will work but you cant see the partition and you cant move apps back to the internal with out app corruption. terminal commands dont work cant edit system
You are a lifesaver, my friend. I just wanted to note for others that Frija did not work for me. It would only fetch a .zip.enc4 image for my SM-T500 (CSC is XAR). I am currently downloading the firmware from SamMobile to try. Magisk can't flash the file Frija get's for me, it needs to be .tar. Yes, I know it says zip but the file is extracted. Just a heads up for others out there! Also, have you flashed a different recovery for this tablet? And, if so, what image based on what model? TWRP and OrangeFox don't have an official image for the SM-T500. Thanks in advance!
DJ
UPDATE: the image from SamMobile was corrupt. Stuck me in a boot loop with a message about it not being offical Samsung software. Had to factory reset from recovery. This method is flawless, otherwise. Gonna try again with different firmware.
Hey guys. Followed the guide to a T (downloaded latest firmware using Friaj) and also flashed CSC (not home) so I could have a clean install. Magisk patched the file just fine. Odin flashed with no error but on first boot besides the usual "bootloader unlocked" error I get another one saying that custom binaries are installed and the tablet is locked. I cant seem to boot to download mode now. I can boot to the bootloader unlock screen but that's it. Any ideas?
Thanks, DJBhardwaj. Very good guide!
Just a note for European SM-T500 users: SafetyNet won't pass as magisk will return evalType: hardware. At least that's what I found in T500XXU2ATJ6. That's not a problem for me as the only app that requires SafetyNet that I use is Netflix and the issue can be fixed by installed a very legacy version of it, but I think people should be warned before tripping knox fuse
Cloudxddd said:
you can not move any app to the sdcard no option tried different formats as well tried app2sd pro creating a adaptable storage will work but you cant see the partition and you cant move apps back to the internal with out app corruption. terminal commands dont work cant edit system
Click to expand...
Click to collapse
I suppose Scoped Storage has some effect, not 100% sure. But I am really curious now. Going to dig in.
Dj89 said:
You are a lifesaver, my friend. I just wanted to note for others that Frija did not work for me. It would only fetch a .zip.enc4 image for my SM-T500 (CSC is XAR). I am currently downloading the firmware from SamMobile to try. Magisk can't flash the file Frija get's for me, it needs to be .tar. Yes, I know it says zip but the file is extracted. Just a heads up for others out there! Also, have you flashed a different recovery for this tablet? And, if so, what image based on what model? TWRP and OrangeFox don't have an official image for the SM-T500. Thanks in advance!
DJ
UPDATE: the image from SamMobile was corrupt. Stuck me in a boot loop with a message about it not being offical Samsung software. Had to factory reset from recovery. This method is flawless, otherwise. Gonna try again with different firmware.
Click to expand...
Click to collapse
Thanks for the kind words.
Frija, Samloader, SamFirm. All of those tools fetch the firmware from Samsung's Firmware Update Servers. These packages are encrypted as .zip.enc4 (for newer devices) or .zip.enc2 (mostly for old ones).
After downloading, the firmware package will automatically be decrypted and converted to a regular ZIP file, if you're using Frija or SamFirm. The ZIP file should contain the AP, CSC, and BL firmware TAR files.
I don't use custom recoveries anymore, but I was more than willing to try. Couldn't find anything for the Tab A7 (yet).
paziusss said:
Thanks, DJBhardwaj. Very good guide!
Just a note for European SM-T500 users: SafetyNet won't pass as magisk will return evalType: hardware. At least that's what I found in T500XXU2ATJ6. That's not a problem for me as the only app that requires SafetyNet that I use is Netflix and the issue can be fixed by installed a very legacy version of it, but I think people should be warned before tripping knox fuse
Click to expand...
Click to collapse
It's more likely to be unit-based. For example, my OnePlus 8 still hasn't been forced to hardware-backed attestation for SN. But my friend's unit (same model and region) has been.
Have you tried enabling Magisk Hide? It is disabled by default. Another thing to try is the Magisk Props module.
jserio said:
Hey guys. Followed the guide to a T (downloaded latest firmware using Friaj) and also flashed CSC (not home) so I could have a clean install. Magisk patched the file just fine. Odin flashed with no error but on first boot besides the usual "bootloader unlocked" error I get another one saying that custom binaries are installed and the tablet is locked. I can't seem to boot to download mode now. I can boot to the bootloader unlock screen but that's it. Any ideas?
Click to expand...
Click to collapse
Could you share a picture of the screen you're referring to?
DJBhardwaj said:
Thanks for the kind words.
Frija, Samloader, SamFirm. All of those tools fetch the firmware from Samsung's Firmware Update Servers. These packages are encrypted as .zip.enc4 (for newer devices) or .zip.enc2 (mostly for old ones).
After downloading, the firmware package will automatically be decrypted and converted to a regular ZIP file, if you're using Frija or SamFirm. The ZIP file should contain the AP, CSC, and BL firmware TAR files.
I don't use custom recoveries anymore, but I was more than willing to try. Couldn't find anything for the Tab A7 (yet).
Click to expand...
Click to collapse
Thanks for the info! I'll post an update later this week once I get it going! Take care and thanks again for posting this guide!
DJBhardwaj said:
Could you share a picture of the screen you're referring to?
Click to expand...
Click to collapse
Sorry for the late reply. I went through the process again and everything worked. It's possible the issue was either a) I used the newest fw to patch and flash or b) I didn't check to make sure "oem unlocking" was greed-out after unlocking it.
Any way to block updates? I prefer not to go through this each update? Hopefully we get twrp for this tablet. I live it compared to the 2019 A with its crappy one-sided speakers.
jserio said:
Sorry for the late reply. I went through the process again and everything worked. It's possible the issue was either a) I used the newest fw to patch and flash or b) I didn't check to make sure "oem unlocking" was greed-out after unlocking it.
Any way to block updates? I prefer not to go through this each update? Hopefully we get twrp for this tablet. I live it compared to the 2019 A with its crappy one-sided speakers.
Click to expand...
Click to collapse
That's great!
As for updates, I think there was a way by blocking the update services using Titanium. Might have to look it up again. I did that years ago. Yes, TWRP would be great for flashing ROMs and NANDroid backups.
I was going for the 10.1 earlier, didn't knew it had one-sided speakers.
I have a question... Unlocking the bootloader and rooting a device are mostly the first steps to a custom rom like lineageos . I find tons of threads for the SM-T510, but not the SM-T505.
Will there ever be a custom rom for the T505?
DJBhardwaj said:
I suppose Scoped Storage has some effect, not 100% sure. But I am really curious now. Going to dig in.
Click to expand...
Click to collapse
So it's impossible to move apps to sd even with root?
Any fixes to allow apps to be moved/installed on SD card? Can't root with work/UEM apps installed. Seems super wierd for a new tablet, is this a bug or should I return?
Allow apps to be moved/installed on SD card
ormefocus said:
Any fixes to allow apps to be moved/installed on SD card? Can't root with work/UEM apps installed. Seems super wierd for a new tablet, is this a bug or should I return?
Click to expand...
Click to collapse
Same here i tried on 2 different sd cards(SD- HD) format them from the tablet and no one app won't move to the sd card.
I turn on the develpoers options and i fount this option: Force allow apps on external(Makes any app eligible to be written to external storage regardless of manifest values) and i tried to donwload Asphal 9 and Gangster Vegas and 2 apps downloaded to the internal storage...
I chekt if the options to move apps is visable on this apps and its not.
If any one fine how to transfer apps to the sd card i will very thankful