Flashable Zips, need assistance - HTC Desire S

Hi everyone,
Well I have a htc saga that is s-off and I have flashed different custom roms many times. Flashed a different radio or two but when I go to the sticky Thread below and try to flash keyboards and boot animations well there just not working.
USEFUL LINKS
[DOWNLOAD] Flashable ZIPs : Keyboards, Boot Animations and More.
[FIX] For wifi connection dropping too easily/often
[MISC] Enable Adhoc Networks
[MOD] IncrediControl - Easy GUI Voltage Control
[TWEAK][GPS]Get your GPS configured properly
[INFO] Android hidden secret phone codes..(Not for beginners)
[TWEAKS]Tweaks, a place to start.
[TWEAKS][SCRIPTS] Collection of 'em all - build.prop; init.d; etc.

monitormode said:
Hi everyone,
Well I have a htc saga that is s-off and I have flashed different custom roms many times. Flashed a different radio or two but when I go to the sticky Thread below and try to flash keyboards and boot animations well there just not working.
USEFUL LINKS
[DOWNLOAD] Flashable ZIPs : Keyboards, Boot Animations and More.
Click to expand...
Click to collapse
Hello,
You should really post this problem into the thread that you talking about, the one from which the ZIP appear not to be working, (the thread below I believe), I remember that the owner said he had tested all of the links and therefore maybe he'll be able to offer you further advice and discover what it is that you are doing wrong.
I'd suggest that you try to be more specific with what exactly you've tried and what didn't work.
[DOWNLOAD] Flashable ZIPs : Keyboards, Boot Animations and More.
Good luck

try extracting the boot animation and push to system/customize/resources
I hope you are that intelligent for renaming the boot animation and down animation as it is in ROM
Well anyways which ROM are you on..
I saw in Android Kitchen an option for enabling bootanimation, so there may be chance that your ROM doesnt have the option enabled

Sorry for such a quick thread.
However I did try to post this thread in the development section but was not allowed yet.
I did work out how to get the boot animation working.
But I still need help finding the ADVICE on how to install the keyboard.
If I find the advice I should be ok.
I flash the keyboard zip in recovery with no luck.
I can not find commands or even know if emulator is a option to install keyboard zip.
I'm also looking for adb commands.
I found a rar file for a keyboard.zip but I'm not sure how to install that either.
Caynogenmod. 7.1.0 -rc1 desire s -nexx is my rom of choice.

monitormode said:
Sorry for such a quick thread.
However I did try to post this thread in the development section but was not allowed yet.
I did work out how to get the boot animation working.
But I still need help finding the ADVICE on how to install the keyboard.
If I find the advice I should be ok.
I flash the keyboard zip in recovery with no luck.
I can not find commands or even know if emulator is a option to install keyboard zip.
I'm also looking for adb commands.
I found a rar file for a keyboard.zip but I'm not sure how to install that either.
Caynogenmod. 7.1.0 -rc1 desire s -nexx is my rom of choice.
Click to expand...
Click to collapse
There is a link to adb in ben_pyett's signature as well as in mine.
Today we have a Stable CyanogenMod 7.1 for Desire S thanks to Nexx and SuperKid efforts. So flash the stable version it is much more fixed first.
Then to have a new keyboard layout (it is installed as an app) - you have to start it to be active (try in settings -> keyboard and language)
For the boot animation the folder to copy the files to (you can do this with any root file explorer instead of flashing or you can repack the zip with the proper path and modify the update script) in CyanogenMOD is /system/media not /system/customize/resource like in the zip...
Good luck

monitormode said:
Sorry for such a quick thread.
However I did try to post this thread in the development section but was not allowed yet.
I did work out how to get the boot animation working.
But I still need help finding the ADVICE on how to install the keyboard.
If I find the advice I should be ok.
I flash the keyboard zip in recovery with no luck.
I can not find commands or even know if emulator is a option to install keyboard zip.
I'm also looking for adb commands.
I found a rar file for a keyboard.zip but I'm not sure how to install that either.
Caynogenmod. 7.1.0 -rc1 desire s -nexx is my rom of choice.
Click to expand...
Click to collapse
This isn't a development issue so shouldn't be posted in that area - so luckily you weren't able to do so.
You must explain what you mean by "I flash the keyboard zip in recovery with no luck." was there an error or did it just not work after you'd flashed?
You may have more success with a response if you look at the thread for the ROM that you are using and when you have enough posts you post into the thread.

Related

Read this before posting. MT4G Slide Compendium

The Almost Complete Compendium for MT4G Slide (Read This before Posting)
Note as of 12/22/2011 the ota update is not rootable (H boot 1.45.0013)
and s-off cannot be obtained. If you updated with s-off it is possible to revert back. [url='http://forum.xda-developers.com/showthread.php?t=1421258"] Reference thread [/url]
Also, people who used HTC unlock and have s-on will have trouble flashing roms that are not gingerbread based.
Table Of Contents
1. XDA Lingo
2. MT4G Slide Specs.
3. S-Off, Root, Recovery, Backup, Unroot
4. ROMS, Kernels, Fixes, Mods
5. Network (Unlocking, Backtrack)
6. Apps
7. Development Section
8. Credits
Section One
READ FIRST
READ SECOND
READ THIRD
This is really helpful if a person is new to the forums. Some Lingo, Jargon!!
S-Off: This term is used when describing the security radio. With S-on only signed ROMs may be flashed, when S-off unsigned ROMs may be flashed IE custom ROMs.
Root: This means the user will have unrestricted full access to almost the entire system stack. Another way of describing it would be, having administrator rights on a windows computer
Custom Rom: This stands for “read only Memory”. With Android OS, a custom rom allows you to change things that were un-changeable.
Hybrid ROM: When referring to the MT4G Slide. This ROM contains both HTC Sense and AOSP Theme.
(Unlocked)Bootloader: Loads the core operating system. Unlocked bootloader means users can modify what files the bootloader opens.
H-Boot: Hitting power+volume down after a power down or restart brings up the H-boot (skating androids). This is used to get into recovery and can also be used to flash files using the proper file name.
Fastboot: Fastboot is the name of a tool used to manipulate the flash partitions of the Android developer phone. It can also boot the phone using a kernel image or root filesystem image which reside on the host machine rather than in the phone flash
Zipalign: Is an archive alignment tool. The benefit of zipalign is a reduction in the amount of RAM consumed when running the application.
A.O.S.P "Android Open Source Project": Pure google source untouced by carriers and phone manufacturers.
SDK ADK: “Software Development Kit”” Android Development kit” A suite of tools that helps developers create software for the Android OS.
ADB: “Android Debug Bridge” Allows a user to control and interface with the Android OS.
SBF: System binary file. “I sbfed back to stock” Meaning, I reverted my phone back to stock using a system binary file with a stock image.
Kernel: This is the center of the computer operating system. It provides basic services to the other parts of the system.
Overclock: Forcing the processor to increase its clock rate (therefore more cycles per second). Normally used to get better performance.
Underclock: Reducing the processor clock rate (less cycles per second). This is used to get battery performance and increase processor life.
Undervolt: Lowering the voltage while still maintaining clock rate. This is used to help save power and heat reduction.
Frosted/Defrost: A term used when freezing (frosted) an application or unfreezing (defrost).
Bloatware/Debloat: The many useless applications that carriers add onto the stock os (bloatware). Debloat means that the bloatware has been removed.
Master Subsidy Lock (MSL): Many phones are sold below cost, (at a loss to the carrier,) with the expectation that the money will be recouped in the cost of the monthly service plan. The up-front loss that is later recouped is called a Subsidy.For this to work financially for the carrier, the user must not buy the phone and then use it with a different carrier.The carriers slap on a MSL so the user cannot switch service providers.The term "unlock" means to get the MSL code to free the phone from the carriers lock.
Section Two
MT4G Slide Specs.
Phone specs:
Phone Scoop
[url='http://www.t-mobile.com/shop/Phones/cell-phone-detail.aspx?cell-phone=T-Mobile-myTouch-4G-Slide-Black"]T-Mobile[/url]
HTC
Snapdragon
"Best Still Image shooter" according to PC World
T.V Out
Section Three
S-Off, Root, Recovery, BackUp.
S-Off and Root
How to find out S-On or S-Off / Booting Into Hboot
Radio - Necessary to recover botched radio install Stock Radio Another Stock Radio Thread
S-OFF for Retail (S-ON) Devices, NOTE ADDED 8/17/11
Revolutionary's site also has the root zip that is needed. Does this give me root?
Boot into H-boot, then recovery, use camera button and select "install zip from sd card". When zip is done reboot phone, check superuser.
PERMANENT-ROOT (NEW!) & Temp-Root (v2) for any MT4GS (Windows) Great Guide with very good information!
Recovery
[RECOVERY] Official CWM Recovery v5.0.2.7
Thanks Undeadk9 for install guide.
Also, if using an older ROM version of Sense On Crack, Senseless, Virtrous, etc both the system and data need to be mounted.
ROM Manager is also supported for flashing CWM Recovery. Simply download ROM manager, click flash recovery at the top. Then select our phone. Follow the directions.
Directions:
1. Make Sure Your On a WiFi connection.
2. Go here: http://www.clockworkmod.com
Go to recoveries, Download v5.0.2.7 recovery for doubleshot
3. Download Term Emulator
4. Using root explorer, move the recovery image to /data/local, then mount System r/w in root explorer, then press the home button.
5. Then open Term emulator and this....
su
dd if=/data/local/recovery-clockworkmod-5.0.2.7-doubleshot.img of=/dev/block/mmcblk0p21
Press ENTER
6. It should say transferring bytes blah blah
7. Open ROM manager and press reboot into recovery.
8. If it says v5.0.2.7 then You are done.
ClockworkMod Recovery 4.0.0.9 for the T-Mobile myTouch 4G Slide (MoDaCo edition)
*Older Version*
I took out the terminal emulator post in the thread which is how I upgraded my recovery. The words and numbers must be exact.
here is the OP Thanks
1. Download Recovery 4.0.0.9 from Modaco's website
2. Using Root Explorer, find the file in your downloads folder on the sdcard.
3. Paste the recovery img file into your phone's /data/local folder.
4. In terminal emulator, first type "su" and then type "'dd if=/data/local/doubleshot.clockworkmod.4.0.0.9.modaco.img of=/dev/block/mmcblk0p21" and let it transfer the recovery file.
Re-Cap How To Turn S-Off, Install MoDaCo Clockworkmod Recovery, and Install a Rom For Dummie
Backup (Read and Re-Read this section)
Backups - After Rooting, before ROMing, take this step
Unroot
For The What Ifs
Section Four
Roms!Roms!Roms
Difference between full rom and patch
Basic Installation of a NEW ROM
1. MAKE NANDROID BACKUP OF STOCK ROM
2. REBOOT INTO RECOVERY
3. WIPE DATA AND CACHE
4. FORMAT DATA
5. FORMAT SYSTEM
6. WIPE BATTERY STATS "OPTIONAL BUT HIGHLY RECOMMENDED"
7. WIPE DALVIK CACHE
8. INSTALL ROM
9. REBOOT
10*. LET PHONE SET FOR 5-7 MINUTES.(see below)
*The system is still building symlinks and installing things behind the scenes on first boot of a fresh installation. If you choose to play with it before the 5 minute mark, you risk losing data that has yet to be written. This can lead to buggy performance and issues the DEVS will have a hard time figuring out.
For patches
Backup
1. Wipe cache
2. Wipe davik
3. Flash Patch
4.Reboot
Stock Roms
12/Aug 1.28.531.9 r1 - HTC Doubleshot Stock ROM Rooted and decodexed
Pure Stock Doubleshot, Root/Deodex/Busybox/Opt/Zip
Ice Cream Sandwhich
[ROM][Jan 5 2012] Pyr-o-Ice ICS 0.3.0 alpha (Android 4.0.1) |Camera(photo)|FaceUnlock
Android Open Source Project (AOSP) Roms
CM7
Sense Roms
Virtrous
Crack Injected Sense
BulletProof
Touch 4G Slide DoubleShot Lite
*These Roms Have active Developer support. If I missed a ROM please message or post and I will fix.
Kernels
BoneStock Kernel
Unity V2
Kanged
Fixes, Mods
GPS Fix
Safe Bloatware Removal
Turn off system update for good
*Data Connectivity Fix
*Clutter Cleanup
*indicates stock ROM safe
Section Five
Networking(Unlock,Backtrack)
Unlock:Use method one
Another Way to Unlock the MSL
Backtrack (offensive network secruity)
Section Six
Apps
Good App suggestions and reviews
Section Seven
Development Section
This section is intended for DEVS and beginner DEVS. If you have a question ask before doing something.
MT4GS Stock App Developers Reference
Partions - memory address listing
ADB,SDK,JDK
Fastboot.Exe is in the attachments incase you did not get it. Put the .Exe in platform-tools folder.
Blue61x's Guide to setting up a fresh Dev Computer XP
ADB Workshop by Adrynalyne and Guide by Captainkrtek
Understanding Basic ADB Commands
Dev guide to adb
Key Mapping
Genius button to search
Hardware Key mapping and Flashable zips and requests
LockRing Editing
[How-To] Custom Sense Lockring on the MT4GS - easy step-by-step.Part 1
[How-To] Edit .9.png files for the MT4GS - step-by-step.Part 2
[How-To] Edit Mode10 Files for the MT4GS - step-by-step. Part 3
Tools and Dowloads
MR.Root by XMC Wildchild22 Great scripts!!!
SuperOneClick Root
Section Eight
Credits
I am adding more sections, more links and more information as well as some more jargon.
Pm's welcome for mistakes, more information, etc. ( I am human).
Thanks Blue6IX,Very involved with the creation of this compendium
I thank all the Devs, Mods,end users, supporters and noobs for helping me compile this information. I take no credit for this as it's an orangized Hub for all of our information.
Change Log: 11/02/2011 Added New CWM Recovery, CM7, Mods and Fixes section. Changed name of Unlocking section to networking. Added backtrack.
11/06/2011: Added new terminology.Updated and split the ROM section into aosp and sense roms. Added another way to obtain an unlock code. Added development Section.
11/11/2011: Added new terminology. Added new section to ROM: Hybrid. Added Doubleshot Lite to ROM section. Moved Key mapping section to dev. section. Added ADB section to dev. section. Edits.
11/22/2011: Added new terminology. Added Rom Manager is now supported for flashing CWM. Minor Edits.
12/21/2011: Updated Dev. Section and added fastboot.exe to attachments
1/05/12 : Added ICS Rom section, Added tools and download section, Added Blue's guide and XMC's root tool.
This should help clear up some of the oft-asked questions for people new to the device.
Droidmoder really put a lot of effort into making this happen!
Edit - How did I forget to click thanks on the OP? Dec 14th, 2011
Blue6IX said:
This should help clear up some of the oft-asked questions for people new to the device.
Droidmoder really put a lot of effort into making this happen!
Click to expand...
Click to collapse
Blue6IX,
thanks for your help. You helped more than you think you did!
Blue6IX said:
The system is still building symlinks and installing things behind the scenes on first boot of a fresh installation. If you choose to play with it before the 5 minute mark, you risk losing data that has yet to be written.
The system will serve you, the user, before itself, and will drop from memory things it still needs to write to process your requests. This can result in buggy performance or problems down the line, and lead to frustrating issues that developers of the ROM can't figure out - because no one else will have these problems. Please be advised of this.
Click to expand...
Click to collapse
Added to step ten.
Very nice write up =D.
ekoee said:
Very nice write up =D.
Click to expand...
Click to collapse
Yes, thank you very much! Now the goal is to keep it up to date which will probably turn into more work than you want, but thank you!
unclespoon said:
Yes, thank you very much! Now the goal is to keep it up to date which will probably turn into more work than you want, but thank you!
Click to expand...
Click to collapse
No problem.
Sent from my Crack Injected Doubleshot using xda premium
Great Job!
Suggestion: a section on key remapping? (there was a thread somewhere but never got completed)
Etn40ff said:
Great Job!
Suggestion: a section on key remapping? (there was a thread somewhere but never got completed)
Click to expand...
Click to collapse
I'm going to add this tonight. At work. I have that thread alreay
Sent from my Crack Injected Doubleshot using xda premium
Etn40ff said:
Great Job!
Suggestion: a section on key remapping? (there was a thread somewhere but never got completed)
Click to expand...
Click to collapse
Two threads actually.
Original
Then I made one for requests that people want in flashable zip form:
Requests
So technically, there is no need to 'finish' the first one, and I support my request thread as time allows. It's set up so any dev can come in and handle requests, and there are a few floating around here that would be more then happy to help.
by finish I refer to ekoee's post on shift+alt keys, either it never appeared or i could not find it at the time
Etn40ff said:
by finish I refer to ekoee's post on shift+alt keys, either it never appeared or i could not find it at the time
Click to expand...
Click to collapse
Ah, good catch - i'd forgotten about that with everything else that's been going on.
Wonder if someone will put time into figuring it out?
I bet the answer to that will also lead to the answer for getting other languages supported on the hardware keyboard.
Yeah sorry about that, I haven't had the time to start pulling apart key mappings. Ill make sure to get on it when work settles down.
ekoee said:
Yeah sorry about that, I haven't had the time to start pulling apart key mappings. Ill make sure to get on it when work settles down.
Click to expand...
Click to collapse
I thinking about moving key mapping in the dev section. Wouldn't it be more of a devlopmental thing?
Btw I'm going to refurb the dev sections with links and guides on adk adb and fastboot .
sent from my sense on crack MT4G Slide using xda premium
What does "nandroid" backup mean?
I have backed up with the recovery and I have backed up with ROM manager. What is nandroid?
sandiegoan said:
I have backed up with the recovery and I have backed up with ROM manager. What is nandroid?
Click to expand...
Click to collapse
Nandroid is what clockwork mod calls the actual backup file.
Backup means to create a backup.
Nandroid is the file backup of your system . Hence nan (small) and droid the os. So you can also say you made a small android os .
Ill add this to terminology when I get to it. Hope this helped.
sent from my Agent Orange MT4G Slide using xda premium
Very helpful info, I unrooted, but theunlockr guide stated that this would turn the phone back to S-ON, but it hasnt, i have the stock tmobile rom back on the phone, but HBOOT states I still have S-ON, is this a problem? is there a way to get S-ON again so I can start the root process over? or am is there shortcuts I can take to root now that I have S-off?
I actually do not know. I would assume s on is attainable. Why would you want s on, you can re root without going threw rev again.
Follow the root guide its easy enough.
sent from my Agent Orange MT4G Slide using xda premium
You mean the guide from theunlockr? or another guide? if its another guide please post it? as far as following theunlockr method, in order to gain perm root it stated I have to first boot into recovery, and then flash the ZIP file, but when I try to go into recovery, I get a red exclamation mark, even though I have S -OFF

Motorola Fire XT316/XT311/XT317/XT530/XT531/XT532 - All About It

Hello Fire owners!
I open this thread to keep all things of Fire together, only one thread, everything here.
So here we go:
THIS THREAD IS FOR MOTOROLA XT311/XT316/XT317, XT530/XT531, XT532 AND XT611 (aka SMARTFLIP) ONLY. IF YOU HAVE A SIMILAR THREAD, PLEASE PM ME AND PASS ME YOUR POST. LET'S KEEP XDA ORGANIZED!
CWM FOR FIRE XT XT530/XT532, SPICE XT XT531, FIRE XT311, SPICE KEY XT316 OFFICIALLY LAUNCHED
This thread was focused in the 2nd-Init for XT31X and XT530, 531 and 532. For almost six months, we worked patientlly to get the CWM working on our devices. The wait for CWM is OFFICIALLY OVER. In a couple days ago, our friend aweosomeabhijeet found a way to run CWM on Gingerbread. The tutorial (made by himself) will be posted NOW:
Hey Guys
All your wait is over.
Here I'll tell you how to get CWM for Moto Fire XT.
Disclaimer : I'm not responsible for any damage to your phone. I have tried it and finished successfully.
Try only if you know little bit about android.
This is beta version. However, a dev is working on not using a PC to reboot back into system, and is trying to make the installation simplified.
Lot of thanks to andrewidya
Required things
1. Rooted XT
2. Pc
Download these things on your phone:
1. Terminal emulator
2. Busybox(Open it and install)
3. Root browser
4. Pimp my Rom
5. ES file explorer
You can find all of them in the Play Store.
If you have done with it download the attachment.
Now main work.
It is not easy though but I think everyone can do it.
Steps:
1. Extract the attachment and copy it to your sdcard
2. Mount /system as RW.
3. Open Root Browser and copy bootmenu folder from sdcard/XT530 and paste it in /system.
4. Open Pimp My Rom and Add universal init.d support.
5.Create 97bootmenu manually.(For this using ES file explorer is recommended)
Steps:
a.Open /system/etc/init.d
b. Create a file, name it 97bootmenu.
c. Open the file as text
Type:
Code:
#!/system/bin/sh
stop
exec /system/bootmenu/binary/bootmenu
d.save the file
6. Change permissions of 97bootmenu to rwx r-- r--
7. Reboot your phone.
Now your phone will start at bootmenu.
Select Recovery>Custom Recovery
PS: If you want to get back the phone to boot normally. Just connect it to PC, open CMD and type
cd path-to-adb.exe
adb shell
rm -R /system/etc/init.d/97bootmenu
exit
adb reboot
I succeeded here's the video:
http://youtu.be/OyHwMqkBArk
Sorry for poor camera quality.
Thanks to all the members.
Special Thanks to:
Gentrylamp for creating bootmenu.
7amdoun for his great knowledge and modding bootmenu for XT530.
andrewidya for correcting me at every point.
Mazen.kh for everything he did.
Mr.Indigo for giving us hopes.
And all other members whom I forgot to mention here.
Click to expand...
Click to collapse
This above quote is the 1ST post of his thread.
THANKS TO HIM AND TO ALL OF THE DEVELOPERS WHO HELPED TO GET THIS.
ROOTING & UNROOTING
You will follow this tutorial if you have 2.3.5 version of Android:
Downloads:
Here are the apps/files needed for Rooting -
1. SuperOneClick 2.3.3.0
2. SUT LR 1.8.2 (Doesn't seem to be working on 64-bit systems)
3. FXX_PR3_NV.xml and NvDefinition.xml [ATTACHED]
Before Rooting:
Prepare your phone by doing the following:
- Go to Settings > Applications > CHECK "Unknown Sources"
- Go to Settings > Applications > Developer > CHECK "USB Debugging" and "Stay Awake"
- Connect your phone via USB, when prompted DO NOT select USB Mass Storage.
- Extract FXX_PR3_NV.xml and NvDefinition.xml from the attached zip file in to a folder
- Now, install SUT LR, run the app
- Select the FXX_PR3_NV.xml [ensure NvDefinition.xml is also in the same folder as FXX_PR3_NV.xml]
- Your phone will restart.
It does NOT erase anything on the phone, since it only patches the ROM.
Rooting:
After the phone restarts, open SuperOneClick and select root. It will take less than a minute to finish.
Click to expand...
Click to collapse
From: Motorola Fire XT / XT-530 / XT-531 ROOTING! - NEW METHOD - [ DEVS NEEDED ] posted by the user jeet.9890427233
Official Motorola SBF Files
Link: www.grupoandroid.com/topic/43248-motorola-firmwares-superthread/
Just copy and paste.
Custom ROMs
None yet.
Custom Recovery
None Yet.
Custom Kernels
None yet.
Applications that you can remove​There are some apps that you can remove, here is the complete list with all apps:
My ROM is VIVO 2.3.5 and can be different in some ROMs.
7x27_FQC or FQC Program= YES, maybe is F actory Q uality C heck or other thing....
AccountAndSyncSettings.apk= NO
ApplicationsProvider.apk= NO - Will brick apps install/uninstall
APR.apk= ?
BatteryManagerAP.apk= YES
BatteryProtect.apk= ?
Bluetooth.apk= NO
BlueToothTestMode.apk= NO
Browser.apk= YES
Calculator.apk= YES
Calendar.apk= NO
CalendarProvider.apk= NO
Camera.apk= NO
CDA.apk= ?
CDASYSTEM.apk= ?
CertInstaller.apk= NO
Contacts.apk= NO
ContactsProvider.apk= NO
DataConnectionWidget= YES
DateTimeSetup.apk= NO
DbgCfgTool.apk= ?
DefaultContainerService.apk= ?
DeskClock.apk= YES/NO
DMClient.apk= NO
DownloadProvier.apk= NO
DownloadProviderUI.apk= NO
DrmProvider= NO
DxDrmApplication= NO
DxDrmPlugin= NO
ECompassCalibration= NO
Email= NO
Facebook_LT= YES
Fallback= NO
FileManager= YES
FM Radio= ?
Gallery3D= YES, but replace with another gallery app
GenieWidget= ?
- THIS LIST WILL BE UPDATED SOON -
Click to expand...
Click to collapse
If you are a DEV our a guy who can provide a ROM for us, please PM me and i will add you in GTalk. If you have a mod or something useful or want to help me, please PM me and i will add you on GTalk. If we get sucess this thread will be updated!
Thread changelog:
- Initial post
- CG2.smg extractor added to the 2nd Post (THANKS TO: Mazen.kh)
- Chainfire 3D support added ( THANKS TO: Overcrasher)
- Thread stopped a lil bit
- Back with some news
- SUPPORT FOR XT530/531/532 (FIRE XT) Added
- SUPPORT FOR XT317 (FIRE in Brazil) Added
- XT317 kernel tested, but didn't work smoothly as 2.2 kernel
- SUPPORT FOR XT611 (aka SMARTFLIP) added
- SUPPORT FOR XT611 DROPED. See more below.
- CWM FOR FIRE DEVICES LAUNCHED BY aweosomeabhijeet
about CG2.smg
Hey man I'm interested in the thread and i can help you extracting the CG2.smg
Here you are my tut. [for windows] it worked for me
1- unrar the file in the attachments
2- make sure that your file is named to 'CG2.smg' without quotes for sure, and in the same folder..
3- just run the .bat and wait for cmd to finish the job then you will find a folder called 'CG2-extracted' in the same place you extracted my .rar file
Note: you will find in the folder called 'CG2-extracted' some mbn files, systemsec.mbn is the /system folder in the xt311/xt316
extract it easily using unyaffs like a system.img file, if you need help in this PM me. i can help you extracting systemsec.mbn only, i dunno about other files also to repack systemsec.mbn you'll need mkyaffs and i think it's usable on ubuntu only and i can't help you with it
sorry for long reply but press thanks if i helped.
Mazen.kh said:
Hey man I'm interested in the thread and i can help you extracting the CG2.smg
Here you are my tut. [for windows] it worked for me
1- unrar the file in the attachments
2- make sure that your file is named to 'CG2.smg' without quotes for sure, and in the same folder..
3- just run the .bat and wait for cmd to finish the job then you will find a folder called 'CG2-extracted' in the same place you extracted my .rar file
Note: you will find in the folder called 'CG2-extracted' some mbn files, systemsec.mbn is the /system folder in the xt311/xt316
extract it easily using unyaffs like a system.img file, if you need help in this PM me. i can help you extracting systemsec.mbn only, i dunno about other files also to repack systemsec.mbn you'll need mkyaffs and i think it's usable on ubuntu only and i can't help you with it
sorry for long reply but press thanks if i helped.
Click to expand...
Click to collapse
IT WORKED!
Thanks!
It helps me a lot!
Now my device Works!
Thanks!
Sent from my Xt316
Is there any custom rom for XT316/XT311?
luume said:
Is there any custom rom for XT316/XT311?
Click to expand...
Click to collapse
Unfortunately not yet.. Neither custom recoveries
Mr.Indigo said:
IT WORKED!
Thanks!
Click to expand...
Click to collapse
Anytime Sir ! I just want to help in anyway getting this device better, By the way here's a list of useless applications so far !
- 7x27_FQC.apk
- Arabware.apk < 7 megabytes and useless
- Wifipowersavingmode.apk < I think it drains the battery faster -.-
- i also removed all motoswitch APKs, And installed go launcher instead in the system. And removed pre-installed live wallpapers
Also if you have errors like "preparing sd card - checking for errors" in the status bar you can delete system/bin/fsck_msdos since i deleted i get no errors for my partitioned sd card
Q/Request: Do you know how can i customize Notify led ? Like changing color and speed ? also it doesn't work with whatsapp!
Thanks anyway ! Ps. led works by Notifyled.apk.. of course you know xD
And Yeah, i found some srs files also, time ago, i thought it would be awesome to have a panel for it ! but maybe it's the normal speakers at the back and it's drivers..
Mazen.kh said:
Unfortunately not yet.. Neither custom recoveries
Anytime Sir ! I just want to help in anyway getting this device better, By the way here's a list of useless applications so far !
- 7x27_FQC.apk
- Arabware.apk < 7 megabytes and useless
- Wifipowersavingmode.apk < I think it drains the battery faster -.-
- i also removed all motoswitch APKs, And installed go launcher instead in the system. And removed pre-installed live wallpapers
Also if you have errors like "preparing sd card - checking for errors" in the status bar you can delete system/bin/fsck_msdos since i deleted i get no errors for my partitioned sd card
Q/Request: Do you know how can i customize Notify led ? Like changing color and speed ? also it doesn't work with whatsapp!
Thanks anyway ! Ps. led works by Notifyled.apk.. of course you know xD
And Yeah, i found some srs files also, time ago, i thought it would be awesome to have a panel for it ! but maybe it's the normal speakers at the back and it's drivers..
Click to expand...
Click to collapse
No, i don't know, srry!
And we cannot use the control panel with the file incluided in the ROM. Needs a lot of files...
And i'm trying to por XT300 Toggle Widget to XT316. It will be harder but... it's beautiful!
Mr.Indigo said:
No, i don't know, srry!
And we cannot use the control panel with the file incluided in the ROM. Needs a lot of files...
And i'm trying to por XT300 Toggle Widget to XT316. It will be harder but... it's beautiful!
Click to expand...
Click to collapse
It's weird how motorola build their phones and drivers, unlike samsung they give full customization !
And good luck man i wish i could help but i'm not really helpful in porting and modding
Mazen.kh said:
It's weird how motorola build their phones and drivers, unlike samsung they give full customization !
And good luck man i wish i could help but i'm not really helpful in porting and modding
Click to expand...
Click to collapse
Yeah, Motorola lock the bootloader, locks the customization and much more. We need a CWM. FASTER!
Edit: before 2.3 versions, Motorola odexed the roms. All of the files were odexed. But Motorola now deodexed everything. So it will be easier.
And i think we can port the CWM from XT300. So, let's try!
Mr.Indigo said:
Yeah, Motorola lock the bootloader, locks the customization and much more. We need a CWM. FASTER!
Edit: before 2.3 versions, Motorola odexed the roms. All of the files were odexed. But Motorola now deodexed everything. So it will be easier.
And i think we can port the CWM from XT300. So, let's try!
Click to expand...
Click to collapse
I didn't know that there was cwm for xt300, but i think, if there is cwm for xt530/xt531/xt532 it'd be easier to port, since xt53X is to close to our xt311/xt316 and it also have 2.3.5 while xt300 2.1 only
Edit: i think xt311/xt316 users will never have custom recoveries/roms unless the bootloader is unlocked, and it'll be so hard to unlock such bootloader since the phone is not popular
Mazen.kh said:
I didn't know that there was cwm for xt300, but i think, if there is cwm for xt530/xt531/xt532 it'd be easier to port, since xt53X is to close to our xt311/xt316 and it also have 2.3.5 while xt300 2.1 only
Edit: i think xt311/xt316 users will never have custom recoveries/roms unless the bootloader is unlocked, and it'll be so hard to unlock such bootloader since the phone is not popular
Click to expand...
Click to collapse
Some guys tried to do an 2ndInit to maybe try to get CWM work. But didn't worked. A file from the battery (when you turn off the phone and conntect the charger, the big battery icon) was missing. But works without this file.
AND I FOUND WHERE WE CAN ACTIVATE SRS! Is in cda.prop, it's configured to false.
So what happens if i changed the value to true ?
i don't think cda props apply actually i tried to change the value of lock screen support rotation to true and nothing changed.
And Yup i read something about that battery icon too but i didn't understand fully how does that relate to unlocking bootloader
i think the bootloader must get hacked easily since as i see it's a common bootloader in many fones for ex. xt530 xt531 xt532 xt300 xt311 xt316 xt317 or am i wrong ?
If i can test the ROM in my computer (i don't know how to do it), we see if works. And Bootloader it's not the same for every phone series. XT300 executes 2.1 WITH UNLOCKED BOOTLOADER. And XT316 with 2.3.5 WITH THE LOCKED Bootloader.
The SRS file is in the attachments. Just take a look on the 'st line:
BLOCK... I understand that is blocked.
And the battery icon maybe is on a apk or anywhere. We might look better.
EDIT:
I googled around and i found a thread that talks about CG2.smg. They tried to do the same what i doing, and didn't finish very well. The phone was bricked, but they use some files, replace and the ROM was going on very well.
Mr.Indigo said:
I googled around and i found a thread that talks about CG2.smg. They tried to do the same what i doing, and didn't finish very well. The phone was bricked, but they use some files, replace and the ROM was going on very well.
Click to expand...
Click to collapse
i actually didn't understand what you said in the "EDIT" but i read that even with a locked bootloader we can have a custom rom, but not a custom kernel right ?
so you can recompress the edited cg2.smg files and re sbf it again after customizing it or am i saying meaningless words ?
Mazen.kh said:
i actually didn't understand what you said in the "EDIT" but i read that even with a locked bootloader we can have a custom rom, but not a custom kernel right ?
so you can recompress the edited cg2.smg files and re sbf it again after customizing it or am i saying meaningless words ?
Click to expand...
Click to collapse
OK. I will explain the edit first.
They edit the systemsec.mbn, repack the mbn and repack everything. but they've got an error. Then, the phone was bricked and RSD doesn't saw the phone.
A custom kernel will be pretty great, but we have to unlock the bootloader 1st.
Mr.Indigo said:
OK. I will explain the edit first.
They edit the systemsec.mbn, repack the mbn and repack everything. but they've got an error. Then, the phone was bricked and RSD doesn't saw the phone.
A custom kernel will be pretty great, but we have to unlock the bootloader 1st.
Click to expand...
Click to collapse
so what kind of error did they get, cause i wanted to do the same as they and repack the rom as sbf and flash it..
also, can we try porting as .nb0 rom? i can see our stock recovery have the option to flash nb0 files
Mazen.kh said:
so what kind of error did they get, cause i wanted to do the same as they and repack the rom as sbf and flash it..
also, can we try porting as .nb0 rom? i can see our stock recovery have the option to flash nb0 files
Click to expand...
Click to collapse
Maybe... Here is the error they got:
I got this after the flash attempt.
Phone[0000]: Error flashing subscriber unit. Device API error. 0xE002000B Address 0x94C3800 Command: BIN (0xE032300B)
Click to expand...
Click to collapse
I've got from ModMyMobile (M3). They mod and bang! Bricked the device!
But they recovered.
See another error here
The recover is change the FLEX VERSION to please flash please (something like that)
Does this file mean anything ?
Code:
ro.product.model.num=2013
ro.product.name=XT316
ro.product.device=XT316
ro.product.model=XT316
ro.product.brand=Motorola
ro.product.board=XT316
ro.telephony.num.auto.hyphen=false
ro.telephony.gsm.spn.shortname=true
ro.telephony.gsm.wait.switch=true
ro.telephony.rat.network.select=true
ro.telephony.gsm.sms.auto-reg=false
ro.telephony.add.mccmnctable=true
ro.telephony.spn.support.mvno=false
ro.telephony.fdn.data=true
ro.telephony.configurable.mtu=false
ro.nitz.name.ignore.plmns=72405
ro.telephony.cphs-spn.support=true
ro.telephony.dun.show=true
ro.telephony.fast.dormancy=true
ro.tether.denied=false
ro.telephony.mvno.sim.spn=false
ro.telephony.croatia.shortcode=false
ro.CDG_MENU_EVDO_ONLY=false
ro.telephony.custom.showspn=false
ro.telephony.extended.mnc=false
ro.telephony.hidemenu.data=false
ro.telephony.gsm.ecclist=112,911,190
ro.telephony.ecclist=112,911,190
ro.telephony.cdma.ecclist=112,911,190
ro.telephony.gsm.voicemail=*555
ro.telephony.cdma.ecm=false
ro.contacts.number.match.length=11
ro.contacts.number.match.minima=7
ro.contacts.polyphonename=false
ro.sf.lcd_density=120
ro.product.locale.language=pt
ro.product.locale.region=BR
ro.config.dbgcfgtool_config=3
ro.DRM_SOLUTION_ID=1
ro.SYSTEM_CTA_MODEL=false
ro.NETWORK_DISABLE_3G_MODULE=false
ro.USB_PLUG_IN_NOTIFICATION=true
ro.LOCKSCREEN_SUPPORT_ROTATION=false
ro.SETTINGS_ENABLE_MSISDN_ALPHA=true
ro.CC_SEC_INC_CALL_OPTIONS=false
ro.SETTINGS_LANG_HIDE_TW_CHINA=false
ro.CALENDAR_FESTIVALS_OPTION=false
ro.SETTINGS_LOCK_PRELOADED_APN=NONE
ro.PHONE_ENABLE_COUNTRY_CODE=false
ro.MEDIA_ENABLE_SRS=false
ro.FB_ENABLE_HIDE_FOLDER=false
ro.CONTACT_VCARD_VERSION=3.0
ro.NETWORK_SB_CUST_FD_MECH=false
ro.SETTINGS_LOCK_VOICEMAIL_NUM=false
ro.CC_QUERY_CF_ON_BOOT=false
ro.BROWSER_ENABLE_PROXY=false
ro.SETTINGS_REMOVE_SIGNAL_STR=false
ro.SYSTEM_GCF_MODEL=false
ro.CC_HIDE_CB_PW_CHANGE=false
ro.SYSTEM_UI_STYLE_ID=0
ro.SB_SHOW_PLMN=false
ro.SETTINGS_DISABLE_TOUCH_TONE=false
ro.NETWORK_ENABLE_HOTSPOT_SEC=false
ro.CC_ENABLE_MAKE_OOS_CALL=false
ro.NETWORK_NET_MODE_IND=false
ro.NETWORK_ENABLE_OP_LABEL=false
ro.NETWORK_HOTSPOT_AUTO_OFF=false
ro.NETWORK_OP_NAME_OPTION=0
ro.NETWORK_WIFI_SLEEP_POLICY=0
ro.NETWORK_SIGNAL_DISP_STYLE=0
ro.SYSTEM_LED_NOTIFY_STYLE=0
ro.SL_DISABLE_UNLOCK_PROMPT=false
ro.BT_ENABLE_FF_RW=false
ro.MUSIC_DEACTIVATED_BY_FW_BW=false
ro.RSS_DISABLE_COST_PROMPT=false
ro.SETTINGS_HIDE_WIFI_SCAN=false
ro.PHONE_ENABLE_REBOOT_FUNC=false
ro.SYSTEM_SIM_WATCHER=false
ro.CAMERA_DISABLE_H263_ENCODER=false
ro.SYSTEM_SPK_OFF_WHEN_HS_IN=false
ro.NETWORK_REMOVE_GSM_COMBO=false
ro.STANDMODE_ENABLE_TV=false
ro.IME_DISABLE_AUTO_PUNC=false
ro.IME_DISABLE_SHOW_SUGGESTION=false
ro.MEDIA_HIDE_3g2_FILE=false
ro.BROWSER_DL_POPUP_DIALOG=false
ro.CC_HIDE_SIP_UI=false
ro.SYSTEM_DISABLE_LOW_MM_CHECK=false
ro.SYSTEM_ENABLE_FLIP_FONT=false
ro.MUSIC_ENABLE_FORCE_TRNAS_RU=false
ro.DL_PROVIDER_CUSTOMIZED_FUNC=0
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.yt=android-motorola
ro.com.google.clientidbase.am=android-motorola
ro.com.google.clientidbase.gmm=android-motorola
ro.com.google.clientidbase.ms=android-hms-tef-{country}
ro.hwt.softbank=false
ro.cust.cover_shutdown=false
kent_lkc said:
Does this file mean anything ?
Code:
ro.product.model.num=2013
ro.product.name=XT316
ro.product.device=XT316
ro.product.model=XT316
ro.product.brand=Motorola
ro.product.board=XT316
ro.telephony.num.auto.hyphen=false
ro.telephony.gsm.spn.shortname=true
ro.telephony.gsm.wait.switch=true
ro.telephony.rat.network.select=true
ro.telephony.gsm.sms.auto-reg=false
ro.telephony.add.mccmnctable=true
ro.telephony.spn.support.mvno=false
ro.telephony.fdn.data=true
ro.telephony.configurable.mtu=false
ro.nitz.name.ignore.plmns=72405
ro.telephony.cphs-spn.support=true
ro.telephony.dun.show=true
ro.telephony.fast.dormancy=true
ro.tether.denied=false
ro.telephony.mvno.sim.spn=false
ro.telephony.croatia.shortcode=false
ro.CDG_MENU_EVDO_ONLY=false
ro.telephony.custom.showspn=false
ro.telephony.extended.mnc=false
ro.telephony.hidemenu.data=false
ro.telephony.gsm.ecclist=112,911,190
ro.telephony.ecclist=112,911,190
ro.telephony.cdma.ecclist=112,911,190
ro.telephony.gsm.voicemail=*555
ro.telephony.cdma.ecm=false
ro.contacts.number.match.length=11
ro.contacts.number.match.minima=7
ro.contacts.polyphonename=false
ro.sf.lcd_density=120
ro.product.locale.language=pt
ro.product.locale.region=BR
ro.config.dbgcfgtool_config=3
ro.DRM_SOLUTION_ID=1
ro.SYSTEM_CTA_MODEL=false
ro.NETWORK_DISABLE_3G_MODULE=false
ro.USB_PLUG_IN_NOTIFICATION=true
ro.LOCKSCREEN_SUPPORT_ROTATION=false
ro.SETTINGS_ENABLE_MSISDN_ALPHA=true
ro.CC_SEC_INC_CALL_OPTIONS=false
ro.SETTINGS_LANG_HIDE_TW_CHINA=false
ro.CALENDAR_FESTIVALS_OPTION=false
ro.SETTINGS_LOCK_PRELOADED_APN=NONE
ro.PHONE_ENABLE_COUNTRY_CODE=false
ro.MEDIA_ENABLE_SRS=false
ro.FB_ENABLE_HIDE_FOLDER=false
ro.CONTACT_VCARD_VERSION=3.0
ro.NETWORK_SB_CUST_FD_MECH=false
ro.SETTINGS_LOCK_VOICEMAIL_NUM=false
ro.CC_QUERY_CF_ON_BOOT=false
ro.BROWSER_ENABLE_PROXY=false
ro.SETTINGS_REMOVE_SIGNAL_STR=false
ro.SYSTEM_GCF_MODEL=false
ro.CC_HIDE_CB_PW_CHANGE=false
ro.SYSTEM_UI_STYLE_ID=0
ro.SB_SHOW_PLMN=false
ro.SETTINGS_DISABLE_TOUCH_TONE=false
ro.NETWORK_ENABLE_HOTSPOT_SEC=false
ro.CC_ENABLE_MAKE_OOS_CALL=false
ro.NETWORK_NET_MODE_IND=false
ro.NETWORK_ENABLE_OP_LABEL=false
ro.NETWORK_HOTSPOT_AUTO_OFF=false
ro.NETWORK_OP_NAME_OPTION=0
ro.NETWORK_WIFI_SLEEP_POLICY=0
ro.NETWORK_SIGNAL_DISP_STYLE=0
ro.SYSTEM_LED_NOTIFY_STYLE=0
ro.SL_DISABLE_UNLOCK_PROMPT=false
ro.BT_ENABLE_FF_RW=false
ro.MUSIC_DEACTIVATED_BY_FW_BW=false
ro.RSS_DISABLE_COST_PROMPT=false
ro.SETTINGS_HIDE_WIFI_SCAN=false
ro.PHONE_ENABLE_REBOOT_FUNC=false
ro.SYSTEM_SIM_WATCHER=false
ro.CAMERA_DISABLE_H263_ENCODER=false
ro.SYSTEM_SPK_OFF_WHEN_HS_IN=false
ro.NETWORK_REMOVE_GSM_COMBO=false
ro.STANDMODE_ENABLE_TV=false
ro.IME_DISABLE_AUTO_PUNC=false
ro.IME_DISABLE_SHOW_SUGGESTION=false
ro.MEDIA_HIDE_3g2_FILE=false
ro.BROWSER_DL_POPUP_DIALOG=false
ro.CC_HIDE_SIP_UI=false
ro.SYSTEM_DISABLE_LOW_MM_CHECK=false
ro.SYSTEM_ENABLE_FLIP_FONT=false
ro.MUSIC_ENABLE_FORCE_TRNAS_RU=false
ro.DL_PROVIDER_CUSTOMIZED_FUNC=0
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.yt=android-motorola
ro.com.google.clientidbase.am=android-motorola
ro.com.google.clientidbase.gmm=android-motorola
ro.com.google.clientidbase.ms=android-hms-tef-{country}
ro.hwt.softbank=false
ro.cust.cover_shutdown=false
Click to expand...
Click to collapse
This is cda.prop right?
it has some tweaks like build.prop, if you tried to change the mobile model that appears to the market from build.prop it won't work, but if you change it from cda.prop it will work also it have some other tweaks that i actually don't know what's it's use
And Don't Forget Thanks Button ^^
XT316 bricked
Hello guys, sorry if this is not the best place to post a problem but, this is the only one active discussion about XT316 that i have found, i have this phone with Brazil Claro stock 2.3.3 Gingerbread Android installed, then i have installed the ChainFire3D hoping to have better experience with some games...
But i got a bricked phone... when powering on, the phone shows only the Motorola logo, then a black screen with no response, and continous reboot
I started the phone in recovery mode and tryed to perform a Factory Recover, but no sucess, same with Wipe Cache Partition option, so, what is left to do now is my question...

[RECOVERY][HeroC]TWRP 2.2.2.0 touch recovery [2012-08-24]

Team Win Recovery Project 2.2, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG (for 2.2.2.0 compared to 2.2.0.0):
Mostly bugfixes:
Significantly improved sd-ext handling (ext partitions on sdcards)
Changes to kinetic scrolling in file selectors
Fixed a problem with using periods in backup names
Fixed problems in XML layouts with mounting system and USB storage
Fixed a problem with unmounting a partition before formatting during restore
Add Jelly Bean decrypt support
Updated 320x480 theme to match others (thanks to Llewelyn)
Improve "symlinking" of /data/media to either /sdcard or /emmc
Added sanitizing of device IDs for invalid characters (thanks to bigbiff)
Fixed free space calculation when switching backup devices on /data/media devices
Fixed a problem with using OpenRecoveryScript to create a backup without providing a backup name
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
NOTE: If you're coming from another build of TWRP, you may need to go into settings and tap reset defaults to reset the storage paths so that you can see your zip files.
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
thank you for this, ill test asap
if anyone wants a flashable zip, lemme know. i already have it done
edit: works good. only thing is i was flashing a rom (attempting to anyway) and somehow my zip got corrupted and unreadable. never had that happen before. any thoughts? (it was fine when i put it on my sd card, was flashing a 2nd time, so zip had worked previously and all other files on my sd are fine)
Going to flash this now and give it a try. Hopefully it works out good.
whoshotjr2006 said:
if anyone wants a flashable zip, lemme know. i already have it done
Click to expand...
Click to collapse
Throw it up brother!
thanks, always wanted a touch recovery and this one is great, if i could make a recovery touch it would be like this one again thanks
I flashed this a week or two ago and been working awesome! I love it.
i have been using cw recovery all time and always wanted to have a touch screen recovery and this one is sick, my only thing i have found is when i go to restore a backup it cannot find it,(one from cwm recovert). is it that it just cant restore those or did i miss something? no big deal to me ,just wanted to put it out there.
again thanks for this
they are in different folders on the SDCARD, im not even sure they are compatible.
ok cool im trying to do differant things and ill update you either way
would you know off hand where twrp folder would be? im looking if i get it before a reply ill post it
i got it twrp folder
alsp cani get the twrp 2220 in a zip format?
will this recovery work with firerats? on heroc?
dankdank11 said:
will this recovery work with firerats? on heroc?
Click to expand...
Click to collapse
Yes, Firerats has nothing to do with the recovery. Firerats just resizes your data/system/cache portion of the system really so you can install more apps.
I am using it and love it and works awesome on my Hero. :good:
thanks im trying it now, love the use of touch
I am going to leave the automated GooManager install for the Hero on version 2.2.2.0 due to the age of the device and the problems with recovery API 3 and older zips. TWRP 2.3.0.0 does work fine on the HeroC but I'm willing to bet that most zips are using old update binaries that will not install on the new version. If anyone wants to try, you're welcome to download and flash the newer versions manually:
http://techerrata.com/browse/twrp2/heroc
I was going to give 2.3.0.0 a try but like you stated, and someone in IRC said, that most of the zips online for the old Hero are prob all older so going to stick with 2.2.0.0 I think. Thanks for the update though.
Does TWRP require any particular hboot version, or will it function with any of them? I know you need to be on Android 2.3 in order to install TWRP, but I'm wondering... does it also mean that if you flash back to a stock ROM that TWRP won't work properly?
EDIT: My question was obviously stated with some knowledge missing. Recovery is obviously not dependent upon the ROM, as the ROM is loaded after the recovery program is done! But... I'm curious to know, if I made a nandroid backup with TWRP 2.2.2.0, will TWRP2 be able to restore it?
* DELETE *
There has been a small oversight with the GooManager route of distribution and the original post for this particular phone. You must have a PC or have a phone that can flash .zips or has a 2.3 or up ROM installed so it can run GooManager, even though this phones last OTA was Android 2.1, so it probably should have a .zip posted instead.
For example, I have a stock but rooted HTC Hero from Sprint as my backup with the latest OTA. So I can't use this method of install for this recovery without flashing a different recovery first, and then either flashing it as a .zip or upgrading my ROM to a 2.2 or 2.3 based ROM. In reality, I think most will just stick with whatever recovery must be flashed first in this situation as I will, even though I wanted TWRP. That said I think most of the users that use this will just want a .zip.
But there is no .zip posted for the guys that can flash it. This also makes it an overly cumbersome option if the handset is in stock state. As I said, I probably won't bother re-flashing, I kind of like sticking to one recovery on a phone and prefer to do minimal NAND writes.
DizturbedOne said:
There has been a small oversight with the GooManager route of distribution and the original post for this particular phone. You must have a PC or have a phone that can flash .zips or has a 2.3 or up ROM installed so it can run GooManager, even though this phones last OTA was Android 2.1, so it probably should have a .zip posted instead.
That said I think most of the users that use this will just want a .zip.
But there is no .zip posted for the guys that can flash it. This also makes it an overly cumbersome option if the handset is in stock state. As I said, I probably won't bother re-flashing, I kind of like sticking to one recovery on a phone and prefer to do minimal NAND writes.
Click to expand...
Click to collapse
As stated a couple of posts before you:
Dees_Troy said:
I am going to leave the automated GooManager install for the Hero on version 2.2.2.0 due to the age of the device and the problems with recovery API 3 and older zips. TWRP 2.3.0.0 does work fine on the HeroC but I'm willing to bet that most zips are using old update binaries that will not install on the new version. If anyone wants to try, you're welcome to download and flash the newer versions manually:
http://techerrata.com/browse/twrp2/heroc
Click to expand...
Click to collapse
Sent from my SCH-I535 using xda app-developers app
Hippie459MN said:
Yes, Firerats has nothing to do with the recovery. Firerats just resizes your data/system/cache portion of the system really so you can install more apps.
I am using it and love it and works awesome on my Hero. :good:
Click to expand...
Click to collapse
That's good to know. I think I'll give it a shot.

[HOW-TO]Alter updater-script to flash 3.4 kernel based ROMs on lower hboots/firmware

Hi there.
As most of you already know, starting some time ago, CM team has decided to include a script check for firmware/hboot that will allow to flash a CM based ROM only on newer firmware/hboots (2.13.0000, 2.15.0000, 2.15.4444). This is valid for all 3.4 kernel based ROMs (CM 10.2, PACman, PA, Odyssey and so on). This check was introduced because some were reporting problems by flashing such ROMs on lower hboots and it was assumed that you MUST have the latest firmware in order to flash and run them.
This leaves few options for those having lower hboots: either upgrade to latest firmware OR not flashing the ROMs at all.
What if, someone has a lower hboot/firmware and IS able to run those ROMs without issues? The previous assumption that having lower hboot will make the ROM not working/booting is wrong...at least for me and I don't think I'm unique. I'm sure that there are more users having lower hboots that could run the latest ROMs without having to upgrade their firmwares. I'm on 1.06.0000 hboot S-On and I'm happy with it. I didn't had any single ROM flashed on my device that didn't run. I don't like the idea of being forced to upgrade (going through a procedure that for some proved to be difficult or bricked their phones) without needing to
Well there is still hope....
DISCLAIMER
PLEASE BE AWARE THAT I DO NOT RECOMMEND TO TRY THIS IF YOU DON'T KNOW WHAT YOU'RE DOING. EVEN IF FOR SOME USERS THE 3.4 KERNEL BASED ROMS WILL WORK ON LOWER HBOOT/FIRMWARE, CM DIDN'T PUT THAT CHECK THERE FOR NOTHING. I SHOULD NOT BE HELD RESPONSIBLE IF YOU FLASH SUCH ROM AND IT WON'T WORK. ALSO DO NOT REPORT ANY BUGS IN CASE YOU FLASH A ROM THIS WAY
Now, what people maybe thought already (but some don't know how to do it) is that you need to get rid of that script check in order to flash such ROM. Following the steps below anyone can get rid of the check and enjoy the newest ROMs without upgrading their firmware, presuming such a ROM will run on their firmware/device
Prerequisites:
In order to do this properly anyone will need two tools
- PPCGeeks Android Signer application (or similar) - DOWNLOAD
- Notepad ++ (or similar) - DOWNLOAD
Download and install both from links above then you're ready to go...
Steps to change the script & flash ROM:
1. Download the ROM of your choice and save it on your PC
2. Create a folder with a distinctive name (say CM 10.2) and extract the ROMs ZIP there
3. Look for the file "updater-script" located in \META-INF\com\google\android folder where you have previously extracted the ROM
4. Open the file using Notepad++
5. You will usually find the check for firmware at the beginning of the file and it'll look like something like below:
assert(getprop("ro.bootloader") == "2.15.4444" ||
getprop("ro.bootloader") == "2.15.0000" ||
getprop("ro.bootloader") == "2.13.0000");
That means that, only the users having hboot 2.15.4444, 2.15.0000 and 2.13.0000 will be able to flash that ROM, anyone else will be receiving an error and ROM won't flash
6. Delete those lines with Notepad++ then save the file
7. ZIP the whole ROM again and give the ZIP a name
8. Sign the ZIP with Android Signer then copy the signed ZIP on your phone's sdcard
9. Flash the ROM
This should do it and you'll be able to flash such ROM.
There is an alternative method of extracting the file from the ZIP, deleting the lines then putting it back in the ZIP...this will skip the unzipping and signing steps but depending on how you'll do it it could also give you script errors when flashing (Status 7 or Status 6 errors). Steps to be followed for this "quick" method are:
1. Extract the updater-script from the ZIP and save it on your PC
2. Edit it with Notepad++ like I've described above
3. Open the ZIP with WinRAR and navigate to the place where updater-script is (\META-INF\com\google\android) and delete it from the ZIP
4. Using drag&drop, take the modified updater-script and drop it onto the opened WinRAR window in the location where it should be. There will be a popup windows to confirm adding the file to the ZIP, just press OK.
5. Close the ZIP and flash it
Well many of you might already know and do this one way or another but there might also be some users that don't know how to do it and either ask for help in various ROM Development threads or just quit flashing the ROM
So this is for all those that would like to try the new 3.4 kernel based ROMs and don't know how to do it. It won't guarantee that such ROM WILL WORK on their devices, it just allows flashing it even if they don't meet the firmware requirements. If after flashing, the ROM won't boot or it'll boot loop, there's almost sure need for a firmware upgrade in order to run it.
Thanks rapier. This helps me tons.
I guess the only annoying part about it is that we have to delete those lines each time there's an update/nightly that comes out. But for the time being this will suffice until I have the luxury to upgrade my firmware.
Sent from my HTC One S using xda app-developers app
I too am on Hboot 1.06 and S-on and have never had problems with other ROMs. Being away from the community for several months i'm a bit bewildered by all the risky processes I have to carry out to get my phone to accept the new 3.4 kernel.
So I will give your method a try right away!
Many thanks
RichardW1992 said:
I too am on Hboot 1.06 ...
So I will give your method a try right away!
Click to expand...
Click to collapse
Have you had any success? I am very curious.
Thanks
Patrick
This looks interesting and looks much less complicated than the whole upgrade process.
I'm on HBOOT 1.13 and S-ON; I tried to flash CM 10.2 just for fun but I got the error message (script related).
I read that those who had no problem running the latest Trickdroid and Viper can use this ROM without upgrading their firmware. TD and Viper are the 2 latest ROMS I've been using.
I'm gonna try this this weekend or next week lol - although I prefer the features of Sense ROMS.
androidsigner doesnt work
after dragging the modified zip, it get "Unable to locate file"
---------- Post added at 09:54 PM ---------- Previous post was at 09:11 PM ----------
Ok so on a forum I've found that workaround - no extraction-rezipping-signing.
This is known about theme'd files, you cannot sign them even with command line. They must be opened with 7zip as not to break the signature and edited that way, then close and flash.
Click to expand...
Click to collapse
I did that, so I guess I dont need to re-sign the file
I'll flash another day, Im really tired
By the way, question : I deleted the 2.15 verification lines in the script updater, which moved the next line "mount .... etc" up to Line 2 (Notepad++)
Should leave it as it is, or move it to Line 1?
Thanks
salutcemoi said:
androidsigner doesnt work
after dragging the modified zip, it get "Unable to locate file"
...
Click to expand...
Click to collapse
This error is because AndroidSigner uses the Java JRE and it cannot find in on the path variable. Install latest Java JRE from official site and it'll work.
salutcemoi said:
...
Ok so on a forum I've found that workaround - no extraction-rezipping-signing.
I did that, so I guess I dont need to re-sign the file
...
Click to expand...
Click to collapse
You can extract the file, modify it with Notepad++ (or equivalent) and add it back to the zip using an archiving program (I use WinRar). No need for signing in this case
salutcemoi said:
...By the way, question : I deleted the 2.15 verification lines in the script updater, which moved the next line "mount .... etc" up to Line 2 (Notepad++)
Should leave it as it is, or move it to Line 1?
...
Click to expand...
Click to collapse
After deleting the check lines, the next line in the script should be on line 1 (no blank line at the beginning of the script)
Rapier said:
This error is because AndroidSigner uses the Java JRE and it cannot find in on the path variable. Install latest Java JRE from official site and it'll work.
You can extract the file, modify it with Notepad++ (or equivalent) and add it back to the zip using an archiving program (I use WinRar). No need for signing in this case
After deleting the check lines, the next line in the script should be on line 1 (no blank line at the beginning of the script)
Click to expand...
Click to collapse
thank you !
Much appreciated :good:
I did all the zipping/unzipping through my phone with the help of es file explorer. I got cm 10.2 sept 05 nightly to work but the only thing that's being funky is my wifi. I can turn on the Wifi and it scans all the available network just fine but after placing the password to my designated internet, it doesn't connect.
I'm not sure if it's this method of flashing roms or the way I performed my zip that's causing the issue.
Sent from my HTC One S using xda app-developers app
cougzzz said:
I did all the zipping/unzipping through my phone with the help of es file explorer. I got cm 10.2 sept 05 nightly to work but the only thing that's being funky is my wifi. I can turn on the Wifi and it scans all the available network just fine but after placing the password to my designated internet, it doesn't connect.
I'm not sure if it's this method of flashing roms or the way I performed my zip that's causing the issue.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Shouldn't be affected by the script change. This change only allows you to flash the ROM, nothing else. You can try a WiFi fix or reflash kernel for this kind of issue. I had CM10.2 running well on my phone and didn't have any problems with WiFi. Same for Odyssey ROM which is also Android 4.3 with same kernel as I know
hi
i've tried this metod to install cm10.2 over cm 10.1 on hboot 1.13 htc one s.
After flash rom+gapps and flash boot.img via fastboot i'm on htc logo bootloop
any suggestion?
Tnx in advice
I also had exactly the same issue with CM...could not fix it even after flashing kernels....gave up and went to AOKP ..now Wi-Fi works, still no 4g..but that wasn't working with CM either
Sent from my HTC One S using xda app-developers app
okaiuz said:
hi
i've tried this metod to install cm10.2 over cm 10.1 on hboot 1.13 htc one s.
After flash rom+gapps and flash boot.img via fastboot i'm on htc logo bootloop
any suggestion?
Tnx in advice
Click to expand...
Click to collapse
Same here
I'm also hboot 1.13
Sent from my HTC One S using xda app-developers app
I've read it in the forum for either AOKP or CM that lower HBOOT like 1.13 is going to cause bootloops....I was hoping that using this method, in the OP thread, I'd be able to upgrade to newer ROM...but I wasn't able to (bootloops)
Sent from my HTC One S using xda app-developers app
Bootloops mean you need to upgrade your firmware. This method is only for the rare few with lower hboots and newer firmware.
el_smurfo said:
Bootloops mean you need to upgrade your firmware. This method is only for the rare few with lower hboots and newer firmware.
Click to expand...
Click to collapse
Yup
I rooted my phone and flashed custom roms before the official JB firmware update.
Sent from my HTC One S using xda app-developers app

Outdated MOFO IMG Computerfreek274_1.6 ,Pon-3V4A,PowerSave_11/7/15

With Sunshine unlocking droid Turbo Bootloader I will be moving on to making ROM's not just an img. please see my Forum on XDA here and my Website Computerfreek.com Here for more info.
I will continue to do MOFO support for the next month or so as users make the switch.
Computerfreek274_Turbo_lollipop (SU4TL-44)​
Also On my website Computerfreek.com Now has updated help and support how to setup stuff like adaway,Boot anamation, Dpi and more. Also I will be posting Pre-Released images there days be for there on XDA. There will also be images some custom images that will not ever be listed on here on XDA for I will not support them. So please check out the site it is still a work in progress but it is getting there. As of right now I did not get custom IMG listed and the newest ver is still 1.6 and it is listed below.
This Firmware upgrade to 5.1 SU4TL-44 from 4.4.4! VIA Mofo.
If you took the OTA 5.1 update you out of luck as you where told not to on here over and over. Go check out sunshine root maybe coming soon for locked 5.1 users.
If this software somehow kills your phone I am not to be held liable.
PLEASE BACKUP YOUR DATA 1st For the best speed and no bugs if you are coming from 4.4.4 for the 1st time I recommend that you backup your photos,music and other data. and when you get to step 3 wipe Data and cache. It is not a must but for me to give you support this is a must.​
Thanks to @firstEncounter for his great post and images. Thank you @mattlgroff for his help and everyone who sent me links to the OTA and Full ver.
Thanks to http://motofirmware.center/files/ for hosting stock lollipop IMG's so I an update missing or outdated system files I had.
Big Thanks for PON-3 Audio mod from @mrchezco1995 and his forum is here
Please support better battery stats and give a big thanks over on there forum here. The better battery stats companion app installed in 1.4 will only work with paid ver of bbs from google play.
Thank you guys so much.
Features:
Stable! - I don't publish images without exhaustively testing them. If you have any issues to report, reply to this post and either myself or the community will rally to help fix the issue.
Much better battery life! - This image focuses on battery savings without compromising performance. Your phone will last much longer while running this system image.
Multiple versions - Custom version from DPI dpi higher resolution to Custom fonts
Fast! - This image is lean, fast, and enhanced for performance.
No bloat! - All bloat that is available on the Play Store has been removed. Extra files (like help videos and help audio files) have also been removed.
Optional adblocking! - Adblocking via AdAway that can be toggled on and off.
Now with Pon-3 Audio/ V4A - Increase the volume and the quality of audio output from the Droid Turbo by enabling VIPER4Android which comes bundled in this system image.
Enabled for XPOSED Updated to newest ver. - This system image has been enabled for the XPOSED framework as well as includes BusyBox.
For better support I have removed old versions on here my focus is to have better support for all of you starting from 1.5+
Please Read! If your not on Kernel Version 3.10.40-perf-g90ddf4a Sept 1st 2015 Please Download and flash all .IMG files in this zip here. To find the kernel build go to settings > About phone. Most of you guys will need to update!
Computerfreek274_TurboPop_1.6 Update. 11/07/2015
Now With Turbo 2 Command Center. Screenshot
Download 1.6 Here
Change Log.
Updated .img files in 1..6 No need to download Img pack when upgrading from KK or to update your kernel,modem,etc... all files are updated 1.6 Zip.
Cleaned up some more junk from system
Updated some apps.
Removed music2 aka google music.
Samsung Sans Font IMg's has the IOS9 emojis.
Turbo 2 Command Center​
Download 1.5B Here Updated 10/16/2015 Base on SU4TL-44
Download 1.5 Here 10/5/2015
Custom fonts in 1.4 I will update 1.5 as needed.​1.4 Download Here.
All Files and IMG's files that are needed to install my IMG are Zipped with all my system images from ver 1.3 and up Just download 1.4 or 1.3 and unzip open the help file and do a step by step install.
Please Read 09/12/2015 For Android Pay support and Setup please see Post #3 ​
You can still download 1.3 and 1.3A here.
[/URL].
1.5B Change Log 10/16/2015.
Updated to SU4TL-44
Updated Xposed
Boosted overall audio and mixer profile updated
Fix Pon-3 audio buffer for large audio high bit rate files buffer from 32m to 48m
Few other tweaks also see 1.5 for more info. This has all the tweaks from 1.5 and 1.5 is the best battery and fast running ver to date.
​
1.5 Change Log 10/5/2015
Removed more junk like maps and stuff as you have updated ones from market.
Added for more Tweaks for faster GPU and CPU and more memory.
In call VOL boosted default was max 3 now max 10.
Better GPS.
Battery Seems much better with memory fixes.​
1.4 Change Log 6/12/2015
Android Pay Support Please see post #3 For more info.
Custom Fonts There will be 1.4 img with custom fonts. More to come check one of the last post for more info.
Some Of the changes listed here is from 1.3A
PowerSave Is in all from 1.3A and up.
Removed some more bloat.
SuperSU is the stable ver.
Xposed to newest ver Please uninstall your old xposed.apk be for you flash.
HDR Camera setting is fixed as of 1.3A
Updated some system files.
Tweaked GPS a bit for faster lock.
PON-3 updated
Fixed audio profiles for PON-3 to match are turbo for a more stable PON-3 audio.
Updated Mixer Profiles for better audio.
mixer_paths updated louder audio as we had in my ver of KK. 09/02/2015 I had to make a new one for Lollipop as the old mods did not work.
updated to work better with the turbo Pon-3.
There is now a set of 1.4 Pure/MAX IMG's also for none Verizon users only.
​
More help and support can be found on my website at Computerfreek.com for full install and updates Or read below.
How to install
See Post number 2. http://forum.xda-developers.com/showpost.php?p=61636340&postcount=2.
To setup DPI,Adaway and more.
To install system img via mofo see post 2.
Setup Adaway Install AdAway from Play Store. Run AdAway (don't download hosts files yet) and go to settings - preferences. Check 'allow redirections' and under 'target hosts file' select '/data/host Then go back and hit update host files.
Xposed In Pre-installed and setup just install the mods you like to use.
On Pon-3 V4A Open Pon 3 and check the sound devices you like to enable.
Setting up an custom boot animation place bootanimation.zip under /data/local/moodle/bootanimation.zip for more info or watch this small video on how to. https://www.dropbox.com/s/lom6zduant...rding.mp4?dl=0
For 493 Builds to fix the ambient display being off set you must install xposed MOD app settings found here or download it from inside of xposed. and set moto diplay to 640 DPI. If you need more help check the forums here.​
Flashing from KitKat to Lollipop
This is a nice well written guide by @Purpeltendire Thank you @Purpeltendire Thank you for this great guide.
If you are new or upgrading and need more help I updated help and info on my website also at computerfreek.com
Steps to flash from KitKat to Lollipop - This assumes that you're currently using a rooted KitKat image already, and have used mofo to get root.
BACK UP ANY DATA YOU DO NOT WISH TO LOSE.
YOU ARE ULTIMATELY RESPONSIBLE FOR ANY LOST FILES OR DEVICE PROBLEMS.
Make sure you have a good hour or two set aside, at the minimum. It’s probably not a great idea to try this right before work or class.
Install mofo, ADB, and fastboot on your computer if you haven't already. On Windows, I like using this for ADB/fastboot.
Download the image of your choice.
Download 5.1_images.zip. Extract the files, and put them into the same directory as fastboot. Next, boot into your phone's bootloader (turn the phone on by holding power and volume down), and flash each file seperately using fastboot:[/FONT]
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot erase ddr
Now open mofo_gui.bat, and flash the system image you downloaded:
Code:
mofo flash Your_imagename_here.img
Once that finishes, you want to try to boot the phone. Select Boot to System from the bootloader and then go grab a snack - chances are, it will sit at the Motorola boot screen for some time. After about five minutes, press and hold power to turn the phone off.
Next, boot into the bootloader again and select Recovery. You will likely get a "Dead Android" screen with "No Command." To bypass this, hold power and tap volume up (if that method does not work after a few tries, hold volume up and press power).
Now that you're in recovery, you're wiping both data (factory reset) and cache. Wipe cache first - this may take a very long time (20-30 minutes), especially if you've never done it before. Wipe data/factory reset second. If you're feeling paranoid, wipe everything again.
From recovery, boot to the bootloader. From bootloader, boot to system. This first boot might take some time as well.
Assuming all went well, you should see a Lollipop setup screen within 10-15 minutes. Congratulations!
Remember that your device is now in “like new and improved” mode. You’ll need to restore your apps and settings from wherever you backed them up to, and you'll still need to get the APKs for Xposed and AdAway. Again, nobody else is responsible for any of your lost data.
[FONT=Arial[/FONT]
For more help see Computerfreek.com
Android Pay Setup and Support. 9/28/2015
Update The updated android pay from google market is no longer working with root so if you flash back to an rooted img after setting up this one android pay will stop working.
9/30/2015
For Working android play and info please go to this forum I have made an IMG with tweaks and more here with working android pay.
Tomsgt said:
just talked with the dev behind moforoot and he said that mofo was patched in android 5.1 but he may look into other ways to get around it.
Click to expand...
Click to collapse
This was stated in another thread. I don't know if you heard, but I'm holding on that there's still hope. Is there still a possibility to be able to make a rooted image? I'm really hoping that we'll be able to have root with lollipop, but at the same time, I don't want you to put in all this time and effort for nothing.
Sent from my XT1254 using XDA Free mobile app
There's a lot of places with the ota, try one of them
Jaocagomez said:
There's a lot of places with the ota, try one of them
Click to expand...
Click to collapse
he needs the firmware img's
Michaelmansour1997 said:
he needs the firmware img's
Click to expand...
Click to collapse
Those will be released in the following days
Jaocagomez said:
Those will be released in the following days
Click to expand...
Click to collapse
noooo i need them today to fix my paperweight
Ahhhhh! I can barely wait!
Downloading the update NOW.. How do I get a dump and copy of the firmware OFF the turbo? Where is it located.. Using ES File Explorer to access /
MoPhoMike said:
Downloading the update NOW.. How do I get a dump and copy of the firmware OFF the turbo? Where is it located.. Using ES File Explorer to access /
Click to expand...
Click to collapse
I am far from the skill level of any rom creator but every google guide I've found seems to indicate root (even temporary root) is required to do a system dump. Is temporary root possible on the lolipop update? If theres another way, please post a guide @computerfreek274 so one of the people who has updated is able to easily help us out and get the ball rolling.
Correct me if I'm wrong, but can't you simply extract the system.img from the OTA zip using this method? http://forum.xda-developers.com/showthread.php?t=2497883
TheSt33v said:
Correct me if I'm wrong, but can't you simply extract the system.img from the OTA zip using this method? http://forum.xda-developers.com/showthread.php?t=2497883
Click to expand...
Click to collapse
Yes but I like to get ahold of a system dump. I been working on the ota today.
Pretty stoked!
Sent from my XT1254 using Tapatalk
siegesoldier said:
I am far from the skill level of any rom creator but every google guide I've found seems to indicate root (even temporary root) is required to do a system dump. Is temporary root possible on the lolipop update? If theres another way, please post a guide @computerfreek274 so one of the people who has updated is able to easily help us out and get the ball rolling.
Click to expand...
Click to collapse
If you Google it there was a way to do it without root. I do not care if it is a system.img dump like that. If you can just copy the system folder to your sd card i do not think you will need root for that use es file man and send it my way that will be great.
Want to make sure so if you have root via MOFRO then you should wait and not install the OTA and wait for new System Image from the Freek!!!
computerfreek274 said:
Yes but I like to get ahold of a system dump. I been working on the ota today.
Click to expand...
Click to collapse
Gotcha. Well unless someone has had luck with Kingroot (early reports said that it didn't work), I don't think that will be possible.
EDIT: Nevermind. It's totally possible. I'll try to track down someone who can get it to you.
computerfreek274 said:
If you Google it there was a way to do it without root. I do not care if it is a system.img dump like that. If you can just copy the system folder to your sd card i do not think you will need root for that use es file man and send it my way that will be great.
Click to expand...
Click to collapse
Pulling /system with adb should be easy and noob-proof.
Sent from my LG-E400 using XDA Free mobile app
TheSt33v said:
Correct me if I'm wrong, but can't you simply extract the system.img from the OTA zip using this method? http://forum.xda-developers.com/showthread.php?t=2497883
Click to expand...
Click to collapse
there are no system img's in the ota, its a flashable zip not an xml
Is this what we're looking for?
http://forum.xda-developers.com/droid-turbo/general/lollipop-5-1-coming-23-11-38-t3146663/page4
I have the restore firmware ... where should I host it?
VRZ_XT1254_SU2-12_12_1FF.xml.zip
Click to expand...
Click to collapse
http://forum.xda-developers.com/droid-turbo/general/droid-turbo-lolipop-firmware-t3147979

Categories

Resources