CWMR & Unified msm8960 Philz 6.2.+.+ in the 926 dev section - Droid RAZR M General

V 62++ http://forum.xda-developers.com/showthread.php?p=51349055#post51349055
The new version is very strict on errors, errors that were ignored on 6079 now cause a status 7 stop.
So I go back to 6079 at times.
Xt925 & 926 philz update is only img. Use Recovery Tools, on Play, to flash from phone up.
For those still wanting twrp here News:
http://forum.xda-developers.com/showpost.php?p=49493136&postcount=2
I have issues (not so major) w/ the latest philz
http://forum.xda-developers.com/showpost.php?p=49583155&postcount=2324
All the following issues, I think are due the the 791.. version of twrp & not plilz. I would flash it at various times to restore a rom I only had in twrp.
I think it is more stable now. I did go back & forth to v6, v5 & even twrp 263 and I will just stay on the 2nd v6 only now.
Xt926 & 925 philz flashable is up in attachments
I had another crash: this time the sd unmounted coincident with the screen out!
I do think there should be no screen out anyway. Who really wants to stay long in recovery!
I disable them both in the ini but this points out another issue: Why is not the sdcard1/clockworkmod the home base for Philz??
But our phone is a weird emulated data/media. But so are its 3 siblings.
I made a BU to data/media with v6.07.9 & it failed to restore @ the end of the data run, to almost the very last file. A format of data & data/media allowed the restore to succeed in the same rec session.
Now I am sure to set the following,
using 4.1.2 roms:
Be sure both the backup & restore>Misc Nand. settings>process SE context is unchecked
& adv>storage set to data/media.
I do not use the the following but I think 4.2 would have:
process SE context unchecked
& adv>storage set to data/media/0.
4.3: checked
& .../0.
4.4 same?
New Philz home http://goo.im/devs/philz_touch/CWM_Advanced_Edition
A new version, using Mediafire now, of Philz is up.
I know mediafire does not work for some. Let me know & I can up a copy.
http://www.mediafire.com/download/yc2qcjy7ge2txca/philz_touch_6.07.9-xt907.zip
No assert ck version, if you get a status 7 error, to do I think w/ an out dated binary but the Philz train is moving too fast for anyone to care.
http://forum.xda-developers.com/showthread.php?t=2567603
******************************
I up'ed a no check xt907 v6 too. After all my bad experience flashing a rom could have been something unique to me.
I have gone back to v5 of Philz recovery.
Warning I was installing a rom that bombed on boot & the noticeably slow sdcard1 access turned into no access when I keyed my way back to recovery!!! I had to resurrect parallels desktop & use my restore modded xml. Back on the prev. version (is solid).
http://forum.xda-developers.com/showthread.php?t=2461651
Philz is the bomb. Usb mount works. Aroma access to sdcard1(realSD) is only through /storage folder!
I attached my settings (simple mode-double tap only,no data/media/0, hide progress-fast mode) as it is daunting to setup-must go in :
data/media/philz... philz-touch_6.ini.bak for v6.
And............................................/philz-touch.ini.bak for v5.
***********NOTE this file is not a zip: change the .zip to .bak.**********
More about how to load Aroma to your cwm folder & a no assert check v5 Philz. http://forum.xda-developers.com/showpost.php?p=42689559&postcount=3
Scroll down to see an easy to read & concise summary
https://github.com/PhilZ-cwm6/philz_touch_cwm6
Do not use cwr 6.0.4.4 or any other recovery that forces data/media/0 with stock 4.1.2 roms. Philz is the exception allowing you to choose.

New PhilZ is up.

Skip

New Philz is up
see op

New Philz finally!
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/xt907/philz_touch_6.19.3-xt907.zip
Be aware keep 6079 handy for only flashing dirty permissions stuff.

Please delete.

Here is the latest 6221, screen input works now, on the 907.
http://forum.xda-developers.com/showthread.php?t=2686374

Please get to testing the newest unified build. Between hachamacha & Phil... We could get one build for all msm8960 phones.
http://forum.xda-developers.com/showthread.php?t=2686374

I guess I am dreaming if I think I can unlock my x....

Related

[ROM] seeARMS' XXJPY v0.2 (12/23/10) [STEAM RECOVERY]

PLEASE NOTE: If you are using a Canadian handset, I recommend switching over to my JL2 based ROM. It's the same speed (if not quicker), and I will be providing much more updates for it. The ROM can be found here: http://forum.xda-developers.com/showthread.php?t=906977
News
12/23/10 - v0.2 released! Includes an error-checking script to prevent possible errors from occuring, new Steam recovery, wipe and non-wipe versions and more! Check the changelog for more info.
12/22/10 - v0.1, initial beta release
Hey everyone,
This is a rom which aims to provide the absolute best user experience by being extremely quick without sacrificing any necessary features. The majority of Samsung bloatware is removed, however a good portion of the pre-installed apps are left untouched. This ROM is based on XXJPY (Froyo 2.2.1).
If you have any questions prior, while, or after installing this ROM, please read the first few posts, as I'll try to address every possible (major) problem which can occur. If, after reading the posts, you are still encountering a problem, please reply to this thread being as detailed as possible. This allows me to fix problems quickly and easily.
Now, this is my first ROM, so there are bound to be a handful of bugs. However, I've been using this ROM for a few days and have yet to encounter any major problems.
Note: Please don't complain about Quadrant, Linpack, or any other pointless benchmark scores. If you've used the ROM and it's sluggish, by all means tell me, but don't base your opinion of the speed merely on a benchmark.
Okay, so what now?
1. Download and Install Instructions
2. Changelog, To-Do
3. FAQ and Problems
4. Screenshots, Media, User Comments
Features
Based on XXJPY (Froyo 2.2.1)
Patched Speedmod kernel, version K12 hz=256(allows you to mount on computer without problems)
Steam multi-touch recovery: update.zip on SD card
Added an error-checking script which prevents errors when installing [thanks Darkyy!]
All-black Gingerbread theme (saves battery)
Fully deodexed
Fully zipaligned
Fully updated Google Apps (YouTube, Flash, Market, Gmail, Maps)
Latest Su and Busybox
All protected apps in market - modified build.prop
Big APN list, which allows instant internet + MMS access
Integrated ClockworkMod Recovery
Stock AOSP Lockscreen
Bell UGJK3 Modem
Backlight Notifications
Added Applications:
Nexus S Live Wallpapers
Swype v 2.15 (Newest)
Launcher Pro
Optional: Gingerbread Keyboard (install from SD Card)
Removed Applications:
AllShare
Diary
Aldiko Reader
Press Reader
Layar
Thinkdroid
Write and Go
Credits (in no particular order)
-Hardcore for the kernel
-santiemanuel for the Nexus S Live Wallpapers
-vukandric for the theme
-Darkyy for help on the update script, and for generally being awesome
Download and Install Instructions
Downloads
Latest and Greatest
-v0.2: seeARMS XXJPY (12/23/10)
Wipe: http://www.multiupload.com/L9SUOBKO88
No Wipe: http://www.multiupload.com/9F5E89AYTP
-v0.1: seeARMS XXJPY (12/22/10)
http://multiupload.com/G6XTJF07MO
Modems
To flash these modems, use Odin and select the "modem.bin" file in the PHONE box. Go to Settings -> About on your phone after flashing and look at Baseband to ensure it flashed correctly.
JL2: http://www.multiupload.com/TC1ME8VB20
JK4: http://www.multiupload.com/3HOKWMBHO2
Installation Instructions
Before installing, disable any lagfixes (which can typically be done by booting into recovery mode and selecting "Disable Lagfix").
Also, if you wish, backup everything! Perform a NANDROID backup in recovery, backup your music, files, etc. In case something goes wrong (it will eventually), you'll have peace of mind.
Please note: this rom will wipe all your data. It will not, however, format your internal or external SD cards. This means you'll lose apps and settings, but not music, movies, etc.
Lastly, I recommend performing a factory reset before installing any new rom.
If you're running a previous version of my ROM, feel free to install the non-wiping version. However, if you're switching roms, I recommend running the standard version, which will erase all data.
1. Download and copy this file to your internal memory card.
2. Boot into recovery, and select "Install zip from sdcard".
3. Select "Choose zip from sdcard", and scroll to the ROM.
4. Select OK, and wait for the file to flash.
5. Reboot. This reboot will take a while (upwards of 2-5 minutes), so be patient and don't shut off your phone!
Congratulations, you've successfully flashed!
After it boots, I'd recommend doing a few things in order to allow your phone to be as quick as possible:
1. Boot back into recovery, select "Advanced SpeedMod ULK Features". Choose "LAGFIX options", then "Faster: EXT4 ALL". This applies a lagfix, and converts the partitions into the faster EXT4 filesystem.
2. In recovery, go back to the Advanced SpeedMod ULK Features menu. Choose "TWEAK options", and enable every tweak. For more information about these tweaks, see HERE.
Also, window animations are disabled by default. You can enable them by going into settings -> Display, and selecting Animations.
3. If you'd like the Gingerbread Keyboard, open up the My Files application and navigate to the directory "Gingerbread_Keyboard". Open up the .APK file and install as usual.
Changelog And To-Do
Changelog
v0.2
-Google Voice Search updated
-Added option to install gingerbread keyboard
-Updated kernel version to K12
-Added error checking script - with help from Darkyys rom (This prevents possible errors when installing)
-added nowipe and wipe versions
-Modified build.prop to allow all protected market apps
-Added Steam recovery - check FAQ for info on how to access it
v0.1 - Initial beta release
To-Do
-Gingerbread Keyboard
-Extended Power menu
-Support for different themes
-Stock application pack (available for flashing through CWM)
-Better modem (JL2? JK4?)
-Faster browser
-Modded SMS Application
-Modded Camera Application
If there's anything else you'd like to see in this ROM, just ask.
FAQ And Problems
FAQ
I'm on stock Froyo and I have 3e recovery!
Click to expand...
Click to collapse
No worries. Follow these steps:
1. Download Odin from here.
2. Download the Speedmod kernel for whichever Android version you're running. Make sure to download the Odin kernel, not the CWM one!
3. After downloading, extract the .TAR file from the file you just downloaded.
4. Open Odin, and turn off your phone. Connect your phone to your PC via USB, and enter download mode by holding volume down + home + power.
5. Odin should detect your phone. Load up the .TAR file in the "PDA" box in Odin. Make sure the other boxes are left blank. Untick "Repartition". Start flashing.
6. Your phone should automatically reboot with the new kernel! To double check, shut it off and boot into recovery. If you see CWM recovery, you're successful!
7. Now you're required to download the patch for the Speedmod kernel, which will allow you to copy the ROM over to your internal SD card. If you don't install this patch, the internal SD card will be detected as a CD drive, and will be read-only. The patch is able to be downloaded from HERE. Simply copy this patch to your SD card, boot into CWM, and flash it using "install zip from sdcard". After doing this, follow the normal steps to install this rom!
I'm encountering force-close issues, and general app issues right after installation.
Click to expand...
Click to collapse
Simply perform a factory reset. Clear the cache + Dalvik cache in recovery as well, if you'd like.
What's this steam recovery and how do I access it?
Click to expand...
Click to collapse
Steam recovery is a new, semi-functional multi-touch recovery created by sztupy. This recovery has all the features the standard CWM one has and more. Check his thread for more info.
Please note: Because (currently) the only Steam-compatible kernel is based on a much older base version (ie: not XXJPY), a small amount of features are incompatible, such as lagfix options, kernel options, etc. However, the majority of features (such as mounting, wiping, etc) are working just fine. I'm working on getting everything working; as soon as it is, it will fully replace CWM on this ROM.
To enable it, just boot into CWM and go to "Apply sdcard: update.zip". After doing this, it will boot into the new Steam recovery. You must do this every time you want to access it.
My GPS isn't working! It takes forever to lock and displays my position inaccurately!
Click to expand...
Click to collapse
Try clearing the GPS data on your phone. Do the following: (Original poster unknown. Reposted by dpvu.)
1) Enter *#3214789650# into the dialpad.
2) Under "Application Settings" set the Start Mode to Coldstart.
3) At the main menu "Delete GPS Data".
4) At the main menu "Get Position Test".
If you're still not finding many satellites try setting Operation Mode to "MS Based" in the "Application Settings". I did all of this then set the GPS back to hot start.
Screenshots, Media, User Comments
Screenshots
Click for a larger image.
User Comments
°Dexter° said:
Impressive rom seeArms, really really fast...faster than others, indeed.
...
Very good work,no major issues by now,i'm eagerly waiting for next release
Click to expand...
Click to collapse
Existence. said:
it's runnin great, thanks seeARMS. can't wait for the JL2 version. i really dont wnt to brick my phone and i think the JL2 version fixes the SD dying problem so i cant wait!
Click to expand...
Click to collapse
hi. looks good. i will test it now and give feedback after.
thanks for your work and keep going.
btw: why are using this modem?
gonna try this ROM out!
Quadrant score? I will try it, looks good.
gonna try this release soon, good job
fenerbuuh said:
hi. looks good. i will test it now and give feedback after.
thanks for your work and keep going.
btw: why are using this modem?
Click to expand...
Click to collapse
I'm using this modem because I need the Canadian band, because, well, I'm located in Canada. And, according to this guide, this modem is very good on battery life and reception.
In later versions of this ROM I'll most likely include a different modem (or a flashable modem). Something like that.
Any modem you'd prefer to see included?
Place this zip into PDA on Odin and upload it.
Any chance to work this?
I would like to try this rom,but I've 3e and I can't do it the way been described...
Hey man, to bad i flashed Docs jpy rom just yesterday evening, and dont want to change rom on a daily base. But ill test it for sure just because id not have to change kernel afterwards...
so thanx for your work and keep it coming man...
Mparmpa-Nikos said:
Place this zip into PDA on Odin and upload it.
Any chance to work this?
I would like to try this rom,but I've 3e and I can't do it the way been described...
Click to expand...
Click to collapse
Flash the SpeedMod kernel (or any kernel which supports froyo and has integrated Clockworkmod Recovery).
I'll add a guide to do this in the FAQ.
seeARMS said:
Flash the SpeedMod kernel (or any kernel which supports froyo and has integrated Clockworkmod Recovery).
I'll add a guide to do this in the FAQ.
Click to expand...
Click to collapse
I'm looking forward to this,man!Thank's
Mparmpa-Nikos said:
Place this zip into PDA on Odin and upload it.
Any chance to work this?
I would like to try this rom,but I've 3e and I can't do it the way been described...
Click to expand...
Click to collapse
No way man, but you could get hardcores kernel as an odin package, it comes with cwm recovery, flash that first and then use cwm to install this rom.
Mparmpa-Nikos said:
I'm looking forward to this,man!Thank's
Click to expand...
Click to collapse
Done. See the FAQ.
Welcome new devinteresting rom,gonna try it...
Thank you
Welcome seeARM!
Nice to see another dev helping the SGS Community.
Feel free to PM me if you have a question or anything else
- darkyy.
Sounds good
Will likely give this a try as the XXJPX modem causes me to lose my 850 WCDMA connection all too frequently (even though I've enabled it). Just curious if there are any problems with Market, or will it come updated to 2.2.7 already?
Cheers mate!
Darkyy said:
Welcome seeARM!
Nice to see another dev helping the SGS Community.
Feel free to PM me if you have a question or anything else
- darkyy.
Click to expand...
Click to collapse
Will do Darky, thanks.
canad1an said:
Will likely give this a try as the XXJPX modem causes me to lose my 850 WCDMA connection all too frequently (even though I've enabled it). Just curious if there are any problems with Market, or will it come updated to 2.2.7 already?
Cheers mate!
Click to expand...
Click to collapse
Market comes updated to version 2.2.7 already. I haven't had any problems with it at all.

[NIGHTLY][ROM][2.3.7][GWK74] CyanogenMod 7 for Samsung Galaxy S

This thread is reserved for nightly builds of CyanogenMod Rom for Samsung Galaxy S.
All Samsung Roms are running ontop of BML/RFS, CyanogenMod 7 does NOT.
It runs on MTD/yaffs2 (like Nexus One) which means you're not able to flash any kernel or run any filesystem you want. Use it as it is.
Only data partition, which is on movinand, is ext4 like on speedmod or voodoo ("lagfix").
CyanogenMod is a free, community built distribution of Android 2.3 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
What are Nightly builds? Auto compiled builds of the latest CyanogenMod source from github. This version change each night and aren't officialy supported.
If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).
INSTRUCTIONS:
- First time flashing CM 7 to your Galaxy S (or coming from another ROM)?
Root your device and install ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Upgrading from earlier CM7?
Do a Nandroid Backup!
Install the ROM (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps, after flashing rom don't forget to flash Google Addon package if you want it.
Latest version: http://download.cyanogenmod.com/?device=galaxysmtd
Compatible Radio Images (>= Nightly 15): http://codeworkx.de/download/cyanogenmod/
Supported devices: GT-I9000, GT-I9000M, GT-I9000T
before flash is recommended to check the md5sum
FREQUENTLY ASKED QUESTIONS:
http://forum.cyanogenmod.com/topic/24169-faq-cm7-on-the-samsung-galaxy-s/
CYANOGENMOD WIKI:
http://wiki.cyanogenmod.com/index.php?title=Samsung_Galaxy_S
HOWTO BUILD FROM SOURCES:
http://wiki.cyanogenmod.com/index.php?title=Compile_CyanogenMod_for_GalaxySMTD
ADDITIONAL INFORMATIONS:
Maintainers:
- atinm - http://twitter.com/atinm
- codeworkx - http://twitter.com/codeworkx
- coolya - http://twitter.com/dumdidum
- guiperpt - http://twitter.com/guiperpt
- unhelpful - http://twitter.com/unhelpfulone
Irc:
- Host: irc.freenode.net:6667
- Channels: #cyanogenmod, #cyanogenmod-dev, #cmsgs
Changelog:
- Generic Changelog
- CyanogenMod Source Twitter
- Device specific Changelog by igor.tonky
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
If You Have Any Questions, Please Refer To This
CM7 QUESTIONS & ANSWERS XDA THREAD
http://forum.xda-developers.com/showthread.php?t=1067074​
Regards,
~drz
have i ever told you i love you? i'm pretty sure i have but i'd just like to tell you again. i'm sorry for this offtopic post but i'll edit it later to something useful. just wanted to show my affection.
This should be it since the beginning.
Clean thread. That's how I like it
Excited for the Coming Soon patch!
Reboot Recovery
Woah! Can't wait to try this.
The quick troubleshooting post.
This post contains a compilation of problems/issues and answers provided in this thread and earlier threads. Not all answers are tested by me and I will in no way guarantee that this wont mess up your phone.
You know, watch your kittens. They might be eaten by following the advice written down here.
DETAILED INSTALLATION INSTRUCTIONS CAN BE FOUND HERE.
rschenck wrote a very nice (and updated) guide for how you install CM7 on your SGS these days.
Things have changed quite a bit recently, so even if you installed it two weeks ago, you may want to check this one again.
What do people mean with "correct" bootloader? How can I make sure I have the right one?
Do NOT install directly on top of existing Samsung 2.3.3 firmwares or other firmwares based on this (like Darky's 10). Similarly, don't install directly on top of Eclair.
See this very easy guide on the android soul for flashing XXJPU, which is Froyo with the correct bootloaders needed..
I'm not sure I understand these procedures. Can you draw it out for me?
Anticipating this very question, rschenck actually did draw out a flow-chart for you.
See here.
But I'm not using the I9000, I'm using something else...
codeworkx provided a reference list you can check to ensure you are getting the right files.
After flashing the initial CM kernel I can't get CWM Recovery to work. It just displays some weird image
CWM Recovery might have different keymappings from the ones you are used to.
- Volume keys: Naviagte up and down in menus
- Power button: Select item
- Home key: Show/hide menus
If you are only seeing a weird image, chances are you've hidden the menu by pressing the home key. Try pressing it again
I can't find Cyanogenmod nightlies in ROM Manager
Yes. CM7 for the SGS is now mainlined and supports ROM Manager for nightlies, should you have the premium version. If you have the Premium version, follow these very graphic instructions to configure ROM Manager for nightlies.
To install from MIUI (courtesy of runedrune)
- Reboot into recovery using 3-button-combo
- Choose "mounts & storage" and format system, data, cache, datadata
- Do not apply the initial-file.
- Apply the latest update
- Apply the latest gapps (which can be obtained here. You want the one with -gb- in the name )
- Done. Reboot
Odin doesn't recognize my phone anymore and I want this fixed in case I mess something up
You will probably need the Nexus S drivers (which supposedly is really just some updated Galaxy S drivers).
If Odin for some reason don't see your device when connected, make sure the old Galaxy S drivers are uninstalled and removed. Bilboa1 gives some good hints about how to make sure your drivers are actually fully removed. Do check this before proceeding to install the Nexus S drivers.
After you have installed the Nexus S drivers, plug in your phone. Windows should now install some drivers, but you are not done yet. When using download-mode your phone will show up a little differently to Windows, so put your phone in download-mode and plug it in, with neither Kies nor Odin running. You will probably see Windows installing some more drivers.
After doing this, Odin should hopefully be able to recognize (and flash) your phone.
IS THIS "FOR EVERYDAY USE" NOW?
It depends. If you have to ask, it probably isn't.
I've flashed this and decided it is not ready for me. How do I flash back to stock ROMs?
Get the appropriate firmware you are interested in, flash as usual using Odin, but check re-partition and use the 512 pit-file.
For pre-rooted stock-images, you can use EZBase as shown here (also includes download links).
OTHER STUFF / KNOWN ISSUES AND SOLUTIONS
Please take a look here to see if your issue is mentioned and has a known solution before posting.
After flashing CM7 I get strange colours on my screen during boot
You do not have the correct bootloaders. Basically flash 2.2.1 following this article and then redo the CM7 installation. All should be fine.
Guys! Guys! I cannot find Android Market!
Google stuff is not included in CM7 by default. Download and apply latest gapps from CWM. You want the "universal" one with "-gb-" in the name.
But I want the latest gtalk with video and all that fancy stuff
got_milk was nice and uploaded some stuff. Beware though that lots of people are reporting this to force-close a lot, and that's not just on SGS CM7.
Can I run Samsung apps like Memo, Camera etc on this firmware?
No. Sorry. All Samsung apps depend on TouchWiz libraries which can only be found in Samsung firmwares.
How do I get additional themes for CM7 themes chooser?
Check the themes forum here on XDA or search for "CM7 themes" on Android market.
Once installed, the themes will be available in the themes chooser yes. According to the devs should reboot to fully apply the theme, but if you want to avoid reboots Android market might have something for you.
Things used to work, I applied a nightly update and now everything force-closes
Try wiping cache and dalvik cache in CWM. You should do this every time you install a new update.
Does CM7 need a lagfix?
CM7 uses ext4 (for /data) and yaffs2 (for everything else). CM7 does not use Samsung's RFS which was the main cause of poor performance on Samsung firmwares.
So no, your system is already lagfixed, you don't need to apply a lagfix and according to the developers very bad things will happen if you try to apply one anyway.
My current ROM has a lagfix. Do I need to disable that?
Probably not.
If you have a 2.3.3 ROM with 2.3.3 bootloaders, you will want to do a full wipe to stock 2.2.1. See above. In this case you no longer have a lagfix anyway and don't have to worry about it.
If you have a non-2.3.3 ROM with a lagfix, you don't have to disable it. All your partitions will get wiped by the installer anyway and so will your lagfix.
For whatever reason, I want to flash a custom kernel
You can use custom-kernels, but CM7 is a work in progress with new kernel-revisions popping out with every release. Make sure you flash a kernel which is compatible with the nightly you are running. Also: Do NOT flash via Odin, flash via CWM.
rschenck has a very good post on this.
If all you want is a "voodoo kernel" for voodoo sound, just (buy and) install Voodoo Control Plus from the market. It will load the required kernel-modules while you can stay on the stock kernel, making the lives of the developers much easier should you encounter bugs.
Is it possible to flash my own CSC from recovery after installing cm7?
According to the devs, this should not be needed.
Flashing other modems/radios
(Courtesy of GrimVarg: http://forum.xda-developers.com/showpost.php?p=13399590&postcount=8117 )
Odin will not work and it might **** **** up. The reason is that Odin and heimdal does not understand the CM partition layout and will just write the modem where it thinks is should be. Overwriting other stuff in the process.. So you need to use the specific update zipfiles on teamhacksungs sourceforge page
Click to expand...
Click to collapse
Instead of using Odin, download radio-packages from the following link, transfer to your phone and flash via CWM:
http://sourceforge.net/projects/teamhacksung/files/galaxys/
I want to keep my 850 band, and I don't recognize any of the modems on the sourceforge page
Lorssoth says "use KC1" and robbiev80 posted some download links you might be interested in.
Does external SD card work with cm7? Thanks!
It does. Make sure you have the proper bootloaders before installing as mentioned in the first part of this post. EZBase can be used for this.
External SD card will get mounted as /mnt/emmc. This may not be visible to all apps. If you desperately need the contents visible to apps only looking in /mnt/sdcard, create an empty directory there and remount the /mnt/emmc there as well:
Using either the terminal emulator or adb shell:
Code:
su
mkdir -p /mnt/sdcard/external_sd
mount /dev/block/vold/179:9 /mnt/sdcard/external_sd
Note: This is only a temporary fix for when needed. It will cause issues when you try to use USB sharing later. Write the following to get things back to normal:
Code:
umount /mnt/sdcard/external_sd
USB sharing doesn't work
Try installing the Nexus S drivers, instead of the Samsung ones.
After installing this camera doesn't work
Try locking and unlocking your phone. No really.
After installing this I cannot get any data-connections apart from wifi
There is a problem with RIL (radio interface layer)-polling. Lock and unlock and you should be OK.
If this sounds cumbersome, mobilescooby claims that installing Juicedefender somehow fixes this for him and that he no longer needs any lock and unluck boot-rituals.
This issue should now be resolved.
After doing this I still cannot get any data-connection apart from wifi
You might need to configure APN settings. Normally your network-provider will have this information on their homepages and some even offer to send them to you over the network.
After installing this I cannot send and/or receive MMSes
See above: You might need to configure APN settings. Check your provider.
After installing CM7 I cannot connect to my wifi-network
It might be related to what channels you have enabled on your phone. If your wifi network is using channel 12 or higher, you may need to enable those channels on your phone.
Go to Settings/Wifi & Network/Wifi settings/Advanced/Regulatory domain. And try not to be in violation of local laws with regard to channel usage
After installing CM7 I cannot connect to 802.1x EAP Wifi networks
This is seemingly an issue with lots of custom kernels and even some of the Samsung Firmwares. Yours truly can't get it to work at all, not on CM7 nor Samsung's JVB firmware.
Other people have reported that forgetting the network and adding it manually, by entering the SSID (with correct casing) and filling in all the details themselves have solved their problems.
YMMV
After installing CM7 I cannot charge my phone to 100%. WTH
No actual firmwares allows you to charge the battery to 100%, but stops a little bit before it reaches that point. This is to protect the battery from overcharging and should (in the long run) give you much better battery-life.
While stock firmwares from Samsung shows that the phone is 100% charged, this simply isn't true and is just UI-candy to make you all feel comfy. It's really charged to something around 94-98 percent.
So if your phone stops charging around that point, everything is normal, and the only new thing is that your phone is no longer lying to you
My GPS performance is terrible
Welcome to the world of Samsung Galaxy S GPS flux. Things you can try to improve on this includes the following:
- Install faster fix from Android market. Ensure you have the best time-server for your area chosen.
- You can also try AngryGPS, which siberian tiger was nice enough to upload.
- If all else fails, you can also try to flash a radio with a good GPS reputation. For flashing radios, see the appropriate section of this post. For some detailed post about the different radios eeyunopper posted this link and this link. (With ZSJPG I am getting decent result, YMMV)
Auto brigthness is kinda not-worky
You can try the presets outlined by Arkymedes right here.
How do I configure proxy settings?
(Thanks to runedrune)
If you are used to looking for proxy settings under Settings/Wifi & Network/Wifi settings/Advanced, you wont find it there.
Using either Launcher pro/ADW Launcher or another launcher which lets you create shortcuts to activities:
* Long hold on some open space on your launcher
* Select (Custom) Shortcut
* Select Pick your activity/Activities
* Scroll down to settings and click this
* Scroll down the long list and you should find proxy settings
You now have a shortcut to configure proxies as usual.
This "headphones mic on mute + instant music after call bug" is really irritating
If you are using Samsung or Nokia headsets, this is due to a problem on their part. See Arkanius' post right here.
Other things I should be aware of?
- Don't use 2G/3G data-switching. Period. At least not while the data-connection is active.
Not trough widgets, tasker or any other means. Seriously. Should you do this, you might end up having to restore nandroid backups or doing factory resets.
This report has details on more sophisticated ways of cleaning up which may lead to less data-loss, although not everyone can get it to work.
*subscribes*
nice work with the GPIOs, camera and other parts !
Lol, having two threads will confuse a lot of people. I look forward to all the questions relating thus...
sent via potential brick...
eeyunopper said:
Lol, having two threads will confuse a lot of people. I look forward to all the questions relating thus...
sent via potential brick...
Click to expand...
Click to collapse
I've already notified the mods to close / lock the other one ...
Good job on the clean house, everything is working great on my phone and very speedy
Mortify1 said:
Good job on the clean house, everything is working great on my phone and very speedy
Click to expand...
Click to collapse
The same for me My phone is working so great and very very speedy
Probably a stupid question but to switch from MIUI to cyano that steps should I follow?
Only this ? :
-Reboot into recovery using 3-button-combo
-Choose "mounts & storage" and format system, data, cache
-Apply zip from sdcard: cm7-DEVICE-initial-XXXXXXXX.zip
-Do a factory reset / data wipe!
-Reboot
-Install the latest update after a reboot!
Tantrico I said:
Probably a stupid question but to switch from MIUI to cyano that steps should I follow?
Only this ? :
-Reboot into recovery using 3-button-combo
-Choose "mounts & storage" and format system, data, cache
-Apply zip from sdcard: cm7-DEVICE-initial-XXXXXXXX.zip
-Do a factory reset / data wipe!
-Reboot
-Install the latest update after a reboot!
Click to expand...
Click to collapse
format /system /data /cache /datadata and then flash the latest update and the latest gapps.
I'm waiting the upcoming improves on camera in great expectation.
Tantrico I said:
Probably a stupid question but to switch from MIUI to cyano that steps should I follow?
Only this ? :
-Reboot into recovery using 3-button-combo
-Choose "mounts & storage" and format system, data, cache
-Apply zip from sdcard: cm7-DEVICE-initial-XXXXXXXX.zip
-Do a factory reset / data wipe!
-Reboot
-Install the latest update after a reboot!
Click to expand...
Click to collapse
no
after format system/data/cache
just apply the last update
runedrune said:
format /system /data /cache /datadata and then flash the latest update and the latest gapps.
Click to expand...
Click to collapse
Only this file ?
update-cm-7-05012011-NIGHTLY-GalaxyS-signed.zip
I do not have first place this
cm7-galaxys-initial-20110410.zip
and after the update ?
Nice things are comming... I hope for battery improvemant and radio FM. Since we got GPS, Compass is not so important but nice additional that save battery/make quicker fix.
Codeworks, do you got any rodemap?
Tantrico I said:
Only this file ?
update-cm-7-05012011-NIGHTLY-GalaxyS-signed.zip
I do not have first place this
cm7-galaxys-initial-20110410.zip
and after the update ?
Click to expand...
Click to collapse
nope. just flash that file. i made the same switch from miui to cm7 two days ago
@codeworkx , if reboot in recovery works = nightlys updates for ROM Manager? !
Enviado desde mi GT-I9000 usando Tapatalk

[Guide] All things Iconia A100 (guide to modding) - updated 8.13.13

Since the information for this device is so fragmented, I decided to attempt to keep it all in one (or a series of) posts. I aim to link to the original posts as well as outline what do to with your device from the time it leaves to box to running the latest and greatest modified rom or CM9 or whatever else is out there. I will not link directly to anything, rather I will link to the thread, and I very seriously recommend reading at least the post, if not the thread, before you begin ANYTHING.
This guide is a work in progress, it is not complete, and I will work on it bit by bit until it's completed!
Section 1: So its shiny and new...how can I MOD IT?
This will be assuming the new shiny toy in question is indeed an Acer Iconia Tab A100, this is not meant to cover any other devices. And, this is assuming it's coming with Honeycomb installed, in stock form. If its used, or comes with ICS, the next section will amuse you.
First thing most users that want to mod their devices do is root their device. Now, rooting is not unlocking, as carrier unlocking is not boot loader unlocking. Rooting a device allows you to access the system in a much more in depth manner, including read/write (R/W) access to the /system partition, among other things. It allows use of programs such as Titanium Backup (TB or TiBu) ROM Toolbox, overclocking or other clock setting utilities such as SetCPU or CPU Master for overclocking (if the kernel supports it) underclocking and undervolting.
So...how do I do that rooting thing? Well assuming you are running Honeycomb and are wanting to update to ICS plus root and unlock the bootloader, we will use the info from this thread Simple Root Method by ZeroNull to update you to ICS and then gain Root access on that new ICS install!
What about rooting Honeycomb? Well most users are already running ICS and prefer it, and those on Honeycomb are likely wanting to update to ICS, so I will leave this out for now. If I have the time I will come back and include the link for that as well.
Now, ICS is installed, and you're rooted, what else can I do? Well you can unlock your bootloader, and load up a custom recovery such as CWM or TWRP and using those, install Custom ROMS! For this, we visit this thread here Install unlocked bootloader by ZeroNull. Follow ALL directions in this thread for a fully unlocked bootloader!
Custom recoveries, what are they and how do I get that shiz? Custom recoveries, CWM and TWRP, allow the user to flash anything they want, provided its for their device and properly packaged. This included custom roms, some tools, and allows you to "wipe" various parts of the device's storage and backup/restore to a previous installation. Powerful, and dangerous, do not go pushing buttons to things you do NOT understand! Also, you MUST delete or rename /system/etc/install-recovery.sh prior to flashing recovery! This will restore stock recovery every time android boots, wiping out your custom recovery. The only time you want that file there is if you are using the crossix mount swap mod, which replaces that file with a modified version that leaves recovery alone.
Safe to do wipe:
Wipe cache, data, dalvik cache, system. Theonew also reports Flex and boot can be wiped as well as SD-EXT. This is not to be confused with External SD, this is a separate partition on your External SD card, wiping it will NOT wipe external SD, only what's installed on that partition, the rest is safe and requires a separate wipe.
If you wipe system you MUST install a new rom or restore from backup!
If you wipe boot please restore or install a new ROM before rebooting! Safety first.
Not safe to wipe:
Don't wipe anything else, and always install a new rom or backup after wiping system!
Never reboot system after wiping without first restoring or installing a new ROM!
Post 2 will cover custom recovery functions in more detail, for both recoveries.
Now that you have an unlocked bootloader, what can I do? Install that custom recovery! There is two flavors, CWM and TWRP, CWM available here CWM Recovery by ptesmoke. Follow the instructions in this post to the letter! Only attempt this after you have ICS, rooted, and unlocked the boot loader correctly! Next we have TWRP Recovery here TWRP Recovery by ZeroNull. Again, follow the instructions to the letter, and attempt only after ICS, root and unlocked boot loader are finished.
Ok, gots me some custom recoveries, what about custom roms? This is why we just did all that work, to prepare for this! Custom ROMs! I'll be listing some (all?) ROMs that you can use, besides stock HC and ICS.
The list in order of version, oldest to newest, updated to retired:
4.0.3
KEBBERSROM by Hardslog Stock based 4.0.3
Flex Reaper by civato ICS 4.0.3 Modified Stock
Green ICS by lgcmn & ZeroNull ICS 4.0.3 Modified Stock
4.0.4
KEBBERSROM SHELLSHOCK by Hardslog 4.0.4, based on A500 and A700 ROMs
Nightly Builds of CM9 by pio_masaki ICS 4.0.4
Aoikaze Modified CM9 by pio_masaki ICS 4.0.4
4.1.1
CM10 Preview builds by waydownsouth 4.1.1
4.1.2
Unofficial CM10 builds by pio_masaki (stock and modded, Phone UI and Tablet UI)
Jellytime Sosei by pio_masaki Jellybean 4.1.2
Cyanosaki_Flex by Hardslog
4.2.2
CarbonROM JB 4.2.2 Unofficial by pio_masaki
These are most of the ROMs. There are others that seem to no longer be in active development and are based on the old leaks that vache was kind enough to grab for us. Development is currently only active in the KEBBERSROM builds by Hardslog, and occasional updated in the CM10 builds by pio_masaki.
That ends Section 1, preparing for awesomeness, and Post 2 will continue with installing your new custom ROM!
Section 2: Recoveries and what they can do for you.
This section will cover recoveries and what they can do, and how to do it. I will be starting with TWRP, as I use that on all of my devices, and after that I will include a CWM section, as a lot, if not most, use that. They are similar in what they do, but different in where things are.
TWRP Recovery
Official TWRP for A100 by linuxsociety
This assumes you have already done everything in section 1, including installed ICS, rooted it, unlocked your bootloader, and installed TWRP custom recovery. Links for this information is provided in Section 1, in the post above.
First thing you should ALWAYS do when you enter recovery, before doing ANYTHING ELSE, is make a nandroid backup!
Getting into recovery: Depending on what ROM you use, this is done a couple ways. First is an AOSP ROM, like CM9/AOKP, which you can hold the power button, then select Reboot, then Recovery. In modified stock or rooted stock ROMs, this menu doesn't exist, you can either use an app like Quick Boot, and select recovery, or power off, then hold the Volume - key (closest to the rotation lock switch) and while holding it, hold power, once the acer screen comes up and starts saying Recovery kernel, release both and recovery will boot provided an update.zip is NOT on the root of your external SD card. This method works for any ROM.
Now I'm in recovery, what do I do? As I mentioned, make a nandroid backup before you do ANYTHING else! From the first screen (home screen) in TWRP select Mount. In mount you can leave everything alone and at the bottom will be two options with Circles. Select Using external SD Card for Backup. This will store your backup on your external SD card, never use internal SD if possible. After you select use external SD, press the Home button in the upper right corner. Now, back on the Home screen, select Backup. Double check the boxes checked are System, Data, Boot and Recovery. At the bottom is a nice little slide bar, slide that over and sit back. Takes about 4-5 minutes depending on how full your device storage is. This does NOT backup internal SD! After this is done, you have created a nandroid backup that when restored will put the system exactly how it was last time you used it. You can make multiple backups of multiple ROMs without issue, just however big your SD card is to hold them.
The restore menu, or the OOPS SAVE MEH menu is your best friend. This will restore you back to the last state your device was in for the backup that is restored. By default TWRP saves by date and time, however you can rename this with any file manager, never caused me any issues. Theonew reminded me of an MD5 issue that can happen on renaming backups, if this does happen, rename it back to the stock naming system to fix it. Generally I'll just append the ROM name to the front, so instead of 2012-6-14--18-25-01 it'll be CM9-2012-6-14--18-25-01. Make sense? That way to restore it in case of error, just drop the name. Easy. Theonew also did some testing, and confirmed that spaces in the folder name WILL cause MD5 errors and fail the restore, please use ONLY dashes and underscores (- and _ lol) in the folder name! To restore make sure you are on the Home screen, then select Restore. In the window you will see a list of your current backups, select one. Next screen has check boxes, make sure System, Data, Boot and Recovery are checked, then slide the bar to begin. This takes a bit, make sure you let it finish! Once done, your system will be at the last point it was used for that backup.
Advanced restore...I'm to lazy to reload and reset up my stuff after a ROM flash, so this is the fast and dirty way of doing it. If you flash a ROM and you don't feel like manually restoring your apps, you can uncheck System, Recovery and Boot, and leave only Data checked. This will restore your user installed apps and settings over the current ROM install. I don't recommend this for different ROMs, only for updates of the same ROM! Up to you but if you get alot of issues, you'll know why. After advanced restoring, go to the Home Screen and select Advanced, then Fix Permissions. Press Home again and select Wipe. Wipe Cache and Dalvik Cache, then reboot system.
Alright, enough already lets get our flash on! From the Home screen, select Wipe, then press on Cache, Dalvik Cache, Factory Reset, and System. Optional you can wipe Battery Stats if your battery seems off. Leave the rest alone. Once these are all wiped, go back to the Home screen, and press Install. The window on the left is your device folders, window on the right is contents of the current folder. I hope you remembered where your rom.zip is, because you select it here. Press on the zip for the ROM of your choice, then slide the bar to flash it. After that is done, select the left button Wipe Cache and Dalvik, then select Reboot system.
OK LETS ROCK THAT ROM! Woah, slow down scooter, there's a few things to do, or not do, first. After it boots, meaning it's past the boot animation and is sitting on the Welcome screen, set it down and leave it alone for 10 minutes or longer. Don't sign in, don't do anything, just leave it be for 10 minutes. If you can't think of what to do to manage the time you have to wait for awesomness of custom ROMs, read the thread of the ROM you chose. Set the thread for 50 posts and just read. After 10 minutes, hold the power key, and either choose Power off or Reboot, Reboot depending on ROM used. After it finishes rebooting (that was alot faster wasn't it?) you can go ahead and do the Welcome stuff, log in to Google, setup your device, download your apps, restore your apps etc. After restoring your apps (try not to restore app + data if possible, though I know games and stuff you'll want to) reboot one more time. After that second reboot, use the tablet as normal. From my experience this offers the BEST possible ROM usage, a vast reduction in lag, bugs, and oddness.
What else can I do with the TWRP Recovery? Well, the most useful tools are Backup, Restore (and advanced restore) and the wipe menu, plus fix permissions. Those generally can fix anything thats wrong. If you notice alot of lagging, FCs or general unruliness, wipe Cache, Dalvik Cache, and Fix Permissions. Another useful ability is ADB, which is beyond the scope of this section, but may be included generally in a later section. ADB can be used to repair otherwise bricked devices, and offers a very large amount of tools that you don't normally get to use in Recovery. Keep in mind ADB is powerful, and can quickly destroy your device, so please, be careful using it.
Placeholder for CWM Recovery section - coming soon!
CWM Recovery for A100 by ptesmoke
Section 3
Additional Recovery tools:
Blackhole Wipe/Nullifier by pio_masaki
These are tools I created to make wiping a little easier, but please read the post completely before deciding to use it! There are multiple versions, and they can and will wipe internal SD, as well as take up to 40 minutes to run (1, not all). Please ask questions if you have them there and I will help as best I can!
AROMA Recovery Touch Recovery
A touch file manger to be used in recovery, even on non touch CWM! Good for renaming backups as soon as you make them (I tend to forget afterwards and get confused by 6 backups with just dates). Also moving a downloaded zip from internal to external or whatever before running a system wipe, any number of things. Please read the post completely before using this tool! It can cause damage if not used properly and with care!
Kernels:
linuxsociety / godmachine's A100 OC Kernel
Plenty of extra balls thrown in for good measure, a good place to look if you like high benchmarks and plenty of extra goodies baked in. Available in a few flavors, with some GPU OC thrown in for good measure.
ezterry's A100 OC/UV Kernel
The only other option for a kernel that we have besides stock and CM9's included kernel. Excellent kernel, really wakes up the A100, allows up to 1.5 GHz for some extra umph and undervolting to help conserve power on our very weak batteries.
PRO TIPS:
The 10 minute rule:
The reason I mention waiting 10 minutes on first boot of a ROM install is this: Alot of things happen the first time the ROM runs, alot of scripts run, the kernel has to settle and search and move things, files are flying all over the nand. Think of a tornado in a cubicle. That's first boot for your device. Allowing it 10 minutes uninterrupted allows all of that to happen and settle down. The following reboot lets all that new info fire up from it's new home and continue settling in. After restoring and downloading apps, that reboot allows that new info to settle into it's new home and the system to catch up. This isn't device specific, rather a general rule of thumb for all devices. Does not really apply to restores unless something is changed.
Undervolting:
Undervolting on this device is only available on ezterry's excellent kernel. The following is a rough guideline of how to do it, and do it right:
Start small, don't just dump it -200 and expect it to work. For the time you're testing, make sure it is NOT set for boot. If something goes wrong you don't want it doing it everytime it boots, right? Go in small increments, -25 is usually OK. For now, don't overclock. Starting at 1 Ghz, lower every speed range down -25, and run the device for at least 10-20 minutes, normal use, hard use, benchmark, browse the web, watch a HD movie. If all is fine and its not lagging, freezing, force closing or heating up more then usual, move everything to -50, and repeat. My device freezes at -150 but runs stable at -145. Every device and chip is different, mine may do -145 yours may do -175 or only -50.
Overclocking
Overclocking is available on ezterry's bodacious (already used excellent) kernel, up to 1.5 GHz, and the CM9 kernel up to 1.4GHz. As with undervolting, this should be done in small steps and tested between to find your max. Generally 1.5 GHz is fine for every device, however all devices and chips are slightly different, and some may not be stable at it. Mixing undervolting and overclocking can be tricky, but following the steps above for undervolting you can find that sweet spot for your device.
Batteries and why they fail
This section is entirely my opinion, other's swear one way, other's another, but this is what I've concluded from multiple posts for this device.
Consider 10% to be 0%. There have been more then a couple posts that say they let their battery fall below 10% and they can NOT get the device to work properly again afterwards. I think there's a few reasons for this, and I'll explain them now. First, a lot of batteries tend to have some kind of breaker protection if the voltage drops below a certain level. This is to prevent damage to the cells, which it does, however we can't close that breaker to restore activity from the battery, IE, it's dead anyways. This threshold varies from one device to another, one battery pack to another, some can go to 0% and be ok, others can't. I say voltage level, because while draining the voltage can spike up, and it can also spike down, which can fall below this threshold even though it says you have 5% battery life remaining, and trigger the protection.
The acer does not seem to power on without a working battery. If the battery is "dead" it doesn't seem to boot. Its basically a brick until either the battery is replaced (by acer I would assume) or the motherboard is replaced due to some sort of damage causing this. Replacing the motherboard costs almost as much as a new unit, so at this point, just save up some more and buy a new one.
For this, I never go below 10% if ever possible. Even on my phones.
Another thing I try not to do is charge in bursts, or at random times. Basically, I plug in at 10%, then allow full charge to 100%, I don't charge in between those ranges, and I don't charge for periods less then 100%. So I don't plug in at 48% then unplug at 60%. I've learned this one from my Evo 4g, the battery was fantastic for months, then I started using the car charger to top off, and the battery life over the course of 2 weeks took a very noticable hit on overall life. I lost easily 4 hours a day usage on it. This on a phone and ROM combo that got me 16 hours a day.
Again this entire section is just what I've noticed and is purely my opinion, please do whatever you please with your device, it is yours after all!
ADB and Fastboot...is it really a faster boot?
No, fastboot isn't a toggle to boot at warp 9. Fastboot is a mode you can put your bootloader into for flashing the system for upgrades, repairs, mods, or general havok if you're not careful. The bootloader is what you see when you first turn on your device, that lovely Acer logo with the text up in the left corner (usually saying bootloader version and Unlocked Mode if unlocked, or nothing if it's locked). If you go into fasboot, it will say download usb protocol, so if you see that, you're in fastboot mode for whatever reason.
How do I get into fastboot mode?
Well you can do this in a couple ways, either Quickboot app (reboot bootloader), if you're on CM9, the power menu will give the option, or you can use ADB for it.
adb reboot bootloader
I'll explain some more about adb after fastboot, I know its odd, but one does have something to do with the other at times.
Once you've rebooted to the bootloader (device will turn off, vibrate, then boot to acer screen) you can then issue your fastboot commands assuming 2 things:
Acer USB drivers are installed and working correctly (if you use adb to reboot, then it is)
Your tablet is connected to your PC over USB.
Now, at this point, its up to you to do whatever you want, but BE CAREFUL USING FASTBOOT FLASH! It doesn't care or check what you're flashing, it'll just flash it. For example, I flashed CWM Touch recovery to boot once because I was distracted and mixed up the images for whatever reason. End result: Can't boot android. Why? Because boot was recovery, it only booted to CWM Touch recovery. Booting to actual recovery booted to TWRP, which was my previously installed recovery. I got it back easy enough once I figured out what I did wrong, but not all mistakes are reversible, or fixable!
General Fastboot uses and commands...
general layout goes like this:
fastboot (this is calling the command) flash (this is what fastboot will do) recovery (where it will send it to) recovery.img (the file it will send)
So, it looks like this:
fastboot flash recovery recovery.img
it will then flash whatever img to whatever partition you said, and let you know when it's done. You can flash any img to any partition, provided it fits, which means you do have to be careful about what you flash to where!
when you are finished with fastboot:
fastboot reboot
There are plenty of other commands, but the general basic use of fastboot is to flash a recovery or bootloader, so that is what I laid out above.
This section is hugely in need of improving, I know, but the guide in general is still rough, my apologies.
What about ADB?
ADB, or Android Debugging Bridge, can be used in System or in custom recoveries to interact with the device behind the curtain, meaning what you do isn't readily apparent on the device itself, unless you do something obvious like reboot it. ADB has a ton of commands, in particular in ADB Shell mode (you drop into the device shell itself, issuing commands from within itself, not from the PC).
Some random ADB commands:
adb reboot (where to reboot to) so:
adb reboot recovery
adb pull (what file to copy) /(where to copy file to) so for example, a recovery log to the adb working folder:
adb pull /cache/recovery/last_log recovery.txt
adb push /(file to copy to) /(file to send to device) so for example, placing that recovery file back into the device:
adb push recovery.txt /cache/recovery/last_log
Thats all the time I have for now, sorry in advance, I'm still working on all of this, I swear lol
Placeholder for additional tips and usage, some ADB stuff, and anything else I can think of.
Placeholder for Toubleshooting.
Placeholder for FAQS.
System Modding
justjackyl's Iconia A100 CM10 Setup & Use Tips/Tricks
A good guide to check out to try to get the most out of your A100 on CM10 (or any JB ROM like Sosei/black bean). A must read for those new to CM10/JB on these devices or in general. Not an outright mod, but a good source of information about some modding you should browse.
Hulu Flash Hack by NoSudo
What the Hulu Flash Hack by NoSudo does is allow you to use our android browser (setup according to the thread) to watch sites like Hulu to play on your android flash player. Its basic function is to scan for, then backup, then place a modified libflashplayer.so file. Setup with script manager and run at boot for best results. As always, read the thread for more information.
Mount Swap by crossix
What the Mount Swap by crossix does is pretty awesome, it mounts your external SD as internal, meaning your 32GB external SD card shows as internal, and is used for your apps, data, downloads, whatever, as if it was your internal SD. Internal SD is then mounted as external SD. It's operation is based on install-recovery being replaced with crossix's version. Instead of replacing recovery, it runs the mount swap. Requires Root, as the file is placed into /system/etc. Designed for stock/modified stock ROMs, it can be used with AOSP/AOKP ROMs by using script manager and setting it to run as Root at Boot. Please read the thread for the files and information on how to use it.
Adapted to ICS Build Prop Mods by patrick_spd4u adapted from crossix
What the Build Prop mods do is pretty basic, however can greatly increase the abilities of the A100, including faster boot times, more apps/games available for download in the Play Store, and tons of other stuff. Adapted from crossix's mods for HC.
Guide to 2 ways of running the crossix mount swap script, Acer based and AOSP/AOKP based
Direct paste from a post I made about this earlier...details using ES File Manager, however you can adapt it for any root file manager.
Using your tab, download the crossix mod zip file.
Unzip the file to get your epic mount swap mod by crossix, it can be unzipped anywhere.
At this point, I'm using ES File Manager but you can use Root Explorer or whatever. I'll be giving directions for ES.
Go into settings, scroll down and check the box for Up to Root.
Scroll a little futher down, same menu, and check the box for Root Explorer. Tap Yes, then allow when SU asks.
Now check the box next to Mount File System.
A little notice should pop up saying system is writable. If it fails at this point, you'll need to reroot, though it should work fine.
Press back, and go to where your crossix install-recovery.sh file is, hold your finger on it, and select Copy from the menu.
Press back and keep pressing it until you get to /. You'll see folders like acct, cache, config, d, etc.
Scroll down to system, and tap on it to go into system
Tap on etc to enter the etc directory.
You should now be in /system/etc, check up top there will be the address bar showing where you are.
You shouldn't have an install-recovery.sh file there, but if you do, long press it and select rename, then rename it install-recovery.bak.
On the upper buttons, select paste.
Now hold on the install-recovery.sh and select Properties, all the way at the bottom of that menu.
Next to where it says permissions, click Change
You will get a new window showing 3 rows of 3 colums of boxes with Xs.
Check the boxes so it looks like this:
XXX
XXX
XXO
Click on OK, then OK again, you should be back to the main ES window. Go ahead and hit home, or hit back over and over to exit.
Stock or Modified stock ONLY
Reboot the device by whatever method you prefer.
Once it finishes booting, wait a minute, then check your Settings>storage and your external SD card should show as internal. You only need to do this 1 time, it will continue to do this after.
AOSP/CM9/AOKP ONLY
Go to the Play store and download Script Manager(smanager).
After it installs, open the app then select Browse as root, Allow when SU asks, then click OK.
It will likely be listing /mnt/sdcard as your default directory, press the folder with .. to go back up until it says /
Click on system, then etc
It should now show /system/etc
Find your install-recovery.sh file, and it will open a new window.
Pay close attention here!
Right under the buttons that say Run Exit Edit Save are some icons,
Fav Su Boot Net Wick Ntfy
Press on Su and Boot, then click on Save.
Now exit smanager and reboot.
Wait a minute, then check settings>storage and your external SD should show up as Internal.
Don't disable smanager from running at boot! If you disable it, your script won't run. smanager must remain installed, or the script won't run.
Thanks to:
ZeroNull: For being one of the pioneers for getting our devices cracked open for our amusement!
ptesmoke: Also for being a pioneer in getting custom recoveries on our devices!
vache: For releasing the ICS leaks way ahead of schedule and hosting them for us to use and abuse!
civato: For releasing his Flex Reaper ROMs on our devices, his modified stock ROMs are still (IMO) the slickest available!
da-pharoah: For helping me understand how recoveries work a little better, allowing me to create Blackhole Wipe/Nullifier, and general encouragement for creating things for this device! (G2x and KF forums)
ezterry: For creating an OC/UV kernel that so far is the best EVER for any ROM on our device!
Theonew: reading ALL of that, and providing some nice info I missed and left out, and catching typos (Almost made it...)
crossix: that mount swap mod is just awesome, I never run a ROM without it!
NoSudo: creating a method to easily modify the system to watch HULU and other sites that normally won't allow it!
There's more I'm forgetting, I'll be adding more as I remember, I promise.
Even though I knew everything you posted, it was very interesting and I recommend everyone (even if you don't need it or already know) to read this guide. Its a marvellous read with some humor to keep you going. One thing though:
- You stated that its only safe to wipe "cache, dalvik cache, data, and system". Technically, this is not true. Flexrom and boot partitions are also safe to wipe (and for some roms for certain devices, the boot partition must be wiped for stable kernel performance, etc.). It's also a good idea to wipe sd-ext if you have it set up (in most cases). Once again, excellent guide (you even did a part of my job ).
Theonew said:
Even though I knew everything you posted, this is a brilliant guide and I recommend everyone (even if you don't need it or already know) to read this guide. Its a marvellous read with some humor to keep you going. One thing though:
- You stated that its only safe to wipe "cache, dalvik cache, data, and system". Technically, this is not true. Flexrom and boot partitions are also safe to wipe (and for some roms for certain devices, the boot partition must be wiped for stable kernel performance, etc.). It's also a good idea to wipe sd-ext if you have it set up (in most cases). Once again, excellent guide (you even did a part of my job ).
Click to expand...
Click to collapse
While sd-ext is safe to wipe, using factory reset wipes that for you, and I think, could be wrong, but cwm does it on data wipes. Part of why I missed it was I confused it with my phone, where wiping sd-ext bricks the phone, and also people mix it up with external SD. I'll add it in as its a very valid point, and I shouldn't let personal things interfere with the guide.
As for boot, our devices don't need that wiped and honestly asks for problems if someone doesn't restore or install a rom to cover it. I've never wiped it on any device, however I will also add that in as it is good info. I left it out of "safe" to prevent possible issues from wiping it.
I forgot about flex and I honestly don't know what it is for lol. Again thanks for reminding me and I'll add it in.
Of course I'm open to posts like these please give some input on what I missed or need to correct, I want this to be the go to guide for the a100 for anything needed!
Tapatalked from my Galaxy S II.
pio_masaki said:
I forgot about flex and I honestly don't know what it is for lol....Of course I'm open to posts like these please give some input on what I missed or need to correct, I want this to be the go to guide for the a100 for anything needed!
Click to expand...
Click to collapse
In your 4th to last sentence of the "Advanced Restore" section, you have a typo . Anyways, according to here: forum.tegraowners.com/viewtopic.php?f=10&t=149, Flexrom is "a partition on the nand that acer made to hold some proprietary apks and build information".
Oh damn almost made it without a typo...not bad for just running through all of that without really checking on it..other then it was english.
Corrections and additions added to the posts, thanks!
pio_masaki said:
Oh damn almost made it without a typo...not bad for just running through all of that without really checking on it..other then it was english.
Corrections and additions added to the posts, thanks!
Click to expand...
Click to collapse
One more thing - This occurred for one of my other devices, but the problem may still exist here. I haven't tried it with TWRP, but renaming CWM backups can cause a md5 mismatch error to occur. If this happens, simply rename it back to a date (in the default format).
I've never ran into that issue on any of my devices in CWM or TWRP, however I have heard of it occuring, definatly something I should add in there. Full of good catches tonight aren't you?
Awesome write up, thanks you guys!!
What about Zeronull's .014 v1.2 rom? http://forum.xda-developers.com/showthread.php?t=1574897
I'm still digging through all the threads for the ROMs, however I included the currently developed or recently released ROMs first, ZN has since released Green ICS, which is included already. I do plan to list every ROM, but it'll take some time to finish this guide up with as much info as possible, then go back and add things in.
pio_masaki said:
I've never ran into that issue on any of my devices in CWM or TWRP, however I have heard of it occuring, definatly something I should add in there. Full of good catches tonight aren't you?
Click to expand...
Click to collapse
I tested it to see if it occurs, and it turns out that it does. I made a backup with CWM, renamed it then tried to restore, and it immediately gave me the "md5 mismatch" error.
Theonew said:
I tested it to see if it occurs, and it turns out that it does. I made a backup with CWM, renamed it then tried to restore, and it immediately gave me the "md5 mismatch" error.
Click to expand...
Click to collapse
That is so weird I never have that issue cwm or twrp. I use es file manager..maybe why?
Tapatalked from my Galaxy S II.
pio_masaki said:
That is so weird I never have that issue cwm or twrp. I use es file manager..maybe why?
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
I renamed it using Root Explorer. Have you tried renaming them to something including spaces?
Theonew said:
I renamed it using Root Explorer. Have you tried renaming them to something including spaces?
Click to expand...
Click to collapse
No, as its a Linux based environment I use dashes and underscores never spaces in directory names. That shouldn't cause md5 fails because the md5 is based per zip not the folder name. If you could try an experiment and rename with es I'd appreciate it, and maybe with and without spaces. I'll try root explorer when I get home and see if it causes issues.
Tapatalked from my Galaxy S II.
pio_masaki said:
No, as its a Linux based environment I use dashes and underscores never spaces in directory names. That shouldn't cause md5 fails because the md5 is based per zip not the folder name. If you could try an experiment and rename with es I'd appreciate it, and maybe with and without spaces. I'll try root explorer when I get home and see if it causes issues.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Done. The error seems to only occur when spaces are used in the name.
Theonew said:
Done. The error seems to only occur when spaces are used in the name.
Click to expand...
Click to collapse
Thanks for taking the time to figure that one out, I've been testing a new rom on my phone plus a new test T20 kernel for ezterry and getting cm9 build 5 up, just kinda managed to forget that experiment lol
I'll have some time...maybe...to append that new bit into that section tonight. The "free" time has been spent trying to get aokp for the a100 but my lack of experience, random problems with the repos and devs ignoring my PMs its been going slow. And by slow I mean nowhere.
Tapatalked from my Galaxy S II.
Great read. Sorta like flashing for dummies. Thaanks for your work.
Sent from my HTC Glacier using Tapatalk
It's great to have all this information compiled in one location. Looking forward to your next installment. THX

[GUIDE][FAQ][Android 4.4 KitKat] Installing & Customizing CM11 or SlimKat

This guide explains how to install and update CyanogenMod 11 (CM11) and SlimKat roms (aftermarket firmwares of Android 4.4) on your Motorola Defy (MB525) or Defy+ (MB526). Neither the CyanogenMod development team nor the Slim Roms development team officially support the Defy. Thankfully, a number of independent developers (listed below) are working hard to port those roms to the Defy, and the present versions are mostly (but not completely) bug-free and stable.
Please note: The latest CM11 and SlimKat roms for the Defy still have a few bugs, most of which are explained in a bug list that is frequently updated by okij. Although okij's bug list concerns the CM11 roms built by Quarx, most of these bugs also apply to TJKV's SlimKat roms, which are based partly on Quarx's sources.
If you just want a perfectly stable, bug-free phone, and don't care about having the latest and coolest features of Android, CM11 and SlimKat are not for you. I recommend installing CyanogenMod 7 (CM7) instead: it's very fast and perfectly stable. However, CM11 and SlimKat are continually becoming more stable, and are already usable as daily drivers if you can live with the few remaining bugs.
How to install Android 4.4 SlimKat or CM11 on the Motorola Defy or Defy+
Step 1: Download the correct files for installation.
If installing SlimKat, download the rom (Slim-mb526-4.4.2.build.4-UNOFFICIAL-20140407-2344.zip) and Google Apps package (minimal_Slim_AIO_gapps.4.4.2.build.4.zip) here.
If installing CM11, download the rom here (or here) and the minimal Google Apps package here (or here or here). (You want the file called "GApps_Minimal_4.4.4_signed.zip". Do NOT try to install the "Standard" Google Apps package, as there is not enough room on the Defy's system partition.)
Customize the rom file if desired. (See "Tips for customizing & improving performance," below.) Then put both files on your phone's SD card. Also download defy_twrp_recovery_2.6.3.0.zip and safewipe.zip, and put those files on the SD card too.
Note: SlimKat build 4 is very stable, but it does have a bug that causes the phone to reboot into recovery mode automatically if the phone encounters a telephony error, instead of rebooting normally. To fix this issue, download DefyParts.apk here and replace the old DefyParts.apk by following the instructions in this post.​
Step 2: Install Team Win Recovery (TWRP) version 2.6.3.0 (or newer).
If you have already installed a custom recovery on your phone (e.g. ClockWorkMod or an earlier version of TWRP) and you know how to use it, just flash defy_twrp_recovery_2.6.3.0.zip and proceed to step 3. If you've never used a custom recovery, keep reading.
If you're using a stock rom from Motorola, you first need to root the phone (I recommend using either Framaroot or SuperOneClick), then install 2ndInit. Run the 2ndInit app and use it to install the custom recovery (ClockworkMod Recovery). Then reboot the phone, and watch the small LED light at the top of your phone. If the recovery was installed properly, the LED will light up with a blue color for a few seconds during startup. Allow the phone to fully boot up, then reboot the phone again and watch for the blue light. As soon as you see the blue light, press the volume down button to enter the bootmenu. Use the volume buttons to navigate the menu and the power button to select an option. Select Recovery > Custom Recovery > Backup and restore > Backup (all), and wait for the backup process to complete. This will create a backup of your system on your SD card, so you can revert to the stock rom later if needed. Next, select Go Back > install zip from sdcard > choose zip from sdcard, and install defy_twrp_recovery_2.6.3.0.zip.
Step 3: Install CM11 or SlimKat, and the corresponding Google Apps package.
After installing TWRP 2.6.3.0, reboot the phone and enter the bootmenu again by pressing the volume down button when you see the blue LED. (Note: If you're updating from a recent version of SlimKat or CM11, you won't see any blue light. Instead you'll see a screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup.)
Enter TeamWin Recovery, which you can navigate with the touchscreen rather than the volume buttons. Wait 30 seconds before proceeding, to make sure the recovery is behaving in a stable way. (If the phone spontaneously reboots, just try again.)
Select Install, choose safewipe.zip, then swipe to confirm the flash.
In the same way, flash the rom of your choice (either SlimKat or CM11), followed by the Google Apps package.
Reboot the phone. The first boot will take a while (typically 5-10 minutes), since the phone has to build the Dalvik Cache.
Step 4: Set the correct baseband, and adjust performance settings.
Go to System settings > Advanced options > Device > Baseband selection, and make sure that the correct baseband is selected for your region and carrier. (Note: This step is not necessary if you already changed the default baseband in the zip file. See "Tips for customizing & improving performance," below.)
I also strongly recommend configuring the rom for better performance, by following the tips listed below. (See especially the tips about using Aero Kernel Control. This will help with many problems, for example the infamous call wakeup delay issue.)
Step 5: Thank our awesome developers, and donate to them if you can.
You can find donation links under any post by the developers. (Just look for the button that says "donate to me.") Here's the donation link for Quarx.
How to update SlimKat or CM11 to newer versions (or downgrade to older versions)
Step 1: Backup your current rom, apps, and settings.
I recommend using Online Nandroid Backup to create TWRP-compatible backups, for the reasons mentioned here (see bug #36). In the Online Nandroid Backup app, select Custom Backup > Backup Type > TWRP. Then select Backup Mode > Selective, and select the "system" and "data" partitions to backup. Make sure the Save Location is set to /sdcard, and also check the box to "Exclude Dalvik Cache." Then press the blue arrow (looks like a "play" button) at the top right corner of the screen to begin the backup.
Also back up your apps and settings with Titanium Backup.
Step 2: Download the updated rom.
Customize the rom file if desired. (See "Tips for customizing & improving performance," below.) Then place it on your phone's SD card along with the appropriate Google Apps package. [Note: if using CM updater, you don't have to download the rom ahead of time.]
Step 3: Install the updated rom using one of the following three methods:
Note: If switching from SlimKat to CM11 or vice versa, you must use the clean install method.
"Clean" install (recommended)
- Boot into TWRP by pressing the menu button when you see the bootstrap image (the screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup), which should appear just after the Motorola logo disappears and before the boot animation begins.
- Select "Install" and flash safewipe.zip, then flash the updated rom, followed by Google Apps.
- After rebooting the phone, you'll have to restore your apps and settings using Titanium Backup. Don't restore settings for system apps unless necessary, as that may lead to problems.
"Dirty" flash (easier, but may cause problems)
- Boot into TWRP and select Wipe > Advanced Wipe, and select Dalvik Cache, Cache, and System (not Data), then swipe to wipe. (WARNING: Wiping the system partition also deletes the custom recovery, so you must either flash a rom or restore a backup before rebooting the phone. If the phone is rebooted before a new system is installed, it will be "soft bricked" and you'll have to flash a stock sbf with RSD Lite to recover it.) Then press the back button to return to the main menu and select Install. Flash the updated rom, followed by Google Apps. Now it is safe to reboot the phone.
- Since this method does not affect the /data partition, you won't have to restore all of your apps and settings, but you may still need to switch the baseband. If you encounter any bugs or problems after updating the firmware by this method, do not report them. First try a "clean" install, and check whether that solves the issue.
CM updater method (easiest, but may cause problems)
- If you're using CM11, you can update via the built-in CM updater located under Settings > About Phone > CyanogenMod Updates. (Obviously this won't work on SlimKat.)
- If you encounter any bugs or problems after updating the firmware by this method, do not report them. First try a "clean" install, and check whether that solves the issue.
Tips for customizing & improving performance
How to customize the rom before installation:
Install 7-zip on your PC.
Right-click on the CM11 or SlimKat zip file and select 7-zip > Open archive. (Don't extract it; just open it.) Now you can:
Remove unnecessary files to save space on the system partition. For example, you can navigate to system > media > audio, and delete any ringtones you don't use. You can also delete unused apps from system > app. See @x53's post here for a list of system apps that are safe to remove; see also here and here for more info. Here's a list of system apps that I removed before installing SlimKat: BasicDreams (live wallpaper), Browser (I use Next Browser instead), Calendar, Dashclock, Deskclock, Email (I just use Gmail app), Exchange2, Gallery2, Livewallpaperspicker, PhaseBeam (live wallpaper), PhotoTable, PicoTTS, Slimcenter, SlimFileManager, SlimIRC, SoundRecorder, VisualizationWallpapers.
Replace the default bootanimation in system > media. (Just drag and drop your custom bootanimation to replace the original.)
Replace the default bootstrap image in system > bootstrap > images.
Change the default baseband. To do this, navigate to system > etc > motorola > basebands, and find the zip file that corresponds to your region and carrier. Drag that file out to a folder on your PC, and extract (unzip) it. Then drag and drop those extracted baseband files into system > etc > motorola > bp_nvm_default, replacing the default baseband files in the rom.
Edit build properties. To do this, find the build.prop file in the system directory, and drag it out to a folder on your PC. Open the file in Notepad++, and edit the build properties as desired. (For example, you can change the LCD screen density by editing the line that says "ro.sf.lcd_density=". The default density in CM11 is 240, and the default in SlimKat is 213. Larger numbers make icons appear larger on your screen.) After making any desired changes, save the file and drag it back into the rom zip file where you found it, replacing the original.
After installation, configure the rom for better performance:
Install Aero Kernel Control from the Google Play store, which will allow you to tweak many settings to improve the performance of your phone. For starters, I recommend the following: In the Aero Control app, go to CPU Performance > Governor Settings, and select “ondemand”. The default is Interactive governor, which may be able to deliver slightly better performance if you know how to tweak its settings, but its default settings aren’t very good, so I recommend using On Demand at least initially.
If you want to try using Interactive governor, I recommend the following settings: open Aero Kernel Control, go to CPU Performance, select Interactive governor, then tap the little phone icon at the top right corner of the screen to open the settings for the Interactive governor. Set suspend_enabled to 0. That should help to reduce the call wakeup delay. Changing hispeed_freq and input_boost_freq to your maximum value (e.g. 1200000 if you've overclocked to 1200 MHz) will also boost performance, though you may see a slight drop in battery life. Note: Interactive governor is not recommended for CM11 builds prior to the 06-10 nightly, because the suspend/resume handler was missing. (See okij's note on bug #26 for more info.)​
Open the HWA Settings app (which is already installed as part of the rom) and disable HWA for all apps except ones that really need it. (Explanation: HWA requires more RAM, and the Defy is already short on RAM, so enabling HWA usually does more harm than good. That's why it's best to disable it whenever it's not really needed for an app to function properly.)
The following apps require HWA: Camera, Dialer (on CM11 only), Google Maps (version 7+), Chrome browser. Other apps may also require HWA. If an app doesn't display properly, try enabling HWA again to see if that solves the problem.​
Install Greenify, which you can use to “hibernate” any apps that you don’t want to run automatically at startup.
Other tips & suggestions:
You may wish to install Google Camera instead of the stock camera, for the reasons mentioned here.
For offline voice recognition, see here.
For better GPS performance, you may want to try flashing this zip and/or using this app. (Thanks to @Male_zvire and @okij for recommending these solutions.)
FAQ & what to do if something goes wrong
A freshly installed rom takes some time to "settle" while various services run in the background, so the phone may be a bit unstable at first. If you're still encountering errors or other problems after a few hours, first check the bug list and use the XDA forum search feature to see if the issue you are having has already been reported.
If you think you've found a new bug, don't just complain about it; try to help solve it by taking logs. @measel has provided a very helpful guide for taking logs.
What if the phone doesn't boot up properly?
If you can still access the custom recovery, just flash safewipe again and re-install the rom, or restore a backup. (To enter TeamWin recovery after installing SlimKat or CM11, press the menu button when you see the screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup. That screen should appear just after the Motorola logo disappears, and before the boot animation begins.)
If you can't access the recovery, you may need to flash an sbf file using RSD Lite. Be careful! Flashing an sbf file improperly is one of the few things that can actually hard-brick the Defy, and if you flash the wrong sbf file for your phone, it may be impossible to restore your phone back to its original firmware. Read the All-in-One Defy Beginner's guide for more information about sbfs and RSD Lite. You can also check out the Motorola Defy wiki page for other tips and tutorials.
A special thanks to @Quarx, who has been faithfully updating our phone to newer and better firmwares since the beginning of Defy history, and has undoubtedly put more work into this project than anyone else. Thanks also to our many other developers, past and present: @TJKV (who uses Quarx's kernel sources to port SlimKat to the Defy), @Blechd0se (who has made significant contributions to the kernel development for the Defy and also developed the Aero Control app that we use to fine-tune the performance of our phones), @SlugZero, @YetAnotherForumUser, @struq, @htto, @Epsylon3, @maniac103, @walter79, @czechop, @kabaldan, and @Kayant. Many thanks to all of them, and to anyone I may have forgotten. Thanks also to @okij and other Defy users who have helped with testing new builds and identifying bugs for the developers to solve.
suggestion for improvement
Thanks for the guide. I'm pretty sure it is very useful for beginners!
I would suggest to try to get rid of as much text as possible and make it more step-by-step-y, you know what I mean? People (at least I recognized that on me) tend to give up quickly when it comes to reading. Right now it looks really difficult!
Just a suggestions. People will still appreciate your work as is. Thanks.
CM 7 and SBFS
Proverbs2 said:
The following is a guide that I wrote for one of my family members, and I decided to post it here so that others may benefit. I know there are numerous similar guides already in the forums, but they have not been updated recently. I intend to keep this guide updated for as long as I own a Defy (and I have no plans to get rid of my beloved phone anytime soon).
This guide explains how to install either CyanogenMod 11 (CM11) or SlimKat roms (aftermarket firmwares of Android 4.4) on your Motorola Defy (MB525) or Defy+ (MB526). Please note that neither the CyanogenMod development team nor the Slim Roms development team officially support the Defy. Thankfully, a number of independent developers are working hard to port those roms to the Defy, and the present versions are mostly (but not completely) bug-free and stable. A special thanks to @Quarx, who has been faithfully updating our phone to newer and better firmwares since the beginning of Defy history, and has undoubtedly put more work into this project than anyone else. Thanks also to our many other developers, past and present: @TJKV (who uses Quarx's kernel sources to port SlimKat to the Defy), @Blechd0se (who has made significant contributions to the kernel development for the Defy and also developed the Aero Control app that we use to fine-tune the performance of our phones), @SlugZero, @YetAnotherForumUser, @struq, @htto, @Epsylon3, @maniac103, @walter79, @czechop, @kabaldan, and @Kayant. Many thanks to all of them, and to anyone I may have forgotten. Thanks also to @okij and other Defy users who have helped with testing new builds and identifying bugs for the developers to solve.
Please note: The latest CM11 and SlimKat roms for the Defy still have a few bugs, most of which are explained in a bug list that is frequently updated by okij. Although okij's bug list concerns the CM11 roms built by Quarx, most of these bugs also apply to TJKV's SlimKat roms, which are based partly on Quarx's sources.
If you just want a perfectly stable, bug-free phone, and don't care about having the latest and coolest features of Android, CM11 and SlimKat are not for you. I recommend installing CyanogenMod 7 (CM7) instead: it's very fast and perfectly stable. However, CM11 and SlimKat are continually becoming more stable, and are already usable as daily drivers if you can live with the few remaining bugs.
Installation instructions for Android 4.4 SlimKat or CM11 on the Motorola Defy or Defy+
Step 1: Make sure you've downloaded the correct files for installation.
If installing SlimKat, download the rom (Slim-mb526-4.4.2.build.4-UNOFFICIAL-20140407-2344.zip) and Google Apps package (minimal_Slim_AIO_gapps.4.4.2.build.4.zip) here.
If installing CM11, download the rom here and the minimal Google Apps package (4-16_GApps_Minimal_4.4.2_signed.zip) here.
Put both files on your phone's SD card. Also download defy_twrp_recovery_2.6.3.0.zip and safewipe.zip, and put those files on the SD card too.
Step 2: Install Team Win Recovery (TWRP) version 2.6.3.0 or newer.
If you have already installed a custom recovery on your phone (e.g. ClockWorkMod or an earlier version of TWRP) and you know how to use it, just flash defy_twrp_recovery_2.6.3.0.zip and proceed to the next step. If you've never used a custom recovery, keep reading.
If you're using a stock rom from Motorola, you first need to root the phone and install 2ndInit. Run the 2ndInit app and use it to install the custom recovery (ClockworkMod Recovery). Then reboot the phone, and watch the small led light at the top of your phone. If the LED lights up with a blue color for a few seconds during startup, the custom recovery was installed properly, but you still need to upgrade the recovery to TWRP 2.6.3.0. Reboot the phone again and watch for the blue LED light. As soon as you see the blue light, press the volume down button to enter the bootmenu. Use the volume buttons to navigate the menu and the power button to select an option. Select Recovery > Custom Recovery > Backup and restore > Backup (all), and wait for the backup process to complete. This will create a backup of your system on your SD card, so you can revert to the stock rom later if needed. Next, select Go Back > install zip from sdcard > choose zip from sdcard, and install defy_twrp_recovery_2.6.3.0.zip.
Step 3: Installing CM11 or SlimKat
After installing TWRP 2.6.3.0, reboot the phone and enter the bootmenu again by pressing the volume down button when you see the blue LED. (Note: If you're updating from a recent version of SlimKat or CM11, you won't see any blue light, instead you'll see a screen that tells you to either press the menu button to enter recovery or the search button to continue with normal bootup.)
Enter the newly installed TeamWin Recovery, which you can navigate with the touchscreen rather than the volume buttons. Wait 30 seconds before proceeding, to make sure the recovery is behaving in a stable way. (If the phone spontaneously reboots, just try again.) Then select Install, choose safewipe.zip, then swipe to confirm the flash. In the same way, flash the rom of your choice (either SlimKat or CM11).
If you installed SlimKat, you can now install the minimal_Slim_AIO_gapps file in the same way, then reboot the phone.
If you installed installed CM11, don't flash the Google Apps package yet, or it will conflict with the Cyanogenmod setup and cause an error. You must first reboot the phone and allow it to fully boot up. Then reboot the phone once more and go into TWRP recovery again. (Note: This time, you won't see the blue LED light; instead you'll see a screen indicating that you can press the menu button to enter the recovery.) Select Wipe > Advanced Wipe > and wipe the Dalvik Cache and the Cache. Then press the back button twice to return to the main menu and select Install, then install the GApps_Minimal_4.4.2 zip file, and reboot the phone.
Note: The first boot will take a while (typically 5-10 minutes), since the phone has to build the Dalvik Cache.
Step 4: Configure the Rom.
Go to System settings > Advanced options > Device > Baseband selection, and make sure that the correct baseband is selected for your region and carrier.
Open the HWA Settings app (which is already installed as part of the rom) and disable HWA for all apps except ones that really need it. (I disable HWA for everything except the camera. The latest version of Google Maps also requires HWA, but I’m using an older version that doesn’t.)
I recommend installing Aero Control from the Google Play store, which will allow you to tweak many settings to improve the performance of your phone. I'll post some suggested settings when I have time later; but for starters, I recommend the following: In the Aero Control app, go to CPU Performance > Governor Settings, and select “ondemand”. The default is Interactive governor, which may be able to deliver slightly better performance if you know how to tweak its settings, but its default settings aren’t very good, so I recommend using On Demand at least initially.
I also recommend installing Greenify, which you can use to “hibernate” any apps that you don’t want to run automatically at startup.
Step 5: Thank our awesome developers, and donate to them if you can.
Click to expand...
Click to collapse
Hey
very usefull guide, thank you for it.
Two suggestions
Can you add how to switch back to CM7 from CM11 for those that installed and did not liked it?
and SBFS this Guide is intented for those who already know alot of topics like TWRP
can you insert a referneces to guide explaining how to root?
Thanks @measel and @yosef_a for your suggestions. I'll try to implement these ideas as soon as I have time.
Nice Guide
Thanks @Proverbs2 for this great guide.
For the sake of completeness, I would suggest you to add a section in the post on How to safely update from one nightly to a another newer/older nightly.
Iloveyou and thanks for that guide I've made my first succeded rom install ever
MelaPL said:
Iloveyou and thanks for that guide I've made my first succeded rom install ever
Click to expand...
Click to collapse
Congratulations! :laugh:
Aero kernel on SlimKat
Hello, first of all great guide, big thanks.
Did anyone have this problem using Aero Kernel (which is still awesome app :good on SK, every time i instal Aero k. and start to using it phone display become so dark that only in total dark place (brightnes is set to auto) is posible to read (relly hard), and after uninstaling AK every is fine
Did I miss something? tx
Mislav12 said:
Hello, first of all great guide, big thanks.
Did anyone have this problem using Aero Kernel (which is still awesome app :good on SK, every time i instal Aero k. and start to using it phone display become so dark that only in total dark place (brightnes is set to auto) is posible to read (relly hard), and after uninstaling AK every is fine
Did I miss something? tx
Click to expand...
Click to collapse
That's a strange bug. I'm using Aero Control on SlimKat 4.0, and I've never had that problem. Which SlimKat version are you using? Are you using the latest version of Aero Control from the Play store?
Proverbs2 said:
That's a strange bug. I'm using Aero Control on SlimKat 4.0, and I've never had that problem. Which SlimKat version are you using? Are you using the latest version of Aero Control from the Play store?
Click to expand...
Click to collapse
Firs of all thaks for reply.
I'm got one device on SK 3.85 (20140323) and other on 4.0 (didn't try to use aero kernel because of problems with first one-stupid me), eveythig working great, (first time I instal it, SK take my breath, really can't searching for more with that old and hardware limited device like Defy is). Used Aero Kernel from Play store, these days was the latest (about month ago), take a chance 3-4 times during 10 days but allways with same result - start to using AK, about 5-10 hours having no issue and then darknes
Another thing that I notice (forgive me if i'm on wrong thread, can't make post on dev section), when my devices was on stock ROM after installing 2nd booth app (nothing else) the phones start to have screen wake up delay, just like now, 2-3 sec. Is it possible to exist some connection or is just coincidence!?
Mislav12 said:
start to using AK, about 5-10 hours having no issue and then darknes
Click to expand...
Click to collapse
In Aero Control settings, try going to GPU Control > Display Color, and make sure "Energy Saver" is not selected.
after installing 2nd booth app (nothing else) the phones start to have screen wake up delay, just like now, 2-3 sec. Is it possible to exist some connection or is just coincidence!?
Click to expand...
Click to collapse
Do you mean 2nd Boot (not Booth)? What exactly are you installing, and where did you get it?
Have you tried changing your governor settings for better wake-up performance? The default governor (Interactive) is set to limit the CPU frequency to 600 MHz when the screen is off, which can cause slow wakeup. In Aero Control, try changing the governor to OnDemand (or set suspend_enabled to 0 for Interactive governor). That might help.
Proverbs2 said:
In Aero Control settings, try going to GPU Control > Display Color, and make sure "Energy Saver" is not selected.
Do you mean 2nd Boot (not Booth)? What exactly are you installing, and where did you get it?
Click to expand...
Click to collapse
You're wright, there is no left or right boot for Defy :silly:, i was thinking about 2ndInitDefy app, just didn't read well before posted. Defy on stock ROM with this app (only rooted, and 2ndInit installed!) became lagy when call is reciving.
Have you tried changing your governor settings for better wake-up performance? The default governor (Interactive) is set to limit the CPU frequency to 600 MHz when the screen is off, which can cause slow wakeup. In Aero Control, try changing the governor to OnDemand (or set suspend_enabled to 0 for Interactive governor). That might help.
Click to expand...
Click to collapse
Will try tomorrow and report.
Thanks a lott.
Mislav12 said:
i was thinking about 2ndInitDefy app, just didn't read well before posted. Defy on stock ROM with this app (only rooted, and 2ndInit installed!) became lagy when call is reciving.
Click to expand...
Click to collapse
That's very strange. I wonder if the SndInitDefy app is somehow conflicting with another app that you use. Try taking logs with CatLog and see if that provides any clues.
Proverbs2 said:
That's very strange. I wonder if the SndInitDefy app is somehow conflicting with another app that you use. Try taking logs with CatLog and see if that provides any clues.
Click to expand...
Click to collapse
To late for log taking, won't go back on stock rom. Beside, settings for Aero K. you recommend are super, no problem annymore. Got my voice on presidential elections!:good:
Thanks for compiling this guide. I've been using OmniRom for some weeks on both my Defys and it's worked with very few problems. I wanted to give Quarx latest build a try though, so followed your guide, as previously when I've flashed Quarx CM11, I've had problems with the 4 lower buttons not working. However after attempting to install Safewipe from TWRP, my phone froze on the Moto logo and I had to flash the stock rom and start again. I'm running CM7.2 on my spare phone. Strange that Safewipe caused the very problem that it's meant to avoid on my phone.
Snugglehog said:
Thanks for compiling this guide. I've been using OmniRom for some weeks on both my Defys and it's worked with very few problems. I wanted to give Quarx latest build a try though, so followed your guide, as previously when I've flashed Quarx CM11, I've had problems with the 4 lower buttons not working. However after attempting to install Safewipe from TWRP, my phone froze on the Moto logo and I had to flash the stock rom and start again. I'm running CM7.2 on my spare phone. Strange that Safewipe caused the very problem that it's meant to avoid on my phone.
Click to expand...
Click to collapse
That's unusual. Did you remember to flash defy_twrp_recovery_2.6.3.0, reboot into TWRP version 2.6.3.0, and wait 30 seconds before flashing safewipe?
Proverbs2 said:
That's unusual. Did you remember to flash defy_twrp_recovery_2.6.3.0, reboot into TWRP version 2.6.3.0, and wait 30 seconds before flashing safewipe?
Click to expand...
Click to collapse
The TWRP version was integral to OmniRom, so I think it was v2.7.0.0. However after booting into TWRP I doubt I waited 30 seconds before flashing Safewipe. Why the need to wait?
Snugglehog said:
The TWRP version was integral to OmniRom, so I think it was v2.7.0.0. However after booting into TWRP I doubt I waited 30 seconds before flashing Safewipe. Why the need to wait?
Click to expand...
Click to collapse
TWRP is unstable, and sometimes causes random reboots within the first 20 seconds. I'm guessing your phone rebooted while flashing safewipe.
Home buuton stopped working
After a couple of months of using slimkat v.3.85 today home button stopped working. There is also problem with notification, and telephony (not able to reach the phone, but making calls from device is possible). I found that someone has similar symptoms in Quarks kk4.4 thread:
Sounds like the device got 'unprovisioned', this sometimes happens and leads to at least some of the effects you listed: status bar problems, home button, settings. If you haven't nuked the thing yet you might try to manually set the provisioning bits:
Code:
#!/system/bin/sh
db=/data/data/com.android.providers.settings/databases/settings.db
prv_dev="INSERT INTO secure (name,value) VALUES ('device_provisioned','1'); INSERT INTO global (name,value) VALUES ('device_provisioned','1'); INSERT INTO secure (name,value) VALUES ('user_setup_complete','1');"
/system/xbin/sqlite3 "$db" "$prv_dev"
Click to expand...
Click to collapse
I'v tried tu run that script but with no luck, i am getting errors. It is probably becaouse this script is for Quarq KK not SLimkat.
Any Help? (Sorry for posting this question here, but i am unable to post in dev section.)
ktwist said:
After a couple of months of using slimkat v.3.85 today home button stopped working. There is also problem with notification, and telephony (not able to reach the phone, but making calls from device is possible). I found that someone has similar symptoms in Quarks kk4.4 thread:
I'v tried tu run that script but with no luck, i am getting errors. It is probably becaouse this script is for Quarq KK not SLimkat.
Any Help? (Sorry for posting this question here, but i am unable to post in dev section.)
Click to expand...
Click to collapse
I've never run into that problem, and I don't know if there's any easy way to fix it, but you could try just wiping data then restoring your apps and settings with Titanium Backup. Make a nandroid backup (so if wiping data doesn't help you can restore all your data easily), then wipe data, cache, and dalvik. If that doesn't work, you may have to do a clean install.

[Q&A] [ROM]TN.kitkat.4.4.2.HTC.evo.supersonic(aosp)viper.mod. a2sd_updated4/26/14

Q&A for [ROM]TN.kitkat.4.4.2.HTC.evo.supersonic(aosp)viper.mod. a2sd_updated4/26/14
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
I'm running supersonic, hboot 6.16 with S-OFF. Have TWRP 2.8 Installed and flashed the TN kitkat rom and gapps core together but play store and the other Gapps do not show up. Someone suggested that using TWRP 2.7.0.0 worked for them, however, flashing 2.7.0.0 through bootloader gives a Fail-PU Update Fail and trying to flash it via fastboot also fails. So far, 2.7.0.0 is the only version of TWRP that fails to install. Any suggestions for getting gapps to work on this rom? I've tried flashing several other kk gapp packs, but they all fail with a message about not being able to run the update script in the zip file.
paultyler82 said:
I'm running supersonic, hboot 6.16 with S-OFF. Have TWRP 2.8 Installed and flashed the TN kitkat rom and gapps core together but play store and the other Gapps do not show up. Someone suggested that using TWRP 2.7.0.0 worked for them, however, flashing 2.7.0.0 through bootloader gives a Fail-PU Update Fail and trying to flash it via fastboot also fails. So far, 2.7.0.0 is the only version of TWRP that fails to install. Any suggestions for getting gapps to work on this rom? I've tried flashing several other kk gapp packs, but they all fail with a message about not being able to run the update script in the zip file.
Click to expand...
Click to collapse
TWRP 2.8 is probably fine - the GApps packages are likely just too large and the flash is failing because your system partition is full.
What do I need to do to get gapps working then? The posted gapps core package doesn't fail on flash like other gapp packs, but the market and other apps never show up.
paultyler82 said:
What do I need to do to get gapps working then? The posted gapps core package doesn't fail on flash like other gapp packs, but the market and other apps never show up.
Click to expand...
Click to collapse
Have you tried downloading the latest core GApps through the EV Updater in the ROM?
(I assume this ROM has that)
Just tried that, flashed through recovery, EV Update only lets you flash gapps in conjunction with a nightly. Flash seemed to succeed, but no luck. Gapps not appearing, nowhere to enter google account in the UI.
paultyler82 said:
Just tried that, flashed through recovery, EV Update only lets you flash gapps in conjunction with a nightly. Flash seemed to succeed, but no luck. Gapps not appearing, nowhere to enter google account in the UI.
Click to expand...
Click to collapse
Can you use the File Manager in Recovery to navigate to /system/priv-app and look for the Google apps? Maybe try extracting them from the zip and manually copying them and setting permissions? There must be some explanation. I've never had a problem with GApps. Can you try fully wiping (including system) and flash the ROM and core GApps again, just to be sure?
Ok. Wiped and reflashed. Odd thing is, before rebooting, the gapps appear to be in /system, however, on restart, they don't show up and when browsing to /system in ES File Explorer, the gapps have disappeared. I have never seen anything like it before, but then, I haven't played with Evos much.
paultyler82 said:
Ok. Wiped and reflashed. Odd thing is, before rebooting, the gapps appear to be in /system, however, on restart, they don't show up and when browsing to /system in ES File Explorer, the gapps have disappeared. I have never seen anything like it before, but then, I haven't played with Evos much.
Click to expand...
Click to collapse
You are wiping system, right?
Ok, tried a few more times now, let me walk you through what I've done.
First, using TWRP, I go to Wipe>Advanced Wipe and select EVERYTHING except sdcard, do the wipe. No errors.
Next, Install. I've now tried both TN KitKat and gapps together, gapps seperately after KitKat, and gapps seperately before KitKat
Each time the result is the same, new boot into KitKat results in the first run demo and no gapps to be found.
Here is the odd part I've now noticed that makes me think either I'm not doing something right, or TWRP isn't treating system correctly. All references to TWRP's file manager means using Advanced>File Manager.
On a new wipe, TWRP's file manager shows usr and bin directories in /system.
After any of the above methods of flashing, TWRP's file manager shows usr and bin AND everything from the gapps package but nothing from the KitKat package.
After first boot, ES File Explorer shows everything expected from the KitKat package in /system and nothing from gapps.
After first boot, rebooting into TWRP and using it's file manager shows only usr and bin present in /system, none of the KitKat or gapps stuff, yet booting back into the system works fine and ES File Explorer continues to show the KitKat stuff in /system.
Attempting to flash the gapps package in again after first boot gives the same results as above.
Attempting to copy anything into /system via ES File Explorer fails on a Read Only error.
Attempting to copy gapps into /system via TWRP file manager gives the same results as flashing the package.
Some other info that may or may not help... Using the Repair or Change File System tool in the Advanced Wipe menu reports the following for System partition: Mount Point: /system, File System: yaffs2, Present: Yes, Removable: No, Size: 350MB, Used: 317MB, Free: 32MB, Backup Size: 317MB
I appreciate the help, I'm thinking that certainly I've missed something along the way, but I can't figure out what.
paultyler82 said:
Ok, tried a few more times now, let me walk you through what I've done.
First, using TWRP, I go to Wipe>Advanced Wipe and select EVERYTHING except sdcard, do the wipe. No errors.
Next, Install. I've now tried both TN KitKat and gapps together, gapps seperately after KitKat, and gapps seperately before KitKat
Each time the result is the same, new boot into KitKat results in the first run demo and no gapps to be found.
Here is the odd part I've now noticed that makes me think either I'm not doing something right, or TWRP isn't treating system correctly. All references to TWRP's file manager means using Advanced>File Manager.
On a new wipe, TWRP's file manager shows usr and bin directories in /system.
After any of the above methods of flashing, TWRP's file manager shows usr and bin AND everything from the gapps package but nothing from the KitKat package.
After first boot, ES File Explorer shows everything expected from the KitKat package in /system and nothing from gapps.
After first boot, rebooting into TWRP and using it's file manager shows only usr and bin present in /system, none of the KitKat or gapps stuff, yet booting back into the system works fine and ES File Explorer continues to show the KitKat stuff in /system.
Attempting to flash the gapps package in again after first boot gives the same results as above.
Attempting to copy anything into /system via ES File Explorer fails on a Read Only error.
Attempting to copy gapps into /system via TWRP file manager gives the same results as flashing the package.
Some other info that may or may not help... Using the Repair or Change File System tool in the Advanced Wipe menu reports the following for System partition: Mount Point: /system, File System: yaffs2, Present: Yes, Removable: No, Size: 350MB, Used: 317MB, Free: 32MB, Backup Size: 317MB
I appreciate the help, I'm thinking that certainly I've missed something along the way, but I can't figure out what.
Click to expand...
Click to collapse
That's because you have to mount system in TWRP to see the actual contents.
What is the exact GApps package you're flashing?
I tried using both the gapps-core-kk-2013-11-25.zip posted in the OP, as well as gapps-kk442-20131211-core.zip from the EVUpdater.
I think I may have just gotten this to work, Play store is showing up. My solution was to manually mount /dev/block/mtdblock4 to /system via ADB and THEN flash the gapps package. Does TWRP not automatically mount NAND to /system? I didn't see an option anywhere in TWRP to mount partitions, the only thing I saw was the Mount menu item that seemed to be related to USB Media Device mounting, not actually mounting partitions. Did I miss something, for future reference?
paultyler82 said:
I tried using both the gapps-core-kk-2013-11-25.zip posted in the OP, as well as gapps-kk442-20131211-core.zip from the EVUpdater.
I think I may have just gotten this to work, Play store is showing up. My solution was to manually mount /dev/block/mtdblock4 to /system via ADB and THEN flash the gapps package. Does TWRP not automatically mount NAND to /system? I didn't see an option anywhere in TWRP to mount partitions, the only thing I saw was the Mount menu item that seemed to be related to USB Media Device mounting, not actually mounting partitions. Did I miss something, for future reference?
Click to expand...
Click to collapse
In the Mount menu in TWRP, there is a list of partitions and check boxes next to them. If you're not seeing that, then perhaps you have a bad recovery flash.
A recovery log would tell us exactly what's happening when you flash.
Thanks, figured that out now, mount via ADB accomplished the same thing.
Problem solved. The original directions call for both packages to be flashed at the same time, however, at least with TWRP 2.8.0.0, system appears to unmount after KitKat is flashed and gapps is installed to null. On this version of TWRP, you must flash KitKat, then mount system again via the Mount menu or ADB before flashing gapps. It seems that the KitKat package's script causes system to dismount and/or gapps package's script does not properly mount system on it's own.
---------- Post added at 10:18 PM ---------- Previous post was at 10:11 PM ----------
Also, thank you Captain for helping to solve the issue. I was apparently suffering from a serious case of terminal stupidity. It didn't even occur to me to manually mount system until you made the statement about having to mount it.
paultyler82 said:
Thanks, figured that out now, mount via ADB accomplished the same thing.
Problem solved. The original directions call for both packages to be flashed at the same time, however, at least with TWRP 2.8.0.0, system appears to unmount after KitKat is flashed and gapps is installed to null. On this version of TWRP, you must flash KitKat, then mount system again via the Mount menu or ADB before flashing gapps. It seems that the KitKat package's script causes system to dismount and/or gapps package's script does not properly mount system on it's own.
---------- Post added at 10:18 PM ---------- Previous post was at 10:11 PM ----------
Also, thank you Captain for helping to solve the issue. I was apparently suffering from a serious case of terminal stupidity. It didn't even occur to me to manually mount system until you made the statement about having to mount it.
Click to expand...
Click to collapse
Well it's weird that the updater-scripts aren't doing it. Like I said, I've never had an issue with flashing the ROM and GApps in TWRP.
I thought it was a bit weird as well, gonna have a look at the recovery log.
Found it. Gapps update script tries to run /sbin/busybox mount /system. This line fails because busybox isn't there, this failure only shows up in the recovery log, the script messages do not indicate that /system has failed to mount and the update script proceeds to run, installing to null and indicating install was successful.
And then there were two.
I still check in to this forum every day. And as far as I can tell, Vin and Cap are the only reason we are able put our legendary device in our pocket every day and know our rom and recovery are bleeding edge. Lollipop would be huge for our small but dedicated community. But for now the gift of KitKat plus a number of Android 5.0 apps gives me what I like to call "LolliKat". This is the most reliable phone I have ever owned! I hope I get to use it for another four years.
htc supersonic TN 4.4.4 problems
I installed TN 4.4.4 a month or so ago and keep having to reinstall at least once a week. The following problems occur:
Home button softkey quits working, while the menu and back soft keys still work.
Browser is inop, when i click it, it seems like it wants to open because a white screen pops up but then it disappears and goes back to my home screen.
I get no notifications in the status bar for anything.
Calls don't ring, i only know i have missed a call if i check my call history.
Lost theme settings, lost all info i setup on phone. Almost like it reset, except it didn't give me a welcome screen.
I am s-on, but i followed the s-on workaround.
When i hit the home button, catlog shows a keyguard msg, a dropping event because of a non touchable area, and a dalvik VM msg too.
Any ideas or suggestions?
cody85 said:
I installed TN 4.4.4 a month or so ago and keep having to reinstall at least once a week. The following problems occur:
Home button softkey quits working, while the menu and back soft keys still work.
Browser is inop, when i click it, it seems like it wants to open because a white screen pops up but then it disappears and goes back to my home screen.
I get no notifications in the status bar for anything.
Calls don't ring, i only know i have missed a call if i check my call history.
Lost theme settings, lost all info i setup on phone. Almost like it reset, except it didn't give me a welcome screen.
I am s-on, but i followed the s-on workaround.
When i hit the home button, catlog shows a keyguard msg, a dropping event because of a non touchable area, and a dalvik VM msg too.
Any ideas or suggestions?
Click to expand...
Click to collapse
im going to install this today.
---------- Post added at 11:02 PM ---------- Previous post was at 10:59 PM ----------
cryptickid715 said:
im going to install this today.
Click to expand...
Click to collapse
will there be a LP lol

Categories

Resources