Related
I developed a flashable zip to help configure dual boot. Zip is designed to be independent of ROM type, version and install method, whether by flashable zip, cloning primary ROM to SD, or in general copying a ROM system image to SD.
Then I overhauled this thread...
Config-Dual-Boot-v1.0-signed.zip: http://www.mediafire.com/?edgat0koyp7d33l
Backs up /sdcard[-ext]/Boot (if it exists) to /sdcard[-ext]/Boot.bak
Creates Boot/ROM1 and Boot/ROM2 directory paths under /sdcard[-ext]
Installs Script Manager on ROM1 and ROM2
Contains shell script “copy-boot.sh” to copy ROM boot partition to boot image file
Contains shell script “boot-rom.sh” to switch to boot ROM2 from ROM1 and vice versa
The updated “boot-rom.sh” script now features generic boot image directory names: Boot/ROM1 and Boot/ROM2, and automatically captures the SD Boot directory path (/sdcard for CM ROMs and /sdcard-ext for Blur ROMs).
Instructions:
1. Boot to ROM1 (emmc)
2. Reboot to CWM and flash: http://www.mediafire.com/?edgat0koyp7d33l . Doing so will backup any existing Boot directory under /sdcard[-ext] and push a new Boot directory containing empty subdirectories ROM1 and ROM2 and two shell scripts: copy-boot.sh (copy boot partition to image file) and boot-rom.sh (boot switcher).
In the following steps, the shell (sh) commands can be run using ADB (Android SDK Platform Tools), Terminal Emulator, Script Manager or other suitable app.
3. Reboot to ROM1
4. Enter: “sh /sdcard[-ext]/Boot/copy-boot.sh”. This detects which ROM is running, ROM1 in this case, and copies its boot image to /sdcard[-ext]/Boot/ROM1
5. Configure Script Manager to execute “sh boot-rom.sh 2” which enables booting to ROM2. But do not run this command until ROM2 “boot.img” is in place. We'll do that now.
6. Reboot to fastboot and connect phone to computer.
7. Enter: “fastboot flash boot boot.img” where boot.img is a boot image file modified to host ROM2 on SD. Please see my Auto-Modify Boot Image thread.
8. Enter: “fastboot reboot"
9. Enter: “sh /sdcard[-ext]/Boot/copy-boot.sh” as in step 4.
10. Configure Script Manager to execute “sh boot-rom.sh 1” which enables booting to ROM1.
More on configuring Script Manager:
Go to Settings > More > Advanced Options > Config > Home Directory. Set home directory to /sdcard/Boot. Then while still in SManager, navigate to /sdcard/Boot and press boot-rom.sh to configure. Valid arguments are:
Code:
blank: Reboot to current ROM
1: Reboot to ROM1 (emmc)
2: Reboot to ROM2 (SD)
3: Reboot to recovery
Press the “Su” box to run as root (note green symbol) and press “Save” at top right. Then press “Run” at top left to launch boot-rom.sh and reboot to the other ROM.
Place shortcut to Script Manager on home screen.
If all goes well, you can now boot ROM2 from ROM1 and vice versa with just a few screen taps.
This procedure was tested working with Neutrino V2.8 EE (CM) on emmc and NottachTrix 1.3.1 ATT (Blur) on SD.
Legacy YouTube video (3:38) showing reboots from one ROM to the other: http://www.youtube.com/watch?v=31TPyAguQ60
Credits
Special thanks to jokersax11, Notorious544d, ATRIXXIRTA, ghost_og, hatefuel19, J-Roc and many others for their technical direction, useful suggestions and encouragement. And of course to the Photon/Atrix/Android dev teams, Koush and https://sites.google.com/site/devwom/
Thanks a lot dude! Im going to try this!
how do you install two roms at the same time? i thought this was showing how to do that but im confused. how do you change the cwm zip installers to .img?
edit:: sorry i thought this was the other thread showing how to install a dual boot system but in fact its how to configure it to boot into them easier. sorry for the mixup ill defiantly read over your 1st thread
Note: Joker recommended as a refinement to place all apps in sdcard to keep apps common to both builds. Good idea.
Click to expand...
Click to collapse
Does this mean that across both on CM7 and CM9, the same apps will be installed? And if you install a new app, it will be seen in both CM7 and CM9?
And is data for apps accessible as well for both CM7 and CM9? So saving a data file with CM9 for example will be saved in /data and when I boot back into CM7, the same data I saved from CM9 will be there in CM7?
Lastly, did you manage to get that dalvik cache thingy working?
That's a lot of questions, but I hope you understand what I'm trying to say.
If it is, then WOW!
Notorious544d said:
Does this mean that across both on CM7 and CM9, the same apps will be installed? And if you install a new app, it will be seen in both CM7 and CM9?
And is data for apps accessible as well for both CM7 and CM9? So saving a data file with CM9 for example will be saved in /data and when I boot back into CM7, the same data I saved from CM9 will be there in CM7?
Lastly, did you manage to get that dalvik cache thingy working?
That's a lot of questions, but I hope you understand what I'm trying to say.
If it is, then WOW!
Click to expand...
Click to collapse
Thanks for the good questions. I haven't yet considered Joker's tip in detail as I spent most of yesterday writing this thread, researching other related topics (and watching Downton Abbey with my beloved wife ). But off the top, I assume that if a given app works on both ROMs, theoretically there should not be a problem hosting it and its corresponding data on the kitchen table (sdcard).
I guess one of the challenging questions is: Are there certain apps for which data should be kept separate to enable ROM-specific customization?
I just updated my thread with this...
"Alternatively (and actually preferred), you can extract the contents of this zip: http://www.mediafire.com/?0kdp4qvy6fv71kp to /sdcard. It makes ROM selections generic, and also fixes a problem with boot-rom.sh (Android shell apparently does not like trailing spaces in script files.) Then drop your boot.img files into /sdcard/Boot/ROM1 and ROM2 and you're good to go."
Cheers.
I developed a flashable zip to help configure dual boot. Zip is designed to be independent of ROM type, version and install method, whether flashable zip, cloning primary ROM to SD, or in general copying a ROM system image to SD.
Then I overhauled this thread...
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 site8 - 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
dear frinds,
i am being unable again and again to install android 4.4.2 on my hp touchpad
here is the process I followed:
1. Install tailor on my touch pad and kept U.S.B media 22 gb
2. downloaded cm-11-20140401-UNOFFICIAL-tenderloin.zip, moboot_038-tenderloin.zip, pa_gapps-stock-4.4.2-20140329-signed.zip, and update-PhilZ_CWM-jcs-dm-tenderloin-20140317.zip and put them in a folder of my pad named cminstall
3. then run acmeinstaller 5 on my laptop
4. at last get this message: unsufficient space available in system partition. you may want to use a smaller Gapps(i.e. mini modular gapps)
....................................................................................................................................................................................................................
*************************************Gapps installation failed**************************************************
unmounting system.........................
aborting................................
E: error in/ storage/ sd card/ cminstall/pa_gapps-stock-4.4.2-20140329-signedzip
(status 7)
installation aborted
after these when I open tailor got this rusult as picture
jonysn2 said:
dear frinds,
i am being unable again and again to install android 4.4.2 on my hp touchpad
here is the process I followed:
1. Install tailor on my touch pad and kept U.S.B media 22 gb
2. downloaded cm-11-20140401-UNOFFICIAL-tenderloin.zip, moboot_038-tenderloin.zip, pa_gapps-stock-4.4.2-20140329-signed.zip, and update-PhilZ_CWM-jcs-dm-tenderloin-20140317.zip and put them in a folder of my pad named cminstall
3. then run acmeinstaller 5 on my laptop
4. at last get this message: unsufficient space available in system partition. you may want to use a smaller Gapps(i.e. mini modular gapps)
....................................................................................................................................................................................................................
*************************************Gapps installation failed**************************************************
unmounting system.........................
aborting................................
E: error in/ storage/ sd card/ cminstall/pa_gapps-stock-4.4.2-20140329-signedzip
(status 7)
installation aborted
after these when I open tailor got this rusult as picture
Click to expand...
Click to collapse
Assuming that you are trying to use a data media Rom the majority of space should be for Android data also acme installer 5 creates a 600 mb Android system partition which is only big enough for PA Gapps mini ,800 is enough for any of the PA Gapps.. You also appear to have a lot of unallocated space, all of which can be changed by going back into webOS and using Taylor again.
Here is how I have mine set up:
USB Media. 1.469 GIB (I couldn't make it smaller)
Android System. 800 MIB
Android Cache. 200 MIB. (Unchanged)
Android Data. 25.086 GIB
Unused. 0
I hope this helps.
sstar said:
Assuming that you are trying to use a data media Rom the majority of space should be for Android data also acme installer 5 creates a 600 mb Android system partition which is only big enough for PA Gapps mini ,800 is enough for any of the PA Gapps.. You also appear to have a lot of unallocated space, all of which can be changed by going back into webOS and using Taylor again.
Here is how I have mine set up:
USB Media. 1.469 GIB (I couldn't make it smaller)
Android System. 800 MIB
Android Cache. 200 MIB. (Unchanged)
Android Data. 25.086 GIB
Unused. 0
I hope this helps.
Click to expand...
Click to collapse
it worked. what should I do now. got a message: install from sd card complete. press any key to continue
try fixing some assert errors
setting will be reset on reboot
sstar said:
Assuming that you are trying to use a data media Rom the majority of space should be for Android data also acme installer 5 creates a 600 mb Android system partition which is only big enough for PA Gapps mini ,800 is enough for any of the PA Gapps.. You also appear to have a lot of unallocated space, all of which can be changed by going back into webOS and using Taylor again.
Here is how I have mine set up:
USB Media. 1.469 GIB (I couldn't make it smaller)
Android System. 800 MIB
Android Cache. 200 MIB. (Unchanged)
Android Data. 25.086 GIB
Unused. 0
I hope this helps.
Click to expand...
Click to collapse
I used JCSullins tp toolbox for the install. Took care of re-sizing and install automatically. What a great tool!
JCSullins Toolbox: Problems!
I installed the JCSullins toolbox on my touchpad. I mounted the media volume, installed the files proposed by jCSullins, then unmounted the volume. Then, when I tried to install "android", the following message appears:
Checking install files...
1 logical volume(s) in volume group "store" now active
No supported recovery file found. Aborting.
What is wrong?
Grettings from Germany,
Matteo2000
What I used.
I did have this problem initially in trying to install evervolv. Using jcs TWRP helped.
Here are the packages I used:
update-TWRP-jcs-dm-tenderloin-20140512.zip
cm-11-20140409-SNAPSHOT-jcsullins-tenderloin.zip
pa_gapps-modular-mini-4.4.2-20140608-signed.zip
Make sure when it loads to do a complete data reset before installing android.
Here is a link that helps walk you through the install:
http://liliputing.com/2014/06/use-touchpad-toolbox-install-android-erase-webos-hp-touchpad.html
gtallmadge said:
I did have this problem initially in trying to install evervolv. Using jcs TWRP helped.
Here are the packages I used:
update-TWRP-jcs-dm-tenderloin-20140512.zip
cm-11-20140409-SNAPSHOT-jcsullins-tenderloin.zip
pa_gapps-modular-mini-4.4.2-20140608-signed.zip
Make sure when it loads to do a complete data reset before installing android.
Here is a link that helps walk you through the install:
I used the same files and instructions but it still says
>>>checking install files...
1 logical volume(s) in volume group "store" now active
No supported ROM file found. Aborting
I don't get it
Click to expand...
Click to collapse
djrolling said:
gtallmadge said:
I did have this problem initially in trying to install evervolv. Using jcs TWRP helped.
Here are the packages I used:
update-TWRP-jcs-dm-tenderloin-20140512.zip
cm-11-20140409-SNAPSHOT-jcsullins-tenderloin.zip
pa_gapps-modular-mini-4.4.2-20140608-signed.zip
Make sure when it loads to do a complete data reset before installing android.
Here is a link that helps walk you through the install:
I used the same files and instructions but it still says
>>>checking install files...
1 logical volume(s) in volume group "store" now active
No supported ROM file found. Aborting
I don't get it
Click to expand...
Click to collapse
I got it....one of my files had been downloaded a couple times and the name had been appended and once I renamed it to its original name it worked
Click to expand...
Click to collapse
djrolling said:
djrolling said:
I got it....one of my files had been downloaded a couple times and the name had been appended and once I renamed it to its original name it worked
Click to expand...
Click to collapse
I had this same problem at first with a ROM I wanted to use. Very picky these linux/android kernels can be with text commands and such.
Click to expand...
Click to collapse
same problem
djrolling said:
djrolling said:
I got it....one of my files had been downloaded a couple times and the name had been appended and once I renamed it to its original name it worked
Click to expand...
Click to collapse
what did you rename it to I am having the same problem
Click to expand...
Click to collapse
Hi,
I upgraded my Android to version 4.4.4 via the updater following these steps (from what I can recall).
1) I downloaded the latest Release version & the latest Gapps files locally to the tablet & went to recovery.
2) I took a backup, wiped Dalvik cache & apply update from sdcard.
3) I ran the Android release build zip file but forgot to run the Gapps zip file.
4) Android upgraded to version 4.4.4 but when I log in I get prompted that 'Unfortunately Google Play Store has stopped' . As I forgot to run the Gapps zip file that is to be expected.
When I boot into recovery it can only see the following directories & not the update folder where the Gapps file was downloaded.
Android
DCIM
LOST.DIR
appdata
clockworkmd
downloads
ringtones
wallpapers
The recovery doesn't seem to be able to see the sdcard & only the internal storage.
However if I copy the Gapps zip file to any of the folders above, boot to recovery again it won't see the zip file.
I also seem to have wiped my backup trying to recovery the situation so can't roll back.
Within the recovery menu I've tried to mount/unmounts the below but it still can't see any of the folders.
Mount /boot
Unmount /cache
Mount /data
Mount /system
unmounts /sdcard
The above is my current settings but I've tried mounting them all.
To complicate the matter further the USB port on the tablet is broken so I can't connect it to my computer.
Previously to transfer files I used a ftp client on my laptop & Wifi File Transfer Pro on the tablet.
I don't know whether to finally give up on my touchpad so any help/advice is much appreciated.
Thanks,
Chip
ChipJnr said:
Hi,
I upgraded my Android to version 4.4.4 via the updater following these steps (from what I can recall).
1) I downloaded the latest Release version & the latest Gapps files locally to the tablet & went to recovery.
2) I took a backup, wiped Dalvik cache & apply update from sdcard.
3) I ran the Android release build zip file but forgot to run the Gapps zip file.
4) Android upgraded to version 4.4.4 but when I log in I get prompted that 'Unfortunately Google Play Store has stopped' . As I forgot to run the Gapps zip file that is to be expected.
When I boot into recovery it can only see the following directories & not the update folder where the Gapps file was downloaded.
Android
DCIM
LOST.DIR
appdata
clockworkmd
downloads
ringtones
wallpapers
The recovery doesn't seem to be able to see the sdcard & only the internal storage.
However if I copy the Gapps zip file to any of the folders above, boot to recovery again it won't see the zip file.
I also seem to have wiped my backup trying to recovery the situation so can't roll back.
Within the recovery menu I've tried to mount/unmounts the below but it still can't see any of the folders.
Mount /boot
Unmount /cache
Mount /data
Mount /system
unmounts /sdcard
The above is my current settings but I've tried mounting them all.
To complicate the matter further the USB port on the tablet is broken so I can't connect it to my computer.
Previously to transfer files I used a ftp client on my laptop & Wifi File Transfer Pro on the tablet.
I don't know whether to finally give up on my touchpad so any help/advice is much appreciated.
Thanks,
Chip
Click to expand...
Click to collapse
Access to the sdcard has to be enabled by the developer. You must have installed one that doesn't (since you didn't specify which it was)
shumash said:
Access to the sdcard has to be enabled by the developer. You must have installed one that doesn't (since you didn't specify which it was)
Click to expand...
Click to collapse
Here is the build info currently on the tablet.
Kernel Version:
3.4.82-tenderloin
Mod Version:
ev_ternderloin=testing-2015.01.22
Build number:
ev_tenerloin-eng 4.4.4 KTU84Q eng.flintman.20150122.215911 test-keys
If this build doesn't recognise the sdcard, should it not recognise the Gapps zip file on the internal storage?
There is 1.4GB in total on the internal storage with 388MB free.
Do you know if there is anyway I could get a build of Android & Gapps on the tablet & upgrade to that?
Thanks for responding to the thread.
ChipJnr said:
Here is the build info currently on the tablet.
Kernel Version:
3.4.82-tenderloin
Mod Version:
ev_ternderloin=testing-2015.01.22
Build number:
ev_tenerloin-eng 4.4.4 KTU84Q eng.flintman.20150122.215911 test-keys
If this build doesn't recognise the sdcard, should it not recognise the Gapps zip file on the internal storage?
There is 1.4GB in total on the internal storage with 388MB free.
Do you know if there is anyway I could get a build of Android & Gapps on the tablet & upgrade to that?
Thanks for responding to the thread.
Click to expand...
Click to collapse
I doubt you've used the latest and proper way to install 4.4/5.0 ROM's. Go here. Start over and follow the instructions to the letter. Read everything first and decide how you want to proceed before doing anything.
Hi All,
***MIUI 8 is now operational on our TCL_S960!
I managed to get it running on TCL S960 (IDOL X+),
Here's my work... (I am not a developer but I followed some instructions online and was able to make it at least for me...)
Probably there will be bugs - so let me know
I'll try to fix what I know...
If you want to use my work elsewhere, you must request in advance and make sure that credits goes to the correct people....
Supported Languages:
All languages that are supported by Xiaomi.EU roms.
Credits:
Xiaomi.eu - for the translations and guides.
Latest version Download links:
Android File Host: (WIP)...
30/Jul/2016 -
Older Versions (Miui8)
24/Jul/2016 (fixes to 14/7/2016) - https://www.androidfilehost.com/?fid=24651429356503158
14/Jul/2016 - https://www.androidfilehost.com/?fid=24591000424947416
7/7/2016 - https://www.androidfilehost.com/?fid=24591020540823614
30/6/2016 - https://www.androidfilehost.com/?fid=24591020540823614
Older Versions (MIUI7):
26/5/2016 - https://www.androidfilehost.com/?fid=24566454284190288
19/5/2016 - https://www.androidfilehost.com/?fid=24533103863143479
12/05/2016 - https://www.androidfilehost.com/?fid=24533103863139453
05/05/2016 - https://www.androidfilehost.com/?fid=24533103863137243
28/4/2016 - https://www.androidfilehost.com/?fid=4996500813288309006
14/4/2016 - https://www.androidfilehost.com/?fid=24499762636000772
7/4/2016 - https://www.androidfilehost.com/?fid=24459283995317117
31/3/2016 - https://www.androidfilehost.com/?fid=24459283995310311
17/3/2016 - https://www.androidfilehost.com/?fid=24459283995303903
XdaDevDB:
Installations:
Important:
Prior to any install make sure to backup your existing ROM. (TWRP backup?) if you wish to backup your SMS/Contacts there are a bunch of apps that can do it... (MobilePro is an example)
Backup your IMEI just in case... (Use MobileUncle or similar)
If you chose to install - your warranty is void.
I am not responsible for any damage that may be caused by this ROM.
Did you make a backup? - Save your backup on a PC...
First time transition to MIUI8 requires re-partition of the phone to increase system size.
you will need a different recovery to finalise the process.
1. Copy the Repartition zip file to phone.
2. Copy the Philz recovery to your phone.
3. Install Philz recovery.
4. Reboot into recovery
5. Install Re-partition zip (It will take several minutes - it needs to format the partitions)
6. if format is not running - reboot to recovery and manually format the partitions (System, Data, Cache). - DO NOT FORMAT other partitions.
6.a. - check to see where the SDCARD data directory is mounted(data or data), if it is the data - change it back to data in the philz recovery, otherwise - upgrades will not work in TWRP.
7. using SP-Flash tools or another way, install the TWRP 2.8.7 recovery again.
8. Restore your backup.
9. Boot the phone.
10. Copy the MIUI8 install file to phone.
11. Click on the 3 dots
12. Chose select update file --> select your copied file.
13. Phone will Reboot and install.
If the above version does not work, you will need to use SP-Flash tools to install the EBR1, EBR2 files in the zip.
Then continue from step 6 (Format partitions)
if coming from another rom/ Fresh install
as ususal... - I recomend a total wipe, but it is not a must....
Wipe Cache, Dalvik, Data, System, custpack.
Install Rom from internal memory
reboot.
Wait patiently - it will take 3-4 minutes on the 1st boot.
To update (existing Miui Rom):
Copy rom to SD Card
Open updater app.
Click on the 3 dots
Chose select update file --> select your copied file.
Reboot
*** Make sure to disable Automated OTA... as it is based on Redmi Note 3G MTK, and I can't promise to keep this forever...
Recovery:
I used TWRP 2.8.7.0 for TCL S960
Other recoveries:
CWM - Link
TWRP 2.6.3 - Link
If you like my work feel free to buy me beer Donation link
Known Issues:
Default theme - some icons are missing - Use another theme icon set...
When making full wipe - unable to login to MiAccount - Install 6.1.28 version --> login, then update to latest.
TouchAssistant APK exceeds the space of System partition - I removed it, you can install it manually after the rom installs. - Link solved after repartition.
31/3/16 - Additional settings FC - Fixed.
12/05/2016 - Fixed wallpaper carousel FC when unlocking device
Some screenshots:
Miui8:
{
"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"
}
Miui7:
XDA:DevDB Information
TCL S960/Alcatel (IdolX+), ROM for the Android General
Contributors
hellfreezover, Xiaomi.eu
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: MIUI
Version Information
Status: Beta
Current Beta Version: 26-05-2016
Beta Release Date: 2016-07-15
Created 2016-01-22
Last Updated 2016-07-30
Reserved
Changelog: (Latest Version)
24/7/2016 - still based on 6.7.14
Fixed Settings menus.
Enabled "Button mode"
Enabled additional settings to split the menu bar.
Fixed MIUI version to 8...
System seems to be running faster...
Older versions:
14/7/2016
System
Fix - Fingerprint issues (07-12)
Fix - Fingerprint scanner made the device freeze and reboot (07-12)
Lockscreen, Status Bar, Notification Bar
Optimization - Clickable arrow for Wi-Fi (07-12)
Optimization - A prompt about entering password and activating fingerprint after rebooting the device (07-13)
Fix - Customized carrier name isn't shown in Second space (07-12)
Home screen
Optimization - Landscape mode for Task manager (07-08)
Optimization - Task Manager stability (07-13)
Fix - Issues with wallpaper when switching to Second space (07-13)
Delete - Home screen Music widget (07-13)
Gallery
New - Delete directly from the screenshot preview page (07-12)
Optimization - Adjusted size for the button which creates new albums (07-12)
Optimization - "Show original" option appears only on cloud or optimized items (07-12)
Optimization - Double tap to zoom in, swipe up without entering sharing mode (07-12)
Optimization - When auto-rotate is off in Gallery, it won't influence the rest of the system (07-13)
Fix - Scrolling screenshot issues in Notes and Mail (07-12)
Fix - Couldn't go back to the original photo after making a screenshot or finishing editing/sharing it (07-12)
Fix - Couldn't pick up calls while making Scrolling screenshots (07-13)
Fix - Enter system app while editing a scrolling screenshot in the OOB flow (07-13)
Delete - Removed Edit option for GIF images (07-12)
Weather
Fix - Issues with curves in forecasts (07-13)
Optimization - Set C/F in settings (07-13)
7/7/2016
Highlights
New - Saved and available Wi-Fi networks appear first in the list (07-05)
New - After a permission is restricted, a clickable notification is sent to the user which can restore permissions (07-05)
Lock Screen, Status Bar, Notification Bar
New - Animation of WiFi connection (07-07)
Optimization - separate "Ringtone and Vibration" permission in Notification （07-07）
Fix - Switching notification bar style in landscape view issues (07-07)
Fix - In Second Space, enter Mi Home in lock Screen issue (07-07)
Desktop
Optimization - Restore app uninstallation sound effect (07-07)
Fix - Recent app tray, long press to enter wrong app info page issue (07-07)
Fix - Recent app tray, switching view mode issues (07-07)
Settings
New - Saved and available Wi-Fi networks appear first in the list (07-05)
Clock / Calculator
Optimization - "Shutdown alarm", "Set default alarm sound" moved up In Clock settings. (07-01).
30/6/2016 - Miui 8.
26/5/2016 -
Gallery
New - Deleting synced photos from internal storage without deleting from Mi Cloud (05-25)
Cleaner
Optimization - Accessibility support (05-24)
Fix - FC issues (05-24)
19/05/2016 -
System
Optimization - Background CPU processes caused performance issues (05-16)
Optimization - Delayed response for charger's notifications (05-19)
Fix - Wireless display caused reboots (05-19)
Fix - Read mode appeared more red than it should be (05-19)
Fix - Draining battery while using GPS in some cases (05-19)
Fix - Bluetooth turned on automatically with the device (05-19)
Settings
New - Introducing Shortcut menu. Check out the new MIUI 8 feature early. You can turn it on in Additional settings. (05-17)
TouchAssistant must be installed post rom.
Mi Cloud
New - Added "Back up now" feature for fast backups (05-19)
12/05/2016 -
System
Optimization - System storage UI (05-05)
Optimization - Background processes kept CPU busy and lead to performance issues (05-09)
Fix - Issues with adding fingerprint (05-05)
Fix - Problems with sound when listening to some songs using earphones (05-05)
Fix - Issues with video chats in some cases (05-05)
Fix - Sound disappeared in long phone conversations (05-05)
Fix - Fingerprint unlock didn't respond in some cases (05-05)
Backup
New - Optimizing transferring rate in File Transfer (05-09)
05/05/2016 -
System
Optimization - System storage UI (05-05)
Fix - Issues with adding fingerprint (05-05)
Fix - Problems with sound when listening to some songs using earphones (05-05)
Fix - Issues with video chats in some cases (05-05)
Fix - Sound disappeared in long phone conversations (05-05)
Fix - Fingerprint unlock didn't respond in some cases (05-05)
Security
New - Added on/off switch for App lock (05-03)
New - Customized settings for App lock (05-03)
28/4/2016 -
System
Optimisation - Improved speed and performance for devices which have been used for a long time (04-27)
Weather
New - New white design (04-27)
Cleaner
New - New design for Cleaner (04-27)
Gallery
New - Progress list for syncing with Mi Cloud (04-27)
Optimization - Added a prompt notifying about Mi Cloud trash bin when deleting photos for the first time (04-27)
Optimization - Improved sharpness for big photos (04-27)
Security
New - Fingerprint support for App lock in Redmi 3 Pro (04-27)
14/4/2016 -
System
Optimization - Improved algorithms for Silent and DND modes to be used at the same time. (04-13)
Fix - Storage leaks lead to performance problems (04-08)
Fix - Security Center FC in Hebrew Language
7/4/2016 -
Lockscreen, Status Bar, Notification Bar
Optimization - Improved order of switches in notification shade (04-06)
Fix - Music lock screen appeared when a game was running in the background (04-06)
Settings
Optimization - Improved algorithms for international roaming (04-06)
Mi Account
New - Added more items to personal info (04-06)
Cleaner
Optimization - Press and hold to add items to exceptions (04-06)
Optimization - Fixed problems with performance after clean-ups (04-06)
Mi Cloud
Fix - Couldn't find device or sign in to Mi Account due to wrong system time (04-06)
Fix - Fixed issues with incorrect time in backup lists (04-06)
Bug fixes by Xiaomi.
Fixed Additional settings FC.
31/3/2016 general bug fixes by Xiaomi.
24/3/2016
System
Optimization - Apps open faster, system animations work smoother (03-17)
Optimization - Increased image processing speed for image decryption database (03-22)
Fix - Problems with performance after switching from mobile data to Wi-Fi (03-18)
Backup
In some cases Mi Mover stopped working after the connection was established (03-18)
Clock / Calculator
New - Option for deleting an alarm automatically after it was used if it had been set to go off only once (03-23)
thank you
thank you for this awesome Rom. but the sound setting under audio force closes im on viper4android
Did you try sound settings without viper?
For me it works... but I did had to do a clean install...
Sent from my ASUS_Z00XS using XDA Free mobile app
Hi i just tried your rom bt i am stuck at mi login.. It says checking find device status and stays there only.... What to do now...?
santhosh5639 said:
Hi i just tried your rom bt i am stuck at mi login.. It says checking find device status and stays there only.... What to do now...?
Click to expand...
Click to collapse
Try using an older version like 6.1.28, then log in to miui, then update without full wipe.
I have reported this to miui, it is under discussion...
Sent from my ASUS_Z00XS using XDA Free mobile app
Updated OP with the link to 6.1.28 version
Sent from my ASUS_Z00XS using XDA Free mobile app
Updated OP with MIUI 8 for TCL.
Sent from my ASUS_Z00XS using XDA Free mobile app
Bricking my phone
Dear Hellfreezover,
I tried to install your ROM, but I bricked my phone.
(I installed ROM before several times, I never made mistake, but now I did it.)
When I used SP flashtool I selected "Firmware upgrade" option instead of "Download only" option (I never did it before) and I started to install TWRP recovery but I got error message.
Now I can not use my phone, but I know that I can be repairable just I need important files....
...these all files or just some of them:
- PRELOADER
-MBC
-EBR1
-UBOOT
-BOOTIMG
-RECOVERY
-SEC-RO
-LOGO
-EBR2
-CUSTPACK
-MOBILE_INFO
-ANDROID
-CACHE
-USRDATA
Now I get this error message when I try to update the recovery.
Could u send me these files? Or could you link me URL where I can find these files?
Sorry for disturbing, I shame on me, I did ROM install before without mistake, but now I screwed up...
Regards,
Peter (Hungary)
I am not at home now,
I have the files...
You can get searching TCL multi language rom 70 languages and download it through SP flash tools, then, repartition and finally the rest....
Sent from my ASUS_Z00XS using XDA Free mobile app
Olympos.81 said:
Dear Hellfreezover,
I tried to install your ROM, but I bricked my phone.
(I installed ROM before several times, I never made mistake, but now I did it.)
When I used SP flashtool I selected "Firmware upgrade" option instead of "Download only" option (I never did it before) and I started to install TWRP recovery but I got error message.
Now I can not use my phone, but I know that I can be repairable just I need important files....
...these all files or just some of them:
- PRELOADER
-MBC
-EBR1
-UBOOT
-BOOTIMG
-RECOVERY
-SEC-RO
-LOGO
-EBR2
-CUSTPACK
-MOBILE_INFO
-ANDROID
-CACHE
-USRDATA
Now I get this error message when I try to update the recovery.
Could u send me these files? Or could you link me URL where I can find these files?
Sorry for disturbing, I shame on me, I did ROM install before without mistake, but now I screwed up...
Regards,
Peter (Hungary)
Click to expand...
Click to collapse
Check your PM - I sent you a link with all files needed...
Updating problem
hellfreezover said:
Check your PM - I sent you a link with all files needed...
Click to expand...
Click to collapse
Thank you very much, I could unbrick my mobile! :good: :fingers-crossed: :highfive:
I tried to upgrade my ROM according to your instructions, but I could not do it.
What I did:
1. Unbrick my mobile with your files.
2. I copied your MIUI8 ROM, Repartition and Philz zip files to my mobile.
3. In SP Flash I downloaded Philz.zip what contains recovery.
4. I rebooted my mobile in recovery mode.
5. I installed the Repartition zip. (...but I think it was unnecessary, because I did it when I unbricked my mobile.)
6. I tried to reboot my mobile into reocvery mode, but it was not available (after repartition.)
7. I had to download your TWRP 2.8.7.0 recovery to my mobile via SP-Flash tool.
8. I tried to reboot, but same situation: this recovery also was not available.
9. I had to download other 2.6.3 or 2.7.0 TWRP recovery to my mobile.
10. I could reach recovery from that point.
11. I installed your MIUI 8 rom, and it was successful according to message.
12. In spite fo this the ROM can not start: "Idol X+" is appearing and go away and black screen is flashing without logo or sound.
What do I do in wrong way?
Otherway, before I unbricked my mobile and after also I tried to upgrade my ROM to your MIUI 8 version in different way.
Then I had different problem: when I did the uploading of your ROM into my exist differnet rom (like offical ROM, LeWa ROM or modded MIUI 5 rom) in recovery mode the installation was finally failed, unsuccessful: "/data" directory can not reachable/readable/writeable or somehting else.
(I have screenshot, I will share.)
Regards,
Peter
Olympos.81 said:
Thank you very much, I could unbrick my mobile! :good: :fingers-crossed: :highfive:
I tried to upgrade my ROM according to your instructions, but I could not do it.
What I did:
1. Unbrick my mobile with your files.
2. I copied your MIUI8 ROM, Repartition and Philz zip files to my mobile.
3. In SP Flash I downloaded Philz.zip what contains recovery.
4. I rebooted my mobile in recovery mode.
5. I installed the Repartition zip. (...but I think it was unnecessary, because I did it when I unbricked my mobile.)
6. I tried to reboot my mobile into reocvery mode, but it was not available (after repartition.)
7. I had to download your TWRP 2.8.7.0 recovery to my mobile via SP-Flash tool.
8. I tried to reboot, but same situation: this recovery also was not available.
9. I had to download other 2.6.3 or 2.7.0 TWRP recovery to my mobile.
10. I could reach recovery from that point.
11. I installed your MIUI 8 rom, and it was successful according to message.
12. In spite fo this the ROM can not start: "Idol X+" is appearing and go away and black screen is flashing without logo or sound.
What do I do in wrong way?
Otherway, before I unbricked my mobile and after also I tried to upgrade my ROM to your MIUI 8 version in different way.
Then I had different problem: when I did the uploading of your ROM into my exist differnet rom (like offical ROM, LeWa ROM or modded MIUI 5 rom) in recovery mode the installation was finally failed, unsuccessful: "/data" directory can not reachable/readable/writeable or somehting else.
(I have screenshot, I will share.)
Regards,
Peter
Click to expand...
Click to collapse
Hi,
I think what you missed is the format of system, data, cache - after the installation of re partition, in Philz recovery.
also - you need to verify that your SD-Data is mounted correctly (sometimes in Philz it adds a 0, and then you will not find files there...
You need to change the mount location before you reboot recovery.
Sorry I have no pictures for this, but it is in the menu...
if the above does not work
Try extracting EBR1, EBR2 from repartition file, install them with Philz recovery through SP-Flash tool.
reboot into recovery --> format data, system, cache - check again where SD is mounted...
Reboot recovery
Install rom - if works great if not:
Install TWRP 2.8.7
Place new ROM and install
let me know if this works for you.
The 1st install will take a few minutes until you will see something on the phone...
hellfreezover said:
Hi,
I think what you missed is the format of system, data, cache - after the installation of re partition, in Philz recovery.
also - you need to verify that your SD-Data is mounted correctly (sometimes in Philz it adds a 0, and then you will not find files there...
You need to change the mount location before you reboot recovery.
Sorry I have no pictures for this, but it is in the menu...
if the above does not work
Try extracting EBR1, EBR2 from repartition file, install them with Philz recovery through SP-Flash tool.
reboot into recovery --> format data, system, cache - check again where SD is mounted...
Reboot recovery
Install rom - if works great if not:
Install TWRP 2.8.7
Place new ROM and install
let me know if this works for you.
The 1st install will take a few minutes until you will see something on the phone...
Click to expand...
Click to collapse
Yes, u have right: during procedure, before I would install the MIUI 8 rom in TWRP 2.8.7.0 the SD-DATA is unmounted, internal storage is 0.
What can I do to reach it again?
---------- Post added at 05:49 PM ---------- Previous post was at 05:02 PM ----------
Olympos.81 said:
Yes, u have right: during procedure, before I would install the MIUI 8 rom in TWRP 2.8.7.0 the SD-DATA is unmounted, internal storage is 0.
What can I do to reach it again?
Click to expand...
Click to collapse
My problem is now:
/E: Unable to mount '/system'
/E: Unable to mount '/protect_s'
/E: Unable to mount '/protect_f'
Olympos.81 said:
Yes, u have right: during procedure, before I would install the MIUI 8 rom in TWRP 2.8.7.0 the SD-DATA is unmounted, internal storage is 0.
What can I do to reach it again?
---------- Post added at 05:49 PM ---------- Previous post was at 05:02 PM ----------
My problem is now:
/E: Unable to mount '/system'
/E: Unable to mount '/protect_s'
/E: Unable to mount '/protect_f'
Click to expand...
Click to collapse
you can change the mount location in Philz recovery...
6.a. - check to see where the SDCARD data directory is mounted(\data or \data\0), if it is the \data\0 - change it back to \data in the philz recovery, otherwise - upgrades will not work in TWRP.
I followed your instruction, please see my notes and check my pictures:
1. Copy the Repartition zip file to phone.
OK!
2. Copy the Philz recovery to your phone.
OK!
Please see it, I copied everything to my phone from Window 10, so these files copied into /data directory:
http://kepfeltoltes.hu/160717/factory_directory_www.kepfeltoltes.hu_.jpg
3. Install Philz recovery.
I did it from factory recovery:
http://kepfeltoltes.hu/160717/IMG_1596_www.kepfeltoltes.hu_.jpg
(You can not see the "Philz*.zip" file because of bad quality of picture, but belive me, it is.
4. Reboot into recovery
OK!
5. Install Re-partition zip (It will take several minutes - it needs to format the partitions)
I did it:
http://kepfeltoltes.hu/160717/IMG_1597_www.kepfeltoltes.hu_.jpg
6. if format is not running - reboot to recovery and manually format the partitions (System, Data, Cache). - DO NOT FORMAT other partitions.
6.a. - check to see where the SDCARD data directory is mounted(data or data), if it is the data - change it back to data in the philz recovery, otherwise - upgrades will not work in TWRP.
I did not need the format, because your Repartition.zip was installed successfully, and format was done by Repartition.zip as you requested:
Begin:
http://kepfeltoltes.hu/160717/IMG_1598_www.kepfeltoltes.hu_.jpg
End:
http://kepfeltoltes.hu/160717/IMG_1599_www.kepfeltoltes.hu_.jpg
7. using SP-Flash tools or another way, install the TWRP 2.8.7 recovery again.
Because of your Repartition procedure all files were deleted from /data directory so I had to upload TWRP 2.8.7.0 recovery from SP-Flash tool to mobile:
http://kepfeltoltes.hu/160717/Recovery_www.kepfeltoltes.hu_.jpg
8. Restore your backup.
(I do not know what is it...maybe I make a mistake here. I skiped this step.)
9. Boot the phone.
OK.
10. Copy the MIUI8 install file to phone.
Negative. There is no operation system, because Repartition.zip formatted /data and /system directory.
Furthermore, Internal storage is 0 from the Repartition.zip is completed.
http://kepfeltoltes.hu/160717/IMG_1603_www.kepfeltoltes.hu_.jpg
11. Click on the 3 dots
Negative.
12. Chose select update file --> select your copied file.
I had to use OTG-USB cable and chose the MIUI 8 rom in TWRP 2.8.7.0
But from now due to unavailable /data, /cache / etc - internalt storage is 0 - the installation however started, but failed.
Begin:
http://kepfeltoltes.hu/160717/IMG_1604_www.kepfeltoltes.hu_.jpg
End:
http://kepfeltoltes.hu/160717/IMG_1605_www.kepfeltoltes.hu_.jpg
13. Phone will Reboot and install.
Negative.
Where do I make mistake?
Olympos.81 said:
I followed your instruction, please see my notes and check my pictures:
1. Copy the Repartition zip file to phone.
OK!
2. Copy the Philz recovery to your phone.
OK!
Please see it, I copied everything to my phone from Window 10, so these files copied into /data directory:
http://kepfeltoltes.hu/160717/factory_directory_www.kepfeltoltes.hu_.jpg
3. Install Philz recovery.
I did it from factory recovery:
http://kepfeltoltes.hu/160717/IMG_1596_www.kepfeltoltes.hu_.jpg
(You can not see the "Philz*.zip" file because of bad quality of picture, but belive me, it is.
4. Reboot into recovery
OK!
5. Install Re-partition zip (It will take several minutes - it needs to format the partitions)
I did it:
http://kepfeltoltes.hu/160717/IMG_1597_www.kepfeltoltes.hu_.jpg
6. if format is not running - reboot to recovery and manually format the partitions (System, Data, Cache). - DO NOT FORMAT other partitions.
6.a. - check to see where the SDCARD data directory is mounted(data or data), if it is the data - change it back to data in the philz recovery, otherwise - upgrades will not work in TWRP.
I did not need the format, because your Repartition.zip was installed successfully, and format was done by Repartition.zip as you requested:
Begin:
http://kepfeltoltes.hu/160717/IMG_1598_www.kepfeltoltes.hu_.jpg
End:
http://kepfeltoltes.hu/160717/IMG_1599_www.kepfeltoltes.hu_.jpg
7. using SP-Flash tools or another way, install the TWRP 2.8.7 recovery again.
Because of your Repartition procedure all files were deleted from /data directory so I had to upload TWRP 2.8.7.0 recovery from SP-Flash tool to mobile:
http://kepfeltoltes.hu/160717/Recovery_www.kepfeltoltes.hu_.jpg
8. Restore your backup.
(I do not know what is it...maybe I make a mistake here. I skiped this step.)
9. Boot the phone.
OK.
10. Copy the MIUI8 install file to phone.
Negative. There is no operation system, because Repartition.zip formatted /data and /system directory.
Furthermore, Internal storage is 0 from the Repartition.zip is completed.
http://kepfeltoltes.hu/160717/IMG_1603_www.kepfeltoltes.hu_.jpg
11. Click on the 3 dots
Negative.
12. Chose select update file --> select your copied file.
I had to use OTG-USB cable and chose the MIUI 8 rom in TWRP 2.8.7.0
But from now due to unavailable /data, /cache / etc - internalt storage is 0 - the installation however started, but failed.
Begin:
http://kepfeltoltes.hu/160717/IMG_1604_www.kepfeltoltes.hu_.jpg
End:
http://kepfeltoltes.hu/160717/IMG_1605_www.kepfeltoltes.hu_.jpg
13. Phone will Reboot and install.
Negative.
Where do I make mistake?
Click to expand...
Click to collapse
First you missed your previous MIUI backup...
but that is not the issue...
I would recommend formatting the /system, /data, /cache partitions - even though that it shoes success...
Then reboot recovery (to PHILZ)
Make sure your SDCARD mount is without the "0"...
Try to flash ROM using ADB sideload, in PHILZ touch...
if it doesn't work, try installing with TWRP 2.6.3 recovery.
I shared what I did on my phone and it worked...
If all the above fails - try installing EBR1, EBR2 from SP-Flash tool, then Recovery (Philz), Format cache, system, data, then install rom through PHILZ or TWRP...
Somebody could install this rom as Hellfreezover described?
---------- Post added at 09:23 PM ---------- Previous post was at 09:05 PM ----------
hellfreezover said:
First you missed your previous MIUI backup...
but that is not the issue...
I would recommend formatting the /system, /data, /cache partitions - even though that it shoes success...
Then reboot recovery (to PHILZ)
Make sure your SDCARD mount is without the "0"...
Try to flash ROM using ADB sideload, in PHILZ touch...
if it doesn't work, try installing with TWRP 2.6.3 recovery.
I shared what I did on my phone and it worked...
If all the above fails - try installing EBR1, EBR2 from SP-Flash tool, then Recovery (Philz), Format cache, system, data, then install rom through PHILZ or TWRP...
Click to expand...
Click to collapse
Dear Hellfreezover!
I am sure, that you are advanced or professional developer and you have more experience about mobiles and ROMS, but now, I think what you have written in instructions is different as you have done it in real life.
...or someting is wrong with ROMs.
So...
I tried to follow your instruction several times and when I have reached that point that there were no error message at the beginning of installation of ROM, finally, it was also unsucessfull:
- begining: http://kepfeltoltes.hu/160717/IMG_1592_www.kepfeltoltes.hu_.jpg
- ending: http://kepfeltoltes.hu/160717/IMG_1593_www.kepfeltoltes.hu_.jpg
(See, there is no error message as before like "unmount /data" or somthing else...)
I am hardly a professional....
I used philz, and my files the way I described...
There may be some issues, I had miui Rom installed before...
And there is another guy that did the repartition process... using SP flash tools...
You can try maybe replacing the EBR1, EBR2 in the original Rom and choose firmware update....
Then install the twrp recovery and the Rom...
hellfreezover said:
I am hardly a professional....
I used philz, and my files the way I described...
There may be some issues, I had miui Rom installed before...
And there is another guy that did the repartition process... using SP flash tools...
You can try maybe replacing the EBR1, EBR2 in the original Rom and choose firmware update....
Then install the twrp recovery and the Rom...
Click to expand...
Click to collapse
Now I tried again and again, I followed again your every intsructions and I tried the following ROMs with TWRP 2.6.3.0:
- xiaomi.eu_multi_TCL_S960_6.7.14_v8-4.4 (latest) - Failed
- xiaomi.eu_multi_TCL_S960_6.6.30_v8-4.4 (previous) - Failed
- xiaomi.eu_multi_TCL_S960_6.3.10_v7-4.4 - Success!
Now, the MIUI 7 is running.
I am trying to upgrade to latest MIUI 7 and after to MIUI 8....
...but I am afraid: this will be again failed.