Related
Build your own CWM recovery
The procedure in short is:
A. Read the ROM
B. Process the ROM and generate the recovery (should
be automatic)
C. Flash the generated recovery
In a bit more details:
A. Read the ROM which includes these sub steps:
1. Create a scatter file for your phone with
MTKDroidTools and leave MTKDroidTools open
2. Open SP Flash Tools and load the scatter file you just
created
3. Go to ReadBack Tab and Add a new entry - name it
as you wish but leave the ROM_0 prefix - double tap the
new entry and choose the length of ROM you want to
read - to create the recovery it is enough to put the
number of the partition right after the recovery (you can
take that number from the scatter file you created) -
Keep in mind the number must be in Hex - so when you
copy it from the scatter file - make sure it's with the 0x
prefix - something like 0x03d80000 for example.
4. Hit the Readback and disconnect your phone from the
computer, shut it down, pull out the battery for a few
seconds and then put the battery back - don't turn the
phone on - just connect it to the usb - it should start
the readback and eventually should finish with a green
circle - if everything went good Smiling
B. Process the ROM and generate the recovery (should
be automatic):
1. Go back to your MTKDroidTools - which should still
be open from before - and hit "Process ROM" and
choose the one you just read from the SP Flash Tools.
2. If the reading was successful - you should see the
partitions you read being copied - and you would be
asked if to create CWM recovery automatically - answer
YES Smiling
3. After this process has ended successfully - go into
the backups folder inside the mtkdroidtools folder - and
you should see the ROM partitions you read - including
the original boot.img and recovery.img as well as the
newly created patched_recovery.img and
patched_boot.img
C. Flash the generated recovery:
1. Create a new folder and copy your original scatter file
you created in step A1 and your patched_recovery.img
into this new folder.
2. In the new folder you created, rename the
patched_recovery.img to just recovery.img
3. Open SP Flash Tools, choose the scatter file you
copied in the new folder and you should see that it also
adds automatically the recovery (make sure it's the
correct folder) - Make sure that ONLY recovery section
is selected !!!!!!
- hit Download and disconnect your phone from the
computer, shut it down, pull out the battery for a few
seconds and then put the battery back - don't turn the
phone on - just connect it to the usb - it should start
the flashing of the recovery and upon successful flasih -
you will see the green circle
it works for me always .... so i thought of sharing with you guys...try at your own risk...
dont forget to press the thanks button
credits: to the one who discovered the method and also me for understndng and testing and den posting in xda
press the thanks button if i helped you with this guide
SAMSUNG GALAXY S4 - SUPPORTS ALL VERSIONS UP TO THE LATEST ANDROID BUILDS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
SUPPORTED MODELS
INTERNATIONAL MODEL GSM [GT-I9500]
INTERNATIONAL MODEL LTE [GT-I9505]
US SPRINT MODEL LTE [SPH-L720]
US CELLULAR MODEL LTE [SCH-R970]
US C SPIRE MODEL LTE [SCH-R970X]
US CRICKET MODEL LTE [SCH-R970C]
US TMOBILE/METROPCS MODEL LTE [SGH-M919]
CANADA MOBIL, VIDEO, WIND LTE [SGH-M919V]
Click to expand...
Click to collapse
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports many 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/Windows 10
* 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]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
* Install BusyBox on your device
* 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]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* 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
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* 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 Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
{
"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"
}
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: ChainsDD for Superuser, Chainfire for SuperSU and kernel patches, 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, NextApp for the SD Fix 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 AND ROOT YOUR DEVICE.
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.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): 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.
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 superuser files available and custom recovery (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. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
USEFUL INFORMATION
How to get into Recovery Mode
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Shut down the phone.
3. Hold down the 'HOME' + 'VOLUME DOWN' buttons and press the 'POWER' button for about 2 seconds until a WARNING! Screen appears. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
**Updates**
**FREQUENTLY ASKED QUESTIONS**
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. 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. What is the difference between Nandroid and Titanium backup?
A NANDROID will backup the whole system including boot, system, data and recovery
partitions so you can restore a complete rom and all data and settings.
Titanium Backup is mainly used to backup apps and associated user data. These
could be restored AFTER a full wipe and a new Rom had been flashed on your phone.
The other option now which google added into the new adb command list is the adb
backup which is in the ToolKit and can do the same job as Titanium Backup but will
store the data on your PC rather than on the phone (which takes up space).
Q. I cannot find Developer options
With Android 4.2 google have thought it would be funny to hide the Developer options
screen in the Settings. This means you cannot enable usb debugging to communicate
with your device. To show the Developers options screen do the following:
1. Goto Settings, About and tap the Build number text 7 times.
2. When you have tapped 3 times you will be given a countdown of taps until you
become a developer.
3. Once you are told you are now a developer you can go back to the Settings
Screen and can see Developer options.
4. You can now go into Developer options and enable usb debugging.
Q. I am having trouble getting adb working with the drivers installed
Try switching your connection type from media (MTP) mode to camera (P2P) mode.
To do this open the notification area [top left] with the device connected via usb,
click where it says 'connected as' and change from MTP to PTP.
------------------------------------------------------------------------------------
Q. How to get into your Download Mode
1. Unplug your usb cable if you have one plugged in
2. Keep holding the Volume Down, Home and Power buttons until you see a warning
screen [about 10 seconds]
3. Press the Volume Up button to boot the phone into Download Mode
------------------------------------------------------------------------------------
Q. How to get into Recovery
1. Unplug your usb cable if you have one plugged in
2. Keep holding the Volume Up, Home and Power buttons until you see a green android
man on the scree [about 15-20 seconds]
Q. I tried to enter the code for the pro version but it says the code is incorrect
1. Make sure the code entered is for the correct Toolkit being used.
2. You need to start the Toolkit with the toolkit.exe file when activating so the
settings can be initialised or the code will not be accepted.
3. Make sure you enter the code correctly as the characters are case sensitive.
**if needed*
GREAT. Thank you for providing your tools to our device mskip
powered by Fingerbite Chocolate™
mskip said:
**if needed*
Click to expand...
Click to collapse
I think most of your pics are damaged...can they be repaired?
Sent from my GT-I9500
anu.cool said:
I think most of your pics are damaged...can they be repaired?
Sent from my GT-I9500
Click to expand...
Click to collapse
Sorry im not sure what you mean.
Mark.
mskip said:
Sorry im not sure what you mean.
Mark.
Click to expand...
Click to collapse
tapatalk shows images in first post are damaged ie can't be seen,broken links maybe.
Can they be fixed?
Sent from my GT-I9500
Thanks mskip, yours utilities are the best.
Enviado do meu GT-I9500
knox
if you do root the S4 with this process, active knox?
kraiioL said:
if you do root the S4 with this process, active knox?
Click to expand...
Click to collapse
bump bump:highfive:
kraiioL said:
if you do root the S4 with this process, active knox?
Click to expand...
Click to collapse
If you flash any custom image on a device with KNOX present then yes you will trip the knox flag.
Mark.
mskip said:
If you flash any custom image on a device with KNOX present then yes you will trip the knox flag.
Mark.
Click to expand...
Click to collapse
Works to root 4.4.2 official?
I need the phone in download mode? Recovery mode?
[SGS4]
KNOX S4
whether this method changes the root flag knox with 0x0 to 0x1
by far the best application i have used for a long time... whether rooting the phone or reverting to stock firmware. great piece of work.
i keep getting error when i try to install custom recovery ive tried both my wifes phone and mineim on 4.4.2
I installed the toolkit to do an ADB backup of Samsung Galaxy S4 M919 with Android 4.2.2 (already rooted)
PC system in Win7/32
After installing the Samsung USB drivers, and plugging in the USB cable, I can see that the ADB drivers are loaded. In Device Manager, The "SAMSUNG Android ADB Interface" is shown under Android Phone. Running "adb device" from the command line shows that the SGS4 is recognized.
However, the prompt about pairing with the PC never occurs. I thought maybe I had done it before, so I didn't worry about it since ADB was working. I selected ADB Backup in the toolkit using the -all -apk -system -noshared options.
The Full Backup function appeared on the phone, and I selected "Back Up My Data". The phone had not rebooted - the backup app is on top of the regular phone function and the status bar is still showing at the top. I did not enter a password.
Below the password field various apps are displayed one by one.
However the progress is unbelievably slow. After 30 minutes, only at 200 MB file is present in the backup folder. It hasn't increased in size for over 10 minutes.
This is the first time I've tried an ADB backup with the SGS4, but my previous phone would back up several Gbytes in about 15 minutes.
Is this process just very slow on the SGS4, or is something wrong?
so the Att SGH 1337 model is not supported by this toolkit?
thank you for this wonderful tool, makes things easier
HI Mark,
I just want to say THANK YOU for all of your toolkits!
I bought the OG N7 AND N7 2013 versions, and I (finally) have a SGS4 on the way and will be buying this toolkit as well when my i9500 arrives.
You have saved me a ton of time of trouble, and I plan on following your work down the road as well.
Thank you for making these available to us, and please keep up the great work... :highfive:
HERE IS THE FIRST OFFICIAL
CWM FOR KARBONN TITANIUM S20
ORIGINAL BOOT N RECOVERY .IMG
join FB GROUP:::<ww.facebook.com/groups/323894334469784>
sTOCK ROM (SOON BE UPLOADING)
Site ::: karbonnts20.blogspot.in/
nEWBIE PROBLEM THATS WHY LINKS ARE NOT ALLOWED TO POST
Rooting KArbonn Titanium s20
#Requirements:
"I am not responsible if you brick your phone"
CWM recovery (Link)
SU & Binary files (Link)
Use SP Flasher v 5.0xx to flash (Link) .
Download the scatter file MT6582(Link)
#Procedure :
Open SP flasher and choose scatter file Mt6582_android_emmc.txt
Goto recovery link and choose the CWM recovery (downloaded).
Now connect your device in switch off Mode with its battery inside and Download it
Now open CWM by pressing Vol up+Power Key
Choose "Install zip from sd card" >Choose zip from Sd card > select the update SU.zip
Reboot and we are done rooting.
for links check the site!!
Repartition Internal SDCARD
As we know this device {MTK6582}comes with 4GB ROM with APP data to be 1GB and user Storage 1.59 GB.
Such small APP space cause a lots of problems Thus best way is to repartition it with HKRom Manager.
For links visit the site :-htp://karbonnts20.blogspot.in/
"I am not responsible if u brick your phone , dead internal sd or so n so .Better do it on your own risk"
Requisites:
Hk rom manager.apk
CWM /TPRW recovery
A full backup CWM or TPRW.
Procedure:
Before you proceed take a full CWM or TPRW backup as phone internal partition may not work or respond sometimes.
Now install the app
Open the app and select mt6582 fast runner (2nd option) ::it will be the only highlighted option .
Choose your required data size (say 2GB , its fine ) and hit apply and now wait.
It will show boot into recovery ,hit yes
After 3 mins you are done. ReBoot it
Now You have 1.8GB APP space and 540MB for storage
"Remember all your phone data will be lost as phone is re-partitioned and Formatted. "
thanks to XDA
Ways to extract stock rom
How to Extract Stock Rom {Detailed procedure with Video tutorial}
FOR LINKS PLEASE VISIT THE SITE :- []ttp://karbonnts20.blogspot.in/[/url]
"This Tutorial is applicable MTK devices "
Required :-
SP flasher- [ttp://sh.st/o9xC5[/url]
MTK Droid Tools- [tp://sh.st/o895X[/url]
Scatter file
ABD Drivers
Ways to extract stock rom:- Video Links
1.Case I:- "If you have a unrooted and no CWM ANDROID Phone with USB Debugging Enabled "
Tutorial Visit:- ttp://sh.st/ocUme[/url]
2. Case II :- An Android Phone having CWM (with or without Root)
Tutorial Visit:- ttp://sh.st/ocOaC[/url]
3. Case III :- "A rooted Android phone (with or without CWM) USB Debugging Enabled"
Tutorial Visit :- ttp://sh.st/ocOBw[/url]
Thanks to XDA , and the Developers
Procedure:-
Case-I :If you have a unrooted and no CWM ANDROID Phone with USB Debugging Enabled
First TURN ON the USB Debugging Option :: ie , Settings>Developer options>USB debugging and install ADB drivers
Start MTK Droid Tools <Provided above> ,Grant the USB debugging request and wait till device get discovered .
Then click on BLOCKs Map and you will get all partition and their length .Here you can create a scatter file also. and minimise the window .\, We would require the location later.
Then TURN OFF the phone . OPEN SP flasher , Choose the scatter file you made or provided in the link.
Then Goto READBACK tab and add a readback file ie ROM_0
Click on ROM_0 and choose the destination Folder .
Now a Box will open and ask for Start address and length ,SET it in hex and do the following
start address:0x0000000 and length 0x7FB80000 [The length of FAT as in scatter file] ,Remember if you want the length shown in block map then just ADD 0x [length] .
Now HIT readback. Connect the Phone using USB with battery inside the phone and wait till its get discovered and yellow bar will represent the work.
It would nearly take 30-45 mins and we got our ROM_0 file.
Again Turn ON the phone and connect with USB debugging ON.
Open Minimised MTK Droid tools and Goto Root,backup tab and Hit Process ROM_0.
It will ask to make CWM recovery from original recovery ,if u want CWM fro your phone here you can get it HIT Yes.
After Processing finished we will get our SP flashable STOCK Rom Files in mtkdroidtools>backup
Hence we are done . And In RESULT we get ,ScAtter File ,SP Flashable STOCK Rom images and CWM Recovery for the phone.
Thank You
Case II:-An Android Phone having CWM (with or without Root)
Here we get CWM Backup For Stock Rom which is good for Porting like purposes.
Keep 3 GB of space empty in SD card.
First Turn OFF the Phone and HOLD UP+ Power Key
Enter to Recovery Menu>Backup and Restore
Hit Backup
After it completes Goto SDCARD>CLOCKWORKMOD>BACKUP
Result we get CWM Backup of STOCK ROM which can be flashed By CWM on Hitting restore in Backup and Restore.
Case-III:-A rooted Android phone (with or without CWM) USB Debugging Enabled
Here we can get CWM recovery,SP Flashable Stock Rom and to work with Rom files.
Connect the phone phone to PC via USB and turn ON the USB Debugging.Keep 3GB SDcard Space
Then start MTK Droid Tools and let it detect your Phone.
Then Hit ROOT button just at Down right.
Let it connect to phone and Grant the SU Permission in the phone.
The yellow mark in down left corner will turn Green .
Goto Root, Backup Tab and Select userdata and cache in Bacup option.
Now hit Backup. It would take and hour or so.
Then click on" prepare blocks for flash tools" and wait .
After it Finishes you have CWM recovery,SP Flashable Stock Rom and to work with Rom files.
Mtkdroidtools>backups>"[Phone name]">!imagesfor flashtool
Hope it help You
Hit like and Share
When my new Cubot X16 arrived, I was quite excited. It’s a great phone I must admit. After one day of exploring, I decided to root the phone using the method described here: http://forum.xda-developers.com/showpost.php?p=64093232&postcount=8
However this method did not succeed on my phone, possibly because I did an OTA update to the latest firmware. After installing SuperSU, my phone boot-looped forever. So I had to remove SuperSU within TWRP using this method: http://forum.xda-developers.com/showpost.php?p=63615067
Because I only need root to stop ads, I decided another approach without root access. And it works!
I used TWRP recovery (which also enables you to backup your phone’s ROM).
So here is the method, which may work on most MTK phones and possibly others too.
The first part is the same as http://forum.xda-developers.com/showpost.php?p=64093232&postcount=8
1) Things you need (i did it with windows 10 x64):
• TWRP recovery file from https://cloud.mail.ru/public/6AL2/3P8rxeavd
• Flash tool "SP Flash tool" (google for the latest version)
• USB Driver for Android/MTK (e.g. from http://forum.xda-developers.com/showpost.php?p=53854405) there are a few driver-packages in the file; "New inst. win 7&8x64" worked for me; maybe you have to try another one)
• A good hosts file for blocking Ads. Copied to your phone’s memory. There are many to be found. Hard to say which is the best. Watch out that it is in Unix format, not in Windows format! Some suggestions:
a. http://hosts-file.net/.\ad_servers.txt
b. http://pgl.yoyo.org/adservers/serverlist.php?hostformat=hosts&showintro=0&mimetype=plaintext
c. http://winhelp2002.mvps.org/hosts.txt
d. http://hosts-file.net/ad_servers.txt
e. https://github.com/Free-Software-for-Android/AdAway/wiki/hostssources• Backup your old /system/etc/hosts file somewhere safe, in case you need/want to restore it!
2) Install the drivers (if you have none installed!); Download the Flashtool and the recovery-file (and unzip it); Inside the zip you will find a scatter-file and revovery.img
3) Start the Flashtool as admin and go to the download window. Click at "Download-Action" and choose the file "MTK_AllInOne_Da.bin" (comes together with the flash tool). Click at "Scatter-loading" and choose "MT6735_Android_scatter.txt" from the unpacked recovery zip (Important: if you have another phone, please find the correct scatter file! You can also use Mtk_Droid_Tool_v2.5.3 to generate a scatter file for your phone). The section below should now be filled with the recovery-file, only the recovery-checkbox should be ticked (otherwise you may loose your smartphone-data)! Choose "Download only" from the dropdown-menu.
4) Connect your phone to the computer (just normal booted, no special recovery- or download-mode). Click at Download in the Flashtool. The application is now ready to install the recovery. Now reboot your phone via the normal power-menu. The Download should start automatically, when the phone reboots. When the download was completed successfully, a green snag should appear in the flash tool. You can now disconnect your phone.
5) Now let’s test your new recovery: Restart you phone holding the Power & Vol+ buttons. If you have a normal reboot while holding these buttons, you have to release them for a short period of time after the boot-screen appears. As soon as the screen lights up, you can release the buttons and you are now entering recovery (first time you have to allow the recovery to change your system at first).
6) You can now take a system backup (or more)
7) Mount the system partition (Mount and tick system)
8) Start TWRP File manager and copy the previously downloaded hosts file to /system/etc/hosts
9) Reboot normally and your phone runs Adfree
Ps. Some users report that their phone generates a “corrupted system” message while booting (not so on mine). This may be due to the fact that the system does a checksum and detect that the system partition was “tampered” (but no problem we only changed the hosts file).
Once in a while you may have to update the hosts file. Download a new hosts file and reboot in TWRP and repeat the last 3 steps above (takes only 5 minutes).
Note that a bigger hosts file may slowdown lookups, but I did not see any slowing down. As a matter of fact AdAway uses the same method of replacing the hosts-file (on a rooted phone)
Imortant: You can still use Android Pay, since your phone was not rooted! Some other apps may also refuse duty when your phone is rooted.
Ps. Alternatively, you may prefer to replace the hosts file using ADB v1.4.3 (you can find a stripped version without installing the full Android development environment at: http://forum.xda-developers.com/showthread.php?t=2588979)
Copy the original hosts file from phone to pc:
Code:
adb pull /system/etc/hosts
Edit the hosts file, and add your own ads blocking records:
Code:
adb push hosts /system/etc/
adb shell chmod 644 /system/etc/hosts
What's currently included in this thread :-
TWRP (With/without magisk)
Installing EdXposed
Root with magisk (not recommended due to bootloops, use twrp with magisk)
RMM state Prenormal solution
Stock and combination firmware and Kernal source Gdrive links
Tools for flashing and downloading latest firmware
Post 2
Hide bootloader unlocked warning message
DeGoogle & debloat M30s and install MicroG
Enable Haptic feedback on m30s (or any other samsung phone)
BACKUP YOUR EFS PARTITION BEFORE DOING ANYTHINGIf EFSpartition is corrupted or lost, you would not be able to get calls and wifi and your IMEI will be permanently lost.
There is currently no way of restoring corrupted EFS partition since it is device specific, so flashing stock firmware will also be useless
Here is one guide. follow this or any other that works for you.
Here is another (droid view.com/restore-efs-imei-galaxy-s7/)
OR You can Backup all partitions using twrp (nandroid backup) and store in someplace safe (make sure to tick all partitions including EFS)
This is an excellent guide regarding EFS (thanks to @PlayingPoise). I HIGHLY RECOMMEND READING IT BEFORE PROCEEDING.
TWRP (With/without magisk) (huge thanks to @santhoosh)
Thread
there are two .tar files, flash the one you need
Pro Tip: I would recommend Smalipatcher module to reboot directly into magisk system.
Installing EdXposed
See This for installation video OR This Or This for installation guide.
This, for official website
And This for github!
NOTE: v0.4.6.0_beta from github requires custom magisk otherwise the system wont boot since github hosts alpha versions, so i advice to follow the video tutorial since it has installed the most stable EdXposed
Rooting with Magisk (Currently causing random bootloops since custom Kernal is req., i recommend flashing twrp with magisk)
From magisk official repo and This Link, Both are same, but i just wanted to make AIO thread)
thanks to @santhoosh and @topjohnwu
Unlocking Bootloader
Normally I wouldn’t provide instructions for this, but since things had changed drastically from previous Samsung devices, and there are some caveats, I figure this would be helpful.
* Allow bootloader unlocking in Developer options → OEM unlocking
* Reboot your device to download mode. Either use adb reboot download, or use turn off m30s, press vol+ and vol- simultaneously (while powered off) and connect to pc.
* Long press volume up to unlock the bootloader. This will wipe your data and automatically reboot.
Just when you think the bootloader is unlocked, it is actually not! Samsung introduced VaultKeeper, meaning the bootloader will reject any unofficial partitions before VaultKeeper explicitly allows it.
* Go through the initial setup. Skip through all the steps since data will be wiped again later when we are installing Magisk. Connect the device to internet in the setup!
* Enable developer options, and confirm that the OEM unlocking option exists and grayed out! The VaultKeeper service will unleash the bootloader after it confirms that the user has the OEM unlocking option enabled.
* if there is no OEM unlock option, set phone's date to 7+ days and back and now see.
* Your bootloader now accepts unofficial images in download mode.
Instructions
* Download the firmware for your device.
* Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
* Install the latest Magisk Manager
* In Magisk Manager: Install → Install → Select and Patch a File and select the AP tar file.
* Magisk Manager will patch the whole firmware file and store the output to [Internal Storage]/Download/magisk_patched.tar
* Copy the patched file to your PC with adb pull /sdcard/Download/magisk_patched.tar. Do not use MTP as it is reported to corrupt files.
* Reboot to download mode, and flash magisk_patched.tar as AP in Odin, together with the BL, CP and HOME_CSC files. Never flash only an AP file, as Odin can shrink your /data file-system if you do.
Important: Uncheck “Auto Reboot” in Options!
* Magisk is now successfully flashed to your device! But there are still several steps before you can properly use the device.
* We now want to boot into the stock recovery to factory reset our device.
* Full data wipe is mandatory! Do not skip this step.
* Press Power + Volume Down to exit download mode. As soon as the screen turns off, immediately press the Vol up and power to boot to recovery . Since we want to boot into stock recovery, continue pressing the volume up button until you see the stock recovery screen.
* Use volume buttons to navigate through the stock recovery menu, and the power button to select an option. Choose Wipe data/factory reset to wipe the data of the device.
* This time, we can finally boot to the system with Magisk. Select Reboot system now, and immediately press the combo key to recovery. After seeing the bootloader warning screen, release all buttons so it can boot to the system.
* The device will automatically reboot for the first time it boots. This is completely normal and done by design.
* After the device is booted up, do the usual initial setup. The following steps will need an internet connection.
* You shall see Magisk Manager in your app drawer; if not, manually install the APK you downloaded in step 3 and continue to the next step. The app would be a stub and it shall automatically upgrade to the full Magisk Manager when you open it.
* Magisk Manager will ask to do additional setups. Let it do its job and the app will automatically reboot your device.
Voila! Enjoy Magisk
Additional Info
* Magisk actually patches 3 partitions on your device:
vbmeta: replace with empty vbmeta image to disable partition verification
boot: remove the signature of the image to prevent soft bricks
recovery: this is where Magisk is actually installed
* Never, ever try to restore either of the 3 images mentioned back to stock! You can easily brick your device by doing so, and the only way out is to do full Odin restore following with factory reset. Just don’t do it.
* If you want to upgrade your device, never flash the stock AP tar file with the reasons mentioned above. Always pre-patch the firmware before flashing in Odin.
* If you don’t need to patch the full firmware, you can manually create a tar file with at least vbmeta.img, boot.img, and recovery.img to let Magisk Manager patch your images in the proper way.
Due to the fact that some devices no longer uses ramdisk in boot images, Magisk has no choice but to be installed in the recovery partition. For these devices, you will have to boot to recovery every time if you want Magisk. Since both Magisk and recovery lives in the same partition, what you actually end up getting when you choose to boot to recovery will be determined by how long you press volume up.
1. Powering up normally → System without Magisk
2. Power + Volume Up → Bootloader warning → Release all buttons → System with Magisk
3. Power + Volume Up → Bootloader warning → Keep holding volume up → Actual recovery
I would recommend Smalipatcher module to reboot directly into magisk system.
Updates: For each and every updates, either magisk or system update always patch the firmware with magisk and flash using odin(data will not be wiped if HOME_CSC
used instead of CSC)
RMM state Prenormal solution
Flash stock firmware
Boot up WITH sim inserted, CONNECT to internet during setup (or you can connect after setting up, but perform below operations only when connected to internet).
Enable developer options and go to them.
Now connect to internet and go to dev options, now set date 8 days back and check dev options for OEM unlocking
if it's still not there set date to today and again 8 days back and again check.
This worked for me and OEM unlocking was there and RMM state was changed to checking.
(what we are doing is fooling phone to believe that sim was inserted for more than 7 days)
Stock and combination firmware and Kernal source
Below are Gdrive links for Combination firmware for (M307FXXU1ASH9) and (M307FXXU2ASK2) and ROM M307FXXU1ASHI, M307FXXU2ASL2, M307FXXS2ATB3 (FOR INS ONLY, for other regions, use frija or samfirm).
I have also uploaded Kernal source for M307FXXU2ASL2 on gdrive for faster download.
Tools included
The following tools are also included in the shared folder, they are up to date as of FEB 2020, but i have attached links to original threads of xda to give credits and in case they are updated, you can download them from there. (As i said, this is AIO thread to find tools, none of them are my creation)
Frija, Samfirm continued and Samfirm are Tools for downloading Official firmware from samsung servers with high speed (so no to sammobile and other ****ty premium websites)
Frija thanks to @invmini, Github
SamFirm thanks to @zxz0O0, Github
SamFirm_continued, Github
Odin
Patched Odin by @realbbb
Frija not working ? install both vcredist_x00 for your device !
(check your windows settings to know which version to install)
(Microsoft Visual C++ 2010 Redistributable Package) and (Microsoft Visual C++ 2008 Redistributable Package)
https://www.microsoft.com/en-US/download/details.aspx?id=29 (x86) 2008
https://www.microsoft.com/en-US/download/details.aspx?id=5555 (x86) 2010
https://www.microsoft.com/en-US/download/details.aspx?id=15336 (64bit) 2008
https://www.microsoft.com/en-US/download/details.aspx?id=14632 (64bit) 2010
-Open Frija and type in your model (mine is SM-m307f) and your CSC : (mine is INS).
(All models on samfrew: https://samfrew.com/model/SM-M307F/).
Thanks to @BK
Other Tools
PIT Magic v1.3.10 - Samsung PIT Creator, Editor, Analyzer
Samsung firmware naming convention and explanation (Outdated)
SM-M307F - Galaxy M30s Samfrew
Extract Samsung PIT File from Samsung Firmware -> www.droid views.com/extract-samsung-pit-file-from-firmware (remove space b/w "droid" and "views")
NAND Erase Samsung Devices in Odin -> www.droid views.com/nand-erase-odin-samsung-firmware (remove space b/w "droid" and "views")
Latest Odin Downloader: https://odindownloader.com/category/download
Samsung USB Driver: https://samsungusbdriver.com/category/download
Samsung Firmware: https://firmwarefile.com/category/samsung
LinksLINK (Pm me if link is dead. If there is error like "try after some time", make a copy of file to your drive and then download)
Hide bootloader unlocked warning message
See Here
DeGoogle & debloat M30s and install MicroG
Here
Enable Haptic feedback on m30s (or any other samsung phone) (thanks to ak****)
1- download "Settings database Editor" from playstore.
2- scroll to bottom and find "haptic_feedback_enabled" and change it to 1
Just in case
great, im planning to buy this device and sell my a70, wouldn't have though a little bit of my thread would have been used there also combination files cannot be flashed anymore until a fix is found (nope Z3X Samsung tool don't work )
BK said:
great, im planning to buy this device and sell my a70, wouldn't have though a little bit of my thread would have been used there also combination files cannot be flashed anymore until a fix is found (nope Z3X Samsung tool don't work )
Click to expand...
Click to collapse
Are you talking about the frija and samfirm part?
I think i took it from some other thread which i cant find now. (maybe s10 or note10 ones)
Edit: Gave credits to you
How to flash Combination firmware?
I am trying to flash combination firmware [COMBINATION_FAC_FA90_M307FXXU1ASH9_FAC_CL16672589_QB25543275_REV00] with Odin v3.13.3B Patched but it doesn't work, giving this error on the phone
"Please get the approval to use factory binaries (PIT)"
Anyone know any way to make it work? It would be really nice to be able to downgrade to U1 binaries.
nobody_nowhere said:
I am trying to flash combination firmware [COMBINATION_FAC_FA90_M307FXXU1ASH9_FAC_CL16672589_QB25543275_REV00] with Odin v3.13.3B Patched but it doesn't work, giving this error on the phone
"Please get the approval to use factory binaries (PIT)"
Anyone know any way to make it work? It would be really nice to be able to downgrade to U1 binaries.
Click to expand...
Click to collapse
it's currently impossible to install a test/debugging firmware without a samsung dev account that work as an authorization to flash combination files.
Sm-m307f/ds
Hi i got OTG update and my phone didnt restart after that, i have been trying to find the right Stock firmware for my Samsung M30S SM-m307F/DS but i couldnt find the right one, can you please help me out with the link of the right firmware for my phone.
Thanks
Watch this video broo...you will get to know how to download all latest updated frimware