[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - NEXUS 4 - Drivers, Root, Recovery + MORE - Nexus 4 Original Android Development
NEXUS 4 - SUPPORTS ALL VERSIONS UP TO LATEST ANDROID 5.1.1 BUILDS
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.
Google Nexus 4 Frequently Asked Questions
UPDATES:
Frequently Asked Questions:
Q. What is ADB Shell?
Adb shell is a linux command line tool (because android is based on linux) used to send commands to your android device. For S-ON devices, this is crucial for modifying files in the /system partition (where the rom sits) as you cannot modify anything in /system when the rom is running without S-OFF (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.
I think koush tweeted that the recoveries are available about 10 mins ago
Sent from my Galaxy Nexus using Tapatalk 2
Count me in for testing
I can test
Sent from my Nexus 4 using xda app-developers app
Will we get Auto Update access if we participate as testers? =)
Popopinsel said:
Will we get Auto Update access if we participate as testers? =)
Click to expand...
Click to collapse
Yes I am giving activation codes to all testers for helping.
Mark.
[vertigo] said:
Count me in for testing
Click to expand...
Click to collapse
buddahlou said:
I can test
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
pm's sent
Mark.
Dorilife said:
I think koush tweeted that the recoveries are available about 10 mins ago
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
http://www.clockworkmod.com/rommanager
not listed yet anyway
Dorilife said:
I think koush tweeted that the recoveries are available about 10 mins ago
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
He messaged earlier saying that the Nexus 4 and 10 would get CWM Recovery soon but they aren't in http://www.clockworkmod.com/rommanager yet.
Mark.
mskip said:
Yes I am giving activation codes to all testers for helping.
Mark.
Click to expand...
Click to collapse
That's nice!
Any drawbacks in testing? Is it safe or will I brick my precious?
I can do some testing too.
Is it only available for Windows users (I don't have any Windows to test) ?
Popopinsel said:
That's nice!
Any drawbacks in testing? Is it safe or will I brick my precious?
Click to expand...
Click to collapse
No possibility of bricks as images are booted and not flashed so nothing is written permanently.
Mark.
gromez said:
I can do some testing too.
Is it only available for Windows users (I don't have any Windows to test) ?
Click to expand...
Click to collapse
Yes im afraid its only for Windows but if you have already setup adb/fastboot from a previous phone you may be able to run it under an emulator such as WineHQ.
Mark.
I have used your toolkit with my galaxy nexus, but, sadly, I have not the nexus 4 yet. If I get it soon you will know, but maybe you will have enough testers
mskip said:
No possibility of bricks as images are booted and not flashed so nothing is written permanently.
Mark.
Click to expand...
Click to collapse
Ok then, I am at your command for testing!
I will test for you.
Thanks
C
I can test it
My Nexus 4 was delivered a few minutes ago, i can Test it
just PM me
Thanks for the work
Related
[TUT]Root And Install Clock Work Mod Recovey(CWM) Any MediaTek Device!!!!!!!
In most cases an android phone user comes to know about ROOTING and Installing Custom Recovery like CWMR, TWRP and Philz......Popular System on a chip manufacturer(Soc) like Qualcomm has been in the industry since 1985 and has a strong foundation and many of the flagship companies like sam, sony, lg, are using their Soc's. So somewhat developers are very eager to develop for these devices and let the other manufacturer down in their developer community(But not now a days). So here we present the Ultimate guide for the media tek device owners on how to root and install Clock Work Mod Recovery for their phones. ROOTING One of the Best tools for rooting your phone is using FRAMAROOT which was developed by alephzain (Senior Member at XDA) Just use any one of the exploit, Try the available exploit......IT will not ruin your Phone After rebooting if you see the SUPER SU APP in your app drawer, you have successfully ROOTED your Phone. BACKUP YOUR IMEI First of all take backup of your imei for that you have to install 5iromtoolbox 1)Open the app 2)Press backup IMEI 3)Connect your phone with USB cable and go to your pc 4)Open your sd card through windows explorer or whatever you use 5)Seek the folder /sdcard/5irom/imeibackup/ 6)Copy the imeibackup folder to your pc to a folder that you will not by accident format ^_^ 7)You are ok...now you can make whatever you like... To restore your IMEI 1)Take your imeibackup folder from your pc 2)Paste it on your sd card on folder /sdcard/5irom/imeibackup/ 3)Open the 5iromtoolbox 4)Press Restore IMEI and restart your phone!! INSTALLING CUSTOM RECOVERY[IN THIS TUT CLOCK WORK MOD] Install MTK Drivers for your phone if officially available or else follow the steps bellow. Installing Drivers for any android phone First of all download Pdanet+ 1) Enable USB Debugging in Settings -> Developer Options (If you dont have Developer Options in your settings tap 7 times the build number inside about phone, Then you will get the Developer Option) 2) Connect your Phone with a Data cable and run the Pdanet setup >> choose others and continue all the way IF SETUP FAILS 1) Do it another time with other usb options available in your phone like changing to MTP, Camera(PTP), or by turning on the USB Storage, Do it several times it should install the Drivers IF SETUP SUCCEEDS 1) Untick the ticked check-box and click finish. Download MTK Droid Root & Tools developed by rua1(Senior Member at XDA) 1) Connect your phone to computer. 2) Run the tool View attachment 2785013 View attachment 2785014 View attachment 2785015 3) Press Root.... Wait for few Secs 4) Go to Root, backup & Recovery 5) Select "To use boot from phone". and select Recovery and Boot 6) If asked for any permission select yes. And at last the device will reboot into recovery if you were inside the recovery, you have successfully done your job This is an expanded version of rua1 review in his site......
[GUIDE] [Fix] Dreamtab hangs at characters.
Symptoms The classic symptoms of the issue are at some point the Nvidia Dreamtab will stop booting and hang at the Dreamworks characters screen and never boot any further. The frequency ranges from once a month to a year. You are able to factory reset and the issue goes away for some periodicity and then returns. NOTE: If you recently bought a new Nvidia Dreamtab and you have this character freeze right after doing the OTA then this probably isn't the issue, I am working on a different fix for that problem in this thread. If however this solution does fix your issue I'd like to hear about it. Background The tablet uses the linux ext4 filesystem. The Dreamtab kernel requests a filesystem check every 20 partition mounts(typically during reboots) or when the files system is marked dirty(the tablet is hard powered off, or some other glitch). The tablet is missing the fsck binary which is the filesystem checker similar to what you might have seen in windows with chkdsk. Without this file the tablet can not check filesystem and the kernel waits indefinitely for that to happen and your tablet sits and the Dreamworks characters. Solution Temporarily boot to a program(TWRP) that can install the filesystem file on the tablet. To temporarily boot to TWRP the bootloader must be unlocked. The unlock procedure requires erasing all information on the tablet which isn't an issue if you are currently experiencing the problem as a factory reset was the only way to recover anyway. If you have a working tablet and want to apply this fix you should find a way to backup your files prior to attempting this. To better understand how the low level Nabi functions this should be required reading and will help better understand what you are doing. http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119 Procedure Only for Nvidia Dreamtab NV08B. Use this at your own risk, your warranty is void. You will lose all personal data on the device Link to video Youtube video installation 1) Down load the drivers. -- There are 3 popular options included in the link from above in the driver section of the Nabi General Information thread. Have them handy for the next step. 2) Download TWRP recovery. -- The file is attached at bottom of post. DTTWRPinstaller300.zip -- Note: You can automate some of the bootloader unlock and installing TWRP steps below with the install.bat file if you have a working Nabi. 3) Download the fsck patch. -- The file is attached at bottom of post. NV08B_FSCK_PATCH.zip 4) Reboot to fastboot protocol -- With Nabi powered off press and hold the power button and the vol + button until a small menu(bootloader menu) appears. Quickly release both buttons or the tablet will start booting normally. Using the vol- button to highlight the fastboot protocol(2nd option from top) and then press the vol+ button to select it. Note: Depending on if the drivers are installed the screen will change or stay the same. 5) Verify drivers installed or install drivers. -- Open windows device manager. On Windows 10 type "device manager" in to the Cortana search bar. On other versions open run by pressing the "windows key" in lower left of keyboard while also pressing R key. Then type: devmgmt.msc -- If you have "Android Device" and it's sub menu says bootloader/fastboot then you are set up. If down by "other devices" you have an unknown device then you will need to install the drivers from the selection and download you made from reading the Nabi General Information thread. 6) Unlock the bootloader -- This step will ERASE ALL information on the tablet. -- Unzip the DTTWRPinstaller300.zip to a location of your choosing. If you use Windows built in unzip utility make sure you check the box that says to open when unzipping is complete. -- Hold the shift key on the keyboard while right clicking on the "files" folder. Then select "open command window here" -- At the prompt type: Code: fastboot oem unlock Note: You need to move quickly to the tablet and do the next step as there is a timeout -- On the tablet it will ask if you want to unlock. Using the vol- key select "yes" with vol+ or pwr. If you do this properly in the command window on your computer it will tell you it is erasing the device. 7) Temporary boot TWRP -- I can't remember if after the bootloader unlock if tablet is at fastboot, or if you have to power off the tablet and do step 4 again. I think you can just proceed. -- At the prompt type Code: fastboot boot recovery.img 8) Get the patch file on the tablet -- Option A: There are a couple options for this. Check the file explorer on your computer. If you see t8400n as a device you can just copy and paste the NV08B_FSCK_PATCH.zip to the internal storage by copy and pasting in windows. Go to step 9. -- Option B: Insert a microSD card in your computer and copy the NV08B_FSCK_PATCH.zip to your microsd card and insert the sdcard in the tablet. -- Option C: If the t8400n does not show up on your computer then you will need to transfer via ADB. This will require you to setup the ADB driver like you did for fastboot in step 5. Now in sub Android Device in Device Manager you should see ADB, if you don't install driver. --Copy the NV08B_FSCK_PATCH.zip to the "files" folder where you extracted DTTWRPinstaller300.zip. It should be in a folder with adb, fastboot, AdbWinAPi, etc -- At the command prompt type: Code: adb push NV08B_FSCK_PATCH.zip /sdcard 9) Install patch -- In TWRP on tablet click the install tab. Generally you will now see the NV08B_FSCK_PATCH.zip if you picked option A or C. If not navigate to the sdcard folder. If you picked option B navigate up a folder and find external_sdcard folder and look in there. Note: For external_sdcard it may be necessary to exit to TWRP main menu and select mount tab and make sure Micro SDcard is checked. -- Once you have found the NV08B_FSCK_PATCH.zip from inside the install tab you can select it and then swipe to install. You should get verification it completed normally.
I know this is rather old, but I have a couple of these tablets I'm trying to get working again to give to a friend's kids, but this doesn't seem to work. Did you have to have USB debugging checked before the tablets stopped booting in order for this to work properly? Basically I can do all the fastboot stuff without any errors, but when I try to boot to TWRP all the tablets do is pretty much rotate the screen 180° so the bootloader screen is in the opposite corner and the volume buttons no longer work until I hold power for ten seconds to power it off... Any help is greatly appreciated!
Help Kindle Fire HDX 7
I have a rooted kindle and the past few days my Wi-Fi isn't working right. Some days it will switch right on and connect other says you switch it on and it does nothing and acts as if the wifi is still turned off. Please help. I did factory reset and it didn't help. I can post a video to YouTube to show you if you need.
Heatherb90 said: I have a rooted kindle and the past few days my Wi-Fi isn't working right. Some days it will switch right on and connect other says you switch it on and it does nothing and acts as if the wifi is still turned off. Please help. I did factory reset and it didn't help. I can post a video to YouTube to show you if you need. Click to expand... Click to collapse - known side effect of KingRoot - toggling Airplane/Flight mode should work; give it a few seconds to connect - consider a custom ROM if further relief is needed; Fire Nexus (KitKat based) works best if WiFi reliability/stability is a priority
worse issues lol I tried that and now I have royally screwed it up lol. I was in the recovery menu which is team win recovery project v2.8.6.0 and I think it was the advanced wipe which I was thinking was basically a factory reset and it deleted the OS. I tried connecting it to my laptop and have been at it for over an hour and can't get it to connect to my windows 10 laptop. I installed the drivers from amazon. In device manager it shows as Android Phone > Google Nexus ADB Interface but I can't actually see it in my file manager area to try and put the stock kindle back on it. At my witts end and my daughter is so mad she cant use her tablet (she is 3 lol) any help is greatly appreciated.
heather90 said: I tried that and now I have royally screwed it up lol. I was in the recovery menu which is team win recovery project v2.8.6.0 and I think it was the advanced wipe which I was thinking was basically a factory reset and it deleted the OS. I tried connecting it to my laptop and have been at it for over an hour and can't get it to connect to my windows 10 laptop. I installed the drivers from amazon. In device manager it shows as Android Phone > Google Nexus ADB Interface but I can't actually see it in my file manager area to try and put the stock kindle back on it. At my witts end and my daughter is so mad she cant use her tablet (she is 3 lol) any help is greatly appreciated. Click to expand... Click to collapse I will respond to this in the next 24 hours - hang tight.
Thank you I will keep checking for your response. I really appreciate your help.
heather90 said: I tried that and now I have royally screwed it up lol. I was in the recovery menu which is team win recovery project v2.8.6.0 and I think it was the advanced wipe which I was thinking was basically a factory reset and it deleted the OS. I tried connecting it to my laptop and have been at it for over an hour and can't get it to connect to my windows 10 laptop. I installed the drivers from amazon. In device manager it shows as Android Phone > Google Nexus ADB Interface but I can't actually see it in my file manager area to try and put the stock kindle back on it. At my witts end and my daughter is so mad she cant use her tablet (she is 3 lol) any help is greatly appreciated. Click to expand... Click to collapse Obviously the first step is to gain access to the device so files can transfered to it. Unfortunately, TWRP 2.8.6.0 has a mixed record when it comes to exposing the device to Windows. There are alternatives but it gets ugly fast unless you are comfortable messing with adb/fastboot commands. Suggested path: - on Windows 10 install this package to obtain drivers that are know to work with 3rd gen HDX devices - untether device - open Windows device manager - boot HDX into recovery (TWRP) - tether device; take note of what entry(s) appear in device manager - right click those entries and click 'uninstall' - untether HDX, wait a few seconds then retether - when Windows prompts for new drivers manually navigate to "Mot Composite ADB Interface" - open File Explorer in Windows ... does device now appear? There a lot of assumptions built-in to those skeletal instructions starting with familiarity with dealing with Windows devices and drivers (ugh!). Give it a whirl; post back with questions.
LINK? When I click the link to download package it shows up to a thread to download motorola package? Should I be downloading that? Thanks. Davey126 said: Obviously the first step is to gain access to the device so files can transfered to it. Unfortunately, TWRP 2.8.6.0 has a mixed record when it comes to exposing the device to Windows. There are alternatives but it gets ugly fast unless you are comfortable messing with adb/fastboot commands. Suggested path: - on Windows 10 install this package to obtain drivers that are know to work with 3rd gen HDX devices - untether device - open Windows device manager - boot HDX into recovery (TWRP) - tether device; take note of what entry(s) appear in device manager - right click those entries and click 'uninstall' - untether HDX, wait a few seconds then retether - when Windows prompts for new drivers manually navigate to "Mot Composite ADB Interface" - open File Explorer in Windows ... does device now appear? There a lot of assumptions built-in to those skeletal instructions starting with familiarity with dealing with Windows devices and drivers (ugh!). Give it a whirl; post back with questions. Click to expand... Click to collapse
Heatherb90 said: When I click the link to download package it shows up to a thread to download motorola package? Should I be downloading that? Thanks. Click to expand... Click to collapse Yes - Motorola drivers have proven to be highly compatible with HDX devices. The link will install some other stuff that is not needed but is otherwise benign (does not run in background, etc).
My other Kindle Tethers fine I am not sure if this makes any difference but my other Kindle which is exactly the same except unrooted tethers just fine to my laptop. It immediately shows up in file manager as Fire when I plug in the cord. Davey126 said: Obviously the first step is to gain access to the device so files can transfered to it. Unfortunately, TWRP 2.8.6.0 has a mixed record when it comes to exposing the device to Windows. There are alternatives but it gets ugly fast unless you are comfortable messing with adb/fastboot commands. Suggested path: - on Windows 10 install this package to obtain drivers that are know to work with 3rd gen HDX devices - untether device - open Windows device manager - boot HDX into recovery (TWRP) - tether device; take note of what entry(s) appear in device manager - right click those entries and click 'uninstall' - untether HDX, wait a few seconds then retether - when Windows prompts for new drivers manually navigate to "Mot Composite ADB Interface" - open File Explorer in Windows ... does device now appear? There a lot of assumptions built-in to those skeletal instructions starting with familiarity with dealing with Windows devices and drivers (ugh!). Give it a whirl; post back with questions. Click to expand... Click to collapse
waiting I am installing that motorola driver now. Seems it may take quite a while to install.
It didn't change anything. It still shows in device manager as Andriod Phone > Google Nexus ABD Interface and the only thing it does when I right click is open properties and in properties it has General, Drivers, Details, Events and under drivers my only option is Driver details and it also says Driver Provider: Clockwork Mod. Heatherb90 said: When I click the link to download package it shows up to a thread to download motorola package? Should I be downloading that? Thanks. Click to expand... Click to collapse
It didn't change anything when I got the motorola drivers. Still shows up in device manager are android phone and no options to uninstall anything. Davey126 said: Obviously the first step is to gain access to the device so files can transfered to it. Unfortunately, TWRP 2.8.6.0 has a mixed record when it comes to exposing the device to Windows. There are alternatives but it gets ugly fast unless you are comfortable messing with adb/fastboot commands. Suggested path: - on Windows 10 install this package to obtain drivers that are know to work with 3rd gen HDX devices - untether device - open Windows device manager - boot HDX into recovery (TWRP) - tether device; take note of what entry(s) appear in device manager - right click those entries and click 'uninstall' - untether HDX, wait a few seconds then retether - when Windows prompts for new drivers manually navigate to "Mot Composite ADB Interface" - open File Explorer in Windows ... does device now appear? There a lot of assumptions built-in to those skeletal instructions starting with familiarity with dealing with Windows devices and drivers (ugh!). Give it a whirl; post back with questions. Click to expand... Click to collapse
I got it to tether sucessfully. Now to try the next steps in recovering my kindle. Thanks so so so so much for your help. I had to go into TWRP menu and select mount usb storage. Davey126 said: Obviously the first step is to gain access to the device so files can transfered to it. Unfortunately, TWRP 2.8.6.0 has a mixed record when it comes to exposing the device to Windows. There are alternatives but it gets ugly fast unless you are comfortable messing with adb/fastboot commands. Suggested path: - on Windows 10 install this package to obtain drivers that are know to work with 3rd gen HDX devices - untether device - open Windows device manager - boot HDX into recovery (TWRP) - tether device; take note of what entry(s) appear in device manager - right click those entries and click 'uninstall' - untether HDX, wait a few seconds then retether - when Windows prompts for new drivers manually navigate to "Mot Composite ADB Interface" - open File Explorer in Windows ... does device now appear? There a lot of assumptions built-in to those skeletal instructions starting with familiarity with dealing with Windows devices and drivers (ugh!). Give it a whirl; post back with questions. Click to expand... Click to collapse
Got the computer to recognize my device but now I can't flash the kindle software. I tried just drag and dropping it into kindle and couldnt find it via twrp install so i found a thread about using adb commands and i get the issue that my device is unauthorized when i type ADB devices. Davey126 said: Obviously the first step is to gain access to the device so files can transfered to it. Unfortunately, TWRP 2.8.6.0 has a mixed record when it comes to exposing the device to Windows. There are alternatives but it gets ugly fast unless you are comfortable messing with adb/fastboot commands. Suggested path: - on Windows 10 install this package to obtain drivers that are know to work with 3rd gen HDX devices - untether device - open Windows device manager - boot HDX into recovery (TWRP) - tether device; take note of what entry(s) appear in device manager - right click those entries and click 'uninstall' - untether HDX, wait a few seconds then retether - when Windows prompts for new drivers manually navigate to "Mot Composite ADB Interface" - open File Explorer in Windows ... does device now appear? There a lot of assumptions built-in to those skeletal instructions starting with familiarity with dealing with Windows devices and drivers (ugh!). Give it a whirl; post back with questions. Click to expand... Click to collapse
Heatherb90 said: Got the computer to recognize my device but now I can't flash the kindle software. I tried just drag and dropping it into kindle and couldnt find it via twrp install so i found a thread about using adb commands and i get the issue that my device is unauthorized when i type ADB devices. Click to expand... Click to collapse Drag and drop is the way to go. In Windows File Explorer you should see an entry titled "Kindle Fire HDX" (or something similar). Drilling down the next layer should say "Internal Storage". Going further should yield a handful of folders, one of which should be labeled "Download". Put the ROM zip there. On the HDX boot into TWRP, whap the "Install" button and navigate to "/sdcard/download". Note you can NOT reinstall stock FireOS using this method. Unfortunately, the HDX has no native method for recovering from an OS wipe. There are ways to get FireOS reinstalled but there are several caveats. If uncertain which ROM to flash I suggest starting with this one. While relatively old it goes in easy, works with older TWRP builds and is feature complete. Can always upgrade later. Post back with any questions.
When opening the kindle with file explorer I see internal devices then twrp and in that folder is a single file called twrp. I
I am going to try just dropping it in the twrp folder since that is the only folder I have and if that does not work I am not sure what to do. Could I possible create the Download folder within the internal storage folder? Davey126 said: Drag and drop is the way to go. In Windows File Explorer you should see an entry titled "Kindle Fire HDX" (or something similar). Drilling down the next layer should say "Internal Storage". Going further should yield a handful of folders, one of which should be labeled "Download". Put the ROM zip there. On the HDX boot into TWRP, whap the "Install" button and navigate to "/sdcard/download". Note you can NOT reinstall stock FireOS using this method. Unfortunately, the HDX has no native method for recovering from an OS wipe. There are ways to get FireOS reinstalled but there are several caveats. If uncertain which ROM to flash I suggest starting with this one. While relatively old it goes in easy, works with older TWRP builds and is feature complete. Can always upgrade later. Post back with any questions. Click to expand... Click to collapse
OK so I got the file onto the kindle and when i try to flash the rom I get the error E: Error execturing updater binary in zip '/sdcard/downloads/kk-fire-nexus-rom-apollo-20161017.zip' Davey126 said: Drag and drop is the way to go. In Windows File Explorer you should see an entry titled "Kindle Fire HDX" (or something similar). Drilling down the next layer should say "Internal Storage". Going further should yield a handful of folders, one of which should be labeled "Download". Put the ROM zip there. On the HDX boot into TWRP, whap the "Install" button and navigate to "/sdcard/download". Note you can NOT reinstall stock FireOS using this method. Unfortunately, the HDX has no native method for recovering from an OS wipe. There are ways to get FireOS reinstalled but there are several caveats. If uncertain which ROM to flash I suggest starting with this one. While relatively old it goes in easy, works with older TWRP builds and is feature complete. Can always upgrade later. Post back with any questions. Click to expand... Click to collapse
Finally got it thank god. The only rom that would work was Thor. The Apollo one would not work and kicked out that error but first try Thor went right on. Thank you so much for all your help and listening to my annoying posts lol. Davey126 said: Drag and drop is the way to go. In Windows File Explorer you should see an entry titled "Kindle Fire HDX" (or something similar). Drilling down the next layer should say "Internal Storage". Going further should yield a handful of folders, one of which should be labeled "Download". Put the ROM zip there. On the HDX boot into TWRP, whap the "Install" button and navigate to "/sdcard/download". Note you can NOT reinstall stock FireOS using this method. Unfortunately, the HDX has no native method for recovering from an OS wipe. There are ways to get FireOS reinstalled but there are several caveats. If uncertain which ROM to flash I suggest starting with this one. While relatively old it goes in easy, works with older TWRP builds and is feature complete. Can always upgrade later. Post back with any questions. Click to expand... Click to collapse
Heatherb90 said: Finally got it thank god. The only rom that would work was Thor. The Apollo one would not work and kicked out that error but first try Thor went right on. Thank you so much for all your help and listening to my annoying posts lol. Click to expand... Click to collapse Glad you got it sorted. FWIW: - Thor = 7" 3rd gen HDX (your device) - Apollo = 8.9” 3rd gen HDX
Howto recover contacts via TWRP
My screen has been completely destroyed and I managed to put TWRP on the phone like a blind man and start it. That means I can access internal storage from the PC via USB. Now I am wondering where the contacts are stored which I'd love to recover. I start fearing that I need to apply more hacks to the phone which however is unrealistic given the circumstances. To be honest I haven't really grasped all the layers of Android OS, but as long as I'm in recovery I should be allowed to access anything, or not? UPDATE Looks like I need to access "/data/data/..." I guess the problem is that only Internal Storage "/sdcard" is exposed over USB. Can that be changed? BTW "adb devices" shows "unauthorized". How to access everything? What part of the system is blocking it? UPDATE2 Almost there, pulled TWRP from official sources, that apparently has the engineering bit set so you don't need any authorization Now I'm stuck will just "adb pull"ing the entire /data directory cause my crap Windows machine tells me it can't create directories *sigh* Thanks. (Oh BTW , it's an S3 Neo (Android 4.4) and TWRP is 2.8.5.0)
For those who come after me, here is how the entire situation was solved from beginning to end. This is a Galaxy S3 Neo with the display completely broken, no input, no output My PC is a Windows 10 laptop. * Got odin (flash tool) I used 3.12 * Got twrp (from URL twrp.me and looked for my phone model) I used 2.8.7.0, it's important to have an official/correctly compiled one, otherwise adb may show "unauthorized" or whatever * Got Android SDK platform tools (includes adb) Now on the phone, I go to download mode, flash the new recovery and then immediately boot into recovery (otherwise the stock ROM, if still working, will replace the newly flashed recovery again by the stock one): * Remove and restore power (remove all cables and battery, and put them back on) * Careful, maybe the phone will start automatically after you give it power in some situations, you have to be fast * vol-down + home + pow * wait 8 secs * vol-up * start odin 3.12, should see COMx (Windows Device manager shows Samsung USB device) ** untick autoreboot in odin options ** flash new recovery to "AP" (twrp-2.8.7.0-s3ve3g.img.tar) * remove power (cable + battery) * restore power (cable + battery) and immediately hold down vol-up + home + pow * inside recovery I can do anything I want using adb (Device manager shows USB composite device) like "adb shell cp -a /data /external_sd/" (ignore "can't preserve ownership" messages, that because you're copying from ext to fat, no worries here) * copying to the external sd card was the way that worked, just using "adb pull /data" to copy the data directory didn't work because the Windows part of adb somehow could not create files on the local system, no idea (I had Windows device manager running all the time with the "Universal Serial Bus controllers" branch expanded, in order to see what was going on. Maybe take a screenshot with nothing connected, so you see the difference.) Finally, when you're in recovery there are no other layers. Must tutorials talk about adb commands while the ROM is running with USB debugging turned on, which is obviously very much different, and you don't get very far without root(ed ROM). Now for the contacts, on this phone they are located in data\data\com.android.providers.contacts\databases\contacts2.db (use your favorite sqlite browser to view). Noone says this data is easily readable though Feel free to correct me if any of this is wrong =) PS. I must add that during all of this I installed Windows drivers from different sources which made these things work YMMV PS2. You may be able to use commercial tools in cases like this. However it depends on the level of brickage. I believe some have like advanced recovery options to retrieve files from broken phones where they will do automatically what I did here manually (flash new recovery and stuff). However you always need to make sure your exact device is supported, as always. PS3. Now you have all the data. You will not be able to just restore another phone to the state in which the old phone was, but at least you have your data in some form. And you have the possibility of deleting everything left on the phone before recycling
Disassembling MBN Files
I am working on trying to root my Alcatel A50 (nice little phone I picked up on the cheap). In order to install SuperSU to get root access, I need to install a bootloader. By the looks of it, I should be able to make a working bootloader if I have the boot.img file. In order to extract boot.img from the phone, I need root access... a bit of a catch22... I have so far managed to unlock the bootloader and download an official MBN file via the official Alcatel Windows updater. If I can figure out how to extract boot.img from this MBN file, then I may be able to get around the above3 catch 22. From this MBN file (3.4 GB in size), I have managed to extract a bunch of apps (see my journal in the hidden section below for details of how I did that). However, part way through the extractor chokes and quits. Based on the size differential of what I am able to extract vs the overall size of the MBN file, I am sure that there is more lurking inside of this file beyond what was extracted - such as the desired boot.img. What I have gleaned so far in my reading suggests that these MBN files are, in fact, a sort of executable binary file. To that end, I am wondering if anybody has had any luck disassembling these files/fully extracting their contents. In case it helps (either for my query or some future endeavor in a related vein), here is what I have documented of my quest thus far (follow the directions/links/downloads at your own risk): https://web.archive.org/web/2017070...bile.com:80/global-en/support/smartsuite/list Enable OEM Unlock: http://techbeasts.com/how-to-enable-oem-unlock-on-android-nougat/ Install ADB and Fastboot. Go here: https://developer.android.com/studio/releases/platform-tools scroll down to the Downloads section and click on “SDK Platform-Tools for Windows” - it should be a 4-5 MB download. Unzip the files and navigate to the folder via CMD.exe. As Alcatel seems to have merged with another company, it would appear that links to useful software, drivers etc have all been broken in the midst of their overhaul. I must say I was unimpressed with the limited information/downloads available from their present sites (even checking many of their international sites). At any rate, I managed to find a link to the Alcatel Smart Suite (https://web.archive.org/web/2017070...bile.com:80/global-en/support/smartsuite/list) via Archive.org. I simply selected the newest one and – behold – it downloaded. Download Smart Suite → Install and load application. Plug in phone to install Alcatel ADB Driver. Reboot Windows I did run into an issue when running “adb devices” after launching the Smart Suite where it was saying: adb server version (31) doesn't match this client (40); killing... could not read ok from ADB Server * failed to start daemon error: cannot connect to daemon I found someone else had a similar issue (https://stackoverflow.com/questions...rsion-31-doesnt-match-this-client-36#38447003). As per the link, I closed Smart Suite and ran the following terminal commands: adb kill-server adb start-server And that seemed to resolve the issue. You will want to reboot the phone into fastboot mode with this command: adb reboot bootloader And verify that you have connectivity by running: fastboot devices Then type in this command: fastboot oem unlock Your phone will display some text prompting you to unlock the bootloader. Mine says: Unlock bootloader? If you unlock the bootloader, you will be able to install custom operating system software on this phone. A custom OS is not subject to the same testing as the original OS, and can cause your phone and installed applications to stop working properly. To prevent unauthorized access to your personal data, unlocking the bootloader will also delete all personal data from our phone (a “factory data reset”). Press the UP/Down buttons to select Yes or No. Yes: (Volume Up): Unlock (may void warranty) No: (Volume Down): Do not unlock bootloader. To continue, Press the Volume Up button on the phone. Another site suggested I also run: fastboot flashing unlock. I am not sure if that is necessary, but I ran it for good measure. The procedure is the same as above. Once it finishes, press and hold the power button to power the phone off. Then power it back up. Once it is finished erasing, set up the phone again, enable developer mode and USB debugging. Next, we will need to obtain root access. To do this, we will install SUPERSU. Unfortunately, at the time of this writing, the official website only gives us XML files when trying to download the files. I did track down an unofficial mirror, though am not 100% sure of its veracity. Download the latest version (the zip file) and use ADB to push it to the phone (adb push filename.zip /sdcard/) and then use the onboard file manager to move it to your external SD card. Then reboot into recovery mode (adb reboot recovery). Getting Original Firmware http://www.alcatel-mobile.com/cari/support/softwareUpgrade/list Download Mobile_Upgrade_S_Gotu2_v5.2.1_Setup.exe • Install • Shutdown Phone • Load software & select 5085O • Plug in Phone to initiate the downloaded • (?Unplug phone) and wait for download to complete • Go into C:\Mobile Upgrade S Gotu2 v5.2.1\download and grab the big file. Extract Zip → Get MBM File Either using CYGWIN or running it on Linux directly, execute the following perl script (as per this thread discussion - https://forum.xda-developers.com/an...p-4s-help-rooting-installing-t3514186/page9): cat system.mbn | perl -pe 's/(\xFF{5}\x00{4}\xFF{54})[^\xFF]{10}(\xFF{16})/\1\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\2 /g' | perl -pe 's/(\xFF{32})\xA8\xCF\x56\xCF\xFA\x43\x09\x9F\x79(\xFF{32})/\1\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\xFF\2/g' > system.img On Linux, install simg2img. Use this utility to convert the system.img to system.img.raw (cannot recall where I saw this tidbit) Mount system.img.raw (mount system.img.raw /mnt/tmp) sudo cp -R * /home/Downloads/temp/