Stock Deodexed G928TUVS4DPH2 Rom
Read below "BEFORE" downloading, flashing, and posting questions....
...REMEMBER...
I am not responsible for anything that happens to your device, if your SD card goes dead, and everything else!
STOCK DEODEXED G928TUVS4DPH2 ROM FEATURES
Stock
Rooted
Zipaligned
Deodexed
Busybox
SuperSU
KNOX Free
Data/App Support
NOTE #1 - Has All Of The Bloatware Kept In, It Can Be Removed By The User.
NOTE #2 -The Rom Is Running Completely Stock Kernel If You Want A Permissive Kernel You Need To Flash One From The Forum Here
NOTE #3 - I Will Not Be Doing Any Further Modifications On This, It's Just A Stock Deodexed Rom For Users To Try Out And Can Use As Their Daily Driver.
NOTE #4 - Your KNOX Warranty Void Will Counter From 0 To 1.
BUILD.PROP INFO
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MMB29K
ro.build.display.id=MMB29K.G928TUVS4DPH2
ro.build.version.incremental=G928TUVS4DPH2
ro.build.version.sdk=23
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=6.0.1
ro.build.version.security_patch=2016-09-01
ro.build.version.base_os=samsung/zenltetmo/zenltetmo:6.0.1/MMB29K/G928TUVU3DPG1:user/release-keys
ro.build.date=Mon Aug 29 20:25:06 KST 2016
ro.build.date.utc=1472469906
ro.build.type=user
ro.build.user=dpi
ro.build.host=SWDD5006
ro.build.tags=release-keys
ro.build.flavor=zenltetmo-user
ro.product.model=SM-G928T
ro.product.brand=samsung
ro.product.name=zenltetmo
ro.product.device=zenltetmo
ro.product.board=universal7420
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=samsung
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=exynos5
# ro.build.product is obsolete; use ro.product.device
ro.build.product=zenltetmo
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=zenltetmo-user 6.0.1 MMB29K G928TUVS4DPH2 release-keys
ro.build.fingerprint=samsung/zenltetmo/zenltetmo:6.0.1/MMB29K/G928TUVS4DPH2:user/release-keys
ro.build.characteristics=tmo
# Samsung Specific Properties
ro.build.PDA=G928TUVS4DPH2
ro.build.hidden_ver=G928TUVS4DPH2
ro.config.rm_preload_enabled=0
ro.build.changelist=8479853
ro.product_ship=true
ro.chipname=exynos7420
# end build properties
INSTALLATION INSTRUCTIONS
WARNING: Before Flashing Any Rom, Make Sure To Remove All Registered Fingerprints By Going To Settings -> Lock Screen And Security -> Fingerprints Then Press "MORE" Then "Edit" Tick All The Registered Fingerprints And Press "REMOVE"!
TWRP RECOVERY INSTALLATION INSTRUCTIONS (Recommended)
* First Thing You Want To Do Is Reboot Into TWRP Recovery And Backup Your Device! (Boot, Data, System, etc...)
* Download G928TUVS4DPH2 Stock Deodexed Rom.
* Place The Rom Into Your Internal Storage.
* Now Reboot Into TWRP Recovery.
* While In TWRP Recovery, Press "Wipe" And Then "Swipe To Factory Reset".
* Now Press "Back" And Then Press "Advanced Wipe".
* Now Select "Cache", "Dalvik Cache", "Data", And "System" And Then "Swipe To Wipe".
* Now Install The Rom Until Its Finished.
* Reboot Your Device.
* Once Rebooted And In The Setup Wizard, DO NOT Touch For 2 Minutes!
* After 2 Minutes, Reboot The Phone... DONE!
CHANGELOG
★ 9.27.2016
- INITIAL G928TUVS4DPH2 RELEASE
DOWNLOAD LINK
Download Mega
https://mega.nz/#!bBBjmDoL!dghg-ZGy44Ba5dtKSH2_ivOLF4wGrYwiyHg9GtxSf0A
Credits
Samsung=For The Stock Rom
Superr=For The Rom Kitchen And Use
If I Forgot Anyone Please Let Me Know And I Will Add You
STOCK G928TUVS4DPH2 ODIN TAR
STOCK ODIN TAR INSTALLATION INSTRUCTIONS
NOTE #1 - The Stock G928TUVS4DPH2_G928TTMB4DPH2_G928TUVS4DPH2_HOME.tar Inside The Zip File Is Plain Stock So By Flashing This And Going By All The Steps, It Will Trigger Your KNOX Warranty Void From 0 To 1!
NOTE #2 - I Would Highly Recommend That You Backup Your Whole Internal Storage To Your PC Or Cloud Storage Just In Case.
NOTE #3 - Make Sure You Have OEM Unlocking Enabled By Going To Settings -> About Device -> Then Tap "Build Number" Several Times Until You Get A "Developer Mode Has Been Turned On" Message. Now Go To Settings -> Developer Options -> And Enable The "OEM Unlock" Option.
INSTALLATION INSTRUCTIONS
1. First What Your Going To Need To Do Is Download This G928T_MM_ODIN_PACK_LATEST.zip.Zip That I Have Done Myself With All The Files That You Need - https://www.androidfilehost.com/?fid=529141701856462149
2. Extract The Files Inside The Zip Onto Your PC Desktop, You Will Then Have Five Files Inside Of It Including G928TUVS4DPH2_G928TTMB4DPH2_G928TUVS4DPH2_HOME.tar , SR1-SuperSU-v2.78-SR1-20160915123031, Odin3 v3.12.3, SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.0.exe ,twrp-3.0.2-0-zenltetmo.img
3. Now Put Your Phone Into Download Mode By Powering Off Your Device First And Then Hold The Volume Down, Home Button, And Power Button At The Same Time Until You See The Download Mode Warning Screen. Now Press Volume Up Key And Then Insert Your Samsung USB Plug.
4. Now Open Odin3 v3.10.7.exe, Click On "AP", Select "G928TUVS4DPH2_G928TTMB4DPH2_G928TUVS4DPH2_HOME.tar ", And Then Click On "Start". (Also Make Sure Before Doing This Step That You Have Installed The Samsung USB Drivers, If You Haven't, Install It By Opening SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.0.exe.)
5. Wait For 5-10 Minutes For The Stock Odin Tar To Finish Installing.
6. Once Complete Your Phone Will Automatically Reboot And You Will Be On The Latest G928TUVS4DPH2 Android 6.0.1 Marshmallow Stock Update.
7. Next Your Going To Install twrp-3.0.2-0-zenltetmo.img & SR1-SuperSu-V2.78-SR1-20160915123031.
Place SR1-SuperSu-V2.78-SR1-20160915123031 on internal storage.
Now Reboot Back Into Download Mode From Step 3 And Now Open Odin3 v3.10.7.exe, Click On "AP", Select "twrp-3.0.2-0-zenltetmo.img", And Then Click On "Start".
As soon as it starts flashing twrp-3.0.2-0-zenltetmo.img hold volume up and home and wait for it to reboot.
As soon as it reboots hold power button down along with the other 2 you were holding and it will reboot to recovery.
Click on install once in recovery and install SuperSu-V2.78-SR1-20160915123031 and reboot.
8. After This You Are All Done! You Should Now Be On The Latest Update With Root And TWRP Custom Recovery! Now Go To "Settings" And Scroll Down And Press "About Device" And Verify That Your Baseband Version AND Build Number Say G928TUVS4DPH2.
Use As A Base
For those of you who want to use this as a base for building a rom
feel free to as long as you give proper credit i am ok with it
another for good measure
final one thats mine just in case
followed the instructions in post 2, 15 minutes later, rooted. thanks!
Alternate Link ?
Wanted to download the stock deodexed rom but when I clicked the androidfilehost link it says no mirrors available. How can I get the rom?
I will look into it
Sent from my SM-N930F using XDA-Developers mobile app
Will be posting another link
Sent from my SM-N930F using XDA-Developers mobile app
AndroidLifestyle said:
Wanted to download the stock deodexed rom but when I clicked the androidfilehost link it says no mirrors available. How can I get the rom?
Click to expand...
Click to collapse
Link up for differnt download site
Sent from my SM-N930F using XDA-Developers mobile app
allenjthomsen said:
Link up for differnt download site
Sent from my SM-N930F using XDA-Developers mobile app
Click to expand...
Click to collapse
What's the decryption key to your mega link?
I can't download the rom w/o it
AndroidLifestyle said:
I can't download the rom w/o it
Click to expand...
Click to collapse
Link fixed
Sent from my SM-N930F using XDA-Developers mobile app
error 7
Post 2 works perfectly, but when i try to install the deodexed rom, it errors with: "updater process ended with error 7"
filledtwinkie said:
Post 2 works perfectly, but when i try to install the deodexed rom, it errors with: "updater process ended with error 7"
Click to expand...
Click to collapse
I have this same problem now I have no OS installed, please help.
Sorry you need to go under wipe and select format data and type yes but be warned your internal will be wiped then install my deodexed Rom and there should be no error.
I set the deodexed Rom to act like stock Odin which wiped everything sorry I'll make another where you don't have to format data
Sent from my SM-A810F using XDA-Developers mobile app
still getting error 7
allenjthomsen said:
Sorry you need to go under wipe and select format data and type yes but be warned your internal will be wiped then install my deodexed Rom and there should be no error.
I set the deodexed Rom to act like stock Odin which wiped everything sorry I'll make another where you don't have to format data
Sent from my SM-A810F using XDA-Developers mobile app
Click to expand...
Click to collapse
tried formatting data and them transferring the file over and flashing and still nogo
I just did same and flashed my rom and i didnt get no error
Sent from my SM-A810F using XDA-Developers mobile app
I flashed the ROM w/o having to wipe my internal data.
But on a side note, any reason why private mode doesn't work ?
I didnt apply private mode fix
Sent from my SM-A810F using XDA-Developers mobile app
Related
INTRODUCING THE SAMSUNG GALAXY NOTE2 TOOLKIT
GSM (GT-N7100) and LTE (GT-N7105) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1923956
AUSTRALIAN GSM (GT-N7100T) and LTE (GT-N7105T) SUPPORTED. USE GSM THREAD
SPRINT (SPH-L900) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957155
TMOBILE (SGH-T889) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=1957720
MOBILICITY, VIDEOTRON, WIND [SGH-T889V] SUPPORTED. NO THREAD YET. USE TMOBILE THREAD
AT&T (SGH-L317) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052779
BELL, ROGERS, SASKTEL, TELUS [SGH-I317M] SUPPORTED. NO THREAD YET. USE AT&T THREAD
VERIZON ([SCH-I605]) SUPPORTED. THREAD: http://forum.xda-developers.com/showthread.php?t=2052788
US CELLULAR (SCH-R950) SUPPORTED. NO THREAD YET. USE ANY
KOREAN SK TELECOM [SHV-E250S] SUPPORTED. NO THREAD YET. USE ANY
NOTE: If you want a new build added to the Toolkit then download and install, Type 'A' in the Model Selection screen and follow the instructions.
HOW TO VIDEOS ARE ON POST#4 (THANKS TO WWJOSHDEW) MAKE SURE YOU HAVE A LOOK AT THEM AS A VIDEO IS WORTH A THOUSAND WORDS
FUNCTIONS OF SAMSUNG GALAXY NOTE2 TOOLKIT V4.1.0 [9TH APRIL 2013]
Install drivers automatically
Backup/Restore a single package or all apps, user data and Internal Storage
Backup your /data/media (virtual SD Card) to your PC for a Full Safe backup of data
Root any public build (different options)
Root with Superuser (ChainsDD) or SuperSU (Chainfire) via CWM (works on ANY build)
[*]Root+busybox+rename recovery restore files via Custom Recovery
[*]Unroot (delete root files and busybox)
[*]Many root/unroot options including adb, recovery and sideload via custom recovery
[*]Perform a FULL NANDROID Backup of your system via adb and save in Custom Recovery format on your PC
[*]Pull /data and /system folders, compress to a .tar file and save to your PC
[*]Auto Update ToolKit to latest push version on startup (donator feature)
[*]Dump selected Phone Partitions, compress to a .zip file with md5 and save to your PC
[*]Install BusyBox binary on phone
[*]Flash Stock Recovery
[*]Flash CWM Recovery (thanks to Clockworkmod Team) or TWRP Recovery (thanks to Team Win)
[*]Rename Recovery Restore files if present
[*]Flash Insecure Boot Image for adb mode
[*]Flash Stock Boot Image back to your phone
[*]Create tar file to flash via Odin (from upto 10 image files) with 1-click process
[*]Download, Extract and Flash Stock Rom (full DETAILED steps) ESSENTIAL FOR WARRANTY RETURNS
[*]Rip cache.img to zip file in CWM format for editing and flashing (thanks to Adam Lange)
[*]Install a single apk or multiple apk's to your phone (being worked on)
[*]Push Files from your PC to your phone
[*]Pull Files from your phone to your PC
[*]Set Files Permissions on your phone
[*]Dump selected LogCat buffers to your PC
[*]Dump BugReport to your PC (if installed)
[*]Help, Information Screen for various tasks
[*]Mods Section to Modify your phone (being worked on)
[*]Reboot Phone options in adb mode
[*]Change background, text colour in ToolKit
[*]Device Information screen which pulls info directly from device
[*]Activate Professional features from within the ToolKit
--------------------------------------------------------------
Mod edit: Download link removed
MD5 Sum for V4.1.0: 37360aabdf3869aad55d12dd2c2b0b07
NOTE: As the ToolKit.exe and ModsSection.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.
IMPORTANT: ONLY FLASH ROMS THAT ARE SPECIFICALLY MADE FOR YOUR PHONES MODEL NUMBER AS FLASHING AN INCORRECT ROM CAN SOFT BRICK YOUR DEVICE!
Credits: ChainsDD for Superuser, Chainfire for SuperSU, Chenglu for modded cwm.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN FREE (PUBLIC) AND DONATE (PROFESSIONAL) VERSIONS?
THE FREE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD POSSIBLY NEED TO MANIPULATE YOUR PHONE. NOTHING IS RESTRICTED. ACTIVATING THE DONATE VERSION WILL ADD THE ABILITY TO CHECK FOR UPDATES VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED TO MY SERVER WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. THIS ALSO MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE VARIANT OR CARRIER SO DONATOR VERSIONS WILL BE UPDATED SOONER. IF YOU ARE NOT ABLE TO, OR DO NOT WANT THE AUTO UPDATE FEATURE THEN ALL UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL DOWNLOAD VERSION AS SOON AS TIME ALLOWS AND THERE ARE ENOUGH UPDATES TO WARRANT IT. DONATORS WILL ALSO HAVE THE QUICK PICKS AND EXTRAS SECTIONS UNLOCKED AND THE 'NAG' SCREEN ON EXIT WILL BE DISABLED. NEW DONATOR FEATURES WILL ALSO BE ADDED TO THE TOOLKIT IN THE FUTURE.
AUTO REPLY LINKS FOR PAYPAL AND GOOGLE CHECKOUT TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
AUTO UPDATES ARE BY FAR THE EASIEST WAY TO KEEP THE TOOLKITS UP TO DATE AS I HAVE LOTS OF OTHER TOOLKITS TO LOOK AFTER. IF ANYONE HAS ANY VIEWS ON THIS PLEASE PM ME OR CONTACT ME AT [email protected]. PLEASE DO NOT POST YOUR VIEWS IN THIS THREAD AS I WANT TO KEEP IT CLEAN FOR USER SUPPORT.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(Changelog at the Bottom of Post#1)
--------------------------------------------------------------
PLEASE READ THE *FAQ* IN POST#2 BEFORE ASKING QUESTIONS
--------------------------------------------------------------
1. INSTALLING GALAXY NOTE2 DRIVERS
The first thing you need to do is to install the drivers. These are needed so that you can communicate with the phone via the PC and perform the tasks that the ToolKit offers.
NOTE: If you have Kies installed then it is advisable to uninstall it first to avoid conflicts.
a. Make sure your phone is booted into Android and the USB cable is unplugged.
b. Select Option 1 in the ToolKit to install the Samsung USB Driver pack. This should install all the neccessary drivers you need.
C. While the drivers are installing make sure that USB Debugging is enabled on your phone via the Settings, Developer options Screen.
d. After the drivers have been installed connect the USB cable and the PC should detect the phone and install the correct drivers. This will also happen when you enter Download Mode and Recovery Mode for the first time.
e. If you want to check the drivers then go to your Control Panel on your PC and open the Device Manager. With the USB cable connected you should see a device listed as 'Samsung Android Phone' or something similar and a driver attached to it.
NOTE: If you are having trouble with your device being detected or the drivers installing correctly then you could try rebooting your phone, using a different usb port and making sure no other drivers are installed on your pc.
--------------------------------------------------------------
2. USING MSKIPS' SAMSUNG GALAXY NOTE2 TOOLKIT
a. Download the Samsung Galaxy Note2 ToolKit package and run to install the ToolKit to your PC. The installation will also create a Shortcut on your desktop for easy access. You have the option to include or exclude the drivers files at installation so if you already have your drivers set up and are just updating the ToolKit then you can untick the drivers if you wish.
b. Once the ToolKit is installed make sure your phone is booted and plugged in via USB cable and double click on the shortcut on your desktop to run it.
c. You will be asked if you want to check for an Update. If you type 'yes' this will download and check the latest version numbers against the versions in the ToolKit. If there is an update available then you will have the option to download and install it (professional feature).
d. You will now be presented with a Model Selection Screen to choose the Model/Build that you are currently on. Type the number that corresponds to your desired selection. For example type '12' for INTERNATIONAL GSM MODEL [GT-N7100] 4.1.1 [Build ALJ1-ALJ3]. If you cannot find the build your device is using then type 'h' to select the HELP option to get more info.
NOTE: If you have a new build that isnt covered by the Toolkit you can also type 'a' in the Model Selection screen to see instructions on how to pull your stock image and send it to [email protected] so support can be added.
e. The Toolkit will now locate and download the boot image pack for your chosen Model. This is a new feature so the Toolkit is not limited to how many Models can be added and it cuts down ALOT on the download size. After the zip file has finished downloading it will be extracted to the correct folders and the files checked to make sure everything is ok.
f. When you enter the Main Menu you will see 'Adb Mode' at the top. If you have installed your drivers correctly then you will see your devices serial number under the text with 'device' next to it. If you see this then your device is connected and you can carry on.
NOTE: If you haven't installed the drivers and don't see a serial number at the top then this is the FIRST thing you want to do so the Toolkit can operate properly.
g. Each option in the ToolKit has full information on what it is and how to use it.
--------------------------------------------------------------
3. FLASHING A ROM, RADIO OR KERNEL VIA CWM RECOVERY
a. Download your chosen Rom, Radio or Kernel from the Development Forum, then make sure your phone is booted up as normal and connect your usb cable so it goes into MTP Mode. Copy the .zip file (DO NOT UNZIP IT FIRST) to the 'Internal Storage' part on your phone. Do not copy it to a Sub Directory as it will be harder to find when flashing it.
b. Enter CWM Recovery (shut down the phone then hold down the 'HOME' + 'VOLUME UP' buttons and press the 'POWER' button for about 5 seconds).
c. Select 'Install zip from sdcard' and select 'choose zip from sdcard' if the file is on Internal Memory.
d. Scroll to your zip file and select. Then select 'Yes' in the list to start flashing.
e. When flashing is finished press the BACK Button to go back until you get to the Main Menu and then select 'reboot system now' to reboot your phone into Android.
--------------------------------------------------------------
4. FLASHING A ROM, RADIO OR KERNEL VIA DOWNLOAD MODE USING ODIN
Odin can be used to flash image files or parts of your phone. You can flash something as simple as a boot image or a complete system. Everything is packed in a tar or tar.md5 file on your PC and flashed via Odin which is a Windows OS program.
a. Make sure you have your tar file stored on your PC.
b. Reboot your phone to Download Mode [shut down your phone, then hold down the Home + Volume DOWN Buttons and press the Power Button for about 2 seconds until a Warning screen appears. Press Volume UP to continue to Download Mode.
c. Connect your phone via usb and the first box at the top under ID:COM should turn blue and have some text in it. If you are using Download Mode on your phone for the first time then you will notice drivers being installed to use it.
d. The site or page you downloaded the file from will usually give you instructions to set Odin but if not you want to load boot/recovery/system files to the PDA location and have 'Auto Reboot' and 'F.Reset Time' ticked and nothing else.
e. Click on 'Start' to start the flash. You can see what is happening in the text box in the lower left.
--------------------------------------------------------------
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.
--------------------------------------------------------------
ChangeLog
ToolKit v4.1.0 (9th April 2013)
+Updated complete Toolkit structure for easier support and faster updates
+Added GT-N7100T and GT-N7105T models to the support list
+Added 4.1.2 support for many models. See screenshot for full list
+Updated CWM and TWRP Recovery to the latest model specific version
+Added TWRP NAND backup/restore procedure to backups section
+Updated SuperSU Root procedure to V1.25
+Updated Samsung usb drivers to 1.5.18.0
+Added more error detection and updated many parts of the Toolkit procedures
+Added Activation option and support procedure for new builds to Model Screen
+Updated Stock firmware download section with new Samsung images
+Adb server is now shut down if you exit from Model Selection screen
+Added more error control Toolkit processes
+Updated mods section
ToolKit v3.0.0 (18th December 2012)
+Rewrote soo many parts its hard to list them all
+Changed the Model Selection screen
+Split up images for all supported models to make them easier to distinguish
+Added support for Verizon, GT-N7105 (lte), AT&T and Korean SK Telecom
+Added new options to Root/Unroot Screen
+Added root+busybox+rename recovery restore files via Custom Recovery
+Added Root/Unroot via Sideload feature in Recovery
+Updated CWM Recovery to 6.0.1.9
+Updated TWRP Recovery to 2.3.2.3 for all available Models
+Updated SuperSU to 0.99
+Added Device Information Screen
+Added instant reply donate link to Toolkit
+Soo many more behind the scene changes
ToolKit v2.0.0 (27th October 2012)
+Added FULL support for Sprint (SPH-L900)
+Added FULL support for TMobile (SGH-T889)
+Added FULL support for US Cellular (SCH-R950)
+Updated SuperSU Root zip file to V0.96
+Updated CWM Recovery to V6.0.1.5
+Added TWRP Recovery V2.3.1.1
+Added option on all Root procedures to root with Superuser (ChainsDD) or SuperSU (Chainfire)
+Added option in ALLINONE Root routine to flash cwm or twrp Recovery
+Improved Root procedure on all builds
+Made some edits for Toolkit stability
+More tweaks
ToolKit v1.0 (7th Oct 2012)
+First version of Samsung Galaxy Note2 ToolKit released
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
**FAQ**
Q. 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 (e.g removing system apps).
From Google:
Android Debug Bridge (adb) is a versatile tool lets you manage the state of an emulator instance or Android-powered device. It is a client-server program that includes three components:
A client, which runs on your development machine. You can invoke a client from a shell by issuing an adb command. Other Android tools such as the ADT plugin and DDMS also create adb clients.
A server, which runs as a background process on your development machine. The server manages communication between the client and the adb daemon running on an emulator or device.
A daemon, which runs as a background process on each emulator or device instance.
----------------------------------------------------------------------------
Q. I flashed CWM but each time I reboot the Stock Recovery is back
There is an auto recovery restore system on Android 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 the Market). Delete the file recovery-from-boot.p from /system. Now when you flash CWM Recovery it will NOT be overwritten after a reboot. You can also use the Toolkit to rename the files if you wish.
----------------------------------------------------------------------------
Q. What is the difference between Nandroid and Titanium backup?
A NANDROID will backup the whole system including boot, system, data and recovery partitions so you can restore a complete rom and all data and settings.
Essentially Titanium Backup is used to backup apps and associated user data. These could be restored AFTER a full wipe and a new Rom had been flashed on your phone.
The other option now which google added into the new adb command list is the adb backup which is in the ToolKit and can do the same job as Titanium Backup but will store the data on your PC rather than on the phone (where it takes up space and could be deleted).
----------------------------------------------------------------------------
Q. When would i perform a nandroid vs a titanium backup?
You would perform a nandroid backup to back up your entire system including boot image and data and system partitions so you can restore your entire system back to that particular point in the future.
You would use Titanium Backup mainly to back up your installed apps and settings so they could be reinstalled easily and quickly on any future roms. You can also choose individual apps to backup or restore on Titanium Backup whereas if you restore your boot partition via CWM Recovery you are stuck with the whole lot.
----------------------------------------------------------------------------
Q. When I try to open the ToolKit I get a box pop up for a split second and then it goes away. My AntiVirus program says the file may be harmful.
The exe files I compiled are not digitally signed with a Microsoft certificate (as they cost money) so certain AntiVirus programs (mainly Norton and AVG Free) will pick it up as potentially harmful when it is not. They pick up ANY file that doesnt contain a purchased Microsoft certificate in the same way. Restore the deleted file and exclude it from further scans and it will be fine.
----------------------------------------------------------------------------
Q. I have Windows 8 and cannot install the drivers
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
When your computer restarts, select ‘Disable driver signature enforcement‘ from the list. You can now load your modified driver. Reboot again once the driver is installed and all will be well.
----------------------------------------------------------------------------
Q. I flashed the Stock Firmware Image. Odin flashes the file successfully and the phone reboots but it stays stuck on the samsung logo
If the firmware tar file does not include a userdata image (which most Samsung firmware do not) then your userdata partition will be left from your previous setup. If this is incompatible with the new firmware because of build or something else then your system will freeze on boot up.
This is easily fixable by holding the Volume UP, Home and Power buttons all at the same time for about 10 seconds until the device reboots to the Stock Recovery screen. Use the Volume Down button to scroll down to 'wipe data/factory reset' and press the Home button to select it. Go down to yes to confirm and your userdata partition will be wiped. Your device should now boot fine.
**RESERVED FOR MANUAL INSTRUCTIONS**
Reserved for how to videos on this incredible toolkit!
http://www.youtube.com/playlist?list=PLwCVKEYxr_z7FBQYT32dbYw_kdSJmSDH2
How To Root
http://www.youtube.com/watch?v=M9zF6x1MURM
How To Flash Stock Recovery
http://www.youtube.com/watch?v=9CL5x84Tu_U
How To Manually Boot to Custom (or Stock) Recovery
http://www.youtube.com/watch?v=9m6Uugh8ps8&hd=1
Sent from my SPH-L710 using Tapatalk 2
Can i unroot with toolkit?.Many thank for awesome work..:good:
thank you! worked like a charm!!!
simplelife said:
Can i unroot with toolkit?.Many thank for awesome work..:good:
Click to expand...
Click to collapse
Yes you can.
Mark.
So does this add to the flash counter?
Tiffany84 said:
So does this add to the flash counter?
Click to expand...
Click to collapse
Flashing any custom firmware (boot, recovery) will add to the flash counter but im sure Chainfire will update his Triangle Away app to include the US variants.
Mark.
simplelife said:
Can i unroot with toolkit?.Many thank for awesome work..:good:
Click to expand...
Click to collapse
mskip said:
Yes you can.
Mark.
Click to expand...
Click to collapse
Just to be certain, I can unroot with this? How? We don't have a stock recovery since there is no stock firmware avail. Can you please clarify? Thanx bud.
GREAT work and thank you for getting this into an easy toolkit form, as many people will be helped out by this!! I was already rooted, as some others were too, but you created a tool that needs a BIG :good:
teshxx said:
Just to be certain, I can unroot with this? How? We don't have a stock recovery since there is no stock firmware avail. Can you please clarify? Thanx bud.
Click to expand...
Click to collapse
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.
Is TWRP supported on the TMo Note II?
mskip said:
Flashing any custom firmware (boot, recovery) will add to the flash counter but im sure Chainfire will update his Triangle Away app to include the US variants.
Click to expand...
Click to collapse
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number
mskip said:
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.
Click to expand...
Click to collapse
Oh ok. I would, but I haven't rooted mine yet. Still deciding if I want to keep my grey one or exchange it for the white lolol. Hopefully, someone who is already rooted will be kind enough to do it for you.
Thanks for your effort and time.
Chainfire said:
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number
Click to expand...
Click to collapse
PM sent w/ link for stock T889 kernel.img. build number is the file name. sorry i can't help with stock recovery.img since i already rooted and flashed CWM recovery.
---------- Post added at 11:43 AM ---------- Previous post was at 11:40 AM ----------
mskip said:
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.
Click to expand...
Click to collapse
hey mark, if u wanna post or PM me instructions i'll get u the mount points.
Chainfire said:
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number
Click to expand...
Click to collapse
So nice to see you here. Thanks for all u do!!
Sent from my SGH-T889 using Tapatalk 2
I am getting issues with both TWRP and CWM. With TWRP, the data partition is unable to mount, making a full wipe a no go. With CWM, data partition can mount...but the external sd can't. Anyone else having these issues, or is it something on my end?
LvDisturbed1 said:
I am getting issues with both TWRP and CWM. With TWRP, the data partition is unable to mount, making a full wipe a no go. With CWM, data partition can mount...but the external sd can't. Anyone else having these issues, or is it something on my end?
Click to expand...
Click to collapse
I can use my extSD with CWM so it's something on your end. I used the toolkit for the N7100 but same stuff...
Chainfire said:
I will, I just need a stock recovery.img ! If you have it, please pass it to me (this goes for all US variants, btw).
I might get it to work as well if somebody can get me the stock kernel. Root first, then from a root shell:
Code:
dd if=/dev/block/mmcblk0p8 of=/data/local/tmp/kernel.img bs=4096
then from normal cmd:
Code:
adb pull /data/local/tmp/kernel.img
And post the kernel.img - should be 8mb
I will also need: Settings -> About device -> Build number
Click to expand...
Click to collapse
I just sent you a pm with the stock recovery.img from my device(T-Mobile Galaxy Note 2). My build number is JRO03C.T889UVALJ1. Hopefully this gives you what you need. Thanks again.
---------- Post added at 03:53 AM ---------- Previous post was at 03:43 AM ----------
mskip said:
Well I keep asking for someone with adb root access to do an adb shell mount and send me the mount points so I can verify the partitions but noone is getting back to me.
If you or anyone else can send me the mount points then please do so asap. The unroot zip file will remove the su and superuser files along with busybox and cwm manager (if present) but it needs the correct system partition value to mount the system and run the script.
Mark.
Click to expand...
Click to collapse
Just sent you a pm with the mount points for the T-Mobile Galaxy Note 2. Thanks for this tool. It's incredible.
INTRODUCING THE SAMSUNG GALAXY NOTE 10.1 TOOLKIT
IMPORTANT: THIS TOOLKIT DEVICE MODULE SUPPORTS 5 DIFFERENT VARIANTS SO MAKE SURE YOU SELECT THE CORRECT MODEL FOR YOUR DEVICE IN THE MODEL SELECTION SCREEN OR INCORRECT BOOT IMAGES WILL BE DOWNLOADED WHICH COULD SOFT BRICK YOUR DEVICE.
SUPPORTED MODELS
GT-N8000 3G/WIFI MODEL
GT-N8005 3G/WIFI MODEL
GT-N8010 WIFI ONLY MODEL
GT-N8013 WIFI ONLY MODEL
GT-N8020 LTE/WIFI MODEL
Click to expand...
Click to collapse
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports a multitude of Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.3.3 [8TH DEC 2014]
* 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 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.
Note: If you cannot get into Recovery by using the buttons then you can reboot to it from the Toolkit 'reboot device' section.
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.2).
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).
This feature will be added to the Toolkit after testing has been completed.
----------------------------------------------------------------------------
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.
**Reserved if needed**
Loved your work for nexus 7 . Great to see you here.
Thanks
thanks so much
what a great tool. Thanks so much for creating it. I will download and explore
aalupatti said:
Loved your work for nexus 7 . Great to see you here.
Thanks
Click to expand...
Click to collapse
justauser said:
what a great tool. Thanks so much for creating it. I will download and explore
Click to expand...
Click to collapse
I need it tested before I can release it. If either of you or anyone else can test, busybox and make a nand backup then I can release it publicly.
Mark.
mskip said:
I need it tested before I can release it. If either of you or anyone else can test, busybox and make a nand backup then I can release it publicly.
Mark.
Click to expand...
Click to collapse
I will let you know this weekend. I am currently on ASOP based rom and will need sometime before I can go back to stock.
On ARHD8.0!
Hmmm...I'm on ARHD8.0 + with KALAGAS Theme.
I'm ready to Test.
Is it OK??
Edit : Back to ARHD 8.0 + STOCK Theme.
just received my N8010 yesterday and was looking for a toolbox, like í did with my N7.
it's completely Stock (see attached screenshot)
I'm willing to test.
Sent from my GT-N8010 using xda app-developers app
Hi,
I Have samsung galaxy note 10.1 GT-N8000. OFFICIAL ROM , ROOT ACCESS , STOCK RECOVERY. BINARY COUNTER ZERO
I AM READY TO TEST
PM me
william84 said:
just received my N8010 yesterday and was looking for a toolbox, like í did with my N7.
it's completely Stock (see attached screenshot)
I'm willing to test.
Sent from my GT-N8010 using xda app-developers app
Click to expand...
Click to collapse
Jaspreet.master7 said:
Hi,
I Have samsung galaxy note 10.1 GT-N8000. OFFICIAL ROM , ROOT ACCESS , STOCK RECOVERY. BINARY COUNTER ZERO
I AM READY TO TEST
PM me
Click to expand...
Click to collapse
Great thanks I will finish building the installation file now and send you both pm's with the link to test ASAP
EDIT: DOWNLOAD LINKS AND INSTRUCTIONS SENT TO YOUR INBOX. PLEASE TEST AS SOON AS POSSIBLE.
Mark.
Excellent! Im very happy to see Mscip working on a tool for galaxy note 10.1 like the for Gnex. I hope we get a release soon.....much much thanks
Sent from my GT-N8000 using xda app-developers app
Hi Mark,
I used your toolbox for the Galaxy Note 2.
My Galaxy Note 10.1 is arriving this evening and I'm willing to test your toolbox!
@mskip: i'm using your Toolkit on my Galaxy Nexus, Galaxy S3 and Galaxy Note 2.
Would be happy to use and test it also on my Galaxy Note 10.1 (N8000)
Greetings
king.larry
Sent from my GT-N8000 using xda premium
king.larry said:
@mskip: i'm using your Toolkit on my Galaxy Nexus, Galaxy S3 and Galaxy Note 2.
Would be happy to use and test it also on my Galaxy Note 10.1 (N8000)
Greetings
king.larry
Sent from my GT-N8000 using xda premium
Click to expand...
Click to collapse
You have too many devices lol. If you (or the above user) can test and give me feedback tonight then please let me know as soon as possible so I can release the Toolkit soon.
Also can someone with a GT-N8010 or N8013 device please install voodoo report (free from google play store) and email the results to [email protected] so I can make sure the partition points are set right. I have the points for the N8000 so do not need it for that.
Mark.
mskip said:
You have too many devices lol. If you (or the above user) can test and give me feedback tonight then please let me know as soon as possible so I can release the Toolkit soon.
Also can someone with a GT-N8010 or N8013 device please install voodoo report (free from google play store) and email the results to [email protected] so I can make sure the partition points are set right. I have the points for the N8000 so do not need it for that.
Mark.
Click to expand...
Click to collapse
Sent u the report from N8013 running Revolt rom - Asop based.
I sent a voodoo report running stock JZO54K.N8013UEUCMB3.
I can test the toolkit on my device if needed.
Sent from my GT-N8013 using XDA Premium HD app
djmasoda said:
I sent a voodoo report running stock JZO54K.N8013UEUCMB3.
I can test the toolkit on my device if needed.
Sent from my GT-N8013 using XDA Premium HD app
Click to expand...
Click to collapse
When is the soonest you can test? I was expecting feedback from testers by now but nothing so I may just have to take it out of beta testing, post the installer and wait for public feedback.
Mark.
TOOLKIT ANNOUNCEMENT!!
TOOLKIT OPENED FOR PUBLIC RELEASE. PLEASE REMEMBER THIS IS THE INITIAL VERSION SO PLEASE GIVE FEEDBACK IF ANYTHING IS TEXTUALLY INCORRECT OR NEEDS FIXING.
DOWNLOAD LINKS AND INFO IN POST#1
MARK.
Can anyone who has used the Toolkit give some feedback pleased. Just if its working as it should or if anything needs fixing.
Mark.
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/
CyanogenMod/CWM is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed.
This is CWM for the fairphone FP1 (first edition, repartitioned as of FP cherry 1.6). As there are no custom roms (yet), this might not be very useful as of now
Do not install on any other device than the fairphone FP1 first edition - repartitioned as of FP cherry 1.6.
Note:
- The recovery has been compiled from Cyanogenmod 11.0
- device tree https://github.com/chrmhoffmann/android_device_fairphone_FP1
Before proceeding please make a complete backup for ALL partitions (especially the recovery with e.g. MTK Droid Root & Tools).
Thxs go to:
- bgcngm/mtk-tools
- the guys who make MTK droid root & tools
- keesj from fairphone and tmp_ who gave us working kernel
What works
- you can adb into the CWM
- backup and restore (boot, data, cache, system)
- install from .zip files not tested but should work
Installation
a) copy the recovery to the device: adb push cwm-fp1-kk.0.1.img /storage/sdcard1
b) adb into device: adb shell
c) flash to recovery: dd if=/storage/sdcard1/cwm-fp1-kk.0.1.img of=/dev/recovery
You could also try to use a tool like mtk mobile uncle tools (not tested by me): https://play.google.com/store/apps/details?id=com.mobileuncle.toolbox
Download:
Changelog:
kk-0.1:
- update to kitkat compliant version 6.0.5.0
- self-compiled kernel
https://goo.im/devs/chrmhoffmann/cm-11.0/fp1/cwm-fp1-kk.0.1.img
md5sum b0081650e0e3677dc0c2f38ad76282e0
Older downloads:
Changelog:
v.0.2:
- rename to FP1 so that original zips should be flashable
v.0.1:
- initial version
Download
http://goo.im/devs/chrmhoffmann/fairphone/fp1/recovery-cwm-FP1-0.2.img
md5sum ba524ae0d59125809d0c08b59e664a65
Older download
http://goo.im/devs/chrmhoffmann/fairphone/fp1/recovery-cwm-fp1-0.1.img
md5sum 78a79f83bb2fc52b5bb6074df04d6892
Very nice!!! Thanks for your hard work! :good:
Atm I don't have access to an FP1 but did anybody tried it already?
Regards,
Asmaron
asmaron said:
Very nice!!! Thanks for your hard work! :good:
Atm I don't have access to an FP1 but did anybody tried it already?
Regards,
Asmaron
Click to expand...
Click to collapse
Ofc we tried ^^ (athought i suppose chrmhoffmann tried first ).
I mean it installs and starts without any noticable issue. Thanks again chrmhoffmann !
Issue when installing zip
MoreThanADev said:
Ofc we tried ^^ (athought i suppose chrmhoffmann tried first ).
I mean it installs and starts without any noticable issue. Thanks again chrmhoffmann !
Click to expand...
Click to collapse
Actually, there seems to be some issue when installing zip. (Or maybe I did not used it the right way ?)
I tried to
install zip -> chose zip from sdcard -> Fairphone_FP1_OS_v1_Recovery_2014-01-04.zip (downloaded from FP website) -> Yes
and it failled with some error message
"assert failed: getprop("ro.product.device") = "FP1" || getprop ("ro.build.product") = "FP1"
Error ... blablabla"
Is this normal that the file default.prop located at the / of the recovery contains different value from the file Fairphone_FP1_OS_v1_Recovery_2014-01-04.zip/system/build.prop downloaded from FP website ?
ie :
/default.prop as beeing seen in recovery
...
ro.product.model=Fairphone FP1
ro.product.brand=Android
ro.product.name=cm_fp1
ro.product.device=fp1
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Fairphone
Fairphone_FP1_OS_v1_Recovery_2014-01-04.zip/system/build.prop
...
ro.product.model=FP1
ro.product.brand=FP
ro.product.name=FP1
ro.product.device=FP1
ro.product.board=FP1
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=FP1
You should be able to reproduce this easely if you own a FairPhone. Still i can provide further log if you wish.
MoreThanADev said:
Actually, there seems to be some issue when installing zip. (Or maybe I did not used it the right way ?)
I tried to
install zip -> chose zip from sdcard -> Fairphone_FP1_OS_v1_Recovery_2014-01-04.zip (downloaded from FP website) -> Yes
and it failled with some error message
"assert failed: getprop("ro.product.device") = "FP1" || getprop ("ro.build.product") = "FP1"
Error ... blablabla"
Is this normal that the file default.prop located at the / of the recovery contains different value from the file Fairphone_FP1_OS_v1_Recovery_2014-01-04.zip/system/build.prop downloaded from FP website ?
ie :
/default.prop as beeing seen in recovery
...
ro.product.model=Fairphone FP1
ro.product.brand=Android
ro.product.name=cm_fp1
ro.product.device=fp1
ro.product.board=
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Fairphone
Fairphone_FP1_OS_v1_Recovery_2014-01-04.zip/system/build.prop
...
ro.product.model=FP1
ro.product.brand=FP
ro.product.name=FP1
ro.product.device=FP1
ro.product.board=FP1
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=FP1
You should be able to reproduce this easely if you own a FairPhone. Still i can provide further log if you wish.
Click to expand...
Click to collapse
Hmmm... You can test the installation by removing that assert from the zip file. It must be somewhere in META-INF/..../upgrade script.
I guess I could change the ro.product.device to FP1 [EDIT: argh that changes directory structures etc...]
Chris
chrmhoffmann said:
Hmmm... You can test the installation by removing that assert from the zip file. It must be somewhere in META-INF/..../upgrade script.
I guess I could change the ro.product.device to FP1 [EDIT: argh that changes directory structures etc...]
Chris
Click to expand...
Click to collapse
Should be fixed now. Update recovery to 0.2. See op.
Chris
FP1U
Does this version work with the new FP1U model with only a different chipset?
Don't think so. Someone who has the new one has to create it (new kernel needed, I think they also have different partitions?).
Chris
Updated version 6.0.5.0. See op.
Chris
CheckItOut said:
Does this version work with the new FP1U model with only a different chipset?
Click to expand...
Click to collapse
I tested the install on FP1U and can confirm it works.
EDIT: I only tested the KitKat install.
is this new recovery compatible with 1.6 FPOS (4.2.2) too? Or do i have to flash it back to the original one after testing?
drcyber said:
is this new recovery compatible with 1.6 FPOS (4.2.2) too? Or do i have to flash it back to the original one after testing?
Click to expand...
Click to collapse
Can confirm: Just flashed the new recovery 6.0.5.0 to 1.6 FPOS (Stock Android 4.2.2), perfectly compatible. Thanks a ton, Chris!
when i do dd if=/storage/sdcard1/cwm-fp1-kk.0.1.img of=/dev/recovery
i always get an error:
Code:
[email protected]:/ $ dd if=/storage/sdcard1/cwm-fp1-kk.0.1.img of=/dev/recovery
dd if=/storage/sdcard1/cwm-fp1-kk.0.1.img of=/dev/recovery
/dev/recovery: cannot open for write: Permission denied
did i forget something?
Before entering the command, enter
Code:
su
to grant terminal superuser access.
now the error is gone but how can i check if the new recovery is installed..
when i boot to recovery it looks like Stock-Recovery..
Code:
[email protected]:/storage/sdcard1 $ su dd if=/storage/sdcard1/cwm-fp1-kk.0.1.img of
=/dev/recovery
d1/cwm-fp1-kk.0.1.img of=/dev/recovery <
drcyber said:
now the error is gone but how can i check if the new recovery is installed..
Click to expand...
Click to collapse
In Terminal, did you get a message confirming successful file transfer?
With Xposed & Gravity Box, I have a modified power button menu, including an option for rebooting to recovery.
My phone then rebooted into CWM recovery. Important: When rebooting from CWM recovery, don't forget to disable stock recovery, as the phone may attempt to return to it - CWM will ask you before shutting down.
Hope this helps!
drcyber said:
Code:
[email protected]:/storage/sdcard1 $ su dd if=/storage/sdcard1/cwm-fp1-kk.0.1.img of
=/dev/recovery
d1/cwm-fp1-kk.0.1.img of=/dev/recovery <
Click to expand...
Click to collapse
su and dd are two separate commands. Either you execute su first to gain root privileges and write your CWM image to /dev/recovery afterwards using dd, or you can use
su -c "single command you want to execute as root"
to, sort of, combine both.
it worked now
thx
Is it possible to update to 1.8 with this recovery?
everytime i tried with FP-Updater after reboot it says that the signature is unknown, and if i try "ok, install" the phone reboots and i still have 1.6
Yeah, not working here either, not even with the original Recovery.img.
Update process completed, but as with you, I'm stuck on AOSP 4.2.2, not updating to AOSP. 4.2.2-11, even though some apps, like the Fairphone updater, are different. Completely messed up my phone, even after reinstalling GApps. I'll ask them to simply provide the image for the updates, and start fresh... Seems to be the only thing one can do.
★Stock Deodexed N910TUVU2EQI2 Rom★
Read below "BEFORE" downloading, flashing, and posting questions....
...REMEMBER...
I am not responsible for anything that happens to your device, if your SD card goes dead, and everything else!
STOCK DEODEXED N910TUVU2EQI2 ROM FEATURES
★ Stock
★ Rooted
★ Zipaligned
★ Deodexed
★ Busybox
★ MagiskSU
★ KNOX Free
★ Lightly Debloated
★ Data/App Support
★ Working Private Mode
★ Wi-Fi Securestorage Fix
★ Screen Overlay Detected Fix
★ External SD Card Read/Write Fix
★ Disabled Signature App Verification
★ Netflix & Google Play Movies Video Streaming Fix
NOTE #1 - Has Some More Bloatware Kept In, It Can Be Removed By The User.
NOTE #2 - I Will Not Be Doing Any Further Modifications On This, It's Just A Stock Deodexed Rom For Users To Try Out And Can Use As Their Daily Driver.
NOTE #3 - Your KNOX Warranty Void Will Counter From 0 To 1.
BUILD.PROP INFO
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MMB29M
ro.build.display.id=MMB29M.N910TUVU2EQI2
ro.build.version.incremental=N910TUVU2EQI2
ro.build.version.sdk=23
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=6.0.1
ro.build.version.security_patch=2017-08-01
ro.build.version.base_os=
ro.build.date=Thu Sep 21 19:11:22 KST 2017
ro.build.date.utc=1505988682
ro.build.type=user
ro.build.user=dpi
ro.build.host=SWHD4419
ro.build.tags=release-keys
ro.build.flavor=trltetmo-user
ro.product.model=SM-N910T
ro.product.brand=samsung
ro.product.name=trltetmo
ro.product.device=trltetmo
ro.product.board=APQ8084
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=samsung
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=apq8084
# ro.build.product is obsolete; use ro.product.device
ro.build.product=trltetmo
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=trltetmo-user 6.0.1 MMB29M N910TUVU2EQI2 release-keys
ro.build.fingerprint=samsung/trltetmo/trltetmo:6.0.1/MMB29M/N910TUVU2EQI2:user/release-keys
ro.build.characteristics=tmo
# Samsung Specific Properties
ro.build.PDA=N910TUVU2EQI2
ro.build.hidden_ver=N910TUVU2EQI2
ro.config.rm_preload_enabled=0
ro.build.changelist=9385989
ro.product_ship=true
ro.build.official.release=true
ro.chipname=APQ8084
# end build properties
INSTALLATION INSTRUCTIONS
WARNING: Before Flashing Any Rom, Make Sure To Remove All Registered Fingerprints By Going To Settings -> Finger Scanner -> Fingerprint manager Then Press The "3 Dot" Menu Then "Select". Now Tick All The Registered Fingerprints Then Press The "Trash" Button And Hit "OK"!
NOTE #1 - Once The Rom Is Installed The First Initial Boot Will Take Long So Be Patient.
TWRP RECOVERY INSTALLATION INSTRUCTIONS (Recommended)
TWRP Recovery Download Link - (Click Here)
* First Thing You Want To Do Is Reboot Into TWRP Recovery And Backup Your Device! (Boot, Data, System, etc...)
* Download The Stock Deodexed Rom.
* Place The Rom Into Your Internal Or MicroSD Card Storage.
* Now Reboot Into TWRP Recovery.
* While In TWRP Recovery, Press "Wipe" And Then "Swipe To Factory Reset".
* Now Press "Back" And Then Press "Advanced Wipe".
* Now Select "Cache", "Dalvik Cache", "Data", And "System" And Then "Swipe To Wipe".
* Now Install The Rom Until Its Finished.
* Reboot Your Device.
* Once Rebooted And In The Setup Wizard, DO NOT Touch For 2 Minutes!
* After 2 Minutes, Reboot The Phone... DONE!
CHANGELOG
★ 10.23.2014
- INITIAL N910TUVU1ANJ7 RELEASE
★ 12.7.2014
- Removed DT (Digital Turbine) Ignite! (No More Bloatware Getting Installed Onto Your Phone Without Your Approval.)
- Updated Stock Deodexed Rom Build To The New N910TUVU1ANK4 Update!
- Updated Some Of The Google Apps To Their Latest Update!
★ 4.30.2015
- Updated Stock Deodexed Rom Build To The New N910TUVU1COD6 Update!
- Updated Some Of The Google Apps To Their Latest Update!
★ 11.21.2017
- Updated Stock Deodexed Rom Build To The New N910TUVU2EQI2 Update!
- Removed SuperSU And Switched It For Magisk Systemless Root!
DOWNLOAD LINK
Stock Deodexed N910TUVU2EQI2 Rom - https://www.androidfilehost.com/?fid=817906626617948300
MD5 Checksum - 3dcb1886da0edff9df95bb19cb14aa24
★STOCK N910TUVU2EQI2 ODIN TAR★
STOCK ODIN TAR INSTALLATION INSTRUCTIONS
NOTE #1 - The Stock N910TUVU2EQI2_N910TTMB2EQI2_N910TUVU2EQI2_HOME.tar.md5 Inside The Zip File Is Complete Stock Firmware.
NOTE #2 - I Would Highly Recommend That You Backup Your Applications, Data, And Etc To Your PC, Preferred Backup Application, Or Cloud Storage Just In Case.
NOTE #3 - By Flashing The Stock Odin Tar Your Device Will Be Back To Normal Just Like When You First Bought Your Device. It Can Be Used If You Want To Go With A Rootless Approach Or Before You Return/Sell Your Device.
INSTALLATION INSTRUCTIONS
1. First Thing Your Going To Do Is Download This N910T_Stock_Firmware_Odin_Pack.zip That I Have Done Myself With All The Files That You Need - CLICK HERE
2. Extract All The Files From N910T_Stock_Firmware_Odin_Pack.zip Onto Your PC Desktop, You Will Then Have Four Files On Your Desktop Which Will Be N910TUVU2EQI2_N910TTMB2EQI2_N910TUVU2EQI2_HOME.tar.md5, SAMSUNG_USB_Driver_for_Mobile_Phones.exe, Odin3.exe, And Odin3.ini.
3. If You Haven't Installed The Samsung USB Drivers, Just Open The Executable SAMSUNG_USB_Driver_for_Mobile_Phones.exe And Complete The Setup Process. Once Done You Should Now Have The Samsung USB Drivers Installed.
4. Now Put Your Phone Into Download Mode By Powering Off Your Device First And Then Hold The "Volume Down, Home Button, And Power Button" At The Same Time Until You See The Download Mode Warning Screen. Now Press The "Volume Up Button" And Then Insert Your Samsung USB Plug.
5. Now Open Odin3.exe, Click On "AP", Select "N910TUVU2EQI2_N910TTMB2EQI2_N910TUVU2EQI2_HOME.tar.md5", And Then Click On "Start". Wait For A Couple Of Minutes For The Complete Stock N910TUVU2EQI2 Firmware To Finish Installing.
6. Once Complete Your Phone Will Automatically Reboot And Next Is To Wait A Few Minutes On The Bootanimation Screen Until You End Up At The Setup Wizard.
7. When You Get To The Setup Wizard Your All Done You Will Be On The Latest T-Mobile N910TUVU2EQI2 Stock Firmware Update.
NOTE #1 - When Going Back To The Complete Stock Firmware Android Pay, Netflix, Snapchat, Etc Will Now Work Since Root Is No Longer Available.
NOTE #2 - If You Get Stuck At The Bootanimation Screen During Step 5. You Will Need To Put Your Phone Into Recovery Mode By Powering Off Your Device First And Then Hold The "Volume Up, Home Button, And Power Button" At The Same Time Until You See The Stock Recovery Menu. Now Select "Wipe data/factory reset" > "Yes". Then "Reboot system now". Once Done, You Should Now Be Able To Pass The Bootanimation Screen.
CUSTOM RECOVERY AND ROOT INSTALLATION INSTRUCTIONS
NOTE #1 - Once You Install A Custom Recovery And Root Your Device, Your KNOX Warranty Void Will Trigger From 0 To 1.
NOTE #2 - When Rooted Some Applications From The Google Play Store Such As Android Pay, Netflix, Snapchat, Etc May No Longer Work Due To SafetyNet Checks Failing Or Because The Kernel Has Been Tampered With. There Should Be Workarounds To Get Them To Work Even While Being Rooted Just Search The Threads Or The Users Can Post Their Findings For Others To Try Out In Order For Them To Work.
1. To Install A Custom Recovery Such As TWRP, First Thing Your Going To Do Is Download This twrp-3.1.1-0-trlte.img.tar Image File Here - CLICK HERE
2. Now Put Your Phone Into Download Mode By Powering Off Your Device First And Then Hold The "Volume Down, Home Button, And Power Button" At The Same Time Until You See The Download Mode Warning Screen. Now Press The "Volume Up Button" And Then Insert Your Samsung USB Plug.
3. Now Open Odin3.exe, Click On "AP", Select "twrp-3.1.1-0-trlte.img.tar", And Then Click On "Start" To Install TWRP Custom Recovery. While It's Installing Make Sure To Hold The "Volume Up, Home Button, And Power Button" At The Same Time Until Your Phone Automatically Reboots And Then Opens Up The TWRP Recovery Menu. This Is Needed So Your Device Won't Revert To Stock Recovery During A Fail Safe Everytime You Reboot Into Recovery. Once Done Properly Just Reboot Device From TWRP Recovery And You Are All Done!
4. Next Your Going To Root Your Device Using Magisk. Install These Two Files Which Is The Magisk Flashable Zip CLICK HERE And The Magisk Manager Apk File CLICK HERE. You Can Also Go To The Original Thread For More Info Over Here - CLICK HERE. Once Both Files Are Downloaded Place Them Into Your Device's Internal Or MicroSD Card Storage.
5. Now Put Your Phone Into Recovery Mode By Powering Off Your Device First And Then Hold The "Volume Up, Home Button, And Power Button" At The Same Time Until You See The TWRP Recovery Menu. Next Install The Magisk Flashable Zip Magisk-v14.0.zip Then Reboot Your device. Once Back To Your Phone's Homescreen Just Go Into Any File Manager And Then Install The Magisk Manager Apk File Which Should Be Named As MagiskManager-v5.4.0.apk.
6. Once You Have Followed All The Steps You Are All Done! You Should Now Be On The Latest Update With Root And TWRP Custom Recovery! Now Go To Menu, System Settings, And Scroll Down And Press "About Device" And Verify That Your Baseband Version AND Build Number Say N910TUVU2EQI2.
NOTE #1 - Getting a "SECURE CHECK FAIL" error while trying to root your device? Make sure that "Reactivation lock" is turned off in System settings > Security > Reactivation Lock. See if that works. Also use the original Note 4 usb cable that came with your device.
reserving this one as well
one more just in case
Oh Yeah!!!!
Why are you so awesome!!!
whoaaaaa. here we go
Hey, I wasn't aware that ciq was in this phone. How did you find it? What's your method in removing ciq?
Just removing a few apks and libs, or did you get it out at the framework level?
Thank you for this, does this remove the lag everyone is complaining about???
I don't suppose you can use this with a sprint note 4?
I have the lg g3 and it was explained that carrier IQ was needed for initial set up of ROM and then could be removed with a script afterwards. That's not the same here, or was I misunderstood?
Sent from my LG-D851 using Tapatalk
srimay said:
I have the lg g3 and it was explained that carrier IQ was needed for initial set up of ROM and then could be removed with a script afterwards. That's not the same here, or was I misunderstood?
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
Was wondering the same thing since with the new carrier IQ it can't be disabled pre-flashing, not with the main APK tied into the set up anyway.,
Hope to hear from ya jovy before I flash this and start fighting lol
srimay said:
I have the lg g3 and it was explained that carrier IQ was needed for initial set up of ROM and then could be removed with a script afterwards. That's not the same here, or was I misunderstood?
Sent from my LG-D851 using Tapatalk
Click to expand...
Click to collapse
G3 is night day difference from note 4
NOTE 4
Things just got real!
About 15 more minutes and done downloading!
BACARDILIMON said:
G3 is night day difference from note 4
NOTE 4
Click to expand...
Click to collapse
It is but the tmobile iq is still embedded in the same way because of their new recent update. lg g3 maybe night and day but tmobile is well still tmobile
re: U R FAST
jovy23 said:
taking this spot
Click to expand...
Click to collapse
U R FAST!
This is just what I needed with my morning coffee
Thanks!
mgbotoe said:
It is but the tmobile iq is still embedded in the same way because of their new recent update. lg g3 maybe night and day but tmobile is well still tmobile
Click to expand...
Click to collapse
Yes but when u remove it from Samsung it did not break anything
NOTE 4
So it begins
YAY! Thanks Jovy for the first working deodexed ROM base for T-mobile Note 4!
★STOCK DEODEXED N930TUVU1APGC ROM★
Read below "BEFORE" downloading, flashing, and posting questions....
...REMEMBER...
I am not responsible for anything that happens to your device, if your SD card goes dead, and everything else!
STOCK DEODEXED N920TUVU3DPG1 ROM FEATURES
★ Stock
★ Rooted
★ Zipaligned
★ Deodexed
★ Busybox
★ SuperSU
★ KNOX Free
★ Init.d Support
★ Lightly Debloated
★ Data/App Support
★ Shell Script Tweaks
★ Wi-Fi Securestorage Fix
★ Screen Overlay Detected Fix
★ External SD Card Read/Write Fix
NOTE #1 - Has Some More Bloatware Kept In, It Can Be Removed By The User.
NOTE #2 - I Will Not Be Doing Any Further Modifications On This, It's Just A Stock Deodexed Rom For Users To Try Out And Can Use As Their Daily Driver.
NOTE #3 - Your KNOX Warranty Void Will Not Counter From 0 To 1 It Will Still Be Left At 0x0.
INSTALLATION INSTRUCTIONS
WARNING #1: Before Flashing Any Rom, Make Sure To Remove All Registered Fingerprints And Irises By Going To Settings -> Lock Screen And Security -> Fingerprints And Settings -> Lock Screen And Security -> Irises.
WARNING #2: Make Sure To Backup Any Of Your Applications And Data Using Samsung Cloud, Helium App Sync And Backup, Titanium Backup Root, Or FlashFire To Your External MicroSD Card Storage And Not Your Internal Storage.
WARNING #3: Make Sure You Have USB Debugging Enabled By Going To Settings -> General Management -> Then Tap "Build Number" Several Times Until You Get A "Developer Mode Has Been Turned On" Message. Now Go To Settings -> Developer Options -> And Enable The "USB Debugging" Option.
KNOWN ISSUES
- There Is No Secure Folder Knox Has Been Completely Removed And It Doesn't Work While Being Rooted Whenever There Is A Fix I Will Add It Back.
- Nothing Else So Far, You Tell Me.
INSTALLATION INSTRUCTIONS
1. First Thing Your Going To Do Is Download Both graceqltetmo_N930TUVU1APGC_Stock_Deodexed.zip And N930T_Note7_Adb_Rootkit_And_Odin_Pack.zip Files From The Download Link Section Below.
2. Extract All The Files From N930T_Note7_Adb_Rootkit_And_Odin_Pack.zip Onto Your PC Desktop, You Will Then Have Eight Files On Your Desktop Which Will Be MODIFIED_TMO_SPR_N930PVPU1APH3_REV00_ENGBOOT_FIRMWARE.tar.md5, graceqltetmo_N930TUVU1APGC_Stock_Deodexed.img, SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.0.exe, adb-setup-1.4.3.exe, CommandPrompt.bat, Odin3.exe, Odin3.ini, And sun7.
3. If You Haven't Setup ADB On Your PC Yet Or Installed The Samsung USB Drivers, Just Open Both Executables SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.0.exe And adb-setup-1.4.3.exe And Complete Both The Setup Processes. Once Done You Should Now Have A Created ADB Directory Which Should Be Located At C:\adb. Once ADB Is Setup, Place The sun7 Folder And CommandPrompt.bat Inside Your ADB Folder From The New Directory.
4. Now Put Your Phone Into Download Mode By Powering Off Your Device First And Then Hold The "Volume Down+Home+Power Buttons" At The Same Time Until You See The Download Mode Warning Screen. Now Press The "Volume Up Button" And Then Insert Your Samsung USB Plug.
5. Now Open Odin3.exe, Click On "AP", Select "MODIFIED_TMO_SPR_N930PVPU1APH3_REV00_ENGBOOT_FIRMWARE.tar.md5", And Then Click On "Start". Wait For A Couple Of Minutes For The Modified N930PVPU1APH3 Engboot Firmware To Finish Installing.
6. Once Complete Your Phone Will Automatically Reboot Into Recovery Mode Where You Will See An Updating + Erasing Screen. Wait A Few Seconds So It Can Do It's Thing And Your Device Will Automatically Reboot Again. Next Is To Wait Patiently For Almost 20 Minutes On The Samsung Bootanimation Screen Until You End Up At The Setup Wizard.
7. While At The Beginning Of The Setup Wizard, Don't Press Anything! Next Thing Your Going To Do Is Root Your Device. Now Go Into Your ADB Directory First Thing You Might Want To Do Which Is Optional Is Open My Modified root.sh Shell Script That's Inside The sun7 Folder And In The Bloatware Section You Can Remove Any Of The Hashtags "#" To Remove Certain Applications That I Have Left Not To Be Removed By Default. Make Sure To Check Out The Information I Have Left Inside Of The Shell Script For The Users. Once Your Done With That Save Your Edits And Now Open The CommandPrompt.bat That You Have Placed In Your ADB Directory And Copy And Paste The Following Commands That You See Below One By One To Get Your Device Rooted.
Code:
adb push sun7 /data/local/tmp/su
adb shell chmod 0777 /data/local/tmp/su/*
adb shell
cd /data/local/tmp/su
su
./root.sh
After The Last Command You Need To Wait A Couple Of Seconds And Your Device Will Automatically Reboot. If It Gets Stuck During The Package Installation Process You Will Need To Go To Your Device And Press On "Accept" From The "Allow Google To Regularly Check Device Activity" Dialog Message. Once Rebooted Now Skip Everything From The Setup Wizard Until You Reach The TouchWiz Homescreen.
8. Next Place graceqltetmo_N930TUVU1APGC_Stock_Deodexed.zip Into Your Phone's Internal Or MicroSD Card Storage Until The File Transfer Completes. Now Open The FlashFire App From The App Drawer And Give It Root Privileges. Now In The Actions Menu Press The "+" Button Then "Flash ZIP or OTA". From Your Internal Or MicroSD Card Storage Find And Choose graceqltetmo_N930TUVU1APGC_Stock_Deodexed.zip And When In The Options Menu Make Sure Only "Mount /system read/write" Is Ticked And Then From The Top Right Corner Press The "Check Mark" Button. Now Scroll To The Bottom And Press "FLASH" And Hit "OK".
9. Now Your Phone Will Automatically Reboot And Then FlashFire Will Install The Rom. Once It's Done Installing Your Device Will Reboot Again, Now You Will End Up With A Black Boot Screen With No LED Indicator Light. Next Is To Wait Patiently For Almost 20 Minutes On This Black Boot Screen Until You End Up At The Setup Wizard. While At The Beginning Of The Setup Wizard, Don't Press Anything! Now Repeat "Step 7" To Root Your Device Again. Once Rebooted You Are All Done Your Device Is Now Rooted Again And You Can Now Restore Any Of Your Applications And Data And You Don't Need To Install Busybox Since My Modified su.img Has Already Got It Placed Inside The Image File And Extracts It To su/xbin. Also My Modified root.sh Shell Script Will Add More Tweaks To The Rom Adding Init.d Support, Setting Kernel To Permissive, And Disabling Dynamic Voltage Frequency Scaling!
Note #1 - Turn Off Automatic Updates For SuperSU In The Google Play Store Because Whenever There's A New Version For It And If You Update It, Root Will Break.
Note #2 - If Your Going To Use S-Health Don't Allow Google Play Store Or The Galaxy Apps Store To Update It Because The Latest Version Of The Application Checks For Root And Breaks The App. If It Gets Updated, Just Remove Any Traces Of It From system/priv-app/SHealth4 And data/app/com.sec.android.app.shealth-1 And Then Install The S-Health App From The Link Provided - Click Here
CHANGELOG
★ 9.14.2016
- INITIAL N930TUVU1APGC RELEASE
★ 9.17.2016
- There Will Be No More MicroSD Card Only Method! (You Can Now Install The Rom From Both The Internal Or MicroSD Card Storage.)
- Modified The Root Shell Script So It Will Now Install Chainfire's FlashFire App To Make Things Easier For The Users!
- Did Some Minor Renaming Changes And Fixes To The Root Shell Script!
- Root Shell Script Will Now Remove Leftover Facebook Installer Data!
- Updated SuperSU To v2.78 SR1!
CREDITS AND SPECIAL THANKS
chainfire
OvrDriVE
ted77usa
Kamy
galaxyuser88
Surge1223
bajasur
freeza
DOWNLOAD LINK
graceqltetmo_N930TUVU1APGC_Stock_Deodexed.zip - https://www.androidfilehost.com/?fid=24728673521238068
N930T_Note7_Adb_Rootkit_And_Odin_Pack.zip - https://www.androidfilehost.com/?fid=24728673521238069
★STOCK N930TUVU1APGC ODIN TAR★
STOCK ODIN TAR INSTALLATION INSTRUCTIONS
NOTE #1 - The Stock N930TUVU1APGC_N930TTMB1APGC_N930TUVU1APGC_HOME.tar.md5 Inside The Zip File Is Complete Stock Firmware.
NOTE #2 - I Would Highly Recommend That You Backup Your Applications, Data, And Etc To Your PC, Preferred Backup Application, Or Cloud Storage Just In Case.
NOTE #3 - By Flashing The Stock Odin Tar Your Device Will Be Back To Normal Just Like When You First Bought Your Device. It Can Be Used If You Want To Go With A Rootless Approach Or Before You Return/Sell Your Device.
INSTALLATION INSTRUCTIONS
1. First Thing Your Going To Do Is Download This N930T_Stock_Firmware_Odin_Pack.zip That I Have Done Myself With All The Files That You Need - CLICK HERE
2. Extract All The Files From N930T_Stock_Firmware_Odin_Pack.zip Onto Your PC Desktop, You Will Then Have Four Files On Your Desktop Which Will Be N930TUVU1APGC_N930TTMB1APGC_N930TUVU1APGC_HOME.tar.md5, SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.0.exe, Odin3.exe, And Odin3.ini.
3. If You Haven't Installed The Samsung USB Drivers, Just Open The Executable SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.45.0.exe And Complete The Setup Process. Once Done You Should Now Have The Samsung USB Drivers Installed.
4. Now Put Your Phone Into Download Mode By Powering Off Your Device First And Then Hold The "Volume Down+Home+Power Buttons" At The Same Time Until You See The Download Mode Warning Screen. Now Press The "Volume Up Button" And Then Insert Your Samsung USB Plug.
4. Now Open Odin3.exe, Click On "AP", Select "N930TUVU1APGC_N930TTMB1APGC_N930TUVU1APGC_HOME.tar.md5", And Then Click On "Start". Wait For A Couple Of Minutes For The Complete Stock N930TUVU1APGC Firmware To Finish Installing.
5. Once Complete Your Phone Will Automatically Reboot Into Recovery Mode Where You Will See An Updating + Erasing Screen. Wait A Few Seconds So It Can Do It's Thing And Your Device Will Automatically Reboot Again. Next Is To Wait A Few Minutes On The Bootanimation Screen Until You End Up At The Setup Wizard.
6. Once At The Setup Wizard Your All Done You Will Be On The Latest T-Mobile N930TUVU1APGC Stock Firmware Update.
NOTE #1 - When Going Back To The Complete Stock Firmware Samsung Pay, Android Pay, Etc Will Now Work Since Root Is No Longer Available And Your Knox Warranty Void Counter Will Not Get Triggered So Everything Will Be Perfect.
★XPOSED★
XPOSED INSTALLATION INSTRUCTIONS
NOTE #1 - Just A Reminder If Your Going To Install Xposed Which Would Cause Problems With Your Galaxy Note 7 Device Because It Isn't Fully Compatible Don't Post Any Issues That You Are Having While Your On Any Rom Because Xposed Can Break Things And Will Cause Many Problems While It's Installed.
NOTE #2 - Your Device Will Get A Bit Hotter Once It's Installed Just Wait For It To Cool Down Or Power Off Your Device For A Few Minutes And Then Power It Back On.
INSTALLATION INSTRUCTIONS
1. If You Haven't Yet, Download FlashFire From The Google Play Store From Here - https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en
2. Next Download The Xposed Installer Apk From Here - http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
3. Then Download Wanam's Custom Xposed Framework Flashable Zip From The Link Provided - https://www.androidfilehost.com/?fid=24591000424962807
3. Once All Files Are Downloaded Place Them Into Your Phone's Internal Or MicroSD Card Storage Until The File Transfer Completes. Now Open The FlashFire App From The App Drawer And Give It Root Privileges. Now In The Actions Menu Press The "+" Button Then "Flash ZIP or OTA". From Your Internal Or MicroSD Card Storage Find And Choose xposed-v86.1-sdk23-arm64-custom-build-by-wanam-20160904.zip And When In The Options Menu Make Sure Only "Mount /system read/write" Is Ticked And Then From The Top Right Corner Press The "Check Mark" Button. Now Scroll To The Bottom And Press "FLASH" And Hit "OK".
4. Now Your Phone Will Automatically Reboot And Then FlashFire Will Install Wanam's Custom Xposed Framework Flashable Zip. Once It's Done Installing Your Device Will Reboot Again And You Will Need To Wait For Almost 15 Minutes On The Boot Screen Until Your Device Optimizes All The Apps And Then Head Back To The Homescreen.
5. Next Install The Xposed Installer Apk. Once Installed Go Into The App And In "FRAMEWORK" You Should Now See "Xposed framework version 86.1 (custom build by wanam / 20160904 is active" At The Top. If You Do Then Your All Done Now You Can Go Into "DOWNLOAD" To Install Other Xposed Applications (Making Sure They Are Compatible For Marshmallow) And Then Go To "MODULES" To Enable Them Following A Device Reboot To Activate Any Modules. Now Enjoy Working Xposed On Your Rooted Galaxy Note 7 Device!
Note #1 - If You Ever Want To Uninstall Xposed From Your Device Just Download And Install The Xposed Uninstaller Flashable Zip From The Link Here - http://dl-xda.xposed.info/framework/uninstaller/xposed-uninstaller-20160829-arm64.zip Using FlashFire.
★ARYAMOD PREMIUM SOUND CONTROL★
ALL IN ONE APP WITH BEATS AUDIO + VIPER4ANDROID + DOLBY ATMOS
ARYAMOD PREMIUM SOUND CONTROL INSTALLATION INSTRUCTIONS
NOTE #1 - This Is An Advanced Sound Controller For Those Who Like To Have Full Control On Their Phone's Sound.
INSTALLATION INSTRUCTIONS
1. If You Haven't Yet, Download FlashFire From The Google Play Store From Here - https://play.google.com/store/apps/details?id=eu.chainfire.flash&hl=en
2. Next Go To The Link And Then Download The AryaMod Premium Sound Control Flashable Zip - http://forum.xda-developers.com/showpost.php?p=65887220&postcount=798
3. Once Downloaded Place It Into Your Phone's Internal Or MicroSD Card Storage Until The File Transfer Completes. Now Open The FlashFire App From The App Drawer And Give It Root Privileges. Now In The Actions Menu Press The "+" Button Then "Flash ZIP or OTA". From Your Internal Or MicroSD Card Storage Find And Choose AryaMod_Premium_Sound_Control.zip And When In The Options Menu Make Sure Only "Mount /system read/write" Is Ticked And Then From The Top Right Corner Press The "Check Mark" Button. Now Scroll To The Bottom And Press "FLASH" And Hit "OK".
4. Now Your Phone Will Automatically Reboot And Your All Done Now You Will Have Full Control With Your Phone's Sound And You Will Be Able To Enjoy A Much More Better Audio Experience.
reserved 4
This is just the beginning :good:
@jovy23
Amazing work as always Sir[emoji106]
Swyped From TWIST3D_N930T
ted77usa said:
@jovy23
Amazing work as always Sir[emoji106]
Swyped From TWIST3D_N930T
Click to expand...
Click to collapse
@jovy23. Thank you so much for yet another option for our Note 7's!
Can you tell me if this is compatible with xposed?
Is this still stable? I know with the rooting and all that good stuff of the s7 series, root cause quite a few instability issues.
v.v and nice, knox does not get trip! Anyone able to confirm samsung pay still works?
May just give this a spin when I get home...instead of exchanging for s7 edge lmao
edit: ah still based on sprint rooting system i see
mgbotoe said:
Is this still stable? I know with the rooting and all that good stuff of the s7 series, root cause quite a few instability issues.
v.v and nice, knox does not get trip! Anyone able to confirm samsung pay still works?
May just give this a spin when I get home...instead of exchanging for s7 edge lmao
edit: ah still based on sprint rooting system i see
Click to expand...
Click to collapse
Wassup madina..... u have Note 7 too .....haha awesome..... so far pretty stable for me.... but I didn't try @jovy23 deodexed rom yet..... I'm using @OvrDriVE modded stock rom right now
We used sprint userdebug kernel only .... there rest are TMO firmware
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-N920T using Tapatalk
ted77usa said:
Wassup madina..... u have Note 7 too .....haha awesome..... so far pretty stable for me.... but I didn't try @jovy23 deodexed rom yet..... I'm using @OvrDriVE modded stock rom right now
We used sprint userdebug kernel only .... there rest are TMO firmware
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Sweet, will definently gives this a spin
oh and ya! I am definitely here...riding along the ship going down in flame...literally
Will wifi calling still work?
BACARDILIMON said:
Will wifi calling still work?
Click to expand...
Click to collapse
Everything Works Wi-Fi Calling, VOLTE, Even Bluetooth Works I Even Paired One Of My Bluetooth Headsets And Even After A Reboot It Automatically Re-Paired And It's Still Connected No Bugs Whatsoever This Is 100% Deodexed And Not Ran Into One Bug Yet! Even Though I Always Thought Benchmarks Is Bull In My Opinion, I Always Get Above 143,000 Antutu Benchmark Scores!
Oh yeah by the way even though i don't use Xposed, but for testing purposes even Xposed works!
Thanks for this @jovy23 any difference in how the phone reacts as compare to stock, is it more fluid less stutter
Sent from my SM-N930T using XDA-Developers mobile app
mike28 said:
Thanks for this @jovy23 any difference in how the phone reacts as compare to stock, is it more fluid less stutter
Sent from my SM-N930T using XDA-Developers mobile app
Click to expand...
Click to collapse
It's stable, fluid, and super smooth you have to try it for yourself :good:
mgbotoe said:
Is this still stable? I know with the rooting and all that good stuff of the s7 series, root cause quite a few instability issues.
v.v and nice, knox does not get trip! Anyone able to confirm samsung pay still works?
May just give this a spin when I get home...instead of exchanging for s7 edge lmao
edit: ah still based on sprint rooting system i see
Click to expand...
Click to collapse
It's super stable there is no instability issues. Samsung pay will not work because of root im guessing latest samsung pay update should now check for both triggered knox and root even while i was on the odexed firmware root method samsung pay or any of the other paying apps didn't work as well. Flashing the modified tar file will likely flash the sprint firmware but the step after that your installing the tmobile firmware over it so there is no sprint system once your device boots to the setup wizard the only thing that's sprint is the kernel everything else is tmobile based.
jovy23 said:
Oh yeah by the way even though i don't use Xposed, but for testing purposes even Xposed works!
Click to expand...
Click to collapse
Thank you! ?
Sent from my SM-N930T using Tapatalk
carandcar said:
Thank you!
Sent from my SM-N930T using Tapatalk
Click to expand...
Click to collapse
Your welcome. :good:
And by the way just to let everyone know i have found a way to get the rom to install from the internal storage as well! Internal storage root method will be the main method so no more MicroSD card instructions from now on which should be somewhat easier. Once im done testing, I will most likely release the instructions tomorrow or by the weekend.