Related
!!This is ONLY for Elocity A7!!!
This Mod is based on Elocity Stock with additions from Nvidia SDK, to make a better functioning stock rom with google apps.
You can also follow updates on Twitter now: Dexter Picard (DexterPicard) on Twitter or
for the continued support or you can visit my homepage at Dexter's mods
I Thought this demo deserved to be posted with my Mod for ElocityA7
I get some creds here too , thanks!
Installation Instructions:
ALWAYS HAVE CHARGER CONNECTED WHEN UPDATING A FIRMWARE
Download ElocityMod v1.42 patch update
Download ElocityMod v1.41
It will require Wipe/factory reset as well. as reports on the update seems to report some problems if not, so its your own if it does FC alot, if you do not wipe
PATCHES
installs like regular full updates: rename to Update.zip and run recovery.
- v1.xx Adhoc patch here if you need connecting to mobile teetering app, it will not autostart wifi after sleep.
Previous releases
Download ElocityMod v1.3
Download ElocityMod v1.2
Install using recovery menu.
copy the file to the root of your sdcard and rename to Update.zip.
Enter "Recovery menu" by pressing power for 2seconds, release
then hold power button until "hold power 5sec...." appear and wait until it says booting recovery kernel..and release power button.
Press "HOME" button to see menu, use SEARCH/BACK button to navigate.
select "Wipe/factory reset" - press MENU key to activate
then select "apply sdcard:update.zip" - press MENU to activate
after the small install process - press "reboot" to finalize and wait for the upgrade to take place on second screen that appear.
[/INDENT]
ISSUES
- Files manager app does FC too much, use the OI filemanager for local filehandling.
CHANGELOG
v1.42
- added latest 17-04 update from ElocityA7 update.
- Fixed sdcard problem, you can now eject/insert as much as wanted.
alternate patch is now removed.
v1.41
- build.prop (ro.kernel.android.checkjni=false) enables Skype to function (and maybe other apps)
- usb stick support added.
- changed sdcard handler to stock, but with exception it only work until you eject sdcard/usb , and a reboot is only way to remount (or restart vold daemon which is from a shell)
- honeycomb bootanimation added.
- Files app added (for copying network files to tablet) is buggy with pictures handling in folders. (might be removed again)
- VPN (script + vpn settings enabled/added)
- HDMI resolution changer added in settings (480p -> 1080p output available)v1.4
- Based on latest 24-02 update from Elocity.
- Cracked the sdcard issue, and its fully working now..
- Added patched hulu Flashplayer 10.2 (uninstall this one first, if you download it from market)
- New calendar appv1.3
- finally latest Market app included (2.2.7 will be upgraded to 2.2.11 when you enter market the first time)
- Added Gsensor fix, so screen rotation works, if playing games that need sensor like SpeedX or racing games..
- Added DSP audio manager with EQU function (does help increasing volume a little too)
- re-arranged process, so installers do not keep trying to install apps.v1.2
- Updated to latest stock of Feb-04 .
- removed wifi Settings again, solution did not work (im told)
- Fixed Calendar app FC.
- Updated Market to the latest release.
THANKS to all who donated up to now! its appreciated, and shows that people like the extras added...
WARNING: Use this image at your own risk and i take no responsibility if you brick your tablet..
Reserved for future use..
This will be very helpful for a lot people. Great of you to put this together for everyone!
Just curious, what's the advantage of having the superuser app when the device is rooted out of the box?
I look forward to seeing what else can happen with this device, and would be happy to test if needed.
DroidxRage said:
Just curious, what's the advantage of having the superuser app when the device is rooted out of the box?
Click to expand...
Click to collapse
although its already in non-secure mode, the apps that run "su" dont recognise it, so the root app is required together with its "su" command.
and it actually also have the advantage of you being in control of which apps get root access..
although your "adb shell" is in a root shell, the apps running still has non-su rights to the system, otherwise its would be pretty open as well and without much security.
I went ahead and applied version 1.0a over 1.0. I didn't take the time to do a backup so I didn't wipe/factory reset first. Everything went well, but calendar still gets a force close upon launch (not a problem for me, I don't need it). I may go ahead and wipe it and reinstall 1.0a, but I'm very happy with it as is for now.
Thanks again for making this rom! I'll hit that donate button for sure.
Thanks Dexter, tossed a donation your way.
I couldn't get root access back so I'm rerunning the update after a full wipe of data and cache. I will let you know how it goes.
rich_e said:
I went ahead and applied version 1.0a over 1.0. I didn't take the time to do a backup so I didn't wipe/factory reset first. Everything went well, but calendar still gets a force close upon launch (not a problem for me, I don't need it). I may go ahead and wipe it and reinstall 1.0a, but I'm very happy with it as is for now.
Thanks again for making this rom! I'll hit that donate button for sure.
Click to expand...
Click to collapse
rich_e said:
I couldn't get root access back so I'm rerunning the update after a full wipe of data and cache. I will let you know how it goes.
Click to expand...
Click to collapse
I lost root access loading this rom too. It tried to update su but couldn't.
DroidxRage said:
I lost root access loading this rom too. It tried to update su but couldn't.
Click to expand...
Click to collapse
Couldnt install the su zip file it put on my sd either..
I couldn't get SU to update either (placed on SD card as update.zip, but no joy). Just for grins I tried Z4root too, it went through the motions but no root. I tried to use Titanium Backup to install busybox. It downloaded the binaries but nothing changed.
DroidxRage said:
I lost root access loading this rom too. It tried to update su but couldn't.
Click to expand...
Click to collapse
rich_e said:
I couldn't get SU to update either (placed on SD card as update.zip, but no joy). Just for grins I tried Z4root too, it went through the motions but no root. I tried to use Titanium Backup to install busybox. It downloaded the binaries but nothing changed.
Click to expand...
Click to collapse
I cant see what the problem is... dex any ideas?
I may flash the offocial update, reinstall the modified build.prop, and reinstall market.
The was a post somewhere in the BJ's 299 thread about busybox not installing correctly due to differences in the directory structure on this device, which caused loss of root.
rich_e said:
The was a post somewhere in the BJ's 299 thread about busybox not installing correctly due to differences in the directory structure on this device, which caused loss of root.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=10097888&postcount=750
Gonna try that now
DroidxRage said:
http://forum.xda-developers.com/showpost.php?p=10097888&postcount=750
Gonna try that now
Click to expand...
Click to collapse
This didn't work... other than this superuser permissions being messed up everything else works stellar!
If we don't have anything soon, I'll flash back and poke around with the modified build.prop on the official build.
Edit: Reinstalled the official elocity update and got my root back, installed gapps, now updating build.prop. Hopefully this gets me all the market fixes minus that Su thing. Superuser app is available in the market too. Report back soon.
So you're basically just using the build prop settings out of this rom with the factory update? I went back to version 1.0 for now.
rich_e said:
So you're basically just using the build prop settings out of this rom with the factory update? I went back to version 1.0 for now.
Click to expand...
Click to collapse
Yeah pretty much!... did you not have the SU issues with version 1.0? If not I'll just update to that. I can't get Bank of America or Tasker to install even using the build.prop from the ROM, there's something other than the fingerprint in this ROM making the magic happen.
Titanium back up reports root access with V1.0 and I can get the # at the prompt in terminal. Lots of other apps that wouldn't install with the eLocity update install just fine with it too.
im a little confused..
i added the "su" command to the build, it never was there...
i added Superuser.apk as well.. and if you're trying to add those on top , you might corrupt it, and also,
VERY IMPORTANT filesystem has 0 bytes free, so any copying will probably corrupt the su command or other copied files..
Does this rom support ad-hoc wifi tether?
GALAXY NEXUS - SUPPORTS ALL AVAILABLE VERSIONS
SEE SUPPORT LIST FOR PUBLIC/PRO VERSIONS *HERE*
The Unified Android Toolkit brings together all the Nexus and Samsung Toolkits and supports many Nexus and Samsung devices. There is also an option at startup to run a Basic Android Toolkit which any Android device can use to install drivers, make app backups, install apk files, reboot the device into different modes and run a command prompt for manual input.
FUNCTIONS OF UNIFIED ANDROID TOOLKIT V1.4.1 [05th Oct 2015]
* Install correct adb/fastboot drivers automatically on Windows xp/vista/7/8 32bit+64bit
* Backup/Restore a single package or all apps, user data and Internal Storage
* Backup your data from selectable folders [internal or external storage] to your PC for a Full Safe backup of data
* Unlock/Re-Lock your Bootloader [Nexus]
* Root Stock builds
* Various Root options using insecure boot image or custom recovery
* ALLINONE to Unlock, Root, Rename the Restore Files and install busybox [Nexus]
* ALLINONE to flash custom Recovery Root, Rename the Restore Files and install busybox [Samsung]
* [NEW] use SkipRoot boot image to Auto Root device, install Busybox Binaries and rename Recovery Restore files [selected devices]
* Install BusyBox on your device
* Perform a FULL NANDROID Backup of your system (Boot, Cache, Data, Recovery and System) via adb and save in Custom Recovery format on your PC which can be Restored via CWM Recovery [if insecure boot image available]
* Fix extSdCard write permissions from installed apps in Android 4.4+ [Samsung]
* Pull /data and /system folders, compress to a .tar file and save to your PC [if insecure boot image available]
* Dump selected Device Partitions, compress to a .zip file with md5 and save to your PC [if insecure boot image available]
* Extras, Tips and Tricks section
* Auto Update ToolKit to latest available version at startup (professional only feature)
* Program up to 10 Quickpick slots and run them very quickly (professional only feature)
* Mods section to automatically perform certain tasks on your device
* Download Google Stock Image directly to correct ToolKit folder for extracting and flashing [Nexus]
* Check md5 of stock image to make sure downloaded file isn’t corrupted before flashing [Nexus]
* Download Samsung Stock Firmware to PC for extracting and flashing via Odin [Samsung]
* Flash Custom Recovery or Google Stock Image to Device
* Flash any part of a stock Nexus image to device [boot, system, recovery] – Great for fixing broken parts of firmware
* Rename the Recovery Restore File present on some Stock Roms
* Boot into CWM Touch, TWRP, Philz Touch Recovery or Stock Recovery without Flashing it [Nexus]
* Flash Custom Recovery to Device
* Boot [Nexus] or Flash .img Files directly from your PC
* Install a single apk or multiple apk’s to your device
* Push Files from your PC to your device
* Pull Files from your device to your PC
* Disable forced encryption on Nexus6 and Nexus9 devices
* Install Root Checker app by Burrows Apps
* Install Backup/Restore app by MDroid Apps [calls log, sms, contacts]
* Install EFS/Partition Backup/Restore app by Wanam
* Dump selected LogCat buffers to your PC
* Dump BugReport to your PC
* Set Files Permissions on your device
* Open new Command Prompt for manual input
* Reboot device to Fastboot Mode or Android from fastboot mode [Nexus]
* Reboot device to Fastboot Mode [Nexus], Recovery, Android or Download Mode [Samsung] from adb mode
* Display Important Information about your device
--------------------------------------------------------------
SUPPORTED DEVICES AND LATEST SUPPORTED BUILDS *HERE*
DOWNLOAD THE SKIPSOFT UNIFIED ANDROID TOOLKIT *HERE* (FROM SKIPSOFT.NET)
NOTE: Key files are signed with a Digital Certificate from skipsoft.net but some ‘may’ get picked up as potentially harmful by Antivirus Programs and deleted. They are not harmful, this is a false positive given because of the compiler used. If this happens restore the file and exclude the folder from future scans to use it. This seems to happen mostly on AVG Free and Norton. If you are using the Auto Update feature on pro versions then you will need to disable the AV program or exclude the folder from scans before running the update again.
Credits: ChainsDD for Superuser, Chainfire for SuperSU, koush and the clockworkmod team for cwm and the universal driver pack, 1wayjonny for the adb/fastboot driver pack, Adam Lange for all his support and help with the insecure kernels, Viperboy for the Knox Disabler app, Stephen Erickson for the BusyBox installer app, BurrowsApps for the Root Checker app, NextApp for the SD Fix app, fOmey for TWRP for the Galaxy Gear.
--------------------------------------------------------------
WHAT IS THE DIFFERENCE BETWEEN PUBLIC (FREE) AND PROFESSIONAL (DONATE) VERSIONS?
THE PUBLIC VERSION OF THE TOOLKIT INCLUDES EVERYTHING YOU COULD NEED TO MANIPULATE AND ROOT YOUR DEVICE.
ACTIVATING THE PROFESSIONAL VERSION ADDS THE MOST USEFUL FUNCTION IN THE TOOLKIT, THE ABILITY TO CHECK FOR ‘AUTO UPDATES’ DIRECTLY VIA THE TOOLKIT AND HAVE THEM PUSHED TO YOUR PC RIGHT AWAY AS SOON AS THEY ARE UPLOADED WITHOUT NEEDING TO DOWNLOAD THE WHOLE TOOLKIT EVERY TIME. YOU WILL ALWAYS HAVE THE LATEST VERSION AS SOON AS IT IS MADE AVAILABLE. THIS MEANS SMALLER UPDATES CAN BE SENT OUT MORE FREQUENTLY, SUCH AS ADDING A SINGLE FUNCTION, FIXING A BUG OR ADDING COMPATIBILITY FOR A SINGLE CARRIER. THE SMALLER UPDATES WILL BE COMPILED AND RELEASED TO THE XDA COMMUNITY AS A FULL (PUBLIC) DOWNLOAD VERSION SO PROFESSIONAL VERSIONS ARE ALWAYS UPDATED SOONER.
THE PRO VERSION ALSO ADDS THE ABILITY TO CHECK FOR THE LATEST VERSION OF SUPERUSER AND RECOVERY FILES AND DOWNLOAD THEM DIRECTLY TO THE TOOLKIT.
THE ‘QUICK PICKS’ SECTION[/B] ALLOWS YOU TO PROGRAM UPTO 10 SLOTS WITH TASKS THAT YOU MAY PERFORM ON A REGULAR BASIS OR JUST WANT TO KEEP A SET OF TASKS IN 1 PLACE. THEN JUST SELECT THE SLOT AND IT WILL REMEMBER ALL YOUR SETTINGS FOR THAT TASK AND RUN IT.
PRO USERS CAN ALSO SELECT THE “ANY BUILD” OPTION IN THE BUILD SELECTION SCREEN TO ROOT ANY BUILD AS LONG AS THE VERSION IS SUPPORTED (USEFUL IF YOUR BUILD IS NOT LISTED).
MORE IMPORTANTLY DONATING SHOWS YOUR APPRECIATION AND ALLOWS THE TOOLKIT TO CONTINUE TO EVOLVE AND GROW.
AUTO REPLY LINKS FOR PAYPAL TO GET A CODE INSTANTLY CAN BE FOUND AT http://goo.gl/nyGqv
--------------------------------------------------------------
PLEASE READ THE *HELP* PAGE AT http://www.skipsoft.net/?page_id=1269 OR USE THE INFORMATION SECTION WITHIN THE TOOLKIT IF YOU HAVE ANY QUESTIONS. I HAVE TAKEN A LOT OF TIME TO WRITE IT AND SOMETHING ON THERE SHOULD ANSWER 99% OF PROBLEMS.
--------------------------------------------------------------
1. INSTALLING ADB/FASTBOOT DRIVERS
The first thing you need to do is to install the adb/fastboot drivers. These are needed so that you can unlock your bootloader, root your device and perform other adb/fastboot functions.
THE DRIVERS CAN BE INSTALLED DIRECTLY VIA THE TOOLKIT. OPTION 1 IN THE MAIN MENU.
If drivers are not installed or there is an exclamation mark next to the device:
Plug the device in to a usb cable directly connected to your motherboard.
In the Device Manager a new item, usually called Android 1.0 should pop up in the list.
Right click on the device item then left click on Update Driver Software. Select 'browse my computer' and then 'Let me pick from a list'.
If no adb interface driver appears in the list then untick 'Show compatible hardware' and find the Android or Samsung adb interface driver.
If you cannot find either of these click Have Disk, browse to the Toolkit install folder, drivers folder, click on android_winusb.inf and click Open.
Click OK and select Google ADB Interface.
Make sure you have USB debugging enabled in settings, developer options. In Android 4.2.2 or later you have to enable the developer options screen by going to settings, About on your device and click on Build number at the bottom 7 times until it says You are now a developer. If you have already enabled usb debugging then unplug/replug the usb cable.
On Android 4.2.2 or later when you replug the usb cable after enabling usb debugging for the first time you will get a popup asking you to authenticate your pc. Tick 'Always allow' then click 'ok'.
--------------------------------------------------------------
2. USING SKIPSOFT UNIFIED ANDROID TOOLKIT
When starting the Toolkit you will first be asked which device you want to work with. Working folders will be created and the device files downloaded. You will then be taken to the Model/Build selection screen where you can do a number of things (other than select your model/build): Type '00' to enter your activation code and enable pro features, 'i' will take you to the Information and Help Section, 'a' will give you information on how to add support for a new build.
Supported builds are listed in the Model/Build selection screen and typing the associated number (i.e. 11) will download needed boot and recovery files (stock and custom recovery) then check for and download the latest superuser files available and custom recovery (pro versions only), verify all the files and start the Main Menu. You can now use all the functions and tools the Android Toolkit offers. Pro users can select the "any build" option to root any build (useful if your build is not listed).
--------------------------------------------------------------
ChangeLog:
ToolKit v1.4.1 (05th Oct 2015)
+Added new upcoming devices to device selection screen
+Main files now signed with Digital Certificate to ensure files are original and safe
+Added file checker after device selection to check needed files are up to date
+Updated UniversalAdbInstaller for Windows 10 compatability
+Added driver installation option at startup for new installs
+Updated ToolKitClean.exe to allow users to update the main ToolKit.exe file to latest available version without having to download/install the whole ToolKit again (like when a new device is added or files/drivers updated)
+Improvements and minor bug fixes
+Installer now give option for Fresh Install (removes any existing device files) or Upgrade (to just update base files)
--------------------------------------------------------------
USEFUL INFORMATION
How to get into your FastBoot Mode
1. Turn your phone off
2. Unplug your usb cable if you have one plugged in
3. Keep holding the 'Volume Down' and 'Power' buttons to boot the phone into FastBoot Mode
How to get into Recovery
1. First boot into FastBoot Mode as described above
2. Scroll down with the 'Volume Down' button until it says 'Recovery mode' at the top and press the 'Power' button to enter Recovery
Show the Menu in the Stock Recovery Screen
1. Hold the Power button and keep holding as you press the Volume Up button quickly. The blue recovery menu screen should pop up.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
Manual Rooting Instructions for Galaxy Nexus
UPDATES:
VIDEOS:
Frequently Asked Questions:
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF (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. What is FASTBOOT?
Fastboot is 2 things. It is a mode on the phone, which looks a little like Bootloader. You can access it by holding 'Volume Up' and 'Volume Down' whilst turning on the phone.
It is also a way of flashing radios, recovery, boot images and system images in a command line method from a PC much like adb.
----------------------------------------------------------------------------
Q. I flashed CWM 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. Now when you flash CWM Recovery it will NOT be overwritten after a reboot.
OR you can use the ToolKit to rename the files (root access needed).
----------------------------------------------------------------------------
Q. I want to send my phone back so I need to flash a stock rom and relock the bootloader
1. Download, install and run the Google Nexus 4 Toolkit.
2. Install adb/fastboot drivers (if you havent already done so)
3. Option 9 to download a Google Factory Image.
4. After it finishes downloading you will be given the option to flash the image to your tablet. Do this.
4. Let the phone reboot, then shut the device down and reenter fastboot mode (or boot to fastboot mode via the Reboot Screen in the ToolKit).
5. Option3, 2 to relock the bootloader.
Your internal storage will be formatted and data and cache wiped. Your tablet will now be back to an out-of-the-box FULLY STOCK state and ready to send back.
----------------------------------------------------------------------------
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 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) will pick it up as potentially harmful when it is not. They will 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. The ToolKit recognises my tablet in adb mode but not in fastboot mode (or other way round).
Open the Device Manager on your pc and then boot your tablet into fastboot mode or adb mode (dont plug the usb cable in yet). Make sure USB debugging is enabled on your tablet in settings, developer options. Plug the cable in while watching the Device Manager and determine which item is added to the list with the device plugged in. Once you have found it right click on the item and select update driver. Select 'browse my computer' from the list and then browse to the 'drivers' folder in the ToolKit folder (wherever you installed the ToolKit to). Make sure sub folders is ticked and click next. Hopefully the driver will be picked up and installed.
You can check if a driver has been installed by looking at the top of the Main Menu in the ToolKit while in fastboot mode and adb modes. If a serial number is displayed in each mode then it will work fine.
----------------------------------------------------------------------------
Q. Can I back up my apps before unlocking the Bootloader so I don't lose everything?
Performing an APPS BACKUP (option2, 1) will backup all apps that were installed after you first used your device. This will include any associated user data (such as settings or high scores for games) and apps you installed from Google Play Store. Just follow the recommended options and remember to turn your phones screen on before starting it as you need to confirm on your screen.
This option will NOT require your bootloader to be unlocked first.
You can also backup your Internal Storage without unlocking using option 2, 3 from the main menu. This will backup anything you store on your Internal Storage such as game data, music, videos. This is just pulled from your /data/media folder so you can view or edit the files on your pc after they have been pulled.
You can then unlock the bootloader (wiping your device) and retore the apps (option 2, 10) and Internal Storage data (option 2, 11) after doing whatever you want to with your device.
The only thing you cannot do with the ToolKit is to save the system settings but some of those are backed up by google if you chose that option when turning your device on the first time.
----------------------------------------------------------------------------
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 cannot find Developer options to Enable USB Debugging
With Android 4.2 google have thought it would be funny to hide the Developer options screen in the Settings. This means you cannot enable usb debugging to communicate with your device. To show the Developers options screen do the following:
Goto Settings, About tablet and tap your finger on the the 'Build number' text at the bottom 7 times (not too fast).
When you have tapped 3 times you will be given a countdown of taps until you become a 'developer'.
Once you are told you are now a developer you can go back to the Settings screen and can see Developer options.
You can now go into Developer options and enable usb debugging.
----------------------------------------------------------------------------
Q. I tried to enter the code for the professional version but the Toolkit says the code is incorrect
Make sure the code entered is for the correct Toolkit being used.
You need to make sure you start the Toolkit with the toolkit.exe file when activating and not the tkmain.exe file so the settings can be initialised or the code will not be accepted.
Also make sure you enter the code correctly as the characters are case sensitive.
thnx man!
Works great. very easy and effective. happy to be rooted and have custom recovery and unlocked boot loader. thnc again for hooking us up so quickly.
Much recomended for all users. Easy and all the options and extras you'll need. Then just flash away..............
dangambino said:
Works great. very easy and effective. happy to be rooted and have custom recovery and unlocked boot loader. thnc again for hooking us up so quickly.
Click to expand...
Click to collapse
You're welcome
Can you just confirm if the cwm included in the ToolKit works with the Sprint phone as I have seen nothing about that working or not.
Mark.
mskip said:
You're welcome
Can you just confirm if the cwm included in the ToolKit works with the Sprint phone as I have seen nothing about that working or not.
Mark.
Click to expand...
Click to collapse
Works for me. Flashed it perm and the first thing i did was do a backup. No issues thus far. About to flash Team Win's to see what its all about. But yeah, its working.
whats option 5 rename recovery restore file and also i see manual wipes everything but does the tool kit? i assume the tool kit does too but would just like to clarify thanks.
Anon9mouz said:
whats option 5 rename recovery restore file and also i see manual wipes everything but does the tool kit? i assume the tool kit does too but would just like to clarify thanks.
Click to expand...
Click to collapse
With the non google stock roms there are 2 files that 'could' be present in the system folder. If these files are present and you flash a custom recovery image such as cwm or twrp then on your next reboot the stock recovery will be reflashed and you will lose your custom recovery. To stop this from happening I simply rename the 2 files if they are present so they cant do any harm. The exact commands I use are:
adb-toolkit shell mv /system/recovery-from-boot.p /system/recovery-from-boot.p-old
adb-toolkit shell mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh-old
Click to expand...
Click to collapse
You can rename them yourself but you need root access and a root explorer.
Unlocking the bootloader will wipe EVERYTHING including the virtual sd card whether done manually or using the ToolKit there is no way round this. Even flashing a rom via odin with the phone still locked will unlock the phone and wipe it during the process.
Mark.
Skip I just sent you a message regarding the radio pull CMD
mskip said:
With the non google stock roms there are 2 files that 'could' be present in the system folder. If these files are present and you flash a custom recovery image such as cwm or twrp then on your next reboot the stock recovery will be reflashed and you will lose your custom recovery. To stop this from happening I simply rename the 2 files if they are present so they cant do any harm. The exact commands I use are:
You can rename them yourself but you need root access and a root explorer.
Unlocking the bootloader will wipe EVERYTHING including the virtual sd card whether done manually or using the ToolKit there is no way round this. Even flashing a rom via odin with the phone still locked will unlock the phone and wipe it during the process.
Mark.
Click to expand...
Click to collapse
O OK thanks for that. I see u mention odin I see it was used for everything with the epic 4g touch (SGS2) but I don't see that yet from this even tho there's a dl mode? Well thanks
_____________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Anon9mouz said:
O OK thanks for that. I see u mention odin I see it was used for everything with the epic 4g touch (SGS2) but I don't see that yet from this even tho there's a dl mode? Well thanks
_____________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Click to expand...
Click to collapse
I think people just prefer using fastboot I know I certainly do.
Mark.
Awesome, going to check it out ASAP. I hate not being able to install my root required apps (ES Explorer/Titanium/etc).
Just got my GNex yesterday, was only one of two that the store got.
LAYGO said:
Awesome, going to check it out ASAP. I hate not being able to install my root required apps (ES Explorer/Titanium/etc).
Just got my GNex yesterday, was only one of two that the store got.
Click to expand...
Click to collapse
You're lucky then I think there has been more demand for the Nexus than anyone thought and most places are out of stock.
Mark.
mskip said:
You're lucky then I think there has been more demand for the Nexus than anyone thought and most places are out of stock.
Mark.
Click to expand...
Click to collapse
I KNOW! I tried doing the preorder, but I had just dropped $4500 on getting my roof repaired & the funds were all tied up. By time I had em, the preorder had closed.
I half expected a line or something when I got there, but wasn't anyone. Asked for it, she said "hmm, let me check". Came back with one in her hand saying they only received two & mine was the last one.
I'm not taking time to set it all up until I root it . . . only to repeat it. I'm kinda befuddled about the lack of SD Card slot though. I didn't realize it didn't come with one until I had pulled the battery looking for where it mounted!
LAYGO said:
I KNOW! I tried doing the preorder, but I had just dropped $4500 on getting my roof repaired & the funds were all tied up. By time I had em, the preorder had closed.
I half expected a line or something when I got there, but wasn't anyone. Asked for it, she said "hmm, let me check". Came back with one in her hand saying they only received two & mine was the last one.
I'm not taking time to set it all up until I root it . . . only to repeat it. I'm kinda befuddled about the lack of SD Card slot though. I didn't realize it didn't come with one until I had pulled the battery looking for where it mounted!
Click to expand...
Click to collapse
Plus one on no sd
_____________________________________________________
Sent from my SPH-L700-GNEX-using Tapatalk 2
Will be doing this when I get home from work! I was glad I picked my GNex up yesterday...it was the only one my store received! So I was quite happy...can't wait for more support on the sprint side.
I couldn't wait, I rooted after lunch. Getting Swype installed, first thing, EVERY time. I needs my Swype!
Then to get some apps on there. Connection sucks at work though.
Can someone please pull the radio for the sprint galaxy nexus
I did a n00b mistake and restored a google factory image for VZW on my Sprint Galaxy Nexus...
Any help would be greatly appreciated!!!
I may have spoke so soon. I'm getting error 7 assert fail when flashing a twrp recovery zip. Is that an issue with the recovery on the toolkit or the zip. I flashed a teerom and kernel with no issues though.....
Finally, the OTA came out. But it's still not available in my area here (Malaysia) so I have to wait for it to come. But I'm a little short of patience here, and while the OTA zip files is out, I thought I could just sideload it via adb. But when I try to make it work, I spent 4 hours facing some adb problems. I'm using Linux most of the time, and I have Android SDK downloaded. It was so troublesome to make adb work. Initially adb just couldn't find my device. So I Googled about it, and did some modifications on the PC to solve the usb problem and finally adb could connect to my device (while in Android). Then I started to follow the instructions to sideload. I booted into TWRP recovery using adb command and just to be sure, I ran ./adb devices again while the device is in recovery. But then adb shows no device connected. Trouble. I thought it's the problem with some drivers so I used Windows to try it again. Same problem again. Then I started to Google about it and found some forums that mention that it only works when I manually boot into recovery (Volume Down+Power+Volume UP). I followed. And finally, it solved it. It was only the first problem. Then I pressed into adb sideload mode in TWRP and started sideload mode. And just to be sure again, ./adb devices, no device connected again. I thought it's some bug in TWRP, I stopped sideload mode, and went back to the main menu of TWRP (where adb once can detect the device) and ./adb devices again. Guess what, it shows no device again. Problematic. I restarted my pc for many times, switching from Windows and Ubuntu for many times, repeated the above steps for many times, but the problem is just so random. I even changed the usb cable but no luck. So I decided not to use adb anymore and I've Googled for just flashing ota in TWRP. But there's just very few articles on it. Most of them are using adb and stock recovery. Some of it mentioned that if custom recovery is present then it shouldn't have to be so complicated but none of them shows how to use custom recovery. And one of them says I could just flash the OTA zip file through custom recovery but no instructions for it. The last one is my ideal method now, but because of lack of references, I'm not sure about it.
In short:
-Nexus 7 with TWRP
-problems when using adb to communicate with my device whether it's in normal boot, TWRP recovery, sideload mode, or whatever
-problem is so random and I cant figure out whats the problem
-tried installing and uninstalling and installing drivers again and again
-I dont wanna lose my data
-fed up
Question:
Is the OTA zip file recovery flashable? I dont wanna mess with adb anymore. It just wont work properly with me. Or I have to wait for OTA to reach me?
Are you completely stock (besides the custom recovery)? In other words, have you made any changes to your system partition? (have you uninstalled any app? removed any system apk? installed XPosed framework? edited any file on the system partition?)
If your system partition is not completely stock, OTA may not work (depending on which file you modified).
If you are stock, yes, you can download the OTA zip file to your device (make sure you get the right one), and reboot into recovery, and just install it from recovery.
According to Androidpolice, 4.4.4 -> 5.0: razor LRX21P from KTU84P is available at http://android.clients.google.com/p....signed-razor-LRX21P-from-KTU84P.5a0f7a47.zip
If your device is the razor, and is currently on LRX21P, you can download this and flash it.
jj14 said:
Are you completely stock (besides the custom recovery)? In other words, have you made any changes to your system partition? (have you uninstalled any app? removed any system apk? installed XPosed framework? edited any file on the system partition?)
If your system partition is not completely stock, OTA may not work (depending on which file you modified).
If you are stock, yes, you can download the OTA zip file to your device (make sure you get the right one), and reboot into recovery, and just install it from recovery.
According to Androidpolice, 4.4.4 -> 5.0: razor LRX21P from KTU84P is available at http://android.clients.google.com/p....signed-razor-LRX21P-from-KTU84P.5a0f7a47.zip
If your device is the razor, and is currently on LRX21P, you can download this and flash it.
Click to expand...
Click to collapse
Thanks for answering. This helped me a lot. As I remember I did not modify the system except for xposed which I uninstalled beforehand. What's the worst that could happen if I flash the ota on a modified system?
ImjuzCY said:
Thanks for answering. This helped me a lot. As I remember I did not modify the system except for xposed which I uninstalled beforehand. What's the worst that could happen if I flash the ota on a modified system?
Click to expand...
Click to collapse
When you uninstalled XPosed, I hope you opened XPosed app and clicked the "Uninstall" button from there (instead of just uninstalling XPosed app itself). If not, you will need to reinstall XPosed, uninstall from within the app, and the uninstall the app.
(XPosed modifies a file on your system partition - if you use the uninstall from within the app, it will restore the original file. If you just uninstall the app, the modified file will be left on the system partition).
Worst case scenario - the OTA will fail. I don't think it will cause your existing OS to stop working.
jj14 said:
When you uninstalled XPosed, I hope you opened XPosed app and clicked the "Uninstall" button from there (instead of just uninstalling XPosed app itself). If not, you will need to reinstall XPosed, uninstall from within the app, and the uninstall the app.
(XPosed modifies a file on your system partition - if you use the uninstall from within the app, it will restore the original file. If you just uninstall the app, the modified file will be left on the system partition).
Worst case scenario - the OTA will fail. I don't think it will cause your existing OS to stop working.
Click to expand...
Click to collapse
Yeah i uninstalled it within the installer app and left the installer installed and hope it will work with lollipop in the future.
ImjuzCY said:
Yeah i uninstalled it within the installer app and left the installer installed and hope it will work with lollipop in the future.
Click to expand...
Click to collapse
cool! (it will almost certainly require a new XPosed app because of all the changes that Lollipop brought, but it won't hurt to leave it installed)
Edit: Just read http://forum.xda-developers.com/showpost.php?p=56748099&postcount=5 - looks like you will need to uninstall XPosed too
ImjuzCY said:
Yeah i uninstalled it within the installer app and left the installer installed and hope it will work with lollipop in the future.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=56748099&postcount=5
So my wife, not knowing any better, installed the OTA update about 3 weeks ago. Since then she's been stuck at 60% battery. She isn't concerned about root, and her phone has never been rooted. I was going to do the Verizon Repair Assistant (as others have done) to restore her phone to a previous firmware that (depending on what they have on VZW's servers at this point in time) should revert back to a firmware that allows 100% battery. I know we cannot revert from PHE to PH1 firmware, but upon looking at her phone she has N930VVRS2APK1 . A google search of this build gives me ONE result. What the hell is PK1 on a Verizon phone? Now I'm wondering what exactly she has and what my options are to get her on a 100% battery firmware. I may still try the Verizon Repair Assistant, as there's nothing to lose, but any input on this would be greatly appreciated. Thanks.
Well, I still have no idea what PK1 firmware was, but I was successfully able to ODIN her phone to N930VVRS2APHE with 100% battery. I'm a happy camper.
NarcissusV said:
Well, I still have no idea what PK1 firmware was, but I was successfully able to ODIN her phone to N930VVRS2APHE with 100% battery. I'm a happy camper.
Click to expand...
Click to collapse
This is just what I need to accomplish as well. What were the steps you took to do this?
Dude2 said:
This is just what I need to accomplish as well. What were the steps you took to do this?
Click to expand...
Click to collapse
I've never written a guide, but I just pieced this together after going back and retracing my steps. Feel free to post if you run into errors, but it should work if you're on the same firmware as I was. And, of course, I'm not liable for anything that goes wrong.
- Downloaded the N930VVRS2APHE firmware.
Direct link: https://drive.google.com/open?id=0B40ItdHKfkyQZWM4dU56bjBsb2c
Link above is from this site (in case above direct link fails): http://samfirm.net/threads/update-safely-firmware-galaxy-note7-all-model-22-09-2016.119/ Download SM-N930V file
- Install Samsung drivers: http://www.devfiles.co/download/AbRa7wHc/SAMSUNG_USB_Driver_for_Mobile_Phones.exe
- Install ODIN: http://forum.xda-developers.com/attachment.php?attachmentid=3787684&d=1466307212
- Place phone in 'Download Mode':
Step 1 – Turn OFF your Galaxy Note 7.
Step 2 – Now press and hold the following keys on your phone together:
Volume Down + Home + Power.
- Connect N7 to PC via USB
- Open ODIN
You should have a blue bar under ID:COM in the upper left hand corner if your phone is properly connected and recognized.
- Click on BL and find the BL_xxxxxxx file that you extracted from Step 1
- Click on AP and find the AP_xxxxxxx file that you extracted from Step 1
- Click on CP and find the CP_xxxxxxx file that you extracted from Step 1
- Click on CSC and find the CSC_xxxxxxx file that you extracted from Step 1
(note: you will not need the HOME_CSC_xxxxx file)
- Click 'Start'
- Hold your breath and pray it works
Don't forget that the initial bootup on a new firmware can take a few minutes, so be patient and let it do it's thing. Good luck! Hope it works for you as well as it did me.
NarcissusV said:
I've never written a guide, but I just pieced this together after going back and retracing my steps. Feel free to post if you run into errors, but it should work if you're on the same firmware as I was. And, of course, I'm not liable for anything that goes wrong.
- Downloaded the N930VVRS2APHE firmware.
Direct link: https://drive.google.com/open?id=0B40ItdHKfkyQZWM4dU56bjBsb2c
Link above is from this site (in case above direct link fails): http://samfirm.net/threads/update-safely-firmware-galaxy-note7-all-model-22-09-2016.119/ Download SM-N930V file
- Install Samsung drivers: http://www.devfiles.co/download/AbRa7wHc/SAMSUNG_USB_Driver_for_Mobile_Phones.exe
- Install ODIN: http://forum.xda-developers.com/attachment.php?attachmentid=3787684&d=1466307212
- Place phone in 'Download Mode':
Step 1 – Turn OFF your Galaxy Note 7.
Step 2 – Now press and hold the following keys on your phone together:
Volume Down + Home + Power.
- Connect N7 to PC via USB
- Open ODIN
You should have a blue bar under ID:COM in the upper left hand corner if your phone is properly connected and recognized.
- Click on BL and find the BL_xxxxxxx file that you extracted from Step 1
- Click on AP and find the AP_xxxxxxx file that you extracted from Step 1
- Click on CP and find the CP_xxxxxxx file that you extracted from Step 1
- Click on CSC and find the CSC_xxxxxxx file that you extracted from Step 1
(note: you will not need the HOME_CSC_xxxxx file)
- Click 'Start'
- Hold your breath and pray it works
Don't forget that the initial bootup on a new firmware can take a few minutes, so be patient and let it do it's thing. Good luck! Hope it works for you as well as it did me.
Click to expand...
Click to collapse
NV, thanks for these steps. Two questions as follow up:
1) is the process destructive? Does it effect any data or apps?
2) do I need to add the Over The Air Transfer block before or after running these steps?
I removed the SD card for safe measure, which as absolutely recommend you do. Sorry, forgot to mention that. You will lose all your app data, so upon initial reboot and login/setup it should ask you of you want to load apps from a previous phone (you'll select your N930V), at which point it will very slowly download and install all your apps you had before in the background. It may take 2+ hours, even in wifi. When they're done installing, you'll have to log back into each of your apps.
In regard to the OTA update, yes, you'll need to get Package Disabler Pro and disable the following two processes so you no longer receive any pop-ups or requests to update:
com.sec.android.soagent
com.samsung.sdm
Note: It appears now that Package Disabler Pro and EZ Package Disabler (Samsung) have both decided to completely f*!% over people like us that paid for the apps to disable Samsung bloatware and OTA update reminders. They have removed the ability to manually disable packages (such as the ones we need to deactivate the OTA update messages). If you try and install a previous versions that allowed manual disable it fails the license authentication. They force you to use the current version, which no longer does what we need. Shady business practice and total horse ****.
NarcissusV said:
I removed the SD card for safe measure, which as absolutely recommend you do. Sorry, forgot to mention that. You will lose all your app data, so upon initial reboot and login/setup it should ask you of you want to load apps from a previous phone (you'll select your N930V), at which point it will very slowly download and install all your apps you had before in the background. It may take 2+ hours, even in wifi. When they're done installing, you'll have to log back into each of your apps.
In regard to the OTA update, yes, you'll need to get Package Disabler Pro and disable the following two processes so you no longer receive any pop-ups or requests to update:
com.sec.android.soagent
com.samsung.sdm
Note: It appears now that Package Disabler Pro and EZ Package Disabler (Samsung) have both decided to completely f*!% over people like us that paid for the apps to disable Samsung bloatware and OTA update reminders. They have removed the ability to manually disable packages (such as the ones we need to deactivate the OTA update messages). If you try and install a previous versions that allowed manual disable it fails the license authentication. They force you to use the current version, which no longer does what we need. Shady business practice and total horse ****.
Click to expand...
Click to collapse
Whaaaat? So none of this can be accomplished and we are stuck with the 60% battery of the Verizon update?
No. You can go back to the 100% green battery, but cannot disable the packages so that the phone stops reminding you to update. Just don't accidentally hit it and you're okay.
Okay, but the 60% package was forced on the phone, will these new reminders force their way on to the Note 7?
NarcissusV said:
I removed the SD card for safe measure, which as absolutely recommend you do. Sorry, forgot to mention that. You will lose all your app data, so upon initial reboot and login/setup it should ask you of you want to load apps from a previous phone (you'll select your N930V), at which point it will very slowly download and install all your apps you had before in the background. It may take 2+ hours, even in wifi. When they're done installing, you'll have to log back into each of your apps.
In regard to the OTA update, yes, you'll need to get Package Disabler Pro and disable the following two processes so you no longer receive any pop-ups or requests to update:
com.sec.android.soagent
com.samsung.sdm
Note: It appears now that Package Disabler Pro and EZ Package Disabler (Samsung) have both decided to completely f*!% over people like us that paid for the apps to disable Samsung bloatware and OTA update reminders. They have removed the ability to manually disable packages (such as the ones we need to deactivate the OTA update messages). If you try and install a previous versions that allowed manual disable it fails the license authentication. They force you to use the current version, which no longer does what we need. Shady business practice and total horse ****.
Click to expand...
Click to collapse
NV, when you say "you loose all the app data" will this process erase the email accounts and all the emails, contacts, etc, on the Note 7? I am just using the built in email for a couple of accounts.
I can not find these processes in disablere. Still asks update.
Maybe there is a way to obtain Root with this firmware?
I doubt we can get root, but here's how you can disable OTA update nags:
http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294
http://forum.xda-developers.com/verizon-note-7/help/how-to-disable-samsung-ota-t3478488
Disbler pro did not help, they blocked these processes are associated with the upgrade. Install the new version does not work, wants to update.
Another program is OZ Disabler. Just need to install the earlier version.
shablovskiy said:
Disbler pro did not help, they blocked these processes are associated with the upgrade. Install the new version does not work, wants to update.
Another program is OZ Disabler. Just need to install the earlier version.
Click to expand...
Click to collapse
Shablovskiy, were you able to use OZ Disabler successfully?
NarcissusV said:
I've never written a guide, but I just pieced this together after going back and retracing my steps. Feel free to post if you run into errors, but it should work if you're on the same firmware as I was. And, of course, I'm not liable for anything that goes wrong.
- Downloaded the N930VVRS2APHE firmware.
Direct link: https://drive.google.com/open?id=0B40ItdHKfkyQZWM4dU56bjBsb2c
Link above is from this site (in case above direct link fails): http://samfirm.net/threads/update-safely-firmware-galaxy-note7-all-model-22-09-2016.119/ Download SM-N930V file
- Install Samsung drivers: http://www.devfiles.co/download/AbRa7wHc/SAMSUNG_USB_Driver_for_Mobile_Phones.exe
- Install ODIN: http://forum.xda-developers.com/attachment.php?attachmentid=3787684&d=1466307212
- Place phone in 'Download Mode':
Step 1 – Turn OFF your Galaxy Note 7.
Step 2 – Now press and hold the following keys on your phone together:
Volume Down + Home + Power.
- Connect N7 to PC via USB
- Open ODIN
You should have a blue bar under ID:COM in the upper left hand corner if your phone is properly connected and recognized.
- Click on BL and find the BL_xxxxxxx file that you extracted from Step 1
- Click on AP and find the AP_xxxxxxx file that you extracted from Step 1
- Click on CP and find the CP_xxxxxxx file that you extracted from Step 1
- Click on CSC and find the CSC_xxxxxxx file that you extracted from Step 1
(note: you will not need the HOME_CSC_xxxxx file)
- Click 'Start'
- Hold your breath and pray it works
Don't forget that the initial bootup on a new firmware can take a few minutes, so be patient and let it do it's thing. Good luck! Hope it works for you as well as it did me.
Click to expand...
Click to collapse
How do you install ODIN? I downloaded it to my Windows 7 PC but it is a ".rar" file, not sure how to install it and connect to my Note 7?
Dude2 said:
How do you install ODIN? I downloaded it to my Windows 7 PC but it is a ".rar" file, not sure how to install it and connect to my Note 7?
Click to expand...
Click to collapse
Please pm if you still.need help
Dude2 said:
Shablovskiy, were you able to use OZ Disabler successfully?
Click to expand...
Click to collapse
Yes. I downloaded not latest version. Working good.
http://4pda.ru/forum/dl/post/8422541/EZ+Package+Disabler+v2.3.2P.apk
Sorry. Name is EZ disabler 2.3.2
---------- Post added at 06:30 AM ---------- Previous post was at 05:34 AM ----------
jjayzx said:
Click to expand...
Click to collapse
rar it's archive. You need to install the "win rar" app. Unpack the file "rar".
If you do not know what a "rar" better if not to experiment with it.
Verizon promises to turn off all note 7 of the fifth of January.
shablovskiy said:
Yes. I downloaded not latest version. Working good.
http://4pda.ru/forum/dl/post/8422541/EZ+Package+Disabler+v2.3.2P.apk
Sorry. Name is EZ disabler 2.3.2
---------- Post added at 06:30 AM ---------- Previous post was at 05:34 AM ----------
rar it's archive. You need to install the "win rar" app. Unpack the file "rar".
If you do not know what a "rar" better if not to experiment with it.
Verizon promises to turn off all note 7 of the fifth of January.
Click to expand...
Click to collapse
I know what it is, it's the person above that's lost and made my brain fry by not knowing what it is but wants to mess with odin.
Used a great step by step process to make this happen.
Hi All!!
This thread will now contain pre rooted Odin files for F926B users to flash and update
Before you start, download "420rom_F926B_BVA9_Odin_EUY.zip" from HERE
THIS IS FOR F926B ONLY
The process requires knowledge of basic adb and YOU MUST HAVE ADB INSTALLED BEFORE TRYING THIS
This will no longer wipe data but it is advisable to backup first anyway - i wont be responsible for any data lost that could have been backed up
PROCESS to update from rooted a11 or a12
1 - Unzip the 4 odin files from the zip provided in the link above & connect phone to PC
2 - load ODIN on PC and disable AUTO Reboot - Next load BL.tar in BL, AP.tar in AP, Stock CP in CP and Stock HOMECSC in CSC
3 - Click start to flash the files - when completed, keeping phone connected to PC, press and hold power and volume down and as soon as the screen turns off, press and hold vol up and power UNTIL in TWRP
4 - Head to the TWRP mount menu disable MTP
5 - ONLY IF YOU DONT HAVE A MAGISK.ZIP ON INTERNAL STORAGE copy app-debug.zip to your adb folder and then open a command window and first confirm adb is working by typing adb devices you should see your device listed and "recovery" next to the device in command window - this means adb is working - type adb push app-debug.zip /sdcard this should send the app-debug.zip to internal storage (or sdcard if you prefer)
6 - go to the TWRP flash menu and you should see the app-debug.zip, flash it to root your A12 device - this needs to be done everytime TWRP is flashed in Odin it seems
7 - reboot to system from TWRP power menu
You will boot rooted, updated and with intact data if all the steps above are followed correctly
------------------------------------------------------------------------------------------------------------------
PROCESS IF COMING FROM STOCK A12
1 - Unzip the 4 odin files from the zip provided in the link above & connect phone to PC (please ensure dev settings are enabled and that you have unlocked bootloader and checked "Oem unlock" is faded out under dev settings)
2 - load ODIN on PC and disable AUTO Reboot - Next load BL.tar in BL, AP.tar in AP, Stock CP in CP and Stock HOMECSC in CSC
3 - Click start to flash the files - when completed, keeping phone connected to PC, press and hold power and volume down and as soon as the screen turns off, press and hold vol up and power UNTIL in TWRP
4 - Head to the TWRP wipe menu and format device (type yes and press enter) - then reboot TWRP
5 - when TWRP has rebooted, go to the mounts menu and disable MTP -> this will allow us to send app-debug.zip (magisk) to your sdcard
6 - copy app-debug.zip to your adb folder and then open a command window and first confirm adb is working by typing adb devices you should see your device listed and "recovery" next to the device in command window - this means adb is working
7 - type adb push app-debug.zip /sdcard this should send the app-debug.zip to internal storage (or sdcard if you prefer) - go to the TWRP flash menu and you should see this app-debug.zip, flash it to root your A12 device
8 - as stated previously, i have disabled encryption therefore we just need to boot STRAIGHT to SYSTEM from the TWRP POWER MENU
9 -When phone reboots, set up as normal and you should now see a magisk stub in the app drawer meaning you are rooted
PLEASE NOTE THAT THE MAGISK PATCHED AP FILE IS UPLOADING AND WILL BE AVAILABLE IN A FEW HOURS
Reuploading patched AP file to Mega and will be available shortly
G-drive too a dump on me last night - apologies for the delay
@ianmacd is working on his disabler soon so we will be able to simplify things a bit also - thanks for bearing with me!!
ok my teammate has built a tested and working AP file to use in the guide above - this will be up very shortly
mine was fine however my internet connection is not lol
Ok guys - sorry for the muck about!! the patched AP file is now live in the first post - therefore you can go ahead and root!
Follow the steps carefully, please also read and make sure you have everything prepared before you start
Had a couple of peeps join my telegram chat asking about OEM option being missing.
Please note that this guide only covers the WWE F926B at the moment (US models have a locked bootloader afaik)
Thanks a lot for your work, Just got my hands on with the device.
Is losing the camera option inevitable?
There is no way to keep it enabled?
JazonX said:
Thanks a lot for your work, Just got my hands on with the device.
Is losing the camera option inevitable?
There is no way to keep it enabled?
Click to expand...
Click to collapse
At the moment there is sadly no camera til the bootloader is relocked. Hopefully a fix is found soon
exocetdj said:
Reuploading patched AP file to Mega and will be available shortly
G-drive too a dump on me last night - apologies for the delay
@ianmacd is working on his disabler soon so we will be able to simplify things a bit also - thanks for bearing with me!!
Click to expand...
Click to collapse
Hi, have you managed to upload it to Mega too? I can’t download it from google drive — it failed three times and now it tells me it’s inaccessible as too many people tried to download it...
白い熊 said:
Hi, have you managed to upload it to Mega too? I can’t download it from google drive — it failed three times and now it tells me it’s inaccessible as too many people tried to download it...
Click to expand...
Click to collapse
Hi mate have you managed to access it yet? if not ill try sort links out
白い熊 said:
Hi, have you managed to upload it to Mega too? I can’t download it from google drive — it failed three times and now it tells me it’s inaccessible as too many people tried to download it...
Click to expand...
Click to collapse
try this alternative link
If not ill ask my teammate to mirror to Mega
exocetdj said:
Hi mate have you managed to access it yet? if not ill try sort links out
Click to expand...
Click to collapse
Yeah, after an hour or so it let me in again, and didn’t fail this time. :O)
Killing the camera after unlocking the bootloader is a stupid and crappy move by Samsung.
I remember, oh so long ago, when Samsung actually supported us here on XDA, found quite a large number of things done by devs here suddenly appearing on their "next big thing", then they quietly withdrew their support and went over to the dark side of the Apple-verse.
ultramag69 said:
Killing the camera after unlocking the bootloader is a stupid and crappy move by Samsung.
I remember, oh so long ago, when Samsung actually supported us here on XDA, found quite a large number of things done by devs here suddenly appearing on their "next big thing", then they quietly withdrew their support and went over to the dark side of the Apple-verse.
Click to expand...
Click to collapse
They don't seem to care as much about the modding community nowadays it seems.
Iv had Sammy phones since s8 and been modding with roms since March last year and they've all been a ***** in some way to root
exocetdj said:
They don't seem to care as much about the modding community nowadays it seems.
Iv had Sammy phones since s8 and been modding with roms since March last year and they've all been a ***** in some way to root
Click to expand...
Click to collapse
See, now I'm starting to feel old.
Been here since S2.
Samsung actually had representatives on the forum. They actively helped with rooting and used features that were developed here on XDA, assuming with the dev's permission, in their latest phones (suffice to say most of the features we take for granted today were developed here).
Rooting was EASY. As simple as flashing CWM on to your phone. No worries about KNOX or losing any features. That came around the time of the Note 3 along with region locking.
ultramag69 said:
See, now I'm starting to feel old.
Been here since S2.
Samsung actually had representatives on the forum. They actively helped with rooting and used features that were developed here on XDA, assuming with the dev's permission, in their latest phones (suffice to say most of the features we take for granted today were developed here).
Rooting was EASY. As simple as flashing CWM on to your phone. No worries about KNOX or losing any features. That came around the time of the Note 3 along with region locking.
Click to expand...
Click to collapse
So from my understanding, Knox was actually designed for dual rom booting, as a way to keep the original firmware in tact and safe, but also be able to flash a custom rom for dual boot. But investors, carriers, and the like decided they weren't happy with that and saw that it could also be used to lock the device down to make everything more secure for their intents. After like 4 iterations where Samsung kept being pushed, it became what it is today.
I'm assuming they thought if they just impliment everything that a person would root for, that it would make people OK with it, but of course not the case. In the end, just like any other major corporation, they let money push them around
If we root, remove bloat, and then re-lock the bootloader, would the bloat still be gone? Knowing Sammy, they would prevent us from removing bloat.
I can handle holding out on flashing a sweet ROM if I can remove garbage like Bixby.
As soon as you flash any custom binary then your software is classed as custom and will not boot at all with a locked bootloader. It would soft brick requiring a stock odin flash to revive device most likely
dirtybudha said:
If we root, remove bloat, and then re-lock the bootloader, would the bloat still be gone? Knowing Sammy, they would prevent us from removing bloat.
I can handle holding out on flashing a sweet ROM if I can remove garbage like Bixby.
Click to expand...
Click to collapse
You can remove and/or disable bloat with adb commands for now. There is a thread about it somewhere in our forum
Samkey apparently now supports f926b but I'm getting unsupported firmware errors on AUG8 and AUHF. I really want to get rid of this three bloat