Related
UMT - Ultimate Multi Tools
For HTC Android Devices (Desire HD First)
Changes / Improvements:
Code:
Release 2.5.0 to 2.5.12
-------------------------------
-Update Android SDK link in config file
-Fix Error with ROM Cleaner when try to retrieve Picture Application
-Update Titanium Backup APK file
-Update ROM Manager APK file
-Added Italian language (Thanks antonaq)
-Added Turkish language (Thanks TheNorth)
-Update APK ROM Manager (v4.5.0.1) & Titanium Backup (v4.4.0)
-Minors bugs fixed
-Increase 5 to 10 seconds when exit UMT. Please donate if you use and appreciate my work.
-When Downgrade, now, device do not reboot
-Downgrade: Added a wait time of 10 seconds if file is present (to resolve failed push)
-Added Dutch Language (Thanks sparkienl)
-Minors changes
Release 2.4.0 to 2.4.6
-------------------------------
-This update is necessary to update 2.5.0!
-Fix bug Startup since 2.4.2 update
-Update Titanium Backup
-Update ROM Manager
-UMT turn now on Unique Instance
Release 2.3.0 to 2.3.10
-------------------------------
-Added External program to MD5 Checksum with Explorer
-Fix MD5 Checksum
-Added Shell Explorer "UMT MD5 Checksum"
-Remove button to check MD5. Automatically checksum MD5 when file loaded
-Added new function "MD5 Checksum"
-Fix MD5 Message Failed when Downgrade Desire Z devices
-Enable Flash Radio for all HTC Vision (G2 & Desire Z)
-Temproot Gingerbread install Superuser & TitaniumBackup
-Possible to clean Debug Log
Release 2.2.0 to 2.2.6
-------------------------------
-Flash Radio enable for HTC Desire Z & G2 (Vision) devices
-HTC Desire S is now recognized
-Flash HBOOT & S-OFF function activated for Desire Z & T-Mobile G2
-For Desire Z only: To S-OFF device, function has moved to "Flash HBOOT (ENG S-OFF)"
-HTC Desire Z (Vision) function S-OFF enabled. This function flash HBOOT and recovery. Only Vision Europe (don't use if you have G2)
Release 2.1.0 to 2.1.18
--------------------------------
-Added language "persian" (Thanks ocz_ocz_ocz)
-Temproot HTC Desire Z (Vision) is now available
-Fix Downgrade HTC Desire Z (Vision)
-Fix and update code of Temproot Gingerbread
-When downgrade fails, retry once UMT
-HTC Desire Z (vision) Downgrade 2.x enabled
-Disable Flash HBOOT Desire Z (vision). Will enable in future...
-Downgrade for "HTC Desire Z" (vision) is now possible
-Fix HBOOT for Desire devices
-Flash HBOOT is now possible on HTC Desire (bravo). HBOOT image is the Alpharev HBOOT (bravo_alphaspl.img)
-Fix List of directories ROM Clean
-Fix Anchor ROM Clean
-Modifying ROM Clean: You can choose directory where APK are added in CWM ROM
-Fix Error when you start and close "ROM Clean" immediatly
-Added German Language (Thanks hoppkins)
-Added Spanish Language (Thanks wyattcold)
-Fix S-OFF in "Restauration SFR" (French Only)
-Update code "Restauration SFR" (French only)
-Now, all Window start on Top Left
-Remove "adb restart routine" when closing window in UMT
-Update Languages Files (Russian & English) Thanks abZorber
Release 2.0.0 to 2.0.22
--------------------------------
-When bootanimation finished, UMT Status change correctly
-Fix Languages Error
-Fix Error on Start bootanimation
-Added "Change Bootanimation" function
-Enable Slashscreen Changer for "Desire" and "Desire Z"
-Add Close Action in Debug Log
-Disable button when Splachscreen started
-Added function "Change Splashscreen"
-Minors Changes graphicals
-Added differents devices recognition
-Added HTC Sensation compatibility in Flash Radio
-Added functions for HTC Desire Z devices
-Added confirm box on "Install APK"
-Add "Waiting Device" when PD98IMG.zip is already download to fix Downgrade
-The language change is no longer restart the application
-The language list is now displayed
-Fix Police size in window About
-Hide Popup when language changed
-Fix Exception error when GoldCard opening
-Fix translation GoldCard
Make sure you have .NET Framework 4.0 installed
If you have UMT 1.x.x, please uninstall first and Remove folder "Ultimate Multi Tool" in "Program Files" folder
Application Capabilities:
- Auto Update-Tool
- MUlti-language Support
- ROM Cleaner
- Android SDK installation (with auto-update PATH variable)
- GoldCard Tool
- Change Boot animation
- Change Splashscreen
- Check your getprop
- Install HBOOT drivers
- Radio S-OFF
- Reboot Mode
- Flash ENG HBOOT (S-OFF)
- Flash Recovery
- Auto Flash Radio Capability (All radios are stocked in a private server) Compatibility "Desire, Desire HD & Incredible S"
- SIM UnLock
- Change CID
- Set Super CID
- Install APK Packages
- Auto Detection Capability
- Auto Downgrade Capability
- Auto Logging for debug
To make sure everything works correctly, make sure you do the following on your device:
- HTC Sync installed
- Enable USB Debugging.
- Disable Fast Boot.
- Enable Unknown Sources in Application Settings.
- Connect Device in 'Charge Only' mode.
All credits for used tools in this tool go to their respective authors
Developped in C#
Download Link : Download Ultimate Multi Tool (18,64 Mo)
MD5: 1A924F3E928ED0E89EF8490BC0CD0BCA
Download Link : Download Ultimate Multi Tool - Code Source (17,02 Mo)
Screenshots are in French but this tool is translate French & English
Sorry if translate is not perfect: Report me suggestions
Thanks to Developpers: gfree, psneuter, GingerBreak, wpthis, visionary+, gfree_verify, fre3vo
Chainfire, CuBz90, paulobrien, jkoljo and All others I forget (sorry, you could tell me if I forgot to mention)
How To "root" and install "ROM Custom" with Ultimate Multi Tool
Follow the instructions:
Create a goldcard if your device is branded
Launch a Downgrade
Install visionary+ (In visionary+, launch "Temproot", and "Atempt Perm root"). Your device is now rooted!
Launch S-OFF/Super CID/SIM Unlock
Install ROM Manager (In ROM Manager, flash recovery)
Flash HBOOT
You can install a ROM Custom
Video to Downgrade & Root: Click here
Video to Clean ROM: Click here
HELP Functions: Click here
FAQ: Click here
Analyse Virus Total:
Nothing risk, virus detected are just exploit to downgrade your device.
AhnLab-V3 2011.09.17.00 -
AntiVir 7.11.14.223 2011.09.16 -
Antiy-AVL 2.0.3.7 -
Avast 4.8.1351.0 -
Avast5 5.0.677.0 -
AVG 10.0.0.1190 -
BitDefender 7.2 -
ByteHero 1.0.0.1 2011.09.13 -
CAT-QuickHeal 11.00 2011.09.16 -
ClamAV 0.97.0.0 PUA.Packed.PECompact-1
Commtouch 5.3.2.6 -
Comodo 10147 -
DrWeb 5.0.2.03300 -
Emsisoft 5.1.0.11 -
eSafe 7.0.17.0 2011.09.15 -
eTrust-Vet 36.1.8566 -
F-Prot 4.6.2.117 -
F-Secure 9.0.16440.0 Exploit.Android.Lotoor.C
Fortinet 4.3.370.0 -
GData 22 -
Ikarus T3.1.1.107.0 -
Jiangmin 13.0.900 -
K7AntiVirus 9.113.5150 -
Kaspersky 9.0.0.837 Exploit.Linux.Lotoor.g
McAfee 5.400.0.1158 -
McAfee-GW-Edition 2010.1D -
Microsoft 1.7604 -
Microsoft 1.7604 -
NOD32 6472 -
Norman 6.07.11 -
nProtect 2011-09-17.01 -
Panda 10.0.3.5 Suspicious file
PCTools 8.0.0.5 -
Prevx 3.0 -
Rising 23.75.04.02 2011.09.16 -
Sophos 4.69.0 -
SUPERAntiSpyware 4.40.0.1006 -
Symantec 20111.2.0.82 -
TheHacker 6.7.0.1.298 -
TrendMicro 9.500.0.1008 -
TrendMicro-HouseCall 9.500.0.1008 -
VBA32 3.12.16.4 2011.09.16 -
VIPRE 10504 -
ViRobot 2011.9.17.4674 -
VirusBuster 14.0.218.0 -
Click to expand...
Click to collapse
Nice one mate It'll definitely make the thing easier. Keep it up!
is possible to downgrade from 2.50??
No, Impossible at this time
You are using code that is not yours, but under GPL, and you do not mention about it. That is bad manners. I suggest you put the code up, and credit people who you should.
Sent from my Desire HD using Tapatalk
Look Post #1:
All credits for used tools in this tool go to their respective authors
Click to expand...
Click to collapse
My code is:
Code:
string[] ThreadReply;
foreach (string blah in ThreadReply)
{
if (blah.contains("useless replies")
{
return;
}
}
If my work don't like on XDA, a moderator can delete thread...
Can't time to enumerate every person but soon... (sorry bad english)
Is that possible to S-OFF my DHD on 2.37...?
Your software does not even install.
Win7 x64 error when trying to install :
The Application has failed to start because its side by side configuration is in correct, please see the application event log or use the command line sxstrace.exe tool for more detail.
-------------------------------
Good to see that rooting etc is getting so easy from our old times with dhd we would require almost like 1-3hours to be able to do these things =)
Sent from my HTC Desire HD using XDA Premium App
Volupia said:
Look Post #1:
Click to expand...
Click to collapse
Yep, but you are using gfree, for example. That binary is under GPL, so you have to release the sources.
Sent from my Desire HD using Tapatalk
ViRuS3k said:
Your software does not even install.
Win7 x64 error when trying to install :
The Application has failed to start because its side by side configuration is in correct, please see the application event log or use the command line sxstrace.exe tool for more detail.
-------------------------------
Click to expand...
Click to collapse
Try to download again, check MD5
ViRuS3k said:
Your software does not even install.
Win7 x64 error when trying to install :
The Application has failed to start because its side by side configuration is in correct, please see the application event log or use the command line sxstrace.exe tool for more detail.
-------------------------------
Click to expand...
Click to collapse
Hi,
no errors here on x64.
@Volupia
Downgrade 2.37 => 1.32 works also?
with friendly greet
starbase64
Normally yes
Hi,
when i click downgrade, comes an error (Win7 x64 SP1):
System.ArgumentOutOfRangeException: Der Index und die Länge müssen sich auf eine Position in der Zeichenfolge beziehen.
Parametername: length
bei System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy)
bei System.String.Substring(Int32 startIndex, Int32 length)
bei Ultimate_Multi_Tool.MainForm.c73ea2d03681d4ec03218824511668ef8(Object c817b27b6de19740a350c1f5eb870ec61, EventArgs c325d59a43fd6db731d4b330167940de2)
bei System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
bei System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
bei System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
bei System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
bei System.Windows.Forms.ToolStripItem.FireEventInteractive(EventArgs e, ToolStripItemEventType met)
bei System.Windows.Forms.ToolStripItem.FireEvent(EventArgs e, ToolStripItemEventType met)
bei System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
bei System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.ScrollableControl.WndProc(Message& m)
bei System.Windows.Forms.ToolStrip.WndProc(Message& m)
bei System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
bei System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Geladene Assemblys **************
mscorlib
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.235 (RTMGDR.030319-2300).
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll.
----------------------------------------
Ultimate Multi Tool
Assembly-Version: 1.2.12.0.
Win32-Version: 1.2.12.
CodeBase: file:///C:/Program%20Files%20(x86)/Ultimate%20Multi%20Tool/Ultimate%20Multi%20Tool.exe.
----------------------------------------
System
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.232 built by: RTMGDR.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll.
----------------------------------------
ResourceAssembly
Assembly-Version: 1.0.0.0.
Win32-Version: 1.2.12.
CodeBase: file:///C:/Program%20Files%20(x86)/Ultimate%20Multi%20Tool/Ultimate%20Multi%20Tool.exe.
----------------------------------------
System.Windows.Forms
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.235 built by: RTMGDR.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll.
----------------------------------------
System.Drawing
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.1 built by: RTMRel.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.
----------------------------------------
AutomaticUpdater
Assembly-Version: 2.6.14.0.
Win32-Version: 2.6.14.0.
CodeBase: file:///C:/Program%20Files%20(x86)/Ultimate%20Multi%20Tool/AutomaticUpdater.DLL.
----------------------------------------
System.Xml
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.1 built by: RTMRel.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll.
----------------------------------------
System.Configuration
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.1 (RTMRel.030319-0100).
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll.
----------------------------------------
mscorlib.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.235 (RTMGDR.030319-2300).
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_de_b77a5c561934e089/mscorlib.resources.dll.
----------------------------------------
System.Windows.Forms.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.0.30319.1 built by: RTMRel.
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.
----------------------------------------
************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.
Zum Beispiel:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
Click to expand...
Click to collapse
with friendly greet
starbase64
win xp mode on win7
ViRuS3k said:
Your software does not even install.
Win7 x64 error when trying to install :
The Application has failed to start because its side by side configuration is in correct, please see the application event log or use the command line sxstrace.exe tool for more detail.
-------------------------------
Click to expand...
Click to collapse
should you try on xp mode???
i hope it works
good luck
When you click on "Downgrade", UMT call adb "getprop ro.product.version" to obtain your version.
Can you put command in cmd.exe: adb shell getprop ro.product.version
And post your result please
Hi,
i would test the tool, but i have cm7.
I will test at this night with a device from a friend
with friendly greet
starbase64
Sorry, Not tested with cm7...
Hi, I want to S-OFF my DHD 2.37, but it show"Unknown error, probably connection." any ideal?
---------------------------------
Overview
---------------------------------
*RZrecovery*:
-=overclock settings=-
-=Arbitrary update.zip selection (with folders) (don't have to rename files to update.zip).=-
-=rom.tgz support (of course)=-
-=Unsigned update.zip support=-
-=ability to wipe system, data, boot, dalvik-cache, battery stats, cache-
-=No automatic backup when installing a rom.tgz=-
-=update.zip from folder support=-
-=Ability to install APK's, IMG's, ZIP's, TAR's, TGZ's from the same menu=-
-=Wipe battery statistics=-
-=Battery charging!=-
-=clockwork nandroid restore=-
-=Ability to root any ROM=-
-=12 predefined colors + random color selection=-
-=Rave mode: random color every time screen is redrawn=-
-=preinstall update.zip menu=-
-=battery status (charging status, temperature and charge level) display=-
-=android_secure nandroid / wipe support=-
-=Hold volume keys to scroll=-
-=Touch screen scrolling on some devices=-
-=Davlik bytecode verification disable/enable=-
---------------------------------
Background
---------------------------------
Last year I made RZRecovery for the original droid. It was a huge success, since then I have been asked to port to other devices. So here, about 1 year later, I have done just that. This will bring all the features of the old RZR plus a few new ones including the epic rom.tgz install format from the days of yore to any device. I have built this recovery specifically to handle all devices without the need for a recompile (except for Tegra2-based devices, they have to be recompiled because of some libc bugs). I have made img files for a few devices to start with:
---------------------------------
CONFIRMED
---------------------------------
HTC Thunderbolt
Samsung Nexus S
Samsung Nexus S 4G
Motorola Droid
HTC Incredible/Incredible S/ Incredible 2
HTC EVO 4G
---------------------------------
EXPERIMENTAL
---------------------------------
HTC MyTouch 4G/Slide
HTC Leo
HTC Dream/Sapphire/Magic
HTC Click/Tattoo
HTC Aria
HTC Wildfire
HTC Legend
HTC Desire/Desire CDMA/Desire S/ Desire HD
HTC Hero/Hero CDMA
Samsung Fascinate (need to find out where recovery is stored for mtd)
LG Optimus S
LG Optimus 1
LG Optimus V
LG Optimus 2X
Huawei Ideos
Huawei u8220/u8150
Motorola Cliq/ Cliq XT
Motorola Backflip
Motorola Atrix
PLEASE: IF ANY OF THSE EXPERIMENTAL BUILDS WORK, PLEASE POST AND LET ME KNOW SO THAT I MAY MOVE THEM TO THE CONFIRMED SECTION
In order to port RZR to anything, I need to know the base kernel address, the boot command line, the page size and the partition layout.
---------------------------------
SCREENSHOTS
---------------------------------
{
"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"
}
View all (in case forums limit the amount of images shown): http://rzdroid.com/ftp/recovery/screenshots/2.1.0/view.html
---------------------------------
CREDITS
---------------------------------
(without any of these individuals/organizations none of this could be possible)
CyanogenMod - for being completely open and having a huge database of device information
koush - for clockworkmod, where I got support for other partition types and filesystems
rbox - for repeat scroll and touch screen scrolling
cvpcs - for helping with anything I have ever asked
slayher - for showing me how to enable capacitive buttons on HTC devices
bekit - for showing me the bionic commits to get recovery built for tegra2's
trevorj - for the original battery charge knowledge
my wife - for giving me all the time I needed to get this done
all the testers for testing and encouragement!
---------------------------------
DOWNLOADS
---------------------------------
I will link img files for use with fastboot or flash_image and any applicable zips.
DISCLAIMER: Not that this needs to be said, but by downloading any of the files below, you take full responsibility for what happens with them. Make sure you have a way out if something goes wrong. The devices above are in the experimental section for a reason
EVO 4G: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-supersonic-update.zip
SAMSUNG FASCINATE: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-fascinate-update.zip
MYTOUCH 4G: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-glacier-update.zip
HTC THUNDERBOLT: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-mecha-update.zip
SAMSUNG NEXUS S: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-nexusS-update.zip
SAMSUNG NEXUS S 4G: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-ns4g-update.zip
HTC INCREDIBLE 2: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-vivow-update.zip
HTC INCREDIBLE S: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-vivo-update.zip
LG OPTIMUS S: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-thunderc-update.zip
LG OPTIMUS 1: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-thunderg-update.zip
LG OPTIMUS 2X: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-p990-update.zip
MOTOROLA DROID: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-sholes-update.zip
HTC LEO: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-leo-update.zip
HTC MAGIC: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-magic-update.zip
HTC DREAM: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-dream_sapphire-update.zip
HTC MARVEL: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-dream_sapphire-update.zip
HTC ACE: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-ace-update.zip
HTC DESIRE http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-bravo-update.zip
HTC DESIRE (CDMA): http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-bravoc-update.zip
HTC WILDFIRE: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-buzz-update.zip
HTC CLICK: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-click-update.zip
MyTouch Slide: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-espresso-update.zip
HTC HERO: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-hero-update.zip
HTC HERO (CDMA): http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-heroc-update.zip
HTC LEGEND: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-legend-update.zip
HTC ARIA: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-liberty-update.zip
MOTO CLIQ: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-morrison-update.zip
MOTO BACKFLIP: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-motus-update.zip
MOTO ATRIX: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-olympus-update.zip
HTC SAGA: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-saga-update.zip
HUAWEI U8150: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-u8150-update.zip
HUAWEI U8220: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-u8220-update.zip
HTC VISION: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-vision-update.zip
MOTO CLIQ XT: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-zeppelin-update.zip
HTC ZERO: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-zero-update.zip
---------------------------------
SOURCE
---------------------------------
https://github.com/raidzero/RZrecovery/tree/gingerbread
---------------------------------
WALKTHROUGH
---------------------------------
Volume up/down - scroll (can hold down to repeat scroll)
HTC - touch screen - scroll
Home - select
Back/Power - back
Code:
Main screen
Reboot android
Reboot recovery
Reboot bootloader
Power off
Wipe menu
Wipe all - wipe everything on the device except recovery
Wipe system (the ROM)
Wipe data (your applications and settings)
Wipe .android-secure (other applications and settings on sdcard)
Wipe boot (the main android kernel)
Wipe cache
Wipe battery stats
Wipe dalvik cache (cache of optimized dalvik executables)
Mount menu
Mount/unmount system (the ROM)
Mount/unmount data (apps and settings)
Mount/unmount sdcard
Enable/Disable USB Mass storage
Nandroid menu
Nandroid Backup
Perform backup
choose boot,data,android-secure,system to back up
Nandroid restore
Choose backup
choose boot,data,android-secure,system to restore
Clockwork nandroid restore
choose backup and immediately restore the whole thing
Install from sdcard
choose item to install:
APK, ZIP, IMG, (must end in rec.img or boot.img) .TAR, .TGZ
Preinstall Menu
Abort Install
Backup before install (make a quick backup of the device naming it preinstall-date-time)
Wipe data
Perform install
if(APK)
Abort APK install
Install to system
Install to data
Extras menu
Custom Colors
Random - randomly generated color, will save to sdcard
Any other color - will save to sdcard
Rave mode - a totally random color each time the screen is redrawn (every key press)
Show battery status - will show charge status, level, temperature if available
Recovery overclocking
Kernel will report the available CPU slots, pick one and it will set the max to your selection. Saves to sdcard
ROM tweaks
Disable OTA update downloads in ROM - will prevent android from downloading updates OTA
Activate Root access in ROM
Yes - roots the current ROM (still requires the superuser.apk from chainsdd)
No - does nothing
Dalvik bytecode tweaks
Disable bytecode verification
Enable bytecode verificaion
this deserves some explaining. saved the best for last :) In android, when executables are loaded, the dalvik VM will go
through each line of instructions and make sure it is valid, if it isn't (poorly written application) it will fix it to the best of its ability. This verification process takes time. Disabling this will speed up all the operations on the phone and might even save some RAM. If it doesn't work for you or causes apps to crash, re-enable the verifier here.
So please, if you want this for your device just post here and I will try to get it done for you
POSSIBLE CAVEATS
Update.zip status 2: this means the update.zip you re trying to flash has an outdated update-binary (META-INF/com/google/android/update-binary). Please replace this file in your zip with my version (from gingerbread) here: http://rzdroid.com/ftp/recovery/gingerbread/APIlevel3-update-binary
Update.zip status 7: This means the script is not compatible with the update-binary. This will most likely happen after you replace the update-binary in an outdated update.zip. The most common errors are that the mount and format commands now take extra arguments. you must pass the filesystem type like so:
OLD:
Code:
format("MTD", "system");
mount("MTD", "system", "/system");
NEW:
Code:
format("MTD", "yaffs2", "system");
mount ("MTD", "yaffs2", "system", "/system");
I have changed the API level to 2, to help alleviate some of these issues. It is still evel 3 but all level 2 update.zips should work fine.
Not the addition of the filesystem type. No idea why they changed this, seems like since it now uses recovery.fstab that this info could simply be figured out. or maybe I will implement a method of checking for status 7 and possibly telling it the filesystem information myself. Either way, this info will get you rolling now.
Can you make one for the lg optimus gt540 dont no it this helps
Partitions
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 04000000 00020000 "cache"
mtd2: 00500000 00020000 "recovery"
mtd3: 00060000 00020000 "splash"
mtd4: 0f500000 00020000 "system"
mtd5: 002c0000 00020000 "lgdrm"
mtd6: 08a80000 00020000 "userdata"
mtd7: 00100000 00020000 "misc"
mtd8: 00080000 00020000 "usd"
mtd9: 005a0000 00020000 "pkg"
mtd10: 1cfc0000 00020000 ""
Cmdline
mem=214M console=ttyMSM2,115200n8 androidboot.hardware=swift uart.mode=arm11_uart_disable crash=off
Sent from my LG GT540 Swift using xda premium
eoghan2t7 said:
Can you make one for the lg optimus gt540 dont no it this helps
Partitions
dev: size erasesize name
mtd0: 00500000 00020000 "boot"
mtd1: 04000000 00020000 "cache"
mtd2: 00500000 00020000 "recovery"
mtd3: 00060000 00020000 "splash"
mtd4: 0f500000 00020000 "system"
mtd5: 002c0000 00020000 "lgdrm"
mtd6: 08a80000 00020000 "userdata"
mtd7: 00100000 00020000 "misc"
mtd8: 00080000 00020000 "usd"
mtd9: 005a0000 00020000 "pkg"
mtd10: 1cfc0000 00020000 ""
Cmdline
mem=214M console=ttyMSM2,115200n8 androidboot.hardware=swift uart.mode=arm11_uart_disable crash=off
Sent from my LG GT540 Swift using xda premium
Click to expand...
Click to collapse
The only other thing I am missing is the pagesize and base address. Is there a Cyanogenmod for it? thats the quickest way to get all that info
raidzero said:
The only other thing I am missing is the pagesize and base address. Is there a Cyanogenmod for it? thats the quickest way to get all that info
Click to expand...
Click to collapse
There is kernel source would that help? Thanks
Edit: no cm repo but heres the kernel source:
https://github.com/wingrime/android_kernel_swift_lg/
Sent from my LG GT540 Swift using xda premium
About to try this
nobody calls my EVO a fizzle and gets away with it!!
Well mate any luck?
Sent from my LG GT540 Swift using xda premium
with some research I have found the base address for that device to be
0x00200000
I will make an img for it tonight. Do you have google talk? I will need to experiment to find the correct pagesize for the device.
raidzero said:
with some research I have found the base address for that device to be
0x00200000
I will make an img for it tonight. Do you have google talk? I will need to experiment to find the correct pagesize for the device.
Click to expand...
Click to collapse
Yeah i do ill pm you the address
Sent from my LG GT540 Swift using xda premium
For wildfire s??
Would you mind bringing this to the HTC Wildfire S?????
And as for the info you need.......there is an unofficial port of cm7
here
HD2
i like what u have here...if u can i hope i can use it on HD2
THX
Can it be made for Dell streak 5 PLease PLease..................
anyone try this on NS4G yet?
TheBurgh said:
anyone try this on NS4G yet?
Click to expand...
Click to collapse
ns4g is the phone I have. it works great
Would you mind making this available to HTC G1 please?
Thanks in advance.
ahmadns said:
Would you mind bringing this to the HTC Wildfire S?????
And as for the info you need.......there is an unofficial port of cm7
here
Click to expand...
Click to collapse
marvel? http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-marvel-update.zip
BeenAndroidized said:
Would you mind making this available to HTC G1 please?
Thanks in advance.
Click to expand...
Click to collapse
dream & magic:
http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-dream-update.zip
http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-magic-update.zip
(they are the exact same thing)
raidzero said:
dream & magic:
http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-dream-update.zip
http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-magic-update.zip
(they are the exact same thing)
Click to expand...
Click to collapse
Thank you. I will download it when I have a chance.
EDIT: OK, since there is no instruction on this. I am assuming that I flash it through my current recovery from SD card. Is that right?
BeenAndroidized said:
Thank you. I will download it when I have a chance.
EDIT: OK, since there is no instruction on this. I am assuming that I flash it through my current recovery from SD card. Is that right?
Click to expand...
Click to collapse
that is correct. flash it like any other update.zip please let me know if it boots and how it works!
eoghan2t7 said:
Yeah i do ill pm you the address
Sent from my LG GT540 Swift using xda premium
Click to expand...
Click to collapse
try this: http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-swift-update.zip
let me know if it boots and how it runs
seaman2k said:
i like what u have here...if u can i hope i can use it on HD2
THX
Click to expand...
Click to collapse
htc leo, right? http://rzdroid.com/ftp/recovery/gingerbread/RZR-2.1.0-leo-update.zip
same story as the rest...
I am trying to install the just released update from Verizon but I klept getting the message that the software failed. Do I need to unroot the device first?
You can keep root but make sure you have stock recovery otherwise the ota will fail.
Sent from my SGH-T999V using xda premium
shahkam said:
You can keep root but make sure you have stock recovery otherwise the ota will fail.
Sent from my SGH-T999V using xda premium
Click to expand...
Click to collapse
If I am running an unrooted VRBLI5 will OTA work to update to VRBLK3? I keep trying to check for a software update and it says that there is no new software update available.
The OTA will not show up unless you downgrade to VRALHE. Since VRBLI5 was not an official version it won't offer you the OTA. You could also upgrade to VRBLK3 using one of the guides in the development section which would probably be a lot easier.
fromaap integrable
BigErnM said:
The OTA will not show up unless you downgrade to VRALHE. Since VRBLI5 was not an official version it won't offer you the OTA. You could also upgrade to VRBLK3 using one of the guides in the development section which would probably be a lot easier.
Click to expand...
Click to collapse
Thanks so much for the quick response and for the insight - very appreciated. I was bummed when my wife got the OTA and I didn't! I will probably just upgrade to the new stock rather than downgrade and upgrade.
My completely stock S3 is failing checking for updates saying that the update service is not available. It doesn't seem to ever have been able to successfully check for updates (last checked time is blank).
I noticed the following in adb logcat when I tried to check for updates:
Code:
E/SyncmlDMGenericExtHandlerConnector( 1913): Can not route to Mobile Admin Network 64.186.176.220
However, on the phone, I can ping that IP address just fine, at the same time as it's supposedly trying to check for updates:
Code:
[email protected]:/ $ ping 64.186.176.220
PING 64.186.176.220 (64.186.176.220) 56(84) bytes of data.
64 bytes from 64.186.176.220: icmp_seq=1 ttl=248 time=61.6 ms
64 bytes from 64.186.176.220: icmp_seq=2 ttl=248 time=58.4 ms
64 bytes from 64.186.176.220: icmp_seq=3 ttl=248 time=56.5 ms
This happens on wifi or mobile data. Any suggestions on how to make this thing check for updates?
Thanks.
---------- Post added at 12:04 PM ---------- Previous post was at 12:02 PM ----------
The rest of the error:
Code:
D/ConnectivityService( 650): requestRouteToHostAddress on down network (10) - dropped
I/ ( 1913): HTTP: http_socket_connect ret:-1 Errno:115
I/ ( 1913): connect wouldblock: EINPROGRESS
D/memalloc( 340): ion: Allocated buffer base:0x42f61000 size:630784 fd:62
D/memalloc( 1913): ion: Mapped buffer base:0x5e66b000 size:630784 offset:0 fd:77
D/KeyguardViewMediator( 650): setHidden false
I/Adreno200-EGLSUB( 340): <CreateImage:893>: Android Image
I/Adreno200-EGLSUB( 340): <GetImageAttributes:1102>: RGBA_8888
D/KeyguardViewMediator( 650): setHidden false
I/ ( 1913): HTTP: SSL_CTX_load_verify_locations ret :0
I/ ( 1913): SSL_load_verify_locations failed
I/ ( 1913): HTTP: xaction 1574547464 ssl init error
I/ ( 1913): HTTP: status code 0
I/ ( 1913): [s]:[ERROR]:
I/ ( 1913): vendor/samsung/common/packages/apps/SyncMLSvc/native/syncmlcore/base/dm/src/tsldm_ses.cpp:Line:683 SesWaitForMsgSt:Error:9 happend while Recv Msg
I/ ( 1913):
I/ ( 1913): [s]:[ERROR]:
I/ ( 1913): vendor/samsung/common/packages/apps/SyncMLSvc/native/syncmlcore/base/dm/src/tsldm_ses.cpp:Line:788 Session Status :100663305
I/ ( 1913):
D/KeyguardViewMediator( 650): setHidden false
I/ ( 1913): shutdown Socket :50 return: 0
I/ ( 1913): HTTP: http_dispatch trans is already freed 5dd9b008
shahkam said:
You can keep root but make sure you have stock recovery otherwise the ota will fail.
As far as I know I have stock recovery. I did not flash a new ROM
Click to expand...
Click to collapse
I cant upgrade mine either, all I did was root
no unlocked bootloader, everything is stock
all stock apps are installed and running
Seems like lots of other Verizon customers are having the same problem. My phone is rooted, bootloader is unlocked and I have stock ROM
Please read forum rules before posting
Rule 15 tells you where to post if you are confused
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
And please search, this has been asked and answered several times
[Q] Installing WP7.8 error "The Preinstallation Update/Super package isn't signed"
I have tried multiple times trying to install the WP7.8 upgrade package DL'ed via NaviFirm, but, while installing the package using WP7 Update Cab Sender, It keeps aborting. Can someone shed any lights as to what I had done wrong?
Many thanks to all in advance...
The screen shows the message as below:
╔════════════════════════════════════════════════════════════════════╗
║ WP7 Update Cab Sender xboxmod-Yuki 2011 ║
╠════════════════════════════════════════════════════════════════════╝
■
╠══════» S ·(S)end Cabs to device
■
╠══════» B ·Send Cabs to device with (B)ackup
■
╠══════» R ·(R)estore device backup
■
╠══════» L ·Read last Update (L)ogs from device
■
╚══> Your choice: S
╔══════» Creating list of cabs
■
■
╠══════» Updating device
■
UpdateWP version 4.8.2345.0
Applying updates to device
Id: \\?\usb#vid_045e&pid_04ec&mi_00#6&1a2d7d96&0&0000#{ca3d7387-f67
b-11da-bbec-8000600fe800}
SN: 691cad0a - 1fa581b0 - c3f49745 - f3fdba46
Name: XXXX Lumia 800
KITLName: SEARAYxxxxxxxxx
Manufacturer: NOKIA
ModelId: 4
Model: Lumia 800
MobileOperator: 000-ID
Version: 07.10.08773.03-00.00.00000.00-00.00.00000.00
Checking your phone's status: Completed in 0.01 seconds
Checking system requirements: Completed in 0.03 seconds
Downloading updates: Completed in 32.68 seconds
Checking system requirements: Completed in 0.02 seconds
Transferring updates: Completed in 49.04 seconds
Preparing to install: Completed in 8.07 seconds
Error:
Update device 691cad0a - 1fa581b0 - c3f49745 - f3fdba46 Complete with error code
: 80188223, error message: Phone Update Agent error: The preinstallation update
package (or super package) isn't signed.
■
╚══════» Done
Press any key to continue . . .
Re: [Q] Installing WP7.8 error "The Preinstallation Update/Super package isn't signed
I am having htc explorer a310e plz tell me how to install rom in it and upgrad to android 4 in easiest way. For your info i am new to android world. I unlock bootloader and root my phone using super user. After this i done factor reset and now stuck on htc logo screen. Plz help me in repairing my device.
Sent from my GT-P3100 using xda app-developers app
RESILVED
I resolved the issue by updating/upgrading the WP os to 7.8 by way of Nokia Care Suite.
I am now running WP7.8, will update with all the goods and bads of this new update.
Thanks
maclear said:
I have tried multiple times trying to install the WP7.8 upgrade package DL'ed via NaviFirm, but, while installing the package using WP7 Update Cab Sender, It keeps aborting. Can someone shed any lights as to what I had done wrong?
Many thanks to all in advance...
The screen shows the message as below:
╔════════════════════════════════════════════════════════════════════╗
║ WP7 Update Cab Sender xboxmod-Yuki 2011 ║
╠════════════════════════════════════════════════════════════════════╝
■
╠══════» S ·(S)end Cabs to device
■
╠══════» B ·Send Cabs to device with (B)ackup
■
╠══════» R ·(R)estore device backup
■
╠══════» L ·Read last Update (L)ogs from device
■
╚══> Your choice: S
╔══════» Creating list of cabs
■
■
╠══════» Updating device
■
UpdateWP version 4.8.2345.0
Applying updates to device
Id: \\?\usb#vid_045e&pid_04ec&mi_00#6&1a2d7d96&0&0000#{ca3d7387-f67
b-11da-bbec-8000600fe800}
SN: 691cad0a - 1fa581b0 - c3f49745 - f3fdba46
Name: XXXX Lumia 800
KITLName: SEARAYxxxxxxxxx
Manufacturer: NOKIA
ModelId: 4
Model: Lumia 800
MobileOperator: 000-ID
Version: 07.10.08773.03-00.00.00000.00-00.00.00000.00
Checking your phone's status: Completed in 0.01 seconds
Checking system requirements: Completed in 0.03 seconds
Downloading updates: Completed in 32.68 seconds
Checking system requirements: Completed in 0.02 seconds
Transferring updates: Completed in 49.04 seconds
Preparing to install: Completed in 8.07 seconds
Error:
Update device 691cad0a - 1fa581b0 - c3f49745 - f3fdba46 Complete with error code
: 80188223, error message: Phone Update Agent error: The preinstallation update
package (or super package) isn't signed.
■
╚══════» Done
Press any key to continue . . .
Click to expand...
Click to collapse
hLe Storm ROM
I am playing with ArchiKitchen and I may be on to something here. But first...
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and
* YOU acknowledge you are doing so at your own risk.
*/
Now that that's out of the way, hLe Storm (pronounced "hailstorm") is a stock, de-bloated (without many GApps, without T-Mobile bloat, and a few other apps removed), de-branded (T-Mobile animations removed), deodexed ROM. The boot image has been replaced with @xdajog's sediKERNEL v2.0, with other replacements as well (see credits). Keep in mind that the Optimus UI is still going strong.
SCREENSHOTS:
{
"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"
}
WHAT WORKS/FEATURES:
Powers on.
Able to make calls.
Download and install apps.
Camera.
App drawer down to two pages!
Able to install a fair amount of apps without needing Link2SD (I currently have 33 extra apps installed on my device, and still have over 400MB free space)!
Write/Share key remapped to "Tab" (for those console lovers like myself - this feature can be reverted)
Right Fn is now Ctrl Key (but be sure you are using the latest version of ConnectBot for the key to work in that app!)
MicroSD Edition runs all userdata from the MicroSD - have as much or as little space to play with!
WHAT DOES NOT WORK:
Wifi calling (specific to T-Mo - feature removed - to avoid the notifications after every call, you must still disable it in call settings).
Built-in Tethering (broken for most anyway, use jTether instead)
You may not be able to access the bootloader (but you have the three-finger-salute magic keys to get you to TWRP anyway).
Soft reboot (often invoked optionally via XPosed) tends to lead to bootloop. If stuck in this situation, pull battery, reinsert, and power on normally.
Probably inherited by the stock ROM, but there is a ~10,000 SMS/MMS limit in messaging. Auto-delete works, but if you turn that off, or plan to have more than 20 frequent contacts, you may lose access to new messages (will get the notification, but chat window will have nothing new). For the latter problem, this can be worked around by decreasing the number of texts stored per conversation (so if you have ~40 frequent contacts, set the limit to 250). For the former (and optionally for the latter), you will have to freeze the stock messaging app and download a different one to handle your SMS/MMS.
Home Screen in Setting forsce closes. This is because I removed the stock launcher. Oops.
Latest version has the "Feeling Lucky" activity that should not be there - was supposedly removed by the launcher dev - is present. Not that it is permanent (remove it from homescreen)
You tell me...
TODO:
Continue to extensively test current functionality.
Suggestions?
DOWNLOAD:
hLe_Storm_Fx3q_20150516.zip (MD5: fae80f8a4cd248231e0fefafad1abc85)
hLe_Storm_Fx3q_20150527-CWM-Edition.zip (MD5: 5c00bf0ddc8724e8f8fa32ecb5ed93ff)
SPECIAL DOWNLOAD:
A few considerations before the download link ... please read before clicking!
There is risk to flashing ROM's (hence the disclaimer above). This one provides more risk even if done correctly...
You will need a MicroSD card before starting. Unlink all your apps (if were using Link2SD), and remove it from the device (unmount first if still on).
Load it into a PC, and fire up GParted (or similar tool that can format ext4 partitions). Be sure to select the MicroSD under devices (or you may nuke your PC)!
Shrink the current FAT32 partition to leave around 5GB unused space (or more or less, depending on your preference - this free space will become your userdata partition). If coming from Link2SD setup, you may have already done this.
Create a partition (set as primary - as logical type will not be found by the ROM) and format the unused space to ext4. If coming from Link2SD, you may need to remove and re-add the partition (note this will kill all your previously saved linked apps - make a backup first if concerned).
By the way, the previous step (formatting via PC) is how you will wipe userdata, at least until we have a TWRP that can do this easier. Keep not of this technique.
Once ready (you may take the time to copy the ROM over to the FAT32 partition), pop the MicroSD into the device, and boot into TWRP.
Follow steps as usual (back up, wipe, install ROM, wipe dalvik, reboot).
You will be faced with a fresh system, with more room to play with!
One last consideration - becasue there will be more writing to the MicroSD, the card will deteriorate faster, back up (on your PC) often (dd'ing the entire drive will work fine), and be wary of glitches, cause when they start, all bets are off. Have a spare (preferably of the same size/model, but don't size down or your backups won't restore).
Got it? :fingers-crossed: Okay, now you can download ... see below.
hLe_Storm_Fx3q_20150714-MicroSD-Edition.zip (MD5: 6412d91f5f2600a1a8352c6e21bb9442)
OLD DOWNLOADS:
Be sure which one to download/flash! The type determines which partition the kernel gets flashed to. If you are using a typical setup, use the Boot option. If using xdajog's "Really Bulletproof Method" (aka Method 2), then you must use the Recovery option. Failure to use the right one will result in losing your recovery, and there is a good chance your ROM won't start either! You have been warned!
Also, these downloads use the older kernel. So in an emergency you would need to "adb reboot recovery" to get back into TWRP.
hLe_Storm_Fx3q_20150511-Boot.zip (MD5: 7c8436bb2053965bef1ca5e733fe127a)
hLe_Storm_Fx3q_20150416-Boot.zip (MD5: 21c3d5386a92523a10f631d04c35bfe6)
hLe_Storm_Fx3q_20150228-Boot.zip (MD5: 8b82caa80663f3bb327958c105f4f3a6)
hLe_Storm_Fx3q_20141222-Boot.zip (MD5: bb3f3a9ca82f972947bca6a24fd16987)
hLe_Storm_Fx3q_20141203-Boot.zip (MD5: 16e0da3d9109548820cd23a0d2bfd7d6)
INSTRUCTIONS:
Have a custom recovery installed - see "Install Considerations" in the next post for more info
Download ROM above
Save/push file to your External SD card (preferably in the root folder where you can find it later)
Reboot into recovery ("adb reboot recovery")
Nandroid/Back up device (optional - see considerations below)
Wipe cache and data/factory reset (see considerations below)
Install ROM
Wipe Dalvik cache
Reboot
Enjoy!
RESOURCES:
TWRP
CWM
sediKERNEL
Revert to TRUE STOCK
F3Q General Discussion
CREDITS:
xdajog for sediKERNEL
dennisxl for Apex Launcher
Shaftamle for ShaftaGhostKO Keyboard
Chainfire for SuperSU
JustArchi for ArchiKitchen
awillquik for testing with CWM and providing workaround instructions
Did I miss anything? I appreciate the feedback, and any thanks as well!
XDA:DevDB Information
[ROM][STOCK][JB 4.1.2] LG Optimus F3Q / D520, ROM for the Android General
Contributors
joel.maxuel
ROM OS Version: 4.1.x Jelly Bean
ROM Kernel: Linux 3.4.x
Based On: Stock
Version Information
Status: Nightly
Current Stable Version: 2.2/2.3
Created 2015-05-19
Last Updated 2016-02-07
More Info...
INSTALL CONSIDERATIONS:
There is an option between recoveries, CWM and TWRP. Both have their purpose, so it comes down to personal preference. For the lesser amount of hassle (see below), I would recommend TWRP. Download and instructions for TWRP are in the resources section of the first post, here is how one can install CWM for the F3Q (expand following spoiler):
Download F3Q-Utilities.apk to your computer (from http://androidforums.com/threads/recovery-unofficial-cwm-6-0-5-0-fx3q.863081/)
Put F3Q-Utilities.apk on to the external SD card of the phone
Run F3Q-Utilities.apk on the phone/install it
Open the app that is created on the phone (app name: F3QUtilities2)
In F3QUtilities2 app, choose "Begin", and then "Install CWM"
"Install CWM" will probably not work... so, you must manually add the .LOK file
Download .LOK file to your computer (from http://forum.xda-developers.com/showpost.php?p=54757168&postcount=188)
On the phone, use File Manager to find "/sdcard/f3qutilities" (alternatively, the full path could be "/storage/sdcard0/F3QUtilities2")
Determine if the .LOK file in that directory is 0 bytes; if the .LOK file is 0 bytes, rename the newly downloaded .LOK file (on your computer) with the same name that the 0 byte .LOK file has
Put the newly downloaded and renamed .LOK file on the phone (I put it on the SD card initially)
Restart the F3QUtilities2 app (choose "Begin", and then "Install CWM"
After choosing "Install CWM", open File Manager and then move the newly downloaded/renamed .LOK file to the "/sdcard/f3qutilities" folder (replace the 0 byte .LOK file)
Switch back to F3QUtilities2 app and again choose "Install CWM"
This should complete the CWM install (however, the "Reboot to Recovery" button in the F3QUtilities2 app will probably not work)
Go to "Play Store" on your phone and search for "OUD HitSquad Manager"; find and download the app
Open the app; go to "Recovery Options"; go to "Reboot to Recovery" - This should restart the phone in CWM recovery
TWRP was more flexible than CWM in terms of access to recovery. CWM will factory reset the device if accessed via the bootloader (and apparently only that - not that it matters once the ROM is installed). CWM will however, not install the ROM out of the box (until recently will fail on a set_metadata_recursive error). I now have a "CWM Edition" of the ROM, and since it works with TWRP as well, every new version is set to be for CWM too. But for more information on what was done, expand the following spoiler...
This guide assumes a Windows PC.
Download update-binary.zip to your computer (file and instructions from http://forum.xda-developers.com/showthread.php?t=2532300)
Unzip update-binary.zip (i.e. extract the file) to some place on your computer
Use 7-Zip to navigate to "/META-INF/com/google/android" within the unzipped ROM
Drag and drop the unzipped/extracted "update-binary" file into the "/META-INF/com/google/android" directory (this should replace the old "update-binary" file in the zipped ROM)
The ROM should be ready to be installed as normal (i.e. upload zipped ROM to the phone's SD card, enter recovery, etc.)
TWRP currently has a broken wipe function, and limitations when it comes to backup. For example, if you use Link2SD, TWRP will back up the linked data, not the link, creating a backup that will end up being too big to restore. A nandroid is still recommended - I would just trust a dd backup more - you can always do both! (Also, if you haven't backed up your EFS to be put in a safe place, now is the time.) Because of these shortcomings, you should issue the following commands via adb shell (while in TWRP) to work around:
This process should be done regardless if you are using CWM or TWRP!
Code:
# Back up EFS (Just in case)
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/external_sd/modemst1.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/external_sd/modemst2.img
# Back up existing ROM
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/external_sd/system.2014-11-12.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/external_sd/boot.2014-11-12.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/cache of=/external_sd/cache.2014-11-12.img
dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata of=/external_sd/userdata.2014-11-12.img
# Wipe /cache and /data
umount /dev/block/mmcblk0p15
mke2fs -T ext4 /dev/block/mmcblk0p15
umount /dev/block/mmcblk0p14
mke2fs -T ext4 /dev/block/mmcblk0p14
# Restart TWRP
reboot recovery
From there you can install the ROM. If you have problems and need to back out, issue the following commands to restore:
Code:
# Restore device
dd if=/external_sd/system.2014-11-12.img of=/dev/block/platform/msm_sdcc.1/by-name/system
dd if=/external_sd/boot.2014-11-12.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/external_sd/cache.2014-11-12.img of=/dev/block/platform/msm_sdcc.1/by-name/cache
dd if=/external_sd/userdata.2014-11-12.img of=/dev/block/platform/msm_sdcc.1/by-name/userdata
# Reboot
reboot
The restart looks glitchy at first, but the device ends up starting normally.
Other Info...
CHANGE LOG:
Nightly 20150527 (CWM Edition v2.3):
Changed Updater Binary to work with CWM
Updated Apex Launcher to 3.10
Nightly 20150516 (v2.2):
Keymappings (moved Ctrl key for introduction of Tab)
Default ringtone label changed
Majority of bloat (moved to another folder) now purged
Nightly 20150511 (v2.0):
Enhancements with sediKERNEL 2.0
Shutdown animation replaced with LG logo
Default ringtone changed
Nightly 20150416 (v1.8):
Replaced Write & Share keypress in favour of Ctrl key.
Nightly 20150228 (v1.6):
Updated Apex Launcher to latest version (v3.0.3)
Updated SuperSU to latest version (v2.46)
Nightly 20141222 (v1.4):
Updated Apex Launcher to latest version (v3.0.1)
Updated SuperSU to latest version (v2.40)
Nightly 20141203 (v1.2):
Update sediKERNEL to v1.5
Added newest SuperSU (v2.37) to updater-script
Nightly 20141125 (v1.0):
Replaced Keyboard
Replaced Launcher
Removed bloat normally installed on first boot
Nightly 20141120 (v0.8):
Initial upload, using sediKERNEL v1.2
Debloated apps (see below)
Removed boot-up and shutdown sounds
Replaced boot and shutdown animations
BLOATWARE REMOVED:
Lines commented out (starting with a #) have been left in.
Code:
# probably safe to be removed:
Dictionarybin.apk
FileManager*.apk
FileShare*.apk
PolarisViewer*.apk
QTranslator*.apk
LGBrowser*.apk
LGBackup*.apk
Lookout*.apk
tmo_highlight*.apk
TMobile*.apk
ECID*.apk
com.mobitv*.apk
VVM*.apk
# QMemo*.apk
SmartShare*.apk
IQ*.apk
Weather*.apk
WifiCall*.apk
/system/etc/csc_*.txt
/system/etc/hidden_apks_list_*.txt
# Google apps which are downloadable from the market
Videos.apk
PlayGames.apk
#ChromeWithBrowser.apk
#GMS_Maps.apk
#Gmail2.apk
#YouTube.apk
Hangouts.apk
GoogleDrive.apk
Drive.apk
PlusOne.apk
Books.apk
Street.apk
Music2.apk
Magazines.apk
#This needs a replacement (done):
LGHome3a.apk
LGHome3_Theme_Biz.apk
LGHome3_Theme_Optimus.apk
LGIMEbin.apk
IDEAS:
I am open for them...
joel.maxuel said:
[Time for me to ask around, to see if there are any workarounds on this issue. @xdajog, do you know?
Click to expand...
Click to collapse
Ah ok I may understand what you meant. What have you done regarding the boot image when you used archikitchen? Is it the pure stock boot image that you included only or how do you included that?
Well it must be pure DD ' ed boot image or simply using sediKERNEL as mentioned already. Both should fix your issue here.
Hi Joel,
as I need to setup my wife's device now I choosen your debloated ROM.
I may will work on the AROMA installer if you like The problem is I cannot test/debug anymore so it may be not such smooth developing experience though..
Options would be:
- Boot or Recovery installation
- Full wipe or partial wipe
- Rooted or not
- ...
xdajog said:
Hi Joel,
as I need to setup my wife's device now I choosen your debloated ROM.
I may will work on the AROMA installer if you like The problem is I cannot test/debug anymore so it may be not such smooth developing experience though..
Options would be:
- Boot or Recovery installation
- Full wipe or partial wipe
- Rooted or not
- ...
Click to expand...
Click to collapse
Great! I can host the next version later tonight if you like (~9PM GMT), just need to get the changes together. (Do you have the new boot.img so I can include that?)
That would be awesome! I think having a separate zip for the boot and recovery install would be preferable though, less chance of devastatingly hitting the wrong option. The rest of the options can be managed by AROMA.
joel.maxuel said:
Do you have the new boot.img so I can include that?
Click to expand...
Click to collapse
Hm the mentioned adb options are already included in sediKERNEL. I remember that I added them because I thought it could make sense
The trick is to watch the existence of adb while booting up because the mentioned setting will start adb for a short time only!
I use this while booting up:
Code:
while [ 1=1 ];do sleep 2 && adb devices;done
When you see your device connect with adb and you should be there.
The following settings are made in default.prop
Code:
ro.secure=0
ro.adb.secure=0
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.lge.eula_agreement=true
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
So there should be everything you need in place. I think the reason why it was not working for you was that you do not connect to adb while booting.
The kexec-patches removed sediKERNEL is not ready yet.. may come today or tomorrow..
That would be awesome! I think having a separate zip for the boot and recovery install would be preferable though, less chance of devastatingly hitting the wrong option. The rest of the options can be managed by AROMA.
Click to expand...
Click to collapse
really? I think that would makes life much easier.. I think about such a thing:
Code:
------------------------------------------------------------------------------------------------------------------------
Normal installation (default selected)
Advanced installation
|
|---> if the user selects this the following would appear:
|
|- Default installation method
| (if you're not sure select this one)
|
|- Recovery installation method
| (if you have TWRP installed at BOOT partition only!!! some more detail hints etc)
------------------------------------------------------------------------------------------------------------------------
That would avoid having 2 installation zips which both need to be maintained and it will be clear enough (or can be made more clear) I believe..
xdajog said:
Hm the mentioned adb options are already included in sediKERNEL. I remember that I added them because I thought it could make sense
The trick is to watch the existence of adb while booting up because the mentioned setting will start adb for a short time only!
I use this while booting up:
Code:
while [ 1=1 ];do sleep 2 && adb devices;done
When you see your device connect with adb and you should be there.
The following settings are made in default.prop
Code:
ro.secure=0
ro.adb.secure=0
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.lge.eula_agreement=true
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mtp,adb
So there should be everything you need in place. I think the reason why it was not working for you was that you do not connect to adb while booting.
The kexec-patches removed sediKERNEL is not ready yet.. may come today or tomorrow..
Click to expand...
Click to collapse
If adb is already configured in v1.2, I will roll with that.
xdajog said:
really? I think that would makes life much easier.. I think about such a thing:
Code:
------------------------------------------------------------------------------------------------------------------------
Normal installation (default selected)
Advanced installation
|
|---> if the user selects this the following would appear:
|
|- Default installation method
| (if you're not sure select this one)
|
|- Recovery installation method
| (if you have TWRP installed at BOOT partition only!!! some more detail hints etc)
------------------------------------------------------------------------------------------------------------------------
That would avoid having 2 installation zips which both need to be maintained and it will be clear enough (or can be made more clear) I believe..
Click to expand...
Click to collapse
Oh, that sounds great! I was avoiding the possibility where there is two (small) buttons that decide which route to go. Thus, mis-"clicking" on the wrong one would cause a lot of headaches for the user.
If we can have a summary page of the options before flashing, with the opportunity to go back, that would make it bulletproof!
joel.maxuel said:
If adb is already configured in v1.2, I will roll with that.
Click to expand...
Click to collapse
yeah its in there..
Oh, that sounds great! I was avoiding the possibility where there is two (small) buttons that decide which route to go. Thus, mis-"clicking" on the wrong one would cause a lot of headaches for the user.
If we can have a summary page of the options before flashing, with the opportunity to go back, that would make it bulletproof!
Click to expand...
Click to collapse
I would do it really near bulletproof:
The user would be asked at least 2 or 3 times when the advanced mode selected and get information about some background details what that special option means.
And yes you could step back to the very first selection when you decide that this was not the correct option you want. no problem sir
November 25th nightly released. Please see OP for details/download. I think we are now in beta phase!
Investigate the ability to assign a custom app to the keyboard key currently reserved for T-Mos "Write & Share" app.
Click to expand...
Click to collapse
One question regarding that:
I see that "Write & Share" thing now every time when opening the hw keyboard.
In my case it opens AK Notepad which is an app i installed.
I wish we could disable that behaviour completely somehow..
xdajog said:
One question regarding that:
I see that "Write & Share" thing now every time when opening the hw keyboard.
In my case it opens AK Notepad which is an app i installed.
I wish we could disable that behaviour completely somehow..
Click to expand...
Click to collapse
Does anything happen if you freeze AK Notepad and then press that button? It's possible another app will take it's place, but I am curious about it's function because I haven't looked at it yet. I didn't know where to start with this one, but it gives me a clue.
You on hLe Storm now?
joel.maxuel said:
Does anything happen if you freeze AK Notepad and then press that button?
It's possible another app will take it's place, but I am curious about it's function because I haven't looked at it yet. I didn't know where to start with this one, but it gives me a clue.
Click to expand...
Click to collapse
I try to do so when my wife is willing to give it to me
You on hLe Storm now?
Click to expand...
Click to collapse
yes latest hLe version but with sediKERNEL v1.5 because the kernel code is not kexec patched there.
joel.maxuel said:
Does anything happen if you freeze AK Notepad and then press that button?
Click to expand...
Click to collapse
Cool idea yes when I freeze ak notepad it will do nothing when opening the keyboard! That could be some kind of workaround.
I wondering if the slide open is an action / android intent which could be catched.. adb logcat would also be interesting when that happens..
hm i would like to really have a develop device
-----
Sent from my SGH-I927 using XDA Android mobile app
---------- Post added at 10:43 PM ---------- Previous post was at 10:34 PM ----------
Ah and one another thing: the physical keyboard backlight is very low and too short on as it could be useful.
I would like to have that optimized I know that there was the same issue with my Samsung Captivate Glide and it was fixed by replacing the liblights module amongst some other things.
I think we could do the same with the F3Q.. I may look into that some day
-----
Sent from my SGH-I927 using XDA Android mobile app
xdajog said:
Cool idea yes when I freeze ak notepad it will do nothing when opening the keyboard! That could be some kind of workaround.
I wondering if the slide open is an action / android intent which could be catched.. adb logcat would also be interesting when that happens..
hm i would like to really have a develop device
-----
Sent from my SGH-I927 using XDA Android mobile app
---------- Post added at 10:43 PM ---------- Previous post was at 10:34 PM ----------
Ah and one another thing: the physical keyboard backlight is very low and too short on as it could be useful.
I would like to have that optimized I know that there was the same issue with my Samsung Captivate Glide and it was fixed by replacing the liblights module amongst some other things.
I think we could do the same with the F3Q.. I may look into that some day
-----
Sent from my SGH-I927 using XDA Android mobile app
Click to expand...
Click to collapse
Could start with this:
Code:
12-01 20:27:26.215 637 728 D WindowManager: ConfigurationLocked() conf= null
12-01 20:27:26.245 637 728 D WindowManager: ConfigurationLocked() conf= {0.0 0mcc0mnc (no locale) sw320dp w533dp h294dp nrml long land ?uimode ?night finger qwerty/v/v -nav/h-1fontTypeIndex}
12-01 20:27:26.245 637 728 I ActivityManager: Config changed: {1.0 302mcc270mnc en_US sw320dp w533dp h294dp nrml long land finger qwerty/v/v -nav/h s.900fontTypeIndex}
12-01 20:27:26.255 948 948 V xt9input_alpha: alpha_getKdbId(context(0x5B60F338))...
12-01 20:27:26.255 948 948 V xt9input_dbregistry: keyboard2skid(qwerty)...
12-01 20:27:26.255 948 948 V xt9input_dbregistry: keyboard2skid(qwerty)... done : 0x0100
12-01 20:27:26.255 948 948 V xt9input_alpha: alpha_data::hasKdbLoadCallback()... done : true
12-01 20:27:26.255 948 948 V xt9input_alpha: alpha_getKdbId(context(0x5B60F338))... 0x0109
12-01 20:27:26.285 637 728 D LockPatternUtils: OMADM Lock is OFF
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_setLanguage(context(0x5B60F338))...
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_data::setLanguage(0x109):set...ok
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_setLanguage(context(0x5B60F338))...success
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_setAttribute(context(5B60F338))...
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_controller::setAutoCorrectionMode(3)
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_data::setRegionalCorrection(OX109) - status(0)
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_data::setSpellCorrectionMode(1)...status = 0x0
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_setAttribute(context(5B60F338))...success
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_setAttribute(context(5B60F338))...
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_controller::setNextWordPrediction(0)
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_setAttribute(context(5B60F338))...success
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_setAttribute(context(5B60F338))...
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_setAttribute(context(5B60F338))...success
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_setAttribute(context(5B60F338))...
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_data::setWordCompletionPoint(0x1)...status = 0x0
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_setAttribute(context(5B60F338))...success
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_hasLdb(context(0x5B60F338))...
12-01 20:27:26.295 948 948 V xt9input_dbregistry: DBRegistry::get_ldb_path(0x0109)...LG_902_r1-16_ENubUN_xt9_ALM.ldb
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_hasLdb(context(0x5B60F338))... 0x0109=>1
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_hasLdb(context(0x5B60F338))...
12-01 20:27:26.295 948 948 V xt9input_dbregistry: DBRegistry::get_ldb_path(0x0109)...LG_902_r1-16_ENubUN_xt9_ALM.ldb
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_hasLdb(context(0x5B60F338))... 0x0109=>1
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_hasLdb(context(0x5B60F338))...
12-01 20:27:26.295 948 948 V xt9input_dbregistry: DBRegistry::get_ldb_path(0x0109)...LG_902_r1-16_ENubUN_xt9_ALM.ldb
12-01 20:27:26.295 948 948 V xt9input_alpha: alpha_hasLdb(context(0x5B60F338))... 0x0109=>1
That might be it.
Yeah I wonder if the backlight could be tweaked as well. Doesn't work when you want it to (like the lockscreen).
Hm could you do this:
adb shell
tail -f /proc/kmsg
Then open the keyboard and wait until the lights of the keyboard go off . cancel the tail command and use e.g pastebin for the output
-----
Sent from my SGH-I927 using XDA Android mobile app
December 3rd nightly released (sediKERNEL and SuperSU updated). As usual, please see OP for details/download, and now second post for change log.
xdajog said:
Hm could you do this:
adb shell
tail -f /proc/kmsg
Then open the keyboard and wait until the lights of the keyboard go off . cancel the tail command and use e.g pastebin for the output
Click to expand...
Click to collapse
Unfortunately there is no output. I Ctrl+C'd when I realized I wasn't going to get anything (even after running as superuser). Also, interestingly enough (going back a few posts), my "Write and Share" button still brings up the appropriate app!
joel.maxuel said:
Unfortunately there is no output. I Ctrl+C'd when I realized I wasn't going to get anything (even after running as superuser). Also, interestingly enough (going back a few posts), my "Write and Share" button still brings up the appropriate app!
Click to expand...
Click to collapse
oh I'm sorry tail will not work here, we must use cat instead
could you try:
Code:
adb shell
su
[B]cat[/B] /proc/kmsg > /tmp/dmesg.log
--> slide open, wait until lights going off, slide close
adb pull /tmp/dmesg.log
if the above does not work (only then):
Code:
adb shell
su
while true; do dmesg -c >> /tmp/dmesg.log && sleep 2 ;done
adb pull /tmp/dmesg.log
upload /tmp/dmesg.log
thx
xdajog said:
oh I'm sorry tail will not work here, we must use cat instead
could you try:
Code:
adb shell
su
[B]cat[/B] /proc/kmsg > /tmp/dmesg.log
--> slide open, wait until lights going off, slide close
adb pull /tmp/dmesg.log
if the above does not work (only then):
Code:
adb shell
su
while true; do dmesg -c >> /tmp/dmesg.log && sleep 2 ;done
adb pull /tmp/dmesg.log
upload /tmp/dmesg.log
thx
Click to expand...
Click to collapse
Achieved.
http://pastebin.com/nCHnY2Qu
A bit modified though. Used method one (saving to /sdcard as it didn't like /tmp), opened keyboard, pressed the "write and share" button, closed keyboard.