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.
**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.
**VIDEOS**
excellent
great
great share!
Will this work for rooting the XXALI9?
this is great,
lithium86 said:
Will this work for rooting the XXALI9?
Click to expand...
Click to collapse
It will work on everything upto ALJ7 and beyond.
Final checks and uploading now.
Mark.
The Toolkit will be finished uploading in less than 10 minutes but before I release it publicly I need someone with a GT-I9305 to download and test the root and nand backup features. Please message back in here if you can test it right away as I can't post the link until I know it works properly.
Theres absolutely no risk of any damage as Stock Firmware images exist for your device so if anything doesnt work a simple flash will fix anything.
Mark.
Download link posted in OP.
Thread officially open
If anyone spots any bugs or errors in V6.0.0 please let me know right away as this was a major major rewrite to be able to incorporate I9305 and while I think everything looks fine I may have missed something.
Enjoy.
Mark.
Thanks Mark!
I know it is not your bag but any idea when CWM-Touch may be available for the I9305?
Thanks!
ALI9 ??
The welcome screen does not show the xxxali9 version of the i9305 model.. I surpose that means we have to wait for support for this one as well ??
Edit... didn't see before after posting that this q already has been answered....
[email protected] said:
The welcome screen does not show the xxxali9 version of the i9305 model.. I surpose that means we have to wait for support for this one as well ??
Click to expand...
Click to collapse
Did you read the text on the Model Selection Screen?
FOR ROOTING AND PERFORMING ADB TASKS ON YOUR DEVICE, IF YOU CANNOT FIND THE BUILD
IN YOUR DEVICES SECTION THEN YOU CAN SELECT THE CLOSEST BUILD IN THE LIST (AS LONG
AS IT IS THE SAME ANDROID NUMBER IE. 4.0.4 or 4.1.1).
Click to expand...
Click to collapse
For xxali9 you can choose the ALI5 or the ALJ4 model it doesnt matter they will both work perfectly.
Mark.
mskip said:
Did you read the text on the Model Selection Screen?
For xxali9 you can choose the ALI5 or the ALJ4 model it doesnt matter they will both work perfectly.
Mark.
Click to expand...
Click to collapse
Thanks a lot.. . .Wasn´t sure..
and one thing is for sure.. Rather ask you one time to much, than brick my phone.:angel:
[email protected] said:
Thanks a lot.. . .Wasn´t sure..
and one thing is for sure.. Rather ask you one time to much, than brick my phone.:angel:
Click to expand...
Click to collapse
Correct
Mark.
Just to clarify for I9305 users this toolkit states full support for our device but just be aware it cannot communicate in Qualcomm Diag Mode so backing up EFS on its own is not amicable. Please still use the QPST method to backup NV Items and EFS area of the device.
For anything else then this toolkit is the biz although I write my own tools!
Sent from my GT-I9305 using Tapatalk 2
Thanks for your hard work. I love the Nexus toolkit.
Do you have any plans to expand this G3 toolkit for verizon? It is the d2vzw.
lyriquidperfection said:
Just to clarify for I9305 users this toolkit states full support for our device but just be aware it cannot communicate in Qualcomm Diag Mode so backing up EFS on its own is not amicable. Please still use the QPST method to backup NV Items and EFS area of the device.
For anything else then this toolkit is the biz although I write my own tools!
Sent from my GT-I9305 using Tapatalk 2
Click to expand...
Click to collapse
Do you mean we should use the steps provided in this guide - http://forum.xda-developers.com/showthread.php?t=1946915 before using the Samsung Toolkit?
lithium86 said:
Do you mean we should use the steps provided in this guide - http://forum.xda-developers.com/showthread.php?t=1946915 before using the Samsung Toolkit?
Click to expand...
Click to collapse
Yes and I'm also updating my application to support Qualcomm NV item backup and restore.
Sent from my GT-I9305 using Tapatalk 2
Installing ROMS & Such on the A700/701
For Extreme A700/Android Neophytes
Read It All BEFORE Beginning!
Important Links:
http://forum.xda-developers.com/showthread.php?t=1710755 ← Unlock Bootloader
http://forum.xda-developers.com/showthread.php?t=1791165 ← CWM
http://forum.xda-developers.com/showthread.php?t=1806980 ← CM10 Official Thread
http://forum.xda-developers.com/showthread.php?t=2056964 ← CM10.1 Official Thread
http://forum.xda-developers.com/showthread.php?t=2489708 ← CM10.2 Official Thread
-----http://get.cm/?device=a700 ← CM10 Download
-----http://goo.im/gapps ← Google Apps 4.1.2
http://forum.xda-developers.com/showthread.php?t=1995981 ← AOSP 4.2
http://forum.xda-developers.com/showthread.php?t=1952124 ← iconiaN
http://forum.xda-developers.com/showthread.php?t=1953917 ← Vorbeth’s EasyRoot ← Do This to Root!
http://forum.xda-developers.com/showthread.php?t=2004441 ← Vorbeth’s OC GPU Kernel
http://forum.xda-developers.com/showthread.php?t=1994294 ← CoolOne700
http://forum.xda-developers.com/showthread.php?t=2196266 ← IcOdiv for A701 & A700 based on CyanogenMod 10.1
http://forum.xda-developers.com/showthread.php?t=2219575 ← Evil Alex Purgatory A701
http://forum.xda-developers.com/showthread.php?t=2232411 ← 7comp based on RootBox
http://forum.xda-developers.com/showthread.php?t=2510004 ← Official PAC-man 4.3
Software You Will Use/Need (depending on your root method):
http://support.acer.com/us/en/product/default.aspx?tab=1&modelId=4318 ← Acer USB Drivers
http://developer.android.com/sdk/index.html ← Android SDK
General Information:
First off, this was never made adequately clear for new users (without going through a hundred different posts with hundreds of replies): You will be using the Android SDK and the Windows Command Prompt. When installing the Android SDK, change the directory to something easy like C:\SDK because you will be typing it a lot. The directory in that folder you will be using exclusively for this process is the “platform-tools” directory. This is where adb and fastboot are found.
In addition, you will need to activate ADB Debugging on your tablet. This is found by going to Settings -> Developer Options -> USB Debugging. If this isn’t done, you will get nothing accomplished. Yes, you will need to have your tablet connected through USB to your PC for this to work. I know there are other ways, but I’m writing this with brand new users in mind.
After you’ve got that set, you should go ahead and install the Acer USB Drivers. None of my computers could properly identify the tablet without the drivers. Speaking of quirks, 64GB microsd cards are not generally very friendly with CM10 or CWM even when formatted as Fat32. There are lots of issues I can’t find a workaround to. Consider using a 32GB until the kinks are worked out.
I’m also assuming you are currently running the JB OTA that was pushed worldwide in October 2012. If you are not, then there are a few extra steps when installing IconiaN. Although I compiled the instructions you’re reading, I had nothing to do with anything else. In fact, I didn’t write the codes used to install things through the command prompt….I just compiled all the information into one easy-ish to follow paper.
As usual, if anything in this causes a brick to your tablet, it was your decision. I’m just providing the information that has worked for me (repeatedly). Also, as I’m not a developer, nor am I very handy with editing files or trouble shooting things without actually handling them…….Ask your specific questions directly to those people in charge of the files (pawitp, Vorbeth, Moscow Desire, meier2009, odiv81 and alx5962). They’re the gurus at this..I am a plebe in their shadow.
TL;DR:
Install Android SDK to an easy directory.
Install Acer USB Drivers.
Unlock Your Bootloader: (codes from alx5962)
1. Open a command prompt in windows and navigate to the directory where adb is stored. For the sake of conversation, I’m going to call it “C:\SDK\platform-tools”
2. Plug your tablet into your computer through USB. It should automatically mount because you’ve installed the Acer USB Drivers and didn’t skip that step above. J
3. At the command prompt, enter the following:
Code:
adb reboot-bootloader
-- Allow the device to reboot.
4. Type Code:
Code:
fastboot oem unlock
5. Press the + Volume button to select Unlock then - Volume button to confirm.
6. Restart :
Code:
fastboot reboot-bootloader
----- I had issues on step 6. I tried that, and it rebooted to the bootloader screen. To be on the safe side without hard rebooting (not knowing what was going on), I used the command from Step 3. to reboot. This works for ICS and for JB bootloaders, I confirm I used the above steps on both.-----7. Confirmation of your unlocked status will be seen in the upper left hand corner of the screen.
Install Clockwork Mod Recovery: (all work & codes from pawitp)
Somehow I wasn’t able to install this properly (permanently) until last night (11/09/12). I’m still not entirely sure what I did differently, but I’ll try to document it here. The safest version of CWM is 6.0.1.5. Don’t attempt anything without that version or better. I’ve heard that at this time the touch version isn’t working properly, so be sure to download the original style CWM.
To navigate CWM, the following bit of information will come in handy (especially if you’ve never used it before.) Use the ‘Vol-‘ and ‘Vol+’ buttons to navigate up and down and the ‘Power’ button to select your choice. When you have made a choice it will sometimes give a screen with a ton of “NO” options with only one “YES” option (usually near the bottom). Like any good video game, if you scroll upwards, you can get to the bottom of the screen faster.
1. Place the CWM file you downloaded into your “platform-tools” directory. For the sake of being easy to install, I changed the file name to ‘recovery.img.’
2. Open a command prompt in windows and navigate to the directory where adb is stored. For the sake of conversation, I’m going to call it “C:\SDK\platform-tools”
3. Plug your tablet into your computer through USB.
4. At the command prompt, enter the following:
Code:
fastboot flash recovery recovery.img
5. At this point, you have flashed CWM to the system, BUT you will now need to boot into CWM using :
Code:
fastboot boot recovery.img
The caveat here is that you will need to install either a custom ROM or unencumbered boot.img (kernel) NOW. If you do not install one, flashing CWM was pointless because stock recovery will overwrite it at next reboot. When prompted at reboot (leaving CWM after flashing a ROM) you should choose to keep CWM. This was sort of a miscommunication between the devs and myself, but meier2009 and Moscow Desire cleared it up.
-----Step 5. does NOT install recovery, but forces your system to boot into CWM by pushing the file to your A700 from your ‘platform-tools’ directory.-----
For Future Reference: Enter recovery…(JB):
a. With system powered off, press and hold ‘Power’ and ‘Vol -‘
b. When the system vibrates, release the ‘Power’ button.
c. When the system vibrates a second time, slide your finger from ‘Vol-‘ to ‘Vol+.”
d. When the system vibrates a third time, release that button.
Install pawitp’s CM10.1 OR IcOdiv (A701): (all work & codes from pawitp)
Download the CM10 nightly from the official Cyanogen page and grab the Google Apps file (optional, but you won’t have market without it) listed in the links section. Despite what people say, I have always been unable to install from my external SD card. Instead, I save the zip files to the root/main directory of the internal SD. Save BOTH FILES to internal SD at this time. This has always worked for me, but your mileage may vary. You do this at your own risk, blah, blah, blah.
1. Boot your A700 into CWM using the steps outlined in Step 5. (or 6) from “Install Clockwork Recovery Mod.”
2. Backup your system by navigating to “backup and restore” by using the ‘Vol-‘ and ‘Vol+’ buttons to navigate up and down and the ‘Power’ button to select your choice.
3. At this point, there are two options for you. “backup” and “backup to external_sdcard”…. I have never been able to mount my 64GB Fat32 external_sd in CWM. Try a smaller card if you have one available (I don’t). If you can backup to external, that is probably necessary when coming from stock. I would only backup to internal if you are just updating from an older nightly or previous rom.
4. On the main screen, assuming you’re coming from stock JB or ICS, you will need to do a couple of wipes. I’m positive the first is necessary, and have read in other parts of threads and other forums that the other two wipes are needed, but as they’re both called “cache,” I went ahead and did both (with no ill effects).
Select “wipe data/factory reset”
Select “wipe cache partition”
Select “advanced” and navigate to “wipe dalvik cache”
Go back to the main menu.
5. From the main menu, select “install zip from sdcard”.
6. Select “choose zip from sdcard” and scroll down to the CM10 zip file. Press the ‘Power’ button to select and confirm.
After this has successfully installed, you can choose to install Google Apps or not. I’m assuming you will want to install them because…well…who doesn’t?
7. To install Google Apps, follow Steps 3 and 4 from above, but this time you will choose the gapps zip file instead of the CM10 zip.
8. Reboot Device & Enjoy well sorted Jelly Beans.
Install iconiaN: (all work & codes from Vorbeth)
At the moment this is my favorite. It is one version number (4.1.1) behind CM10 (4.1.2), BUT it is compatible with my SD card, and is similar to the stock experience …. only faster and without the bloatware. The only reason it is second in this guide is because of the alphabet (C before I & P before V).
The latest updates to the ROM bring the latest GAPPS and firmware. meier2009’s 4Way Reboot Mod is also included (and rocks).
1. Boot your A700 into CWM.
2. Follow Steps 2-6 from above if coming from stock JB (or CM10, or CoolOne700) with the exception that you’re installing the iconiaN zip (not CM10, duh). Also, iconiaN comes with v4.2 Google Apps pre-installed, so no need for Step 7.
-----2.a. If coming from stock ICS, you will need to install the Jelly Bean Firmware (Found in the Aroma Setup of the ROM)
3. If coming from an older version of iconiaN, you shouldn’t need to do the wipes, but go ahead and do the backup just to be safe.
4. Reboot Device & Enjoy well sorted Jelly Beans.
-----On a side note, I went ahead and installed BusyBox (https://play.google.com/store/apps/details?id=stericson.busybox) not sure if this was necessary, but I am suffering no ill effects from having it running on my tablet. -----
Install Vorbeth's OC GPU Kernel: (all work & codes from Vorbeth)
This is a custom kernel (as of this writing available only for the A700) that overclocks the Tegra 3 from 1.3Ghz to 1.5Ghz. There has been a noted improvement in gaming performance using this kernel.
1. Boot your A700 into CWM.
2. From the main menu, select “install zip from sdcard”.
3. Select “choose zip from sdcard” and scroll down to the iconiaN Kernel zip file. Press the ‘Power’ button to select and confirm.
4. Reboot Device PLAY SOME GAMES! WEE!
Install Vorbeth’s EasyRoot: (all work & codes from Vorbeth)
If for some reason you’re happy with stock and just want a very simple way to ROOT, then this is for you. Using this kernel will cause OTA to stop working (or you will have to edit the updater-script) and remove all the file checks. The latest update has made all previous instructions null, and it is now exceedingly easy to install ROOT on your A700. Awesome! Still, this does require an unlocked bootloader.
1. Download and extract the EasyRoot ZIP on your computer.
2. Locate and double click the file 'easyroot.bat'.
3. Follow all onscreen instructions.
4. Profit.
CoolOne700: (all work & codes from meier2009)
This is the new kid on the block. meier2009 has included three different install options in this ROM including Full (rooted stock), Small (all the Acer bloatware removed), and Custom (Choose what you want.) It’s definitely one to keep an eye on. Custom install is very handy. He’s also got his 4Way Reboot Mod which adds all our favorite reboot/recovery features. Sweet! Also, BusyBox and SuperSU are included on install, so you don’t need to worry about that.
1. Boot your A700 into CWM.
2. Follow Steps 2-6 from CM10 Install if coming from stock JB (or CM10, or iconiaN) with the exception that you’re installing the CoolOne700 zip (not CM10, duh). Also, CoolOne700 comes with Google Apps pre-installed, so no need for Step 7.
-----2. a. If coming from stock ICS, you will need to install the Jelly Bean Firmware (Found in the Aroma Setup of the ROM)
3. If updating from an older version of CoolOne700, you won’t need to do any of the wipes, but it is always a great idea to do the backup.
4. Reboot Device & Enjoy well sorted Jelly Beans.
Code:
6. If upon reboot, you hit the old system recovery, you will need to reflash the recovery.img OR just work around it by doing:
Code:
fastboot boot recovery.img
-----Step 6. does NOT install recovery, but forces your system to boot into CWM by pushing the file to your A700 from your ‘platform-tools’ directory. I had to use this method to install CM10 because I was never able to get CWM to install. Your luck may be different.-----
THAT´s the Trick my Friend !
Install recovery with
Code:
fastboot flash recovery recovery.img
AND THEN
Code:
fastboot boot recovery.img
Install any ROM and if you´re rebooting and asked to FIX Recovery, answer YES, then it will be leaved there !!!
With this way your also able to start CWM Recovery temporary
only use
Code:
fastboot boot recovery.img
then CWM will start, you can flash anything and after that CWM is gone, because the Stock Recovery is always inside the Recovery Partition
Makes sense then how I finally ended up with CWM actually installed on my tablet. Were the original instructions from pawitp mistaken, or just incomplete?
ExtremeRyno said:
Makes sense then how I finally ended up with CWM actually installed on my tablet. Were the original instructions from pawitp mistaken, or just incomplete?
Click to expand...
Click to collapse
Lost in translation...
ROFLMAO
Added more info last night and have now included the AOSP 4.2 to the links. Keepin' this bumped & updated.
Thanks for posting this excellent How To! I used it to install CM10.
I can confirm the backup to external backup functionality does work with a 8 GB MicroSDHC card. One thing you could do to bypass the external vs internal SD card discussion is to use sideloading. I used it to both install CM10 and the Google Apps and it works nicely. Just select Update through sideload in CWM and then enter 'adb sideload <filename>' on the command line and everything works nicely.
Also for the real beginner you could may be suggest backing up all user applications using Titanium Backup in order to easily restore them after flashing a mod.
Bumping thread back near the top. Lots of people got an A700 for the holiday and it seems many of them are bricking or at least screwing things up using outdated methods or strange new forms of CWM from other forums.
Also, thanks for the info, SanjuroE. Appreciated, and I can honestly say I never knew how to do the sideloading thing. I didn't actually realize that was what it was as on my old tablet (three years ago) sideloading was always in reference to installing from the external SD.
This guide was awesome. Many thanks for this.
I flashed CWM 6.0.3.1 via fastboot.
After that I tried fastboot boot recovery.img but it doesn't work.
On the display:
Booting downloaded image.
But nothing happens ??
Can anyone help me ??
schlex2010 said:
I flashed CWM 6.0.3.1 via fastboot.
After that I tried fastboot boot recovery.img but it doesn't work.
On the display:
Booting downloaded image.
But nothing happens ??
Can anyone help me ??
Click to expand...
Click to collapse
Loot at
http://forum.xda-developers.com/showthread.php?t=1791165
Post #166 to end of thread.
cfgh said:
Loot at
http://forum.xda-developers.com/showthread.php?t=1791165
Post #166 to end of thread.
Click to expand...
Click to collapse
Thanks mate!
I tried another recovery.img and than everything went fine!! :good:
USB driver link is not working.
papars said:
USB driver link is not working.
Click to expand...
Click to collapse
Check this : http://forum.xda-developers.com/showpost.php?p=58172023
Many files available, including Drivers
I can't connect my iconia a700 to PC (Windows 10) is say: device not found. Any help?
I install USB Driver, but in Device managers shows Acer Iconia Tab a700 with yellow worming sign.
Driver Issues WIN10
goralpm said:
I can't connect my iconia a700 to PC (Windows 10) is say: device not found. Any help?
I install USB Driver, but in Device managers shows Acer Iconia Tab a700 with yellow worming sign.
Click to expand...
Click to collapse
Hi,
I have the same issue and it took me hours to even find a driver from ACER. But even after the installation I cannot get the tablet to work stable. I installed general MTP drivers which gave me access to the "adb reboot-bootloader" command but during the reboot the tablet gets stuck on the Acer logo screen and does not boot into the bootloader. I have to unplug the tablet and only then I get the white text in the top left corner of the screen saying "starting Fastboot USB download protocol". But that is it. I assume that fastboot would use the Acer drivers to access the tablet but I don't have any for windows 10.
My question: Could somebody post drivers for Windows 10 for the A700/A701?
Thanks
realshadow
realShadow said:
Hi,
... ...
My question: Could somebody post drivers for Windows 10 for the A700/A701?
Thanks
realshadow
Click to expand...
Click to collapse
I had exactly the same problem. The solution was give here: https://forum.xda-developers.com/showthread.php?p=48915118
You don not need Acer driver.
- Wayne
With the help of the ever awesome Team Win, and specifically a developer named Dees Troy we now have a working recovery for the I9505G.
[Update 8/22/2013]: Thanks to ClockworkMod developer gweedo767, the official CWM Recovery for I9505/jfltexx/International GS4 is now fully compatible with I9505G/jgedlte/GS4 GPe. Download either the regular or Touch version here (scroll down to "Samsung Galaxy S4 (i9505)"). Also, official CM 10.x and CM 11 nightlies for I9505/jfltexx are now fully compatible with I9505G/jgedlte, without any modifications.
Here is the guide to get both the recovery and CM 10.x/11 onto the GS4 GPe GT-I9505G:
Assuming you are on a Windows machine.
First we need to install the USB drivers:
Download and install Android SDK tools from here.
Run "SDK Manager.exe" from wherever you installed Android SDK in previous step.
Under "Tools" section select "Android SDK Tools" and "Android SDK Platform-tools". Under "Extras" section select "Google USB Driver."
Click the "Install" button and wait for installation to complete.
Exit the SDK Manager program.
Now unlock the bootloader (according to some people this step may not be necessary):
Boot up device normally, skip setup or do minimal setup - NOTE: you will wipe your phone during this process, so don't go nuts yet on config/installing apps.
Go to Settings --> About Phone
Tap Build Number 7 times, go back to Main Settings Menu and under now shown Developer Options enable USB debugging.
Plug into PC and ensure the phone is recognized.
On the phone accept the footprint signature popup - if it DOESN'T appear unplug/replug USB cable.
Under Command Prompt or Terminal on PC type in "adb devices" and press Enter. Ensure it shows the device and doesn't show "Offline" - if it does repeat steps 4-5.
Under Command Prompt or Terminal type in:
Code:
adb reboot bootloader
and press Enter.
Once in bootloader, on your PC Command Prompt type in:
Code:
fastboot oem unlock
and press Enter. Note that in Linux you will need to run fastboot with elevated privileges, i.e.
Code:
sudo fastboot oem unlock
.
Accept unlock using Volume key, and confirm with Power button - device will reboot possibly a few times, once rebooted and in device you can sign into accounts - REPEAT step 2-3 to re-enable USB debugging.
Now we can get down to flashing a custom recovery:
Un-install all existing Samsung drivers from your PC. This includes Kies program. I can't stress enough how important this step is for avoiding issues with flashing images via Heimdall or Odin.
Download the latest version of Heimdall from here and extract the ZIP to a folder on your hard drive (e.g. C:\Heimdall\ )
Download and install Microsoft Visual C++ 2012 redistributables package from here. These are required to have Heimdall work properly.
Download either the latest TWRP recovery from here, or latest official ClockworkMod Recovery for I9505 here and place the .IMG file into the Heimdall folder.
Shut down your phone, disconnect it from USB, and turn it on by holding Home + Volume Down + Power buttons together. This will start the phone in the Download mode. *NOTE: It is very important to get into the Download mode from a switched off phone. If you are coming from a different custom ROM, do not simply reboot into download mode (via advanced reboot option, or via "adb reboot bootloader" command) as that will cause issues with Heimdall and Odin.
Connect the phone to your computer via USB.
Run zadig.exe included in the "Drivers" sub-directory of Heimdall installation. From the menu chose Options -> List All Devices. From the USB Device list chose "Samsung USB Composite Device", or "MSMnnnn" - basically the S4. Press "Install Driver", click "Yes" to the prompt and if you receive a message about being unable to verify the publisher of the driver click "Install this driver software anyway". Your phone should now be recognized by Heimdall.
Open Windows Command Prompt and navigate to the directory where you extracted Heimdall. Now type in the following command:
Code:
heimdall flash --RECOVERY file-name-of-recovery-image-here.img --no-reboot
and press Enter. This will flash the recovery. Disconnect the USB cable, and hold the Power button until the phone vibrates. Now hold Home + Volume Up + Power to boot into the recovery.
Now we can flash the i9505's CM nightly:
Once in Recovery mode, connect your phone to USB. You may need to once again install the USB drivers. Just point it to \extras\google\usb_driver\ folder and select "Samsung USB Composite Device".
Perform a backup if you wish (highly recommended!)
Back on the computer, download the CM nightly build (10.x or 11) for the i9505/jflte from here.
Download the latest GApps package appropriate for the CM version you downloaded in previous step from here. (CM 11 compatible gapps, especially those working with new ART VM are currently in flux, but someone put together images of most used ones here).
Back on the phone in Recovery mode perform a full wipe (system, data, cache, and dalvik-cache.)
Flash the files in the following order: 1) CM nightly 2) GApps zip 3) Any other ZIPs you usually flash.
Reboot.
At this point your phone should be booting CyanogenMod. Should something go wrong, follow instructions in donovanbrock's thread to flash back to the stock GE firmware.
Older CM 10.1 ROMs for jfltexx used an outdated syntax for MOUNT command that required an edit to the updater-script, as described here. However, latest CM 10.x and all CM 11 nightlies converted to using a new mount syntax that does not need any modifications.
Working:
Root (superuser) without having to flash or install other packages.
Wi-Fi
Cell data (with LTE)
GPS
Bluetooth
NFC
Vibration
A/C and USB charging
Voice calls
Notification lights
All sensors
Both cameras
Physical and capacitive buttons
Google Apps (Gmail, Play Store, etc.)
Wi-Fi Tethering.
Not Working:
IR Blaster - CM doesn't have official support for it yet. Only apps that access IR modules via root methods will work (e.g. IR Universal Remote.) The functionality has changed from Android 4.3 to 4.4, so it will take some time for CM team to get it working properly. It should make it into CM eventually.
Sometimes when you simply reboot the phone, it gets stuck on the Google logo and doesn't proceed to boot into CM. This seems to be a known issue for the GS4 models and CM, which might have been introduced with SELinux commits. Experts think this is due to a race condition during initial boot-up phases, and are working on a fix. For now the work-around is manually ejecting the SD Card, and immediately putting it back in.
Untested:
Wireless display.
HDMI-out
Thanks and acknowledgements:
Team Win for TWRP recovery, especially Dees_Troy for making it work on I9505G.
CloclworkMod team for the CWM recovery, especially gweedo767 for getting it to work on I9505G.
CM Team for the ROM.
@donovanbrock for the flashing back to stock guide.
@NPS_CA for the bootloader unlock instructions.
Google for Android, and JBQ for AOSP.
WinZip
I claim no credit or ownership of any of the above. The pieces were already out there, I just put them together.
All the linked files are here.
Android SDK tools
Project page: http://developer.android.com/sdk/index.html
Direct download (Windows): installer_r23-windows.exe
Heimdall 1.40
Project page: http://www.glassechidna.com.au/products/heimdall/
Direct download (Windows): heimdall-suite-1.4.0-win32.zip
Support files: Microsoft Visual C++ 2012 redistributables.
Official TWRP recovery for I9505G/jgedlte
Project page: http://teamw.in/project/twrp2/192
Direct download: jgedlte.img
Official CWM recovery for I9505/jfltexx (fully compatible with I9505G/jgedlte)
Project page: http://www.clockworkmod.com/rommanager
Direct download Regular version: recovery-clockwork-6.0.4.7-jfltexx.img
Direct download Touch version: recovery-clockwork-touch-6.0.4.7-jfltexx.img
CM 10.x or 11 for the i9505 (jflte)
Download page: jflte nightlies
Latest GApps package for 4.2.x or 4.3.x (CM 10.x)
Project page: http://goo.im/gapps
Direct download for 4.2.x/CM 10.1: gapps-jb-20130812-signed.zip
Direct download for 4.3/CM 10.2: gapps-jb-20130813-signed.zip
Latest GApps images for 4.4.x (CM 11)
XDA-developers link: http://forum.xda-developers.com/showthread.php?t=2012857
Bonus: 4.3 Camera with Gallery that preserves Picasa Albums sync
Downloads: jb-43-camera-gallery-picasa.zip and jb-43-camera-gallery-picasa_lib.zip
Instructions: Flash both these files in Recovery AFTER flashing the ROM and GApps packages.
Excellent tutorial, thank you. Really happy to see some progress on custom ROMs for the 9505G. Hopefully we will have some custom kernels soon too!
Been waiting on the final version of TWRP. Just flashed. Good work guys!!! :good:
donovanbrock said:
Been waiting on the final version of TWRP. Just flashed. Good work guys!!! :good:
Click to expand...
Click to collapse
Well, it's not final until it shows up on http://teamw.in/project/twrp2 but it's close enough.
I keep getting error:
Code:
Installing '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip.md5
Skipping MD5 check: no MD5 file found.
line 1 col 93: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
E:Error executing updater binary in zip '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'
Error flashing zip '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'
Any work need to be done to /META-INF/com/google/android/update-binary
?
Has anybody done a successful restore and backup using TWRP? Also silly questions but will the touchwiz roms work on this phone? I was going to do a backup and attempt flashing different ROMs for 9505 or should I hold off?
Thanks all and very nice work
donovanbrock said:
I keep getting error:
Code:
Installing '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'...
Checking for MD5 file...
I:Cannot find file /sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip.md5
Skipping MD5 check: no MD5 file found.
line 1 col 93: syntax error, unexpected BAD, expecting IF or STRING or '!' or '('
1 parse errors
E:Error executing updater binary in zip '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'
Error flashing zip '/sdcard/cm-10.1-20130719-NIGHTLY-jfltexx.zip'
Any work need to be done to /META-INF/com/google/android/update-binary
?
Click to expand...
Click to collapse
Could be pastebin messed up the formatting of the updater-script. I'll upload from my original source in a minute.
Edit: Done. Try the file attached in this post, and if it works I'll replace in OP.
Chahk said:
Could be pastebin messed up the formatting of the updater-script. I'll upload from my original source in a minute.
Edit: Done. Try the file attached in this post, and if it works I'll replace in OP.
Click to expand...
Click to collapse
Yah buddy.. update your OP. The new files worked flawlessly. :highfive:
Worked for me as well. Very happy to see CM on our GE S4's.
I would like to add this, though: I've performed every step successfully without ever performing a "fastboot oem unlock". In other words, I'm currently running TWRP + CM10.1 without unlocking my bootloader. May be worth noting. Either way, good work everyone.
Thanks for this! Subscribed.
Gave this a try and can't get it working at all and now my phone just keeps booting into recovery.
When I trying wiping it takes forver (which I assume is it timing out) then I get:
E: Failed to Wipe dalvik
E: Unable to mount '/preload
Then the recovery ends with Failed
When I try flashing I just get error flashing:
Unable to mount /preload
Then just says failed.
Anyone have any thoughts? I tried re flashing the recovery... No luck.. Should also mention the recovery is prompting me for a password when I first get into it (which I never set) and I'm just hitting cancel...
Not for nothing guys, But why would anyone buy the GE Galaxy S4 when you can just buy the i9505 or the T Mobile variant which is literally what the GE is with a different bootloader. Its also $100 cheaper than the GE. with the GE you are **** out of luck with running touchwiz roms for now and you have to struggle to get CM 10.1 working when its already here and flawless on other variants..
drdingo21 said:
Gave this a try and can't get it working at all and now my phone just keeps booting into recovery.
When I trying wiping it takes forver (which I assume is it timing out) then I get:
E: Failed to Wipe dalvik
E: Unable to mount '/preload
Then the recovery ends with Failed
When I try flashing I just get error flashing:
Unable to mount /preload
Then just says failed.
Anyone have any thoughts? I tried re flashing the recovery... No luck.. Should also mention the recovery is prompting me for a password when I first get into it (which I never set) and I'm just hitting cancel...
Click to expand...
Click to collapse
Are you using the recovery I linked to?
Also, when modifying the ROM zip, make sure you are not editing the updater-script or build.prop files in an editor that will mangle line endings like Notepad. Try an advanced editor like Notepad++ instead.
Chahk said:
Are you using the recovery I linked to?
Also, when modifying the ROM zip, make sure you are not editing the updater-script or build.prop files in an editor that will mangle line endings like Notepad. Try an advanced editor like Notepad++ instead.
Click to expand...
Click to collapse
Yep! Everything from your op. are you not getting a password prompt?
I also didn't edit the files. I just dropped them into the Zip
drdingo21 said:
Yep! Everything from your op. are you not getting a password prompt?
I also didn't edit the files. I just dropped them into the Zip
Click to expand...
Click to collapse
No, no password prompts here. Can you try re-flashing the recovery via download mode again?
I heard the LTE bands are different for the phone because of the locked radio and modem. Only the GE edition can operate on both US carriers.
Sent from my GT-I9505G using xda premium
Chahk said:
No, no password prompts here. Can you try re-flashing the recovery via download mode again?
Click to expand...
Click to collapse
Alright. New computer with windows JUST installed.
When I flash the recovery and reboot it doesn't boot into recovery right away. It sits on the Teamwin splash (which it did before) but a reboot gets me into recovery. I still get the password prompt. I re downloaded everything in the OP. Is there somewhere else I should try grabbing the recovery?
---------- Post added at 09:46 PM ---------- Previous post was at 09:16 PM ----------
So I fixed my problems.
I've had my phone since they day they were shipped. I just tried the how to above with out any kind of wipe before hand.
I reflashed the stock recovery then did a full wipe and then wiped the cache again to be sure. Reflashed the attached recovery and all is well! I assume there was something making twrp think there was a password.
thanks for the tutorial!
Can your tweaked installer be used in the same way to make other 9505 ROMs and kernels work on the 9505G?
i had to change zadigto libusb0 (v1.2.5.0) from the default WinUSB (v6.1.7600.16385)
then everyting worked
i know have twrp on my i9505G.
btw if you boot the file using fastboot the touchscreen dose not work but once you flash it it works.
The following is an outcome of an initial post I put up in Q&A regarding achieving root on the SM-T235 for the 5.1.1 Stock Rom (and subsequent questions and dialog with other forum members on issues) I have tried to clean up the posts here but am retaining most of them as it shows the issues other users went through (and feedback perhaps useful to some) The TWRP version is key here and it is what was seen as enabling correct flashing of the SU zip to achieve root. So hope this helps!
I used the following firmware today as a demonstration (have tried now all available 5.1.1 firmwares (successfully) except the DBT which does not flash fully for some reason)
https://www.androidfilehost.com/?fid=24269982087020611
which is AUT-T235XXU1BOH7-20151217085736.zip
ROMs are available here
http://forum.xda-developers.com/tab-4/general/links-galaxy-tab-4-official-lollipop-5-t3102844
I took out external sd (so NO EXTERNAL SD..no linkstosd nothing of the sort)
(TO NOTE-I simply took out the external SD and worked with just the internal storage for THIS demonstration to weed out the issue as other members posting on my original thread were not able to achieve the root I was able to get-it is not absolutely necessary and you could have your SU zip and any other files on the external SD however it is a good idea to keep it simple initially)
SO...I went to TWRP
TWRP is the one attached here in this post (from the thread below but may be different as the OP got updated-however the one I have attached works!)
http://forum.xda-developers.com/tab-...a1-sm-t3027059
You will see in this post that has a picture of the previous OP, the file name is what I have
http://forum.xda-developers.com/show...1&postcount=52
anyway, not sure if there are any differences but am using what works for me (the attached file)
So i did the following which may contain extra or unnecessary steps-no harm though in doing them-as I was trying to demonstrate the rooting process relative to issues other forum posters were having
(EDIT-VERIFIED-you could simply start at step 4 below where you go into download mode to flash the rom (but have the SU zip on external SD card unless it is already in the internal sdcard) and also uncheck autoreboot in Odin (do NOT check repartition!) so that once the rom has been flashed you do not have to boot up the rom, but then reset odin, again go to download mode, again uncheck autoreboot, flash TWRP, then go to recovery (do not boot rom), and flash SU zip and then only boot up-thanks frenkie9999999)
Otherwise this is what I did
1) complete wipe data, cache, system, dalvik all 2 times just for good measure
2) format internal sd (note NO external sd card) (no SIM either but that is because I need my phone working during this process and my SIM is on the T705)
3) reboot to download (do NOT install SU by twrp)
4) Used odin 1.85
5) flash the rom above (or the country firmware of your choice)
6) once device boots up do not connect to anything NO google, no wireless nothing
7) just go to settings, enable development and usb debugging (just what I do normally and mock locations) and in security allow for unknown sources, in google settings I uncheck ALL options
8) do not set up anything else
9) connect device to the laptop
10) copied over the beta 2.65 latest chainfire and root explorer apk that I have (to internal storage...see pictures...I do not have anything else in the internal card, and do not have any external card)
Chainfire's SU zip is from (credits to him for his awesome work for many many years now)
http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
credit goes to K94U for this post that helped me achieve root on the T235 (not my original work as such but just listing the steps here as there were no explicit instructions for the T235)
http://forum.xda-developers.com/showpost.php?p=64182938&postcount=15
11) disconnected device from the laptop
12) went to download mode
13) odin 1.85 again and this time the TWRP recovery I have attached
14) did not let it boot up.,,,forced it to recovery by first pressing power, vol down and home to get to the choice of download or continue to reboot...
15) chose continue to reboot
16) immediately switched to power, vol up and home to get to TWRP
17) flashed the SU zip
18) do not install SU as prompted by TWRP
19) let it reboot
20) found SU in the installed apps in launcher
21) opened up SU and checked the options I want
that was it...opened root explorer and sure enough have root
Google may prompt accept. decline check apps...I always decline and then go to google settings and uncheck those pesky secuirty options as well (if not done already)
the TWRP version is important as the one I have attached works for the purpose of flashing the SU zip to get root correctly
here are the screenshots and the TWRP tar
Got xposed working too wanam arm (32) v78.1 sdk22
Sent from my SM-T235 using XDA Free mobile app
@mac231us
Doesnt work for me. Did everything as your thread guides but i still can't get the SU permissions.
Enabling SuperSU gives me the note "There is no SU binary installed[...]"
Any idea what i did wrong?
1. Flashed to 5.1.1 from CM12.1 and didn't boot
2. Flashed TWRP and booted directly to recovery
3. Flashed BETA-SuperSU-v2.62-20151210170034 and reboot
4. Got SuperSU app installed but it don't let me launch it (not installed binaries)
tyktak said:
@mac231us
Doesnt work for me. Did everything as your thread guides but i still can't get the SU permissions.
Enabling SuperSU gives me the note "There is no SU binary installed[...]"
Any idea what i did wrong?
1. Flashed to 5.1.1 from CM12.1 and didn't boot
2. Flashed TWRP and booted directly to recovery
3. Flashed BETA-SuperSU-v2.62-20151210170034 and reboot
4. Got SuperSU app installed but it don't let me launch it (not installed binaries)
Click to expand...
Click to collapse
that is odd..i just did a fresh install..wiped fully formatted...went to download (do NOT install SU as twrp prompts) odin flashed the 5.1.1 (nordic)...in fact this time even rebooted and set up google account..then went back to download...installed twrp again...again rebooted but this time straight to twrp...then installed the latest su 2.62-3...rebooted (again do not check the SU install prompted by TWRP)...and the su app was there..and so was the binary
noticed chainfire now has BETA-SuperSU-v2.64-20151220185127.zip
curious did you do a 5.1.1 odin flash from cm12.1 or a twrp nandroid recovery...just wondering if it makes a difference
twrp is from here
http://forum.xda-developers.com/tab-4/general/sm-t235-lte-rooted-twrp-2-8-alpha1-sm-t3027059
again...am only speaking of the T235 (or T235Y) not any other variant
the 5.1.1 I used is from here
https://www.androidfilehost.com/?fid=24052804347821380
in order to prevent stock recovery from coming up always first go to download step (not actual download) but using the volume down, power and home to get to the choice of download and reboot..then reboot but quickly go to volume up home and power to get to the twrp recovery
@mac231us
Aww, i cant get it working..
Did exactly what you said:
1. Format everything from TWRP (5.1.1 rom)
2. Flash 5.1.1 (nordic)
3. Configure google account
4. Back to download and flash TWRP
5. Back straight from download to recovery
6. Flash 2.62-3 and reboot (didnt checked the SU install prompted by TWRP)
7. When i open SuperSU app i am getting exactly:
There is no SU binary installed, and SuperSU cannot install it. This is a problem!
If you just upgrade to Android 5.0, you need to manually re-root - consult the revelant forums for your device!
Click to expand...
Click to collapse
Btw. i am getting red and blue text when booting - Kernel is not seandroid enforcing.
Galaxy Tab 4 7.0 LTE (SM-T235)
EDIT...also
tyktak said:
@mac231us
Aww, i cant get it working..
Did exactly what you said:
1. Format everything from TWRP (5.1.1 rom)
2. Flash 5.1.1 (nordic)
3. Configure google account
4. Back to download and flash TWRP
5. Back straight from download to recovery
6. Flash 2.62-3 and reboot (didnt checked the SU install prompted by TWRP)
7. When i open SuperSU app i am getting exactly:
Btw. i am getting red and blue text when booting - Kernel is not seandroid enforcing.
Galaxy Tab 4 7.0 LTE (SM-T235)
Click to expand...
Click to collapse
cannot think of anything else at the moment except that am using older version of odin v 1.85 (i too get the red and blue text..the recovery is not default as simply rebooting to recovery takes one to the stock unless doing the 3button to download to recovery process to get to twrp)
try it again w odin 1.85 and maybe go back to the way I 'instructed' the first time (where I did not set up the rom at all and went back to straight to twrp and flashed supersu...formatting internal storage is important but think you are doing that already)
you may want to ask some of the other folks who also got root
though imo there were no explicit instructions but enough for me to go on with..here....
http://forum.xda-developers.com/tab-4/general/sm-t235-lte-rooted-twrp-2-8-alpha1-sm-t3027059/page15
except for K94U's post here which was very informative
http://forum.xda-developers.com/showpost.php?p=64182938&postcount=15
and
http://forum.xda-developers.com/tab...laxy-tab-4-t3264281/post64216314#post64216314
EDIT another thought i may have done this at some point do not recall (but not today for example on this new installation) is to format the internal card using the stock recovery itself after installation of the odin-rom
then do the other steps of twrp etc from download mode again
@mac231us
Giving up and waiting for CM13.
I've did everything exactly how it should be done and SuperSU is showing information about mising SU binary.
Tried every SuperSU zips from Chainfire but effect was the same every time even with fresh flash of nordic rom and recovery. Ive tried cleaning data through stock recovery but it didnt helped.
Thanks for trying.
tyktak said:
@mac231us
Giving up and waiting for CM13.
I've did everything exactly how it should be done and SuperSU is showing information about mising SU binary.
Tried every SuperSU zips from Chainfire but effect was the same every time even with fresh flash of nordic rom and recovery. Ive tried cleaning data through stock recovery but it didnt helped.
Thanks for trying.
Click to expand...
Click to collapse
Apparently some users need these additional steps to fix supersu:
11. - Reboot Tablet, and from you PC extract the originally downloaded SuperSU 2.6x file on you PC, and navigate to the common directory on the extracted folder, and copy the superuser.apk file to your tablet.
12. - Make sure that you have Unknown Sources checked in the Device administration section of security settings so that you can install superuser.apk.
13. - Install superuser.apk
Also, SuperSU 2.64 fixed my kernel enforcing msg on boot...
@K94U
Still the same. I'll try flash KK then LL and try again whole process instead of CM12.1 -> LL.
I will let you know if it helped.
Btw. Chainfire published version 2.65 today
tyktak said:
@K94U
Still the same. I'll try flash KK then LL and try again whole process instead of CM12.1 -> LL.
I will let you know if it helped.
Btw. Chainfire published version 2.65 today
Click to expand...
Click to collapse
another wild guess is put all your supersu zip and apk files onto the internal storage itself
you will boot into the rom (now seeing that it does not matter if you boot into rom and then go back to download, odin the twrp, flash the supersu zip or that from odin rom directly go to download again, twrp odin and then flash supersu zip as both worked for me-not sure if there really is any technical difference)
you will need to boot to rom anyway especially after formatting and in order to put the supersu apk as K94U mentioned onto the device and then go back to download and do the recovery etc steps
after yesterday's fresh install the way of booting into rom, then going back to download etc (so this process has worked 2 ways, 4 times so no fluke understand some little differences may exist) i was doing backups only to find that when i actually went to the sd card no backup was there although i could transfer files back and forth between storage and the sdcard and computer and sdcard...so finally it was the sdcard that was bad...now all is working fine with backups after switching to different sdcard and using the ridgecrop 32formatter
http://www.ridgecrop.demon.co.uk
32bit version
@mac231us
Is that possible there is something wrong with the downloaded rom and it causes the problems?
When i get "upgrading" notice after flashing, bar goes 1/4 and then show "erasing".
I'll download germany 5.1.1 and try again. Totally no idea what's wrong. Maybe Link2SD has broke mine partitions or something.. after flashing SuperSU it didn't created any folders in /system
I've unmounted my sdcard but recovery still shows it as possible to wipe.
EDIT: After flashing Germany 5.1.1 there is still Erasing in 1/4 way of upgrading software..
EDIT2: Tried again with differrent usb cable and its the same.
EDIT3: After flashing SuperSU and reboot, device is starting and there is a samsung logo for a few secs and then there is a second reboot but with sound at samsung logo.
tyktak said:
@mac231us
Is that possible there is something wrong with the downloaded rom and it causes the problems?
When i get "upgrading" notice after flashing, bar goes 1/4 and then show "erasing".
I'll download germany 5.1.1 and try again. Totally no idea what's wrong. Maybe Link2SD has broke mine partitions or something.. after flashing SuperSU it didn't created any folders in /system
I've unmounted my sdcard but recovery still shows it as possible to wipe.
EDIT: After flashing Germany 5.1.1 there is still Erasing in 1/4 way of upgrading software..
EDIT2: Tried again with differrent usb cable and its the same.
EDIT3: After flashing SuperSU and reboot, device is starting and there is a samsung logo for a few secs and then there is a second reboot but with sound at samsung logo.
Click to expand...
Click to collapse
the DBT 5.1.1 has never worked for me (flash failed always) (am in the USA btw not that it makes a difference)
the ones that have worked are (have tried all of them at one time or the other when I was experimenting getting root type control (removing unwanted system apps, deodexing etc by flashing zips to perform certain mods/functions))
do not have any special apps like link2sd...i recommend removing external sdcard altogether and just working w the internal storage for now
LTE SM-T235 XXU1BOH7 AUT Region (Switzerland)
--LTE SM-T235 XXU1BOH7 NEE Region (Nordic Countries)
--LTE SM-T235 XXU1BOH7 SER Region (Russia)
--LTE SM-T235 XXU1BOH7 SKZ Region (Kazakhstan)
tyktak said:
@mac231us
Is that possible there is something wrong with the downloaded rom and it causes the problems?
When i get "upgrading" notice after flashing, bar goes 1/4 and then show "erasing".
I'll download germany 5.1.1 and try again. Totally no idea what's wrong. Maybe Link2SD has broke mine partitions or something.. after flashing SuperSU it didn't created any folders in /system
I've unmounted my sdcard but recovery still shows it as possible to wipe.
EDIT: After flashing Germany 5.1.1 there is still Erasing in 1/4 way of upgrading software..
EDIT2: Tried again with differrent usb cable and its the same.
EDIT3: After flashing SuperSU and reboot, device is starting and there is a samsung logo for a few secs and then there is a second reboot but with sound at samsung logo.
Click to expand...
Click to collapse
Here the same for me. Like Tyktak I ve tried every every step like him but not work for me too.
I
Will do flash, root etc from scratch once more tomorrow taking pictures along the way and post here...maybe by evening U.S time
Sent from my SM-T705 using XDA Free mobile app
deleted
mostly replicated/cleaned up in the OP now
@mac231us
Thanks mate, it worked!
The reason was probably the newer TWRP which was 2.8.7.0 Add this tutorial as new topic in general section of Galaxy Tab 4.
@frenkie9999999
tyktak said:
@mac231us
Thanks mate, it worked!
The reason was probably the newer TWRP which was 2.8.7.0 Add this tutorial as new topic in general section of Galaxy Tab 4.
@frenkie9999999
Click to expand...
Click to collapse
AWESOME!...yes was thinking about the TWRP yesterday so posted it this morning along with the other steps.
have requested moderator to move the thread to the General section.
@mac231us
Don't forget to edit first post so ppl won't have any problems
YesssSSS! Twrp 2.8.1.0 !!!!
Works great!!!
Thanks Mac231us!
Thanks tyktak!
-Flash TWRP 2.8.1.0 recovery with odin3 1.85 (without re-stocking) -dont forget UNCHECK "autoreboot" on odin.
-WIPE CACHE & DALVIK
- Flash SuperSU 2.65
enjoy!
---------- Post added at 11:38 PM ---------- Previous post was at 11:37 PM ----------
thanks mr. Chainfire!!!!!!
without you Android will never be the same
Thanks a lot !
I followed every step and I was successful . Everything worked .
My tablet is rooted again !
In order to keep this thread clean, please use this one to discuss about Development, Support or Software Updates.
ROMs:
To avoid any possible issue, do not forget to backup your NVRAM so that you won't risk to lose your IMEI. How-to: http://www.anythingultimate.in/2015/11/how-to-backup-your-nvram-partition.html
Stock (Android 6.0)
- 20161207: https://cloud.mail.ru/public/2Rhv/g4hNyccdM or http://www.doogee.cc/bbs/viewtopic.php?f=10&t=34
DO NOT USE THE "Format All & Download" OPTION IF YOU CARE ABOUT YOUR IMEI! Choose "Download Only" or "Firmware Upgrade" instead.
Previous Releases:
- 20160920: https://drive.google.com/file/d/0Bziqh7RXsn-DcVhmQ1pHS01FdzQ/view
- 20160920 (OTA Update from 20160819, not Stock ROM): https://mega.nz/#!ENV2GRzS!H-JMxGI0aMqEm0wQOCZBZbj0GnFm73dSdAP64MwJqyA
OTA Update can be flashed only via Local Update feature. (Settings -> About phone -> Wireless Update -> Manual Update)
- 20160819: https://drive.google.com/file/d/0BzpZ7jq52i28RXY5N1M4bmJGN2c
Flash Tool
- SP Flash Tool v5.1628 for Windows & Linux: https://mega.nz/#F!dYUm0TbB!SWeMLb5Wu1NbRzTPQ8-s_A
Recovery:
- TWRP 3.0.2: http://joco1114.synology.me/share/F7Pro/TWRP/
Root:
Rooting Methods (if you are on Stock ROM)
- SuperSU (flashable using TWRP): http://forum.xda-developers.com/apps/supersu
Extras (Root-Only):
Customization
- Xposed Framework: http://forum.xda-developers.com/showthread.php?t=3034811
Useful Third-Party Apps:
Battery Life
- Amplify: https://play.google.com/store/apps/details?id=com.ryansteckler.nlpunbounce&hl=en
- Greenify: https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en
Thank you for this thread, waiting for my own phone. If you need, I can host files as a mirror in 24/7 with 200 mbits up.
Sent from my Nexus 5 using XDA-Developers mobile app
My phone has arrived! It has very nice screen, but the hyped camera is worst than my old Nexus 5 (8MP). Very noisy, and not so detailed. Maybe the next upgrade will solve it.
The problem: is there any idea, how can I access my phone? I have an unknown device in my Device manager, but I cant find driver. Tried MTP and USB device too. Interesting: PTP (Photo transfer) if working!
Thank you!
Edit: Windows 10 driver is not working properly. Have to unisntall it and reinstall MTK USB driver. MTP is working now.
20160819 Stock ROM & OTA Update from 20160819 to 20160920 added to first post
After updating, my 5 GHz WiFi stopped working. (timeout everytime) But 2.4 Ghz is a little faster, more stable.
Any change log?
joco1114 said:
After updating, my 5 GHz WiFi stopped working. (timeout everytime) But 2.4 Ghz is a little faster, more stable.
Any change log?
Click to expand...
Click to collapse
No changelog. My 5.0GHz WiFi works perfectly though.
@joco1114 : have you noticed some battery improvements with the latest OTA update? Here I see huge improvements.
Nope, but the bluetooth connection is better now. And the troubles with WiFi still exist. The SSIDs are vanishing, connection stable, but no internet transmission. I've tried several places with same result. Used Veloxity for better channel selection, but sometimes I got 65/135 Mbps, other 0.1/0.5 only. Or 0/0... The problem mainly appears on 5 GHz network.
Alberto96 said:
@joco1114 : have you noticed some battery improvements with the latest OTA update? Here I see huge improvements.
Click to expand...
Click to collapse
Here's Carliv Touch Recovery, but it's not fully complete yet. Some mounts still don't work, like sdcard, but you still can install root though adb sideload. I'll fix it up later.
goo gl 5h636h
Sorry, can't post links yet.
mars873 said:
Here's Carliv Touch Recovery, but it's not fully complete yet. Some mounts still don't work, like sdcard, but you still can install root though adb sideload. I'll fix it up later.
goo gl 5h636h
Sorry, can't post links yet.
Click to expand...
Click to collapse
Thank you, I appreciate your work.
I'm also facing issues with the touchscreen with any recovery I try to build, there is something we both are doing in the wrong way.
This is the link he can't post: goo.gl/5h636h
How can I install CTR? After that can I install root?
joco1114 said:
How can I install CTR? After that can I install root?
Click to expand...
Click to collapse
Just like TWRP, get the "scatter" file from the Stock ROM package, copy it in a folder (new one, it must be empty) where you put the "recovery.img" file together with the "scatter" file, then open SP Flash Tool, select scatter, press download. Done!
Thank you! I'm very new in this topic, I had a Nexus 5, I used adb/fastboot to flash recovery. MTK (and SP Flash Tool) is new for me, so sorry about my dumb questions.
I installed the img file (succesfully), started the phone with vol-/power, but I got the original recovery menu. Did I miss something?
Alberto96 said:
Just like TWRP, get the "scatter" file from the Stock ROM package, copy it in a folder (new one, it must be empty) where you put the "recovery.img" file together with the "scatter" file, then open SP Flash Tool, select scatter, press download. Done!
Click to expand...
Click to collapse
joco1114 said:
I installed the img file (succesfully), started the phone with vol-/power, but I got the original recovery menu. Did I miss something?
Click to expand...
Click to collapse
Vol + / Power, not Vol - / Power
Yep, Vol+/Power, I miswrote it.
J
Alberto96 said:
Vol + / Power, not Vol - / Power
Click to expand...
Click to collapse
joco1114 said:
Yep, Vol+/Power, I miswrote it.
J
Click to expand...
Click to collapse
Uhm ok, so you might have missed something. After flashing the device with SP Flash Tool, turn it on with Vol +/Power and go into recovery mode. If the device boots to the OS before you get into TWRP, then it will be overwritten losing the work you have done before.
TWRP Recovery by jemmini.
All thanks to him!
Mirror - Google Drive
Scatter file - here (need to unzip)
Drivers, SPFT, SN Writer - here
If I start the phone with vol+/power, I got 3 menu in very small font size. The first is Recovery. After that I got an open android icon (recovery) and "No command." title (or somthing similar). If I press vol+/power for a short time, the original recovery appear. Maybe everything is OK, but I press wrong buttons. There is no CTR. Trying TWRP...
Edit: TWRP is working! Thank you!
joco1114 said:
Edit: TWRP is working! Thank you!
Click to expand...
Click to collapse
U're wellcome )