Database Develop

Droid 4 Utility Updated

If you are on a ICS leak now and want to move to another check out this new tool here: http://forum.xda-developers.com/showthread.php?t=1779810
You can use this to restore stock Gingerbread if you are on a modified GB or to go from one ICS to another.
This is the original D4 tool with additions created by several others and repackaged-edited by me.
UPDATE NOTICE: If you downloaded the tool on 06/20 from about 10pm eastern till noon the next day the script was an old version. It is correct now. Just download again.
06/22 9 AM Eastern - updated superuser binary to most recent version.
06/23 12:30 PM Eastern - updated links for 6.16.213 (thanks again droidian1441)
06/25 10:30 PM Eastern - Revised script, that includes a data save option for restoring GB and the best change. The flashing of the GB files and the ICS Kernel to jump from one ICS to another is now all in one. Removed the push file to sdcard (some thought you could do this after you started flashing the system).
06/30 11 AM Eastern - add new link to download all files.
07/01 10:30 Eastern - Updated Superuser (3.1.3) + binary and VoodooRootKeeper (2.0.3) to latest versions. Update ICS root for Dan Rosenburg's root script, this will install superuser and busybox. The other root method didn't seem to install busybox in proper location and resulted in some malfunctions of root only apps. If you installed the previous root script, use voodoo to temporary unroot, then uninstall superuser. Run the new script and you should be good. Note on the latest version of superuser scroll to the left for the update binary menu. Also contains a temporary unroot and OTA protect root.
Some users have reported driver trouble especially after moving to ICS and trying to root.
Go here to get the driver update tools: https://motorola-global-portal.custh...p/30,6720,8302
Some have reported that the USB utility didn't fix there trouble and had to download motocast, which downloaded new drivers.
Thanks again to 1898trouble07 (droidforums) for the data save tip.
I am on longer putting a full version out. It was was just too big to maintain updates. Everything you need is here. You just have to download a few things and move around a couple of files.
First read this entire post at least twice, skipping any step will be BAD!. Then download everything you need for this.
1. All downloads are listed here: http://d-h.st/users/jsnweitzel/?fld_id=3413#files
Other download links below.
1. Get the Tool Here: https://docs.google.com/open?id=0Byw...URLSjQ5V29pYk0
or here: https://www.dropbox.com/s/132a5i038luy4vu/Droid4withICSfix-rootLITE (3).zip
or here: https://docs.google.com/open?id=0Byw...XV2N2N3cTBoQW8
This is a double zip extract until you see the .bat files and a "files" folder. Double click the script to run the tool.
2. Get the GB 219 Fastboot files here: http://sbf.droid-developers.org/cdma...1FF_01.xml.zip
or here: https://docs.google.com/open?id=0Byw...WswcF91MkxkODA
3. If you are just restoring GB this is all you need. Extract the fastboot zip files and copy them to "files" folder of the tool.
If you are just restoring GB, rooted and running the data save option...It might mess up your root. I don't really know for sure. It will erase the superuser binary and the backup if you are running the rootkeeper, but should keep superuser installed. Therefore you may be in a half rooted stuck state and running the root again may not work. I don't have a phone on GB to test this out. To be extra cautious you may want to run the unroot, restore GB then root again. Let me know what you experience and I can update the post.
If you want to go to ICS and are on GB. Then download (see item one below) the D4213 and put it on your external sdcard Boot to recovery and flash from external. You don't have to be rooted. but if you are the easy way to keep root is to use voodoo's rootkeeper. Protect root, temporarily unroot, reroot, flash the ota, then restore root. If you mess up just use the tool to run the ICS root.
If you are moving from one ICS to another keep reading. Downloading the following two files.
1. Get the ICS OTA currently 6.16.213 ICS here: https://docs.google.com/open?id=0Byw...jVSanRzaTZ5alU
This is a double zip to open until you see the folder named D4213, then copy this file to the external sdcard of your phone.
2. Get the matching Kernel 6.16.213 (boot.img) here: https://docs.google.com/open?id=0Byw...1J0VFBCY1NBM2M
Unzip this folder and copy the boot.img to the "files" folder of the tool. It must be named "ICSFIX" for the tool to work.
If you are going from one ICS to another this is the basic procedure. This uses a fair amount of your pc resources. Don't have a bunch of other programs running. Set the phone to MTP for USB and be sure debugging is on (system setting, developer options).
Be sure you charge your battery first. This is a long process be patient. You will get several errors (INFO validation type) if you are on ICS and flash the GB files. Just let it finish.
1. Charge your battery to 100% and have a high quality usb cable. Sometimes the process fails so you might have to do it twice. When in fastboot mode the battery will not charge.
2. Put the D4213 zip on your external sdcard; just copy and paste with windows.
3. Boot to bootloader and select fastboot (power down, hold both volume buttons and press power, release power, select ap fastboot). You can use the tool for this step but will have to manually do it later.
4. Select menu 16 and flash the GB files plus the boot.img of 213. This will take a while just let it finish and follow the prompts when ask to press a key to continue. You will get some errors (Info validation type). Just let it run and finish.
5. Your phone will reboot and attempt to update (android with spinning ball).
6. Let it run until the screen goes blank and the red "M" appears.
7. Then force a power down and boot to the bootloader.
9. Select recovery. When you see the android with the red exclamation press both volume buttons. Select apply update from external storage and chose the 213 zip.
10. Once complete reboot.
11. ENJOY
12. Root ICS if you want.
If you use this to install vodoo's root keeper make sure your screen is unlocked. If not it seems to hang up sometimes. You should immediately get a superuser request.
Finally this is windows only. If someone writes the linux script I can add it in later. Let me know if you have any issues, suggestions, questions or problems.
As usual doing any of this is at your own risk and may render your phone to be a nice paperweight.
Here is the full menu of the tool:
1. Fastboot GB to stock and ERASE DATA (You can use this to restore stock Gingerbread if you are on a modified GB)
2. Fastboot GB to stock and SAVE DATA
3. Root GB
4. Unroot GB
5. Install Voodoo Rootkeeper
6. Install Safestrap for GB
7. System Pull
8. Overclock for GB
9. Boot to Fastboot
10. Boot to Recovery
11. ADB Shell
12. Reboot phone
13. Flash the ICSFIX Kernel (This is not necessary to jump from one ICS to another, use menu 16. Left in for advanced users only)
14. Install Safestrap for ICS
15. Droid 4 ICS Root
16. D4 ICS Fix (Jump from one leak to another) and SAVE DATA

Thought fastboot back to gb after going to the leaked ics caused a brick?
Sent from my DROID4 using xda premium

twizzles said:
Thought fastboot back to gb after going to the leaked ics caused a brick?
Click to expand...
Click to collapse
Yes, but not completely. The phone will still be able to go into fastboot mode which then allows you to flash the necessary files for the upgrade to work.

Gotcha. Thanks a lot
Sent from my DROID4 using xda premium

What are the necessary files to flash via fastboot after downgrading to gingerbread from ICS?

If you are on GB and want to do a stock restore this will do it for you. If you are on a ICS leak it's one of the steps you need to move up.

Now I will feel more comfortable in flashing the update!, thanks man. Great job.
Sent from my DROID4 using XDA

stereokid said:
What are the necessary files to flash via fastboot after downgrading to gingerbread from ICS?
Click to expand...
Click to collapse
You can't go back to GB if you are on a ICS leak. You can upgrade to a newer leak. Here are the instructions: http://www.droidforums.net/forum/dr...k-200-aka-upgrading-200-206-instructions.html
Same ones can be used to go up to 208. The tool has everything you need.

If im on 206 do i have to flash to 208 in order to flash the new 211 version? And whats in the updates? Enough to take the risk yet again of flashing a leak?
Sent from my DROID4 using xda premium

You can go right up to 211. I haven't changed the tool yet so you will have to replace the 208 files with the 211 files. I will be modifying the tool soon for 211.

Is there an eta for the tool update by any chance? Thanks
Sent from my DROID4 using xda premium

I have started working over the script, with an idea to simplify a step too. But will test on my own phone before I post. You can use the tool as-is if you rename the boot.img and the ota. There is one little hiccup in the script after pushing the boot.img (kernel), but it's doesn't affect the process. Hope to have it up in a few hours.
The new tool is up with some instructions too. The Lite version is good to go, the other is still uploading.

Is it possible to use this tool to flash up from gb? I'm currently using eclipse on safestrap (I know id need to remove safestrap) but didn't know if this will only work with those already on the leaks or if we can use straight from gb
Sent from my DROID4 using XDA

This tool can restore your phone to stock GB. If you have the GB Fastboot files and the latest ICS OTA you can use the lite version and just put add the files to files folder.
If you want to move to ICS you might be able to uninstall your rom, safestrap and fix the logwrapper renaming. I think I saw a thread about that somewhere.

For anyone trying to download I was having some issues setting up the links for gdrive. Just haven't used it before for file sharing. All should be good now.

jsnweitzel said:
This tool can restore your phone to stock GB. If you have the GB Fastboot files and the latest ICS OTA you can use the lite version and just put add the files to files folder.
Click to expand...
Click to collapse
If you can, you might want to edit that first sentence to specify that it can restore your phone to stock GB _if you haven't upgraded to ICS_.

Thanks for the suggestion...just saw that 212 is coming. Will be updating once I get a copy.

Ok I just updated the OP, with all the downloads you need. But it's late I am a bit tired. Let me know if something is out of sorts or a link is broke or wrong. It was just too much to keep the full tool up to date and upload.

Link to the tool is broken unfortunately

jgardner said:
Link to the tool is broken unfortunately
Click to expand...
Click to collapse
Not sure what happened there. I did the link over. Try it now:https://docs.google.com/open?id=0BywuYGr-7VrYcURLSjQ5V29pYk0
Some users on droidforums.net had trouble when they just clicked the link. Not sure why, but it worked if they did a copy and paste to the browser.

[TOOL] All-In-One ToolKit v6.0 |KDZ FLASH|ROOT|Repartitioning|SmartFlash|DualBoot

All-In-One Toolkit​
It is an easy to use tool (especially for noobs) with On-Screen instructions step-by-step to do what the following main menu screen says .. Read detailed information below.
!!! Open to suggestions and ideas !!!​
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
This toolkit runs under Windows. ​Installation Instructions:
Download the package from these links: Mirror1 Mirror2
Run the downloaded package and select a folder to extract the files (your user account must have write permissions in this folder). You can now extract it over a previous version because any un-needed previous files will be removed automatically.
SU660 Users: Download Both P990 & SU660-AddOn packages. Run & extract the P990 first and then extract in the same folder the SU660-AddOn. AIO-Toolkit will be converted to support SU660 device. ​Short & useful description for these options
1 - Backup/Restore Options.
A) Backup/Restore your internal SD Card (via USB Mass-Storage) which is taken with 7z open source tool. Auto-Detects the SD-card’s drive letter (by searching for external_sd or _ExteralSD folder). It just makes a compressed file (7z) of all the files in SD-card as backup action, and extracts this file in SD-card as restore action.
B) Backup/Restore ROM and/or Data partition with nvflash. Backup saves images under Bachup\OldLayout or Backup\NewLayout folder. Restore checks the sizes of current partitions and the backed up images and aborts restore if a partition is smaller than its image or warns if larger. It is needed because anyone now can resize the partitions easily with option 9. Note!! Smaller images can be restored to larger partitions but the final usable size will be the image’s one.​2 - Change your Recovery Image.
Easily change the recovery. It supports two methods: via ADB or NVFlash. It detects the current partition layout and lists the suitable recovery images available for you to choose.
A) Change Recovery via ADB (rooted devices only). It is done with adb tool and dd command.
This works on both normal operation and recovery mode.
On normal operation the device must be rooted and USB debugging must be enabled.
Note: LG Driver package (or at least ADB drivers) must be installed at your PC for these to work.
B) Change Recovery with NVFlash. The recovery is flashed by NVFlash tool.
All latest available recovery images are located in ToolKitFiles\P990-imgs folder to be used by toolkit in any option needed. (or ToolKitFiles\SU660-imgs if SU660-AddOn package is installed).
1) The latest versions of cwm v5, v6 and twrp v2.6, for old BooLoader based ROMS prefixed as oldbl-
2) The modified cwm ones v5, v6 and twrp v2.6 for new BooLoader based ROMS prefixed as newbl-
Any procedure in toolkit, if needed, automatically detects the current partition layout, old or new and lists the suitable recoveries from imgs folder for you to choose.
Tip: You can add/remove/modify the recovery images yourself by copying/deleting/renaming them, in ToolKitFiles\<device>-imgs folder and just prefixing them as oldbl- or newbl- The toolkit will include them automatically. ​3 - Root a Stock ROM (with NVFlash method).
Roots a stock ROM with the method of NVFlashing a recovery of your choice and then installing SuperUser or SuperSU within recovery mode. This method always worked when other tools failed. ​4 - Repartition your device with preferred layout and bootloader:
ATTENTION!! This operation totally wipes your device's internal memory including internal SD-Card. Make sure you have a backup of your critical files, contacts, sms, etc.
It wipes internal memory, recreates partitions, and flashes the right bootloader and recovery image of your choice. You'll be able to boot in recovery mode only to install a new ROM or restore a previous nandroid-backup. It can be used for:
Quick switching to different partition layouts and bootloaders
Repairing a bricked device
It also offers a choice between pre-sized partition tables (for the selected layout and BL) to flash:
Stock [512MB System, 1536MB Data]
Double-Sized System [1024MB System, 2048MB Data] DualBoot Ready
Your own custom one (if you created one with option 9).
After repartition is finished you are prompted to:
a) Fix internal SD-Card automatically, because it is un-mountable after repartitioning.
b) Enable Dual-Boot (only if a DualBoot Ready partition table is selected).
For controling/maintaining Dual-Boot please refer to the DualBoot-Manual.pdf.
Note: LG Driver package (or at least ADB drivers) must be installed at your PC for these to work.
Safety keys: If any of the “SD-Card fix” or “Enable Dual-Boot” step fails go to ToolkitFiles\tools folder and run the IntSD-MountFix.cmd or DualBoot-Enable.cmd accordingly.
Attention: Both scripts are designed to run as standalone scripts also. The IntSD-MountFix.cmd is harmless but DualBoot-Enable.cmd always leaves system switched to ROM1 at the end, so use it ONLY if needed and ONLY on full-wiped data & boot partition e.g. after repartitioning.​5 - Extract LG KDZ and/or AP.bin file.
Use this to extract a downloaded kdz file to get the baseband (fls file) and/or the ROM (bin file) to flash with SmartFlash.
Additionally you may need to extract the bin file to separate the included partition images like chefs need to cook their new ROM. ​6 - LG Update Tool (Off-Line mode) to flash any KDZ ROM file.
It helps you flash any KDZ file, since the LG Update Tool does not allow a flash if the device is not in the current version LG expects. So we make our PC to serve LG update tool locally (offline).
The script automatically:
Adds 127.0.0.1 csmg.lgmobile.com entry (temporarily) in hosts file,
Sets the mini mongoose web server on the PC listening to port 9002 which serves the requests of the LG flash utility and run from wherever this package is extracted),
Installs MSXML needed for the tools to run
Runs all the utilities automatically for you (you only have to set to ON the windows enabler)
Opens in your web browser the instructions to follow and flash the ROM.
Finally it reverts back your hosts file, after closing the utility (R&D Test Tool), removing the above entry and stops http server and windows enabler.
7 - SmartFlash a Stock ROM and/or BaseBand.
It flashes a full Stock ROM (bin file) AND/OR Baseband (fls file) as I mention before in option 5.
For BaseBands information and downloads visit the detailed and helpful Complete Baseband overview thread by tonyp.
For official Stock ROMs (KDZ files) visit this site​8 - Replace Stock (locked) ICS BootLoader with the New un-locked one.
ONLY for devices already partitioned to ICS layout.
It detects the current partition layout and does not proceed if OLD layout found.
Needed for those who:
Installed Stock ICS with SmartFlash or LGUpdate
Flashed a ready-rooted system.img only and trying to flash a recovery image after
Have a P990 device but are still on the bootloader logoed with a white padlock, which does not enter SmartFlash mode.
9 - Create your own custom-sized partition table to flash with option 4.
It launches the Partitions Customizer GUI tool I created (see attached picture), to help you easily create your own custom-sized partition table to flash with option 4.
Attention!! DO NOT use it if you don’t know what and why you are doing it.​A – Get useful logs.
This option gets 4 different useful logs (Normal Logcat, Radio Logcat, Kernel and Last_kmsg) as very nicely described in this useful TonyP’s thread. All four commands are integrated in AIO-Toolkit for quick use without having to remember the commands. Thanks to TonyP.​I - Install APX (NVFlash Recovery) Drivers if not already installed.
It starts the windows device driver wizard to help you install the drivers needed for NVFlash. It detects your system OS and gives additional on-screen instructions needed if your PC is running Windows 8.
FYI: The drivers are located under ToolKitFiles\nvflash\driver folder.​Spanish Translation here by elxufas (Thank you)​Change Log
V6.0: Date 10 November 2013:
Evolved DualBoot-Control.zip v6.0:
It now supports two different sized system parts for ROM1 & ROM2 (not only two half) depending on total system size. You can also have a standard 512MB for one ROM and the rest for the other.
One zip for both P990 & SU660 devices (no more different zips for the two devices)
An option is added to re-join the previously split /system partition after enabling DualBoot.
Some bug fixes
New icons and short descriptions for each option added.
DualBoot-Enable.cmd (under ToolKitFiles\tools) is also updated to support different sized system parts too. This is called by Option 4 after repartitioning to enable Dual-Boot, when a DualBoot Ready layout is selected.
Small HTTP server (http.exe) which was used by option 6 for off-line LG update, has been substituted by mini web server mongoose, cause http.exe was considered infected by most Anti-Virus SW.
Prefixes ICS- and GB- of files and recovery images changed to newbl- and oldbl- accordingly, as these are commonly used at all XDA threads to declare the bootloader and partition layout. (SU660-AddOn package also updated to v6.0 with prefix changes).
New Update mechanism: When extracting toolkit-package into existing toolkit-folder, any previous manually added recovery image(s) will be kept and properly prefixed automatically (SU660 recoveries too). Recovery images are now reside under new folder named ToolKitFiles\<device>-imgs where <device> is P990 (or SU660 if SU660-AddOn package is installed).
You can now add more than 9 recovery images per layout. No more limits of nine (9) recovery images per layout. (That’s only because I don’t like limits, not because more than 9 recoveries exist )
TWRP Recovery images updated with TonyP’s latest v2.6.0.0 versions. Thanks TonyP
SuperSU install zip updated to latest version 1.65 (SU\SuperSU-v1.65.zip)
Some warning msgs added about adb drivers when they are gonna be needed.
Of course updated manuals to reflect new changes.
A HowTo.. Steps Guide (pdf) is included, to help (mostly new) users.
Older versions' changes:
V5.6: Date 03 June 2013:
SDCard can now be fixed if TWRP recovery is selected.
a typo corrected that caused the toolkit to close without any explanation after option 4 was completed.
V5.5: Date 07 May 2013:
New and more efficient DualBoot-Control.zip v5.5:
Dual-Boot is NO MORE dependent on the specific re-sized layout DualBoot-Control.zip auto-detects the system partition’s total size and splits it into two parts when enabling dual-boot. Note: If you create your own custom partition table (Option 9), the minimum system’s total size for enabling Dual-Boot is 1024MB.
It is noob-proof because it detects the current system part (ROM1 or ROM2) and gives only the appropriate options for maintaining Dual-Boot.
An additional option is added in its aroma menu, to switch ROMs within recovery (not only through SystemChangerX app in normal operation).
Improved and more detailed aroma GUI and more..
Same zip for both P900 & SU660 devices. (Till now a different file was included in SU660 add-on pack)
Option 4 renamed to: Repartition your device with preferred layout and bootloader
Optimized and updated to support Dual-Boot. Besides layout and bl you can now choose between a) stock, b) dual-boot ready partition table and c) your own created with option 9 (if you created one)
It fixes automatically the Internal SD-Card after repartitioning (if you select so when prompted). Necessary for devices with no external sdcard available. No more need to install the IntSD-MountFix.zip.
Simplified and clearer display messages to eliminate newbies’ confusion.
It also enables dual-boot (if you accept when prompted), if a dual-boot partition table is flashed and save you some steps and reboots from installation instructions.
Option A – Prepare device for Real Dual-Boot is removed. The existing Dual-Boot ready re-sized layouts are now available in Option 4.
Option 8 renamed to:Replace Stock (locked) ICS BootLoader with the New un-locked one to eliminate newbies’ confusion about its use.
TWRP Recovery images updated with TonyP’s latest v2.5.0.0. Thanks TonyP
New Option: A – Get useful Logs is now added in toolkit as requested by some of you. All commands described very nicely in TonyP’s thread are integrated in toolkit for quick use. Thank you TonyP.
Minor fix in backup/restore sd-card: When canceling it didn’t return correctly.
ADB tool updated to latest 1.0.31
V5.0: Date 08 Feb 2013:
Toolkit is now modular: It can support theoretically more LG devices with AddOn packages. An AddOn package for SU660 is already implemented.
Option: A – Prepare device for Dual-Boot is added to repartition the device for Dual-Boot support. Attention: DualBoot uses a spesific partition table, so if you are on dual-boot you cannot resize partitions because it will mess-up the device.
Changing recovery via adb now also works when device is into recovery (not only on normal operation) and gives the option to boot into the newly flashed recovery right after.
In option 8 is now clearly mentioned that it is not needed if option 4 has been used, It is needed only if the device is still on Stock locked bootloader. A lot of people still think that they have to use option 8 every time they change to ICS partition layout. Option 4 had always been flashing the un-locked ICS bootloader when changing to ICS partition.
After repartitioning the device enters recovery automatically when powered on. No need to keep pressing Vol- & Pwr.
For OLD BL only the extended (512MB system) partition table is included, to support up-coming new ROMs. If someone wants the stock 350MB he can always make one with PartitionResizer.
Only one of the latest v5, v6 & twrp v2.4 recovery versions is now included for each bootloader to reduce the package size. It will not remove the existing recoveries if extracted into the same folder. Remember that any other recovery image wanted can be added manually as always. (Thanks to Tonyp for his modified twrp v2.4 for the new bl)
Fixed: Extracting kdz under WinXP not working. It was due to different behavior of Microsoft expand.exe on WinXP than on Win7,8 (it doesn't accept wildcards as input file).
Toolkit now checks its write permissions in the folder extracted and gives a warning.
Updated IntSD-MountFix.zip & System-ReFormat-ext4.zip to work on both P990 and SU660 devices independently of the partition layout and bootloader.
SuperSU install zip updated to install latest v1.04 version.
V4.0: Date 05 Jan 2013:
Includes the fix for the options 1 & 5 not starting under certain circumstances.
Off-Line LG-Update Instructions now converted to html and will be opened on your default browser. (NO doc file, NO need to be associated to some application like office to open). It also has an info page of its own too.
More checking and error handling. Now checks (where possible) prerequisites and errors and gives possible reasons and solutions. It is important at least to prevent showing that an operation finished successfully while it didn't. I had to use other mechanisms to do that since some tools don’t return error codes.
KDZ extractor will stop if file is corrupted
BIN extractor will also check if images extracted successfully.
Off-Line LG Update will check if http.exe is not blocked by AV S/W and if the hosts file is modified successfully.
NVFlash Restore checks the sizes of current partitions and the backed up images and aborts restore if a partition is smaller than its image or warns if larger. It is needed because anyone now can resize the partitions easily with option 9. Note!! Smaller images can be restored to larger partitions but the final usable size will be the image’s one.
Completed instructions for flashing a recovery image via ADB successfully on CM10 ROMs too.
Minor changes in displayed messages.
V3.6: Date 01 Jan 2013:
Fixes the nvflash configuration file error: file not found In option 4, which happens if error occurs and user presses any key to retry.
V3.5: Date 30 Dec 2012
Option 1 changed to Backup/Restore options and now (additionally to SDCard backup/restore) includes NVFlash Backup/Restore of full ROM (boot, system, data), ROM only or Data only.
Option 2 changed to Change your Recovery Image and have two options (to select the method)
1 - Change Recovery via ADB (rooted devices only). It now works in CM ROMs too
2 - Change Recovery with NVFlash
The new versions of intSD-MountFix.zip and System-ReFormat-ext4.zip (already attached in OP) now included in toolkit
IntSD-MountFix.zip now works on both layouts and fixes SD only if needed to avoid formatting wrong partition when flashed by mistake.
System-ReFormat-ext4.zip now works on both layouts too.
More detailed information On-Screen for newbies by just pressing H when prompted.
ics-partitions.cfg file for nvflash has the ext3 FS-fix for the MSC partition (thanks pengus77 for your advice).
New ICS recovery 6.0.2.5 by pengus77 is now included. (Thanks pengus77).
Install APX Drivers now as new option (I) in main menu with on-screen instructions for win8 users. (In gray color cause it's an one time action and needed only if drivers are not already installed).
The AIO-Toolkit now zipped as self-extracted exe. It can be extracted over a previous version also, because now any un-needed previous files will be removed automatically. Also creates a shortcut in your desktop for quick access.
V3.0: Date 23 Dec 2012
A new tool “PartitionCustomizer.exe”added with option 9 to help you easily create a re-sized partition table to flash with option 4.
Windows 8 users won’t be asked anymore to install MS .Net Framework 3.5.
Toolkit now checks your windows version and uses system’s choice.exe in Vista,Win7& Win8. In WinXP systems it will use the alternate Choice.exe (under ToolKitFiles\tools, renamed to Choice4XP.exe.
CMxx_IntSD-Mount-Fix_AfterRepartitioning.zip added in CWM folder. Install this in recovery mode after repartitioning and installing a CMxx based ROM.
Install-APX-Drivers.cmd script is added in ToolKitFiles\nvflash\driver. It installs APX drivers without having to plug the phone first (in nvflash mode pressing vol- & vol+)
All instructions and help of OP now Included in pack as a pdf document for quick help. I will keep working on it to make it a full manual and guide.
V2.0: Date 16 Dec 2012
Two more options added.
SmartFlash a Stock ROM and/or Baseband (Completing this way the toolkit’s name “All-In-One”)
Flash New Un-Locked ICS Bootloader.
Added more safeties (like automatic detection of partition layout) and warnings to prevent wrong choices.
Added a cwm-flashable SuperSU-v0.99.zip inSU folder also for those who prefer it instead of SuperUser. Every zip can be flashed over an already installed SU or SuperSU. Removes previous occurrences of these.
Added two flashable zips in CWM folder for re-formating system partition in ext4 in case nandroid restore fails after repartioning.
Simplified/shorter instructions for the automatic off-line LG Update Tool
2nd minor fix in BIN extractor occurring sometimes when drag/drop a folder or file. Thanks to SuperSkill for discovering the bug.
Bugfix of not backing-up files with no extension from internal SD-card.
DPInst32.exe& DPInst64.exe files have been added under ToolKitFiles\nvflash\driver. Run one depending on your windows platform (x86, x64) to install APX drivers easier if needed.
An extra Addon pack available for fixing the not mounting interal sd-card bug in CMxx ROMs.
V1.1: Date 2 Dec 2012 Fixes a weird bug in BIN Extractor, when the full pathname of the BIN file contains parenthesis ( ) either in a parent folder or the name itself.
V1.0: Date 29 Nov 2012 First version uploaded.
​Credits
rmein & Stefan for the idea and parts of their scripts I integrate
wkpark for the modified cwm v5.0.2.8e the BIN extractor and of course for Unlocking the ICS Bootloader, Big thanks to him. Without him we would have no ICS development.
Tonyp For: baseband instructions, his modified twrp recovery for new BL and adb commands for getting logs.
pengus77 for his custom v6.0.2.5 cwm image
Rusty! for cwm 5.0.2.8 (internal – external)
Stefan again for modified v6.0.1.5 cwm image
homero2 for part of his script in bin extractor.
unknown_world for his original instructions how to officially update in off-line mode.
ProgMaq: For his Full Brick Repair tool that helped with CMxx mount bug.
jes0411 for his original script for P970 to extract KDZ files.
navossoc and XDA team for creating LGExtract tool
thomas_polaert for his colorizing echo (cecho.exe)​General Info: How to install unsigned drivers in Windows 8.
For APX Drivers needed for NVFlash operations, use Option I.
For any other unsigned drivers needed, this is the way to install them:
Move your mouse to Right down Corner.
Click Settings (gear icon)
Click Change PC Settings
Click General (On right panel of the screen) under Advanced startup
Click Restart now
OR
Easiest way for the above: Hit WinKey + R, type in the following command and hit enter:
shutdown -o -r -t 0
--------------------
Wait for next menu..
Click Troubleshoot.
Click Advanced Options
Click Startup Settings
Click Restart.
Wait to reboot. It will come back with boot menu with many options
Press the number of the Disable driver signature enforcement
Windows will boot normally.Now install the drivers you want.
Note:After your next reboot the enforcement gets enabled again.
​

thanks for sharing

Oh nice. thats hell lot of options. will try sometimes this weekend. Thanks a lot for your work. P990 is unbrickable phone and many nvflash builds available, so not afraid of trying anything these days. lolz.

Thank You! This toolkit is very useful! From new ics layout back to GB layout smartflashing 28G baseband was easy!

Thanks...
Looks to be very promising, Thanks, will try it.

Nice work indeed!
I love the fact that there's still fresh development on this old phone
But I don't think I should appear in the credits for providing CWM 6.0.1.5 touch.
I just dowloaded the official build from here: http://www.clockworkmod.com/rommanager
For removing me you could highlight wkpark a little more, especially for cracking the new bootloader.
Without him there wouldn't be any CWM with the new bootloader.

What was the data size? 1.5GB? Can u make a size of 744 for the system? Tks alots....

tonyp said:
Nice work indeed!
I love the fact that there's still fresh development on this old phone
But I don't think I should appear in the credits for providing CWM 6.0.1.5 touch.
I just dowloaded the official build from here: http://www.clockworkmod.com/rommanager
For removing me you could highlight wkpark a little more, especially for cracking the new bootloader.
Without him there wouldn't be any CWM with the new bootloader.
Click to expand...
Click to collapse
Thank you,
You are right about wkpark and the bootloader I forgot the new bootloader completely.
I will correct it.
@wkpark sorry,

cmahendra said:
Oh nice. thats hell lot of options. will try sometimes this weekend. Thanks a lot for your work. P990 is unbrickable phone and many nvflash builds available, so not afraid of trying anything these days. lolz.
Click to expand...
Click to collapse
Glad you found this to be true in your case Been struggling with a bricked P990 for a few days now that errs out when nvflash tries to flash a new bootloader. Will definitely try this tool when I get home tonight and see what I find. Crossing my fingers here
[EDIT] No dice. Still bricked. Happy for any input here; I'm clueless at this point. Seems I've tried everything the internet can suggest. Can't even read the partition table from my phone; can't download bootloader; always errors. Full info at http://forum.xda-developers.com/showpost.php?p=34754117&postcount=38 [/EDIT]

orbital_71 said:
What was the data size? 1.5GB? Can u make a size of 744 for the system? Tks alots....
Click to expand...
Click to collapse
Noted.
Maybe in next version I will include different system sizes for the user to select.
But for now you can always edit the .cfg file (gb-large.cfg or ics-partitions.cfg) under ToolKitFiles\nvflash folder.
Search for the partition named APP and change its size to 780140544 (744*1024*1024).
Note: This is enough for old layout (gb-large.cfg). For ICS one (ICS-partition.cfg) since all partitions are sized (in contrary with OLD layout that UDB partition is set to 0xFFFFFFFFFFFFFFFF which means all the rest) you have to reduce UDB size (internal SD) by the additional size you added in APP partition.
So for this example you have to reduce UDB by (744-512)*1024*1024 = 243269632.
Have in mind that you are not gonna have this system size available if you flash one of the current ICS NVFlash ROMs because their system.img is 512MB.
The whole 744 size will be avalable only with ROMS that are flashed with CWM zips, which don't have a system.img inside but a system folder.
OR
After you flash an nvflash ROM make a nandroid backup, resize the partitions and restore the backup (I haven't tried it but it should work)

can you add the bootloader install?! old and ne, may be useful after flash ics via smart flash ie

solrakk6 said:
can you add the bootloader install?! old and ne, may be useful after flash ics via smart flash ie
Click to expand...
Click to collapse
I am not sure I understood.
Which new and old? You mean the GB and the ICS one or the ICS locked and unlocked one?
The new unlocked one is usefull in case you want to be able to boot in a cwm recovery and it is flashed in rooting option along with the recovery of your choice.
What would be the reason to flash only the bootloader.

Great tool, but is it only me who can't extract the bin file? Thanks
Sent from the new smoothly LGP990

I just uploaded an update v.1.1
It fixes a weird bug in BIN Extractor that it's not working, when the full pathname of the BIN file contains parenthesis ( ) either in a parent folder or the name itself.
If you already have downloaded the v1.0 just download the updated-script attached in post.
EDIT: It is a batch scripting bug.
I had used conditional “IF something DO (….) ELSE (….)” in BIN extracting script, to extract all partitions or just one. A BIN file’s pathname with parenthesis breaked the IF ELSE condition. Batch just s***ks

spyrosk said:
I just uploaded an update v.1.1
It fixes a weird bug in BIN Extractor that it's not working, when the full pathname of the BIN file contains parenthesis ( ) either in a parent folder or the name itself.
If you already have downloaded the v1.0 just download the updated-script attached in post.
Click to expand...
Click to collapse
I got it working last night, so this is my reply, I got another output on the bin file
Thanks for updating
Sent from the new smoothly LGP990

Internal SD
Hey, I really like your ToolKit. I've been messing around with it, but I have one problem (not sure whether it lies in your ToolKit or me being stupid). After I flashed to a rooted ICS leak a few days ago, I wanted to revert back to CM10 (to check out the in-call-bug fix). Now, it seemed to me that your toolkit would come in handy to revert back to the old bootloader and partition layout. At first i was messing around with CWM: I couldn't mount my SD to flash a CM.zip. It seems that only the older CWM version (1st option in your menu) lets me mount the SD. Ok, so I was able to mount my micro-SD again and I flashed the rom, gapps and the fix. After booting, my phone didnt recognize my internal nor external SD; after connecting to USB, my computer only showed my micro-SD, but when I entered it, it seemed empty. The internal storage isn't recognized by my computer at all. I tried some other tools to flash a few different roms but I ended up reverting back to the ICS-leak I was using in the first place: then both the internal and external storage were recognized again (with no loss of data on the micro-sd).
Well, I'm no developer at all but I read some things about formatting the internal storage; could it be that, after repartitioning, your tool doesn't format my internal storage partition and that this causes mounting problems? I tried formatting it manually through ADB, but it didn't work (probably because my ADB/linux s*ck).
Maybe you have any idea to help me out here Thanks in advance

Thank you for this great tool!

ValentineCrow said:
Hey, I really like your ToolKit. I've been messing around with it, but I have one problem (not sure whether it lies in your ToolKit or me being stupid). After I flashed to a rooted ICS leak a few days ago, I wanted to revert back to CM10 (to check out the in-call-bug fix). Now, it seemed to me that your toolkit would come in handy to revert back to the old bootloader and partition layout. At first i was messing around with CWM: I couldn't mount my SD to flash a CM.zip. It seems that only the older CWM version (1st option in your menu) lets me mount the SD. Ok, so I was able to mount my micro-SD again and I flashed the rom, gapps and the fix. After booting, my phone didnt recognize my internal nor external SD; after connecting to USB, my computer only showed my micro-SD, but when I entered it, it seemed empty. The internal storage isn't recognized by my computer at all. I tried some other tools to flash a few different roms but I ended up reverting back to the ICS-leak I was using in the first place: then both the internal and external storage were recognized again (with no loss of data on the micro-sd).
Well, I'm no developer at all but I read some things about formatting the internal storage; could it be that, after repartitioning, your tool doesn't format my internal storage partition and that this causes mounting problems? I tried formatting it manually through ADB, but it didn't work (probably because my ADB/linux s*ck).
Maybe you have any idea to help me out here Thanks in advance
Click to expand...
Click to collapse
your tool doesn't format my internal storage partition and that this causes mounting problems?
Click to expand...
Click to collapse
Repartitoning uses nvflash to recreate all partitions again and nvflash wipes all partitions including internal SD for sure.
At first i was messing around with CWM: I couldn't mount my SD to flash a CM.zip. It seems that only the older CWM version (1st option in your menu) lets me mount the SD
Click to expand...
Click to collapse
where your CM.zip was? In external or Internal SD? 1st option should be the cwm-5.0.2.8-ext.img. That recovery mounts the external SD by default.
Could you give me more details of what exactly you did step by step? Somewhere I lost you.
1) you repartioned to old layout
2) which cwm did you choose?
3) Your CM.zip should be in your external SD because internal would be wiped.
I would also suggest that if you have a nandroid backup of a previous CM ROM try to restore it first, make sure that everything is working as it should and then flash the newer CM you want. Maybe the problem with SD cards is in the ROM you are trying to flash.
Please let me know

can i root the 30A with the root toolkit option??!
---------- Post added at 08:45 PM ---------- Previous post was at 08:28 PM ----------
spyrosk said:
I am not sure I understood.
Which new and old? You mean the GB and the ICS one or the ICS locked and unlocked one?
The new unlocked one is usefull in case you want to be able to boot in a cwm recovery and it is flashed in rooting option along with the recovery of your choice.
What would be the reason to flash only the bootloader.
Click to expand...
Click to collapse
exactly

solrakk6 said:
can i root the 30A with the root toolkit option??!
---------- Post added at 08:45 PM ---------- Previous post was at 08:28 PM ----------
exactly
Click to expand...
Click to collapse
I tested it with V28G and it worked. It should work with 30A also

TWRP, ROOT and disable Encryption for Yoga Tab 3 Plus (YT-X703F/L)

TWRP is an open source, community project. TWRP development is done by roughly 4 people at this point. We also have a large support community with many people who are willing to answer questions and help people with their devices either through our IRC channel or on forums like xda-developers.
Team Win was originally formed to work on porting WiMAX to CM7 for the HTC EVO 4G. After our work on the EVO 4G we wanted to work on a project that would work on more devices than just the EVO 4G and we settled on working on a recovery. Today TWRP is the leading custom recovery for Android phones.
A custom recovery is used for installing custom software on your device. This custom software can include smaller modifications like rooting your device or even replacing the firmware of the device with a completely custom "ROM" like OmniROM
Click to expand...
Click to collapse
WARNING!!! Be careful what you do here. One mistake and the device is soft-bricked. I take no responsibility for bricked devices, lost warranty or even OTAs not working!! Booting and/or flashing files from this post is on your own risk.
Requirements
Unlocked bootloader
Yoga Tablet 3 Plus with and without LTE (YT-X703L and YT-X703F) are supported
Known Issues
WARNING! Our device uses dm-verity (verified boot). The system partition should remain read-only. Otherwise a bootloop will occur. You can flash my modified kernel or SuperSU to resolve this but OTA's are no longer possible! You have to restore a factory image or clean system backup to receive OTAs
Potentially DRM keys are lost! Pure unlocking and rooting does not cause the issue. However, there have been reports of lost DRM keys by some unknown action. It is advised to act with caution. Losing your DRM keys can lead to issues with some apps which use DRM which could then have limited or no functionality. E.g. Netflix will only stream in SD (480p). You can check with DRM info if you still have L1 security level which means DRM keys are intact.
Download
Official TWRP for YT-X703F (Wifi): twrp.me
Official TWRP for YT-X703L (LTE): twrp.me
Instructions
Install fastboot and adb on your PC, e.g. from here
Enable developer options and in there select to unlock your bootloader by enabling OEM unlock and enable USB debugging
Connect your PC to your tablet and run
Code:
adb reboot bootloader
using adb on command line. The tablet will reboot into bootloader mode where you will only see the Lenovo logo. Now you use
Code:
fastboot oem unlock-go
to unlock. This will factory reset your device
Setup the tablet again and reboot again to the bootloader
Then run
Code:
fastboot boot twrp-3.2.1-0-yt_x703f.img
to temporarily boot into TWRP. You can also flash if you are sure
Select to keep system read only when TWRP starts to avoid modification which will make OTAs impossible
Optionally flash SuperSU or Magisk in TWRP which should install system less. Keep OEM unlock enabled if you flash or modify anything
Additional Downloads
Backup of original boot, recovery and system image for YT-X703F S000936: MEGA
Modified Boot image with forceencrypt disabled and it switches off CABC fully. You need to factory reset after flashing to format data without encryption boot_yt_x703f_s000963_noforceencrypt_cabc.img (YT-X703F S000963) / boot_yt_x703l_s000963_noforceencrypt_cabc.img (YT-X703L S000963) . Use
Code:
fastboot flash boot boot_yt_x703f_s000963_noforceencrypt_cabc.img
to flash the kernel in fastboot. SuperSU or Magisk should be flashed afterwards if root is desired.
Full factory images with flash tool and instructions YT_X703F_S000689, YT_X703L_S000704, YT_X703F_S000725, YT_X703L_S000725, YT_X703F_S000734, YT_X703L_S000734, YT_X703L_S000744, YT-X703F_S000744, YT-X703L_S000963, YT-X703F_S000963 and OTA updates: MEGA (These images contain the individual boot, recovery and system images that you need to restore from any modification mentioned above)
System Updates (OTA)
In order to successfully apply Lenovo system updates after root you have to restore the original boot, recovery (if you flashed TWRP) and system partitions from your current installed version (e.g. S000744) for your variant of the tablet. This will NOT delete your apps and data but will unroot. Note that OTAs are block based and always check the contents of most of the partitions. This means that all of these partitions (except your data) have to be original and have to be on the exact same version (e.g. S000734) for the update to succeed.
See here for instructions how to restore the partitions with fastboot.
Credits
@pogo1975 - for providing the factory images and fixing the AV sync issue
@launcher20 and @deecept - for testing the LTE version
TeamWin
Changelog
v4:
Now official TWRP with version 3.0.3-0
v3:
enable full disk encryption for access to the encrypted data partition
update TWRP kernel to latest S000725 version
v2:
add support for LTE variant (YT-X703L)
add further mount points to be able to backup more data

Thanks buddy! You are an absolute champion! Tell me what you need me to do and I'll do it before rooting and up load what you need.

Doing good work here.
Who wants to bet on a race between matshias and Lenovo support for who can fix the issues with this device first?

That's great and fast, I'm thinking tab 3 plus is getting hot now.

Great to see there is something moving for the yoga now. You think it will support the lte Version anytime? Or maybee even lineageos?

so you know, i've managed to install xposed thanks to this thread https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268 and is working well.

wayney said:
Thanks buddy! You are an absolute champion! Tell me what you need me to do and I'll do it before rooting and up load what you need.
Click to expand...
Click to collapse
Well if you haven't modified anything yet then it'd be great if you can boot into TWRP with system read only and then connect via ADB to the tablet with a big SD card inserted which has enough free space (4 GB).
The run the following command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
This will take a while. Then copy the file system.img from your SD card to a PC and zip it (or 7z, rar). Then upload it

Gogoho said:
Great to see there is something moving for the yoga now. You think it will support the lte Version anytime? Or maybee even lineageos?
Click to expand...
Click to collapse
The LTE variant is probably very similar and it wouldn't be much work. But I don't own the device, so I would need some help. So someone with the LTE variant who is not afraid to experiment with fastboot and adb and who can provide me with the details needed I am happy to compile a TWRP for it.
LineageOS is much much more work than TWRP. For an experienced cyanogenmod/LineageOS dev it is not much of a thing and would take only a few days, especially since it is a Qualcomm device and there are already ports for devices with SD 652. But for me this is new as well so it'll take much longer. As soon as I have time I'll look into it.

matshias said:
Well if you haven't modified anything yet then it'd be great if you can boot into TWRP with system read only and then connect via ADB to the tablet with a big SD card inserted which has enough free space (4 GB).
The run the following command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
This will take a while. Then copy the file system.img from your SD card to a PC and zip it (or 7z, rar). Then upload it
Click to expand...
Click to collapse
You forgot to tell me to go to adb shell :silly:
DD is currently doing a dump, non interactive so I hope it is still alive, it has been close to 1 hour so far. I will upload the clean image once it is done and await further instructions from you. :good:
I'm in Perth, Western Australia (UTC +8:00), so we might be playing timezone tag.

wayney said:
You forgot to tell me to go to adb shell :silly:
DD is currently doing a dump, non interactive so I hope it is still alive, it has been close to 1 hour so far. I will upload the clean image once it is done and await further instructions from you. :good:
I'm in Perth, Western Australia (UTC +8:00), so we might be playing timezone tag.
Click to expand...
Click to collapse
I think I forgot one more thing. The external SD card needs to be mounted in the TWRP menu. I believe it's not mounted automatically. So the DD command does nothing. It shouldn't take that long. Sorry about that!
It's UTC +1:00 here in Germany

matshias said:
Well if you haven't modified anything yet then it'd be great if you can boot into TWRP with system read only and then connect via ADB to the tablet with a big SD card inserted which has enough free space (4 GB).
The run the following command
Code:
dd if=/dev/block/bootdevice/by-name/system of=/sdcard1/system.img
This will take a while. Then copy the file system.img from your SD card to a PC and zip it (or 7z, rar). Then upload it
Click to expand...
Click to collapse
matshias said:
I think I forgot one more thing. The external SD card needs to be mounted in the TWRP menu. I believe it's not mounted automatically. So the DD command does nothing. It shouldn't take that long. Sorry about that!
It's UTC +1:00 here in Germany
Click to expand...
Click to collapse
I was wondering why nothing was happening after 3 hours.
I have rared it and it is uploading at the moment, it is going to take 5 hours.

wayney said:
I was wondering why nothing was happening after 3 hours.
I have rared it and it is uploading at the moment, it is going to take 5 hours.
Click to expand...
Click to collapse
Wow ok. Well thanks a lot for your efforts. This will not just help me but anyone with modified system partition to get OTAs.

Unmodified System Image
Here is the vanilla image via DD of the system partition.
Software Version : YT-X703F_160817
Android Version : 6.0.1
Security Patch Level : 1 September 2016
Kernel Version : 3.10.84-perf
Build Number : YT-X703F_S000689_161105_ROW
Tablet purchased retail from Australia.
https://mega.nz/#!bos0GIjI!vcO9dpSJX...Grjb7k3z6mjnqA

wayney said:
Here is the vanilla image via DD of the system partition.
Software Version : YT-X703F_160817
Android Version : 6.0.1
Security Patch Level : 1 September 2016
Kernel Version : 3.10.84-perf
Build Number : YT-X703F_S000689_161105_ROW
Tablet purchased retail from Australia.
https://mega.nz/#!bos0GIjI
Click to expand...
Click to collapse
Perfect!!
Can you send me the key for the download via PM or post it?

matshias said:
Perfect!!
Can you send me the key for the download via PM or post it?
Click to expand...
Click to collapse
Let's try that again.
https://mega.nz/#!bos0GIjI!vcO9dpSJXp6cKtdH07Kt0RSaqpqQ7Grjb7k3z6mjnqA

matshias said:
Wow ok. Well thanks a lot for your efforts. This will not just help me but anyone with modified system partition to get OTAs.
Click to expand...
Click to collapse
Thank you guys for spending times on it, it would be wonderful if Lenovo people do thing like this way, too.

In the depths of the Russian Internet i have found this
YT-X703F_USR_S000689_1611051146_Q00237_ROW.zip
https://drive.google.com/drive/folders/0B_jGuhC9WsNfYUZzZmhRY2NhQlU?usp=sharing
it is supose to be complete image to Wifi-Version.
I HAVE NOT FLASHED THIS YET. Do it on your risk.

pogo1975 said:
In the depths of the Russian Internet i have found this
YT-X703F_USR_S000689_1611051146_Q00237_ROW.zip
https://drive.google.com/drive/folders/0B_jGuhC9WsNfYUZzZmhRY2NhQlU?usp=sharing
it is supose to be complete image to Wifi-Version.
I HAVE NOT FLASHED THIS YET. Do it on your risk.
Click to expand...
Click to collapse
Hahaha got to love the dark corner of the Russian internets :laugh:

pogo1975 said:
In the depths of the Russian Internet i have found this
YT-X703F_USR_S000689_1611051146_Q00237_ROW.zip
https://drive.google.com/drive/folders/0B_jGuhC9WsNfYUZzZmhRY2NhQlU?usp=sharing
it is supose to be complete image to Wifi-Version.
I HAVE NOT FLASHED THIS YET. Do it on your risk.
Click to expand...
Click to collapse
If that's real it would have saved me a lot of time finding the loophole in the system to extract the boot and recovery image. But still a great find which will rescue some soft-bricked devices.

matshias said:
If that's real it would have saved me a lot of time finding the loophole in the system to extract the boot and recovery image. But still a great find which will rescue some soft-bricked devices.
Click to expand...
Click to collapse
so long as it's safe and not loaded with malware...

[Solved!] I want to update TWRP, but ...

Hi!
I have a Nook HD+ running CM 12.1 (Android 5.1.1). The tablet is not rooted. Right now I have TWRP v2.7.1.0 installed, but would like to update to a newer version.
Installing v2.7.1.0 was a breeze. I booted into recovery mode (ClockWorkMod at the time), then flashed an Ovation TWRP ZIP file that I downloaded online. Looking for the most recent Ovation version, it seems it's only available as an IMG file. I can't find a version of TWRP more recent than v2.7.1.0 for Ovation in a ZIP format. Since the tablet is not rooted, I can't flash the newer version using Flashify or similar apps (as far as I can tell, that is) since they all require root access. And I can't flash an IMG file with v2.7.1.0, since that feature wasn't included until a later version (v2.8.5.0 I think). Therein lies the problem. I need a newer version to update, but I can't update until I have a newer version!
I've struggled with the suggested methods of installing TWRP from an IMG file, and would really like to simply flash a ZIP file (I'm already pretty good at doing that). So I've come up with a possible method that sounds too easy and too good to be true. Examining the ZIP folder for v2.7.1.0 (using Linux Archive Manager), I can see that there is a recovery IMG file and a folder labeled META-INF. If I replaced the v2.7.10 recovery IMG file with a more recent TWRP IMG file and left the META-INF file as is, would that work? Or, does the META-INF folder only support v2.7.1.0?
Thanks for your help ... and for not laughing at my possibly nutty idea

MaydayMalone said:
Hi!
I have a Nook HD+ running CM 12.1 (Android 5.1.1). The tablet is not rooted. Right now I have TWRP v2.7.1.0 installed, but would like to update to a newer version.
Installing v2.7.1.0 was a breeze. I booted into recovery mode (ClockWorkMod at the time), then flashed an Ovation TWRP ZIP file that I downloaded online. Looking for the most recent Ovation version, it seems it's only available as an IMG file. I can't find a version of TWRP more recent than v2.7.1.0 for Ovation in a ZIP format.
Click to expand...
Click to collapse
More recent versions of TWRP in flashable zip for HD+ (ovation) are available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778, but you should check for their compatibility with your CM12.1 ROM.
...
I've struggled with the suggested methods of installing TWRP from an IMG file, and would really like to simply flash a ZIP file (I'm already pretty good at doing that). So I've come up with a possible method that sounds too easy and too good to be true. Examining the ZIP folder for v2.7.1.0 (using Linux Archive Manager), I can see that there is a recovery IMG file and a folder labeled META-INF. If I replaced the v2.7.10 recovery IMG file with a more recent TWRP IMG file and left the META-INF file as is, would that work? Or, does the META-INF folder only support v2.7.1.0?
...
Click to expand...
Click to collapse
I have successfully updated flashable recovery zip files (for both the Nook NT and Nook HD+) with more updated recovery images by using an archive manager tool (mostly Windows 7-zip) to swap the recovery img files, just as you're contemplating -- see my brief discussion of this at https://forum.xda-developers.com/showpost.php?p=71402570&postcount=270.
There is a possibility that the update-binary and updater-script in the given flashable zip are not compatible with the newer recovery file image (in which case one would get an error trying to flash it) but I have yet to encounter it, presumably because the versions of old and new recovery images involved have been relative close to one another.

digixmax said:
More recent versions of TWRP in flashable zip for HD+ (ovation) are available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778, but you should check for their compatibility with your CM12.1 ROM.
I have successfully updated flashable recovery zip files (for both the Nook NT and Nook HD+) with more updated recovery images by using an archive manager tool (mostly Windows 7-zip) to swap the recovery img files, just as you're contemplating -- see my brief discussion of this at https://forum.xda-developers.com/showpost.php?p=71402570&postcount=270.
There is a possibility that the update-binary and updater-script in the given flashable zip are not compatible with the newer recovery file image (in which case one would get an error trying to flash it) but I have yet to encounter it, presumably because the versions of old and new recovery images involved have been relative close to one another.
Click to expand...
Click to collapse
Thanks for your response. You told me exactly what I needed to know.
I have viewed D. Andrei Măceș dropbox in the past, but I neglected to check it for TWRP updates (my bad). I'll keep this in mind the next time I want to explore new possibilities for my HD+.
The idea of creating my own zip was a temptation that I couldn't resist (since I was now feeling confident that I wouldn't brick my tablet, blow up Pittsburgh, or be responsible for something equally catastrophic). So, instead of downloading a zip file from the dropbox, I used Linux Archive Manager (I switched to Linux Mint some time ago to escape the more-frequent-than-I-could-bear crashes with Windows), to delete the file named recovery.img in the v2.7.1.0 zip, then inserted a recovery.img file for TWRP v3.1.1.0 in it's place. It worked perfectly, and I feel like a genius (I'm very easily impressed)!
Thanks for letting me know that my idea wasn't as dumb as I feared it might be.

digixmax said:
More recent versions of TWRP in flashable zip for HD+ (ovation) are available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778, but you should check for their compatibility with your CM12.1 ROM.
I have successfully updated flashable recovery zip files (for both the Nook NT and Nook HD+) with more updated recovery images by using an archive manager tool (mostly Windows 7-zip) to swap the recovery img files, just as you're contemplating -- see my brief discussion of this at https://forum.xda-developers.com/showpost.php?p=71402570&postcount=270.
There is a possibility that the update-binary and updater-script in the given flashable zip are not compatible with the newer recovery file image (in which case one would get an error trying to flash it) but I have yet to encounter it, presumably because the versions of old and new recovery images involved have been relative close to one another.
Click to expand...
Click to collapse
Hello,
I tried using the TWRP 3.0.1.0 - ovation and 2.8.7.5. and they both receive the status 7 error:
"This package is for device: ovation ; this device is .
E: Error in /external+sd/twrp-3.0.1-0-ovation.zip
(Status 7)
Installation aborted"
I currently run on CWM Recovery 6.0.4.6, with cyanogenbootloader, lineage os 14.1. Unfortunately I cannot turn off my device (Nook HD+) no matter what, it keeps turning itself on until it empties battery (if I don't pay attention).
I keep trying to install the zips from CWM Recovery but I cannot do it.
Is there any way for me to install TWRP from CWM?
Thank you

pnkye said:
Hello,
I tried using the TWRP 3.0.1.0 - ovation and 2.8.7.5. and they both receive the status 7 error:
"This package is for device: ovation ; this device is .
E: Error in /external+sd/twrp-3.0.1-0-ovation.zip
(Status 7)
Installation aborted"
Click to expand...
Click to collapse
Did you use one of the flashable TWRP zip files from https://www.mediafire.com/#6a4rivb8kkdfu?
I currently run on CWM Recovery 6.0.4.6, with cyanogenbootloader, lineage os 14.1. Unfortunately I cannot turn off my device (Nook HD+) no matter what, it keeps turning itself on until it empties battery (if I don't pay attention).
Click to expand...
Click to collapse
Did you tried holding down the power button for 30+ sec?

Thank you for the answer.
1. The link doesn't work (https://www.mediafire.com/#6a4rivb8kkdfu?) leads me to an upload page.
2. I tried all the options I could find online. If I let it be for 1 week (I use it for reading and sometimes youtube) it turns itself on at some point and the battery goes empty. And it is so hard to turn it on again. When I plug it for charging the battery and is completely empty, the led stays green - instead of orange - for a long time and is not responsive to anything I do until it reaches 80%+ , so I let it be for 2hrs while plugged.
3. What I try to do is actually root it for overclocking or make it a little bit faster because it lags in every thing I do with it. Although in some variants of the Android which I installed over the years it used to be more responsive.
Unfortunately I cannot root it because CWM doesn't recognize the install of SuperSU zip from Lineage website. Do you have any advice on that?
Thanks

pnkye said:
...
The link doesn't work (https://www.mediafire.com/#6a4rivb8kkdfu?) leads me to an upload page.
Click to expand...
Click to collapse
Try this link: https://www.mediafire.com/folder/6a4rivb8kkdfu/Nook+HD+

digixmax said:
Try this link: https://www.mediafire.com/folder/6a4rivb8kkdfu/Nook+HD+
Click to expand...
Click to collapse
Thank you very much! You really helped me with this one!
I just did it! Flashed it with the cwm.flashable.twrp zip from your link!
I run now the TWRP 3.0.1-0.
I couldn't flash any higher versions (3.2.x) directly from this installed version
Anyway my booting time is faster and so far (1min time) the turning on/off procedure works normal, as it should be.
What lineage OS version is the best one for the nook hd+?
I just installed the 14.1 version from the lnos-ovation-ota-NJH47F.181223.zip found at: https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778
This version, however, has landscape mode as default viewing mode and it keeps spinning here and there.
At the moment I find myself in the latest stage of my process: rooting the device so I can try and overclock it.
Trying to install the official lineage "addonsu-14.1-arm-signed.zip" , from their website (https://download.lineageos.org/extras), but it doesn't work.
I mean it installs it successfully in the TWRP recovery. It is enabled in the developer options for both Apps and Adb. But the root checker app says it is not rooted.
Is there a proper way to root it? If so could you please share a solution when you have time?
Also any ideas on how to properly overclock (make the tablet a little snappier, besides the animation scale option from dev options)?
Cheers!

pnkye said:
I just did it! Flashed it with the cwm.flashable.twrp zip from your link!
I run now the TWRP 3.0.1-0.
I couldn't flash any higher versions (3.2.x) directly from this installed version
Click to expand...
Click to collapse
There should be an option in TWRP to "flash image" you can use to directly flash .img binary of a newer TWRP version.
What lineage OS version is the best one for the nook hd+?
I just installed the 14.1 version from the lnos-ovation-ota-NJH47F.181223.zip found at: https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3332706778
This version, however, has landscape mode as default viewing mode and it keeps spinning here and there.
Click to expand...
Click to collapse
You should be able to disable auto-rotation in Settings->Display.
At the moment I find myself in the latest stage of my process: rooting the device so I can try and overclock it.
Trying to install the official lineage "addonsu-14.1-arm-signed.zip" , from their website (https://download.lineageos.org/extras), but it doesn't work.
I mean it installs it successfully in the TWRP recovery. It is enabled in the developer options for both Apps and Adb. But the root checker app says it is not rooted.
Click to expand...
Click to collapse
Try disabling and exit Settings->Developer Options, then come back and re-enable it.

digixmax said:
There should be an option in TWRP to "flash image" you can use to directly flash .img binary of a newer TWRP version.
You should be able to disable auto-rotation in Settings->Display.
Click to expand...
Click to collapse
My device is with default landscape. If I disable it it stays in landscape and never goes to portrait.
digixmax said:
Try disabling and exit Settings->Developer Options, then come back and re-enable it.
Click to expand...
Click to collapse
It still doesn't work.
Thanks for the overall guidance!

Finally A605FN with ROOTED Android 10 and WORKING lockscreen/keystore !!!

Hi guys, it's a while since my last post on XDA, but a couple of days ago I got that phone and I started playing with it.
I spent literally one day to figure out how to get the damn thing working. I NEEDED Android 10 (too long to explain why, given I usually stick with the oldest version available)
The problem is that the broken lockscreen is just the tip of the iceberg, with broken biometrics and/or keystore a lot of apps are broken as well (banking apps, billing apps, and also simpler apps that relies on such features (like the current Parallels RDP client)
Long story short, after a lot of reading here and elsewhere looks like no one before me had a fully working A6+ with root and A10, so I accepted the challenge and used a lot of my free time flashing and reflashing and testing, and finally the stubborn thing surrended.
So below is what what you need to do to to have a fixed phone
(I assume you have already unlocked your bootloader)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
#1 Flash Android 10 with odin (I suggest to use an U5 build, so you can go back to Android 9 (if you want/need to)
#2 Boot the phone once, skip the google account part but connect it to internet once or you will be stick to PRENORMAL condition (and you can't flash anything except official firmwares)
#3 Extract boot.img from the official firmware using 7zip ZETA STANDARD (not the plain 7zip!!!). C opy the file to the phone (say the download folder)
#4 Install Magisk 24 (not 25, not 22), Magisk 23 may work as well. Use magisk to install itself on the boot.img file (it's your only option since the phone isn't yet rooted), copy the patched file back to your PC, RENAME IT to boot.img, and compress it to boot.tar using 7zip
#5 Use odin, be sure to uncheck the autoreboot option then flash boot.tar, w/o rebooting the phone flash the TRWP recovery (disconnect and reconnect the USB cable before the 2nd flash operation).
Use the old twrp_3.2.3-1_sm-a605_141218.tar (it's buggy, but newer recoveries 3.5.x.x are more buggy, in a different way)
#6 reboot to recovery, format data (I mean FORMAT not just wipe !!!), then reboot to recovery (if you can mount the data partition you are OK for the next step)
#7 Install the lockscreen fix for Pie SM-A605-keymaster-fix-by-Not_Sure.zip (here)
#8 Install Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (not Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip or no-verity-opt-encrypt-6.0.zip as suggested in other threads), don't install other suggested files like "RMM-disable-something")
#9 Reboot to system, and you are almost done
#10 check the lockscreen, if everything is ok, install the magisk 24 apk, and open it (it may ask to do additional configurations and reboot the phone
#11 enjoy your rooted and fully working phone
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Optionally you can flash the latest U8 android 10 w/o having to upgrade your bootloader, to do so you can flash just the system and vendor partitions.
To do so you have to extract them from the AP file from the very latest FW for your phone then recompress the img files to tar (same thing as boot file described in #3 for boot image.
If you do so you need to repeat the above steps starting from #7
The lockscreen fix still works on freshest A10 (tested personally)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
That's all, I hope this help the (few) people who owns this phone.

The Solutor said:
Hi guys, it's a while since my last post on XDA, but a couple of days ago I got that phone and I started playing with it.
I spent literally one day to figure out how to get the damn thing working. I NEEDED Android 10 (too long to explain why, given I usually stick with the oldest version available)
The problem is that the broken lockscreen is just the tip of the iceberg, with broken biometrics and/or keystore a lot of apps are broken as well (banking apps, billing apps, and also simpler apps that relies on such features (like the current Parallels RDP client)
Long story short, after a lot of reading here and elsewhere looks like no one before me had a fully working A6+ with root and A10, so I accepted the challenge and used a lot of my free time flashing and reflashing and testing, and finally the stubborn thing surrended.
So below is what what you need to do to to have a fixed phone
(I assume you have already unlocked your bootloader)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
#1 Flash Android 10 with odin (I suggest to use an U5 build, so you can go back to Android 9 (if you want/need to)
#2 Boot the phone once, skip the google account part but connect it to internet once or you will be stick to PRENORMAL condition (and you can't flash anything except official firmwares)
#3 Extract boot.img from the official firmware using 7zip ZETA STANDARD (not the plain 7zip!!!). C opy the file to the phone (say the download folder)
#4 Install Magisk 24 (not 25, not 22), Magisk 23 may work as well. Use magisk to install itself on the boot.img file (it's your only option since the phone isn't yet rooted), copy the patched file back to your PC, RENAME IT to boot.img, and compress it to boot.tar using 7zip
#5 Use odin, be sure to uncheck the autoreboot option then flash boot.tar, w/o rebooting the phone flash the TRWP recovery (disconnect and reconnect the USB cable before the 2nd flash operation).
Use the old twrp_3.2.3-1_sm-a605_141218.tar (it's buggy, but newer recoveries 3.5.x.x are more buggy, in a different way)
#6 reboot to recovery, format data (I mean FORMAT not just wipe !!!), then reboot to recovery (if you can mount the data partition you are OK for the next step)
#7 Install the lockscreen fix for Pie SM-A605-keymaster-fix-by-Not_Sure.zip (here)
#8 Install Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (not Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip or no-verity-opt-encrypt-6.0.zip as suggested in other threads), don't install other suggested files like "RMM-disable-something")
#9 Reboot to system, and you are almost done
#10 check the lockscreen, if everything is ok, install the magisk 24 apk, and open it (it may ask to do additional configurations and reboot the phone
#11 enjoy your rooted and fully working phone
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Optionally you can flash the latest U8 android 10 w/o having to upgrade your bootloader, to do so you can flash just the system and vendor partitions.
To do so you have to extract them from the AP file from the very latest FW for your phone then recompress the img files to tar (same thing as boot file described in #3 for boot image.
If you do so you need to repeat the above steps starting from #7
The lockscreen fix still works on freshest A10 (tested personally)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
That's all, I hope this help the (few) people who owns this phone.
Click to expand...
Click to collapse
You are amazing.... you did it MASTER.
IEarlyer i also tryed but I gived up.... when I made root I allways lost the encryption the keystore no screenlock etc ... that was unusable.
Another time I was able install working recovery but the system crashed allways. But now its perfect.
The only beauty flaw is the lack of custom roms for a6plus but now I can customize for myself.
Many respect.

Thanks for your kind words

respect and appreciation to you.
You are a true moddfanatic.
Its not about how to keep in use the old phones. Its a passion .
Im the same just lwith mouch less expertion.
Simce You solved this problem I quickly founf the next.
Thr Last 2 -3 ays II spend with a experiment to to open Sansung native callrecder. I tried mouch ways...
all Csc changers
Secret codes
and dparrser mode
wtth activity hacks
with disrcibe files edit
With an apps replacing from customrom.
Wasnnot good .Tomorrow I flash with Odin csc f
So thats what I told ya.
Really I never use this feature !!!!!!
But I can let away I WANT to solve
If a problem prevents you from doing what you imagined, it is unacceptable to us.
caiuse Its about our force in this doddned )mazrix

Will it work in Samsung a605GN?
And what do you mean by 7zip zeta standard?

JulioM18 said:
Will it work in Samsung a605GN?
And what do you mean by 7zip zeta standard?
Click to expand...
Click to collapse
This: https://github.com/mcmilk/7-Zip-zstd/releases
It is a moded version of 7zip with support for Zstandard. You need this to extract the boot.img from the firmware files.
Hope it helps

It works on Samsung A605GN. I just tested IT. Thanks!

The Solutor said:
Hi guys, it's a while since my last post on XDA, but a couple of days ago I got that phone and I started playing with it.
I spent literally one day to figure out how to get the damn thing working. I NEEDED Android 10 (too long to explain why, given I usually stick with the oldest version available)
The problem is that the broken lockscreen is just the tip of the iceberg, with broken biometrics and/or keystore a lot of apps are broken as well (banking apps, billing apps, and also simpler apps that relies on such features (like the current Parallels RDP client)
Long story short, after a lot of reading here and elsewhere looks like no one before me had a fully working A6+ with root and A10, so I accepted the challenge and used a lot of my free time flashing and reflashing and testing, and finally the stubborn thing surrended.
So below is what what you need to do to to have a fixed phone
(I assume you have already unlocked your bootloader)
--------------------------------------------------------------------------------------------------------------------------------------------------------------------
#1 Flash Android 10 with odin (I suggest to use an U5 build, so you can go back to Android 9 (if you want/need to)
#2 Boot the phone once, skip the google account part but connect it to internet once or you will be stick to PRENORMAL condition (and you can't flash anything except official firmwares)
#3 Extract boot.img from the official firmware using 7zip ZETA STANDARD (not the plain 7zip!!!). C opy the file to the phone (say the download folder)
#4 Install Magisk 24 (not 25, not 22), Magisk 23 may work as well. Use magisk to install itself on the boot.img file (it's your only option since the phone isn't yet rooted), copy the patched file back to your PC, RENAME IT to boot.img, and compress it to boot.tar using 7zip
#5 Use odin, be sure to uncheck the autoreboot option then flash boot.tar, w/o rebooting the phone flash the TRWP recovery (disconnect and reconnect the USB cable before the 2nd flash operation).
Use the old twrp_3.2.3-1_sm-a605_141218.tar (it's buggy, but newer recoveries 3.5.x.x are more buggy, in a different way)
#6 reboot to recovery, format data (I mean FORMAT not just wipe !!!), then reboot to recovery (if you can mount the data partition you are OK for the next step)
#7 Install the lockscreen fix for Pie SM-A605-keymaster-fix-by-Not_Sure.zip (here)
#8 Install Disable_Dm-Verity_ForceEncrypt_11.02.2020.zip (not Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip or no-verity-opt-encrypt-6.0.zip as suggested in other threads), don't install other suggested files like "RMM-disable-something")
#9 Reboot to system, and you are almost done
#10 check the lockscreen, if everything is ok, install the magisk 24 apk, and open it (it may ask to do additional configurations and reboot the phone
#11 enjoy your rooted and fully working phone
----------------------------------------------------------------------------------------------------------------------------------------------------------------------
Optionally you can flash the latest U8 android 10 w/o having to upgrade your bootloader, to do so you can flash just the system and vendor partitions.
To do so you have to extract them from the AP file from the very latest FW for your phone then recompress the img files to tar (same thing as boot file described in #3 for boot image.
If you do so you need to repeat the above steps starting from #7
The lockscreen fix still works on freshest A10 (tested personally)
------------------------------------------------------------------------------------------------------------------------------------------------------------------------
That's all, I hope this help the (few) people who owns this phone.
Click to expand...
Click to collapse
It's been so long since this forum was published, and recently I came across it, purely by chance, since I gave up trying to root my A6+ (A605GN). I tried endless tutorials and invested many hours of my time and rest, and here is my reward.
I am totally grateful for giving you the time to explain these steps in detail, and help the community that has this device (still) and can configure it to their liking.
A big hug and blessings. You have saved my life. <3