Related
INTRODUCING THE SAMSUNG GALAXY S3 UNIFIED TOOLKIT
SUPPORTED MODELS
INTERNATIONAL [GT-I9300] SUPPORT THREAD HERE
AUSTRALIAN MODEL GSM [GT-I9300T]
INTERNATIONAL [GT-I9305/GT-I9305N] SUPPORT THREAD HERE
AUSTRALIAN MODEL LTE [GT-I9305T]
C SPIRE MODEL LTE [SCH-L710]
AT&T US [SGH-I747] SUPPORT THREAD HERE
BELL, ROGERS, SASKTEL, TELUS [SGH-I747M] [SGH-I747M] USE AT&T SUPPORT THREAD
US CELLULAR MODEL LTE [SCH-R530] USE AT&T SUPPORT THREAD
METRO PCS MODEL LTE [SCH-R530M] USE AT&T SUPPORT THREAD
SPRINT US [SPH-L710] SUPPORT THREAD HERE
TMOBILE US [SGH-T999] SUPPORT THREAD HERE
MOBILICITY, VIDEOTRON, WIND [SGH-T999V] USE TMOBILE SUPPORT THREAD
VERIZON US [SCH-I535] SUPPORT THREAD HERE
CHINA ANYCALL CDMA MODEL [SCH-I939] USE GT-I9300 SUPPORT THREAD
Click to expand...
Click to collapse
The Unified Android Toolkit supports a multitude of Nexus and Samsung devices with more devices being added all the time. 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 V1.3.4 [9TH JAN 2015]
* 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]
* 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]
* 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
* 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
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: 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: 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.
--------------------------------------------------------------
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. NOTHING IS 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.
PRO USERS CAN ALSO SELECT THE "ANY BUILD" OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD (USEFUL IF YOUR BUILD IS NOT LISTED).
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 AND UPDATE CHANGELOG**
This Updater file will update your Toolkit to the latest version and add the latest support the Toolkit offers. Download the below file, move the file to the Toolkit installation folder and run the file to update to the latest version.
THIS IS AN XDA EXCLUSIVE AND MUST NOT BE REDISTRIBUTED IN ANY FORM!!
IF YOU ARE PLEASED WITH HOW THE TOOLKIT WORKS DON'T BE TIGHT AND CONSIDER DONATING TO THE PRO VERSION TO SAY THANK YOU AND GET UPDATES PUSHED STRAIGHT TO YOUR TOOLKIT WITHOUT HAVING TO UPDATE MANUALLY. A LOT OF WORK GOES IN TO THE TOOLKITS AND IM ALWAYS TRYING TO MAKE THEM BETTER. THANK YOU.
**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). If you have a GT-I9300 GSM Model then you can do this from the Toolkit but if you have an LTE device then it isn't soo easy to do. If you have an LTE device you should go to *THIS* thread by lyriquidperfection and follow the information to save your IMEI/NV Data so that you are covered if anything should happen.
----------------------------------------------------------------------------
Q. Is there currently no way to root the Samsung Galaxy S3 without voiding the warranty?
All methods of rooting will void your warranty in some way as you will have superuser files on your phone that arent supposed to be there. There is a method of rooting your phone without increasing the flash counter which involves flashing a complete rom with root files already added but if anything happens and you need to send it back under warranty you will need to flash a 'proper' Stock Rom back before returning it or your warranty will be void. Flashing a custom kernel or recovery to root will increase the flash counter and also void any warranty. There is currently no method of resetting the flash counter on Snapdragon models but im pretty sure there will be some support for it soon. If you dont want to risk it or you aren't sure then you shouldnt really be flashing your phone and should just leave it alone. Its your choice .
----------------------------------------------------------------------------
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.
Changelogs from previous builds to the Unified version
ToolKit v6.0 (08th November 2012)
+Added Full Support for International LTE Model GT-I9305
+Updated root support for latest 4.1.1 builds
+Added new Builds to Model Selection Screen
+Added Hotfile links to Stock Firmware for both Models in Downloads Section
+Added choice of Superuser or SuperSU on all root procedures
+Added choice of Custom Recovery when rooting (I9300 only)
+Updated Samsung USB Drivers to v1.5.15.0 (latest version)
+Added Device Information Screen from Main Menu
+Fixed Odin Tar Creator crashing
+Disabled ICS mods being enabled on JB builds which could soft brick the device
+Added NEW ‘Quick Picks’ Donators Feature
+Re-wrote lots of procedures to incorporate the Quick Picks Feature
+Re-ordered some functions on the Main Menu
+Added solution if CWM Root boots into Stock Recovery after flash
+Fixed lots of parts to improve the Toolkit
ToolKit v5.0 (23rd August 2012)
+Added Root Support for new Jelly Bean Builds
+Added Model Selection Screen at startup for selecting different builds
+Added cwm unroot zip file for quick unroot without wiping and flashing stock firmware
+Added cwm root for Superuser or SuperSU
+Added new Stock and Insecure kernels
+Added new Stock Recovery images
+Added new Stock Firmware download method and new links to various Stock Images
+Wrote new Date/Time method to give support for non UK Regions in various functions
+Added teaser for upcoming Quick Pick function
+Added new options to Settings Screen
+Added ‘Help’ option on Model Selection Screen
+Added ‘Auto Update’ check in Settings Screen
+Checked entire code and made edits to parts
ModsSection v2.1 (23rd August 2012)
+Updated Date/Time stamp method
+Updated NAND Backup script
+Added Jelly Bean detection for mods that do not work on that build
ToolKit v4.0 (24th July 2012)
+Added Auto Update Feature (at startup)
+Added 1-Click tar file creator to flash via Odin (from upto 10 images placed in the INPUT folder)
+Added Donator Features Activation from within ToolKit
+Changed Extras Section for new Activation method
+Added CWM Touch 6.0.1.0 to ToolKit
+Added Reboot to Download + Start Odin in ‘Reboot Phone Options’ screen
+Edited backup scripts for easier operation
+Removed Sim Unlock Tool for further testing
+Various tweaks
ModsSection v2.0 (24th July 2012)
+Added NAND backup option when starting to safe guard against bad mods
+Fixed some code
ToolKit v3.0 (4th July 2012)
+Added CF-CWM Recovery (thanks to Chainfire) as option
+Added cache.img dump to backup options
+Fixed /efs backup/restore tool from previous version not working
+Added Galaxy S3 SIM Unlocker by Adam Lange
+Added Samsung Cache Ripper by Adam Lange
+Updated Odin Flash Tool to v3.07
+Added option to NAND backup to Internal or External Storage + keep/delete files on phone after completion
+Added Rename Recovery Restore files for future proofing
+Fixed CWM Rooting as it wasnt working (incorrect script)
+Lots of re-written code for better functionality
+A few minor bug fixes
+A few other things I forgot to write down
ToolKit v2.0 (22nd June 2012)
+Updated CWM Recovery to Touch v5.8.4.3
+Updated Samsung drivers to v1.5.5.0
+Added text on NAND Restore option to check free space (2GB) before starting
+Streamlined Odin flash process. Phone will now automatically reboot into Download Mode
+Added Download Mode to reboot options
+Added Download, extract, flash Stock Rom option. Everything you will ever need to know is in there
+Added Stock Boot Image option
+Added full information on Resetting flash counter
+Alot more minor stuff
ModsSection v1.0 (22nd June 2012)
+Added first version of Mods Section. 3 mods
available for now with more to be added
ToolKit v1.0 (10th June 2012)
+First version of SGS3 ToolKit released
thanks for the great app! coming form galaxy nexus (thanks god i sold it) and knowing it will work flawlessly waiting for dl link
great application
Download link posted in Post#1
Mark.
AWESOME !!
Amazing work ! Can't wait to see what the future holds for this app !!
@mskip good to see u here and congrats on becoming a MOD :0)
Coming from the Galaxy Nexus,and i used your toolkit software many many times and it worked like magic..and im sure this one will be the same
Sent from my GT-I9300 using Tapatalk 2
Hi Mark,
amazing work and very useful app,
thank you very much!
Absolutely Perfeeeeect tool
Amazing, wonderful. Damn job dude. no words at all. U all DEVS ROOOOCKS. AMAZING GUYS HERE.
sooo goood baby baby
Used your toolkit on my Gnex (so easy to use )
And now we can enjoy it on the S3 !! Thank you mskip, for your great job, and for sharring this wonderful tool !
thank you very much good business
Thank You from a fellow East Anglian S3'er
72931761ND9517718
PS: ROM Manager isnt great with Sammy devices - may want to update first post to recommend use of CWM Manager instead.
Cool look epic good work :thumbup::thumbup::thumbup::thumbup:
Sent from my GT-I9300 using xda premium
Very good work!!
I test now the backup options. I already made an efs-backup and try now to make a full backup of the internal sd-card. Till now everything work very well.
Thanks very much for the toolkit!!
subvertbeats said:
Thank You from a fellow East Anglian S3'er
72931761ND9517718
PS: ROM Manager isnt great with Sammy devices - may want to update first post to recommend use of CWM Manager instead.
Click to expand...
Click to collapse
Thank you very much
First post updated, I just took out the link to Rom Manager as I have never used CWM Manager and dont know if you can get to CWM directly from the app.
What part of East Anglia?
Mark.
hurray said:
Very good work!!
I test now the backup options. I already made an efs-backup and try now to make a full backup of the internal sd-card. Till now everything work very well.
Thanks very much for the toolkit!!
Click to expand...
Click to collapse
You're welcome
If you find any bugs or have any opinion on improvements please let me know as im working on the mods and extras section now for the next version.
Mark.
oned said:
Used your toolkit on my Gnex (so easy to use )
And now we can enjoy it on the S3 !! Thank you mskip, for your great job, and for sharring this wonderful tool !
Click to expand...
Click to collapse
Although the S3 is a bit harder to automate without fastboot flashing I hope the ToolKit can be every bit as good as for the GNex (maybe even a bit better)
There will certainly be alot more mods in the mods section
Mark.
FIRMWARE MEDIAPAD ICS 4.0.3 HWMOD C232B005
Kernel: 3.0.8 ([email protected]_server) Thu Jun 7 17:50:45 CST 2012
Compiler: (gcc version 4.4.3 (GCC)) #1 SMP PREEMPT
Baseband: 314007 - Android: 4.0.3 - GAPPS: 4.0.4
Incremental Build: V100R002C002B010SP030
This is a modified copy of the official firmware released by Huawei C232B005 General Version (June 2012). It doesn't require running "sanix" patches nor modifications to the system partitions "boot.img"/"system.img".
As in the original, the zip file contains instructions on how to upgrade from a MicroSD memory card. The firmware contains updated GAPPS ICS 4.0.4 (gapps-ics-20120429-signed.zip).
It has been said several time however you know you will void your warranty by modifying your device.
I have tried these modified firmware several times on my MediaPad before rendering them available.
On "Androidiani.com", in the MediaPad forum, I have been releasing these same kind of modifications for the following firmwares:
C232B002, C167B003, C170B008, C170B009 and currently C232B005
I have to say thanks to many users on that forum for their contributions and suggestions.
Before you start the upgrade
Download the firmware ZIP file, unpack the file on your PC and copy the "dload" folder found in the archive on the external MicroSD card. In the same archive you will also find Huawei original PDF document in English explaining how to upgrade the device and a "readme.txt" file that lists version numbers of the various components of the firmware (kernel, baseband, build etc.).
Remember to use Huawei's "All Backup" (suggested) or similar tools to backup all the applications and data on the external MicroSD card before proceeding with the update. In this firmware it is possible to activate a remote Google backup of the applications installed from the Market using a personal Google account ("Setting -> Backup and reset -> Backup account").
Standard update method
Only copy the "dload" folder in your MicroSD card, reset the device by switching the device off (press "power" button for 10 sec). If the device doesn't start automatically again press the power button. If the update does not start repeat the operation and additionally keep pressing the Volume+ button (on the right).
Alternate update method
Use the phone application to dial the following number * # * # 2 8 4 6 5 7 9 # * # * then, from the menu that appears, select:
"Project Menu Act -> Upgrade -> SD Card Upgrade -> SD Card Upgrade External Storage".
For both methods
Follow the instructions on the device screen (in green), the complete update process will be about 10 minutes, then the device will reboot a couple of times, be patient and let the device be quiet a couple of minutes more before touching it (while updating the sim, sn, touch & coulometer firmware).
I always suggest executing a "Factory reset" after a firmware upgrade. You can do that from "Setting -> Backup & reset -> Factory data reset" and if possible also check the box related with the formatting of the device internal memory (after ensuring you have made a backup of all you may need).
IMPORTANT !!!
To avoid touching key partitions of the Android OS and the original firmware I decided to leave the duplicated "Gallery2" application (found in the "system" partition). For this reason, after the upgrade you will end up with two "Gallery" applications. Deactivate or remove the first one of the two, the one which is smaller in size. The second one has more options (Google+/PicasaWeb sync) than the one pre-installed by Huawei. Since the device is "rooted" any file manager capable of browsing folders with "root" privileges will be enough to perform the removal.
Informations
This firmware uses an alternate method to obtain "root" permissions on the MediaPad avoiding modifications to important parts of the original firmware ("boot" and "system"), at the same time it adds missing Huawei/Google applications and enable some of the functionalities that were not enabled in the original firmware.
Modifications have been applied exclusively to the device "cust" partition ("cust.img.ext4") all the remaining partitions and files have been left untouched compared to the originals Huawei ICS 4.0.3 firmware released 21 June (C232B005).
Updated:
all ICS Google Apps (gapps-ics-20120429-signed.zip)
modified permissions for "busybox" executable (755)
International language selected as "default" (English)
International wifi settings for channels (13)
Added:
Huawei applications missing in the official version
GenieWidget application included in newer gapps-ics
Removed:
"Huawei Input Method" add-on keyboard and all related Language Packs (42)
Gmail, Maps, Music2, PlusOne, Street, TagGoogle, Talkback, Youtube
Aldiko, Facebook, FoxitReader, Twitter, YozoOffice and related libraries
two space hungry games, Asphalt6, LGolf and related libraries
images and demo animations (media)
List of added/updated applications and their versions:
AccountAgent-1.1.17.apk
AllBackup-4.1.33.apk
HiDisk-3.0.21.apk
HwOUC-2.3.8.apk
PhoneFinder-2.2.0.apk
PushAgent-2.2.1.apk
Superuser-3.0.7.apk
List of functionalities added to this firmware:
"root" permissions, Superuser.apk, busybox v1.20.1, su v3.0.3.2
firmware updates from "Settings" (Huawei/Google components)
Google GenieWidget & Google Backup Transport functional
Huawei applications: All Backup, HiDisk, PhoneFinder
* FIRMWARE DOWNLOAD *
ZIP containing firmware and software (essential: huawei_apps + google_apps):
Download size: 258.649.399 bytes (247Mb) - md5: 8c8bac1094d7dcb87d959a3be1482f6f
MIRROR 1 (GameFront)
* HUAWEI KEYBOARD DOWNLOAD *
ZIP containing the new keyboard and 42 additional language packs (Huawei Input Method):
Download size: 16.266.684 bytes (15Mb) - md5: 22b4aeddd6c214ffc7e5ef753216d68b
MIRROR 1 (GameFront)
Have fun,
.:HWMOD:.
HWMOD Linux kernel 3.0.42 Overclocked + customizations update
This update replaces (overwrite) the "boot" and "cust" partitions of the device.
The update process should retain all installed applications and data.
To achieve "non destructive" update I used the same method used in OTA updates.
At the end of the update process the tablet will reboot once more after restoring the
serial number, sim/imei, firmwares for touch-screen and coulometer etc.
The update methods remain unchanged (no need to use "fastboot/adb"):
1) download the compressed ZIP archive and unpack it on your PC
2) copy the "dload" folder contained in the archive on the external SD card
3) restart the device and follow exactly the on-screen instructions (in yellow)
The "boot" contains the new kernel 3.0.42 Overclocked and the initialization "ramdisk".
The "cust" partition has been updated with the new "Superuser.apk", "su" and "busybox".
Inside the ZIP compressed archive you will find a "readme.txt" with expanded informations and instructions.
Credits to "arkusuma" for the modifications related to the touch screen driver and to "contributors/modders" on XDA.
* FIRMWARE DOWNLOAD (updated 2012/09/10) *
ZIP contains kernel (boot.img) and customization software (cust.img)
Size: 82.463.617 (∼80Mb) - md5: 05dc4f0a5aa564dc8f628659540bbb8d
MIRROR 1 (GameFront)
* HUAWEI KEYBOARD DOWNLOAD *
ZIP containing the new keyboard and 42 additional language packs (Huawei Input Method):
Download size: 16.266.684 bytes (15Mb) - md5: 22b4aeddd6c214ffc7e5ef753216d68b
MIRROR 1 (GameFront)
Have fun,
.:HWMOD:.
what modifications did you made?
441Excelsior said:
what modifications did you made?
Click to expand...
Click to collapse
Sorry for the short description, really, many more info are missing. I will do my best to update and translate asap the rest of what I have published on "Androidiani" forum.
Basically I have added "root" permissions, removed all the extra applications and updated the Google Apps to a newer version (gapps-20120429-signed.zip).
I also added a few missing Huawei utilities like AllBackup, HiDisk and PhoneFinder that were found on previous Huawei releases.
The method I used to add "root" permissions is a bit different than on other modified firmwares. I only changed "cust" partition to achieve that, all the other partitions have been left untouched as the originals from Huawei.
I probably trust Huawei developers a bit more than others
441Excelsior said:
what modifications did you made?
Click to expand...
Click to collapse
OK, I added the expected informations in the op.
I will add more info and corrections.
How bout the edge to.H/3G? In 002 when there's still stuck problem..
Sent from my SPH-D710 using Tapatalk 2
It should work in this firmware (also I haven't tried yet).
The problem you mentioned was already fixed in both Russian releases.
There are no known problems for the phone to switch between 3G <-> HDSPA.
no gmail in this release? Noticed it when i was to replace gmail apk with a modified one.
mangoman said:
no gmail in this release? Noticed it when i was to replace gmail apk with a modified one.
Click to expand...
Click to collapse
Right ... not there. Why include Gmail if you wanted to replace it anyway ?
It would have happened anyway at first update (if you decided to install it).
I have tried to remove everything that can be installed later through the Market or by placing the file in the SD card. That gives end users more freedom and let them sort out OS/firmware related problems vs. applications bugs/problems.
This also avoid keeping duplicates in your device.
Since this firmware have "root" privileges, I suggest users to install their "preferred" applications in "/cust/channel/normal/delapp/" folder so if they later want to do software reset (Factory data reset) they will not loose their "preferred" applications.
Copying the ".apk" in that folder has to be done using a file manager that works and let you browse folder with "root" privileges (read/write).
Hope I answered the question and left additional informations.
There's a bug on HWMOD b005.
Double Galery icon.
I've big mistake to disable it, and my device freeze.
fortunately i can recover it with hard reset.
I think it'll better if you add V6Supercharger too.
Thank you very much
arekwaru said:
There's a bug on HWMOD b005.
Double Galery icon.
I've big mistake to disable it, and my device freeze.
fortunately i can recover it with hard reset.
I think it'll better if you add V6Supercharger too.
Thank you very much
Click to expand...
Click to collapse
This has both galery applications, one from the ICS and another from Gapps pack. You can safely uninstall anyone using Titanium Backup. I uninstalled the default ICS one. No problems so far...
Sent from my HUAWEI MediaPad using XDA Premium HD app
arekwaru said:
There's a bug on HWMOD b005.
Double Galery icon.
I've big mistake to disable it, and my device freeze.
fortunately i can recover it with hard reset.
I think it'll better if you add V6Supercharger too.
Thank you very much
Click to expand...
Click to collapse
you right agan gigiku.com
shiranmotha said:
This has both galery applications, one from the ICS and another from Gapps pack. You can safely uninstall anyone using Titanium Backup. I uninstalled the default ICS one. No problems so far...
Sent from my HUAWEI MediaPad using XDA Premium HD app
Click to expand...
Click to collapse
Exactly, you are correct, this is not a bug, it was on purpose.
No freezing and no crashes that we know about in C232B005.
I wanted to leave the choice to the users installing this firmware.
Users can remove the one they want/prefer, one is part of the manufacturer ICS release the other is in Google Apps, they have similar options but different functionalities. The one from Google can sync your picture with those uploaded in G+/PicasaWeb. I personally prefer to keep the second one, the bigger in size.
Since this firmware has "root" privileges it will be easy to remove the duplicate Gallery2 application by using a file manager or Titanium Backup as suggested.
I have not included V6 Supercharger and other stuff because it is not sure everybody wants it on their devices. It can be installed though, for those that want it, however I doubt it's needed on the MediaPad.
Updated the OP with needed informations for applying the upgrade process.
Added an additional mirror for the download of the firmware.
Please tell if you find mistakes or have suggestions.
.:HWMOD:.
hwmod said:
Exactly, you are correct, this is not a bug, it was on purpose.
No freezing and no crashes that we know about in C232B005.
I wanted to leave the choice to the users installing this firmware.
Click to expand...
Click to collapse
Thank you for your respond. I don't know exactly how my mediapad freeze. Now I reinstall your ROM again, and no problem so far.
If you don't mind, I have request. How about change boot animation? may be like OsiMood.
actualy, I love OsiMood User Interface, but cause They stop updating, I'm not using it anymore.
But, If you don't want to add it on HWMOD, could you tell me how to change it, please. I've try many application to change it, and change from /system/media/bootanimation.zip . But, it still not change.
Thank you very much.
arekwaru said:
Thank you for your respond. I don't know exactly how my mediapad freeze. Now I reinstall your ROM again, and no problem so far.
If you don't mind, I have request. How about change boot animation? may be like OsiMood.
actualy, I love OsiMood User Interface, but cause They stop updating, I'm not using it anymore.
But, If you don't want to add it on HWMOD, could you tell me how to change it, please. I've try many application to change it, and change from /system/media/bootanimation.zip . But, it still not change.
Thank you very much.
Click to expand...
Click to collapse
I never did it myself and it depends on what are your objectives.
If you want to just change the boot animation in your device doing what you did should be enough (make sure you use a correctly formatted/packed "bootanimation.zip") and give the right attributes to the files you modify.
If you need to modify an existing firmware and add a different boot animation then you have to handle "ext4" partitions images files under Linux ("system.img.ext4" in the update archive) and substitute that file in the "ext4" image.
If you just want to modify the boot logo, not the animation, you have to rewrite the "splash" partition using "fastboot" (called "logo" in MediaPad mmcblk0p10).
I need to do a test on a brand new Mediapad (not "rooted") but I don't have access to one.
Could someone execute the following "fastboot" command on a new device:
Code:
fastboot oem device-info
and report their results here ?
I have used 2-3 roms in my mp, is it ok?
dark_fighter said:
I have used 2-3 roms in my mp, is it ok?
Click to expand...
Click to collapse
Post them anyway, also they shouldn't be different from mine (more or less):
Code:
[email protected]:~# fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: true
OKAY [ 0.294s]
finished. total time: 0.294s
[email protected]:~#
I am not sure the internal "fuse" is set up to allow people some chance
I believe it is a one shot only sw "fuse", that's why I asked for a brand new device, one with the original manufacturer firmware and never rooted/unlocked.
Thank you.
Hotmail over active sync as a cooparate account not works for me. Any other faced the same issue? It says couldn't connect to server.
Sent from my HUAWEI MediaPad using XDA Premium HD app
Note to NON SHV-E160L users
This software & this thread is aimed at developers Mainly, Please don't post 3 line request like "my device is bricked , please help" as you will be ignored, if you cant do the research required to provide the right details plus finding the correct files required then this thread is not for you and you should post in the device thread for your device, This program and it's associated files & thread is NOT being actively developed but the thread remains open for user to post more information, additional files, updates from the public etc.
It's not here for lazy people to scream fix my device, can those type of users please speak to your retailer, cell phone service shop.
I will reiterate again, THIS IS A DEVELOPMENT THREAD AND NOT A REQUEST PAGE FOR "fix my device"
PLEASE NOTE: This tool only comes pre-packed with files for the Korean SHV-E160L galaxy note. Usage on other devices requires that you understand the requirements, this includes but not limited to :-
1. Alteration of the scripts to use the files specific to your device
2. Correct HEX and SD-CARD loader also known as sdcard mbn
3. Correct partition information (knowing if it's MBR/GPT or hybrid)
4. Correct bootloaders for your device (SBL1/2/3/ABOOT)
I am not currently doing further development on this tool, it is here for anyone to expand on use how they seem fit so long as the authors involved are given the credit.
Users are welcome to build and post altered versions specific to their device but PLEASE post plenty of information as to what device/model it is for or the post may be deleted to protect other less educated users.
darkspr1te
Hi All,
I've updated my Debrick tool to Version 2.
Many Changes to the base code, inclusion of new tools, Almost a one click Linux solution for Qualcomm Development and debricking of Qualcomm devices.
As documented on this thread SHV-E160L home debrick thread I debricked a qualcomm based msm8660 device without using any special devices.
my first tools were internal development and had more bugs than a sewer, so after many hours of work i can now bring this new version to you.
Please do not pm with bugs, POST HERE Only.
This tool currently only supports the SHV-E160L , if users willing to provide the files from their devices I can expand the support of this tool.
in most cases linux is required for this, a ubuntu live cd/flash will work perfectly.
New Feature, Windows Based BACKUP of partitions and bootloaders, ROOT/Python27-windows is required and cannot function without this.
*nix backup coming soon,
Rules for posting backups
Post ONLY the link here, use www.sendspace.com to upload your backup zip (remember to change the .zip filename to reflect your device, example SHV-E160L-16GB.zip )
zip up only the backup folder, not the whole program, right click on backup folder, sent to compressed folder, rename.
this program does not backup personal or device specific data like IMEI number, it only backups the bootloaders, partition table and .pit file for samsung SHV based devices
When Posting links, please include your device details well, a example would be
SHV-E160L 16 GB, 9000lang rom,
The rom part is only so if we a tracing possible backup issues that may be rom specific.
Future backup features will include automatic detection of .mbn partitions based on qualcomm header.
Support for non SHV devices will be slow, but future versions will include other devices.
Well Enjoy,
EDIT: some users are reporting cookie not present error could be fixed by using a winxp/another qpst driver windows driver. this is unconfirmed bu i thought i should mention it. 04-12/2013
Changelog:- V2-2(dev version only - not a public release)
added command line device/folder parameter, you can now specify a unzip copy of posted bootloaders and it will restore them
added additional file to specify output sectors based on getpart data, testing option for building partition0.bin by hand based on known simalr devices
added dev switches for wiriting specified parts only
added skip aboot option (for now it is specified to skip writing of aboot.mbn, public release will be opposite, you will have to force writing aboot , sbl1/2/4/tz/rpm seems to come as one package, interchangeable as a package, aboot is totally device specific)
bugs:-
there is a known bug in the getpartbin.py python program, it cannot handle greater than 29 partitions.
Changelog:- V2-1
added windows backup.bat program to backup all bootloaders and partition0.bin
minor changes to code for changing device (current version support only changing of variable $DEVICE, feature will eventually be cmd line based)
tesing of backup files
bugs:-
there is a known bug in the getpartbin.py python program, it cannot handle greater than 29 partitions, and one will to help in python please let me know. I am not the author of the program
Changelog : V2
Improved error checking*
automated qdload detection*
automated qdload hex & .mbn upload
automated detection of device in sd-card mode*
user input*
colours
major code changes to start support for automatic parition information & collection allowing backup to be one command and upload to a website for distribution & recovery for all
development documentation
Code changes to allow expansion to other Qualcomm devices
Sendspace Links
BrixFix V2-1-Inc Python27-Inc cwm recoveries
http://www.androidfilehost.com/?fid=9390355257214632490 mirror tanks too Marduk191
Brixfix V2-1 No Python for windows, No cwm-recovery-Slim Version
Brixfix V2-1-Super-SlimNo drivers, bootloaders, python-win.
Media Fire Links
BrixFix V2-1-Inc Python27-Inc cwm recoveries
SHV-E160K 32GB Recovery files
SHV-E160L 32GB Recovery Files
SHV-E120L Recovery Files (posted on another page)
-------------------------
Here is the README
brixfix V2
=================================
By dakrspr1te ========Doc=V=1====
=================================
Thanks To :-
E:V:A, SLS, JCSullins(Rootz Wiki), Adam Outler, many more, sorry if i've missed you out.
Warning, Although i've tested this tool many times on my own devices, it always has the potential to damage both computer & cell phone device, YOU HAVE BEEN WARNED!!!!
This tool is designed to repair SHV-E160L Korean Galaxy Note 1 based on the MSM8660 & MDM9600 Qualcomm Chips
It Only works with devices that are stuck in QDLOAD mode or 05c6:9008 as the PID/VID
It uses Tool/info Written By Others as well as myself.
Namely :-
qdload - http://github.com/jcsullins/qdloader
getpartbin.py - http://blog.csdn.net/su_ky/article/details/7773273
hex2bin - hex2bin.sourceforge.net
Instructions
############
connect Qualcomm based device to usb port on linux PC, not tested under windows via USB redirection,
on command line run
sudo ./brickfix
Follow on screen instructions, tool will detect device in QDLOAD mode (05c6:9008) and switch to DMSS protocol, upload a hex (converted to bin for this purpose)
the hex is then executed and the device switches to Streaming Protocol, at this point we write a .mbn file to the internal emmc chip, at the end of the emmc write process the device then reboots
after the reboot re-running brixfix with detect the device in the second stage for repair , the device's emmc is accssable as a sd-card, we then write back the damaged parts of the bootchain,
at a minimum you must write a new partition table or the device will always boot in sd-card mode, WARNING, failure to write the rest of the boot chain could leave your device in a situation
which give only black-screen, no usb enumeration, dead. The only way around that is jtag, or finding the Boot resistor which switches the device back to QDLOAD mode, or emergency boot.
goto http://forum.xda-developers.com/showthread.php?t=1914359 for further details.
Come give me thanks on XDA if this tool helped you
Additional Tools (DEV Level)
===========================
getpartbin.py - A tool for backing up the primary partition & extended parition tables and combines them into a writable parition0.bin file (python)
qdload.pl - A tool for talking in the HDLC framed DMSS & Streaming Protocol's used by Qualcomm (Perl)
switchmode.sh - A executes qdload.pl for msm8660 device upload
get-part.sh - **DEV** unfinished tool by darkspr1te for creating partition tables in sfdisk format and .csv format (to be used in the future to create parition0.bin plus more automated collection)
tools/ - Folder containing armv5 (arm7 compatible) tools for parition manipulation and data collection
SHV-E160L-16GB/ - Folder contain SHV-E160L bootloaders & pit file
ADB/ - Folder containing adb programs
extras/ - Folder containing odin and clock work mode recovery installers for 160l devices
QUALCOMM/ - Windows drivers (For QPST, Not required in linux, included for backwards compatability with older guides)
hex2bin - convert your xxxxMPRG.hex file to bin for use with qdload
Tips
====
Additional
==========
I will accept brick qualcomm devices for developing further debricks. pm me via XDA Forums
Darkspr1te
Click to expand...
Click to collapse
Re: SHV-E160L Debricking Tool / Qualcomm Tool Pack
Kudos to u.
Nicely done ..OP
I'll get this thread added into the note super thread .
An amazing resource to be sure ...
Many thanks ....g
Very nice!
< reserved >
Thank you!
Re: SHV-E160L Debricking Tool / Qualcomm Tool Pack
I'll take a deeper look at it later.
You should note that qualcomm chipsets do not have support for USB 3.0. While the linux USB 3.0 driver is backwards compatible with the older standards, it is still buggy so it's best to only use USB 2 and lower ports.
Also, you should be using a 32bit Linux distro with a kernel from 2012 or later.
-SLS-
Will this work on SHV-E160S??
Two days ago I tried to flash the 'N7000XXLSA_N7000OXALSA_DBT' into a SHV-E160S.. Odin failed two times
When tried to reboot the phone nothing appears(just black screen). When i connect it to my PC, windows device manger shows ' QHSUSB DLOAD'..
Can this tool fix my problem? Please help me..
Re: SHV-E160L Debricking Tool / Qualcomm Tool Pack
BarakOsama said:
Two days ago I tried to flash the 'N7000XXLSA_N7000OXALSA_DBT' into a SHV-E160S.. Odin failed two times
When tried to reboot the phone nothing appears(just black screen). When i connect it to my PC, windows device manger shows ' QHSUSB DLOAD'..
Can this tool fix my problem? Please help me..
Click to expand...
Click to collapse
Probably. You'll need Linux. If you don't have linux, go grab the above mention ubuntu live cd (I suggest version 12.04 32bit)
As I'm not familiar with that device I don't know exactly what will need to be fixed.
-SLS-
Re: SHV-E160L Debricking Tool / Qualcomm Tool Pack
BarakOsama said:
Two days ago I tried to flash the 'N7000XXLSA_N7000OXALSA_DBT' into a SHV-E160S.. Odin failed two times
When tried to reboot the phone nothing appears(just black screen). When i connect it to my PC, windows device manger shows ' QHSUSB DLOAD'..
Can this tool fix my problem? Please help me..
Click to expand...
Click to collapse
Please state specs of your model, you flashed the wrong firmware which has crashed your pit/partition and your running a boot chain for another device, which is failing due to signing issues
By specs I mean device size, original few etc, we can recover it, I am sure of that, I just need some info , don't jump the gun, if we have your device files already it would be a simple case of running ./brixfix.sh I was able to recover all my files from my device, same would be you all sure, but you WILL need a copy of Ubuntu as SLS said
Sent from my A210 using Tapatalk 2
darkspr1te said:
Please state specs of your model, you flashed the wrong firmware which has crashed your pit/partition and your running a boot chain for another device, which is failing due to signing issues
By specs I mean device size, original few etc, we can recover it, I am sure of that, I just need some info , don't jump the gun, if we have your device files already it would be a simple case of running ./brixfix.sh I was able to recover all my files from my device, same would be you all sure, but you WILL need a copy of Ubuntu as SLS said
Sent from my A210 using Tapatalk 2
Click to expand...
Click to collapse
What files do you need from the ATT Note? I know what you have done, but don't understand it, but sure as hell would like to help !!!!!!!!!!
I have Ubuntu...(Yay !) ..... let me know the steps to dump files.
PS: Is there any chance of getting Tegrak kernel or ROMs for ATT Note. Maybe I should ask what is the status of the Tegrak kernel etc.? I see it on the app store, but I know its not for ATT Note. I remember Tegrak from when I used to use Voodoo Sound that Tegrak kernel supported. But I have never found anything comparable to voodoo sound for our more 'advanced' phones like the note.
PS: Does this make any sense to you ? Or am I rambling ?
Shv-e160s 32gb..
darkspr1te said:
Please state specs of your model, you flashed the wrong firmware which has crashed your pit/partition and your running a boot chain for another device, which is failing due to signing issues
By specs I mean device size, original few etc, we can recover it, I am sure of that, I just need some info , don't jump the gun, if we have your device files already it would be a simple case of running ./brixfix.sh I was able to recover all my files from my device, same would be you all sure, but you WILL need a copy of Ubuntu as SLS said
Click to expand...
Click to collapse
SHV-E160S 32GB, Thats all I know about this..
I'm downloading ubuntu right now. Then I'll try this tool on my device
Re: SHV-E160L Debricking Tool / Qualcomm Tool Pack
This tool works only on the 16gb right now, as soon as I can get a 32gb partition and S about file I will extend it
Sent from my A210 using Tapatalk 2
darkspr1te said:
This tool works only on the 16gb right now, as soon as I can get a 32gb partition and S about file I will extend it
Sent from my A210 using Tapatalk 2
Click to expand...
Click to collapse
Oh.. No luck for me then..
Tool Updated, Please go my OP
SouL Shadow said:
Probably. You'll need Linux. If you don't have linux, go grab the above mention ubuntu live cd (I suggest version 12.04 32bit)
As I'm not familiar with that device I don't know exactly what will need to be fixed.
-SLS-
Click to expand...
Click to collapse
BarakOsama said:
Two days ago I tried to flash the 'N7000XXLSA_N7000OXALSA_DBT' into a SHV-E160S.. Odin failed two times
When tried to reboot the phone nothing appears(just black screen). When i connect it to my PC, windows device manger shows ' QHSUSB DLOAD'..
Can this tool fix my problem? Please help me..
Click to expand...
Click to collapse
As soon as a user uploads a backup for the 160S (16 or 32GB depending on your device) I will include it in a repair file.
chappatti said:
What files do you need from the ATT Note? I know what you have done, but don't understand it, but sure as hell would like to help !!!!!!!!!!
I have Ubuntu...(Yay !) ..... let me know the steps to dump files.
PS: Is there any chance of getting Tegrak kernel or ROMs for ATT Note. Maybe I should ask what is the status of the Tegrak kernel etc.? I see it on the app store, but I know its not for ATT Note. I remember Tegrak from when I used to use Voodoo Sound that Tegrak kernel supported. But I have never found anything comparable to voodoo sound for our more 'advanced' phones like the note.
PS: Does this make any sense to you ? Or am I rambling ?
Click to expand...
Click to collapse
you can find all tegrak roms/kernels via my clean korean rom link in my signature,not sure on ATT but i've ported a few ATT kernels to the 160L so it's possible to convert back. *nix backup coming soon but for those that want to jump the gun, just run the same adb commands as in backup.bat and also the python command. please note they will download the files to the current directory so make a directory first, cd into it and refer back to the scripts. to run python partition0.bin script just use python ../getpartbin.py to create a partition0.bin file in current directory.
root is required for backup, python27 is required for windows backup (13mb file, included)
Thank
darkspr1te said:
As soon as a user uploads a backup for the 160S (16 or 32GB depending on your device) I will include it in a repair file.
Click to expand...
Click to collapse
I found some useful links (I hope) to the understanding of some mechanisms useful in debricking of devices using Qualcomm chipsets. I hope this may help generally, even to unbrick the i8150 (Ancora)!
http://blog.csdn.net/su_ky/article/details/7773273
http://www.anyclub.org/search/label/emmc boot
http://www.anyclub.org/2012/04/how-to-build-emmc-flash-programmer.html
Some stuff is in chinese, other in english but reading a bunch of articles I became convinced that the explanations available can be very useful!
Regards!
Just curious, why not post under original development? Love to see you there, you deserve it. :thumbup:
Sent from my SAMSUNG-SGH-I717 using xda premium
shv-e160L 32GB
Any success on the SHV-e160L 32GB yet?
So guys,
Are you new here , does these terms like bloatware, adb seems new to you, but it wont be after reading this thread.
ADB: Android Debug Bridge, a utility to run on a PC to allow connection to and control of an Android device. Part of the Android Software Development Kit (SDK), it allows for ROOT-level access to the Android device from a computer.
AOSP: Short for Android Open Source Project. The open-sourced code from which individuals can build new distributions of Android.
APK: An Android executable file, similar to the .exe file in Windows. Most programs will install with a .apk file.
Apps2SD:A method of storing applications and cache on the device's microSD card.
Bloatware: Software or 'apps' that you don't need, but come preinstalled to a device's /system partition, meaning that you cannot remove them unless the device has been rooted
Boot Animation: Boot animation is a term for a graphical representation of the boot process of the operating system. After you switch on / reboot phone you see this.
BOOTLOADER: There are two of these; the primary and secondary bootloaders. These programs tell the Android device how to start up, and are critical to its functionality.
Bootloop: When your system recycles over and over without entering the main OS.
BRICK/(HARD BRICK): An Android device that is completely non-responsive, i.e. nothing lights up, the screen does nothing, no combination of button presses cause any reaction. Can only be restored by JTAG or warranty service.
BUILD.PROP: A plain text file which contains environmental variables for the system to use during operation. Can be hacked to fake a different model for increased functionality, among many other operations. It is also used to make tweaks to boost speed/performance, etc.
BUSYBOX: An application that contains many standard Unix tools.
BUTTON COMBO/THREE BUTTON COMBO: The act of pressing several buttons at the same time to produce a desired result (e.g. press and hold volume up+home button+power button for 10 seconds will reboot into the RECOVERY menu at any movement when phone is on or Press and hold volume down+power button+home button to get into ODIN mode/DOWNLOAD mode).
Cache:A component that transparently stores data so that future requests for that data can be served faster.
CM: Short for CyanogenMod. CyanogenMod is an Android build built from the Android Open Source Project, and its builds are usable on multiple different Android Devices.
CPU: It stands for Central Processing Unit and handles all the complex mathematical formulas necessary to do everyday things like surfing the Internet.
CSC - File with Carrier Customizations
Custom bin counter: A line of code in several Samsung Galaxy devices' bootloaders that counts the number of times a user uses ODIN to flash ROMS/KERNELS to the device. Commonly used to detect software modification. This is called custom bin down in ODIN mode and it should be 0 to claim warranty. Can be reset with GALAXY TOOLBOX APP by Doky73
Custom: Independent developers who like to customize their devices beyond the standard options provided often tend to release the fruits of their labor for the rest to enjoy, in form of custom ROMs.
CWM: Short for ClockWorkMod Recovery Menu. This is a program that allows you to install custom ROMS/KERNELS as well as do many other customizations. Often referred to as the "RECOVERY MENU"/"CWM"
DALVIK CACHE: The collection of program information stored for use by the DALVIK program. This can be cleared from the RECOVERY menu to resolve issues with the Android OS.
DALVIK: The Android operating system's memory management tool. This program handles which other programs are running and assigns memory to them
DEODEXED: Removing the .odex files from an APK file. The .odex files contain a list of dependencies for the associated file, and if something changes, the .odex (and similarly, the associated file) not longer function correctly.
DMESG: dmesg (for "display message") is a command on some Unix-like operating systems that prints the message buffer of the kernel..
DOWNLOAD MODE: Read Button combo to know about this.
EFS: The directory /efs on the Android device's internal storage. Contains files with the Android device's IMEI, wireless devices MAC addresses, product code, and other information..
EMMC: Short for Embedded MultiMediaCard. A chip architecture consisting of an embedded storage solution with MMC interface, flash memory and controller, all in a small ball grid array package.
EXT4: A journaling file system (e.g. NTFS, FAT32 are file systems) often used by Linux distributions. Can be used with Android.
EXTERNAL SD: A micro SD card that has been inserted in the micro SD slot in the Android device. Can be removed.
FACTORY RESET: This will remove all user customizations in the Android OS, returning it to a factory state. Note: This will not wipe the Internal SD card. It will just make it as a phone just bought from the store state.
FC/FORCE CLOSE: When a program on the Android device becomes unstable/gets an error, the DALVIK program will force it to terminate to prevent further system instability which appears as a Force Close message usually in phone.
FLASHING: The act of writing code to the Android device. ROMs, MODEMs, KERNELs, and BOOTLOADERs can all be flashed. Independent from, and having nothing to do with, Adobe's Flash product.
FREEZE: Specific to LINK2SD/TITANIUM BACKUP. Using these 2 apps, the user changes a program into a non-functional, but still installed, state. Useful for identifying problem and FCs.
gapps - Google Applications, like GMail, Calendar, Maps, G+, etc
GB - Gingerbread, AKA Android OS 2.3.X
GOVERNOR: A program that interacts with the device hardware to increase or decrease the processor's clock speed (e.g. at low usage, it will set the processor speed to 400 MHz, but as usage increases, it would scale up to 1000 MHz).
HSUPA/HSDPA: Short for High Speed (Up/Down) Packet Access. This is 3G+, and is the Android device's internet speed level between 3G and 4G.
ICS: Short for Ice Cream Sandwich, the Android OS version 4.0.x.
IMEI: Short for International Mobile Equipment Identity. A unique number to identify GSM, WCDMA, and iDEN phones. Used by GSM networks to identify valid devices.
INTERNAL SD: The internal storage memory of the Android device. Not a physical SD card that can be removed.
JB: Short for Jelly Bean, the Android OS version 4.1.x.
JIG: A piece of hardware that makes a physical connection between pins of the USB slot to force the Android device into DOWNLOAD mode.
JTAG: A process of connecting directly to the main board of the Android device to rewrite corrupted BOOTLOADERS.
KERNEL: The kernel is a program that constitutes the central core of a computer operating system. It has complete control over everything that occurs in the system.
LAST_KMESG: last_kmsg is a dump of the printk statements from the kernel before the operating system itself crashed.
LAUNCHER: A program that launches programs in Android. Examples are Touchwiz (Samsung), HOLO Launcher, Launcher Pro, ADW Launcher, and Go Launcher EX.
LCD Density: Pixel density is a measurement of the resolution of devices in various contexts; typically computer displays, image scanners, and digital camera image sensors.
LOGCAT: A command to view messages in one of the system logs. See Android logger.
LTE: Stands for Long Term Evolution. It is based on the GSM/EDGE and UMTS/HSPA network technologies, increasing the capacity and speed using a different radio interface together with core network improvements.
MAI77 method: Its only known here. So dont say this out of SGY forum. This is a method to flash kernel through CWM using Kernel flasher tool made by MAI77. Its basically you have kernel flasher tool and boot.img file in SDCARD root and you select kernel flasher tool in CWM and it will install boot.img file which is the kernel you selected.
MD5 CHECKSUM: A 32-digit (128-bit) hash number generated by a cryptographic program to ensure that a downloaded file matches the original file. The original file is run through the MD5 generator program, which creates the 32-bit number. This number is checked against the md5 number created with the file the end user receives to ensure file integrity.
MIUI: A Chinese built-from-source ROM. Short for "Mobile Internet User Interface". Also can refer to the MIUI music player, which has been included in other ROMs.
Mod: The act of modifying a piece of hardware or software or anything else for that matter, to perform a function not originally conceived or intended by the designer.
MODEM: The software that interfaces with the phone's radio hardware to connect to cell phone towers.
NANDROID BACKUP: A complete system image backup of the Android device except for the MODEM and KERNEL. Can be accessed from CWM.
ODEX: A file that is associated with an APK file, containing a list of the dependencies for the program. See also DEODEXED.
ODIN: A Samsung proprietary program that allows the Android device to be flashed back to stock or with custom software.
OVERCLOCKING/OC: Setting the processor's clock speed to run faster than its default setting, i.e. 1248 MHz (1.2 GHz) vs 832 MHz (Default)
OTA - Over-the-Air (usually used as "OTA update" for firmware updates that can be installed directly via 3G/4G/Wi-Fi without the need of an PC)
PIT FILE: Short for Partition Information Table file. One of the possible file types used while flashing with ODIN or HEIMDALL.
Port: To Take a rom or app from one phone and program it to work on a different one.
Ram: (Random Access Memory) A group of memory chips, typically of the dynamic RAM (DRAM) type, which function as the computer's primary workspace.
RECOVERY: The menu that allows a user to do many low-level operations on the Android Device. This menu can either be the stock Samsung menu, or the CLOCKWORKMOD RECOVERY MENU (CWM). See also CWM.
RFS: A Samsung-proprietary file system (e.g. NTFS, FAT32 are file systems) used on some Android devices. Stands for Robust File System.
RIL - Radio Interface Layer
ROM: The collection of programs, themes, and settings that create the general look-and-feel of your Android device. This is what most users will initially be wanting to change. Or custom ROM firmware file, Can also refer to a Read-only memory.
ROOT: Changing the permission level of the Android system to its most powerful level, the root user, allowing full access to the file system. More like Administrator permission in Windows OS.
SGS /SGSD /SGSP /SGSPD : Samsung Galaxy Star / Samsung Galaxy Star Duos / Samsung Galaxy Star Pro/ Samsung Galaxy Star Pro Duos
Sideloading: It means installing applications without using the official Android Market.
SOFT BRICK: A device that is not functioning correctly, but still shows some signs of operation. See also BRICK.
STOCK: The Android software version that comes installed on new devices, prior to sale to the user. Can also be used to refer to the Android software issued from Samsung or the carrier.
Superuser/SU: On many computer operating systems, the superuser is a special user account used for system administration. Depending on the operating system, the actual name of this account might be: root, administrator or supervisor.
TETHER: Connecting the Android device to a computer via a wired or wireless connection to allow the transfer of data through the Android device's internet connection. Commonly used to provide internet access to a laptop or desktop computer when other methods are not desired or available.
THEME: A collection of images, backgrounds, colors, font types, and other visual items to change the Android device's look and feel. Separate from LAUNCHER, and is usually FLASHed in CWM.
TWRP2 - an alternate recovery mode for your phone
UNDERVOLTING/UV: Setting the voltage levels drawn by the Android device to a lower level to reduce overall battery usage.
Updater Script: When Android devices install updates via CWM/recovery mode they have to perform a wide range of functions on files and permissions. The scripting language is called Edify and is defined primarily in the bootable/recovery/{edify,edifyscripting,updater} directories of the Android source-code tree.
WCDMA: Short for Wideband Code Division Multiple Access. An air interface standard in 3G mobile communications networks that allows higher speeds and more users.
ZIPALIGNED: An archive alignment tool that provides important optimization to APK files. The purpose is to ensure that all uncompressed data starts with a particular alignment relative to the start of the file. Reduces RAM consumption.
Credits
CREDITS
I) @Niku-Droid
II) MY PC
III) MY INTERNET CONNECTION
OH! I missed someone, PM me, I will add credits soon :silly:
[TOOLKIT] UNIFIED ANDROID TOOLKIT - SAMSUNG GALAXY NOTE 10.1 [2014] - Drivers, Root, Recovery + MORE
SUPPORTED MODELS/VARIANTS
WIFI ONLY MODEL [SM-P600] [Supported up to 4.4.2]
3G/WIFI MODEL [SM-P601] [Supported up to 4.4.2]
LTE/WIFI MODEL [SM-P605] [Supported up to 4.4.2]
The Unified Android Toolkit supports 22 Android devices: Galaxy Nexus, Nexus 4, Nexus 5, Nexus 6, Nexus 7 [2012], Nexus 7 [2013], Nexus 9, Nexus 10, Samsung Galaxy S3, Samsung Galaxy S3 Mini, Samsung Galaxy S4, Samsung Galaxy S4 Mini, Samsung Galaxy S5, Samsung Galaxy Note 2, Samsung Galaxy Note 3, Samsung Galaxy Note 4, Samsung Galaxy Note 8.0 [2012], Samsung Galaxy Note 10.1 [2012], Samsung Galaxy Note 10.1 [2014], Samsung Galaxy TabS 8.4 and 10.5 models [2014], Samsung Galaxy Camera (smartcamera) and Samsung Galaxy Gear [smartwatch] on Android Only. The Galaxy Gear Toolkit module will not work if the watch is using the Tizen operating system. There is also a Basic Android Toolkit included which any Android device can use.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.3.4 [9TH JAN 2015]
* 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]
* 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]
* 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
* 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
--------------------------------------------------------------
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: 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.
--------------------------------------------------------------
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. NOTHING IS 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.
PRO USERS CAN ALSO SELECT THE "ANY BUILD" OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD (USEFUL IF YOUR BUILD IS NOT LISTED).
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 Hard Reboot the device
1. Unplug the USB cable.
2. Hold down the 'VOLUME DOWN' + 'POWER' buttons for about 5-15 seconds until the device reboots
How to get into Recovery Mode
1. Unplug the USB cable.
2. Hold down the 'VOLUME UP' + 'POWER' buttons for about 5-15 seconds until you see the Samsung logo on the screen.
3. Release all buttons straight away to enter Recovery Mode.
How to get into Download Mode (For Odin)
1. Unplug the USB cable.
2. Hold down the 'HOME' + 'VOLUME DOWN' + 'POWER' buttons for about 2-15 seconds until a WARNING! Screen appears.
3. Press the 'VOLUME UP' button to enter Download Mode.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by using the Unified Android Toolkit. No warranties of any kind are given.
**UPDATES**
**VIDEOS**
**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.
Thanks for an excellent tool!
I'm having issues with my P600, and I'm pretty sure I've tried everything I can think of, but I'm also sure there is a strong possibility that I'm making a noob mistake. I haven't rooted anything since my Galaxy S3, so I'm incredibly rusty.
Here's what I've done:
32. Samsung Galaxy Note 10.1 (2014)
01. Wifi Only Model
12. 4.4.2
1. Install Device Drivers
This was done successfully with no issues reported by the toolkit.
After this, I know I selected option 3 and I know I installed TWRP 2.8.3.0 and SuperSU 2.45. When I first installed it, I got all successful messages, and I made sure to follow the directions precisely (always read first and then execute). Now my end game here is to install Lollipop on this puppy, which I really cannot wait for. I have three huge issues preventing me from doing that. First, when I launch SuperSU is says something about it cannot find the binary and it cannot install itself (I will update this with the exact message when I get home). The next problem is I attempted to fix that by reinstalling using the toolkit, and whenever my tablet restarts it hits that "android man laying on his back". Then, the third issue is my tablet keeps coming to a message screen saying something along the lines of "installing a custom rom is dangerous and can affect the installed applications" (again, I will update this with the exact message when I get home tonight).
Can anyone suggest a course of action to fix these issues? Even if it involves starting from scratch, I don't mind at all. I just want to be able to install Lollipop already, and I really do not know what I did wrong.
Thanks in advanced, XDA.
- Brandon
BBKoenigsegg said:
I'm having issues with my P600, and I'm pretty sure I've tried everything I can think of, but I'm also sure there is a strong possibility that I'm making a noob mistake. I haven't rooted anything since my Galaxy S3, so I'm incredibly rusty.
Here's what I've done:
32. Samsung Galaxy Note 10.1 (2014)
01. Wifi Only Model
12. 4.4.2
1. Install Device Drivers
This was done successfully with no issues reported by the toolkit.
After this, I know I selected option 3 and I know I installed TWRP 2.8.3.0 and SuperSU 2.45. When I first installed it, I got all successful messages, and I made sure to follow the directions precisely (always read first and then execute). Now my end game here is to install Lollipop on this puppy, which I really cannot wait for. I have three huge issues preventing me from doing that. First, when I launch SuperSU is says something about it cannot find the binary and it cannot install itself (I will update this with the exact message when I get home). The next problem is I attempted to fix that by reinstalling using the toolkit, and whenever my tablet restarts it hits that "android man laying on his back". Then, the third issue is my tablet keeps coming to a message screen saying something along the lines of "installing a custom rom is dangerous and can affect the installed applications" (again, I will update this with the exact message when I get home tonight).
Can anyone suggest a course of action to fix these issues? Even if it involves starting from scratch, I don't mind at all. I just want to be able to install Lollipop already, and I really do not know what I did wrong.
Thanks in advanced, XDA.
- Brandon
Click to expand...
Click to collapse
Which root option did you use to root the device? Using the push method is the simplest.
If the device is booting in the the Stock Recovery screen (Android man on his back) then it looks like the stock recovery restore files are present on your device. In this case choose options 7,3 from the main menu and follow the instructions to stop the stock recovery being restored after a reboot.
Mark.
Update
I have updated the module files (that are downloaded after the Note 10.1 2014 is selected at startup) to fix several config settings, update some Toolkit functions and update TWRP for all variants to 2.8.5.0. The unroot zip file has also been fixed/updated.
Supported models/builds list: http://www.skipsoft.net/?page_id=1203
Download from: http://www.skipsoft.net/?page_id=1069 if you don't already have the Toolkit
If you have already downloaded the new Toolkit and have the v1 module for the Note 10.1 2014 then delete the ConfigGalaxyNote101_2014.exe and the _currentrecoveryversionGalaxyNote101_2014.ini from the tools folder and the Unroot-UninstallBusybox-CwmManager.zip from the root folder. Download the new unroot zip file from http://skipsoft.net/download/fileupd...CwmManager.zip and move it to the root folder, start the Toolkit and select the Galaxy Note 10.1 2014 from the list. The Toolkit will then download new module files.
I will also push an AutoUpdate with the same updates/fixes for Pro users to automate the whole above procedure.
Note: Can someone let me know if the openrecoverscript method via twrp works with twrp 2.8.5.0. I know 2.8 has problems with adb and the openrecovery script method is heavily reliant on this. If it does not work I can revert the recovery back to 2.7.1.1 which has no problems with adb.
Mark.
mskip said:
Update
Supported models/builds list: http://www.skipsoft.net/?page_id=1203
Click to expand...
Click to collapse
This lists the P605, but doesn't state specific carriers. I believe the Verizon is P605V. I am aware the Bootloader is locked, but will it at least Root the P605V?
Any question: do you see any chance to insert a tool into the kit,for enabling otg usb ajd charge at the same time? On Note 3 snapdragon it works with a y adapter,but not on the P605.....
Gesendet von meinem SM-N9005 mit Tapatalk
I've finally decided to root my Note 10. Almost at the end I get this message, "Rebooting device to recovery mode, error: no device/emulators found". What am I doing wrong?
AutoUpdate Available for Samsung Galaxy Note 10.1 (2014) module (Ultimate/Pro Users)
CHANGELOG: [1.5.5]
+Updated FULL support for Android 5.1.1 for ALL models
+Added futureproof support with the new custom support loader option
+no-verity-opt-encrypt zip file [downloads to tools folder after device selection]
+Added latest Magisk zip file [downloads to root folder after device selection]
+Added NEW ULTIMATE FEATURE to add build support for any supported Toolkit device from download link, firmware or boot/recovery images. More Info at skipsoft.net
+Added completely new much improved detection routine for adb/recovery modes and integrated it in Toolkit procedures so automatic detection/rebooting works better|
+Updated Toolkit base for NEW Ultimate feature. Toolkit will update any device module to latest main module version even if an AutoUpdate is not ready yet
+Updated some root functions and removed SuperUser by CWM from root relection
+Added VerifiedBootSigner zip file to use in the Toolkit on newer builds if needed
+Integrated flashing verifiedbootsigner in to root procedures if ever needed
+Toolkit will disable all server pings if they cause any trouble with downloads
+Made some routines work better with more checks to make sure files exist
+Updated Drivers section with new options and adb check tool
+Updated Firmware section with better firmware support. Added Updato.com links
+Improved some Main Menu functions
+Updated app/file versions to latest
+Bug fixes and more I probably forgot to write down
If you find any of this useful PLEASE donate to a device project. You can do it through the Toolkit (after selecting the device at startup) or from the link at https://www.skipsoft.net/?page_id=703 so you get the right code fast and can update to the latest version. You can also go ULTIMATE mode and unlock ALL device modules for the lifetime of the Toolkit. Follow us on twitter at https://twitter.com/mskipxda for posts/updates.
Enjoy.
old thread but still, thanks!
mskip said:
AutoUpdate Available for Samsung Galaxy Note 10.1 (2014) module (Ultimate/Pro Users)
CHANGELOG: [1.5.5]
+Updated FULL support for Android 5.1.1 for ALL models
+Added futureproof support with the new custom support loader option
+no-verity-opt-encrypt zip file [downloads to tools folder after device selection]
+Added latest Magisk zip file [downloads to root folder after device selection]
+Added NEW ULTIMATE FEATURE to add build support for any supported Toolkit device from download link, firmware or boot/recovery images. More Info at skipsoft.net
+Added completely new much improved detection routine for adb/recovery modes and integrated it in Toolkit procedures so automatic detection/rebooting works better|
+Updated Toolkit base for NEW Ultimate feature. Toolkit will update any device module to latest main module version even if an AutoUpdate is not ready yet
+Updated some root functions and removed SuperUser by CWM from root relection
+Added VerifiedBootSigner zip file to use in the Toolkit on newer builds if needed
+Integrated flashing verifiedbootsigner in to root procedures if ever needed
+Toolkit will disable all server pings if they cause any trouble with downloads
+Made some routines work better with more checks to make sure files exist
+Updated Drivers section with new options and adb check tool
+Updated Firmware section with better firmware support. Added Updato.com links
+Improved some Main Menu functions
+Updated app/file versions to latest
+Bug fixes and more I probably forgot to write down
If you find any of this useful PLEASE donate to a device project. You can do it through the Toolkit (after selecting the device at startup) or from the link at https://www.skipsoft.net/?page_id=703 so you get the right code fast and can update to the latest version. You can also go ULTIMATE mode and unlock ALL device modules for the lifetime of the Toolkit. Follow us on twitter at https://twitter.com/mskipxda for posts/updates.
Enjoy.
Click to expand...
Click to collapse
no android 5 support for note 10.1 2014
will this allow you to dump a custom rom on the device? The last samsung I had was like a galaxy 2 or 3 and it was impossible then. I came accross a verizon 10.1 2014 from work and its a nice beater tablet but the UI just sucks compared to my nexus and pixel vanilla android devices.